From 8615806e4a69af402ce1b5ec480b962d312c1802 Mon Sep 17 00:00:00 2001 From: yoichigmf Date: Mon, 1 Jul 2024 04:11:54 +0900 Subject: [PATCH] i18n update for ja and en --- doc/source/conf.py | 8 + doc/source/locale/en/LC_MESSAGES/about.po | 55 + .../locale/en/LC_MESSAGES/about_no_title.po | 51 + doc/source/locale/en/LC_MESSAGES/api.po | 10030 +++ doc/source/locale/en/LC_MESSAGES/community.po | 691 + .../locale/en/LC_MESSAGES/contributing.po | 45 + .../locale/en/LC_MESSAGES/development.po | 31662 ++++++++++ doc/source/locale/en/LC_MESSAGES/download.po | 251 + .../locale/en/LC_MESSAGES/download_past.po | 411 + doc/source/locale/en/LC_MESSAGES/drivers.po | 51208 ++++++++++++++++ doc/source/locale/en/LC_MESSAGES/faq.po | 198 + doc/source/locale/en/LC_MESSAGES/index.po | 76 + doc/source/locale/en/LC_MESSAGES/index_pdf.po | 29 + doc/source/locale/en/LC_MESSAGES/license.po | 63 + doc/source/locale/en/LC_MESSAGES/programs.po | 10322 ++++ .../en/LC_MESSAGES/software_using_gdal.po | 731 + doc/source/locale/en/LC_MESSAGES/sponsors.po | 312 + doc/source/locale/en/LC_MESSAGES/tutorials.po | 4534 ++ doc/source/locale/en/LC_MESSAGES/user.po | 7545 +++ doc/source/locale/ja/LC_MESSAGES/about.mo | Bin 0 -> 2071 bytes doc/source/locale/ja/LC_MESSAGES/about.po | 61 + .../locale/ja/LC_MESSAGES/about_no_title.mo | Bin 0 -> 2071 bytes .../locale/ja/LC_MESSAGES/about_no_title.po | 57 + doc/source/locale/ja/LC_MESSAGES/api.mo | Bin 0 -> 701 bytes doc/source/locale/ja/LC_MESSAGES/api.po | 10030 +++ doc/source/locale/ja/LC_MESSAGES/community.mo | Bin 0 -> 429 bytes doc/source/locale/ja/LC_MESSAGES/community.po | 691 + .../locale/ja/LC_MESSAGES/contributing.mo | Bin 0 -> 622 bytes .../locale/ja/LC_MESSAGES/contributing.po | 45 + .../locale/ja/LC_MESSAGES/development.mo | Bin 0 -> 507 bytes .../locale/ja/LC_MESSAGES/development.po | 31662 ++++++++++ doc/source/locale/ja/LC_MESSAGES/download.mo | Bin 0 -> 609 bytes doc/source/locale/ja/LC_MESSAGES/download.po | 251 + .../locale/ja/LC_MESSAGES/download_past.mo | Bin 0 -> 481 bytes .../locale/ja/LC_MESSAGES/download_past.po | 411 + doc/source/locale/ja/LC_MESSAGES/drivers.mo | Bin 0 -> 415 bytes doc/source/locale/ja/LC_MESSAGES/drivers.po | 51208 ++++++++++++++++ doc/source/locale/ja/LC_MESSAGES/faq.mo | Bin 0 -> 415 bytes doc/source/locale/ja/LC_MESSAGES/faq.po | 198 + doc/source/locale/ja/LC_MESSAGES/index.mo | Bin 0 -> 2043 bytes doc/source/locale/ja/LC_MESSAGES/index.po | 82 + doc/source/locale/ja/LC_MESSAGES/index_pdf.mo | Bin 0 -> 415 bytes doc/source/locale/ja/LC_MESSAGES/index_pdf.po | 29 + doc/source/locale/ja/LC_MESSAGES/license.mo | Bin 0 -> 415 bytes doc/source/locale/ja/LC_MESSAGES/license.po | 63 + doc/source/locale/ja/LC_MESSAGES/programs.mo | Bin 0 -> 415 bytes doc/source/locale/ja/LC_MESSAGES/programs.po | 10322 ++++ .../ja/LC_MESSAGES/software_using_gdal.mo | Bin 0 -> 415 bytes .../ja/LC_MESSAGES/software_using_gdal.po | 731 + doc/source/locale/ja/LC_MESSAGES/sponsors.mo | Bin 0 -> 415 bytes doc/source/locale/ja/LC_MESSAGES/sponsors.po | 312 + doc/source/locale/ja/LC_MESSAGES/tutorials.mo | Bin 0 -> 415 bytes doc/source/locale/ja/LC_MESSAGES/tutorials.po | 4534 ++ doc/source/locale/ja/LC_MESSAGES/user.mo | Bin 0 -> 415 bytes doc/source/locale/ja/LC_MESSAGES/user.po | 7545 +++ 55 files changed, 236454 insertions(+) create mode 100644 doc/source/locale/en/LC_MESSAGES/about.po create mode 100644 doc/source/locale/en/LC_MESSAGES/about_no_title.po create mode 100644 doc/source/locale/en/LC_MESSAGES/api.po create mode 100644 doc/source/locale/en/LC_MESSAGES/community.po create mode 100644 doc/source/locale/en/LC_MESSAGES/contributing.po create mode 100644 doc/source/locale/en/LC_MESSAGES/development.po create mode 100644 doc/source/locale/en/LC_MESSAGES/download.po create mode 100644 doc/source/locale/en/LC_MESSAGES/download_past.po create mode 100644 doc/source/locale/en/LC_MESSAGES/drivers.po create mode 100644 doc/source/locale/en/LC_MESSAGES/faq.po create mode 100644 doc/source/locale/en/LC_MESSAGES/index.po create mode 100644 doc/source/locale/en/LC_MESSAGES/index_pdf.po create mode 100644 doc/source/locale/en/LC_MESSAGES/license.po create mode 100644 doc/source/locale/en/LC_MESSAGES/programs.po create mode 100644 doc/source/locale/en/LC_MESSAGES/software_using_gdal.po create mode 100644 doc/source/locale/en/LC_MESSAGES/sponsors.po create mode 100644 doc/source/locale/en/LC_MESSAGES/tutorials.po create mode 100644 doc/source/locale/en/LC_MESSAGES/user.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/about.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/about.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/about_no_title.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/about_no_title.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/api.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/api.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/community.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/community.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/contributing.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/contributing.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/development.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/development.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/download.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/download.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/download_past.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/download_past.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/drivers.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/drivers.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/faq.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/faq.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/index.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/index.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/index_pdf.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/index_pdf.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/license.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/license.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/programs.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/programs.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/software_using_gdal.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/software_using_gdal.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/sponsors.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/sponsors.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/tutorials.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/tutorials.po create mode 100644 doc/source/locale/ja/LC_MESSAGES/user.mo create mode 100644 doc/source/locale/ja/LC_MESSAGES/user.po diff --git a/doc/source/conf.py b/doc/source/conf.py index 091075678639..f1b853f87bfb 100644 --- a/doc/source/conf.py +++ b/doc/source/conf.py @@ -89,6 +89,14 @@ # Cf https://stackoverflow.com/questions/15258831/how-to-handle-two-dashes-in-rest smartquotes = False + + +gettext_compact = True + +locale_dirs = ['locale/'] + +language = 'en' + # Read the file of substitutions and append it to the beginning of each file. # This avoids the need to add an explicit ..include directive to every file. rst_prolog = open(os.path.join(os.path.dirname(__file__), "substitutions.rst")).read() diff --git a/doc/source/locale/en/LC_MESSAGES/about.po b/doc/source/locale/en/LC_MESSAGES/about.po new file mode 100644 index 000000000000..0e978b7bb2e9 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/about.po @@ -0,0 +1,55 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: en\n" +"Language-Team: en \n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/about.rst:5 +msgid "What is GDAL?" +msgstr "" + +#: ../../source/about_no_title.rst:1 +msgid "" +"GDAL is a translator library for raster and vector geospatial data " +"formats that is released under an MIT style Open Source :ref:`license` by" +" the `Open Source Geospatial Foundation`_. As a library, it presents a " +"single raster abstract data model and single vector abstract data model " +"to the calling application for all supported formats. It also comes with " +"a variety of useful command line utilities for data translation and " +"processing. The `NEWS`_ page describes the June 2024 GDAL/OGR 3.9.1 " +"release." +msgstr "" + +#: ../../source/about_no_title.rst:-1 +msgid "OSGeo project" +msgstr "" + +#: ../../source/about_no_title.rst:10 +msgid "See :ref:`software_using_gdal`" +msgstr "" + +#: ../../source/about_no_title.rst:16 +msgid "" +"You may quote GDAL in publications by using the following Digital Object " +"Identifier: |DOI|" +msgstr "" + +#: ../../source/about_no_title.rst +msgid "DOI 10.5281/zenodo.5884351" +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/about_no_title.po b/doc/source/locale/en/LC_MESSAGES/about_no_title.po new file mode 100644 index 000000000000..89680998e936 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/about_no_title.po @@ -0,0 +1,51 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: en\n" +"Language-Team: en \n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/about_no_title.rst:1 +msgid "" +"GDAL is a translator library for raster and vector geospatial data " +"formats that is released under an MIT style Open Source :ref:`license` by" +" the `Open Source Geospatial Foundation`_. As a library, it presents a " +"single raster abstract data model and single vector abstract data model " +"to the calling application for all supported formats. It also comes with " +"a variety of useful command line utilities for data translation and " +"processing. The `NEWS`_ page describes the June 2024 GDAL/OGR 3.9.1 " +"release." +msgstr "" + +#: ../../source/about_no_title.rst:-1 +msgid "OSGeo project" +msgstr "" + +#: ../../source/about_no_title.rst:10 +msgid "See :ref:`software_using_gdal`" +msgstr "" + +#: ../../source/about_no_title.rst:16 +msgid "" +"You may quote GDAL in publications by using the following Digital Object " +"Identifier: |DOI|" +msgstr "" + +#: ../../source/about_no_title.rst +msgid "DOI 10.5281/zenodo.5884351" +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/api.po b/doc/source/locale/en/LC_MESSAGES/api.po new file mode 100644 index 000000000000..86dcfa81f5f1 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/api.po @@ -0,0 +1,10030 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: en\n" +"Language-Team: en \n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/api/cpl.rst:10 +msgid "Common Portability Library C API" +msgstr "" + +#: ../../source/api/cpl.rst:13 +msgid "cpl_conv.h" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/gdal_alg.rst +#: ../../source/api/gdalwarp_cpp.rst ../../source/api/gnm_cpp.rst +#: ../../source/api/ogr_srs_api.rst ../../source/api/ogrspatialref.rst +#: ../../source/api/raster_c_api.rst ../../source/api/vector_c_api.rst +msgid "Defines" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdal_alg.rst ../../source/api/gdal_utils.rst +#: ../../source/api/gdalwarp_cpp.rst ../../source/api/gnm_cpp.rst +#: ../../source/api/ogr_srs_api.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/raster_c_api.rst ../../source/api/vector_c_api.rst +msgid "Typedefs" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdal_alg.rst ../../source/api/gdal_utils.rst +#: ../../source/api/gdalwarp_cpp.rst ../../source/api/ogr_srs_api.rst +#: ../../source/api/ogrspatialref.rst ../../source/api/raster_c_api.rst +#: ../../source/api/vector_c_api.rst +msgid "Functions" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdal_alg.rst ../../source/api/gdal_utils.rst +#: ../../source/api/gdalabstractmdarray_cpp.rst +#: ../../source/api/gdalattribute_cpp.rst ../../source/api/gdaldataset_cpp.rst +#: ../../source/api/gdaldimension_cpp.rst ../../source/api/gdaldriver_cpp.rst +#: ../../source/api/gdalextendeddatatype_cpp.rst +#: ../../source/api/gdalgroup_cpp.rst ../../source/api/gdalmdarray_cpp.rst +#: ../../source/api/gdalrasterband_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/gnm_cpp.rst ../../source/api/ogr_srs_api.rst +#: ../../source/api/ogrfeature_cpp.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/ogrgeometry_cpp.rst ../../source/api/ogrlayer_cpp.rst +#: ../../source/api/ogrspatialref.rst ../../source/api/raster_c_api.rst +#: ../../source/api/vector_c_api.rst of osgeo.gdal.BuildVRT +#: osgeo.gdal.BuildVRTOptions osgeo.gdal.DEMProcessing +#: osgeo.gdal.DEMProcessingOptions osgeo.gdal.Grid osgeo.gdal.GridOptions +#: osgeo.gdal.Info osgeo.gdal.MultiDimInfo osgeo.gdal.MultiDimTranslate +#: osgeo.gdal.MultiDimTranslateOptions osgeo.gdal.Nearblack +#: osgeo.gdal.NearblackOptions osgeo.gdal.Rasterize osgeo.gdal.RasterizeOptions +#: osgeo.gdal.Translate osgeo.gdal.TranslateOptions osgeo.gdal.VectorTranslate +#: osgeo.gdal.VectorTranslateOptions osgeo.gdal.Warp osgeo.gdal.WarpOptions +#: osgeo.ogr.DataSource.CopyLayer osgeo.ogr.DataSource.CreateLayer +#: osgeo.ogr.DataSource.DeleteLayer osgeo.ogr.DataSource.ExecuteSQL +#: osgeo.ogr.DataSource.GetDriver osgeo.ogr.DataSource.GetLayerByName +#: osgeo.ogr.DataSource.GetLayerCount osgeo.ogr.DataSource.GetName +#: osgeo.ogr.DataSource.ReleaseResultSet osgeo.ogr.DataSource.TestCapability +#: osgeo.ogr.Feature.Clone osgeo.ogr.Feature.DumpReadable +#: osgeo.ogr.Feature.Equal osgeo.ogr.Feature.FillUnsetWithDefault +#: osgeo.ogr.Feature.GetDefnRef osgeo.ogr.Feature.GetFID +#: osgeo.ogr.Feature.GetFieldAsBinary osgeo.ogr.Feature.GetFieldAsDateTime +#: osgeo.ogr.Feature.GetFieldAsDouble osgeo.ogr.Feature.GetFieldAsDoubleList +#: osgeo.ogr.Feature.GetFieldAsInteger osgeo.ogr.Feature.GetFieldAsInteger64 +#: osgeo.ogr.Feature.GetFieldAsInteger64List +#: osgeo.ogr.Feature.GetFieldAsIntegerList osgeo.ogr.Feature.GetFieldAsString +#: osgeo.ogr.Feature.GetFieldAsStringList osgeo.ogr.Feature.GetFieldCount +#: osgeo.ogr.Feature.GetFieldDefnRef osgeo.ogr.Feature.GetFieldIndex +#: osgeo.ogr.Feature.GetGeomFieldCount osgeo.ogr.Feature.GetGeomFieldDefnRef +#: osgeo.ogr.Feature.GetGeomFieldIndex osgeo.ogr.Feature.GetGeomFieldRef +#: osgeo.ogr.Feature.GetNativeData osgeo.ogr.Feature.GetNativeMediaType +#: osgeo.ogr.Feature.GetStyleString osgeo.ogr.Feature.IsFieldNull +#: osgeo.ogr.Feature.IsFieldSet osgeo.ogr.Feature.IsFieldSetAndNotNull +#: osgeo.ogr.Feature.SetFID osgeo.ogr.Feature.SetFieldDoubleList +#: osgeo.ogr.Feature.SetFieldInteger64 osgeo.ogr.Feature.SetFieldInteger64List +#: osgeo.ogr.Feature.SetFieldIntegerList osgeo.ogr.Feature.SetFieldNull +#: osgeo.ogr.Feature.SetFieldString osgeo.ogr.Feature.SetFieldStringList +#: osgeo.ogr.Feature.SetFrom osgeo.ogr.Feature.SetFromWithMap +#: osgeo.ogr.Feature.SetGeomField osgeo.ogr.Feature.SetGeomFieldDirectly +#: osgeo.ogr.Feature.SetGeometry osgeo.ogr.Feature.SetGeometryDirectly +#: osgeo.ogr.Feature.SetNativeData osgeo.ogr.Feature.SetNativeMediaType +#: osgeo.ogr.Feature.SetStyleString osgeo.ogr.Feature.UnsetField +#: osgeo.ogr.Feature.Validate osgeo.ogr.FeatureDefn.AddFieldDefn +#: osgeo.ogr.FeatureDefn.AddGeomFieldDefn +#: osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn +#: osgeo.ogr.FeatureDefn.GetFieldCount osgeo.ogr.FeatureDefn.GetFieldDefn +#: osgeo.ogr.FeatureDefn.GetFieldIndex osgeo.ogr.FeatureDefn.GetGeomFieldCount +#: osgeo.ogr.FeatureDefn.GetGeomFieldDefn +#: osgeo.ogr.FeatureDefn.GetGeomFieldIndex osgeo.ogr.FeatureDefn.GetGeomType +#: osgeo.ogr.FeatureDefn.GetName osgeo.ogr.FeatureDefn.GetReferenceCount +#: osgeo.ogr.FeatureDefn.IsGeometryIgnored osgeo.ogr.FeatureDefn.IsSame +#: osgeo.ogr.FeatureDefn.IsStyleIgnored osgeo.ogr.FeatureDefn.SetGeomType +#: osgeo.ogr.FeatureDefn.SetGeometryIgnored +#: osgeo.ogr.FeatureDefn.SetStyleIgnored +#: osgeo.ogr.FieldDefn.GetAlternativeNameRef osgeo.ogr.FieldDefn.GetDefault +#: osgeo.ogr.FieldDefn.GetDomainName osgeo.ogr.FieldDefn.GetJustify +#: osgeo.ogr.FieldDefn.GetNameRef osgeo.ogr.FieldDefn.GetPrecision +#: osgeo.ogr.FieldDefn.GetSubType osgeo.ogr.FieldDefn.GetType +#: osgeo.ogr.FieldDefn.GetWidth osgeo.ogr.FieldDefn.IsDefaultDriverSpecific +#: osgeo.ogr.FieldDefn.IsIgnored osgeo.ogr.FieldDefn.IsNullable +#: osgeo.ogr.FieldDefn.IsUnique osgeo.ogr.FieldDefn.SetAlternativeName +#: osgeo.ogr.FieldDefn.SetDefault osgeo.ogr.FieldDefn.SetDomainName +#: osgeo.ogr.FieldDefn.SetIgnored osgeo.ogr.FieldDefn.SetJustify +#: osgeo.ogr.FieldDefn.SetName osgeo.ogr.FieldDefn.SetNullable +#: osgeo.ogr.FieldDefn.SetPrecision osgeo.ogr.FieldDefn.SetSubType +#: osgeo.ogr.FieldDefn.SetType osgeo.ogr.FieldDefn.SetUnique +#: osgeo.ogr.FieldDefn.SetWidth osgeo.ogr.FieldDefn.justify +#: osgeo.ogr.FieldDefn.precision osgeo.ogr.FieldDefn.type +#: osgeo.ogr.FieldDefn.width osgeo.ogr.Geometry.AssignSpatialReference +#: osgeo.ogr.Geometry.Buffer osgeo.ogr.Geometry.Contains +#: osgeo.ogr.Geometry.Crosses osgeo.ogr.Geometry.DelaunayTriangulation +#: osgeo.ogr.Geometry.Difference osgeo.ogr.Geometry.Disjoint +#: osgeo.ogr.Geometry.Distance osgeo.ogr.Geometry.Distance3D +#: osgeo.ogr.Geometry.Equals osgeo.ogr.Geometry.ExportToIsoWkb +#: osgeo.ogr.Geometry.ExportToWkb osgeo.ogr.Geometry.Intersection +#: osgeo.ogr.Geometry.Intersects osgeo.ogr.Geometry.MakeValid +#: osgeo.ogr.Geometry.Overlaps osgeo.ogr.Geometry.Segmentize +#: osgeo.ogr.Geometry.Set3D osgeo.ogr.Geometry.SetCoordinateDimension +#: osgeo.ogr.Geometry.SetMeasured osgeo.ogr.Geometry.Simplify +#: osgeo.ogr.Geometry.SimplifyPreserveTopology osgeo.ogr.Geometry.SymDifference +#: osgeo.ogr.Geometry.Touches osgeo.ogr.Geometry.Transform +#: osgeo.ogr.Geometry.TransformTo osgeo.ogr.Geometry.Union +#: osgeo.ogr.Geometry.Within osgeo.ogr.Layer.AlterFieldDefn +#: osgeo.ogr.Layer.Clip osgeo.ogr.Layer.CreateFeature +#: osgeo.ogr.Layer.CreateField osgeo.ogr.Layer.CreateGeomField +#: osgeo.ogr.Layer.DeleteFeature osgeo.ogr.Layer.DeleteField +#: osgeo.ogr.Layer.Erase osgeo.ogr.Layer.GetExtent osgeo.ogr.Layer.GetFeature +#: osgeo.ogr.Layer.GetFeatureCount osgeo.ogr.Layer.GetGeometryTypes +#: osgeo.ogr.Layer.Identity osgeo.ogr.Layer.Intersection +#: osgeo.ogr.Layer.ReorderField osgeo.ogr.Layer.ReorderFields +#: osgeo.ogr.Layer.SetAttributeFilter osgeo.ogr.Layer.SetFeature +#: osgeo.ogr.Layer.SetIgnoredFields osgeo.ogr.Layer.SetNextByIndex +#: osgeo.ogr.Layer.SetSpatialFilter osgeo.ogr.Layer.SetSpatialFilterRect +#: osgeo.ogr.Layer.SymDifference osgeo.ogr.Layer.TestCapability +#: osgeo.ogr.Layer.Union osgeo.ogr.Layer.Update osgeo.ogr.Layer.UpsertFeature +msgid "Parameters" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdal_alg.rst ../../source/api/gdal_utils.rst +#: ../../source/api/gdalabstractmdarray_cpp.rst +#: ../../source/api/gdalattribute_cpp.rst ../../source/api/gdaldataset_cpp.rst +#: ../../source/api/gdaldimension_cpp.rst ../../source/api/gdaldriver_cpp.rst +#: ../../source/api/gdalgroup_cpp.rst ../../source/api/gdalmdarray_cpp.rst +#: ../../source/api/gdalrasterband_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/gnm_cpp.rst ../../source/api/ogr_srs_api.rst +#: ../../source/api/ogrfeature_cpp.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/ogrgeometry_cpp.rst ../../source/api/ogrlayer_cpp.rst +#: ../../source/api/ogrspatialref.rst ../../source/api/raster_c_api.rst +#: ../../source/api/vector_c_api.rst of osgeo.ogr.DataSource.CopyLayer +#: osgeo.ogr.DataSource.CreateLayer osgeo.ogr.DataSource.DeleteLayer +#: osgeo.ogr.DataSource.ExecuteSQL osgeo.ogr.DataSource.GetDriver +#: osgeo.ogr.DataSource.GetLayerByName osgeo.ogr.DataSource.GetLayerCount +#: osgeo.ogr.DataSource.GetName osgeo.ogr.DataSource.TestCapability +#: osgeo.ogr.Feature.Clone osgeo.ogr.Feature.Equal osgeo.ogr.Feature.GetDefnRef +#: osgeo.ogr.Feature.GetFID osgeo.ogr.Feature.GetFieldAsBinary +#: osgeo.ogr.Feature.GetFieldAsDateTime osgeo.ogr.Feature.GetFieldAsDouble +#: osgeo.ogr.Feature.GetFieldAsDoubleList osgeo.ogr.Feature.GetFieldAsInteger +#: osgeo.ogr.Feature.GetFieldAsInteger64 +#: osgeo.ogr.Feature.GetFieldAsInteger64List +#: osgeo.ogr.Feature.GetFieldAsIntegerList osgeo.ogr.Feature.GetFieldAsString +#: osgeo.ogr.Feature.GetFieldAsStringList osgeo.ogr.Feature.GetFieldCount +#: osgeo.ogr.Feature.GetFieldDefnRef osgeo.ogr.Feature.GetFieldIndex +#: osgeo.ogr.Feature.GetGeomFieldCount osgeo.ogr.Feature.GetGeomFieldDefnRef +#: osgeo.ogr.Feature.GetGeomFieldIndex osgeo.ogr.Feature.GetGeometryRef +#: osgeo.ogr.Feature.GetNativeData osgeo.ogr.Feature.GetNativeMediaType +#: osgeo.ogr.Feature.GetStyleString osgeo.ogr.Feature.IsFieldNull +#: osgeo.ogr.Feature.IsFieldSet osgeo.ogr.Feature.IsFieldSetAndNotNull +#: osgeo.ogr.Feature.SetFID osgeo.ogr.Feature.SetFrom +#: osgeo.ogr.Feature.SetFromWithMap osgeo.ogr.Feature.SetGeomField +#: osgeo.ogr.Feature.SetGeomFieldDirectly osgeo.ogr.Feature.SetGeometry +#: osgeo.ogr.Feature.SetGeometryDirectly osgeo.ogr.Feature.Validate +#: osgeo.ogr.Feature.geometry osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn +#: osgeo.ogr.FeatureDefn.GetFieldCount osgeo.ogr.FeatureDefn.GetFieldDefn +#: osgeo.ogr.FeatureDefn.GetFieldIndex osgeo.ogr.FeatureDefn.GetGeomFieldCount +#: osgeo.ogr.FeatureDefn.GetGeomFieldDefn +#: osgeo.ogr.FeatureDefn.GetGeomFieldIndex osgeo.ogr.FeatureDefn.GetGeomType +#: osgeo.ogr.FeatureDefn.GetName osgeo.ogr.FeatureDefn.GetReferenceCount +#: osgeo.ogr.FeatureDefn.IsGeometryIgnored osgeo.ogr.FeatureDefn.IsSame +#: osgeo.ogr.FeatureDefn.IsStyleIgnored +#: osgeo.ogr.FieldDefn.GetAlternativeNameRef osgeo.ogr.FieldDefn.GetDefault +#: osgeo.ogr.FieldDefn.GetDomainName osgeo.ogr.FieldDefn.GetJustify +#: osgeo.ogr.FieldDefn.GetNameRef osgeo.ogr.FieldDefn.GetPrecision +#: osgeo.ogr.FieldDefn.GetSubType osgeo.ogr.FieldDefn.GetType +#: osgeo.ogr.FieldDefn.GetWidth osgeo.ogr.FieldDefn.IsDefaultDriverSpecific +#: osgeo.ogr.FieldDefn.IsIgnored osgeo.ogr.FieldDefn.IsNullable +#: osgeo.ogr.FieldDefn.IsUnique osgeo.ogr.FieldDefn.justify +#: osgeo.ogr.FieldDefn.precision osgeo.ogr.FieldDefn.type +#: osgeo.ogr.FieldDefn.width osgeo.ogr.Geometry.Boundary +#: osgeo.ogr.Geometry.Buffer osgeo.ogr.Geometry.Clone +#: osgeo.ogr.Geometry.Contains osgeo.ogr.Geometry.ConvexHull +#: osgeo.ogr.Geometry.CoordinateDimension osgeo.ogr.Geometry.Crosses +#: osgeo.ogr.Geometry.DelaunayTriangulation osgeo.ogr.Geometry.Difference +#: osgeo.ogr.Geometry.Disjoint osgeo.ogr.Geometry.Distance +#: osgeo.ogr.Geometry.Distance3D osgeo.ogr.Geometry.Equals +#: osgeo.ogr.Geometry.GetCoordinateDimension osgeo.ogr.Geometry.GetDimension +#: osgeo.ogr.Geometry.GetEnvelope osgeo.ogr.Geometry.GetEnvelope3D +#: osgeo.ogr.Geometry.GetGeometryType osgeo.ogr.Geometry.Intersection +#: osgeo.ogr.Geometry.Intersects osgeo.ogr.Geometry.Is3D +#: osgeo.ogr.Geometry.IsEmpty osgeo.ogr.Geometry.IsMeasured +#: osgeo.ogr.Geometry.IsRing osgeo.ogr.Geometry.IsSimple +#: osgeo.ogr.Geometry.IsValid osgeo.ogr.Geometry.MakeValid +#: osgeo.ogr.Geometry.Normalize osgeo.ogr.Geometry.Overlaps +#: osgeo.ogr.Geometry.PointOnSurface osgeo.ogr.Geometry.Polygonize +#: osgeo.ogr.Geometry.Simplify osgeo.ogr.Geometry.SimplifyPreserveTopology +#: osgeo.ogr.Geometry.SymDifference osgeo.ogr.Geometry.Touches +#: osgeo.ogr.Geometry.Transform osgeo.ogr.Geometry.TransformTo +#: osgeo.ogr.Geometry.Union osgeo.ogr.Geometry.UnionCascaded +#: osgeo.ogr.Geometry.Within osgeo.ogr.Layer.AlterFieldDefn +#: osgeo.ogr.Layer.Clip osgeo.ogr.Layer.CommitTransaction +#: osgeo.ogr.Layer.CreateFeature osgeo.ogr.Layer.CreateField +#: osgeo.ogr.Layer.CreateGeomField osgeo.ogr.Layer.DeleteFeature +#: osgeo.ogr.Layer.DeleteField osgeo.ogr.Layer.Erase +#: osgeo.ogr.Layer.FindFieldIndex osgeo.ogr.Layer.GetExtent +#: osgeo.ogr.Layer.GetFIDColumn osgeo.ogr.Layer.GetFeature +#: osgeo.ogr.Layer.GetFeatureCount osgeo.ogr.Layer.GetGeomType +#: osgeo.ogr.Layer.GetGeometryColumn osgeo.ogr.Layer.GetGeometryTypes +#: osgeo.ogr.Layer.GetLayerDefn osgeo.ogr.Layer.GetName +#: osgeo.ogr.Layer.GetNextFeature osgeo.ogr.Layer.GetSpatialFilter +#: osgeo.ogr.Layer.GetSpatialRef osgeo.ogr.Layer.Identity +#: osgeo.ogr.Layer.Intersection osgeo.ogr.Layer.ReorderField +#: osgeo.ogr.Layer.ReorderFields osgeo.ogr.Layer.RollbackTransaction +#: osgeo.ogr.Layer.SetAttributeFilter osgeo.ogr.Layer.SetFeature +#: osgeo.ogr.Layer.SetIgnoredFields osgeo.ogr.Layer.SetNextByIndex +#: osgeo.ogr.Layer.StartTransaction osgeo.ogr.Layer.SymDifference +#: osgeo.ogr.Layer.SyncToDisk osgeo.ogr.Layer.TestCapability +#: osgeo.ogr.Layer.Union osgeo.ogr.Layer.Update osgeo.ogr.Layer.UpsertFeature +msgid "Returns" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/gdal_alg.rst +#: ../../source/api/gdaldataset_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/ogr_srs_api.rst ../../source/api/raster_c_api.rst +#: ../../source/api/vector_c_api.rst +msgid "Public Members" +msgstr "" + +#: ../../source/api/cpl.rst:19 +msgid "cpl_csv.h" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/gdal_alg.rst +#: ../../source/api/gdalwarp_cpp.rst ../../source/api/gnm_cpp.rst +#: ../../source/api/ogr_srs_api.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/raster_c_api.rst ../../source/api/vector_c_api.rst +msgid "Enums" +msgstr "" + +#: ../../source/api/cpl.rst:25 +msgid "cpl_compressor.h" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param input_data" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param input_size" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param output_data" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param output_size" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param options" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param compressor_user_data" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/gdal_alg.rst +#: ../../source/api/gdalabstractmdarray_cpp.rst +#: ../../source/api/raster_c_api.rst +msgid "Return" +msgstr "" + +#: ../../source/api/cpl.rst:31 +msgid "cpl_error.h" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdalabstractmdarray_cpp.rst +#: ../../source/api/gdalattribute_cpp.rst ../../source/api/gdaldataset_cpp.rst +#: ../../source/api/gdaldimension_cpp.rst ../../source/api/gdaldriver_cpp.rst +#: ../../source/api/gdalextendeddatatype_cpp.rst +#: ../../source/api/gdalgroup_cpp.rst ../../source/api/gdalmdarray_cpp.rst +#: ../../source/api/gdalrasterband_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/gnm_cpp.rst ../../source/api/ogrfeature_cpp.rst +#: ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/ogrgeometry_cpp.rst ../../source/api/ogrlayer_cpp.rst +#: ../../source/api/ogrspatialref.rst ../../source/api/vector_c_api.rst +msgid "Public Functions" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdalwarp_cpp.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/ogrspatialref.rst +msgid "Private Members" +msgstr "" + +#: ../../source/api/cpl.rst:37 +msgid "cpl_http.h" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pszURL" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param papszOptions" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pfnProgress" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pProgressArg" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pfnWrite" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pWriteArg" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/gdalabstractmdarray_cpp.rst +#: ../../source/api/raster_c_api.rst +msgid "Param pUserData" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdalabstractmdarray_cpp.rst +#: ../../source/api/gdaldataset_cpp.rst ../../source/api/ogrgeometry_cpp.rst +#: ../../source/api/ogrlayer_cpp.rst +msgid "Public Types" +msgstr "" + +#: ../../source/api/cpl.rst:43 +msgid "cpl_minixml.h" +msgstr "" + +#: ../../source/api/cpl.rst:49 +msgid "cpl_multiproc.h" +msgstr "" + +#: ../../source/api/cpl.rst:55 +msgid "cpl_port.h" +msgstr "" + +#: ../../source/api/cpl.rst:61 +msgid "cpl_progress.h" +msgstr "" + +#: ../../source/api/cpl.rst:67 +msgid "cpl_string.h" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdaldataset_cpp.rst ../../source/api/gdaldriver_cpp.rst +#: ../../source/api/gdalextendeddatatype_cpp.rst +#: ../../source/api/gdalrasterband_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/ogrfeature_cpp.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/ogrgeometry_cpp.rst ../../source/api/ogrlayer_cpp.rst +#: ../../source/api/ogrspatialref.rst +msgid "Public Static Functions" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/gnm_cpp.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/ogrspatialref.rst +msgid "Private Functions" +msgstr "" + +#: ../../source/api/cpl.rst:73 +msgid "cpl_time.h" +msgstr "" + +#: ../../source/api/cpl.rst:79 +msgid "cpl_virtualmem.h" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param ctxt" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param nOffset" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pPageToFill" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param nToFill" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pPageToBeEvicted" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param nToBeEvicted" +msgstr "" + +#: ../../source/api/cpl.rst:85 +msgid "cpl_vsi_error.h" +msgstr "" + +#: ../../source/api/cpl.rst:91 +msgid "cpl_vsi.h" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pFile" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param nRanges" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param panOffsets" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param panSizes" +msgstr "" + +#: ../../:-1 +msgid "Install /vsisubfile/ virtual file handler." +msgstr "" + +#: ../../:-1 +msgid "See /vsisubfile/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Install /vsicurl/ HTTP/FTP file system handler (requires libcurl)" +msgstr "" + +#: ../../:-1 +msgid "See /vsicurl/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Since GDAL 1.8.0" +msgstr "" + +#: ../../:-1 +msgid "" +"Install /vsicurl_streaming/ HTTP/FTP file system handler (requires " +"libcurl)." +msgstr "" + +#: ../../:-1 +msgid "See /vsicurl_streaming/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Since GDAL 1.10" +msgstr "" + +#: ../../:-1 +msgid "Install /vsis3/ Amazon S3 file system handler (requires libcurl)" +msgstr "" + +#: ../../:-1 +msgid "See /vsis3/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Since GDAL 2.1" +msgstr "" + +#: ../../:-1 +msgid "" +"Install /vsis3_streaming/ Amazon S3 file system handler (requires " +"libcurl)." +msgstr "" + +#: ../../:-1 +msgid "See /vsis3_streaming/ documentation" +msgstr "" + +#: ../../:-1 +msgid "" +"Install /vsigs/ Google Cloud Storage file system handler (requires " +"libcurl)" +msgstr "" + +#: ../../:-1 +msgid "See /vsigs/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Since GDAL 2.2" +msgstr "" + +#: ../../:-1 +msgid "" +"Install /vsigs_streaming/ Google Cloud Storage file system handler " +"(requires libcurl)" +msgstr "" + +#: ../../:-1 +msgid "See /vsigs_streaming/ documentation" +msgstr "" + +#: ../../:-1 +msgid "" +"Install /vsiaz/ Microsoft Azure Blob file system handler (requires " +"libcurl)" +msgstr "" + +#: ../../:-1 +msgid "See /vsiaz/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Since GDAL 2.3" +msgstr "" + +#: ../../:-1 +msgid "" +"Install /vsiaz_streaming/ Microsoft Azure Blob file system handler " +"(requires libcurl)" +msgstr "" + +#: ../../:-1 +msgid "See /vsiaz_streaming/ documentation" +msgstr "" + +#: ../../:-1 +msgid "" +"Install /vsiaz/ Microsoft Azure Data Lake Storage Gen2 file system " +"handler (requires libcurl)" +msgstr "" + +#: ../../:-1 +msgid "See /vsiadls/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Since GDAL 3.3" +msgstr "" + +#: ../../:-1 +msgid "" +"Install /vsioss/ Alibaba Cloud Object Storage Service (OSS) file system " +"handler (requires libcurl)" +msgstr "" + +#: ../../:-1 +msgid "See /vsioss/ documentation" +msgstr "" + +#: ../../:-1 +msgid "" +"Install /vsiaz_streaming/ Alibaba Cloud Object Storage Service (OSS) " +"(requires libcurl)" +msgstr "" + +#: ../../:-1 +msgid "See /vsioss_streaming/ documentation" +msgstr "" + +#: ../../:-1 +msgid "" +"Install /vsiswift/ OpenStack Swif Object Storage (Swift) file system " +"handler (requires libcurl)" +msgstr "" + +#: ../../:-1 +msgid "See /vsiswift/ documentation" +msgstr "" + +#: ../../:-1 +msgid "" +"Install /vsiswift_streaming/ OpenStack Swif Object Storage (Swift) file " +"system handler (requires libcurl)" +msgstr "" + +#: ../../:-1 +msgid "See /vsiswift_streaming/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Install /vsi7z/ 7zip file system handler (requires libarchive)" +msgstr "" + +#: ../../:-1 +msgid "See /vsi7z/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Since GDAL 3.7" +msgstr "" + +#: ../../:-1 +msgid "Install /vsirar/ RAR file system handler (requires libarchive)" +msgstr "" + +#: ../../:-1 +msgid "See /vsirar/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Install GZip file system handler." +msgstr "" + +#: ../../:-1 +msgid "" +"A special file handler is installed that allows reading on-the-fly and " +"writing in GZip (.gz) files." +msgstr "" + +#: ../../:-1 +msgid "" +"All portions of the file system underneath the base path \"/vsigzip/\" " +"will be handled by this driver." +msgstr "" + +#: ../../:-1 +msgid "See /vsigzip/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Since GDAL 1.6.0" +msgstr "" + +#: ../../:-1 +msgid "Install ZIP file system handler." +msgstr "" + +#: ../../:-1 +msgid "" +"A special file handler is installed that allows reading on-the-fly in ZIP" +" (.zip) archives." +msgstr "" + +#: ../../:-1 +msgid "" +"All portions of the file system underneath the base path \"/vsizip/\" " +"will be handled by this driver." +msgstr "" + +#: ../../:-1 +msgid "See /vsizip/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Install /vsistdin/ file system handler." +msgstr "" + +#: ../../:-1 +msgid "" +"A special file handler is installed that allows reading from the standard" +" input stream." +msgstr "" + +#: ../../:-1 +msgid "" +"The file operations available are of course limited to Read() and forward" +" Seek() (full seek in the first MB of a file by default)." +msgstr "" + +#: ../../:-1 +msgid "" +"Starting with GDAL 3.6, this limit can be configured either by setting " +"the CPL_VSISTDIN_BUFFER_LIMIT configuration option to a number of bytes " +"(can be -1 for unlimited), or using the \"/vsistdin?buffer_limit=value\" " +"filename." +msgstr "" + +#: ../../:-1 +msgid "See /vsistdin/ documentation" +msgstr "" + +#: ../../:-1 +msgid "" +"Install /vsiwebhdfs/ WebHDFS (Hadoop File System) REST API file system " +"handler (requires libcurl)" +msgstr "" + +#: ../../:-1 +msgid "See /vsiwebhdfs/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Since GDAL 2.4" +msgstr "" + +#: ../../:-1 +msgid "Install /vsistdout/ file system handler." +msgstr "" + +#: ../../:-1 +msgid "" +"A special file handler is installed that allows writing to the standard " +"output stream." +msgstr "" + +#: ../../:-1 +msgid "The file operations available are of course limited to Write()." +msgstr "" + +#: ../../:-1 +msgid "" +"A variation of this file system exists as the /vsistdout_redirect/ file " +"system handler, where the output function can be defined with " +"VSIStdoutSetRedirection()." +msgstr "" + +#: ../../:-1 +msgid "See /vsistdout/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Install /vsisparse/ virtual file handler." +msgstr "" + +#: ../../:-1 +msgid "See /vsisparse/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Install /vsitar/ file system handler." +msgstr "" + +#: ../../:-1 +msgid "" +"A special file handler is installed that allows reading on-the-fly in TAR" +" (regular .tar, or compressed .tar.gz/.tgz) archives." +msgstr "" + +#: ../../:-1 +msgid "" +"All portions of the file system underneath the base path \"/vsitar/\" " +"will be handled by this driver." +msgstr "" + +#: ../../:-1 +msgid "See /vsitar/ documentation" +msgstr "" + +#: ../../:-1 +msgid "Install /vsicached? file system handler." +msgstr "" + +#: ../../:-1 +msgid "See /vsicached? documentation" +msgstr "" + +#: ../../:-1 +msgid "Since GDAL 3.8.0" +msgstr "" + +#: ../../source/api/cpl.rst:98 +msgid ":ref:`cpl_cpp_api`." +msgstr "" + +#: ../../source/api/cpl_cpp.rst:10 +msgid "Common Portability Library C++ API" +msgstr "" + +#: ../../source/api/cpl_cpp.rst:13 +msgid "cpl_odbc.h" +msgstr "" + +#: ../../source/api/cpl_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/ogrspatialref.rst +msgid "Private Static Functions" +msgstr "" + +#: ../../source/api/cpl_cpp.rst:19 +msgid "cpl_vsi_virtual.h" +msgstr "" + +#: ../../source/api/cpl_cpp.rst +msgid "Variables" +msgstr "" + +#: ../../source/api/cpl_cpp.rst:26 +msgid ":ref:`cpl_api`." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:5 +msgid "Compiling the C# bindings - CMake Scripts" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:7 +msgid "" +"This page describes the primary steps when creating the GDAL/OGR C# " +"binaries from the source using the new CMake scripts." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:9 +#: ../../source/api/csharp/csharp_compile_legacy.rst:9 +msgid "" +"In most cases this is not necessary and it is better to use one of the " +"pre-compiled sources, such as `GisInternals " +"`__ or Conda." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:11 +msgid "" +"You can either build the bindings as part of a full GDAL build - or " +"standalone on top of an existing installation." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:14 +#: ../../source/api/csharp/csharp_compile_legacy.rst:18 +#: ../../source/api/csharp/csharp_compile_legacy.rst:105 +msgid "Requirements" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:16 +#: ../../source/api/csharp/csharp_compile_legacy.rst:20 +#: ../../source/api/csharp/csharp_compile_legacy.rst:107 +msgid "The build environment has the following dependencies:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:18 +msgid "CMake 3.10 or later" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:19 +msgid "the appropriate C++ build environment (i.e. gcc or Visual Studio etc)." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:20 +msgid "SWIG 4" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:21 +msgid ".NET 5.0 or Mono" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:24 +msgid ".NET Build Toolchain" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:26 +msgid "" +"The build scripts can use either .NET 5.0 and :file:`dotnet.exe` or Mono" +" and :file:`msc.exe` to compile the bindings." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:28 +msgid "" +".NET is used for preference if it found on all platforms but the use of " +"Mono can be forced using a command line variable." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:31 +msgid "Building as part of a GDAL Build" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:33 +msgid "The build environment uses the following variables:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:36 +msgid "CSHARP_MONO" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:36 +#: ../../source/api/csharp/csharp_compile_cmake.rst:42 +#: ../../source/api/csharp/csharp_compile_cmake.rst:44 +msgid "Boolean" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:36 +msgid "Forces the use of Mono" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:38 +msgid "CSHARP_LIBRARY_VERSION" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:38 +#: ../../source/api/csharp/csharp_compile_cmake.rst:40 +msgid "String" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:38 +msgid "Set the .NET version for the shared libraries" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:40 +msgid "CSHARP_APPLICATION_VERSION" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:40 +msgid "Set the .NET version for the sample apps" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:42 +msgid "GDAL_CSHARP_ONLY" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:42 +msgid "Build standalone on GDAL binaries" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:44 +msgid "BUILD_CSHARP_BINDINGS" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:44 +msgid "Build the C# bindings DEFAULT ON" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:48 +msgid "Building with .NET" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:50 +msgid "" +"If the build environment has .NET 5.0 installed and GDAL is built, then " +"the c# bindings will be built using .NET by default." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:52 +msgid "" +"The details of building GDAL are documented elsewhere, but there are " +"likely to be variants of the following commands run from the root " +"directory of the gdal repository:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:60 +#: ../../source/api/csharp/csharp_compile_cmake.rst:115 +msgid "" +"The C# bindings and sample apps are installed in the install directory " +"(in the above case that would be `../install`, in the `share/csharp` sub " +"folder. There would be the following files:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:62 +#: ../../source/api/csharp/csharp_compile_cmake.rst:117 +#: ../../source/api/csharp/csharp_compile_legacy.rst:66 +msgid ":file:`gdal_csharp.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:63 +#: ../../source/api/csharp/csharp_compile_cmake.rst:118 +#: ../../source/api/csharp/csharp_compile_legacy.rst:67 +msgid ":file:`ogr_csharp.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:64 +#: ../../source/api/csharp/csharp_compile_cmake.rst:119 +#: ../../source/api/csharp/csharp_compile_legacy.rst:68 +msgid ":file:`osr_csharp.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:65 +#: ../../source/api/csharp/csharp_compile_cmake.rst:120 +#: ../../source/api/csharp/csharp_compile_legacy.rst:69 +msgid ":file:`gdalconst_csharp.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:66 +#: ../../source/api/csharp/csharp_compile_cmake.rst:121 +msgid "" +":file:`gdal_wrap.dll` or :file:`libgdal_wrap.so` or " +":file:`libgdal_wrap.dylib`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:67 +#: ../../source/api/csharp/csharp_compile_cmake.rst:122 +msgid "" +":file:`ogr_wrap.dll` or :file:`libogr_wrap.so` or " +":file:`libogr_wrap.dylib`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:68 +#: ../../source/api/csharp/csharp_compile_cmake.rst:69 +#: ../../source/api/csharp/csharp_compile_cmake.rst:123 +#: ../../source/api/csharp/csharp_compile_cmake.rst:124 +msgid "" +":file:`osr_wrap.dll` or :file:`libosr_wrap.so` or " +":file:`libosr_wrap.dylib`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:70 +#: ../../source/api/csharp/csharp_compile_cmake.rst:125 +msgid "" +":file:`gdalconst_wrap.dll` or :file:`libgdalconst_wrap.so` or " +":file:`libgdalconst_wrap.dylib`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:71 +msgid "" +"various sample applications - as \\*.exe on Windows, or just as \\* on " +"Unix, along with \\*.dll for each app and the runtime config files." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:73 +msgid "" +"There are also subdirectories for each of the sample apps, holding the " +"config files." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:75 +msgid "There are also the following NuGET packages:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:77 +msgid ":file:`OSGeo.GDAL`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:78 +msgid ":file:`OSGeo.OGR`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:79 +msgid ":file:`OSgeo.OSR`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:80 +msgid ":file:`OSGeo.GDAL.CONST`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:81 +msgid "various sample application" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:84 +msgid "Using the .NET Bindings" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:86 +msgid "" +"The easiest way to use the bindings in development would be use the NuGET" +" packages created." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:88 +msgid "" +"To do this you need to add a local repistory pointing to the GDAL install" +" directory. `This is explained here `__ ." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:90 +msgid "Once this is done, you add the GDAL packages into your project as normal." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:92 +msgid "" +"These packages only install the bindings and do not install core GDAL. It" +" is for you as the developer to make sure that the GDAL binaries are " +"available in the search path." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:95 +msgid "" +"The NuGET packages are created with the same version number as the " +"version of GDAL in the build system. If you are building in a GIT " +"repository, then the build system automatically makes the version with a " +"x.y.z-dev pre-release tag. This means that to load the package into " +"Visual Studio (for instance), you have to tick the pre-release box. This " +"is all intentional and not a bug." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:102 +msgid "Building on Mono" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:104 +msgid "" +"If the build environment does not have .NET 5.0 or msbuild installed and " +"GDAL is built, then the c# bindings will be built using Mono by default. " +"Mono building can also be forced by setting CSHARP_MONO." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:107 +msgid "" +"The details of building GDAL are documented elsewhere, but the there are " +"likely to be variants of the following commands run from the root " +"directory of the gdal repository:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:126 +msgid "various sample applications as \\*.exe on all platforms." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:129 +msgid "Using the Mono Bindings" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:131 +msgid "Note that the bindings created by this process will only work with Mono." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:133 +#: ../../source/api/csharp/csharp_compile_legacy.rst:177 +msgid "" +"To run one of the prebuilt executables - you can run them with Mono as " +"follows :" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:135 +#: ../../source/api/csharp/csharp_compile_legacy.rst:179 +msgid ":program:`mono GDALInfo.exe`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:137 +#: ../../source/api/csharp/csharp_compile_legacy.rst:181 +msgid "" +"Both the managed libraries (i.e. the DLLs) and the unmanaged libraries " +"must be available to Mono. This is in more detail in `the Mono " +"documentation `__" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:141 +msgid "Building Standalone" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:143 +msgid "" +"The Bindings using both the .NET or Mono toolchains can be build on top " +"of an existing implementation of GDAL that includes the include files and" +" libs - for instance the Conda distribution." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:146 +msgid "" +"To do this, Cmake must be run with the GDAL_CSHARP_ONLY flag set and only" +" one of the following targets should be built:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:150 +msgid "csharp_binding" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:150 +msgid "Just the bindings" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:152 +msgid "csharp_samples" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:152 +msgid "The bindings and the sample apps" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:155 +msgid "Do not build the install target when running standalone, it will fail!" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:157 +msgid "" +"Do not run a bare ctest command on this build, it will likely fail! Use " +"something like `ctest -R \"^csharp.*\"` instead." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:159 +msgid "As an example:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:166 +msgid "" +"The output from this build is axactly the same as documented as above, " +"except that the outputs will be in `../build/swig/csharp` and some of the" +" sub folders." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:169 +msgid "Signing of build artifacts" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:171 +msgid "" +"The CSharp assemblies are strong name signed by default with the provided" +" key file in :source_file:`swig/csharp/gdal.snk`. If authenticode signing" +" of the assemblies is wished, it should be done in a post-build manual " +"step, for example with:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:5 +msgid "Compiling the C# bindings - Legacy Scripts" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:7 +msgid "" +"This page describes the primary steps when creating the GDAL/OGR C# " +"binaries from the source." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:12 +msgid "Building on Windows" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:14 +msgid "" +"To building the C# interface, you need a compiled version of the GDAL " +"core. This can be the result of a manual compilation or can be linking to" +" one of the prebuilt binaries. In the former case the following should be" +" run in the clone of the GitHub repository used to build GDAL and the " +"steps to create the environment should not be necessary." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:22 +msgid "nmake / Visual Studio" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:23 +#: ../../source/api/csharp/csharp_compile_legacy.rst:110 +msgid "SWIG 3/4" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:25 +msgid "" +"The `GDAL test scripts " +"`__" +" use VS 2019 (MSVC Ver 1920) so it would make sense to use the same " +"versions." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:27 +msgid "" +"`SWIG `__ is used to build the API bindings. The " +"GDAL test scripts use version 3 and the conda build use version 4. Both " +"Work." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:30 +#: ../../source/api/csharp/csharp_compile_legacy.rst:114 +msgid "Build Environment" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:32 +msgid "" +"You need to set up the build environment. If you are using VS 2019, this " +"might be the command:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:34 +msgid ":program:`VsDevCmd.bat -arch=x64`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:36 +msgid "" +"The :program:`VsDevCmd.bat` command can usually be found in " +":file:`C:\\\\Program Files (x86)\\\\Microsoft Visual " +"Studio\\\\2019\\\\Enterprise\\\\Common7\\\\Tools` or the equivalent for " +"the Community Edition." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:38 +msgid "" +"If you don't want to bother with executing the proper vcvars*.bat you " +"might use the development environment specific command prompt to " +"accomplish this task. When using a Win64 compilation be careful to " +"activate the x64 version of the command prompt installed on your system." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:40 +msgid "" +"If you are not running in an environment that has been used to compile " +"GDAL locally, then there are a number of variables that need to be " +"configured. The Conda ``gdal-feedstock`` configuration app can be used as" +" a guideline about how to do that - `build.bat `__." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:43 +#: ../../source/api/csharp/csharp_compile_legacy.rst:121 +msgid "Creating the SWIG interface code" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:45 +msgid "" +"The first step is to generate the SWIG interface code. This will create a" +" set of ``.cs`` definitions that will be compiled into the ``.dll`` files" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:47 +msgid "" +"To create the interface execute the following command (from the " +"``swig\\csharp`` directory):" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:53 +msgid "" +"You should edit nmake.opt adding the actual location of the " +":file:`swig.exe` file." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:56 +#: ../../source/api/csharp/csharp_compile_legacy.rst:134 +msgid "Compiling the code" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:58 +msgid "" +"After creating the interface the code can be compiled using this command " +"(from the ``swig\\csharp`` directory):" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:64 +#: ../../source/api/csharp/csharp_compile_legacy.rst:142 +msgid "Upon a successful compilation the following files are created:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:70 +msgid ":file:`gdal_wrap.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:71 +msgid ":file:`ogr_wrap.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:72 +msgid ":file:`osr_wrap.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:73 +msgid ":file:`gdalconst_wrap.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:74 +msgid "various sample applications" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:76 +msgid "" +"The :file:`\\*_csharp.dll` binaries are the managed part of the " +"interface. You should add a reference to these assemblies for using the " +"classes of the interface. These :file:`\\*_csharp.dll` files will load " +"the corresponding :file:`\\*_wrap.dll` files, which are the unmanaged " +"part of the interface hosting the code of the gdal core." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:79 +#: ../../source/api/csharp/csharp_compile_legacy.rst:160 +msgid "Testing the successful compilation" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:81 +#: ../../source/api/csharp/csharp_compile_legacy.rst:162 +msgid "To test the compiled binaries, you can use:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:87 +#: ../../source/api/csharp/csharp_compile_legacy.rst:168 +msgid "This command will invoke some of the sample applications." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:89 +msgid "" +"For the tests to work the location of the proj and gdal DLLs should be " +"available in the PATH." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:92 +msgid "Using MONO on Windows" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:94 +msgid "" +"If you have the Windows version of the MONO package installed you can " +"compile the C# code using the MONO compiler. In this case uncomment the " +"following entry in csharp.opt:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:96 +msgid ":program:`MONO = YES`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:98 +msgid "mcs.exe must be in the PATH." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:102 +msgid "Building on Linux/OSX" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:109 +msgid "make" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:111 +msgid "mono (probably any reasonable version)" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:116 +msgid "" +"The build environment needs to be correctly configured. If you are not " +"running in an environment that has been used to locally build GDAL then " +"you should run the :program:`configure` command from the GDAL root " +"directory." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:118 +msgid "" +"The conda gdal-feedstock recipe provides an example of how to do that - " +"`build.sh `__" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:123 +msgid "" +"The first step is to generate the SWIG interface code. This will create a" +" set of :file:`.cs` definitions that will be compiled into the " +":file:`.dll` files" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:125 +msgid "" +"To create the interface execute the following command (from the " +":file:`swig/ csharp` directory):" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:131 +msgid "" +"In versions of GDAL < 3.3.0 - this command will create incorrect " +"interfaces without the correct namespace. See `#3670 " +"`__." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:136 +msgid "" +"After creating the interface the code can be compiled using this command " +"(from the :file:`swig/csharp` directory):" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:144 +msgid ":file:`gdal_csharp.dll` and :file:`gdal_csharp.dll.config`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:145 +msgid ":file:`ogr_csharp.dll` and :file:`ogr_csharp.dll.config`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:146 +msgid ":file:`osr_csharp.dll` and :file:`osr_csharp.dll.config`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:147 +msgid ":file:`gdalconst_csharp.dll` and :file:`gdalconst_csharp.dll.config`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:148 +msgid ":file:`libgdalcsharp.so / .dylib` etc" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:149 +msgid ":file:`libogrcsharp.so / .dylib` etc" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:150 +msgid ":file:`libosrcsharp.so / .dylib` etc" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:151 +msgid ":file:`libgdalconst_wrap.so / .dylib` etc" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:152 +msgid "various sample applications (:file:`\\*.exe`)" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:154 +msgid "" +"The :file:`\\*_csharp.dll` binaries are the managed part of the " +"interface. You should add a reference to these assemblies for using the " +"classes of the interface." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:156 +msgid "" +"The :file:`\\*_csharp.dll` files will try to load the corresponding " +":file:`\\*_wrap.dll` and are redirected to the :file:`libxxxcsharp.\\*` " +"libraries, which are the unmanaged part of the interface hosting the code" +" of the gdal core, by the :file:`\\*.dll.config` definitions." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:170 +msgid "" +"For the tests to work the location of the proj and gdal libraries should " +"be available in the PATH." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:173 +msgid "Using The Bindings on Unix" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:175 +msgid "" +"Note that the bindings created by this process will only work with Mono " +"at the moment." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:184 +msgid "" +"This document was amended from the previous version at " +"`https://trac.osgeo.org/gdal/wiki/GdalOgrCsharpCompile " +"`__" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:5 +msgid "C# Bindings Conda Package" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:7 +msgid "The GDAL C# Bindings Conda Package is a community supported project." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:10 +#: ../../source/api/python_bindings.rst:22 +msgid "Installation" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:12 +msgid "GDAL with the C# bindings and example applications can be loaded using" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:19 +#: ../../source/api/csharp/csharp_conda.rst:51 +#: ../../source/api/python_bindings.rst:117 +msgid "Usage" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:21 +msgid "" +"The Conda package for GDAL version 3.5.0 and later uses the CMAKE build " +"scripts and therefore there have been changes in the build process and " +"the artifacts produced." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:23 +msgid ":ref:`csharp_conda_35`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:25 +msgid ":ref:`csharp_conda_34`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:32 +msgid "GDAL 3.5.0 and later" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:34 +msgid "" +"The Conda package for GDAL version 3.5.0 and later is built using the new" +" Cmake build scripts." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:37 +msgid ".NET Target Framework" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:39 +msgid "" +"On all architectures (i.e. Windows, Linux and Mac), the bindings are " +"compiled using .NET6.0 as the current (at the time of writing) LTS " +"version." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:42 +msgid "Package Artifacts" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:44 +msgid "The Conda package contains two sets of artifacts:" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:46 +msgid "" +"The SWIG wrapper Dynamic Shared Objects (DSO) - :file:`gdal_wrap.dll` or " +":file:`libgdal_wrap.so` or :file:`libgdal_wrap.dylib` etc. These are " +"loaded as one would expect for a Conda package (i.e. in the :file:`bin` " +"folder in Windows and the :file:`lib` folder in Unix) and thus will " +"automatically link to the correct version of the GDAL DSO and the " +"dependencies, and" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:48 +msgid "" +"Local NuGet packages for the actual C# bindings (i.e. " +":file:`gdal_csharp.dll`, :file:`gdalconst_csharp.dll`, " +":file:`osr_csharp.dll` and :file:`ogr_csharp.dll`). These are created as " +"packages called :file:`OSGeo.GDAL`, :file:`OSGeo.OSR` and " +":file:`OSGeo.OGR`. These are loaded into the :file:`share/gdal` folder." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:53 +msgid "" +"To use the bindings in your application, you will need to basically do " +"the following:" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:55 +msgid "Add the relevant Packages to you application as local packages, and" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:56 +msgid "Add the DSOs to the search path for the application." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:58 +msgid "" +"The former is not complicated and can be done by defining a local source," +" either global (as `is explained here `__ ) or in the build command as is" +" shown below." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:60 +msgid "" +"The latter can be based on Conda for a console application, as is shown " +"below, but if you are working in an IDE (which being a .NET IDE knows " +"nothing about Conda) and/or working on a GUI application (which is not " +"going to be running in a Conda environment) you are going to have to sort" +" out the DSOs your self; probably involving copying the relevant DSOs " +"into the application package." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:63 +msgid "Usage Example - Windows" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:65 +msgid "The most simple example would be:" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:67 +#: ../../source/api/csharp/csharp_conda.rst:104 +msgid "Create a new application (in a dedicated empty folder)" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:69 +#: ../../source/api/csharp/csharp_conda.rst:106 +msgid ":program:`dotnet new console`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:71 +#: ../../source/api/csharp/csharp_conda.rst:108 +msgid "" +"Create a small application (by replacing the contents of " +":file:`Program.cs`)." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:91 +#: ../../source/api/csharp/csharp_conda.rst:128 +msgid "Add the GDAL package" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:93 +msgid "" +":program:`dotnet add package OSGeo.GDAL -s " +"%CONDA_PREFIX%\\\\Library\\\\share\\\\gdal`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:95 +#: ../../source/api/csharp/csharp_conda.rst:132 +msgid "Compile or run" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:97 +#: ../../source/api/csharp/csharp_conda.rst:134 +msgid ":program:`dotnet run`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:99 +msgid "" +"Provided you run these commands in a Conda environment (containing the " +"gdal-csharp package) this should just work." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:102 +msgid "Usage Example - Unix" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:130 +msgid ":program:`dotnet add package OSGeo.GDAL -s $CONDA_PREFIX/share/gdal`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:136 +msgid "" +"This will not just work under Unix since, unlike Windows, the Library " +"Search Path is separate from the Process Search path and is not set by " +"Conda." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:138 +msgid "" +"To make this work, you will probably have to change the Library search " +"path, which is ok for development but should not be accepted for " +"production (which means that you will need to copy the DSOs to the " +"application search path)." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:140 +msgid "Under Linux:" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:142 +msgid ":program:`export LD_LIBRARY_PATH=$CONDA_PREFIX/lib`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:144 +msgid "Under OSX:" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:146 +msgid ":program:`export DYLD_LIBRARY_PATH=$CONDA_PREFIX/lib`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:153 +msgid "GDAL 3.4.x and earlier" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:156 +msgid "Windows" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:158 +msgid "" +"You can test if the C# bindings are working in a Conda environment by " +"running :program:`%CONDA_PREFIX%\\\\Library\\\\bin\\\\gcs\\\\gdal_test`." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:160 +msgid "" +"The DLLs are loaded into the :file:`%CONDA_PREFIX%\\\\Library\\\\bin` " +"folder, as is normal for a Conda environment." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:162 +msgid "" +"The C# sample .EXEs are loaded into " +":file:`%CONDA_PREFIX%\\\\Library\\\\bin\\\\gcs`, because otherwise they " +"over write the standard GDAL tools." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:164 +msgid "" +"To run a sample application - eg GDALinfo.exe - add " +":file:`%CONDA_PREFIX%\\\\Library\\\\bin\\\\gcs` to the path and just run " +":program:`gdalinfo`." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:166 +msgid "" +"To link the DLLs into your code, you will need to include the DLLs into " +"the project (which will almost certainly mean copying them to the project" +" directory)." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:168 +msgid "" +"For a console app that is run from within the Conda environment (i.e. run" +" :program:`conda activate`) then they should work once compiled." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:170 +msgid "" +"For GUI apps or other apps that cannot be run from with the Conda " +"environment then you will have to setup the environment to make the GDAL " +"DLLs available to the app." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:174 +msgid "Mac / Linux" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:176 +msgid "" +"You test if the C# bindings are working in a Conda environment by running" +" :program:`mono $CONDA_PREFIX/lib/gdal_test.exe`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:178 +msgid "" +"The shared objects (i.e. :file:`\\*.so` / :file:`\\*.dylib`), the .EXE " +"and .DLL files are all loaded into the :file:`$CONDA_PREFIX/lib` folder " +"(not the :file:`bin` folder as you might expect). This is in line with " +"`the Mono documentation `__." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:181 +msgid "" +"To run one of the sample applications (e.g. :file:`GDALinfo.exe`), run " +":program:`mono $CONDA_PREFIX/lib/GDALinfo.exe`." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:183 +msgid "" +"To build a console app in Mono, you can do this in a conda environment " +"simple using a command similar to this (changing the source name to your " +"own):" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:189 +msgid "" +"If the compiled executable is run in the conda environment, this should " +"work. For something more portable or a GUI app, then you have to work out" +" the dependencies your self." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:191 +msgid "" +"The DLLs can also be used in a .NET project, for instance built in VS. " +"Just link the DLLs in as dependencies." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:194 +msgid "Differences in the Conda build" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:196 +msgid "" +"The Conda build is in some ways different from the \"standard\" GDAL " +"3.4.x build:" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:198 +msgid "" +"On Mac and Linux, the SWIG files are built as :file:`\\*_wrap` in line " +"with the windows versions. This means that there are no :file:`.config` " +"files. Most importantly, this means that the DLLs can be used in .NET and" +" Unity projects as well as Mono." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:199 +msgid "On Windows, the sample apps are built in .NET5 and not .NET CORE 2.1." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:201 +msgid "These changes anticipated the standard build for GDAL 3.5.x." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:5 +msgid "C# Raster Interface" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:7 +msgid "" +"The GDAL C# interface supports transferring raster data between the C# " +"application and GDAL." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:9 +msgid "" +"The various :file:`Band.ReadRaster`, :file:`Band.WriteRaster`, " +":file:`Dataset.ReadRaster`, :file:`Dataset.WriteRaster` overloads are " +"involved in transferring raster data between the managed and the " +"unmanaged parts of the application." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:12 +msgid "" +"This page will summarize the main aspects of raster data handling related" +" exclusively to the C# interface." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:14 +msgid "" +"The :file:`Band` class contains the following " +":file:`ReadRaster`/:file:`WriteRaster` overloads:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:54 +msgid "" +"The only difference between these functions is the actual type of the " +"buffer parameter. The last 2 overloads are the generic overloads and the " +"caller should write the proper marshaling code for the buffer holding the" +" raster data. The overloads that have a C# array as the buffer parameter " +"implement the proper marshaling code for the caller." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:60 +msgid "Reading the raster image" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:62 +msgid "" +"When reading raster data from GDAL, the user will probably create a .NET " +"image to hold C# representation of the data. The raster data can be read " +"directly or in a buffered fashion." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:66 +msgid "Using the buffered read approach" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:68 +msgid "" +"When reading the image this way the C# API will copy the image data " +"between the C and the C# arrays:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:88 +msgid "" +"In this case the interface implementation uses an internally created " +"unmanaged array to transfer the data between the C and C++ part of the " +"code, like:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:106 +msgid "Using the direct read approach" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:108 +msgid "" +"Raster data can be read into the C# bitmap directly using the following " +"approach:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:127 +msgid "" +"This approach is more performant than the previous since there's no need " +"to allocate an intermediary array for transferring the data." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:130 +msgid "Using /unsafe code and the fixed statement" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:132 +msgid "" +"In the previous examples the programmer could ignore bothering with " +"implementing the marshaling code for the raster arrays. Both of the " +"examples prevent the garbage collector from relocating the array during " +"the execution of the P/Invoke call. Without using an intermediary array " +"the programmer can also use the following method to read the raster data:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:143 +msgid "" +"When using this approach the application must be compiled using the " +":program:`/unsafe` command line option." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:146 +msgid "Using indexed / grayscale images" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:148 +msgid "" +"The :file:`PaletteInterp` enumeration can be used to distinguish between " +"the various type of the image color interpretations." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:159 +msgid "" +"When reading images with indexed color representations, the programmer " +"might have to do some extra work copying the palette over:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:192 +msgid "" +"When reading grayscale images, the programmer should create a sufficient " +"palette for the .NET image." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:220 +#: ../../source/api/csharp/csharp_vector.rst:212 +msgid "Related C# examples" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:222 +msgid "" +"The following examples demonstrate the usage of the GDAL raster " +"operations mentioned previously:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:224 +msgid ":source_file:`swig/csharp/apps/GDALRead.cs`" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:225 +#: ../../source/api/csharp/csharp_raster.rst:226 +msgid ":source_file:`swig/csharp/apps/GDALReadDirect.cs`" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:228 +msgid "" +"This document was amended from the previous version at " +"`https://trac.osgeo.org/gdal/wiki/GdalOgrCsharpRaster " +"`__" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:5 +msgid "C# Bindings Usage Advice" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:8 +msgid "Adding reference to the GDAL/OGR assemblies" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:10 +#: ../../source/api/csharp/csharp_usage.rst:15 +msgid "TODO" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:13 +msgid "Using the interface classes" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:19 +msgid "Modifying Local Search Path" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:22 +msgid "" +"If you want to add a folder to PATH during run-time, so you don't have to" +" pollute system PATH permanently, you can do it this way, in C#" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:43 +msgid "MSDN documentation:" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:45 +msgid "" +"`http://msdn2.microsoft.com/en-us/library/ms686206.aspx " +"`__" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:46 +msgid "" +"`http://msdn2.microsoft.com/en-" +"us/library/system.environment.setenvironmentvariable.aspx " +"`__" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:48 +msgid "" +"Instead of the P/Invoke call to :program:`SetEnvironmentVariable()`, you " +"can use C# native method :program:`Environment.SetEnvironmentVariable()`." +" Read the doc carefully, because there are two versions of this method. " +"Unlike the Win32 API call accessed through P/Invoke, the method " +":program:`Environment.SetEnvironmentVariable()` has an overload that " +"*may* change environment permanently, across processes." +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:5 +msgid "C# Vector and Spatial Reference Interfaces" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:8 +msgid "Basic Architecture" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:10 +msgid "" +"The vector interface is within the :file:`OSGeo.OGR` namespace and the " +"spatial reference interface is within the :file:`OSGeo.OSR` namespace." +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:12 +msgid "The **main** classes are as follows" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:35 +msgid "Accessing Feature Geometries" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:37 +msgid "" +"The basic process is :file:`DataSource` => :file:`Layer` => " +":file:`Feature` => :file:`Geometry`" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:40 +msgid "Open a DataSource" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:42 +msgid "" +"A :file:`DataSource` wraps a OGR source (e.g a filename) and is created " +"as follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:63 +msgid "Access the Layers" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:65 +msgid "" +"Each :file:`DataSource` will have one or more layers that can be iterated" +" as follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:85 +msgid "Access a Layer's Features" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:87 +msgid "" +"Each :file:`Layer` can have zero or more :file:`Feature` s. These should " +"be accessed as follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:100 +msgid "Access a Features's Geometry" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:107 +msgid ":file:`Geometry` objects are nested - so for instance:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:109 +msgid "" +"a :file:`Geometry` of type :file:`wkbGeometryType.wkbTIN` has multiple " +"daughter :file:`Geometry` objects of type " +":file:`wkbGeometryType.wkbTriangle`," +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:110 +msgid "" +"each :file:`Geometry` object of type :file:`wkbGeometryType.wkbTriangle` " +"has a daughter :file:`Geometry` object of type " +":file:`wkbGeometryType.LinearRing`," +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:111 +msgid "" +"each :file:`Geometry` of type :file:`wkbGeometryType.LinearRing` contains" +" a number of points." +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:113 +msgid "" +"When you get to the most basic type - which usually seems to be " +":file:`wkbGeometryType.wkbPoint`, :file:`wkbGeometryType.wkbLineString` " +"or :file:`wkbGeometryType.wkbLinearRing` or their multi- versions or 25D " +"or ZM versions, you can access the point coordinates as follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:126 +msgid "" +"The size of the :file:`double[]` depends on the number of dimensions of " +"the :file:`Geometry`." +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:129 +msgid "Access a Feature's data fields" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:131 +msgid "" +"Each :file:`Feature` object can have a number of data fields associated. " +"The schema for the data fields is defined in a :file:`FieldDefn` object. " +"The fields can be fetched a follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:162 +msgid "Access a Geometry's CRS" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:164 +msgid "" +"If there is a CRS (aka SRS) defined for the :file:`Geometry` it can be " +"retrieved as follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:170 +msgid "" +"The :file:`SpatialReference` is the main class for representing the CRS /" +" projection. The CRS can be turned into a WKT string, e.g. for display " +"purposes, as follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:178 +msgid "" +"Sometimes the CRS defined on the layer does not cascade down to the " +"Feature - you need to refer bak to the Layer" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:182 +msgid "Reproject a Geometry" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:184 +msgid "" +"If the :file:`Geometry` has a valid :file:`SpatialReference` defined, " +"then the :file:`Geometry` can be transformed to a new CRS using this " +"command:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:192 +msgid "" +"However, often it is better to explicitly define the " +":file:`CoordinateTransform` to be used" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:214 +msgid "" +"The following examples demonstrate the usage of the OGR vector operations" +" mentioned above:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:216 +msgid ":source_file:`swig/csharp/apps/ogrinfo.cs`" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:217 +msgid ":source_file:`swig/csharp/apps/OGRLayerAlg.cs`" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:218 +msgid ":source_file:`swig/csharp/apps/OGRFeatureEdit.cs`" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:219 +msgid ":source_file:`swig/csharp/apps/OSRTransform.cs`" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:220 +msgid ":source_file:`swig/csharp/apps/GetCRSInfo.cs`" +msgstr "" + +#: ../../source/api/csharp/index.rst:5 +msgid "C# bindings" +msgstr "" + +#: ../../source/api/csharp/index.rst:7 +msgid "" +"The GDAL project (primarily Tamas Szekeres) maintains SWIG generated C# " +"bindings for GDAL and OGR." +msgstr "" + +#: ../../source/api/csharp/index.rst:9 +msgid "" +"Generally speaking the classes and methods mostly match those of the GDAL" +" and OGR C++ classes, but there is currently no C# specific documentation" +" beyond this site." +msgstr "" + +#: ../../source/api/csharp/index.rst:11 +msgid "The C# bindings are also usable from other .NET languages, such as VB.Net." +msgstr "" + +#: ../../source/api/csharp/index.rst:13 +msgid "" +"The C# interface has been built upon the same libraries as the other SWIG" +" generated wrappers (like Python, Java). Therefore, the class names, " +"class member names, and the method signatures are driven by the GDAL+SWIG" +" conventions and might not follow the conventional .NET naming " +"guidelines. However, one can easily identify the matching members in the " +"GDAL/OGR API documentation." +msgstr "" + +#: ../../source/api/csharp/index.rst:17 +msgid "" +"The GDAL/OGR C# classes use the .NET P/Invoke mechanism for the " +"communication between the managed and unmanaged code. Every class " +"implements the IDisposable interface to control the finalization of the " +"underlying unmanaged memory referenced by every the wrapper class." +msgstr "" + +#: ../../source/api/csharp/index.rst:21 +msgid "Supported platforms" +msgstr "" + +#: ../../source/api/csharp/index.rst:23 +msgid "Currently the interface is compilable on and supports:" +msgstr "" + +#: ../../source/api/csharp/index.rst:25 +msgid "" +"the various Win32 and Win64 platforms targeting the Microsoft.NET and the" +" MONO frameworks," +msgstr "" + +#: ../../source/api/csharp/index.rst:26 +msgid "GNU Linux/OSX systems using the MONO framework, and" +msgstr "" + +#: ../../source/api/csharp/index.rst:27 +msgid "" +"Unity systems on Windows, OSX and Linux (currently only the MONO " +"framework and not IL2CPP)." +msgstr "" + +#: ../../source/api/csharp/index.rst:30 +msgid "Getting GDAL for C#" +msgstr "" + +#: ../../source/api/csharp/index.rst:32 +msgid "" +"There are a number of ways to get the C# bindings, including but not " +"limited to:" +msgstr "" + +#: ../../source/api/csharp/index.rst:34 +msgid "" +"The `gisinternals `__ site, see below " +"under \"Windows Build SDK\"," +msgstr "" + +#: ../../source/api/csharp/index.rst:35 +msgid "" +"The `Conda package `__, see" +" instructions below" +msgstr "" + +#: ../../source/api/csharp/index.rst:36 +msgid "The gdal.netcore NuGet package, see link below, and" +msgstr "" + +#: ../../source/api/csharp/index.rst:37 +msgid "" +"For Unity, there is a UPM package that installs GDAL, `available from " +"here `__ " +"(available on Windows, Mac and Linux)" +msgstr "" + +#: ../../source/api/csharp/index.rst:39 +msgid "(all of these are community supported)" +msgstr "" + +#: ../../source/api/csharp/index.rst:43 +msgid "Related Documents" +msgstr "" + +#: ../../source/api/csharp/index.rst:56 ../../source/api/java/index.rst:69 +msgid "Useful Links" +msgstr "" + +#: ../../source/api/csharp/index.rst:58 +msgid "" +"A variety of example programs in CSharp are available at the " +"`/swig/csharp/apps " +"`__ folder of" +" the GDAL project tree." +msgstr "" + +#: ../../source/api/csharp/index.rst:60 +msgid "The Conda Feedstock" +msgstr "" + +#: ../../source/api/csharp/index.rst:62 +msgid "" +"A simple (as is) build engine of GDAL 3.2 library for .NET Core. `MaxRev-" +"Dev/gdal.netcore `__" +msgstr "" + +#: ../../source/api/csharp/index.rst:64 +msgid "" +"The `ViRGiS project `__ makes extensive use of " +"GDAL in c# in a Unity environment." +msgstr "" + +#: ../../source/api/csharp/index.rst:66 +msgid "(Please add your project to this section)" +msgstr "" + +#: ../../source/api/csharp/index.rst:70 +msgid "Windows Build SDKs" +msgstr "" + +#: ../../source/api/csharp/index.rst:72 +msgid "" +"Tamas Szekeres maintains `build SDK packages " +"`__ in order to compile GDAL from the " +"sources on Windows. The build system provides daily build binary packages" +" for the latest stable and development versions." +msgstr "" + +#: ../../source/api/gdal_alg.rst:10 +msgid "gdal_alg.h: GDAL Algorithms C API" +msgstr "" + +#: ../../source/api/gdal_alg.rst:13 +msgid "gdal_alg.h" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param pTransformerArg" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param bDstToSrc" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param nPointCount" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param x" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param y" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param z" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param panSuccess" +msgstr "" + +#: ../../source/api/gdal_utils.rst:10 +msgid "gdal_utils.h: GDAL Algorithms C API" +msgstr "" + +#: ../../source/api/gdalabstractmdarray_cpp.rst:10 +msgid "GDALAbstractMDArray C++ API" +msgstr "" + +#: ../../source/api/gdalabstractmdarray_cpp.rst +msgid "Param array" +msgstr "" + +#: ../../source/api/gdalabstractmdarray_cpp.rst +msgid "Param chunkArrayStartIdx" +msgstr "" + +#: ../../source/api/gdalabstractmdarray_cpp.rst +msgid "Param chunkCount" +msgstr "" + +#: ../../source/api/gdalabstractmdarray_cpp.rst +msgid "Param iCurChunk" +msgstr "" + +#: ../../source/api/gdalabstractmdarray_cpp.rst +msgid "Param nChunkCount" +msgstr "" + +#: ../../source/api/gdalattribute_cpp.rst:10 +msgid "GDALAttribute C++ API" +msgstr "" + +#: ../../source/api/gdalattribute_cpp.rst:13 +msgid "GDALAttribute class" +msgstr "" + +#: ../../source/api/gdalattribute_cpp.rst:20 +msgid "GDALIHasAttribute interface" +msgstr "" + +#: ../../source/api/gdaldataset_cpp.rst:10 +msgid "GDALDataset C++ API" +msgstr "" + +#: ../../source/api/gdaldimension_cpp.rst:10 +msgid "GDALDimension C++ API" +msgstr "" + +#: ../../source/api/gdaldriver_cpp.rst:10 +msgid "GDALDriver C++ API" +msgstr "" + +#: ../../source/api/gdaldriver_cpp.rst:13 +msgid "GDALDriver class" +msgstr "" + +#: ../../source/api/gdaldriver_cpp.rst:20 +msgid "GDALDriverManager class" +msgstr "" + +#: ../../source/api/gdalextendeddatatype_cpp.rst:10 +msgid "GDALExtendedDataType C++ API" +msgstr "" + +#: ../../source/api/gdalextendeddatatype_cpp.rst:13 +msgid "GDALExtendedDataType class" +msgstr "" + +#: ../../source/api/gdalextendeddatatype_cpp.rst:20 +msgid "GDALEDTComponent class" +msgstr "" + +#: ../../source/api/gdalgroup_cpp.rst:10 +msgid "GDALGroup C++ API" +msgstr "" + +#: ../../source/api/gdalmdarray_cpp.rst:10 +msgid "GDALMDArray C++ API" +msgstr "" + +#: ../../source/api/gdalrasterband_cpp.rst:10 +msgid "GDALRasterBand C++ API" +msgstr "" + +#: ../../source/api/gdalrasterband_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/gnm_cpp.rst +msgid "Protected Functions" +msgstr "" + +#: ../../source/api/gdalwarp_cpp.rst:10 +msgid "Warper C++ API" +msgstr "" + +#: ../../source/api/gdalwarp_cpp.rst +msgid "Friends" +msgstr "" + +#: ../../source/api/gnm_cpp.rst:10 +msgid "Geographic Network C++ API" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Go" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Julia" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Lua" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Original Node.js bindings" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Node.js fork with full Promise-based async and TypeScript support" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Perl" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "PHP" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "R" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Ruby" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Rust" +msgstr "" + +#: ../../source/api/index.rst:136 +msgid "Fiona" +msgstr "" + +#: ../../source/api/index.rst:136 +msgid "Rasterio" +msgstr "" + +#: ../../source/api/index.rst:144 +msgid "Godal" +msgstr "" + +#: ../../source/api/index.rst:5 ../../source/api/python_bindings.rst:133 +msgid "API" +msgstr "" + +#: ../../source/api/index.rst:10 +msgid "`Full Doxygen output <../doxygen/index.html>`_" +msgstr "" + +#: ../../source/api/index.rst:13 +msgid "C API" +msgstr "" + +#: ../../source/api/index.rst:26 +msgid "C++ API" +msgstr "" + +#: ../../source/api/index.rst:29 +msgid "Raster API" +msgstr "" + +#: ../../source/api/index.rst:40 +msgid "Vector API" +msgstr "" + +#: ../../source/api/index.rst:51 +msgid "Spatial reference system API" +msgstr "" + +#: ../../source/api/index.rst:59 +msgid "Multi-dimensional array API" +msgstr "" + +#: ../../source/api/index.rst:72 +msgid "Miscellaneous C++ API" +msgstr "" + +#: ../../source/api/index.rst:81 +msgid "Python API" +msgstr "" + +#: ../../source/api/index.rst:99 +msgid "`Java API <../java/index.html>`_" +msgstr "" + +#: ../../source/api/index.rst:103 +msgid "GDAL/OGR In Other Languages" +msgstr "" + +#: ../../source/api/index.rst:105 +msgid "" +"There is a set of generic `SWIG `__ interface files" +" in the GDAL source tree (subdirectory swig) and a set of language " +"bindings based on those. Currently active ones are:" +msgstr "" + +#: ../../source/api/index.rst:113 +msgid "" +"There are also other bindings that are developed outside of the GDAL " +"source tree (**note**: those offer APIs not strictly coupled to the " +"GDAL/OGR C/C++ API). These include bindings for" +msgstr "" + +#: ../../source/api/index.rst:130 +msgid "" +"For Perl, since GDAL 3.5 the link `Perl " +"`__ is deprecated, use " +"above link instead." +msgstr "" + +#: ../../source/api/index.rst:134 +msgid "There are also more Pythonic ways of using the vector/OGR functions with" +msgstr "" + +#: ../../source/api/index.rst:142 +msgid "There is a more idiomatic Golang way of using the raster functions with" +msgstr "" + +#: ../../source/api/index.rst:151 +msgid "" +"API is omitted in this PDF document. You can consult it on " +"https://gdal.org/api/index.html" +msgstr "" + +#: ../../source/api/java/index.rst:5 +msgid "Java bindings" +msgstr "" + +#: ../../source/api/java/index.rst:7 +msgid "The GDAL project has SWIG generated Java bindings for GDAL and OGR." +msgstr "" + +#: ../../source/api/java/index.rst:9 +msgid "" +"Generally speaking the classes and methods mostly match those of the GDAL" +" and OGR C++ classes. You can find the `​Javadoc " +"`__ of the API of the Java bindings." +msgstr "" + +#: ../../source/api/java/index.rst:11 +msgid "" +"Due to the fact the Java garbage collector works in a separate thread " +"from the main thread, it is necessary to configure GDAL with multi-" +"threading support, even if you do not use GDAL API from several Java " +"threads." +msgstr "" + +#: ../../source/api/java/index.rst:14 +msgid "How to build bindings" +msgstr "" + +#: ../../source/api/java/index.rst:16 +msgid "" +"Please consult the CMake :ref:`building_from_source_java` paragraph for " +"CMake options controlling how to enable the Java bindings and where to " +"install its artifacts" +msgstr "" + +#: ../../source/api/java/index.rst:21 +msgid "How to use the bindings" +msgstr "" + +#: ../../source/api/java/index.rst:23 +msgid "" +"The result of the build of the Java bindings will be both a " +":file:`gdal.jar` and a companion :file:`libgdalalljni.so` / " +":file:`libgdalalljni.dylib` / :file:`gdalalljni.dll` native library. To " +"limit potential compatibility problems, you should ensure that gdal.jar " +"and gdalalljni come from the same GDAL sources." +msgstr "" + +#: ../../source/api/java/index.rst:28 +msgid "" +"The native gdalalljni library, as well as the core libgdal library (and " +"its dependencies) should be accessible through the mechanism of the " +"operating system to locate shared libraries. Typically on Linux, this " +"means that the path to those libraries should be set in the " +"``LD_LIBRARY_PATH`` environment variable (or in :file:`/etc/ld.so.conf`)." +" On MacOSX, it should be in the ``DYLD_LIBRARY_PATH`` environment " +"variable. And on Windows, in the ``PATH`` environment variable." +msgstr "" + +#: ../../source/api/java/index.rst:36 +msgid "" +"For example, to test on Linux that the bindings are working, you can " +"lanch, from the build directory:" +msgstr "" + +#: ../../source/api/java/index.rst:44 +msgid "On Windows:" +msgstr "" + +#: ../../source/api/java/index.rst:53 +msgid "Maven Users" +msgstr "" + +#: ../../source/api/java/index.rst:55 +msgid "" +"The Java bindings are available from the ​`Maven Central " +"`__ repository. All that is needed is to " +"declare a dependency." +msgstr "" + +#: ../../source/api/java/index.rst:71 +msgid "​`Javadoc `__ of the API of the Java bindings." +msgstr "" + +#: ../../source/api/java/index.rst:72 +msgid "" +"`gdalinfo.java " +"`__" +" Sample Java program similar to gdalinfo utility." +msgstr "" + +#: ../../source/api/java/index.rst:73 +msgid "" +"`All Java sample programs " +"`__" +msgstr "" + +#: ../../source/api/java/index.rst:74 +msgid "" +"`Tamas Szekeres' Windows daily builds " +"`__ : Tamas Szekeres maintains a " +"complete set of Win32 and Win64 binary packages that include the GDAL " +"Java bindings. These packages are based on the current development and " +"stable branches built from the GDAL source repository." +msgstr "" + +#: ../../source/api/java/index.rst:75 +msgid "" +"`Image I/O-Ext `__ : The main core " +"module of the project is gdalframework, a framework leveraging on GDAL " +"via SWIG's generated JAVA bindings to provide support for a reach set of " +"data formats. (**Note**: this framework doesn't necessarily ship the " +"latest released GDAL version)" +msgstr "" + +#: ../../source/api/ogr_srs_api.rst:10 +msgid "ogr_srs_api.h: Spatial Reference System C API" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:10 +msgid "OGRFeature C++ API" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:13 +msgid "OGRFeature class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:20 +msgid "OGRFeatureDefn class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:27 +msgid "OGRFieldDefn class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:34 +msgid "OGRGeomFieldDefn class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:41 +msgid "OGRFieldDomain class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:48 +msgid "OGRCodedFieldDomain class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:55 +msgid "OGRRangeFieldDomain class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:62 +msgid "OGRGlobFieldDomain class" +msgstr "" + +#: ../../source/api/ogrfeaturestyle_cpp.rst:10 +msgid "OGRFeature Style C++ API" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:10 +msgid "OGRGeometry C++ API" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:12 +msgid "Include file: ogr_geometry.h" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:15 +msgid "OGRGeometryFactory class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:22 +msgid "OGRGeometry class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:29 +msgid "OGRPoint class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:36 +msgid "OGRLineString class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:43 +msgid "OGRLinearRing class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:50 +msgid "OGRCircularString class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:57 +msgid "OGRCurve class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:64 +msgid "OGRSurface class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:71 +msgid "OGRPolygon class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:78 +msgid "OGRCurvePolygon class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:85 +msgid "OGRMultiPoint class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:92 +msgid "OGRMultiLineString class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:99 +msgid "OGRMultiPolygon class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:106 +msgid "OGRGeometryCollection class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:113 +msgid "OGRMultiCurve class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:120 +msgid "OGRMultiSurface class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:127 +msgid "OGRPolyhedralSurface class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:134 +msgid "OGRTriangle class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:141 +msgid "OGRTriangulatedSurface class" +msgstr "" + +#: ../../source/api/ogrlayer_cpp.rst:10 +msgid "OGRLayer C++ API" +msgstr "" + +#: ../../source/api/ogrlayer_cpp.rst ../../source/api/ogrspatialref.rst +msgid "Public Static Attributes" +msgstr "" + +#: ../../source/api/ogrspatialref.rst:10 +msgid "Spatial Reference System C++ API" +msgstr "" + +#: ../../source/api/python/general.rst:9 +msgid "Python General API" +msgstr "" + +#: ../../source/api/python/general.rst:12 +msgid "Configuration Management" +msgstr "" + +#: ../../source/api/python/general.rst:58 +msgid "Error Handling" +msgstr "" + +#: of osgeo.gdal.ConfigurePythonLogging:1 +msgid "Configure GDAL to use Python's logging framework" +msgstr "" + +#: ../../source/api/python/general.rst:96 +msgid "File Management" +msgstr "" + +#: of osgeo.gdal.DirEntry:1 +msgid "Proxy of C++ DirEntry class." +msgstr "" + +#: of osgeo.gdal.DirEntry.extra:1 +msgid "p.p.char" +msgstr "" + +#: of osgeo.gdal.Band.DataType osgeo.gdal.Band.XSize osgeo.gdal.Band.YSize +#: osgeo.gdal.ColorEntry.c1 osgeo.gdal.ColorEntry.c2 osgeo.gdal.ColorEntry.c3 +#: osgeo.gdal.ColorEntry.c4 osgeo.gdal.Dataset.RasterCount +#: osgeo.gdal.Dataset.RasterXSize osgeo.gdal.Dataset.RasterYSize +#: osgeo.gdal.DirEntry.extra osgeo.gdal.DirEntry.mode +#: osgeo.gdal.DirEntry.modeKnown osgeo.gdal.DirEntry.mtime +#: osgeo.gdal.DirEntry.mtimeKnown osgeo.gdal.DirEntry.name +#: osgeo.gdal.DirEntry.size osgeo.gdal.DirEntry.sizeKnown +#: osgeo.gdal.Driver.HelpTopic osgeo.gdal.Driver.LongName +#: osgeo.gdal.Driver.ShortName osgeo.gdal.GCP.GCPLine osgeo.gdal.GCP.GCPPixel +#: osgeo.gdal.GCP.GCPX osgeo.gdal.GCP.GCPY osgeo.gdal.GCP.GCPZ +#: osgeo.gdal.GCP.Id osgeo.gdal.GCP.Info osgeo.gdal.StatBuf.mode +#: osgeo.gdal.StatBuf.mtime osgeo.gdal.StatBuf.size osgeo.gdal.Statistics.max +#: osgeo.gdal.Statistics.mean osgeo.gdal.Statistics.min +#: osgeo.gdal.Statistics.std_dev osgeo.gdal.Statistics.valid_count +#: osgeo.ogr.DataSource.name osgeo.ogr.Driver.name +#: osgeo.osr.AreaOfUse.east_lon_degree osgeo.osr.AreaOfUse.name +#: osgeo.osr.AreaOfUse.north_lat_degree osgeo.osr.AreaOfUse.south_lat_degree +#: osgeo.osr.AreaOfUse.west_lon_degree osgeo.osr.CRSInfo.area_name +#: osgeo.osr.CRSInfo.auth_name osgeo.osr.CRSInfo.bbox_valid +#: osgeo.osr.CRSInfo.code osgeo.osr.CRSInfo.deprecated +#: osgeo.osr.CRSInfo.east_lon_degree osgeo.osr.CRSInfo.name +#: osgeo.osr.CRSInfo.north_lat_degree osgeo.osr.CRSInfo.projection_method +#: osgeo.osr.CRSInfo.south_lat_degree osgeo.osr.CRSInfo.type +#: osgeo.osr.CRSInfo.type:3 osgeo.osr.CRSInfo.west_lon_degree +msgid "type" +msgstr "" + +#: of osgeo.gdal.DirEntry.extra:3 +msgid "extra" +msgstr "" + +#: of osgeo.gdal.Band.XSize:1 osgeo.gdal.Band.YSize:1 +#: osgeo.gdal.Dataset.RasterCount:1 osgeo.gdal.Dataset.RasterXSize:1 +#: osgeo.gdal.Dataset.RasterYSize:1 osgeo.gdal.DirEntry.mode:1 +#: osgeo.gdal.StatBuf.mode:1 +msgid "int" +msgstr "" + +#: of osgeo.gdal.DirEntry.mode:3 osgeo.gdal.StatBuf.mode:3 +msgid "mode" +msgstr "" + +#: of osgeo.gdal.DirEntry.modeKnown:1 osgeo.gdal.DirEntry.mtimeKnown:1 +#: osgeo.gdal.DirEntry.sizeKnown:1 osgeo.osr.CRSInfo.bbox_valid:1 +#: osgeo.osr.CRSInfo.deprecated:1 +msgid "bool" +msgstr "" + +#: of osgeo.gdal.DirEntry.modeKnown:3 +msgid "modeKnown" +msgstr "" + +#: of osgeo.gdal.DirEntry.mtime:1 osgeo.gdal.DirEntry.size:1 +#: osgeo.gdal.StatBuf.mtime:1 osgeo.gdal.StatBuf.size:1 +#: osgeo.gdal.Statistics.valid_count:1 +msgid "GIntBig" +msgstr "" + +#: of osgeo.gdal.DirEntry.mtime:3 osgeo.gdal.StatBuf.mtime:3 +msgid "mtime" +msgstr "" + +#: of osgeo.gdal.DirEntry.mtimeKnown:3 +msgid "mtimeKnown" +msgstr "" + +#: of osgeo.gdal.DirEntry.name:1 osgeo.gdal.GCP.Id:1 osgeo.gdal.GCP.Info:1 +#: osgeo.osr.AreaOfUse.name:1 osgeo.osr.CRSInfo.area_name:1 +#: osgeo.osr.CRSInfo.auth_name:1 osgeo.osr.CRSInfo.code:1 +#: osgeo.osr.CRSInfo.name:1 osgeo.osr.CRSInfo.projection_method:1 +msgid "p.char" +msgstr "" + +#: of osgeo.gdal.DirEntry.name:3 osgeo.ogr.DataSource.name:3 +#: osgeo.ogr.Driver.name:3 osgeo.osr.AreaOfUse.name:3 osgeo.osr.CRSInfo.name:3 +msgid "name" +msgstr "" + +#: of osgeo.gdal.DirEntry.size:3 osgeo.gdal.StatBuf.size:3 +msgid "size" +msgstr "" + +#: of osgeo.gdal.DirEntry.sizeKnown:3 +msgid "sizeKnown" +msgstr "" + +#: of osgeo.gdal.DirEntry.thisown:1 osgeo.gdal_array.VirtualMem.thisown:1 +#: osgeo.gnm.GenericNetwork.thisown:1 osgeo.gnm.Network.thisown:1 +msgid "The membership flag" +msgstr "" + +#: ../../source/api/python/mdim_api.rst:9 +msgid "Python Multi-dimensional array API" +msgstr "" + +#: of osgeo.gdal.Group:1 +msgid "Proxy of C++ GDALGroupHS class." +msgstr "" + +#: of osgeo.gdal.Dimension:1 +msgid "Proxy of C++ GDALDimensionHS class." +msgstr "" + +#: of osgeo.gdal.MDArray:1 +msgid "Proxy of C++ GDALMDArrayHS class." +msgstr "" + +#: of osgeo.gdal.MDArray.GetShape:1 +msgid "Return the shape of the array" +msgstr "" + +#: of osgeo.gdal.MDArray.ReadAsMaskedArray:1 +msgid "Return a numpy masked array of ReadAsArray() with GetMask()" +msgstr "" + +#: of osgeo.gdal.MDArray.shape:1 +msgid "Returns the shape of the array." +msgstr "" + +#: of osgeo.gdal.Attribute:1 +msgid "Proxy of C++ GDALAttributeHS class." +msgstr "" + +#: of osgeo.gdal.Attribute.Read:1 +msgid "Read an attribute and return it with the most appropriate type" +msgstr "" + +#: of osgeo.gdal.ExtendedDataType:1 +msgid "Proxy of C++ GDALExtendedDataTypeHS class." +msgstr "" + +#: ../../source/api/python/osgeo.rst:4 +msgid "Miscellaneous Python API" +msgstr "" + +#: ../../source/api/python/osgeo.rst:8 +msgid "Submodules" +msgstr "" + +#: ../../source/api/python/osgeo.rst:21 +msgid "Module contents" +msgstr "" + +#: ../../source/api/python/osgeo.gdal.rst:7 +msgid "osgeo.gdal module" +msgstr "" + +#: of osgeo.gdal.AsyncReader:1 osgeo.gdal.EDTComponent:1 +#: osgeo.gdal.GDALTransformerInfoShadow:1 osgeo.gdal.MajorObject:1 +#: osgeo.gdal.StatBuf:1 osgeo.gdal.Statistics:1 osgeo.gdal.VSILFILE:1 +#: osgeo.gdal.VirtualMem:1 osgeo.gdal_array.VirtualMem:1 osgeo.ogr.ArrowArray:1 +#: osgeo.ogr.ArrowArrayStream:1 osgeo.ogr.ArrowSchema:1 +#: osgeo.ogr.GeomTransformer:1 osgeo.ogr.MajorObject:1 +#: osgeo.ogr.PreparedGeometry:1 osgeo.osr.AreaOfUse:1 osgeo.osr.CRSInfo:1 +msgid "Bases: :py:class:`object`" +msgstr "" + +#: of osgeo.gdal.AsyncReader:1 +msgid "Proxy of C++ GDALAsyncReaderShadow class." +msgstr "" + +#: of osgeo.gdal.EDTComponent:1 +msgid "Proxy of C++ GDALEDTComponentHS class." +msgstr "" + +#: of osgeo.gdal.GDALTransformerInfoShadow:1 +msgid "Proxy of C++ GDALTransformerInfoShadow class." +msgstr "" + +#: of osgeo.gdal.MajorObject:1 osgeo.ogr.MajorObject:1 +msgid "Proxy of C++ GDALMajorObjectShadow class." +msgstr "" + +#: of osgeo.gdal.StatBuf:1 +msgid "Proxy of C++ StatBuf class." +msgstr "" + +#: of osgeo.gdal.Statistics:1 +msgid "Proxy of C++ Statistics class." +msgstr "" + +#: of osgeo.gdal.GCP.GCPLine:1 osgeo.gdal.GCP.GCPPixel:1 osgeo.gdal.GCP.GCPX:1 +#: osgeo.gdal.GCP.GCPY:1 osgeo.gdal.GCP.GCPZ:1 osgeo.gdal.Statistics.max:1 +#: osgeo.gdal.Statistics.mean:1 osgeo.gdal.Statistics.min:1 +#: osgeo.gdal.Statistics.std_dev:1 osgeo.osr.AreaOfUse.east_lon_degree:1 +#: osgeo.osr.AreaOfUse.north_lat_degree:1 +#: osgeo.osr.AreaOfUse.south_lat_degree:1 osgeo.osr.AreaOfUse.west_lon_degree:1 +#: osgeo.osr.CRSInfo.east_lon_degree:1 osgeo.osr.CRSInfo.north_lat_degree:1 +#: osgeo.osr.CRSInfo.south_lat_degree:1 osgeo.osr.CRSInfo.west_lon_degree:1 +msgid "double" +msgstr "" + +#: of osgeo.gdal.Statistics.max:3 +msgid "max" +msgstr "" + +#: of osgeo.gdal.Statistics.mean:3 +msgid "mean" +msgstr "" + +#: of osgeo.gdal.Statistics.min:3 +msgid "min" +msgstr "" + +#: of osgeo.gdal.Statistics.std_dev:3 +msgid "std_dev" +msgstr "" + +#: of osgeo.gdal.Statistics.valid_count:3 +msgid "valid_count" +msgstr "" + +#: of osgeo.gdal.VSILFILE:1 +msgid "Proxy of C++ VSILFILE class." +msgstr "" + +#: of osgeo.gdal.VirtualMem:1 osgeo.gdal_array.VirtualMem:1 +msgid "Proxy of C++ CPLVirtualMemShadow class." +msgstr "" + +#: of osgeo.gdal.listdir:1 +msgid "Iterate over a directory." +msgstr "" + +#: of osgeo.gdal.listdir:3 +msgid "recursionLevel = -1 means unlimited level of recursion." +msgstr "" + +#: ../../source/api/python/osgeo.gdal_array.rst:7 +msgid "osgeo.gdal\\_array module" +msgstr "" + +#: of osgeo.gdal_array.BandReadAsArray:1 +msgid "" +"Pure python implementation of reading a chunk of a GDAL file into a numpy" +" array. Used by the gdal.Band.ReadAsArray method." +msgstr "" + +#: of osgeo.gdal_array.BandWriteArray:1 +msgid "" +"Pure python implementation of writing a chunk of a GDAL file from a numpy" +" array. Used by the gdal.Band.WriteArray method." +msgstr "" + +#: of osgeo.gdal_array.CopyDatasetInfo:1 +msgid "" +"Copy georeferencing information and metadata from one dataset to another." +" src: input dataset dst: output dataset - It can be a ROI - xoff, yoff: " +"dst's offset with respect to src in pixel/line." +msgstr "" + +#: of osgeo.gdal_array.CopyDatasetInfo:6 +msgid "Notes: Destination dataset must have update access. Certain formats" +msgstr "" + +#: of osgeo.gdal_array.CopyDatasetInfo:7 +msgid "do not support creation of geotransforms and/or gcps." +msgstr "" + +#: of osgeo.gdal_array.DatasetReadAsArray:1 +msgid "" +"Pure python implementation of reading a chunk of a GDAL file into a numpy" +" array. Used by the gdal.Dataset.ReadAsArray method." +msgstr "" + +#: of osgeo.gdal_array.DatasetWriteArray:1 +msgid "" +"Pure python implementation of writing a chunk of a GDAL file from a numpy" +" array. Used by the gdal.Dataset.WriteArray method." +msgstr "" + +#: of osgeo.gdal_array.RATReadArray:1 +msgid "" +"Pure Python implementation of reading a chunk of the RAT into a numpy " +"array. Called from RasterAttributeTable.ReadAsArray" +msgstr "" + +#: of osgeo.gdal_array.RATWriteArray:1 +msgid "" +"Pure Python implementation of writing a chunk of the RAT from a numpy " +"array. Type of array is coerced to one of the types (int, double, string)" +" supported. Called from RasterAttributeTable.WriteArray" +msgstr "" + +#: ../../source/api/python/osgeo.gdalconst.rst:7 +msgid "osgeo.gdalconst module" +msgstr "" + +#: ../../source/api/python/osgeo.gnm.rst:7 +msgid "osgeo.gnm module" +msgstr "" + +#: of osgeo.gnm.GenericNetwork:1 +msgid "Bases: :py:class:`~osgeo.gnm.Network`" +msgstr "" + +#: of osgeo.gnm.GenericNetwork:1 +msgid "Proxy of C++ GNMGenericNetworkShadow class." +msgstr "" + +#: of osgeo.gnm.Network:1 osgeo.ogr.DataSource:1 osgeo.ogr.Driver:1 +msgid "Bases: :py:class:`~osgeo.ogr.MajorObject`" +msgstr "" + +#: of osgeo.gnm.Network:1 +msgid "Proxy of C++ GNMNetworkShadow class." +msgstr "" + +#: ../../source/api/python/osgeo.ogr.rst:7 +msgid "osgeo.ogr module" +msgstr "" + +#: of osgeo.ogr.ArrowArray:1 +msgid "Proxy of C++ ArrowArray class." +msgstr "" + +#: of osgeo.ogr.ArrowArrayStream:1 +msgid "Proxy of C++ ArrowArrayStream class." +msgstr "" + +#: of osgeo.ogr.ArrowSchema:1 +msgid "Proxy of C++ ArrowSchema class." +msgstr "" + +#: of osgeo.ogr.DataSource:1 +msgid "Proxy of C++ OGRDataSourceShadow class." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:1 +msgid "" +"OGRLayerH OGR_DS_CopyLayer(OGRDataSourceH hDS, OGRLayerH hSrcLayer, const" +" char \\*pszNewName, char \\*\\*papszOptions)" +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:5 +msgid "Duplicate an existing layer." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:7 +msgid "" +"This function creates a new layer, duplicate the field definitions of the" +" source layer and then duplicate each features of the source layer. The " +"papszOptions argument can be used to control driver specific creation " +"options. These options are normally documented in the format specific " +"documentation. The source layer may come from another dataset." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:14 +msgid "Deprecated Use GDALDatasetCopyLayer() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:16 +msgid "handle to the data source where to create the new layer" +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:17 +msgid "handle to the source layer." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:18 +msgid "the name of the layer to create." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:19 +msgid "a StringList of name=value options. Options are driver specific." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:22 +msgid "a handle to the layer, or NULL if an error occurs." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer osgeo.ogr.DataSource.CreateLayer +#: osgeo.ogr.DataSource.DeleteLayer osgeo.ogr.DataSource.ExecuteSQL +#: osgeo.ogr.DataSource.GetDriver osgeo.ogr.DataSource.GetLayerByName +#: osgeo.ogr.DataSource.GetLayerCount osgeo.ogr.DataSource.GetName +#: osgeo.ogr.DataSource.TestCapability osgeo.ogr.Feature.Clone +#: osgeo.ogr.Feature.Equal osgeo.ogr.Feature.GetDefnRef +#: osgeo.ogr.Feature.GetFID osgeo.ogr.Feature.GetFieldAsBinary +#: osgeo.ogr.Feature.GetFieldAsDateTime osgeo.ogr.Feature.GetFieldAsDouble +#: osgeo.ogr.Feature.GetFieldAsDoubleList osgeo.ogr.Feature.GetFieldAsInteger +#: osgeo.ogr.Feature.GetFieldAsInteger64 +#: osgeo.ogr.Feature.GetFieldAsInteger64List +#: osgeo.ogr.Feature.GetFieldAsIntegerList osgeo.ogr.Feature.GetFieldAsString +#: osgeo.ogr.Feature.GetFieldAsStringList osgeo.ogr.Feature.GetFieldCount +#: osgeo.ogr.Feature.GetFieldDefnRef osgeo.ogr.Feature.GetFieldIndex +#: osgeo.ogr.Feature.GetGeomFieldCount osgeo.ogr.Feature.GetGeomFieldDefnRef +#: osgeo.ogr.Feature.GetGeomFieldIndex osgeo.ogr.Feature.GetGeometryRef +#: osgeo.ogr.Feature.GetNativeData osgeo.ogr.Feature.GetNativeMediaType +#: osgeo.ogr.Feature.GetStyleString osgeo.ogr.Feature.IsFieldNull +#: osgeo.ogr.Feature.IsFieldSet osgeo.ogr.Feature.IsFieldSetAndNotNull +#: osgeo.ogr.Feature.SetFID osgeo.ogr.Feature.SetFrom +#: osgeo.ogr.Feature.SetFromWithMap osgeo.ogr.Feature.SetGeomField +#: osgeo.ogr.Feature.SetGeomFieldDirectly osgeo.ogr.Feature.SetGeometry +#: osgeo.ogr.Feature.SetGeometryDirectly osgeo.ogr.Feature.Validate +#: osgeo.ogr.Feature.geometry osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn +#: osgeo.ogr.FeatureDefn.GetFieldCount osgeo.ogr.FeatureDefn.GetFieldDefn +#: osgeo.ogr.FeatureDefn.GetFieldIndex osgeo.ogr.FeatureDefn.GetGeomFieldCount +#: osgeo.ogr.FeatureDefn.GetGeomFieldDefn +#: osgeo.ogr.FeatureDefn.GetGeomFieldIndex osgeo.ogr.FeatureDefn.GetGeomType +#: osgeo.ogr.FeatureDefn.GetName osgeo.ogr.FeatureDefn.GetReferenceCount +#: osgeo.ogr.FeatureDefn.IsGeometryIgnored osgeo.ogr.FeatureDefn.IsSame +#: osgeo.ogr.FeatureDefn.IsStyleIgnored +#: osgeo.ogr.FieldDefn.GetAlternativeNameRef osgeo.ogr.FieldDefn.GetDefault +#: osgeo.ogr.FieldDefn.GetDomainName osgeo.ogr.FieldDefn.GetJustify +#: osgeo.ogr.FieldDefn.GetNameRef osgeo.ogr.FieldDefn.GetPrecision +#: osgeo.ogr.FieldDefn.GetSubType osgeo.ogr.FieldDefn.GetType +#: osgeo.ogr.FieldDefn.GetWidth osgeo.ogr.FieldDefn.IsDefaultDriverSpecific +#: osgeo.ogr.FieldDefn.IsIgnored osgeo.ogr.FieldDefn.IsNullable +#: osgeo.ogr.FieldDefn.IsUnique osgeo.ogr.FieldDefn.justify +#: osgeo.ogr.FieldDefn.precision osgeo.ogr.FieldDefn.type +#: osgeo.ogr.FieldDefn.width osgeo.ogr.Geometry.Boundary +#: osgeo.ogr.Geometry.Buffer osgeo.ogr.Geometry.Centroid +#: osgeo.ogr.Geometry.Clone osgeo.ogr.Geometry.Contains +#: osgeo.ogr.Geometry.ConvexHull osgeo.ogr.Geometry.CoordinateDimension +#: osgeo.ogr.Geometry.Crosses osgeo.ogr.Geometry.DelaunayTriangulation +#: osgeo.ogr.Geometry.Difference osgeo.ogr.Geometry.Disjoint +#: osgeo.ogr.Geometry.Distance osgeo.ogr.Geometry.Distance3D +#: osgeo.ogr.Geometry.Equals osgeo.ogr.Geometry.ExportToIsoWkb +#: osgeo.ogr.Geometry.ExportToIsoWkt osgeo.ogr.Geometry.ExportToWkb +#: osgeo.ogr.Geometry.ExportToWkt osgeo.ogr.Geometry.GetCoordinateDimension +#: osgeo.ogr.Geometry.GetDimension osgeo.ogr.Geometry.GetGeometryName +#: osgeo.ogr.Geometry.GetGeometryType osgeo.ogr.Geometry.GetSpatialReference +#: osgeo.ogr.Geometry.Intersection osgeo.ogr.Geometry.Intersects +#: osgeo.ogr.Geometry.Is3D osgeo.ogr.Geometry.IsEmpty +#: osgeo.ogr.Geometry.IsMeasured osgeo.ogr.Geometry.IsRing +#: osgeo.ogr.Geometry.IsSimple osgeo.ogr.Geometry.IsValid +#: osgeo.ogr.Geometry.MakeValid osgeo.ogr.Geometry.Normalize +#: osgeo.ogr.Geometry.Overlaps osgeo.ogr.Geometry.PointOnSurface +#: osgeo.ogr.Geometry.Polygonize osgeo.ogr.Geometry.Simplify +#: osgeo.ogr.Geometry.SimplifyPreserveTopology osgeo.ogr.Geometry.SymDifference +#: osgeo.ogr.Geometry.Touches osgeo.ogr.Geometry.Transform +#: osgeo.ogr.Geometry.TransformTo osgeo.ogr.Geometry.Union +#: osgeo.ogr.Geometry.UnionCascaded osgeo.ogr.Geometry.Within +#: osgeo.ogr.Geometry.WkbSize osgeo.ogr.Layer.AlterFieldDefn +#: osgeo.ogr.Layer.Clip osgeo.ogr.Layer.CommitTransaction +#: osgeo.ogr.Layer.CreateFeature osgeo.ogr.Layer.CreateField +#: osgeo.ogr.Layer.CreateGeomField osgeo.ogr.Layer.DeleteFeature +#: osgeo.ogr.Layer.DeleteField osgeo.ogr.Layer.Erase +#: osgeo.ogr.Layer.FindFieldIndex osgeo.ogr.Layer.GetFIDColumn +#: osgeo.ogr.Layer.GetFeature osgeo.ogr.Layer.GetFeatureCount +#: osgeo.ogr.Layer.GetGeomType osgeo.ogr.Layer.GetGeometryColumn +#: osgeo.ogr.Layer.GetGeometryTypes osgeo.ogr.Layer.GetLayerDefn +#: osgeo.ogr.Layer.GetName osgeo.ogr.Layer.GetNextFeature +#: osgeo.ogr.Layer.GetSpatialFilter osgeo.ogr.Layer.GetSpatialRef +#: osgeo.ogr.Layer.Identity osgeo.ogr.Layer.Intersection +#: osgeo.ogr.Layer.ReorderField osgeo.ogr.Layer.ReorderFields +#: osgeo.ogr.Layer.RollbackTransaction osgeo.ogr.Layer.SetAttributeFilter +#: osgeo.ogr.Layer.SetFeature osgeo.ogr.Layer.SetIgnoredFields +#: osgeo.ogr.Layer.SetNextByIndex osgeo.ogr.Layer.StartTransaction +#: osgeo.ogr.Layer.SymDifference osgeo.ogr.Layer.SyncToDisk +#: osgeo.ogr.Layer.TestCapability osgeo.ogr.Layer.Union osgeo.ogr.Layer.Update +#: osgeo.ogr.Layer.UpsertFeature +msgid "Return type" +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:1 +msgid "" +"OGRLayerH OGR_DS_CreateLayer(OGRDataSourceH hDS, const char \\*pszName, " +"OGRSpatialReferenceH hSpatialRef, OGRwkbGeometryType eType, char " +"\\*\\*papszOptions)" +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:6 +msgid "" +"This function attempts to create a new layer on the data source with the " +"indicated name, coordinate system, geometry type." +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:9 +msgid "" +"The papszOptions argument can be used to control driver specific creation" +" options. These options are normally documented in the format specific " +"documentation." +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:13 +msgid "Deprecated Use GDALDatasetCreateLayer() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:15 +msgid "" +"The dataset handle.pszName: the name for the new layer. This should " +"ideally not match any existing layer on the datasource." +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:17 +msgid "" +"handle to the coordinate system to use for the new layer, or NULL if no " +"coordinate system is available. The driver might only increase the " +"reference counter of the object to take ownership, and not make a full " +"copy, so do not use OSRDestroySpatialReference(), but OSRRelease() " +"instead when you are done with the object." +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:22 +msgid "" +"the geometry type for the layer. Use wkbUnknown if there are no " +"constraints on the types geometry to be written." +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:24 +msgid "" +"a StringList of name=value options. Options are driver specific, and " +"driver information can be found at the following " +"url:http://www.gdal.org/ogr_formats.html" +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:28 +msgid "NULL is returned on failure, or a new OGRLayer handle on success." +msgstr "" + +#: of osgeo.ogr.DataSource.DeleteLayer:1 +msgid "Delete the indicated layer from the datasource." +msgstr "" + +#: of osgeo.ogr.DataSource.DeleteLayer:3 +msgid "For more details: :c:func:`OGR_DS_DeleteLayer`" +msgstr "" + +#: of osgeo.ogr.DataSource.DeleteLayer:5 +msgid "index or name of the layer to delete." +msgstr "" + +#: of osgeo.ogr.DataSource.DeleteLayer:8 +msgid "" +":py:const:`osgeo.ogr.OGRERR_NONE` on success, or " +":py:const:`osgeo.ogr.OGRERR_UNSUPPORTED_OPERATION` if deleting layers is " +"not supported for this datasource." +msgstr "" + +#: of osgeo.ogr.DataSource.Dereference:1 osgeo.ogr.DataSource.Reference:1 +#: osgeo.ogr.Layer.Dereference:1 osgeo.ogr.Layer.Reference:1 +msgid "For backwards compatibility only." +msgstr "" + +#: of osgeo.ogr.DataSource.Destroy:1 osgeo.ogr.DataSource.Release:1 +#: osgeo.ogr.Feature.Destroy:1 osgeo.ogr.FeatureDefn.Destroy:1 +#: osgeo.ogr.FieldDefn.Destroy:1 +msgid "" +"Once called, self has effectively been destroyed. Do not access. For " +"backwards compatibility only" +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:1 +msgid "" +"OGRLayerH OGR_DS_ExecuteSQL(OGRDataSourceH hDS, const char " +"\\*pszStatement, OGRGeometryH hSpatialFilter, const char \\*pszDialect)" +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:5 +msgid "Execute an SQL statement against the data store." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:7 +msgid "" +"The result of an SQL query is either NULL for statements that are in " +"error, or that have no results set, or an OGRLayer handle representing a " +"results set from the query. Note that this OGRLayer is in addition to the" +" layers in the data store and must be destroyed with " +"OGR_DS_ReleaseResultSet() before the data source is closed (destroyed)." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:14 +msgid "" +"For more information on the SQL dialect supported internally by OGR " +"review theOGR SQL document. Some drivers (i.e. Oracle and PostGIS) pass " +"the SQL directly through to the underlying RDBMS." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:18 +msgid "TheSQLITE dialect can also be used." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:20 +msgid "Deprecated Use GDALDatasetExecuteSQL() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:22 +msgid "handle to the data source on which the SQL query is executed." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:23 +msgid "the SQL statement to execute." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:24 +msgid "handle to a geometry which represents a spatial filter. Can be NULL." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:26 +msgid "" +"allows control of the statement dialect. If set to NULL, the OGR SQL " +"engine will be used, except for RDBMS drivers that will use their " +"dedicated SQL engine, unless OGRSQL is explicitly passed as the dialect. " +"The SQLITE dialect can also be used." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:31 +msgid "" +"a handle to a OGRLayer containing the results of the query. Deallocate " +"with OGR_DS_ReleaseResultSet()." +msgstr "" + +#: of osgeo.ogr.DataSource.GetDriver:1 +msgid "OGRSFDriverH OGR_DS_GetDriver(OGRDataSourceH hDS)" +msgstr "" + +#: of osgeo.ogr.DataSource.GetDriver:4 +msgid "Returns the driver that the dataset was opened with." +msgstr "" + +#: of osgeo.ogr.DataSource.GetDriver:6 +msgid "" +"NOTE: Starting with GDAL 2.0, it is NOT safe to cast the returned handle " +"to OGRSFDriver\\*. If a C++ object is needed, the handle should be cast " +"to GDALDriver\\*." +msgstr "" + +#: of osgeo.ogr.DataSource.GetDriver:10 +msgid "Deprecated Use GDALGetDatasetDriver() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.GetDriver:12 +msgid "handle to the datasource" +msgstr "" + +#: of osgeo.ogr.DataSource.GetDriver:14 +msgid "" +"NULL if driver info is not available, or pointer to a driver owned by the" +" OGRSFDriverManager." +msgstr "" + +#: of osgeo.gdal.Dataset.GetLayer:1 osgeo.ogr.DataSource.GetLayer:1 +msgid "Return the layer given an index or a name" +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:1 +msgid "" +"OGRLayerH OGR_DS_GetLayerByName(OGRDataSourceH hDS, const char " +"\\*pszLayerName)" +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:4 +msgid "Fetch a layer by name." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:6 +msgid "" +"The returned layer remains owned by the OGRDataSource and should not be " +"deleted by the application." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:9 +msgid "Deprecated Use GDALDatasetGetLayerByName() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:11 +msgid "handle to the data source from which to get the layer." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:12 +msgid "Layer the layer name of the layer to fetch." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:14 +msgid "" +"a handle to the layer, or NULL if the layer is not found or an error " +"occurs." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerCount:1 +msgid "int OGR_DS_GetLayerCount(OGRDataSourceH hDS)" +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerCount:4 +msgid "Get the number of layers in this data source." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerCount:6 +msgid "Deprecated Use GDALDatasetGetLayerCount() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerCount:8 +msgid "handle to the data source from which to get the number of layers." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerCount:11 +msgid "layer count." +msgstr "" + +#: of osgeo.ogr.DataSource.GetName:1 +msgid "const char\\* OGR_DS_GetName(OGRDataSourceH hDS)" +msgstr "" + +#: of osgeo.ogr.DataSource.GetName:4 +msgid "Returns the name of the data source." +msgstr "" + +#: of osgeo.ogr.DataSource.GetName:6 +msgid "" +"This string should be sufficient to open the data source if passed to the" +" same OGRSFDriver that this data source was opened with, but it need not " +"be exactly the same string that was used to open the data source. " +"Normally this is a filename." +msgstr "" + +#: of osgeo.ogr.DataSource.GetName:11 +msgid "Deprecated Use GDALGetDescription() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.GetName:13 +msgid "handle to the data source to get the name from." +msgstr "" + +#: of osgeo.ogr.DataSource.GetName:15 +msgid "" +"pointer to an internal name string which should not be modified or freed " +"by the caller." +msgstr "" + +#: of osgeo.ogr.DataSource.GetRefCount:1 +msgid "int OGR_DS_GetRefCount(OGRDataSourceH hDataSource)" +msgstr "" + +#: of osgeo.ogr.DataSource.GetStyleTable:1 +msgid "OGRStyleTableH OGR_DS_GetStyleTable(OGRDataSourceH hDS)" +msgstr "" + +#: of osgeo.ogr.DataSource.GetStyleTable:4 osgeo.ogr.Layer.GetStyleTable:1 +msgid "Get style table." +msgstr "" + +#: of osgeo.ogr.DataSource.GetSummaryRefCount:1 +msgid "int OGR_DS_GetSummaryRefCount(OGRDataSourceH hDataSource)" +msgstr "" + +#: of osgeo.ogr.DataSource.ReleaseResultSet:1 +msgid "void OGR_DS_ReleaseResultSet(OGRDataSourceH hDS, OGRLayerH hLayer)" +msgstr "" + +#: of osgeo.ogr.DataSource.ReleaseResultSet:4 +msgid "Release results of OGR_DS_ExecuteSQL()." +msgstr "" + +#: of osgeo.ogr.DataSource.ReleaseResultSet:6 +msgid "" +"This function should only be used to deallocate OGRLayers resulting from " +"an OGR_DS_ExecuteSQL() call on the same OGRDataSource. Failure to " +"deallocate a results set before destroying the OGRDataSource may cause " +"errors." +msgstr "" + +#: of osgeo.ogr.DataSource.ReleaseResultSet:11 +msgid "Deprecated Use GDALDatasetReleaseResultSet() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.ReleaseResultSet:13 +msgid "a handle to the data source on which was executed an SQL query." +msgstr "" + +#: of osgeo.ogr.DataSource.ReleaseResultSet:14 +msgid "handle to the result of a previous OGR_DS_ExecuteSQL() call." +msgstr "" + +#: of osgeo.ogr.DataSource.SetStyleTable:1 +msgid "void OGR_DS_SetStyleTable(OGRDataSourceH hDS, OGRStyleTableH hStyleTable)" +msgstr "" + +#: of osgeo.ogr.DataSource.SetStyleTable:4 osgeo.ogr.Layer.SetStyleTable:1 +msgid "Set style table." +msgstr "" + +#: of osgeo.ogr.DataSource.SyncToDisk:1 +msgid "OGRErr OGR_DS_SyncToDisk(OGRDataSourceH hDS)" +msgstr "" + +#: of osgeo.ogr.DataSource.SyncToDisk:4 osgeo.ogr.Layer.SyncToDisk:1 +msgid "Flush pending changes to disk." +msgstr "" + +#: of osgeo.ogr.DataSource.SyncToDisk:6 +msgid "See GDALDataset::FlushCache()" +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:1 +msgid "int OGR_DS_TestCapability(OGRDataSourceH hDS, const char \\*pszCapability)" +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:4 +msgid "Test if capability is available." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:6 +msgid "" +"One of the following data source capability names can be passed into this" +" function, and a TRUE or FALSE value will be returned indicating whether " +"or not the capability is available for this object." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:10 +msgid "ODsCCreateLayer: True if this datasource can create new layers." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:12 +msgid "ODsCDeleteLayer: True if this datasource can delete existing layers." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:14 +msgid "" +"ODsCCreateGeomFieldAfterCreateLayer: True if the layers of this " +"datasource support CreateGeomField() just after layer creation." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:17 +msgid "" +"ODsCCurveGeometries: True if this datasource supports writing curve " +"geometries. (GDAL 2.0). In that case, OLCCurveGeometries must also be " +"declared in layers of that dataset." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:21 +msgid "" +"The #define macro forms of the capability names should be used in " +"preference to the strings themselves to avoid misspelling." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:24 +msgid "Deprecated Use GDALDatasetTestCapability() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:26 +msgid "handle to the data source against which to test the capability." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:27 +msgid "the capability to test." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:29 +msgid "TRUE if capability available otherwise FALSE." +msgstr "" + +#: of osgeo.gdal.Driver.HelpTopic:1 osgeo.gdal.Driver.LongName:1 +#: osgeo.gdal.Driver.ShortName:1 osgeo.ogr.DataSource.name:1 +#: osgeo.ogr.Driver.name:1 +msgid "p.q(const).char" +msgstr "" + +#: of osgeo.ogr.Driver:1 +msgid "Proxy of C++ OGRDriverShadow class." +msgstr "" + +#: of osgeo.ogr.GeomTransformer:1 +msgid "Proxy of C++ OGRGeomTransformerShadow class." +msgstr "" + +#: of osgeo.ogr.PreparedGeometry:1 +msgid "Proxy of C++ OGRPreparedGeometryShadow class." +msgstr "" + +#: ../../source/api/python/osgeo.osr.rst:7 +msgid "osgeo.osr module" +msgstr "" + +#: of osgeo.osr.AreaOfUse:1 +msgid "Proxy of C++ OSRAreaOfUse class." +msgstr "" + +#: of osgeo.osr.AreaOfUse.east_lon_degree:3 osgeo.osr.CRSInfo.east_lon_degree:3 +msgid "east_lon_degree" +msgstr "" + +#: of osgeo.osr.AreaOfUse.north_lat_degree:3 +#: osgeo.osr.CRSInfo.north_lat_degree:3 +msgid "north_lat_degree" +msgstr "" + +#: of osgeo.osr.AreaOfUse.south_lat_degree:3 +#: osgeo.osr.CRSInfo.south_lat_degree:3 +msgid "south_lat_degree" +msgstr "" + +#: of osgeo.osr.AreaOfUse.west_lon_degree:3 osgeo.osr.CRSInfo.west_lon_degree:3 +msgid "west_lon_degree" +msgstr "" + +#: of osgeo.osr.CRSInfo:1 +msgid "Proxy of C++ OSRCRSInfo class." +msgstr "" + +#: of osgeo.osr.CRSInfo.area_name:3 +msgid "area_name" +msgstr "" + +#: of osgeo.osr.CRSInfo.auth_name:3 +msgid "auth_name" +msgstr "" + +#: of osgeo.osr.CRSInfo.bbox_valid:3 +msgid "bbox_valid" +msgstr "" + +#: of osgeo.osr.CRSInfo.code:3 +msgid "code" +msgstr "" + +#: of osgeo.osr.CRSInfo.deprecated:3 +msgid "deprecated" +msgstr "" + +#: of osgeo.osr.CRSInfo.projection_method:3 +msgid "projection_method" +msgstr "" + +#: of osgeo.osr.CRSInfo.type:1 +msgid "OSRCRSType" +msgstr "" + +#: ../../source/api/python/raster_api.rst:9 +msgid "Python Raster API" +msgstr "" + +#: ../../source/api/python/raster_api.rst:11 +msgid "" +"This page contains classes, methods, functions that relate to the GDAL " +":ref:`raster_data_model`:" +msgstr "" + +#: ../../source/api/python/raster_api.rst:13 +msgid "`Driver`_" +msgstr "" + +#: ../../source/api/python/raster_api.rst:14 +msgid "`Dataset`_" +msgstr "" + +#: ../../source/api/python/raster_api.rst:15 +msgid "`Band`_" +msgstr "" + +#: ../../source/api/python/raster_api.rst:16 +msgid "`Other`_" +msgstr "" + +#: ../../source/api/python/raster_api.rst:21 +msgid "Driver" +msgstr "" + +#: of osgeo.gdal.Driver:1 +msgid "Proxy of C++ GDALDriverShadow class." +msgstr "" + +#: of osgeo.gdal.Driver.HelpTopic:3 +msgid "HelpTopic" +msgstr "" + +#: of osgeo.gdal.Driver.LongName:3 +msgid "LongName" +msgstr "" + +#: of osgeo.gdal.Driver.ShortName:3 +msgid "ShortName" +msgstr "" + +#: ../../source/api/python/raster_api.rst:41 +msgid "Dataset" +msgstr "" + +#: of osgeo.gdal.Dataset:1 +msgid "Proxy of C++ GDALDatasetShadow class." +msgstr "" + +#: of osgeo.gdal.Dataset.DeleteLayer:1 +msgid "Deletes the layer given an index or layer name" +msgstr "" + +#: of osgeo.gdal.Dataset.GetTiledVirtualMemArray:1 +msgid "" +"Return a NumPy array for the dataset, seen as a virtual memory mapping " +"with a tile organization. If there are several bands and " +"tile_organization = gdal.GTO_TIP, an element is accessed with " +"array[tiley][tilex][y][x][band]. If there are several bands and " +"tile_organization = gdal.GTO_BIT, an element is accessed with " +"array[tiley][tilex][band][y][x]. If there are several bands and " +"tile_organization = gdal.GTO_BSQ, an element is accessed with " +"array[band][tiley][tilex][y][x]. If there is only one band, an element is" +" accessed with array[tiley][tilex][y][x]. Any reference to the array must" +" be dropped before the last reference to the related dataset is also " +"dropped." +msgstr "" + +#: of osgeo.gdal.Dataset.GetVirtualMemArray:1 +msgid "" +"Return a NumPy array for the dataset, seen as a virtual memory mapping. " +"If there are several bands and band_sequential = True, an element is " +"accessed with array[band][y][x]. If there are several bands and " +"band_sequential = False, an element is accessed with array[y][x][band]. " +"If there is only one band, an element is accessed with array[y][x]. Any " +"reference to the array must be dropped before the last reference to the " +"related dataset is also dropped." +msgstr "" + +#: of osgeo.gdal.Dataset.RasterCount:3 +msgid "RasterCount" +msgstr "" + +#: of osgeo.gdal.Dataset.RasterXSize:3 +msgid "RasterXSize" +msgstr "" + +#: of osgeo.gdal.Dataset.RasterYSize:3 +msgid "RasterYSize" +msgstr "" + +#: of osgeo.gdal.Band.ReadAsArray:1 osgeo.gdal.Dataset.ReadAsArray:1 +msgid "" +"Reading a chunk of a GDAL band into a numpy array. The optional " +"(buf_xsize,buf_ysize,buf_type) parameters should generally not be " +"specified if buf_obj is specified. The array is returned" +msgstr "" + +#: ../../source/api/python/raster_api.rst:55 +msgid "Band" +msgstr "" + +#: of osgeo.gdal.Band:1 +msgid "Proxy of C++ GDALRasterBandShadow class." +msgstr "" + +#: of osgeo.gdal.Band.DataType:1 +msgid "GDALDataType" +msgstr "" + +#: of osgeo.gdal.Band.DataType:3 +msgid "DataType" +msgstr "" + +#: of osgeo.gdal.Band.GetTiledVirtualMemArray:1 +msgid "" +"Return a NumPy array for the band, seen as a virtual memory mapping with " +"a tile organization. An element is accessed with " +"array[tiley][tilex][y][x]. Any reference to the array must be dropped " +"before the last reference to the related dataset is also dropped." +msgstr "" + +#: of osgeo.gdal.Band.GetVirtualMemArray:1 +#: osgeo.gdal.Band.GetVirtualMemAutoArray:1 +msgid "" +"Return a NumPy array for the band, seen as a virtual memory mapping. An " +"element is accessed with array[y][x]. Any reference to the array must be " +"dropped before the last reference to the related dataset is also dropped." +msgstr "" + +#: of osgeo.gdal.Band.XSize:3 +msgid "XSize" +msgstr "" + +#: of osgeo.gdal.Band.YSize:3 +msgid "YSize" +msgstr "" + +#: ../../source/api/python/raster_api.rst:67 +msgid "Other" +msgstr "" + +#: of osgeo.gdal.RasterAttributeTable:1 +msgid "Proxy of C++ GDALRasterAttributeTableShadow class." +msgstr "" + +#: of osgeo.gdal.ColorTable:1 +msgid "Proxy of C++ GDALColorTableShadow class." +msgstr "" + +#: of osgeo.gdal.ColorEntry:1 +msgid "Proxy of C++ GDALColorEntry class." +msgstr "" + +#: of osgeo.gdal.ColorEntry.c1:1 osgeo.gdal.ColorEntry.c2:1 +#: osgeo.gdal.ColorEntry.c3:1 osgeo.gdal.ColorEntry.c4:1 +msgid "short" +msgstr "" + +#: of osgeo.gdal.ColorEntry.c1:3 +msgid "c1" +msgstr "" + +#: of osgeo.gdal.ColorEntry.c2:3 +msgid "c2" +msgstr "" + +#: of osgeo.gdal.ColorEntry.c3:3 +msgid "c3" +msgstr "" + +#: of osgeo.gdal.ColorEntry.c4:3 +msgid "c4" +msgstr "" + +#: of osgeo.gdal.GCP:1 +msgid "Proxy of C++ GDAL_GCP class." +msgstr "" + +#: of osgeo.gdal.GCP.GCPLine:3 +msgid "GCPLine" +msgstr "" + +#: of osgeo.gdal.GCP.GCPPixel:3 +msgid "GCPPixel" +msgstr "" + +#: of osgeo.gdal.GCP.GCPX:3 +msgid "GCPX" +msgstr "" + +#: of osgeo.gdal.GCP.GCPY:3 +msgid "GCPY" +msgstr "" + +#: of osgeo.gdal.GCP.GCPZ:3 +msgid "GCPZ" +msgstr "" + +#: of osgeo.gdal.GCP.Id:3 +msgid "Id" +msgstr "" + +#: of osgeo.gdal.GCP.Info:3 +msgid "Info" +msgstr "" + +#: ../../source/api/python/spatial_ref_api.rst:9 +msgid "Python Spatial Reference System API" +msgstr "" + +#: ../../source/api/python/spatial_ref_api.rst:11 +msgid "" +"This page contains classes, methods and functions that relate to spatial " +"reference systems:" +msgstr "" + +#: ../../source/api/python/spatial_ref_api.rst:13 +msgid "`SpatialReference`_" +msgstr "" + +#: ../../source/api/python/spatial_ref_api.rst:14 +msgid "`CoordinateTransformation`_" +msgstr "" + +#: ../../source/api/python/spatial_ref_api.rst:17 +msgid "SpatialReference" +msgstr "" + +#: of osgeo.osr.SpatialReference:1 +msgid "Proxy of C++ OSRSpatialReferenceShadow class." +msgstr "" + +#: ../../source/api/python/spatial_ref_api.rst:25 +msgid "CoordinateTransformation" +msgstr "" + +#: of osgeo.osr.CoordinateTransformation:1 +msgid "Proxy of C++ OSRCoordinateTransformationShadow class." +msgstr "" + +#: of osgeo.osr.CoordinateTransformationOptions:1 +msgid "Proxy of C++ OGRCoordinateTransformationOptions class." +msgstr "" + +#: ../../source/api/python/utilities.rst:9 +msgid "Python Utilities" +msgstr "" + +#: ../../source/api/python/utilities.rst:12 +msgid "Raster Utilities" +msgstr "" + +#: of osgeo.gdal.BuildVRT:1 +msgid "Build a VRT from a list of datasets." +msgstr "" + +#: of osgeo.gdal.BuildVRT:3 +msgid "Output dataset name." +msgstr "" + +#: of osgeo.gdal.BuildVRT:4 +msgid "" +"An array of Dataset objects or filenames, or a Dataset object or a " +"filename." +msgstr "" + +#: of osgeo.gdal.BuildVRT:5 +msgid "" +"options: return of gdal.BuildVRTOptions(), string or array of strings, " +"other keywords arguments of gdal.BuildVRTOptions(). If options is " +"provided as a gdal.BuildVRTOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:1 +msgid "Create a BuildVRTOptions() object that can be passed to gdal.BuildVRT()" +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:3 osgeo.gdal.DEMProcessingOptions:3 +#: osgeo.gdal.GridOptions:3 osgeo.gdal.MultiDimTranslateOptions:3 +#: osgeo.gdal.NearblackOptions:3 osgeo.gdal.RasterizeOptions:3 +#: osgeo.gdal.TranslateOptions:3 osgeo.gdal.VectorTranslateOptions:3 +#: osgeo.gdal.WarpOptions:3 +msgid "" +"can be be an array of strings, a string or let empty and filled from " +"other keywords." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:5 +msgid "'highest', 'lowest', 'average', 'user'." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:6 +msgid "output bounds as (minX, minY, maxX, maxY) in target SRS." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:8 osgeo.gdal.BuildVRTOptions:9 +msgid "output resolution in target SRS." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:10 +msgid "whether to force output bounds to be multiple of output resolution." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:11 +msgid "" +"whether each source file goes into a separate stacked band in the VRT " +"band." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:12 +msgid "array of band numbers (index start at 1)." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:13 +msgid "" +"whether to add an alpha mask band to the VRT when the source raster have " +"none." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:14 +msgid "resampling mode." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:15 +msgid "assigned output SRS." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:16 +msgid "" +"whether to accept input datasets have not the same projection. Note: they" +" will *not* be reprojected." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:18 +msgid "source nodata value(s)." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:19 +msgid "nodata values at the VRT band level." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:20 +msgid "whether to make the VRT band not report the NoData value." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:21 +msgid "set to True if warnings should be failures" +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:22 +msgid "callback method." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:23 +msgid "user data for callback." +msgstr "" + +#: of osgeo.gdal.DEMProcessing:1 +msgid "Apply a DEM processing." +msgstr "" + +#: of osgeo.gdal.DEMProcessing:3 osgeo.gdal.Grid:3 +#: osgeo.gdal.MultiDimTranslate:3 osgeo.gdal.Translate:3 +msgid "Output dataset name" +msgstr "" + +#: of osgeo.gdal.DEMProcessing:4 osgeo.gdal.Grid:4 osgeo.gdal.Info:3 +#: osgeo.gdal.MultiDimInfo:3 osgeo.gdal.Nearblack:4 osgeo.gdal.Rasterize:4 +#: osgeo.gdal.Translate:4 osgeo.gdal.VectorTranslate:4 +msgid "a Dataset object or a filename" +msgstr "" + +#: of osgeo.gdal.DEMProcessing:5 +msgid "" +"one of \"hillshade\", \"slope\", \"aspect\", \"color-relief\", \"TRI\", " +"\"TPI\", \"Roughness\"" +msgstr "" + +#: of osgeo.gdal.DEMProcessing:6 +msgid "" +"options: return of gdal.DEMProcessingOptions(), string or array of " +"strings, other keywords arguments of gdal.DEMProcessingOptions(). If " +"options is provided as a gdal.DEMProcessingOptions() object, other " +"keywords are ignored." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:1 +msgid "" +"Create a DEMProcessingOptions() object that can be passed to " +"gdal.DEMProcessing()" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:4 +msgid "" +"(mandatory for \"color-relief\") name of file that contains palette " +"definition for the \"color-relief\" processing." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:5 osgeo.gdal.GridOptions:4 +#: osgeo.gdal.MultiDimTranslateOptions:4 osgeo.gdal.NearblackOptions:4 +#: osgeo.gdal.RasterizeOptions:4 osgeo.gdal.TranslateOptions:4 +#: osgeo.gdal.WarpOptions:4 +msgid "output format (\"GTiff\", etc...)" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:6 osgeo.gdal.GridOptions:8 +#: osgeo.gdal.MultiDimTranslateOptions:5 osgeo.gdal.NearblackOptions:5 +#: osgeo.gdal.RasterizeOptions:6 osgeo.gdal.TranslateOptions:14 +#: osgeo.gdal.WarpOptions:23 +msgid "list of creation options" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:7 +msgid "whether to compute values at raster edges." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:8 +msgid "" +"'Horn' (default) or 'ZevenbergenThorne' for hillshade, slope or aspect. " +"'Wilson' (default) or 'Riley' for TRI" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:9 +msgid "source band number to use" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:10 +msgid "" +"(hillshade only) vertical exaggeration used to pre-multiply the " +"elevations." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:11 +msgid "ratio of vertical units to horizontal." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:12 +msgid "" +"(hillshade only) azimuth of the light, in degrees. 0 if it comes from the" +" top of the raster, 90 from the east, ... The default value, 315, should " +"rarely be changed as it is the value generally used to generate shaded " +"maps." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:13 +msgid "" +"(hillshade only) altitude of the light, in degrees. 90 if the light comes" +" from above the DEM, 0 if it is raking light." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:14 +msgid "" +"(hillshade only) whether to compute combined shading, a combination of " +"slope and oblique shading. Only one of combined, multiDirectional and " +"igor can be specified." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:15 +msgid "" +"(hillshade only) whether to compute multi-directional shading. Only one " +"of combined, multiDirectional and igor can be specified." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:16 +msgid "" +"(hillshade only) whether to use Igor's hillshading from Maperitive. Only" +" one of combined, multiDirectional and igor can be specified." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:17 +msgid "(slope only) \"degree\" or \"percent\"." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:18 +msgid "" +"(aspect only) whether to return trigonometric angle instead of azimuth. " +"Thus 0deg means East, 90deg North, 180deg West, 270deg South." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:19 +msgid "" +"(aspect only) whether to return 0 for flat areas with slope=0, instead of" +" -9999." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:20 +msgid "" +"adds an alpha band to the output file (only for processing = 'color-" +"relief')" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:21 +msgid "" +"(color-relief only) Determines how color entries are selected from an " +"input value. Can be \"nearest_color_entry\", \"exact_color_entry\" or " +"\"linear_interpolation\". Defaults to \"linear_interpolation\"" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:22 osgeo.gdal.GridOptions:26 +#: osgeo.gdal.MultiDimTranslateOptions:14 osgeo.gdal.NearblackOptions:12 +#: osgeo.gdal.RasterizeOptions:41 osgeo.gdal.TranslateOptions:34 +#: osgeo.gdal.VectorTranslateOptions:31 osgeo.gdal.WarpOptions:42 +msgid "callback method" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:23 osgeo.gdal.GridOptions:27 +#: osgeo.gdal.MultiDimTranslateOptions:15 osgeo.gdal.NearblackOptions:13 +#: osgeo.gdal.RasterizeOptions:42 osgeo.gdal.TranslateOptions:35 +#: osgeo.gdal.VectorTranslateOptions:32 osgeo.gdal.WarpOptions:43 +msgid "user data for callback" +msgstr "" + +#: of osgeo.gdal.Grid:1 +msgid "Create raster from the scattered data." +msgstr "" + +#: of osgeo.gdal.Grid:5 +msgid "" +"options: return of gdal.GridOptions(), string or array of strings, other " +"keywords arguments of gdal.GridOptions() If options is provided as a " +"gdal.GridOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.GridOptions:1 +msgid "Create a GridOptions() object that can be passed to gdal.Grid()" +msgstr "" + +#: of osgeo.gdal.GridOptions:5 osgeo.gdal.RasterizeOptions:5 +#: osgeo.gdal.TranslateOptions:5 osgeo.gdal.WarpOptions:17 +msgid "output type (gdalconst.GDT_Byte, etc...)" +msgstr "" + +#: of osgeo.gdal.GridOptions:6 osgeo.gdal.RasterizeOptions:11 +#: osgeo.gdal.TranslateOptions:8 osgeo.gdal.WarpOptions:10 +msgid "width of the output raster in pixel" +msgstr "" + +#: of osgeo.gdal.GridOptions:7 osgeo.gdal.RasterizeOptions:12 +#: osgeo.gdal.TranslateOptions:9 osgeo.gdal.WarpOptions:11 +msgid "height of the output raster in pixel" +msgstr "" + +#: of osgeo.gdal.GridOptions:9 osgeo.gdal.TranslateOptions:22 +msgid "assigned output bounds: [ulx, uly, lrx, lry]" +msgstr "" + +#: of osgeo.gdal.GridOptions:11 osgeo.gdal.RasterizeOptions:9 +#: osgeo.gdal.TranslateOptions:24 +msgid "assigned output SRS" +msgstr "" + +#: of osgeo.gdal.GridOptions:12 osgeo.gdal.RasterizeOptions:16 +msgid "nodata value" +msgstr "" + +#: of osgeo.gdal.GridOptions:13 +msgid "" +"e.g " +"\"invdist:power=2.0:smoothing=0.0:radius1=0.0:radius2=0.0:angle=0.0:max_points=0:min_points=0:nodata=0.0\"" +msgstr "" + +#: of osgeo.gdal.GridOptions:14 osgeo.gdal.VectorTranslateOptions:21 +msgid "list of layers to convert" +msgstr "" + +#: of osgeo.gdal.GridOptions:15 osgeo.gdal.RasterizeOptions:36 +#: osgeo.gdal.VectorTranslateOptions:10 +msgid "SQL statement to apply to the source dataset" +msgstr "" + +#: of osgeo.gdal.GridOptions:16 osgeo.gdal.RasterizeOptions:38 +#: osgeo.gdal.VectorTranslateOptions:12 +msgid "WHERE clause to apply to source layer(s)" +msgstr "" + +#: of osgeo.gdal.GridOptions:17 osgeo.gdal.VectorTranslateOptions:17 +msgid "spatial filter as (minX, minY, maxX, maxY) bounding box" +msgstr "" + +#: of osgeo.gdal.GridOptions:18 +msgid "" +"Identifies an attribute field on the features to be used to get a Z value" +" from. This value overrides Z value read from feature geometry record." +msgstr "" + +#: of osgeo.gdal.GridOptions:20 +msgid "" +"Addition to the attribute field on the features to be used to get a Z " +"value from. The addition should be the same unit as Z value. The result " +"value will be Z value + Z increase value. The default value is 0." +msgstr "" + +#: of osgeo.gdal.GridOptions:23 +msgid "" +"Multiplication ratio for Z field. This can be used for shift from e.g. " +"foot to meters or from elevation to deep. The result value will be (Z " +"value + Z increase value) * Z multiply value. The default value is 1." +msgstr "" + +#: of osgeo.gdal.Info:1 osgeo.gdal.MultiDimInfo:1 +msgid "Return information on a dataset." +msgstr "" + +#: of osgeo.gdal.Info:4 +msgid "" +"options: return of gdal.InfoOptions(), string or array of strings other " +"keywords arguments of gdal.InfoOptions(). If options is provided as a " +"gdal.InfoOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.InfoOptions:1 +msgid "" +"Create a InfoOptions() object that can be passed to gdal.Info() options " +"can be be an array of strings, a string or let empty and filled from " +"other keywords." +msgstr "" + +#: of osgeo.gdal.Nearblack:1 +msgid "Convert nearly black/white borders to exact value." +msgstr "" + +#: of osgeo.gdal.Nearblack:3 osgeo.gdal.Rasterize:3 +#: osgeo.gdal.VectorTranslate:3 osgeo.gdal.Warp:3 +msgid "Output dataset name or object" +msgstr "" + +#: of osgeo.gdal.Nearblack:5 +msgid "" +"options: return of gdal.NearblackOptions(), string or array of strings, " +"other keywords arguments of gdal.NearblackOptions(). If options is " +"provided as a gdal.NearblackOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.NearblackOptions:1 +msgid "Create a NearblackOptions() object that can be passed to gdal.Nearblack()" +msgstr "" + +#: of osgeo.gdal.NearblackOptions:6 +msgid "" +"whether to search for nearly white (255) pixels instead of nearly black " +"pixels." +msgstr "" + +#: of osgeo.gdal.NearblackOptions:7 +msgid "" +"list of colors to search for, e.g. ((0,0,0),(255,255,255)). The pixels " +"that are considered as the collar are set to 0" +msgstr "" + +#: of osgeo.gdal.NearblackOptions:8 +msgid "" +"number of non-black (or other searched colors specified with white / " +"colors) pixels that can be encountered before the giving up search " +"inwards. Defaults to 2." +msgstr "" + +#: of osgeo.gdal.NearblackOptions:9 +msgid "" +"select how far from black, white or custom colors the pixel values can be" +" and still considered near black, white or custom color. Defaults to 15." +msgstr "" + +#: of osgeo.gdal.NearblackOptions:10 +msgid "adds an alpha band to the output file." +msgstr "" + +#: of osgeo.gdal.NearblackOptions:11 +msgid "adds a mask band to the output file." +msgstr "" + +#: of osgeo.gdal.Rasterize:1 +msgid "Burns vector geometries into a raster" +msgstr "" + +#: of osgeo.gdal.Rasterize:5 +msgid "" +"options: return of gdal.RasterizeOptions(), string or array of strings, " +"other keywords arguments of gdal.RasterizeOptions() If options is " +"provided as a gdal.RasterizeOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:1 +msgid "Create a RasterizeOptions() object that can be passed to gdal.Rasterize()" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:7 +msgid "assigned output bounds: [minx, miny, maxx, maxy]" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:10 osgeo.gdal.WarpOptions:31 +msgid "list of transformer options" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:13 osgeo.gdal.RasterizeOptions:14 +#: osgeo.gdal.WarpOptions:7 osgeo.gdal.WarpOptions:8 +msgid "output resolution in target SRS" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:15 osgeo.gdal.WarpOptions:9 +msgid "whether to force output bounds to be multiple of output resolution" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:17 +msgid "" +"Value or list of values to pre-initialize the output image bands with. " +"However, it is not marked as the nodata value in the output file. If " +"only one value is given, the same value is used in all the bands." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:19 +msgid "Value or list of values to pre-initialize the output image bands with." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:19 +msgid "However, it is not marked as the nodata value in the output file." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:20 +msgid "If only one value is given, the same value is used in all the bands." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:21 +msgid "list of output bands to burn values into" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:22 +msgid "" +"whether to invert rasterization, i.e. burn the fixed burn value, or the " +"burn value associated with the first feature into all parts of the image " +"not inside the provided a polygon." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:25 +msgid "" +"whether to enable the ALL_TOUCHED rasterization option so that all pixels" +" touched by lines or polygons will be updated, not just those on the line" +" render path, or whose center point is within the polygon." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:28 +msgid "" +"list of fixed values to burn into each band for all objects. Excusive " +"with attribute." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:30 +msgid "" +"identifies an attribute field on the features to be used for a burn-in " +"value. The value will be burned into all output bands. Excusive with " +"burnValues." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:32 +msgid "" +"whether to indicate that a burn value should be extracted from the \"Z\" " +"values of the feature. These values are added to the burn value given by " +"burnValues or attribute if provided. As of now, only points and lines are" +" drawn in 3D." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:35 +msgid "list of layers from the datasource that will be used for input features." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:37 osgeo.gdal.VectorTranslateOptions:11 +msgid "SQL dialect ('OGRSQL', 'SQLITE', ...)" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:39 +msgid "optimization mode ('RASTER', 'VECTOR')" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:40 +msgid "set to True to use additive mode instead of replace when burning values" +msgstr "" + +#: of osgeo.gdal.Translate:1 +msgid "Convert a dataset." +msgstr "" + +#: of osgeo.gdal.Translate:5 +msgid "" +"options: return of gdal.TranslateOptions(), string or array of strings " +"other keywords arguments of gdal.TranslateOptions(). If options is " +"provided as a gdal.TranslateOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.TranslateOptions:1 +msgid "Create a TranslateOptions() object that can be passed to gdal.Translate()" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:6 +msgid "array of band numbers (index start at 1)" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:7 +msgid "mask band to generate or not (\"none\", \"auto\", \"mask\", 1, ...)" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:10 +msgid "width of the output raster in percentage (100 = original width)" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:11 +msgid "height of the output raster in percentage (100 = original height)" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:12 +msgid "output horizontal resolution" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:13 +msgid "output vertical resolution" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:15 +msgid "subwindow in pixels to extract: [left_x, top_y, width, height]" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:16 +msgid "subwindow in projected coordinates to extract: [ulx, uly, lrx, lry]" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:17 +msgid "SRS in which projWin is expressed" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:18 +msgid "strict mode" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:19 +msgid "unscale values with scale and offset metadata" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:20 +msgid "" +"list of scale parameters, each of the form [src_min,src_max] or " +"[src_min,src_max,dst_min,dst_max]" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:21 +msgid "list of exponentiation parameters" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:23 +msgid "list of metadata options" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:25 +msgid "ignore GCP in the raster" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:26 +msgid "list of GCPs" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:27 +msgid "nodata value (or \"none\" to unset it)" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:28 +msgid "Color palette expansion mode: \"gray\", \"rgb\", \"rgba\"" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:29 +msgid "whether to calculate statistics" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:30 +msgid "whether to write source RAT" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:31 +msgid "whether to copy XMP metadata" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:32 osgeo.gdal.WarpOptions:22 +msgid "resampling mode" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:33 osgeo.gdal.WarpOptions:41 +msgid "To specify which overview level of source files must be used" +msgstr "" + +#: of osgeo.gdal.Warp:1 +msgid "Warp one or several datasets." +msgstr "" + +#: of osgeo.gdal.MultiDimTranslate:4 osgeo.gdal.Warp:4 +msgid "" +"an array of Dataset objects or filenames, or a Dataset object or a " +"filename" +msgstr "" + +#: of osgeo.gdal.Warp:5 +msgid "" +"options: return of gdal.WarpOptions(), string or array of strings, other " +"keywords arguments of gdal.WarpOptions(). If options is provided as a " +"gdal.WarpOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.WarpOptions:1 +msgid "Create a WarpOptions() object that can be passed to gdal.Warp()" +msgstr "" + +#: of osgeo.gdal.WarpOptions:5 +msgid "output bounds as (minX, minY, maxX, maxY) in target SRS" +msgstr "" + +#: of osgeo.gdal.WarpOptions:6 +msgid "" +"SRS in which output bounds are expressed, in the case they are not " +"expressed in dstSRS" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:6 osgeo.gdal.WarpOptions:12 +msgid "source SRS" +msgstr "" + +#: of osgeo.gdal.WarpOptions:13 +msgid "output SRS" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:8 osgeo.gdal.WarpOptions:14 +msgid "coordinate operation as a PROJ string or WKT string" +msgstr "" + +#: of osgeo.gdal.WarpOptions:15 +msgid "" +"whether to force the last band of the input dataset to be considered as " +"an alpha band" +msgstr "" + +#: of osgeo.gdal.WarpOptions:16 +msgid "whether to force the creation of an output alpha band" +msgstr "" + +#: of osgeo.gdal.WarpOptions:18 +msgid "working type (gdalconst.GDT_Byte, etc...)" +msgstr "" + +#: of osgeo.gdal.WarpOptions:19 +msgid "list of warping options" +msgstr "" + +#: of osgeo.gdal.WarpOptions:20 +msgid "error threshold for approximation transformer (in pixels)" +msgstr "" + +#: of osgeo.gdal.WarpOptions:21 +msgid "size of working buffer in MB" +msgstr "" + +#: of osgeo.gdal.WarpOptions:24 +msgid "source nodata value(s)" +msgstr "" + +#: of osgeo.gdal.WarpOptions:25 +msgid "output nodata value(s)" +msgstr "" + +#: of osgeo.gdal.WarpOptions:26 +msgid "whether to multithread computation and I/O operations" +msgstr "" + +#: of osgeo.gdal.WarpOptions:27 +msgid "whether to use Thin Plate Spline GCP transformer" +msgstr "" + +#: of osgeo.gdal.WarpOptions:28 +msgid "whether to use RPC transformer" +msgstr "" + +#: of osgeo.gdal.WarpOptions:29 +msgid "whether to use GeoLocation array transformer" +msgstr "" + +#: of osgeo.gdal.WarpOptions:30 +msgid "order of polynomial GCP interpolation" +msgstr "" + +#: of osgeo.gdal.WarpOptions:32 +msgid "cutline dataset name" +msgstr "" + +#: of osgeo.gdal.WarpOptions:33 +msgid "cutline layer name" +msgstr "" + +#: of osgeo.gdal.WarpOptions:34 +msgid "cutline WHERE clause" +msgstr "" + +#: of osgeo.gdal.WarpOptions:35 +msgid "cutline SQL statement" +msgstr "" + +#: of osgeo.gdal.WarpOptions:36 +msgid "cutline blend distance in pixels" +msgstr "" + +#: of osgeo.gdal.WarpOptions:37 +msgid "whether to use cutline extent for output bounds" +msgstr "" + +#: of osgeo.gdal.WarpOptions:38 +msgid "whether to copy source metadata" +msgstr "" + +#: of osgeo.gdal.WarpOptions:39 +msgid "metadata data conflict value" +msgstr "" + +#: of osgeo.gdal.WarpOptions:40 +msgid "whether to force color interpretation of input bands to output bands" +msgstr "" + +#: ../../source/api/python/utilities.rst:75 +msgid "Multidimensional Raster Utilities" +msgstr "" + +#: of osgeo.gdal.MultiDimInfo:4 +msgid "" +"options: return of gdal.MultiDimInfoOptions(), string or array of strings" +" other keywords arguments of gdal.MultiDimInfoOptions(). If options is " +"provided as a gdal.MultiDimInfoOptions() object, other keywords are " +"ignored." +msgstr "" + +#: of osgeo.gdal.MultiDimInfoOptions:1 +msgid "" +"Create a MultiDimInfoOptions() object that can be passed to " +"gdal.MultiDimInfo() options can be be an array of strings, a string or " +"let empty and filled from other keywords." +msgstr "" + +#: of osgeo.gdal.MultiDimTranslate:1 +msgid "MultiDimTranslate one or several datasets." +msgstr "" + +#: of osgeo.gdal.MultiDimTranslate:5 +msgid "" +"options: return of gdal.MultiDimTranslateOptions(), string or array of " +"strings other keywords arguments of gdal.MultiDimTranslateOptions(). If " +"options is provided as a gdal.MultiDimTranslateOptions() object, other " +"keywords are ignored." +msgstr "" + +#: of osgeo.gdal.MultiDimTranslateOptions:1 +msgid "" +"Create a MultiDimTranslateOptions() object that can be passed to " +"gdal.MultiDimTranslate()" +msgstr "" + +#: of osgeo.gdal.MultiDimTranslateOptions:6 +msgid "" +"list of array specifications, each of them being an array name or " +"\"name={src_array_name},dstname={dst_name},transpose=[1,0],view=[:,::-1]\"" +msgstr "" + +#: of osgeo.gdal.MultiDimTranslateOptions:8 +msgid "" +"list of group specifications, each of them being a group name or " +"\"name={src_array_name},dstname={dst_name},recursive=no\"" +msgstr "" + +#: of osgeo.gdal.MultiDimTranslateOptions:10 +msgid "" +"list of subset specifications, each of them being like " +"\"{dim_name}({min_val},{max_val})\" or \"{dim_name}({slice_va})\"" +msgstr "" + +#: of osgeo.gdal.MultiDimTranslateOptions:12 +msgid "" +"list of dimension scaling specifications, each of them being like " +"\"{dim_name}({scale_factor})\"" +msgstr "" + +#: ../../source/api/python/utilities.rst:86 +msgid "Vector Utilities" +msgstr "" + +#: of osgeo.gdal.VectorTranslate:1 +msgid "Convert one vector dataset" +msgstr "" + +#: of osgeo.gdal.VectorTranslate:5 +msgid "" +"options: return of gdal.VectorTranslateOptions(), string or array of " +"strings, other keywords arguments of gdal.VectorTranslateOptions(). If " +"options is provided as a gdal.VectorTranslateOptions() object, other " +"keywords are ignored." +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:1 +msgid "" +"Create a VectorTranslateOptions() object that can be passed to " +"gdal.VectorTranslate()" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:4 +msgid "format (\"ESRI Shapefile\", etc...)" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:5 +msgid "None for creation, 'update', 'append', 'upsert', 'overwrite'" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:7 +msgid "output SRS (with reprojection if reproject = True)" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:9 +msgid "whether to do reprojection" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:13 +msgid "list of fields to select" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:14 +msgid "" +"whether to add new fields found in source layers (to be used with " +"accessMode == 'append' or 'upsert')" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:15 +msgid "whether to drop NOT NULL constraints on newly created fields" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:16 +msgid "whether to treat empty string values as NULL" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:18 +msgid "" +"SRS in which the spatFilter is expressed. If not specified, it is assumed" +" to be the one of the layer(s)" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:19 +msgid "list of dataset creation options" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:20 +msgid "list of layer creation options" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:22 +msgid "output layer name" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:23 +msgid "output layer geometry type ('POINT', ....)" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:24 +msgid "output dimension ('XY', 'XYZ', 'XYM', 'XYZM', 'layer_dim')" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:25 +msgid "maximum distance between consecutive nodes of a line geometry" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:26 +msgid "run MakeValid() on geometries" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:27 +msgid "name of field to use to set the Z component of geometries" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:28 +msgid "" +"whether to create an additional field for each field associated with a " +"coded field domain." +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:29 +msgid "whether to skip failures" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:30 +msgid "maximum number of features to read per layer" +msgstr "" + +#: ../../source/api/python/vector_api.rst:9 +msgid "Python Vector API" +msgstr "" + +#: ../../source/api/python/vector_api.rst:11 +msgid "" +"This page contains classes, methods, functions that relate to the GDAL " +":ref:`vector_data_model`. The :py:class:`Driver` and :py:class:`Dataset` " +"classes, which applies to both vector and raster data, are documented " +"with the :ref:`python_raster_api`." +msgstr "" + +#: ../../source/api/python/vector_api.rst:13 +msgid "`Layer`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:14 +msgid "`Feature`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:15 +msgid "`Geometry`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:16 +msgid "`FeatureDefn`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:17 +msgid "`FieldDefn`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:18 +msgid "`GeomFieldDefn`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:19 +msgid "`FieldDomain`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:20 +msgid "`Relationship`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:21 +msgid "`StyleTable`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:24 +msgid "Layer" +msgstr "" + +#: of osgeo.ogr.Layer:1 +msgid "Proxy of C++ OGRLayerShadow class." +msgstr "" + +#: of osgeo.ogr.Layer.AlterFieldDefn:1 +msgid "Alter the definition of an existing field on a layer." +msgstr "" + +#: of osgeo.ogr.Layer.AlterFieldDefn:3 +msgid "For more details: :cpp:func:`OGR_L_AlterFieldDefn`" +msgstr "" + +#: of osgeo.ogr.Layer.AlterFieldDefn:5 +msgid "index of the field whose definition must be altered." +msgstr "" + +#: of osgeo.ogr.Layer.AlterFieldDefn:7 +msgid "new field definition" +msgstr "" + +#: of osgeo.ogr.Layer.AlterFieldDefn:9 +msgid "" +"Combination of :py:const:`osgeo.ogr.ALTER_NAME_FLAG`, " +":py:const:`osgeo.ogr.ALTER_TYPE_FLAG`, " +":py:const:`osgeo.ogr.ALTER_WIDTH_PRECISION_FLAG`, " +":py:const:`osgeo.ogr.ALTER_NULLABLE_FLAG` and " +":py:const:`osgeo.ogr.ALTER_DEFAULT_FLAG` to indicate which of the name " +"and/or type and/or width and precision fields and/or nullability from the" +" new field definition must be taken into account." +msgstr "" + +#: of osgeo.ogr.Layer.AlterFieldDefn:20 osgeo.ogr.Layer.CommitTransaction:5 +#: osgeo.ogr.Layer.CreateFeature:10 osgeo.ogr.Layer.CreateField:11 +#: osgeo.ogr.Layer.CreateGeomField:11 osgeo.ogr.Layer.DeleteField:8 +#: osgeo.ogr.Layer.ReorderField:12 osgeo.ogr.Layer.ReorderFields:10 +#: osgeo.ogr.Layer.RollbackTransaction:5 osgeo.ogr.Layer.StartTransaction:5 +#: osgeo.ogr.Layer.UpsertFeature:8 +msgid ":py:const:`osgeo.ogr.OGRERR_NONE` on success." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:1 +msgid "Clip off areas that are not covered by the method layer." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:3 +msgid "For more details: :cpp:func:`OGR_L_Clip`" +msgstr "" + +#: of osgeo.ogr.Layer.Clip:5 osgeo.ogr.Layer.Erase:5 osgeo.ogr.Layer.Identity:5 +#: osgeo.ogr.Layer.Intersection:5 osgeo.ogr.Layer.SymDifference:5 +#: osgeo.ogr.Layer.Union:7 osgeo.ogr.Layer.Update:5 +msgid "the method layer. Should not be None." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:7 osgeo.ogr.Layer.Erase:7 osgeo.ogr.Layer.Identity:7 +#: osgeo.ogr.Layer.Intersection:7 osgeo.ogr.Layer.SymDifference:7 +#: osgeo.ogr.Layer.Union:9 osgeo.ogr.Layer.Update:7 +msgid "" +"the layer where the features resulting from the operation are inserted. " +"Should not be None." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:10 osgeo.ogr.Layer.Erase:10 +#: osgeo.ogr.Layer.Identity:10 osgeo.ogr.Layer.Intersection:10 +#: osgeo.ogr.Layer.SymDifference:10 osgeo.ogr.Layer.Union:12 +#: osgeo.ogr.Layer.Update:10 +msgid "" +"List of options (empty list is allowed). For example " +"[\"PROMOTE_TO_MULTI=YES\"]." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:12 osgeo.ogr.Layer.Erase:12 +#: osgeo.ogr.Layer.Identity:12 osgeo.ogr.Layer.Intersection:12 +#: osgeo.ogr.Layer.SymDifference:12 osgeo.ogr.Layer.Union:14 +#: osgeo.ogr.Layer.Update:12 +msgid "" +"a GDALProgressFunc() compatible callback function for reporting progress " +"or None." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:15 osgeo.ogr.Layer.Erase:15 +#: osgeo.ogr.Layer.GetGeometryTypes:14 osgeo.ogr.Layer.Identity:15 +#: osgeo.ogr.Layer.Intersection:15 osgeo.ogr.Layer.SymDifference:15 +#: osgeo.ogr.Layer.Union:17 osgeo.ogr.Layer.Update:15 +msgid "Argument to be passed to 'callback'. May be None." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:17 osgeo.ogr.Layer.Erase:17 +#: osgeo.ogr.Layer.Identity:17 osgeo.ogr.Layer.Intersection:17 +#: osgeo.ogr.Layer.SymDifference:17 osgeo.ogr.Layer.Union:19 +#: osgeo.ogr.Layer.Update:17 +msgid "" +"An error code if there was an error or the execution was interrupted, " +":py:const:`osgeo.ogr.OGRERR_NONE` otherwise." +msgstr "" + +#: of osgeo.ogr.Layer.CommitTransaction:1 +msgid "For datasources which support transactions, this commits a transaction." +msgstr "" + +#: of osgeo.ogr.Layer.CommitTransaction:3 +msgid "For more details: :cpp:func:`OGR_L_CommitTransaction`" +msgstr "" + +#: of osgeo.ogr.Layer.CreateFeature:1 +msgid "Create and write a new feature within a layer." +msgstr "" + +#: of osgeo.ogr.Layer.CreateFeature:3 +msgid "For more details: :cpp:func:`OGR_L_CreateFeature`" +msgstr "" + +#: of osgeo.ogr.Layer.CreateFeature:5 +msgid "" +"To create a feature, but set it if it exists see " +":py:meth:`.Layer.UpsertFeature`." +msgstr "" + +#: of osgeo.ogr.Layer.CreateFeature:7 osgeo.ogr.Layer.UpsertFeature:5 +msgid "The feature to write to disk." +msgstr "" + +#: of osgeo.ogr.Layer.CreateField:1 +msgid "Create a new field on a layer." +msgstr "" + +#: of osgeo.ogr.Layer.CreateField:3 +msgid "For more details: :cpp:func:`OGR_L_CreateField`" +msgstr "" + +#: of osgeo.ogr.Layer.CreateField:5 +msgid "The field definition to write to disk." +msgstr "" + +#: of osgeo.ogr.Layer.CreateField:7 osgeo.ogr.Layer.CreateGeomField:7 +msgid "" +"If True, the field may be created in a slightly different form depending " +"on the limitations of the format driver." +msgstr "" + +#: of osgeo.ogr.Layer.CreateFields:1 +msgid "Create a list of fields on the Layer" +msgstr "" + +#: of osgeo.ogr.Layer.CreateGeomField:1 +msgid "Create a new geometry field on a layer." +msgstr "" + +#: of osgeo.ogr.Layer.CreateGeomField:3 +msgid "For more details: :cpp:func:`OGR_L_CreateGeomField`" +msgstr "" + +#: of osgeo.ogr.Layer.CreateGeomField:5 +msgid "The geometry field definition to write to disk." +msgstr "" + +#: of osgeo.ogr.Layer.DeleteFeature:1 +msgid "Delete feature from layer." +msgstr "" + +#: of osgeo.ogr.Layer.DeleteFeature:3 +msgid "For more details: :cpp:func:`OGR_L_DeleteFeature`" +msgstr "" + +#: of osgeo.ogr.Layer.DeleteFeature:5 +msgid "The feature id to be deleted from the layer" +msgstr "" + +#: of osgeo.ogr.Layer.DeleteFeature:8 +msgid "" +":py:const:`osgeo.ogr.OGRERR_NONE` if the operation works, otherwise an " +"appropriate error code (e.g " +":py:const:`osgeo.ogr.OGRERR_NON_EXISTING_FEATURE`) if the feature does " +"not exist." +msgstr "" + +#: of osgeo.ogr.Layer.DeleteField:1 +msgid "Delete an existing field on a layer." +msgstr "" + +#: of osgeo.ogr.Layer.DeleteField:3 +msgid "For more details: :cpp:func:`OGR_L_DeleteField`" +msgstr "" + +#: of osgeo.ogr.Layer.DeleteField:5 +msgid "index of the field to delete." +msgstr "" + +#: of osgeo.ogr.Layer.Erase:1 +msgid "Remove areas that are covered by the method layer." +msgstr "" + +#: of osgeo.ogr.Layer.Erase:3 +msgid "For more details: :cpp:func:`OGR_L_Erase`" +msgstr "" + +#: of osgeo.ogr.Layer.FindFieldIndex:1 +msgid "Find the index of field in a layer." +msgstr "" + +#: of osgeo.ogr.Layer.FindFieldIndex:3 +msgid "For more details: :cpp:func:`OGR_L_FindFieldIndex`" +msgstr "" + +#: of osgeo.ogr.Layer.FindFieldIndex:5 +msgid "field index, or -1 if the field doesn't exist" +msgstr "" + +#: of osgeo.ogr.Layer.GetArrowStreamAsNumPy:1 +msgid "" +"Return an ArrowStream as NumPy Array objects. A specific option to this " +"method is USE_MASKED_ARRAYS=YES/NO (default is YES)." +msgstr "" + +#: of osgeo.ogr.Layer.GetArrowStreamAsPyArrow:1 +msgid "Return an ArrowStream as PyArrow Schema and Array objects" +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:1 +msgid "Fetch the extent of this layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:3 osgeo.ogr.Layer.SetSpatialFilter:3 +#: osgeo.ogr.Layer.SetSpatialFilterRect:3 +msgid "For more details:" +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:5 +msgid ":cpp:func:`OGR_L_GetExtent`" +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:6 +msgid ":cpp:func:`OGR_L_GetExtentEx`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:6 osgeo.ogr.Geometry.GetEnvelope3D:6 +#: osgeo.ogr.Layer.GetExtent:8 +msgid "Check the return order of the bounds." +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:10 +msgid "" +"Flag indicating whether the extent should be computed even if it is " +"expensive." +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:13 +msgid "Whether None can be returned in the response." +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:15 +msgid "" +"Ithe index of the geometry field on which to compute the extent. Can be " +"iterated over using :py:func:`range` and :py:func:`GetGeomFieldCount`." +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:8 osgeo.ogr.Layer.GetExtent:19 +msgid "" +"* **minx** (*float*) * **maxx** (*float*) * **miny** (*float*) * **maxy**" +" (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:8 osgeo.ogr.Geometry.GetEnvelope3D:8 +#: osgeo.ogr.Layer.GetExtent:19 +msgid "**minx** (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:9 osgeo.ogr.Geometry.GetEnvelope3D:9 +#: osgeo.ogr.Layer.GetExtent:20 +msgid "**maxx** (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:10 osgeo.ogr.Geometry.GetEnvelope3D:10 +#: osgeo.ogr.Layer.GetExtent:21 +msgid "**miny** (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:11 osgeo.ogr.Geometry.GetEnvelope3D:11 +#: osgeo.ogr.Layer.GetExtent:22 +msgid "**maxy** (*float*)" +msgstr "" + +#: of osgeo.ogr.Layer.GetFIDColumn:1 +msgid "" +"This method returns the name of the underlying database column being used" +" as the FID column, or '' if not supported." +msgstr "" + +#: of osgeo.ogr.Layer.GetFIDColumn:4 +msgid "For more details: :cpp:func:`OGR_L_GetFIDColumn`" +msgstr "" + +#: of osgeo.ogr.Layer.GetFIDColumn:6 +msgid "fid column name." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeature:1 +msgid "Fetch a feature by its identifier." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeature:3 +msgid "For more details: :cpp:func:`OGR_L_GetFeature`" +msgstr "" + +#: of osgeo.ogr.Layer.GetFeature:5 +msgid "" +"Use :py:func:`TestCapability` with (:py:const:`osgeo.ogr.OLCRandomRead`) " +"to establish if this layer supports efficient random access reading via " +":py:func:`GetFeature`; However, the call should always work if the " +"feature exists." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeature:9 +msgid "" +"Sequential reads (with :py:func:`GetNextFeature`) are generally " +"considered interrupted by a :py:func:`GetFeature` call." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeature:12 +msgid "The feature id of the feature to read." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeature:15 +msgid "" +"A new feature now owned by the caller, or None on failure. The returned " +"feature should be deleted with :py:func:`Destroy`." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeatureCount:1 +msgid "Fetch the feature count in this layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeatureCount:3 +msgid "For more details: :cpp:func:`OGR_L_GetFeatureCount`" +msgstr "" + +#: of osgeo.ogr.Layer.GetFeatureCount:5 +msgid "" +"Flag indicating whether the count should be computed even if it is " +"expensive." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeatureCount:9 +msgid "Feature count, -1 if count not known." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeaturesRead:1 +msgid "For more details: :cpp:func:`OGR_L_GetFeaturesRead`" +msgstr "" + +#: of osgeo.ogr.Layer.GetGeomType:1 +msgid "Return the layer geometry type." +msgstr "" + +#: of osgeo.ogr.Layer.GetGeomType:3 +msgid "For more details: :cpp:func:`OGR_L_GetGeomType`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetGeometryType:5 osgeo.ogr.Layer.GetGeomType:5 +msgid "" +"The geometry type code. The types can be found with 'osgeo.ogr.wkb' " +"prefix. For example :py:const:`osgeo.ogr.wkbPolygon`." +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryColumn:1 +msgid "" +"This method returns the name of the underlying database column being used" +" as the geometry column, or '' if not supported." +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryColumn:4 +msgid "For more details: :cpp:func:`OGR_L_GetGeometryColumn`" +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryColumn:6 +msgid "geometry column name." +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryTypes:1 +msgid "Get actual geometry types found in features." +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryTypes:3 +msgid "For more details: :cpp:func:`OGR_L_GetGeometryTypes`" +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryTypes:5 +msgid "index of the geometry field" +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryTypes:7 +msgid "" +"0, or a combination of :py:const:`osgeo.ogr.GGT_COUNT_NOT_NEEDED`, " +":py:const:`osgeo.ogr.GGT_STOP_IF_MIXED` and " +":py:const:`osgeo.ogr.GGT_GEOMCOLLECTIONZ_TINZ`" +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryTypes:11 +msgid "" +"a GDALProgressFunc() compatible callback function for cancellation or " +"None." +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryTypes:16 +msgid "" +"A dictionary whose keys are :py:const:`osgeo.ogr.wkbXXXX` constants and " +"values the corresponding number of geometries of that type in the layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetLayerDefn:1 +msgid "Fetch the schema information for this layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetLayerDefn:3 +msgid "For more details: :cpp:func:`OGR_L_GetLayerDefn`" +msgstr "" + +#: of osgeo.ogr.Layer.GetLayerDefn:5 +msgid "The feature definition." +msgstr "" + +#: of osgeo.ogr.Layer.GetName:1 +msgid "Return the layer name." +msgstr "" + +#: of osgeo.ogr.Layer.GetName:3 +msgid "For more details: :cpp:func:`OGR_L_GetName`" +msgstr "" + +#: of osgeo.ogr.Layer.GetName:5 +msgid "The layer name" +msgstr "" + +#: of osgeo.ogr.Layer.GetNextFeature:1 +msgid "Fetch the next available feature from this layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetNextFeature:3 +msgid "For more details: :cpp:func:`OGR_L_GetNextFeature`" +msgstr "" + +#: of osgeo.ogr.Layer.GetNextFeature:5 +msgid "A feature or None if no more features are available." +msgstr "" + +#: of osgeo.ogr.Layer.GetRefCount:1 +msgid "For more details: :cpp:func:`OGR_L_GetRefCount`" +msgstr "" + +#: of osgeo.ogr.Layer.GetSpatialFilter:1 +msgid "This function returns the current spatial filter for this layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetSpatialFilter:3 +msgid "For more details: :cpp:func:`OGR_L_GetSpatialFilter`" +msgstr "" + +#: of osgeo.ogr.Layer.GetSpatialFilter:5 +msgid "The spatial filter geometry." +msgstr "" + +#: of osgeo.ogr.Layer.GetSpatialRef:1 +msgid "Fetch the spatial reference system for this layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetSpatialRef:3 +msgid "For more details: :cpp:func:`OGR_L_GetSpatialRef`" +msgstr "" + +#: of osgeo.ogr.Layer.GetSpatialRef:5 +msgid "spatial reference, or None if there isn't one." +msgstr "" + +#: of osgeo.ogr.Layer.GetStyleTable:3 +msgid "For more details: :cpp:func:`OGR_L_GetStyleTable`" +msgstr "" + +#: of osgeo.ogr.Layer.Identity:1 +msgid "Identify the features of this layer with the ones from the identity layer." +msgstr "" + +#: of osgeo.ogr.Layer.Identity:3 +msgid "For more details: :cpp:func:`OGR_L_Identity`" +msgstr "" + +#: of osgeo.ogr.Layer.Intersection:1 +msgid "Intersection of two layers." +msgstr "" + +#: of osgeo.ogr.Layer.Intersection:3 +msgid "For more details: :cpp:func:`OGR_L_Intersection`" +msgstr "" + +#: of osgeo.ogr.Layer.ReorderField:1 +msgid "Reorder an existing field on a layer." +msgstr "" + +#: of osgeo.ogr.Layer.ReorderField:3 +msgid "For more details: :cpp:func:`OGR_L_ReorderField`" +msgstr "" + +#: of osgeo.ogr.Layer.ReorderField:5 +msgid "" +"previous position of the field to move. Must be in the range " +"[0,GetFieldCount()-1]." +msgstr "" + +#: of osgeo.ogr.Layer.ReorderField:8 +msgid "" +"new position of the field to move. Must be in the range " +"[0,GetFieldCount()-1]." +msgstr "" + +#: of osgeo.ogr.Layer.ReorderFields:1 +msgid "Reorder all the fields of a layer." +msgstr "" + +#: of osgeo.ogr.Layer.ReorderFields:3 +msgid "For more details: :cpp:func:`OGR_L_ReorderFields`" +msgstr "" + +#: of osgeo.ogr.Layer.ReorderFields:5 +msgid "" +"A list of GetLayerDefn().GetFieldCount() elements which is a permutation " +"of [0, GetLayerDefn().GetFieldCount()-1]." +msgstr "" + +#: of osgeo.ogr.Layer.ResetReading:1 +msgid "Reset feature reading to start on the first feature." +msgstr "" + +#: of osgeo.ogr.Layer.ResetReading:3 +msgid "For more details: :cpp:func:`OGR_L_ResetReading`" +msgstr "" + +#: of osgeo.ogr.Layer.RollbackTransaction:1 +msgid "" +"Roll back a datasource to its state before the start of the current " +"transaction." +msgstr "" + +#: of osgeo.ogr.Layer.RollbackTransaction:3 +msgid "For more details: :cpp:func:`OGR_L_RollbackTransaction`" +msgstr "" + +#: of osgeo.ogr.Layer.SetAttributeFilter:1 +msgid "Set a new attribute query." +msgstr "" + +#: of osgeo.ogr.Layer.SetAttributeFilter:3 +msgid "For more details: :cpp:func:`OGR_L_SetAttributeFilter`" +msgstr "" + +#: of osgeo.ogr.Layer.SetAttributeFilter:5 +msgid "query in restricted SQL WHERE format, or None to clear the current query." +msgstr "" + +#: of osgeo.ogr.Layer.SetAttributeFilter:9 +msgid "" +":py:const:`osgeo.ogr.OGRERR_NONE` if successfully installed, or an error " +"code if the query expression is in error, or some other failure occurs." +msgstr "" + +#: of osgeo.ogr.Layer.SetFeature:1 +msgid "Rewrite an existing feature." +msgstr "" + +#: of osgeo.ogr.Layer.SetFeature:3 +msgid "For more details: :cpp:func:`OGR_L_SetFeature`" +msgstr "" + +#: of osgeo.ogr.Layer.SetFeature:5 +msgid "" +"To set a feature, but create it if it doesn't exist see " +":py:meth:`.Layer.UpsertFeature`." +msgstr "" + +#: of osgeo.ogr.Layer.SetFeature:7 +msgid "The feature to write." +msgstr "" + +#: of osgeo.ogr.Layer.SetFeature:10 +msgid "" +":py:const:`osgeo.ogr.OGRERR_NONE` if the operation works, otherwise an " +"appropriate error code (e.g " +":py:const:`osgeo.ogr.OGRERR_NON_EXISTING_FEATURE` if the feature does not" +" exist)." +msgstr "" + +#: of osgeo.ogr.Layer.SetIgnoredFields:1 +msgid "Set which fields can be omitted when retrieving features from the layer." +msgstr "" + +#: of osgeo.ogr.Layer.SetIgnoredFields:4 +msgid "For more details: :cpp:func:`OGR_L_SetIgnoredFields`" +msgstr "" + +#: of osgeo.ogr.Layer.SetIgnoredFields:6 +msgid "" +"A list of field names. If an empty list is passed, the ignored list is " +"cleared." +msgstr "" + +#: of osgeo.ogr.Layer.SetIgnoredFields:10 +msgid "" +":py:const:`osgeo.ogr.OGRERR_NONE` if all field names have been resolved " +"(even if the driver does not support this method)" +msgstr "" + +#: of osgeo.ogr.Layer.SetNextByIndex:1 +msgid "Move read cursor to the nIndex'th feature in the current resultset." +msgstr "" + +#: of osgeo.ogr.Layer.SetNextByIndex:3 +msgid "For more details: :cpp:func:`OGR_L_SetNextByIndex`" +msgstr "" + +#: of osgeo.ogr.Layer.SetNextByIndex:5 +msgid "The index indicating how many steps into the result set to seek." +msgstr "" + +#: of osgeo.ogr.Layer.SetNextByIndex:8 +msgid ":py:const:`osgeo.ogr.OGRERR_NONE` on success or an error code." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilter:1 +msgid "Set a new spatial filter." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilter:5 +msgid ":cpp:func:`OGR_L_SetSpatialFilter`" +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilter:6 +msgid ":cpp:func:`OGR_L_SetSpatialFilterEx`" +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilter:8 osgeo.ogr.Layer.SetSpatialFilterRect:8 +msgid "index of the geometry field on which the spatial filter operates." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilter:10 +msgid "" +"The geometry to use as a filtering region. None may be passed indicating " +"that the current spatial filter should be cleared, but no new one " +"instituted." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:1 +msgid "Set a new rectangular spatial filter." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:5 +msgid ":cpp:func:`OGR_L_SetSpatialFilterRect`" +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:6 +msgid ":cpp:func:`OGR_L_SetSpatialFilterRectEx`" +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:10 +msgid "the minimum X coordinate for the rectangular region." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:12 +msgid "the minimum Y coordinate for the rectangular region." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:14 +msgid "the maximum X coordinate for the rectangular region." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:16 +msgid "the maximum Y coordinate for the rectangular region." +msgstr "" + +#: of osgeo.ogr.Layer.SetStyleTable:3 +msgid "For more details: :cpp:func:`OGR_L_SetStyleTable`" +msgstr "" + +#: of osgeo.ogr.Layer.StartTransaction:1 +msgid "For datasources which support transactions, this creates a transaction." +msgstr "" + +#: of osgeo.ogr.Layer.StartTransaction:3 +msgid "For more details: :cpp:func:`OGR_L_StartTransaction`" +msgstr "" + +#: of osgeo.ogr.Layer.SymDifference:1 +msgid "Symmetrical difference of two layers." +msgstr "" + +#: of osgeo.ogr.Layer.SymDifference:3 +msgid "For more details: :cpp:func:`OGR_L_SymDifference`" +msgstr "" + +#: of osgeo.ogr.Layer.SyncToDisk:3 +msgid "For more details: :cpp:func:`OGR_L_SyncToDisk`" +msgstr "" + +#: of osgeo.ogr.Layer.SyncToDisk:5 +msgid "" +":py:const:`osgeo.ogr.OGRERR_NONE` if no error occurs (even if nothing is " +"done) or an error code." +msgstr "" + +#: of osgeo.ogr.Layer.TestCapability:1 +msgid "Test if this layer supported the named capability." +msgstr "" + +#: of osgeo.ogr.Layer.TestCapability:3 +msgid "For more details: :cpp:func:`OGR_L_TestCapability`" +msgstr "" + +#: of osgeo.ogr.Layer.TestCapability:5 +msgid "" +"The name of the capability to test. These can be found in the `osgeo.ogr`" +" namespace. For example, :py:const:`osgeo.ogr.OLCRandomRead`." +msgstr "" + +#: of osgeo.ogr.Layer.TestCapability:10 +msgid "" +"True if the layer has the requested capability, or False otherwise. Will " +"return False for any unrecognized capabilities." +msgstr "" + +#: of osgeo.ogr.Layer.Union:1 +msgid "Union of two layers." +msgstr "" + +#: of osgeo.ogr.Layer.Union:3 +msgid "For more details: :cpp:func:`OGR_L_Union`" +msgstr "" + +#: of osgeo.ogr.Layer.Union:5 +msgid "The first geometry field is always used." +msgstr "" + +#: of osgeo.ogr.Layer.Update:1 +msgid "Update this layer with features from the update layer." +msgstr "" + +#: of osgeo.ogr.Layer.Update:3 +msgid "For more details: :cpp:func:`OGR_L_Update`" +msgstr "" + +#: of osgeo.ogr.Layer.UpsertFeature:1 +msgid "Rewrite an existing feature or create a new feature within a layer." +msgstr "" + +#: of osgeo.ogr.Layer.UpsertFeature:3 +msgid "For more details: :cpp:func:`OGR_L_UpsertFeature`" +msgstr "" + +#: ../../source/api/python/vector_api.rst:32 +msgid "Feature" +msgstr "" + +#: of osgeo.ogr.Feature:1 +msgid "Proxy of C++ OGRFeatureShadow class." +msgstr "" + +#: of osgeo.ogr.Feature.Clone:1 +msgid "OGRFeatureH OGR_F_Clone(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.Clone:3 +msgid "Duplicate feature." +msgstr "" + +#: of osgeo.ogr.Feature.Clone:5 +msgid "" +"The newly created feature is owned by the caller, and will have its own " +"reference to the OGRFeatureDefn." +msgstr "" + +#: of osgeo.ogr.Feature.Clone:8 +msgid "This function is the same as the C++ method OGRFeature::Clone()." +msgstr "" + +#: of osgeo.ogr.Feature.Clone:10 +msgid "handle to the feature to clone." +msgstr "" + +#: of osgeo.ogr.Feature.Clone:12 +msgid "a handle to the new feature, exactly matching this feature." +msgstr "" + +#: of osgeo.ogr.Feature.DumpReadable:1 +msgid "void OGR_F_DumpReadable(OGRFeatureH hFeat, FILE \\*fpOut)" +msgstr "" + +#: of osgeo.ogr.Feature.DumpReadable:4 +msgid "Dump this feature in a human readable form." +msgstr "" + +#: of osgeo.ogr.Feature.DumpReadable:6 +msgid "" +"This dumps the attributes, and geometry; however, it doesn't definition " +"information (other than field types and names), nor does it report the " +"geometry spatial reference system." +msgstr "" + +#: of osgeo.ogr.Feature.DumpReadable:10 +msgid "This function is the same as the C++ method OGRFeature::DumpReadable()." +msgstr "" + +#: of osgeo.ogr.Feature.DumpReadable:13 +msgid "handle to the feature to dump." +msgstr "" + +#: of osgeo.ogr.Feature.DumpReadable:14 +msgid "the stream to write to, such as strout." +msgstr "" + +#: of osgeo.ogr.Feature.Equal:1 +msgid "int OGR_F_Equal(OGRFeatureH hFeat, OGRFeatureH hOtherFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.Equal:4 +msgid "Test if two features are the same." +msgstr "" + +#: of osgeo.ogr.Feature.Equal:6 +msgid "" +"Two features are considered equal if the share them (handle equality) " +"same OGRFeatureDefn, have the same field values, and the same geometry " +"(as tested by OGR_G_Equal()) as well as the same feature id." +msgstr "" + +#: of osgeo.ogr.Feature.Equal:10 +msgid "This function is the same as the C++ method OGRFeature::Equal()." +msgstr "" + +#: of osgeo.ogr.Feature.Equal:12 +msgid "handle to one of the feature." +msgstr "" + +#: of osgeo.ogr.Feature.Equal:13 +msgid "handle to the other feature to test this one against." +msgstr "" + +#: of osgeo.ogr.Feature.Equal:15 +msgid "TRUE if they are equal, otherwise FALSE." +msgstr "" + +#: of osgeo.ogr.Feature.ExportToJson:1 +msgid "" +"Exports a GeoJSON object which represents the Feature. The as_object " +"parameter determines whether the returned value should be a Python object" +" instead of a string. Defaults to False. The options parameter is passed " +"to Geometry.ExportToJson()" +msgstr "" + +#: of osgeo.ogr.Feature.FillUnsetWithDefault:1 +msgid "" +"void OGR_F_FillUnsetWithDefault(OGRFeatureH hFeat, int bNotNullableOnly, " +"char \\*\\*papszOptions)" +msgstr "" + +#: of osgeo.ogr.Feature.FillUnsetWithDefault:5 +msgid "Fill unset fields with default values that might be defined." +msgstr "" + +#: of osgeo.ogr.Feature.FillUnsetWithDefault:7 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::FillUnsetWithDefault()." +msgstr "" + +#: of osgeo.ogr.Feature.FillUnsetWithDefault:12 +#: osgeo.ogr.Feature.GetNativeData:28 osgeo.ogr.Feature.GetNativeMediaType:18 +#: osgeo.ogr.Feature.SetNativeData:18 osgeo.ogr.Feature.SetNativeMediaType:20 +msgid "handle to the feature." +msgstr "" + +#: of osgeo.ogr.Feature.FillUnsetWithDefault:13 +msgid "if we should fill only unset fields with a not-null constraint." +msgstr "" + +#: of osgeo.ogr.Feature.FillUnsetWithDefault:15 +msgid "unused currently. Must be set to NULL." +msgstr "" + +#: of osgeo.ogr.Feature.GetDefnRef:1 +msgid "OGRFeatureDefnH OGR_F_GetDefnRef(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetDefnRef:3 +msgid "Fetch feature definition." +msgstr "" + +#: of osgeo.ogr.Feature.GetDefnRef:5 +msgid "This function is the same as the C++ method OGRFeature::GetDefnRef()." +msgstr "" + +#: of osgeo.ogr.Feature.GetDefnRef:7 +msgid "handle to the feature to get the feature definition from." +msgstr "" + +#: of osgeo.ogr.Feature.GetDefnRef:9 +msgid "a handle to the feature definition object on which feature depends." +msgstr "" + +#: of osgeo.ogr.Feature.GetFID:1 +msgid "GIntBig OGR_F_GetFID(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFID:4 +msgid "Get feature identifier." +msgstr "" + +#: of osgeo.ogr.Feature.GetFID:6 +msgid "" +"This function is the same as the C++ method OGRFeature::GetFID(). Note: " +"since GDAL 2.0, this method returns a GIntBig (previously a long)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFID:10 +msgid "handle to the feature from which to get the feature" +msgstr "" + +#: of osgeo.ogr.Feature.GetFID:13 +msgid "feature id or OGRNullFID if none has been assigned." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:1 +msgid "" +"GByte\\* OGR_F_GetFieldAsBinary(OGRFeatureH hFeat, int iField, int " +"\\*pnBytes)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:4 +msgid "Fetch field value as binary." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:6 +msgid "This method only works for OFTBinary and OFTString fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:8 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsBinary()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:11 +#: osgeo.ogr.Feature.GetFieldAsDateTime:16 +#: osgeo.ogr.Feature.GetFieldAsDouble:12 +#: osgeo.ogr.Feature.GetFieldAsDoubleList:12 +#: osgeo.ogr.Feature.GetFieldAsInteger:12 +#: osgeo.ogr.Feature.GetFieldAsInteger64:15 +#: osgeo.ogr.Feature.GetFieldAsInteger64List:14 +#: osgeo.ogr.Feature.GetFieldAsIntegerList:11 +#: osgeo.ogr.Feature.GetFieldAsString:12 +#: osgeo.ogr.Feature.GetFieldAsStringList:14 +#: osgeo.ogr.Feature.SetFieldDoubleList:18 +#: osgeo.ogr.Feature.SetFieldInteger64:21 +#: osgeo.ogr.Feature.SetFieldInteger64List:20 +#: osgeo.ogr.Feature.SetFieldIntegerList:18 osgeo.ogr.Feature.SetFieldString:21 +#: osgeo.ogr.Feature.SetFieldStringList:17 +msgid "handle to the feature that owned the field." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:12 +#: osgeo.ogr.Feature.GetFieldAsDateTime:17 +#: osgeo.ogr.Feature.GetFieldAsDouble:13 +#: osgeo.ogr.Feature.GetFieldAsDoubleList:13 +#: osgeo.ogr.Feature.GetFieldAsInteger:13 +#: osgeo.ogr.Feature.GetFieldAsInteger64:16 +#: osgeo.ogr.Feature.GetFieldAsInteger64List:15 +#: osgeo.ogr.Feature.GetFieldAsIntegerList:12 +#: osgeo.ogr.Feature.GetFieldAsString:13 +#: osgeo.ogr.Feature.GetFieldAsStringList:15 +#: osgeo.ogr.Feature.GetFieldDefnRef:9 osgeo.ogr.Feature.SetFieldInteger64:22 +#: osgeo.ogr.Feature.SetFieldString:22 +msgid "the field to fetch, from 0 to GetFieldCount()-1." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:13 +msgid "location to place count of bytes returned." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:15 +#: osgeo.ogr.Feature.GetFieldAsStringList:17 +msgid "" +"the field value. This list is internal, and should not be modified, or " +"freed. Its lifetime may be very brief." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:1 +msgid "" +"int OGR_F_GetFieldAsDateTime(OGRFeatureH hFeat, int iField, int " +"\\*pnYear, int \\*pnMonth, int \\*pnDay, int \\*pnHour, int \\*pnMinute, " +"int \\*pnSecond, int \\*pnTZFlag)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:6 +msgid "Fetch field value as date and time." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:8 +msgid "" +"Currently this method only works for OFTDate, OFTTime and OFTDateTime " +"fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:11 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsDateTime()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:14 +msgid "Use OGR_F_GetFieldAsDateTimeEx() for second with millisecond accuracy." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:18 +msgid "(including century)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:19 +msgid "(1-12)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:20 +msgid "(1-31)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:21 +msgid "(0-23)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:22 +#: osgeo.ogr.Feature.GetFieldAsDateTime:23 +msgid "(0-59)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:24 +msgid "(0=unknown, 1=localtime, 100=GMT, see data model for" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:27 +msgid "TRUE on success or FALSE on failure." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDouble:1 +msgid "double OGR_F_GetFieldAsDouble(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDouble:3 +msgid "Fetch field value as a double." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDouble:5 +msgid "" +"OFTString features will be translated using CPLAtof(). OFTInteger fields " +"will be cast to double. Other field types, or errors will result in a " +"return value of zero." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDouble:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsDouble()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDouble:15 +#: osgeo.ogr.Feature.GetFieldAsInteger:15 +#: osgeo.ogr.Feature.GetFieldAsInteger64:18 +msgid "the field value." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDoubleList:1 +msgid "" +"const double\\* OGR_F_GetFieldAsDoubleList(OGRFeatureH hFeat, int iField," +" int \\*pnCount)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDoubleList:5 +msgid "Fetch field value as a list of doubles." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDoubleList:7 +msgid "Currently this function only works for OFTRealList fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDoubleList:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsDoubleList()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDoubleList:14 +msgid "an integer to put the list count (number of doubles) into." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDoubleList:16 +#: osgeo.ogr.Feature.GetFieldAsInteger64List:18 +#: osgeo.ogr.Feature.GetFieldAsIntegerList:15 +msgid "" +"the field value. This list is internal, and should not be modified, or " +"freed. Its lifetime may be very brief. If \\*pnCount is zero on return " +"the returned pointer may be NULL or non-NULL." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger:1 +msgid "int OGR_F_GetFieldAsInteger(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger:3 +msgid "Fetch field value as integer." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger:5 +msgid "" +"OFTString features will be translated using atoi(). OFTReal fields will " +"be cast to integer. Other field types, or errors will result in a return " +"value of zero." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsInteger()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64:1 +msgid "GIntBig OGR_F_GetFieldAsInteger64(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64:3 +msgid "Fetch field value as integer 64 bit." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64:5 +msgid "" +"OFTInteger are promoted to 64 bit. OFTString features will be translated " +"using CPLAtoGIntBig(). OFTReal fields will be cast to integer. Other " +"field types, or errors will result in a return value of zero." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64:10 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsInteger64()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64List:1 +msgid "" +"const GIntBig\\* OGR_F_GetFieldAsInteger64List(OGRFeatureH hFeat, int " +"iField, int \\*pnCount)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64List:5 +msgid "Fetch field value as a list of 64 bit integers." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64List:7 +msgid "Currently this function only works for OFTInteger64List fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64List:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsInteger64List()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64List:16 +#: osgeo.ogr.Feature.GetFieldAsIntegerList:13 +msgid "an integer to put the list count (number of integers) into." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsIntegerList:1 +msgid "" +"const int\\* OGR_F_GetFieldAsIntegerList(OGRFeatureH hFeat, int iField, " +"int \\*pnCount)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsIntegerList:4 +msgid "Fetch field value as a list of integers." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsIntegerList:6 +msgid "Currently this function only works for OFTIntegerList fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsIntegerList:8 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsIntegerList()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsString:1 +msgid "const char\\* OGR_F_GetFieldAsString(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsString:3 +msgid "Fetch field value as a string." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsString:5 +msgid "" +"OFTReal and OFTInteger fields will be translated to string using " +"sprintf(), but not necessarily using the established formatting rules. " +"Other field types, or errors will result in a return value of zero." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsString:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsString()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsString:15 +msgid "" +"the field value. This string is internal, and should not be modified, or " +"freed. Its lifetime may be very brief." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsStringList:1 +msgid "char\\*\\* OGR_F_GetFieldAsStringList(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsStringList:4 +msgid "Fetch field value as a list of strings." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsStringList:6 +msgid "Currently this method only works for OFTStringList fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsStringList:8 +msgid "" +"The returned list is terminated by a NULL pointer. The number of elements" +" can also be calculated using CSLCount()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsStringList:11 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsStringList()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldCount:1 +msgid "int OGR_F_GetFieldCount(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldCount:3 +msgid "" +"Fetch number of fields on this feature This will always be the same as " +"the field count for the OGRFeatureDefn." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldCount:6 +msgid "This function is the same as the C++ method OGRFeature::GetFieldCount()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldCount:9 +msgid "handle to the feature to get the fields count from." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldCount:11 osgeo.ogr.FeatureDefn.GetFieldCount:10 +msgid "count of fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldDefnRef:1 +msgid "OGRFieldDefnH OGR_F_GetFieldDefnRef(OGRFeatureH hFeat, int i)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldDefnRef:3 +msgid "Fetch definition for this field." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldDefnRef:5 +msgid "This function is the same as the C++ method OGRFeature::GetFieldDefnRef()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldDefnRef:8 osgeo.ogr.Feature.GetFieldIndex:10 +#: osgeo.ogr.Feature.GetGeomFieldDefnRef:10 +msgid "handle to the feature on which the field is found." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldDefnRef:11 +#: osgeo.ogr.Feature.GetGeomFieldDefnRef:13 +msgid "" +"a handle to the field definition (from the OGRFeatureDefn). This is an " +"internal reference, and should not be deleted or modified." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldIndex:1 +msgid "int OGR_F_GetFieldIndex(OGRFeatureH hFeat, const char \\*pszName)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldIndex:3 +msgid "Fetch the field index given field name." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldIndex:5 +msgid "This is a cover for the OGRFeatureDefn::GetFieldIndex() method." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldIndex:7 +msgid "This function is the same as the C++ method OGRFeature::GetFieldIndex()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldIndex:11 +msgid "the name of the field to search for." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldIndex:13 +msgid "the field index, or -1 if no matching field is found." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldCount:1 +msgid "int OGR_F_GetGeomFieldCount(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldCount:3 +msgid "" +"Fetch number of geometry fields on this feature This will always be the " +"same as the geometry field count for the OGRFeatureDefn." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldCount:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetGeomFieldCount()." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldCount:11 +msgid "handle to the feature to get the geometry fields count from." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldCount:13 +#: osgeo.ogr.FeatureDefn.GetGeomFieldCount:13 +msgid "count of geometry fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldDefnRef:1 +msgid "OGRGeomFieldDefnH OGR_F_GetGeomFieldDefnRef(OGRFeatureH hFeat, int i)" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldDefnRef:3 +msgid "Fetch definition for this geometry field." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldDefnRef:5 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetGeomFieldDefnRef()." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldDefnRef:11 +msgid "the field to fetch, from 0 to GetGeomFieldCount()-1." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:1 +msgid "int OGR_F_GetGeomFieldIndex(OGRFeatureH hFeat, const char \\*pszName)" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:3 +msgid "Fetch the geometry field index given geometry field name." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:5 +msgid "This is a cover for the OGRFeatureDefn::GetGeomFieldIndex() method." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:7 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetGeomFieldIndex()." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:12 +msgid "handle to the feature on which the geometry field is found." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:13 +msgid "the name of the geometry field to search for." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:15 +msgid "the geometry field index, or -1 if no matching geometry field is found." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldRef:1 +msgid "OGRGeometryH OGR_F_GetGeomFieldRef(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldRef:4 +msgid "Fetch a handle to feature geometry." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldRef:6 +msgid "This function is the same as the C++ method OGRFeature::GetGeomFieldRef()." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldRef:9 +msgid "handle to the feature to get geometry from." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldRef:10 +msgid "geometry field to get." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeometryRef:1 osgeo.ogr.Feature.geometry:1 +msgid "Return the feature geometry" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeometryRef:3 osgeo.ogr.Feature.geometry:3 +msgid "" +"The lifetime of the returned geometry is bound to the one of its " +"belonging feature." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeometryRef:6 osgeo.ogr.Feature.geometry:6 +msgid "For more details: :cpp:func:`OGR_F_GetGeometryRef`" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeometryRef:8 +msgid "The geometry() method is also available as an alias of GetGeometryRef()" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeometryRef:10 osgeo.ogr.Feature.geometry:10 +msgid "the geometry, or None." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:1 +msgid "const char\\* OGR_F_GetNativeData(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:4 +msgid "Returns the native data for the feature." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:6 osgeo.ogr.Feature.SetNativeData:6 +msgid "" +"The native data is the representation in a \"natural\" form that comes " +"from the driver that created this feature, or that is aimed at an output " +"driver. The native data may be in different format, which is indicated by" +" OGR_F_GetNativeMediaType()." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:11 +msgid "" +"Note that most drivers do not support storing the native data in the " +"feature object, and if they do, generally the NATIVE_DATA open option " +"must be passed at dataset opening." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:15 +msgid "" +"The \"native data\" does not imply it is something more performant or " +"powerful than what can be obtained with the rest of the API, but it may " +"be useful in round-tripping scenarios where some characteristics of the " +"underlying format are not captured otherwise by the OGR abstraction." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:21 +msgid "This function is the same as the C++ method OGRFeature::GetNativeData()." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:24 +#: osgeo.ogr.Feature.GetNativeMediaType:14 osgeo.ogr.Feature.SetNativeData:14 +#: osgeo.ogr.Feature.SetNativeMediaType:15 +msgid "See https://trac.osgeo.org/gdal/wiki/rfc60_improved_roundtripping_in_ogr" +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:30 osgeo.ogr.Feature.SetNativeData:19 +msgid "a string with the native data, or NULL if there is none." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeMediaType:1 +msgid "const char\\* OGR_F_GetNativeMediaType(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeMediaType:4 +msgid "Returns the native media type for the feature." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeMediaType:6 +#: osgeo.ogr.Feature.SetNativeMediaType:7 +msgid "" +"The native media type is the identifier for the format of the native " +"data. It follows the IANA RFC 2045 " +"(seehttps://en.wikipedia.org/wiki/Media_type), e.g. " +"\"application/vnd.geo+json\" for JSon." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeMediaType:11 +msgid "This function is the same as the C function OGR_F_GetNativeMediaType()." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeMediaType:20 +#: osgeo.ogr.Feature.SetNativeMediaType:21 +msgid "a string with the native media type, or NULL if there is none." +msgstr "" + +#: of osgeo.ogr.Feature.GetStyleString:1 +msgid "const char\\* OGR_F_GetStyleString(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetStyleString:4 +msgid "Fetch style string for this feature." +msgstr "" + +#: of osgeo.ogr.Feature.GetStyleString:6 +msgid "" +"Set the OGR Feature Style Specification for details on the format of this" +" string, and ogr_featurestyle.h for services available to parse it." +msgstr "" + +#: of osgeo.ogr.Feature.GetStyleString:10 +msgid "This function is the same as the C++ method OGRFeature::GetStyleString()." +msgstr "" + +#: of osgeo.ogr.Feature.GetStyleString:13 +msgid "handle to the feature to get the style from." +msgstr "" + +#: of osgeo.ogr.Feature.GetStyleString:15 +msgid "" +"a reference to a representation in string format, or NULL if there isn't " +"one." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldNull:1 +msgid "int OGR_F_IsFieldNull(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldNull:3 +msgid "Test if a field is null." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldNull:5 +msgid "This function is the same as the C++ method OGRFeature::IsFieldNull()." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldNull:9 osgeo.ogr.Feature.IsFieldSet:7 +#: osgeo.ogr.Feature.IsFieldSetAndNotNull:10 osgeo.ogr.Feature.SetFieldNull:10 +#: osgeo.ogr.Feature.UnsetField:7 +msgid "handle to the feature on which the field is." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldNull:10 osgeo.ogr.Feature.IsFieldSet:8 +#: osgeo.ogr.Feature.IsFieldSetAndNotNull:11 +msgid "the field to test." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldNull:12 +msgid "TRUE if the field is null, otherwise false." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSet:1 +msgid "int OGR_F_IsFieldSet(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSet:3 +msgid "Test if a field has ever been assigned a value or not." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSet:5 +msgid "This function is the same as the C++ method OGRFeature::IsFieldSet()." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSet:10 +msgid "TRUE if the field has been set, otherwise false." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSetAndNotNull:1 +msgid "int OGR_F_IsFieldSetAndNotNull(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSetAndNotNull:3 +msgid "Test if a field is set and not null." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSetAndNotNull:5 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::IsFieldSetAndNotNull()." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSetAndNotNull:13 +msgid "TRUE if the field is set and not null, otherwise false." +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:1 +msgid "OGRErr OGR_F_SetFID(OGRFeatureH hFeat, GIntBig nFID)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:4 +msgid "Set the feature identifier." +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:6 +msgid "" +"For specific types of features this operation may fail on illegal " +"features ids. Generally it always succeeds. Feature ids should be greater" +" than or equal to zero, with the exception of OGRNullFID (-1) indicating " +"that the feature id is unknown." +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:11 +msgid "This function is the same as the C++ method OGRFeature::SetFID()." +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:13 +msgid "handle to the feature to set the feature id to." +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:14 +msgid "the new feature identifier value to assign." +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:16 +msgid "On success OGRERR_NONE, or on failure some other value." +msgstr "" + +#: of osgeo.ogr.Feature.SetField:1 +msgid "SetField(self, int id, int year, int month, int day, int hour, int minute," +msgstr "" + +#: of osgeo.ogr.Feature.SetField:2 +msgid "int second, int tzflag)" +msgstr "" + +#: of osgeo.ogr.Feature.SetField:3 +msgid "SetField(self, char name, int year, int month, int day, int hour," +msgstr "" + +#: of osgeo.ogr.Feature.SetField:4 +msgid "int minute, int second, int tzflag)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:1 +msgid "" +"void OGR_F_SetFieldDoubleList(OGRFeatureH hFeat, int iField, int nCount, " +"const double \\*padfValues)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:5 +msgid "Set field to list of doubles value." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:7 +msgid "" +"This function currently on has an effect of OFTIntegerList, " +"OFTInteger64List, OFTRealList fields." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:10 +#: osgeo.ogr.Feature.SetFieldInteger64:11 +#: osgeo.ogr.Feature.SetFieldInteger64List:10 +#: osgeo.ogr.Feature.SetFieldIntegerList:10 osgeo.ogr.Feature.SetFieldString:13 +#: osgeo.ogr.Feature.SetFieldStringList:9 +msgid "This function is the same as the C++ method OGRFeature::SetField()." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:12 +#: osgeo.ogr.Feature.SetFieldInteger64:13 +#: osgeo.ogr.Feature.SetFieldInteger64List:12 +#: osgeo.ogr.Feature.SetFieldIntegerList:12 osgeo.ogr.Feature.SetFieldString:15 +#: osgeo.ogr.Feature.SetFieldStringList:11 osgeo.ogr.Feature.SetGeometry:11 +#: osgeo.ogr.Feature.SetGeometryDirectly:12 +msgid "" +"This method has only an effect on the in-memory feature object. If this " +"object comes from a layer and the modifications must be serialized back " +"to the datasource, OGR_L_SetFeature() must be used afterwards. Or if this" +" is a new feature, OGR_L_CreateFeature() must be used afterwards." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:19 +#: osgeo.ogr.Feature.SetFieldInteger64List:21 +#: osgeo.ogr.Feature.SetFieldIntegerList:19 +#: osgeo.ogr.Feature.SetFieldStringList:18 +msgid "the field to set, from 0 to GetFieldCount()-1." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:20 +#: osgeo.ogr.Feature.SetFieldInteger64List:22 +#: osgeo.ogr.Feature.SetFieldIntegerList:20 +msgid "the number of values in the list being assigned." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:21 +#: osgeo.ogr.Feature.SetFieldInteger64List:23 +#: osgeo.ogr.Feature.SetFieldIntegerList:21 +msgid "the values to assign." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64:1 +msgid "" +"void OGR_F_SetFieldInteger64(OGRFeatureH hFeat, int iField, GIntBig " +"nValue)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64:4 +msgid "Set field to 64 bit integer value." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64:6 +msgid "" +"OFTInteger, OFTInteger64 and OFTReal fields will be set directly. " +"OFTString fields will be assigned a string representation of the value, " +"but not necessarily taking into account formatting constraints on this " +"field. Other field types may be unaffected." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64:23 +#: osgeo.ogr.Feature.SetFieldString:23 +msgid "the value to assign." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64List:1 +msgid "" +"void OGR_F_SetFieldInteger64List(OGRFeatureH hFeat, int iField, int " +"nCount, const GIntBig \\*panValues)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64List:5 +msgid "Set field to list of 64 bit integers value." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64List:7 +#: osgeo.ogr.Feature.SetFieldIntegerList:7 +msgid "" +"This function currently on has an effect of OFTIntegerList, " +"OFTInteger64List and OFTRealList fields." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldIntegerList:1 +msgid "" +"void OGR_F_SetFieldIntegerList(OGRFeatureH hFeat, int iField, int nCount," +" const int \\*panValues)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldIntegerList:5 +msgid "Set field to list of integers value." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldNull:1 +msgid "void OGR_F_SetFieldNull(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldNull:3 +msgid "Clear a field, marking it as null." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldNull:5 +msgid "This function is the same as the C++ method OGRFeature::SetFieldNull()." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldNull:11 +msgid "the field to set to null." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldString:1 +msgid "" +"void OGR_F_SetFieldString(OGRFeatureH hFeat, int iField, const char " +"\\*pszValue)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldString:5 +msgid "Set field to string value." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldString:7 +msgid "" +"OFTInteger fields will be set based on an atoi() conversion of the " +"string. OFTInteger64 fields will be set based on an CPLAtoGIntBig() " +"conversion of the string. OFTReal fields will be set based on an " +"CPLAtof() conversion of the string. Other field types may be unaffected." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldStringList:1 +msgid "" +"void OGR_F_SetFieldStringList(OGRFeatureH hFeat, int iField, CSLConstList" +" papszValues)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldStringList:5 +msgid "Set field to list of strings value." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldStringList:7 +msgid "This function currently on has an effect of OFTStringList fields." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldStringList:19 +msgid "the values to assign. List of NUL-terminated string," +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:1 +msgid "" +"OGRErr OGR_F_SetFrom(OGRFeatureH hFeat, OGRFeatureH hOtherFeat, int " +"bForgiving)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:4 osgeo.ogr.Feature.SetFromWithMap:5 +msgid "Set one feature from another." +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:6 +msgid "" +"Overwrite the contents of this feature from the geometry and attributes " +"of another. The hOtherFeature does not need to have the same " +"OGRFeatureDefn. Field values are copied by corresponding field names. " +"Field types do not have to exactly match. OGR_F_SetField\\*() function " +"conversion rules will be applied as needed." +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:12 osgeo.ogr.Feature.SetFromWithMap:16 +msgid "This function is the same as the C++ method OGRFeature::SetFrom()." +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:14 osgeo.ogr.Feature.SetFromWithMap:18 +msgid "handle to the feature to set to." +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:15 osgeo.ogr.Feature.SetFromWithMap:19 +msgid "" +"handle to the feature from which geometry, and field values will be " +"copied." +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:17 osgeo.ogr.Feature.SetFromWithMap:26 +msgid "" +"TRUE if the operation should continue despite lacking output fields " +"matching some of the source fields." +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:20 osgeo.ogr.Feature.SetFromWithMap:29 +msgid "" +"OGRERR_NONE if the operation succeeds, even if some values are not " +"transferred, otherwise an error code." +msgstr "" + +#: of osgeo.ogr.Feature.SetFromWithMap:1 +msgid "" +"OGRErr OGR_F_SetFromWithMap(OGRFeatureH hFeat, OGRFeatureH hOtherFeat, " +"int bForgiving, const int \\*panMap)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFromWithMap:7 +msgid "" +"Overwrite the contents of this feature from the geometry and attributes " +"of another. The hOtherFeature does not need to have the same " +"OGRFeatureDefn. Field values are copied according to the provided indices" +" map. Field types do not have to exactly match. OGR_F_SetField\\*() " +"function conversion rules will be applied as needed. This is more " +"efficient than OGR_F_SetFrom() in that this doesn't lookup the fields by " +"their names. Particularly useful when the field names don't match." +msgstr "" + +#: of osgeo.ogr.Feature.SetFromWithMap:21 +msgid "" +"Array of the indices of the destination feature's fields stored at the " +"corresponding index of the source feature's fields. A value of -1 should " +"be used to ignore the source's field. The array should not be NULL and be" +" as long as the number of fields in the source feature." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:1 +msgid "" +"OGRErr OGR_F_SetGeomField(OGRFeatureH hFeat, int iField, OGRGeometryH " +"hGeom)" +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:4 osgeo.ogr.Feature.SetGeomFieldDirectly:3 +msgid "Set feature geometry of a specified geometry field." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:6 osgeo.ogr.Feature.SetGeometry:5 +msgid "" +"This function updates the features geometry, and operate exactly as " +"SetGeometryDirectly(), except that this function does not assume " +"ownership of the passed geometry, but instead makes a copy of it." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:10 +msgid "This function is the same as the C++ OGRFeature::SetGeomField()." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:12 osgeo.ogr.Feature.SetGeometry:17 +msgid "handle to the feature on which new geometry is applied to." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:13 +#: osgeo.ogr.Feature.SetGeomFieldDirectly:15 +msgid "geometry field to set." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:14 +#: osgeo.ogr.Feature.SetGeomFieldDirectly:16 osgeo.ogr.Feature.SetGeometry:18 +#: osgeo.ogr.Feature.SetGeometryDirectly:19 +msgid "handle to the new geometry to apply to feature." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:16 osgeo.ogr.Feature.SetGeometry:20 +#: osgeo.ogr.Feature.SetGeometryDirectly:21 +msgid "" +"OGRERR_NONE if successful, or OGR_UNSUPPORTED_GEOMETRY_TYPE if the " +"geometry type is illegal for the OGRFeatureDefn (checking not yet " +"implemented)." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomFieldDirectly:1 +msgid "" +"OGRErr OGR_F_SetGeomFieldDirectly(OGRFeatureH hFeat, int iField, " +"OGRGeometryH hGeom)" +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomFieldDirectly:5 +msgid "" +"This function updates the features geometry, and operate exactly as " +"SetGeomField(), except that this function assumes ownership of the passed" +" geometry (even in case of failure of that function)." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomFieldDirectly:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::SetGeomFieldDirectly." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomFieldDirectly:14 +#: osgeo.ogr.Feature.SetGeometryDirectly:18 +msgid "handle to the feature on which to apply the geometry." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomFieldDirectly:18 +msgid "" +"OGRERR_NONE if successful, or OGRERR_FAILURE if the index is invalid, or " +"OGR_UNSUPPORTED_GEOMETRY_TYPE if the geometry type is illegal for the " +"OGRFeatureDefn (checking not yet implemented)." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeometry:1 +msgid "OGRErr OGR_F_SetGeometry(OGRFeatureH hFeat, OGRGeometryH hGeom)" +msgstr "" + +#: of osgeo.ogr.Feature.SetGeometry:3 osgeo.ogr.Feature.SetGeometryDirectly:3 +msgid "Set feature geometry." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeometry:9 +msgid "This function is the same as the C++ OGRFeature::SetGeometry()." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeometryDirectly:1 +msgid "OGRErr OGR_F_SetGeometryDirectly(OGRFeatureH hFeat, OGRGeometryH hGeom)" +msgstr "" + +#: of osgeo.ogr.Feature.SetGeometryDirectly:5 +msgid "" +"This function updates the features geometry, and operate exactly as " +"SetGeometry(), except that this function assumes ownership of the passed " +"geometry (even in case of failure of that function)." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeometryDirectly:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::SetGeometryDirectly." +msgstr "" + +#: of osgeo.ogr.Feature.SetNativeData:1 +msgid "void OGR_F_SetNativeData(OGRFeatureH hFeat, const char \\*pszNativeData)" +msgstr "" + +#: of osgeo.ogr.Feature.SetNativeData:4 +msgid "Sets the native data for the feature." +msgstr "" + +#: of osgeo.ogr.Feature.SetNativeData:11 +msgid "This function is the same as the C++ method OGRFeature::SetNativeData()." +msgstr "" + +#: of osgeo.ogr.Feature.SetNativeMediaType:1 +msgid "" +"void OGR_F_SetNativeMediaType(OGRFeatureH hFeat, const char " +"\\*pszNativeMediaType)" +msgstr "" + +#: of osgeo.ogr.Feature.SetNativeMediaType:5 +msgid "Sets the native media type for the feature." +msgstr "" + +#: of osgeo.ogr.Feature.SetNativeMediaType:12 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::SetNativeMediaType()." +msgstr "" + +#: of osgeo.ogr.Feature.SetStyleString:1 +msgid "void OGR_F_SetStyleString(OGRFeatureH hFeat, const char \\*pszStyle)" +msgstr "" + +#: of osgeo.ogr.Feature.SetStyleString:4 +msgid "Set feature style string." +msgstr "" + +#: of osgeo.ogr.Feature.SetStyleString:6 +msgid "" +"This method operate exactly as OGR_F_SetStyleStringDirectly() except that" +" it does not assume ownership of the passed string, but instead makes a " +"copy of it." +msgstr "" + +#: of osgeo.ogr.Feature.SetStyleString:10 +msgid "This function is the same as the C++ method OGRFeature::SetStyleString()." +msgstr "" + +#: of osgeo.ogr.Feature.SetStyleString:13 +msgid "handle to the feature to set style to." +msgstr "" + +#: of osgeo.ogr.Feature.SetStyleString:14 +msgid "the style string to apply to this feature, cannot be NULL." +msgstr "" + +#: of osgeo.ogr.Feature.UnsetField:1 +msgid "void OGR_F_UnsetField(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.UnsetField:3 +msgid "Clear a field, marking it as unset." +msgstr "" + +#: of osgeo.ogr.Feature.UnsetField:5 +msgid "This function is the same as the C++ method OGRFeature::UnsetField()." +msgstr "" + +#: of osgeo.ogr.Feature.UnsetField:8 +msgid "the field to unset." +msgstr "" + +#: of osgeo.ogr.Feature.Validate:1 +msgid "int OGR_F_Validate(OGRFeatureH hFeat, int nValidateFlags, int bEmitError)" +msgstr "" + +#: of osgeo.ogr.Feature.Validate:4 +msgid "Validate that a feature meets constraints of its schema." +msgstr "" + +#: of osgeo.ogr.Feature.Validate:6 +msgid "The scope of test is specified with the nValidateFlags parameter." +msgstr "" + +#: of osgeo.ogr.Feature.Validate:8 +msgid "" +"Regarding OGR_F_VAL_WIDTH, the test is done assuming the string width " +"must be interpreted as the number of UTF-8 characters. Some drivers might" +" interpret the width as the number of bytes instead. So this test is " +"rather conservative (if it fails, then it will fail for all " +"interpretations)." +msgstr "" + +#: of osgeo.ogr.Feature.Validate:14 +msgid "This function is the same as the C++ method OGRFeature::Validate()." +msgstr "" + +#: of osgeo.ogr.Feature.Validate:18 +msgid "handle to the feature to validate." +msgstr "" + +#: of osgeo.ogr.Feature.Validate:19 +msgid "" +"OGR_F_VAL_ALL or combination of OGR_F_VAL_NULL, OGR_F_VAL_GEOM_TYPE, " +"OGR_F_VAL_WIDTH and OGR_F_VAL_ALLOW_NULL_WHEN_DEFAULT with '|' operator" +msgstr "" + +#: of osgeo.ogr.Feature.Validate:22 +msgid "TRUE if a CPLError() must be emitted when a check fails" +msgstr "" + +#: of osgeo.ogr.Feature.Validate:24 +msgid "TRUE if all enabled validation tests pass." +msgstr "" + +#: of osgeo.ogr.Feature.geometry:8 +msgid "The GetGeometryRef() method is also available as an alias of geometry()" +msgstr "" + +#: of osgeo.ogr.Feature.items:1 +msgid "" +"Return a dictionary with the field names as key, and their value in the " +"feature" +msgstr "" + +#: of osgeo.ogr.Feature.keys:1 +msgid "Return the list of field names (of the layer definition)" +msgstr "" + +#: ../../source/api/python/vector_api.rst:40 +msgid "Geometry" +msgstr "" + +#: of osgeo.ogr.Geometry:1 +msgid "Proxy of C++ OGRGeometryShadow class." +msgstr "" + +#: of osgeo.ogr.Geometry.AssignSpatialReference:1 +msgid "Assign spatial reference to this object." +msgstr "" + +#: of osgeo.ogr.Geometry.AssignSpatialReference:3 +msgid "For more details: :cpp:func:`OGR_G_AssignSpatialReference`" +msgstr "" + +#: of osgeo.ogr.Geometry.AssignSpatialReference:5 +msgid "The new spatial reference system to apply." +msgstr "" + +#: of osgeo.ogr.Geometry.Boundary:1 +msgid "Compute boundary." +msgstr "" + +#: of osgeo.ogr.Geometry.Boundary:3 +msgid "For more details: :cpp:func:`OGR_G_Boundary`" +msgstr "" + +#: of osgeo.ogr.Geometry.Boundary:5 osgeo.ogr.Geometry.Polygonize:5 +msgid "A new geometry or None on failure." +msgstr "" + +#: of osgeo.ogr.Geometry.Buffer:1 +msgid "Compute buffer of geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.Buffer:3 +msgid "For more details: :cpp:func:`OGR_G_Buffer`" +msgstr "" + +#: of osgeo.ogr.Geometry.Buffer:5 +msgid "" +"The buffer distance to be applied. Should be expressed into the same unit" +" as the coordinates of the geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.Buffer:8 +msgid "" +"The number of segments used to approximate a 90 degree (quadrant) of " +"curvature." +msgstr "" + +#: of osgeo.ogr.Geometry.Buffer:12 +msgid "The newly created geometry or None if an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.Centroid:1 +msgid "Compute the geometry centroid." +msgstr "" + +#: of osgeo.ogr.Geometry.Centroid:3 +msgid "For more details: :cpp:func:`OGR_G_Centroid`" +msgstr "" + +#: of osgeo.ogr.Geometry.Clone:1 +msgid "Make a copy of this object." +msgstr "" + +#: of osgeo.ogr.Geometry.Clone:3 +msgid "For more details: :cpp:func:`OGR_G_Clone`" +msgstr "" + +#: of osgeo.ogr.Geometry.Clone:5 +msgid "" +"The copy of the geometry with the same spatial reference system as the " +"original." +msgstr "" + +#: of osgeo.ogr.Geometry.CloseRings:1 +msgid "Force rings to be closed." +msgstr "" + +#: of osgeo.ogr.Geometry.CloseRings:3 +msgid "For more details: :cpp:func:`OGR_G_CloseRings`" +msgstr "" + +#: of osgeo.ogr.Geometry.Contains:1 osgeo.ogr.Geometry.Within:1 +msgid "Test for containment." +msgstr "" + +#: of osgeo.ogr.Geometry.Contains:3 +msgid "For more details: :cpp:func:`OGR_G_Contains`" +msgstr "" + +#: of osgeo.ogr.Geometry.Contains:5 osgeo.ogr.Geometry.Crosses:5 +#: osgeo.ogr.Geometry.Overlaps:5 osgeo.ogr.Geometry.Touches:5 +#: osgeo.ogr.Geometry.Within:5 +msgid "the other geometry to compare." +msgstr "" + +#: of osgeo.ogr.Geometry.Contains:8 +msgid "True if this contains the other geometry, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.ConvexHull:1 +msgid "Compute convex hull." +msgstr "" + +#: of osgeo.ogr.Geometry.ConvexHull:3 +msgid "For more details: :cpp:func:`OGR_G_ConvexHull`" +msgstr "" + +#: of osgeo.ogr.Geometry.ConvexHull:5 +msgid "" +"a handle to A newly allocated geometry now owned by the caller, or None " +"on failure." +msgstr "" + +#: of osgeo.ogr.Geometry.CoordinateDimension:1 +#: osgeo.ogr.Geometry.GetCoordinateDimension:1 +msgid "Get the dimension of the coordinates in this geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.CoordinateDimension:3 +msgid "For more details: :cpp:func:`OGR_G_CoordinateDimension`" +msgstr "" + +#: of osgeo.ogr.Geometry.CoordinateDimension:7 +msgid "This will return 2 for XY, 3 for XYZ and XYM, and 4 for XYZM data." +msgstr "" + +#: of osgeo.ogr.Geometry.Crosses:1 +msgid "Test for crossing." +msgstr "" + +#: of osgeo.ogr.Geometry.Crosses:3 +msgid "For more details: :cpp:func:`OGR_G_Crosses`" +msgstr "" + +#: of osgeo.ogr.Geometry.Crosses:8 +msgid "True if they are crossing, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.DelaunayTriangulation:1 +msgid "Return a Delaunay triangulation of the vertices of the geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.DelaunayTriangulation:3 +msgid "For more details: :cpp:func:`OGR_G_DelaunayTriangulation`" +msgstr "" + +#: of osgeo.ogr.Geometry.DelaunayTriangulation:7 +msgid "optional snapping tolerance to use for improved robustness" +msgstr "" + +#: of osgeo.ogr.Geometry.DelaunayTriangulation:9 +msgid "" +"If True, will return a MULTILINESTRING, otherwise it will return a " +"GEOMETRYCOLLECTION containing triangular POLYGONs." +msgstr "" + +#: of osgeo.ogr.Geometry.DelaunayTriangulation:13 +msgid "" +"The geometry resulting from the Delaunay triangulation or None if an " +"error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.Difference:1 +msgid "Compute difference." +msgstr "" + +#: of osgeo.ogr.Geometry.Difference:3 +msgid "For more details: :cpp:func:`OGR_G_Difference`" +msgstr "" + +#: of osgeo.ogr.Geometry.Difference:5 osgeo.ogr.Geometry.Intersection:5 +#: osgeo.ogr.Geometry.Union:5 +msgid "The other geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.Difference:8 +msgid "" +"A new geometry representing the difference or None if the difference is " +"empty or an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.Disjoint:1 +msgid "Test for disjointness." +msgstr "" + +#: of osgeo.ogr.Geometry.Disjoint:3 +msgid "For more details: :cpp:func:`OGR_G_Disjoint`" +msgstr "" + +#: of osgeo.ogr.Geometry.Disjoint:5 +msgid "The other geometry to compare." +msgstr "" + +#: of osgeo.ogr.Geometry.Disjoint:8 +msgid "True if they are disjoint, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.Distance:1 +msgid "Compute distance between two geometries." +msgstr "" + +#: of osgeo.ogr.Geometry.Distance:3 +msgid "For more details: :cpp:func:`OGR_G_Distance`" +msgstr "" + +#: of osgeo.ogr.Geometry.Distance:5 osgeo.ogr.Geometry.Distance3D:7 +msgid "The other geometry to compare against." +msgstr "" + +#: of osgeo.ogr.Geometry.Distance:8 osgeo.ogr.Geometry.Distance3D:10 +msgid "The distance between the geometries or -1 if an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.Distance3D:1 +msgid "Returns the 3D distance between two geometries." +msgstr "" + +#: of osgeo.ogr.Geometry.Distance3D:3 +msgid "For more details: :cpp:func:`OGR_G_Distance3D`" +msgstr "" + +#: of osgeo.ogr.Geometry.Empty:1 +msgid "Clear geometry information." +msgstr "" + +#: of osgeo.ogr.Geometry.Empty:3 +msgid "For more details: :cpp:func:`OGR_G_Empty`" +msgstr "" + +#: of osgeo.ogr.Geometry.Equals:1 +msgid "Returns True if two geometries are equivalent." +msgstr "" + +#: of osgeo.ogr.Geometry.Equals:3 +msgid "For more details: :cpp:func:`OGR_G_Equals`" +msgstr "" + +#: of osgeo.ogr.Geometry.Equals:5 osgeo.ogr.Geometry.Intersects:5 +msgid "The other geometry to test against." +msgstr "" + +#: of osgeo.ogr.Geometry.Equals:8 +msgid "True if equivalent or False otherwise." +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToIsoWkb:1 +msgid "" +"Convert a geometry into SFSQL 1.2 / ISO SQL/MM Part 3 well known binary " +"format." +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToIsoWkb:4 +msgid "For more details: :cpp:func:`OGR_G_ExportToIsoWkb`" +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToIsoWkb:8 osgeo.ogr.Geometry.ExportToWkb:5 +msgid "One of wkbXDR or wkbNDR indicating MSB or LSB byte order respectively." +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToIsoWkt:1 +msgid "" +"Convert a geometry into SFSQL 1.2 / ISO SQL/MM Part 3 well known text " +"format." +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToIsoWkt:4 +msgid "For more details: :cpp:func:`OGR_G_ExportToIsoWkt`" +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToWkb:1 +msgid "Convert a geometry well known binary format." +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToWkb:3 +msgid "For more details: :cpp:func:`OGR_G_ExportToWkb`" +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToWkt:1 +msgid "Convert a geometry into well known text format." +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToWkt:3 +msgid "For more details: :cpp:func:`OGR_G_ExportToWkt`" +msgstr "" + +#: of osgeo.ogr.Geometry.FlattenTo2D:1 +msgid "Convert geometry to strictly 2D." +msgstr "" + +#: of osgeo.ogr.Geometry.FlattenTo2D:3 +msgid "For more details: :cpp:func:`OGR_G_FlattenTo2D`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetBoundary:1 +msgid "Compute boundary (deprecated)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetBoundary:3 +msgid "For more details: :cpp:func:`OGR_G_GetBoundary`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetBoundary:5 +msgid "..warning:: Deprecated" +msgstr "" + +#: of osgeo.ogr.Geometry.GetBoundary:7 +msgid "See: :cpp:func:`OGR_G_Boundary`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetCoordinateDimension:3 +msgid "For more details: :cpp:func:`OGR_G_GetCoordinateDimension`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetCoordinateDimension:5 +msgid "" +"Deprecated. Use :py:func:`CoordinateDimension`, :py:func:`Is3D`, or " +":py:func:`IsMeasured`." +msgstr "" + +#: of osgeo.ogr.Geometry.GetCoordinateDimension:8 +msgid "This will return 2 or 3." +msgstr "" + +#: of osgeo.ogr.Geometry.GetDimension:1 +msgid "Get the dimension of this geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.GetDimension:3 +msgid "For more details: :cpp:func:`OGR_G_GetDimension`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetDimension:5 +msgid "0 for points, 1 for lines, and 2 for surfaces." +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:1 +msgid "" +"Computes and returns the bounding envelope for this geometry in the " +"passed psEnvelope structure." +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:4 +msgid "For more details: :cpp:func:`OGR_G_GetEnvelope`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope3D:1 +msgid "" +"Computes and returns the bounding envelope (3D) for this geometry in the " +"passed psEnvelope structure." +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope3D:4 +msgid "For more details: :cpp:func:`OGR_G_GetEnvelope3D`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope3D:8 +msgid "" +"* **minx** (*float*) * **maxx** (*float*) * **miny** (*float*) * **maxy**" +" (*float*) * **minz** (*float*) * **maxz** (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope3D:12 +msgid "**minz** (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope3D:13 +msgid "**maxz** (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetGeometryName:1 +msgid "Fetch WKT name for geometry type." +msgstr "" + +#: of osgeo.ogr.Geometry.GetGeometryName:3 +msgid "For more details: :cpp:func:`OGR_G_GetGeometryName`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetGeometryName:5 +msgid "geometry to get name from." +msgstr "" + +#: of osgeo.ogr.Geometry.GetGeometryType:1 +msgid "Fetch geometry type." +msgstr "" + +#: of osgeo.ogr.Geometry.GetGeometryType:3 +msgid "For more details: :cpp:func:`OGR_G_GetGeometryType`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetSpatialReference:1 +msgid "For more details: :cpp:func:`OGR_G_GetSpatialReference`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetSpatialReference:3 +msgid "Returns spatial reference system for geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.Intersection:1 +msgid "Compute intersection." +msgstr "" + +#: of osgeo.ogr.Geometry.Intersection:3 +msgid "For more details: :cpp:func:`OGR_G_Intersection`" +msgstr "" + +#: of osgeo.ogr.Geometry.Intersection:8 +msgid "" +"A new geometry representing the intersection or None if there is no " +"intersection or an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.Intersects:1 +msgid "Determines whether two geometries intersect." +msgstr "" + +#: of osgeo.ogr.Geometry.Intersects:3 +msgid "For more details: :cpp:func:`OGR_G_Intersects`" +msgstr "" + +#: of osgeo.ogr.Geometry.Intersects:8 +msgid "True if the geometries intersect, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.Is3D:1 +msgid "See whether this geometry has Z coordinates." +msgstr "" + +#: of osgeo.ogr.Geometry.Is3D:3 +msgid "For more details: :cpp:func:`OGR_G_Is3D`" +msgstr "" + +#: of osgeo.ogr.Geometry.Is3D:7 +msgid "True if the geometry has Z coordinates." +msgstr "" + +#: of osgeo.ogr.Geometry.IsEmpty:1 +msgid "Test if the geometry is empty." +msgstr "" + +#: of osgeo.ogr.Geometry.IsEmpty:3 +msgid "For more details: :cpp:func:`OGR_G_IsEmpty`" +msgstr "" + +#: of osgeo.ogr.Geometry.IsEmpty:5 osgeo.ogr.Geometry.IsRing:5 +#: osgeo.ogr.Geometry.IsValid:5 +msgid "True if the geometry has no points, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.IsMeasured:1 +msgid "See whether this geometry is measured." +msgstr "" + +#: of osgeo.ogr.Geometry.IsMeasured:3 +msgid "For more details: :cpp:func:`OGR_G_IsMeasured`" +msgstr "" + +#: of osgeo.ogr.Geometry.IsMeasured:7 +msgid "True if the geometry has M coordinates." +msgstr "" + +#: of osgeo.ogr.Geometry.IsRing:1 +msgid "Test if the geometry is a ring." +msgstr "" + +#: of osgeo.ogr.Geometry.IsRing:3 +msgid "For more details: :cpp:func:`OGR_G_IsRing`" +msgstr "" + +#: of osgeo.ogr.Geometry.IsSimple:1 +msgid "Returns True if the geometry is simple." +msgstr "" + +#: of osgeo.ogr.Geometry.IsSimple:3 +msgid "For more details: :cpp:func:`OGR_G_IsSimple`" +msgstr "" + +#: of osgeo.ogr.Geometry.IsSimple:5 +msgid "True if object is simple, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.IsValid:1 +msgid "Test if the geometry is valid." +msgstr "" + +#: of osgeo.ogr.Geometry.IsValid:3 +msgid "For more details: :cpp:func:`OGR_G_IsValid`" +msgstr "" + +#: of osgeo.ogr.Geometry.MakeValid:1 +msgid "Attempts to make an invalid geometry valid without losing vertices." +msgstr "" + +#: of osgeo.ogr.Geometry.MakeValid:3 +msgid "For more details: :cpp:func:`OGR_G_MakeValidEx`" +msgstr "" + +#: of osgeo.ogr.Geometry.MakeValid:6 +msgid "options" +msgstr "" + +#: of osgeo.ogr.Geometry.MakeValid:8 +msgid "papszOptions to be passed in. For example: [\"METHOD=STRUCTURE\"]." +msgstr "" + +#: of osgeo.ogr.Geometry.MakeValid:11 osgeo.ogr.Geometry.Normalize:7 +msgid "A newly allocated geometry now owned by the caller, or None on failure." +msgstr "" + +#: of osgeo.ogr.Geometry.Normalize:1 +msgid "Attempts to bring geometry into normalized/canonical form." +msgstr "" + +#: of osgeo.ogr.Geometry.Normalize:3 +msgid "For more details: :cpp:func:`OGR_G_Normalize`" +msgstr "" + +#: of osgeo.ogr.Geometry.Overlaps:1 +msgid "Test for overlap." +msgstr "" + +#: of osgeo.ogr.Geometry.Overlaps:3 +msgid "For more details: :cpp:func:`OGR_G_Overlaps`" +msgstr "" + +#: of osgeo.ogr.Geometry.Overlaps:8 +msgid "True if they are overlapping, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.PointOnSurface:1 +msgid "Returns a point guaranteed to lie on the surface." +msgstr "" + +#: of osgeo.ogr.Geometry.PointOnSurface:3 +msgid "For more details: :cpp:func:`OGR_G_PointOnSurface`" +msgstr "" + +#: of osgeo.ogr.Geometry.PointOnSurface:5 +msgid "A point guaranteed to lie on the surface or None if an error occurred." +msgstr "" + +#: of osgeo.ogr.Geometry.Polygonize:1 +msgid "Polygonizes a set of sparse edges." +msgstr "" + +#: of osgeo.ogr.Geometry.Polygonize:3 +msgid "For more details: :cpp:func:`OGR_G_Polygonize`" +msgstr "" + +#: of osgeo.ogr.Geometry.Segmentize:1 +msgid "Modify the geometry such it has no segment longer then the given distance." +msgstr "" + +#: of osgeo.ogr.Geometry.Segmentize:4 +msgid "For more details: :cpp:func:`OGR_G_Segmentize`" +msgstr "" + +#: of osgeo.ogr.Geometry.Segmentize:6 +msgid "the maximum distance between 2 points after segmentization" +msgstr "" + +#: of osgeo.ogr.Geometry.Set3D:1 +msgid "Add or remove the Z coordinate dimension." +msgstr "" + +#: of osgeo.ogr.Geometry.Set3D:3 +msgid "For more details: :cpp:func:`OGR_G_Set3D`" +msgstr "" + +#: of osgeo.ogr.Geometry.Set3D:7 +msgid "Should the geometry have a Z dimension, either True or False." +msgstr "" + +#: of osgeo.ogr.Geometry.SetCoordinateDimension:1 +msgid "Set the coordinate dimension." +msgstr "" + +#: of osgeo.ogr.Geometry.SetCoordinateDimension:3 +msgid "For more details: :cpp:func:`OGR_G_SetCoordinateDimension`" +msgstr "" + +#: of osgeo.ogr.Geometry.SetCoordinateDimension:5 +msgid "Deprecated. Use :py:func:`Set3D` or :py:func:`SetMeasured`." +msgstr "" + +#: of osgeo.ogr.Geometry.SetCoordinateDimension:7 +msgid "New coordinate dimension value, either 2 or 3." +msgstr "" + +#: of osgeo.ogr.Geometry.SetMeasured:1 +msgid "Add or remove the M coordinate dimension." +msgstr "" + +#: of osgeo.ogr.Geometry.SetMeasured:3 +msgid "For more details: :cpp:func:`OGR_G_SetMeasured`" +msgstr "" + +#: of osgeo.ogr.Geometry.SetMeasured:7 +msgid "Should the geometry have a M dimension, either True or False." +msgstr "" + +#: of osgeo.ogr.Geometry.Simplify:1 +msgid "Compute a simplified geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.Simplify:3 +msgid "For more details: :cpp:func:`OGR_G_Simplify`" +msgstr "" + +#: of osgeo.ogr.Geometry.Simplify:5 +#: osgeo.ogr.Geometry.SimplifyPreserveTopology:5 +msgid "The distance tolerance for the simplification." +msgstr "" + +#: of osgeo.ogr.Geometry.Simplify:8 +#: osgeo.ogr.Geometry.SimplifyPreserveTopology:8 +msgid "The simplified geometry or None if an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.SimplifyPreserveTopology:1 +msgid "Simplify the geometry while preserving topology." +msgstr "" + +#: of osgeo.ogr.Geometry.SimplifyPreserveTopology:3 +msgid "For more details: :cpp:func:`OGR_G_SimplifyPreserveTopology`" +msgstr "" + +#: of osgeo.ogr.Geometry.SwapXY:1 +msgid "Swap x and y coordinates." +msgstr "" + +#: of osgeo.ogr.Geometry.SwapXY:3 +msgid "For more details: :cpp:func:`OGR_G_SwapXY`" +msgstr "" + +#: of osgeo.ogr.Geometry.SymDifference:1 +msgid "Compute symmetric difference." +msgstr "" + +#: of osgeo.ogr.Geometry.SymDifference:3 +msgid "For more details: :cpp:func:`OGR_G_SymDifference`" +msgstr "" + +#: of osgeo.ogr.Geometry.SymDifference:5 +msgid "the other geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.SymDifference:7 +msgid "" +"A new geometry representing the symmetric difference or None if the " +"difference is empty or an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.SymmetricDifference:1 +msgid "Compute symmetric difference (deprecated)" +msgstr "" + +#: of osgeo.ogr.Geometry.SymmetricDifference:3 +msgid "For more details: :cpp:func:`OGR_G_SymmetricDifference`" +msgstr "" + +#: of osgeo.ogr.Geometry.SymmetricDifference:5 +msgid "Deprecated" +msgstr "" + +#: of osgeo.ogr.Geometry.Touches:1 +msgid "Test for touching." +msgstr "" + +#: of osgeo.ogr.Geometry.Touches:3 +msgid "For more details: :cpp:func:`OGR_G_Touches`" +msgstr "" + +#: of osgeo.ogr.Geometry.Touches:7 +msgid "True if they are touching, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.Transform:1 +msgid "Apply arbitrary coordinate transformation to geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.Transform:3 +msgid "For more details: :cpp:func:`OGR_G_Transform`" +msgstr "" + +#: of osgeo.ogr.Geometry.Transform:5 +msgid "The transformation to apply." +msgstr "" + +#: of osgeo.ogr.Geometry.Transform:8 +msgid "The transformed geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.TransformTo:1 +msgid "Transform geometry to new spatial reference system." +msgstr "" + +#: of osgeo.ogr.Geometry.TransformTo:3 +msgid "For more details: :cpp:func:`OGR_G_TransformTo`" +msgstr "" + +#: of osgeo.ogr.Geometry.TransformTo:5 +msgid "The spatial reference system to apply." +msgstr "" + +#: of osgeo.ogr.Geometry.TransformTo:8 +msgid ":py:const:`osgeo.ogr.OGRERR_NONE` on success, or an error code." +msgstr "" + +#: of osgeo.ogr.Geometry.Union:1 +msgid "Compute union." +msgstr "" + +#: of osgeo.ogr.Geometry.Union:3 +msgid "For more details: :cpp:func:`OGR_G_Union`" +msgstr "" + +#: of osgeo.ogr.Geometry.Union:8 osgeo.ogr.Geometry.UnionCascaded:5 +msgid "A new geometry representing the union or None if an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.UnionCascaded:1 +msgid "Compute union using cascading." +msgstr "" + +#: of osgeo.ogr.Geometry.UnionCascaded:3 +msgid "For more deails: :cpp:func:`OGR_G_UnionCascaded`" +msgstr "" + +#: of osgeo.ogr.Geometry.Within:3 +msgid "For more details: :cpp:func:`OGR_G_Within`" +msgstr "" + +#: of osgeo.ogr.Geometry.Within:8 +msgid "True if this is within other, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.WkbSize:1 +msgid "Returns size of related binary representation." +msgstr "" + +#: of osgeo.ogr.Geometry.WkbSize:3 +msgid "For more details: :cpp:func:`OGR_G_WkbSize`" +msgstr "" + +#: ../../source/api/python/vector_api.rst:98 +msgid "FeatureDefn" +msgstr "" + +#: of osgeo.ogr.FeatureDefn:1 +msgid "Proxy of C++ OGRFeatureDefnShadow class." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:1 +msgid "void OGR_FD_AddFieldDefn(OGRFeatureDefnH hDefn, OGRFieldDefnH hNewField)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:4 +#: osgeo.ogr.FeatureDefn.AddGeomFieldDefn:5 +msgid "Add a new field definition to the passed feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:6 +msgid "" +"To add a new field definition to a layer definition, do not use this " +"function directly, but use OGR_L_CreateField() instead." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:9 +msgid "" +"This function should only be called while there are no OGRFeature objects" +" in existence based on this OGRFeatureDefn. The OGRFieldDefn passed in is" +" copied, and remains the responsibility of the caller." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:13 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::AddFieldDefn()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:16 +msgid "handle to the feature definition to add the field definition to." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:17 +#: osgeo.ogr.FeatureDefn.AddGeomFieldDefn:22 +msgid "handle to the new field definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddGeomFieldDefn:1 +msgid "" +"void OGR_FD_AddGeomFieldDefn(OGRFeatureDefnH hDefn, OGRGeomFieldDefnH " +"hNewGeomField)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddGeomFieldDefn:7 +msgid "" +"To add a new field definition to a layer definition, do not use this " +"function directly, but use OGR_L_CreateGeomField() instead." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddGeomFieldDefn:10 +msgid "" +"This function should only be called while there are no OGRFeature objects" +" in existence based on this OGRFeatureDefn. The OGRGeomFieldDefn passed " +"in is copied, and remains the responsibility of the caller." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddGeomFieldDefn:15 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::AddGeomFieldDefn()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddGeomFieldDefn:20 +msgid "handle to the feature definition to add the geometry field definition to." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:1 +msgid "OGRErr OGR_FD_DeleteGeomFieldDefn(OGRFeatureDefnH hDefn, int iGeomField)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:4 +msgid "Delete an existing geometry field definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:6 +msgid "" +"To delete an existing geometry field definition from a layer definition, " +"do not use this function directly, but use OGR_L_DeleteGeomField() " +"instead ( not implemented yet)." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:10 +msgid "" +"This method should only be called while there are no OGRFeature objects " +"in existence based on this OGRFeatureDefn." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:13 +msgid "" +"This method is the same as the C++ method " +"OGRFeatureDefn::DeleteGeomFieldDefn()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:18 +msgid "handle to the feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:19 +msgid "the index of the geometry field definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:21 +msgid "OGRERR_NONE in case of success." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldCount:1 +msgid "int OGR_FD_GetFieldCount(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldCount:4 +msgid "Fetch number of fields on the passed feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldCount:6 +msgid "This function is the same as the C++ OGRFeatureDefn::GetFieldCount()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldCount:8 +#: osgeo.ogr.FeatureDefn.GetGeomFieldCount:11 +msgid "handle to the feature definition to get the fields count from." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldDefn:1 +msgid "OGRFieldDefnH OGR_FD_GetFieldDefn(OGRFeatureDefnH hDefn, int iField)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldDefn:4 +msgid "Fetch field definition of the passed feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldDefn:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::GetFieldDefn()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldDefn:9 +#: osgeo.ogr.FeatureDefn.GetGeomFieldDefn:11 +msgid "handle to the feature definition to get the field definition from." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldDefn:10 +msgid "the field to fetch, between 0 and GetFieldCount()-1." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldDefn:12 +#: osgeo.ogr.FeatureDefn.GetGeomFieldDefn:14 +msgid "" +"a handle to an internal field definition object or NULL if invalid index." +" This object should not be modified or freed by the application." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:1 +msgid "" +"int OGR_FD_GetFieldIndex(OGRFeatureDefnH hDefn, const char " +"\\*pszFieldName)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:4 +msgid "Find field by name." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:6 +msgid "" +"The field index of the first field matching the passed field name (case " +"insensitively) is returned." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:9 +msgid "This function is the same as the C++ method OGRFeatureDefn::GetFieldIndex." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:12 +#: osgeo.ogr.FeatureDefn.GetGeomFieldIndex:13 +msgid "handle to the feature definition to get field index from." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:13 +msgid "the field name to search for." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:15 +msgid "the field index, or -1 if no match found." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldCount:1 +msgid "int OGR_FD_GetGeomFieldCount(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldCount:4 +msgid "Fetch number of geometry fields on the passed feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldCount:6 +msgid "This function is the same as the C++ OGRFeatureDefn::GetGeomFieldCount()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldDefn:1 +msgid "" +"OGRGeomFieldDefnH OGR_FD_GetGeomFieldDefn(OGRFeatureDefnH hDefn, int " +"iGeomField)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldDefn:4 +msgid "Fetch geometry field definition of the passed feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldDefn:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::GetGeomFieldDefn()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldDefn:12 +msgid "the geometry field to fetch, between 0 and GetGeomFieldCount() - 1." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldIndex:1 +msgid "" +"int OGR_FD_GetGeomFieldIndex(OGRFeatureDefnH hDefn, const char " +"\\*pszGeomFieldName)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldIndex:5 +msgid "Find geometry field by name." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldIndex:7 +msgid "" +"The geometry field index of the first geometry field matching the passed " +"field name (case insensitively) is returned." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldIndex:10 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::GetGeomFieldIndex." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldIndex:14 +msgid "the geometry field name to search for." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldIndex:16 +msgid "the geometry field index, or -1 if no match found." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomType:1 +msgid "OGRwkbGeometryType OGR_FD_GetGeomType(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomType:4 +msgid "Fetch the geometry base type of the passed feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomType:6 +msgid "This function is the same as the C++ method OGRFeatureDefn::GetGeomType()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomType:9 +msgid "" +"Starting with GDAL 1.11, this method returns " +"GetGeomFieldDefn(0)->GetType()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomType:12 +msgid "handle to the feature definition to get the geometry type from." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomType:14 +msgid "the base type for all geometry related to this definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetName:1 +msgid "const char\\* OGR_FD_GetName(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetName:4 +msgid "Get name of the OGRFeatureDefn passed as an argument." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetName:6 +msgid "This function is the same as the C++ method OGRFeatureDefn::GetName()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetName:8 +msgid "handle to the feature definition to get the name from." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetName:10 +msgid "the name. This name is internal and should not be modified, or freed." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetReferenceCount:1 +msgid "int OGR_FD_GetReferenceCount(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetReferenceCount:4 +msgid "Fetch current reference count." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetReferenceCount:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::GetReferenceCount()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetReferenceCount:9 +#: osgeo.ogr.FeatureDefn.IsGeometryIgnored:12 osgeo.ogr.FeatureDefn.IsSame:8 +#: osgeo.ogr.FeatureDefn.SetGeometryIgnored:12 +#: osgeo.ogr.FeatureDefn.SetStyleIgnored:9 +msgid "handle to the feature definition on witch OGRFeature are based on." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetReferenceCount:11 +msgid "the current reference count." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsGeometryIgnored:1 +msgid "int OGR_FD_IsGeometryIgnored(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsGeometryIgnored:4 +msgid "Determine whether the geometry can be omitted when fetching features." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsGeometryIgnored:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::IsGeometryIgnored()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsGeometryIgnored:9 +msgid "" +"Starting with GDAL 1.11, this method returns " +"GetGeomFieldDefn(0)->IsIgnored()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsGeometryIgnored:14 +#: osgeo.ogr.FeatureDefn.IsStyleIgnored:11 +#: osgeo.ogr.FeatureDefn.SetGeometryIgnored:13 +#: osgeo.ogr.FeatureDefn.SetStyleIgnored:10 osgeo.ogr.FieldDefn.IsIgnored:10 +#: osgeo.ogr.FieldDefn.SetIgnored:9 +msgid "ignore state" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsSame:1 +msgid "int OGR_FD_IsSame(OGRFeatureDefnH hFDefn, OGRFeatureDefnH hOtherFDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsSame:4 +msgid "Test if the feature definition is identical to the other one." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsSame:9 +msgid "handle to the other feature definition to compare to." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsSame:11 +msgid "TRUE if the feature definition is identical to the other one." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsStyleIgnored:1 +msgid "int OGR_FD_IsStyleIgnored(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsStyleIgnored:4 +msgid "Determine whether the style can be omitted when fetching features." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsStyleIgnored:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::IsStyleIgnored()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsStyleIgnored:9 +msgid "handle to the feature definition on which OGRFeature are based on." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:1 +msgid "void OGR_FD_SetGeomType(OGRFeatureDefnH hDefn, OGRwkbGeometryType eType)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:4 +msgid "" +"Assign the base geometry type for the passed layer (the same as the " +"feature definition)." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:7 +msgid "" +"All geometry objects using this type must be of the defined type or a " +"derived type. The default upon creation is wkbUnknown which allows for " +"any geometry type. The geometry type should generally not be changed " +"after any OGRFeatures have been created against this definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:12 +msgid "This function is the same as the C++ method OGRFeatureDefn::SetGeomType()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:15 +msgid "Starting with GDAL 1.11, this method calls GetGeomFieldDefn(0)->SetType()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:18 +msgid "handle to the layer or feature definition to set the geometry type to." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:19 +msgid "the new type to assign." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeometryIgnored:1 +msgid "void OGR_FD_SetGeometryIgnored(OGRFeatureDefnH hDefn, int bIgnore)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeometryIgnored:4 +msgid "Set whether the geometry can be omitted when fetching features." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeometryIgnored:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::SetGeometryIgnored()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeometryIgnored:9 +msgid "" +"Starting with GDAL 1.11, this method calls " +"GetGeomFieldDefn(0)->SetIgnored()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetStyleIgnored:1 +msgid "void OGR_FD_SetStyleIgnored(OGRFeatureDefnH hDefn, int bIgnore)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetStyleIgnored:4 +msgid "Set whether the style can be omitted when fetching features." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetStyleIgnored:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::SetStyleIgnored()." +msgstr "" + +#: ../../source/api/python/vector_api.rst:106 +msgid "FieldDefn" +msgstr "" + +#: of osgeo.ogr.FieldDefn:1 +msgid "Proxy of C++ OGRFieldDefnShadow class." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:1 +msgid "const char\\* OGR_Fld_GetAlternativeNameRef(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:4 +msgid "Fetch the alternative name (or \"alias\") for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:6 +#: osgeo.ogr.FieldDefn.SetAlternativeName:7 +msgid "" +"The alternative name is an optional attribute for a field which can " +"provide a more user-friendly, descriptive name of a field which is not " +"subject to the usual naming constraints defined by the data provider." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:10 +#: osgeo.ogr.FieldDefn.SetAlternativeName:11 +msgid "" +"This is a metadata style attribute only: the alternative name cannot be " +"used in place of the actual field name during SQL queries or other field " +"name dependent API calls." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:14 +msgid "" +"This function is the same as the CPP method " +"OGRFieldDefn::GetAlternativeNameRef()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:19 +#: osgeo.ogr.FieldDefn.GetDefault:11 osgeo.ogr.FieldDefn.GetNameRef:9 +#: osgeo.ogr.FieldDefn.SetDefault:29 +msgid "handle to the field definition." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:21 +msgid "the alternative name of the field definition." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDefault:1 +msgid "const char\\* OGR_Fld_GetDefault(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDefault:4 +msgid "Get default field value." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDefault:6 +msgid "This function is the same as the C++ method OGRFieldDefn::GetDefault()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDefault:13 +msgid "default field value or NULL." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:1 +msgid "const char\\* OGR_Fld_GetDomainName(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:4 +msgid "Return the name of the field domain for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:6 +msgid "By default, none (empty string) is returned." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:8 +msgid "" +"Field domains ( OGRFieldDomain class) are attached at the GDALDataset " +"level and should be retrieved with GDALDatasetGetFieldDomain()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:11 +msgid "This method is the same as the C++ method OGRFieldDefn::GetDomainName()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:16 +#: osgeo.ogr.FieldDefn.IsDefaultDriverSpecific:16 +#: osgeo.ogr.FieldDefn.IsIgnored:8 osgeo.ogr.FieldDefn.IsNullable:17 +#: osgeo.ogr.FieldDefn.IsUnique:12 osgeo.ogr.FieldDefn.SetDomainName:13 +#: osgeo.ogr.FieldDefn.SetIgnored:8 osgeo.ogr.FieldDefn.SetNullable:16 +#: osgeo.ogr.FieldDefn.SetUnique:17 +msgid "handle to the field definition" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:18 +msgid "the field domain name, or an empty string if there is none." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetJustify:1 +msgid "OGRJustification OGR_Fld_GetJustify(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetJustify:4 osgeo.ogr.FieldDefn.justify:5 +msgid "Get the justification for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetJustify:6 osgeo.ogr.FieldDefn.justify:7 +msgid "This function is the same as the CPP method OGRFieldDefn::GetJustify()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetJustify:9 osgeo.ogr.FieldDefn.SetJustify:6 +#: osgeo.ogr.FieldDefn.justify:10 +msgid "Note: no driver is know to use the concept of field justification." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetJustify:11 osgeo.ogr.FieldDefn.justify:12 +msgid "handle to the field definition to get justification from." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetJustify:13 osgeo.ogr.FieldDefn.justify:14 +msgid "the justification." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetNameRef:1 +msgid "const char\\* OGR_Fld_GetNameRef(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetNameRef:4 +msgid "Fetch name of this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetNameRef:6 +msgid "This function is the same as the CPP method OGRFieldDefn::GetNameRef()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetNameRef:11 +msgid "the name of the field definition." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetPrecision:1 +msgid "int OGR_Fld_GetPrecision(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetPrecision:4 osgeo.ogr.FieldDefn.precision:5 +msgid "Get the formatting precision for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetPrecision:6 osgeo.ogr.FieldDefn.SetPrecision:6 +#: osgeo.ogr.FieldDefn.precision:7 +msgid "This should normally be zero for fields of types other than OFTReal." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetPrecision:8 osgeo.ogr.FieldDefn.precision:9 +msgid "This function is the same as the CPP method OGRFieldDefn::GetPrecision()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetPrecision:11 osgeo.ogr.FieldDefn.precision:12 +msgid "handle to the field definition to get precision from." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetPrecision:13 osgeo.ogr.FieldDefn.precision:14 +msgid "the precision." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetSubType:1 +msgid "OGRFieldSubType OGR_Fld_GetSubType(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetSubType:4 +msgid "Fetch subtype of this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetSubType:6 +msgid "This function is the same as the CPP method OGRFieldDefn::GetSubType()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetSubType:11 +msgid "handle to the field definition to get subtype from." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetSubType:13 +msgid "field subtype." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetType:1 +msgid "OGRFieldType OGR_Fld_GetType(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetType:4 osgeo.ogr.FieldDefn.type:5 +msgid "Fetch type of this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetType:6 osgeo.ogr.FieldDefn.type:7 +msgid "This function is the same as the CPP method OGRFieldDefn::GetType()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetType:8 osgeo.ogr.FieldDefn.type:9 +msgid "handle to the field definition to get type from." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetType:10 osgeo.ogr.FieldDefn.type:11 +msgid "field type." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetWidth:1 +msgid "int OGR_Fld_GetWidth(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetWidth:4 osgeo.ogr.FieldDefn.width:5 +msgid "Get the formatting width for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetWidth:6 osgeo.ogr.FieldDefn.width:7 +msgid "This function is the same as the CPP method OGRFieldDefn::GetWidth()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetWidth:8 osgeo.ogr.FieldDefn.width:9 +msgid "handle to the field definition to get width from." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetWidth:10 osgeo.ogr.FieldDefn.width:11 +msgid "the width, zero means no specified width." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsDefaultDriverSpecific:1 +msgid "int OGR_Fld_IsDefaultDriverSpecific(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsDefaultDriverSpecific:4 +msgid "Returns whether the default value is driver specific." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsDefaultDriverSpecific:6 +msgid "" +"Driver specific default values are those that are not NULL, a numeric " +"value, a literal value enclosed between single quote characters, " +"CURRENT_TIMESTAMP, CURRENT_TIME, CURRENT_DATE or datetime literal value." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsDefaultDriverSpecific:11 +msgid "" +"This function is the same as the C++ method " +"OGRFieldDefn::IsDefaultDriverSpecific()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsDefaultDriverSpecific:18 +msgid "TRUE if the default value is driver specific." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsIgnored:1 +msgid "int OGR_Fld_IsIgnored(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsIgnored:4 +msgid "Return whether this field should be omitted when fetching features." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsIgnored:6 +msgid "This method is the same as the C++ method OGRFieldDefn::IsIgnored()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsNullable:1 +msgid "int OGR_Fld_IsNullable(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsNullable:4 +msgid "Return whether this field can receive null values." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsNullable:6 +msgid "By default, fields are nullable." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsNullable:8 +msgid "" +"Even if this method returns FALSE (i.e not-nullable field), it doesn't " +"mean that OGRFeature::IsFieldSet() will necessary return TRUE, as fields " +"can be temporary unset and null/not-null validation is usually done when " +"OGRLayer::CreateFeature()/SetFeature() is called." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsNullable:13 +msgid "This method is the same as the C++ method OGRFieldDefn::IsNullable()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsNullable:19 +msgid "TRUE if the field is authorized to be null." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsUnique:1 +msgid "int OGR_Fld_IsUnique(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsUnique:4 +msgid "Return whether this field has a unique constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsUnique:6 +msgid "By default, fields have no unique constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsUnique:8 +msgid "This method is the same as the C++ method OGRFieldDefn::IsUnique()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsUnique:14 +msgid "TRUE if the field has a unique constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetAlternativeName:1 +msgid "" +"void OGR_Fld_SetAlternativeName(OGRFieldDefnH hDefn, const char " +"\\*pszAlternativeName)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetAlternativeName:5 +msgid "Reset the alternative name (or \"alias\") for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetAlternativeName:15 +msgid "" +"This function is the same as the CPP method " +"OGRFieldDefn::SetAlternativeName()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetAlternativeName:20 +msgid "handle to the field definition to apply the new alternative name to." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetAlternativeName:21 +msgid "the new alternative name to apply." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:1 +msgid "void OGR_Fld_SetDefault(OGRFieldDefnH hDefn, const char \\*pszDefault)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:4 +msgid "Set default field value." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:6 +msgid "" +"The default field value is taken into account by drivers (generally those" +" with a SQL interface) that support it at field creation time. OGR will " +"generally not automatically set the default field value to null fields by" +" itself when calling OGRFeature::CreateFeature() / " +"OGRFeature::SetFeature(), but will let the low-level layers to do the " +"job. So retrieving the feature from the layer is recommended." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:13 +msgid "" +"The accepted values are NULL, a numeric value, a literal value enclosed " +"between single quote characters (and inner single quote characters " +"escaped by repetition of the single quote character), CURRENT_TIMESTAMP, " +"CURRENT_TIME, CURRENT_DATE or a driver specific expression (that might be" +" ignored by other drivers). For a datetime literal value, format should " +"be 'YYYY/MM/DD HH:MM:SS[.sss]' (considered as UTC time)." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:21 +msgid "" +"Drivers that support writing DEFAULT clauses will advertise the " +"GDAL_DCAP_DEFAULT_FIELDS driver metadata item." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:24 +msgid "This function is the same as the C++ method OGRFieldDefn::SetDefault()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:30 +msgid "new default field value or NULL pointer." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDomainName:1 +msgid "" +"void OGR_Fld_SetDomainName(OGRFieldDefnH hDefn, const char " +"\\*pszFieldName)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDomainName:4 +msgid "Set the name of the field domain for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDomainName:6 +msgid "Field domains ( OGRFieldDomain) are attached at the GDALDataset level." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDomainName:8 +msgid "This method is the same as the C++ method OGRFieldDefn::SetDomainName()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDomainName:14 +msgid "Field domain name." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetIgnored:1 +msgid "void OGR_Fld_SetIgnored(OGRFieldDefnH hDefn, int ignore)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetIgnored:4 +msgid "Set whether this field should be omitted when fetching features." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetIgnored:6 +msgid "This method is the same as the C++ method OGRFieldDefn::SetIgnored()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetJustify:1 +msgid "void OGR_Fld_SetJustify(OGRFieldDefnH hDefn, OGRJustification eJustify)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetJustify:4 +msgid "Set the justification for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetJustify:8 +msgid "This function is the same as the CPP method OGRFieldDefn::SetJustify()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetJustify:11 +msgid "handle to the field definition to set justification to." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetJustify:12 +msgid "the new justification." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetName:1 +msgid "void OGR_Fld_SetName(OGRFieldDefnH hDefn, const char \\*pszName)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetName:4 +msgid "Reset the name of this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetName:6 +msgid "This function is the same as the CPP method OGRFieldDefn::SetName()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetName:8 +msgid "handle to the field definition to apply the new name to." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetName:9 +msgid "the new name to apply." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetNullable:1 +msgid "void OGR_Fld_SetNullable(OGRFieldDefnH hDefn, int bNullableIn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetNullable:4 +msgid "Set whether this field can receive null values." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetNullable:6 +msgid "" +"By default, fields are nullable, so this method is generally called with " +"FALSE to set a not-null constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetNullable:9 +msgid "" +"Drivers that support writing not-null constraint will advertise the " +"GDAL_DCAP_NOTNULL_FIELDS driver metadata item." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetNullable:12 +msgid "This method is the same as the C++ method OGRFieldDefn::SetNullable()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetNullable:17 +msgid "FALSE if the field must have a not-null constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetPrecision:1 +msgid "void OGR_Fld_SetPrecision(OGRFieldDefnH hDefn, int nPrecision)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetPrecision:4 +msgid "Set the formatting precision for this field in characters." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetPrecision:8 +msgid "This function is the same as the CPP method OGRFieldDefn::SetPrecision()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetPrecision:11 +msgid "handle to the field definition to set precision to." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetPrecision:12 +msgid "the new precision." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetSubType:1 +msgid "void OGR_Fld_SetSubType(OGRFieldDefnH hDefn, OGRFieldSubType eSubType)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetSubType:4 +msgid "Set the subtype of this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetSubType:6 osgeo.ogr.FieldDefn.SetType:6 +msgid "" +"This should never be done to an OGRFieldDefn that is already part of an " +"OGRFeatureDefn." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetSubType:9 +msgid "This function is the same as the CPP method OGRFieldDefn::SetSubType()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetSubType:14 osgeo.ogr.FieldDefn.SetType:11 +msgid "handle to the field definition to set type to." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetSubType:15 +msgid "the new field subtype." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetType:1 +msgid "void OGR_Fld_SetType(OGRFieldDefnH hDefn, OGRFieldType eType)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetType:4 +msgid "Set the type of this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetType:9 +msgid "This function is the same as the CPP method OGRFieldDefn::SetType()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetType:12 +msgid "the new field type." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetUnique:1 +msgid "void OGR_Fld_SetUnique(OGRFieldDefnH hDefn, int bUniqueIn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetUnique:4 +msgid "Set whether this field has a unique constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetUnique:6 +msgid "" +"By default, fields have no unique constraint, so this method is generally" +" called with TRUE to set a unique constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetUnique:9 +msgid "" +"Drivers that support writing unique constraint will advertise the " +"GDAL_DCAP_UNIQUE_FIELDS driver metadata item. field can receive null " +"values." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetUnique:13 +msgid "This method is the same as the C++ method OGRFieldDefn::SetUnique()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetUnique:18 +msgid "TRUE if the field must have a unique constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetWidth:1 +msgid "void OGR_Fld_SetWidth(OGRFieldDefnH hDefn, int nNewWidth)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetWidth:4 +msgid "Set the formatting width for this field in characters." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetWidth:6 +msgid "This function is the same as the CPP method OGRFieldDefn::SetWidth()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetWidth:8 +msgid "handle to the field definition to set width to." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetWidth:9 +msgid "the new width." +msgstr "" + +#: of osgeo.ogr.FieldDefn.justify:1 +msgid "" +"GetJustify(FieldDefn self) -> OGRJustification OGRJustification " +"OGR_Fld_GetJustify(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.name:1 +msgid "GetName(FieldDefn self) -> char const *" +msgstr "" + +#: of osgeo.ogr.FieldDefn.precision:1 +msgid "" +"GetPrecision(FieldDefn self) -> int int " +"OGR_Fld_GetPrecision(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.type:1 +msgid "" +"GetType(FieldDefn self) -> OGRFieldType OGRFieldType " +"OGR_Fld_GetType(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.width:1 +msgid "GetWidth(FieldDefn self) -> int int OGR_Fld_GetWidth(OGRFieldDefnH hDefn)" +msgstr "" + +#: ../../source/api/python/vector_api.rst:118 +msgid "GeomFieldDefn" +msgstr "" + +#: of osgeo.ogr.GeomFieldDefn:1 +msgid "Proxy of C++ OGRGeomFieldDefnShadow class." +msgstr "" + +#: of osgeo.ogr.GeomFieldDefn.name:1 +msgid "GetName(GeomFieldDefn self) -> char const *" +msgstr "" + +#: of osgeo.ogr.GeomFieldDefn.srs:1 +msgid "GetSpatialRef(GeomFieldDefn self) -> SpatialReference" +msgstr "" + +#: of osgeo.ogr.GeomFieldDefn.type:1 +msgid "GetType(GeomFieldDefn self) -> OGRwkbGeometryType" +msgstr "" + +#: ../../source/api/python/vector_api.rst:126 +msgid "FieldDomain" +msgstr "" + +#: of osgeo.ogr.FieldDomain:1 +msgid "Proxy of C++ OGRFieldDomainShadow class." +msgstr "" + +#: ../../source/api/python/vector_api.rst:140 +msgid "Relationship" +msgstr "" + +#: of osgeo.gdal.Relationship:1 +msgid "Proxy of C++ GDALRelationshipShadow class." +msgstr "" + +#: ../../source/api/python/vector_api.rst:148 +msgid "StyleTable" +msgstr "" + +#: of osgeo.ogr.StyleTable:1 +msgid "Proxy of C++ OGRStyleTableShadow class." +msgstr "" + +#: ../../source/api/python_bindings.rst:5 +msgid "General information" +msgstr "" + +#: ../../source/api/python_bindings.rst:7 +msgid "" +"This Python package and extensions are a number of tools for programming " +"and manipulating the GDAL_ Geospatial Data Abstraction Library." +msgstr "" + +#: ../../source/api/python_bindings.rst:9 +msgid "" +"The GDAL project maintains SWIG generated Python bindings for GDAL/OGR. " +"Generally speaking the classes and methods mostly match those of the GDAL" +" and OGR C++ classes. There is no Python specific reference " +"documentation, but the :ref:`tutorials ` includes Python " +"examples." +msgstr "" + +#: ../../source/api/python_bindings.rst:15 +msgid "Dependencies" +msgstr "" + +#: ../../source/api/python_bindings.rst:17 +msgid "libgdal and header files (gdal-devel)" +msgstr "" + +#: ../../source/api/python_bindings.rst:18 +msgid "" +"numpy (1.0.0 or greater) and header files (numpy-devel) (not explicitly " +"required, but many examples and utilities will not work without it)" +msgstr "" + +#: ../../source/api/python_bindings.rst:25 +msgid "Conda" +msgstr "" + +#: ../../source/api/python_bindings.rst:27 +msgid "" +"GDAL can be quite complex to build and install, particularly on Windows " +"and MacOS. Pre built binaries are provided for the conda system:" +msgstr "" + +#: ../../source/api/python_bindings.rst:30 +msgid "https://docs.conda.io/en/latest/" +msgstr "" + +#: ../../source/api/python_bindings.rst:32 +msgid "By the conda-forge project:" +msgstr "" + +#: ../../source/api/python_bindings.rst:34 +msgid "https://conda-forge.org/" +msgstr "" + +#: ../../source/api/python_bindings.rst:36 +msgid "" +"Once you have Anaconda or Miniconda installed, you should be able to " +"install GDAL with:" +msgstr "" + +#: ../../source/api/python_bindings.rst:38 +msgid "``conda install -c conda-forge gdal``" +msgstr "" + +#: ../../source/api/python_bindings.rst:41 +msgid "Unix" +msgstr "" + +#: ../../source/api/python_bindings.rst:43 +msgid "The GDAL Python bindings requires setuptools." +msgstr "" + +#: ../../source/api/python_bindings.rst:46 +msgid "pip" +msgstr "" + +#: ../../source/api/python_bindings.rst:48 +msgid "" +"GDAL can be installed from the `Python Package Index " +"`__:" +msgstr "" + +#: ../../source/api/python_bindings.rst:55 +msgid "" +"In order to enable numpy-based raster support, libgdal and its " +"development headers must be installed as well as the Python packages " +"numpy, setuptools, and wheel. To install the Python dependencies and " +"build numpy-based raster support:" +msgstr "" + +#: ../../source/api/python_bindings.rst:65 +msgid "Users can verify that numpy-based raster support has been installed with:" +msgstr "" + +#: ../../source/api/python_bindings.rst:72 +msgid "" +"If this command raises an ImportError, numpy-based raster support has not" +" been properly installed:" +msgstr "" + +#: ../../source/api/python_bindings.rst:83 +msgid "" +"This is most often due to pip reusing a cached GDAL installation. Verify " +"that the necessary dependencies have been installed and then run the " +"following to force a clean build:" +msgstr "" + +#: ../../source/api/python_bindings.rst:92 +msgid "Potential issues with GDAL >= 3.9, Python >= 3.9 and NumPy 2.0" +msgstr "" + +#: ../../source/api/python_bindings.rst:94 +msgid "" +"The pyproject.toml file of GDAL 3.9 requires numpy >= 2.0.0rc1 (for " +"Python >= 3.9) at build time to be able to build bindings that are " +"compatible of both NumPy 1 and NumPy 2. If for some reason the numpy >= " +"2.0.0rc1 build dependency can not be installed, it is possible to " +"manually install the build requirements, and invoke ``pip install`` with " +"the ``--no-build-isolation`` flag." +msgstr "" + +#: ../../source/api/python_bindings.rst:108 +msgid "Building as part of the GDAL library source tree" +msgstr "" + +#: ../../source/api/python_bindings.rst:110 +msgid "" +"Python bindings are generated by default when building GDAL from source. " +"For more detail, see :ref:`building-python-bindings`." +msgstr "" + +#: ../../source/api/python_bindings.rst:113 +msgid "" +"The GDAL Python package is built using `SWIG `__. " +"The currently supported version is SWIG >= 4" +msgstr "" + +#: ../../source/api/python_bindings.rst:120 +msgid "Imports" +msgstr "" + +#: ../../source/api/python_bindings.rst:122 +msgid "" +"There are five major modules that are included with the GDAL_ Python " +"bindings.:" +msgstr "" + +#: ../../source/api/python_bindings.rst:135 +msgid "API documentation is available at :ref:`python_osgeo`" +msgstr "" + +#: ../../source/api/python_bindings.rst:138 +msgid "Numpy" +msgstr "" + +#: ../../source/api/python_bindings.rst:140 +msgid "" +"One advanced feature of the GDAL Python bindings not found in the other " +"language bindings is integration with the Python numerical array " +"facilities. The gdal.Dataset.ReadAsArray() method can be used to read " +"raster data as numerical arrays, ready to use with the Python numerical " +"array capabilities." +msgstr "" + +#: ../../source/api/python_bindings.rst:147 +msgid "Tutorials" +msgstr "" + +#: ../../source/api/python_bindings.rst:149 +msgid "" +"Chris Garrard has given courses at Utah State University on " +"\"Geoprocessing with Python using Open Source GIS\" " +"(`http://www.gis.usu.edu/~chrisg/python " +"`__). There a re many slides, " +"examples, test data... and homework ;-) that can -be greatly helpful for " +"beginners with GDAL/OGR in Python." +msgstr "" + +#: ../../source/api/python_bindings.rst:153 +msgid "" +"A cookbook full of recipes for using the Python GDAL/OGR bindings : " +"`http://pcjericks.github.io/py-gdalogr-cookbook/index.html " +"`__" +msgstr "" + +#: ../../source/api/python_bindings.rst:156 +msgid "Gotchas" +msgstr "" + +#: ../../source/api/python_bindings.rst:158 +msgid "" +"Although GDAL's and OGR's Python bindings provide a fairly \"Pythonic\" " +"wrapper around the underlying C++ code, there are several ways in which " +"the Python bindings differ from typical Python libraries. These " +"differences can catch Python programmers by surprise and lead to " +"unexpected results. These differences result from the complexity of " +"developing a large, long-lived library while continuing to maintain " +"backward compatibility. They are being addressed over time, but until " +"they are all gone, please review this list of :ref:`python_gotchas`." +msgstr "" + +#: ../../source/api/python_bindings.rst:163 +msgid "Examples" +msgstr "" + +#: ../../source/api/python_bindings.rst:165 +msgid "" +"An assortment of other samples are available in the `Python github " +"samples directory `__ with some description in the " +":ref:`python_samples`." +msgstr "" + +#: ../../source/api/python_bindings.rst:167 +msgid "" +"Several `GDAL utilities " +"`__ are implemented in Python and can be useful " +"examples." +msgstr "" + +#: ../../source/api/python_bindings.rst:169 +msgid "" +"The majority of GDAL regression tests are written in Python. They are " +"available at `https://github.com/OSGeo/gdal/tree/master/autotest " +"`__" +msgstr "" + +#: ../../source/api/python_bindings.rst:171 +msgid "" +"Some examples of GDAL/numpy integration can be found is found in the " +"following scripts:" +msgstr "" + +#: ../../source/api/python_bindings.rst:173 +msgid "`gdal_calc.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:174 +msgid "`val_repl.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:175 +msgid "`gdal_merge.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:176 +msgid "`gdal2tiles.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:177 +msgid "`gdal2xyz.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:178 +msgid "`pct2rgb.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:179 +msgid "`gdallocationinfo.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:181 +msgid "" +"One example of GDAL/numpy integration is found in the `val_repl.py " +"`__ script." +msgstr "" + +#: ../../source/api/python_bindings.rst:184 +msgid "**Performance Notes**" +msgstr "" + +#: ../../source/api/python_bindings.rst:186 +msgid "" +"ReadAsArray expects to make an entire copy of a raster band or dataset " +"unless the data are explicitly subsetted as part of the function call. " +"For large data, this approach is expected to be prohibitively memory " +"intensive." +msgstr "" + +#: ../../source/api/python_gotchas.rst:5 +msgid "Python Gotchas in the GDAL and OGR Python Bindings" +msgstr "" + +#: ../../source/api/python_gotchas.rst:7 +msgid "" +"This page lists aspects of GDAL's and OGR's Python bindings that may " +"catch Python programmers by surprise. If you find something new, feel " +"free to open a pull request adding it to the list. Consider discussing it" +" on the `gdal-dev mailing list `__ first, to make sure you fully understand the issue and " +"that others agree that it is unexpected, \"non-Pythonic\", or something " +"that would catch many Python programmers by surprise. Be sure to " +"reference email threads, GitHub tickets, and other sources of additional " +"information." +msgstr "" + +#: ../../source/api/python_gotchas.rst:13 +msgid "" +"This list is not the place to report bugs. If you believe something is a " +"bug, please `open a ticket `__ and " +"report the problem to gdal-dev. Then consider listing it here if it is " +"something related to Python specifically. Do not list it here if it " +"relates to GDAL or OGR generally, and not the Python bindings " +"specifically." +msgstr "" + +#: ../../source/api/python_gotchas.rst:16 +msgid "" +"Not all items listed here are bugs. Some of these are just how GDAL and " +"OGR work and cannot be fixed easily without breaking existing code. If " +"you don't like how something works and think it should be changed, feel " +"free to discuss it on gdal-dev and see what can be done." +msgstr "" + +#: ../../source/api/python_gotchas.rst:21 +msgid "Gotchas that are by design... or per history" +msgstr "" + +#: ../../source/api/python_gotchas.rst:23 +msgid "" +"These are unexpected behaviors that are not considered by the GDAL and " +"OGR teams to be bugs and are unlikely to be changed due to effort " +"required, or whose fixing might affect backward compatibility, etc." +msgstr "" + +#: ../../source/api/python_gotchas.rst:27 +msgid "" +"Python bindings do not raise exceptions unless you explicitly call " +"``UseExceptions()``" +msgstr "" + +#: ../../source/api/python_gotchas.rst:29 +msgid "" +"By default, the GDAL and OGR Python bindings do not raise exceptions when" +" errors occur. Instead they return an error value such as ``None`` and " +"write an error message to ``sys.stdout``. For example, when you try to " +"open a non-existing dataset with GDAL:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:41 +msgid "" +"In Python, it is traditional to report errors by raising exceptions. You " +"can enable this behavior in GDAL and OGR by calling the " +"``UseExceptions()`` function:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:58 +msgid "" +"It is planned that exceptions will be enabled by default in GDAL 4.0. " +"Code that does not want exceptions to be raised in a future version of " +"GDAL should explicitly disable them with ``gdal.DontUseExceptions()``." +msgstr "" + +#: ../../source/api/python_gotchas.rst:62 +msgid "" +"Python crashes or throws an exception if you use an object after deleting" +" a related object" +msgstr "" + +#: ../../source/api/python_gotchas.rst:64 +msgid "Consider this example:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:74 +msgid "" +"In this example, ``band`` has a relationship with ``dataset`` that " +"requires ``dataset`` to remain allocated in order for ``band`` to work. " +"If we delete ``dataset`` and then try to use ``band``, Python will throw " +"a confusing exception:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:88 +msgid "" +"In GDAL 3.7 and earlier, using a band after the dataset has been " +"destroyed will cause a crash instead of an exception." +msgstr "" + +#: ../../source/api/python_gotchas.rst:90 +msgid "" +"This problem can manifest itself in subtle ways. For example, it can " +"occur if you try to instantiate a temporary dataset instance within a " +"single line of code:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:98 +msgid "" +"In this example, the dataset instance was no longer needed after the call" +" to ``GetRasterBand()`` so Python deallocated it *before* calling " +"``Checksum()``." +msgstr "" + +#: ../../source/api/python_gotchas.rst:112 +msgid "" +"This example is the same case as above but it looks different. The " +"dataset object is only available in the ``load_band`` function and will " +"be deleted right after leaving the function." +msgstr "" + +#: ../../source/api/python_gotchas.rst:116 +msgid "" +"The problem is not restricted to GDAL band and dataset objects and " +"happens in other areas where objects have relationships with each other. " +"The issue occurs because deleting an object in Python causes not only the" +" C++ object behind it to be deallocated, but also other objects for which" +" that C++ object maintains ownership (e.g., a Dataset owning a Band, a " +"Feature owning a Geometry.) If the Python object associated with one of " +"these child objects retains a reference to that object, Python will crash" +" when the object is accessed. In common cases such as the Band/Dataset " +"relationship above, the GDAL bindings invalidate references to objects " +"that no longer exist so that an exception is thrown instead of a crash, " +"but the work is not complete." +msgstr "" + +#: ../../source/api/python_gotchas.rst:127 +msgid "" +"Unfortunately there is no complete list of such relationships, so you " +"have to watch for it yourself." +msgstr "" + +#: ../../source/api/python_gotchas.rst:130 +msgid "" +"Python crashes if you add a new field to an OGR layer when features " +"deriving from this layer definition are still active" +msgstr "" + +#: ../../source/api/python_gotchas.rst:132 +msgid "For example:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:142 +msgid "" +"For more information, please see `#3552 " +"`__." +msgstr "" + +#: ../../source/api/python_gotchas.rst:145 +msgid "" +"Layers with attribute filters (``SetAttributeFilter()``) will only return" +" filtered features when using ``GetNextFeature()``" +msgstr "" + +#: ../../source/api/python_gotchas.rst:147 +msgid "" +"If you read the documentation for ``SetAttributeFilter()`` carefully you " +"will see the caveat about ``OGR_L_GetNextFeature()``. This means that if " +"you use ``GetFeature()``, instead of ``GetNextFeature()``, then you can " +"still access and work with features from the layer that are not covered " +"by the filter. ``GetFeatureCount()`` will respect the filter and show the" +" correct number of features filtered. However, working with " +"``GetFeatureCount()`` in a loop can lead to some subtle confusion. " +"Iterating over the Layer object or using ``GetNextFeature()`` should be " +"the default method for accessing features:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:162 +msgid "" +"Certain objects contain a ``Destroy()`` method, but you should never use " +"it" +msgstr "" + +#: ../../source/api/python_gotchas.rst:164 +msgid "" +"You may come across examples that call the ``Destroy()`` method. `This " +"tutorial " +"`__" +" even gives specific advice on page 12 about when to call ``Destroy``." +msgstr "" + +#: ../../source/api/python_gotchas.rst:166 +msgid "" +"Calling ``Destroy`` forces the underlying native object to be destroyed." +" This is typically unnecessary because these objects are automatically " +"destroyed during garbage collection when no references to the Python " +"object remain." +msgstr "" + +#: ../../source/api/python_gotchas.rst:170 +msgid "" +"In most situations, it is not necessary to force the object to be " +"destroyed at a specific point in time. However, because the contents of " +"``gdal.Dataset`` and ``ogr.DataSource`` objects are only guaranteed to be" +" written to disk when the backing native object is destroyed, it may be " +"necessary to explicitly destroy these objects. In these cases, a context " +"manager (``with`` block) is often a good solution, e.g.:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:187 +msgid "" +"If this is not possible, for example if the object needs to be destroyed " +"within a function, then the ``Close()`` method may be called." +msgstr "" + +#: ../../source/api/python_gotchas.rst:192 +msgid "" +"Context managers and the ``Close()`` method are available beginning in " +"GDAL 3.8. In earlier versions, ``Destroy()`` can be used for " +"``ogr.DataSource`` objects, or garbage collection may be forced by " +"destroying reference using ``del`` or setting variables to ``None``." +msgstr "" + +#: ../../source/api/python_gotchas.rst:197 +msgid "" +"With some drivers, raster datasets can be intermittently saved without " +"closing using ``FlushCache()``. Similarly, vector datasets can be saved " +"using ``SyncToDisk()``. However, neither of these methods guarantee that" +" the data are written to disk, so the preferred method is to use a " +"context manager or call ``Close()``." +msgstr "" + +#: ../../source/api/python_gotchas.rst:205 +msgid "Exceptions raised in custom error handlers do not get caught" +msgstr "" + +#: ../../source/api/python_gotchas.rst:207 +msgid "" +"The python bindings allow you to specify a python callable as an error " +"handler (`#4993 `__). However, " +"these error handlers appear to be called in a separate thread and any " +"exceptions raised do not propagate back to the main thread (`#5186 " +"`__)." +msgstr "" + +#: ../../source/api/python_gotchas.rst:210 +msgid "" +"So if you want to `catch warnings as well as errors " +"`__, something like this won't work:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:228 +msgid "But you can do something like this instead:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:283 +msgid "Gotchas that result from bugs or behaviors of other software" +msgstr "" + +#: ../../source/api/python_gotchas.rst:286 +msgid "Python crashes in GDAL functions when you upgrade or downgrade numpy" +msgstr "" + +#: ../../source/api/python_gotchas.rst:288 +msgid "" +"Much of GDAL's Python bindings are implemented in C++. Much of the core " +"of numpy is implemented in C. The C++ part of GDAL's Python bindings " +"interacts with the C part of numpy through numpy's ABI (application " +"binary interface). This requires GDAL's Python bindings to be compiled " +"using numpy header files that define numpy C data structures. Those data " +"structures sometimes change between numpy versions. When this happens, " +"the new version of numpy is not be compatible at the binary level with " +"the old version, and the GDAL Python bindings must be recompiled before " +"they will work with the new version of numpy. And when they are " +"recompiled, they probably won't work with the old version." +msgstr "" + +#: ../../source/api/python_gotchas.rst:292 +msgid "" +"If you obtained a precompiled version of GDAL's Python bindings, such as " +"the Windows packages from `http://gisinternals.com/sdk.php " +"`__ be sure you look up what version of " +"numpy was used to compile them, and install that version of numpy on your" +" machine." +msgstr "" + +#: ../../source/api/python_gotchas.rst:295 +msgid "" +"Python bindings cannot be used successfully from ArcGIS in-process " +"geoprocessing tools (ArcGIS 9.3 and later)" +msgstr "" + +#: ../../source/api/python_gotchas.rst:297 +msgid "" +"ArcGIS allows the creation of custom, Python-based geoprocessing tools. " +"Until ArcGIS 10, there was no easy way to read raster data into memory. " +"GDAL provides such a mechanism." +msgstr "" + +#: ../../source/api/python_gotchas.rst:299 +msgid "" +"Starting with ArcGIS 9.3, geoprocessing tools can either run in the " +"ArcGIS process itself (ArcCatalog.exe or ArcMap.exe) or run in a separate" +" python.exe worker process. Unfortunately ArcGIS contains a bug in how it" +" runs in-process tools. Thus, if you use GDAL from an in-process tool, it" +" will run fine the first time but after that it may fail with " +"``TypeError`` exceptions until you restart the ArcGIS process. For " +"example, band.ReadAsArray() fails with:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:301 +msgid "" +"``TypeError: in method 'BandRasterIONumpy', argument 1 of type " +"'GDALRasterBandShadow *``'" +msgstr "" + +#: ../../source/api/python_gotchas.rst:303 +msgid "" +"This is a bug in ArcGIS. Please see `#3672 " +"`__ for complete details and " +"advice on workarounds." +msgstr "" + +#: ../../source/api/python_samples.rst:5 +msgid "Python Sample scripts" +msgstr "" + +#: ../../source/api/python_samples.rst:7 +msgid "" +"The following are sample scripts intended to give an idea how to use the " +"GDAL's Python interface. Please feel free to use them in your " +"applications." +msgstr "" + +#: ../../source/api/python_samples.rst:10 +msgid "" +"From GDAL 3.2, Python utility scripts :ref:`programs` are located inside " +"the `osgeo_utils` module. From GDAL 3.3, Python sample scripts are " +"located inside the `osgeo_utils.samples` sub-module." +msgstr "" + +#: ../../source/api/python_samples.rst:14 +msgid "Python Raster Sample scripts" +msgstr "" + +#: ../../source/api/python_samples.rst:18 +msgid "" +"assemblepoly: Script demonstrates how to assemble polygons from arcs. " +"Demonstrates various aspects of OGR Python API." +msgstr "" + +#: ../../source/api/python_samples.rst:19 +msgid "" +"fft: Script to perform forward and inverse two-dimensional fast Fourier " +"transform." +msgstr "" + +#: ../../source/api/python_samples.rst:20 +msgid "" +"gdal2grd: Script to write out ASCII GRD rasters (used in Golden Software " +"Surfer). from any source supported by GDAL." +msgstr "" + +#: ../../source/api/python_samples.rst:21 +msgid "gdal_vrtmerge: Similar to gdal_merge, but produces a VRT file." +msgstr "" + +#: ../../source/api/python_samples.rst:22 +msgid "" +"gdalcopyproj: Duplicate the geotransform, projection and/or GCPs from one" +" raster dataset to another, which can be useful after performing image " +"manipulations with other software that ignores or discards georeferencing" +" metadata." +msgstr "" + +#: ../../source/api/python_samples.rst:24 +msgid "" +"gdalfilter: Example script for applying kernel based filters to an image" +" using GDAL. Demonstrates use of virtual files as an intermediate " +"representation." +msgstr "" + +#: ../../source/api/python_samples.rst:26 +msgid "" +"get_soundg: Script to copy the SOUNDG layer from an S-57 file to a " +"Shapefile, splitting up features with MULTIPOINT geometries into many " +"POINT features, and appending the point elevations as an attribute." +msgstr "" + +#: ../../source/api/python_samples.rst:29 +msgid "histrep: Module to extract data from many rasters into one output." +msgstr "" + +#: ../../source/api/python_samples.rst:30 +msgid "" +"load2odbc: Load ODBC table to an ODBC datastore. Uses direct SQL since " +"the ODBC driver is read-only for OGR." +msgstr "" + +#: ../../source/api/python_samples.rst:31 +msgid "" +"rel: Script to produce a shaded relief image from the elevation data. " +"(similar functionality in gdaldem now)" +msgstr "" + +#: ../../source/api/python_samples.rst:32 +msgid "" +"tigerpoly: Script demonstrating how to assemble polygons from arcs in " +"TIGER/Line datasource, writing results to a newly created shapefile." +msgstr "" + +#: ../../source/api/python_samples.rst:34 +msgid "" +"tolatlong: Script to read coordinate system and geotransformation matrix " +"from input file and report latitude/longitude coordinates for the " +"specified pixel." +msgstr "" + +#: ../../source/api/python_samples.rst:36 +msgid "" +"val_repl: Script to replace specified values from the input raster file " +"with the new ones. May be useful in cases when you don't like value, used" +" for NoData indication and want replace it with other value. Input file " +"remains unchanged, results stored in other file." +msgstr "" + +#: ../../source/api/python_samples.rst:39 +msgid "" +"vec_tr: Example of applying some algorithm to all the geometries in the " +"file, such as a fixed offset." +msgstr "" + +#: ../../source/api/python_samples.rst:40 +msgid "" +"vec_tr_spat: Example of using Intersect() to filter based on only those " +"features that truly intersect a given rectangle. Easily extended to " +"general polygon!" +msgstr "" + +#: ../../source/api/python_samples.rst:42 +msgid "" +"classify: Demonstrates using numpy for simple range based classification " +"of an image. This is only an example that has stuff hardcoded." +msgstr "" + +#: ../../source/api/python_samples.rst:44 +msgid "" +"gdal_lut: Read a LUT from a text file, and apply it to an image. Sort of " +"a '1 band' version of pct2rgb." +msgstr "" + +#: ../../source/api/python_samples.rst:46 +msgid "" +"magphase: Example script computing magnitude and phase images from a " +"complex image." +msgstr "" + +#: ../../source/api/python_samples.rst:47 +msgid "hsv_merge: Merge greyscale image into RGB image as intensity in HSV space." +msgstr "" + +#: ../../source/api/python_samples.rst:48 +msgid "" +"gdal_ls: Display the list of files in a virtual directory, like /vsicurl " +"or /vsizip" +msgstr "" + +#: ../../source/api/python_samples.rst:49 +msgid "gdal_cp: Copy a virtual file" +msgstr "" + +#: ../../source/api/python_samples.rst:52 +msgid "Python Vector Sample scripts" +msgstr "" + +#: ../../source/api/python_samples.rst:56 +msgid "" +"ogrupdate: Update a target datasource with the features of a source " +"datasource. Contrary to ogr2ogr, this script tries to match features " +"between the datasources, to decide whether to create a new feature, or to" +" update an existing one." +msgstr "" + +#: ../../source/api/python_samples.rst:59 +msgid "ogr_layer_algebra: Application for executing OGR layer algebra operations." +msgstr "" + +#: ../../source/api/python_samples.rst:60 +msgid "" +"ogr_dispatch: Dispatch features into layers according to the value of " +"some fields or the geometry type." +msgstr "" + +#: ../../source/api/python_samples.rst:61 +msgid "" +"wcs_virtds_params: Generates MapServer WCS layer definition from a " +"tileindex with mixed SRS" +msgstr "" + +#: ../../source/api/python_samples.rst:62 +msgid "" +"ogr_build_junction_table: Create junction tables for layers coming from " +"GML datasources that reference other objects in _href fields" +msgstr "" + +#: ../../source/api/python_samples.rst:64 +msgid "gcps2ogr: Outputs GDAL GCPs as OGR points" +msgstr "" + +#: ../../source/api/python_samples.rst:68 +msgid "Python Coordinate Reference System Sample scripts" +msgstr "" + +#: ../../source/api/python_samples.rst:72 +msgid "" +"crs2crs2grid: A script to produce PROJ.4 grid shift files from HTDP " +"program." +msgstr "" + +#: ../../source/api/python_samples.rst:75 +msgid "Python direct ports of c++ programs" +msgstr "" + +#: ../../source/api/python_samples.rst:79 +msgid ":ref:`gdalinfo`: A direct port of apps/gdalinfo.c" +msgstr "" + +#: ../../source/api/python_samples.rst:80 +msgid ":ref:`ogrinfo`: A direct port of apps/ogrinfo.cpp" +msgstr "" + +#: ../../source/api/python_samples.rst:81 +msgid ":ref:`gdallocationinfo`: A direct port of apps/gdallocationinfo.cpp" +msgstr "" + +#: ../../source/api/python_samples.rst:84 +msgid "Python sample scripts that are now programs" +msgstr "" + +#: ../../source/api/python_samples.rst:86 +msgid "" +"Sample scripts might be upgraded to proper gdal utilities (programs) in " +"next versions with added functionality and documentation. The following " +"samples from previous versions are now programs." +msgstr "" + +#: ../../source/api/python_samples.rst:92 +msgid ":ref:`gdal2xyz`: Translates a raster file into xyz format." +msgstr "" + +#: ../../source/api/python_samples.rst:93 +msgid "" +":ref:`gdal_retile`: Script for restructuring data in a tree of regular " +"tiles." +msgstr "" + +#: ../../source/api/python_samples.rst:94 +msgid "val_at_coord: see :ref:`gdallocationinfo`" +msgstr "" + +#: ../../source/api/raster_c_api.rst:10 +msgid "gdal.h: Raster C API" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param pszFuncName" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param papszFunctionArgs" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param nInBands" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param eInDT" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param padfInNoData" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param pnOutBands" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param peOutDT" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param ppadfOutNoData" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param pszVRTPath" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param ppWorkingData" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param pWorkingData" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param nBufXSize" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param nBufYSize" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param pInBuffer" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param nInBufferSize" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param pOutBuffer" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param nOutBufferSize" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param eOutDT" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param nOutBands" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param padfOutNoData" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param dfSrcXOff" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param dfSrcYOff" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param dfSrcXSize" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param dfSrcYSize" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param adfSrcGT" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param papszExtra" +msgstr "" + +#: ../../source/api/vector_c_api.rst:10 +msgid "ogr_core.h and ogr_api.h: Vector C API" +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/community.po b/doc/source/locale/en/LC_MESSAGES/community.po new file mode 100644 index 000000000000..d92cf003c50e --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/community.po @@ -0,0 +1,691 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: en\n" +"Language-Team: en \n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/community/code_of_conduct.rst:5 +#: ../../source/community/index.rst:16 +msgid "Code of Conduct" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:7 +msgid "" +"This code of conduct governs how we behave in any GDAL forum or event and" +" whenever we will be judged by our actions. We expect it to be honored by" +" everyone who participates in the GDAL community formally or informally, " +"or claims any affiliation with the project." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:13 +msgid "Introduction" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:15 +msgid "" +"This code of conduct governs how we behave in any GDAL forum or event and" +" whenever we will be judged by our actions. We expect it to be honored by" +" everyone who participates in the GDAL community formally or informally, " +"or claims any affiliation with the GDAL project." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:20 +msgid "" +"It applies to in-person events (such as conferences and related social " +"events), IRC, public and private mailing lists, the issue tracker, the " +"wiki, blogs, Twitter, and any other forums which the community uses for " +"communication and interactions." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:25 +msgid "" +"This code is not exhaustive or complete. It serves to distill our common " +"understanding of a collaborative, shared environment and goals. We expect" +" it to be followed in spirit as much as in the letter, so that it can " +"enrich all of us and the technical communities in which we participate." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:31 +msgid "Diversity Statement" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:33 +msgid "" +"GDAL welcomes and encourages participation by everyone. We are committed " +"to being a community that everyone feels good about joining, and we will " +"always work to treat everyone well. No matter how you identify yourself " +"or how others perceive you: we welcome you. Specific Guidelines" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:39 +msgid "We strive to:" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:41 +msgid "Be open." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:43 +msgid "" +"We invite anyone to participate in our community. We preferably use " +"public methods of communication for project-related messages, unless " +"discussing something sensitive. This applies to messages for help or " +"project-related support, too; not only is a public support request much " +"more likely to result in an answer to a question, it also makes sure that" +" any inadvertent mistakes made by people answering will be more easily " +"detected and corrected." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:50 +msgid "Be empathetic, welcoming, friendly, and patient." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:52 +msgid "" +"We work together to resolve conflict, assume good intentions, and do our " +"best to act in an empathetic fashion. We may all experience some " +"frustration from time to time, but we do not allow frustration to turn " +"into a personal attack. A community where people feel uncomfortable or " +"threatened is not a productive one. Note that we have a multi-cultural, " +"multi-lingual community and some of us are non-native speakers. We should" +" be respectful when dealing with other community members as well as with " +"people outside our community." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:60 +msgid "Be collaborative." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:62 +msgid "" +"Our work will be used by other people, and in turn we will depend on the " +"work of others. When we make something for the benefit of GDAL, we are " +"willing to explain to others how it works, so that they can build on the " +"work to make it even better. Any decision we make will affect users and " +"colleagues, and we take those consequences seriously when making " +"decisions." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:68 +msgid "Be inquisitive." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:70 +msgid "" +"Nobody knows everything! Asking questions early avoids many problems " +"later, so questions are encouraged, though they may be directed to the " +"appropriate forum. Those who are asked should be responsive and helpful, " +"within the context of our shared goal of improving GDAL." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:75 +msgid "Be careful in the words that we choose." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:77 +msgid "" +"Whether we are participating as professionals or volunteers, we value " +"professionalism in all interactions, and take responsibility for our own " +"speech. Be kind to others. Do not insult or put down other participants." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:81 +msgid "Be concise." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:83 +msgid "" +"Keep in mind that what you write once will be read by hundreds of " +"persons. Writing a short email means people can understand the " +"conversation as efficiently as possible. Short emails should always " +"strive to be empathetic, welcoming, friendly and patient. When a long " +"explanation is necessary, consider adding a summary." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:89 +msgid "" +"Try to bring new ideas to a conversation so that each mail adds something" +" unique to the thread, keeping in mind that the rest of the thread still " +"contains the other messages with arguments that have already been made." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:93 +msgid "" +"Try to stay on topic, especially in discussions that are already fairly " +"large." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:95 +msgid "Step down considerately." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:97 +msgid "" +"Members of every project come and go. When somebody leaves or disengages " +"from the project they should tell people they are leaving and take the " +"proper steps to ensure that others can pick up where they left off. In " +"doing so, they should remain respectful of those who continue to " +"participate in the project and should not misrepresent the project's " +"goals or achievements. Likewise, community members should respect any " +"individual's choice to leave the project." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:106 +msgid "Anti-Harassment" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:108 +msgid "" +"Harassment and other exclusionary behavior are not acceptable. This " +"includes, but is not limited to:" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:111 +msgid "" +"Personal insults or discriminatory jokes and language, especially those " +"using racist or sexist terms." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:112 +msgid "Offensive comments, excessive or unnecessary profanity." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:113 +msgid "Intimidation, violent threats or demands." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:114 +msgid "Sustained disruption of sessions or events." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:115 +msgid "Stalking, harassing photography or recording." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:116 +msgid "Unwelcome physical contact or sexual attention." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:117 +msgid "" +"Repeated harassment of others. In general, if someone asks you to stop, " +"then stop." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:118 +msgid "" +"Posting (or threatening to post) other people's personally identifying " +"information (\"doxing\")." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:119 +msgid "" +"Sharing private content, such as emails sent privately or non-publicly, " +"or unlogged forums such as IRC channel history." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:120 +msgid "Advocating for, or encouraging, any of the above behavior." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:123 +msgid "Reporting Guidelines" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:125 +msgid "" +"If you believe someone is breaking this code of conduct, you may reply to" +" them, and point to this code of conduct. Such messages may be in public " +"or in private, whatever is most appropriate. Assume good faith; it is " +"more likely that participants are unaware of their bad behavior than that" +" they intentionally try to degrade the quality of the discussion. Should " +"there be difficulties in dealing with the situation, you may report your " +"concerns to event staff, a forum leader or the GDAL Board. Serious or " +"persistent offenders may be expelled from the event or forum by event " +"organizers or forum leaders." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:134 +msgid "" +"To privately email the code of conduct committee leadership use " +"coc@osgeo.org." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:137 +msgid "Credits" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:139 +msgid "" +"GDAL re-uses the `OSGeo Code of Conduct `__" +msgstr "" + +#: ../../source/community/index.rst:5 +msgid "Community" +msgstr "" + +#: ../../source/community/index.rst:7 +msgid "" +"GDAL's community interacts through `Mailing List`_, `GitHub`_, and " +"`Chat`_. Please feel welcome to ask questions and participate in all of " +"the venues. The `Mailing List`_ communication channel is for general " +"questions, development discussion, and feedback. The `GitHub`_ " +"communication channel is for development activities, bug reports, and " +"testing. The `Chat`_ room is for real-time chat activities such as " +"meetings and interactive debugging sessions." +msgstr "" + +#: ../../source/community/index.rst:20 +msgid "" +"GDAL uses a :ref:`code_of_conduct` which governs how we behave in any " +"GDAL forum or event and whenever we will be judged by our actions. We " +"expect it to be honored by everyone who participates in the GDAL " +"community formally or informally, or claims any affiliation with the " +"project." +msgstr "" + +#: ../../source/community/index.rst:32 +msgid "Mailing List" +msgstr "" + +#: ../../source/community/index.rst:34 +msgid "" +"Developers and users of GDAL participate on the GDAL mailing list. It is " +"OK to ask questions about how to use GDAL, how to integrate GDAL into " +"your own software, and report issues that you might have." +msgstr "" + +#: ../../source/community/index.rst:38 +msgid "http://lists.osgeo.org/mailman/listinfo/gdal-dev" +msgstr "" + +#: ../../source/community/index.rst:42 +msgid "GitHub" +msgstr "" + +#: ../../source/community/index.rst:44 +msgid "" +"Visit http://github.com/OSGeo/GDAL to file issues you might be having " +"with the software. GitHub is also where you can obtain a current " +"development version of the software in the `git`_ revision control " +"system. The GDAL project is eager to take contributions in all forms, and" +" we welcome those who are willing to roll up their sleeves and start " +"filing tickets, pushing code, generating builds, and answering questions." +msgstr "" + +#: ../../source/community/index.rst:54 +msgid "Chat" +msgstr "" + +#: ../../source/community/index.rst:56 +msgid "" +"You can find some GDAL developers in the IRC channel #gdal on " +"`Libera.Chat`_. This mechanism is usually reserved for active meetings " +"and other outreach with the community. The `Mailing List`_ and `GitHub`_ " +"avenues are going to be more productive communication channels in most " +"situations." +msgstr "" + +#: ../../source/community/index.rst:67 +msgid "Social media" +msgstr "" + +#: ../../source/community/index.rst:69 +msgid "" +"You can follow GDAL official news on Mastodon: " +"https://mastodon.social/@gdal / @gdal@mastodon.social" +msgstr "" + +#: ../../source/community/index.rst:73 +msgid "Conference" +msgstr "" + +#: ../../source/community/index.rst:-1 +msgid "FOSS4G 2023" +msgstr "" + +#: ../../source/community/index.rst:79 +msgid "" +"`FOSS4G 2023 `_ is the leading annual " +"conference for free and open source geospatial software. It will include " +"presentations related to GDAL/OGR, and some of the GDAL/OGR development " +"community will be attending. It is the event for those interested in " +"GDAL/OGR, other FOSS geospatial technologies and the community around " +"them. The conference will be held at Prizren, Kosovo from June 26th to " +"July 2nd 2023." +msgstr "" + +#: ../../source/community/index.rst:82 +msgid "Governance and Community Participation" +msgstr "" + +#: ../../source/community/index.rst:85 +msgid "OSGeo Project Membership" +msgstr "" + +#: ../../source/community/index.rst:87 +msgid "" +"Originally, GDAL has been lead by Frank Warmerdam, the original author of" +" much of GDAL/OGR, though with contributions and input from a variety of " +"people. As of February 2006 GDAL/OGR became a founding project of the " +"`Open Source Geospatial Foundation (OSGeo) `_ and" +" began a transition to a more community oriented governance model - in " +"keeping with OSGeo expectations." +msgstr "" + +#: ../../source/community/index.rst:94 +msgid "" +"Membership as an OSGeo project provides assurances that a variety of best" +" practices are being employed by the GDAL/OGR project, and that users and" +" contributors can be assured of responsible project operation and " +"continuity of the project. In particular:" +msgstr "" + +#: ../../source/community/index.rst:98 +msgid "" +"A consensus oriented Project Management Committee will be in charge of " +"the project." +msgstr "" + +#: ../../source/community/index.rst:99 +msgid "" +"Project source code and contributions will be vetted to ensure code is " +"properly made available, protecting contributors and users of GDAL/OGR." +msgstr "" + +#: ../../source/community/index.rst:101 +msgid "" +"Part of the systems infrastructure used by the project is provided by the" +" foundation, with responsible backup and redundancy to minimize " +"disruptions." +msgstr "" + +#: ../../source/community/index.rst:107 +msgid "Project Steering Committee" +msgstr "" + +#: ../../source/community/index.rst:109 +msgid "" +"As of April 2006 (following the GDAL/OGR 1.3.2 release) the project has " +"been placed in the hands of a Project Steering Committee. This project " +"steering committee operates under the rules of :ref:`rfc-1`, and is " +"overall responsible for decisions related to the GDAL/OGR project. The " +"current members are (@github username):" +msgstr "" + +#: ../../source/community/index.rst:114 +msgid "Frank Warmerdam (@warmerdam)" +msgstr "" + +#: ../../source/community/index.rst:115 +msgid "Daniel Morissette (@dmorissette)" +msgstr "" + +#: ../../source/community/index.rst:116 +msgid "Howard Butler (@hobu)" +msgstr "" + +#: ../../source/community/index.rst:117 +msgid "Tamas Szekeres (@szekerest)" +msgstr "" + +#: ../../source/community/index.rst:118 +msgid "Even Rouault (chair) (@rouault)" +msgstr "" + +#: ../../source/community/index.rst:119 +msgid "Jukka Rahkonen (@jratike80)" +msgstr "" + +#: ../../source/community/index.rst:120 +msgid "Kurt Schwehr (@schwehr)" +msgstr "" + +#: ../../source/community/index.rst:121 +msgid "Norman Barker (@normanb)" +msgstr "" + +#: ../../source/community/index.rst:122 +msgid "Sean Gillies (@sgillies)" +msgstr "" + +#: ../../source/community/index.rst:123 +msgid "Javier Jimenez Shaw (@jjimenezshaw)" +msgstr "" + +#: ../../source/community/index.rst:125 +msgid "Past members:" +msgstr "" + +#: ../../source/community/index.rst:127 +msgid "Andrey Kiselev (@strezen) (retired in 2019)" +msgstr "" + +#: ../../source/community/index.rst:128 +msgid "Mateusz Łoskot (@mloskot) (retired in 2023)" +msgstr "" + +#: ../../source/community/index.rst:130 +msgid "" +"Note that discussion of proposals to the PSC take place on gdal-dev, and " +"input from all subscribers is welcome. A :ref:`list of past RFC " +"` is available for review." +msgstr "" + +#: ../../source/community/index.rst:135 +#: ../../source/community/service_providers.rst:5 +msgid "GDAL Service Providers" +msgstr "" + +#: ../../source/community/index.rst:139 +msgid "" +"GDAL is developed and supported by a rich ecosystem of businesses and " +"individuals around the world. You can consult a list of " +":ref:`service_providers` who can assist you in getting the best out of " +"your GDAL investment." +msgstr "" + +#: ../../source/community/service_providers.rst:7 +msgid "" +"GDAL is developed and supported by a rich ecosystem of businesses and " +"individuals around the world." +msgstr "" + +#: ../../source/community/service_providers.rst:10 +msgid "" +"In this page we provide a list of service providers who can assist you in" +" getting the best out of your GDAL investment. Their services can range " +"from training and technical support to help you get started, all the way " +"to specialized development and support services to advance the software " +"and support your organization's mission-critical applications." +msgstr "" + +#: ../../source/community/service_providers.rst:20 +msgid "" +"This list is non-exhaustive, and there are quite likely other service " +"providers in your region of the world who are not listed here. If you " +"think your organization should be listed here, please submit a pull " +"request to add it to this page." +msgstr "" + +#: ../../source/community/service_providers.rst:26 +msgid "" +"We take responsibility for the accuracy, reliability or completeness of " +"the provided information for Core Contributors only." +msgstr "" + +#: ../../source/community/service_providers.rst:32 +msgid "Service Providers order is randomized on page load." +msgstr "" + +#: ../../source/community/service_providers.rst:35 +msgid "Core Contributors" +msgstr "" + +#: ../../source/community/service_providers.rst:37 +msgid "" +"Core Contributor organizations have GDAL Committers and/or PSC members as" +" part of their team and as such they are the closest to the core " +"development of the software and are usually the best to go to for " +"support." +msgstr "" + +#: ../../source/community/service_providers.rst:41 +msgid "" +"They are close enough to the architecture to know what is possible, and " +"to ensure that any improvement to be made to GDAL gets done in the right " +"way and will be included in future releases of the software." +msgstr "" + +#: ../../source/community/service_providers.rst:45 +msgid "" +"They wrote the software that you use, so you can trust them to help you " +"get the most out of it." +msgstr "" + +#: ../../source/community/service_providers.rst:50 +msgid "|logo_spatialys|" +msgstr "" + +#: ../../source/community/service_providers.rst +msgid "logo_spatialys" +msgstr "" + +#: ../../source/community/service_providers.rst:54 +msgid "" +"`Spatialys`_ (France) is a company founded by Even Rouault that is " +"dedicated to providing to its clients the best of its expertise around " +"Open Source geospatial software - such as GDAL/OGR, PROJ, MapServer, and " +"QGIS - and Open standards." +msgstr "" + +#: ../../source/community/service_providers.rst:60 +msgid "|logo_hobu|" +msgstr "" + +#: ../../source/community/service_providers.rst +msgid "logo_hobu" +msgstr "" + +#: ../../source/community/service_providers.rst:64 +msgid "" +"`Hobu, Inc.`_ (United States) is a `sam.gov " +"`__-registered company founded by Howard Butler with " +"more than twenty years experience supporting the creation, enhancement, " +"and management of geospatial open source geospatial software such as " +"`PDAL `__, GDAL/OGR, PROJ, and open standards such as " +"`GeoJSON `__, `PROJJSON " +"`__, and `Cloud " +"Optimized Point Cloud `__." +msgstr "" + +#: ../../source/community/service_providers.rst:74 +msgid "Contributors" +msgstr "" + +#: ../../source/community/service_providers.rst:76 +msgid "" +"The Contributors listed here usually have power users and experienced " +"integrators as part of their team who are recognized in the GDAL " +"community for their contributions to various aspects of the software over" +" the years and are very well positioned to assist you with GDAL." +msgstr "" + +#: ../../source/community/service_providers.rst:83 +msgid "None listed yet." +msgstr "" + +#: ../../source/community/service_providers.rst:87 +msgid "Other Service Providers" +msgstr "" + +#: ../../source/community/service_providers.rst:89 +msgid "" +"The service providers in this category offer services around GDAL and " +"related Open Source technologies." +msgstr "" + +#: ../../source/community/service_providers.rst:94 +msgid "|logo_faunalia|" +msgstr "" + +#: ../../source/community/service_providers.rst +msgid "logo_faunalia" +msgstr "" + +#: ../../source/community/service_providers.rst:98 +msgid "" +"`Faunalia`_ (Italy) is a company that operates since more than 15 years " +"in the field of Geographic Information Systems (GIS) based on free and " +"open source software (chiefly QGIS, PostGIS, and more). Our main " +"customers are public administrations, private companies, associations. " +"Faunalia has its main branch in Italy, and operates worldwide. Faunalia " +"provides training services on GDAL." +msgstr "" + +#: ../../source/community/service_providers.rst:102 +msgid "|logo_kartoza|" +msgstr "" + +#: ../../source/community/service_providers.rst +msgid "logo_kartoza" +msgstr "" + +#: ../../source/community/service_providers.rst:106 +msgid "" +"`Kartoza`_ (South Africa) is a South Africa-based Free and Open Source " +"GIS (FOSSGIS) service provider. We use GIS software to solve complex " +"location-related problems for individuals, businesses and governments " +"around the world. Kartoza provides training services on GDAL." +msgstr "" + +#: ../../source/community/service_providers.rst:110 +msgid "|logo_mundialis|" +msgstr "" + +#: ../../source/community/service_providers.rst +msgid "logo_mundialis" +msgstr "" + +#: ../../source/community/service_providers.rst:114 +msgid "" +"`mundialis`_ (Germany) is specialized in the processing of massive " +"geospatial and remote sensing data. Our services centered on the Open " +"Source geospatial systems GRASS GIS, actinia and QGIS are incorporated " +"into our process chains, projects and tailored solutions. We analyse " +"satellite, aerial and drone imagery for land degradation and landuse " +"change. We offer support and training for GRASS GIS and GDAL." +msgstr "" + +#: ../../source/community/service_providers.rst:155 +msgid "" +"Search for GDAL service providers with the `OSGeo Service Providers " +"`__" +msgstr "" + +#: ../../source/community/service_providers.rst:158 +msgid "How to Add a Company" +msgstr "" + +#: ../../source/community/service_providers.rst:160 +msgid "" +"The steps to add a company to the service providers list are outlined in " +"the :ref:`rfc-79` document." +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/contributing.po b/doc/source/locale/en/LC_MESSAGES/contributing.po new file mode 100644 index 000000000000..ba8c2a6e411e --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/contributing.po @@ -0,0 +1,45 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: en\n" +"Language-Team: en \n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/contributing/index.rst:5 +msgid "How to contribute?" +msgstr "" + +#: ../../source/contributing/index.rst:7 +msgid "There are several ways for users to contribute to GDAL:" +msgstr "" + +#: ../../source/contributing/index.rst:9 +msgid ":ref:`contributing code` (bug fixes or enhancements)" +msgstr "" + +#: ../../source/contributing/index.rst:10 +msgid "filing high-quality `bug reports `_" +msgstr "" + +#: ../../source/contributing/index.rst:11 +msgid "improving :ref:`documentation`" +msgstr "" + +#: ../../source/contributing/index.rst:12 +msgid ":ref:`financial sponsorship`" +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/development.po b/doc/source/locale/en/LC_MESSAGES/development.po new file mode 100644 index 000000000000..8f286d4c7076 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/development.po @@ -0,0 +1,31662 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: en\n" +"Language-Team: en \n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/development/building_from_source.rst:5 +msgid "Building GDAL from source" +msgstr "" + +#: ../../source/development/building_from_source.rst:10 +#: ../../source/development/dev_environment.rst:8 +msgid "Build requirements" +msgstr "" + +#: ../../source/development/building_from_source.rst:12 +msgid "The minimum requirements to build GDAL are:" +msgstr "" + +#: ../../source/development/building_from_source.rst:14 +msgid "" +"CMake >= 3.16, and an associated build system (make, ninja, Visual " +"Studio, etc.)" +msgstr "" + +#: ../../source/development/building_from_source.rst:15 +msgid "C99 compiler" +msgstr "" + +#: ../../source/development/building_from_source.rst:16 +msgid "C++17 compiler since GDAL 3.9 (C++11 in previous versions)" +msgstr "" + +#: ../../source/development/building_from_source.rst:17 +msgid "PROJ >= 6.3.1" +msgstr "" + +#: ../../source/development/building_from_source.rst:19 +msgid "Additional requirements to run the GDAL test suite are:" +msgstr "" + +#: ../../source/development/building_from_source.rst:21 +msgid "SWIG >= 4, for building bindings to other programming languages" +msgstr "" + +#: ../../source/development/building_from_source.rst:22 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:25 +msgid "Python >= 3.8" +msgstr "" + +#: ../../source/development/building_from_source.rst:23 +msgid "Python packages listed in `autotest/requirements.txt`" +msgstr "" + +#: ../../source/development/building_from_source.rst:25 +msgid "" +"A number of optional libraries are also strongly recommended for most " +"builds: SQLite3, expat, libcurl, zlib, libtiff, libgeotiff, libpng, " +"libjpeg, etc. Consult :ref:`raster_drivers` and :ref:`vector_drivers` " +"pages for information on dependencies of optional drivers." +msgstr "" + +#: ../../source/development/building_from_source.rst:31 +msgid "CMake (GDAL versions >= 3.5.0)" +msgstr "" + +#: ../../source/development/building_from_source.rst:33 +msgid "" +"Since version 3.5.0, GDAL can be built using the CMake build system. With" +" the CMake build system you can compile and install GDAL on more or less " +"any platform. After unpacking the source distribution archive (or cloning" +" the repository) step into the source tree:" +msgstr "" + +#: ../../source/development/building_from_source.rst:42 +msgid "Create a build directory and step into it:" +msgstr "" + +#: ../../source/development/building_from_source.rst:49 +msgid "" +"From the build directory you can now configure CMake, build and install " +"the binaries:" +msgstr "" + +#: ../../source/development/building_from_source.rst:59 +msgid "" +"For a minimal build, add these options to the initial ``cmake`` command: " +"``-DGDAL_BUILD_OPTIONAL_DRIVERS=OFF -DOGR_BUILD_OPTIONAL_DRIVERS=OFF``. " +"To enable specific drivers, add ``-DGDAL_ENABLE_DRIVER_=ON``" +" or ``-DOGR_ENABLE_DRIVER_=ON``. See :ref:`selection-of-" +"drivers` for more details." +msgstr "" + +#: ../../source/development/building_from_source.rst:65 +msgid "" +"The ``--prefix /installation/prefix`` option of CMake (>= 3.14) is " +"supported since GDAL 3.7.0, but note that contrary to setting the " +"CMAKE_INSTALL_PREFIX at configuration time, it will not result in the " +"GDAL_DATA path to be hardcoded into the libgdal binary, and is thus not " +"recommended. It is also not supported on Windows multi-configuration " +"generator (such as VisualStudio)." +msgstr "" + +#: ../../source/development/building_from_source.rst:72 +msgid "" +"If a dependency is installed in a custom location, specify the paths to " +"the include directory and the library:" +msgstr "" + +#: ../../source/development/building_from_source.rst:79 +msgid "Alternatively, a custom prefix can be specified:" +msgstr "" + +#: ../../source/development/building_from_source.rst:85 +msgid "" +"It is strongly recommended (and sometimes compulsory) to specify paths on" +" Windows using forward slashes as well, e.g.: ``c:/path/to/include``." +msgstr "" + +#: ../../source/development/building_from_source.rst:88 +msgid "" +"You can unset existing cached variables, by using the -U switch of cmake," +" for example with wildcards:" +msgstr "" + +#: ../../source/development/building_from_source.rst:94 +msgid "" +"You can assemble dependency settings in a file ``ConfigUser.cmake`` and " +"use it with the -C option. The file contains set() commands that use the " +"CACHE option. You can set for example a different name for the shared " +"lib, *e.g.* ``set (GDAL_LIB_OUTPUT_NAME gdal_x64 CACHE STRING \"\" " +"FORCE)``:" +msgstr "" + +#: ../../source/development/building_from_source.rst:104 +msgid "" +"When iterating to configure GDAL to add/modify/remove dependencies, some " +"cache variables can remain in CMakeCache.txt from previous runs, and " +"conflict with new settings. If strange errors appear during cmake run, " +"you may try removing CMakeCache.txt to start from a clean state." +msgstr "" + +#: ../../source/development/building_from_source.rst:109 +msgid "" +"Refer to :ref:`using_gdal_in_cmake` for how to use GDAL in a CMake " +"project." +msgstr "" + +#: ../../source/development/building_from_source.rst:112 +msgid "Building on Windows" +msgstr "" + +#: ../../source/development/building_from_source.rst:114 +msgid "On Windows, one may need to specify generator:" +msgstr "" + +#: ../../source/development/building_from_source.rst:122 +msgid "Building on MacOS" +msgstr "" + +#: ../../source/development/building_from_source.rst:124 +msgid "" +"On MacOS, there are a couple of libraries that do not function properly " +"when the GDAL build requirements are installed using Homebrew." +msgstr "" + +#: ../../source/development/building_from_source.rst:126 +msgid "" +"The `Apache Arrow `_ library " +"included in the current distribution of Homebrew is broken, and causes a " +"detection issue. In order to build GDAL successfully, configure CMake to " +"not find the Arrow package:" +msgstr "" + +#: ../../source/development/building_from_source.rst:133 +msgid "" +"Similarly, recent versions of Homebrew no longer bundle `Boost " +"`_ with libkml, causing a failure to find Boost " +"headers. You should either install Boost manually or disable libkml when " +"building on MacOS:" +msgstr "" + +#: ../../source/development/building_from_source.rst:141 +msgid "CMake general configure options" +msgstr "" + +#: ../../source/development/building_from_source.rst:143 +msgid "" +"Options to configure a CMake are provided using ``-D=``. All " +"cached entries can be viewed using ``cmake -LAH`` from a build directory." +msgstr "" + +#: ../../source/development/building_from_source.rst:148 +msgid "Build applications. Default is ON." +msgstr "" + +#: ../../source/development/building_from_source.rst:152 +msgid "" +"Build GDAL library shared. Default is ON. See also the CMake " +"documentation for `BUILD_SHARED_LIBS " +"`_." +msgstr "" + +#: ../../source/development/building_from_source.rst:158 +msgid "" +"Choose the type of build, options are: None (default), Debug, Release, " +"RelWithDebInfo, or MinSizeRel. See also the CMake documentation for " +"`CMAKE_BUILD_TYPE " +"`_." +msgstr "" + +#: ../../source/development/building_from_source.rst:164 +msgid "" +"A default build is not optimized without specifying " +"``-DCMAKE_BUILD_TYPE=Release`` (or similar) during configuration, or by " +"specifying ``--config Release`` with CMake multi-configuration build " +"tools (see example below)." +msgstr "" + +#: ../../source/development/building_from_source.rst:171 +msgid "C compiler. Ignored for some generators, such as Visual Studio." +msgstr "" + +#: ../../source/development/building_from_source.rst:175 +msgid "" +"Flags used by the C compiler during all build types. This is initialized " +"by the :envvar:`CFLAGS` environment variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:180 +msgid "C++ compiler. Ignored for some generators, such as Visual Studio." +msgstr "" + +#: ../../source/development/building_from_source.rst:184 +msgid "" +"Flags used by the C++ compiler during all build types. This is " +"initialized by the :envvar:`CXXFLAGS` environment variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:189 +msgid "Where to install the software. Default for Unix-like is ``/usr/local/``." +msgstr "" + +#: ../../source/development/building_from_source.rst:194 +msgid "" +"List of directories specifying installation prefixes to be searched when " +"external dependencies are looked for." +msgstr "" + +#: ../../source/development/building_from_source.rst:197 +msgid "" +"Starting with CMake 3.12, it is also possible to use a " +"``_ROOT`` variable to define the prefix for a particular " +"package. See " +"https://cmake.org/cmake/help/latest/release/3.12.html?highlight=root#commands" +msgstr "" + +#: ../../source/development/building_from_source.rst:205 +msgid "" +"Default is OFF. This can be set to ON to build GDAL using the " +"https://cmake.org/cmake/help/latest/variable/CMAKE_UNITY_BUILD.html " +"feature. This helps speeding GDAL build times. This feature is still " +"considered experimental for now, and could hide subtle bugs (we are not " +"aware of any at writing time though). We don't recommend it for mission " +"critical builds." +msgstr "" + +#: ../../source/development/building_from_source.rst:214 +msgid "" +"Build library using the compiler's `interprocedural optimization " +"`_ (IPO), if " +"available, default OFF." +msgstr "" + +#: ../../source/development/building_from_source.rst:220 +msgid "" +"Set to ON so that the rpath of installed binaries is written as a " +"relative path to the library. This option overrides the " +"`CMAKE_INSTALL_RPATH " +"`__" +" variable, and assumes that the `CMAKE_SKIP_INSTALL_RPATH " +"`__" +" variable is not set." +msgstr "" + +#: ../../source/development/building_from_source.rst:228 +msgid "CMake package dependent options" +msgstr "" + +#: ../../source/development/building_from_source.rst:232 +msgid "" +"Generally speaking, packages (external dependencies) will be " +"automatically found if they are in default locations used by CMake. This " +"can be also tuned for example with the ``CMAKE_PREFIX_PATH`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:236 +msgid "" +"Starting with CMake 3.12, it is also possible to use a " +"``_ROOT`` variable to define the prefix for a particular " +"package. See " +"https://cmake.org/cmake/help/latest/release/3.12.html?highlight=root#commands" +" Note that the case of the package name matters for the _ROOT, " +"_INCLUDE_DIR and _LIBRARY variables." +msgstr "" + +#: ../../source/development/building_from_source.rst:242 +msgid "" +"Most dependencies that would be found can also be disabled by setting the" +" following option:" +msgstr "" + +#: ../../source/development/building_from_source.rst:247 +msgid "Control whether a found dependency can be used for the GDAL build." +msgstr "" + +#: ../../source/development/building_from_source.rst:249 +msgid "" +"It is also possible to ask GDAL to disable the use of any external " +"dependency (besides the required one, PROJ) by default by setting the " +"following option to OFF. Individual libraries shall then be enabled " +"explicitly with GDAL_USE_:BOOL=ON." +msgstr "" + +#: ../../source/development/building_from_source.rst:256 +msgid "" +"Defaults to ON. When set to OFF, all external dependencies (but mandatory" +" ones) will be disabled, unless individually enabled with " +"GDAL_USE_:BOOL=ON. This option should be set " +"before CMakeCache.txt is created. If it is set to OFF after " +"CMakeCache.txt is created, then cmake should be reinvoked with " +"\"-UGDAL_USE_*\" to cancel the activation of previously detected " +"libraries." +msgstr "" + +#: ../../source/development/building_from_source.rst:263 +msgid "" +"Some of the GDAL dependencies (GEOTIFF, GIF, JPEG, JSONC, LERC, OPENCAD, " +"PNG, QHULL, TIFF, ZLIB) have a copy of their source code inside the GDAL " +"source code tree. It is possible to enable this internal copy by setting " +"the GDAL_USE__INTERNAL:BOOL=ON variable. When " +"set, this has precedence over the external library that may be detected. " +"The behavior can also be globally controlled with the following variable:" +msgstr "" + +#: ../../source/development/building_from_source.rst:271 +msgid "" +"Control how internal libraries should be used. If set to ON, they will " +"always be used. If set to OFF, they will never be used (unless " +"individually enabled with " +"GDAL_USE__INTERNAL:BOOL=ON) If set to " +"WHEN_NO_EXTERNAL (default value), they will be used only if no " +"corresponding external library is found and enabled. This option should " +"be set before CMakeCache.txt is created." +msgstr "" + +#: ../../source/development/building_from_source.rst:282 +msgid "" +"Using together GDAL_USE_EXTERNAL_LIBS=OFF and GDAL_USE_INTERNAL_LIBS=OFF " +"will result in a CMake configuration failure, because the following " +"libraries (either as external dependencies or using the internal copy) " +"are at least required: ZLIB, TIFF, GEOTIFF and JSONC. Enabling them as " +"external or internal libraries is thus required." +msgstr "" + +#: ../../source/development/building_from_source.rst:290 +msgid "Archive" +msgstr "" + +#: ../../source/development/building_from_source.rst:292 +msgid "" +"`libarchive `_ is a library that supports a " +"variety of archive and compression formats. It might be used since GDAL " +"3.7 to enable the :ref:`/vsi7z/ ` virtual file system." +msgstr "" + +#: ../../source/development/building_from_source.rst:298 +msgid "Path to an include directory with the ``archive.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:302 +#: ../../source/development/building_from_source.rst:363 +#: ../../source/development/building_from_source.rst:405 +#: ../../source/development/building_from_source.rst:559 +#: ../../source/development/building_from_source.rst:614 +#: ../../source/development/building_from_source.rst:707 +#: ../../source/development/building_from_source.rst:730 +#: ../../source/development/building_from_source.rst:749 +#: ../../source/development/building_from_source.rst:862 +#: ../../source/development/building_from_source.rst:981 +#: ../../source/development/building_from_source.rst:1006 +#: ../../source/development/building_from_source.rst:1055 +#: ../../source/development/building_from_source.rst:1076 +#: ../../source/development/building_from_source.rst:1100 +#: ../../source/development/building_from_source.rst:1153 +#: ../../source/development/building_from_source.rst:1198 +#: ../../source/development/building_from_source.rst:1387 +#: ../../source/development/building_from_source.rst:1426 +#: ../../source/development/building_from_source.rst:1445 +#: ../../source/development/building_from_source.rst:1464 +#: ../../source/development/building_from_source.rst:1495 +#: ../../source/development/building_from_source.rst:1543 +#: ../../source/development/building_from_source.rst:1638 +#: ../../source/development/building_from_source.rst:1689 +#: ../../source/development/building_from_source.rst:1785 +#: ../../source/development/building_from_source.rst:1817 +#: ../../source/development/building_from_source.rst:1966 +#: ../../source/development/building_from_source.rst:1987 +#: ../../source/development/building_from_source.rst:2038 +msgid "Path to a shared or static library file." +msgstr "" + +#: ../../source/development/building_from_source.rst:306 +msgid "" +"Control whether to use libarchive. Defaults to ON when libarchive is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:310 +msgid "Armadillo" +msgstr "" + +#: ../../source/development/building_from_source.rst:312 +msgid "" +"The `Armadillo `_ C++ library is used to " +"speed up computations related to the Thin Plate Spline transformer. See " +"https://cmake.org/cmake/help/latest/module/FindArmadillo.html for " +"details. On Windows builds using Conda-Forge dependencies, the following " +"packages may also need to be installed: ``blas blas-devel libblas " +"libcblas liblapack liblapacke``" +msgstr "" + +#: ../../source/development/building_from_source.rst:320 +msgid "Control whether to use Armadillo. Defaults to ON when Armadillo is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:324 +msgid "Arrow" +msgstr "" + +#: ../../source/development/building_from_source.rst:326 +msgid "" +"The `Apache Arrow C++ ` " +"library is required for the :ref:`vector.arrow` and :ref:`vector.parquet`" +" drivers. Specify install prefix in the ``CMAKE_PREFIX_PATH`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:332 +msgid "Control whether to use Arrow. Defaults to ON when Arrow is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:336 +msgid "" +"Control whether to use statically built Arrow libraries. Defaults to OFF " +"when Arrow is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:339 +msgid "basisu" +msgstr "" + +#: ../../source/development/building_from_source.rst:341 +msgid "" +"The `Basis Universal " +"` library is " +"required for the :ref:`raster.basisu` and :ref:`raster.ktx2` drivers. " +"Specify install prefix in the ``CMAKE_PREFIX_PATH`` variable or " +"``basisu_ROOT`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:347 +msgid "Control whether to use basisu. Defaults to ON when basisu is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:351 +msgid "Blosc" +msgstr "" + +#: ../../source/development/building_from_source.rst:353 +msgid "" +"`Blosc `_ is a library which offers a " +"meta-compression, with different backends (LZ4, Snappy, Zlib, Zstd, " +"etc.). It is used by the :ref:`raster.zarr` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:359 +msgid "Path to an include directory with the ``blosc.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:367 +msgid "Control whether to use Blosc. Defaults to ON when Blosc is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:371 +msgid "BRUNSLI" +msgstr "" + +#: ../../source/development/building_from_source.rst:373 +msgid "" +"The `Brunsli `_ JPEG repacking " +"library, used by the :ref:`raster.marfa` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:378 +msgid "" +"Path to an include directory with the ``brunsli/decode.h`` and " +"``brunsli\\encode.h`` header files." +msgstr "" + +#: ../../source/development/building_from_source.rst:382 +msgid "Path to the brunslienc-c library file." +msgstr "" + +#: ../../source/development/building_from_source.rst:386 +msgid "Path to the brunslidec-c library file." +msgstr "" + +#: ../../source/development/building_from_source.rst:390 +msgid "Control whether to use BRUNSLI. Defaults to ON when Brunsli is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:394 +msgid "CFITSIO" +msgstr "" + +#: ../../source/development/building_from_source.rst:396 +msgid "" +"The `C FITS I/O `_ library is " +"required for the :ref:`raster.fits` driver. It can be detected with pkg-" +"config." +msgstr "" + +#: ../../source/development/building_from_source.rst:401 +msgid "Path to an include directory with the ``fitsio.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:409 +msgid "Control whether to use CFITSIO. Defaults to ON when CFITSIO is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:413 +msgid "Crnlib" +msgstr "" + +#: ../../source/development/building_from_source.rst:415 +msgid "" +"`Crnlib / crunch `_ " +"is required for the :ref:`raster.dds` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:420 +msgid "Path to Crnlib include directory with ``crunch/crnlib.h`` header." +msgstr "" + +#: ../../source/development/building_from_source.rst:424 +msgid "Path to Crnlib library to be linked." +msgstr "" + +#: ../../source/development/building_from_source.rst:428 +msgid "Control whether to use Crnlib. Defaults to ON when Crnlib is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:432 +msgid "CURL" +msgstr "" + +#: ../../source/development/building_from_source.rst:434 +msgid "" +"`libcurl `_ is required for all network accesses (HTTP," +" etc.)." +msgstr "" + +#: ../../source/development/building_from_source.rst:438 +msgid "Path to an include directory with the ``curl`` directory." +msgstr "" + +#: ../../source/development/building_from_source.rst:442 +msgid "" +"Path to a shared or static library file, such as ``libcurl.so``, " +"``libcurl.lib``, or other name." +msgstr "" + +#: ../../source/development/building_from_source.rst:449 +msgid "Must be set to ON when linking against a static build of Curl." +msgstr "" + +#: ../../source/development/building_from_source.rst:453 +msgid "Control whether to use Curl. Defaults to ON when Curl is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:457 +msgid "CryptoPP" +msgstr "" + +#: ../../source/development/building_from_source.rst:459 +msgid "" +"The `Crypto++ `_ library can be " +"used for the RSA SHA256 signing functionality used by some authentication" +" methods of Google Cloud. It might be required to use the " +":ref:`raster.eedai` images or use the :ref:`/vsigs/ ` virtual file" +" system. It is also required for the :ref:`/vsicrypt/ ` virtual" +" file system." +msgstr "" + +#: ../../source/development/building_from_source.rst:467 +#: ../../source/development/building_from_source.rst:1114 +#: ../../source/development/building_from_source.rst:1194 +#: ../../source/development/building_from_source.rst:1854 +#: ../../source/development/building_from_source.rst:1983 +msgid "Path to the base include directory." +msgstr "" + +#: ../../source/development/building_from_source.rst:471 +msgid "" +"Path to a shared or static library file. A similar variable " +"``CRYPTOPP_LIBRARY_DEBUG`` can also be specified to a similar library for" +" building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:477 +msgid "" +"Defaults to OFF. Might be required to set to ON when linking against " +"cryptopp.dll" +msgstr "" + +#: ../../source/development/building_from_source.rst:482 +msgid "Control whether to use CryptoPP. Defaults to ON when CryptoPP is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:486 +msgid "Deflate" +msgstr "" + +#: ../../source/development/building_from_source.rst:488 +msgid "" +"`libdeflate `_ is a compression " +"library which offers the lossless Deflate/Zip compression algorithm. It " +"offers faster performance than ZLib, but is not a full replacement for " +"it, consequently it must be used as a complement to ZLib." +msgstr "" + +#: ../../source/development/building_from_source.rst:496 +msgid "Path to an include directory with the ``libdeflate.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:500 +msgid "" +"Path to a shared or static library file. A similar variable " +"``Deflate_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:506 +msgid "Control whether to use Deflate. Defaults to ON when Deflate is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:510 +#: ../../source/development/rfc/rfc11_fastidentify.rst:207 +#: ../../source/development/rfc/rfc34_license_policy.rst:175 +msgid "ECW" +msgstr "" + +#: ../../source/development/building_from_source.rst:512 +msgid "" +"The Hexagon ECW SDK (closed source/proprietary) is required for the " +":ref:`raster.ecw` driver. Currently only support for ECW SDK 3.3 and 5.5 " +"is offered." +msgstr "" + +#: ../../source/development/building_from_source.rst:515 +msgid "" +"For ECW SDK 5.5, ECW_ROOT or CMAKE_PREFIX_PATH should point to the " +"directory into which there are include and lib subdirectories, typically " +"ending with ERDAS-ECW_JPEG_2000_SDK-5.5.0/Desktop_Read-Only." +msgstr "" + +#: ../../source/development/building_from_source.rst:521 +msgid "Path to the include directory with the ``NCSECWClient.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:525 +msgid "Path to library file libNCSEcw" +msgstr "" + +#: ../../source/development/building_from_source.rst:529 +msgid "Path to library file libNCSCnet (only needed for SDK 3.3)" +msgstr "" + +#: ../../source/development/building_from_source.rst:533 +msgid "Path to library file libNCSEcwC (only needed for SDK 3.3)" +msgstr "" + +#: ../../source/development/building_from_source.rst:537 +msgid "Path to library file libNCSUtil (only needed for SDK 3.3)" +msgstr "" + +#: ../../source/development/building_from_source.rst:541 +msgid "Control whether to use ECW. Defaults to ON when ECW is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:545 +msgid "EXPAT" +msgstr "" + +#: ../../source/development/building_from_source.rst:547 +msgid "" +"`Expat `_ is a stream-oriented XML " +"parser library which is required to enable XML parsing capabilities in an" +" important number of OGR drivers (GML, GeoRSS, GPX, KML, LVBAG, OSM, ODS," +" SVG, WFS, XSLX, etc.). It is strongly recommended. Other driver such as " +"ILI or GMLAS may also require the XercesC library." +msgstr "" + +#: ../../source/development/building_from_source.rst:555 +msgid "Path to the include directory with the ``expat.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:565 +msgid "Must be set to ON when linking against a static build of Expat." +msgstr "" + +#: ../../source/development/building_from_source.rst:569 +msgid "Control whether to use EXPAT. Defaults to ON when EXPAT is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:573 +#: ../../source/development/rfc/rfc34_license_policy.rst:185 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:113 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:68 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:587 +msgid "FileGDB" +msgstr "" + +#: ../../source/development/building_from_source.rst:575 +msgid "" +"The `FileGDB SDK `_ (closed" +" source/proprietary) is required for the :ref:`vector.filegdb` driver " +"(not to be confused with the :ref:`vector.openfilegdb` driver that has no" +" external requirements)" +msgstr "" + +#: ../../source/development/building_from_source.rst:579 +msgid "" +"FileGDB_ROOT or CMAKE_PREFIX_PATH should point to the directory of the " +"SDK." +msgstr "" + +#: ../../source/development/building_from_source.rst:583 +msgid "Path to the include directory with the ``FileGDBAPI.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:587 +msgid "Path to library file" +msgstr "" + +#: ../../source/development/building_from_source.rst:591 +msgid "Path to Release library file (only used on Windows)" +msgstr "" + +#: ../../source/development/building_from_source.rst:595 +msgid "Path to Debug library file (only used on Windows)" +msgstr "" + +#: ../../source/development/building_from_source.rst:599 +msgid "Control whether to use FileGDB. Defaults to ON when FileGDB is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:603 +msgid "FreeXL" +msgstr "" + +#: ../../source/development/building_from_source.rst:605 +msgid "" +"The `FreeXL `_ library is " +"required for the :ref:`vector.xls` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:610 +msgid "Path to an include directory with the ``freexl.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:618 +msgid "Control whether to use FreeXL. Defaults to ON when FreeXL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:622 +msgid "FYBA" +msgstr "" + +#: ../../source/development/building_from_source.rst:624 +msgid "" +"The `OpenFyba `_ libraries are needed" +" to build the :ref:`vector.sosi` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:628 +msgid "Path to an include directory with the ``fyba.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:632 +msgid "Path to a library file ``fyba``" +msgstr "" + +#: ../../source/development/building_from_source.rst:636 +msgid "Path to a library file ``fygm``" +msgstr "" + +#: ../../source/development/building_from_source.rst:640 +msgid "Path to a library file ``fyut``" +msgstr "" + +#: ../../source/development/building_from_source.rst:644 +msgid "Control whether to use FYBA. Defaults to ON when FYBA is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:648 +msgid "GEOTIFF" +msgstr "" + +#: ../../source/development/building_from_source.rst:650 +msgid "" +"It is required for the :ref:`raster.gtiff` drivers, and a few other " +"drivers. If not found, an internal copy of libgeotiff can be used." +msgstr "" + +#: ../../source/development/building_from_source.rst:655 +msgid "Path to an include directory with the libgeotiff header files." +msgstr "" + +#: ../../source/development/building_from_source.rst:659 +msgid "" +"Path to a shared or static library file, such as ``libgeotiff.so``, " +"``geotiff.lib``, or other name. A similar variable " +"``GEOTIFF_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:666 +msgid "" +"Control whether to use external libgeotiff. Defaults to ON when external " +"libgeotiff is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:670 +msgid "" +"Control whether to use internal libgeotiff copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_GEOTIFF=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:675 +msgid "GEOS" +msgstr "" + +#: ../../source/development/building_from_source.rst:677 +msgid "" +"`GEOS `_ is a C++ library for performing" +" operations on two-dimensional vector geometries. It is used as the " +"backend for most geometry processing operations available in OGR " +"(intersection, buffer, etc.). The ``geos-config`` program can be used to " +"detect it." +msgstr "" + +#: ../../source/development/building_from_source.rst:684 +msgid "Path to an include directory with the ``geos_c.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:688 +msgid "Path to a shared or static library file (libgeos_c)." +msgstr "" + +#: ../../source/development/building_from_source.rst:692 +msgid "Control whether to use GEOS. Defaults to ON when GEOS is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:696 +#: ../../source/development/rfc/rfc11_fastidentify.rst:201 +msgid "GIF" +msgstr "" + +#: ../../source/development/building_from_source.rst:698 +msgid "" +"`giflib `_ is required for the " +":ref:`raster.gif` driver. If not found, an internal copy can be used." +msgstr "" + +#: ../../source/development/building_from_source.rst:703 +msgid "Path to an include directory with the ``gif_lib.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:711 +msgid "" +"Control whether to use external giflib. Defaults to ON when external " +"giflib is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:715 +msgid "" +"Control whether to use internal giflib copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_GIF=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:720 +msgid "GTA" +msgstr "" + +#: ../../source/development/building_from_source.rst:722 +msgid "" +"The `GTA `_ library is required for the " +":ref:`raster.gta` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:726 +msgid "Path to an include directory with the ``gta/gta.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:734 +msgid "Control whether to use GTA. Defaults to ON when GTA is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:738 +msgid "HEIF" +msgstr "" + +#: ../../source/development/building_from_source.rst:740 +msgid "" +"The `HEIF `_ (>= 1.1) library used" +" by the :ref:`raster.heif` driver. It can be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:745 +msgid "Path to an include directory with the ``libheif/heif.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:753 +msgid "Control whether to use HEIF. Defaults to ON when HEIF is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:756 +#: ../../source/development/rfc/rfc11_fastidentify.rst:202 +msgid "HDF4" +msgstr "" + +#: ../../source/development/building_from_source.rst:758 +msgid "" +"The `HDF4 `_ C library is " +"needed for the :ref:`raster.hdf4` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:763 +msgid "Path to an include directory with the ``hdf.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:767 +msgid "" +"Path to a shared or static ``dfalt`` or ``df`` library file. A similar " +"variable ``HDF4_df_LIBRARY_DEBUG`` can also be specified to a similar " +"library for building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:773 +msgid "" +"Path to a shared or static ``mfhdfalt`` or ``mfhdf`` library file. A " +"similar variable ``HDF4_mfhdf_LIBRARY_DEBUG`` can also be specified to a " +"similar library for building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:779 +msgid "" +"Path to a shared or static ``xdr`` library file. A similar variable " +"``HDF4_xdr_LIBRARY_DEBUG`` can also be specified to a similar library for" +" building Debug releases. It is generally not needed for Linux builds" +msgstr "" + +#: ../../source/development/building_from_source.rst:786 +msgid "" +"Path to a shared or static ``szip`` library file. A similar variable " +"``HDF4_szip_LIBRARY_DEBUG`` can also be specified to a similar library " +"for building Debug releases. It is generally not needed for Linux builds" +msgstr "" + +#: ../../source/development/building_from_source.rst:793 +msgid "" +"The value of this option is a list which defaults to " +"``df;mfhdf;xdr;szip``. It may be customized if the linking of HDF4 " +"require different libraries, in which case " +"HDF4_{comp_name}_LIBRARY_[RELEASE/DEBUG] variables will be available to " +"configure the library file." +msgstr "" + +#: ../../source/development/building_from_source.rst:800 +msgid "Control whether to use HDF4. Defaults to ON when HDF4 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:804 +msgid "HDF5" +msgstr "" + +#: ../../source/development/building_from_source.rst:806 +msgid "" +"The `HDF5 `_ C library is needed for " +"the :ref:`raster.hdf5` and :ref:`raster.bag` drivers. The HDF5 CXX " +"library is needed for the :ref:`raster.kea` driver. The " +"https://cmake.org/cmake/help/latest/module/FindHDF5.html module is used " +"to detect the HDF5 library." +msgstr "" + +#: ../../source/development/building_from_source.rst:814 +msgid "Control whether to use HDF5. Defaults to ON when HDF5 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:818 +msgid "" +"Control whether to add a global lock around calls to HDF5 library. This " +"is needed if the HDF5 library is not built with thread-safety enabled and" +" if the HDF5 driver is used in a multi-threaded way. On Unix, a " +"heuristics try to detect if the HDF5 library has been built with thread-" +"safety enabled when linking against a HDF5 library. In other situations, " +"the setting must be manually set when needed." +msgstr "" + +#: ../../source/development/building_from_source.rst:829 +msgid "HDFS" +msgstr "" + +#: ../../source/development/building_from_source.rst:831 +msgid "" +"The `Hadoop File System `_ native library is needed for the" +" :ref:`/vsihdfs/ ` virtual file system." +msgstr "" + +#: ../../source/development/building_from_source.rst:836 +msgid "Path to an include directory with the ``hdfs.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:840 +msgid "Path to a shared or static ``hdfs`` library file." +msgstr "" + +#: ../../source/development/building_from_source.rst:844 +msgid "Control whether to use HDFS. Defaults to ON when HDFS is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:848 +msgid "Iconv" +msgstr "" + +#: ../../source/development/building_from_source.rst:850 +msgid "" +"The `Iconv `_ library is used to " +"convert text from one encoding to another encoding. It is generally " +"available as a system library for Unix-like systems. On Windows, GDAL can" +" leverage the API of the operating system for a few base conversions, but" +" using Iconv will provide additional capabilities." +msgstr "" + +#: ../../source/development/building_from_source.rst:858 +msgid "Path to an include directory with the ``iconv.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:866 +msgid "Control whether to use Iconv. Defaults to ON when Iconv is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:870 +msgid "IDB" +msgstr "" + +#: ../../source/development/building_from_source.rst:872 +msgid "" +"The Informix DataBase Client SDK (closed source/proprietary) is needed " +"to build the :ref:`vector.idb` driver. IDB_ROOT or CMAKE_PREFIX_PATH " +"should point to the directory of the SDK." +msgstr "" + +#: ../../source/development/building_from_source.rst:879 +msgid "" +"Path to an include directory (typically ending with ``incl``) with the " +"``c++/it.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:883 +msgid "" +"Path to a library file ``ifc++`` (typically in the ``lib/c++`` sub " +"directory)" +msgstr "" + +#: ../../source/development/building_from_source.rst:887 +msgid "" +"Path to a library file ``ifdmi`` (typically in the ``lib/dmi`` sub " +"directory)" +msgstr "" + +#: ../../source/development/building_from_source.rst:891 +msgid "" +"Path to a library file ``ifsql`` (typically in the ``lib/esql`` sub " +"directory)" +msgstr "" + +#: ../../source/development/building_from_source.rst:895 +msgid "" +"Path to a library file ``ifcli`` (typically in the ``lib/cli`` sub " +"directory)" +msgstr "" + +#: ../../source/development/building_from_source.rst:899 +msgid "Control whether to use IDB. Defaults to ON when IDB is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:903 +#: ../../source/development/rfc/rfc11_fastidentify.rst:199 +msgid "JPEG" +msgstr "" + +#: ../../source/development/building_from_source.rst:905 +msgid "" +"libjpeg is required for the :ref:`raster.jpeg` driver, and may be used by" +" a few other drivers (:ref:`raster.gpkg`, :ref:`raster.marfa`, internal " +"libtiff, etc.) If not found, an internal copy of libjpeg (6b) can be " +"used. Using `libjpeg-turbo `_ is highly recommended to get best performance. See " +"https://cmake.org/cmake/help/latest/module/FindJPEG.html for more details" +" on how the library is detected." +msgstr "" + +#: ../../source/development/building_from_source.rst:915 +msgid "" +"When using libjpeg-turbo, JPEG_LIBRARY[_RELEASE/_DEBUG] should point to a" +" library with libjpeg ABI, not TurboJPEG. See https://libjpeg-" +"turbo.org/About/TurboJPEG for the difference." +msgstr "" + +#: ../../source/development/building_from_source.rst:921 +msgid "Path to an include directory with the ``jpeglib.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:925 +msgid "" +"Path to a shared or static library file. A similar variable " +"``JPEG_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:931 +msgid "" +"Control whether to use external libjpeg. Defaults to ON when external " +"libjpeg is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:935 +msgid "" +"Control whether to use internal libjpeg copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_JPEG=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:940 +msgid "" +"Used with external libjpeg. number is for example 80, for libjpeg 8 ABI. " +"This can be used to check a build time that the expected JPEG library is " +"the one that is included by GDAL." +msgstr "" + +#: ../../source/development/building_from_source.rst:946 +msgid "JPEG12" +msgstr "" + +#: ../../source/development/building_from_source.rst:948 +msgid "" +"libjpeg-12 bit can be used by the :ref:`raster.jpeg`, :ref:`raster.gtiff`" +" (when using internal libtiff), :ref:`raster.jpeg`, :ref:`raster.marfa` " +"and :ref:`raster.nitf` drivers to handle JPEG images with a 12 bit depth." +" It is only supported with the internal libjpeg (6b). This can be used " +"independently of if for regular 8 bit JPEG an external or internal " +"libjpeg is used." +msgstr "" + +#: ../../source/development/building_from_source.rst:956 +msgid "Control whether to use internal libjpeg-12 copy. Defaults to ON." +msgstr "" + +#: ../../source/development/building_from_source.rst:960 +msgid "" +"Starting with GDAL 3.7, if using libjpeg-turbo >= 2.2, which adds native " +"support for dual 8/12-bit, using internal libjpeg-12 is no longer needed " +"to get 12-bit JPEG support in the JPEG, MRF, NITF or GeoTIFF (when built " +"with internal libtiff) drivers. If using external libtiff, libtiff >= 4.5" +" built against libjpeg-turbo >= 2.2 is needed to get 12-bit JPEG support " +"in the GeoTIFF support." +msgstr "" + +#: ../../source/development/building_from_source.rst:968 +msgid "JSON-C" +msgstr "" + +#: ../../source/development/building_from_source.rst:970 +msgid "" +"The `json-c `_ library is required to " +"read and write JSON content. It can be detected with pkg-config. If not " +"found, an internal copy of json-c can be used." +msgstr "" + +#: ../../source/development/building_from_source.rst:977 +msgid "Path to an include directory with the ``json.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:985 +msgid "Control whether to use JSON-C. Defaults to ON when JSON-C is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:989 +msgid "" +"Control whether to use internal JSON-C copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_JSONC=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:994 +msgid "JXL" +msgstr "" + +#: ../../source/development/building_from_source.rst:996 +msgid "" +"The `libjxl ` library used by the " +":ref:`raster.gtiff` driver, when built against internal libtiff. It can " +"be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:1002 +msgid "Path to an include directory with the ``jxl/decode.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1010 +msgid "Control whether to use JXL. Defaults to ON when JXL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1014 +msgid "KDU" +msgstr "" + +#: ../../source/development/building_from_source.rst:1016 +msgid "" +"The Kakadu library (proprietary) is required for the :ref:`raster.jp2kak`" +" and :ref:`raster.jpipkak` drivers. There is no standardized installation" +" layout, nor fixed library file names, so finding Kakadu artifacts is a " +"bit challenging. Currently automatic finding of it from the KDU_ROOT " +"variable is only implemented for Linux, Mac and Windows x86_64 builds. " +"For other platforms, users need to manually specify the KDU_LIBRARY and " +"KDU_AUX_LIBRARY variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:1026 +msgid "" +"Path to the root of the Kakadu build tree, from which the " +"``coresys/common/kdu_elementary.h`` header file should be found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1031 +msgid "" +"Path to a shared library file whose name is like libkdu_vXYR.so on Unix " +"or kdu_vXYR.lib on Windows, where X.Y is the Kakadu version." +msgstr "" + +#: ../../source/development/building_from_source.rst:1036 +msgid "" +"Path to a shared library file whose name is like libkdu_aXYR.so on Unix " +"or kdu_aXYR.lib on Windows, where X.Y is the Kakadu version." +msgstr "" + +#: ../../source/development/building_from_source.rst:1041 +msgid "Control whether to use KDU. Defaults to ON when KDU is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1044 +msgid "KEA" +msgstr "" + +#: ../../source/development/building_from_source.rst:1046 +msgid "" +"The `KEA `_ library is required for the " +":ref:`raster.kea` driver. The HDF5 CXX library is also required." +msgstr "" + +#: ../../source/development/building_from_source.rst:1051 +msgid "Path to an include directory with the ``libkea/KEACommon.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1059 +msgid "Control whether to use KEA. Defaults to ON when KEA is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1063 +msgid "LERC" +msgstr "" + +#: ../../source/development/building_from_source.rst:1065 +msgid "" +"`LERC `_ is an open-source image or raster " +"format which supports rapid encoding and decoding for any pixel type (not" +" just RGB or Byte). Users set the maximum compression error per pixel " +"while encoding, so the precision of the original input image is preserved" +" (within user defined error bounds)." +msgstr "" + +#: ../../source/development/building_from_source.rst:1072 +msgid "Path to an include directory with the ``Lerc_c_api.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1080 +msgid "Control whether to use LERC. Defaults to ON when LERC is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1084 +msgid "" +"Control whether to use the LERC internal library. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_LERC=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:1088 +msgid "LIBAEC" +msgstr "" + +#: ../../source/development/building_from_source.rst:1090 +msgid "" +"`libaec `_ is a compression " +"library which offers the extended Golomb-Rice coding as defined in the " +"CCSDS recommended standard 121.0-B-3. It is used by the " +":ref:`raster.grib` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1096 +msgid "Path to an include directory with the ``libaec.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1104 +msgid "Control whether to use LIBAEC. Defaults to ON when LIBAEC is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1107 +msgid "LibKML" +msgstr "" + +#: ../../source/development/building_from_source.rst:1109 +msgid "" +"`LibKML `_ is required for the " +":ref:`vector.libkml` driver. It can be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:1118 +msgid "Path to a shared or static library file for ``kmlbase``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1122 +msgid "Path to a shared or static library file for ``kmldom``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1126 +msgid "Path to a shared or static library file for ``kmlengine``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1130 +msgid "Path to a shared or static library file for ``minizip``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1134 +msgid "Path to a shared or static library file for ``uriparser``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1138 +msgid "Control whether to use LibKML. Defaults to ON when LibKML is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1141 +msgid "LibLZMA" +msgstr "" + +#: ../../source/development/building_from_source.rst:1143 +msgid "" +"`LibLZMA `_ is a compression library which " +"offers the lossless LZMA2 compression algorithm. It is used by the " +"internal libtiff library or the :ref:`raster.zarr` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1149 +msgid "Path to an include directory with the ``lzma.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1157 +msgid "Control whether to use LibLZMA. Defaults to ON when LibLZMA is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1161 +msgid "libOpenDRIVE" +msgstr "" + +#: ../../source/development/building_from_source.rst:1163 +msgid "" +"`libOpenDRIVE `_ is required " +"for the :ref:`vector.xodr` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1167 +msgid "" +"Path to libOpenDRIVE CMake configuration directory " +"``/cmake/``. The :file:`cmake/` path is usually automatically" +" created when installing libOpenDRIVE and contains the necessary " +"configuration files for inclusion into other project builds." +msgstr "" + +#: ../../source/development/building_from_source.rst:1171 +msgid "" +"Control whether to use libOpenDRIVE. Defaults to ON when libOpenDRIVE is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1175 +msgid "LibQB3" +msgstr "" + +#: ../../source/development/building_from_source.rst:1177 +msgid "" +"The `QB3 `_ compression, used by the " +":ref:`raster.marfa` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1182 +msgid "Control whether to use LibQB3. Defaults to ON when LibQB3 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1186 +msgid "LibXml2" +msgstr "" + +#: ../../source/development/building_from_source.rst:1188 +msgid "" +"The `LibXml2 `_ processing library is used to do " +"validation of XML files against a XML Schema (.xsd) in a few drivers " +"(PDF, GMLAS, GML OGR VRT) and for advanced capabilities in GMLJP2v2 " +"generation." +msgstr "" + +#: ../../source/development/building_from_source.rst:1202 +msgid "Control whether to use LibXml2. Defaults to ON when LibXml2 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1206 +msgid "LURATECH" +msgstr "" + +#: ../../source/development/building_from_source.rst:1208 +msgid "" +"The Luratech JPEG2000 SDK (closed source/proprietary) is required for the" +" :ref:`raster.jp2lura` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1211 +msgid "" +"LURATECH_ROOT or CMAKE_PREFIX_PATH should point to the directory of the " +"SDK." +msgstr "" + +#: ../../source/development/building_from_source.rst:1215 +msgid "Path to the include directory with the ``lwf_jp2.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1219 +msgid "Path to library file lib_lwf_jp2.a / lwf_jp2.lib" +msgstr "" + +#: ../../source/development/building_from_source.rst:1223 +msgid "Control whether to use LURATECH. Defaults to ON when LURATECH is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1227 +msgid "LZ4" +msgstr "" + +#: ../../source/development/building_from_source.rst:1229 +msgid "" +"`LZ4 `_ is a compression library which offers" +" the lossless LZ4 compression algorithm. It is used by the " +":ref:`raster.zarr` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1235 +msgid "Path to an include directory with the ``lz4.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1239 +msgid "" +"Path to a shared or static library file. A similar variable " +"``LZ4_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:1245 +msgid "Control whether to use LZ4. Defaults to ON when LZ4 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1249 +msgid "MONGOCXX" +msgstr "" + +#: ../../source/development/building_from_source.rst:1251 +msgid "" +"The `MongoCXX `_ and BsonCXX" +" libraries are needed to build the :ref:`vector.mongodbv3` driver. They " +"can be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:1257 +msgid "Path to an include directory with the ``mongocxx/client.hpp`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1261 +msgid "" +"Path to an include directory with the ``bsoncxx/config/version.hpp`` " +"header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1265 +msgid "Path to a library file ``mongocxx``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1269 +msgid "Path to a library file ``bsoncxx``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1273 +msgid "Control whether to use MONGOCXX. Defaults to ON when MONGOCXX is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1277 +#: ../../source/development/rfc/rfc34_license_policy.rst:177 +msgid "MRSID" +msgstr "" + +#: ../../source/development/building_from_source.rst:1279 +msgid "" +"The MRSID Raster DSDK (closed source/proprietary) is required for the " +":ref:`raster.mrsid` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1282 +msgid "" +"MRSID_ROOT or CMAKE_PREFIX_PATH should point to the directory of the SDK " +"ending with Raster_DSDK. Note that on Linux, its lib subdirectory should " +"be in the LD_LIBRARY_PATH so that the linking of applications succeeds " +"and libtbb.so can be found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1289 +msgid "Path to the include directory with the ``lt_base.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1293 +msgid "Path to library file libltidsdk" +msgstr "" + +#: ../../source/development/building_from_source.rst:1297 +msgid "" +"Whether to enable JPEG2000 support through the MrSID SDK. The default " +"value of this option is OFF." +msgstr "" + +#: ../../source/development/building_from_source.rst:1302 +msgid "Control whether to use MRSID. Defaults to ON when MRSID is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1306 +msgid "MSSQL_NCLI" +msgstr "" + +#: ../../source/development/building_from_source.rst:1308 +msgid "" +"The Microsoft SQL Native Client Library (closed source/proprietary) is " +"required to enable bulk copy in the :ref:`vector.mssqlspatial` driver. If" +" both MSSQL_NCLI and MSSQL_ODBC are found and enabled, MSSQL_ODBC will be" +" used. The library is normally found if installed in standard location, " +"and at version 11." +msgstr "" + +#: ../../source/development/building_from_source.rst:1315 +msgid "Major version of the Native Client, typically 11" +msgstr "" + +#: ../../source/development/building_from_source.rst:1319 +msgid "Path to include directory with ``sqlncli.h`` header." +msgstr "" + +#: ../../source/development/building_from_source.rst:1323 +#: ../../source/development/building_from_source.rst:1348 +#: ../../source/development/building_from_source.rst:1367 +msgid "Path to library to be linked." +msgstr "" + +#: ../../source/development/building_from_source.rst:1327 +msgid "" +"Control whether to use MSSQL_NCLI. Defaults to ON when MSSQL_NCLI is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1331 +msgid "MSSQL_ODBC" +msgstr "" + +#: ../../source/development/building_from_source.rst:1333 +msgid "" +"The Microsoft SQL Native ODBC driver Library (closed source/proprietary) " +"is required to enable bulk copy in the :ref:`vector.mssqlspatial` driver." +" If both MSSQL_NCLI and MSSQL_ODBC are found and enabled, MSSQL_ODBC will" +" be used. The library is normally found if installed in standard " +"location, and at version 17." +msgstr "" + +#: ../../source/development/building_from_source.rst:1340 +msgid "Major version of the Native Client, typically 17" +msgstr "" + +#: ../../source/development/building_from_source.rst:1344 +msgid "Path to include directory with ``msodbcsql.h`` header." +msgstr "" + +#: ../../source/development/building_from_source.rst:1352 +msgid "" +"Control whether to use MSSQL_ODBC. Defaults to ON when MSSQL_ODBC is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1356 +msgid "MYSQL" +msgstr "" + +#: ../../source/development/building_from_source.rst:1358 +msgid "" +"The MySQL or MariaDB client library is required to enable the " +":ref:`vector.mysql` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1363 +msgid "Path to include directory with ``mysql.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1371 +msgid "Control whether to use MYSQL. Defaults to ON when MYSQL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1375 +msgid "NetCDF" +msgstr "" + +#: ../../source/development/building_from_source.rst:1377 +msgid "" +"The `netCDF `_ is required to enable" +" the :ref:`raster.netcdf` driver. The ``nc-config`` program can be used " +"to detect it." +msgstr "" + +#: ../../source/development/building_from_source.rst:1383 +msgid "Path to an include directory with the ``netcdf.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1391 +msgid "Control whether to use netCDF. Defaults to ON when netCDF is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1395 +msgid "ODBC" +msgstr "" + +#: ../../source/development/building_from_source.rst:1397 +msgid "" +"ODBC is required for various drivers: :ref:`vector.odbc`, " +":ref:`vector.pgeo`, :ref:`vector.hana` and :ref:`vector.mssqlspatial`. It" +" is normally automatically found in system directories on Unix and " +"Windows." +msgstr "" + +#: ../../source/development/building_from_source.rst:1403 +msgid "Path to ODBC include directory with ``sql.h`` header." +msgstr "" + +#: ../../source/development/building_from_source.rst:1407 +msgid "Path to ODBC library to be linked." +msgstr "" + +#: ../../source/development/building_from_source.rst:1411 +msgid "Control whether to use ODBC. Defaults to ON when ODBC is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1415 +msgid "ODBC-CPP" +msgstr "" + +#: ../../source/development/building_from_source.rst:1417 +msgid "" +"The `odbc-cpp-wrapper library `_" +" is required for the :ref:`vector.hana` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1422 +msgid "Path to an include directory with the ``odbc/Environment.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1430 +msgid "Control whether to use ODBC-CPP. Defaults to ON when ODBC-CPP is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1434 +msgid "OGDI" +msgstr "" + +#: ../../source/development/building_from_source.rst:1436 +msgid "" +"The `OGDI `_ library is required for " +"the :ref:`vector.ogdi` driver. It can be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:1441 +msgid "Path to an include directory with the ``ecs.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1449 +msgid "Control whether to use OGDI. Defaults to ON when OGDI is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1453 +msgid "OpenCAD" +msgstr "" + +#: ../../source/development/building_from_source.rst:1455 +msgid "" +"`libopencad `_ is required" +" for the :ref:`vector.cad` driver. If not found, an internal copy can be " +"used." +msgstr "" + +#: ../../source/development/building_from_source.rst:1460 +msgid "Path to an include directory with the ``opencad.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1468 +msgid "" +"Control whether to use external libopencad. Defaults to ON when external " +"libopencad is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1472 +msgid "" +"Control whether to use internal libopencad copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_OPENCAD=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:1478 +msgid "OpenCL" +msgstr "" + +#: ../../source/development/building_from_source.rst:1480 +msgid "" +"The OpenCL library may be used to accelerate warping computations, " +"typically with a GPU." +msgstr "" + +#: ../../source/development/building_from_source.rst:1483 +msgid "" +"(GDAL 3.5 and 3.6) It is disabled by default even when detected, since " +"the current OpenCL warping implementation lags behind the generic " +"implementation. Starting with GDAL 3.7, build support is enabled by " +"default when OpenCL is detected, but it is disabled by default at " +"runtime. The warping option USE_OPENCL or the configuration option " +"GDAL_USE_OPENCL must be set to YES to enable it." +msgstr "" + +#: ../../source/development/building_from_source.rst:1491 +msgid "Path to an include directory with the ``CL/cl.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1499 +msgid "Control whether to use OPENCL. Defaults to *OFF* when OPENCL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1503 +msgid "OpenEXR" +msgstr "" + +#: ../../source/development/building_from_source.rst:1505 +msgid "" +"`OpenEXR `_ is " +"required for the :ref:`raster.exr` driver" +msgstr "" + +#: ../../source/development/building_from_source.rst:1507 +msgid "" +"Specify ``OpenEXR_ROOT`` variable pointing to the parent directory of " +"/lib and /include subdirectories, i.e. /DEV/lib/openexr-3.0. For OpenEXR " +">= 3 additionally specify ``Imath_ROOT`` as this is a separate library " +"now, i.e. /DEV/lib/imath-3.1.3" +msgstr "" + +#: ../../source/development/building_from_source.rst:1512 +#: ../../source/development/building_from_source.rst:1517 +msgid "or" +msgstr "" + +#: ../../source/development/building_from_source.rst:1514 +msgid "" +"Specify root directory adding to the ``CMAKE_PREFIX_PATH`` variable to " +"find OpenEXR's pkgconfig. For example " +"-DCMAKE_PREFIX_PATH=/DEV/lib/openexr-3.0;/DEV/lib/imath-3.1.3" +msgstr "" + +#: ../../source/development/building_from_source.rst:1519 +msgid "" +"Get real specific and set ``OpenEXR_INCLUDE_DIR``, ``Imath_INCLUDE_DIR``," +" ``OpenEXR_LIBRARY``, ``OpenEXR_UTIL_LIBRARY``, ``OpenEXR_HALF_LIBRARY``," +" ``OpenEXR_IEX_LIBRARY`` explicitly" +msgstr "" + +#: ../../source/development/building_from_source.rst:1527 +msgid "Control whether to use OpenEXR. Defaults to ON when OpenEXR is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1531 +msgid "OpenJPEG" +msgstr "" + +#: ../../source/development/building_from_source.rst:1533 +msgid "" +"The `OpenJPEG `_ library is an " +"open-source JPEG-2000 codec written in C language. It is required for the" +" :ref:`raster.jp2openjpeg` driver, or other drivers that use JPEG-2000 " +"functionality." +msgstr "" + +#: ../../source/development/building_from_source.rst:1539 +msgid "Path to an include directory with the ``openjpeg.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1547 +msgid "Control whether to use OpenJPEG. Defaults to ON when OpenJPEG is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1553 +msgid "" +"Control the mode used for find_package(OpenJPEG). Defaults to MODULE for " +"compatibility with OpenJPEG < 2.5.1. If set to CONFIG, only Config mode " +"search is attempted. If set to empty string, default CMake logic " +"(https://cmake.org/cmake/help/latest/command/find_package.html) applies." +msgstr "" + +#: ../../source/development/building_from_source.rst:1560 +msgid "OpenSSL" +msgstr "" + +#: ../../source/development/building_from_source.rst:1562 +msgid "" +"The Crypto component of the `OpenSSL " +"`_ library can be used for the RSA " +"SHA256 signing functionality used by some authentication methods of " +"Google Cloud. It might be required to use the :ref:`raster.eedai` images " +"or use the :ref:`/vsigs/ ` virtual file system." +msgstr "" + +#: ../../source/development/building_from_source.rst:1567 +msgid "" +"See https://cmake.org/cmake/help/latest/module/FindOpenSSL.html for " +"details on how to configure the library. For static linking, the " +"following options may be needed: -DOPENSSL_USE_STATIC_LIBS=TRUE " +"-DOPENSSL_MSVC_STATIC_RT=TRUE" +msgstr "" + +#: ../../source/development/building_from_source.rst:1573 +msgid "Control whether to use OpenSSL. Defaults to ON when OpenSSL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1577 +msgid "Oracle" +msgstr "" + +#: ../../source/development/building_from_source.rst:1579 +msgid "" +"The Oracle Instant Client SDK (closed source/proprietary) is required for" +" the :ref:`vector.oci` and the :ref:`raster.georaster` drivers" +msgstr "" + +#: ../../source/development/building_from_source.rst:1584 +msgid "Path to the root directory of the Oracle Instant Client SDK." +msgstr "" + +#: ../../source/development/building_from_source.rst:1588 +msgid "Control whether to use Oracle. Defaults to ON when Oracle is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1592 +msgid "Parquet" +msgstr "" + +#: ../../source/development/building_from_source.rst:1594 +msgid "" +"The Parquet component of the `Apache Arrow C++ " +"` library is required " +"for the :ref:`vector.parquet` driver. Specify install prefix in the " +"``CMAKE_PREFIX_PATH`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:1600 +msgid "Control whether to use Parquet. Defaults to ON when Parquet is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1604 +msgid "" +"Control whether to use statically built Arrow libraries. Defaults to OFF " +"when Parquet is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1608 +msgid "PCRE2" +msgstr "" + +#: ../../source/development/building_from_source.rst:1610 +msgid "" +"`PCRE2 `_ implements Perl-" +"compatible Regular Expressions support. It is used for the REGEXP " +"operator in drivers using SQLite3." +msgstr "" + +#: ../../source/development/building_from_source.rst:1615 +msgid "Path to an include directory with the ``pcre2.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1619 +msgid "Path to a shared or static library file with \"pcre2-8\" in its name." +msgstr "" + +#: ../../source/development/building_from_source.rst:1623 +msgid "Control whether to use PCRE2. Defaults to ON when PCRE2 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1627 +msgid "PDFIUM" +msgstr "" + +#: ../../source/development/building_from_source.rst:1629 +msgid "" +"The `PDFium `_ library " +"is one of the possible backends for the :ref:`raster.pdf` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1634 +msgid "Path to an include directory with the ``public/fpdfview.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1642 +msgid "Control whether to use PDFIUM. Defaults to ON when PDFIUM is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1646 +#: ../../source/development/rfc/rfc11_fastidentify.rst:200 +msgid "PNG" +msgstr "" + +#: ../../source/development/building_from_source.rst:1648 +msgid "" +"`libpng `_ is required for the " +":ref:`raster.png` driver, and may be used by a few other drivers " +"(:ref:`raster.grib`, :ref:`raster.gpkg`, etc.) If not found, an internal " +"copy of libpng can be used. See " +"https://cmake.org/cmake/help/latest/module/FindPNG.html for more details " +"on how the library is detected." +msgstr "" + +#: ../../source/development/building_from_source.rst:1656 +msgid "Path to an include directory with the ``png.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1660 +msgid "" +"Path to a shared or static library file. A similar variable " +"``PNG_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:1666 +msgid "" +"Control whether to use external libpng. Defaults to ON when external " +"libpng is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1670 +msgid "" +"Control whether to use internal libpng copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_PNG=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:1675 +msgid "Poppler" +msgstr "" + +#: ../../source/development/building_from_source.rst:1677 +msgid "" +"The `Poppler `_ library is one of the " +"possible backends for the :ref:`raster.pdf` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1680 +msgid "" +"Note that GDAL requires Poppler private headers, that are only installed " +"if configuring Poppler with -DENABLE_UNSTABLE_API_ABI_HEADERS." +msgstr "" + +#: ../../source/development/building_from_source.rst:1685 +msgid "Path to an include directory with the ``poppler-config.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1693 +msgid "Control whether to use Poppler. Defaults to ON when Poppler is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1697 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:46 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:60 +msgid "PostgreSQL" +msgstr "" + +#: ../../source/development/building_from_source.rst:1699 +msgid "" +"The `PostgreSQL client library `_ is " +"required for the :ref:`vector.pg` and :ref:`raster.postgisraster` " +"drivers." +msgstr "" + +#: ../../source/development/building_from_source.rst:1704 +msgid "Path to an include directory with the ``libpq-fe.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1708 +msgid "" +"Path to a shared or static library file ``pq`` / ``libpq``. A similar " +"variable ``PostgreSQL_LIBRARY_DEBUG`` can also be specified to a similar " +"library for building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:1714 +msgid "" +"Control whether to use PostgreSQL. Defaults to ON when PostgreSQL is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1718 +msgid "PROJ" +msgstr "" + +#: ../../source/development/building_from_source.rst:1720 +msgid "" +"`PROJ `_ >= 6.3 is a *required* " +"dependency for GDAL." +msgstr "" + +#: ../../source/development/building_from_source.rst:1724 +msgid "Path to an include directory with the ``proj.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1728 +msgid "" +"Path to a shared or static library file, such as ``libproj.so``, " +"``proj.lib``, or other name. A similar variable ``PROJ_LIBRARY_DEBUG`` " +"can also be specified to a similar library for building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:1737 +msgid "" +"Control the mode used for find_package(PROJ). Alters how the default " +"CMake search logic " +"(https://cmake.org/cmake/help/latest/command/find_package.html) applies. " +"Defaults to CUSTOM, where the CONFIG mode is applied for PROJ >= 8, and " +"fallbacks to default MODULE mode otherwise. Other values are passed " +"directly to find_package()" +msgstr "" + +#: ../../source/development/building_from_source.rst:1745 +msgid "QHULL" +msgstr "" + +#: ../../source/development/building_from_source.rst:1747 +msgid "" +"The `QHULL `_ library is used for the " +"linear interpolation of gdal_grid. If not found, an internal copy can be " +"used." +msgstr "" + +#: ../../source/development/building_from_source.rst:1752 +msgid "" +"Name of the pkg-config package, typically ``qhull_r`` or " +"``qhullstatic_r``. Defaults to ``qhull_r``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1756 +msgid "" +"Path to an include directory with the ``libqhull_r/libqhull_r.h`` header " +"file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1760 +msgid "Path to a shared or static library file to the reentrant library." +msgstr "" + +#: ../../source/development/building_from_source.rst:1764 +msgid "Control whether to use QHULL. Defaults to ON when QHULL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1768 +msgid "" +"Control whether to use internal QHULL copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_QHULL=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:1773 +msgid "RASTERLITE2" +msgstr "" + +#: ../../source/development/building_from_source.rst:1775 +msgid "" +"The `RasterLite2 `_ " +"(>= 1.1.0) library used by the :ref:`raster.rasterlite2` driver. It can " +"be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:1781 +msgid "" +"Path to an include directory with the ``rasterlite2/rasterlite2.h`` " +"header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1789 +msgid "" +"Control whether to use RasterLite2. Defaults to ON when RasterLite2 is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1793 +msgid "rdb" +msgstr "" + +#: ../../source/development/building_from_source.rst:1795 +msgid "" +"The `RDB ` " +"(closed source/proprietary) library is required for the :ref:`raster.rdb`" +" driver. Specify install prefix in the ``CMAKE_PREFIX_PATH`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:1801 +msgid "Control whether to use rdb. Defaults to ON when rdb is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1805 +msgid "SPATIALITE" +msgstr "" + +#: ../../source/development/building_from_source.rst:1807 +msgid "" +"The `Spatialite `_ " +"library used by the :ref:`vector.sqlite` and :ref:`vector.gpkg` drivers, " +"and the :ref:`sql_sqlite_dialect`. It can be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:1813 +msgid "Path to an include directory with the ``spatialite.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1821 +msgid "" +"Control whether to use Spatialite. Defaults to ON when Spatialite is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1825 +msgid "SQLite3" +msgstr "" + +#: ../../source/development/building_from_source.rst:1827 +msgid "" +"The `SQLite3 `_ library is required for " +"the :ref:`vector.sqlite` and :ref:`vector.gpkg` drivers (and also used by" +" other drivers), and the :ref:`sql_sqlite_dialect`." +msgstr "" + +#: ../../source/development/building_from_source.rst:1833 +msgid "Path to an include directory with the ``sqlite3.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1837 +msgid "" +"Path to a shared or static library file, such as ``libsqlite3.so``, " +"``sqlite3.lib`` or other name." +msgstr "" + +#: ../../source/development/building_from_source.rst:1842 +msgid "Control whether to use SQLite3. Defaults to ON when SQLite3 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1846 +msgid "SFCGAL" +msgstr "" + +#: ../../source/development/building_from_source.rst:1848 +msgid "" +"`SFCGAL `_ is a geometry library " +"which supports ISO 19107:2013 and OGC Simple Features Access 1.2 for 3D " +"operations (PolyhedralSurface, TINs, ...)" +msgstr "" + +#: ../../source/development/building_from_source.rst:1858 +msgid "" +"Path to a shared or static library file. A similar variable " +"``SFCGAL_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:1864 +msgid "Control whether to use SFCGAL. Defaults to ON when SFCGAL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1868 +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:213 +msgid "SWIG" +msgstr "" + +#: ../../source/development/building_from_source.rst:1870 +msgid "" +"`SWIG `_ is a software development tool that connects " +"programs written in C and C++ with a variety of high-level programming " +"languages. It is used for the Python, Java and CSharp bindings." +msgstr "" + +#: ../../source/development/building_from_source.rst:1876 +msgid "Path to the SWIG executable." +msgstr "" + +#: ../../source/development/building_from_source.rst:1878 +msgid "" +"Note that setting it explicitly might be needed, and that putting the " +"directory of the installed binary into the PATH might not be sufficient. " +"The reason is that when building from source, a \"swig\" binary will be " +"generated, but FindSWIG will prefer a \"swig-4.0\" binary if found " +"elsewhere in the PATH." +msgstr "" + +#: ../../source/development/building_from_source.rst:1886 +msgid "TEIGHA" +msgstr "" + +#: ../../source/development/building_from_source.rst:1888 +msgid "" +"The TEIGHA / Open Design Alliance libraries (closed source/proprietary) " +"are required for the :ref:`vector.dwg` and :ref:`vector.dgnv8` drivers. " +"Note that on Linux, with a SDK consisting of shared libraries, the " +"bin/{platform_name} subdirectory of the SDK should be in the " +"LD_LIBRARY_PATH so that the linking of applications succeeds. The " +"TEIGHA_ROOT variable must be set." +msgstr "" + +#: ../../source/development/building_from_source.rst:1897 +msgid "" +"Path to the base directory where the Kernel and Drawings package must be " +"extracted." +msgstr "" + +#: ../../source/development/building_from_source.rst:1902 +msgid "" +"Path to a directory where a ``OdActivationInfo`` file is located. If the " +"file is somewhere under TEIGHA_ROOT, it will be automatically discovered." +" Otherwise this variable must be set for recent SDK versions (at least " +"with 2021 and later)." +msgstr "" + +#: ../../source/development/building_from_source.rst:1909 +msgid "Control whether to use TEIGHA. Defaults to ON when TEIGHA is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1913 +msgid "TIFF" +msgstr "" + +#: ../../source/development/building_from_source.rst:1915 +msgid "" +"`libtiff `_ is required for the " +":ref:`raster.gtiff` drivers, and a few other drivers. If not found, an " +"internal copy of libtiff can be used." +msgstr "" + +#: ../../source/development/building_from_source.rst:1921 +msgid "Path to an include directory with the ``tiff.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1925 +msgid "" +"Path to a shared or static library file, such as ``libtiff.so``, " +"``tiff.lib``, or other name. A similar variable ``TIFF_LIBRARY_DEBUG`` " +"can also be specified to a similar library for building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:1932 +msgid "" +"Control whether to use external libtiff. Defaults to ON when external " +"libtiff is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1936 +msgid "" +"Control whether to use internal libtiff copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_TIFF=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:1941 +msgid "TileDB" +msgstr "" + +#: ../../source/development/building_from_source.rst:1943 +msgid "" +"The `TileDB ` library is required " +"for the :ref:`raster.tiledb` driver. Specify install prefix in the " +"``CMAKE_PREFIX_PATH`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:1946 +msgid "TileDB >= 2.15 is required since GDAL 3.9" +msgstr "" + +#: ../../source/development/building_from_source.rst:1950 +msgid "Control whether to use TileDB. Defaults to ON when TileDB is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1954 +msgid "WebP" +msgstr "" + +#: ../../source/development/building_from_source.rst:1956 +msgid "" +"`WebP `_ is a image compression " +"library. It is required for the :ref:`raster.webp` driver, and may be " +"used by the :ref:`raster.gpkg` and the internal libtiff library." +msgstr "" + +#: ../../source/development/building_from_source.rst:1962 +msgid "Path to an include directory with the ``webp/encode.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1970 +msgid "Control whether to use WebP. Defaults to ON when WebP is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1974 +msgid "XercesC" +msgstr "" + +#: ../../source/development/building_from_source.rst:1976 +msgid "" +"`Xerces-C `_ is a stream-oriented XML" +" parser library which is required to enable XML parsing capabilities in " +"the :ref:`vector.nas`, :ref:`vector.ili` and :ref:`vector.gmlas` drivers." +" It can also be used as an alternative to Expat for the GML driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1991 +msgid "Control whether to use XercesC. Defaults to ON when XercesC is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1995 +msgid "ZLIB" +msgstr "" + +#: ../../source/development/building_from_source.rst:1997 +msgid "" +"`ZLib `_ is a compression library which " +"offers the lossless Deflate/Zip compression algorithm." +msgstr "" + +#: ../../source/development/building_from_source.rst:2002 +msgid "Path to an include directory with the ``zlib.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:2006 +msgid "" +"Path to a shared or static library file. A similar variable " +"``ZLIB_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:2012 +msgid "" +"Link to static external ZLIB directory. Only used if " +"GDAL_USE_ZLIB_INTERNAL=OFF and MSVC." +msgstr "" + +#: ../../source/development/building_from_source.rst:2017 +msgid "Control whether to use ZLIB. Defaults to ON when ZLIB is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:2021 +msgid "" +"Control whether to use internal zlib copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_ZLIB=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:2026 +msgid "ZSTD" +msgstr "" + +#: ../../source/development/building_from_source.rst:2028 +msgid "" +"`ZSTD `_ is a compression library which" +" offers the lossless ZStd compression algorithm (faster than Deflate/ZIP," +" but incompatible with it). It is used by the internal libtiff library or" +" the :ref:`raster.zarr` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:2034 +msgid "Path to an include directory with the ``zstd.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:2042 +msgid "Control whether to use ZSTD. Defaults to ON when ZSTD is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:2048 +msgid "Selection of drivers" +msgstr "" + +#: ../../source/development/building_from_source.rst:2050 +msgid "" +"By default, all drivers that have their build requirements satisfied will" +" be built-in in the GDAL core library." +msgstr "" + +#: ../../source/development/building_from_source.rst:2053 +msgid "The following options are available to select a subset of drivers:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2059 +#: ../../source/development/building_from_source.rst:2198 +msgid "" +"Independently of options that control global behavior, drivers can be " +"individually enabled or disabled with those options." +msgstr "" + +#: ../../source/development/building_from_source.rst:2064 +msgid "" +" above and below is *generally*, but not systematically the " +"short driver name." +msgstr "" + +#: ../../source/development/building_from_source.rst:2066 +msgid "Some drivers may also be grouped together for build purposes." +msgstr "" + +#: ../../source/development/building_from_source.rst:2068 +msgid "" +"A number of \"raw\" raster drivers (ACE2, BT, BYN, CPG, CTable2, DIPEx, " +"DOQ1, DOQ2, EHDR, EIR, ENVI, FAST, GenBIN, GSC, GTX, MFF2, ISCE, KRO, " +"MFF, LAN, LCP, LOSLAS, NDF, NTv2, PAUX, PNM, ROIPAC, RRASTER, SNODAS) are" +" controlled by the GDAL_ENABLE_DRIVER_RAW option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2073 +msgid "" +"Planetary raster formats (PDS, PDS4, ISIS2, ISIS3, VICAR) are controlled " +"by the GDAL_ENABLE_DRIVER_PDS option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2076 +msgid "" +"The AAIGRID, GRASSASCIIGRID and ISG raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_AAIGRID option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2078 +msgid "" +"The ECW and JP2ECW raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_ECW option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2080 +msgid "" +"The vector EEDA and raster EEDAI drivers are controlled by the " +"GDAL_ENABLE_DRIVER_EEDA option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2082 +msgid "" +"The GSAG, GSBG and GS7BG raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_GSG option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2084 +msgid "" +"The HDF5 and BAG raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_HDF5 option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2086 +msgid "" +"The MrSID and JP2MrSID raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_MRSID option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2088 +msgid "" +"The NITF, RPFTOC and ECRGTOC raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_NITF option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2090 +msgid "" +"The NWT_GRD and NWT_GRC raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_NORTHWOOD option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2092 +msgid "" +"The SRP and ADRG raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_ADRG option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2094 +msgid "" +"The Interlis 1 and Interlis 2 vector drivers are controlled by the " +"GDAL_ENABLE_DRIVER_ILI option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2096 +msgid "" +"The WFS and OAPIF vector drivers are controlled by the " +"GDAL_ENABLE_DRIVER_WFS option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2098 +msgid "" +"The AVCBIN and AVCE00 vector drivers are controlled by the " +"GDAL_ENABLE_DRIVER_AVC option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2100 +msgid "" +"The DWG and DGNv8 vector drivers are controlled by the " +"GDAL_ENABLE_DRIVER_DWG option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2102 +msgid "There might be variations in naming, e.g. :" +msgstr "" + +#: ../../source/development/building_from_source.rst:2104 +msgid "the \"AIG\" raster driver is controlled by GDAL_ENABLE_DRIVER_AIGRID." +msgstr "" + +#: ../../source/development/building_from_source.rst:2106 +msgid "the \"ESAT\" raster driver is controlled by GDAL_ENABLE_DRIVER_ENVISAT." +msgstr "" + +#: ../../source/development/building_from_source.rst:2108 +msgid "the \"GeoRaster\" raster driver is controlled by GDAL_ENABLE_DRIVER_GEOR." +msgstr "" + +#: ../../source/development/building_from_source.rst:2110 +msgid "the \"RST\" raster driver is controlled by GDAL_ENABLE_DRIVER_IDRISI." +msgstr "" + +#: ../../source/development/building_from_source.rst:2112 +msgid "" +"the \"ElasticSearch\" vector driver is controlled by " +"OGR_ENABLE_DRIVER_ELASTIC." +msgstr "" + +#: ../../source/development/building_from_source.rst:2114 +msgid "the \"PostgreSQL\" vector driver is controlled by OGR_ENABLE_DRIVER_PG." +msgstr "" + +#: ../../source/development/building_from_source.rst:2116 +msgid "the \"UK .NTF\" vector driver is controlled by OGR_ENABLE_DRIVER_NTF." +msgstr "" + +#: ../../source/development/building_from_source.rst:2120 +msgid "" +"Drivers that have both a raster and vector side (and are internally " +"implemented by a single GDALDriver instance) are controlled by either a " +"GDAL_ENABLE_DRIVER_ option or a " +"OGR_ENABLE_DRIVER_ one, but not both:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2124 +msgid "The CAD drivers are controlled by the OGR_ENABLE_DRIVER_CAD option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2125 +msgid "The netCDF drivers are controlled by the GDAL_ENABLE_DRIVER_NETCDF option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2126 +msgid "The PDF drivers are controlled by the GDAL_ENABLE_DRIVER_PDF option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2127 +msgid "The GPKG drivers are controlled by the OGR_ENABLE_DRIVER_GPKG option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2128 +msgid "The NGW drivers are controlled by the OGR_ENABLE_DRIVER_NGW option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2129 +msgid "The SQLite drivers are controlled by the OGR_ENABLE_DRIVER_SQLITE option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2133 +msgid "" +"The GDAL_ENABLE_DRIVER_ and OGR_ENABLE_DRIVER_ " +"options are only created when their required dependencies are found." +msgstr "" + +#: ../../source/development/building_from_source.rst:2141 +msgid "" +"Globally enable/disable all optional GDAL/raster, resp. all optional " +"OGR/vector drivers. More exactly, setting those variables to ON affect " +"the default value of the ``GDAL_ENABLE_DRIVER_`` or " +"``OGR_ENABLE_DRIVER_`` variables (when they are not yet " +"set)." +msgstr "" + +#: ../../source/development/building_from_source.rst:2146 +msgid "" +"This can be combined with individual activation of a subset of drivers by" +" using the ``GDAL_ENABLE_DRIVER_:BOOL=ON`` or " +"``OGR_ENABLE_DRIVER_:BOOL=ON`` variables. Note that changing" +" the value of GDAL_BUILD_OPTIONAL_DRIVERS/ OGR_BUILD_OPTIONAL_DRIVERS " +"after a first run of CMake does not change the activation of individual " +"drivers. It might be needed to pass ``-UGDAL_ENABLE_DRIVER_* " +"-UOGR_ENABLE_DRIVER_*`` to reset their state." +msgstr "" + +#: ../../source/development/building_from_source.rst:2155 +msgid "" +"The following GDAL drivers cannot be disabled: VRT, DERIVED, GTiff, COG, " +"HFA, MEM. The following OGR drivers cannot be disabled: \"ESRI " +"Shapefile\", \"MapInfo File\", OGR_VRT, Memory, KML, GeoJSON, GeoJSONSeq," +" ESRIJSON, TopoJSON." +msgstr "" + +#: ../../source/development/building_from_source.rst:2160 +msgid "" +"Disabling all OGR/vector drivers with -DOGR_BUILD_OPTIONAL_DRIVERS=OFF " +"may affect the ability to enable some GDAL/raster drivers that require " +"some vector drivers to be enabled (and reciprocally with some GDAL/raster" +" drivers depending on vector drivers). When such dependencies are not " +"met, a CMake error will be emitted with a hint for the way to resolve the" +" issue. It is also possible to anticipate such errors by looking at files" +" :source_file:`frmts/CMakeLists.txt` for dependencies of raster drivers " +"and :source_file:`ogr/ogrsf_frmts/CMakeLists.txt` for dependencies of " +"vector drivers." +msgstr "" + +#: ../../source/development/building_from_source.rst:2171 +msgid "Example of minimal build with the JP2OpenJPEG and SVG drivers enabled::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2179 +msgid "Build drivers as plugins" +msgstr "" + +#: ../../source/development/building_from_source.rst:2181 +msgid "" +"An important subset, but not all, drivers can be also built as plugin, " +"that is to say as standalone .dll/.so shared libraries, to be installed " +"in the ``gdalplugins`` subdirectory of the GDAL installation. This can be" +" useful in particular for drivers that depend on libraries that have a " +"license different (proprietary, copyleft, ...) from the core GDAL " +"library." +msgstr "" + +#: ../../source/development/building_from_source.rst:2187 +msgid "The list of drivers that can be built as plugins can be obtained with::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2191 +msgid "" +"The following options are available to select the plugin/builtin status " +"of a driver:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2201 +msgid "" +"Note that for the driver to be built, the corresponding base " +"``GDAL_ENABLE_DRIVER_{driver_name}:BOOL=ON`` or " +"``OGR_ENABLE_DRIVER_{driver_name}:BOOL=ON`` option must be set." +msgstr "" + +#: ../../source/development/building_from_source.rst:2207 +msgid "" +"Globally enable/disable building all (plugin capable), GDAL and OGR, " +"drivers as plugins. More exactly, setting that variable to ON affects the" +" default value of the ``GDAL_ENABLE_DRIVER__PLUGIN`` or " +"``OGR_ENABLE_DRIVER__PLUGIN`` variables (when they are not " +"yet set)." +msgstr "" + +#: ../../source/development/building_from_source.rst:2212 +msgid "" +"This can be combined with individual activation/deactivation of the " +"plugin status with the ``GDAL_ENABLE_DRIVER_{driver_name}_PLUGIN:BOOL`` " +"or ``OGR_ENABLE_DRIVER_{driver_name}_PLUGIN:BOOL`` variables. Note that " +"changing the value of GDAL_ENABLE_PLUGINS after a first run of CMake does" +" not change the activation of the plugin status of individual drivers. It" +" might be needed to pass ``-UGDAL_ENABLE_DRIVER_* -UOGR_ENABLE_DRIVER_*``" +" to reset their state." +msgstr "" + +#: ../../source/development/building_from_source.rst:2218 +msgid "" +"Example of build with all potential drivers as plugins, except the " +"JP2OpenJPEG one::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2224 +msgid "" +"There is a subtelty regarding ``GDAL_ENABLE_PLUGINS:BOOL=ON``. It only " +"controls the plugin status of plugin-capable drivers that have external " +"dependencies, that are not part of GDAL core dependencies (e.g. are " +"netCDF, HDF4, Oracle, PDF, etc.)." +msgstr "" + +#: ../../source/development/building_from_source.rst:2230 +msgid "" +"Globally enable/disable building all (plugin capable), GDAL and OGR, " +"drivers as plugins, for drivers that have no external dependencies (e.g. " +"BMP, FlatGeobuf), or that have dependencies that are part of GDAL core " +"dependencies (e.g GPX). Building such drivers as plugins is generally not" +" necessary, hence the use of a different option from GDAL_ENABLE_PLUGINS." +msgstr "" + +#: ../../source/development/building_from_source.rst:2236 +msgid "" +"In some circumstances, it might be desirable to prevent loading of GDAL " +"plugins. This can be done with:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2241 +msgid "Set to OFF to disable loading of GDAL plugins. Default is ON." +msgstr "" + +#: ../../source/development/building_from_source.rst:2245 +msgid "Deferred loaded plugins" +msgstr "" + +#: ../../source/development/building_from_source.rst:2247 +msgid "" +"Starting with GDAL 3.9, a number of in-tree drivers, that can be built as" +" plugins, are loaded in a deferred way. This involves that some part of " +"their code, which does not depend on external libraries, is included in " +"core libgdal, whereas most of the driver code is in a separated " +"dynamically loaded library. For builds where libgdal and its plugins are " +"built in a single operation, this is fully transparent to the user." +msgstr "" + +#: ../../source/development/building_from_source.rst:2254 +msgid "" +"When a plugin driver is known of core libgdal, but not available as a " +"plugin at runtime, GDAL will inform the user that the plugin is not " +"available, but could be installed. It is possible to give more hints on " +"how to install a plugin by setting the following option:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2263 +msgid "Custom message to give a hint to the user how to install a missing plugin" +msgstr "" + +#: ../../source/development/building_from_source.rst:2266 +msgid "For example, if doing a build with::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2270 +msgid "" +"and opening a Parquet file while the plugin is not installed will display" +" the following error::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2277 +msgid "" +"For more specific builds where libgdal would be first built, and then " +"plugin drivers built in later incremental builds, this approach would not" +" work, given that the core libgdal built initially would lack code needed" +" to declare the plugin(s)." +msgstr "" + +#: ../../source/development/building_from_source.rst:2282 +msgid "" +"In that situation, the user building GDAL will need to explicitly declare" +" at initial libgdal build time that one or several plugin(s) will be " +"later built. Note that it is safe to distribute such a libgdal library, " +"even if the plugins are not always available at runtime." +msgstr "" + +#: ../../source/development/building_from_source.rst:2287 +#: ../../source/development/building_from_source.rst:2329 +msgid "This can be done with the following option:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2293 +msgid "Declares that a driver will be later built as a plugin." +msgstr "" + +#: ../../source/development/building_from_source.rst:2295 +msgid "" +"Setting this option to drivers not ready for it will lead to an explicit " +"CMake error." +msgstr "" + +#: ../../source/development/building_from_source.rst:2299 +msgid "" +"For some drivers (ECW, HEIF, JP2KAK, JPEG, JPEGXL, KEA, LERC, MrSID, " +"MSSQLSpatial, netCDF, OpenJPEG, PDF, TileDB, WEBP), the metadata and/or " +"dataset identification code embedded on libgdal, will depend on optional " +"capabilities of the dependent library (e.g. libnetcdf for netCDF) In that" +" situation, it is desirable that the dependent library is available at " +"CMake configuration time for the core libgdal built, but disabled with " +"GDAL_USE_=OFF. It must of course be re-enabled later when " +"the plugin is built." +msgstr "" + +#: ../../source/development/building_from_source.rst:2308 +msgid "For example for netCDF::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2317 +msgid "" +"For other drivers, GDAL_REGISTER_DRIVER__FOR_LATER_PLUGIN / " +"OGR_REGISTER_DRIVER__FOR_LATER_PLUGIN can be declared at " +"libgdal build time without requiring the dependent libraries needed to " +"build the plugin later to be available." +msgstr "" + +#: ../../source/development/building_from_source.rst:2323 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:315 +msgid "Out-of-tree deferred loaded plugins" +msgstr "" + +#: ../../source/development/building_from_source.rst:2325 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:317 +msgid "" +"Out-of-tree drivers can also benefit from the deferred loading " +"capability, provided libgdal is built with CMake variable(s) pointing to " +"external code containing the code for registering a proxy driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:2333 +msgid "" +"The pointed file must declare a ``void " +"DeclareDeferred(void)`` method with C linkage that takes " +"care of creating a GDALPluginDriverProxy instance and calling " +":cpp:func:`GDALDriverManager::DeclareDeferredPluginDriver` on it." +msgstr "" + +#: ../../source/development/building_from_source.rst:2340 +msgid "Python bindings options" +msgstr "" + +#: ../../source/development/building_from_source.rst:2344 +msgid "" +"Whether Python bindings should be built. It is ON by default, but only " +"effective if a Python installation is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:2347 +msgid "" +"A nominal Python installation should comprise the Python runtime (>= 3.6)" +" and the setuptools module. numpy and its header and development library " +"are also strongly recommended." +msgstr "" + +#: ../../source/development/building_from_source.rst:2351 +msgid "" +"The Python installation is normally found if found in the path or " +"registered through other standard installation mechanisms of the Python " +"installers. It is also possible to specify it using several variables, as" +" detailed in https://cmake.org/cmake/help/git-" +"stage/module/FindPython.html" +msgstr "" + +#: ../../source/development/building_from_source.rst:2356 +msgid "GDAL also provides the following option:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2360 +msgid "" +"When it is specified, Python_FIND_STRATEGY=VERSION is assumed. Note that " +"the patch number must be provided, as the EXACT strategy is used" +msgstr "" + +#: ../../source/development/building_from_source.rst:2363 +msgid "Other useful options:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2367 +msgid "Specify 'ONLY' to use virtualenv activated." +msgstr "" + +#: ../../source/development/building_from_source.rst:2371 +msgid "Specify Python installation prefix." +msgstr "" + +#: ../../source/development/building_from_source.rst:2373 +msgid "Examples::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2380 +msgid "" +"The following options are advanced ones and only taken into account " +"during the ``install`` CMake target." +msgstr "" + +#: ../../source/development/building_from_source.rst:2385 +msgid "" +"This option can be specified to a directory name, to override the " +"``CMAKE_INSTALL_PREFIX`` option. It is used to set the value of the " +"``--prefix`` option of ``python3 setup.py install``." +msgstr "" + +#: ../../source/development/building_from_source.rst:2391 +msgid "" +"This option can be specified to set the value of the ``--install-layout``" +" option of ``python3 setup.py install``. The install layout is by default" +" set to ``deb`` when it is detected that the Python installation looks " +"for the ``site-packages`` subdirectory. Otherwise it is unspecified." +msgstr "" + +#: ../../source/development/building_from_source.rst:2398 +msgid "" +"This option can be specified to set the value of the ``--install-lib`` " +"option of ``python3 setup.py install``. It is only taken into account on " +"MacOS systems, when the Python installation is a framework." +msgstr "" + +#: ../../source/development/building_from_source.rst:2404 +msgid "" +"The Python bindings are made of several modules (osgeo.gdal, osgeo.ogr, " +"etc.) which link each against libgdal. Consequently, a static build of " +"libgdal is not compatible with the bindings." +msgstr "" + +#: ../../source/development/building_from_source.rst:2411 +msgid "Java bindings options" +msgstr "" + +#: ../../source/development/building_from_source.rst:2415 +msgid "" +"Whether Java bindings should be built. It is ON by default, but only " +"effective if Java runtime and development packages are found. The " +"relevant options that can be set are described in " +"https://cmake.org/cmake/help/latest/module/FindJava.html and " +"https://cmake.org/cmake/help/latest/module/FindJNI.html. The ``ant`` " +"binary must also be available in the PATH." +msgstr "" + +#: ../../source/development/building_from_source.rst:2424 +msgid "" +"Subdirectory into which to install the :file:`gdal.jar` file. It defaults" +" to \"${CMAKE_INSTALL_DATADIR}/java\"" +msgstr "" + +#: ../../source/development/building_from_source.rst:2428 +msgid "" +"Prior to GDAL 3.8, the gdalalljni library was also installed in that " +"directory. Starting with GDAL 3.8, this is controlled by the " +"``GDAL_JAVA_JNI_INSTALL_DIR`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:2436 +msgid "" +"Subdirectory into which to install the :file:`libgdalalljni.so` / " +":file:`libgdalalljni.dylib` / :file:`gdalalljni.dll` library. It defaults" +" to \"${CMAKE_INSTALL_LIBDIR}/jni\"." +msgstr "" + +#: ../../source/development/building_from_source.rst:2441 +msgid "" +"Prior to GDAL 3.8, the gdalalljni library was installed in the directory " +"controlled by the ``GDAL_JAVA_INSTALL_DIR`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:2447 +msgid "" +"The Java bindings are made of several modules (org.osgeo.gdal, " +"org.osgeo.ogr, etc.) which link each against libgdal. Consequently, a " +"static build of libgdal is not compatible with the bindings." +msgstr "" + +#: ../../source/development/building_from_source.rst:2451 +msgid "Option only to be used by maintainers:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2455 +msgid "GPG key to sign build artifacts. Needed to generate bundle.jar." +msgstr "" + +#: ../../source/development/building_from_source.rst:2459 +msgid "GPG pass phrase to sign build artifacts." +msgstr "" + +#: ../../source/development/building_from_source.rst:2462 +msgid "C# bindings options" +msgstr "" + +#: ../../source/development/building_from_source.rst:2464 +msgid "" +"For more details on how to build and use the C# bindings read the " +"dedicated section :ref:`csharp_compile_cmake`." +msgstr "" + +#: ../../source/development/building_from_source.rst:2468 +msgid "" +"Whether C# bindings should be built. It is ON by default, but only " +"effective if C# runtime and development packages are found. Either .NET " +"SDK can be used or Mono. The relevant options that can be set are " +"described in ``cmake/modules/thirdparty/FindDotNetFrameworkSdk.cmake`` " +"and ``cmake/modules/thirdparty/FindMono.cmake``." +msgstr "" + +#: ../../source/development/building_from_source.rst:2476 +msgid "Forces the use of Mono as opposed to .NET to compile the C# bindings." +msgstr "" + +#: ../../source/development/building_from_source.rst:2480 +msgid "" +"Sets the .NET (or Mono) target SDK to be used when compiling the C# " +"binding libraries. `List of acceptable contents for .NET " +"`_" +msgstr "" + +#: ../../source/development/building_from_source.rst:2484 +msgid "" +"Sets the .NET (or Mono) target SDK to be used when compiling the C# " +"sample applications. `List of acceptable contents for .NET " +"`_" +msgstr "" + +#: ../../source/development/building_from_source.rst:2488 +msgid "" +"Build the C# bindings without building GDAL. This should be used when " +"building the bindings on top of an existing GDAL installation - for " +"instance on top of the CONDA package." +msgstr "" + +#: ../../source/development/building_from_source.rst:2492 +msgid "" +"The C# bindings are made of several modules (OSGeo.GDAL, OSGeo.OGR, etc.)" +" which link each against libgdal. Consequently, a static build of libgdal" +" is not compatible with the bindings." +msgstr "" + +#: ../../source/development/building_from_source.rst:2497 +msgid "Driver specific options" +msgstr "" + +#: ../../source/development/building_from_source.rst:2501 +msgid "" +"The :ref:`raster.msg` driver is built only if this option is set to ON " +"(default is OFF). Its effect is to download the " +"https://gitlab.eumetsat.int/open-source/PublicDecompWT.git repository " +"(requires the ``git`` binary to be available at configuration time) into " +"the build tree and build the needed files from it into the driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:2508 +msgid "Cross-compiling for Android" +msgstr "" + +#: ../../source/development/building_from_source.rst:2510 +msgid "" +"First refer to https://cmake.org/cmake/help/latest/manual/cmake-" +"toolchains.7.html#cross-compiling-for-android and to " +":source_file:`.github/workflows/android_cmake/start.sh` for an example of" +" a build script to cross-compile from Ubuntu." +msgstr "" + +#: ../../source/development/building_from_source.rst:2516 +msgid "Typical build issues" +msgstr "" + +#: ../../source/development/building_from_source.rst:2519 +msgid "How do I get PROJ ?" +msgstr "" + +#: ../../source/development/building_from_source.rst:2521 +msgid "" +"PROJ is the only required build-time dependency of GDAL that is not " +"vendorized in the GDAL source code tree. Consequently, the PROJ header " +"and library must be available when configuring GDAL's CMake. Consult " +"`PROJ installation `__." +msgstr "" + +#: ../../source/development/building_from_source.rst:2526 +msgid "Conflicting PROJ libraries" +msgstr "" + +#: ../../source/development/building_from_source.rst:2528 +msgid "" +"If using a custom PROJ build (that is a PROJ build that does not come " +"from a distribution channel), it can sometimes happen that this custom " +"PROJ build conflicts with packaged dependencies, such as spatialite or " +"libgeotiff, that themselves link to another copy of PROJ." +msgstr "" + +#: ../../source/development/building_from_source.rst:2533 +msgid "" +"The clean way to solve this is to rebuild from sources those other " +"libraries against the custom PROJ build. For Linux based systems, given " +"that C API/ABI has been preserved in the PROJ 6, 7, 8, 9 series, if the " +"custom PROJ build is more recent than the PROJ used by those other " +"libraries, doing aliases of the older ``libproj.so.XX`` name to the newer" +" ``libproj.so.YY`` (with ``ln -s``) should work, although it is " +"definitely not recommended to use this solution in a production " +"environment." +msgstr "" + +#: ../../source/development/building_from_source.rst:2541 +msgid "" +"In any case, if ``ldd libgdal.so | grep libproj`` reports more than one " +"line, crashes will occur at runtime (often at process termination with a " +"``malloc_consolidate(): invalid chunk size`` and/or ``Aborted (core " +"dumped)`` error message)" +msgstr "" + +#: ../../source/development/building_from_source.rst:2547 +msgid "Autoconf/nmake (GDAL versions < 3.5.0)" +msgstr "" + +#: ../../source/development/building_from_source.rst:2549 +msgid "" +"See https://trac.osgeo.org/gdal/wiki/BuildHints for hints for GDAL < 3.5 " +"autoconf and nmake build systems." +msgstr "" + +#: ../../source/development/cmake.rst:5 +msgid "Using GDAL in CMake projects" +msgstr "" + +#: ../../source/development/cmake.rst:9 +msgid "" +"The recommended way to use the GDAL library 3.5 or higher in a CMake " +"project is to link to the imported library target ``GDAL::GDAL`` provided" +" by the CMake configuration which comes with the library. Typical usage " +"is:" +msgstr "" + +#: ../../source/development/cmake.rst:19 +msgid "" +"By adding the imported library target ``GDAL::GDAL`` to the target link " +"libraries, CMake will also pass the include directories to the compiler." +msgstr "" + +#: ../../source/development/cmake.rst:23 +msgid "" +"The CMake command ``find_package`` will look for the configuration in a " +"number of places. The lookup can be adjusted for all packages by setting " +"the cache variable or environment variable ``CMAKE_PREFIX_PATH``. In " +"particular, CMake will consult (and set) the cache variable ``GDAL_DIR``." +msgstr "" + +#: ../../source/development/cmake.rst:29 +msgid "" +"Before GDAL 3.5, it is recommended to use `find module supplied with " +"CMake `__. This" +" also creates the ``GDAL::GDAL`` target. It requires CMake version 3.14." +msgstr "" + +#: ../../source/development/dev_documentation.rst:5 +#: ../../source/development/dev_documentation.rst:20 +msgid "Building documentation" +msgstr "" + +#: ../../source/development/dev_documentation.rst:8 +msgid "Documentation overview" +msgstr "" + +#: ../../source/development/dev_documentation.rst:10 +msgid "" +"GDAL's documentation includes C and C++ :ref:`API documentation ` " +"built automatically from source comments using Doxygen and " +"reStructuredText (rst) files containing manually-edited content." +msgstr "" + +#: ../../source/development/dev_documentation.rst:14 +msgid "" +"|Sphinx| is used to combine the above components into a complete set of " +"documentation in HTML, PDF, and other formats." +msgstr "" + +#: ../../source/development/dev_documentation.rst:16 +msgid "" +"|Sphinx| and extensions used by GDAL can be installed by running " +"``python3 -m pip install -r requirements.txt`` from the ``doc`` " +"subdirectory." +msgstr "" + +#: ../../source/development/dev_documentation.rst:22 +msgid "" +"Documentation can be generated with Makefile targets, from the ``doc`` " +"subdirectory of the GDAL source repository (only on Unix systems)." +msgstr "" + +#: ../../source/development/dev_documentation.rst:25 +msgid "The following targets are available:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:27 +msgid "" +"``html``: build HTML documentation into the ``doc/build/html`` directory," +" where they can be viewed using a web browser." +msgstr "" + +#: ../../source/development/dev_documentation.rst:30 +msgid "``man``: build MAN pages into the ``doc/build/man`` directory." +msgstr "" + +#: ../../source/development/dev_documentation.rst:32 +msgid "``latexpdf``: build PDF documentation into the ``doc/build/pdf`` directory" +msgstr "" + +#: ../../source/development/dev_documentation.rst:34 +msgid "" +"``doxygen``: regenerate API Doxygen XML and HTML output, that is used by " +"the ``html`` target. Doxygen content is not automatically rebuilt when " +"source files are modified, hence this target must be explicitly run to " +"refresh it." +msgstr "" + +#: ../../source/development/dev_documentation.rst:38 +msgid "" +"``doxygen_check_warnings``: same as ``doxygen``, but errors out when " +"Doxygen emits a warning (the ``doxygen`` target is tolerant to Doxygen " +"warnings). This can be useful to reproduce one of the continuous " +"integration checks that verifies that there are no Doxygen warnings. " +"Requires Doxygen >= 1.9.3 to be warning free." +msgstr "" + +#: ../../source/development/dev_documentation.rst:44 +msgid "``clean``: clean the ``doc/build`` directory." +msgstr "" + +#: ../../source/development/dev_documentation.rst:46 +msgid "" +"It is also possible to run those targets as CMake targets. In that case, " +"the output directory will be the ``doc/build`` subdirectory of the CMake " +"build directory. To only clean the documentation, the ``clean_doc`` " +"target can be invoked. Note: those CMake targets are only available if " +"the CMake BUILD_DOCS=ON variable is set (it is set by default if build " +"preconditions are met, that is if Doxygen, Sphinx and make are available)" +msgstr "" + +#: ../../source/development/dev_documentation.rst:54 +msgid "" +"To visualize documentation changes while editing, it may be useful to " +"install the |sphinx-autobuild| python package. Once installed, running " +"``sphinx-autobuild -b html source build`` from the ``doc`` subdirectory " +"will build documentation and serve it on a local web server at " +"``http://127.0.0.1:8000``. The pages served will be automatically " +"refreshed as changes are made to underlying ``rst`` documentation files." +msgstr "" + +#: ../../source/development/dev_documentation.rst:60 +msgid "Python API documentation" +msgstr "" + +#: ../../source/development/dev_documentation.rst:62 +msgid "" +"Sphinx uses the `autodoc `_ extension to generate " +"documentation for the Python API from Python function docstrings. To be " +"correctly parsed by ``autodoc``, docstrings should follow the `numpydoc " +"Style guide `_. " +"Docstrings may be found in two locations. If the function was defined in " +"Python (i.e., using a ``%pythoncode`` SWIG directive), then the docstring" +" must be placed within the function definition. If the function is " +"defined in C++ only, then the docstring should be placed in a separate " +"file containing only docstrings (located in " +":source_file:`swig/include/python/docs`). Sphinx loads the Python " +"bindings when generating documentation, so for it to see any changes the " +"following steps must be completed:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:73 +msgid "" +"rebuild the Python bindings from the build directory (``cmake --build . " +"--target python_binding``)" +msgstr "" + +#: ../../source/development/dev_documentation.rst:74 +msgid "" +"make the updated Python bindings visible to Python, either by installing " +"them, or by running ``scripts/setdevenv.sh`` from the build directory" +msgstr "" + +#: ../../source/development/dev_documentation.rst:76 +msgid "" +"update the timestamp of the ``rst`` files associated with the page where " +"the documentation appears (e.g., ``touch " +"doc/source/api/python/osgeo.ogr.rst``)" +msgstr "" + +#: ../../source/development/dev_documentation.rst:82 +msgid "Sphinx RST Style guide" +msgstr "" + +#: ../../source/development/dev_documentation.rst:84 +msgid "" +"This section contains syntax rules, tips, and tricks for using Sphinx and" +" reStructuredText. For more information, please see this `comprehensive" +" guide to reStructuredText " +"`_, " +"as well as the `Sphinx reStructuredText Primer " +"`_." +msgstr "" + +#: ../../source/development/dev_documentation.rst:87 +msgid "Basic markup" +msgstr "" + +#: ../../source/development/dev_documentation.rst:89 +msgid "" +"A reStructuredText document is written in plain text. Without the need " +"for complex formatting, one can be composed simply, just like one would " +"any plain text document. For basic formatting, see this table:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:95 +msgid "**Format**" +msgstr "" + +#: ../../source/development/dev_documentation.rst:96 +msgid "**Syntax**" +msgstr "" + +#: ../../source/development/dev_documentation.rst:97 +msgid "**Output**" +msgstr "" + +#: ../../source/development/dev_documentation.rst:98 +msgid "Italics" +msgstr "" + +#: ../../source/development/dev_documentation.rst:99 +msgid "``*italics*`` (single asterisk)" +msgstr "" + +#: ../../source/development/dev_documentation.rst:100 +msgid "*italics*" +msgstr "" + +#: ../../source/development/dev_documentation.rst:101 +msgid "Bold" +msgstr "" + +#: ../../source/development/dev_documentation.rst:102 +msgid "``**bold**`` (double asterisk)" +msgstr "" + +#: ../../source/development/dev_documentation.rst:103 +msgid "**bold**" +msgstr "" + +#: ../../source/development/dev_documentation.rst:104 +msgid "Monospace" +msgstr "" + +#: ../../source/development/dev_documentation.rst:105 +msgid "`` ``monospace`` `` (double back quote)" +msgstr "" + +#: ../../source/development/dev_documentation.rst:106 +msgid "``monospace``" +msgstr "" + +#: ../../source/development/dev_documentation.rst:108 +msgid "" +"Use of basic markup is **not recommend**! Where possible use sphinx " +"inline directives (described below) to logically mark commands, " +"parameters, options, input, and files. By using directives consistently " +"these items can be styled appropriately." +msgstr "" + +#: ../../source/development/dev_documentation.rst:111 +msgid "Lists" +msgstr "" + +#: ../../source/development/dev_documentation.rst:113 +msgid "" +"There are two types of lists, bulleted lists and numbered lists. A " +"**bulleted list** looks like this:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:115 +msgid "An item" +msgstr "" + +#: ../../source/development/dev_documentation.rst:116 +msgid "Another item" +msgstr "" + +#: ../../source/development/dev_documentation.rst:117 +msgid "Yet another item" +msgstr "" + +#: ../../source/development/dev_documentation.rst:119 +#: ../../source/development/dev_documentation.rst:131 +msgid "This is accomplished with the following code::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:125 +msgid "A **numbered list** looks like this:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:127 +msgid "First item" +msgstr "" + +#: ../../source/development/dev_documentation.rst:128 +msgid "Second item" +msgstr "" + +#: ../../source/development/dev_documentation.rst:129 +msgid "Third item" +msgstr "" + +#: ../../source/development/dev_documentation.rst:137 +msgid "" +"Note that numbers are automatically generated, making it easy to " +"add/remove items." +msgstr "" + +#: ../../source/development/dev_documentation.rst:140 +msgid "List-tables" +msgstr "" + +#: ../../source/development/dev_documentation.rst:142 +msgid "" +"Bulleted lists can sometimes be cumbersome and hard to follow. When " +"dealing with a long list of items, use list-tables. For example, to talk" +" about a list of options, create a table that looks like this:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:148 +msgid "Shapes" +msgstr "" + +#: ../../source/development/dev_documentation.rst:149 +msgid "Description" +msgstr "" + +#: ../../source/development/dev_documentation.rst:150 +msgid "Square" +msgstr "" + +#: ../../source/development/dev_documentation.rst:151 +msgid "Four sides of equal length, 90 degree angles" +msgstr "" + +#: ../../source/development/dev_documentation.rst:152 +msgid "Rectangle" +msgstr "" + +#: ../../source/development/dev_documentation.rst:153 +msgid "Four sides, 90 degree angles" +msgstr "" + +#: ../../source/development/dev_documentation.rst:155 +msgid "This is done with the following code::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:169 +msgid "Page labels" +msgstr "" + +#: ../../source/development/dev_documentation.rst:171 +msgid "" +"**Ensure every page has a label that matches the name of the file.** For " +"example if the page is named ``foo_bar.rst`` then the page should have " +"the label::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:175 +msgid "Other pages can then link to that page by using the following code::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:182 +msgid "Linking" +msgstr "" + +#: ../../source/development/dev_documentation.rst:184 +msgid "" +"Links to other pages should never be titled as \"here\". Sphinx makes " +"this easy by automatically inserting the title of the linked document." +msgstr "" + +#: ../../source/development/dev_documentation.rst:186 +msgid "Bad" +msgstr "" + +#: ../../source/development/dev_documentation.rst:187 +msgid "More information about linking can be found :ref:`here `." +msgstr "" + +#: ../../source/development/dev_documentation.rst:189 +msgid "Good" +msgstr "" + +#: ../../source/development/dev_documentation.rst:189 +msgid "For more information, please see the section on :ref:`linking`." +msgstr "" + +#: ../../source/development/dev_documentation.rst:191 +msgid "To insert a link to an external website::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:195 +msgid "" +"The resulting link would look like this: `Text of the link " +"`__" +msgstr "" + +#: ../../source/development/dev_documentation.rst:197 +msgid "" +"It is very easy to have two links with the same text resulting in the " +"following error::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:201 +msgid "To avoid these warnings use of a double `__` generates an anonymous link." +msgstr "" + +#: ../../source/development/dev_documentation.rst:205 +msgid "Sections" +msgstr "" + +#: ../../source/development/dev_documentation.rst:207 +msgid "" +"Use sections to break up long pages and to help Sphinx generate tables of" +" contents." +msgstr "" + +#: ../../source/development/dev_documentation.rst:228 +msgid "Notes and warnings" +msgstr "" + +#: ../../source/development/dev_documentation.rst:230 +msgid "" +"When it is beneficial to have a section of text stand out from the main " +"text, Sphinx has two such boxes, the note and the warning. They function" +" identically, and only differ in their coloring. You should use notes " +"and warnings sparingly, however, as adding emphasis to everything makes " +"the emphasis less effective." +msgstr "" + +#: ../../source/development/dev_documentation.rst:232 +msgid "Here is an example of a note:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:234 +msgid "This is a note." +msgstr "" + +#: ../../source/development/dev_documentation.rst:236 +msgid "This note is generated with the following code::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:240 +msgid "Similarly, here is an example of a warning:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:242 +msgid "Beware of dragons." +msgstr "" + +#: ../../source/development/dev_documentation.rst:244 +msgid "This warning is generated by the following code::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:249 +msgid "Images" +msgstr "" + +#: ../../source/development/dev_documentation.rst:251 +msgid "" +"Add images to your documentation when possible. Images, such as " +"screenshots, are a very helpful way of making documentation " +"understandable. When making screenshots, try to crop out unnecessary " +"content (browser window, desktop, etc). Avoid scaling the images, as the" +" Sphinx theme automatically resizes large images. It is also helpful to " +"include a caption underneath the image.::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:258 +msgid "" +"In this example, the image file exists in the same directory as the " +"source page. If this is not the case, you can insert path information in" +" the above command. The root :file:`/` is the directory of the " +":file:`conf.py` file.::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:263 +msgid "External files" +msgstr "" + +#: ../../source/development/dev_documentation.rst:265 +msgid "" +"Text snippets, large blocks of downloadable code, and even zip files or " +"other binary sources can all be included as part of the documentation." +msgstr "" + +#: ../../source/development/dev_documentation.rst:267 +msgid "To include link to sample file, use the ``download`` directive::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:271 +msgid "" +"The result of this code will generate a standard link to an " +":download:`external file `" +msgstr "" + +#: ../../source/development/dev_documentation.rst:273 +msgid "To include the contents of a file, use ``literalinclude`` directive::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:279 +msgid "Example of :command:`gdalinfo` use:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:283 +msgid "" +"The ``literalinclude`` directive has options for syntax highlighting, " +"line numbers and extracting just a snippet::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:295 +msgid "Reference files and paths" +msgstr "" + +#: ../../source/development/dev_documentation.rst:297 +msgid "Use the following syntax to reference files and paths::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:301 +msgid "This will output: :file:`myfile.txt`." +msgstr "" + +#: ../../source/development/dev_documentation.rst:303 +msgid "You can reference paths in the same way::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:307 +msgid "This will output: :file:`path/to/myfile.txt`." +msgstr "" + +#: ../../source/development/dev_documentation.rst:309 +msgid "For Windows paths, use double backslashes::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:313 +msgid "This will output: :file:`C:\\\\myfile.txt`." +msgstr "" + +#: ../../source/development/dev_documentation.rst:315 +msgid "If you want to reference a non-specific path or file name::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:319 +msgid "This will output: :file:`{your/own/path/to}/myfile.txt`" +msgstr "" + +#: ../../source/development/dev_documentation.rst:321 +msgid "To reference a file in the GDAL source tree, use::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:325 +msgid "" +"This will output a link to the file on GitHub: " +":source_file:`gcore/gdaldriver.cpp`" +msgstr "" + +#: ../../source/development/dev_documentation.rst:328 +msgid "Reference code" +msgstr "" + +#: ../../source/development/dev_documentation.rst:330 +msgid "To reference a class::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:334 +msgid "To reference a method or function::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:342 +msgid "Define and reference configuration options" +msgstr "" + +#: ../../source/development/dev_documentation.rst:344 +msgid "To define a configuration option, use::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:353 +msgid "" +"Similar syntax can be used to define opening options (``.. oo::``), " +"creation options (``.. co::``), dataset creation options (``.. dsco::``)," +" or layer creation options (``.. lco::``)." +msgstr "" + +#: ../../source/development/dev_documentation.rst:357 +msgid "" +"To reference a configuration option, such as **GDAL_CACHEMAX**, use the " +"syntax in the table below." +msgstr "" + +#: ../../source/development/dev_documentation.rst:363 +msgid "Option type" +msgstr "" + +#: ../../source/development/dev_documentation.rst:364 +msgid "Syntax" +msgstr "" + +#: ../../source/development/dev_documentation.rst:365 +msgid "Configuration option" +msgstr "" + +#: ../../source/development/dev_documentation.rst:369 +msgid "Creation option" +msgstr "" + +#: ../../source/development/dev_documentation.rst:373 +msgid "Open option" +msgstr "" + +#: ../../source/development/dev_documentation.rst:377 +msgid "Dataset creation option" +msgstr "" + +#: ../../source/development/dev_documentation.rst:381 +msgid "Layer creation option" +msgstr "" + +#: ../../source/development/dev_documentation.rst:388 +msgid "Reference commands" +msgstr "" + +#: ../../source/development/dev_documentation.rst:390 +msgid "" +"Reference commands (such as :program:`gdalinfo`) with the following " +"syntax::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:394 +msgid "Use ``option`` directive for command line options::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:400 +msgid "Use ``describe`` to document create parameters::" +msgstr "" + +#: ../../source/development/dev_environment.rst:5 +msgid "Setting up a development environment" +msgstr "" + +#: ../../source/development/dev_environment.rst:10 +msgid "See :ref:`build_requirements`" +msgstr "" + +#: ../../source/development/dev_environment.rst:13 +msgid "Vagrant" +msgstr "" + +#: ../../source/development/dev_environment.rst:15 +msgid "" +"`Vagrant `_ is a tool that works with a " +"virtualization product such as VirtualBox to create a reproducible " +"development environment. GDAL includes a Vagrant configuration file that " +"sets up an Ubuntu virtual machine with a comprehensive set of " +"dependencies." +msgstr "" + +#: ../../source/development/dev_environment.rst:19 +msgid "" +"Once Vagrant has been installed and the GDAL source downloaded, the " +"virtual machine can be set up by running the following from the source " +"root directory:" +msgstr "" + +#: ../../source/development/dev_environment.rst:27 +msgid "" +"The source root directory is exposed inside the virtual machine at " +"``/vagrant``, so changes made to GDAL source files on the host are seen " +"inside the VM. To rebuild GDAL after changing source files, you can " +"connect to the VM and re-run the build command:" +msgstr "" + +#: ../../source/development/dev_environment.rst:36 +msgid "" +"Note that the following directories on the host will be created (and can " +"be removed if the Vagrant environment is no longer needed):" +msgstr "" + +#: ../../source/development/dev_environment.rst:39 +msgid "" +"``../apt-cache/ubuntu/jammy64``: contains a cache of Ubuntu packages of " +"the VM, to allow faster VM reconstruction" +msgstr "" + +#: ../../source/development/dev_environment.rst:41 +msgid "``build_vagrant``: CMake build directory" +msgstr "" + +#: ../../source/development/dev_environment.rst:42 +msgid "``ccache_vagrant``: CCache directory" +msgstr "" + +#: ../../source/development/dev_environment.rst:45 +msgid "Docker" +msgstr "" + +#: ../../source/development/dev_environment.rst:47 +msgid "" +"The Linux environments used for building and testing GDAL on GitHub " +"Actions are defined by Docker images that can be pulled to any machine " +"for development. The Docker image used for each build is specified in " +":source_file:`.github/workflows/linux_build.yml`. As an example, the " +"following commands can be run from the GDAL source root to build and test" +" GDAL using the clang address sanitizer (ASAN) in the same environment " +"that is used in GitHub Actions:" +msgstr "" + +#: ../../source/development/dev_environment.rst:65 +msgid "" +"To avoid built objects being owned by root, it may be desirable to add " +"``-u $(id -u):$(id -g) -v /etc/passwd:/etc/passwd`` to the ``docker run``" +" command above." +msgstr "" + +#: ../../source/development/dev_environment.rst:69 +msgid "Building on Windows with Conda dependencies and Visual Studio" +msgstr "" + +#: ../../source/development/dev_environment.rst:71 +msgid "" +"It is less appropriate for Debug builds of GDAL, than other methods, such" +" as using vcpkg." +msgstr "" + +#: ../../source/development/dev_environment.rst:74 +msgid "Install git" +msgstr "" + +#: ../../source/development/dev_environment.rst:76 +msgid "Install `git `_" +msgstr "" + +#: ../../source/development/dev_environment.rst:79 +msgid "Install miniconda" +msgstr "" + +#: ../../source/development/dev_environment.rst:81 +msgid "" +"Install `miniconda `_" +msgstr "" + +#: ../../source/development/dev_environment.rst:84 +msgid "Install GDAL dependencies" +msgstr "" + +#: ../../source/development/dev_environment.rst:86 +msgid "Start a Conda enabled console and assuming there is a c:\\\\dev directory" +msgstr "" + +#: ../../source/development/dev_environment.rst:103 +msgid "" +"The ``compilers`` package will install ``vs2017_win-64`` (at time of " +"writing) to set the appropriate environment for cmake to pick up. It is " +"also possible to use the ``vs2019_win-64`` package if Visual Studio 2019 " +"is to be used." +msgstr "" + +#: ../../source/development/dev_environment.rst:108 +msgid "Checkout GDAL sources" +msgstr "" + +#: ../../source/development/dev_environment.rst:116 +msgid "Build GDAL" +msgstr "" + +#: ../../source/development/dev_environment.rst:118 +msgid "From a Conda enabled console" +msgstr "" + +#: ../../source/development/dev_environment.rst:132 +msgid "Run GDAL tests" +msgstr "" + +#: ../../source/development/dev_environment.rst:144 +msgid "Setting development environment variables" +msgstr "" + +#: ../../source/development/dev_environment.rst:146 +msgid "" +"Once GDAL has been built, a number of environment variables must be set " +"to be able to execute C++ or Python utilities of the build directory, or " +"run tests." +msgstr "" + +#: ../../source/development/dev_environment.rst:149 +msgid "This can be done by sourcing the following from the build directory:" +msgstr "" + +#: ../../source/development/dev_environment.rst:155 +msgid "" +"(with adjustments to the above path if the build directory is not a " +"subdirectory of the GDAL source root)." +msgstr "" + +#: ../../source/development/dev_environment.rst:157 +msgid "" +"For Windows, a similar ``scripts/setdevenv.bat`` script exists (it " +"currently assumes a Release build)." +msgstr "" + +#: ../../source/development/dev_environment.rst:159 +msgid "" +"To verify that environment variables have been set correctly, you can " +"check the version of a GDAL binary:" +msgstr "" + +#: ../../source/development/dev_environment.rst:166 +msgid "and the Python bindings:" +msgstr "" + +#: ../../source/development/dev_practices.rst:5 +msgid "Development practices" +msgstr "" + +#: ../../source/development/dev_practices.rst:8 +msgid "Making changes to GDAL" +msgstr "" + +#: ../../source/development/dev_practices.rst:10 +msgid "" +"Minor changes to GDAL, such as bug fixes, may be made by opening a GitHub" +" pull request." +msgstr "" + +#: ../../source/development/dev_practices.rst:12 +msgid "" +"Major changes should be discussed on the |gdal-dev| listserv and may " +"require the drafting of a RFC (request for comment) document." +msgstr "" + +#: ../../source/development/dev_practices.rst:15 +msgid "" +"GDAL's policy on substantial code additions is documented at " +":ref:`rfc-85`." +msgstr "" + +#: ../../source/development/dev_practices.rst:18 +#: ../../source/development/rfc/rfc45_virtualmem.rst:1045 +msgid "Portability" +msgstr "" + +#: ../../source/development/dev_practices.rst:20 +msgid "" +"GDAL strives to be widely portable to 32 bit and 64 bit computing " +"environments, as well as little-endian and big-endian ordered CPUs. CPL " +"functions in the port directory provide services to abstract platform " +"specific operations." +msgstr "" + +#: ../../source/development/dev_practices.rst:25 +msgid "" +"Generally speaking, where available CPL functions should be used in " +"preference to operating system functions for operations like memory " +"allocation, path parsing, filesystem I/O (using VSILFILE* / " +"VSIVirtualFile*), ODBC access, etc." +msgstr "" + +#: ../../source/development/dev_practices.rst:31 +msgid "C/C++ standards" +msgstr "" + +#: ../../source/development/dev_practices.rst:33 +msgid "" +"The current C and C++ standards adopted by GDAL/OGR are C99 and C++17 " +"(last updated per :ref:`rfc-98`)." +msgstr "" + +#: ../../source/development/dev_practices.rst:37 +msgid "Variable naming" +msgstr "" + +#: ../../source/development/dev_practices.rst:39 +msgid "" +"Much of the existing GDAL/OGR code uses an adapted Hungarian naming " +"convention. Use of this convention is not mandatory, but when maintaining" +" code using this convention it is desirable to continue adhering to it " +"with changes. Most importantly, please avoiding using it improperly as " +"that can be very confusing." +msgstr "" + +#: ../../source/development/dev_practices.rst:45 +msgid "" +"In Hungarian prefixing the prefix tells something about about the type, " +"and potentially semantics of a variable. The following are some prefixes " +"used in GDAL/OGR." +msgstr "" + +#: ../../source/development/dev_practices.rst:49 +msgid "*a*: array" +msgstr "" + +#: ../../source/development/dev_practices.rst:50 +msgid "" +"*b*: C/C++ bool. In C code that pre-dates C99 adoption, it is also used " +"for ints with only TRUE/FALSE values." +msgstr "" + +#: ../../source/development/dev_practices.rst:51 +msgid "*by*: byte (GByte / unsigned char)." +msgstr "" + +#: ../../source/development/dev_practices.rst:52 +msgid "*df*: floating point value (double precision)" +msgstr "" + +#: ../../source/development/dev_practices.rst:53 +msgid "*e*: enumeration" +msgstr "" + +#: ../../source/development/dev_practices.rst:54 +msgid "*i*: integer number used as a zero based array or loop index." +msgstr "" + +#: ../../source/development/dev_practices.rst:55 +msgid "*f*: floating point value (single precision)" +msgstr "" + +#: ../../source/development/dev_practices.rst:56 +msgid "*h*: an opaque handle (such as GDALDatasetH)." +msgstr "" + +#: ../../source/development/dev_practices.rst:57 +msgid "*n*: integer number (size unspecified)" +msgstr "" + +#: ../../source/development/dev_practices.rst:58 +msgid "*o*: C++ object" +msgstr "" + +#: ../../source/development/dev_practices.rst:59 +msgid "*os*: CPLString or std::string" +msgstr "" + +#: ../../source/development/dev_practices.rst:60 +msgid "*p*: pointer" +msgstr "" + +#: ../../source/development/dev_practices.rst:61 +msgid "*psz*: pointer to a null-terminated string. (eg. \"char \\*pszName;\")" +msgstr "" + +#: ../../source/development/dev_practices.rst:62 +msgid "*sz*: null-terminated string (eg.\" char szName[100];\")" +msgstr "" + +#: ../../source/development/dev_practices.rst:63 +msgid "*k*: compile-time constant" +msgstr "" + +#: ../../source/development/dev_practices.rst:65 +msgid "" +"Prefixes can be stacked. The following are some examples of meaningful " +"variables." +msgstr "" + +#: ../../source/development/dev_practices.rst:68 +msgid "\\*char !\\*\\ *papszTokens*: Pointer to an array of strings." +msgstr "" + +#: ../../source/development/dev_practices.rst:69 +msgid "\\*int *panBands*: Pointer to the first element of an array of numbers." +msgstr "" + +#: ../../source/development/dev_practices.rst:71 +msgid "" +"\\*double *padfScanline*: Pointer to the first element of an array of " +"doubles." +msgstr "" + +#: ../../source/development/dev_practices.rst:73 +msgid "\\*double *pdfMeanRet*: Pointer to a single double." +msgstr "" + +#: ../../source/development/dev_practices.rst:74 +msgid "\\*GDALRasterBand *poBand*: Pointer to a single object." +msgstr "" + +#: ../../source/development/dev_practices.rst:75 +msgid "\\*GByte *pabyHeader*: Pointer to an array of bytes." +msgstr "" + +#: ../../source/development/dev_practices.rst:77 +msgid "" +"It may also be noted that the standard convention for variable names is " +"to capitalize each word in a variable name." +msgstr "" + +#: ../../source/development/dev_practices.rst:81 +msgid "Function and class naming" +msgstr "" + +#: ../../source/development/dev_practices.rst:83 +msgid "" +"Functions and classes should have a selective enough namespace (\"GDAL\" " +"or \"OGR\" prefix, or use of C++ namespace) to avoid symbol collision." +msgstr "" + +#: ../../source/development/dev_practices.rst:86 +msgid "File naming and code formatting" +msgstr "" + +#: ../../source/development/dev_practices.rst:88 +msgid "" +"All source files (.h, .c, .cpp, .py, etc.) should have a header with " +"copyright attribution and the text of the GDAL X/MIT license." +msgstr "" + +#: ../../source/development/dev_practices.rst:89 +msgid "Use lower case filenames." +msgstr "" + +#: ../../source/development/dev_practices.rst:90 +msgid "Use .cpp extension for C++ files (not .cc)." +msgstr "" + +#: ../../source/development/dev_practices.rst:91 +msgid "" +"C/C++ code formatting rules are defined in :source_file:`.clang-format`. " +"Python code formatting is enforced by Black. The pre-commit utility " +"should be used to enforce them automatically. See :ref:`commit_hooks`." +msgstr "" + +#: ../../source/development/dev_practices.rst:95 +msgid "Memory allocation" +msgstr "" + +#: ../../source/development/dev_practices.rst:97 +msgid "" +"Large memory allocations should be performed using the " +":cpp:func:`VSIMalloc` family of functions, which will return ``nullptr`` " +"on allocation failure. As per :ref:`rfc-19`, you can use ``VSIMalloc2(x, " +"y)`` instead of doing ``CPLMalloc(x * y)`` or ``VSIMalloc(x * y)``. " +":cpp:func:`VSIMalloc2` will detect potential overflows in the " +"multiplication and return a NULL pointer if it happens. This can be " +"useful in GDAL raster drivers where x and y are related to the raster " +"dimensions or raster block sizes. Similarly, ``VSIMalloc3(x, y, z)`` can " +"be used as a replacement for ``CPLMalloc(x * y * z)``." +msgstr "" + +#: ../../source/development/dev_practices.rst:105 +msgid "" +"When working with standard library data structures such as " +"``std::vector`` that may throw ``std::bad_alloc``, a try/catch block " +"should be used around blocks that may allocate a large amount of memory." +msgstr "" + +#: ../../source/development/dev_practices.rst:108 +msgid "Adding a new driver" +msgstr "" + +#: ../../source/development/dev_practices.rst:110 +msgid "" +"If the driver depends on a third-party library, compilation of the driver" +" must be made conditional on the presence of the library. Drivers should " +"try to re-use existing library dependencies as much as possible, e.g. " +"Expat for SAX XML parsing." +msgstr "" + +#: ../../source/development/dev_practices.rst:111 +msgid "" +"For a vector driver, check that the Open() method of the driver (often " +"delegated to a Open() method of the datasource) is selective enough (i.e." +" it will not accept data files that are not meant for the driver), and " +"robust enough (it will not crash for small variations w.r.t content that " +"it would recognize). Check that it can deal with unusual filenames. For a" +" GDAL driver, similar checks, as well for the optional Identify() method." +msgstr "" + +#: ../../source/development/dev_practices.rst:112 +msgid "" +"A set of tests covering the driver should be added to the Python test " +"suite. If appropriate, small sample data files may be added to " +"autotest/gdrivers/data or autotest/ogr/data. The ``test_ogrsf`` utility " +"and ``GDALTest`` class may simplify testing of basic driver " +"functionality." +msgstr "" + +#: ../../source/development/dev_practices.rst:113 +msgid "" +"A documentation page should be created for the driver. Documentation " +"should, at a minimum, briefly describe the format handled by the driver " +"and, when relevant, describe the particular syntax for the connection " +"string, creation options, configuration options, etc. The documentation " +"should provide a link to a more detailed format description and mention " +"needed third-party libraries." +msgstr "" + +#: ../../source/development/dev_practices.rst:116 +msgid "Writing tests" +msgstr "" + +#: ../../source/development/dev_practices.rst:118 +msgid "See :ref:`writing_tests`." +msgstr "" + +#: ../../source/development/dev_practices.rst:121 +msgid "Git usage" +msgstr "" + +#: ../../source/development/dev_practices.rst:123 +msgid "" +"This section collects a few best practices for git usage for GDAL " +"development." +msgstr "" + +#: ../../source/development/dev_practices.rst:126 +msgid "Initiating your work repository" +msgstr "" + +#: ../../source/development/dev_practices.rst:128 +msgid "Fork |OSGeo/gdal| from the GitHub UI, and then run:" +msgstr "" + +#: ../../source/development/dev_practices.rst:137 +msgid "Working with a feature branch" +msgstr "" + +#: ../../source/development/dev_practices.rst:173 +msgid "From the GitHub UI, issue a pull request." +msgstr "" + +#: ../../source/development/dev_practices.rst:175 +msgid "" +"If the pull request discussion or automated checks require changes, " +"commit locally and push. To get a reasonable history, you may need to " +"combine commits using ``git rebase -i master``, in which case you will " +"have to force-push your branch with ``git push -f my_user_name " +"my_new_feature_branch``." +msgstr "" + +#: ../../source/development/dev_practices.rst:182 +msgid "Updating your local master against upstream master" +msgstr "" + +#: ../../source/development/dev_practices.rst:193 +msgid "Commit messages" +msgstr "" + +#: ../../source/development/dev_practices.rst:195 +msgid "" +"Commit messages should indicate a component name (eg a driver name), a " +"short description, and when relevant, a reference to a issue (with 'fixes" +" #' if it actually fixes it)" +msgstr "" + +#: ../../source/development/dev_practices.rst:208 +msgid "Commit hooks" +msgstr "" + +#: ../../source/development/dev_practices.rst:210 +msgid "" +"GDAL provides pre-commit hooks to run code formatters and linters before " +"a commit is made. The hooks are cloned with the repository and can be " +"installed using `pre-commit `_:" +msgstr "" + +#: ../../source/development/dev_practices.rst:220 +msgid "" +"Once installed, the hooks can be run manually via ``pre-commit run --all-" +"files``." +msgstr "" + +#: ../../source/development/dev_practices.rst:223 +msgid "Blame ignore file" +msgstr "" + +#: ../../source/development/dev_practices.rst:225 +msgid "" +"Due to whole-tree code reformatting done during GDAL 3.7 development, " +"``git blame`` information might be misleading. To avoid that, you need to" +" modify your git configuration as following to ignore the revision of the" +" whole-tree reformatting:" +msgstr "" + +#: ../../source/development/dev_practices.rst:236 +msgid "Backporting bugfixes from master to a stable branch" +msgstr "" + +#: ../../source/development/dev_practices.rst:248 +msgid "If changes are needed, do them and ``git commit -a --amend``" +msgstr "" + +#: ../../source/development/dev_practices.rst:252 +msgid "Things you should NOT do" +msgstr "" + +#: ../../source/development/dev_practices.rst:254 +msgid "" +"(For anyone with push rights to |OSGeo/gdal|) Never modify a commit or " +"the history of anything that has been committed to " +"https://github.com/OSGeo/gdal" +msgstr "" + +#: ../../source/development/dev_practices.rst:258 +msgid "" +"Committing symbolic links is allowed only under the .github directory in " +"order to avoid potential problems on Windows." +msgstr "" + +#: ../../source/development/index.rst:6 +#: ../../source/development/rfc/rfc14_imagestructure.rst:66 +msgid "Development" +msgstr "" + +#: ../../source/development/rfc/index.rst:5 +msgid "RFC list" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:5 +msgid "RFC 10: OGR Open Parameters (not implemented)" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:7 +#: ../../source/development/rfc/rfc5_unicode.rst:7 +msgid "Author: Andrey Kiselev" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:9 +#: ../../source/development/rfc/rfc5_unicode.rst:9 +msgid "Contact: dron@ak4719.spb.edu" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:11 +msgid "Status: Development, *not* implemented" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:14 +#: ../../source/development/rfc/rfc11_fastidentify.rst:14 +#: ../../source/development/rfc/rfc12_filemanagement.rst:14 +#: ../../source/development/rfc/rfc14_imagestructure.rst:14 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:14 +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:14 +#: ../../source/development/rfc/rfc17_python_namespaces.rst:14 +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:14 +#: ../../source/development/rfc/rfc19_safememalloc.rst:14 +#: ../../source/development/rfc/rfc1_pmc.rst:14 +#: ../../source/development/rfc/rfc20_srs_axes.rst:14 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:14 +#: ../../source/development/rfc/rfc22_rpc.rst:14 +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:14 +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:14 +#: ../../source/development/rfc/rfc25_fast_open.rst:15 +#: ../../source/development/rfc/rfc27_supportdata.rst:14 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:14 +#: ../../source/development/rfc/rfc29_desired_fields.rst:14 +#: ../../source/development/rfc/rfc2_svn.rst:14 +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:14 +#: ../../source/development/rfc/rfc31_ogr_64.rst:14 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:14 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:14 +#: ../../source/development/rfc/rfc34_license_policy.rst:14 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:14 +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:16 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:16 +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:14 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:8 +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:12 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:12 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:14 +#: ../../source/development/rfc/rfc45_virtualmem.rst:14 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:14 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:14 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:14 +#: ../../source/development/rfc/rfc4_geolocate.rst:14 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:14 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:14 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:14 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:14 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:14 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:14 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:16 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:16 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:16 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:16 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:14 +#: ../../source/development/rfc/rfc5_unicode.rst:14 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:16 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:16 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:16 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:16 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:16 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:16 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:16 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:16 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:19 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:24 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:14 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:16 +#: ../../source/development/rfc/rfc71_github_migration.rst:15 +#: ../../source/development/rfc/rfc72_pytest.rst:15 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:16 +#: ../../source/development/rfc/rfc74_sphinx.rst:16 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:16 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:16 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:16 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:16 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:16 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:17 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:15 +#: ../../source/development/rfc/rfc84_cmake.rst:19 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:15 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:17 +#: ../../source/development/rfc/rfc87_signed_int8.rst:16 +#: ../../source/development/rfc/rfc88_googletest.rst:16 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:16 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:16 +#: ../../source/development/rfc/rfc91_dataset_close.rst:16 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:16 +#: ../../source/development/rfc/rfc93_update_feature.rst:16 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:16 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:16 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:16 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:16 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:15 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:16 +msgid "Summary" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:16 +msgid "" +"It is proposed that OGRSFDriver::Open() and OGRSFDriverRegistrar::Open() " +"calls should be changed to accept additional parameter containing " +"arbitrary additional parameters supplied by caller. OGROpenEx() function " +"will be introduced to map this new functionality into C interface. In " +"addition it is proposed to add an \"update\" flag to " +"OGRSFDriverRegistrar::Open() call to avoid using " +"OGRSFDriverRegistrar::OpenShared() method." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:25 +msgid "Open parameters" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:27 +msgid "" +"Sometimes it is needed to pass additional information to OGR driver along" +" with the name of the dataset to be opened. It can be, for example, the " +"style table name (some drivers allow to choose from the various style " +"tables) or any other additional data. The old method for doing this was " +"to encode the extra info in the dataset name string. It was inconvenient " +"approach, so it proposed to use separate parameter in OGRSFDriver::Open()" +" and OGRSFDriverRegistrar::Open() calls representing open options, just " +"like it is implemented in OGRDataSource::CreateLayer() call." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:37 +msgid "" +"It is supposed that open options will be supplied in form of NAME=VALUE " +"pairs forming the string list." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:40 +msgid "" +"In addition to options parameter the special \"shared\" flag will be " +"added to OGRSFDriverRegistrar::Open() call, so there will be no need in " +"separate OGRSFDriverRegistrar::OpenShared() method." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:45 +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:139 +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:106 +#: ../../source/development/rfc/rfc20_srs_axes.rst:217 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:101 +#: ../../source/development/rfc/rfc22_rpc.rst:266 +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:165 +#: ../../source/development/rfc/rfc25_fast_open.rst:24 +#: ../../source/development/rfc/rfc26_blockcache.rst:114 +#: ../../source/development/rfc/rfc26_blockcache.rst:210 +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:206 +#: ../../source/development/rfc/rfc31_ogr_64.rst:378 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:114 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:129 +#: ../../source/development/rfc/rfc34_license_policy.rst:232 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:278 +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:47 +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:101 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:38 +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:39 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:639 +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:19 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:29 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:29 +#: ../../source/development/rfc/rfc45_virtualmem.rst:1259 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:679 +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:89 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:613 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:169 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:253 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:56 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:500 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:590 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:85 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:167 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:133 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:105 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:782 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:202 +#: ../../source/development/rfc/rfc5_unicode.rst:79 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:285 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:394 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:134 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:279 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:480 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:90 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:276 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:192 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:243 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:191 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:53 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:118 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:530 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:225 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:454 +#: ../../source/development/rfc/rfc7_vsilapi.rst:96 +msgid "Implementation" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:47 +msgid "All Open() functions will be changed in the following way:" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:71 +msgid "" +"The last change needs to be propagated in all OGR drivers. The change " +"itself is pretty simple: one additional parameter should be added to " +"function definition. But it has impact on third-party OGR drivers: they " +"are not source compatible anymore and should be changed too." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:76 +msgid "Also appropriate C functions will be added:" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:90 +msgid "New Options for OGR Utilities" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:92 +msgid "" +"Proposed functionality will be available in OGR utilities ogr2ogr and " +"ogrinfo via the '-doo NAME=VALUE' (\"Datasource Open Option\") format " +"specific parameter." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:97 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:126 +#: ../../source/development/rfc/rfc26_blockcache.rst:178 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:65 +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:50 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:224 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:332 +#: ../../source/development/rfc/rfc5_unicode.rst:174 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:415 +msgid "Backward Compatibility" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:99 +msgid "" +"Proposed additions will not have any impact on C binary compatibility. " +"C++ binary interface will be broken, source level compatibility will be " +"broken for third-party OGR drivers only. There will be no impact for " +"high-level applications on source level." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:105 +msgid "Responsibility and Timeline" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:107 +msgid "" +"Andrey Kiselev is responsible to implement this proposal. New API will be" +" available in GDAL 1.5.0." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:5 +msgid "RFC 11: Fast Format Identification" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:7 +#: ../../source/development/rfc/rfc12_filemanagement.rst:7 +#: ../../source/development/rfc/rfc14_imagestructure.rst:7 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:7 +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:7 +#: ../../source/development/rfc/rfc1_pmc.rst:7 +#: ../../source/development/rfc/rfc20_srs_axes.rst:7 +#: ../../source/development/rfc/rfc22_rpc.rst:7 +#: ../../source/development/rfc/rfc27_supportdata.rst:7 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:7 +#: ../../source/development/rfc/rfc2_svn.rst:7 +#: ../../source/development/rfc/rfc3_commiters.rst:7 +#: ../../source/development/rfc/rfc4_geolocate.rst:7 +#: ../../source/development/rfc/rfc8_devguide.rst:7 +#: ../../source/development/rfc/rfc9_maintainer.rst:7 +msgid "Author: Frank Warmerdam" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:9 +#: ../../source/development/rfc/rfc12_filemanagement.rst:9 +#: ../../source/development/rfc/rfc14_imagestructure.rst:9 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:9 +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:9 +#: ../../source/development/rfc/rfc1_pmc.rst:9 +#: ../../source/development/rfc/rfc20_srs_axes.rst:9 +#: ../../source/development/rfc/rfc22_rpc.rst:9 +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:9 +#: ../../source/development/rfc/rfc25_fast_open.rst:9 +#: ../../source/development/rfc/rfc27_supportdata.rst:9 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:9 +#: ../../source/development/rfc/rfc2_svn.rst:9 +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:9 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:9 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:9 +#: ../../source/development/rfc/rfc34_license_policy.rst:9 +#: ../../source/development/rfc/rfc3_commiters.rst:9 +#: ../../source/development/rfc/rfc4_geolocate.rst:9 +#: ../../source/development/rfc/rfc8_devguide.rst:9 +#: ../../source/development/rfc/rfc9_maintainer.rst:9 +msgid "Contact: warmerdam@pobox.com" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:11 +msgid "Status: Adopted (and Implemented)" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:16 +msgid "" +"This RFC aims to add the ability for applications to quickly identify " +"what files in the file system are GDAL supported file formats without " +"necessarily opening any of them. It is mainly intended to allow GUI file " +"browsers based on file types." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:21 +msgid "" +"This is accomplished by extending the GDALOpenInfo structure to hold more" +" directory context, and by adding an Identify() method on the GDALDriver " +"which a driver can implement to quickly identify that a file is of a " +"given format without doing a more expensive Open() operation." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:27 +msgid "GDALOpenInfo" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:29 +msgid "" +"The Open() (or Identify()) methods of many drivers need to probe for " +"files associated with the target file in order to open or identify a file" +" as being of a particular format. For instance, in order to open an ESRI " +"BIL file (EHDR driver) it is necessary to probe for a driver with the " +"same basename as the target file, but the extension .hdr. Currently this " +"is typically accomplished with VSIFStatL() calls or similar which can be " +"fairly expensive." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:37 +msgid "" +"In order to reduce the need for such searches touch the operating system " +"file system machinery, the GDALOpenInfo structure will be extended to " +"hold an optional list of files. This is the list of all files at the same" +" level in the file system as the target file, including the target file. " +"The filenames will *not* include any path components, are an essentially " +"just the output of CPLReadDir() on the parent directory. If the target " +"object does not have filesystem semantics then the file list should be " +"NULL." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:46 +msgid "The following is added to GDALOpenInfo:" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:53 +msgid "" +"The new constructor allows the file list to be passed in to populate the " +"papszSiblingFiles member (the argument will be copied). The existing " +"default constructor will use CPLGetDirname() to get the directory of the " +"passed pszFile, and CPLReadDir() to read the corresponding file list. The" +" new constructor is primarily aimed at efficient implementation of the " +"later GDALIdentifyDriver() function, avoiding re-reading the file list " +"for each file to be tested." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:62 +msgid "Identify()" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:64 +msgid "The GDALDriver class will be extended with the following function:" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:70 +msgid "" +"When implemented by a driver, the function is intended to return TRUE " +"(non-zero) if the driver determines that the file passed in via " +"GDALOpenInfo appears to be of the format the driver is implemented for. " +"To call this applications should call the new function:" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:79 +msgid "Internally GDALIdentifyDriver() will do the following" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:81 +msgid "" +"A GDALOpenInfo structure will be initialized based on pszDatasource and " +"papszDirFiles." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:83 +msgid "" +"It will iterate over all drivers similarly to GDALOpen(). For each driver" +" it will use the pfnIdentify function if available, otherwise it will use" +" the pfnOpen() method to establish if the driver supports the file." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:87 +msgid "" +"It will return the driver handle for the first driver to respond " +"positively or NULL if none accept it." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:91 +msgid "Driver Changes" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:93 +msgid "" +"In theory it is not necessary for any drivers to be modified, since " +"GDALIdentifyDriver() will fallback to using the pfnOpen function to test." +" But in practice, no optimization is achieved unless at least some " +"drivers (hopefully those for which Open can be very expensive) are " +"updated. Part of the ongoing effort then is to implement identify " +"functions for GDAL drivers." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:100 +msgid "" +"Generally speaking it should be easy to craft an identify function from " +"the initial test logic in the open function. For instance, the GeoTIFF " +"driver might be changed like this:" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:139 +msgid "" +"The open might then be modified to use the identify function to avoid " +"duplicating the test logic." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:162 +msgid "" +"Drivers which require header files such as the EHdr driver might " +"implement Identify() like this:" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:192 +msgid "" +"During the initial implementation a variety of drivers will be updated, " +"including the following. As well some performance and file system " +"activity logging will be done to identify drivers that are currently " +"expensive." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:197 +msgid "HFA" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:198 +msgid "GTiff" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:203 +msgid "DTED" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:204 +msgid "USGS DEM" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:205 +msgid "MrSID" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:206 +#: ../../source/development/rfc/rfc34_license_policy.rst:181 +msgid "JP2KAK" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:208 +msgid "EHdr" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:209 +msgid "RST" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:212 +msgid "CPLReadDir()" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:214 +msgid "" +"Currently the VSIMemFilesystemHandler implemented in cpl_vsi_mem.cpp " +"which provides \"filesystem like\" access to objects in memory does not " +"implement directory reading services. In order to properly populate the " +"directory listing this will need to be added." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:219 +msgid "" +"To do this the CPLReadDir() function will also need to be reimplemented " +"to use VSIFilesystemHandler::ReadDir() instead of direct implementation " +"in cpl_dir.cpp. The win32 and unix/posix implementations of " +"VSIFilesystemHandler::ReadDir() already exist. This should essentially " +"complete the virtualization of filesystem access services." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:225 +msgid "" +"CPLReadDir() will also be renamed VSIReadDir() but with a stub under the " +"old name available for backward compatibility." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:229 +#: ../../source/development/rfc/rfc29_desired_fields.rst:115 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:628 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:146 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:220 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:70 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:138 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:108 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:462 +#: ../../source/development/rfc/rfc84_cmake.rst:133 +msgid "Compatibility" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:231 +msgid "" +"There are no anticipated backward compatibility problems. However forward" +" compatibility will be affected, in that drivers updated in trunk with " +"the Identify function will not be able to be ported back into 1.4 builds " +"and used their. Unmodified drivers, and externally maintained drivers " +"should not be impacted by this development." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:238 +#: ../../source/development/rfc/rfc12_filemanagement.rst:192 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:176 +msgid "SWIG Implications" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:240 +msgid "" +"The GDALIdentifyDriver() and VSIReadDir() functions will need to be " +"exposed via SWIG." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:244 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:429 +msgid "Regression Testing" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:246 +msgid "" +"A test script for the Identify() function will be added to the " +"autotest/gcore directory. It will include testing of identify in a " +"/vsimem memory collection." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:251 +#: ../../source/development/rfc/rfc12_filemanagement.rst:186 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:170 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:169 +msgid "Implementation Plan" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:253 +msgid "" +"The new features will be implemented by Frank Warmerdam in *trunk* for " +"the GDAL/OGR 1.5.0 release." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:257 +msgid "Performance Tests" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:259 +msgid "" +"A very quick test introducing the Identify without actually opening " +"changed the time to identify all files in a directory with 70 TIFF files " +"(on an NFS share) from 2 seconds to 0.5 seconds. So saving the overhead " +"of actually opening files can be significant for some formats, including " +"very common ones like GeoTIFF." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:5 +msgid "RFC 12: Improved File Management" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:11 +msgid "Status: Adopted / Implemented" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:16 +msgid "" +"Some applications using GDAL have a requirement to provide file " +"management operations through the GUI. This includes deleting, renaming, " +"moving and packaging up datasets which often requires operations on " +"several associated files. This RFC introduces an operation on a " +"GDALDataset to identify all the dataset files, and operations to move or " +"copy them." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:24 +msgid "GetFileList()" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:26 +msgid "" +"The following new virtual method is added on the GDALDataset class, with " +"an analygous C function." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:33 +msgid "" +"The method is intended to return a list of files associated with this " +"open dataset. The return is a NULL terminated string list which becomes " +"owned by the caller and should be deallocated with CSLDestroy()." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:37 +msgid "" +"The default implementation tests the name of the datasource to see if it " +"is a file, and if so it is returned otherwise an empty list is returned. " +"If the default overview manager is active, and has overviews, those will " +"also be included in the file list. The default implementation also checks" +" for world files, but only those with extensions based on the original " +"files extension (ie. .tfw or .tifw for .tif) but does not search for .wld" +" since that is not very specific." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:45 +msgid "" +"The GDALPamDataset::GetFileList() method will add the ability to find " +".aux and .aux.xml files associated with a dataset to the core default " +"behavior." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:50 +msgid "pfnRename()" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:52 +#: ../../source/development/rfc/rfc12_filemanagement.rst:105 +msgid "The following new function is added to the GDALDriver class." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:58 +#: ../../source/development/rfc/rfc12_filemanagement.rst:111 +msgid "Also a corresponding function is added to the C API." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:64 +msgid "" +"Note that renaming is done by the driver, but the dataset to be operated " +"on should *not* be open at the time. GDALRenameDataset() will invoke " +"pfnRename if it is non-NULL." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:68 +msgid "" +"If pfnRename is NULL the default implementation will be used which will " +"open the dataset, fetch the file list, close the dataset, and then try to" +" rename all the files (based on shared basenames). The default rename " +"operation will fail if it is unable to establish a relationship between " +"the files (ie. a common basename or stem) to indicate how the group of " +"files should be rename to the new pattern." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:75 +#: ../../source/development/rfc/rfc12_filemanagement.rst:129 +msgid "" +"Optionally a NULL hDriver argument may be passed in, in which case the " +"appropriate driver will be selected by first opening the datasource." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:79 +msgid "CPLMoveFile()" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:81 +msgid "" +"The POSIX rename() function on which VSIRename() is usually based does " +"not normally allow renaming files between file systems or between " +"different kinds of file systems (ie. /vsimem to C:/abc). In order to " +"implement GDALRenameDataset() such that it works efficiently within a " +"file system, but still works between file systems, a new operation will " +"be added to gdal/port. This is the CPLMoveFile() function which will " +"first try a VSIRename(). If that fails it will use CPLCopyFile() to copy " +"the whole file and then VSIUnlink() to get rid of the old file." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:94 +msgid "The return value will be zero on success, otherwise an errno style value." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:97 +msgid "" +"It should be noted that in some error conditions, such as the destination" +" file system running out of space during a copy, it may happen that some " +"files for a dataset get renamed, and some do not leaving things in an " +"inconsistent state." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:103 +msgid "pfnCopyFiles()" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:117 +msgid "" +"Note that copying is done by the driver. The dataset may be opened, but " +"if opened in update mode it may be prudent to first do a flush to " +"synchronize the in-process state with what is on disk. " +"GDALCopyDatasetFiles() will invoke pfnCopyFiles if it is non-NULL." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:122 +msgid "" +"If pfnCopy is NULL the default implementation will be used which will " +"open the dataset, fetch the file list, close the dataset, and then try to" +" copy all the files (based on shared basenames). The default copy " +"operation will fail if it is unable to establish a relationship between " +"the files (ie. a common basename or stem) to indicate how the group of " +"files should be renamed to the new pattern." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:132 +msgid "" +"Copy is essentially the same as Rename, but the original files are " +"unaltered. Note that this form of copy is distinct from CreateCopy() in " +"that it preserves the exact binary files on disk in the new location " +"while CreateCopy() just attempts to reproduce a new dataset with " +"essentially the same data as modelled and carried through GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:139 +msgid "pfnDelete()" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:142 +msgid "" +"The delete operations default implementation will be extended to use the " +"GetFileList() results." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:146 +msgid "Supporting Functions" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:148 +msgid "" +"Some sort of supporting functions should be provided to make it easy to " +"identify worldfiles, .aux files and .prj files associated with a file." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:152 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:144 +msgid "Drivers Updated" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:154 +msgid "" +"It is anticipated that a majority of the commonly used drivers will be " +"updated with custom GetFileList() methods that account for world files " +"and other idiosyncratic files. A particular emphasis will made to handle " +"the various formats in gdal/frmts/raw that consist of a header file and a" +" raw binary file." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:160 +msgid "" +"Drivers for \"one file formats\" that are not updated will still use the " +"default logic which should work fairly well, but might neglect auxiliary " +"world files." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:164 +msgid "" +"VRT: I do not anticipate updating the VRT driver at this time since it " +"gets quite complicated to collect a file list for some kinds of virtual " +"files. It is also not exactly clear whether related files should be " +"considered \"owned\" by the virtual dataset or not." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:168 +msgid "" +"AIGRID: I will implement a custom rename operation in an attempt to " +"handle this directory oriented format gracefully." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:172 +msgid "Additional Notes" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:174 +msgid "" +"Subdatasets will generally return an empty file list from GetFileList(), " +"and will not be manageable via Rename or Delete though a very " +"sophisticated driver could implement these operations." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:177 +msgid "" +"There is no mechanism anticipated to ensure that files are closed before " +"they are removed. If an application does not ensure this rename/move " +"operations may fail on win32 since it doesn't allow rename/delete " +"operations on open files. Things could easily be left in an inconsistent " +"state." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:182 +msgid "" +"Datasets without associated files in the file system will return an empty" +" file list. This essentially identifies them as \"unmanagable\"." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:188 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:172 +msgid "" +"This change will be implemented by Frank Warmerdam in trunk in time for " +"the 1.5.0 release." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:194 +msgid "" +"The GDALRenameDataset(), and GDALCopyDatasetFiles() operations on the " +"driver, and the GetFileList() operation on the dataset will need to be " +"exposed through SWIG." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:199 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:184 +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:128 +#: ../../source/development/rfc/rfc22_rpc.rst:272 +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:228 +#: ../../source/development/rfc/rfc25_fast_open.rst:100 +#: ../../source/development/rfc/rfc26_blockcache.rst:198 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:175 +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:66 +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:92 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:231 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:340 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:664 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:605 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:160 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:242 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:100 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:159 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:127 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:472 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:230 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:112 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:513 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:219 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:439 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:209 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:212 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:80 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:410 +#: ../../source/development/rfc/rfc87_signed_int8.rst:99 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:126 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:403 +#: ../../source/development/rfc/rfc91_dataset_close.rst:174 +#: ../../source/development/rfc/rfc93_update_feature.rst:257 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:161 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:168 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:486 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:306 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:139 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:683 +msgid "Testing" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:201 +msgid "" +"Rename and CopyFiles testing will be added to the regression tests for a " +"few representative formats. These rename operations will be between one " +"directory and another, and will not test cross file system copying which " +"will have to be tested manually." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:206 +msgid "" +"A small gdalmanage utility will be implemented allowing use and testing " +"of the identify, rename, copy and delete operations from the commandline " +"in a convenient fashion." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:5 +msgid "RFC 13: Improved Feature Insertion/Update/Delete Performance in Batch Mode" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:15 +msgid "*Withdrawn*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:17 +msgid "" +"I have withdrawn this RFC based on some comments from `Frank " +"`__ and " +"`Tamas `__ on GDAL-dev." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:23 +msgid "*Summary*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:25 +msgid "" +"Some OGR drivers can dramatically increase the speed of and optimize the " +"insertion, update, and deletion of a set of features, if the driver " +"knows, that there is a whole set of features that should/could be " +"inserted, updated, or deleted at once (instead of just one by one)." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:30 +msgid "*CreateFeatures()*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:32 +#: ../../source/development/rfc/rfc13_createfeatures.rst:61 +#: ../../source/development/rfc/rfc13_createfeatures.rst:90 +msgid "" +"The following new virtual method is added to the OGRLayer class, with an " +"analogous C function:" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:39 +#: ../../source/development/rfc/rfc13_createfeatures.rst:68 +#: ../../source/development/rfc/rfc13_createfeatures.rst:97 +msgid "A default implementation is given as below:" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:54 +msgid "This triggers the old behavior of an unoptimized insertion." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:56 +msgid "" +"Individual drivers can override the default implementation and can " +"implement an optimized algorithm for inserting a set of features." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:59 +msgid "*SetFeatures()*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:83 +msgid "This triggers the old behavior of an unoptimized update." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:85 +msgid "" +"Individual drivers can override the default implementation and can " +"implement an optimized algorithm for updating a set of features." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:88 +msgid "*DeleteFeatures()*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:112 +msgid "This triggers the old behavior of an unoptimized deletion." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:114 +msgid "" +"Individual drivers can override the default implementation and can " +"implement an optimized algorithm for deleting a set of features." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:117 +msgid "*C API functions*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:119 +msgid "The following C functions are added:" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:127 +msgid "" +"However, there are some issues with adding plain C arrays to the public " +"OGR interface due to the SWIG based wrapping, see for example `GDAL-Dev " +"Mail from Tamas `__..." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:132 +msgid "*Additional Notes*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:134 +msgid "" +"Based in this new interface functions, I was able to increase the " +"insertion speed of features in the MySQL driver from 40 per second to up " +"to 800-2000 per second. I think other drivers can benefit from this " +"change, too." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:139 +msgid "See also ticket #1633." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:141 +msgid "*Implementation Plan*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:143 +msgid "A patch for the describe additions can be trivially provided." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:145 +msgid "" +"I can provide another patch based on this interface which contains the " +"optimized implementation for the MySQL driver." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:148 +msgid "*History*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:150 +msgid "14-May-2007: initial version created" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:152 +msgid "15-May-2007: SetFeatures() added" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:154 +msgid "16-May-2007: DeleteFeatures() added" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:156 +msgid "17-May-2007: C API functions added; SWIG wrapping issues mentioned" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:158 +msgid "23-May-2007: Withdrawn due some concerns on GDAL-dev" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:5 +msgid "RFC 14: Image Structure Metadata" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:11 +msgid "Status: Adopted, amended per :ref:`rfc-87`" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:16 +msgid "" +"This RFC attempts to formalize the semantics of the \"IMAGE_STRUCTURE\" " +"domain of metadata. This metadata domain is used to hold structural " +"information about image organization that would not normally be carried " +"with an image when translated into another format. The IMAGE_STRUCTURE " +"metadata may occur on the GDALDataset or on individual bands, and most " +"items are meaningful in both contexts. When items like NBITS are found on" +" the dataset it is assumed they apply to all bands of that dataset." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:25 +msgid "IMAGE_STRUCTURE items" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:27 +msgid "" +"COMPRESSION:: The compression type used for this dataset or band. There " +"is no fixed catalog of compression type names, but where a given format " +"includes a COMPRESSION creation option, the same list of values should be" +" used here as there." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:32 +msgid "" +"NBITS:: The actual number of bits used for this band, or the bands of " +"this dataset. Normally only present when the number of bits is non-" +"standard for the datatype, such as when a 1 bit TIFF is represented " +"through GDAL as GDT_Byte." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:37 +msgid "" +"INTERLEAVE:: This only applies on datasets, and the value should be one " +"of PIXEL, LINE or BAND. It can be used as a data access hint." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:40 +msgid "" +"PIXELTYPE:: This may appear on a GDT_Byte band (or the corresponding " +"dataset) and have the value SIGNEDBYTE to indicate the unsigned byte " +"values between 128 and 255 should be interpreted as being values between " +"-128 and -1 for applications that recognise the SIGNEDBYTE type." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:47 +msgid "" +"Starting with GDAL 3.7, with the implementation of :ref:`rfc-87`, " +"PIXELTYPE is no longer used, as the Int8 data type is used for signed " +"bytes." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:51 +#: ../../source/development/rfc/rfc20_srs_axes.rst:224 +#: ../../source/development/rfc/rfc31_ogr_64.rst:306 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:70 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:237 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:447 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:549 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:79 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:94 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:772 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:169 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:274 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:351 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:128 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:274 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:79 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:262 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:164 +msgid "Compatibility Issues" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:53 +msgid "" +"This RFC has two changes from existing practise that may cause " +"compatibility issues:" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:56 +msgid "" +"Traditionally the NBITS metadata appeared in the default metadata domain " +"on datasets, instead of in the IMAGE_STRUCTURE domain." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:58 +msgid "" +"Traditionally the COMPRESSION metadata appeared only on the dataset, " +"never one the band." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:61 +msgid "" +"I am only aware of one application previously making systematic use of " +"these items, and it will be updated to reflect the new usage as GDAL " +"1.5.0 is adopted." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:68 +msgid "" +"Beyond adopting the definition for the semantics of the IMAGE_STRUCTURE " +"metadata, the following development steps will be taken:" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:71 +msgid "" +"The PNG, GTiff, NITF and EHdr drivers will be updated to place NBITS in " +"the IMAGE_STRUCTURE metadata domain." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:73 +msgid "The HFA driver will be updated to return NBITS metadata." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:74 +msgid "" +"The HFA, GTiff, JP2KAK, ECW, JPEG, and PNG drivers will be updated to " +"return INTERLEAVE metadata." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:76 +msgid "The HFA and GTiff drivers will be updated to return PIXELTYPE metadata." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:79 +msgid "" +"The development will be done by Frank Warmerdam in trunk in time for " +"GDAL/OGR 1.5.0 release. Changes to other drivers that these definitions " +"might be useful for while be done as time permits by interested " +"developers - not necessarily in time for GDAL/OGR 1.5.0." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:85 +msgid "Notes" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:87 +msgid "" +"The gdalinfo utility already reports IMAGE_STRUCTURE metadata when it is " +"available." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:89 +msgid "" +"The GTiff, and HFA drivers CreateCopy() methods check the source for " +"NBITS, and PIXELTYPE metadata to create specialized output files types." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:92 +msgid "" +"The GTiff, HFA and default CreateCopy() implementations have been " +"reworked to use the new GDALDatasetCopyWholeRaster() function which uses " +"the INTERLEAVE metadata as a clue whether to do interleaved copies if the" +" source dataset is interleaved." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:5 +msgid "RFC 15: Band Masks" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:11 +#: ../../source/development/rfc/rfc17_python_namespaces.rst:11 +#: ../../source/development/rfc/rfc1_pmc.rst:11 +#: ../../source/development/rfc/rfc20_srs_axes.rst:11 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:11 +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:11 +#: ../../source/development/rfc/rfc29_desired_fields.rst:11 +#: ../../source/development/rfc/rfc2_svn.rst:11 +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:11 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:11 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:11 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:11 +#: ../../source/development/rfc/rfc3_commiters.rst:11 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:11 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:11 +#: ../../source/development/rfc/rfc7_vsilapi.rst:11 +msgid "Status: Adopted" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:16 +msgid "" +"Some file formats support a concept of a bitmask to identify pixels that " +"are not valid data. This can be particularly valuable with byte image " +"formats where a nodata pixel value can not be used because all pixel " +"values have a valid meaning. This RFC tries to formalize a way of " +"recognising and accessing such null masks through the GDAL API, while " +"moving to a uniform means of representing other kinds of masking (nodata " +"values, and alpha bands)." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:24 +msgid "" +"The basic approach is to treat such masks as raster bands, but not " +"regular raster bands on the datasource. Instead they are freestanding " +"raster bands in a manner similar to the overview raster band objects. The" +" masks are represented as GDT_Byte bands with a value of zero indicating " +"nodata and non-zero values indicating valid data. Normally the value 255 " +"will be used for valid data pixels." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:32 +msgid "API" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:34 +msgid "GDALRasterBand is extended with the following methods:" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:42 +msgid "GDALDataset is extended with the following method:" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:48 +msgid "" +"Note that the GetMaskBand() should always return a GDALRasterBand mask, " +"even if it is only an all 255 mask with the flags indicating " +"GMF_ALL_VALID." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:52 +msgid "" +"The GetMaskFlags() method returns an bitwise OR-ed set of status flags " +"with the following available definitions that may be extended in the " +"future:" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:56 +msgid "" +"GMF_ALL_VALID(0x01): There are no invalid pixels, all mask values will be" +" 255. When used this will normally be the only flag set." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:58 +msgid "" +"GMF_PER_DATASET(0x02): The mask band is shared between all bands on the " +"dataset." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:60 +msgid "" +"GMF_ALPHA(0x04): The mask band is actually an alpha band and may have " +"values other than 0 and 255." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:62 +msgid "" +"GMF_NODATA(0x08): Indicates the mask is actually being generated from " +"nodata values. (mutually exclusive of GMF_ALPHA)" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:65 +msgid "" +"The CreateMaskBand() method will attempt to create a mask band associated" +" with the band on which it is invoked, issuing an error if it is not " +"supported. Currently the only flag that is meaningful to pass in when " +"creating a mask band is GMF_PER_DATASET. The rest are used to represent " +"special system provided mask bands. GMF_PER_DATASET is assumed when " +"CreateMaskBand() is called on a dataset." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:73 +msgid "Default GetMaskBand() / GetMaskFlags() Implementation" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:75 +msgid "" +"The GDALRasterBand class will include a default implementation of " +"GetMaskBand() that returns one of three default implementations." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:78 +msgid "If a corresponding .msk file exists it will be used for the mask band." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:80 +msgid "" +"If the band has a nodata value set, an instance of the new " +"GDALNodataMaskRasterBand class will be returned. GetMaskFlags() will " +"return GMF_NODATA." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:83 +msgid "" +"If there is no nodata value, but the dataset has an alpha band that seems" +" to apply to this band (specific rules yet to be determined) and that is " +"of type GDT_Byte then that alpha band will be returned, and the flags " +"GMF_PER_DATASET and GMF_ALPHA will be returned in the flags." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:88 +msgid "" +"If neither of the above apply, an instance of the new " +"GDALAllValidRasterBand class will be returned that has 255 values for all" +" pixels. The null flags will return GMF_ALL_VALID." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:92 +msgid "" +"The GDALRasterBand will include a protected poMask instance variable and " +"a bOwnMask flag. The first call to the default GetMaskBand() will result " +"in creation of the GDALNodataMaskRasterBand, GDALAllValidMaskRasterBand " +"and their assignment to poMask with bOwnMask set TRUE. If an alpha band " +"is identified for use, it will be assigned to poMask and bOwnMask set to " +"FALSE. The GDALRasterBand class will take care of deleting the poMask if " +"set and bOwnMask is true in the destructor. Derived band classes may " +"safely use the poMask and bOwnMask flag similarly as long as the " +"semantics are maintained." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:102 +msgid "" +"For an external .msk file to be recognized by GDAL, it must be a valid " +"GDAL dataset, with the same name as the main dataset and suffixed with " +".msk, with either one band (in the GMF_PER_DATASET case), or as many " +"bands as the main dataset. It must have INTERNAL_MASK_FLAGS_xx metadata " +"items set at the dataset level, where xx matches the band number of a " +"band of the main dataset. The value of those items is a combination of " +"the flags GMF_ALL_VALID, GMF_PER_DATASET, GMF_ALPHA and GMF_NODATA. If a " +"metadata item is missing for a band, then the other rules explained above" +" will be used to generate a on-the-fly mask band." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:113 +msgid "Default CreateMaskBand()" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:115 +msgid "" +"The default implementation of the CreateMaskBand() method will be " +"implemented based on similar rules to the .ovr handling implemented using" +" the GDALDefaultOverviews object. A TIFF file with the extension .msk " +"will be created with the same basename as the original file, and it will " +"have as many bands as the original image (or just one for " +"GMF_PER_DATASET). The mask images will be deflate compressed tiled images" +" with the same block size as the original image if possible." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:123 +msgid "" +"The default implementation of GetFileList() will also be modified to know" +" about the .msk files." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:127 +msgid "CreateCopy()" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:129 +msgid "" +"The GDALDriver::DefaultCreateCopy(), and GDALPamDataset::CloneInfo() " +"methods will be updated to copy mask information if it seems necessary " +"and is possible. Note that NODATA, ALL_VALID and ALPHA type masks are not" +" copied since they are just derived information." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:135 +msgid "Alpha Bands" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:137 +msgid "" +"When a dataset has a normal GDT_Byte alpha (transparency) band that " +"applies, it should be returned as the null mask, but the GetMaskFlags() " +"method should include GMF_ALPHA. For processing purposes any value other " +"than 0 should be treated as valid data, though some algorithms will treat" +" values between 1 and 254 as partially transparent." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:146 +msgid "These drivers will be updated:" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:148 +msgid "" +"JPEG Driver: support the \"zlib compressed mask appended to the file\" " +"approach used by a few data providers." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:150 +msgid "GRASS Driver: updated to support handling null values as masks." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:152 +msgid "Possibly updated:" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:154 +msgid "" +"HDF4 Driver: This driver might possibly be updated to return real mask if" +" we can figure out a way." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:156 +msgid "" +"SDE Driver: This driver might be updated if Howard has sufficient time " +"and enthusiasm." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:160 +#: ../../source/development/rfc/rfc31_ogr_64.rst:176 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:507 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:353 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:529 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:61 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:79 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:732 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:151 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:251 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:322 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:112 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:243 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:64 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:234 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:147 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:606 +msgid "Utilities" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:162 +msgid "" +"The gdalwarp utility and the gdal warper algorithm will be updated to use" +" null masks on input. The warper algorithm already uses essentially this " +"model internally. For now gdalwarp output (nodata or alpha band) will " +"remain unchanged, though at some point in the future support may be added" +" for explicitly generating null masks, but for most purposes producing an" +" alpha band is producing a null mask." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:178 +msgid "" +"The GetMaskBand(), GetMaskFlags() and CreateMaskBand() methods (and " +"corresponding defines) will need to be added. The mask should work like a" +" normal raster band for swig purposes so minimal special work should be " +"required." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:186 +msgid "The gdalautotest will be extended with the following:" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:188 +msgid "" +"gcore/mask.py: test default mask implementation for nodata, alpha and all" +" valid cases." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:190 +msgid "" +"gdriver/jpeg.py: extend with a test for \"appended bitmask\" case - " +"creation and reading." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:193 +msgid "Interactive testing will be done for gdalwarp." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:5 +msgid "RFC 16: OGR Thread Safety" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:11 +#: ../../source/development/rfc/rfc27_supportdata.rst:11 +#: ../../source/development/rfc/rfc34_license_policy.rst:11 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:11 +#: ../../source/development/rfc/rfc5_unicode.rst:11 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:11 +msgid "Status: Development" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:16 +msgid "" +"In an effort to better support thread safety in OGR some methods are " +"added as internal infrastructure is updated." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:20 +#: ../../source/development/rfc/rfc34_license_policy.rst:22 +msgid "Definitions" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:22 +msgid "" +"*Reentrant*: A reentrant function can be called simultaneously by " +"multiple threads provided that each invocation of the function references" +" unique data." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:26 +msgid "" +"*Thread-safe*: A thread-safe function can be called simultaneously by " +"multiple threads when each invocation references shared data. All access " +"to the shared data is serialized." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:31 +#: ../../source/development/rfc/rfc17_python_namespaces.rst:28 +msgid "Objective" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:33 +msgid "" +"To make all of the OGR core and selected drivers reentrant, and to make " +"the driver registrar, drivers and datasources at least potentially " +"thread-safe." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:38 +msgid "TestCapability()" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:40 +msgid "" +"The TestCapability() method on the driver, and datasource will be " +"extended to include ways of testing for reentrancy and thread safety on " +"particular instances. The following macros will be added:" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:51 +msgid "Meaning:" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:53 +msgid "" +"OLCReentrant: The layer class is reentrant. Multiple threads can operate " +"on distinct instances of this class - including different layers on a " +"single datasource." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:56 +msgid "" +"ODsCReentrant: The datasource class is reentrant. Multiple threads can " +"operate on distinct instances of this class." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:58 +msgid "" +"ODsCThreadSafe: The datasource class is thread-safe. Multiple threads can" +" operate on a single instance of this class." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:60 +msgid "" +"ODsCLayerClones: The OGRDataSource::GetLayerClone() method is supported, " +"and returns a layer instance with distinct state from the default layer " +"returned by GetLayer()." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:64 +msgid "" +"Note that a single layer instance cannot be threadsafe as long as layer " +"feature reading status is implicit in the layer object. The default " +"return value for all test values is FALSE, as is normal for the " +"TestCapability() method, but specific drivers can return TRUE after " +"determining that the driver datasources or layers are in fact reentrant " +"and/or threadsafe." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:72 +msgid "OGRSFDriverRegistrar" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:74 +msgid "" +"Various changes have already been made to make the driver registrar " +"thread safe, primarily by protecting operations on it with a mutex." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:78 +msgid "OGRSFDriver" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:80 +msgid "" +"No changes are required to the OGRSFDriver base class for thread safety, " +"primarily because it does almost nothing." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:84 +msgid "OGRDataSource" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:86 +msgid "" +"This class has been modified to include an m_hMutex class data member " +"which is a mutex used to ensure thread safe access to internal " +"datastructures such as the layer list. Classes derived from OGRDataSource" +" that wish to implement threadsafe operation should use this mutex when " +"exclusivity is required." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:92 +msgid "A new method is added to this class:" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:98 +msgid "" +"The default implementation of this method returns NULL. If the " +"ODsCLayerClones capability is true for the datasource, this method must " +"return duplicates of the requested layer that have distinct feature " +"reading state. That is they can have their own spatial and attribute " +"filter settings, and the internal feature iterator (for GetNextFeature() " +"and ResetReading()) is distinct from other OGRLayer instances referencing" +" the same underlying datasource layer." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:106 +msgid "" +"The intention of this method in the multi-threaded context is that " +"different threads can have clones of a layer with distinct read state. A " +"sort of poor-mans threadsafety, even though in fact it is just " +"reentrancy." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:111 +msgid "" +"Layers return by GetLayerClone() should be released with the " +"OGRDataSource::ReleaseResultSet() method, much like layers returned by " +"ExecuteSQL()." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:116 +msgid "ExecuteSQL()" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:118 +msgid "" +"The default OGR implementation of OGRDataSource::ExecuteSQL() internally " +"uses and modifies the layer state (feature iterators and filters) and as " +"such is not appropriate to use on a datasource that is attempting to be " +"threadsafe even though it is understood that individual layers are not " +"threadsafe." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:124 +msgid "" +"The proposed solution is that this code will be modified to use " +"GetLayerClone() if the datasource supports GetLayerClone()." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:130 +msgid "" +"A multi-threaded C++ test harnass will be implemented for read-only " +"stress testing of datasources claiming to support reentrancy and " +"threadsafety." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:134 +msgid "" +"No testing of reentrancy and threadsafety will be incorporated into the " +"regression test suite (gdalautotest) as it does not appear to be " +"practical." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:141 +msgid "" +"Frank Warmerdam will implement all the core features of this RFC for the " +"GDAL/OGR 1.5.0 release. As well the Shapefile, Personal Geodatabase, ODBC" +" and Oracle drivers will implement OLCReentrant, ODsCLayerClones, " +"ODsCReentrant and ODsThreadSafe." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:5 +msgid "RFC 17: Python Namespaces" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:7 +msgid "Author: Howard Butler" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:9 +msgid "Contact: hobu.inc@gmail.com" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:17 +msgid "" +"GDAL bindings for Python have historically dodged the normal Python " +"practices of using packages and namespaces to provide organization." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:25 +msgid "" +"This RFC implements a new namespace for Python, called *osgeo*, where the" +" GDAL Python bindings henceforth will reside. Backward compatibility is " +"provided, so that current code will continue to run unchanged, but new " +"developments should utilize the namespace for code organization and " +"global namespace pollution reasons. As of 10/1/2007, the changes " +"described here in RFC 17 only pertain to the \"next-gen\" Python " +"bindings. It is expected that these bindings will be the default bindings" +" for GDAL 1.5." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:30 +msgid "" +"To provide the GDAL Python bindings in a Python package that is properly " +"namespaced, eliminating pollution of Python's global namespace." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:34 +msgid "Past Usage" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:36 +msgid "GDAL's Python bindings previously used globally-aware Python modules:" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:47 +msgid "New Usage" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:49 +msgid "RFC 17 now provides these modules under the *osgeo* namespace:" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:59 +msgid "" +"Additionally, the old module-style imports continue to work with a " +"deprecation warning:" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:68 +msgid "" +"It is planned that we will remove the GDAL-specific global modules at " +"some point in the future." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:72 +msgid "Other Sprint Updates" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:74 +msgid "" +"The work for this RFC was done at the FOSS4G2007 GDAL code sprint by " +"Howard Butler and Chris Barker. In addition to the Python namespacing, " +"some minor issues were dealt with respect to building the GDAL bindings." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:78 +msgid "" +"The next-gen Python bindings now use setuptools by default if it is " +"available." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:80 +msgid "" +"The ./swig/python directory was slightly reorganized to separate " +"extension building from pure python modules." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:82 +msgid "" +"gdal2tiles, a Google Summer of Code project by Petr Klokan, was " +"integrated into the next-gen bindings" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:86 +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:120 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:153 +#: ../../source/development/rfc/rfc26_blockcache.rst:230 +#: ../../source/development/rfc/rfc29_desired_fields.rst:132 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:463 +#: ../../source/development/rfc/rfc7_vsilapi.rst:114 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:134 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:231 +msgid "Voting History" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:88 +msgid "A voice vote (our first ever!) commenced at the FOSS4G2007 sprint." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:90 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:155 +#: ../../source/development/rfc/rfc29_desired_fields.rst:134 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:465 +msgid "Frank Warmerdam +1" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:91 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:159 +msgid "Howard Butler +1" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:92 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:157 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:467 +msgid "Daniel Morissette +1" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:93 +msgid "Tamas Szekerest +1" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:5 +msgid "RFC 18: OGR Style Support in C API" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:7 +msgid "Author: Daniel Morissette" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:9 +msgid "Contact: dmorissette@mapgears.com" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:11 +msgid "Status: Adopted (2007-12-05)" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:16 +msgid "" +"OGR has a number of C++ classes that deal with the encoding of style " +"information and attaching that to features. More information is available" +" in the :ref:`ogr_feature_style` document." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:20 +msgid "" +"With GDAL/OGR version 1.4.x and older, it was not possible to deal with " +"style information using the C API. This RFC proposes the addition of " +"functions to the C API to manipulate style information in GDAL/OGR 1.5." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:25 +msgid "Implementation Details" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:27 +msgid "The following enums will be moved from ogr_featurestyle.h to ogr_core.h:" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:39 +msgid "" +"The OGRStyleMgrH (corresponding to the OGRStyleMgr C++ class) will be " +"added to the C API:" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:53 +msgid "" +"The OGRStyleToolH (corresponding to the OGRStyleTool C++ class) will be " +"added to the C API:" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:77 +msgid "" +"Note: at implementation time, the OGR_ST_GetParamIsNull() has been " +"removed and replaced by an 'int \\*bValueIsNull' argument on all the " +"OGR_ST_GetParam...() functions in order to map more closely to the C++ " +"methods." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:82 +msgid "" +"NO wrappers will be needed for the following C++ classes which are " +"handled internally by the OGR\\_ST\\_\\* wrappers above:" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:92 +msgid "" +"Note that ogr_featurestyle.h also contains a OGRSTVectorParam enum and a " +"corresponding OGRStyleVector class but this class is currently unused and" +" may eventually be removed, so we will not implement support for it in " +"the C API (and the OGRSTVectorParam enum will NOT be moved to " +"ogr_core.h)." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:99 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:621 +msgid "Python and other language bindings" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:101 +msgid "" +"The initial implementation will be for the C API only and will not be " +"ported/tested with the Python and other scripting language bindings. This" +" will have to wait for a later release." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:108 +msgid "" +"Daniel Morissette will implement the changes to the C API described in " +"this RFC for the GDAL/OGR 1.5.0 release." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:111 +msgid "" +"The first test of the new C API functions will be the conversion of " +"MapServer's mapogr.cpp to use them." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:115 +msgid "Related Ticket(s)" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:117 +msgid "#2061" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:122 +#: ../../source/development/rfc/rfc19_safememalloc.rst:90 +msgid "+1 from all PSC members (FrankW, DanielM, HowardB, TamasS, AndreyK)" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:5 +msgid "RFC 19: Safer memory allocation in GDAL" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:7 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:7 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:7 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:7 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:7 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:7 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:7 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:7 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:7 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:7 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:7 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:7 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:7 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:7 +msgid "Author: Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:9 +msgid "Contact: even.rouault@spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:11 +#: ../../source/development/rfc/rfc26_blockcache.rst:11 +#: ../../source/development/rfc/rfc45_virtualmem.rst:11 +#: ../../source/development/rfc/rfc4_geolocate.rst:11 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:11 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:11 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:11 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:11 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:11 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:11 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:11 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:11 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:11 +msgid "Status: Adopted, implemented" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:16 +msgid "" +"This document contains proposal on how to make GDAL safer (prevent " +"crashes) when doing memory allocations. The starting point of this " +"discussion is ticket #2075." +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:21 +#: ../../source/development/rfc/rfc29_desired_fields.rst:31 +#: ../../source/development/rfc/rfc2_svn.rst:22 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:20 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:32 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:53 +#: ../../source/development/rfc/rfc84_cmake.rst:111 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:54 +#: ../../source/development/rfc/rfc87_signed_int8.rst:50 +#: ../../source/development/rfc/rfc93_update_feature.rst:55 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:42 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:82 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:56 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:37 +msgid "Details" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:23 +msgid "" +"In many places in GDAL source code, multiplications are done to compute " +"the size of the memory buffer to allocate, like raster blocks, scanlines," +" whole image buffers, etc.. Currently no overflow checking is done, thus " +"leading to potential allocation of not large enough buffers. Overflow can" +" occur when raster dimensions are very large (this can be the case with a" +" WMS raster source for example) or when a dataset is corrupted, " +"intentionnaly or unintentionnaly. This can lead to latter crash." +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:32 +msgid "" +"This RFC introduces new API to allocate memory when the computation of " +"the size to allocate is based on multiplications. These new API report " +"overflows when they occur. Overflows are detected by checking that " +"((a*b)/b) == a. This does not require to make assumptions on the size of " +"the variable types, their signedness, etc." +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:58 +msgid "" +"The behavior of VSIMalloc2 and VSIMalloc3 is consistent with the behavior" +" of VSIMalloc. Implementation of already existing memory allocation API " +"(CPLMalloc, CPLCalloc, CPLRealloc, VSIMalloc, VSICalloc, VSIRealloc) will" +" not be changed." +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:63 +msgid "" +":ref:`rfc-8` will be updated to promote new API for safer memory " +"allocation. For example using VSIMalloc2(x, y) instead of doing " +"CPLMalloc(x \\* y) or VSIMalloc(x \\* y)." +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:69 +msgid "Implementation steps" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:71 +msgid "Introduce the new API in gdal/port" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:73 +msgid "" +"Use the new API in GDAL core where it is relevant. The following files " +"have been identified as candidates : gcore/gdalnodatamaskband.cpp, " +"gcore/overview.cpp, gcore/gdaldriver.cpp, gcore/gdalrasterblock.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:78 +msgid "" +"Use the new API in GDAL drivers. This step can be done incrementally. " +"Transition from CPL to VSI allocation can be necessary in some cases too." +" Candidate drivers : Idrisi, PNG, GXF, BSB, VRT, MEM, JP2KAK, RPFTOC, " +"AIRSAIR, AIGRIB, XPM, USGDEM, BMP, GSG, HFA, AAIGRID. (See " +"gdal_svn_trunk_use_vsi_safe_mul_in_frmts.patch in ticket #2075)" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:84 +msgid "" +"Even Rouault will implement the changes described in this RFC for the " +"GDAL 1.6.0 release." +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:88 +#: ../../source/development/rfc/rfc31_ogr_64.rst:392 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:287 +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:96 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:652 +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:52 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:245 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:352 +#: ../../source/development/rfc/rfc45_virtualmem.rst:1266 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:691 +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:224 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:628 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:184 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:267 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:105 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:515 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:605 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:100 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:181 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:146 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:113 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:791 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:213 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:297 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:402 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:167 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:290 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:491 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:95 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:288 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:201 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:265 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:228 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:129 +#: ../../source/development/rfc/rfc71_github_migration.rst:117 +#: ../../source/development/rfc/rfc72_pytest.rst:242 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:542 +#: ../../source/development/rfc/rfc74_sphinx.rst:117 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:232 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:462 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:231 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:232 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:91 +#: ../../source/development/rfc/rfc84_cmake.rst:195 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:87 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:682 +#: ../../source/development/rfc/rfc87_signed_int8.rst:117 +#: ../../source/development/rfc/rfc88_googletest.rst:231 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:132 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:456 +#: ../../source/development/rfc/rfc91_dataset_close.rst:200 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:295 +#: ../../source/development/rfc/rfc93_update_feature.rst:275 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:167 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:181 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:558 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:318 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:163 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:738 +msgid "Voting history" +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:5 +msgid "RFC 1: Project Management Committee Guidelines" +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:16 +msgid "" +"This document describes how the GDAL/OGR Project Management Committee " +"determines membership, and makes decisions on GDAL/OGR project issues." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:19 +msgid "" +"In brief the committee votes on proposals on gdal-dev. Proposals are " +"available for review for at least two days, and a single veto is " +"sufficient to delay progress though ultimately a majority of members can " +"pass a proposal." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:25 +msgid "Detailed Process" +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:27 +msgid "" +"Proposals are written up and submitted on the gdal-dev mailing list for " +"discussion and voting, by any interested party, not just committee " +"members." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:30 +msgid "" +"Proposals need to be available for review for at least two business days " +"before a final decision can be made." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:32 +msgid "" +"Respondents may vote \"+1\" to indicate support for the proposal and a " +"willingness to support implementation." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:34 +msgid "" +"Respondents may vote \"-1\" to veto a proposal, but must provide clear " +"reasoning and alternate approaches to resolving the problem within the " +"two days." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:37 +msgid "" +"A vote of -0 indicates mild disagreement, but has no effect. A 0 " +"indicates no opinion. A +0 indicate mild support, but has no effect." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:39 +msgid "" +"Anyone may comment on proposals on the list, but only members of the " +"Project Management Committee's votes will be counted." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:41 +msgid "" +"A proposal will be accepted if it receives +2 (including the proposer) " +"and no vetos (-1)." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:43 +msgid "" +"If a proposal is vetoed, and it cannot be revised to satisfy all parties," +" then it can be resubmitted for an override vote in which a majority of " +"all eligible voters indicating +1 is sufficient to pass it. Note that " +"this is a majority of all committee members, not just those who actively " +"vote." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:48 +msgid "" +"Upon completion of discussion and voting the proposer should announce " +"whether they are proceeding (proposal accepted) or are withdrawing their " +"proposal (vetoed)." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:51 +msgid "The Chair gets a vote." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:52 +msgid "" +"The Chair is responsible for keeping track of who is a member of the " +"Project Management Committee." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:54 +msgid "" +"Addition and removal of members from the committee, as well as selection " +"of a Chair should be handled as a proposal to the committee. The " +"selection of a new Chair also requires approval of the OSGeo board." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:58 +msgid "The Chair adjudicates in cases of disputes about voting." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:61 +msgid "When is Vote Required?" +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:63 +msgid "Anything that could cause backward compatibility issues." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:64 +msgid "Adding substantial amounts of new code." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:65 +msgid "Changing inter-subsystem APIs, or objects." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:66 +msgid "Issues of procedure." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:67 +msgid "When releases should take place." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:68 +msgid "Anything that might be controversial." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:71 +msgid "Observations" +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:73 +msgid "The Chair is the ultimate adjudicator if things break down." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:74 +msgid "" +"The absolute majority rule can be used to override an obstructionist " +"veto, but it is intended that in normal circumstances vetoers need to be " +"convinced to withdraw their veto. We are trying to reach consensus." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:80 +msgid "Bootstrapping" +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:82 +msgid "" +"Frank Warmerdam is declared initial Chair of the Project Management " +"Committee." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:85 +msgid "" +"Daniel Morissette, Frank Warmerdam, Andrey Kiselev and Howard Butler are " +"declared to be the founding Project Management Committee. The current " +"membership list can be found on the :ref:`psc` page." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:5 +msgid "RFC 20: OGRSpatialReference Axis Support" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:16 +msgid "" +"The OGRSpatialReference and OGRCoordinateTransformation classes assume " +"that all coordinate systems use (easting, northing) coordinate order (or " +"in geographic terms (longitude, latitude)). In practice some coordinate " +"systems use alternate axis orientations (such as the Krovak projection), " +"and some standards (GML, WMS 1.3, WCS 1.1) require honouring the EPSG " +"declaration that all it's geographic coordinates have (latitude, " +"longitude) coordinate ordering." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:24 +msgid "" +"This RFC attempts to extend the OGRSpatialReference, and " +"OGRCoordinateTransformation classes to support alternate axis " +"orientations, and to update selected drivers (GML, WMS, WCS, GMLJP2) to " +"properly support axis ordering." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:30 +msgid "WKT Axis Representation" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:32 +msgid "" +"The OGC WKT SRS format (per OGC 01-???) already indicates a way of " +"defining coordinate system axes as shown in this example:" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:51 +msgid "" +"There is one AXIS definition per axis with order relating to position " +"within a tuple. The first argument is the user name for the axis and " +"exact values are not specified. The second argument is a direction and " +"may be one of NORTH, SOUTH, EAST or WEST." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:57 +msgid "Dilemma" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:59 +msgid "" +"The core challenge of this RFC is adding support for axes orders, " +"including honouring EPSG desired axis order for geographic coordinate " +"systems where appropriate without breaking existing files and code that " +"make extensive use of EPSG coordinate systems but override axis " +"orientations and assume they should be treated as long, lat regardless of" +" what EPSG says." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:66 +msgid "" +"In particular, we come up with appropriate policies and mechanisms to " +"decide when a file in a geographic coordinate system like EPSG:4326 is to" +" be treated as lat/long and when it should be long/lat. Because of the " +"extensive existing practice it behooves us to err on the side of past " +"practice, and require \"opting in\" to honouring EPSG axis ordering." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:73 +msgid "The Hack" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:75 +msgid "" +"The main mechanism by I propose to work around the dilemma is to " +"differentiate between geographic coordinate systems with the AXIS values " +"set and those without. In particular, a WKT coordinate system with the " +"EPSG authority code (ie. 4326) set, but no axis declarations will be " +"assumed to be long, lat even though that is contrary to the definition " +"from EPSG of 4326. Only in cases where we really *know* we want to honour" +" EPSG's axis order will we actually populate the axis declarations " +"indicating lat, long." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:84 +msgid "" +"The hope is that this will let us continue to (mis)use EPSG:4326 " +"definitions without necessary honouring the EPSG axis ordering except in " +"specific circumstances." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:89 +msgid "OGRSpatialReference" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:92 +msgid "New Enumeration" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:106 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:194 +msgid "New methods" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:113 +msgid "Fetch information about one axis (iAxis is zero based)." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:122 +msgid "Defines the X and Y axes for a given target key (PROJCS or GEOGCS)." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:128 +msgid "" +"Returns true based on the EPSG code if EPSG would like this coordinate " +"system to be treated as lat/long. This is useful in contexts like WMS 1.3" +" where EPSG:4326 needs to be interpreted as lat/long due to the standard." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:137 +msgid "" +"This works like importFromEPSG() but will assign the EPSG defined AXIS " +"definition." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:140 +msgid "" +"Note that OGRSpatialReference::StripNodes( \"AXIS\" ); can be used to " +"strip axis definitions where they are not desired." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:144 +msgid "importFromURN" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:146 +msgid "" +"Modify importFromURN() to set AXIS values properly for EPSG and OGC " +"geographic coordinate systems. So urn:...:EPSG: will be assumed to really" +" honour EPSG conventions." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:151 +msgid "SetWellKnownGeogCS()" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:153 +msgid "This method appears to be the only code" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:155 +msgid "" +"Modify SetWellKnownGeogCS() to *not* set AXIS values, and strip AXIS " +"values out of any other hardcoded WKT definitions." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:159 +msgid "importFromEPSG()" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:161 +msgid "" +"importFromEPSG() will continue to *not* set AXIS values for GEOGCS " +"coordinate systems." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:163 +msgid "" +"importFromEPSG() will now set axis values for projected coordinate " +"systems (at least in cases like Krovak where it is a non-default axis " +"orientation)." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:166 +msgid "" +"importFromEPSG() will be implemented by calling importFromEPSGA() and " +"stripping off axis definitions from the geographic portion of the " +"returned definition." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:171 +msgid "SetFromUserInput()" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:173 +msgid "" +"This method will have one new option which is a value prefixed by EPSGA: " +"will be passed to importFromEPSGA() (similarly to EPSG:n being passed to " +"importFromEPSG())." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:178 +msgid "OGRCoordinateTransformation" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:180 +msgid "" +"If AXIS values are set on source and/or destination coordinate system, " +"the OGRCoordinateTransformation code will take care of converting into " +"normal easting/northing before calling PROJ." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:184 +msgid "" +"The CPL config option \"GDAL_IGNORE_AXIS_ORIENTATION\" may also be set to" +" \"TRUE\" to disable OGRCoordinateTransformation's checking, and " +"application of axis orientation changes. Effectively this is a backdoor " +"to disable the core effects of the RFC." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:190 +#: ../../source/development/rfc/rfc34_license_policy.rst:171 +msgid "Drivers Affected" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:192 +msgid "" +"GMLJP2 (classes in gcore/gdalgmlcoverage.cpp and " +"gcore/gdaljp2metadata.cpp)." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:194 +msgid "WCS (based on interpretation of urns)." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:195 +msgid "" +"WMS (maybe? actually, I suspect we don't actually get the coordinate " +"system from the capabalities)" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:197 +msgid "OGR GML (maybe? only GML3 affected?)" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:198 +msgid "" +"BSB, SAR_CEOS, ENVISAT, HDF4, JDEM, L1B, LAN, SRTMHGT: Like " +"SetWellKnownGeogCS() these all include lat/long AXIS specifications in " +"their hardcoded WGS84 coordinate systems. These need to be removed so " +"they will default to being interpreted as long/lat." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:204 +msgid "Versions" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:206 +msgid "" +"Work will be in trunk for GDAL/OGR 1.6.0 with the following exceptions " +"which will be address in 1.5.x:" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:209 +msgid "" +"Existing use of AXIS specifier will for geographic coordinate systems " +"will be stripped from SetWellKnownGeogCS() and the various drivers with " +"hard coded WKT strings." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:212 +msgid "" +"Some sort of hack will need to be introduced into the GMLJP2 (and " +"possibly WCS) code to flip EPSG authority lat/long values (details to be " +"worked out)." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:219 +msgid "" +"Implementation would be done by Frank Warmerdam. Some aspects (such as " +"properly capturing axis ordering for projected coordinate systems) might " +"not be implemented immediately." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:226 +msgid "" +"The greatest concern is that any existing WKT coordinate systems with " +"LAT/LONG axis ordering (in VRT files, or .aux.xml files for instance) " +"will be interpreted differently by GDAL/OGR 1.6.0 than they were by " +"1.5.0. This could easily occur if files in formats like BSB, or HDF4 were" +" copied to a format using WKT coordinate systems (such as JPEG with a " +".aux.xml file). To partially mitigate this I am proposing that AXIS " +"definitions be removed from GDAL 1.5.1." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:235 +msgid "Supporting Information" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:237 +msgid "" +"OSGeo Wiki Summary: `http://wiki.osgeo.org/index.php/Axis_Order_Confusion" +" `__" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:5 +msgid "RFC 21: OGR SQL type cast and field name alias" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:7 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:7 +msgid "Author: Tamas Szekeres" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:9 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:9 +msgid "Contact: szekerest@gmail.com" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:16 +msgid "" +"This proposal provides support for changing the column name and the " +"column type in the OGR SQL select list." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:19 +msgid "" +"The main motivation of this change is to provide better control when " +"transferring the OGR_STYLE special field from each data source to the " +"other. For example we can use ogr2ogr for this purpose using the " +"following command line:" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:28 +msgid "" +"The shape driver will truncate the OGR_STYLE field to 80 characters by " +"default in length that may not be enough to hold the actual value. So as " +"to fix this issue we might want to specify the desired length in the " +"select list, like:" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:37 +msgid "" +"In some cases it would also be useful to change the name of the field in " +"the target data source:" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:45 +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:21 +#: ../../source/development/rfc/rfc26_blockcache.rst:45 +#: ../../source/development/rfc/rfc5_unicode.rst:20 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:29 +msgid "Main concepts" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:47 +msgid "" +"To support these new features we will extend the current OGR SQL syntax. " +"The proposed addition will keep the syntax conform to the SQL92 " +"specification:" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:95 +msgid "" +"This RFC doesn't address implementing conversion to the 'integer list', " +"'double list' and 'string list' OGR data types, which doesn't conform to " +"the SQL92 specification and the necessary conversion routines are missing" +" in the OGR code." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:103 +msgid "" +"To implement the addition the following changes should be made in the OGR" +" codebase:" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:106 +msgid "" +"In ogr_swq.h I'll have to add to 4 fields to swq_col_def to hold the " +"field_alias the target_type, the field_length, and field_precision" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:109 +msgid "" +"In ogr_swq.h SWQ_DATE, SWQ_TIME, SWQ_TIMESTAMP will be added to " +"swq_field_type enum." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:112 +msgid "" +"In swq.c I'll have to change swq_select_preparse to take care of the " +"field alias and the CAST specification." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:115 +msgid "" +"A new function (swq_parse_typename) will be added to parse the supported " +"typenames." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:118 +msgid "" +"In ogr_gensql.cpp the .ctor of OGRGenSQLResultsLayer will be changed to " +"set up the field name and the field length to the target data source" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:122 +msgid "" +"In ogr_gensql.cpp TranslateFeature will be modified to take care of the " +"type change if specified." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:128 +msgid "" +"The backward compatibility for the current SQL syntax will be retained. " +"This addition doesn't require changes in the OGR C and SWIG API." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:132 +#: ../../source/development/rfc/rfc22_rpc.rst:260 +#: ../../source/development/rfc/rfc26_blockcache.rst:193 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:182 +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:200 +#: ../../source/development/rfc/rfc31_ogr_64.rst:194 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:108 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:119 +#: ../../source/development/rfc/rfc34_license_policy.rst:227 +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:96 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:615 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:656 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:598 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:154 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:237 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:383 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:535 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:66 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:153 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:121 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:84 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:737 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:156 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:264 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:339 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:118 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:263 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:457 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:69 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:250 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:154 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:435 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:505 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:210 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:433 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:203 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:207 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:74 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:404 +#: ../../source/development/rfc/rfc87_signed_int8.rst:91 +#: ../../source/development/rfc/rfc93_update_feature.rst:252 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:163 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:479 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:298 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:134 +msgid "Documentation" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:134 +msgid "" +"The OGR SQL document will be updated to reflect the new features. I'll " +"take care of updating the OGR Style Documentation with the support of " +"transferring the styles between the data sources." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:139 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:441 +msgid "Implementation Staffing" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:141 +msgid "Tamas Szekeres will implement the RFC in the development version." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:143 +msgid "" +"Frank Warmerdam will implement the regression test scripts according to " +"this new functionality." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:147 +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:175 +#: ../../source/development/rfc/rfc26_blockcache.rst:217 +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:41 +#: ../../source/development/rfc/rfc5_unicode.rst:191 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:156 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:209 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:452 +msgid "References" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:149 +msgid "" +"Tracking bug for this feature (containing all of the proposed code " +"changes): #2171" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:161 +msgid "Even Rouault +1" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:163 +#: ../../source/development/rfc/rfc29_desired_fields.rst:135 +msgid "Tamas Szekeres +1" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:165 +msgid "Andrey Kiselev +0" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:5 +msgid "RFC 22: RPC Georeferencing" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:11 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:11 +msgid "Status: Adopted, Implemented" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:16 +msgid "" +"It is proposed that GDAL support an additional mechanism for geolocation " +"of imagery based on rational polynomial coefficients (RPCs) represented " +"as metadata." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:20 +msgid "" +"Many modern raw satellite products are distributed with RPCs, including " +"products from GeoEye, and DigitalGlobe. RPCs provide a higher systematic " +"description of georeferencing over an image, and also contain information" +" on the viewing geometry that in theory makes orthocorrection (given a " +"DEM) and some 3D operations like building height computation possible." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:28 +msgid "RPC Domain Metadata" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:30 +msgid "" +"Datasets with RPCs will include the following dataset level metadata " +"items in the \"RPC\" domain to identify the rational polynomials." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:33 +msgid "" +"ERR_BIAS: Error - Bias. The RMS bias error in meters per horizontal axis " +"of all points in the image (-1.0 if unknown)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:35 +msgid "" +"ERR_RAND: Error - Random. RMS random error in meters per horizontal axis " +"of each point in the image (-1.0 if unknown)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:37 +msgid "LINE_OFF: Line Offset" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:38 +msgid "SAMP_OFF: Sample Offset" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:39 +msgid "LAT_OFF: Geodetic Latitude Offset" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:40 +msgid "LONG_OFF: Geodetic Longitude Offset" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:41 +msgid "HEIGHT_OFF: Geodetic Height Offset" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:42 +msgid "LINE_SCALE: Line Scale" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:43 +msgid "SAMP_SCALE: Sample Scale" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:44 +msgid "LAT_SCALE: Geodetic Latitude Scale" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:45 +msgid "LONG_SCALE: Geodetic Longitude Scale" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:46 +msgid "HEIGHT_SCALE: Geodetic Height Scale" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:47 +msgid "" +"LINE_NUM_COEFF (1-20): Line Numerator Coefficients. Twenty coefficients " +"for the polynomial in the Numerator of the rn equation. (space separated)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:50 +msgid "" +"LINE_DEN_COEFF (1-20): Line Denominator Coefficients. Twenty coefficients" +" for the polynomial in the Denominator of the rn equation. (space " +"separated)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:53 +msgid "" +"SAMP_NUM_COEFF (1-20): Sample Numerator Coefficients. Twenty coefficients" +" for the polynomial in the Numerator of the cn equation. (space " +"separated)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:56 +msgid "" +"SAMP_DEN_COEFF (1-20): Sample Denominator Coefficients. Twenty " +"coefficients for the polynomial in the Denominator of the cn equation. " +"(space separated)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:60 +msgid "" +"These fields are directly derived from the document prospective GeoTIFF " +"RPC document at:" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:63 +msgid "" +"`http://geotiff.maptools.org/rpc_prop.html " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:65 +msgid "" +"The line and pixel offset expressed with LINE_OFF and SAMP_OFF are with " +"respect to the center of the pixel (#5993)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:69 +msgid "Updating NITF Driver" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:71 +msgid "" +"Already supports RPCs in this model, but will be modified to put them in " +"the RPC domain instead of the primary metadata domain." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:73 +msgid "Add support for reading Digital Globe .RPB files." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:74 +msgid "No support for writing RPCs for now." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:77 +msgid "Updating GeoTIFF Driver" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:79 +msgid "Upgrade to support reading Digital Globe .RPB files." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:80 +msgid "Possible support reading Space Imaging (GeoEye?) rpc.txt files." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:81 +msgid "" +"Support reading RPC TIFF tag (per " +"`http://geotiff.maptools.org/rpc_prop.html " +"`__)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:83 +msgid "Support writing RPC TIFF tag." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:84 +msgid "Support writing .RPB files (if RPB=YES or PROFILE not GDALGeoTIFF)." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:87 +msgid "Changes to GenImgProj Transformer" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:89 +msgid "" +"Currently it is difficult to reliably create a warp transformer based on " +"RPCs using GDALGenImgProjTransformer() as it will use a geotransform in " +"preference to RPCs if available. Many images with useful RPC information " +"also include a geotransform (approximate or accurate). It is therefore " +"proposed to modify the GDALCreateGenImgProjTransformer() function to make" +" it practical to provide more direction in the creation of the " +"transformer. The proposed new function is:" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:103 +msgid "Supported Options:" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:105 +msgid "SRC_SRS: WKT SRS to be used as an override for hSrcDS." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:106 +msgid "DST_SRS: WKT SRS to be used as an override for hDstDS." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:107 +msgid "GCPS_OK: If false, GCPs will not be used, default is TRUE." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:108 +msgid "" +"MAX_GCP_ORDER: the maximum order to use for GCP derived polynomials if " +"possible. The default is to autoselect based on the number of GCPs. A " +"value of -1 triggers use of Thin Plate Spline instead of polynomials." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:112 +msgid "" +"METHOD: may have a value which is one of GEOTRANSFORM, GCP_POLYNOMIAL, " +"GCP_TPS, GEOLOC_ARRAY, RPC to force only one geolocation method to be " +"considered on the source dataset." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:115 +msgid "RPC_HEIGHT: A fixed height to be used with RPC calculations." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:117 +msgid "" +"This replaces the older function which did not include support for " +"passing arbitrary options, and was thus not easily extended. The old " +"function will be re-implemented with a call to the new functions." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:121 +msgid "" +"The most important addition is the METHOD option which can be set to " +"specifically use one of the image to georeferenced coordinate system " +"methods instead of leaving it up to the code to pick the one it thinks is" +" best." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:127 +msgid "Changes to gdalwarp and gdaltransform" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:129 +msgid "" +"In order to facilitate passing transformer options into the updated " +"GDALCreateGenImgProjTransformer2(), the gdalwarp and gdaltransform " +"programs (built on this function) will be updated to include a -to " +"(transformer option) switch, and to use the new function." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:135 +#: ../../source/development/rfc/rfc4_geolocate.rst:146 +msgid "Preserving Geolocation Through Translation" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:137 +msgid "" +"The RPC information needs to be copied and preserved through translations" +" that do not alter the spatial arrangement of the data. To that end RPC " +"metadata copying will be added to:" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:141 +msgid "VRT driver's CreateCopy()." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:142 +msgid "GDALDriver's default CreateCopy()." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:143 +msgid "GDALPamDataset::CopyInfo()" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:144 +msgid "" +"gdal_translate will be updated to copy RPC metadata to the intermediate " +"internal VRT if, and only if, no resizing or subsetting is being done." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:149 +msgid "Changes to RPC Transformer" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:151 +msgid "" +"Implement iterative \"back transform\" from pixel/line to lat/long/height" +" instead of simple linear approximator." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:153 +msgid "" +"Add support for RPC_HEIGHT offset, so all Z values to transformer are " +"assumed to be relative to this offset (normally really and average " +"elevation for the scene)." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:156 +msgid "Make RPC Transformer serializable (in VRT files, etc)." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:159 +#: ../../source/development/rfc/rfc25_fast_open.rst:92 +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:60 +msgid "Backward Compatibility Issues" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:161 +msgid "" +"Previously the NITF driver returned RPC metadata in the default domain. " +"With the implementation of this RFC for GDAL 1.6.0 any applications using" +" this metadata would need to consult the RPC domain instead. The RPC\\_ " +"prefix on the metadata values has also been removed." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:166 +msgid "" +"The GDALCreateGenImgProjTransformer() function is preserved, so no " +"compatibility issues are anticipated by the addition of the new " +"generalized factory." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:171 +msgid "SWIG Bindings Issues" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:173 +msgid "" +"The raw access is by the established metadata api, so no changes are " +"needed for this." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:175 +msgid "" +"The Warp API is only bound at a high level, so there should be no changes" +" in this regard." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:177 +msgid "" +"For testing purposes it is desirable to provide a binding around the GDAL" +" transformer API. The following planned binding is based loosely on " +"OGRCoordinateTransformation API binding. So far I have only found the " +"TransformPoint( bDstToSrc, x, y, z ) entry point to be useful in Python " +"and even that ends up returning a (bSuccess, (x, y, z)) result which is " +"somewhat awkward. Is there a better way of doing this?" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:262 +msgid "" +"In addition to standard API documentation, the RPC metadata mechanism " +"will be introduced into the \"GDAL Data Model\" document." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:268 +msgid "" +"This work will be implemented by Frank Warmerdam with support from the " +"Canadian Nuclear Safety Commission." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:274 +msgid "" +"A test script for the transformer API covering RPC, GCP_TPS, " +"GCP_POLYNOMIAL, GEOLOC and GEOTRANSFORM methods will be implemented." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:276 +msgid "" +"A test script for reading and writing RPB, and GeoTIFF RPC tags will be " +"written." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:5 +msgid "RFC 23.1: Unicode support in OGR" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:7 +#: ../../source/development/rfc/rfc25_fast_open.rst:7 +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:7 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:7 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:7 +#: ../../source/development/rfc/rfc34_license_policy.rst:7 +msgid "Authors: Frank Warmerdam" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:11 +msgid "Status: Adopted (implemented)" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:16 +msgid "" +"This document proposes preliminary steps towards GDAL/OGR handling " +"strings internally in UTF-8, and supporting conversion between different " +"encodings." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:23 +#: ../../source/development/rfc/rfc5_unicode.rst:22 +msgid "GDAL should be modified in a way to support three following main ideas:" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:25 +msgid "" +"C Functions will be provided to support a variety of encoding " +"conversions, including conversion between representations (ie. UTF-8 to " +"UCS-16/wchar_t)." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:28 +msgid "Character encodings will be identified by iconv() style strings." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:29 +msgid "" +"OFTString/OFTStringList feature attributes in OGR will be treated as " +"being in UTF-8." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:32 +msgid "" +"This RFC specifically does not attempt to address issues of using non-" +"ascii filenames. It also does not attempt to make definitions about the " +"encoding of other strings used in GDAL/OGR (such as field names, " +"metadata, etc). These would presumably be addressed in a later RFC " +"building on this one." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:39 +msgid "CPLRecode API" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:41 +msgid "" +"The following three C callable functions will be introduced for recoding " +"strings, and for converting between wchar_t (wide character) and char " +"(multi-byte) formats:" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:57 +msgid "" +"In each case the returned string is zero terminated, as is the input " +"string, and the returned string should be deallocated with CPLFree(). In " +"case of error the returned string will be NULL, and the function will " +"issue a CPLError(). The functions will be marked with CPL_DLL and " +"considered part of the public GDAL/OGR API for use of applications as " +"well as internal use." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:65 +msgid "Encoding Names" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:67 +msgid "" +"It is proposed that the encoding names will be the same sorts of names " +"used by iconv(). So stuff like \"UTF-8\", \"LATIN5\", \"CP850\" and " +"\"ISO_8859-1\". It does not appear that these names for encodings are a " +"1:1 match with C library locale names (like \"en_CA.utf8\" for instance) " +"which may cause some issues." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:73 +msgid "Some particular names of interest:" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:75 +msgid "" +"\"\": The current locale. Use this when converting from/to the users " +"locale." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:77 +msgid "" +"\"UTF-8\": Unicode in multi-byte encoding. Most of the time this will be " +"our internal linga-franca." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:79 +msgid "" +"\"POSIX\": I think this is roughly ASCII (perhaps with some extended " +"characters?)." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:81 +msgid "" +"\"UCS-2\": Two byte unicode. This is a wide character format and only " +"suitable for use with the wchar_t methods." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:84 +msgid "" +"On some systems you can use \"iconv --list\" to get a list of supported " +"encodings." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:88 +msgid "iconv()" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:90 +msgid "" +"It is proposed to implement the CPLRecode() method using the iconv() and " +"related functions when available." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:93 +msgid "" +"There is an excellent implementation of this API as GNU libiconv(), which" +" is used by the C libraries on Linux. Also some operating systems provide" +" the iconv() API as part of the C library (all unix?); however, the " +"system iconv() often has a restricted set of conversions supported so it " +"may be desirable to use libiconv in preference to the system iconv() even" +" when it is available." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:100 +msgid "" +"If iconv() is not available, a stub implementation of the recode services" +" will be provided which:" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:103 +msgid "" +"implements UCS-2 / UTF-8 interconversion using either mbtowc/wctomb, or " +"an implementation derived from " +"`http://www.cl.cam.ac.uk/~mgk25/unicode.html " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:106 +msgid "" +"Implements recoding from \"\" to and from \"UTF-8\" by doing nothing, but" +" issuing a warning on the first use if the current locale does not appear" +" to be the \"C\" locale." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:109 +msgid "Implements recoding from \"ASCII\" to \"UTF-8\" as a null operation." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:110 +msgid "" +"Implements recoding from \"UTF-8\" to \"ASCII\" by turning all non-ASCII " +"multi-byte characters to '?'." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:113 +msgid "" +"This hopefully gives us a weak operational status when built without " +"iconv(), but full operation when it is available." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:116 +msgid "" +"The --with-iconv= option will be added to configure. The argument can be " +"the path to a libiconv installation or the special value 'system' " +"indicating that the system lib should be used. Alternatively, --without-" +"iconv can be used to avoid using iconv." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:122 +msgid "OFTString/OFTStringList Fields" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:124 +msgid "" +"It is declared that OGR string attribute values will be in UTF-8. This " +"means that OGR drivers are responsible for translating format specific " +"representations to UTF-8 when reading, and back to the format specific " +"representation when writing. In many cases (of simple ASCII text) this " +"requires no transformation." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:130 +msgid "" +"This implies that the arguments to methods like OGRFeature::SetField( int" +" i, const char \\*) should be UTF-8, and that GetFieldAsString() will " +"return UTF-8." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:134 +msgid "" +"The same issues apply to OFTStringList lists of strings. Each string will" +" be assumed to be UTF-8." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:138 +msgid "OLCStringsAsUTF8 Capability Flag" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:140 +msgid "" +"Some drivers (ie. CSV) can effectively not know the encoding of their " +"inputs. Therefore, it isn't always practical to turn things into UTF-8 in" +" a guaranteed way. So, the new layer level capability called " +"\"StringsAsUTF8\" represented with the macro \"OLCStringsAsUTF8\" will be" +" testable at the layer level with TestCapability(). Drivers which are " +"certain to return string attributes as UTF-8 should return TRUE, while " +"drivers that do not know the encoding they return should return FALSE. " +"Any driver which knows it's encoding should convert to UTF-8." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:150 +msgid "OGR Driver Updates" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:152 +msgid "" +"The following OGR drivers could benefit immediately from recoding to " +"UTF-8 support in one way or another." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:155 +msgid "ODBC (add support for wchar_t / NVARSHAR fields)" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:156 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:58 +msgid "Shapefile" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:157 +msgid "" +"GML (I'm not sure how the XML encoding values all map to our concept of " +"encoding)" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:159 +msgid "Postgres" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:161 +msgid "" +"I'm sure a number of the other drivers, particularly the RDBMS drivers, " +"could benefit from an update." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:167 +msgid "" +"Frank Warmerdam will implement the core iconv() capabilities, the " +"CPLRecode() additions and update the ODBC driver. Other OGR drivers would" +" be updated as time and demand mandates to conform to the definitions in " +"this RFC by interested developers." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:172 +msgid "The core work will be completed for GDAL/OGR 1.6.0 release." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:177 +#: ../../source/development/rfc/rfc5_unicode.rst:193 +msgid "" +"`The Unicode Standard, Version 4.0 - Implementation Guidelines " +"`__ - Chapter 5 (PDF)" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:180 +#: ../../source/development/rfc/rfc5_unicode.rst:196 +msgid "" +"FAQ on how to use Unicode in software: " +"`http://www.cl.cam.ac.uk/~mgk25/unicode.html " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:182 +#: ../../source/development/rfc/rfc5_unicode.rst:198 +msgid "" +"FLTK implementation of string conversion functions: " +"`http://svn.easysw.com/public/fltk/fltk/trunk/src/utf.c " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:184 +#: ../../source/development/rfc/rfc5_unicode.rst:200 +msgid "" +"`http://www.easysw.com/~mike/fltk/doc-2.0/html/utf_8h.html " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:185 +#: ../../source/development/rfc/rfc5_unicode.rst:201 +msgid "Ticket #1494 : UTF-8 encoding for GML output." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:186 +msgid "" +"Libiconv: `http://www.gnu.org/software/libiconv/ " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:188 +msgid "" +"ICU (another i18n library): `http://www.icu-project.org/ `__" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:5 +msgid "RFC 24: GDAL Progressive Data Support" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:7 +msgid "Author: Norman Barker, Frank Warmerdam" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:9 +msgid "Contact: nbarker@ittvis.com, warmerdam@pobox.com" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:16 +msgid "" +"Provide an interface for asynchronous/streaming data access in GDAL. The " +"initial implementation is for JPIP, but should be generic enough to apply" +" to other streaming / progressive approaches. Background on the JPIP " +"(Kakadu) implementation can be found in [wiki:rfc24_jpipkak]." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:22 +msgid "Interfaces" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:25 +msgid "GDALAsyncReader" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:27 +msgid "" +"This new class is intended to represent an active asynchronous raster " +"imagery request. The request includes information on a source window on " +"the dataset, a target buffer size (implies level of decimation or " +"replication), the buffer type, buffer interleaving, data buffer and bands" +" being requested. Essentially the same sort of information that is passed" +" in a GDALDataset::!RasterIO() request." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:34 +msgid "" +"The GetNextUpdatedRegion() method can be used to wait for an update to " +"the imagery buffer, and to find out what area was updated. The " +"LockBuffer() and UnlockBuffer() methods can be used to temporarily " +"disable updates to the buffer while application code accesses the buffer." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:40 +msgid "" +"While an implementation of the simple accessors is provided as part of " +"the class, it is intended that the class be subclassed as part of " +"implementation of a particular driver, and custom implementations of " +"GetNextUpdatedRegion(), LockBuffer() and UnlockBuffer() provided." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:45 +msgid "" +"{{{ class CPL_DLL GDALAsyncReader { protected: GDALDataset\\* poDS; int " +"nXOff; int nYOff; int nXSize; int nYSize; void \\* pBuf; int nBufXSize; " +"int nBufYSize; GDALDataType eBufType; int nBandCount; int\\* panBandMap; " +"int nPixelSpace; int nLineSpace; int nBandSpace; long nDataRead;" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:50 +msgid "" +"public: GDALAsyncReader(GDALDataset\\* poDS = NULL); virtual " +"~GDALAsyncReader();" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:81 +msgid "}; }}}" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:84 +msgid "GetNextUpdatedRegion()" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:105 +msgid "" +"The async return status list is as follows, and will be declared in " +"gdal.h." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:119 +msgid "The meaning as a return value is:" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:121 +msgid "" +"GARIO_PENDING: No imagery was altered in the buffer, but there is still " +"activity pending, and the application should continue to call " +"GetNextUpdatedRegion() as time permits." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:124 +msgid "" +"GARIO_UPDATE: Some of the imagery has been updated, but there is still " +"activity pending." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:126 +msgid "" +"GARIO_ERROR: Something has gone wrong. The asynchronous request should be" +" ended." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:128 +msgid "" +"GARIO_COMPLETE: An update has occurred and there is no more pending work " +"on this request. The request should be ended and the buffer used." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:133 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:122 +msgid "GDALDataset" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:135 +msgid "" +"The GDALDataset class is extended with methods to create an asynchronous " +"reader, and to cleanup the asynchronous reader. It is intended that these" +" methods would be subclassed by drivers implementing asynchronous data " +"access." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:151 +msgid "" +"It is expected that as part of gdal/gcore a default !GDALAsyncReader " +"implementation will be provided that just uses GDALDataset::!RasterIO() " +"to perform the request as a single blocking request. However, this " +"default implementation will ensure that applications can use the " +"asynchronous interface without worrying whether a particular format will " +"actually operate asynchronously." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:159 +msgid "GDALDriver" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:161 +msgid "" +"In order to provide a hint to applications whether particular formats " +"support asynchronous IO, we will add a new metadata item on the " +"GDALDriver of implementing formats. The metadata item will be " +"\"DCAP_ASYNCIO\" (macro GDAL_DCAP_ASYNCIO) and will have the value " +"\"YES\" if asynchronous IO is available." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:167 +msgid "" +"Implementing drivers will do something like this in their driver setup " +"code:" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:175 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:147 +msgid "GDALRasterBand" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:177 +msgid "" +"There are no changes to the GDALRasterBand interface for asynchronous " +"raster IO. Asynchronous IO requests can only be made at the dataset " +"level, not the band." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:182 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:364 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:183 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:219 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:144 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:87 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:152 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:382 +#: ../../source/development/rfc/rfc91_dataset_close.rst:135 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:146 +msgid "C API" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:184 +msgid "" +"The following C API wrappers for the C++ classes and methods will be " +"added. Note that at this time there is no intention to provide C wrappers" +" for all the GDALAsyncReader accessors since the provided information is " +"already available in the application from the call launching the async " +"io." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:215 +msgid "" +"It is intended that all the above functions in the C API will be wrapped " +"for SWIG." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:219 +msgid "Driver Implementations" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:221 +msgid "" +"A full implementation of the Asynchronous API will be provided as the " +"JPIPKAK driver - a JPIP protocol implementation using the Kakadu library." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:225 +msgid "At this time, no other implementations are planned." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:230 +msgid "" +"Some testing of the asynchronous api against normal drivers will be added" +" in the test suite, as well as testing of the JPIPKAK driver in " +"asynchronous and conventional data access methods." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:234 +msgid "" +"Also, a new commandline program, gdalasyncread, is implemented which " +"provides a mechanism to test the async API from the commandline. It takes" +" a subset of the gdal_translate commandline options." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:5 +msgid "RFC 25: Fast Open (withdrawn)" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:11 +msgid "" +"Status: Withdrawn (in favor of some specific improvements in #2957 - rfc " +"may be renewed at a later date)" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:17 +msgid "" +"This document proposes a mechanism for application to indicate a desire " +"for the fastest possible open of a raster file, even if a variety of " +"metadata and supporting information may not be available. It is primarily" +" intended to optimize applications working with catalogs containing many " +"raster files." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:26 +msgid "" +"An application can request fast open mode by setting the " +"\"GDAL_FAST_OPEN\" configuration option to \"YES\" - the default is " +"assumed to be no. When this option is set to YES selected drivers can " +"operate differently so as to optimize the speed of opening a dataset. " +"Acceleration options include:" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:32 +msgid "" +"Skip establishing a coordinate system - particularly helpful if it avoids" +" an EPSG lookup." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:34 +msgid "Skip probing for supporting .aux.xml, world files and other files." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:36 +msgid "" +"It is anticipated that fast open mode will be used primarily for fast " +"raster display from datasets where required metadata is already provided " +"by a catalog of some sort. Because of this it is essential that in fast " +"open mode datasets will still accurately return a list of bands, their " +"datatypes, and their overviews." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:43 +msgid "Thread Local Configuration Options" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:45 +msgid "" +"In multi-threaded applications use of a process-global configuration " +"option - turned on just while calling GDALOpen() - may not be " +"appropriate. In particular, it is hard to ensure that this configuration " +"option won't affect GDALOpen()'s in other threads of the same process. " +"This problem also affects other configuration options that. To resolve " +"this problem it is intended to add a new function to set \"thread local\"" +" configuration options." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:57 +msgid "" +"This mechanism will be implemented using normal thread local data " +"handling (CPLGetTLS(), etc)." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:60 +msgid "" +"It should be noted that CPLSetConfigOption() will continue to set " +"configuration options to apply to all threads. CPLGetConfigOption() will " +"first search thread local values, then process global values and then the" +" environment." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:66 +msgid "Work Plan" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:68 +msgid "" +"For the time being the following changes will be made to drivers to " +"accelerate them in fast open mode." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:71 +msgid "GDALOpenInfo will avoid loading a list of all files in a directory." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:72 +msgid "GTIFF driver will avoid collecting a coordinate systems." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:74 +msgid "" +"This work will be completed in trunk in time for the GDAL 1.7.0 release " +"by Frank Warmerdam." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:78 +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:53 +msgid "Utilization" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:80 +msgid "" +"There is no plan to do this immediately, but the GDAL VRT driver would be" +" a good candidate to utilize this mechanism." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:83 +msgid "" +"In theory, it would also be desirable for MapServer to utilize this mode " +"for tileindexed rasters - except that MapServer depends on the " +"geotransform coming from the underlying raster file rather than coming " +"from the raster catalog. MapServer also assumes the color table, and " +"nodata values will be available." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:89 +msgid "ArcGIS is also expected to utilize this feature." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:94 +msgid "" +"There are no known backward compatibility issues. However, there may be " +"forward compatibility issues if we are not precise and consistent from " +"version to version on what supporting info is allowed to be omitted in " +"fast open mode." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:102 +msgid "" +"Tests would be added to the appropriate driver test scripts to test fast " +"open mode - confirming that expected information is discarded, and kept." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:107 +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:71 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:119 +msgid "Issues" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:109 +msgid "" +"Potentially desirable things like ignoring .aux.xml files are not " +"possible as they are also sometimes the source of overview information." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:112 +msgid "" +"Potentially discarding all metadata including color tables, nodata " +"values, and geotransforms makes this mode not useful for applications " +"like MapServer that don't keep such information in their catalog." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:115 +msgid "" +"This RFC does not discuss a way of accelerating GDALOpen() by skipping " +"unnecessary drivers, though that would also potentially help quite a bit." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:5 +msgid "RFC 26: GDAL Block Cache Improvements" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:7 +msgid "Authors: Tamas Szekeres, Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:9 +msgid "Contact: szekerest@gmail.com, even.rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:13 +msgid "Implementation version: GDAL 2.1" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:16 +msgid "Summary and rationale" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:18 +msgid "" +"GDAL maintains an in-memory cache for the raster blocks fetched from the " +"drivers and ensures that the second attempt to access the same block will" +" be served from the cache instead of the driver. This cache is maintained" +" in a per-band fashion and an array is allocated for the pointers for " +"each blocks (or sub-blocks). This approach is not sufficient with large " +"raster dimensions (or large virtual rasters ie. with the WMS/TMS driver)," +" which may cause out of memory errors in GDALRasterBand::InitBlockInfo, " +"as raised in #3224" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:27 +msgid "" +"For example, a band of a dataset at level 21 with a GoogleMaps tiling " +"requires 2097152x2097152 tiles of 256x256 pixels. This means that GDAL " +"will try to allocate an array of 32768x32768 = 1 billion elements (32768 " +"= 2097152 / 64). The size of this array is 4 GB on a 32-bit build, so it " +"cannot be allocated at all. And it is 8 GB on a 64-bit build (even if " +"this is generally only virtual memory reservation but not actually " +"allocation of physical pages of memory, due to over-commit mechanism of " +"the operating system). At dataset closing, this means that those 1 " +"billion cells will have to be explored to discover remaining cached " +"blocks. In reality, all above figures must be multiplied by 3 for a RGB " +"(or 4 for a RGBA) dataset." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:39 +msgid "" +"In the hash set implementation, memory allocation depends directly on the" +" number of cached blocks. Typically with the default GDAL_CACHEMAX size " +"of 40 MB, only 640 blocks of 256x256 pixels can be simultaneously cached " +"(for all datasets)." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:47 +msgid "" +"Awareness of thread-safety issues is crucial in the design of block " +"caching. In gdalrasterblock.cpp, a static linked list is maintained so as" +" to track the access order of the blocks and keep the size of the cache " +"within a desired limit by dropping the oldest blocks out of the list. " +"This linked list is shared among all the datasets and bands in GDAL " +"(protected by a hRBMutex) and a thread on each band, when reading a new " +"block, may also trigger a GDALRasterBand::UnreferenceBlock call on " +"another band within the scope of this mutex. GDALRasterBand::FlushBlock " +"will also access the data structure of the band level cache by removing " +"the corresponding tile from the array or the hashtable." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:58 +msgid "" +"In GDAL 2.0, some issues related to thread-safety (#3225, #3226) have " +"been fixed and this RFC still preserves those scenarios as safe." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:61 +msgid "" +"The changes of this RFC consist in moving away from the GDALRasterBand " +"class the logic to access to a cached block, to add or remove it. This is" +" done with the new GDALAbstractBandBlockCache class. The current array " +"based logic is moved into the new GDALArrayBandBlockCache class, and the " +"new hashset based logic in GDALHashsetBandBlockCache." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:67 +msgid "" +"For the array based implementation, due to the \"static\" nature of the " +"hosting structure (an array), no special care is needed when reading or " +"writing a cell from concurrent threads. The only special care that must " +"be taken is to prevent a given cell (block) to be accessed concurrently. " +"For example we want to avoid TryGetLockedBlockRef() to return a block " +"that is being freed by another thread from " +"GDALRasterBlock::FlushCacheBlock() or Internalize(). For that, the " +"nRefCount member of GDALRasterBlock is now accessed and modified only " +"through atomic functions to increase, decrease or compare-and-swap its " +"value." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:78 +msgid "" +"For the hash set based implementation, the base implementation of hash " +"set data structure done in in cpl_hash_set.h / cpl_hash_set.cpp is not " +"thread safe by default. So GDALHashsetBandBlockCache has a dedicated " +"mutex to protect all reads, additions and removals from the hash set. No " +"dead-lock with the hRBMutex can occurs since no operations done under the" +" hashset mutex involves calling any method from GDALRasterBlock." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:85 +msgid "" +"We could potentially have reused the hRBMutex to protect the hash set, " +"but this would have increased the contention of the hRBMutex " +"unnecessarily." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:89 +msgid "" +"By default, the selection between the array based and the hashtable based" +" approaches is based on the following rule: if the dataset has more than " +"1 million blocks, the hashset based implementation is used, otherwise the" +" array based implementation is used. The new GDAL_OF_ARRAY_BLOCK_ACCESS " +"and GDAL_OF_HASHSET_BLOCK_ACCESS open flags can also be passed to " +"GDALOpenEx() to override this choice. The :config:`GDAL_BAND_BLOCK_CACHE`" +" configuration option can also be set to ARRAY or HASHSET." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:98 +msgid "" +"The hashset based implementation could potentially be the default " +"implementation in all cases (performance comparisons done with the " +"autotest/cpp/testblockcache utility with 4 or 8 cores show non measurable" +" differences), but in theory the array based implementation offers less " +"contention of the hRBMutex, so should be more scalable when using lots of" +" cores. And as work has been done during GDAL 2.0 to improve the " +"scalability, it might be prudent for now to remain on the array based " +"implementation on rasters of modest size." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:107 +msgid "" +"Not completely linked with this RFC, a few changes have been done to " +"limit the number of allocation/deallocation of objects (GDALRasterBlock " +"instances, as well as an internal element of CPLHashSet), which has an " +"effect on scalability since memory allocation routines involve " +"synchronization between threads." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:116 +msgid "" +"To implement the addition the following changes is made in the GDAL " +"codebase:" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:119 +msgid "" +"port/cpl_hash_set.cpp / port/cpl_hash_set.h: CPLHashSetClear() function " +"added to remove all the elements in one operation." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:122 +msgid "" +"port/cpl_hash_set.cpp / port/cpl_hash_set.h: " +"CPLHashSetRemoveDeferRehash() function added to remove one element " +"quickly. That is to say the potential resizing of the array used " +"internally is deferred to a later operation" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:127 +msgid "" +"port/cpl_hash_set.cpp / port/cpl_hash_set.h: improvements to \"recycle\" " +"links from the linked lists and avoid useless malloc()/free()." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:131 +msgid "port/cpl_atomic_ops.cpp: addition of CPLAtomicCompareAndExchange()" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:133 +msgid "" +"gcore/gdal.h: additions of GDAL_OF_DEFAULT_BLOCK_ACCESS, " +"GDAL_OF_ARRAY_BLOCK_ACCESS and GDAL_OF_HASHSET_BLOCK_ACCESS values." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:136 +msgid "" +"gcore/gdal_priv.h: definition of GDALAbstractBandBlockCache class, and " +"GDALArrayBandBlockCacheCreate() and GDALHashSetBandBlockCacheCreate() " +"functions. Modifications of GDALRasterBand, GDALDataset and " +"GDALRasterBlock definitions." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:141 +msgid "" +"gcore/gdalrasterband.cpp: InitBlockInfo() instantiates the appropriate " +"band block cache implementation." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:144 +msgid "" +"gcore/gdalrasterband.cpp: the AdoptBlock(), UnreferenceBlock(), " +"FlushBlock() and TryGetLockedBlockRef() methods delegate to the actual " +"band block cache implementation." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:148 +msgid "" +"gcore/gdalrasterband.cpp: AddBlockToFreeList() is added and delegate to " +"GDALAbstractBandBlockCache" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:151 +msgid "gcore/gdalrasterblock.cpp: SafeLockBlock() is replaced by TakeLock()" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:153 +msgid "" +"gcore/gdalrasterblock.cpp: RecycleFor() method added to recycle an " +"existing block object to save a few new/delete calls (used by " +"GDALAbstractBandBlockCache::CreateBlock())" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:157 +msgid "" +"gcore/gdalrasterblock.cpp: Internalize() or FlushCacheBlock() no longer " +"directly free a block (they still free or recycle its pData member), but " +"provide it to GDALRasterBand::AddBlockToFreeList() for layer reuse." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:162 +msgid "" +"gcore/gdalrasterblock.cpp: DropLockForRemovalFromStorage() is added to " +"avoid racing destruction of blocks between GDALRasterBand::FlushCache() " +"or FlushBlock() with GDALRasterBlock::Internalize() or FlushCacheBlock()." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:167 +msgid "" +"gcore/gdalabstractbandblockcache.cpp: added. Contains logic to keep " +"instantiated GDALRasterBlock that were discarded by the global block " +"manager for their later reuse. Saves a few new/delete calls." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:171 +msgid "" +"gcore/gdalarraybandblockcache.cpp: the GDALArrayBandBlockCache class " +"implementation with mostly the existing code" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:174 +msgid "" +"gcore/gdalhashsetbandblockcache.cpp: the new GDALHashsetBandBlockCache " +"class implementation" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:180 +msgid "" +"This implementation retains the backward compatibility with the existing " +"API. The C++ ABI of GDALRasterBand, GDALDataset and GDALRasterBlock is " +"modified." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:185 +msgid "Performance impacts" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:187 +msgid "" +"The array based implementation after this RFC should still show the same " +"performance than the current implementation (potentially very slightly " +"improved with the recycling of blocks). Confirmed by tests with " +"autotest/cpp/testblockcache." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:195 +msgid "This change doesn't affect the existing user documentation." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:200 +msgid "" +"The autotest/cpp/testblockcache utility is now run by the \"quick_test\" " +"target of autotest/cpp/Makefile with " +":config:`GDAL_BAND_BLOCK_CACHE=HASHSET` in additions to the array based " +"implementation." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:204 +msgid "" +"A new autotest/cpp/testblockcachelimits utility has been developed to " +"test a few racing situations. As races are hard to trigger, the code of " +"GDALRasterBlock has been instrumented to allow sleeping in particular " +"places, enabling races to be reliably simulated." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:212 +msgid "" +"Tamas Szekeres had provided an initial version of this RFC. It has been " +"restructured and ported on GDAL 2.0 by Even Rouault (sponsored by `LINZ " +"(Land Information New Zealand) `__)" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:219 +msgid "" +"The proposed implementation lies in the \"rfc26_bandblockcache\" branch " +"of the `https://github.com/rouault/gdal2/tree/rfc26_bandblockcache " +"`__ " +"repository." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:224 +msgid "" +"The list of changes: " +"`https://github.com/rouault/gdal2/compare/rfc26_bandblockcache " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:227 +msgid "Related bugs: #3264, #3224." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:232 +msgid "+1 from EvenR, DanielM, TamasS. +0 from JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:5 +msgid "RFC 27: Improved Supporting Data File Options" +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:16 +msgid "" +"Currently GDAL depends on a variety of supporting data files from the " +"`gdal data `__ directory. The " +"largest part of these are coordinate system dictionaries from EPSG and " +"other sources. It also includes S-57 dictionaries, seed DGN and DXF " +"files, and project logos. Uncompressed it currently comes to roughly " +"1.8MB and it is expected to grow as additional dictionaries are added " +"(for PCI and IAU coordinate systems for instance)." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:24 +msgid "" +"It has also been a frequent problem at run time to find the data files " +"when they are installed in unusual locations." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:27 +msgid "" +"This RFC aims to overhaul support file handling with two new major " +"features." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:30 +msgid "" +"The ability to read from compressed data files to reduce the disk " +"footprint of GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:32 +msgid "" +"The ability to embed the data files with the GDAL DLL or shared library " +"to remove the \"finding\" problem." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:36 +msgid "CPL CSV Access via VSI*L" +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:38 +msgid "" +"The large majority of the support data file access is via the CPL CSV API" +" (gdal/port/cpl_csv.cpp). Finding support data files is done via " +"CPLFindFile(). It turns out these functions are still using the old VSI " +"API which does not support special handlers (like /vsizip/), or in at " +"least one case direct fopen() calls. So the first stage of this RFC is to" +" convert these functions to all use the VSI*L API. A `patch " +"`__" +" has been prepared that demonstrates the bulk of the required changes. " +"With this patch it is possible to access files from a GDAL_DATA setting " +"like /vsizip//home/warmerda/gdal/data/gdaldata.zip." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:49 +msgid "" +"Note that we are explicitly changing the contract about the nature of the" +" FILE\\* passed to functions like CSVReadParseLine() (real FILE\\* vs. " +"VSI\\ *L style FILE*). It is possible, though relatively unlikely that " +"application code, or private driver implementations will be using the SV " +"functions and will need to be changed. This change should be noted in the" +" GDAL 1.8 release notes." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:56 +msgid "" +"It is also unclear if there will be bad interactions with the cpl_csv " +"implementation embedded in libgeotiff in some situations, such as when " +"using libgeotiff as an external library. Some review will be needed." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:60 +msgid "" +"Another point to investigate is what the performance impact of doing all " +"the file finding through the VSI*L API will be." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:5 +msgid "RFC 28: OGR SQL Generalized Expressions" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:16 +msgid "" +"The OGR SQL evaluation engine currently does not allow general purpose " +"functions to be applied to columns in SELECT statements. Some special " +"purpose functions are supported (ie. CAST, COUNT, AVG, MAX, MIN, and " +"SUM), but not as part of more general expressions and generally in very " +"constrained arrangements. It is the intent of this work item to extend " +"the OGR SQL engine to support fairly general purpose expression " +"evaluation in the output field list of OGR SQL SELECT statements and to " +"implement a few preliminary processing functions in a fashion compatible " +"with standard SQL. As well, expressions used in WHERE clauses will be " +"generalized to support evaluation of non-logical operations, such as math" +" and functions. For example, after implementation it is intended the " +"following could be evaluated." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:35 +msgid "" +"A prototype implementation is now available for review in " +"`http://svn.osgeo.org/gdal/sandbox/warmerdam/gdal-rfc28 " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:39 +msgid "Technical Approach" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:41 +msgid "" +"Currently logical expressions take a very constrained format with the " +"base elements having to be of the form * *. As part of " +"the generalization non-logical expressions will be supported and the left" +" and right side of operators will be equally treated. The current OGR SQL" +" parser is ad hoc and cannot be practically extended to this generalized " +"form of expression. So at this point we will move to a yacc/bison based " +"parser grammar for expressions." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:49 +msgid "" +"Since it is not really practical to continue to use the existing ad hoc " +"SELECT parsing when parts of the SELECT statement are expressions, the " +"yacc/bison based parser will also be used to parse the whole SELECT " +"statement." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:54 +msgid "" +"The current expression node will be generalized to have 0-n children (for" +" arguments to functions), and to treat field references and constant " +"values as distinct leaf nodes rather than embedding this information in a" +" node defining an operation." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:59 +msgid "" +"It should be noted that as a side effect WHERE clauses will also support " +"more general expressions - not just logical comparisons. For instance:" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:62 +msgid "SELECT \\* WHERE (subtotal+salestax) > 100.0" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:65 +msgid "New Functions" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:67 +msgid "Math: +, -, \\*, /, \\*\\*" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:68 +msgid "String: CONCAT, SUBSTR" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:71 +msgid "SELECT Rules" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:120 +msgid "Special Notes" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:122 +msgid "" +"The existing CAST, and column summary functions COUNT, AVG, MIN, MAX and " +"SUM will be treated more-or-less as functions but constrained to be root " +"operations on column definitions and treated as a special case (still)." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:127 +msgid "Compatibility Implications" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:129 +msgid "" +"Some identifiers that were previously allowed as unquoted field names " +"will likely now have to be quoted as they will be keywords in the " +"grammar. The keyword set is:" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:133 +msgid "IN" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:134 +msgid "LIKE" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:135 +msgid "NULL" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:136 +msgid "IS" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:137 +msgid "SELECT" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:138 +msgid "LEFT" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:139 +msgid "JOIN" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:140 +msgid "WHERE" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:141 +msgid "ON" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:142 +msgid "ORDER" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:143 +msgid "BY" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:144 +msgid "FROM" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:145 +msgid "AS" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:146 +msgid "ASC" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:147 +msgid "DESC" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:148 +msgid "DISTINCT" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:149 +msgid "CAST" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:151 +msgid "" +"The previous implementation was written in C and avoided all use of " +"GDAL/OGR services so that it could be easily used in other contexts, " +"including as the where clause evaluator of the OGDI library. After this " +"update the code is C++, and direct use of CPL error and other services " +"has been directly incorporated. This means the implementation used by " +"GDAL and OGDI will diverge." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:158 +msgid "" +"For the most part the change results in some OGR SQL statements to work " +"that would previously have generated an error." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:162 +msgid "Performance Implications" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:164 +msgid "" +"I am hopeful that the evaluation speed will not be significantly " +"different for simple selections, but each output field will need to be " +"evaluated as an expression (with presumably one value-from-field node)." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:171 +msgid "" +"Frank Warmerdam will implement, test and document for the GDAL/OGR 1.8 " +"release." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:177 +msgid "" +"All existing OGR SQL test suite tests should pass. A new " +"autotest/ogr/ogr_sql_rfc28.py script will be introduced to test new " +"functionality." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:184 +msgid "" +"The :ref:`OGR SQL ` document will be extended to " +"describe the new capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:5 +msgid "RFC 29: OGR Set Ignored Fields" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:7 +msgid "Author: Martin Dobias" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:9 +msgid "Contact: wonder.sk@gmail.com" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:16 +msgid "" +"To improve performance when fetching features, this RFC proposes a way " +"how to tell OGR which fields are not going to be required in subsequent " +"GetFeature() / GetNextFeature() calls. Such fields will be ignored by the" +" driver and their value will be kept null. The RFC counts also with the " +"possibility to ignore feature geometry and style." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:22 +msgid "Common use cases:" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:24 +msgid "" +"the client renders the layer: all (or most) fields can be ignored, only " +"the geometry is required" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:27 +msgid "" +"the client shows attribute table: all fields are required, the geometry " +"can be ignored" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:33 +msgid "" +"A new function will be added to OGRLayer class to allow the client to set" +" which fields will *not* be fetched:" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:40 +msgid "and an equivalent call for C API:" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:46 +msgid "" +"The argument is a list of fields to be ignored, by name, and the special " +"field names \"OGR_GEOMETRY\" and \"OGR_STYLE\" will be interpreted to " +"refer to the geometry and style values of a feature." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:50 +msgid "" +"Passing by field name has been chosen so that we could handle " +"OGR_GEOMETRY, OGR_STYLE and possibly some other special fields in the " +"future. Instead of specifying \"desired\" fields, it has been decided to " +"specify \"ignored\" fields so that we wouldn't accidentally drop things " +"like geometry and style just because they weren't explicitly listed in a " +"desired list." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:57 +msgid "Passing NULL for papszFields will clear the ignored list." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:59 +msgid "" +"The method will return OGRERR_NONE as long as all the field names are " +"able to be resolved, even if the method does not support selection of " +"fields." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:63 +msgid "" +"The drivers supporting this method will return TRUE to OLCIgnoreFields " +"(\"IgnoreFields\") capability." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:66 +msgid "" +"The method will be implemented at the level of OGRLayer class: it will " +"resolve indexes of the fields and set the following new member variables " +"which indicate what should be ignored. The flags will be stored within " +"OGRFeatureDefn and OGRFieldDefn classes and available with these getter " +"functions:" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:78 +msgid "" +"The getter member functions will be complemented by setter functions for " +"use by OGRLayer. Setting the \"ignored\" flags directly by clients will " +"be forbidden." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:82 +msgid "" +"Optionally the method ``SetIgnoredFields()`` can be overridden in driver " +"implementation if the driver has some special needs." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:86 +msgid "Implementation in drivers" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:88 +msgid "" +"The implementation of drivers will require small adjustments in order to " +"support this RFC. Drivers not making use of this addition will simply " +"continue to fetch also fields/geometry/style that are not requested by " +"the caller." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:93 +msgid "The adjustments in driver implementation will look as follows:" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:117 +msgid "" +"This change is fully backwards compatible: OGR will continue to fetch " +"geometry, style and all fields by default. Only applications using the " +"proposed API will experience the new behavior." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:121 +msgid "" +"Initially, only some drivers (Shapefile and few others) will implement " +"this RFC. There is no need to modify all existing drivers when adopting " +"the RFC - drivers that do not consider the ignored fields will simply " +"fetch all attributes as before. To check whether a driver supports this " +"RFC, OLCIgnoreFields capability can be checked." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:127 +msgid "" +"ogr2ogr command line tool will make use of this RFC in cases it receives " +"-select argument with a list of required fields. Other than the specified" +" fields will be ignored." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:136 +msgid "Daniel Morissette +0" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:137 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:469 +msgid "Howard Butler +0" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:138 +msgid "Even Rouault +0" +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:5 +msgid "RFC 2: Migration to OSGeo Subversion Repository" +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:16 +msgid "" +"It is proposed that the GDAL source tree be moved a subversion repository" +" in such a manner as to preserve the history existing in the CVS " +"repository. A 1.3.x branch will be created after automatic updating of " +"the header format." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:24 +msgid "The conversion will be done by Howard Butler using the cvs2svn tool." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:25 +msgid "" +"At least 24 hours notice will be provided before the transition starts to" +" allow committers to commit any outstanding work that is ready to into " +"the repository." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:28 +msgid "" +"When the conversion starts, the GDAL (and gdalautotest) trees will be " +"removed from cvs.maptools.org, and archived to avoid any confusion." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:30 +msgid "" +"Frank Warmerdam will modify the \"daily cvs snapshot\" capability to work" +" from SVN." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:32 +msgid "" +"Frank will be responsible for updating the source control information in " +"the documentation." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:34 +msgid "" +"All source files in SVN will have the svn:keywords property set to \"Id\"" +" by Frank after they are created." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:36 +msgid "" +"Committers will need to get a login on osgeo.org and notify Frank to " +"regain commit access. Committer access on the new repository will be " +"enabled after the above changes are all complete." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:39 +msgid "" +"The GDAL committers document should be updated, removing non-GDAL " +"committers (ie. libtiff, geotiff, etc)." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:43 +msgid "Header Format" +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:45 +msgid "" +"SVN does not support history insertion in source files, and to keep the " +"old history listings around without keeping them up to date would be very" +" confusing. So it is proposed that Frank Warmerdam write a script to " +"strip the history logs out. Changing this:" +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:75 +msgid "to this:" +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:98 +msgid "Branch for 1.3" +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:100 +msgid "" +"Once the headers have been updated appropriately, a 1.3 branch will be " +"established in subversion. The intent is that further 1.3.x releases " +"would be made against this \"stable branch\" while trunk work is towards " +"a 1.4.0 release targeted for around the time of the OSGeo conference." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:5 +msgid "RFC 30: Unicode Filenames" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:16 +msgid "" +"This document describes steps to generally handle filenames as UTF-8 " +"strings in GDAL/OGR. In brief it will be assumed that filenames passed " +"into and returned by GDAL/OGR interfaces are UTF-8. On some operating " +"systems, notably Windows, this will require use of \"wide character\" " +"interfaces in the low level VSI*L API." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:23 +msgid "Key Interfaces" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:26 +msgid "VSI*L API" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:28 +msgid "" +"All filenames in the VSI*L API will be treated as UTF-8, which means the " +"cpl_vsil_win32.cpp implementation will need substantial updates to use " +"wide character interfaces." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:32 +msgid "VSIFOpenL()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:33 +msgid "VSIFStatL()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:34 +msgid "VSIReadDir()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:35 +msgid "VSIMkdir()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:36 +msgid "VSIRmdir()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:37 +msgid "VSIUnlink()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:38 +msgid "VSIRename()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:41 +msgid "Old (small file) VSI API" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:43 +msgid "" +"The old VSIFOpen() function will be adapted to use \\_wfopen() on windows" +" instead of fopen() so that utf-8 filenames will be supported." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:46 +msgid "VSIFOpen()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:47 +msgid "VSIStat()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:50 +msgid "Filename Parsing" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:52 +msgid "" +"Because the path/extension delimiter characters '.', '', '/' and ':' will" +" never appear in the non-ascii portion of utf-8 strings we can safely " +"leave the existing path parsing functions working as they do now. They do" +" not need to be aware of the real character boundaries for exotic " +"characters in utf-8 paths. The following will be left unchanged." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:58 +msgid "CPLGetPath()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:59 +msgid "CPLGetDirname()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:60 +msgid "CPLGetFilename()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:61 +msgid "CPLGetBasename()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:62 +msgid "CPLGetExtension()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:63 +msgid "CPLResetExtension()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:66 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:506 +msgid "Other" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:68 +msgid "CPLStat()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:69 +msgid "CPLGetCurrentDir()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:70 +msgid "GDALDataset::GetFileList()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:72 +msgid "These will all also need to treat filenames as utf-8." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:75 +msgid "Windows" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:77 +msgid "" +"Currently Windows's cpl_vsil_win32.cpp module uses CreateFile() with " +"ascii filenames. It needs to be converted to use CreateFileW() and other " +"wide character functions for stat(), rename, mkdir, etc. Prototype " +"implementation already developed (r20620)." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:85 +msgid "Linux / Unix / MacOS X" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:87 +msgid "" +"On modern linux, unix and MacOS operating systems the fopen(), stat(), " +"readdir() functions already support UTF-8 strings. It is not currently " +"anticipated that any work will be needed on Linux/Unix/MacOS X though " +"there is some question about this. It is considered permissible under the" +" definition of this RFC for old, and substandard operating systems " +"(WinCE?) to support only ASCII, not UTF-8 filenames." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:95 +msgid "Metadata" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:97 +msgid "" +"There are a variety of places where general text may contain filenames. " +"One obvious case is the subdataset filenames returned from the SUBDATASET" +" domain. Previously these were just exposed as plain text and " +"interpretation of the character set was undefined. As part of this RFC we" +" state that such filenames should be considered to be in utf-8 format." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:104 +msgid "Python Changes" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:106 +msgid "" +"I observe with Python 2.6 that functions like gdal.Open() do not accept " +"unicode strings, but they do accept utf-8 string objects. One possible " +"solution is to update the bindings in selective places to identify " +"unicode strings passed in, and transform them to utf-8 strings." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:111 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:87 +msgid "eg." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:119 +msgid "" +"I'm not sure what the easiest way is to accomplish this in the bindings. " +"The key entries are:" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:122 +msgid "gdal.Open()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:123 +msgid "ogr.Open()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:124 +msgid "gdal.ReadDir()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:125 +msgid "gdal.PushFinderLocation()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:126 +msgid "gdal.FindFile()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:127 +msgid "gdal.Unlink()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:129 +msgid "" +"Similarly all interfaces (ie. gdal.ReadDir()) that return filenames will " +"hereafter return unicode objects rather than string objects." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:132 +msgid "Also note that in Python 3.x strings are always unicode." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:135 +msgid "C# Changes" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:137 +msgid "" +"Tamas notes that in C# we normally convert the unicode C# strings into C " +"string with the PtrToStringAnsi marshaller. Presumably we will need to " +"use a utf-8 converter for all interface strings considered to be " +"filenames. I would note this should also apploy to OGR string attribute " +"values which are also intended to be treated as utf-8." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:143 +msgid "" +"(It is unclear who will take care of this aspect since the primary author" +" (FrankW) is not C#-binding-competent." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:147 +msgid "Perl Changes" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:149 +msgid "" +"The general rule in Perl is that all strings should be decoded before " +"giving them to Perl and encoded when they are output. In practice things " +"usually just work. To be sure, I (Ari) have added an explicit decode from" +" utf8 to FindFile and ReadDir (#20800)." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:155 +msgid "Java Changes" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:157 +msgid "" +"No changes are needed for Java. Java strings are unicode, and they are " +"already converted to utf-8 in the java swig bindings. That is, the java " +"bindings already assumed passing and receiving utf-8 strings to/from " +"GDAL/OGR." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:163 +msgid "Commandline Issues" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:165 +msgid "" +"On windows argv[] as passed into main() will not generally be able to " +"represent exotic filenames that can't be represented in the locale " +"charset. It is possible to fetch the commandline and parse it as wide " +"characters using GetCommandLineW() and CommandLinetoArgvW() to capture " +"ucs-16 filenames (easily converted to utf-8); however, this interferes " +"with the use of setargv.obj to expand wildcards on windows." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:172 +msgid "" +"I have not been able to come up with a good solution, so for now I am not" +" intending to make any changes to the GDAL/OGR commandline utilities to " +"allow passing exotic filenames. So this RFC is mainly aimed at ensuring " +"that other applications using GDAL/OGR can utilize exotic filenames." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:179 +#: ../../source/development/rfc/rfc31_ogr_64.rst:201 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:388 +msgid "File Formats" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:181 +msgid "" +"The proposed implementation really only addresses file format drivers " +"that use VSIFOpenL(), VSIFOpen() and related functions. Some drivers " +"dependent on external libraries (ie. netcdf) do not have a way to hook " +"the file IO API and may not support utf-8 filenames. It might be nice to " +"be able to distinguish these." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:187 +msgid "" +"At the very least any driver marked with GDAL_DCAP_VIRTUALIO as \"YES\" " +"will support UTF-8. Perhaps this opportunity ought to be used to more " +"uniformly apply this driver metadata (done)." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:192 +#: ../../source/development/rfc/rfc31_ogr_64.rst:295 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:102 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:109 +#: ../../source/development/rfc/rfc34_license_policy.rst:222 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:269 +#: ../../source/development/rfc/rfc45_virtualmem.rst:1250 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:435 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:541 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:73 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:89 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:742 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:161 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:269 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:344 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:123 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:268 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:74 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:255 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:159 +msgid "Test Suite" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:194 +msgid "" +"We will need to introduce some test suite tests with multibyte utf-8 " +"filenames. In support of that aspects of the VSI*L API - particularly the" +" rename, mkdir, rmdir, functions and VSIFOpenL itself have been exposed " +"in python." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:202 +msgid "" +"Appropriate API entry points will be documented as taking and return " +"UTF-8 strings." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:208 +msgid "Implementation is underway and being tracked in ticket #3766." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:5 +msgid "RFC 31: OGR 64bit Integer Fields and FIDs" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:7 +msgid "Authors: Frank Warmerdam, Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:9 +msgid "Contact: warmerdam@pobox.com, even dot rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:11 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:11 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:11 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:11 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:11 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:11 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:11 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:11 +msgid "Status: Adopted, implemented in GDAL 2.0" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:16 +msgid "" +"This RFC addresses steps to upgrade OGR to support 64bit integer fields " +"and feature ids. Many feature data formats support wide integers, and the" +" inability to transform these through OGR causes increasing numbers of " +"problems." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:24 +msgid "64bit FID, feature index and feature count" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:26 +msgid "" +"Feature id's will be handled as type \"GIntBig\" instead of \"long\" " +"internally. This will include the nFID field of the OGRFeature. The " +"existing GetFID() and SetFID() methods on the OGRFeature use type long " +"and are changed to return (respectively accept) GIntBig instead. The " +"change of return type for GetFID() will require application code to " +"carefully adapt to avoid potential issues (for example if GetFID() is " +"used in printf-like expression). SetFID() change should be mostly " +"transparent. So the changes in the OGRFeature class are:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:40 +msgid "At the C API level:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:47 +msgid "" +"Note that the old interfaces using \"long\" are already 64bit on 64bit " +"operating systems (excluding Windows target compilers where long is 32bit" +" even on 64bit builds), so there is little harm to applications " +"continuing to use these interfaces on 64bit operating systems." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:52 +msgid "" +"A layer that can discover in a relatively cheap way that it holds " +"features with 64bit FID should advertise the OLMD_FID64 metadata item to " +"\"YES\", so ogr2ogr can pass the FID64 creation option to drivers that " +"support it." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:57 +msgid "" +"The OGRLayer class allows several operations based on the FID. The " +"signature of these will be *altered* to accept GIntBig instead of long. " +"In theory this should not require any changes to application code since " +"long can be converted to GIntBig losslessly. However, all existing OGR " +"drivers require changes, including private drivers. This will also result" +" in a backwards incompatible change in the C ABI. While we are at it, we " +"want GetFeatureCount() to be able to return more than 2 billion record " +"(currently returning 32 bit integer), and thus it will return GIntBig. " +"Similarly to GetFID(), this change of return type will require caution in" +" application code." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:68 +msgid "So at the OGRLayer C++ class level:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:77 +msgid "At the C API level :" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:89 +msgid "64bit Fields" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:91 +msgid "New field types will be introduced for 64bit integers:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:98 +msgid "The OGRField union will be extended to include:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:108 +msgid "The OGRFeature class will be extended with these new methods:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:124 +msgid "At the C level, the following functions are added :" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:133 +msgid "" +"Furthermore, the new interfaces will internally support setting/getting " +"integer fields, and the integer field methods will support " +"getting/setting 64bit integer fields so that one case can be used for " +"both field types where convenient (except GetFieldAsInteger64List() that " +"can only operate on Integer64List fields)" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:139 +msgid "" +"A GDAL_DMD_CREATIONFIELDDATATYPES = \"DMD_CREATIONFIELDDATATYPES\" driver" +" metadata item is added so as drivers to be able to declare the field " +"types they support on creation. For example \"Integer Integer64 Real " +"String Date DateTime Time IntegerList Integer64List RealList StringList " +"Binary\". Commonly used drivers will be updated to declare it." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:146 +#: ../../source/development/rfc/rfc31_ogr_64.rst:302 +msgid "OGR SQL" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:148 +msgid "" +"A SWQ_INTEGER64 internal type is added so as to be able to map/from " +"OFTInteger64 fields. The int_value member of the swq_expr_node class is " +"extended from int to GIntBig (so both SWQ_INTEGER and SWQ_INTEGER64 refer" +" to that member)." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:156 +msgid "Python / Java / C# / perl Changes" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:158 +msgid "The following changes have been done :" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:160 +msgid "GetFID(), GetFeatureCount() have been changed to return a 64 bit integer" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:162 +msgid "" +"SetFID(), GetFeature(), DeleteFeature(), SetNextByIndex() have been " +"changed to accept a 64 bit integer as argument" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:164 +msgid "GetFieldAsInteger64() and SetFieldInteger64() have been added" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:165 +msgid "In Python, GetField(), SetField() can accept/return 64 bit values" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:166 +msgid "" +"GetFieldAsInteger64List() and SetFieldInteger64List() have been added " +"(Python only, due to lack of relevant typemaps for other languages, but " +"could potentially be done)" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:170 +msgid "" +"The change in return type of GetFID() and GetFeatureCount() might cause " +"warnings at compilation time in some languages (Java YES, Python not " +"relevant, Perl/C# ?). All changes to existing methods will are an ABI " +"change for Java bytecode." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:178 +msgid "ogr2ogr and ogrinfo are updated to support the new 64bit interfaces." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:180 +msgid "" +"A new option is added to ogr2ogr : -mapFieldType. Can be used like this " +"-mapFieldType Integer64=Integer,Date=String to mean that Integer64 field " +"in the source layer should be created as Integer, and Date as String. " +"ogr2ogr will also warn if attempting to create a field in an output " +"driver that advertises a GDAL_DMD_CREATIONFIELDDATATYPES metadata item " +"that does not mention the required field type. For Integer64 fields, if " +"it is not advertized in GDAL_DMD_CREATIONFIELDDATATYPES metadata item or " +"GDAL_DMD_CREATIONFIELDDATATYPES is missing, conversion to Real is done by" +" default with a warning. ogr2ogr will also query the source layer to " +"check if the OLMD_FID64 metadata item is declared and if the output " +"driver has the FID64 layer creation option. In which case it will set it." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:196 +msgid "" +"New/modified API are documented. Updates in drivers with new " +"options/behaviours are documented. MIGRATION_GUIDE.TXT extended with a " +"section related to this RFC. OGR API updated." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:203 +msgid "" +"As appropriate, existing OGR drivers have been updated to support the " +"new/updated interfaces. In particular an effort has been made to update a" +" few database drivers to support 64bit integer columns for use as feature" +" id, though they don't always create FID columns as 64bit by default when" +" creating new layers as this may cause problems for other applications." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:210 +msgid "" +"Apart from the mechanical changes due to interface changes, the detailed " +"list of changes is :" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:213 +msgid "" +"Shapefile: OFTInteger fields are created by default with a width of 9 " +"characters, so to be unambiguously read as OFTInteger (and if specifying " +"integer that require 10 or 11 characters. the field is dynamically " +"extended like managed since a few versions). OFTInteger64 fields are " +"created by default with a width of 18 digits, so to be unambiguously read" +" as OFTInteger64, and extended to 19 or 20 if needed. Integer fields of " +"width between 10 and 18 will be read as OFTInteger64. Above they will be " +"treated as OFTReal. In previous GDAL versions, Integer fields were " +"created with a default with of 10, and thus will be now read as " +"OFTInteger64. An open option, ADJUST_TYPE=YES, can be specified so as OGR" +" does a full scan of the DBF file to see if integer fields of size 10 or " +"11 hold 32 bit or 64 bit values and adjust the type accordingly (and same" +" for integer fields of size 19 or 20, in case of overflow of 64 bit " +"integer, OFTReal is chosen)" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:228 +msgid "" +"PG: updated to read and create OFTInteger64 as INT8 and OFTInteger64List " +"as bigint[]. 64 bit FIDs are supported. By default, on layer creation, " +"the FID field is created as a SERIAL (32 bit integer) to avoid " +"compatibility issues. The FID64=YES creation option can be passed to " +"create it as a BIGSERIAL instead. If needed, the drivers will dynamically" +" alter the schema to extend a 32 bit integer FID field to 64 bit. " +"GetFeatureCount() modified to return 64 bit values. OLMD_FID64 = \"YES\" " +"advertized as soon as the FID column is 64 bit." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:237 +msgid "" +"PGDump: Integer64, Integer64List and 64 bit FID supported in read/write. " +"FID64=YES creation option available." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:239 +msgid "" +"GeoJSON: Integer64, Integer64List and 64 bit FID supported in read/write." +" The 64 bit variants are reported only if needed, otherwise " +"OFTInteger/OFTIntegerList is used. OLMD_FID64 = \"YES\" advertized if " +"needed" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:243 +msgid "" +"CSV: Integer64 supported in read/write, including the autodetection " +"feature of field types." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:245 +msgid "" +"GPKG: Integer64 and 64 bit FID supported in read/write. Conforming with " +"the GeoPackage spec, \"INT\" or \"INTEGER\" columns are considered 64 " +"bits, whereas \"MEDIUMINT\" is considered 32 bit. OLMD_FID64 = \"YES\" " +"advertized as soon as MAX(fid_column) is 64 bit. GetFeatureCount() " +"modified to return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:250 +msgid "" +"SQLite: Integer64 and 64 bit FID supported in read/write. On write, " +"Integer64 are createad as \"BIGINT\" and on read BIGINT or INT8 are " +"considered as Integer64. However it might be possible that databases " +"produced by other tools are created with \"INTEGER\" and hold 64 bit " +"values, in which case OGR will not be able to detect it. The " +":config:`OGR_PROMOTE_TO_INTEGER64=YES` configuration option can then be " +"passed to workaround that issue. OLMD_FID64 = \"YES\" advertized as soon " +"as MAX(fid_column) is 64 bit. GetFeatureCount() modified to return 64 bit" +" values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:259 +msgid "" +"MySQL: Integer64 and 64 bit FID supported in read/write. Similarly to PG," +" FID column is created as 32 bit by default, unless FID64=YES creation " +"option is specified. OLMD_FID64 = \"YES\" advertized as soon as the FID " +"column is 64 bit. GetFeatureCount() modified to return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:264 +msgid "" +"OCI: Integer64 and 64 bit FID supported in read/write. Detecting " +"Integer/Integer64 on read is tricky since there's only a NUMBER SQL type " +"with a field width. It is assumed that if the width is <= 9 or if it is " +"the unspecified value (38), then it is a Integer. On creation, OGR will " +"set a width of 20 for OFTInteger64, so a NUMBER without decimal part and " +"with a width of 20 will be considered as a Integer64." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:271 +msgid "" +"MEM: Integer64 and 64 bit FID supported in read/write. GetFeatureCount() " +"modified to return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:273 +msgid "" +"VRT: Integer64, Integer64List and 64 bit FID supported in read/write. " +"GetFeatureCount() modified to return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:275 +msgid "" +"JML: Integer64 supported on creation (created as \"OBJECT\"). On read, " +"returned as String" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:277 +msgid "" +"GML: Integer64, Integer64List and 64 bit FID supported in read/write. " +"GetFeatureCount() modified to return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:279 +msgid "" +"WFS: Integer64, Integer64List and 64 bit FID supported in read/write. " +"GetFeatureCount() modified to return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:281 +msgid "" +"CartoDB: Integer64 supported on creation. On read returned as Real " +"(CartoDB only advertises a 'Number' type). GetFeatureCount() modified to " +"return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:284 +msgid "XLSX: Integer64 supported in read/write." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:285 +msgid "ODS: Integer64 supported in read/write." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:286 +msgid "" +"MSSQLSpatial: GetFeatureCount() modified to return 64 bit values. No " +"Integer64 support implemented although could likely be done." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:288 +msgid "OSM: FID is now always set even when sizeof(long) != 8" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:289 +msgid "LIBKML: KML 'uint' advertized as Integer64." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:290 +msgid "" +"MITAB: Change the way FID of Seamless tables are generated to make it " +"more robust and accept arbitrary number of index tables made of an " +"arbitrary number of features, by using full 64bit width of IDs" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:297 +msgid "The test suite is extended to test the new capabilities:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:299 +msgid "core SetField/GetField methods" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:300 +msgid "" +"updated drivers: Shapefile, PG, GeoJSON, CSV, GPKG, SQLite, MySQL, VRT, " +"GML, XLSX, ODS, MITAB" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:303 +msgid "option -mapFieldType of ogr2ogr" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:309 +msgid "Driver Code Changes" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:311 +msgid "" +"All drivers implementing SetNextByIndex(), DeleteFeature(), GetFeature()," +" GetFeatureCount() will need to change their prototype and do modest " +"changes." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:315 +msgid "" +"Drivers supporting CreateField() likely ought to be extended to support " +"OFTInteger64 as an integer/real/string field if nothing else is available" +" (and if bApproxOK is TRUE). ogr2ogr will convert Integer64 to Real if " +"Integer64 support is not advertized" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:320 +msgid "" +"Drivers reporting FIDs via Debug statements, printf's or using sprintfs " +"like statements to format them for output have been updated to use " +"CPL_FRMT_GIB to format the FID. Failure to make these changes may result " +"in code crashing. Due to the use of GCC annotation to advertise " +"printf()-like formatting syntax in CPL functions, we are reasonably " +"confident to have done the required changes in in-tree drivers (except in" +" some proprietary drivers, like SDE, IDB, INGRES, ArcObjects, where this " +"couldn't be compiled-checked). The same holds true for GetFeatureCount()" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:331 +msgid "Application Code" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:333 +msgid "" +"Application code may need to be updated to use GIntBig for FIDs and " +"feature count in order to avoid warnings about downcasting." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:336 +msgid "" +"Application code formatting FIDs or feature count using printf like " +"facilities may also need to be changed to downcast explicitly or to use " +"CPL_FRMT_GIB." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:340 +msgid "" +"Application code may need to add Integer64 handling in order to utilize " +"wide fields." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:344 +msgid "Behavioral Changes" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:346 +msgid "" +"Wide integer fields that were previously treated as \"real\" or Integer " +"by the shapefile driver will now be treated as Integer64 which will " +"likely not work with some applications, and translation to other formats " +"may fail." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:352 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:580 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:388 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:131 +msgid "Related tickets" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:354 +msgid "" +"`#3747 OGR FID needs to be 64 bit " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:356 +msgid "" +"`#3615 Shapefile : A 10-digit value doesn't necessarily fit into a 32 bit" +" integer. `__" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:358 +msgid "" +"`#3150 Precision Problem for Numeric on OGR/OCI driver " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:362 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:465 +msgid "Related topics out of scope of this RFC" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:364 +msgid "" +"The possibility of having a Numeric type that corresponds to the matching" +" SQL type, i.e. a decimal number with an arbitrary number of significant " +"figures has been considered. In OGR, this could be implemented as a full " +"type like Integer, Integer64 etc., or possibly as a subtype of String " +"(see `RFC 50: OGR field subtypes <./rfc50_ogr_field_subtype>`__). The " +"latter approach would be easier to implement and mostly useful for " +"lossless conversion between database drivers (and shapefile). The former " +"approach would require more work, and would ideally involve OGR SQL " +"support, which would require supporting arithmetic of arbitrary length. " +"The use cases for such a numeric type have been considered marginal " +"enough to let that aside for now." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:380 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:502 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:592 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:87 +msgid "" +"Implementation will be done by Even Rouault (`Spatialys " +"`__), and sponsored by `LINZ (Land Information New " +"Zealand) `__." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:384 +msgid "" +"The proposed implementation lies in the \"rfc31_64bit\" branch of the " +"`https://github.com/rouault/gdal2/tree/rfc31_64bit " +"`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:388 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/rfc31_64bit " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:394 +msgid "+1 from JukkaR, DanielM, TamasS, HowardB and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:5 +msgid "RFC 32: gdallocationinfo utility" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:16 +msgid "" +"This document proposes the addition of a new standard commandline utility" +" for GDAL to report details about a location (pixel) in a raster." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:20 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:23 +#: ../../source/development/rfc/rfc34_license_policy.rst:41 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:21 +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:21 +#: ../../source/development/rfc/rfc45_virtualmem.rst:21 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:24 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:21 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:24 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:24 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:23 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:22 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:22 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:29 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:23 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:25 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:22 +msgid "Rationale" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:22 +msgid "" +"A user has a use case where they would like to be able to identify the " +"VRT file used to satisfy requests for a particular pixel / location." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:26 +msgid "" +"Many users have requested a tool to find the value of a location, often " +"expressed in a coordinate system different than that of the image. For " +"instance, \"what is the elevation at a given lat/long location?\"." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:31 +msgid "" +"The gdallocationinfo utility is intended to address both sorts of " +"requests, and hopefully in a way that will have some general value as a " +"\"raster point query\" tool." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:36 +msgid "gdallocationinfo" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:38 +msgid "Full docs are available at :ref:`gdallocationinfo`" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:46 +msgid "" +"The key aspects of the utility are control over the coordinate system of " +"the location (-s_srs, -geoloc, -wgs84) and various controls over the " +"output format (-xml, -lifonly, -valonly). An example of full output in " +"xml might be:" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:64 +msgid "LocationInfo Metadata Domain" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:66 +msgid "" +"The pixel values and location transformation logic is all built into " +"gdallocationinfo and doesn't require much elaboration. The more exotic " +"portion is reporting of \"LocationInfo\" queried from the datasource." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:70 +msgid "" +"For our immediate needs the requirement is to have the " +"VRTSourcedRasterBand return information on the file(s) overlapping the " +"target pixel. But, in theory different drivers might return different " +"sorts of information about a location. For instance, a WMS driver might " +"issue a GetFeatureInfo for the location and return the result." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:76 +msgid "" +"The mechanism to query the datasource is a specially named " +"GetMetadataItem() request against the \"LocationInfo\" domain of the " +"target band(s). The following requested item name is of the form " +"\"Pixel_x_y\" where x and y are the pixel and line of the pixel being " +"queried." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:82 +msgid "" +"The returned value from this item should either be NULL, or an XML " +"documented with the root element \"\". The contents of the document are " +"otherwise undefined as long as they are well formed XML. The VRT driver " +"returns a series of xxx entries for each of the files at that location." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:93 +msgid "might return:" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:104 +msgid "" +"A test will be introduced in the gdal utilities suite, and the " +"gdrivers/vrt.py script for the utility and VRT behavior respectively." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:110 +msgid "" +"Documentation for the utility has already been prepared and is referenced" +" above." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:116 +msgid "" +"Implementation is already complete, and in trunk. Adjustments can be made" +" by Frank Warmerdam as needed due to RFC revisions." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:5 +msgid "RFC 33: GTiff - Fixing PixelIsPoint Interpretation" +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:16 +msgid "" +"This document proposes changes in the GDAL GTiff (GeoTIFF) driver's " +"interpretation of PixelIsPoint when constructing the geotransform and " +"interpreting control points. An RFC is used due to the fundamental role " +"of GeoTIFF in GDAL and the GDAL user community and the risk for " +"significant backward compatibility problems with this adjustment." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:25 +msgid "" +"The GeoTIFF specification includes a data item, GTRasterTypeGeoKey, which" +" may be set to either RasterPixelIsArea (the default), or " +"RasterPixelIsPoint. RasterPixelIsArea defines that a pixel represents an " +"area in the real world, while RasterPixelIsPoint defines a pixel to " +"represent a point in the real world. Often this is useful to distinguish " +"the behavior of optical sensors that average light values over an area " +"vs. raster data which is point oriented like an elevation sample at a " +"point." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:34 +msgid "" +"Traditionally GDAL has treated this flag as having no relevance to the " +"georeferencing of the image despite disputes from a variety of other " +"software developers and data producers. This was based on the authors " +"interpretation of something said once by the GeoTIFF author. However, a " +"recent review of section [`section 2.5.2.2 " +"`__] " +"of the GeoTIFF specificaiton has made it clear that GDAL behavior is " +"incorrect and that PixelIsPoint georeferencing needs to be offset by a " +"half a pixel when transformed to the GDAL georeferencing model. This " +"issue is documented in the following tickets including #3837, #3838, ...." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:46 +msgid "" +"This RFC attempts to manage this transition with a minimum of disruption " +"for the users of GDAL/OGR." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:50 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:35 +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:50 +msgid "Planned Changes" +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:52 +msgid "" +"Interpretation of the raster space from the GeoTIFF tie points will be " +"offset by half a pixel in the PixelIsPoint case in " +"gdal/frmts/gtiff/geotiff.cpp. This will impact the formation of the " +"geotransform and the formation of GCPs when there are multiple tie " +"points. geotransmatrix conversion to geotransform will also be affected." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:58 +msgid "" +"Conversely if writing files with PixelIsPoint (as driven by the " +"\"AREA_OR_POINT\" metadata item being set to \"POINT\") the written " +"raster space coordinates would be offset by half a pixel." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:62 +msgid "" +"In trunk the above behavior may be disabled by setting the " +"GTIFF_POINT_GEO_IGNORE configuration option to TRUE (it will default to " +"FALSE)." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:66 +msgid "" +"In GDAL 1.7 and 1.6 branch the same changes will be applied, except the " +"GTIFF_POINT_GEO_IGNORE configuration option will default to TRUE." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:72 +msgid "" +"This change will alter the apparent georeferencing of all GeoTIFF files " +"with PixelIsPoint set. It is not clear how large a proportion of GeoTIFF " +"files this will apply to, but it is significant. This isn't too bad for " +"files coming from non-GDAL sources as most other produces have made the " +"correct interpretation of PixelIsPoint for years. However, unfortunately," +" files produced in the past by GDAL with PixelIsPoint will now be " +"interpreted differently and the values will be off by half a pixel." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:81 +msgid "" +"In practice it was not particularly convenient or well documented how to " +"produce PixelIsPoint GeoTIFF files with GDAL, so these files should be " +"fairly rare. Thee easiest way to produce them was by copying from another" +" PixelIsPoint GeoTIFF file in which the error on write just undid the " +"error when reading the source GeoTIFF file." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:88 +msgid "Reporting Extents" +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:90 +msgid "" +"Folks have at various points in the past requested that we report the " +"extents differently for files with an AREA_OR_POINT value of POINT, much " +"as listgeo does for GeoTIFF files that have a PixelIsPoint " +"interpretation. I do *not* plan to do this, and for the purpose of GDAL " +"the GCPs, RPCs and GeoTransform will always be based on an area " +"interpretation of pixels. The AREA_OR_POINT will *only* be used to " +"control setting of the PixelIsPoint value in GeoTIFF files, and as " +"metadata about the physical interpretation of pixels." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:100 +msgid "World Files" +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:102 +msgid "" +"These changes will have no impact on how world files are treated or " +"written. They are always based on the assumption of a area based pixel, " +"but with the origin at the center of the top left pixel. This is " +"effectively the same as the values for PixelIsPoint, but is not in any " +"way tried to this metadata." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:111 +msgid "The 1.6 and 1.7 branch test suites will not be altered." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:113 +msgid "" +"The trunk branch test suite will be altered to check for the updated " +"values and will be extended with a test to confirm that setting the " +"config option GTIFF_POINT_GEO_IGNORE to TRUE suppresses the altered " +"behavior." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:121 +msgid "" +"The situation will be noted in the 1.8.0, 1.7.4 and 1.6.4 release notes " +"as well as in the GeoTIFF driver documentation in trunk." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:124 +msgid "" +"The GeoTIFF web site GeoTIFF FAQ will be updated to clarify the " +"interpretation of PixelIsPoint and note that up to GDAL 1.8 it was " +"improperly interpreted by GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:131 +msgid "All code implementation will be by Frank Warmerdam in the next few weeks." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:134 +msgid "" +"Applied in trunk (r21158), 1.7 (r21159), 1.6 (r21160) and 1.6-esri " +"(r21161)." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:5 +msgid "RFC 34: License Policy Enforcement" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:16 +msgid "" +"This document proposes the addition of a new mechanisms so that " +"applications and end users can define a license policy, and so that GDAL " +"can help avoid license conflicts between proprietary and reciprocally " +"licensed applications and format drivers." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:24 +msgid "" +"Reciprocal FOSS License: A open source software license, such as the GPL," +" that requires all other software components linked into the same " +"executable and distributed beyond the creator to also be offered under " +"open source terms." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:29 +msgid "" +"Non-Reciprocal FOSS License: A open source software license, such as MIT," +" BSD or LGPL, that does not place any requirements on other linked " +"components in the same executable at distribution time." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:33 +msgid "" +"Proprietary License: Software provided under terms that do not adhere to " +"the requirements of the open source definition, such as libraries from " +"Oracle (OCI), Lizardtech (MrSID) and Erdas (ECW). While often offered for" +" zero cost, these components are incompatible with reciprocal FOSS " +"licenses and may place a variety of other restrictions on the distributor" +" or end user." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:43 +msgid "" +"GDAL/OGR is distributed under the Non-Reciprocal MIT open source license " +"which facilitates it's use by proprietary and open source applications, " +"and facilitates the inclusion of proprietary format drivers along side " +"the open source format drivers. However, it is still a license violation " +"to distribute reciprocally licensed applications (like QGIS and GRASS) " +"which use GDAL with proprietary licensed drivers (such as the MrSID, ECW " +"or Oracle drivers). Likewise, it is a license violation to distribute " +"proprietary applications with reciprocally licensed drivers such as the " +"GDAL GRASS driver, or the PDF driver." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:53 +msgid "" +"This RFC, and the improvements it promotes are intended to facilitate " +"users, applications and drivers setting and following license policies to" +" avoid unintentional license violations. One area this can be " +"particularly helpful is broad software distributions like `OSGeo4W " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:60 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:85 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:22 +msgid "Approach" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:62 +msgid "" +"The general approach proposed is that drivers will declare their license " +"category, and applications or end users will declare a policy for what " +"sorts of drivers may be used in combination with them. The " +"GDALDriverManager and OGRDriverRegistrar classes will apply this " +"information to avoid unintentional license violations." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:69 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:449 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:210 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:305 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:102 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:185 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:225 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:116 +msgid "Drivers" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:71 +msgid "" +"Drivers will declare one of these three driver specific licensing " +"policies via the \"LICENSE_POLICY\" (DMD_LICENSE_POLICY) metadata item on" +" the driver:" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:75 +msgid "" +"\"RECIPROCAL\": the driver is available under a reciprocal FOSS license " +"such as the GPL, and should not be mixed with proprietary drivers or " +"applications." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:78 +msgid "" +"\"NONRECIPROCAL\": the driver is available under a non-reciprocal FOSS " +"license such as MIT, or LGPL. This is the default if no licensing policy " +"is declared and is the natural policy of drivers provided as part of GDAL" +" without outside dependencies." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:82 +msgid "" +"\"PROPRIETARY\": the driver, usually due to use of proprietary libraries," +" has some licensing restrictions which make it ineligible for " +"distribution with reciprocally licensed software. This would include " +"MrSID, ECW, and Oracle related drivers." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:88 +msgid "Application License Policy" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:90 +msgid "" +"Applications are encouraged to set one of the following licensing " +"policies reflective of the applications nature. The policy should be set " +"as the value of the GDAL_APPLICATION_LICENSE_POLICY configuration " +"variable, typically via a call to GDALSetConfigOption() *before* the call" +" to GDALAllRegister() or OGRRegisterAll()." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:96 +msgid "" +"\"RECIPROCAL\": the application is licensed under a reciprocal license " +"such as the GPL, and no proprietary drivers should be loaded." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:98 +msgid "" +"\"PROPRIETARY\": the application has some licensing restrictions which " +"make it ineligible for distribution with reciprocally licensed software. " +"Care will be taken to avoid loading reciprocally licensed drivers, such " +"as the GRASS and PDF drivers." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:102 +msgid "" +"\"DEFAULT\": the application does not apply any licensing restrictions. " +"This is typical of non-GPL open source applications such as MapServer, " +"and will be the default policy if nothing is declared." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:107 +msgid "User License Policy" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:109 +msgid "" +"The restrictions on mixing proprietary and reciprocally licensed software" +" generally applies at the point of distribution. In particular, it is not" +" intended to prevent the end user from assembling a variety of components" +" for their own use as they see fit, for their own use. To that end it is " +"important to provide a mechanism for the end user to deliberately " +"override the restrictions on mixing reciprocally licensed, and " +"proprietary components. This is accomplished via the GDAL_LICENSE_POLICY " +"configuration variable which might typically be set via the environment " +"or via the --config commandline switch to most GDAL applications. It may " +"have the following values:" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:120 +msgid "\"USE_ALL\": do not discard any drivers based on licensing restrictions." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:122 +msgid "" +"\"PREFER_PROPRIETARY\": If there is a conflict between proprietary and " +"reciprocally licensed drivers, use the proprietary ones." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:124 +msgid "" +"\"PREFER_RECIPROCAL\": If there is a conflict between proprietary and " +"reciprocally licensed drivers, use the reciprocally licensed ones." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:127 +msgid "" +"In addition to setting this via config variables, there will also be a " +"configure / nmake.opt declaration to alter the default " +"GDAL_LICENSE_POLICY. Thus a local build could be configured to USE_ALL at" +" build time instead of having to set environment variables or commandline" +" switches. This would not be suitable for software that will be " +"redistributed." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:135 +msgid "Policy Logic" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:137 +msgid "" +"If the user selected a GDAL_LICENSE_POLICY of \"USE_ALL\" then no drivers" +" are unloaded on the basis of licensing." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:139 +msgid "" +"If the user selected a GDAL_LICENSE_POLICY of \"PREFER_PROPRIETARY\" or " +"\"PREFER_RECIPROCAL\" then ignore the GDAL_APPLICATION_LICENSE_POLICY." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:141 +msgid "" +"if the application select a GDAL_APPLICATION_LICENSE_POLICY of " +"\"PROPRIETARY\" or \"RECIPROCAL\" then use that." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:143 +msgid "" +"In the absence of a user or application level policy, default to a policy" +" of \"PREFER_PROPRIETARY\"." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:146 +msgid "" +"The policy will be applied in the GDALDriverManager::AutoSkipDrivers() " +"method and in the newly introduced OGRSFDriverManager::AutoSkipDrivers() " +"method. The AutoSkipDrivers() method is already used to unload drivers " +"based on GDAL_SKIP (and soon OGR_SKIP) and is generally called after the " +"preliminary registration of drivers." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:153 +msgid "Strict Link Level Compliance" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:155 +msgid "" +"The GPL, the leading reciprocal license, talks about distribution of GPL " +"applications with proprietary code linked in. In a literal sense we may " +"still have running processes with mixed code linked in. Instead of " +"addressing the problem at the point of linking we are disabling use of " +"incompatible components at runtime. There is some small risk that this " +"may be considered not to be compliant with the requirements of the GPL " +"license in a literal sense, though it is clear we are making every " +"reasonable effort to enforce it in a practical sense." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:164 +msgid "" +"In the situation of standalone software packages being distributed with " +"GDAL, it may still be best for those preparing the package to completely " +"omit any components incompatible with the license of the applications. " +"This RFC is primarily intended to support complex mixed-component " +"distributions such as OSGeo4W." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:173 +msgid "I believe the following drivers should be marked as \"PROPRIETARY\":" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:176 +msgid "JP2ECW" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:178 +msgid "JP2MRSID" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:179 +msgid "MG4Lidar" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:180 +msgid "GEORASTER" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:182 +msgid "JPIPKAK" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:183 +msgid "ArcObjects" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:184 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:106 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:63 +msgid "OCI" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:186 +msgid "FME" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:187 +msgid "ArcSDE (raster and vector)" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:189 +msgid "I believe the following drivers should be marked as \"RECIPROCAL\":" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:191 +msgid "grass (raster and vector)" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:192 +msgid "EPSILON" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:193 +msgid "MySQL (depending on active license terms!)" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:194 +msgid "PDF" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:196 +msgid "Unresolved:" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:198 +msgid "" +"The OGR SOSI driver should probably be marked as proprietary currently as" +" it relies on linking with binary objects with unknown licencing terms, " +"even if apparently the ultimate goal seems to open source them." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:202 +msgid "" +"I'm a bit confused by :ref:`raster.msg`. Seems that it relies on third " +"party stuff with both proprietary and GPL code." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:205 +msgid "" +"I am unsure about the ODBC based drivers. I suppose PGEO and MSSQLSPATIAL" +" drivers ought to be marked proprietary too? Might it depend on the " +"actual license terms of the odbc library?" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:209 +msgid "Please let me know of other drivers needing marking." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:212 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:121 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:398 +#: ../../source/development/rfc/rfc91_dataset_close.rst:160 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:156 +msgid "SWIG Bindings" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:214 +msgid "" +"Some (all?) swig bindings automatically call GDALAllRegister() and/or " +"OGRRegisterAll() at the point the bindings are loaded making it hard to " +"set the application level GDAL_LICENSE_POLICY in a script before the " +"registration takes place. To address that I believe we should expose the " +"AutoSkipDrivers() methods via SWIG so that scripts can set the policy and" +" then \"clean\" the drivers based on the policy in force." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:224 +msgid "How to test?" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:229 +msgid "How to document?" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:234 +msgid "" +"Frank Warmerdam will do the core implementation in trunk. Driver " +"maintainers may need to update the metadata for particular drivers." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:5 +msgid "RFC 35: Delete, reorder and alter field definitions of OGR layers" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:7 +#: ../../source/development/rfc/rfc45_virtualmem.rst:7 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:7 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:7 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:7 +msgid "Authors: Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:9 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:9 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:9 +#: ../../source/development/rfc/rfc45_virtualmem.rst:9 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:9 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:9 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:9 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:9 +msgid "Contact: even dot rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:16 +msgid "" +"This document proposes changes in OGR to add the capability to delete " +"fields, reorder fields and alter field definitions, in OGR layer " +"definitions." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:23 +msgid "" +"Currently, an OGR layer definition can only be altered to add a new field" +" definition with OGRLayer::CreateField()." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:26 +msgid "" +"It is desirable to extend OGR capabilities to be able to delete, reorder " +"and alter field definitions of existing layers. Such wish has been " +"expressed in ticket #2671 and comes back regularly on QGIS mailing list " +"(e.g. `http://lists.osgeo.org/pipermail/qgis-user/2011-May/011935.html " +"`__). " +"QGIS currently has a \"Table Manager\" extension to work around the lack " +"of DeleteField(), so a proper solution is clearly needed." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:37 +msgid "The OGRLayer class will be extended with the following methods :" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:48 +msgid "The documentation of those new methods is :" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:183 +msgid "Three new layer capabilities are added :" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:196 +msgid "The new methods are mapped to the C API :" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:205 +msgid "" +"For the purpose of the implementation, new methods are also added to the " +"OGRFeatureDefn class :" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:213 +msgid "" +"A OGRErr OGRCheckPermutation(int\\* panPermutation, int nSize) function " +"is added to ogrutils.cpp to check that the array is a permutation of " +"[0,nSize-1]. It is used by OGRFeatureDefn::ReorderFieldDefns() and can be" +" used by all drivers implementing OGRLayer::ReorderFields() to validate " +"the panMap argument." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:220 +msgid "Altering field types" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:222 +msgid "" +"This RFC does not attempt to guarantee which type conversions will be " +"possible. It will depend on the capabilities of the implementing drivers." +" For example, for database drivers, the operation will be directly done " +"on the server side (through a 'ALTER TABLE my_table ALTER COLUMN " +"my_column TYPE new_type' command for the PG driver). So some conversions " +"might be possible, others not..." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:229 +msgid "" +"It is however expected that converting from any type to OFTString will be" +" supported in most cases when AlterFieldDefn() is supported." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:232 +msgid "" +"Drivers that don't support a conversion and that were required to do it " +"(ALTER_TYPE_FLAG set and new_type != old_type) should emit an explicit " +"error." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:239 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:61 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:189 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:405 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:126 +msgid "None" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:242 +msgid "Changed drivers" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:244 +msgid "" +"The shapefile driver will implement DeleteField(), ReorderFields() and " +"AlterFieldDefn(). Shapelib will be extended with DBFReorderFields() and " +"DBFAlterFieldDefn()." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:248 +msgid "" +"Note: The implementation of AlterFieldDefn() in the Shapefile driver does" +" not support altering the field type, except when converting to " +"OFTString. It will not reformat numeric values of existing features if " +"width or precision are changed. However, appropriate field truncation or " +"expansion will occur if the width is altered." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:254 +msgid "" +"Other drivers, mainly database drivers (PG, MySQL, SQLite), could be " +"easily extended to implement the new API by issuing the appropriate SQL " +"command (ALTER TABLE foo DROP COLUMN bar, ALTER TABLE foo ALTER COLUMN " +"bar, ...). The implementation of DeleteField() and AlterFieldDefn() in " +"the PG driver is indeed planned, provided this RFC is adopted. The Memory" +" driver will also updated to support DeleteField(), ReorderFields() and " +"AlterFieldDefn()." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:263 +#: ../../source/development/rfc/rfc45_virtualmem.rst:1168 +#: ../../source/development/rfc/rfc84_cmake.rst:125 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:88 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:262 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:656 +msgid "SWIG bindings" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:265 +msgid "" +"DeleteField(), ReorderField(), ReorderFields() and AlterFieldDefn() will " +"be mapped to SWIG." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:271 +msgid "" +"The autotest suite will be extended to test the implementation of the new" +" API for the Shapefile driver. An example of the use of the new API is " +"attached to ticket #2671 (`rfc35_test.py " +"`__) and" +" will be turned into unit tests." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:280 +msgid "" +"Implementation will be done by Even Rouault in GDAL/OGR trunk. Changes in" +" Shapelib will need to be pushed into upstream CVS by a Shapelib " +"committer. The proposed implementation is attached as a patch in ticket " +"#2671 (`rfc35_v3.patch " +"`__)." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:289 +msgid "+1 from FrankW, DanielM, HowardB, TamasS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:5 +msgid "RFC 36: Allow specification of intended driver on GDALOpen (withdrawn)" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:7 +msgid "Authors: Ivan Lucena" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:9 +msgid "Contact: ivan.lucena@pmldnet.com" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:11 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:11 +msgid "Status: Withdrawn." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:13 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:13 +msgid "Covered by `RFC 46: GDAL/OGR unification <./rfc46_gdal_ogr_unification>`__" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:18 +msgid "" +"This document proposes a mechanism to explicitly tell GDAL what driver " +"should open a particular dataset." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:22 +msgid "Justification" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:24 +msgid "" +"By selecting the driver, users can optimize processing time and avoid " +"incorrect or undesirable driver selection due to the driver probing " +"mechanism." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:29 +msgid "Concept" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:31 +msgid "" +"The idea is to pass to GDALOpen a string containing the token \"driver=\"" +" followed by the driver name and a comma separating it from the file-" +"name." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:35 +msgid "[driver=driver-name,]file-name" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:37 +msgid "Examples:" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:39 +msgid "$ gdalinfo driver=nitf:imagefile01.ntf" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:41 +msgid "" +"In that case no probing is necessary, since the user has indicated to use" +" the specific driver. If for some reason that process fails the function " +"returns NULL and no other attempt is made to open the file by another " +"driver." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:49 +msgid "" +"The amount of code is minimal and there is already a proposed patch on " +"ticket #3043." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:55 +msgid "" +"Any application that uses GDAL API or any GDAL command line tool's user " +"that, at one point, wants to force the use of a particular driver to open" +" a datasets." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:62 +msgid "" +"That optional entry on GDALOpen process should not affect the current " +"logic." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:68 +msgid "Extra tests would be added to the test script" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:73 +msgid "" +"For gdalbuildvrt and gdaltindex it will not be possible to use the driver" +" selection with wildcard, as in \"driver=gtiff,*.tif\"." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:5 +msgid "RFC 37: User data callbacks in CPLError" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst +msgid "Date" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:7 +msgid "2011/10/25" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst +msgid "Author" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:8 +#: ../../source/development/rfc/rfc3_commiters.rst:218 +#: ../../source/development/rfc/rfc74_sphinx.rst:8 +msgid "Howard Butler" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst +msgid "Contact" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:9 +msgid "hobu.inc at gmail dot com" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst +msgid "Status" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:10 +msgid "Implemented" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst +msgid "Version" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:11 +msgid "GDAL 1.9" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst +msgid "Voting" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:12 +msgid "+1 Frank, Howard, Tamas, Daniel, Even" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:15 +msgid "" +"Description: This RFC proposes to implement user context data in " +"CPLErrorHandler callback functions. It does so without disrupting " +"existing callback patterns already in use, and provides completely " +"auxiliary functionality to CPLErrorHandler." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:23 +msgid "" +"It could be argued that users could already manage user context of error " +"handling functions with application-level globals that control its " +"interaction. While this sentiment is technically true, this approach adds" +" a ton of complication for library users. A scenario that has error " +"callbacks pass back user context data means simpler code for users " +"wishing to have the state of their application be returned along with " +"errors from inside of GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:30 +msgid "The case for user data be passed in callbacks:" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:32 +msgid "" +"It is a common idiom for signal-based APIs (of which CPLErrorHandler is " +"one)" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:33 +msgid "" +"It is simpler than requiring library users to manage the state of " +"internal library error handling externally in their own applications" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:38 +msgid "Implementation Concerns" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:40 +msgid "" +"GDAL's (and OGR and OSR's) error handling callback mechanisms are in wide" +" use and changes to the base library that were to break either the " +"callback signatures *or* the behavior of existing callback operations " +"should be rejected. Adding support for user data in the call back is to " +"be provided in addition to existing functionality that already exists in " +"the error handling, and an approach that mimics and looks similar to the " +"existing operations is likely the best approach for GDAL -- if not the " +"cleanest approach in general." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:52 +msgid "The first change will add a void* to CPLErrorHandlerNode:" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:63 +msgid "and to methods to add error handlers with user data will be provided:" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:70 +msgid "" +"``CPLSetErrorHandler`` and ``CPLPushErrorHandler`` will simply use the " +"``Ex`` functions and pass NULL in for the pUserData member." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:73 +msgid "" +"Finally, similar to ``CPLGetLastErrorType`` and ``CPLGetLastErrorMsg`` " +"methods, a ``CPLGetErrorHandlerUserData``" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:81 +msgid "SWIG bindings consideration" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:83 +msgid "" +"The SWIG bindings will *not* be updated to provide access to user data " +"for the currently active error handler for implementation of this RFC. " +"SWIG bindings maintainers can take advantage of this new functionality at" +" their discretion, however." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:89 +msgid "Ticket History" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:91 +msgid "" +"`http://trac.osgeo.org/gdal/ticket/4295 " +"`_ contains a patch that " +"implements the proposed solution and provides context and discussion " +"about this feature. " +"http://trac.osgeo.org/gdal/attachment/ticket/4295/4295-hobu-rfc.patch " +"contains the current patch to implemented the proposed functionality." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:98 +msgid "Documentation of the added functions is provided as part of the patch." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:103 +msgid "" +"All code will be implemented in trunk by Howard Butler after passage of " +"the RFC." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:5 +msgid "RFC 38: OGR Faster Open (withdrawn)" +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:18 +msgid "" +"It is proposed that the OGR datasource opening mechanism relies on the " +"GDALOpenInfo class, already used by GDAL drivers, to speed-up datasource " +"opening. The speed-up is due to the fact that the file passed to " +"OGROpen() will be opened and stat'ed only once, whereas currently, it is " +"opened and closed as many times as there are OGR drivers. This should be " +"particularly beneficial for network filesystems, or when trying to open a" +" file that is not a OGR datasource at all." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:26 +msgid "" +"E.g., trying to open a file that is not a OGR datasource currently " +"requires 45 file opening or stat operations :" +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:34 +msgid "" +"It is expected that if/once all drivers are migrated, it will decrease to" +" 2 operations only." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:40 +msgid "" +"Similarly to GDALDriver, the OGRSFDriver class is extended to have a " +"pfnOpen member, that drivers will set to point to their own Open method." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:52 +msgid "" +"The OGRSFDriverRegistrar::Open() method is updated to call pfnOpen when " +"iterating over the drivers. When pfnOpen is not set, it will try to call " +"the Open() method of OGRSFDriver (which enables a progressive migration " +"of drivers)." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:57 +msgid "" +"Mainly for compatibility reasons, the virtual method Open() of " +"OGRSFDriver that is currently pure virtual, will now be a regular virtual" +" method, that will have a default implementation, that will try to call " +"pfnOpen." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:62 +msgid "The patch with the changes to OGR core is attached to this page." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:67 +msgid "Proposed additions will not have any impact on C binary compatibility." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:69 +msgid "" +"C++ binary interface will be broken (due to the addition of a new member " +"in OGRSFDriver class and the Open() method changed from pure virtual to " +"virtual)." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:73 +msgid "Source level compatibility will be preserved for third-party OGR drivers." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:77 +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:61 +msgid "Impact on drivers" +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:79 +msgid "" +"Existing drivers are *not* required to migrate to RFC38, but are strongly" +" encouraged to. New drivers *should* use RFC38 mechanism to preserve the " +"overall faster opening." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:83 +msgid "An example of the migration for a few drivers is attached to this page." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:86 +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:66 +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:99 +msgid "Timeline" +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:88 +msgid "" +"Even Rouault is responsible to implement this proposal. New API will be " +"available in GDAL 2.0. Most in-tree OGR drivers will be migrated to the " +"new mechanism." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:5 +msgid "RFC 39: OGR Layer Algebra" +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:7 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:7 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:7 +msgid "Author: Ari Jolma" +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:9 +msgid "Contact: ari dot jolma at aalto dot fi" +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:11 +msgid "Status: Adopted, implemented in GDAL 1.10" +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:16 +msgid "" +"It is proposed that the OGR layer class and the C API contains methods " +"for commonly needed overlay analysis methods." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:19 +msgid "" +"The basic functionality for spatial analysis with GDAL is provided by " +"GEOS. However, GEOS operates on geometries and typically people work with" +" geospatial data layers. Vector data layers are represented in GDAL by " +"OGRLayer objects. Thus, there is a need for spatial analaysis operations " +"that work on layers." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:25 +msgid "" +"Unfortunately there is no standard for spatial analysis operations API, " +"but it is possible to create a useful set by using existing software as " +"example." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:29 +msgid "" +"The methods are fundamentally dependent on comparison of all the features" +" of two layers. There would possibly be huge performance improvements " +"achievable with layer specific spatial indexes. This is considered out of" +" the scope of these methods and belonging to the general problem of " +"iterating features in a layer and accessing features randomly. For these " +"reasons these methods should be only considered convenience methods and " +"not replacements for analysis in relational databases for example." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:41 +msgid "" +"The methods are implemented by new methods in OGRLayer class " +"(ogrsf_frmts.h and ogrlayer.cpp) and new calls in the C API (ogr_api.h). " +"The Swig bindings (ogr.i) are also extended with these methods." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:45 +msgid "" +"The patch with the changes to OGR core and to the Swig bindings is " +"attached to this page. The patch has been superficially tested but it is " +"not written or formatted according to the GDAL tradition." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:52 +msgid "" +"Proposed additions will have an impact on C binary compatibility because " +"they change the API." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:55 +msgid "" +"C++ binary interface will be broken (due to the addition of a new members" +" in OGRLayer class)." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:58 +msgid "The changes are purely extensions and have no impact on existing code." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:63 +msgid "The changes do not have any impacts on drivers." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:68 +msgid "" +"Ari Jolma is responsible to implement this proposal. New API should be " +"available in GDAL 1.11." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:71 +msgid "" +"There needs to be a discussion on the names of the methods and on the " +"internal logic of the methods (this refers especially to the handling of " +"attributes and error conditions)." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:75 +msgid "" +"In addition to the methods in the attached patch, there should be some " +"discussion on additional methods. For example Append and Buffer methods " +"could be easily added to the set. An illustration of what is currently " +"available in the common software is for example this page: " +"`http://courses.washington.edu/gis250/lessons/Model_Builder/ " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:82 +msgid "Comments on performance" +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:84 +msgid "" +"Profiling Intersection of a layer of 46288 line string features with a " +"layer of one polygon feature (~1/3 of features within and many only " +"partly within the one feature) showed that when the method layer was a " +"Shapefile, most of the time was spent in reading the feature from the " +"Shapefile. When the method layer was copied into memory, most of the time" +" (83 %) was spent in OGRLineString::getEnvelope. The 6th version of the " +"patch contains a test against a pre-computed layer envelope, which speeds" +" up the computation in this case ~30% (from 2.44 s to 1.76 in my " +"machine). Still the most of the time (82 %) is spent in " +"OGRLineString::getEnvelope." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:98 +msgid "(June 2012) +1 from Even, Frank, Howard, Tamas, Daniel" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:5 +msgid "RFC 3: GDAL Committer Guildlines" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:14 +#: ../../source/development/rfc/rfc7_vsilapi.rst:14 +#: ../../source/development/rfc/rfc8_devguide.rst:14 +#: ../../source/development/rfc/rfc9_maintainer.rst:14 +msgid "Purpose" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:16 +msgid "" +"To formalize SVN (or CVS) commit access, and specify some guidelines for " +"SVN committers." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:20 +msgid "Election to SVN Commit Access" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:22 +msgid "" +"Permission for SVN commit access shall be provided to new developers only" +" if accepted by the GDAL/OGR Project Steering Committee. A proposal " +"should be written to the PSC for new committers and voted on normally. It" +" is not necessary to write an RFC document for these votes, a proposal to" +" gdal-dev is sufficient." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:28 +msgid "Removal of SVN commit access should be handled by the same process." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:30 +msgid "" +"The new committer should have demonstrated commitment to GDAL/OGR and " +"knowledge of the GDAL/OGR source code and processes to the committee's " +"satisfaction, usually by reporting bugs, submitting patches, and/or " +"actively participating in the GDAL/OGR mailing list(s)." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:35 +msgid "" +"The new committer should also be prepared to support any new feature or " +"changes that he/she commits to the GDAL/OGR source tree in future " +"releases, or to find someone to which to delegate responsibility for them" +" if he/she stops being available to support the portions of code that " +"he/she is responsible for." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:41 +msgid "" +"All committers should also be a member of the gdal-dev mailing list so " +"they can stay informed on policies, technical developments and release " +"preparation." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:45 +msgid "" +"New committers are responsible for having read, and understood this " +"document." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:49 +msgid "Committer Tracking" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:51 +msgid "" +"A list of all project committers will be kept in the main gdal directory " +"(called COMMITTERS) listing for each SVN committer:" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:54 +msgid "Userid: the id that will appear in the SVN logs for this person." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:55 +msgid "Full name: the users actual name." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:56 +msgid "" +"Email address: A current email address at which the committer can be " +"reached. It may be altered in normal ways to make it harder to auto-" +"harvest." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:59 +msgid "A brief indication of areas of responsibility." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:62 +msgid "SVN Administrator" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:64 +msgid "" +"One member of the Project Steering Committee will be designed the SVN " +"Administrator. That person will be responsible for giving SVN commit " +"access to folks, updating the COMMITTERS file, and other SVN related " +"management. That person will need login access on the SVN server of " +"course." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:70 +msgid "Initially Frank Warmerdam will be the SVN Administrator." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:73 +msgid "SVN Commit Practices" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:75 +msgid "" +"The following are considered good SVN commit practices for the GDAL/OGR " +"project." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:78 +msgid "Use meaningful descriptions for SVN commit log entries." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:79 +msgid "" +"Add a bug reference like \"(#1232)\" at the end of SVN commit log entries" +" when committing changes related to a ticket in Trac. The '#' character " +"enables Trac to create a hyperlink from the changeset to the mentioned " +"ticket." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:83 +msgid "" +"After committing changes related to a ticket in Trac, write the tree and " +"revision in which it was fixed in the ticket description. Such as \"Fixed" +" in trunk (r12345) and in branches/1.7 (r12346)\". The 'r' character " +"enables Trac to create a hyperlink from the ticket to the changeset." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:88 +msgid "" +"Changes should not be committed in stable branches without a " +"corresponding bug id. Any change worth pushing into the stable version is" +" worth a bug entry." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:91 +msgid "" +"Never commit new features to a stable branch without permission of the " +"PSC or release manager. Normally only fixes should go into stable " +"branches." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:94 +msgid "New features go in the main development trunk." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:95 +msgid "" +"Only bug fixes should be committed to the code during pre-release code " +"freeze, without permission from the PSC or release manager." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:97 +msgid "" +"Significant changes to the main development version should be discussed " +"on the gdal-dev list before you make them, and larger changes will " +"require a RFC approved by the PSC." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:100 +msgid "" +"Do not create new branches without the approval of the PSC. Release " +"managers are assumed to have permission to create a branch." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:102 +msgid "" +"All source code in SVN should be in Unix text format as opposed to DOS " +"text mode." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:104 +msgid "" +"When committing new features or significant changes to existing source " +"code, the committer should take reasonable measures to insure that the " +"source code continues to build and work on the most commonly supported " +"platforms (currently Linux and Windows), either by testing on those " +"platforms directly, running [wiki:Buildbot] tests, or by getting help " +"from other developers working on those platforms. If new files or library" +" dependencies are added, then the configure.in, Makefile.in, Makefile.vc " +"and related documentations should be kept up to date." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:115 +msgid "Relationship with other upstream projects imported in GDAL/OGR code base" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:117 +msgid "" +"Some parts of the GDAL/OGR code base are regularly refreshed from other " +"upstream projects. So changes in those areas should go first into those " +"upstream projects, otherwise they may be lost during a later refresh. " +"Note that those directories may contain a mix of GDAL specific files and " +"upstream files. This has to be checked on a case-by-case basis (any file " +"with CVS changelog at its beginning is a good candidate for belonging to " +"the upstream project)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:125 +msgid "Currently the list of those areas is :" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:127 +msgid "" +"frmts/gtiff/libtiff : from libtiff CVS " +"(`http://www.remotesensing.org/libtiff/ " +"`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:129 +msgid "" +"frmts/gtiff/libgeotiff : from libgeotiff SVN " +"(`http://trac.osgeo.org/geotiff/ `__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:131 +msgid "" +"frmts/jpeg/libjpeg : from libjpeg project " +"(`http://sourceforge.net/projects/libjpeg/ " +"`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:133 +msgid "" +"frmts/png/libpng : from libpng project " +"(`http://www.libpng.org/pub/png/libpng.html " +"`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:135 +msgid "" +"frmts/gif/giflib : from giflib project " +"(`http://sourceforge.net/projects/giflib " +"`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:137 +msgid "" +"frmts/zlib : from zlib project (`http://www.zlib.net/ " +"`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:139 +msgid "" +"ogr/ogrsf_frmts/mitab : from MITAB CVS (`http://mitab.maptools.org/ " +"`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:141 +msgid "" +"ogr/ogrsf_frmts/avc : from AVCE00 CVS (`http://avce00.maptools.org/ " +"`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:143 +msgid "" +"ogr/ogrsf_frmts/shape/[dbfopen.c, shpopen.c, shptree.c, shapefil.h] : " +"from shapelib project (`http://shapelib.maptools.org/ " +"`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:146 +msgid "data/ : some .csv files related to CRS come from libgeotiff" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:149 +msgid "Legal" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:151 +msgid "" +"Committers are the front line gatekeepers to keep the code base clear of " +"improperly contributed code. It is important to the GDAL/OGR users, " +"developers and the OSGeo foundation to avoid contributing any code to the" +" project without it being clearly licensed under the project license." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:156 +msgid "" +"Generally speaking the key issues are that those providing code to be " +"included in the repository understand that the code will be released " +"under the MIT license, and that the person providing the code has the " +"right to contribute the code. For the committer themselves understanding " +"about the license is hopefully clear. For other contributors, the " +"committer should verify the understanding unless the committer is very " +"comfortable that the contributor understands the license (for instance " +"frequent contributors)." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:165 +msgid "" +"If the contribution was developed on behalf of an employer (on work time," +" as part of a work project, etc) then it is important that an appropriate" +" representative of the employer understand that the code will be " +"contributed under the MIT license. The arrangement should be cleared with" +" an authorized supervisor/manager, etc." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:171 +msgid "" +"The code should be developed by the contributor, or the code should be " +"from a source which can be rightfully contributed such as from the public" +" domain, or from an open source project under a compatible license." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:176 +msgid "All unusual situations need to be discussed and/or documented." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:178 +msgid "" +"Committers should adhere to the following guidelines, and may be " +"personally legally liable for improperly contributing code to the source " +"repository:" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:182 +msgid "" +"Make sure the contributor (and possibly employer) is aware of the " +"contribution terms." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:184 +msgid "" +"Code coming from a source other than the contributor (such as adapted " +"from another project) should be clearly marked as to the original source," +" copyright holders, license terms and so forth. This information can be " +"in the file headers, but should also be added to the project licensing " +"file if not exactly matching normal project licensing (gdal/LICENSE.txt)." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:190 +msgid "" +"Existing copyright headers and license text should never be stripped from" +" a file. If a copyright holder wishes to give up copyright they must do " +"so in writing to the foundation before copyright messages are removed. If" +" license terms are changed it has to be by agreement (written in email is" +" ok) of the copyright holders." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:195 +msgid "" +"Code with licenses requiring credit, or disclosure to users should be " +"added to /trunk/gdal/LICENSE.TXT." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:197 +msgid "" +"When substantial contributions are added to a file (such as substantial " +"patches) the author/contributor should be added to the list of copyright " +"holders for the file." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:200 +msgid "" +"If there is uncertainty about whether a change it proper to contribute to" +" the code base, please seek more information from the project steering " +"committee, or the foundation legal counsel." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:205 +msgid "Bootstraping" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:207 +msgid "" +"The following existing committers will be considered authorized GDAL/OGR " +"committers as long as they each review the committer guidelines, and " +"agree to adhere to them. The SVN administrator will be responsible for " +"checking with each person." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:212 +msgid "Daniel Morissette" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:213 +msgid "Frank Warmerdam" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:214 +msgid "Gillian Walter" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:215 +msgid "Andrey Kiselev" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:216 +msgid "Alessandro Amici" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:217 +msgid "Kor de Jong" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:219 +msgid "Lichun Wang" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:220 +msgid "Norman Vine" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:221 +msgid "Ken Melero" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:222 +msgid "Kevin Ruland" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:223 +msgid "Marek Brudka" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:224 +msgid "Pirmin Kalberer" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:225 +msgid "Steve Soule" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:226 +msgid "Frans van der Bergh" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:227 +msgid "Denis Nadeau" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:228 +msgid "Oleg Semykin" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:229 +msgid "Julien-Samuel Lacroix" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:230 +msgid "Daniel Wallner" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:231 +msgid "Charles F. I. Savage" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:232 +msgid "Mateusz Loskot" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:233 +msgid "Peter Nagy" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:234 +msgid "Simon Perkins" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:235 +msgid "Radim Blazek" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:236 +msgid "Steve Halasz" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:237 +msgid "Nacho Brodin" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:238 +msgid "Benjamin Collins" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:239 +msgid "Ivan Lucena" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:240 +msgid "Ari Jolma" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:241 +msgid "Tamas Szekeres" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:245 +msgid "" +"`COMMITTERS `__" +" file" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:247 +msgid "" +"`Edit GDAL Subversion Group `__" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:5 +msgid "" +"RFC 40: Improving performance of Raster Attribute Table implementation " +"for large tables" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:8 +msgid "Summary:" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:10 +msgid "" +"Raster Attrbute Tables from some applications (notably segmentation) can " +"be very large and are slow to access with the current API due to the way " +"only one element can get read or written at a time. Also, when an " +"attribute table is requested by the application the whole table must be " +"read - there is no way of delaying this so just the required subset is " +"read off disk. These changes will bring the attribute table support more " +"in line with the way raster data is accessed." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:19 +msgid "Implementation:" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:21 +msgid "" +"It is proposed that GDALRasterAttributeTable be re-written as a virtual " +"base class. This will allow drivers to have their own implementation that" +" only reads and writes data when requested. A new derived class, " +"GDALDefaultRasterAttributeTable will be provided that provides the " +"functionality of the GDAL 1.x GDALRasterAttributeTable (ie holds all data" +" in memory)." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:28 +msgid "" +"Additional methods will be provided in the GDALRasterAttributeTable class" +" that allow 'chunks' of data from a column to be read/written in one " +"call. As with the GetValueAs functions columns of different types would " +"be able to read as a value of a different type (i.e., read a int column " +"as a double) with the appropriate conversion taking place. The following " +"overloaded methods will be available:" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:41 +msgid "" +"It is expected that the application will allocate the required space for " +"reading in the same way as with the RasterIO() call." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:44 +msgid "" +"The char*\\* type will be used for reading and writing strings. When " +"reading strings, it is expected that the array is created of the correct " +"size and ValuesIO will just create the individual strings for each row. " +"The application should call CPLFree on each of the strings before de-" +"allocating the array." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:50 +msgid "" +"These methods will be available from C as GDALRATValuesIOAsDouble, " +"GDALRATValuesIOAsInteger and GDALRATValuesIOAsString." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:53 +msgid "" +"This is also an opportunity to remove unused functions on the attribute " +"table such as GetRowMin(), GetRowMax() and GetColorOfValue()." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:57 +msgid "Language Bindings:" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:59 +msgid "" +"The Python bindings will be altered so ValuesIO will be supported using " +"numpy arrays for the data with casting of types as appropriate. Strings " +"will be supported using the numpy support for string arrays." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:64 +msgid "Backward Compatibility:" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:66 +msgid "" +"The proposed additions will extend the C API. However, the C++ binary " +"interface will be broken and so GDAL 2.0 is suggested as an appropriate " +"time to introduce the changes." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:70 +msgid "" +"Care will be taken to still support the use of Clone() and Serialize() in" +" derived implementations of the GDALRasterAttributeTable class as these " +"are called by existing code. For implementations where the table is not " +"held in memory these may fail if the table is larger than some suitable " +"limit (for example, GetRowCount() \\* GetColCount() < 1 000 000). Clone()" +" should return a instance of GDALDefaultRasterAttributeTable to prevent " +"problems with sharing memory between objects." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:79 +msgid "" +"Existing code may need to be altered to use create instances of " +"GDALDefaultRasterAttributeTable rather than GDALRasterAttributeTable if " +"an in memory implementation is still required." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:84 +msgid "Impact on Drivers" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:86 +msgid "" +"The HFA driver will be updated to support all aspects of the new " +"interface, such as the new functions and reading/writing upon request. " +"Other drivers will be modified to continue to use the in memory " +"implementation (GDALDefaultRasterAttributeTable)." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:94 +msgid "" +"The Python autotest suite will be extended to test the new API, both for " +"the default implementation and specialised implementation in the HFA " +"driver." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:101 +msgid "" +"We (Sam Gillingham and Pete Bunting) are prepared undertake the work " +"required and have it ready for inclusion in GDAL 1.11 There needs to be a" +" discussion on the names of the methods and on the internal logic of the " +"methods." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:107 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:237 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:347 +msgid "Ticket" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:109 +msgid "Ticket #5129 has been opened to track the progress of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:5 +msgid "RFC 41 : Support for multiple geometry fields in OGR" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:10 +msgid "" +"Add read/write support in the OGR data model for features with multiple " +"geometry fields." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:14 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:30 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:33 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:24 +#: ../../source/development/rfc/rfc72_pytest.rst:26 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:25 +#: ../../source/development/rfc/rfc74_sphinx.rst:23 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:22 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:21 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:21 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:37 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:22 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:23 +#: ../../source/development/rfc/rfc84_cmake.rst:30 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:22 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:28 +#: ../../source/development/rfc/rfc87_signed_int8.rst:22 +#: ../../source/development/rfc/rfc88_googletest.rst:27 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:23 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:31 +#: ../../source/development/rfc/rfc91_dataset_close.rst:26 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:25 +#: ../../source/development/rfc/rfc93_update_feature.rst:22 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:24 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:24 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:27 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:25 +msgid "Motivation" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:16 +msgid "" +"The OGR data model is currently tied to a single geometry field per " +"feature, feature definition and layer. But a number of data formats " +"support multiple geometry fields. The OGC Simple Feature Specifications " +"also do not limit to one geometry field per layer (e.g. §7.1.4 of `OGC " +"06-104r4 \"OpenGIS® Implementation Standard for Geographic information - " +"Simple feature access -Part 2: SQL option " +"`__)." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:24 +msgid "" +"There are workarounds : using geometries of type GEOMETRYCOLLECTION, or " +"advertizing as many layers as there are geometry columns in the layer " +"(like currently done in the PostGIS or SQLite drivers). All those " +"approach are at best workarounds that suffer from limitations :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:29 +msgid "" +"GEOMETRYCOLLECTION approach : no way to know the name/semantics of each " +"sub-geometry. All sub-geometries must be expressed in the same SRS. No " +"way of guaranteeing that the GEOMETRYCOLLECTION has always the same " +"number of sub-geometries or that there are of a consistent geometry type." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:34 +msgid "" +"one layer per geometry column approach : only appropriate for read-only " +"scenarios. Cannot work in write scenarios." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:37 +msgid "" +"The purpose of this RFC is to make support for multiple geometry fields " +"per feature to be properly taken into account in the OGR data model." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:41 +msgid "Proposed solution" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:43 +msgid "" +"(Note: alternative solutions have also been studied. They are explained " +"in a following section of this RFC.)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:46 +msgid "" +"To sum it up, geometry fields will be treated similarly as attribute " +"fields are handled at the OGRFeatureDefn and OGRFeature levels, but they " +"will be kept separate. Attribute fields and geometry fields will have " +"their own separate indexing in the feature definition." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:51 +msgid "" +"This choice has been mainly made to maximize backward compatibility, " +"while offering new capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:54 +msgid "" +"Its involves creating a OGRGeomFieldDefn class, and changes in " +"OGRFieldDefn, OGRFeatureDefn, OGRFeature and OGRLayer classes." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:58 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:206 +msgid "OGRGeomFieldDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:60 +msgid "" +"The OGRGeomFieldDefn is a new class. Its structure is directly inspired " +"from the OGRFieldDefn class." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:92 +msgid "" +"One can notice that the member variables were to be found at OGRLayer " +"level previously." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:95 +msgid "" +"The SRS object is ref-counted. The reference count is increased in the " +"constructor and in SetSpatialRef(), and decreased in the destructor." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:98 +msgid "" +"GetSpatialRef() is deliberately set virtual, so that lazy evaluation can " +"be implemented (getting SRS can have a noticeable cost in some driver " +"implementations, like reading an extra file, or issuing a SQL request)." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:103 +msgid "OGRFeatureDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:105 +msgid "The OGRFeatureDefn class will be extended as the following :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:131 +msgid "" +"At instantiation, OGRFeatureDefn would create a default geometry field " +"definition of name \"\" and type wkbUnknown. If SetGeomType() is called, " +"this will be routed on papoGeomFieldDefn[0]. If only one geometry field " +"definition exists, SetGeomType(wkbNone) will remove it." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:136 +msgid "" +"GetGeomType() will be routed on papoGeomFieldDefn[0] if it exists. " +"Otherwise it will return wkbNone." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:139 +msgid "" +"It is strongly advised that there is name uniqueness among the combined " +"set of regular field names and the geometry field names. Failing to do so" +" will result in unspecified behavior in SQL queries. This advice will not" +" be checked by the code (it is currently not done for regular fields)." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:145 +msgid "" +"Another change is to make all the existing methods of OGRFeatureDefn " +"virtual (and change private visibility to protected), so this class can " +"be subclassed if needed. This will enable lazy creation of the object. " +"Justification: establishing the full feature definition can be costly. " +"But applications may want to list all the layers of a datasource, and " +"only present some information that is important, but cheap to establish. " +"In the past, OGRLayer::GetName() and OGRLayer::GetGeomType() have been " +"introduced in order to workaround for that." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:154 +msgid "" +"Note also that ReorderGeomFieldDefns() is not foreseen for the moment. It" +" could be added in a later step, should the need arises. " +"DeleteGeomFieldDefn() is mostly there for the own benefit of " +"OGRFeatureDefn itself when calling SetGeomType(wkbNone)." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:160 +msgid "OGRFeature class" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:162 +msgid "The OGRFeature class will be extended as following :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:188 +msgid "" +"Note: before RFC41, SetGeometry() or SetGeometryDirectly() could work on " +"a feature whose feature definition had a GetGeomType() == wkbNone (which " +"was inconsistent). This will be no longer the case since the size of the " +"papoGeometries array is now based on GetGeomFieldCount(), and when " +"GetGeomType() == wkbNone, the geometry field count is 0. The VRT and CSV " +"drivers will be fixed to declare their geometry type consistently." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:196 +msgid "OGRLayer class" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:198 +msgid "Impact on OGRLayer class :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:200 +msgid "" +"Spatial filter: the option considered is to only allow one spatial filter" +" at the time." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:203 +msgid "" +"the need for spatial filters applied simultaneously on several geometry " +"fields is not obvious." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:205 +msgid "" +"the m_poFilterGeom protected member is used more than 250 times in the " +"OGR code base, so turning it into an array would be a tedious task..." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:209 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:415 +msgid "Additions:" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:228 +msgid "" +"GetGeomType() : unchanged. For other fields, use " +"GetLayerDefn()->GetGeomField(i)->GetType()" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:231 +msgid "" +"GetSpatialRef(): Currently the default implementation returns NULL. It " +"will be changed to return " +"GetLayerDefn()->GetGeomField(0)->GetSpatialRef() (if there is at least " +"one geometry field). New drivers are encouraged not to specialize " +"GetSpatialRef() anymore, but to appropriately set the SRS of their first " +"geometry field. For other fields, use " +"GetLayerDefn()->GetGeomField(i)->GetSpatialRef()." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:239 +msgid "" +"Caveat: as SRS wasn't previously stored at the OGRFeatureDefn level, all " +"existing drivers, if not updated, will have " +"GetGeomField(0)->GetSpatialRef() returning NULL. The test_ogrsf utility " +"will check and warn about this. Update of existing drivers will be made " +"progressively. In the mean time, using OGRLayer::GetSpatialRef() will be " +"advized to get the SRS of the first geometry field in a reliable way." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:247 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:258 +msgid "add :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:264 +msgid "" +"no DeleteGeomField(), ReorderGeomFields() or AlterGeomFieldDefn() for " +"now. Could be added later if the need arises." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:267 +msgid "" +"GetGeometryColumn() : unchanged. Routed onto the first geometry field. " +"For other fields, use GetLayerDefn()->GetGeomField(i)->GetNameRef()" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:271 +msgid "" +"SetIgnoredFields() : iterate over the geometry fields in addition to " +"regular fields. The special \"OGR_GEOMETRY\" value will only apply to the" +" first geometry field." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:275 +msgid "" +"Intersection(), Union(), etc... : unchanged. Later improvements could use" +" the papszOptions parameter to specify an alternate geometry field" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:278 +msgid "" +"TestCapability(): add a OLCCreateGeomField capability to inform if " +"CreateGeomField() is implemented." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:282 +msgid "OGRDataSource class" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:284 +msgid "Impact on OGRDataSource class :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:286 +msgid "" +"CreateLayer() : signature will be unchanged. If more than one geometry " +"fields are needed, OGRLayer::CreateGeomField() must be used. If the name " +"of the first geometry field must be specified, for datasources supporting" +" ODsCCreateGeomFieldAfterCreateLayer, using code should call " +"CreateLayer() with eGType = wkbNone and then add all geometry fields with" +" OGRLayer::CreateGeomField()." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:293 +msgid "" +"CopyLayer() : adapted to replicate all geometry fields (if supported by " +"target layer)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:296 +msgid "" +"ExecuteSQL() : takes a spatial filter. In the case of the generic OGR SQL" +" implementation, this filter is a facility. It could also as well be " +"applied on the returned layer object. So there is no real need for adding" +" a way of specifying the geometry field at the ExecuteSQL() API level." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:302 +msgid "" +"TestCapability(): add a ODsCCreateGeomFieldAfterCreateLayer capability to" +" inform if CreateGeomField() is implemented after layer creation and that" +" CreateLayer() can be safely called with eGType = wkbNone." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:308 +msgid "Explored alternative solutions" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:310 +msgid "" +"( This paragraph can be skipped if you are totally convinced by the " +"proposed approach detailed above :-) )" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:313 +msgid "" +"A possible alternative solution would have been to extend the existing " +"OGRFieldDefn object with information related to the geometry. That would " +"have involved adding a OFTGeometry value in the OGRFieldType enumeration," +" and adding the OGRwkbGeometryType eGeomType and OGRSpatialReference\\* " +"poSRS members to OGRFieldDefn. At OGRFeature class level, the OGRField " +"union could have been extended with a OGRGeometry\\* field. Similarly at " +"OGRLayer level, CreateField() could have been used to create new geometry" +" fields." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:322 +msgid "" +"The main drawback of this approach, which seems the most natural way, is " +"backward compatibility. This would have affected all places in OGR own " +"code or external code where fields are retrieved and geometry is not " +"expected. For example, in code like the following (very common in the " +"CreateFeature() of most drivers, or in user code consuming features " +"returned by GetNextFeature()) :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:338 +msgid "" +"This would lead, for legacy code, to geometry being handled as regular " +"field. We could imagine that GetFieldAsString() converts the geometry as " +"WKT, but it is doubtfull that this would really be desired. " +"Fundamentally, the handling of attribute and geometry fields is different" +" in most use cases." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:344 +msgid "" +"(On the other side, if we introduce 64bit integer as a OGR type (this is " +"an RFC that is waiting for implementation...), the above code would still" +" produce a meaningful result. The string reprentation of a 64bit integer " +"is not that bad as a default behavior.)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:349 +msgid "" +"GetFieldCount() would also take into account geometry fields, but in most" +" cases, you would need to subtract them." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:352 +msgid "" +"A possible way of avoiding the above compatibility issue would be to have" +" 2 sets of API at OGRFeatureDefn and OGRFeature level. The current one, " +"that would ignore the geometry fields, and an \"extended\" one that would" +" take them into account. For example, OGRFeatureDefn::GetFieldCountEx(), " +"OGRFeatureDefn::GetFieldIndexEx(), OGRFeatureDefn::GetFieldDefnEx(), " +"OGRFeature::GetFieldEx(), OGRFeature::SetFieldAsXXXEx() would take into " +"account both attribute and geometry fields. The annoying thing with that " +"approach is the duplication of the ~ 20 methods GetField() and " +"SetFieldXXX() in OGRFeature." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:366 +msgid "The following functions are added to the C API :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:420 +msgid "OGR SQL engine" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:422 +msgid "" +"Currently, \"SELECT fieldname1[, ...fieldnameN] FROM layername\" returns " +"the specified fields, as well as the associated geometry. This behavior " +"is clearly not following the behavior of spatial RDBMS where the geometry" +" field must be explicitly specified." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:427 +msgid "" +"The following compromise between backward compatibility and the new " +"capabilities of this RFC is adopted :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:430 +msgid "" +"if no geometry field is explicitly specified in the SELECT clause, and " +"there is only one geometry fields associated with the layer, then return " +"it implicitly" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:433 +msgid "" +"otherwise, only return the explicitly mentioned geometry fields (or all " +"geometry fields if \"*\" is used)." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:437 +#: ../../source/development/rfc/rfc45_virtualmem.rst:1113 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:192 +#: ../../source/development/rfc/rfc91_dataset_close.rst:152 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:330 +msgid "Limitations" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:439 +msgid "Geometries from joined layers will not be fetched, as currently." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:440 +msgid "" +"UNION ALL will only handle the default geometry, as currently. (could be " +"extended in later work.)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:442 +msgid "" +"The special fields OGR_GEOMETRY, OGR_GEOM_WKT and OGR_GEOM_AREA will " +"operate on the first geometry field. It does not seem wise to extend this" +" ad-hoc syntax. A better alternative will be the OGR SQLite dialect (with" +" Spatialite support), once it is updated to support multi-geometry (not " +"in the scope of this RFC)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:452 +msgid "Updated drivers in the context of this RFC" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:454 +msgid "PostGIS:" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:456 +msgid "" +"a ad-hoc form of support already exists. Tables with multiple geometries " +"are reported currently as layers called \"table_name(geometry_col_name)\"" +" (as many layers as geometry columns). This behavior will be changed so " +"that the table is reported only once as a OGR layer." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:462 +msgid "PGDump:" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:464 +msgid "add write support for multi-geometry tables." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:466 +msgid "Memory:" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:468 +msgid "updated as a simple illustration of the new capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:470 +msgid "Interlis:" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:472 +msgid "" +"updated to support multiple geometry fields (as well as other changes " +"unrelated to this RFC)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:476 +msgid "Other candidate drivers (upgrade not originally covered by this RFC)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:478 +msgid "" +"GML driver : currently, only one geometry per feature reported. " +"Possibility of changing this by hand-editing of the .gfs file --> " +"implemented post RFC in GDAL 1.11" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:481 +msgid "SQLite driver :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:483 +msgid "currently, same behavior as current PostGIS driver." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:484 +msgid "" +"both the driver and the SQLite dialect could be updated to support multi-" +"geometry layers. --> implemented post RFC in GDAL 2.0" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:487 +msgid "" +"Google Fusion Tables driver : currently, only the first found geometry " +"column used. Possibility of specifying " +"\"table_name(geometry_column_name)\" as the layer name passed to " +"GetLayerByName()." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:491 +msgid "" +"VRT : some thoughts needed to find the syntax to support multiple " +"geometries. Impacted XML syntax : . at OGRVRTLayer element level : " +"GeometryType, LayerSRS, GeomField, SrcRegion, ExtentXMin/YMin/XMax/YMax, " +". at OGRVRTWarpedLayer element level : add new element to select the " +"geometry field . at OGRVRTUnionLayer element level : GeometryType, " +"LayerSRS, ExtentXMin/YMin/XMax/YMax --> implemented post RFC in GDAL 1.11" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:498 +msgid "" +"CSV : currently, take geometries from column named \"WKT\". To be " +"extended to support multiple geometry columns. Not sure worth the effort." +" Could be done with the extended VRT driver. --> implemented post RFC in " +"GDAL 1.11" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:502 +msgid "" +"WFS : currently, only single-geometry layers supported. The standard " +"allows multi-geometry. Would require GML driver support first." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:504 +msgid "Other RDBMS based drivers: MySQL ?, MSSQLSpatial ? Oracle Spatial ?" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:510 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:326 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:609 +msgid "ogrinfo" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:512 +msgid "" +"ogrinfo will be updated to report information related to multi-geometry " +"support. Output is expected to be unchanged w.r.t current output in the " +"case of single-geometry datasource." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:516 +msgid "Expected output for multi-geometry datasource:" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:580 +msgid "" +"A \"-geomfield\" option will be added to specify on which field the -spat" +" option applies." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:584 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:186 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:615 +msgid "ogr2ogr" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:586 +msgid "Enhancements :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:588 +msgid "" +"will translate multi-geometry layers into multi-geometry layers if " +"supported by output layer (OLCCreateGeomField capability). In case it is " +"not supported, only translates the first geometry." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:591 +msgid "" +"\"-select\" option. If only attribute field names are specified, all " +"input geometries will be implicitly selected (backward compatible " +"behavior). If one or several geometry field names are specified, only " +"those ones will be selected." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:595 +msgid "" +"add a \"-geomfield\" option to specify on which field the -spat option " +"applies" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:597 +msgid "" +"the various geometry transformations (reprojection, clipping, etc.) will " +"be applied on all geometry fields." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:601 +msgid "test_ogrsf" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:603 +msgid "Will be enhanced with a few consistency checks :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:605 +msgid "" +"OGRLayer::GetSpatialRef() == " +"OGRFeatureDefn::GetGeomField(0)->GetSpatialRef()" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:607 +msgid "OGRLayer::GetGeomType() == OGRFeatureDefn::GetGeomField(0)->GetGeomType()" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:609 +msgid "" +"OGRLayer::GetGeometryColumn() == " +"OGRFeatureDefn::GetGeomField(0)->GetNameRef()" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:612 +msgid "Spatial filtering tests will loop over all geometry fields." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:617 +msgid "" +"In addition to function level documentation, the new capability will be " +"documented in the :ref:`vector_data_model` and :ref:`vector_api_tut` " +"documents." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:623 +msgid "" +"The new C API will be mapped to SWIG bindings. It will be only tested " +"with the Python bindings. No new typemaps are expected, so this should " +"work with other languages in a straightforward way." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:630 +msgid "" +"Changes are only additions to the existing API, and existing behavior " +"should be preserved, so this will be backwards compatible." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:633 +msgid "C++ ABI changes" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:635 +msgid "" +"Change of behavior in PostGIS driver w.r.t GDAL 1.10 for tables with " +"multiple geometries." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:641 +msgid "" +"Even Rouault will implement the above described changes for GDAL 1.11 " +"release, except the upgrade of the Interlis driver that will be done by " +"Pirmin Kalberer." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:646 +#: ../../source/development/rfc/rfc84_cmake.rst:188 +msgid "Funding" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:648 +msgid "" +"This work is funded by the `Federal Office of Topography (swisstopo), " +"COGIS " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:654 +msgid "+1 from EvenR, FrankW, HowardB, DanielM and TamasS" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:5 +msgid "RFC 42: OGR Layer laundered field lookup" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:7 +msgid "Author: Jürgen Fischer" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:9 +msgid "Contact: jef at norbit dot de" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:14 +msgid "" +"This (mini)RFC proposes a new method in the OGR layer class (and a C API)" +" to lookup the field index of fields, whose names have been altered by " +"drivers (eg. by LAUNDER in OCI or Pg)." +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:21 +msgid "" +"There is already a pull request on github " +"(`https://github.com/OSGeo/gdal/pull/23 " +"`__) that implements this RFC. It " +"adds the virtual method OGRLayer::FindFieldIndex(), that implements the " +"usual mapping, which can be overloaded by drivers. The OCI driver does " +"this to optionally return the index of the LAUNDERed field in case the " +"original field does not exists. The pull request also modifies ogr2ogr to" +" make use of that method and offers a switch -relaxedFieldNameMatch to " +"enable it." +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:31 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:19 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:19 +msgid "Background" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:33 +msgid "" +"This is a particular problem when using NAS as that usually operates on a" +" pre-existing schema. This schema had to be adapted for Oracle as Oracle " +"has a identifier length restrictions that quite a number of identifiers " +"in NAS exceed. Hence ogr2ogr failed to make the mapping between the short" +" names and their long counter parts and leaves those fields empty." +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:43 +msgid "" +"`https://github.com/OSGeo/gdal/pull/23 " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:44 +msgid "" +"PostgreSQL NAS schema: " +"`http://trac.wheregroup.com/PostNAS/browser/trunk/import/alkis_PostNAS_schema.sql" +" " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:46 +msgid "" +"Oracle NAS schema: " +"`http://trac.wheregroup.com/PostNAS/browser/trunk/import/alkis_PostNAS_ORACLE_schema.sql" +" " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:48 +msgid "" +"conversion script from Pg to OCI: " +"`http://trac.wheregroup.com/PostNAS/browser/trunk/import/pg-to-oci.pl " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:54 +msgid "+1 from DanielM, EvenR, FrankW, TamasS, JukkaR and jef" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:57 +msgid "Commits" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:59 +msgid "r26572 & r26573" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:5 +msgid "RFC 43: GDALMajorObject::GetMetadataDomainList" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:14 +msgid "" +"This (mini)RFC proposes a new virtual method, GetMetadataDomainList(), in" +" the GDALMajorObject class (and a C API) to return the list of all " +"available metadata domains." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:21 +msgid "" +"GDALMajorObject currently offers the GetMetadata() and GetMetadataItem() " +"methods that both accept a metadata domain argument. But there is no way " +"to auto-discover which metadata domains are valid for a given " +"GDALMajorObject (i.e. a dataset or raster band). This make it impossible " +"to have generic code that can exhaustively discover all metadata in a " +"dataset/raster band." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:31 +msgid "" +"The base implementation in GDALMajorObject just calls GetDomainList() on " +"the internal oMDMD member." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:57 +msgid "" +"This method is also available in the C API ( char \\*\\* CPL_STDCALL " +"GDALGetMetadataDomainList( GDALMajorObjectH hObject) ) and Swig bindings." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:62 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:314 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:250 +#: ../../source/development/rfc/rfc93_update_feature.rst:152 +msgid "Impacted drivers" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:64 +msgid "" +"Drivers that have custom implementations of GetMetadata() and/or " +"GetMetadataItem() will generally have to also implement " +"GetMetadataDomainList(), when they don't modify the oMDMD member." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:68 +msgid "" +"To make it easy to implement the specialized GetMetadataDomainList(), " +"GDALMajorObject will offer a protected BuildMetadataDomainList() method " +"that can be used like the following :" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:87 +msgid "" +"The TRUE parameter means that the list of domains that follows are " +"potential domains, and thus BuildMetadataDomainList() will check for each" +" one that GetMetadata() returns a non-NULL value." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:91 +msgid "" +"An exhaustive search in GDAL drivers has been made and all drivers that " +"needed to be updated to implement GetMetadataDomainList() have been " +"updated: ADRG, BAG, CEOS2, DIMAP, ECW, ENVISAT, ERS, GeoRaster (cannot " +"check myself that it compiles), GIF, GTiff, HDF4, JPEG, MBTILES, netCDF, " +"NITF, OGDI, PCIDSK, PDF, PNG, PostgisRaster, RasterLite, RS2, VRT, WCS, " +"WebP, WMS." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:98 +msgid "A few caveats :" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:100 +msgid "" +"For MBTiles, WMS and VRT, GetMetadataDomainList(), at the band level, " +"will return \"LocationInfo\" as a valid metadata domain (used by the " +"gdallocationinfo utility), even if GetMetadata(\"LocationInfo\") itself " +"does not return metadata : you have to call " +"GetMetadataItem(\"Pixel_someX_someY\", \"LocationInfo\") or " +"GetMetadataItem(\"GeoPixel_someX_someY\", \"LocationInfo\")." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:106 +msgid "" +"For CEOS2 and ENVISAT, the list of metadata domains cannot be established" +" easily. GetMetadataDomainList() will return the pattern of accepted " +"domain names." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:111 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:319 +msgid "Impacted utilities" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:113 +msgid "The gdalinfo utility is extended to accept :" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:115 +msgid "a \"-listmdd\" option that will print the metadata domains available," +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:139 +msgid "and \"-mdd all\" will display the content of all metadata domains." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:226 +msgid "" +"This change has no impact on backward compatibility at the C API/ABI and " +"C++ API levels. But it impacts C++ ABI, so it requires a full rebuild of " +"all GDAL drivers." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:233 +msgid "" +"The Python autotest suite will be extended to test the new API in a few " +"drivers." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:239 +msgid "Ticket #5275 has been opened to track the progress of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:241 +msgid "" +"The implementation is available in `an attachment to ticket 5275 " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:247 +msgid "+1 from EvenR, DanielM and JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:5 +msgid "RFC 44: Add Parseable Output Formats for ogrinfo and gdalinfo" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:7 +msgid "Authors: Dan \"Ducky\" Little, Faza Mahamood" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:9 +msgid "Contacts: danlittle at yahoo dot com, fazamhd at live dot com" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:11 +msgid "Status: Development. gdalinfo -json implemented in GDAL 2.0" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:16 +msgid "Add XML and JSON output to the ogrinfo and gdalinfo utilities." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:21 +msgid "" +"ogrinfo and gdalinfo are incredibly useful metadata gathering tools. " +"Their native text-based output formats, however, are not easily parseable" +" by common external tools. Both XML and JSON are easily parsed and adding" +" those output formats would substantially increase the utility for those " +"looking to add the ogrinfo and gdalinfo utilities to a scripting stack." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:31 +msgid "" +"An example implementation can be seen at the following github fork " +"`https://github.com/theduckylittle/gdal/blob/trunk/gdal/apps/ogrinfo.cpp " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:34 +msgid "" +"To add the XML output to each utility will require \"breaking up\" the " +"main loop into contingent chunks. All diagnostic messages will also need " +"to be moved to STDERR to ensure that output on STDOUT is always " +"parseable. The XML representation will be constructed using the MiniXML " +"library built into GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:41 +msgid "Proposed json format for gdalinfo" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:316 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:189 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:194 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:199 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:204 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:115 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:147 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:153 +msgid "None." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:321 +msgid "gdalinfo" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:323 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:328 +msgid "Adds a \"-xml\" output option." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:324 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:329 +msgid "Adds a \"-json\" output option." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:334 +msgid "" +"This change has no impact on backward compatibility at the C API/ABI and " +"C++ API/ABI levels. Default output will remain the same. The new XML " +"output will only effect users who specify \"-xml\" or \"-json\" on the " +"command line." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:342 +msgid "" +"The Python autotest suite will be extended to test the new XML/JSON " +"outputs and existing tests will be modified to check STDERR for " +"diagnostic messages." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:349 +msgid "No tickets." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:354 +msgid "Proposed." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:5 +msgid "RFC 45: GDAL datasets and raster bands as virtual memory mappings" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:16 +msgid "" +"This document proposes additions to GDAL so that image data of GDAL " +"datasets and raster bands can be seen as virtual memory mappings, for " +"hopefully simpler usage." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:23 +msgid "" +"When one wants to read or write image data from/into a GDAL dataset or " +"raster band, one must use the RasterIO() interface for the regions of " +"interest that are read or written. For small images, the most convenient " +"solution is usually to read/write the whole image in a single request " +"where the region of interest is the full raster extent. For larger " +"images, particularly when they do not fit entirely in RAM, this is not " +"possible, and if one wants to operate on the whole image, one must use a " +"windowing strategy to avoid memory issues : typically by proceeding " +"scanline (or group of scanlines) by scanline, or by blocks for tiled " +"images. This can make the writing of algorithms more complicated when " +"they need to access a neighbourhood of pixels around each pixel of " +"interest, since the size of this extra window must be taken into account," +" leading to overlapping regions of interests. Nothing that cannot be " +"solved, but that requires some additional thinking that distracts from " +"the followed main purpose." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:39 +msgid "" +"The proposed addition of this RFC is to make the image data appear as a " +"single array accessed with a pointer, without being limited by the size " +"of RAM with respect to the size of the dataset (excepted limitations " +"imposed by the CPU architecture and the operating system)" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:45 +msgid "Technical solution" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:48 +msgid "Low-level machinery : cpl_virtualmem.h" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:50 +msgid "" +"The low-level machinery to support this new capability is a CPLVirtualMem" +" object that represents an area of virtual memory ( on Linux, an area of " +"virtual memory allocated by the mmap() function ). This virtual memory " +"area is initially just reserved in terms of virtual memory space, but has" +" no actual allocation in physical memory. This reserved virtual memory " +"space is protected with an access permission that cause any attempt to " +"access it to result in an exception - a page fault, that on POSIX systems" +" triggers a SIGSEGV signal (segmentation fault). Fortunately, " +"segmentation faults can be caught by the software with a signal handler. " +"When such a segmentation fault occurs, our specialized signal handler " +"will check if it occurs in a virtual memory region under its " +"responsibility and, if so, it will proceed to fill the part (a \"page\") " +"of the virtual memory area that has been accessed with sensible values " +"(thanks to a user provided callback). It will then set appropriate " +"permissions to the page (read-only or read-write), before attempting " +"again the instruction that triggered the segmentation fault. From the " +"point of view of the user code that accesses the memory mapping, this is " +"completely transparent, and this is equivalent as if the whole virtual " +"memory area had been filled from the start." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:70 +msgid "" +"For very large mappings that are larger than RAM, this would still cause " +"disk swapping to occur at a certain point. To avoid that, the " +"segmentation fault handler will evict the least recently used pages, once" +" a threshold defined at the creation of the CPLVirtualMem object has been" +" reached." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:76 +msgid "" +"For write support, another callback can be passed. It will be called " +"before a page is evicted so that user code has a chance to flush its " +"content to a more persistent storage." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:80 +msgid "" +"We also offer an alternative way of creating a CPLVirtualMem object, by " +"using memory file mapping mechanisms. This may be used by \"raw\" " +"datasets (EHdr driver for example) where the organization of data on disk" +" directly matches the organization of a in-memory array." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:86 +msgid "High-level usage" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:88 +msgid "Four new API are introduced (detailed in further section):" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:90 +msgid "" +"GDALDatasetGetVirtualMem() : takes almost the same arguments as " +"GDALDatasetRasterIO(), with the notable exception of a pData buffer. It " +"returns a CPLVirtualMem\\* object, from which the base address of the " +"virtual memory mapping can be obtained with CPLVirtualMemGetAddr()." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:98 +msgid "" +"GDALRasterBandGetVirtualMem(): equivalent of GDALDatasetGetVirtualMem() " +"that operates on a raster band object rather than a dataset object." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:102 +msgid "" +"GDALDatasetGetTiledVirtualMem(): this is a rather original API. Instead " +"of presenting a 2D view of the image data (i.e. organized rows by rows), " +"the mapping exposes it as an array of tiles, which is more suitable, " +"performance wise, when the dataset is itself tiled." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:109 +msgid "" +"When they are several bands, 3 different organizations of band components" +" are possible. To the best of our knowledge, there is no standard way of " +"calling those organizations, which consequently will be best illustrated " +"by the following schemas :" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:-1 +#: ../../source/development/rfc/rfc45_virtualmem.rst:114 +msgid "TIP / Tile Interleaved by Pixel" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:-1 +#: ../../source/development/rfc/rfc45_virtualmem.rst:119 +msgid "BIT / Band Interleaved by Tile" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:-1 +#: ../../source/development/rfc/rfc45_virtualmem.rst:124 +msgid "BSQ / Band SeQuential organization" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:129 +msgid "" +"GDALRasterBandGetTiledVirtualMem(): equivalent of " +"GDALDatasetGetTiledVirtualMem() that operates on a raster band object " +"rather than a dataset object." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:133 +msgid "" +"GDALGetVirtualMemAuto(): simplified version of " +"GDALRasterBandGetVirtualMem() where the user only specifies the access " +"mode. The pixel spacing and line spacing are returned by the function. " +"This is implemented as a virtual method at the GDALRasterBand level, so " +"that drivers have a chance of overriding the base implementation. The " +"base implementation just uses GDALRasterBandGetVirtualMem(). Overridden " +"implementation may use the memory file mapping mechanism instead. Such " +"implementations will be done in the RawRasterBand object and in the " +"GeoTIFF driver." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:144 +msgid "Details of new API" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:149 +msgid "Implemented by cpl_virtualmem.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:503 +msgid "Implemented by gdalvirtualmem.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:972 +msgid "Implemented by gdalrasterband.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1047 +msgid "" +"The CPLVirtualMem low-level machinery is only implemented for Linux now. " +"It assumes that returning from a SIGSEGV handler is possible, which is a " +"blatant violation of POSIX, but in practice it seems that most POSIX (and" +" non POSIX such as Windows) systems should be able to resume execution " +"after a segmentation fault." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1053 +msgid "" +"Porting to other POSIX operating systems such as MacOSX should be doable " +"with moderate effort. Windows has API that offer similar capabilities as " +"POSIX API with VirtualAlloc(), VirtualProtect() and " +"SetUnhandledExceptionFilter(), although the porting would undoubtly " +"require more effort." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1059 +msgid "" +"The existence of `libsigsegv `__ " +"that run on various OS is an evidence on its capacity of being ported to " +"other platforms." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1063 +msgid "" +"The trickiest part is ensuring that things will work reliably when two " +"concurrent threads that try to access the same initially unmapped page. " +"Without special care, one thread could manage to access the page that is " +"being filled by the other thread, before it is completely filled. On " +"Linux this can be easily avoided with the mremap() call. When a page is " +"filled, we don't actually pass the target page to the user callback, but " +"a temporary page. When the callback has finished its job, this temporary " +"page is mremap()'ed to its target location, which is an atomic operation." +" An alternative implementation for POSIX systems that don't have this " +"mremap() call has been tested : any declared threads that can access the " +"memory mapping are paused before the temporary page is memcpy'ed to its " +"target location, and are resumed afterwards. This requires threads to " +"priorly declare their \"interest\" for a memory mapping with " +"CPLVirtualMemDeclareThread(). Pausing a thread is interestingly non-" +"obvious : the solution found to do so is to send it a SIGUSR1 signal and " +"make it wait in a signal handler for this SIGUSR1 signal... It has not " +"been investigated if/how this could be done on Windows. " +"CPLVirtualMemIsAccessThreadSafe() has been introduced for that purpose." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1083 +msgid "" +"As far as CPLVirtualMemFileMapNew() is concerned, memory file mapping on " +"POSIX systems with mmap() should be portable. Windows has " +"CreateFileMapping() and MapViewOfFile() API that have similar " +"capabilities as mmap()." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1089 +msgid "Performance" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1091 +msgid "" +"No miraculous performance gain should be expected from this new " +"capability, when compared to code that carefully uses GDALRasterIO(). " +"Handling segmentation faults has a cost ( the operating system catches a " +"hardware exception, then calls the user program segmentation fault " +"handler, which does the normal GDAL I/O operations, and plays with page " +"mappings and permissions which invalidate some CPU caches, etc... ). " +"However, when a page has been realized, access to it should be really " +"fast, so with appropriate access patterns and cache size, good " +"performance should be expected." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1101 +msgid "" +"It should also be noted that in the current implementation, the " +"realization of pages is done in a serialized way, that is to say if 2 " +"threads which use 2 different memory mappings cause a segmentation fault " +"at the same time, they will not be dealt by 2 different threads, but one " +"after the other one." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1107 +msgid "" +"The overhead of virtual memory objects returned by GetVirtualMemAuto(), " +"when using the memory file mapping, should be lesser than the manual " +"management of page faults. However, GDAL has no control of the strategy " +"used by the operating system to cache pages." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1115 +msgid "" +"The maximum size of the virtual memory space (and thus a virtual memory " +"mapping) depends on the CPU architecture and OS limitations :" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1118 +msgid "on Linux AMD64, 128 TB." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1119 +msgid "on Linux x86, 2 GB." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1120 +msgid "On Windows AMD64 (unsupported by the current implementation), 8 TB." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1121 +msgid "On Windows x86 (unsupported by the current implementation), 2 GB." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1123 +msgid "" +"Clearly, the main interest of this new functionality is for AMD64 " +"platforms." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1126 +msgid "" +"On a Linux AMD64 machine with 4 GB RAM, the Python binding of " +"GDALDatasetGetTiledVirtualMem() has been successfully used to access " +"random points on the new `Europe 3'' DEM dataset " +"`__, which is a 20 GB compressed GeoTIFF ( and 288000 \\* 180000 \\*" +" 4 = 193 GB uncompressed )" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1134 +msgid "Related thoughts" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1136 +msgid "" +"Some issues with system calls such as read() or write(), or easier multi-" +"threading could potentially be solved by making a FUSE (File system in " +"USEr space) driver that would expose a GDAL dataset as a file, and the " +"mmap()'ing the file itself. However FUSE drivers are only available on " +"POSIX OS, and need root privilege to be mounted (a FUSE filesystem does " +"not need root privilege to run, but the mounting operation does)." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1145 +msgid "Open questions" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1147 +msgid "" +"Due to the fact that it currently only works on Linux, should we mark the" +" API as experimental for now ?" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1151 +msgid "Backward compatibility issues" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1153 +msgid "" +"C/C++ API --> compatible (new API). C ABI --> compatible (new API). C++ " +"ABI --> incompatibility because GDALRasterBand has a new virtual method." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1157 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:37 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:56 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:54 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:268 +msgid "Updated drivers" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1159 +msgid "" +"The RawRasterBand object and GeoTIFF drivers will be updated to implement" +" GetVirtualMemAuto() and offer memory file mapping when possible (see " +"above documented restrictions on when this is possible)." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1163 +msgid "" +"In future steps, other drivers such as the VRT driver (for " +"VRTRawRasterBand) could also offer a specialized implementation of " +"GetVirtualMemAuto()." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1170 +msgid "" +"The high level API (dataset and raster band) API is available in Python " +"bindings." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1173 +msgid "" +"GDALDatasetGetVirtualMem() is mapped as Dataset.GetVirtualArray(), which " +"returns a NumPy array." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1192 +msgid "Similarly for GDALDatasetGetTiledVirtualMem() :" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1213 +msgid "And the Band object has the following 3 methods :" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1243 +msgid "" +"Note: dataset/Band.GetVirtualMem()/GetTiledVirtualMem() methods are also " +"available. They return a VirtualMem python object that has a GetAddr() " +"method that returns a Python memoryview object (Python 2.7 or later " +"required). However, using such object does not seem practical for non-" +"Byte data types." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1252 +msgid "" +"The autotest suite will be extended to test the Python API of this RFC. " +"It will also test the specialized implementations of GetVirtualMemAuto() " +"in RawRasterBand and the GeoTIFF drivers. In autotest/cpp, a " +"test_virtualmem.cpp file tests concurrent access to the same pages by 2 " +"threads." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1261 +msgid "" +"Implementation will be done by Even Rouault in GDAL/OGR trunk. The " +"proposed implementation is attached as a `patch " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1268 +msgid "+1 from EvenR, FrankW, DanielM and JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:5 +msgid "RFC 46: GDAL/OGR unification" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:16 +msgid "" +"In the 1.X series of GDAL/OGR, the GDAL/raster and OGR/vector sides are " +"quite different on some aspects even where there is no strong reason for " +"them to be different, particularly in the structure of drivers. This RFC " +"aims at unifying the OGR driver structure with the GDAL driver structure." +" The main advantages of using the GDAL driver structure are :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:22 +msgid "" +"metadata capabilities : description of driver, extensions, creation " +"options, virtual IO capability ..." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:24 +msgid "efficient driver identification and opening." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:26 +msgid "" +"Similarly, OGR datasource and layer classes lack the metadata mechanisms " +"offered by the corresponding GDAL dataset and raster band classes." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:29 +msgid "" +"Another aspect is that the separation between GDAL \"datasets\" and OGR " +"\"datasources\" is sometimes artificial. Various data containers can " +"accept both data types. The list of drivers that have a GDAL side and OGR" +" side is : SDTS, PDS, GRASS, KML, Spatialite/Rasterlite, GeoPackage " +"(raster side not yet implemented), PostGIS/PostGIS Raster, PDF, PCIDSK, " +"FileGDB (raster side not yet implemented). For applications that are " +"interested in both, this currently means to open the file twice with " +"different API. And for update mode, for file-based drivers, the updates " +"must be done sequentially to avoid opening a file twice simultaneously in" +" update mode and making conflicting changes." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:41 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:249 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:158 +msgid "Related RFCs" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:43 +msgid "" +"There are a few related past RFCs that have never been adopted but " +"strongly relate to RFC 46 :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:46 +msgid "" +"`RFC 10: OGR Open Parameters <./rfc10_ogropen>`__. All the functionality " +"described in RFC 10 is included in RFC 46, mainly the GDALOpenEx() new " +"API" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:49 +msgid "" +"`RFC 25: Fast Open <./rfc25_fast_open>`__. RFC 25 mentions avoiding to " +"systematically listing the sibling files to the file being opened. This " +"can now achieved in RFC 46 by lazy loading with " +"GDALOpenInfo::GetSiblingFiles(). At least Identify() should not trigger " +"GetSiblingFiles()." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:54 +msgid "" +"`RFC 36: Allow specification of intended on GDALOpen " +"<./rfc36_open_by_drivername>`__. The new GDALOpenEx() accepts a list of a" +" subset drivers that must be probed, as suggested by RFC36. The " +"specification of the drivers on the command line of utilities could be " +"easily done through a new option, but that's not in the scope of RFC 46." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:60 +msgid "" +"`RFC 38: OGR Faster Open <./rfc38_ogr_faster_open>`__ is completely " +"included in RFC 46 through the possibility of using Open(GDALOpenInfo*) " +"in OGR drivers" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:65 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:162 +msgid "Self-assigned development constraints" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:67 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:164 +msgid "" +"The changes should have moderate impact on the existing GDAL/OGR code " +"base, and particularly on most of its code, that lies in drivers. " +"Existing users of the GDAL/OGR API should also be moderately impacted by " +"the changes, if they do not need to use the new offered capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:73 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:174 +msgid "Core changes: summary" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:75 +msgid "OGRSFDriver extends GDALDriver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:76 +msgid "Vector drivers can be implemented as GDALDriver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:77 +msgid "" +"OGRSFDriverRegistrar is a compatibility wrapper around GDALDriverManager " +"for legacy OGRSFDriver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:79 +msgid "OGRDataSource extends GDALDataSource." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:80 +msgid "GDALOpenEx() API is added to be able to open \"mixed\" datasets." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:81 +msgid "OGRLayer extends GDALMajorObject, thus adding metadata capability." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:82 +msgid "" +"The methods of OGRDataSource related to layers are moved to GDALDataset, " +"making it both a raster and vector capable container." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:84 +msgid "Performance improvements in GDALOpenInfo() mechanism." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:85 +msgid "" +"New driver metadata item to describe open options (i.e. deprecate the use" +" of configuration option)." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:87 +msgid "New driver metadata item to describe layer creation options." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:90 +msgid "Core changes: details" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:93 +msgid "Drivers and driver registration" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:95 +msgid "" +"The OGRSFDriver now extends GDALDriver and is meant as being a legacy way" +" of implementing a vector driver. It is kept mainbly because, in the " +"current implementation, not all drivers have been migrated to being " +"\"pure\" GDALDriver. The CopyDataSource() virtual method has been removed" +" since no in-tree drivers implement it. The inheritance to GDALDriver " +"make it possible to manage vector drivers by the GDALDriverManager, and " +"to be able to attach metadata to them, to document driver long name, link" +" to documentation, file extension, datasource creation options with the " +"existing GDAL\\_DMD\\_\\* metadata items." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:106 +msgid "" +"Drivers directly inheriting from GDALDriver (to be opposed to those " +"inheriting from OGRSFDriver) should : - declare SetMetadataItem( " +"GDAL_DCAP_VECTOR, \"YES\" ). - implement pfnOpen() for dataset opening - " +"optionally, implement pfnCreate() for dataset creation. For vector " +"drivers, the nBands parameter of Create() is supposed to be passed to 0. " +"- optionally, implement pfnDelete() for dataset deletion" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:113 +msgid "" +"The *C* OGR Driver API will still work with drivers that have been " +"converted as \"pure\" GDALDrivers (this is not true of the C++ OGR Driver" +" API). For example OGR_Dr_GetName() calls GDALDriver::GetDescription(), " +"OGR_Dr_CreateDatasource() calls GDALDriver::Create(), etc..." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:119 +msgid "" +"The C++ definition of GDALDriver is extended with the following function " +"pointers so that it can work with legacy OGRSFDriver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:140 +msgid "GDALDriver::Create() can accept nBands == 0 for a vector capable driver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:143 +msgid "" +"GDALDriver::DefaultCreateCopy() can accept a dataset with 0 bands for a " +"vector capable driver, and if the output dataset has layer creation " +"capability and the source dataset has layers, it copies the layers from " +"the source dataset into the target dataset." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:148 +msgid "" +"GDALDriver::Identify() now iterates over all kinds of drivers. It has " +"been modified to do a first pass on drivers that have an implementation " +"of Identify(). If no match is found, it does a second pass on all drivers" +" and use the potentially slower Open() as the identification method." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:154 +msgid "" +"Related to the above point, the implementations of " +"GDALDriver::pfnIdentify function pointer used to return a boolean value " +"to indicate if the passed GDALOpenInfo was a match for the driver. For " +"some drivers, this was too restrictive so that they were able to " +"implement Identify(). For example where the detection logic can return " +"\"yes, I definitely recognize that file\", \"no, it is not for me\" or " +"\"I have not enough elements in GDALOpenInfo to be able to tell\". That " +"last state can now be advertized with a negative return value." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:164 +msgid "" +"The OGRSFDriverRegistrar is trimmed down to be mostly a wrapper around " +"GDALDriverManager. In particular, it does not contain any longer a list " +"of drivers. The Open(), OpenShared(), ReleaseDataSource(), " +"DeregisterDriver() and AutoLoadDrivers() methods are removed from the " +"class. This change can have impact on C++ code. A few adaptations in OGR " +"utilities have been done to accommodate for those changes. The " +"RegisterDriver() API has been kept for legacy OGR drivers and it " +"automatically sets SetMetadataItem( GDAL_DCAP_VECTOR, \"YES\" ). The " +"GetDriverCount(), GetDriver() and GetDriverByName() methods delegate to " +"GDALDriverManager and make sure to only take into account drivers that " +"have the GDAL_DCAP_VECTOR capability. In the case a driver has the same " +"name as GDAL and OGR driver, the OGR variant is internally prefixed with " +"OGR\\_, and GetDriverByName() will first try the OGR\\_ variant. The " +"GetOpenDSCount() and GetOpenDS() have now a dummy implementation " +"returning 0/NULL. For reference, neither MapServer nor QGIS use those " +"functions." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:181 +msgid "" +"OGRRegisterAll() is now an alias of GDALAllRegister(). The past " +"OGRRegisterAll() is now renamed OGRRegisterAllInternal() and called by " +"GDALAllRegister(). So, GDALAllRegister() and OGRRegisterAll() are now " +"equivalent and register all drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:186 +msgid "GDALDriverManager has received a few changes :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:188 +msgid "" +"use of a map from driver name to driver object to speed-up " +"GetDriverByName()" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:190 +msgid "" +"accept OGR_SKIP and OGR_DRIVER_PATH configuration options for backward " +"compatibility." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:192 +msgid "" +"The recommended separator for driver names in GDAL_SKIP is now comma " +"instead of space (similarly to what OGR_SKIP does). This is to make it " +"possible to define OGR driver names in GDAL_SKIP that have spaces in " +"their names like \"ESRI Shapefile\" or \"MapInfo File\". If there is no " +"comma in the GDAL_SKIP value, then space separator is assumed (backward " +"compatibility)." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:198 +msgid "" +"removal of GetHome()/SetHome() methods whose purpose seemed to define an " +"alternate path for the search directory of plugins. Those methods only " +"existed at the C++ level, and are redundant with GDAL_DRIVER_PATH " +"configuration option" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:203 +msgid "" +"Raster-capable drivers should declare SetMetadataItem( GDAL_DCAP_RASTER, " +"\"YES\" ). All in-tree GDAL drivers have been patched to declare it. But " +"the registration code detects if a driver does not declare any of " +"GDAL_DCAP_RASTER nor GDAL_DCAP_VECTOR, in which case it declares " +"GDAL_DCAP_RASTER on behalf of the un-patched driver, with a debug message" +" inviting to explicitly set it." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:210 +msgid "New metadata items :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:212 +msgid "" +"GDAL_DCAP_RASTER=YES / GDAL_DCAP_VECTOR=YES at driver level. To declare " +"that a driver has raster/vector capabilities. A driver can declare both." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:215 +msgid "" +"GDAL_DMD_EXTENSIONS (with a final S) at driver level. This is a small " +"evolution of GDAL_DMD_EXTENSION where one can specify several extensions " +"in the value string. The extensions are space-separated. For example " +"\"shp dbf\", \"tab mif mid\", etc... For ease of use, " +"GDALDriver::SetMetadataItem(GDAL_DMD_EXTENSION) also sets the passed " +"value as GDAL_DMD_EXTENSIONS, if it is not already set. So new code can " +"always use GDAL_DMD_EXTENSIONS." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:222 +msgid "" +"GDAL_DMD_OPENOPTIONLIST at driver level. The value of this item is an XML" +" snippet with a format similar to creation options. GDALOpenEx(), once it" +" has identified with Identify() that a driver accepts the file, will " +"validate the passed open option list with the authorized open option " +"list. Below an example of such an authorized open option list in the S57 " +"driver" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:295 +msgid "Datasets / Datasources" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:297 +msgid "The main methods from OGRDataSource have been moved to GDALDataset :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:376 +msgid "" +"OGRDataSource::SyncToDisk() has been removed. The equivalent " +"functionality should be implemented in existing FlushCache(). " +"GDALDataset::FlushCache() nows does the job of the previous generic " +"implementation of OGRDataSource::SyncToDisk(), i.e. iterate over all " +"layers and call SyncToDisk() on them." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:382 +msgid "GDALDataset has now a protected ICreateLayer() method." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:402 +msgid "" +"GDALOpenEx() is added to be able to open raster-only, vector-only, or " +"raster-vector datasets. It accepts read-only/update mode, shared/non-" +"shared mode. A list of potential candidate drivers can be passed. If " +"NULL, all drivers are probed. A list of open options (NAME=VALUE syntax) " +"can be passed. If the list of sibling files has already been established," +" it can also be passed. Otherwise GDALOpenInfo will establish it." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:457 +msgid "GDALOpenInfo class. The following changes are done :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:459 +msgid "" +"the second argument of the constructor is now nOpenFlags instead of " +"GDALAccess, with same semantics as GDALOpenEx(). GDALOpenInfo uses the " +"read-only/update bit to \"compute\" the eAccess flag that is heavily used" +" in existing drivers. Drivers with both raster and vector capabilities " +"can use the GDAL_OF_VECTOR/GDAL_OF_RASTER bits to determine the intent of" +" the caller. For example if a caller opens with GDAL_OF_RASTER only and " +"the dataset only contains vector data, the driver might decide to not " +"open the dataset (if it is a read-only driver. If it is a driver with " +"update capability, it should do that only if the opening is done in read-" +"only mode)." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:470 +msgid "" +"the open options passed to GDALOpenEx() are stored into a " +"papszOpenOptions member of GDALOpenInfo, so that drivers can use them." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:473 +msgid "" +"the \"FILE\\* fp\" member is transformed into \"VSILFILE\\* fpL\". This " +"change is motivated by the fact that most popular drivers now use the VSI" +" Virtual File API, so they can now directly use the fpL member instead of" +" re-opening again the file. A global pass on all in-tree GDAL drivers " +"that used fp has been made." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:478 +msgid "" +"A VSIStatExL() was done previously to determine the nature of the file " +"passed. Now, we optimistically begin with a VSIFOpenL(), assuming that in" +" most use cases the passed filename is a file. If the opening fails, " +"VSIStatExL() is done to determine the nature of the filename." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:483 +msgid "" +"If the requested access mode is update, the opening of the file with " +"VSIFOpenL() is done with \"rb+\" permissions to be directly usable." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:486 +msgid "" +"The papszSiblingFiles member is now private. It is accessed by a " +"GetSiblingFiles() method that does the ReadDir() on demand. This can " +"speed up the Identify() method that generally does not require to know " +"sibling files." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:490 +msgid "" +"A new method, TryToIngest(), is added to read more than the first 1024 " +"bytes of a file. This is useful for a few vector drivers, like GML or " +"NAS, that must fetch a bit more bytes to be able to identify the file." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:496 +msgid "Layer" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:498 +msgid "" +"OGRLayer extends GDALMajorObject. Drivers can now define layer metadata " +"items that can be retrieved with the usual " +"GetMetadata()/GetMetadateItem() API." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:502 +msgid "" +"The GetInfo() method has been removed. It has never been implemented in " +"any in-tree drivers and has been deprecated for a long time." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:508 +msgid "" +"The deprecated and unused GDALProjDefH and GDALOptionDefinition types " +"have been removed from gdal.h" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:511 +msgid "" +"GDALGeneralCmdLineProcessor() now interprets the nOptions (combination of" +" GDAL_OF_RASTER and GDAL_OF_RASTER) argument as the type of drivers that " +"should be displayed with the --formats option. If set to 0, " +"GDAL_OF_RASTER is assumed." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:516 +msgid "" +"the --formats option of GDAL utilities outputs whether drivers have " +"raster and/or vector capabilities" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:519 +msgid "" +"the --format option of GDAL utilities outputs GDAL_DMD_EXTENSIONS, " +"GDAL_DMD_OPENOPTIONLIST, GDAL_DS_LAYER_CREATIONOPTIONLIST." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:522 +msgid "" +"OGRGeneralCmdLineProcessor() use GDALGeneralCmdLineProcessor() " +"implementation, restricting --formats to vector capable drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:526 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:438 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:96 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:185 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:113 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:87 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:304 +msgid "Changes in drivers" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:528 +msgid "OGR PCIDSK driver has been merged into GDAL PCIDSK driver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:530 +msgid "OGR PDF driver has been merged into GDAL PDF driver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:532 +msgid "" +"A global pass has been made to in-tree OGR drivers that have to open a " +"file to determine if they recognize it. They have been converted to " +"GDALDriver to accept a GDALOpenInfo argument and they now use its " +"pabyHeader field to examine the first bytes of files. The number of " +"system calls realated to file access (open/stat), in order to determine " +"that a file is not recognized by any OGR driver, has now dropped from 46 " +"in GDAL 1.11 to 1. The converted drivers are : AeronavFAA, ArcGEN, " +"AVCBin, AVCE00, BNA, CSV, DGN, EDIGEO, ESRI Shapefile, GeoJSON, GeoRSS, " +"GML, GPKG, GPSBabel, GPX, GTM, HTF, ILI1, ILI2, KML, LIBKML, MapInfo " +"File, MySQL, NAS, NTF, OpenAIR, OSM, PDS, REC, S57, SDTS, SEGUKOOA, SEGY," +" SOSI, SQLite, SUA, SVG, TIGER, VFK, VRT, WFS" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:545 +msgid "Long driver description is set for most OGR drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:547 +msgid "" +"All classes deriving from OGRLayer have been modified to call " +"SetDescription() with the value of GetName()/poFeatureDefn->GetName(). " +"test_ogrsf tests that it is properly set." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:552 +msgid "" +"Following drivers are kept as OGRSFDriver, but their Open() method does " +"early extension/prefix testing to avoid datasource object to be " +"instantiated : CartoDB, CouchDB, DXF, EDIGEO, GeoConcept, GFT, GME, " +"IDRISI, OGDI, PCIDSK, PG, XPlane." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:557 +msgid "" +"Identify() has been implemented for CSV, DGN, DXF, EDIGEO, GeoJSON, GML, " +"KML, LIBKML, MapInfo File, NAS, OpenFileGDB, OSM, S57, Shape, SQLite, " +"VFK, VRT." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:561 +msgid "" +"GDAL_DMD_EXTENSION/GDAL_DMD_EXTENSIONS set for following drivers: AVCE00," +" BNA, CSV, DGN, DWG, DXF, EDIGEO, FileGDB, Geoconcept, GeoJSON, Geomedia," +" GML, GMT, GPKG, GPX, GPSTrackMaker, IDRISI Vector, Interlis 1, Interlis " +"2, KML, LIBKML, MDB, MapInfo File, NAS, ODS, OpenFileGDB, OSM, PGDump, " +"PGeo, REC, S57, ESRI Shapefile, SQLite, SVG, WaSP, XLS, XLSX, XPlane." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:568 +msgid "" +"Document dataset and layer creation options of BNA, DGN, FileGDB, " +"GeoConccept, GeoJSON, GeoRSS, GML, GPKG, KML, LIBKML, PG, PGDump and ESRI" +" Shapefile drivers as GDAL_DMD_CREATIONOPTIONLIST / " +"GDAL_DS_LAYER_CREATIONOPTIONLIST." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:573 +msgid "Add open options AAIGRID, PDF, S57 and ESRI Shapefile drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:575 +msgid "GetFileList() implemented in OpenFileGDB, Shapefile and OGR VRT drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:578 +msgid "" +"Rename datasource SyncToDisk() as FlushCache() for LIBKML, OCI, ODS, XLSX" +" drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:581 +msgid "" +"Use poOpenInfo->fpL to avoid useless file re-opening in GTiff, PNG, JPEG," +" GIF, VRT, NITF, DTED." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:584 +msgid "HTTP driver: declared as GDAL_DCAP_RASTER and GDAL_DCAP_VECTOR driver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:587 +msgid "RIK: implement Identify()" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:589 +msgid "" +"Note: the compilation and good working of the following OGR drivers " +"(mostly proprietary) could not be tested: ArcObjects, DWG, DODS, SDE, " +"FME, GRASS, IDB, OCI, MSSQLSpatial(compilation OK, but not runtime " +"tested)" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:595 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:503 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:112 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:201 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:93 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:413 +msgid "Changes in utilities" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:597 +msgid "gdalinfo accepts a -oo option to define open options" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:598 +msgid "ogrinfo accepts a -oo option to define open options" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:599 +msgid "" +"ogr2ogr accepts a -oo option to define input dataset open options, and " +"-doo to define destination dataset open options" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:603 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:518 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:136 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:211 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:132 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:98 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:191 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:77 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:124 +msgid "Changes in SWIG bindings" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:605 +msgid "Python and Java bindings:" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:607 +msgid "" +"add new GDALDataset methods taken from OGRDataSource : CreateLayer(), " +"CopyLayer(), DeleteLayer(), GetLayerCount(), GetLayerByIndex(), " +"GetLayerByName(), TestCapability(), ExecuteSQL(), ReleaseResultSet(), " +"GetStyleTable() and SetStyleTable()." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:612 +msgid "make OGR Driver, DataSource and Layer objects derive from MajorObject" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:615 +msgid "" +"Perl and CSharp: make sure that it still compiles but some work would " +"have to be done by their mainteners to be able to use the new " +"capabilities" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:620 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:197 +msgid "Potential changes that are *NOT* included in this RFC" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:622 +msgid "\"Natural\" evolutions of current RFC :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:624 +msgid "Unifying the GDAL MEM and OGR Memory drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:625 +msgid "Unifying the GDAL VRT and OGR VRT drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:627 +msgid "Further unification steps :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:629 +msgid "" +"Source tree changes to move OGR drivers from ogr/ogrsf_frmts/ to frmts/ ," +" to move ogr/ogrsf_frmts/generic/\\* to gcore/\\*, etc..." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:631 +msgid "Documentation unification (pages with list of drivers, etc...)" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:632 +msgid "Renaming to remove traces of OGR namespace : OGRLayer -> GDALLayer, etc..." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:634 +msgid "" +"Kill --without-ogr compilation option ? It has been preserved in a " +"working state even if it embeds now ogr/ogrsf_frmts/generic and " +"ogr/ogrsf_frmts/mitab for conveniency." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:637 +msgid "" +"Unification of some utilities : \"gdal info XXX\", \"gdal convert XXX\" " +"that would work on all kind of datasets." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:641 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:551 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:221 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:99 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:471 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:205 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:428 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:150 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:60 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:381 +#: ../../source/development/rfc/rfc87_signed_int8.rst:83 +#: ../../source/development/rfc/rfc88_googletest.rst:218 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:113 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:390 +#: ../../source/development/rfc/rfc91_dataset_close.rst:140 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:151 +#: ../../source/development/rfc/rfc93_update_feature.rst:244 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:151 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:94 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:360 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:276 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:129 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:688 +msgid "Backward compatibility" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:643 +msgid "" +"GDALDriverManager::GetDriverCount(), GetDriver() now returns OGR drivers," +" as well as GDAL drivers" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:646 +msgid "" +"The reference counting in GDAL datasets and GDAL 1.X OGR datasources was " +"a bit different. It starts at 1 for GDAL datasets, and started at 0 for " +"OGR datasources. Now that OGRDataSource is basically a GDALDataset, it " +"starts at 1 for both cases. Hopefully there are very few users of the " +"OGR_DS_GetRefCount() API. If it was deemed necessary we could restore the" +" previous behavior at the C API, but that would not be possible at the " +"C++ level. For reference, neither MapServer nor QGIS use " +"OGR_DS_GetRefCount()." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:658 +msgid "" +"A pass should be made on the documentation to check that all new methods " +"are properly documented. The OGR general documentation (especially C++ " +"API Read/Write tutorial, Driver implementation tutorial and OGR " +"architecture) should be updated to reflect the changes." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:666 +msgid "" +"Very few changes have been made so that the existing autotest suite still" +" passes. Additions have been made to test the GDALOpenEx() API and the " +"methods \"imported\" from OGRDataSource into GDALDataset." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:671 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:235 +msgid "Version numbering" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:673 +msgid "" +"Although the above describes changes should have very few impact on " +"existing applications of the C API, some behavior changes, C++ level " +"changes and the conceptual changes are thought to deserve a 2.0 version " +"number." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:681 +msgid "Implementation will be done by Even Rouault." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:683 +msgid "" +"The proposed implementation lies in the \"unification\" branch of the " +"`https://github.com/rouault/gdal2/tree/unification " +"`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:687 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/unification " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:693 +msgid "+1 from JukkaR, FrankW, DanielM, TamasS and EvenR." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:5 +msgid "" +"RFC 47: Per Dataset Caching and GDALRasterBand Multithreading (not " +"implemented)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:7 +msgid "Author: Blake Thompson" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:9 +msgid "Contact: flippmoke at gmail dot com" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:16 +msgid "" +"When utilizing GDAL in multithread code, it was found that often the " +"limiting portion of the code was often the LRU block cache within GDAL. " +"This is an attempt to make the LRU cache more efficient in multithreaded " +"situations by making it possible to have multiple LRU per dataset and " +"optimizing when locking occurs. Additionally, the changes outlined " +"attempt to find an efficient manner to manage data within the cache." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:23 +msgid "*This change attempts to:*" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:25 +msgid "Make the caching system within raster datasets:" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:27 +msgid "Thread Safe" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:28 +msgid "Provide performance more linearly with an increasing number of threads" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:31 +msgid "Reduce the scope of the current cache locking." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:32 +msgid "Optionally enable a per dataset cache (rather then a global cache)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:33 +msgid "Make Mem datasets READ thread safe per dataset." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:34 +msgid "" +"Lay the ground work for future development to increase thread safety in " +"drivers." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:37 +msgid "*This change does NOT attempt to:*" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:39 +msgid "Make all drivers thread safe" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:40 +msgid "Make datasets thread safe" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:43 +msgid "Two Different Solutions" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:45 +msgid "" +"Two different ways for solving this problem are being proposed and both " +"have been coded up (test code for each still to be written). However, " +"both share some common solutions. First I will go over the common changes" +" for the two different methods, then the ways in which the two solutions " +"differ." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:52 +msgid "Pull Requests" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:54 +msgid "" +"`Pull Request #1 `__ - SOLUTION 1 " +"(Dataset RW Locking)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:56 +msgid "" +"`Pull Request #2 `__ - SOLUTION 2 " +"(Block RW Locking)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:60 +msgid "Common Solution" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:63 +msgid "Dataset Caching" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:65 +msgid "" +"The static global mutex that is limiting performance is located within " +"gcore/gdalrasterblock.cpp. This mutex is there to protect the setting of " +"the maximum cache, the LRU cache itself itself, and the current size of " +"the cache. The current scope of this mutex makes it lock for extended " +"periods once the cache is full, and new memory is being initialized in " +"GDALRasterBlock::Internalize()." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:72 +msgid "" +"In order to remove the need for this LRU cache to be locked more often a " +"new global config option is introducted \"GDAL_DATASET_CACHING\". This " +"causes the LRU cache to be per dataset when set to \"YES\", rather then a" +" global cache (\"NO\" Default). Doing this will also allow threaded " +"applications to flush only the cache for a single dataset, improving " +"performance in some situations for two reasons. First a cache of a more " +"commonly used dataset, might be set separately from other datasets, " +"meaning that it is more likely to remain cached. The second is that the " +"lack of a common global mutex will result in a less likely situation of " +"two threads locking the same mutex if operations are being performed on " +"different datasets." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:84 +msgid "" +"In order to have management of the different caches, a " +"GDALRasterBlockManager class is introduced. This class is responsible for" +" the management of the cache in the global or per dataset situations." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:89 +msgid "GDALRasterBlockManager" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:118 +msgid "" +"Many of the operations originally done by statistics:* within " +"GDALRasterBlock are now moved into the GDALRasterBlockManager." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:124 +msgid "Every GDALDataset now has a:" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:130 +msgid "This is set at initialization of the dataset via:" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:149 +msgid "" +"In order to make caching safer and more efficient, a mutex as also " +"introduced in GDALRasterBand as well. The job of this mutex is to protect" +" the RasterBlock array per band (papoBlocks)." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:154 +msgid "Thread Safety and the Two Solutions" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:156 +msgid "" +"The multithreading of GDAL is a complicated thing, while these changes do" +" seek to *improve* threading within GDAL. It does not *solve* threading " +"problems within GDAL and make it truly thread safe. The goal of this " +"change is simply to make the cache thread safe, in order to achieve this " +"three mutexes are utilized. Where these three mutexes are located is " +"different between the two solutions proposed." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:166 +msgid "Solution 1 (RW Mutex in GDALDataset )" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:169 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:234 +msgid "Mutexes" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:171 +msgid "For solution 1 the three mutexes are:" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:173 +msgid "Dataset RW Mutex (per GDALDataset)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:174 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:238 +msgid "Band Mutex (per GDALRasterBand)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:175 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:240 +msgid "RBM Mutex (per GDALRasterBlockManager)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:177 +msgid "" +"In order to prevent deadlocks, a priority of the mutexes is established " +"in the order they are listed. For example if you have the Band Mutex, you" +" may not obtain the Dataset RW Mutex, unless it was obtained prior to the" +" Band Mutex being obtained. However, the goal should always be to never " +"have more then mutex at a time!" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:184 +msgid "Dataset RW Mutex" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:186 +msgid "" +"The objective of the Dataset RW Mutex is to protect the data stored " +"within the GDALRasterBlocks associated with a dataset, and lock during " +"large Read or Write operations. This prevents two different threads from " +"using memcpy on the same GDALRasterBlock at the same time. This mutex " +"normally lies within the GDALDataset, but in the case of a standalone " +"GDALRasterBand, it utilizes a new mutex on the Band." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:194 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:251 +msgid "Band Mutex" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:196 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:253 +msgid "" +"The objective of the Band Mutex is to manage the control of the array of " +"blocks in the GDALRasterBand, and manages the locking of the " +"GDALRasterBlocks. This is a per GDALRasterBand Mutex." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:201 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:260 +msgid "RBM Mutex" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:203 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:262 +msgid "" +"The objective of the RBM Mutex is to manage control of the LRU cache. " +"This mutex is responsible for the control of the management of the " +"cache's linked list and total amount of data stored in the cache." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:208 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:278 +msgid "Pros" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:210 +msgid "" +"This is a much more simple solution of the two different possible " +"solutions. Since the protection of the Blocks are done at the Dataset " +"level, it prevents the problem of some drivers such as geotiff where more" +" then one band might be accessed in the reading or writing of one band. " +"Therefore with out this protection here it could cause issues if locking " +"was just at a band level per block's data." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:218 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:294 +msgid "Cons" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:220 +msgid "" +"This solution is not perhaps the most optimal way to lock because the " +"protection of the IReadBlock, IWriteBlock, and IRasterIO routines is over" +" the entire dataset. This is very limiting when you are reading the same " +"dataset in a threaded environment, because it is not possible to read " +"more then one block at a time." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:229 +msgid "Solution 2 (RW Mutex in GDALRasterBlock )" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:236 +msgid "For solution 2 the three mutexes are:" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:241 +msgid "Block RW Mutex (per GDALRasterBlock)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:243 +msgid "" +"In order to prevent deadlocks the band mutex has priority. This means " +"that you can not get the Band Mutex if you have the RBM or Blow RW Mutex," +" unless you already had the Band Mutex prior to this. You may not obtain " +"the Block mutex and the RBM mutex at the same time." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:267 +msgid "Block RW Mutex" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:269 +msgid "" +"The objective of the Block RW Mutex is to protect the data stored within " +"the GDALRasterBlocks associated with a dataset, and lock during large " +"Read or Write operations. This prevents two different threads from using " +"memcpy on the same GDALRasterBlock at the same time. It is created on a " +"per block basis." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:280 +msgid "" +"This is probably the most complete solution to making an intensive and " +"fast threaded solution for the blocking. This is because the IReadWrite, " +"IWriteBlock, and IRasterIO now are able to possibly pass a mutex with " +"their calls, as a void pointer pointer. A change was made to the mutex as" +" well such that a void pointer pointer that is NULL passed to " +"CPLMutexHolderD, will not result in any pointer being created or any " +"locking to occur. This means much of the behavior of the existing code " +"can be maintained by simply passing a NULL value for the mutex. All of " +"these changes allow the drivers to maintain much more control over the " +"way that locking occurs when protecting the data inside a block." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:296 +msgid "" +"Obviously, this is a much more complex solution and therefore is harder " +"to manage. It means that writing a driver is not as trivial as before and" +" care must be taken in how locking is done within the driver in order to " +"prevent deadlocks and maintain thread safety. The other issue that might " +"arise from this is a slight slow down in non-threaded code because of the" +" extra cycles spent locking data that will not be accessed in a threaded " +"manner. Additionally, it might have issues in windows if too many mutexes" +" are created (as there are quite a few more since it is a per " +"GDALRasterBlock mutex). (Note: Not sure how I will be able to test this " +"properly?)" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:5 +msgid "RFC 48: Geographical networks support" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:7 +msgid "Author: Mikhail Gusev, Dmitry Baryshnikov" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:9 +msgid "Contact: gusevmihs at gmail dot com, polimax@mail.ru" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:11 +msgid "Status: adopted, implemented in GDAL 2.1" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:14 +msgid "Introduction" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:16 +msgid "" +"This document proposes the integration of the results of GSoC 2014 " +"project “GDAL/OGR Geography Network support” into GDAL library. GNM " +"(Geographical Network Model) intends to bring the capabilities to create," +" manage and analyse networks built over spatial data in GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:21 +msgid "" +"GSoC project description: " +"`http://trac.osgeo.org/gdal/wiki/geography_network_support " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:24 +msgid "" +"GDAL fork with all changes in trunk: `https://github.com/MikhanGusev/gdal" +" `__" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:27 +msgid "" +"GSoC blog: `http://gsoc2014gnm.blogspot.ru/ " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:31 +msgid "Purpose and description" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:33 +msgid "" +"There is a need to have an instrument in GDAL which on the one hand " +"provides an abstraction for different existed network formats (pgRouting," +" OSRM, GraphHopper, SpatiaLite networks, etc.), like GDAL (previously " +"OGR) provides one for spatial vector formats, and on the other hand " +"provides a network functionality to those spatial formats which does not " +"have it at all (Shapefiles)." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:40 +msgid "" +"Such instrument is implemented as a separate set of C++ classes, called " +"GNM. The two main of them represent an abstract network (GNMNetwork " +"class) and the network of ”GDAL-native” or generic format " +"(GNMGenericNetwork class). An abstract network is used by user as a " +"common interface to manage his network data. The list of underlying " +"format-specific classes can be extended anytime like a list of GDAL " +"drivers to support more network formats. The ”GDAL-native” format " +"implements the abstract network and is used to provide the network " +"functionality to the spatial formats which are already supported by GDAL." +" All the network data of this format is stored in the special set of " +"layers along with spatial data in a spatial dataset (internally " +"GDALDataset and OGRLayer are widely used)." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:53 +msgid "What does the interface of working with networks include:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:64 +msgid "" +"See the class architecture document (gdal/gnm/gnm_arch.dox) for more " +"details and how this set of classes internally works." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:68 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:107 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:236 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:262 +#: ../../source/development/rfc/rfc87_signed_int8.rst:75 +#: ../../source/development/rfc/rfc93_update_feature.rst:194 +msgid "Bindings" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:70 +msgid "" +"The C API wrapper functions are declared in gdal/gnm/gnm_api.h. All " +"current python bindings are implemented in a swig interface file and use " +"these C functions." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:75 +msgid "Set of applications" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:77 +msgid "" +"It is proposed to include the two following apps which use the GNM into " +"GDAL source tree:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:85 +msgid "" +"See the description of these applications in according documentation for " +"more details." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:91 +msgid "" +"There is already a pull request on github " +"(`https://github.com/OSGeo/gdal/pull/60 " +"`__) that implements this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:96 +msgid "Building GDAL with GNM support" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:98 +msgid "" +"By default the building of GNM support is disabled. To build GNM support " +"one have to add --with-gnm key to configure or uncomment the appropriate " +"line in nmake.opt." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:103 +msgid "Set of tests" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:105 +msgid "" +"All public methods of GNMNetwork tested in autotest gnm tests. The " +"several tests for GNMGenericNetwork added. The console applications " +"(gnmmanage and gnmanalyse) tested in autotest/utilities." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:109 +msgid "" +"All tests were implemented according to the general rules: they are " +"written on Python and situated in /autotest folder:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:118 +msgid "Documentation structure" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:120 +msgid "" +"All new methods and GNM classes are documented. GDAL documentation is " +"updated when necessary." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:123 +msgid "" +"The following new Doxyfiles in /gnm and /apps directories will be " +"automatically built into the main auto-generated html into the “Related " +"pages” section. All them are similar to OGR docs:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:136 +msgid "Source code tree organization" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:138 +msgid "*What is being added:*" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:140 +msgid "" +"The integration will cause the *addition* of new folders with header, " +"source, make and doc files:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:152 +msgid "*What is being modified:*" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:154 +msgid "The *changing* of the existed GDAL files *will be insignificant*:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:166 +msgid "Future ideas" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:168 +msgid "I see many useful and interesting ways of GNM expending in future:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:170 +msgid "" +"More formats support. The important thing, which must be firstly " +"implemented in future, while the GNM intends to work with as many network" +" formats as possible. It includes not only the support of GNMGdalNetwork " +"formats – i.e. the testing to work with other GDAL spatial formats " +"(currently tested only for Shapefiles and PostGIS). For example:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:177 +msgid "GNMPGRoutingNetwork. Works with pgRouting tables. Some ideas:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:179 +msgid "" +"GNMPGRoutingNetwork::ConnectFeatures() will add to \"source\" and " +"\"target\" columns according values via OGRFeature::setField()" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:181 +msgid "" +"GNMPGRoutingNetwork::AutoConnect() will internally call " +"pgr_createTopology method" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:184 +msgid "" +"GNMSQLiteNetwork. Works with SpatiaLite VirtualNetwork networks. Some " +"ideas:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:187 +msgid "" +"write all network data to the Roads_net_data table and to corresponding " +"NodeFrom and NodeTo columns" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:190 +msgid "GNMGMLNetwork. Works with the GML topology. Some ideas:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:192 +msgid "" +"write network data to the `gml::TopoComplex `__, " +"`gml::Node `__ and `gml::Edge `__ directly" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:197 +msgid "" +"More effective algorithm of topology building in GDAL-networks. The " +"current one is implemented as the default for any network format and can " +"connect any amount of line and point layers but is not so efficient – the" +" large networks are being connected too long. GNMGenericNetwork can have " +"more effective default algorithm." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:203 +msgid "" +"More rules in GDAL-networks, i.e. more complex syntax describing the " +"following:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:206 +msgid "costs extracted from geometrical lengths of lines" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:207 +msgid "turn restriction roles of features" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:208 +msgid "" +"more complex connection rules: set the limit of features can be connected" +" and more complex expressions" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:211 +msgid "" +"Applications. May be one of the most useful application which can be " +"build with GNM is *network2network*, which converts the network and " +"spatial data of the dataset from the one format to another (for example " +"from pgRouting to Oracle Spatial networks);" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:216 +msgid "" +"Analysis. The support of different graph types and the algorithms working" +" with them, for different routing and even engineering purposes. For " +"example:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:220 +msgid "Boost library" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:221 +msgid "Contraction Hierarchies technology (for large graphs)" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:226 +msgid "+1 from JukkaR, TamasS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:5 +msgid "RFC 49: Curve geometries" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:9 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:9 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:9 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:9 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:9 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:9 +msgid "Contact: even dot rouault at spatialys dot com" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:16 +msgid "" +"The current geometry model in GDAL 1.X makes use of points, lines, " +"polygons and aggregations of them (multipoints, multilines, multipolygons" +" and geometry collections). It was modeled from the geometry class " +"hierarchy of the \"OpenGIS Simple Feature Access Part 1 : Common " +"Architecture\" (in its 1.1.0 version)." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:22 +msgid "" +"This RFC covers the addition of new geometry types that have been added " +"in ISO/IEC 13249 Part 3 Spatial (abbreviated as ISO SQL/MM Part 3):" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:25 +msgid "" +"circular string: a circular arc, or a sequence of connected circular " +"arcs, each of them describe by 3 points: the first point of the arc, an " +"intermediate point and the final point" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:28 +msgid "" +"compound curve: a sequence of connected curves, either line strings or " +"circular strings" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:30 +msgid "" +"curve polygon: polygon consisting of one outer ring, and zero or more " +"inner rings. Each ring can be one of the curve implementations: line " +"strings, circular strings, compound curves." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:33 +msgid "" +"multicurve: a collection of curves (line strings, circular strings, " +"compound curves)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:35 +msgid "multisurface: a collection of surfaces (polygons, curve polygons)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:37 +msgid "The scope of this RFC consists in :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:39 +msgid "" +"adding the new geometry classes to the existing geometry class hierarchy," +" with the corresponding importer and exporter of WKT (Well Known Text) " +"and WKB (Well Known Binary) encodings" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:42 +msgid "" +"adding methods to convert those curve geometries into their approximated " +"linear version, and to do the reverse operation" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:44 +msgid "" +"upgrading some of the drivers that can support such geometries : GML (and" +" indirectly NAS, WFS), PostGIS/PGDump, GeoPackage, SQLite, CSV, VRT." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:49 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:36 +msgid "Reference documents" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:51 +msgid "The following documents have been used for the implementation :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:53 +msgid "" +"`Old draft version of ISO/IEC 13249 Part 3 Spatial, dating from " +"2004-05-09 `__, a.k.a SQL/MM Part 3 : Caution the WKB codes given at " +"page 137 and following are not the latest ones used. Refer to SFA 1.2.1" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:58 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:38 +msgid "" +"`OpenGIS Simple Feature Access Part 1 : Common Architecture,v 1.2.1 " +"`__, a.k.a. " +"SFA 1.2.1" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:62 +msgid "" +"`BNF of WKT encoding `__: extracted from SQL/MM Part 3" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:66 +msgid "" +"`BNF of WKB encoding `__: extracted from SQL/MM Part 3" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:71 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:24 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:22 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:24 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:26 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:49 +msgid "Core changes" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:74 +msgid "New cass hierarchy" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:76 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:51 +msgid "" +"The new class hierarchy is the following and is mostly consistent with " +"SQL/MM Part 3" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:81 +msgid "The only exceptions are :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:83 +msgid "" +"OGRLinearRing: this class present in GDAL 1.X is kept for backward " +"compatibility and also because it is still present in SFA 1.2.1, even if " +"absent from SQL/MM Part 3" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:86 +msgid "" +"OGRSimpleCurve: this abstract class is an implementation detail in OGR " +"that simplifies the implementation of OGRCircularString, by sharing code " +"with what was in OGRLineString only." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:91 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:279 +msgid "Geometry types" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:93 +msgid "" +"The OGRwkbGeometryType enumeration has been extended with the following " +"values :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:113 +msgid "" +"The codes have been taken from SFA 1.2.1, and are consistent with the " +"PostGIS 2 implementation. Note that ISO SQL/MM Part 3 allows alternates " +"values for wkbCircularString (8 or 1000001) : see Table 15 in the above " +"mentioned draft. The values in the range 10000XX probably date back from " +"an earlier draft version. OGR will import them, but will use the values " +"from SFA 1.2.1 when exporting WKB." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:120 +msgid "" +"It has been considered if it would worth to modify the enumeration values" +" of the existing 2.5D geometries (wkbPoint25D, etc...) to conform with " +"the WKB codes of ISO SQL/MM Part 3 / SFA 1.2.1, but there was not a clear" +" advantage in doing so, with respect to the impact on existing users of " +"OGR API." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:126 +msgid "" +"Note: the mix of different ways of expression the Z dimension (wkb25DBit " +"bit for \"old\" geometry types, and +1000 for \"new\" geometry types) has" +" no direct impact on the export of geometries as WKB. There is no direct " +"coupling between the values of OGRwkbGeometryType and what goes to WKB " +"geometries. The exportToWkb() method of OGRGeometry takes a wkbVariant " +"parameter to select the variant of WKB that is wished." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:133 +msgid "" +"The use of the wkb25DBit value (0x8000000) that was sometimes used to " +"test if a geometry type was 3D is now clearly deprecated since it will " +"not work for the new geometry type. The wkbHasZ() and wkbSetZ() have been" +" added to respectively test if a geometry type is 3D, or modify a " +"geometry type to be 3D. The wkb25DBit constant is now disabled for all " +"code in GDAL (but still accessible by user code) and all drivers have " +"been converted to use the new macros." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:141 +msgid "A new family of functions have been used to operate on geometry types :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:189 +msgid "" +"The existing wkbFlatten() is an alias of OGR_GT_Flatten(), the new " +"wkbHasZ() an alias of OGR_GT_HasZ() and wkbSetZ() an alias of " +"OGR_GT_SetZ()." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:196 +msgid "In OGRGeometry class :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:261 +msgid "In OGRGeometryFactory class :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:364 +msgid "Implementation of existing OGRGeometry methods" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:366 +msgid "" +"As GEOS does not support curve geometries for now, all GEOS related " +"operations, the ones returning a boolean value such as Intersects(), or " +"the ones returning a new geometry such as Intersection(), have been " +"adapted so that non-linear geometries are first converted to their linear" +" approximation (this might be revisited if GEOS supports curve geometries" +" in the future) When GEOS returns a geometry, and that one of the input " +"parameters was a non-linear geometry, the reverse operation is done to " +"attempt retrieving as much as possible of the curve geometry. Of course, " +"the result will not generally perfect, but it is better than nothing." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:377 +msgid "Simple example doing the union of 2 half-circles that are contiguous:" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:386 +msgid "" +"Or using GetCurveGeometry() explicitly on the result of a buffer " +"operation:" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:396 +msgid "" +"The Length() operation on OGRCircularString (and thus OGRCompoundCurve) " +"uses circle geometry to compute the exact length, without falling back to" +" linear approximation. The Area() operation on OGRCurvePolygon will " +"generally need to go to linear approximation. When operating on a full " +"circle, or a curve polygon that is convex, an optimization is done to " +"avoid this (by computing the area of the polygon formed with all the " +"vertex including in the circular parts of the description, and adding the" +" area of the `circular segments " +"`__)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:407 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:72 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:159 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:99 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:53 +msgid "C API changes" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:409 +msgid "Deprecation:" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:411 +msgid "" +"wkb25DBit still present, but deprecated since incompatible with the new " +"geometry type. Use the wkbFlatten(), wkbHasZ(), wkbSetZ() macros instead" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:417 +msgid "OGR_GT_xxxx (for Geometry Type): described above" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:418 +msgid "" +"OGRErr OGR_G_ExportToIsoWkb( OGRGeometryH, OGRwkbByteOrder, unsigned " +"char*) : Export geometry as WKB conforming to ISO SQL/MM Part 3." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:420 +msgid "" +"OGRErr OGR_G_ExportToIsoWkt( OGRGeometryH, char \\*\\* ) : Export " +"geometry as WKT conforming to ISO SQL/MM Part 3, i.e. 2.5D geometries " +"names are suffixed by \" Z\", e.g. \"POINT Z (1 2 3)\"." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:423 +msgid "" +"OGRGeometryH OGR_G_Value( OGRGeometryH, double dfDistance ) : mapping of " +"existing OGRGeometry::Value()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:425 +msgid "" +"int OGR_G_HasCurveGeometry( OGRGeometryH, int bLookForNonLinear ) : " +"mapping of OGRGeometry::hasCurveGeometry()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:427 +msgid "" +"OGRGeometryH OGR_G_GetLinearGeometry( OGRGeometryH hGeom, double " +"dfMaxAngleStepSizeDegrees, char*\\* papszOptions) : mapping of " +"OGRGeometry::hasCurveGeometry()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:430 +msgid "" +"OGRGeometryH OGR_G_GetCurveGeometry( OGRGeometryH hGeom, char*\\* " +"papszOptions ) : mapping of OGRGeometry::hasCurveGeometry()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:432 +msgid "" +"void OGRSetNonLinearGeometriesEnabledFlag(int bFlag) : discussed in " +"Backward compatibility section" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:434 +msgid "" +"int OGRGetNonLinearGeometriesEnabledFlag() : discussed in Backward " +"compatibility section" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:440 +msgid "" +"GML geometry importer: Arc, ArcString, ArcByBulge, ArcByCenterPoint, " +"Circle and CircleByCenterPoints GML elements will be returned as circular" +" string OGR geometries. If they are included in other GML elements such " +"as CurveComposite, MultiCurve, Surface, corresponding non-linear OGR " +"geometries will be returned as well. When reading geometries that are " +"made of or consist of Surface, MultiSurface, Curve, MultiCurve, an effort" +" is made to return the OGR geometry class of a linear type as much as " +"possible, i.e. OGRCurvePolygon, OGRCompoundCurve, etc... will only be " +"returned if there's a circular string in the geometry." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:451 +msgid "" +"GML geometry exporter: can generate ArcString and Circle GML elements " +"when passed a geometry with circular string in it." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:454 +msgid "" +"GML driver: Can read/write all the new geometry types. When reading GML3 " +"application schemas, declarations of geometry fields such as " +"CurvePropertyType, SurfacePropertyType, MultiCurvePropertyType or " +"MultiSurfacePropertyType will be also interpreted as being potential non-" +"linear geometries, and corresponding OGR geometry type will be used for " +"the layer geometry type, and the geometries of the feature will also " +"follow that layer geometry type. This can affect the WFS drivers." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:463 +msgid "" +"NAS driver: Can return the new geometry types. NAS layers will use the " +"new geometry types only if the NAS file contains arcs." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:466 +msgid "" +"PG/PostGIS: Can read/write all the new geometry types for both PostGIS " +"2.X and PostGIS 1.X. For PostGIS 1.X compatibility, special processing " +"must be done in the importFromWkb()/exportToWkb() to deal with the non " +"standard codes used by PostGIS 1.X for curvepolygon, multicurve and " +"multisurface. This is done with a wkbVariantPostGIS1 value added to " +"OGRwkbVariant enumeration used by those methods." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:473 +msgid "" +"PGDump: Can write all new geometry types. Above remark related to the " +"differences among version make it important to specify correctly the " +"POSTGIS_VERSION dataset creation option." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:477 +msgid "" +"GeoPackage: Can read/write all the new geometry types. Note: this isn't " +"in the core of the GeoPackage specification, but it is still a registered" +" extension." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:481 +msgid "" +"SQLite: Can read/write all the new geometry types for databases that are " +"NOT Spatialite databases, since Spatialite does no support curve geometry" +" types. However an attempt (well a hack) is done so that the SQLite SQL " +"dialect can still be used. Basically when converting a OGR geometry to " +"Spatialite, if it is of one of the curve geometry type, the resulting " +"blob will first contain the spatialite compatible blob of the linear " +"geometry, and afterwards the WKB of the curve geometry. Spatialite " +"functions, if called with a ST\\_ function for example, will ignore the " +"later one. When reading a blob from sqlite, if the added WKB of the curve" +" geometry is still there, it will be used. Otherwise the spatialite " +"geometry blob will be used. So SELECT statement just selecting the " +"geometry column without doing any operation on it should preserve curve " +"geometries." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:495 +msgid "MEM: Can read/write all the new geometry types." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:497 +msgid "CSV: Can read/write all the new geometry types." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:499 +msgid "" +"VRT: Declared as compatible with all the new geometry types. Actual " +"capability will depend on the underlying layers wrapped by the VRT." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:505 +msgid "" +"ogr2ogr: the new geometry names (CIRCULARSTRING, etc...) are supported in" +" the -nlt option. \"-nlt CONVERT_TO_LINEAR\" can also be used to ask " +"curve geometries to be converted into their linear approximation ( what " +"is used to do that is forceTo(xxx, OGR_GT_GetLinear()) ). Note: this " +"isn't strictly necessary as all drivers should be able to deal with the " +"non-linear geometry types with the compatibility mechanism described in " +"Backward compatibility. But this might be useful to produce a PostGIS " +"table or GeoPackage database with linear geometry types even if the " +"source contains non-linear geometries. \"-nlt CONVERT_TO_LINEAR\" can be " +"combined with \"-nlt PROMOTE_TO_MULTI\"." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:520 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:138 +msgid "Addition of :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:522 +msgid "the new geometry types as ogr.wkbXXXXX" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:523 +msgid "ogr.ForceTo()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:524 +msgid "Geometry.ExportToIsoWkt()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:525 +msgid "Geometry.ExportToIsoWkb()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:526 +msgid "Geometry.HasCurveGeometry(int bLookForCircular = FALSE)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:527 +msgid "" +"Geometry.GetLinearGeometry(double dfMaxAngleStepSizeDegrees = " +"0.0,char*\\* options = NULL)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:529 +msgid "Geometry.GetCurveGeometry(char*\\* options = NULL)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:530 +msgid "ogr.SetNonLinearGeometriesEnabledFlag(int bFlag)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:531 +msgid "ogr.GetNonLinearGeometriesEnabledFlag()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:532 +msgid "ogr.GT_xxxxx functions" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:534 +msgid "Using ogr.wkb25DBit will issue a deprecation warning" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:537 +msgid "Related changes that are *NOT* included in this RFC" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:539 +msgid "" +"Support for other ISO SQL/MM geometries such as Polyhedral Surface, " +"Triangulated Irregular Network (TIN), Triangle." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:541 +msgid "Support for the M (Measure) dimension of geometries." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:542 +msgid "" +"Upgrade of other drivers that could make use of curve geometries : MSSQL " +"Spatial, Oracle Spatial, DXF, DWG, ..." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:544 +msgid "" +"Support for arbitrary new geometry types: Conceptually one could hope " +"that a new class extending OGRCurve (Bezier or Spline curve) for example " +"could be added without touching OGR core. This isn't currently possible: " +"changes in OGRGeometryFactory and the OGR_GT\\_ functions would be needed" +" to remove a few hardcoded assumptions." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:554 +msgid "Regarding code using GDAL" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:556 +msgid "" +"Many applications will not be able to properly deal with the new geometry" +" types that may now be returned by some drivers. If they don't want to " +"test the geometry type and explicitly calling the conversion function, " +"they can call OGRSetNonLinearGeometriesEnabledFlag(FALSE) (the default " +"value is TRUE, i.e. non-linear geometries can be returned). In which " +"case, they will be transformed into their closest linear geometry, by " +"doing linear approximation, with OGR_G_ForceTo()." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:564 +msgid "" +"This flag has only an effect on the OGR_F_GetGeometryRef(), " +"OGR_F_GetGeomFieldRef(), OGR_L_GetGeomType(), OGR_GFld_GetType() and " +"OGR_FD_GetGeomType() C API, and corresponding methods in the SWIG " +"bindings." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:569 +msgid "" +"Libraries should generally *not* use that method, since that could " +"interfere with other libraries or applications." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:572 +msgid "" +"Note that it does *not* affect the behavior of the C++ API. It has been " +"deemed dangerous/complicated to try doing that at the C++ level as it " +"could confuse drivers since they might call GetGeomType() for example." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:577 +msgid "Regarding OGR drivers" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:579 +msgid "" +"Drivers that can deal with the new geometry types SHOULD declare the new " +"dataset level ODsCCurveGeometries AND layer level OLCCurveGeometries " +"capabilities. The virtual methods CreateFeature() and SetFeature() " +"implemented by drivers have been renamed ICreateFeature() and " +"ISetFeature(). OGRLayer has now a non-virtual CreateFeature() and " +"SetFeature() that checks if the layer has curve geometry capability. If " +"it has not, and that the passed feature has non-linear geometries, they " +"will be transparently converted to their linear approximation before " +"calling the driver ICreateFeature()/ISetFeature() method. Similarly the " +"CreateLayer() method at datasource level will convert the passed geometry" +" type to a non-linear corresponding type if necessary." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:591 +msgid "" +"All in-tree drivers have been converted to switch from CreateFeature() to" +" ICreateFeature() and SetFeature() to ISetFeature(). Out-of-tree drivers " +"will have to be adapted similarly otherwise those methods will fails (the" +" now non-virtual methods in OGRLayer class will try to create the default" +" implementation of the same class, which will fail)." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:600 +msgid "" +"All new methods and OGR geometry classes are documented. Driver " +"documentation is updated when necessary. MIGRATION_GUIDE.TXT is updated " +"with a summary of the text of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:607 +msgid "" +"Very few changes have been made so that the existing autotest suite still" +" passes. Very comprehensive testing of new geometry classes and " +"conversion methods has been added to ogr_geom.py and ogr_gml_geom.py. " +"Updated drivers have received new tests also." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:615 +msgid "" +"Implementation will be done by Even Rouault. Coordinated with Sourcepole " +"(see `QGIS Enhancement 8: Geometry redesign `__)," +" sponsored by Swiss QGIS User Group." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:620 +msgid "" +"The proposed implementation lies in the \"curve_geometries\" branch of " +"the `https://github.com/rouault/gdal2/tree/curve_geometries " +"`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:624 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/curve_geometries " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:630 +msgid "+1 from TamasS, JukkaR and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:5 +msgid "RFC 4: Geolocation Arrays" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:16 +msgid "" +"It is proposed that GDAL support an additional mechanism for geolocation " +"of imagery based on large arrays of points associating pixels and lines " +"with geolocation coordinates. These arrays would be represented as raster" +" bands themselves." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:21 +msgid "" +"It is common in AVHRR, Envisat, HDF and netCDF data products to " +"distribute geolocation for raw or projected data in this manner, and " +"current approaches to representing this as very large numbers of GCPs, or" +" greatly subsampling the geolocation information to provide more " +"reasonable numbers of GCPs are inadequate for many applications." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:28 +msgid "Geolocation Domain Metadata" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:30 +msgid "" +"Datasets with geolocation information will include the following dataset " +"level metadata items in the \"GEOLOCATION\" domain to identify the " +"geolocation arrays, and the details of the coordinate system and " +"relationship back to the original pixels and lines." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:35 +msgid "SRS: wkt encoding of spatial reference system." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:36 +msgid "X_DATASET: dataset name (defaults to same dataset if not specified)" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:37 +msgid "X_BAND: band number within X_DATASET." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:38 +msgid "Y_DATASET: dataset name (defaults to same dataset if not specified)" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:39 +msgid "Y_BAND: band number within Y_DATASET." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:40 +msgid "Z_DATASET: dataset name (defaults to same dataset if not specified)" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:41 +msgid "Z_BAND: band number within Z_DATASET. (optional)" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:42 +msgid "PIXEL_OFFSET: pixel offset into geo-located data of left geolocation pixel" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:44 +msgid "LINE_OFFSET: line offset into geo-located data of top geolocation pixel" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:46 +msgid "PIXEL_STEP: each geolocation pixel represents this many geolocated pixels." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:48 +msgid "LINE_STEP: each geolocation pixel represents this many geolocated lines." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:50 +msgid "" +"GEOREFERENCING_CONVENTION: (added in GDAL 3.5) either TOP_LEFT_CORNER to " +"indicate that the X/Y values refer to the top-left corner of the pixel, " +"or PIXEL_CENTER to indicate that they refer to the center of the pixel. " +"The default is TOP_LEFT_CORNER." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:55 +msgid "" +"In the common case where two of the bands of a dataset are actually " +"latitude and longitude, and so the geolocation arrays are the same size " +"as the base image, the metadata might look like:" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:69 +msgid "" +"For AVHRR datasets, there are only 11 points (note, the more recent NOAA " +"AVHRR datasets have 51 points), but for every line. So the result for a " +"LAC dataset might look like:" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:85 +msgid "" +"This assumes the L1B driver is modified to support the special access to " +"GCPs as bands using the L1BGCPS: prefix." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:89 +msgid "Updating Drivers" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:91 +msgid "" +"HDF4: Client needs mandate immediate incorporation of geolocation array " +"support in the HDF4 driver (specifically for swath products). (complete)" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:94 +msgid "" +"HDF5: Some HDF5 products include geolocation information that should be " +"handled as arrays. No timetable for update." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:96 +msgid "" +"AVHRR: Has 11/51 known locations per-scanline. These are currently " +"substantially downsampled and returned as GCPs, but this format would be " +"an excellent candidate for treating as geolocation arrays. Planned in " +"near future." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:100 +msgid "" +"Envisat: Envisat raw products use geolocation information currently " +"subsampled as GCPs, good candidate for upgrade. No timetable for update." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:103 +msgid "" +"netCDF: NetCDF files can have differently varying maps in x and y " +"directions, which are represented as geolocation arrays when they are " +"encoded as CF conventions \"two-dimensional coordinate variables\". See " +"the netcdf driver page for details." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:107 +msgid "" +"OPeNDAP: Can have differently varying maps in x and y directions which " +"could be represented as geolocation arrays when they are irregular. No " +"timetable for update." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:112 +msgid "Changes to Warp API and gdalwarp" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:114 +msgid "" +"Introduce a new geolocation array based transformation method, following " +"the existing GDALTransformer mechanism. A geolocation array transformer " +"will be created with the following function call. The \"char \\**\" array" +" is the list of metadata from the GEOLOCATION metadata domain." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:125 +msgid "" +"This transformer is currently partially implemented, but in a manner that" +" potentially uses a great deal of memory (twice the memory needed for the" +" geolocation arrays), and with still dubious correctness, but once " +"approved this will be fixup up to at least be correct, though likely not " +"efficient for the time being." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:131 +msgid "" +"The GDALGenImgProjTransformer will be upgraded to instantiate the GeoLoc " +"transformer (instead of an affine, gcp, or rpc transformer) if only " +"geolocation information is available (done). However, the current " +"GDALCreateGenImgProjTransformer() function does not provide a mechanism " +"to select which transformation mechanism is used. So, for instance, if an" +" affine transform is available it will be used in preference to " +"geolocation data. If bGCPUseOK is TRUE, gcps will be used in preference " +"to geolocation data." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:140 +msgid "" +"The gdalwarp program currently always sets bGCPUseOK to TRUE so there is " +"no means for gdalwarp users select use of geolocation data in preference " +"to gcps. Some modification to gdalwarp may be needed in the future in " +"this regard." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:150 +msgid "" +"''How do we preserve access to geolocation information when translating a" +" dataset? Do applications like gdal_translate need special handling?" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:152 +msgid "" +"Placement of the geolocation data in a special metadata domain means it " +"won't be transferred in default translations.''" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:5 +msgid "RFC 50: OGR field subtypes" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:16 +msgid "" +"This RFC aims at adding the capability of specifying sub-types to OGR " +"fields, like boolean, 16 bit integers or 32 bit floating point values. " +"The sub-type of a field definition is an additional attribute that " +"specifies a hint or a restriction to the main type. The subtype can be " +"used by applications and drivers that know how to handle it, and can " +"generally be safely ignored by applications and drivers that do not." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:27 +msgid "Field subtypes" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:29 +msgid "The OGRFieldSubType enumeration is added :" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:55 +msgid "New attributes and methods" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:57 +msgid "In OGRFieldDefn class :" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:67 +msgid "" +"OGRFeature::SetField() will check that the passed value is in the " +"accepted range for boolean and int16 subtypes. If not, it will emit a " +"warning and correct/clamp the value to fit the subtype." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:74 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:161 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:101 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:55 +msgid "Only additions :" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:85 +msgid "Changes in OGR SQL" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:87 +msgid "" +"Subtypes are preserved when a field name (or \\*) is specified in the " +"list of fields of a SELECT" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:89 +msgid "CAST(xxx AS BOOLEAN) and CAST(xxx AS SMALLINT) are now supported." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:90 +msgid "" +"The field list of a SELECT can now accept boolean expressions, such as " +"\"SELECT x IS NULL, x >= 5 FROM foo\"" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:92 +msgid "" +"The WHERE clause of a SELECT can now accept boolean fields, such as " +"\"SELECT \\* FROM foo WHERE a_boolean_field\"" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:98 +msgid "GeoJSON: can read/write OFSTBoolean" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:99 +msgid "GML: can read/write OFSTBoolean, OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:100 +msgid "" +"CSV: can read/write OFSTBoolean (explicitly with CSVT or with " +"autodetection), OFSTInt16 and OFSTFloat32 (explicitly with CSVT)" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:102 +msgid "PG: can read/write OFSTBoolean, OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:103 +msgid "PGDump: can write OFSTBoolean, OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:104 +msgid "GeoPackage: can read/write OFSTBoolean, OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:105 +msgid "SQLite: can read/write OFSTBoolean and OFSTInt16" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:106 +msgid "SQLite dialect: can read/write OFSTBoolean, OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:107 +msgid "FileGDB: can read/write OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:108 +msgid "OpenFileGDB: can read OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:109 +msgid "VRT: 'subtype' property added to be able to handle any subtype." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:114 +msgid "" +"ogrinfo: the output of ogrinfo is slightly modified in presence of a " +"subtype. A field with a non-default subtype will be described as " +"\"field_type(field_subtype)\". For example" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:140 +msgid "ogr.OFSTNone, ogr.OFSTBoolean, ogr.OFSTInt16 and ogr.OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:141 +msgid "ogr.GetFieldSubTypeName()" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:142 +msgid "FieldDefn.GetSubType()" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:143 +msgid "FieldDefn.SetSubType()" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:148 +msgid "" +"This should have no impact on read-only operations done by applications. " +"Update operations could be impacted if an out-of-range value for the " +"subtype is written (but such a behavior probably already caused issues, " +"either ignored or notified by the backend)" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:156 +msgid "" +"All new methods are documented. Driver documentation is updated when " +"necessary." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:162 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:161 +msgid "The various aspects of this RFC are tested:" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:164 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:163 +msgid "core changes" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:165 +msgid "OGR SQL changes" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:166 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:164 +msgid "driver changes" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:171 +msgid "" +"Implementation will be done by Even Rouault (`Spatialys " +"`__), and sponsored by `CartoDB " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:175 +msgid "" +"The proposed implementation lies in the \"ogr_field_subtype\" branch of " +"the `https://github.com/rouault/gdal2/tree/ogr_field_subtype " +"`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:180 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/ogr_field_subtype " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:186 +msgid "+1 JukkaR, TamasS, FrankW and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:5 +msgid "RFC 51: RasterIO() improvements : resampling and progress callback" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:16 +msgid "" +"This RFC aims at extending the RasterIO() API to allow specifying a " +"resampling algorithm when doing requests involving subsampling or " +"oversampling. A progress callback can also be specified to be notified of" +" progression and allow the user to interrupt the operation." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:25 +msgid "Addition of GDALRasterIOExtraArg structure" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:27 +msgid "A new structure GDALRasterIOExtraArg is added to contain the new options." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:75 +msgid "" +"There are several reasons to prefer a structure rather than new " +"parameters to the RasterIO() methods :" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:78 +msgid "code readability (GDALDataset::IRasterIO() has already 14 parameters...)" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:80 +msgid "allow future extensions without changing the prototype in all drivers" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:81 +msgid "" +"to a lesser extent, efficiency: it is common for RasterIO() calls to be " +"chained between generic/specific and/or dataset/rasterband " +"implementations. Passing just the pointer is more efficient." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:85 +msgid "" +"The structure is versioned. In the future if further options are added, " +"the new members will be added at the end of the structure and the version" +" number will be incremented. Code in GDAL core&drivers can check the " +"version number to determine which options are available." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:91 +msgid "Addition of GDALRIOResampleAlg structure" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:93 +msgid "The following resampling algorithms are available :" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:113 +msgid "" +"Those new resampling methods can be used by the " +"GDALRasterBand::IRasterIO() default implementation when the size of the " +"buffer (nBufXSize x nBufYSize) is different from the size of the area of " +"interest (nXSize x nYSize). The code heavily relies on the algorithms " +"used for overview computation, with adjustments to be also able to deal " +"with oversampling. Bilinear, CubicSpline and Lanczos are now available in" +" overview computation as well, and rely on the generic infrastructure for" +" convolution computation introduced lately for improved cubic overviews. " +"Some algorithms are not available on raster bands with color palette. A " +"warning will be emitted if an attempt of doing so is done, and nearest " +"neighbour will be used as a fallback." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:125 +msgid "" +"The GDAL_RASTERIO_RESAMPLING configuration option can be set as an " +"alternate way of specifying the resampling algorithm. Mainly useful for " +"tests with applications that do not yet use the new API." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:129 +msgid "" +"Currently, the new resampling methods are only available for GF_Read " +"operations. The use case for GF_Write operations isn't obvious, but could" +" be added without API changes if needed." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:134 +msgid "C++ changes" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:136 +msgid "" +"GDALDataset and GDALRasterBand (non virtual) RasterIO() and (virtual) " +"IRasterIO() methods have a new final argument psExtraArg of type " +"GDALRasterIOExtraArg*. This extra argument defaults to NULL for code " +"using GDAL, but is required for all in-tree code, so as to avoid that in-" +"tree code forgets to forwards psExtraArg it might have returned from a " +"caller." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:143 +msgid "" +"GDALDataset::RasterIO() and GDALRasterBand::RasterIO() can accept a NULL " +"pointer for that argument in which case they will instantiate a default " +"GDALRasterIOExtraArg structure to be passed to IRasterIO(). Any other " +"code that calls IRasterIO() directly (a few IReadBlock() implementations)" +" should make sure of doing so, so that IRasterIO() can assume that its " +"psExtraArg is not NULL." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:150 +msgid "" +"As a provision to be able to deal with very large requests with buffers " +"larger than several gigabytes, the nPixelSpace, nLineSpace and nBandSpace" +" parameters have been promoted from the int datatype to the new GSpacing " +"datatype, which is an alias of a signed 64 bit integer." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:155 +msgid "" +"GDALRasterBand::IRasterIO() and GDALDataset::BlockBasedRasterIO() now use" +" the progress callback when available." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:180 +msgid "" +"Those are the same as the existing functions with a final " +"GDALRasterIOExtraArg\\* psExtraArg argument, and the spacing parameters " +"promoted to GSpacing." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:187 +msgid "" +"All in-tree drivers that implemented or used RasterIO have been edited to" +" accept the GDALRasterIOExtraArg\\* psExtraArg parameter, and forward it " +"when needed. Those who had a custom RasterIO() implementation now use the" +" progress callback when available." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:191 +msgid "" +"VRT: the and elements can accept a 'resampling' attribute. The VRT driver" +" will also set the dfXOff, dfYOff, dfXSize and dfYSize fields of " +"GDALRasterIOExtraArg\\* to have source sub-pixel accuracy, so that " +"GDALRasterBand::IRasterIO() leads to consistent results when operating on" +" a small area of interest or the whole raster. If that was not done, " +"chunking done in GDALDatasetCopyWholeRaster() or other algorithms could " +"lead to repeated lines due to integer rounding issues." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:203 +msgid "" +"gdal_translate: accept a -r parameter to specify the resampling " +"algorithm. Defaults to NEAR. Can be set to bilinear, cubic, cubicspline, " +"lanczos, average or mode. (Under the hood, this sets the new resampling " +"property at the VRT source level.)" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:207 +msgid "" +"gdaladdo: -r parameter now accepts bilinear, cubicspline and lanczos as " +"additional algorithms to the existing ones." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:213 +msgid "" +"For Python and Perl bindings: Band.ReadRaster(), Dataset.ReadRaster() now" +" accept optional resample_alg, callback and callback_data arguments. " +"(untested for Perl, but the existing tests pass)" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:216 +msgid "" +"For Python bindings, Band.ReadAsArray() and Dataset.ReadAsArray() now " +"accept optional resample_alg, callback and callback_data arguments." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:222 +msgid "C API/ABI preserved." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:224 +msgid "" +"C++ users of the GDALRasterBand::RasterIO() and GDALDataset::RasterIO() " +"API do not need to change their code, since the new " +"GDALRasterIOExtraArg\\* psExtraArg argument is optional for out-of-tree " +"code." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:229 +msgid "" +"Out-of-tree drivers that implement IRasterIO() must be changed to accept " +"the new GDALRasterIOExtraArg\\* psExtraArg argument. Note: failing to do " +"so will be undetected at compile time (due to how C++ virtual method " +"overloading work)." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:234 +msgid "Both issues will be mentioned in MIGRATION_GUIDE.TXT" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:239 +msgid "All new methods are documented." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:244 +msgid "The various aspects of this RFC are tested in the Python bindings:" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:246 +msgid "" +"use of the new options of Band.ReadRaster(), Dataset.ReadRaster(), " +"Band.ReadAsArray() and Dataset.ReadAsArray()." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:248 +msgid "resampling algorithms in subsampling and oversampling RasterIO() requests." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:250 +msgid "\"-r\" option of gdal_translate" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:255 +msgid "" +"Implementation will be done by Even Rouault (`Spatialys " +"`__), and sponsored by `R3 GIS " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:259 +msgid "" +"The proposed implementation lies in the \"rasterio\" branch of the " +"`https://github.com/rouault/gdal2/tree/rasterio " +"`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:263 +msgid "" +"The list of changes : `https://github.com/rouault/gdal2/compare/rasterio " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:269 +msgid "+1 from FrankW, JukkaR, HowardB, DanielM, TamasS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:5 +msgid "RFC 52: Strict OGR SQL quoting" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:11 +msgid "Status: adopted, implemented in GDAL 2.0" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:16 +msgid "" +"This RFC proposes that OGR SQL enforces strict quoting rules for SQL " +"literals and identifiers" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:22 +msgid "" +"Currently the OGR SQL engine deals indifferently with single quote " +"characters (') and double quote characters (\"), although they can be " +"used in 2 different contexts :" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:26 +msgid "to specify string literals" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:27 +msgid "to specify column or table names (when they need quoting)" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:29 +msgid "" +"SQL 92 mandates that string literals are surrounded with single quote " +"characters whereas quoted identifiers (column, table names) are " +"surrounded with double quote characters." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:33 +msgid "" +"From `http://savage.net.au/SQL/sql-92.bnf.html " +"`__:" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:41 +msgid "" +"Current OGR behavior is generally fine, except in some situations when " +"specifying columns in a SELECT statement or in a WHERE expression. The " +"OGR SQL engine tries to determine the intent with the following rule : if" +" the quoted string matches a column name, then it is assumed to be a " +"column identifier, otherwise a string literal. But sometimes (see " +"`http://trac.osgeo.org/gdal/ticket/5428 " +"`__), there are situations where " +"filters such as \"MyField\" = 'MYFIELD' are needed, and currently they " +"always evaluate to TRUE." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:50 +msgid "" +"To avoid any ambiguities and more conformant to SQL, string literals " +"should be single-quoted, and identifiers (column/table names) unquoted or" +" surrounded by double-quote character if conflicting with reserved " +"keywords." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:58 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:169 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:135 +msgid "" +"Implementation will be done by Even Rouault (`Spatialys " +"`__)." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:61 +msgid "" +"The proposed implementation lies in the \"rfc52_stricter_sql\" branch of " +"the `https://github.com/rouault/gdal2/tree/rfc52_stricter_sql " +"`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:66 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/rfc52_stricter_sql " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:72 +msgid "" +"This change affects compatibility in the sense that users that relied on " +"the current permissive behavior will have to adapt their SQL expressions." +" This might be quite tricky to detect as it will not always cause obvious" +" runtime failures. For example \" SELECT " +"'i_thought_this_would_be_interpreted_as_a_column_name_but_now_it_is_a_string_litteral'" +" FROM atable \" will run without error but not produce the previously " +"expected result. So applications will have to review how they build SQL " +"filters ( SetAttributeFilter() ) and expressions ( ExecuteSQL() )" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:81 +msgid "" +"Expressions fixed to be compliant with stricter rules will also work with" +" older GDAL versions." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:84 +msgid "" +"A prominent warning should also be put on the OGR SQL documentation page " +"to advertise the change of behavior" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:88 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:201 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:251 +msgid "Discussion" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:90 +msgid "" +"Tests done with SQLite show that it is sometimes tolerant to misuse of " +"quote characters, but in the reverse way as current OGR. So it will " +"accept SELECT \"non_existing_column\" FROM 'atable' and interpret it as " +"SELECT 'non_existing_column' FROM \"atable\". On the contrary, PostgreSQL" +" will not accept it. I'd be rather inclined to follow PostgreSQL stricter" +" approach to keep things simple and understandable: \"string literals " +"should be single-quoted, and identifiers (column/table names) unquoted or" +" surrounded by double-quote character\"" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:102 +msgid "The Python autotest suite will be fixed to still pass." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:107 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:131 +msgid "+1 from JukkaR, TamasS, DanielM and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:5 +msgid "RFC 53: OGR not-null constraints and default values" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:16 +msgid "" +"This RFC addresses handling of NOT NULL constraints and DEFAULT values " +"for OGR fields. NOT NULL constraints are useful to maintain basic data " +"integrity and are handled by most (all?) drivers that have SQL " +"capabilities. Default fields values may be used complementary or " +"independently of NOT NULL constraints to specify the value a field must " +"be assigned to if it is not provided when inserting a feature into the " +"layer." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:25 +msgid "NOT NULL constraint" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:27 +msgid "" +"Up to now, OGR fields did not have NOT NULL constraints, i.e. fields in " +"layers/tables were created with the possibility for a field of a " +"feature/record to be unset (i.e. having a NULL value). This will still be" +" the default, i.e. fields are assumed to be nullable. The OGRFieldDefn " +"class is extended with a boolean attribute bNullable that defaults to " +"TRUE and can be set to FALSE to express a NOT NULL constraint (bNullable " +"has been preferred over bNotNullable to avoid confusion with double " +"negation). Drivers that can translate NOT NULL constraints in their " +"storage will use that attribute to determine if the field definition must" +" include a NOT NULL constraint. When opening a datasource, their metadata" +" will be inspected to set the nullable attribute properly, so that round-" +"tripping works." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:40 +msgid "The following methods are added to the OGRFieldDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:79 +msgid "" +"As this holds true for geometry fields, those 2 methods are also add to " +"the OGRGeometryFieldDefn class." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:82 +msgid "" +"Note that adding a field with a NOT NULL constraint on a non-empty layer " +"is generally impossible, unless a DEFAULT value is associated with it." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:85 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:292 +msgid "The following method is added to the OGRFeature class :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:111 +msgid "where nValidateFlags is a combination of :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:148 +msgid "" +"Validation of NOT NULL constraints is generally let to the driver low-" +"level layer, so OGRFeature::Validate() is only useful on a few cases (one" +" of such case is the GML driver)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:152 +msgid "" +"A new flag ALTER_NULLABLE_FLAG = 0x8 is added to be passed to " +"OGRLayer::AlterFieldDefn() so as to set or drop NULL / NOT-NULL " +"constraints (for drivers that implement it)." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:156 +msgid "" +"Drivers that handle NOT NULL constraint for regular attribute fields " +"should advertise the new GDAL_DCAP_NOTNULL_FIELDS and/or " +"GDAL_DCAP_NOTNULL_GEOMFIELDS driver metadata items." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:160 +msgid "" +"Drivers that do not implement the OGRLayer::CreateGeomField() interface " +"(i.e. the ones that support single geometry field), but can create a " +"layer with a NOT NULL constraint on the geometry field can expose a " +"GEOMETRY_NULLABLE=YES/NO layer creation option." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:165 +msgid "" +"Note: due to the way they are commonly written, the CreateField() " +"implementations of drivers that do not support NOT NULL constraint will " +"generally copy the value of the nullable flag, which may be a bit " +"misleading if querying the field definition just after having adding it " +"(the same holds true for width/precision as well)." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:171 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:328 +msgid "All above methods are mapped into the C API :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:184 +msgid "Default field values" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:186 +msgid "" +"Fields with NOT NULL constraints are sometimes accompanied with a DEFAULT" +" clause so as to be able to create a new feature without filling all " +"fields, while maintaining integrity. DEFAULT values can also be set on " +"nullable fields but for reasons exposed later it is recommended to avoid " +"that." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:192 +msgid "" +"Drivers that can translate DEFAULT values in their storage will use that " +"attribute to determine if the field definition must include a DEFAULT " +"value. When opening a datasource, their metadata will be inspected to set" +" the default value attribute properly, so that round-tripping works." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:197 +msgid "" +"There was an embryonic support for default values in GDAL 1.X but that " +"never got implemented beyond the getter/setter methods on OGRFieldDefn. " +"It relied on a \"OGRField uDefault\" member. The choice of OGRField " +"restricts the default values to be expressed with the type of the field, " +"but in some situations we want to be able to assign expressions or " +"special keywords for non-string fields. For example the SQL standard " +"defines CURRENT_TIMESTAMP for DateTime fields. So as to be general, we " +"have remove this uDefault member and replaced it with a \"char\\* " +"pszDefault\" string." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:207 +msgid "The values that can be set as default values are :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:209 +msgid "" +"literal string values enclosed in single-quote characters and properly " +"escaped like: ``'Nice weather. Isn''t it ?'``" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:211 +msgid "numeric values (unquoted)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:212 +msgid "" +"reserved keywords (unquoted): CURRENT_TIMESTAMP, CURRENT_DATE, " +"CURRENT_TIME, NULL" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:214 +msgid "" +"datetime literal values enclosed in single-quote characters with the " +"following defined format: 'YYYY/MM/DD HH:MM:SS[.sss]'" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:216 +#, python-format +msgid "" +"any other driver specific expression. e.g. for SQLite: " +"(strftime('%Y-%m-%dT%H:%M:%fZ','now'))" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:219 +msgid "The following methods are added/modified to the OGRFieldDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:281 +msgid "" +"SetDefault() validates that a string literal beginning with ' is properly" +" escaped." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:284 +msgid "" +"IsDefaultDriverSpecific() returns TRUE if the value set does not belong " +"to one of the 4 bullets in the above enumeration. This is used by drivers" +" to determine if they can handle or not a default value." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:288 +msgid "" +"Drivers should do some effort to interpret and reformat default values in" +" the above 4 standard formats so as to be able to propagate default " +"values from one driver to another one." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:309 +msgid "" +"It will replace unset fields of a feature with their default values, but " +"should rarely be used as most drivers will do that substitution " +"automatically in their low-level layer. CreateFeature() cannot be trusted" +" to automatically modify the passed OGRFeature object to set unset fields" +" to their default values. For that, an explicit GetFeature() call should " +"be issued to retrieve the record as stored in the database." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:316 +msgid "" +"A new flag ALTER_DEFAULT_FLAG = 0x8 is added to be passed to " +"OGRLayer::AlterFieldDefn() so as to set, drop or modify default values " +"(for drivers that implement it)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:320 +msgid "" +"Drivers that handle default values should advertise the new " +"GDAL_DCAP_DEFAULT_FIELDS driver metadata items." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:323 +msgid "" +"Note: due to the way they are commonly written, the CreateField() " +"implementations of drivers that do not support default values will " +"generally copy the value of the default value string, which may be a bit " +"misleading if querying the field definition just after having adding it." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:341 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:518 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:55 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:74 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:156 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:64 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:204 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:293 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:59 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:214 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:111 +msgid "SWIG bindings (Python / Java / C# / Perl) changes" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:343 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:520 +msgid "The following additions have been done :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:345 +msgid "SetNullable(), IsNullable() added on FieldDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:346 +msgid "SetNullable(), IsNullable() added on GeomFieldDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:347 +msgid "Validate() added on Feature class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:348 +msgid "" +"SetDefault(), GetDefault(), IsDefaultDriverSpecific() available on " +"FieldDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:350 +msgid "FillUnsetWithDefault() added on Feature class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:355 +msgid "" +"ogrinfo has been updated to expose NOT NULL constraints and DEFAULT " +"values. e.g." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:370 +msgid "2 news options have been added to ogr2ogr :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:372 +msgid "" +"-forceNullable to remove NOT NULL constraint (NOT NULL constraints are " +"propagated by default from source to target layer)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:374 +msgid "" +"-unsetDefault to remove DEFAULT values (DEFAULT values are propagated by " +"default from source to target layer)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:377 +msgid "" +"Unless it is explicitly specified, ogr2ogr will also automatically set " +"the GEOMETRY_NULLABLE=NO creation option to target layers that support " +"it, if the source layer has its first geometry field with a NOT NULL " +"constraint." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:385 +msgid "New/modified API are documented." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:390 +msgid "The following OGR drivers have been updated to support the new interfaces." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:393 +msgid "" +"PG: supports NOT NULL (for attribute and multiple geometry fields) and " +"DEFAULT on creation/read. AlterFieldDefn() implementation modified to " +"support ALTER_NULLABLE_FLAG and ALTER_DEFAULT_FLAG." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:396 +msgid "" +"PGDump: supports NOT NULL (for attribute and multiple geometry fields) " +"and DEFAULT on creation." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:398 +msgid "" +"CartoDB: supports NOT NULL (for attribute and single geometry fields) and" +" DEFAULT on creation. Supported also on read with authenticated login " +"only (relies on queries on PostgreSQL system tables)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:401 +msgid "" +"GPKG: supports NOT NULL (for attribute and its single geometry field) and" +" DEFAULT on creation/read. GEOMETRY_NULLABLE layer creation added." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:403 +msgid "" +"SQLite: supports NOT NULL (for attribute and multiple geometry fields. " +"Support for multiple geometry fields has been added recently per #5494) " +"and DEFAULT on creation/read. AlterFieldDefn() implementation modified to" +" support ALTER_NULLABLE_FLAG and ALTER_DEFAULT_FLAG." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:408 +msgid "" +"MySQL: supports NOT NULL (for attribute fields only) and DEFAULT on " +"creation/read." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:410 +msgid "" +"OCI: supports NOT NULL (for attribute and its single geometry field) and " +"DEFAULT on creation/read. GEOMETRY_NULLABLE layer creation added." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:412 +msgid "" +"VRT: supports NOT NULL (for attribute and multiple geometry fields) and " +"DEFAULT on read, through new attributes \"nullable\" and \"default\" " +"(driver documentation and data/ogrvrt.xsd updated)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:415 +msgid "" +"GML: supports NOT NULL (for attribute and multiple geometry field) on " +"creation/read. DEFAULT not truly supported (no way to express it in .xsd " +"AFAIK), but on creation, unset fields with a NOT NULL constraint and " +"DEFAULT values will be filled by using FillUnsetWithDefault() so as to " +"generate valid XML." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:420 +msgid "WFS: supports NOT NULL (for attribute fields only) on read" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:421 +msgid "" +"FileGDB: supports NOT NULL (for attribute and its single geometry field) " +"on read/write. GEOMETRY_NULLABLE layer creation added. DEFAULT supported " +"for String,Integer and Real fieds on creation/read (with some bugs/weird " +"behavior seen in FileGDB SDK and E$RI tools, workarounded by using the " +"OpenFileGDB driver in problematic cases...). DEFAULT supported for " +"DateTime on read, but unsupported on creation to bug in FileGDB SDK." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:428 +msgid "" +"OpenFileGDB: supports NOT NULL (for attribute and its single geometry " +"field) and DEFAULT on read" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:431 +msgid "" +"MSSQLSpatial could probably support NOT NULL / DEFAULT, but has not been " +"updated as part of this work." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:437 +msgid "The test suite is extended to test:" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:439 +msgid "" +"all new methods of OGRFieldDefn, OGRGeomFieldDefn and OGRFeature in " +"ogr_feature.py" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:441 +msgid "" +"updated drivers: PG, PGDump, CartoDB, GPKG, SQLite, MySQL, OCI, VRT, GML," +" FileGDB, OpenFileGDB" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:443 +msgid "" +"new options of ogr2ogr, and default behavior with NOT NULL / DEFAULT " +"propagation" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:449 +msgid "This RFC should cause few compatibility issues." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:451 +msgid "" +"Regarding API, the existing OGRFieldDefn::SetDefault() has been changed " +"and GetDefaultRef() has been removed. Impact should be low as this wasn't" +" used in any drivers, was documented as being prone to be removed in the " +"future, and so was unlikely to be used in applications either (there was " +"no C binding)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:457 +msgid "" +"When not using the new API, behavior should remain unchanged w.r.t GDAL " +"1.X when operating on layers created by GDAL. If reading layers created " +"by other tools, then NOT NULL and/or DEFAULT can be read, and propagated." +" We cannot exclude that propagation of NOT NULL / DEFAULT can cause " +"problems in some situations. In which case the new options of ogr2ogr " +"will revert to a behavior that was the one of the GDAL 1.X era." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:467 +msgid "" +"There might be an ambiguity between a field that has not been set and a " +"field that is set to NULL. Both concepts are not distinguished in OGR " +"currently, but most RDBMS are able to make such a distinction." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:471 +msgid "Consider the 2 following statements :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:478 +msgid "They are not equivalent when COL2 has a default value." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:480 +msgid "" +"The behavior of the modified drivers by this RFC is to *NOT* emit NULL at" +" CreateFeature() time when a field is unset, so that the low-level layer " +"of the driver can replace it with its default value if it exists. This is" +" generally the wished behavior." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:485 +msgid "" +"If explicit NULL insertion is wanted, then using SetFeature() afterwards " +"might be needed, if supported by the drivers (some drivers will likely " +"not force unset OGR fields to be NULL when composing an UPDATE " +"statement), otherwise with a direct SQL UPDATE statement." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:490 +msgid "" +"In fact, this confusion between unset or NULL hurts only in the case of " +"fields that are nullable and have a DEFAULT value. If making sure to " +"always associate DEFAULT with NOT NULL, then it becomes a non-issue as " +"the database would refuse explicit NULL values." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:495 +msgid "" +"Solving the confusion would require to add a new state to an instantiated" +" field within a feature to distinguish explicit NULL from unset, but this" +" would have deep impact in drivers and application code." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:506 +msgid "" +"The proposed implementation lies in the \"rfc53_ogr_notnull_default\" " +"branch of the " +"`https://github.com/rouault/gdal2/tree/rfc53_ogr_notnull_default " +"`__ " +"repository." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:511 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/rfc53_ogr_notnull_default " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:517 +msgid "+1 from JukkaR, DanielM and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:5 +msgid "RFC 54: Dataset transactions" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:16 +msgid "" +"This RFC introduces an API to offer a transaction mechanism at dataset " +"level and uses it in the PostgreSQL, SQLite and GPKG drivers. It also " +"reworks significantly how transactions are handled in the PostgreSQL " +"driver. It also introduces a generic mechanism to implement an emulation " +"of transactions for datasources that would not natively support it, and " +"uses it in the FileGDB driver." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:26 +msgid "" +"The current abstraction offers a transaction API at the layer level. " +"However, this is generally misleading since, when it is implemented in " +"DBMS with BEGIN/COMMIT/ROLLBACK sql statements (PostgreSQL, SQLite, GPKG," +" PGDump, MSSQLSpatial), the semantics is really a transaction at database" +" level that spans over all layers/tables. So even if calling " +"StartTransaction() on a layer, it also extends on the changes done on " +"other layers. In a very few drivers " +"StartTransaction()/CommitTransaction() is sometimes used as a mechanism " +"to do bulk insertion. This is for example the case of WFS, CartoDB, GFT, " +"GME. For some of them, it could rather be at dataset level too since " +"potentially multiple layer modifications could be stacked together." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:38 +msgid "" +"Furthermode some use cases require updating several layers consistently, " +"hence the need for a real database level transaction abstraction." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:41 +msgid "" +"The current situation of various drivers is the following (some of the " +"below observations resulting from the analysis are kept mainly for the " +"benefit of developers that would need to work in the drivers) :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:48 +msgid "A few facts about cursors used to run GetNextFeature() requests:" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:50 +msgid "" +"Cursors are needed for retrieval of huge amount of data without being " +"memory bound." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:52 +msgid "Cursors need transactions to run." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:53 +msgid "" +"Default cursors (WITHOUT HOLD) cannot be used outside of the transaction " +"that created tem" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:55 +msgid "" +"You cannot modify the structure of a table while the transaction (yes, " +"the transaction, not the cursor) is still active and if you do that on " +"another connection, it hangs until the other connection commits or " +"rollbacks)" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:59 +msgid "" +"Within a transaction, deleted/modified rows are only visible if they are " +"done before declaring the cursor." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:61 +msgid "" +"Cursors WITH HOLD: may be used outside of transaction but cause a copy of" +" the table to be done --> bad for performance" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:64 +msgid "Current flaws are :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:66 +msgid "" +"one cannot do interleaved layer reading (beyond the first 500 features " +"fetched, can be easily seen with OGR_PG_CURSOR_PAGE=1) due to the " +"underlying implicit transaction created to read layer A being closed when" +" the reading of layer B starts." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:70 +msgid "" +"GetFeature() flushes the current transaction and starts a new one to do a" +" cursor SELECT. Which is unnecessary since we retrieve only one record" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:73 +msgid "" +"SetAttributeFilter() issues a ResetReading() which currently " +"FlushSoftTransaction() the ongoing transaction. Can be annoying in a " +"scenario with long update where you need transactional guarantee" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:77 +msgid "What works :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:79 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:90 +msgid "Transaction support at the layer level forwarded to datasource." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:80 +msgid "Interleaved writing works (even with copy mode)" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:83 +msgid "SQLite/GPKG" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:85 +msgid "" +"Mechanisms used to read table content (sqlite3_prepare() / " +"sqlite3_step()) do not need transactions." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:87 +msgid "" +"Step sees structure modifications (e.g. column addition) if run after " +"prepared statement but before first step." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:89 +msgid "Step sees row modifications/additions as soon as they occur." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:93 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:61 +msgid "MySQL" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:95 +msgid "" +"Cannot do interleaved layer reading (reading in one layer resets the " +"other reading) because of the use of mysql_use_result() that can work " +"with one single request at a time. mysql_store_result() would be a " +"solution but requires ingesting the whole result set into memory, which " +"is inpractical for big layers." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:100 +msgid "" +"step does not set row changes once the query has started (if done through" +" another connection, because if done through ExecuteSQL() the long " +"transaction is interrupted)" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:103 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:110 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:117 +msgid "No transaction support" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:108 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:115 +msgid "Interleaved layer reading works" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:109 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:116 +msgid "Changes done after SELECT seem not to be seen." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:120 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:38 +msgid "Proposed changes" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:123 +msgid "GDALDataset changes" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:125 +msgid "" +"The following methods are added to GDALDataset (and usable by " +"OGRDataSource which inherits from GDALDataset)." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:218 +msgid "" +"Note: in the GDALDataset class itself, those methods have an empty " +"implementation that returns OGRERR_UNSUPPORTED_OPERATION." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:221 +msgid "Those 3 methods are mapped at the C level as :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:229 +msgid "Two news dataset capabilities are added :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:231 +msgid "" +"ODsCTransactions: True if this datasource supports (efficient) " +"transactions." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:233 +msgid "" +"ODsCEmulatedTransactions: True if this datasource supports transactions " +"through emulation." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:237 +msgid "Emulated transactions" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:239 +msgid "" +"A new function OGRCreateEmulatedTransactionDataSourceWrapper() is added " +"for used by drivers that do not natively support transactions but want an" +" emulation of them. It could potentially be adopted by any datasource " +"whose data is supported by files/directories." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:279 +msgid "The definition of the IOGRTransactionBehaviour interface is the following:" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:343 +msgid "OPGRLayer changes" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:345 +msgid "" +"At the OGRLayer level, the documentation of GetNextFeature() receives the" +" following additional information to clarify its semantics :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:359 +msgid "PG driver changes" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:361 +msgid "" +"Dataset level transactions have been implemented, and use of implicitly " +"created transactions reworked." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:364 +msgid "Interleaved layer reading is now possible." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:366 +msgid "" +"GetFeature() has been modified to run without a cursor or a transaction, " +"and all other calls to transactions have been checked/modified to not " +"reset accidentally a transaction initiated by the user." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:370 +msgid "" +"Below the new behavior as described in the updated drv_pg_advanced.html " +"help page :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:493 +msgid "" +"It is recommended to do operations within explicit transactions for ease " +"of mind (some troubles fixing ogr_pg.py, but which does admittedly weird " +"things like reopening connections, which does not fly very well with " +"'implicit' transactions)" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:499 +msgid "GPKG and SQLite driver changes" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:501 +msgid "" +"Dataset level transactions have been implemented. A few fixes made here " +"and there to avoid resetting accidentally a transaction initiated by the " +"user." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:506 +msgid "FileGDB driver changes" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:508 +msgid "" +"The FileGDB driver uses the above described emulation to offer a " +"transaction mechanism. This works by backing up the current state of a " +"geodatabase when StartTransaction(force=TRUE) is called. If the " +"transaction is committed, the backup copy is destroyed. If the " +"transaction is rolled back, the backup copy is restored. So this might be" +" costly when operating on huge geodatabases. Note that this emulation has" +" an unspecified behavior in case of concurrent updates (with different " +"connections in the same or another process)." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:522 +msgid "Dataset.StartTransaction(int force=FALSE)" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:523 +msgid "Dataset.CommitTransaction()" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:524 +msgid "Dataset.RollbackTransaction()" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:525 +msgid "ogr.ODsCTransactions constant" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:526 +msgid "ogr.ODsCEmulatedTransactions constant" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:531 +msgid "" +"ogr2ogr now uses dataset transactions (instead of layer transactions) if " +"ODsCTransactions is advertized." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:537 +msgid "" +"New/modified API are documented. MIGRATION_GUIDE.TXT updated with mention" +" to below compatibility issues." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:543 +msgid "The test suite is extended to test" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:545 +msgid "updated drivers: PG, GPKG, SQLite, FileGDB" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:546 +msgid "use of database transactions by ogr2ogr" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:551 +msgid "" +"As described above, subtle behavior changes can be observed with the PG " +"driver, related to implicit transactions that were flushed before and are" +" no longer now, but this should hopefully be restricted to non-typical " +"use cases. So some cases that \"worked\" before might no longer work, but" +" the new behavior should hopefully be more understandable." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:558 +msgid "" +"The PG and SQLite drivers could accept apparently nested calls to " +"StartTransaction() (at the layer level). This is no longer possible since" +" they are now redirected to dataset transactions, that explicitly do not " +"support it." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:564 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:642 +msgid "Out of scope" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:566 +msgid "" +"The following drivers that implement BEGIN/COMMIT/ROLLBACK could be later" +" enhanced to support dataset transactions: OCI, MySQL, MSSQLSpatial." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:570 +msgid "GFT, CartoDB, WFS could also benefit for dataset transactions." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:572 +msgid "" +"VRT currently supports layer transactions (if the underlying dataset " +"support it, and excluding union layers). If dataset transaction were to " +"be implemented, should it consist in forwarding dataset transaction to " +"source dataset(s) ? Implementation might be complicated in case the same " +"dataset is used by multiple sources, but more fundamentally one cannot " +"guarantee ACID on multiple datasets." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:582 +msgid "" +"A proposed revision on how transactions are implemented in the PG driver " +"was proposed a long time ago (`https://trac.osgeo.org/gdal/ticket/1265 " +"`__) to solve some of the above " +"issues. The patch no longer applies but it is expected that the changes " +"done for this RFC cover the issues that the ticket wanted to address." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:596 +msgid "" +"The proposed implementation lies in the \"rfc54_dataset_transactions\" " +"branch of the " +"`https://github.com/rouault/gdal2/tree/rfc54_dataset_transactions " +"`__ " +"repository." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:601 +msgid "" +"The list of changes: " +"`https://github.com/rouault/gdal2/compare/rfc54_dataset_transactions " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:607 +msgid "+1 from JukkaR, HowardB and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:5 +msgid "RFC 55: Refined SetFeature() and DeleteFeature() semantics" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:16 +msgid "" +"This RFC refines the semantics of SetFeature() and DeleteFeature() so as " +"to be able to distinguish nominal case, attempts of updating/deleting " +"non-existing features, from failures to update/delete existing features." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:23 +msgid "" +"Currently, depending on the drivers, calling SetFeature() or " +"DeleteFeature() on a non-existing feature may succeed, or fail. It is " +"generally not desirable that those functions return the OGRERR_NONE code," +" as in most situations, it might be a sign of invalid input. Therefore " +"the OGRERR_NON_EXISTING_FEATURE return code is introduced so that drivers" +" can inform the calling code that it has attempted to update or delete a " +"non-existing feature." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:32 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:49 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:31 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:29 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:130 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:33 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:99 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:177 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:40 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:55 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:44 +msgid "Changes" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:34 +msgid "#define OGRERR_NON_EXISTING_FEATURE 9 is added to ogr_core.h" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:39 +msgid "" +"The following drivers are updated to implement the new semantics: " +"PostgreSQL, CartoDB, SQLite, GPKG, MySQL, OCI, FileGDB, Shape, MITAB" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:42 +msgid "Note: MSSQL could also likely be updated" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:45 +msgid "Caveats" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:47 +msgid "" +"The behavior of the shapefile driver is a bit particular, in that, its " +"SetFeature() implementation accepts to recreate a feature that had been " +"deleted (and its CreateFeature() implementation ignores any set FID on " +"the passed feature to append a new feature). So " +"OGRERR_NON_EXISTING_FEATURE will effictively been returned only if the " +"FID is negative or greater or equal to the maximum feature count." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:57 +msgid "" +"OGRERR_NON_EXISTING_FEATURE is added. All OGRERR_xxxx constants are " +"exposed to the Python bindings" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:63 +msgid "No impact" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:68 +msgid "" +"Documentation of SetFeature() and DeleteFeature() mentions the new error " +"code. MIGRATION_GUIDE.TXT updated with mention to below compatibility " +"issues." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:75 +msgid "" +"The test suite is extended to test the modified drivers. test_ogrsf also " +"tests the behavior of drivers updating/deleting non-existing features." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:81 +msgid "" +"Code that expected update or deleting of non-existing features to succeed" +" will have to be updated." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:91 +msgid "" +"The proposed implementation lies in the " +"\"rfc55_refined_setfeature_deletefeature_semantics\" branch of the " +"`https://github.com/rouault/gdal2/tree/rfc55_refined_setfeature_deletefeature_semantics" +" " +"`__" +" repository." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:96 +msgid "" +"The list of changes: " +"`https://github.com/rouault/gdal2/compare/rfc55_refined_setfeature_deletefeature_semantics" +" " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:102 +msgid "+1 from from DanielM, HowardB, JukkaR and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:5 +msgid "RFC 56: OFTTime/OFTDateTime millisecond accuracy" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:13 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:13 +msgid "Version: 2.0" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:18 +msgid "" +"This RFC aims at adding millisecond accuracy to OFTTime and OFTDateTime " +"fields, as a number of formats support it explicitly or implicitly : " +"MapInfo, GPX, Atom (GeoRSS driver), GeoPackage, SQLite, PostgreSQL, CSV, " +"GeoJSON, ODS, XLSX, KML (potentially GML too)..." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:26 +msgid "The OGRField enumeration is modified as such :" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:46 +msgid "" +"So the \"GByte Second\" field is removed and replaced by a padding Byte " +"reserved for potential later uses. A \"float Second\" field is added." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:49 +msgid "" +"On 32 bit builds, the size of OGRField is now 12 bytes instead of 8 " +"bytes. On 64 bit builds, the size of OGRField remains 16 bytes." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:53 +msgid "New/modified methods" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:55 +msgid "" +"OGRFeature::SetFieldAsDateTime() methods that took a int nSecond now take" +" a float fSecond parameter. The GetFieldAsDateTime() method that took a " +"int\\* pnSecond is kept, and a new GetFieldAsDateTime() method that takes" +" a float\\* pfSecond is added." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:60 +msgid "In OGRFeature class :" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:80 +msgid "" +"OGRFeature::GetFieldAsString() is modified to output milliseconds if the " +"Second member of OGRField.Date is not integral" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:83 +msgid "OGRParseDate() is modified to parse second as floating point number." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:85 +msgid "" +"The following utility functions have their signature modified to take a " +"OGRField (instead of the full year, month, day, hour, minute, second, " +"TZFlag decomposition) and accept decimal seconds as input/output :" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:115 +msgid "The following drivers now accept milliseconds as input/output :" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:117 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:56 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:437 +msgid "GeoJSON" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:118 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:504 +msgid "CSV" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:119 +msgid "PG" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:120 +msgid "PGDump (output only)" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:121 +msgid "CartoDB" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:122 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:434 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:514 +msgid "GeoPackage" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:123 +msgid "SQLite" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:124 +msgid "MapInfo .tab and .mif" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:125 +msgid "LIBKML" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:126 +msgid "ODS" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:127 +msgid "XLSX" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:128 +msgid "GeoRSS (Atom format)" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:129 +msgid "GPX" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:134 +msgid "" +"Feature.GetFieldAsDateTime() and Feature.SetFieldAsDateTime() now " +"takes/returns a floating point number for seconds" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:140 +msgid "This modifies the C/C++ API and ABI." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:142 +msgid "" +"Output of above mentioned drivers will now include milliseconds if a " +"DateTime/Time field has such precision." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:146 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:116 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:100 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:779 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:199 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:280 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:85 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:187 +msgid "Related ticket" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:148 +msgid "" +"The need came from `http://trac.osgeo.org/gdal/ticket/2680 " +"`__ for MapInfo driver." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:155 +msgid "" +"All new/modified methods are documented. MIGRATION_GUIDE.TXT is updated " +"with a new section for this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:172 +msgid "" +"The proposed implementation lies in the \"subsecond_accuracy\" branch of " +"the `https://github.com/rouault/gdal2/tree/subsecond_accuracy " +"`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:177 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/subsecond_accuracy " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:183 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:148 +msgid "+1 from DanielM, JukkaR and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:5 +msgid "RFC 57: 64-bit bucket counts for histograms" +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:18 +msgid "" +"This RFC modifies the GDALRasterBand GetHistogram(), " +"GetDefaultHistogram() and SetDefaultHistogram() methods to accept arrays " +"of 64-bit integer instead of the current arrays of 32-bit integer for " +"bucket counts. It also changes GetRasterSampleOverview() to take a 64-bit" +" integer. This will fix issues when operating on large rasters that have " +"more than 2 billion pixels." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:28 +msgid "" +"The following methods of GDALRasterBand class are modified to take a " +"GUIntBig\\* argument for GetHistogram() and SetDefaultHistograph(), " +"GUIntBig*\\* for GetDefaultHistogram() and GUIntBig for " +"GetRasterSampleOverview()" +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:50 +msgid "PAM serialization/deserialization is also updated." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:80 +msgid "" +"The existing methods GDALGetRasterHistogram(), GDALGetDefaultHistogram() " +"and GDALSetDefaultHistogram() are marked deprecated. They internally call" +" the 64-bit methods, and, for GDALGetRasterHistogram() and " +"GDALGetDefaultHistogram(), warn if a 32-bit overflow would occur, in " +"which case the bucket count is set to INT_MAX." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:89 +msgid "" +"All in-tree drivers that use/implement the C++ histogram methods are " +"modified: ECW, VRT, MEM and HFA." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:95 +msgid "gdalinfo and gdalenhance are modified to use the modified methods." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:100 +msgid "" +"For Python bindings only, RasterBand.GetHistogram(), " +"GetDefaultHistogram() and SetDefaultHistogram() use the new 64-bit C " +"functions." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:104 +msgid "" +"Other bindings could be updated, but likely need new typemaps for (int, " +"GUIntBig*). In the meantime, they still use the 32-bit C functions." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:110 +msgid "This modifies the C++ API and ABI." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:112 +msgid "" +"Out-of-tree drivers must make sure to take into account the updated C++ " +"API if they implement some of the 4 modified virtual methods." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:118 +msgid "#5159" +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:123 +msgid "" +"All new/modified methods/functions are documented. MIGRATION_GUIDE.TXT is" +" updated with a new section for this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:129 +msgid "Setting/getting 64 bit values is tested in gcore/pam.y and gdrivers/mem.py" +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:138 +msgid "" +"The proposed implementation lies in the \"histogram_64bit_count\" branch " +"of the `https://github.com/rouault/gdal2/tree/histogram_64bit_count " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:142 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/histogram_64bit_count " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:5 +msgid "RFC 58: Removing Dataset Nodata Value" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:7 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:7 +msgid "Authors: Sean Gillies" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:9 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:9 +msgid "Contact: sean at mapbox.com" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:13 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:13 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:13 +msgid "Implementation version: 2.1" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:18 +msgid "" +"This RFC concerns addition of a ``DeleteNoDataValue()`` function to the " +"C++ GDALRasterBand API. This function removes the nodata value of a " +"raster band. When it succeeds, the raster band will have no nodata value." +" When it fails, the nodata value will be unchanged." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:26 +msgid "" +"The nodata value has accessors ``GetNoDataValue()`` and " +"``SetNoDataValue()``. For GeoTIFFs, the value is stored in a " +"TIFFTAG_GDAL_NODATA TIFF tag. Newly created GeoTIFF files can have no " +"nodata value (no tag), but once a nodata value is set and stored it can " +"only be given new values, it can not be removed. Nor can it be set to a " +"value outside the range of the data type; for 8-bit data passing ``nan``," +" ``-inf``, or ``256`` to ``GDALSetNoDataValue()`` has the same effect as " +"passing 0." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:35 +msgid "The problem with un-removable nodata values is this:" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:37 +msgid "" +"Nodata masks (see GDAL RFC 15) can cover up a nodata value but if the " +".msk file gets lost (and this is ever the problem with sidecar files), " +"the nodata value you were hiding is exposed again." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:40 +msgid "" +"Nodata masks are not available everywhere in GDAL, nodata values are the " +"only definition of valid data in some parts of GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:43 +msgid "" +"The current recommended practice for removing a nodata value is to copy " +"the GeoTIFF using gdal_translate, specifying that the nodata tag not be " +"copied over along with the data. By making the nodata value fully " +"editable and removable we could avoid copying unnecessarily." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:51 +msgid "" +"The ``virtual CPLErr DeleteNoDataValue()`` method will be added to the " +"GDALRasterBand method in gdal_priv.h (C++ API), and ``CPLErr " +"GDALDeleteRasterNoDataValue()`` to gdal.h (C API)" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:58 +msgid "The following drivers will be updated: GTiff, MEM, VRT and KEA." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:60 +msgid "" +"For GTiff, the TIFFTAG_GDAL_NODATA TIFF tag is unset if GDAL is built " +"against libtiff 4.X, which is the appropriate behavior. For libtiff 3.X " +"where TIFFUnsetField() does not exist, the tag is set to the empty string" +" : GDAL 2.0 will detect that as the absence of a nodata value, older " +"versions will parse it as 0." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:66 +msgid "" +"The ``GDALPamRasterBand`` class will also be updated (for drivers that " +"have no built-in mechanism nodata mechanism and rely on .aux.xml " +"sidecars). Note that this only removes the tag from the .aux.xml, so in " +"the situation where a driver would have a internal way of storing nodata," +" but would be opened in read-only mode (so defaulting to PAM), " +"DeleteNoData() would have no effect." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:76 +msgid "The DeleteNoDataValue() method is added to the RasterBand object." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:81 +msgid "The gdal_edit.py script is enhanced with a -unsetnodata option." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:86 +msgid "The new method and function are documented." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:91 +msgid "The tests of the updated drivers test the effect of the new method." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:96 +msgid "" +"None for the C API. ABI change for the C++ API because of introduction of" +" a new virtual method." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:102 +msgid "#2020 mentions the issue." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:107 +msgid "Implementation will be done by Even Rouault and be sponsored by Mapbox." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:109 +msgid "" +"A proposed implementation is available in " +"`https://github.com/OSGeo/gdal/compare/trunk...rouault:rfc58_removing_nodata_value" +" " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:115 +msgid "+1 from EvenR, HowardB, DanielM and JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:5 +msgid "RFC 59.1 : GDAL/OGR utilities as a library" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:7 +msgid "Authors: Faza Mahamood, Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:9 +msgid "Contact: fazamhd at gmail dot com, even.rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:18 +msgid "" +"This RFC defines how to expose GDAL/OGR C/C++ utilities as C callable " +"functions. The utility code is modified to call the new function. This " +"RFC gives a general frame and principles, demonstrated with a few " +"utilities, but aimed at being extended with other utilities." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:26 +msgid "" +"There is a need for calling GDAL utilities from code without involving " +"system calls, to be able to work on in-memory datasets and use " +"progress/cancellation callback functions." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:33 +msgid "" +"A public header file gdal_utils.h is created which contains the public " +"declarations of GDAL utilities. The current header(still in progress) can" +" be found `here " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:38 +msgid "" +"Each utility has a function (XXXXOptionsNew) to create an option " +"structure from arguments specified as an array of strings. This function " +"also accepts as argument an extra semi-private structure used to " +"cooperate with the code of the command line utility itself." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:43 +msgid "For GDALInfo():" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:83 +msgid "Similarly for GDALTranslate():" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:105 +msgid "Similarly for GDALWarp():" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:130 +msgid "Similarly for GDALVectorTranslate() (equivalent of ogr2ogr):" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:152 +msgid "" +"For other utilities, see `gdal_utils.h " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:159 +msgid "All bindings" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:161 +msgid "For all bindings, the above functions are mapped to SWIG with :" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:276 +msgid "" +"For other utilities, see `gdal.i " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:280 +msgid "Python bindings" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:282 +msgid "" +"For Python bindings, convenience wrappers are created to allow specifying" +" options in a more user friendly way." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:306 +msgid "" +"gdal.Info() can be used either with setting the attributes of " +"gdal.InfoOptions() or inlined arguments of gdal.Info(). Arguments can be " +"specified as array of strings, command line syntax or dedeicated " +"keywords. So various combinations are possible :" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:734 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:153 +msgid "Utilities are modified to call the respective function." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:739 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:158 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:266 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:341 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:252 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:156 +msgid "All new methods/functions are documented." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:744 +msgid "" +"gdal.Info method is tested in `test_gdalinfo_lib.py " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:747 +msgid "" +"gdal.Translate method is tested in `test_gdal_translate_lib.py " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:750 +msgid "" +"gdal.Warp method is tested in `test_gdalwarp_lib.py " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:753 +msgid "" +"gdal.VectorTranslate method is tested in `test_ogr2ogr_lib.py " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:756 +msgid "" +"gdal.DEMProcessing method is tested in `test_gdaldem_lib.py " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:759 +msgid "" +"gdal.Nearblack method is tested in `test_nearblack_lib.py " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:762 +msgid "" +"gdal.Grid method is tested in `test_gdal_grid_lib.py " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:765 +msgid "" +"gdal.Rasterize method is tested in `test_gdal_rasterize_lib.py " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:768 +msgid "" +"gdal.BuildVRT method is tested in `test_gdalbuildvrt_lib.py " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:774 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:171 +msgid "" +"None expected. Command line utilities will keep the same interface. It " +"will be checked by ensuring their tests in autotest/utilities still pass." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:784 +msgid "Implementation will be done by Faza Mahamood and Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:786 +msgid "" +"The proposed implementation for gdalinfo and gdal_translate lies in the " +"\"rfc59.1\" branch of the `https://github.com/rouault/gdal2/tree/rfc59.1 " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:793 +msgid "+1 from DanielM and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:5 +msgid "RFC 59 : GDAL/OGR utilities as a library" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:7 +msgid "Authors: Faza Mahamood" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:9 +msgid "Contact: fazamhd at gmail dot com" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:11 +msgid "Status: Retracted in favor of :ref:`rfc-59.1`" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:16 +msgid "" +"This RFC defines new function for each GDAL utility. The new utility " +"functions can be used to work on in-memory datasets. The utility code is " +"modified to call the new function. This RFC gives a general frame and " +"principles, demonstrated with gdalinfo, but aimed at being extended with " +"other utilities." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:25 +msgid "" +"There is need for calling GDAL utilities from the code. But this involves" +" using system calls and cannot work on in-memory datasets." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:31 +msgid "" +"New library libgdalutils is created. Both Unix and Windows build have " +"been modified to take into account the new lib. The GDAL utilities are " +"modified to use the new functions. New header file gdal_utils.h is " +"created which contains the public declarations of GDAL utilities. The " +"current header(still in progress) can be found `here " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:66 +msgid "" +"For Python bindings only, new functions Info(), Translate() and Warp() " +"are added in the gdal module which uses the new GDALInfo(), " +"GDALTranslate() and GDALWarp() function respectively. Translate() is " +"added in the ogr module which uses the new OGR2OGR() function." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:71 +msgid "" +"gdal.Info() can be used either with setting the attributes of " +"gdal.InfoOptions() or inlined arguments of gdal.Info()." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:163 +msgid "" +"gdal.Info method is tested in test_gdalinfo_lib.py. gdal.Translate method" +" is tested in test_gdal_translate_lib.py. gdal.Warp method is tested in " +"test_gdalwarp_lib.py. ogr.Translate method is tested in " +"test_ogr2ogr_lib.py." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:176 +msgid "Open question" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:178 +msgid "" +"What name should be given for librarified ogr2ogr? OGR2OGR() or " +"OGRTranslate() ?" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:181 +msgid "" +"The order of arguments in GDALTranslate(), GDALWarp() and OGR2OGR() is " +"currently dest then source(s)." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:194 +msgid "" +"It is similar to GDALCreateCopy(const char\\* pszDestFilename, " +"GDALDatasetH hSrcDS, ....), so at least there's a form of consistency at " +"the API level. Any comments?" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:204 +msgid "Implementation will be done by Faza Mahamood." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:206 +msgid "" +"The proposed implementation lies in the \"gdalinfo\" branch of the " +"`https://github.com/fazam/gdal/tree/gdalinfo " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:209 +msgid "" +"The list of changes : `https://github.com/fazam/gdal/compare/gdalinfo " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:5 +msgid "RFC 5: Unicode support in GDAL" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:16 +msgid "" +"This document contains proposal on how to make GDAL core locale " +"independent preserving support for native character sets." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:24 +msgid "" +"Users work in localized environment using their native languages. That " +"means we can not assume ASCII character set when working with string data" +" passed to GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:27 +msgid "GDAL uses UTF-8 encoding internally when working with strings." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:28 +msgid "GDAL uses Unicode version of third-party APIs when it is possible." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:30 +msgid "" +"So all strings, used in GDAL, are in UTF-8, not in plain ASCII. That " +"means we should convert user's input from the local encoding to UTF-8 " +"during interactive sessions. The opposite should be done for GDAL output." +" For example, when user passes a filename as a command-line parameter to " +"GDAL utilities, that filename should be immediately converted to UTF-8 " +"and only afetrwards passed to functions like GDALOpen() or OGROpen(). All" +" functions, which take character strings as parameters, assume UTF-8 " +"(with except of several ones, which will do the conversion between " +"different encodings, see Implementation). The same is valid for output " +"functions. Output functions (CPLError/CPLDebug), embedded in GDAL, should" +" convert all strings from UTF-8 to local encoding just before printing " +"them. Custom error handlers should be aware of UTF-8 issue and do the " +"proper transformation of strings passed to them." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:45 +msgid "" +"The string encoding pops up again when GDAL needs to call the third-party" +" API. UTF-8 should be converted to encoding suitable for that API. In " +"particular, that means we should convert UTF-8 to UTF-16 before calling " +"CreateFile() function in Windows implementation of VSIFOpenL(). Another " +"example is a PostgreSQL API. PostgreSQL stores strings in UTF-8 encoding " +"internally, so we should notify server that passed string is already in " +"UTF-8 and it will be stored as is without any conversions and losses." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:54 +msgid "" +"For file format drivers the string representation should be worked out on" +" per-driver basis. Not all file formats support non-ASCII characters. For" +" example, various .HDR labeled rasters are just 7-bit ASCII text files " +"and it is not a good idea to write 8-bit strings in such a files. When we" +" need to pass strings, extracted from such file outside the driver (e.g.," +" in SetMetadata() call), we should convert them to UTF-8. If you just " +"want to use extracted strings internally in driver, there is no need in " +"any conversions." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:63 +msgid "" +"In some cases the file encoding can differ from the local system encoding" +" and we do not have a way to know the file encoding other than ask a user" +" (for example, imagine a case when someone added a 8-bit non-ASCII string" +" field to mentioned above plain text .HDR file). That means we can't use " +"conversion form the local encoding to UTF-8, but from the file encoding " +"to UTF-8. So we need a way to get file encoding in some way on per " +"datasource basis. The natural solution of the problem is to introduce " +"optional open parameter \"ENCODING\" to GDALOpen/OGROpen functions. " +"Unfortunately, those functions do not accept options. That should be " +"introduced in another RFC. Fortunately, tehre is no need to add encoding " +"parameter immediately, because it is independent from the general i18n " +"process. We can add UTF-8 support as it is defined in this RFC and add " +"support for forcing per-datasource encoding later, when the open options " +"will be introduced." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:81 +msgid "" +"New character conversion functions will be introduced in CPLString class." +" Objects of that class always contain UTF-8 string internally." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:106 +msgid "" +"In order to use non-ASCII characters in user input every application " +"should call setlocale(LC_ALL, \"\") function right after the entry point." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:110 +msgid "" +"Code example. Let's look how the gdal utilities and core code should be " +"changed in regard to Unicode." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:113 +msgid "For input instead of" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:121 +#: ../../source/development/rfc/rfc5_unicode.rst:136 +msgid "we should do" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:129 +msgid "For output instead of" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:145 +msgid "" +"The filename passed to GDALOpen() in UTF-8 encoding in the code snippet " +"above will be further processed in the GDAL core. On Windows instead of" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:155 +msgid "we do" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:167 +msgid "" +"The actual implementation of the character conversion functions does not " +"specified in this document yet. It needs additional discussion. The main " +"problem is that we need not only local<->UTF-8 encoding conversions, but " +"*arbitrary*\\ <->UTF-8 ones. That requires significant support on " +"software part." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:176 +msgid "" +"The GDAL/OGR backward compatibility will be broken by this new " +"functionality in the way how 8-bit characters handled. Before users may " +"rely on that all 8-bit character strings will be passed through the " +"GDAL/OGR without change and will contain exact the same data all the way." +" Now it is only true for 7-bit ASCII and 8-bit UTF-8 encoded strings. " +"Note, that if you used only ASCII subset with GDAL, you are not affected " +"by these changes." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:184 +msgid "From The Unicode Standard, chapter 5:" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:186 +msgid "" +"*The width of wchar_t is compiler-specific and can be as small as 8 bits." +" Consequently, programs that need to be portable across any C or C++ " +"compiler should not use wchar_t for storing Unicode text.*" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:202 +msgid "Filenames also covered in [[wiki:rfc30_utf8_filenames]]" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:5 +msgid "RFC 60 : Improved round-tripping in OGR" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:9 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:9 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:9 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:9 +msgid "Contact: even.rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:18 +msgid "" +"This RFC defines how to improve better round-tripping in conversion of " +"vector formats, in particular for GeoJSON extensions." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:24 +msgid "" +"Some formats have concepts that are not well modeled by the OGR " +"abstraction, but that are desirable to be preserved in transformation " +"scenarios involving reprojection, spatial/attribute filtering, clipping, " +"etc... where the target format is the source format." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:29 +msgid "" +"Various extensions exist above the core GeoJSON specification: at the " +"FeatureCollection, Feature or Geometry levels." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:32 +msgid "" +"See `https://github.com/mapbox/carmen/blob/master/carmen-geojson.md " +"`__," +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:72 +msgid "" +"`https://github.com/geocoders/geocodejson-" +"spec/blob/master/draft/README.md `__:" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:108 +msgid "" +"or `https://github.com/geojson/draft-" +"geojson/issues/80#issuecomment-138037554 `__ for a few examples." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:133 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:72 +msgid "OGRFeature" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:135 +msgid "" +"Two new members will be added to the OGRFeature class, m_pszNativeData " +"(string) and m_pszNativeMediaType (string). m_pszNativeData will contain " +"the representation (or part of the representation) of the original " +"feature, and m_pszNativeMediaType the `media type " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:141 +msgid "The following methods will be added to OGRFeature class:" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:151 +msgid "" +"Thus, in the GeoJSON case, nativeData would contain the full " +"serialization of a GeoJSON Feature. m_pszNativeMediaType would be set to " +"\"application/vnd.geo+json\" The writer side of the GeoJSON driver would " +"start from the nativeData if present (and if nativeMediaType = " +"\"application/vnd.geo+json\", replace its properties member with the " +"content of the OGR fields and patch its geometry to include additional " +"JSON objects." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:159 +msgid "" +"The OGRFeature::Clone() and ::SetFrom() methods will propagate nativeData" +" and nativeMediaType." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:163 +msgid "OGRLayer" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:165 +msgid "" +"A dedicated metadata domain \"NATIVE_DATA\" in which there would be a " +"\"NATIVE_DATA\" and \"NATIVE_MEDIA_TYPE\" items would be used. In the " +"GeoJSON case, this would contain JSON members at the FeatureCollection " +"level (excluding the features array of course)." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:171 +msgid "Driver open options and layer creation options" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:173 +msgid "" +"Drivers that support nativeData on read should expose a NATIVE_DATA " +"boolean open option, and disable it by default so as not to impact " +"performance. ogr2ogr will by default turn this option on." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:177 +msgid "" +"Drivers that support nativeData on write at the layer level should expose" +" a NATIVE_DATA string and NATIVE_MEDIA_TYPE string layer creation " +"options, so that ogr2ogr can fill them with the content of the " +"NATIVE_DATA metadata domain of the source layer(s)." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:185 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:89 +msgid "The following functions will be added:" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:195 +msgid "SQL result layers" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:197 +msgid "" +"Both OGR SQL and SQLite SQL dialect implementations have been modified to" +" propagate the content of the NATIVE_DATA metadata domain of the source " +"layer (the one of the FROM table) to the target layer, and NativeData and" +" NativeMediaType from source features are copied into target features." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:206 +msgid "" +"The new functions will mapped to SWIG as GetNativeData(), " +"SetNativeData(), GetNativeMediaType() and SetNativeMediaType()" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:212 +msgid "" +"The GeoJSON driver will be modified to implement this RFC, in read and " +"write, and thus will\\* :" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:215 +msgid "" +"declare a NATIVE_DATA open option to enable storing layer and feature " +"native data." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:217 +msgid "" +"and NATIVE_DATA & NATIVE_MEDIA_TYPE layer creation options so as to be " +"able to write native data at FeatureCollection levels" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:219 +msgid "use OGRFeature nativeData on write." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:221 +msgid "" +"The effect of this is that ogr2ogr will be able to preserve the members " +"marked between ``***`` in the below snippet:" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:246 +msgid "" +"Other drivers like ElasticSearch and MongoDB drivers, that use a \\_json " +"OGR field for round-tripping could potentially be upgraded to benefit " +"from the mechanism of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:253 +msgid "" +"ogr2ogr will be modified to automatically copy nativeData at layer and " +"feature level. A -noNativeData flag will be added to avoid doing so, when" +" this is not desirable." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:257 +msgid "" +"By default, ogr2ogr will open datasources with the NATIVE_DATA=YES open " +"option so that drivers that can store nativeData do so. And if the output" +" datasource supports the NATIVE_DATA and NATIVE_MEDIA_TYPE layer creation" +" options, it will feel them with the content of the source layer " +"NATIVE_DATA metadata domain." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:271 +msgid "The GeoJSON and ogr2ogr related tests will be extended" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:276 +msgid "" +"Nothing severe expected. Potentially existing scripts might need to add " +"-noNativeData to get previous behavior." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:282 +msgid "" +"`https://trac.osgeo.org/gdal/ticket/5310 " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:287 +msgid "" +"The implementation will be done by Even Rouault (Spatialys) and be " +"sponsored by Mapbox." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:290 +msgid "" +"The proposed implementation lies in the \"rfc60_native_data\" branch of " +"the ​\\ `https://github.com/rouault/gdal2/tree/rfc60_native_data " +"`__, in pull " +"request `https://github.com/OSGeo/gdal/pull/75 " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:299 +msgid "+1 from HowardB, KurtS, TamasS, JukkaR and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:5 +msgid "RFC 61 : Support for measured geometries" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:9 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:9 +msgid "Contact: ari.jolma at gmail.com" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:13 +msgid "Implementation in version: 2.1" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:18 +msgid "" +"This RFC defines how to implement measured geometries (geometries, where " +"the points have M coordinate, i.e., they are XYM or XYZM)." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:24 +msgid "" +"An M coordinate, which is also known as \"measure\", is an additional " +"value that can be stored for each point of a geometry (IBM Technical " +"Note, `https://www-304.ibm.com/support/docview.wss?uid=swg21054384 " +"`__)." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:29 +msgid "" +"M coordinate is in the OGC simple feature model and it is used in many " +"vector data formats." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:35 +msgid "" +"Changes are required into the C++ API and the C API needs to be enhanced." +" Several drivers need to be changed to take advantage of this enhancement" +" but also due to the changes in the C++ API." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:40 +msgid "Common API" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:42 +msgid "" +"New OGRwkbGeometryType values are needed. SFSQL 1.2 and ISO SQL/MM Part 3" +" will be used, i.e., 2D type + 2000 for M and 2D type + 3000 for ZM. " +"(Also types such as Tin, PolyhedralSurface and Triangle types can be " +"added for completeness, even if unimplemented currently). wkbCurve and " +"wkbSurface have been moved from #define to the OGRwkbGeometryType " +"enumerations, and their Z/M/ZM variants have been added as well (per " +"#6401)" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:50 +msgid "" +"On a more general note, there could (should?) be a path to using a clean " +"set of values and have legacy support as an exception." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:53 +msgid "Abstract types are defined and not part of the enum." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:115 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:41 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:58 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:56 +msgid "C++ API" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:117 +msgid "" +"The property int nCoordinateDimension in class OGRGeometry will be " +"replaced by int flags. It may have the following flags:" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:127 +msgid "" +"The \"ignore\" flag is needed internally for backwards compatibility. The" +" flag OGR_G_NOT_EMPTY_POINT is used only to denote the emptiness of an " +"OGRPoint object." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:131 +msgid "" +"Currently a hack to set nCoordDimension negative is used to denote an " +"empty point." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:134 +msgid "" +"The removal of nCoordinateDimension may imply changes to drivers etc. " +"which get or set it." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:137 +msgid "The tests are" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:144 +msgid "The setters and getters are implemented with \\|= and &=." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:146 +msgid "" +"When any of these flags is set or unset, the corresponding data becomes " +"invalid and may be discarded." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:149 +msgid "" +"Keep the following methods with original semantics, i.e., coordinate " +"dimension is 2 or 3, but deprecate. There is some discrepancy in " +"documentation. Their documentation says that they may return zero for " +"empty points while in ogrpoint.cpp it says that negative nCoordDimension " +"values are used for empty points and the getCoordinateDimension method of" +" point returns absolute value of nCoordDimension - thus not zero. A fix " +"to the doc is probably enough." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:163 +msgid "" +"It is proposed to possibly add a new method to replace " +"getCoordinateDimension. set3D and setMeasured would replace " +"setCoordinateDimension and flattenTo2D. See below." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:167 +msgid "class OGRGeometry:" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:190 +msgid "" +"int CoordinateDimension() should have the new semantics. The method name " +"in simple features documents actually is without prefix get." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:193 +msgid "" +"Whether set3D and setMeasured should affect the children geometries in a " +"collection is an issue. Currently doc for setCoordinateDimension says " +"\"Setting the dimension of a geometry collection will affect the children" +" geometries.\", thus we have already committed to maintaining dimensions " +"of children in collections. It is proposed that set3D and setMeasured " +"either add or strip Z or M values to or from the geometry (including " +"possible children). In general the strategy should be to follow the " +"existing strategy regarding Z (i.e., to strip or add)." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:202 +msgid "" +"Add property double m to class OGRPoint. Add constructor, getters, and " +"setters for it." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:205 +msgid "" +"Add property double \\*padfM to class OGRSimpleCurve. Add constructor, " +"getters, and setters for it. New setters with postfix M are needed for " +"XYM data since the object may be upgraded to XYZ from XY in setters. Add " +"also methods RemoveM() and AddM() with similar semantics as Make3D and " +"Make2D." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:211 +msgid "" +"Override methods set3D and setMeasured in those classes where " +"setCoordinateDimension is overridden." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:214 +msgid "" +"Change the semantics of methods whose name begins with \\_ and have a " +"parameter \"int b3D\". The parameter will be \"int coordinates\", i.e., a" +" flags like int, which tells about Z and M." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:221 +msgid "ogr_core.h:" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:228 +msgid "" +"The current behavior is that calling SetPoint on a geometry with " +"coordinate dimension 2 upgrades the coordinate dimension 3. To keep 2D " +"points 2D SetPoint_2D must be used. Thus we need separate functions for M" +" and ZM geometries. The proposal is to use postfixes M and ZM, i.e., " +"SetPointM, SetPointZM. Similarly for AddPoint." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:234 +msgid "" +"Currently there is no SetPoints_2D function. The doc at pabyZ param at " +"SetPoints comments that \"defaults to NULL for 2D objects\" but that does" +" not seem to be the case. See #6344. If that is fixed as written there, " +"then only SetPointsZM is needed." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:239 +msgid "" +"GetPoint and GetPoints do not have a 2D version, so only \\*ZM version is" +" needed." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:242 +msgid "ogr_api.h:" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:254 +msgid "ogr_p.h (This is public header, so new functions are needed)" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:267 +msgid "pggeometry.h is internal, so we can change the function prototype" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:280 +msgid "Use of padfM requires changes to openfilegdb driver." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:283 +msgid "GEOS, filters, and other issues" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:285 +msgid "" +"When a geometry with measures is sent to GEOS or used as a filter the M " +"coordinate is ignored." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:288 +msgid "" +"LocateAlong and LocateBetween are the only standard methods, which use M " +"but there could be others, which for example get the extent of M. Such " +"are not intended to be added now but they can be added later." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:295 +msgid "" +"The new C API functions need to be exposed through swig. Further changes " +"depend on whether the language bindings are aware of coordinates. At " +"least Python and Perl are." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:299 +msgid "The new geometry types will be included into the i files." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:301 +msgid "" +"Some new setters and getters are needed for M. Is3D, IsMeasured, Set3D " +"and SetMeasured methods should be added. Also OGR_GT_HasM." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:307 +msgid "" +"Drivers that are probably affected by the C++ changes are at least (these" +" use the CoordinateDimension API) pg, mssqlspatial, sqlite, db2, mysql, " +"gml, pgdump, geojson, libkml, gpkg, wasp, gpx, filegdb, vfk, bna, dxf." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:312 +msgid "" +"The now deprecated CoordinateDimension API is proposed to be replaced " +"with calls to \\*3D and \\*Measured." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:315 +msgid "" +"Once the support for M coordinates is in place the driver will advertise " +"the support." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:318 +msgid "" +"Within the work of this RFC the support is built into memory, shape and " +"pg drivers. Support for other drivers are left for further work." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:324 +msgid "There is a minimum requirement and new possibilities." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:326 +msgid "ogrinfo: report measured geom type, report measures" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:328 +msgid "ogr2ogr: support measured geom types" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:330 +msgid "ogrlineref: seems to deal specifically with measures, needs more thought" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:332 +msgid "gdal_rasterize: measure could be used for the burn-in value" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:334 +msgid "gdal_contour: measure could be used as the \"elevation\" value" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:336 +msgid "gdal_grid: measure could be used as the \"Z\" value" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:346 +msgid "" +"At least the initial tests will be done with Perl unit tests " +"(swi/perl/t/measures-\\*.t). Later autotest suite will be extended. " +"Existing tests should not fail." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:353 +msgid "" +"Many drivers (actually datasets and layers) which support measures need " +"to have the support added. Support should be advertised using" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:361 +msgid "" +"The entry point for a creating a layer is CreateLayer method in " +"GDALDataset. If the dataset does not support measured geometries it will " +"strip the measured flag from the geometry type it gets as a parameter. " +"This is in line with current behavior non linear geometry types and " +"datasets not supporting them." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:367 +msgid "" +"ICreateLayer, which all drivers that have create layer capability " +"implement, have geometry type as an argument. The method should call " +"CPLError() with CPLE_NotSupported and return NULL if the driver does not " +"support measures. Similarly for ICreateFeature and ISetFeature." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:372 +msgid "" +"The user-oriented API functions (CreateLayer, CreateFeature, and " +"SetFeature) should (silently) strip out the measures before continuing to" +" the I\\* methods in drivers that do not support measures. This (side " +"effect) may not be what is wanted in some usage scenarios but it would " +"follow the pattern of what is already done with nonlinear geometries. " +"This should be documented." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:379 +msgid "" +"An alternative would be to store M value(s) (or WKT or WKB) as attribute " +"(scalar or vector, depending on the geometry type)." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:382 +msgid "Needs a decision." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:384 +msgid "" +"Some incompatibilities will necessarily be introduced. For example when " +"the current XYM-as-XYZ hack in shape will be replaced by proper XYM." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:390 +msgid "" +"`https://trac.osgeo.org/gdal/ticket/6063 " +"`__ " +"`https://trac.osgeo.org/gdal/ticket/6331 " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:396 +msgid "The implementation will be done by Ari Jolma." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:398 +msgid "" +"The proposed implementation will be in `https://github.com/ajolma/GDAL-" +"XYZM `__" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:404 +msgid "+1 from Even, Tamas, Jukka and Daniel" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:5 +msgid "RFC 62 : Raster algebra" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:13 +msgid "Implementation in version:" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:18 +msgid "" +"It is proposed that a set of functions or methods are written for raster " +"band objects to support \"raster algebra\", i.e., a set of operations, " +"which modify bands or compute values from bands. An example of a " +"modification is adding a value to all the cells of the band. An example " +"of a computation is the maximum cell value in the band. Operations may or" +" may not take arguments, in addition to the band itself, and if they " +"take, the argument may be a numeric value, a data structure, or another " +"band. Similarly, the computed value may be a simple numeric value, a data" +" structure, or another band." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:31 +msgid "" +"Raster algebra is a well known branch of geospatial science and " +"technology and an often needed tool. Currently GDAL does not have " +"comprehensive support for raster algebra in core." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:36 +msgid "Related work" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:38 +msgid "" +"Python bindings: raster bands or parts of raster bands can be read into /" +" written from numpy array objects. Huge rasters can be iterated block by " +"block. numpy methods allow efficient implementation of many raster " +"algebra methods using python. There is some support for parallel " +"processing using numpy." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:44 +msgid "" +"Perl bindings: raster bands or parts of raster bands can be read into / " +"written from PDL objects. Huge rasters can be iterated block by block. " +"PDL methods allow efficient implementation of many raster algebra methods" +" using perl. There is some support for parallel processing using PDL." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:50 +msgid "" +"QGIS raster calculator: raster calculation string is parsed into an " +"expression tree and output band is computed row by row from the inputs. " +"All computations are done with double precision floating point numbers. " +"The calculation does not support parallel processing." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:55 +msgid "PostGIS raster: raster algebra is supported by callback functions." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:57 +msgid "There is existing research, which may be exploited:" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:59 +msgid "" +"Parallel Priority-Flood depression filling for trillion cell digital " +"elevation models on desktops or clusters " +"`http://www.sciencedirect.com/science/article/pii/S0098300416301704 " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:63 +msgid "" +"Parallel Non-divergent Flow Accumulation For Trillion Cell Digital " +"Elevation Models On Desktops Or Clusters " +"`https://arxiv.org/abs/1608.04431 `__" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:68 +msgid "Requirements (Goals)" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:70 +msgid "" +"The implementation should be data type aware. This may mean code written " +"with templates." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:73 +msgid "The implementation should be parallel processing friendly." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:75 +msgid "" +"The implementation should allow a relatively easy to use C++ / C API. " +"This may mean interface, which does not use templates." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:78 +msgid "" +"The implementation should allow arbitrary functions on cell values. I.e.," +" be extensible by the user." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:81 +msgid "" +"The implementation should allow focal methods. I.e., methods, where the " +"value of a cell depends on its neighborhood." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:87 +msgid "" +"The implementation does not need to be tightly integrated with the core. " +"This means an \"add-on\" type solution is ok." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:90 +msgid "" +"GDAL design sets some constraints/requirements to raster algebra " +"implementation: 1) the access to data is based on blocks, 2) GDAL " +"supports several datatypes, even complex values, 3) there is no immediate" +" support for the not-simple data structures needed by some methods (by " +"\"method\" I refer to functions of raster algebra in this text), 4) data " +"can be read from a band in parallel but writing needs to be exclusive." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:104 +msgid "Drivers are not affected." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:109 +msgid "The functionality will be added to the bindings." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:114 +msgid "" +"Existing utilities are not affected but new utilities may be written " +"taking advantage of the new functionality." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:120 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:125 +msgid "Must be written." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:136 +msgid "" +"A proposed implementation is developed at " +"`https://github.com/ajolma/raster_algebra " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:139 +msgid "" +"This code attempts to solve the problem as follows. (The source is in " +"transition from an old approach, which was based on operators as methods," +" while the new approach is based on operator classes)" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:143 +msgid "" +"Classes 'operand' and 'operator' are defined. An operand is an object, " +"which holds data and an operator is an object, which computes a result " +"(essentially an operand) from operands." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:147 +msgid "" +"Raster algebra computation is a tree of operand and operator objects, " +"which is executed in a recursive fashion." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:150 +msgid "" +"There are interface classes and templated concrete classes. The concrete " +"classes inherit from the interface classes." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:153 +msgid "" +"Two operand classes are defined: a number and a band. There is a need for" +" other types of operands. For example a classifier would map integer " +"values or real number ranges into numbers. Code for such exists in the " +"source but it is not organized to reflect the new approach." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:158 +msgid "" +"A central method is 'compute' in band class, which is basically the " +"effective block loop code presented in the documentation for " +"GDALRasterBand::ReadBlock." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:162 +msgid "" +"Multiple data types are supported by template concrete class for bands " +"and by overloaded get_value method, which returns the value in required " +"data type." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:5 +msgid "RFC 63 : Sparse datasets improvements" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:13 +msgid "Version: 2.2" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:18 +msgid "" +"This RFC covers an improvement to manage sparse datasets, that is to say " +"datasets that contain substantial empty regions." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:24 +msgid "" +"There are use cases where one needs to read or generate a dataset that " +"covers a large spatial extent, but in which significant parts are not " +"covered by data. There is no way in the GDAL API to quickly know which " +"areas are covered or not by data, hence requiring to process all pixels, " +"which is rather inefficient. Whereas some formats like GeoTIFF, VRT or " +"GeoPackage can potentially give such an information without processing " +"pixels." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:32 +msgid "" +"It is thus proposed to add a new method GetDataCoverageStatus() in the " +"GDALRasterBand class, that takes as input a window of interest and " +"returns whether it is made of data, empty blocks or a mix of them." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:36 +msgid "" +"This method will be used by the GDALDatasetCopyWholeRaster() method (used" +" by CreateCopy() / gdal_translate) to avoid processing sparse regions " +"when the output driver instructs it to do so." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:43 +msgid "In GDALRasterBand class, a new virtual method is added :" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:128 +msgid "" +"This method has a dumb default implementation that returns " +"GDAL_DATA_COVERAGE_STATUS_UNIMPLEMENTED \\| " +"GDAL_DATA_COVERAGE_STATUS_DATA" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:132 +msgid "The public API is made of :" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:173 +msgid "" +"GDALRasterBand::GetDataCoverageStatus() does basic checks on the validity" +" of the window before calling IGetDataCoverageStatus()" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:179 +msgid "" +"GDALDatasetCopyWholeRaster() and GDALRasterBandCopyWholeRaster() accepts " +"a SKIP_HOLES option that can be set to YES by the output driver to cause " +"GetDataCoverageStatus() to be called on each chunk of the source dataset " +"to determine if contains only holes or not." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:187 +msgid "" +"This RFC upgrades the GeoTIFF and VRT drivers to implement the " +"IGetDataCoverageStatus() method." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:190 +msgid "" +"The GeoTIFF driver has also receive a number of prior enhancements, " +"related to that topic, for example to accept the SPARSE_OK=YES creation " +"option in CreateCopy() mode (or the SPARSE_OK open option in update " +"mode)." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:195 +msgid "Extract of the documentation of the driver:" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:238 +msgid "" +"The Python bindings has a mapping of GDALGetDataCoverageStatus(). Other " +"bindings could be updated (need to figure out how to return both a status" +" flag and a percentage)" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:245 +msgid "No direct changes in utilities." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:248 +msgid "Results" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:250 +msgid "" +"With this new capability, a VRT of size 200 000 x 200 000 pixels that " +"contains 2 regions of 20x20 pixels each can be gdal_translated as a " +"sparse tiled GeoTIFF in 2 seconds. The resulting GeoTIFF can be itself " +"translated into another sparse tiled GeoTIFF in the same time." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:256 +msgid "Future work" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:258 +msgid "" +"Future work using the new capability could be done in overview building " +"or warping. Other drivers could also benefit from that new capability: " +"GeoPackage, ERDAS Imagine, ..." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:265 +msgid "The new method is documented." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:270 +msgid "" +"Tests of the VRT and GeoTIFF drivers are enhanced to test their " +"IGetDataCoverageStatus() implementation." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:276 +msgid "C++ ABI change. No functional incompatibility foreseen." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:281 +msgid "The implementation will be done by Even Rouault." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:283 +msgid "" +"The proposed implementation is in " +"`https://github.com/rouault/gdal2/tree/sparse_datasets " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:286 +msgid "" +"Changes can be seen with " +"`https://github.com/OSGeo/gdal/compare/trunk...rouault:sparse_datasets?expand=1" +" " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:292 +msgid "+1 from EvenR and DanielM" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:5 +msgid "RFC 64: Triangle, Polyhedral surface and TIN" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:7 +msgid "Authors: Avyav Kumar Singh, Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:9 +msgid "Contact: avyavkumar at gmail dot com, even.rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:13 +msgid "Implementation version: GDAL 2.2" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:18 +msgid "" +"As of now, the :cpp:class:`OGRGeometry` class (the base class from which " +"all the subtypes are derived) is limited to OGRCompoundCurve, " +"OGRCircularString, OGRLinearRing, OGRMultiLineString, OGRMultiPoint, " +"OGRMultiPolygon, OGRMultiCurve, OGRSimpleCurve, OGRCurvePolygon and " +"OGRPolygon." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:24 +msgid "" +"This RFC addresses the addition of the following new geometries in " +"OGRGeometry:" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:27 +msgid "" +"Triangle - A subset of polygons, the fundamental difference is that it is" +" made of 3 nodes only (actually 4, with the last one being the repetition" +" of the first one) and ONLY ONE exterior boundary and NO interior " +"polygons." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:31 +msgid "PolyhedralSurface - A 3D figure made exclusively of Polygons." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:32 +msgid "" +"TriangulatedSurface - A subset of PolyhedralSurface; a 3D figure which " +"consists exclusively of Triangles." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:41 +msgid "" +"`BNF of WKT encoding `__: extracted from SQL/MM Part 3" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:44 +msgid "" +"`BNF of WKB encoding `__: extracted from SQL/MM Part 3" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:56 +msgid "" +"Some prelimenary work had already been done prior to this proposal, such " +"as including the necessary WKB codes in ." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:59 +msgid "" +"Additionally, the `SFCGAL `__ library is a new " +"optional dependency of GDAL (build support only done for Unix for now). " +"The minimum version tested to build is 1.2.2 (as found in Ubuntu 16.04). " +"As mentioned in its home page, \"SFCGAL is a C++ wrapper library around " +"CGAL with the aim of supporting ISO 19107:2013 and OGC Simple Features " +"Access 1.2 for 3D operations.\" It is mostly used as a potential geometry" +" backend by PostGIS. It has a C API, that is the one we use." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:67 +msgid "" +"SFCGAL functions may be used by methods of OGRGeometry (currently " +"IsValid(), Distance(), ConvexHull(), Intersection(), Union(), " +"Difference(), SymDifference(), Crosses()), as soon as one of the geometry" +" operands is a Triangle, PolyhedralSurface or TIN." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:72 +msgid "" +"Two new OGRGeometry methods are used to convert SFCGAL geometries <-> OGR" +" geometries." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:80 +msgid "" +"Besides SFCGAL, GEOS methods are still used in some cases, but with the " +"following limitations - a Triangle is converted to a Polygon with one " +"exterior ring; Polyhedral Surfaces and Triangulated Surfaces are " +"converted to geometry collection of polygons. (each Triangle in a " +"Triangulated Surface is converted to a Polygon as described previously)" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:86 +msgid "The API for the new geometries introduced includes -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:88 +msgid "" +"Overwriting existing methods for Polygon in the case of Triangle API. A " +"complete API is provided below -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:129 +msgid "" +"The PolyhedralSurface API is derived from OGRSurface. Internally, it uses" +" an OGRMultiPolygon to store all the Polygons comprising the Polyhedral " +"Surface. Most of the implementations of the methods just reference " +"corresponding OGRMultiPolygon methods with checks to ensure that " +"conditions are maintained." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:200 +msgid "" +"The Triangulated Surface API is similar to Polyhedral Surface, and the " +"MultiPolygon class was tweaked slightly to include methods to run which " +"consisted of subgeometries of the form Triangle. (A MultiPolygon is " +"strictly a collection of Polygons). These methods are internal to " +"OGRMultiPolygon and cannot be accessed by a public user. For instance, " +"the ``OGRMultiPolygon::addGeometryDirectly`` method has a check that the " +"subgeometry added to it should be of the type POLYGON. Rather than mess " +"around with the existing function, a new function has been written which " +"does not implement this check -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:247 +msgid "The Triangulated Surface API is as follows -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:281 +msgid "The new geometry WKB values can be seen as below -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:284 +msgid "Geometry Type" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:284 +msgid "2D" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:284 +msgid "Z" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:284 +msgid "M" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:284 +msgid "ZM" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:286 +msgid "PolyhedralSurface" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:286 +msgid "0015" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:286 +msgid "1015" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:286 +msgid "2015" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:286 +msgid "3015" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:287 +msgid "TIN" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:287 +msgid "0016" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:287 +msgid "1016" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:287 +msgid "2016" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:287 +msgid "3016" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:288 +msgid "Triangle" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:288 +msgid "0017" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:288 +msgid "1017" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:288 +msgid "2017" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:288 +msgid "3017" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:292 +msgid "Geometry conversions" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:294 +msgid "" +"The OGRGeometryFactory::forceTo() and forceToMultiPolygon() methods have " +"been enhanced to support conversions between the new geometry types, and " +"towards multipolygon. Note that converting a TIN or a PolyhedralSurface " +"into a MultiPolygon is semantically incorrect since a MultiPolygon is " +"suppose to contain geometries in the same plane, but it might help when " +"converting those new geometry types into a format that doesn't support " +"them (and such conversion was for example implicitly done in the reading " +"side of the shapefile driver previously)" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:307 +msgid "PostGIS" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:309 +msgid "" +"No changes done to the driver explicitly, but it has been ensured that PG" +" <-> OGR compatibility has been maintained. PostGIS 3D functions work on " +"OGR, simple scripts work, for example from ``autotest/ogr/ogr_pg.py``, we" +" have -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:324 +msgid "ShapeFile" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:326 +msgid "" +"Shapefiles have the concept of a \"MultiPatch\" object. The MultiPatch " +"can be made of several parts, which are" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:329 +msgid "" +"A TriangleStrip is a linked strip of triangles, where every vertex (after" +" the first two) completes a new triangle. A new triangle is always formed" +" by connecting the new vertex with its two immediate predecessors." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:333 +msgid "" +"A TriangleFan is a linked fan of triangles, where every vertex (after the" +" first two) completes a new triangle. A new triangle is always formed by " +"connecting the new vertex with its immediate predecessor and the first " +"vertex of the part." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:337 +msgid "" +"Rings (outer ring, inner ring, first ring, \"non-typed\" ring) Up to now " +"multipatch were read as MultiPolygon. Now, in general, a " +"GeometryCollection will be returned, with zero or several TIN " +"corresponding to the TriangleStrip/TriangleFan and zero or one " +"MultiPolygon with all the rings. If there's only one TIN or one " +"MultiPolygon, it will be returned as a top-level geometry. The layer type" +" will be Unknown On writing, the SHPT layer creation option is extended " +"to recognize the MULTIPATCH value, and the current logic to guess the " +"shape type from the layer geometry type or the geometry type of the first" +" feature is extended to support MULTIPATCH. On a MULTIPATCH layer, " +"geometries of type TIN, POLYHEDRALSURFACE, MULTIPOLYGON or " +"GEOMETRYCOLLECTION (whose subgeometries are on of the 3 previous types) " +"are accepted and converted to a MultiPatch object, trying to use " +"TriangleStrip and TriangleFan if the triangles are in the expected order." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:354 +msgid "FileGDB, OpenFileGDB" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:356 +msgid "" +"The FileGDB format support the MultiPatch object as well, with one " +"extension. There is a new type of part, which is made of several " +"triangles whose organization is not TriangleStrip or TriangleFan. Both " +"drivers have been upgraded to work like the ShapeFile driver on the " +"reading side. On the writing side, the FileGDB driver will automatically " +"write a MultiPatch if the layer geometry type is TIN or " +"PolyhedralSurface. The layer option that existed before " +"CREATE_MULTIPATCH=YES can still be used to force writing as MultiPatch" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:366 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:69 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:480 +msgid "GML" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:368 +msgid "" +"The GML driver has been modified for both input and output -> Triangle, " +"PolyhedralSurface and TriangulatedSurface are capable of being " +"read/written from/to a GML document. Sample examples include -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:417 +msgid "" +"Note that on the writing side those geometries are only generated for a " +"GML 3 output." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:421 +msgid "DXF" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:423 +msgid "" +"The changes in the DXF driver include converting a PolyFaceMesh (a " +"subtype of PolyLine) to PolyhedralSurface. This is illustrated by a bug " +"on the GDAL trac - `https://trac.osgeo.org/gdal/ticket/6246 " +"`__. A PolyFace Mesh consists of" +" points defined initially using specific codes, then these points are " +"described as part of a polygon (a polygon can have four points at the " +"maximum). Reading the PolyFace Mesh is supported in OGR as of now, but " +"write support for it as well (though not implemented by me in this " +"changeset) should be possible as well now." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:436 +msgid "" +"The GeoPackage specification supports [Multi]Point, [Multi]LineString, " +"[Multi]Polygon and GeometryCollection in its core. Curve geometry types " +"are mentioned as a registered extension. But Triangle, PolyhedralSurface " +"or TIN are not mentioned at all. However the GeoPackage geometry blob " +"format being based on ISO WKB, support for the new geometry types did not" +" really require new code. Hence we have kepts this possibility of " +"reading/writing the 3 new geometry types, but with a warning emitted that" +" a non-standard extension will be used on the writing side." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:447 +msgid "Other drivers" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:449 +msgid "" +"The CSV, VRT, PGDump, SQLite (but not Spatialite) drivers support the new" +" geometry types. A couple of drivers have been modified, so as not to " +"crash on the writing side when being provided with the new geometry " +"types. Besides the previously mentioned drivers, the following drivers " +"have been verified to not crash (but potentially error out, or skip " +"unrecognized geometries): MySQL, OCI, KML, LIBKML, GeoJSON, MapInfo" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:459 +msgid "Using standard Doxygen documentation procedure." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:464 +msgid "" +"Many applications will not be able to properly deal with the new geometry" +" types that may now be returned by some drivers. In GDAL 2.1, the new " +"types were introduced mentioning that they might be returned by GDAL in " +"the future. Code should either skip the new geometries, deal with them " +"properly or use the OGR_G_ForceTo() function to convert to a geometry " +"type it supports." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:474 +msgid "" +"Very few changes have been made so that the existing autotest suite still" +" passes. New geometry classes and conversion methods has been added to " +"ogr_geom.py and ogr_gml_geom.py. Updated drivers have received new tests " +"also." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:482 +msgid "" +"Done by Avyav Kumar Singh, under the Google Summer of Code 2016 program, " +"and fine tuned / extended / integrated by Even Rouault." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:485 +msgid "" +"The proposed implementation lies in the \"gsoc-triangle-ps-tin-rebased\" " +"branch of the `https://github.com/rouault/gdal2/tree/gsoc-triangle-ps-" +"tin-rebased `__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:493 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:203 +msgid "+1 from JukkaR, DanielM, HowardB and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:5 +msgid "RFC 65: RFC 7946 GeoJSON" +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:13 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:13 +msgid "Implementation version: 2.2" +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:18 +msgid "" +"GeoJSON has been standardized by the IETF: `RFC 7946 " +"`__. Updates to the OGR GeoJSON " +"driver are needed so that it may write RFC 7946 GeoJSON." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:25 +msgid "" +"The RFC 7946 standard is backwards compatible with the legacy definition " +"of GeoJSON, but has a few differences (see " +"`https://tools.ietf.org/html/rfc7946#appendix-B " +"`__). For OGR, the most " +"significant are: removal of \"crs\" (CRS84 only), counter-clockwise " +"winding of polygons, geometry splitting at the antimeridian, and " +"representation of bounding boxes at the antimeridian and poles. Note: RFC" +" 7946 explicitly restricts to 2D and 3D coordinates, and forbid use of " +"the M dimension for example. This was already the case in the existing " +"driver for the GeoJSON 2008 output." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:35 +msgid "" +"Consensus on the gdal-dev list is that developers should be able to " +"require RFC 7946 GeoJSON by configuring layer creation with an option and" +" that it be an all-or-nothing switch." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:42 +msgid "" +"A layer creation option will be added for the GeoJSON driver, e.g., " +"``RFC7946=TRUE``. When \"on\", OGR will write GeoJSON with CRS84 " +"coordinates (reprojecting as needed) with 7 places of precision by " +"default, polygons wound properly, and geometries split at the " +"antimeridian." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:48 +msgid "" +"Related to that work, the OGRGeometryFactory::transformWithOptions() " +"method has been improved to better deal with reprojection of geometries " +"from polar projections, and projections that span the antimeridian, to " +"EPSG:4326" +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:66 +msgid "Utilities will implement RFC 7946 by using the layer creation option." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:71 +msgid "Documentation of the new layer creation option will reference RFC 7946." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:76 +msgid "The ogr_geojson.py file tests the effect of the new option." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:81 +msgid "" +"As this is a opt-in parameter, no backward compatibility issue. GeoJSON " +"files conformant to RFC 7646 can be read by previous GDAL/OGR versions." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:87 +msgid "#6705" +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:92 +msgid "Implementation has been done by Even Rouault and sponsored by Mapbox." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:97 +msgid "+1 from JukkaR, HowardB, DanielM and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:5 +msgid "RFC 66 : OGR random layer read/write capabilities" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:11 +msgid "Status: Implemented" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:13 +msgid "Implementing version: 2.2" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:18 +msgid "" +"This RFC introduces a new API to be able to iterate over vector features " +"at dataset level, in addition to the existing capability of doing it at " +"the layer level. The existing capability of writing features in layers in" +" random order, that is supported by most drivers with output " +"capabilities, is formalized with a new dataset capability flag." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:27 +msgid "" +"Some vector formats mix features that belong to different layers in an " +"interleaved way, which make the current feature iteration per layer " +"rather inefficient (this requires for each layer to read the whole file)." +" One example of such drivers is the OSM driver. For this driver, a hack " +"had been developed in the past to be able to use the " +"OGRLayer::GetNextFeature() method, but with a really particular " +"semantics. See \"Interleaved reading\" paragraph of :ref:`vector.osm` for" +" more details. A similar need arises with the development of a new " +"driver, GMLAS (for GML Application Schemas), that reads GML files with " +"arbitrary element nesting, and thus can return them in a apparent random " +"order, because it works in a streaming way. For example, let's consider " +"the following simplified XML content :" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:50 +msgid "" +"The driver will be first able to complete the building of feature B " +"before emitting feature A. So when reading sequences of this pattern, the" +" driver will emit features in the order B,A,B,A,..." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:60 +msgid "Two new methods are added at the GDALDataset level :" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:62 +msgid "GetNextFeature():" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:115 +msgid "and ResetReading():" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:134 +msgid "New capabilities" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:136 +msgid "The following 2 new dataset capabilities are added :" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:146 +msgid "The above 2 new methods are available in the C API with :" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:159 +msgid "Discussion about a few design choices of the new API" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:161 +msgid "" +"Compared to OGRLayer::GetNextFeature(), GDALDataset::GetNextFeature() has" +" a few differences :" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:164 +msgid "" +"it returns the layer which the feature belongs to. Indeed, there's no " +"easy way from a feature to know which layer it belongs too (since in the " +"data model, features can exist outside of any layer). One possibility " +"would be to correlate the OGRFeatureDefn\\* object of the feature with " +"the one of the layer, but that is a bit inconvenient to do (and " +"theoretically, one could imagine several layers sharing the same feature " +"definition object, although this probably never happen in any in-tree " +"driver)." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:172 +msgid "" +"even if the feature returned is not NULL, the returned layer might be " +"NULL. This is just a provision for now, since that cannot currently " +"happen. This could be interesting to address schema-less datasources " +"where basically each feature could have a different schema (GeoJSON for " +"example) without really belonging to a clearly identified layer." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:177 +msgid "" +"it returns a progress percentage. When using OGRLayer API, one has to " +"count the number of features returned with the total number returned by " +"GetFeatureCount(). For the use cases we want to address knowing quickly " +"the total number of features of the dataset is not doable. But knowing " +"the position of the file pointer regarding the total size of the size is " +"easy. Hence the decision to make GetNextFeature() return the progress " +"percentage. Regarding the choice of the range [0,1], this is to be " +"consistent with the range accepted by GDAL progress functions." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:186 +#, python-format +msgid "" +"it accepts a progress and cancellation callback. One could wonder why " +"this is needed given that GetNextFeature() is an \"elementary\" method " +"and that it can already returns the progress percentage. However, in some" +" circumstances, it might take a rather long time to complete a " +"GetNextFeature() call. For example in the case of the OSM driver, as an " +"optimization you can ask the driver to return features of a subset of " +"layers. For example all layers except nodes. But generally the nodes are " +"at the beginning of the file, so before you get the first feature, you " +"have typically to process 70% of the whole file. In the GMLAS driver, the" +" first GetNextFeature() call is also the opportunity to do a preliminary " +"quick scan of the file to determine the SRS of geometry columns, hence " +"having progress feedback is welcome." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:199 +msgid "" +"The progress percentage output is redundant with the progress callback " +"mechanism, and the latter could be used to get the former, however it may" +" be a bit convoluted. It would require doing things like:" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:216 +msgid "" +"GDALDatasetGetNextFeature is mapped as gdal::Dataset::GetNextFeature() " +"and GDALDatasetResetReading as gdal::Dataset::ResetReading()." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:219 +msgid "" +"Regarding gdal::Dataset::GetNextFeature(), currently only Python has been" +" modified to return both the feature and its belonging layer. Other " +"bindings just return the feature for now (would need specialized " +"typemaps)" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:227 +msgid "The OSM and GMLAS driver are updated to implement the new API." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:229 +msgid "" +"Existing drivers that support ODsCRandomLayerWrite are updated to " +"advertise it (that is most drivers that have layer creation capabilities," +" with the exceptions of KML, JML and GeoJSON)." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:236 +msgid "" +"ogr2ogr / GDALVectorTranslate() is changed internally to remove the hack " +"that was used for the OSM driver to use the new API, when " +"ODsCRandomLayerRead is advertized. It checks if the output driver " +"advertises ODsCRandomLayerWrite, and if it does not, emit a warning, but " +"still goes on proceeding with the conversion using random layer " +"reading/writing." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:243 +msgid "" +"ogrinfo is extended to accept a -rl (for random layer) flag that " +"instructs it to use the GDALDataset::GetNextFeature() API. It was " +"considered to use it automatically when ODsCRandomLayerRead was " +"advertized, but the output can be quite... random and thus not very " +"practical for the user." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:257 +msgid "" +"The specialized GetNextFeature() implementation of the OSM and GMLAS " +"driver is tested in their respective tests. The default implementation of" +" GDALDataset::GetNextFeature() is tested in the MEM driver tests." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:264 +msgid "None for existing users of the C/C++ API." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:266 +msgid "" +"Since there is a default implementation, the new functions/methods can be" +" safely used on drivers that don't have a specialized implementation." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:269 +msgid "" +"The addition of the new virtual methods GDALDataset::ResetReading() and " +"GDALDataset::GetNextFeature() may cause issues for out-of-tree drivers " +"that would already use internally such method names, but with different " +"semantics, or signatures. We have encountered such issues with a few in-" +"tree drivers, and fixed them." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:278 +msgid "" +"The implementation will be done by Even Rouault, and is mostly triggered " +"by the needs of the new GMLAS driver (initial development funded by the " +"European Earth observation programme Copernicus)." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:282 +msgid "" +"The proposed implementation is in " +"`https://github.com/rouault/gdal2/tree/gmlas_randomreadwrite " +"`__ (commit:" +" " +"`https://github.com/rouault/gdal2/commit/8447606d68b9fac571aa4d381181ecfffed6d72c" +" " +"`__)" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:290 +msgid "+1 from TamasS, HowardB, JukkaR, DanielM and EvenR." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:5 +msgid "RFC 67 : Null values in OGR" +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:18 +msgid "" +"This RFC implement the concept of null value for the field of a feature, " +"in addition to the existing unset status." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:24 +msgid "" +"Currently, OGR supports one single concept to indicate that a field value" +" is missing : the concept of unset field." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:27 +msgid "" +"So assuming a JSON feature collection with 2 features would properties " +"would be { \"foo\": \"bar\" } and { \"foo\": \"bar\", \"other_field\": " +"null }, OGR currently returns that the other_field is unset in both " +"cases." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:31 +msgid "" +"What is proposed here is that in the first case where the \"other_field\"" +" keyword is totally absent, we use the current unset field concept. And " +"for the other case, we add a new concept of null field." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:35 +msgid "" +"This distinction between both concepts apply to all GeoJSON based formats" +" and protocols, so GeoJSON, ElasticSearch, MongoDB, CouchDB, Cloudant." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:39 +msgid "" +"This also applies for GML where the semantics of a missing element would " +"be mapped to unset field and an element with a xsi:nil=\"true\" attribute" +" would be mapped to a null field." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:47 +msgid "OGRField" +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:49 +msgid "" +"The Set structure in the \"raw field\" union is modified to add a third " +"marker" +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:60 +msgid "" +"This is not strictly related to this work but the 3rd marker decreases " +"the likelihood of a genuine value to be misinterpreted as unset / null. " +"This does not increase the size of the structure that is already at least" +" 12 bytes large." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:65 +msgid "" +"The current special value of OGRUnsetMarker = -21121 will be set in the 3" +" markers for unset field (currently set to the first 2 markers)." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:68 +msgid "" +"Similarly for the new Null state, the new value OGRNullMarker = -21122 " +"will be set to the 3 markers." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:74 +msgid "" +"The methods int IsFieldNull( int nFieldIdx ) and void SetNullField ( int " +"nFieldIdx ) are added." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:77 +msgid "" +"The accessors GetFieldXXXX() are modified to take into account the null " +"case, in the same way as if they are called on a unset field, so " +"returning 0 for numeric field types, empty string for string fields, " +"FALSE for date time fields and NULL for list-based types." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:82 +msgid "" +"A convenience method OGRFeature::IsFieldSetAndNotNull() is added to ease " +"the porting of existing code that used previously IsFieldSet() and " +"doesn't need to distinguish between the unset and null states." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:99 +msgid "" +"Lower-level functions will be added to manipulate directly the raw field " +"union (for use mostly in core and a few drivers), instead of directly " +"testing/ setting the markers :" +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:113 +msgid "The new methods will mapped to SWIG." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:118 +msgid "" +"The following drivers will be modified to take into account the unset and" +" NULL state as distinct states: GeoJSON, ElasticSearch, MongoDB, CouchDB," +" Cloudant, GML, GMLAS, WFS." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:122 +msgid "" +"Note: regarding the GMLAS driver, the previous behavior to have both xxxx" +" and xxxx_nil fields when xxxx is an optional nillable XML elements is " +"preserved by default (can be changed through a configuration setting in " +"the gmlasconf.xml file). The rationale is that the GMLAS driver is mostly" +" used to convert to SQL capable formats that cannot distinguish between " +"the unset and null states, hence the need for the 2 dedicated fields." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:130 +msgid "" +"The CSV driver will be modified so that when EMPTY_STRING_AS_NULL open " +"option is specified, the new Null state is used." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:133 +msgid "" +"All drivers that in their writing part test if the source feature has a " +"field unset will also test if the field is null." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:136 +msgid "" +"For SQL based drivers (PG, PGDump, Carto, MySQL, OCI, SQLite, GPKG), on " +"reading a SQL NULL value will be mapped to the new Null state. On " +"writing, a unset field will not be mentioned in the corresponding INSERT " +"or UPDATE statement. Whereas a Null field will be mentioned and set to " +"NULL. On insertion, there will generally be no difference of behavior, " +"unless a default value is defined on the field, in which case it will be " +"used by the database engine to set the value in the unset case. On " +"update, a unset field will not see its content updated by the database, " +"where as a field set to NULL will be updated to NULL." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:149 +msgid "" +"No direct changes, but as the OGRFeature::DumpReadable() method is " +"modified so that unset fields of features are no longer displayed, the " +"output of ogrinfo will be affected." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:161 +msgid "Core changes and updated drivers will be tested." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:166 +msgid "" +"All code, in GDAL source code, and in calling external code, that " +"currently uses OGRFeature::IsFieldSet() / OGR_F_IsFieldSet() should also " +"be updated to used IsFieldNull() / OGR_F_IsFieldNull(), either to act " +"exactly as in the unset case, or add a new appropriate behavior. A " +"convenience method and function OGRFeature::IsFieldSetAndNotNull() / " +"OGR_F_IsFieldSetAndNotNull() is added to ease the porting of existing " +"code." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:174 +msgid "" +"Failure to do so, the existing code will see 0 for numeric field types, " +"empty string for string fields, FALSE for date time fields and NULL for " +"list-based types." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:178 +msgid "" +"On the write side, for the GeoJSON driver, in GDAL 2.1 or before, a unset" +" field was written as field_name: null. Starting with GDAL 2.2, only " +"fields explicitly set as null with OGR_F_SetFieldNull() will be written " +"with a null value. Unset fields of a feature will not be present in the " +"corresponding JSON feature element." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:184 +msgid "MIGRATION_GUIDE.TXT is updated to discuss those compatibility issues." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:194 +msgid "" +"The implementation will be done by Even Rouault (Spatialys) and be " +"sponsored by Safe Software." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:197 +msgid "" +"The proposed implementation is available in " +"`https://github.com/rouault/gdal2/tree/rfc67 " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:5 +msgid "RFC 68: C++11 Compilation Mode" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:8 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:11 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:8 +#: ../../source/development/rfc/rfc71_github_migration.rst:8 +#: ../../source/development/rfc/rfc72_pytest.rst:8 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:8 +#: ../../source/development/rfc/rfc74_sphinx.rst:8 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:8 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:8 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:8 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:8 +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:8 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:8 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:8 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:8 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:8 +#: ../../source/development/rfc/rfc87_signed_int8.rst:8 +#: ../../source/development/rfc/rfc88_googletest.rst:8 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:8 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:8 +#: ../../source/development/rfc/rfc91_dataset_close.rst:8 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:8 +#: ../../source/development/rfc/rfc93_update_feature.rst:8 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:8 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:8 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:8 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:8 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:7 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:8 +msgid "Author:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:8 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:11 +msgid "Kurt Schwehr" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:9 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:12 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:14 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:9 +#: ../../source/development/rfc/rfc71_github_migration.rst:9 +#: ../../source/development/rfc/rfc72_pytest.rst:9 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:9 +#: ../../source/development/rfc/rfc74_sphinx.rst:10 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:9 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:9 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:9 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:9 +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:9 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:9 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:9 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:9 +#: ../../source/development/rfc/rfc84_cmake.rst:10 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:9 +#: ../../source/development/rfc/rfc87_signed_int8.rst:9 +#: ../../source/development/rfc/rfc88_googletest.rst:9 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:9 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:9 +#: ../../source/development/rfc/rfc91_dataset_close.rst:9 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:9 +#: ../../source/development/rfc/rfc93_update_feature.rst:9 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:9 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:9 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:9 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:9 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:8 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:9 +msgid "Contact:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:9 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:12 +msgid "schwehr@google.com / schwehr@gmail.com" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:10 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:15 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:10 +#: ../../source/development/rfc/rfc71_github_migration.rst:10 +#: ../../source/development/rfc/rfc72_pytest.rst:10 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:10 +#: ../../source/development/rfc/rfc74_sphinx.rst:11 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:10 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:10 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:10 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:10 +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:10 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:10 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:10 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:10 +#: ../../source/development/rfc/rfc84_cmake.rst:13 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:10 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:10 +#: ../../source/development/rfc/rfc87_signed_int8.rst:10 +#: ../../source/development/rfc/rfc88_googletest.rst:10 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:10 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:10 +#: ../../source/development/rfc/rfc91_dataset_close.rst:10 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:10 +#: ../../source/development/rfc/rfc93_update_feature.rst:10 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:10 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:10 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:10 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:10 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:9 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:10 +msgid "Started:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:10 +msgid "2017-Apr-11" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:11 +msgid "Passed:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:11 +msgid "2017-Sep-11" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:12 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:16 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:11 +#: ../../source/development/rfc/rfc71_github_migration.rst:11 +#: ../../source/development/rfc/rfc72_pytest.rst:11 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:12 +#: ../../source/development/rfc/rfc74_sphinx.rst:12 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:12 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:12 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:12 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:12 +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:12 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:12 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:12 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:11 +#: ../../source/development/rfc/rfc84_cmake.rst:15 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:11 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:12 +#: ../../source/development/rfc/rfc87_signed_int8.rst:11 +#: ../../source/development/rfc/rfc88_googletest.rst:11 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:11 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:11 +#: ../../source/development/rfc/rfc91_dataset_close.rst:11 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:11 +#: ../../source/development/rfc/rfc93_update_feature.rst:11 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:11 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:11 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:11 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:11 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:10 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:11 +msgid "Status:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:12 +msgid "Adopted, implemented in GDAL 2.3" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:15 +msgid "" +"This RFC is based on `GEOS RFC 5 " +"`__ by Mateusz Łoskot." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:21 +msgid "" +"The document proposes to switch to `C++11 " +"`__ compilation mode as default " +"throughout the whole C++ source code of GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:25 +msgid "" +"The goal of the document is to request and achieve agreement on using " +"C++11 as the minimum required version of the C++ programming language " +"standard." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:32 +msgid "" +"C++11 is the first major update of the C++ standard since 1998. (`C++03 " +"`__ was a bug fix release.)" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:36 +msgid "" +"Having fewer versions of C++ to support will reduce the load on " +"developers and testing systems." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:39 +msgid "" +"C++11 features aim to promote writing clean, compact, type-safe and fast " +"code. It also delivers better feature-wise compatibility with the C " +"language (C99)." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:43 +msgid "" +"The Wikipedia article at `http://en.wikipedia.org/wiki/C++11 " +"`__ does a great job describing all " +"changes in C++11 extensively." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:47 +msgid "" +"The ``std::auto_ptr`` smart pointer, together with a bunch of other " +"features, were deprecated and will be removed from C++17. Features like " +"``std::unique_ptr`` provide much stronger replacements." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:51 +msgid "" +"Enabling C++11 compilation mode will improve the programming environment " +"making it much friendlier than C++98." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:54 +msgid "" +"A social factor: since (many) C++ programmers no longer enjoy C++98, " +"allowing C++11 mode may increase potential for new contributions." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:58 +msgid "Compilers Landscape" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:60 +msgid "" +"Summary of compilers supported by GDAL with their minimal versions " +"required to compile source code based on" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:63 +msgid "" +"`http://en.cppreference.com/w/cpp/compiler_support " +"`__ C++11 features." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:67 +msgid "C++11" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:70 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:82 +msgid "GCC" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:70 +msgid "4.8.1+" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:70 +msgid "`C++11 status `__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:70 +msgid "" +"Debian 8 (stable), Ubuntu 15.04+, Ubuntu 14.04 ``ppa:ubuntu-" +"toolchain-r/test``, Fedora 19+, RHEL7" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:72 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:84 +msgid "Clang" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:72 +msgid "3.3+" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:72 +msgid "`C++11 status `__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:72 +msgid "Debian 8 (stable), Ubuntu 14.04+, Fedora 19+, CentOS 6(?)" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:73 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:85 +msgid "MSVC" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:73 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:85 +msgid "14.0+ (2015)" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:73 +msgid "`C++11 status `__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:73 +msgid "n/a" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:77 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:140 +msgid "C++14" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:79 +msgid "The C++14 compilers are listed for comparison only:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:82 +msgid "4.9+" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:84 +msgid "3.4+" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:89 +msgid "Plan" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:91 +msgid "" +"This proposal only requests agreement for the C++11 compilation mode " +"switch in the current ``trunk`` branch only." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:94 +msgid "" +"This proposal does not suggest any detailed roadmap of large refactoring " +"of the GDAL C++ codebase." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:97 +msgid "" +"The GDAL codebase is > 1.3M LOC and given the available man-power to LOCs" +" ratio, such one-step refactoring would not be feasible." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:100 +msgid "" +"Instead, the task will be tackled with the baby step approach gradually " +"transforming the codebase according to priorities set along the way. Any " +"disruptive refactoring, changes in interfaces of C++ classes, breaking " +"changes in C++ API must be announced and discussed on the mailing list or" +" the bug tracker." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:106 +msgid "" +"*IMPORTANT*: C++11 refactoring must not change the C API or break C API " +"compatibility, unless agreed upon based on prior RFC proposed." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:109 +msgid "" +"However, if the proposal is accepted, any new C++ code written for GDAL " +"must be C++11-compliant." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:112 +msgid "" +"Prior acceptance of this proposal is necessary in order to start any " +"source code refactoring using C++11 features." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:115 +msgid "" +"Once accepted, first step will be to update the build configurations to " +"require C++11-compliant compiler." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:121 +msgid "" +"This section outlines issues potentially caused by upgrade to C++11 " +"language." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:124 +msgid "" +"C++11 destructors, by default, have now the new exception specification " +"of ``nothrow(true)``. Destructors of GDAL classes should be reviewed and " +"any that are allowed/expected to throw exceptions must be marked with " +"``nothrow(false)``. Otherwise, any user of the existing GDAL codebase " +"would find the program terminating whenever GDAL destructor throws an " +"exception. Such review would be beneficial anyway." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:133 +msgid "Release" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:135 +msgid "First release of GDAL with C++11 compiler requirement could be 2.3.0." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:142 +msgid "This section clarifies status of C++14 support in GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:144 +msgid "" +"Once C++11 is adopted as default compilation mode, GDAL developers and " +"maintainers must ensure it also successfully compiles in C++14 and C++17 " +"modes." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:148 +msgid "" +"Are contributors allowed to add ``ifdef``'s for C++14 and C++17? No. Not " +"at this time." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:151 +msgid "" +"Is there a plan to upgrade to C++14 or C++17 to allow use of the C++ " +"latest features? No, there is no plan. It is, however, recognized, such " +"motion may be put to the vote around 2020." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:158 +msgid "" +"`http://en.cppreference.com/w/cpp/compiler_support " +"`__ C++ compiler " +"support" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:169 +msgid "" +"GDAL has been working well with C++11 builds for a number of years now, " +"so there should be no externally visible changes for the initial removal " +"of C++03 support." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:176 +msgid "" +"Change configure.ac to remove ``with_cpp11`` flag, always use C++11, and " +"fail if ``AX_CXX_COMPILE_STDCXX_11`` does not find C++11" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:178 +msgid "Remove @CXX11_SUPPORT@ in GDALmake.opt.in and anywhere else it occurs" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:179 +msgid "" +"Remove continuous build targets that do not support C++11 from Travis-CI " +"and AppVeyor" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:181 +msgid "Remove #if HAVE_CXX11 and leave only the C++11 code" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:183 +msgid "``find . -name \\*.h -o -name \\*.cpp | xargs egrep 'HAVE_CXX11'``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:185 +msgid "CPL_STATIC_ASSERT -> ``static_assert``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:186 +msgid "``NULL`` -> ``nullptr`` (Only for C++ code)" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:187 +msgid "CPL_OVERRIDE -> override and remove redundant virtual" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:188 +msgid "-MAX or -max() -> ``std::numeric_limits::lowest()``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:193 +msgid "" +"The switch does not impact the ``C`` API used by the SWIG bindings. " +"However, there may be some code that can be removed." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:199 +msgid "" +"There are many C++11 features not address in this RFC. See " +"`https://en.wikipedia.org/wiki/C%2B%2B11 " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:202 +msgid "attributes" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:203 +msgid "``auto``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:204 +msgid "``consexpr``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:205 +msgid "``cstdint``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:206 +msgid "``delete`` and ``default`` for member functions" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:207 +msgid "enum classes" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:208 +msgid "initializer lists and ``std::initializer_list``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:209 +msgid "lambda" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:210 +msgid "range based for loops" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:211 +msgid "std::regex" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:212 +msgid "rvalue references" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:213 +msgid "smart pointers ``std::unique_ptr`` and ``std::shared_ptr``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:214 +msgid "" +"New string literals: u8\"An UTF-8 string\", u\"An UTF-16 str\", U\"An " +"UTF-32 str\", R\"xml(raw content)xml\"" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:216 +msgid "``std::thread``, ``thread_local`` and related" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:217 +msgid "tuples" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:218 +msgid "And more..." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:223 +msgid "Any code using the C++ API must use C++11 or newer." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:225 +msgid "The C API should not be impacted." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:227 +msgid "GDAL 2.2.x and older will continue to have C++03 support." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:232 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:141 +msgid "The existing autotest suite should continue to pass." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:237 +msgid "" +"Although the above describes changes should have very few impact on " +"existing applications of the C API, some behavior changes, C++ level " +"changes and the conceptual changes are thought to deserve a 2.3 version " +"number." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:245 +msgid "" +"Implementation will be done by Kurt Schwehr. Others are welcome to pitch " +"in." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:251 +msgid "Related RFCs:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:253 +msgid "" +"`GEOS RFC 5: C++11 Compilation Mode " +"`__: GEOS is switching to requiring" +" C++11 to build." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:256 +msgid "" +"`Move OTB to C++14 `__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:260 +msgid "Amendments" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:262 +msgid "This RFC is superseded per :ref:`rfc-98`." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:267 +msgid "" +"`https://lists.osgeo.org/pipermail/gdal-dev/2017-September/047139.html " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:269 +msgid "EvenR +1" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:270 +msgid "JukkaR +1" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:271 +msgid "DanielM +0" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:272 +msgid "HowardB +1" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:273 +msgid "KurtS +1" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:5 +msgid "RFC 69: C/C++ Code Formatting" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:7 +msgid "" +"This document proposes and describes desired code formatting style used " +"across C and C++ source code in GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:13 +msgid "Co-Author:" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:13 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:8 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:8 +msgid "Alessandro Pasotti" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:14 +msgid "elpaso@itopen.it" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:15 +msgid "2017-May-04" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:16 +msgid "Adpoted, implemented" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:19 +msgid "" +"This RFC is based on `GEOS RFC 4 " +"`__ by Mateusz Łoskot." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:26 +msgid "" +"The document proposes and describes desired default code formatting style" +" guidelines for GDAL programming in C and C++ languages." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:29 +msgid "" +"The goal of this document is to initiate process to reach an agreement " +"for the default code formatting style." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:35 +msgid "" +"There is a need to decide on format of GDAL source code and apply such " +"globally consistent format to GDAL C/C++ codebase." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:38 +msgid "" +"A uniform, codebase-wide formatting style makes reading and comprehending" +" existing code easier, writing code focused on important aspects of new " +"developments and more pleasant, removes burden during a patch or pull " +"request code reviews and prevents `bikeshedding religious arguments " +"`__. Even in small projects, " +"contributing developers discover the problems of working without an " +"agreed upon code format." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:46 +msgid "" +"The utility of such guidelines has been proven by many open source " +"software projects." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:49 +msgid "" +"The scope of the proposal is specifically limited to formatting style " +"guidelines. It is not an intention to develop a general coding guide " +"covering other aspects of writing software like naming, etc." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:54 +#: ../../source/development/rfc/rfc72_pytest.rst:55 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:90 +#: ../../source/development/rfc/rfc74_sphinx.rst:51 +msgid "Proposal" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:56 +msgid "" +"It is important to make effortless for developers to produce properly " +"formatted code." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:59 +msgid "" +"The proposal suggests to use `clang-format " +"`__ version 3.8 or higher " +"to define C++ code formatting rules for GDAL code." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:63 +msgid "" +"The ``clang-format`` is a tool to automatically format C/C++ code, so " +"that developers don't need to worry about style issues. Unlike other " +"tools which use own parsers, ``clang-format`` uses the Clang tokenizer " +"and supports the same C++ source code as the Clang compiler. This " +"guarantees correct output is produced and offers unique features (eg. " +"wrapping long lines whether of code, strings, arrays - something which " +"AStyle has no way of doing)." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:71 +msgid "" +"The style settings can be defined in a ``.clang-format`` configuration " +"file, however to make it as easy as possible, we will use the default " +"style (LLVM style?)." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:75 +msgid "" +"The ``clang-format`` is straightforward to run and can support " +"development workflow as standalone tool or as one of many editor " +"integrations or other bespoke utilities (eg. ``git cl format`` " +"[Chromium])." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:80 +msgid "" +"A new pre-commit hook will be added to the current configuration in " +"``.pre-commit-config.yaml`` to run [clang-format pre-commit]." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:83 +msgid "" +"To enforce the code formatting, a gatekeeper will be installed in CI, " +"rejecting commits with code not conforming to the code formatting style " +"and a brief textual hint to install or update the pre-commit hooks will " +"be added to failure message." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:91 +msgid "Code Formatting Rules" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:93 +msgid "What code formatting rules to use?" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:95 +msgid "" +"*\"A mature engineers know that a standard is more important than which " +"standard.\"* ~[MongoDB]" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:98 +msgid "" +"``clang-format`` offers several defaults (eg. LLVM, Mozilla, Linux, " +"Google C++ Style)." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:101 +msgid "" +"The proposal recommends to use one of the base styles without any " +"modification. It is possible to fine-tune the configuration, but this RFC" +" aims for simplicity." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:105 +msgid "The reasons are two-fold:" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:107 +msgid "" +"make GDAL code unified with the wide spectrum of well-established C/C++ " +"projects" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:109 +msgid "long arguments and religious wars prevention." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:112 +msgid "``.clang-format``" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:114 +msgid "The hope is to avoid requiring a .clang-format file in the code base." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:117 +msgid "``.editorconfig``" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:119 +msgid "" +"`EditorConfig `__ is currently in use and " +"``.editorconfig`` file is provided to automatically tell popular code " +"editors about the basic style settings like indentation, whitespaces and " +"end-of-line markers for distinguished types of plain text files." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:124 +msgid "" +"The ``.editorconfig`` file will have to be updated to match the chosen " +"``.clang-format`` settings if they are required." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:128 +msgid "EOL" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:130 +msgid "``clang-format`` does not enforce line endings." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:132 +msgid "" +"The EOL marker is considered to be `a part of a file encoding decision " +"`__ and not part of any coding style." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:136 +msgid "" +"The EOL marker can be enforced as project-wide setting controlled with " +"``.gitattributes`` and ``.editorconfig``." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:139 +msgid "" +"However, it shall still be left as configurable setting in developer's " +"environment of choice (eg. ``git config``) independently from the " +"project-wide setting." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:144 +msgid "Big Reformat" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:146 +msgid "What to do about the existing code?" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:148 +msgid "The proposal recommends to just do one big reformat of the codebase." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:150 +msgid "" +"While it may seem causing clutter in the repository log (eg. ``svn " +"blame``), if it occurs infrequently (eg. yearly) and is applied to the " +"entire codebase at that time, it should not be very disruptive to the " +"source code history. One way to cope with skewed history is to use ``git " +"blame -w`` which ignores whitespace when comparing commits." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:156 +msgid "" +"Partial application of the code formatting rules would create more work " +"without delivering the full benefit [MongoDB] leading to codebase with " +"different styles mixed." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:160 +msgid "" +"To skip the \"big reformat\" commit from ``git blame``, git offers a " +"mechanism to [git_blame_ignore] , a pre-configured ignore file ``.git-" +"blame-ignore-revs`` will be provided in the source tree with the \"big " +"reformat\" commit hash in it." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:165 +msgid "" +"The ignore file can be specified on the command line with ``git blame " +"--ignore-revs-file .git-blame-ignore-revs`` or it can be set permanently " +"with ``git config blame.ignoreRevsFile .git-blame-ignore-revs``." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:169 +msgid "" +"The a.m. instructions will be added to the `developers documentation " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:173 +msgid "Branches" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:175 +msgid "Branches to run the big reformat in are:" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:177 +msgid "``master``" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:178 +msgid "current stable version (to make backports easier)" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:181 +msgid "After Big Reformat" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:183 +msgid "" +"The pre-commit hook will automatically take care of formatting the code " +"before every commit, the CI test will reject not formatted code." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:187 +msgid "" +"*\"After all, every moment of time wasted on code formatting or " +"discussion thereof is eliminated.\"* ~[MongoDB]" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:193 +msgid "add clang-format to pre-commit configuration file" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:194 +msgid "Set up GitHub workflow [clang-format-check]" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:196 +msgid "" +"A draft of the implementation is available at `this branch " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:198 +msgid "The relevant files are:" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:200 +msgid "" +"`pre-commit " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:201 +msgid "" +"`.clang-format style " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:202 +msgid "" +"`GH workflow " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:203 +msgid "" +"`clang-format script " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:211 +msgid "" +"[clang-format pre-commit] `Clang-Format Pre-Commit `__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:212 +msgid "" +"[clang-format-check] `Clang-Format Check Workflow " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:213 +msgid "" +"[MongoDB] Succeeding With ClangFormat: `Part 1 " +"`__, `Part 2 " +"`__, `Part 3 `__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:219 +msgid "" +"[Chromium] `Using clang-format on Chromium C++ Code " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:221 +msgid "" +"`https://clangformat.com `__ - ``clang-format`` " +"interactive guide and builder" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:223 +msgid "" +"`https://zed0.co.uk/clang-format-configurator/ `__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:224 +msgid "" +"`https://trac.osgeo.org/geos/wiki/RFC4 " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:225 +msgid "" +"[git_blame_ignore] `Ignore Commits in Blame View` `__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:230 +msgid "+1 from PSC members KurtS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:5 +msgid "RFC 6: Geometry and Feature Style as OGR Special Fields" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:16 +msgid "" +"This proposal addresses and issue have been discovered long ago, and OGR " +"provides no equivalent solution so far." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:19 +msgid "" +"Some of the supported formats like Mapinfo.tab may contain multiple " +"geometry types and style information. In order to handle this kind of " +"data sources properly a support for selecting the layers by geometry type" +" or by the style info would be highly required. For more details see the " +"following MapServer related bugs later in this document." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:25 +msgid "" +"All of the proposed changes can be found at the tracking bug of this RFC " +"referenced later in this document." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:31 +msgid "" +"The most reasonable way to support this feature is to extend the " +"currently existing 'special field' approach to allow specifying more than" +" one fields. Along with the already defined 'FID' field we will add the " +"following ones:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:36 +msgid "'OGR_GEOMETRY' containing the geometry type like 'POINT' or 'POLYGON'." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:38 +msgid "'OGR_STYLE' containing the style string." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:39 +msgid "'OGR_GEOM_WKT' containing the full WKT of the geometry." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:41 +msgid "" +"By providing the aforementioned fields one can make for example the " +"following selections:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:44 +msgid "" +"select FID, OGR_GEOMETRY, OGR_STYLE, OGR_GEOM_WKT, \\* from MyTable where" +" OGR_GEOMETRY='POINT' OR OGR_GEOMETRY='POLYGON'" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:46 +msgid "" +"select FID, OGR_GEOMETRY, OGR_STYLE, OGR_GEOM_WKT, \\* from MyTable where" +" OGR_STYLE LIKE '%BRUSH%'" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:48 +msgid "" +"select FID, OGR_GEOMETRY, OGR_STYLE, OGR_GEOM_WKT, \\* from MyTable where" +" OGR_GEOM_WKT LIKE 'POLYGON%'" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:50 +msgid "select distinct OGR_GEOMETRY from MyTable order by OGR_GEOMETRY desc" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:55 +msgid "There are two distinct areas where this feature plays a role" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:57 +msgid "Feature query implemented at ogrfeaturequery.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:59 +msgid "SQL based selection implemented at ogr_gensql.cpp and ogrdatasource.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:62 +msgid "" +"To specify arbitrary number of special fields we will declare an array " +"for the field names and types in ogrfeaturequery.cpp as" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:72 +msgid "" +"So as to make this array accessible to the other files the followings " +"will be added to ogr_p.h" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:90 +msgid "" +"In ogrfeature.cpp the field accessor functions (GetFieldAsString, " +"GetFieldAsInteger, GetFieldAsDouble) will be modified providing the " +"values of the special fields by the field index" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:94 +msgid "" +"The following code will be added to the beginning of " +"OGRFeature::GetFieldAsInteger:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:112 +msgid "" +"The following code will be added to the beginning of " +"OGRFeature::GetFieldAsDouble:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:130 +msgid "" +"The following code will be added to the beginning of " +"OGRFeature::GetFieldAsString:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:160 +msgid "" +"The current implementation of OGRFeature::GetFieldAsString uses a static " +"string to hold the const char\\* return value that is highly avoidable " +"and makes the code thread unsafe. In this regard the 'static char " +"szTempBuffer[80]' will be changed to non static and a new member will be " +"added to OGRFeature in ogrfeature.h as:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:170 +msgid "" +"This member will be initialized to NULL at the constructor, and will be " +"freed using CPLFree() at the destructor of OGRFeature." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:173 +msgid "" +"In OGRFeature::GetFieldAsString all of the occurrences of 'return " +"szTempBuffer;' will be changed to 'return m_pszTmpFieldValue = CPLStrdup(" +" szTempBuffer );'" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:177 +msgid "" +"OGRFeature::GetFieldAsString is responsible to destroy the old value of " +"m_pszTmpFieldValue at the beginning of the function:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:185 +msgid "" +"In ogrfeaturequery.cpp we should change OGRFeatureQuery::Compile to add " +"the special fields like:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:198 +msgid "" +"In ogrfeaturequery.cpp OGRFeatureQueryEvaluator() should be modifyed " +"according to the field specific actions like" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:226 +msgid "" +"In ogrfeaturequery.cpp OGRFeatureQuery::FieldCollector should be modifyed" +" to add the field names like:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:235 +msgid "" +"In ogrdatasource.cpp ExecuteSQL() will allocate the arrays according to " +"the number of the special fields:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:249 +msgid "And the fields will be added as" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:262 +msgid "" +"For supporting the SQL based queries we should also modify the " +"constructor of OGRGenSQLResultsLayer in ogr_gensql.cpp and set the field " +"type properly:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:284 +msgid "" +"Some of the queries will require to modify " +"OGRGenSQLResultsLayer::PrepareSummary in ogr_gensql.cpp will be " +"simplified (GetFieldAsString will be used in all cases to access the " +"field values):" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:294 +msgid "" +"OGRGenSQLResultsLayer::TranslateFeature should also be modifyed when " +"copying the fields from primary record to the destination feature" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:311 +msgid "" +"For supporting the 'order by' queries we should also modify " +"OGRGenSQLResultsLayer::CreateOrderByIndex() as:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:332 +msgid "" +"All of the strings allocated previously should be deallocated later in " +"the same function as:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:352 +msgid "" +"When ordering by the field values the OGRGenSQLResultsLayer::Compare " +"should also be modifyed:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:386 +msgid "Adding New Special Fields" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:388 +msgid "" +"Adding a new special field in a subsequent development phase is fairly " +"straightforward and the following steps should be made:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:391 +msgid "" +"In ogr_p.h a new constant should be added with the value of the " +"SPECIAL_FIELD_COUNT and SPECIAL_FIELD_COUNT should be incremented by one." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:395 +msgid "" +"In ogrfeaturequery.cpp the special field string and the type should be " +"added to SpecialFieldNames and SpecialFieldTypes respectively" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:398 +msgid "" +"The field value accessors (OGRFeature::GetFieldAsString, " +"OGRFeature::GetFieldAsInteger, OGRFeature::GetFieldAsDouble) should be " +"modifyed to provide the value of the new special field. All of these " +"functions provide const return values so GetFieldAsString should retain " +"the value in the m_pszTmpFieldValue member." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:404 +msgid "" +"When adding a new value with a type other than SWQ_INTEGER and SWQ_STRING" +" the following functions might also be modified accordingly:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:408 +msgid "OGRGenSQLResultsLayer::OGRGenSQLResultsLayer" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:409 +msgid "OGRGenSQLResultsLayer::TranslateFeature" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:410 +msgid "OGRGenSQLResultsLayer::CreateOrderByIndex" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:411 +msgid "OGRGenSQLResultsLayer::Compare" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:412 +msgid "OGRFeatureQueryEvaluator" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:417 +msgid "" +"In most cases the backward compatibility of the OGR library will be " +"retained. However the special fields will potentially conflict with " +"regard fields with the given names. When accessing the field values the " +"special fields will take pecedence over the other fields with the same " +"names." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:423 +msgid "" +"When using OGRFeature::GetFieldAsString the returned value will be stored" +" as a member variable instead of a static variable. The string will be " +"deallocated and will no longer be usable after the destruction of the " +"feature." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:431 +msgid "" +"A new gdalautotest/ogr/ogr_sqlspecials.py script to test support for all " +"special fields in the ExecuteSQL() call and with WHERE clauses." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:437 +msgid "" +"The OGR SQL document will be updated to reflect the support for special " +"fields." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:443 +msgid "" +"Tamas Szekeres will implement the bulk of the RFC in time for GDAL/OGR " +"1.4.0." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:446 +msgid "" +"Frank Warmerdam will consider how the backward compatibility issues (with" +" special regard to the modified lifespan of the GetFieldAsString returned" +" value) will affect the other parts of the OGR project and will write the" +" Python regression testing script." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:454 +msgid "" +"Tracking bug for this feature (containing all of the proposed code " +"changes): #1333" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:457 +msgid "MapServer related bugs:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:459 +msgid "`1129 `__" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:460 +msgid "`1438 `__" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:471 +msgid "Andrey Kiselev +1" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:5 +msgid "" +"RFC 70: Guessing output format from output file name extension for " +"utilities" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:8 +#: ../../source/development/rfc/rfc71_github_migration.rst:8 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:8 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:8 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:8 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:8 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:8 +#: ../../source/development/rfc/rfc87_signed_int8.rst:8 +#: ../../source/development/rfc/rfc88_googletest.rst:8 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:8 +#: ../../source/development/rfc/rfc91_dataset_close.rst:8 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:8 +#: ../../source/development/rfc/rfc93_update_feature.rst:8 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:8 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:8 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:8 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:7 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:8 +msgid "Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:9 +#: ../../source/development/rfc/rfc71_github_migration.rst:9 +msgid "even.rouault@spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:10 +msgid "Aug 2017" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:11 +#: ../../source/development/rfc/rfc71_github_migration.rst:11 +#: ../../source/development/rfc/rfc88_googletest.rst:11 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:11 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:11 +#: ../../source/development/rfc/rfc91_dataset_close.rst:11 +#: ../../source/development/rfc/rfc93_update_feature.rst:11 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:11 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:11 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:11 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:10 +msgid "Adopted, implemented" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:12 +msgid "Implementation version:" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:12 +msgid "2.3.0" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:18 +msgid "" +"This proposal is to add syntaxic sugar to make GDAL and OGR command line " +"utilities, so they take into account the extension of the output filename" +" to guess which output driver to use, when it is not explicitly specified" +" with -f / -of switch." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:26 +msgid "" +"Currently command line utilities require to explicitly specify the output" +" format when not wishing to use the default format (generally GeoTIFF for" +" raster, and Shapefile for vector). But this is rather counter-intuitive." +" For example \"gdal_translate in.tif out.png\" will generate a GeoTIFF, " +"and \"ogr2ogr out.gpkg in.shp\" a shapefile. So you have to specify " +"respectively -of PNG and -f GPKG to get the expected result." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:34 +msgid "" +"Guessing the output format from the extension of the output filename is " +"for example a behavior found in ImageMagick convert utility, or in " +"OpenJPEG opj_compress/opj_decompress utilities." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:39 +msgid "Changes in C/C++ and Python utilities" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:41 +msgid "" +"Command line utilities, when neither -f nor -of are specified (note: " +"since r39878 both switches can be indifferently used), will loop through " +"the registered drivers and check if one or several drivers, with output " +"capabilities, declare to recognize the extension of the output filename." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:46 +msgid "" +"When one and only one driver declares this extension (.tif, .png, .jpg " +"etc), it will be used automatically" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:48 +msgid "" +"When several drivers declare this extension (for example KML and LIBKML " +"for .kml), the utility will select the first registered driver (except " +"netCDF instead of GMT for .nc files), and a warning is emitted specifying" +" which driver is used" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:52 +msgid "" +"When no driver declares this extension, and the extension is not empty " +"(e.g a .mpg filename), the utility will error out" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:55 +msgid "For completeness:" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:57 +msgid "" +"When there's no extension, and no prefix is recognized (see below), the " +"default output driver will be silently used, as currently" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:60 +msgid "" +"Since at least GDAL 1.10, the base of this logic already exists since a " +"warning is emitted for C/C++ utilities, when the extension of the output " +"format is known to be recognized by another driver than the default " +"output driver." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:65 +msgid "" +"Similarly, for vector output, if doing something like \"ogr2ogr " +"PG:dbname=mydb out.shp\", a PG:dbname=mydb directory is created with " +"shapefiles, instead of ingesting the shapefile into PostgreSQL. A warning" +" is emitted in that case since the PG driver declares the PG: prefix in " +"its metadata. The new behavior will be to imply the -update switch in " +"such situation." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:72 +msgid "" +"When the utilities are available as library functions (GDALTranslate(), " +"etc.), output format guessing will also be applied if the -f/-of switch " +"is not specified" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:79 +msgid "" +"For librarified utilities (gdal.Translate, etc.), the format argument now" +" defaults to None." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:83 +msgid "Potential issues" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:85 +msgid "" +"There might be some fragility with the new logic in the situation where a" +" GDAL version has only one driver that supports extension xxx, but a " +"later version adds another driver that also supports extension xxx (or " +"another distribution of the same version has a plugin that handles xxx). " +"So scripts that did \"gdal_translate in out.xxx\" would now error out in " +"the next version since several drivers are available." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:92 +msgid "" +"Bottom line: always specify the output driver when " +"reliability/reproducibility is desired." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:95 +msgid "" +"This RFC mostly helps for interactive conversions where the less you type" +" the better." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:101 +msgid "" +"This will break scripts that use an output filename whose extension is " +"matched by a driver which is not the default one. This incompatibility is" +" rather unlikely since previous GDAL versions already emit a warning in " +"this situation (for C/C++ utilities only. for Python utilities default " +"driver is silently used), so people have likely specified the output " +"driver if they really want to do \"gdal_translate in.tif out.png -of " +"GTiff\"." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:109 +msgid "MIGRATION_GUIDE.TXT will mention those potential caveats." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:114 +msgid "" +"The existing autotest suite should continue to pass (with a few changes " +"related to tests for the current behavior)" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:120 +msgid "Implementation will be done by Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:122 +msgid "" +"Proposed implementation is in " +"`https://github.com/rouault/gdal2/tree/rfc70 " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:125 +msgid "" +"Diff: `https://github.com/OSGeo/gdal/compare/trunk...rouault:rfc70 " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:5 +msgid "RFC 71: Migration to GitHub" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:10 +msgid "March 2018" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:17 +msgid "" +"It is proposed that the GDAL source tree and ticket database moves from " +"the OSGeo hosted Subversion repository/Trac database to GitHub. Full " +"source code history will be preserved. To make the migration simpler, " +"existing tickets will remain in OSGeo Trac and will not be migrated to " +"GitHub. New tickets will have to be opened in GitHub." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:24 +msgid "Motivations" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:26 +msgid "" +"It is considered that most developers interested by GDAL development are " +"nowadays more used to git than Subversion, and the use of Subversion as " +"the main source control management makes contributions less attractive." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:30 +msgid "" +"The `https://github.com/OSGeo/gdal `__ " +"mirror has existed since 2012 and has over time become the preferred way " +"for contributors without direct SVN access (or even those with SVN " +"access) to submit their contributions, in particular because of the " +"coupling with the continuous integratations services of Travis-CI and " +"!AppVeyor that enable maintainers to check that the contribution doesn't " +"introduce known regressions + the friendly way of commenting a pull " +"request. However the manual porting of !GitHub pull requests to Trac is a" +" bit painful for GDAL maintainers." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:39 +msgid "" +"GitHub has become the de-facto hosting platform for a lot of open-source " +"projects." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:43 +msgid "Details of the migration" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:45 +msgid "" +"The existing GitHub git repository will be pushed to " +"`https://github.com/OSGeo/gdal_svn_mirror_backup " +"`__ (eventually removed " +"once we are confident further steps have not messed things up)" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:49 +msgid "" +"As GitHub also uses the syntax \"#1234\" to link commit messages to its " +"issues that was also used in Trac, currently when following links in " +"!GitHub that point to a Trac ticket, one ends up to a non-existing or " +"unrelated !GitHub issue/pull request. So the commit messages of the " +"current !GitHub mirror will be rewritten by a \"git filter-branch --msg-" +"filter 'python rewrite.py' -- --all\" command to replace \"#1234\" with " +"\"`https://trac.osgeo.org/gdal/ticket/1234 " +"`__\"" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:57 +msgid "" +"The git 'trunk' branch will be renamed 'master' to follow git best " +"practices" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:59 +msgid "The existing 'tag/x.y.z' branches will be replaced by proper git tags." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:61 +msgid "" +"This modified repository will be forced push to " +"`https://github.com/OSGeo/gdal `__ This " +"will have the consequence of invalidating existing pull request or forks " +"of repository that will have to be rebased to the new one. From that " +"point, \"svn commit\" should be avoided and changes should go to the git " +"repository." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:67 +msgid "" +"The cron job on the OSGeo server that refreshes the website from sources " +"will be modified to pull from !GitHub rather than SVN." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:69 +msgid "" +"Ticket creation permissions will be removed in Trac. Modification or " +"closing of existing open tickets will still be possible. From that point," +" if closing a Trac ticket, one will have manually to reference the github" +" commit." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:73 +msgid "" +"The settings of the GDAL GitHub repository will be changed allow tickets " +"to be filed. Labels and Milestones will be populated with relevant " +"content" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:77 +msgid "" +"Further actions required, in no particular order, and for which help from" +" other GDAL developers/contributors would be welcome:" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:80 +msgid "" +"Most visible Trac wiki documentation will have to be revised to point to " +"GitHub" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:82 +msgid "HOWTO-RELEASE will have to be revised." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:83 +msgid "" +"Existing SVN committers still interested in the project will have to " +"request commit access to the GitHub repo." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:85 +msgid "" +"Some support from OSGeo SAC will be needed to turn the GDAL SVN " +"repository to read-only (a complementary option would be to rename it to " +"gdal_historical so that people pulling from the old one are well aware of" +" the migration by having their scripts 'cleanly' error out)" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:89 +msgid "" +"Some guidelines on how we intend to use git/GitHub features will have to " +"be rewritten." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:93 +msgid "Exit strategy" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:95 +msgid "" +"GitHub is a closed platform. In case it would close or would start askin " +"to pay unreasonable fees, some backup strategy of the tickets would be " +"needed. The solutions might be:" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:99 +msgid "" +"`https://github.com/josegonzalez/python-github-backup " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:100 +msgid "" +"GitLab has an import module from GitHub. Although some experimentation " +"has been done with those, this RFC does *not* cover setting up those " +"solutions as a regular backup system." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:105 +msgid "Not covered by this RFC" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:107 +msgid "" +"Migration of Trac wiki content to GitHub wiki is not in the scope of this" +" RFC. Can be done later" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:111 +msgid "Previous related discussions" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:113 +msgid "" +"`https://lists.osgeo.org/pipermail/gdal-dev/2018-March/048240.html " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:114 +msgid "" +"`https://lists.osgeo.org/pipermail/gdal-dev/2017-September/047060.html " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:119 +msgid "+1 from HowardB, JukkaR, KurtS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:5 +msgid "RFC 72: Update autotest suite to use pytest" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:8 +msgid "Craig de Stigter" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:9 +msgid "craig.destigter@koordinates.com" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:10 +msgid "2018-Sep-27" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:11 +msgid "*Implemented in GDAL 2.4*" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:17 +msgid "" +"The document proposes and describes conversion of the existing Python " +"autotest suite to use the `pytest framework " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:21 +msgid "" +"Using pytest provides significant productivity gains for writing, reading" +" and debugging python tests, compared with the current home-grown " +"approach." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:28 +msgid "" +"The current autotest framework dates back to 2007 (at least), and while " +"reasonably comprehensive (and 186,000 lines of Python) is difficult for " +"developers to use and extend." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:32 +msgid "" +"As a homegrown framework it'll never get any better than the effort GDAL " +"developers put in. For example: reporting, test coverage, " +"parallelisation, resumption, log/output handling, parameterisation." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:35 +msgid "" +"Test failures are typically only as descriptive as \"fail\", determining " +"the cause requires editing the tests." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:37 +msgid "It is difficult to run/rerun individual tests" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:38 +msgid "" +"The tests often assume a set of compile options that may not be valid for" +" the local build." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:40 +msgid "" +"Tests are patched/disabled in various CI environments by scripts outside " +"the test tree. This is opaque to developers working locally." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:42 +msgid "" +"Some tests depend on each other and a specific execution order, making it" +" difficult to debug and extend." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:44 +msgid "Shared functionality is repeated across tests and modules" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:45 +msgid "" +"Tests are typically only written for new functionality, not regressions. " +"(Crudely, from the 2663 commits in the last year only 725 touched the " +"autotest tree)" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:49 +msgid "" +"By adopting an OSS test framework in widespread use we can leverage the " +"ecosystem to provide GDAL with benefits and improvements going forward. " +"The utility of automated testing has been proven for GDAL, and we need to" +" make test writing as easy as possible." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:57 +msgid "" +"Port the existing Python autotest suite to use the `pytest framework " +"`__. Why pytest? It's in widespread " +"use, has a wide set of features, is extensible via plugins, and focuses " +"on making writing and debugging tests as easy as possible - minimising " +"boilerplate code and maximising reuse. `This presentation " +"`__ (despite dating back to " +"2014) gives a brief overview of the key benefits." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:65 +msgid "" +"Do the bulk of this port using automated code refactoring tools so the " +"autotest suite matches the preferred pytest approach. While pytest does " +"support all sorts of custom test collection and execution methods, in " +"order to increase the benefits to developers going forward we should do a" +" proper conversion. Initial goal is to get the tests ported, remove as " +"much boilerplate as feasible, all while keeping the existing CI green. " +"Future goals are to continue to reduce boilerplate code and increase " +"isolation between tests." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:74 +msgid "At a minimum we still need to preserve the existing ability to:" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:76 +msgid "" +"Run all existing CI tests in all environments using the existing " +"configuration" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:78 +msgid "Run individual test modules" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:79 +msgid "Support existing subprocess/multiprocess tests" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:80 +msgid "Support testing under Python 2.7 & Python 3" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:81 +msgid "Stacktraces for assertion failures" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:83 +msgid "" +"The new test suite will be in place for the GDAL 2.4.0 release in " +"December 2018. Changes will not be backported to the 2.3.x or earlier " +"release branches." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:87 +#: ../../source/development/rfc/rfc74_sphinx.rst:110 +msgid "References:" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:89 +msgid "`issue #949 `__." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:90 +msgid "" +"`gdal-dev post `__, Oct 2018" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:95 +msgid "Example" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:97 +msgid "A typical existing GDAL python unit test:" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:124 +msgid "Could *eventually* become something like this" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:135 +msgid "" +"It's a lot clearer what it is actually testing, and all support " +"functionality is handled by shared-use fixtures (``gdaladdo`` & " +"``require_files``), including cleanup and conditional-skipping." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:140 +msgid "Test output" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:142 +msgid "" +"Pytest out-of-the-box produces readable output, and is augmented by the " +"``pytest-sugar`` plugin which makes it even nicer:" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:145 +msgid "" +"Successful tests don't produce much output (a single ``.`` or ``✓`` per " +"test, by default)" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:147 +msgid "" +"Failed tests produce a traceback. Any logs, stdout and stderr produced by" +" the failing tests are printed too. This is a great start for debugging " +"the cause of the failure." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:150 +msgid "Any expressions used in failing asserts are printed." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:151 +msgid "Test output is clearly colourised (red/green) if the terminal supports it." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:154 +msgid "![](pytest-output-example.png, 626px, center)" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:157 +msgid "Plan Phase 1" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:159 +msgid "Progress at `pull request 963 `__." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:162 +msgid "" +"Using code automation, convert the existing Python autotest suite to use " +"pytest-style assertions." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:165 +msgid "" +"rename all tests to ``test_*()``. Pytest finds tests by matching names " +"against a regex and this is the default regex." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:168 +msgid "" +"generate assertions from ``post_reason()``/``return 'fail'`` calls where " +"possible" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:171 +msgid "replace all ``skip``/``fail``/``success`` return values" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:173 +msgid "" +"remove extra ``../pymod`` entries from ``sys.path``. All tests now run in" +" a single process" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:176 +msgid "remove ``__main__`` block and ``gdaltest_list`` from test files" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:178 +msgid "" +"these collectively achieve better test collection/selection, output " +"capturing, and improved assertions and reporting" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:181 +msgid "" +"Manually convert the dynamically-generated tests to use `parametrization " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:184 +msgid "" +"Ensure the slow/internet tests are still marked as such and skipped by " +"default." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:187 +msgid "" +"Use `pytest-sugar `__ to make " +"test output pretty. Disable it in CI since it doesn't work well with " +"travis CI's output buffering." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:191 +msgid "" +"Move environment-specific test-skipping from CI to the test suite, " +"possibly with additional tag/marks." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:194 +msgid "Ensure the existing CI tests pass & debug any failures" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:196 +msgid "Add documentation and a straightforward install process for pytest itself" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:200 +msgid "Notable changes and their implications" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:202 +msgid "" +"tests are now run with ``cd autotest ; pytest``. (The first time you may " +"need to ``pip install -r requirements.txt`` to install pytest)" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:204 +msgid "" +"All tests now run in a single process (they were previously forked for " +"each test module). This means that:" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:207 +msgid "" +"errors during test collection are now loud, and immediately fail the " +"entire test run with a traceback. Previously things like syntax errors in" +" files and errors at module level were easy to miss." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:211 +msgid "a single segfault will kill the entire test run dead." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:213 +msgid "" +"It's now possible to run individual tests, instead of just entire files. " +"However, tests are *not yet independent of each other*. So that might " +"cause the tests to behave differently than if you ran the whole module." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:217 +msgid "" +"``test_py_scripts.run_py_script`` was modified to always run the script " +"as a subprocess. The stdout capturing of the original method did strange " +"things with pytest. This change broke some tests that relied on passing " +"files in the ``/vsimem/`` root to scripts, so those have been changed to " +"use the ``tmp/`` root instead." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:222 +msgid "no test suite support for Python <2.7" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:227 +msgid "Plan Phase 2 / Future Work" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:229 +msgid "" +"Improving test isolation, so running an entire module at a time isn't " +"required." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:231 +msgid "" +"Removing the global ``gdaltest._drv`` variables and replace " +"them with pytest fixtures." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:233 +msgid "Use fixtures for temporary file handling and cleanup" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:234 +msgid "More automated test skipping based on what's actually compiled." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:235 +msgid "Automated style cleanup using `Black `__." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:237 +msgid "" +"Consider parallelising test runs by default (there are several `plugins " +"available `__ for this)" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:244 +msgid "Adopted with the following votes from PSC members:" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:246 +msgid "+1 from EvenR, DanielM, HowardB and KurtS" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:247 +msgid "+0 from JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:5 +msgid "" +"RFC 73: Integration of PROJ6 for WKT2, late binding capabilities, time-" +"support and unified CRS database" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:9 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:9 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:9 +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:9 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:9 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:9 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:9 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:9 +#: ../../source/development/rfc/rfc87_signed_int8.rst:9 +#: ../../source/development/rfc/rfc88_googletest.rst:9 +#: ../../source/development/rfc/rfc93_update_feature.rst:9 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:9 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:9 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:9 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:8 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:9 +msgid "even.rouault @ spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:10 +msgid "2019-Jan-08" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:11 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:11 +msgid "Last modified:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:11 +msgid "2019-May-02" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:12 +msgid "Implemented in GDAL 3.0" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:18 +msgid "" +"The document describe work related to integration of PROJ 6 with GDAL, " +"which adds different capabilities: support for CRS WKT 2 version, \"late " +"binding\" capabilities for coordinate transformations between CRS, " +"support of time-dimension for coordinate operations and the use of a " +"unified CRS database." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:27 +msgid "" +"The motivations are those exposed in `https://gdalbarn.com/#why " +"`__ , which are copied here" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:31 +msgid "" +"Coordinate systems in GDAL, PROJ, and libgeotiff are missing modern " +"capabilities and need a thorough refactoring:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:34 +msgid "" +"The dreaded ad hoc CSV databases in PROJ_LIB and GDAL_DATA are " +"frustrating for users, pose challenges for developers, and impede " +"interoperability of definitions." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:37 +msgid "GDAL and PROJ are missing OGC WKT2 support." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:38 +msgid "" +"PROJ 5.0+ no longer requires datum transformation pivots through WGS84, " +"which can introduce errors of up to 2m, but the rest of the tools do not " +"take advantage of it." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:43 +msgid "CSV database" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:45 +msgid "" +"The use of a SQLite-based database for EPSG and other definitions will " +"allow the projects to add more capability (area-aware validation), " +"transition the custom peculiar data structures of the projects to " +"something more universally consumable, and promote definition " +"interoperability between many coordinate system handling software tools." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:52 +msgid "WKT2" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:54 +msgid "" +"`OGC WKT2 `__ " +"fixes longstanding interoperability coordinate system definition " +"discrepancies. WKT2 contains tools for describing time-dependent " +"coordinate reference systems. PROJ 5+ is now capable of time-dependent " +"transformations, but GDAL and other tools do not yet support them." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:60 +msgid "" +"Several countries are updating their geodetic infrastructure to include " +"time-dependent coordinate systems. For example, Australia and the United " +"States are adapting time-dependent coordinate systems in 2020 and 2022, " +"respectively. The familiar NAD83 and NAVD88 in North America being " +"replaced by NATRF2022 and NAPGD2022, and the industry WILL have to adapt " +"to these challenges sooner or later." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:68 +msgid "WGS84 Pivot" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:70 +msgid "" +"PROJ previously required datum transformation that pivoted through WGS84 " +"via a 7-parameter transform. This pivot is a practical solution, but it " +"can introduce error of about two meters, and many legacy datums cannot be" +" defined in terms of WGS84. PROJ 5+ now provides the tools to support " +"late-binding through its `transformation pipeline framework " +"`__," +" but GDAL and the rest of the tools cannot use it yet. Higher accuracy " +"transformations avoid stepping through WGS84 and eliminates extra " +"transformation steps with side-car data from a local geodetic authority." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:81 +msgid "Related work in other libraries" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:83 +msgid "" +"This RFC is the last step in the \"gdalbarn\" work. Previous steps have " +"consisted in implementing the related changes in PROJ master per `PROJ " +"RFC 2 `__ and in libgeotiff " +"master per `libgeotiff pull request 2 " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:93 +msgid "Third-party library requirements" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:95 +msgid "" +"GDAL master (future 3.0) will require PROJ master (future PROJ 6.0) and " +"libgeotiff master (future libgeotiff 1.5 or 2.0) for build and execution." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:99 +msgid "" +"Regarding PROJ, no internal copy of PROJ will be embedded in GDAL master." +" It is not doable of supporting older versions of PROJ, as the " +"OGRSpatialReference class has been largely rewritten to take advantage of" +" functionality that has been completely moved from GDAL to PROJ: PROJ " +"string import and export, WKT string import and export, EPSG database " +"exploitation. To be able to use more easily GDAL master and PROJ master " +"in complex setups where some GDAL dependencies use a libproj provided by " +"the system, and where mixing naively PROJ master and this older libproj " +"would result in runtime crashes, PROJ master can be built with " +"CFLAGS/CXXFLAGS=-DPROJ_RENAME_SYMBOLS to alias its public symbols, and " +"GDAL will be able to use this custom build. Note that this is not " +"intended to be used in a long term, since proper packaging solutions will" +" eventually use PROJ 6 to rebuild all its reverse dependencies. It should" +" be noted also that PROJ is required at configure / nmake time, that is " +"the dynamic loading at runtime through dlopen() / LoadLibrary() is no " +"longer available." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:116 +msgid "" +"Regarding libgeotiff, the internal copy in frmts/gtiff/libgeotiff has " +"been refreshed with the content of upstream libgeotiff master." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:119 +msgid "" +"All continuous integration systems (Travis-CI and AppVeyor) have been " +"updated to build PROJ master as part of the GDAL build." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:123 +msgid "OGRSpatialReference rewrite" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:125 +msgid "" +"The OGRSpatialReference class is central in GDAL/OGR for all coordinate " +"reference systems (CRS) manipulations. Up to GDAL 2.4, this class " +"contained mostly a OGR_SRSNode root node of a WKT 1 representation, and " +"all getters and setters manipulated this tree representation. As part of " +"this work, the main object contained internally by OGRSpatialReference is" +" now a PROJ PJ object, and methods call PROJ C API getters and setters on" +" this PJ object. This enables to be, mostly (*), representation " +"independent." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:134 +msgid "" +"WKT1, WKT2, ESRI WKT, PROJ strings import and export is now delegated to " +"PROJ. The same holds for import of CRS from the EPSG database, that now " +"relies on proj.db SQLite database. Consequently all the data/\\*.csv " +"files that contained CRS related information have been removed from GDAL." +" It should be noted that \"morphing\" from ESRI WKT is now done " +"automatically when importing WKT." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:141 +msgid "" +"While general semantics of methods like IsSame() or FindMatches() remain " +"the same, underneath implementations are substantially different, which " +"can lead to different results than previous GDAL versions in some cases. " +"In the FindMatches() case, identification of CRS to EPSG entries is " +"generally improved due to enhanced query capabilities in the database." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:147 +msgid "" +"(*) The \"mostly\" precision is here since it was not practical to do " +"this rewrite in every place. So for some methods, an internal WKT1 export" +" is still done. This is the case for methods that take a path to a SRS " +"node (like \"GEOGCS|UNIT\") as an argument, or some methods like " +"SetProjection(), GetProjParm(), that expect a OGC WKT1 specific name. " +"Those are thought to be used mostly be drivers. Changing them to be EPSG " +"names would impact a number of drivers, some of them little tested " +"regarding SRS support, and which furthermore mostly support WKT1 " +"representation only." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:158 +msgid "OGRCoordinateTransformation changes" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:160 +msgid "" +"Since GDAL 2.3 and initial PROJ 5 support, when transforming between two " +"CRS we still relied on the PROJ.4 string export of the source and target " +"CRS to create a coordinate operation pipeline. So this limited to " +"\"early-binding\" operations, that is using the WGS84 pivot through " +"towgs84 or nadgrids PROJ keywords. Now PROJ new capabilities to find " +"appropriate coordinate operations between two CRS is used, offering " +"\"late-binding\" capabilities to take into account other pivots than " +"WGS84 or area of uses." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:169 +msgid "" +"OGRCreateCoordinateOperation() now takes an extra optional arguments to " +"define options." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:172 +msgid "" +"One of those options is to define an area of interest that will be taken " +"into account when searching candidate operations. If several operations " +"match, the \"best\" (according to PROJ sorting criterion) will be " +"selected. Note: it will systematically be used even if later calls to " +"Transform() use coordinates outside of the initial area of interest." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:178 +msgid "" +"Another option is the ability to specify the coordinate operation to " +"apply, so as an override of what GDAL / PROJ would have automatically " +"computed, either as a PROJ string (generally a +proj=pipeline), or a WKT " +"coordinate operation/concatenated operation. Users can typically select a" +" specific coordinate operation by using the new PROJ projinfo utility " +"that can return the candidate operations from a source_crs / target_crs " +"tuple." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:186 +msgid "" +"When no option is specified, GDAL will use PROJ to list all candidate " +"coordinate operations. For each call to Transform(), it will compute the " +"average coordinate of the input coordinates and use it to determine the " +"best coordinate operation from the candidate ones." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:191 +msgid "" +"The Transform() method now takes an extra argument to contain the " +"coordinate epoch (generally as a decimal year value) for coordinate " +"operations that are time-dependent. Related, the transform options of the" +" GDALTransform mechanism typically used by gdalwarp now accepts a " +"COORDINATE_EPOCH for the same purpose." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:198 +msgid "Use of OGRSpatialReference in GDAL" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:200 +msgid "" +"Currently GDAL datasets accept and return a WKT 1 string to describe the " +"SRS. To be more independent of the actual encoding, and for example " +"allowing a GeoPackage raster dataset to be able to use WKT 2, it is " +"desirable to be able to attach a SRS that is not dependent of the " +"representation (WKT 1 or WKT 2), hence using a OGRSpatialReference object" +" instead of a const char\\* string." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:207 +msgid "The following new methods are added in GDALDataset:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:209 +msgid "virtual const OGRSpatialReference\\* GetSpatialRef() const;" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:210 +msgid "virtual CPLErr SetSpatialRef(const OGRSpatialReference*);" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:211 +msgid "virtual const OGRSpatialReference\\* GetGCPSpatialRef() const;" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:212 +msgid "" +"virtual CPLErr SetGCPs(int nGCPCount, const GDAL_GCP *pasGCPList, const " +"OGRSpatialReference*);" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:215 +msgid "" +"To ease the transition, the following non virtual methods are added in " +"GDALDataset:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:218 +msgid "const OGRSpatialReference\\* GetSpatialRefFromOldGetProjectionRef() const;" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:220 +msgid "" +"CPLErr OldSetProjectionFromSetSpatialRef(const OGRSpatialReference\\* " +"poSRS);" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:222 +msgid "" +"const OGRSpatialReference\\* GetGCPSpatialRefFromOldGetGCPProjection() " +"const;" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:224 +msgid "" +"CPLErr OldSetGCPsFromNew( int nGCPCount, const GDAL_GCP \\*pasGCPList, " +"const OGRSpatialReference \\* poGCP_SRS );" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:227 +msgid "" +"and the previous GetProjectionRef(), SetProjection(), GetGCPProjection() " +"and SetGCPs() are available as projected virtual methods, prefixed by an " +"underscore" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:231 +msgid "" +"This way to convert an existing driver, it is a matter of renaming its " +"GetProjectionRef() method as \\_GetProjectionRef(), and adding:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:241 +msgid "Default WKT version" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:243 +msgid "" +"OGRSpatialReference::exportToWkt() without options will report WKT 1 " +"(with explicit AXIS nodes. See below \"Axis order issues\" paragraph) for" +" CRS compatibles of this representation, and otherwise use WKT2:2018 " +"(typically for Geographic 3D CRS)." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:248 +msgid "" +"An enhanced version of exportToWkt() accepts options to specify the exact" +" WKT version used, if multi-line or single-line output must be used, etc." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:252 +msgid "" +"Alternatively the OSR_WKT_FORMAT configuration option can be used to " +"modify the WKT version used by exportToWk() (when no explicit version is " +"passed in the options of exportToWkt())" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:256 +msgid "" +"The gdalinfo, ogrinfo and gdalsrsinfo utililies will default to " +"outputting WKT2:2018" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:260 +msgid "Axis order issues" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:262 +msgid "" +"This is a recurring pain point. This RFC proposes a new approach (without" +" pretending to solving it completely) to what was initially done per `RFC" +" 20: OGRSpatialReference Axis Support <./rfc20_srs_axes>`__. The issue is" +" that CRS official definitions use axis orders that do not conform to the" +" way raster or vector data is traditionally encoded in GIS applications. " +"The typical example is the Geographic \"WGS 84\" definition from EPSG, " +"EPSG:4326, which uses latitude as the first axis and longitude as the " +"second axis. RFC 20 decided that by default the AXIS definition would be " +"stripped off from the WKT when the axis order from the authority did not " +"match the GIS friendly one (and use a custom EPSGA authority to have WKT " +"with official AXIS elements)" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:274 +msgid "" +"This was technically possible since the WKT 1 grammar makes the AXIS " +"element definition. However removal of the AXIS definitions was a " +"potential source of confusion as it was unclear which axis order was " +"actually used. Furthermore, in WKT2, the AXIS element is compulsory, and " +"the internal PROJ representation requires also a coordinate system to be " +"defined. So there would have been two unsatisfactory options:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:281 +msgid "" +"return patched versions of the official definition with the GIS friendly " +"order, while still using the official authority code. Practical since we " +"keep the link with the source code, but a lie since we modify it. Users " +"would not know whether they must trust the encoded order, or the official" +" order from the authority." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:286 +msgid "" +"return patched versions of the official definition with the GIS friendly " +"order, but without the official authority code. This would be compliant, " +"but we would lose the link with the authority code." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:290 +msgid "" +"The solution put forward in this RFC is to add a \"data axis to SRS axis " +"mapping\" concept, which is a bit similar to what is done in WCS " +"DescribeCoverage response to explain how the SRS axis map to the grid " +"axis of a coverage" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:295 +msgid "" +"Extract from " +"`https://docs.geoserver.org/stable/en/user/extensions/wcs20eo/index.html " +"`__" +" for a coverage that uses EPSG:4326" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:308 +msgid "" +"A similar mapping is added to define how the 'x' and 'y' components in " +"the geotransform matrix or in a OGRGeometry map to the axis defined by " +"the CRS definition." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:312 +msgid "Such mapping is given by a new method in OGRSpatialReference" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:318 +msgid "" +"To explain its semantics, imagine that it return 2,-1,3. That is " +"interpreted as:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:321 +msgid "2: the first axis of the CRS maps to the second axis of the data" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:322 +msgid "" +"-1: the second axis of the CRS maps to the first axis of the data, with " +"values negated" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:324 +msgid "3: the third axis of the CRS maps to the third axis of the data" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:326 +msgid "" +"This is similar to the PROJ axisswap operation: " +"`https://proj4.org/operations/conversions/axisswap.html " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:329 +msgid "" +"By default, on a newly create OGRSpatialReference object, " +"GetDataAxisToSRSAxisMapping() returns the identity 1,2[,3], that is, " +"conform to the axis order defined by the authority." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:333 +msgid "" +"As all GDAL and a vast majority of OGR drivers depend on using the \"GIS " +"axis mapping\", a method SetAxisMappingStrategy( " +"OAMS_TRADITIONAL_GIS_ORDER or OAMS_AUTHORITY_COMPLIANT or OAMS_CUSTOM ) " +"is added to make their job of specifying the axis mapping easier;" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:338 +msgid "OAMS_TRADITIONAL_GIS_ORDER means:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:340 +msgid "for geographic 2D CRS," +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:342 +msgid "" +"for Latitude NORTH, Longitude EAST (such as EPSG:4326), " +"GetDataAxisToSRSAxisMapping() returns {2,1}, meaning that the data order " +"is longitude, latitude" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:345 +msgid "for Longitude EAST, Latitude NORTH (such as OGC:CRS84), returns {1,2}" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:348 +msgid "for projected CRS," +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:350 +msgid "for EAST, NORTH (ie most projected CRS), return {1,2}" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:351 +msgid "for NORTH, EAST, return {2,1}" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:352 +msgid "" +"for North Pole CRS, with East/SOUTH, North/SOUTH, such as EPSG:5041 " +"(\"WGS 84 / UPS North (E,N)\"), would return {1,2}" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:354 +msgid "" +"for North Pole CRS, with northing/SOUTH, easting/SOUTH, such as " +"EPSG:32661 (\"WGS 84 / UPS North (N,E)\"), would return {2,1}" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:356 +msgid "similarly for South Pole CRS" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:357 +msgid "for all other cases, return {1,2}" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:359 +msgid "" +"OGRCreateCoordinateTransformation() now honors the data axis to srs axis " +"mapping." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:362 +msgid "" +"Note: contrary to what I indicated in a previous email, gdaltransform " +"behavior is unchanged, since internally the GDALTransform mechanism " +"forces the GIS friendly order." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:366 +msgid "" +"Raster datasets are modified to call " +"SetAxisMappingStrategy(OAMS_TRADITIONAL_GIS_ORDER) on the " +"OGRSpatialReference\\* they return, and assumes it in SetSpatialRef() " +"(assumed and unchecked for now)" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:371 +msgid "" +"Vector layers mostly all call " +"SetAxisMappingStrategy(OAMS_TRADITIONAL_GIS_ORDER) on the " +"OGRSpatialReference\\* returned by GetSpatialRef(). In the case of the " +"GML driver, if the user defines the INVERT_AXIS_ORDER_IF_LAT_LONG open " +"option, axis swapping is not done (as previously) and the " +"AUTHORITY_COMPLIANT strategy is used. ICreateLayer() when receiving a " +"OGRSpatialReference\\* may decide (and most will do it) to change the " +"axis mapping strategy. That is: if it receives a OGRSpatialReference with" +" AUTHORITY_COMPLIANT order, it may decide to switch to " +"TRADITIONAL_GIS_ORDER and GetSpatialRef()::GetDataAxisToSRSAxisMapping() " +"will reflect that. ogr2ogr is modified to do the geometry axis swapping " +"in that case." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:384 +msgid "" +"Related to that change, WKT 1 export now always return the AXIS element, " +"and EPSG:xxxx thus behaves identically to EPSGA:xxxx" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:387 +msgid "" +"So a summary view of this approach is that in the formal SRS definition, " +"we no longer do derogations regarding axis order, but we add an " +"additional interface to describe how we actually make our match match " +"with the SRS definition." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:393 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:158 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:432 +msgid "Driver changes" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:395 +msgid "" +"Raster drivers that returned / accepted a SRS as a WKT string through the" +" GetProjectionRef(), SetProjection(), GetGCPProjection() and SetGCPs() " +"methods have been upgraded to use the new virtual methods, in most cases " +"by using the compatibility layer." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:400 +msgid "" +"The GDALPamDataset (PAM .aux.xml files) and the GDAL VRT drivers have " +"been fully upgraded to support the new interfaces, and " +"serialize/deserialize the data axis to SRS axis mapping values." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:404 +msgid "" +"The GeoPackage driver now fully supports the official \"gpkg_crs_wkt\" " +"extension used to store WKT 2 string definitions in the " +"gpkg_spatial_ref_sys table. The driver attempts at not using the " +"extension when SRS can be encoded as WKT1 strings, and will automatically" +" add the \"definition_12_063\" column to an existing gpkg_spatial_ref_sys" +" table if a SRS requiring WKT2 (typically a Geographic 3D CRS) is " +"inserted." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:415 +msgid "" +"gdalinfo and ogrinfo reports the data axis to CRS axis mapping whenever a" +" CRS is reported. They will also output WKT2_2018 by default, unless " +"\"-wkt_format wkt1\" is specified." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:447 +msgid "" +"gdalwarp, ogr2ogr and gdaltransform have gained a -ct switch that can be " +"used by advanced users to specify a coordinate operation, either as a " +"PROJ string (generally a +proj=pipeline), or a WKT coordinate " +"operation/concatenated operation, as explained in the above " +"\"OGRCoordinateTransformation changes\" paragraph. Note: the pipeline " +"must take into account the axis order of the CRS, even if the underlying " +"raster/vector drivers use the \"GIS friendly\" order. For example " +"\"+proj=pipeline +step +proj=axisswap +order=2,1 +step +proj=unitconvert " +"+xy_in=deg +xy_out=rad +step +proj=utm +zone=31 +ellps=WGS84\" when " +"transforming from EPSG:4326 to EPSG:32631." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:458 +msgid "" +"gdalsrsinfo is enhanced to be able to specify the 2 new supported WKT " +"variants: WKT2_2015 and WKT2_2018. It will default to outputting " +"WKT2_2018" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:463 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:184 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:403 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:184 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:192 +msgid "SWIG binding changes" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:465 +msgid "" +"The enhanced ExportToWkt() and OGRCoordinateTransformation methods are " +"available through SWIG bindings. May require additional typemaps for non-" +"Python languages (particularly for the support of 4D X,Y,Z,time " +"coordinates)" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:473 +msgid "" +"This work is intended to be *mostly* backward compatible, yet inevitable " +"differences will be found. For example the WKT 1 and PROJ string export " +"has been completely rewritten in PROJ, and so while being hopefully " +"equivalent to what GDAL 2.4 or earlier generated, this is not strictly " +"identical: number of significant digits, order of PROJ parameters, " +"rounding, etc etc..." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:480 +msgid "MIGRATION_GUIDE.TXT has been updated to reflect some differences:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:482 +msgid "OSRImportFromEPSG() takes into account official axis order." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:483 +msgid "" +"removal of OPTGetProjectionMethods(), OPTGetParameterList() and " +"OPTGetParameterInfo() No equivalent." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:485 +msgid "" +"removal of OSRFixup() and OSRFixupOrdering(): no longer needed since " +"objects constructed are always valid" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:487 +msgid "" +"removal of OSRStripCTParms(). Use OSRExportToWktEx() instead with the " +"FORMAT=SQSQL option" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:489 +msgid "exportToWkt() outputs AXIS nodes" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:490 +msgid "" +"OSRIsSame(): now takes into account data axis to CRS axis mapping, unless" +" IGNORE_DATA_AXIS_TO_SRS_AXIS_MAPPING=YES is set as an option to " +"OSRIsSameEx()" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:493 +msgid "" +"ogr_srs_api.h: SRS_WKT_WGS84 macro is no longer declared by default since" +" WKT without AXIS is too ambiguous. Preferred remediation: use " +"SRS_WKT_WGS84_LAT_LONG. Or #define USE_DEPRECATED_SRS_WKT_WGS84 before " +"including ogr_srs_api.h" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:498 +msgid "" +"Out-of-tree raster drivers will be impacted by the introduction of the " +"new virtual methods GetSpatialRef(), SetSpatialRef(), GetGCPSpatialRef() " +"and SetGCPs(..., const OGRSpatialReference\\* poSRS), and the removal of " +"their older equivalents using WKT strings instead of a " +"OGRSpatialReference\\* instance." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:507 +msgid "" +"New methods have been documented, and documentation of existing methods " +"has been changed when appropriate during the development. That said, a " +"more thorough pass will be needed. The tutorials will also have to be " +"updated." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:515 +msgid "" +"The autotest suite has been adapted in a number of places since the " +"expected results have changed for a number of reasons (AXIS node exported" +" in WKT, differences in WKT and PROJ string generation). New tests have " +"been added for the new capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:520 +msgid "" +"It should be noted that autotest not necessarily checks everything, and " +"issues have been discovered and fixed through manual testing. The " +"introduction of the \"data axis to CRS axis mapping\" concept is also " +"quite error prone, as it requires setting the OAMS_TRADITIONAL_GIS_ORDER " +"strategy in a lot of different places." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:526 +msgid "" +"So users and developers are kindly invited to thoroughly test GDAL once " +"this work has landed in master." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:532 +msgid "" +"Done by Even Rouault, `Spatialys `__. Available" +" per `PR 1185 `__ Funded through" +" `gdalbarn `__ sponsoring." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:536 +msgid "" +"While it is provided as a multiple commit for \"\"\"easier\"\"\" review, " +"it will be probably squashed in a single commit for inclusion in master, " +"as intermediate steps are not all buildable, due to PROJ symbol renames " +"having occurred during the development, which would break bisectability." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:544 +msgid "Adopted with +1 from PSC members HowardB, JukkaR, DanielM and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:547 +msgid "Modifications" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:549 +msgid "2019-May-02: change mentions of GDAL 2.5 to GDAL 3.0" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:5 +msgid "RFC 74: Migrate gdal.org to RTD-style Sphinx infrastructure" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:10 +msgid "howard@hobu.co" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:11 +msgid "2019-May-19" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:12 +msgid "*Adopted*" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:18 +msgid "" +"The document proposes migrating the GDAL documentation from a Doxygen to " +"`Sphinx `__ in `ReadTheDocs " +"`__ format." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:25 +msgid "" +"Casual contribution to the GDAL documentation is challenging. Wiki-style " +"contribution is possible through the Trac instance, but that requires " +"getting an OSGeo login, which is a high bar, and the Trac information is " +"disconnected from the primary documentation. Other projects such as PROJ " +"and `MapServer `__ have seen significant uptick in" +" contributed documentation by adopting Sphinx-based systems, and we hope " +"the adoption of this approach for GDAL will ignite a renaissance of " +"documentation contribution as it did for those projects." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:34 +msgid "" +"The current approach has some significant deficiencies that have not been" +" overcome by waiting for new versions of Doxygen to arrive. These " +"include:" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:38 +msgid "" +"The Doxygen build buries the source of the documentation deep into the " +"source tree, which makes it hard to find where to properly add " +"information." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:41 +msgid "" +"The structure of the website is indirect from the source code that " +"creates it." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:43 +msgid "" +"New features such as convenient mobile-friendly styling, alternative " +"serializations such as PDF, and tighter API and user-level documentation " +"integration are not within easy reach." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:46 +msgid "" +"Editing of raw HTML means that convenient output of other serialization " +"types, such as PDF, Windows Compiled Help, or manpage output is " +"challenging." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:53 +msgid "" +"The GDAL team will refactor the GDAL.org website to be based on Sphinx " +"with the following properties:" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:56 +msgid "Convert the bulk of the existing documentation to reStructuredText" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:57 +msgid "" +"Adapt the `ReadTheDocs theme `__" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:59 +msgid "" +"Apply an \"Edit this Page on GitHub\" link to every page on the site for " +"convenient contribution" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:61 +msgid "" +"Utilize `GitHub Pages `__ to host gdal.org, " +"with updates being regenerated and committed to a repository by `Azure " +"Pipelines `__ continuous " +"integration." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:66 +msgid "" +"Output a PDF serialization of the website for documentation version " +"posterity." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:70 +msgid "Considerations" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:72 +msgid "" +"Numerous hard links to driver pages exist in source code. Care must be " +"taken to attempt to preserve these links as well as possible with " +"redirects to adapt to any new organization." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:75 +msgid "" +"Porting of existing Trac content to the new data structure will allow " +"decommission of that piece of infrastructure. Significant content porting" +" investment may be required to achieve this." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:78 +msgid "" +"Doxygen API-style documents are still valuable, and we propose to keep a " +"rendering of them at ``/doxygen`` for users who wish to continue with " +"that approach. Internal API documentation will continue to use Doxygen, " +"and it will be reflected into the Sphinx website using the Breathe " +"capability." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:83 +msgid "" +"Initial content organization will attempt to mimic the existing website " +"as well as can be achieved, but no requirement to maintain adherence to " +"the previous structure is required if other organization approaches are " +"more convenient given the features and capabilities of Sphinx." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:88 +msgid "" +"Existing translations will not be ported. Adaptation and continuation of " +"porting of translations is beyond the scope of this RFC, but there are " +"capabilities for managing translations in Sphinx (MapServer.org provides " +"an excellent example), and follow-on contributors can keep moving forward" +" with the architecture once the initial effort is complete." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:94 +msgid "" +"Content may be missed during the transition. Please file tickets in " +"GitHub for any items that became more difficult to find or are gone after" +" the transition." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:99 +msgid "Logistics" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:101 +msgid "" +"A current example of the site lives at `https://gdal.dev " +"`__ This example is set to noindex. Once the RFC is " +"passed, adaptation of the infrastructure that builds it will be migrated " +"to `https://gdal.org `__ and the example website will " +"be completely decommissioned. Currently, `https://github.com/hobu/gdal " +"`__ ``doc-sprint`` branch is the fork that " +"drives this content. It will be squash-merged to the main repository at " +"the passing of the RFC." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:112 +msgid "`issue #1204 `__." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:113 +msgid "" +"`2019 OSGeo Community Code Sprint " +"`__" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:119 +msgid "+1 from KurtS, HowardB, DanielM, NormanB, JukkaR and EvenR." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:5 +msgid "RFC 75: Multidimensional arrays" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:10 +msgid "2019-May-24" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:11 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:11 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:11 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:11 +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:11 +msgid "Last updated:" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:11 +msgid "2019-Jul-22" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:12 +msgid "Implemented in GDAL 3.1" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:18 +msgid "" +"This document describes the addition of read/write support for " +"multidimensional arrays, in particular of dimension 3 or above, in GDAL " +"core and a few select drivers." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:24 +msgid "" +"Multidimensional arrays (also known as hypercubes) are a way of mоdelling" +" spatio-temporal (time series of 2D raster) or spatio-vertical-temporal " +"(2D + Z dimension + time dimension) data which are becoming increasingly " +"more available. GDAL current raster model is however strongly 2D " +"oriented. A number of drivers, such as netCDF, HDF4, HDF5, work around " +"that limitation by using raster bands or subdatasets to expose muliple 2D" +" slices of what is intrinsically a N>2 Multidimensional dataset. It is " +"desirable to have a proper API, and driver support, to be able to expose " +"those multidimensional arrays as such, and be able to perform slice and " +"trim operations on them." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:34 +msgid "" +"That topic had already been discussed in the past, in particular in this " +"`mailing list thread `_" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:40 +msgid "" +"A lot of existing GDAL raster API are strongly 2D oriented. Rather than " +"upgrading all those API, and driver code, to be ready for N arbitrary " +"dimensions, which would be a enormous effort for the benefit of only a " +"small fraction of drivers, we propose to add a new dedicated API to " +"support multidimensional arrays. We also want to support hierarchical " +"structure of data as found in the `HDF5 format and data model " +"`_. This model can " +"encompass the needs of other formats/drivers that have multidimensional " +"capabilities such as HDF4, netCDF, GRIB, WCS. Therefore the proposed API " +"will be strongly inspired by the API of the HDF5 library itself." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:51 +msgid "Data model" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:52 +msgid "" +"The data model is described in: " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/user/multidim_raster_data_model.rst" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:58 +msgid "" +"New classes and methods will be added. See " +"https://github.com/rouault/gdal/blob/rfc75/gdal/gcore/gdal_priv.h#L1715" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:61 +msgid "" +"A new driver capability will be added for drivers supporting " +"multidimensional rasters:" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:69 +msgid "" +"A new open flag, ``GDAL_OF_MULTIDIM_RASTER``, for :cpp:func:`GDALOpenEx` " +"will be added. When this is specified, drivers supporting " +"multidimensional raster will return a root GDALGroup. Otherwise their " +"current traditional 2D mode will still be used." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:74 +msgid "" +"New creation options metadata items are added to documents " +"multidimensional dataset, group, dimension, array and attribute creation " +"options." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:104 +msgid "Examples with the netCDF driver:" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:154 +msgid "" +"All C++ methods are mapped to the C API. See " +"https://github.com/rouault/gdal/blob/rfc75/gdal/gcore/gdal.h#L1397" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:160 +msgid "The MEM driver will implement read and write support." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:161 +msgid "" +"The VRT driver will allow extraction of 2D slices from multidimensional " +"drivers to 2D/classic drivers, as well as " +"multidimensional->multidimensional slicing/trimming" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:164 +msgid "The netCDF driver will implement read and write support." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:165 +msgid "The HDF4 and HDF5 drivers will implement read support." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:166 +msgid "" +"The GRIB driver will implement read support (exposing X,Y,Time arrays for" +" GRIB messages only differing by timestamp)" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:170 +msgid "New Utilities" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:172 +msgid "" +"A new gdalmdiminfo utility is added to report the hierarchical structure " +"and content. Its output format is JSON. See " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/programs/gdalmdiminfo.rst" +" for its documentation." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:176 +msgid "" +"A new gdalmdimtranslate utility is added to convert multidimensional " +"raster between different formats, and/or can perform selective conversion" +" of specific arrays and groups, and/or subsetting operations. It can also" +" do extraction of 2D slices from multidimensional drivers to 2D/classic " +"drivers. See " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/programs/gdalmdimtranslate.rst" +" for its documentation." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:186 +msgid "" +"The C API is mapped to the SWIG bindings. The scope is complete for the " +"Python bindings. Other languages would need to add missing typemaps, but " +"this is not in the scope of the work of this RFC. For Python bindings, " +"NumPy integration is done." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:194 +msgid "" +"This is intended to be a preliminary work on that topic. While the aim is" +" for it to be be usable for the defined scope, it will probably require " +"future enhancements to fill functional and/or performance gaps." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:198 +msgid "No block cache mechanism (not sure this is needed)" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:199 +msgid "No sub-pixel requests, or non-nearest subsampling" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:200 +msgid "" +"Upgrade of WCS driver or other drivers with potential multidimensional " +"capabilities are not part of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:202 +msgid "SWIG bindings: full scope only for Python bindings." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:207 +msgid "No backward incompatibility. Only API and utility additions." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:212 +msgid "" +"Data model: " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/user/multidim_raster_data_model.rst" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:213 +msgid "" +"API tutorial: " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/tutorials/multidimensional_api_tut.rst" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:214 +msgid "" +"gdalmdiminfo: " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/programs/gdalmdiminfo.rst" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:215 +msgid "" +"gdalmdimtranslate: " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/programs/gdalmdimtranslate.rst" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:216 +msgid "" +"VRT driver: " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/drivers/raster/vrt_multidimensional.rst" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:221 +msgid "" +"The gdalautotest suite is extended to test the modified drivers and the " +"new utilities." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:227 +msgid "" +"The implementation will be done by Even Rouault. A preliminary " +"implementation is available at https://github.com/OSGeo/gdal/pull/1704" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:234 +msgid "+1 from HowardB, NormanB and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:5 +msgid "RFC 76: OGR Python drivers" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:10 +msgid "2019-Nov-5" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:11 +msgid "2019-Nov-15" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:12 +msgid "Adopted, implemented in GDAL 3.1" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:18 +msgid "This RFC adds the capability to write OGR/vector drivers in Python." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:23 +msgid "" +"For some use cases that do not require lighting speed, or to deal with " +"very niche formats (possibly in house format), it might be faster and " +"more efficient to write a vector driver in Python rather than a GDAL C++ " +"driver as currently required, or an ad-hoc converter." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:30 +msgid "" +"QGIS has now a way to create Python-based providers such as in " +"https://github.com/qgis/QGIS/blob/master/tests/src/python/provider_python.py" +" Having a way to do in GDAL itself also allows the rest of GDAL/OGR based" +" tools to use the OGR Python driver." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:36 +msgid "How does that work ?" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:39 +msgid "Driver registration" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:41 +msgid "" +"The driver registration mechanism is extended to look for .py scripts in " +"a dedicated directory:" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:44 +msgid "" +"the directory pointed by the :config:`GDAL_PYTHON_DRIVER_PATH` " +"configuration option (there may be several paths separated by `:` on Unix" +" or `;` on Windows)" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:46 +msgid "" +"if not defined, the directory pointed by the :config:`GDAL_DRIVER_PATH` " +"configuration option." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:48 +msgid "" +"if not defined, in the directory (hardcoded at compilation time on Unix " +"builds) where native plugins are located." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:51 +msgid "Those Python script must set in their first lines at least 2 directives:" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:53 +msgid "``# gdal: DRIVER_NAME = \"short_name\"``" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:54 +msgid "" +"``# gdal: DRIVER_SUPPORTED_API_VERSION = 1`` . Currently only 1 " +"supported. If the interface changed in a backward incompatible way, we " +"would increment internally the supported API version number. This item " +"enables us to check if we are able to \"safely\" load a Python driver. If" +" a Python driver would support several API versions (not clear if that's " +"really possible at that point), it might use an array syntax to indicate " +"that, like ``[1,2]``" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:60 +msgid "``# gdal: DRIVER_DCAP_VECTOR = \"YES\"``" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:61 +msgid "``# gdal: DRIVER_DMD_LONGNAME = \"my super plugin\"``" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:63 +msgid "" +"Optional metadata such as ``# gdal: DRIVER_DMD_EXTENSIONS`` or ``# gdal: " +"DRIVER_DMD_HELPTOPIC`` can be defined (basically, any driver metadata key" +" string prefixed by ``# gdal: DRIVER_``" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:67 +msgid "" +"These directives will be parsed in a pure textual way, without invocation" +" of the Python interpreter, both for efficiency consideration and also " +"because we want to delay the research or launch of the Python interpreter" +" as much as possible (the typical use case if GDAL used by QGIS: we want " +"to make sure that QGIS has itself started Python, to reuse that Python " +"interpreter)" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:73 +msgid "" +"From the short metadata, the driver registration code can instantiate " +"GDALDriver C++ objects. When the Identify() or Open() method is invoked " +"on that object, the C++ code will:" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:77 +msgid "" +"if not already done, find Python symbols, or start Python (see below " +"paragraph for more details)" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:79 +msgid "if not already done, load the .py file as a Python module" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:80 +msgid "" +"if not already done, instantiate an instance of the Python class of the " +"module deriving from ``gdal_python_driver.BaseDriver``" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:82 +msgid "" +"call the ``identify`` and ``open`` method depending on the originated " +"API call." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:84 +msgid "" +"The ``open`` method will return a Python ``BaseDataset`` object with " +"required and optional methods that will be invoked by the corresponding " +"GDAL API calls. And likewise for the ``BaseLayer`` object. See the " +"example_." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:89 +msgid "Connection with the Python interpreter" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:91 +msgid "" +"The logic will be shared with the VRT pixel functions written in Python " +"functionality It relies on runtime linking to the Python symbols already " +"available in the process (for example the python executable or a binary " +"embedding Python and using GDAL, such as QGIS), or loading of the Python " +"library in case no Python symbols are found, rather than compile time " +"linking. The reason is that we do not know in advance with which Python " +"version GDAL can potentially be linked, and we do not want " +"gdal.so/gdal.dll to be explicitly linked with a particular Python " +"library." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:100 +msgid "This is both embedding and extending Python." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:102 +msgid "The steps are:" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:104 +msgid "" +"through dlopen() + dlsym() on Unix and " +"EnumProcessModules()+GetProcAddress() on Windows, look for Python " +"symbols. If found, use it. This is for example the case if GDAL is used " +"from a Python module (GDAL Python bindings, rasterio, etc.) or an " +"application like QGIS that starts a Python interpreter." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:108 +msgid "" +"otherwise, look for the PYTHONSO environment variable that should point " +"to a pythonX.Y[...].so/.dll" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:110 +msgid "" +"otherwise, look for the python binary in the path and try to identify the" +" correspond Python .so/.dll" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:112 +msgid "" +"otherwise, try to load with dlopen()/LoadLibrary() well-known names of " +"Python .so/.dll" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:116 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:173 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:187 +msgid "Impacts on GDAL core" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:118 +msgid "" +"They are minimal. The GDALAllRegister() method has an added call to " +"GDALDriverManager::AutoLoadPythonDrivers() that implements the above " +"mentioned logic. The GDALDriver class has been extended to support a new " +"function pointer, IdentifyEx(), which is used by the C++ shim that loads " +"the Python code." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:127 +msgid "" +"This extended IdentifyEx() function pointer, which adds the GDALDriver* " +"argument, is used in priority by GDALIdentify() and GDALOpen() methods. " +"The need for that is purely boring. For normal C++ drivers, there is no " +"need to pass the driver, as there is a one-to-one correspondence between " +"a driver and the function that implements the driver. But for the Python " +"driver, there is a single C++ method that does the interface with the " +"Python Identify() method of several Python drivers, hence the need of a " +"GDALDriver* argument to forward the call to the appropriate driver." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:139 +msgid "Example of such a driver" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:141 +msgid "" +"Note that the prefixing by the driver name in the connection string is " +"absolutely not a requirement, but something specific to this particular " +"driver which is a bit artificial. The CityJSON driver mentioned below " +"does not need it." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:356 +msgid "Other examples:" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:358 +msgid "" +"a PASSTHROUGH driver that forwards calls to the GDAL SWIG Python API: " +"https://github.com/OSGeo/gdal/blob/master/examples/pydrivers/ogr_PASSTHROUGH.py" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:360 +msgid "" +"a driver implemented a simple parsing of `CityJSON " +"`_: " +"https://github.com/OSGeo/gdal/blob/master/examples/pydrivers/ogr_CityJSON.py" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:364 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:179 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:129 +msgid "Limitations and scope" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:366 +msgid "Vector and read-only for now. This could later be extended of course." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:368 +msgid "" +"No connection between the Python code of the plugin and the OGR Python " +"API that is built on top of SWIG. This does not appear to be doable in a " +"reasonable way. Nothing prevents people from using the GDAL/OGR/OSR " +"Python API but the objects exchanged between the OGR core and the Python " +"code will not be OGR Python SWIG objects. A typical example is that a " +"plugin will return its CRS as a string (WKT, PROJSON, or deprecated " +"PROJ.4 string), but not as a osgeo.osr.SpatialReference object. But it is" +" possible to use the osgeo.osr.SpatialReference API to generate this WKT " +"string." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:378 +msgid "" +"This RFC does not try to cover the management of Python dependencies. It " +"is up to the user to do the needed \"pip install\" or whatever Python " +"package management solution it uses." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:382 +msgid "" +"The Python \"Global Interpreter Lock\" is held in the Python drivers, as " +"required for safe use of Python. Consequently scaling of such drivers is " +"limited." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:385 +msgid "" +"Given the above restrictions, this will remain an \"experimental\" " +"feature and the GDAL project will not accept such Python drivers to be " +"included in the GDAL repository. This is similar to the situation of the " +"QGIS project that allows Python plugins outside of the main QGIS " +"repository. If a QGIS plugin want to be moved into the main repository, " +"it has to be converted to C++. The rationale for this is that the " +"correctness of the Python code can mostly be checked at runtime, whereas " +"C++ benefits from static analysis (at compile time, and other checkers). " +"In the context of GDAL, this rationale also applies. GDAL drivers are " +"also stress-tested by the OSS Fuzz infrastructure, and that requires them" +" to be written in C++." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:396 +msgid "" +"The interface between the C++ and Python code might break between GDAL " +"feature releases. In that case we will increment the expected API version" +" number to avoid loading incompatible Python drivers. We will likely not " +"make any effort to be able to deal with plugins of incompatible " +"(previous) API version." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:408 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:191 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:197 +msgid "Security implications" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:410 +msgid "" +"Similar to the existing native code plugin mechanism of GDAL. If the user" +" defines the GDAL_PYTHON_DRIVER_PATH environment variable or " +"GDAL_DRIVER_PATH, annd put .py scripts in them (or in " +"{prefix}/lib/gdalplugins/python as a fallback), they will be executed." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:415 +msgid "" +"However, opening a .py file with GDALOpen() or similar mechanisms will " +"not lead to its execution, so this is safe for normal GDAL usage." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:418 +msgid "" +"The GDAL_NO_AUTOLOAD compile time #define, already used to disable " +"loading of native plugins, is also honoured to disable the loading of " +"Python plugins." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:422 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:197 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:202 +msgid "Performance impact" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:424 +msgid "" +"If no .py script exists in the researched location, the performance " +"impact on GDALAllRegister() should be within the noise." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:430 +msgid "No backward incompatibility. Only functionality addition." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:435 +msgid "" +"A tutorial will be added to explain how to write such a Python driver: " +"https://github.com/rouault/gdal/blob/pythondrivers/gdal/doc/source/tutorials/vector_python_driver.rst" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:441 +msgid "" +"The gdalautotest suite will be extended with the above test Python " +"driver, and a few error cases: " +"https://github.com/rouault/gdal/blob/pythondrivers/autotest/ogr/ogr_pythondrivers.py" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:446 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:216 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:217 +msgid "Previous discussions" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:448 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:218 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:219 +msgid "This topic has been discussed in the past in :" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:450 +msgid "https://lists.osgeo.org/pipermail/gdal-dev/2017-April/thread.html#46526" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:451 +msgid "https://lists.osgeo.org/pipermail/gdal-dev/2018-November/thread.html#49294" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:456 +msgid "" +"A candidate implementation is available at in " +"https://github.com/rouault/gdal/tree/pythondrivers" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:459 +msgid "https://github.com/OSGeo/gdal/compare/master...rouault:pythondrivers" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:464 +msgid "+1 from EvenR, JukkaR, MateuzL, DanielM" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:465 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:238 +msgid "-0 from SeanG" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:466 +msgid "+0 from HowardB" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:469 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:238 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:241 +msgid "Credits" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:471 +msgid "Sponsored by OpenGeoGroep" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:5 +msgid "RFC 77: Drop Python 2 support in favour of Python 3.6" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:8 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:8 +msgid "Idan Miara" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:9 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:9 +msgid "idan@miara.com" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:10 +msgid "2020-Nov-3" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:11 +msgid "2020-Nov-29" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:12 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:12 +msgid "Adopted, implemented in GDAL 3.3" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:18 +msgid "" +"This RFC drops Python 2 support and sets Python 3.6 as the new minimum " +"supported Python version." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:23 +msgid "" +"Currently GDAL Python bindings support Python 2.7 and Python 3 (so only " +"the common between the two). Python 2 is at End Of Life, and is no longer" +" supported since the January 2020. https://www.python.org/doc/sunset-" +"python-2/" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:27 +msgid "" +"\"We did not want to hurt the people using Python 2. So, in 2008, we " +"announced that we would sunset Python 2 in 2015, and asked people to " +"upgrade before then. Some did, but many did not. So, in 2014, we extended" +" that sunset till 2020.\"" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:30 +msgid "" +"While keeping Python 2.7 support might serve those who didn't upgrade " +"their code to Python 3 in the 12 year transition period, This PR suggests" +" that the time has come and the benefits of dropping Python 2 support " +"outnumber the drawbacks. Virtually all supported OS and relevant programs" +" already use Python 3. Moreover, most of the related projects that " +"usually is used with GDAL already dropped Python 2 support (as can be " +"seen below). It makes sense that people who didn't upgrade their code in " +"12 years are still using a much older version of GDAL anyway..." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:36 +msgid "" +"The drawbacks of keeping Python 2 support puts unnecessary maintenance " +"burden on the GDAL maintainers, As maintainers need to make sure their " +"new code is backwards compatible with Python 2. Furthermore, many " +"important features that added in Python 3 cannot be used in GDAL to " +"maintain backwards compatibility with Python 2." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:41 +msgid "Related projects that dropped Python 2 support:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:43 +msgid "QGIS since v3.0 - February 2018. (now supports Python 3.7)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:45 +msgid "" +"https://www.qgis.org/en/site/forusers/visualchangelog30/index.html " +"https://qgis.org/api/api_break.html" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:48 +msgid "GRASS GIS since v7.8 - September 2019 (now supports Python 3.7)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:50 +msgid "https://trac.osgeo.org/grass/wiki/Python3Support" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:52 +msgid "pyproj since v2.3 - August 2019 (now supports Python 3.5-3.7)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:54 +msgid "https://pyproj4.github.io/pyproj/stable/history.html" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:56 +msgid "numpy since v1.19 - June 2020 (now supports Python Python 3.6-3.8)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:58 +msgid "https://numpy.org/devdocs/release/1.19.0-notes.html" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:60 +msgid "RasterIO since v1.1 - October 2019 (now supports Python 3.6)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:62 +msgid "" +"https://sgillies.net/2019/10/10/rasterio-1-1-0.html " +"https://github.com/mapbox/rasterio/issues/1813" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:66 +msgid "Python 3 version status:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:68 +msgid "" +"Python 3.5 (Released: Sep 2015) is End Of Life. Many related projects " +"already dropped support of it." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:69 +msgid "" +"Python 3.6 (Released: Dec 2016) will be End Of Life on Dec 2021. Python " +"3.6 brings many important features." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:70 +msgid "" +"Python 3.7 (Released: Jun 2018) will be End Of Life on Jun 2023. Python " +"3.7 is already widely adopted and supported by all the related projects " +"listed above." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:71 +msgid "" +"Python 3.8 (Released: Oct 2019) will be End Of Life on Oct 2024. Python " +"3.8 is too new to be set as the minimum supported version." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:73 +#, python-format +msgid "https://endoflife.date/python#:~:text=The%20support%20for%20Python%202.7,dropping%20support%20for%20Python%202.7." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:76 +msgid "Python 3 OS Support:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:79 +msgid "Linux:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:82 +msgid "Distribution" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:82 +msgid "Release date" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:82 +msgid "End Of Life" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:82 +msgid "Python Version" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:83 +msgid "Ubuntu 16.04 Xenial LTS" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:83 +msgid "April 2016" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:83 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:85 +msgid "April 2021" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:83 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:86 +msgid "Python 3.5" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:84 +msgid "Ubuntu 18.04 Bionic LTS" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:84 +msgid "April 2018" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:84 +msgid "April 2023" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:84 +msgid "Python 3.6 (3.7 in universe)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:85 +msgid "Ubuntu 20.04 Xenial LTS" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:85 +msgid "April 2020" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:85 +msgid "Python 3.8" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:86 +msgid "Debian 9.0 Stretch LTS" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:86 +msgid "June 2017" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:86 +msgid "July 2022" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:87 +msgid "Debian 10.0 Buster LTS" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:87 +msgid "July 2019" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:87 +msgid "~2022" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:87 +msgid "Python 3.7" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:88 +msgid "Centos/RHEL 8" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:88 +msgid "September 2019" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:88 +msgid "?" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:88 +msgid "Python 3.6 (?)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:89 +msgid "Amazon Linux" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:89 +msgid "December 2021" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:89 +msgid "Python 3.6" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:92 +msgid "https://wiki.python.org/moin/Python3LinuxDistroPortingStatus" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:96 +msgid "Windows:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:98 +msgid "Conda: Python 3.6-3.9" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:99 +msgid "OSGeo4W: Python 3.7" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:100 +msgid "gisinternals: Python 2.7, 3.4-3.7" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:103 +msgid "MacOS:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:105 +msgid "" +"It appears the even though Python 2.7 is preinstalled on Mac OS X, Python" +" 3.5-3.9 can be installed alongside Python 2 on Mac OS X 10.8 (Released: " +"July 2012) and newer." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:108 +msgid "https://docs.python.org/3.6/using/mac.html." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:111 +msgid "Which version should be the new minimum version ?" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:113 +msgid "" +"This RFC suggest the new minimum supported Python version should be 3.6 " +"for the following reasons:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:115 +msgid "Python < 3.6 is End of Life." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:120 +msgid "" +"Long list of great new features that were introduced in Python 3.6, " +"Several of which are immediately useful to simplify code or improve " +"testing:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:117 +msgid "f-strings" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:118 +msgid "builtin pathlib" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:119 +msgid "underscores in numeric literals" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:120 +msgid "type annotations" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:121 +msgid "malloc debugging" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:122 +msgid "Python 3.6 is supported out of the box in virtually every relevant OS." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:123 +msgid "" +"Python 3.6 is probably the safest choice for now in respect to other " +"related projects." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:124 +msgid "" +"Python 3.7 (and newer) isn't available seamlessly in some popular LTS " +"Linux distributions." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:125 +msgid "" +"We want to make the transition as smooth and easy as possible. Setting " +"the minimum to Python 3.7 might make the transition harder for the CI " +"because of the above reason." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:126 +msgid "" +"Dropping Python 3.6 in favour of Python 3.7 or newer in future versions " +"shouldn't be as hard as this drop (see next section for a suggested " +"approach)." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:129 +msgid "GDAL Release cycle and regular Python version dropping" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:131 +msgid "" +"When releasing GDAL 3.1.0, Even Rouault suggested GDAL would use fixed " +"release cycles of 6 months between major versions:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:133 +msgid "" +"http://osgeo-org.1560.x6.nabble.com/gdal-dev-Reconsidering-release-cycle-" +"length-td5436163.html#a5436242" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:135 +msgid "" +"Projecting from that suggestion, GDAL 3.3.0 should be released around " +"April-May 2021." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:137 +msgid "" +"We could potentially synchronize with NEP 29 - Recommend Python and Numpy" +" version support as a community policy standard. Which suggests when to " +"drop each Python version." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:141 +msgid "https://numpy.org/neps/nep-0029-deprecation_policy.html" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:143 +msgid "" +"NEP 29 suggests to drop support for Python 3.6 support on Jun 23, 2020 " +"(in favour of Python 3.7)." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:145 +msgid "" +"We could potentially discuss similar/more conservative approaches and " +"delay each drop by a few more months, or only drop Python versions that " +"have reached End Of Life (As of today, Python < 3.6 have reached End Of " +"Life). Further discussion on the matter of dropping other Python versions" +" is a subject for another RFC." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:152 +msgid "" +"Currently, GDAL Python code itself is compatible with Python 2 and Python" +" 3. Once this PR is accepted, GDAL 3.3.0 would not be compatible with " +"Python 2. Thus any \"Python 2 only\" code that uses GDAL would need to be" +" upgraded to Python 3 and at the same time the respective Python " +"interpreter would need to be upgraded to a supported Python version." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:159 +msgid "Will GDAL 3.2 be a LTS?" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:161 +msgid "" +"Currently - No. So far, nobody has stepped up to make a LTS, So there " +"won't be one unless someone takes it up upon themselves or raise funds to" +" make it happen. GDAL only provide bugfix releases of the current stable " +"branch for 6 months." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:166 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:181 +msgid "CI Impacts:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:168 +msgid "" +"Impacts on our CI should be analyzed. It seems that all our CI builds use" +" Python 2.7 or 3.5, so all of them would need to be adjusted. In " +"particular, builds that use older Linux distributions would need to be " +"upgraded." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:175 +msgid "" +"There should be no impacts on GDAL core, As the Python bindings are " +"generated by SWIG on top of the binary form of GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:181 +msgid "" +"The scope of this RFC should be the GDAL Python code alone. There " +"shouldn't be effect on any other language supported by GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:186 +msgid "" +"To begin with, the SWIG Python bindings already support Python 3.6. " +"Dropping Python 2 support might allow us to use a newer SWIG version or " +"to make some improvements to the bindings, but it doesn't have to be in " +"the first step." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:193 +msgid "" +"Python 3.6 is the minimum Python version that is not End Of Life, thus " +"still receiving security updates." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:199 +msgid "" +"There might be some performance gain for this upgrade for some uses as " +"there were many performance improvements between Python 2.7-3.6. The " +"scope of the improvements could be limited because most of GDAL Python " +"code is a thin wrapper around the C++ code." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:205 +msgid "" +"The GDAL Python documentation is generated automatically in should " +"already support Python 3. If there are sections in the documentation that" +" are Python 2 specific, they should be removed or refactored." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:211 +msgid "" +"While upgrading the CI, Python 2 tests should be removed or upgraded. A " +"simple test that fails on Python < 3.6 should be added. No any additional" +" tests should be needed." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:220 +msgid "https://github.com/OSGeo/gdal/issues/3114" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:221 +msgid "https://github.com/OSGeo/gdal/pull/3142" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:224 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:224 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:86 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:415 +msgid "Related PRs:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:226 +msgid "" +"Adding a deprecation warning if running a Python version that is known to" +" be unsupported in the next GDAL version:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:228 +msgid "https://github.com/OSGeo/gdal/pull/3165" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:233 +msgid "https://lists.osgeo.org/pipermail/gdal-dev/2020-November/053039.html" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:235 +msgid "+1 from EvenR, HowardB, KurtS, JukkaR, DanielM" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:240 +msgid "implemented by Even Rouault, Robert Coup and Idan Miara" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:5 +msgid "RFC 78: gdal-utils package" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:10 +msgid "2020-Dec-3" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:11 +msgid "2021-March-26" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:18 +msgid "" +"This RFC suggests to put all the GDAL python modules (formly scripts), " +"except from the GDAL core SWIG bindings, into their own distribution on " +"pypi. The GDAL python sub-package `osgeo.utils` (introduced in GDAL 3.2) " +"would be renamed into a package named `osgeo_utils`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:22 +msgid "" +"The standalone python scripts from GDAL <= 3.1 were transformed to " +"`osgeo.utils` in GDAL 3.2. For backwards compatibility these scripts " +"still exist and function as tiny wrappers around the python modules. " +"Users of these scripts would not be effected from this RFC as the scripts" +" would continue to function in GDAL 3.3 in the same way as in GDAL <= " +"3.2." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:27 +msgid "" +"To allow maximum backwards compatibility, The `osgeo` package (which " +"includes the GDAL core SWIG bindings) and the `osgeo_utils` package will " +"continue to be distributed in a single `sdist` named `gdal` in `pypi`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:30 +msgid "" +"In addition, a new pure python `wheel` distribution named `gdal-utils` " +"will be available in `pypi` under the name `gdal-utils`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:33 +msgid "" +"This will allow users who wish to upgrade the utils without upgrading the" +" bindings to do so with `pip install --upgrade gdal-utils` (see more " +"details in the following sections)." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:47 +msgid "" +"Making gdal Python developers life easier on Windows (and maybe other " +"platforms):" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:40 +msgid "" +"The straightforward way of cloning `gdal` and adding `gdal/swig/python` " +"to Python path (In PyCharm: marking the it as a `Source Root`) won't work" +" because the `pyc` files are missing from `gdal/swig/python/osgeo`, thus " +"by adding `osgeo` to Python path we would be masking a binary " +"installation of gdal that might be already installed (i.e. `osgeo4w` or " +"Christoph Gohlke's binary Windows wheels). Workarounds, like copying the " +"`pyc` files to the `osgeo` dir, cause their own problems, like: * " +"Switching interpreters that have different versions of `gdal` causes more" +" problems. * Non clean git working tree so committing the changes to git " +"is harder. By moving the `gdal-utils` into another root this problem is " +"completely avoid." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:79 +msgid "Allow mixing `gdal` and `gdal-utils` versions" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:50 +msgid "" +"As the Python code evolves semi-independently of the GDAL core and is not" +" directly dependent on a specific GDAL version, one might want use the " +"latest `gdal-utils` package with an older version of `gdal` core " +"bindings, or vice versa. Currently, One would need to mix the contents " +"different `gdal` packages to do so." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:54 +msgid "" +"As the `gdal` package is platform specific, and requires compilation, In " +"some distributions upgrading to a new GDAL version might take more time, " +"so one could upgrade the `gdal-utils` package easily and independently of" +" upgrading the `gdal` package, using `pip install --upgrade gdal-utils`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:58 +msgid "" +"On the other hand, if we drop another Python version, like we just did " +"with Python 2.7, One might be still be able to use newer gdal core " +"bindings (which might still support an older version of Python) with an " +"older `gdal-utils`, Which might drop Python versions sooner." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:62 +msgid "Reasons why users wouldn't be able to upgrade to recent GDAL:" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:64 +msgid "" +"They use some LTS distribution (like Debian), or application (like QGIS " +"LTS)." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:65 +msgid "" +"Recent GDAL is not available for their platform or distribution (even if " +"not LTS)." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:66 +msgid "" +"Their code dependents on some binary gdal-plugin which is available for a" +" specific GDAL version." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:68 +msgid "" +"A concrete example would be someone who uses QGIS (or QGIS LTS) that " +"currently comes with GDAL 3.1, and wants to use the neat stuff added to " +"`gdal_calc`, With this RFC he could just `pip install --upgrade gdal-" +"utils`. Because this package package is Pure Python, upgrades should be " +"easy." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:72 +msgid "" +"Although each version of `gdal-utils` would only be tested against the " +"equivalent version of `gdal`, In most cases different versions would " +"still be compatible, but without guarantee." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:75 +msgid "" +"This RFC would make further testing the compatibility between different " +"versions of these packages easier and could be considered the first step " +"into making the `gdal-utils` package completely independent of the `gdal`" +" package. It would also potentially allow forward compatibility in case " +"we ever decide to remove the utils from the `gdal` wheel and keep them " +"only in the `gdal-utils` wheel." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:82 +msgid "Package Names and PyPi release:" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:84 +msgid "" +"This RFC suggests to keep the all-in-one package and in addition to " +"distribute a utils only package, In order to keep the required changes " +"from users to a minimum and at the same time allow mixing versions:" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:87 +msgid "https://pypi.org/project/GDAL/" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:89 +msgid "" +"Distribution of a single `pypi.org` wheel named `gdal` will be retained " +"and will includes both packages. This will insure smooth transition and " +"maximum backwards compatibility." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:92 +msgid "https://pypi.org/project/gdal-utils/" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:94 +msgid "" +"A new `pypi.org` package is introduced to include with just the " +"`osgeo_utils` package, which will allow upgrading the utils without " +"upgrading the bindings." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:97 +msgid "" +"To be consistent with the `gdal` `pypi` package name, the utils `pypi` " +"package is named `gdal-utils`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:99 +msgid "" +"the name `osgeo_utils` is consistent with the `osgeo` namespace and " +"module names." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:114 +msgid "How to upgrade the utils without upgrading the bindings:" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:116 +msgid "" +"> If someone installs the \"gdal\" all-in-one package and the \"gdal-" +"utils\" one. Wouldn't that conflict ?" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:118 +msgid "" +"`pip install` a wheel overwrites whichever files already exist (even if " +"installed by a different package) If you `pip install gdal` then `pip " +"install gdal-utils` you'd get the utils from `gdal-utils`. If later you " +"do again `pip install gdal` with a different version then you'd get the " +"utils from `gdal` again, and so on. (it doesn't seem that it matters " +"which version is a bigger number, just which one you installed later)" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:123 +msgid "" +"If you `pip install gdal` then `pip install gdal-utils` and then `pip " +"uninstall gdal-utils` then the utils would be uninstalled and you'd be " +"left with gdal without utils. Then you could `pip install gdal-utils` or " +"`pip install gdal --ignore-installed` to get them back again (`--ignore-" +"installed` is not required if you install a different version)" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:131 +msgid "" +"The scope of this RFC is the GDAL Python code, except for the SWIG " +"bindings. There is no effect on any other language supported by GDAL. " +"Because gdal core is tested using the Python SWIG bindings - this RFC " +"does not suggest changing them in any way. Binary wheel distribution - " +"discussed in the past and related to ideas in this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:138 +msgid "`gdal` and `gdal-utils` Compatibility" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:140 +msgid "" +"This RFC suggests that `gdal-utils` would continue to be only tested " +"against the same version of `gdal`. In most cases different versions " +"would still be compatible, but without guarantee." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:143 +msgid "" +"A minimum energy approach might keep `gdal-utils` compatible with some " +"`gdal` versions != `x.y`. `gdal-utils` might officially drop support of " +"some too old version of GDAL by specifying a newer minimum version of " +"GDAL in the `setup.py` of `gdal-utils`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:147 +msgid "" +"For maximum backwards compatibility and because we would only test `gdal`" +" against the same version of `gdal-utils` - `osgeo` and `osgeo_utils` " +"will continue to be distributed inside a single wheel in addition to the " +"new separate wheel for the utils only." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:151 +msgid "" +"In cases were an `gdal-utils` module or function actually does need a " +"minimum specific version of `gdal` (i.e. dependence on a new GDAL C API) " +"Compatibility could be checked at runtime by comparing to " +"`osgeo.__version__`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:155 +msgid "Versioning" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:157 +msgid "" +"As development of `gdal-utils` will be still tied with the development of" +" GDAL and will be released together with the same `x.y.z` version number." +" In case a hotfix to `gdal-utils` is required for some reason, a " +"`x.y.z.p` version might be used, Which will not effect the distribution " +"of version `z+1`, i.e. `3.3.0` < `3.3.0.1` < `3.3.1`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:164 +msgid "Backward compatibility issues:" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:166 +msgid "`osgeo.utils` will need be replaced with `osgeo_utils`" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:167 +msgid "" +"This is the only breaking change, only for GDAL=3.2, and only a single " +"character." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:168 +msgid "" +"`swig/python/scripts` - users of the gdal scripts (which are thin " +"wrappers around the utils) wouldn't be effected." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:172 +msgid "Folder structure change" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:174 +msgid "" +"`gdal/swig/python/osgeo/utils` -> `gdal/swig/python/gdal-" +"utils/osgeo_utils`" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:176 +msgid "" +"`gdal/swig/python/osgeo/setup.py` - was updated to include the utils from" +" the new location under the `gdal-utils` folder." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:178 +msgid "" +"`gdal/swig/python/gdal-utils/setup.py` - additional setup was added for " +"`gdal-utils`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:183 +msgid "" +"`gdal-utils` wheel building could be added to the CI, i.e. like in " +"https://github.com/OSGeo/gdal/pull/3579 No other CI Impacts." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:209 +msgid "Implications of this change shell documented in the README." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:214 +msgid "Minor changes were made to pytest." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:221 +msgid "" +"http://osgeo-org.1560.x6.nabble.com/gdal-dev-Call-for-discussion-on-RFC77" +"-Drop-Python-2-support-td5449659.html" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:226 +msgid "https://gdal.org/development/rfc/rfc77_drop_python2_support.html" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:227 +msgid "https://github.com/OSGeo/gdal/pull/3131" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:228 +msgid "https://github.com/OSGeo/gdal/pull/3117" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:229 +msgid "https://github.com/OSGeo/gdal/pull/3247" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:234 +msgid "" +"http://osgeo-org.1560.x6.nabble.com/gdal-dev-Motion-RFC-78-gdal-utils-" +"package-td5482707.html" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:236 +msgid "+1 from EvenR, HowardB" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:237 +msgid "+0 from KurtS, JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:243 +msgid "Implemented by the author of this RFC, Idan Miara." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:5 +msgid "RFC 79: Listing of Service Providers on GDAL website" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:8 +msgid "Daniel Morissette, Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:10 +msgid "2021-Feb-22" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:11 +msgid "2021-Mar-01" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:12 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:12 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:12 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:11 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:11 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:12 +msgid "Adopted" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:16 +msgid "1. Motivation" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:18 +msgid "" +"GDAL is developed and supported by a rich ecosystem of businesses and " +"individuals around the world but we do not do a good job of promoting " +"those service providers and making them easy to find by our users at the " +"moment." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:22 +msgid "" +"In this RFC, we propose a plan to address this by adding a Service " +"Providers page to the GDAL website." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:26 +msgid "2. Proposed plan" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:28 +msgid "A new Service Providers page will be added to the Sphinx documentation." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:30 +msgid "" +"The service providers will be grouped in three categories. The " +"descriptions below should make it relatively easy to determine in which " +"group a given organization belongs." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:34 +msgid "" +"Each qualified organization who wishes to be listed is responsible for " +"adding themselves to the correct category in the page through a pull " +"request (or a direct commit in case of core committers). We are " +"intentionally not providing instructions here for preparing the pull " +"request as it is expected that a qualified service provider should have " +"people on staff who can figure it out. Yes, we intentionally try to keep " +"the bar at a minimum level." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:42 +msgid "" +"A PSC vote is NOT required in order to add a new service provider, i.e. " +"any core committer can validate and commit the pull request (or their own" +" entry) but in case of doubts or disagreements on the interpretation of " +"the rules, the GDAL PSC will be the ultimate authority to resolve the " +"question." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:48 +msgid "" +"Organizations in each category are displayed in randomized order (except " +"in the PDF docs which are static). However entries should be added to the" +" source file in alphabetical order (for PDF docs purpose). The output " +"will be similar to https://mapserver.org/community/service_providers.html" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:55 +msgid "2.1 Core Contributors" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:57 +msgid "" +"Core Contributors are the organizations that have one or more Core " +"Committer (a person with merge rights in the GDAL GitHub repository) " +"and/or PSC members as part of their staff and who provide GDAL related " +"services to customers." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:62 +msgid "" +"To qualify, the Core Committers and/or PSC members must be directly " +"employed by the organization and not part time contractors." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:65 +msgid "" +"They get to add a 200px max high or wide logo with a descriptive text " +"outlining their qualifications and services." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:68 +msgid "2.2 Contributors" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:70 +msgid "" +"Contributors are organizations who provide GDAL related services and have" +" one or more people on their staff who are well known in the GDAL " +"community for their long term contributions to the project. Contributions" +" are not limited to source code and can also be in the form of " +"documentation, binary builds, active user support via the public forums, " +"etc." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:76 +msgid "" +"They get to add a 150px max high or wide logo with a descriptive text " +"outlining their qualifications and services." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:79 +msgid "2.3 Other Service Providers" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:81 +msgid "" +"Organization with GDAL expertise and providing services around GDAL can " +"fit in this category. While proprietary solutions providers are welcome, " +"we expect organizations listed here to be providing legitimate services " +"to users of the Open Source software as well. This is not an " +"advertisement board for proprietary products." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:87 +msgid "" +"They get to add a 100px max high or wide logo with a descriptive text " +"outlining their qualifications and services." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:90 +msgid "2.4 Refreshing the service providers list" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:92 +msgid "" +"If at some point (every 2 years?) we feel that the list is or might be no" +" longer current, we could bring it up to date as follows:" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:95 +msgid "create a GitHub ticket dedicated for the refresh" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:96 +msgid "" +"send an email to the list with this message \"in 4 weeks, we are going to" +" remove all currently listed service providers to refresh the site. If " +"you are still interested, add a note to ticket XXXX\"." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:100 +msgid "" +"Instead of the ticket we could just ask people to reply to the email but " +"the advantage of the ticket is to generate less email traffic for those " +"not interested. It leaves a trace of the list of organizations who " +"responded in a single place inside the ticket." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:105 +msgid "3. FAQ" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:107 +msgid "" +"Should we also recognize sponsors or organizations that are funding " +"significant features in this page?" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:110 +msgid "" +"No. This is a service provider page and not a sponsorship page. However " +"if the organization in question is also offering GDAL related services " +"they can be added to the relevant category. They just won't get special " +"status due to their financial contributions." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:116 +msgid "4. Credits" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:118 +msgid "" +"This RFC is a straightforward adaptation of the equivalent MapServer one:" +" https://mapserver.org/development/rfc/ms-rfc-116.html" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:122 +msgid "5. Voting History" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:124 +msgid "+1 from PSC members MateuszL, KurtS, JukkaR, DanielM and EvenR." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:5 +msgid "RFC 7: Use VSILFILE for VSI*L Functions" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:7 +msgid "Author: Even Rouault (Eric Doenges is original author)" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:9 +msgid "Contact: even dot rouault at spatialys.com, Eric.Doenges@gmx.net" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:16 +msgid "" +"To change the API for the VSI*L family of functions to use a new data-" +"type VSILFILE instead of the current FILE." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:20 +msgid "Background, Rationale" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:22 +msgid "" +"Currently, GDAL offers two APIs to abstract file access functions " +"(referred to as VSI\\* and VSI\\ *L in this document). Both APIs claim to" +" operate on FILE pointers; however, the VSI*\\ L functions can only " +"operate on FILE pointers created by the VSIFOpenL function. This is " +"because VSIFOpenL returns a pointer to an internal C++ class typecast to " +"a FILE pointer, not an actual FILE pointer. This makes it impossible for " +"the compiler to warn when the VSI\\* and VSI*L functions are " +"inappropriately mixed." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:32 +msgid "Proposed Fix" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:34 +msgid "" +"A new opaque data-type VSILFILE shall be declared. All VSI\\ *L functions" +" shall be changed to use this new type instead of FILE. Additionally, any" +" GDAL code that uses the VSI*\\ L functions must be changed to use this " +"data-type as well." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:40 +msgid "RawRasterBand changes" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:42 +msgid "" +"The 2 constructors are changed to accept a void\\* fpRaw instead of a " +"FILE\\*" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:44 +msgid "" +"A new member VSILFILE\\* fpRawL is added. The existing member FILE\\* " +"fpRaw is kept. The constructors will set the adequate member according to" +" the value of the bIsVSIL parameter." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:47 +msgid "A new method VSILFILE\\* GetFPL() is added." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:48 +msgid "" +"The old FILE\\* GetFP() is adapted to have same behavior as before (can " +"return a standard FILE handle or a VSI*L handle depending on the handle " +"that was passed to the constructor)" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:52 +msgid "" +"Those changes are meant to minimize the need for casting when using " +"RawRasterBand. Backward API compatibility is preserved." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:56 +msgid "Compatibility Issues, Transition timeline" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:58 +msgid "" +"In order to allow the compiler to detect inappropriate parameters passed " +"to any of the VSI*L functions, VSILFILE will be declared with the help of" +" an empty forward declaration, i.e." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:66 +msgid "with the struct \\_VSILFILE itself left undefined." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:68 +msgid "" +"However, this would break source compatibility for any existing code " +"using the VSI*L API. Therefore, for now, VSILFILE is defined to be an " +"alias of FILE, unless the VSIL_STRICT_ENFORCE macro is defined." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:80 +msgid "" +"In a future release (GDAL 2.0 ?), the behavior will be changed to enforce" +" the new strong typing." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:83 +msgid "" +"Any future development done since the adoption of this RFC should use " +"VSILFILE when dealing with the VSIF*L API." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:87 +msgid "Questions" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:89 +msgid "Should we define VSIL_STRICT_ENFORCE by default when DEBUG is defined ?" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:92 +msgid "" +"This would make life easier for GDAL developers to use the appropriate " +"typing, but not affect API/ABI when using release mode." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:98 +msgid "" +"The whole source tree ( port, gcore, frmts, ogr, swig/include ) will be " +"altered adequatly so that the compilation works in VSIL_STRICT_ENFORCE " +"mode. Ticket #3799 contains a patch with the implementation. The " +"compilation doesn't add any new warning. The autotest suite still works " +"after this change." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:104 +msgid "" +"The GeoRaster and JPIPKAK drivers have been modified during the " +"conversion process, but I'm not in position to compile them. Testing " +"appreciated. All other drivers that have been altered in the conversion " +"process have been compiled." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:109 +msgid "" +"In the conversion process, a misuse of POSIX FILE API with a large file " +"handler was discovered in the ceos2 driver, but the function happened to " +"be unusued." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:5 +msgid "RFC 80: NumFOCUS relationship and sponsorship program" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:8 +msgid "Even Rouault (with content from Chris Holmes)" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:10 +msgid "2021-Apr-15" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:11 +msgid "2021-Jun-07" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:18 +msgid "" +"The GDAL project will apply for Fiscal sponsorship to `NumFOCUS " +"`__, under the \"Grantor-Grantee\" model" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:24 +msgid "" +"GDAL's funding model to date has been using the overhead of new feature " +"implementation to support the maintenance activities. While this is a " +"common open source funding model, it is no longer sustainable given the " +"maturity that GDAL has reached. Undirected financial resources will give " +"the project the ability to target challenges that have proven too big or " +"too structural to otherwise attack." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:34 +msgid "" +"The GDAL project has determined that joining NumFOCUS for Fiscal " +"sponsorship will help address those challenges. NumFOCUS will receive " +"donations given by sponsors of the GDAL project." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:38 +msgid "" +"GDAL is well aligned with the requirements for a project to join " +"NumFOCUS, most of them are inherited from being an OSGeo project:" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:41 +msgid "Be scientifically oriented." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:42 +msgid "Be open." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:43 +msgid "Be kind." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:45 +msgid "" +"More precisely, GDAL will apply for Fiscal sponsorship under the " +"\"Grantor-Grantee\" model. It is described at https://numfocus.org" +"/projects-overview and put inline below for convenience:" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:60 +msgid "" +"Funds donated to GDAL will be earmarked to it (minus the commission " +"received by NumFOCUS for its operations, typically 15%, to be confirmed)." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:63 +msgid "" +"The project has already submitted a `first document " +"`__" +" presenting what GDAL is and why it wants to join NumFOCUS:" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:65 +msgid "" +"We now need to formally apply through their `application form " +"`__ so that the application is " +"passed to the NumFOCUS board for approval." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:68 +msgid "" +"The proposed answers to that application form are at: " +"https://docs.google.com/document/d/1bc5jdpCe1axdyBHxbJnun7e0DTyDoZI_eFYgJYnOhB8/edit" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:71 +msgid "" +"A `Pre-approved Grantor/ Grantee Agreement " +"`__ will also have to be signed by 3 members of the " +"GDAL PSC." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:75 +msgid "General use of funds" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:77 +msgid "" +"This topic will be refined in a further document, but we will underline " +"here the general principles." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:80 +msgid "" +"Funds obtained through NumFOCUS should be used in a way that is for the " +"general good of the project, as well as its key open source dependencies " +"(such as PROJ, libgeotiff, libtiff, shapelib, etc.)." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:84 +msgid "The tasks candidate to funding will be along (non-exhaustive list):" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:87 +msgid "ticket triaging and fixing," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:88 +msgid "code contribution review," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:89 +msgid "continuous integration maintenance and improvements," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:90 +msgid "monitoring of mailing list," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:91 +msgid "addressing reports raised by security monitoring infrastructure," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:92 +msgid "documentation improvement," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:93 +msgid "software releases," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:94 +msgid "co-operation with other funded developers (in particular onboarding)," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:95 +msgid "reports of those activities" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:97 +msgid "" +"More generally, all tasks that are needed for a project to strive on the " +"long term, but are typically hard to get directly funding from, as not " +"being directly tied to a particular feature. It is expected that new " +"features and improvements will go on being submitted as code " +"contributions by the interested parties in capacity to develop them, or " +"through service providers they might hire for that purpose." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:104 +msgid "" +"Sponsors will not be able to direct particular developments, nor receive " +"priority support through the sponsorship program. For such purposes, they" +" may use community support or refer to service providers, as for other " +"GDAL users. However, we will offer a way to sponsors to give feedback, as" +" detailed afterwards." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:110 +msgid "GDAL Advisory Council" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:112 +msgid "" +"The GDAL Advisory Council is a newly forming group that is tasked with " +"ensuring the project is evolving to meet the needs of its largest " +"supporters. There will be periodic meetings with the advisory board, GDAL" +" PSC members wishing to participate, and persons benefiting from funding," +" providing a forum to give feedback on the latest GDAL work. Board " +"members will also be expected to share how they are using GDAL in their " +"organization (in as much detail as is possible, understanding that some " +"can only talk in general terms). Though the GDAL PSC owns the decision " +"making around how the sponsorship money is allocated, the advisory board " +"will provide key input on the maintenance priorities of the sponsors." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:114 +msgid "" +"Our hope is that these sessions can also lead to new feature development " +"in GDAL through joint funding initiatives between top sponsors, providing" +" more structure to the way GDAL features are funded today. This ideally " +"leads to more cost-sharing as organizations will be able to be more " +"strategic when they know what everyone else is interested in. These " +"efforts will be above and beyond the core maintenance sponsorship, but " +"the Advisory Council will be a key forum to enable it." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:116 +msgid "" +"The Advisory board will have an email list, with members of the GDAL PSC " +"on it, and will meet on a periodic schedule, to be determined as the " +"group forms. It will consist of one representative from each of the Gold " +"sponsors, one representative for every three Silver sponsors, and one " +"representative from Bronze sponsors." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:119 +msgid "Acknowledgment of NumFOCUS and sponsors" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:121 +msgid "" +"The GDAL website will be updated to have a page dedicated to the " +"sponsoring program, acknowledging sponsors and NumFOCUS, providing a " +"detailed FAQ on what the sponsorship program consists in and a " +"\"sponsoring prospectus\" that can be used by candidate sponsors. A work-" +"in-progress version of this update is available at " +"https://github.com/OSGeo/gdal/pull/3681" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:128 +msgid "Impacts on OSGeo relationship" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:130 +msgid "" +"GDAL and will continue to remain a OSGeo project for all other concerns " +"than NumFOCUS-related sponsorship." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:136 +msgid "" +"+1 from PSC members EvenR, KurtS, FrankW, MateuszL, DanielM, HowardB and " +"NormanB" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:5 +msgid "RFC 81: Support for coordinate epochs in geospatial formats" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:10 +msgid "2021-May-10" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:11 +msgid "Last Updated:" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:11 +msgid "2021-Jun-18" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:13 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:13 +#: ../../source/development/rfc/rfc87_signed_int8.rst:12 +#: ../../source/development/rfc/rfc88_googletest.rst:12 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:12 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:12 +#: ../../source/development/rfc/rfc91_dataset_close.rst:12 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:12 +#: ../../source/development/rfc/rfc93_update_feature.rst:12 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:12 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:12 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:12 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:12 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:11 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:12 +msgid "Target:" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:13 +msgid "GDAL 3.4" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:19 +msgid "" +"This RFC describes support for coordinate epochs in a few key geospatial " +"formats and in GDAL/OGR API and utilities" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:25 +msgid "" +"A number of coordinate reference systems (CRS) are called \"dynamic " +"CRS\", that is the coordinates of a point on the surface of the Earth in " +"those CRS may change with time. To be unambiguous the coordinates must " +"always be qualified with the epoch at which they are valid. The " +"coordinate epoch is not necessarily the epoch at which the observation " +"was collected." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:31 +msgid "" +"Examples of dynamic CRS are ``WGS 84 (G1762)``, ``ITRF2014``, " +"``ATRF2014``." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:33 +msgid "" +"The generic EPSG:4326 WGS 84 CRS is also considered dynamic, although it " +"is not recommended to use it due to being based on a datum ensemble whose" +" positional accuracy is 2 meters, but prefer one of its realizations, " +"such as WGS 84 (G1762)" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:37 +msgid "" +"At time of writing, no formats handled by GDAL/OGR have a standardized " +"way of encoding a coordinate epoch. We consequently have made choices how" +" to encode it, admittedly not always elegant, with the aim of being as " +"much as possible backward compatible with existing readers. Those " +"encodings might change if corresponding official specifications evolve to" +" take this concept into account. But, as this is a bit of a chicken-and-" +"egg problem (\"why should we care about storing coordinate epoch if no " +"software can make use of it ?\"), let's start with this initial solution." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:46 +msgid "" +"PROJ can handle a number of time-dependent transformations between static" +" CRS and dynamic CRS, e.g a GDA2020 (static CRS/datum for Australia) to " +"ATRF2014 (dynamic CRS/datum for Australia), taking into account plate " +"motion. Having support to store coordinate epoch will make it easier to " +"have more accurate coordinate transformation." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:55 +msgid "" +"See :ref:`coordinate_epoch` for impacts on the API, encoding of CRS in a " +"number of formats, and impacts on existing utilities." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:62 +msgid "At the API level, only additions." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:64 +msgid "" +"Regarding creation of new datasets, no backward incompatibility at all if" +" datasets are created without a coordinate epoch associated to their CRS," +" as its encoding is only added when needed." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:68 +msgid "" +"And when it is used, it is done in a way that shouldn't affect existing " +"reader. The only exception would be the FlatGeobuf format if writing a " +"non-EPSG coded CRS, and with a coordinate epoch (a backport to the 3.3 " +"branch will be done to avoid an error in that case)." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:76 +msgid "" +"New methods are documented, and the page mentioned in the Details " +"paragraph will be part of the user documentation." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:82 +msgid "" +"New methods are tested. Formats extended with coordinate epoch support " +"have also received new tests." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:88 +msgid "https://github.com/OSGeo/gdal/pull/4011" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:93 +msgid "+1 from JukkaR and EvenR, -0 from HowardB and +0 from KurtS" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:5 +msgid "RFC 83: guidelines for the use of GDAL project sponsorship" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:8 +msgid "Even Rouault (with content from RFC 9)" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:10 +msgid "2021-May-19" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:17 +msgid "" +"Per :ref:`rfc-80`, the GDAL project benefits from a multi-year budget " +"coming from sponsorship. This document formalizes guidelines for how that" +" budget will be spent by the project and supersedes :ref:`rfc-9`" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:21 +msgid "There are two different type of tasks that will be funded:" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:23 +msgid "" +"Day-to-day maintenance tasks. They will be filled by several co-" +"maintainers." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:24 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:163 +msgid "Tasks to achieve a specific development" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:27 +msgid "Day-to-day maintenance tasks" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:30 +msgid "Scope" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:32 +msgid "Bug tracker maintenance:" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:34 +msgid "Validating completeness of bug reports to ensure reproducibility" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:35 +msgid "Closing reports that don't respect the guidelines, or are invalid." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:36 +msgid "Tagging the issue with appropriate labels and milestones." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:37 +msgid "When a fix is relevant, addressing the issue with a pull request." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:38 +msgid "" +"Adding / enhancing tests in the regression test suite should be done as " +"much as practical" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:40 +msgid "" +"Tasks that are expected, or are found, to take more than a given time " +"should be confirmed with the supervisor." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:43 +msgid "" +"Continuous Integration maintenance and improvements: the project has " +"several Continuous Integration configurations. Some of them break " +"regularly due to external causes (network resources no longer available, " +"change in dependencies, etc.). The co-maintainer will take the necessary " +"actions to keep them in working state." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:48 +msgid "" +"Review of code and documentation contributions. Such contributions are " +"made currently through GitHub pull requests. The co-maintainer will " +"review the contribution and guide the proponent through the steps to make" +" it accepted: identifying issues reported by Continuous Integration, " +"asking for new tests to be developed whenever possible, etc. When the " +"contributor is not in capacity to polish his/her contribution, the co-" +"maintainer may do it themself." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:54 +msgid "" +"Ensuring that fixes that are appropriate for backporting in stable " +"branche(s) are backported." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:56 +msgid "" +"Monitoring of project communication channels (mailing list, IRC, Slack " +"channels, etc.). The co-maintainer will in particular identify issues " +"that are reported through those means and ensures that they are captured " +"by a corresponding ticket. The co-maintainer may also occasionally answer" +" questions on usage of the library and tools, but in-depth support of " +"users is not in the scope of the covered tasks (users may use service " +"providers for that purpose)." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:63 +msgid "" +"Proactive tracking of new versions of libraries that GDAL depends on, and" +" address needed changes for compilation and proper runtime behavior" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:65 +msgid "" +"Monitor and address reports of static and dynamic analyzers. Currently: " +"OSS-Fuzz, cppcheck, Clang Static Analyzer, Coverity Scan, gcc&clang " +"memory/undefined behavior/etc. analyzers." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:68 +msgid "Documentation improvements" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:69 +msgid "" +"Activities related to software releases: writing the release notes, " +"issuing release candidates, addressing feedback, finalizing releases" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:71 +msgid "" +"For experienced contributors, help less experienced contributors get on " +"board and along with GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:74 +msgid "" +"Projects that are concerned by such activities: GDAL itself of course, " +"but also other, generally smaller, free and open source projects that " +"have been strongly tied to it as being required or very common " +"dependencies for GDAL, and don't benefit from similar maintenance funds " +"(on the contrary, projects that use GDAL don't qualify for being funded " +"by the GDAL sponsorship funds). The current list includes PROJ, libtiff, " +"libgeotiff, shapelib, GEOS, OpenJPEG. If during the investigation of an " +"issue, a co-maintainer finds an issue in another open source component " +"and can come up with a patch, they are also welcome to do it." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:83 +#, python-format +msgid "" +"A typical share of time could be 75% for GDAL and 25% for the other " +"projects." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:85 +msgid "" +"GDAL is a vast and complex project. It is not expected that each co-" +"maintainer has expertise in all its aspects. Applicants will mention " +"their domains of interest, which can evolve over time, and coordinate " +"with other stakeholders in how tasks are assigned." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:91 +#: ../../source/development/rfc/rfc9_maintainer.rst:42 +msgid "Direction" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:96 +msgid "" +"The co-maintainer is generally subject to the project PSC. However, for " +"day to day decisions one PSC member might be designated as the supervisor" +" for the co-maintainer (PSC members that are funded through this program " +"will use existing decision making processes to prioritize their work). " +"This supervisor will coordinate with the co-maintainer via email or IRC " +"discussions." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:106 +msgid "" +"The supervisor will try to keep the following in mind when prioritizing " +"tasks:" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:108 +msgid "" +"Tickets that are regressions compared to a previous release are of higher" +" priority than other tasks" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:110 +msgid "" +"Bug reports should be given higher priority than other tasks. (bug " +"reports from sponsors will *not* qualify as such for higher priority " +"treatment)" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:112 +msgid "" +"Areas of focus identified by the PSC should be given higher priority than" +" other tasks." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:114 +#: ../../source/development/rfc/rfc9_maintainer.rst:56 +msgid "Bugs or needs that affect many users should have higher priority." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:115 +msgid "" +"The co-maintainer should be used to take care of work that no one else is" +" willing and able to do (i.e. fill the holes, rather than displacing " +"volunteers)" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:117 +msgid "" +"Try to avoid tying up the co-maintainer on one big task for many weeks " +"unless directed by the PSC." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:119 +msgid "" +"The co-maintainer should not be directed to do work for which someone " +"else is getting paid." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:122 +msgid "" +"Substantial new development projects will only be taken on by the co-" +"maintainer with the direction of a PSC motion (or possibly an RFC " +"designating the co-maintainer to work on a change)." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:126 +msgid "" +"Note that the co-maintainer and the co-maintainer supervisor are subject " +"to the normal RFC process for any substantial change to GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:130 +#: ../../source/development/rfc/rfc9_maintainer.rst:73 +msgid "Reporting" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:132 +msgid "" +"The co-maintainer will produce a monthly report (typically in a shared " +"spreadsheet) with the tasks they have tackled, typically pointing at " +"tickets and pull requests, and the amount of hours spent during the " +"reported period." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:137 +msgid "Who can apply ?" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:139 +msgid "" +"Applicants should be individuals, either self-employed or employed by a " +"company agreeing to allocate some of their time to such activities, that " +"have been a proven public track record of meeting the following " +"qualities:" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:143 +msgid "" +"Knowledge of the programming languages required for the task: C/C++ for " +"GDAL library and some knowledge of Python for the test suite, appropriate" +" language for any of the SWIG bindings." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:146 +msgid "" +"Knowledge of the geospatial field, ideally with one or several open " +"source geospatial projects, and/or experience with file formats and low-" +"level considerations." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:149 +msgid "" +"Ability to interact with members of an open source community in " +"accordance to the Code of Conduct." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:151 +msgid "Good knowledge of written English is necessary." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:153 +msgid "" +"We cannot put formal criteria on that, but applicants should ideally aim " +"for a multi-year involvement with the project, so that their onboarding " +"time is amortized." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:156 +msgid "" +"Each co-maintainer will be allocated a maximum number of hours per " +"quarter (they will indicate their planned availability and the PSC will " +"decide on the effective allocation), and will invoice on the time " +"effectively spent within that allocation." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:160 +msgid "" +"Applicants will provide their hourly rate, in US dollars, to the PSC " +"(privately)" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:169 +msgid "" +"The GDAL PSC will call for proposals (frequency to be adjusted, but could" +" be per quarter year) of proponents that want to achieve a specific " +"development. The PSC will indicate the total budget available and other " +"conditions. The PSC may suggest a few ideas that it would want to receive" +" proposals for." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:174 +msgid "" +"Generally speaking, priority will be given to proposals that address " +"housekeeping tasks, non-directly user oriented aspects of the " +"project(s), rather than user-oriented features (new drivers, new " +"utilities, etc. are more prone to be funded by interested parties), but " +"the later ones can be proposed if they are deemed of sufficiently large " +"interest." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:180 +msgid "" +"A non-exhaustive list of topics that are meant to be addressed per this " +"vehicle are:" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:182 +msgid "Improving/rewriting a part of the code base" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:183 +msgid "Changes that affect a large part of the code base" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:184 +msgid "Speed optimizations" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:185 +msgid "Adding / improving support for some platforms" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:186 +msgid "Improvements in test suite / Continuous Integration" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:187 +msgid "Improvements in build system" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:188 +msgid "Improvements in documentation" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:189 +msgid "" +"Packaging efforts (provided that they use fully reproducible open source " +"build recipes)" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:191 +msgid "" +"Applicants will provide the amount to be funded. Proposals may be put " +"together by one or several individuals (in the later case, to be " +"determined if we can let the team have a \"invoicing point of contact\" " +"and let them arrange how to dispatch it amongst members, or if each team " +"member should ask for its part of funding). An applicant may submit " +"proposals for several subjects." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:198 +msgid "" +"Applicants will submit the technical details of their proposal as an " +"issue in the bug tracker where it can be collaboratively discussed with " +"interested members of the community (or as an RFC for changes that would " +"usually qualify for a RFC)." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:205 +msgid "Criteria for applicants are the same as in the above section." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:208 +msgid "Decision process" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:210 +msgid "" +"The allocation of funds, through the selection of co-maintainers and " +"grantees of specific developments, will be decided by the PSC." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:213 +msgid "" +"The input provided by the Advisory Board regarding maintenance priorities" +" will be taken into account by the PSC, on an equal footing as other " +"input provided by the community, and PSC's own analysis of priorities." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:218 +msgid "" +"PSC members that apply for funds, or that have a conflict of interest " +"(e.g. working in the same company as an applicant), or any other " +"situation of conflict or interest, may take part in discussions, but " +"should abstain from voting on decisions related to fund allocation." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:224 +msgid "Note" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:226 +msgid "" +"As this is a new way of operating for the project, it is expected that " +"this RFC will evolve over time with the gained experience in the " +"management of the sponsorship program." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:233 +msgid "https://lists.osgeo.org/pipermail/gdal-dev/2021-June/thread.html#54249" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:235 +msgid "" +"+1 from PSC members MateuszL, HowardB, FrankW, KurtS, SeanG, JukkaR, " +"DanielM and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:5 +msgid "RFC 84: Migrating build systems to CMake" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:8 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:8 +msgid "Authors:" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:8 +msgid "Even Rouault, Nyall Dawson, Howard Butler" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:10 +msgid "" +"even.rouault at spatialys.com, nyall.dawson at gmail.com, howard at " +"hobu.co" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:13 +msgid "2021-09-22" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:14 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:11 +msgid "Updated:" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:14 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:10 +msgid "2022-01-17" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:15 +msgid "Adopted (implementation in progress)" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:21 +msgid "The document proposes :" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:23 +msgid "to develop a CMake build system, officially integrated in the source tree." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:25 +msgid "" +"and remove the current GNU makefiles and nmake build systems, when the " +"CMake build system has matured enough and reached feature parity. We " +"don't want to end up with a https://xkcd.com/927/ situation." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:32 +msgid "" +"A dual build system means editing twice, which increases the amount of " +"work and the chance for bugs." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:35 +msgid "" +"For Unix, we have a rather custom and non-idiomatic build system using " +"autoconf, but not automake." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:38 +msgid "" +"The makefiles in both build systems are hand-written. One of their main " +"deficiency from the point of view of a GDAL developer is the lack of " +"tracking of header dependencies. It is this very easy to produce a " +"corrupted GDAL build, if forgetting to manually clean a previous build. " +"This is a serious obstacle to embed regular or occasional GDAL developers" +" that hit that issue, generally not found in other projects." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:45 +msgid "Neither Unix or Windows builds support out-of-tree builds." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:47 +msgid "" +"Windows builds have poor support for parallel build: it is limited to the" +" files in one directory." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:50 +msgid "" +"There is generally no consistency in the naming of build options in our " +"Unix and Windows build systems, which makes life harder for users having " +"to build GDAL on multiple platforms." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:54 +msgid "" +"The two existing build systems do not have the same features. For " +"example, configure now offers the option to selectively disable drivers, " +"including ones that do not depend on external dependencies, using a opt-" +"out or opt-in strategies, whereas the NMake build does not." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:59 +msgid "" +"CMake has become the defacto solution with the widest adoption for C/C++ " +"software that want to address multiple platforms. Most of GDAL " +"dependencies have at least a CMake build system, and some have now CMake " +"as the only option (GEOS 3.10 will only have a CMake build system, and " +"the same is proposed for PROJ 9 in " +"https://github.com/OSGeo/PROJ/pull/2880), making soon CMake a de-facto " +"requirement for a GDAL build. Looking a bit in the FOSS4G field for C/C++" +" project, CMake is ubiquitous, so there is a widespread knowledge of it " +"among existing or potential contributors to GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:69 +msgid "" +"A CMake build system has been asked repeatedly by many developers or " +"users of GDAL over the past years. We are aware of a least two public " +"out-of-tree CMake efforts: https://github.com/miurahr/cmake4gdal and " +"https://github.com/nextgis-borsch/lib_gdal" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:73 +msgid "" +"CMake has the widest industry tooling support. A number of Modern C++ " +"IDEs offer good support for CMake: Visual Studio, qtcreator, etc. This " +"should help reduce the barrier for contribution." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:77 +msgid "" +"CMake development is active with regular feature releases, whereas the " +"technologies behind our existing build systems are more in a maintenance " +"mode." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:81 +msgid "Why not CMake?" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:83 +msgid "" +"Other modern cross-platform build systems exist, including Meson and " +"Bazel, which have many advantages over CMake. However, they are currently" +" not widely familiar or used by active GDAL contributors. CMake represent" +" the current \"least worse\" solution for multiple platform builds when " +"comparing its capabilities and its maturity." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:89 +msgid "" +"CMake does not address simultaneously building shared and static " +"libraries. This can however be worked around by doing 2 builds and " +"merging build artifacts." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:93 +msgid "Phases / Schedule" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:95 +msgid "The following is the planned schedule:" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:97 +msgid "" +"Add CMake as a new build system, and formally deprecate GNUmakefile and " +"NMake base file systems. Users and packagers are encouraged to switch to " +"CMake and actively report (and help fixing) issues the find in the " +"process. GDAL 3.5.x point releases will be used to address reported " +"issues." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:103 +msgid "==> Target: GDAL 3.5 / May 2022" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:105 +msgid "" +"Completely remove GNUmakefile and NMake base file systems, and make CMake" +" the only build system in GDAL source tree." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:108 +msgid "==> Target: GDAL 3.6 / November 2022" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:113 +msgid "" +"The above mentioned cmake4gdal repository seems to us the best starting " +"point. It respects the current tree organization of the GDAL repository " +"and targets a not too old CMake version (3.10)." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:117 +msgid "" +"We will start by running the scripts that deploy the CMakeLists.txt and " +"other cmake support files, and commit them into the GDAL repository." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:120 +msgid "" +"A checklist of all features of our current build systems that will need " +"to be ported and checked has been initiated in: " +"https://docs.google.com/spreadsheets/d/1SsUXiZxKim6jhLjlJFCRs1zwMvNpbJbBMB6yl0ms01c/edit" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:127 +msgid "" +"The Python, Java and CSharp bindings will be available as options of the " +"CMake build options." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:130 +msgid "" +"The Perl bindings will not be available, as being planned for removal in " +"GDAL 3.5" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:135 +msgid "" +"The addition of the CMake build system, being mostly an addition during " +"the transient phase where it will be available alongside the existing " +"build systems, should moderately impact existent files. However, it is " +"likely that there will be some improvements that affect C++ files (for " +"example, to use consistently ``#include `` style of " +"inclusion instead of the``#include `` with " +"``-I${include_prefix}/project`` pattern sometimes used) and the " +"GNUmakefile/makefile.vc files." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:142 +msgid "" +"We may use of PRIVATE linking of vendored and intermediate libraries to " +"hide non-public symbols. This might change a bit from existing builds " +"that can leak them." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:146 +msgid "Minimum CMake version" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:148 +msgid "" +"cmake4gdal uses CMake 3.10 as the minimum version. This is a reasonable " +"choice, as it would be compatible with the cmake version provided by " +"Ubuntu 18.04 for example, the current old-stable Ubuntu LTS." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:152 +msgid "" +"Given the mentioned schedule, CMake will become a requirement in May " +"2023, at a time where the new old-stable LTS will be Ubuntu 20.04. So we " +"can't exclude we will bump this minimum version if it is found to be more" +" practical. For example, CMake 3.12 adds an easier way for handling " +"\"object libraries\", that can help solving issues regarding static " +"builds and vendored dependencies (cf " +"https://github.com/libgeos/geos/issues/463)" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:160 +msgid "Supported platforms" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:162 +msgid "" +"Our continuous integration \"only\" tests Linux (Intel/AMD, ARM64 and " +"s390x architectures), Android (build only), MacOSX and Windows. We will " +"welcome involvement at some point from users/developers of other " +"environments to test and help address any outstanding issues." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:167 +msgid "General requirements" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:169 +msgid "" +"The following lists a few requirements to consider the new build system " +"be ready, and the existing ones can be removed:" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:172 +msgid "" +"The build system works on most environments where the build systems are " +"known to work. For CI-tested environments, this will involve porting to " +"them and checking that the builds are functional. For other build " +"systems, we will depend on manual testing from users." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:177 +msgid "objdir / out-of-source builds are supported." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:179 +msgid "cross builds are supported." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:181 +msgid "" +"Explicit testing of OSes through ``if(THIS_OS)`` should be limited, and " +"replaced by testing of feature wherever doable." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:184 +msgid "" +"There has been a formal release (presumably 3.6) with existing build " +"systems and cmake where cmake meets the above requirements, as verified " +"by packager feedback." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:190 +msgid "" +"Even Rouault and Nyall Dawson will use project sponsorship funding to " +"complete that work. An estimate of 2 man-months of effort has been made " +"recently to provide an initial build out of CMake support for GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:197 +msgid "+1 from PSC members: HowardB, MateuszL, KurtS, DanielM and JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:5 +msgid "RFC 85: Policy regarding substantial code additions" +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:8 +msgid "Howard Butler, Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:17 +msgid "" +"This document describes the policies that the GDAL project will apply to " +"assess substantial code additions, typically new drivers, in particular " +"coming from new contributors to the project." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:24 +msgid "" +"The GDAL project has historically been quite open to new code additions, " +"including drivers that rely on proprietary licensed and/or closed-source " +"SDKs (called \"binary SDK\" in the rest of this document). This approach " +"is part of its strengths, but also comes at a price, with the software " +"becoming larger and larger, and with contributions sometimes being " +"abandoned by their authors without new maintainers." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:31 +msgid "" +"Being a free & open-source project, the GDAL project will apply stronger " +"scrutiny to code that requires a binary SDK and encourage contributors to" +" submit code additions that do not depend on such binary SDK, or license " +"SDKs under free & open-source license terms." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:37 +msgid "Policy" +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:39 +msgid "" +"Drivers require a designated responsible contact, tracked in " +"https://github.com/OSGeo/gdal/wiki/Maintainers-per-sub-system" +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:42 +msgid "" +"Contributions should follow other RFCs describing development rules, and " +"come with test scripts and sufficient documentation, covering usage and " +"build instructions." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:45 +msgid "" +"If the driver require a binary SDK not downloadable without cost, or that" +" requires a complicated registration process, the GDAL team is unlikely " +"to support driver inclusion." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:48 +msgid "" +"GDAL supports multiple operating systems, and new drivers should support " +"as many as is practical. At a minimum, drivers should work with the " +"latest and OS-vendor supported releases of operating systems the driver " +"is documented to work with." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:52 +msgid "" +"If the binary SDK is no longer supported, or modernized to work with " +"current compilers and GDAL, the driver can be dropped. This rule also " +"applies to open-source dependencies that are no longer maintained or are " +"superseded by other alternatives." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:56 +msgid "" +"If the driver has unaddressed bugs, is breaking continuous integration " +"(CI), has caused CI bits to be disabled, or has not caught up to API " +"modifications requiring updates (extremely rare), the driver will be " +"dropped from build scripts, and thus will not be built without " +"significant user intervention." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:61 +msgid "" +"If critical/blocking issues reported in a driver are not addressed within" +" a 2 month time-frame, it can be dropped from the tree entirely by a " +"designated GDAL maintainer for all releases going forward." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:65 +msgid "" +"Contributors of significant code additions are expected to participate in" +" the day-to-day life of the GDAL project, and need to monitor closely the" +" communication channels of the project: issue tracker, mailing lists, " +"etc." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:69 +msgid "" +"Maintainers are expected to support their contributions by triaging bug " +"reports, reviewing related pull requests and RFCs, making functional " +"enhancements, testing releases, and improving documentation, tests, and " +"infrastructure." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:73 +msgid "" +"In addition, maintainers are expected to respond in a timely manner to " +"wider project changes (CI, build scripts, upgrade of dependencies, build " +"tools, documentation, etc.) as it pertains to their contributions." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:77 +msgid "" +"New contributions may require a significant review effort from a GDAL " +"committer (ie someone with direct modification rights to the source " +"repository). While the project has funded maintainers, it must be " +"understood that they might not be immediately available to do reviews of " +"significant code additions. Contributors may contract GDAL committers to " +"have such task done within a more predictable timeline." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:83 +msgid "" +"The above rules are not exhaustive. The PSC reserves the right to reject " +"a proposed code addition depending on its particular nature and other " +"contextual elements." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:89 +msgid "" +"+1 from PSC members MateuszL, KurtS, TamasS, SeanG, HowardB, JukkaR and " +"EvenR." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:5 +msgid "RFC 86: Column-oriented read API for vector layers" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:10 +msgid "2022-May-24" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:11 +msgid "2022-June-14" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:13 +msgid "GDAL 3.6" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:19 +msgid "" +"This RFC describes the addition of new methods to the " +":cpp:class:`OGRLayer` class to retrieve batches of features with a " +"column-oriented memory layout, that suits formats that have that " +"organization or downstream consumers that expect data to be presented in " +"such a way, in particular the `Apache Arrow " +"`_, `Pandas " +"`_ / `GeoPandas `_ " +"ecosystem, R spatial packages, and many modern (data analytics focused) " +"databases / engines which are column oriented (eg Snowflake, Google " +"BigQuery, ..)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:30 +msgid "" +"Currently, to retrieve feature information, users must iterate over each " +"feature of a layer with GetNextFeature(), which returns a C++ object, on " +"which query attributes and geometries are retrieved with various \"get\" " +"methods. When invoked from binding languages, a overhead typically occurs" +" each time the other language calls native code. So to retrieve all " +"information on a layer made of N_features and N_fields, you need of the " +"order of N_features * N_fields calls. That overhead is significant. See " +"below :ref:`rfc-86-benchmarks`." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:38 +msgid "" +"Another inconvenience of the C API is that processings that involve many " +"rows of a same field (e.g computing statistics on a field) may require " +"data to be contiguously placed in RAM, for the most efficient processing " +"(use of vectorized CPU instruction). The current OGR API does not allow " +"that directly, and require the users to shuffle itself data into " +"appropriate data structures. Similarly the above mentioned frameworks " +"(Arrow, Pandas/GeoPandas) require such memory layouts, and currently " +"require reorganizing data when reading from OGR. The `pyogrio " +"`_ project is for example an " +"attempt at addressing that need." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:48 +msgid "" +"Furthermore, the :ref:`vector.arrow` and :ref:`vector.parquet` drivers, " +"whose file organization is columnar, and batch oriented, have been added " +"in GDAL 3.5.0. Consequently a columnar-oriented API will enable the best " +"performance for those formats." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:56 +msgid "" +"The new proposed API implements the `Apache Arrow C Stream interface " +"`_. Reading " +"that document, as well of the first paragraphs of the `Apache Arrow C " +"data interface " +"`_. (details on" +" the various data types can be skipped) is strongly encouraged for a " +"better understanding of the rest of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:63 +msgid "" +"The Arrow C Stream interface is currently marked as experimental, but it " +"has not evolved since its introduction in Nov 2020 and is already used in" +" ABI sensitive places like the interface between the Arrow R bindings and" +" DuckDB." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:67 +msgid "" +"This interface consists of a set of C structures, ArrowArrayStream, that " +"provides two main callbacks to get:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:70 +msgid "" +"a ArrowSchema with the get_schema() callback. A ArrowSchema describes a " +"set of field descriptions (name, type, metadata). All OGR data types have" +" a corresponding Arrow data type." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:74 +msgid "" +"a sequence of ArrowArray with the get_next() callback. A ArrowArray " +"captures a set of values for a specific column/field in a subset of " +"features. This is the equivalent of a `Series " +"`_ in a Pandas " +"DataFrame. This is a potentially hiearchical structure that can aggregate" +" sub arrays, and in OGR usage, the main array will be a StructArray which" +" is the collection of OGR attribute and geometry fields. The layout of " +"buffers and children arrays per data type is detailed in the `Arrow " +"Columnar Format `_." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:84 +msgid "" +"If a layer consists of 4 features with 2 fields (one of integer type, one" +" of floating-point type), the representation as a ArrowArray is " +"*conceptually* the following one:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:93 +msgid "" +"The content of a whole layer can be seen as a sequence of record batches," +" each record batches being an ArrowArray of a subset of features. Instead" +" of iterating over individual features, one iterates over a batch of " +"several features at once." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:98 +msgid "" +"The ArrowArrayStream, ArrowSchema, ArrowArray structures are defined in a" +" ogr_recordbatch.h public header file, directly derived from " +"https://github.com/apache/arrow/blob/main/cpp/src/arrow/c/abi.h to get " +"API/ABI compatibility with Apache Arrow C++. This header file must be " +"explicitly included when the related array batch API is used." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:103 +msgid "The following virtual method is added to the OGRLayer class:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:110 +msgid "This method is also available in the C API as OGR_L_GetArrowStream()." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:112 +msgid "" +"out_stream is a pointer to a ArrowArrayStream structure, that can be in a" +" uninitialized state (the method will ignore any initial content)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:115 +msgid "" +"On successful return, and when the stream interfaces is no longer needed," +" it must must be freed with out_stream->release(out_stream)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:118 +msgid "" +"There are extra precautions to take into account in a OGR context. Unless" +" otherwise specified by a particular driver implementation, the " +"ArrowArrayStream structure, and the ArrowSchema or ArrowArray objects its" +" callbacks have returned, should no longer be used (except for " +"potentially being released) after the OGRLayer from which it was " +"initialized has been destroyed (typically at dataset closing). " +"Furthermore, unless otherwise specified by a particular driver " +"implementation, only one ArrowArrayStream can be active at a time on a " +"given layer (that is the last active one must be explicitly released " +"before a next one is asked). Changing filter state, ignored columns, " +"modifying the schema or using ResetReading()/GetNextFeature() while using" +" a ArrowArrayStream is strongly discouraged and may lead to unexpected " +"results. As a rule of thumb, no OGRLayer methods that affect the state of" +" a layer should be called on a layer, while an ArrowArrayStream on it is " +"active." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:132 +msgid "A potential usage can be:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:164 +msgid "" +"The papszOptions that may be provided is a NULL terminated list of " +"key=value strings, that may be driver specific." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:167 +msgid "OGRLayer has a base implementation of GetArrowStream() that is such:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:169 +msgid "" +"The get_schema() callback returns a schema whose top-level object " +"returned is of type Struct, and whose children consist in the FID column," +" all OGR attribute fields and geometry fields to Arrow fields. The FID " +"column may be omitted by providing the INCLUDE_FID=NO option." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:174 +msgid "" +"When get_schema() returns 0, and the schema is no longer needed, it must " +"be released with the following procedure, to take into account that it " +"might have been released by other code, as documented in the Arrow C data" +" interface:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:185 +msgid "The get_next() callback retrieve the next record batch over the layer." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:187 +msgid "" +"out_array is a pointer to a ArrowArray structure, that can be in a " +"uninitialized state (the method will ignore any initial content)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:190 +msgid "" +"The default implementation uses GetNextFeature() internally to retrieve " +"batches of up to 65,536 features (configurable with the " +"MAX_FEATURES_IN_BATCH=num option). The starting address of buffers " +"allocated by the default implementation is aligned on 64-byte boundaries." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:195 +msgid "" +"The default implementation outputs geometries as WKB in a binary field, " +"whose corresponding entry in the schema is marked with the metadata item " +"``ARROW:extension:name`` set to ``ogc.wkb``. Specialized implementations " +"may output by default other formats (particularly the Arrow driver that " +"can return geometries encoded according to the GeoArrow specification " +"(using a list of coordinates). The GEOMETRY_ENCODING=WKB option can be " +"passed to force the use of WKB (through the default implementation)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:203 +msgid "" +"The method may take into account ignored fields set with " +"SetIgnoredFields() (the default implementation does), and should take " +"into account filters set with SetSpatialFilter() and " +"SetAttributeFilter(). Note however that specialized implementations may " +"fallback to the default (slower) implementation when filters are set." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:208 +msgid "" +"Mixing calls to GetNextFeature() and get_next() is not recommended, as " +"the behavior will be unspecified (but it should not crash)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:211 +msgid "" +"When get_next() returns 0, and the array is no longer needed, it must be " +"released with the following procedure, to take into account that it might" +" have been released by other code, as documented in the Arrow C data " +"interface:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:221 +msgid "" +"Drivers that have a specialized implementation should advertise the new " +"OLCFastGetArrowStream layer capability." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:225 +msgid "Other remarks" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:227 +msgid "" +"Using directly (as a producer or a consumer) a ArrowArray is admittedly " +"not trivial, and requires good intimacy with the Arrow C data interface " +"and columnar array specifications, to know, in which buffer of an array, " +"data is to be read, which data type void* buffers should be cast to, how " +"to use buffers that contain null/not_null information, how to use offset " +"buffers for data types of type List, etc." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:233 +msgid "" +"For the consuming side, the new API will be best used with the (Py)Arrow," +" Pandas, GeoPandas, Numpy libraries which offer easier and safer access " +"to record batches. The study of the gdal_array._RecordBatchAsNumpy() " +"method added to the SWIG Python bindings can give a good hint of how to " +"use an ArrowArray object, in conjunction with the associated ArrowSchema." +" DuckDB is also another example of using the ArrowArray interface: " +"https://github.com/duckdb/duckdb/blob/master/src/common/types/data_chunk.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:240 +msgid "" +"It is not expected that most drivers will have a dedicated implementation" +" of GetArrowStream() or its callbacks. Implementing it requires a non-" +"trivial effort, and significant gains are to be expected only for those " +"for which I/O is very fast, and thus in-memory shuffling of data takes a " +"substantial time relatively to the total time (I/O + shuffling)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:246 +msgid "" +"Potential future work, not in the scope of this RFC, could be the " +"addition of a column-oriented method to write new features, a " +"WriteRecordBatch() method." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:252 +msgid "" +"Arrow and Parquet: get_schema() and get_next() have a specialized " +"implementation in those drivers that directly map to methods of the " +"arrow-cpp library that bridges at near zero cost (no data copying) the " +"internal C++ implementation with the C data interface." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:257 +msgid "" +"FlatGeoBuf and GeoPackage: a specialized implementation of get_next() has" +" been done, which saves going through the OGRFeature abstraction. See " +"below benchmarks for measurement of the efficiency." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:264 +msgid "" +"Per this RFC, only the Python bindings are extended to map the new " +"functionality." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:266 +msgid "The ogr.Layer class receives the following new methods:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:268 +msgid "" +"GetArrowStreamAsPyArrow(): wrapper over OGRLayer::GetArrowStream() that " +"has a ``schema`` property with the C ArrowSchema into a corresponding " +"PyArrow Schema object and which implements a Python iterator exposing the" +" C ArrowArray returned by the get_next() callback as a corresponding " +"PyArrow Array object. This is a almost zero-cost call." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:274 +msgid "" +"GetArrowStreamAsNumPy(): wrapper over OGRLayer::GetArrowStream() which " +"implements a Python iterator exposing the C ArrowArray returned by the " +"get_next() callback as a Python dictionary whose keys are field names and" +" values a Numpy array representing the values of the ArrowArray. The " +"mapping of types is done for all Arrow data types returned by the base " +"implementation of OGRLayer::GetArrowStream(), but may not cover " +"\"exotic\" data types that can be returned by specialized implementations" +" such as the one in the Arrow/Parquet driver. For numeric data types, the" +" Numpy array is a zero-copy adaptation of the C buffer. For other data " +"types, a copy is involved, with potentially arrays of Python objects." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:289 +msgid "Benchmarks" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:291 +msgid "" +"The test programs referenced in :ref:`rfc-86-annexes` have been run on a " +"dataset with 3.3 millions features, with 13 fields each (2 fields of type" +" Integer, 8 of type String, 3 of type DateTime) and polygon geometries." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:295 +msgid "" +":ref:`rfc-86-bench-ogr-py`, :ref:`rfc-86-bench-fiona` and :ref:`rfc-86" +"-bench-ogr-cpp` have similar functionality: iterating over features with " +"GetNextFeature()." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:298 +msgid "" +":ref:`rfc-86-bench-pyogrio-raw` does a little more by building Arrow " +"arrays." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:300 +msgid "" +":ref:`rfc-86-bench-pyogrio`, :ref:`rfc-86-bench-geopandas` and " +":ref:`rfc-86-bench-ogr-to-geopandas` have all similar functionality: " +"building a GeoPandas GeoDataFrame" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:303 +msgid "" +":ref:`rfc-86-bench-ogr-batch-cpp` can be used to measure the raw " +"performance of the proposed GetArrowStream() API." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:306 +msgid "nz-building-outlines.fgb (FlatGeoBuf, 1.8 GB)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:309 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:331 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:350 +msgid "Bench program" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:309 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:331 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:350 +msgid "Timing (s)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:311 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:333 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:352 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:427 +msgid "bench_ogr.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:311 +msgid "6.3" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:312 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:334 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:353 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:485 +msgid "bench_ogr.py" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:312 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:353 +msgid "71" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:313 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:335 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:354 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:518 +msgid "bench_fiona.py" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:313 +msgid "68" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:314 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:336 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:355 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:539 +msgid "bench_pyogrio_raw.py" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:314 +msgid "40" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:315 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:337 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:356 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:555 +msgid "bench_pyogrio.py" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:315 +msgid "108" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:316 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:338 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:357 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:570 +msgid "bench_geopandas.py" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:316 +msgid "232" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:317 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:339 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:358 +msgid "bench_ogr_batch.cpp (driver impl.)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:317 +msgid "4.5" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:318 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:340 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:359 +msgid "bench_ogr_batch.cpp (base impl.)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:318 +msgid "14" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:319 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:341 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:360 +msgid "bench_ogr_to_geopandas.py (driver impl.)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:319 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:360 +msgid "10" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:320 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:342 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:361 +msgid "bench_ogr_to_geopandas.py (base impl.)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:320 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:342 +msgid "20" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:323 +msgid "" +"\"driver impl.\" means that the specialized implementation of " +"GetArrowStream() is used. \"base impl.\" means that the generic " +"implementation of GetArrowStream(), using GetNextFeature() underneath, is" +" used." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:328 +msgid "nz-building-outlines.parquet (GeoParquet, 436 MB)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:333 +msgid "6.4" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:334 +msgid "72" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:335 +msgid "70" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:336 +msgid "46" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:337 +msgid "115" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:338 +msgid "228" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:339 +msgid "1.6" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:340 +msgid "13.8" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:341 +msgid "6.8" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:345 +msgid "" +"Note: Fiona slightly modified to accept Parquet driver as a recognized " +"one." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:347 +msgid "nz-building-outlines.gpkg (GeoPackage, 1.7 GB)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:352 +msgid "7.6" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:354 +msgid "63" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:355 +msgid "41" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:356 +msgid "103" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:357 +msgid "227" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:358 +msgid "4.8" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:359 +msgid "15.5" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:361 +msgid "21" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:365 +msgid "This demonstrates that:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:367 +msgid "" +"the new API can yield significant performance gains to ingest a OGR layer" +" as a GeoPandas GeoDataFrame, of the order of a 4x - 10x speed-up " +"compared to pyogrio, even without a specialized implementation of " +"GetArrowStream(), and with formats that have a natural row organization " +"(FlatGeoBuf, GeoPackage)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:373 +msgid "" +"the Parquet driver is where this shines most due to the file organization" +" being columnar, and its native access layer being ArrowArray compatible." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:376 +msgid "" +"for drivers that don't have a specialized implementation of " +"GetArrowStream() and whose layout is row oriented, the GetNextFeature() " +"approach is (a bit) faster than GetArrowStream()." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:383 +msgid "Only API additions, fully backward compatible." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:385 +msgid "The C++ ABI changes due to the addition of virtual methods." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:388 +msgid "New dependencies" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:390 +msgid "For libgdal: none" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:392 +msgid "" +"The Apache Arrow C data interface just defines 2 C structures. GDAL " +"itself does not need to link against the Apache Arrow C++ libraries (it " +"might link against them, if the Arrow and/or Parquet drivers are enabled," +" but that's orthogonal to the topic discussed in this RFC)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:397 +msgid "" +"For Python bindings: none at compile time. At runtime, pyarrow is " +"imported by GetArrowStreamAsPyArrow(). The GetArrowStreamAsNumPy() method" +" is implemented internally by the gdal_array module, and thus is only " +"available if Numpy is available at compile time and runtime." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:406 +msgid "" +"New methods are documented, and a new documentation page will be added in" +" the documentation." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:412 +msgid "New methods are tested." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:417 +msgid "https://github.com/OSGeo/gdal/compare/master...rouault:arrow_batch_new?expand=1" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:422 +msgid "Annexes" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:429 +msgid "Use of traditional GetNextFeature() and related API from C" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:487 +msgid "" +"Use of traditional GetNextFeature() and related API from Python (port of " +"bench_ogr.cpp)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:520 +msgid "" +"Use of the Fiona Python library which uses the OGR C GetNextFeature() " +"underneath to expose them as GeoJSON features holded by a Python " +"dictionary." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:532 +msgid "" +"Changing the above loop to ``list(features)`` to accumulate features has " +"a significant negative impact on memory usage on big datasets, and on " +"memory usage." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:541 +msgid "" +"Use of the pyogrio Python library which uses the OGR C GetNextFeature() " +"underneath to expose a layer as a set of Arrow arrays." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:557 +msgid "" +"Use of the pyogrio Python library which uses the OGR C GetNextFeature() " +"underneath to expose a layer as GeoPandas GeoDataFrame (which involves " +"parsing WKB as GEOS objects)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:572 +msgid "" +"Use of the GeoPandas Python library which uses Fiona underneath to expose" +" a layer as GeoPandas GeoDataFrame." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:585 +msgid "bench_ogr_batch.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:587 +msgid "Use of the proposed GetNextRecordBatch() API from C++" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:626 +msgid "bench_ogr_to_geopandas.py" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:628 +msgid "" +"Use of the proposed GetNextRecordBatchAsPyArrow API from Python, to build" +" a GeoPandas GeoDataFrame from the concatenation of the returned arrays." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:684 +msgid "+1 from PSC members MateuszL, JukkaR, HowardB and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:5 +msgid "RFC 87: Signed int8 data type for raster" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:10 +msgid "2022-Nov-8" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:11 +msgid "Adopted and implemented" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:12 +#: ../../source/development/rfc/rfc88_googletest.rst:12 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:12 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:12 +#: ../../source/development/rfc/rfc91_dataset_close.rst:12 +#: ../../source/development/rfc/rfc93_update_feature.rst:12 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:12 +msgid "GDAL 3.7" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:18 +msgid "" +"This RFC describes the addition of a new GDT_Int8 data type, for signed " +"8-bit integer data, to the GDALDataType enumeration." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:24 +msgid "" +":ref:`rfc-14` introduced in GDAL 1.5.0 a way of specifying that a 8-bit " +"integer should be interpreted as signed, by (ab)using the GDT_Byte type, " +"with the addition of the PIXELTYPE=SIGNEDBYTE metadata item in the " +"IMAGE_STRUCTURE metadata domain of bands for which this is desired." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:29 +msgid "" +"While this approach avoided the introduction of a new data type, which " +"has consequences internally in the GDAL code base at all places where a " +"\"switch\" is done on a GDALDataType variable, as well as impact on " +"external code using GDAL, this historical approach had the following " +"shortcomings:" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:34 +msgid "" +"drivers that need to support reading signed 8-bit integers must remind to" +" expose the PIXELTYPE=SIGNEDBYTE metadata item." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:37 +msgid "" +"drivers that need to support writing signed 8-bit integers must provide a" +" creation option for that purpose (generally called PIXELTYPE=SIGNEDBYTE " +"itself)." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:41 +msgid "" +"but more importantly, the absence of a proper data type means that it is " +"easy to forget to test the PIXELTYPE=SIGNEDBYTE metadata item in all " +"places where the value of pixels is taken into account. There were " +"special cases for statistics computations, but most of the other code, " +"such as the overview or warping computation code had no provision for it," +" and consequently mis-interpreted negative values in the range [-128,-1] " +"as positive values in the range [128,255]." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:52 +msgid "" +"A new ``GDT_Int8`` = 14 item is added to the :cpp:enum:`GDALDataType` " +"enumeration." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:54 +msgid "" +"It is taken into account in all places in gcore/ and alg/ that have " +"specific behavior depending on the value of GDALDataType. All places that" +" only dealt specifically with a subset of types (e.g Byte, Float32) and " +"promoted other types to the closest one will automatically have proper " +"support for the new data type (e.g overview computation)." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:60 +msgid "" +"Existing drivers that, on reading, reported GDT_Byte + " +"PIXELTYPE=SIGNEDBYTE are modified to report GDT_Int8. This has backward " +"compatibility impact to external code. This affects the EEDAI, ERS, GTA, " +"GTiff, HFA, netCDF, PostGISRaster, EHDR, RRaster, Rasterlite2 and Zarr " +"drivers." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:65 +msgid "" +"Existing drivers that, on writing, accepted the PIXELTYPE=SIGNEDBYTE, are" +" modified to accept GDT_Int8 as a valid data type in their " +"Create()/CreateCopy() implementations, and advertise \"GDT_Int8\" in " +"their GDAL_DMD_CREATIONDATATYPES metadata item. The PIXELTYPE=SIGNEDBYTE " +"creation option is kept but deprecated and discouraged: working with it " +"prior to this RFC was clunky at times, and will remain such." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:71 +msgid "" +"The MEM, HDF4, HDF5, KEA and PDS4 drivers are extended to support " +"GDT_Int8 on reading (and writing, except HDF5 that is read-only)." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:77 +msgid "The GDT_Int8 constant is made available in SWIG bindings." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:79 +msgid "" +"The numpy interface of the Python bindings is modified to map GDT_Int8 to" +" ``numpy.int8``." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:85 +msgid "" +"The PIXELTYPE=SIGNEDBYTE band metadata item in IMAGE_STRUCTURE is no " +"longer reported. Code that depended on it needs to switch testing for " +"GDT_Int8. Code that has \"switch\"-like constructs on GDALDataType must " +"also account for GDT_Int8." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:93 +msgid "" +"Documentation of utilities that have a ``-ot`` switch is modified to " +"mention Int8." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:95 +msgid "" +":ref:`rfc-14` will be amended to point to this RFC, and mention that " +"starting with GDAL 3.7.0, PIXELTYPE=SIGNEDBYTE is no longer the technical" +" solution." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:101 +msgid "" +"The test_gdal.cpp and testcopywords.cpp test files are extended to test " +"functions like :cpp:func:`GDALDataTypeIsInteger`, " +":cpp:func:`GDALDataTypeIsFloating`, :cpp:func:`GDALDataTypeIsComplex`, " +"etc. and all data type conversion combinations from/into GInt8." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:106 +msgid "" +"Parts of autotest, in driver specific tests, that were testing GByte + " +"PIXELTYPE=SIGNEDBYTE on reading or writing are adapted to the new " +"technical solution." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:110 +#: ../../source/development/rfc/rfc88_googletest.rst:224 +msgid "Related tickets and PRs:" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:112 +msgid "https://github.com/OSGeo/gdal/issues/4002" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:114 +msgid "https://github.com/OSGeo/gdal/pull/6633" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:119 +msgid "+1 from KurtS, JukkaR, MateuszL and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:5 +msgid "RFC 88: Use GoogleTest framework for C/C++ unit tests" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:10 +msgid "2022-Nov-16" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:18 +msgid "" +"The document proposes and describes conversion of the existing C/C++ " +"autotest suite to use the `GoogleTest framework " +"`__." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:22 +msgid "" +"GoogleTest is a popular and maintained framework for C/C++ test writing, " +"that is a better replacement for the `TUT framework " +"`__ that we use currently." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:29 +msgid "" +"The current TUT framework was adopted in 2006, and copied from the GEOS " +"project. While it works reasonably well, its use has the following " +"drawbacks:" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:32 +msgid "" +"TUT has little upstream activity. The last tagged release was apparently " +"in 2016." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:35 +msgid "We have an internal copy in our repository that might have diverged." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:37 +msgid "" +"TUT is, to the best of our understanding, not very popular among C/C++ " +"projects that have a regression test suite, which adds a (small) learning" +" curve to new contributors." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:41 +msgid "" +"One of TUT main practical disadvantages is that it is not obvious to know" +" which assertion has failed in a given test, unless adding a text string " +"describing the assertion, and often redundant with it. Like " +"``ensure_equals(\"x = 2\", x, 2);`` or some number like " +"``ensure_equals(\"(1)\", x, 2);``. In GoogleTest, you just write " +"``EXPECT_EQ(x, 2);`` and if it fails the filename and line number will be" +" printed in the error log, as well as the value of ``x``. With " +"GoogleTest, you may also provide additional context that will be output " +"when an assertion fails to help diagnose the reason of the failure, e.g.:" +" ``EXPECT_EQ(x, 2) << \"if that matters, y = \" << y;``" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:52 +msgid "" +"Another issue I stumbled upon a few months ago is that the default limit " +"for a given test group is 50 steps. If you don't increase it explicitly, " +"tests beyond the 50th one will be compiled but not run, without any " +"compile or runtime failure. One might easily believe they are successful " +"when they are not run at all!" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:57 +msgid "A few GoogleTest advantages:" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:59 +msgid "" +"It has been adopted by PROJ as its C/C++ test framework, and it makes " +"sense to use the same technologies whenever it makes sense given the " +"relationship of the 2 projects." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:63 +msgid "It has extensive documentation: https://google.github.io/googletest/" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:65 +msgid "" +"GoogleTest distinguishes assertions that must abort the test when failed " +"(ASSERT_xxxx) from those where the test can continue (EXPECT_xxxx), which" +" can be useful." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:69 +msgid "" +"The only noticed inconvenience of GoogleTest-based tests is that they " +"might be quite slow to compile in optimized mode (probably related to " +"https://github.com/google/googletest/issues/1478). I've found that " +"forcing non-optimized mode when building tests reduces build time of " +"tests to a reasonable amount, while not having practical disadvantages: " +"it still allows to test the library built in optimized mode. This is what" +" is done in the candidate implementation." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:77 +msgid "" +"This RFC doesn't change the logic of deciding when C/C++-based vs Python-" +"based tests should be written. My own position is that Python-based tests" +" should be preferred when possible, as productivity is higher in Python " +"and there is no associated compilation time (compilation time affects " +"feedback received from continuous integration). C/C++-based test should " +"be reserved for C++-specific aspects that cannot be tested with the SWIG " +"Python bindings, which use the C interface. For example testing of C++ " +"operators (copy/move constructors/assignment operators, iterator " +"interfaces, etc.) or C/C++ functionality not mapped to SWIG (e.g. CPL " +"utility functions/classes)" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:88 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:36 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:94 +#: ../../source/development/rfc/rfc91_dataset_close.rst:50 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:67 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:93 +msgid "Technical details" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:90 +msgid "" +"GoogleTest >= 1.10 will be required. If available in the system, the " +"system GoogleTest library will be used. Otherwise the CMake " +"ExternalProject_Add() functionality is used to download and built it " +"transparently. Use of system vs downloaded framework can be controlled " +"with the USE_EXTERNAL_GTEST=YES/NO CMake variable. This logic is copied &" +" pasted from PROJ." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:96 +msgid "" +"All assertion based tests will be migrated to GoogleTest. The few " +"performance tests that don't have any assertions and do not use TUT will " +"be kept unmodified (at least for now)." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:100 +msgid "The autotest/cpp/tut directory will be removed." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:102 +msgid "The migration from TUT to GoogleTest is mostly mechanical:" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:104 +msgid "TUT groups ==> GoogleTest test suite or fixture" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:105 +msgid "``ensure_equals(a,b)`` ==> ``ASSERT_EQ(a,b)`` or ``EXPECT(a,b)``" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:106 +msgid "``ensure(a)`` ==> ``ASSERT_TRUE(a)`` or ``EXPECT(a)``" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:107 +msgid "" +"``ensure_almost_equal(a,b)`` ==> ``ASSERT_NEAR(a,b,tolerance)`` or " +"``EXPECT_NEAR(a,b,tolerance)``" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:108 +msgid "``ensure(a >= b)`` ==> ``ASSERT_GE(a,b)`` or ``EXPECT_GE(a,b)``" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:109 +msgid "etc." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:111 +msgid "" +"Customized ensure logic like ``ensure_equal_geometries(geom1, geom2)`` " +"can also be migrated cleanly as functions that result an AssertionResult:" +" https://google.github.io/googletest/advanced.html#using-a-function-that-" +"returns-an-assertionresult" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:115 +msgid "" +"``GTEST_SKIP() << \"reason for the skip\"`` can be used to skip tests for" +" which a build-time or run-time requirement is missing." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:118 +msgid "" +"GoogleTest also offers capabilities for parametrized tests that were not " +"existing in TUT and can be adopted where it makes sense." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:121 +msgid "" +"For example the following test in TUT that tested GDALDataTypeUnion() on " +"all potential combinations of (datatype1, datatype2)" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:147 +msgid "can be written in GoogleTest as" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:197 +msgid "" +"While it is admittedly more verbose (which is an exception, as for " +"simpler tests, the GoogleTest way is generally smaller than the TUT way) " +"but much more expressive when looking at the test run output, where each " +"combination is run as a given named test, and thus if failure occurs, it " +"is easy to spot which combination failed, whereas with TUT you had to add" +" manual instrumentation:" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:220 +msgid "" +"None. This doesn't affect the library, nor the release source code " +"archive which don't include the autotest/ directory." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:226 +msgid "Ticket: https://github.com/OSGeo/gdal/issues/3525" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:228 +msgid "Implementation: https://github.com/OSGeo/gdal/pull/6732" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:233 +msgid "" +"+1from PSC members MateuszL, HowardB, JukkaR, KurtS , FrankW, DanielM and" +" EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:5 +msgid "RFC 89: SQL logging callback" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:9 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:9 +msgid "elpaso @ itopen.it" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:10 +msgid "2022-Nov-30" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:18 +msgid "" +"The document proposes and describes the introduction of a new callback " +"function to allow applications that use the GDAL library to monitor the " +"SQL queries actually sent from GDAL to the database." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:25 +msgid "" +"Applications (for example QGIS) may provide a debugging panel that allow " +"users to monitor the SQL command that are sent to the layers stored on " +"databases." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:29 +msgid "" +"This panel implemented in QGIS is very useful to identify erroneous or " +"inefficient queries and also made the users more conscious about what is " +"going on in the application when layers are loaded and features are " +"fetched." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:38 +msgid "" +"The implementation details are still to be defined, a possible " +"implementation would provide a method to `GDALDataset` that allows client" +" code to set the callback function (with some opaque context to be passed" +" back to client code)." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:43 +msgid "" +"The callback function will then be called from the drivers that make " +"database calls each time a SQL command is sent to the backend, in case of" +" prepared queries the actual SQL after parameter substitutions should be " +"sent." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:48 +msgid "" +"The callback will provide additional information about the executed query" +" (if available):" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:51 +msgid "error string message" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:52 +msgid "number of affected/retrieved records" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:53 +msgid "time taken to execute the query" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:56 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:118 +msgid "Example API:" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:77 +msgid "" +"The callback function will be initially used by the SQLite-based drivers " +"only (GPKG included)." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:79 +msgid "" +"The callback may be called by multiple threads in a concurrent way, for " +"this reason the implementation of the callback should be robust to that " +"(use of lock typically). That problem may arise in drivers that use " +"multi-threading as an optimization implementation detail. And this is " +"typically the case of the GeoPackage driver in its Arrow stream " +"interface." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:87 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:145 +msgid "Efficiency considerations" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:89 +msgid "" +"Drivers that support the query logger callback function would need to " +"check if the function pointer is `nullptr` and call the function if it is" +" not. The cost of thish check is probably negligible on most " +"architectures." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:93 +msgid "" +"In order to catch SQLite prepare errors, a prepare function wrapper will " +"be called instead of the sqlite3 API C function, this implies the cost of" +" a function call (which might be inlined if necessary)." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:97 +msgid "" +"Comparison of current master release build with the proposed " +"implementation on a 145665553 feature 15GB GPKG Point layer stored on " +"fast SSD:" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:101 +#: ../../source/development/rfc/rfc93_update_feature.rst:199 +msgid "Benchmark" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:101 +msgid "Master" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:101 +msgid "Proposed implementation" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:103 +msgid "bench_ogr_batch" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:103 +msgid "0.13m" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:103 +msgid "0.12m" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:105 +msgid "bench_ogr_c_capi" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:105 +msgid "2.57m" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:117 +msgid "" +"The callback would be set from a new method, no changes to the class " +"constructor would be needed." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:123 +msgid "This implementation will not be exposed to bindings." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:128 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:163 +msgid "A C++ test will be added to the test suite." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:134 +msgid "+1 from PSC members MateuszL, JukkaR, TamasS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc8_devguide.rst:5 +msgid "RFC 8: Developer Guidelines" +msgstr "" + +#: ../../source/development/rfc/rfc8_devguide.rst:11 +msgid "Status: draft" +msgstr "" + +#: ../../source/development/rfc/rfc8_devguide.rst:16 +msgid "" +"This document used to document developer practices for the GDAL/OGR " +"project. As it was an evolving document, its content has been moved to " +":ref:`development_practices`." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:5 +msgid "RFC 90: Direct access to compressed raster data" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:9 +#: ../../source/development/rfc/rfc91_dataset_close.rst:9 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:9 +msgid "even.rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:10 +msgid "2023-Jan-03" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:18 +msgid "" +"The document proposes 2 new methods to directly obtain the content of a " +"window of interest of a raster dataset in its native compressed format. " +"Those methods can be optionally implemented and used by drivers to " +"perform:" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:22 +msgid "" +"extraction of a compressed tile as a standalone file from a container " +"format (GeoTIFF, GeoPackage, etc.)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:25 +msgid "creation of mosaics from a set of tiles in individual files" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:27 +msgid "" +"lossless conversion between container formats using the same compression " +"method" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:33 +msgid "" +"When converting data between formats, calls to RasterIO(GF_Read, ...) " +"followed by RasterIO(GF_Write, ...) must be currently done. For " +"compressed formats, this causes decompression and recompression of data." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:37 +msgid "" +"In some particular cases, we could avoid decompressing and recompressing " +"when the underlying compression method is the same (or compatible), and " +"when requesting data aligned on the boundaries of the encoded data " +"(typically whole tiles). This would save execution time and would avoid " +"extra quality loss due to recompression cycles for lossy compression " +"methods." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:43 +msgid "" +"This RFC offers the framework to potentially address the following use " +"cases (non exhaustive list):" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:46 +msgid "" +"extraction of a JPEG (resp. WEBP, JPEGXL)-compressed whole tile from a " +"GeoTIFF file to a standalone JPEG (resp. WEBP, JPEGXL) file. Typical " +"scenario of tile servers using a GeoTIFF file as a tile backend." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:50 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:55 +msgid "" +"similarly as above, but with GeoPackage and JPEG/PNG/WEBP compression " +"methods." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:52 +msgid "" +"extraction of a subset of whole tiles of a JPEG/WEBP/JPEGXL-compressed " +"tiled GeoTIFF to a tiled GeoTIFF using the same compression method." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:57 +msgid "" +"lossless conversion of a mosaic of JPEG, WEBP, etc. non-overlapping and " +"contiguous tiles, each in a separate file, assembled as a VRT mosaic, to " +"a tiled GeoTIFF using the same compression method, with the tile " +"dimension being the one of each source file." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:62 +msgid "" +"lossless conversion of a JPEG-compressed (resp. WEBP-compressed) tiled " +"GeoTIFF to a JPEG-compressed (resp. WEBP-compressed) GeoPackage file and " +"vice-versa. Or a subset of the file, provided that the window of interest" +" is aligned on tiles boundaries." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:67 +msgid "" +"lossless conversion of JPEG to JPEGXL (currently implemented in master in" +" a rather ad-hoc way in the JPEGXL driver)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:70 +msgid "" +"lossless conversion of JPEGXL that has JPEG reconstruction box back to " +"JPEG (currently implemented in master in a rather ad-hoc way in the " +"JPEGXL and JPEGXL drivers)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:74 +msgid "" +"lossless conversion of JPEG-compressed tiled GeoTIFF to a JPEGXL-" +"compressed tiled GeoTIFF (and the reverse if JPEG reconstruction box is " +"included). Or a subset of the file, provided that the window of interest " +"is aligned on tiles boundaries." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:79 +msgid "" +"extraction of a subset of a JPEG-compressed tiled GeoTIFF to a standalone" +" JPEG file, with a window of interest not necessarily aligned on tile " +"boundaries, but just on the JPEG MCU (Minimum Code Unit), which is equal " +"to 8 pixels in the general case, and 16 for YCbCr data. And when " +"intersecting several tiles, provided that they share the same quality " +"settings (which is usually the case!) Or lossless retiling of JPEG-" +"compressed tiled GeoTIFF (e.g 256x256 -> 512x512)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:88 +msgid "" +"The proposed candidate implementation only covers a subset of those use " +"cases (some of them would require significant implementation effort), but" +" the proposed API addition makes them possible pending further " +"developments." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:96 +msgid "" +"The following 2 new methods are added at the :cpp:class:`GDALDataset` " +"level:" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:99 +msgid "GetCompressionFormats()" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:158 +msgid "" +"For example, to check if native compression format(s) are available on " +"the whole image:" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:179 +msgid "ReadCompressedData()" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:263 +msgid "" +"For example, to request JPEG content on the whole image and let GDAL deal" +" with the buffer allocation." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:295 +msgid "Or to manage the buffer allocation on your side:" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:342 +msgid "LOSSLESS_COPY creation option" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:344 +msgid "" +"Those methods are typically used by a GDALDriver::CreateCopy() " +"implementation to short-circuit the nominal logic of acquiring pixels " +"from the source and compressing them and use instead the compressed data " +"if available in the desired target compression format." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:349 +msgid "" +"Drivers that implement such short-circuit should expose a LOSSLESS_COPY " +"creation option, whose default value is AUTO, to mean that use of source " +"compressed data should be done in priority, and fallback to the regular " +"code path otherwise. Users might set it to YES to require the use of " +"lossless copy, and, when it is not possible to use it, the driver should " +"error out. Users might also set it to NO to ask for the regular code path" +" to be taken. Setting it to NO should be uncommon. This is a provision in" +" case the optimized code path would have bugs, or if for any other " +"reason, the regular code path must be taken (if the source compressed " +"data was not fully conformant for example)." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:361 +msgid "Miscellaneous" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:363 +msgid "" +"A helper ``bool GDALDataset::IsAllBands(int nBandCount, const int " +"*panBandList) const`` method is also added to check if (nBandCount, " +"panBandList) requests all the bands of the dataset." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:369 +msgid "Intended use" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:371 +msgid "" +"This RFC does *not* deprecate the traditional RasterIO() usage by any " +"means. Its main intended users are (some) CreateCopy() implementations." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:374 +msgid "" +"Clearly, the use of ReadCompressedData() is an advanced one, which often " +"requires a good understanding of some low-level characteristics of the " +"compression methods to be used properly (e.g. not all formulations of " +"JPEG codestreams are usable as a JPEG-in-TIFF or supported by libjxl in " +"JPEG lossless transcoding, which requires to examine the output of the " +"new helper GDALGetCompressionFormatForJPEG() function)." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:384 +msgid "" +"The 2 above C++ methods are available in the C API as " +"``GDALDatasetGetCompressionFormats()`` and " +"``GDALDatasetReadCompressedData()``. The return of " +"GDALDatasetGetCompressionFormats() should be freed with " +":cpp:func:`CSLDestroy`." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:392 +msgid "No backward incompatibility. Only API addition." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:394 +msgid "" +"For driver using ReadCompressedData() in their CreateCopy() " +"implementation, generated files might be changed, with more frequent " +"lossless conversions." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:400 +msgid "The new functions will *not* be exposed to bindings currently." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:405 +msgid "" +"The scenarios covered by the below proposed implementation will be tested" +" by C++ unit tests (unit testing of GetCompressionFormats() and " +"ReadCompressedData() implementations), and in Python autotest suite for " +"end-to-end tests (e.g lossless JPEG -> JPEGXL -> JPEG)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:411 +#: ../../source/development/rfc/rfc91_dataset_close.rst:183 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:281 +msgid "Issues / pull requests" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:413 +msgid "" +"https://github.com/OSGeo/gdal/compare/master...rouault:gdal:ReadCompressedData?expand=1" +" contains a candidate implementation with the following capabilities:" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:416 +msgid "" +"core empty implementation of GetCompressionFormats() and " +"ReadCompressedData()" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:418 +msgid "" +"implement ReadCompressedData() in the GeoTIFF driver for JPEG/WEBP/JPEGXL" +" compression (limited to extracting a single tile for now)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:421 +msgid "" +"implement ReadCompressedData() in the VRT driver (limited to a single " +"source for now, which forwards the call to the source)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:424 +msgid "implement ReadCompressedData() in the JPEG driver." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:426 +msgid "" +"use ReadCompressedData() in the JPEG driver (with pszFormat equal to " +"\"JPEG\") in its CreateCopy() implementation, and expose the " +"LOSSLESS_COPY creation option" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:430 +msgid "" +"implement ReadCompressedData() in the JPEGXL driver, returning both " +"\"JXL\" of course, but also \"JPEG\" if the JPEGXL file includes a JPEG " +"reconstruction box." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:433 +msgid "" +"use ReadCompressedData() in the JPEGXL driver, with pszFormat equal to " +"\"JPEG\" or \"JXL\", in its CreateCopy() implementation, and expose the " +"LOSSLESS_COPY creation option" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:437 +msgid "implement ReadCompressedData() in the WEBP driver." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:439 +msgid "" +"use ReadCompressedData() in the WEBP driver (with pszFormat equal to " +"\"WEBP\") in its CreateCopy() implementation, and expose the " +"LOSSLESS_COPY creation option" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:443 +msgid "Given the above, the following scenarios are for example covered:" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:445 +msgid "" +"gdal_translate -srcwin of a tile of a JPEG (resp. JPEGXL, " +"WEBP)-compressed tiled GeoTIFF to JPEG (resp. JPEGXL, WEBP). (involves " +"the GTiff and VRT drivers as producers, the JPEG/JPEGXL/WEBP drivers as " +"consumers)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:450 +msgid "" +"gdal_translate of a JPEGXL file with JPEG reconstruction box to JPEG " +"(involves the JPEGXL driver as producer, the JPEG driver as consumer). " +"And the reverse operation: lossless conversion of JPEG to JPEGXL with a " +"JPEG reconstruction box." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:458 +msgid "+1 from PSC members JukkaR, FrankW, SeanG, MateuzL and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:5 +msgid "RFC 91: GDALDataset::Close() method" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:10 +msgid "2023-Jan-20" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:18 +msgid "" +"This RFC aims at providing more robust error detection during dataset " +"closing, in particular for datasets in creation/update mode." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:21 +msgid "" +"It modifies the GDALDataset::FlushCache() method and GDALFlushCache() " +"function to return an error code, adds a GDALDataset::Close() virtual " +"method and modifies GDALClose() to return an error code." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:28 +msgid "" +"A lot of drivers that have write capabilities may do write operations in " +"their destructors, or just close the file descriptor owned by the " +"dataset. Currently there is no clean way of catching errors that might " +"occur. This recently bit `Fiona " +"` where the GeoJSON " +"driver may emit an error in its dataset destructor when writing the " +"content of a file to a cloud object storage." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:35 +msgid "" +"Code that currently wants to detect if GDALClose() causes an error has to" +" do something like the following:" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:45 +msgid "" +"This is awkward and there is a risk that something in the chain of calls " +"would clean the error state. It is thus desirable for the GDALClose() " +"method to return an error code." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:52 +msgid "" +"The GDALDataset::FlushCache() method is modified to return a CPLErr " +"return value." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:54 +msgid "A new virtual method GDALDataset::Close() is added." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:81 +msgid "A typical implementation might look as the following:" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:131 +msgid "" +"The default GDALDataset::Close() implementation sets nOpenFlags to " +"OPEN_FLAGS_CLOSED" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:137 +msgid "" +"GDALClose() and GDALFlushCache() are modified to return a CPLErr return " +"value." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:142 +msgid "" +"This is an ABI change that should not require more than rebuilding " +"applications against GDAL headers." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:145 +msgid "" +"For out-of-tree drivers that implement GDALDataset::FlushCache(), they " +"need to take into account the change in its signature." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:148 +msgid "" +"Out-of-tree drivers that have write capabilities are also encouraged to " +"implement GDALDataset::Close()." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:154 +msgid "" +"Not all drivers will be modified to implement Close() in the candidate " +"implementation, and even those modified might call internal methods of " +"the driver that do not do error propagation. Consequently, further work " +"might be needed on a case-by-case to improve driver implementations." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:162 +msgid "" +"The destructor of gdal.Dataset is modified to test the return value of " +"GDALClose() and emits a CPLError(CE_Failure, ...) if the error state is " +"clean (normally it should not)" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:167 +msgid "C/C++ command line utilities" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:169 +msgid "" +"C/C++ command line utilities are modified to test the return value of " +"GDALClose() on output datasets, and return a non-zero return code for the" +" process if GDALClose() returns an error." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:176 +msgid "" +"autotest/pymod/gdaltest.py::testCreate() is modified to call FlushCache()" +" and test its return value." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:179 +msgid "" +"The existing tests of the C/C++ command line utilities test GDALClose() " +"modified behavior." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:185 +msgid "Addresses https://github.com/OSGeo/gdal/issues/6886" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:187 +msgid "" +"https://github.com/OSGeo/gdal/compare/master...rouault:gdal:dataset_FlushCache_return_CPLErr?expand=1" +" contains a candidate implementation." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:190 +msgid "The candidate implementation does the following:" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:192 +msgid "Update all drivers that implements GDALDataset::FlushCache()." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:193 +msgid "" +"Implements GDALDataset::Close() for all drivers that derive from " +"RawDataset." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:194 +msgid "" +"Implements GDALDataset::Close() in the GeoJSON, GTiff, ODS, XLSX, SQLite," +" GPKG, netCDF, JP2OpenJPEG, FlatGeoBuf and OpenFileGDB drivers." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:196 +msgid "" +"Modifies all C/C++ command line utilities to test the return value of " +"GDALClose()" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:197 +msgid "Tests GDALClose() return value in gdal.Dataset destructor." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:202 +msgid "+1 from PSC members KurtS, MateuszL and me, and +0 from JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:5 +msgid "RFC 92: WKB Only geometries (on hold)" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:10 +msgid "2023-Jan-31" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:11 +msgid "On hold" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:12 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:64 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:68 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:70 +msgid "N/A" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:18 +msgid "" +"This RFC provides shortcuts to avoid instantiation of full OGRGeometry " +"instances in scenarios where only the WKB representation of geometries is" +" needed. The hope is to save CPU time." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:22 +msgid "This RFC is on hold." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:27 +msgid "" +"Some consumers of the OGR feature API only use the WKB representation of " +"the geometry. This is typically the case in the QGIS OGR provider (a QGIS" +" \"provider\" ~= a GDAL driver) which creates the corresponding " +"QgsGeometry instance from WKB." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:32 +msgid "" +"The format of geometries of some popular formats like GeoPackage or " +"PostGIS is based on WKB. Consequently the chain of processings done by " +"QGIS reading GeoPackage is:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:36 +msgid "GDAL side:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:38 +msgid "" +"acquire GeoPackage geometry blob (WKB with a GeoPackage specific header) " +"from the database" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:40 +msgid "" +"instantiate the relevant OGRGeometry subclass instance (OGRPoint, " +"OGRLineString, OGRPolygon, etc.) from WKB" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:42 +msgid "store it in a OGRFeature" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:44 +msgid "QGIS side:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:46 +msgid "get the OGRGeometry from the OGRFeature" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:47 +msgid "" +"asks for its WKB representation, build from the subclass members (not the" +" original WKB of step 2.)" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:49 +msgid "instantiate QgsGeometry from WKB" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:51 +msgid "" +"One can see that if we were able to store the original WKB representation" +" and get it back we could save OGRGeometry subclass object creation, " +"destruction and WKB deserialization and serialization." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:55 +msgid "" +":ref:`rfc-86` has seen related performance boosts since ArrowArray " +"batches store the WKB representation of geometries and not OGRGeometry " +"instances. This RFC borrows the same idea, but applying it to the " +"traditional feature API, as switching to ArrowArray API is a significant " +"undertaking for GDAL users." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:60 +msgid "" +"That could also be used in the future for a generic implementation of a " +"potential OGRLayer::WriteArrowArray() method that would build temporary " +"OGRFeature objects from the rows of the array to call the " +"ICreateFeature() implementation: the temporary geometries could be " +"OGRWKBOnlyGeometry instances for drivers such as GeoPackage that use WKB " +"natively." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:69 +msgid "" +"The proposal mostly contains in adding a new subclass of OGRGeometry " +"called `OGRWKBOnlyGeometry`" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:111 +msgid "A new method is added to the OGRLayer class:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:122 +msgid "Two new capabilities are added at the OGRLayer level:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:124 +msgid "" +"OLCReadWKBGeometries: a layer must return TRUE for it when the layer can " +"honour RequestWKBOnlyGeometries(true)" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:126 +msgid "" +"OLCWriteWKBGeometries: a layer must return TRUE for it if its " +"CreateFeature() and SetFeature() implementations support being passed " +"OGRWKBOnlyGeometry instances." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:130 +msgid "" +"ogr2ogr is modified to call RequestWKBOnlyGeometries(true) on the source " +"layer:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:132 +msgid "if the source layer advertises OLCReadWKBGeometries" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:133 +msgid "if the target layer advertises OLCWriteWKBGeometries" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:134 +msgid "if no command line switch requires a \"materialized\" geometry." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:136 +msgid "" +"So basically this is for requests like \"ogr2ogr out.gpkg in.gpkg [layer " +"or SQL request] [attribute filter] [spatial filter]\"" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:139 +msgid "" +"To be noted that while bounding box intersection in the case of " +"GeoPackage is done at the SQLite RTree level, the GeoPackage driver " +"currently does a \"client-side\" post filtering using GEOSIntersects() " +"(in situations where bounding box analysis only cannot conclude), so " +"geometry materialization is done in OGRLayer::FilterGeometry() for a " +"subset of features." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:148 +msgid "OGR_L_RequestWKBOnlyGeometries() is added." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:153 +msgid "No issue. Only API additions" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:156 +msgid "Benchmarking" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:159 +msgid "bench_ogr_c_api" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:161 +msgid "" +"The `bench_ogr_c_api " +"`_" +" benchmark utility which uses the C API to iterate over features and get " +"their WKB representation is enhanced with a `-wkb_only_geometry` switch " +"to call OGR_L_RequestWKBOnlyGeometries()." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:166 +msgid "" +"On a 1.6 GB GeoPackage (nz-building-outlines.gpkg) made of 3.2 million " +"features with simple polygons (typically quadrilaterals, building " +"footprints) and 13 attributes:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:170 +msgid "bench_ogr_c_api runs in 6.4 s" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:171 +msgid "bench_ogr_c_api -wkb_only_geometry runs in 5.0 s" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:173 +#, python-format +msgid "==> 22% faster" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:175 +#, python-format +msgid "" +"Other synthetic benchmarks show that the maximum speed-up is about 30% on" +" a dataset with 10 millions polygonal features of 10 points each." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:178 +msgid "" +"Conversely, the gain is much more modest, or close to null, with just a " +"few thousands of features that hold larger geometries (several thousands " +"of points each)." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:182 +msgid "" +"The gain is more in saving instantiation of OGRPolygon and OGRLinearRing " +"objects that in the size of their coordinate set." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:193 +#, python-format +msgid "" +"runs in 15.8 second in WKBOnlyGeometry mode vs 19.1 second without it " +"(master), hence a 17% speed-up." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:196 +#, python-format +msgid "" +"With spatial index creation enabled (multi-threaded), the wall clock time" +" difference is within measurement noise. And for singe threaded creation," +" the WKBOnlyGeometry mode is 5% faster." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:203 +msgid "Is it a good idea... ?" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:205 +msgid "" +"The design of OGRWKBOnlyGeometry is admittedly a bit clunky, or at least " +"at odds with other OGRGeometry subclasses, but nothing more elegant, " +"concise, performant and that doesn't change the whole OGRGeometry API and" +" driver implementations comes to mind." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:210 +msgid "" +"The scope is limited to a few drivers: GeoPackage, PostGIS (but the " +"current throughput of the driver is probably not sufficient for " +"OGRGeometry overhead to be noticeable), what else?" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:214 +msgid "" +"Should methods of OGRWKBOnlyGeometry that cannot work without " +"materialization of the real geometry return an error like done currently," +" or do the materialization on-the-fly when needed ? The motivation for " +"erroring out is to avoid silent performance issues related to " +"materialization." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:220 +msgid "Points raised during discussion" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:222 +msgid "" +"Sean Gillies: Wouldn't it be possible for all OGRFeatures to carry WKB " +"data by default and add a method to provide it to callers?" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:225 +msgid "" +"Even: That involve massive code rewrites in all drivers and wouldn't be " +"desirable from a performance point of view, because most drivers can't " +"generate WKB easily (PostGIS and GPKG are the exceptions rather the " +"norm). So either all other drivers should be modified to compose WKB at " +"hand (massive coding effort. Probably several weeks of effort and " +"significant risk of regressions). Or get it from the ExportToWkb() method" +" of the OGRGeometry instance they currently build, but then you pay the " +"price in memory and CPU time to generate WKB that might not be consumed " +"by users." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:234 +msgid "" +"Sean Gillies: And only construct an OGRGeometry when it's asked for? Such" +" as when GetGeometryRef is called?" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:237 +msgid "" +"Even: we could both make GetGeometryRef() and GetGeomFieldRef() virtual " +"methods whose default implementation would be the same as currently, ie. " +"return the value of the corresponding member variable in the base " +"OGRFeature class stored with " +"SetGeometry[Directly]()/SetGeomField[Directly]()" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:242 +msgid "And add a new virtual method:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:244 +msgid "" +"virtual GByte* OGRFeature::GetWKBGeometry(int iGeomField, size_t* " +"pnOutSize) const" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:246 +msgid "" +"whose default implementation would just use " +"GetGeomFieldRef(iGeomField)->ExportToWkb()." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:248 +msgid "" +"The few drivers that can provide a more efficient implementation (GPKG " +"typically) would create a derived class OGRFeatureGPKG with a specific " +"implementation of those new virtual methods to avoid systematic " +"OGRGeometry instantiation. The only drawback I see is that making " +"GetGeometryRef() and GetGeomFieldRef() virtual would have a slight " +"performance impact, but probably small enough." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:254 +msgid "" +"Dan Baston: I'm wondering about a more broad application of this. Would " +"it be helpful to have the ability to lazy-initialize an OGRGeometry from " +"multiple source types such as WKB and GEOS, initially storing only a " +"reference to the external data in WKB/GEOS/etc and actually materializing" +" the geometry when required? Then methods such as " +"OGRGeometry::exportToWkb and OGRGeometry::exportToGEOS could check the " +"external data type and use it directly if it is compatible, avoiding " +"materialization. This would avoid multiple conversions to/from GEOS in " +"cases where operations are chained, as well as allowing WKB to pass " +"directly between input and output drivers that support it. Relatedly, " +"this ability could be used to cache external-format data when it is " +"generated for an OGRGeometry, avoiding inefficiencies such as two " +"conversions to GEOS when checking to see if two geometries intersect " +"before calculating their intersection." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:268 +msgid "" +"Even: That's definitely something doable. At a minimum, you would have to" +" inspect the top geometry type to instantiate the appropriate OGRGeometry" +" subclass, and then its members could be lazy initialized, but that means" +" that all methods of OGRGeometry and its subclasses would have to do a " +"check whether the object has been fully initialized. There might be " +"performance implications for people doing for example " +"lineString->getX(idx) to iterate on big geometries, although branch " +"predictors of modern CPUs are probably very good at repeatedly evaluating" +" stuff like \"if (!materialized) materialize();\". The main drawback is " +"that is a substantial & risky change that requires to revisit *all* " +"methods of the geometry classes. For setters, you would also have to make" +" sure to invalidate the potentially initial WKB / GEOS source." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:283 +msgid "" +"https://github.com/OSGeo/gdal/compare/master...rouault:gdal:rfc92_implementation?expand=1" +" contains a preliminary candidate implementation." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:286 +msgid "" +"Not all subtleties have been taken into account in the prototype " +"implementation (like doing OGRSQL and requesting the OGR_GEOMETRY special" +" attribute)." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:289 +msgid "" +"OGRLayer::FilterGeometry() (used for spatial filter evaluation by " +"GetNextFeature()) uses OGRWKBOnlyGeometry::Materialize() for convenience " +"currently. This could be improved for geometry types that are directly " +"compatible of GEOS to pass directly the WKB to GEOS." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:297 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:183 +msgid "TBD" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:5 +msgid "RFC 93: OGRLayer::UpdateFeature() method" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:10 +msgid "2023-Feb-15" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:18 +msgid "" +"This RFC adds a new method in the OGRLayer class, UpdateFeature(), to be " +"able to update a subset of the attributes and geometry fields of a " +"feature." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:24 +msgid "" +"There are currently 2 ways of updating (in a broad sense) existing " +"features in drivers that support editing an existing feature:" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:27 +msgid "" +"through the SetFeature() method, which has roughly a Replace semantics. " +"All the fields of the passed feature are used to update the feature" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:29 +msgid "" +"through the UpsertFeature() method. UpsertFeature() semantics is: \"if " +"the passed feature doesn't exist, considering its feature id, then create" +" it, otherwise replace it with the existing feature\". So UpsertFeature()" +" is conceptually CreateFeature() or UpdateFeature()." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:34 +msgid "" +"However a number of use cases only involve updating a subset of the " +"fields of a feature, and not a full replacement:" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:37 +msgid "" +"Typically QGIS changeAttributeValues() and changeGeometryValues() " +"currently have to call GetFeature() on features they want to edit, modify" +" the desired fields and call SetFeature() to update the feature. This is " +"suboptimal from a performance point of view. Similarly pgsql-ogr-fdw " +"could potentially be enhanced to map its implementation of the UPDATE on " +"a OGR foreign table to use UpdateFeature() instead of a full replacement " +"with SetFeature()." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:43 +msgid "" +"SQL based drivers implement SetFeature() through the SQL UPDATE " +"statement, which does not require the full set of attributes to be " +"provided. Consequently UpdateFeature() would be a better match with their" +" native capability. SetFeature() updating all fields, even those not " +"modified, may cause triggers to be unnecessarily run (for example the " +"GeoPackage triggers related to updating the RTree of the spatial index)" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:49 +msgid "" +"no-SQL based drivers such as MongoDB have separate API to replace, upsert" +" or update features." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:51 +msgid "" +"The transactional profile of WFS 2 also distinguishes Update and Replace " +"commands." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:57 +msgid "" +"Similarly to CreateFeature(), SetFeature() and UpsertFeature(), two " +"methods are added in OGRLayer:" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:60 +msgid "" +"UpdateFeature(), non-virtual, and aimed at being the one called by the " +"end user. This method does a few sanity checks on the passed arguments " +"(the arrays containing the indices of the attributes to updated) and " +"convert curve geometries to linear ones if needed for layers that do not " +"support curve geometries (similarly as CreateFeature(), SetFeature() and " +"UpdateFeature())" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:67 +msgid "" +"IUpdateFeature(), virtual method implemented by drivers. A default " +"implementation is provided in the base OGRLayer class for drivers that " +"expose the OLCRandomWrite capability. The default implementation calls " +"GetFeature() to retrieve the current version of the feature, updates it " +"with the feature passed as argument to IUpdateFeature() and calls " +"ISetFeature() to replace the feature." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:74 +msgid "The prototype of UpdateFeature() is the following one:" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:145 +msgid "The corresponding C function ``OGR_L_UpdateFeature`` is added." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:147 +msgid "" +"The OGRLayerDecorator, OGRLayerPool, OGRMutexedLayer, OGRUnionLayer, " +"OGRWarpedLayer and OGREditableLayer utility classes that wrap other " +"layers are modified to take the new IUpdateFeature() virtual method into " +"account." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:154 +msgid "" +"The proposed implementation adds a dedicated implementation of " +"IUpdateFeature() in the following drivers: memory driver, PostgreSQL, " +"GPKG, MongoDB." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:157 +msgid "" +"Other drivers could potentially benefit from it, e.g Shapefile, where " +"separate updates of the .shp (geometries) and .dbf (attributes) files. " +"But not in scope of the initial implementation." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:162 +msgid "Design choices" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:164 +msgid "" +"Q: Why is it necessary to specify which fields of the feature passed to " +"UpdateFeature() should be taken into account?" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:167 +msgid "" +"A: For attributes, it could have been possible to rely on the set/unset " +"status of the fields, but for drivers that distinguish unset from NULL " +"(typically all JSON based drivers, or no-SQL driver which map to " +"key/value documents with a non-fixed schema), this would have make it " +"impossible to unset a field in the stored feature. And geometry fields " +"don't have a unset status, so it would be otherwise be impossible to " +"distinguish between setting the geometry to NULL or not modifying the " +"existing geometry." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:175 +msgid "" +"Q: Why having a default implementation of IUpdateFeature() in the " +"OGRLayer base class and not just returning OGRERR_UNSUPPORTED_OPERATION ?" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:178 +msgid "" +"A: The rationale is to make it easier for code to use UpdateFeature(), " +"even when the underlying driver does not have a specialized " +"implementation. User code that needs to know if a specialized " +"implementation is available (in particular if atomicity of changes is a " +"requirement) can test the OLCUpdateFeature capability (UpdateFeature() is" +" available as soon as the OLCRandomWrite capability is advertized)." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:185 +msgid "" +"Q: Is it appropriate that IUpdateFeature() implementations may alter the " +"feature passed to them ?" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:188 +msgid "" +"A: given that the purpose of UpdateFeature() is to only require the " +"modified fields to be specified, the feature generally cannot be used to " +"reflect the full state of the corresponding stored object. Consequently " +"modifying it has no anticipated drawbacks for intended use cases." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:196 +msgid "OGR_L_UpdateFeature() is mapped to SWIG's ogr.Feature.UpdateFeature()." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:201 +msgid "" +"A benchmark using the below Python script has been run to compare " +"updating a single field on a GeoPackage layer with 3.2 million features, " +"each with 13 attributes and small polygons, of a total size of 1.6 GB." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:205 +msgid "" +"The runtime using the new UpdateFeature() method is 38.5 seconds, versus " +"168 seconds using GetFeature() + SetFeature(), hence a x4.4 speed-up. The" +" speed-up should generally increase with the number of attributes per " +"feature." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:209 +msgid "" +"This is a good simulation of the benefit QGIS changeAttributeValues() " +"implementation could get by using UpdateFeature()." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:246 +msgid "None, new functionality." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:248 +msgid "" +"C++ ABI breakage due to a new virtual method, typical of functionality " +"introduced in GDAL minor versions." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:254 +msgid "The new functions and methods are documented." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:259 +msgid "" +"The API, base implementation and dedicated UpdateFeature() are tested by " +"new autotest checks." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:263 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:173 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:493 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:313 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:725 +msgid "Related issues and PRs" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:265 +msgid "" +"https://github.com/OSGeo/gdal/issues/6544: Extend OGR API SetFeature to " +"control Replace vs Update behavior" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:268 +msgid "" +"https://github.com/qgis/QGIS/issues/46355: Saving a large edited point " +"layer takes far too long" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:271 +msgid "" +"Proposed implementation in " +"https://github.com/OSGeo/gdal/compare/master...rouault:gdal:update_feature?expand=1" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:277 +msgid "+1 from PSC members Jukka, MateuszL and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:5 +msgid "RFC 94: Numeric fields width/precision metadata" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:10 +msgid "2023-Feb-17" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:18 +msgid "" +"The document proposes and describes the introduction of a couple of new " +"vector driver metadata that return information for numeric real fields " +"about how the precision and width have been calculated by the driver and " +"have to be interpreted." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:26 +msgid "" +"Applications (for example OGR/GDAL utils and QGIS) may require " +"information about the field width and precision in order to convert " +"between different formats or to validate user input on editing." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:30 +msgid "" +"Different drivers may calculate the width and precision differently by " +"including or not the decimal separator and/or the minus sign into the " +"calculated length." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:33 +msgid "" +"There is currently no way for an application to access this information " +"and this can lead to loss of width or precision while converting between " +"formats or when the application decides to stay on the safe side and " +"reduce the width reported by GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:37 +msgid "" +"Additionally, attention must be paid to the meaning of \"width\" and " +"\"precision\": OGR \"width\" corresponds to SQL \"precision\" and OGR " +"\"precision\" corresponds to SQL \"scale\"." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:41 +msgid "For reference:" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:43 +msgid "https://trac.osgeo.org/gdal/ticket/6960" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:44 +msgid "https://issues.qgis.org/issues/11755" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:45 +msgid "https://issues.qgis.org/issues/15188#note-8" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:46 +msgid "https://github.com/qgis/QGIS/issues/51849" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:50 +msgid "Current drivers behavior" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:52 +msgid "" +"Here is a list of the drivers and how they behave with respect to the " +"width and precision, (for databases we refer to the `NUMERIC` data type)." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:56 +msgid "Driver" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:56 +msgid "Width Includes Decimal Separator" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:56 +msgid "Width Includes Sign" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:58 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:59 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:65 +msgid "YES" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:59 +msgid "MapInfo" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:60 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:61 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:62 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:63 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:66 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:67 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:69 +msgid "NO" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:62 +msgid "MSSQL" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:64 +msgid "GPKG" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:65 +msgid "CSV (from .csvt)" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:66 +msgid "HANA" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:67 +msgid "FlatGeoBuf" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:70 +msgid "MEM" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:75 +msgid "Notes about specific drivers" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:77 +msgid "GPKG: SQLite column affinity storage is 8-byte IEEE floating point number" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:78 +msgid "" +"GML: `xsd:decimal` with `totalDigits` and `fractionDigits`, " +"`xs:totalDigits` defines the maximum number of digits of decimal and " +"derived datatypes (both after and before the decimal point, not counting " +"the decimal point itself). `xs:fractionDigits`` defines the maximum " +"number of fractional digits (i.e., digits that are after the decimal " +"point) of an xs:decimal datatype." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:83 +msgid "" +"FlatGeoBuf: for Float fields, OGR_width = flatgeobuf_precision and " +"OGR_precision = flatgeobuf_scale (if flatgeobuf_scale != -1, or 0 if " +"flatgeobuf_scale == -1)" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:85 +msgid "" +"FileGDB: Scale is the number of digits to the right of the decimal point " +"in a number. For example, the number 56.78 has a scale of 2. Scale " +"applies only to fields that are double. Scale is always returned as 0 " +"from personal or File geodatabase fields. Precision is the number of " +"digits in a number. For example, the number 56.78 has a precision of 4. " +"Precision is only valid for fields that are numeric. Precision is always " +"returned as 0 from personal or File geodatabase fields" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:95 +msgid "" +"The change will be done at the driver metadata level with a couple of " +"flags that report the capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:98 +msgid "" +"The vector drivers will expose a metadata entry to define if the width of" +" the fields includes the decimal separator and/or the sign." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:101 +msgid "" +"If the metadata entry is undefined the feature is not supported (there is" +" no client-accessible width or precision constraint for numeric fields)." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:104 +msgid "" +"The feature will be exposed to the `ogr2ogr` application with a switch to" +" enable/disable the width reduction when converting from a format where " +"width includes the minus sign to a format where it doesn't. This is " +"useful when the user knows that the input data are all negative values " +"because in that that case it won't be necessary to add the extra width to" +" store it." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:109 +msgid "" +"To clarify, when converting from DBF to SQL the width is decreased by 1, " +"when converting from SQL to DBF the width is increased by 2." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:112 +msgid "" +"\"-1.23\" for .DBF needs width=5 and precision=2. In SQL, it needs " +"precision=3 and scale=2 \"12.34\" for DBF needs width=5 and precision=2. " +"In SQL, it needs precision=4 and scale=2" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:115 +msgid "" +"This means that when converting from DBF to SQL we can safely reduce the " +"width by 1 but we cannot safely reduce it by 2 unless we are sure all " +"values are negative." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:158 +msgid "This implementation will be exposed to bindings." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:169 +msgid "+1 from PSC members EvenR and JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:5 +msgid "RFC 95: Use standard C/C++ integer types (proposed, *NOT* adopted)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:10 +msgid "2023-Sep-15" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:11 +msgid "Proposed, but *not* adopted" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:12 +msgid "GDAL 4.0" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:18 +msgid "" +"This RFC replaces the use of the custom integer types defined in " +"cpl_port.h (G[U]Int[8/16/32/64/Big]) by their standard " +"[u]int[8/16/32/64]_t C99/C++11 counterparts, as well as other derived " +"integer data types. Due to the API and ABI break, this will be " +"implemented in GDAL 4.0." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:26 +msgid "" +"The existing Gxxxxx typedefs have been defined at a time that predates " +"C99 and C++11 which introduced those fixed with integer types. If GDAL " +"would be created today, we would use C99 data types." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:30 +msgid "" +"Using those aliases, particularly GIntBig/GUIntBig which are not self-" +"explanatory on their actual width (64 bit), adds cognitive load to " +"developers." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:34 +msgid "" +"Due to their poor namespacing, those short typenames may occasionally " +"clash with other libraries. At a time, Poppler used a ``GBool`` data type" +" as well, which was clashing with GDAL's one." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:38 +msgid "" +"Other projects (e.g. libtiff), have recently switched from the use of " +"similar custom types to C99 ones." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:44 +msgid "The following data types replacement are done in the whole code base:" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:46 +msgid "``GBool`` --> ``bool`` (``GBool`` was aliased to ``int``)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:47 +msgid "``GInt8`` --> ``int8_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:48 +msgid "``GInt16`` --> ``int16_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:49 +msgid "``GUInt16`` --> ``uint16_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:50 +msgid "``GInt32`` --> ``int32_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:51 +msgid "``GUInt32`` --> ``uint32_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:52 +msgid "``GInt64`` --> ``int64_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:53 +msgid "``GUInt64`` --> ``uint64_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:54 +msgid "``GIntBig`` --> ``int64_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:55 +msgid "``GUIntBig`` --> ``uint64_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:57 +msgid "Other changes have been done for other integer data types:" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:59 +msgid "``vsi_l_offset``--> ``uint64_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:60 +msgid "``GSpacing`` --> ``int64_t`` (affects mostly C++ raster drivers)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:61 +msgid "" +"``GPtrDiff_t`` --> ``ptrdiff_t`` (affects the multidimensional C and " +"C++ API)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:63 +msgid "The following macro replacement are done in the whole code base:" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:65 +msgid "``CPL_FRMT_GIB`` --> ``\"%\" PRId64``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:66 +msgid "``CPL_FRMT_GUIB`` --> ``\"%\" PRIu64``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:67 +msgid "``GINT64_MAX`` --> ``std::numeric_limits::max()``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:68 +msgid "``GINT64_MIN`` --> ``std::numeric_limits::min()``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:69 +msgid "``GUINT64_MAX`` --> ``std::numeric_limits::max()``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:70 +msgid "``GINTBIG_MAX`` --> ``std::numeric_limits::max()``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:71 +msgid "``GINTBIG_MIN`` --> ``std::numeric_limits::min()``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:72 +msgid "``GUINTBIG_MAX`` --> ``std::numeric_limits::max()``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:74 +msgid "" +"The old types are no longer used in the GDAL code base since their " +"definition is protected by ``#ifdef GDAL_USE_OLD_INT_TYPES``, which " +"external code might define to help for the migration (particularly if " +"supporting GDAL < 4.0 and GDAL >= 4.0 is needed)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:80 +msgid "Impacts in the code base" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:82 +msgid "" +"Significant part of the code base (735 files changed). Most changes have " +"been done in a automated way, with manual changes specifically for the " +"CPL_FRMT_GIB/CPL_FRMT_GUIB replacement which was harder to automate." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:90 +msgid "" +"While .i files are impacted to cope with the C type changes, the language" +" specific API of SWIG bindings is not impacted." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:96 +msgid "C and C++ API and ABI are impacted." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:98 +msgid "Main impacts are:" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:100 +msgid "" +"GBool was aliased to ``int``: changing to ``bool`` in C++ methods of the " +"OGRStyleXXXX classes affect the API and ABI. Impact should be modest as " +"this functionality is thought to be marginally used, and this only " +"impacts the C++ API (the C API for those methods uses ``int`` and not " +"``GBool``)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:105 +msgid "" +"GIntBig/GInt64 was aliased to ``long long`` and GUIntBig/GUInt64 to " +"```unsigned long long``. While ``int64_t`` and ``long long`` have in " +"practice same width and signedness, they are formally different data " +"types. For scalar usage of those types, compilers shouldn't warn. But for" +" usage of those types as pointers, compilers warn in C (``-Wincompatible-" +"pointer-types`` with gcc) and error outs in C++ (unless ``-fpermissive`` " +"is passed), when mixing a ``int64_t`` pointer and a ``long long`` pointer" +" (similarly for their unsigned counterparts)." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:115 +msgid "C Raster API impacts (and equivalent C++ methods):" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:117 +msgid ":cpp:func:`GDALGetDefaultHistogramEx` (e.g. used by QGIS)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:118 +msgid ":cpp:func:`GDALSetDefaultHistogramEx`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:119 +msgid ":cpp:func:`GDALGetRasterHistogramEx` (e.g. used by QGIS)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:120 +msgid ":cpp:func:`GDALGetVirtualMemAuto`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:122 +msgid "C Vector API impacts (and equivalent C++ methods):" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:124 +msgid ":cpp:func:`OGR_F_GetFieldAsInteger64List`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:125 +msgid ":cpp:func:`OGR_F_SetFieldInteger64List`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:127 +msgid "C Multidimension API impacts (and equivalent C++ methods):" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:129 +msgid ":cpp:func:`GDALGroupCreateDimension`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:130 +msgid ":cpp:func:`GDALGroupCreateAttribute`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:131 +msgid ":cpp:func:`GDALMDArrayRead`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:132 +msgid ":cpp:func:`GDALMDArrayWrite`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:133 +msgid ":cpp:func:`GDALMDArrayAdviseRead`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:134 +msgid ":cpp:func:`GDALMDArrayAdviseReadEx`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:135 +msgid ":cpp:func:`GDALMDArrayCreateAttribute`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:136 +msgid ":cpp:func:`GDALMDArrayResize`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:137 +msgid ":cpp:func:`GDALMDArrayGetBlockSize`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:138 +msgid ":cpp:func:`GDALMDArrayGetStatistics`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:139 +msgid ":cpp:func:`GDALMDArrayComputeStatistics`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:140 +msgid ":cpp:func:`GDALMDArrayComputeStatisticsEx`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:141 +msgid ":cpp:func:`GDALAttributeGetDimensionsSize`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:143 +msgid "Out-of-tree drivers are also impacted:" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:145 +msgid "" +"the vector ones that implement :cpp:func:`OGRLayer::ISetFeature`, " +":cpp:func:`OGRLayer::SetNextByIndex`, " +":cpp:func:`OGRLayer::DeleteFeature`, " +":cpp:func:`OGRLayer::GetFeatureCount`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:149 +msgid "" +"the ones that implement the multidimensional API (no publicly ones known " +"by us)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:152 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:287 +msgid "Risks" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:154 +msgid "" +"The changes of this RFC are somewhat risky, particularly the replacement " +"of the formatting macros CPL_FRMT_GIB/CPL_FRMT_GUIB with the " +"PRId64/PRIu64 ones, which requires to add a ``%`` formatting character. " +"While compilers caught most of the mismatches, there were remaining ones " +"undetected at compilation time. Manual corrections have been done to make" +" the regression test suite pass. Additional \"grep\"-based searches in " +"the code base have been done to find faulty patterns, but we cannot " +"exclude that some might have been missed." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:165 +msgid "MIGRATION_GUIDE.TXT will be updated to point to this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:170 +msgid "No changes in Python tests. Updates in the C++ test suite.`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:175 +msgid "" +"https://github.com/OSGeo/gdal/issues/8288: Consider using standard C/C++ " +"integer types" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:178 +msgid "https://github.com/OSGeo/gdal/pull/8396: candidate implementation" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:5 +msgid "RFC 96: Deferred C++ plugin loading" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:10 +msgid "2023-Nov-01" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:12 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:12 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:11 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:12 +msgid "GDAL 3.9" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:18 +msgid "" +"This RFC adds a mechanism to defer the loading of C++ plugin drivers to " +"the point where their executable code is actually needed, and converts a " +"number of relevant drivers to use that mechanism. The aim is to allow for" +" more modular GDAL builds, while improving the performance of plugin " +"loading." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:23 +msgid "" +"It mostly targets in-tree plugin drivers, but it also provides a way for " +"out-of-tree plugin drivers to benefit from deferred loading capabilities," +" provided libgdal is built in a specific way" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:28 +msgid "Context and motivation" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:30 +msgid "There are currently two ways of loading a GDAL C++ driver:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:32 +msgid "" +"embedded in the core libgdal library. This is the default behavior for " +"drivers in the official GDAL source repository." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:35 +msgid "" +"available in a shared library (.so, .dll, .dylib) in a directory where it" +" is dynamically loaded when GDALAllRegister() is called. This is what " +"out-of-tree drivers use, or in-tree drivers if enabling the " +"[GDAL|OGR]_ENABLE_DRIVER_FOO_PLUGIN=ON or GDAL_ENABLE_PLUGINS=ON CMake " +"options (cf https://gdal.org/development/building_from_source.html#build-" +"drivers-as-plugins) to build them as plugins." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:42 +msgid "" +"For packagers/distributors, the second option is convenient for in-tree " +"drivers that depend on external libraries that are big and/or have a big " +"number of dependencies (libparquet, etc) and that would substantially " +"increase the size of the core libgdal library, or which have licenses " +"more restrictive than the MIT license used by libgdal." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:48 +msgid "" +"However, there is a penalty at GDALAllRegister() time. For example, on " +"Linux, it takes ~ 300 ms to complete for a build with 126 plugins, which " +"is a substantial time for short lived GDAL-based processes (for example a" +" script which would run gdalinfo or ogrinfo on many files). This time is " +"entirely spent in the dlopen() method of the operating system and there " +"is, to the best of our knowledge, nothing we can do to reduce it... " +"besides limiting the amount of dynamic loading (attempts have been made " +"to load plugins in parallel in multiple threads, but this does not " +"improve total loading time) For developers, that plugin loading phase is " +"actually considerably slower, of the order of ten seconds or more, when " +"debugging GDAL under GDB with many plugin drivers." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:60 +msgid "" +"Furthermore, loading drivers that are not needed also involves some " +"startup/teardown code of external libraries to be run, as well as more " +"virtual memory to be consumed. Hence this proposal of deferring the " +"actual loading of the shared library of the plugins until it is really " +"needed." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:66 +msgid "Design constraints" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:68 +msgid "We want the new mechanism to be opt-in and fully backwards compatible:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:70 +msgid "to still allow out-of-tree drivers." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:72 +msgid "" +"to still allow in-tree drivers, that are compatible of being built as " +"plugins, to be built in libgdal core, or as plugins depending on the " +"CMake variables." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:75 +msgid "to progressively convert existing in-tree drivers to use it." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:77 +msgid "" +"to provide the capability to out-of-tree drivers to optionally benefit " +"from the new capability, provided they build GDAL with the code needed to" +" declared a plugin proxy driver." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:84 +msgid "" +"The main idea if that drivers using the new capability will register a " +"proxy driver (of type GDALPluginDriverProxy, or extending it) with a new " +"GDALDriverManager::DeclareDeferredPluginDriver() method." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:134 +msgid "" +"The proxy driver uses the metadata items that have been set on it to " +"declare a minimum set of capabilities (GDAL_DCAP_RASTER, " +"GDAL_DCAP_MULTIDIM_RASTER, GDAL_DCAP_VECTOR, GDAL_DCAP_OPEN, etc.) to " +"which it can answer directly, and which are the ones used by GDALOpen() " +"to open a dataset. For other metadata items, it will fallback to loading " +"the actual driver and forward the requests to it." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:152 +msgid "" +"DeclareDeferredPluginDriver() method will also keep track of the plugin " +"filename to avoid automatically loading it in the " +"GDALDriverManager::AutoLoadDrivers() method (that method will only load " +"out-of-tree drivers or in-tree drivers that have not been converted to " +"use DeclareDeferredPluginDriver())." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:157 +msgid "" +"The main point is that drivers set the Identify() method on the proxy " +"driver. That Identify() method must be compiled in libgdal itself, and " +"thus be defined in a C++ file that does not depend on any external " +"library. Similarly for the GetSubdatasetInfoFunc() optional method." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:162 +msgid "" +"When loading the actual driver, the " +"GDALPluginDriverProxy::GetRealDriver() method will check that all " +"information set in its metadata is consistent with the actual metadata of" +" the underlying driver, and will warn when there are differences." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:167 +msgid "" +"GDALDataset::Open(), Create(), CreateCopy() methods are modified to not " +"use directly the pfnOpen, pfnCreate, pfnCreateCopy callbacks (that would " +"be the ones of the proxy driver, and thus nullptr), but to call new " +"GetOpenCallback()/ GetCreateCallback()/GetCreateCopyCallback() methods " +"that the GDALProxyDriver class overloads to return the function pointers " +"of the real driver, once it has loaded it." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:174 +msgid "" +"The DeclareDeferredPluginDriver() method checks if the file of the plugin" +" exists before registering it. If it is not available, a CPLDebug() " +"message is emitted. This allows to build a \"universal\" core libgdal, " +"with plugins that can be optionally available at runtime." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:179 +msgid "" +"Cherry-on-the-cake: GDALOpen() will given an explicit error message if it" +" identifies a dataset to a plugin that is not available at runtime. " +"Example::" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:188 +msgid "" +"For each driver supporting deferred plugin loading, GDALAllRegister() " +"must be modified to call a driver-specific function that calls " +"GDALDriverManager::DeclareDeferredPluginDriver() (see example in below " +"paragraph). This code path is enabled only when the driver is built as " +"plugin." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:196 +msgid "Example of changes to do on a simplified driver" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:198 +msgid "" +"In the :file:`CMakeLists.txt` file of a driver, the new option " +"CORE_SOURCES can be passed to ``add_gdal_driver()`` to define source " +"file(s) that must be built in libgdal, even when the driver is built as a" +" plugin." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:214 +msgid "A typical :file:`mydrivercore.h`` header will declare the identify method:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:227 +msgid "" +"And :file:`mydrivercore.cpp` will contain the implementation of the " +"identify method, a ``FOODriverSetCommonMetadata()`` method (with most of " +"the content of the normal driver registration method, except for function" +" pointers such as pfnOpen, pfnCreate, pfnCreateCopy or " +"pfnCreateMultiDimensional), as well as a ``DeclareDeferredXXXPlugin()`` " +"method that will be called by GDALAllRegister() when the driver is built " +"as a plugin (the PLUGIN_FILENAME macro is automatically set by the CMake " +"scripts with the filename of the plugin, e.g. \"gdal_FOO.so\"):" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:268 +msgid "" +"The GDALRegisterFoo() method itself, which is defined in the plugin code," +" calls ``FOODriverSetCommonMetadata``, and defines the pfnOpen, " +"pfnCreate, pfnCreateCopy, pfnCreateMultiDimensional callbacks when they " +"exist:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:290 +msgid "The modified :file:`gdalallregister.cpp` file will look like:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:321 +msgid "This can be done with the following CMake option:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:325 +msgid "" +"The pointed file must declare a ``void " +"DeclareDeferred(void)`` method with C linkage that takes " +"care of creating a GDALPluginDriverProxy instance and calling " +"GDALDriverManager::DeclareDeferredPluginDriver() on it." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:332 +msgid "" +"One could imagine a further enhancement for out-of-tree plugins where " +"they would be accompanied by a sidecar text file that would for example " +"declare the driver capabilities, as well as a limited implementation of " +"the identify method as a regular expression. But that is out-of-scope of " +"this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:338 +msgid "" +"Changes in the loading of OGR Python drivers (see :ref:`rfc-76`) are also" +" out-of-scope of this RFC (they will continue to be loaded at " +":cpp:func:`GDALAllRegister` time)." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:343 +msgid "Candidate implementation" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:345 +msgid "" +"A candidate implementation has been started to implement all the core " +"mechanism, and convert the Parquet, netCDF and HDF5 drivers. The HDF5 " +"plugin is actually a good stress test for the deferred loading mechanism," +" since it incorporates 4 drivers (HDF5, HDF5Image, BAG and S102) in the " +"same shared object. The plan is to update progressively all in-tree " +"drivers that depend on third-party libraries (that is the one that are " +"built as plugins when setting the GDAL_ENABLE_PLUGINS=YES CMake options)." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:353 +msgid "" +"Tests have also been done with QGIS (with the changes at " +"https://github.com/qgis/QGIS/pull/55115) to check that the declared set " +"of metadata items in GDALPluginDriverFeatures is sufficient to avoid " +"loading of the actual drivers at QGIS startup (they are only loaded when " +"a dataset of the format handled by the driver is identified)" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:362 +msgid "Expected to be backward compatible for most practical purposes." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:364 +msgid "" +"Drivers that would request a driver instance with GDALGetDriverByName() " +"may now get a GDALPluginDriverProxy instance instead of the \"real\" " +"driver instance. This is usually not an issue as few drivers subclass " +"GDALDriver, but that issue was hit on the PostGISRasterDriver that did " +"subclass it. The solution was to store the real PostGISRasterDriver " +"instance when it is built in a global variable, and use that global " +"variable instead of the one returned by GDALGetDriverByName()." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:371 +msgid "" +"Another potential issue is that if external code would directly use the " +"pfnOpen, pfnCreate, pfnCreateCopy, etc. function pointers of a GDALDriver" +" instance, it would see them null before the actual driver is loading, " +"but direct access to those function pointers has never been documented " +"(instead users should use GDALOpen(), GDALCreate(), GDALCreateCopy() " +"etc), and is not expected to be done by code external to libgdal core." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:378 +msgid "" +"However, the candidate implementation hits an issue with the way the GDAL" +" CondaForge builds work currently. At time of writing, the GDAL " +"CondaForge build recipee does:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:382 +msgid "" +"a regular GDAL build without Arrow/Parquet dependency (and thus without " +"the driver), whose libgdal.so goes in to the libgdal package." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:384 +msgid "installs libarrow and libparquet" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:385 +msgid "" +"does an incremental GDAL build with -DOGR_ENABLE_DRIVER_FOO_PLUGIN=ON to " +"generate ogr_Arrow.so and ogr_Parquet.so. However with the above new " +"mechanism, this will result in libgdal to be modified to have a " +"DeclareDeferredOGRParquetPlugin function, as well as including the " +"identification method of the Parquet plugin. But that modified libgdal.so" +" is discarded currently, and the ogr_Parquet.so plugin then depends on a " +"identify method that is not implemented." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:392 +msgid "" +"The initial idea was that the build recipee would have to be modified to " +"produce all artifacts (libgdal.so and libparquet.so) at a single time, " +"and dispatch them appropriately in libgdal and libgdal-arrow-parquet " +"packages, rather than doing two builds. However, CondaForge builds " +"support several libarrow versions, and produce thus different " +"Arrow/Parquet plugins, so this approach would not be practical." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:399 +msgid "" +"To solve this, the following idea has been implemented. Extract from the " +"updated :ref:`building_from_source` document::" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:481 +msgid "" +":ref:`raster_driver_tut` and :ref:`vector_driver_tut` will be updated to " +"point to this RFC. :ref:`building_from_source` will receive the new " +"paragraph mentioned above." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:488 +msgid "" +"A C++ test will be added testing that for one of the updated drivers, the" +" plugin is loaded in a deferred way in situations where this is expected," +" and is not loaded in other situations." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:495 +msgid "https://github.com/OSGeo/gdal/pull/8695: candidate implementation" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:498 +msgid "Adjustments done post GDAL 3.9.0, for GDAL 3.9.1" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:500 +msgid "" +"After GDAL 3.9.0 release, it has been noticed that the following setup " +"which used to work in prior releases no longer worked:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:503 +msgid "Step 1: building libgdal without support for driver X" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:504 +msgid "" +"Step 2: building driver X as a plugin, discarding the libgdal share " +"library," +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:505 +msgid "built at that stage" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:507 +msgid "" +"Step 3: using driver X built as a plugin against libgdal built at step 1." +" In that" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:507 +msgid "" +"scenario, driver X is expected to be loaded as if it was an out-of-tree " +"drivers." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:509 +msgid "" +"Such scenario is used when delivering a fully open-source libgdal without" +" any prior knowledge of which drivers could be later built as plugins, or" +" for which pre-configuring libgdal to support such drivers is not " +"practical because they rely on a proprietary SDK and the identification " +"method and/or driver metadata depends on the availability of the SDK " +"include files (e.g. MrSID)." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:515 +msgid "" +"Starting with GDAL 3.9.1, the ``add_gdal_driver()`` function in the " +"CMakeLists.txt of drivers which use the ``CORE_SOURCES`` keyword must " +"also declare the ``NO_SHARED_SYMBOL_WITH_CORE`` keyword, so that the " +"files pointed by CORE_SOURCES are built twice: once in libgdal with a " +"``GDAL_core_`` prefix, and another time in the plugin itself with a " +"``GDAL_driver_`` prefix, by using the PLUGIN_SYMBOL_NAME() macro of " +":file:`gdal_priv.h`." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:522 +msgid "Example in ogr/ogrsf_frmsts/oci/CMakeLists.txt:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:533 +msgid "Example in ogrocidrivercore.h:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:547 +msgid "" +"A consequence of that change is that drivers built as a plugin against " +"GDAL 3.9.0 will not be loadable by GDAL 3.9.1 (or later patch in the 3.9 " +"series), because they relied on driver-specific functions that are no " +"longer exported by libgdal >= 3.9.1." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:551 +msgid "" +"After that, things should work as they used to, and drivers built against" +" libgdal 3.9.1 should work against libgdal 3.9.2 for example." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:554 +msgid "" +"Also note that the above only affects *in-tree* plugin drivers. Out-of-" +"tree plugin drivers are not affected." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:560 +msgid "+1 from PSC members KurtS, HowardB, JukkaR, JavierJS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:5 +msgid "RFC 97: OGRFeatureDefn, OGRFieldDefn and OGRGeomFieldDefn \"sealing\"" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:10 +msgid "2023-Nov-16" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:18 +msgid "" +"This RFC aims at avoiding common misuse of the setter methods of the " +"OGRFeatureDefn, OGRFieldDefn and OGRGeomFieldDefn classes. Indeed, the " +"setter methods of those classes should not be used directly by user code " +"(that is non driver implementations), on instances that are owned by a " +"OGRLayer. It is quite frequent for users (even seasoned ones) to neglect " +"that constraint. Hence this RFC introduces an optional \"sealing\" " +"capability that drivers can enable to avoid users modifying instances " +"that they should not." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:29 +msgid "" +"Let's take an example to clarify. We want to prevent a user from doing " +"the following:" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:36 +msgid "" +"The above code will not raise any warning or error at runtime, but will " +"not change the underlying on-disk dataset to reflect the new field name. " +"Indeed poLayer->GetLayerDefn() and its child objects should be considered" +" immutable, unless using dedicated methods of OGRLayer to modify them. " +"The correct way of renaming an existing field is (for drivers that " +"support such capability):" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:48 +msgid "" +"For other operations, such as calling " +":cpp:func:`OGRFieldDefn::AddFieldDefn()` or " +":cpp:func:`OGRFieldDefn::DeleteFieldDefn()` on an instance of " +"OGRLayer::GetLayerDefn(), crashes could potentially occur in drivers that" +" are not ready to see the number of fields to change behind their back. " +"The correct way of adding or deleting fields to a layer is to use " +":cpp:func:`OGRLayer::CreateField()` or " +":cpp:func:`OGRLayer::DeleteField()`" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:58 +msgid "" +"A ``bool m_bSealed`` member variable is added to the " +":cpp:class:`OGRFieldDefn` and :cpp:class:`OGRGeomFieldDefn` classes. Its " +"default value is false, meaning that calling setters method on instances " +"of those classes is allowed by default." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:63 +msgid "" +"The following methods are added on :cpp:class:`OGRFieldDefn` (and " +"similarly for :cpp:class:`OGRGeomFieldDefn`)" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:97 +msgid "" +"All setter methods of those classes are modified to check the value of " +"``m_bSealed``. If it is set, a CE_Failure CPLError() is emitted " +"indicating that the object is sealed. Unfortunately most setters return " +"``void``, so there is no way to advertise the error through an error " +"code. However, when using the Python bindings with exceptions enabled, a " +"Python exception will be thrown." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:103 +msgid "" +"A convenience method is also offered to use the Resource Acquisition Is " +"Initialization (RAII) paradygm to temporary unseal an instance, which is " +"an operation that drivers implementing AlterFieldDefn() / " +"AlterGeomFieldDefn() will need to do on fields they have priorly sealed." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:124 +msgid "Typical usage is by AlterFieldDefn() / AlterGeomFieldDefn() is:" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:138 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:215 +msgid "" +"For punctual changes, a convenience ``whileUnsealing`` function is also " +"provided." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:141 +msgid "It can be used as in the following:" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:148 +msgid "" +"For OGRFeatureDefn, similar changes are done but with an extra subtelty. " +"For convenience of drivers, we want a driver to be able to call " +"GetTemporaryUnsealer() in a nested way, where only the first/most " +"external call does something, and next/nested ones are a no-operation. " +"This is similar to using a recursive mutex from the same thread. The user" +" can also indicate if it wishes fields and geometry fields owned by the " +"OGRFeatureDefn to be sealed/unsealed at the same time." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:218 +msgid "" +"In practice, the only Seal() invocation in driver core should be done on " +"the OGRFeatureDefn instance they return with GetLayerDefn(). All " +"subsequent sealing/unsealing operations should be done through " +"OGRFeatureDefn::GetTemporaryUnsealer()" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:224 +msgid "Example of a typical driver" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:226 +msgid "Constructor of the OGRLayer subclass:" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:240 +msgid "Simple CreateField() implementation:" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:253 +msgid "" +"Why not just having a ``const OGRFeatureDefn* OGRLayer::GetLayerDefn() " +"const`` method ?" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:256 +msgid "" +"That would only work when using the C++ API (and would require changes in" +" all drivers to modify the signature, as well as doing changes at places " +"where drivers require a non-const OGRFeatureDefn*), because const " +"correctness is not available in the C API and the SWIG bindings." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:264 +msgid "" +"No impact. Those C++ methods are intended to be used by driver " +"implementation only." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:270 +msgid "" +"For the initial implementation, the following drivers are updated to seal" +" their layer definition: GeoPackage, PostgreSQL, Shapefile, OpenFileGDB, " +"MITAB, Memory, GeoJSON, JSONFG, TopoJSON, ESRIJSON, ODS, XLSX." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:278 +msgid "" +"C API is unchanged. Backwards compatible addition to the C++ API (ABI " +"change)" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:280 +msgid "" +"There is the possibility to break user code that mis-used the API. For " +"example, this was the case of a few tests in the autotest suite that have" +" had to be modified." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:284 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:695 +msgid "MIGRATION_GUIDE.TXT will mention that and point to this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:289 +msgid "" +"Drivers that implement sealing should make sure they unseal at the " +"appropriate places: OGRLayer::Rename(), CreateField(), DeleteField(), " +"CreateGeomField(), DeleteGeomField(), ReorderFields(), AlterFieldDefn() " +"AlterGeomFieldDefn() and any other places where they might modify " +"objects. Failure to do so will result in failures, and potentially " +"crashes. Hence implementation of sealing should only be done on drivers " +"that have sufficient test coverage." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:300 +msgid "" +"The documentation of the setters as well as the introduction text of " +"OGRFeatureDefn, OGRFieldDefn and OGRGeomFieldDefn is modified to reflect " +"that setters of those classes should not be called on instances returned " +"by OGRLayer::GetLayerDefn()." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:308 +msgid "The autotest suite is modified to comply with sealing" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:309 +msgid "" +"Calls to setters on sealed instances will be done to test that an error " +"is triggered." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:315 +msgid "Candidate implementation in https://github.com/OSGeo/gdal/pull/8733" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:320 +msgid "+1 from PSC members JukkaR, JavierJS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:5 +msgid "RFC 98: Build requirements for GDAL 3.9" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:9 +msgid "2023-Nov-23" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:17 +msgid "" +"The document updates :ref:`rfc-68` with the new build requirements for " +"GDAL 3.9:" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:19 +msgid "C++ >= 17" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:20 +msgid "CMake >= 3.16" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:21 +msgid "PROJ >= 6.3.1." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:23 +msgid "" +"The minimum version for the following optional dependencies is also " +"updated:" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:26 +msgid "GEOS >= 3.8" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:27 +msgid "Poppler >= 0.86" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:28 +msgid "libtiff >= 4.1" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:29 +msgid "libcurl >= 7.68" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:30 +msgid "libpng >= 1.6.0" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:31 +msgid "libsqlite3 >= 3.31" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:32 +msgid "libopenjp2 >= 2.3.1" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:33 +msgid "libnetcdf >= 4.7 and built with NC4 enabled" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:34 +msgid "libhdf5 >= 1.10" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:39 +msgid "" +"Our past build requirements were C++11, CMake 3.9, and PROJ 6.0.0. All of" +" them correspond to now outdated versions of those components, and it " +"makes sense to update to more up-to-date versions to be able to clean up " +"code, leverage new capabilities and be consistent with the current state " +"of our software environment." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:44 +msgid "" +"The proposed updates are all compatible with versions of those components" +" available by default in the old LTS (Long Term Support) Ubuntu 20.04, " +"which corresponds to the oldest environment used by our continuous " +"integration:" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:48 +msgid "" +"C++17 is the minimum version required by the latest versions of some of " +"our C++ dependencies, including Poppler, PDFium, PoDoFo, TileDB, " +"libarrow-cpp. Ubuntu 20.04 includes GCC 9.4, which supports C++17. While " +"we want to allow C++17 features to build GDAL, for now, we will stick to " +"exposing at most C++11 features in the exported headers of the library to" +" minimize disruption for GDAL C++ users. That might be revisited later. " +"At the time of writing, the C++17 requirement has already been " +"implemented in master / 3.9.0dev." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:57 +msgid "" +"CMake 3.16.0 was released in November 2019. Updating to CMake 3.16 " +"enables us to make a number of cleanups in GDAL CMakeLists.txt scripts, " +"and in particular to make it possible to use the " +"[CMAKE_UNITY_BUILD](https://cmake.org/cmake/help/latest/variable/CMAKE_UNITY_BUILD.html)" +" feature. Ubuntu 20.04 includes CMake 3.16.4." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:63 +msgid "" +"PROJ 6.3.1 was released in February 2020. Updating to that version " +"implies PROJ >= 6.2 and the availability of PROJJSON output, and PROJ >= " +"6.3 enables us to remove a few specific code paths in ogrct.cpp. Ubuntu " +"20.04 includes PROJ 6.3.1. Earlier PROJ 6.x versions had a number of " +"annoying issues." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:68 +msgid "" +"By the time GDAL 3.9 is released (May 2024), all the above requirements " +"correspond to versions of the tools/libraries that have been released " +"more than 4 years earlier." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:72 +msgid "" +"More generally, we also update requirements for optional dependencies to " +"be consistent with the versions available in Ubuntu 20.04, to eliminate " +"code paths that are no longer exercised by our continuous integration:" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:76 +msgid "" +"Python >= 3.8: Python 3.7 is already end-of-life " +"(https://devguide.python.org/versions/) Python 3.8 is the minimum version" +" used by our CI" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:78 +msgid "" +"GEOS >= 3.8: ensures that MakeValid() is available when GEOS is " +"available, which simplifies the code base and test suite" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:80 +msgid "Poppler >= 0.86: removes a lot of #ifdef trickery in the PDF driver" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:81 +msgid "libtiff >= 4.1: simplifies a few code paths in the GeoTIFF driver" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:82 +msgid "libcurl >= 7.68: removes outdated code paths in CPL networking code" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:83 +msgid "libpng >= 1.6.0: removes outdated code paths in the PNG driver" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:84 +msgid "" +"libsqlite3 >= 3.31: removes outdated code paths in the SQLite and GPKG " +"drivers" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:85 +msgid "libopenjp2 >= 2.3.1: removes outdated code paths in the OpenJPEG driver" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:86 +msgid "" +"libnetcdf >= 4.7 built with NC4 support enabled (i.e. libnetcdf built " +"against libhdf5): removes #ifdef code paths in netCDF driver. The netCDF " +"multidimensional code already requires NC4." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:89 +msgid "libhdf5 >= 1.10: removes outdated code paths in the HDF5 driver" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:92 +msgid "C++17 capable compilers" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:94 +msgid "" +"From https://en.wikipedia.org/wiki/C%2B%2B17, compilers supporting C++17 " +"are:" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:96 +msgid "GCC >= 8" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:97 +msgid "clang >= 5" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:98 +msgid "Visual Studio >= 2017 15.8 (MSVC 19.15)" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:101 +msgid "C++14 and C++17 features" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:103 +msgid "Features that can be used in the code base (not an exhaustive list):" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:105 +msgid "Use of ``std::make_unique<>`` instead of ``cpl::make_unique<>``" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:106 +msgid "Use of ``[[fallthrough]]`` instead of ``CPL_FALLTHROUGH``" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:107 +msgid "Use of ``[[maybe_unused]]`` instead of ``CPL_UNUSED``" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:108 +msgid "" +"Nicer iteration in ``std::map`` with ``for (const auto &[key, value]: " +"my_map )`` (more generally \"structured binding declarations\")" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:111 +msgid "Banned features:" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:113 +msgid "" +"Use of ``std::filesystem`` (https://en.cppreference.com/w/cpp/filesystem)" +" is not appropriate since our existing :cpp:class:`VSIFilesystemHandler` " +"mechanism has broader support for all our /vsi specific file systems." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:118 +msgid "Changes in continuous integration" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:120 +msgid "" +"Continuous integration is modified to test configurations that have at " +"least the new set of build requirements." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:131 +msgid "No change in API and ABI" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:136 +msgid "The Build requirements documentation page will be updated." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:144 +msgid "Related tickets / pull requests" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:146 +msgid "" +"https://github.com/OSGeo/gdal/pull/8680: CI: Remove Ubuntu 18.04 " +"configurations" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:147 +msgid "https://github.com/OSGeo/gdal/issues/8270: Bump to C++17" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:148 +msgid "" +"https://github.com/OSGeo/gdal/pull/8687: Switch default C++ standard to " +"C++17" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:149 +msgid "https://github.com/OSGeo/gdal/pull/8710: Cxx17 tunings" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:150 +msgid "" +"https://github.com/OSGeo/gdal/pull/8716: C++17: use if constexpr() " +"construct" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:151 +msgid "" +"https://github.com/OSGeo/gdal/pull/8723: C++17: replace CPL_FALLTHROUGH " +"by standard [[fallthrough]];" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:152 +msgid "" +"https://github.com/OSGeo/gdal/pull/8725: C++17: use structured bindings " +"declaration and class template argument deduction for std::pair()" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:153 +msgid "" +"https://github.com/OSGeo/gdal/issues/8751: Bumping minimum CMake version " +"to 3.16" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:154 +msgid "" +"https://github.com/OSGeo/gdal/issues/8796: Add CI test we can use GDAL " +"public/installed headers with C++11" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:155 +msgid "" +"https://github.com/OSGeo/gdal/pull/8804: Make build compatible of " +"-DCMAKE_UNITY_BUILD=ON for faster builds" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:160 +msgid "This RFC supersedes :ref:`rfc-68`" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:165 +msgid "+1 from PSC members JavierJS, KurstS, HowardB, JukkaR and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:5 +msgid "RFC 99: Geometry coordinate precision" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:10 +msgid "2024-Feb-24" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:11 +msgid "Adopted, implemented in GDAL 3.9" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:18 +msgid "" +"This RFC aims at introducing optional metadata to specify the coordinate " +"precision of geometries, to be able to round appropriately coordinates " +"and limit the number of decimals when exporting to text-based formats or " +"nullify least-significant bits for binary formats. That metadata will be " +"stored into and read from formats that can support it." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:27 +msgid "The aim is multiple:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:29 +msgid "" +"reducing file size. For text-based formats, rounding and truncating to " +"the specified precision directly reduce file size. For binary formats, " +"using that information to zero least-significant bits can increase the " +"potential when applying afterwards lossless compression methods " +"(typically zipping a file)." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:34 +msgid "" +"presenting the user with hints on the precision of the data he/she " +"accesses. This can be used by user interfaces build on top of GDAL to " +"display geometry coordinates with an appropriate number of decimals." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:38 +msgid "" +"a few drivers (GeoJSON, JSONFG, OpenFileGDB) have layer creation options " +"to specify coordinate precision, but there is currently no driver " +"agnostic way of specifying it." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:42 +msgid "" +"For example, currently, when exporting a file to GML, 15 significant " +"decimal digits (ie the total of digits for the integral and decimal " +"parts) are used, which corresponds to a 0.1 micrometer precision for " +"geography coordinates. The same holds for regular GeoJSON export, unless " +"the RFC 7946 variant is selected, in which case only 7 decimal digits " +"after decimal separators are used. However this is a layer creation " +"option, which means that it is no longer remembered when data is " +"edited/appended to an existing layer (see " +"https://github.com/qgis/QGIS/issues/56335)." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:51 +#, python-format +msgid "" +"For binary formats using IEEE-754 double-precision encoding of real " +"numbers, one can show that at least the last 16 least-significants bits " +"(ie the last 2 bytes of 8) of a coordinate can be set to zero while " +"keeping a 1 mm precision (which corresponds to about 8.9e-9 degree). On a" +" test dataset, setting a 1 mm precision reduced the size of the .zip of " +"the .gpkg file from 766 MB to 667 MB (13% size decrease). If only a 1 " +"meter precision is wished, this increases to 26 useless least-significant" +" bits." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:76 +msgid "C and C++ API extensions and changes" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:79 +msgid "OGRGeomCoordinatePrecision class" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:81 +msgid "" +"A new ``OGRGeomCoordinatePrecision`` class is introduced in the " +"``ogr_geomcoordinateprecision.h`` file:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:170 +msgid "Corresponding additions at the C API level:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:208 +msgid "" +"The existing :cpp:class:`OGRGeomFieldDefn` is extended with a new " +"OGRGeomCoordinatePrecision member, and associated getter and setter " +"methods." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:224 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:261 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:358 +msgid "New corresponding C API:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:234 +msgid "OGRGeometry class" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:236 +msgid "" +"The existing :cpp:class:`OGRGeometry` is extended with the following new " +"``SetPrecision`` method which is a wrapper of the " +"``GEOSGeom_setPrecision_r`` function:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:276 +msgid "" +"Note that this method is not automatically run by the writing side of " +"drivers, which assume that the passed geometries are valid once rounded " +"with the specified coordinate precision metadata." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:280 +msgid "However it is invoked when the `-xyRes` switch of ogr2ogr is passed." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:282 +msgid "" +"It may also be triggered by setting the new " +"``OGR_APPLY_GEOM_SET_PRECISION`` configuration option to ``YES``, for " +"geometries passed to :cpp:func:`OGRLayer::CreateFeature` and " +":cpp:func:`OGRLayer::SetFeature` before they are passed to the driver." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:288 +msgid "A closely related ``roundCoordinates`` method is also introduced:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:310 +msgid "WKB export" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:312 +msgid "" +"WKB export methods will be modified in a similar way as in the prototype " +"https://github.com/OSGeo/gdal/pull/6974 to nullify least significant bits" +" from the precision specifications." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:316 +msgid "More specifically the following 2 new classes are added:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:346 +msgid "" +"And the C++ OGRGeometry ``exportToWkb`` virtual method is modified to " +"have the following prototype:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:355 +msgid "" +"The existing method with signature ``OGRErr exportToWkb(OGRwkbByteOrder, " +"unsigned char *, OGRwkbVariant = wkbVariantOldOgc) const`` is kept and " +"call the new virtual method." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:378 +msgid "OGRLayer CreateLayer()/ICreateLayer() changes" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:380 +msgid "" +"The signature of the current :cpp:func:`OGRLayer::ICreateLayer()` " +"protected method (implemented by drivers) will be changed from" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:389 +msgid "to" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:398 +msgid "This will require changes to out-of-tree drivers that implement it." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:400 +msgid "A corresponding non-virtual public method will also be added:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:409 +msgid "" +"And the current CreateLayer() signature will be adapted to call the " +"modified ICreateLayer()." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:412 +msgid "And for the C API:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:422 +msgid "" +"A new ``GDAL_DCAP_HONOR_GEOM_COORDINATE_PRECISION`` driver capability " +"will be added to advertise that a driver honours " +"OGRGeomFieldDefn::GetCoordinatePrecision() when writing geometries. This " +"may be useul for user interfaces that could offer an option to the user " +"to specify the coordinate precision. Note however that the driver may not" +" be able to store that precision in the dataset metadata." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:428 +msgid "" +"There will be *no* provision to modify the coordinate precision of an " +"existing layer geometry field with :cpp:func:`OGRLayer::AlterFieldDefn`." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:434 +msgid "" +"The following drivers will be modified to honour " +"``GDAL_DCAP_HONOR_GEOM_COORDINATE_PRECISION``" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:439 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:452 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:482 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:506 +msgid "" +"The driver will compute the number of decimal digits after the decimal " +"point to write as ``ceil(1. / log10(resolution))``" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:442 +msgid "" +"The driver will be able to store and retrieve the coordinate precision " +"metadata in the files it generates, by adding " +"``xy_coordinate_resolution`` and ``z_coordinate_resolution`` members at " +"the FeatureCollection level." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:446 +msgid "" +"The existing COORDINATE_PRECISION layer creation option, if specified, " +"will take precedence over the settings coming from " +"OGRGeomFieldDefn::GetCoordinatePrecision()." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:450 +msgid "GeoJSONSeq" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:455 +msgid "It will *not* be able to store it in its metadata." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:458 +msgid "JSONFG" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:460 +msgid "" +"Similar to GeoJSON. One subtelty is that this driver may write both the " +"\"place\" geometry (generally in a non-WGS84 CRS) and the GeoJSON RFC7946" +" WGS84 \"geometry\"." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:463 +msgid "" +"The OGRGeomFieldDefn::GetCoordinatePrecision() will qualify the \"place\"" +" geometry. The coordinate precision of the WGS84 \"geometry\" will be " +"derived from the one of the \"place\" geometry with appropriate " +"geographic/projected CRS and axis unit changes." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:468 +msgid "" +"The coordinate precision metadata of the \"place\" member will be stored " +"in ``xy_coordinate_resolution_place`` and " +"``z_coordinate_resolution_place`` members at the FeatureCollection level." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:472 +msgid "" +"For the \"geometry\" member, the same ``xy_coordinate_resolution`` and " +"``z_coordinate_resolution`` members as the GeoJSON driver will be used." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:475 +msgid "" +"The existing COORDINATE_PRECISION_PLACE or COORDINATE_PRECISION_GEOMETRY " +"layer creation option, if specified, will take precedence over the " +"settings coming from OGRGeomFieldDefn::GetCoordinatePrecision()." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:485 +msgid "" +"The driver will be able to store the coordinate precision metadata in the" +" XML schema it generates by adding a ``xs:annotation/xs:appinfo`` element" +" in the declaration of the geometry property, and with " +"``ogr:xy_coordinate_resolution`` and ``ogr:z_coordinate_resolution`` sub-" +"elements. This should hopefully be ignored by readers that don't " +"recognize that metadata (this will be the case of GDAL < 3.9)" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:509 +msgid "" +"It will *not* be able to store it in its metadata. The possibility of " +"storing the coordinate metadata in the .csvt side-car file has been " +"considered, but it would not be backwards-compatible." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:516 +msgid "" +"The GeoPackage driver will support reading and writing the geometry " +"coordinate precision. By default, the geometry coordinate precision will " +"only noted in metadata, and does not cause geometries that are written to" +" be modified to comply with this precision." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:521 +msgid "Several settings may be combined to apply further processing:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:523 +msgid "" +"the ``OGR_APPLY_GEOM_SET_PRECISION`` configuration option as described " +"previously." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:526 +msgid "" +"if the new ``DISCARD_COORD_LSB`` layer creation option is set to YES, the" +" less-significant bits of the WKB geometry encoding which are not " +"relevant for the requested precision are set to zero. This can improve " +"further lossless compression stages, for example when putting a " +"GeoPackage in an archive. Note however that when reading back such " +"geometries and displaying them to the maximum precision, they will not " +"\"exactly\" match the original OGRGeomCoordinatePrecision settings. " +"However, they will round back to it. The value of the " +"``DISCARD_COORD_LSB`` layer creation option is written in the dataset " +"metadata, and will be re-used for later edition sessions." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:537 +msgid "" +"if the new ``UNDO_DISCARD_COORD_LSB_ON_READING`` layer creation option is" +" set to YES (only makes sense if the ``DISCARD_COORD_LSB`` layer creation" +" option is also set to YES), when *reading* back geometries from a " +"dataset, the ``OGRGeometry::roundCoordinates`` method will be applied so " +"that the geometry coordinates exactly match the original specified " +"coordinate precision. That option will only be honored by GDAL 3.9 or " +"later." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:545 +msgid "" +"Implementation details: the coordinate precision is stored in a record in" +" each of the ``gpkg_metadata`` and ``gpkg_metadata_reference`` table, " +"with the following additional constraints on top of the ones imposed by " +"the GeoPackage specification:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:550 +msgid "gpkg_metadata.md_standard_uri = 'http://gdal.org'" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:551 +msgid "gpkg_metadata.mime_type = 'text/xml'" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:552 +msgid "" +"gpkg_metadata.metadata = ''" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:553 +msgid "gpkg_metadata_reference.reference_scope = 'column'" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:554 +msgid "gpkg_metadata_reference.table_name = '{table_name}'" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:555 +msgid "gpkg_metadata_reference.column_name = '{geometry_column_name}'" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:557 +msgid "" +"Note that the xy_resolution, z_resolution or m_resolution attributes of " +"the XML CoordinatePrecision element are optional. Their numeric value is " +"expressed in the units of the SRS for xy_resolution and z_resolution." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:568 +msgid "OpenFileGDB" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:570 +msgid "" +"OGRGeomCoordinatePrecision::dfXYResolution (resp. dfZResolution, " +"dfMResolution) directly map to 1. / xyscale (resp. 1 / zscale, 1 / " +"mscale) in the declaration of the coordinate grid precision options of " +"the FileGeodatabase format (cf " +"https://help.arcgis.com/en/sdk/10.0/java_ao_adf/conceptualhelp/engine/index.html#//00010000037m000000)." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:575 +msgid "" +"Consequently the OpenFileGDB driver can be modified in reading and " +"writing to fully honour OGRGeomCoordinatePrecision." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:578 +msgid "" +"The driver will also get and set other coordinate grid precision options," +" such as the origin and tolerance, values in the ``FileGeodatabase`` key " +"of the ``OGRGeomCoordinatePrecision::oFormatSpecificOptions`` member." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:582 +msgid "" +"The existing ``XYSCALE``, ``ZSCALE`` and ``MSCALE`` layer creation " +"options, if specified, will take precedence over the settings coming from" +" OGRGeomFieldDefn::GetCoordinatePrecision()." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:589 +msgid "Modified to have exactly the same behavior as OpenFileGDB." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:592 +msgid "OGR VRT" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:594 +msgid "" +"The driver will read the geometry coordinate precision from the source " +"geometry field, or possibly overridden with the following elements in the" +" XML VRT:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:611 +msgid "" +"ogrinfo will be modified to honour OGRGeomCoordinatePrecision when " +"outputting WKT geometries (or GeoJSON geometries for the -json output)" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:617 +msgid "" +"ogr2ogr will forward by default the OGRGeomCoordinatePrecision of the " +"input layer to the output layer, but of course it will only have effects " +"for drivers honouring ``GDAL_DCAP_HONOR_GEOM_COORDINATE_PRECISION``." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:621 +msgid "" +"When reprojection occurs, the coordinate precision will be adjusted to " +"take into account geographic vs projected CRS changes and unit changes." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:624 +msgid "The following options will be added:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:626 +msgid "" +"``-xyRes ``: XY coordinate resolution. Nominally in the unit of the " +"X and Y SRS axis. Appending a ``m``, ``mm`` or ``deg`` suffix will be " +"also supported. A warning will be emitted if the user specifies this " +"option when creating a new layer for a driver that does not advertise " +"``GDAL_DCAP_HONOR_GEOM_COORDINATE_PRECISION``." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:633 +msgid "" +"``-zRes ``: Z coordinate resolution. Nominally in the unit of the Z " +"SRS axis. Appending a ``m`` or ``mm`` suffix will be also supported." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:636 +msgid "``-mRes ``: M coordinate resolution." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:638 +msgid "" +"``-unsetCoordPrecision``: to disable automatic propagation of the input " +"coordinate precision to the output." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:644 +msgid "" +"While there is an obvious logical connection with GEOS' PrecisionModel " +"(https://libgeos.org/doxygen/classgeos_1_1geom_1_1PrecisionModel.html), " +"this RFC does not tie the introduced OGR coordinate precision metadata " +"with it. Tying both would require either adding a reference to a " +"OGRGeomCoordinatePrecision as a member of the OGRGeometry class (which " +"would have some extra RAM usage implications), or as a parameter in " +"OGRGeometry GEOS related methods." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:652 +msgid "" +"Quantization of raster pixel values (e.g. the ``DISCARD_LSB`` creation " +"option of the GeoTIFF driver) is also slightly connected." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:658 +msgid "The new C functions are bound to SWIG." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:685 +msgid "Tests will be added for the new API and the modified drivers." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:690 +msgid "The C and C++ API are extended." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:692 +msgid "" +"The change of the ICreateLayer() virtual method is an ABI change, and " +"will require source code changes to out-of-tree drivers implementing it." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:698 +msgid "Design discussion" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:700 +msgid "" +"This paragraph discusses a number of thoughts that arose during the " +"writing of this RFC but were not kept." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:703 +msgid "" +"While changing ICreateLayer() prototype, which requires the tedious " +"process of changing it in more than 50 drivers, I've also considered " +"introducing an additional OGRLayerCreationContext argument, but I've " +"decided against if, as it is unclear if it would be that useful. For " +"example, in most ogr2ogr scenarios, the final extent and feature count is" +" unknown at the start of the process." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:727 +msgid "Candidate implementation: https://github.com/OSGeo/gdal/pull/9378" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:729 +msgid "" +"A prior implementation with a different and reduced scope was done last " +"year in https://github.com/OSGeo/gdal/pull/6974. The GeoPackage driver " +"specific creation options of this pull request will no longer be needed " +"in the implementation of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:734 +msgid "" +"Related QGIS issue about coordinate precision not being preserved when " +"appending to GeoJSON: https://github.com/qgis/QGIS/issues/56335" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:740 +msgid "+1 from PSC members EvenR and HowardB. +0 from KurtS" +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:5 +msgid "RFC 9: GDAL Paid Maintainer Guidelines" +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:11 +msgid "Status: Approved, but superseded per :ref:`rfc-83`" +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:16 +msgid "" +"To formalize guidelines for the work of maintainers paid out of GDAL " +"project sponsorship funds." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:20 +msgid "Responsibilities" +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:22 +msgid "Analyse and where possible fix bugs reported against GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:23 +msgid "Run, review and extend the test suite (via buildbot, etc)." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:24 +msgid "Maintain and extend documentation." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:25 +msgid "Assist integrating new contributed features." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:26 +msgid "" +"Help maintain project infrastructure (mailing lists, buildbot, source " +"control, etc)" +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:28 +msgid "Provide user support on the project mailing lists, and in other venues." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:30 +msgid "Develop new capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:32 +msgid "" +"Bug fixing and maintenance should be focused on GDAL/OGR, but as needed " +"will extend into sub-projects such as libtiff, libgeotiff, Shapelib and " +"MITAB as long it is to serve a need of the GDAL/OGR project." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:36 +msgid "" +"In order to provide reasonable response times the maintainer is expected " +"spend some time each week addressing new bugs and user support. If the " +"maintainer will be unavailable for an extended period of time (vacation, " +"etc) then the supervisor should be notified." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:44 +msgid "" +"The maintainer is generally subject to the project PSC. However, for day " +"to day decisions one PSC member will be designated as the supervisor for " +"the maintainer. This supervisor will prioritize work via email, bug " +"assignments, and IRC discussions." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:49 +msgid "" +"The supervisor will try to keep the following in mind when prioritizing " +"tasks." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:52 +msgid "" +"Bug reports, and support needs of Sponsors should be given higher " +"priority than other tasks." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:54 +msgid "" +"Areas of focus identified by the PSC (ie. multi-threading, SWIG " +"scripting) should be given higher priority than other tasks." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:57 +msgid "" +"The maintainer should be used to take care of work that no one else is " +"willing and able to do (ie. fill the holes, rather than displacing " +"volunteers)" +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:60 +msgid "" +"Try to avoid tying up the maintainer on one big task for many weeks " +"unless directed by the PSC." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:62 +msgid "" +"The maintainer should not be directed to do work for which someone else " +"is getting paid." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:65 +msgid "" +"Substantial new development projects will only be taken on by the " +"maintainer with the direction of a PSC motion (or possibly an RFC " +"designating the maintainer to work on a change)." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:69 +msgid "" +"Note that the maintainer and the maintainer supervisor are subject to the" +" normal RFC process for any substantial change to GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:75 +msgid "" +"The maintainer will produce a brief bi-weekly report to the gdal-dev list" +" indicating tasks worked on, and a more detailed timesheet for the " +"supervisor." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:79 +msgid "" +"This is intended to provide visibility into status, accomplishments, and " +"time allocation. It also gives an opportunity for the PSC to request a " +"\"course correction\" fairly promptly." +msgstr "" + +#: ../../source/development/testing.rst:5 +msgid "Automated testing" +msgstr "" + +#: ../../source/development/testing.rst:7 +msgid "" +"GDAL includes a comprehensive test suite, implemented using a combination" +" of Python (via pytest) and C++ (via gtest)." +msgstr "" + +#: ../../source/development/testing.rst:9 +msgid "" +"After building GDAL using CMake, the complete test suite can be run using" +" ``ctest -v --output-on-failure``. This will automatically set " +"environment variables so that tests are run on the the built version of " +"GDAL, rather than an installed system copy." +msgstr "" + +#: ../../source/development/testing.rst:13 +msgid "Running a subset of tests using ``ctest``" +msgstr "" + +#: ../../source/development/testing.rst:15 +msgid "" +"The complete set of test suites known to ``ctest`` can be viewed running " +"``ctest -N``." +msgstr "" + +#: ../../source/development/testing.rst:17 +msgid "" +"A subset of tests can be run using the ``-R`` argument to ``ctest``, " +"which selects tests using a provided regular expression. For example, " +"``ctest -R autotest`` would run the Python-based tests." +msgstr "" + +#: ../../source/development/testing.rst:20 +msgid "" +"The ``-E`` argument can be used to exclude tests using a regular " +"expression. For example, ``ctest -E gdrivers`` would exclude the suite of" +" driver tests." +msgstr "" + +#: ../../source/development/testing.rst:23 +msgid "Running a subset of tests using ``pytest``" +msgstr "" + +#: ../../source/development/testing.rst:25 +msgid "" +"The test subsets exposed by ``ctest`` are still rather large and some may" +" take several minutes to run. If a higher level of specificity is needed," +" ``pytest`` can be called directly to run groups of tests or individual " +"tests. Before running ``pytest``, it is important to set " +":ref:`development environment variables " +"` so that the development build of " +"GDAL is tested, rather than a system version." +msgstr "" + +#: ../../source/development/testing.rst:29 +msgid "" +"Tests can then be run by calling ``pytest``, for example on an individual" +" file. On Linux and MacOS builds, the tests are symlinked into the build " +"directory, so this can be done by running the following from the build " +"directory:" +msgstr "" + +#: ../../source/development/testing.rst:37 +msgid "" +"On Windows, the test files remain in the source tree, but the pytest " +"configuration file ``pytest.ini`` is only available in the build " +"directory. To accommodate this, the above command would be modified as " +"follows:" +msgstr "" + +#: ../../source/development/testing.rst:43 +msgid "" +"A subset of tests within an individual test file can be run by providing " +"a regular expression to the ``-k`` argument to ``pytest``." +msgstr "" + +#: ../../source/development/testing.rst:49 +msgid "" +"``pytest`` can also report information on the tests without running them." +" For example, to list tests containing \"tiff\" in the name:" +msgstr "" + +#: ../../source/development/testing.rst:57 +msgid "" +"Not all Python tests can be run independently; some tests depend on state" +" set by a previous tests in the same file." +msgstr "" + +#: ../../source/development/testing.rst:61 +msgid "Checking for memory leaks and access errors using Valgrind" +msgstr "" + +#: ../../source/development/testing.rst:63 +msgid "" +"The GDAL unit test suite can be run using the Valgrind tool to detect " +"memory errors such as leaks and incorrect reads/writes." +msgstr "" + +#: ../../source/development/testing.rst:66 +msgid "" +"The test suite will run considerably slower under Valgrind (perhaps by a " +"factor of ten) so it is generally advisable to run a subset of the tests " +"using the methods described above." +msgstr "" + +#: ../../source/development/testing.rst:70 +msgid "" +"Calling ``valgrind ctest`` will _not_ run the tests under ``valgrind``. " +"Although it is possible to use Valgrind with ctest, it is simpler to call" +" ``pytest`` or ``gdal_unit_test`` directly." +msgstr "" + +#: ../../source/development/testing.rst:74 +msgid "" +"The following preparatory steps are necessary to avoid numerous false-" +"positive errors from Valgrind:" +msgstr "" + +#: ../../source/development/testing.rst:77 +msgid "" +"Many false-positive errors are generated by Python itself. Most of these " +"can be removed by obtaining a suppression file that corresponds to the " +"version of the Python interpreter used to run the tests. This file can be" +" located in a source distribution of Python, or downloaded directly from " +"GitHub (for example, at " +"https://raw.githubusercontent.com/python/cpython/3.11/Misc/valgrind-" +"python.supp)" +msgstr "" + +#: ../../source/development/testing.rst:84 +msgid "" +"A few false-positive errors are generated by the GDAL test suite or " +"libraries that it uses (e.g., SWIG, numpy). These can be removed by " +"``autotest/valgrind-gdal.supp`` file in the GDAL repository." +msgstr "" + +#: ../../source/development/testing.rst:88 +msgid "" +"When running Python unit tests, the default system memory allocator " +"should be used instead of Python's internal memory allocator. This can be" +" done by setting the ``PYTHONMALLOC`` environment variable to ``malloc``." +msgstr "" + +#: ../../source/development/testing.rst:92 +msgid "" +"When running Python unit tests, Valgrind will report numerous \"Invalid " +"file descriptor\" warnings that cannot currently be suppressed. These can" +" be removed from the output using ``grep -v \"invalid file " +"descriptor\\|alternative log fd\"``." +msgstr "" + +#: ../../source/development/testing.rst:97 +msgid "" +"Combining the following, we can run valgrind for a subset of Python tests" +" as follows:" +msgstr "" + +#: ../../source/development/testing.rst:108 +msgid "" +"To avoid verbose commands such as the one above, it may be useful to " +"reference the suppression files and other common arguments in a " +"``~/.valgrindrc`` file." +msgstr "" + +#: ../../source/development/testing.rst:116 +msgid "Recommendations on how to write new tests" +msgstr "" + +#: ../../source/development/testing.rst:118 +msgid "" +"Python-based tests should be preferred when possible, as productivity is " +"higher in Python and there is no associated compilation time (compilation" +" time affects feedback received from continuous integration)." +msgstr "" + +#: ../../source/development/testing.rst:122 +msgid "" +"C/C++-based test should be reserved for C++-specific aspects that cannot " +"be tested with the SWIG Python bindings, which use the C interface. For " +"example testing of C++ operators (copy/move constructors/assignment " +"operators, iterator interfaces, etc.) or C/C++ functionality not mapped " +"to SWIG (e.g. CPL utility functions/classes)" +msgstr "" + +#: ../../source/development/testing.rst:128 +msgid "Python tests" +msgstr "" + +#: ../../source/development/testing.rst:130 +msgid "" +"Python tests use the `pytest `__ " +"framework since :ref:`rfc-72`." +msgstr "" + +#: ../../source/development/testing.rst:133 +msgid "" +"Test cases should be written in a way where they are independent from " +"other ones, so they can potentially be run in a isolated way or in " +"parallel of other test cases. In particular temporary files should be " +"created with a name that cannot conflict with other tests: preferably use" +" pytest's ```tmp_path`` fixture `__." +msgstr "" + +#: ../../source/development/testing.rst:138 +msgid "" +"Use ``@pytest.mark.require_driver(driver_name)`` as an annotation for a " +"test case that requires an optional driver to be present." +msgstr "" + +#: ../../source/development/testing.rst:141 +msgid "" +"Use ``pytestmark = pytest.mark.require_driver(\"driver_name\")`` towards " +"the beginning of a test file that requires a given driver to be available" +" for all its test cases. This is typically when writing tests for a " +"particular driver." +msgstr "" + +#: ../../source/development/testing.rst:146 +msgid "" +"Use ``@pytest.mark.require_run_on_demand`` as an annotation to signal a " +"test that should not be run by default, typically because it requires " +"special pre-conditions, use a lot of RAM, etc. and is thus not " +"appropriate to be automatically run by continuous integration." +msgstr "" + +#: ../../source/development/testing.rst:151 +msgid "" +"Use ``@pytest.mark.parametrize(...)`` as an annotation for test functions" +" that test for variations, instead of for() constructs. More details at " +"https://docs.pytest.org/en/latest/parametrize.html" +msgstr "" + +#: ../../source/development/testing.rst:155 +msgid "e.g.:" +msgstr "" + +#: ../../source/development/testing.rst:164 +msgid "instead of" +msgstr "" + +#: ../../source/development/testing.rst:173 +msgid "" +"`Fixtures `__ can" +" be used to share set-up and tear-down code between test cases." +msgstr "" + +#: ../../source/development/testing.rst:176 +msgid "" +"e.g. a fixture automatically loaded for all test cases of a test file, " +"that takes care to unregister a given driver before the test case is run," +" and re-register it afterwards:" +msgstr "" + +#: ../../source/development/testing.rst:195 +msgid "" +"or a fixture that runs preliminary checks to discover if a driver has " +"some optional capabilities, and skip a test case if not:" +msgstr "" + +#: ../../source/development/testing.rst:220 +msgid "C++ tests" +msgstr "" + +#: ../../source/development/testing.rst:222 +msgid "" +"GDAL C++ tests use the `GoogleTest " +"`__ framework since :ref:`rfc-88`." +msgstr "" + +#: ../../source/development/testing.rst:225 +msgid "" +"Common non-failing assertions are: ``EXPECT_TRUE(cond)``, " +"``EXPECT_FALSE(cond)``, ``EXPECT_EQ(a, b)``, ``EXPECT_NE(a, b)``, " +"``EXPECT_STREQ(a, b)``, ``EXPECT_LE(a, b)``, ``EXPECT_LT(a, b)``, " +"``EXPECT_GE(a, b)``, ``EXPECT_GT(a, b)``, ``EXPECT_NEAR(a, b, " +"tolerance)`` If one of those assertions fail, the execution of the rest " +"of the test cases continues, hence they should not typically be used if " +"testing a pointer against NULL and dereferencing it unconditionally " +"afterwards. The ASSERT_xxxx family of assertions should be used for such " +"cases where early exit of the test case is desired." +msgstr "" + +#: ../../source/development/testing.rst:234 +msgid "GoogleTest also offers capabilities for parametrized tests. For example:" +msgstr "" + +#: ../../source/development/testing.rst:286 +msgid "Test coverage reports" +msgstr "" + +#: ../../source/development/testing.rst:288 +msgid "" +"GDAL continuous integration has a ``coverage`` configuration that builds " +"GDAL with the ``gcov`` GCC module to get the line coverage of running " +"Python and C++ autotest tests." +msgstr "" + +#: ../../source/development/testing.rst:292 +msgid "" +"This is used by the `Coveralls GitHub Action " +"`__ to " +"upload results to https://coveralls.io/github/OSGeo/gdal, for both push " +"and pull requests events." +msgstr "" + +#: ../../source/development/testing.rst:296 +msgid "" +"A somewhat nicer looking output of line coverage results for the latest " +"master build, generated by ``lcov``, is also available at https" +"://gdalautotest-coverage-results.github.io/coverage_html/index.html" +msgstr "" + +#: ../../source/development/testing.rst:301 +msgid "Post-commit testing" +msgstr "" + +#: ../../source/development/testing.rst:303 +msgid "" +"A weekly static analysis is run by `Coverity " +"`__. Developers/maintainers can request access" +" on the `GDAL project page `__." +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/download.po b/doc/source/locale/en/LC_MESSAGES/download.po new file mode 100644 index 000000000000..0ba6d38ab1e7 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/download.po @@ -0,0 +1,251 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: en\n" +"Language-Team: en \n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/download.rst:5 +msgid "Download" +msgstr "" + +#: ../../source/download.rst:10 +msgid "Contents" +msgstr "" + +#: ../../source/download.rst:13 +msgid "" +"The GDAL project distributes GDAL as source code and :ref:`Containers` " +"only. :ref:`Binaries` produced by others are available for a variety of " +"platforms and package managers." +msgstr "" + +#: ../../source/download.rst:16 +msgid "Source Code" +msgstr "" + +#: ../../source/download.rst:19 +msgid "Current Release" +msgstr "" + +#: ../../source/download.rst:21 +msgid "**2024-06-26** `gdal-3.9.1.tar.gz`_ `3.9.1 Release Notes`_ (`3.9.1 md5`_)" +msgstr "" + +#: ../../source/download.rst:28 +msgid "Past Releases" +msgstr "" + +#: ../../source/download.rst:30 +msgid "Links to :ref:`download_past` are also available." +msgstr "" + +#: ../../source/download.rst:35 +msgid "Development Source" +msgstr "" + +#: ../../source/download.rst:37 +msgid "" +"The main repository for GDAL is located on GitHub at " +"https://github.com/OSGeo/GDAL." +msgstr "" + +#: ../../source/download.rst:40 +msgid "" +"You can obtain a copy of the active source code by issuing the following " +"command" +msgstr "" + +#: ../../source/download.rst:48 +msgid "" +"Additional information is available about :ref:`build_requirements` and " +":ref:`building_from_source`." +msgstr "" + +#: ../../source/download.rst:54 +msgid "Binaries" +msgstr "" + +#: ../../source/download.rst:56 +msgid "" +"In this section we list a number of the binary distributions of GDAL all " +"of which should have fully reproducible open source build recipes." +msgstr "" + +#: ../../source/download.rst:59 +msgid "" +"Note that the maintainers of those distributions are generally not the " +"maintainers of the GDAL sources, so please report any issue specific to " +"those builds through their own support channels." +msgstr "" + +#: ../../source/download.rst:64 +msgid "Windows" +msgstr "" + +#: ../../source/download.rst:66 +msgid "" +"Windows builds are available via `Conda Forge`_ (64-bit only). See the " +":ref:`conda` section for more detailed information. GDAL is also " +"distributed by `GISInternals`_ and `OSGeo4W`_ and through the `NuGet`_ " +"and :ref:`vcpkg` package managers." +msgstr "" + +#: ../../source/download.rst:76 +msgid "Linux" +msgstr "" + +#: ../../source/download.rst:78 +msgid "" +"Packages are available for `Debian`_, `Alpine_`, `Fedora_`, and other " +"distributions." +msgstr "" + +#: ../../source/download.rst:86 +msgid "Mac OS" +msgstr "" + +#: ../../source/download.rst:88 +msgid "GDAL packages are available on `Homebrew`_." +msgstr "" + +#: ../../source/download.rst:94 +msgid "Cross-Platform Package Managers" +msgstr "" + +#: ../../source/download.rst:99 +msgid "Conda" +msgstr "" + +#: ../../source/download.rst:101 +msgid "" +"`Conda `__ can be used on multiple platforms " +"(Windows, macOS, and Linux) to install software packages and manage " +"environments. Conda packages for GDAL are available through `conda-forge " +"`__." +msgstr "" + +#: ../../source/download.rst:107 +msgid "Latest version: |Conda badge|" +msgstr "" + +#: ../../source/download.rst +msgid "Conda badge" +msgstr "" + +#: ../../source/download.rst:122 +msgid "To install the Arrow and Parquet drivers as plugins:" +msgstr "" + +#: ../../source/download.rst:130 +msgid "GDAL master Conda builds" +msgstr "" + +#: ../../source/download.rst:132 +msgid "" +"GDAL master builds are available in the `gdal-master " +"`__ channel. They are based on " +"dependencies from the ``conda-forge`` channel." +msgstr "" + +#: ../../source/download.rst:135 +msgid "" +"First, install mamba into the ``base`` environment, create a dedicated " +"``gdal_master_env`` environment, and then activate the dedicated " +"``gdal_master_env`` environment." +msgstr "" + +#: ../../source/download.rst:145 +msgid "Then install GDAL from the ``gdal-master`` channel:" +msgstr "" + +#: ../../source/download.rst:156 +msgid "vcpkg" +msgstr "" + +#: ../../source/download.rst:158 +msgid "" +"The GDAL port in the `vcpkg `__ " +"dependency manager is kept up to date by Microsoft team members and " +"community contributors. You can download and install GDAL using the vcpkg" +" as follows:" +msgstr "" + +#: ../../source/download.rst:169 +msgid "" +"If the version is out of date, please `create an issue or pull request " +"`__ on the vcpkg repository." +msgstr "" + +#: ../../source/download.rst:172 +msgid "Spack" +msgstr "" + +#: ../../source/download.rst:174 +msgid "" +"Spack is a package management tool designed to support multiple versions " +"and configurations of software on a wide variety of platforms and " +"environments. It was designed for large supercomputing centers. Spack " +"builds packages from sources, and allows tweaking their configurations." +msgstr "" + +#: ../../source/download.rst:179 +msgid "" +"You can find information about GDAL in Spack at " +"https://packages.spack.io/package.html?name=gdal" +msgstr "" + +#: ../../source/download.rst:182 +msgid "For the default GDAL build with a reduced number of drivers:" +msgstr "" + +#: ../../source/download.rst:190 +msgid "For a build with netcdf driver enabled:" +msgstr "" + +#: ../../source/download.rst:200 +msgid "Containers" +msgstr "" + +#: ../../source/download.rst:202 +msgid "" +"Docker images with nightly builds of GDAL master and tagged releases are " +"available at `GitHub Container registry " +"`_." +msgstr "" + +#: ../../source/download.rst:205 +msgid "" +"Information on the content of the different configurations can be found " +"at `https://github.com/OSGeo/gdal/tree/master/docker " +"`_." +msgstr "" + +#: ../../source/download.rst:210 +msgid "Documentation" +msgstr "" + +#: ../../source/download.rst:212 +msgid "" +"Besides being included when downloading the software, the documentation " +"is also available independently as a `PDF file " +"`_, and `a ZIP of individual HTML pages " +"`_ for " +"offline browsing. (The ZIP also includes the PDF.) The documentation " +"reflects the latest state of the development branch of the software." +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/download_past.po b/doc/source/locale/en/LC_MESSAGES/download_past.po new file mode 100644 index 000000000000..a8fd71312581 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/download_past.po @@ -0,0 +1,411 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: en\n" +"Language-Team: en \n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/download_past.rst:6 +msgid "Past Releases" +msgstr "" + +#: ../../source/download_past.rst:8 +msgid "**2024-05-10** `gdal-3.9.0.tar.gz`_ `3.9.0 Release Notes`_ (`3.9.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:14 +msgid "**2024-04-04** `gdal-3.8.5.tar.gz`_ `3.8.5 Release Notes`_ (`3.8.5 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:20 +msgid "**2024-02-18** `gdal-3.8.4.tar.gz`_ `3.8.4 Release Notes`_ (`3.8.4 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:26 +msgid "**2024-01-08** `gdal-3.8.3.tar.gz`_ `3.8.3 Release Notes`_ (`3.8.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:32 +msgid "**2023-12-20** `gdal-3.8.2.tar.gz`_ `3.8.2 Release Notes`_ (`3.8.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:38 +msgid "**2023-11-30** `gdal-3.8.1.tar.gz`_ `3.8.1 Release Notes`_ (`3.8.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:44 +msgid "**2023-11-13** `gdal-3.8.0.tar.gz`_ `3.8.0 Release Notes`_ (`3.8.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:50 +msgid "**2023-11-03** `gdal-3.7.3.tar.gz`_ `3.7.3 Release Notes`_ (`3.7.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:56 +msgid "**2023-09-13** `gdal-3.7.2.tar.gz`_ `3.7.2 Release Notes`_ (`3.7.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:62 +msgid "**2023-07-13** `gdal-3.7.1.tar.gz`_ `3.7.1 Release Notes`_ (`3.7.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:68 +msgid "**2023-05-10** `gdal-3.7.0.tar.gz`_ `3.7.0 Release Notes`_ (`3.7.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:74 +msgid "**2023-04-21** `gdal-3.6.4.tar.gz`_ `3.6.4 Release Notes`_ (`3.6.4 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:80 +msgid "**2023-03-13** `gdal-3.6.3.tar.gz`_ `3.6.3 Release Notes`_ (`3.6.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:86 +msgid "**2023-01-05** `gdal-3.6.2.tar.gz`_ `3.6.2 Release Notes`_ (`3.6.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:92 +msgid "**2022-12-11** `gdal-3.6.1.tar.gz`_ `3.6.1 Release Notes`_ (`3.6.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:98 +msgid "" +"**2022-11-06** `3.6.0 Release Notes`_ *Warning*: this version has been " +"officially retracted and superseded per 3.6.1" +msgstr "" + +#: ../../source/download_past.rst:102 +msgid "**2022-10-21** `gdal-3.5.3.tar.gz`_ `3.5.3 Release Notes`_ (`3.5.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:108 +msgid "**2022-09-12** `gdal-3.5.2.tar.gz`_ `3.5.2 Release Notes`_ (`3.5.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:114 +msgid "**2022-07-06** `gdal-3.5.1.tar.gz`_ `3.5.1 Release Notes`_ (`3.5.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:120 +msgid "**2022-05-13** `gdal-3.5.0.tar.gz`_ `3.5.0 Release Notes`_ (`3.5.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:126 +msgid "**2022-04-22** `gdal-3.4.3.tar.gz`_ `3.4.3 Release Notes`_ (`3.4.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:132 +msgid "**2022-03-08** `gdal-3.4.2.tar.gz`_ `3.4.2 Release Notes`_ (`3.4.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:138 +msgid "**2021-12-27** `gdal-3.4.1.tar.gz`_ `3.4.1 Release Notes`_ (`3.4.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:144 +msgid "**2021-11-08** `gdal-3.4.0.tar.gz`_ `3.4.0 Release Notes`_ (`3.4.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:150 +msgid "**2021-10-29** `gdal-3.3.3.tar.gz`_ `3.3.3 Release Notes`_ (`3.3.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:156 +msgid "**2021-09-01** `gdal-3.3.2.tar.gz`_ `3.3.2 Release Notes`_ (`3.3.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:162 +msgid "**2021-07-05** `gdal-3.3.1.tar.gz`_ `3.3.1 Release Notes`_ (`3.3.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:168 +msgid "**2021-05-03** `gdal-3.3.0.tar.gz`_ `3.3.0 Release Notes`_ (`3.3.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:174 +msgid "**2021-05-04** `gdal-3.2.3.tar.gz`_ `3.2.3 Release Notes`_ (`3.2.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:180 +msgid "**2021-03-10** `gdal-3.2.2.tar.gz`_ `3.2.2 Release Notes`_ (`3.2.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:186 +msgid "**2020-12-28** `gdal-3.2.1.tar.gz`_ `3.2.1 Release Notes`_ (`3.2.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:192 +msgid "**2020-10-26** `gdal-3.2.0.tar.gz`_ `3.2.0 Release Notes`_ (`3.2.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:198 +msgid "**2020-10-23** `gdal-3.1.4.tar.gz`_ `3.1.4 Release Notes`_ (`3.1.4 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:204 +msgid "**2020-09-01** `gdal-3.1.3.tar.gz`_ `3.1.3 Release Notes`_ (`3.1.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:210 +msgid "**2020-07-07** `gdal-3.1.2.tar.gz`_ `3.1.2 Release Notes`_ (`3.1.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:216 +msgid "**2020-06-22** `gdal-3.1.1.tar.gz`_ `3.1.1 Release Notes`_ (`3.1.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:223 +msgid "**2020-05-03** `gdal-3.1.0.tar.gz`_ `3.1.0 Release Notes`_ (`3.1.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:229 +msgid "**2020-01-28** `gdal-3.0.4.tar.gz`_ `3.0.4 Release Notes`_ (`3.0.4 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:235 +msgid "**2020-01-08** `gdal-2.4.4.tar.gz`_ `2.4.4 Release Notes`_ (`2.4.4 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:241 +msgid "**2020-01-08** `gdal-3.0.3.tar.gz`_ `3.0.3 Release Notes`_ (`3.0.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:247 +msgid "**2019-10-28** `gdal-3.0.2.tar.gz`_ `3.0.2 Release Notes`_ (`3.0.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:253 +msgid "**2019-10-28** `gdal-2.4.3.tar.gz`_ `2.4.3 Release Notes`_ (`2.4.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:260 +msgid "**2019-06-28** `gdal-3.0.1.tar.gz`_ `3.0.1 Release Notes`_ (`3.0.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:267 +msgid "**2019-06-28** `gdal-2.4.2.tar.gz`_ `2.4.2 Release Notes`_ (`2.4.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:274 ../../source/download_past.rst:295 +msgid "**2019-05** `gdal-3.0.0.tar.gz`_ `3.0.0 Release Notes`_ (`3.0.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:281 ../../source/download_past.rst:302 +msgid "**2019-03** `gdal-2.4.1.tar.gz`_ `2.4.1 Release Notes`_ (`2.4.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:288 ../../source/download_past.rst:309 +msgid "**2018-12** `gdal-2.4.0.tar.gz`_ `2.4.0 Release Notes`_ (`2.4.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:316 +msgid "**2018-12** `gdal-2.3.3.tar.gz`_ `2.3.3 Release Notes`_ (`2.3.3 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:323 +msgid "**2018-09** `gdal-2.3.2.tar.gz`_ `2.3.2 Release Notes`_ (`2.3.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:330 +msgid "**2018-06** `gdal-2.3.1.tar.gz`_ `2.3.1 Release Notes`_ (`2.3.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:337 +msgid "**2018-05** `gdal-2.3.0.tar.gz`_ `2.3.0 Release Notes`_ (`2.3.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:344 +msgid "**2018-03** `gdal-2.2.4.tar.gz`_ `2.2.4 Release Notes`_ (`2.2.4 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:351 +msgid "**2017-11** `gdal-2.2.3.tar.gz`_ `2.2.3 Release Notes`_ (`2.2.3 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:358 +msgid "**2017-09** `gdal-2.2.2.tar.gz`_ `2.2.2 Release Notes`_ (`2.2.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:365 +msgid "**2017-06** `gdal-2.2.1.tar.gz`_ `2.2.1 Release Notes`_ (`2.2.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:372 +msgid "**2017-06** `gdal-2.1.4.tar.gz`_ `2.1.4 Release Notes`_ (`2.1.4 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:379 +msgid "**2017-04** `gdal-2.2.0.tar.gz`_ `2.2.0 Release Notes`_ (`2.2.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:386 +msgid "**2017-01** `gdal-2.1.3.tar.gz`_ `2.1.3 Release Notes`_ (`2.1.3 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:393 +msgid "**2016-10** `gdal-2.1.2.tar.gz`_ `2.1.2 Release Notes`_ (`2.1.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:400 +msgid "**2016-07** `gdal-2.1.1.tar.gz`_ `2.1.1 Release Notes`_ (`2.1.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:407 +msgid "**2016-07** `gdal-2.0.3.tar.gz`_ `2.0.3 Release Notes`_ (`2.0.3 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:414 +msgid "**2016-07** `gdal-1.11.5.tar.gz`_ `1.11.5 Release Notes`_ (`1.11.5 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:421 +msgid "**2016-04** `gdal-2.1.0.tar.gz`_ `2.1.0 Release Notes`_ (`2.1.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:428 +msgid "**2016-01** `gdal-2.0.2.tar.gz`_ `2.0.2 Release Notes`_ (`2.0.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:435 +msgid "**2016-01** `gdal-1.11.4.tar.gz`_ `1.11.4 Release Notes`_ (`1.11.4 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:442 +msgid "**2015-09** `gdal-2.0.1.tar.gz`_ `2.0.1 Release Notes`_ (`2.0.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:449 +msgid "**2015-09** `gdal-1.11.3.tar.gz`_ `1.11.3 Release Notes`_ (`1.11.3 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:456 +msgid "**2015-06** `gdal-2.0.0.tar.gz`_ `2.0.0 Release Notes`_ (`2.0.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:463 +msgid "**2015-02** `gdal-1.11.2.tar.gz`_ `1.11.2 Release Notes`_ (`1.11.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:470 +msgid "**2014-09** `gdal-1.11.1.tar.gz`_ `1.11.1 Release Notes`_ (`1.11.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:477 +msgid "**2014-04** `gdal-1.11.0.tar.gz`_ `1.11.0 Release Notes`_ (`1.11.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:484 +msgid "**2013-08** `gdal-1.10.1.tar.gz`_ `1.10.1 Release Notes`_ (`1.10.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:491 +msgid "**2013-04** `gdal-1.10.0.tar.gz`_ `1.10.0 Release Notes`_ (`1.10.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:498 +msgid "**2012-10** `gdal-1.9.2.tar.gz`_ `1.9.2 Release Notes`_ (`1.9.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:505 +msgid "**2012-05** `gdal-1.9.1.tar.gz`_ `1.9.1 Release Notes`_ (`1.9.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:512 +msgid "**2011-12** `gdal-1.9.0.tar.gz`_ `1.9.0 Release Notes`_ (`1.9.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:519 +msgid "**2011-07** `gdal-1.8.1.tar.gz`_ `1.8.1 Release Notes`_ (`1.8.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:526 +msgid "**2011-01** `gdal-1.8.0.tar.gz`_ `1.8.0 Release Notes`_ (`1.8.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:533 +msgid "**2010-11** `gdal-1.7.3.tar.gz`_ `1.7.3 Release Notes`_ (`1.7.3 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:539 +msgid "**2010-04** `gdal-1.7.2.tar.gz`_ `1.7.2 Release Notes`_ (`1.7.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:546 +msgid "**2010-02** `gdal-1.7.1.tar.gz`_ `1.7.1 Release Notes`_ (`1.7.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:553 +msgid "**2010-01** `1.7.0 (retracted) Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:558 +msgid "**2009-11** `gdal-1.6.3.tar.gz`_ `1.6.3 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:564 +msgid "**2009-08** `gdal-1.6.2.tar.gz`_ `1.6.2 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:570 +msgid "**2009-05** `gdal-1.6.1.tar.gz`_ `1.6.1 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:576 +msgid "**2008-12** `gdal-1.6.0.tar.gz`_ `1.6.0 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:582 +msgid "**2009-01** `gdal-1.5.4.tar.gz`_ `1.5.4 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:588 +msgid "**2008-10** `gdal-1.5.3.tar.gz`_ `1.5.3 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:594 +msgid "**2008-05** `gdal-1.5.2.tar.gz`_ `1.5.2 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:600 +msgid "**2008-03** `gdal-1.5.1.tar.gz`_ `1.5.1 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:606 +msgid "**2007-12** `gdal-1.5.0.tar.gz`_ `1.5.0 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:612 +msgid "**2008-12** `gdal-1.4.5.tar.gz`_ `1.4.5 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:618 +msgid "**2007-11** `gdal-1.4.4.tar.gz`_ `1.4.4 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:624 +msgid "**2007-06** `gdal-1.4.2.tar.gz`_ `1.4.2 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:630 +msgid "**2007-04** `gdal-1.4.1.tar.gz`_ `1.4.1 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:636 +msgid "**2007-01** `gdal-1.4.0.tar.gz`_" +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/drivers.po b/doc/source/locale/en/LC_MESSAGES/drivers.po new file mode 100644 index 000000000000..eb0bba282b65 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/drivers.po @@ -0,0 +1,51208 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR , 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language: en\n" +"Language-Team: en \n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/drivers/raster/Idrisi.rst:5 +msgid "RST -- Idrisi Raster Format" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:-1 +#: ../../source/drivers/raster/aaigrid.rst:-1 +#: ../../source/drivers/raster/ace2.rst:-1 +#: ../../source/drivers/raster/adrg.rst:-1 +#: ../../source/drivers/raster/aig.rst:-1 +#: ../../source/drivers/raster/airsar.rst:-1 +#: ../../source/drivers/raster/bag.rst:-1 +#: ../../source/drivers/raster/basisu.rst:-1 +#: ../../source/drivers/raster/blx.rst:-1 +#: ../../source/drivers/raster/bmp.rst:-1 +#: ../../source/drivers/raster/bsb.rst:-1 ../../source/drivers/raster/bt.rst:-1 +#: ../../source/drivers/raster/byn.rst:-1 +#: ../../source/drivers/raster/cad.rst:-1 +#: ../../source/drivers/raster/cals.rst:-1 +#: ../../source/drivers/raster/ceos.rst:-1 +#: ../../source/drivers/raster/coasp.rst:-1 +#: ../../source/drivers/raster/cog.rst:-1 +#: ../../source/drivers/raster/cosar.rst:-1 +#: ../../source/drivers/raster/cpg.rst:-1 +#: ../../source/drivers/raster/ctable2.rst:-1 +#: ../../source/drivers/raster/ctg.rst:-1 +#: ../../source/drivers/raster/daas.rst:-1 +#: ../../source/drivers/raster/dds.rst:-1 +#: ../../source/drivers/raster/derived.rst:-1 +#: ../../source/drivers/raster/dimap.rst:-1 +#: ../../source/drivers/raster/dipex.rst:-1 +#: ../../source/drivers/raster/doq1.rst:-1 +#: ../../source/drivers/raster/doq2.rst:-1 +#: ../../source/drivers/raster/dted.rst:-1 +#: ../../source/drivers/raster/ecrgtoc.rst:-1 +#: ../../source/drivers/raster/ecw.rst:-1 +#: ../../source/drivers/raster/eedai.rst:-1 +#: ../../source/drivers/raster/ehdr.rst:-1 +#: ../../source/drivers/raster/eir.rst:-1 +#: ../../source/drivers/raster/elas.rst:-1 +#: ../../source/drivers/raster/envi.rst:-1 +#: ../../source/drivers/raster/ers.rst:-1 +#: ../../source/drivers/raster/esat.rst:-1 +#: ../../source/drivers/raster/esric.rst:-1 +#: ../../source/drivers/raster/exr.rst:-1 +#: ../../source/drivers/raster/fast.rst:-1 +#: ../../source/drivers/raster/fit.rst:-1 +#: ../../source/drivers/raster/fits.rst:-1 +#: ../../source/drivers/raster/genbin.rst:-1 +#: ../../source/drivers/raster/georaster.rst:-1 +#: ../../source/drivers/raster/gff.rst:-1 +#: ../../source/drivers/raster/gif.rst:-1 +#: ../../source/drivers/raster/gpkg.rst:-1 +#: ../../source/drivers/raster/grass.rst:-1 +#: ../../source/drivers/raster/grassasciigrid.rst:-1 +#: ../../source/drivers/raster/grib.rst:-1 +#: ../../source/drivers/raster/gs7bg.rst:-1 +#: ../../source/drivers/raster/gsag.rst:-1 +#: ../../source/drivers/raster/gsbg.rst:-1 +#: ../../source/drivers/raster/gsc.rst:-1 +#: ../../source/drivers/raster/gta.rst:-1 +#: ../../source/drivers/raster/gti.rst:-1 +#: ../../source/drivers/raster/gtiff.rst:-1 +#: ../../source/drivers/raster/gxf.rst:-1 +#: ../../source/drivers/raster/hdf4.rst:-1 +#: ../../source/drivers/raster/hdf5.rst:-1 +#: ../../source/drivers/raster/heif.rst:-1 +#: ../../source/drivers/raster/hf2.rst:-1 +#: ../../source/drivers/raster/hfa.rst:-1 +#: ../../source/drivers/raster/ilwis.rst:-1 +#: ../../source/drivers/raster/iris.rst:-1 +#: ../../source/drivers/raster/isce.rst:-1 +#: ../../source/drivers/raster/isg.rst:-1 +#: ../../source/drivers/raster/isis2.rst:-1 +#: ../../source/drivers/raster/isis3.rst:-1 +#: ../../source/drivers/raster/jdem.rst:-1 +#: ../../source/drivers/raster/jp2ecw.rst:-1 +#: ../../source/drivers/raster/jp2kak.rst:-1 +#: ../../source/drivers/raster/jp2lura.rst:-1 +#: ../../source/drivers/raster/jp2mrsid.rst:-1 +#: ../../source/drivers/raster/jp2openjpeg.rst:-1 +#: ../../source/drivers/raster/jpeg.rst:-1 +#: ../../source/drivers/raster/jpegxl.rst:-1 +#: ../../source/drivers/raster/jpipkak.rst:-1 +#: ../../source/drivers/raster/kea.rst:-1 +#: ../../source/drivers/raster/kmlsuperoverlay.rst:-1 +#: ../../source/drivers/raster/kro.rst:-1 +#: ../../source/drivers/raster/ktx2.rst:-1 +#: ../../source/drivers/raster/l1b.rst:-1 +#: ../../source/drivers/raster/lan.rst:-1 +#: ../../source/drivers/raster/lcp.rst:-1 +#: ../../source/drivers/raster/leveller.rst:-1 +#: ../../source/drivers/raster/loslas.rst:-1 +#: ../../source/drivers/raster/map.rst:-1 +#: ../../source/drivers/raster/marfa.rst:-1 +#: ../../source/drivers/raster/mbtiles.rst:-1 +#: ../../source/drivers/raster/mem.rst:-1 +#: ../../source/drivers/raster/mff.rst:-1 +#: ../../source/drivers/raster/mff2.rst:-1 +#: ../../source/drivers/raster/mrsid.rst:-1 +#: ../../source/drivers/raster/msg.rst:-1 +#: ../../source/drivers/raster/msgn.rst:-1 +#: ../../source/drivers/raster/ndf.rst:-1 +#: ../../source/drivers/raster/netcdf.rst:-1 +#: ../../source/drivers/raster/ngsgeoid.rst:-1 +#: ../../source/drivers/raster/ngw.rst:-1 +#: ../../source/drivers/raster/nitf.rst:-1 +#: ../../source/drivers/raster/noaa_b.rst:-1 +#: ../../source/drivers/raster/nsidcbin.rst:-1 +#: ../../source/drivers/raster/ntv2.rst:-1 +#: ../../source/drivers/raster/nwtgrd.rst:-1 +#: ../../source/drivers/raster/ogcapi.rst:-1 +#: ../../source/drivers/raster/openfilegdb.rst:-1 +#: ../../source/drivers/raster/ozi.rst:-1 +#: ../../source/drivers/raster/palsar.rst:-1 +#: ../../source/drivers/raster/paux.rst:-1 +#: ../../source/drivers/raster/pcidsk.rst:-1 +#: ../../source/drivers/raster/pcraster.rst:-1 +#: ../../source/drivers/raster/pdf.rst:-1 +#: ../../source/drivers/raster/pds.rst:-1 +#: ../../source/drivers/raster/pds4.rst:-1 +#: ../../source/drivers/raster/plmosaic.rst:-1 +#: ../../source/drivers/raster/png.rst:-1 +#: ../../source/drivers/raster/pnm.rst:-1 +#: ../../source/drivers/raster/postgisraster.rst:-1 +#: ../../source/drivers/raster/prf.rst:-1 ../../source/drivers/raster/r.rst:-1 +#: ../../source/drivers/raster/rasterlite.rst:-1 +#: ../../source/drivers/raster/rasterlite2.rst:-1 +#: ../../source/drivers/raster/rdb.rst:-1 +#: ../../source/drivers/raster/rik.rst:-1 +#: ../../source/drivers/raster/rmf.rst:-1 +#: ../../source/drivers/raster/roi_pac.rst:-1 +#: ../../source/drivers/raster/rpftoc.rst:-1 +#: ../../source/drivers/raster/rraster.rst:-1 +#: ../../source/drivers/raster/rs2.rst:-1 +#: ../../source/drivers/raster/s102.rst:-1 +#: ../../source/drivers/raster/s104.rst:-1 +#: ../../source/drivers/raster/s111.rst:-1 +#: ../../source/drivers/raster/safe.rst:-1 +#: ../../source/drivers/raster/sar_ceos.rst:-1 +#: ../../source/drivers/raster/sdat.rst:-1 +#: ../../source/drivers/raster/sdts.rst:-1 +#: ../../source/drivers/raster/sentinel2.rst:-1 +#: ../../source/drivers/raster/sgi.rst:-1 +#: ../../source/drivers/raster/sigdem.rst:-1 +#: ../../source/drivers/raster/snodas.rst:-1 +#: ../../source/drivers/raster/srp.rst:-1 +#: ../../source/drivers/raster/srtmhgt.rst:-1 +#: ../../source/drivers/raster/stacit.rst:-1 +#: ../../source/drivers/raster/stacta.rst:-1 +#: ../../source/drivers/raster/terragen.rst:-1 +#: ../../source/drivers/raster/tga.rst:-1 +#: ../../source/drivers/raster/til.rst:-1 +#: ../../source/drivers/raster/tiledb.rst:-1 +#: ../../source/drivers/raster/tsx.rst:-1 +#: ../../source/drivers/raster/usgsdem.rst:-1 +#: ../../source/drivers/raster/vicar.rst:-1 +#: ../../source/drivers/raster/vrt.rst:-1 +#: ../../source/drivers/raster/wcs.rst:-1 +#: ../../source/drivers/raster/webp.rst:-1 +#: ../../source/drivers/raster/wms.rst:-1 +#: ../../source/drivers/raster/wmts.rst:-1 +#: ../../source/drivers/raster/xpm.rst:-1 +#: ../../source/drivers/raster/xyz.rst:-1 +#: ../../source/drivers/raster/zarr.rst:-1 +#: ../../source/drivers/raster/zmap.rst:-1 +#: ../../source/drivers/vector/amigocloud.rst:-1 +#: ../../source/drivers/vector/arrow.rst:-1 +#: ../../source/drivers/vector/avcbin.rst:-1 +#: ../../source/drivers/vector/avce00.rst:-1 +#: ../../source/drivers/vector/cad.rst:-1 +#: ../../source/drivers/vector/carto.rst:-1 +#: ../../source/drivers/vector/csv.rst:-1 +#: ../../source/drivers/vector/csw.rst:-1 +#: ../../source/drivers/vector/dgn.rst:-1 +#: ../../source/drivers/vector/dgnv8.rst:-1 +#: ../../source/drivers/vector/dwg.rst:-1 +#: ../../source/drivers/vector/dxf.rst:-1 +#: ../../source/drivers/vector/edigeo.rst:-1 +#: ../../source/drivers/vector/eeda.rst:-1 +#: ../../source/drivers/vector/elasticsearch.rst:-1 +#: ../../source/drivers/vector/esrijson.rst:-1 +#: ../../source/drivers/vector/filegdb.rst:-1 +#: ../../source/drivers/vector/flatgeobuf.rst:-1 +#: ../../source/drivers/vector/geoconcept.rst:-1 +#: ../../source/drivers/vector/geojson.rst:-1 +#: ../../source/drivers/vector/geojsonseq.rst:-1 +#: ../../source/drivers/vector/georss.rst:-1 +#: ../../source/drivers/vector/gml.rst:-1 +#: ../../source/drivers/vector/gmlas.rst:-1 +#: ../../source/drivers/vector/gmt.rst:-1 +#: ../../source/drivers/vector/gpkg.rst:-1 +#: ../../source/drivers/vector/gpsbabel.rst:-1 +#: ../../source/drivers/vector/gpx.rst:-1 +#: ../../source/drivers/vector/grass.rst:-1 +#: ../../source/drivers/vector/gtfs.rst:-1 +#: ../../source/drivers/vector/hana.rst:-1 +#: ../../source/drivers/vector/idb.rst:-1 +#: ../../source/drivers/vector/idrisi.rst:-1 +#: ../../source/drivers/vector/ili.rst:-1 +#: ../../source/drivers/vector/jml.rst:-1 +#: ../../source/drivers/vector/jsonfg.rst:-1 +#: ../../source/drivers/vector/kml.rst:-1 +#: ../../source/drivers/vector/libkml.rst:-1 +#: ../../source/drivers/vector/lvbag.rst:-1 +#: ../../source/drivers/vector/mapml.rst:-1 +#: ../../source/drivers/vector/memory.rst:-1 +#: ../../source/drivers/vector/miramon.rst:-1 +#: ../../source/drivers/vector/mitab.rst:-1 +#: ../../source/drivers/vector/mongodbv3.rst:-1 +#: ../../source/drivers/vector/mssqlspatial.rst:-1 +#: ../../source/drivers/vector/mvt.rst:-1 +#: ../../source/drivers/vector/mysql.rst:-1 +#: ../../source/drivers/vector/nas.rst:-1 +#: ../../source/drivers/vector/netcdf.rst:-1 +#: ../../source/drivers/vector/ngw.rst:-1 +#: ../../source/drivers/vector/ntf.rst:-1 +#: ../../source/drivers/vector/oapif.rst:-1 +#: ../../source/drivers/vector/oci.rst:-1 +#: ../../source/drivers/vector/odbc.rst:-1 +#: ../../source/drivers/vector/ods.rst:-1 +#: ../../source/drivers/vector/ogdi.rst:-1 +#: ../../source/drivers/vector/openfilegdb.rst:-1 +#: ../../source/drivers/vector/osm.rst:-1 +#: ../../source/drivers/vector/parquet.rst:-1 +#: ../../source/drivers/vector/pdf.rst:-1 +#: ../../source/drivers/vector/pds.rst:-1 ../../source/drivers/vector/pg.rst:-1 +#: ../../source/drivers/vector/pgdump.rst:-1 +#: ../../source/drivers/vector/pgeo.rst:-1 +#: ../../source/drivers/vector/plscenes.rst:-1 +#: ../../source/drivers/vector/pmtiles.rst:-1 +#: ../../source/drivers/vector/s57.rst:-1 +#: ../../source/drivers/vector/sdts.rst:-1 +#: ../../source/drivers/vector/selafin.rst:-1 +#: ../../source/drivers/vector/shapefile.rst:-1 +#: ../../source/drivers/vector/sosi.rst:-1 +#: ../../source/drivers/vector/sqlite.rst:-1 +#: ../../source/drivers/vector/svg.rst:-1 +#: ../../source/drivers/vector/sxf.rst:-1 +#: ../../source/drivers/vector/tiger.rst:-1 +#: ../../source/drivers/vector/tiledb.rst:-1 +#: ../../source/drivers/vector/topojson.rst:-1 +#: ../../source/drivers/vector/vdv.rst:-1 +#: ../../source/drivers/vector/vfk.rst:-1 +#: ../../source/drivers/vector/vrt.rst:-1 +#: ../../source/drivers/vector/wasp.rst:-1 +#: ../../source/drivers/vector/wfs.rst:-1 +#: ../../source/drivers/vector/xls.rst:-1 +#: ../../source/drivers/vector/xlsx.rst:-1 +#: ../../source/drivers/vector/xodr.rst:-1 +msgid "Driver short name" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:7 +msgid "RST" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:11 +msgid "" +"This format is basically a raw one. There is just one band per files, " +"except in the RGB24 data type where the Red, Green and Blue bands are " +"store interleaved by pixels in the order Blue, Green and Red. The others " +"data type are unsigned 8 bits integer with values from 0 to 255 or signed" +" 16 bits integer with values from -32.768 to 32.767 or 32 bits single " +"precision floating point.32 bits. The description of the file is stored " +"in a accompanying text file, extension RDC." +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:19 +msgid "" +"The RDC image description file doesn't include color table, or detailed " +"geographic referencing information. The color table if present can be " +"obtained by another accompanying file using the same base name as the RST" +" file and SMP as extension." +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:24 +msgid "" +"For geographical referencing identification, the RDC file contains " +"information that points to a file that holds the geographic reference " +"details. Those files uses extension REF and  resides in the same folder " +"as the RST image or more likely in the Idrisi installation folders." +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:29 +#: ../../source/drivers/vector/idrisi.rst:18 +msgid "" +"Therefore the presence or absence of the Idrisi software in the running " +"operation system will determine the way that this driver will work. By " +"setting the environment variable IDRISIDIR pointing to the Idrisi main " +"installation folder will enable GDAL to find more detailed information " +"about geographical reference and projection in the REF files." +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:35 +msgid "" +"Note that the RST driver recognizes the name convention used in Idrisi " +"for UTM and State Plane geographic reference so it doesn't need to access" +" the REF files. That is the case for RDC file that specify \"utm-30n\" or" +" \"spc87ma1\" in the \"ref. system\" field. Note that exporting to RST in" +" any other geographical reference system will generate a suggested REF " +"content in the comment section of the RDC file." +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:42 +msgid "\".rst\" the raw image file" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:43 +msgid "\".rdc\" the description file" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:44 +msgid "\".smp\" the color table file" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:45 +msgid "\".ref\" the geographical reference file" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:48 +#: ../../source/drivers/raster/aaigrid.rst:65 +#: ../../source/drivers/raster/ace2.rst:23 +#: ../../source/drivers/raster/adrg.rst:33 +#: ../../source/drivers/raster/aig.rst:31 +#: ../../source/drivers/raster/airsar.rst:49 +#: ../../source/drivers/raster/bag.rst:33 +#: ../../source/drivers/raster/basisu.rst:35 +#: ../../source/drivers/raster/blx.rst:25 +#: ../../source/drivers/raster/bmp.rst:27 +#: ../../source/drivers/raster/bsb.rst:32 ../../source/drivers/raster/bt.rst:33 +#: ../../source/drivers/raster/byn.rst:44 +#: ../../source/drivers/raster/cad.rst:24 +#: ../../source/drivers/raster/cals.rst:28 +#: ../../source/drivers/raster/ceos.rst:25 +#: ../../source/drivers/raster/cog.rst:24 +#: ../../source/drivers/raster/cosar.rst:27 +#: ../../source/drivers/raster/cpg.rst:14 +#: ../../source/drivers/raster/ctable2.rst:14 +#: ../../source/drivers/raster/ctg.rst:38 +#: ../../source/drivers/raster/daas.rst:26 +#: ../../source/drivers/raster/dds.rst:34 +#: ../../source/drivers/raster/dimap.rst:30 +#: ../../source/drivers/raster/dipex.rst:14 +#: ../../source/drivers/raster/doq1.rst:18 +#: ../../source/drivers/raster/doq2.rst:24 +#: ../../source/drivers/raster/dted.rst:17 +#: ../../source/drivers/raster/ecrgtoc.rst:29 +#: ../../source/drivers/raster/ecw.rst:17 +#: ../../source/drivers/raster/eedai.rst:17 +#: ../../source/drivers/raster/ehdr.rst:46 +#: ../../source/drivers/raster/eir.rst:25 +#: ../../source/drivers/raster/elas.rst:16 +#: ../../source/drivers/raster/envi.rst:53 +#: ../../source/drivers/raster/ers.rst:22 +#: ../../source/drivers/raster/esat.rst:33 +#: ../../source/drivers/raster/esric.rst:14 +#: ../../source/drivers/raster/exr.rst:105 +#: ../../source/drivers/raster/fast.rst:28 +#: ../../source/drivers/raster/fit.rst:14 +#: ../../source/drivers/raster/fits.rst:366 +#: ../../source/drivers/raster/genbin.rst:32 +#: ../../source/drivers/raster/georaster.rst:53 +#: ../../source/drivers/raster/gff.rst:30 +#: ../../source/drivers/raster/gif.rst:26 +#: ../../source/drivers/raster/gpkg.rst:50 +#: ../../source/drivers/raster/grassasciigrid.rst:25 +#: ../../source/drivers/raster/grib.rst:85 +#: ../../source/drivers/raster/gs7bg.rst:19 +#: ../../source/drivers/raster/gsag.rst:20 +#: ../../source/drivers/raster/gsbg.rst:23 +#: ../../source/drivers/raster/gsc.rst:14 +#: ../../source/drivers/raster/gta.rst:19 +#: ../../source/drivers/raster/gtiff.rst:29 +#: ../../source/drivers/raster/gxf.rst:26 +#: ../../source/drivers/raster/hdf4.rst:24 +#: ../../source/drivers/raster/hdf5.rst:20 +#: ../../source/drivers/raster/heif.rst:30 +#: ../../source/drivers/raster/hf2.rst:25 +#: ../../source/drivers/raster/hfa.rst:30 +#: ../../source/drivers/raster/ilwis.rst:38 +#: ../../source/drivers/raster/iris.rst:33 +#: ../../source/drivers/raster/isce.rst:30 +#: ../../source/drivers/raster/isg.rst:22 +#: ../../source/drivers/raster/isis2.rst:29 +#: ../../source/drivers/raster/isis3.rst:35 +#: ../../source/drivers/raster/jdem.rst:27 +#: ../../source/drivers/raster/jp2ecw.rst:22 +#: ../../source/drivers/raster/jp2kak.rst:50 +#: ../../source/drivers/raster/jp2lura.rst:20 +#: ../../source/drivers/raster/jp2mrsid.rst:18 +#: ../../source/drivers/raster/jp2openjpeg.rst:31 +#: ../../source/drivers/raster/jpeg.rst:67 +#: ../../source/drivers/raster/jpegxl.rst:36 +#: ../../source/drivers/raster/jpipkak.rst:17 +#: ../../source/drivers/raster/kea.rst:36 +#: ../../source/drivers/raster/kmlsuperoverlay.rst:15 +#: ../../source/drivers/raster/kro.rst:24 +#: ../../source/drivers/raster/ktx2.rst:36 +#: ../../source/drivers/raster/l1b.rst:18 +#: ../../source/drivers/raster/lan.rst:29 +#: ../../source/drivers/raster/lcp.rst:38 +#: ../../source/drivers/raster/leveller.rst:25 +#: ../../source/drivers/raster/loslas.rst:17 +#: ../../source/drivers/raster/map.rst:14 +#: ../../source/drivers/raster/marfa.rst:21 +#: ../../source/drivers/raster/mbtiles.rst:53 +#: ../../source/drivers/raster/mem.rst:85 +#: ../../source/drivers/raster/mff.rst:37 +#: ../../source/drivers/raster/mff2.rst:39 +#: ../../source/drivers/raster/mrsid.rst:30 +#: ../../source/drivers/raster/msg.rst:31 +#: ../../source/drivers/raster/msgn.rst:28 +#: ../../source/drivers/raster/ndf.rst:28 +#: ../../source/drivers/raster/netcdf.rst:22 +#: ../../source/drivers/raster/ngsgeoid.rst:15 +#: ../../source/drivers/raster/ngw.rst:36 +#: ../../source/drivers/raster/nitf.rst:52 +#: ../../source/drivers/raster/noaa_b.rst:17 +#: ../../source/drivers/raster/nsidcbin.rst:36 +#: ../../source/drivers/raster/ntv2.rst:14 +#: ../../source/drivers/raster/ogcapi.rst:25 +#: ../../source/drivers/raster/openfilegdb.rst:32 +#: ../../source/drivers/raster/ozi.rst:17 +#: ../../source/drivers/raster/palsar.rst:40 +#: ../../source/drivers/raster/paux.rst:38 +#: ../../source/drivers/raster/pcidsk.rst:58 +#: ../../source/drivers/raster/pcraster.rst:63 +#: ../../source/drivers/raster/pdf.rst:28 +#: ../../source/drivers/raster/pds.rst:33 +#: ../../source/drivers/raster/pds4.rst:36 +#: ../../source/drivers/raster/plmosaic.rst:23 +#: ../../source/drivers/raster/png.rst:40 +#: ../../source/drivers/raster/pnm.rst:33 +#: ../../source/drivers/raster/postgisraster.rst:22 +#: ../../source/drivers/raster/prf.rst:35 ../../source/drivers/raster/r.rst:22 +#: ../../source/drivers/raster/rasterlite.rst:37 +#: ../../source/drivers/raster/rasterlite2.rst:34 +#: ../../source/drivers/raster/rdb.rst:18 +#: ../../source/drivers/raster/rik.rst:21 +#: ../../source/drivers/raster/rmf.rst:22 +#: ../../source/drivers/raster/roi_pac.rst:27 +#: ../../source/drivers/raster/rpftoc.rst:63 +#: ../../source/drivers/raster/rraster.rst:51 +#: ../../source/drivers/raster/rs2.rst:34 +#: ../../source/drivers/raster/s102.rst:29 +#: ../../source/drivers/raster/s104.rst:30 +#: ../../source/drivers/raster/s111.rst:34 +#: ../../source/drivers/raster/safe.rst:33 +#: ../../source/drivers/raster/sar_ceos.rst:68 +#: ../../source/drivers/raster/sdat.rst:35 +#: ../../source/drivers/raster/sdts.rst:26 +#: ../../source/drivers/raster/sentinel2.rst:47 +#: ../../source/drivers/raster/sgi.rst:31 +#: ../../source/drivers/raster/sigdem.rst:26 +#: ../../source/drivers/raster/snodas.rst:21 +#: ../../source/drivers/raster/srp.rst:29 +#: ../../source/drivers/raster/srtmhgt.rst:34 +#: ../../source/drivers/raster/stacit.rst:101 +#: ../../source/drivers/raster/stacta.rst:85 +#: ../../source/drivers/raster/terragen.rst:20 +#: ../../source/drivers/raster/tga.rst:26 +#: ../../source/drivers/raster/til.rst:14 +#: ../../source/drivers/raster/tiledb.rst:19 +#: ../../source/drivers/raster/tsx.rst:15 +#: ../../source/drivers/raster/usgsdem.rst:34 +#: ../../source/drivers/raster/vicar.rst:23 +#: ../../source/drivers/raster/vrt.rst:2154 +#: ../../source/drivers/raster/wcs.rst:52 +#: ../../source/drivers/raster/webp.rst:32 +#: ../../source/drivers/raster/wms.rst:15 +#: ../../source/drivers/raster/wmts.rst:18 +#: ../../source/drivers/raster/xpm.rst:25 +#: ../../source/drivers/raster/xyz.rst:94 +#: ../../source/drivers/raster/zarr.rst:32 +#: ../../source/drivers/raster/zmap.rst:32 +#: ../../source/drivers/vector/amigocloud.rst:19 +#: ../../source/drivers/vector/arrow.rst:44 +#: ../../source/drivers/vector/avcbin.rst:53 +#: ../../source/drivers/vector/avce00.rst:46 +#: ../../source/drivers/vector/cad.rst:27 +#: ../../source/drivers/vector/carto.rst:17 +#: ../../source/drivers/vector/csv.rst:70 +#: ../../source/drivers/vector/csw.rst:19 +#: ../../source/drivers/vector/dgn.rst:33 +#: ../../source/drivers/vector/dgnv8.rst:31 +#: ../../source/drivers/vector/dxf.rst:19 +#: ../../source/drivers/vector/edigeo.rst:32 +#: ../../source/drivers/vector/eeda.rst:16 +#: ../../source/drivers/vector/elasticsearch.rst:21 +#: ../../source/drivers/vector/esrijson.rst:33 +#: ../../source/drivers/vector/filegdb.rst:19 +#: ../../source/drivers/vector/flatgeobuf.rst:18 +#: ../../source/drivers/vector/geoconcept.rst:21 +#: ../../source/drivers/vector/geojson.rst:30 +#: ../../source/drivers/vector/geojsonseq.rst:28 +#: ../../source/drivers/vector/georss.rst:41 +#: ../../source/drivers/vector/gml.rst:27 +#: ../../source/drivers/vector/gmlas.rst:25 +#: ../../source/drivers/vector/gmt.rst:22 +#: ../../source/drivers/vector/gpkg.rst:36 +#: ../../source/drivers/vector/gpsbabel.rst:17 +#: ../../source/drivers/vector/gpx.rst:43 +#: ../../source/drivers/vector/gtfs.rst:38 +#: ../../source/drivers/vector/hana.rst:14 +#: ../../source/drivers/vector/idb.rst:33 +#: ../../source/drivers/vector/idrisi.rst:34 +#: ../../source/drivers/vector/ili.rst:38 +#: ../../source/drivers/vector/jml.rst:26 +#: ../../source/drivers/vector/jsonfg.rst:33 +#: ../../source/drivers/vector/kml.rst:22 +#: ../../source/drivers/vector/libkml.rst:32 +#: ../../source/drivers/vector/lvbag.rst:60 +#: ../../source/drivers/vector/mapml.rst:25 +#: ../../source/drivers/vector/memory.rst:25 +#: ../../source/drivers/vector/miramon.rst:41 +#: ../../source/drivers/vector/mitab.rst:34 +#: ../../source/drivers/vector/mongodbv3.rst:21 +#: ../../source/drivers/vector/mssqlspatial.rst:15 +#: ../../source/drivers/vector/mvt.rst:55 +#: ../../source/drivers/vector/mysql.rst:37 +#: ../../source/drivers/vector/nas.rst:60 +#: ../../source/drivers/vector/netcdf.rst:28 +#: ../../source/drivers/vector/ngw.rst:36 +#: ../../source/drivers/vector/ntf.rst:25 +#: ../../source/drivers/vector/oapif.rst:22 +#: ../../source/drivers/vector/oci.rst:48 +#: ../../source/drivers/vector/odbc.rst:78 +#: ../../source/drivers/vector/ods.rst:28 +#: ../../source/drivers/vector/ogdi.rst:52 +#: ../../source/drivers/vector/openfilegdb.rst:29 +#: ../../source/drivers/vector/osm.rst:31 +#: ../../source/drivers/vector/parquet.rst:23 +#: ../../source/drivers/vector/pdf.rst:15 +#: ../../source/drivers/vector/pds.rst:29 ../../source/drivers/vector/pg.rst:25 +#: ../../source/drivers/vector/pgdump.rst:23 +#: ../../source/drivers/vector/pgeo.rst:83 +#: ../../source/drivers/vector/plscenes_data_v1.rst:14 +#: ../../source/drivers/vector/pmtiles.rst:39 +#: ../../source/drivers/vector/s57.rst:34 +#: ../../source/drivers/vector/sdts.rst:31 +#: ../../source/drivers/vector/selafin.rst:33 +#: ../../source/drivers/vector/shapefile.rst:57 +#: ../../source/drivers/vector/sqlite.rst:61 +#: ../../source/drivers/vector/svg.rst:25 +#: ../../source/drivers/vector/sxf.rst:52 +#: ../../source/drivers/vector/tiger.rst:69 +#: ../../source/drivers/vector/tiledb.rst:19 +#: ../../source/drivers/vector/topojson.rst:17 +#: ../../source/drivers/vector/vdv.rst:32 +#: ../../source/drivers/vector/vfk.rst:21 +#: ../../source/drivers/vector/vrt.rst:21 +#: ../../source/drivers/vector/wasp.rst:14 +#: ../../source/drivers/vector/wfs.rst:22 +#: ../../source/drivers/vector/xlsx.rst:36 +#: ../../source/drivers/vector/xodr.rst:17 +msgid "Driver capabilities" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:59 +#: ../../source/drivers/raster/airsar.rst:54 +#: ../../source/drivers/raster/bag.rst:472 +#: ../../source/drivers/raster/bmp.rst:50 +#: ../../source/drivers/raster/byn.rst:78 +#: ../../source/drivers/raster/cals.rst:71 +#: ../../source/drivers/raster/cog.rst:612 +#: ../../source/drivers/raster/cosar.rst:32 +#: ../../source/drivers/raster/dted.rst:116 +#: ../../source/drivers/raster/ecrgtoc.rst:37 +#: ../../source/drivers/raster/ecw.rst:294 +#: ../../source/drivers/raster/eedai.rst:178 +#: ../../source/drivers/raster/ehdr.rst:57 +#: ../../source/drivers/raster/elas.rst:27 +#: ../../source/drivers/raster/ers.rst:65 +#: ../../source/drivers/raster/esric.rst:162 +#: ../../source/drivers/raster/fast.rst:118 +#: ../../source/drivers/raster/gif.rst:64 +#: ../../source/drivers/raster/gpkg.rst:815 +#: ../../source/drivers/raster/grass.rst:18 +#: ../../source/drivers/raster/gta.rst:39 +#: ../../source/drivers/raster/gtiff.rst:1202 +#: ../../source/drivers/raster/hdf4.rst:271 +#: ../../source/drivers/raster/hdf5.rst:238 +#: ../../source/drivers/raster/hfa.rst:194 +#: ../../source/drivers/raster/isis2.rst:67 +#: ../../source/drivers/raster/isis3.rst:350 +#: ../../source/drivers/raster/jp2ecw.rst:372 +#: ../../source/drivers/raster/jp2kak.rst:288 +#: ../../source/drivers/raster/jp2lura.rst:389 +#: ../../source/drivers/raster/jp2mrsid.rst:127 +#: ../../source/drivers/raster/jp2openjpeg.rst:667 +#: ../../source/drivers/raster/jpeg.rst:479 +#: ../../source/drivers/raster/jpegxl.rst:193 +#: ../../source/drivers/raster/jpipkak.rst:255 +#: ../../source/drivers/raster/kea.rst:132 +#: ../../source/drivers/raster/l1b.rst:129 +#: ../../source/drivers/raster/mbtiles.rst:646 +#: ../../source/drivers/raster/msg.rst:205 +#: ../../source/drivers/raster/palsar.rst:47 +#: ../../source/drivers/raster/pds.rst:119 +#: ../../source/drivers/raster/plmosaic.rst:215 +#: ../../source/drivers/raster/postgisraster.rst:130 +#: ../../source/drivers/raster/prf.rst:40 +#: ../../source/drivers/raster/rasterlite.rst:290 +#: ../../source/drivers/raster/rasterlite2.rst:192 +#: ../../source/drivers/raster/rraster.rst:62 +#: ../../source/drivers/raster/rs2.rst:68 +#: ../../source/drivers/raster/s102.rst:76 +#: ../../source/drivers/raster/s104.rst:55 +#: ../../source/drivers/raster/s111.rst:59 +#: ../../source/drivers/raster/safe.rst:146 +#: ../../source/drivers/raster/sentinel2.rst:455 +#: ../../source/drivers/raster/stacit.rst:124 +#: ../../source/drivers/raster/stacta.rst:90 +#: ../../source/drivers/raster/terragen.rst:72 +#: ../../source/drivers/raster/tiledb.rst:189 +#: ../../source/drivers/raster/vicar.rst:249 +#: ../../source/drivers/raster/wcs.rst:315 +#: ../../source/drivers/raster/webp.rst:72 +#: ../../source/drivers/raster/wms.rst:529 +#: ../../source/drivers/raster/wmts.rst:469 +#: ../../source/drivers/vector/amigocloud.rst:213 +#: ../../source/drivers/vector/avcbin.rst:60 +#: ../../source/drivers/vector/avce00.rst:53 +#: ../../source/drivers/vector/cad.rst:48 +#: ../../source/drivers/vector/carto.rst:235 +#: ../../source/drivers/vector/csw.rst:126 +#: ../../source/drivers/vector/edigeo.rst:81 +#: ../../source/drivers/vector/elasticsearch.rst:763 +#: ../../source/drivers/vector/esrijson.rst:83 +#: ../../source/drivers/vector/flatgeobuf.rst:122 +#: ../../source/drivers/vector/geoconcept.rst:286 +#: ../../source/drivers/vector/geojson.rst:550 +#: ../../source/drivers/vector/geojsonseq.rst:143 +#: ../../source/drivers/vector/georss.rst:309 +#: ../../source/drivers/vector/gml.rst:1365 +#: ../../source/drivers/vector/gmlas.rst:471 +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:351 +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:159 +#: ../../source/drivers/vector/gpkg.rst:809 +#: ../../source/drivers/vector/gpsbabel.rst:126 +#: ../../source/drivers/vector/gpx.rst:466 +#: ../../source/drivers/vector/grass.rst:18 +#: ../../source/drivers/vector/hana.rst:352 +#: ../../source/drivers/vector/jml.rst:89 +#: ../../source/drivers/vector/jsonfg.rst:234 +#: ../../source/drivers/vector/kml.rst:170 +#: ../../source/drivers/vector/lvbag.rst:106 +#: ../../source/drivers/vector/miramon.rst:369 +#: ../../source/drivers/vector/mitab.rst:204 +#: ../../source/drivers/vector/mongodbv3.rst:332 +#: ../../source/drivers/vector/ntf.rst:32 +#: ../../source/drivers/vector/oapif.rst:277 +#: ../../source/drivers/vector/oda.rst:200 +#: ../../source/drivers/vector/odbc.rst:107 +#: ../../source/drivers/vector/ogdi.rst:112 +#: ../../source/drivers/vector/osm.rst:268 +#: ../../source/drivers/vector/pdf.rst:104 +#: ../../source/drivers/vector/pds.rst:34 +#: ../../source/drivers/vector/pg.rst:583 +#: ../../source/drivers/vector/pg_advanced.rst:357 +#: ../../source/drivers/vector/pgdump.rst:283 +#: ../../source/drivers/vector/plscenes.rst:21 +#: ../../source/drivers/vector/plscenes_data_v1.rst:250 +#: ../../source/drivers/vector/pmtiles.rst:354 +#: ../../source/drivers/vector/s57.rst:371 +#: ../../source/drivers/vector/sdts.rst:38 +#: ../../source/drivers/vector/shapefile.rst:484 +#: ../../source/drivers/vector/svg.rst:32 +#: ../../source/drivers/vector/sxf.rst:59 +#: ../../source/drivers/vector/tiger.rst:242 +#: ../../source/drivers/vector/tiledb.rst:238 +#: ../../source/drivers/vector/topojson.rst:43 +#: ../../source/drivers/vector/wfs.rst:425 +#: ../../source/drivers/vector/xls.rst:45 +msgid "See Also" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:61 +msgid "Implemented as :source_file:`frmts/idrisi/IdrisiDataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:62 +msgid "`www.idrisi.com `__" +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:5 +msgid "AAIGrid -- Arc/Info ASCII Grid" +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:7 +msgid "AAIGrid" +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:11 +msgid "" +"Supported for read and write access, including reading of an affine " +"georeferencing transform and some projections. This format is the ASCII " +"interchange format for Arc/Info Grid, and takes the form of an ASCII " +"file, plus sometimes an associated .prj file. It is normally produced " +"with the Arc/Info ASCIIGRID command." +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:17 +msgid "" +"The projections support (read if a \\*.prj file is available) is quite " +"limited. Additional sample .prj files may be sent to the maintainer, " +"warmerdam@pobox.com." +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:21 +msgid "" +"The NODATA value for the grid read is also preserved when available in " +"the same format as the band data." +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:24 +msgid "The following configuration options are supported:" +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:59 +msgid "" +"The :ref:`raster.aig` driver is also available for Arc/Info Binary Grid " +"format." +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:62 +#: ../../source/drivers/raster/grassasciigrid.rst:22 +#: ../../source/drivers/raster/isg.rst:19 +msgid "NOTE: Implemented as :source_file:`frmts/aaigrid/aaigriddataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ace2.rst:5 +msgid "ACE2 -- ACE2" +msgstr "" + +#: ../../source/drivers/raster/ace2.rst:7 +#: ../../source/drivers/raster/driver_summary.rst:24 +msgid "ACE2" +msgstr "" + +#: ../../source/drivers/raster/ace2.rst:11 +msgid "" +"This is a convenience driver to read ACE2 DEMs. Those files contain raw " +"binary data. The georeferencing is entirely determined by the filename. " +"Quality, source and confidence layers are of Int16 type, whereas " +"elevation data is returned as Float32." +msgstr "" + +#: ../../source/drivers/raster/ace2.rst:16 +msgid "" +"`ACE2 product overview " +"`__" +msgstr "" + +#: ../../source/drivers/raster/ace2.rst:19 +msgid "NOTE: Implemented as :source_file:`frmts/raw/ace2dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:5 +msgid "ADRG -- ADRG/ARC Digitized Raster Graphics (.gen/.thf)" +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:7 +msgid "ADRG" +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:11 +msgid "" +"Supported by GDAL for read access. Creation is possible, but it must be " +"considered as experimental and a means of testing read access (although " +"files created by the driver can be read successfully on another GIS " +"software)" +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:16 +msgid "" +"An ADRG dataset is made of several files. The file recognised by GDAL is " +"the General Information File (.GEN). GDAL will also need the image file " +"(.IMG), where the actual data is." +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:20 +msgid "" +"The Transmission Header File (.THF) can also be used as an input to GDAL." +" If the THF references more than one image, GDAL will report the images " +"it is composed of as subdatasets. If the THF references just one image, " +"GDAL will open it directly." +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:25 +msgid "" +"Overviews, legends and insets are not used. Polar zones (ARC zone 9 and " +"18) are not supported (due to the lack of test data)." +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:28 +msgid "" +"See also : the `ADRG specification (MIL-A-89007) `__" +msgstr "" + +#: ../../source/drivers/raster/aig.rst:5 +msgid "AIG -- Arc/Info Binary Grid" +msgstr "" + +#: ../../source/drivers/raster/aig.rst:7 +msgid "AIG" +msgstr "" + +#: ../../source/drivers/raster/aig.rst:11 +msgid "" +"Supported by GDAL for read access. This format is the internal binary " +"format for Arc/Info Grid, and takes the form of a coverage level " +"directory in an Arc/Info database. To open the coverage select the " +"coverage directory, or an .adf file (such as hdr.adf) from within it. If " +"the directory does not contain file(s) with names like w001001.adf then " +"it is not a grid coverage." +msgstr "" + +#: ../../source/drivers/raster/aig.rst:18 +msgid "" +"Support includes reading of an affine georeferencing transform, some " +"projections, and a color table (.clr) if available." +msgstr "" + +#: ../../source/drivers/raster/aig.rst:21 +msgid "" +"This driver is implemented based on a reverse engineering of the format. " +"See the :ref:`raster.arcinfo_grid_format` for more details." +msgstr "" + +#: ../../source/drivers/raster/aig.rst:24 +msgid "" +"The projections support (read if a prj.adf file is available) is quite " +"limited. Additional sample prj.adf files may be sent to the maintainer, " +"warmerdam@pobox.com." +msgstr "" + +#: ../../source/drivers/raster/aig.rst:28 +msgid "NOTE: Implemented as :source_file:`frmts/aigrid/aigdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:5 +msgid "AIRSAR -- AIRSAR Polarimetric Format" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:7 +msgid "AIRSAR" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:11 +msgid "" +"Most variants of the AIRSAR Polarimetric Format produced by the AIRSAR " +"Integrated Processor are supported for reading by GDAL. AIRSAR products " +"normally include various associated data files, but only the imagery data" +" themselves is supported. Normally these are named *mission*\\ \\_l.dat " +"(L-Band) or *mission*\\ \\_c.dat (C-Band)." +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:17 +msgid "" +"AIRSAR format contains a polarimetric image in compressed stokes matrix " +"form. Internally GDAL decompresses the data into a stokes matrix, and " +"then converts that form into a covariance matrix. The returned six bands " +"are the six values needed to define the 3x3 Hermitian covariance matrix. " +"The convention used to represent the covariance matrix in terms of the " +"scattering matrix elements HH, HV (=VH), and VV is indicated below. Note " +"that the non-diagonal elements of the matrix are complex values, while " +"the diagonal values are real (though represented as complex bands)." +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:26 +#: ../../source/drivers/raster/sar_ceos.rst:56 +msgid "Band 1: Covariance_11 (Float32) = HH*conj(HH)" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:27 +#: ../../source/drivers/raster/sar_ceos.rst:57 +msgid "Band 2: Covariance_12 (CFloat32) = sqrt(2)*HH*conj(HV)" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:28 +#: ../../source/drivers/raster/sar_ceos.rst:58 +msgid "Band 3: Covariance_13 (CFloat32) = HH*conj(VV)" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:29 +#: ../../source/drivers/raster/sar_ceos.rst:59 +msgid "Band 4: Covariance_22 (Float32) = 2*HV*conj(HV)" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:30 +#: ../../source/drivers/raster/sar_ceos.rst:60 +msgid "Band 5: Covariance_23 (CFloat32) = sqrt(2)*HV*conj(VV)" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:31 +#: ../../source/drivers/raster/sar_ceos.rst:61 +msgid "Band 6: Covariance_33 (Float32) = VV*conj(VV)" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:33 +msgid "" +"The identities of the bands are also reflected in metadata and in the " +"band descriptions." +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:36 +msgid "" +"The AIRSAR product format includes (potentially) several headers of " +"information. This information is captured and represented as metadata on " +"the file as a whole. Information items from the main header are prefixed " +"with \"MH\\_\", items from the parameter header are prefixed with " +"\"PH\\_\" and information from the calibration header are prefixed with " +"\"CH\\_\". The metadata item names are derived automatically from the " +"names of the fields within the header itself." +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:44 +msgid "" +"No effort is made to read files associated with the AIRSAR product such " +"as *mission*\\ \\_l.mocomp, *mission*\\ \\_meta.airsar or *mission*\\ " +"\\_meta.podaac." +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:56 +msgid "" +"`AIRSAR Data Format " +"`__" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:5 +msgid "Arc/Info Binary Grid Format" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:7 +msgid "" +"*by* `Frank Warmerdam `__ " +"(warmerdam@pobox.com)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:10 +msgid "" +"The Arc/Info Binary Grid format is the internal working format of the " +"Arc/Info Grid product. It is also usable and creatable within the spatial" +" analyst component of ArcView. It is a tiled (blocked) format with run " +"length compression capable of holding raster data of up to 4 byte " +"integers or 4 byte floating data." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:16 +msgid "" +"This format should not be confused with the Arc/Info ASCII Grid format " +"which is the interchange format for grids. Files can be converted between" +" binary and ASCII format with the GRIDASCII and ASCIIGRID commands in " +"Arc/Info. This format is also different than the flat binary raster " +"output of the GRIDFLOAT command. The Arc/Info binary float, and ASCII " +"formats are also accessible from within ArcView." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:23 +msgid "" +"This format should also not be confused with what I know as ESRI BIL " +"format. This is really a standard ESRI way of creating a header file " +"(.HDR) describing the data layout a binary raster file containing raster " +"data." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:29 +msgid "Version" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:31 +msgid "" +"I am not sure yet how the versions work for grid files. I have been " +"working primarily with grid files generated by ArcView 3.x, and its " +"associated gridio API. The hdr.adf files I have examined start with the " +"string **GRID1.2** for what that's worth. Certainly the file naming " +"conventions seem to follow the Arc/Info 7.x conventions rather than that " +"of earlier versions." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:39 +msgid "File Set" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:41 +msgid "" +"A grid coverage actually consists of a number of files. A grid normally " +"lives in its own directory named after the grid. For instance, the grid " +"**nwgrd1** lives in the directory **nwgrd1**, and has the following " +"component files:" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:55 +msgid "" +"Sometimes datasets will also include a prj.adf files containing the " +"projection definition in the usual ESRI format. Grids also normally have " +"associated tables in the info directory. This is beyond the scope of my " +"discussion for now." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:60 +msgid "The files have the following roles:" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:62 +msgid "" +"`dblbnd.adf <#dblbnd>`__: Contains the bounds (LLX, LLY, URX, URY) of the" +" portion of utilized portion of the grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:64 +msgid "" +"`hdr.adf <#hdr.adf>`__: This is the header, and contains information on " +"the tile sizes, and number of tiles in the dataset. It also contains " +"assorted other information I have yet to identify." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:67 +msgid "" +"`sta.adf <#sta>`__: This contains raster statistics. In particular, the " +"raster min, max, mean and standard deviation." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:69 +msgid "" +"**vat.adf**: This relates to the value attribute table. This is the table" +" corresponding integer raster values with a set of attributes. I presume " +"it is really just a pointer into info in a manner similar to the pat.adf " +"file in a vector coverage, but I haven't investigated yet." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:74 +msgid "" +"`w001001.adf <#w001001>`__: This is the file containing the actual raster" +" data." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:76 +msgid "" +"`w001001x.adf <#w001001x>`__: This is an index file containing pointers " +"to each of the tiles in the w001001.adf raster file." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:82 +msgid "dblbnd.adf - Georef Bounds" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:84 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:173 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:232 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:316 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:604 +msgid "Fields:" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:86 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:175 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:234 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:318 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:606 +msgid "Start Byte" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:88 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:177 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:236 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:320 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:608 +msgid "# of Bytes" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:90 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:179 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:238 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:322 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:610 +#: ../../source/drivers/vector/csv.rst:79 +#: ../../source/drivers/vector/selafin.rst:58 +msgid "Format" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:92 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:240 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:324 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:612 +msgid "Name" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:94 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:181 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:242 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:326 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:614 +#: ../../source/drivers/raster/lcp.rst:247 +#: ../../source/drivers/raster/vrt.rst:1109 +#: ../../source/drivers/vector/geopackage_aspatial.rst:96 +msgid "Description" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:96 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:183 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:244 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:328 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:616 +#: ../../source/drivers/raster/lcp.rst:171 +msgid "0" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:98 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:107 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:109 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:120 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:131 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:185 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:190 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:246 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:254 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:256 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:266 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:276 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:330 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:337 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:618 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:626 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:628 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:668 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:679 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:690 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:700 +#: ../../source/drivers/raster/lcp.rst:173 +#: ../../source/drivers/raster/lcp.rst:174 +#: ../../source/drivers/raster/lcp.rst:175 +#: ../../source/drivers/raster/lcp.rst:176 +#: ../../source/drivers/raster/lcp.rst:177 +#: ../../source/drivers/raster/lcp.rst:220 +#: ../../source/drivers/raster/lcp.rst:221 +#: ../../source/drivers/raster/lcp.rst:222 +#: ../../source/drivers/raster/lcp.rst:223 +#: ../../source/drivers/raster/lcp.rst:225 +#: ../../source/drivers/raster/lcp.rst:226 +msgid "8" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:100 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:111 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:122 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:133 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:248 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:258 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:268 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:278 +msgid "MSB double" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:102 +msgid "D_LLX" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:104 +msgid "" +"Lower left X (easting) of the grid. Generally -0.5 for an ungeoreferenced" +" grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:113 +msgid "D_LLY" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:115 +msgid "" +"Lower left Y (northing) of the grid. Generally -0.5 for an " +"ungeoreferenced grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:118 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:192 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:264 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:339 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:636 +msgid "16" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:124 +msgid "D_URX" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:126 +msgid "" +"Upper right X (easting) of the grid. Generally #Pixels-0.5 for an " +"ungeoreferenced grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:129 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:196 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:274 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:343 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:656 +msgid "24" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:135 +msgid "D_URY" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:137 +msgid "" +"Upper right Y (northing) of the grid. Generally #Lines-0.5 for an " +"ungeoreferenced grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:140 +msgid "" +"This file is always 32 bytes long. The bounds apply to the portion of the" +" grid that is in use, not the whole thing." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:146 +msgid "w001001x.adf - Tile Index" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:148 +msgid "This is a binary dump of the first 320 bytes of a w001001x.adf file." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:187 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:334 +msgid "" +"Magic Number (always hex 00 00 27 0A FF FF \\*\\* \\**, usually ending in" +" FC 14, FB F8 or FC 08)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:194 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:209 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:341 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:358 +msgid "zero fill" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:198 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:213 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:221 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:345 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:638 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:648 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:710 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:721 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:732 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:742 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:750 +#: ../../source/drivers/raster/jpeg.rst:357 +#: ../../source/drivers/raster/jpeg.rst:363 +#: ../../source/drivers/raster/jpeg.rst:381 +#: ../../source/drivers/raster/jpeg.rst:412 +#: ../../source/drivers/raster/jpeg.rst:423 +#: ../../source/drivers/raster/lcp.rst:171 +#: ../../source/drivers/raster/lcp.rst:172 +#: ../../source/drivers/raster/lcp.rst:173 +#: ../../source/drivers/raster/lcp.rst:178 +#: ../../source/drivers/raster/lcp.rst:179 +#: ../../source/drivers/raster/lcp.rst:180 +#: ../../source/drivers/raster/lcp.rst:182 +#: ../../source/drivers/raster/lcp.rst:183 +#: ../../source/drivers/raster/lcp.rst:184 +#: ../../source/drivers/raster/lcp.rst:186 +#: ../../source/drivers/raster/lcp.rst:187 +#: ../../source/drivers/raster/lcp.rst:188 +#: ../../source/drivers/raster/lcp.rst:190 +#: ../../source/drivers/raster/lcp.rst:191 +#: ../../source/drivers/raster/lcp.rst:192 +#: ../../source/drivers/raster/lcp.rst:194 +#: ../../source/drivers/raster/lcp.rst:195 +#: ../../source/drivers/raster/lcp.rst:196 +#: ../../source/drivers/raster/lcp.rst:198 +#: ../../source/drivers/raster/lcp.rst:199 +#: ../../source/drivers/raster/lcp.rst:200 +#: ../../source/drivers/raster/lcp.rst:202 +#: ../../source/drivers/raster/lcp.rst:203 +#: ../../source/drivers/raster/lcp.rst:204 +#: ../../source/drivers/raster/lcp.rst:206 +#: ../../source/drivers/raster/lcp.rst:207 +#: ../../source/drivers/raster/lcp.rst:208 +#: ../../source/drivers/raster/lcp.rst:210 +#: ../../source/drivers/raster/lcp.rst:211 +#: ../../source/drivers/raster/lcp.rst:212 +#: ../../source/drivers/raster/lcp.rst:214 +#: ../../source/drivers/raster/lcp.rst:215 +#: ../../source/drivers/raster/lcp.rst:216 +#: ../../source/drivers/raster/lcp.rst:218 +#: ../../source/drivers/raster/lcp.rst:219 +#: ../../source/drivers/raster/lcp.rst:224 +msgid "4" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:200 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:215 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:223 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:347 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:640 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:650 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:712 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:723 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:734 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:744 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:752 +msgid "MSB Int32" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:202 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:351 +msgid "Size of whole file in shorts (multiply by two to get file size in bytes)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:205 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:354 +#: ../../source/drivers/raster/lcp.rst:176 +msgid "28" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:207 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:356 +msgid "72" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:211 +msgid "100 + **t**\\ \\*8" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:217 +msgid "Offset to tile **t** in w001001.adf measured in two byte shorts." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:219 +msgid "104 + **t**\\ \\*8" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:225 +msgid "Size of tile **t** in 2 byte shorts." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:230 +msgid "sta.adf - Raster Statistics" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:250 +msgid "SMin" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:252 +msgid "Minimum value of a raster cell in this grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:260 +msgid "SMax" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:262 +msgid "Maximum value of a raster cell in this grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:270 +msgid "SMean" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:272 +msgid "Mean value of a raster cells in this grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:280 +msgid "SStdDev" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:282 +msgid "Standard deviation of raster cells in this grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:284 +msgid "This file is always 32 bytes long." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:289 +msgid "w001001.adf - Raster Data" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:291 +msgid "This is a binary dump of the first 320 bytes of a w001001.adf file." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:332 +msgid "RMagic" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:349 +msgid "RFileSize" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:360 +msgid "100, ..." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:362 +#: ../../source/drivers/raster/jpeg.rst:339 +#: ../../source/drivers/raster/jpeg.rst:391 +#: ../../source/drivers/raster/jpeg.rst:424 +#: ../../source/drivers/raster/jpeg.rst:426 +#: ../../source/drivers/raster/jpeg.rst:432 +#: ../../source/drivers/raster/jpeg.rst:433 +#: ../../source/drivers/raster/jpeg.rst:435 +#: ../../source/drivers/raster/jpeg.rst:437 +#: ../../source/drivers/raster/jpeg.rst:439 +#: ../../source/drivers/raster/jpeg.rst:442 +#: ../../source/drivers/raster/jpeg.rst:444 +#: ../../source/drivers/raster/jpeg.rst:446 +#: ../../source/drivers/raster/jpeg.rst:448 +#: ../../source/drivers/raster/lcp.rst:227 +#: ../../source/drivers/raster/lcp.rst:228 +#: ../../source/drivers/raster/lcp.rst:229 +#: ../../source/drivers/raster/lcp.rst:230 +#: ../../source/drivers/raster/lcp.rst:231 +#: ../../source/drivers/raster/lcp.rst:232 +#: ../../source/drivers/raster/lcp.rst:233 +#: ../../source/drivers/raster/lcp.rst:234 +#: ../../source/drivers/raster/lcp.rst:235 +#: ../../source/drivers/raster/lcp.rst:236 +#: ../../source/drivers/raster/vrt.rst:1111 +#: ../../source/drivers/raster/vrt.rst:1115 +#: ../../source/drivers/raster/vrt.rst:1135 +#: ../../source/drivers/raster/vrt.rst:1139 +#: ../../source/drivers/raster/vrt.rst:1143 +#: ../../source/drivers/raster/vrt.rst:1195 +msgid "2" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:364 +msgid "MSB Int16" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:366 +msgid "RTileSize" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:368 +msgid "" +"Size of this tiles data measured in shorts. This matches the size in the " +"index file, and does not include the tile size itself. The next tile " +"starts **2*n+2** bytes after the start of this tile, where **n** is the " +"value of this field." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:373 +msgid "102, ..." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:375 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:386 +#: ../../source/drivers/raster/fits.rst:73 +#: ../../source/drivers/raster/fits.rst:88 +#: ../../source/drivers/raster/fits.rst:98 +#: ../../source/drivers/raster/fits.rst:103 +#: ../../source/drivers/raster/fits.rst:108 +#: ../../source/drivers/raster/fits.rst:128 +#: ../../source/drivers/raster/fits.rst:133 +#: ../../source/drivers/raster/fits.rst:138 +#: ../../source/drivers/raster/fits.rst:158 +#: ../../source/drivers/raster/fits.rst:163 +#: ../../source/drivers/raster/fits.rst:188 +#: ../../source/drivers/raster/fits.rst:193 +#: ../../source/drivers/raster/fits.rst:208 +#: ../../source/drivers/raster/fits.rst:218 +#: ../../source/drivers/raster/fits.rst:228 +#: ../../source/drivers/raster/jpeg.rst:331 +#: ../../source/drivers/raster/jpeg.rst:332 +#: ../../source/drivers/raster/jpeg.rst:333 +#: ../../source/drivers/raster/jpeg.rst:334 +#: ../../source/drivers/raster/jpeg.rst:342 +#: ../../source/drivers/raster/jpeg.rst:345 +#: ../../source/drivers/raster/jpeg.rst:346 +#: ../../source/drivers/raster/jpeg.rst:347 +#: ../../source/drivers/raster/jpeg.rst:351 +#: ../../source/drivers/raster/jpeg.rst:352 +#: ../../source/drivers/raster/jpeg.rst:353 +#: ../../source/drivers/raster/jpeg.rst:354 +#: ../../source/drivers/raster/jpeg.rst:355 +#: ../../source/drivers/raster/jpeg.rst:356 +#: ../../source/drivers/raster/jpeg.rst:364 +#: ../../source/drivers/raster/jpeg.rst:365 +#: ../../source/drivers/raster/jpeg.rst:366 +#: ../../source/drivers/raster/jpeg.rst:367 +#: ../../source/drivers/raster/jpeg.rst:368 +#: ../../source/drivers/raster/jpeg.rst:369 +#: ../../source/drivers/raster/jpeg.rst:370 +#: ../../source/drivers/raster/jpeg.rst:371 +#: ../../source/drivers/raster/jpeg.rst:372 +#: ../../source/drivers/raster/jpeg.rst:373 +#: ../../source/drivers/raster/jpeg.rst:374 +#: ../../source/drivers/raster/jpeg.rst:382 +#: ../../source/drivers/raster/jpeg.rst:383 +#: ../../source/drivers/raster/jpeg.rst:384 +#: ../../source/drivers/raster/jpeg.rst:386 +#: ../../source/drivers/raster/jpeg.rst:388 +#: ../../source/drivers/raster/jpeg.rst:389 +#: ../../source/drivers/raster/jpeg.rst:390 +#: ../../source/drivers/raster/jpeg.rst:392 +#: ../../source/drivers/raster/jpeg.rst:393 +#: ../../source/drivers/raster/jpeg.rst:394 +#: ../../source/drivers/raster/jpeg.rst:395 +#: ../../source/drivers/raster/jpeg.rst:397 +#: ../../source/drivers/raster/jpeg.rst:398 +#: ../../source/drivers/raster/jpeg.rst:399 +#: ../../source/drivers/raster/jpeg.rst:400 +#: ../../source/drivers/raster/jpeg.rst:401 +#: ../../source/drivers/raster/jpeg.rst:402 +#: ../../source/drivers/raster/jpeg.rst:403 +#: ../../source/drivers/raster/jpeg.rst:404 +#: ../../source/drivers/raster/jpeg.rst:405 +#: ../../source/drivers/raster/jpeg.rst:406 +#: ../../source/drivers/raster/jpeg.rst:408 +#: ../../source/drivers/raster/jpeg.rst:428 +#: ../../source/drivers/raster/jpeg.rst:429 +#: ../../source/drivers/raster/jpeg.rst:434 +#: ../../source/drivers/raster/jpeg.rst:436 +#: ../../source/drivers/raster/jpeg.rst:438 +#: ../../source/drivers/raster/jpeg.rst:440 +#: ../../source/drivers/raster/jpeg.rst:447 +#: ../../source/drivers/raster/jpeg.rst:449 +#: ../../source/drivers/raster/jpeg.rst:453 +#: ../../source/drivers/raster/jpeg.rst:454 +#: ../../source/drivers/raster/vrt.rst:1119 +#: ../../source/drivers/raster/vrt.rst:1123 +#: ../../source/drivers/raster/vrt.rst:1127 +#: ../../source/drivers/raster/vrt.rst:1131 +#: ../../source/drivers/raster/vrt.rst:1147 +#: ../../source/drivers/raster/vrt.rst:1151 +#: ../../source/drivers/raster/vrt.rst:1155 +#: ../../source/drivers/raster/vrt.rst:1167 +#: ../../source/drivers/raster/vrt.rst:1171 +#: ../../source/drivers/raster/vrt.rst:1183 +#: ../../source/drivers/raster/vrt.rst:1191 +#: ../../source/drivers/raster/vrt.rst:1199 +#: ../../source/drivers/raster/vrt.rst:1203 +#: ../../source/drivers/raster/vrt.rst:1207 +msgid "1" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:377 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:388 +#: ../../source/drivers/vector/netcdf.rst:86 +#: ../../source/drivers/vector/netcdf.rst:122 +msgid "byte" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:379 +msgid "RTileType" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:381 +msgid "" +"Tile type code indicating the organization of the following data (integer" +" coverages only)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:384 +msgid "103, ..." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:390 +msgid "RMinSize" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:392 +msgid "" +"Number of bytes following to form the minimum value for the tile (integer" +" coverages only)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:395 +msgid "104, ..." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:397 +msgid "(RMinSize bytes)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:399 +msgid "MSB Int (var size)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:401 +msgid "RMin" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:403 +msgid "" +"The minimum value pixels for this tile. This number is added to the pixel" +" values for each pixel in this tile (integer coverages only). I must " +"stress that if RMinSize is less than 4 this is still a signed quantity. " +"For instance, if RMinSize is 2, the value is 65536 - byte0*256 - byte1 if" +" byte0 is > 127." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:409 +msgid "104+RMinSize, ..." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:411 +msgid "RTileSize*2 - 3 - RMinSize" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:413 +#: ../../source/drivers/raster/jpeg.rst:327 +#: ../../source/drivers/raster/jpeg.rst:328 +#: ../../source/drivers/raster/jpeg.rst:329 +#: ../../source/drivers/raster/jpeg.rst:330 +#: ../../source/drivers/raster/jpeg.rst:336 +#: ../../source/drivers/raster/jpeg.rst:338 +#: ../../source/drivers/raster/jpeg.rst:344 +#: ../../source/drivers/raster/jpeg.rst:348 +#: ../../source/drivers/raster/jpeg.rst:349 +#: ../../source/drivers/raster/jpeg.rst:350 +#: ../../source/drivers/raster/jpeg.rst:375 +#: ../../source/drivers/raster/jpeg.rst:376 +#: ../../source/drivers/raster/jpeg.rst:377 +#: ../../source/drivers/raster/jpeg.rst:378 +#: ../../source/drivers/raster/jpeg.rst:379 +#: ../../source/drivers/raster/jpeg.rst:380 +#: ../../source/drivers/raster/jpeg.rst:387 +#: ../../source/drivers/raster/jpeg.rst:396 +#: ../../source/drivers/raster/jpeg.rst:407 +#: ../../source/drivers/raster/jpeg.rst:410 +#: ../../source/drivers/raster/jpeg.rst:411 +#: ../../source/drivers/raster/jpeg.rst:413 +#: ../../source/drivers/raster/jpeg.rst:414 +#: ../../source/drivers/raster/jpeg.rst:415 +#: ../../source/drivers/raster/jpeg.rst:431 +#: ../../source/drivers/raster/jpeg.rst:441 +#: ../../source/drivers/raster/jpeg.rst:450 +#: ../../source/drivers/raster/jpeg.rst:451 +msgid "variable" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:415 +msgid "RTileData" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:417 +msgid "" +"The data for this tile. Format varies according to RTileType for integer " +"coverages." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:420 +msgid "" +"The fields RTileSize, RTileType, RMinSize, RMin, and RTileData occur in " +"the file for each tile of data present. They are usually packed one after" +" the other, but this isn't necessarily guaranteed. The index file " +"(w001001x.adf) should be used to establish the tile locations. Note that " +"tiles that appear in the index file with a size of zero will appear as " +"just two bytes (zeros) for the RTileSize for that tile." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:428 +msgid "Raster Size" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:430 +msgid "" +"The size of a the grid isn't as easy to deduce as one might expect. The " +"hdr.adf file contains the HTilesPerRow, HTilesPerColumn, HTileXSize, and " +"HTileYSize fields which imply a particular raster space. However, it " +"seems that this is created much larger than necessary to hold the users " +"raster data. I have created 3x1 rasters which resulted in the standard " +"8x512 tiles of 256x4 pixels each." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:437 +msgid "" +"It seems that the user portion of the raster has to be computed based on " +"the georeferenced bounds in the dblbnd.adf file (assumed to be anchored " +"at the top left of the total raster space), and the HPixelSizeX, and " +"HPixelSizeY fields from hdr.adf." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:442 +msgid "**#Pixels = (D_URX - D_LRX) / HPixelSizeX**" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:444 +msgid "**#Lines = (D_URY - D_LRY) / HPixelSizeY**" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:446 +msgid "" +"Based on this number of pixels and lines, it is possible to establish " +"what portion out of the top left of the raster is really *of interest*. " +"All regions outside this appear to empty tiles, or filled with no data " +"markers." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:452 +msgid "RTileType/RTileData" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:454 +msgid "" +"Each tile contains HBlockXSize \\* HBlockYSize pixels of data. For " +"floating point and uncompressed integer files the data is just the tile " +"size (in two bytes) followed by the pixel data as 4 byte MSB order IEEE " +"floating point words. For compressed integer tiles it is necessary to " +"interpret the RTileType to establish the details of the tile " +"organization:" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:462 +msgid "RTileType = 0x00 (constant block)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:464 +msgid "" +"All pixels take the value of the RMin. Data is ignored. It appears there " +"is sometimes a bit of meaningless data (up to four bytes) in the block." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:468 +msgid "RTileType = 0x01 (raw 1bit data)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:470 +msgid "" +"One full tile worth of data pixel values follows the RMin field, with " +"1bit per pixel." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:474 +msgid "RTileType = 0x04 (raw 4bit data)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:476 +msgid "" +"One full tiles worth of data pixel values follows the RMin field, with 4 " +"bits per pixel. The high order four bits of a byte comes before the low " +"order four bits." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:481 +msgid "RTileType = 0x08 (raw byte data)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:483 +msgid "" +"One full tiles worth of data pixel values (one byte per pixel) follows " +"the RMin field." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:487 +msgid "RTileType = 0x10 (raw 16bit data)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:489 +msgid "" +"One full tiles worth of data pixel values follows the RMin field, with 16" +" bits per pixel (MSB)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:493 +msgid "RTileType = 0x20 (raw 32bit data)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:495 +msgid "" +"One full tiles worth of data pixel values follows the RMin field, with 32" +" bits per pixel (MSB)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:499 +msgid "RTileType = 0xCF (16 bit literal runs/nodata runs)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:501 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:513 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:525 +msgid "" +"The data is organized in a series of runs. Each run starts with a marker " +"which should be interpreted as:" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:504 +msgid "" +"**Marker < 128**: The marker is followed by **Marker** pixels of literal " +"data with two MSB bytes per pixel." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:506 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:518 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:530 +msgid "" +"**Marker > 127**: The marker indicates that **256-Marker** pixels of *no " +"data* pixels should be put into the output stream. No data (other than " +"the next marker) follows this marker." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:511 +msgid "RTileType = 0xD7 (literal runs/nodata runs)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:516 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:528 +msgid "" +"**Marker < 128**: The marker is followed by **Marker** pixels of literal " +"data with one byte per pixel." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:523 +msgid "RTileType = 0xDF (RMin runs/nodata runs)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:534 +msgid "" +"This is similar to 0xD7, except that the data size is zero bytes instead " +"of 1, so only RMin values are inserted into the output stream." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:538 +msgid "RTileType = 0xE0 (run length encoded 32bit)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:540 +msgid "" +"The data is organized in a series of runs. Each run starts with a marker " +"which should be interpreted as a **count**. The four bytes following the " +"count should be interpreted as an MSB Int32 **value**. They indicate that" +" **count** pixels of **value** should be inserted into the output stream." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:547 +msgid "RTileType = 0xF0 (run length encoded 16bit)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:549 +msgid "" +"The data is organized in a series of runs. Each run starts with a marker " +"which should be interpreted as a **count**. The two bytes following the " +"count should be interpreted as an MSB Int16 **value**. They indicate that" +" **count** pixels of **value** should be inserted into the output stream." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:556 +msgid "RTileType = 0xFC/0xF8 (run length encoded 8bit)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:558 +msgid "" +"The data is organized in a series of runs. Each run starts with a marker " +"which should be interpreted as a **count**. The following byte is the " +"**value**. They indicate that **count** pixels of **value** should be " +"inserted into the output stream." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:563 +msgid "" +"The interpretation is the same for 0xFC, and 0xF8. I believe that 0xFC " +"has a lower dynamic (2 bit) range than 0xF8 (4 or 8 bit)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:567 +msgid "RTileType = 0xFF (RMin CCITT RLE 1Bit)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:569 +msgid "" +"The data stream for this file is CCITT RLE (G1 fax) compressed. The " +"format is complex but source is provided with the sample program (derived" +" from libtiff) for reading it. The result of uncompressing is 1bit data " +"so which the RMin value should be added." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:577 +msgid "hdr.adf - Header" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:579 +msgid "This is a binary dump of the first 308 bytes of a hdr.adf file." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:620 +msgid "Char" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:622 +msgid "HMagic" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:624 +msgid "Magic Number - always \"GRID1.2\\0\"" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:634 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:664 +msgid "assorted data, I don't know the purpose." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:642 +msgid "HCellType" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:644 +msgid "1 = int cover, 2 = float cover." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:646 +#: ../../source/drivers/raster/jpeg.rst:337 +#: ../../source/drivers/raster/jpeg.rst:358 +#: ../../source/drivers/raster/jpeg.rst:359 +#: ../../source/drivers/raster/lcp.rst:175 +#: ../../source/drivers/raster/sentinel2.rst:31 +#: ../../source/drivers/raster/sentinel2.rst:35 +#: ../../source/drivers/raster/sentinel2.rst:36 +#: ../../source/drivers/raster/sentinel2.rst:37 +#: ../../source/drivers/raster/sentinel2.rst:39 +#: ../../source/drivers/raster/sentinel2.rst:40 +#: ../../source/drivers/raster/sentinel2.rst:42 +#: ../../source/drivers/raster/sentinel2.rst:43 +msgid "20" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:652 +msgid "CompFlag" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:654 +msgid "0 = compressed, 1 = uncompressed" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:658 +msgid "232" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:666 +#: ../../source/drivers/raster/lcp.rst:237 +#: ../../source/drivers/raster/lcp.rst:238 +#: ../../source/drivers/raster/lcp.rst:239 +#: ../../source/drivers/raster/lcp.rst:240 +#: ../../source/drivers/raster/lcp.rst:241 +#: ../../source/drivers/raster/lcp.rst:242 +#: ../../source/drivers/raster/lcp.rst:243 +#: ../../source/drivers/raster/lcp.rst:244 +#: ../../source/drivers/raster/lcp.rst:245 +#: ../../source/drivers/raster/lcp.rst:246 +msgid "256" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:670 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:681 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:692 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:702 +msgid "MSB Double" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:672 +msgid "HPixelSizeX" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:674 +msgid "" +"Width of a pixel in georeferenced coordinates. Generally 1.0 for " +"ungeoreferenced rasters." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:677 +msgid "264" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:683 +msgid "HPixelSizeY" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:685 +msgid "" +"Height of a pixel in georeferenced coordinates. Generally 1.0 for " +"ungeoreferenced rasters." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:688 +msgid "272" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:694 +msgid "XRef" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:696 +msgid "dfLLX-(nBlocksPerRow*nBlockXSize*dfCellSizeX)/2.0" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:698 +msgid "280" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:704 +msgid "YRef" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:706 +msgid "dfURY-(3*nBlocksPerColumn*nBlockYSize*dfCellSizeY)/2.0" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:708 +msgid "288" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:714 +msgid "HTilesPerRow" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:716 +msgid "" +"The width of the file in tiles (often 8 for files of less than 2K in " +"width)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:719 +msgid "292" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:725 +msgid "HTilesPerColumn" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:727 +msgid "" +"The height of the file in tiles. Note this may be much more than the " +"number of tiles actually represented in the index file." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:730 +msgid "296" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:736 +msgid "HTileXSize" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:738 +msgid "The width of a file in pixels. Normally 256." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:740 +msgid "300" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:746 +msgid "Unknown, usually 1." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:748 +msgid "304" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:754 +msgid "HTileYSize" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:756 +msgid "Height of a tile in pixels, usually 4." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:761 +msgid "Acknowledgements" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:763 +msgid "" +"I would like to thank `Geosoft Inc. `__ for " +"partial funding of my research into this format. I would also like to " +"thank:" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:767 +msgid "Kenneth R. McVay for providing the statistics file format." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:768 +msgid "" +"Noureddine Farah of ThinkSpace who dug up lots of datasets that caused " +"problems." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:770 +msgid "Luciano Fonseca who worked out RTileType 0x01." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:771 +msgid "Martin Manningham of Global Geomatics for additional problem sample files." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:773 +msgid "" +"Harry Anderson of EDX Engineering, for showing me that floating point " +"tiles don't have RTileType." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:775 +msgid "" +"Ian Turton for supplying a sample files demonstrating the need to be " +"careful with the sign of \"short\" RMin values." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:777 +msgid "Duncan Chaundy at PCI for poking hard till I finally deduced 0xFF tiles." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:779 +msgid "Stephen Cheeseman of GeoSoft for yet more problem files." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:780 +msgid "Geoffrey Williams for a files demonstrating tile type 0x20." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:5 +msgid "BAG -- Bathymetry Attributed Grid" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:7 +msgid "BAG" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:-1 +#: ../../source/drivers/raster/basisu.rst:-1 +#: ../../source/drivers/raster/cad.rst:-1 +#: ../../source/drivers/raster/daas.rst:-1 +#: ../../source/drivers/raster/dds.rst:-1 +#: ../../source/drivers/raster/ecw.rst:-1 +#: ../../source/drivers/raster/eedai.rst:-1 +#: ../../source/drivers/raster/exr.rst:-1 +#: ../../source/drivers/raster/fits.rst:-1 +#: ../../source/drivers/raster/georaster.rst:-1 +#: ../../source/drivers/raster/gif.rst:-1 +#: ../../source/drivers/raster/gpkg.rst:-1 +#: ../../source/drivers/raster/grass.rst:-1 +#: ../../source/drivers/raster/gta.rst:-1 +#: ../../source/drivers/raster/hdf4.rst:-1 +#: ../../source/drivers/raster/hdf5.rst:-1 +#: ../../source/drivers/raster/heif.rst:-1 +#: ../../source/drivers/raster/jp2ecw.rst:-1 +#: ../../source/drivers/raster/jp2kak.rst:-1 +#: ../../source/drivers/raster/jp2lura.rst:-1 +#: ../../source/drivers/raster/jp2mrsid.rst:-1 +#: ../../source/drivers/raster/jp2openjpeg.rst:-1 +#: ../../source/drivers/raster/jpeg.rst:-1 +#: ../../source/drivers/raster/jpegxl.rst:-1 +#: ../../source/drivers/raster/jpipkak.rst:-1 +#: ../../source/drivers/raster/kea.rst:-1 +#: ../../source/drivers/raster/ktx2.rst:-1 +#: ../../source/drivers/raster/mbtiles.rst:-1 +#: ../../source/drivers/raster/mrsid.rst:-1 +#: ../../source/drivers/raster/msg.rst:-1 +#: ../../source/drivers/raster/netcdf.rst:-1 +#: ../../source/drivers/raster/ngw.rst:-1 +#: ../../source/drivers/raster/ogcapi.rst:-1 +#: ../../source/drivers/raster/pcraster.rst:-1 +#: ../../source/drivers/raster/pdf.rst:-1 +#: ../../source/drivers/raster/pdf.rst:672 +#: ../../source/drivers/raster/plmosaic.rst:-1 +#: ../../source/drivers/raster/postgisraster.rst:-1 +#: ../../source/drivers/raster/rasterlite.rst:-1 +#: ../../source/drivers/raster/rasterlite2.rst:-1 +#: ../../source/drivers/raster/rdb.rst:-1 +#: ../../source/drivers/raster/rik.rst:-1 +#: ../../source/drivers/raster/s102.rst:-1 +#: ../../source/drivers/raster/s104.rst:-1 +#: ../../source/drivers/raster/s111.rst:-1 +#: ../../source/drivers/raster/tiledb.rst:-1 +#: ../../source/drivers/raster/wcs.rst:-1 +#: ../../source/drivers/raster/webp.rst:-1 +#: ../../source/drivers/raster/wms.rst:-1 +#: ../../source/drivers/raster/wmts.rst:-1 +#: ../../source/drivers/raster/zarr.rst:-1 +#: ../../source/drivers/vector/amigocloud.rst:-1 +#: ../../source/drivers/vector/arrow.rst:-1 +#: ../../source/drivers/vector/cad.rst:-1 +#: ../../source/drivers/vector/carto.rst:-1 +#: ../../source/drivers/vector/csw.rst:-1 +#: ../../source/drivers/vector/dgnv8.rst:-1 +#: ../../source/drivers/vector/dwg.rst:-1 +#: ../../source/drivers/vector/eeda.rst:-1 +#: ../../source/drivers/vector/elasticsearch.rst:-1 +#: ../../source/drivers/vector/filegdb.rst:-1 +#: ../../source/drivers/vector/georss.rst:-1 +#: ../../source/drivers/vector/gml.rst:-1 +#: ../../source/drivers/vector/gmlas.rst:-1 +#: ../../source/drivers/vector/gpkg.rst:-1 +#: ../../source/drivers/vector/gpsbabel.rst:-1 +#: ../../source/drivers/vector/gpx.rst:-1 +#: ../../source/drivers/vector/grass.rst:-1 +#: ../../source/drivers/vector/hana.rst:-1 +#: ../../source/drivers/vector/idb.rst:-1 +#: ../../source/drivers/vector/ili.rst:-1 +#: ../../source/drivers/vector/jml.rst:-1 +#: ../../source/drivers/vector/kml.rst:-1 +#: ../../source/drivers/vector/libkml.rst:-1 +#: ../../source/drivers/vector/lvbag.rst:-1 +#: ../../source/drivers/vector/mongodbv3.rst:-1 +#: ../../source/drivers/vector/mssqlspatial.rst:-1 +#: ../../source/drivers/vector/mvt.rst:-1 +#: ../../source/drivers/vector/mysql.rst:-1 +#: ../../source/drivers/vector/nas.rst:-1 +#: ../../source/drivers/vector/netcdf.rst:-1 +#: ../../source/drivers/vector/ngw.rst:-1 +#: ../../source/drivers/vector/oapif.rst:-1 +#: ../../source/drivers/vector/oci.rst:-1 +#: ../../source/drivers/vector/odbc.rst:-1 +#: ../../source/drivers/vector/ods.rst:-1 +#: ../../source/drivers/vector/ogdi.rst:-1 +#: ../../source/drivers/vector/osm.rst:-1 +#: ../../source/drivers/vector/parquet.rst:-1 +#: ../../source/drivers/vector/pdf.rst:-1 ../../source/drivers/vector/pg.rst:-1 +#: ../../source/drivers/vector/pgeo.rst:-1 +#: ../../source/drivers/vector/plscenes.rst:-1 +#: ../../source/drivers/vector/sosi.rst:-1 +#: ../../source/drivers/vector/sqlite.rst:-1 +#: ../../source/drivers/vector/svg.rst:-1 +#: ../../source/drivers/vector/tiledb.rst:-1 +#: ../../source/drivers/vector/vfk.rst:-1 +#: ../../source/drivers/vector/wfs.rst:-1 +#: ../../source/drivers/vector/xls.rst:-1 +#: ../../source/drivers/vector/xlsx.rst:-1 +#: ../../source/drivers/vector/xodr.rst:-1 +msgid "Build dependencies" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:9 +#: ../../source/drivers/raster/driver_summary.rst:52 +#: ../../source/drivers/raster/driver_summary.rst:382 +#: ../../source/drivers/raster/driver_summary.rst:820 +#: ../../source/drivers/raster/driver_summary.rst:826 +#: ../../source/drivers/raster/driver_summary.rst:832 +#: ../../source/drivers/raster/hdf5.rst:11 +#: ../../source/drivers/raster/s102.rst:9 +#: ../../source/drivers/raster/s104.rst:9 +#: ../../source/drivers/raster/s111.rst:9 +msgid "libhdf5" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:11 +msgid "" +"This driver provides read-only support, and starting with GDAL 2.4 for " +"creation, for bathymetry data in the BAG format. BAG files are actually a" +" specific product profile in an HDF5 file, but a custom driver exists to " +"present the data in a more convenient manner than is available through " +"the generic HDF5 driver." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:17 +msgid "" +"BAG files have two image bands representing Elevation (band 1), " +"Uncertainty (band 2) values for each cell in a raster grid area. Nominal " +"Elevation values may also be present, and starting with GDAL 3.2, any 2D " +"array of numeric data type and with the same dimensions as Elevation " +"present under BAG_root will be reported as a GDAL band." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:23 +msgid "" +"The geotransform and coordinate system is extracted from the internal XML" +" metadata provided with the dataset. However, some products may have " +"unsupported coordinate system formats, if using the non-WKT way of " +"encoding the spatial reference system." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:28 +msgid "The full XML metadata is available in the \"xml:BAG\" metadata domain." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:30 +#: ../../source/drivers/raster/s102.rst:26 +msgid "Nodata, minimum and maximum values for each band are also reported." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:39 +msgid "This driver supports the :cpp:func:`GDALDriver::Create` operation" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:48 +#: ../../source/drivers/raster/daas.rst:93 +#: ../../source/drivers/raster/eedai.rst:36 +#: ../../source/drivers/raster/esric.rst:143 +#: ../../source/drivers/raster/grib.rst:125 +#: ../../source/drivers/raster/gti.rst:363 +#: ../../source/drivers/raster/gtiff.rst:305 +#: ../../source/drivers/raster/hdf4.rst:227 +#: ../../source/drivers/raster/netcdf.rst:275 +#: ../../source/drivers/raster/ngw.rst:123 +#: ../../source/drivers/raster/nitf.rst:63 +#: ../../source/drivers/raster/ogcapi.rst:74 +#: ../../source/drivers/raster/openfilegdb.rst:52 +#: ../../source/drivers/raster/plmosaic.rst:62 +#: ../../source/drivers/raster/s102.rst:36 +#: ../../source/drivers/raster/s104.rst:37 +#: ../../source/drivers/raster/s111.rst:41 +#: ../../source/drivers/raster/sentinel2.rst:176 +#: ../../source/drivers/raster/stacit.rst:42 +#: ../../source/drivers/raster/stacta.rst:56 +#: ../../source/drivers/raster/tiledb.rst:30 +#: ../../source/drivers/raster/wcs.rst:207 +#: ../../source/drivers/raster/wmts.rst:87 +#: ../../source/drivers/raster/xyz.rst:51 +#: ../../source/drivers/raster/zarr.rst:256 +#: ../../source/drivers/vector/carto.rst:118 +#: ../../source/drivers/vector/csv.rst:266 +#: ../../source/drivers/vector/csw.rst:50 +#: ../../source/drivers/vector/eeda.rst:33 +#: ../../source/drivers/vector/esrijson.rst:60 +#: ../../source/drivers/vector/flatgeobuf.rst:41 +#: ../../source/drivers/vector/geojson.rst:185 +#: ../../source/drivers/vector/gml.rst:502 +#: ../../source/drivers/vector/gmlas.rst:186 +#: ../../source/drivers/vector/gpx.rst:89 +#: ../../source/drivers/vector/jsonfg.rst:97 +#: ../../source/drivers/vector/lvbag.rst:33 +#: ../../source/drivers/vector/miramon.rst:260 +#: ../../source/drivers/vector/ngw.rst:167 +#: ../../source/drivers/vector/oapif.rst:78 +#: ../../source/drivers/vector/ods.rst:35 +#: ../../source/drivers/vector/osm.rst:223 +#: ../../source/drivers/vector/parquet.rst:32 +#: ../../source/drivers/vector/plscenes_data_v1.rst:54 +#: ../../source/drivers/vector/shapefile.rst:277 +#: ../../source/drivers/vector/sosi.rst:14 +#: ../../source/drivers/vector/tiledb.rst:99 +#: ../../source/drivers/vector/vfk.rst:28 +#: ../../source/drivers/vector/wfs.rst:312 +#: ../../source/drivers/vector/xlsx.rst:43 +#: ../../source/drivers/vector/xodr.rst:59 +msgid "Open options" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:50 +msgid "" +"|about-open-options| For open options specific to variable resolution, " +"see following chapter." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:53 +msgid "Other open options are:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:65 +msgid "Variable resolution (VR) grid support" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:67 +msgid "" +"Starting with GDAL 2.4, GDAL can handle BAG files with `variable " +"resolution grids " +"`__." +" Such datasets are made of a low-resolution grid, which is the one " +"presented by default by the driver, and for each of those low-resolution " +"cells, a higher resolution grid can be present in the file. Such higher " +"resolution grids are dubbed \"supergrids\" in GDAL." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:75 +msgid "" +"The driver has different modes of working which can be controlled by the " +"MODE open option:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:84 +msgid "" +"MODE=LOW_RES_GRID: this is the default mode (unless opening a supergrid)." +" The driver will expose the low resolution grid, and indicate in the " +"dataset metadata if the dataset has supergrids (HAS_SUPERGRIDS=TRUE), as " +"well as the minimum and maximum resolution of those grids." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:89 +msgid "" +"MODE=LIST_SUPERGRIDS: in this mode, the driver will report the various " +"supergrids in the subdataset list. It is possible to apply in this mode " +"additional open options to restrict the search" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:100 +msgid "" +"MINX=value: Minimum georeferenced X value to use as a filter for the " +"supergrids to list." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:102 +msgid "" +"MINY=value: Minimum georeferenced Y value to use as a filter for the " +"supergrids to list." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:104 +msgid "" +"MAXX=value: Maximum georeferenced X value to use as a filter for the " +"supergrids to list." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:106 +msgid "" +"MAXY=value: Maximum georeferenced Y value to use as a filter for the " +"supergrids to list." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:108 +msgid "" +"RES_FILTER_MIN=value: Minimum resolution of supergrids to take into " +"account (excluded bound)" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:110 +msgid "" +"RES_FILTER_MAX=value: Maximum resolution of supergrids to take into " +"account (included bound)" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:113 +msgid "" +"Opening a supergrid. This mode is triggered by using as a dataset name a " +"string formatted like BAG:my.bag:supergrid:{y}:{x}, which is the value of" +" the SUBDATASET_x_NAME metadata items reported by the above described " +"mode. {y} is the index (starting from 0, from the south of the grid), and" +" {x} is the index (starting from 0, from the west of the grid) of the " +"supergrid to open." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:120 +msgid "" +"MODE=RESAMPLED_GRID: in this mode, the user specify the extent and " +"resolution of a target grid, and for each cell of this target grid, the " +"driver will find the nodes of the supergrids that fall into that cell. By" +" default, it will select the node with the maximum elevation value to " +"populate the cell value. Or if no node of any supergrid are found, the " +"cell value will be set to the nodata value. Overviews are reported: note " +"that, those overviews correspond to resampled grids computed with " +"different values of the RESX and RESY parameters, but using the same " +"value population rules (and not nearest neighbour resampling of the full " +"resolution resampled grid). The last overview level is the low-resolution" +" grid (if SUPERGRIDS_MASK=NO)" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:133 +msgid "The available open options in this mode are:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:135 +msgid "" +"MINX=value: Minimum georeferenced X value for the resampled grid. By " +"default, the corresponding value of the low resolution grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:137 +msgid "" +"MINY=value: Minimum georeferenced Y value for the resampled grid. By " +"default, the corresponding value of the low resolution grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:139 +msgid "" +"MAXX=value: Maximum georeferenced X value for the resampled grid. By " +"default, the corresponding value of the low resolution grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:141 +msgid "" +"MAXY=value: Maximum georeferenced Y value for the resampled grid. By " +"default, the corresponding value of the low resolution grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:143 +msgid "" +"RESX=value: Horizontal resolution. By default, and if RES_STRATEGY is set" +" to AUTO, this will be the minimum resolution among all the supergrids." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:146 +msgid "" +"RESY=value: Vertical resolution (positive value). By default, and if " +"RES_STRATEGY is set to AUTO, this will be the minimum resolution among " +"all the supergrids." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:149 +msgid "" +"RES_STRATEGY=AUTO/MIN/MAX/MEAN: Which strategy to apply to set the " +"resampled grid resolution. By default, if none of RESX, RESY, " +"RES_FILTER_MIN and RES_FILTER_MAX is specified, the AUTO strategy will " +"correspond to the MIN strategy: that is the minimum resolution among all " +"the supergrids is used. If MAX is specified, the maximum resolution among" +" all the supergrids is used. If MEAN is specified, the mean resolution " +"among all the supergrids is used. RESX and RESY, if defined, will " +"override the resolution determined by RES_STRATEGY." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:158 +msgid "" +"RES_FILTER_MIN=value: Minimum resolution of supergrids to take into " +"account (excluded bound, except if it is the minimum resolution of " +"supergrids). By default, the minimum resolution of supergrids available. " +"If this value is specified and none of RES_STRATEGY, RES_FILTER_MAX, RESX" +" or RESY is specified, the maximum resolution among all the supergrids " +"will be used as the resolution for the resampled grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:165 +msgid "" +"RES_FILTER_MAX=value: Maximum resolution of supergrids to take into " +"account (included bound). By default, the maximum resolution of " +"supergrids available. If this value is specified and none of " +"RES_STRATEGY, RESX or RESY is specified, this will also be used as the " +"resolution for the resampled grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:170 +msgid "" +"VALUE_POPULATION=MIN/MAX/MEAN/COUNT: Which value population strategy to " +"apply to compute the resampled cell values. This default to MAX: the " +"elevation value of a target cell is the maximum elevation of all " +"supergrid nodes (potentially filtered with RES_FILTER_MIN and/or " +"RES_FILTER_MAX) that fall into this cell; the corresponding uncertainty " +"will be the uncertainty of the source node where this maximum elevation " +"si reached. If no supergrid node fall into the target cell, the nodata " +"value is set. The MIN strategy is similar, except that this is the " +"minimum elevation value among intersecting nodes that is selected. The " +"MEAN strategy uses the mean value of the elevation of intersecting nodes," +" and the maximum uncertainty of those nodes. The COUNT strategy (GDAL >= " +"3.2) exposes one single UInt32 band where each target cell contains the " +"count of supergrid nodes that fall into it." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:184 +msgid "" +"SUPERGRIDS_MASK=YES/NO. Default to NO. If set to YES, instead of the " +"elevation and uncertainty band, the dataset contains a single Byte band " +"which is boolean valued. For a target cell, if at least one supergrids " +"nodes (potentially filtered with RES_FILTER_MIN and/or RES_FILTER_MAX) " +"falls into the cell, the cell value is set at 255. Otherwise it is set at" +" 0. This can be used to distinguish if elevation values at nodata are due" +" to no source supergrid node falling into them, or if that/those " +"supergrid nodes were themselves at the nodata value." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:193 +msgid "NODATA_VALUE=value. Override the default value, which is usually 1000000." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:196 +msgid "" +"MODE=INTERPOLATED: (GDAL >= 3.8) in this mode, the user specify the " +"extent and resolution of a target grid, and for each cell of this target " +"grid, the driver will interpolate the value from the surrounding nodes of" +" the supergrid(s) that applies to the cell, using in priority bilinear " +"interpolation (for a node that falls within a supergrid and when all 4 " +"surrounding nodes of the supergrid are not at nodata value), and " +"fallbacks to barycentric interpolation or inverse distance weighting in " +"other situations." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:205 +msgid "" +"Overviews are reported. Note that those overviews correspond to resampled" +" grids computed with different values of the RESX and RESY parameters, " +"but for performance reasons, the interpolation is still limited to the " +"immediate neighbours of the target grid in the supergrid(s), which result" +" in the equivalent of nearest-neighbour downsampling of the full " +"resolution raster. The last overview level is the low-resolution grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:212 +msgid "" +"The available open options in this mode are MINX, MINY, MAXX, MAXY, RESX," +" RESY, RES_STRATEGY, RES_FILTER_MIN, RES_FILTER_MAX and NODATA_VALUE (cf " +"their above description for the MODE=RESAMPLED_GRID)" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:217 +#: ../../source/drivers/raster/s102.rst:64 +msgid "Spatial metadata support" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:219 +msgid "" +"Starting with GDAL 3.2, GDAL can expose BAG files with `spatial metadata " +"`__." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:222 +msgid "" +"When such spatial metadata is present, the subdataset list will include " +"names of the form 'BAG:\"{filename}\":georef_metadata:{name_of_layer}' " +"where ``name_of_layer`` is the name of a subgroup under " +"``/BAG_root/Georef_metadata``" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:226 +msgid "" +"The values of the ``keys`` dataset under each metadata layer are used as " +"the GDAL raster value. And the corresponding ``values`` dataset is " +"exposed as a GDAL Raster Attribute Table associated to the GDAL raster " +"band. If ``keys`` is absent, record 1 of ``values`` is assumed to be met " +"for each elevation point that does not match the nodata value of the " +"elevation band." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:232 +msgid "" +"When variable resolution grids are present, the MODE=LIST_SUPERGRIDS open" +" option will cause subdatasets of names of the form " +"'BAG:\"{filename}\":georef_metadata:{name_of_layer}:{y}:{x}' to be " +"reported. When opening such a subdataset, the ``varres_keys`` dataset " +"will be used to populate the GDAL raster value. If ``varres_keys`` is " +"absent, record 1 of ``values`` is assumed to be met for each elevation " +"point that does not match the nodata value of the variable resolution " +"elevation band." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:241 +msgid "Tracking list support" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:243 +msgid "" +"When the dataset is opened in vector mode (ogrinfo, ogr2ogr, etc.), the " +"tracking_list dataset will be reported as a OGR vector layer" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:247 +#: ../../source/drivers/raster/isis3.rst:154 +#: ../../source/drivers/raster/pds4.rst:91 +#: ../../source/drivers/raster/vicar.rst:181 +#: ../../source/drivers/vector/gmlas.rst:286 +msgid "Creation support" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:249 +msgid "" +"Starting with GDAL 2.4, the driver can create a BAG dataset (without " +"variable resolution extension) with the elevation and uncertainty bands " +"from a source dataset. The source dataset must be georeferenced, and have" +" one or two bands. The first band is assumed to be the elevation band, " +"and the second band the uncertainty band. If the second band is missing, " +"the uncertainty will be set to nodata." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:256 +msgid "" +"The driver will instantiate the BAG XML metadata by using a template " +"file, which is by default, `bag_template.xml " +"`__," +" found in the GDAL data definition files. This template contains " +"variables, present as ${KEYNAME} or ${KEYNAME:default_value} in the XML " +"file, that can be substituted by providing a creation option whose name " +"is the VAR\\_ string prefixed to the key name." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:264 +#: ../../source/drivers/raster/blx.rst:42 +#: ../../source/drivers/raster/bmp.rst:40 +#: ../../source/drivers/raster/ecw.rst:73 +#: ../../source/drivers/raster/ers.rst:35 +#: ../../source/drivers/raster/exr.rst:24 +#: ../../source/drivers/raster/georaster.rst:112 +#: ../../source/drivers/raster/gif.rst:40 +#: ../../source/drivers/raster/gta.rst:28 +#: ../../source/drivers/raster/hdf4.rst:208 +#: ../../source/drivers/raster/hf2.rst:36 +#: ../../source/drivers/raster/hfa.rst:50 +#: ../../source/drivers/raster/isis2.rst:49 +#: ../../source/drivers/raster/jp2kak.rst:147 +#: ../../source/drivers/raster/jpeg.rst:165 +#: ../../source/drivers/raster/pcidsk.rst:31 +#: ../../source/drivers/raster/rasterlite.rst:87 +#: ../../source/drivers/raster/rasterlite2.rst:68 +#: ../../source/drivers/raster/rmf.rst:59 +#: ../../source/drivers/raster/rraster.rst:29 +#: ../../source/drivers/raster/usgsdem.rst:59 +#: ../../source/drivers/raster/vrt.rst:64 +msgid "|about-creation-options| The following creation options are supported:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:337 +msgid "" +"Other required variables found in the template, such as RES, RESX, RESY, " +"RES_UNIT, HEIGHT, WIDTH, CORNER_POINTS and HORIZ_WKT will be " +"automatically filled from the input dataset metadata." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:341 +msgid "The other following creation options are available:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:380 +#: ../../source/drivers/raster/esric.rst:48 +msgid "Usage examples" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:382 +msgid "Opening in low resolution mode:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:398 +msgid "Displaying available supergrids:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:415 +msgid "Opening a particular supergrid:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:421 +msgid "" +"Converting a BAG in resampling mode with default parameters (use of " +"minimum resolution of supergrids, MAX value population rule):" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:428 +msgid "" +"Converting a BAG in resampling mode with a particular grid origin and " +"resolution" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:435 +msgid "" +"Converting a BAG in resampling mode, with a mask indicating where " +"supergrids nodes intersect the cell of the resampled dataset." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:442 +msgid "" +"Converting a BAG in resampling mode, by filtering on supergrid " +"resolutions (and the resampled grid will use 4 meter resolution by " +"default)" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:450 +msgid "" +"Converting a GeoTIFF file to a BAG dataset, and provide a custom value " +"for the ABSTRACT substituable variable." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:457 +msgid "" +"Converting a (VR) BAG in resampling mode with a particular grid " +"resolution (5m) to a BAG dataset (without variable resolution extension)," +" and provide a custom value for the ABSTRACT metadata:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:465 +msgid "Displaying the tracking list:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:474 +msgid "Implemented as :source_file:`frmts/hdf5/bagdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:475 +msgid "`The Open Navigation Surface Project `__" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:476 +msgid "" +"`Description of Bathymetric Attributed Grid Object (BAG) Version 1.6 " +"`__" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:478 +msgid "" +"`Variable resolution grid extension for BAG files " +"`__" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:480 +#: ../../source/drivers/raster/s104.rst:60 +#: ../../source/drivers/raster/s111.rst:64 +msgid ":ref:`S-102 driver `" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:5 +msgid "BASISU -- Basis Universal" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:9 +msgid "BASISU" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:11 +#: ../../source/drivers/raster/driver_summary.rst:54 +#: ../../source/drivers/raster/driver_summary.rst:58 +#: ../../source/drivers/raster/driver_summary.rst:520 +#: ../../source/drivers/raster/ktx2.rst:11 +msgid "Basis Universal" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:14 +#: ../../source/drivers/raster/ktx2.rst:14 +msgid "From https://github.com/BinomialLLC/basis_universal," +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:16 +#: ../../source/drivers/raster/ktx2.rst:16 +msgid "" +"Basis Universal is a \"supercompressed\" GPU texture data interchange " +"system that supports two highly compressed intermediate file formats " +"(.basis or the .KTX2 open standard from the Khronos Group) that can be " +"quickly transcoded to a very wide variety of GPU compressed and " +"uncompressed pixel formats." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:22 +msgid "" +"This driver handles textures with the .basis extension. For KTX2, refer " +"to the :ref:`raster.ktx2` driver." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:25 +#: ../../source/drivers/raster/ktx2.rst:26 +msgid "" +"Note that while the file format supports direct transcoding to other GPU " +"pixel formats, this GDAL driver supports only conversion between " +"uncompressed RGB(A) data and Basis Universal textures." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:29 +msgid "" +"When a file is made of several images, they are exposed as subdataset, " +"with the `BASISU:filename:image_idx` syntax." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:32 +#: ../../source/drivers/raster/ktx2.rst:33 +msgid "Mipmaps levels are exposed as GDAL overviews." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:42 +#: ../../source/drivers/raster/gpkg.rst:422 +#: ../../source/drivers/raster/gta.rst:26 +#: ../../source/drivers/raster/hf2.rst:34 +#: ../../source/drivers/raster/kea.rst:49 +#: ../../source/drivers/raster/ktx2.rst:43 +#: ../../source/drivers/raster/mbtiles.rst:255 +#: ../../source/drivers/raster/rasterlite.rst:85 +#: ../../source/drivers/raster/rasterlite2.rst:66 +#: ../../source/drivers/raster/tiledb.rst:58 +#: ../../source/drivers/raster/vrt.rst:62 +#: ../../source/drivers/raster/webp.rst:39 +#: ../../source/drivers/raster/xyz.rst:64 +#: ../../source/drivers/raster/zarr.rst:339 +#: ../../source/drivers/vector/pgdump.rst:32 +msgid "Creation options" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:44 +#: ../../source/drivers/raster/ktx2.rst:45 +msgid "" +"The format supports 2 modes: a high quality mode which is internally " +"based off the `UASTC compressed texture format " +"`_, and the original lower quality mode which is based off " +"a subset of ETC1 called \"ETC1S\". The default is ETC1S. Only input of " +"type Byte and with 1 (grey), 2 (grey+alpha), 3 (RGB) or 4 (RGB + alpha) " +"bands is supported. Refer to " +"https://github.com/BinomialLLC/basis_universal for more details on those " +"modes and their options." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:53 +#: ../../source/drivers/raster/gpkg.rst:424 +#: ../../source/drivers/raster/jp2lura.rst:80 +#: ../../source/drivers/raster/jp2openjpeg.rst:125 +#: ../../source/drivers/raster/jpegxl.rst:79 +#: ../../source/drivers/raster/ktx2.rst:54 +#: ../../source/drivers/raster/mbtiles.rst:257 +#: ../../source/drivers/raster/netcdf.rst:430 +#: ../../source/drivers/raster/nitf.rst:114 +#: ../../source/drivers/raster/nwtgrd.rst:68 +#: ../../source/drivers/raster/pdf.rst:223 ../../source/drivers/raster/r.rst:31 +msgid "|about-creation-options| The following creation options are available:" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:111 +msgid "" +"Defaults to the maximum number of virtual CPUs available. Can also be " +"controlled with the :config:`GDAL_NUM_THREADS` configuration option." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:119 +#: ../../source/drivers/raster/ktx2.rst:126 +msgid "Whether to enable MIPMAP generation." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:129 +#: ../../source/drivers/raster/dds.rst:40 +#: ../../source/drivers/raster/ktx2.rst:136 +#: ../../source/drivers/vector/mongodbv3.rst:305 +msgid "Build instructions" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:131 +#: ../../source/drivers/raster/ktx2.rst:138 +msgid "" +"Building basisu as a library requires currently building the `cmake` " +"branch of the https://github.com/rouault/basis_universal/tree/cmake fork." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:143 +#: ../../source/drivers/raster/ktx2.rst:150 +msgid "" +"Once basisu is built, GDAL CMake options must be configured by pointing " +"the basisu install prefix in the ``CMAKE_PREFIX_PATH`` variable or " +"``basisu_ROOT`` variable." +msgstr "" + +#: ../../source/drivers/raster/blx.rst:5 +msgid "BLX -- Magellan BLX Topo File Format" +msgstr "" + +#: ../../source/drivers/raster/blx.rst:7 +msgid "BLX" +msgstr "" + +#: ../../source/drivers/raster/blx.rst:11 +msgid "" +"BLX is the format for storing topographic data in Magellan GPS units. " +"This driver supports both reading and writing. In addition the 4 overview" +" levels inherent in the BLX format can be used with the driver." +msgstr "" + +#: ../../source/drivers/raster/blx.rst:15 +msgid "" +"The BLX format is tile based, for the moment the tile size is fixed to " +"128x128 size. Furthermore the dimensions must be a multiple of the tile " +"size." +msgstr "" + +#: ../../source/drivers/raster/blx.rst:19 +msgid "" +"The data type is fixed to Int16 and the value for undefined values is " +"fixed to -32768. In the BLX format undefined values are only really " +"supported on tile level. For undefined pixels in non-empty tiles see the " +"FILLUNDEF/FILLUNDEFVAL options." +msgstr "" + +#: ../../source/drivers/raster/blx.rst:34 +#: ../../source/drivers/raster/gtiff.rst:40 +#: ../../source/drivers/raster/jp2ecw.rst:49 +#: ../../source/drivers/raster/jp2kak.rst:97 +#: ../../source/drivers/raster/jp2lura.rst:29 +#: ../../source/drivers/raster/jp2mrsid.rst:27 +#: ../../source/drivers/raster/jp2openjpeg.rst:40 +#: ../../source/drivers/raster/pds.rst:54 +msgid "Georeferencing" +msgstr "" + +#: ../../source/drivers/raster/blx.rst:36 +msgid "" +"The BLX projection is fixed to WGS84 and georeferencing from BLX is " +"supported in the form of one tiepoint and pixelsize." +msgstr "" + +#: ../../source/drivers/raster/blx.rst:40 +#: ../../source/drivers/raster/bmp.rst:38 +#: ../../source/drivers/raster/cog.rst:33 +#: ../../source/drivers/raster/ecw.rst:44 +#: ../../source/drivers/raster/ers.rst:33 +#: ../../source/drivers/raster/exr.rst:22 +#: ../../source/drivers/raster/georaster.rst:110 +#: ../../source/drivers/raster/gtiff.rst:375 +#: ../../source/drivers/raster/isis2.rst:47 +#: ../../source/drivers/raster/jp2lura.rst:78 +#: ../../source/drivers/raster/jp2mrsid.rst:62 +#: ../../source/drivers/raster/jp2openjpeg.rst:123 +#: ../../source/drivers/raster/jpeg.rst:148 +#: ../../source/drivers/raster/jpegxl.rst:68 +#: ../../source/drivers/raster/lcp.rst:76 +#: ../../source/drivers/raster/mem.rst:76 +#: ../../source/drivers/raster/netcdf.rst:428 +#: ../../source/drivers/raster/nwtgrd.rst:66 +#: ../../source/drivers/raster/pcidsk.rst:29 +#: ../../source/drivers/raster/pdf.rst:221 +#: ../../source/drivers/raster/pnm.rst:18 ../../source/drivers/raster/r.rst:29 +#: ../../source/drivers/raster/rmf.rst:57 +#: ../../source/drivers/vector/kml.rst:92 +msgid "Creation Options" +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:5 +msgid "BMP -- Microsoft Windows Device Independent Bitmap" +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:7 +msgid "BMP" +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:11 +msgid "" +"MS Windows Device Independent Bitmaps supported by the Windows kernel and" +" mostly used for storing system decoration images. Due to the nature of " +"the BMP format it has several restrictions and could not be used for " +"general image storing. In particular, you can create only 1-bit " +"monochrome, 8-bit pseudocoloured and 24-bit RGB images only. Even " +"grayscale images must be saved in pseudocolour form." +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:18 +msgid "" +"This driver supports reading almost any type of the BMP files and could " +"write ones which should be supported on any Windows system. Only single- " +"or three- band files could be saved in BMP file. Input values will be " +"resampled to 8 bit." +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:23 +msgid "" +"If an ESRI world file exists with the .bpw, .bmpw or .wld extension, it " +"will be read and used to establish the geotransform for the image." +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:52 +msgid "Implemented as :source_file:`frmts/bmp/bmpdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:53 +msgid "" +"`Wikipedia BMP file format " +"`__" +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:5 +msgid "BSB -- Maptech/NOAA BSB Nautical Chart Format" +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:7 +msgid "BSB" +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:11 +msgid "" +"BSB Nautical Chart format is supported for read access, including reading" +" the colour table and the reference points (as GCPs). Note that the .BSB " +"files cannot be selected directly. Instead select the .KAP files. " +"Versions 1.1, 2.0 and 3.0 have been tested successfully." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:16 +msgid "" +"This driver should also support GEO/NOS format as supplied by Softchart. " +"These files normally have the extension .nos with associated .geo files " +"containing georeferencing ... the .geo files are currently ignored." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:20 +msgid "" +"This driver is based on work by Mike Higgins. See the " +":source_file:`frmts/bsb/bsb_read.c` files for details on patents " +"affecting BSB format." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:23 +msgid "" +"It is possible to select an alternate color palette via the BSB_PALETTE " +"configuration option. The default value is RGB. Other common values that " +"can be found are : DAY, DSK, NGT, NGR, GRY, PRC, PRG..." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:28 +msgid "NOTE: Implemented as :source_file:`frmts/bsb/bsbdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:39 +#: ../../source/drivers/raster/cals.rst:35 +#: ../../source/drivers/raster/eedai.rst:150 +#: ../../source/drivers/raster/fast.rst:106 +#: ../../source/drivers/raster/gpkg.rst:638 +#: ../../source/drivers/raster/gtiff.rst:164 +#: ../../source/drivers/raster/hdf4.rst:220 +#: ../../source/drivers/raster/isis3.rst:46 +#: ../../source/drivers/raster/jp2ecw.rst:338 +#: ../../source/drivers/raster/l1b.rst:67 +#: ../../source/drivers/raster/lcp.rst:47 +#: ../../source/drivers/raster/mrsid.rst:37 +#: ../../source/drivers/raster/ngw.rst:181 +#: ../../source/drivers/raster/nwtgrd.rst:51 +#: ../../source/drivers/raster/openfilegdb.rst:77 +#: ../../source/drivers/raster/pdf.rst:42 +#: ../../source/drivers/raster/pds4.rst:47 +#: ../../source/drivers/raster/rmf.rst:33 +#: ../../source/drivers/raster/sentinel2.rst:139 +#: ../../source/drivers/raster/vicar.rst:35 +#: ../../source/drivers/vector/dgnv8.rst:93 +#: ../../source/drivers/vector/gpkg.rst:525 +#: ../../source/drivers/vector/ngw.rst:279 +#: ../../source/drivers/vector/parquet.rst:189 +msgid "Metadata" +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:41 +msgid "The following metadata items may be reported:" +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:43 +msgid "" +"**BSB_KNP**: content of the KNP/ header field, giving information on the " +"coordinate reference system." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:46 +msgid "" +"**BSB_KNQ**: content of the KNQ/ header field, giving information on the " +"coordinate reference system." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:49 +msgid "" +"**BSB_CUTLINE**: (starting with GDAL 3.1). When PLY/ header is present, " +"Well-Known text representation of a polygon with coordinates in " +"longitude, latitude order, representing the cutline of the chart." +msgstr "" + +#: ../../source/drivers/raster/bt.rst:5 +msgid "BT -- VTP .bt Binary Terrain Format" +msgstr "" + +#: ../../source/drivers/raster/bt.rst:7 +msgid "BT" +msgstr "" + +#: ../../source/drivers/raster/bt.rst:11 +msgid "" +"The .bt format is used for elevation data in the VTP software. The driver" +" includes support for reading and writing .bt 1.3 format including " +"support for Int16, Int32 and Float32 pixel data types." +msgstr "" + +#: ../../source/drivers/raster/bt.rst:15 +msgid "" +"The driver does **not** support reading or writing gzipped (.bt.gz) .bt " +"files even though this is supported by the VTP software. Please unpack " +"the files before using with GDAL using the \"gzip -d file.bt.gz\"." +msgstr "" + +#: ../../source/drivers/raster/bt.rst:19 +msgid "" +"Projections in external .prj files are read and written, and support for " +"most internally defined coordinate systems is also available." +msgstr "" + +#: ../../source/drivers/raster/bt.rst:22 +msgid "" +"Read/write imagery access with the GDAL .bt driver is terribly slow due " +"to a very inefficient access strategy to this column oriented data. This " +"could be corrected, but it would be a fair effort." +msgstr "" + +#: ../../source/drivers/raster/bt.rst:26 +msgid "NOTE: Implemented as :source_file:`frmts/raw/btdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/bt.rst:28 +msgid "" +"See Also: The `BT file format " +"`__ is defined on" +" the `VTP `__ web site." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:5 +msgid "BYN - Natural Resources Canada's Geoid file format (.byn)" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:7 +msgid "BYN" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:11 +msgid "" +"Files with extension \".byn\" have a binary format. The format includes " +"two sections which are the Header and the Data. The data are stored by " +"rows starting from the north. Each row is stored from the west to the " +"east. The data are either short (2 bytes) or standard (4 bytes) integers." +" The size of the bytes is defined in the header." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:17 +msgid "" +"The total size of the file is 80 bytes + (Row x Column x (2 or 4) bytes) " +"where Row is the number of rows in the grid and Column is the number of " +"columns in the grid. Row and Column can be calculated by these two " +"equations:" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:22 +msgid "Row = (North Boundary - South Boundary) / (NS Spacing) + 1" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:24 +msgid "Column = (East Boundary - West Boundary) / (EW Spacing) + 1" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:26 +msgid "" +"The \".byn\" files may contain undefined data. Depending if the data are " +"stored as 2-byte or 4-byte integers, the undefined data are expressed the" +" following way:" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:30 +msgid "" +"4-byte data (Standard integer): 9999.0 \\* Factor, the Factor is given in" +" the header" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:33 +msgid "2 byte data (Short integer): 32767" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:35 +msgid "" +"Most of the parameters in the \".byn\" header can be read by clicking the" +" “Information” icon in software GPS-H." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:38 +msgid "" +"NOTE: Files with extension \".err\" are also in the \".byn\" format. An " +"\".err\" file usually contains the error estimates of the \".byn\" file " +"of the same name (e.g., CGG2013n83.byn and CGG2013n83.err). The \".err\" " +"file will have variable Data equal to 1 or 3." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:55 +msgid "Factor" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:57 +msgid "" +"When translating from or into BYN file to or from another formats the " +"scale will affect the result profoundly." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:60 +msgid "" +"Translating to a format that supports Scale (GTIFF for example) will " +"maintain the data type and thescale information. The pixel values are " +"perfectly preserved." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:64 +msgid "" +"Translating to a format that does not support Scale will maintain the " +"data type but without the Scale, meaning loss of information on every " +"pixels." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:68 +msgid "" +"The solution to the problem above is to use \"-unscale\" and \"-ot " +"Float32\" when using gdal_translate or GDAL API. That will produce a " +"dataset without scale but with the correct pixel information. Ex.:" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:72 +msgid "gdal_translate CGG2013an83.err test2.tif -unscale -ot Float32" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:74 +msgid "" +"NOTE: The BYN header variable **Factor** is the inverse of GDAL " +"**Scale**. (Scale = 1.0 / Factor)." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:80 +msgid "Implemented as :source_file:`frmts/raw/byndataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:81 +msgid "`www.nrcan.gc.ca `__" +msgstr "" + +#: ../../source/drivers/raster/cad.rst:5 +msgid "CAD -- AutoCAD DWG raster layer" +msgstr "" + +#: ../../source/drivers/raster/cad.rst:7 ../../source/drivers/vector/cad.rst:7 +msgid "CAD" +msgstr "" + +#: ../../source/drivers/raster/cad.rst:11 +#: ../../source/drivers/raster/driver_summary.rst:94 +#: ../../source/drivers/vector/cad.rst:9 +#: ../../source/drivers/vector/driver_summary.rst:40 +msgid "(internal libopencad provided)" +msgstr "" + +#: ../../source/drivers/raster/cad.rst:13 +msgid "" +"OGR DWG support is based on libopencad, so the list of supported DWG " +"(DXF) versions can be seen in libopencad documentation. All drawing " +"entities are separated into layers as they are in DWG file. The rasters " +"are usually a separate georeferenced files (GeoTiff, Jpeg, Png etc.) " +"which exist in DWG file as separate layers. The driver try to get spatial" +" reference and other methadata from DWG Image description and set it to " +"GDALDataset." +msgstr "" + +#: ../../source/drivers/raster/cad.rst:21 +msgid "" +"NOTE: Implemented as " +":source_file:`ogr/ogrsf_frmts/cad/gdalcaddataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:5 +msgid "CALS -- CALS Type 1" +msgstr "" + +#: ../../source/drivers/raster/cals.rst:7 +msgid "CALS" +msgstr "" + +#: ../../source/drivers/raster/cals.rst:13 +msgid "" +"CALS Type 1 rasters are untiled back and white rasters made of a " +"2048-byte text header in the MIL-STD-1840 standard, followed by a single " +"datastream compressed with CCITT/ITU-T Recommendation 6, aka Group 6, aka" +" CCITT FAX 4. CALS Type 1 rasters are one of the 4 types of formats " +"described by MIL-PRF-28002C (this standard is now deprecated). Other " +"types are not handled by this driver." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:20 +msgid "" +"This driver supports reading and creation of CALS Type 1 rasters. Update " +"of existing rasters is not supported." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:23 +msgid "" +"A CALS dataset is exposed by the driver as a single-band 1-bit raster " +"with a 2-entry color table. The first entry (0) is white " +"(RGB=255,255,255) and the second entry (1) is black (RGB=0,0,0)." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:37 +msgid "" +"The following metadata items might be exposed by the driver (or read from" +" the input dataset to generate a cor" +msgstr "" + +#: ../../source/drivers/raster/cals.rst:40 +msgid "" +"**PIXEL_PATH**: First value of the \"rorient\" header field, measured in " +"degrees counterclockwise from the positive horizontal axis (east). The " +"pel path value represents the number of degrees the image would have to " +"be rotated counterclockwise in order to display the image with proper " +"viewing orientation. The permissible values for the pixel path direction " +"shall be \"0\", \"90\", \"180\", or \"270\". 0 is the typical value. If " +"PIXEL_PATH=0 and LINE_PROGRESSION=270, neither are reported." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:48 +msgid "" +"**LINE_PROGRESSION**: Second value of the \"rorient\" header field. The " +"line progression direction is measured in degrees counterclockwise from " +"the pel path direction. The permissible values for the line progression " +"direction shall be \"90\" or \"270\". 270 is the typical value. If " +"PIXEL_PATH=0 and LINE_PROGRESSION=270, neither are reported." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:54 +msgid "" +"**TIFFTAG_XRESOLUTION**: Scan X resolution in dot per inch, from the " +"\"rdensty\" header field. TIFFTAG_XRESOLUTION and TIFFTAG_YRESOLUTION are" +" always equal in CALS." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:57 +msgid "" +"**TIFFTAG_YRESOLUTION**: Scan Y resolution in dot per inch, from the " +"\"rdensty\" header field. TIFFTAG_XRESOLUTION and TIFFTAG_YRESOLUTION are" +" always equal in CALS." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:62 +#: ../../source/drivers/raster/gpkg.rst:173 +#: ../../source/drivers/raster/rasterlite.rst:64 +#: ../../source/drivers/vector/arrow.rst:53 +#: ../../source/drivers/vector/gpkg.rst:256 +#: ../../source/drivers/vector/mvt.rst:214 +#: ../../source/drivers/vector/parquet.rst:57 +#: ../../source/drivers/vector/pmtiles.rst:87 +#: ../../source/drivers/vector/tiledb.rst:84 +#: ../../source/drivers/vector/vdv.rst:41 +msgid "Creation issues" +msgstr "" + +#: ../../source/drivers/raster/cals.rst:64 +msgid "" +"Only single band 1-bit rasters are valid input to create a new CALS file." +" If the input raster has no color table, 0 is assumed to be black and 1 " +"to be white. If the input raster has a (2 entries) color table, the value" +" for the black and white color will be determined from the color table." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:73 +msgid "" +"`MIL-PRF-28002C `__" +msgstr "" + +#: ../../source/drivers/raster/cals.rst:74 +msgid "" +"`MIL-STD-1840C `__" +msgstr "" + +#: ../../source/drivers/raster/ceos.rst:5 +msgid "CEOS -- CEOS Image" +msgstr "" + +#: ../../source/drivers/raster/ceos.rst:7 +msgid "CEOS" +msgstr "" + +#: ../../source/drivers/raster/ceos.rst:11 +msgid "" +"This is a simple, read-only reader for ceos image files. To use, select " +"the main imagery file. This driver reads only the image data, and does " +"not capture any metadata, or georeferencing." +msgstr "" + +#: ../../source/drivers/raster/ceos.rst:15 +msgid "" +"This driver is known to work with CEOS data produced by Spot Image, but " +"will have problems with many other data sources. In particular, it will " +"only work with eight bit unsigned data." +msgstr "" + +#: ../../source/drivers/raster/ceos.rst:19 +msgid "" +"See the separate :ref:`raster.sar_ceos` driver for access to SAR CEOS " +"data products." +msgstr "" + +#: ../../source/drivers/raster/ceos.rst:22 +msgid "NOTE: Implemented as :source_file:`frmts/ceos/ceosdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/coasp.rst:5 +msgid "COASP -- DRDC COASP SAR Processor Raster" +msgstr "" + +#: ../../source/drivers/raster/coasp.rst:7 +msgid "COASP" +msgstr "" + +#: ../../source/drivers/raster/coasp.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/coasp/coasp_dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:5 +msgid "COG -- Cloud Optimized GeoTIFF generator" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:9 +msgid "COG" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:13 +msgid "This driver supports the creation of Cloud Optimized GeoTIFF (COG)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:15 +msgid "" +"It essentially relies upon the :ref:`raster.gtiff` driver with the " +"``COPY_SRC_OVERVIEWS=YES`` creation option, but automatically does the " +"needed preprocessing stages (reprojection if asked and creation of " +"overviews on imagery and/or mask) if not already done, and also takes " +"care of morphing the input dataset into the expected form when using some" +" compression types (for example a RGBA dataset will be transparently " +"converted to a RGB+mask dataset when selecting JPEG compression)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:35 +msgid "|about-creation-options|" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:38 +msgid "General creation options" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:53 +msgid "" +"``JPEG`` should generally only be used with Byte data (8 bit per " +"channel). But if GDAL is built with internal libtiff and libjpeg, it is" +" possible to read and write TIFF files with 12bit JPEG compressed TIFF" +" files (seen as UInt16 bands with NBITS=12). See the `\"8 and 12 bit JPEG" +" in TIFF\" `__ wiki page " +"for more details. For the COG driver, JPEG compression for 3 or 4-band " +"images automatically selects the PHOTOMETRIC=YCBCR colorspace with a " +"4:2:2 subsampling of the Y,Cb,Cr components. For a input dataset (single-" +"band or 3-band), plus an alpha band, the alpha band will be converted as " +"a 1-bit DEFLATE compressed mask." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:65 +#: ../../source/drivers/raster/gtiff.rst:463 +msgid "" +"``LZW``, ``DEFLATE`` and ``ZSTD`` compressions can be used with the " +"PREDICTOR creation option." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:67 +msgid "" +"``ZSTD`` is available when using internal libtiff and if GDAL built " +"against libzstd >=1.0, or if built against external libtiff with zstd " +"support." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:70 +msgid "``LERC`` is available when using internal libtiff." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:72 +#: ../../source/drivers/raster/gtiff.rst:472 +msgid "``LERC_ZSTD`` is available when ``LERC`` and ``ZSTD`` are available." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:74 +msgid "" +"``JXL`` is for JPEG-XL, and is only available when using internal libtiff" +" and building GDAL against https://github.com/libjxl/libjxl . JXL " +"compression may only be used on datasets with 4 bands or less. Option " +"added in GDAL 3.4" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:86 +msgid "" +"For DEFLATE/LZMA, 9 is the slowest/higher compression rate (or 12 when " +"using a libtiff with libdeflate support). The default is 6." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:88 +msgid "For ZSTD, 22 is the slowest/higher compression rate. The default is 9." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:194 +#: ../../source/drivers/raster/gtiff.rst:686 +msgid "``YES`` forces BigTIFF." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:195 +#: ../../source/drivers/raster/gtiff.rst:687 +msgid "``NO`` forces classic TIFF." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:196 +#: ../../source/drivers/raster/gtiff.rst:688 +msgid "" +"``IF_NEEDED`` will only create a BigTIFF if it is clearly needed (in the " +"uncompressed case, and image larger than 4GB. So no effect when using a " +"compression)." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:199 +msgid "" +"``IF_SAFER`` will create BigTIFF if the resulting file \\*might\\* exceed" +" 4GB. Note: this is only a heuristics that might not always work " +"depending on compression ratios." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:203 +msgid "" +"BigTIFF is a TIFF variant which can contain more than 4GiB of data (size " +"of classic TIFF is limited by that value). This option is available if " +"GDAL is built with libtiff library version 4.0 or higher. The default is " +"IF_NEEDED." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:208 +msgid "" +"When creating a new GeoTIFF with no compression, GDAL computes in advance" +" the size of the resulting file. If that computed file size is over 4GiB," +" GDAL will automatically decide to create a BigTIFF file. However, when " +"compression is used, it is not possible in advance to known the final " +"size of the file, so classical TIFF will be chosen. In that case, the " +"user must explicitly require the creation of a BigTIFF with BIGTIFF=YES " +"if the final file is anticipated to be too big for classical TIFF format." +" If BigTIFF creation is not explicitly asked or guessed and the resulting" +" file is too big for classical TIFF, libtiff will fail with an error " +"message like \"TIFFAppendToStrip:Maximum TIFF file size exceeded\"." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:250 +msgid "" +"``AUTO`` (default): source overviews will be used if present. If not " +"present, overviews will be automatically generated in the output file." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:254 +msgid "" +"``IGNORE_EXISTING``: potential existing overviews on the source dataset " +"will be ignored and new overviews will be automatically generated." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:257 +msgid "" +"``FORCE_USE_EXISTING``: potential existing overviews on the source will " +"be used. If there is no source overview, this is equivalent to specifying" +" ``NONE``." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:261 +msgid "" +"``NONE``: potential source overviews will be ignored, and no overview " +"will be generated." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:266 +msgid "" +"When using the gdal_translate utility, source overviews will not be " +"available if general options (i.e. options which are not creation " +"options, like subsetting, etc.) are used." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:281 +msgid "" +"If not specified, the driver will use all the overviews available in the " +"source raster, in :co:`OVERVIEWS=AUTO` or ``FORCE_USE_EXISTING`` modes. " +"In situations where GDAL generates overviews, the default number of " +"overview levels is such that the dimensions of the smallest overview are " +"smaller or equal to the :co:`BLOCKSIZE` value." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:292 +msgid "" +"By default (``AUTO``) the overviews will be created with the same " +"compression method as the COG." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:324 +#: ../../source/drivers/raster/gtiff.rst:774 +msgid "Write support for GeoTIFF 1.1 requires libgeotiff 1.6.0 or later." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:354 +msgid "Reprojection related creation options" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:366 +msgid "" +"The tile size indicated in the tiling scheme definition (generally 256 " +"pixels) will be used, unless the user has specified a value with the " +":co:`BLOCKSIZE` creation option, in which case the user specified one " +"will be taken into account (that is if setting a higher value than 256, " +"the original tiling scheme is modified to take into account the size of " +"the HiDPi tiles)." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:372 +msgid "" +"In non-CUSTOM mode, TARGET_SRS, RES and EXTENT options are ignored. " +"Starting with GDAL 3.2, the value of :co:`TILING_SCHEME` can also be the " +"filename of a JSON file according to the `OGC Two Dimensional Tile Matrix" +" Set standard`_, a URL to such file, the radical of a definition file in " +"the GDAL data directory (e.g. ``FOO`` for a file named ``tms_FOO.json``) " +"or the inline JSON definition. The list of available tiling schemes can " +"be obtained by looking at values of the TILING_SCHEME option reported by " +"``gdalinfo --format COG``." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:441 +msgid "Update" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:443 +msgid "" +"Updating a COG file generally breaks part of the optimizations, but still" +" produces a valid GeoTIFF file. Starting with GDAL 3.8, to avoid " +"undesired loss of the COG characteristics, opening such a file in update " +"mode will be rejected, unless the IGNORE_COG_LAYOUT_BREAK open option is " +"also explicitly set to YES." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:448 +msgid "" +"Note that a subset of operations are possible when opening a COG file in " +"read-only mode, like metadata edition (including statistics storage), " +"that will be stored in a auxiliary .aux.xml side-car file." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:453 +msgid "File format details" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:456 +msgid "High level" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:458 +msgid "A Cloud optimized GeoTIFF has the following characteristics:" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:460 +msgid "TIFF or BigTIFF file" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:461 +msgid "Tiled (512 pixels by default) for imagery, mask and overviews" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:462 +msgid "" +"Overviews until the maximum dimension of the smallest overview level is " +"lower than 512 pixels." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:464 +msgid "Compressed or not" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:465 +msgid "Pixel interleaving for multi-band dataset" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:466 +msgid "" +"Optimized layout of TIFF sections to minimize the number of GET requests " +"needed by a reader doing random read access." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:470 +msgid "Low level" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:472 +msgid "" +"A COG file is organized as the following (if using libtiff >= 4.0.11 or " +"GDAL internal libtiff. For other versions, the layout will be different " +"and some of the optimizations will not be available)." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:476 +msgid "" +"TIFF/BigTIFF header/signature and pointer to first IFD (Image File " +"Directory)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:477 +msgid "\"ghost area\" with COG optimizations (see `Header ghost area`_)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:478 +msgid "" +"IFD of the full resolution image, followed by TIFF tags values, excluding" +" the TileOffsets and TileByteCounts arrays." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:480 +msgid "" +"IFD of the mask of the full resolution image, if present, followed by " +"TIFF tags values, excluding the TileOffsets and TileByteCounts arrays." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:482 +msgid "IFD of the first (largest in dimensions) overview level, if present" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:483 +#: ../../source/drivers/raster/cog.rst:486 +#: ../../source/drivers/raster/cog.rst:492 +#: ../../source/drivers/vector/selafin.rst:253 +msgid "..." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:484 +msgid "IFD of the last (smallest) overview level, if present" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:485 +msgid "" +"IFD of the first (largest in dimensions) overview level of the mask, if " +"present" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:487 +msgid "IFD of the last (smallest) overview level of the mask, if present" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:488 +msgid "TileOffsets and TileByteCounts arrays of the above IFDs" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:489 +msgid "" +"tile data of the smallest overview, if present (with each tile followed " +"by the corresponding tile of mask data, if present), with :ref:`leader " +"and trailer bytes `" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:493 +msgid "" +"tile data of the largest overview, if present (interleaved with mask data" +" if present)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:494 +msgid "" +"tile data of the full resolution image, if present (interleaved with " +"corresponding mask data if present)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:497 +msgid "Header ghost area" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:499 +msgid "" +"To describe the specific layout of COG files, a description of the " +"features used is located at the beginning of the file, so that optimized " +"readers (like GDAL) can use them and take shortcuts. Those features are " +"described as ASCII strings \"hidden\" just after the 8 first bytes of a " +"ClassicTIFF (or after the 16 first ones for a BigTIFF). That is the first" +" IFD starts just after those strings. It is completely valid to have " +"*ghost* areas like this in a TIFF file, and readers will normally skip " +"over them. So for a COG file with a transparency mask, those strings will" +" be:" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:520 +msgid "A newline character `\\\\n` is used to separate those strings." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:521 +msgid "" +"A space character is inserted after the newline following " +"`KNOWN_INCOMPATIBLE_EDITION=NO`" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:522 +msgid "" +"For a COG without mask, the `MASK_INTERLEAVED_WITH_IMAGERY` item will not" +" be present of course." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:524 +msgid "" +"The ghost area starts with ``GDAL_STRUCTURAL_METADATA_SIZE=XXXXXX " +"bytes\\n`` (of a fixed size of 43 bytes) where XXXXXX is a 6-digit number" +" indicating the remaining size of the section (that is starting after the" +" linefeed character of this starting line)." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:529 +msgid "" +"``LAYOUT=IFDS_BEFORE_DATA``: the IFDs are located at the beginning of the" +" file. GDAL will also makes sure that the tile index arrays are written " +"just after the IFDs and before the imagery, so that a first range request" +" of 16 KB will always get all the IFDs" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:534 +msgid "" +"``BLOCK_ORDER=ROW_MAJOR``: (strile is a contraction of 'strip or tile') " +"the data for tiles is written in increasing tile id order. Future " +"enhancements could possibly implement other layouts." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:538 +msgid "" +"``BLOCK_LEADER=SIZE_AS_UINT4``: each tile data is preceded by 4 bytes, in" +" a *ghost* area as well, indicating the real tile size (in little endian " +"order). See `Tile data leader and trailer`_ for more details." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:542 +msgid "" +"``BLOCK_TRAILER=LAST_4_BYTES_REPEATED``: just after the tile data, the " +"last 4 bytes of the tile data are repeated. See `Tile data leader and " +"trailer`_ for more details." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:545 +msgid "" +"``KNOWN_INCOMPATIBLE_EDITION=NO``: when a COG is generated this is always" +" written. If GDAL is then used to modify the COG file, as most of the " +"changes done on an existing COG file, will break the optimized structure," +" GDAL will change this metadata item to KNOWN_INCOMPATIBLE_EDITION=YES, " +"and issue a warning on writing, and when reopening such file, so that " +"users know they have *broken* their COG file" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:552 +msgid "" +"``MASK_INTERLEAVED_WITH_IMAGERY=YES``: indicates that mask data " +"immediately follows imagery data. So when reading data at " +"offset=TileOffset[i] - 4 and size=TileOffset[i+1]-TileOffset[i]+4, you'll" +" get a buffer with:" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:556 +msgid "leader with imagery tile size (4 bytes)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:557 +msgid "imagery data (starting at TileOffsets[i] and of size TileByteCounts[i])" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:558 +msgid "trailer of imagery (4 bytes)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:559 +msgid "leader with mask tilesize (4 bytes)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:560 +msgid "" +"mask data (starting at mask.TileOffsets[i] and of size " +"mask.TileByteCounts[i], but none of them actually need to be read)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:562 +msgid "trailer of mask data (4 bytes)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:566 +msgid "" +"The content of the header ghost area can be retrieved by getting the " +"``GDAL_STRUCTURAL_METADATA`` metadata item of the ``TIFF`` metadata " +"domain on the datasett object (with GetMetadataItem())" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:573 +msgid "Tile data leader and trailer" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:575 +msgid "" +"Each tile data is immediately preceded by a leader, consisting of a " +"unsigned 4-byte integer, in little endian order, giving the number of " +"bytes of *payload* of the tile data that follows it. This leader is " +"*ghost* in the sense that the TileOffsets[] array does not point to it, " +"but points to the real payload. Hence the offset of the leader is " +"TileOffsets[i]-4." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:581 +msgid "" +"An optimized reader seeing the ``BLOCK_LEADER=SIZE_AS_UINT4`` metadata " +"item will thus look for TileOffset[i] and TileOffset[i+1] to deduce it " +"must fetch the data starting at offset=TileOffset[i] - 4 and of " +"size=TileOffset[i+1]-TileOffset[i]+4. It then checks the 4 first bytes to" +" see if the size in this leader marker is consistent with " +"TileOffset[i+1]-TileOffset[i]. When there is no mask, they should " +"normally be equal (modulo the size taken by BLOCK_LEADER and " +"BLOCK_TRAILER). In the case where there is a mask and " +"MASK_INTERLEAVED_WITH_IMAGERY=YES, then the tile size indicated in the " +"leader will be < TileOffset[i+1]-TileOffset[i] since the data for the " +"mask will follow the imagery data (see MASK_INTERLEAVED_WITH_IMAGERY=YES)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:592 +msgid "" +"Each tile data is immediately followed by a trailer, consisting of the " +"repetition of the last 4 bytes of the payload of the tile data. The size " +"of this trailer is *not* included in the TileByteCounts[] array. The " +"purpose of this trailer is forces readers to be able to check if TIFF " +"writers, not aware of those optimizations, have modified the TIFF file " +"in a way that breaks the optimizations. If an optimized reader detects an" +" inconsistency, it can then fallbacks to the regular/slower method of " +"using TileOffsets[i] + TileByteCounts[i]." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:601 +#: ../../source/drivers/raster/eedai.rst:163 +#: ../../source/drivers/raster/fits.rst:282 +#: ../../source/drivers/raster/gpkg.rst:739 +#: ../../source/drivers/raster/grib.rst:446 +#: ../../source/drivers/raster/isis3.rst:309 +#: ../../source/drivers/raster/ngw.rst:201 +#: ../../source/drivers/raster/openfilegdb.rst:83 +#: ../../source/drivers/raster/pdf.rst:774 +#: ../../source/drivers/raster/plmosaic.rst:108 +#: ../../source/drivers/raster/postgisraster.rst:108 +#: ../../source/drivers/raster/rasterlite.rst:184 +#: ../../source/drivers/raster/rasterlite2.rst:144 +#: ../../source/drivers/raster/safe.rst:54 +#: ../../source/drivers/raster/sentinel2.rst:198 +#: ../../source/drivers/raster/stacit.rst:106 +#: ../../source/drivers/raster/vrt.rst:1392 +#: ../../source/drivers/raster/wcs.rst:285 +#: ../../source/drivers/raster/wms.rst:382 +#: ../../source/drivers/raster/zarr.rst:511 +#: ../../source/drivers/vector/amigocloud.rst:140 +#: ../../source/drivers/vector/carto.rst:209 +#: ../../source/drivers/vector/csv.rst:517 +#: ../../source/drivers/vector/csw.rst:97 +#: ../../source/drivers/vector/eeda.rst:182 +#: ../../source/drivers/vector/elasticsearch.rst:664 +#: ../../source/drivers/vector/flatgeobuf.rst:104 +#: ../../source/drivers/vector/geoconcept.rst:171 +#: ../../source/drivers/vector/geojson.rst:522 +#: ../../source/drivers/vector/gml.rst:1348 +#: ../../source/drivers/vector/gmlas.rst:449 +#: ../../source/drivers/vector/gpkg.rst:763 +#: ../../source/drivers/vector/gpsbabel.rst:111 +#: ../../source/drivers/vector/hana.rst:272 +#: ../../source/drivers/vector/libkml.rst:959 +#: ../../source/drivers/vector/lvbag.rst:65 +#: ../../source/drivers/vector/miramon.rst:327 +#: ../../source/drivers/vector/mongodbv3.rst:284 +#: ../../source/drivers/vector/mssqlspatial.rst:289 +#: ../../source/drivers/vector/mvt.rst:430 +#: ../../source/drivers/vector/ngw.rst:367 +#: ../../source/drivers/vector/oapif.rst:145 +#: ../../source/drivers/vector/ogdi.rst:82 +#: ../../source/drivers/vector/openfilegdb.rst:344 +#: ../../source/drivers/vector/pg.rst:479 +#: ../../source/drivers/vector/pmtiles.rst:341 +#: ../../source/drivers/vector/shapefile.rst:455 +#: ../../source/drivers/vector/sosi.rst:29 +#: ../../source/drivers/vector/vfk.rst:112 +#: ../../source/drivers/vector/wfs.rst:390 +#: ../../source/drivers/vector/xlsx.rst:96 +#: ../../source/drivers/vector/xodr.rst:78 +msgid "Examples" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:614 +msgid ":ref:`raster.gtiff` driver" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:615 +msgid "" +"`How to generate and read cloud optimized GeoTIFF files " +"`__ (before GDAL " +"3.1)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:617 +msgid "" +"If your source dataset is an internally tiled geotiff with the desired " +"georeferencing and compression, using `cogger " +"`__ (possibly along with gdaladdo to" +" create overviews) will be much faster than the COG driver." +msgstr "" + +#: ../../source/drivers/raster/cosar.rst:5 +msgid "COSAR -- TerraSAR-X Complex SAR Data Product" +msgstr "" + +#: ../../source/drivers/raster/cosar.rst:7 +msgid "COSAR" +msgstr "" + +#: ../../source/drivers/raster/cosar.rst:11 +msgid "" +"This driver provides the capability to read TerraSAR-X complex data. " +"While most users will receive products in GeoTIFF format (representing " +"detected radiation reflected from the targets, or geocoded data), ScanSAR" +" products will be distributed in COSAR format." +msgstr "" + +#: ../../source/drivers/raster/cosar.rst:16 +msgid "" +"Essentially, COSAR is an annotated binary matrix, with each sample held " +"in 4 bytes (16 bits real, 16 bits imaginary) stored with the most " +"significant byte first (Big Endian). Within a COSAR container there are " +"one or more \"bursts\" which represent individual ScanSAR bursts. Note " +"that if a Stripmap or Spotlight product is held in a COSAR container it " +"is stored in a single burst." +msgstr "" + +#: ../../source/drivers/raster/cosar.rst:23 +msgid "" +"Support for ScanSAR data is currently under way, due to the difficulties " +"in fitting the ScanSAR \"burst\" identifiers into the GDAL model." +msgstr "" + +#: ../../source/drivers/raster/cosar.rst:34 +msgid "DLR Document TX-GS-DD-3307 \"Level 1b Product Format Specification.\"" +msgstr "" + +#: ../../source/drivers/raster/cpg.rst:5 +msgid "CPG -- Convair PolGASP data" +msgstr "" + +#: ../../source/drivers/raster/cpg.rst:7 +msgid "CPG" +msgstr "" + +#: ../../source/drivers/raster/cpg.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/raw/cpgdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ctable2.rst:5 +msgid "CTable2 -- CTable2 Datum Grid Shift" +msgstr "" + +#: ../../source/drivers/raster/ctable2.rst:7 +msgid "CTable2" +msgstr "" + +#: ../../source/drivers/raster/ctable2.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/raw/ctable2dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:5 +msgid "CTG -- USGS LULC Composite Theme Grid" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:7 +msgid "CTG" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:11 +msgid "" +"This driver can read USGS Land Use and Land Cover (LULC) grids encoded in" +" the Character Composite Theme Grid (CTG) format. Each file is reported " +"as a 6-band dataset of type Int32. The meaning of each band is the " +"following one :" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:16 +msgid "Land Use and Land Cover Code" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:17 +msgid "Political units Code" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:18 +msgid "Census county subdivisions and SMSA tracts Code" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:19 +msgid "Hydrologic units Code" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:20 +msgid "Federal land ownership Code" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:21 +msgid "State land ownership Code" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:23 +msgid "" +"Those files are typically named grid_cell.gz, grid_cell1.gz or " +"grid_cell2.gz on the USGS site." +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:26 +msgid "" +"`Land Use and Land Cover Digital Data (Data Users Guide 4) " +"`__ - PDF " +"version from USGS" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:29 +msgid "" +"`Land Use and Land Cover Digital Data (Data Users Guide 4) " +"`__ - HTML " +"version converted by Ben Discoe" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:32 +msgid "" +"`USGS LULC data at 250K and 100K " +"`__" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:35 +msgid "NOTE: Implemented as :source_file:`frmts/ctg/ctgdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:5 +#: ../../source/drivers/raster/driver_summary.rst:144 +msgid "DAAS (Airbus DS Intelligence Data As A Service driver)" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:7 +msgid "DAAS" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:11 +#: ../../source/drivers/raster/driver_summary.rst:148 +#: ../../source/drivers/raster/driver_summary.rst:208 +#: ../../source/drivers/raster/driver_summary.rst:628 +#: ../../source/drivers/raster/driver_summary.rst:670 +#: ../../source/drivers/raster/driver_summary.rst:730 +#: ../../source/drivers/raster/driver_summary.rst:958 +#: ../../source/drivers/raster/driver_summary.rst:970 +#: ../../source/drivers/raster/driver_summary.rst:976 +#: ../../source/drivers/raster/eedai.rst:11 +#: ../../source/drivers/raster/ngw.rst:10 +#: ../../source/drivers/raster/ogcapi.rst:11 +#: ../../source/drivers/raster/plmosaic.rst:9 +#: ../../source/drivers/raster/wcs.rst:9 ../../source/drivers/raster/wms.rst:9 +#: ../../source/drivers/raster/wmts.rst:11 +#: ../../source/drivers/vector/amigocloud.rst:11 +#: ../../source/drivers/vector/carto.rst:9 +#: ../../source/drivers/vector/csw.rst:8 +#: ../../source/drivers/vector/driver_summary.rst:20 +#: ../../source/drivers/vector/driver_summary.rst:45 +#: ../../source/drivers/vector/driver_summary.rst:55 +#: ../../source/drivers/vector/driver_summary.rst:85 +#: ../../source/drivers/vector/driver_summary.rst:90 +#: ../../source/drivers/vector/driver_summary.rst:270 +#: ../../source/drivers/vector/driver_summary.rst:280 +#: ../../source/drivers/vector/driver_summary.rst:345 +#: ../../source/drivers/vector/driver_summary.rst:430 +#: ../../source/drivers/vector/eeda.rst:10 +#: ../../source/drivers/vector/elasticsearch.rst:8 +#: ../../source/drivers/vector/ngw.rst:10 +#: ../../source/drivers/vector/oapif.rst:10 +#: ../../source/drivers/vector/plscenes.rst:8 +#: ../../source/drivers/vector/wfs.rst:8 +msgid "libcurl" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:13 +msgid "" +"This driver can connect to the Airbus DS Intelligence Data As A Service " +"API. GDAL/OGR must be built with Curl support in order for the DAAS " +"driver to be compiled." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:17 +msgid "" +"Orthorectified (with geotransform) and raw (with RPCs) images are " +"supported." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:20 +msgid "Overviews are supported." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:22 +msgid "" +"The API is not publicly available but will be released soon. Further " +"information will be found here: https://api.oneatlas.airbus.com/" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:31 +#: ../../source/drivers/raster/eedai.rst:22 +#: ../../source/drivers/raster/ngw.rst:65 +#: ../../source/drivers/raster/plmosaic.rst:28 +#: ../../source/drivers/vector/amigocloud.rst:28 +#: ../../source/drivers/vector/carto.rst:24 +#: ../../source/drivers/vector/csw.rst:24 +#: ../../source/drivers/vector/eeda.rst:21 +#: ../../source/drivers/vector/mongodbv3.rst:34 +#: ../../source/drivers/vector/ngw.rst:48 +#: ../../source/drivers/vector/oapif.rst:27 +#: ../../source/drivers/vector/plscenes_data_v1.rst:19 +#: ../../source/drivers/vector/wfs.rst:27 +msgid "Dataset name syntax" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:33 +msgid "The nominal syntax to open a datasource is :" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:39 +msgid "A more minimal syntax can be used:" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:45 +msgid "provided that the GET_METADATA_URL open option is filled." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:48 +#: ../../source/drivers/raster/ngw.rst:115 +#: ../../source/drivers/vector/amigocloud.rst:59 +#: ../../source/drivers/vector/carto.rst:43 +#: ../../source/drivers/vector/ngw.rst:100 +msgid "Authentication" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:50 +msgid "" +"Access to the API requires an authentication token. There are two methods" +" supported:" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:53 +msgid "" +"Authentication with an API key and a client id. They must be provided " +"respectively with the :oo:`API_KEY` open option (or " +":config:`GDAL_DAAS_API_KEY` configuration option) and the :oo:`CLIENT_ID`" +" open option (or :config:`GDAL_DAAS_CLIENT_ID` configuration option). In " +"that case, the driver will authenticate against the authentication " +"endpoint to get an access token." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:59 +msgid "" +"Directly providing the access token with the :oo:`ACCESS_TOKEN` open " +"option (or :config:`GDAL_DAAS_ACCESS_TOKEN` configuration option)." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:62 +msgid "" +"In both cases, the :oo:`X_FORWARDED_USER` open option (or " +":config:`GDAL_DAAS_X_FORWARDED_USER` configuration option) can be " +"specified to fill the HTTP X-Forwarded-User header in requests sent to " +"the DAAS service endpoint with the user from which the request originates" +" from." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:67 +msgid "" +"See https://api.oneatlas.airbus.com/guides/g-authentication/ for further " +"details" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:71 +#: ../../source/drivers/raster/dted.rst:26 +#: ../../source/drivers/raster/eedai.rst:82 +#: ../../source/drivers/raster/grib.rst:94 +#: ../../source/drivers/raster/gtiff.rst:913 +#: ../../source/drivers/raster/jpeg.rst:90 +#: ../../source/drivers/raster/mbtiles.rst:64 +#: ../../source/drivers/raster/ngw.rst:83 +#: ../../source/drivers/raster/pdf.rst:56 +#: ../../source/drivers/raster/pds.rst:40 +#: ../../source/drivers/raster/plmosaic.rst:69 +#: ../../source/drivers/raster/rasterlite.rst:137 +#: ../../source/drivers/raster/stacta.rst:25 +#: ../../source/drivers/raster/wms.rst:354 +#: ../../source/drivers/vector/amigocloud.rst:125 +#: ../../source/drivers/vector/carto.rst:180 +#: ../../source/drivers/vector/csv.rst:493 +#: ../../source/drivers/vector/csw.rst:89 +#: ../../source/drivers/vector/dwg.rst:39 +#: ../../source/drivers/vector/edigeo.rst:39 +#: ../../source/drivers/vector/eeda.rst:63 +#: ../../source/drivers/vector/elasticsearch.rst:622 +#: ../../source/drivers/vector/filegdb.rst:244 +#: ../../source/drivers/vector/geojson.rst:151 +#: ../../source/drivers/vector/geojsonseq.rst:56 +#: ../../source/drivers/vector/gml.rst:36 +#: ../../source/drivers/vector/gpkg.rst:485 +#: ../../source/drivers/vector/gpx.rst:52 +#: ../../source/drivers/vector/idb.rst:56 +#: ../../source/drivers/vector/jsonfg.rst:84 +#: ../../source/drivers/vector/mitab.rst:186 +#: ../../source/drivers/vector/mssqlspatial.rst:216 +#: ../../source/drivers/vector/ngw.rst:65 +#: ../../source/drivers/vector/oci.rst:125 +#: ../../source/drivers/vector/ods.rst:62 +#: ../../source/drivers/vector/ogdi.rst:68 +#: ../../source/drivers/vector/openfilegdb.rst:83 +#: ../../source/drivers/vector/osm.rst:85 +#: ../../source/drivers/vector/pdf.rst:91 +#: ../../source/drivers/vector/pgeo.rst:59 +#: ../../source/drivers/vector/plscenes_data_v1.rst:121 +#: ../../source/drivers/vector/shapefile.rst:412 +#: ../../source/drivers/vector/sqlite.rst:425 +#: ../../source/drivers/vector/vfk.rst:52 +#: ../../source/drivers/vector/wasp.rst:23 +#: ../../source/drivers/vector/wfs.rst:364 +#: ../../source/drivers/vector/xls.rst:20 +#: ../../source/drivers/vector/xlsx.rst:71 +msgid "Configuration options" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:73 +#: ../../source/drivers/raster/eedai.rst:84 +#: ../../source/drivers/raster/jpeg.rst:92 +#: ../../source/drivers/raster/plmosaic.rst:71 +msgid "|about-config-options| The following configuration options are available :" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:95 +#: ../../source/drivers/raster/eedai.rst:38 +msgid "|about-open-options| The following open options are available :" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:139 +msgid "" +"**AUTO**: for 1, 3 or 4-band images of type Byte, resolves to PNG. " +"Otherwise to RAW" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:141 +msgid "" +"**RAW**: compatible of all images. Pixels are requested in a uncompressed" +" raw format." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:143 +msgid "**PNG**: compatible of 1, 3 or 4-band images of type Byte" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:144 +msgid "**JPEG**: compatible of 1 or 3-band images of type Byte" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:145 +msgid "" +"**JPEG2000**: compatible of all images. Requires GDAL to be built with " +"one of its JPEG2000-capable drivers." +msgstr "" + +#: ../../source/drivers/raster/dds.rst:5 +msgid "DDS -- DirectDraw Surface" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:7 +msgid "DDS" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:9 +#: ../../source/drivers/raster/driver_summary.rst:154 +msgid "Crunch Lib" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:11 +msgid "" +"The DirectDraw Surface file format (uses the filename extension DDS), " +"from Microsoft, is a standard for storing data compressed with the lossy " +"S3 Texture Compression (S3TC) algorithm. The DDS format and compression " +"are provided by the crunch library." +msgstr "" + +#: ../../source/drivers/raster/dds.rst:17 +msgid "" +"Support for reading has been added in GDAL 3.1. Previous versions have " +"write-only support." +msgstr "" + +#: ../../source/drivers/raster/dds.rst:20 +msgid "" +"The driver supports the following texture formats: DXT1, DXT1A, DXT3 " +"(default), DXT5 and ETC1. You can set the texture format using the " +"creation option FORMAT." +msgstr "" + +#: ../../source/drivers/raster/dds.rst:24 +msgid "" +"The driver supports the following compression quality: SUPERFAST, FAST, " +"NORMAL (default), BETTER and UBER. You can set the compression quality " +"using the creation option QUALITY." +msgstr "" + +#: ../../source/drivers/raster/dds.rst:28 +msgid "" +"More information about `Crunch Lib " +"`__ (see below for build " +"instructions of a working fork of that repository)" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:31 +msgid "NOTE: Implemented as :source_file:`frmts/dds/ddsdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/dds.rst:42 +msgid "" +"Building crunch can be a bit difficult. The `build_fixes` branch of " +"https://github.com/rouault/crunch/ includes a CMake build system, as well" +" as a few fixes that are not found in the upstream repository" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:47 +msgid "Build crunch" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:50 +#: ../../source/drivers/raster/dds.rst:77 +#: ../../source/drivers/raster/fits.rst:351 +msgid "Linux" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:62 +#: ../../source/drivers/raster/dds.rst:84 +msgid "Windows" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:74 +msgid "Build GDAL against crunch" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:86 +msgid "In nmake.local, add the following lines:" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:5 +msgid "DERIVED -- Derived subdatasets driver" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:7 +msgid "DERIVED" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:11 +msgid "" +"This driver allows accessing subdatasets derived from a given dataset. " +"Those derived datasets have the same projection reference, geo-transform " +"and metadata than the original dataset, but derives new pixel values " +"using gdal pixel functions." +msgstr "" + +#: ../../source/drivers/raster/derived.rst:17 +msgid "Available functions" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:19 +msgid "Available derived datasets are:" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:21 +msgid "AMPLITUDE: Amplitude of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:22 +msgid "PHASE: Phase of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:23 +msgid "REAL: Real part of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:24 +msgid "IMAG: Imaginary part of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:25 +msgid "CONJ: Conjugate of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:26 +msgid "INTENSITY: Intensity (squared amplitude) of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:27 +msgid "LOGAMPLITUDE: Log10 of amplitude of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:29 +msgid "Note: for non-complex data types, only LOGAMPLITUDE will be listed." +msgstr "" + +#: ../../source/drivers/raster/derived.rst:31 +msgid "" +"A typical use is to directly access amplitude, phase or log-amplitude of " +"any complex dataset." +msgstr "" + +#: ../../source/drivers/raster/derived.rst:35 +msgid "Accessing derived subdatasets" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:37 +msgid "" +"Derived subdatasets are stored in the DERIVED_SUBDATASETS metadata " +"domain, and can be accessed using the following syntax:" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:44 +msgid "" +"where function is one of AMPLITUDE, PHASE, REAL, IMAG, CONJ, INTENSITY, " +"LOGAMPLITUDE. So as to ensure numerical precision, all derived " +"subdatasets bands will have Float64 or CFloat64 precision (depending on " +"the function used)." +msgstr "" + +#: ../../source/drivers/raster/derived.rst:49 +msgid "For instance:" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:164 +msgid "Listing available subdatasets" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:166 +msgid "" +"Available subdatasets are reported in the DERIVED_SUBDATASETS metadata " +"domain. Only functions that make sense will be reported for a given " +"dataset, which means that AMPLITUDE, PHASE, REAL, IMAG, CONJ and " +"INTENSITY will only be reported if the dataset has at least one complex " +"band. Nevertheless, even if not reported, those derived datasets are " +"still reachable with the syntax presented above." +msgstr "" + +#: ../../source/drivers/raster/derived.rst:247 +#: ../../source/drivers/raster/grib.rst:456 +#: ../../source/drivers/raster/leveller.rst:74 +#: ../../source/drivers/raster/map.rst:21 +#: ../../source/drivers/raster/mrsid.rst:67 +#: ../../source/drivers/raster/netcdf.rst:735 +#: ../../source/drivers/raster/pcidsk.rst:69 +#: ../../source/drivers/raster/pds4.rst:547 +#: ../../source/drivers/raster/r.rst:48 ../../source/drivers/raster/rmf.rst:112 +#: ../../source/drivers/raster/rpftoc.rst:55 +#: ../../source/drivers/raster/sgi.rst:21 +#: ../../source/drivers/raster/srtmhgt.rst:24 +#: ../../source/drivers/raster/zarr.rst:540 +#: ../../source/drivers/vector/eeda.rst:209 +#: ../../source/drivers/vector/mvt.rst:440 +msgid "See Also:" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:249 +msgid "" +":ref:`Using Derived Bands part of the GDAL VRT tutorial " +"`" +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:5 +msgid "DIMAP -- Spot DIMAP" +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:7 +msgid "DIMAP" +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:11 +msgid "" +"This is a read-only read for Spot DIMAP described images. To use, select " +"the METADATA.DIM (DIMAP 1), VOL_PHR.XML (DIMAP 2) or VOL_PNEO.XML (DIMAP " +"2 VHR-2020) file in a product directory, or the product directory itself." +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:15 +msgid "" +"The imagery is in a distinct imagery file, often a TIFF file, but the " +"DIMAP dataset handles accessing that file, and attaches geolocation and " +"other metadata to the dataset from the metadata xml file." +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:19 +msgid "" +"The content of the node is reported as metadata at " +"the level of the raster band. Note that the content of the " +"Spectral_Band_Info of the first band is still reported as metadata of the" +" dataset, but this should be considered as a deprecated way of getting " +"this information." +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:25 +msgid "" +"For multi-component products, each component will be exposed in a " +"subdataset." +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:27 +msgid "NOTE: Implemented as :source_file:`frmts/dimap/dimapdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/dipex.rst:5 +msgid "DIPEx -- ELAS DIPEx" +msgstr "" + +#: ../../source/drivers/raster/dipex.rst:7 +msgid "DIPEx" +msgstr "" + +#: ../../source/drivers/raster/dipex.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/raw/dipxdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/doq1.rst:5 +msgid "DOQ1 -- First Generation USGS DOQ" +msgstr "" + +#: ../../source/drivers/raster/doq1.rst:7 +msgid "DOQ1" +msgstr "" + +#: ../../source/drivers/raster/doq1.rst:11 +msgid "" +"Support for read access, including reading of an affine georeferencing " +"transform, and capture of the projection string. This format is the old, " +"unlabelled DOQ (Digital Ortho Quad) format from the USGS." +msgstr "" + +#: ../../source/drivers/raster/doq1.rst:15 +msgid "NOTE: Implemented as :source_file:`frmts/raw/doq1dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/doq2.rst:5 +msgid "DOQ2 -- New Labelled USGS DOQ" +msgstr "" + +#: ../../source/drivers/raster/doq2.rst:7 +msgid "DOQ2" +msgstr "" + +#: ../../source/drivers/raster/doq2.rst:11 +msgid "" +"Support for read access, including reading of an affine georeferencing " +"transform, capture of the projection string and reading of other " +"auxiliary fields as metadata. This format is the new, labelled DOQ " +"(Digital Ortho Quad) format from the USGS." +msgstr "" + +#: ../../source/drivers/raster/doq2.rst:16 +msgid "This driver was implemented by Derrick J Brashear." +msgstr "" + +#: ../../source/drivers/raster/doq2.rst:18 +msgid "NOTE: Implemented as :source_file:`frmts/raw/doq2dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/doq2.rst:20 +msgid "" +"See Also: `USGS DOQ Standards " +"`__" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:11 +#: ../../source/drivers/vector/driver_summary.rst:11 +msgid "Short name" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:12 +#: ../../source/drivers/vector/driver_summary.rst:12 +msgid "Long name" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:13 +msgid "Creation (1)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:14 +msgid "Copy (2)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:15 +#: ../../source/drivers/vector/driver_summary.rst:14 +msgid "Geo-referencing" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:16 +#: ../../source/drivers/vector/driver_summary.rst:15 +msgid "Build requirements" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:17 +msgid ":ref:`AAIGrid `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:18 +msgid "Arc/Info ASCII Grid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:19 +#: ../../source/drivers/raster/driver_summary.rst:25 +#: ../../source/drivers/raster/driver_summary.rst:26 +#: ../../source/drivers/raster/driver_summary.rst:37 +#: ../../source/drivers/raster/driver_summary.rst:38 +#: ../../source/drivers/raster/driver_summary.rst:43 +#: ../../source/drivers/raster/driver_summary.rst:44 +#: ../../source/drivers/raster/driver_summary.rst:45 +#: ../../source/drivers/raster/driver_summary.rst:55 +#: ../../source/drivers/raster/driver_summary.rst:57 +#: ../../source/drivers/raster/driver_summary.rst:61 +#: ../../source/drivers/raster/driver_summary.rst:73 +#: ../../source/drivers/raster/driver_summary.rst:74 +#: ../../source/drivers/raster/driver_summary.rst:91 +#: ../../source/drivers/raster/driver_summary.rst:92 +#: ../../source/drivers/raster/driver_summary.rst:97 +#: ../../source/drivers/raster/driver_summary.rst:99 +#: ../../source/drivers/raster/driver_summary.rst:103 +#: ../../source/drivers/raster/driver_summary.rst:104 +#: ../../source/drivers/raster/driver_summary.rst:105 +#: ../../source/drivers/raster/driver_summary.rst:109 +#: ../../source/drivers/raster/driver_summary.rst:110 +#: ../../source/drivers/raster/driver_summary.rst:111 +#: ../../source/drivers/raster/driver_summary.rst:115 +#: ../../source/drivers/raster/driver_summary.rst:121 +#: ../../source/drivers/raster/driver_summary.rst:122 +#: ../../source/drivers/raster/driver_summary.rst:123 +#: ../../source/drivers/raster/driver_summary.rst:127 +#: ../../source/drivers/raster/driver_summary.rst:128 +#: ../../source/drivers/raster/driver_summary.rst:139 +#: ../../source/drivers/raster/driver_summary.rst:140 +#: ../../source/drivers/raster/driver_summary.rst:145 +#: ../../source/drivers/raster/driver_summary.rst:146 +#: ../../source/drivers/raster/driver_summary.rst:151 +#: ../../source/drivers/raster/driver_summary.rst:153 +#: ../../source/drivers/raster/driver_summary.rst:157 +#: ../../source/drivers/raster/driver_summary.rst:158 +#: ../../source/drivers/raster/driver_summary.rst:159 +#: ../../source/drivers/raster/driver_summary.rst:163 +#: ../../source/drivers/raster/driver_summary.rst:164 +#: ../../source/drivers/raster/driver_summary.rst:169 +#: ../../source/drivers/raster/driver_summary.rst:170 +#: ../../source/drivers/raster/driver_summary.rst:175 +#: ../../source/drivers/raster/driver_summary.rst:176 +#: ../../source/drivers/raster/driver_summary.rst:181 +#: ../../source/drivers/raster/driver_summary.rst:182 +#: ../../source/drivers/raster/driver_summary.rst:187 +#: ../../source/drivers/raster/driver_summary.rst:193 +#: ../../source/drivers/raster/driver_summary.rst:194 +#: ../../source/drivers/raster/driver_summary.rst:205 +#: ../../source/drivers/raster/driver_summary.rst:206 +#: ../../source/drivers/raster/driver_summary.rst:217 +#: ../../source/drivers/raster/driver_summary.rst:218 +#: ../../source/drivers/raster/driver_summary.rst:241 +#: ../../source/drivers/raster/driver_summary.rst:242 +#: ../../source/drivers/raster/driver_summary.rst:243 +#: ../../source/drivers/raster/driver_summary.rst:247 +#: ../../source/drivers/raster/driver_summary.rst:248 +#: ../../source/drivers/raster/driver_summary.rst:259 +#: ../../source/drivers/raster/driver_summary.rst:260 +#: ../../source/drivers/raster/driver_summary.rst:265 +#: ../../source/drivers/raster/driver_summary.rst:277 +#: ../../source/drivers/raster/driver_summary.rst:278 +#: ../../source/drivers/raster/driver_summary.rst:279 +#: ../../source/drivers/raster/driver_summary.rst:289 +#: ../../source/drivers/raster/driver_summary.rst:290 +#: ../../source/drivers/raster/driver_summary.rst:291 +#: ../../source/drivers/raster/driver_summary.rst:295 +#: ../../source/drivers/raster/driver_summary.rst:297 +#: ../../source/drivers/raster/driver_summary.rst:307 +#: ../../source/drivers/raster/driver_summary.rst:308 +#: ../../source/drivers/raster/driver_summary.rst:309 +#: ../../source/drivers/raster/driver_summary.rst:313 +#: ../../source/drivers/raster/driver_summary.rst:314 +#: ../../source/drivers/raster/driver_summary.rst:319 +#: ../../source/drivers/raster/driver_summary.rst:331 +#: ../../source/drivers/raster/driver_summary.rst:343 +#: ../../source/drivers/raster/driver_summary.rst:344 +#: ../../source/drivers/raster/driver_summary.rst:345 +#: ../../source/drivers/raster/driver_summary.rst:349 +#: ../../source/drivers/raster/driver_summary.rst:355 +#: ../../source/drivers/raster/driver_summary.rst:356 +#: ../../source/drivers/raster/driver_summary.rst:357 +#: ../../source/drivers/raster/driver_summary.rst:367 +#: ../../source/drivers/raster/driver_summary.rst:368 +#: ../../source/drivers/raster/driver_summary.rst:379 +#: ../../source/drivers/raster/driver_summary.rst:380 +#: ../../source/drivers/raster/driver_summary.rst:385 +#: ../../source/drivers/raster/driver_summary.rst:386 +#: ../../source/drivers/raster/driver_summary.rst:387 +#: ../../source/drivers/raster/driver_summary.rst:391 +#: ../../source/drivers/raster/driver_summary.rst:415 +#: ../../source/drivers/raster/driver_summary.rst:416 +#: ../../source/drivers/raster/driver_summary.rst:427 +#: ../../source/drivers/raster/driver_summary.rst:428 +#: ../../source/drivers/raster/driver_summary.rst:445 +#: ../../source/drivers/raster/driver_summary.rst:446 +#: ../../source/drivers/raster/driver_summary.rst:457 +#: ../../source/drivers/raster/driver_summary.rst:463 +#: ../../source/drivers/raster/driver_summary.rst:469 +#: ../../source/drivers/raster/driver_summary.rst:475 +#: ../../source/drivers/raster/driver_summary.rst:481 +#: ../../source/drivers/raster/driver_summary.rst:487 +#: ../../source/drivers/raster/driver_summary.rst:493 +#: ../../source/drivers/raster/driver_summary.rst:494 +#: ../../source/drivers/raster/driver_summary.rst:505 +#: ../../source/drivers/raster/driver_summary.rst:513 +#: ../../source/drivers/raster/driver_summary.rst:517 +#: ../../source/drivers/raster/driver_summary.rst:519 +#: ../../source/drivers/raster/driver_summary.rst:523 +#: ../../source/drivers/raster/driver_summary.rst:524 +#: ../../source/drivers/raster/driver_summary.rst:530 +#: ../../source/drivers/raster/driver_summary.rst:535 +#: ../../source/drivers/raster/driver_summary.rst:547 +#: ../../source/drivers/raster/driver_summary.rst:548 +#: ../../source/drivers/raster/driver_summary.rst:553 +#: ../../source/drivers/raster/driver_summary.rst:554 +#: ../../source/drivers/raster/driver_summary.rst:589 +#: ../../source/drivers/raster/driver_summary.rst:590 +#: ../../source/drivers/raster/driver_summary.rst:595 +#: ../../source/drivers/raster/driver_summary.rst:596 +#: ../../source/drivers/raster/driver_summary.rst:601 +#: ../../source/drivers/raster/driver_summary.rst:602 +#: ../../source/drivers/raster/driver_summary.rst:607 +#: ../../source/drivers/raster/driver_summary.rst:608 +#: ../../source/drivers/raster/driver_summary.rst:619 +#: ../../source/drivers/raster/driver_summary.rst:620 +#: ../../source/drivers/raster/driver_summary.rst:625 +#: ../../source/drivers/raster/driver_summary.rst:626 +#: ../../source/drivers/raster/driver_summary.rst:637 +#: ../../source/drivers/raster/driver_summary.rst:638 +#: ../../source/drivers/raster/driver_summary.rst:643 +#: ../../source/drivers/raster/driver_summary.rst:644 +#: ../../source/drivers/raster/driver_summary.rst:667 +#: ../../source/drivers/raster/driver_summary.rst:668 +#: ../../source/drivers/raster/driver_summary.rst:673 +#: ../../source/drivers/raster/driver_summary.rst:674 +#: ../../source/drivers/raster/driver_summary.rst:679 +#: ../../source/drivers/raster/driver_summary.rst:680 +#: ../../source/drivers/raster/driver_summary.rst:685 +#: ../../source/drivers/raster/driver_summary.rst:686 +#: ../../source/drivers/raster/driver_summary.rst:693 +#: ../../source/drivers/raster/driver_summary.rst:709 +#: ../../source/drivers/raster/driver_summary.rst:715 +#: ../../source/drivers/raster/driver_summary.rst:716 +#: ../../source/drivers/raster/driver_summary.rst:727 +#: ../../source/drivers/raster/driver_summary.rst:728 +#: ../../source/drivers/raster/driver_summary.rst:733 +#: ../../source/drivers/raster/driver_summary.rst:741 +#: ../../source/drivers/raster/driver_summary.rst:745 +#: ../../source/drivers/raster/driver_summary.rst:751 +#: ../../source/drivers/raster/driver_summary.rst:752 +#: ../../source/drivers/raster/driver_summary.rst:753 +#: ../../source/drivers/raster/driver_summary.rst:757 +#: ../../source/drivers/raster/driver_summary.rst:759 +#: ../../source/drivers/raster/driver_summary.rst:763 +#: ../../source/drivers/raster/driver_summary.rst:769 +#: ../../source/drivers/raster/driver_summary.rst:775 +#: ../../source/drivers/raster/driver_summary.rst:776 +#: ../../source/drivers/raster/driver_summary.rst:781 +#: ../../source/drivers/raster/driver_summary.rst:782 +#: ../../source/drivers/raster/driver_summary.rst:799 +#: ../../source/drivers/raster/driver_summary.rst:800 +#: ../../source/drivers/raster/driver_summary.rst:811 +#: ../../source/drivers/raster/driver_summary.rst:812 +#: ../../source/drivers/raster/driver_summary.rst:817 +#: ../../source/drivers/raster/driver_summary.rst:818 +#: ../../source/drivers/raster/driver_summary.rst:823 +#: ../../source/drivers/raster/driver_summary.rst:824 +#: ../../source/drivers/raster/driver_summary.rst:829 +#: ../../source/drivers/raster/driver_summary.rst:830 +#: ../../source/drivers/raster/driver_summary.rst:835 +#: ../../source/drivers/raster/driver_summary.rst:836 +#: ../../source/drivers/raster/driver_summary.rst:841 +#: ../../source/drivers/raster/driver_summary.rst:842 +#: ../../source/drivers/raster/driver_summary.rst:853 +#: ../../source/drivers/raster/driver_summary.rst:854 +#: ../../source/drivers/raster/driver_summary.rst:859 +#: ../../source/drivers/raster/driver_summary.rst:860 +#: ../../source/drivers/raster/driver_summary.rst:867 +#: ../../source/drivers/raster/driver_summary.rst:871 +#: ../../source/drivers/raster/driver_summary.rst:877 +#: ../../source/drivers/raster/driver_summary.rst:878 +#: ../../source/drivers/raster/driver_summary.rst:883 +#: ../../source/drivers/raster/driver_summary.rst:884 +#: ../../source/drivers/raster/driver_summary.rst:889 +#: ../../source/drivers/raster/driver_summary.rst:895 +#: ../../source/drivers/raster/driver_summary.rst:896 +#: ../../source/drivers/raster/driver_summary.rst:897 +#: ../../source/drivers/raster/driver_summary.rst:901 +#: ../../source/drivers/raster/driver_summary.rst:902 +#: ../../source/drivers/raster/driver_summary.rst:903 +#: ../../source/drivers/raster/driver_summary.rst:913 +#: ../../source/drivers/raster/driver_summary.rst:914 +#: ../../source/drivers/raster/driver_summary.rst:915 +#: ../../source/drivers/raster/driver_summary.rst:919 +#: ../../source/drivers/raster/driver_summary.rst:920 +#: ../../source/drivers/raster/driver_summary.rst:931 +#: ../../source/drivers/raster/driver_summary.rst:932 +#: ../../source/drivers/raster/driver_summary.rst:937 +#: ../../source/drivers/raster/driver_summary.rst:955 +#: ../../source/drivers/raster/driver_summary.rst:956 +#: ../../source/drivers/raster/driver_summary.rst:961 +#: ../../source/drivers/raster/driver_summary.rst:963 +#: ../../source/drivers/raster/driver_summary.rst:967 +#: ../../source/drivers/raster/driver_summary.rst:973 +#: ../../source/drivers/raster/driver_summary.rst:974 +#: ../../source/drivers/raster/driver_summary.rst:979 +#: ../../source/drivers/raster/driver_summary.rst:981 +#: ../../source/drivers/raster/driver_summary.rst:985 +#: ../../source/drivers/raster/driver_summary.rst:992 +#: ../../source/drivers/raster/driver_summary.rst:997 +#: ../../source/drivers/vector/driver_summary.rst:28 +#: ../../source/drivers/vector/driver_summary.rst:33 +#: ../../source/drivers/vector/driver_summary.rst:38 +#: ../../source/drivers/vector/driver_summary.rst:53 +#: ../../source/drivers/vector/driver_summary.rst:68 +#: ../../source/drivers/vector/driver_summary.rst:69 +#: ../../source/drivers/vector/driver_summary.rst:74 +#: ../../source/drivers/vector/driver_summary.rst:78 +#: ../../source/drivers/vector/driver_summary.rst:83 +#: ../../source/drivers/vector/driver_summary.rst:93 +#: ../../source/drivers/vector/driver_summary.rst:133 +#: ../../source/drivers/vector/driver_summary.rst:158 +#: ../../source/drivers/vector/driver_summary.rst:159 +#: ../../source/drivers/vector/driver_summary.rst:163 +#: ../../source/drivers/vector/driver_summary.rst:164 +#: ../../source/drivers/vector/driver_summary.rst:178 +#: ../../source/drivers/vector/driver_summary.rst:213 +#: ../../source/drivers/vector/driver_summary.rst:214 +#: ../../source/drivers/vector/driver_summary.rst:238 +#: ../../source/drivers/vector/driver_summary.rst:258 +#: ../../source/drivers/vector/driver_summary.rst:268 +#: ../../source/drivers/vector/driver_summary.rst:273 +#: ../../source/drivers/vector/driver_summary.rst:278 +#: ../../source/drivers/vector/driver_summary.rst:288 +#: ../../source/drivers/vector/driver_summary.rst:294 +#: ../../source/drivers/vector/driver_summary.rst:298 +#: ../../source/drivers/vector/driver_summary.rst:308 +#: ../../source/drivers/vector/driver_summary.rst:323 +#: ../../source/drivers/vector/driver_summary.rst:324 +#: ../../source/drivers/vector/driver_summary.rst:338 +#: ../../source/drivers/vector/driver_summary.rst:343 +#: ../../source/drivers/vector/driver_summary.rst:344 +#: ../../source/drivers/vector/driver_summary.rst:358 +#: ../../source/drivers/vector/driver_summary.rst:373 +#: ../../source/drivers/vector/driver_summary.rst:374 +#: ../../source/drivers/vector/driver_summary.rst:383 +#: ../../source/drivers/vector/driver_summary.rst:388 +#: ../../source/drivers/vector/driver_summary.rst:393 +#: ../../source/drivers/vector/driver_summary.rst:399 +#: ../../source/drivers/vector/driver_summary.rst:403 +#: ../../source/drivers/vector/driver_summary.rst:413 +#: ../../source/drivers/vector/driver_summary.rst:418 +#: ../../source/drivers/vector/driver_summary.rst:428 +#: ../../source/drivers/vector/driver_summary.rst:433 +#: ../../source/drivers/vector/driver_summary.rst:434 +#: ../../source/drivers/vector/driver_summary.rst:439 +#: ../../source/drivers/vector/driver_summary.rst:443 +#: ../../source/drivers/vector/eeda.rst:105 +#: ../../source/drivers/vector/eeda.rst:109 +#: ../../source/drivers/vector/eeda.rst:112 +#: ../../source/drivers/vector/eeda.rst:114 +#: ../../source/drivers/vector/eeda.rst:127 +#: ../../source/drivers/vector/eeda.rst:129 +#: ../../source/drivers/vector/eeda.rst:131 +#: ../../source/drivers/vector/eeda.rst:133 +#: ../../source/drivers/vector/eeda.rst:135 +#: ../../source/drivers/vector/eeda.rst:137 +#: ../../source/drivers/vector/eeda.rst:139 +#: ../../source/drivers/vector/eeda.rst:141 +#: ../../source/drivers/vector/eeda.rst:143 +#: ../../source/drivers/vector/eeda.rst:145 +#: ../../source/drivers/vector/gpkg.rst:674 +#: ../../source/drivers/vector/gpkg.rst:677 +msgid "No" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:20 +#: ../../source/drivers/raster/driver_summary.rst:21 +#: ../../source/drivers/raster/driver_summary.rst:27 +#: ../../source/drivers/raster/driver_summary.rst:31 +#: ../../source/drivers/raster/driver_summary.rst:32 +#: ../../source/drivers/raster/driver_summary.rst:33 +#: ../../source/drivers/raster/driver_summary.rst:39 +#: ../../source/drivers/raster/driver_summary.rst:49 +#: ../../source/drivers/raster/driver_summary.rst:50 +#: ../../source/drivers/raster/driver_summary.rst:51 +#: ../../source/drivers/raster/driver_summary.rst:56 +#: ../../source/drivers/raster/driver_summary.rst:62 +#: ../../source/drivers/raster/driver_summary.rst:63 +#: ../../source/drivers/raster/driver_summary.rst:67 +#: ../../source/drivers/raster/driver_summary.rst:68 +#: ../../source/drivers/raster/driver_summary.rst:69 +#: ../../source/drivers/raster/driver_summary.rst:75 +#: ../../source/drivers/raster/driver_summary.rst:79 +#: ../../source/drivers/raster/driver_summary.rst:80 +#: ../../source/drivers/raster/driver_summary.rst:81 +#: ../../source/drivers/raster/driver_summary.rst:85 +#: ../../source/drivers/raster/driver_summary.rst:86 +#: ../../source/drivers/raster/driver_summary.rst:87 +#: ../../source/drivers/raster/driver_summary.rst:93 +#: ../../source/drivers/raster/driver_summary.rst:98 +#: ../../source/drivers/raster/driver_summary.rst:116 +#: ../../source/drivers/raster/driver_summary.rst:117 +#: ../../source/drivers/raster/driver_summary.rst:129 +#: ../../source/drivers/raster/driver_summary.rst:133 +#: ../../source/drivers/raster/driver_summary.rst:134 +#: ../../source/drivers/raster/driver_summary.rst:135 +#: ../../source/drivers/raster/driver_summary.rst:141 +#: ../../source/drivers/raster/driver_summary.rst:147 +#: ../../source/drivers/raster/driver_summary.rst:152 +#: ../../source/drivers/raster/driver_summary.rst:165 +#: ../../source/drivers/raster/driver_summary.rst:171 +#: ../../source/drivers/raster/driver_summary.rst:177 +#: ../../source/drivers/raster/driver_summary.rst:183 +#: ../../source/drivers/raster/driver_summary.rst:188 +#: ../../source/drivers/raster/driver_summary.rst:189 +#: ../../source/drivers/raster/driver_summary.rst:195 +#: ../../source/drivers/raster/driver_summary.rst:199 +#: ../../source/drivers/raster/driver_summary.rst:200 +#: ../../source/drivers/raster/driver_summary.rst:201 +#: ../../source/drivers/raster/driver_summary.rst:207 +#: ../../source/drivers/raster/driver_summary.rst:211 +#: ../../source/drivers/raster/driver_summary.rst:212 +#: ../../source/drivers/raster/driver_summary.rst:213 +#: ../../source/drivers/raster/driver_summary.rst:219 +#: ../../source/drivers/raster/driver_summary.rst:223 +#: ../../source/drivers/raster/driver_summary.rst:224 +#: ../../source/drivers/raster/driver_summary.rst:225 +#: ../../source/drivers/raster/driver_summary.rst:229 +#: ../../source/drivers/raster/driver_summary.rst:230 +#: ../../source/drivers/raster/driver_summary.rst:231 +#: ../../source/drivers/raster/driver_summary.rst:235 +#: ../../source/drivers/raster/driver_summary.rst:236 +#: ../../source/drivers/raster/driver_summary.rst:237 +#: ../../source/drivers/raster/driver_summary.rst:249 +#: ../../source/drivers/raster/driver_summary.rst:253 +#: ../../source/drivers/raster/driver_summary.rst:254 +#: ../../source/drivers/raster/driver_summary.rst:255 +#: ../../source/drivers/raster/driver_summary.rst:261 +#: ../../source/drivers/raster/driver_summary.rst:266 +#: ../../source/drivers/raster/driver_summary.rst:267 +#: ../../source/drivers/raster/driver_summary.rst:271 +#: ../../source/drivers/raster/driver_summary.rst:272 +#: ../../source/drivers/raster/driver_summary.rst:273 +#: ../../source/drivers/raster/driver_summary.rst:283 +#: ../../source/drivers/raster/driver_summary.rst:284 +#: ../../source/drivers/raster/driver_summary.rst:285 +#: ../../source/drivers/raster/driver_summary.rst:296 +#: ../../source/drivers/raster/driver_summary.rst:301 +#: ../../source/drivers/raster/driver_summary.rst:302 +#: ../../source/drivers/raster/driver_summary.rst:303 +#: ../../source/drivers/raster/driver_summary.rst:315 +#: ../../source/drivers/raster/driver_summary.rst:320 +#: ../../source/drivers/raster/driver_summary.rst:321 +#: ../../source/drivers/raster/driver_summary.rst:325 +#: ../../source/drivers/raster/driver_summary.rst:326 +#: ../../source/drivers/raster/driver_summary.rst:327 +#: ../../source/drivers/raster/driver_summary.rst:332 +#: ../../source/drivers/raster/driver_summary.rst:333 +#: ../../source/drivers/raster/driver_summary.rst:337 +#: ../../source/drivers/raster/driver_summary.rst:338 +#: ../../source/drivers/raster/driver_summary.rst:339 +#: ../../source/drivers/raster/driver_summary.rst:350 +#: ../../source/drivers/raster/driver_summary.rst:351 +#: ../../source/drivers/raster/driver_summary.rst:361 +#: ../../source/drivers/raster/driver_summary.rst:362 +#: ../../source/drivers/raster/driver_summary.rst:363 +#: ../../source/drivers/raster/driver_summary.rst:369 +#: ../../source/drivers/raster/driver_summary.rst:373 +#: ../../source/drivers/raster/driver_summary.rst:374 +#: ../../source/drivers/raster/driver_summary.rst:375 +#: ../../source/drivers/raster/driver_summary.rst:381 +#: ../../source/drivers/raster/driver_summary.rst:392 +#: ../../source/drivers/raster/driver_summary.rst:393 +#: ../../source/drivers/raster/driver_summary.rst:397 +#: ../../source/drivers/raster/driver_summary.rst:398 +#: ../../source/drivers/raster/driver_summary.rst:399 +#: ../../source/drivers/raster/driver_summary.rst:403 +#: ../../source/drivers/raster/driver_summary.rst:404 +#: ../../source/drivers/raster/driver_summary.rst:405 +#: ../../source/drivers/raster/driver_summary.rst:409 +#: ../../source/drivers/raster/driver_summary.rst:410 +#: ../../source/drivers/raster/driver_summary.rst:411 +#: ../../source/drivers/raster/driver_summary.rst:417 +#: ../../source/drivers/raster/driver_summary.rst:421 +#: ../../source/drivers/raster/driver_summary.rst:422 +#: ../../source/drivers/raster/driver_summary.rst:423 +#: ../../source/drivers/raster/driver_summary.rst:429 +#: ../../source/drivers/raster/driver_summary.rst:433 +#: ../../source/drivers/raster/driver_summary.rst:434 +#: ../../source/drivers/raster/driver_summary.rst:435 +#: ../../source/drivers/raster/driver_summary.rst:439 +#: ../../source/drivers/raster/driver_summary.rst:440 +#: ../../source/drivers/raster/driver_summary.rst:441 +#: ../../source/drivers/raster/driver_summary.rst:447 +#: ../../source/drivers/raster/driver_summary.rst:451 +#: ../../source/drivers/raster/driver_summary.rst:452 +#: ../../source/drivers/raster/driver_summary.rst:453 +#: ../../source/drivers/raster/driver_summary.rst:458 +#: ../../source/drivers/raster/driver_summary.rst:459 +#: ../../source/drivers/raster/driver_summary.rst:464 +#: ../../source/drivers/raster/driver_summary.rst:465 +#: ../../source/drivers/raster/driver_summary.rst:470 +#: ../../source/drivers/raster/driver_summary.rst:471 +#: ../../source/drivers/raster/driver_summary.rst:476 +#: ../../source/drivers/raster/driver_summary.rst:477 +#: ../../source/drivers/raster/driver_summary.rst:482 +#: ../../source/drivers/raster/driver_summary.rst:483 +#: ../../source/drivers/raster/driver_summary.rst:488 +#: ../../source/drivers/raster/driver_summary.rst:489 +#: ../../source/drivers/raster/driver_summary.rst:495 +#: ../../source/drivers/raster/driver_summary.rst:499 +#: ../../source/drivers/raster/driver_summary.rst:500 +#: ../../source/drivers/raster/driver_summary.rst:501 +#: ../../source/drivers/raster/driver_summary.rst:506 +#: ../../source/drivers/raster/driver_summary.rst:507 +#: ../../source/drivers/raster/driver_summary.rst:511 +#: ../../source/drivers/raster/driver_summary.rst:512 +#: ../../source/drivers/raster/driver_summary.rst:518 +#: ../../source/drivers/raster/driver_summary.rst:525 +#: ../../source/drivers/raster/driver_summary.rst:529 +#: ../../source/drivers/raster/driver_summary.rst:531 +#: ../../source/drivers/raster/driver_summary.rst:536 +#: ../../source/drivers/raster/driver_summary.rst:537 +#: ../../source/drivers/raster/driver_summary.rst:541 +#: ../../source/drivers/raster/driver_summary.rst:542 +#: ../../source/drivers/raster/driver_summary.rst:543 +#: ../../source/drivers/raster/driver_summary.rst:549 +#: ../../source/drivers/raster/driver_summary.rst:555 +#: ../../source/drivers/raster/driver_summary.rst:559 +#: ../../source/drivers/raster/driver_summary.rst:560 +#: ../../source/drivers/raster/driver_summary.rst:561 +#: ../../source/drivers/raster/driver_summary.rst:565 +#: ../../source/drivers/raster/driver_summary.rst:566 +#: ../../source/drivers/raster/driver_summary.rst:567 +#: ../../source/drivers/raster/driver_summary.rst:571 +#: ../../source/drivers/raster/driver_summary.rst:572 +#: ../../source/drivers/raster/driver_summary.rst:573 +#: ../../source/drivers/raster/driver_summary.rst:577 +#: ../../source/drivers/raster/driver_summary.rst:578 +#: ../../source/drivers/raster/driver_summary.rst:579 +#: ../../source/drivers/raster/driver_summary.rst:583 +#: ../../source/drivers/raster/driver_summary.rst:584 +#: ../../source/drivers/raster/driver_summary.rst:585 +#: ../../source/drivers/raster/driver_summary.rst:591 +#: ../../source/drivers/raster/driver_summary.rst:597 +#: ../../source/drivers/raster/driver_summary.rst:603 +#: ../../source/drivers/raster/driver_summary.rst:609 +#: ../../source/drivers/raster/driver_summary.rst:613 +#: ../../source/drivers/raster/driver_summary.rst:614 +#: ../../source/drivers/raster/driver_summary.rst:615 +#: ../../source/drivers/raster/driver_summary.rst:621 +#: ../../source/drivers/raster/driver_summary.rst:627 +#: ../../source/drivers/raster/driver_summary.rst:631 +#: ../../source/drivers/raster/driver_summary.rst:632 +#: ../../source/drivers/raster/driver_summary.rst:633 +#: ../../source/drivers/raster/driver_summary.rst:639 +#: ../../source/drivers/raster/driver_summary.rst:645 +#: ../../source/drivers/raster/driver_summary.rst:649 +#: ../../source/drivers/raster/driver_summary.rst:650 +#: ../../source/drivers/raster/driver_summary.rst:651 +#: ../../source/drivers/raster/driver_summary.rst:655 +#: ../../source/drivers/raster/driver_summary.rst:656 +#: ../../source/drivers/raster/driver_summary.rst:657 +#: ../../source/drivers/raster/driver_summary.rst:661 +#: ../../source/drivers/raster/driver_summary.rst:662 +#: ../../source/drivers/raster/driver_summary.rst:663 +#: ../../source/drivers/raster/driver_summary.rst:669 +#: ../../source/drivers/raster/driver_summary.rst:675 +#: ../../source/drivers/raster/driver_summary.rst:681 +#: ../../source/drivers/raster/driver_summary.rst:687 +#: ../../source/drivers/raster/driver_summary.rst:691 +#: ../../source/drivers/raster/driver_summary.rst:692 +#: ../../source/drivers/raster/driver_summary.rst:697 +#: ../../source/drivers/raster/driver_summary.rst:698 +#: ../../source/drivers/raster/driver_summary.rst:699 +#: ../../source/drivers/raster/driver_summary.rst:703 +#: ../../source/drivers/raster/driver_summary.rst:704 +#: ../../source/drivers/raster/driver_summary.rst:705 +#: ../../source/drivers/raster/driver_summary.rst:710 +#: ../../source/drivers/raster/driver_summary.rst:711 +#: ../../source/drivers/raster/driver_summary.rst:717 +#: ../../source/drivers/raster/driver_summary.rst:721 +#: ../../source/drivers/raster/driver_summary.rst:722 +#: ../../source/drivers/raster/driver_summary.rst:723 +#: ../../source/drivers/raster/driver_summary.rst:729 +#: ../../source/drivers/raster/driver_summary.rst:734 +#: ../../source/drivers/raster/driver_summary.rst:735 +#: ../../source/drivers/raster/driver_summary.rst:739 +#: ../../source/drivers/raster/driver_summary.rst:740 +#: ../../source/drivers/raster/driver_summary.rst:746 +#: ../../source/drivers/raster/driver_summary.rst:747 +#: ../../source/drivers/raster/driver_summary.rst:758 +#: ../../source/drivers/raster/driver_summary.rst:764 +#: ../../source/drivers/raster/driver_summary.rst:765 +#: ../../source/drivers/raster/driver_summary.rst:770 +#: ../../source/drivers/raster/driver_summary.rst:771 +#: ../../source/drivers/raster/driver_summary.rst:777 +#: ../../source/drivers/raster/driver_summary.rst:783 +#: ../../source/drivers/raster/driver_summary.rst:787 +#: ../../source/drivers/raster/driver_summary.rst:788 +#: ../../source/drivers/raster/driver_summary.rst:789 +#: ../../source/drivers/raster/driver_summary.rst:793 +#: ../../source/drivers/raster/driver_summary.rst:794 +#: ../../source/drivers/raster/driver_summary.rst:795 +#: ../../source/drivers/raster/driver_summary.rst:801 +#: ../../source/drivers/raster/driver_summary.rst:805 +#: ../../source/drivers/raster/driver_summary.rst:806 +#: ../../source/drivers/raster/driver_summary.rst:807 +#: ../../source/drivers/raster/driver_summary.rst:813 +#: ../../source/drivers/raster/driver_summary.rst:819 +#: ../../source/drivers/raster/driver_summary.rst:825 +#: ../../source/drivers/raster/driver_summary.rst:831 +#: ../../source/drivers/raster/driver_summary.rst:837 +#: ../../source/drivers/raster/driver_summary.rst:843 +#: ../../source/drivers/raster/driver_summary.rst:847 +#: ../../source/drivers/raster/driver_summary.rst:848 +#: ../../source/drivers/raster/driver_summary.rst:849 +#: ../../source/drivers/raster/driver_summary.rst:855 +#: ../../source/drivers/raster/driver_summary.rst:861 +#: ../../source/drivers/raster/driver_summary.rst:865 +#: ../../source/drivers/raster/driver_summary.rst:866 +#: ../../source/drivers/raster/driver_summary.rst:872 +#: ../../source/drivers/raster/driver_summary.rst:873 +#: ../../source/drivers/raster/driver_summary.rst:879 +#: ../../source/drivers/raster/driver_summary.rst:885 +#: ../../source/drivers/raster/driver_summary.rst:890 +#: ../../source/drivers/raster/driver_summary.rst:891 +#: ../../source/drivers/raster/driver_summary.rst:907 +#: ../../source/drivers/raster/driver_summary.rst:908 +#: ../../source/drivers/raster/driver_summary.rst:909 +#: ../../source/drivers/raster/driver_summary.rst:921 +#: ../../source/drivers/raster/driver_summary.rst:925 +#: ../../source/drivers/raster/driver_summary.rst:926 +#: ../../source/drivers/raster/driver_summary.rst:927 +#: ../../source/drivers/raster/driver_summary.rst:933 +#: ../../source/drivers/raster/driver_summary.rst:938 +#: ../../source/drivers/raster/driver_summary.rst:939 +#: ../../source/drivers/raster/driver_summary.rst:943 +#: ../../source/drivers/raster/driver_summary.rst:944 +#: ../../source/drivers/raster/driver_summary.rst:945 +#: ../../source/drivers/raster/driver_summary.rst:949 +#: ../../source/drivers/raster/driver_summary.rst:950 +#: ../../source/drivers/raster/driver_summary.rst:951 +#: ../../source/drivers/raster/driver_summary.rst:957 +#: ../../source/drivers/raster/driver_summary.rst:962 +#: ../../source/drivers/raster/driver_summary.rst:968 +#: ../../source/drivers/raster/driver_summary.rst:969 +#: ../../source/drivers/raster/driver_summary.rst:975 +#: ../../source/drivers/raster/driver_summary.rst:980 +#: ../../source/drivers/raster/driver_summary.rst:986 +#: ../../source/drivers/raster/driver_summary.rst:987 +#: ../../source/drivers/raster/driver_summary.rst:991 +#: ../../source/drivers/raster/driver_summary.rst:993 +#: ../../source/drivers/raster/driver_summary.rst:998 +#: ../../source/drivers/raster/driver_summary.rst:999 +#: ../../source/drivers/vector/driver_summary.rst:18 +#: ../../source/drivers/vector/driver_summary.rst:19 +#: ../../source/drivers/vector/driver_summary.rst:23 +#: ../../source/drivers/vector/driver_summary.rst:24 +#: ../../source/drivers/vector/driver_summary.rst:29 +#: ../../source/drivers/vector/driver_summary.rst:34 +#: ../../source/drivers/vector/driver_summary.rst:39 +#: ../../source/drivers/vector/driver_summary.rst:43 +#: ../../source/drivers/vector/driver_summary.rst:44 +#: ../../source/drivers/vector/driver_summary.rst:48 +#: ../../source/drivers/vector/driver_summary.rst:49 +#: ../../source/drivers/vector/driver_summary.rst:54 +#: ../../source/drivers/vector/driver_summary.rst:58 +#: ../../source/drivers/vector/driver_summary.rst:59 +#: ../../source/drivers/vector/driver_summary.rst:63 +#: ../../source/drivers/vector/driver_summary.rst:64 +#: ../../source/drivers/vector/driver_summary.rst:73 +#: ../../source/drivers/vector/driver_summary.rst:79 +#: ../../source/drivers/vector/driver_summary.rst:84 +#: ../../source/drivers/vector/driver_summary.rst:88 +#: ../../source/drivers/vector/driver_summary.rst:89 +#: ../../source/drivers/vector/driver_summary.rst:94 +#: ../../source/drivers/vector/driver_summary.rst:98 +#: ../../source/drivers/vector/driver_summary.rst:99 +#: ../../source/drivers/vector/driver_summary.rst:103 +#: ../../source/drivers/vector/driver_summary.rst:104 +#: ../../source/drivers/vector/driver_summary.rst:108 +#: ../../source/drivers/vector/driver_summary.rst:109 +#: ../../source/drivers/vector/driver_summary.rst:113 +#: ../../source/drivers/vector/driver_summary.rst:114 +#: ../../source/drivers/vector/driver_summary.rst:118 +#: ../../source/drivers/vector/driver_summary.rst:119 +#: ../../source/drivers/vector/driver_summary.rst:123 +#: ../../source/drivers/vector/driver_summary.rst:124 +#: ../../source/drivers/vector/driver_summary.rst:128 +#: ../../source/drivers/vector/driver_summary.rst:129 +#: ../../source/drivers/vector/driver_summary.rst:134 +#: ../../source/drivers/vector/driver_summary.rst:138 +#: ../../source/drivers/vector/driver_summary.rst:139 +#: ../../source/drivers/vector/driver_summary.rst:143 +#: ../../source/drivers/vector/driver_summary.rst:144 +#: ../../source/drivers/vector/driver_summary.rst:148 +#: ../../source/drivers/vector/driver_summary.rst:149 +#: ../../source/drivers/vector/driver_summary.rst:153 +#: ../../source/drivers/vector/driver_summary.rst:154 +#: ../../source/drivers/vector/driver_summary.rst:168 +#: ../../source/drivers/vector/driver_summary.rst:169 +#: ../../source/drivers/vector/driver_summary.rst:173 +#: ../../source/drivers/vector/driver_summary.rst:174 +#: ../../source/drivers/vector/driver_summary.rst:179 +#: ../../source/drivers/vector/driver_summary.rst:183 +#: ../../source/drivers/vector/driver_summary.rst:184 +#: ../../source/drivers/vector/driver_summary.rst:188 +#: ../../source/drivers/vector/driver_summary.rst:189 +#: ../../source/drivers/vector/driver_summary.rst:193 +#: ../../source/drivers/vector/driver_summary.rst:194 +#: ../../source/drivers/vector/driver_summary.rst:198 +#: ../../source/drivers/vector/driver_summary.rst:199 +#: ../../source/drivers/vector/driver_summary.rst:203 +#: ../../source/drivers/vector/driver_summary.rst:204 +#: ../../source/drivers/vector/driver_summary.rst:208 +#: ../../source/drivers/vector/driver_summary.rst:209 +#: ../../source/drivers/vector/driver_summary.rst:218 +#: ../../source/drivers/vector/driver_summary.rst:219 +#: ../../source/drivers/vector/driver_summary.rst:223 +#: ../../source/drivers/vector/driver_summary.rst:224 +#: ../../source/drivers/vector/driver_summary.rst:228 +#: ../../source/drivers/vector/driver_summary.rst:229 +#: ../../source/drivers/vector/driver_summary.rst:233 +#: ../../source/drivers/vector/driver_summary.rst:234 +#: ../../source/drivers/vector/driver_summary.rst:239 +#: ../../source/drivers/vector/driver_summary.rst:243 +#: ../../source/drivers/vector/driver_summary.rst:244 +#: ../../source/drivers/vector/driver_summary.rst:248 +#: ../../source/drivers/vector/driver_summary.rst:249 +#: ../../source/drivers/vector/driver_summary.rst:253 +#: ../../source/drivers/vector/driver_summary.rst:254 +#: ../../source/drivers/vector/driver_summary.rst:259 +#: ../../source/drivers/vector/driver_summary.rst:263 +#: ../../source/drivers/vector/driver_summary.rst:264 +#: ../../source/drivers/vector/driver_summary.rst:269 +#: ../../source/drivers/vector/driver_summary.rst:274 +#: ../../source/drivers/vector/driver_summary.rst:279 +#: ../../source/drivers/vector/driver_summary.rst:283 +#: ../../source/drivers/vector/driver_summary.rst:284 +#: ../../source/drivers/vector/driver_summary.rst:289 +#: ../../source/drivers/vector/driver_summary.rst:293 +#: ../../source/drivers/vector/driver_summary.rst:299 +#: ../../source/drivers/vector/driver_summary.rst:303 +#: ../../source/drivers/vector/driver_summary.rst:304 +#: ../../source/drivers/vector/driver_summary.rst:309 +#: ../../source/drivers/vector/driver_summary.rst:313 +#: ../../source/drivers/vector/driver_summary.rst:314 +#: ../../source/drivers/vector/driver_summary.rst:318 +#: ../../source/drivers/vector/driver_summary.rst:319 +#: ../../source/drivers/vector/driver_summary.rst:328 +#: ../../source/drivers/vector/driver_summary.rst:329 +#: ../../source/drivers/vector/driver_summary.rst:333 +#: ../../source/drivers/vector/driver_summary.rst:334 +#: ../../source/drivers/vector/driver_summary.rst:339 +#: ../../source/drivers/vector/driver_summary.rst:348 +#: ../../source/drivers/vector/driver_summary.rst:349 +#: ../../source/drivers/vector/driver_summary.rst:353 +#: ../../source/drivers/vector/driver_summary.rst:354 +#: ../../source/drivers/vector/driver_summary.rst:359 +#: ../../source/drivers/vector/driver_summary.rst:363 +#: ../../source/drivers/vector/driver_summary.rst:364 +#: ../../source/drivers/vector/driver_summary.rst:368 +#: ../../source/drivers/vector/driver_summary.rst:369 +#: ../../source/drivers/vector/driver_summary.rst:378 +#: ../../source/drivers/vector/driver_summary.rst:379 +#: ../../source/drivers/vector/driver_summary.rst:384 +#: ../../source/drivers/vector/driver_summary.rst:389 +#: ../../source/drivers/vector/driver_summary.rst:394 +#: ../../source/drivers/vector/driver_summary.rst:398 +#: ../../source/drivers/vector/driver_summary.rst:404 +#: ../../source/drivers/vector/driver_summary.rst:408 +#: ../../source/drivers/vector/driver_summary.rst:409 +#: ../../source/drivers/vector/driver_summary.rst:414 +#: ../../source/drivers/vector/driver_summary.rst:419 +#: ../../source/drivers/vector/driver_summary.rst:423 +#: ../../source/drivers/vector/driver_summary.rst:424 +#: ../../source/drivers/vector/driver_summary.rst:429 +#: ../../source/drivers/vector/driver_summary.rst:438 +#: ../../source/drivers/vector/driver_summary.rst:444 +msgid "**Yes**" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:22 +#: ../../source/drivers/raster/driver_summary.rst:28 +#: ../../source/drivers/raster/driver_summary.rst:34 +#: ../../source/drivers/raster/driver_summary.rst:40 +#: ../../source/drivers/raster/driver_summary.rst:46 +#: ../../source/drivers/raster/driver_summary.rst:64 +#: ../../source/drivers/raster/driver_summary.rst:70 +#: ../../source/drivers/raster/driver_summary.rst:76 +#: ../../source/drivers/raster/driver_summary.rst:82 +#: ../../source/drivers/raster/driver_summary.rst:88 +#: ../../source/drivers/raster/driver_summary.rst:100 +#: ../../source/drivers/raster/driver_summary.rst:106 +#: ../../source/drivers/raster/driver_summary.rst:112 +#: ../../source/drivers/raster/driver_summary.rst:118 +#: ../../source/drivers/raster/driver_summary.rst:124 +#: ../../source/drivers/raster/driver_summary.rst:130 +#: ../../source/drivers/raster/driver_summary.rst:136 +#: ../../source/drivers/raster/driver_summary.rst:142 +#: ../../source/drivers/raster/driver_summary.rst:160 +#: ../../source/drivers/raster/driver_summary.rst:166 +#: ../../source/drivers/raster/driver_summary.rst:172 +#: ../../source/drivers/raster/driver_summary.rst:178 +#: ../../source/drivers/raster/driver_summary.rst:184 +#: ../../source/drivers/raster/driver_summary.rst:190 +#: ../../source/drivers/raster/driver_summary.rst:196 +#: ../../source/drivers/raster/driver_summary.rst:214 +#: ../../source/drivers/raster/driver_summary.rst:220 +#: ../../source/drivers/raster/driver_summary.rst:226 +#: ../../source/drivers/raster/driver_summary.rst:232 +#: ../../source/drivers/raster/driver_summary.rst:238 +#: ../../source/drivers/raster/driver_summary.rst:244 +#: ../../source/drivers/raster/driver_summary.rst:250 +#: ../../source/drivers/raster/driver_summary.rst:262 +#: ../../source/drivers/raster/driver_summary.rst:268 +#: ../../source/drivers/raster/driver_summary.rst:280 +#: ../../source/drivers/raster/driver_summary.rst:292 +#: ../../source/drivers/raster/driver_summary.rst:316 +#: ../../source/drivers/raster/driver_summary.rst:322 +#: ../../source/drivers/raster/driver_summary.rst:328 +#: ../../source/drivers/raster/driver_summary.rst:334 +#: ../../source/drivers/raster/driver_summary.rst:340 +#: ../../source/drivers/raster/driver_summary.rst:346 +#: ../../source/drivers/raster/driver_summary.rst:358 +#: ../../source/drivers/raster/driver_summary.rst:364 +#: ../../source/drivers/raster/driver_summary.rst:370 +#: ../../source/drivers/raster/driver_summary.rst:394 +#: ../../source/drivers/raster/driver_summary.rst:400 +#: ../../source/drivers/raster/driver_summary.rst:406 +#: ../../source/drivers/raster/driver_summary.rst:412 +#: ../../source/drivers/raster/driver_summary.rst:418 +#: ../../source/drivers/raster/driver_summary.rst:424 +#: ../../source/drivers/raster/driver_summary.rst:430 +#: ../../source/drivers/raster/driver_summary.rst:436 +#: ../../source/drivers/raster/driver_summary.rst:442 +#: ../../source/drivers/raster/driver_summary.rst:448 +#: ../../source/drivers/raster/driver_summary.rst:508 +#: ../../source/drivers/raster/driver_summary.rst:514 +#: ../../source/drivers/raster/driver_summary.rst:526 +#: ../../source/drivers/raster/driver_summary.rst:532 +#: ../../source/drivers/raster/driver_summary.rst:538 +#: ../../source/drivers/raster/driver_summary.rst:544 +#: ../../source/drivers/raster/driver_summary.rst:550 +#: ../../source/drivers/raster/driver_summary.rst:556 +#: ../../source/drivers/raster/driver_summary.rst:562 +#: ../../source/drivers/raster/driver_summary.rst:574 +#: ../../source/drivers/raster/driver_summary.rst:580 +#: ../../source/drivers/raster/driver_summary.rst:586 +#: ../../source/drivers/raster/driver_summary.rst:604 +#: ../../source/drivers/raster/driver_summary.rst:610 +#: ../../source/drivers/raster/driver_summary.rst:622 +#: ../../source/drivers/raster/driver_summary.rst:634 +#: ../../source/drivers/raster/driver_summary.rst:640 +#: ../../source/drivers/raster/driver_summary.rst:646 +#: ../../source/drivers/raster/driver_summary.rst:652 +#: ../../source/drivers/raster/driver_summary.rst:658 +#: ../../source/drivers/raster/driver_summary.rst:664 +#: ../../source/drivers/raster/driver_summary.rst:676 +#: ../../source/drivers/raster/driver_summary.rst:682 +#: ../../source/drivers/raster/driver_summary.rst:688 +#: ../../source/drivers/raster/driver_summary.rst:694 +#: ../../source/drivers/raster/driver_summary.rst:700 +#: ../../source/drivers/raster/driver_summary.rst:718 +#: ../../source/drivers/raster/driver_summary.rst:724 +#: ../../source/drivers/raster/driver_summary.rst:736 +#: ../../source/drivers/raster/driver_summary.rst:742 +#: ../../source/drivers/raster/driver_summary.rst:754 +#: ../../source/drivers/raster/driver_summary.rst:760 +#: ../../source/drivers/raster/driver_summary.rst:790 +#: ../../source/drivers/raster/driver_summary.rst:796 +#: ../../source/drivers/raster/driver_summary.rst:802 +#: ../../source/drivers/raster/driver_summary.rst:808 +#: ../../source/drivers/raster/driver_summary.rst:814 +#: ../../source/drivers/raster/driver_summary.rst:838 +#: ../../source/drivers/raster/driver_summary.rst:844 +#: ../../source/drivers/raster/driver_summary.rst:850 +#: ../../source/drivers/raster/driver_summary.rst:856 +#: ../../source/drivers/raster/driver_summary.rst:862 +#: ../../source/drivers/raster/driver_summary.rst:868 +#: ../../source/drivers/raster/driver_summary.rst:874 +#: ../../source/drivers/raster/driver_summary.rst:880 +#: ../../source/drivers/raster/driver_summary.rst:886 +#: ../../source/drivers/raster/driver_summary.rst:892 +#: ../../source/drivers/raster/driver_summary.rst:898 +#: ../../source/drivers/raster/driver_summary.rst:904 +#: ../../source/drivers/raster/driver_summary.rst:910 +#: ../../source/drivers/raster/driver_summary.rst:916 +#: ../../source/drivers/raster/driver_summary.rst:922 +#: ../../source/drivers/raster/driver_summary.rst:934 +#: ../../source/drivers/raster/driver_summary.rst:940 +#: ../../source/drivers/raster/driver_summary.rst:946 +#: ../../source/drivers/raster/driver_summary.rst:952 +#: ../../source/drivers/raster/driver_summary.rst:982 +#: ../../source/drivers/raster/driver_summary.rst:988 +#: ../../source/drivers/raster/driver_summary.rst:1000 +#: ../../source/drivers/vector/driver_summary.rst:30 +#: ../../source/drivers/vector/driver_summary.rst:35 +#: ../../source/drivers/vector/driver_summary.rst:50 +#: ../../source/drivers/vector/driver_summary.rst:60 +#: ../../source/drivers/vector/driver_summary.rst:75 +#: ../../source/drivers/vector/driver_summary.rst:80 +#: ../../source/drivers/vector/driver_summary.rst:95 +#: ../../source/drivers/vector/driver_summary.rst:105 +#: ../../source/drivers/vector/driver_summary.rst:110 +#: ../../source/drivers/vector/driver_summary.rst:115 +#: ../../source/drivers/vector/driver_summary.rst:120 +#: ../../source/drivers/vector/driver_summary.rst:140 +#: ../../source/drivers/vector/driver_summary.rst:165 +#: ../../source/drivers/vector/driver_summary.rst:180 +#: ../../source/drivers/vector/driver_summary.rst:200 +#: ../../source/drivers/vector/driver_summary.rst:220 +#: ../../source/drivers/vector/driver_summary.rst:225 +#: ../../source/drivers/vector/driver_summary.rst:230 +#: ../../source/drivers/vector/driver_summary.rst:235 +#: ../../source/drivers/vector/driver_summary.rst:275 +#: ../../source/drivers/vector/driver_summary.rst:305 +#: ../../source/drivers/vector/driver_summary.rst:325 +#: ../../source/drivers/vector/driver_summary.rst:335 +#: ../../source/drivers/vector/driver_summary.rst:350 +#: ../../source/drivers/vector/driver_summary.rst:355 +#: ../../source/drivers/vector/driver_summary.rst:360 +#: ../../source/drivers/vector/driver_summary.rst:365 +#: ../../source/drivers/vector/driver_summary.rst:370 +#: ../../source/drivers/vector/driver_summary.rst:390 +#: ../../source/drivers/vector/driver_summary.rst:395 +#: ../../source/drivers/vector/driver_summary.rst:405 +#: ../../source/drivers/vector/driver_summary.rst:410 +#: ../../source/drivers/vector/driver_summary.rst:420 +#: ../../source/drivers/vector/driver_summary.rst:425 +msgid "Built-in by default" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:23 +msgid ":ref:`ACE2 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:29 +msgid ":ref:`ADRG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:30 +msgid "ADRG/ARC Digitized Raster Graphics (.gen/.thf)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:35 +msgid ":ref:`AIG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:36 +msgid "Arc/Info Binary Grid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:41 +msgid ":ref:`AIRSAR `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:42 +msgid "AIRSAR Polarimetric Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:47 +msgid ":ref:`BAG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:48 +msgid "Bathymetry Attributed Grid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:53 +msgid ":ref:`BASISU `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:59 +msgid ":ref:`BLX `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:60 +msgid "Magellan BLX Topo File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:65 +msgid ":ref:`BMP `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:66 +msgid "Microsoft Windows Device Independent Bitmap" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:71 +msgid ":ref:`BSB `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:72 +msgid "Maptech/NOAA BSB Nautical Chart Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:77 +msgid ":ref:`BT `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:78 +msgid "VTP .bt Binary Terrain Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:83 +msgid ":ref:`BYN `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:84 +msgid "Natural Resources Canada's Geoid file format (.byn)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:89 +msgid ":ref:`CAD `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:90 +msgid "AutoCAD DWG raster layer" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:95 +msgid ":ref:`CALS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:96 +msgid "CALS Type 1" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:101 +msgid ":ref:`CEOS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:102 +msgid "CEOS Image" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:107 +msgid ":ref:`COASP `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:108 +msgid "DRDC COASP SAR Processor Raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:113 +msgid ":ref:`COG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:114 +msgid "Cloud Optimized GeoTIFF generator" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:119 +msgid ":ref:`COSAR `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:120 +msgid "TerraSAR-X Complex SAR Data Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:125 +msgid ":ref:`CPG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:126 +msgid "Convair PolGASP data" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:131 +msgid ":ref:`CTable2 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:132 +msgid "CTable2 Datum Grid Shift" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:137 +msgid ":ref:`CTG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:138 +msgid "USGS LULC Composite Theme Grid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:143 +msgid ":ref:`DAAS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:149 +msgid ":ref:`DDS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:150 +msgid "DirectDraw Surface" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:155 +msgid ":ref:`DERIVED `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:156 +msgid "Derived subdatasets driver" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:161 +msgid ":ref:`DIMAP `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:162 +msgid "Spot DIMAP" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:167 +msgid ":ref:`DIPEx `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:168 +msgid "ELAS DIPEx" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:173 +msgid ":ref:`DOQ1 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:174 +msgid "First Generation USGS DOQ" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:179 +msgid ":ref:`DOQ2 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:180 +msgid "New Labelled USGS DOQ" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:185 +msgid ":ref:`DTED `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:186 +msgid "Military Elevation Data" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:191 +msgid ":ref:`ECRGTOC `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:192 +msgid "ECRG Table Of Contents (TOC.xml)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:197 +msgid ":ref:`ECW `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:198 +msgid "Enhanced Compressed Wavelets (.ecw)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:202 +#: ../../source/drivers/raster/driver_summary.rst:454 +#: ../../source/drivers/raster/ecw.rst:9 +#: ../../source/drivers/raster/jp2ecw.rst:9 +msgid "ECW SDK" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:203 +msgid ":ref:`EEDAI `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:204 +msgid "Google Earth Engine Data API Image" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:209 +msgid ":ref:`EHdr `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:210 +msgid "ESRI .hdr Labelled" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:215 +msgid ":ref:`EIR `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:216 +msgid "Erdas Imagine Raw" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:221 +msgid ":ref:`ELAS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:222 +msgid "Earth Resources Laboratory Applications Software" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:227 +msgid ":ref:`ENVI `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:228 +msgid "ENVI .hdr Labelled Raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:233 +msgid ":ref:`ERS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:234 +msgid "ERMapper .ERS" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:239 +msgid ":ref:`ESAT `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:240 +msgid "Envisat Image Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:245 +msgid ":ref:`ESRIC `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:246 +msgid "Esri Compact Cache" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:251 +msgid ":ref:`EXR `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:252 +msgid "Extended Dynamic Range Image File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:256 +#: ../../source/drivers/raster/exr.rst:11 +msgid "libopenexr" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:257 +msgid ":ref:`FAST `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:258 +msgid "EOSAT FAST Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:263 +msgid ":ref:`FIT `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:264 +#: ../../source/drivers/raster/fit.rst:7 +msgid "FIT" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:269 +msgid ":ref:`FITS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:270 +msgid "Flexible Image Transport System" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:274 +#: ../../source/drivers/raster/fits.rst:9 +msgid "libcfitsio" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:275 +msgid ":ref:`GenBin `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:276 +msgid "Generic Binary (.hdr labelled)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:281 +msgid ":ref:`GeoRaster `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:282 +#: ../../source/drivers/raster/georaster.rst:5 +msgid "Oracle Spatial GeoRaster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:286 +#: ../../source/drivers/raster/georaster.rst:9 +msgid "Oracle client libraries" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:287 +msgid ":ref:`GFF `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:288 +msgid "Sandia National Laboratories GSAT File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:293 +msgid ":ref:`GIF `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:294 +msgid "Graphics Interchange Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:298 +#: ../../source/drivers/raster/gif.rst:9 +msgid "(internal GIF library provided)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:299 +msgid ":ref:`GPKG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:300 +msgid "GeoPackage raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:304 +#: ../../source/drivers/raster/gpkg.rst:9 +msgid "libsqlite3 (and any or all of PNG, JPEG, WEBP drivers)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:305 +msgid ":ref:`GRASS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:306 +#: ../../source/drivers/raster/grass.rst:4 +msgid "GRASS Raster Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:310 +#: ../../source/drivers/raster/grass.rst:8 +#: ../../source/drivers/vector/driver_summary.rst:160 +#: ../../source/drivers/vector/grass.rst:8 +msgid "gdal-grass-driver" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:311 +msgid ":ref:`GRASSASCIIGrid `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:312 +msgid "GRASS ASCII Grid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:317 +msgid ":ref:`GRIB `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:318 +msgid "WMO General Regularly-distributed Information in Binary form" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:323 +msgid ":ref:`GS7BG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:324 +msgid "Golden Software Surfer 7 Binary Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:329 +msgid ":ref:`GSAG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:330 +msgid "Golden Software ASCII Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:335 +msgid ":ref:`GSBG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:336 +msgid "Golden Software Binary Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:341 +msgid ":ref:`GSC `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:342 +msgid "GSC Geogrid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:347 +msgid ":ref:`GTA `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:348 +msgid "Generic Tagged Arrays" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:352 +#: ../../source/drivers/raster/gta.rst:9 +msgid "libgta" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:353 +msgid ":ref:`GTI `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:354 +msgid "GDAL Raster Tile Index" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:359 +msgid ":ref:`GTiff `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:360 +msgid "GeoTIFF File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:365 +msgid ":ref:`GXF `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:366 +msgid "Grid eXchange File" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:371 +msgid ":ref:`HDF4 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:372 +msgid "Hierarchical Data Format Release 4 (HDF4)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:376 +#: ../../source/drivers/raster/hdf4.rst:11 +msgid "libdf" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:377 +msgid ":ref:`HDF5 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:378 +msgid "Hierarchical Data Format Release 5 (HDF5)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:383 +msgid ":ref:`HEIF `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:384 +msgid "ISO/IEC 23008-12:2017 High Efficiency Image File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:388 +#: ../../source/drivers/raster/heif.rst:11 +msgid "libheif (>= 1.1), built against libde265" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:389 +msgid ":ref:`HF2 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:390 +msgid "HF2/HFZ heightfield raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:395 +msgid ":ref:`HFA `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:396 +msgid "Erdas Imagine .img" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:401 +msgid ":ref:`RST `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:402 +msgid "Idrisi Raster Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:407 +msgid ":ref:`ILWIS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:408 +msgid "Raster Map" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:413 +msgid ":ref:`IRIS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:414 +msgid "Vaisala's weather radar software format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:419 +msgid ":ref:`ISCE `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:420 +#: ../../source/drivers/raster/isce.rst:7 +msgid "ISCE" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:425 +msgid ":ref:`ISG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:426 +msgid "International Service for the Geoid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:431 +msgid ":ref:`ISIS2 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:432 +msgid "USGS Astrogeology ISIS Cube (Version 2)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:437 +msgid ":ref:`ISIS3 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:438 +msgid "USGS Astrogeology ISIS Cube (Version 3)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:443 +msgid ":ref:`JDEM `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:444 +msgid "Japanese DEM (.mem)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:449 +msgid ":ref:`JP2ECW `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:450 +msgid "ERDAS JPEG2000 (.jp2)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:455 +msgid ":ref:`JP2KAK `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:456 +msgid "JPEG 2000 (based on Kakadu SDK)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:460 +#: ../../source/drivers/raster/jp2kak.rst:9 +msgid "Kakadu SDK" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:461 +msgid ":ref:`JP2LURA `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:462 +msgid "JPEG2000 driver based on Lurawave library" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:466 +#: ../../source/drivers/raster/jp2lura.rst:11 +msgid "Lurawave library" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:467 +msgid ":ref:`JP2MrSID `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:468 +msgid "JPEG2000 via MrSID SDK" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:472 +#: ../../source/drivers/raster/driver_summary.rst:592 +#: ../../source/drivers/raster/jp2mrsid.rst:9 +#: ../../source/drivers/raster/mrsid.rst:9 +msgid "MrSID SDK" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:473 +msgid ":ref:`JP2OpenJPEG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:474 +msgid "JPEG2000 driver based on OpenJPEG library" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:478 +#: ../../source/drivers/raster/jp2openjpeg.rst:9 +msgid "openjpeg >= 2.1" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:479 +msgid ":ref:`JPEG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:480 +msgid "JPEG JFIF File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:484 +#: ../../source/drivers/raster/jpeg.rst:9 +msgid "(internal libjpeg provided)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:485 +msgid ":ref:`JPEGXL `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:486 +msgid "JPEG-XL File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:490 +#: ../../source/drivers/raster/jpegxl.rst:11 +msgid "libjxl" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:491 +msgid ":ref:`JPIPKAK `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:492 +msgid "JPIP Streaming" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:496 +#: ../../source/drivers/raster/jpipkak.rst:9 +msgid "Kakadu library" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:497 +msgid ":ref:`KEA `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:498 +#: ../../source/drivers/raster/kea.rst:5 ../../source/drivers/raster/kea.rst:7 +msgid "KEA" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:502 +#: ../../source/drivers/raster/kea.rst:9 +msgid "libkea and libhdf5 libraries" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:503 +msgid ":ref:`KMLSuperoverlay `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:504 +#: ../../source/drivers/raster/kmlsuperoverlay.rst:7 +msgid "KMLSuperoverlay" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:509 +msgid ":ref:`KRO `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:510 +msgid "KOLOR Raw format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:515 +msgid ":ref:`KTX2 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:516 +#: ../../source/drivers/raster/ktx2.rst:5 +#: ../../source/drivers/raster/ktx2.rst:9 +msgid "KTX2" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:521 +msgid ":ref:`L1B `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:522 +msgid "NOAA Polar Orbiter Level 1b Data Set (AVHRR)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:527 +msgid ":ref:`LAN `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:528 +msgid "Erdas 7.x .LAN and .GIS" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:533 +msgid ":ref:`LCP `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:534 +msgid "FARSITE v.4 LCP Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:539 +msgid ":ref:`Leveller `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:540 +msgid "Daylon Leveller Heightfield" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:545 +msgid ":ref:`LOSLAS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:546 +msgid "NADCON .los/.las Datum Grid Shift" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:551 +msgid ":ref:`MAP `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:552 +msgid "OziExplorer .MAP" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:557 +msgid ":ref:`MRF `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:558 +msgid "Meta Raster Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:563 +msgid ":ref:`MBTiles `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:564 +#: ../../source/drivers/raster/mbtiles.rst:5 +#: ../../source/drivers/raster/mbtiles.rst:7 +msgid "MBTiles" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:568 +#: ../../source/drivers/raster/driver_summary.rst:766 +#: ../../source/drivers/raster/mbtiles.rst:9 +#: ../../source/drivers/raster/rasterlite.rst:9 +#: ../../source/drivers/vector/driver_summary.rst:145 +#: ../../source/drivers/vector/driver_summary.rst:415 +#: ../../source/drivers/vector/gpkg.rst:8 ../../source/drivers/vector/vfk.rst:8 +msgid "libsqlite3" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:569 +msgid ":ref:`MEM `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:570 +msgid "In Memory Raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:575 +msgid ":ref:`MFF `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:576 +msgid "Vexcel MFF Raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:581 +msgid ":ref:`MFF2 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:582 +msgid "Vexcel MFF2 Image" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:587 +msgid ":ref:`MrSID `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:588 +msgid "Multi-resolution Seamless Image Database" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:593 +msgid ":ref:`MSG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:594 +msgid "Meteosat Second Generation" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:598 +#: ../../source/drivers/raster/msg.rst:9 +msgid "msg library" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:599 +msgid ":ref:`MSGN `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:600 +msgid "Meteosat Second Generation (MSG) Native Archive Format (.nat)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:605 +msgid ":ref:`NDF `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:606 +msgid "NLAPS Data Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:611 +msgid ":ref:`netCDF `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:612 +#: ../../source/drivers/raster/netcdf.rst:5 +msgid "NetCDF: Network Common Data Form" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:616 +#: ../../source/drivers/raster/netcdf.rst:9 +#: ../../source/drivers/vector/driver_summary.rst:265 +#: ../../source/drivers/vector/netcdf.rst:10 +msgid "libnetcdf" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:617 +msgid ":ref:`NGSGEOID `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:618 +msgid "NOAA NGS Geoid Height Grids" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:623 +msgid ":ref:`NGW `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:624 +#: ../../source/drivers/vector/driver_summary.rst:267 +msgid "NextGIS Web" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:629 +msgid ":ref:`NITF `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:630 +msgid "National Imagery Transmission Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:635 +msgid ":ref:`NOAA_B `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:636 +msgid "NOAA GEOCON/NADCON5 .b format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:641 +msgid ":ref:`NSIDCbin `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:642 +msgid "National Snow and Ice Data Centre Sea Ice Concentrations" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:647 +msgid ":ref:`NTv2 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:648 +msgid "NTv2 Datum Grid Shift" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:653 +msgid ":ref:`NWT_GRD `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:654 +#: ../../source/drivers/raster/driver_summary.rst:660 +msgid "Northwood/Vertical Mapper File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:659 +msgid ":ref:`NWT_GRC `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:665 +msgid ":ref:`OGCAPI `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:666 +msgid "OGC API Tiles / Maps / Coverage" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:671 +msgid ":ref:`OpenFileGDB `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:672 +#: ../../source/drivers/raster/openfilegdb.rst:4 +msgid "ESRI File Geodatabase raster (OpenFileGDB)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:677 +msgid ":ref:`OZI `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:678 +msgid "OZF2/OZFX3 raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:683 +msgid ":ref:`JAXAPALSAR `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:684 +#: ../../source/drivers/raster/palsar.rst:5 +msgid "JAXA PALSAR Processed Products" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:689 +msgid ":ref:`PAux `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:690 +msgid "PCI .aux Labelled Raw Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:695 +msgid ":ref:`PCIDSK `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:696 +msgid "PCI Geomatics Database File" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:701 +msgid ":ref:`PCRaster `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:702 +msgid "PCRaster raster file format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:706 +#: ../../source/drivers/raster/pcraster.rst:9 +msgid "(internal libcf provided)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:707 +msgid ":ref:`PDF `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:708 +#: ../../source/drivers/vector/driver_summary.rst:317 +msgid "Geospatial PDF" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:712 +#: ../../source/drivers/raster/pdf.rst:9 +#: ../../source/drivers/vector/driver_summary.rst:320 +#: ../../source/drivers/vector/pdf.rst:9 +msgid "none for write support, Poppler/PoDoFo/PDFium for read support" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:713 +msgid ":ref:`PDS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:714 +msgid "Planetary Data System v3" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:719 +msgid ":ref:`PDS4 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:720 +msgid "NASA Planetary Data System (Version 4)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:725 +msgid ":ref:`PLMosaic `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:726 +#: ../../source/drivers/raster/plmosaic.rst:5 +msgid "PLMosaic (Planet Labs Mosaics API)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:731 +msgid ":ref:`PNG `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:732 +msgid "Portable Network Graphics" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:737 +msgid ":ref:`PNM `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:738 +msgid "Netpbm (.pgm, .ppm)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:743 +msgid ":ref:`PostGISRaster `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:744 +msgid "PostGIS Raster driver" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:748 +#: ../../source/drivers/raster/postgisraster.rst:9 +msgid "PostgreSQL library" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:749 +msgid ":ref:`PRF `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:750 +#: ../../source/drivers/raster/prf.rst:5 +msgid "PHOTOMOD Raster File" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:755 +msgid ":ref:`R `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:756 +msgid "R Object Data Store" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:761 +msgid ":ref:`Rasterlite `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:762 +#: ../../source/drivers/raster/driver_summary.rst:768 +msgid "Rasters in SQLite DB" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:767 +msgid ":ref:`SQLite `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:772 +#: ../../source/drivers/raster/rasterlite2.rst:14 +msgid "libsqlite3, librasterlite2, libspatialite" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:773 +msgid ":ref:`RDB `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:774 +msgid "*RIEGL* Database" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:778 +#: ../../source/drivers/raster/rdb.rst:11 +msgid "rdblib >= 2.2.0." +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:779 +msgid ":ref:`RIK `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:780 +msgid "Swedish Grid Maps" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:784 +#: ../../source/drivers/raster/rik.rst:9 +msgid "(internal zlib is used if necessary)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:785 +msgid ":ref:`RMF `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:786 +msgid "Raster Matrix Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:791 +msgid ":ref:`ROI_PAC `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:792 +#: ../../source/drivers/raster/roi_pac.rst:7 +msgid "ROI_PAC" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:797 +msgid ":ref:`RPFTOC `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:798 +msgid "Raster Product Format/RPF (a.toc)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:803 +msgid ":ref:`RRASTER `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:804 +msgid "R Raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:809 +msgid ":ref:`RS2 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:810 +msgid "RadarSat 2 XML Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:815 +msgid ":ref:`S102 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:816 +msgid "S-102 Bathymetric Surface Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:821 +msgid ":ref:`S104 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:822 +msgid "S-104 Water Level Information for Surface Navigation Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:827 +msgid ":ref:`S111 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:828 +msgid "S-111 Surface Currents Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:833 +msgid ":ref:`SAFE `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:834 +msgid "Sentinel-1 SAFE XML Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:839 +msgid ":ref:`SAR_CEOS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:840 +msgid "CEOS SAR Image" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:845 +msgid ":ref:`SAGA `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:846 +msgid "SAGA GIS Binary Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:851 +msgid ":ref:`SDTS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:852 +msgid "USGS SDTS DEM" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:857 +msgid ":ref:`SENTINEL2 `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:858 +msgid "Sentinel-2 Products" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:863 +msgid ":ref:`SGI `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:864 +msgid "SGI Image Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:869 +msgid ":ref:`SIGDEM `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:870 +msgid "Scaled Integer Gridded DEM" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:875 +msgid ":ref:`SNODAS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:876 +msgid "Snow Data Assimilation System" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:881 +msgid ":ref:`SRP `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:882 +msgid "Standard Product Format (ASRP/USRP) (.gen)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:887 +msgid ":ref:`SRTMHGT `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:888 +msgid "SRTM HGT Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:893 +msgid ":ref:`STACIT `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:894 +msgid "Spatio-Temporal Asset Catalog Items" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:899 +msgid ":ref:`STACTA `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:900 +msgid "Spatio-Temporal Asset Catalog Tiled Assets" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:905 +msgid ":ref:`Terragen `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:906 +msgid "Terragen™ Terrain File" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:911 +msgid ":ref:`TGA `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:912 +msgid "TARGA Image File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:917 +msgid ":ref:`TIL `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:918 +msgid "EarthWatch/DigitalGlobe .TIL" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:923 +msgid ":ref:`TileDB `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:924 +msgid "TileDB raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:928 +#: ../../source/drivers/raster/tiledb.rst:11 +msgid "TileDB (>= 2.7 starting with GDAL 3.7)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:929 +msgid ":ref:`TSX `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:930 +msgid "TerraSAR-X Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:935 +msgid ":ref:`USGSDEM `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:936 +msgid "USGS ASCII DEM (and CDED)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:941 +msgid ":ref:`VICAR `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:942 +#: ../../source/drivers/raster/vicar.rst:7 +msgid "VICAR" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:947 +msgid ":ref:`VRT `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:948 +msgid "GDAL Virtual Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:953 +msgid ":ref:`WCS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:954 +msgid "OGC Web Coverage Service" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:959 +msgid ":ref:`WEBP `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:960 +#: ../../source/drivers/raster/gtiff.rst:1181 +#: ../../source/drivers/raster/webp.rst:7 +msgid "WEBP" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:964 +#: ../../source/drivers/raster/webp.rst:9 +msgid "libwebp" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:965 +msgid ":ref:`WMS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:966 +msgid "Web Map Services" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:971 +msgid ":ref:`WMTS `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:972 +msgid "OGC Web Map Tile Service" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:977 +msgid ":ref:`XPM `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:978 +msgid "X11 Pixmap" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:983 +msgid ":ref:`XYZ `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:984 +msgid "ASCII Gridded XYZ" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:989 +msgid ":ref:`Zarr `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:990 +#: ../../source/drivers/raster/zarr.rst:5 +#: ../../source/drivers/raster/zarr.rst:9 +msgid "Zarr" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:994 +msgid "Built-in by default, but liblz4, libxz (lzma), libzstd and libblosc" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:995 +msgid ":ref:`ZMAP `" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:996 +msgid "ZMap Plus Grid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:1002 +msgid "(1): Creation refers to implementing :cpp:func:`GDALCreate`." +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:1003 +msgid "(2): Copy refers to implementing :cpp:func:`GDALCreateCopy`." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:5 +msgid "DTED -- Military Elevation Data" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:7 +msgid "DTED" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:11 +msgid "" +"GDAL supports DTED Levels 0, 1, and 2 elevation data for read access. " +"Elevation data is returned as 16 bit signed integer. Appropriate " +"projection and georeferencing information is also returned. A variety of " +"header fields are returned dataset level metadata." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:28 +msgid "" +"|about-config-options| This paragraph lists the configuration options " +"that can be set to alter the default behavior of the DTED driver." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:65 +msgid "Read Issues" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:68 +msgid "Read speed" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:70 +msgid "" +"Elevation data in DTED files are organized per columns. This data " +"organization doesn't fit very well with some scanline oriented algorithms" +" and can cause slowdowns, especially for DTED Level 2 datasets. By " +"defining :config:`GDAL_DTED_SINGLE_BLOCK=TRUE`, a whole DTED dataset will" +" be considered as a single block. The first access to the file will be " +"slow, but further accesses will be much quicker. Only use that option if " +"you need to do processing on a whole file." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:79 +msgid "Georeferencing Issues" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:87 +msgid "" +"The DTED specification (`MIL-PRF-89020B `__) states " +"that *horizontal datum shall be the World Geodetic System (WGS 84)*. The " +"vertical datum is defined as EGM96, or EPSG:5773. However, there are " +"still people using old data files georeferenced in WGS 72. A header field" +" indicates the horizontal datum code, so we can detect and handle this " +"situation." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:89 +msgid "" +"If the horizontal datum specified in the DTED file is WGS84, the DTED " +"driver will report WGS 84 as SRS." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:91 +msgid "" +"If the horizontal datum specified in the DTED file is WGS72, the DTED " +"driver will report WGS 72 as SRS and issue a warning." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:93 +msgid "" +"If the horizontal datum specified in the DTED file is neither WGS84 nor " +"WGS72, the DTED driver will report WGS 84 as SRS and issue a warning." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:98 +msgid "Checksum Issues" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:100 +msgid "" +"The default behavior of the DTED driver is to ignore the checksum while " +"reading data from the files. However, you may specify the environment " +"variable ``DTED_VERIFY_CHECKSUM=YES`` if you want the checksums to be " +"verified. In some cases, the checksum written in the DTED file is wrong " +"(the data producer did a wrong job). This will be reported as a warning. " +"If the checksum written in the DTED file and the checksum computed from " +"the data do not match, an error will be issued." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:109 +#: ../../source/drivers/raster/gif.rst:33 +#: ../../source/drivers/raster/gtiff.rst:354 +#: ../../source/drivers/raster/hdf4.rst:193 +#: ../../source/drivers/raster/hfa.rst:41 +#: ../../source/drivers/raster/isis2.rst:40 +#: ../../source/drivers/raster/jp2kak.rst:137 +#: ../../source/drivers/raster/netcdf.rst:330 +#: ../../source/drivers/raster/nitf.rst:88 +#: ../../source/drivers/raster/pdf.rst:208 +#: ../../source/drivers/raster/usgsdem.rst:43 +#: ../../source/drivers/vector/csv.rst:417 +#: ../../source/drivers/vector/dgn.rst:98 +#: ../../source/drivers/vector/dgnv8.rst:100 +#: ../../source/drivers/vector/flatgeobuf.rst:94 +#: ../../source/drivers/vector/geoconcept.rst:52 +#: ../../source/drivers/vector/georss.rst:126 +#: ../../source/drivers/vector/gml.rst:638 +#: ../../source/drivers/vector/gmt.rst:31 +#: ../../source/drivers/vector/gpx.rst:192 +#: ../../source/drivers/vector/hana.rst:55 +#: ../../source/drivers/vector/jml.rst:68 +#: ../../source/drivers/vector/memory.rst:32 +#: ../../source/drivers/vector/miramon.rst:195 +#: ../../source/drivers/vector/mitab.rst:43 +#: ../../source/drivers/vector/mssqlspatial.rst:99 +#: ../../source/drivers/vector/mysql.rst:85 +#: ../../source/drivers/vector/oci.rst:109 +#: ../../source/drivers/vector/odbc.rst:100 +#: ../../source/drivers/vector/pg.rst:115 +#: ../../source/drivers/vector/shapefile.rst:146 +#: ../../source/drivers/vector/sqlite.rst:220 +#: ../../source/drivers/vector/vrt.rst:28 +msgid "Creation Issues" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:111 +msgid "" +"The DTED driver does support creating new files, but the input data must " +"be exactly formatted as a Level 0, 1 or 2 cell. That is the size, and " +"bounds must be appropriate for a cell." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:118 +msgid "Implemented as :source_file:`frmts/dted/dteddataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:5 +msgid "ECRGTOC -- ECRG Table Of Contents (TOC.xml)" +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:7 +msgid "ECRGTOC" +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:11 +msgid "" +"This is a read-only reader for ECRG (Enhanced Compressed Raster Graphic) " +"products, that uses the table of content file, TOC.xml, and exposes it as" +" a virtual dataset whose coverage is the set of ECRG frames contained in " +"the table of content." +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:16 +msgid "" +"The driver will report a different subdataset for each subdataset found " +"in the TOC.xml file. Each subdataset consists of the frames of same " +"product id, disk id, and with same scale." +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:20 +msgid "Result of a gdalinfo on a TOC.xml file." +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:39 +msgid ":ref:`raster.nitf`: format of the ECRG frames" +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:40 +#: ../../source/drivers/raster/nitf.rst:355 +msgid "" +"`MIL-PRF-32283 `__ : specification of ECRG" +" products" +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:43 +msgid "NOTE: Implemented as :source_file:`frmts/nitf/ecrgtocdataset.cpp`" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:5 +msgid "ECW -- Enhanced Compressed Wavelets (.ecw)" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:7 +msgid "ECW" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:11 +msgid "" +"GDAL supports reading and writing ECW files using the ERDAS ECW/JP2 SDK " +"developed by Hexagon Geospatial (formerly Intergraph, ERDAS, ERMapper). " +"Support is optional and requires linking in the libraries available from " +"the ECW/JP2 SDK Download page." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:28 +#: ../../source/drivers/raster/jp2ecw.rst:33 +msgid "Licensing" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:30 +#: ../../source/drivers/raster/jp2ecw.rst:35 +msgid "" +"The ERDAS ECW/JP2 SDK v5.x is available under multiple license types. For" +" Desktop usage, decoding any sized ECW/JP2 image is made available free " +"of charge. To compress, deploy on a Server platform, or decode unlimited " +"sized files on Mobile platforms a license must be purchased from Hexagon " +"Geospatial." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:37 +#: ../../source/drivers/raster/jp2ecw.rst:42 +msgid "History" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:39 +#: ../../source/drivers/raster/jp2ecw.rst:44 +msgid "v3.x - Last release, 2006" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:40 +#: ../../source/drivers/raster/jp2ecw.rst:45 +msgid "v4.x - Last release, 2012" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:41 +#: ../../source/drivers/raster/jp2ecw.rst:46 +msgid "v5.x - Active development, 2013 - current" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:46 +msgid "" +"The ERDAS ECW/JP2 v4.x and v5.x SDK is only free for image decompression." +" To compress images it is necessary to build with the read/write SDK and " +"to provide an OEM licensing key at runtime which may be purchased from " +"ERDAS." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:51 +msgid "" +"For those still using the ECW 3.3 SDK, images less than 500MB may be " +"compressed for free, while larger images require licensing from ERDAS. " +"See the licensing agreement and the LARGE_OK option." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:55 +msgid "" +"Files to be compressed into ECW format must also be at least 128x128. ECW" +" currently only supports 8 bits per channel for ECW Version 2 files. ECW " +"Version 3 files supports 16 bits per channel (as Uint16 data type). " +"Please see Creation options to enable ECW V3 files writing" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:60 +msgid "" +"When writing coordinate system information to ECW files, many less common" +" coordinate systems are not mapped properly. If you know the ECW name for" +" the coordinate system you can force it to be set at creation time with " +"the PROJ and DATUM creation options." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:65 +msgid "" +"ECW format does not support creation of overviews since the ECW format is" +" already considered to be optimized for \"arbitrary overviews\"." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:71 +#: ../../source/drivers/raster/envi.rst:28 +#: ../../source/drivers/raster/jp2ecw.rst:89 +#: ../../source/drivers/raster/paux.rst:20 +msgid "Creation Options:" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:131 +#: ../../source/drivers/raster/hfa.rst:142 +#: ../../source/drivers/raster/jp2ecw.rst:297 +#: ../../source/drivers/raster/jp2kak.rst:59 +#: ../../source/drivers/raster/jp2lura.rst:50 +#: ../../source/drivers/raster/netcdf.rst:584 +#: ../../source/drivers/vector/pg.rst:396 +msgid "Configuration Options" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:133 +msgid "" +"|about-config-options| The ERDAS ECW SDK supports a variety of " +"configuration options to control various features. See the ECW SDK " +"documentation for full details on the meaning of these options." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:203 +msgid "The GDAL-specific options:" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:218 +msgid "ECW Version 3 Files" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:220 +msgid "ECW 5.x SDK introduces a new file format version which," +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:222 +msgid "" +"Storage of data statistics, histograms, metadata, RPC information within " +"the file header" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:224 +msgid "Support for UInt16 data type" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:225 +msgid "Ability to update regions within an existing ECW v3 file" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:226 +msgid "Introduces other space saving optimizations" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:228 +msgid "" +"Note: This version is not backward compatible and will fail to decode in " +"v3.x or v4.x ECW/JP2 SDK's. The File VERSION Metadata will advertise " +"whether the file is ECW v2 or ECW v3." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:233 +msgid "ECWP" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:235 +msgid "" +"In addition to local files, this driver also supports access to streaming" +" network imagery services using the proprietary \"ECWP\" protocol from " +"the ERDAS APOLLO product. Use the full ecwp:// prefixed dataset url as " +"input. When built with ECW/JP2 SDK v4.1 or newer it is also possible to " +"take advantage of :ref:`rfc-24` for asynchronous / progressive streaming " +"access to ECWP services." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:243 +msgid "Metadata / Georeferencing" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:245 +msgid "" +"The PROJ, DATUM and UNITS found in the ECW header are reported in the ECW" +" metadata domain. They can also be set with the SetMetadataItem() method," +" in order to update the header information of an existing ECW file, " +"opened in update mode, without modifying the imagery." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:250 +msgid "" +"The geotransform and projection can also be modified with the " +"SetGeoTransform() and SetProjection() methods. If the projection is set " +"with SetProjection() and the PROJ, DATUM or UNITS with SetMetadataItem()," +" the later values will override the values built from the projection " +"string." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:256 +msgid "" +"All those can for example be modified with the -a_ullr, -a_srs or -mo " +"switches of the :ref:`gdal_edit` utility." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:259 +#: ../../source/drivers/raster/isis3.rst:51 +#: ../../source/drivers/raster/mem.rst:30 +#: ../../source/drivers/raster/vicar.rst:40 +#: ../../source/drivers/raster/vicar.rst:145 +#: ../../source/drivers/raster/vrt.rst:1957 +#: ../../source/drivers/raster/wld.rst:19 +#: ../../source/drivers/vector/gpkg.rst:584 +#: ../../source/drivers/vector/shapefile.rst:182 +msgid "For example:" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:268 +msgid "File Metadata Keys:" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:270 +msgid "FILE_METADATA_ACQUISITION_DATE" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:271 +msgid "FILE_METADATA_ACQUISITION_SENSOR_NAME" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:272 +msgid "FILE_METADATA_ADDRESS" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:273 +msgid "FILE_METADATA_AUTHOR" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:274 +msgid "FILE_METADATA_CLASSIFICATION" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:275 +msgid "FILE_METADATA_COMPANY - should be set to ECW_ENCODE_COMPANY" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:276 +msgid "FILE_METADATA_COMPRESSION_SOFTWARE - updated during recompression" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:277 +msgid "FILE_METADATA_COPYRIGHT" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:278 +msgid "FILE_METADATA_EMAIL" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:279 +msgid "FILE_METADATA_TELEPHONE" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:280 +msgid "CLOCKWISE_ROTATION_DEG" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:281 +msgid "COLORSPACE" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:282 +msgid "COMPRESSION_DATE" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:283 +msgid "COMPRESSION_RATE_ACTUAL" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:284 +msgid "" +"COMPRESSION_RATE_TARGET. This is the percentage of the target compressed " +"file size divided by the uncompressed file size. This is equal to 100 / " +"(100 - TARGET) where TARGET is the value of the TARGET creation option " +"used at file creation, so a COMPRESSION_RATE_TARGET=1 is equivalent to a " +"TARGET=0 (ie no compression), COMPRESSION_RATE_TARGET=5 is equivalent to " +"TARGET=80 (ie dividing uncompressed file size by 5), etc..." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:291 +msgid "VERSION" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:296 +#: ../../source/drivers/raster/jp2ecw.rst:374 +msgid "Implemented as :source_file:`frmts/ecw/ecwdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:297 +msgid "" +"ERDAS ECW/JP2 SDK Read-Only Redistributable available at " +"`www.hexagongeospatial.com `__" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:299 +msgid "" +"Further product information available in the `User Guide " +"`__" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:301 +msgid "" +"Support for non-GDAL specific issues should be directed to the `Hexagon " +"Geospatial public forum `__" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:304 +msgid "" +"Community contributed `patches " +"`__" +" to apply to ECW SDK 3.3 sources" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:305 +#: ../../source/drivers/raster/jp2ecw.rst:382 +msgid "`GDAL ECW Build Hints `__" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:5 +msgid "EEDAI - Google Earth Engine Data API Image" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:7 +msgid "EEDAI" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:13 +msgid "" +"The driver supports read-only operations to access image content, using " +"Google Earth Engine REST API." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:24 +#: ../../source/drivers/raster/plmosaic.rst:30 +#: ../../source/drivers/vector/plscenes_data_v1.rst:21 +msgid "The minimal syntax to open a datasource is :" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:30 +msgid "" +"where asset is something like projects/earthengine-" +"public/assets/COPERNICUS/S2/20170430T190351_20170430T190351_T10SEG, and " +"band_names a comma separated list of band names (typically indicated by " +"subdatasets on the main image)" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:64 +#: ../../source/drivers/vector/eeda.rst:44 +msgid "Authentication methods" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:66 +#: ../../source/drivers/vector/eeda.rst:46 +msgid "The following authentication methods can be used:" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:68 +msgid "" +"Authentication Bearer header passed through the :config:`EEDA_BEARER` or " +":config:`EEDA_BEARER_FILE` configuration options." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:70 +#: ../../source/drivers/vector/eeda.rst:50 +msgid "" +"Service account private key file, through the " +":config:`GOOGLE_APPLICATION_CREDENTIALS` configuration option." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:72 +#: ../../source/drivers/vector/eeda.rst:52 +msgid "" +"OAuth2 Service Account authentication through the " +":config:`EEDA_PRIVATE_KEY`/ :config:`EEDA_PRIVATE_KEY_FILE` + " +":config:`EEDA_CLIENT_EMAIL` configuration options." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:74 +msgid "" +"Finally if none of the above method succeeds, the code will check if the " +"current machine is a Google Compute Engine instance, and if so will use " +"the permissions associated to it (using the default service account " +"associated with the VM). To force a machine to be detected as a GCE " +"instance (for example for code running in a container with no access to " +"the boot logs), you can set :config:`CPL_MACHINE_IS_GCE=YES`." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:136 +#: ../../source/drivers/raster/gpkg.rst:623 +#: ../../source/drivers/raster/gtiff.rst:114 +#: ../../source/drivers/raster/rasterlite.rst:148 +#: ../../source/drivers/raster/vrt.rst:746 +msgid "Overviews" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:138 +msgid "" +"The driver expose overviews, following a logic of decreasing power of 2 " +"factors, until both dimensions of the smallest overview are lower than " +"256 pixels." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:143 +#: ../../source/drivers/raster/gtiff.rst:777 +#: ../../source/drivers/raster/l1b.rst:102 +#: ../../source/drivers/raster/stacit.rst:94 +#: ../../source/drivers/raster/stacta.rst:78 +msgid "Subdatasets" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:145 +msgid "" +"When all bands don't have the same georeferencing, resolution, CRS or " +"image dimensions, the driver will expose subdatasets. Each subdataset " +"groups together bands of the same dimension, extent, resolution and CRS." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:152 +msgid "" +"The driver will expose metadata reported in \"properties\" as dataset-" +"level or band-level metadata." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:156 +msgid "Pixel encoding" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:158 +msgid "" +"By default (:oo:`PIXEL_ENCODING=AUTO`), the driver will request pixels in" +" a format compatible of the number and data types of the bands. The PNG, " +"JPEG and AUTO_JPEG_PNG can only be used with bands of type Byte." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:165 +msgid "Get metadata on an image:" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:171 +#: ../../source/drivers/raster/fast.rst:72 +#: ../../source/drivers/raster/fast.rst:76 +#: ../../source/drivers/raster/fast.rst:80 +#: ../../source/drivers/raster/fast.rst:84 +#: ../../source/drivers/raster/gtiff.rst:898 +#: ../../source/drivers/raster/isis3.rst:144 +#: ../../source/drivers/raster/mem.rst:38 +#: ../../source/drivers/raster/plmosaic.rst:116 +#: ../../source/drivers/raster/plmosaic.rst:122 +#: ../../source/drivers/raster/vicar.rst:130 +#: ../../source/drivers/vector/amigocloud.rst:184 +#: ../../source/drivers/vector/eeda.rst:190 +#: ../../source/drivers/vector/hana.rst:281 +#: ../../source/drivers/vector/hana.rst:287 +#: ../../source/drivers/vector/plscenes_data_v1.rst:175 +#: ../../source/drivers/vector/plscenes_data_v1.rst:181 +#: ../../source/drivers/vector/plscenes_data_v1.rst:236 +#: ../../source/drivers/vector/wfs.rst:207 +msgid "or" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:180 +msgid ":ref:`Google Earth Engine Data API driver `" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:5 +msgid "EHdr -- ESRI .hdr Labelled" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:7 +msgid "EHdr" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:11 +msgid "" +"GDAL supports reading and writing the ESRI .hdr labeling format, often " +"referred to as ESRI BIL format. Eight, sixteen and thirty-two bit integer" +" raster data types are supported as well as 32 bit floating point. " +"Coordinate systems (from a .prj file), and georeferencing are supported. " +"Unrecognized options in the .hdr file are ignored. To open a dataset " +"select the file with the image file (often with the extension .bil). If " +"present .clr color table files are read, but not written. If present, " +"image.rep file will be read to extract the projection system of " +"SpatioCarte Defense 1.0 raster products." +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:21 +msgid "" +"This driver does not always do well differentiating between floating " +"point and integer data. The GDAL extension to the .hdr format to " +"differentiate is to add a field named PIXELTYPE with values of either " +"FLOAT, SIGNEDINT or UNSIGNEDINT. In combination with the NBITS field it " +"is possible to described all variations of pixel types." +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:27 +msgid "eg." +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:41 +msgid "This driver may be sufficient to read GTOPO30 data." +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:43 +msgid "NOTE: Implemented as :source_file:`frmts/raw/ehdrdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:59 +msgid "" +"`ESRI whitepaper: + Extendable Image Formats for ArcView GIS 3.1 and 3.2 " +"`__ " +"(BIL, see p. 5)" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:62 +msgid "" +"`GTOPO30 - Global Topographic Data " +"`__" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:64 +msgid "`GTOPO30 Documentation `__" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:66 +msgid "" +"`SpatioCarte Defense 1.0 specification " +"`__ (in " +"French)" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:69 +msgid "`SRTMHGT Driver <#SRTMHGT>`__" +msgstr "" + +#: ../../source/drivers/raster/eir.rst:5 +msgid "EIR -- Erdas Imagine Raw" +msgstr "" + +#: ../../source/drivers/raster/eir.rst:7 +msgid "EIR" +msgstr "" + +#: ../../source/drivers/raster/eir.rst:11 +msgid "" +"GDAL supports the Erdas Imagine Raw format for read access including 1, " +"2, 4, 8, 16 and 32bit unsigned integers, 16 and 32bit signed integers and" +" 32 and 64bit complex floating point. Georeferencing is supported." +msgstr "" + +#: ../../source/drivers/raster/eir.rst:15 +msgid "" +"To open a dataset select the file with the header information. The driver" +" finds the image file from the header information. Erdas documents call " +"the header file the \"raw\" file and it may have the extension .raw while" +" the image file that contains the actual raw data may have the extension " +".bl." +msgstr "" + +#: ../../source/drivers/raster/eir.rst:21 +msgid "NOTE: Implemented as :source_file:`frmts/raw/eirdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/elas.rst:5 +msgid "ELAS - Earth Resources Laboratory Applications Software" +msgstr "" + +#: ../../source/drivers/raster/elas.rst:7 +msgid "ELAS" +msgstr "" + +#: ../../source/drivers/raster/elas.rst:11 +msgid "" +"ELAS is an old remote sensing system still used for a variety of research" +" projects within NASA. The ELAS format support can be found in " +":source_file:`frmts/elas`." +msgstr "" + +#: ../../source/drivers/raster/elas.rst:29 +msgid "" +"`Short announcement of ELAS driver in GDAL " +"`__" +msgstr "" + +#: ../../source/drivers/raster/elas.rst:31 +msgid "" +"`NASA Software Used In Imaging Service " +"`__ " +"includes ELAS overview" +msgstr "" + +#: ../../source/drivers/raster/envi.rst:5 +msgid "ENVI -- ENVI .hdr Labelled Raster" +msgstr "" + +#: ../../source/drivers/raster/envi.rst:7 +msgid "ENVI" +msgstr "" + +#: ../../source/drivers/raster/envi.rst:11 +msgid "" +"GDAL supports some variations of raw raster files with associated ENVI " +"style .hdr files describing the format. To select an existing ENVI raster" +" file select the binary file containing the data (as opposed to the .hdr " +"file), and GDAL will find the .hdr file by replacing the dataset " +"extension with .hdr." +msgstr "" + +#: ../../source/drivers/raster/envi.rst:17 +msgid "" +"GDAL should support reading bil, bip and bsq interleaved formats, and " +"most pixel types are supported, including 8bit unsigned, 16 and 32bit " +"signed and unsigned integers, 32bit and 64 bit floating point, and 32bit " +"and 64bit complex floating point. There is limited support for " +"recognising map_info keywords with the coordinate system and " +"georeferencing. In particular, UTM and State Plane should work." +msgstr "" + +#: ../../source/drivers/raster/envi.rst:24 +msgid "" +"All ENVI header fields are stored in the ENVI metadata domain, and all of" +" these can then be written out to the header file." +msgstr "" + +#: ../../source/drivers/raster/envi.rst:50 +msgid "NOTE: Implemented as :source_file:`frmts/raw/envidataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ers.rst:5 +msgid "ERS -- ERMapper .ERS" +msgstr "" + +#: ../../source/drivers/raster/ers.rst:7 +msgid "ERS" +msgstr "" + +#: ../../source/drivers/raster/ers.rst:11 +msgid "" +"GDAL supports reading and writing raster files with .ers header files, " +"with some limitations. The .ers ascii format is used by ERMapper for " +"labeling raw data files, as well as for providing extended metadata, and " +"georeferencing for some other file formats. The .ERS format, or variants " +"are also used to hold descriptions of ERMapper algorithms, but these are " +"not supported by GDAL." +msgstr "" + +#: ../../source/drivers/raster/ers.rst:18 +msgid "" +"The PROJ, DATUM and UNITS values found in the ERS header are reported in " +"the ERS metadata domain." +msgstr "" + +#: ../../source/drivers/raster/ers.rst:67 +msgid "Implemented as :source_file:`frmts/ers/ersdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/esat.rst:5 +msgid "ESAT -- Envisat Image Product" +msgstr "" + +#: ../../source/drivers/raster/esat.rst:7 +msgid "ESAT" +msgstr "" + +#: ../../source/drivers/raster/esat.rst:11 +msgid "" +"GDAL supports the Envisat product format for read access. All sample " +"types are supported. Files with two matching measurement datasets (MDS) " +"are represented as having two bands. Currently all ASAR Level 1 and above" +" products, and some MERIS and AATSR products are supported." +msgstr "" + +#: ../../source/drivers/raster/esat.rst:16 +msgid "" +"The control points of the GEOLOCATION GRID ADS dataset are read if " +"available, generally giving a good coverage of the dataset. The GCPs are " +"in WGS84." +msgstr "" + +#: ../../source/drivers/raster/esat.rst:20 +msgid "" +"Virtually all key/value pairs from the MPH and SPH (primary and secondary" +" headers) are copied through as dataset level metadata." +msgstr "" + +#: ../../source/drivers/raster/esat.rst:23 +msgid "" +"ASAR and MERIS parameters contained in the ADS and GADS records (excluded" +" geolocation ones) can be retrieved as key/value pairs using the " +"\"RECORDS\" metadata domain." +msgstr "" + +#: ../../source/drivers/raster/esat.rst:27 +msgid "NOTE: Implemented as :source_file:`frmts/envisat/envisatdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/esat.rst:29 +msgid "" +"See Also: `Envisat `__ " +"at ESA." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:5 +msgid "ESRIC -- Esri Compact Cache" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:7 +msgid "ESRIC" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:11 +msgid "Read Esri Compact Cache V2 as a single raster" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:21 +msgid "Esri Compact Cache V2" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:23 +msgid "" +"A reader for `Esri Compact Cache V2 `__. The cache is stored in multiple files located in " +"a specific folder structure. From the point of view of this driver the " +"raster is represented by the file named conf.xml, which resides in the " +"root folder of the cache. The exact content of this XML file is not " +"fully documented by Esri, and is subject to change. This driver uses only" +" a few of the XML fields, as necessary to read the raster." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:32 +msgid "Esri Tile Package (.tpkx)" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:34 +msgid "" +"Starting from GDAL 3.8, the driver supports reading the `Esri Tile " +"Package Specification `__. A " +"tile package is a compressed file with \".tpkx\" extension. It has a " +"simplified structure, containing image tiles stored in Compact Cache V2 " +"storage format and tiling scheme and other metadata stored in a JSON " +"file." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:43 +msgid "" +"Tile packages with \".tpk\" extension, use compact storage V1 format for " +"cache tiles. The spec for this package type is not available and it is " +"not supported by GDAL." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:50 +msgid "" +"If the /path/Layers contains an Esri Compact Cache in V2 format in the " +"normal Web Mercator tile grid, this command will copy the level 2 content" +" into a TIF file." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:54 +msgid "``gdal_translate -outsize 1024 1024 path/Layers/conf.xml output.tif``" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:56 +msgid "To convert a .tpkx file to a GeoTIFF:" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:58 +msgid "``gdal_translate -outsize 1024 1024 \"/path/to/my.tpkx output.tif``" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:61 +msgid "Features and Limitations" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:63 +msgid "" +"Only V2 Compact cache is supported. This format is identified by the " +"value **esriMapCacheStorageModeCompactV2** in the " +"**CacheInfo.TileCacheInfo.StorageFormat** element of the conf.xml file. " +"Other legacy Esri cache formats are not supported." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:68 +msgid "" +"Only caches with tiles of 256 by 256 pixels are supported. These are " +"stored as the values of the **CacheInfo.TileCacheInfo.TileRows** and " +"**CacheInfo.TileCacheInfo.TileCols** elements." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:73 +msgid "" +"Tiles in the cache can be in different formats, including JPEG and PNG. " +"The most common are 8 bit color or grayscale JPEG and color PNG with or " +"without opacity. These caches will have the value **JPEG**, **PNG** or " +"**MIXED** in the **CacheInfo.TileImageInfo.CacheTileFormat** element. " +"Other tile formats, such as **PNG8** are not supported. The raster will " +"be promoted to RGB or RGBA by this driver, even if the source is " +"grayscale." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:82 +msgid "" +"Only caches with 128 by 128 tiles in a bundle file are supported. This " +"value, the linear number of tiles in a bundle, is contained in the " +"**CacheInfo.CacheStorageInfo.PacketSize** element." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:87 +msgid "" +"The spatial reference is obtained from the " +"**CacheInfo.TileCacheInfo.SpatialReference.WKT** field. If this field is " +"not present, the default value of EPSG:4326 is assumed." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:91 +msgid "" +"As defined in the standard conf.xml file, the cache tile grid has an " +"origin location, stored in the **CacheInfo.TileCacheInfo.TileOrigin** " +"element, which has X and Y components. The cache size is not explicitly " +"defined. The ESRIC format driver will assume a symmetric area around the " +"0,0 coordinates, in the reference system coordinates. This is true for " +"the standard Web Mercator and GCS reference systems. If this assumption " +"is not valid, the conf.xml file can be modified, adding a non-standard " +"**CacheInfo.TileCacheInfo.TileEnd** element with the appropriate values " +"for the X and Y components, similar to the **TileOrigin**. Note that the " +"grid origin and size is different from the raster data extent. For " +"example, it is common to generate a cache in the standard Web Mercator " +"tile grid, which is defined for the whole Earth, even if data is only " +"available for a small region of the globe." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:108 +msgid "" +"A bundled cache has multiple resolution levels, encoded in a series of " +"**CacheInfo.TileCacheInfo.LODInfos.LODInfo** nodes. The **LODInfo** XML " +"nodes are identified by the **LevelID** value, which have to be " +"successive, starting with 0 for the level with the largest value for the " +"**Resolution** and increasing towards the **LODInfo** node with smallest " +"**Resolution** value. The level convention is similar to other Level, Row" +" and Column tile addressing schemes used in WMTS for example. While " +"common, it is not a requirement to have the resolutions of two successive" +" levels differ by a factor of two. Each cache level will be read as an " +"overview, at the appropriate resolution. The resolution values are in " +"spatial reference distance units per pixel." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:122 +msgid "" +"Many caches are built level by level from different sources, similar to " +"many web map tile protocols supported by the GDAL WMS driver. This means " +"that the content of a specific level might be from a different source " +"than an adjacent one, or content for a specific level can be missing " +"altogether. This driver will return opaque black when reading areas which" +" do not have tiles in the cache at a given resolution level, even if data" +" does exist at other levels at the same location." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:131 +msgid "" +"Starting from GDAL 3.8, the driver can automatically expand the paletted " +"images to RGBA. The same cache may contain tiles with different color " +"representations." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:135 +msgid "" +"A cache can exceed the maximum size supported by GDAL, which is " +"INT32_MAX, in either dimension. This driver will generate an error when " +"opening such caches. Removing the **LODInfo** nodes with the highest " +"**LevelID** from the conf.xml file until the raster size drops below " +"INT32_MAX is a possible workaround, but the highest resolution levels " +"will not be read." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:145 +#: ../../source/drivers/raster/gpkg.rst:83 +#: ../../source/drivers/raster/jp2ecw.rst:72 +#: ../../source/drivers/raster/jp2kak.rst:120 +#: ../../source/drivers/raster/jp2openjpeg.rst:86 +#: ../../source/drivers/raster/jpeg.rst:127 +#: ../../source/drivers/raster/jpegxl.rst:55 +#: ../../source/drivers/raster/mbtiles.rst:77 +#: ../../source/drivers/raster/netcdf.rst:277 +#: ../../source/drivers/raster/ngw.rst:125 +#: ../../source/drivers/raster/ogcapi.rst:76 +#: ../../source/drivers/raster/openfilegdb.rst:54 +#: ../../source/drivers/vector/eeda.rst:35 +#: ../../source/drivers/vector/gpkg.rst:194 +#: ../../source/drivers/vector/gpx.rst:93 +#: ../../source/drivers/vector/mvt.rst:163 +#: ../../source/drivers/vector/ngw.rst:169 +#: ../../source/drivers/vector/oapif.rst:80 +#: ../../source/drivers/vector/ods.rst:37 +#: ../../source/drivers/vector/plscenes_data_v1.rst:56 +#: ../../source/drivers/vector/pmtiles.rst:50 +#: ../../source/drivers/vector/tiledb.rst:101 +#: ../../source/drivers/vector/wfs.rst:314 +#: ../../source/drivers/vector/xlsx.rst:45 +msgid "|about-open-options| The following open options are available:" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:163 +msgid "Implemented as :source_file:`frmts/esric/esric_dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:5 +msgid "EXR -- Extended Dynamic Range Image File Format" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:9 +msgid "EXR" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:13 +msgid "" +"OpenEXR is a high dynamic range raster file format. The driver supports " +"reading and writing images in that format." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:16 +msgid "" +"Georeferencing is written as a WKT CRS string and a 3x3 geotransform " +"matrix in EXR header metadata." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:19 +msgid "\"Deep images\" are not supported." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:39 +msgid "``HALF`` corresponds to a IEEE-754 16-bit floating point value." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:40 +msgid "``FLOAT`` corresponds to a IEEE-754 32-bit floating point value." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:41 +msgid "``UINT`` corresponds to a 32-bit unsigned integer value." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:43 +msgid "" +"If not specified, the following GDAL data types will be mapped as " +"following:" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:45 +msgid "``Byte`` ==> HALF" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:46 +msgid "``Int16`` ==> HALF (potentially lossy)" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:47 +msgid "``UInt16`` ==> HALF (potentially lossy)" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:48 +msgid "``Int32`` ==> FLOAT (potentially lossy)" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:49 +msgid "``UInt32`` ==> UINT" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:50 +msgid "``Float32`` ==> FLOAT" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:51 +msgid "``Float64`` ==> FLOAT (generally lossy)" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:-1 +msgid "Supports Create()" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:111 +msgid "" +"With the caveat, that it is only for tiled data, and each tile must be " +"written at most once, and written tiles cannot be read back before " +"dataset closing." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:5 +msgid "FAST -- EOSAT FAST Format" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:7 +msgid "FAST" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:11 +msgid "" +"Supported reading from FAST-L7A format (Landsat TM data) and EOSAT Fast " +"Format Rev. C (IRS-1C/1D data). If you want to read other datasets in " +"this format (SPOT), write to me (Andrey Kiselev, dron@ak4719.spb.edu). " +"You should share data samples with me." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:16 +msgid "" +"Datasets in FAST format represented by several files: one or more " +"administrative headers and one or more files with actual image data in " +"raw format. Administrative files contains different information about " +"scene parameters including filenames of images. You can read files with " +"administrative headers with any text viewer/editor, it is just plain " +"ASCII text." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:23 +msgid "" +"This driver wants administrative file for input. Filenames of images will" +" be extracted and data will be imported, every file will be interpreted " +"as band." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:35 +#: ../../source/drivers/raster/l1b.rst:57 +msgid "Data" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:38 +msgid "FAST-L7A" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:40 +msgid "" +"FAST-L7A consists form several files: big ones with image data and three " +"small files with administrative information. You should give to driver " +"one of the administrative files:" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:44 +msgid "L7fppprrr_rrrYYYYMMDD_HPN.FST: panchromatic band header file with 1 band" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:46 +msgid "L7fppprrr_rrrYYYYMMDD_HRF.FST: VNIR/ SWIR bands header file with 6 bands" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:48 +msgid "L7fppprrr_rrrYYYYMMDD_HTM.FST: thermal bands header file with 2 bands" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:50 +msgid "" +"All raw images corresponded to their administrative files will be " +"imported as GDAL bands." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:53 +msgid "" +"From the \\`\\` `Level 1 Product Output Files Data Format Control Book " +"`__'':" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:56 +msgid "" +"``The file naming convention for the FAST-L7A product files is " +"L7fppprrr_rrrYYYYMMDD_AAA.FST where L7 = Landsat 7 mission f = ETM+ " +"format (1 or 2) (data not pertaining to a specific format defaults to 1)" +" ppp = starting path of the product rrr_rrr = starting and ending rows " +"of the product YYYYMMDD = acquisition date of the image AAA = file " +"type: HPN = panchromatic band header file HRF = VNIR/ SWIR bands header " +"file HTM = thermal bands header file B10 = band 1 B20 = band 2 B30 = band" +" 3 B40 = band 4 B50 = band 5 B61 = band 6L B62 = band 6H B70 = band 7 B80" +" = band 8 FST = FAST file extension``" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:58 +msgid "" +"So you should give to driver one of the " +"``L7fppprrr_rrrYYYYMMDD_HPN.FST``, ``L7fppprrr_rrrYYYYMMDD_HRF.FST`` or " +"``L7fppprrr_rrrYYYYMMDD_HTM.FST`` files." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:63 +msgid "IRS-1C/1D" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:65 +msgid "" +"Fast Format REV. C does not contain band filenames in administrative " +"header. So we should guess band filenames, because different data " +"distributors name their files differently. Several naming schemes " +"hardcoded in GDAL's FAST driver. These are:" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:70 +msgid "``
.
.1.
.2. ...``" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:74 +msgid "``
. band1. band2. ...``" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:78 +msgid "``
. band1.dat band2.dat ...``" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:82 +msgid "``
. imagery1. imagery2. ...``" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:86 +msgid "``
. imagery1.dat imagery2.dat ...``" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:88 +msgid "" +"in lower or upper case. Header file could be named arbitrarily. This " +"should cover majority of distributors fantasy in naming files. But if you" +" out of luck and your datasets named differently you should rename them " +"manually before importing data with GDAL." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:93 +msgid "" +"GDAL also supports the logic for naming band files for datasets produced " +"by Euromap GmbH for IRS-1C/IRS-1D PAN, LISS3 and WIFS sensors. Their " +"filename logic is explained in the `Euromap Naming Conventions " +"`__ document." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:99 +#: ../../source/drivers/raster/hdf4.rst:171 +#: ../../source/drivers/raster/hdf5.rst:197 +#: ../../source/drivers/raster/l1b.rst:25 +#: ../../source/drivers/raster/mrsid.rst:56 +#: ../../source/drivers/raster/netcdf.rst:245 +msgid "Georeference" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:101 +msgid "" +"All USGS projections should be supported (namely UTM, LCC, PS, PC, TM, " +"OM, SOM). Contact me if you have troubles with proper projection " +"extraction." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:108 +msgid "Calibration coefficients for each band reported as metadata items." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:110 +msgid "**ACQUISITION_DATE**: First scene acquisition date in yyyyddmm format." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:112 +msgid "**SATELLITE**: First scene satellite name." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:113 +msgid "**SENSOR**: First scene sensor name." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:114 +msgid "**BIASn**: Bias value for the channel **n**." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:115 +msgid "**GAINn**: Gain value for the channel **n**." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:120 +msgid "Implemented as :source_file:`frmts/raw/fastdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:122 +msgid "" +"Landsat FAST L7A format description available from " +"http://ltpwww.gsfc.nasa.gov/IAS/htmls/l7_review.html (see `ESDIS Level 1 " +"Product Generation System (LPGS) Output Files DFCB, Vol. 5, Book 2 " +"`__)" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:127 +msgid "" +"EOSAT Fast Format REV. C description available from " +"http://www.euromap.de/docs/doc_001.html" +msgstr "" + +#: ../../source/drivers/raster/fit.rst:5 +msgid "FIT -- FIT" +msgstr "" + +#: ../../source/drivers/raster/fit.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/fit/fitdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:5 +msgid "FITS -- Flexible Image Transport System" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:7 +msgid "FITS" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:11 +msgid "" +"FITS is a format used mainly by astronomers, but it is a relatively " +"simple format that supports arbitrary image types and multi-spectral " +"images, and so has found its way into GDAL. FITS support is implemented " +"in terms of the standard `CFITSIO library " +"`__, which" +" you must have on your system in order for FITS support to be enabled " +"(see :ref:`notes on CFITSIO linking `). Both " +"reading and writing of FITS files is supported." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:20 +msgid "" +"Starting from version 3.0 georeferencing system support is implemented " +"via the conversion of WCS (World Coordinate System) keywords. Only " +"Latitude - Longitude systems (see the `FITS standard document " +"`_) have been implemented, those for which remote " +"sensing processing is commonly used. As 3D Datum information is missing " +"in FITS/WCS standard, Radii and target bodies are translated using the " +"planetary extension proposed `here " +"`_." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:30 +msgid "" +"Non-standard header keywords that are present in the FITS file will be " +"copied to the dataset's metadata when the file is opened, for access via " +"GDAL methods. Similarly, non-standard header keywords that the user " +"defines in the dataset's metadata will be written to the FITS file when " +"the GDAL handle is closed." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:36 +msgid "" +"Note to those familiar with the CFITSIO library: The automatic rescaling " +"of data values, triggered by the presence of the BSCALE and BZERO header " +"keywords in a FITS file, is disabled in GDAL < v3.0. Those header " +"keywords are accessible and updatable via dataset metadata, in the same " +"was as any other header keywords, but they do not affect reading/writing " +"of data values from/to the file. Starting from version 3.0 BZERO and " +"BSCALE keywords are managed via standard " +":cpp:func:`GDALRasterBand::GetOffset` / " +":cpp:func:`GDALRasterBand::SetOffset` and " +":cpp:func:`GDALRasterBand::GetScale` / " +":cpp:func:`GDALRasterBand::SetScale` GDAL functions and no more referred " +"as metadata." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:47 +msgid "Multiple image support" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:49 +msgid "" +"Starting with GDAL 3.2, Multi-Extension FITS (MEF) files that contain one" +" or more extensions following the primary HDU are supported. When more " +"than 2 image HDUs are found, they are reported as subdatasets." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:53 +msgid "" +"The connection string for a given subdataset/HDU is " +"``FITS:\"filename.fits\":hdu_number``" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:56 +msgid "Binary table support" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:58 +msgid "" +"Starting with GDAL 3.2, binary tables will be exposed as vector layers " +"(update and creation support from GDAL 3.2.1)." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:61 +msgid "The FITS data types are mapped to OGR data types as the following:" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:63 +msgid "Data types" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:66 +msgid "TFORM value" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:67 +msgid "TSCAL, TOFFSET value" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:68 +msgid "Occurrence count" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:69 +#: ../../source/drivers/vector/netcdf.rst:81 +#: ../../source/drivers/vector/netcdf.rst:120 +msgid "OGR field type" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:70 +msgid "OGR field subtype" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:71 +#: ../../source/drivers/raster/fits.rst:76 +msgid "'L' (Logical)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:72 +#: ../../source/drivers/raster/fits.rst:77 +#: ../../source/drivers/raster/fits.rst:82 +#: ../../source/drivers/raster/fits.rst:177 +#: ../../source/drivers/raster/fits.rst:182 +msgid "ignored" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:74 +#: ../../source/drivers/raster/fits.rst:84 +#: ../../source/drivers/raster/fits.rst:89 +#: ../../source/drivers/raster/fits.rst:99 +#: ../../source/drivers/raster/fits.rst:104 +#: ../../source/drivers/raster/fits.rst:129 +#: ../../source/drivers/raster/fits.rst:134 +#: ../../source/drivers/vector/ngw.rst:141 +msgid "OFTInteger" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:75 +#: ../../source/drivers/raster/fits.rst:80 +msgid "OFSTBoolean" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:78 +#: ../../source/drivers/raster/fits.rst:93 +#: ../../source/drivers/raster/fits.rst:123 +#: ../../source/drivers/raster/fits.rst:153 +#: ../../source/drivers/raster/fits.rst:168 +#: ../../source/drivers/raster/fits.rst:173 +#: ../../source/drivers/raster/fits.rst:198 +#: ../../source/drivers/raster/fits.rst:203 +#: ../../source/drivers/raster/fits.rst:213 +#: ../../source/drivers/raster/fits.rst:223 +#: ../../source/drivers/raster/fits.rst:233 +msgid "> 1" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:79 +#: ../../source/drivers/raster/fits.rst:94 +#: ../../source/drivers/raster/fits.rst:114 +#: ../../source/drivers/raster/fits.rst:119 +#: ../../source/drivers/raster/fits.rst:144 +#: ../../source/drivers/raster/fits.rst:149 +msgid "OFTIntegerList" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:81 +msgid "'X' (bit)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:83 +msgid "each bit mapped to a OGR field" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:85 +#: ../../source/drivers/raster/fits.rst:90 +#: ../../source/drivers/raster/fits.rst:95 +#: ../../source/drivers/raster/fits.rst:105 +#: ../../source/drivers/raster/fits.rst:110 +#: ../../source/drivers/raster/fits.rst:120 +#: ../../source/drivers/raster/fits.rst:125 +#: ../../source/drivers/raster/fits.rst:130 +#: ../../source/drivers/raster/fits.rst:135 +#: ../../source/drivers/raster/fits.rst:140 +#: ../../source/drivers/raster/fits.rst:145 +#: ../../source/drivers/raster/fits.rst:150 +#: ../../source/drivers/raster/fits.rst:155 +#: ../../source/drivers/raster/fits.rst:160 +#: ../../source/drivers/raster/fits.rst:165 +#: ../../source/drivers/raster/fits.rst:170 +#: ../../source/drivers/raster/fits.rst:175 +#: ../../source/drivers/raster/fits.rst:180 +#: ../../source/drivers/raster/fits.rst:185 +#: ../../source/drivers/raster/fits.rst:195 +#: ../../source/drivers/raster/fits.rst:205 +#: ../../source/drivers/raster/fits.rst:210 +#: ../../source/drivers/raster/fits.rst:215 +#: ../../source/drivers/raster/fits.rst:220 +#: ../../source/drivers/raster/fits.rst:225 +#: ../../source/drivers/raster/fits.rst:230 +#: ../../source/drivers/raster/fits.rst:235 +msgid "OFSTNone" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:86 +#: ../../source/drivers/raster/fits.rst:91 +msgid "'B' (unsigned byte)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:87 +#: ../../source/drivers/raster/fits.rst:92 +msgid "1, 0 (unsigned byte) or 1, -128 (signed byte)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:96 +#: ../../source/drivers/raster/fits.rst:106 +#: ../../source/drivers/raster/fits.rst:121 +msgid "'I' (16 bit signed integer)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:97 +#: ../../source/drivers/raster/fits.rst:112 +#: ../../source/drivers/raster/fits.rst:127 +#: ../../source/drivers/raster/fits.rst:142 +#: ../../source/drivers/raster/fits.rst:157 +#: ../../source/drivers/raster/fits.rst:167 +#: ../../source/drivers/raster/fits.rst:187 +#: ../../source/drivers/raster/fits.rst:197 +msgid "1, 0" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:100 +#: ../../source/drivers/raster/fits.rst:115 +msgid "OFSTInt16" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:101 +#: ../../source/drivers/raster/fits.rst:116 +msgid "'I' (16 bit integer, interpreted as unsigned)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:102 +#: ../../source/drivers/raster/fits.rst:117 +msgid "1, 32768" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:107 +msgid "other than (1,0) and (1,32768)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:109 +#: ../../source/drivers/raster/fits.rst:139 +#: ../../source/drivers/raster/fits.rst:164 +#: ../../source/drivers/raster/fits.rst:189 +#: ../../source/drivers/raster/fits.rst:194 +#: ../../source/drivers/raster/fits.rst:209 +#: ../../source/drivers/vector/ngw.rst:143 +msgid "OFTReal" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:111 +msgid "'I' (16 bit integer)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:113 +#: ../../source/drivers/raster/fits.rst:118 +#: ../../source/drivers/raster/fits.rst:143 +#: ../../source/drivers/raster/fits.rst:148 +msgid ">1" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:122 +msgid "other than (1, 0) and (1, 32768)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:124 +#: ../../source/drivers/raster/fits.rst:154 +#: ../../source/drivers/raster/fits.rst:174 +#: ../../source/drivers/raster/fits.rst:199 +#: ../../source/drivers/raster/fits.rst:204 +#: ../../source/drivers/raster/fits.rst:214 +msgid "OFTRealList" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:126 +#: ../../source/drivers/raster/fits.rst:136 +#: ../../source/drivers/raster/fits.rst:151 +msgid "'J' (32 bit signed integer)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:131 +#: ../../source/drivers/raster/fits.rst:146 +msgid "'J' (32 bit integer, interpreted as unsigned)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:132 +#: ../../source/drivers/raster/fits.rst:147 +msgid "1, 2147483648" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:137 +#: ../../source/drivers/raster/fits.rst:152 +msgid "other than (1, 0) and (1, 2147483648)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:141 +msgid "'J' (32 bit integer)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:156 +#: ../../source/drivers/raster/fits.rst:161 +#: ../../source/drivers/raster/fits.rst:166 +#: ../../source/drivers/raster/fits.rst:171 +msgid "'K' (64 bit signed integer)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:159 +#: ../../source/drivers/raster/fits.rst:169 +#: ../../source/drivers/vector/ngw.rst:142 +msgid "OFTInteger64" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:162 +#: ../../source/drivers/raster/fits.rst:172 +#: ../../source/drivers/raster/fits.rst:192 +#: ../../source/drivers/raster/fits.rst:202 +msgid "other than (1, 0)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:176 +#: ../../source/drivers/raster/fits.rst:181 +msgid "'A' (character)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:178 +msgid "if TFORM='Axxx' and no TDIM header" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:179 +#: ../../source/drivers/vector/ngw.rst:144 +msgid "OFTString" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:183 +msgid "TDIM for 2D field, or variable length ('PA')" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:184 +msgid "OFTStringList" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:186 +#: ../../source/drivers/raster/fits.rst:191 +#: ../../source/drivers/raster/fits.rst:196 +#: ../../source/drivers/raster/fits.rst:201 +msgid "'E' (single precision floating point)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:190 +#: ../../source/drivers/raster/fits.rst:200 +msgid "OFSTFloat32" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:206 +#: ../../source/drivers/raster/fits.rst:211 +msgid "'D' (double precision floating point)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:207 +#: ../../source/drivers/raster/fits.rst:212 +#: ../../source/drivers/raster/fits.rst:217 +#: ../../source/drivers/raster/fits.rst:222 +#: ../../source/drivers/raster/fits.rst:227 +#: ../../source/drivers/raster/fits.rst:232 +msgid "any" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:216 +#: ../../source/drivers/raster/fits.rst:221 +msgid "'C' (single precision complex)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:219 +#: ../../source/drivers/raster/fits.rst:229 +msgid "OFTString whose value is of the form \"x + yj\"" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:224 +#: ../../source/drivers/raster/fits.rst:234 +msgid "OFTStringList whose values are of the form \"x + yj\"" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:226 +#: ../../source/drivers/raster/fits.rst:231 +msgid "'M' (double precision complex)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:237 +msgid "" +"Fields with a repeat count > 1 expressing fixed size arrays, or fields " +"using array descriptors 'P' and 'Q' for variable length arrays are mapped" +" to OGR OFTxxxxxList data types. The potential 2D structure of such field" +" has no direct equivalence in OGR, so OGR will expose a linear structure." +" For fixed size arrays, the user can retrieve the value of the TDIMxx " +"header in the layer metadata to recover the dimensionality of the field." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:244 +msgid "" +"Fields that have TSCAL and/or TZERO headers are automatically scaled and " +"offset to the physical value (only applies to numeric data types)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:247 +msgid "" +"TNULL headers are used for integer numeric data types and for a single-" +"occurence field to set a OGR field to NULL." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:251 +#: ../../source/drivers/vector/amigocloud.rst:106 +#: ../../source/drivers/vector/arrow.rst:58 +#: ../../source/drivers/vector/carto.rst:138 +#: ../../source/drivers/vector/dgnv8.rst:204 +#: ../../source/drivers/vector/elasticsearch.rst:447 +#: ../../source/drivers/vector/geojson.rst:279 +#: ../../source/drivers/vector/geojsonseq.rst:64 +#: ../../source/drivers/vector/gpkg.rst:343 +#: ../../source/drivers/vector/gpx.rst:229 +#: ../../source/drivers/vector/jsonfg.rst:130 +#: ../../source/drivers/vector/libkml.rst:283 +#: ../../source/drivers/vector/memory.rst:46 +#: ../../source/drivers/vector/miramon.rst:294 +#: ../../source/drivers/vector/mongodbv3.rst:234 +#: ../../source/drivers/vector/mvt.rst:400 +#: ../../source/drivers/vector/netcdf.rst:319 +#: ../../source/drivers/vector/ngw.rst:256 +#: ../../source/drivers/vector/parquet.rst:62 +#: ../../source/drivers/vector/pmtiles.rst:220 +#: ../../source/drivers/vector/selafin.rst:349 +#: ../../source/drivers/vector/shapefile.rst:346 +#: ../../source/drivers/vector/sqlite.rst:323 +#: ../../source/drivers/vector/tiledb.rst:160 +msgid "Layer creation options" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:253 +#: ../../source/drivers/raster/mbtiles.rst:474 +#: ../../source/drivers/vector/amigocloud.rst:108 +#: ../../source/drivers/vector/gpkg.rst:345 +#: ../../source/drivers/vector/memory.rst:48 +#: ../../source/drivers/vector/ngw.rst:258 +#: ../../source/drivers/vector/tiledb.rst:162 +#: ../../source/drivers/vector/vdv.rst:59 +msgid "" +"|about-layer-creation-options| The following layer creation options are " +"available:" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:277 +msgid "" +"When using ogr2ogr or :cpp:func:`GDALVectorTranslate` with a FITS source," +" the FITS header will be taken into account, in particular to help to " +"determine the FITS data type of target columns." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:284 +msgid "Listing subdatasets in a MEF .fits:" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:307 +msgid "Opening a given raster HDU:" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:326 +msgid "Listing potential binary tables in a FITS file:" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:333 +msgid "Converting a GeoPackage layer into a FITS binary table:" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:342 +msgid "Other" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:344 +msgid "NOTE: Implemented as :source_file:`frmts/fits/fitsdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:349 +msgid "Notes on CFITSIO linking in GDAL" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:353 +msgid "From source" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:354 +msgid "" +"Install CFITSIO headers from your distro (eg, cfitsio-devel on Fedora; " +"libcfitsio-dev on Debian-Ubuntu), then compile GDAL as usual. CFITSIO " +"will be automatically detected and linked." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:357 +msgid "From distros" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:358 +msgid "" +"On Fedora/CentOS install CFITSIO then GDAL with dnf (yum): cfitsio is " +"automatically linked." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:361 +msgid "MacOSX" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:362 +msgid "" +"The last versions of the MacOSX packages are not linked against CFITSIO. " +"Install CFITSIO as described in the `official documentation " +"`__." +msgstr "" + +#: ../../source/drivers/raster/genbin.rst:5 +msgid "GenBin -- Generic Binary (.hdr labelled)" +msgstr "" + +#: ../../source/drivers/raster/genbin.rst:7 +msgid "GenBin" +msgstr "" + +#: ../../source/drivers/raster/genbin.rst:11 +msgid "" +"This driver supporting reading \"Generic Binary\" files labelled with a " +".hdr file, but distinct from the more common ESRI labelled .hdr format " +"(EHdr driver). The origin of this format is not entirely clear. The .hdr " +"files supported by this driver are look something like this:" +msgstr "" + +#: ../../source/drivers/raster/genbin.rst:25 +msgid "" +"Pixel data types of U8, U16, S16, F32, F64, and U1 (bit) are supported. " +"Georeferencing and coordinate system information should be supported when" +" provided." +msgstr "" + +#: ../../source/drivers/raster/genbin.rst:29 +msgid "NOTE: Implemented as :source_file:`frmts/raw/genbindataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:7 +msgid "GeoRaster" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:11 +msgid "" +"This driver supports reading and writing raster data in Oracle Spatial " +"GeoRaster format (10g or later). The Oracle Spatial GeoRaster driver is " +"optionally built as a GDAL plugin, but it requires Oracle client " +"libraries." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:16 +msgid "When opening a GeoRaster, its name should be specified in the form:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:18 +msgid "georaster:{,/}{,@}[db],[schema.][table],[column],[where]" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:19 +msgid "georaster:{,/}{,@}[db],," +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:21 +msgid "Where:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:23 +msgid "user   = Oracle server user's name login" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:24 +msgid "pwd    = user password" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:25 +msgid "db     = Oracle server identification (database name)" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:26 +msgid "schema = name of a schema" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:28 +msgid "table  = name of a GeoRaster table (table that contains GeoRaster columns)" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:29 +msgid "column = name of a column data type MDSYS.SDO_GEORASTER" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:31 +msgid "where  = a simple where clause to identify one or multiples GeoRaster(s)" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:32 +msgid "rdt    = name of a raster data table" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:33 +msgid "rid    = numeric identification of one GeoRaster" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:35 +#: ../../source/drivers/raster/mbtiles.rst:528 +msgid "Examples:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:37 +msgid "geor:scott,tiger,demodb,table,column,id=1" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:38 +msgid "geor:scott,tiger,demodb,table,column,\"id = 1\"" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:39 +msgid "\"georaster:scott/tiger@demodb,table,column,gain>10\"" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:40 +msgid "\"georaster:scott/tiger@demodb,table,column,city='Brasilia'\"" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:41 +msgid "georaster:scott,tiger,,rdt_10$,10" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:42 +msgid "geor:scott/tiger,,rdt_10$,10" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:44 +msgid "Note: do note use space around the field values and the commas." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:46 +msgid "" +"Note: like in the last two examples, the database name field could be " +"left empty (\",,\") and the TNSNAME will be used." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:49 +msgid "" +"Note: If  the query results in more than one GeoRaster it will be treated" +" as a GDAL metadata's list of sub-datasets (see below)" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:64 +msgid "Browsing the database for GeoRasters" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:66 +msgid "" +"By providing some basic information the GeoRaster driver is capable of " +"listing the existing rasters stored on the server:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:69 +msgid "" +"To list all the GeoRaster table on the server that belongs to that user " +"name and database:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:76 +msgid "To list all the GeoRaster type columns that exist in that table:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:82 +msgid "That will list all the GeoRaster objects stored in that table." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:88 +msgid "" +"That will list all the GeoRaster existing on that table according to a " +"Where clause." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:96 +msgid "" +"Note that the result of those queries are returned as GDAL metadata sub-" +"datasets, e.g.:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:258 +msgid "" +"When this value is set to FALSE, then the bin function to use is the one " +"generated dynamically as previously described." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:271 +msgid "A valid function defined in the GeoRaster metadata." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:272 +msgid "The same bin function generated when :co:`GENSTATS_USEBIN` is FALSE." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:284 +msgid "" +"A NODATA value is used for cells whose values are either not known or " +"meaningless" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:368 +msgid "Importing GeoRaster" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:370 +msgid "" +"During the process of importing raster into a GeoRaster object it is " +"possible to give the driver a simple SQL table definition and also a SQL " +"insert/values clause to inform the driver about the table to be created " +"and the values to be added to the newly created row. The following " +"example does that:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:384 +msgid "" +"Note that the create option DESCRIPTION requires to inform table name (in" +" bold). And column name (underlined) should match the description:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:393 +msgid "" +"If the table \"landsat\" exist, the option \"DESCRIPTION\" is ignored. " +"The driver can only update one GeoRaster column per run of " +"gdal_translate. Oracle create default names and values for RDT and RID " +"during the initialization of the SDO_GEORASTER object but user are also " +"able to specify a name and value of their choice." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:404 +msgid "" +"If no information is given about where to store the raster the driver " +"will create (if doesn't exist already) a default table named GDAL_IMPORT " +"with just one GeoRaster column named RASTER and a table GDAL_RDT as the " +"RDT, the RID will be given automatically by the server, example:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:414 +msgid "Exporting GeoRaster" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:416 +msgid "A GeoRaster can be identified by a Where clause or by a pair of RDT & RID:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:424 +msgid "Cross schema access" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:426 +msgid "" +"As long as the user was granted full access the GeoRaster table and the " +"Raster Data Table, e.g.:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:435 +msgid "" +"It is possible to an user access to extract and load GeoRaster from " +"another user/schema by informing the schema name as showed here:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:438 +msgid "Browsing:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:446 +msgid "Extracting:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:453 +msgid "" +"Note: On the above example that accessing by RDT/RID doesn't need schame " +"name as long as the users is granted full access to both tables." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:457 +msgid "Loading:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:466 +msgid "General use of GeoRaster" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:468 +msgid "" +"GeoRaster can be used in any GDAL command line tool with all the " +"available options. Like a image subset extraction or re-project:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:478 +msgid "" +"Two different GeoRaster can be used as input and output on the same " +"operation:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:485 +msgid "" +"Applications that use GDAL can theoretically read and write from " +"GeoRaster just like any other format but most of then are more inclined " +"to try to access files on the file system so one alternative is to create" +" VRT to represent the GeoRaster description, e.g.:" +msgstr "" + +#: ../../source/drivers/raster/gff.rst:5 +msgid "GFF -- Sandia National Laboratories GSAT File Format" +msgstr "" + +#: ../../source/drivers/raster/gff.rst:7 +msgid "GFF" +msgstr "" + +#: ../../source/drivers/raster/gff.rst:11 +msgid "" +"This read-only GDAL driver is designed to provide access to processed " +"data from Sandia National Laboratories' various experimental sensors. The" +" format is essentially an arbitrary length header containing instrument " +"configuration and performance parameters along with a binary matrix of " +"16- or 32-bit complex or byte real data." +msgstr "" + +#: ../../source/drivers/raster/gff.rst:17 +msgid "" +"The GFF format was implemented based on the Matlab code provided by " +"Sandia to read the data. The driver supports all types of data (16-bit or" +" 32-bit complex, real bytes) theoretically, however due to a lack of data" +" only 32-bit complex data has been tested." +msgstr "" + +#: ../../source/drivers/raster/gff.rst:22 +msgid "" +"Sandia provides some sample data at http://www.sandia.gov/radar/complex-" +"data/." +msgstr "" + +#: ../../source/drivers/raster/gff.rst:25 +msgid "The extension for GFF formats is .gff." +msgstr "" + +#: ../../source/drivers/raster/gff.rst:27 +msgid "NOTE: Implemented as :source_file:`frmts/gff/gff_dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:5 +msgid "GIF -- Graphics Interchange Format" +msgstr "" + +#: ../../source/drivers/raster/gif.rst:7 +msgid "GIF" +msgstr "" + +#: ../../source/drivers/raster/gif.rst:11 +msgid "" +"GDAL supports reading and writing of normal, and interlaced GIF files. " +"Gif files always appear as having one colormapped eight bit band. GIF " +"files have no support for georeferencing." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:15 +msgid "" +"A GIF image with transparency will have that entry marked as having an " +"alpha value of 0.0 (transparent). Also, the transparent value will be " +"returned as the NoData value for the band." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:19 +msgid "" +"If an ESRI world file exists with the .gfw, .gifw or .wld extension, it " +"will be read and used to establish the geotransform for the image." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:22 +#: ../../source/drivers/raster/jpeg.rst:60 +#: ../../source/drivers/raster/pdf.rst:48 +#: ../../source/drivers/raster/png.rst:36 +#: ../../source/drivers/raster/webp.rst:28 +msgid "" +"XMP metadata can be extracted from the file, and will be stored as XML " +"raw content in the xml:XMP metadata domain." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:35 +msgid "" +"GIF files can only be created as 1 8bit band using the \"CreateCopy\" " +"mechanism. If written from a file that is not colormapped, a default " +"greyscale colormap is generated. Transparent GIFs are not currently " +"supported on creation." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:55 +msgid "" +"GDAL's internal GIF support is implemented based on source from the " +"giflib 4.1.6 library (written by Gershon Elbor, Eric Raymond and Toshio " +"Kuratomi), hence generating LZW compressed GIF." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:59 +msgid "" +"The driver was written with the financial support of the `DM Solutions " +"Group `__, and `CIET International " +"`__." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:66 +msgid "`giflib Home Page `__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:5 +msgid "GPKG -- GeoPackage raster" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:7 +#: ../../source/drivers/vector/gpkg.rst:6 +msgid "GPKG" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:11 +msgid "" +"This driver implements full read/creation/update of tables containing " +"raster tiles in the `OGC GeoPackage format standard " +"`__. The GeoPackage standard uses a " +"SQLite database file as a generic container, and the standard defines:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:17 +msgid "" +"Expected metadata tables (``gpkg_contents``, ``gpkg_spatial_ref_sys``, " +"``gpkg_tile_matrix``, ``gpkg_tile_matrix_set``, ...)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:20 +msgid "" +"Tile format encoding (PNG and JPEG for base specification, WebP as " +"extension) and tiling conventions" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:22 +msgid "Naming and conventions for extensions" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:24 +#: ../../source/drivers/vector/gpkg.rst:24 +msgid "" +"This driver reads and writes SQLite files from the file system, so it " +"must be run by a user with read/write access to the files it is working " +"with." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:28 +msgid "" +"The driver can also handle GeoPackage vectors. See :ref:`GeoPackage " +"vector ` documentation page" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:31 +msgid "Various kind of input datasets can be converted to GeoPackage raster :" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:33 +msgid "Single band grey level" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:34 +msgid "Single band with R,G,B or R,G,B,A color table" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:35 +msgid "Two bands: first band with grey level, second band with alpha channel" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:36 +msgid "Three bands: Red, Green, Blue" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:37 +msgid "Four band: Red, Green, Blue, Alpha" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:39 +msgid "GeoPackage rasters only support Byte data type." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:41 +msgid "" +"All raster extensions standardized by the GeoPackage specification are " +"supported in read and creation :" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:44 +msgid "" +"*gpkg_webp*: when storing WebP tiles, provided that GDAL is compiled " +"against libwebp." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:46 +msgid "" +"*gpkg_zoom_other*: when resolution of consecutive zoom levels does not " +"vary with a factor of 2." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:61 +#: ../../source/drivers/raster/mbtiles.rst:75 +#: ../../source/drivers/vector/mvt.rst:161 +#: ../../source/drivers/vector/pmtiles.rst:48 +msgid "Opening options" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:63 +msgid "" +"By default, the driver will expose a GeoPackage dataset as a four band " +"(Red,Green, Blue,Alpha) dataset, which gives the maximum compatibility " +"with the various encodings of tiles that can be stored. It is possible to" +" specify an explicit number of bands with the BAND_COUNT opening option. " +"Starting with GDAL 3.6, a special metadata item is written when creating " +"a GeoPackage raster with GDAL (when using the default CUSTOM tiling " +"scheme), and it is used on reading as the default number of bands." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:72 +msgid "" +"The driver will use the geographic/projected extent indicated in the " +"`gpkg_contents `__ table, and " +"do necessary clipping, if needed, to respect that extent. However that " +"information being optional, if omitted, the driver will use the extent " +"provided by the `gpkg_tile_matrix_set " +"`__, which covers the " +"extent at all zoom levels. The user can also specify the " +"USE_TILE_EXTENT=YES open option to use the actual extent of tiles at the " +"maximum zoom level. Or it can specify any of MINX/MINY/MAXX/MAXY to have " +"a custom extent." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:169 +msgid "" +"Note: open options are typically specified with \"-oo name=value\" syntax" +" in most GDAL utilities, or with the GDALOpenEx() API call." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:175 +msgid "" +"Depending of the number of bands of the input dataset and the tile format" +" selected, the driver will do the necessary conversions to be compatible " +"with the tile format." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:179 +msgid "" +"To add several tile tables to a GeoPackage dataset (seen as GDAL " +"subdatasets), or to add a tile table to an existing vector-only " +"GeoPackage, the generic APPEND_SUBDATASET=YES creation option must be " +"provided." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:184 +#: ../../source/drivers/raster/mbtiles.rst:189 +msgid "" +"Fully transparent tiles will not be written to the database, as allowed " +"by the format." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:187 +msgid "" +"The driver implements the Create() and IWriteBlock() methods, so that " +"arbitrary writing of raster blocks is possible, enabling the direct use " +"of GeoPackage as the output dataset of utilities such as gdalwarp." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:191 +#: ../../source/drivers/raster/mbtiles.rst:196 +msgid "" +"On creation, raster blocks can be written only if the geotransformation " +"matrix has been set with SetGeoTransform() This is effectively needed to " +"determine the zoom level of the full resolution dataset based on the " +"pixel resolution, dataset and tile dimensions." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:196 +msgid "" +"Technical/implementation note: when a dataset is opened with a non-" +"default area of interest (i.e. use of MINX,MINY,MAXX,MAXY or " +"USE_TILE_EXTENT open option), or when creating/ opening a dataset with a " +"non-custom tiling scheme, it is possible that GDAL blocks do not exactly " +"match a single GeoPackage tile. In which case, each GDAL block will " +"overlap four GeoPackage tiles. This is easily handled on the read side, " +"but on creation/update side, such configuration could cause numerous " +"decompression/ recompression of tiles to be done, which might cause " +"unnecessary quality loss when using lossy compression (JPEG, WebP). To " +"avoid that, the driver will create a temporary database next to the main " +"GeoPackage file to store partial GeoPackage tiles in a lossless (and " +"uncompressed) way. Once a tile has received data for its four quadrants " +"and for all the bands (or the dataset is closed or explicitly flushed " +"with FlushCache()), those uncompressed tiles are definitely transferred " +"to the GeoPackage file with the appropriate compression. All of this is " +"transparent to the user of GDAL API/utilities" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:213 +#: ../../source/drivers/vector/gpkg.rst:263 +msgid "" +"The driver updates the GeoPackage ``last_change`` timestamp when the file" +" is created or modified. If consistent binary output is required for " +"reproducibility, the timestamp can be forced to a specific value by " +"setting the :config:`OGR_CURRENT_DATE` global configuration option. When " +"setting the option, take care to meet the specific time format " +"requirement of the GeoPackage standard, e.g. `for version 1.2 " +"`__." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:225 +#: ../../source/drivers/raster/mbtiles.rst:216 +msgid "Tile formats" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:228 +msgid "Tiled rasters" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:230 +msgid "This section only applies for raster of Byte data type." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:232 +msgid "" +"GeoPackage can store tiles in different formats, PNG and/or JPEG for the " +"baseline specification, and WebP for extended GeoPackage. Support for " +"those tile formats depend if the underlying drivers are available in " +"GDAL, which is generally the case for PNG and JPEG, but not necessarily " +"for WebP since it requires GDAL to be compiled against the optional " +"libwebp." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:239 +msgid "" +"By default, GDAL will use a mix of PNG and JPEG tiles (PNG_JPEG tile " +"format, or AUTO). PNG tiles will be used to store tiles that are not " +"completely opaque, either because input dataset has an alpha channel with" +" non fully opaque content, or because tiles are partial due to clipping " +"at the right or bottom edges of the raster, or when a dataset is opened " +"with a non-default area of interest, or with a non-custom tiling scheme. " +"On the contrary, for fully opaque tiles, JPEG format will be used. " +"Starting with GDAL 3.6, if the raster has only one band, the default is " +"PNG." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:249 +msgid "" +"It is possible to select one unique tile format by setting the " +"creation/open option TILE_FORMAT to one of PNG, JPEG or WEBP. When using " +"JPEG, the alpha channel will not be stored. When using WebP, the " +"`gpkg_webp `__ " +"extension will be registered. The lossy compression of WebP is used. Note" +" that a recent enough libwebp (>=0.1.4) must be used to support alpha " +"channel in WebP tiles." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:257 +#: ../../source/drivers/raster/mbtiles.rst:226 +msgid "" +"PNG8 can be selected to use 8-bit PNG with a color table up to 256 " +"colors. On creation, an optimized color table is computed for each tile. " +"The DITHER option can be set to YES to use Floyd/Steinberg dithering " +"algorithm, which spreads the quantization error on neighbouring pixels " +"for better rendering (note however than when zooming in, this can cause " +"non desirable visual artifacts). Setting it to YES will generally cause " +"less effective compression. Note that at that time, such an 8-bit PNG " +"formulation is only used for fully opaque tiles, as the median-cut " +"algorithm currently implemented to compute the optimal color table does " +"not support alpha channel (even if PNG8 format would potentially allow " +"color table with transparency). So when selecting PNG8, non fully opaque " +"tiles will be stored as 32-bit PNG." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:271 +msgid "Tiled gridded coverage data" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:273 +msgid "" +"Since GDAL 2.3, `tiled gridded coverage data " +"`__ can be " +"stored using PNG unsigned 16bit tiles (with potential offset and scaling " +"so as to be able to represent floating point data) or TIFF 32-bit " +"floating-point LZW compressed tiles." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:279 +msgid "" +"When converting a GDAL Int16 or UInt16 dataset, PNG tiles will be used. " +"When converting a GDAL Float32 dataset, TIFF tiles will be used by " +"default, unless PNG is explicitly selected, in which case scaling and " +"offsetting will be automatically computed for each tile." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:286 +msgid "" +"The `tiled gridded extension " +"`__" +" initially implemented in GDAL 2.2 was not officially adopted and had " +"been later reworked by OGC. The adopted `tiled gridded coverage data " +"`__ has a " +"few differences that will make GDAL 2.2 datasets not be compliant with " +"the final extension. GDAL 2.3 can open those GDAL 2.2-generated files." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:298 +msgid "Tiling schemes" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:300 +msgid "" +"By default, conversion to GeoPackage will create a custom tiling scheme, " +"such that the input dataset can be losslessly converted, both at the " +"pixel and georeferencing level (if using a lossless tile format such as " +"PNG). That tiling scheme is such that its origin (*min_x*, *max_y*) in " +"the `gpkg_tile_matrix_set " +"`__ table perfectly " +"matches the top left corner of the dataset, and the selected resolution " +"(*pixel_x_size*, *pixel_y_size*) at the computed maximum zoom_level of " +"the `gpkg_tile_matrix `__ " +"table will match the pixel width and height of the raster." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:312 +msgid "" +"However to ease interoperability with other implementations, and enable " +"use of GeoPackage with tile servicing software, it is possible to select " +"a predefined tiling scheme that has world coverage. The available tiling " +"schemes are :" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:317 +msgid "" +"*GoogleMapsCompatible*, as described in WMTS 1.0 specification, Annex " +"E.4. That tiling schemes consists of a single 256x256 tile at its zoom " +"level 0, in EPSG:3857 CRS, with extent in easting and northing in the " +"range [-20037508.34,20037508.34]." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:321 +msgid "" +"*InspireCRS84Quad*, as described in `Inspire View Services " +"`__." +" That tiling schemes consists of two 256x256 tiles at its zoom level 0, " +"in EPSG:4326 CRS, with extent in longitude in the range [-180,180] and in" +" latitude in the range [-90,90]." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:326 +msgid "" +"*PseudoTMS_GlobalGeodetic*, based on the `global-geodetic " +"`__ profile of OSGeo TMS (Tile Map Service) specification. This " +"has exactly the same definition as *InspireCRS84Quad* tiling scheme. Note" +" however that full interoperability with TMS is not possible due to the " +"origin of numbering of tiles being the top left corner in GeoPackage " +"(consistently with WMTS convention), whereas TMS uses the bottom left " +"corner as origin." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:334 +msgid "" +"*PseudoTMS_GlobalMercator*, based on the `global-mercator " +"`__ profile of OSGeo TMS (Tile Map Service) specification. That " +"tiling schemes consists of four 256x256 tiles at its zoom level 0, in " +"EPSG:3857 CRS, with extent extent in easting and northing in the range " +"[-20037508.34,20037508.34]. The same remark as with " +"PseudoTMS_GlobalGeodetic applies regarding interoperability with TMS." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:341 +msgid "" +"*GoogleCRS84Quad*, as described in `OGC 07-057r7 WMTS 1.0 " +"`__ " +"specification, Annex E.3. That tiling schemes consists of a single " +"256x256 tile at its zoom level 0, in EPSG:4326 CRS, with extent in " +"longitude and latitude in the range [-180,180]. Consequently, at zoom " +"level 0, 64 lines are unused at the top and bottom of that tile. This may" +" cause issues with some implementations of the specification, and there " +"are some ambiguities about the exact definition of this tiling scheme. " +"Using InspireCRS84Quad/PseudoTMS_GlobalGeodetic instead is therefore " +"recommended. NOTE: `OGC WMTS Simple Profile 13-082r2 " +"`__ changed " +"the definition of GoogleCRS84Quad (so not implemented by the driver). The" +" new definition includes a -1 level (that cannot be modeled in GeoPackage" +" given constraints on zoom_level being positive or 0), with a single tile" +" at origin -180,90 and whose bottom 128 lines are empty. Levels 0 or " +"greater are identical to the InspireCRS84Quad tiling scheme. So for " +"practical purposes, InspireCRS84Quad in GeoPackage is conformant to the " +"new GoogleCRS84Quad definition." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:362 +msgid "" +"In all the above tiling schemes, consecutive zoom levels defer by a " +"resolution of a factor of two." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:365 +msgid "" +"Starting with GDAL 3.2, it is also possible to use a Tile Matrix Set " +"definition, encoded as a JSON file, according to the `OGC Two Dimensional" +" Tile Matrix Set standard`_ Examples of such files can be found at " +"http://schemas.opengis.net/tms/1.0/json/examples/ The GDAL data directory" +" also contains files prefixed with ``tms_`` and with a ``.json`` " +"extension. If there is a ``tms_FOO.json`` file, then ``FOO`` can be used " +"as the value of the TILING_SCHEME creation option. There are restrictions" +" on the types of tile matrix set supported:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:373 +msgid "all zoom levels must have the same origin" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:374 +msgid "consecutive zoom levels defer by a resolution of a factor of two." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:375 +msgid "all zoom levels must have the same tile dimension" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:376 +msgid "variable matrix width tile set are not supported." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:381 +#: ../../source/drivers/raster/gtiff.rst:241 +msgid "Nodata value" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:383 +msgid "" +"The concept of the nodata value is only supported for tiled gridded " +"elevation datasets. For regular tiled rasters, the alpha band must rather" +" be used." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:387 +msgid "" +"For Float32 datasets with TIFF tiles, the concepts of nodata in GDAL and " +"null_value in the GeoPackage internals perfectly match." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:390 +msgid "" +"For Int16, UInt16 or Float32 with PNG tiles, GDAL will generally remap " +"the input nodata value to another value." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:393 +msgid "On writing, for PNG tiles, the behavior is the following one:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:396 +#: ../../source/drivers/raster/gpkg.rst:405 +#: ../../source/drivers/raster/gpkg.rst:415 +msgid "GDAL data type" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:396 +msgid "Input GDAL nodata value" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:396 +#: ../../source/drivers/raster/gpkg.rst:405 +#: ../../source/drivers/raster/gpkg.rst:415 +msgid "null_value in GPKG gpkg_2d_gridded_coverage_ancillary" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:397 +#: ../../source/drivers/raster/gpkg.rst:406 +#: ../../source/drivers/raster/gpkg.rst:407 +#: ../../source/drivers/raster/gpkg.rst:416 +msgid "Int16" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:397 +#: ../../source/drivers/raster/gpkg.rst:399 +msgid "Any" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:397 +#: ../../source/drivers/raster/gpkg.rst:399 +#: ../../source/drivers/raster/gpkg.rst:416 +#: ../../source/drivers/raster/gpkg.rst:418 +msgid "65535" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:398 +#: ../../source/drivers/raster/gpkg.rst:408 +#: ../../source/drivers/raster/gpkg.rst:417 +msgid "UInt16" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:398 +#: ../../source/drivers/raster/gpkg.rst:417 +msgid "X (if coverage offset == 0 and coverage scale == 1)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:398 +#: ../../source/drivers/raster/gpkg.rst:407 +#: ../../source/drivers/raster/gpkg.rst:408 +#: ../../source/drivers/raster/gpkg.rst:409 +#: ../../source/drivers/raster/gpkg.rst:417 +msgid "X" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:399 +#: ../../source/drivers/raster/gpkg.rst:409 +#: ../../source/drivers/raster/gpkg.rst:418 +msgid "Float32" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:402 +msgid "On reading, for PNG tiles, the behavior is the following one:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:405 +msgid "Exposed GDAL nodata value" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:406 +msgid ">= 32768" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:406 +#: ../../source/drivers/raster/gpkg.rst:416 +msgid "-32768" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:407 +msgid "X <= 32767" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:412 +msgid "Thus, perfect roundtripping is achieved in the following cases:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:415 +msgid "GDAL nodata value" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:502 +msgid "" +"Starting with GDAL 3.2, the value of TILING_SCHEME can also be the " +"filename of a JSON file according to the `OGC Two Dimensional Tile Matrix" +" Set standard`_, a URL to such file, the radical of a definition file in " +"the GDAL data directory (e.g. ``FOO`` for a file named ``tms_FOO.json``) " +"or the inline JSON definition. Note: the TILING_SCHEME option with a non-" +"CUSTOM value is best used with the gdal_translate utility / CreateCopy() " +"API operation. If used with gdalwarp, it requires setting the -tr switch " +"to the exact value expected by one zoom level of the tiling scheme." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:511 +msgid "" +"In non-CUSTOM mode, the actual resolution can be controlled with the " +":co:`ZOOM_LEVEL` or :co:`ZOOM_LEVEL_STRATEGY` options." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:625 +msgid "" +"gdaladdo / BuildOverviews() can be used to compute overviews. Power-of-" +"two overview factors (2,4,8,16,...) should be favored to be conformant " +"with the baseline GeoPackage specification. Use of other overview factors" +" will work with the GDAL driver, and cause the `gpkg_zoom_other " +"`__ " +"extension to be registered, but that could potentially cause " +"interoperability problems with other implementations that do not support " +"that extension." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:634 +#: ../../source/drivers/raster/mbtiles.rst:510 +msgid "" +"Overviews can also be cleared with the -clean option of gdaladdo (or " +"BuildOverviews() with nOverviews=0)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:640 +msgid "" +"GDAL uses the standardized `gpkg_metadata " +"`__ and " +"`gpkg_metadata_reference " +"`__ tables to " +"read and write metadata." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:646 +msgid "" +"GDAL metadata, from the default metadata domain and possibly other " +"metadata domains, is serialized in a single XML document, conformant with" +" the format used in GDAL PAM (Persistent Auxiliary Metadata) .aux.xml " +"files, and registered with md_scope=dataset and " +"md_standard_uri=http://gdal.org in gpkg_metadata. In " +"gpkg_metadata_reference, this entry is referenced with a " +"reference_scope=table and table_name={name of the raster table}" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:654 +msgid "" +"It is possible to read and write metadata that applies to the global " +"GeoPackage, and not only to the raster table, by using the *GEOPACKAGE* " +"metadata domain." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:658 +#: ../../source/drivers/vector/gpkg.rst:543 +msgid "" +"Metadata not originating from GDAL can be read by the driver and will be " +"exposed as metadata items with keys of the form GPKG_METADATA_ITEM_XXX " +"and values the content of the *metadata* columns of the gpkg_metadata " +"table. Update of such metadata is not currently supported through GDAL " +"interfaces ( although it can be through direct SQL commands)." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:664 +#: ../../source/drivers/vector/gpkg.rst:549 +msgid "" +"The specific DESCRIPTION and IDENTIFIER metadata item of the default " +"metadata domain can be used in read/write to read from/update the " +"corresponding columns of the gpkg_contents table." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:668 +msgid "" +"You can set the CREATE_METADATA_TABLES configuration option to NO to " +"avoid creating and filling the metadata tables." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:672 +msgid "IMAGE_STRUCTURE metadata item" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:676 +msgid "" +"Implementation details, normally transparent to GDAL users, but useful " +"for other implementations." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:679 +msgid "" +"Starting with GDAL 3.6.1, the following optional metadata items can be " +"read and write into the ``IMAGE_STRUCTURE`` metadata domain, in the " +"```` XML element:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:683 +msgid "" +"BAND_COUNT=1, 2, 3 or 4. Applies only for Byte data. Set when creating a " +"dataset so that GDAL knows the number of bands when reopening it." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:686 +msgid "" +"COLOR_TABLE={{r0,g0,b0,a0},...{r255,g255,b255,a255}}. Applies only for " +"Byte data and a single band dataset. Set when creating a dataset from a " +"source dataset that has a color table." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:690 +msgid "" +"TILE_FORMAT=PNG/PNG8/PNG_JPEG/JPEG/WEBP. Set when creating a dataset so " +"that GDAL knows the tile format when reopening it, for updates." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:693 +msgid "NODATA_VALUE=integer between 0 and 255. Applies only for Byte data." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:696 +#: ../../source/drivers/raster/netcdf.rst:351 +#: ../../source/drivers/raster/nitf_advanced.rst:328 +#: ../../source/drivers/raster/vrt.rst:562 +#: ../../source/drivers/vector/geojson.rst:510 +#: ../../source/drivers/vector/gml.rst:1334 +#: ../../source/drivers/vector/jsonfg.rst:220 +#: ../../source/drivers/vector/s57.rst:227 +msgid "Example:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:712 +#: ../../source/drivers/vector/gpkg.rst:648 +msgid "Level of support of GeoPackage Extensions" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:714 +msgid "(Restricted to those have a raster scope)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:716 +#: ../../source/drivers/vector/gpkg.rst:652 +msgid "Extensions" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:719 +#: ../../source/drivers/vector/gpkg.rst:655 +msgid "Extension name" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:720 +#: ../../source/drivers/vector/gpkg.rst:656 +msgid "OGC adopted extension ?" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:721 +#: ../../source/drivers/vector/gpkg.rst:657 +msgid "Supported by GDAL?" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:722 +msgid "" +"`Zoom Other intervals " +"`__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:723 +#: ../../source/drivers/raster/gpkg.rst:724 +#: ../../source/drivers/raster/gpkg.rst:726 +#: ../../source/drivers/raster/gpkg.rst:727 +#: ../../source/drivers/raster/gpkg.rst:729 +#: ../../source/drivers/raster/gpkg.rst:730 +#: ../../source/drivers/raster/gpkg.rst:732 +#: ../../source/drivers/raster/gpkg.rst:735 +#: ../../source/drivers/vector/gpkg.rst:659 +#: ../../source/drivers/vector/gpkg.rst:662 +#: ../../source/drivers/vector/gpkg.rst:663 +#: ../../source/drivers/vector/gpkg.rst:665 +#: ../../source/drivers/vector/gpkg.rst:666 +#: ../../source/drivers/vector/gpkg.rst:668 +#: ../../source/drivers/vector/gpkg.rst:671 +#: ../../source/drivers/vector/gpkg.rst:680 +msgid "Yes" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:725 +msgid "" +"`Tiles Encoding WebP " +"`__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:728 +#: ../../source/drivers/vector/gpkg.rst:664 +msgid "`Metadata `__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:731 +#: ../../source/drivers/vector/gpkg.rst:670 +msgid "" +"`WKT for Coordinate Reference Systems " +"`__ (WKT " +"v2)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:733 +msgid "" +"Partially, since GDAL 2.2. GDAL can read databases using this extension. " +"GDAL 3.0 brings support for the WKT v2 entry." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:734 +msgid "" +"`Tiled Gridded Coverage Data " +"`__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:736 +msgid "" +"Yes, since GDAL 2.3 (GDAL 2.2 supported a preliminary version of this " +"extension)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:741 +msgid "" +"Simple translation of a GeoTIFF into GeoPackage. The table 'byte' will be" +" created with the tiles." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:748 +msgid "Translation of a GeoTIFF into GeoPackage using WebP tiles" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:754 +msgid "" +"Translation of a GeoTIFF into GeoPackage using GoogleMapsCompatible " +"tiling scheme (with reprojection and resampling if needed)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:761 +msgid "Building of overviews of an existing GeoPackage, and forcing JPEG tiles" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:768 +msgid "" +"Addition of a new subdataset to an existing GeoPackage, and choose a non " +"default name for the raster table." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:775 +msgid "Reprojection of an input dataset to GeoPackage" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:781 +msgid "Open a specific raster table in a GeoPackage" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:790 +msgid "Raster SQL functions" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:792 +msgid "" +"The raster SQL functions mentioned at " +":ref:`sql_sqlite_dialect_raster_functions` are also available." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:795 +msgid "" +"The ``gdal_get_layer_pixel_value()`` function (added in GDAL 3.7), " +"variant of the generic ``gdal_get_pixel_value()``, can be used to extract" +" the value of a pixel in a raster layer of the current dataset." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:799 +msgid "It takes 5 arguments:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:801 +msgid "a string with the layer/table name" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:802 +msgid "a band number (numbering starting at 1)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:803 +msgid "" +"a string being \"georef\" to indicate that subsequent values will be " +"georeferenced coordinates, or \"pixel\" to indicate that subsequent " +"values will be in column, line pixel space" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:806 +msgid "georeferenced X value or column number" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:807 +msgid "georeferenced Y value or line number" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:817 +msgid ":ref:`GeoPackage vector ` documentation page" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:818 +#: ../../source/drivers/vector/gpkg.rst:812 +msgid "" +"`Getting Started With GeoPackage `__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:820 +#: ../../source/drivers/vector/gpkg.rst:814 +msgid "" +"`OGC GeoPackage format standard `__ " +"specification, HTML format (current/development version of the standard)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:823 +#: ../../source/drivers/vector/gpkg.rst:817 +msgid "" +"`OGC GeoPackage Encoding Standard " +"`__ page" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:825 +#: ../../source/drivers/vector/gpkg.rst:819 +msgid "`SQLite `__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:826 +msgid ":ref:`PNG driver ` documentation page" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:827 +msgid ":ref:`JPEG driver ` documentation page" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:828 +msgid ":ref:`WEBP driver ` documentation page" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:829 +msgid "" +"`OGC 07-057r7 WMTS 1.0 " +"`__ " +"specification" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:832 +msgid "" +"`OSGeo TMS (Tile Map Service) " +"`__ " +"specification" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:837 +#: ../../source/drivers/vector/selafin.rst:413 +msgid "Other notes" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:839 +msgid "" +"Development of raster support in the GeoPackage driver was financially " +"supported by `Safe Software `__." +msgstr "" + +#: ../../source/drivers/raster/grass.rst:6 +#: ../../source/drivers/vector/grass.rst:6 +msgid "GRASS" +msgstr "" + +#: ../../source/drivers/raster/grass.rst:10 +msgid "" +"The GDAL-GRASS driver can read GRASS GIS raster maps. The driver is " +"maintained at the `GDAL-GRASS GIS driver repository " +"`__." +msgstr "" + +#: ../../source/drivers/raster/grass.rst:13 +msgid "" +"For the driver documentation, please visit the `GDAL-GRASS GIS raster " +"driver page `__." +msgstr "" + +#: ../../source/drivers/raster/grass.rst:20 +#: ../../source/drivers/vector/grass.rst:20 +msgid "`GRASS GIS home page `__" +msgstr "" + +#: ../../source/drivers/raster/grassasciigrid.rst:5 +msgid "GRASSASCIIGrid -- GRASS ASCII Grid" +msgstr "" + +#: ../../source/drivers/raster/grassasciigrid.rst:7 +msgid "GRASSASCIIGrid" +msgstr "" + +#: ../../source/drivers/raster/grassasciigrid.rst:11 +msgid "" +"Supports reading GRASS ASCII grid format (similar to Arc/Info ASCIIGRID " +"command)." +msgstr "" + +#: ../../source/drivers/raster/grassasciigrid.rst:14 +msgid "" +"By default, the datatype returned for GRASS ASCII grid datasets by GDAL " +"is autodetected, and set to Float32 for grid with floating point values " +"or Int32 otherwise. This is done by analysing the format of the null " +"value and the first 100k bytes of data of the grid. You can also " +"explicitly specify the datatype by setting the GRASSASCIIGRID_DATATYPE " +"configuration option (Int32, Float32 and Float64 values are supported " +"currently)" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:5 +msgid "GRIB -- WMO General Regularly-distributed Information in Binary form" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:7 +msgid "GRIB" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:11 +msgid "" +"GDAL supports GRIB1 (reading) and GRIB2 (reading and writing) format " +"raster data, with support for common coordinate system, georeferencing " +"and other metadata. GRIB format is commonly used for distribution of " +"Meteorological information, and is propagated by the World Meteorological" +" Organization." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:17 +msgid "" +"The GDAL GRIB driver is based on a modified version of the degrib " +"application which is written primarily by Arthur Taylor of NOAA NWS NDFD " +"(MDL). The degrib application (and the GDAL GRIB driver) are built on the" +" g2clib grib decoding library written primarily by John Huddleston of " +"NOAA NWS NCEP." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:23 +msgid "" +"GRIB2 files without projection on lon/lat grids have the peculiarity of " +"using longitudes in the [0,360] range and wrapping around the " +"antimeridian as opposed to the usual wrapping around the prime meridian " +"of other raster datasets. Starting with GDAL 3.4.0, when reading such " +"files, a transparent conversion of the longitudes to [-180,180] will be " +"performed and the data will be rewrapped around the prime meridian - the " +"split&swap mode. This behavior can be disabled by setting the " +":config:`GRIB_ADJUST_LONGITUDE_RANGE` configuration option to `NO`." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:32 +msgid "" +"There are several encoding schemes for raster data in GRIB format. Most " +"common ones should be supported including PNG encoding. JPEG2000 encoded " +"GRIB files will generally be supported if GDAL is also built with " +"JPEG2000 support via one of the GDAL JPEG2000 drivers." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:37 +msgid "" +"GRIB files may a be represented in GDAL as having many bands, with some " +"sets of bands representing a time sequence. GRIB bands are represented as" +" Float64 (double precision floating point) regardless of the actual " +"values. GRIB metadata is captured as per-band metadata and used to set " +"band descriptions, similar to this:" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:54 +msgid "" +"GRIB2 files may also include an extract of other metadata, such as the " +"`identification section " +"`__," +" `product definition " +"`__" +" template number (GRIB_PDS_PDTN, octet 8-9), and the product definition " +"template values (GRIB_PDS_TEMPLATE_NUMBERS, octet 10+) as metadata like " +"this:" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:71 +msgid "" +"GRIB_DISCIPLINE was added in GDAL 2.3.0 and is the `Discipline " +"`__" +" field of the Section 0 of the message." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:75 +msgid "" +"GRIB_IDS was added in GDAL 2.3.0 and is the `identification section " +"`__" +" / Section 1 of the message." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:79 +msgid "" +"GRIB_PDS_TEMPLATE_ASSEMBLED_VALUES was added in GDAL 2.3.0, and use " +"template definitions to assemble several bytes that make a template item " +"into a 16 or 32 bit signed/unsigned integers, whereas " +"GRIB_PDS_TEMPLATE_NUMBERS expose raw bytes" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:96 +msgid "" +"|about-config-options| This paragraph lists the configuration options " +"that can be set to alter the default behavior of the GRIB driver." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:127 +#: ../../source/drivers/raster/rmf.rst:46 +#: ../../source/drivers/raster/s102.rst:38 +#: ../../source/drivers/raster/s104.rst:39 +#: ../../source/drivers/raster/s111.rst:43 +#: ../../source/drivers/raster/stacit.rst:44 +#: ../../source/drivers/raster/stacta.rst:58 +#: ../../source/drivers/vector/csv.rst:268 +#: ../../source/drivers/vector/csw.rst:52 +#: ../../source/drivers/vector/elasticsearch.rst:40 +#: ../../source/drivers/vector/esrijson.rst:62 +#: ../../source/drivers/vector/flatgeobuf.rst:43 +#: ../../source/drivers/vector/gml.rst:504 +#: ../../source/drivers/vector/gmlas.rst:188 +#: ../../source/drivers/vector/hana.rst:63 +#: ../../source/drivers/vector/jsonfg.rst:99 +#: ../../source/drivers/vector/oci.rst:294 +#: ../../source/drivers/vector/odbc.rst:64 +#: ../../source/drivers/vector/openfilegdb.rst:105 +#: ../../source/drivers/vector/osm.rst:225 +#: ../../source/drivers/vector/parquet.rst:34 +#: ../../source/drivers/vector/pg.rst:156 +#: ../../source/drivers/vector/pgeo.rst:72 +#: ../../source/drivers/vector/shapefile.rst:279 +#: ../../source/drivers/vector/sqlite.rst:243 +msgid "|about-open-options| The following open options are supported:" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:152 +msgid "GRIB2 write support" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:154 +msgid "" +"GRIB2 write support is available since GDAL 2.3.0, through the " +"CreateCopy() / gdal_translate interface." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:157 +msgid "" +"Each band of the input dataset is translated as a GRIB2 message, and all " +"of them are concatenated in a single file, conforming to the usual " +"practice." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:161 +msgid "" +"The input dataset must be georeferenced, and the supported projections " +"are: Geographic Longitude/Latitude, Mercator 1SP/2SP, Transverse " +"Mercator, Polar Stereographic, Lambert Conformal Conic 1SP/2SP, Albers " +"Conic Equal Area and Lambert Azimuthal Equal Area." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:166 +msgid "" +"A number of creation options are available as detailed in below sections." +" Those creation options are valid for all bands. But it is possible to " +"override those global settings in a per-band way, by defining creation " +"options that use the same key and are prefixed by BAND_X\\_ where X is " +"the band number between 1 and the total number of bands. For example " +"BAND_1_PDS_PDTN" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:174 +msgid "Product identification and definition" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:176 +msgid "" +"Users are strongly advised to provide necessary information to " +"appropriately fill the `Section 0 / \"Indicator\" " +"`__," +" `Section 1 / \"Identification section\" " +"`__" +" and `Section 4 / \"Product definition section\" " +"`__" +" with the following creation options. Otherwise, GDAL will fill with " +"default values, but readers might have trouble exploiting GRIB2 datasets " +"generating with those defaults. |about-creation-options|" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:195 +msgid "0: Meteorological Products. Default value" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:196 +msgid "1: Hydrological Products" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:197 +msgid "2: Land Surface Products" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:198 +msgid "3, 4: Space Products" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:199 +msgid "10: Oceanographic Product" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:318 +msgid "Data encoding" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:320 +msgid "" +"In GRIB2, a number of data encoding schemes exist (see `Section 5 / " +"\"Data representation section\" " +"`__)." +" By default, GDAL will select an appropriate data encoding that will " +"preserve the range of input data. with the :co:`DATA_ENCODING`, " +":co:`NBITS`, :co:`DECIMAL_SCALE_FACTOR`, :co:`JPEG2000_DRIVER`, " +":co:`COMPRESSION_RATIO` and :co:`SPATIAL_DIFFERENCING_ORDER` creation " +"options." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:328 +msgid "Users can override those defaults with the following creation options are:" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:338 +msgid "" +"In AUTO mode, COMPLEX_PACKING is selected if input band has a nodata " +"value. Otherwise if input band datatype is Float32 or Float64, " +"IEEE_FLOATING_POINT is selected. Otherwise SIMPLE_PACKING is selected." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:342 +msgid "" +"`SIMPLE_PACKING " +"`__:" +" use integer representation internally, with offset and decimal and/or " +"binary scaling. So can be used for any datatype." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:345 +msgid "" +"COMPLEX_PACKING: evolution of SIMPLE_PACKING with nodata handling. By " +"default, a `non-spatial differencing encoding is used " +"`__," +" but if SPATIAL_DIFFERENCING_ORDER=1 or 2, `complex packing with spatial " +"differencing " +"`__" +" is used" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:352 +msgid "" +"`IEEE_FLOATING_POINT " +"`__:" +" store values as IEEE-754 single or double precision numbers." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:354 +msgid "" +"`PNG " +"`__:" +" uses the same preparation steps as SIMPLE_PACKING but with PNG encoding " +"of the integer values." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:357 +msgid "" +"`JPEG2000 " +"`__:" +" uses the same preparation steps as SIMPLE_PACKING but with JPEG2000 " +"encoding of the integer values." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:414 +msgid "Data units" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:416 +msgid "" +"Internally GRIB stores values in the units of the international system " +"(ie Metric system). So temperatures must be stored as Kelvin degrees. But" +" on the reading side of the driver, fields with temperatures are exposed " +"in Celsius degrees (unless the :config:`GRIB_NORMALIZE_UNITS` " +"configuration option is set to NO). For consistency, the writing side of " +"the driver also assumed that temperature (detected if the first value of " +"a product definition template, ie the *Parameter category* is " +"0=Temperature) values in the input dataset will be in Celsius degrees, " +"and will automatically offset them to Kelvin degrees. It is possible to " +"control that behavior using the :co:`INPUT_UNIT` creation option:" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:435 +msgid "GRIB2 to GRIB2 conversions" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:437 +msgid "" +"If GRIB2 to GRIB2 translation is done with gdal_translate (or " +"CreateCopy()), the GRIB_DISCIPLINE, GRIB_IDS, GRIB_PDS_PDTN and " +"GRIB_PDS_TEMPLATE_NUMBERS metadata items of the bands of the source " +"dataset are used by default (unless creation options override them)." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:442 +msgid "" +"DECIMAL_SCALE_FACTOR and NBITS will also be attempted to be retrieved " +"from the GRIB special metadata domain." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:458 +msgid "" +"`NOAA NWS NDFD \"degrib\" GRIB2 Decoder " +"`__" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:460 +msgid "" +"`NOAA NWS NCEP g2clib grib decoding library " +"`__" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:462 +msgid "" +"`WMO GRIB1 Format Documents `__" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:464 +msgid "" +"`NCEP WMO GRIB2 Documentation " +"`__" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:468 +#: ../../source/drivers/raster/openfilegdb.rst:105 +#: ../../source/drivers/raster/postgisraster.rst:121 +#: ../../source/drivers/raster/sentinel2.rst:464 +#: ../../source/drivers/vector/gml.rst:1380 +#: ../../source/drivers/vector/gmlas.rst:479 +#: ../../source/drivers/vector/jml.rst:94 +#: ../../source/drivers/vector/netcdf.rst:506 +#: ../../source/drivers/vector/oci.rst:357 +#: ../../source/drivers/vector/openfilegdb.rst:374 +#: ../../source/drivers/vector/sqlite.rst:588 +msgid "Credits" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:470 +msgid "" +"Support for GRIB2 write capabilities has been funded by Meteorological " +"Service of Canada." +msgstr "" + +#: ../../source/drivers/raster/gs7bg.rst:5 +msgid "GS7BG -- Golden Software Surfer 7 Binary Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/gs7bg.rst:7 +msgid "GS7BG" +msgstr "" + +#: ../../source/drivers/raster/gs7bg.rst:11 +msgid "" +"This is the binary (non-human-readable) version of one of the raster " +"formats used by Golden Software products (such as the Surfer series). " +"This format differs from the :ref:`raster.gsbg` format (also known as " +"Surfer 6 binary grid format), it is more complicated and flexible." +msgstr "" + +#: ../../source/drivers/raster/gs7bg.rst:16 +msgid "NOTE: Implemented as :source_file:`frmts/gsg/gs7bgdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/gsag.rst:5 +msgid "GSAG -- Golden Software ASCII Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/gsag.rst:7 +msgid "GSAG" +msgstr "" + +#: ../../source/drivers/raster/gsag.rst:11 +msgid "" +"This is the ASCII-based (human-readable) version of one of the raster " +"formats used by Golden Software products (such as the Surfer series). " +"This format is supported for both reading and writing (copy mode only). " +"Currently the associated formats for color, metadata, and shapes are not " +"supported." +msgstr "" + +#: ../../source/drivers/raster/gsag.rst:17 +msgid "NOTE: Implemented as :source_file:`frmts/gsg/gsagdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/gsbg.rst:5 +msgid "GSBG -- Golden Software Binary Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/gsbg.rst:7 +msgid "GSBG" +msgstr "" + +#: ../../source/drivers/raster/gsbg.rst:11 +msgid "" +"This is the binary (non-human-readable) version of one of the raster " +"formats used by Golden Software products (such as the Surfer series). " +"Like the ASCII version, this format is supported for both reading and " +"writing (including create, delete, and copy). Currently the associated " +"formats for color, metadata, and shapes are not supported." +msgstr "" + +#: ../../source/drivers/raster/gsbg.rst:17 +msgid "" +"Surfer 8 uses a fixed nodata value at 1.701410009187828e+38. When writing" +" a GSBG dataset, GDAL remaps the user-specified input nodata value to " +"1.701410009187828e+38." +msgstr "" + +#: ../../source/drivers/raster/gsbg.rst:20 +msgid "NOTE: Implemented as :source_file:`frmts/gsg/gsbgdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/gsc.rst:5 +msgid "GSC -- GSC Geogrid" +msgstr "" + +#: ../../source/drivers/raster/gsc.rst:7 +msgid "GSC" +msgstr "" + +#: ../../source/drivers/raster/gsc.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/raw/gscdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/gta.rst:5 +msgid "GTA - Generic Tagged Arrays" +msgstr "" + +#: ../../source/drivers/raster/gta.rst:7 +msgid "GTA" +msgstr "" + +#: ../../source/drivers/raster/gta.rst:11 +msgid "GDAL can read and write GTA data files through the libgta library." +msgstr "" + +#: ../../source/drivers/raster/gta.rst:14 +msgid "" +"GTA is a file format that can store any kind of multidimensional array " +"data, allows generic manipulations of array data, and allows easy " +"conversion to and from other file formats." +msgstr "" + +#: ../../source/drivers/raster/gta.rst:41 +msgid "`GTA home page `__" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:5 +msgid "GTI -- GDAL Raster Tile Index" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:9 +msgid "GTI" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:14 +#: ../../source/drivers/raster/vrt.rst:12 +#: ../../source/drivers/vector/geopackage_aspatial.rst:18 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:16 +msgid "Introduction" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:16 +msgid "" +"The GTI driver is a driver that allows to handle catalogs with a large " +"number of raster files (called \"tiles\" in the rest of this document, " +"even if a regular tiling is not required by the driver), and build a " +"virtual mosaic from them. Each tile may be in any GDAL supported raster " +"format, and be a file stored on a regular filesystem, or any GDAL " +"supported virtual filesystem (for raster drivers that support such " +"files)." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:23 +msgid "" +"This driver offers similar functionality as the :ref:`VRT ` " +"driver with the following main differences:" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:26 +msgid "" +"The tiles are listed as features of any GDAL supported vector format. Use" +" of formats with efficient spatial filtering is recommended, such as " +":ref:`GeoPackage `, :ref:`FlatGeoBuf ` or" +" :ref:`PostGIS `. The GTI driver can thus use a larger number " +"of tiles than the VRT driver (hundreds of thousands or more), provided " +"the underlying vector format is efficient." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:33 +msgid "" +"The tiles may have different SRS. The GTI driver is capable of on-the-fly" +" reprojection" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:36 +msgid "" +"The GTI driver offers control on the order in which tiles are composited," +" when they overlap (z-order)" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:39 +msgid "" +"The GTI driver honours the mask/alpha band when compositing together " +"overlapping tiles." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:42 +msgid "" +"Contrary to the VRT driver, the GTI driver does not enable to alter " +"characteristics of referenced tiles, such as their georeferencing, nodata" +" value, etc. If such behavior is desired, the tiles must be for example " +"wrapped individually in a VRT file before being referenced in the GTI " +"index." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:48 +#: ../../source/drivers/vector/mvt.rst:64 +msgid "Connection strings" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:50 +msgid "The GTI driver accepts different types of connection strings:" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:52 +msgid "" +"a vector file in GeoPackage format with a ``.gti.gpkg`` extension, or in " +"FlatGeoBuf format with a ``.gti.fgb`` extension, meeting the minimum " +"requirements for a GTI compatible tile index, detailed later." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:56 +msgid "For example: ``tileindex.gti.gpkg``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:58 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if GTI`` option to command " +"line utilities accepting it, or ``GTI`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename if its extension is just ``.gpkg`` or " +"``.fgb``." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:63 +msgid "" +"any vector file in a GDAL supported format, with its filename (or " +"connection string prefixed with ``GTI:``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:66 +msgid "" +"For example: ``GTI:tileindex.shp`` or ``GTI:PG:database=my_db " +"schema=tileindex``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:68 +msgid "" +"a XML file, following the below GTI XML format, generally with the " +"recommended ``.gti`` extension, referencing a vector file. Using such XML" +" file may be more practical for tile indexes not stored in a file, or if " +"some additional metadata must be defined at the dataset or band level of " +"the virtual mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:74 +msgid "For example: ``tileindex.gti``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:77 +msgid "Tile index requirements" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:79 +msgid "" +"The minimum requirements for a GTI compatible tile index is to be a " +"vector format supported by GDAL, with a geometry column storing polygons " +"with the extent of the tiles, and an attribute field of type string, " +"storing the path to each tile. The default name for this attribute field " +"is ``location``. If relative filenames are stored in the tile index, they" +" are considered to be relative to the path of the tile index." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:86 +msgid "" +"In addition, for formats that can store layer metadata (GeoPackage, " +"FlatGeoBuf, PostGIS, ...), the following layer metadata items may be set:" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:89 +msgid "" +"``RESX=`` and ``RESY=``: resolution along X and Y axis, in " +"SRS units / pixel." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:92 +msgid "" +"Setting those metadata items is recommended, otherwise the driver will " +"try to open one of the tiles referenced in the tile index, and use its " +"resolution as the resolution for the mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:96 +msgid "" +"``BAND_COUNT=``: number of bands of the virtual mosaic. The tiles " +"stored in an index should generally have the same number of bands." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:99 +msgid "" +"Setting that metadata item is recommended, otherwise the driver will try " +"to open one of the tiles referenced in the tile index, and use it as the " +"number of bands for the mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:103 +msgid "" +"A mix of tiles with N and N+1 bands is allowed, provided that the color " +"interpretation of the (N+1)th band is alpha. The N+1 value must be " +"written as the band count in that situation." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:107 +msgid "" +"If tiles contains a single band with a color table, and that the color " +"table may differ among tiles, BAND_COUNT should be set to 3 (resp. 4) to " +"perform expansion to Red, Green, Blue components (resp. Red, Green, Blue," +" Alpha). If the color table is identical between the tiles, and it is " +"desired to preserve it, the VRRTI XML file format may be used to include " +"the ColorTable element." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:115 +msgid "" +"``DATA_TYPE=``: data type of the tiles of the tile index ``Byte``, " +"``Int8``, ``UInt16``, ``Int16``, ``UInt32``, ``Int32``, ``UInt64``, " +"``Int64``, ``Float32``, ``Float64``, ``CInt16``, ``CInt32``, ``CFloat32``" +" or ``CFloat64``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:120 +msgid "" +"Setting that metadata item is recommended, otherwise the driver will try " +"to open one of the tiles referenced in the tile index, and use it as the " +"data type for the mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:124 +msgid "" +"``NODATA=[,``, ``MINY=``, ``MAXX=`` and " +"``MAXY=``: defines the extent of the virtual mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:132 +msgid "" +"For vector formats that have efficient retrieval of the layer extent, " +"setting those items is not needed." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:135 +msgid "" +"``GEOTRANSFORM=,,,,,``: defines the " +"GeoTransform. Used together with ``XSIZE`` and ``YSIZE``, this is an " +"alternate way of defining the extent and resolution os the virtual " +"mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:139 +msgid "" +"It is not necessary to define this item if ``RESX=`` and ``RESY`` are set" +" (potentially accompanied with ``MINX``, ``MINY``, ``MAXX`` and ``MAXY``)" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:142 +msgid "``XSIZE=``, ``YSIZE=``: size of the virtual mosaic in pixel." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:144 +msgid "" +"``COLOR_INTERPRETATION=[,``: defines the SRS of the virtual mosaic, using any value " +"supported by the :cpp:func:`OGRSpatialReference::SetFromUserInput` call, " +"which includes EPSG Projected, Geographic or Compound CRS (i.e. " +"EPSG:4296), a well known text (WKT) CRS definition, PROJ.4 declarations, " +"etc." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:153 +msgid "" +"It is not necessary to define this element if the virtual mosaic SRS is " +"recorded as the SRS of the vector layer of the tile index." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:156 +msgid "" +"``LOCATION_FIELD=``: name of the field where the tile location is" +" stored. Defaults to ``location``." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:159 +msgid "" +"``SORT_FIELD=``: name of a field to use to control the order in " +"which tiles are composited, when they overlap (z-order). That field may " +"be of type String, Integer, Integer64, Date or DateTime. By default, the " +"higher the value in that field, the last the corresponding tile will be " +"rendered in the virtual mosaic (unless SORT_FIELD_ASC=NO is set)" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:165 +msgid "" +"``SORT_FIELD_ASC=YES|NO``: whether the values in SORT_FIELD should be " +"sorted in ascendent or descent order. Defaults to YES (ascendent)" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:168 +msgid "" +"``BLOCKXSIZE=`` and ``BLOCKYSIZE=``: Block size of bands of the" +" virtual mosaic. Defaults to 256x256." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:171 +msgid "" +"``MASK_BAND=YES|NO``: whether a dataset-level mask band should be " +"exposed. Defaults to NO." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:174 +msgid "" +"``RESAMPLING=``: Resampling method to use for on-the-fly " +"reprojection, or rendering of tiles whose origin coordinates are not at " +"an offset multiple of the resolution of the mosaic compared to the origin" +" of the mosaic. In that later case, RESAMPLING is only taken into account" +" when requesting pixels with the default nearest resampling mode." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:180 +msgid "" +"Possible values: ``nearest``, ``cubic``, ``cubicspline``, ``lanczos``, " +"``average``, ``rms``, ``gauss``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:182 +msgid "Defaults to ``nearest``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:184 +msgid "" +"``BAND__OFFSET=`` where number is an integer index starting " +"at 1." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:186 +msgid "Additive offset to apply to the raw numbers of the band." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:188 +msgid "" +"``BAND__SCALE=`` where number is an integer index starting " +"at 1." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:190 +msgid "Multiplicative factor to apply to the raw numbers of the band." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:192 +msgid "" +"``BAND__UNITTYPE=`` where number is an integer index " +"starting at 1." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:194 +msgid "Unit of the band." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:196 +msgid "" +"``OVERVIEW__DATASET=`` where idx is an integer index " +"starting at 0." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:198 +msgid "" +"Name of the dataset to use as the first overview level. This may be a " +"raster dataset (for example a GeoTIFF file, or another GTI dataset). This" +" may also be a vector dataset with a GTI compatible layer, potentially " +"specified with ``OVERVIEW__LAYER``." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:203 +msgid "" +"``OVERVIEW__OPEN_OPTIONS=[,key2=value2]...`` where idx " +"is an integer index starting at 0." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:205 +msgid "Open options(s) to use to open ``OVERVIEW__DATASET``." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:207 +msgid "" +"``OVERVIEW__LAYER=`` where idx is an integer index starting " +"at 0." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:209 +msgid "" +"Name of the vector layer to use as the first overview level, assuming " +"``OVERVIEW__DATASET`` points to a vector dataset. " +"``OVERVIEW__DATASET`` may also not be specified, in which case the " +"vector dataset of the full resolution virtual mosaic is used." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:214 +msgid "" +"``OVERVIEW__FACTOR=`` where idx is an integer index starting at" +" 0." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:216 +msgid "" +"Sub-sampling factor, strictly greater than 1. If " +"``OVERVIEW__DATASET`` and ``OVERVIEW__LAYER`` are not " +"specified, then all tiles of the full resolution virtual mosaic are used," +" with the specified sub-sampling factor (it is recommended, but not " +"required, that those tiles do have a corresponding overview). " +"``OVERVIEW__DATASET`` and/or ``OVERVIEW__LAYER`` may also be " +"specified to point to another tile index." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:223 +msgid "" +"All overviews *must* have exactly the same extent as the full resolution " +"virtual mosaic. The GTI driver does not check that, and if that condition" +" is not met, subsampled pixel request will lead to incorrect result." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:227 +msgid "" +"In addition to those layer metadata items, the dataset-level metadata " +"item ``TILE_INDEX_LAYER`` may be set to indicate, for dataset with " +"multiple layers, which one should be used as the tile index layer." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:231 +msgid "" +"Alternatively to setting those metadata items individually, the " +"corresponding information can be grouped together in a GTI XML document, " +"attached in the ``xml:GTI`` metadata domain of the layer (for drivers " +"that support alternate metadata domains such as GeoPackage)" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:237 +msgid "GTI XML format" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:239 +msgid "" +"A `XML schema of the GDAL GTI format " +"`_" +" is available." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:242 +msgid "" +"The following artificial example contains all potential elements and " +"attributes. A number of them have similar name and same semantics as " +"layer metadata items mentioned in the previous section." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:334 +msgid "At the GDALTileIndexDataset level, the elements specific to GTI XML are:" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:336 +msgid "" +"``Filter``: value of a SQL WHERE clause, used to select a subset of the " +"features of the index." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:339 +msgid "" +"``BlockXSize`` / ``BlockYSize``: dimension of the block size of bands. " +"Defaults to 256x256" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:342 +msgid "" +"``Metadata``: defines dataset-level metadata. You can refer to the " +"documentation of the :ref:`VRT ` driver for its syntax." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:345 +msgid "" +"At the Band level, the elements specific to GTI XML are: Description, " +"Offset, Scale, UnitType, ColorTable, CategoryNames, " +"GDALRasterAttributeTable, Metadata. You can refer to the documentation of" +" the :ref:`VRT ` driver for their syntax and semantics." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:353 +msgid "How to build a GTI comptatible index ?" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:355 +msgid "" +"The :ref:`gdaltindex` program may be used to generate both a vector tile " +"index, and optionally a wrapping .gti XML file." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:358 +msgid "" +"A GTI comptatible index may also be created by any programmatic means, " +"provided the above format specifications are met." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:365 +msgid "" +"|about-open-options| The following open options are available. Most of " +"them can be also defined as layer metadata items or in the .gti XML file" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:5 +msgid "GTiff -- GeoTIFF File Format" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:7 +msgid "GTiff" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:11 +msgid "" +"Most forms of TIFF and GeoTIFF files are supported by GDAL for reading, " +"and somewhat less varieties can be written." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:14 +msgid "" +"GDAL also supports reading and writing BigTIFF files (evolution of the " +"TIFF format to support files larger than 4 GB)." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:17 +msgid "" +"Currently band types of Byte, UInt16, Int16, UInt32, Int32, Float32, " +"Float64, CInt16, CInt32, CFloat32 and CFloat64 are supported for reading " +"and writing. Paletted images will return palette information associated " +"with the band. The compression formats listed below should be supported " +"for reading as well." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:23 +msgid "" +"As well, one bit files, and some other unusual formulations of GeoTIFF " +"file, such as YCbCr color model files, are automatically translated into " +"RGBA (red, green, blue, alpha) form, and treated as four eight bit bands." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:42 +msgid "" +"Most GeoTIFF projections should be supported, with the caveat that in " +"order to translate uncommon Projected, and Geographic coordinate systems " +"into OGC WKT it is necessary to have the PROJ proj.db database available." +" It must be found at the location pointed to by the PROJ_LIB environment " +"variable, or at one of the locations set programmatically via " +"OSRSetPROJSearchPaths()." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:49 +msgid "" +"Georeferencing from GeoTIFF is supported in the form of one tiepoint and " +"pixel size, a transformation matrix, or a list of GCPs." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:52 +msgid "" +"If no georeferencing information is available in the TIFF file itself, " +"GDAL will also check for, and use an ESRI :ref:`world file ` " +"with the extension .tfw, .tifw/.tiffw or .wld, as well as a MapInfo .tab " +"file." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:57 +msgid "" +"By default, information is fetched in following order (first listed is " +"the highest priority): PAM (Persistent Auxiliary metadata) .aux.xml " +"sidecar file, INTERNAL (GeoTIFF keys and tags), TABFILE (.tab), WORLDFILE" +" (.tfw, .tifw/.tiffw or .wld), XML (.xml)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:62 +msgid "" +"Starting with GDAL 2.2, the allowed sources and their priority order can " +"be changed with the :config:`GDAL_GEOREF_SOURCES` configuration option " +"(or :oo:`GEOREF_SOURCES` open option) whose value is a comma-separated " +"list of the following keywords : PAM, INTERNAL, TABFILE, WORLDFILE, XML " +"(added in 3.7), NONE. Earlier mentioned sources take priority over later " +"ones. A non mentioned source will be ignored." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:69 +msgid "" +"For example setting it to \"WORLDFILE,PAM,INTERNAL\" will make a " +"geotransformation matrix from a potential worldfile priority over PAM or " +"GeoTIFF." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:73 +msgid "" +"Minimum support for extracting the CRS from ESRI .xml side car files has " +"been added in GDAL 3.7, using the " +"metadata.refSysInfo.RefSystem.refSysID.identCode.code CRS code." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:77 +msgid "" +"GDAL can read and write the *RPCCoefficientTag* as described in the `RPCs" +" in GeoTIFF `__ proposed " +"extension. The tag is written only for files created with the default " +"profile GDALGeoTIFF. For other profiles, a .RPB file is created. In GDAL " +"data model, the RPC coefficients are stored into the RPC metadata domain." +" For more details, see the :ref:`rfc-22`. If .RPB or \\_RPC.TXT files are" +" found, they will be used to read the RPCs, even if the " +"*RPCCoefficientTag* tag is set." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:87 +msgid "Internal nodata masks" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:89 +msgid "" +"TIFF files can contain internal transparency masks. The GeoTIFF driver " +"recognizes an internal directory as being a transparency mask when the " +"FILETYPE_MASK bit value is set on the TIFFTAG_SUBFILETYPE tag. According " +"to the TIFF specification, such internal transparency masks contain 1 " +"sample of 1-bit data. Although the TIFF specification allows for higher " +"resolutions for the internal transparency mask, the GeoTIFF driver only " +"supports internal transparency masks of the same dimensions as the main " +"image. Transparency masks of internal overviews are also supported." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:98 +msgid "" +"When the :config:`GDAL_TIFF_INTERNAL_MASK` configuration option is set to" +" YES (which is the case starting with GDAL 3.9 when CreateMaskBand() is " +"invoked on the dataset, or when it is invoked on a raster band with the " +"GMF_PER_DATASET flag), and the GeoTIFF file is opened in update mode, the" +" CreateMaskBand() method on a TIFF dataset or rasterband will create an " +"internal transparency mask. Otherwise, the default behavior of nodata " +"mask creation will be used, that is to say the creation of a .msk file, " +"as per :ref:`rfc-15`." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:106 +msgid "" +"1-bit internal mask band are deflate compressed. When reading them back, " +"to make conversion between mask band and alpha band easier, mask bands " +"are exposed to the user as being promoted to full 8 bits (i.e. the value " +"for unmasked pixels is 255) unless the " +":config:`GDAL_TIFF_INTERNAL_MASK_TO_8BIT` configuration option is set to " +"NO. This does not affect the way the mask band is written (it is always " +"1-bit)." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:116 +msgid "" +"The GeoTIFF driver supports reading, creation and update of internal " +"overviews. Internal overviews can be created on GeoTIFF files opened in " +"update mode (with gdaladdo for instance). If the GeoTIFF file is opened " +"as read only, the creation of overviews will be done in an external .ovr " +"file. Overview are only updated on request with the BuildOverviews() " +"method." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:123 +msgid "" +"The block size (tile width and height) used for overviews (internal or " +"external) can be specified by setting the GDAL_TIFF_OVR_BLOCKSIZE " +"environment variable to a power-of-two value between 64 and 4096. The " +"default is 128, or starting with GDAL 3.1 to use the same block size as " +"the full-resolution dataset if possible (i.e. block height and width are " +"equal, a power-of-two, and between 64 and 4096)." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:131 +msgid "Overviews and nodata masks" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:133 +msgid "" +"The following configurations can be encountered depending if overviews " +"and nodata masks are internal or not." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:136 +msgid "" +"Internal overviews, internal nodata mask: If a GeoTIFF file has a " +"internal transparency mask and the GeoTIFF file is opened in update mode," +" BuildOverviews() will automatically create overviews for the internal " +"transparency mask." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:140 +msgid "" +"External overviews, external nodata mask: When opened in read-only mode, " +"BuildOverviews() will automatically create overviews for the external " +"transparency mask (in a .msk.ovr file)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:143 +msgid "" +"Internal overviews, external nodata mask: when running BuildOverviews() " +"in update mode on the .tif file, starting with GDAL 3.9, overviews of the" +" main bands and of the external .msk will be generated ( as internal " +"overview of the .msk). Prior to GDAL 3.9, only the overviews of the main " +"bands are generated. Overviews of the external .msk file had to be " +"explicitly generated by running BuildOverviews() on the .msk." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:151 +msgid "For the remaining configuration, behavior is less obvious:" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:153 +msgid "" +"External overviews, internal nodata mask: when running BuildOverviews() " +"in read-only mode on the .tif file, only the overviews of the main bands " +"will be generated. Generating the overviews of the internal nodata mask " +"is not currently supported by the driver." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:159 +msgid "" +"Practical note: for a command line point of view, BuildOverview() in " +"update mode means \"gdaladdo the.tiff\" (without -ro). Whereas " +"BuildOverviews() in read-only mode means \"gdaladdo -ro the.tiff\"." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:166 +msgid "" +"GDAL can deal with the following baseline TIFF tags as dataset-level " +"metadata :" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:169 +msgid "TIFFTAG_DOCUMENTNAME" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:170 +msgid "TIFFTAG_IMAGEDESCRIPTION" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:171 +msgid "TIFFTAG_SOFTWARE" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:172 +msgid "TIFFTAG_DATETIME" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:173 +msgid "TIFFTAG_ARTIST" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:174 +msgid "TIFFTAG_HOSTCOMPUTER" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:175 +msgid "TIFFTAG_COPYRIGHT" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:176 +msgid "TIFFTAG_XRESOLUTION" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:177 +msgid "TIFFTAG_YRESOLUTION" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:178 +msgid "TIFFTAG_RESOLUTIONUNIT" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:179 +msgid "TIFFTAG_MINSAMPLEVALUE (read only)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:180 +msgid "TIFFTAG_MAXSAMPLEVALUE (read only)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:181 +msgid "" +"`GEO_METADATA " +"`__:" +" This tag may be used for embedding XML-encoded instance documents " +"prepared using 19139-based schema (GeoTIFF DGIWG) (GDAL >= 2.3)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:184 +msgid "" +"`TIFF_RSID " +"`__: " +"This tag specifies a File Universal Unique Identifier, or RSID, according" +" to DMF definition (GeoTIFF DGIWG) (GDAL >= 2.3)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:188 +msgid "" +"The name of the metadata item to use is one of the above names " +"(\"TIFFTAG_DOCUMENTNAME\", ...). On creation, those tags can for example " +"be set with" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:196 +msgid "" +"Other non standard metadata items can be stored in a TIFF file created " +"with the profile GDALGeoTIFF (the default, see below in the Creation " +"issues section). Those metadata items are grouped together into a XML " +"string stored in the non standard TIFFTAG_GDAL_METADATA ASCII tag (code " +"42112). When BASELINE or GeoTIFF profile are used, those non standard " +"metadata items are stored into a PAM .aux.xml file." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:203 +msgid "" +"The value of GDALMD_AREA_OR_POINT (\"AREA_OR_POINT\") metadata item is " +"stored in the GeoTIFF key RasterPixelIsPoint for GDALGeoTIFF or GeoTIFF " +"profiles." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:207 +msgid "" +"XMP metadata can be extracted from the file, and will be reported as XML " +"raw content in the xml:XMP metadata domain." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:210 +msgid "" +"EXIF metadata can be extracted from the file, and will be reported in the" +" EXIF metadata domain." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:214 +#: ../../source/drivers/raster/jpeg.rst:76 +#: ../../source/drivers/raster/jpegxl.rst:45 +#: ../../source/drivers/raster/png.rst:49 +msgid "Color Profile Metadata" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:216 +#: ../../source/drivers/raster/jpeg.rst:78 +#: ../../source/drivers/raster/jpegxl.rst:47 +#: ../../source/drivers/raster/png.rst:51 +msgid "" +"GDAL can deal with the following color profile metadata in the " +"COLOR_PROFILE domain:" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:219 +#: ../../source/drivers/raster/png.rst:54 +msgid "" +"SOURCE_ICC_PROFILE (Base64 encoded ICC profile embedded in file. If " +"available, other tags are ignored.)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:221 +#: ../../source/drivers/raster/png.rst:58 +msgid "SOURCE_PRIMARIES_RED (xyY in \"x,y,1\" format for red primary.)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:222 +#: ../../source/drivers/raster/png.rst:59 +msgid "SOURCE_PRIMARIES_GREEN (xyY in \"x,y,1\" format for green primary)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:223 +#: ../../source/drivers/raster/png.rst:60 +msgid "SOURCE_PRIMARIES_BLUE (xyY in \"x,y,1\" format for blue primary)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:224 +#: ../../source/drivers/raster/png.rst:61 +msgid "SOURCE_WHITEPOINT (xyY in \"x,y,1\" format for whitepoint)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:225 +msgid "TIFFTAG_TRANSFERFUNCTION_RED (Red table of TIFFTAG_TRANSFERFUNCTION)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:226 +msgid "TIFFTAG_TRANSFERFUNCTION_GREEN (Green table of TIFFTAG_TRANSFERFUNCTION)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:228 +msgid "TIFFTAG_TRANSFERFUNCTION_BLUE (Blue table of TIFFTAG_TRANSFERFUNCTION)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:230 +msgid "TIFFTAG_TRANSFERRANGE_BLACK (Min range of TIFFTAG_TRANSFERRANGE)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:231 +msgid "TIFFTAG_TRANSFERRANGE_WHITE (Max range of TIFFTAG_TRANSFERRANGE)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:233 +#: ../../source/drivers/raster/png.rst:64 +msgid "" +"Note that these metadata properties can only be used on the original raw " +"pixel data. If automatic conversion to RGB has been done, the color " +"profile information cannot be used." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:237 +msgid "All these metadata tags can be overridden and/or used as creation options." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:243 +msgid "" +"GDAL stores band nodata value in the non standard TIFFTAG_GDAL_NODATA " +"ASCII tag (code 42113) for files created with the default profile " +"GDALGeoTIFF. Note that all bands must use the same nodata value. When " +"BASELINE or GeoTIFF profile are used, the nodata value is stored into a " +"PAM .aux.xml file." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:250 +msgid "Sparse files" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:252 +msgid "" +"GDAL makes a special interpretation of a TIFF tile or strip whose offset " +"and byte count are set to 0, that is to say a tile or strip that has no " +"corresponding allocated physical storage. On reading, such tiles or " +"strips are considered to be implicitly set to 0 or to the nodata value " +"when it is defined. On writing, it is possible to enable generating such " +"files through the Create() interface by setting the :co:`SPARSE_OK` " +"creation option to YES. Then, blocks that are never written through the " +"IWriteBlock()/IRasterIO() interfaces will have their offset and byte " +"count set to 0. This is particularly useful to save disk space and time " +"when the file must be initialized empty before being passed to a further " +"processing stage that will fill it. To avoid ambiguities with another " +"sparse mechanism discussed in the next paragraphs, we will call such " +"files with implicit tiles/strips \"TIFF sparse files\". They will be " +"likely **not** interoperable with TIFF readers that are not GDAL based " +"and would consider such files with implicit tiles/strips as defective." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:268 +msgid "" +"Starting with GDAL 2.2, this mechanism is extended to the CreateCopy() " +"and Open() interfaces (for update mode) as well. If the :co:`SPARSE_OK` " +"creation option (or the :oo:`SPARSE_OK` open option for Open()) is set to" +" YES, even an attempt to write a all 0/nodata block will be detected so " +"that the tile/strip is not allocated (if it was already allocated, then " +"its content will be replaced by the 0/nodata content)." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:275 +msgid "" +"Starting with GDAL 2.2, in the case where :co:`SPARSE_OK` is **not** " +"defined (or set to its default value FALSE), for uncompressed files whose" +" nodata value is not set, or set to 0, in Create() and CreateCopy() mode," +" the driver will delay the allocation of 0-blocks until file closing, so " +"as to be able to write them at the very end of the file, and in a way " +"compatible of the filesystem sparse file mechanisms (to be distinguished " +"from the TIFF sparse file extension discussed earlier). That is that all " +"the empty blocks will be seen as properly allocated from the TIFF point " +"of view (corresponding strips/tiles will have valid offsets and byte " +"counts), but will have no corresponding physical storage. Provided that " +"the filesystem supports such sparse files, which is the case for most " +"Linux popular filesystems (ext2/3/4, xfs, btfs, ...) or NTFS on Windows. " +"If the file system does not support sparse files, physical storage will " +"be allocated and filled with zeros." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:291 +msgid "Raw mode" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:293 +msgid "" +"For some TIFF formulations that have \"odd\" photometric color spaces, " +"on-the-fly decoding as RGBA is done. This might not be desirable in some " +"use cases. This behavior can be disabled by prefixing the filename with " +"GTIFF_RAW:" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:298 +msgid "For example to translate a CMYK file to another one :" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:307 +#: ../../source/drivers/raster/xyz.rst:53 +#: ../../source/drivers/vector/geojson.rst:187 +msgid "|about-open-options| This driver supports the following open options:" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:-1 +msgid "" +"NUM_THREADS=[/ALL_CPUS]: Enable multi-threaded " +"compression by specifying the number of worker threads. Worth it for slow" +" compression algorithms such as DEFLATE or LZMA. Default is compression " +"in the main thread. Starting with GDAL 3.6, this option also enables " +"multi-threaded decoding when RasterIO() requests intersect several " +"tiles/strips. The GDAL_NUM_THREADS configuration option can also be used " +"as an alternative to setting the open option." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:-1 +msgid "" +"GEOREF_SOURCES=comma-separated list with one or several of PAM, INTERNAL," +" TABFILE, WORLDFILE or XML (XML added in 3.7): Define which " +"georeferencing sources are allowed and their priority order. See " +"Georeferencing paragraph." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:-1 +msgid "" +"SPARSE_OK=[TRUE/FALSE]: Defaults to FALSE. Should empty blocks be " +"omitted on disk? When this option is set, any attempt of writing a block " +"whose all pixels are 0 or the nodata value will cause it not to be " +"written at all (unless there is a corresponding block already allocated " +"in the file). Sparse files have 0 tile/strip offsets for blocks never " +"written and save space; however, most non-GDAL packages cannot read such " +"files." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:344 +msgid "" +"**IGNORE_COG_LAYOUT_BREAK=YES/NO** (GDAL >= 3.8): Updating a COG (Cloud " +"Optimized GeoTIFF) file generally breaks part of the optimizations, but " +"still produces a valid GeoTIFF file. Starting with GDAL 3.8, to avoid " +"undesired loss of the COG characteristics, opening such a file in update " +"mode will be rejected, unless this option is also set to YES (default is " +"NO). This option has only effect on COG files and when opening in update " +"mode, and is ignored on regular (Geo)TIFF files." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:356 +msgid "" +"GeoTIFF files can be created with any GDAL defined band type, including " +"the complex types. Created files may have any number of bands. Files of " +"type Byte with exactly 3 bands will be given a photometric interpretation" +" of RGB, files of type Byte with exactly four bands will have a " +"photometric interpretation of RGBA, while all other combinations will " +"have a photometric interpretation of MIN_IS_BLACK. Starting with GDAL " +"2.2, non-standard (regarding to the intrinsics TIFF capabilities) band " +"color interpretation, such as BGR ordering, will be handled in creation " +"and reading, by storing them in the GDAL internal metadata TIFF tag." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:367 +msgid "" +"The TIFF format only supports R,G,B components for palettes / color " +"tables. Thus on writing the alpha information will be silently discarded." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:371 +msgid "" +"You may want to read hints to `generate and read cloud optimized GeoTIFF " +"files `__" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:377 +msgid "" +"|about-creation-options| This driver supports the following creation " +"options:" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:449 +msgid "" +"``JPEG`` should generally only be used with Byte data (8 bit per " +"channel). Better compression for RGB images can be obtained by using the " +"PHOTOMETRIC=YCBCR colorspace with a 4:2:2 subsampling of the Y,Cb,Cr " +"components." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:453 +msgid "" +"Starting with GDAL 3.4, if GDAL is built with its internal libtiff, read " +"and write support for JPEG-in-TIFF compressed images with 12-bit sample " +"is enabled by default (if JPEG support is also enabled), using GDAL " +"internal libjpeg (based on IJG libjpeg-6b, with additional changes for " +"12-bit sample support). Support for JPEG with 12-bit sample is " +"independent of whether 8-bit JPEG support is enabled through internal IJG" +" libjpeg-6b or external libjpeg (like libjpeg-turbo)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:461 +msgid "" +"``CCITTFAX3``, ``CCITTFAX4`` or ``CCITRLE`` compression should only be " +"used with 1bit (NBITS=1) data" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:465 +msgid "" +"``ZSTD`` is available since GDAL 2.3 when using internal libtiff and if " +"GDAL built against libzstd >=1.0, or if built against external libtiff " +"with zstd support." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:468 +msgid "" +"``LERC`` and ``LERC_DEFLATE`` are available only when using internal " +"libtiff for GDAL < 3.3.0. Since GDAL 3.3.0, LERC compression is also " +"available when building GDAL against external libtiff >= 4.3.0, built " +"itself against https://github.com/esri/lerc" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:474 +msgid "" +"``JXL`` is for JPEG-XL, and is only available when using internal libtiff" +" and building GDAL against https://github.com/libjxl/libjxl . Supported " +"data types are ``Byte``, ``UInt16`` and ``Float32`` only. For GDAL < " +"3.6.0, JXL compression may only be used alongside ``INTERLEAVE=PIXEL`` " +"(the default) on datasets with 4 bands or less." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:479 +msgid "``NONE`` is the default." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:527 +#: ../../source/drivers/raster/jpeg.rst:180 +msgid "" +"Low values result in higher compression ratios, but poorer image quality " +"with strong blocking artifacts. Values above 95 are not meaningfully " +"better quality but can be substantially larger." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:540 +msgid "" +"0: JpegTables is not written. Each strip/tile contains its own " +"quantization tables and use optimized Huffman coding." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:542 +msgid "" +"1: JpegTables is written with only the quantization tables. Each " +"strip/tile refers to those quantized tables and use optimized Huffman " +"coding. This is generally the optimal choice for smallest file size, and " +"consequently is the default." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:546 +msgid "" +"2: JpegTables is written with only the default Huffman tables. Each " +"strip/tile refers to those Huffman tables (thus no optimized Huffman " +"coding) and contains its own quantization tables (identical). This option" +" has no anticipated practical value." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:550 +msgid "" +"3: JpegTables is written with the quantization and default Huffman " +"tables. Each strip/tile refers to those tables (thus no optimized Huffman" +" coding). This option could perhaps with some data be more efficient than" +" 1, but this should only occur in rare circumstances." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:673 +msgid "" +"With ``GDALGeoTIFF`` (the default) various GDAL custom tags may be " +"written." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:675 +msgid "With ``GeoTIFF`` only GeoTIFF tags will be added to the baseline." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:676 +msgid "" +"With ``BASELINE`` no GDAL or GeoTIFF tags will be written. BASELINE is " +"occasionally useful when writing files to be read by applications " +"intolerant of unrecognized tags." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:691 +msgid "" +"``IF_SAFER`` will create BigTIFF if the resulting file \\*might\\* exceed" +" 4GB. Note: this is only a heuristic that might not always work depending" +" on compression ratios." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:695 +msgid "" +"BigTIFF is a TIFF variant which can contain more than 4GiB of data (size " +"of classic TIFF is limited by that value). This option is available if " +"GDAL is built with libtiff library version 4.0 or higher." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:700 +msgid "" +"When creating a new GeoTIFF with no compression, GDAL computes in advance" +" the size of the resulting file. If that computed file size is over 4GiB," +" GDAL will automatically decide to create a BigTIFF file. However, when " +"compression is used, it is not possible in advance to known the final " +"size of the file, so classical TIFF will be chosen. In that case, the " +"user must explicitly require the creation of a BigTIFF with " +":co:`BIGTIFF=YES` if the final file is anticipated to be too big for " +"classical TIFF format. If BigTIFF creation is not explicitly asked or " +"guessed and the resulting file is too big for classical TIFF, libtiff " +"will fail with an error message like \"TIFFAppendToStrip:Maximum TIFF " +"file size exceeded\"." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:779 +msgid "" +"Multi-page TIFF files are exposed as subdatasets. On opening, a " +"subdataset name is GTIFF_DIR:{index}:filename.tif, where {index} starts " +"at 1." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:783 +msgid "" +"Starting with GDAL 3.0, subdataset creation is possible by using the " +"APPEND_SUBDATASET=YES creation option. The filename passed to Create() / " +"CreateCopy() should be the regular filename (not with GTIFF_DIR: syntax. " +"Creating overviews on a multi-page TIFF is not supported." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:788 +msgid "" +"Starting with GDAL 3.2, read-only access to subdataset overviews and " +"masks is possible provided that they are referenced by their parent IFD " +"through the `TIFFTAG_SUBIFD " +"`__ tag." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:793 +msgid "About JPEG compression of RGB images" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:795 +msgid "" +"When translating a RGB image to JPEG-In-TIFF, using PHOTOMETRIC=YCBCR can" +" make the size of the image typically 2 to 3 times smaller than the " +"default photometric value (RGB). When using PHOTOMETRIC=YCBCR, the " +"INTERLEAVE option must be kept to its default value (PIXEL), otherwise " +"libtiff will fail to compress the data." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:801 +msgid "" +"Note also that the dimensions of the tiles or strips must be a multiple " +"of 8 for PHOTOMETRIC=RGB or 16 for PHOTOMETRIC=YCBCR" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:805 +msgid "Lossless conversion of JPEG into JPEG-in-TIFF" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:807 +msgid "" +"The conversion of a JPEG file (but *not* a JPEG-in-TIFF file) to a JPEG-" +"in-TIFF file without decompression and compression cycles, and thus " +"without any additional quality loss, can be done with gdal_translate (or " +"the CreateCopy() API), if all the following conditions are met:" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:812 +msgid "" +"the source dataset is a JPEG file (or a VRT with a JPEG as a single " +"SimpleSource)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:813 +msgid "the target dataset is a JPEG-in-TIFF file" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:814 +msgid "no explicitly target JPEG quality is specified" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:815 +msgid "no change in colorspace is specified" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:816 +msgid "no sub-windowing is requested" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:817 +msgid "and more generally, no change that alters pixel values" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:819 +msgid "" +"The generation of a tiled JPEG-in-TIFF from the original JPEG image is " +"possible. Explicit assignment of target SRS and bounds are also possible." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:822 +msgid "So, the following commands will use the lossless copy method :" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:833 +msgid "" +"whereas the following commands will *not* (and thus cause JPEG " +"decompression and compression):" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:844 +msgid "Streaming operations" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:846 +msgid "" +"The GeoTIFF driver can support reading or writing TIFF files (with some " +"restrictions detailed below) in a streaming compatible way." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:850 +msgid "" +"When reading a file from /vsistdin/, a named pipe (on Unix), or if " +"forcing streamed reading by setting the :config:`TIFF_READ_STREAMING` " +"configuration option to YES, the GeoTIFF driver will assume that the TIFF" +" Image File Directory (IFD) is at the beginning of the file, i.e. at " +"offset 8 for a classical TIFF file or at offset 16 for a BigTIFF file. " +"The values of the tags of array type must be contained at the beginning " +"of file, after the end of the IFD and before the first image strip/tile. " +"The reader must read the strips/tiles in the order they are written in " +"the file. For a pixel interleaved file (PlanarConfiguration=Contig), the " +"recommended order for a writer, and thus for a reader, is from top to " +"bottom for a strip-organized file or from top to bottom, which a chunk of" +" a block height, and left to right for a tile-organized file. For a band " +"organized file (PlanarConfiguration=Separate), the above order is " +"recommended with the content of the first band, then the content of the " +"second band, etc... Technically this order corresponds to increasing " +"offsets in the TileOffsets/StripOffsets tag. This is the order that the " +"GDAL raster copy routine will assume." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:868 +msgid "" +"If the order is not the one described above, the UNORDERED_BLOCKS=YES " +"dataset metadata item will be set in the TIFF metadata domain. Each block" +" offset can be determined by querying the " +"\"BLOCK_OFFSET_[xblock]_[yblock]\" band metadata items in the TIFF " +"metadata domain (where xblock, yblock is the coordinate of the block), " +"and a reader could use that information to determine the appropriate " +"reading order for image blocks." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:876 +msgid "" +"The files that are streamed into the GeoTIFF driver may be compressed, " +"even if the GeoTIFF driver cannot produce such files in streamable output" +" mode (regular creation of TIFF files will produce such compatible files " +"for streamed reading)." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:881 +msgid "" +"When writing a file to /vsistdout/, a named pipe (on Unix), or when " +"defining the :co:`STREAMABLE_OUTPUT=YES` creation option, the " +"CreateCopy() method of the GeoTIFF driver will generate a file with the " +"above defined constraints (related to position of IFD and block order), " +"and this is only supported for a uncompressed file. The Create() method " +"also supports creating streamable compatible files, but the writer must " +"be careful to set the projection, geotransform or metadata before writing" +" image blocks (so that the IFD is written at the beginning of the file). " +"And when writing image blocks, the order of blocks must be the one of the" +" above paragraph, otherwise errors will be reported." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:892 +msgid "Some examples :" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:906 +msgid "" +"Note: not all utilities are compatible with such input or output " +"streaming operations, and even those which may deal with such files may " +"not manage to deal with them in all circumstances, for example if the " +"reading driver driven by the output file is not compatible with the block" +" order of the streamed input." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:915 +msgid "" +"|about-config-options| This paragraph lists the configuration options " +"that can be set to alter the default behavior of the GTiff driver." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1012 +msgid "" +":config:`USE_RRD`: Can be set to TRUE to force external overviews in the " +"RRD format." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1097 +msgid "" +":config:`GDAL_NUM_THREADS` enables multi-threaded compression by " +"specifying the number of worker threads. Worth it for slow compression " +"algorithms such as DEFLATE or LZMA. Will be ignored for JPEG. Default is " +"compression in the main thread. Note: this configuration option also " +"apply to other parts to GDAL (warping, gridding, ...). Starting with GDAL" +" 3.6, this option also enables multi-threaded decoding when RasterIO() " +"requests intersect several tiles/strips." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1156 +msgid "Codec Recommendations" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1160 +msgid "LZW" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1162 +msgid "If you don't know what to choose, choose this one." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1165 +msgid "DEFLATE" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1167 +msgid "" +"The most commonly supported TIFF codec, especially with older non-geo " +"software." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1170 +msgid "LERC" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1172 +msgid "" +"Used for storing quantized floating point data. " +"https://github.com/esri/lerc" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1176 +msgid "ZSTD" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1178 +msgid "Smaller and faster than DEFLATE, but not as commonly supported." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1183 +msgid "A smaller and faster JPEG." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1186 +msgid "JXL" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1188 +msgid "Next-gen JPG from the JPG group." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1192 +msgid "LZMA" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1194 +msgid "Slow but storage efficient." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1197 +msgid "CCITTRLE/CCITTFAX3/CCITTFAX4" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1199 +msgid "Did you happen to have fax files from the 1990s? Use these." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1204 +msgid "`GeoTIFF Information Page `__" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1205 +msgid "`libtiff Page `__" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1206 +msgid "" +"`Details on BigTIFF file format " +"`__" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1208 +msgid ":ref:`raster.cog` driver" +msgstr "" + +#: ../../source/drivers/raster/gxf.rst:5 +msgid "GXF -- Grid eXchange File" +msgstr "" + +#: ../../source/drivers/raster/gxf.rst:7 +msgid "GXF" +msgstr "" + +#: ../../source/drivers/raster/gxf.rst:11 +msgid "" +"This is a raster exchange format propagated by Geosoft, and made a " +"standard in the gravity/magnetics field. GDAL supports reading (but not " +"writing) GXF-3 files, including support for georeferencing information, " +"and projections." +msgstr "" + +#: ../../source/drivers/raster/gxf.rst:16 +msgid "" +"By default, the datatype returned for GXF datasets by GDAL is Float32. " +"You can specify the datatype by setting the GXF_DATATYPE configuration " +"option (Float64 supported currently)" +msgstr "" + +#: ../../source/drivers/raster/gxf.rst:20 +msgid "" +"Details on the supporting code, and format can be found on the `GXF-3 " +"`__" +" page." +msgstr "" + +#: ../../source/drivers/raster/gxf.rst:23 +msgid "NOTE: Implemented as :source_file:`frmts/gxf/gxfdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:5 +msgid "HDF4 -- Hierarchical Data Format Release 4 (HDF4)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:7 +msgid "HDF4" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:9 +msgid "HDF4Image" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:13 +msgid "" +"There are two HDF formats, HDF4 (4.x and previous releases) and HDF5. " +"These formats are completely different and NOT compatible. This driver " +"intended for HDF4 file formats importing. NASA's Earth Observing System " +"(EOS) maintains its own HDF modification called HDF-EOS. This " +"modification is suited for use with remote sensing data and fully " +"compatible with underlying HDF. This driver can import HDF4-EOS files. " +"Currently EOS use HDF4-EOS for data storing (telemetry from \"Terra\" and" +" \"Aqua\" satellites). In the future they will switch to HDF5-EOS format," +" which will be used for telemetry from \"Aura\" satellite." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:33 +#: ../../source/drivers/raster/hdf5.rst:29 +#: ../../source/drivers/raster/netcdf.rst:31 +msgid "Multiple Image Handling (Subdatasets)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:35 +msgid "" +"Hierarchical Data Format is a container for several different datasets. " +"For data storing Scientific Datasets (SDS) used most often. SDS is a " +"multidimensional array filled by data. One HDF file may contain several " +"different SDS arrays. They may differ in size, number of dimensions and " +"may represent data for different regions." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:41 +msgid "" +"If the file contains only one SDS that appears to be an image, it may be " +"accessed normally, but if it contains multiple images it may be necessary" +" to import the file via a two step process. The first step is to get a " +"report of the components images (SDS arrays) in the file using " +"**gdalinfo**, and then to import the desired images using gdal_translate." +" The **gdalinfo** utility lists all multidimensional subdatasets from the" +" input HDF file. The name of individual images (subdatasets) are assigned" +" to the **SUBDATASET_n_NAME** metadata item. The description for each " +"image is found in the **SUBDATASET_n_DESC** metadata item. For HDF4 " +"images the subdataset names will be formatted like this:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:53 +msgid "*HDF4_SDS:subdataset_type:file_name:subdataset_index*" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:55 +msgid "" +"where *subdataset_type* shows predefined names for some of the well known" +" HDF datasets, *file_name* is the name of the input file, and " +"*subdataset_index* is the index of the image to use (for internal use in " +"GDAL)." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:60 +#: ../../source/drivers/raster/hdf5.rst:58 +msgid "" +"On the second step you should provide this name for **gdalinfo** or " +"**gdal_translate** for actual reading of the data." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:63 +msgid "For example, we want to read data from the MODIS Level 1B dataset:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:78 +msgid "...a lot of metadata output skipped..." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:124 +msgid "" +"Now select one of the subdatasets, described as ``[12x2040x1354] " +"EV_1KM_RefSB (16-bit unsigned integer)``:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:136 +msgid "...metadata skipped..." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:159 +msgid "" +"Or you may use **gdal_translate** for reading image bands from this " +"dataset." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:162 +msgid "" +"Note that you should provide exactly the contents of the line marked " +"**SUBDATASET_n_NAME** to GDAL, including the **HDF4_SDS:** prefix." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:165 +msgid "" +"This driver is intended only for importing remote sensing and geospatial " +"datasets in form of raster images. If you want explore all data contained" +" in HDF file you should use another tools (you can find information about" +" different HDF tools using links at end of this page)." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:173 +#: ../../source/drivers/raster/hdf5.rst:199 +msgid "" +"There is no universal way of storing georeferencing in HDF files. " +"However, some product types have mechanisms for saving georeferencing, " +"and some of these are supported by GDAL. Currently supported are " +"(*subdataset_type* shown in parenthesis):" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:178 +msgid "HDF4 files created by GDAL (**GDAL_HDF4**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:179 +msgid "ASTER Level 1A (**ASTER_L1A**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:180 +msgid "ASTER Level 1B (**ASTER_L1B**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:181 +msgid "ASTER Level 2 (**ASTER_L2**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:182 +msgid "ASTER DEM (**AST14DEM**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:183 +msgid "MODIS Level 1B Earth View products (**MODIS_L1B**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:184 +msgid "MODIS Level 3 products (**MODIS_L3**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:185 +msgid "SeaWiFS Level 3 Standard Mapped Image Products (**SEAWIFS_L3**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:187 +msgid "" +"By default the hdf4 driver only reads the gcps from every 10th row and " +"column from EOS_SWATH datasets. You can change this behavior by setting " +"the GEOL_AS_GCPS environment variable to PARTIAL (default), NONE, or " +"FULL." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:195 +msgid "" +"This driver supports creation of the HDF4 Scientific Datasets. You may " +"create set of 2D datasets (one per each input band) or single 3D dataset " +"where the third dimension represents band numbers. All metadata and band " +"descriptions from the input dataset are stored as HDF4 attributes. " +"Projection information (if it exists) and affine transformation " +"coefficients also stored in form of attributes. Files, created by GDAL " +"have the special attribute:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:203 +msgid "\"Signature=Created with GDAL (http://www.remotesensing.org/gdal/)\"" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:205 +msgid "" +"and are automatically recognised when read, so the projection info and " +"transformation matrix restored back." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:-1 +msgid "" +"RANK=[2/3]: Defaults to 3. Create n-dimensional SDS. Currently only 2D " +"and 3D datasets supported. By default a 3-dimensional dataset will be " +"created." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:222 +msgid "" +"All HDF4 attributes are transparently translated as GDAL metadata. In the" +" HDF file attributes may be assigned assigned to the whole file as well " +"as to particular subdatasets." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:229 +msgid "|about-open-options| The following open option is supported:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:-1 +msgid "" +"LIST_SDS=[AUTO/YES/NO]: (GDAL >= 3.2) Whether to report Scientific Data " +"Sets (SDS). By default, when a HDF file contains EOS_SWATH or EOS_GRID, " +"SDS will not be listed as GDAL subdatasets (as this would cause them to " +"be reported twice). Listing them can be forced by setting LIST_SDS to " +"YES." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:243 +#: ../../source/drivers/raster/hdf5.rst:220 +#: ../../source/drivers/raster/mem.rst:94 +#: ../../source/drivers/raster/netcdf.rst:661 +#: ../../source/drivers/raster/tiledb.rst:133 +msgid "Multidimensional API support" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:247 +msgid "" +"The HDF4 driver supports the :ref:`multidim_raster_data_model` for " +"reading operations." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:251 +#: ../../source/drivers/raster/hdf5.rst:228 +#: ../../source/drivers/raster/netcdf.rst:724 +msgid "Driver building" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:253 +msgid "" +"This driver built on top of NCSA HDF library, so you need one to compile " +"GDAL with HDF4 support. You may search your operating system distribution" +" for the precompiled binaries or download source code or binaries from " +"the NCSA HDF Home Page (see links below)." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:258 +msgid "" +"Please note, that NCSA HDF library compiled with several defaults which " +"is defined in *hlimits.h* file. For example, *hlimits.h* defines the " +"maximum number of opened files:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:266 +msgid "" +"If you need open more HDF4 files simultaneously you should change this " +"value and rebuild HDF4 library (and relink GDAL if using static HDF " +"libraries)." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:273 +msgid "" +"Implemented as :source_file:`frmts/hdf4/hdf4dataset.cpp` and " +":source_file:`frmts/hdf4/hdf4imagedataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:275 +msgid "`The HDF Group `__" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:276 +msgid "" +"Sources of the data in HDF4 and HDF4-EOS formats: `Earth Observing System" +" Data Gateway `__" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:280 +#: ../../source/drivers/raster/hdf5.rst:251 +msgid "Documentation to individual products, supported by this driver:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:282 +msgid "" +"`Geo-Referencing ASTER L1B Data " +"`__" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:284 +msgid "" +"`ASTER Standard Data Product Specifications Document " +"`__" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:286 +msgid "" +"`MODIS Level 1B Product Information and Status " +"`__" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:288 +msgid "" +"`MODIS Ocean User's Guide `__" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:5 +msgid "HDF5 -- Hierarchical Data Format Release 5 (HDF5)" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:7 +msgid "HDF5" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:9 +msgid "HDF5Image" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:13 +msgid "This driver intended for HDF5 file formats importing." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:15 +msgid "" +"Starting with GDAL 3.7, the driver can parse HDF-EOS5 encoded grid and " +"swath metadata to establish projection and geotransform (for grids), and " +"geolocation array (for swaths)" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:31 +msgid "" +"Hierarchical Data Format is a container for several different datasets. " +"For data storing. HDF contains multidimensional arrays filled by data. " +"One HDF file may contain several arrays. They may differ in size, number " +"of dimensions." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:36 +msgid "" +"The first step is to get a report of the components images (arrays) in " +"the file using **gdalinfo**, and then to import the desired images using " +"gdal_translate. The **gdalinfo** utility lists all multidimensional " +"subdatasets from the input HDF file. The name of individual images " +"(subdatasets) are assigned to the **SUBDATASET_n_NAME** metadata item. " +"The description for each image is found in the **SUBDATASET_n_DESC** " +"metadata item. For HDF5 images the subdataset names will be formatted " +"like this:" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:45 +msgid "*HDF5:file_name:subdataset*" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:47 +msgid "where:" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:48 +msgid "*file_name* is the name of the input file, and" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:50 +msgid "" +"*subdataset* is the dataset name of the array to use (for internal use in" +" GDAL)." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:52 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if HDF5`` option to command " +"line utilities accepting it, or ``HDF5`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename, when it is not using subdataset syntax" +" (it can typically be used to force open a netCDF file that would be " +"nominally recognized by the netCDF driver)." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:61 +msgid "For example, we want to read data from the OMI/Aura Ozone (O3) dataset:" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:140 +msgid "" +"Now select one of the subdatasets, described as ``[1645x60] CloudFraction" +" (32-bit floating-point)``:" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:179 +msgid "" +"Corner Coordinates: Upper Left ( 0.0, 0.0) Lower Left ( 0.0, 1645.0) " +"Upper Right ( 60.0, 0.0) Lower Right ( 60.0, 1645.0) Center ( 30.0, " +"822.5) Band 1 Block=60x1 Type=Float32, ColorInterp=Undefined Open GDAL " +"Datasets: 1 N DriverIsNULL 512x512x0" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:184 +msgid "You may use **gdal_translate** for reading image bands from this dataset." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:187 +msgid "" +"Note that you should provide exactly the contents of the line marked " +"**SUBDATASET_n_NAME** to GDAL, including the **HDF5:** prefix." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:190 +msgid "" +"This driver is intended only for importing remote sensing and geospatial " +"datasets in form of raster images(2D or 3D arrays). If you want explore " +"all data contained in HDF file you should use another tools (you can find" +" information about different HDF tools using links at end of this page)." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:204 +msgid "" +"HDF5 OMI/Aura Ozone (O3) Total Column 1-Orbit L2 Swath 13x24km (**Level-2" +" OMTO3**)" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:207 +msgid "HDF-EOS5 grids (starting with GDAL 3.7)" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:209 +msgid "HDF-EOS5 swaths (starting with GDAL 3.7)" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:212 +msgid "Multi-file support" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:214 +msgid "" +"Starting with GDAL 3.1, the driver supports opening datasets split over " +"several files using the 'family' HDF5 file driver. For that, GDAL must be" +" provided with the filename of the first part, containing in it a single " +"'0' (zero) character, or ending with 0.h5 or 0.hdf5" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:224 +msgid "" +"The HDF5 driver supports the :ref:`multidim_raster_data_model` for " +"reading operations." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:230 +msgid "" +"This driver built on top of NCSA HDF5 library, so you need to download " +"prebuild HDF5 libraries: HDF5-1.6.4 library or higher. You also need zlib" +" 1.2 and szlib 2.0. For windows user be sure to set the attributes " +"writable (especially if you are using Cygwin) and that the DLLs can be " +"located somewhere by your PATH environment variable. You may also " +"download source code NCSA HDF Home Page (see links below)." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:240 +msgid "" +"Implemented as :source_file:`frmts/hdf5/hdf5dataset.cpp` and " +":source_file:`frmts/hdf5/hdf5imagedataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:243 +msgid "" +"`The NCSA HDF5 Download Page " +"`__ at the `National " +"Center for Supercomputing Applications `__" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:248 +msgid "" +"`The HDFView is a visual tool for browsing and editing NCSA HDF4 and HDF5" +" files. `__" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:253 +msgid "" +"`OMTO3: OMI/Aura Ozone (O3) Total Column 1-Orbit L2 Swath 13x24km V003 " +"`__" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:256 +msgid "" +"`HDF-EOS5 Data Model, File Format and Library " +"`__" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:5 +msgid "HEIF / HEIC -- ISO/IEC 23008-12:2017 High Efficiency Image File Format" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:9 +msgid "HEIF" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:13 +msgid "" +"High Efficiency Image File Format (HEIF) is a container format for " +"individual images and image sequences. The driver has mostly been " +"developed and tested to be able to read images using the High Efficiency " +"Video Coding (HEVC, ITU-T H.265) codec. Such images are usually called " +"HEIC (HEVC in HEIF) files, and have the .heic extension. iOS 11 can " +"generate such files." +msgstr "" + +#: ../../source/drivers/raster/heif.rst:19 +msgid "" +"libheif 1.4 or later is needed to support images with more than 8-bits " +"per channel." +msgstr "" + +#: ../../source/drivers/raster/heif.rst:21 +msgid "" +"The driver can read EXIF metadata (exposed in the ``EXIF`` metadata " +"domain) and XMP metadata (exposed in the ``xml:XMP`` metadata domain)" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:24 +msgid "" +"The driver will expose the thumbnail as an overview (when its number of " +"bands matches the one of the full resolution image)" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:27 +msgid "" +"If a file contains several top-level images, they will be exposed as GDAL" +" subdatasets." +msgstr "" + +#: ../../source/drivers/raster/heif.rst:-1 +msgid "Supports VirtualIO" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:32 +msgid "if libheif >= 1.4" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:36 +msgid "Built hints on Windows" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:38 +msgid "" +"Download source archives for libheif at " +"https://github.com/strukturag/libheif and libde265 at " +"https://github.com/strukturag/libde265" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:42 +msgid "" +"Unpack the archives (for example libde265-1.0.5.tar.gz and " +"libheif-1.7.0.tar.gz)" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:44 +msgid "Build libde265:" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:58 +msgid "Build libheif with libde265 support:" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:73 +msgid "Add in GDAL's nmake.local the following lines before building GDAL:" +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:5 +msgid "HF2 -- HF2/HFZ heightfield raster" +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:7 +msgid "HF2" +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:11 +msgid "" +"GDAL supports reading and writing HF2/HFZ/HF2.GZ heightfield raster " +"datasets." +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:14 +msgid "" +"HF2 is a heightfield format that records difference between consecutive " +"cell values. HF2 files can also optionally be compressed by the gzip " +"algorithm, and so the HF2.GZ files (or HFZ, equivalently) may be " +"significantly smaller than the uncompressed data. The file format enables" +" the user to have control on the desired accuracy through the vertical " +"precision parameter." +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:21 +msgid "" +"GDAL can read and write georeferencing information through extended " +"header blocks." +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:58 +#: ../../source/drivers/raster/ngsgeoid.rst:22 +#: ../../source/drivers/raster/ngw.rst:216 +#: ../../source/drivers/raster/noaa_b.rst:24 +#: ../../source/drivers/raster/ozi.rst:24 +#: ../../source/drivers/raster/pdf.rst:800 +#: ../../source/drivers/raster/xyz.rst:103 +#: ../../source/drivers/vector/dxf.rst:432 +#: ../../source/drivers/vector/ngw.rst:406 +msgid "See also" +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:60 +msgid "" +"`Specification of HF2/HFZ format " +"`__" +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:62 +msgid "" +"`Specification of HF2 extended header blocks " +"`__" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:5 +msgid "HFA -- Erdas Imagine .img" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:7 +msgid "HFA" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:11 +msgid "" +"GDAL supports Erdas Imagine .img format for read access and write. The " +"driver supports reading overviews, palettes, and georeferencing. It " +"supports the Erdas band types u8, s8, u16, s16, u32, s32, f32, f64, c64 " +"and c128." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:16 +msgid "" +"Compressed and missing tiles in Erdas files should be handled properly on" +" read. Files between 2GiB and 4GiB in size should work on Windows NT, and" +" may work on some Unix platforms. Files with external spill files (needed" +" for datasets larger than 2GiB) are also supported for reading and " +"writing." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:22 +msgid "" +"Metadata reading and writing is supported at the dataset and band level. " +"But this is GDAL specific metadata, not metadata in an Imagine recognized" +" form. The metadata is stored in a table called GDAL_MetaData which as " +"many columns as metadata items. The title of the column is the ``key`` of" +" the ``key``=``value`` metadata item pair and the value of row 1 is " +"``value``." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:43 +msgid "" +"Erdas Imagine files can be created with any GDAL defined band type, " +"including the complex types. Created files may have any number of bands. " +"Pseudo-Color tables will be written if using the GDALDriver::CreateCopy()" +" methodology. Most projections should be supported, though translation of" +" unusual datums (other than WGS84, WGS72, NAD83, and NAD27) may be " +"problematic." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:128 +msgid "" +"Erdas Imagine supports external creation of overviews (with gdaladdo for " +"instance). To force them to be created in an .rrd file (rather than " +"inside the original .img) set the global config option HFA_USE_RRD=YES)." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:132 +msgid "" +"Layer names can be set and retrieved with the " +"GDALSetDescription/GDALGetDescription calls on the Raster Band objects." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:135 +msgid "Some HFA band metadata exported to GDAL metadata:" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:137 +msgid "LAYER_TYPE - layer type (athematic, ... )" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:138 +msgid "" +"OVERVIEWS_ALGORITHM - layer overviews algorithm ('IMAGINE 2X2 " +"Resampling', 'IMAGINE 4X4 Resampling', and others)" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:144 +msgid "" +"|about-config-options| Currently the following configuration options are " +"supported by the HFA driver:" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:162 +msgid "" +"This configuration option can be used when building external overviews " +"for a base image that is not in Erdas Imagine format. Resulting overview " +"file will use the rrd structure and have .aux extension." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:171 +msgid "" +"Erdas Imagine and older ArcGIS versions may recognize overviews for some " +"image formats only if they have .rrd extension. In this case use:" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:196 +msgid "Implemented as :source_file:`frmts/hfa/hfadataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:197 +msgid "" +"More information, and other tools are available on the `Imagine (.img) " +"Reader " +"`__" +" page as saved by archive.org." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:201 +msgid "`Erdas.com `__" +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:5 +msgid "ILWIS -- Raster Map" +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:7 +msgid "ILWIS" +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:11 +msgid "" +"This driver implements reading and writing of ILWIS raster maps and map " +"lists. Select the raster files with ``the.mpr`` (for raster map) or " +"``the.mpl`` (for maplist) extensions." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:15 +msgid "Features:" +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:17 +msgid "Support for Byte, Int16, Int32 and Float64 pixel data types." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:18 +msgid "Supports map lists with an associated set of ILWIS raster maps." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:19 +msgid "" +"Read and write geo-reference (.grf). Support for geo-referencing " +"transform is limited to north-oriented GeoRefCorner only. If possible the" +" affine transform is computed from the corner coordinates." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:22 +msgid "" +"Read and write coordinate files (.csy). Support is limited to: Projection" +" type of Projection and Lat/Lon type that are defined in .csy file, the " +"rest of pre-defined projection types are ignored." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:26 +msgid "Limitations:" +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:28 +msgid "" +"Map lists with internal raster map storage (such as produced through " +"Import General Raster) are not supported." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:30 +msgid "ILWIS domain (.dom) and representation (.rpr) files are currently ignored." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:33 +msgid "NOTE: Implemented in :source_file:`frmts/ilwis`." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:35 +msgid "See Also: http://www.itc.nl/ilwis/default.asp ." +msgstr "" + +#: ../../source/drivers/raster/index.rst:5 +msgid "Raster drivers" +msgstr "" + +#: ../../source/drivers/raster/index.rst:17 +msgid "" +"The following drivers have been retired and moved to the " +"https://github.com/OSGeo/gdal-extra-drivers repository: BPG, E00GRID, " +"EPSILON, IGNFHeightASCIIGrid, NTv1" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:5 +msgid "IRIS -- Vaisala's weather radar software format" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:7 +msgid "IRIS" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:11 +msgid "" +"This read-only GDAL driver is designed to provide access to the products " +"generated by the IRIS weather radar software." +msgstr "" + +#: ../../source/drivers/raster/iris.rst:14 +msgid "" +"IRIS software format includes a lot of products, and some of them aren't " +"even raster. The driver can read currently:" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:17 +msgid "PPI (reflectivity and speed): Plan position indicator" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:18 +msgid "CAPPI: Constant Altitude Plan position indicator" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:19 +msgid "RAIN1: Hourly rainfall accumulation" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:20 +msgid "RAINN: N-Hour rainfall accumulation" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:21 +msgid "TOPS: Height for selectable dBZ contour" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:22 +msgid "VIL: Vertically integrated liquid for selected layer" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:23 +msgid "MAX: Column Max Z WF W/NS Sections" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:25 +msgid "Most of the metadata is read." +msgstr "" + +#: ../../source/drivers/raster/iris.rst:27 +msgid "" +"Vaisala provides information about the format and software at " +"http://www.vaisala.com/en/defense/products/weatherradar/Pages/IRIS.aspx." +msgstr "" + +#: ../../source/drivers/raster/iris.rst:30 +msgid "NOTE: Implemented as :source_file:`frmts/iris/irisdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/isce.rst:5 +msgid "ISCE -- ISCE" +msgstr "" + +#: ../../source/drivers/raster/isce.rst:11 +msgid "" +"Driver for the image formats used in the JPL's Interferometric synthetic " +"aperture radar Scientific Computing Environment (ISCE). Only images with " +"data types mappable to GDAL data types are supported." +msgstr "" + +#: ../../source/drivers/raster/isce.rst:15 +msgid "" +"Image properties are stored under the ISCE metadata domain, but there is " +"currently no support to access underlying components elements and their " +"properties. Likewise, ISCE domain metadata will be saved as properties in" +" the image XML file." +msgstr "" + +#: ../../source/drivers/raster/isce.rst:20 +msgid "Georeferencing is not yet implemented." +msgstr "" + +#: ../../source/drivers/raster/isce.rst:22 +msgid "The ACCESS_MODE property is not currently honored." +msgstr "" + +#: ../../source/drivers/raster/isce.rst:24 +msgid "" +"The only creation option currently is SCHEME, which value (BIL, BIP, BSQ)" +" determine the interleaving (default is BIP)." +msgstr "" + +#: ../../source/drivers/raster/isce.rst:27 +msgid "NOTE: Implemented as :source_file:`frmts/raw/iscedataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/isg.rst:5 +msgid "ISG -- International Service for the Geoid" +msgstr "" + +#: ../../source/drivers/raster/isg.rst:9 +msgid "ISG" +msgstr "" + +#: ../../source/drivers/raster/isg.rst:13 +msgid "" +"Supports reading grids in the International Service for the Geoid text " +"format, used for number of geoid models at " +"http://www.isgeoid.polimi.it/Geoid/reg_list.html" +msgstr "" + +#: ../../source/drivers/raster/isg.rst:17 +msgid "" +"Format specification is at " +"https://www.isgeoid.polimi.it/Geoid/format_specs.html" +msgstr "" + +#: ../../source/drivers/raster/isg.rst:28 +msgid "" +"WGS84 will always be arbitrarily reported as the interpolation CRS of the" +" grid. Consult grid documentation for exact CRS to apply." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:5 +msgid "ISIS2 -- USGS Astrogeology ISIS Cube (Version 2)" +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:7 +msgid "ISIS2" +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:11 +msgid "" +"ISIS2 is a format used by the USGS Planetary Cartography group to store " +"and distribute planetary imagery data. GDAL provides read and write " +"access to ISIS2 formatted imagery data." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:15 +msgid "" +"ISIS2 files often have the extension .cub, sometimes with an associated " +".lbl (label) file. When a .lbl file exists it should be used as the " +"dataset name rather than the .cub file." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:19 +msgid "" +"In addition to support for most ISIS2 imagery configurations, this driver" +" also reads georeferencing and coordinate system information as well as " +"selected other header metadata." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:23 +#: ../../source/drivers/raster/isis3.rst:29 +#: ../../source/drivers/raster/pds.rst:23 +#: ../../source/drivers/raster/pds4.rst:26 +msgid "" +"Implementation of this driver was supported by the United States " +"Geological Survey." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:26 +msgid "ISIS2 is part of a family of related formats including PDS and ISIS3." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:42 +msgid "" +"Currently the ISIS2 writer writes a very minimal header with only the " +"image structure information. No coordinate system, georeferencing or " +"other metadata is captured." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:69 +msgid "Implemented as :source_file:`frmts/pds/isis2dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:70 +msgid ":ref:`raster.pds` driver" +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:71 +msgid ":ref:`raster.isis3` driver" +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:5 +msgid "ISIS3 -- USGS Astrogeology ISIS Cube (Version 3)" +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:7 +msgid "ISIS3" +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:11 +msgid "" +"ISIS3 is a format used by the USGS Planetary Cartography group to store " +"and distribute planetary imagery data. GDAL provides read/creation/update" +" access to ISIS3 formatted imagery data." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:15 +msgid "" +"ISIS3 files often have the extension .cub, sometimes with an associated " +".lbl (label) file. When a .lbl file exists it should be used as the " +"dataset name rather than the .cub file. Since GDAL 2.2, the driver also " +"supports imagery stored in a separate GeoTIFF file." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:20 +msgid "" +"In addition to support for most ISIS3 imagery configurations, this driver" +" also reads georeferencing and coordinate system information as well as " +"selected other header metadata." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:24 +msgid "" +"Starting with GDAL 2.2, a mask band is attached to each source band. The " +"value of this mask band is 0 when the pixel value is the NULL value or " +"one of the low/high on-intstrument/processed saturation value, or 255 " +"when the pixel value is valid." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:32 +msgid "ISIS3 is part of a family of related formats including PDS and ISIS2." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:48 +msgid "" +"Starting with GDAL 2.2, the ISIS3 label can be retrieved as JSON-" +"serialized content in the json:ISIS3 metadata domain." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:150 +msgid "" +"On creation, a source template label can be passed to the SetMetadata() " +"interface in the \"json:ISIS3\" metadata domain." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:156 +msgid "" +"Starting with GDAL 2.2, the ISIS3 driver supports updating imagery of " +"existing datasets, creating new datasets through the CreateCopy() and " +"Create() interfaces." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:160 +msgid "" +"When using CreateCopy(), gdal_translate or gdalwarp, an effort is made to" +" preserve as much as possible of the original label when doing ISIS3 to " +"ISIS3 conversions. This can be disabled with the USE_SRC_LABEL=NO " +"creation option." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:165 +#: ../../source/drivers/raster/vicar.rst:192 +msgid "|about-creation-options| The available creation options are:" +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:311 +msgid "" +"How to create a copy of a source ISIS3 dataset to another ISIS3 dataset " +"while modifying a parameter of IsisCube.Mapping group, by using GDAL " +"Python :" +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:352 +msgid "Implemented as :source_file:`frmts/pds/isis3dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:353 +msgid ":ref:`GDAL PDS Driver `" +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:354 +msgid ":ref:`GDAL ISIS2 Driver `" +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:5 +msgid "JDEM -- Japanese DEM (.mem)" +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:7 +msgid "JDEM" +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:11 +msgid "" +"GDAL includes read support for Japanese DEM files, normally having the " +"extension .mem. These files are a product of the Japanese Geographic " +"Survey Institute." +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:15 +msgid "" +"These files are represented as having one 32bit floating band with " +"elevation data. The georeferencing of the files is returned as well as " +"the coordinate system (always lat/long on the Tokyo datum)." +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:19 +msgid "There is no update or creation support for this format." +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:21 +msgid "NOTE: Implemented as :source_file:`frmts/jdem/jdemdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:23 +msgid "" +"See Also: `Geographic Survey Institute (GSI) Web Site. " +"`__" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:5 +msgid "JP2ECW -- ERDAS JPEG2000 (.jp2)" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:7 +msgid "JP2ECW" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:11 +msgid "" +"GDAL supports reading and writing JPEG2000 files using the ERDAS ECW/JP2 " +"SDK developed by Hexagon Geospatial (formerly Intergraph, ERDAS, " +"ERMapper). Support is optional and requires linking in the libraries " +"available from the ECW/JP2 SDK Download page." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:16 +msgid "" +"Coordinate system and georeferencing transformations are read, and some " +"degree of support is included for GeoJP2 (tm) (GeoTIFF-in-JPEG2000), " +"ERDAS GML-in-JPEG2000, and the new GML-in-JPEG2000 specification " +"developed at OGC." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:51 +#: ../../source/drivers/raster/jp2kak.rst:99 +#: ../../source/drivers/raster/jp2lura.rst:31 +#: ../../source/drivers/raster/jp2mrsid.rst:29 +#: ../../source/drivers/raster/jp2openjpeg.rst:42 +msgid "" +"Georeferencing information can come from different sources : internal " +"(GeoJP2 or GMLJP2 boxes), worldfile .j2w/.wld sidecar files, or PAM " +"(Persistent Auxiliary metadata) .aux.xml sidecar files. By default, " +"information is fetched in following order (first listed is the highest " +"priority): PAM, GeoJP2, GMLJP2, WORLDFILE." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:57 +#: ../../source/drivers/raster/jp2kak.rst:105 +#: ../../source/drivers/raster/jp2mrsid.rst:35 +#: ../../source/drivers/raster/jp2openjpeg.rst:48 +msgid "" +"Starting with GDAL 2.2, the allowed sources and their priority order can " +"be changed with the :config:`GDAL_GEOREF_SOURCES` configuration option " +"(or :oo:`GEOREF_SOURCES` open option) whose value is a comma-separated " +"list of the following keywords : PAM, GEOJP2, GMLJP2, INTERNAL (shortcut " +"for GEOJP2,GMLJP2), WORLDFILE, NONE. Earlier mentioned sources take " +"priority over later ones. A non mentioned source will be ignored." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:64 +#: ../../source/drivers/raster/jp2kak.rst:112 +#: ../../source/drivers/raster/jp2lura.rst:44 +#: ../../source/drivers/raster/jp2mrsid.rst:42 +#: ../../source/drivers/raster/jp2openjpeg.rst:55 +msgid "" +"For example setting it to \"WORLDFILE,PAM,INTERNAL\" will make a " +"geotransformation matrix from a potential worldfile priority over PAM or " +"internal JP2 boxes. Setting it to \"PAM,WORLDFILE,GEOJP2\" will use the " +"mentioned sources and ignore GMLJP2 boxes." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:70 +#: ../../source/drivers/raster/jp2lura.rst:66 +#: ../../source/drivers/raster/jp2mrsid.rst:48 +#: ../../source/drivers/raster/jp2openjpeg.rst:84 +#: ../../source/drivers/raster/jpeg.rst:125 +#: ../../source/drivers/raster/jpegxl.rst:53 +#: ../../source/drivers/raster/pdf.rst:121 +#: ../../source/drivers/raster/rmf.rst:44 +msgid "Open Options" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:91 +msgid "|about-creation-options| Supported creation options are listed below." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:94 +msgid "" +"Note: Only Licensing and compression target need to be specified. The " +"ECW/JP2 SDK will default all other options to recommended settings based " +"on the input characteristics. Changing other options can *substantially* " +"impact decoding speed and compatibility with other JPEG2000 toolkits." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:267 +msgid "" +"If there are metadata domain whose name starts with \"xml:BOX\\_\", they " +"will be written each as separate JP2 XML box." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:270 +msgid "" +"If there is a metadata domain whose name is \"xml:XMP\", its content will" +" be written as a JP2 UUID XMP box." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:281 +msgid "" +"\"JPEG2000 format does not support creation of GDAL overviews since the " +"format is already considered to be optimized for \"arbitrary overviews\"." +" JP2ECW driver also arranges JP2 codestream to allow optimal access to " +"power of two overviews. This is controlled with the creation option " +"LEVELS.\"" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:288 +msgid "Create support" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:290 +msgid "" +"While the driver advertises the Create() capability, contrary to most " +"other drivers that implement it, the implementation of RasterIO() and " +"WriteBlock() in the JP2ECW driver does not support arbitrary random " +"writing. Data must be written in the dataset from top to bottom, whole " +"line(s) at a time." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:299 +msgid "" +"|about-config-options| The ERDAS ECW/JP2 SDK supports a variety of " +"runtime configuration options to control various features. See the " +"ECW/JP2 SDK documentation for full details on the meaning of these " +"options." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:304 +msgid ":copy-config:`ECW_CACHE_MAXMEM`" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:306 +msgid ":copy-config:`ECW_TEXTURE_DITHER`" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:340 +#: ../../source/drivers/raster/jp2openjpeg.rst:18 +#: ../../source/drivers/raster/mrsid.rst:51 +msgid "" +"XMP metadata can be extracted from JPEG2000 files, and will be stored as " +"XML raw content in the xml:XMP metadata domain." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:344 +msgid "" +"ECW/JP2 SDK v5.1+ also advertises JPEG2000 structural information as " +"generic File Metadata reported under \"JPEG2000\" metadata domain (-mdd):" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:347 +msgid "**ALL_COMMENTS**: Generic comment text field" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:348 +msgid "" +"**PROFILE**: Profile type (0,1,2). Refer to ECW/JP2 SDK documentation for" +" more info" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:350 +msgid "**TILES_X**: Number of tiles on X (horizontal) Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:351 +msgid "**TILES_Y**: Number of tiles on Y (vertical) Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:352 +msgid "**TILE_WIDTH**: Tile size on X Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:353 +msgid "**TILE_HEIGHT**: Tile size on Y Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:354 +msgid "" +"**PRECINCT_SIZE_X**: Precinct size for each resolution level (smallest to" +" largest) on X Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:356 +msgid "" +"**PRECINCT_SIZE_Y**: Precinct size for each resolution level (smallest to" +" largest) on Y Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:358 +msgid "**CODE_BLOCK_SIZE_X**: Code block size on X Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:359 +msgid "**CODE_BLOCK_SIZE_Y**: Code block size on Y Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:360 +msgid "" +"**PRECISION**: Precision / Bit-depth of each component eg. 8,8,8 for 8bit" +" 3 band imagery." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:362 +msgid "**RESOLUTION_LEVELS**: Number of resolution levels" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:363 +msgid "**QUALITY_LAYERS**: Number of quality layers" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:364 +msgid "**PROGRESSION_ORDER**: Progression order (RPCL, LRCP, CPRL, RLCP)" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:365 +msgid "**TRANSFORMATION_TYPE**: Filter transformation used (9x7, 5x3)" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:366 +msgid "**USE_SOP**: Start of Packet marker detected (TRUE/FALSE)" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:367 +msgid "**USE_EPH**: End of Packet header marker detected (TRUE/FALSE)" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:368 +msgid "**GML_JP2_DATA**: OGC GML GeoReferencing box detected (TRUE/FALSE)" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:369 +msgid "**COMPRESSION_RATE_TARGET**: Target compression rate used on encoding" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:375 +msgid "" +"ECW/JP2 SDK available at `www.hexagongeospatial.com " +"`__" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:377 +msgid "" +"Further product information available in the `User Guide " +"`__" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:379 +msgid "" +"Support for non-GDAL specific issues should be directed to the `Hexagon " +"Geospatial public forum " +"`__" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:5 +msgid "JP2KAK -- JPEG 2000 (based on Kakadu SDK)" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:7 +msgid "JP2KAK" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:11 +msgid "" +"The JP2KAK driver, which uses the proprietary `Kakadu SDK " +"`__, supports JPEG 2000 images, which are" +" specified in the Rec. ITU-T T.8xx | ISO/IEC 15444 family of standards. " +"JPEG 2000 uses a substantially different format and compression mechanism" +" than the traditional JPEG compression and JPEG JFIF format. JPEG and " +"JPEG 2000 are distinct compression standards produced by the same group. " +"JPEG 2000 is based on wavelet compression." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:18 +msgid "The driver includes support for:" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:20 +msgid "" +"reading both JPEG 2000 codestreams (.j2c or .jpc) and JP2 files (.jp2). " +"New images can be also written, but existing images cannot be updated in " +"place." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:23 +msgid "" +"lossy and lossless compression of 8-bit and 16-bit images with 1 or more " +"bands (components)." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:26 +msgid "" +"GeoTIFF style coordinate system and georeferencing information in JP2 " +"file via the `GeoJP2(tm) " +"`__" +" mechanism." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:31 +msgid "" +"JPEG 2000 Part 1 (Rec. ITU-T T.800 | ISO/IEC 15444-1), Part 2 (Rec. ITU-T" +" T.801 | ISO/IEC 15444-2) and Part 15 (HTJ2K) (Rec. ITU-T T.814 | ISO/IEC" +" 15444-15)" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:34 +msgid "" +"The Kakadu SDK is a high quality and high performance JPEG 2000 library " +"in wide used in the geospatial and general imaging community. However, it" +" is not free, and, by default, a builds of GDAL from source does not " +"include support for the JP2KAK driver. The builder must acquire a license" +" for the Kakadu SDK and configure GDAL accordingly." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:40 +msgid "" +"When reading images this driver will represent the bands as being Byte " +"(8-bit unsigned), 16-bit signed/unsigned, and 32-bit signed/unsigned. " +"Georeferencing and coordinate system information will be available if the" +" file is a GeoJP2 (tm) file. Files color encoded in YCbCr color space " +"will be automatically translated to RGB. Paletted images are also " +"supported." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:46 +msgid "" +"XMP metadata can be extracted from JPEG 2000 files, and will be stored as" +" XML raw content in the xml:XMP metadata domain." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:61 +msgid "" +"|about-config-options| The JP2KAK driver supports the following " +"configuration options:" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:118 +msgid "Option Options" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:139 +msgid "" +"JPEG 2000 files can only be created using the CreateCopy mechanism to " +"copy from an existing dataset." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:142 +msgid "" +"JPEG 2000 overviews are maintained as part of the mathematical " +"description of the image. Overviews cannot be built as a separate " +"process, but on read the image will generally be represented as having " +"overview levels at various power of two factors." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:233 +msgid "" +"The following creation options are tightly tied to the Kakadu SDK, and " +"are considered to be for advanced use only. Consult the Kakadu SDK " +"documentation to better understand their meaning." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:237 +msgid "**Corder**: Defaults to \"PRCL\"." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:238 +msgid "" +"**Cprecincts**: Defaults to " +"\"{512,512},{256,512},{128,512},{64,512},{32,512},{16,512},{8,512},{4,512},{2,512}\"." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:240 +msgid "**ORGgen_plt**: Defaults to \"yes\"." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:241 +msgid "**ORGgen_tlm**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:242 +msgid "**ORGtparts**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:243 +msgid "**Cmodes**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:244 +msgid "**Clevels**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:245 +msgid "**Rshift**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:246 +msgid "**Rlevels**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:247 +msgid "**Rweight**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:248 +msgid "**Qguard**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:249 +msgid "" +"**Creversible**: If not set and QUALITY >= 99.5, set to \"yes\", " +"otherwise to \"false\"." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:250 +msgid "**Sprofile**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:251 +msgid "" +"**RATE**: Kakadu SDK defaults used. One or more bit-rates, expressed in " +"terms of the ratio between the total number of compressed bits (including" +" headers) and the product of the largest horizontal and vertical image " +"component dimensions. A dash, -, may be used in place of the first bit-" +"rate in the list to indicate that the final quality layer should include " +"all compressed bits. If Clayers is not used, the number of layers is set " +"to the number of rates specified here. If Clayers is used to specify an " +"actual number of quality layers, one of the following must be true: 1) " +"the number of rates specified here is identical to the specified number " +"of layers; or 2) one or two rates are specified using this argument. " +"When two rates are specified, the number of layers must be 2 or more and " +"intervening layers will be assigned roughly logarithmically spaced bit-" +"rates. When only one rate is specified, an internal heuristic determines " +"a lower bound and logarithmically spaces the layer rates over the range. " +"The rates have to be in ASC order." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:263 +msgid "Known Kakadu SDK Issues" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:266 +msgid "Alpha Channel Writing in v7.8" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:268 +msgid "" +"Kakadu SDK v7.8 has a bug in jp2_channels::set_opacity_mapping that can " +"cause an error when writing images with an alpha channel. Please upgrade " +"to version 7.9." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:279 +msgid "kdu_get_num_processors always returns 0 for some platforms" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:281 +msgid "" +"On non-windows / non-mac installs (e.g. Linux), Kakadu SDK might not " +"include unistd.h in kdu_arch.cpp. This means that \\_SC_NPROCESSORS_ONLN " +"and \\_SC_NPROCESSORS_CONF are not defined and kdu_get_num_processors " +"will always return 0. Therefore the jp2kak driver might not default to " +"creating worker threads." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:290 +msgid "Implemented as :source_file:`frmts/jp2kak/jp2kakdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:291 +msgid "" +"If you're using a Kakadu SDK release before v7.5, configure & compile " +"GDAL with eg. `CXXFLAGS=\"-DKDU_MAJOR_VERSION=7 -DKDU_MINOR_VERSION=3 " +"-DKDU_PATCH_VERSION=2\"` for Kakadu SDK version 7.3.2." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:295 +msgid "Alternate :ref:`raster.jp2openjpeg` driver." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:5 +msgid "JP2Lura -- JPEG2000 driver based on Lurawave library" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:7 +msgid "JP2LURA" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:13 +msgid "" +"This driver is an implementation of a JPEG2000 reader/writer based on " +"Lurawave library." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:16 +#: ../../source/drivers/raster/jp2openjpeg.rst:15 +msgid "" +"The driver uses the VSI Virtual File API, so it can read JPEG2000 " +"compressed NITF files." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:37 +msgid "" +"The allowed sources and their priority order can be changed with the " +":config:`GDAL_GEOREF_SOURCES` configuration option (or " +":oo:`GEOREF_SOURCES` open option) whose value is a comma-separated list " +"of the following keywords : PAM, GEOJP2, GMLJP2, INTERNAL (shortcut for " +"GEOJP2,GMLJP2), WORLDFILE, NONE. Earlier mentioned sources take priority " +"over later ones. A non mentioned source will be ignored." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:52 +#: ../../source/drivers/raster/pdf.rst:58 +#: ../../source/drivers/vector/idb.rst:58 +msgid "|about-config-options| The following configuration options are supported:" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:68 +#: ../../source/drivers/raster/jp2mrsid.rst:50 +msgid "|about-open-options| The following open option is available:" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:330 +#: ../../source/drivers/raster/jp2openjpeg.rst:417 +msgid "" +"If there are metadata domain whose name starts with \"xml:BOX\\_\", they " +"will be written each as separate JP2 'xml ' box." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:333 +#: ../../source/drivers/raster/jp2openjpeg.rst:420 +msgid "" +"If there is a metadata domain whose name is \"xml:XMP\", its content will" +" be written as a JP2 'uuid' XMP box." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:355 +#: ../../source/drivers/raster/jp2openjpeg.rst:450 +msgid "Lossless compression" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:357 +msgid "" +"Lossless compression can be achieved if REVERSIBLE=YES is used (and RATE " +"is not specified)." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:361 +#: ../../source/drivers/raster/jp2openjpeg.rst:646 +msgid "Vector information" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:363 +#: ../../source/drivers/raster/jp2openjpeg.rst:648 +msgid "" +"A JPEG2000 file containing a GMLJP2 v2 box with GML feature collections " +"and/or KML annotations embedded can be opened as a vector file with the " +"OGR API. For example:" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:377 +#: ../../source/drivers/raster/jp2openjpeg.rst:662 +msgid "" +"Feature collections can be linked from the GMLJP2 v2 box to a remote " +"location. By default, the link is not followed. It will be followed if " +"the open option OPEN_REMOTE_GML is set to YES." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:382 +msgid "Bugs" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:384 +msgid "" +"Proper support of JPEG-2000 images with " +"Int32/UInt32/Float32-IEEE754-split on Linux 64 bits require a v2.1.00.17 " +"or later SDK." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:391 +msgid "" +"`LuraTech JPEG-2000 SDK " +"`__" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:394 +#: ../../source/drivers/raster/jp2openjpeg.rst:687 +msgid "Other JPEG2000 GDAL drivers :" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:396 +msgid "" +":ref:`JP2OpenJPEG: based on Openjpeg library (open source) " +"`" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:399 +#: ../../source/drivers/raster/jp2openjpeg.rst:689 +msgid ":ref:`JP2ECW: based on Erdas ECW library (proprietary) `" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:402 +#: ../../source/drivers/raster/jp2openjpeg.rst:692 +msgid "" +":ref:`JP2MRSID: based on LizardTech MrSID library (proprietary) " +"`" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:405 +#: ../../source/drivers/raster/jp2openjpeg.rst:695 +msgid ":ref:`JP2KAK: based on Kakadu library (proprietary) `" +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:5 +msgid "JP2MrSID -- JPEG2000 via MrSID SDK" +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:7 +msgid "JP2MrSID" +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:11 +msgid "" +"JPEG2000 file format is supported for reading with the MrSID DSDK. It is " +"also supported for writing with the MrSID ESDK." +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:14 +msgid "" +"JPEG2000 MrSID support is only available with the version 5.x or newer " +"DSDK and ESDK." +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:64 +msgid "" +"If you have the MrSID ESDK (5.x or newer), it can be used to write " +"JPEG2000 files. |about-creation-options| The following creation options " +"are supported." +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:129 +#: ../../source/drivers/raster/mrsid.rst:69 +msgid "Implemented as :source_file:`frmts/mrsid/mrsiddataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:130 +#: ../../source/drivers/raster/mrsid.rst:70 +msgid "`Extensis web site `__" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:5 +msgid "JP2OpenJPEG -- JPEG2000 driver based on OpenJPEG library" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:7 +msgid "JP2OpenJPEG" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:12 +msgid "" +"This driver is an implementation of a JPEG2000 reader/writer based on " +"OpenJPEG library **v2**." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:21 +msgid "" +"The driver supports writing georeferencing information as GeoJP2 and " +"GMLJP2 boxes." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:24 +msgid "" +"The driver supports creating files with transparency, arbitrary band " +"count, and adding/reading metadata. Update of georeferencing or metadata " +"of existing file is also supported. Optional intellectual property " +"metadata can be read/written in the xml:IPR box." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:61 +msgid "Thread support" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:63 +msgid "" +"By default, if the JPEG2000 file has internal tiling, GDAL will try to " +"decode several tiles in multiple threads if the RasterIO() request it " +"receives intersect several tiles. This behavior can be controlled with " +"the :config:`GDAL_NUM_THREADS` configuration option that defaults to " +"ALL_CPUS in that context. In case RAM is limited, it can be needed to set" +" this configuration option to 1 to disable multi-threading" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:70 +msgid "" +"Starting with OpenJPEG 2.2.0, multi-threaded decoding can also be enabled" +" at the code-block level. This must be enabled with the OPJ_NUM_THREADS " +"environment variable (note: this is a system environment variable, not a " +"GDAL configuration option), which can be set to a numeric value or " +"NUM_CPUS. Its default value is 1. Starting with GDAL 2.3, this multi-" +"threading at code-block level is automatically enabled by GDAL. Starting " +"with GDAL 3.0.1 and OpenJPEG 2.3.2, multi-threaded encoding is " +"automatically enabled and can be controlled with the OPJ_NUM_THREADS " +"environment variable or the :config:`GDAL_NUM_THREADS` configuration " +"option." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:81 +msgid "Both multi-threading mechanism can be combined together." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:354 +msgid "" +"(OpenJPEG >= 2.3.0) Style of the code-block coding passes. The following " +"6 independent settings can be combined together (values should be comma " +"separated):" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:358 +msgid "" +"*BYPASS* (1): enable selective arithmetic coding bypass (can " +"substantially improve coding/decoding speed, at the expense of larger " +"file size)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:361 +msgid "*RESET* (2): reset context probabilities on coding pass boundaries" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:362 +msgid "*TERMALL* (4): enable termination on each coding pass" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:363 +msgid "*VSC* (8): enable vertically causal context" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:364 +msgid "" +"*PREDICTABLE* (16): enable predictable termination (helps for error " +"detection)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:366 +msgid "*SEGSYM* (32): enable segmentation symbols (helps for error detection)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:369 +msgid "" +"Instead of specifying them by text, it is also possible to give the " +"corresponding numeric value of the global codeblock style, by adding the " +"selected options (for example \"BYPASS,TERMALL\" is equivalent to " +"\"5\"=1+4)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:374 +msgid "" +"By default, none of them are enabled. Enabling them will generally " +"increase codestream size, but improve either coding/decoding speed or " +"resilience/error detection." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:423 +msgid "" +"If there is a metadata domain whose name is \"xml:IPR\", its content will" +" be written as a JP2 'jp2i' box." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:452 +msgid "" +"Lossless compression can be achieved if ALL the following creation " +"options are defined :" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:455 +msgid ":co:`QUALITY=100`" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:456 +msgid ":co:`REVERSIBLE=YES`" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:457 +msgid ":co:`YCBCR420=NO` (which is the default)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:462 +msgid "GMLJP2v2 definition file" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:464 +msgid "" +"A GMLJP2v2 box typically contains a GMLJP2RectifiedGridCoverage with the " +"SRS information and geotransformation matrix. It is also possible to add " +"metadata, vector features (GML feature collections), annotations (KML), " +"styles (typically SLD, or other XML format) or any XML content as an " +"extension. The value of the GMLJP2V2_DEF creation option should be a file" +" that conforms with the below syntax (elements starting with \"#\" are " +"documentation, and can be omitted):" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:629 +msgid "" +"Metadata can be dynamically generated from a template file (in that " +"context, with a XML structure) and a XML source file. The template file " +"is processed by searching for patterns like {{{XPATH(xpath_expr)}}} and " +"replacing them by their evaluation against the content of the source " +"file. xpath_expr must be a XPath 1.0 compatible expression, with the " +"addition of the following functions :" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:636 +msgid "" +"**if(cond_expr,expr_if_true,expr_if_false)**: if cond_expr evaluates to " +"true, returns expr_if_true. Otherwise returns expr_if_false" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:638 +msgid "**uuid()**: evaluates to a random UUID" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:640 +msgid "" +"A template file to process XML metadata of Pleiades imagery can be found " +"`here `__, and a template file to process XML " +"metadata of GeoEye/WorldView imagery can be found `here " +"`__." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:669 +msgid "Implemented as :source_file:`frmts/openjpeg/openjpegdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:671 +msgid "`Official JPEG-2000 page `__" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:673 +msgid "`The OpenJPEG library home page `__" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:676 +msgid "" +"`OGC GML in JPEG2000, version 2.0 " +"`__ (GDAL 2.0 " +"and 2.1)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:680 +msgid "" +"`OGC GML in JPEG2000, version 2.0.1 " +"`__ (GDAL 2.2 " +"and above)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:684 +msgid "" +"`Inspire Data Specification on Orthoimagery - Technical Guidelines " +"`__" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:5 +msgid "JPEG -- JPEG JFIF File Format" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:7 +msgid "JPEG" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:11 +msgid "" +"The JPEG JFIF format is supported for reading, and batch writing, but not" +" update in place. JPEG files are represented as one band (greyscale) or " +"three band (RGB) datasets with Byte valued bands." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:15 +msgid "" +"The driver will automatically convert images whose color space is YCbCr, " +"CMYK or YCbCrK to RGB, unless :config:`GDAL_JPEG_TO_RGB` is set to NO " +"(YES is the default). When color space translation to RGB is done, the " +"source color space is indicated in the SOURCE_COLOR_SPACE metadata of the" +" IMAGE_STRUCTURE domain." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:21 +msgid "" +"EXIF metadata can be read from JPEG files (but this will not result in a " +"georeferenced image even if the EXIF_GPSLatitude and EXIF_GPSLongitude " +"tags are set). But if an ESRI world file exists with the .jgw, " +".jpgw/.jpegw or .wld suffixes, it will be read and used to establish the " +"geotransform for the image. If available a MapInfo .tab file will also be" +" used for georeferencing. Overviews can be built for JPEG files as an " +"external .ovr file." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:29 +msgid "" +"The driver also supports the \"zlib compressed mask appended to the " +"file\" approach used by a few data providers to add a bitmask to identify" +" pixels that are not valid data. See :ref:`rfc-15` for further details." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:34 +msgid "" +"The driver can deal with bitmask where the bits are ordered with most " +"significant bit first (whereas the usual convention is least significant " +"bit first). The driver will try to autodetect that situation, but the " +"heuristics may fail. In that circumstance, you can set the " +":config:`JPEG_MASK_BIT_ORDER` configuration option to MSB. Bitmask can " +"also be completely ignored by specifying :config:`JPEG_READ_MASK=NO`." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:42 +msgid "" +"The GDAL JPEG Driver is built using the Independent JPEG Group's jpeg " +"library. Also note that the GeoTIFF driver supports tiled TIFF with JPEG " +"compressed tiles. This can be used to apply JPEG compression to datasets " +"that exceed the maximum dimensions of 65,535x65,535 pixels for a single " +"JPEG image." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:48 +msgid "" +"It is also possible to use the JPEG driver with the libjpeg-turbo, a " +"version of libjpeg, API and ABI compatible with IJG libjpeg-6b, which " +"uses MMX, SSE, and SSE2 SIMD instructions to accelerate baseline JPEG " +"compression/decompression." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:53 +msgid "" +"Starting with GDAL 3.4, read and write support for JPEG images with " +"12-bit sample is enabled by default (if JPEG support is also enabled), " +"using GDAL internal libjpeg (based on IJG libjpeg-6b, with additional " +"changes for 12-bit sample support). Support for JPEG with 12-bit sample " +"is independent of whether 8-bit JPEG support is enabled through internal " +"IJG libjpeg-6b or external libjpeg (like libjpeg-turbo)" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:63 +msgid "" +"Embedded EXIF thumbnails (with JPEG compression) can be used as " +"overviews, and generated by GDAL." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:81 +#: ../../source/drivers/raster/jpegxl.rst:50 +msgid "SOURCE_ICC_PROFILE (Base64 encoded ICC profile embedded in file.)" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:83 +msgid "" +"Note that this metadata property can only be used on the original raw " +"pixel data. If automatic conversion to RGB has been done, the color " +"profile information cannot be used." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:87 +msgid "This metadata tag can be used as creation options." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:150 +msgid "" +"JPEG files are created using the \"JPEG\" driver code. Only Byte band " +"types are supported." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:153 +msgid "" +"Only 1 (greyscale), 3 band (input should be in RGB colorspace. the driver" +" will convert it automatically to YCbCr colorspace for storage, and will " +"expose it back as RGB on reading) or 4 band (input should already by in " +"CMYK colorspace. It will be exposed as RGB on reading by default, unless " +"the :config:`GDAL_JPEG_TO_RGB` configuration option is set to NO) " +"configurations." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:160 +msgid "" +"JPEG file creation is implemented by the batch (CreateCopy) method. " +"YCbCrK colorspace is not supported in creation. If the source dataset has" +" a nodata mask, it will be appended as a zlib compressed mask to the JPEG" +" file." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:276 +msgid "EXIF and GPS tags" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:278 +msgid "The below tables list the EXIF and GPS tags that can be written." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:280 +msgid "" +"The \"Metadata item name\" column presents the name of the metadata item " +"to attach to the source dataset." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:282 +msgid "" +"The \"Hex code\" column is the value of the corresponding TIFF EXIF/GPS " +"tag (for reference only)" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst +msgid "The \"Type\" column is the TIFF type associated." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:286 +msgid "" +"ASCII is for text values that are NUL-terminated (for a fixed length tag," +" the length includes this NUL-terminating characters). e.g " +"EXIF_Make=the_make" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:289 +msgid "" +"BYTE/UNDEFINED is for values that can be made of any byte value. The " +"value of the corresponding GDAL metadata item must be a string of " +"hexadecimal formatted values, e.g EXIF_GPSVersionID=0x02 0x00 0x00 0x00. " +"GDAL also accepts an ASCII string: e.g. EXIF_ExifVersion=0231" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:294 +msgid "" +"SHORT is for unsigned integer values in the range [0,65535]. Some tags " +"may accept multiple values, in which case they must be separated by " +"space." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:297 +msgid "" +"LONG is for unsigned integer values in the range [0,4294967295]. Some " +"tags may accept multiple values, in which case they must be separated by " +"space." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:300 +msgid "" +"RATIONAL is for positive floating-point values. Some tags may accept " +"multiple values, in which case they must be separated by space. e.g " +"EXIF_GPSLatitude=49 2 3.5" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:303 +msgid "" +"SRATIONAL is for positive or negative floating-point values. Some tags " +"may accept multiple values, in which case they must be separated by " +"space." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:307 +msgid "" +"When an item accepts a fixed number of values and that more are provided," +" they will be truncated with a warning. In the case they are less values " +"provided than needed, they will be padded with appropriate spaces / " +"zeroes" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:312 +msgid "" +"The \"Number of values\" column is the number of values for the item. " +"Might be \"variable\" if there is no restriction, or a fixed value. For " +"Type=ASCII, the fixed value includes the NUL-terminating byte, so the " +"number of actual printable characters is number of values - 1." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:316 +msgid "" +"The \"Optionality\" column indicates whether the item should be present " +"(\"Mandatory\"), is \"Recommended\" or \"Optional\". GDAL does not " +"enforce this." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:320 +msgid "" +"Many items have more restrictions on the valid content that are not " +"expressed in the below tables. Consult the EXIF specification for more " +"information." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:325 +#: ../../source/drivers/raster/jpeg.rst:421 +msgid "Metadata item name" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:325 +#: ../../source/drivers/raster/jpeg.rst:421 +msgid "Hex code" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:325 +#: ../../source/drivers/raster/jpeg.rst:421 +#: ../../source/drivers/vector/eeda.rst:103 +#: ../../source/drivers/vector/geopackage_aspatial.rst:95 +msgid "Type" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:325 +#: ../../source/drivers/raster/jpeg.rst:421 +msgid "Number of values" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:325 +#: ../../source/drivers/raster/jpeg.rst:421 +msgid "Optionality" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:327 +msgid "EXIF_Document_Name" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:327 +msgid "0x010D" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:327 +#: ../../source/drivers/raster/jpeg.rst:328 +#: ../../source/drivers/raster/jpeg.rst:329 +#: ../../source/drivers/raster/jpeg.rst:330 +#: ../../source/drivers/raster/jpeg.rst:336 +#: ../../source/drivers/raster/jpeg.rst:337 +#: ../../source/drivers/raster/jpeg.rst:338 +#: ../../source/drivers/raster/jpeg.rst:344 +#: ../../source/drivers/raster/jpeg.rst:348 +#: ../../source/drivers/raster/jpeg.rst:358 +#: ../../source/drivers/raster/jpeg.rst:359 +#: ../../source/drivers/raster/jpeg.rst:360 +#: ../../source/drivers/raster/jpeg.rst:361 +#: ../../source/drivers/raster/jpeg.rst:362 +#: ../../source/drivers/raster/jpeg.rst:378 +#: ../../source/drivers/raster/jpeg.rst:379 +#: ../../source/drivers/raster/jpeg.rst:380 +#: ../../source/drivers/raster/jpeg.rst:385 +#: ../../source/drivers/raster/jpeg.rst:409 +#: ../../source/drivers/raster/jpeg.rst:410 +#: ../../source/drivers/raster/jpeg.rst:411 +#: ../../source/drivers/raster/jpeg.rst:413 +#: ../../source/drivers/raster/jpeg.rst:414 +#: ../../source/drivers/raster/jpeg.rst:415 +#: ../../source/drivers/raster/jpeg.rst:424 +#: ../../source/drivers/raster/jpeg.rst:426 +#: ../../source/drivers/raster/jpeg.rst:431 +#: ../../source/drivers/raster/jpeg.rst:432 +#: ../../source/drivers/raster/jpeg.rst:433 +#: ../../source/drivers/raster/jpeg.rst:435 +#: ../../source/drivers/raster/jpeg.rst:437 +#: ../../source/drivers/raster/jpeg.rst:439 +#: ../../source/drivers/raster/jpeg.rst:441 +#: ../../source/drivers/raster/jpeg.rst:442 +#: ../../source/drivers/raster/jpeg.rst:444 +#: ../../source/drivers/raster/jpeg.rst:446 +#: ../../source/drivers/raster/jpeg.rst:448 +#: ../../source/drivers/raster/jpeg.rst:452 +msgid "ASCII" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:327 +#: ../../source/drivers/raster/jpeg.rst:335 +#: ../../source/drivers/raster/jpeg.rst:336 +#: ../../source/drivers/raster/jpeg.rst:338 +#: ../../source/drivers/raster/jpeg.rst:339 +#: ../../source/drivers/raster/jpeg.rst:340 +#: ../../source/drivers/raster/jpeg.rst:341 +#: ../../source/drivers/raster/jpeg.rst:343 +#: ../../source/drivers/raster/jpeg.rst:344 +#: ../../source/drivers/raster/jpeg.rst:346 +#: ../../source/drivers/raster/jpeg.rst:347 +#: ../../source/drivers/raster/jpeg.rst:348 +#: ../../source/drivers/raster/jpeg.rst:349 +#: ../../source/drivers/raster/jpeg.rst:350 +#: ../../source/drivers/raster/jpeg.rst:351 +#: ../../source/drivers/raster/jpeg.rst:352 +#: ../../source/drivers/raster/jpeg.rst:353 +#: ../../source/drivers/raster/jpeg.rst:354 +#: ../../source/drivers/raster/jpeg.rst:355 +#: ../../source/drivers/raster/jpeg.rst:356 +#: ../../source/drivers/raster/jpeg.rst:358 +#: ../../source/drivers/raster/jpeg.rst:359 +#: ../../source/drivers/raster/jpeg.rst:360 +#: ../../source/drivers/raster/jpeg.rst:361 +#: ../../source/drivers/raster/jpeg.rst:362 +#: ../../source/drivers/raster/jpeg.rst:364 +#: ../../source/drivers/raster/jpeg.rst:365 +#: ../../source/drivers/raster/jpeg.rst:366 +#: ../../source/drivers/raster/jpeg.rst:367 +#: ../../source/drivers/raster/jpeg.rst:368 +#: ../../source/drivers/raster/jpeg.rst:369 +#: ../../source/drivers/raster/jpeg.rst:370 +#: ../../source/drivers/raster/jpeg.rst:371 +#: ../../source/drivers/raster/jpeg.rst:372 +#: ../../source/drivers/raster/jpeg.rst:374 +#: ../../source/drivers/raster/jpeg.rst:375 +#: ../../source/drivers/raster/jpeg.rst:376 +#: ../../source/drivers/raster/jpeg.rst:377 +#: ../../source/drivers/raster/jpeg.rst:378 +#: ../../source/drivers/raster/jpeg.rst:379 +#: ../../source/drivers/raster/jpeg.rst:380 +#: ../../source/drivers/raster/jpeg.rst:385 +#: ../../source/drivers/raster/jpeg.rst:386 +#: ../../source/drivers/raster/jpeg.rst:387 +#: ../../source/drivers/raster/jpeg.rst:388 +#: ../../source/drivers/raster/jpeg.rst:389 +#: ../../source/drivers/raster/jpeg.rst:390 +#: ../../source/drivers/raster/jpeg.rst:391 +#: ../../source/drivers/raster/jpeg.rst:392 +#: ../../source/drivers/raster/jpeg.rst:393 +#: ../../source/drivers/raster/jpeg.rst:394 +#: ../../source/drivers/raster/jpeg.rst:395 +#: ../../source/drivers/raster/jpeg.rst:396 +#: ../../source/drivers/raster/jpeg.rst:397 +#: ../../source/drivers/raster/jpeg.rst:400 +#: ../../source/drivers/raster/jpeg.rst:401 +#: ../../source/drivers/raster/jpeg.rst:403 +#: ../../source/drivers/raster/jpeg.rst:404 +#: ../../source/drivers/raster/jpeg.rst:405 +#: ../../source/drivers/raster/jpeg.rst:406 +#: ../../source/drivers/raster/jpeg.rst:407 +#: ../../source/drivers/raster/jpeg.rst:408 +#: ../../source/drivers/raster/jpeg.rst:409 +#: ../../source/drivers/raster/jpeg.rst:410 +#: ../../source/drivers/raster/jpeg.rst:411 +#: ../../source/drivers/raster/jpeg.rst:412 +#: ../../source/drivers/raster/jpeg.rst:413 +#: ../../source/drivers/raster/jpeg.rst:414 +#: ../../source/drivers/raster/jpeg.rst:415 +#: ../../source/drivers/raster/jpeg.rst:423 +#: ../../source/drivers/raster/jpeg.rst:424 +#: ../../source/drivers/raster/jpeg.rst:425 +#: ../../source/drivers/raster/jpeg.rst:426 +#: ../../source/drivers/raster/jpeg.rst:427 +#: ../../source/drivers/raster/jpeg.rst:428 +#: ../../source/drivers/raster/jpeg.rst:429 +#: ../../source/drivers/raster/jpeg.rst:430 +#: ../../source/drivers/raster/jpeg.rst:431 +#: ../../source/drivers/raster/jpeg.rst:432 +#: ../../source/drivers/raster/jpeg.rst:433 +#: ../../source/drivers/raster/jpeg.rst:434 +#: ../../source/drivers/raster/jpeg.rst:435 +#: ../../source/drivers/raster/jpeg.rst:436 +#: ../../source/drivers/raster/jpeg.rst:437 +#: ../../source/drivers/raster/jpeg.rst:438 +#: ../../source/drivers/raster/jpeg.rst:439 +#: ../../source/drivers/raster/jpeg.rst:440 +#: ../../source/drivers/raster/jpeg.rst:441 +#: ../../source/drivers/raster/jpeg.rst:442 +#: ../../source/drivers/raster/jpeg.rst:443 +#: ../../source/drivers/raster/jpeg.rst:444 +#: ../../source/drivers/raster/jpeg.rst:445 +#: ../../source/drivers/raster/jpeg.rst:446 +#: ../../source/drivers/raster/jpeg.rst:447 +#: ../../source/drivers/raster/jpeg.rst:448 +#: ../../source/drivers/raster/jpeg.rst:449 +#: ../../source/drivers/raster/jpeg.rst:450 +#: ../../source/drivers/raster/jpeg.rst:451 +#: ../../source/drivers/raster/jpeg.rst:452 +#: ../../source/drivers/raster/jpeg.rst:453 +#: ../../source/drivers/raster/jpeg.rst:454 +msgid "Optional" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:328 +msgid "EXIF_ImageDescription" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:328 +msgid "0x010E" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:328 +#: ../../source/drivers/raster/jpeg.rst:329 +#: ../../source/drivers/raster/jpeg.rst:330 +#: ../../source/drivers/raster/jpeg.rst:331 +#: ../../source/drivers/raster/jpeg.rst:337 +#: ../../source/drivers/raster/jpeg.rst:345 +#: ../../source/drivers/raster/jpeg.rst:373 +#: ../../source/drivers/raster/jpeg.rst:398 +#: ../../source/drivers/raster/jpeg.rst:399 +#: ../../source/drivers/raster/jpeg.rst:402 +msgid "Recommended" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:329 +msgid "EXIF_Make" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:329 +msgid "0x010F" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:330 +msgid "EXIF_Model" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:330 +msgid "0x0110" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:331 +msgid "EXIF_Orientation" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:331 +msgid "0x0112" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:331 +#: ../../source/drivers/raster/jpeg.rst:334 +#: ../../source/drivers/raster/jpeg.rst:335 +#: ../../source/drivers/raster/jpeg.rst:342 +#: ../../source/drivers/raster/jpeg.rst:347 +#: ../../source/drivers/raster/jpeg.rst:349 +#: ../../source/drivers/raster/jpeg.rst:351 +#: ../../source/drivers/raster/jpeg.rst:371 +#: ../../source/drivers/raster/jpeg.rst:372 +#: ../../source/drivers/raster/jpeg.rst:373 +#: ../../source/drivers/raster/jpeg.rst:375 +#: ../../source/drivers/raster/jpeg.rst:382 +#: ../../source/drivers/raster/jpeg.rst:390 +#: ../../source/drivers/raster/jpeg.rst:391 +#: ../../source/drivers/raster/jpeg.rst:393 +#: ../../source/drivers/raster/jpeg.rst:397 +#: ../../source/drivers/raster/jpeg.rst:398 +#: ../../source/drivers/raster/jpeg.rst:399 +#: ../../source/drivers/raster/jpeg.rst:401 +#: ../../source/drivers/raster/jpeg.rst:402 +#: ../../source/drivers/raster/jpeg.rst:404 +#: ../../source/drivers/raster/jpeg.rst:405 +#: ../../source/drivers/raster/jpeg.rst:406 +#: ../../source/drivers/raster/jpeg.rst:408 +#: ../../source/drivers/raster/jpeg.rst:453 +msgid "SHORT" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:332 +msgid "EXIF_XResolution" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:332 +msgid "0x011A" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:332 +#: ../../source/drivers/raster/jpeg.rst:333 +#: ../../source/drivers/raster/jpeg.rst:339 +#: ../../source/drivers/raster/jpeg.rst:340 +#: ../../source/drivers/raster/jpeg.rst:341 +#: ../../source/drivers/raster/jpeg.rst:343 +#: ../../source/drivers/raster/jpeg.rst:345 +#: ../../source/drivers/raster/jpeg.rst:346 +#: ../../source/drivers/raster/jpeg.rst:364 +#: ../../source/drivers/raster/jpeg.rst:366 +#: ../../source/drivers/raster/jpeg.rst:369 +#: ../../source/drivers/raster/jpeg.rst:370 +#: ../../source/drivers/raster/jpeg.rst:374 +#: ../../source/drivers/raster/jpeg.rst:386 +#: ../../source/drivers/raster/jpeg.rst:388 +#: ../../source/drivers/raster/jpeg.rst:389 +#: ../../source/drivers/raster/jpeg.rst:392 +#: ../../source/drivers/raster/jpeg.rst:400 +#: ../../source/drivers/raster/jpeg.rst:403 +#: ../../source/drivers/raster/jpeg.rst:412 +#: ../../source/drivers/raster/jpeg.rst:425 +#: ../../source/drivers/raster/jpeg.rst:427 +#: ../../source/drivers/raster/jpeg.rst:429 +#: ../../source/drivers/raster/jpeg.rst:430 +#: ../../source/drivers/raster/jpeg.rst:434 +#: ../../source/drivers/raster/jpeg.rst:436 +#: ../../source/drivers/raster/jpeg.rst:438 +#: ../../source/drivers/raster/jpeg.rst:440 +#: ../../source/drivers/raster/jpeg.rst:443 +#: ../../source/drivers/raster/jpeg.rst:445 +#: ../../source/drivers/raster/jpeg.rst:447 +#: ../../source/drivers/raster/jpeg.rst:449 +#: ../../source/drivers/raster/jpeg.rst:454 +msgid "RATIONAL" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:332 +#: ../../source/drivers/raster/jpeg.rst:333 +#: ../../source/drivers/raster/jpeg.rst:334 +#: ../../source/drivers/raster/jpeg.rst:342 +#: ../../source/drivers/raster/jpeg.rst:357 +#: ../../source/drivers/raster/jpeg.rst:363 +#: ../../source/drivers/raster/jpeg.rst:381 +#: ../../source/drivers/raster/jpeg.rst:382 +#: ../../source/drivers/raster/jpeg.rst:383 +#: ../../source/drivers/raster/jpeg.rst:384 +msgid "**Mandatory**" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:333 +msgid "EXIF_YResolution" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:333 +msgid "0x011B" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:334 +msgid "EXIF_ResolutionUnit" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:334 +msgid "0x0128" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:335 +msgid "EXIF_TransferFunction" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:335 +msgid "0x012D" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:335 +msgid "768" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:336 +msgid "EXIF_Software" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:336 +msgid "0x0131" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:337 +msgid "EXIF_DateTime" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:337 +msgid "0x0132" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:338 +msgid "EXIF_Artist" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:338 +msgid "0x013B" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:339 +msgid "EXIF_WhitePoint" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:339 +msgid "0x013E" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:340 +msgid "EXIF_PrimaryChromaticities" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:340 +msgid "0x013F" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:340 +#: ../../source/drivers/raster/jpeg.rst:343 +msgid "6" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:341 +msgid "EXIF_YCbCrCoefficients" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:341 +msgid "0x0211" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:341 +#: ../../source/drivers/raster/jpeg.rst:425 +#: ../../source/drivers/raster/jpeg.rst:427 +#: ../../source/drivers/raster/jpeg.rst:430 +#: ../../source/drivers/raster/jpeg.rst:443 +#: ../../source/drivers/raster/jpeg.rst:445 +#: ../../source/drivers/vector/netcdf.rst:251 +msgid "3" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:342 +msgid "EXIF_YCbCrPositioning" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:342 +msgid "0x0213" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:343 +msgid "EXIF_ReferenceBlackWhite" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:343 +msgid "0x0214" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:344 +msgid "EXIF_Copyright" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:344 +msgid "0x8298" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:345 +msgid "EXIF_ExposureTime" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:345 +msgid "0x829A" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:346 +msgid "EXIF_FNumber" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:346 +msgid "0x829D" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:347 +msgid "EXIF_ExposureProgram" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:347 +msgid "0x8822" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:348 +msgid "EXIF_SpectralSensitivity" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:348 +msgid "0x8824" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:349 +msgid "EXIF_ISOSpeedRatings" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:349 +msgid "0x8827" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:350 +msgid "EXIF_OECF" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:350 +msgid "0x8828" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:350 +#: ../../source/drivers/raster/jpeg.rst:357 +#: ../../source/drivers/raster/jpeg.rst:363 +#: ../../source/drivers/raster/jpeg.rst:376 +#: ../../source/drivers/raster/jpeg.rst:377 +#: ../../source/drivers/raster/jpeg.rst:381 +#: ../../source/drivers/raster/jpeg.rst:387 +#: ../../source/drivers/raster/jpeg.rst:394 +#: ../../source/drivers/raster/jpeg.rst:395 +#: ../../source/drivers/raster/jpeg.rst:396 +#: ../../source/drivers/raster/jpeg.rst:407 +#: ../../source/drivers/raster/jpeg.rst:450 +#: ../../source/drivers/raster/jpeg.rst:451 +msgid "UNDEFINED" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:351 +msgid "EXIF_SensitivityType" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:351 +msgid "0x8830" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:352 +msgid "EXIF_StandardOutputSensitivity" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:352 +msgid "0x8831" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:352 +#: ../../source/drivers/raster/jpeg.rst:353 +#: ../../source/drivers/raster/jpeg.rst:354 +#: ../../source/drivers/raster/jpeg.rst:355 +#: ../../source/drivers/raster/jpeg.rst:356 +#: ../../source/drivers/raster/jpeg.rst:383 +#: ../../source/drivers/raster/jpeg.rst:384 +msgid "LONG" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:353 +msgid "EXIF_RecommendedExposureIndex" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:353 +msgid "0x8832" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:354 +msgid "EXIF_ISOSpeed" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:354 +msgid "0x8833" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:355 +msgid "EXIF_ISOSpeedLatitudeyyy" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:355 +msgid "0x8834" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:356 +msgid "EXIF_ISOSpeedLatitudezzz" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:356 +msgid "0x8835" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:357 +msgid "EXIF_ExifVersion" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:357 +msgid "0x9000" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:358 +msgid "EXIF_DateTimeOriginal" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:358 +msgid "0x9003" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:359 +msgid "EXIF_DateTimeDigitized" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:359 +msgid "0x9004" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:360 +msgid "EXIF_OffsetTime" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:360 +msgid "0x9010" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:360 +#: ../../source/drivers/raster/jpeg.rst:361 +#: ../../source/drivers/raster/jpeg.rst:362 +msgid "7" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:361 +msgid "EXIF_OffsetTimeOriginal" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:361 +msgid "0x9011" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:362 +msgid "EXIF_OffsetTimeDigitized" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:362 +msgid "0x9012" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:363 +msgid "EXIF_ComponentsConfiguration" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:363 +msgid "0x9101" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:364 +msgid "EXIF_CompressedBitsPerPixel" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:364 +msgid "0x9102" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:365 +msgid "EXIF_ShutterSpeedValue" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:365 +msgid "0x9201" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:365 +#: ../../source/drivers/raster/jpeg.rst:367 +#: ../../source/drivers/raster/jpeg.rst:368 +msgid "SRATIONAL" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:366 +msgid "EXIF_ApertureValue" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:366 +msgid "0x9202" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:367 +msgid "EXIF_BrightnessValue" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:367 +msgid "0x9203" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:368 +msgid "EXIF_ExposureBiasValue" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:368 +msgid "0x9204" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:369 +msgid "EXIF_MaxApertureValue" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:369 +msgid "0x9205" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:370 +msgid "EXIF_SubjectDistance" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:370 +msgid "0x9206" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:371 +msgid "EXIF_MeteringMode" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:371 +msgid "0x9207" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:372 +msgid "EXIF_LightSource" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:372 +msgid "0x9208" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:373 +msgid "EXIF_Flash" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:373 +msgid "0x9209" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:374 +msgid "EXIF_FocalLength" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:374 +msgid "0x920A" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:375 +msgid "EXIF_SubjectArea" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:375 +msgid "0x9214" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:376 +msgid "EXIF_MakerNote" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:376 +msgid "0x927C" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:377 +msgid "EXIF_UserComment" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:377 +msgid "0x9286" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:378 +msgid "EXIF_SubSecTime" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:378 +msgid "0x9290" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:379 +msgid "EXIF_SubSecTime_Original" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:379 +msgid "0x9291" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:380 +msgid "EXIF_SubSecTime_Digitized" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:380 +msgid "0x9292" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:381 +msgid "EXIF_FlashpixVersion" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:381 +msgid "0xA000" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:382 +msgid "EXIF_ColorSpace" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:382 +msgid "0xA001" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:383 +msgid "EXIF_PixelXDimension" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:383 +msgid "0xA002" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:384 +msgid "EXIF_PixelYDimension" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:384 +msgid "0xA003" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:385 +msgid "EXIF_RelatedSoundFile" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:385 +msgid "0xA004" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:385 +msgid "13" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:386 +msgid "EXIF_FlashEnergy" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:386 +msgid "0xA20B" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:387 +msgid "EXIF_SpatialFrequencyResponse" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:387 +msgid "0xA20C" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:388 +msgid "EXIF_FocalPlaneXResolution" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:388 +msgid "0xA20E" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:389 +msgid "EXIF_FocalPlaneYResolution" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:389 +msgid "0xA20F" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:390 +msgid "EXIF_FocalPlaneResolutionUnit" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:390 +msgid "0xA210" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:391 +msgid "EXIF_SubjectLocation" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:391 +msgid "0xA214" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:392 +msgid "EXIF_ExposureIndex" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:392 +msgid "0xA215" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:393 +msgid "EXIF_SensingMethod" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:393 +msgid "0xA217" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:394 +msgid "EXIF_FileSource" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:394 +msgid "0xA300" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:395 +msgid "EXIF_SceneType" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:395 +msgid "0xA301" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:396 +msgid "EXIF_CFAPattern" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:396 +msgid "0xA302" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:397 +msgid "EXIF_CustomRendered" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:397 +msgid "0xA401" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:398 +msgid "EXIF_ExposureMode" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:398 +msgid "0xA402" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:399 +msgid "EXIF_WhiteBalance" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:399 +msgid "0xA403" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:400 +msgid "EXIF_DigitalZoomRatio" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:400 +msgid "0xA404" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:401 +msgid "EXIF_FocalLengthIn35mmFilm" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:401 +msgid "0xA405" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:402 +msgid "EXIF_SceneCaptureType" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:402 +msgid "0xA406" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:403 +msgid "EXIF_GainControl" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:403 +msgid "0xA407" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:404 +msgid "EXIF_Contrast" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:404 +msgid "0xA408" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:405 +msgid "EXIF_Saturation" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:405 +msgid "0xA409" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:406 +msgid "EXIF_Sharpness" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:406 +msgid "0xA40A" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:407 +msgid "EXIF_DeviceSettingDescription" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:407 +msgid "0xA40B" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:408 +msgid "EXIF_SubjectDistanceRange" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:408 +msgid "0xA40C" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:409 +msgid "EXIF_ImageUniqueID" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:409 +msgid "0xA420" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:409 +msgid "33" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:410 +msgid "EXIF_CameraOwnerName" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:410 +msgid "0xA430" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:411 +msgid "EXIF_BodySerialNumber" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:411 +msgid "0xA431" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:412 +msgid "EXIF_LensSpecification" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:412 +msgid "0xA432" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:413 +msgid "EXIF_LensMake" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:413 +msgid "0xA433" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:414 +msgid "EXIF_LensModel" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:414 +msgid "0xA434" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:415 +msgid "EXIF_LensSerialNumber" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:415 +msgid "0xA435" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:418 +msgid "GPS tags:" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:423 +msgid "EXIF_GPSVersionID" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:423 +msgid "0x0000" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:423 +#: ../../source/drivers/raster/jpeg.rst:428 +msgid "BYTE" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:424 +msgid "EXIF_GPSLatitudeRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:424 +msgid "0x0001" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:425 +msgid "EXIF_GPSLatitude" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:425 +msgid "0x0002" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:426 +msgid "EXIF_GPSLongitudeRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:426 +msgid "0x0003" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:427 +msgid "EXIF_GPSLongitude" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:427 +msgid "0x0004" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:428 +msgid "EXIF_GPSAltitudeRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:428 +msgid "0x0005" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:429 +msgid "EXIF_GPSAltitude" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:429 +msgid "0x0006" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:430 +msgid "EXIF_GPSTimeStamp" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:430 +msgid "0x0007" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:431 +msgid "EXIF_GPSSatellites" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:431 +msgid "0x0008" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:432 +msgid "EXIF_GPSStatus" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:432 +msgid "0x0009" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:433 +msgid "EXIF_GPSMeasureMode" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:433 +msgid "0x000A" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:434 +msgid "EXIF_GPSDOP" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:434 +msgid "0x000B" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:435 +msgid "EXIF_GPSSpeedRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:435 +msgid "0x000C" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:436 +msgid "EXIF_GPSSpeed" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:436 +msgid "0x000D" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:437 +msgid "EXIF_GPSTrackRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:437 +msgid "0x000E" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:438 +msgid "EXIF_GPSTrack" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:438 +msgid "0x000F" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:439 +msgid "EXIF_GPSImgDirectionRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:439 +msgid "0x0010" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:440 +msgid "EXIF_GPSImgDirection" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:440 +msgid "0x0011" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:441 +msgid "EXIF_GPSMapDatum" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:441 +msgid "0x0012" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:442 +msgid "EXIF_GPSDestLatitudeRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:442 +msgid "0x0013" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:443 +msgid "EXIF_GPSDestLatitude" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:443 +msgid "0x0014" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:444 +msgid "EXIF_GPSDestLongitudeRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:444 +msgid "0x0015" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:445 +msgid "EXIF_GPSDestLongitude" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:445 +msgid "0x0016" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:446 +msgid "EXIF_GPSDestBearingRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:446 +msgid "0x0017" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:447 +msgid "EXIF_GPSDestBearing" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:447 +msgid "0x0018" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:448 +msgid "EXIF_GPSDestDistanceRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:448 +msgid "0x0019" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:449 +msgid "EXIF_GPSDestDistance" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:449 +msgid "0x001A" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:450 +msgid "EXIF_GPSProcessingMethod" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:450 +msgid "0x001B" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:451 +msgid "EXIF_GPSAreaInformation" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:451 +msgid "0x001C" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:452 +msgid "EXIF_GPSDateStamp" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:452 +msgid "0x001D" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:452 +msgid "11" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:453 +msgid "EXIF_GPSDifferential" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:453 +msgid "0x001E" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:454 +msgid "EXIF_GPSHPositioningError" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:454 +msgid "0x001F" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:458 +msgid "FLIR metadata" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:462 +msgid "" +"Metadata encoded according to the FLIR convention (infrared images) is " +"available in the ``FLIR`` metadata domain." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:465 +msgid "Metadata from the following sections is supported:" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:467 +msgid "Header" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:468 +msgid "RawData" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:469 +msgid "CameraInfo" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:470 +msgid "PaletteInfo" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:471 +msgid "GPSInfo" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:473 +msgid "Consult https://exiftool.org/TagNames/FLIR.html for details." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:475 +msgid "" +"The thermal image data, stored either as raw data or in PNG, is exposed " +"as a GDAL subdataset whose name is " +"``JPEG:\"filename.jpg\":FLIR_RAW_THERMAL_IMAGE``" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:481 +msgid "`Independent JPEG Group `__" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:482 +msgid "`libjpeg-turbo `__" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:483 +msgid ":ref:`raster.gtiff`" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:484 +msgid "" +"`EXIF v2.31 specification " +"`__" +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:5 +msgid "JPEGXL -- JPEG-XL File Format" +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:9 +msgid "JPEGXL" +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:13 +msgid "" +"The JPEG-XL format is supported for reading, and batch writing " +"(CreateCopy()), but not update in place." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:16 +msgid "" +"The driver supports reading and writing: - georeferencing: encoded as a " +"GeoJP2 UUID box within a JUMBF box. - XMP in the xml:XMP metadata domain " +"- EXIF in the EXIF metadata domain - color profile in the COLOR_PROFILE " +"metadata domain." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:22 +msgid "" +"Reading or writing involves ingesting the whole uncompressed image in " +"memory. Compression is in particular very memory hungry with current " +"libjxl implementation. For large images (let's say width or height larger" +" than 10,000 pixels), using JPEGXL compression as a :ref:`raster.gtiff` " +"codec is thus recommended." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:27 +msgid "" +"The number of worker threads for multi-threaded compression and " +"decompression can be set with the :config:`GDAL_NUM_THREADS` " +"configuration option to an integer value or ``ALL_CPUS`` (the later is " +"the default)." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:32 +msgid "" +"Support for reading and writing XMP and EXIF, and writing georeferencing," +" requires a libjxl version build from its main branch, post 0.6.1 " +"release." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:70 +msgid "" +"With libjxl 0.6.1, only 1 (greyscale), 2 band (greyscale + alpha), 3 band" +" (RGB) or 4 band (RGBA) source images are supported. With later libjxl " +"versions, any number of bands can be written. Supported data types are " +"Byte, UInt16 and Float32." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:75 +msgid "" +"When copying from a (regular) JPEG file, and not specifying lossy " +"compression options, its content is re-encoded in a lossless way, and " +"with reconstruction data that enables to recreate a JPEG file from the " +"JPEGXL codestream." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:195 +msgid "`JPEG-XL home page `__" +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:196 +msgid "`libjxl `__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:5 +msgid "JPIPKAK - JPIP Streaming" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:7 +msgid "JPIPKAK" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:11 +msgid "" +"JPEG 2000 Interactive Protocol (JPIP) flexibility with respect to random " +"access, code stream reordering and incremental decoding is highly " +"exploitable in a networked environment allowing access to remote large " +"files using limited bandwidth connections or high contention networks." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:22 +msgid "JPIPKAK - JPIP Overview" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:24 +msgid "" +"A brief overview of the JPIP event sequence is presented in this section," +" more information can be found at `JPEG 2000 Interactive Protocol (Part 9" +" – JPIP) `__ and the " +"specification can (and should) be purchased from `ISO " +"`__." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:30 +msgid "" +"An earlier version of JPEG 2000 Part 9 is available here " +"http://www.jpeg.org/public/fcd15444-9v2.pdf, noting the ISO copyright, " +"diagrams are not replicated in this documentation." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:34 +msgid "" +"The JPIP protocol has been abstracted in this format driver, requests are" +" made at the 1:1 resolution level." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:37 +msgid "|JPIP Sequence Diagram|" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:270 +msgid "JPIP Sequence Diagram" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:39 +msgid "" +"Initial JPIP request for a target image, a target id, a session over " +"http, data to be returned as a jpp-stream are requested and a maximum " +"length is put on the response. In this case no initial window is " +"requested, though it can be. Server responds with a target identifier " +"that can be used to identify the image on the server and a JPIP-cnew " +"response header which includes the path to the JPIP server which will " +"handle all future requests and a cid session identifier. A session is " +"required so that that the server can model the state of the client " +"connection, only sending the data that is required." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:48 +msgid "" +"Client requests particular view windows on the target image with a " +"maximum response length and includes the session identifier established " +"in the previous communication. 'fsiz' is used to identify the resolution " +"associated with the requested view-window. The values 'fx' and 'fy' " +"specify the dimensions of the desired image resolution. 'roff' is used to" +" identify the upper left hand corner off the spatial region associated " +"with the requested view-windw. 'rsiz' is used to identify the horizontal " +"and vertical extents of the spatial region associated with the requested " +"view-window." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:59 +msgid "JPIPKAK -approach" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:61 +msgid "" +"The JPIPKAK driver uses an approach that was first demonstrated here, " +"`J2KViewer `__, by " +"Juan Pablo Garcia Ortiz of separating the communication layer (socket / " +"http) from the Kakadu kdu_cache object. Separating the communication " +"layer from the data object is desirable since it allows the use of " +"optimized http client libraries such as libcurl, Apache HttpClient (note " +"that jportiz used a plain Java socket) and allows SSL communication " +"between the client and server." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:70 +msgid "" +"Kakadu's implementation of client communication with a JPIP server uses a" +" socket, and this socket connection holds the state for this client " +"session. A client session with Kakadu can be recreated using the JPIP " +"cache operations between client and server, but no use of traditional " +"HTTP cookies is supported since JPIP is neutral to the transport layer." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:76 +msgid "" +"The JPIPKAK driver is written using a HTTP client library with the Kakadu" +" cache object and supports optimized communication with a JPIP server " +"(which may or may not support HTTP sessions) and the high performance of " +"the kakadu kdu_region_decompressor." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:81 +msgid "|Component Diagram|" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:271 +msgid "Component Diagram" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:84 +msgid "JPIPKAK - implementation" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:86 +msgid "" +"The implementation supports the GDAL C++ and C API, and provides an " +"initial SWIG wrapper for this driver with a Java ImageIO example " +"(**TODO** - qGIS Example)." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:90 +msgid "" +"The driver uses a simple threading model to support requesting reads of " +"the data and remote fetching. This threading model supports two separate " +"client windows, with just one connection to the server. Requests to the " +"server are multiplexed to utilize available bandwidth efficiently. The " +"client identifies these windows by using “0” (low) or “1” (high) values " +"to a “PRIORITY” metadata request option." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:97 +msgid "Note: SSL support" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:99 +msgid "" +"If the client is built with support for SSL, then driver determines " +"whether to use SSL if the request is a jpips:// protocol as opposed to " +"jpip:// . Note that the driver does not verify server certificates using " +"the Curl certificate bundle and is currently set to accept all SSL server" +" certificates." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:105 +msgid "Note: libCurl" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:107 +msgid "" +"JPIP sets client/server values using HTTP headers, modifications have " +"been made to the GDAL HTTP portability library to support this." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:110 +msgid "|GDAL Sequence Diagram|" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:272 +msgid "GDAL Sequence Diagram" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:112 +msgid "GDALGetDatasetDriver" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:114 +msgid "Fetch the driver to which this dataset relates." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:116 +msgid "Open" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:118 +msgid "" +"If the filename contained in the ``GDALOpenInfo`` object has a case " +"insensitive URI scheme of JPIP or JPIPS the ``JPIPKAKDataset`` is created" +" and initialized, otherwise NULL is returned." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:122 +msgid "Initialize" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:124 +msgid "" +"Initialization involves making an initial connection to the JPIP Server " +"to establish a session and to retrieve the initial metadata about the " +"image (ref. `JPIP Sequence Diagram <#initJPIP>`__)." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:128 +msgid "" +"If the connection fails, the function returns false and the ``Open`` " +"function returns NULL indicating that opening the dataset with this " +"driver failed." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:132 +msgid "" +"If the connection is successful, then subsequent requests to the JPIP " +"server are made to retrieve all the available metadata about the image. " +"Metadata items are set using the ``GDALMajorObject->SetMetadataItem`` in " +"the \"JPIP\" domain." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:137 +msgid "" +"If the metadata returned from the server includes GeoJP2 UUID box, or a " +"GMLJP2 XML box then this metadata is parsed and sets the geographic " +"metadata of this dataset." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:141 +msgid "GDALGetMetadata" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:143 +msgid "C API to ``JPIPKAKDataset->GetMetadata``" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:145 +msgid "GetMetadata" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:147 +msgid "" +"returns metadata for the \"JPIP\" domain, keys are " +"\"JPIP_NQUALITYLAYERS\", \"JPIP_NRESOLUTIONLEVELS\", \"JPIP_NCOMPS\" and " +"\"JPIP_SPRECISION\"" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:151 +msgid "GDALEndAsyncRasterIO" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:153 +msgid "" +"If the asynchronous raster IO is active and not required, the C API calls" +" ``JPIPKAKDataset->EndAsyncRasterIO``" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:156 +msgid "EndAsyncRasterIO" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:158 +msgid "The JPIPKAKAsyncRasterIO object is deleted" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:160 +msgid "delete" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:161 +msgid "GDALBeginAsyncRasterIO" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:163 +msgid "C API to ``JPIPKAKDataset->BeginAsyncRasterIO``" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:165 +msgid "BeginAsyncRasterIO" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:167 +msgid "" +"The client has set the requested view window at 1:1 and have optionally " +"set the discard level, quality layers and thread priority metadata items." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:171 +msgid "Create" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:173 +msgid "Creates a JPIPKAKAsyncRasterIO Object" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:175 +msgid "Start" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:177 +msgid "" +"Configures the kakadu machinery and starts a background thread (if not " +"already running) to communicate to the server the current view window " +"request. The background thread results in the ``kdu_cache`` object being " +"updated until the JPIP server sends an \"End Of Response\" (EOR) message " +"for the current view window request." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:183 +msgid "GDALLockBuffer" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:185 +msgid "C API to LockBuffer" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:187 +msgid "LockBuffer" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:189 +#: ../../source/drivers/raster/jpipkak.rst:227 +msgid "" +"Not implemented in ``JPIPKAKAsyncRasterIO``, a lock is acquired in " +"``JPIPKAKAsyncRasterIO->GetNextUpdatedRegion``" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:192 +msgid "GDALGetNextUpdatedRegion" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:194 +msgid "C API to GetNextUpdatedRegion" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:196 +msgid "GetNextUpdatedRegion" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:198 +msgid "" +"The function decompresses the available data to generate an image " +"(according to the dataset buffer type set in " +"``JPIPKAKDataset->BeginAsyncRasterIO``) The window width, height (at the " +"requested discard level) decompressed is returned in the region pointer " +"and can be rendered by the client. The status of the rendering operation " +"is one of ``GARIO_PENDING, GARIO_UPDATE, GARIO_ERROR, GARIO_COMPLETE`` " +"from the ``GDALAsyncStatusType`` structure. ``GARIO_UPDATE, " +"GARIO_PENDING`` require more reads of GetNextUpdatedRegion to get the " +"full image data, this is the progressive rendering of JPIP. " +"``GARIO_COMPLETE`` indicates the window is complete." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:210 +msgid "" +"``GDALAsyncStatusType`` is a structure used by\\ ``GetNextUpdatedRegion``" +" to indicate whether the function should be called again when either " +"kakadu has more data in its cache to decompress, or the server has not " +"sent an End Of Response (EOR) message to indicate the request window is " +"complete." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:216 +msgid "" +"The region passed into this function is passed by reference, and the " +"caller can read this region when the result returns to find the region " +"that has been decompressed. The image data is packed into the buffer, " +"e.g. RGB if the region requested has 3 components." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:221 +msgid "GDALUnlockBuffer" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:223 +msgid "C Api to UnlockBuffer" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:225 +msgid "UnlockBuffer" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:230 +msgid "Draw" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:232 +msgid "Client renders image data" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:234 +msgid "`GDALLockBuffer <#GDALLockBuffer>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:235 +msgid "`LockBuffer <#LockBuffer>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:236 +msgid "`GDALGetNextUpdatedRegion <#GDALGetNextUpdatedRegion>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:237 +msgid "`GetNextUpdatedRegion <#GetNextUpdatedRegion>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:238 +msgid "`GDALUnlockBuffer <#GDALUnlockBuffer>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:239 +msgid "`UnlockBuffer <#UnlockBuffer>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:240 +msgid "`Draw <#Draw>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:243 +msgid "JPIPKAK - installation requirements" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:245 +msgid "`Libcurl 7.9.4 `__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:246 +msgid "" +"`OpenSSL 0.9.8K `__ (if SSL is required, a JPIPS" +" connection)" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:248 +msgid "`Kakadu `__ (tested with v5.2.6 and v6)" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:251 +msgid "" +"Currently only a Windows makefile is provided, however this should " +"compile on Linux as well as there are no Windows dependencies." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:257 +msgid "" +"`JPEG 2000 Interactive Protocol (Part 9 – JPIP) " +"`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:259 +msgid "http://www.opengeospatial.org/standards/gmljp2" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:260 +msgid "`Kakadu Software `__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:261 +msgid "`IAS demo (example JPIP(S) streams) `__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:264 +msgid "NOTES" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:266 +msgid "" +"Driver originally developed by `ITT VIS `__ and " +"donated to GDAL to enable SSL enabled JPIP client streaming of remote " +"JPEG 2000 datasets." +msgstr "" + +#: ../../source/drivers/raster/kea.rst:11 +msgid "" +"GDAL can read, create and update files in the KEA format, through the " +"libkea library." +msgstr "" + +#: ../../source/drivers/raster/kea.rst:13 +msgid "" +"KEA is an image file format, named after the New Zealand bird, that " +"provides a full implementation of the GDAL data model and is implemented " +"within a HDF5 file. A software library, libkea, is used to access the " +"file format. The format has comparable performance with existing formats " +"while producing smaller file sizes and is already within active use for a" +" number of projects within Landcare Research, New Zealand, and the wider " +"community." +msgstr "" + +#: ../../source/drivers/raster/kea.rst:21 +msgid "The KEA format supports the following features of the GDAL data model:" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:23 +msgid "" +"Multiple-band support, with possible different datatypes. Bands can be " +"added to an existing dataset with AddBand() API" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:25 +msgid "Image blocking support" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:26 +msgid "Reading, creation and update of data of image blocks" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:27 +msgid "Affine geotransform, WKT projection, GCP" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:28 +msgid "Metadata at dataset and band level" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:29 +msgid "Per-band description" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:30 +msgid "Per-band nodata and color interpretation" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:31 +msgid "Per-band color table" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:32 +msgid "Per-band RAT (Raster Attribute Table) of arbitrary size" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:33 +msgid "Internal overviews and mask bands" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:51 +msgid "" +"|about-creation-options| The following creation options are available. " +"Some are rather esoteric and should rarely be specified, unless the user " +"has good knowledge of the working of the underlying HDF5 format." +msgstr "" + +#: ../../source/drivers/raster/kea.rst:134 +msgid "`libkea GitHub repository `__" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:136 +msgid "" +"`The KEAimage file format, by Peter Bunting and Sam Gillingham, published" +" in Computers&Geosciences " +"`__" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:139 +msgid ":ref:`HDF5 driver page `" +msgstr "" + +#: ../../source/drivers/raster/kmlsuperoverlay.rst:5 +msgid "KMLSuperoverlay -- KMLSuperoverlay" +msgstr "" + +#: ../../source/drivers/raster/kmlsuperoverlay.rst:11 +msgid "" +"NOTE: Implemented as " +":source_file:`frmts/kmlsuperoverlay/kmlsuperoverlaydataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/kro.rst:5 +msgid "KRO -- KOLOR Raw format" +msgstr "" + +#: ../../source/drivers/raster/kro.rst:7 +msgid "KRO" +msgstr "" + +#: ../../source/drivers/raster/kro.rst:11 +msgid "" +"Supported for read access, update and creation. This format is a binary " +"raw format, that supports data of several depths ( 8 bit, unsigned " +"integer 16 bit and floating point 32 bit) and with several band number (3" +" or 4 typically, for RGB and RGBA). There is no file size limit, except " +"the limitation of the file system." +msgstr "" + +#: ../../source/drivers/raster/kro.rst:17 +msgid "" +"`Specification of the format `__" +msgstr "" + +#: ../../source/drivers/raster/kro.rst:20 +msgid "NOTE: Implemented as :source_file:`frmts/raw/krodataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ktx2.rst:22 +msgid "" +"This driver handles textures with the .ktx2 extension. For .basic, refer " +"to the :ref:`raster.basisu` driver. Note that this driver does *not* " +"handle KTX(1) files." +msgstr "" + +#: ../../source/drivers/raster/ktx2.rst:30 +msgid "" +"When a file is made of several images, they are exposed as subdataset, " +"with the `KTX2:filename:layer_idx:face_idx` syntax." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:5 +msgid "L1B -- NOAA Polar Orbiter Level 1b Data Set (AVHRR)" +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:7 +msgid "L1B" +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:11 +msgid "" +"GDAL supports NOAA Polar Orbiter Level 1b Data Set format for reading. " +"Now it can read NOAA-9(F) -- NOAA-17(M) datasets. NOTE: only AVHRR " +"instrument supported now, if you want read data from other instruments, " +"write to me (Andrey Kiselev, dron@ak4719.spb.edu). AVHRR LAC/HRPT (1 km " +"resolution) and GAC (4 km resolution) should be processed correctly." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:27 +msgid "" +"Note that GDAL simple affine georeference model is completely unsuitable " +"for the NOAA data. So you should not rely on it. It is recommended to use" +" the thin plate spline warper (tps). Automatic image rectification can be" +" done with ground control points (GCPs) from the input file." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:32 +msgid "" +"NOAA stores 51 GCPs per scanline both in the LAC and GAC datasets. In " +"fact you may get less than 51 GCPs, especially at end of scanlines. " +"Another approach to rectification is manual selection of the GCPs using " +"external source of georeference information." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:37 +msgid "" +"A high density of GCPs will be reported, unless the L1B_HIGH_GCP_DENSITY " +"configuration option is set to NO." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:40 +msgid "" +"Precision of the GCPs determination depends from the satellite type. In " +"the NOAA-9 -- NOAA-14 datasets geographic coordinates of the GCPs stored " +"in integer values as a 128th of a degree. So we can't determine positions" +" more precise than 1/128=0.0078125 of degree (~28\"). In NOAA-15 -- " +"NOAA-17 datasets we have much more precise positions, they are stored as " +"10000th of degree." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:47 +msgid "" +"The GCPs will also be reported as a :ref:`geolocation array `, " +"with Lagrangian interpolation of the 51 GCPs per scanline to the number " +"of pixels per scanline width." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:52 +msgid "" +"Image will be always returned with most northern scanline located at the " +"top of image. If you want determine actual direction of the satellite " +"moving you should look at **LOCATION** metadata record." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:59 +msgid "In case of NOAA-10 in channel 5 you will get repeated channel 4 data." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:64 +msgid "" +"AVHRR/3 instrument (NOAA-15 -- NOAA-17) is a six channel radiometer, but " +"only five channels are transmitted to the ground at any given time. " +"Channels 3A and 3B cannot operate simultaneously. Look at channel " +"description field reported by ``gdalinfo`` to determine what kind of " +"channel contained in processed file." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:69 +msgid "Several parameters, obtained from the dataset stored as metadata records." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:72 +msgid "Metadata records:" +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:74 +msgid "**SATELLITE**: Satellite name" +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:75 +msgid "" +"**DATA_TYPE**: Type of the data, stored in the Level 1b dataset (AVHRR " +"HRPT/LAC/GAC)." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:77 +msgid "" +"**REVOLUTION**: Orbit number. Note that it can be 1 to 2 off the correct " +"orbit number (according to documentation)." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:79 +msgid "**SOURCE**: Receiving station name." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:80 +msgid "**PROCESSING_CENTER**: Name of data processing center." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:81 +msgid "" +"**START**: Time of first scanline acquisition (year, day of year, " +"millisecond of day)." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:83 +msgid "" +"**STOP**: Time of last scanline acquisition (year, day of year, " +"millisecond of day)." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:85 +msgid "" +"**LOCATION**: AVHRR Earth location indication. Will be **Ascending** when" +" satellite moves from low latitudes to high latitudes and **Descending** " +"in other case." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:89 +msgid "" +"Most metadata records can be written to a .CSV file when the " +"L1B_FETCH_METADATA configuration file is set to YES. By default, the " +"filename will be called \"[l1b_dataset_name]_metadata.csv\", and located " +"in the same directory as the L1B dataset. By defining the " +"L1B_METADATA_DIRECTORY configuration option, it is possible to create " +"that file in another directory. The documentation to interpret those " +"metadata is `PODUG 3.1 `__ for NOAA <=14 and `KLM " +"8.3.1.3.3.1 `__ for NOAA >=15." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:104 +msgid "" +"NOAA <=14 datasets advertise a " +"L1B_SOLAR_ZENITH_ANGLES:\"l1b_dataset_name\" subdataset that contains a " +"maximum of 51 solar zenith angles for each scanline ( beginning at sample" +" 5 with a step of 8 samples for GAC data, beginning at sample 25 with a " +"step of 40 samples for HRPT/LAC/FRAC data)." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:110 +msgid "" +"NOAA >=15 datasets advertise a L1B_ANGLES:\"l1b_dataset_name\" subdataset" +" that contains 3 bands (solar zenith angles, satellite zenith angles and " +"relative azimuth angles) with 51 values for each scanline ( beginning at " +"sample 5 with a step of 8 samples for GAC data, beginning at sample 25 " +"with a step of 40 samples for HRPT/LAC/FRAC data)." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:116 +msgid "" +"NOAA >=15 datasets advertise a L1B_CLOUDS:\"l1b_dataset_name\" subdataset" +" that contains a band of same dimensions as bands of the main L1B " +"dataset. The values of each pixel are 0 = unknown; 1 = clear; 2 = cloudy;" +" 3 = partly cloudy." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:122 +msgid "Nodata mask" +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:124 +msgid "" +"NOAA >=15 datasets that report in their header to have missing scan lines" +" will expose a per-dataset mask band (following :ref:`rfc-15`) to " +"indicate such scan lines." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:131 +msgid "Implemented as :source_file:`frmts/l1b/l1bdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:132 +msgid "" +"NOAA Polar Orbiter Level 1b Data Set documented in the \\``POD User's " +"Guide'' (TIROS-N -- NOAA-14 satellites) and in the \\``NOAA KLM User's " +"Guide'' (NOAA-15 -- NOAA-16 satellites). You can find this manuals at " +"`NOAA Technical Documentation Introduction Page " +"`__" +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:137 +msgid "" +"There are a great variety of L1B datasets, sometimes with variations in " +"header locations that are not documented in the official NOAA " +"documentation. In case a dataset is not recognized by the GDAL L1B " +"driver, the `pytroll `__ package might be able " +"to recognize it." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:142 +msgid "" +"Excellent and complete review contained in the printed book \\``The " +"Advanced Very High Resolution Radiometer (AVHRR)'' by Arthur P. " +"Cracknell, Taylor and Francis Ltd., 1997, ISBN 0-7484-0209-8." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:145 +msgid "" +"NOAA data can be downloaded from the `Comprehensive Large Array-data " +"Stewardship System (CLASS) `__ (former SAA). " +"Actually it is only source of Level 1b datasets for me, so my " +"implementation tested with that files only." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:149 +msgid "`NOAA spacecrafts status page `__" +msgstr "" + +#: ../../source/drivers/raster/lan.rst:5 +msgid "LAN -- Erdas 7.x .LAN and .GIS" +msgstr "" + +#: ../../source/drivers/raster/lan.rst:7 +msgid "LAN" +msgstr "" + +#: ../../source/drivers/raster/lan.rst:11 +msgid "" +"GDAL supports reading and writing Erdas 7.x .LAN and .GIS raster files. " +"Currently 4bit, 8bit and 16bit pixel data types are supported for reading" +" and 8bit and 16bit for writing." +msgstr "" + +#: ../../source/drivers/raster/lan.rst:15 +msgid "" +"GDAL does read the map extents (geotransform) from LAN/GIS files, and " +"attempts to read the coordinate system information. However, this format " +"of file does not include complete coordinate system information, so for " +"state plane and UTM coordinate systems a LOCAL_CS definition is returned " +"with valid linear units but no other meaningful information." +msgstr "" + +#: ../../source/drivers/raster/lan.rst:21 +msgid "The .TRL, .PRO and worldfiles are ignored at this time." +msgstr "" + +#: ../../source/drivers/raster/lan.rst:23 +msgid "NOTE: Implemented as :source_file:`frmts/raw/landataset.cpp`" +msgstr "" + +#: ../../source/drivers/raster/lan.rst:25 +msgid "" +"Development of this driver was financially supported by Kevin Flanders of" +" (`PeopleGIS `__)." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:5 +msgid "LCP -- FARSITE v.4 LCP Format" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:7 +msgid "LCP" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:11 +msgid "" +"FARSITE v. 4 landscape file (LCP) is a multi-band raster format used by " +"wildland fire behavior and fire effect simulation models such as FlamMap " +"(`firelab.org `__). The bands of" +" an LCP file store data describing terrain, tree canopy, and surface " +"fuel. The `LANDFIRE Program `__ provides " +"geospatial data in LCP format to support fire simulation modeling." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:18 +msgid "" +"An LCP file (.lcp) is basically a raw format with a 7,316-byte header " +"described below. The data type for all bands is 16-bit signed integer. " +"Bands are interleaved by pixel. Five bands are required: elevation, " +"slope, aspect, fuel model, and tree canopy cover. Crown fuel bands " +"(canopy height, canopy base height, canopy bulk density), and surface " +"fuel bands (duff, coarse woody debris) are optional. The LCP driver " +"reports several band-level metadata items described below. The band names" +" used are: ELEVATION, SLOPE, ASPECT, FUEL_MODEL, CANOPY_COV, CANOPY_HT, " +"CBH, CBD, DUFF and CWD." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:29 +msgid "" +"The LCP driver reads the linear unit, cell size, and extent, but the .lcp" +" file does not specify a projection internally. UTM projections are " +"typical, but other projections are possible. The driver will look for a " +"file with .prj extension and read the coordinate system in ESRI pseudo-" +"OGC WKT format." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:34 +msgid "" +"LCP does not support an inherent no data value, but -9999 is used by " +"convention to mark pixels that are not valid data." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:49 +msgid "The GDAL LCP driver reports dataset- and band-level metadata:" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:52 +msgid "Dataset" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "LATITUDE: Latitude of the dataset, negative for southern hemisphere" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "LINEAR_UNIT: Feet or meters" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "DESCRIPTION: LCP file description" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:59 +msgid "Band" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "_UNIT or _OPTION: units or options code for the band" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "_UNIT_NAME or _OPTION_DESC: descriptive name of units/options" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "_MIN: minimum value" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "_MAX: maximum value" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "_NUM_CLASSES: number of classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "_VALUES: comma-delimited list of class values (fuel model band only)" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "_FILE: original input raster file name for the band" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:71 +msgid "" +"**Note:** The LCP driver derives from the RawDataset helper class " +"declared in `frmts/raw`. It should be implemented as " +":source_file:`frmts/raw/lcpdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:78 +msgid "" +"|about-creation-options| The LCP driver supports CreateCopy() and " +"metadata values can be set via creation options. Below is a list of " +"options with default values listed first." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:160 +msgid "" +"Creation options that are units of linear measure are fairly lenient. " +"METERS=METER and FOOT=FEET for the most part." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:163 +msgid "" +"**Note:** CreateCopy does not scale or change any data. By setting the " +"units for various bands, it is assumed that the values are in the " +"specified units." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:167 +msgid "**LCP header format:**" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:170 +msgid "**Start byte**" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:170 +msgid "**No. of bytes**" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:170 +msgid "**Format**" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:170 +msgid "**Name**" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:170 +msgid "**Description**" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:171 +#: ../../source/drivers/raster/lcp.rst:172 +#: ../../source/drivers/raster/lcp.rst:173 +#: ../../source/drivers/raster/lcp.rst:178 +#: ../../source/drivers/raster/lcp.rst:179 +#: ../../source/drivers/raster/lcp.rst:180 +#: ../../source/drivers/raster/lcp.rst:181 +#: ../../source/drivers/raster/lcp.rst:182 +#: ../../source/drivers/raster/lcp.rst:183 +#: ../../source/drivers/raster/lcp.rst:184 +#: ../../source/drivers/raster/lcp.rst:185 +#: ../../source/drivers/raster/lcp.rst:186 +#: ../../source/drivers/raster/lcp.rst:187 +#: ../../source/drivers/raster/lcp.rst:188 +#: ../../source/drivers/raster/lcp.rst:189 +#: ../../source/drivers/raster/lcp.rst:190 +#: ../../source/drivers/raster/lcp.rst:191 +#: ../../source/drivers/raster/lcp.rst:192 +#: ../../source/drivers/raster/lcp.rst:193 +#: ../../source/drivers/raster/lcp.rst:194 +#: ../../source/drivers/raster/lcp.rst:195 +#: ../../source/drivers/raster/lcp.rst:196 +#: ../../source/drivers/raster/lcp.rst:197 +#: ../../source/drivers/raster/lcp.rst:198 +#: ../../source/drivers/raster/lcp.rst:199 +#: ../../source/drivers/raster/lcp.rst:200 +#: ../../source/drivers/raster/lcp.rst:201 +#: ../../source/drivers/raster/lcp.rst:202 +#: ../../source/drivers/raster/lcp.rst:203 +#: ../../source/drivers/raster/lcp.rst:204 +#: ../../source/drivers/raster/lcp.rst:205 +#: ../../source/drivers/raster/lcp.rst:206 +#: ../../source/drivers/raster/lcp.rst:207 +#: ../../source/drivers/raster/lcp.rst:208 +#: ../../source/drivers/raster/lcp.rst:209 +#: ../../source/drivers/raster/lcp.rst:210 +#: ../../source/drivers/raster/lcp.rst:211 +#: ../../source/drivers/raster/lcp.rst:212 +#: ../../source/drivers/raster/lcp.rst:213 +#: ../../source/drivers/raster/lcp.rst:214 +#: ../../source/drivers/raster/lcp.rst:215 +#: ../../source/drivers/raster/lcp.rst:216 +#: ../../source/drivers/raster/lcp.rst:217 +#: ../../source/drivers/raster/lcp.rst:218 +#: ../../source/drivers/raster/lcp.rst:219 +#: ../../source/drivers/raster/lcp.rst:224 +msgid "long" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:171 +msgid "crown fuels" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:171 +msgid "" +"20 if no crown fuels, 21 if crown fuels exist (crown fuels = canopy " +"height, canopy base height, canopy bulk density)" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:172 +msgid "ground fuels" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:172 +msgid "" +"20 if no ground fuels, 21 if ground fuels exist (ground fuels = duff " +"loading, coarse woody)" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:173 +msgid "latitude" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:173 +msgid "latitude (negative for southern hemisphere)" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:174 +msgid "12" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:174 +#: ../../source/drivers/raster/lcp.rst:175 +#: ../../source/drivers/raster/lcp.rst:176 +#: ../../source/drivers/raster/lcp.rst:177 +#: ../../source/drivers/raster/lcp.rst:220 +#: ../../source/drivers/raster/lcp.rst:221 +#: ../../source/drivers/raster/lcp.rst:222 +#: ../../source/drivers/raster/lcp.rst:223 +#: ../../source/drivers/raster/lcp.rst:225 +#: ../../source/drivers/raster/lcp.rst:226 +#: ../../source/drivers/vector/netcdf.rst:89 +#: ../../source/drivers/vector/netcdf.rst:135 +msgid "double" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:174 +msgid "loeast" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:174 +#: ../../source/drivers/raster/lcp.rst:175 +#: ../../source/drivers/raster/lcp.rst:176 +#: ../../source/drivers/raster/lcp.rst:177 +msgid "offset to preserve coordinate precision (legacy from 16-bit OS days)" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:175 +msgid "hieast" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:176 +msgid "lonorth" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:177 +msgid "36" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:177 +msgid "hinorth" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:178 +msgid "44" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:178 +msgid "loelev" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:178 +msgid "minimum elevation" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:179 +msgid "48" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:179 +msgid "hielev" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:179 +msgid "maximum elevation" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:180 +msgid "52" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:180 +msgid "numelev" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:180 +msgid "number of elevation classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:181 +msgid "56" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:181 +#: ../../source/drivers/raster/lcp.rst:185 +#: ../../source/drivers/raster/lcp.rst:189 +#: ../../source/drivers/raster/lcp.rst:193 +#: ../../source/drivers/raster/lcp.rst:197 +#: ../../source/drivers/raster/lcp.rst:201 +#: ../../source/drivers/raster/lcp.rst:205 +#: ../../source/drivers/raster/lcp.rst:209 +#: ../../source/drivers/raster/lcp.rst:213 +#: ../../source/drivers/raster/lcp.rst:217 +msgid "400" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:181 +msgid "elevation values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:181 +msgid "list of elevation values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:182 +msgid "456" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:182 +msgid "loslope" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:182 +msgid "minimum slope" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:183 +msgid "460" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:183 +msgid "hislope" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:183 +msgid "maximum slope" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:184 +msgid "464" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:184 +msgid "numslope" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:184 +msgid "number of slope classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:185 +msgid "468" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:185 +msgid "slope values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:185 +msgid "list of slope values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:186 +msgid "868" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:186 +msgid "loaspect" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:186 +msgid "minimum aspect" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:187 +msgid "872" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:187 +msgid "hiaspect" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:187 +msgid "maximum aspect" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:188 +msgid "876" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:188 +msgid "numaspects" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:188 +msgid "number of aspect classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:189 +msgid "880" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:189 +msgid "aspect values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:189 +msgid "list of aspect values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:190 +msgid "1280" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:190 +msgid "lofuel" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:190 +msgid "minimum fuel model value" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:191 +msgid "1284" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:191 +msgid "hifuel" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:191 +msgid "maximum fuel model value" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:192 +msgid "1288" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:192 +msgid "numfuel" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:192 +msgid "number of fuel models -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:193 +msgid "1292" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:193 +msgid "fuel values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:193 +msgid "list of fuel model values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:194 +msgid "1692" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:194 +msgid "locover" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:194 +msgid "minimum canopy cover" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:195 +msgid "1696" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:195 +msgid "hicover" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:195 +msgid "maximum canopy cover" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:196 +msgid "1700" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:196 +msgid "numcover" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:196 +msgid "number of canopy cover classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:197 +msgid "1704" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:197 +msgid "cover values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:197 +msgid "list of canopy cover values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:198 +msgid "2104" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:198 +msgid "loheight" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:198 +msgid "minimum canopy height" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:199 +msgid "2108" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:199 +msgid "hiheight" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:199 +msgid "maximum canopy height" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:200 +msgid "2112" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:200 +msgid "numheight" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:200 +msgid "number of canopy height classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:201 +msgid "2116" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:201 +msgid "height values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:201 +msgid "list of canopy height values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:202 +msgid "2516" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:202 +msgid "lobase" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:202 +msgid "minimum canopy base height" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:203 +msgid "2520" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:203 +msgid "hibase" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:203 +msgid "maximum canopy base height" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:204 +msgid "2524" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:204 +msgid "numbase" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:204 +msgid "number of canopy base height classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:205 +msgid "2528" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:205 +msgid "base values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:205 +msgid "list of canopy base height values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:206 +msgid "2928" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:206 +msgid "lodensity" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:206 +msgid "minimum canopy bulk density" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:207 +msgid "2932" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:207 +msgid "hidensity" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:207 +msgid "maximum canopy bulk density" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:208 +msgid "2936" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:208 +msgid "numdensity" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:208 +msgid "number of canopy bulk density classes, -1 if >100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:209 +msgid "2940" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:209 +msgid "density values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:209 +msgid "list of canopy bulk density values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:210 +msgid "3340" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:210 +msgid "loduff" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:210 +msgid "minimum duff" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:211 +msgid "3344" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:211 +msgid "hiduff" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:211 +msgid "maximum duff" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:212 +msgid "3348" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:212 +msgid "numduff" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:212 +msgid "number of duff classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:213 +msgid "3352" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:213 +msgid "duff values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:213 +msgid "list of duff values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:214 +msgid "3752" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:214 +msgid "lowoody" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:214 +msgid "minimum coarse woody" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:215 +msgid "3756" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:215 +msgid "hiwoody" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:215 +msgid "maximum coarse woody" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:216 +msgid "3760" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:216 +msgid "numwoodies" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:216 +msgid "number of coarse woody classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:217 +msgid "3764" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:217 +msgid "woody values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:217 +msgid "list of coarse woody values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:218 +msgid "4164" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:218 +msgid "numeast" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:218 +msgid "number of raster columns" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:219 +msgid "4168" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:219 +msgid "numnorth" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:219 +msgid "number of raster rows" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:220 +msgid "4172" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:220 +msgid "EastUtm" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:220 +msgid "max X" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:221 +msgid "4180" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:221 +msgid "WestUtm" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:221 +msgid "min X" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:222 +msgid "4188" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:222 +msgid "NorthUtm" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:222 +msgid "max Y" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:223 +msgid "4196" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:223 +msgid "SouthUtm" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:223 +msgid "min Y" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:224 +msgid "4204" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:224 +msgid "GridUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:224 +msgid "linear unit: 0 = meters, 1 = feet, 2 = kilometers" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:225 +msgid "4208" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:225 +msgid "XResol" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:225 +msgid "cell size width in GridUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:226 +msgid "4216" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:226 +msgid "YResol" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:226 +msgid "cell size height in GridUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:227 +msgid "4224" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:227 +#: ../../source/drivers/raster/lcp.rst:228 +#: ../../source/drivers/raster/lcp.rst:229 +#: ../../source/drivers/raster/lcp.rst:230 +#: ../../source/drivers/raster/lcp.rst:231 +#: ../../source/drivers/raster/lcp.rst:232 +#: ../../source/drivers/raster/lcp.rst:233 +#: ../../source/drivers/raster/lcp.rst:234 +#: ../../source/drivers/raster/lcp.rst:235 +#: ../../source/drivers/raster/lcp.rst:236 +#: ../../source/drivers/vector/netcdf.rst:87 +#: ../../source/drivers/vector/netcdf.rst:127 +msgid "short" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:227 +msgid "EUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:227 +msgid "elevation units: 0 = meters, 1 = feet" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:228 +msgid "4226" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:228 +msgid "SUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:228 +msgid "slope units: 0 = degrees, 1 = percent" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:229 +msgid "4228" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:229 +msgid "AUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:229 +msgid "aspect units: 0 = Grass categories, 1 = Grass degrees, 2 = azimuth degrees" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:230 +msgid "4230" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:230 +msgid "FOptions" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:230 +msgid "" +"fuel model options: 0 = no custom models AND no conversion file, 1 = " +"custom models BUT no conversion file, 2 = no custom models BUT conversion" +" file, 3 = custom models AND conversion file needed" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:231 +msgid "4232" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:231 +msgid "CUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:231 +msgid "canopy cover units: 0 = categories (0-4), 1 = percent" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:232 +msgid "4234" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:232 +msgid "HUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:232 +msgid "canopy height units: 1 = meters, 2 = feet, 3 = m x 10, 4 = ft x 10" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:233 +msgid "4236" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:233 +msgid "BUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:233 +msgid "canopy base height units: 1 = meters, 2 = feet, 3 = m x 10, 4 = ft x 10" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:234 +msgid "4238" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:234 +msgid "PUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:234 +msgid "" +"canopy bulk density units: 1 = kg/m^3, 2 = lb/ft^3, 3 = kg/m^3 x 100, 4 =" +" lb/ft^3 x 1000" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:235 +msgid "4240" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:235 +msgid "DUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:235 +msgid "duff units: 1 = Mg/ha x 10, 2 = t/ac x 10" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:236 +msgid "4242" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:236 +msgid "WOptions" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:236 +msgid "coarse woody options (1 if coarse woody band is present)" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:237 +msgid "4244" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:237 +#: ../../source/drivers/raster/lcp.rst:238 +#: ../../source/drivers/raster/lcp.rst:239 +#: ../../source/drivers/raster/lcp.rst:240 +#: ../../source/drivers/raster/lcp.rst:241 +#: ../../source/drivers/raster/lcp.rst:242 +#: ../../source/drivers/raster/lcp.rst:243 +#: ../../source/drivers/raster/lcp.rst:244 +#: ../../source/drivers/raster/lcp.rst:245 +#: ../../source/drivers/raster/lcp.rst:246 +#: ../../source/drivers/raster/lcp.rst:247 +msgid "char[]" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:237 +msgid "ElevFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:237 +msgid "elevation file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:238 +msgid "4500" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:238 +msgid "SlopeFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:238 +msgid "slope file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:239 +msgid "4756" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:239 +msgid "AspectFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:239 +msgid "aspect file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:240 +msgid "5012" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:240 +msgid "FuelFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:240 +msgid "fuel model file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:241 +msgid "5268" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:241 +msgid "CoverFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:241 +msgid "canopy cover file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:242 +msgid "5524" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:242 +msgid "HeightFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:242 +msgid "canopy height file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:243 +msgid "5780" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:243 +msgid "BaseFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:243 +msgid "canopy base file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:244 +msgid "6036" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:244 +msgid "DensityFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:244 +msgid "canopy bulk density file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:245 +msgid "6292" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:245 +msgid "DuffFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:245 +msgid "duff file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:246 +msgid "6548" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:246 +msgid "WoodyFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:246 +msgid "coarse woody file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:247 +msgid "6804" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:247 +msgid "512" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:247 +msgid "LCP file description" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:250 +msgid "*Chris Toney, 2009-02-14*" +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:5 +msgid "Leveller -- Daylon Leveller Heightfield" +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:7 +msgid "Leveller" +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:11 +msgid "" +"Leveller heightfields store 32-bit elevation values. Format versions 4 " +"through 9 are supported with various caveats (see below). The file " +"extension for Leveller heightfields is \"TER\" (which is the same as " +"Terragen, but the driver only recognizes Leveller files)." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:16 +msgid "" +"Blocks are organized as pixel-high scanlines (rows), with the first " +"scanline at the top (north) edge of the DEM, and adjacent pixels on each " +"line increasing from left to right (west to east)." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:20 +msgid "" +"The band type is always Float32, even though format versions 4 and 5 " +"physically use 16.16 fixed-point. The driver auto-converts them to " +"floating-point." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:36 +#: ../../source/drivers/raster/terragen.rst:31 +msgid "Reading" +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:38 +msgid "" +"``dataset::GetProjectionRef()`` will return only a local coordinate " +"system for file versions 4 through 6." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:41 +msgid "" +"``dataset::GetGeoTransform()`` returns a simple world scaling with a " +"centered origin for formats 4 through 6. For versions 7 and higher, it " +"returns a real-world transform except for rotations. The identity " +"transform is not considered an error condition; Leveller documents often " +"use them." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:47 +msgid "" +"``band::GetUnitType()`` will report the measurement units used by the " +"file instead of converting unusual types to meters. A list of unit types " +"is in the ``levellerdataset.cpp`` module." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:51 +msgid "" +"``band::GetScale()`` and ``band::GetOffset()`` will return the physical-" +"to-logical (i.e., raw to real-world) transform for the elevation data." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:56 +#: ../../source/drivers/raster/terragen.rst:44 +msgid "Writing" +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:58 +msgid "The ``dataset::Create()`` call is supported, but for version 7 files only." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:61 +msgid "" +"``band::SetUnitType()`` can be set to any of the unit types listed in the" +" ``levellerdataset.cpp`` module." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:64 +msgid "``dataset::SetGeoTransform()`` should not include rotation data." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:66 +msgid "" +"As with the Terragen driver, the ``MINUSERPIXELVALUE`` option must be " +"specified. This lets the driver correctly map from logical (real-world) " +"elevations to physical elevations." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:70 +msgid "" +"Header information is written out on the first call to " +"``band::IWriteBlock``." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:76 +msgid "Implemented as :source_file:`frmts/leveller/levellerdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:77 +msgid "" +"Visit `Daylon Graphics `__ for the " +"Leveller SDK, which documents the Leveller format." +msgstr "" + +#: ../../source/drivers/raster/loslas.rst:5 +msgid "LOSLAS -- NADCON .los/.las Datum Grid Shift" +msgstr "" + +#: ../../source/drivers/raster/loslas.rst:7 +msgid "LOSLAS" +msgstr "" + +#: ../../source/drivers/raster/loslas.rst:11 +msgid "" +"Starting with GDAL 3.1, can also open geoid models of extension .geo such" +" as https://geodesy.noaa.gov/GEOID/MEXICO97/" +msgstr "" + +#: ../../source/drivers/raster/loslas.rst:14 +msgid "NOTE: Implemented as :source_file:`frmts/raw/loslasdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/map.rst:5 +msgid "MAP -- OziExplorer .MAP" +msgstr "" + +#: ../../source/drivers/raster/map.rst:7 +msgid "MAP" +msgstr "" + +#: ../../source/drivers/raster/map.rst:11 +msgid "OziExplorer MAP files." +msgstr "" + +#: ../../source/drivers/raster/map.rst:23 +msgid "Implemented as :source_file:`frmts/map/mapdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/map.rst:24 +msgid "" +"`OziExplorer Map File Format " +"`__" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:5 +msgid "MRF -- Meta Raster Format" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:7 +msgid "MRF" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:13 +msgid "" +"Access to a indexed heap of regular tiles (blocks). Controlled by an xml " +"file, usually organized as a pyramid of overviews, with level zero being " +"the full resolution image. None, PNG, JPEG, ZLIB tile packing are " +"implemented" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:18 +msgid "For file creation options, see \"gdalinfo --format MRF\"" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:32 +#: ../../source/drivers/raster/nitf.rst:345 +#: ../../source/drivers/raster/openfilegdb.rst:99 +#: ../../source/drivers/raster/tga.rst:31 +#: ../../source/drivers/vector/arrow.rst:121 +#: ../../source/drivers/vector/filegdb.rst:313 +#: ../../source/drivers/vector/gtfs.rst:44 +#: ../../source/drivers/vector/mapml.rst:150 +#: ../../source/drivers/vector/openfilegdb.rst:365 +#: ../../source/drivers/vector/parquet.rst:237 +#: ../../source/drivers/vector/sqlite.rst:597 +#: ../../source/drivers/vector/vdv.rst:152 +msgid "Links" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:34 +msgid "" +"`MRF User Guide `__" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:35 +msgid "" +"`MRF Specification `__" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:36 +msgid "`Source repository nasa-gibs/mrf `__" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:11 +msgid "" +"The MBTiles driver allows reading rasters in the MBTiles format, which is" +" a specification for storing tiled map data in SQLite databases." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:15 +msgid "" +"Starting with GDAL 2.1, the MBTiles driver has creation and write support" +" for MBTiles raster datasets." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:18 +msgid "" +"Starting with GDAL 2.3, the MBTiles driver has read and write support for" +" MBTiles vector datasets. For standalone Mapbox Vector Tile files or set " +"of MVT files, see the :ref:`MVT ` driver. Note: vector write " +"support requires GDAL to be built with GEOS." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:23 +msgid "" +"GDAL/OGR must be compiled with OGR SQLite driver support, and JPEG and " +"PNG drivers." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:26 +#: ../../source/drivers/vector/pmtiles.rst:24 +msgid "" +"The SRS is always the `Pseudo-Mercator " +"`__ (a.k.a Google " +"Mercator) projection, EPSG:3857." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:29 +msgid "" +"Starting with GDAL 2.3, the driver will open a dataset as RGBA. For " +"previous versions, the driver will try to determine the number of bands " +"by probing the content of one tile. It is possible to alter this behavior" +" by defining the :config:`MBTILES_BAND_COUNT` configuration option (or " +"starting with GDAL 2.1, the :oo:`BAND_COUNT` open option) to the number " +"of bands. The values supported are 1, 2, 3 or 4. Four band " +"(Red,Green,Blue,Alpha) dataset gives the maximum compatibility with the " +"various encodings of tiles that can be stored." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:38 +msgid "" +"The driver will use the 'bounds' metadata in the metadata table and do " +"necessary tile clipping, if needed, to respect that extent. However that " +"information being optional, if omitted, the driver will use the extent of" +" the tiles at the maximum zoom level. The user can also specify the " +":oo:`USE_BOUNDS=NO` open option to force the use of the actual extent of " +"tiles at the maximum zoom level. Or it can specify any of " +"MINX/MINY/MAXX/MAXY to have a custom extent." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:46 +msgid "" +"The driver can retrieve pixel attributes encoded according to the UTFGrid" +" specification available in some MBTiles files. They can be obtained with" +" the gdallocationinfo utility, or with a " +"GetMetadataItem(\"Pixel_iCol_iLine\", \"LocationInfo\") call on a band " +"object." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:66 +#: ../../source/drivers/raster/pds.rst:42 +#: ../../source/drivers/vector/geojsonseq.rst:58 +msgid "|about-config-options| The following configuration option is available:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:80 +#: ../../source/drivers/raster/mbtiles.rst:260 +#: ../../source/drivers/raster/pds4.rst:184 +msgid "Raster and vector:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:118 +#: ../../source/drivers/raster/mbtiles.rst:279 +#: ../../source/drivers/raster/pds4.rst:104 +msgid "Raster only:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:160 +msgid "Vector only:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:180 +msgid "Raster creation issues" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:182 +msgid "" +"Depending of the number of bands of the input dataset and the tile format" +" selected, the driver will do the necessary conversions to be compatible " +"with the tile format. When using the CreateCopy() API (such as with " +":ref:`gdal_translate`), automatic reprojection of the input dataset to " +"EPSG:3857 (Pseudo-Mercator) will be done, with selection of the " +"appropriate zoom level." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:192 +msgid "" +"The driver implements the Create() and IWriteBlock() methods, so that " +"arbitrary writing of raster blocks is possible, enabling the direct use " +"of MBTiles as the output dataset of utilities such as gdalwarp." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:201 +msgid "" +"Technical/implementation note: in the general case, GDAL blocks do not " +"exactly match a single MBTiles tile. In which case, each GDAL block will " +"overlap four MBTiles tiles. This is easily handled on the read side, but " +"on creation/update side, such configuration could cause numerous " +"decompression/ recompression of tiles to be done, which might cause " +"unnecessary quality loss when using lossy compression (JPEG). To avoid " +"that, the driver will create a temporary database next to the main " +"MBTiles file to store partial MBTiles tiles in a lossless (and " +"uncompressed) way. Once a tile has received data for its four quadrants " +"and for all the bands (or the dataset is closed or explicitly flushed " +"with FlushCache()), those uncompressed tiles are definitely transferred " +"to the MBTiles file with the appropriate compression. All of this is " +"transparent to the user of GDAL API/utilities" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:218 +msgid "" +"MBTiles can store tiles in PNG, JPEG or WEBP (since 3.8). Support for " +"those tile formats depend if the underlying drivers are available in " +"GDAL. By default, GDAL will PNG tiles." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:222 +msgid "" +"It is possible to select the tile format by setting the creation/open " +"option TILE_FORMAT to one of PNG, PNG8, JPEG or WEBP. When using JPEG, " +"the alpha channel will not be stored." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:240 +msgid "Vector creation issues" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:242 +msgid "" +"Tiles are generated with WebMercator (EPSG:3857) projection. It is " +"possible to decide at which zoom level ranges a given layer is written. " +"Several layers can be written but the driver has only write-once support " +"for vector data. For writing several vector datasets into MBTiles file an" +" intermediate format like GeoPackage must be used as a container so that " +"all layers can be converted at the same time. Write-once support means " +"also that existing vector layers can't be edited." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:250 +#: ../../source/drivers/vector/mvt.rst:221 +#: ../../source/drivers/vector/pmtiles.rst:93 +msgid "" +"Part of the conversion is multi-threaded by default, using as many " +"threads as there are cores. The number of threads used can be controlled " +"with the :config:`GDAL_NUM_THREADS` configuration option." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:344 +msgid "Vector only (GDAL >= 2.3):" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:442 +msgid "Layer configuration (vector)" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:444 +#: ../../source/drivers/vector/mvt.rst:372 +#: ../../source/drivers/vector/pmtiles.rst:192 +msgid "" +"The above mentioned CONF dataset creation option can be set to a string " +"whose value is a JSON serialized document such as the below one:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:463 +#: ../../source/drivers/vector/mvt.rst:391 +#: ../../source/drivers/vector/pmtiles.rst:211 +msgid "" +"*boundaries_lod0* and *boundaries_lod1* are the name of the OGR layers " +"that are created into the target MVT dataset. They are mapped to the MVT " +"target layer *boundaries*." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:467 +#: ../../source/drivers/vector/mvt.rst:395 +#: ../../source/drivers/vector/pmtiles.rst:215 +msgid "" +"It is also possible to get the same behavior with the below layer " +"creation options, although that is not convenient in the ogr2ogr use " +"case." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:472 +msgid "Layer creation options (vector)" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:502 +msgid "Overviews (raster)" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:504 +msgid "" +"gdaladdo / BuildOverviews() can be used to compute overviews. Only power-" +"of-two overview factors (2,4,8,16,...) are supported." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:507 +msgid "" +"If more overview levels are specified than available, the extra ones are " +"silently ignored." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:514 +msgid "Vector tiles" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:516 +msgid "" +"Starting with GDAL 2.3, the MBTiles driver can read MBTiles files " +"containing vector tiles conforming to the Mapbox Vector Tile format " +"(format=pbf)." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:520 +msgid "" +"The driver requires the 'metadata' table to contain a name='json' entry, " +"that has a 'vector_layers' array describing layers and their schema. See " +":ref:`metadata.json `" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:524 +msgid "" +"Note: The driver will make no effort of stitching together geometries for" +" features that overlap several tiles." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:530 +msgid "Accessing a remote MBTiles raster :" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:536 +#: ../../source/drivers/raster/mbtiles.rst:598 +#: ../../source/drivers/raster/rasterlite.rst:192 +#: ../../source/drivers/raster/rasterlite.rst:231 +#: ../../source/drivers/raster/wms.rst:124 +msgid "Output:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:591 +msgid "Reading pixel attributes encoded according to the UTFGrid specification :" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:612 +msgid "Converting a dataset to MBTiles and adding overviews :" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:619 +msgid "Opening a vector MBTiles:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:639 +msgid "Converting a GeoPackage to a Vector tile MBTILES:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:648 +msgid "`MBTiles specification `__" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:649 +msgid "" +"`UTFGrid specification `__" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:651 +#: ../../source/drivers/vector/pmtiles.rst:357 +msgid ":ref:`Mapbox Vector tiles driver `" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:5 +msgid "MEM -- In Memory Raster" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:7 +msgid "MEM" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:11 +msgid "" +"GDAL supports the ability to hold rasters in a temporary in-memory " +"format. This is primarily useful for temporary datasets in scripts or " +"internal to applications. It is not generally of any use to application " +"end-users." +msgstr "" + +#: ../../source/drivers/raster/mem.rst:16 +msgid "" +"Memory datasets should support for most kinds of auxiliary information " +"including metadata, coordinate systems, georeferencing, GCPs, color " +"interpretation, nodata, color tables and all pixel data types." +msgstr "" + +#: ../../source/drivers/raster/mem.rst:21 +msgid "Dataset Name Format" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:23 +msgid "" +"It is possible to open an existing array in memory. To do so, construct a" +" dataset name with the following format:" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:46 +msgid "" +"DATAPOINTER: address of the first pixel of the first band. The address " +"can be represented as a hexadecimal or decimal value. Hexadecimal values " +"must be prefixed with '0x'. Some implementations (notably Windows) " +"doesn't print hexadecimal pointer values with a leading '0x', so the " +"prefix must be added. You can use CPLPrintPointer to create a string with" +" format suitable for use as a DATAPOINTER." +msgstr "" + +#: ../../source/drivers/raster/mem.rst:53 +msgid "PIXELS: Width of raster in pixels. (required)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:54 +msgid "LINES: Height of raster in lines. (required)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:55 +msgid "BANDS: Number of bands, defaults to 1. (optional)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:56 +msgid "" +"DATATYPE: Name of the data type, as returned by GDALGetDataTypeName() " +"(eg. Byte, Int16) Defaults to Byte. (optional)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:58 +msgid "" +"PIXELOFFSET: Offset in bytes between the start of one pixel and the next " +"on the same scanline. (optional)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:60 +msgid "" +"LINEOFFSET: Offset in bytes between the start of one scanline and the " +"next. (optional)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:62 +msgid "" +"BANDOFFSET: Offset in bytes between the start of one bands data and the " +"next." +msgstr "" + +#: ../../source/drivers/raster/mem.rst:64 +msgid "" +"GEOTRANSFORM: Set the affine transformation coefficients. 6 real numbers " +"with '/' as separator (optional)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:66 +msgid "" +"SPATIALREFERENCE: (GDAL >= 3.7) Set the projection. The coordinate " +"reference systems that can be passed are anything supported by the " +"OGRSpatialReference.SetFromUserInput() as per '-a_srs' in " +":ref:`gdal_translate`. If the passed string includes comma or double-" +"quote characters (typically WKT), it should be surrounded by double-quote" +" characters and the double-quote characters inside it should be escaped " +"with anti-slash. e.g ``SPATIALREFERENCE=\"GEOGCRS[\\\"WGS 84\\\",[... " +"snip ...],ID[\\\"EPSG\\\",4326]]\"``" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:78 +msgid "There are no supported creation options." +msgstr "" + +#: ../../source/drivers/raster/mem.rst:80 +msgid "" +"The MEM format is one of the few that supports the AddBand() method. The " +"AddBand() method supports DATAPOINTER, PIXELOFFSET and LINEOFFSET options" +" to reference an existing memory array." +msgstr "" + +#: ../../source/drivers/raster/mem.rst:98 +msgid "The MEM driver supports the :ref:`multidim_raster_data_model`." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:5 +msgid "MFF -- Vexcel MFF Raster" +msgstr "" + +#: ../../source/drivers/raster/mff.rst:7 +msgid "MFF" +msgstr "" + +#: ../../source/drivers/raster/mff.rst:11 +msgid "" +"GDAL includes read, update, and creation support for Vexcel's MFF raster " +"format. MFF dataset consist of a header file (typically with the " +"extension .hdr) and a set of data files with extensions like .x00, .b00 " +"and so on. To open a dataset select the .hdr file." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:16 +msgid "" +"Reading lat/long GCPs (TOP_LEFT_CORNER, ...) is supported but there is no" +" support for reading affine georeferencing or projection information." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:19 +msgid "Unrecognized keywords from the .hdr file are preserved as metadata." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:21 +msgid "" +"All data types with GDAL equivalents are supported, including 8, 16, 32 " +"and 64 bit data precisions in integer, real and complex data types. In " +"addition tile organized files (as produced by the Vexcel SAR Processor - " +"APP) are supported for reading." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:26 +msgid "" +"On creation (with a format code of MFF) a simple, ungeoreferenced raster " +"file is created." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:29 +msgid "" +"MFF files are not normally portable between systems with different byte " +"orders. However GDAL honours the new BYTE_ORDER keyword which can take a " +"value of LSB (Integer - little endian), and MSB (Motorola - big endian). " +"This may be manually added to the .hdr file if required." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:34 +msgid "NOTE: Implemented as :source_file:`frmts/raw/mffdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:5 +msgid "MFF2 -- Vexcel MFF2 Image" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:7 +msgid "MFF2" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:11 +msgid "" +"GDAL supports MFF2 Image raster file format for read, update, and " +"creation. The MFF2 (Multi-File Format 2) format was designed to fit into " +"Vexcel Hierarchical Key-Value (HKV) databases, which can store binary " +"data as well as ASCII parameters. This format is primarily used " +"internally to the Vexcel InSAR processing system." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:17 +msgid "" +"To select an MFF2 dataset, select the directory containing the " +"``attrib``, and ``image_data`` files for the dataset." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:20 +msgid "" +"Currently only latitude/longitude and UTM projection are supported " +"(georef.projection.name = ll or georef.projection.name = utm), with the " +"affine transform computed from the lat/long control points. In any event," +" if GCPs are available in a georef file, they are returned with the " +"dataset." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:26 +msgid "" +"Newly created files (with a type of ``MFF2``) are always just raw rasters" +" with no georeferencing information. For read, and creation all data " +"types (real, integer and complex in bit depths of 8, 16, 32) should be " +"supported." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:31 +msgid "" +"IMPORTANT: When creating a new MFF2, be sure to set the projection before" +" setting the geotransform (this is necessary because the geotransform is " +"stored internally as 5 latitude-longitude ground control points, and the " +"projection is needed to do the conversion)." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:36 +msgid "NOTE: Implemented as :source_file:`frmts/raw/hkvdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:50 +msgid "Format Details" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:53 +msgid "MFF2 Top-level Structure" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:55 +msgid "" +"An MFF2 \"file\" is actually a set of files stored in a directory " +"containing an ASCII header file entitled \"attrib\", and binary image " +"data entitled \"image_data\". Optionally, there may be an ASCII " +"\"georef\" file containing georeferencing and projection information, and" +" an \"image_data_ovr\" (for \"image_data\" binary image data) file " +"containing tiled overviews of the image in TIFF format. The ASCII files " +"are arranged in key=value pairs. The allowable pairs for each file are " +"described below." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:65 +msgid "The \"attrib\" File" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:67 +msgid "" +"As a minimum, the \"attrib\" file must specify the image extents, pixel " +"size in bytes, pixel encoding and datatype, and pixel byte order. For " +"example," +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:81 +msgid "" +"specifies an image that is 1040 lines by 800 pixels in extent. The pixels" +" are 32 bits of real data in \"most significant byte first\" (msbf) " +"order, encoded according to the ieee_754 specification. In MFF2, when a " +"value must belong to a certain subset (eg. pixel.order must be either " +"lsbf or msbf), all options are displayed between curly brackets, and the " +"one appropriate for the current file is indicated with a \"*\"." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:88 +msgid "" +"The file may also contain the following lines indicating the number of " +"channels of data, and how they are interleaved within the binary data " +"file." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:98 +msgid "The \"image_data\" File" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:100 +msgid "" +"The \"image_data\" file consists of raw binary data, with extents, pixel " +"encoding, and number of channels as indicated in the \"attrib\" file." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:104 +msgid "The \"georef\" File" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:106 +msgid "" +"The \"georef\" file is used to describe the geocoding and projection " +"information for the binary data. For example," +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:125 +msgid "" +"describes an orthogonal latitude/longitude (ll) projected image, with " +"latitudes and longitudes based on the wgs-84 ellipsoid." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:128 +msgid "" +"Since MFF2 version 1.1, top_left refers to the top left corner of the top" +" left pixel. top_right refers to the top right corner of the top right " +"pixel. bottom_left refers to the bottom left corner of the bottom left " +"pixel. bottom_right refers to the bottom right corner of the bottom right" +" pixel. centre refers to the centre of the four corners defined above " +"(center of the image)." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:135 +msgid "" +"Mathematically, for an Npix by Nline image, the corners and centre in " +"(pixel,line) coordinates for MFF2 version 1.1 are:" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:146 +msgid "" +"These calculations are done using floating point arithmetic (i.e. centre " +"coordinates may take on non-integer values)." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:149 +msgid "" +"Note that the corners are always expressed in latitudes/longitudes, even " +"for projected images." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:153 +msgid "Supported projections" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:155 +msgid "" +"ll- Orthogonal latitude/longitude projected image, with latitude parallel" +" to the rows, longitude parallel to the columns. Parameters: spheroid " +"name, projection.origin_longitude (longitude at the origin of the " +"projection coordinates). If not set, this should default to the central " +"longitude of the output image based on its projection boundaries." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:162 +msgid "" +"utm- Universal Transverse Mercator projected image. Parameters: spheroid " +"name, projection.origin_longitude (central meridian for the utm " +"projection). The central meridian must be the meridian at the centre of a" +" UTM zone, i.e. 3 degrees, 9 degrees, 12 degrees, etc. If this is not " +"specified or set a valid UTM central meridian, the reader should reset " +"the value to the nearest valid central meridian based on the central " +"longitude of the output image. The latitude at the origin of the UTM " +"projection is always 0 degrees." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:172 +msgid "Recognized ellipsoids" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:174 +msgid "" +"MFF2 format associates the following names with ellipsoid equatorial " +"radius and inverse flattening parameters:" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:211 +msgid "Explanation of fields" +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:5 +msgid "MrSID -- Multi-resolution Seamless Image Database" +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:7 +msgid "MrSID" +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:11 +msgid "" +"MrSID is a wavelet-based image compression technology which can utilize " +"both lossy and lossless encoding. This technology was acquired in its " +"original form from Los Alamos National Laboratories (LANL), where it was " +"developed under the aegis of the U.S. government for storing fingerprints" +" for the FBI. Now it is developed and distributed by Extensis." +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:18 +msgid "" +"This driver supports reading of MrSID image files using Extensis' " +"decoding software development kit (DSDK). **This DSDK is not free " +"software, you should contact Extensis to obtain it (see link at end of " +"this page).** If you are using GCC, please, ensure that you have the same" +" compiler as was used for DSDK compilation. It is C++ library, so you may" +" get incompatibilities in C++ name mangling between different GCC " +"versions (2.95.x and 3.x)." +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:26 +msgid "" +"Latest versions of the DSDK also support decoding JPEG2000 file format, " +"so this driver can be used for JPEG2000 too." +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:39 +msgid "" +"MrSID metadata transparently translated into GDAL metadata strings. Files" +" in MrSID format contain a set of standard metadata tags such as: " +"IMAGE__WIDTH (contains the width of the image), IMAGE__HEIGHT (contains " +"the height of the image), IMAGE__XY_ORIGIN (contains the x and y " +"coordinates of the origin), IMAGE__INPUT_NAME (contains the name or names" +" of the files used to create the MrSID image) etc. GDAL's metadata keys " +"cannot contain characters \\`:' and \\`=', but standard MrSID tags always" +" contain double colons in tag names. These characters replaced in GDAL " +"with \\`_' during translation. So if you are using other software to work" +" with MrSID be ready that names of metadata keys will be shown " +"differently in GDAL." +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:58 +msgid "" +"MrSID images may contain georeference and coordinate system information " +"in form of GeoTIFF GeoKeys, translated in metadata records. All those " +"GeoKeys properly extracted and used by the driver. Unfortunately, there " +"is one caveat: old MrSID encoders has a bug which resulted in wrong " +"GeoKeys, stored in MrSID files. This bug was fixed in MrSID software " +"version 1.5, but if you have older encoders or files, created with older " +"encoders, you cannot use georeference information from them." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:5 +msgid "MSG -- Meteosat Second Generation" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:7 +msgid "MSG" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:11 +msgid "" +"This driver implements reading support for Meteosat Second Generation " +"files. These are files with names like " +"``H-000-MSG1\\_\\_-MSG1\\_\\_\\_\\_\\_\\_\\_\\_-HRV\\_\\_\\_\\_\\_\\_-000007\\_\\_\\_-200405311115-C\\_``," +" commonly distributed into a folder structure with dates (e.g. " +"``2004\\05\\31`` for the file mentioned)." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:17 +msgid "" +"The MSG files are wavelet-compressed. A decompression library licensed " +"from `EUMETSAT `__ is needed (`Public Wavelet " +"Transform Decompression Library Software `__, shorter *Wavelet Transform Software*). " +"The software is compilable on Microsoft Windows, Linux and Solaris " +"Operating Systems, and it works on 32 bits and 64 bits as well as mixed " +"architectures. It is licensed under Apache v2." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:28 +msgid "" +"This driver is not \"enabled\" by default. See `Build Instructions " +"<#MSG_Build_Instructions>`__ on how to include this driver in your GDAL " +"library." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:36 +msgid "Build Instructions" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:39 +msgid "CMake builds" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:41 +msgid "See the ``GDAL_USE_PUBLICDECOMPWT`` option of :ref:`building_from_source`." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:44 +msgid "Other build systems" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:46 +msgid "Clone the EUMETSAT library for wavelet decompression into ``frmts/msg``." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:48 +msgid "" +"If you are building with Visual Studio 6.0, extract the .vc makefiles for" +" the PublicDecompWT from the file `PublicDecompWTMakefiles.zip` stored in" +" that directory." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:52 +msgid "" +"If you build using the GNUMakefile, use *--with-msg* option to enable MSG" +" driver:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:59 +msgid "" +"If you find that some adjustments are needed in the makefile and/or the " +"msg source files, please \"commit\" them. The EUMETSAT library promises " +"to be \"platform independent\", but as we are working with Microsoft " +"Windows and Visual Studio 6.0, we did not have the facilities to check if" +" the rest of the msg driver is. Furthermore, apply steps 4 to 7 from the " +":ref:`raster_driver_tut`, section \"Adding Driver to GDAL Tree\"." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:66 +msgid "" +"MSG Wiki page is available at http://trac.osgeo.org/gdal/wiki/MSG. It's " +"dedicated to document building and usage hints" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:70 +msgid "Specification of Source Dataset" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:72 +msgid "" +"It is possible to select individual files for opening. In this case, the " +"driver will gather the files that correspond to the other strips of the " +"same image, and correctly compose the image." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:76 +msgid "Example with gdal_translate.exe:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:84 +msgid "It is also possible to use the following syntax for opening the MSG files:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:87 +msgid "MSG(source_folder,timestamp,(channel,channel,...,channel),use_root_folder,data_conversion,nr_cycles,step)" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:90 +msgid "source_folder: a path to a folder structure that contains the files" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:92 +msgid "" +"timestamp: 12 digits representing a date/time that identifies the 114 " +"files of the 12 images of that time, e.g. 200501181200" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:94 +msgid "" +"channel: a number between 1 and 12, representing each of the 12 available" +" channels. When only specifying one channel, the brackets are optional." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:97 +msgid "" +"use_root_folder: Y to indicate that the files reside directly into the " +"source_folder specified. N to indicate that the files reside in date " +"structured folders: source_folder/YYYY/MM/DD" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:100 +msgid "data_conversion:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:103 +msgid "N to keep the original 10 bits DN values. The result is UInt16." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:104 +msgid "" +"B to convert to 8 bits (handy for GIF and JPEG images). The result is " +"Byte." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:106 +msgid "" +"R to perform radiometric calibration and get the result in " +"mW/m2/sr/(cm-1)-1. The result is Float32." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:108 +msgid "" +"L to perform radiometric calibration and get the result in W/m2/sr/um. " +"The result is Float32." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:110 +msgid "" +"T to get the reflectance for the visible bands (1, 2, 3 and 12) and the " +"temperature in degrees Kelvin for the infrared bands (all other bands). " +"The result is Float32." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:114 +msgid "" +"nr_cycles: a number that indicates the number of consecutive cycles to be" +" included in the same file (time series). These are appended as " +"additional bands." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:117 +msgid "" +"step: a number that indicates what is the stepsize when multiple cycles " +"are chosen. E.g. every 15 minutes: step = 1, every 30 minutes: step = 2 " +"etc. Note that the cycles are exactly 15 minutes apart, so you can not " +"get images from times in-between (the step is an integer)." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:123 +msgid "Examples with gdal_translate utility:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:125 +msgid "" +"Example call to fetch an MSG image of 200501181200 with bands 1, 2 and 3 " +"in IMG format:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:132 +msgid "" +"In JPG format, and converting the 10 bits image to 8 bits by dividing all" +" values by 4:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:139 +msgid "The same, but reordering the bands in the JPEG image to resemble RGB:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:145 +msgid "Geotiff output, only band 2, original 10 bits values:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:151 +msgid "Band 12:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:157 +msgid "The same band 12 with radiometric calibration in mW/m2/sr/(cm-1)-1:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:163 +msgid "" +"Retrieve data from c:\\hrit-data\\2005\\01\\18 instead of " +"\\\\\\pc2133-24002\\RawData\\... :" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:170 +msgid "" +"Another option to do the same (note the difference in the Y and the N for" +" the “use_root_folder” parameter:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:177 +msgid "" +"Without radiometric calibration, but for 10 consecutive cycles (thus from" +" 1200 to 1415):" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:184 +msgid "10 cycles, but every hour (thus from 1200 to 2100):" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:190 +msgid "10 cycles, every hour, and bands 3, 2 and 1:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:197 +msgid "Georeference and Projection" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:199 +msgid "" +"The images are using the Geostationary Satellite View projection. Most " +"GIS packages don't recognize this projection (we only know of ILWIS that " +"does have this projection), but gdalwarp.exe can be used to re-project " +"the images." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:207 +msgid "Implemented as :source_file:`frmts/msg/msgdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:208 +msgid "" +"http://www.eumetsat.int - European Organisation for the Exploitation of " +"Meteorological Satellites" +msgstr "" + +#: ../../source/drivers/raster/msgn.rst:5 +msgid "MSGN -- Meteosat Second Generation (MSG) Native Archive Format (.nat)" +msgstr "" + +#: ../../source/drivers/raster/msgn.rst:7 +msgid "MSGN" +msgstr "" + +#: ../../source/drivers/raster/msgn.rst:11 +msgid "" +"GDAL supports reading only of MSG native files. These files may have " +"anything from 1 to 12 bands, all at 10-bit resolution." +msgstr "" + +#: ../../source/drivers/raster/msgn.rst:14 +msgid "" +"Includes support for the 12th band (HRV - High Resolution Visible). This " +"is implemented as a subset, i.e., it is accessed by prefixing the " +"filename with the tag \"HRV:\"." +msgstr "" + +#: ../../source/drivers/raster/msgn.rst:18 +msgid "" +"Similarly, it is possible to obtain floating point radiance values in " +"stead of the usual 10-bit digital numbers (DNs). This subset is accessed " +"by prefixing the filename with the tag \"RAD:\"." +msgstr "" + +#: ../../source/drivers/raster/msgn.rst:22 +msgid "" +"Georeferencing is currently supported, but the results may not be " +"acceptable (accurate enough), depending on your requirements. The current" +" workaround is to implement the CGMS Geostationary projection directly, " +"using the code available from EUMETSAT." +msgstr "" + +#: ../../source/drivers/raster/ndf.rst:5 +msgid "NDF -- NLAPS Data Format" +msgstr "" + +#: ../../source/drivers/raster/ndf.rst:7 +msgid "NDF" +msgstr "" + +#: ../../source/drivers/raster/ndf.rst:11 +msgid "" +"GDAL has limited support for reading NLAPS Data Format files. This is a " +"format primarily used by the Eros Data Center for distribution of Landsat" +" data. NDF datasets consist of a header file (often with the extension " +".H1) and one or more associated raw data files (often .I1, .I2, ...). To " +"open a dataset select the header file, often with the extension .H1, .H2 " +"or .HD." +msgstr "" + +#: ../../source/drivers/raster/ndf.rst:18 +msgid "" +"The NDF driver only supports 8bit data. The only supported projection is " +"UTM. NDF version 1 (NDF_VERSION=0.00) and NDF version 2 are both " +"supported." +msgstr "" + +#: ../../source/drivers/raster/ndf.rst:22 +msgid "NOTE: Implemented as :source_file:`frmts/raw/ndfdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ndf.rst:24 +msgid "" +"See Also: `NLAPS Data Format Specification " +"`__." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:7 +#: ../../source/drivers/vector/netcdf.rst:8 +msgid "netCDF" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:11 +msgid "" +"This format is supported for read and write access. This page only " +"describes the raster support (you can find documentation for the " +":ref:`vector side `) NetCDF is an interface for array-" +"oriented data access and is used for representing scientific data." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:16 +msgid "" +"The fill value metadata or missing_value backward compatibility is " +"preserved as NODATA value when available." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:19 +msgid "NOTE: Implemented as :source_file:`frmts/netcdf/netcdfdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:33 +msgid "" +"Network Command Data Form is a container for several different arrays " +"most used for storing scientific dataset. One NetCDF file may contain " +"several datasets. They may differ in size, number of dimensions and may " +"represent data for different regions." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:38 +msgid "" +"If the file contains only one NetCDF array which appears to be an image, " +"it may be accessed directly, but if the file contains multiple images it " +"may be necessary to import the file via a two step process." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:42 +msgid "" +"The first step is to get a report of the components images (dataset) in " +"the file using gdalinfo, and then to import the desired images using " +"gdal_translate. The gdalinfo utility lists all multidimensional " +"subdatasets from the input NetCDF file." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:47 +msgid "" +"The name of individual images are assigned to the SUBDATASET_n_NAME " +"metadata item. The description for each image is found in the " +"SUBDATASET_n_DESC metadata item. For NetCDF images will follow this " +"format: *NETCDF:filename:variable_name*" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:52 +msgid "" +"where *filename* is the name of the input file, and *variable_name* is " +"the dataset selected within the file." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:55 +msgid "" +"On the second step you provide this name for **gdalinfo** to get " +"information about the dataset or **gdal_translate** to read dataset." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:58 +msgid "For example, we want to read data from a NetCDF file:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:95 +msgid "" +"This NetCDF files contain 4 datasets, lon_bnds, lat_bnds, tim_bnds and " +"tos. Now select the subdataset, described as: ``NETCDF:\"sst.nc\":tos`` " +"``[24x17x180] sea_surface_temperature (32-bit floating-point)`` and get " +"the information about the number of bands there is inside this variable." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:113 +msgid ".... More metadata" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:143 +msgid ".... More Bands" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:166 +msgid "" +"gdalinfo displays the number of bands into this subdataset. There are " +"metadata attached to each band. In this example, the metadata informs us " +"that each band correspond to an array of monthly sea surface temperature " +"from January 2001. There are 24 months of data in this subdataset. You " +"may also use **gdal_translate** for reading the subdataset." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:172 +msgid "" +"Note that you should provide exactly the contents of the line marked " +"**SUBDATASET_n_NAME** to GDAL, including the **NETCDF:** prefix." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:175 +msgid "" +"The **NETCDF** prefix must be first. It triggers the subdataset NetCDF " +"driver. This driver is intended only for importing remote sensing and " +"geospatial datasets in form of raster images. If you want explore all " +"data contained in NetCDF file you should use another tools." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:180 +msgid "" +"Starting with GDAL 3.5, the :oo:`VARIABLES_AS_BANDS=YES` open option can " +"be used to indicate to the driver that if the netCDF file only contains " +"2D variables of the same type and indexed by the same dimensions, then " +"they should be reported as multiple bands of a same dataset." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:225 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if netCDF`` option to command " +"line utilities accepting it, or ``netCDF`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename, when it is not using subdataset syntax" +" (it can typically be used to force open a HDF5 file that would be " +"nominally recognized by the HDF5 driver)." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:232 +msgid "Dimension" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:234 +msgid "" +"The NetCDF driver assume that data follows the CF-1 convention from " +"`UNIDATA " +"`__ " +"The dimensions inside the NetCDF file use the following rules: (Z,Y,X). " +"If there are more than 3 dimensions, the driver will merge them into " +"bands. For example if you have an 4 dimension arrays of the type (P, T, " +"Y, X). The driver will multiply the last 2 dimensions (P*T). The driver " +"will display the bands in the following order. It will first increment T " +"and then P. Metadata will be displayed on each band with its " +"corresponding T and P values." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:247 +msgid "" +"There is no universal way of storing georeferencing in NetCDF files. The " +"driver first tries to follow the CF-1 Convention from UNIDATA looking for" +" the Metadata named \"grid_mapping\". If \"grid_mapping\" is not present," +" the driver will try to find an lat/lon grid array to set geotransform " +"array. The NetCDF driver verifies that the Lat/Lon array is equally " +"spaced." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:254 +msgid "crs_wkt attribute support" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:256 +msgid "" +"If those 2 methods fail, NetCDF driver will try to read the following " +"metadata directly and set up georeferencing." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:259 +msgid "spatial_ref (Well Known Text)" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:261 +msgid "GeoTransform (GeoTransform array)" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:263 +msgid "or," +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:265 +msgid "Northernmost_Northing" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:266 +msgid "Southernmost_Northing" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:267 +msgid "Easternmost_Easting" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:268 +msgid "Westernmost_Easting" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:270 +msgid "" +"See also the configuration options **GDAL_NETCDF_VERIFY_DIMS** and " +"**GDAL_NETCDF_IGNORE_XY_AXIS_NAME_CHECKS** which control this behavior." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:332 +msgid "" +"This driver supports creation of NetCDF file following the CF-1 " +"convention. You may create set of 2D datasets. Each variable array is " +"named Band1, Band2, ... BandN." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:336 +msgid "" +"Each band will have metadata tied to it giving a short description of the" +" data it contains." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:340 +msgid "GDAL NetCDF Metadata" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:342 +msgid "All NetCDF attributes are transparently translated as GDAL metadata." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:344 +msgid "The translation follow these directives:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:346 +msgid "Global NetCDF metadata have a **NC_GLOBAL** tag prefixed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:347 +msgid "Dataset metadata have their **variable name** prefixed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:348 +msgid "Each prefix is followed by a **#** sign." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:349 +msgid "The NetCDF attribute follows the form: **name=value**." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:363 +msgid "NetCDF global attributes" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:369 +msgid "Variables attributes for: tos, lon, lat and time" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:402 +msgid "" +"On writing, when using the CreateCopy() interface or gdal_translate, " +"dataset level metadata that follows the naming convention " +"NC_GLOBAL#key=value will be used to write the netCDF attributes. Metadata" +" set at the band level using key=value will also be used to write " +"variable attributes." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:408 +msgid "Product specific behavior" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:411 +msgid "Sentinel 5" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:415 +msgid "" +"The most verbose metadata is reported in the ``json:ISO_METADATA``, " +"``json:ESA_METADATA``, ``json:EOP_METADATA``, ``json:QA_STATISTICS``, " +"``json:GRANULE_DESCRIPTION``, ``json:ALGORITHM_SETTINGS`` and " +"``json:SUPPORT_DATA`` metadata domains." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:420 +msgid "Can be discovered for example with:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:532 +msgid "Creation of multidimensional files with CreateCopy() 2D raster API" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:534 +msgid "" +"Starting with GDAL 3.1, the preferred way of creating > 2D files is to " +"use the the :ref:`multidim_raster_data_model` API. However it is possible" +" to create such files with the 2D raster API using the CreateCopy() " +"method (note that at time of writing, this is not supported using the " +"Create() method)." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:539 +msgid "" +"The ``NETCDF_DIM_EXTRA={dim1_name,...dimN_name}`` metadata item must be " +"set on the source dataset, where dim1_name is the name of the slowest " +"varying dimension and dimN_name the name of the fastest varying one." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:543 +msgid "" +"For each extra dimension, the " +"``NETCDF_DIM_{dim_name}_DEF={dimension_size,netcdf_data_type}`` metadata " +"item must be set where dimension_size is the size of the dimension " +"(number of samples along that dimension) and netcdf_data_type is the " +"integer value for the netCDF data type of the corresponding indexing " +"variable. Among the most useful data types:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:549 +msgid "4 for Int" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:550 +msgid "5 for Float" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:551 +msgid "6 for Double" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:552 +msgid "10 for Int64" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:554 +msgid "" +"The ``NETCDF_DIM_{dim_name}_VALUES={value1,...valueN}`` is set to define " +"the values of the indexing variable corresponding to dimension." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:557 +msgid "" +"``dim_name#attribute`` metadata items can also be set to define the " +"attributes of the indexing variable of the dimension." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:560 +msgid "Example of creation of a Time,Z,Y,X 4D file in Python:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:621 +#: ../../source/drivers/vector/csv.rst:252 +#: ../../source/drivers/vector/geojson.rst:415 +#: ../../source/drivers/vector/georss.rst:238 +#: ../../source/drivers/vector/gml.rst:792 +#: ../../source/drivers/vector/gpx.rst:385 +#: ../../source/drivers/vector/jsonfg.rst:186 +#: ../../source/drivers/vector/kml.rst:128 +#: ../../source/drivers/vector/libkml.rst:949 +#: ../../source/drivers/vector/lvbag.rst:53 +#: ../../source/drivers/vector/pgdump.rst:256 +#: ../../source/drivers/vector/selafin.rst:405 +msgid "VSI Virtual File System API support" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:623 +msgid "" +"Since GDAL 2.4, and with Linux kernel >=4.3 and libnetcdf >=4.5, read " +"operations on /vsi file systems are supported using the userfaultfd Linux" +" system call. If running from a container, that system call may be " +"unavailable by default. For example with Docker, ``--security-opt " +"seccomp=unconfined`` might be needed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:628 +msgid "" +"Corollary: operations on /vsi file systems are *not* supported on Windows" +" or MacOSX. If the netCDF file is a NetCDF 4 / HDF5 file, and the HDF5 " +"driver is available, you may set the :config:`GDAL_SKIP` configuration " +"option to ``netCDF`` to force the use of the HDF5 driver. Note that " +"specificities of the netCDF driver, such as support georeferencing with " +"the netCDF CF conventions, will not be available." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:637 +msgid "NetCDF-4 groups support on reading (GDAL >= 3.0)" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:639 +msgid "" +"The driver has undergone significant changes in GDAL 3.0 to support " +"NetCDF-4 groups on reading:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:642 +msgid "Explore recursively all nested groups to create the subdatasets list" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:644 +msgid "" +"Subdatasets in nested groups use the /group1/group2/.../groupn/var " +"standard NetCDF-4 convention, except for variables in the root group " +"which do not have a leading slash for backward compatibility with the " +"NetCDF-3 driver" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:649 +msgid "" +"Global attributes of each nested group are also collected in the GDAL " +"dataset metadata, using the same convention " +"/group1/group2/.../groupn/NC_GLOBAL#attr_name, except for the root group " +"which do not have a leading slash for backward compatibility" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:654 +msgid "" +"When searching for a variable containing auxiliary information on the " +"selected subdataset, like coordinate variables or grid_mapping, we now " +"also search in parent groups and their children as specified in `Support " +"of groups in CF `__" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:665 +msgid "" +"The netCDF driver supports the :ref:`multidim_raster_data_model` for " +"reading and creation operations." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:668 +msgid "" +"The :cpp:func:`GDALGroup::GetGroupNames` method supports the following " +"options:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:670 +msgid "" +"GROUP_BY=SAME_DIMENSION. If set, single-dimensional variables will be " +"exposed as a \"virtual\" subgroup. This enables the user to get a clearer" +" organization of variables, for example in datasets where variables " +"belonging to different trajectories are indexed by different dimensions " +"but mixed in the same netCDF group." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:676 +msgid "" +"The :cpp:func:`GDALGroup::OpenGroup` method supports the following " +"options:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:678 +msgid "GROUP_BY=SAME_DIMENSION. See above description" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:680 +msgid "" +"The :cpp:func:`GDALGroup::GetMDArrayNames` method supports the following " +"options:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:682 +msgid "" +"SHOW_ALL=YES/NO. Defaults to NO. If set to YES, all variables will be " +"listed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:683 +msgid "" +"SHOW_ZERO_DIM=YES/NO. Defaults to NO. If set to NO, variables with " +"0-dimension will not be listed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:685 +msgid "" +"SHOW_COORDINATES=YES/NO. Defaults to YES. If set to NO, variables " +"refererenced in the ``coordinates`` attribute of another variable will " +"not be listed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:687 +msgid "" +"SHOW_BOUNDS=YES/NO. Defaults to YES. If set to NO, variables refererenced" +" in the ``bounds`` attribute of another variable will not be listed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:689 +msgid "" +"SHOW_INDEXING=YES/NO. Defaults to YES. If set to NO, single-dimensional " +"variables whose name is equal to the name of their indexing variable will" +" not be listed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:692 +msgid "" +"SHOW_TIME=YES/NO. Defaults to YES. If set to NO, single-dimensional " +"variables whose ``standard_name`` attribute is \"time\" will not be " +"listed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:695 +msgid "" +"GROUP_BY=SAME_DIMENSION. If set, single-dimensional variables will not be" +" listed" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:697 +msgid "" +"The :cpp:func:`GDALGroup::OpenMDArray` method supports the following " +"options:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:699 +msgid "" +"USE_DEFAULT_FILL_AS_NODATA=YES/NO. (GDAL >= 3.6) Defaults to NO. If set " +"to YES, the default fill value will be used as nodata when there is no " +"_FillValue or missing_value attribute (except on variables of type Byte, " +"UByte, Char)" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:703 +msgid "" +"The :cpp:func:`GDALGroup::CreateMDArray` method supports the following " +"options:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:705 +msgid "" +"NC_TYPE=NC_CHAR/NC_BYTE/NC_INT64/NC_UINT64: to overload the netCDF data " +"type normally deduced from the GDAL data type passed to CreateMDArray(). " +"NC_CHAR can only be used for strings of a fixed size." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:708 +msgid "" +"BLOCKSIZE=size_dim0,size_dim1,...,size_dimN: to set the netCDF chunk " +"size, as set by nc_def_var_chunking(). There must be exactly as many " +"values as the number of dimensions passed to CreateMDArray()" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:711 +msgid "COMPRESS=DEFLATE: to ask for deflate compression" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:712 +msgid "ZLEVEL=number: DEFLATE compression level (1-9)" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:713 +msgid "" +"CHECKSUM=YES/NO: Whether to turn on Fletcher32 checksums. Checksum " +"generation requires chunking, and if no explicit chunking has been asked " +"with the BLOCKSIZE option, a default one will be used. Defaults to NO." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:716 +msgid "" +"FILTER=filterid,param1,...,paramN: Define a filter (typically a " +"compression method) used for writing. This should be a list of numeric " +"values, separated by commas. The first value is the filter id (list of " +"potential values at " +"https://support.hdfgroup.org/services/contributions.html#filters) and " +"following values are per-filter parameters. More details about netCDF-4 " +"filter support at https://www.unidata.ucar.edu/software/netcdf/docs" +"/md__Users_wfisher_Desktop_docs_netcdf-c_docs_filters.html" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:726 +msgid "This driver is compiled with the UNIDATA NetCDF library." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:728 +msgid "" +"You need to download or compile the NetCDF library before configuring " +"GDAL with NetCDF support." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:731 +msgid "" +"See `NetCDF GDAL wiki `__ for " +"build instructions and information regarding HDF4, NetCDF-4 and HDF5." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:737 +msgid ":ref:`Vector side of the netCDF driver. `" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:738 +msgid "" +"`NetCDF CF-1.5 convention `__" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:740 +#: ../../source/drivers/vector/netcdf.rst:500 +msgid "" +"`NetCDF compiled libraries " +"`__" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:742 +#: ../../source/drivers/vector/netcdf.rst:502 +msgid "" +"`NetCDF Documentation " +"`__" +msgstr "" + +#: ../../source/drivers/raster/ngsgeoid.rst:5 +msgid "NGSGEOID - NOAA NGS Geoid Height Grids" +msgstr "" + +#: ../../source/drivers/raster/ngsgeoid.rst:7 +msgid "NGSGEOID" +msgstr "" + +#: ../../source/drivers/raster/ngsgeoid.rst:11 +msgid "" +"GDAL supports reading NOAA NGS geoid height grids in binary format (.bin " +"files). Those files can be used for vertical datum transformations." +msgstr "" + +#: ../../source/drivers/raster/ngsgeoid.rst:24 +msgid "" +"`Description of NGS Geoid Height Grids format " +"`__" +msgstr "" + +#: ../../source/drivers/raster/ngsgeoid.rst:26 +msgid "`GEOID09 main page `__" +msgstr "" + +#: ../../source/drivers/raster/ngsgeoid.rst:27 +msgid "`USGG2009 main page `__" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:4 ../../source/drivers/vector/ngw.rst:4 +msgid "NGW -- NextGIS Web" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:8 ../../source/drivers/vector/ngw.rst:8 +msgid "NGW" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:12 +#: ../../source/drivers/vector/ngw.rst:12 +msgid "" +"NextGIS Web - is a server GIS, which allows storing and editing geodata " +"and to display maps in web browser. Also NextGIS Web can share geodata " +"with other NextGIS software." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:16 +#: ../../source/drivers/vector/ngw.rst:16 +msgid "NextGIS Web has the following features:" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:18 +#: ../../source/drivers/vector/ngw.rst:18 +msgid "" +"Display maps in a web browser (different maps with different layers and " +"styles)" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:20 +#: ../../source/drivers/vector/ngw.rst:20 +msgid "Flexible permissions management" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:21 +#: ../../source/drivers/vector/ngw.rst:21 +msgid "" +"Load geodata from PostGIS or import from GIS formats (ESRI Shape, GeoJSON" +" or GeoTIFF)" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:23 +#: ../../source/drivers/vector/ngw.rst:23 +msgid "" +"Load vector geodata in the following formats: GeoJSON, CSV, ESRI Shape, " +"Mapinfo tab" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:25 +#: ../../source/drivers/vector/ngw.rst:25 +msgid "Import map styles from QGIS project or set them manually" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:26 +#: ../../source/drivers/vector/ngw.rst:26 +msgid "Act as a server for TMS, WMS, MVT, WFS" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:27 +#: ../../source/drivers/vector/ngw.rst:27 +msgid "Act as a client for WMS" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:28 +#: ../../source/drivers/vector/ngw.rst:28 +msgid "" +"User can add photos to records, change record attributes via web " +"interface or WFS-T protocol" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:31 +#: ../../source/drivers/vector/ngw.rst:31 +msgid "" +"NextGIS Web - is an open source software (license GPL v2+, see `GNU " +"General Public License, version 2 `__)." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:41 +#: ../../source/drivers/vector/ngw.rst:41 +msgid "Driver" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:43 +msgid "NextGIS Web supports several raster types:" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:45 +msgid "Raster style" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:46 +msgid "Vector style" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:47 +msgid "WMS layer" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:48 +msgid "WMS Service" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:49 +msgid "Web map as combination of raster and vector styles" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:51 +msgid "" +"Each NextGIS Web raster layer can have one or more raster styles. Each " +"NextGIS Web vector or PostGIS layer can have one or more vector styles " +"(QGIS qml or MapServer xml). WMS layers from external WMS service have no" +" styles. WMS Service is usual WMS protocol implementation." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:57 +msgid "" +"NGW driver supports only raster and vector styles and WMS layers. You can" +" get raster data as tiles or image (only tiles are supported now)." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:61 +msgid "" +"The driver supports read and copy from existing source dataset operations" +" on rasters." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:67 +#: ../../source/drivers/vector/ngw.rst:50 +msgid "" +"The minimal syntax to open a NGW datasource is: NGW:[NextGIS Web " +"URL][/resource/][resource identifier]" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:70 +msgid "" +"**NextGIS Web URL** may be an url to nextgis.com cloud service (for " +"example, https://demo.nextgis.com), or some other url including port and " +"additional path (for example, http://192.168.1.1:8000/test)." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:73 +#: ../../source/drivers/vector/ngw.rst:56 +msgid "" +"**resource** is mandatory keyword dividing resource identifier from the " +"rest of URL." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:75 +#: ../../source/drivers/vector/ngw.rst:58 +msgid "" +"**resource identifier** this is positive number from 0 and above. This " +"may be a resource group, vector, PostGIS or raster layer, style." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:78 +msgid "" +"If identifier is resource group, all vector layers, PostGIS, raster " +"layers, styles will be listed as child resources. In other case this will" +" be a separate raster." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:85 +#: ../../source/drivers/raster/stacta.rst:27 +#: ../../source/drivers/vector/amigocloud.rst:127 +#: ../../source/drivers/vector/carto.rst:182 +#: ../../source/drivers/vector/csv.rst:495 +#: ../../source/drivers/vector/csw.rst:91 +#: ../../source/drivers/vector/dwg.rst:41 +#: ../../source/drivers/vector/edigeo.rst:41 +#: ../../source/drivers/vector/eeda.rst:65 +#: ../../source/drivers/vector/filegdb.rst:246 +#: ../../source/drivers/vector/geojson.rst:153 +#: ../../source/drivers/vector/gml.rst:38 +#: ../../source/drivers/vector/gpkg.rst:487 +#: ../../source/drivers/vector/gpx.rst:54 +#: ../../source/drivers/vector/jsonfg.rst:86 +#: ../../source/drivers/vector/mitab.rst:188 +#: ../../source/drivers/vector/mssqlspatial.rst:218 +#: ../../source/drivers/vector/ngw.rst:67 +#: ../../source/drivers/vector/oci.rst:127 +#: ../../source/drivers/vector/ods.rst:64 +#: ../../source/drivers/vector/ogdi.rst:70 +#: ../../source/drivers/vector/openfilegdb.rst:85 +#: ../../source/drivers/vector/osm.rst:87 +#: ../../source/drivers/vector/pdf.rst:93 +#: ../../source/drivers/vector/pg.rst:398 +#: ../../source/drivers/vector/pgdump.rst:250 +#: ../../source/drivers/vector/pgeo.rst:61 +#: ../../source/drivers/vector/plscenes_data_v1.rst:123 +#: ../../source/drivers/vector/shapefile.rst:414 +#: ../../source/drivers/vector/sqlite.rst:427 +#: ../../source/drivers/vector/vfk.rst:54 +#: ../../source/drivers/vector/wasp.rst:25 +#: ../../source/drivers/vector/wfs.rst:366 +#: ../../source/drivers/vector/xls.rst:22 +#: ../../source/drivers/vector/xlsx.rst:73 +msgid "|about-config-options| The following configuration options are available:" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:117 +#: ../../source/drivers/vector/ngw.rst:102 +msgid "" +"Any operations (read, write, get metadata, change properties, etc.) may " +"require an authenticated access. Authenticated access is obtained by " +"specifying user name and password in open, create or configuration " +"options." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:154 +msgid "Create copy options" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:156 +msgid "" +"NextGIS Web supports only GeoTIFF file format. Prior version 3.1 " +"supported only 3 (RGB) or 4 (RGBA) bands rasters with datatype Byte. In " +"CreateCopy function if source dataset has GeoTIFF file format it will " +"copy as is. For other formats the additional transformation to temporary " +"GeoTIFF file will execute." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:161 +msgid "The following copy options are available:" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:163 +msgid "KEY - Key value. Must be unique in whole NextGIS Web instance. Optional." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:164 +msgid "DESCRIPTION - Resource description. Optional." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:165 +msgid "" +"RASTER_STYLE_NAME - Raster style name. Optional. Default is same as " +"raster layer name." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:167 +msgid "" +"RASTER_QML_PATH - Path to QGIS QML raster style file. Optional for " +"RGB/RGBA, for other bands count/pixel types is mandatory." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:169 +msgid "USERPWD - Username and password, separated by colon." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:170 +msgid "" +"CACHE_EXPIRES=604800 - Time in seconds cached files will stay valid. If " +"cached file expires it is deleted when maximum size of cache is reached. " +"Also expired file can be overwritten by the new one from web. Defaults to" +" 604800 (7 days)." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:174 +msgid "" +"CACHE_MAX_SIZE=67108864 - The cache maximum size in bytes. If cache " +"reached maximum size, expired cached files will be deleted. Defaults to " +"67108864 (64Mb)." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:177 +msgid "" +"JSON_DEPTH=32 - The depth of json response that can be parsed. If depth " +"is greater than this value, parse error occurs." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:183 +msgid "" +"NextGIS Web metadata are supported in datasource, vector, PostGIS, raster" +" layers and styles. Metadata are stored at specific domain \"NGW\". " +"NextGIS Web supported metadata are strings and numbers. Metadata keys " +"with decimal numbers will have suffix **.d** and for real numbers - " +"**.f**. To create new metadata item, add new key=value pair in NGW domain" +" use the *SetMetadataItem* function and appropriate suffix. During " +"transferring to NextGIS Web, suffix will be omitted. You must ensure that" +" numbers correctly transform from string to number." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:192 +#: ../../source/drivers/vector/ngw.rst:290 +msgid "" +"Resource description and key map to appropriate *description* and " +"*keyname* metadata items in default domain. Changing those metadata items" +" will cause an update of resource properties." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:196 +#: ../../source/drivers/vector/ngw.rst:294 +msgid "" +"Resource creation date, type and parent identifier map to appropriate " +"read-only metadata items *creation_date*, *resource_type* and *parent_id*" +" in default domain." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:203 +msgid "Read datasource contensts (1730 is resource group identifier):" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:209 +msgid "Read raster details (1734 is raster layer identifier):" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:218 +msgid ":ref:`Vector side of the driver `" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:219 +msgid "" +"`NextGIS Web documentation " +"`__" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:221 +msgid "" +"`NextGIS Web for developers " +"`__" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:5 +msgid "NITF -- National Imagery Transmission Format" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:7 +msgid "NITF" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:17 +msgid "" +"GDAL supports reading of several subtypes of NITF (National Imagery " +"Transmission Format) image files, and writing simple NITF 2.1 files. NITF" +" 1.1, NITF 2.0, NITF 2.1 and NSIF 1.0 files with uncompressed, ARIDPCM " +"(Adaptive Recursive Interpolated Differential Pulse Code Modulation), " +"JPEG compressed, JPEG2000 (with Kakadu, ECW SDKs or other JPEG2000 " +"capable driver) or VQ (Vector Quantized) compressed images should be " +"readable." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:23 +msgid "" +"The read support test has been tested on various products, including CIB " +"(Controlled Image Base) and CADRG (Compressed ARC Digitized Raster " +"Graphics) frames from RPF (Raster Product Format) products, ECRG " +"(Enhanced Compressed Raster Graphics) frames, HRE (High Resolution " +"Elevation) products." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:28 +msgid "" +"Color tables for pseudocolored images are read. In some cases nodata " +"values may be identified." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:31 +msgid "" +"Lat/Long extents are read from the IGEOLO (Image GeoLocation) information" +" in the image header if available. If high precision lat/long " +"georeferencing information is available in RPF auxiliary data it will be " +"used in preference to the low precision IGEOLO information. In case a " +"BLOCKA (Image Block Information) instance is found, the higher precision " +"coordinates of BLOCKA are used if the block data covers the complete " +"image - that is the L_LINES field with the row count for that block is " +"equal to the row count of the image. Additionally, all BLOCKA instances " +"are returned as metadata. If GeoSDE TRE (Tagged Record Extension) are " +"available, they will be used to provide higher precision coordinates. If " +"the RPC00B (or RPC00A) TRE is available, it is used to report RPC (Rapid " +"Positioning Capability / Rational Polynomial Coefficients) metadata. " +"Starting with GDAL 2.2, RPC information can be retrieved from \\_rpc.txt " +"files, and they will be used in priority over internal RPC00B values, " +"since the latter have less precision than the ones stored in external " +"\\_rpc.txt." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:48 +msgid "" +"Most file header and image header fields are returned as dataset level " +"metadata." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:90 +msgid "" +"On export NITF files are always written as NITF 2.1 with one image and no" +" other auxiliary layers. Images are uncompressed by default, but JPEG and" +" JPEG2000 compression are also available. Georeferencing can only be " +"written for images using a geographic coordinate system or a UTM WGS84 " +"projection. Coordinates are implicitly treated as WGS84 even if they are " +"actually in a different geographic coordinate system. Pseudo-color tables" +" may be written for 8bit images." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:98 +msgid "" +"In addition to the export oriented CreateCopy() API, it is also possible " +"to create a blank NITF file using Create() and write imagery on demand. " +"However, using this methodology writing of pseudocolor tables and " +"georeferencing is not supported unless appropriate IREP (Image " +"Representation) and ICORDS (Image Coordinate) creation options are " +"supplied." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:104 +msgid "" +"Most file header, imagery header metadata and security fields can be set " +"with appropriate **creation options** (although they are reported as " +"metadata item, but must not be set as metadata). For instance setting " +"`\"FTITLE=Image of abandoned missile silo south west of Karsk\"` in the " +"creation option list would result in setting of the FTITLE field in the " +"NITF file header. Use the official field names from the NITF " +"specification document; do not put the \"NITF\\_\" prefix that is " +"reported when asking the metadata list." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:123 +msgid "NC is the default value, and means no compression." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:124 +msgid "" +"C3 means JPEG compression and is only available for the CreateCopy() " +"method. The QUALITY and PROGRESSIVE JPEG-specific creation options can be" +" used. See the :ref:`raster.jpeg` driver. Multi-block images can be " +"written." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:128 +msgid "" +"M3 is a variation of C3. The only difference is that a block map is " +"written, which allow for fast seeking to any block." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:130 +msgid "" +"C8 means JPEG2000 compression (one block) and is available for " +"CreateCopy() and/or Create() methods. See below paragraph for " +"specificities." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:303 +msgid "JPEG2000 compression (write support)" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:305 +msgid "" +"JPEG2000 compression is available when using the IC=C8 creation option, " +"if the JP2ECW (SDK 3.3, or for later versions assuming the user has the " +"key to enable JPEG2000 writing), JP2KAK or JP2OpenJPEG driver are " +"available." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:309 +msgid "" +"They are tried in that order when several ones are available, unless the " +"JPEG2000_DRIVER creation option (added in GDAL 3.4) is set to explicitly " +"specify the JPEG2000 capable driver to use." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:313 +msgid "" +":ref:`JP2ECW `: The :co:`drivers/raster/jp2ecw TARGET` " +"(target size reduction as a percentage of the original) and " +":co:`drivers/raster/jp2ecw PROFILE`\\ " +"=BASELINE_0/BASELINE_1/BASELINE_2/NPJE/EPJE JP2ECW-specific creation " +"options can be used. Both CreateCopy() and/or Create() methods are " +"available. By default the NPJE PROFILE will be used (thus implying " +"BLOCKXSIZE=BLOCKYSIZE=1024)." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:319 +msgid "" +":ref:`JP2KAK `: The :co:`drivers/raster/jp2kak QUALITY`, " +":co:`drivers/raster/jp2kak BLOCKXSIZE`, :co:`drivers/raster/jp2kak " +"BLOCKYSIZE`, :co:`drivers/raster/jp2kak LAYERS`, " +":co:`drivers/raster/jp2kak ROI` JP2KAK-specific creation options can be " +"used. Only CreateCopy() method is available." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:327 +msgid "" +":ref:`JP2OpenJPEG `: (only in the CreateCopy() case)." +" The :co:`drivers/raster/jp2openjpeg QUALITY`, " +":co:`drivers/raster/jp2openjpeg BLOCKXSIZE` and " +":co:`drivers/raster/jp2openjpeg BLOCKYSIZE` JP2OpenJPEG-specific creation" +" options can be used. By default BLOCKXSIZE=BLOCKYSIZE=1024 will be used." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:335 +msgid "" +"Starting with GDAL 3.4.0 and OpenJPEG 2.5, the " +"PROFILE=NPJE_VISUALLY_LOSSLESS/NPJE_NUMERICALLY_LOSSLESS creation option " +"can be used to create files that comply with `STDI-0006 NITF Version 2.1 " +"Commercial Dataset Requirements Document (NCDRD) " +"`__. For NPJE_VISUALLY_LOSSLESS, the last quality layer " +"defaults to 3.9 bits per pixel and per band. It can be adjusted with the " +"QUALITY creation option. When those profiles are specified, the J2KLRA " +"TRE will also be written, unless the ``J2KLRA=NO`` creation option is " +"specified." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:347 +msgid ":ref:`Advanced GDAL NITF Driver Information `" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:348 +msgid "`NITFS Technical Board Public Page `__" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:349 +msgid "" +"`DIGEST Part 2 Annex D (describe encoding of NITF Spatial Data " +"Extensions) " +"`__" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:351 +msgid "" +":ref:`raster.rpftoc`: to read the Table Of Contents of CIB and CADRG " +"products." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:352 +#: ../../source/drivers/raster/rpftoc.rst:57 +msgid "" +"`MIL-PRF-89038 `__ : specification of RPF," +" CADRG, CIB products" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:354 +msgid ":ref:`raster.ecrgtoc`: to read the Table Of Contents of ECRG products." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:359 +msgid "Credit" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:361 +msgid "" +"The author wishes to thank `AUG Signals `__ " +"and the `GeoConnections `__ program for " +"supporting development of this driver, and to thank Steve Rawlinson " +"(JPEG), Reiner Beck (BLOCKA) for assistance adding features." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:5 +msgid "NITF -- Advanced Driver Information" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:7 +msgid "" +"The NITF (National Imagery Transmission Format) driver in GDAL includes a" +" number of advanced, and somewhat esoteric options not suitable for the " +":ref:`general end user documentation ` for the driver. This " +"information is collected here, and is primarily aimed at developers and " +"advanced users." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:14 +msgid "CGM Segments" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:16 +msgid "" +"NITF files that have CGM data (that is segment type GR - graphics, or SY " +"with an STYPE value of 'C') will make that information available as " +"metadata in the CGM domain. The returned metadata will look something " +"like:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:32 +msgid "" +"The SLOC_ROW and SLOC_COL values are the placement of the CGM object " +"relative to the base (SALVL) image. The CCS_ROW/COL values are relative " +"to the common coordinate system. The \\_SDLVL is the display level. The " +"DATA is the raw CGM data with \"backslash quotable\" escaping applied. " +"All occurrences of ASCII zero will be translated to '\\0', and all " +"backslashes and double quotes will be backslashed escaped. The " +"CPLUnescapeString() function can be used to unescape the data into binary" +" format using scheme CPLES_BackslashQuotable." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:41 +msgid "" +"To add CGM data to a NITF image, you can pass creation options in the " +"following format:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:53 +msgid "" +"Notice that passing CGM as creation options will overwrite existing CGM " +"segment read in the CGM metadata domain." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:56 +msgid "" +"While GDAL does not support parsing or rendering CGM data, at least one " +"user has found the `UniConverter " +"`__" +" library useful for this purpose." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:62 +msgid "Multi-Image NITF Files" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:64 +msgid "" +"NITF files with more than one image segment (IM) will present the image " +"segments as subdatasets. Opening a multiple NITF file by filename will " +"provide access to the first image segment. The subdataset metadata for a " +"3 image NITF file might look like:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:79 +msgid "" +"In this case opening \"multi_image_jpeg_2.0.ntf\" directly will give " +"access to \"NITF_IM:0:multi_image_jpeg_2.0.ntf\". To open the others use " +"the corresponding subdataset names. The Subdataset mechanism is generic " +"GDAL concept discussed in the :ref:`raster_data_model` document." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:85 +msgid "Text Segments" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:87 +msgid "" +"NITF files that have text segments (that is segment type TX) will make " +"that information available as metadata in the TEXT domain. The returned " +"metadata will look something like:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:108 +msgid "" +"The argument to DATA_n is the raw text of the n'th (zero based) text " +"segment with no escaping of any kind applied." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:111 +msgid "" +"The TEXT segment header data is preserved in HEADER_n metadata item. The " +"CreateCopy() method on the NITF driver also supports creating text " +"segments on the output file as long as the input file has metadata in the" +" TEXT domain as defined above." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:116 +msgid "" +"To add TEXT data to a NITF image, you can also pass creation options in " +"the following format:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:126 +msgid "" +"Notice that passing TEXT as creation options will overwrite existing text" +" segment read in the TEXT metadata domain." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:130 +msgid "TREs" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:132 +msgid "" +"NITF files with registered (or unregistered?) extensions on the file " +"header, or the referenced image header will make them available in a raw " +"form in metadata via the TRE domain. The TRE domain will hold one " +"metadata item per TRE which will have the name of the TRE as the name, " +"and the data of the TRE as the contents. The data contents will be " +"\"backslash escaped\" like CGM data above." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:139 +msgid "" +"In case of multiple occurrences of the same TRE, the second occurrence " +"will be named \"TRENAME_2\", the third \"TRENAME_3\" where TRENAME is the" +" TRE name." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:157 +msgid "TREs as xml:TRE" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:159 +msgid "" +"All TREs found in file and matching one of the TRE description of the " +"`nitf_spec.xml " +"`__ in " +"GDAL data directory will be reported as XML content in the xml:TRE " +"metadata domain." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:217 +msgid "TRE creation from hexadecimal data" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:219 +msgid "" +"TRE data can be added to a newly created NITF file in hexadecimal format " +"to encode binary data such as unsigned int or floating point types. The " +"hexadecimal TRE creation option is supplied as " +"\"TRE=HEX/=\" or " +"\"FILE_TRE=HEX/=" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:229 +msgid "TRE creation as TRE_OVERFLOW DES" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:231 +msgid "" +"The following example shows how to create a CSEPHA TRE as a TRE_OVERFLOW " +"DES:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:262 +msgid "" +"Note the use of the RESERVE_SPACE_FOR_TRE_OVERFLOW=YES creation option to" +" reserve space for the IXSOFL field in the image subheader pointed by " +"DESITEM." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:267 +msgid "Data Extension Segments (xml:DES)" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:268 +msgid "" +"Data Extension Segments (DESs) are user-defined metadata extensions to " +"the NITF format. The DES metadata is available through the xml\\:DES " +"metadata domain. The xml\\:DES domain returns an XML string with " +"standard and user-defined DES fields in plain text, and the user-defined " +"DES data as Base64 encoded text. The following is an example XML " +"structure:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:289 +msgid "Raw File / Image Headers" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:291 +msgid "" +"In some cases application may need to recover very specific information " +"from the image or file headers that isn't normally available as metadata." +" In this case it is possible to query the \"NITF_METADATA\" metadata " +"domain. The complete file and image headers will be returned as metadata " +"in base64 encoded format. Something like:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:303 +msgid "" +"Note that the ascii encoded numeric values prefixing the base64 encoded " +"header is the length (decoded) in bytes, followed by one space." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:307 +msgid "Writing multiple Image Segments" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:309 +msgid "(GDAL >= 3.4)" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:311 +msgid "" +"Writing a NITF file with several image segments is done with the " +"``APPEND_SUBDATASET=YES`` creation option but requires some care." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:314 +msgid "" +"The file must be created with the content of the first image segment with" +" the ``NUMI`` creation option to specify the total number of image " +"segments and optionally with the ``NUMDES`` creation option with the " +"number of DE segments. TREs that apply to the whole file should also be " +"specified at that stage. The ``APPEND_SUBDATASET`` creation option must " +"NOT be specified." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:320 +msgid "" +"Subsequent images are appended with the ``APPEND_SUBDATASET=YES`` " +"creation option. The ``IDLVL``, ``IALVL``, ``ILOCROW`` and ``ILOCCOL`` " +"creation option may be specified." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:323 +msgid "" +"On the last image segment, the DES content, if any must be specified with" +" the ``DES`` creation option." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:326 +msgid "The file will only be valid if all NUMI images have been actually written." +msgstr "" + +#: ../../source/drivers/raster/noaa_b.rst:5 +msgid "NOAA_B -- NOAA GEOCON/NADCON5 .b format" +msgstr "" + +#: ../../source/drivers/raster/noaa_b.rst:9 +msgid "NOAA_B" +msgstr "" + +#: ../../source/drivers/raster/noaa_b.rst:13 +msgid "" +"GDAL supports reading geodetic grids in the NOAA .b binary format used " +"for GEOCON and NADCON5 grids." +msgstr "" + +#: ../../source/drivers/raster/noaa_b.rst:26 +msgid "" +"`Format specification " +"`__: See " +"paragraph 10.2, \".b grids (GEOCON and NADCON 5.0)\"" +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:5 +msgid "NSIDCbin -- National Snow and Ice Data Centre Sea Ice Concentrations" +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:7 +msgid "NSIDCbin" +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:14 +msgid "" +"Supported by GDAL for read access. This format is a raw binary format for" +" the Nimbus-7 SMMR and DMSP SSM/I-SSMIS Passive Microwave Data sea ice " +"concentrations. There are daily and monthly maps in the north and south " +"hemispheres supported by this driver." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:19 +msgid "" +"Support includes an affine georeferencing transform, and projection - " +"these are both 25000m resolution polar stereographic grids centred on the" +" north and south pole respectively. Metadata from the file including " +"julian day and year are recorded." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:24 +msgid "" +"This driver is implemented based on the NSIDC documentation in the `User " +"Guide `__." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:26 +msgid "" +"Band values are Byte, sea ice concentration (fractional coverage scaled " +"by 250)." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:28 +msgid "" +"The dataset band implements GetScale() which will convert the values from" +" 0,255 to 0.0,102.0 by multiplying by 0.4. Unscaled values above 250 have" +" specific meanings, 251 is Circular mask used in the Arctic, 252 is " +"Unused, 253 is Coastlines, 254 is Superimposed land mask, 255 is Missing " +"data." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:33 +msgid "NOTE: Implemented as :source_file:`frmts/raw/nsidcbindataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:43 +#: ../../source/drivers/vector/esrijson.rst:73 +#: ../../source/drivers/vector/georss.rst:248 +#: ../../source/drivers/vector/gpx.rst:395 +#: ../../source/drivers/vector/idb.rst:67 +#: ../../source/drivers/vector/kml.rst:138 +#: ../../source/drivers/vector/oci.rst:314 +#: ../../source/drivers/vector/pdf.rst:59 +#: ../../source/drivers/vector/pgdump.rst:265 +#: ../../source/drivers/vector/sqlite.rst:561 +msgid "Example" +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:45 +msgid "" +"For example, we want to read monthly data from September 2019, with data " +"from this source (requires authentication)." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:47 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/ntv2.rst:5 +msgid "NTv2 -- NTv2 Datum Grid Shift" +msgstr "" + +#: ../../source/drivers/raster/ntv2.rst:7 +msgid "NTv2" +msgstr "" + +#: ../../source/drivers/raster/ntv2.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/raw/ntv2dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:5 +msgid "NWT_GRD/NWT_GRC -- Northwood/Vertical Mapper File Format" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:7 +msgid "NWT_GRD" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:9 +msgid "NWT_GRC" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:13 +msgid "" +"Support for reading & writing Northwood GRID raster formats. This format " +"is also known as Vertical Mapper Grid or MapInfo Grid and is commonly " +"used in MapInfo Pro software" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:17 +msgid "" +"Full read/write support of \\*.grd (grid) files is available, read-only " +"support is available for classified grids (\\*.grc)." +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:20 +msgid "For writing, Float32 is the only supported band type." +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:23 +msgid "Driver capabilities (NWT_GRD)" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:34 +msgid "Driver capabilities (NWT_GRC)" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:41 +msgid "Color Information" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:43 +msgid "" +"The grid formats have color information embedded in the grid file header." +" This describes how to scale data values to RGB values. When opening in " +"read mode, the driver will report 4 bands - R, G, B and the data band. In" +" reality there is 1 band and the RGB bands are 'virtual', made from " +"scaling data. For this reason, when opening in write mode only 1 band is " +"reported and the RGB bands are unavailable." +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:53 +msgid "GDAL Metadata items are stored in the PAM .aux.xml file" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:55 +msgid "Northwood Grid itself does not natively support arbitrary metadata" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:58 +msgid "Nodata values" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:60 +msgid "" +"In write mode, it is possible to designate any value as the nodata value." +" These values are translated to the Vertical Mapper no data value when " +"writing. Therefore, in read mode the nodata value is always reported as " +"-1e37." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:5 +msgid "OGCAPI -- OGC API Tiles / Maps / Coverage" +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:9 +msgid "OGCAPI" +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:13 +msgid "" +"Access to server implementing OGC API - Tiles, OGC API - Maps or OGC API " +"- Coverages. This driver has raster and vector capabilities." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:18 +msgid "" +"This driver is experimental, and has been developed to demonstrate work " +"related to the \"Modular OGC API Workflows\" initiative. It implements " +"non-finalized versions of OGC API - Tiles, - Maps and - Coverages. Its " +"interface may change at any time, or it might be removed. It might also " +"be eventually merged with the OGC API - Features driver." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:30 +msgid "Dataset opening" +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:32 +msgid "The driver supports opening by:" +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:34 +msgid "" +"passing a filename (with .moaw extension) containing a JSON document, " +"like the following, specifying a deferred processing" +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:51 +msgid "" +"passing a string \"OGCAPI:{url}\" where {url} is the URL to a OGC API " +"landing page In that case the driver will return subdatasets with the " +"different collections." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:54 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if OGCAPI`` option to command " +"line utilities accepting it, or ``OGCAPI`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed URL, without the ``OGCAPI:`` prefix." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:59 +msgid "" +"passing a string \"OGCAPI:{url}\" where {url} is the URL to a OGC API " +"collection description" +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:62 +msgid "" +"When the driver opens a collection, for raster, it will look if tiles or " +"maps API are advertized for it. It will use tiles API by default, and " +"fallback to maps API when not available. It will also look at the image " +"formats, and will prefer PNG When available." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:67 +msgid "" +"For vector collections, this driver handles the tiles API, with GeoJSON " +"or Mapbox Vector tiles." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:70 +msgid "" +"When using the tiles API, the driver will use by default the " +"WorldCRS84Quad tile matrix set when available" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:8 +#: ../../source/drivers/vector/openfilegdb.rst:6 +msgid "OpenFileGDB" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:12 +msgid "" +"The OpenFileGDB driver provides read access to raster layers of File " +"Geodatabases (.gdb directories). The dataset name must be the " +"directory/folder name, and it must end with the .gdb extension." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:16 +#: ../../source/drivers/vector/openfilegdb.rst:16 +msgid "" +"It can also read directly zipped .gdb directories (with .gdb.zip " +"extension), provided they contain a .gdb directory at their first level." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:19 +msgid "The driver supports:" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:21 +msgid "reading CRS information" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:22 +msgid "reading geotransform" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:23 +msgid "exposing overviews" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:24 +msgid "exposing nodata mask band or nodata value" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:25 +msgid "uncompressed, LZ77, JPEG and JPEG2000 compression methods." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:26 +msgid "exposing value attribute tables as GDAL Raster attribute tables." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:28 +msgid "" +"Support for FileGDB created by ArcGIS v10 has been added in GDAL 3.7 " +"Support for FileGDB created by ArcGIS v9 has been added in GDAL 3.8" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:39 +#: ../../source/drivers/vector/jsonfg.rst:42 +#: ../../source/drivers/vector/miramon.rst:230 +msgid "Connection string" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:41 +msgid "" +"When a File Geodatabase contains several raster layers, the raster layer " +"that must be opened is specified with the following connection string" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:48 +msgid "" +"When opening a dataset with pointing only to the .gdb directory, and if " +"it contains several raster layers, a list of subdatasets is returned by " +"the driver" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:62 +msgid "" +"In AUTO mode, the driver will expose a dataset nodata mask band, unless " +"the band data type is Float32 or Float64, in which case a nodata value is" +" used." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:65 +msgid "" +"In MASK mode, the driver will expose a dataset nodata mask band for all " +"data types." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:68 +msgid "" +"In NONE mode, the driver will not expose a nodata mask band or a nodata " +"value." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:71 +msgid "" +"When specifying a numeric nodata value (``nan`` accepted for Float32 or " +"Float64), it is used as the band nodata value. The nodata value should be" +" selected outside the range of valid values (but within the range of the " +"data type)." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:79 +msgid "" +"The ``xml:documentation`` and ``xml:definition`` metadata domains contain" +" the XML content from the ``GDB_Items`` table related to the raster " +"layer." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:85 +msgid "List raster layers from a FileGDB" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:91 +msgid "Open a given subdataset:" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:101 +msgid ":ref:`OpenFileGDB vector ` documentation page" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:107 +msgid "" +"Thanks to Richard Barnes and his ArcRescue tool for the deciphering of " +"the band_types field which indicates the compression method and the data " +"type." +msgstr "" + +#: ../../source/drivers/raster/ozi.rst:5 +msgid "OZI -- OZF2/OZFX3 raster" +msgstr "" + +#: ../../source/drivers/raster/ozi.rst:7 +msgid "OZI" +msgstr "" + +#: ../../source/drivers/raster/ozi.rst:11 +msgid "GDAL supports reading OZF2/OZFX3 raster datasets." +msgstr "" + +#: ../../source/drivers/raster/ozi.rst:13 +msgid "" +"Either the image file or the .map file can be passed to GDAL. To retrieve" +" georeferencing, you need to specify the .map file." +msgstr "" + +#: ../../source/drivers/raster/ozi.rst:26 +msgid "" +"`Specification of OZF2/OZFX3 format " +"`__" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:7 +msgid "JAXAPALSAR" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:11 +msgid "" +"This driver provides enhanced support for processed PALSAR products from " +"the JAXA PALSAR processor. This encompasses products acquired from the " +"following organizations:" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:15 +msgid "JAXA (Japanese Aerospace eXploration Agency)" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:16 +msgid "AADN (Alaska Satellite Facility)" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:17 +msgid "ESA (European Space Agency)" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:19 +msgid "" +"This driver does not support products created using the Vexcel processor " +"(i.e. products distributed by ERSDAC and affiliated organizations)." +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:22 +msgid "Support is provided for the following features of PALSAR products:" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:24 +msgid "Reading Level 1.1 and 1.5 processed products" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:25 +msgid "Georeferencing for Level 1.5 products" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:26 +msgid "Basic metadata (sensor information, ground pixel spacing, etc.)" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:27 +msgid "Multi-channel data (i.e. dual-polarization or fully polarimetric datasets)" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:30 +msgid "This is a read-only driver." +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:32 +msgid "" +"To open a PALSAR product, select the volume directory file (for example, " +"VOL-ALPSR000000000-P1.5_UA or VOL-ALPSR000000000-P1.1__A). The driver " +"will then use the information contained in the volume directory file to " +"find the various image files (the IMG-\\* files), as well as the Leader " +"file. Note that the Leader file is essential for correct operation of the" +" driver." +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:49 +msgid "" +"`RESTEC Sample Data `__" +msgstr "" + +#: ../../source/drivers/raster/paux.rst:5 +msgid "PAux -- PCI .aux Labelled Raw Format" +msgstr "" + +#: ../../source/drivers/raster/paux.rst:7 +msgid "PAux" +msgstr "" + +#: ../../source/drivers/raster/paux.rst:11 +msgid "" +"GDAL includes a partial implementation of the PCI .aux labelled raw " +"raster file for read, write and creation. To open a PCI labelled file, " +"select the raw data file itself. The .aux file (which must have a common " +"base name) will be checked for automatically." +msgstr "" + +#: ../../source/drivers/raster/paux.rst:16 +msgid "" +"The format type for creating new files is ``PAux``. All PCI data types " +"(8U, 16U, 16S, and 32R) are supported. Currently georeferencing, " +"projections, and other metadata is ignored." +msgstr "" + +#: ../../source/drivers/raster/paux.rst:32 +msgid "NOTE: Implemented as :source_file:`frmts/raw/pauxdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/paux.rst:34 +msgid "" +"See Also: `PCI's .aux Format Description `__" +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:5 +msgid "PCIDSK -- PCI Geomatics Database File" +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:7 +msgid "PCIDSK" +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:11 +msgid "" +"PCIDSK database file used by PCI EASI/PACE software for image analysis. " +"It is supported for reading, and writing by GDAL. All pixel data types, " +"and data organizations (pixel interleaved, band interleaved, file " +"interleaved and tiled) should be supported. Currently LUT segments are " +"ignored, but PCT segments should be treated as associated with the bands." +" Overall file, and band specific metadata should be correctly associated " +"with the image or bands." +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:19 +msgid "" +"Georeferencing is supported though there may be some limitations in " +"support of datums and ellipsoids. GCP segments are ignored. RPC segments " +"will be returned as GDAL style RPC metadata." +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:23 +msgid "" +"Internal overview (pyramid) images will also be correctly read though " +"newly requested overviews will be built externally as an .ovr file." +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:26 +msgid "Vector segments are also supported by the driver." +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:34 +msgid "" +"Note that PCIDSK files are always produced pixel interleaved, even though" +" other organizations are supported for read." +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:71 +msgid "Implemented as :source_file:`frmts/pcidsk/pcidskdataset2.cpp`." +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:72 +msgid "" +"`PCIDSK SDK " +"`__" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:5 +msgid "PCRaster -- PCRaster raster file format" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:7 +msgid "PCRaster" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:11 +msgid "" +"GDAL includes support for reading and writing PCRaster raster files. " +"PCRaster is a dynamic modeling system for distributed simulation models. " +"The main applications of PCRaster are found in environmental modeling: " +"geography, hydrology, ecology to name a few. Examples include models for " +"research on global hydrology, vegetation competition models, slope " +"stability models and land use change models." +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:18 +msgid "" +"The driver reads all types of PCRaster maps: booleans, nominal, ordinals," +" scalar, directional and ldd. The same cell representation used to store " +"values in the file is used to store the values in memory." +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:22 +msgid "" +"The driver detects whether the source of the GDAL raster is a PCRaster " +"file. When such a raster is written to a file the value scale of the " +"original raster will be used. The driver **always** writes values using " +"UINT1, INT4 or REAL4 cell representations, depending on the value scale:" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:28 +msgid "Value scale" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:28 +msgid "Cell representation" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:30 +#: ../../source/drivers/raster/pcraster.rst:43 +msgid "VS_BOOLEAN" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:30 +#: ../../source/drivers/raster/pcraster.rst:35 +#: ../../source/drivers/raster/pcraster.rst:43 +msgid "CR_UINT1" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:31 +#: ../../source/drivers/raster/pcraster.rst:44 +msgid "VS_NOMINAL" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:31 +#: ../../source/drivers/raster/pcraster.rst:32 +#: ../../source/drivers/raster/pcraster.rst:44 +msgid "CR_INT4" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:32 +msgid "VS_ORDINAL" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:33 +#: ../../source/drivers/raster/pcraster.rst:45 +#: ../../source/drivers/raster/pcraster.rst:46 +msgid "VS_SCALAR" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:33 +#: ../../source/drivers/raster/pcraster.rst:34 +#: ../../source/drivers/raster/pcraster.rst:45 +#: ../../source/drivers/raster/pcraster.rst:46 +msgid "CR_REAL4" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:34 +msgid "VS_DIRECTION" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:35 +msgid "VS_LDD" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:38 +msgid "" +"For rasters from other sources than a PCRaster raster file a value scale " +"and cell representation is determined according to the following rules:" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:42 +msgid "Source type" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:42 +msgid "Target value scale" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:42 +msgid "Target cell representation" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:43 +msgid "GDT_Byte" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:44 +msgid "GDT_Int32" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:45 +msgid "GDT_Float32" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:46 +msgid "GDT_Float64" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:49 +msgid "" +"The driver can convert values from one supported cell representation to " +"another. It cannot convert to unsupported cell representations. For " +"example, it is not possible to write a PCRaster raster file from values " +"which are used as CR_INT2 (GDT_Int16)." +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:54 +msgid "" +"Although the de-facto file extension of a PCRaster raster file is .map, " +"the PCRaster software does not require a standardized file extension." +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:57 +msgid "NOTE: Implemented as :source_file:`frmts/pcraster/pcrasterdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:59 +msgid "" +"See also: `PCRaster website at Utrecht University " +"`__." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:5 ../../source/drivers/vector/pdf.rst:5 +msgid "PDF -- Geospatial PDF" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:7 ../../source/drivers/vector/pdf.rst:7 +msgid "PDF" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:11 +msgid "" +"GDAL supports reading Geospatial PDF documents, by extracting " +"georeferencing information and rasterizing the data. Non-geospatial PDF " +"documents will also be recognized by the driver." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:15 +msgid "" +"PDF documents can be created from other GDAL raster datasets, and OGR " +"datasources can also optionally be drawn on top of the raster layer (see " +"OGR\\_\\* creation options in the below section)." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:20 +msgid "" +"The driver supports reading georeferencing encoded in either of the 2 " +"current existing ways : according to the OGC encoding best practice, or " +"according to the Adobe Supplement to ISO 32000." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:24 +msgid "" +"Multipage documents are exposed as subdatasets, one subdataset par page " +"of the document." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:37 +#: ../../source/drivers/vector/pdf.rst:24 +msgid "Vector support" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:39 +msgid "See the :ref:`PDF vector ` documentation page" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:44 +msgid "" +"The neatline (for OGC best practice) or the bounding box (Adobe style) " +"will be reported as a NEATLINE metadata item, so that it can be later " +"used as a cutline for the warping algorithm." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:51 +msgid "" +"Additional metadata, such as found in USGS Topo PDF can be extracted from" +" the file, and will be stored as XML raw content in the EMBEDDED_METADATA" +" metadata domain." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:123 +msgid "" +"|about-open-options| Above configuration options are also available as " +"open options." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:161 +msgid "LAYERS Metadata domain" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:163 +msgid "" +"When GDAL is compiled against Poppler or PDFium, the LAYERS metadata " +"domain can be queried to retrieve layer names that can be turned ON or " +"OFF. This is useful to know which values to specify for the " +":config:`GDAL_PDF_LAYERS` or :config:`GDAL_PDF_LAYERS_OFF` configuration " +"options." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:169 +#: ../../source/drivers/vector/osm.rst:63 +msgid "For example :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:189 +msgid "Restrictions" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:191 +msgid "" +"The opening of a PDF document (to get the georeferencing) is fast, but at" +" the first access to a raster block, the whole page will be rasterized " +"(with Poppler), which can be a slow operation." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:195 +msgid "" +"Note: some raster-only PDF files (such as some USGS GeoPDF files), that " +"are regularly tiled are exposed as tiled dataset by the GDAL PDF driver, " +"and can be rendered with any backends." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:199 +msgid "" +"Only a few of the possible Datums available in the OGC best practice spec" +" have been currently mapped in the driver. Unrecognized datums will be " +"considered as being based on the WGS84 ellipsoid." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:203 +msgid "" +"For documents that contain several neatlines in a page (insets), the " +"georeferencing will be extracted from the inset that has the largest area" +" (in term of screen points)." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:210 +msgid "" +"PDF documents can be created from other GDAL raster datasets, that have 1" +" band (graylevel or with color table), 3 bands (RGB) or 4 bands (RGBA)." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:213 +msgid "" +"Georeferencing information will be written by default according to the " +"ISO32000 specification. It is also possible to write it according to the " +"OGC Best Practice conventions (but limited to a few datum and projection " +"types)." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:218 +msgid "Note: PDF write support does not require linking to any backend." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:523 +msgid "Update of existing files" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:525 +msgid "" +"Existing PDF files (created or not with GDAL) can be opened in update " +"mode in order to set or update the following elements :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:528 +msgid "" +"Geotransform and associated projection (with SetGeoTransform() and " +"SetProjection())" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:530 +msgid "GCPs (with SetGCPs())" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:531 +msgid "Neatline (with SetMetadataItem(\"NEATLINE\", polygon_definition_in_wkt))" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:533 +msgid "" +"Content of Info object (with SetMetadataItem(key, value) where key is one" +" of AUTHOR, CREATOR, CREATION_DATE, KEYWORDS, PRODUCER, SUBJECT and " +"TITLE)" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:536 +msgid "xml:XMP metadata (with SetMetadata(md, \"xml:XMP\"))" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:538 +msgid "" +"For geotransform or GCPs, the Geo encoding method used by default is " +"ISO32000. OGC_BP can be selected by setting the GDAL_PDF_GEO_ENCODING " +"configuration option to OGC_BP." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:542 +msgid "" +"Updated elements are written at the end of the file, following the " +"incremental update method described in the PDF specification." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:546 +msgid "Creation of PDF file from a XML composition file (GDAL >= 3.0)" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:548 +msgid "" +"A PDF file can be generate from a XML file that describes the composition" +" of the PDF:" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:551 +msgid "number of pages" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:552 +msgid "layer tree, with visibility state, exclusion groups" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:553 +msgid "definition or 0, 1 or several georeferenced areas per page" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:554 +msgid "page content made of rasters, vectors or labels" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:556 +msgid "" +"The GDALCreate() API must be used with width = height = bands = 0 and " +"datatype = GDT_Unknown and :co:`COMPOSITION_FILE` must be the single " +"creation option." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:560 +msgid "" +"The XML schema against which the composition file must validate is " +"`pdfcomposition.xsd " +"`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:563 +msgid "Example on how to use the API:" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:573 +msgid "" +"A sample Python script `gdal_create_pdf.py " +"`__ is also available. " +"Starting with GDAL 3.2, the :ref:`gdal_create` utility can also be used." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:578 +msgid "Example of a composition XML file:" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:674 +msgid "" +"For read support, GDAL must be built against one of the following " +"libraries :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:677 +msgid "`Poppler `__ (GPL-licensed)" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:678 +msgid "`PoDoFo `__ (LGPL-licensed)" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:679 +msgid "" +"`PDFium `__ (New BSD-licensed, " +"supported since GDAL 2.1.0)" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:682 +msgid "" +"Note: it is also possible to build against a combination of several of " +"the above libraries. PDFium will be used in priority over Poppler, itself" +" used in priority over PoDoFo." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:687 +msgid "Unix build" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:689 +msgid "" +"The relevant configure options are --with-poppler, --with-podofo, --with-" +"podofo-lib and --with-podofo-extra-lib-for-test." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:692 +msgid "" +"Starting with GDAL 2.1.0, --with-pdfium, --with-pdfium-lib, --with-" +"pdfium-extra-lib-for-test and --enable-pdf-plugin are also available." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:697 +msgid "Poppler" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:699 +msgid "" +"libpoppler itself must have been configured with " +"-DENABLE_UNSTABLE_API_ABI_HEADERS=ON so that the xpdf C++ headers are " +"available. Note: the poppler C++ API isn't stable, so the driver " +"compilation may fail with too old or too recent poppler versions." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:706 +msgid "PoDoFo" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:708 +msgid "" +"As a partial alternative, the PDF driver can be compiled against " +"libpodofo to avoid the libpoppler dependency. This is sufficient to get " +"the georeferencing and vector information. However, for getting the " +"imagery, the pdftoppm utility that comes with the poppler distribution " +"must be available in the system PATH. A temporary file will be generated " +"in a directory determined by the following configuration options : " +":config:`CPL_TMPDIR`, ``TMPDIR`` or ``TEMP`` (in that order). If none are" +" defined, the current directory will be used. Successfully tested " +"versions are libpodofo 0.8.4, 0.9.1 and 0.9.3. Important note: using " +"PoDoFo 0.9.0 is strongly discouraged, as it could cause crashes in GDAL " +"due to a bug in PoDoFo." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:721 +msgid "PDFium" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:723 +msgid "" +"Using PDFium as a backend allows access to raster, vector, georeferencing" +" and other metadata. The PDFium backend has also support for arbitrary " +"overviews, for fast zoom-out." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:727 +msgid "" +"Only GDAL builds against static builds of PDFium have been tested. " +"Building PDFium can be challenging, and particular builds must be used to" +" work properly with GDAL." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:732 +msgid "With GDAL >= 3.9" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:734 +msgid "" +"The scripts in the ``__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:738 +msgid "With GDAL = 3.8" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:740 +msgid "" +"The scripts in the ``__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:744 +msgid "With GDAL 3.7" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:746 +msgid "" +"The scripts in the ``__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:750 +msgid "With GDAL 3.5 and 3.6" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:752 +msgid "" +"The scripts in the ``__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:756 +msgid "With GDAL 3.4" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:758 +msgid "" +"The scripts in the ``__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:762 +msgid "With GDAL 3.2 and 3.3" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:764 +msgid "" +"The scripts in the ``__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:768 +msgid "With GDAL 3.1.x" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:770 +msgid "" +"The scripts in the ``__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:776 +msgid "" +"Create a PDF from 2 rasters (main_raster and another_raster), such that " +"main_raster is initially displayed, and they are exclusively displayed :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:786 +msgid "Create of PDF with some JavaScript :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:792 +msgid "where script.js is :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:802 +msgid ":ref:`PDF vector ` documentation page" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:804 +msgid "Specifications :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:806 +msgid "" +"`OGC GeoPDF Encoding Best Practice Version 2.2 (08-139r3) " +"`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:808 +msgid "" +"`Adobe Supplement to ISO 32000 " +"`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:810 +msgid "" +"`PDF Reference, version 1.7 " +"`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:812 +msgid "" +"`Acrobat(R) JavaScript Scripting Reference " +"`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:815 +msgid "Libraries :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:817 +msgid "`Poppler homepage `__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:818 +msgid "`PoDoFo homepage `__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:819 +msgid "`PDFium homepage `__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:820 +msgid "" +"`PDFium forked version for simpler builds " +"`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:823 +msgid "Samples :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:825 +msgid "" +"`A few Geospatial PDF samples `__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:827 +msgid "" +"`Tutorial to generate Geospatial PDF maps from OSM data " +"`__" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:5 +msgid "PDS -- Planetary Data System v3" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:7 ../../source/drivers/vector/pds.rst:6 +msgid "PDS" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:11 +msgid "" +"PDS is a format used primarily by NASA to store and distribute solar, " +"lunar and planetary imagery data. GDAL provides read-only access to PDS " +"formatted imagery data." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:15 +msgid "" +"PDS files often have the extension .img, sometimes with an associated " +".lbl (label) file. When a .lbl file exists it should be used as the " +"dataset name rather than the .img file." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:19 +msgid "" +"In addition to support for most PDS imagery configurations, this driver " +"also reads georeferencing and coordinate system information as well as " +"selected other header metadata." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:27 +msgid "" +"PDS3 datasets can incorporate a VICAR header. By default, GDAL will use " +"the PDS driver in that situation. Starting with GDAL 3.1, if the " +":config:`GDAL_TRY_PDS3_WITH_VICAR` configuration option is set to YES, " +"the dataset will be opened by the :ref:`VICAR ` driver." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:56 +msgid "" +"Due to ambiguities in the PDS specification, the georeferencing of some " +"products is subtly or grossly incorrect. There are configuration " +"variables which may be set for these products to correct the " +"interpretation of the georeferencing. Some details are available in " +"`ticket #5941 `__ and `ticket " +"#3940 `__." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:63 +msgid "" +"As a test, download both the label and image for the lunar `LOLA DEM " +"`__ (digital " +"elevation file) `LOLA PDS label `__" +" and `LOLA PDS v3 image `__." +" Using gdalinfo, the reported centered should be perfectly at 0.0, 0.0 " +"meters in Cartesian space without any configuration options." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:73 +msgid "$ gdalinfo ldem_4.lbl" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:75 +msgid "Example conversion to GeoTiff:" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:77 +msgid "$ gdal_translate ldem_4.lbl out_LOLA.tif" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:79 +#: ../../source/drivers/raster/pds.rst:106 +msgid "" +"Example conversion and applying offset and multiplier values as defined " +"in some PDS labels:" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:82 +msgid "$ gdal_translate -ot Float32 -unscale ldem_4.lbl out_LOLA_32bit.tif" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:86 +msgid "" +"To show an example to correct an offset issue we can use the `MOLA DEM " +"`__ from the " +"PDS. Download both the `MOLA PDS label `__" +" and `MOLA PDS v3 image `__." +" The MOLA labels currently contain a one pixel offset. To read this file " +"correctly, use GDAL with these options." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:95 +msgid "" +"$ gdalinfo --config PDS_SampleProjOffset_Shift -0.5 --config " +"PDS_LineProjOffset_Shift -0.5 megt90n000cb.lbl" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:98 +msgid "" +"Again with these optional parameters, the center should be perfectly 0.0," +" 0.0 meters in Cartesian space." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:101 +msgid "Example conversion for MOLA:" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:103 +msgid "" +"$ gdal_translate --config PDS_SampleProjOffset_Shift -0.5 --config " +"PDS_LineProjOffset_Shift -0.5 megt90n000cb.lbl out_MOLA_4ppd.tif" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:109 +msgid "" +"$ gdal_translate -ot Float32 -unscale --config PDS_SampleProjOffset_Shift" +" -0.5 --config PDS_LineProjOffset_Shift -0.5 megt90n000cb.lbl " +"out_MOLA_4ppd_32bit.tif" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:115 +msgid "PDS is part of a family of related formats including ISIS2 and ISIS3." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:121 +msgid "Implemented as :source_file:`frmts/pds/pdsdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:122 +msgid "`NASA Planetary Data System `__" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:123 +msgid ":ref:`raster.isis2` driver." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:124 +#: ../../source/drivers/raster/pds4.rst:555 +msgid ":ref:`raster.isis3` driver." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:5 +msgid "PDS4 -- NASA Planetary Data System (Version 4)" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:7 +msgid "PDS4" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:11 +msgid "" +"PDS4 is a format used primarily by NASA to store and distribute solar, " +"lunar and planetary imagery data. GDAL provides read-write access to PDS4" +" formatted imagery data." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:15 +msgid "" +"PDS4 files are compose of a .xml (label) file which references a raw " +"imagery file. The driver also supports imagery stored in a separate " +"uncompressed GeoTIFF file with a strip organization compatible of a raw " +"imagery file." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:20 +msgid "" +"The driver also reads and write georeferencing and coordinate system " +"information as well as selected other header metadata." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:23 +msgid "" +"A mask band is attached to each source band. The value of this mask band " +"is 0 when the pixel value is one of the missing constants." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:29 +msgid "PDS4 is part of a family of related formats including PDS and ISIS3." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:31 +msgid "" +"Starting with GDAL 2.5, the PDS4 driver supports reading and writing " +"ASCII fixed-with, binary fixed-with and delimited(CSV) tables as OGR " +"vector layers." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:49 +msgid "" +"The PDS4 label can be retrieved as XML-serialized content in the xml:PDS4" +" metadata domain." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:52 +msgid "" +"On creation, a source template label can be passed to the SetMetadata() " +"interface in the \"xml:PDS4\" metadata domain." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:56 +msgid "Open options (vector only)" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:60 +msgid "" +"|about-open-options| When opening a PDS4 vector dataset, the following " +"open options are available:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:93 +msgid "" +"The PDS4 driver supports updating imagery of existing datasets, creating " +"new datasets through the CreateCopy() and Create() interfaces." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:96 +msgid "" +"When using CreateCopy(), gdal_translate or gdalwarp, an effort is made to" +" preserve as much as possible of the original label when doing PDS4 to " +"PDS4 conversions. This can be disabled with the :co:`USE_SRC_LABEL=NO` " +"creation option." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:101 +msgid "" +"|about-creation-options| The following dataset creation options are " +"available:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:186 +msgid "" +"**VAR_\\***\\ =string. If options like VAR_XXXX=yyyy are specified, any " +"{XXXX} string in the template label will be replaced by the yyyy value." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:193 +msgid "" +"Template label to use. If not specified and not creating from an existing" +" PDS4 file, the data/pds4_template.xml file will be used. For GDAL " +"utilities to find this default PDS4 template, GDAL's data directory " +"should be defined in your environment (typically on Windows builds). " +"Consult the `wiki " +"`__" +" for more information." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:231 +msgid "Layer creation options (vector/table datasets)" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:233 +msgid "" +"|about-layer-creation-options| (Starting with GDAL 3.0) When creating a " +"PDS4 vector dataset, or appending a new table to an existing table, the " +"following layer creation options are available:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:316 +msgid "Subdataset / multiple image support" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:318 +msgid "" +"If several Array objects are present in the label, they will be reported " +"as separate subdatasets (typically the main subdataset is an Array3D, and" +" backplanes are represented as Array2D)." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:322 +msgid "" +"Since GDAL 3.0, creation of new datasets with subdatasets is supported " +"(through the :co:`APPEND_SUBDATASET=YES` creation option). One important " +"restriction is that, given that the georeferencing information in the " +"PDS4 XML label is global for the whole dataset, all subdatasets must " +"share the same georeferencing information: coordinate reference system, " +"georegistration and resolution. Appending to both RAW and GEOTIFF raster " +"is supported. In append mode, most creation options are ignored, except " +":co:`INTERLEAVE` (if GeoTIFF output image), :co:`ARRAY_TYPE` and " +":co:`ARRAY_IDENTIFIER`." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:333 +msgid "PDS4 raster examples" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:335 +msgid "Listing bands and subdatasets:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:383 +msgid "" +"The information displayed by default is the one of the first subdataset " +"(SUBDATASET_1_NAME)" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:386 +msgid "Getting information on a subdataset:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:406 +msgid "Conversion to GeoTIFF of a given subdatasets:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:412 +msgid "Conversion to GeoTIFF of a all subdatasets:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:418 +msgid "This will create b0011_p237201_01_01v02_X.tif files where X=1,....,N" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:420 +msgid "" +"Creation of a new PDS4 dataset, using the default template and setting " +"its parameterized variables:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:434 +msgid "" +"Creation of the same PDS4 dataset as above, using the default template " +"but setting its parameterized variables from a text file. Helps with long" +" command lines:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:438 +msgid "Create a text file \"myOptions.txt\" with the below content" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:457 +msgid "" +"For more on --optfile, consult `the general documentation on GDAL " +"utilities `__." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:460 +msgid "" +"Creation of a PDS4 dataset, using a non default template (here on a HTTP " +"server, but local filename also possible):" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:468 +msgid "" +"Creation of a PDS4 dataset from a source PDS4 dataset (using the XML file" +" of this source PDS4 dataset as an implicit template), with subsetting:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:476 +msgid "" +"In Python, creation of a PDS4 dataset from a GeoTIFF, using a base " +"template into which one substitute one element with a new value:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:502 +msgid "Appending a new image (subdataset) to an existing PDS4 dataset." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:511 +msgid "Adding a PDS4 label to an existing ISIS3 dataset. (GDAL >= 3.1)" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:518 +msgid "PDS4 vector examples" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:520 +msgid "Displaying the content of a PDS4 dataset with a table:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:526 +msgid "" +"Converting a PDS4 dataset with a table to shapefile, by specifying " +"columns that contain longitude and latitude:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:533 +msgid "" +"Converting a shapefile to a PDS4 dataset with a CSV-delimited table (with" +" an implicit WKT column to store the geometry):" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:541 +#: ../../source/drivers/vector/filegdb.rst:285 +#: ../../source/drivers/vector/gpkg.rst:55 +#: ../../source/drivers/vector/openfilegdb.rst:332 +#: ../../source/drivers/vector/xodr.rst:54 +msgid "Limitations" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:543 +msgid "" +"As a new driver and new format, please report any issues to the bug " +"tracker, as explained on the `wiki `__" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:549 +msgid "Implemented as :source_file:`frmts/pds/pds4dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:550 +msgid "`Official documentation `__" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:552 +msgid "" +"`Schemas, including the cartography extension " +"`__" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:554 +msgid ":ref:`raster.pds` driver." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:7 +msgid "PLMosaic" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:11 +msgid "" +"This driver can connect to Planet Labs Mosaics API. GDAL/OGR must be " +"built with Curl support in order for the PLMosaic driver to be compiled." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:14 +msgid "" +"The driver supports listing mosaics and reading them. Mosaics are " +"accessed at their highest resolution. Mosaics are typically composed of " +"quads of 4096x4096 pixels." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:18 +msgid "" +"For mosaics of type Byte, overviews are available by using the tile API. " +"For other data types, there is no support for overviews, so requests that" +" involve downsampling may take a long time to complete." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:36 +#: ../../source/drivers/vector/amigocloud.rst:36 +#: ../../source/drivers/vector/plscenes_data_v1.rst:27 +msgid "" +"Additional optional parameters can be specified after the ':' sign. " +"Currently the following one is supported :" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:39 +msgid "" +"**api_key**\\ =value: To specify the Planet API key. It is mandatory, " +"unless it is supplied through the open option API_KEY, or the " +"configuration option PL_API_KEY." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:42 +msgid "**mosaic**\\ =mosaic_name: To specify the mosaic name." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:43 +msgid "" +"**cache_path**\\ =path: To specify the path to a directory where cached " +"quads (and tiles) are stored. A plmosaic_cache/{mosaic_name} subdirectory" +" will be created under that path. The empty string can be used to disable" +" any disk caching." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:47 +msgid "" +"**trust_cache**\\ =YES/NO: Whether already cached quads should be reused " +"directly, without prior checking if the server has a more recent version." +" Note: this only applies to quads, and not tiles. Default is NO." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:51 +msgid "" +"**use_tiles**\\ =YES/NO: Whether to use the tile API to access full " +"resolution data, instead of downloading quads. Only apply for Byte " +"mosaics. Default is NO." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:55 +#: ../../source/drivers/vector/plscenes_data_v1.rst:51 +msgid "If several parameters are specified, they must be separated by a comma." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:57 +msgid "" +"If no mosaic parameter is supplied, the list of available mosaics will be" +" returned as subdatasets. If only one mosaic is available, it will be " +"directly opened." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:64 +msgid "" +"|about-open-options| The following open options are available : API_KEY, " +"MOSAIC, CACHE_PATH, TRUST_CACHE and USE_TILES. They have the same " +"semantics as the above-described parameters of same name." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:-1 +msgid "PL_API_KEY=value: To specify the Planet API key." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:79 +msgid "Location information" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:81 +msgid "" +"The special *Pixel_{x}_{y}* metadata item of the *LocationInfo* metadata " +"domain, where x is the column and y is the line in the mosaic, can be " +"queried to get information about the scenes that compose the underneath " +"quad. This is the syntax used by the gdallocationinfo utility (see " +":ref:`rfc-32`)" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:86 +msgid "Below an example of the return :" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:110 +msgid "Listing all mosaics available (with the rights of the account) :" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:128 +msgid "returns (in case of multiple mosaics):" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:149 +msgid "Open a particular mosaic :" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:155 +msgid "returns:" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:217 +msgid "" +"`Documentation of Planet Mosaics API `__" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:219 +msgid "" +"`API Authentication `__" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:221 +msgid ":ref:`Vector PLScenes / Planet Scenes API driver `" +msgstr "" + +#: ../../source/drivers/raster/png.rst:5 +msgid "PNG -- Portable Network Graphics" +msgstr "" + +#: ../../source/drivers/raster/png.rst:7 +msgid "PNG" +msgstr "" + +#: ../../source/drivers/raster/png.rst:-1 +#: ../../source/drivers/raster/sentinel2.rst:-1 +msgid "Driver built-in by default" +msgstr "" + +#: ../../source/drivers/raster/png.rst:9 +msgid "internal libpng provided" +msgstr "" + +#: ../../source/drivers/raster/png.rst:11 +msgid "" +"GDAL includes support for reading, and creating .png files. Greyscale, " +"pseudo-colored, Paletted, RGB and RGBA PNG files are supported as well as" +" precisions of eight and sixteen bits per sample." +msgstr "" + +#: ../../source/drivers/raster/png.rst:15 +msgid "" +"The GDAL PNG Driver is built using the libpng library. Also note that the" +" GeoTIFF driver supports tiled TIFF with DEFLATE compressed tiles, which " +"is the same compression algorithm that PNG at its core uses." +msgstr "" + +#: ../../source/drivers/raster/png.rst:19 +msgid "" +"PNG files are linearly compressed, so random reading of large PNG files " +"can be very inefficient (resulting in many restarts of decompression from" +" the start of the file). The maximum dimension of a PNG file that can be " +"created by GDAL is set to 1,000,000x1,000,000 pixels by libpng." +msgstr "" + +#: ../../source/drivers/raster/png.rst:24 +msgid "" +"Text chunks are translated into metadata, typically with multiple lines " +"per item. :ref:`raster.wld` with the extensions of .pgw, .pngw or .wld " +"will be read. Single transparency values in greyscale files will be " +"recognised as a nodata value in GDAL. Transparent index in paletted " +"images are preserved when the color table is read." +msgstr "" + +#: ../../source/drivers/raster/png.rst:30 +msgid "" +"PNG files can be created with a type of PNG, using the CreateCopy() " +"method, requiring a prototype to read from. Writing includes support for " +"the various image types, and will preserve transparency/nodata values. " +"Georeferencing .wld files are written if creation option :co:`WORLDFILE` " +"is set. All pixel types other than 16bit unsigned will be written as " +"eight bit." +msgstr "" + +#: ../../source/drivers/raster/png.rst:56 +msgid "" +"SOURCE_ICC_PROFILE_NAME : ICC profile name. sRGB is recognized as a " +"special value." +msgstr "" + +#: ../../source/drivers/raster/png.rst:62 +msgid "PNG_GAMMA" +msgstr "" + +#: ../../source/drivers/raster/png.rst:68 +msgid "" +"All these metadata tags can be used as creation options. |about-creation-" +"options| The following creation options are available:" +msgstr "" + +#: ../../source/drivers/raster/png.rst:116 +msgid "NOTE: Implemented as :source_file:`frmts/png/pngdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/png.rst:118 +msgid "" +"PNG support is implemented based on the libpng reference library. More " +"information is available at http://www.libpng.org/pub/png." +msgstr "" + +#: ../../source/drivers/raster/pnm.rst:5 +msgid "PNM -- Netpbm (.pgm, .ppm)" +msgstr "" + +#: ../../source/drivers/raster/pnm.rst:7 +msgid "PNM" +msgstr "" + +#: ../../source/drivers/raster/pnm.rst:11 +msgid "" +"GDAL includes support for reading, and creating .pgm (greyscale), and " +".ppm (RGB color) files compatible with the Netpbm tools. Only the binary " +"(raw) formats are supported." +msgstr "" + +#: ../../source/drivers/raster/pnm.rst:15 +msgid "Netpbm files can be created with a type of PNM." +msgstr "" + +#: ../../source/drivers/raster/pnm.rst:20 +msgid "|about-creation-options| The following creation option is available:" +msgstr "" + +#: ../../source/drivers/raster/pnm.rst:30 +msgid "NOTE: Implemented as :source_file:`frmts/raw/pnmdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:5 +msgid "PostGISRaster -- PostGIS Raster driver" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:7 +msgid "PostGISRaster" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:11 +msgid "" +"PostGIS Raster (previously known as WKT Raster) is the project that " +"provides raster support on PostGIS. Since September 26st, 2010, is an " +"official part of PostGIS 2.0+." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:15 +msgid "" +"This driver was started during the Google Summer of Code 2009, and " +"significantly improved since then." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:18 +msgid "" +"Currently, the driver provides read-only support to PostGIS Raster data " +"sources." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:29 +#: ../../source/drivers/vector/hana.rst:21 +#: ../../source/drivers/vector/mssqlspatial.rst:22 +#: ../../source/drivers/vector/pg.rst:32 +msgid "Connecting to a database" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:31 +msgid "" +"To connect to a PostGIS Raster datasource, use a connection string " +"specifying the database name, with additional parameters as necessary" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:38 +msgid "" +"Note that the string, up to the part starting with \"table='\" is a " +"libpq-style connection string. That means that you can leave out " +"unnecessary fields (like password, in some cases)." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:42 +msgid "" +"**schema** - name of PostgreSQL schema where requested raster table is " +"stored." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:44 +msgid "" +"**table** - name of PostGIS Raster table. The table was created by the " +"raster loader (eg. raster2pgsql utility)." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:46 +msgid "**column** - name of raster column in raster table" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:47 +msgid "" +"**where** - option is used to filter the results of the raster table. Any" +" SQL-WHERE expression is valid." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:49 +msgid "" +"**mode** - option is used to know the expected arrangement of the raster " +"table. There are 2 possible values" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:52 +msgid "" +"**mode=1** - ONE_RASTER_PER_ROW mode. In this case, a raster table is " +"considered as a bunch of different raster files. This mode is intended " +"for raster tables storing different raster files. It's the default mode " +"if you don't provide this field in connection string." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:57 +msgid "" +"**mode=2** - ONE_RASTER_PER_TABLE mode. In this case, a raster table is " +"considered as a unique raster file, even if the table has more than one " +"row. This mode is intended for reading tiled rasters from database." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:62 +msgid "" +"**outdb_resolution** - (GDAL >= 2.3.1) option to specify how out-database" +" rasters should be resolved. Default is server_side." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:65 +msgid "" +"**server_side**: The outDB raster will be fetched by the PostgreSQL " +"server. This implies that outdb rasters are enabled on the server." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:68 +msgid "" +"**client_side**: The outDB raster filenames will be returned to the GDAL " +"PostGISRaster client, which will open it on the client side. This implies" +" that the filename stored on te server can be accessed by the client." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:72 +msgid "" +"**client_side_if_possible**: The outDB raster filenames will be returned " +"to the GDAL PostGISRaster client, which will check if it can access them." +" If it can, that's equivalent to client_side. Otherwise that's equivalent" +" to server_side. Note that this mode involves extra queries to the " +"server." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:79 +msgid "Additional notes" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:81 +msgid "" +"If a table stores a tiled raster and you execute the driver with mode=1, " +"each image tile will be considered as a different image, and will be " +"reported as a subdataset. There are use cases the driver can't still work" +" with. For example: non-regular blocked rasters. That cases are detected " +"and an error is raised. Anyway, as I've said, the driver is under " +"development, and will work with more raster arrangements ASAP." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:88 +msgid "" +"There's an additional working mode. If you don't provide a table name, " +"the driver will look for existing raster tables in all allowed database' " +"schemas, and will report each table as a subdataset." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:92 +msgid "" +"You must use this connection string's format in all the gdal tools, like " +"gdalinfo, gdal_translate, gdalwarp, etc." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:96 +#: ../../source/drivers/raster/rasterlite.rst:165 +#: ../../source/drivers/vector/gpkg.rst:757 +#: ../../source/drivers/vector/sqlite.rst:507 +msgid "Performance hints" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:98 +msgid "" +"To get the maximum performance from the driver, it is best to load the " +"raster in PostGIS raster with the following characteristics:" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:101 +msgid "tiled: -t switch of raster2pgsql" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:102 +msgid "with overview: -l 2,4,8,... switch of raster2pgsql" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:103 +msgid "with a GIST spatial index on the raster column: -I switch of raster2pgsql" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:105 +msgid "with constraints registered: -C switch of raster2pgsql" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:110 +msgid "To get a summary about your raster via GDAL use gdalinfo:" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:116 +msgid "" +"For more examples, check the PostGIS Raster FAQ section: `Can I export my" +" PostGIS Raster data to other raster formats? " +"`__" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:123 +msgid "The driver developers" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:125 +msgid "Jorge Arévalo (jorgearevalo at libregis.org)" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:126 +msgid "David Zwarg (dzwarg at azavea.com)" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:127 +msgid "Even Rouault (even.rouault at spatialys.com)" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:132 +msgid "" +"`GDAL PostGISRaster driver Wiki " +"`__" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:134 +msgid "" +"`PostGIS Raster documentation " +"`__" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:7 +msgid "PRF" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:11 +msgid "" +"PRF or MegaTIFF is an internal format of PHOTOMOD software for storing " +"large images." +msgstr "" + +#: ../../source/drivers/raster/prf.rst:14 +msgid "" +"This format was developed to store images larger than 4 GB. As a basis " +"for storing data used TIFF or JPEG2000 format. Raster is split into " +"fragments (tiles) such that each fragment does not exceeded a predefined " +"size (e.g., less than 1 GB). An overview file also added to process " +"raster data on a small scales." +msgstr "" + +#: ../../source/drivers/raster/prf.rst:20 +msgid "" +"PRF files has two variations: 'prf' for imagery data and 'x-dem' for " +"elevation data. Files can be georeferenced, but projection information " +"can be stored only in external files (\\*.prj)." +msgstr "" + +#: ../../source/drivers/raster/prf.rst:24 +msgid "Image format has the following structure:" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:26 +msgid "the header XML file 'image_name.prf'/'image_name.x-dem'" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:27 +msgid "folder 'image_name' with raster subtiles" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:28 +msgid "" +"files \\*.tif/*.jp2/*.demtif inside folder 'image_name', containing " +"raster fragments and the overview image" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:31 +msgid "" +"The driver support the data type among Byte, UInt16, UInt32, Float32 or " +"Float64." +msgstr "" + +#: ../../source/drivers/raster/prf.rst:42 +msgid "`Racurs company home page `__" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:43 +msgid "`PHOTOMOD Lite home page `__" +msgstr "" + +#: ../../source/drivers/raster/r.rst:5 +msgid "R -- R Object Data Store" +msgstr "" + +#: ../../source/drivers/raster/r.rst:7 +msgid "R" +msgstr "" + +#: ../../source/drivers/raster/r.rst:11 +msgid "" +"The R Object File Format is supported for write access, and limited read " +"access by GDAL. This format is the native format R uses for objects saved" +" with the *save* command and loaded with the *load* command. GDAL " +"supports writing a dataset as an array object in this format, and " +"supports reading files with simple rasters in essentially the same " +"organization. It will not read most R object files." +msgstr "" + +#: ../../source/drivers/raster/r.rst:18 +msgid "" +"Currently there is no support for reading or writing georeferencing " +"information." +msgstr "" + +#: ../../source/drivers/raster/r.rst:50 +msgid "`R Project `__" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:5 +msgid "Rasterlite - Rasters in SQLite DB" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:7 +msgid "Rasterlite" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:11 +msgid "The Rasterlite driver allows reading and creating Rasterlite databases." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:16 +msgid "" +"Those databases can be produced by the utilities of the `rasterlite " +"`__ distribution, such as " +"rasterlite_load, rasterlite_pyramids, ...." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:19 +msgid "" +"The driver supports reading grayscale, paletted and RGB images stored as " +"GIF, PNG, TIFF or JPEG tiles. The driver also supports reading " +"overviews/pyramids, spatial reference system and spatial extent." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:21 +msgid "" +"GDAL/OGR must be compiled with OGR SQLite driver support. For read " +"support, linking against spatialite library is not required, but recent " +"enough sqlite3 library is needed to read rasterlite databases. rasterlite" +" library is not required either." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:26 +msgid "" +"For write support a new table, linking against spatialite library " +"\\*is\\* required." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:29 +msgid "" +"Although the Rasterlite documentation only mentions GIF, PNG, TIFF, JPEG " +"as compression formats for tiles, the driver supports reading and writing" +" internal tiles in any format handled by GDAL. Furthermore, the " +"Rasterlite driver also allow reading and writing as many bands and as " +"many band types as supported by the driver for the internal tiles." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:46 +msgid "Connection string syntax in read mode" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:48 +msgid "" +"Syntax: 'rasterlitedb_name' or " +"'RASTERLITE:rasterlitedb_name[,table=raster_table_prefix][,minx=minx_val,miny=miny_val,maxx=maxx_val,maxy=maxy_val][,level=level_number]" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:51 +#: ../../source/drivers/vector/sqlite.rst:167 +msgid "where :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:53 +msgid "*rasterlitedb_name* is the filename of the RasterLite DB." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:54 +msgid "" +"*raster_table_prefix* is the prefix of the raster table to open. For each" +" raster, there are 2 corresponding SQLite tables, suffixed with " +"\\_rasters and \\_metadata" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:57 +msgid "" +"*minx_val,miny_val,maxx_val,maxy_val* set a user-defined extent " +"(expressed in coordinate system units) for the raster that can be " +"different from the default extent." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:60 +msgid "" +"*level_number* is the level of the pyramid/overview to open, 0 being the " +"base pyramid." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:66 +msgid "" +"The driver can create a new database if necessary, create a new raster " +"table if necessary and copy a source dataset into the specified raster " +"table." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:70 +msgid "" +"If data already exists in the raster table, the new data will be added. " +"You can use the WIPE=YES creation options to erase existing data." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:73 +msgid "" +"The driver does not support updating a block in an existing raster table." +" It can only append new data." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:76 +msgid "" +"Syntax for the name of the output dataset: " +"'RASTERLITE:rasterlitedb_name,table=raster_table_prefix' or " +"'rasterlitedb_name'" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:80 +msgid "" +"It is possible to specify only the DB name as in the later form, but only" +" if the database does not already exists. In that case, the raster table " +"name will be base on the DB name itself." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:139 +msgid "|about-config-options| The following configuration option is supported:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:150 +msgid "" +"The driver supports building (if the dataset is opened in update mode) " +"and reading internal overviews." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:153 +msgid "" +"If no internal overview is detected, the driver will try using external " +"overviews (.ovr files)." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:156 +msgid "" +"Options can be used for internal overviews building. They can be " +"specified with the :config:`RASTERLITE_OVR_OPTIONS` configuration option," +" as a comma separated list of the above creation options. See below " +"examples." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:161 +msgid "All resampling methods supported by GDAL overviews are available." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:167 +msgid "" +"Some of the performance hints of the OGR SQLite driver apply. In " +"particular setting the OGR_SQLITE_SYNCHRONOUS configuration option to OFF" +" when creating a dataset or adding overviews might increase performance " +"on some filesystems." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:172 +msgid "" +"After having added all the raster tables and building all the needed " +"overview levels, it is advised to run :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:179 +msgid "" +"in order to optimize the database, and increase read performances " +"afterwards. This is particularly true with big rasterlite datasets. Note " +"that the operation might take a long time." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:186 +msgid "Accessing a rasterlite DB with a single raster table :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:225 +msgid "Listing a multi-raster table DB :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:251 +msgid "Accessing a raster table within a multi-raster table DB:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:257 +msgid "Creating a new rasterlite DB with data encoded in JPEG tiles :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:263 +msgid "Creating internal overviews :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:269 +msgid "Cleaning internal overviews :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:275 +msgid "Creating external overviews in a .ovr file:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:281 +msgid "Creating internal overviews with options (GDAL 1.10 or later):" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:287 +msgid ":" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:292 +msgid "" +"`Spatialite and Rasterlite home page `__" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:294 +msgid "" +"`Rasterlite manual `__" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:296 +msgid "" +"`Rasterlite howto `__" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:298 +msgid "" +"`Sample databases `__" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:300 +#: ../../source/drivers/raster/rasterlite2.rst:196 +msgid ":ref:`OGR SQLite driver `" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:5 +msgid "RasterLite2 - Rasters in SQLite DB" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:9 +#: ../../source/drivers/vector/sqlite.rst:6 +msgid "SQLite" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:11 +msgid "" +"The above short name is not a typo. The RasterLite2 functionality is part" +" of the :ref:`vector.sqlite` driver." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:16 +msgid "" +"The SQLite driver allows reading and writing SQLite databases containing " +"RasterLite2 coverages." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:21 +msgid "" +"Those databases can be produced by the utilities of the `RasterLite2 " +"`__ distribution, such as " +"rl2tools." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:25 +msgid "" +"The driver supports reading grayscale, paletted, RGB, multispectral " +"images stored as tiles in the many compressed formats supported by " +"libRasterLite2. The driver also supports reading overviews/pyramids, " +"spatial reference system and spatial extent." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:27 +msgid "" +"GDAL/OGR must be compiled with sqlite support and against librasterlite2 " +"and libspatialite." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:30 +msgid "" +"The driver is implemented a unified SQLite / SpatiaLite / RasterLite2 " +"vector and raster capable driver." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:43 +#: ../../source/drivers/vector/gmlas.rst:34 +msgid "Opening syntax" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:45 +msgid "" +"A RasterLite2 filename can be specified as the connection string. If the " +"file contains a single RasterLite2 coverage, this one will be exposed as " +"the GDAL dataset. If the file contains multiple coverages, each one will " +"be exposed as a subdataset with the syntax " +"RASTERLITE2:filename:coverage_name. See `the basic concepts of " +"RasterLite2 `__." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:52 +msgid "" +"If a coverage is made of several sections, they will be listed as " +"subdatasets of the coverage dataset, so as to be accessed individually. " +"By default, they will be exposed as a unified dataset. The syntax of " +"section-based dataset is " +"RASTERLITE2:filename:coverage_name:section_id:section_name." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:59 +#: ../../source/drivers/vector/driver_summary.rst:13 +msgid "Creation" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:61 +msgid "" +"The driver supports creating new databases from scratch, adding new " +"coverages to an existing database and adding sections to an existing " +"coverage." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:146 +msgid "Reading a RasterLite2 database with a single coverage:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:152 +msgid "" +"Listing the subdatasets corresponding to the coverages of a RasterLite2 " +"database with several coverages:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:159 +msgid "Reading a subdataset corresponding to a coverage:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:165 +msgid "Creating a RasterLite2 dataset from a grayscale image:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:171 +msgid "" +"Creating a RasterLite2 dataset from a RGB image, and using JPEG " +"compression:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:178 +msgid "" +"Adding a RasterLite2 coverage to an existing SpatiaLite/RasterLite2 " +"database:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:185 +msgid "Adding pyramids to a coverage:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:194 +msgid "" +"`Rasterlite2 home page `__" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:5 +msgid "RDB - *RIEGL* Database" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:7 +msgid "RDB" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:13 +msgid "" +"GDAL can read \\*.mpx files in the RDB format, the in-house format used " +"by `RIEGL Laser Measurement Systems GmbH `__ " +"through the RDB library." +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:15 +msgid "" +"The driver relies on the RDB library, which can be downloaded `here " +"`__ . The minimum" +" version required of the rdblib is 2.2.0." +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:23 +msgid "Provided Bands" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:25 +msgid "" +"All attributes stored in the RDB, but the coordinates, are provided in " +"bands. Vector attributes are split up into multiple bands. The attributes" +" are currently mapped as follows:" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:29 +msgid "RDB attribute" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:29 +msgid "GDAL Band" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:31 +msgid "riegl.surface_normal[0]," +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:33 +msgid "riegl.surface_normal[1]," +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:35 +msgid "riegl.surface_normal[2]" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:31 +msgid "Band 1" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:33 +msgid "Band 2" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:35 +msgid "Band 3" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:37 +msgid "riegl.timestamp_min" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:37 +msgid "Band 4" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:39 +msgid "riegl.timestamp_max" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:39 +msgid "Band 5" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:41 +msgid "riegl.reflectance" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:41 +msgid "Band 6" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:43 +msgid "riegl.amplitude" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:43 +msgid "Band 7" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:45 +msgid "riegl.deviation" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:45 +msgid "Band 8" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:47 +msgid "riegl.height_center" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:47 +msgid "Band 9" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:49 +msgid "riegl.height_mean" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:49 +msgid "Band 10" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:51 +msgid "riegl.height_min" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:51 +msgid "Band 11" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:53 +msgid "riegl.height_max" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:53 +msgid "Band 12" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:55 +msgid "riegl.point_count" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:55 +msgid "Band 13" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:57 +msgid "riegl.point_count_grid_cell" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:57 +msgid "Band 14" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:59 +msgid "riegl.pca_thickness" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:59 +msgid "Band 15" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:61 +msgid "riegl.std_dev" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:61 +msgid "Band 16" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:63 +msgid "riegl.voxel_count" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:63 +msgid "Band 17" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:65 +msgid "riegl.id" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:65 +msgid "Band 18" +msgstr "" + +#: ../../source/drivers/raster/rik.rst:5 +msgid "RIK -- Swedish Grid Maps" +msgstr "" + +#: ../../source/drivers/raster/rik.rst:7 +msgid "RIK" +msgstr "" + +#: ../../source/drivers/raster/rik.rst:11 +msgid "" +"Supported by GDAL for read access. This format is used in maps issued by " +"the swedish organization Lantmäteriet. Supports versions 1, 2 and 3 of " +"the RIK format, but only 8 bits per pixel." +msgstr "" + +#: ../../source/drivers/raster/rik.rst:15 +msgid "" +"This driver is based on the work done in the `TRikPanel " +"`__ project." +msgstr "" + +#: ../../source/drivers/raster/rik.rst:18 +msgid "NOTE: Implemented as :source_file:`frmts/rik/rikdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:5 +msgid "RMF -- Raster Matrix Format" +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:7 +msgid "RMF" +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:11 +msgid "" +"RMF is a simple tiled raster format used in the GIS \"Integration\" and " +"\"Panorama\" GIS. The format itself has very poor capabilities." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:14 +msgid "" +"There are two flavors of RMF called MTW and RSW. MTW supports 16-bit " +"integer and 32/64-bit floating point data in a single channel and aimed " +"to store DEM data. RSW is a general purpose raster. It supports single " +"channel colormapped or three channel RGB images. Only 8-bit data can be " +"stored in RSW. Simple georeferencing can be provided for both image " +"types." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:35 +msgid "**ELEVATION_MINIMUM**: Minimum elevation value (MTW only)." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:36 +msgid "**ELEVATION_MAXIMUM**: Maximum elevation value (MTW only)." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:37 +msgid "" +"**ELEVATION_UNITS**: Name of the units for raster values (MTW only). Can " +"be \"m\" (meters), \"cm\" (centimeters), \"dm\" (decimeters), \"mm\" " +"(millimeters)." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:40 +msgid "" +"**ELEVATION_TYPE**: Could be either 0 (absolute elevation) or 1 (total " +"elevation). MTW only." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:114 +msgid "Implemented as :source_file:`frmts/rmf/rmfdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:115 +msgid "`\"Panorama\" GIS homepage `__" +msgstr "" + +#: ../../source/drivers/raster/roi_pac.rst:5 +msgid "ROI_PAC -- ROI_PAC" +msgstr "" + +#: ../../source/drivers/raster/roi_pac.rst:11 +msgid "" +"Driver for the image formats used in the JPL's ROI_PAC project " +"(https://aws.roipac.org/). All image type are supported excepted .raw " +"images." +msgstr "" + +#: ../../source/drivers/raster/roi_pac.rst:15 +msgid "Metadata are stored in the ROI_PAC domain." +msgstr "" + +#: ../../source/drivers/raster/roi_pac.rst:17 +msgid "" +"Georeferencing is supported, but expect problems when using the UTM " +"projection, as ROI_PAC format do not store any hemisphere field." +msgstr "" + +#: ../../source/drivers/raster/roi_pac.rst:20 +msgid "" +"When creating files, you have to be able to specify the right data type " +"corresponding to the file type (slc, int, etc), else the driver will " +"output an error." +msgstr "" + +#: ../../source/drivers/raster/roi_pac.rst:24 +msgid "NOTE: Implemented as :source_file:`frmts/raw/roipacdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:5 +msgid "RPFTOC -- Raster Product Format/RPF (a.toc)" +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:7 +msgid "RPFTOC" +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:11 +msgid "" +"This is a read-only reader for RPF products, like CADRG or CIB, that uses" +" the table of content file - A.TOC - from a RPF exchange, and exposes it " +"as a virtual dataset whose coverage is the set of frames contained in the" +" table of content." +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:16 +msgid "" +"The driver will report a different subdataset for each subdataset found " +"in the A.TOC file." +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:19 +msgid "Result of a gdalinfo on a A.TOC file." +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:35 +msgid "" +"In some situations, :ref:`raster.nitf` tiles inside a subdataset don't " +"share the same palettes. The RPFTOC driver will do its best to remap " +"palettes to the reported palette by gdalinfo (which is the palette of the" +" first tile of the subdataset). In situations where it would not give a " +"good result, you can try to set the RPFTOC_FORCE_RGBA environment " +"variable to TRUE before opening the subdataset. This will cause the " +"driver to expose the subdataset as a RGBA dataset, instead of a paletted " +"one." +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:44 +msgid "" +"It is possible to build external overviews for a subdataset. The overview" +" for the first subdataset will be named A.TOC.1.ovr for example, for the " +"second dataset it will be A.TOC.2.ovr, etc. Note that you must re-open " +"the subdataset with the same setting of RPFTOC_FORCE_RGBA as the one you " +"have used when you have created it. Do not use any method other than " +"NEAREST resampling when building overviews on a paletted subdataset " +"(RPFTOC_FORCE_RGBA unset)" +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:52 +msgid "" +"A gdalinfo on one of this subdataset will return the various NITF " +"metadata, as well as the list of the NITF tiles of the subdataset." +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:60 +msgid "NOTE: Implemented as :source_file:`frmts/nitf/rpftocdataset.cpp`" +msgstr "" + +#: ../../source/drivers/raster/rraster.rst:5 +msgid "RRASTER -- R Raster" +msgstr "" + +#: ../../source/drivers/raster/rraster.rst:7 +msgid "RRASTER" +msgstr "" + +#: ../../source/drivers/raster/rraster.rst:13 +msgid "" +"This is a read-only reader for the datasets handled by the `R Raster " +"package `__. " +"Those datasets are made of a .grd file, which is a text header file, and " +"a .gri binary file containing the raster data itself. The .grd is the " +"file opened by GDAL. Starting with GDAL 2.3, the driver will read " +"ratvalues as RAT or color tables. Layer names will be assigned to GDAL " +"band description. The 'creator' and 'created' attributes of the " +"'[general]' section will be assigned to the GDAL 'CREATOR' and 'CREATED' " +"dataset metadata items." +msgstr "" + +#: ../../source/drivers/raster/rraster.rst:23 +msgid "" +"Starting with GDAL 2.3, the driver has write capabilities. Color tables " +"or RAT will be written. The 'CREATOR' and 'CREATED' dataset metadata " +"items will be written as the 'creator' and 'created' attributes of the " +"'[general]' section. Band description will be written as the 'layername' " +"attribute of the '[description]' section." +msgstr "" + +#: ../../source/drivers/raster/rraster.rst:64 +msgid "" +"Description of the `\"rasterfile\" format " +"`__" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:5 +msgid "RS2 -- RadarSat 2 XML Product" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:7 +msgid "RS2" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:11 +msgid "" +"This driver will read some RadarSat 2 XML polarimetric products. In " +"particular complex products, and 16bit magnitude detected products." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:14 +msgid "" +"The RadarSat 2 XML products are distributed with a primary XML file " +"called product.xml, and a set of supporting XML data files with the " +"actual imagery stored in TIFF files. The RS2 driver will be used if the " +"product.xml or the containing directory is selected, and it can treat all" +" the imagery as one consistent dataset." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:20 +msgid "" +"The complex products use \"32bit void typed\" TIFF files which are not " +"meaningfully readable normally. The RS2 driver takes care of converting " +"this into useful CInt16 format internally." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:24 +msgid "" +"The RS2 driver also reads geolocation tiepoints from the product.xml file" +" and represents them as GCPs on the dataset." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:27 +msgid "" +"It is very likely that RadarSat International will be distributing other " +"sorts of datasets in this format; however, at this time this driver only " +"supports specific RadarSat 2 polarimetric products. All other will be " +"ignored, or result in various runtime errors. It is hoped that this " +"driver can be generalized when other product samples become available." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:41 +#: ../../source/drivers/raster/safe.rst:141 +msgid "Data Calibration" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:43 +msgid "" +"If you wish to have GDAL apply a particular calibration LUT to the data " +"when you open it, you have to open the appropriate subdatasets. The " +"following subdatasets exist within the SUBDATASET domain for RS2 " +"products:" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:48 +msgid "uncalibrated - open with RADARSAT_2_CALIB:UNCALIB: prepended to filename" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:50 +msgid "beta\\ :sub:`0` - open with RADARSAT_2_CALIB:BETA0: prepended to filename" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:52 +msgid "" +"sigma\\ :sub:`0` - open with RADARSAT_2_CALIB:SIGMA0: prepended to " +"filename" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:54 +msgid "gamma - open with RADARSAT_2_CALIB:GAMMA: prepended to filename" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:56 +msgid "" +"Note that geocoded (SPG/SSG) products do not have this functionality " +"available. Also be aware that the LUTs must be in the product directory " +"where specified in the product.xml, otherwise loading the product with " +"the calibration LUT applied will fail." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:61 +msgid "" +"One caveat worth noting is that the RADARSAT-2 driver will supply the " +"calibrated data as GDT_Float32 or GDT_CFloat32 depending on the type of " +"calibration selected. The uncalibrated data is provided as " +"GDT_Int16/GDT_Byte/GDT_CInt16, also depending on the type of product " +"selected." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:70 +msgid "RadarSat document RN-RP-51-27." +msgstr "" + +#: ../../source/drivers/raster/s102.rst:5 +msgid "S102 -- S-102 Bathymetric Surface Product" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:7 +msgid "S102" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:13 +msgid "" +"This driver provides read-only support for bathymetry data in the S-102 " +"format, which is a specific product profile in an HDF5 file" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:16 +msgid "" +"S-102 files have two image bands representing depth (band 1), uncertainty" +" (band 2) values for each cell in a raster grid area." +msgstr "" + +#: ../../source/drivers/raster/s102.rst:19 +msgid "" +"Note that positive values of depth mean values *below* the reference " +"surface of the vertical datum. The :oo:`DEPTH_OR_ELEVATION` open option " +"can be set to ``ELEVATION`` to expose depth values as elevation values, " +"by negating their sign (i.e. positive values of elevation mean values " +"above the reference surface)" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:24 +#: ../../source/drivers/raster/s104.rst:25 +#: ../../source/drivers/raster/s111.rst:29 +msgid "Georeferencing is reported." +msgstr "" + +#: ../../source/drivers/raster/s102.rst:57 +msgid "" +"This is the default behavior of most GDAL formats, but the native " +"organization of the data in S-102 products is to have the first line of " +"the grid being the southern-most one. This native organization can be " +"exposed by the driver by setting this option to NO (in which case the 6th" +" term of the geotransform matrix will be positive)" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:66 +msgid "Starting with GDAL 3.9, GDAL can handle QualityOfSurvey spatial metadata." +msgstr "" + +#: ../../source/drivers/raster/s102.rst:68 +msgid "" +"When such spatial metadata is present, the subdataset list will include a" +" name of the form ``S102:\"{filename}\":QualityOfSurvey``" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:71 +msgid "" +"The ``/QualityOfSurvey/featureAttributeTable`` dataset is exposed as a " +"GDAL Raster Attribute Table associated to the GDAL raster band. The pixel" +" values of the raster match the ``id`` column of the Raster Attribute " +"Table." +msgstr "" + +#: ../../source/drivers/raster/s102.rst:78 +msgid "Implemented as :source_file:`frmts/hdf5/s102dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/s102.rst:79 +msgid "" +"`S-102 Bathymetric Surface Product Specification " +"`__" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:80 +#: ../../source/drivers/raster/s104.rst:59 +#: ../../source/drivers/raster/s111.rst:63 +msgid ":ref:`BAG driver `" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:81 +#: ../../source/drivers/raster/s111.rst:65 +msgid ":ref:`S-104 driver `" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:82 +#: ../../source/drivers/raster/s104.rst:61 +msgid ":ref:`S-111 driver `" +msgstr "" + +#: ../../source/drivers/raster/s104.rst:5 +msgid "S104 -- S-104 Water Level Information for Surface Navigation Product" +msgstr "" + +#: ../../source/drivers/raster/s104.rst:7 +msgid "S104" +msgstr "" + +#: ../../source/drivers/raster/s104.rst:13 +msgid "" +"This driver provides read-only support for water level data in the S-104 " +"format, which is a specific product profile in an HDF5 file." +msgstr "" + +#: ../../source/drivers/raster/s104.rst:16 +msgid "" +"S-104 files have two image bands representing water level height (band 1)" +" and water level trend (band 2) values for each cell in a raster grid " +"area." +msgstr "" + +#: ../../source/drivers/raster/s104.rst:19 +msgid "" +"When opening a S-104 file, no raster band is directly available. But a " +"list of subdatasets will be reported, one for each timestamp available in" +" the file." +msgstr "" + +#: ../../source/drivers/raster/s104.rst:22 +msgid "" +"An actual dataset can be opened through such a subdataset, with a syntax " +"like ``S104:\"filename.h5\":Group_001``." +msgstr "" + +#: ../../source/drivers/raster/s104.rst:27 +msgid "" +"Note that the driver currently only supports regularly gridded S104 " +"datasets." +msgstr "" + +#: ../../source/drivers/raster/s104.rst:48 +msgid "" +"This is the default behavior of most GDAL formats, but the native " +"organization of the data in S-104 products is to have the first line of " +"the grid being the southern-most one. This native organization can be " +"exposed by the driver by setting this option to NO (in which case the 6th" +" term of the geotransform matrix will be positive)" +msgstr "" + +#: ../../source/drivers/raster/s104.rst:57 +msgid "Implemented as :source_file:`frmts/hdf5/s104dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/s104.rst:58 +msgid "" +"`S-104 Bathymetric Surface Product Specification " +"`__" +msgstr "" + +#: ../../source/drivers/raster/s111.rst:5 +msgid "S111 -- S-111 Surface Currents Product" +msgstr "" + +#: ../../source/drivers/raster/s111.rst:7 +msgid "S111" +msgstr "" + +#: ../../source/drivers/raster/s111.rst:13 +msgid "" +"This driver provides read-only support for surface currents in the S-111 " +"format, which is a specific product profile in an HDF5 file." +msgstr "" + +#: ../../source/drivers/raster/s111.rst:16 +msgid "" +"S-111 files have two image bands representing the following values for " +"each cell in a raster grid area:" +msgstr "" + +#: ../../source/drivers/raster/s111.rst:19 +msgid "surface current speed (band 1), in knots" +msgstr "" + +#: ../../source/drivers/raster/s111.rst:20 +msgid "" +"surface current direction (band 2), in degree measured from true north " +"clock-wise." +msgstr "" + +#: ../../source/drivers/raster/s111.rst:23 +msgid "" +"When opening a S-111 file, no raster band is directly available. But a " +"list of subdatasets will be reported, one for each timestamp available in" +" the file." +msgstr "" + +#: ../../source/drivers/raster/s111.rst:26 +msgid "" +"An actual dataset can be opened through such a subdataset, with a syntax " +"like ``S111:\"filename.h5\":Group_001``." +msgstr "" + +#: ../../source/drivers/raster/s111.rst:31 +msgid "" +"Note that the driver currently only supports regularly gridded S111 " +"datasets." +msgstr "" + +#: ../../source/drivers/raster/s111.rst:52 +msgid "" +"This is the default behavior of most GDAL formats, but the native " +"organization of the data in S-111 products is to have the first line of " +"the grid being the southern-most one. This native organization can be " +"exposed by the driver by setting this option to NO (in which case the 6th" +" term of the geotransform matrix will be positive)" +msgstr "" + +#: ../../source/drivers/raster/s111.rst:61 +msgid "Implemented as :source_file:`frmts/hdf5/s111dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/s111.rst:62 +msgid "" +"`S-111 Bathymetric Surface Product Specification " +"`__" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:5 +msgid "SAFE -- Sentinel-1 SAFE XML Product" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:7 +msgid "SAFE" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:11 +msgid "" +"Driver for Sentinel products. Currently supports only Sentinel-1 SAR " +"products. See also the :ref:`GDAL Sentinel-2 driver `" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:14 +msgid "" +"SENTINEL data products are distributed using a SENTINEL-specific " +"variation of the Standard Archive Format for Europe (SAFE) format " +"specification. The SAFE format has been designed to act as a common " +"format for archiving and conveying data within ESA Earth Observation " +"archiving facilities." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:20 +msgid "" +"The SAFE driver will be used if the manifest.safe or the containing " +"directory is selected, and it can treat all the imagery as one consistent" +" dataset." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:24 +msgid "" +"The SAFE driver also reads geolocation grid points from the metadata and " +"represents them as GCPs on the dataset." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:27 +msgid "" +"ESA will be distributing other satellite datasets in this format; " +"however, at this time this driver only supports specific Sentinel-1 SAR " +"products. All other will be ignored, or result in various runtime errors." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:40 +msgid "Multiple measurements" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:42 +msgid "" +"If the product contains multiple measurements (for example multiple " +"polarizations), each one is available as a raster band - if the swath is " +"the same. When the swath is the same, the geographic area is the same." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:46 +msgid "" +"If the product contains multiple swaths and multiple polatizations, the " +"driver shows the first swath by default. To access other swaths, the user" +" must select a specific subdataset." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:50 +msgid "" +"The syntax of subdataset naming and their content has been significantly " +"change in GDAL 3.4." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:56 +msgid "Opening the Sentinel-1 product:" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:121 +msgid "It's not mandatory to open manifest.safe, just pass the folder name:" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:127 +msgid "Opening a single measurement (for example IW/VH):" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:134 +msgid "or starting with GDAL 3.4" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:143 +msgid "" +"Starting with GDAL 3.4, calibration is applied for SIGMA0, BETA0 and " +"GAMMA calibration subdataset" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:148 +msgid "" +"`SAR Formats (ESA Sentinel Online) `__" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:150 +msgid "" +"`SAFE Specification (ESA Sentinel Online) " +"`__" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:152 +msgid ":ref:`GDAL Sentinel-2 driver `" +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:5 +msgid "SAR_CEOS -- CEOS SAR Image" +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:7 +msgid "SAR_CEOS" +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:11 +msgid "" +"This is a read-only reader for CEOS SAR image files. To use, select the " +"main imagery file." +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:14 +msgid "" +"This driver works with most Radarsat, JERS-1 and ERS data products, " +"including single look complex products; however, it is unlikely to work " +"for non-Radar CEOS products. The simpler :ref:`raster.ceos` driver is " +"often appropriate for these." +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:19 +msgid "" +"This driver will attempt to read 15 lat/long GCPS by sampling the per-" +"scanline CEOS superstructure information. In the case of products from " +"the Alaska Satellite Facility, it will obtain corner coordinates from " +"either the map projection record in the case of ScanSAR products, or the " +"facility data record for non-ScanSAR products. It also captures various " +"pieces of metadata from various header files, including:" +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:40 +msgid "" +"The SAR_CEOS driver also includes some support for SIR-C and PALSAR " +"polarimetric data. The SIR-C format contains an image in compressed " +"scattering matrix form, described `here " +"`__. GDAL " +"decompresses the data as it is read in. The PALSAR format contains bands " +"that correspond almost exactly to elements of the 3x3 Hermitian " +"covariance matrix- see the `ERSDAC-VX-CEOS-004A.pdf " +"`__ document for a complete" +" description (pixel storage is described on page 193). GDAL converts " +"these to complex floating point covariance matrix bands as they are read " +"in. The convention used to represent the covariance matrix in terms of " +"the scattering matrix elements HH, HV (=VH), and VV is indicated below. " +"Note that the non-diagonal elements of the matrix are complex values, " +"while the diagonal values are real (though represented as complex bands)." +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:63 +msgid "The identities of the bands are also reflected in the metadata." +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:65 +msgid "NOTE: Implemented as :source_file:`frmts/ceos2/sar_ceosdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:5 +msgid "SAGA -- SAGA GIS Binary Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:7 +msgid "SAGA" +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:11 +msgid "" +"The driver supports both reading and writing (including create, delete, " +"and copy) SAGA GIS binary grids. SAGA binary grid datasets are made of an" +" ASCII header (.SGRD) and a binary data (.SDAT) file with a common " +"basename. The .SDAT file should be selected to access the dataset. " +"Starting with GDAL 2.3, the driver can read compressed .sg-grd-z files " +"that are ZIP archives with .sgrd, .sdat and .prj files." +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:18 +msgid "" +"The driver supports reading the following SAGA datatypes (in brackets the" +" corresponding GDAL types): BIT (GDT_Byte), BYTE_UNSIGNED (GDT_Byte), " +"BYTE (GDT_Byte), SHORTINT_UNSIGNED (GDT_UInt16), SHORTINT (GDT_Int16), " +"INTEGER_UNSIGNED (GDT_UInt32), INTEGER (GDT_Int32), FLOAT (GDT_Float32) " +"and DOUBLE (GDT_Float64)." +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:24 +msgid "" +"The driver supports writing the following SAGA datatypes: BYTE_UNSIGNED " +"(GDT_Byte), SHORTINT_UNSIGNED (GDT_UInt16), SHORTINT (GDT_Int16), " +"INTEGER_UNSIGNED (GDT_UInt32), INTEGER (GDT_Int32), FLOAT (GDT_Float32) " +"and DOUBLE (GDT_Float64)." +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:29 +msgid "" +"Currently the driver does not support zFactors other than 1 and reading " +"SAGA grids which are written TOPTOBOTTOM." +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:32 +msgid "NOTE: Implemented as :source_file:`frmts/saga/sagadataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/sdts.rst:5 +msgid "SDTS -- USGS SDTS DEM" +msgstr "" + +#: ../../source/drivers/raster/sdts.rst:7 +#: ../../source/drivers/vector/driver_summary.rst:357 +#: ../../source/drivers/vector/sdts.rst:4 +#: ../../source/drivers/vector/sdts.rst:6 +msgid "SDTS" +msgstr "" + +#: ../../source/drivers/raster/sdts.rst:11 +msgid "" +"GDAL includes support for reading USGS SDTS formatted DEMs. USGS DEMs are" +" always returned with a data type of signed sixteen bit integer, or 32bit" +" float. Projection and georeferencing information is also returned." +msgstr "" + +#: ../../source/drivers/raster/sdts.rst:15 +msgid "" +"SDTS datasets consist of a number of files. Each DEM should have one file" +" with a name like XXXCATD.DDF. This should be selected to open the " +"dataset." +msgstr "" + +#: ../../source/drivers/raster/sdts.rst:19 +msgid "" +"The elevation units of DEMs may be feet or meters. The GetType() method " +"on a band will attempt to return if the units are Feet (\"ft\") or Meters" +" (\"m\")." +msgstr "" + +#: ../../source/drivers/raster/sdts.rst:23 +msgid "NOTE: Implemented as :source_file:`frmts/sdts/sdtsdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:5 +msgid "SENTINEL2 -- Sentinel-2 Products" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:7 +msgid "SENTINEL2" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:9 +msgid "" +"This driver is built-in by default, but requires a JPEG2000 capable " +"driver to read the imagery" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:11 +msgid "" +"Driver for Sentinel-2 Level-1B, Level-1C and Level-2A products. Starting " +"with GDAL 2.1.3, Level-1C with \"Safe Compact\" encoding are also " +"supported." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:15 +msgid "" +"The SENTINEL2 driver will be used if the main metadata .xml file at the " +"root of a SENTINEL2 data product is opened (whose name is typically " +"S2A_OPER_MTD_SAFL1C\\_....xml). It can also accept directly .zip files " +"downloaded from the `Sentinels Scientific Data Hub " +"`__" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:21 +msgid "" +"To be able to read the imagery, GDAL must be configured with at least one" +" of the JPEG2000 capable drivers." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:24 +msgid "" +"SENTINEL-2 data are acquired on 13 spectral bands in the visible and " +"near-infrared (VNIR) and Short-wavelength infrared (SWIR) spectrum, as " +"show in the below table:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:29 +msgid "Band name" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:29 +msgid "Resolution (m)" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:29 +msgid "Central wavelength (nm)" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:29 +msgid "Band width (nm)" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:29 +msgid "Purpose" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:31 +msgid "B01" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:31 +#: ../../source/drivers/raster/sentinel2.rst:40 +#: ../../source/drivers/raster/sentinel2.rst:41 +msgid "60" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:31 +msgid "443" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:31 +msgid "Aerosol detection" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:32 +msgid "B02" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:32 +#: ../../source/drivers/raster/sentinel2.rst:33 +#: ../../source/drivers/raster/sentinel2.rst:34 +#: ../../source/drivers/raster/sentinel2.rst:38 +msgid "10" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:32 +msgid "490" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:32 +msgid "65" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:32 +msgid "Blue" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:33 +msgid "B03" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:33 +msgid "560" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:33 +msgid "35" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:33 +msgid "Green" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:34 +msgid "B04" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:34 +msgid "665" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:34 +#: ../../source/drivers/raster/sentinel2.rst:41 +msgid "30" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:34 +msgid "Red" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:35 +msgid "B05" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:35 +msgid "705" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:35 +#: ../../source/drivers/raster/sentinel2.rst:36 +msgid "15" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:35 +#: ../../source/drivers/raster/sentinel2.rst:36 +#: ../../source/drivers/raster/sentinel2.rst:37 +#: ../../source/drivers/raster/sentinel2.rst:39 +msgid "Vegetation classification" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:36 +msgid "B06" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:36 +msgid "740" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:37 +msgid "B07" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:37 +msgid "783" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:38 +msgid "B08" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:38 +msgid "842" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:38 +msgid "115" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:38 +msgid "Near infrared" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:39 +msgid "B08A" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:39 +msgid "865" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:40 +msgid "B09" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:40 +msgid "945" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:40 +msgid "Water vapour" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:41 +msgid "B10" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:41 +msgid "1375" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:41 +msgid "Cirrus" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:42 +msgid "B11" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:42 +msgid "1610" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:42 +msgid "90" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:42 +#: ../../source/drivers/raster/sentinel2.rst:43 +msgid "Snow / ice / cloud discrimination" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:43 +msgid "B12" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:43 +msgid "2190" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:43 +msgid "180" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:54 +msgid "Level-1B" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:56 +msgid "" +"Level-1B products are composed of several \"granules\" of ~ 25 km across-" +"track x ~ 23km along-track, in sensor geometry (i.e. non ortho-" +"rectified). Each granule correspond to the imagery captured by one of the" +" 12 detectors across-track (for a total 290 km swath width). The imagery " +"of each band is put in a separate JPEG2000 file." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:62 +msgid "Level-1B products are aimed at advanced users." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:64 +msgid "" +"When opening the main metadata .xml file, the driver will typically " +"expose N \\* 3 sub-datasets, where N is the number of granules composing " +"the user product, and 3 corresponds to the number of spatial resolutions." +" There's one for the 4 10m bands, one for the 6 20m bands and one for the" +" 3 60m bands. Caution: the number of such subdatasets can be typically of" +" several hundreds or more." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:71 +msgid "" +"It is also possible to open the metadata .xml of a given granule, in " +"which case 3 subdatasets will be reported for each of the 3 spatial " +"resolutions." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:75 +msgid "" +"When opening a subdataset, the georeferencing is made of 5 ground control" +" points for the 4 corner of the images and the center of image." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:79 +msgid "Level-1C" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:81 +msgid "" +"Level-1C products are organized in ortho-rectified tiles of 100 km x 100 " +"km in UTM WGS84 projections. The imagery of each band is put in a " +"separate JPEG2000 file." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:85 +#: ../../source/drivers/raster/sentinel2.rst:120 +msgid "" +"When opening the main metadata .xml file, the driver will typically " +"expose 4 sub-datasets:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:88 +msgid "one for the 4 10m bands," +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:89 +msgid "one for the 6 20m bands," +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:90 +msgid "one for the 3 60m bands and," +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:91 +msgid "one for a preview of the R,G,B bands at a 320m resolution" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:93 +#: ../../source/drivers/raster/sentinel2.rst:134 +msgid "" +"All tiles of same resolution and projection are mosaiced together. If a " +"product spans over several UTM zones, they will be exposed as separate " +"subdatasets." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:97 +msgid "" +"It is also possible to open the metadata .xml file of each tile (only for" +" original L1C encoding, not supported on \"Safe Compact\" encoding), in " +"which case the driver will typically expose the 4 above mentioned types " +"of sub-datasets." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:103 +msgid "Level-2A" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:105 +msgid "" +"Similarly to Level-1C, Level-2A products are organized in ortho-rectified" +" tiles of 100 km x 100 km in UTM WGS84 projections. The imagery of each " +"band is put in a separate JPEG2000 file. The values are Bottom-Of-" +"Atmosphere (BOA) reflectances. L2A specific bands are also computed:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:111 +msgid "AOT: Aerosol Optical Thickness map (at 550nm)" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:112 +msgid "" +"CLD: Raster mask values range from 0 for high confidence clear sky to 100" +" for high confidence cloudy" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:114 +msgid "" +"SCL: Scene Classification. The meaning of the values is indicated in the " +"Category Names of the band." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:116 +msgid "" +"SNW: Raster mask values range from 0 for high confidence NO snow/ice to " +"100 for high confidence snow/ice" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:118 +msgid "WVP: Scene-average Water Vapour map" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:123 +msgid "one for the 4 native 10m bands, and L2A specific bands (AOT and WVP)" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:124 +msgid "" +"one for the 6 native 20m bands, and L2A specific bands (AOT, WVP, SCL, " +"CLD and SNW)," +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:126 +msgid "" +"one for the B01 and B09 native 60m bands, and L2A specific bands (AOT, " +"WVP, SCL, CLD and SNW)," +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:128 +msgid "" +"one for a true-color image (TCI) of the R,G,B bands at a 10m resolution, " +"for the \"compact\" L2A product formulation (or a preview of the R,G,B " +"bands at a 320m resolution for the older L2A product formulation). The " +"TCI products at resolution 20m and 60m are not exposed, as they are just " +"subsampled versions of the 10m product." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:141 +msgid "" +"Metadata of the main metadata .xml file is available in the general " +"metadata domain. The whole XML file is also accessible through the " +"xml:SENTINEL2 metadata domain." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:145 +msgid "" +"Subdatasets are based on the VRT format, so the definition of this VRT " +"can be obtained by querying the xml:VRT metadata domain." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:149 +msgid "Performance issues for L1C and L2A" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:151 +msgid "" +"Due to the way Sentinel-2 products are structured, in particular because " +"of the number of JPEG2000 files involved, zoom-out operations can be very" +" slow for products made of many tiles. For interactive display, it can be" +" useful to generate overviews (can be a slow operation by itself). This " +"can be done with the gdaladdo utility on the subdataset name. The " +"overview file is created next to the main metadata .xml file, with the " +"same name, but prefixed with \\_XX_EPSG_YYYYY.tif.ovr where " +"XX=10m,20m,60m or PREVIEW and YYYYY is the EPSG code." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:160 +msgid "" +"Trick: if the content of the zoom-out preview is not important for the " +"use case, blank overviews can be created instantaneously by using the " +"NONE resampling method ('-r none' as gdaladdo switch)." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:164 +msgid "" +"When converting a subdataset to another format like tiled GeoTIFF, if " +"using the JP2OpenJPEG driver, the recommended minimum value for the " +":config:`GDAL_CACHEMAX` configuration option is (subdataset_width \\* " +"2048 \\* 2 ) / 10000000 if generating a INTERLEAVE=BAND GeoTIFF, or that " +"value multiplied by the number of bands for the default INTERLEAVE=PIXEL " +"configuration. The current versions of the OpenJPEG libraries can also " +"consume a lot of memory to decode a JPEG2000 tile (up to 600MB), so you " +"might want to specify the :config:`GDAL_NUM_THREADS` configuration option" +" to a reasonable number of threads if you are short of memory (the " +"default value is the total number of virtual CPUs)." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:178 +msgid "|about-open-options| The driver can be passed the following open options:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:189 +msgid "" +"0 on areas with no tiles, or when the tile data is set to the NODATA or " +"SATURATED special values," +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:191 +msgid "4095 on areas with valid data." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:193 +msgid "" +"Note: above open options can also be specified as configuration options, " +"by prefixing the open option name with SENTINEL2\\_ (e.g. " +"SENTINEL2_ALPHA)." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:200 +msgid "Opening the main metadata file of a Sentinel2 product:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:257 +msgid "Opening the .zip file directly:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:263 +msgid "Opening the 10 meters resolution bands of a L1C subdataset:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:337 +msgid "Conversion of a L1C subdataset to tiled GeoTIFF" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:345 +msgid "Generating blank overviews for a L1C subdataset:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:351 +msgid "" +"Creating a VRT file from the subdataset (can be convenient to have the " +"subdatasets as files):" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:359 +msgid "Opening the 10 meters resolution bands of a L1B subdataset:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:457 +msgid "`Sentinels Scientific Data Hub `__" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:458 +msgid "" +"`Sentinel 2 User guide `__" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:460 +msgid "" +"`Sentinel 2 User Handbook `__" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:466 +msgid "" +"This driver has been developed by `Spatialys `__ " +"with funding from `Centre National d'Etudes Spatiales (CNES) " +"`__" +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:5 +msgid "SGI -- SGI Image Format" +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:7 +msgid "SGI" +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:11 +msgid "" +"The SGI driver currently supports the reading and writing of SGI Image " +"files." +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:14 +msgid "" +"The driver currently supports 1, 2, 3, and 4 band images. The driver " +"currently supports \"8 bit per channel value\" images. The driver " +"supports both uncompressed and run-length encoded (RLE) images for " +"reading, but created files are always RLE compressed.." +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:19 +msgid "The GDAL SGI Driver was based on Paul Bourke's SGI image read code." +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:23 +msgid "" +"`Paul Bourke's SGI Image Read Code " +"`__" +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:25 +msgid "" +"`SGI Image File Format Document " +"`__" +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:28 +msgid "NOTE: Implemented as :source_file:`frmts/sgi/sgidataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/sigdem.rst:5 +msgid "SIGDEM -- Scaled Integer Gridded DEM" +msgstr "" + +#: ../../source/drivers/raster/sigdem.rst:7 +msgid "SIGDEM" +msgstr "" + +#: ../../source/drivers/raster/sigdem.rst:13 +msgid "" +"The SIGDEM driver supports reading and writing `Scaled Integer Gridded " +"DEM `__ files." +msgstr "" + +#: ../../source/drivers/raster/sigdem.rst:16 +msgid "" +"SIGDEM files contain exactly 1 band. The in-memory band data is stored " +"using GDT_Float64." +msgstr "" + +#: ../../source/drivers/raster/sigdem.rst:19 +msgid "" +"SIGDEM prefers use of an EPSG ID inside the file for coordinate systems. " +"Only if the spatial reference doesn't have an EPSG ID will a .prj file be" +" written or read." +msgstr "" + +#: ../../source/drivers/raster/sigdem.rst:23 +msgid "NOTE: Implemented as :source_file:`frmts/sigdem/sigdemdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/snodas.rst:5 +msgid "SNODAS -- Snow Data Assimilation System" +msgstr "" + +#: ../../source/drivers/raster/snodas.rst:7 +msgid "SNODAS" +msgstr "" + +#: ../../source/drivers/raster/snodas.rst:11 +msgid "" +"This is a convenience driver to read Snow Data Assimilation System data. " +"Those files contain Int16 raw binary data. The file to provide to GDAL is" +" the .Hdr file." +msgstr "" + +#: ../../source/drivers/raster/snodas.rst:15 +msgid "" +"`Snow Data Assimilation System (SNODAS) Data Products at NSIDC " +"`__" +msgstr "" + +#: ../../source/drivers/raster/snodas.rst:18 +msgid "NOTE: Implemented as :source_file:`frmts/raw/snodasdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/srp.rst:5 +msgid "SRP -- Standard Product Format (ASRP/USRP) (.gen)" +msgstr "" + +#: ../../source/drivers/raster/srp.rst:7 +msgid "SRP" +msgstr "" + +#: ../../source/drivers/raster/srp.rst:11 +msgid "" +"The ASRP and USRP raster products (as defined by DGIWG) are variations on" +" a common standard product format and are supported for reading by GDAL. " +"ASRP and USRP datasets are made of several files - typically a .GEN, " +".IMG, .SOU and .QAL file with a common basename. The .IMG file should be " +"selected to access the dataset." +msgstr "" + +#: ../../source/drivers/raster/srp.rst:17 +msgid "" +"ASRP (in a geographic coordinate system) and USRP (in a UTM/UPS " +"coordinate system) products are single band images with a palette and " +"georeferencing." +msgstr "" + +#: ../../source/drivers/raster/srp.rst:21 +msgid "" +"the Transmission Header File (.THF) can also be used as an input to GDAL." +" If the THF references more than one image, GDAL will report the images " +"it is composed of as subdatasets. If the THF references just one image, " +"GDAL will open it directly." +msgstr "" + +#: ../../source/drivers/raster/srp.rst:26 +msgid "NOTE: Implemented as :source_file:`frmts/adrg/srpdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:5 +msgid "SRTMHGT -- SRTM HGT Format" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:7 +msgid "SRTMHGT" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:11 +msgid "" +"The SRTM HGT driver currently supports the reading of SRTM-3 and SRTM-1 " +"V2 (HGT) files. The files must be named like NXXEYYY.hgt, or starting " +"with GDAL 2.1.2, NXXEYYY[.something].hgt" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:15 +msgid "" +"Starting with GDAL 2.2, the driver can directly read .hgt.zip files " +"provided that they are named like NXXEYYY[.something].hgt.zip and contain" +" a NXXEYYY.hgt file. For previous versions, use " +"/vsizip//path/to/NXXEYYY[.something].hgt.zip/NXXEYYY.hgt syntax" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:20 +msgid "" +"The driver does support creating new files, but the input data must be " +"exactly formatted as a SRTM-3 or SRTM-1 cell. That is the size, and " +"bounds must be appropriate for a cell." +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:26 +msgid "" +"`SRTM documentation " +"`__" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:28 +msgid "`SRTM FAQ `__" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:29 +msgid "`SRTM data `__" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:31 +msgid "NOTE: Implemented as :source_file:`frmts/srtmhgt/srtmhgtdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:5 +msgid "STACIT - Spatio-Temporal Asset Catalog Items" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:9 +msgid "STACIT" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:13 +msgid "" +"This driver supports opening STAC API ItemCollections, with the input " +"usually being a `STAC API search query `_ or the results saved as a JSON " +"file. Items in the response must include projection information following" +" the `Projection Extension Specification `_. It builds a virtual mosaic from the items." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:16 +msgid "" +"A STACIT dataset which has no subdatasets is actually a :ref:`raster.vrt`" +" dataset. Thus, translating it into VRT will result in a VRT file that " +"directly references the items." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:19 +msgid "" +"Note that `STAC API ItemCollections `_ are not " +"the same as `STAC Collections `_. STAC API ItemCollections are GeoJSON" +" FeatureCollections enhanced with STAC entities." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:22 +#: ../../source/drivers/raster/stacta.rst:36 +#: ../../source/drivers/raster/wms.rst:453 +#: ../../source/drivers/raster/wmts.rst:25 +#: ../../source/drivers/vector/gtfs.rst:24 +msgid "Open syntax" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:24 +msgid "" +"STACIT datasets/subdatasets can be accessed with one of the following " +"syntaxes:" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:26 +#: ../../source/drivers/raster/stacta.rst:40 +msgid "``filename.json``: local file" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:28 +msgid "``STACIT:\"https://example.com/filename.json\"``: remote file or query" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:30 +msgid "" +"``STACIT:\"filename.json\":asset=my_asset``: specify the name of the " +"asset GDAL should read (i.e. \"visual\")" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:32 +msgid "" +"``STACIT:\"filename.json\":collection=my_collect,asset=my_asset``: limit " +"to items in a given collection and specify asset to read" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:34 +msgid "" +"``STACIT:\"filename.json\":collection=my_collect,asset=my_asset,crs=my_crs``:" +" specify a collection, asset, and limit to items in a given CRS" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:36 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if STACIT`` option to command " +"line utilities accepting it, or ``STACIT`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename or URL." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:79 +msgid "" +"Starting with GDAL 3.9.1, the ``REMOVE_IF_NO_NODATA`` strategy is applied" +" by default. The STACIT virtual mosaic will omit fully covered items, " +"only if no band declares a nodata value. (Note that the determination " +"whether a band has a nodata value of not is done by opening one of the " +"items, and assuming it is representative of the characteristics of the " +"others in the collection)." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:86 +msgid "" +"This strategy can be forced in all cases by selecting the " +"``USE_MOST_RECENT`` strategy (this was the strategy applied prior to " +"3.9.1)" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:89 +msgid "" +"The ``USE_ALL`` strategy always causes all items to be listed in the " +"virtual mosaic, with the most recent ones being rendered on top of the " +"less recent ones." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:96 +msgid "" +"If a STACIT JSON file contains several collections, assets or CRS, the " +"driver will return a list of subdataset names to open each of the " +"possible subdatasets." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:108 +msgid "" +"List the subdatasets associated to a `STAC search " +"`_" +" on a given collection, bbox and starting from a datetime:" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:116 +msgid "Open a subdataset returned by the above request:" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:126 +msgid ":ref:`raster.stacta` documentation page." +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:5 +msgid "STACTA - Spatio-Temporal Asset Catalog Tiled Assets" +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:9 +msgid "STACTA" +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:13 +msgid "" +"This driver supports opening JSON files following the `Spatio-Temporal " +"Asset Catalog Tiled Assets `_ specification. Such JSON file references tiles (also called " +"metatiles), split from a potentially big dataset according to a tiling " +"scheme, with several zoom levels. The driver provides a single raster " +"view, with overviews, of the dataset described by the JSON file. The " +"driver supports metatiles of arbitrary size." +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:20 +msgid "" +"The driver may use the `Electro-Optical Extension `__ and, starting with GDAL 3.8.2, the `Raster " +"Extension `__ attached to an " +"asset template." +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:38 +msgid "" +"STACTA datasets/subdatasets can be accessed with one of the following " +"syntaxes:" +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:42 +msgid "``STACTA:\"https://example.com/filename.json\"``: remote file" +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:44 +msgid "" +"``STACTA:\"filename.json\":my_asset``: specify an asset of a local/remote" +" file" +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:46 +msgid "" +"``STACTA:\"filename.json\":my_asset:my_tms``: specify an asset and tiling" +" scheme of a local/remote file" +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:48 +msgid "The root of the JSON file must be of type ``Feature``." +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:50 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if STACTA`` option to command " +"line utilities accepting it, or ``STACTA`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename or URL." +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:80 +msgid "" +"If a STACTA JSON file contains several asset templates and/or tiling " +"scheme, the driver will return a list of subdataset names to open each of" +" the possible subdatasets." +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:92 +msgid ":ref:`raster.stacit` documentation page." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:5 +msgid "Terragen -- Terragen™ Terrain File" +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:7 +msgid "Terragen" +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:11 +msgid "" +"Terragen terrain files store 16-bit elevation values with optional " +"gridspacing (but not positioning). The file extension for Terragen " +"heightfields is \"TER\" or \"TERRAIN\" (which in the former case is the " +"same as Leveller, but the driver only recognizes Terragen files). The " +"driver ID is \"Terragen\". The dataset is file-based and has only one " +"elevation band. Void elevations are not supported. Pixels are considered " +"points." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:33 +msgid "" +"``dataset::GetProjectionRef()`` returns a local coordinate system using " +"meters." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:36 +msgid "``band::GetUnitType()`` returns meters." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:38 +msgid "" +"Elevations are ``Int16``. You must use the ``band::GetScale()`` and " +"``band::GetOffset()`` to convert them to meters." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:46 +msgid "" +"Use the ``Create`` call. Set the ``MINUSERPIXELVALUE`` option (a float) " +"to the lowest elevation of your elevation data, and ``MAXUSERPIXELVALUE``" +" to the highest. The units must match the elevation units you will give " +"to ``band::SetUnitType()``." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:51 +msgid "" +"Call ``dataset::SetProjection()`` and ``dataset::SetGeoTransform()`` with" +" your coordinate system details. Otherwise, the driver will not encode " +"physical elevations properly. Geographic (degree-based) coordinate " +"systems will be converted to a local meter-based system." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:56 +msgid "" +"To maintain precision, a best-fit baseheight and scaling will be used to " +"use as much of the 16-bit range as possible." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:59 +msgid "Elevations are ``Float32``." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:64 +msgid "Roundtripping" +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:66 +msgid "" +"Errors per trip tend to be a few centimeters for elevations and up to one" +" or two meters for ground extents if degree-based coordinate systems are " +"written. Large degree-based DEMs incur unavoidable distortions since the " +"driver currently only uses meters." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:74 +msgid "Implemented as :source_file:`frmts/terragen/terragendataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:75 +msgid "" +"See `readme.txt <./readme.txt>`__ for installation and support " +"information." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:77 +msgid "" +"`Terragen Terrain File Specification " +"`__." +msgstr "" + +#: ../../source/drivers/raster/tga.rst:5 +msgid "TGA -- TARGA Image File Format" +msgstr "" + +#: ../../source/drivers/raster/tga.rst:9 +msgid "TGA" +msgstr "" + +#: ../../source/drivers/raster/tga.rst:13 +msgid "The TGA driver currently supports reading TGA 2.0 files." +msgstr "" + +#: ../../source/drivers/raster/tga.rst:15 +msgid "" +"The driver supports reading 1 (grey-level or paletted), 3 (RGB), and 4 " +"(RGBA, or RGB-undefined) band images. The driver supports both " +"uncompressed or RLE-compressed images. Top-left or bottom-left origins " +"are supported (if the later, the lines are re-order to expose a top-left " +"order). 16-bit RGB encoded images are also supported." +msgstr "" + +#: ../../source/drivers/raster/tga.rst:21 +msgid "" +"The following metadata items may be reported: IMAGE_ID, AUTHOR_NAME and " +"COMMENTS. The extended area is used to determine if the fourth band is an" +" alpha channel or not." +msgstr "" + +#: ../../source/drivers/raster/tga.rst:33 +msgid "" +"`Format specification " +"`_" +msgstr "" + +#: ../../source/drivers/raster/til.rst:5 +msgid "TIL -- EarthWatch/DigitalGlobe .TIL" +msgstr "" + +#: ../../source/drivers/raster/til.rst:7 +msgid "TIL" +msgstr "" + +#: ../../source/drivers/raster/til.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/til/tildataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:5 +msgid "TileDB - TileDB raster" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:7 +#: ../../source/drivers/vector/tiledb.rst:7 +msgid "TileDB" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:13 +msgid "GDAL can read and write TileDB arrays through the TileDB library." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:15 +#: ../../source/drivers/vector/tiledb.rst:15 +msgid "" +"The driver relies on the Open Source TileDB `library `__ (MIT licensed)." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:32 +msgid "The following open options exist:" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:60 +msgid "The following creation options exist:" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:108 +msgid "" +"``BAND``: a 3D array is created with the slowest varying dimension being " +"the band." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:109 +msgid "" +"``PIXEL``: a 3D array is created with the fastest varying dimension being" +" the band." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:110 +msgid "" +"``ATTRIBUTES``: a 2D array is created with each band being stored in a " +"separate TileDB attribute." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:124 +msgid "" +"When the dataset is created within a TileDB group, overviews that may be " +"created are stored as TileDB arrays inside that group, next to the full " +"resolution array. This makes administration of the dataset easier." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:128 +msgid "" +"Otherwise, the past default behavior (CREATE_GROUP=NO) is to create the " +"dataset as a TileDB array. Overviews cannot be created in that mode." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:137 +msgid "" +"The TileDB driver supports the :ref:`multidim_raster_data_model` for " +"reading and writing operations. It requires GDAL to be built and run " +"against TileDB >= 2.15." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:140 +msgid "" +"The driver supports: - creating and reading groups and subgroups - " +"creating and reading multidimensional dense arrays with a numeric data " +"type - creating and reading numeric or string attributes in groups and " +"arrays - storing an indexing array of a dimension as a TileDB dimension " +"label" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:146 +msgid "" +"The multidimensional API supports reading dense arrays created by the " +"classic raster API of GDAL." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:149 +msgid "The following multidimensional dataset open options are available:" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:151 +#: ../../source/drivers/raster/tiledb.rst:159 +msgid "" +"**TILEDB_CONFIG=config**: A local file with TileDB configuration `options" +" `__" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:154 +#: ../../source/drivers/raster/tiledb.rst:167 +msgid "" +"**TILEDB_TIMESTAMP=val**: inclusive ending timestamp when opening this " +"array" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:157 +msgid "The following multidimensional dataset creation options are available:" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:162 +#: ../../source/drivers/raster/tiledb.rst:182 +msgid "" +"**TILEDB_TIMESTAMP=val**: Create array at this timestamp. Should be " +"strictly greater than zero when set." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:165 +msgid "The following array open options are available:" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:170 +msgid "The following array creation options are available:" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:172 +msgid "**BLOCKSIZE=val1,val2,...,valN**: Block size in pixels" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:174 +msgid "" +"**COMPRESSION=NONE/GZIP/ZSTD/LZ4/RLE/BZIP2/DOUBLE-DELTA/POSITIVE-DELTA**:" +" Compression to use. Default is NONE" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:177 +msgid "**COMPRESSION_LEVEL=int_value**: compression level" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:179 +msgid "" +"**IN_MEMORY=YES/NO**: hether the array should be only in-memory. Useful " +"to create an indexing variable that is serialized as a dimension label" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:185 +msgid "" +"Cf :source_file:`autotest/gdrivers/tiledb_multidim.py` for examples of " +"how to use the Python multidimensional API with the TileDB driver." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:191 +#: ../../source/drivers/vector/tiledb.rst:240 +msgid "`TileDB home page `__" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:193 +msgid ":ref:`TileDB vector ` documentation page" +msgstr "" + +#: ../../source/drivers/raster/tsx.rst:5 +msgid "TSX -- TerraSAR-X Product" +msgstr "" + +#: ../../source/drivers/raster/tsx.rst:7 +msgid "TSX" +msgstr "" + +#: ../../source/drivers/raster/tsx.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/tsx/tsxdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:5 +msgid "USGSDEM -- USGS ASCII DEM (and CDED)" +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:7 +msgid "USGSDEM" +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:11 +msgid "" +"GDAL includes support for reading USGS ASCII DEM files. This is the " +"traditional format used by USGS before being replaced by SDTS, and is the" +" format used for CDED DEM data products from Canada. Most popular " +"variations on USGS DEM files should be supported, including correct " +"recognition of coordinate system, and georeferenced positioning." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:17 +msgid "" +"The 7.5 minute (UTM grid) USGS DEM files will generally have regions of " +"missing data around the edges, and these are properly marked with a " +"nodata value. Elevation values in USGS DEM files may be in meters or " +"feet, and this will be indicated by the return value of " +"GDALRasterBand::GetUnitType() (either \"m\" or \"ft\")." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:23 +msgid "" +"Note that USGS DEM files are represented as one big tile. This may cause " +"cache thrashing problems if the GDAL tile cache size is small. It will " +"also result in a substantial delay when the first pixel is read as the " +"whole file will be ingested." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:28 +msgid "" +"Some of the code for implementing usgsdemdataset.cpp was derived from VTP" +" code by Ben Discoe. See the `Virtual Terrain " +"`__ project for more information on VTP." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:45 +msgid "" +"GDAL supports export of geographic (and UTM) USGS DEM and CDED data " +"files, including the ability to generate CDED 2.0 50K products to " +"Canadian federal government specifications." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:49 +msgid "" +"Input data must already be sampled in a geographic or UTM coordinate " +"system. By default the entire area of the input file will be output, but " +"for CDED50K products the output file will be sampled at the production " +"specified resolution and on product tile boundaries." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:54 +msgid "" +"If the input file has appropriate coordinate system information set, " +"export to specific product formats can take input in different coordinate" +" systems (i.e. from Albers projection to NAD83 geographic for CDED50K " +"production)." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:146 +msgid "" +"Example: The following would generate a single CDED50K tile, extracting " +"from the larger DEM coverage yk_3arcsec for a tile with the top left " +"corner -117w,60n. The file yk_template.dem is used to set some product " +"fields including the Producer of Data, Process Code and Origin Code " +"fields." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:159 +msgid "NOTE: Implemented as :source_file:`frmts/usgsdem/usgsdemdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:161 +msgid "" +"The USGS DEM reading code in GDAL was derived from the importer in the " +"`VTP `__ software. The export capability was " +"developed with the financial support of the Yukon Department of " +"Environment." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:5 +msgid "VICAR -- VICAR" +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:12 +msgid "" +"PDS3 datasets can incorporate a VICAR header. By default, GDAL will use " +"the :ref:`PDS ` driver in that situation. Starting with GDAL " +"3.1, if the :config:`GDAL_TRY_PDS3_WITH_VICAR` configuration option is " +"set to YES, the dataset will be opened by the VICAR driver. " +"Alternatively, starting with GDAL 3.10, specifying the ``-if VICAR`` " +"option to command line utilities accepting it, or ``VICAR`` as the only " +"value of the ``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also " +"forces the driver to recognize the passed filename." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:37 +msgid "" +"Starting with GDAL 3.1, the VICAR label can be retrieved as JSON-" +"serialized content in the json:VICAR metadata domain." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:137 +msgid "Binary prefixes" +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:139 +msgid "" +"Starting with GDAL 3.1, if the VICAR label declares a non-zero binary " +"prefix length (`NBB` label item), then GDAL will look in the `vicar.json`" +" configuration file if there is an entry corresponding to the `BLTYPE` " +"label item (currently only M94_HRSC is defined), and if there is a match," +" a OGR vector layer will be available on the dataset, with a feature for " +"each image record." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:183 +msgid "" +"Starting with GDAL 3.1, the VICAR driver supports updating imagery of " +"existing datasets, creating new datasets through the CreateCopy() and " +"Create() interfaces." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:187 +msgid "" +"When using CreateCopy(), gdal_translate or gdalwarp, an effort is made to" +" preserve as much as possible of the original label when doing VICAR to " +"VICAR conversions. This can be disabled with the :co:`USE_SRC_LABEL=NO` " +"creation option." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:224 +msgid "" +"Value of MAP.TARGET_NAME. This is normally deduced from the SRS datum " +"name. If specified, and USE_SRC_MAP is in effect, this will be taken into" +" account to override the source TARGET_NAME." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:251 +msgid "Implemented as :source_file:`frmts/pds/vicardataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:252 +msgid "`VICAR documentation `_" +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:253 +msgid "" +"`VICAR file format `_" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:5 +msgid "VRT -- GDAL Virtual Format" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:7 ../../source/drivers/vector/vrt.rst:6 +msgid "VRT" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:14 +msgid "" +"The VRT driver is a format driver for GDAL that allows a virtual GDAL " +"dataset to be composed from other GDAL datasets with repositioning, and " +"algorithms potentially applied as well as various kinds of metadata " +"altered or added. VRT descriptions of datasets can be saved in an XML " +"format normally given the extension .vrt." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:20 +msgid "Note .vrt files starting with" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:22 +msgid " open with :ref:`ogrinfo`, etc." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:23 +msgid " open with :ref:`gdalinfo`, etc." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:25 +msgid "" +"The VRT format can also describe :ref:`gdal_vrttut_warped` and " +":ref:`gdal_vrttut_pansharpen`" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:28 +msgid "" +"For mosaic with a very large number of tiles (tens of thousands or " +"mores), the :ref:`GTI ` driver may be used starting with GDAL" +" 3.9." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:31 +msgid "" +"An example of a simple .vrt file referring to a 512x512 dataset with one " +"band loaded from :file:`utm.tif` might look like this:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:49 +msgid "" +"Many aspects of the VRT file are a direct XML encoding of the " +":ref:`raster_data_model` which should be reviewed for understanding of " +"the semantics of various elements." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:53 +msgid "" +"VRT files can be produced by translating to VRT format. The resulting " +"file can then be edited to modify mappings, add metadata or other " +"purposes. VRT files can also be produced programmatically by various " +"means." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:57 +msgid "" +"This tutorial will cover the .vrt file format (suitable for users editing" +" .vrt files), and how .vrt files may be created and manipulated " +"programmatically for developers." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:77 +msgid "" +"Setting explicitly the block size is an advanced setting that should only" +" be used when the user has determined that it is needed. By default the " +"block size is set to:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:81 +msgid "" +"128x128 for a source-based VRT raster band. Unless the VRT is made of a " +"single source and this single source is not subsetted, in which case the " +"block size of the unique source will be set as the VRT raster band block " +"size)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:85 +msgid "512x128 for a warped VRT." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:88 +#: ../../source/drivers/raster/vrt_multidimensional.rst:37 +msgid ".vrt Format" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:90 +msgid "" +"A `XML schema of the GDAL VRT format " +"`_" +" is available." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:93 +msgid "" +"Note, .vrt files starting with - open with ogrinfo, " +"etc. - open with gdalinfo, etc." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:97 +#: ../../source/drivers/raster/vrt_multidimensional.rst:42 +msgid "" +"Virtual files stored on disk are kept in an XML format with the following" +" elements." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:100 +msgid "" +"**VRTDataset**: This is the root element for the whole GDAL dataset. It " +"must have the attributes rasterXSize and rasterYSize describing the width" +" and height of the dataset in pixels. It may have a subClass attributes " +"with values VRTWarpedDataset (:ref:`gdal_vrttut_warped`) or " +"VRTPansharpenedDataset (:ref:`gdal_vrttut_pansharpen`). It may have SRS, " +"GeoTransform, GCPList, Metadata, MaskBand and VRTRasterBand subelements." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:107 +msgid "VRTDataset" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:109 +msgid "The allowed subelements for VRTDataset are :" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:111 +msgid "" +"**SRS**: This element contains the spatial reference system (coordinate " +"system) in OGC WKT format. Note that this must be appropriately escaped " +"for XML, so items like quotes will have the ampersand escape sequences " +"substituted. As well as WKT, valid input to the " +":cpp:func:`OGRSpatialReference::SetFromUserInput` method (such as well " +"known GEOGCS names, and PROJ.4 format) is also allowed in the SRS " +"element." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:117 +msgid "" +"The **dataAxisToSRSAxisMapping** attribute is allowed since GDAL 3.0 to " +"describe the relationship between the axis indicated in the CRS " +"definition and the axis of the GeoTransform or GCP metadata. The value of" +" the attribute is a comma separated list of integers. The number of " +"elements of this list must be the number of axis of the CRS. Values start" +" at 1. If m denotes the array values of this attribute, then m[0] is the " +"data axis number for the first axis of the CRS. If the attribute is " +"missing, then the OAMS_TRADITIONAL_GIS_ORDER data axis to CRS axis " +"mapping strategy is implied." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:119 +msgid "" +"**GeoTransform**: This element contains a six value affine " +"geotransformation for the dataset, mapping between pixel/line coordinates" +" and georeferenced coordinates. Typically (geotransform[0], " +"geotransform[3]) will be the (easting, northing) of the upper-left corner" +" of the raster, geotransform[1] the horizontal resolution in geospatial " +"coordinates/pixel, and geotransform[5] the vertical resolution in " +"geospatial coordinates/pixel, as a negative value if the image is north-" +"up oriented. See :ref:`raster_data_model_geotransform` for more details " +"about that mapping." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:125 +msgid "" +"**GCPList**: This element contains a list of Ground Control Points for " +"the dataset, mapping between pixel/line coordinates and georeferenced " +"coordinates. The Projection attribute should contain the SRS of the " +"georeferenced coordinates in the same format as the SRS element. The " +"dataAxisToSRSAxisMapping attribute is the same as in the SRS element." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:134 +msgid "" +"**Metadata**: This element contains a list of metadata name/value pairs " +"associated with the VRTDataset as a whole, or a VRTRasterBand. It has " +" (metadata item) subelements which have a \"key\" attribute and the " +"value as the data of the element. The Metadata element can be repeated " +"multiple times, in which case it must be accompanied with a \"domain\" " +"attribute to indicate the name of the metadata domain." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:142 +msgid "" +"**MaskBand**: This element represents a mask band that is shared between " +"all bands on the dataset (see GMF_PER_DATASET in RFC 15). It must contain" +" a single VRTRasterBand child element, that is the description of the " +"mask band itself." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:157 +msgid "" +"**OverviewList**: (GDAL >= 3.2.0, not valid for VRTPansharpenedDataset) " +"This elements contains a list of overview factors, separated by space, to" +" create \"virtual overviews\". For example ``2 4``. It can be used so " +"that bands of the VRT datasets declare overviews. This only makes sense " +"to use if the sources added in those bands have themselves overviews " +"compatible with the declared factor. It is generally not necessary to use" +" this mechanism, since downsampling pixel requests on a VRT dataset/band " +"are able to use overviews of the sources, even when the VRT bands do not " +"declare them. One situation where explicit overviews are needed at the " +"VRT level is the warping of a VRT to a lower resolution. This element can" +" also be used with an existing VRT dataset by running " +":cpp:func:`GDALDataset::BuildOverviews` or :program:`gdaladdo` with the " +":config:`VRT_VIRTUAL_OVERVIEWS` configuration option set to ``YES``:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:175 +msgid "" +"Virtual overviews have the least priority compared to the **Overview** " +"element at the **VRTRasterBand** level, or to materialized .vrt.ovr " +"files." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:179 +msgid "**VRTRasterBand**: This represents one band of a dataset." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:182 +msgid "VRTRasterBand" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:184 +msgid "The attributes for VRTRasterBand are:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:186 +msgid "" +"**dataType** (optional): type of the pixel data associated with this band" +" (use names Byte, UInt16, Int16, UInt32, Int32, Float32, Float64, CInt16," +" CInt32, CFloat32 or CFloat64). If not specified, defaults to 1" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:190 +msgid "**band** (optional): band number this element represents (1 based)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:192 +msgid "" +"**blockXSize** (optional, GDAL >= 3.3): block width. If not specified, " +"defaults to the minimum of the raster width and 128." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:195 +msgid "" +"**blockYSize** (optional, GDAL >= 3.3): block height. If not specified, " +"defaults to the minimum of the raster height and 128." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:198 +msgid "" +"This element may have Metadata, ColorInterp, NoDataValue, " +"HideNoDataValue, ColorTable, GDALRasterAttributeTable, Description and " +"MaskBand subelements as well as the various kinds of source elements such" +" as SimpleSource, ComplexSource, AveragedSource, NoDataFromMaskSource, " +"KernelFilteredSource and ArraySource. A raster band may have many " +"\"sources\" indicating where the actual raster data should be fetched " +"from, and how it should be mapped into the raster bands pixel space." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:200 +msgid "The allowed subelements for VRTRasterBand are :" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:202 +msgid "" +"**ColorInterp**: The data of this element should be the name of a color " +"interpretation type. One of Gray, Palette, Red, Green, Blue, Alpha, Hue," +" Saturation, Lightness, Cyan, Magenta, Yellow, Black, or Unknown." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:208 +msgid "" +"**NoDataValue**: If the input datasets to be composed have a nodata value" +" for this raster band, set this element's value to that nodata value for " +"it to be reflected in the VRT. This must not be confused with the NODATA " +"element of a VRTComplexSource element." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:214 +msgid "" +"**HideNoDataValue**: If this value is 1, the nodata value will not be " +"reported. Essentially, the caller will not be aware of a nodata pixel " +"when it reads one. Any datasets copied/translated from this will not " +"have a nodata value. This is useful when you want to specify a fixed " +"background value for the dataset. The background will be the value " +"specified by the NoDataValue element. Default value is 0 when this " +"element is absent." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:220 +msgid "" +"**ColorTable**: This element is parent to a set of Entry elements " +"defining the entries in a color table. Currently only RGBA color tables " +"are supported with c1 being red, c2 being green, c3 being blue and c4 " +"being alpha. The entries are ordered and will be assumed to start from " +"color table entry 0." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:229 +msgid "" +"**GDALRasterAttributeTable**: (GDAL >=2.3) This element is parent to a " +"set of FieldDefn elements defining the columns of a raster attribute " +"table, followed by a set of Row elements defining the values of the " +"columns of each row." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:268 +msgid "" +"**Description**: This element contains the optional description of a " +"raster band as its text value." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:274 +msgid "" +"**UnitType**: This optional element contains the vertical units for " +"elevation band data. One of \"m\" for meters or \"ft\" for feet. Default" +" assumption is meters." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:280 +msgid "" +"**Offset**: This optional element contains the offset that should be " +"applied when computing \"real\" pixel values from scaled pixel values on " +"a raster band. The default is 0.0." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:286 +msgid "" +"**Scale**: This optional element contains the scale that should be " +"applied when computing \"real\" pixel values from scaled pixel values on " +"a raster band. The default is 1.0." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:292 +msgid "" +"**Overview**: This optional element describes one overview level for the " +"band. It should have a child SourceFilename and SourceBand element. The" +" SourceFilename may have a relativeToVRT boolean attribute. Multiple " +"elements may be used to describe multiple overviews." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:301 +msgid "" +"**CategoryNames**: This optional element contains a list of Category " +"subelements with the names of the categories for classified raster band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:313 +msgid "" +"**SimpleSource**: The SimpleSource_ indicates that raster data should be " +"read from a separate dataset, indicating the dataset, and band to be read" +" from, and how the data should map into this band's raster space." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:315 +msgid "" +"**AveragedSource**: The AveragedSource is derived from the SimpleSource " +"and shares the same properties except that it uses an averaging " +"resampling instead of a nearest neighbour algorithm as in SimpleSource, " +"when the size of the destination rectangle is not the same as the size of" +" the source rectangle. Note: a more general mechanism to specify " +"resampling algorithms can be used. See above paragraph about the " +"'resampling' attribute." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:317 +msgid "" +"**NoDataFromMaskSource**: (GDAL >= 3.9) The NoDataFromMaskSource is " +"derived from the SimpleSource and shares the same properties except that " +"it replaces the value of the source with the value of the NODATA child " +"element when the value of the mask band of the source is less or equal to" +" the MaskValueThreshold child element. This is typically used to " +"transform a R,G,B,A image into a R,G,B one with a NoData value." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:319 +msgid "" +"**ComplexSource**: The ComplexSource_ is derived from the SimpleSource " +"(so it shares the SourceFilename, SourceBand, SrcRect and DstRect " +"elements), but it provides support to rescale and offset the range of the" +" source values. Certain regions of the source can be masked by specifying" +" the NODATA value, or starting with GDAL 3.3, with the " +"true element." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:321 +msgid "" +"**KernelFilteredSource**: The KernelFilteredSource_ is a pixel source " +"derived from the Simple Source (so it shares the SourceFilename, " +"SourceBand, SrcRect and DstRect elements, but it also passes the data " +"through a simple filtering kernel specified with the Kernel element." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:323 +msgid "" +"**ArraySource**: The ArraySource_ indicates that raster data should be " +"read from a 2D array using the multidimensional API." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:325 +msgid "" +"**MaskBand**: This element represents a mask band that is specific to the" +" VRTRasterBand it contains. It must contain a single VRTRasterBand child " +"element, that is the description of the mask band itself." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:328 +msgid "Sources" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:331 +msgid "SimpleSource" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:333 +msgid "" +"The SimpleSource may have the SourceFilename, SourceBand, SrcRect, and " +"DstRect subelements. The SrcRect element will indicate what rectangle on" +" the indicated source file should be read, and the DstRect element " +"indicates how that rectangle of source data should be mapped into the " +"VRTRasterBands space." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:338 +msgid "" +"SrcRect and DstRect are expressed in pixel/line coordinate space. Their " +"relationship with the geospatial coordinate space is given by the " +"geotransform matrix of the source for SrcRect, and of the VRT itself " +"(**GeoTransform** element) for DstRect. See " +":ref:`raster_data_model_geotransform` for more details about that " +"mapping." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:344 +msgid "" +"The relativeToVRT attribute on the SourceFilename indicates whether the " +"filename should be interpreted as relative to the .vrt file (value is 1) " +"or not relative to the .vrt file (value is 0). The default is 0." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:348 +msgid "" +"Some characteristics of the source band can be specified in the optional " +"``SourceProperties`` element to enable the VRT driver to defer the " +"opening of the source dataset until it really needs to read data from it." +" This is particularly useful when building VRTs with a big number of " +"source datasets. The needed parameters are the raster dimensions, the " +"size of the blocks and the data type. If the SourceProperties tag is not " +"present, the source dataset will be opened at the same time as the VRT " +"itself." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:357 +msgid "" +"Starting with GDAL 3.4, the ``SourceProperties`` element is no longer " +"necessary for deferred opening of the source datasets." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:360 +msgid "" +"The content of the SourceBand subelement can refer to a mask band. For " +"example mask,1 means the mask band of the first band of the source." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:373 +msgid "" +"A OpenOptions subelement can be added to specify the open options to " +"apply when opening the source dataset. It has (open option item) " +"subelements which have a \"key\" attribute and the value as the data of " +"the element." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:390 +msgid "" +"A resampling attribute can be specified on a SimpleSource or " +"ComplexSource element to specified the resampling algorithm used when the" +" size of the destination rectangle is not the same as the size of the " +"source rectangle. The values allowed for that attribute are : " +"nearest,bilinear,cubic, cubicspline,lanczos,average,mode." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:407 +msgid "ComplexSource" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:409 +msgid "" +"Alternatively to linear scaling, non-linear scaling using a power " +"function can be used by specifying the Exponent, SrcMin, SrcMax, DstMin " +"and DstMax elements. If SrcMin and SrcMax are not specified, they are " +"computed from the source minimum and maximum value (which might require " +"analyzing the whole source dataset). Exponent must be positive. (Those 5 " +"values can be set with the -exponent and -scale options of " +"gdal_translate.)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:417 +msgid "" +"The ComplexSource supports adding a custom lookup table to transform the " +"source values to the destination. The LUT can be specified using the " +"following form:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:425 +msgid "" +"The intermediary values are calculated using a linear interpolation " +"between the bounding destination values of the corresponding range. " +"Source values should be listed in a monotonically non-decreasing order. " +"If there is a Not-A-Number (NaN) source value, it should be the first " +"one. Clamping is performed for input pixel values outside of the range " +"specified by the LUT. That is, if an input pixel value is lower than the " +"minimum source value, then the destination value corresponding to that " +"minimum source value is used as the output pixel value. And similarly for" +" an input pixel value that is greater than the maximum source value." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:434 +msgid "" +"The ComplexSource supports fetching a color component from a source " +"raster band that has a color table. The ColorTableComponent value is the " +"index of the color component to extract : 1 for the red band, 2 for the " +"green band, 3 for the blue band or 4 for the alpha band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:439 +msgid "" +"When transforming the source values the operations are executed in the " +"following order:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:442 +msgid "" +"Masking, if the NODATA element is set or, starting with GDAL 3.3, if the " +"UseMaskBand is set to true and the source band has a mask band. Note that" +" this is binary masking only, so no alpha blending is done if the mask " +"band is actually an alpha band with non-0 or non-255 values." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:446 +msgid "Color table expansion" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:447 +msgid "For linear scaling, applying the scale ratio, then scale offset" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:448 +msgid "" +"For non-linear scaling, apply (DstMax-DstMin) * pow( (SrcValue-SrcMin) / " +"(SrcMax-SrcMin), Exponent) + DstMin" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:449 +msgid "Table lookup" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:465 +msgid "Non-linear scaling:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:483 +msgid "KernelFilteredSource" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:485 +msgid "" +"The Kernel element should have two child elements, Size and Coefs and " +"optionally the boolean attribute normalized (defaults to false=0). The " +"size must always be an odd number, and the Coefs must have Size * Size " +"entries separated by spaces. For now kernel is not applied to sub-" +"sampled or over-sampled data." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:502 +msgid "" +"Starting with GDAL 2.3, a separable kernel may also be used. In this " +"case the number of Coefs entries should correspond to the Size. The " +"Coefs specify a one-dimensional kernel which is applied along each axis " +"in succession, resulting in far quicker execution. Many common image-" +"processing filters are separable. For example, a Gaussian blur:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:520 +msgid "NoDataFromMaskSource" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:524 +msgid "" +"The NoDataFromMaskSource is derived from the SimpleSource and shares the " +"same properties except that it replaces the value of the source with the " +"value of the NODATA child element when the value of the mask band of the " +"source is less or equal to the MaskValueThreshold child element. This is " +"typically used to transform a R,G,B,A image into a R,G,B one with a " +"NoData value. An optional RemappedValue element can be set to specify the" +" value onto which valid pixels whose value is the one of NODATA should be" +" remapped to. When RemappedValue is not explicitly specified, for Byte " +"bands, if NODATA=255, it is implicitly set to 254, otherwise it is set to" +" NODATA+1." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:540 +msgid "ArraySource" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:544 +msgid "" +"The ArraySource_ indicates that raster data should be read from a 2D " +"array using the multidimensional API. If the original array is not a 3D " +"array, a DerivedArray with a View step must be typically used to create a" +" 2D slice." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:548 +msgid "ArraySource can have the following child elements:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:550 +msgid "" +"``SingleSourceArray``, ``DerivedArray`` or ``Array``: required as first " +"child element" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:551 +msgid "``SrcRect`` (same syntax and semantics as in SimpleSource): optional" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:552 +msgid "``DstRect`` (same syntax and semantics as in SimpleSource): optional" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:555 +msgid "SingleSourceArray" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:557 +msgid "" +"SingleSourceArray references a multidimensional raster through a " +"SourceFilename element and an array through its full path within it with " +"SourceArray. When SingleSourceArray is used as a direct child of " +"ArraySource, it must be a 2-dimensional array." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:573 +msgid "" +"Be careful that quite often arrays in the multidimensional API use a " +"\"bottom-up\" approach, and it might thus be needed to reverse the Y " +"axis, with a View expression with a DerivedArray (cf below example)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:578 +msgid "DerivedArray" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:580 +msgid "" +"A DerivedArray starts with an array coming from a SingleSourceArray (but " +"it could also be a DerivedArray or a Array), which must be the first " +"child element, and applies different processing steps wrapped in zero or " +"more Step elements." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:585 +msgid "View step: applies the :cpp:func:`GDALMDArray::GetView` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:587 +msgid "" +"The ``View`` element must have an ``expr`` attribute, which is the " +"argument of :cpp:func:`GDALMDArray::GetView` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:590 +msgid "" +"The following example slices the 3D dimension at index 0 and flips the " +"vertical axis (assuming 1st dimension is a non-spatial one, 2nd dimension" +" is the Y dimension and 3rd dimension is the X dimension)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:608 +msgid "``Transpose`` step: applies the :cpp:func:`GDALMDArray::Transpose` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:610 +msgid "" +"The ``Transpose`` element must have a ``newOrder`` attribute, which is " +"the argument of :cpp:func:`GDALMDArray::Transpose` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:613 +msgid "The following example transposes the 2 axis of a 2D array" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:629 +msgid "Resample step: applies the :cpp:func:`GDALMDArray::GetResampled` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:631 +msgid "" +"The ``Resample`` element may have the following child elements, which " +"correspond to the arguments of the :cpp:func:`GDALMDArray::GetResampled` " +"method:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:634 +msgid "" +"``Dimension``: with a ``name`` and ``size`` attribute. This element may " +"be repeated." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:635 +msgid "" +"``ResampleAlg``: whose value is ``NearestNeighbour`` (default), " +"``Cubic``, ``CubicSpline``, ``Bilinear``, ``Lanczos``, ``Average``, " +"``RMS`` or ``Mode``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:636 +msgid "" +"``SRS``: target SRS (string recognized by " +":cpp:func:`OGRSpatialReference::SetFromUserInput`)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:637 +#: ../../source/drivers/raster/vrt.rst:667 +#: ../../source/drivers/raster/vrt.rst:721 +msgid "" +"``Option`` with a ``name`` attribute and the value as the content of the " +"element. This element may be repeated." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:659 +msgid "Grid step: applies the :cpp:func:`GDALMDArray::GetGridded` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:661 +msgid "" +"The ``Grid`` element may have the following child elements, which " +"correspond to the arguments of the :cpp:func:`GDALMDArray::GetGridded` " +"method:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:664 +msgid "``GridOptions`` (required): name and options of the gridding algorithm" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:665 +msgid "" +"``XArray`` (optional): its child value should be a SingleSourceArray, " +"DerivedArray or Array pointing to the array to use for the X dimension. " +"This is needed if the source array does not have a ``coordinates`` " +"attribute." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:666 +msgid "" +"``YArray`` (optional): its child value should be a SingleSourceArray, " +"DerivedArray or Array pointing to the array to use for the Y dimension. " +"This is needed if the source array does not have a ``coordinates`` " +"attribute." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:698 +msgid "" +"``GetUnscaled`` step: applies the :cpp:func:`GDALMDArray::GetUnscaled` " +"method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:700 +msgid "It does not have any child elements." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:716 +msgid "``GetMask`` step: applies the :cpp:func:`GDALMDArray::GetMask` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:718 +msgid "" +"The ``GetMask`` element may have the following child elements, which " +"correspond to the arguments of the :cpp:func:`GDALMDArray::GetMask` " +"method:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:740 +msgid "Array" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:742 +msgid "" +":ref:`Array ` can be used to mosaic several " +"multidimensional arrays." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:748 +msgid "" +"GDAL can make efficient use of overviews available in the sources that " +"compose the bands when dealing with RasterIO() requests that involve " +"downsampling. But in the general case, the VRT bands themselves will not " +"expose overviews." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:752 +msgid "Except if (from top priority to lesser priority) :" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:754 +msgid "" +"The **Overview** element is present in the VRTRasterBand element. See " +"above." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:755 +msgid "or external .vrt.ovr overviews are built" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:756 +msgid "" +"(starting with GDAL 3.2) explicit virtual overviews, if a " +"**OverviewList** element is declared in the VRTDataset element (see " +"above). Those virtual overviews will be hidden by external .vrt.ovr " +"overviews that might be built later." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:759 +msgid "" +"(starting with GDAL 2.1) implicit virtual overviews, if the VRTRasterBand" +" are made of a single SimpleSource or ComplexSource that has overviews. " +"Those virtual overviews will be hidden by external .vrt.ovr overviews " +"that might be built later." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:764 +msgid ".vrt Descriptions for Raw Files" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:766 +msgid "" +"So far we have described how to derive new virtual datasets from existing" +" files supported by GDAL. However, it is also common to need to utilize " +"raw binary raster files for which the regular layout of the data is known" +" but for which no format specific driver exists. This can be " +"accomplished by writing a .vrt file describing the raw file." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:772 +msgid "" +"For example, the following .vrt describes a raw raster file containing " +"floating point complex pixels in a file called *l2p3hhsso.img*. The " +"image data starts from the first byte (ImageOffset=0). The byte offset " +"between pixels is 8 (PixelOffset=8), the size of a CFloat32. The byte " +"offset from the start of one line to the start of the next is 9376 bytes " +"(LineOffset=9376) which is the width (1172) times the size of a pixel " +"(8)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:791 +msgid "" +"Some things to note are that the VRTRasterBand has a subClass specifier " +"of \"VRTRawRasterBand\". Also, the VRTRawRasterBand contains a number of" +" previously unseen elements but no \"source\" information. " +"VRTRawRasterBands may never have sources (i.e. SimpleSource), but should " +"contain the following elements in addition to all the normal \"metadata\"" +" elements previously described which are still supported." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:798 +msgid "" +"**SourceFilename**: The name of the raw file containing the data for this" +" band. The relativeToVRT attribute can be used to indicate if the " +"SourceFilename is relative to the .vrt file (1) or not (0)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:800 +msgid "" +"**ImageOffset**: The offset in bytes to the beginning of the first pixel " +"of data of this image band. Defaults to zero." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:802 +msgid "" +"**PixelOffset**: The offset in bytes from the beginning of one pixel and " +"the next on the same line. In packed single band data this will be the " +"size of the **dataType** in bytes." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:804 +msgid "" +"**LineOffset**: The offset in bytes from the beginning of one scanline of" +" data and the next scanline of data. In packed single band data this " +"will be PixelOffset * rasterXSize." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:806 +msgid "" +"**ByteOrder**: Defines the byte order of the data on disk. Either LSB " +"(Least Significant Byte first) such as the natural byte order on Intel " +"x86 systems or MSB (Most Significant Byte first) such as the natural byte" +" order on Motorola or Sparc systems. Defaults to being the local machine" +" order." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:808 +msgid "A few other notes:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:810 +msgid "" +"The image data on disk is assumed to be of the same data type as the band" +" **dataType** of the VRTRawRasterBand." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:812 +msgid "" +"All the non-source attributes of the VRTRasterBand are supported, " +"including color tables, metadata, nodata values, and color " +"interpretation." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:814 +msgid "" +"The VRTRawRasterBand supports in place update of the raster, whereas the " +"source based VRTRasterBand is always read-only." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:816 +msgid "" +"The OpenEV tool includes a File menu option to input parameters " +"describing a raw raster file in a GUI and create the corresponding .vrt " +"file." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:818 +msgid "" +"Multiple bands in the one .vrt file can come from the same raw file. Just" +" ensure that the ImageOffset, PixelOffset, and LineOffset definition for " +"each band is appropriate for the pixels of that particular band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:820 +msgid "Another example, in this case a 400x300 RGB pixel interleaved image." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:849 +msgid "Creation of VRT Datasets" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:851 +msgid "" +"The VRT driver supports several methods of creating VRT datasets. The " +":file:`vrtdataset.h` include file should be installed with the core GDAL " +"include files, allowing direct access to the VRT classes. However, even " +"without that most capabilities remain available through standard GDAL " +"interfaces." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:857 +msgid "" +"To create a VRT dataset that is a clone of an existing dataset use the " +":cpp:func:`GDALDriver::CreateCopy` method. For example to clone " +":file:`utm.tif` into a :file:`wrk.vrt` file in C++ the following could be" +" used:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:873 +msgid "" +"Note the use of :cpp:func:`GDALOpenShared` when opening the source " +"dataset. It is advised to use :cpp:func:`GDALOpenShared` in this " +"situation so that you are able to release the explicit reference to it " +"before closing the VRT dataset itself. In other words, in the previous " +"example, you could also invert the 2 last lines, whereas if you open the " +"source dataset with :cpp:func:`GDALOpen`, you'd need to close the VRT " +"dataset before closing the source dataset." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:880 +msgid "" +"To obtain the resulting VRT XML of :file:`wrk.vrt` without having to read" +" the text from an actual file, you can modify the above code to open the " +"new dataset with an empty filename and use the \"xml:VRT\" metadata " +"domain." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:892 +msgid "" +"To create a virtual copy of a dataset with some attributes added or " +"changed such as metadata or coordinate system that are often hard to " +"change on other formats, you might do the following. In this case, the " +"virtual dataset is created \"in memory\" only by virtual of creating it " +"with an empty filename, and then used as a modified source to pass to a " +":cpp:func:`GDALDriver::CreateCopy` written out in TIFF format." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:915 +msgid "" +"In the above example the nodata value is set as -999. You can set the " +"HideNoDataValue element in the VRT dataset's band using " +":cpp:func:`GDALRasterBand::SetMetadataItem` on that band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:923 +msgid "" +"In this example a virtual dataset is created with the " +":cpp:func:`GDALDriver::Create` method, and adding bands and sources " +"programmatically, but still via the \"generic\" API. A special attribute " +"of VRT datasets is that sources can be added to the VRTRasterBand (but " +"not to VRTRawRasterBand) by passing the XML describing the source into " +":cpp:func:`GDALRasterBand::SetMetadataItem` on the special domain target " +"\"new_vrt_sources\". The domain target \"vrt_sources\" may also be used," +" in which case any existing sources will be discarded before adding the " +"new ones. In this example we construct a simple averaging filter source " +"instead of using the simple source." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:949 +msgid "" +"A more general form of this that will produce a 3x3 average filtered " +"clone of any input datasource might look like the following. In this " +"case we deliberately set the filtered datasource as in the " +"\"vrt_sources\" domain to override the SimpleSource created by the " +"`cpp:func:`GDALDriver::CreateCopy` method. The fact that we used " +"`cpp:func:GDALDriver::CreateCopy` ensures that all the other metadata, " +"georeferencing and so forth is preserved from the source dataset ... the " +"only thing we are changing is the data source for each band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:986 +msgid "" +"The :cpp:class:`VRTDataset` class is one of the few dataset " +"implementations that supports the :cpp:func:`GDALDataset::AddBand` " +"method. The options passed to the :cpp:func:`GDALDataset::AddBand` method" +" can be used to control the type of the band created (VRTRasterBand, " +"VRTRawRasterBand, VRTDerivedRasterBand), and in the case of the " +"VRTRawRasterBand to set its various parameters. For standard " +"VRTRasterBand, sources should be specified with the above " +":cpp:func:`GDALRasterBand::SetMetadataItem` examples." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1014 +msgid "Using Derived Bands (with pixel functions in C/C++)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1016 +msgid "" +"A specialized type of band is a 'derived' band which derives its pixel " +"information from its source bands. With this type of band you must also " +"specify a pixel function, which has the responsibility of generating the " +"output raster. Pixel functions are created by an application and then " +"registered with GDAL using a unique key." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1022 +msgid "" +"Using derived bands you can create VRT datasets that manipulate bands on " +"the fly without having to create new band files on disk. For example, " +"you might want to generate a band using four source bands from a nine " +"band input dataset (x0, x3, x4, and x8) and some constant y:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1031 +msgid "" +"You could write the pixel function to compute this value and then " +"register it with GDAL with the name \"MyFirstFunction\". Then, the " +"following VRT XML could be used to display this derived band:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1072 +msgid "" +"PixelFunctionArguments can only be used with C++ pixel functions in GDAL " +"versions 3.4 and greater." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1075 +msgid "" +"In addition to the subclass specification (VRTDerivedRasterBand) and the " +"PixelFunctionType value, there is another new parameter that can come in " +"handy: SourceTransferType. Typically the source rasters are obtained " +"using the data type of the derived band. There might be times, however, " +"when you want the pixel function to have access to higher resolution " +"source data than the data type being generated. For example, you might " +"have a derived band of type \"Float\", which takes a single source of " +"type \"CFloat32\" or \"CFloat64\", and returns the imaginary portion. To" +" accomplish this, set the SourceTransferType to \"CFloat64\". Otherwise " +"the source would be converted to \"Float\" prior to calling the pixel " +"function, and the imaginary portion would be lost." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1097 +msgid "Default Pixel Functions" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1099 +msgid "" +"GDAL provides a set of default pixel functions that can be used without " +"writing new code:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1106 +msgid "PixelFunctionType" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1107 +msgid "Number of input sources" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1108 +msgid "PixelFunctionArguments" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1110 +msgid "**cmul**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1113 +msgid "multiply the first band for the complex conjugate of the second" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1114 +msgid "**complex**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1117 +msgid "make a complex band merging two bands used as real and imag values" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1118 +msgid "**conj**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1121 +msgid "" +"computes the complex conjugate of a single raster band (just a copy if " +"the input is non-complex)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1122 +msgid "**dB**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1124 +msgid "``fact`` (optional)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1125 +msgid "" +"perform conversion to dB of the abs of a single raster band (real or " +"complex): ``20. * log10( abs( x ) )``. The optional ``fact`` parameter " +"can be set to ``10`` to get the alternative formula: ``10. * log10( abs( " +"x ) )``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1126 +msgid "**dB2amp**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1129 +msgid "" +"perform scale conversion from logarithmic to linear (amplitude) (i.e. " +"``10 ^ ( x / 20 )`` ) of a single raster band (real only). Deprecated in " +"GDAL v3.5. Please use the ``exp`` pixel function with ``base = 10.`` and " +"``fact = 0.05`` i.e. ``1./20``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1130 +msgid "**dB2pow**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1133 +msgid "" +"perform scale conversion from logarithmic to linear (power) (i.e. ``10 ^ " +"( x / 10 )`` ) of a single raster band (real only). Deprecated in GDAL " +"v3.5. Please use the ``exp`` pixel function with ``base = 10.`` and " +"``fact = 0.1`` i.e. ``1./10``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1134 +msgid "**diff**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1137 +msgid "computes the difference between 2 raster bands (``b1 - b2``)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1138 +msgid "**div**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1141 +msgid "divide one raster band by another (``b1 / b2``)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1142 +msgid "**norm_diff**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1145 +msgid "" +"computes the normalized difference between two raster bands: ``(b1 - " +"b2)/(b1 + b2)``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1146 +msgid "**exp**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1148 +msgid "``base`` (optional), ``fact`` (optional)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1149 +msgid "" +"computes the exponential of each element in the input band ``x`` (of real" +" values): ``e ^ x``. The function also accepts two optional parameters: " +"``base`` and ``fact`` that allow to compute the generalized formula: " +"``base ^ ( fact * x )``. Note: this function is the recommended one to " +"perform conversion form logarithmic scale (dB): `` 10. ^ (x / 20.)``, in " +"this case ``base = 10.`` and ``fact = 0.05`` i.e. ``1. / 20``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1150 +msgid "**imag**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1153 +msgid "extract imaginary part from a single raster band (0 for non-complex)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1154 +msgid "**intensity**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1157 +msgid "" +"computes the intensity ``Re( x * conj(x) )`` of a single raster band " +"(real or complex)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1158 +msgid "**interpolate_exp**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1159 +#: ../../source/drivers/raster/vrt.rst:1163 +#: ../../source/drivers/raster/vrt.rst:1175 +#: ../../source/drivers/raster/vrt.rst:1179 +#: ../../source/drivers/raster/vrt.rst:1187 +#: ../../source/drivers/raster/vrt.rst:1211 +msgid ">= 2" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1160 +#: ../../source/drivers/raster/vrt.rst:1164 +msgid "``t0``, ``dt``, ``t``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1161 +msgid "" +"interpolate a value at time (or position) ``t`` given input sources " +"beginning at position ``t0`` with spacing ``dt`` using exponential " +"interpolation" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1162 +msgid "**interpolate_linear**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1165 +msgid "" +"interpolate a value at time (or position) ``t`` given input sources " +"beginning at ``t0`` with spacing ``dt`` using linear interpolation" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1166 +msgid "**inv**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1168 +#: ../../source/drivers/raster/vrt.rst:1188 +#: ../../source/drivers/raster/vrt.rst:1212 +msgid "``k`` (optional)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1169 +msgid "" +"inverse (``1./x``). If the optional ``k`` parameter is set then the " +"result is multiplied by ``k`` (``k / x``)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1170 +msgid "**log10**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1173 +msgid "" +"compute the logarithm (base 10) of the abs of a single raster band (real " +"or complex): ``log10( abs( x ) )``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1174 +msgid "**max**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1176 +#: ../../source/drivers/raster/vrt.rst:1180 +msgid "``propagateNoData`` (optional)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1177 +msgid "" +"(GDAL >= 3.8) maximum of 2 or more raster bands, ignoring by default " +"pixels at nodata. If the optional ``propagateNoData`` parameter is set to" +" ``true``, then if a nodata pixel is found in one of the bands, if will " +"be propagated to the output value." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1178 +msgid "**min**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1181 +msgid "" +"(GDAL >= 3.8) minimum of 2 or more raster bands, ignoring by default " +"pixels at nodata. If the optional ``propagateNoData`` parameter is set to" +" ``true``, then if a nodata pixel is found in one of the bands, if will " +"be propagated to the output value." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1182 +msgid "**mod**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1185 +msgid "extract module from a single raster band (real or complex)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1186 +msgid "**mul**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1189 +msgid "" +"multiply 2 or more raster bands. If the optional ``k`` parameter is " +"provided then the result is multiplied by the scalar ``k``." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1190 +msgid "**phase**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1193 +msgid "extract phase from a single raster band [-PI,PI] (0 or PI for non-complex)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1194 +msgid "**polar**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1196 +msgid "``amplitude_type`` (optional)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1197 +msgid "" +"make a complex band using input bands for amplitude and phase values ``b1" +" * exp( j * b2 )``. The optional (string) parameter ``amplitude_type`` " +"can be ``AMPLITUDE`` (default) ``INTENSITY`` or ``dB``. Note: if " +"``amplitude_type`` is set to ``INTENSITY`` then negative values are " +"clipped to zero." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1198 +msgid "**pow**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1200 +msgid "``power``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1201 +msgid "" +"raise a single raster band to a constant power, specified with argument " +"``power`` (real only)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1202 +msgid "**real**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1205 +msgid "" +"extract real part from a single raster band (just a copy if the input is " +"non-complex)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1206 +msgid "**sqrt**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1209 +msgid "perform the square root of a single raster band (real only)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1210 +msgid "**sum**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1213 +msgid "" +"sum 2 or more raster bands. If the optional ``k`` parameter is provided " +"then it is added to each element of the result" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1214 +msgid "**replace_nodata**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1215 +#: ../../source/drivers/raster/vrt.rst:1219 +msgid "= 1" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1216 +msgid "``to`` (optional)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1217 +msgid "" +"convert incoming ``NoData`` values to a new value, IEEE 754 `nan` by " +"default" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1218 +msgid "**scale**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1221 +msgid "" +"perform scaling according to the ``offset`` and ``scale`` values of the " +"raster band" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1224 +msgid "Writing Pixel Functions" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1226 +msgid "" +"To register this function with GDAL (prior to accessing any VRT datasets " +"with derived bands that use this function), an application calls " +":cpp:func:`GDALAddDerivedBandPixelFuncWithArgs` with a key and a " +":cpp:type:`GDALDerivedPixelFuncWithArgs`:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1242 +msgid "" +"A good time to do this is at the beginning of an application when the " +"GDAL drivers are registered. ``pszMetadata`` is optional and can be " +"``nullptr``. It can be used to declare the function signature to the user" +" and to request additional parameters aside from the ones from the " +"Dataset." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1247 +msgid "" +"A :cpp:type:`GDALDerivedPixelFuncWithArgs` is defined with a signature " +"similar to :cpp:func:`GDALRasterBand::IRasterIO`:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst +msgid "Parameters" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1252 +msgid "" +"A pointer to packed rasters; one per source. The datatype of all will be" +" the same, specified in the ``eSrcType`` parameter." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1255 +msgid "The number of source rasters." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1257 +msgid "" +"The buffer into which the data should be read, or from which it should be" +" written. This buffer must contain at least ``nBufXSize * nBufYSize`` " +"words of type eBufType. It is organized in left to right, top to bottom " +"pixel order. Spacing is controlled by the ``nPixelSpace`` and " +"``nLineSpace`` parameters." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1263 +msgid "" +"The width of the buffer image into which the desired region is to be " +"read, or from which it is to be written." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1266 +msgid "" +"The height of the buffer image into which the desired region is to be " +"read, or from which it is to be written." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1269 +msgid "The type of the pixel values in the ``papoSources`` raster array." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1272 +msgid "" +"The type of the pixel values that the pixel function must generate in the" +" ``pData`` data buffer." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1275 +msgid "" +"The byte offset from the start of one pixel value in ``pData`` to the " +"start of the next pixel value within a scanline. If defaulted (0) the " +"size of the datatype eBufType is used." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1279 +msgid "" +"The byte offset from the start of one scanline in pData to the start of " +"the next." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1282 +msgid "An optional string list of named function arguments (e.g. ``y=4``)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1285 +msgid "" +"It is also possible to register a :cpp:type:`GDALDerivedPixelFunc` (which" +" omits the final :cpp:type:`CSLConstList` argument) using " +":cpp:func:`GDALAddDerivedBandPixelFunc`." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1287 +msgid "The following is an implementation of the pixel function:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1349 +msgid "Using Derived Bands (with pixel functions in Python)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1351 +msgid "" +"Starting with GDAL 2.2, in addition to pixel functions written in C/C++ " +"as documented in the :ref:`vrt_derived_bands` section, it is possible to " +"use pixel functions written in Python. Both `CPython " +"`_ and `NumPy `_ are " +"requirements at run-time." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1356 +msgid "" +"The subelements for VRTRasterBand (whose subclass specification must be " +"set to VRTDerivedRasterBand) are :" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1359 +msgid "" +"**PixelFunctionType** (required): Must be set to a function name that " +"will be defined as a inline Python module in PixelFunctionCode element or" +" as the form \"module_name.function_name\" to refer to a function in an " +"external Python module" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1361 +msgid "**PixelFunctionLanguage** (required): Must be set to Python." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1363 +msgid "" +"**PixelFunctionCode** (required if PixelFunctionType is of the form " +"\"function_name\", ignored otherwise). The in-lined code of a Python " +"module, that must be at least have a function whose name is given by " +"PixelFunctionType." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1365 +msgid "" +"**BufferRadius** (optional, defaults to 0): Amount of extra pixels, with " +"respect to the original RasterIO() request to satisfy, that are fetched " +"at the left, right, bottom and top of the input and output buffers passed" +" to the pixel function. Note that the values of the output buffer in this" +" buffer zone willbe ignored." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1367 +msgid "" +"**SkipNonContributingSources** (optional, added in GDAL 3.7, defaults to " +"false) = true/false: Whether sources that do not intersect the " +"VRTRasterBand RasterIO() requested region should be omitted. By default, " +"data for all sources, including ones that do not intersect it, are passed" +" to the pixel function. By setting this parameter to false, only sources " +"that intersect the requested region will be passed." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1369 +msgid "" +"The signature of the Python pixel function must have the following " +"arguments:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1371 +msgid "" +"**in_ar**: list of input NumPy arrays. One NumPy array for each source. " +"If SkipNonContributingSources=true, only contributing sources will be " +"passed." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1372 +msgid "" +"**out_ar**: output NumPy array to fill. The array is initialized at the " +"right dimensions and with the VRTRasterBand.dataType." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1373 +msgid "" +"**xoff**: pixel offset to the top left corner of the accessed region of " +"the band. Generally not needed except if the processing depends on the " +"pixel position in the raster." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1374 +msgid "" +"**yoff** line offset to the top left corner of the accessed region of the" +" band. Generally not needed." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1375 +msgid "" +"**xsize**: width of the region of the accessed region of the band. Can be" +" used together with out_ar.shape[1] to determine the horizontal " +"resampling ratio of the request." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1376 +msgid "" +"**ysize**: height of the region of the accessed region of the band. Can " +"be used together with out_ar.shape[0] to determine the vertical " +"resampling ratio of the request." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1377 +msgid "**raster_xsize**: total width of the raster band. Generally not needed." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1378 +msgid "**raster_ysize**: total height of the raster band. Generally not needed." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1379 +msgid "" +"**buf_radius**: radius of the buffer (in pixels) added to the left, " +"right, top and bottom of in_ar / out_ar. This is the value of the " +"optional BufferRadius element that can be set so that the original pixel " +"request is extended by a given amount of pixels." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1380 +msgid "**gt**: geotransform. Array of 6 double values." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1381 +msgid "" +"**kwargs**: dictionary with user arguments defined in " +"PixelFunctionArguments" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1383 +msgid "" +"The provided ``out_ar`` array must be modified in-place. Any value " +"currently returned by the pixel function is ignored." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1388 +msgid "" +"If wanting to fill ``out_ar`` from another array, use the ``out_ar[:] = " +"...`` syntax." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1395 +msgid "VRT that multiplies the values of the source file by a factor of 1.5" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1421 +msgid "VRT that adds 2 (or more) rasters" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1449 +msgid "VRT that computes hillshading using an external library" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1470 +msgid "with hillshading.py:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1529 +msgid "Python module path" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1531 +msgid "" +"When importing modules from inline Python code or when relying on out-of-" +"line code (PixelFunctionType of the form \"module_name.function_name\"), " +"you need to make sure the modules are accessible through the python path." +" Note that contrary to the Python interactive interpreter, the current " +"path is not automatically added when used from GDAL. So you may need to " +"define the **PYTHONPATH** environment variable if you get " +"ModuleNotFoundError exceptions." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1539 +msgid "Security implications" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1541 +msgid "" +"The ability to run Python code potentially opens the door to many " +"potential vulnerabilities if the user of GDAL may process untrusted " +"datasets. To avoid such issues, by default, execution of Python pixel " +"function will be disabled. The execution policy can be controlled with " +"the following configuration options:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1553 +msgid "" +"YES: all VRT scripts are considered as trusted and their Python pixel " +"functions will be run when pixel operations are involved." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1554 +msgid "" +"NO: all VRT scripts are considered untrusted, and none Python " +"pixelfunction will be run." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1555 +msgid "" +"TRUSTED_MODULES (default setting): all VRT scripts with inline Python " +"code in their PixelFunctionCode elements will be considered untrusted and" +" will not be run. VRT scripts that use a PixelFunctionType of the form " +"\"module_name.function_name\" will be considered as trusted, only if " +"\"module_name\" is allowed in the " +":config:`GDAL_VRT_PYTHON_TRUSTED_MODULES` configuration option." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1564 +msgid "Linking mechanism to a Python interpreter" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1566 +msgid "" +"Currently only CPython 2 and 3 is supported. The GDAL shared object is " +"not explicitly linked at build time to any of the CPython library. When " +"GDAL will need to run Python code, it will first determine if the Python " +"interpreter is loaded in the current process (which is the case if the " +"program is a Python interpreter itself, or if another program, e.g. QGIS," +" has already loaded the CPython library). Otherwise it will look if the " +":config:`PYTHONSO` configuration option is defined. This option can be " +"set to point to the name of the Python library to use, either as a " +"shortname like \"libpython3.10.so\" if it is accessible through the Linux" +" dynamic loader (so typically in one of the paths in /etc/ld.so.conf or " +"LD_LIBRARY_PATH) or as a full path name like \"/usr/lib/x86_64-linux-" +"gnu/libpython3.10.so\". The same holds on Windows will shortnames like " +"\"python310.dll\" if accessible through the PATH or full path names like " +"\"c:\\\\python310\\\\python310.dll\". If the :config:`PYTHONSO` " +"configuration option is not defined, it will look for a \"python\" binary" +" in the directories of the PATH and will try to determine the related " +"shared object (it will retry with \"python3\" if no \"python\" has been " +"found). If the above was not successful, then a predefined list of shared" +" objects names will be tried. At the time of writing, the order of " +"versions searched is 3.8, 3.9, 3.10, 3.11, 3.12, 3.7, 3.6, 3.5, 3.4, 3.3," +" 3.2. Enabling debug information (:config:`CPL_DEBUG=ON`) will show which" +" Python version is used." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1587 +msgid "Just-in-time compilation" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1589 +msgid "" +"The use of a just-in-time compiler may significantly speed up execution " +"times. `Numba `_ has been successfully tested. " +"For better performance, it is recommended to use a offline pixel function" +" so that the just-in-time compiler may cache its compilation." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1594 +msgid "Given the following :file:`mandelbrot.py` file :" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1646 +msgid "The following VRT file can be used (to be opened with QGIS for example)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1683 +msgid "Warped VRT" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1685 +msgid "" +"A warped VRT is a VRTDataset with subClass=\"VRTWarpedDataset\". It has a" +" GDALWarpOptions element which describe the warping options." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1729 +msgid "Pansharpened VRT" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1733 +msgid "" +"A VRT can describe a dataset resulting from a `pansharpening operation " +"`_ The pansharpening " +"VRT combines a panchromatic band with several spectral bands of lower " +"resolution to generate output spectral bands of the same resolution as " +"the panchromatic band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1739 +msgid "" +"VRT pansharpening assumes that the panchromatic and spectral bands have " +"the same projection (or no projection). If that is not the case, " +"reprojection must be done in a prior step. Bands might have different " +"geotransform matrices, in which case, by default, the resulting dataset " +"will have as extent the union of all extents." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1744 +msgid "" +"Currently the only supported pansharpening algorithm is a \"weighted\" " +"Brovey algorithm. The general principle of this algorithm is that, after " +"resampling the spectral bands to the resolution of the panchromatic band," +" a pseudo panchromatic intensity is computed from a weighted average of " +"the spectral bands. Then the output value of the spectral band is its " +"input value multiplied by the ratio of the real panchromatic intensity " +"over the pseudo panchromatic intensity." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1751 +msgid "Corresponding pseudo code:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1760 +msgid "" +"A valid pansharpened VRT must declare subClass=\"VRTPansharpenedDataset\"" +" as an attribute of the VRTDataset top element. The VRTDataset element " +"must have a child **PansharpeningOptions** element. This " +"PansharpeningOptions element must have a **PanchroBand** child element " +"and one of several **SpectralBand** elements. PanchroBand and " +"SpectralBand elements must have at least a **SourceFilename** child " +"element to specify the name of the dataset. They may also have a " +"**SourceBand** child element to specify the number of the band in the " +"dataset (starting with 1). If not specify, the first band will be " +"assumed. **OpenOptions** can also be specified" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1770 +msgid "" +"The SpectralBand element must generally have a **dstBand** attribute to " +"specify the number of the output band (starting with 1) to which the " +"input spectral band must be mapped. If the attribute is not specified, " +"the spectral band will be taken into account in the computation of the " +"pansharpening, but not exposed as an output band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1775 +msgid "" +"Panchromatic and spectral bands should generally come from different " +"datasets, since bands of a GDAL dataset are assumed to have all the same " +"dimensions. Spectral bands themselves can come from one or several " +"datasets. The only constraint is that they have all the same dimensions " +"and geotransform." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1780 +msgid "" +"An example of a minimalist working VRT is the following. It will " +"generates a dataset with 3 output bands corresponding to the 3 input " +"spectral bands of multispectral.tif, pansharpened with panchromatic.tif." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1819 +msgid "" +"In the above example, 3 output pansharpend bands will be created from the" +" 3 declared input spectral bands. The weights will be 1/3. Cubic " +"resampling will be used. The projection and geotransform from the " +"panchromatic band will be reused for the VRT dataset." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1824 +msgid "" +"It is possible to create more explicit and declarative pansharpened VRT, " +"allowing for example to only output part of the input spectral bands " +"(e.g. only RGB when the input multispectral dataset is RGBNir). It is " +"also possible to add \"classic\" VRTRasterBands, in addition to the " +"pansharpened bands." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1829 +msgid "" +"In addition to the above mentioned required PanchroBand and SpectralBand " +"elements, the PansharpeningOptions element may have the following " +"children elements :" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1832 +msgid "" +"**Algorithm**: to specify the pansharpening algorithm. Currently, only " +"WeightedBrovey is supported." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1833 +msgid "" +"**AlgorithmOptions**: to specify the options of the pansharpening " +"algorithm. With WeightedBrovey algorithm, the only supported option is a " +"**Weights** child element whose content must be a comma separated list of" +" real values assigning the weight of each of the declared input spectral " +"bands. There must be as many values as declared input spectral bands." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1834 +msgid "" +"**Resampling**: the resampling kernel used to resample the spectral bands" +" to the resolution of the panchromatic band. Can be one of Cubic " +"(default), Average, Near, CubicSpline, Bilinear, Lanczos." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1835 +msgid "" +"**NumThreads**: Number of worker threads. Integer number or ALL_CPUS. If " +"this option is not set, the :config:`GDAL_NUM_THREADS` configuration " +"option will be queried (its value can also be set to an integer or " +"ALL_CPUS)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1836 +msgid "" +"**BitDepth**: Can be used to specify the bit depth of the panchromatic " +"and spectral bands (e.g. 12). If not specified, the NBITS metadata item " +"from the panchromatic band will be used if it exists." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1837 +msgid "" +"**NoData**: Nodata value to take into account for panchromatic and " +"spectral bands. It will be also used as the output nodata value. If not " +"specified and all input bands have the same nodata value, it will be " +"implicitly used (unless the special None value is put in NoData to " +"prevent that)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1838 +msgid "" +"**SpatialExtentAdjustment**: Can be one of **Union** (default), " +"**Intersection**, **None** or **NoneWithoutWarning**. Controls the " +"behavior when panchromatic and spectral bands have not the same " +"geospatial extent. By default, Union will take the union of all spatial " +"extents. Intersection the intersection of all spatial extents. None will " +"not proceed to any adjustment at all, but will emit a warning. " +"NoneWithoutWarning is the same as None, but in a silent way." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1840 +msgid "" +"The below examples creates a VRT dataset with 4 bands. The first band is " +"the panchromatic band. The 3 following bands are than red, green, blue " +"pansharpened bands computed from a multispectral raster with red, green, " +"blue and near-infrared bands. The near-infrared bands is taken into " +"account for the computation of the pseudo panchromatic intensity, but not" +" bound to an output band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1906 +#: ../../source/drivers/raster/vrt_multidimensional.rst:5 +msgid "Multidimensional VRT" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1910 +msgid "See the dedicated :ref:`vrt_multidimensional` page." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1919 +msgid "Processed dataset VRT" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1923 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:9 +msgid "" +"A VRT processed dataset is a specific variant of the :ref:`raster.vrt` " +"format, to apply chained processing steps that may apply to several bands" +" at the same time." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1926 +msgid "See the dedicated :ref:`vrt_processed_dataset` page." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1935 +msgid "vrt:// connection string" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1939 +msgid "" +"In some contexts, it might be useful to benefit from features of VRT " +"without having to create a file or to provide the rather verbose VRT XML " +"content as the connection string. For that purpose, the following URI " +"syntax is supported for the dataset name since GDAL 3.1" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1980 +msgid "" +"The supported options currently are ``bands``, ``a_nodata``, ``a_srs``, " +"``a_ullr``, ``ovr``, ``expand``, ``a_scale``, ``a_offset``, ``ot``, " +"``gcp``, ``if``, ``scale``, ``exponent``, ``outsize``, ``projwin``, " +"``projwin_srs``, ``tr``, ``r``, ``srcwin``, ``a_gt``, ``oo``, " +"``unscale``, ``a_coord_epoch``, ``nogcp``, ``epo``, ``eco``, ``sd_name``," +" and ``sd``." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1984 +msgid "Other options may be added in the future." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1986 +msgid "" +"The effect of the ``bands`` option is to change the band composition. The" +" values specified are the source band numbers (between 1 and N), possibly" +" out-of-order or with repetitions. The ``mask`` value can be used to " +"specify the global mask band. This can also be seen as an equivalent of " +"running `gdal_translate -of VRT -b num1 ... -b numN`." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1991 +msgid "" +"The effect of the ``a_nodata`` option (added in GDAL 3.9) is to assign " +"(override) the nodata value of the source in the same way as " +"(:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1994 +msgid "" +"The effect of the ``a_srs`` option (added in GDAL 3.7) is to assign " +"(override) the coordinate reference system of the source in the same way " +"as (:ref:`gdal_translate`), it may be missing, or incorrect. The value " +"provided for ``a_srs`` may be a string or a file containing a srs " +"definition." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1999 +msgid "" +"The effect of the ``a_ullr`` option (added in GDAL 3.7) is to assign " +"(override) the georeferenced bounds of the source in the same way as " +"(:ref:`gdal_translate`). The value consists of four numeric values " +"separated by commas, in the order 'xmin,ymax,xmax,ymin' (upper left x,y, " +"lower right x,y)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2003 +msgid "" +"The effect of the ``ovr`` option (added in GDAL 3.7) is to specify which " +"overview level of source file must be used, with the first overview level" +" being 0 (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2006 +msgid "" +"The effect of the ``expand`` option (added in GDAL 3.7) is to expose a " +"dataset with 1 band with a color table as a dataset with 3 (RGB) or 4 " +"(RGBA) bands, as with (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2009 +msgid "" +"The effect of the ``a_scale`` option (added in GDAL 3.7) is to set band " +"scaling value (no modification of pixel values is done), as with " +"(:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2012 +msgid "" +"The effect of the ``a_offset`` option (added in GDAL 3.7) is to set band " +"offset value (no modification of pixel values is done), as with " +"(:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2015 +msgid "" +"The effect of the ``ot`` option (added in GDAL 3.7) is to force the " +"output image bands to have a specific data type supported by the driver " +"as with (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2018 +msgid "" +"The effect of the ``gcp`` option (added in GDAL 3.7) is to add the " +"indicated ground control point to the output dataset. Values are a set of" +" numbers as per (:ref:`gdal_translate`) " +"``pixel,line,easting,northing[,elevation]``. Multiple entries may be " +"included. This can also be seen as an equivalent of running " +"`gdal_translate -of VRT -gcp pixel1 line1 easting1 northing1 [elevation1]" +" -gcp pixel2 line2 easting2 northing2 [elevation2] ... -gcp pixelN lineN " +"eastingN northingN [elevationN]`." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2023 +msgid "" +"The effect of the ``if`` option (added in GDAL 3.7) is to specify the " +"format/driver name/s to be attempted to open the input file " +"(:ref:`gdal_translate`). Values may be repeated separated by comma This " +"can also be seen as an equivalent of running `gdal_translate -of VRT -if " +"DRV1 -if DRV2 ... -if DRVN`." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2027 +msgid "" +"The effect of the ``scale`` option (added in GDAL 3.7) is to rescale the " +"input pixel values from the range **src_min** to **src_max** to the range" +" **dst_min** to **dst_max** ``src_min,src_max[,dst_min,dst_max]`` either" +" 2 or 4 comma separated values. The same rules apply for the source and " +"destination ranges, and ``scale_bn`` syntax may be used as it is with " +"(:ref:`gdal_translate`). The option ``scale=true`` (default if " +"unspecified is ``scale=false``) may also be used without value arguments " +"(added in GDAL 3.8), where it results in the output range 0,255 from " +"whatever the source range is. Do consider the need for also using ``ot`` " +"option in order to accommodate the intended output range." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2031 +msgid "" +"The effect of the ``exponent`` option (added in GDAL 3.7) is to apply " +"non-linear scaling with a power function, a single value to be used with " +"the ``scale`` option. The same ``exponent_bn`` syntax may be used in " +"combination with ``scale_bn`` to target specific band/s as per " +"(:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2035 +msgid "" +"The effect of the ``outsize`` option (added in GDAL 3.7) is to set the " +"size of the output, in numbers `pixel,line` or in fraction `pixel%,line%`" +" as per (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2037 +msgid "" +"The effect of the ``projwin`` option (added in GDAL 3.8) is to select a " +"subwindow from the source image in georeferenced coordinates in the same " +"way as (:ref:`gdal_translate`). The value consists of four numeric values" +" separated by commas, in the order 'xmin,ymax,xmax,ymin', these are in " +"the native georeferenced coordinates of the source unless ``projwin_srs``" +" is also provided." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2042 +msgid "" +"The effect of the ``projwin_srs`` option (added in GDAL 3.8) is to " +"specify the SRS in which to interpret the coordinates given with " +"``projwin`` in the same way as (:ref:`gdal_translate`). This option only " +"applies if ``projwin`` is also supplied." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2044 +msgid "" +"The effect of the ``tr`` option (added in GDAL 3.8) is to set the target " +"resolution, two positive values in georeferenced coordinates, applied in " +"the same way as (:ref:`gdal_translate`). The value consists of two " +"numeric values separated by commas in the order 'xres,yres'." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2046 +msgid "" +"The effect of the ``r`` option (added in GDAL 3.8) is to set the " +"resampling algorithm used, with 'nearest' as the default. This is applied" +" in the same way as (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2048 +msgid "" +"The effect of the ``srcwin`` option (added in GDAL 3.8) is to select a " +"subwindow from the source image based on pixel/line location as with " +"(:ref:`gdal_translate`). The value consists of four integer values " +"separated by commas, in the order 'xoff,yoff,xsize,ysize'." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2051 +msgid "" +"The effect of the ``a_gt`` option (added in GDAL 3.8) is to " +"override/assign the geotransform of the output as with " +"(:ref:`gdal_translate`). The value consists of six numeric values " +"separated by commas, in the order 'gt(0),gt(1),gt(2),gt(3),gt(4),gt(5)'." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2054 +msgid "" +"The effect of the ``oo`` option (added in GDAL 3.8) is to set driver-" +"specific dataset open options, multiple values are allowed. The value " +"consists of string key value pairs with multiple pairs separated by " +"commas e.g. ``oo==`` or . " +"``oo==,=,...``. This is applied in the same way " +"as (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2057 +msgid "" +"The effect of the ``unscale`` option (added in GDAL 3.8) is to apply the " +"scale/offset metadata for the bands to convert scaled values to unscaled " +"values. To apply this use syntax ``unscale=true``, or ``unscale=false`` " +"(which is the default if not specified). Do consider the need for also " +"using ``ot`` option in order to accommodate the intended output range, " +"see more details for the same argument as with (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2059 +msgid "" +"The effect of the ``a_coord_epoch`` option (added in GDAL 3.8) is to " +"assign a coordinate epoch, linked with the output SRS as with " +"(:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2062 +msgid "" +"The effect of the ``nogcp`` option (added in GDAL 3.8) is to not copy the" +" GCPs in the source dataset to the output dataset " +"(:ref:`gdal_translate`). To apply this use syntax ``nogcp=true``, or " +"``nogcp=false`` (which is the default if not specified)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2065 +msgid "" +"The effect of the ``epo`` option (added in GDAL 3.8) is that ``srcwin`` " +"or ``projwin`` values that fall partially outside the source raster " +"extent will be considered as an error as per (:ref:`gdal_translate`). To " +"apply this use syntax ``epo=true``, or ``epo=false`` (which is the " +"default if not specified)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2067 +msgid "" +"The effect of the ``eco`` option (added in GDAL 3.8) is that ``srcwin`` " +"or ``projwin`` values that fall completely outside the source raster " +"extent will be considered as an error as per (:ref:`gdal_translate`). To " +"apply this use syntax ``eco=true``, or ``eco=false`` (which is the " +"default if not specified)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2069 +msgid "" +"The effect of the ``sd_name`` option (added in GDAL 3.9) is to choose an " +"individual subdataset by name for sources that have multiple subdatasets." +" This means that rather than a fully-qualified description such as " +"\"NETCDF:myfile.nc:somearray\" we may use " +"\"vrt://myfile.nc?sd_name=somearray\". This option is mutually exclusive " +"with ``sd``." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2074 +msgid "" +"The effect of the ``sd`` option (added in GDAL 3.9) is to choose an " +"individual subdataset by number for sources that have multiple " +"subdatasets. This means that rather than a fully-qualified description " +"such as \"NETCDF:myfile.nc:somearray\" we may use " +"\"vrt://myfile.nc?sd=\" where \"\" is between 1 and the number of " +"subdatasets. Note that there is no guarantee of the order of the " +"subdatasets within a source between GDAL versions (or in some cases " +"between file series in datasets). This mode is for convenience only, " +"please use ``sd_name`` to choose a subdataset by name explicitly. This " +"option is mutually exclusive with ``sd_name``." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2083 +msgid "" +"The options may be chained together separated by '&'. (Beware the need " +"for quoting to protect the ampersand)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2093 +msgid "Multi-threading optimizations" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2095 +msgid "" +"Starting with GDAL 3.6, the ComputeStatistics() implementation can " +"benefit from multi-threading if the sources are not overlapping and " +"belong to different datasets. This can be enabled by setting the " +":config:`GDAL_NUM_THREADS` configuration option to an integer or " +"``ALL_CPUS``." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2101 +msgid "Multi-threading issues" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2105 +msgid "" +"The below section applies to GDAL <= 2.2. Starting with GDAL 2.3, the use" +" of VRT datasets is subject to the standard GDAL dataset multi-threaded " +"rules (that is a VRT dataset handle may only be used by a same thread at " +"a time, but you may open several dataset handles on the same VRT file and" +" use them in different threads)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2111 +msgid "" +"When using VRT datasets in a multi-threading environment, you should be " +"careful to open the VRT dataset by the thread that will use it " +"afterwards. The reason for that is that the VRT dataset uses " +":cpp:func:`GDALOpenShared` when opening the underlying datasets. So, if " +"you open twice the same VRT dataset by the same thread, both VRT datasets" +" will share the same handles to the underlying datasets." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2118 +msgid "" +"The shared attribute, on the SourceFilename indicates whether the dataset" +" should be shared (value is 1) or not (value is 0). The default is 1. If " +"several VRT datasets referring to the same underlying sources are used in" +" a multithreaded context, shared should be set to 0. Alternatively, the " +":config:`VRT_SHARED_SOURCE` configuration option can be set to ``NO`` to " +"force non-shared mode:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2134 +msgid "Performance considerations" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2136 +msgid "" +"A VRT can reference many (hundreds, thousands, or more) datasets. Due to " +"operating system limitations, and for performance at opening time, it is " +"not reasonable/possible to open them all at the same time. GDAL has a " +"\"pool\" of datasets opened by VRT files whose maximum limit is 100 by " +"default. When it needs to access a dataset referenced by a VRT, it checks" +" if it is already in the pool of open datasets. If not, when the pool has" +" reached its limit, it closes the least recently used dataset to be able " +"to open the new one. This maximum limit of the pool can be increased by " +"setting the :config:`GDAL_MAX_DATASET_POOL_SIZE` configuration option to " +"a bigger value. Note that a typical user process on Linux is limited to " +"1024 simultaneously opened files, and you should let some margin for " +"shared libraries, etc... gdal_translate and gdalwarp, by default, " +"increase the pool size to 450." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2149 +msgid "" +"Starting with GDAL 3.7, the :config:`GDAL_MAX_DATASET_POOL_RAM_USAGE` " +"configuration option to a number of bytes, to limit the RAM usage of " +"opened datasets in the pool." +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:9 +msgid "" +"Multidimensional VRT is a specific variant of the :ref:`raster.vrt` " +"format, dedicated to represent Multidimensional arrays, according to the " +":ref:`multidim_raster_data_model`." +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:13 +msgid "Here's an example of such a file:" +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:39 +msgid "" +"A `XML schema of the GDAL VRT format " +"`_ " +"is available." +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:45 +msgid "" +"**VRTDataset**: This is the root element for the whole GDAL dataset. It " +"has no attributes, and must have a single Group child element with an " +"attribute name set to \"/\"" +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:55 +msgid "" +"**Group**: This represents a :cpp:class:`GDALGroup`. There is at least " +"one root group of name \"/\" immediately under the VRTDataset element. A " +"Group must have a *name* attribute, and may have the following child " +"elements, with 0:n multiplicity: Dimension, Attribute, Array, Group" +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:60 +msgid "" +"**Dimension**: This represents a :cpp:class:`GDALDimension`. It has the " +"following attributes: *name* (required), *size* (required), *type* and " +"*direction*" +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:68 +msgid "" +"**Attribute**: This represents a :cpp:class:`GDALAttribute`. It must have" +" a *name* attribute and a child *DataType* element. Attribute values are " +"stored in one or several child *Value* element(s)" +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:72 +msgid "" +"The value of *DataType* may be: String, Byte, UInt16, Int16, UInt32, " +"Int32, Float32, Float64, CInt16, CInt32, CFloat32 or CFloat64." +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:83 +msgid "" +"**Array**: This represents a :cpp:class:`GDALMDArray`. It must have a " +"*name* attribute and a child *DataType* element. It may have 0 or more " +"*DimensionRef* or *Dimension* child elements to define its dimensions. " +"And the following elements may be optionally specified to define its " +"properties. *SRS, *Unit*, *NoDataValue*, *Offset* and *Scale*. To define " +"its values, it may have one *RegularlySpacedValues* element, or zero, one" +" or several elements among *ConstantValue*, *InlineValues*, " +"*InlineValuesWithValueElement* or *Source*." +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:129 +msgid "" +"**Source**: This indicates that raster data should be read from a " +"separate dataset. A Source must have a *SourceFilename*, and either a " +"*SourceArray* (when the source is a Multidimensional dataset), or a " +"*SourceBand* (when the source is a classic 2D dataset) child element. It " +"may have a *SourceTranspose* child element to apply a " +":cpp:func:`GDALMDArray::Transpose` operation and a *SourceView* to apply " +"slicing/trimming operations or extraction of a component of a compound " +"data type (see :cpp:func:`GDALMDArray::GetView`). It may have a " +"*SourceSlab* element with attributes *offset*, *count* and *step* " +"defining respectively the starting offset of the source, the number of " +"values along each dimension and the step between source elements. It may " +"have a *DestSlab* element with an *offset* attribute to define where the " +"source data is placed into the target array. SourceSlab operates on the " +"output of SourceView if specified, which operates itself on the output of" +" SourceTranspose if specified." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:5 +msgid "VRT processed dataset" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:12 +msgid "" +"The following built-in algorithms are introduced, and may typically be " +"applied in the following order:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:15 +msgid "" +"LocalScaleOffset: apply per-pixel gain and offset coming (typically " +"subsampled) from auxiliary datasets. Can be used for dehazing processing." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:18 +msgid "" +"BandAffineCombination: perform an affine transformation combination of " +"bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:20 +msgid "Trimming: apply local thresholding of saturation" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:22 +msgid "LUT: apply a look-up table (band per band)" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:24 +msgid "" +"More algorithms can be registered at run-time with the " +":cpp:func:`GDALVRTRegisterProcessedDatasetFunc` function`" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:27 +msgid "" +"Here's an example of such a file to apply various correction to a " +"R,G,B,NIR dataset:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:116 +msgid ".vrt format" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:118 +msgid "" +"The ``VRTDataset`` root element must have a " +"``subClass=\"VRTProcessedDataset\"`` attribute." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:120 +msgid "" +"The following child elements of ``VRTDataset`` may be defined: ``SRS``, " +"``GeoTransform``, ``Metadata``. If they are not explicitly set, they are " +"inferred from the input dataset." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:122 +msgid "" +"``VRTRasterBand`` elements may be explicitly defined, in particular if " +"the data type of the virtual dataset after all processing steps is " +"different from the input one, or if the number of output bands is " +"different from the number of input bands. If there is no explicit " +"``VRTRasterBand`` element, the number and data types of input bands are " +"used implicitly. When explicitly defined, ``VRTRasterBand`` elements must" +" have a ``subClass=\"VRTProcessedRasterBand\"`` attribute. ` It must also" +" have the 2 following child elements:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:126 +msgid "" +"``Input``, which must have one and only one of the following " +"``SourceFilename`` or ``VRTDataset`` as child elements, to define the " +"input dataset to which to apply the processing steps." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:128 +msgid "``ProcessingSteps``, with at least one child ``Step`` element." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:130 +msgid "" +"Each ``Step`` must have a ``Algorithm`` child element, and an optional " +"``name`` attribute. The value of ``Algorithm`` must be a registered " +"VRTProcessedDataset function. At time of writing, the following 4 " +"algorithms are defined: ``LocalScaleOffset``, ``BandAffineCombination``, " +"``Trimming`` and ``LUT``." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:133 +msgid "" +"A ``Step`` will generally have one or several ``Argument`` child " +"elements, some of them being required, others optional. Consult the " +"documentation of each algorithm." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:136 +msgid "LocalScaleOffset algorithm" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:138 +msgid "" +"Apply per-pixel gain and offset coming (typically subsampled) from " +"auxiliary datasets. Can be used for dehazing processing." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:141 +msgid "" +"The gain and offset auxiliary datasets must have a georeferencing " +"consistent of the input dataset, but may have a different resolution." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:144 +msgid "" +"The formula applied by that algorithm is: ``output_value = " +"clamp(input_value * gain - offset, min, max)``" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:146 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:222 +msgid "The following required arguments must be specified:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:148 +msgid "" +"``gain_dataset_filename_{band}``: Filename to the gain dataset, where " +"{band} must be replaced by 1 to the number of input bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:150 +msgid "" +"``gain_dataset_band_{band}``: Band number corresponding to " +"``gain_dataset_filename_{band}``, where {band} must be replaced by 1 to " +"the number of input bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:152 +msgid "" +"``offset_dataset_filename_{band}``: Filename to the offset dataset, where" +" {band} must be replaced by 1 to the number of input bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:154 +msgid "" +"``offset_dataset_band_{band}``: Band number corresponding to " +"``offset_dataset_filename_{band}``, where {band} must be replaced by 1 to" +" the number of input bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:157 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:182 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:233 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:265 +msgid "The following optional arguments may be specified:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:159 +msgid "" +"``relativeToVRT``: Whether gain and offset filenames are relative to the " +"VRT. Allowed values are ``true`` and ``false``. Defaults to ``false``" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:161 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:192 +msgid "``min``: Clamp minimum value, applied before writing the output value." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:163 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:194 +msgid "``max``: Clamp maximum value, applied before writing the output value." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:165 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:243 +msgid "" +"``nodata``: Override the input nodata value coming from the previous step" +" (or the input dataset for the first step)." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:167 +msgid "" +"``gain_nodata``: Override the nodata value coming from the gain " +"dataset(s)." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:169 +msgid "" +"``offset_nodata``: Override the nodata value coming from the offset " +"dataset(s)." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:173 +msgid "BandAffineCombination algorithm" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:175 +msgid "Perform an affine transformation combination of bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:177 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:253 +msgid "The following required argument must be specified:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:179 +msgid "" +"``coefficients_{band}``: Comma-separated coefficients for combining bands" +" where {band} must be replaced by 1 to the number of output bands. The " +"number of coefficients in each argument must be 1 + " +"number_of_input_bands, where the first coefficient is a constant, the " +"second coefficient is the weight of the first input band, the third " +"coefficient is the weight of the second input band, etc." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:184 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:267 +msgid "" +"``src_nodata``: Override the input nodata value coming from the previous " +"step (or the input dataset for the first step)." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:186 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:269 +msgid "``dst_nodata``: Set the output nodata value." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:188 +msgid "" +"``replacement_nodata``: Value to substitute to a valid computed value " +"that would be equal to dst_nodata." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:190 +msgid "" +"``dst_intended_datatype``: Intended datatype of output (which might be " +"different than the working data type). Used to infer an appropriate value" +" for replacement_nodata when it is not specified." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:198 +msgid "Trimming algorithm" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:200 +msgid "" +"Apply local thresholding of saturation, with a special processing of the " +"R,G,B bands compared to other bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:202 +msgid "The pseudo algorithm used for each pixel is:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:224 +msgid "" +"``trimming_dataset_filename``: Filename of the trimming dataset. It must " +"have one single band. It must have a georeferencing consistent of the " +"input dataset, but may have a different resolution." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:226 +msgid "``top_rgb``: Maximum saturating RGB output value." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:228 +msgid "``tone_ceil``: Maximum threshold beyond which we give up saturation." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:230 +msgid "" +"``top_margin``: Margin to allow for dynamics in brighest areas (between 0" +" and 1, should be close to 0)" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:235 +msgid "" +"``relativeToVRT``: Whether the trimming dataset filename is relative to " +"the VRT. Allowed values are ``true`` and ``false``. Defaults to ``false``" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:237 +msgid "``red_band``: Index (one-based) of the red band. Defaults to 1." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:239 +msgid "``green_band``: Index (one-based) of the green band. Defaults to 1." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:241 +msgid "``blue_band``: Index (one-based) of the blue band. Defaults to 1." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:245 +msgid "" +"``trimming_nodata``: Override the nodata value coming from the trimming " +"dataset." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:249 +msgid "LUT" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:251 +msgid "" +"Apply a look-up table (band per band), typically to get from UInt16 to " +"Byte data types." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:255 +msgid "" +"``lut_{band}``: List of the form ``[src value 1]:[dest value 1],[src " +"value 2]:[dest value 2],....``. {band} must be replaced by 1 to the " +"number of bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:257 +msgid "" +"The intermediary values are calculated using a linear interpolation " +"between the bounding destination values of the corresponding range. " +"Source values should be monotonically non-decreasing. Clamping is " +"performed for input pixel values outside of the range specified by the " +"LUT. That is, if an input pixel value is lower than the minimum source " +"value, then the destination value corresponding to that minimum source " +"value is used as the output pixel value. And similarly for an input pixel" +" value that is greater than the maximum source value." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:5 +msgid "WCS -- OGC Web Coverage Service" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:7 +msgid "WCS" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:11 +msgid "" +"The optional GDAL WCS driver allows use of a coverage in a WCS server as " +"a raster dataset. GDAL acts as a client to the WCS server." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:14 +msgid "" +"Accessing a WCS server is accomplished by creating a local service " +"description file that contains one `` XML element. It is " +"important that there is no spaces or other content outside that element. " +"Starting at version 2.3 the service description file is meant to be " +"managed by the driver in a cache directory. User should control the " +"contents of the service file using options. The dataset name is " +":samp:`WCS:`, where the is the URL of the server appended " +"potentially appended with WCS version, coverage, and possibly other " +"parameters. If the WCS version is 2.0.1 further parameters can be given " +"to control how the data model of the coverage is mapped to the GDAL data " +"model." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:26 +msgid "" +"If the URL does not contain a coverage name, the driver attempts to fetch" +" the capabilities document from the server, parse it, and show the " +"resulting metadata to the user. Coverages are shown as subdatasets. If " +"the URL contains a coverage name as parameter (the key 'coverage' can be " +"used irrespective of the WCS version), the driver attempts to fetch the " +"coverage description document from the server, parse it, and create " +"service description file. A small test GetCoverage request may be done to" +" obtain details of the served data. If the respective server capabilities" +" file is not cached, it will also be fetched." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:36 +msgid "" +"With service version 2.0.1 (for which support is available starting at " +"GDAL version 2.3), it may be that the coverage has more than two " +"dimensions. In that case, the driver will append the coverage metadata " +"and show zero bands. At that point, the user must use options to further " +"instruct the driver how to deal with extra dimensions and data fields." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:42 +msgid "" +"The WCS driver supports WCS versions 1.0.0, 1.1.0, 1.1.1, 1.1.2, and " +"2.0.1 at basic level (version 0.7 is not supported and support for " +"version 2.0.1 is available starting at GDAL 2.3). Any return format that " +"is a single file, and is in a format supported by GDAL should work. The " +"driver will prefer a format with \"tiff\" in the name, otherwise it will " +"fallback to the first offered format. However, the user may set the " +"preferred format. Coordinate systems are read from the DescribeCoverage " +"result." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:59 +msgid "Service description file" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:61 +msgid "" +"The service description file has the following elements as immediate " +"children of the document element. Note that when the \"WCS:\" syntax" +" for dataset name is used, the contents of the service description file " +"is meant to be modified by using options." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:66 +msgid "**ServiceURL**: URL of the service without parameters" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:67 +msgid "" +"**Version**: The WCS version that is used in the communication. If the " +"dataset name syntax WCS:URL is used the default is 2.0.1 and the server's" +" response may change the user request, otherwise defaults to 1.0.0. " +"Versions 1.0.0, 1.1.0, 1.1.1, 1.1.2, and 2.0.1 are supported." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:71 +msgid "**CoverageName**: The coverage that is used for the dataset." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:72 +msgid "" +"**Format**: The format to use for GetCoverage calls. If not set, selected" +" by the driver. (WCS version 2.0)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:74 +msgid "" +"**PreferredFormat**: The format to use for GetCoverage calls. If not set," +" selected by the driver. (WCS versions 1.0 and 1.1)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:76 +msgid "" +"**Interpolation**: The interpolation method used when scaling. Should be " +"one of the server supported values. (GDAL 2.3)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:78 +msgid "**BlockXSize**: The block width to use for block cached remote access." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:80 +msgid "**BlockYSize**: The block height to use for block cached remote access." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:82 +msgid "" +"**OverviewCount**: The number of overviews to represent bands as having. " +"Defaults to a number such that the top overview is fairly smaller (less " +"than 1K x 1K or so)." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:85 +msgid "" +"**NoDataValue**: The nodata value to use for all the bands (blank for " +"none). Normally determined by the driver. With version 2.0.1 this may be " +"a comma separated list of values, one for each band." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:88 +msgid "**Elements for controlling the range and domain:**" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:89 +msgid "" +"**Domain**: The axes that are used for the spatial dimensions. The " +"default is to use the first two axes given by the server. The axis order " +"swap may apply. Syntax: *axis_name,axis_name* A *field_name:field_name* " +"in the list denotes a range of fields. (Used only with version 2.0.1)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:94 +msgid "" +"**DefaultTime**: A timePosition to use by default when accessing " +"coverages with a time dimension. Populated with the last offered time " +"position by default. (Used only with version 1.0.0)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:97 +msgid "" +"**FieldName**: Name of the field being accessed. Used only with version " +"1.1. Defaults to the first field in the DescribeCoverage. In version 1.1 " +"the range consists of one or more fields, which may be scalar or vector. " +"A vector field contains one or more bands." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:101 +msgid "" +"**BandCount**: Number of bands in the dataset, normally determined by the" +" driver." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:103 +msgid "" +"**BandType**: The pixel data type to use. Normally determined by the " +"driver." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:105 +msgid "**Elements for controlling the communication:**" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:106 +#: ../../source/drivers/vector/wfs.rst:67 +msgid "" +"**Timeout**: The timeout to use for remote service requests. If not " +"provided, the libcurl default is used." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:108 +#: ../../source/drivers/vector/wfs.rst:69 +msgid "" +"**UserPwd**: May be supplied with *userid:password* to pass a userid and " +"password to the remote server." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:110 +#: ../../source/drivers/vector/wfs.rst:71 +msgid "" +"**HttpAuth**: May be BASIC, NTLM or ANY to control the authentication " +"scheme to be used." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:112 +msgid "" +"**GetCoverageExtra**: An additional set of keywords to add to GetCoverage" +" requests in URL encoded form. eg. \"&RESAMPLE=BILINEAR&Band=1\". Note " +"that the extra parameters should not be known parameters (see below)." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:116 +msgid "" +"**DescribeCoverageExtra**: An additional set of keywords to add to " +"DescribeCoverage requests in URL encoded form. eg. \"&CustNo=775\"" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:118 +msgid "" +"**Elements that may be needed to deal with server quirks (GDAL 2.3):** " +"**Note:** The options are not propagated to the subdataset with the " +"switch -sd." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:122 +msgid "" +"**OriginAtBoundary**: Set this flag if the server reports grid origin to " +"be at the pixel boundary instead of the pixel center. (Use for MapServer " +"versions <= 7.0.7 with WCS versions 1.0.0 and 2.0.1)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:125 +msgid "" +"**OuterExtents**: Set to consider WCS 1.1 extents as boundaries of outer " +"pixels instead of centers of outer pixels. (Use for GeoServer)." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:127 +msgid "" +"**BufSizeAdjust**: Set to 0.5 in WCS 1.1 if data access fails due to the " +"response not having expected size. (Use for GeoServer)." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:129 +msgid "" +"**OffsetsPositive**: Use with MapServer in WCS version 2.0.1 together " +"wwith NrOffsets." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:131 +msgid "" +"**NrOffsets**: Set to 2 if the server requires that there are only two " +"values in the GridOffsets. Use when the server is MapServer or ArcGIS. " +"With MapServer use also OffsetsPositive." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:134 +msgid "" +"**GridCRSOptional**: Let the driver skip Grid\\* parameters from a WCS " +"1.1 GetCoverage request if the request is not scaled. Do not use for " +"GeoServer." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:137 +msgid "" +"**NoGridAxisSwap**: Set to tell the driver not to swap axis order. When " +"reading the grid geometry (in WCS 1.1 the origin and offsets, in WCS " +"2.0.1 the grid envelope, axis labels, and offsets) no axis order swap is " +"done although it would otherwise be done if this flag is set. In 1.1 it " +"would be done if the CRS has inverted axes. In 2.0.1 it would be done if " +"the axisOrder of the sequenceRule in GridFunction defines so. This is " +"needed usually both in 1.1 and 2.0.1 when parsing coverage descriptions " +"from MapServer and GeoServer." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:145 +msgid "" +"**SubsetAxisSwap** Set to tell the driver to swap the axis names in " +"boundedBy.Envelope.axisLabels when making WCS 2.0.1 GetCoverage request. " +"Needed for GeoServer when EPSG dictates axis order swap." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:148 +msgid "" +"**UseScaleFactor**: Set to tell the driver to use scale by factor " +"approach instead of scale to size when making a WCS 2.0.1 GetCoverage " +"request. Required when the server is ArcGIS." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:153 +msgid "Range and dimension subsetting" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:155 +msgid "" +"When WCS version 2.0.1 is used, the range (fields/bands) and the " +"dimension can and/or may need to be subsetted. If the data model of the " +"coverage contains dimensions beyond the two geographic or map " +"coordinates, those dimensions must be sliced for GDAL. The coverage may " +"also contain a large number of fields, from which only a subset is wanted" +" in the GDAL dataset." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:162 +msgid "" +"Range and dimension subsetting must be done via URL parameters since from" +" one coverage it is possible to create more than one different GDAL " +"datasets. In the WCS cache this means that there may be the sets of files" +" related to a GDAL dataset:" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:167 +msgid "" +"server Capabilities file and a GDAL dataset metadata file made from it " +"(key = URL with WCS version number)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:169 +msgid "" +"server DescribeCoverage file, a template GDAL service file made from it, " +"and a GDAL dataset metadata file made for it (key = URL with WCS version " +"number and coverage name)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:172 +msgid "" +"the GDAL service file specifically for this dataset, and a GDAL dataset " +"metadata file (key = URL with WCS version number, coverage name, and " +"range and dimension subsetting parameters)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:176 +msgid "" +"The following URL parameters are used to control the range and dimension " +"subsetting. Note that these can also be set through options into the " +"service file. The ones in URL take precedence." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:180 +msgid "" +"**RangeSubset**: Used to select a subset of coverage fields to the " +"dataset. Syntax: *field_name,field_name:field_name,..* (Note: requires " +"that the server implements the range subsetting extension.)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:183 +msgid "" +"**Subset**: Trim or slice a dimension when fetching data from the server." +" Syntax: " +"*axis_name(trim_begin_value,trim_end_value);axis_name(slice_value)* Note " +"that trimming the geographic/map coordinates is done by the driver." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:190 +msgid "Other WCS parameters" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:192 +msgid "" +"The following WCS (version 2.0.1) parameters are recognized besides what " +"has been described above. These all can be set either through options or " +"directly into the URL. The ones in URL take precedence. Note that it is " +"up to the server to support/recognize these." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:197 +msgid "MediaType" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:198 +msgid "UpdateSequence" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:199 +msgid "GEOTIFF:COMPRESSION" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:200 +msgid "GEOTIFF:JPEG_QUALITY" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:201 +msgid "GEOTIFF:PREDICTOR" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:202 +msgid "GEOTIFF:INTERLEAVE" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:203 +msgid "GEOTIFF:TILING" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:204 +msgid "GEOTIFF:TILEWIDTH" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:209 +msgid "" +"When the \"WCS:\" dataset name syntax is used, open options are used" +" to control the driver and the contents of the service description file. " +"In the case the URL does not contain coverage name, the service " +"description file is not used and thus in that case the options are not " +"written into it. Open options are given separate to the dataset name, " +"with GDAL utility programs they are given using the -oo switch (`-oo " +"\"NAME=VALUE\"`). The -oo switch expects only one option but more options" +" can be given repeating the switch." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:218 +msgid "" +"In addition to DescribeCoverageExtra and GetCoverageExtra, which are " +"stored in the service description file, there is also " +"GetCapabilitiesExtra, which can be used as an open option when requesting" +" the overall capabilities from the server. The open option " +"SKIP_GETCOVERAGE can be used to prevent the driver making a GetCoverage " +"request to the server, which it usually does if it can't determine the " +"band count and band data type from the capabilities or coverage " +"descriptions. This option may be needed if GetCoverage request fails." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:227 +msgid "" +"All above listed element names can be given as options to the WCS driver." +" In the case of flags the option should formally be \"Name=TRUE\", but " +"only \"Name\" suffices." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:232 +msgid "The cache" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:234 +msgid "" +"When the \"WCS:\" dataset name syntax is used, the server responses," +" the service description file, and the metadata files are stored in a " +"cache. Generally, if the needed resource is in the cache, it will be used" +" and no extra calls to the server are done." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:239 +msgid "The default location of the cache directory is $HOME/.gdal/wcs_cache" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:241 +msgid "The cache contents can be seen as subdatasets using an empty URL:" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:247 +msgid "The cache control options/flags are" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:249 +msgid "**CACHE=path** Overrides the default cache location." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:250 +msgid "" +"**CLEAR_CACHE** The cache is completely initialized and all files are " +"deleted." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:252 +msgid "" +"**REFRESH_CACHE** The cache entry, either capabilities or coverage, " +"depending on the call at hand, is deleted." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:254 +msgid "**DELETE_FROM_CACHE=k** The cache entry (subdataset k), is deleted." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:257 +msgid "The WCS: dataset name syntax" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:259 +msgid "" +"The URL in the dataset name is not a complete WCS request URL. The " +"request URL, specifically, its query part, for GetCapabilities, " +"DescribeCoverage, and GetCoverage requests is composed by the driver. " +"Typically the user should only need to add to the server address the " +"version and coverage parameters. The string 'coverage' can be used as the" +" coverage parameter key although different WCS versions use different " +"keys. 'coverage' is also always used in the cache key." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:267 +msgid "" +"The user may add arbitrary standard and non-standard extra parameters to " +"the URL. However, when that is done, it should be noted that the URL is a" +" cache database key and capability documents are linked to coverage " +"documents through the key. Please consider using the Extra open options." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:273 +msgid "Time" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:275 +msgid "" +"This driver includes experimental support for time based WCS 1.0.0 " +"servers. On initial access the last offered time position will be " +"identified as the DefaultTime. Each time position available for the " +"coverage will be treated as a subdataset." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:280 +msgid "" +"Note that time based subdatasets are not supported when the service " +"description is the filename. Currently time support is not available for " +"versions other than WCS 1.0.0." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:287 +msgid "A gdalinfo call to a coverage served by MapServer:" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:299 +msgid "A gdal_translate call to a scaled clip of a coverage served by GeoServer:" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:317 +msgid "`OGC WCS Standards `__" +msgstr "" + +#: ../../source/drivers/raster/webp.rst:5 +msgid "WEBP - WEBP" +msgstr "" + +#: ../../source/drivers/raster/webp.rst:11 +msgid "GDAL can read and write WebP images through the WebP library." +msgstr "" + +#: ../../source/drivers/raster/webp.rst:14 +msgid "" +"WebP is a new image format that provides lossy compression for " +"photographic images. A WebP file consists of VP8 image data, and a " +"container based on RIFF." +msgstr "" + +#: ../../source/drivers/raster/webp.rst:18 +msgid "" +"The driver rely on the Open Source WebP library (BSD licensed). The WebP " +"library (at least in its version 0.1) only offers compression and " +"decompression of whole images, so RAM might be a limitation when dealing " +"with big images (which are limited to 16383x16383 pixels)." +msgstr "" + +#: ../../source/drivers/raster/webp.rst:23 +msgid "" +"The WEBP driver supports 3 bands (RGB) images. It also supports 4 bands " +"(RGBA)" +msgstr "" + +#: ../../source/drivers/raster/webp.rst:25 +msgid "" +"The WEBP driver can be used as the internal format used by the " +":ref:`raster.rasterlite` driver." +msgstr "" + +#: ../../source/drivers/raster/webp.rst:41 +msgid "Various creation options exists, among them :" +msgstr "" + +#: ../../source/drivers/raster/webp.rst:74 +msgid "`WebP home page `__" +msgstr "" + +#: ../../source/drivers/raster/wld.rst:5 +msgid "WLD -- ESRI World File" +msgstr "" + +#: ../../source/drivers/raster/wld.rst:7 +msgid "" +"A world file file is a plain ASCII text file consisting of six values " +"separated by newlines. The format is:" +msgstr "" + +#: ../../source/drivers/raster/wld.rst:30 +msgid "You can construct that file simply by using your favorite text editor." +msgstr "" + +#: ../../source/drivers/raster/wld.rst:32 +msgid "" +"World file usually has suffix ``.wld``, but sometimes it may has " +"``.tfw``, ``.tifw``, ``.jgw`` or other suffixes depending on the image " +"file it comes with." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:5 +msgid "WMS -- Web Map Services" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:7 +#: ../../source/drivers/raster/wms.rst:105 +msgid "WMS" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:11 +msgid "" +"Accessing several different types of web image services is possible using" +" the WMS format in GDAL." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:24 +msgid "XML description file" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:26 +msgid "" +"Services are accessed by creating a local service description XML file --" +" there are examples below for each of the supported image services. It is" +" important that there be no spaces or other content before the " +"```` element." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:32 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:33 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:33 +msgid "" +"Define what mini-driver to use, currently supported are: WMS, WorldWind, " +"TileService, TMS, TiledWMS, VirtualEarth or AGS. (required)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:34 +msgid "1.1.1" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:34 +msgid "WMS version. (optional, defaults to 1.1.1)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:35 +msgid "http://host.domain.com/wms.cgi?" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:35 +msgid "WMS server URL. (required)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:36 +msgid "EPSG:4326" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:36 +msgid "" +"Image projection (optional, defaults to EPSG:4326 in WMS and 102100 in " +"AGS, WMS version 1.1.1 or below only and ArcGIS Server). For ArcGIS " +"Server the spatial reference can be specified as either a well-known ID " +"or as a `spatial reference json object " +"`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:37 +msgid "CRS:83" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:37 +msgid "" +"Image projection (optional, defaults to EPSG:4326, WMS version 1.3.0 or " +"above only)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:38 +msgid "image/jpeg" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:38 +msgid "" +"Format in which to request data. Paletted formats like image/gif will be " +"converted to RGB. (optional, defaults to image/jpeg)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:39 +msgid "FALSE" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:39 +msgid "" +"Set to TRUE to include \"transparent=TRUE\" in the WMS GetMap request " +"(optional defaults to FALSE).  The request format and BandsCount need to " +"support alpha." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:40 +msgid "modis%2Cglobal_mosaic" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:40 +msgid "" +"A URL encoded, comma separated string of layers (required, except for " +"TiledWMS)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:41 +msgid "Clementine" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:41 +msgid "Comma separated list of layers. (required for TiledWMS)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:42 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:42 +msgid "Comma separated list of styles. (optional)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:43 +msgid "xyXY" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:43 +msgid "" +"Reorder bbox coordinates arbitrarily. May be required for version 1.3 " +"servers. (optional) x - low X coordinate, y - low Y coordinate, X - high " +"X coordinate, Y - high Y coordinate" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:45 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:46 +#: ../../source/drivers/raster/wmts.rst:239 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:46 +msgid "" +"Define size and extents of the data. (required, except for TiledWMS and " +"VirtualEarth)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:47 +#: ../../source/drivers/raster/wmts.rst:248 +msgid "-180.0" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:47 +msgid "" +"X (longitude) coordinate of upper-left corner. (optional, defaults to " +"-180.0, except for VirtualEarth)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:48 +#: ../../source/drivers/raster/wmts.rst:253 +msgid "90.0" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:48 +msgid "" +"Y (latitude) coordinate of upper-left corner. (optional, defaults to " +"90.0, except for VirtualEarth)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:49 +#: ../../source/drivers/raster/wmts.rst:258 +msgid "180.0" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:49 +msgid "" +"X (longitude) coordinate of lower-right corner. (optional, defaults to " +"180.0, except for VirtualEarth)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:50 +#: ../../source/drivers/raster/wmts.rst:263 +msgid "-90.0" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:50 +msgid "" +"Y (latitude) coordinate of lower-right corner. (optional, defaults to " +"-90.0, except for VirtualEarth)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:51 +msgid "2666666" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:51 +#: ../../source/drivers/raster/wms.rst:52 +msgid "Image size in pixels." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:52 +msgid "1333333" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:53 +msgid "0" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:53 +msgid "" +"Added to tile X value at highest resolution. (ignored for WMS, tiled " +"image sources only, optional, defaults to 0)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:54 +msgid "0" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:54 +msgid "" +"Added to tile Y value at highest resolution. (ignored for WMS, tiled " +"image sources only, optional, defaults to 0)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:55 +msgid "0" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:55 +msgid "" +"Tile level at highest resolution. (tiled image sources only, optional, " +"defaults to 0)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:56 +msgid "0" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:56 +msgid "" +"Can be used to define image size, SizeX = TileCountX \\* BlockSizeX \\* " +"2\\ :sup:`TileLevel`. (tiled image sources only, optional, defaults to 0)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:57 +msgid "0" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:57 +msgid "" +"Can be used to define image size, SizeY = TileCountY \\* BlockSizeY \\* " +"2\\ :sup:`TileLevel`. (tiled image sources only, optional, defaults to 0)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:58 +msgid "top" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:58 +msgid "" +"Can be used to define the position of the Y origin with respect to the " +"tile grid. Possible values are 'top', 'bottom', and 'default', where the " +"default behavior is mini-driver-specific. (TMS mini-driver only, " +"optional, defaults to 'bottom' for TMS)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:59 +#: ../../source/drivers/raster/wmts.rst:268 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:60 +msgid "EPSG:4326" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:60 +msgid "" +"Image projection (optional, defaults to value reported by mini-driver or " +"EPSG:4326)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:61 +msgid "2" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:61 +msgid "Identification tolerance (optional, defaults to 2)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:62 +msgid "3" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:62 +msgid "" +"Number of bands/channels, 1 for grayscale data, 3 for RGB, 4 for RGBA. " +"(optional, defaults to 3)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:63 +#: ../../source/drivers/raster/wmts.rst:279 +msgid "Byte" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:63 +#: ../../source/drivers/raster/wmts.rst:279 +msgid "" +"Band data type, one of: Byte, Int16, UInt16, Int32, UInt32, Float32, " +"Float64, etc.. (optional, defaults to Byte)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:64 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:64 +msgid "" +"Define NoData and/or minimum and/or maximum value for bands. " +"nodata_values, min_values, max_values can be one single value, or a value" +" per band, with a space separator between value" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:65 +msgid "1024" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:65 +#: ../../source/drivers/raster/wms.rst:66 +msgid "" +"Block size in pixels. (optional, defaults to 1024, except for " +"VirtualEarth)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:66 +msgid "1024" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:67 +msgid "10" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:67 +msgid "" +"Count of reduced resolution layers each having 2 times lower resolution. " +"(optional, default is calculated at runtime)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:68 +#: ../../source/drivers/raster/wmts.rst:318 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:68 +msgid "" +"Enable local disk cache. Allows for offline operation. (optional but " +"present in the autogenerated service file, cache is disabled when not " +"present or if it is overridden with GDAL_ENABLE_WMS_CACHE=NO)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:69 +#: ../../source/drivers/raster/wmts.rst:326 +msgid "./gdalwmscache" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:69 +msgid "" +"Location where to store cache files. It is safe to use same cache path " +"for different data sources. /vsimem/ paths are supported allowing for " +"temporary in-memory cache. (optional, cf below Caching section for " +"default value)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:70 +#: ../../source/drivers/raster/wmts.rst:344 +msgid "2" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:70 +#: ../../source/drivers/raster/wmts.rst:344 +msgid "" +"Number of directory layers. 2 will result in files being written as " +"cache_path/A/B/ABCDEF... (optional, defaults to 2)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:71 +#: ../../source/drivers/raster/wmts.rst:350 +msgid ".jpg" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:71 +#: ../../source/drivers/raster/wmts.rst:350 +msgid "Append to cache files. (optional, defaults to none)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:72 +#: ../../source/drivers/raster/wmts.rst:338 +msgid "file" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:72 +#: ../../source/drivers/raster/wmts.rst:338 +msgid "" +"Cache type. Now supported only 'file' type. In 'file' cache type files " +"are stored in file system folders. (optional, defaults to 'file')" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:73 +msgid "604800" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:73 +msgid "" +"Time in seconds cached files will stay valid. If cached file expires it " +"is deleted when maximum size of cache is reached. Also expired file can " +"be overwritten by the new one from web. Default value is 7 days " +"(604800s)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:74 +msgid "67108864" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:74 +msgid "" +"The cache maximum size in bytes. If cache reached maximum size, expired " +"cached files will be deleted. Default value is 64 Mb (67108864 bytes)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:75 +msgid "120" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:75 +msgid "" +"Clean Thread Run Timeout in seconds. How often to run the clean thread, " +"which finds and deletes expired cached files. Default value is 120s. Use " +"value of 0 to disable the Clean Thread (effectively unlimited cache " +"size). If you intend to use very large cache size you might want to " +"disable the cache clean or to use a much longer timeout as the time that " +"takes to scan the cache files for expired cache files might be long. " +"(\"disabled\" was the only option for GDAL <= 2.2; \"120s\" was the only " +"option for 2.3 <= GDAL <= 3.1)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:76 +msgid "True" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:76 +msgid "" +"If set to true the path will appended with md5 hash of ServerURL. Default" +" value is true." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:77 +#: ../../source/drivers/raster/wmts.rst:353 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:78 +msgid "2" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:78 +msgid "" +"Maximum number of simultaneous connections. (optional, defaults to 2). " +"Can also be set with the :config:`GDAL_MAX_CONNECTIONS` configuration " +"option (GDAL >= 3.2)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:79 +#: ../../source/drivers/raster/wmts.rst:359 +msgid "300" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:79 +msgid "" +"Connection timeout in seconds. (optional, defaults to 300 or " +":config:`GDAL_HTTP_TIMEOUT`, if specified)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:80 +#: ../../source/drivers/raster/wmts.rst:362 +msgid "true" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:80 +#: ../../source/drivers/raster/wmts.rst:362 +msgid "" +"Do not download any new images, use only what is in cache. Useful only " +"with cache enabled. (optional, defaults to false)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:81 +msgid "true" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:81 +msgid "" +"Enable AdviseRead API call - download images into cache. (optional, " +"defaults to false)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:82 +msgid "true" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:82 +msgid "" +"Open each downloaded image and do some basic checks before writing into " +"cache. Disabling can save some CPU cycles if server is trusted to always " +"return correct images. (optional, defaults to true)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:83 +msgid "false" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:83 +msgid "" +"Should requests, that otherwise would be partially outside of defined " +"data window, be clipped resulting in smaller than block size request. " +"(optional, defaults to true)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:84 +msgid "GDAL WMS driver (http://www.gdal.org/frmt_wms.html)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:84 +msgid "" +"HTTP User-agent string. Some servers might require a well-known user-" +"agent such as \"Mozilla/5.0\" (optional, defaults to \"GDAL WMS driver " +"(http://www.gdal.org/frmt_wms.html)\"). When used with some servers, like" +" OpenStreetMap ones, it is highly recommended to put a custom user agent " +"to avoid being blocked if the default user agent had to be blocked." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:85 +#: ../../source/drivers/raster/wmts.rst:375 +msgid "mimetype>/Accept>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:85 +msgid "" +"HTTP Accept header to specify the MIME type of the expected output of the" +" server. Empty by default" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:86 +#: ../../source/drivers/raster/wmts.rst:380 +msgid "user:password" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:86 +#: ../../source/drivers/raster/wmts.rst:380 +msgid "User and Password for HTTP authentication (optional)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:87 +#: ../../source/drivers/raster/wmts.rst:383 +msgid "true" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:87 +msgid "" +"Skip SSL certificate verification. May be needed if server is using a " +"self signed certificate (optional, defaults to false)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:88 +msgid "http://example.foo/" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:88 +#: ../../source/drivers/raster/wmts.rst:390 +msgid "HTTP Referer string. Some servers might require it (optional)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:89 +msgid "204,404" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:89 +msgid "" +"Comma separated list of HTTP response codes that will be interpreted as a" +" 0 filled image (i.e. black for 3 bands, and transparent for 4 bands) " +"instead of aborting the request. (optional, defaults to 204)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:90 +msgid "true" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:90 +msgid "" +"Whether to treat a Service Exception returned by the server as a 0 filled" +" image instead of aborting the request. (optional, defaults to false)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:91 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:92 +msgid "\\" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:95 +msgid "" +"Starting with GDAL 2.3, additional HTTP headers can be sent by setting " +"the GDAL_HTTP_HEADER_FILE configuration option to point to a filename of " +"a text file with “key: value” HTTP headers." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:98 +msgid "Minidrivers" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:100 +msgid "" +"The GDAL WMS driver has support for several internal 'minidrivers', which" +" allow access to different web mapping services. Each of these services " +"may support a different set of options in the Service block." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:107 +msgid "" +"Communications with an OGC WMS server. Has support for both tiled and " +"untiled requests." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:110 +msgid "" +"WMS layers can be queried (through a GetFeatureInfo request) with the " +"gdallocationinfo utility, or with a GetMetadataItem(\"Pixel_iCol_iLine\"," +" \"LocationInfo\") call on a band object." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:166 +msgid "TileService" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:168 +msgid "" +"Service to support talking to a WorldWind `TileService " +"`__. Access is always " +"tile based." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:173 +msgid "WorldWind" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:175 +msgid "Access to web-based WorldWind tile services. Access is always tile based." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:179 +msgid "TMS" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:181 +msgid "" +"The TMS Minidriver is designed primarily to support the users of the `TMS" +" Specification " +"`__. This " +"service supports only access by tiles." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:186 +msgid "" +"Because TMS is similar to many other 'x/y/z' flavored services on the " +"web, this service can also be used to access these services. To use it in" +" this fashion, you can use replacement variables, of the format ${x}, " +"${y}, etc." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:191 +msgid "Supported variables (name is case sensitive) are :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:193 +msgid "${x} -- x position of the tile" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:194 +msgid "" +"${y} -- y position of the tile. This can be either from the top or the " +"bottom of the tileset, based on whether the YOrigin parameter is set to " +"true or false." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:197 +msgid "${z} -- z position of the tile -- zoom level" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:198 +msgid "" +"${version} -- version parameter, set in the config file. Defaults to " +"1.0.0." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:200 +msgid "${format} -- format parameter, set in the config file. Defaults to 'jpg'." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:202 +msgid "${layer} -- layer parameter, set in the config file. Defaults to nothing." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:205 +msgid "A typical ServerURL might look like:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:206 +msgid "``http://tilecache.osgeo.org/wms-c/Basic.py/${version}/${layer}/${z}/${x}/${y}.${format}``" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:209 +msgid "" +"In order to better suit TMS users, any URL that does not contain \"${\" " +"will automatically have the string above (after \"Basic.py/\") appended " +"to their URL." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:211 +msgid "" +"The TMS Service has 3 XML configuration elements that are different from " +"other services: ``Format`` which defaults to ``jpg``, ``Layer`` which has" +" no default, and ``Version`` which defaults to ``1.0.0``." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:215 +msgid "" +"Additionally, the TMS service respects one additional parameter, at the " +"DataWindow level, which is the YOrigin element. This element should be " +"one of ``bottom`` (the default in TMS) or ``top``, which matches " +"OpenStreetMap and many other popular tile services." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:220 +msgid "" +"Two examples of usage of the TMS service are included in the examples " +"below." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:224 +msgid "OnEarth Tiled WMS" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:226 +msgid "" +"The OnEarth Tiled WMS minidriver supports the Tiled WMS specification " +"implemented for the JPL OnEarth driver per the specification at " +"http://web.archive.org/web/20130511182803/http://onearth.jpl.nasa.gov/tiled.html." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:230 +msgid "" +"Only the ServerUrl and the TiledGroupName are required, most of the " +"required information is automatically fetched from the remote server " +"using the GetTileService method at open time." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:233 +msgid "A typical OnEarth Tiled WMS configuration file might look like:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:245 +msgid "The TiledWMS minidriver can use the following open options :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:247 +msgid "" +"TiledGroupName -- The value is a string that identifies one of the tiled " +"services available on the server" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:249 +msgid "" +"Change -- A : pair, which will be passed to the server. The " +"key has to match a change key that the server declares for the respective" +" tiled group. This option can be used multiple times, for different keys." +" Example: - Change=time:2020-02-02" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:255 +msgid "" +"These open options are only accepted if the corresponding XML element is " +"not present in the configuration file." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:259 +msgid "VirtualEarth" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:261 +msgid "" +"Access to web-based Virtual Earth tile services. Access is always tile " +"based." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:264 +msgid "The ${quadkey} variable must be found in the ServerUrl element." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:266 +msgid "The DataWindow element might be omitted. The default values are :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:268 +msgid "UpperLeftX = -20037508.34" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:269 +msgid "UpperLeftY = 20037508.34" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:270 +msgid "LowerRightX = 20037508.34" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:271 +msgid "LowerRightY = -20037508.34" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:272 +msgid "TileLevel = 21" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:273 +msgid "OverviewCount = 20" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:274 +msgid "SRS = EPSG:3857" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:275 +msgid "BlockSizeX = 256" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:276 +msgid "BlockSizeY = 256" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:279 +msgid "ArcGIS REST API" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:281 +msgid "" +"Access to ArcGIS REST `map service resource " +"`__ " +"(untiled requests)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:285 +msgid "" +"AGS layers can be `queried " +"`__ " +"(through a GetFeatureInfo request) with the gdallocationinfo utility, or " +"with a GetMetadataItem(\"Pixel_iCol_iLine\", \"LocationInfo\") call on a " +"band object." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:297 +msgid "Internet Imaging Protocol (IIP) (GDAL 2.1 and later)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:299 +msgid "" +"Access to images served through `IIP protocol " +"`__. The server " +"must support the JTL (Retrieve a tile as a complete JFIF image) extension" +" of the IIP protocol." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:304 +msgid "If using the XML syntax, the ServerURL must contain the FIF parameter." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:306 +msgid "" +"Otherwise it is also possible to use " +"\"IIP:http://foo.com/FIF=image_name\" syntax as connection string, to " +"retrieve from the server information on the full resolution dimension and" +" the number of resolutions." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:310 +msgid "" +"The XML definition can then be generated with \"gdal_translate " +"IIP:http://foo.com/FIF=image_name out.xml -of WMS\"" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:314 +msgid "Caching" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:316 +msgid "" +"Caching of remote pixel data is possible by setting a element in " +"the WMS configuration file." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:319 +msgid "" +"Before GDAL 3.9, if the sub-element of was not specified, " +"the directory of the cache was ``./gdalwmscache`` (that is to say a " +"``gdalwmscache`` subdiretory of the current directory), unless the " +":config:`GDAL_DEFAULT_WMS_CACHE_PATH` configuration option is specified." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:324 +msgid "" +"Starting with GDAL 3.9, the directory of the cache is set according to " +"the following logic (first listed criterion is prioritary over following " +"ones):" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:327 +msgid "Value of the sub-element of , if specified." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:329 +msgid "" +"``${GDAL_DEFAULT_WMS_CACHE_PATH}`` if " +":config:`GDAL_DEFAULT_WMS_CACHE_PATH` is set." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:331 +msgid "" +"``${XDG_CACHE_HOME}/gdalwmscache`` if the ``XDG_CACHE_HOME`` " +"configuration option is set." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:333 +msgid "" +"On Unix, ``${HOME}/.cache/gdalwmscache`` if the ``HOME`` configuration " +"option is set." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:335 +msgid "" +"On Windows, ``${USERPROFILE}/.cache/gdalwmscache`` if the ``USERPROFILE``" +" configuration option is set." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:337 +msgid "" +"``${CPL_TMPDIR}/gdalwmscache_${USER}`` if :config:`CPL_TMPDIR` and " +"``USER`` configuration options are set." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:339 +msgid "If ``CPL_TMPDIR`` is not set, then ``TMPDIR`` is used, or ``TEMP``" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:341 +msgid "" +"If ``USER`` is not set, ``USERNAME`` is used if set. If neither " +"``USERNAME`` or ``USER`` are set, the md5sum of the filename of the " +"configuration file is used)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:344 +msgid "" +"``./gdalwmscache_{md5sum(filename)}`` if none of the above mentioned " +"configuration options are set." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:346 +msgid "" +"Note that if the element is set to true (which is its default " +"value), a subdirectory whose name is the md5sum of the filename of the " +"configuration file is appended to the caching directory." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:350 +msgid "" +"The actual caching directory can be got by querying the ``CACHE_PATH`` " +"metadata item on the dataset." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:356 +msgid "The following :ref:`configuration options ` are available:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:386 +msgid "" +"The below examples rely on external servers that might go down over time." +" They are just here to demonstrate how to use the various services." +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"`onearth_global_mosaic.xml " +"`__" +" - Landsat mosaic from a `OnEarth `__ WMS " +"server" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:402 +msgid "*Note : this particular server does no longer accept regular WMS queries.*" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:405 +msgid "" +"`metacarta_wmsc.xml " +"`__" +" - It is possible to configure a WMS Service conforming to a WMS-C cache " +"by specifying a number of overviews and specifying the 'block size' as " +"the tile size of the cache. The following example is a sample set up for " +"a 19-level \"Global Profile\" WMS-C cache." +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"`tileservice_bmng.xml " +"`__" +" - - TileService, Blue Marble NG (January)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"`tileservice_nysdop2004.xml " +"`__" +" - TileService, NYSDOP 2004" +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"`OpenStreetMap TMS Service Example " +"`__:" +" Connect to OpenStreetMap tile service. Note that this file takes " +"advantage of the tile cache; more information about configuring the tile " +"cache settings is available above. Please also change the , to" +" avoid the default one being used, and potentially blocked by OSM servers" +" in case a too big usage of it would be seen." +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"``gdal_translate -of PNG -outsize 512 512 frmt_wms_openstreetmap_tms.xml " +"openstreetmap.png``" +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"`MetaCarta TMS Layer Example " +"`__," +" accessing the default MetaCarta TMS layer." +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"``gdal_translate -of PNG -outsize 512 256 frmt_wms_metacarta_tms.xml " +"metacarta.png``" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:430 +msgid "" +"`BlueMarble Amazon S3 Example " +"`__" +" accessed with the TMS minidriver." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:433 +msgid "" +"`Google Maps " +"`__" +" accessed with the TMS minidriver." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:436 +msgid "" +"`ArcGIS MapServer Tiles " +"`__" +" accessed with the TMS minidriver." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:439 +msgid "" +"OnEarth Tiled WMS `Clementine " +"`__," +" `daily " +"`__," +" and `srtm " +"`__" +" examples." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:443 +msgid "" +"`VirtualEarth Aerial Layer " +"`__" +" accessed with the VirtualEarth minidriver." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:446 +msgid "" +"`ArcGIS online sample server layer " +"`__" +" accessed with the ArcGIS Server REST API minidriver." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:449 +msgid "" +"`IIP online sample server layer " +"`__" +" accessed with the IIP minidriver." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:455 +msgid "The WMS driver can open :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:457 +msgid "a local service description XML file :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:463 +#: ../../source/drivers/raster/wmts.rst:36 +msgid "the content of a description XML file provided as filename :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:469 +msgid "the base URL of a WMS service, prefixed with *WMS:* :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:475 +msgid "" +"A list of subdatasets will be returned, resulting from the parsing of the" +" GetCapabilities request on that server." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:478 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if WMS`` option to command " +"line utilities accepting it, or ``WMS`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed URL, without the ``WMS:`` prefix." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:483 +msgid "" +"a pseudo GetMap request, such as the subdataset name returned by the " +"previous syntax :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:490 +msgid "" +"the base URL of a Tiled WMS service, prefixed with *WMS:* and with " +"request=GetTileService as GET argument:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:497 +msgid "" +"A list of subdatasets will be returned, resulting from the parsing of the" +" GetTileService request on that server." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:500 +msgid "the URL of a REST definition for a ArcGIS MapServer:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:506 +msgid "(GDAL >= 2.1.0) the URL of a IIP image:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:513 +msgid "Generation of WMS service description XML file" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:515 +msgid "" +"The WMS service description XML file can be generated manually, or " +"created as the output of the CreateCopy() operation of the WMS driver, " +"only if the source dataset is itself a WMS dataset. Said otherwise, you " +"can use gdal_translate with as source dataset any of the above syntax " +"mentioned in \"Open syntax\" and as output an XML file. For example:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:525 +#: ../../source/drivers/raster/wmts.rst:465 +msgid "" +"The generated file will come with default values that you may need to " +"edit." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:531 +msgid "`OGC WMS Standards `__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:532 +msgid "" +"`WMS Tiling Client Recommendation (WMS-C) " +"`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:534 +msgid "" +"`WorldWind TileService " +"`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:536 +msgid "" +"`TMS Specification " +"`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:538 +msgid "" +"`OnEarth Tiled WMS specification " +"`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:540 +msgid "" +"`ArcGIS Server REST API " +"`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:542 +msgid ":ref:`raster.wmts` driver page." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:5 +msgid "WMTS -- OGC Web Map Tile Service" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:7 +msgid "WMTS" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:13 +msgid "" +"Access to WMTS layers is possible with the GDAL WMTS client driver (needs" +" Curl support). It support both RESTful and KVP protocols." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:27 +msgid "The WMTS driver can open :" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:29 +msgid "" +"a local service description XML file, whose syntax is described in the " +"below section :" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:42 +msgid "a local GetCapabilities response of a WMTS service :" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:48 +msgid "the URL to the GetCapabilities response of a WMTS service:" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:54 +msgid "" +"the URL to the GetCapabilities response of a WMTS service, prefixed with " +"*WMTS:*, and possibly with optional layer, tilematrixset, " +"tilematrix/zoom_level, style and extendbeyonddateline parameters, with " +"the following syntax " +"*WMTS:url[,layer=layer_id][,tilematrixset=tms_id][,tilematrix=tm_id|,zoom_level=level][,style=style_id][,extendbeyonddateline=yes/no]*." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:68 +msgid "the *WMTS:* prefix with open options" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:74 +msgid "" +"In any of the above syntaxes, if several layers are present and no layer " +"disambiguation was done with the layer parameter/open option, or if a " +"layer has more than one style or a tile matrix set, a list of subdatasets" +" will be returned. If there is only one layer, it will be opened on the " +"default style and the first tile matrix set listed." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:80 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if WMTS`` option to command " +"line utilities accepting it, or ``WMTS`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename/URL, when it is not using subdataset " +"syntax (it can typically be used to force open a HDF5 file that would be " +"nominally recognized by the HDF5 driver)." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:89 +msgid "The following open options are available:" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:170 +msgid "Local service description XML file" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:172 +msgid "" +"It is important that there be no spaces or other content before the " +"```` element." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:176 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:178 +msgid "http://foo/WM TSCapabilities.xml" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:178 +msgid "" +"URL (or filename for local files) to GetCapabilities response document " +"(required). For a KVP only server, will be like " +"http://end_point?SERVICE=WMTS& ;REQUEST=GetCapabilities ." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:186 +msgid "foo=bar&" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:186 +msgid "" +"URL query parameters to add to all requests (GetCapabilities, GetTile, " +"GetFeatureInfo) (added in GDAL 3.5.1)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:191 +msgid "layer_id" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:191 +msgid "" +"Layer identifier (optional, but may be needed to disambiguate between " +"several layers)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:195 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:195 +msgid "" +"Style identifier. Must be one of the listed styles for the layer. " +"(optional, but may be needed to disambiguate between several styles)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:201 +msgid "tile_matrix_set_id " +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:201 +msgid "" +"Tile Matrix Set identifier. Must be one of the listed tile matrix set for" +" the layer. (optional, but may be needed to disambiguate between several " +"tile matrix sets)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:207 +msgid "tile_matrix_id" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:207 +msgid "" +"Tile Matrix identifier. Must be one of the listed tile matrix of the " +"select tile matrix set for the layer. (optional, GDAL >= 2.2. Exclusive " +"with ZoomLevel. If not specified the last tile matrix, ie the one with " +"the best resolution, is selected)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:216 +msgid "int_value" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:216 +msgid "" +"Index of the maximum zoom level / tile matrix to use. The first one (ie " +"the one of lower resolution) is indexed 0. (optional, GDAL >= 2.2. " +"Exclusive with TileMatrix. If not specified the last tile matrix, ie the " +"one with the best resolution, is selected)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:225 +msgid "image/png" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:225 +msgid "" +"Tile format, used by GetTile requests. Must be one of the listed Format " +"for the layer. (optional, but may be needed to disambiguate between " +"several Format)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:232 +msgid "application/xml" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:232 +msgid "" +"Info format, used by GetFeatureInfo requests. Must be one of the listed " +"InfoFormat for the layer. (optional, but may be needed to disambiguate " +"between several InfoFormat)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:239 +msgid "" +"Define extents of the data. (optional, when not specified the driver will" +" query the declared extent of the layer, and if not present fallback to " +"the extent of the select tile matrix set, taking into account potential " +"tile matrix set limits)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:248 +msgid "" +"X (longitude/easting) coordinate of upper-left corner, in the SRS of the " +"tile matrix set. (required if DataWindow is present)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:253 +msgid "" +"Y (latitude/northing) coordinate of upper-left corner, in the SRS of the " +"tile matrix set. (required if DataWindow is present)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:258 +msgid "" +"X (longitude/easting) coordinate of lower-right corner, in the SRS of the" +" tile matrix set. (required if DataWindow is present)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:263 +msgid "" +"Y (latitude/northing) coordinate of lower-right corner, in the SRS of the" +" tile matrix set. (required if DataWindow is present)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:270 +msgid "EPSG:4326" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:270 +msgid "" +"Declared projection, in case the one of the TileMatrixSet is not " +"desirable (optional, defaults to value of the TileMatrixSet)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:275 +msgid "4" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:275 +msgid "" +"Number of bands/channels, 1 for grayscale data, 3 for RGB, 4 for RGBA. " +"(optional, defaults to 4)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:284 +msgid "false" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:284 +msgid "" +"Whether to make the extent go over dateline and warp tile requests. Only " +"appropriate when the 2 following conditions are met (optional, defaults " +"to false):" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:291 +msgid "" +"for a geodetic SRS or EPSG:3857, with tile matrix sets such as the whole " +"[-180,180] range of longitude is entirely covered by an integral number " +"of tiles (e.g. GoogleMapsCompatible)." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:298 +#: ../../source/drivers/vector/tiledb.rst:57 +msgid "AND" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:300 +msgid "" +"when the layer BoundingBox in the SRS of the tile matrix set covers the " +"whole [-180,180] range of longitude, and that there is another " +"BoundingBox in another SRS that is centered around longitude 180. If such" +" alternate BoundingBox is not present in the GetCapabilities document, " +"DataWindow must be explicitly specified" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:313 +msgid "" +"OR when the layer BoundingBox in the SRS of the tile matrix set extends " +"beyond the dateline." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:318 +msgid "" +"Enable local disk cache. Allows for offline operation. (optional, cache " +"is disabled when absent, but it is present in the autogenerated XML, can " +"be overridden with GDAL_ENABLE_WMS_CACHE=NO" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:326 +msgid "" +"Location where to store cache files. It is safe to use same cache path " +"for different data sources. (optional, defaults to ./gdalwmscache if " +"GDAL_DEFAULT_WMS_CACHE_PATH configuration option is not specified) " +"/vsimem/ paths are supported allowing for temporary in-memory cache" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:355 +msgid "2" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:355 +msgid "Maximum number of simultaneous connections. (optional, defaults to 2)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:359 +msgid "Connection timeout in seconds. (optional, defaults to 300)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:367 +msgid "" +"GDAL WMS driver (http://www.gdal.org/frmt_wms.htm " +"l)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:367 +msgid "" +"HTTP User-agent string. Some servers might require a well-known user-" +"agent such as \"Mozilla/5.0\" (optional, defaults to \"GDAL WMS driver " +"(http://www.gdal.org/frmt_wms.htm l)\")." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:375 +msgid "" +"HTTP Accept header to specify the MIME type of the expected output of the" +" server. Empty by default. (added in GDAL 3.5.1)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:383 +msgid "" +"Skip SSL certificate verification. May be needed if server is using a " +"self signed certificate (optional, defaults to false, but set to true in " +"autogenerated XML)." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:390 +msgid "http://example.foo/" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:393 +msgid "204,404" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:393 +msgid "" +"Comma separated list of HTTP response codes that will be interpreted as a" +" 0 filled image (i.e. black for 3 bands, and transparent for 4 bands) " +"instead of aborting the request. (optional, defaults to non set, but set " +"to 204,404 in autogenerated XML)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:403 +msgid "true< /ZeroBlockOnServerException>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:403 +msgid "" +"Whether to treat a Service Exception returned by the server as a 0 filled" +" image instead of aborting the request. (optional, defaults to false, but" +" set to true in autogenerated XML)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:410 +msgid "" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:415 +msgid "" +"Starting with GDAL 2.3, additional HTTP headers can be sent by setting " +"the :config:`GDAL_HTTP_HEADER_FILE` configuration option to point to a " +"filename of a text file with “key: value” HTTP headers." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:420 +msgid "GetFeatureInfo request" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:422 +msgid "" +"WMTS layers can be queried (through a GetFeatureInfo request) with the " +"gdallocationinfo utility, or with a GetMetadataItem(\"Pixel_iCol_iLine\"," +" \"LocationInfo\") call on a band object." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:431 +msgid "Generation of WMTS service description XML file" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:433 +msgid "" +"The WMTS service description XML file can be generated manually, or " +"created as the output of the CreateCopy() operation of the WMTS driver, " +"only if the source dataset is itself a WMTS dataset. Said otherwise, you " +"can use gdal_translate with as source dataset any of the above syntax " +"mentioned in \"Open syntax\" and as output an XML file. For example:" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:443 +msgid "generates the following file:" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:471 +msgid "`OGC WMTS Standard `__" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:472 +msgid ":ref:`raster.wms` driver page." +msgstr "" + +#: ../../source/drivers/raster/xpm.rst:5 +msgid "XPM -- X11 Pixmap" +msgstr "" + +#: ../../source/drivers/raster/xpm.rst:7 +msgid "XPM" +msgstr "" + +#: ../../source/drivers/raster/xpm.rst:11 +msgid "" +"GDAL includes support for reading and writing XPM (X11 Pixmap Format) " +"image files. These are colormapped one band images primarily used for " +"simple graphics purposes in X11 applications. It has been incorporated in" +" GDAL primarily to ease translation of GDAL images into a form usable " +"with the GTK toolkit." +msgstr "" + +#: ../../source/drivers/raster/xpm.rst:17 +msgid "" +"The XPM support does not support georeferencing (not available from XPM " +"files) nor does it support XPM files with more than one character per " +"pixel. New XPM files must be colormapped or greyscale, and colortables " +"will be reduced to about 70 colors automatically." +msgstr "" + +#: ../../source/drivers/raster/xpm.rst:22 +msgid "NOTE: Implemented as :source_file:`frmts/xpm/xpmdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:5 +msgid "XYZ -- ASCII Gridded XYZ" +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:7 +msgid "XYZ" +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:11 +msgid "" +"GDAL supports reading and writing ASCII **gridded** XYZ raster datasets " +"(i.e. ungridded XYZ, LIDAR XYZ etc. must be opened by other means. See " +"the documentation of the :ref:`gdal_grid` utility)." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:15 +msgid "" +"Those datasets are ASCII files with (at least) 3 columns, each line " +"containing the X and Y coordinates of the center of the cell and the " +"value of the cell. (Note the XYZ driver only uses the first band of the " +"dataset. I.e., columns beyond the third are ignored.)" +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:20 +msgid "The spacing between each cell must be constant." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:22 +msgid "The following data organization are supported :" +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:24 +msgid "" +"Cells with same Y coordinates must be placed on consecutive lines. For a " +"same Y coordinate value, the lines in the dataset must be organized by " +"increasing X values. The value of the Y coordinate can increase or " +"decrease however." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:29 +msgid "" +"or, starting with GDAL 3.2.1, cells with same X coordinates must be " +"placed on consecutive lines. For a same X coordinate value, the columns " +"must be organized by increasing or decreasing Y values. For that " +"organization, no missing value is supported, and the whole dataset will " +"be ingested into memory (thus the driver will limit to 100 million " +"points)." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:35 +msgid "" +"The supported column separators are space, comma, semicolon and " +"tabulations." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:37 +msgid "" +"The driver tries to autodetect an header line and will look for 'x', " +"'lon' or 'east' names to detect the index of the X column, 'y', 'lat' or " +"'north' for the Y column and 'z', 'alt' or 'height' for the Z column. If " +"no header is present or one of the column could not be identified in the " +"header, the X, Y and Z columns (in that order) are assumed to be the " +"first 3 columns of each line. The open option :oo:`COLUMN_ORDER` " +"overrides these assumptions (except on 'AUTO')." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:45 +msgid "" +"The opening of a big dataset can be slow as the driver must scan the " +"whole file to determine the dataset size and spatial resolution. The " +"driver will autodetect the data type among Byte, Int16, Int32 or Float32." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:-1 +msgid "" +"COLUMN_ORDER=[AUTO/XYZ/YXZ]: (GDAL >= 3.10) Defaults to AUTO. Specifies" +" the order of the columns. It overrides the header." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:105 +msgid "Documentation of :ref:`gdal_grid`" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:11 +msgid "" +"Built-in by default, but liblz4, libxz (lzma), libzstd and libblosc " +"strongly recommended to get all compressors" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:14 +msgid "" +"Zarr is a format for the storage of chunked, compressed, N-dimensional " +"arrays. This format is supported for read and write access, and using the" +" traditional 2D raster API or the newer multidimensional API" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:18 +msgid "" +"The driver supports the Zarr V2 specification, and has experimental " +"support for the in-progress Zarr V3 specification." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:23 +msgid "" +"The current implementation of Zarr V3 before GDAL 3.8 is incompatible " +"with the latest evolutions of the Zarr V3 specification. GDAL 3.8 is " +"compatible with the Zarr V3 specification at date 2023-May-7, and is not " +"interoperable with Zarr V3 datasets produced by earlier GDAL versions." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:29 +msgid "" +"Local and cloud storage (see :ref:`virtual_file_systems`) are supported " +"in read and write." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:43 +msgid "Concepts" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:45 +msgid "" +"A Zarr dataset is made of a hierarchy of nodes, with intermediate nodes " +"being groups (:cpp:class:`GDALGroup`), and leafs being arrays " +"(:cpp:class:`GDALMDArray`)." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:49 +msgid "Dataset name" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:51 +msgid "" +"For Zarr V2, the dataset name recognized by the Open() method of the " +"driver is a directory that contains a :file:`.zgroup` file, a " +":file:`.zarray` file or a :file:`.zmetadata` file (consolidated " +"metadata). For faster exploration, the driver will use consolidated " +"metadata by default when found." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:56 +msgid "" +"For Zarr V3, the dataset name recognized by the Open() method of the " +"driver is a directory that contains a :file:`zarr.json` file (root of the" +" dataset)." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:59 +msgid "" +"For datasets on file systems where file listing is not reliable, as often" +" with /vsicurl/, it is also possible to prefix the directory name with " +"``ZARR:``, and it is necessary to surround the /vsicurl/-prefixed URL " +"with double quotes. e.g `ZARR:\"/vsicurl/https://example.org/foo.zarr\"`." +" Note that when passing such string in a command line shell, extra " +"quoting might be necessary to preserve the double-quoting." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:66 +msgid "" +"For example with a Bash shell, the whole connection string needs to be " +"surrounded with single-quote characters:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:75 +msgid "Compression methods" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:77 +msgid "" +"Compression methods available depend on how GDAL is built, and `libblosc " +"`__ too." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:80 +msgid "A full-feature build will show:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:92 +msgid "" +"For specific uses, it is also possible to register at run-time extra " +"compressors and decompressors with :cpp:func:`CPLRegisterCompressor` and " +":cpp:func:`CPLRegisterDecompressor`." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:96 +msgid "XArray _ARRAY_DIMENSIONS" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:98 +msgid "" +"The driver support the ``_ARRAY_DIMENSIONS`` special attribute used by " +"`XArray " +"`__ " +"to store the dimension names of an array." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:103 +msgid "NCZarr extensions" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:105 +msgid "" +"The driver support the `NCZarr v2 " +"`__" +" extensions of storing the dimension names of an array (read-only)" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:110 +msgid "SRS encoding" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:112 +msgid "" +"The Zarr specification has no provision for spatial reference system " +"encoding. GDAL uses a ``_CRS`` attribute that is a dictionary that may " +"contain one or several of the following keys: ``url`` (using a OGC CRS " +"URL), ``wkt`` (WKT:2019 used by default on writing, WKT1 also supported " +"on reading.), ``projjson``. On reading, it will use ``url`` by default, " +"if not found will fallback to ``wkt`` and then ``projjson``." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:247 +msgid "Particularities of the classic raster API" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:249 +msgid "" +"If the Zarr dataset contains one single array with 2 dimensions, it will " +"be exposed as a regular GDALDataset when using the classic raster API. If" +" the dataset contains more than one such single array, or arrays with 3 " +"or more dimensions, the driver will list subdatasets to access each array" +" and/or 2D slices within arrays with 3 or more dimensions." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:258 +msgid "The following dataset open options are available:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:320 +msgid "Multi-threaded caching" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:322 +msgid "" +"The driver implements the :cpp:func:`GDALMDArray::AdviseRead` method. " +"This proceed to multi-threaded decoding of the tiles that intersect the " +"area of interest specified. A sufficient cache size must be specified. " +"The call is blocking." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:327 +msgid "The options that can be passed to the methods are:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:329 +msgid "" +"**CACHE_SIZE=value_in_byte**: Maximum RAM to use, expressed in number of " +"bytes. If not specified, half of the remaining GDAL block cache size will" +" be used. Note: the caching mechanism of Zarr array will not update this " +"remaining block cache size." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:334 +msgid "" +"**NUM_THREADS=integer or ALL_CPUS**: Number of threads to use in " +"parallel. If not specified, the :config:`GDAL_NUM_THREADS` configuration " +"option will be taken into account." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:341 +msgid "" +"The following options are creation options of the classic raster API, or " +"array-level creation options for the multidimensional API (must be " +"prefixed with ``ARRAY:`` using :program:`gdalmdimtranslate`):" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:465 +msgid "" +"The following options are creation options of the classic raster API, or " +"dataset-level creation options for the multidimensional API :" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:479 +msgid "The following options are creation options of the classic raster API only:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:513 +msgid "Get information on the dataset using the multidimensional tools:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:520 +msgid "Convert a netCDF file to ZARR using the multidimensional tools:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:527 +msgid "" +"Convert a 2D slice (the one at index 0 of the non-2D dimension) of a 3D " +"array to GeoTIFF:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:535 +msgid "" +"The single quoting around the connection string is specific to the Bash " +"shell to make sure that the double quoting is preserved." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:542 +msgid "" +"`Zarr format and its Python implementation " +"`__" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:543 +msgid "" +"`(In progress) Zarr V3 specification `__" +msgstr "" + +#: ../../source/drivers/raster/zmap.rst:5 +msgid "ZMap -- ZMap Plus Grid" +msgstr "" + +#: ../../source/drivers/raster/zmap.rst:7 +msgid "ZMAP" +msgstr "" + +#: ../../source/drivers/raster/zmap.rst:11 +msgid "" +"Supported for read access and creation. This format is an ASCII " +"interchange format for gridded data in an ASCII line format for transport" +" and storage. It is commonly used in applications in the Oil and Gas " +"Exploration field." +msgstr "" + +#: ../../source/drivers/raster/zmap.rst:16 +msgid "" +"By default, files are interpreted and written according to the " +"PIXEL_IS_AREA convention. If you define the ZMAP_PIXEL_IS_POINT " +"configuration option to TRUE, the PIXEL_IS_POINT convention will be " +"followed to interpret/write the file (the georeferenced values in the " +"header of the file will then be considered as the coordinate of the " +"center of the pixels). Note that in that case, GDAL will report the " +"extent with its usual PIXEL_IS_AREA convention (the coordinates of the " +"topleft corner as reported by GDAL will be a half-pixel at the top and " +"left of the values that appear in the file)." +msgstr "" + +#: ../../source/drivers/raster/zmap.rst:26 +msgid "" +"Informal specification given in this `GDAL-dev mailing list thread " +"`__" +msgstr "" + +#: ../../source/drivers/raster/zmap.rst:29 +msgid "NOTE: Implemented as :source_file:`frmts/zmap/zmapdataset.cpp`." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:5 +#: ../../source/drivers/vector/amigocloud.rst:9 +#: ../../source/drivers/vector/driver_summary.rst:17 +msgid "AmigoCloud" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:13 +msgid "" +"This driver can connect to the AmigoCloud API services. GDAL/OGR must be " +"built with Curl support in order for the AmigoCloud driver to be " +"compiled." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:16 +#: ../../source/drivers/vector/carto.rst:14 +msgid "The driver supports read and write operations." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:30 +msgid "The minimal syntax to open a AmigoCloud datasource is:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:39 +msgid "" +"**datasets=dataset_id1[,dataset_id2, ..]**: A list of AmigoCloud dataset " +"IDs. This is necessary when you need to access a particular AmigoCloud " +"dataset." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:43 +#: ../../source/drivers/vector/carto.rst:40 +msgid "If several parameters are specified, they must be separated by a space." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:45 +msgid "" +"If no datset_id is provided, the driver will print list of available " +"datasets for given project." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:48 +msgid "For example: **\"AmigoCloud:1234 datasets\"**" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:61 +msgid "All the access permissions are defined by AmigoCloud backend." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:63 +msgid "" +"Authenticated access is obtained by specifying the API key given in the " +"AmigoCloud dashboard web interface. It is specified with the " +":config:`AMIGOCLOUD_API_KEY` configuration option." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:68 +#: ../../source/drivers/vector/carto.rst:53 +#: ../../source/drivers/vector/eeda.rst:154 +#: ../../source/drivers/vector/geojson.rst:135 +#: ../../source/drivers/vector/libkml.rst:910 +#: ../../source/drivers/vector/netcdf.rst:187 +#: ../../source/drivers/vector/ngw.rst:122 +#: ../../source/drivers/vector/plscenes_data_v1.rst:144 +msgid "Geometry" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:70 +msgid "" +"The OGR driver will report as many geometry fields as available in the " +"layer, following RFC 41." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:74 +#: ../../source/drivers/vector/carto.rst:59 +#: ../../source/drivers/vector/csw.rst:30 +#: ../../source/drivers/vector/eeda.rst:160 +#: ../../source/drivers/vector/elasticsearch.rst:186 +#: ../../source/drivers/vector/mongodbv3.rst:152 +#: ../../source/drivers/vector/oapif.rst:51 +#: ../../source/drivers/vector/plscenes_data_v1.rst:150 +#: ../../source/drivers/vector/tiledb.rst:50 +#: ../../source/drivers/vector/wfs.rst:156 +msgid "Filtering" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:76 +msgid "" +"The driver will forward any spatial filter set with " +":cpp:func:`OGRLayer::SetSpatialFilter` to the server. It also makes the " +"same for attribute filters set with " +":cpp:func:`OGRLayer::SetAttributeFilter`." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:81 +#: ../../source/drivers/vector/carto.rst:73 +#: ../../source/drivers/vector/elasticsearch.rst:426 +#: ../../source/drivers/vector/gpsbabel.rst:74 +#: ../../source/drivers/vector/mapml.rst:44 +#: ../../source/drivers/vector/mongodbv3.rst:222 +#: ../../source/drivers/vector/ngw.rst:158 +msgid "Write support" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:83 +msgid "Dataset creation and deletion is possible." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:85 +#: ../../source/drivers/vector/carto.rst:77 +#: ../../source/drivers/vector/elasticsearch.rst:430 +#: ../../source/drivers/vector/mongodbv3.rst:226 +#: ../../source/drivers/vector/wfs.rst:219 +msgid "" +"Write support is only enabled when the datasource is opened in update " +"mode." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:88 +msgid "" +"The mapping between the operations of the AmigoCloud service and the OGR " +"concepts is the following :" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:91 +#: ../../source/drivers/vector/carto.rst:83 +msgid ":cpp:func:`OGRFeature::CreateFeature` <==> ``INSERT`` operation" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:92 +#: ../../source/drivers/vector/carto.rst:84 +msgid ":cpp:func:`OGRFeature::SetFeature` <==> ``UPDATE`` operation" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:93 +#: ../../source/drivers/vector/carto.rst:85 +msgid ":cpp:func:`OGRFeature::DeleteFeature` <==> ``DELETE`` operation" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:94 +#: ../../source/drivers/vector/carto.rst:86 +msgid ":cpp:func:`OGRDataSource::CreateLayer` <==> ``CREATE TABLE`` operation" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:95 +msgid ":cpp:func:`OGRDataSource::DeleteLayer` <==> `DROP TABLE` operation" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:97 +msgid "" +"When inserting a new feature with CreateFeature(), and if the command is " +"successful, OGR will fetch the returned amigo_id (GUID) and use hash " +"value of it as the OGR FID." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:101 +#: ../../source/drivers/vector/carto.rst:93 +#: ../../source/drivers/vector/wfs.rst:250 +msgid "" +"The above operations are by default issued to the server synchronously " +"with the OGR API call. This however can cause performance penalties when " +"issuing a lot of commands due to many client/server exchanges." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:142 +msgid "Different ways to provide AmigoCloud API token:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:155 +msgid "Show list of datasets." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:166 +msgid "Accessing data from a list of datasets:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:172 +#: ../../source/drivers/vector/carto.rst:217 +msgid "Creating and populating a table from a shapefile:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:178 +msgid "Append the data to an existing table (dataset id: 12345) from a shapefile:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:190 +msgid "" +"Overwriting the data of an existing table (dataset id: 12345) with data " +"from a shapefile:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:197 +msgid "" +"Delete existing dataset (dataset id: 12345) and create a new one with " +"data from a shapefile:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:204 +msgid "" +"Overwriting the data of an existing table (dataset id: 12345) with data " +"from a shapefile. Filter the only the records with values of the field " +"\"visited_on\" after 2017-08-20" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:215 +msgid "" +"`AmigoCloud API Token management " +"`__" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:216 +msgid "`AmigoCloud API Browser `__" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:4 +#: ../../source/drivers/vector/driver_summary.rst:22 +msgid "(Geo)Arrow IPC File Format / Stream" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:8 +msgid "Arrow" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:10 +#: ../../source/drivers/vector/driver_summary.rst:25 +msgid "Apache Arrow C++ library" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:12 +msgid "" +"The Arrow IPC File Format (Feather) is a portable file format for storing" +" Arrow tables or data frames (from languages like Python or R) that " +"utilizes the Arrow IPC format internally." +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:16 +msgid "The driver supports the 2 variants of the format:" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:18 +msgid "" +"File or Random Access format, also known as Feather: for serializing a " +"fixed number of record batches. Random access is required to read such " +"files, but they can be generated using a streaming-only capable file. The" +" recommended extension for such file is ``.arrow``" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:23 +msgid "" +"Streaming IPC format: for sending an arbitrary length sequence of record " +"batches. The format must generally be processed from start to end, and " +"does not require random access. That format is not generally materialized" +" as a file. If it is, the recommended extension is ``.arrows`` (with a " +"trailing s). But the driver can support regular files as well as the " +"/vsistdin/ and /vsistdout/ streaming files. On opening, it might " +"difficult for the driver to detect that the content is specifically a " +"Arrow IPC stream, especially if the extension is not ``.arrows``, and the" +" metadata section is large. Prefixing the filename with " +"``ARROW_IPC_STREAM:`` (e.g \"ARROW_IPC_STREAM:/vsistdin/\") will cause " +"the driver to unconditionally open the file as a streaming IPC format. " +"Alternatively, starting with GDAL 3.10, specifying the ``-if ARROW`` " +"option to command line utilities accepting it, or ``ARROW`` as the only " +"value of the ``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also " +"forces the driver to recognize the passed filename." +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:39 +msgid "" +"This driver also supports geometry columns using the GeoArrow " +"specification." +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:41 +msgid "" +"The driver should be considered experimental as the GeoArrow " +"specification is not finalized yet." +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:55 +#: ../../source/drivers/vector/parquet.rst:59 +msgid "The driver supports creating only a single layer in a dataset." +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:60 +#: ../../source/drivers/vector/carto.rst:140 +#: ../../source/drivers/vector/csv.rst:429 +#: ../../source/drivers/vector/dgnv8.rst:206 +#: ../../source/drivers/vector/filegdb.rst:126 +#: ../../source/drivers/vector/flatgeobuf.rst:62 +#: ../../source/drivers/vector/geoconcept.rst:155 +#: ../../source/drivers/vector/geojsonseq.rst:66 +#: ../../source/drivers/vector/gpx.rst:231 +#: ../../source/drivers/vector/hana.rst:181 +#: ../../source/drivers/vector/jsonfg.rst:132 +#: ../../source/drivers/vector/mitab.rst:145 +#: ../../source/drivers/vector/mongodbv3.rst:236 +#: ../../source/drivers/vector/mssqlspatial.rst:108 +#: ../../source/drivers/vector/mvt.rst:402 +#: ../../source/drivers/vector/mysql.rst:106 +#: ../../source/drivers/vector/oci.rst:138 +#: ../../source/drivers/vector/openfilegdb.rst:123 +#: ../../source/drivers/vector/parquet.rst:64 +#: ../../source/drivers/vector/pg.rst:245 +#: ../../source/drivers/vector/pgdump.rst:53 +#: ../../source/drivers/vector/pmtiles.rst:222 +#: ../../source/drivers/vector/selafin.rst:351 +#: ../../source/drivers/vector/shapefile.rst:348 +#: ../../source/drivers/vector/sqlite.rst:325 +msgid "" +"|about-layer-creation-options| The following layer creation options are " +"supported:" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:111 +#: ../../source/drivers/vector/parquet.rst:227 +msgid "Conda-forge package" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:113 +#: ../../source/drivers/vector/parquet.rst:229 +msgid "" +"The driver can be installed as a plugin for the ``libgdal`` conda-forge " +"package with:" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:123 +msgid "" +"`Feather File Format " +"`__" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:125 +msgid "`GeoArrow specification `__" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:127 +msgid "Related driver: :ref:`Parquet driver `" +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:5 +#: ../../source/drivers/vector/driver_summary.rst:27 +msgid "Arc/Info Binary Coverage" +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:7 +msgid "AVCBIN" +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:11 +msgid "" +"Arc/Info Binary Coverages (eg. Arc/Info V7 and earlier) are supported by " +"OGR for read access." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:14 +#: ../../source/drivers/vector/avce00.rst:14 +msgid "" +"The label, arc, polygon, centroid, region and text sections of a coverage" +" are all supported as layers. Attributes from INFO are appended to " +"labels, arcs, polygons or region where appropriate. When available the " +"projection information is read and translated. Polygon geometries are " +"collected for polygon and region layers from the composing arcs." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:20 +#: ../../source/drivers/vector/avce00.rst:20 +msgid "" +"Text sections are represented as point layers. Display height is " +"preserved in the HEIGHT attribute field; however, other information about" +" text orientation is discarded." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:24 +#: ../../source/drivers/vector/avce00.rst:24 +msgid "" +"Info tables associated with a coverage, but not specifically named to be " +"attached to one of the existing geometric layers is currently not " +"accessible through OGR. Note that info tables are stored in an 'info' " +"directory at the same level as the coverage directory. If this is " +"inaccessible or corrupt no info attributes will be appended to coverage " +"layers, but the geometry should still be accessible." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:31 +msgid "" +"If the directory contains files with names like w001001.adf then the " +"coverage is a :ref:`grid coverage ` suitable to read with " +"GDAL, not a vector coverage supported by OGR." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:35 +#: ../../source/drivers/vector/avce00.rst:31 +msgid "The layers are named as follows:" +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:37 +#: ../../source/drivers/vector/avce00.rst:33 +msgid "" +"A label layer (polygon labels, or free standing points) is named LAB if " +"present." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:39 +#: ../../source/drivers/vector/avce00.rst:35 +msgid "A centroid layer (polygon centroids) is named CNT if present." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:40 +#: ../../source/drivers/vector/avce00.rst:36 +msgid "An arc (line) layer is named ARC if present." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:41 +#: ../../source/drivers/vector/avce00.rst:37 +msgid "A polygon layer is named \"PAL\" if present." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:42 +#: ../../source/drivers/vector/avce00.rst:38 +msgid "A text section is named according to the section subclass." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:43 +#: ../../source/drivers/vector/avce00.rst:39 +msgid "A region subclass is named according to the subclass name." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:45 +msgid "" +"The Arc/Info binary coverage driver attempts to optimize spatial queries " +"but due to the lack of a spatial index this is just accomplished by " +"minimizing processing for features not within the spatial window." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:49 +msgid "" +"Random (by FID) reads of arcs, and polygons is supported it may not be " +"supported for other feature types." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:62 +#: ../../source/drivers/vector/avce00.rst:55 +msgid "`AVCE00 Library Page `__" +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:63 +msgid ":ref:`AVCE00 OGR Driver (.E00) `" +msgstr "" + +#: ../../source/drivers/vector/avce00.rst:5 +#: ../../source/drivers/vector/driver_summary.rst:32 +msgid "Arc/Info E00 (ASCII) Coverage" +msgstr "" + +#: ../../source/drivers/vector/avce00.rst:7 +msgid "AVCE00" +msgstr "" + +#: ../../source/drivers/vector/avce00.rst:11 +msgid "" +"Arc/Info E00 Coverages (eg. Arc/Info V7 and earlier) are supported by OGR" +" for read access." +msgstr "" + +#: ../../source/drivers/vector/avce00.rst:41 +msgid "" +"Random (by FID) reads of arcs, and polygons is supported it may not be " +"supported for other feature types. Random access to E00 files is " +"generally slow." +msgstr "" + +#: ../../source/drivers/vector/avce00.rst:56 +msgid ":ref:`AVCBin OGR Driver (Binary Coverage) `" +msgstr "" + +#: ../../source/drivers/vector/cad.rst:5 +msgid "CAD -- AutoCAD DWG" +msgstr "" + +#: ../../source/drivers/vector/cad.rst:11 +msgid "" +"OGR DWG support is based on libopencad, so the list of supported DWG " +"(DXF) versions can be seen in libopencad documentation. All drawing " +"entities are separated into layers as they are in DWG file, not in 1 " +"layer as DXF Driver does." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:16 +#: ../../source/drivers/vector/dwg.rst:17 +msgid "" +"DWG files are considered to have no georeferencing information through " +"OGR. Features will all have the following generic attributes:" +msgstr "" + +#: ../../source/drivers/vector/cad.rst:19 +msgid "CADGeometry: CAD Type of the presented geometry." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:20 +msgid "" +"Thickness: Thickness of the object drawing units (if it is not supported " +"by this type, it is set to 0.0)." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:22 +msgid "Color (RGB): IntegerList contains R,G,B components of the color." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:23 +#: ../../source/drivers/vector/dwg.rst:23 +msgid "" +"ExtendedEntity: Where available, extended entity attributes all appended " +"to form a single text attribute." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:34 +#: ../../source/drivers/vector/dgn.rst:42 +#: ../../source/drivers/vector/dgnv8.rst:40 +msgid "Supported Elements" +msgstr "" + +#: ../../source/drivers/vector/cad.rst:36 +#: ../../source/drivers/vector/dgn.rst:44 +msgid "The following element types are supported:" +msgstr "" + +#: ../../source/drivers/vector/cad.rst:38 +msgid "POINT: Produces a simple point geometry feature." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:39 +msgid "" +"LINE: Translated as a LINESTRING. Rounded polylines (those with their " +"vertices' budge attributes set) will be tessellated. Single-vertex " +"polylines are translated to POINT." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:42 +msgid "CIRCLE, ARC: Translated as a CIRCULARSTRING." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:43 +msgid "3DFACE: Translated as POLYGON." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:45 +msgid "The driver is read-only." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:50 +msgid "" +"`ODA DWG Reference " +"`__" +msgstr "" + +#: ../../source/drivers/vector/cad.rst:51 +msgid "`Libopencad repository `__" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:5 +#: ../../source/drivers/vector/driver_summary.rst:42 +msgid "Carto" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:7 +msgid "CARTO" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:11 +msgid "" +"This driver can connect to the services implementing the Carto API. " +"GDAL/OGR must be built with Curl support in order for the Carto driver to" +" be compiled." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:26 +msgid "The minimal syntax to open a Carto datasource is :" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:32 +msgid "" +"For single-user accounts, connection name is the account name. For multi-" +"user accounts, connection_name must be the user name, not the account " +"name. Additional optional parameters can be specified after the ':' sign." +" Currently the following one is supported:" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:37 +msgid "" +"**tables=table_name1[,table_name2]\\***: A list of table names. This is " +"necessary when you need to access to public tables for example." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:45 +msgid "" +"Most operations, in particular write operations, require an authenticated" +" access. The only exception is read-only access to public tables." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:48 +msgid "" +"Authenticated access is obtained by specifying the API key given in the " +"management interface of the Carto service. It is specified with the " +"CARTO_API_KEY configuration option." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:55 +msgid "" +"The OGR driver will report as many geometry fields as available in the " +"layer (except the 'the_geom_webmercator' field), following RFC 41." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:61 +msgid "" +"The driver will forward any spatial filter set with " +":cpp:func:`OGRLayer::SetSpatialFilter` to the server. It also makes the " +"same for attribute filters set with :cpp:func:`SetAttributeFilter`." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:67 +#: ../../source/drivers/vector/eeda.rst:168 +#: ../../source/drivers/vector/elasticsearch.rst:209 +#: ../../source/drivers/vector/mongodbv3.rst:165 +#: ../../source/drivers/vector/ngw.rst:150 +#: ../../source/drivers/vector/plscenes_data_v1.rst:159 +msgid "Paging" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:69 +msgid "" +"Features are retrieved from the server by chunks of 500 by default. This " +"number can be altered with the :config:`CARTO_PAGE_SIZE` configuration " +"option." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:75 +msgid "Table creation and deletion is possible." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:80 +msgid "" +"The mapping between the operations of the Carto service and the OGR " +"concepts is the following :" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:87 +msgid ":cpp:func:`OGRDataSource::DeleteLayer` <==> ``DROP TABLE`` operation" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:89 +msgid "" +"When inserting a new feature with :cpp:func:`OGRFeature::CreateFeature`, " +"and if the command is successful, OGR will fetch the returned rowid and " +"use it as the OGR FID." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:97 +msgid "" +"So, on a newly created layer, the ``INSERT`` of " +":cpp:func:`OGRFeature::CreateFeature` operations are grouped together in " +"chunks until they reach 15 MB (can be changed with the " +":config:`CARTO_MAX_CHUNK_SIZE` configuration option, with a value in MB)," +" at which point they are transferred to the server. By setting " +":config:`CARTO_MAX_CHUNK_SIZE` to 0, immediate transfer occurs." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:105 +msgid "" +"Don't use :cpp:func:`OGRDataSource::DeleteLayer` and " +":cpp:func:`OGRDataSource::CreateLayer` to overwrite a table. Instead only" +" call :cpp:func:`OGRDataSource::CreateLayer` with OVERWRITE=YES. This " +"will avoid CARTO deleting maps that depend on this table" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:111 +#: ../../source/drivers/vector/geopackage_aspatial.rst:35 +#: ../../source/drivers/vector/gpkg.rst:60 +msgid "SQL" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:113 +msgid "" +"SQL commands provided to the :cpp:func:`OGRDataSource::ExecuteSQL` call " +"are executed on the server side, unless the OGRSQL dialect is specified. " +"You can use the full power of PostgreSQL + PostGIS SQL capabilities." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:120 +msgid "The following open options are available: |about-open-options|" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:164 +msgid "" +"**SRS**: Output SRS must be EPSG:4326. You can use ``-a_srs`` or " +"``-t_srs`` to assign or transform to 4326 before importing." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:166 +msgid "" +"**Geometry type**: Must be different than NONE. You can set to something " +"generic with ``-nlt GEOMETRY``." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:211 +msgid "Accessing data from a public table:" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:223 +msgid "" +"Creating and populating a table from a CSV containing geometries on " +"EPSG:4326:" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:231 +msgid "" +"The ``-a_srs`` and ``-nlt`` must be provided to CARTODBFY since the " +"information isn't extracted from the CSV." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:237 +msgid "`Carto API overview `__" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:4 +#: ../../source/drivers/vector/driver_summary.rst:47 +msgid "Comma Separated Value (.csv)" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:6 +msgid "CSV" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:10 +msgid "" +"OGR supports reading and writing primarily non-spatial tabular data " +"stored in text CSV files. CSV files are a common interchange format " +"between software packages supporting tabular data and are also easily " +"produced manually with a text editor or with end-user written scripts or " +"programs." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:16 +msgid "" +"The datasource name may be either a single CSV file or point to a " +"directory. For a directory to be recognised as a .csv datasource at least" +" half the files in the directory need to have the extension .csv. One " +"layer (table) is produced from each .csv file accessed. Starting with " +"GDAL 3.7, pipe separated values files with a \".psv\" extension are also " +"recognized." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:24 +msgid "" +"For files structured as CSV, but not ending with the \".csv\" extension, " +"the 'CSV:' prefix can be added before the filename to force loading by " +"the CSV driver." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:28 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if CSV`` option to command " +"line utilities accepting it, or ``CSV`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename, without the ``CSV:`` prefix." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:33 +msgid "" +"The OGR CSV driver supports reading and writing. Because the CSV format " +"has variable length text lines, reading is done sequentially. Reading " +"features in random order will generally be very slow. OGR CSV layer might" +" have a coordinate system stored in a .prj file (see GeoCSV " +"specification). When reading a field named \"WKT\" is assumed to contain " +"WKT geometry, but also is treated as a regular field. The OGR CSV driver " +"returns all attribute columns as string data types if no field type " +"information file (with .csvt extension) is available." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:42 +msgid "" +"Limited type recognition can be done for Integer, Real, String, Date " +"(YYYY-MM-DD), Time (HH:MM:SS+nn), DateTime (YYYY-MM-DD HH:MM:SS+nn) " +"columns through a descriptive file with the same name as the CSV file, " +"but a .csvt extension. In a single line the types for each column have to" +" be listed with double quotes and be comma separated (e.g., " +"\"Integer\",\"String\"). It is also possible to specify explicitly the " +"width and precision of each column, e.g. " +"\"Integer(5)\",\"Real(10.7)\",\"String(15)\". The driver will then use " +"these types as specified for the csv columns. Subtypes can be passed " +"between parenthesis, such as \"Integer(Boolean)\", \"Integer(Int16)\" and" +" \"Real(Float32)\". Starting with GDAL 2.1, accordingly with the `GeoCSV " +"specification `__, the \"CoordX\" or " +"\"Point(X)\" type can be used to specify a column with longitude/easting " +"values, \"CoordY\" or \"Point(Y)\" for latitude/northing values and " +"\"WKT\" for geometries encoded in WKT" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:59 +msgid "" +"Starting with GDAL 2.2, the \"JSonStringList\", \"JSonIntegerList\", " +"\"JSonInteger64List\" and \"JSonRealList\" types can be used in .csvt to " +"map to the corresponding OGR StringList, IntegerList, Integer64List and " +"RealList types. The field values are then encoded as JSON arrays, with " +"proper CSV escaping." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:65 +msgid "" +"Automatic field type guessing can also be done if specifying the open " +"options described in the below \"Open options\" section." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:81 +msgid "" +"CSV files have one line for each feature (record) in the layer (table). " +"The attribute field values are separated by commas. At least two fields " +"per line must be present. Lines may be terminated by a DOS (CR/LF) or " +"Unix (LF) style line terminators. Each record should have the same number" +" of fields. The driver will also accept a semicolon, a tabulation, a " +"pipe, or a space character as field separator. Starting with GDAL 3.8, " +"the autodection will select the separator with the most occurrences if " +"there are several candidates on the first line of the CSV file (and warn" +" about that). The :oo:`SEPARATOR` open option may also be set to define " +"the desired separator. Previous versions select comma by default when " +"there are several potential separators." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:94 +msgid "" +"Complex attribute values (such as those containing commas, quotes or " +"newlines) may be placed in double quotes. Any occurrences of double " +"quotes within the quoted string should be doubled up to \"escape\" them." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:98 +msgid "" +"By default, the driver attempts to treat the first line of the file as a " +"list of field names for all the fields. However, if one or more of the " +"names is all numeric it is assumed that the first line is actually data " +"values and dummy field names are generated internally (field_1 through " +"field_n) and the first record is treated as a feature. Numeric values are" +" treated as field names if they are enclosed in double quotes. Starting " +"with GDAL 2.1, this behavior can be modified via the HEADERS open option." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:107 +msgid "" +"All CSV files are treated as UTF-8 encoded. A Byte Order Mark (BOM) at " +"the beginning of the file will be parsed correctly. The layer creation " +"option :lco:`WRITE_BOM` can be used to create a file with a Byte Order " +"Mark, which can improve compatibility with some software (particularly " +"Excel)." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:113 +msgid "Example (employee.csv):" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:121 +msgid "" +"Note that the Comments value for the first data record is placed in " +"double quotes because the value contains quotes, and those quotes have to" +" be doubled up so we know we haven't reached the end of the quoted string" +" yet." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:126 +msgid "" +"Many variations of textual input are sometimes called Comma Separated " +"Value files, including files without commas, but fixed column widths, " +"those using tabs as separators or those with other auxiliary data " +"defining field types or structure. This driver does not attempt to " +"support all such files, but instead to support simple .csv files that can" +" be auto-recognised. Scripts or other mechanisms can generally be used to" +" convert other variations into a form that is compatible with the OGR CSV" +" driver." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:136 +msgid "Reading CSV containing spatial information" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:139 +msgid "Building point geometries" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:141 +#: ../../source/drivers/vector/csv.rst:227 +msgid "Consider the following CSV file (test.csv):" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:150 +msgid "" +"Starting with GDAL 2.1, it is possible to directly specify the potential " +"names of the columns that can contain X/longitude and Y/latitude with the" +" :oo:`X_POSSIBLE_NAMES` and :oo:`Y_POSSIBLE_NAMES` open option." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:154 +msgid "" +"*ogrinfo -ro -al test.csv -oo X_POSSIBLE_NAMES=Lon\\* -oo " +"Y_POSSIBLE_NAMES=Lat\\* -oo KEEP_GEOM_COLUMNS=NO* will return :" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:171 +msgid "" +"If the CSV file does not have a header line, the dummy \"field_n\" names " +"can be used as possible names for coordinate fields. For example plain " +"XYZ point data can be opened as" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:175 +msgid "" +"*ogrinfo -ro -al elevation.xyz -oo X_POSSIBLE_NAMES=field_1 -oo " +"Y_POSSIBLE_NAMES=field_2 -oo Z_POSSIBLE_NAMES=field_3*" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:178 +msgid "" +"Otherwise, if one or several columns contain a geometry definition " +"encoded as WKT, WKB (encoded in hexadecimal) or GeoJSON (in which case " +"the GeoJSON content must be formatted to follow CSV rules, that is to say" +" it must be surrounded by double-quotes, and double-quotes inside the " +"string must be repeated for proper escaping), the name of such column(s) " +"can be derived from the :oo:`GEOM_POSSIBLE_NAMES` open option." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:185 +msgid "" +"For older versions, it is possible to extract spatial information " +"(points) from a CSV file which has columns for the X and Y coordinates, " +"through the use of the :ref:`VRT ` driver." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:189 +msgid "You can write the associated VRT file (test.vrt):" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:202 +msgid "and *ogrinfo -ro -al test.vrt* will return :" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:225 +msgid "Building line geometries" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:237 +msgid "" +"With a GDAL build with Spatialite enabled, *ogrinfo test.csv -dialect " +"SQLite -sql \"SELECT way_id, MakeLine(MakePoint(CAST(x AS float),CAST(y " +"AS float))) FROM test GROUP BY way_id\"* will return :" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:254 +#: ../../source/drivers/vector/selafin.rst:407 +msgid "" +"The driver supports reading and writing to files managed by VSI Virtual " +"File System API, which include \"regular\" files, as well as files in the" +" /vsizip/ (read-write) , /vsigzip/ (read-only) , /vsicurl/ (read-only) " +"domains." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:259 +#: ../../source/drivers/vector/geojson.rst:422 +#: ../../source/drivers/vector/georss.rst:245 +#: ../../source/drivers/vector/gpx.rst:392 +#: ../../source/drivers/vector/jsonfg.rst:193 +#: ../../source/drivers/vector/kml.rst:135 +#: ../../source/drivers/vector/libkml.rst:956 +#: ../../source/drivers/vector/pgdump.rst:262 +msgid "Writing to /dev/stdout or /vsistdout/ is also supported." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:261 +msgid "" +"Reading from /vsistdin/ is supported using the ``CSV:/vsistdin/`` " +"connection string and provided that none of the open options whose name " +"starts with ``AUTODETECT_`` is used." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:419 +msgid "" +"The driver supports creating new databases (as a directory of .csv " +"files), adding new .csv files to an existing directory or .csv files or " +"appending features to an existing .csv table. Starting with GDAL 2.1, " +"deleting or replacing existing features, or adding/modifying/deleting " +"fields is supported, provided the modifications done are small enough to " +"be stored in RAM temporarily before flushing to disk." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:427 +msgid "Layer Creation options" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:519 +msgid "" +"This example shows using ogr2ogr to transform a shapefile with point " +"geometry into a .csv file with the X,Y,Z coordinates of the points as " +"first columns in the .csv file" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:527 +msgid "" +"This example shows using ogr2ogr to transform a shapefile into a .csv " +"file with geometry field formatted using GeoJSON format." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:535 +msgid "" +"Convert a CSV into a GeoPackage. Specify the names of the coordinate " +"columns and assign a coordinate reference system." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:546 +msgid "" +"Use `ogr2ogr -segmentize` to densify a input geometry being specified in " +"the ``WKT`` special field. Note that one needs to specify the " +"GEOMETRY=AS_WKT layer creation option, otherwise the input geometry would" +" be returned unmodified:" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:563 +msgid "Particular datasources" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:565 +msgid "The CSV driver can also read files whose structure is close to CSV files :" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:568 +msgid "" +"Airport data files NfdcFacilities.xls, NfdcRunways.xls, NfdcRemarks.xls " +"and NfdcSchedules.xls found on that `FAA website " +"`__" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:572 +msgid "" +"Files from the `USGS GNIS " +"`__ (Geographic " +"Names Information System)" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:576 +msgid "The allCountries file from `GeoNames `__" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:578 +msgid "" +"`Eurostat .TSV files " +"`__" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:582 +#: ../../source/drivers/vector/ili.rst:111 +#: ../../source/drivers/vector/vrt.rst:563 +msgid "Other Notes" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:584 +msgid "" +"`GeoCSV specification `__ (supported by " +"GDAL >= 2.1)" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:586 +msgid "" +"Initial development of the OGR CSV driver was supported by `DM Solutions " +"Group `__ and `GoMOOS " +"`__." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:589 +msgid "" +"`Carto `__ funded field type auto-detection and open " +"options related to geometry columns." +msgstr "" + +#: ../../source/drivers/vector/csw.rst:4 +msgid "CSW - OGC CSW (Catalog Service for the Web)" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:6 +msgid "CSW" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:10 +msgid "" +"This driver can connect to a OGC CSW service. It supports CSW 2.0.2 " +"protocol. GDAL/OGR must be built with Curl support in order to the CSW " +"driver to be compiled. And the GML driver should be set-up for read " +"support (thus requiring GDAL/OGR to be built with Xerces or Expat " +"support)." +msgstr "" + +#: ../../source/drivers/vector/csw.rst:16 +msgid "It retrieves records with Dublin Core metadata." +msgstr "" + +#: ../../source/drivers/vector/csw.rst:26 +msgid "" +"The minimal syntax to open a CSW datasource is : *CSW:* and the URL open " +"option, or *CSW:http://path/to/CSW/endpoint*" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:32 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server. It also makes its best effort to do the same for attribute " +"filters set with SetAttributeFilter() when possible (turning OGR SQL " +"language into OGC filter description)." +msgstr "" + +#: ../../source/drivers/vector/csw.rst:37 +msgid "" +"The *anytext* field can be queried to do a search in any text field. Note" +" that we always return it as null content however in OGR side, to avoid " +"duplicating information." +msgstr "" + +#: ../../source/drivers/vector/csw.rst:42 +msgid "Issues" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:44 +msgid "" +"Some servers do not respect EPSG axis order, in particular latitude, " +"longitude order for WGS 84 geodetic coordinates, so it might be needed to" +" specify the :config:`GML_INVERT_AXIS_ORDER_IF_LAT_LONG=NO` configuration" +" option in those cases." +msgstr "" + +#: ../../source/drivers/vector/csw.rst:94 +msgid ":copy-config:`GML_INVERT_AXIS_ORDER_IF_LAT_LONG`" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:99 +msgid "Listing all the records of a CSW server:" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:105 +msgid "" +"Listing all the records of a CSW server with spatial and an attribute " +"filter on a give field:" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:112 +msgid "" +"Listing all the records of a CSW server that matches a text on any text " +"field:" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:119 +msgid "Listing all the records of a CSW server as ISO 19115/19119:" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:128 +msgid "`OGC CSW Standard `__" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:129 +#: ../../source/drivers/vector/wfs.rst:428 +msgid ":ref:`GML driver documentation `" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:4 +#: ../../source/drivers/vector/driver_summary.rst:57 +msgid "Microstation DGN" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:6 +msgid "DGN" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:10 +msgid "" +"Microstation DGN files from Microstation versions predating version 8.0 " +"are supported for reading (a :ref:`DGNv8 driver `, using " +"Teigha libraries, is available to read and write DGN v8 files). The " +"entire file is represented as one layer (named \"elements\")." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:15 +#: ../../source/drivers/vector/dgnv8.rst:19 +msgid "" +"DGN files are considered to have no georeferencing information through " +"OGR. Features will all have the following generic attributes:" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:18 +#: ../../source/drivers/vector/dgnv8.rst:22 +msgid "Type: The integer type code as listed below in supported elements." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:19 +msgid "Level: The DGN level number (0-63)." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:20 +#: ../../source/drivers/vector/dgnv8.rst:24 +msgid "GraphicGroup: The graphic group number." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:21 +#: ../../source/drivers/vector/dgnv8.rst:25 +msgid "ColorIndex: The color index from the dgn palette." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:22 +#: ../../source/drivers/vector/dgnv8.rst:26 +msgid "Weight: The drawing weight (thickness) for the element." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:23 +#: ../../source/drivers/vector/dgnv8.rst:27 +msgid "Style: The style value for the element." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:24 +msgid "EntityNum and MSLink: The Entity ID and MSLINK values in database linkage." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:25 +#: ../../source/drivers/vector/dgnv8.rst:28 +msgid "" +"ULink: User data linkage (multiple user data linkages may exist for each " +"element)." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:27 +msgid "" +"DGN files do not contain spatial indexes; however, the DGN driver does " +"take advantage of the extents information at the beginning of each " +"element to minimize processing of elements outside the current spatial " +"filter window when in effect." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:46 +msgid "Line (3): Line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:47 +#: ../../source/drivers/vector/dgnv8.rst:46 +msgid "Line String (4): Multi segment line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:48 +#: ../../source/drivers/vector/dgnv8.rst:47 +msgid "Shape (6): Polygon geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:49 +#: ../../source/drivers/vector/dgnv8.rst:49 +msgid "Curve (11): Approximated as a line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:50 +msgid "B-Spline (21): Treated (inaccurately) as a line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:51 +msgid "Arc (16): Approximated as a line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:52 +msgid "Ellipse (15): Approximated as a line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:53 +#: ../../source/drivers/vector/dgnv8.rst:54 +msgid "Text (17): Treated as a point geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:55 +#: ../../source/drivers/vector/dgnv8.rst:59 +msgid "" +"Generally speaking any concept of complex objects, and cells as " +"associated components is lost. Each component of a complex object or cell" +" is treated as a independent feature." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:60 +msgid "MSLINK" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:62 +msgid "" +"A DGN element can have a correspondence to a row in a database table, " +"known as database linkage or database attribute. The EntityNum refers to " +"the database table. The MSLink is the key to find the row in that table." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:68 +#: ../../source/drivers/vector/dgnv8.rst:64 +msgid "User data linkage" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:70 +msgid "" +"A DGN element may have multiple user data linkages. Each linkage has a " +"user id, application id and a number of words of data. The user data " +"linkage output reports the data for each different application id found " +"as raw hexadecimal words (16bits). The application id is the second word " +"of the raw data." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:76 +msgid "" +"Is up to the user how to decode the user raw data, depending on the " +"application id." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:80 +#: ../../source/drivers/vector/dgnv8.rst:75 +msgid "Styling Information" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:82 +#: ../../source/drivers/vector/dgnv8.rst:77 +msgid "" +"Some drawing information about features can be extracted from the " +"ColorIndex, Weight and Style generic attributes; however, for all " +"features an OGR style string has been prepared with the values encoded in" +" ready-to-use form for applications supporting OGR style strings." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:87 +#: ../../source/drivers/vector/dgnv8.rst:82 +msgid "" +"The various kinds of linear geometries will carry style information " +"indicating the color, thickness and line style (i.e. dotted, solid, etc)." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:91 +#: ../../source/drivers/vector/dgnv8.rst:86 +msgid "" +"Polygons (Shape elements) will carry styling information for the edge as " +"well as a fill color if provided. Fill patterns are not supported." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:94 +#: ../../source/drivers/vector/dgnv8.rst:89 +msgid "" +"Text elements will contain the text, angle, color and size information " +"(expressed in ground units) in the style string." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:100 +msgid "2D DGN files may be written with OGR with significant limitations:" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:102 +#: ../../source/drivers/vector/dgnv8.rst:104 +msgid "" +"Output features have the usual fixed DGN attributes. Attempts to create " +"any other fields will fail." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:104 +msgid "" +"Virtual no effort is currently made to translate OGR feature style " +"strings back into DGN representation information." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:106 +#: ../../source/drivers/vector/dgnv8.rst:110 +msgid "" +"POINT geometries that are not text (Text is NULL, and the feature style " +"string is not a LABEL) will be translated as a degenerate (0 length) line" +" element." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:109 +msgid "" +"Polygon, and multipolygon objects will be translated to simple polygons " +"with all rings other than the first discarded." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:111 +msgid "" +"Polygons and line strings with too many vertices will be split into a " +"group of elements prefixed with a Complex Shape Header or Complex Chain " +"Header element as appropriate." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:114 +msgid "" +"A seed file must be provided (or if not provided, " +"$PREFIX/share/gdal/seed_2d.dgn will be used). Many aspects of the " +"resulting DGN file are determined by the seed file, and cannot be " +"affected via OGR, such as initial view window." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:118 +msgid "" +"The various collection geometries other than MultiPolygon are completely " +"discarded at this time." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:120 +#: ../../source/drivers/vector/dgnv8.rst:113 +msgid "" +"Geometries which fall outside the \"design plane\" of the seed file will " +"be discarded, or corrupted in unpredictable ways." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:122 +msgid "" +"DGN files can only have one layer. Attempts to create more than one layer" +" in a DGN file will fail." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:126 +#: ../../source/drivers/vector/dgnv8.rst:117 +#: ../../source/drivers/vector/georss.rst:147 +#: ../../source/drivers/vector/gml.rst:646 +#: ../../source/drivers/vector/gmlas.rst:349 +#: ../../source/drivers/vector/gpkg.rst:272 +#: ../../source/drivers/vector/gpx.rst:253 +#: ../../source/drivers/vector/jsonfg.rst:116 +#: ../../source/drivers/vector/libkml.rst:73 +#: ../../source/drivers/vector/mapml.rst:59 +#: ../../source/drivers/vector/miramon.rst:289 +#: ../../source/drivers/vector/mvt.rst:226 +#: ../../source/drivers/vector/netcdf.rst:267 +#: ../../source/drivers/vector/ngw.rst:207 +#: ../../source/drivers/vector/pmtiles.rst:104 +#: ../../source/drivers/vector/shapefile.rst:341 +#: ../../source/drivers/vector/tiledb.rst:138 +msgid "Dataset creation options" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:128 +msgid "" +"|about-dataset-creation-options| The following dataset-creation options " +"are supported:" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:185 +msgid "`Dgnlib Page `__" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:186 +#: ../../source/drivers/vector/dgnv8.rst:233 +#: ../../source/drivers/vector/jml.rst:91 +#: ../../source/drivers/vector/pdf.rst:107 +msgid ":ref:`ogr_feature_style`" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:187 +msgid ":ref:`DGNv8 driver ` (using Teigha libraries)" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:4 +#: ../../source/drivers/vector/driver_summary.rst:62 +msgid "Microstation DGN v8" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:8 +msgid "DGNv8" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:10 +#: ../../source/drivers/vector/driver_summary.rst:65 +#: ../../source/drivers/vector/driver_summary.rst:70 +#: ../../source/drivers/vector/dwg.rst:8 +msgid "Open Design Alliance Teigha library" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:12 +msgid "" +"Microstation DGN files from Microstation version 8.0 are supported for " +"reading and writing. Each model of the file is represented by a OGR " +"layer." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:16 +msgid "" +"This driver requires to be built against the (non open source) Open " +"Design Alliance Teigha library." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:23 +msgid "Level: The DGN level number." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:42 +msgid "The following element types are supported in reading:" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:44 +msgid "Cell Header (2): used for polygons with holes" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:45 +msgid "Line (3): Line (2 points) geometry." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:48 +msgid "TextNode (7): Container of Text elements." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:50 +msgid "ComplexString (12): Treated as line string or compound curve." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:51 +msgid "ComplexShape (14): Treated as polygon or curve polygon." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:52 +msgid "Ellipse (15): Approximated as a line geometry or a circular string." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:53 +msgid "Arc (16): Approximated as a line geometry or a circular string." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:55 +msgid "B-Spline (21): Treated as a line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:56 +msgid "PointString (22): Treated as multi point." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:57 +msgid "Shared cell reference (35): Treated as point." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:66 +msgid "" +"A DGN element may have multiple user data linkages. Each linkage has a " +"user id, application id and a number of words of data. The user data " +"linkage output reports the data for each different application id." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:70 +msgid "" +"For unknown application ids, the raw data is reported as hexadecimal " +"words (16bit). Is up to the user how to decode the user data, depending " +"on the application id." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:95 +msgid "" +"The various metadata items that can be set in the DGN header with the " +"dataset creation options (see below) can be retrieved in the \"DGN\" " +"metadata domain." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:102 +msgid "DGN files may be written with OGR with limitations:" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:106 +msgid "" +"Translation from OGR feature style strings back into DGN representation " +"information is limited to a few properties of LABEL (text, font name, " +"size, angle, color), PEN (color) and BRUSH (fill color) tools." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:119 +#: ../../source/drivers/vector/geoconcept.rst:84 +#: ../../source/drivers/vector/georss.rst:149 +#: ../../source/drivers/vector/gml.rst:648 +#: ../../source/drivers/vector/gpx.rst:255 +#: ../../source/drivers/vector/jsonfg.rst:118 +#: ../../source/drivers/vector/kml.rst:94 +#: ../../source/drivers/vector/mapml.rst:61 +#: ../../source/drivers/vector/mitab.rst:108 +#: ../../source/drivers/vector/mvt.rst:228 +#: ../../source/drivers/vector/netcdf.rst:269 +#: ../../source/drivers/vector/pgdump.rst:37 +#: ../../source/drivers/vector/pmtiles.rst:106 +#: ../../source/drivers/vector/selafin.rst:328 +#: ../../source/drivers/vector/sqlite.rst:276 +msgid "" +"|about-dataset-creation-options| The following dataset creation options " +"are supported:" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:221 +#: ../../source/drivers/vector/dwg.rst:89 +msgid "Building" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:223 +#: ../../source/drivers/vector/dwg.rst:91 +msgid "" +"See :ref:`ODA platform support ` for building GDAL with ODA " +"support." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:232 +msgid ":ref:`DGN (v7) driver `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:16 +msgid ":ref:`AmigoCloud `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:21 +msgid ":ref:`Arrow `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:26 +msgid ":ref:`AVCBIN `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:31 +msgid ":ref:`AVCE00 `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:36 +msgid ":ref:`CAD `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:37 +#: ../../source/drivers/vector/driver_summary.rst:67 +#: ../../source/drivers/vector/dwg.rst:4 +msgid "AutoCAD DWG" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:41 +msgid ":ref:`CARTO `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:46 +msgid ":ref:`CSV `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:51 +msgid ":ref:`CSW `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:52 +msgid "OGC CSW (Catalog Service for the Web)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:56 +msgid ":ref:`DGN `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:61 +msgid ":ref:`DGNv8 `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:66 +msgid ":ref:`DWG `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:71 +msgid ":ref:`DXF `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:72 +#: ../../source/drivers/vector/dxf.rst:4 +msgid "AutoCAD DXF" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:76 +msgid ":ref:`EDIGEO `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:77 +#: ../../source/drivers/vector/edigeo.rst:4 +#: ../../source/drivers/vector/edigeo.rst:6 +msgid "EDIGEO" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:81 +msgid ":ref:`EEDA `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:82 +#: ../../source/drivers/vector/eeda.rst:4 +msgid "Google Earth Engine Data API" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:86 +msgid ":ref:`Elasticsearch `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:87 +#: ../../source/drivers/vector/elasticsearch.rst:4 +msgid "Elasticsearch: Geographically Encoded Objects for Elasticsearch" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:91 +msgid ":ref:`ESRIJSON `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:92 +#: ../../source/drivers/vector/esrijson.rst:4 +msgid "ESRIJSON / FeatureService driver" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:96 +msgid ":ref:`FileGDB `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:97 +#: ../../source/drivers/vector/filegdb.rst:4 +msgid "ESRI File Geodatabase (FileGDB)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:100 +#: ../../source/drivers/vector/filegdb.rst:8 +msgid "FileGDB API library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:101 +msgid ":ref:`FlatGeobuf `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:102 +#: ../../source/drivers/vector/flatgeobuf.rst:4 +#: ../../source/drivers/vector/flatgeobuf.rst:8 +msgid "FlatGeobuf" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:106 +msgid ":ref:`Geoconcept `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:107 +#: ../../source/drivers/vector/geoconcept.rst:4 +msgid "GeoConcept text export" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:111 +msgid ":ref:`GeoJSON `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:112 +#: ../../source/drivers/vector/geojson.rst:4 +#: ../../source/drivers/vector/geojson.rst:6 +msgid "GeoJSON" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:116 +msgid ":ref:`GeoJSONSeq `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:117 +#: ../../source/drivers/vector/geojsonseq.rst:4 +msgid "GeoJSONSeq: sequence of GeoJSON features" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:121 +msgid ":ref:`GeoRSS `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:122 +#: ../../source/drivers/vector/georss.rst:4 +msgid "GeoRSS : Geographically Encoded Objects for RSS feeds" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:125 +#: ../../source/drivers/vector/driver_summary.rst:155 +#: ../../source/drivers/vector/driver_summary.rst:195 +#: ../../source/drivers/vector/driver_summary.rst:205 +#: ../../source/drivers/vector/georss.rst:8 +#: ../../source/drivers/vector/gpx.rst:8 ../../source/drivers/vector/jml.rst:8 +#: ../../source/drivers/vector/kml.rst:8 +msgid "(read support needs libexpat)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:126 +msgid ":ref:`GML `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:127 +msgid "Geography Markup Language" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:130 +#: ../../source/drivers/vector/gml.rst:8 +msgid "(read support needs Xerces or libexpat)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:131 +msgid ":ref:`GMLAS `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:132 +msgid "Geography Markup Language (GML) driven by application schemas" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:135 +#: ../../source/drivers/vector/driver_summary.rst:185 +#: ../../source/drivers/vector/driver_summary.rst:190 +#: ../../source/drivers/vector/driver_summary.rst:260 +#: ../../source/drivers/vector/gmlas.rst:10 +#: ../../source/drivers/vector/ili.rst:10 ../../source/drivers/vector/nas.rst:8 +msgid "Xerces" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:136 +msgid ":ref:`GMT `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:137 +#: ../../source/drivers/vector/gmt.rst:4 +msgid "GMT ASCII Vectors (.gmt)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:141 +msgid ":ref:`GPKG `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:142 +msgid "GeoPackage vector" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:146 +msgid ":ref:`GPSBabel `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:147 +#: ../../source/drivers/vector/gpsbabel.rst:4 +#: ../../source/drivers/vector/gpsbabel.rst:6 +msgid "GPSBabel" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:150 +#: ../../source/drivers/vector/gpsbabel.rst:8 +msgid "(read support needs GPX driver and libexpat)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:151 +msgid ":ref:`GPX `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:152 +msgid "GPS Exchange Format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:156 +msgid ":ref:`GRASS `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:157 +#: ../../source/drivers/vector/grass.rst:4 +msgid "GRASS Vector Format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:161 +msgid ":ref:`GTFS `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:162 +msgid "General Transit Feed Specification" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:166 +msgid ":ref:`HANA `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:167 +#: ../../source/drivers/vector/hana.rst:4 +msgid "SAP HANA" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:170 +#: ../../source/drivers/vector/hana.rst:8 +msgid "odbc-cpp-wrapper" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:171 +msgid ":ref:`IDB `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:172 +#: ../../source/drivers/vector/idb.rst:4 ../../source/drivers/vector/idb.rst:6 +msgid "IDB" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:175 +#: ../../source/drivers/vector/idb.rst:8 +msgid "Informix DataBlade" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:176 +msgid ":ref:`IDRISI `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:177 +#: ../../source/drivers/vector/idrisi.rst:4 +msgid "Idrisi Vector (.VCT)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:181 +msgid ":ref:`INTERLIS 1 `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:182 +#: ../../source/drivers/vector/driver_summary.rst:187 +#: ../../source/drivers/vector/ili.rst:4 +msgid "\"INTERLIS 1\" and \"INTERLIS 2\" drivers" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:186 +msgid ":ref:`INTERLIS 2 `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:191 +msgid ":ref:`JML `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:192 +#: ../../source/drivers/vector/jml.rst:4 +msgid "JML: OpenJUMP JML format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:196 +msgid ":ref:`JSONFG `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:197 +msgid "OGC Features and Geometries JSON" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:201 +msgid ":ref:`KML `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:202 +msgid "Keyhole Markup Language" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:206 +msgid ":ref:`LIBKML `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:207 +#: ../../source/drivers/vector/libkml.rst:4 +msgid "LIBKML Driver (.kml .kmz)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:210 +#: ../../source/drivers/vector/libkml.rst:8 +msgid "libkml" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:211 +msgid ":ref:`LVBAG `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:212 +#: ../../source/drivers/vector/lvbag.rst:5 +msgid "Dutch Kadaster LV BAG 2.0 Extract" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:215 +#: ../../source/drivers/vector/driver_summary.rst:295 +#: ../../source/drivers/vector/driver_summary.rst:385 +#: ../../source/drivers/vector/driver_summary.rst:440 +#: ../../source/drivers/vector/lvbag.rst:11 +#: ../../source/drivers/vector/ods.rst:8 ../../source/drivers/vector/svg.rst:8 +#: ../../source/drivers/vector/xlsx.rst:9 +msgid "libexpat" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:216 +msgid ":ref:`MapML `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:217 +#: ../../source/drivers/vector/mapml.rst:4 +#: ../../source/drivers/vector/mapml.rst:8 +msgid "MapML" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:221 +msgid ":ref:`Memory `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:222 +#: ../../source/drivers/vector/memory.rst:4 +#: ../../source/drivers/vector/memory.rst:6 +msgid "Memory" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:226 +msgid ":ref:`MiraMonVector `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:227 +#: ../../source/drivers/vector/miramon.rst:4 +msgid "MiraMon Vector" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:231 +msgid ":ref:`MapInfo File `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:232 +#: ../../source/drivers/vector/mitab.rst:4 +msgid "MapInfo TAB and MIF/MID" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:236 +msgid ":ref:`MongoDBv3 `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:237 +#: ../../source/drivers/vector/mongodbv3.rst:4 +#: ../../source/drivers/vector/mongodbv3.rst:8 +msgid "MongoDBv3" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:240 +#: ../../source/drivers/vector/mongodbv3.rst:10 +msgid "Mongo CXX >= 3.4.0 client library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:241 +msgid ":ref:`MSSQLSpatial `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:242 +msgid "Microsoft SQL Server Spatial Database" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:245 +#: ../../source/drivers/vector/driver_summary.rst:290 +#: ../../source/drivers/vector/driver_summary.rst:340 +#: ../../source/drivers/vector/mssqlspatial.rst:8 +#: ../../source/drivers/vector/odbc.rst:8 +#: ../../source/drivers/vector/pgeo.rst:8 +msgid "ODBC library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:246 +msgid ":ref:`MVT `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:247 +#: ../../source/drivers/vector/mvt.rst:4 +msgid "MVT: Mapbox Vector Tiles" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:250 +#: ../../source/drivers/vector/mvt.rst:10 +msgid "(requires SQLite and GEOS for write support)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:251 +msgid ":ref:`MySQL `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:252 +#: ../../source/drivers/vector/mysql.rst:4 +#: ../../source/drivers/vector/mysql.rst:6 +msgid "MySQL" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:255 +#: ../../source/drivers/vector/mysql.rst:8 +msgid "MySQL library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:256 +msgid ":ref:`NAS `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:257 +msgid "ALKIS" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:261 +msgid ":ref:`netCDF `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:262 +msgid "Vector" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:266 +msgid ":ref:`NGW `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:271 +msgid ":ref:`UK .NTF `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:272 +#: ../../source/drivers/vector/ntf.rst:4 ../../source/drivers/vector/ntf.rst:6 +msgid "UK .NTF" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:276 +msgid ":ref:`OAPIF `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:277 +#: ../../source/drivers/vector/oapif.rst:4 +msgid "OGC API - Features" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:281 +msgid ":ref:`OCI `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:282 +#: ../../source/drivers/vector/oci.rst:4 +msgid "Oracle Spatial" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:285 +#: ../../source/drivers/vector/oci.rst:8 +msgid "OCI library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:286 +msgid ":ref:`ODBC `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:287 +#: ../../source/drivers/vector/odbc.rst:4 +msgid "ODBC RDBMS" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:291 +msgid ":ref:`ODS `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:292 +msgid "Open Document Spreadsheet" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:296 +msgid ":ref:`OGDI `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:297 +#: ../../source/drivers/vector/ogdi.rst:4 +msgid "OGDI Vectors" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:300 +#: ../../source/drivers/vector/ogdi.rst:8 +msgid "OGDI library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:301 +msgid ":ref:`OpenFileGDB `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:302 +#: ../../source/drivers/vector/openfilegdb.rst:4 +msgid "ESRI File Geodatabase vector (OpenFileGDB)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:306 +msgid ":ref:`OSM `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:307 +msgid "OpenStreetMap XML and PBF" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:310 +#: ../../source/drivers/vector/osm.rst:8 +msgid "libsqlite3 (and libexpat for OSM XML)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:311 +msgid ":ref:`Parquet `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:312 +#: ../../source/drivers/vector/parquet.rst:4 +msgid "(Geo)Parquet" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:315 +#: ../../source/drivers/vector/parquet.rst:10 +msgid "Parquet component of the Apache Arrow C++ library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:316 +msgid ":ref:`PDF `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:321 +msgid ":ref:`PDS `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:322 +msgid "Planetary Data Systems TABLE" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:326 +msgid ":ref:`PostgreSQL `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:327 +#: ../../source/drivers/vector/pg.rst:4 +msgid "PostgreSQL / PostGIS" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:330 +#: ../../source/drivers/vector/pg.rst:8 +msgid "PostgreSQL client library (libpq)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:331 +msgid ":ref:`PGDump `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:332 +#: ../../source/drivers/vector/pgdump.rst:4 +msgid "PostgreSQL SQL Dump" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:336 +msgid ":ref:`PGeo `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:337 +#: ../../source/drivers/vector/pgeo.rst:4 +msgid "ESRI Personal GeoDatabase" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:341 +msgid ":ref:`PLScenes `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:342 +#: ../../source/drivers/vector/plscenes.rst:4 +msgid "PLScenes (Planet Labs Scenes/Catalog API)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:346 +msgid ":ref:`PMTiles `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:347 +msgid "ProtoMaps Tiles" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:351 +msgid ":ref:`S57 `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:352 +#: ../../source/drivers/vector/s57.rst:4 +msgid "IHO S-57 (ENC)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:356 +msgid ":ref:`SDTS `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:361 +msgid ":ref:`Selafin `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:362 +#: ../../source/drivers/vector/selafin.rst:4 +msgid "Selafin files" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:366 +msgid ":ref:`ESRI Shapefile `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:367 +#: ../../source/drivers/vector/shapefile.rst:4 +msgid "ESRI Shapefile / DBF" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:371 +msgid ":ref:`SOSI `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:372 +#: ../../source/drivers/vector/sosi.rst:5 +msgid "Norwegian SOSI Standard" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:375 +#: ../../source/drivers/vector/sosi.rst:9 +msgid "FYBA library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:376 +msgid ":ref:`SQLite `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:377 +#: ../../source/drivers/vector/sqlite.rst:4 +msgid "SQLite / Spatialite RDBMS" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:380 +#: ../../source/drivers/vector/sqlite.rst:8 +msgid "libsqlite3 or libspatialite" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:381 +msgid ":ref:`SVG `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:382 +msgid "Scalable Vector Graphics" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:386 +msgid ":ref:`SXF `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:387 +#: ../../source/drivers/vector/sxf.rst:6 +msgid "SXF" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:391 +msgid ":ref:`TIGER `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:392 +#: ../../source/drivers/vector/tiger.rst:4 +msgid "U.S. Census TIGER/Line" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:396 +msgid ":ref:`TileDB `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:397 +msgid "TileDB vector" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:400 +#: ../../source/drivers/vector/tiledb.rst:11 +msgid "TileDB >= 2.7" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:401 +msgid ":ref:`TopoJSON `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:402 +#: ../../source/drivers/vector/topojson.rst:4 +msgid "TopoJSON driver" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:406 +msgid ":ref:`VDV `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:407 +msgid "VDV-451/VDV-452/INTREST Data Format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:411 +msgid ":ref:`VFK `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:412 +msgid "Czech Cadastral Exchange Data Format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:416 +msgid ":ref:`VRT `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:417 +msgid "Virtual Format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:421 +msgid ":ref:`WAsP `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:422 +msgid "WAsP .map format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:426 +msgid ":ref:`WFS `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:427 +msgid "OGC WFS service" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:431 +msgid ":ref:`XLS `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:432 +msgid "MS Excel format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:435 +#: ../../source/drivers/vector/xls.rst:8 +msgid "libfreexl" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:436 +msgid ":ref:`XLSX `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:437 +msgid "MS Office Open XML spreadsheet" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:441 +msgid ":ref:`XODR `" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:442 +msgid "OpenDRIVE Road Description Format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:445 +#: ../../source/drivers/vector/xodr.rst:10 +msgid "libOpenDRIVE >= 0.5.0, GEOS" +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:6 +msgid "DWG" +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:10 +msgid "" +"OGR supports reading most versions of AutoCAD DWG when built with the " +"Open Design Alliance Teigha library. DWG is a binary working format used " +"for AutoCAD drawings. A reasonable effort has been made to make the OGR " +"DWG driver work similarly to the OGR DXF driver which shares a common " +"data model. The entire contents of the .dwg file is represented as a " +"single layer named \"entities\"." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:20 +#: ../../source/drivers/vector/dxf.rst:32 +msgid "Layer: The name of the DXF layer. The default layer is \"0\"." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:21 +msgid "" +"SubClasses: Where available, a list of classes to which an element " +"belongs." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:25 +#: ../../source/drivers/vector/dxf.rst:48 +msgid "Linetype: Where available, the line type used for this entity." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:26 +#: ../../source/drivers/vector/dxf.rst:49 +msgid "EntityHandle: The hexadecimal entity handle. A sort of feature id." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:27 +#: ../../source/drivers/vector/dxf.rst:50 +msgid "Text: The text of labels." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:29 +msgid "" +"A reasonable attempt is made to preserve line color, line width, text " +"size and orientation via OGR feature styling information when translating" +" elements. Currently no effort is made to preserve fill styles or complex" +" line style attributes." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:34 +#: ../../source/drivers/vector/dxf.rst:176 +msgid "" +"The :config:`OGR_ARC_STEPSIZE` and :config:`OGR_ARC_MAX_GAP` " +"configurations options control the approximation of arcs, ellipses, " +"circles and rounded polylines as linestrings." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:53 +msgid "" +"A new layer will be available called blocks. It will contain one or more " +"features for each block defined in the file. In addition to the usual " +"attributes, they will also have a BlockName attribute indicate what block" +" they are part of." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:57 +msgid "" +"The entities layer will have new attributes BlockName, BlockScale, " +"BlockAngle and BlockAttributes." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:59 +msgid "" +"BlockAttributes will be a list of (tag x value) pairs of all visible " +"attributes (JSON encoded)." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:61 +msgid "" +"block referenced will populate these new fields with the corresponding " +"information (they are null for all other entities)." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:63 +msgid "" +"block references will not have block geometry inlined - instead they will" +" have a point geometry for the insertion point." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:66 +msgid "" +"The intention is that with :config:`DWG_INLINE_BLOCKS` disabled, the " +"block references will remain as references and the original block " +"definitions will be available via the blocks layer." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:6 +msgid "DXF" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:10 +msgid "" +"DXF is an ASCII format used for interchanging AutoCAD drawings between " +"different software packages. OGR supports reading DXF files generated by " +"all recent versions of AutoCAD, and writing DXF files that are compatible" +" with AutoCAD 2004 and later." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:15 +msgid "" +"DXF files are considered to have no georeferencing information through " +"OGR." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:26 +msgid "DXF Reader" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:28 +msgid "" +"By default, the entire contents of the file are represented as a single " +"OGR layer named \"entities\". Features will all have the following " +"generic fields:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:33 +msgid "" +"PaperSpace: 1 if the entity is located on a layout (paper space), NULL " +"otherwise." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:35 +msgid "SubClasses: Where available, a list of classes to which an entity belongs." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:37 +msgid "" +"ExtendedEntity (GDAL <= 2.2.x): The values of extended entity attributes " +"all appended to form a single text field, where available." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:39 +msgid "" +"RawCodeValues (GDAL >= 2.3.0): A string list containing all group codes " +"and values that are not handled by the DXF reader. Only available when " +"the configuration option :config:`DXF_INCLUDE_RAW_CODE_VALUES=TRUE`." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:53 +msgid "Supported Entities" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:55 +msgid "The following entity types are supported:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:57 +msgid "POINT: Produces a simple POINT geometry feature." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:58 +#, python-format +msgid "" +"MTEXT, TEXT: Produces a POINT feature with LABEL style information. The " +"style string may include the following parameters: f s t a c w p dx dy bo" +" it. Text positioning might not precisely match CAD software (especially " +"the vertical alignment of MTEXT), as calculation of the exact position " +"would require GDAL to be aware of the font metrics. By default, character" +" escapes such as %%p are honored where applicable, and MTEXT control " +"sequences like \\\\Wx.xx; are stripped. To disable this behavior and " +"retrieve the raw text values, set the configuration option " +":config:`DXF_TRANSLATE_ESCAPE_SEQUENCES=FALSE`." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:72 +msgid "" +"LINE, POLYLINE, LWPOLYLINE: Translated as a LINESTRING. Rounded polylines" +" (those with their vertices' bulge attributes set) will be tessellated. " +"Single-vertex polylines are translated to POINT. Polyface meshes are " +"translated as POLYHEDRALSURFACE geometries." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:76 +msgid "MLINE:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:78 +msgid "" +"(GDAL >= 2.3.0) Translated as a MULTILINESTRING. Only the geometry is " +"reconstructed; styling applied to individual line elements within the " +"MLINE is ignored. Fill colors and start/end caps are also omitted." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:82 +#: ../../source/drivers/vector/dxf.rst:166 +msgid "(GDAL <= 2.2.x) No support." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:84 +msgid "" +"CIRCLE, ELLIPSE, ARC, SPLINE, (GDAL >= 2.3.0) HELIX: Translated as a " +"LINESTRING, tessellating the curve into line segments. (GDAL >= 2.3.0) " +"CIRCLEs with nonzero \"thickness\" (cylinders) are approximated as a " +"POLYHEDRALSURFACE." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:88 +msgid "" +"INSERT: By default, the block definition referenced by the INSERT will be" +" inserted as a compound geometry (for example, a MULTILINESTRING for a " +"block containing many lines, or a GEOMETRYCOLLECTION for a block that " +"contains points and lines). If the block contains TEXT or MTEXT entities," +" they are not merged into the compound geometry and are instead returned " +"as separate features." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:95 +msgid "" +"Three configuration options are available to control the behavior of " +"INSERT entities:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:118 +msgid "ATTDEF, ATTRIB:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:120 +msgid "" +"(GDAL >= 2.3.0) Attributes (ATTRIB) are treated as TEXT entities, and " +"attribute definitions (ATTDEF) inside blocks are ignored. The behavior is" +" different when :config:`DXF_INLINE_BLOCKS` is false (see below)." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:123 +msgid "" +"(GDAL <= 2.2.x) ATTDEF entities are treated as TEXT. ATTRIB entities are " +"not supported." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:126 +msgid "" +"HATCH: Line and arc boundaries are collected as a polygon geometry, but " +"no effort is currently made to represent the fill style of HATCH " +"entities. Behavior is affected by the following configuration option:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:137 +msgid "" +"(GDAL <= 2.2.x) Only line and polyline boundary paths are translated " +"correctly." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:140 +msgid "" +"3DFACE, SOLID, (GDAL >= 2.3.0) TRACE: Translated as POLYGON, except for " +"SOLID and TRACE entities with only one distinct vertex (translated as " +"POINT) or two distinct vertices (translated as LINESTRING)." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:144 +msgid "DIMENSION:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:146 +msgid "" +"(GDAL >= 2.3.0) The DXF format allows each DIMENSION entity to reference " +"an \"anonymous\" block (a block whose name starts with \\*D) that " +"contains the geometry of the DIMENSION. If present, this anonymous block " +"will be inlined at the required position. Otherwise, fallback will occur " +"to a simple DIMENSION renderer that explodes a linear dimension as a " +"MULTILINESTRING feature. Arrowheads, if present, are translated as one or" +" more additional features. The fallback renderer will render nonlinear " +"dimensions as if they were linear." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:155 +msgid "" +"(GDAL <= 2.2.x) Dimensions are translated as a MULTILINESTRING and a " +"POINT for the text." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:158 +msgid "LEADER, MULTILEADER:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:160 +msgid "" +"(GDAL >= 2.3.0) The leader line is translated as a LINESTRING (LEADER) or" +" MULTILINESTRING (MULTILEADER). Arrowheads, if present, are translated as" +" one or more additional features. Text for MULTILEADER entities is " +"translated into a POINT feature with a label. Block content for " +"MULTILEADERS is treated as for INSERT. Spline leaders are tessellated " +"into line segments." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:168 +msgid "3DSOLID, REGION, BODY, SURFACE: See below." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:170 +msgid "" +"A reasonable attempt is made to preserve color, line width (lineweight), " +"line type, text size and orientation via OGR feature styling information " +"when translating entities. Currently no effort is made to preserve " +"complex line types (those that include text or shapes) or HATCH fill " +"styles." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:180 +msgid "" +"For splines, the interpolated polyline contains eight vertices for each " +"control point." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:183 +msgid "" +"Object coordinate systems (OCS), also known as \"extrusions\", are " +"supported for all entities to which they apply as per the DXF " +"specification, except DIMENSION, LEADER and MULTILEADER. These three " +"entity types also currently lack support for elevations; the geometries " +"will always be 2D." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:190 +msgid "DXF_INLINE_BLOCKS" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:192 +msgid "" +"The default behavior is for INSERT entities to be exploded with the " +"geometry of the BLOCK they reference. However, if the " +":config:`DXF_INLINE_BLOCKS` configuration option is set to the value " +"FALSE, then the behavior is different as described here." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:197 +msgid "" +"A new layer will be available called \"blocks\". It will contain one or " +"more features for each BLOCK defined in the file. In addition to the " +"usual fields, they will also have a Block field indicating what block " +"they are part of. (Note, in GDAL 2.2.x and earlier this field was called " +"BlockName.)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:202 +msgid "" +"(GDAL >= 2.3.0) ATTDEF entities in the blocks layer will have an " +"AttributeTag field, giving the tag of the ATTDEF entity." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:204 +msgid "The entities layer will have several new fields:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:206 +msgid "BlockName: The name of the referenced block." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:207 +msgid "BlockScale: The X, Y, and Z scale factors." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:208 +msgid "BlockAngle: The angle of the block in degrees." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:209 +msgid "" +"BlockOCSNormal (GDAL >= 2.3.0): The unit normal vector of the object " +"coordinate system (OCS) of the INSERT entity." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:211 +msgid "" +"BlockOCSCoords (GDAL >= 2.3.0): The OCS coordinates of the insertion " +"point." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:213 +msgid "" +"BlockAttributes (GDAL >= 2.3.0): The text content of attributes " +"associated with this block. Each entry in this string list contains an " +"attribute tag, followed by a space, followed by the text for that " +"attribute (which may be empty)." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:218 +msgid "" +"INSERT entities will populate these new fields with the corresponding " +"information (they are null for all other entities)." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:220 +msgid "" +"INSERT entities will not have block geometry inlined - instead they will " +"have a POINT geometry for the insertion point." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:223 +msgid "" +"The intention is that with :config:`DXF_INLINE_BLOCKS` disabled, the " +"block references will remain as references and the original block " +"definitions will be available via the blocks layer. On export this " +"configuration will result in the creation of similar blocks." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:229 +msgid "3D Extensibility" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:231 +msgid "" +"DXF files may contain 3DSOLID, REGION, BODY and SURFACE entities, which " +"contain 3D modelling data in the proprietary Autodesk ShapeManager (ASM) " +"format, a broadly compatible fork of the ACIS format. GDAL cannot " +"transform these entities into OGR geometries, so they are skipped by " +"default." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:236 +msgid "This behavior can be controlled with the following configuration option:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:246 +msgid "ASMData: A binary field that contains the ASM data." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:247 +msgid "" +"ASMTransform: A column-major list of 12 real values indicating the affine" +" transformation to be applied to the entity." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:250 +msgid "" +"This feature only works for DXF files in AutoCAD 2013 (AC1027) format and" +" later." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:254 +msgid "Character Encodings" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:256 +msgid "" +"Normally DXF files are in the ANSI_1252 / Win1252 encoding. GDAL/OGR " +"attempts to translate this to UTF-8 when reading and back into ANSI_1252 " +"when writing. DXF files can also have a header field ($DWGCODEPAGE) " +"indicating the encoding of the file. An attempt is made to use this to " +"recode other code pages to UTF-8. Whether this works will depend on the " +"code page naming and whether GDAL/OGR is built against the iconv library " +"for character recoding." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:264 +msgid "" +"In some cases the $DWGCODEPAGE setting in a DXF file will be wrong, or " +"unrecognised by OGR. In this case, :config:`DXF_ENCODING` may be used to " +"override what id will be used by OGR in transcoding:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:278 +msgid "DXF Writer" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:280 +msgid "" +"DXF files are written in AutoCAD 2004 format. A standard header " +"(everything up to the ENTITIES keyword) is written from the " +"$GDAL_DATA/header.dxf file, and the $GDAL_DATA/trailer.dxf file is added " +"after the entities. Only one OGR layer can be used to create the output " +"file (but many DXF layers can be created - see below)." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:286 +msgid "" +"Point features with LABEL styling are written as MTEXT entities based on " +"the styling information." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:288 +msgid "Point features without LABEL styling are written as POINT entities." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:289 +msgid "" +"LineString and MultiLineString features are written as one or more " +"LWPOLYLINE entities, closed in the case of polygon rings. If the geometry" +" does not have a constant elevation, a POLYLINE entity is written. An " +"effort is made to preserve line width and color." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:293 +msgid "" +"Polygon, Triangle and MultiPolygon features are written as HATCH entities" +" by default. To write these features as LWPOLYLINE/POLYLINE entities " +"instead, set the configuration option :config:`DXF_WRITE_HATCH=FALSE`:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:304 +msgid "" +"You may need to do this if your geometries do not have a constant " +"elevation, as the DXF HATCH entity cannot represent such geometries." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:308 +msgid "" +"Only the first tool (PEN, BRUSH, etc) in the style string is read. The " +"following style string parameters are understood:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:314 +#: ../../source/drivers/vector/pdf.rst:57 +msgid "Tool" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:315 +msgid "Available on geometry types" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:316 +msgid "Supported parameters" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:317 +#: ../../source/drivers/vector/pdf.rst:60 +msgid "PEN" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:318 +msgid "Point, (Multi)LineString" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:319 +#: ../../source/drivers/vector/pdf.rst:61 +msgid "color (c); width (w); dash pattern (p)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:320 +#: ../../source/drivers/vector/pdf.rst:63 +msgid "BRUSH" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:321 +msgid "(Multi)Polygon, Triangle" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:322 +#: ../../source/drivers/vector/pdf.rst:64 +msgid "foreground color (fc)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:323 +#: ../../source/drivers/vector/pdf.rst:74 +msgid "SYMBOL" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:324 +#: ../../source/drivers/vector/dxf.rst:327 +#: ../../source/drivers/vector/ogdi.rst:14 +msgid "Point" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:325 +msgid "color (c)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:326 +#: ../../source/drivers/vector/pdf.rst:66 +msgid "LABEL" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst +msgid "GDAL >= 2.3.0: text (t); font name (f); font size (s), treated as cap" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst +msgid "height; bold (bo); italic (it); text color (c); x and y offsets (dx," +msgstr "" + +#: ../../source/drivers/vector/dxf.rst +msgid "dy); angle (a); anchor point (p); stretch (w)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst +msgid "GDAL <= 2.2.x: text (t); font size (s), treated as cap height; text" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst +msgid "color (c); angle (a); anchor point (p)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:334 +msgid "" +"|about-dataset-creation-options| The driver supports the following " +"dataset creation options:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:349 +msgid "" +"The header and trailer templates can be complete DXF files. The driver " +"will scan them and only extract the needed portions (portion before or " +"after the ENTITIES section)." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:354 +msgid "Block References" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:356 +msgid "" +"It is possible to export a \"blocks\" layer to DXF in addition to the " +"\"entities\" layer in order to produce actual DXF BLOCKs definitions in " +"the output file. It is also possible to write INSERT entities if a block " +"name is provided for an entity. To make this work the following " +"conditions apply:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:362 +msgid "" +"A \"blocks\" layer may be created, and it must be created before the " +"entities layer." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:364 +msgid "" +"The entities in the blocks layer should have the Block field populated. " +"(Note, in GDAL 2.2.x and earlier this attribute was called BlockName.)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:367 +msgid "" +"Objects to be written as INSERTs in the entities layer should have a " +"POINT geometry, and the BlockName field set. You may also set BlockAngle," +" BlockScale, BlockOCSNormal and BlockOCSCoords (see above under " +":config:`DXF_INLINE_BLOCKS` for details). If BlockOCSCoords is set to a " +"list of 3 real numbers, it is used as the location of the block; in this " +"situation the position of the POINT geometry is ignored." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:373 +msgid "" +"If a block (name) is already defined in the template header, that will be" +" used regardless of whether a new definition was provided in the blocks " +"layer." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:377 +msgid "" +"The intention is that a simple translation from DXF to DXF with " +":config:`DXF_INLINE_BLOCKS` set to FALSE will approximately reproduce the" +" original blocks and keep INSERT entities as INSERT entities rather than " +"exploding them." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:383 +msgid "Layer Definitions" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:385 +msgid "" +"When writing entities, if populated the Layer field is used to set the " +"written entities layer. If the layer is not already defined in the " +"template header then a new layer definition will be introduced, copied " +"from the definition of the default layer (\"0\")." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:391 +msgid "Linetype Definitions" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:393 +msgid "" +"When writing linestring geometries, the following rules apply with regard" +" to linetype (dash pattern) definitions." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:396 +msgid "" +"If the Linetype field is set on a written feature, and that linetype is " +"already defined in the template header, then it will be referenced from " +"the entity. If a style string is present with a \"p\" pattern " +"proportional to the linetype defined in the header, a linetype scale " +"value is written." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:401 +msgid "" +"If the Linetype field is set, but the linetype is not defined in the " +"header template, then a definition will be added if the feature has an " +"OGR style string with a PEN tool and a \"p\" pattern setting." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:404 +msgid "" +"If the feature has no Linetype field set, but it does have an OGR style " +"string with a PEN tool with a \"p\" pattern set, then an automatically " +"named linetype will be created in the output file. Or, if an appropriate " +"linetype was previously created, that linetype will be referenced, with a" +" linetype scale if required." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:410 +msgid "" +"The intention is that \"dot dash\" style patterns will be preserved when " +"written to DXF and that specific linetypes can be predefined in the " +"header template, and referenced using the Linetype field if desired." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:414 +msgid "" +"It is assumed that patterns are using \"g\" (georeferenced) units for " +"defining the line pattern. If not, the scaling of the DXF patterns is " +"likely to be wrong - potentially very wrong." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:419 +msgid "Units" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:421 +msgid "" +"GDAL writes DXF files with measurement units set to \"Imperial - " +"Inches\". If you need to change the units, edit the `$MEASUREMENT " +"`__ and `$INSUNITS " +"`__ variables in the header" +" template." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:434 +msgid "" +"`List of known issues " +"`__" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:437 +msgid "" +"`AutoCAD 2000 DXF Reference " +"`__" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:440 +msgid "" +"`AutoCAD 2014 DXF Reference " +"`__" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:10 +msgid "" +"This driver reads files encoded in the French EDIGEO exchange format, a " +"text based file format aimed at exchanging geographical information " +"between GIS, with powerful description capabilities, topology modeling, " +"etc." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:15 +msgid "" +"The driver has been developed to read files of the French PCI (Plan " +"Cadastral Informatisé - Digital Cadastral Plan) as produced by the DGI " +"(Direction Générale des Impots - General Tax Office). The driver should " +"also be able to open other EDIGEO based products." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:20 +msgid "" +"The driver must be provided with the .THF file describing the EDIGEO " +"exchange and it will read the associated .DIC, .GEO, .SCD, .QAL and .VEC " +"files." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:24 +msgid "" +"In order the SRS of the layers to be correctly built, the IGNF file that " +"contains the definition of IGN SRS must be placed in the directory of " +"PROJ resource files." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:28 +msgid "" +"The whole set of files will be parsed into memory. This may be a " +"limitation if dealing with big EDIGEO exchanges." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:56 +msgid "Labels" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:58 +msgid "" +"For EDIGEO PCI files, the labels are contained in the ID_S_OBJ_Z_1_2_2 " +"layer. OGR will export styling following the :ref:`ogr_feature_style`." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:61 +msgid "It will also add the following fields :" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:63 +msgid "OGR_OBJ_LNK: the id of the object that is linked to this label" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:64 +msgid "OBJ_OBJ_LNK_LAYER: the name of the layer of the linked object" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:65 +msgid "" +"OGR_ATR_VAL: the value of the attribute to display (found in the ATR " +"attribute of the OGR_OBJ_LNK object)" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:67 +msgid "" +"OGR_ANGLE: the rotation angle in degrees (0 = horizontal, counter-clock-" +"wise oriented)" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:69 +msgid "" +"OGR_FONT_SIZE: the value of the HEI attribute multiplied by the value of " +"the configuration option :config:`OGR_EDIGEO_FONT_SIZE_FACTOR`." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:72 +msgid "" +"Combined with the FON (font family) attributes, they can be used to " +"define the styling in QGIS for example." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:75 +msgid "" +"By default, OGR will create specific layers (xxx_LABEL) to dispatch into " +"the various labels of the ID_S_OBJ_Z_1_2_2 layer according to the value " +"of xxx=OBJ_OBJ_LNK_LAYER. This can be disabled by setting " +":config:`OGR_EDIGEO_CREATE_LABEL_LAYERS` to NO." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:83 +msgid "" +"`Introduction to the EDIGEO standard " +"`__ (in French)" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:85 +msgid "" +"`EDIGEO standard - AFNOR NF Z 52000 " +"`__ (in " +"French)" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:88 +msgid "" +"`Standard d'échange des objets du PCI selon la norme EDIGEO " +"`__ (in French)" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:91 +msgid "" +"`Homepage of the French Digital Cadastral Plan " +"`__ (in French)" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:93 +msgid "" +"`Geotools EDIGEO module description " +"`__ (in English), `unmaintained " +"and removed `__" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:96 +msgid "" +"`Sample of EDIGEO data " +"`__" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:8 +msgid "EEDA" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:12 +msgid "" +"The driver supports read-only operations to list images and their " +"metadata as a vector layer, using Google Earth Engine REST API." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:23 +msgid "The minimal syntax to open a datasource is:" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:29 +msgid "" +"where collection is something like projects/earthengine-" +"public/assets/COPERNICUS/S2." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:48 +msgid "" +"Authentication Bearer header passed through the EEDA_BEARER or " +":config:`EEDA_BEARER_FILE` configuration options." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:56 +msgid "" +"Finally if none of the above method succeeds, the code will check if the " +"current machine is a Google Compute Engine instance, and if so will use " +"the permissions associated to it (using the default service account " +"associated with the VM). To force a machine to be detected as a GCE " +"instance you can set :config:`CPL_MACHINE_IS_GCE` to YES." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:68 +msgid ":copy-config:`EEDA_BEARER`" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:70 +msgid ":copy-config:`EEDA_BEARER_FILE`" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:72 +msgid ":copy-config:`GOOGLE_APPLICATION_CREDENTIALS`" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:74 +msgid ":copy-config:`EEDA_PRIVATE_KEY`" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:76 +msgid ":copy-config:`EEDA_PRIVATE_KEY_FILE`" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:78 +msgid ":copy-config:`EEDA_CLIENT_EMAIL`" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:89 +#: ../../source/drivers/vector/plscenes_data_v1.rst:134 +msgid "Attributes" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:91 +msgid "" +"The layer field definition is built by requesting a single image from the" +" collection and guessing the schema from its \"properties\" element. The " +"\"eedaconf.json\" file from the GDAL configuration will also be read to " +"check if the collection schema is described in it, in which case the " +"above mentioned schema guessing will not done." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:97 +msgid "The following attributes will always be present:" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:103 +msgid "Field name" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:103 +msgid "Meaning" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:103 +msgid "Server-side filter compatible" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:105 +msgid "name" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:105 +#: ../../source/drivers/vector/eeda.rst:109 +#: ../../source/drivers/vector/eeda.rst:112 +#: ../../source/drivers/vector/eeda.rst:114 +#: ../../source/drivers/vector/eeda.rst:143 +#: ../../source/drivers/vector/eeda.rst:145 +#: ../../source/drivers/vector/netcdf.rst:84 +#: ../../source/drivers/vector/netcdf.rst:125 +#: ../../source/drivers/vector/netcdf.rst:126 +#: ../../source/drivers/vector/selafin.rst:103 +msgid "String" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:105 +msgid "" +"Image name (e.g. projects/earthengine-public/ " +"assets/COPERNICUS/S2/20170430T190351\\_ 20170430T190351_T10SEG)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:109 +msgid "id" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:109 +msgid "" +"Image ID; equivalent to name without the \"projects/\\*/assets/\" prefix " +"(e.g. users/USER/ASSET)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:112 +msgid "path" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:112 +msgid "(Deprecated) Image path; equivalent to id" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:114 +msgid "gdal_dataset" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:114 +msgid "" +"GDAL dataset name (e.g. EEDAI:projects/earthengine-public/ " +"assets/COPERNICUS/S2/ 20170430T190351_20170430T190351\\_ T10SEG) that can" +" be opened with the :ref:`raster.eedai` driver" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:121 +msgid "startTime" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:121 +#: ../../source/drivers/vector/eeda.rst:124 +#: ../../source/drivers/vector/eeda.rst:127 +#: ../../source/drivers/vector/netcdf.rst:92 +#: ../../source/drivers/vector/netcdf.rst:136 +msgid "DateTime" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:121 +msgid "Acquisition start date" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:121 +msgid "**Yes** (restricted to >= comparison on top level)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:124 +msgid "endTime" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:124 +msgid "Acquisition end date" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:124 +msgid "**Yes** (restricted to <= comparison on top level)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:127 +msgid "updateTime" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:127 +msgid "Update date" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:129 +msgid "sizeBytes" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:129 +#: ../../source/drivers/vector/netcdf.rst:88 +#: ../../source/drivers/vector/netcdf.rst:131 +#: ../../source/drivers/vector/netcdf.rst:132 +msgid "Integer64" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:129 +msgid "File size in bytes" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:131 +msgid "band_count" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:131 +#: ../../source/drivers/vector/eeda.rst:133 +#: ../../source/drivers/vector/eeda.rst:135 +#: ../../source/drivers/vector/netcdf.rst:85 +#: ../../source/drivers/vector/netcdf.rst:122 +#: ../../source/drivers/vector/netcdf.rst:123 +#: ../../source/drivers/vector/netcdf.rst:128 +#: ../../source/drivers/vector/netcdf.rst:129 +#: ../../source/drivers/vector/selafin.rst:80 +msgid "Integer" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:131 +msgid "Number of bands" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:133 +msgid "band_max_width" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:133 +msgid "Maximum width among bands" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:135 +msgid "band_max_height" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:135 +msgid "Maximum height among bands" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:137 +msgid "band_min_pixel_size" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:137 +#: ../../source/drivers/vector/eeda.rst:139 +#: ../../source/drivers/vector/eeda.rst:141 +#: ../../source/drivers/vector/netcdf.rst:89 +#: ../../source/drivers/vector/netcdf.rst:133 +#: ../../source/drivers/vector/netcdf.rst:135 +msgid "Real" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:137 +msgid "Minimum pixel size among bands" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:139 +msgid "band_upper_left_x" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:139 +msgid "X origin (only set if equal among all bands)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:141 +msgid "band_upper_left_y" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:141 +msgid "Y origin (only set if equal among all bands)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:143 +msgid "band_crs" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:143 +msgid "CRS as EPSG:XXXX or WKT (only set if equal among all bands)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:145 +msgid "other_properties" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:145 +msgid "" +"Serialized JSON dictionary with key/value pairs where key is not a " +"standalone field" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:149 +msgid "" +"\"Server-side filter compatible\" means that when this field is included " +"in an attribute filter, it is forwarded to the server (otherwise only " +"client-side filtering is done)." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:156 +msgid "" +"The footprint of each image is reported as a MultiPolygon with a " +"longitude/latitude WGS84 coordinate system (EPSG:4326)." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:162 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server. It also makes the same for simple attribute filters set with" +" SetAttributeFilter(). The 3 boolean operators (AND, OR, NOT) and the " +"comparison operators (=, <>, <, <=, > and >=) are supported." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:170 +msgid "" +"Features are retrieved from the server by chunks of 1000 by default (and " +"this is the maximum value accepted by the server). This number can be " +"altered with the :config:`EEDA_PAGE_SIZE` configuration option." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:175 +msgid "Extent and feature count" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:177 +msgid "" +"The reported extent and feature count will always be respectively " +"(-180,-90,180,90) and -1, given there is no way to get efficient answer " +"to those queries from the server." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:184 +msgid "Listing all images available:" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:196 +msgid "Listing all images under a point of (lat,lon)=(40,-100) :" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:202 +msgid "Listing all images available matching criteria :" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:211 +msgid ":ref:`Google Earth Engine Data API Image driver `" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:6 +msgid "Elasticsearch" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:10 +msgid "Driver is read-write starting with GDAL 2.1" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:13 +msgid "" +"As of GDAL 2.1, Elasticsearch 1.X and, partially, 2.X versions are " +"supported (5.0 known not to work). GDAL 2.2 adds supports for " +"Elasticsearch 2.X and 5.X" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:15 +msgid "" +"`Elasticsearch `__ is an Enterprise-level " +"search engine for a variety of data sources. It supports full-text " +"indexing and geospatial querying of those data in a fast and efficient " +"manor using a predefined REST API." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:28 +msgid "Opening dataset name syntax" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:30 +msgid "" +"Starting with GDAL 2.1, the driver supports reading existing indices from" +" a Elasticsearch host. There are two main possible syntaxes to open a " +"dataset:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:34 +msgid "Using *ES:http://hostname:port* (where port is typically 9200)" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:35 +msgid "Using *ES:* with the open options to specify HOST and PORT" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:38 +msgid "Layer open options" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:147 +msgid "Elasticsearch vs OGR concepts" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:149 +msgid "" +"Each mapping type inside a Elasticsearch index will be considered as a " +"OGR layer. A Elasticsearch document is considered as a OGR feature." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:153 +#: ../../source/drivers/vector/georss.rst:72 +msgid "Field definitions" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:155 +msgid "" +"Fields are dynamically mapped from the input OGR data source. However, " +"the driver will take advantage of advanced options within Elasticsearch " +"as defined in a `field mapping file " +"`__." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:160 +msgid "" +"The mapping file allows you to modify the mapping according to the " +"`Elasticsearch field-specific types " +"`__. There are many options to choose from, however, most of " +"the functionality is based on all the different things you are able to do" +" with text fields within Elasticsearch." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:172 +msgid "Geometry types" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:174 +msgid "" +"In GDAL 2.0 and earlier, the driver was limited in the geometry it " +"handles: even if polygons were provided as input, they were stored as " +"`geo point " +"`__ and the \"center\" of the polygon is " +"used as value of the point. Starting with GDAL 2.1, `geo_shape " +"`__ is used to store all geometry types (except curve" +" geometries that are not handled by Elasticsearch and will be " +"approximated to their linear equivalents)." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:188 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:191 +msgid "" +"Starting with GDAL 2.2, SQL attribute filters set with " +"SetAttributeFilter() are converted to `Elasticsearch filter syntax " +"`__. They will be combined with the potentially defined " +"spatial filter." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:196 +msgid "" +"It is also possible to directly use a Elasticsearch filter by setting the" +" string passed to SetAttributeFilter() as a JSON serialized object, e.g." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:204 +msgid "" +"Note: if defining directly an Elastic Search JSON filter, the spatial " +"filter specified through SetSpatialFilter() will be ignored, and must " +"thus be included in the JSON filter if needed." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:211 +msgid "" +"Features are retrieved from the server by chunks of 100. This can be " +"altered with the BATCH_SIZE open option." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:215 +#: ../../source/drivers/vector/gml.rst:175 +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:13 +#: ../../source/drivers/vector/libkml.rst:276 +#: ../../source/drivers/vector/mongodbv3.rst:172 +msgid "Schema" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:217 +msgid "" +"When reading a Elastic Search index/type, OGR must establish the schema " +"of attribute and geometry fields, since OGR has a fixed schema concept." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:220 +msgid "" +"In the general case, OGR will read the mapping definition and the first " +"100 documents (can be altered with the " +":oo:`FEATURE_COUNT_TO_ESTABLISH_FEATURE_DEFN` open option) of the " +"index/type and build the schema that best fit to the found fields and " +"values." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:225 +msgid "" +"It is also possible to set the :oo:`JSON_FIELD=YES` open option so that a" +" \\_json special field is added to the OGR schema. When reading Elastic " +"Search documents as OGR features, the full JSON version of the document " +"will be stored in the \\_json field. This might be useful in case of " +"complex documents or with data types that do not translate well in OGR " +"data types. On creation/update of documents, if the \\_json field is " +"present and set, its content will be used directly (other fields will be " +"ignored)." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:235 +#: ../../source/drivers/vector/mongodbv3.rst:199 +msgid "Feature ID" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:237 +msgid "" +"Elastic Search have a special \\_id field that contains the unique ID of " +"the document. This field is returned as an OGR field, but cannot be used " +"as the OGR special FeatureID field, which must be of integer type. By " +"default, OGR will try to read a potential 'ogc_fid' field to set the OGR " +"FeatureID. The name of this field to look up can be set with the FID open" +" option. If the field is not found, the FID returned by OGR will be a " +"sequential number starting at 1, but it is not guaranteed to be stable at" +" all." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:247 +#: ../../source/drivers/vector/mongodbv3.rst:211 +msgid "ExecuteSQL() interface" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:249 +msgid "" +"Starting with GDAL 2.2, SQL requests, involving a single layer, with " +"WHERE and ORDER BY statements will be translated as Elasticsearch " +"queries." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:253 +msgid "" +"Otherwise, if specifying \"ES\" as the dialect of ExecuteSQL(), a JSON " +"string with a serialized `Elastic Search filter " +"`__ can be passed. The search will be done on all " +"indices and types, unless the filter itself restricts the search. The " +"returned layer will be a union of the types returned by the " +":oo:`FEATURE_COUNT_TO_ESTABLISH_FEATURE_DEFN` first documents. It will " +"also contain the \\_index and \\_type special fields to indicate the " +"provenance of the features." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:263 +msgid "" +"The following filter can be used to restrict the search to the \"poly\" " +"index and its \"FeatureCollection\" type mapping (Elasticsearch 1.X and " +"2.X)" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:283 +msgid "For Elasticsearch 5.X (works also with 2.X) :" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:303 +msgid "" +"Aggregations are not supported through the ExecuteSQL() interface, but " +"through the below described mechanism." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:309 +msgid "Aggregations" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:313 +msgid "" +"The driver can support issuing aggregation requests to an index. " +"ElasticSearch aggregations can potentially be rather complex, so the " +"driver currently limits to geohash grid based spatial aggegrations, with " +"additional fields with statistical indicators (min, max, average, .), " +"which can be used for example to generate heatmaps. The specification of " +"the aggegation is done through the :oo:`AGGREGATION` open option, whose " +"value is a JSON serialized object whose members are:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:321 +msgid "``index`` (required): the name of the index to query." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:323 +msgid "" +"``geometry_field`` (optional): the path to the geometry field on which to" +" do `geohash grid aggregation " +"`__. For documents with " +"points encoded as GeoJSON, this will be for example " +"`geometry.coordinates`. When this property is not specified, the driver " +"will analyze the mapping and use the geometry field definition found into" +" it (provided there is a single one). Note that aggegration on geo_shape " +"geometries is only supported since Elasticsearch 7 and may require a non-" +"free license." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:331 +msgid "" +"``geohash_grid`` (optional): a JSON object, describing a few " +"characteristics of the geohash_grid, that can have the following members:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:334 +msgid "" +"``size`` (optional): maximum number of geohash buckets to return per " +"query. The default is 10,000. If ``precision`` is specified and the " +"number of results would exceed ``size``, then the server will trim the " +"results, by sorting by decreasing number of documents matched." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:339 +msgid "" +"``precision`` (optional): string length of the geohashes used to define " +"cells/buckets in the results, in the [1,12] range. A geohash of size 1 " +"can generate up to 32 buckets, of size 2 up to 32*32 buckets, etc. When " +"it is not specified, the driver will automatically compute a value, " +"taking into account the ``size`` parameter and the spatial filter, so " +"that the theoretical number of buckets returned does not exceed ``size``." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:346 +msgid "" +"``fields`` (optional): a JSON object, describing which additional " +"statistical fields should be added, that can have the following members:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:349 +msgid "" +"``min`` (optional): array with the paths to index properties on which to " +"compute the minimum during aggegation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:352 +msgid "" +"``max`` (optional): array with the paths to index properties on which to " +"compute the maximum during aggegation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:355 +msgid "" +"``avg`` (optional): array with the paths to index properties on which to " +"compute the average during aggegation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:358 +msgid "" +"``sum`` (optional): array with the paths to index properties on which to " +"compute the sum during aggegation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:361 +msgid "" +"``count`` (optional): array with the paths to index properties on which " +"to compute the value_count during aggegation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:364 +msgid "" +"``stats`` (optional): array with the paths to index properties on which " +"to compute all the above indicators during aggegation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:367 +msgid "" +"When using a GeoJSON mapping, the path to an index property is typically " +"``property.some_name``." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:370 +msgid "" +"When specifying the :oo:`AGGREGATION` open option, a single read-only " +"layer called ``aggregation`` will be returned. A spatial filter can be " +"set on it using the standard OGR SetSpatialFilter() API: it is applied " +"prior to aggregation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:374 +msgid "" +"An example of a potential value for the :oo:`AGGREGATION` open option can" +" be:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:392 +msgid "" +"It will return a layer with a Point geometry field and the following " +"fields:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:394 +msgid "" +"``key`` of type String: the value of the geohash of the corresponding " +"bucket" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:395 +msgid "" +"``doc_count`` of type Integer64: the number of matching documents in the " +"bucket" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:396 +msgid "``field_a_min`` of type Real" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:397 +msgid "``field_b_min`` of type Real" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:398 +msgid "``field_c_min`` of type Real" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:399 +msgid "``field_c_max`` of type Real" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:400 +msgid "``field_c_avg`` of type Real" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:401 +msgid "``field_c_sum`` of type Real" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:402 +msgid "``field_c_count`` of type Integer64" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:405 +msgid "Multi-target layers" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:409 +msgid "" +"The GetLayerByName() method accepts a layer name that can be a comma-" +"separated list of indices, potentially combined with the '*' wildcard " +"character. See " +"https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-" +"index.html. Note that in the current implementation, the field definition" +" will be established from the one of the matching layers, but not all, so" +" using this functionality will be appropriate when the multiple matching " +"layers share the same schema." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:417 +msgid "Getting metadata" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:419 +msgid "Getting feature count is efficient." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:421 +msgid "" +"Getting extent is efficient, only on geometry columns mapped to " +"Elasticsearch type geo_point. On geo_shape fields, feature retrieval of " +"the whole layer is done, which might be slow." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:428 +msgid "Index/type creation and deletion is possible." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:433 +msgid "" +"When inserting a new feature with CreateFeature() in non-bulk mode, and " +"if the command is successful, OGR will fetch the returned \\_id and use " +"it for the SetFeature() operation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:438 +msgid "Spatial reference system" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:440 +msgid "" +"Geometries stored in Elastic Search are supposed to be referenced as " +"longitude/latitude over WGS84 datum (EPSG:4326). On creation, the driver " +"will automatically reproject from the layer (or geometry field) SRS to " +"EPSG:4326, provided that the input SRS is set and that is not already " +"EPSG:4326." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:449 +msgid "" +"|about-layer-creation-options| Starting with GDAL 2.1, the driver " +"supports the following layer creation options:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:624 +msgid "" +"|about-config-options| The following (deprecated) configuration options " +"are available. Starting with GDAL 2.1, layer creation options are also " +"available and should be preferred (see above):" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:666 +msgid "**Open the local store:**" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:672 +msgid "**Open a remote store:**" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:678 +msgid "**Filtering on a Elastic Search field:**" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:684 +msgid "" +"**Using \"match\" query on Windows:** On Windows the query must be " +"between double quotes and double quotes inside the query must be escaped." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:692 +msgid "**Basic aggregation:**" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:698 +msgid "**Load an Elasticsearch index with a shapefile:**" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:704 +msgid "" +"**Create a Mapping File:** The mapping file allows you to modify the " +"mapping according to the `Elasticsearch field-specific types " +"`__. There are many options to choose from, however, most of " +"the functionality is based on all the different things you are able to do" +" with text fields." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:715 +#: ../../source/drivers/vector/elasticsearch.rst:728 +#: ../../source/drivers/vector/elasticsearch.rst:743 +#: ../../source/drivers/vector/elasticsearch.rst:756 +msgid "or (GDAL >= 2.1):" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:721 +msgid "" +"**Read the Mapping File:** Reads the mapping file during the " +"transformation" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:734 +msgid "" +"**Bulk Uploading (for larger datasets):** Bulk loading helps when " +"uploading a lot of data. The integer value is the number of bytes that " +"are collected before being inserted. `Bulk size considerations " +"`__" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:749 +msgid "" +"**Overwrite the current Index:** If specified, this will overwrite the " +"current index. Otherwise, the data will be appended." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:765 +msgid "`Home page for Elasticsearch `__" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:766 +msgid "`Examples Wiki `__" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:767 +msgid "`Google Group `__" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:6 +msgid "ESRIJSON" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:10 +#: ../../source/drivers/vector/topojson.rst:10 +msgid "" +"(Note: prior to GDAL 2.3, the functionality of this driver was available " +"in the GeoJSON driver. They are now distinct drivers)" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:13 +msgid "" +"This driver can read the JSON output of Feature Service requests " +"following the `GeoServices REST Specification " +"`__, like implemented by `ArcGIS " +"Server REST API " +"`__. " +"The driver can scroll through such result sets that are spread over " +"multiple pages (for ArcGIS servers >= 10.3). This is automatically " +"enabled if URL does not contain an explicit *resultOffset* parameter. If " +"it contains this parameter and scrolling is still desired, the " +":oo:`FEATURE_SERVER_PAGING` open option must be set to YES. The page size" +" can be explicitly set with the *resultRecordCount* parameter (but is " +"subject to a server limit). If it is not set, OGR will set it to the " +"maximum value allowed by the server." +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:27 +msgid "" +"Note: for paged requests to work properly, it is generally necessary to " +"add a sort clause on a field, typically the OBJECTID with a " +"\"&orderByFields=OBJECTID+ASC\" parameter in the URL, so that the server " +"returns the results in a reliable way." +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:40 +#: ../../source/drivers/vector/geojson.rst:39 +#: ../../source/drivers/vector/geojsonseq.rst:37 +#: ../../source/drivers/vector/libkml.rst:41 +#: ../../source/drivers/vector/topojson.rst:24 +msgid "Datasource" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:42 +#: ../../source/drivers/vector/geojsonseq.rst:39 +#: ../../source/drivers/vector/topojson.rst:26 +msgid "The driver accepts three types of sources of data:" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:44 +#: ../../source/drivers/vector/topojson.rst:28 +msgid "" +"Uniform Resource Locator (`URL `__) - a" +" Web address to perform `HTTP `__ " +"request." +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:47 +msgid "" +"Plain text file with ESRIJSON data - identified from the file extension " +".json" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:49 +msgid "Text passed directly and encoded in ESRI JSON" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:51 +msgid "" +"Starting with GDAL 2.3, the URL/filename/text might be prefixed with " +"ESRIJSON: to avoid any ambiguity with other drivers. Alternatively, " +"starting with GDAL 3.10, specifying the ``-if ESRIJSON`` option to " +"command line utilities accepting it, or ``ESRIJSON`` as the only value of" +" the ``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the " +"driver to recognize the passed URL/filename/text." +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:75 +msgid "" +"Read the result of a FeatureService request against a GeoServices REST " +"server (note that this server does not support paging):" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:85 +#: ../../source/drivers/vector/geojsonseq.rst:145 +#: ../../source/drivers/vector/jsonfg.rst:237 +#: ../../source/drivers/vector/topojson.rst:45 +msgid ":ref:`GeoJSON driver `" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:86 +msgid "" +"`GeoServices REST Specification `__" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:6 +msgid "FileGDB" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:10 +msgid "" +"The FileGDB driver provides read and write access to vector layers of " +"File Geodatabases (.gdb directories) created by ArcGIS 10 and above. The " +"dataset name must be the directory/folder name, and it must end with the " +".gdb extension." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:15 +msgid "" +"Note : the :ref:`OpenFileGDB driver ` driver exists " +"as an alternative built-in (i.e. not depending on a third-party library) " +"driver." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:26 +#: ../../source/drivers/vector/geopackage_aspatial.rst:67 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:66 +msgid "Requirements" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:28 +msgid "" +"`FileGDB API SDK " +"`__" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:30 +msgid "Curve in geometries are supported on reading with GDAL >= 2.2." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:33 +msgid "Bulk feature loading" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:35 +msgid "" +"The :config:`FGDB_BULK_LOAD` configuration option can be set to YES to " +"speed-up feature insertion (or sometimes solve problems when inserting a " +"lot of features (see http://trac.osgeo.org/gdal/ticket/4420). The effect " +"of this configuration option is to cause a write lock to be taken and a " +"temporary disabling of the indexes. Those are restored when the " +"datasource is closed or when a read operation is done." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:42 +msgid "" +"Bulk load is enabled by default for newly created layers (unless " +"otherwise specified)." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:46 +#: ../../source/drivers/vector/openfilegdb.rst:54 +#: ../../source/drivers/vector/parquet.rst:169 +msgid "SQL support" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:48 +msgid "" +"SQL statements are run through the SQL engine of the FileGDB SDK API. " +"This holds for non-SELECT statements. However, due to partial/inaccurate " +"support for SELECT statements in current FileGDB SDK API versions (v1.2)," +" SELECT statements will be run by default by the OGR SQL engine. This can" +" be changed by specifying the *-dialect FileGDB* option to ogrinfo or " +"ogr2ogr." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:56 +#: ../../source/drivers/vector/openfilegdb.rst:61 +#: ../../source/drivers/vector/pgeo.rst:52 +msgid "Special SQL requests" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:58 +msgid "" +"\"GetLayerDefinition a_layer_name\" and \"GetLayerMetadata a_layer_name\"" +" can be used as special SQL requests to get respectively the definition " +"and metadata of a FileGDB table as XML content." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:62 +msgid "" +"Starting with GDAL 3.5, the \"REPACK\" special SQL request can be issued " +"to ask for database compaction." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:66 +#: ../../source/drivers/vector/openfilegdb.rst:251 +#: ../../source/drivers/vector/pgeo.rst:89 +msgid "Field domains" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:70 +msgid "" +"Retrieving coded and range field domains are supported. Writing support " +"has been added in GDAL 3.5." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:74 +#: ../../source/drivers/vector/gpkg.rst:173 +#: ../../source/drivers/vector/openfilegdb.rst:258 +#: ../../source/drivers/vector/pgeo.rst:96 +#: ../../source/drivers/vector/sqlite.rst:231 +msgid "Relationships" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:78 +#: ../../source/drivers/vector/pgeo.rst:100 +msgid "Relationship retrieval is supported." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:81 +#: ../../source/drivers/vector/openfilegdb.rst:265 +msgid "Hiearchical organization" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:85 +msgid "" +"The hiearchical organization of tables and feature classes as top-level " +"element or within a feature dataset can be explored using the methods " +":cpp:func:`GDALDataset::GetRootGroup`, " +":cpp:func:`GDALGroup::GetGroupNames`, :cpp:func:`GDALGroup::OpenGroup`, " +":cpp:func:`GDALGroup::GetVectorLayerNames` and " +":cpp:func:`GDALGroup::OpenVectorLayer`" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:92 +#: ../../source/drivers/vector/gpkg.rst:168 +#: ../../source/drivers/vector/mssqlspatial.rst:284 +#: ../../source/drivers/vector/openfilegdb.rst:276 +#: ../../source/drivers/vector/sqlite.rst:226 +msgid "Transaction support" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:94 +msgid "" +"The FileGDB driver implements transactions at the database level, through" +" an emulation (as per :ref:`rfc-54`), since the FileGDB SDK itself does " +"not offer it. This works by backing up the current state of a geodatabase" +" when StartTransaction(force=TRUE) is called. If the transaction is " +"committed, the backup copy is destroyed. If the transaction is rolled " +"back, the backup copy is restored. So this might be costly when operating" +" on huge geodatabases." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:102 +msgid "" +"Starting with GDAL 2.1, on Linux/Unix, instead of a full backup copy only" +" layers that are modified are backed up." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:105 +#: ../../source/drivers/vector/openfilegdb.rst:285 +msgid "" +"Note that this emulation has an unspecified behavior in case of " +"concurrent updates (with different connections in the same or another " +"process)." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:110 +msgid "CreateFeature() support" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:112 +msgid "" +"The FileGDB SDK API does not allow to create a feature with a FID " +"specified by the user. Starting with GDAL 2.1, the FileGDB driver " +"implements a special FID remapping technique to enable the user to create" +" features at the FID of their choice." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:119 +#: ../../source/drivers/vector/flatgeobuf.rst:55 +#: ../../source/drivers/vector/geoconcept.rst:82 +#: ../../source/drivers/vector/hana.rst:174 +#: ../../source/drivers/vector/mitab.rst:106 +#: ../../source/drivers/vector/openfilegdb.rst:116 +#: ../../source/drivers/vector/pg.rst:238 +#: ../../source/drivers/vector/pgdump.rst:35 +msgid "Dataset Creation Options" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:121 +#: ../../source/drivers/vector/openfilegdb.rst:118 +msgid "None." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:124 +#: ../../source/drivers/vector/flatgeobuf.rst:60 +#: ../../source/drivers/vector/geoconcept.rst:153 +#: ../../source/drivers/vector/hana.rst:179 +#: ../../source/drivers/vector/mitab.rst:143 +#: ../../source/drivers/vector/mssqlspatial.rst:106 +#: ../../source/drivers/vector/mysql.rst:104 +#: ../../source/drivers/vector/oci.rst:136 +#: ../../source/drivers/vector/openfilegdb.rst:121 +#: ../../source/drivers/vector/pg.rst:243 +#: ../../source/drivers/vector/pgdump.rst:51 +msgid "Layer Creation Options" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:167 +#: ../../source/drivers/vector/openfilegdb.rst:176 +msgid "" +"ArcMap 10.0 and OGR defaults for XYTOLERANCE are 0.001m (or equivalent) " +"for projected coordinate systems, and 0.000000008983153° for geographic " +"coordinate systems. ArcMap 10.0 and OGR defaults for ZTOLERANCE and " +"MTOLERANCE are 0.0001." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:179 +msgid "" +"**XORIGIN, YORIGIN, ZORIGIN, MORIGIN, XYSCALE, ZSCALE, MSCALE**: These " +"parameters control the `coordinate precision grid " +"`__" +" inside the file geodatabase. The dimensions of the grid are determined " +"by the origin, and the scale. The origin defines the location of a " +"reference grid point in space. The scale is the reciprocal of the " +"resolution. So, to get a grid with an origin at 0 and a resolution of " +"0.001 on all axes, you would set all the origins to 0 and all the scales " +"to 1000." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:189 +#: ../../source/drivers/vector/openfilegdb.rst:191 +msgid "" +"*Important*: The domain specified by ``(xmin=XORIGIN, ymin=YORIGIN, " +"xmax=(XORIGIN + 9E+15 / XYSCALE), ymax=(YORIGIN + 9E+15 / XYSCALE))`` " +"needs to encompass every possible coordinate value for the feature class." +" If features are added with coordinates that fall outside the domain, " +"errors will occur in ArcGIS with spatial indexing, feature selection, and" +" exporting data." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:196 +#: ../../source/drivers/vector/openfilegdb.rst:198 +msgid "ArcMap 10.0 and OGR defaults:" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:198 +#: ../../source/drivers/vector/openfilegdb.rst:200 +msgid "" +"For geographic coordinate systems: XORIGIN=-400, YORIGIN=-400, " +"XYSCALE=1000000000" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:200 +#: ../../source/drivers/vector/openfilegdb.rst:202 +msgid "" +"For projected coordinate systems: XYSCALE=10000 for the default " +"XYTOLERANCE of 0.001m. XORIGIN and YORIGIN change based on the coordinate" +" system, but the OGR default of -2147483647 is suitable with the default " +"XYSCALE for all coordinate systems." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:204 +#: ../../source/drivers/vector/openfilegdb.rst:206 +msgid "ZORIGIN and MORIGIN: -100000" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:205 +#: ../../source/drivers/vector/openfilegdb.rst:207 +msgid "ZSCALE and MSCALE: 10000" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:207 +msgid "MORIGIN and MSCALE added in GDAL 3.5.1" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:261 +#: ../../source/drivers/vector/geojson.rst:491 +#: ../../source/drivers/vector/geojsonseq.rst:124 +#: ../../source/drivers/vector/gml.rst:1319 +#: ../../source/drivers/vector/gpkg.rst:701 +#: ../../source/drivers/vector/jsonfg.rst:196 +#: ../../source/drivers/vector/openfilegdb.rst:290 +msgid "Geometry coordinate precision" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:263 +#: ../../source/drivers/vector/geojson.rst:493 +#: ../../source/drivers/vector/geojsonseq.rst:126 +#: ../../source/drivers/vector/gml.rst:1321 +#: ../../source/drivers/vector/gpkg.rst:703 +#: ../../source/drivers/vector/jsonfg.rst:198 +#: ../../source/drivers/vector/openfilegdb.rst:292 +msgid "3.9" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:265 +#: ../../source/drivers/vector/openfilegdb.rst:294 +msgid "" +"The driver supports reading and writing the geometry coordinate " +"precision, using the XYResolution, ZResolution and MResolution members of" +" the :cpp:class:`OGRGeomCoordinatePrecision` settings of the " +":cpp:class:`OGRGeomFieldDefn`. ``XYScale`` is computed as 1.0 / " +"``XYResolution`` (and similarly for the Z and M components). The " +"tolerance setting is computed as being one tenth of the resolution" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:272 +#: ../../source/drivers/vector/openfilegdb.rst:301 +msgid "" +"On reading, the coordinate precision grid parameters are returned as " +"format specific options of :cpp:class:`OGRGeomCoordinatePrecision` with " +"the ``FileGeodatabase`` format key, with the following option key names: " +"``XYScale``, ``XYTolerance``, ``XYOrigin``, ``ZScale``, ``ZTolerance``, " +"``ZOrigin``, ``MScale``, ``MTolerance``, ``MOrigin``. On writing, they " +"are also honored (they will have precedence over XYResolution, " +"ZResolution and MResolution)." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:280 +#: ../../source/drivers/vector/openfilegdb.rst:309 +msgid "" +"On layer creation, the XORIGIN, YORIGIN, ZORIGIN, MORIGIN, XYSCALE, " +"ZSCALE, ZORIGIN, XYTOLERANCE, ZTOLERANCE, MTOLERANCE layer creation " +"options will be used in priority over the settings of " +":cpp:class:`OGRGeomCoordinatePrecision`." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:287 +msgid "" +"The SDK is known to be unable to open layers with particular spatial " +"reference systems. This might be the case if messages \"FGDB: Error " +"opening XXXXXXX. Skipping it (Invalid function arguments.)\" when running" +" ``ogrinfo --debug on the.gdb`` (reported as warning in GDAL 2.0). Using " +"the OpenFileGDB driver will generally solve that issue." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:293 +msgid "" +"FGDB coordinate snapping will cause geometries to be altered during " +"writing. Use the origin and scale layer creation options to control the " +"snapping behavior." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:297 +msgid "" +"Reading data compressed in SDC format (Smart Data Compression) is not " +"support by the driver, because it is not supported by the ESRI SDK." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:300 +msgid "" +"Reading data compressed in CDF format (Compressed Data Format) requires " +"ESRI SDK 1.4 or later." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:303 +msgid "" +"Some applications create FileGeodatabases with non-spatial tables which " +"are not present in the GDB_Items metadata table. These tables cannot be " +"opened by the ESRI SDK, so GDAL will automatically fallback to the " +"OpenFileGDB driver to read these tables. Accordingly they will be opened " +"with the limitations of the OpenFileGDB driver (for instance, they will " +"be read only)." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:310 +msgid "The driver does not support 64-bit integers." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:315 +msgid "" +"`ESRI File Geodatabase API Page `__" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:317 +msgid "" +":ref:`OpenFileGDB driver `, not depending on a third-" +"party library/SDK" +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:12 +msgid "" +"This driver implements read/write support for access to features encoded " +"in `FlatGeobuf `__ format, a" +" performant binary encoding for geographic data based on flatbuffers that" +" can hold a collection of Simple Features." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:27 +msgid "Multi layer support" +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:29 +msgid "" +"A single .fgb file only contains one single layer. For multiple layer " +"support, it is possible to put several .fgb files in a directory, and use" +" that directory name as the connection string." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:33 +msgid "" +"On creation, passing a filename without a .fgb suffix will instruct the " +"driver to create a directory of that name, and create layers as .fgb " +"files in that directory." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:37 +msgid "" +"Starting with GDAL 3.9, metadata set at the layer level will be written " +"in the FlatGeobuf header, and retrieved on reading as layer metadata." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:57 +#: ../../source/drivers/vector/geopackage_aspatial.rst:144 +#: ../../source/drivers/vector/geopackage_aspatial.rst:149 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:88 +#: ../../source/drivers/vector/hana.rst:176 +#: ../../source/drivers/vector/miramon.rst:291 +#: ../../source/drivers/vector/pg.rst:240 +#: ../../source/drivers/vector/shapefile.rst:343 +msgid "None" +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:96 +msgid "" +"Currently, NULL geometries are not supported with " +":lco:`SPATIAL_INDEX=YES`." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:98 +msgid "" +"`More background and dicussion on this issue at " +"`__" +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:100 +msgid "" +"The creation of the packet Hilbert R-Tree requires an amount of RAM which" +" is at least the number of features times 83 bytes." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:106 +msgid "" +"Simple translation of a single shapefile into a FlatGeobuf file. The file" +" 'filename.fgb' will be created with the features from abc.shp and " +"attributes from abc.dbf. The file ``filename.fgb`` must **not** already " +"exist, as it will be created." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:115 +msgid "Conversion of a Geopackage file with multiple layers:" +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:124 +msgid "`FlatGeobuf at GitHub `__" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:6 +msgid "Geoconcept" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:10 +#: ../../source/drivers/vector/geoconcept.rst:41 +msgid "GeoConcept text export files should be available for writing and reading." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:13 +#: ../../source/drivers/vector/geoconcept.rst:44 +msgid "" +"The OGR GeoConcept driver treats a single GeoConcept file within a " +"directory as a dataset comprising layers. GeoConcept files extensions are" +" ``.txt`` or ``.gxt``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:17 +#: ../../source/drivers/vector/geoconcept.rst:48 +msgid "" +"Currently the GeoConcept driver only supports multi-polygons, lines and " +"points." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:30 +msgid "GeoConcept Text File Format (gxt)" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:32 +msgid "GeoConcept is a GIS developed by the Company GeoConcept SA." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:34 +msgid "" +"It's an object oriented GIS, where the features are named « objects », " +"and feature types are named « type/subtype » (class allowing " +"inheritance)." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:38 +msgid "" +"Among its import/export formats, it proposes a simple text format named " +"gxt. A gxt file may contain objects from several type/subtype." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:54 +msgid "" +"The GeoConcept driver treats a GeoConcept file (``.txt`` or ``.gxt``) as " +"a dataset." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:57 +msgid "" +"GeoConcept files can store multiple kinds of geometry (one by layer), " +"even if a GeoConcept layer can only have one kind of geometry." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:60 +msgid "" +"Note this makes it very difficult to translate a mixed geometry layer " +"from another format into GeoConcept format using ogr2ogr, since ogr2ogr " +"has no support for separating out geometries from a source layer." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:64 +msgid "" +"GeoConcept sub-type is treated as OGR feature. The name of a layer is " +"therefore the concatenation of the GeoConcept type name, ``'.'`` and " +"GeoConcept sub-type name." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:68 +msgid "GeoConcept type definition (``.gct`` files) are used for creation only." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:70 +msgid "" +"GeoConcept feature fields definition are stored in an associated ``.gct``" +" file, and so fields suffer a number of limitations (FIXME) :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:73 +msgid "Attribute names are not limited in length." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:74 +msgid "" +"Only Integer, Real and String field types are supported. The various " +"list, and other field types cannot be created for the moment (they exist " +"in the GeoConcept model, but are not yet supported by the GeoConcept " +"driver)." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:79 +msgid "The OGR GeoConcept driver does not support deleting features." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:101 +msgid "" +"It is important to note that a GeoConcept export file can hold different " +"types and associated sub-types." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:104 +msgid "" +"configuration section : the GCT file starts with ``//#SECTION CONFIG`` " +"and ends with ``//#ENDSECTION CONFIG``. All the configuration is enclosed" +" within these marks." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:107 +msgid "" +"map section : purely for documentation at the time of writing this " +"document. This section starts with ``//#SECTION MAP`` and ends with " +"``//#ENDSECTION MAP``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:110 +msgid "" +"type section : this section defines a class of features. A type has a " +"name (keyword ``Name``) and an ID (keyword ``ID``). A type holds sub-" +"types and fields. This section starts with ``//#SECTION TYPE`` and ends " +"with ``//#ENDSECTION TYPE``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:115 +msgid "" +"sub-type section : this sub-section defines a kind og features within a " +"class. A sub-type has a name (keyword ``Name``), an ID (keyword ``ID``), " +"a type of geometry (keyword ``Kind``) and a dimension. The following " +"types of geometry are supported : POINT, LINE, POLYGON. The current " +"release of this driver does not support the TEXT geometry. The dimension " +"can be 2D, 3DM or 3D. A sub-type holds fields. This section starts with " +"``//#SECTION SUBTYPE`` and ends with ``//#ENDSECTION SUBTYPE``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:124 +msgid "" +"fields section : defines user fields. A field has a name (keyword " +"``Name``), an ID (keyword ``ID``), a type (keyword ``Kind``). The " +"following types of fields are supported : INT, REAL, MEMO, CHOICE, DATE, " +"TIME, LENGTH, AREA. This section starts with ``//#SECTION FIELD`` and " +"ends with ``//#ENDSECTION FIELD``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:131 +msgid "field section : defines type fields. See above." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:133 +msgid "" +"field section : defines general fields. Out of these, the following rules" +" apply :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:136 +msgid "" +"private field names start with a '@' : the private fields are " +"``Identifier``, ``Class``, ``Subclass``, ``Name``, ``NbFields``, ``X``, " +"``Y``, ``XP``, ``YP``, ``Graphics``, ``Angle``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:139 +msgid "" +"some private field are mandatory (they must appear in the configuration) " +": ``Identifier``, ``Class``, ``Subclass``, ``Name``, ``X``, ``Y``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:142 +msgid "" +"If the sub-type is linear (LINE), then the following fields must be " +"declared ``XP``, ``YP``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:144 +msgid "" +"If the sub-type is linear or polygonal (LINE, POLY), then ``Graphics`` " +"must be declared." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:146 +msgid "" +"If the sub-type is ponctual or textual (POINT, TEXT), the ``Angle`` may " +"be declared." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:149 +msgid "" +"When this option is not used, the driver manage types and sub-types name " +"based on either the layer name or on the use of ``-nln`` option." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:166 +msgid "" +"At the present moment, coordinates are written with 2 decimals for " +"Cartesian spatial reference systems (including height) or with 9 decimals" +" for geographical spatial reference systems." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:174 +msgid "Example of a .gct file :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:247 +msgid "Example of a GeoConcept text export :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:265 +msgid "Example of use :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:267 +msgid "Creating a GeoConcept export file :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:273 +msgid "Appending new features to an existing GeoConcept export file :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:279 +msgid "Translating a GeoConcept export file layer into MapInfo file :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:288 +msgid "`GeoConcept web site `__" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:10 +msgid "" +"This driver implements read/write support for access to features encoded " +"in `GeoJSON `__ format. GeoJSON is a dialect based " +"on the `JavaScript Object Notation (JSON) `__. JSON is " +"a lightweight plain text format for data interchange and GeoJSON is " +"nothing other than its specialization for geographic content." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:16 +msgid "" +"GeoJSON is supported as an output format of a number of services: " +"`GeoServer " +"`__," +" `CartoWeb `__, etc." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:20 +msgid "" +"The OGR GeoJSON driver translates GeoJSON encoded data to objects of the " +"`OGR Simple Features model `__: Datasource, Layer, " +"Feature, Geometry. The implementation is based on `GeoJSON Specification," +" v1.0 `__." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:25 +msgid "" +"Starting with GDAL 2.1.0, the GeoJSON driver supports updating existing " +"GeoJSON files. In that case, the default value for the NATIVE_DATA open " +"option will be YES." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:41 +msgid "The OGR GeoJSON driver accepts three types of sources of data:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:43 +#: ../../source/drivers/vector/geojsonseq.rst:41 +#: ../../source/drivers/vector/jsonfg.rst:46 +msgid "" +"Uniform Resource Locator (`URL `__) - a" +" Web address to perform `HTTP `__ " +"request" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:46 +msgid "" +"Plain text file with GeoJSON data - identified from the file extension " +".geojson or .json" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:48 +msgid "Text passed directly and encoded in GeoJSON" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:50 +msgid "" +"Starting with GDAL 2.3, the URL/filename/text might be prefixed with " +"GeoJSON: to avoid any ambiguity with other drivers. Alternatively, " +"starting with GDAL 3.10, specifying the ``-if GeoJSON`` option to command" +" line utilities accepting it, or ``GeoJSON`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed URL/filename/text." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:58 +#: ../../source/drivers/vector/libkml.rst:256 +msgid "Layer" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:60 +msgid "" +"A GeoJSON datasource is translated to single OGRLayer object with pre-" +"defined name *OGRGeoJSON*:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:67 +msgid "" +"It is also valid to assume that OGRDataSource::GetLayerCount() for " +"GeoJSON datasource always returns 1." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:70 +msgid "Starting with GDAL 2.2, the layer name is built with the following logic:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:73 +msgid "If a \"name\" member is found at the FeatureCollection level, it is used." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:75 +msgid "" +"Otherwise if the filename is regular (ie not a URL with query " +"parameters), then the filename without extension and path is used as the " +"layer name." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:78 +msgid "Otherwise OGRGeoJSON is used." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:80 +msgid "" +"Accessing Web Service as a datasource (i.e. FeatureServer), each request " +"will produce new layer. This behavior conforms to stateless nature of " +"HTTP transaction and is similar to how Web browsers operate: single " +"request == single page." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:85 +msgid "" +"If a top-level member of GeoJSON data is of any other type than " +"*FeatureCollection*, the driver will produce a layer with only one " +"feature. Otherwise, a layer will consists of a set of features." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:89 +msgid "" +"If the :oo:`NATIVE_DATA` open option is set to YES, members at the level " +"of the FeatureCollection will be stored as a serialized JSON object in " +"the NATIVE_DATA item of the NATIVE_DATA metadata domain of the layer " +"object (and \"application/vnd.geo+json\" in the NATIVE_MEDIA_TYPE of the " +"NATIVE_DATA metadata domain)." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:96 +#: ../../source/drivers/vector/libkml.rst:468 +#: ../../source/drivers/vector/ngw.rst:108 +msgid "Feature" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:98 +msgid "" +"The OGR GeoJSON driver maps each object of following types to new " +"*OGRFeature* object: Point, LineString, Polygon, GeometryCollection, " +"Feature." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:102 +msgid "" +"According to the *GeoJSON Specification*, only the *Feature* object must " +"have a member with name *properties*. Each and every member of " +"*properties* is translated to OGR object of type of OGRField and added to" +" corresponding OGRFeature object." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:107 +msgid "" +"The *GeoJSON Specification* does not require all *Feature* objects in a " +"collection to have the same schema of properties. If *Feature* objects in" +" a set defined by *FeatureCollection* object have different schema of " +"properties, then resulting schema of fields in OGRFeatureDefn is " +"generated as `union `__ " +"of all *Feature* properties." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:114 +msgid "" +"Schema detection will recognized fields of type String, Integer, Real, " +"StringList, IntegerList and RealList, Integer(Boolean), Date, Time and " +"DateTime." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:117 +msgid "" +"It is possible to tell the driver to not to process attributes by setting" +" configuration option :config:`ATTRIBUTES_SKIP=YES`. Default behavior is " +"to preserve all attributes (as an union, see previous paragraph), what is" +" equal to setting :config:`ATTRIBUTES_SKIP=NO`." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:123 +msgid "" +"If the :oo:`NATIVE_DATA` open option is set to YES, the Feature JSON " +"object will be stored as a serialized JSON object in the NativeData " +"property of the OGRFeature object (and \"application/vnd.geo+json\" in " +"the NativeMediaType property). On write, if a OGRFeature to be written " +"has its NativeMediaType property set to \"application/vnd.geo+json\" and " +"its NativeData property set to a string that is a serialized JSON object," +" then extra members of this object (i.e. not the \"property\" dictionary," +" nor the first 3 dimensions of geometry coordinates) will be used to " +"enhance the created JSON object from the OGRFeature. See :ref:`rfc-60` " +"for more details." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:137 +msgid "" +"Similarly to the issue with mixed-properties features, the *GeoJSON " +"Specification* draft does not require all *Feature* objects in a " +"collection must have geometry of the same type. Fortunately, OGR objects " +"model does allow to have geometries of different types in single layer - " +"a heterogeneous layer. By default, the GeoJSON driver preserves type of " +"geometries." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:144 +msgid "" +"However, sometimes there is a need to generate a homogeneous layer from a" +" set of heterogeneous features. For this purpose, it is possible to tell " +"the driver to wrap all geometries with OGRGeometryCollection type as a " +"common denominator. This behavior may be controlled by setting the " +":config:`GEOMETRY_AS_COLLECTION` configuration option to YES." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:242 +msgid "" +"To explain :oo:`FLATTEN_NESTED_ATTRIBUTES`, consider the following " +"GeoJSON fragment:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:268 +msgid "\"ogrinfo test.json -al -oo FLATTEN_NESTED_ATTRIBUTES=yes\" reports:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:281 +msgid "" +"|about-layer-creation-options| This driver supports the following layer " +"creation options:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:417 +#: ../../source/drivers/vector/jsonfg.rst:188 +msgid "" +"The driver supports reading and writing to files managed by VSI Virtual " +"File System API, which includes \"regular\" files, as well as files in " +"the /vsizip/ (read-write), /vsigzip/ (read-write), /vsicurl/ (read-only) " +"domains." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:425 +msgid "Round-tripping of extra JSON members" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:427 +msgid "See :ref:`rfc-60` for more details." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:429 +msgid "" +"Starting with GDAL 2.1, extra JSON members at the FeatureCollection, " +"Feature or geometry levels that are not normally reflected in the OGR " +"abstraction, such as the ones called \"extra_XXXXX_member\" in the below " +"snippet, are by default preserved when executing ogr2ogr with GeoJSON " +"both at the source and destination. This also applies to extra values in " +"position tuples of geometries, beyond the 3rd dimension (100, 101 in the " +"below example), if the transformation preserves the geometry structure " +"(for example, reprojection is allowed, but not change in the number of " +"coordinates)." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:461 +msgid "" +"This behavior can be turned off by specifying the **-noNativeData** " +"switch of the ogr2ogr utility." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:465 +msgid "RFC 7946 write support" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:467 +msgid "" +"By default, the driver will write GeoJSON files following GeoJSON 2008 " +"specification. When specifying the :lco:`RFC7946=YES` creation option, " +"the RFC 7946 standard will be used instead." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:471 +msgid "" +"The differences between the 2 versions are mentioned in `Appendix B of " +"RFC 7946 `__ and recalled" +" here for what matters to the driver:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:475 +msgid "" +"Coordinates must be geographic over the WGS 84 ellipsoid, hence if the " +"spatial reference system specified at layer creation time is not " +"EPSG:4326, on-the-fly reprojection will be done by the driver." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:479 +msgid "" +"Polygons will be written such as to follow the right-hand rule for " +"orientation (counterclockwise external rings, clockwise internal rings)." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:482 +msgid "" +"The values of a \"bbox\" array are \"[west, south, east, north]\", not " +"\"[minx, miny, maxx, maxy]\"" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:484 +msgid "" +"Some extension member names (see previous section about round/tripping) " +"are forbidden in the FeatureCollection, Feature and Geometry objects." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:487 +msgid "" +"The default coordinate precision is 7 decimal digits after decimal " +"separator." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:495 +#: ../../source/drivers/vector/jsonfg.rst:200 +msgid "" +"The GeoJSON driver supports reading and writing the geometry coordinate " +"precision, using the :cpp:class:`OGRGeomCoordinatePrecision` settings of " +"the :cpp:class:`OGRGeomFieldDefn` Those settings are used to round the " +"coordinates of the geometry of the features to an appropriate decimal " +"precision." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:502 +#: ../../source/drivers/vector/geojsonseq.rst:135 +msgid "" +"The :lco:`COORDINATE_PRECISION` layer creation option has precedence over" +" the values set on the :cpp:class:`OGRGeomFieldDefn`." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:505 +msgid "" +"Implementation details: the coordinate precision is stored as " +"``xy_coordinate_resolution`` and ``z_coordinate_resolution`` members at " +"the FeatureCollection level. Their numeric value is expressed in the " +"units of the SRS." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:524 +msgid "How to dump content of .geojson file:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:530 +msgid "How to query features from remote service with filtering by attribute:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:536 +msgid "" +"How to translate number of features queried from FeatureServer to ESRI " +"Shapefile:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:543 +msgid "How to translate a ESRI Shapefile into a RFC 7946 GeoJSON file:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:552 +msgid "`GeoJSON `__ - encoding geographic content in JSON" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:554 +msgid "`RFC 7946 `__ standard." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:555 +msgid "" +"`GeoJSON 2008 `__ specification " +"(obsoleted by RFC 7946)." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:557 +msgid "`JSON `__ - JavaScript Object Notation" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:558 +msgid ":ref:`GeoJSON sequence driver `" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:559 +msgid ":ref:`OGC Features and Geometries JSON (JSON-FG) driver `" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:560 +msgid ":ref:`ESRI JSON / FeatureService driver `" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:561 +msgid ":ref:`TopoJSON driver `" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:8 +msgid "GeoJSONSeq" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:12 +msgid "" +"This driver implements read/creation support for features encoded " +"individually as `GeoJSON `__ Feature objects, " +"separated by newline (LF) (`Newline Delimited JSON " +"`__) or record-separator (RS) " +"characters (`RFC 8142 `__ standard: " +"GeoJSON Text Sequences)" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:19 +msgid "" +"Such files are equivalent to a GeoJSON FeatureCollection, but are more " +"friendly for incremental parsing." +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:22 +msgid "" +"The driver automatically reprojects geometries to WGS84 longitude, " +"latitude, if the layer is created with another SRS." +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:25 +msgid "Appending to an existing file is supported since GDAL 3.6" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:44 +msgid "" +"Plain text file with GeoJSON data - identified from the file extension " +".geojsonl or .geojsons" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:46 +msgid "Text passed directly as filename, and encoded as GeoJSON sequences" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:48 +msgid "" +"The URL/filename/text might be prefixed with GeoJSONSeq: to avoid any " +"ambiguity with other drivers. Alternatively, starting with GDAL 3.10, " +"specifying the ``-if GeoJSONSeq`` option to command line utilities " +"accepting it, or ``GeoJSONSeq`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed URL/filename/text." +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:61 +msgid ":copy-config:`OGR_GEOJSON_MAX_OBJ_SIZE`" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:128 +msgid "" +"On creation, the GeoJSONSeq driver supports using the geometry coordinate" +" precision, from th :cpp:class:`OGRGeomCoordinatePrecision` settings of " +"the :cpp:class:`OGRGeomFieldDefn`. Those settings are used to round the " +"coordinates of the geometry of the features to an appropriate decimal " +"precision." +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:138 +msgid "" +"The value of those geometry coordinate precision is *not* serialized in " +"the generated file, hence on reading, the driver will not advertise a " +"geometry coordinate precision." +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:146 +msgid "" +"`RFC 7946 `__ standard: the GeoJSON " +"Format." +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:148 +msgid "" +"`RFC 8142 `__ standard: GeoJSON Text" +" Sequences (RS separator)" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:150 +msgid "" +"`GeoJSONL `__: An " +"optimized format for large geographic datasets" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:152 +msgid "" +"`JSON streaming on Wikipedia " +"`__: An overview over " +"formats for concatenated JSON in a single file" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:4 +msgid "GeoPackage aspatial extension" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:6 +msgid "" +"This extension has been superseded by GeoPackage 1.2 ``attributes`` data " +"type." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:8 +msgid "GeoPackage 1.0 Extension" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:10 +msgid "" +"Extension follows template from Annex I of the OGC `GeoPackage 1.0 " +"Specification`_." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:13 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:11 +msgid "Extension Title" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:15 +msgid "Aspatial Support" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:20 +msgid "" +"Support for aspatial data (i.e. SQLite tables/views without a geometry " +"column), potentially with associated metadata." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:23 +msgid "" +"This was used in GDAL 2.0 and GDAL 2.1, before the introduction of the " +"'attributes' data_type of GeoPackage v1.2. Starting with GDAL 2.2, " +"'attributes' will be used by default, so this extension is now legacy." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:28 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:22 +msgid "Extension Author" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:30 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:24 +msgid "`GDAL - Geospatial Data Abstraction Library`_, author_name `gdal`." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:33 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:27 +msgid "Extension Name or Template" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:51 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:48 +msgid "Extension Type" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:53 +msgid "Extension of Existing Requirement in Clause 2." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:56 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:53 +msgid "Applicability" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:58 +msgid "" +"This extension applies to any aspatial user data table or view specified " +"in the ``gpkg_contents`` table with a lowercase `data_type` column value " +"of \"aspatial\"." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:62 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:61 +msgid "Scope" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:64 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:63 +msgid "Read-write" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:70 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:69 +msgid "GeoPackage" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:72 +msgid "Contents Table - Aspatial" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:74 +msgid "" +"The `gpkg_contents` table SHALL contain a row with a lowercase " +"`data_type` column value of \"aspatial\" for each aspatial user data " +"table or view." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:77 +msgid "User Data Tables" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:79 +msgid "" +"The second component of the SQL schema for aspatial tables in an Extended" +" GeoPackage described in clause 'Contents Table - Aspatial' above are " +"user tables or views that contain aspatial user data." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:83 +msgid "" +"An Extended GeoPackage with aspatial support is not required to contain " +"any user data tables. User data tables MAY be empty." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:86 +msgid "" +"An Extended GeoPackage with aspatial support MAY contain tables or views." +" Every such aspatial table or view MAY have a column with column type " +"INTEGER and PRIMARY KEY AUTOINCREMENT column constraints per EXAMPLE." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:94 +msgid "Column Name" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:97 +msgid "Null" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:98 +msgid "Default" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:99 +msgid "Key" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:100 +msgid "`id`" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:101 +msgid "INTEGER" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:102 +msgid "Autoincrement primary key" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:103 +msgid "no" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:105 +msgid "PK" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:106 +msgid "`text_attribute`" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:107 +msgid "TEXT" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:108 +msgid "Text attribute of row" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:109 +#: ../../source/drivers/vector/geopackage_aspatial.rst:115 +#: ../../source/drivers/vector/geopackage_aspatial.rst:121 +#: ../../source/drivers/vector/geopackage_aspatial.rst:127 +msgid "yes" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:112 +msgid "`real_attribute`" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:113 +msgid "REAL" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:114 +msgid "Real attribute of row" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:118 +msgid "`boolean_attribute`" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:119 +msgid "BOOLEAN" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:120 +msgid "Boolean attribute of row" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:124 +msgid "`raster_or_photo`" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:125 +msgid "BLOB" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:126 +msgid "Photograph" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:131 +msgid "" +"An integer primary key of an aspatial table or view allows features to be" +" linked to row level metadata records in the `gpkg_metadata` table by " +"`SQLite ROWID`_ values in the `gpkg_metadata_reference` table as " +"described in clause 2.4.3 Metadata Reference Table." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:136 +msgid "An aspatial table or view SHALL NOT have a geometry column." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:138 +msgid "" +"Columns in aspatial tables or views SHALL be defined using only the data " +"types specified in Table 1 in Clause 1.1.1.1.3." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:142 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:86 +msgid "GeoPackage SQLite Configuration" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:147 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:91 +msgid "GeoPackage SQLite Extension" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:6 +msgid "GeoRSS" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:10 +msgid "GeoRSS is a way of encoding location in RSS or Atom feeds." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:12 +msgid "" +"OGR has support for GeoRSS reading and writing. Read support is only " +"available if GDAL is built with *expat* library support" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:15 +msgid "The driver supports RSS documents in RSS 2.0 or Atom 1.0 format." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:17 +msgid "" +"It also supports the `3 ways of encoding location " +"`__ : GeoRSS simple, GeoRSS GML and W3C Geo (the" +" later being deprecated)." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:21 +msgid "" +"The driver can read and write documents without location information as " +"well." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:24 +msgid "" +"The default datum for GeoRSS document is the WGS84 datum (EPSG:4326). " +"Although that GeoRSS locations are encoded in latitude-longitude order in" +" the XML file, all coordinates reported or expected by the driver are in " +"longitude-latitude order. The longitude/latitude order used by OGR is " +"meant for compatibility with most of the rest of OGR drivers and " +"utilities. For locations encoded in GML, the driver will support the " +"srsName attribute for describing other SRS." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:32 +msgid "" +"Simple and GML encoding support the notion of a *box* as a geometry. This" +" will be decoded as a rectangle (Polygon geometry) in OGR Simple Feature " +"model." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:36 +msgid "" +"A single layer is returned while reading a RSS document. Features are " +"retrieved from the content of (RSS document) or (Atom " +"document) elements." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:50 +#: ../../source/drivers/vector/gml.rst:399 +#: ../../source/drivers/vector/gpx.rst:124 +#: ../../source/drivers/vector/jml.rst:35 +#: ../../source/drivers/vector/kml.rst:70 +msgid "Encoding issues" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:52 +#: ../../source/drivers/vector/gml.rst:401 +#: ../../source/drivers/vector/gpx.rst:126 +#: ../../source/drivers/vector/jml.rst:37 +#: ../../source/drivers/vector/kml.rst:72 +msgid "Expat library supports reading the following built-in encodings :" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:54 +#: ../../source/drivers/vector/gml.rst:403 +#: ../../source/drivers/vector/gpx.rst:128 +#: ../../source/drivers/vector/jml.rst:39 +#: ../../source/drivers/vector/kml.rst:74 +msgid "US-ASCII" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:55 +#: ../../source/drivers/vector/gml.rst:404 +#: ../../source/drivers/vector/gpx.rst:129 +#: ../../source/drivers/vector/jml.rst:40 +#: ../../source/drivers/vector/kml.rst:75 +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "UTF-8" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:56 +#: ../../source/drivers/vector/gml.rst:405 +#: ../../source/drivers/vector/gpx.rst:130 +#: ../../source/drivers/vector/jml.rst:41 +#: ../../source/drivers/vector/kml.rst:76 +msgid "UTF-16" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:57 +#: ../../source/drivers/vector/gml.rst:406 +#: ../../source/drivers/vector/gpx.rst:131 +#: ../../source/drivers/vector/jml.rst:42 +#: ../../source/drivers/vector/kml.rst:77 +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-1" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:58 +#: ../../source/drivers/vector/gml.rst:407 +#: ../../source/drivers/vector/gpx.rst:132 +#: ../../source/drivers/vector/jml.rst:43 +#: ../../source/drivers/vector/kml.rst:78 +msgid "Windows-1252" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:60 +#: ../../source/drivers/vector/gml.rst:409 +#: ../../source/drivers/vector/gpx.rst:134 +#: ../../source/drivers/vector/kml.rst:80 +msgid "" +"The content returned by OGR will be encoded in UTF-8, after the " +"conversion from the encoding mentioned in the file header is." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:66 +msgid "" +"If your GeoRSS file is not encoded in one of the previous encodings, it " +"will not be parsed by the GeoRSS driver. You may convert it into one of " +"the supported encoding with the *iconv* utility for example and change " +"accordingly the *encoding* parameter value in the XML header." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:68 +msgid "" +"When writing a GeoRSS file, the driver expects UTF-8 content to be passed" +" in." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:74 +msgid "" +"While reading a GeoRSS document, the driver will first make a full scan " +"of the document to get the field definitions." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:77 +msgid "" +"The driver will return elements found in the base schema of RSS channel " +"or Atom feeds. It will also return extension elements, that are allowed " +"in namespaces." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:81 +msgid "Attributes of first level elements will be exposed as fields." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:83 +msgid "" +"Complex content (elements inside first level elements) will be returned " +"as an XML blob." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:86 +msgid "" +"When a same element is repeated, a number will be appended at the end of " +"the attribute name for the repetitions. This is useful for the " +" element in RSS and Atom documents for example." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:90 +msgid "The following content :" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:109 +#: ../../source/drivers/vector/gpx.rst:171 +msgid "will be interpreted in the OGR SF model as :" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:128 +msgid "" +"On export, all layers are written to a single file. Update of existing " +"files is not supported." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:131 +#: ../../source/drivers/vector/gpx.rst:197 +msgid "" +"If the output file already exits, the writing will not occur. You have to" +" delete the existing file first." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:134 +msgid "" +"A layer that is created cannot be immediately read without closing and " +"reopening the file. That is to say that a dataset is read-only or write-" +"only in the same session." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:138 +#: ../../source/drivers/vector/gpx.rst:200 +msgid "Supported geometries :" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:140 +msgid "Features of type wkbPoint/wkbPoint25D." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:141 +msgid "Features of type wkbLineString/wkbLineString25D." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:142 +msgid "Features of type wkbPolygon/wkbPolygon25D." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:144 +msgid "Other type of geometries are not supported and will be silently ignored." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:231 +msgid "" +"When translating from a source dataset, it may be necessary to rename the" +" field names from the source dataset to the expected RSS or ATOM " +"attribute names, such as , <description>, etc... This can be done " +"with a :ref:`OGR VRT <vector.vrt>` dataset, or by using the \"-sql\" " +"option of the ogr2ogr utility (see :ref:`rfc-21`)" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:240 +#: ../../source/drivers/vector/gml.rst:794 +#: ../../source/drivers/vector/gpx.rst:387 +#: ../../source/drivers/vector/kml.rst:130 +#: ../../source/drivers/vector/libkml.rst:951 +msgid "" +"The driver supports reading and writing to files managed by VSI Virtual " +"File System API, which include \"regular\" files, as well as files in the" +" /vsizip/ (read-write) , /vsigzip/ (read-write) , /vsicurl/ (read-only) " +"domains." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:250 +msgid "The ogrinfo utility can be used to dump the content of a GeoRSS datafile :" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:259 +msgid "" +"The ogr2ogr utility can be used to do GeoRSS to GeoRSS translation. For " +"example, to translate a Atom document into a RSS document" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:268 +msgid "" +"Note : in this example we map equivalent fields, from the source name to " +"the expected name of the destination format." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:272 +msgid "" +"The following Python script shows how to read the content of a online " +"GeoRSS feed" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:311 +msgid "`Home page for GeoRSS format <http://georss.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:312 +msgid "`Wikipedia page for GeoRSS format <http://en.wikipedia.org/wiki/GeoRSS>`__" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:314 +msgid "`Wikipedia page for RSS format <http://en.wikipedia.org/wiki/RSS>`__" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:315 +msgid "`RSS 2.0 specification <http://www.rssboard.org/rss-specification>`__" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:316 +msgid "" +"`Wikipedia page for Atom format " +"<http://en.wikipedia.org/wiki/Atom_(standard)>`__" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:318 +msgid "`Atom 1.0 specification <http://www.ietf.org/rfc/rfc4287.txt>`__" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:4 +msgid "GML - Geography Markup Language" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:6 +msgid "GML" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:10 +msgid "" +"OGR has limited support for GML reading and writing. Update of existing " +"files is not supported." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:13 +msgid "Supported GML flavors :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:16 +msgid "Read" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:16 +msgid "Write" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:18 +msgid "GML2 and GML3 that can" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:18 +msgid "GML 2.1.2 or GML 3 SF-0" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:19 +msgid "be translated into simple feature model" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:19 +msgid "(GML 3.1.1 Compliance level SF-0)" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:22 +msgid "" +"Starting with GDAL 2.2, another driver, :ref:`GMLAS <vector.gmlas>`, for " +"GML driven by application schemas, is also available. Both GML and GMLAS " +"drivers have their use cases." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:120 +msgid "Parsers" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:122 +msgid "" +"The reading part of the driver only works if OGR is built with Xerces " +"linked in. When Xerces is unavailable, read support also works if OGR is " +"built with Expat linked in. XML validation is disabled by default. GML " +"writing is always supported, even without Xerces or Expat." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:128 +msgid "" +"Note: if both Xerces and Expat are available at build time, the GML " +"driver will preferentially select at runtime the Expat parser for cases " +"where it is possible (GML file in a compatible encoding), and default " +"back to Xerces parser in other cases. However, the choice of the parser " +"can be overridden by specifying the :config:`GML_PARSER` configuration " +"option to **EXPAT** or **XERCES**." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:136 +#: ../../source/drivers/vector/oapif.rst:62 +msgid "CRS support" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:138 +msgid "" +"The GML driver has coordinate system support. This is only reported when " +"all the geometries of a layer have a srsName attribute, whose value is " +"the same for all geometries. For srsName such as " +"\"urn:ogc:def:crs:EPSG:\" (or \"http://www.opengis.net/def/crs/EPSG/0/\" " +"starting with GDAL 2.1.2), for geographic coordinate systems (as returned" +" by WFS 1.1.0 for example), the axis order should be (latitude, " +"longitude) as required by the standards, but this is unusual and can " +"cause issues with applications unaware of axis order. So by default, the " +"driver will swap the coordinates so that they are in the (longitude, " +"latitude) order and report a SRS without axis order specified. It is " +"possible to get the original (latitude, longitude) order and SRS with " +"axis order by setting the configuration option " +":config:`GML_INVERT_AXIS_ORDER_IF_LAT_LONG` to **NO**." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:152 +msgid "" +"There also situations where the srsName is of the form \"EPSG:XXXX\" " +"(whereas \"urn:ogc:def:crs:EPSG::XXXX\" would have been more explicit on " +"the intent) and the coordinates in the file are in (latitude, longitude) " +"order. By default, OGR will not consider the EPSG axis order and will " +"report the coordinates in (latitude,longitude) order. However, if you set" +" the configuration option :config:`GML_CONSIDER_EPSG_AS_URN` to **YES**, " +"the rules explained in the previous paragraph will be applied." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:160 +msgid "" +"The above also applied for projected coordinate systems whose EPSG " +"preferred axis order is (northing, easting)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:163 +msgid "" +"Starting with GDAL 2.1.2, the :oo:`SWAP_COORDINATES` open option (or " +":config:`GML_SWAP_COORDINATES` configuration option) can be set to " +"AUTO/YES/NO. It controls whether the order of the x/y or long/lat " +"coordinates should be swapped. In AUTO mode, the driver will determine if" +" swapping must be done from the srsName and value of other options like " +":oo:`CONSIDER_EPSG_AS_URN` and :oo:`INVERT_AXIS_ORDER_IF_LAT_LONG`. When " +":oo:`SWAP_COORDINATES` is set to YES, coordinates will be always swapped " +"regarding the order they appear in the GML, and when it set to NO, they " +"will be kept in the same order. The default is AUTO." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:177 +msgid "" +"In contrast to most GML readers, the OGR GML reader does not require the " +"presence of an XML Schema definition of the feature classes (file with " +".xsd extension) to be able to read the GML file. If the .xsd file is " +"absent or OGR is not able to parse it, the driver attempts to " +"automatically discover the feature classes and their associated " +"properties by scanning the file and looking for \"known\" gml objects in " +"the gml namespace to determine the organization. While this approach is " +"error prone, it has the advantage of working for GML files even if the " +"associated schema (.xsd) file has been lost." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:187 +msgid "" +"It is possible to specify an explicit filename for the XSD schema to use," +" by using \"a_filename.gml,xsd=another_filename.xsd\" as a connection " +"string. The XSD can also be specified as the value of the XSD open " +"option." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:193 +msgid "" +"The first time a GML file is opened, if the associated .xsd is absent or " +"could not been parsed correctly, it is completely scanned in order to " +"determine the set of featuretypes, the attributes associated with each " +"and other dataset level information. This information is stored in a .gfs" +" file with the same basename as the target gml file. Subsequent accesses " +"to the same GML file will use the .gfs file to predefine dataset level " +"information accelerating access. To a limited extent the .gfs file can be" +" manually edited to alter how the GML file will be parsed. Be warned that" +" the .gfs file will be ignored if the associated .gml file has a newer " +"timestamp." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:204 +msgid "" +"When prescanning the GML file to determine the list of feature types, and" +" fields, the contents of fields are scanned to try and determine the type" +" of the field. In some applications it is easier if all fields are just " +"treated as string fields. This can be accomplished by setting the " +"configuration option :config:`GML_FIELDTYPES` to the value " +"**ALWAYS_STRING**." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:210 +msgid "" +"The :config:`GML_ATTRIBUTES_TO_OGR_FIELDS` configuration option can be " +"set to **YES** so that attributes of GML elements are also taken into " +"account to create OGR fields." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:214 +msgid "" +"You can use :config:`GML_GFS_TEMPLATE` configuration option (or " +":oo:`GFS_TEMPLATE` open option) set to a **path_to_template.gfs** in " +"order to unconditionally use a predefined GFS file. This option is really" +" useful when you are planning to import many distinct GML files in " +"subsequent steps [**-append**] and you absolutely want to preserve a " +"fully consistent data layout for the whole GML set. Please, pay attention" +" not to use the **-lco LAUNDER=yes** setting when using " +":config:`GML_GFS_TEMPLATE`; this should break the correct recognition of " +"attribute names between subsequent GML import runs." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:225 +msgid "Particular GML application schemas" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:227 +msgid "" +"Feature attributes in nested GML elements (non-flat attribute hierarchy) " +"that can be found in some GML profiles, such as UK Ordnance Survey " +"MasterMap, are detected. IntegerList, RealList and StringList field types" +" when a GML element has several occurrences are also supported." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:232 +msgid "" +"A specialized GML driver - the :ref:`NAS <vector.nas>` driver - is " +"available to read German AAA GML Exchange Format (NAS/ALKIS)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:236 +msgid "The GML driver has partial support for reading AIXM or CityGML files." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:239 +msgid "The GML driver supports reading :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:241 +msgid "" +"`Finnish National Land Survey GML files (a.k.a MTK GML) for topographic " +"data. " +"<http://xml.nls.fi/XML/Schema/Maastotietojarjestelma/MTK/201202/Maastotiedot.xsd>`__" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:244 +msgid "" +"`Finnish National Land Survey GML files for cadastral data " +"<http://xml.nls.fi/XML/Schema/sovellus/ktjkii/modules/kiinteistotietojen_kyselypalvelu_WFS/Asiakasdokumentaatio/ktjkiiwfs/2010/02/>`__." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:246 +msgid "" +"`Cadastral data in Inspire GML schemas " +"<http://inspire.ec.europa.eu/schemas/cp/3.0/CadastralParcels.xsd>`__." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:248 +msgid "" +"`Czech RUIAN Exchange Format (VFR) " +"<http://www.cuzk.cz/Uvod/Produkty-a-sluzby/RUIAN/2-Poskytovani-udaju-" +"RUIAN-ISUI-VDP/Vymenny-format-RUIAN/Vymenny-format-" +"RUIAN-%28VFR%29.aspx>`__." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:251 +msgid "The GML driver supports reading responses to CSW GetRecords queries." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:253 +msgid "Since OGR 2.2, the GML driver supports reading Japanese FGD GML v4 files." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:257 +msgid "Geometry reading" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:259 +msgid "" +"When reading a feature, the driver will by default only take into account" +" the last recognized GML geometry found (in case they are multiples) in " +"the XML subtree describing the feature." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:263 +msgid "" +"But, if the .xsd schema is understood by the XSD parser and declares " +"several geometry fields, or the .gfs file declares several geometry " +"fields, multiple geometry fields will be reported by the GML driver " +"according to :ref:`rfc-41`." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:268 +msgid "" +"In case of multiple geometry occurrences, if a geometry is in a " +"<geometry> element, this will be the one selected. This will make default" +" behavior consistent with Inspire objects." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:272 +msgid "" +"The user can change the .gfs file to select the appropriate geometry by " +"specifying its path with the <GeometryElementPath> element. See the " +"description of the .gfs syntax below." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:277 +msgid "" +"GML geometries including TopoCurve, TopoSurface, MultiCurve are also " +"supported. The TopoCurve type GML geometry can be interpreted as either " +"of two types of geometries. The Edge elements in it contain curves and " +"their corresponding nodes. By default only the curves, the main " +"geometries, are reported as OGRMultiLineString. To retrieve the nodes, as" +" OGRMultiPoint, the configuration option :config:`GML_GET_SECONDARY_GEOM`" +" should be set to the value **YES**. When this is set only the secondary " +"geometries are reported." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:286 +msgid "" +"Arc, ArcString, ArcByBulge, ArcByCenterPoint, Circle and " +"CircleByCenterPoints will be returned as circular string OGR geometries. " +"If they are included in other GML elements such as CurveComposite, " +"MultiCurve, Surface, corresponding non-linear OGR geometries will be " +"returned as well. When reading GML3 application schemas, declarations of " +"geometry fields such as CurvePropertyType, SurfacePropertyType, " +"MultiCurvePropertyType or MultiSurfacePropertyType will be also " +"interpreted as being potential non-linear geometries, and corresponding " +"OGR geometry type will be used for the layer geometry type." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:298 +msgid "gml:xlink resolving" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:300 +msgid "" +"gml:xlink resolving is supported. When the resolver finds an element " +"containing the tag xlink:href, it tries to find the corresponding element" +" with the gml:id in the same gml file, other gml file in the file system " +"or on the web using cURL. Set the configuration option " +":config:`GML_SKIP_RESOLVE_ELEMS` to **NONE** to enable resolution." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:306 +msgid "" +"By default the resolved file will be saved in the same directory as the " +"original file with the extension \".resolved.gml\", if it doesn't exist " +"already. This behavior can be changed using the configuration option " +":config:`GML_SAVE_RESOLVED_TO`. Set it to **SAME** to overwrite the " +"original file. Set it to a **filename ending with .gml** to save it to " +"that location. Any other values are ignored. If the resolver cannot write" +" to the file for any reason, it will try to save it to a temporary file " +"generated using CPLGenerateTempFilename(\"ResolvedGML\"); if it cannot, " +"resolution fails." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:316 +msgid "" +"Note that the resolution algorithm is not optimized for large files. For " +"files with more than a couple of thousand xlink:href tags, the process " +"can go beyond a few minutes. A rough progress is displayed through " +"CPLDebug() for every 256 links. It can be seen by setting the environment" +" variable :config:`CPL_DEBUG`. The resolution time can be reduced if you " +"know any elements that will not be needed. Mention a comma separated list" +" of names of such elements with the configuration option " +":config:`GML_SKIP_RESOLVE_ELEMS`. Set it to **ALL** to skip resolving " +"altogether (default action). Set it to **NONE** to resolve all the " +"xlinks." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:327 +msgid "" +"An alternative resolution method is available. This alternative method " +"will be activated using the configuration option " +":config:`GML_SKIP_RESOLVE_ELEMS=HUGE`. In this case any gml:xlink will be" +" resolved using a temporary SQLite DB so to identify any corresponding " +"gml:id relation. At the end of this SQL-based process, a resolved file " +"will be generated exactly as in the **NONE** case but without their " +"limits. The main advantages in using an external (temporary) DBMS so to " +"resolve gml:xlink and gml:id relations are the following:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:336 +msgid "" +"no memory size constraints. The **NONE** method stores the whole GML " +"node-tree in-memory; and this practically means that no GML file bigger " +"than 1 GB can be processed at all using a 32-bit platform, due to memory " +"allocation limits. Using a file-system based DBMS avoids at all this " +"issue." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:341 +msgid "" +"by far better efficiency, most notably when huge GML files containing " +"many thousands (or even millions) of xlink:href / gml:id relational " +"pairs." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:344 +msgid "" +"using the :config:`GML_SKIP_RESOLVE_ELEMS=HUGE` method realistically " +"allows to successfully resolve some really huge GML file (3GB+) " +"containing many millions xlink:href / gml:id in a reasonable time (about " +"an hour or so on)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:348 +msgid "" +"The :config:`GML_SKIP_RESOLVE_ELEMS=HUGE` method supports the following " +"further configuration option:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:355 +msgid "TopoSurface interpretation rules [polygons and internal holes]" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:357 +msgid "" +"The GML driver is able to recognize two different interpretation rules " +"for TopoSurface when a polygon contains any internal hole:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:361 +msgid "the previously supported interpretation rule assumed that:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:363 +#: ../../source/drivers/vector/gml.rst:374 +msgid "each TopoSurface may be represented as a collection of many Faces" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:364 +msgid "" +"*positive* Faces [i.e. declaring **orientation=\"+\"**] are assumed to " +"represent the Exterior Ring of some Polygon." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:366 +msgid "" +"*negative* Faces [i.e. declaring **orientation=\"-\"**] are assumed to " +"represent an Interior Ring (aka *hole*) belonging to the latest declared " +"Exterior Ring." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:369 +msgid "" +"ordering any Edge used to represent each Ring is important: each Edge is " +"expected to be exactly adjacent to the next one." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:372 +msgid "the new interpretation rule now assumes that:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:375 +msgid "" +"the declared **orientation** for any Face has nothing to deal with " +"Exterior/Interior Rings" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:377 +msgid "" +"each Face is now intended to represent a complete Polygon, eventually " +"including any possible Interior Ring (*holes*)" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:379 +msgid "" +"the relative ordering of any Edge composing the same Face is completely " +"not relevant" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:382 +msgid "" +"The newest interpretation seems to fully match GML 3 standard " +"recommendations; so this latest is now assumed to be the default " +"interpretation supported by OGR." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:386 +msgid "" +"**NOTE** : Using the newest interpretation requires GDAL/OGR to be built " +"against the GEOS library." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:389 +msgid "" +"Using the :config:`GML_FACE_HOLE_NEGATIVE` configuration option you can " +"select the actual interpretation to be applied when parsing GML 3 " +"topologies:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:393 +msgid "" +"setting :config:`GML_FACE_HOLE_NEGATIVE=NO` (*default* option) will " +"activate the newest interpretation rule" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:395 +msgid "" +"but explicitly setting :config:`GML_FACE_HOLE_NEGATIVE=YES` still enables" +" to activate the old interpretation rule" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:412 +msgid "" +"If the GML file is not encoded in one of the previous encodings and the " +"only parser available is Expat, it will not be parsed by the GML driver. " +"You may convert it into one of the supported encodings with the *iconv* " +"utility for example and change accordingly the *encoding* parameter value" +" in the XML header." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:418 +msgid "When writing a GML file, the driver expects UTF-8 content to be passed in." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:421 +msgid "" +"Note: The .xsd schema files are parsed with an integrated XML parser " +"which does not currently understand XML encodings specified in the XML " +"header. It expects encoding to be always UTF-8. If attribute names in the" +" schema file contains non-ascii characters, it is better to use *iconv* " +"utility and convert the .xsd file into UTF-8 encoding first." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:428 +msgid "Feature id (fid / gml:id)" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:430 +msgid "" +"The driver exposes the content of the gml:id attribute as a string field " +"called *gml_id*, when reading GML WFS documents. When creating a GML3 " +"document, if a field is called *gml_id*, its content will also be used to" +" write the content of the gml:id attribute of the created feature." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:436 +msgid "" +"The driver autodetects the presence of a fid (GML2) (resp. gml:id (GML3))" +" attribute at the beginning of the file, and, if found, exposes it by " +"default as a *fid* (resp. *gml_id*) field. The autodetection can be " +"overridden by specifying the :config:`GML_EXPOSE_FID` or " +":config:`GML_EXPOSE_GML_ID` configuration option to **YES** or **NO**." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:444 +msgid "" +"When creating a GML2 document, if a field is called *fid*, its content " +"will also be used to write the content of the fid attribute of the " +"created feature." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:451 +#: ../../source/drivers/vector/gmlas.rst:172 +msgid "Performance issues with large multi-layer GML files." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:453 +msgid "" +"There is only one GML parser per GML datasource shared among the various " +"layers. By default, the GML driver will restart reading from the " +"beginning of the file, each time a layer is accessed for the first time, " +"which can lead to poor performance with large GML files." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:458 +msgid "" +"The :config:`GML_READ_MODE` configuration option can be set to " +"**SEQUENTIAL_LAYERS** if all features belonging to the same layer are " +"written sequentially in the file. The reader will then avoid unnecessary " +"resets when layers are read completely one after the other. To get the " +"best performance, the layers must be read in the order they appear in the" +" file." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:465 +msgid "" +"If no .xsd and .gfs files are found, the parser will detect the layout of" +" layers when building the .gfs file. If the layers are found to be " +"sequential, a *<SequentialLayers>true</SequentialLayers>* element will be" +" written in the .gfs file, so that the :config:`GML_READ_MODE` will be " +"automatically initialized to SEQUENTIAL_LAYERS if not explicitly set by " +"the user." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:472 +msgid "" +"The :config:`GML_READ_MODE` configuration option can be set to " +"INTERLEAVED_LAYERS to be able to read a GML file whose features from " +"different layers are interleaved. In the case, the semantics of the " +"GetNextFeature() will be slightly altered, in a way where a NULL return " +"does not necessarily mean that all features from the current layer have " +"been read, but it could also mean that there is still a feature to read, " +"but that belongs to another layer. In that case, the file should be read " +"with code similar to the following one :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:574 +msgid "Whether to consider srsName like EPSG:XXXX as respecting EPSG axis order." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:632 +msgid "" +"When changing the value of most of the above options, it is recommended " +"to delete the ``.gfs`` file if it pre-exists, otherwise mis-behavior " +"might be observed." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:640 +msgid "" +"On export all layers are written to a single GML file all in a single " +"feature collection. Each layer's name is used as the element name for " +"objects from that layer. Geometries are always written as the " +"ogr:geometryProperty element on the feature." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:691 +msgid "" +"*GML2* in order to write GML files that follow GML 2.1.2 (Default before " +"GDAL 3.4)" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:692 +msgid "*GML3* in order to write GML files that follow GML 3.1.1 SF-0 profile." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:694 +msgid "" +"*GML3Deegree* in order to produce a GML 3.1.1 .XSD schema, with a few " +"variations with respect to what is recommended by GML3 SF-0 profile, but " +"that will be better accepted by some software (such as Deegree 3)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:698 +msgid "" +"*GML3.2*\\ in order to write GML files that follow GML 3.2.1 SF-0 " +"profile. (Default since GDAL 3.4)" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:701 +msgid "" +"Non-linear geometries can be written. This is only compatible with " +"selecting on of that above GML3 format variant. Otherwise, such " +"geometries will be approximating into their closest matching linear " +"geometry. Note: fields of type StringList, RealList or IntegerList can be" +" written. This will cause to advertise the SF-1 profile in the .XSD " +"schema (such types are not supported by SF-0)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:713 +msgid "" +"Whether to use the gml:FeatureCollection, instead of creating a dedicated" +" container element in the target namespace. Only valid for " +"FORMAT=GML3/GML3.2. Note that gml:FeatureCollection has been deprecated " +"in GML 3.2, and is not allowed by the OGC 06-049r1 \"Geography Markup " +"Language (GML) simple features profile\" (for GML 3.1.1) and OGC 10-100r3" +" \"Geography Markup Language (GML) simple features profile (with " +"Corrigendum)\" (for GML 3.2) specifications." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:799 +msgid "" +"Writing to /dev/stdout or /vsistdout/ is also supported. Note that in " +"that case, only the content of the GML file will be written to the " +"standard output (and not the .xsd). The <boundedBy> element will not be " +"written. This is also the case if writing in /vsigzip/" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:805 +msgid "Syntax of .gfs files" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:807 +msgid "" +"A XML Schema for .gfs files can be found at " +"https://raw.githubusercontent.com/OSGeo/gdal/master/ogr/ogrsf_frmts/gml/data/gfs.xsd" +" ." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:810 +#: ../../source/drivers/vector/gml.rst:918 +#: ../../source/drivers/vector/gml.rst:988 +msgid "Let's consider the following test.gml file :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:834 +#: ../../source/drivers/vector/gml.rst:1001 +#: ../../source/drivers/vector/gml.rst:1069 +msgid "and the following associated .gfs file." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:858 +msgid "" +"Note the presence of the '|' character in the <ElementPath> and " +"<GeometryElementPath> elements to specify the wished field/geometry " +"element that is a nested XML element. Nested field elements are " +"supported, as well as specifying <GeometryElementPath> If " +"GeometryElementPath is not specified, the GML driver will use the last " +"recognized geometry element." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:865 +msgid "" +"The <GeometryType> element can be specified to force the geometry type. " +"Accepted values are : 0 (any geometry type), 1 (point), 2 (linestring), 3" +" (polygon), 4 (multipoint), 5 (multilinestring), 6 (multipolygon), 7 " +"(geometrycollection)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:870 +msgid "" +"The <GeometryElementPath> and <GeometryType> can be specified as many " +"times as there are geometry fields in the GML file. Another possibility " +"is to define a <GeomPropertyDefn>element as many times as necessary:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:894 +#: ../../source/drivers/vector/gml.rst:1023 +msgid "The output of *ogrinfo test.gml -ro -al* is:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:913 +msgid "Advanced .gfs syntax" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:916 +msgid "Specifying ElementPath to find objects embedded into top level objects" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:960 +msgid "" +"By default, only the TopLevelObject object would be reported and it would" +" only use the second geometry. This is not the desired behavior in that " +"instance. You can edit the generated .gfs and modify it like the " +"following in order to specify a full path to the element (top level XML " +"element being omitted) :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:982 +msgid "Getting XML attributes as OGR fields" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:984 +msgid "" +"The element@attribute syntax can be used in the <ElementPath> to specify " +"that the value of attribute 'attribute' of element 'element' must be " +"fetched." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1041 +msgid "Using conditions on XML attributes" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1043 +msgid "" +"A <Condition> element can be specified as a child element of a " +"<PropertyDefn>. The content of the Condition follows a minimalistic XPath" +" syntax. It must be of the form @attrname[=|!=]'attrvalue' [and|or " +"other_cond]*. Note that 'and' and 'or' operators cannot be mixed (their " +"precedence is not taken into account)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1049 +msgid "" +"Several <PropertyDefn> can be defined with the same <ElementPath>, but " +"with <Condition> that must be mutually exclusive." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1052 +msgid "Let's consider the following testcondition.gml file :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1105 +msgid "The output of *ogrinfo testcondition.gml -ro -al* is:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1127 +msgid "Registry for GML application schemas" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1129 +msgid "" +"The \"data\" directory of the GDAL installation contains a " +"\"gml_registry.xml\" file that links feature types of GML application " +"schemas to .xsd or .gfs files that contain their definition. This is used" +" in case no valid .gfs or .xsd file is found next to the GML file." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1134 +msgid "" +"An alternate location for the registry file can be defined by setting its" +" full pathname to the GML_REGISTRY configuration option." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1137 +msgid "An example of such a file is :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1179 +msgid "" +"XML schema definition (.xsd) files are pointed by the schemaLocation " +"attribute, whereas OGR .gfs files are pointed by the gfsSchemaLocation " +"attribute. In both cases, the filename can be a URL (http://, https://), " +"an absolute filename, or a relative filename (relative to the location of" +" gml_registry.xml)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1185 +msgid "" +"The schema is used if and only if the namespace prefix and URI are found " +"in the first bytes of the GML file (e.g. " +"*xmlns:ktjkiiwfs=\"http://xml.nls.fi/ktjkiiwfs/2010/02\"*), and that the " +"feature type is also detected in the first bytes of the GML file (e.g. " +"*ktjkiiwfs:KiinteistorajanSijaintitiedot*). If the element value is " +"defined than the schema is used only if the feature type together with " +"the value is found in the first bytes of the GML file (e.g. " +"*vf:TypSouboru>OB_UKSH*)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1195 +msgid "Building junction tables" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1197 +msgid "" +"The :source_file:`swig/python/gdal-" +"utils/osgeo_utils/samples/ogr_build_junction_table.py` script can be used" +" to build a `junction table " +"<http://en.wikipedia.org/wiki/Junction_table>`__ from OGR layers that " +"contain \"XXXX_href\" fields. Let's considering the following output of a" +" GML file with links to other features :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1216 +msgid "After running" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1222 +msgid "to import it into PostGIS and" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1228 +msgid "" +", a *myfeature_otherfeature* table will be created and will contain the " +"following content :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1232 +msgid "myfeature_gml_id" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1232 +msgid "otherfeature_gml_id" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1234 +#: ../../source/drivers/vector/gml.rst:1235 +msgid "myFeature.1" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1234 +#: ../../source/drivers/vector/gml.rst:1237 +msgid "otherFeature.10" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1235 +msgid "otherFeature.20" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1236 +#: ../../source/drivers/vector/gml.rst:1237 +msgid "myFeature.2" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1236 +msgid "otherFeature.30" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1241 +msgid "Reading datasets resulting from a WFS 2.0 join queries" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1243 +msgid "The GML driver can read datasets resulting from a WFS 2.0 join queries." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1245 +msgid "Such datasets typically look like:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1293 +msgid "" +"OGR will group together the attributes from the layers participating to " +"the join and will prefix them with the layer name. So the above example " +"will be read as the following:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1323 +msgid "" +"The GML driver supports reading and writing the geometry coordinate " +"precision, using the :cpp:class:`OGRGeomCoordinatePrecision` settings of " +"the :cpp:class:`OGRGeomFieldDefn`. Those settings are used to round the " +"coordinates of the geometry of the features to an appropriate decimal " +"precision." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1328 +msgid "" +"Implementation details: the coordinate precision is stored in the XML " +"schema as " +"``xs:annotation/xs:appinfo[source=\"http://ogr.maptools.org/\"]/ogr:xy_coordinate_resolution``" +" and " +"``xs:annotation/xs:appinfo[source=\"http://ogr.maptools.org/\"]/ogr:z_coordinate_resolution``" +" optional elements in the declaration of the geometry column. Their " +"numeric value is expressed in the units of the SRS." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1350 +msgid "" +"The ogr2ogr utility can be used to dump the results of a Oracle query to " +"GML:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1357 +msgid "" +"The ogr2ogr utility can be used to dump the results of a PostGIS query to" +" GML:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1367 +msgid "`GML Specifications <http://www.opengeospatial.org/standards/gml>`__" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1368 +msgid "" +"`GML 3.1.1 simple features profile - OGC(R) 06-049r1 " +"<http://portal.opengeospatial.org/files/?artifact_id=15201>`__" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1370 +msgid "" +"`Geography Markup Language (GML) simple features profile (with " +"Corrigendum) (GML 3.2.1) - OGC(R) 10-100r3 " +"<https://portal.opengeospatial.org/files/?artifact_id=42729>`__" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1373 +msgid "`Xerces <http://xml.apache.org/xerces2-j/index.html>`__" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1374 +msgid "" +":ref:`GMLAS - Geography Markup Language (GML) driven by application " +"schemas <vector.gmlas>`" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1376 +msgid "" +":ref:`NAS/ALKIS : specialized GML driver for cadastral data in Germany " +"<vector.nas>`" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1382 +msgid "" +"Implementation for :config:`GML_SKIP_RESOLVE_ELEMS=HUGE` was contributed " +"by A.Furieri, with funding from Regione Toscana" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1384 +msgid "" +"Support for cadastral data in Finnish National Land Survey GML and " +"Inspire GML was funded by The Information Centre of the Ministry of " +"Agriculture and Forestry (Tike)" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:4 +msgid "GMLAS - Geography Markup Language (GML) driven by application schemas" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:8 +msgid "GMLAS" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:12 +msgid "" +"This driver can read and write XML files of arbitrary structure, included" +" those containing so called Complex Features, provided that they are " +"accompanied by one or several XML schemas that describe the structure of " +"their content. While this driver is generic to any XML schema, the main " +"target is to be able to read and write documents referencing directly or " +"indirectly to the GML namespace." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:19 +msgid "The driver requires Xerces-C >= 3.1." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:21 +msgid "" +"The driver can deal with files of arbitrary size with a very modest RAM " +"usage, due to its working in streaming mode." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:36 +msgid "" +"The connection string is GMLAS:/path/to/the.gml. Note the ``GMLAS:`` " +"prefix. If this prefix it is omitted, then the GML driver is likely to be" +" used." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:39 +msgid "" +"Alternatively, starting with GDAL 3.10, specifying the ``-if GMLAS`` " +"option to command line utilities accepting it, or ``GMLAS`` as the only " +"value of the ``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also " +"forces the driver to recognize the passed filename." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:43 +msgid "" +"It is also possible to only used ``GMLAS:`` as the connection string, but" +" in that case the schemas must be explicitly provided with the ``XSD`` " +"open option." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:48 +msgid "Mapping of XML structure to OGR layers and fields" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:50 +msgid "" +"The driver scans the XML schemas referenced by the XML/GML to build the " +"OGR layers and fields. It is strictly required that the schemas, directly" +" or indirectly used, are fully valid. The content of the XML/GML file " +"itself is marginally used, mostly to determine the SRS of geometry " +"columns." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:56 +msgid "" +"XML elements declared at the top level of a schema will generally be " +"exposed as OGR layers. Their attributes and sub-elements of simple XML " +"types (string, integer, real, ...) will be exposed as OGR fields. For " +"sub-elements of complex type, different cases can happen. If the " +"cardinality of the sub-element is at most one and it is not referenced by" +" other elements, then it is \"flattened\" into its enclosing element. " +"Otherwise it will be exposed as a OGR layer, with either a link to its " +"\"parent\" layer if the sub-element is specific to its parent element, or" +" through a junction table if the sub-element is shared by several " +"parents." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:67 +msgid "" +"By default the driver is robust to documents non strictly conforming to " +"the schemas. Unexpected content in the document will be silently ignored," +" as well as content required by the schema and absent from the document." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:72 +msgid "" +"Consult the :ref:`GMLAS mapping examples <gmlas_mapping_examples>` page " +"for more details." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:75 +msgid "" +"By default in the configuration, swe:DataRecord and swe:DataArray " +"elements from the Sensor Web Enablement (SWE) Common Data Model namespace" +" will receive a special processing, so they are mapped more naturally to " +"OGR concepts. The swe:field elements will be mapped as OGR fields, and " +"the swe:values element of a swe:DataArray will be parsed into OGR " +"features in a dedicated layer for each swe:DataArray. Note that those " +"conveniency exposure is for read-only purpose. When using the write side " +"of the driver, only the content of the general mapping mechanisms will be" +" used." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:86 +msgid "Metadata layers" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:88 +msgid "" +"Three special layers \"_ogr_fields_metadata\", \"_ogr_layers_metadata\", " +"\"_ogr_layer_relationships\" and \"_ogr_other_metadata\" add extra " +"information to the basic ones you can get from the OGR data model on OGR " +"layers and fields." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:93 +msgid "" +"Those layers are exposed if the :oo:`EXPOSE_METADATA_LAYERS` open option " +"is set to YES (or if enabled in the configuration). They can also be " +"individually retrieved by specifying their name in calls to " +"GetLayerByName(), or on as layer names with the ogrinfo and ogr2ogr " +"utility." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:99 +msgid "" +"Consult the :ref:`GMLAS metadata layers <gmlas_metadata_layers>` page for" +" more details." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:103 +msgid "Configuration file" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:105 +msgid "" +"A default configuration file " +":source_file:`ogr/ogrsf_frmts/gmlas/data/gmlasconf.xml` file is provided " +"in the data directory of the GDAL installation. Its structure and content" +" is documented in :source_file:`ogr/ogrsf_frmts/gmlas/data/gmlasconf.xsd`" +" schema." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:112 +msgid "This configuration file enables the user to modify the following settings:" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:115 +msgid "whether remote schemas should be downloaded. Enabled by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:116 +msgid "whether the local cache of schemas is enabled. Enabled by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:117 +msgid "the path of the local cache. By default, $HOME/.gdal/gmlas_xsd_cache" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:118 +msgid "" +"whether validation of the document against the schemas should be enabled." +" Disabled by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:120 +msgid "" +"whether validation error should cause dataset opening to fail. Disabled " +"by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:122 +msgid "" +"whether the metadata layers should be exposed by default. Disabled by " +"default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:124 +msgid "" +"whether a 'ogr_pkid' field should always be generated. Disabled by " +"default. Turning that on can be useful on layers that have a ID attribute" +" whose uniqueness is not guaranteed among various documents. Which could " +"cause issues when appending several documents into a target database " +"table." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:129 +msgid "" +"whether layers and fields that are not used in the XML document should be" +" removed. Disable by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:131 +msgid "whether OGR array data types can be used. Enabled by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:132 +msgid "" +"whether the XML definition of the GML geometry should be reported as a " +"OGR string field. Disabled by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:134 +msgid "" +"whether only XML elements that derive from gml:_Feature or " +"gml:AbstractFeature should be considered in the initial pass of the " +"schema building, when at least one element in the schemas derive from " +"them. Enabled by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:138 +msgid "several rules to configure if and how xlink:href should be resolved." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:139 +msgid "" +"a definition of XPaths of elements and attributes that must be ignored, " +"so as to lighten the number of OGR layers and fields." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:142 +msgid "" +"This file can be adapted and modified versions can be provided to the " +"driver with the :oo:`CONFIG_FILE` open option. None of the elements of " +"the configuration file are required. When they are absent, the default " +"value indicated in the schema documentation is used." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:147 +msgid "" +"Configuration can also be provided through other open options. Note that " +"some open options have identical names to settings present in the " +"configuration file. When such open option is provided, then its value " +"will override the one of the configuration file (either the default one, " +"or the one provided through the :oo:`CONFIG_FILE` open option)." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:154 +msgid "Geometry support" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:156 +msgid "" +"XML schemas only indicate the geometry type but do not constraint the " +"spatial reference systems (SRS), so it is theoretically possible to have " +"object instances of the same class having different SRS for the same " +"geometry field. This is not practical to deal with, so when geometry " +"fields are detected, an initial scan of the document is done to find the " +"first geometry of each geometry field that has an explicit srsName set. " +"This one will be used for the whole geometry field. In case other " +"geometries of the same field would have different SRS, they will be " +"reprojected." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:166 +msgid "" +"By default, only the OGR geometry built from the GML geometry is exposed " +"in the OGR feature. It is possible to change the IncludeGeometryXML " +"setting of the configuration file to true so as to expose a OGR string " +"field with the XML definition of the GML geometry." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:174 +msgid "" +"Traditionnaly to read a OGR datasource, one iterate over layers with " +"GDALDataset::GetLayer(), and for each layer one iterate over features " +"with OGRLayer::GetNextFeature(). While this approach still works for the " +"GMLAS driver, it may result in very poor performance on big documents or " +"documents using complex schemas that are translated in many OGR layers." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:180 +msgid "" +"It is thus recommended to use GDALDataset::GetNextFeature() to iterate " +"over features as soon as they appear in the .gml/.xml file. This may " +"return features from non-sequential layers, when the features include " +"nested elements." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:260 +msgid "Whether unused layers should be removed from the reported layers." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:288 +msgid "" +"The GMLAS driver can write XML documents in a schema-driven way by " +"converting a source dataset (contrary to most other drivers that have " +"read support that implement the CreateLayer() and CreateFeature() " +"interfaces). The typical workflow is to use the read side of the GMLAS " +"driver to produce a SQLite/Spatialite/ PostGIS database, potentially " +"modify the features imported and re-export this database as a new XML " +"document." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:296 +msgid "" +"The driver will identify in the source dataset \"top-level\" layers, and " +"in those layers will find which features are not referenced by other top-" +"level layers. As the creation of the output XML is schema-driver, the " +"schemas need to be available. There are two possible ways:" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:301 +msgid "" +"either the result of the processing of the schemas was stored as the 4 " +"\\_ogr_\\* metadata tables in the source dataset by using the " +":oo:`EXPOSE_METADATA_LAYERS=YES` open option when converting the source " +".xml)," +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:305 +msgid "" +"or the schemas can be specified at creation time with the " +":dsco:`INPUT_XSD` creation option." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:308 +msgid "" +"By default, the driver will \"wrap\" the features inside a WFS 2.0 " +"wfs:FeatureCollection / wfs:member element. It is also possible to ask " +"the driver to create instead a custom wrapping .xsd file that declares " +"the ogr_gmlas:FeatureCollection / ogr_gmlas:featureMember XML elements." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:313 +msgid "" +"Note that while the file resulting from the export should be XML valid, " +"there is no strong guarantee that it will validate against the additional" +" constraints expressed in XML schema(s). This will depend on the content " +"of the features (for example if converting from a GML file that is not " +"conformant to the schemas, the output of the driver will generally be not" +" validating)" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:320 +msgid "" +"If the input layers have geometries stored as GML content in a \\_xml " +"suffixed field, then the driver will compare the OGR geometry built from " +"that XML content with the OGR geometry stored in the dedicated geometry " +"field of the feature. If both match, then the GML content stored in the " +"\\_xml suffixed field will be used, such as to preserve particularities " +"of the initial GML content. Otherwise GML will be exported from the OGR " +"geometry." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:328 +msgid "" +"To increase export performance on very large databases, creating " +"attribute indexes on the fields pointed by the 'layer_pkid_name' " +"attribute in '_ogr_layers_metadata' might help." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:333 +msgid "ogr2ogr behavior" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:335 +msgid "" +"When using ogr2ogr / GDALVectorTranslate() to convert to XML/GML from a " +"source database, there are restrictions to the options that can be used. " +"Only the following options of ogr2ogr are supported:" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:339 +msgid "dataset creation options (see below)" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:340 +msgid "layer names" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:341 +msgid "spatial filter through -spat option." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:342 +msgid "attribute filter through -where option" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:344 +msgid "" +"The effect of spatial and attribute filtering will only apply on top-" +"levels layers. Sub-features selected through joins will not be affected " +"by those filters." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:351 +msgid "" +"|about-dataset-creation-options| The supported dataset creation options " +"are:" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:451 +msgid "Listing content of a data file:" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:457 +msgid "Converting to PostGIS:" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:463 +msgid "Converting to Spatialite and back to GML" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:473 +msgid "" +":ref:`GML <vector.gml>`: general purpose driver not requiring the " +"presence of schemas, but with limited support for complex features" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:475 +msgid "" +":ref:`NAS/ALKIS <vector.nas>`: specialized GML driver for cadastral data " +"in Germany" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:481 +msgid "" +"Initial implementation has been funded by the European Union's Earth " +"observation programme Copernicus, as part of the tasks delegated to the " +"European Environment Agency." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:485 +msgid "" +"Development of special processing of some Sensor Web Enablement (SWE) " +"Common Data Model swe:DataRecord and swe:DataArray constructs has been " +"funded by Bureau des Recherches Géologiques et Minières (BRGM)." +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:4 +msgid "GMLAS - Mapping examples" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:6 +msgid "" +"This page gives a few examples of how XML constructs are mapped to OGR " +"layers and fields by the :ref:`vector.gmlas` driver." +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:10 +msgid "Mapping examples" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:14 +msgid "Document" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:15 +msgid "OGR layers" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:16 +#: ../../source/drivers/vector/selafin.rst:77 +msgid "Comments" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:47 +msgid "" +"Element with attributes and sub-elements of simple type and maximum " +"cardinality of 1." +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:98 +msgid "Example with array and child layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:152 +msgid "" +"Example of nested element, that can be folded into main layer. Use of an " +"attribute on a sub-element." +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:268 +msgid "" +"Example of of a common element \"name\" referenced by 2 layers " +"\"MyFeature\" and \"MyFeature1\". The links are established through the " +"junction layers \"MyFeature_names_name_name\" and " +"\"MyFeature2_names_name_name\"." +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:273 +msgid "swe:DataArray" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:275 +msgid "The following snippet" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:317 +msgid "will receive a special processing to be mapped into a dedicated layer:" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:353 +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:161 +msgid ":ref:`main documentation page for GMLAS driver <vector.gmlas>`" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:4 +msgid "GMLAS - Metadata layers" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:6 +msgid "" +"This page details the structure of the extra metadata layers reported by " +"the :ref:`vector.gmlas` driver." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:10 +msgid "\\_ogr_fields_metadata layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:12 +msgid "" +"This layer gives metadata about OGR fields, and also \"abstract\" fields " +"that describe the relation ship between a parent and child layer." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:15 +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:93 +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:121 +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:142 +msgid "Its fields are:" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:17 +msgid "``layer_name``: Name of the layer to which the field belongs to" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:19 +msgid "" +"``field_name``: Name of the field. May be null when field_category is " +"PATH_TO_CHILD_ELEMENT_NO_LINK or GROUP" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:22 +msgid "" +"``field_xpath``: XPath of the element/attribute whose content is used for" +" the field. The XPath is relative to the element that is the direct " +"parent of this element/attribute, or a parent element in case of " +"flattening. May be null for a field generated by OGR." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:27 +msgid "" +"``field_type``: the XML schema base data type (string, int, long, ID, " +"...). Extended with \"geometry\". May be null for a field generated by " +"OGR" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:30 +msgid "``field_is_list``: Whether the XML type is a list." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:32 +msgid "" +"``field_min_occurs``: Integer value with the minimum number of " +"occurrences of values. 0 or 1 typically. Or more for array types. May be " +"null for a field generated by OGR" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:36 +msgid "" +"``field_max_occurs``: Integer value with the maximum number of " +"occurrences of values. 1 typically. Or more for array types. 2147483647 " +"means unlimited. May be null for a field generated by OGR" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:40 +msgid "" +"``field_repetition_on_sequence``: Boolean value to indicate if the field " +"is related to a <sequence maxOccurs=\">1 or unbounded\"> construct. Only " +"set when field_max_occurs is not 0 or 1." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:44 +msgid "``field_default_value``: Default value of the field, or null" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:46 +msgid "``field_fixed_value``: Fixed value of the field, or null" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:48 +msgid "" +"``field_category``: Category of the field. May be REGULAR, " +"PATH_TO_CHILD_ELEMENT_NO_LINK, PATH_TO_CHILD_ELEMENT_WITH_LINK, " +"PATH_TO_CHILD_ELEMENT_WITH_JUNCTION_TABLE, GROUP or SWE_FIELD. May be " +"null for a field generated by OGR." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:53 +msgid "" +"``field_related_layer``: Name of the child layer for field_category != " +"REGULAR" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:55 +msgid "" +"``field_junction_layer``: Name of the junction layer. Only set if " +"field_category is equal to PATH_TO_CHILD_ELEMENT_WITH_JUNCTION_TABLE" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:58 +msgid "``field_documentation``: Documentation from the schema." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:60 +msgid "Explanation of field_category values:" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:62 +msgid "" +"REGULAR: the field is made from the value of an element or attribute that" +" is a direct child of the element that is the root of the layer " +"considered." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:65 +msgid "" +"PATH_TO_CHILD_ELEMENT_NO_LINK: A field declared with this category is not" +" instantiated as a OGR field of the layer 'layer_name'. It is merely " +"there to declare the relationship between the parent and child layers. " +"This is when a sub-element is of a complex type or a repeated sub-element" +" of simple type that does not match one of the OGR array types." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:71 +msgid "" +"PATH_TO_CHILD_ELEMENT_WITH_LINK: the content of this field is the primary" +" key of a OGR feature of another layer. The field_related_layer field " +"contains the name of that linked layer." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:74 +msgid "" +"PATH_TO_CHILD_ELEMENT_WITH_JUNCTION_TABLE: A field declared with this " +"category is not instantiated as a OGR field of the layer 'layer_name'. It" +" is merely there to declare the relationship between the parent and child" +" layers. This is when the link between the parent and child layer is done" +" through a junction table (case where the child layer is referenced by " +"other parent layers)." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:80 +msgid "" +"GROUP: A field declared with this category is not instantiated as a OGR " +"field of the layer 'layer_name'. It is merely there to declare the " +"relationship between the parent and child layers. This is when a layer " +"uses XML schema group constructs with repeated cardinality." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:84 +msgid "" +"SWE_FIELD: A field derived from special processing of swe:DataRecord or " +"swe:DataArray elements." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:89 +msgid "\\_ogr_layers_metadata layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:91 +msgid "This layer gives metadata about OGR layers." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:95 +msgid "``layer_name``: Name of the layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:97 +msgid "" +"``layer_xpath``: XPath of the element that is used as the root element " +"for the layer. May be suffixed with \";extra=XXXX\" for group constructs " +"or repeated sequences of repeated elements, so as to distinguish for the " +"XPath of their parent element. Will be null for junction tables or " +"SWE_DATA_ARRAY layers." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:102 +msgid "" +"``layer_category``: Category of the layer. One of TOP_LEVEL_ELEMENT, " +"NESTED_ELEMENT, JUNCTION_TABLE or SWE_DATA_ARRAY" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:105 +msgid "" +"``layer_pkid_name``: Name of the primary key field. This is the text " +"attribute that uniquely identified a feature (in its layer). This is the " +"XML attribute/name of type xs:ID when it exists, otherwise a \"ogr_pkid\"" +" field is automatically created. Will be null for SWE_DATA_ARRAY layers." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:110 +msgid "" +"``layer_parent_pkid_name``: Name of the field that is a foreign key to " +"the parent layer of this layer. Only set for a NESTED_ELEMENT layer." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:113 +msgid "``layer_documentation``: Documentation from the schema." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:117 +msgid "\\_ogr_layer_relationships layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:119 +msgid "This layer gives metadata about relationship between OGR layers." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:123 +msgid "``parent_layer``: Name of the parent layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:125 +msgid "``parent_pkid``: Name of the primary key of the parent layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:127 +msgid "" +"``parent_element_name``: Name of the XML element that links from the " +"parent to the child. Will be null when the child layer is due to group " +"constructs or repeated sequences of repeated elements of the parent." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:131 +msgid "``child_layer``: Name of the child layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:133 +msgid "" +"``child_pkid``: Name of the primary key of the child layer. Will be null " +"for SWE_DATA_ARRAY layers" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:138 +msgid "\\_ogr_other_metadata layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:140 +msgid "This layer contains key / value pairs with different information." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:144 +msgid "``key``: Name of the metadata item" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:145 +msgid "``value``: Value of the metadata imtem" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:147 +msgid "Possible keys are :" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:149 +msgid "document_filename: Filename of the XML/GML file read." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:150 +msgid "configuration_filename: Filename of the XML configuration file used." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:151 +msgid "configuration_inlined: XML content of the configuration file." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:152 +msgid "namespace_uri_XX: URI of a namespace referenced by the schema(s)." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:153 +msgid "namespace_location_XX: Location of a schema." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:154 +msgid "namespace_prefix_XX: Prefix of a namespace referenced by the schema(s)." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:156 +msgid "gml_version: GML version, such as 2.1.2, 3.1.1 or 3.2.1" +msgstr "" + +#: ../../source/drivers/vector/gmt.rst:6 +msgid "GMT" +msgstr "" + +#: ../../source/drivers/vector/gmt.rst:10 +msgid "" +"OGR supports reading and writing GMT ASCII vector format. This is the " +"format used by the Generic Mapping Tools (GMT) package, and includes " +"recent additions to the format to handle more geometry types, and " +"attributes. Currently GMT files are only supported if they have the " +"extension \".gmt\". Old (simple) GMT files are treated as either point, " +"or linestring files depending on whether a \">\" line is encountered " +"before the first vertex. New style files have a variety of auxiliary " +"information including geometry type, layer extents, coordinate system and" +" attribute field declarations in comments in the header, and for each " +"feature can have attributes." +msgstr "" + +#: ../../source/drivers/vector/gmt.rst:33 +msgid "" +"The driver supports creating new GMT files, and appending additional " +"features to existing files, but update of existing features is not " +"supported. Each layer is created as a separate .gmt file. If a name that " +"ends with .gmt is not given, then the GMT driver will take the layer name" +" and add the \".gmt\" extension." +msgstr "" + +#: ../../source/drivers/vector/gmt.rst:39 +msgid "" +"Writing to /dev/stdout or /vsistdout/ is supported since GDAL 3.5.0 (note" +" that the file will then lack the optional region/bounding box header " +"item)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:4 +msgid "GPKG -- GeoPackage vector" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:10 +msgid "" +"This driver implements support for access to spatial tables in the `OGC " +"GeoPackage format standard " +"<http://www.opengeospatial.org/standards/geopackage>`__ The GeoPackage " +"standard uses a SQLite database file as a generic container, and the " +"standard defines:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:16 +msgid "" +"Expected metadata tables (``gpkg_contents``, ``gpkg_spatial_ref_sys``, " +"``gpkg_geometry_columns``)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:18 +msgid "" +"Binary format encoding for geometries in spatial tables (basically a GPKG" +" standard header object followed by ISO standard well-known binary (WKB))" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:21 +msgid "" +"Naming and conventions for extensions (extended feature types) and " +"indexes (how to use SQLite r-tree in an interoperable manner)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:28 +msgid "" +"The driver also supports reading and writing the following non-linear " +"geometry types: CIRCULARSTRING, COMPOUNDCURVE, CURVEPOLYGON, MULTICURVE " +"and MULTISURFACE" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:32 +msgid "" +"GeoPackage raster/tiles are supported. See the :ref:`GeoPackage raster " +"<raster.gpkg>` documentation page." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:45 +#: ../../source/drivers/vector/xodr.rst:22 +msgid "Specification version" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:47 +msgid "" +"Starting with GDAL 2.2, the driver is able to create GeoPackage databases" +" following the 1.0/1.0.1, 1.1 or 1.2 versions. For GDAL 2.2, it will " +"automatically adjust to the minimum version required for the features of " +"GeoPackage used. For GDAL 2.3 or later, it will default to 1.2. Explicit " +"version choice can be done by specifying the VERSION dataset creation " +"option." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:57 +msgid "GeoPackage only supports one geometry column per table." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:62 +msgid "" +"The driver supports OGR attribute filters, and users are expected to " +"provide filters in the SQLite dialect, as they will be executed directly " +"against the database." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:66 +msgid "" +"SQL SELECT statements passed to ExecuteSQL() are also executed directly " +"against the database. If Spatialite is used, a recent version (4.2.0) is " +"needed and use of explicit cast operators AsGPB() is required to " +"transform GeoPackage geometries to Spatialite geometries (the reverse " +"conversion from Spatialite geometries is automatically done by the GPKG " +"driver). It is also possible to use with any Spatialite version, but in a" +" slower way, by specifying the \"INDIRECT_SQLITE\" dialect. In which " +"case, GeoPackage geometries automatically appear as Spatialite geometries" +" after translation by OGR." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:76 +msgid "" +"Starting with GDAL 2.2, the \"DROP TABLE layer_name\" and \"ALTER TABLE " +"layer_name RENAME TO new_layer\" statements can be used. They will update" +" GeoPackage system tables." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:80 +msgid "" +"Starting with GDAL 2.2, the " +"\"HasSpatialIndex('table_name','geom_col_name')\" statement can be used " +"for checking if the table has spatial index on the named geometry column." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:85 +msgid "" +"When dropping a table, or removing records from tables, the space they " +"occupied is not immediately released and kept in the pool of file pages " +"that SQLite may reuse later. If you need to shrink the file to its " +"minimum size, you need to issue an explicit \"VACUUM\" SQL request. Note " +"that this will result in a full rewrite of the file." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:92 +msgid "SQL functions" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:94 +msgid "" +"The following SQL functions, from the GeoPackage specification, are " +"available:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:96 +msgid "ST_MinX(geom *Geometry*): returns the minimum X coordinate of the geometry" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:98 +msgid "ST_MinY(geom *Geometry*): returns the minimum Y coordinate of the geometry" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:100 +msgid "ST_MaxX(geom *Geometry*): returns the maximum X coordinate of the geometry" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:102 +msgid "ST_MaxY(geom *Geometry*): returns the maximum Y coordinate of the geometry" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:104 +msgid "" +"ST_IsEmpty(geom *Geometry*): returns 1 if the geometry is empty (but not " +"null), e.g. a POINT EMPTY geometry" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:106 +msgid "" +"ST_GeometryType(geom *Geometry*): returns the geometry type: 'POINT', " +"'LINESTRING', 'POLYGON', 'MULTIPOLYGON', 'MULTILINESTRING', 'MULTIPOINT'," +" 'GEOMETRYCOLLECTION'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:109 +msgid "ST_SRID(geom *Geometry*): returns the SRID of the geometry" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:110 +msgid "" +"GPKG_IsAssignable(expected_geom_type *String*, actual_geom_type *String*)" +" : mainly, needed for the 'Geometry Type Triggers Extension'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:113 +msgid "" +"The following functions, with identical syntax and semantics as in " +"Spatialite, are also available :" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:116 +msgid "" +"CreateSpatialIndex(table_name *String*, geom_column_name *String*): " +"creates a spatial index (RTree) on the specified table/geometry column" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:119 +msgid "" +"DisableSpatialIndex(table_name *String*, geom_column_name *String*): " +"drops an existing spatial index (RTree) on the specified table/geometry " +"column" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:122 +msgid "" +"ST_Area(geom *Geometry*): compute the area in square units of the " +"geometry SRS." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:123 +msgid "" +"ST_Area(geom *Geometry*, use_ellipsoid *boolean*): (GDAL >= 3.9): compute" +" the area in square meters, considering the geometry on the ellipsoid " +"(use_ellipsoid must be set to true/1)." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:126 +msgid "" +"SetSRID(geom *Geometry*, srs_id *Integer*): overrides the geometry' SRS " +"ID, without reprojection." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:128 +msgid "" +"ST_Transform(geom *Geometry*, target_srs_id *Integer*): reproject the " +"geometry to the SRS of specified srs_id. If no SRS with that given srs_id" +" is not found in gpkg_spatial_ref_sys, starting with GDAL 3.2, it will be" +" interpreted as a EPSG code." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:132 +msgid "" +"ST_EnvIntersects(geom *Geometry*, minx *Double*, miny *Double*, maxx " +"*Double*, maxy *Double*): (GDAL >= 3.7) Returns 1 if the minimum bounding" +" box of geom intersects the bounding box defined by " +"(minx,miny)-(maxx,maxy), or 0 otherwise." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:135 +msgid "" +"ST_EnvIntersects(geom1 *Geometry*, geom2 *Geometry*): (GDAL >= 3.7) " +"Returns 1 if the minimum bounding box of geom1 intersects the one of " +"geom2, or 0 otherwise. (Note: this function, as all others, does not " +"automatically uses spatial indices)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:140 +msgid "" +"The raster SQL functions mentioned at :ref:`raster.gpkg.raster` are also " +"available." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:144 +msgid "Link with Spatialite" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:146 +msgid "" +"If it has been compiled against Spatialite 4.2 or later, it is also " +"possible to use Spatialite SQL functions. Explicit transformation from " +"GPKG geometry binary encoding to Spatialite geometry binary encoding must" +" be done." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:155 +msgid "Starting with Spatialite 4.3, CastAutomagic is no longer needed." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:157 +msgid "" +"Note that due to the loose typing mechanism of SQLite, if a geometry " +"expression returns a NULL value for the first row, this will generally " +"cause OGR not to recognize the column as a geometry column. It might be " +"then useful to sort the results by making sure that non-null geometries " +"are returned first:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:170 +#: ../../source/drivers/vector/sqlite.rst:228 +msgid "" +"The driver implements transactions at the database level, per " +":ref:`rfc-54`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:177 +msgid "" +"Many-to-many relationship retrieval is supported, respecting the OGC " +"GeoPackage Related Tables Extension. One-to-many relationships will also " +"be reported for tables which utilize FOREIGN KEY constraints." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:180 +msgid "" +"Relationship creation, deletion and updating is supported since GDAL 3.7." +" Relationships can only be updated to change their base or related table " +"fields, or the relationship related table type. It is not permissible to " +"change the base or related table itself, or the mapping table details. If" +" this is desired then a new relationship should be created instead." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:185 +msgid "" +"Note that when a many-to-many relationship is created in a GeoPackage, " +"GDAL will always insert the mapping table into the gpkg_contents table. " +"Formally this is not required by the Related Tables Extension (instead, " +"the table should only be listed in gpkgext_relations), however failing to" +" list the mapping table in gpkg_contents prevents it from being usable in" +" some other applications (e.g. ESRI software)." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:192 +#: ../../source/drivers/vector/odbc.rst:62 +#: ../../source/drivers/vector/openfilegdb.rst:103 +#: ../../source/drivers/vector/pg.rst:154 +#: ../../source/drivers/vector/pgeo.rst:70 +#: ../../source/drivers/vector/sqlite.rst:241 +msgid "Dataset open options" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:222 +msgid "" +"The attached database must be a GeoPackage one too, so that its geometry " +"blobs are properly recognized (so typically not a Spatialite one)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:248 +msgid "" +"Note: open options are typically specified with \"-oo name=value\" syntax" +" in most OGR utilities, or with the ``GDALOpenEx()`` API call." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:251 +msgid "" +"Note: configuration option :config:`OGR_SQLITE_JOURNAL` can be used to " +"set the journal mode of the GeoPackage (and thus SQLite) file, see also " +"https://www.sqlite.org/pragma.html#pragma_journal_mode." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:258 +msgid "" +"When creating a new GeoPackage file, the driver will attempt to force the" +" database into a UTF-8 mode for text handling, satisfying the OGR strict " +"UTF-8 capability. For pre-existing files, the driver will work with " +"whatever it is given." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:274 +msgid "" +"|about-dataset-creation-options| The following creation options (specific" +" to vector, or common with raster) are available:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:339 +msgid "" +"Other options are available for raster. See the :ref:`GeoPackage raster " +"<raster.gpkg>` documentation page." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:490 +msgid ":copy-config:`OGR_SQLITE_JOURNAL`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:492 +msgid ":copy-config:`OGR_SQLITE_CACHE`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:494 +msgid ":copy-config:`OGR_SQLITE_SYNCHRONOUS`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:496 +msgid ":copy-config:`OGR_SQLITE_LOAD_EXTENSIONS`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:498 +msgid ":copy-config:`OGR_SQLITE_PRAGMA`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:510 +msgid ":copy-config:`SQLITE_USE_OGR_VFS`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:527 +msgid "" +"GDAL uses the standardized `gpkg_metadata " +"<http://www.geopackage.org/spec/#_metadata_table>`__ and " +"`gpkg_metadata_reference " +"<http://www.geopackage.org/spec/#_metadata_reference_table>`__ tables to " +"read and write metadata, on the dataset and layer objects." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:533 +msgid "" +"GDAL metadata, from the default metadata domain and possibly other " +"metadata domains, is serialized in a single XML document, conformant with" +" the format used in GDAL PAM (Persistent Auxiliary Metadata) .aux.xml " +"files, and registered with md_scope=dataset and " +"md_standard_uri=http://gdal.org in gpkg_metadata. For the dataset, this " +"entry is referenced in gpkg_metadata_reference with a " +"reference_scope=geopackage. For a layer, this entry is referenced in " +"gpkg_metadata_reference with a reference_scope=table and table_name={name" +" of the table}" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:554 +msgid "Non-spatial tables" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:556 +msgid "" +"The core GeoPackage specification of GeoPackage 1.0 and 1.1 did not " +"support non-spatial tables. This was added in GeoPackage 1.2 as the " +"\"attributes\" data type." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:560 +msgid "" +"The driver allows creating and reading non-spatial tables with the " +":ref:`vector.geopackage_aspatial`." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:562 +msgid "" +"Starting with GDAL 2.2, the driver will also, by default, list non " +"spatial tables that are not registered through the gdal_aspatial " +"extension, and support the GeoPackage 1.2 \"attributes\" data type as " +"well. Starting with GDAL 2.2, non spatial tables are by default created " +"following the GeoPackage 1.2 \"attributes\" data type (can be controlled " +"with the :lco:`ASPATIAL_VARIANT` layer creation option)." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:570 +msgid "Spatial views" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:572 +msgid "" +"Views can be created and recognized as valid spatial layers if a " +"corresponding record is inserted into the gpkg_contents and " +"gpkg_geometry_columns table." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:576 +msgid "" +"Starting with GDAL 2.2, in the case of the columns in the SELECT clause " +"of the view acts a integer primary key, then it can be recognized by OGR " +"as the FID column of the view, provided it is renamed as OGC_FID. " +"Selecting a feature id from a source table without renaming will not be " +"sufficient, since due to joins this feature id could appear several " +"times. Thus the user must explicitly acknowledge that the column is " +"really a primary key." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:592 +msgid "" +"This requires GDAL to be compiled with the SQLITE_HAS_COLUMN_METADATA " +"option and SQLite3 with the SQLITE_ENABLE_COLUMN_METADATA option. " +"Starting with GDAL 2.3, this can be easily verified if the " +"SQLITE_HAS_COLUMN_METADATA=YES driver metadata item is declared (for " +"example with \"ogrinfo --format GPKG\")." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:598 +msgid "" +"Starting with GDAL 3.7.1, it is possible to define a geometry column as " +"the result of a Spatialite spatial function. Note however that this is an" +" extension likely to be non-interoperable with other software that does " +"not activate Spatialite for the SQLite3 database connection. Such " +"geometry column should be registered into the ``gpkg_extensions`` using " +"the ``gdal_spatialite_computed_geom_column`` extension name (cf " +":ref:`vector.gpkg_spatialite_computed_geom_column`), like below:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:618 +msgid "Coordinate Reference Systems" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:620 +msgid "" +"Valid geographic, projected and compound CRS supported in general by GDAL" +" are also supported by GeoPackage and stored in the " +"``gpkg_spatial_ref_sys`` table." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:623 +msgid "Two special hard-coded CRS are reserved per the GeoPackage specification:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:625 +msgid "" +"srs_id=0, for a Undefined Geographic CRS. For GDAL 3.8 or earlier, this " +"one is selected by default if creating a spatial layer without any " +"explicit CRS" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:628 +msgid "" +"srs_id=-1, for a Undefined Projected CRS. It might be selected by " +"creating a layer with a CRS instantiated from the following WKT string: " +"``LOCAL_CS[\"Undefined Cartesian SRS\"]``. (GDAL >= 3.3)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:632 +msgid "" +"Starting with GDAL 3.9, a layer without any explicit CRS is mapped " +"from/to a custom entry of srs_id=99999 with the following properties:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:635 +msgid "``srs_name``: ``Undefined SRS``" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:636 +msgid "``organization``: ``GDAL``" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:637 +msgid "``organization_coordsys_id``: 99999" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:638 +msgid "" +"``definition``: ``LOCAL_CS[\"Undefined " +"SRS\",LOCAL_DATUM[\"unknown\",32767],UNIT[\"unknown\",0],AXIS[\"Easting\",EAST],AXIS[\"Northing\",NORTH]]``" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:639 +msgid "" +"``definition_12_063`` (when the CRS WKT extension is used): " +"``ENGCRS[\"Undefined " +"SRS\",EDATUM[\"unknown\"],CS[Cartesian,2],AXIS[\"easting\",east,ORDER[1],LENGTHUNIT[\"unknown\",0]],AXIS[\"northing\",north,ORDER[2],LENGTHUNIT[\"unknown\",0]]]``" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:640 +msgid "``description``: ``Custom undefined coordinate reference system``" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:642 +msgid "" +"Note that the use of a LOCAL_CS / EngineeringCRS is mostly to provide a " +"valid CRS definition to comply with the requirements of the GeoPackage " +"specification and to be compatible of other applications (or GDAL 3.8 or " +"earlier), but the semantics of that entry is intended to be \"undefined " +"SRS of any kind\"." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:650 +msgid "(Restricted to those that have a vector scope)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:658 +msgid "" +"`Non-Linear Geometry Types " +"<http://www.geopackage.org/guidance/extensions/nonlinear_geometry_types.html>`__" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:660 +msgid "Yes, since GDAL 2.1" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:661 +msgid "" +"`RTree Spatial Indexes " +"<http://www.geopackage.org/guidance/extensions/rtree_spatial_indexes.html>`__" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:667 +msgid "`Schema <http://www.geopackage.org/guidance/extensions/schema.html>`__" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:669 +msgid "Yes, since GDAL 3.3 (Geopackage constraints exposed as field domains)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:672 +msgid "" +"Partially, since GDAL 2.2. GDAL can read databases using this extension, " +"but cannot interpret a SRS entry that has only a WKT v2 entry." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:673 +msgid ":ref:`vector.geopackage_aspatial`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:675 +msgid "Yes. Deprecated in GDAL 2.2 for the *attributes* official data_type" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:676 +msgid ":ref:`vector.gpkg_spatialite_computed_geom_column`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:678 +msgid "Yes, starting with GDAL 3.7.1" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:679 +msgid "" +"`OGC GeoPackage Related Tables Extension <http://www.geopackage.org/spec" +"/related-tables/>`__" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:681 +msgid "Yes, starting with GDAL 3.6" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:684 +#: ../../source/drivers/vector/shapefile.rst:269 +msgid "Compressed files" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:686 +msgid "" +"Starting with GDAL 3.7, the driver can also support reading and creating " +".gpkg.zip files containing one .gpkg file." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:689 +msgid "" +"On large files, good read performance can only be achieved if the file " +"inside the .zip is not compressed or compressed using the `SOZip " +"<https://sozip.org>`__ optimization." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:693 +msgid "Update of an existing file is not supported." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:695 +msgid "" +"Creation involves the creation of a temporary file. Sufficiently large " +"files will be automatically compressed using the SOZip optimization." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:705 +msgid "" +"The GeoPackage driver supports reading and writing the geometry " +"coordinate precision, using the :cpp:class:`OGRGeomCoordinatePrecision` " +"settings of the :cpp:class:`OGRGeomFieldDefn`. By default, the geometry " +"coordinate precision is only noted in metadata, and does not cause " +"geometries that are written to be modified to comply with this precision." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:711 +msgid "Several settings may be combined to apply further processing:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:713 +msgid "" +"if the :config:`OGR_APPLY_GEOM_SET_PRECISION` configuration option is set" +" to ``YES``, the :cpp:func:`OGRGeometry::SetPrecision` method will be " +"applied when calling the CreateFeature() and SetFeature() method of the " +"driver, to round X and Y coordinates to the specified precision, and fix " +"potential geometry invalidities resulting from the rounding." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:719 +msgid "" +"if the ``DISCARD_COORD_LSB`` layer creation option is set to YES, the " +"less-significant bits of the WKB geometry encoding which are not relevant" +" for the requested precision are set to zero. This can improve further " +"lossless compression stages, for example when putting a GeoPackage in an " +"archive. Note however that when reading back such geometries and " +"displaying them to the maximum precision, they will not \"exactly\" match" +" the original :cpp:class:`OGRGeomCoordinatePrecision` settings. However, " +"they will round back to it. The value of the ``DISCARD_COORD_LSB`` layer " +"creation option is written in the dataset metadata, and will be re-used " +"for later edition sessions." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:730 +msgid "" +"if the ``UNDO_DISCARD_COORD_LSB_ON_READING`` layer creation option is set" +" to YES (only makes sense if the ``DISCARD_COORD_LSB`` layer creation " +"option is also set to YES), when *reading* back geometries from a " +"dataset, the :cpp:func:`OGRGeometry::roundCoordinates` method will be " +"applied so that the geometry coordinates exactly match the original " +"specified coordinate precision. That option will only be honored by GDAL " +"3.9 or later." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:738 +msgid "" +"Implementation details: the coordinate precision is stored in a record in" +" each of the ``gpkg_metadata`` and ``gpkg_metadata_reference`` table, " +"with the following additional constraints on top of the ones imposed by " +"the GeoPackage specification:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:743 +msgid "gpkg_metadata.md_standard_uri = 'http://gdal.org'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:744 +msgid "gpkg_metadata.mime_type = 'text/xml'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:745 +msgid "" +"gpkg_metadata.metadata = '<CoordinatePrecision " +"xy_resolution=\"{xy_resolution}\" z_resolution=\"{z_resolution}\" " +"m_resolution=\"{m_resolution}\" discard_coord_lsb={true or false} " +"undo_discard_coord_lsb_on_reading={true or false} />'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:746 +msgid "gpkg_metadata_reference.reference_scope = 'column'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:747 +msgid "gpkg_metadata_reference.table_name = '{table_name}'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:748 +msgid "gpkg_metadata_reference.column_name = '{geometry_column_name}'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:750 +msgid "" +"Note that the xy_resolution, z_resolution or m_resolution attributes of " +"the XML CoordinatePrecision element are optional. Their numeric value is " +"expressed in the units of the SRS for xy_resolution and z_resolution." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:759 +msgid "" +"The same performance hints apply as those mentioned for the :ref:`SQLite " +"driver <target_drivers_vector_sqlite_performance_hints>`." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:765 +msgid "" +"Simple translation of a single shapefile into GeoPackage. The table 'abc'" +" will be created with the features from abc.shp and attributes from " +"abc.dbf. The file ``filename.gpkg`` must **not** already exist, as it " +"will be created. For adding new layers into existing geopackage run " +"ogr2ogr with **-update**." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:775 +msgid "" +"Update of an existing GeoPackage file – e.g. a GeoPackage template – by " +"adding features to it from another GeoPackage file containing features " +"according to the same or a backwards compatible database schema." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:784 +msgid "" +"Translation of a directory of shapefiles into a GeoPackage. Each file " +"will end up as a new table within the GPKG file. The file " +"``filename.gpkg`` must **not** already exist, as it will be created." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:792 +msgid "" +"Translation of a PostGIS database into a GeoPackage. Each table in the " +"database will end up as a table in the GPKG file. The file " +"``filename.gpkg`` must **not** already exist, as it will be created." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:800 +msgid "Perform a join between 2 GeoPackage databases:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:811 +msgid ":ref:`GeoPackage raster <raster.gpkg>` documentation page" +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:4 +msgid "GeoPackage Spatialite computed geometry column extension" +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:6 +msgid "GeoPackage 1.3.1 Extension" +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:8 +msgid "" +"Extension follows template from Annex E of the OGC `GeoPackage 1.3.1 " +"Specification`_." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:13 +msgid "Spatialite computed geometry column" +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:18 +msgid "" +"Support for geometry column computed from the result of a SQL function of" +" the Spatialite library." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:29 +msgid "The extension name is ``gdal_spatialite_computed_geom_column``." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:31 +msgid "" +"Each view using the extension should register its geometry column with " +"the following template:" +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:50 +msgid "Extension of Existing Requirement in Clause 2.1 \"Features\"." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:55 +msgid "" +"This extension applies to any view specified in the ``gpkg_contents`` " +"table with a lowercase `data_type` column value of \"features\" which " +"defines its geometry column as the result of a SQL function of the " +"Spatialite library." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:71 +msgid "" +"A view using this extension should have its geometry column defined as " +"the result of a Spatialite SQL function returning a geometry, and wrapped" +" with the ``AsGPB`` function to return a GeoPackage geometry blob." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:75 +msgid "An example of such a view is:" +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:82 +msgid "" +"The view name and geometry column name should be registered in the " +"``gpkg_extensions`` table, as shown in the above Extension Template." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:93 +msgid "" +"This extension assumes that the `Spatialite SQL functions`_ are available" +" at runtime." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:10 +msgid "" +"The GPSBabel driver for now that relies on the `GPSBabel " +"<http://www.gpsbabel.org>`__ utility to access various GPS file formats." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:14 +msgid "The GPSBabel executable must be accessible through the PATH." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:24 +#: ../../source/drivers/vector/mapml.rst:34 +msgid "Read support" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:26 +msgid "" +"The driver needs the :ref:`GPX <vector.gpx>` driver to be fully " +"configured with read support (through Expat library) to be able to parse " +"the output of GPSBabel, as GPX is used as the intermediate pivot format." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:30 +msgid "" +"The returned layers can be waypoints, routes, route_points, tracks, " +"track_points depending on the input data." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:33 +msgid "" +"The syntax to specify an input datasource is : " +"*GPSBabel:gpsbabel_file_format[,gpsbabel_format_option]*:[features=[waypoints,][tracks,][routes]:]filename*" +" where :" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:37 +#: ../../source/drivers/vector/gpsbabel.rst:89 +msgid "" +"*gpsbabel_file_format* is one of the `file formats " +"<http://www.gpsbabel.org/capabilities.shtml>`__ handled by GPSBabel." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:40 +#: ../../source/drivers/vector/gpsbabel.rst:92 +msgid "" +"*gpsbabel_format_option* is any option handled by the specified GPSBabel " +"format (refer to the documentation of each GPSBabel format)" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:42 +msgid "" +"*features=* can be used to modify the type of features that GPSBabel will" +" import. waypoints matches the -w option of gpsbabel commandline, tracks " +"matches -t and routes matches -r. This option can be used to require full" +" data import from GPS receivers that are slow and for which GPSBabel " +"would only fetch waypoints by default. See the documentation on `Route " +"and Track modes " +"<http://www.gpsbabel.org/htmldoc-1.3.6/Route_And_Track_Modes.html>`__ for" +" more details." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:50 +msgid "" +"*filename* can be an actual on-disk file, a file handled through the GDAL" +" virtual file API, or a special device handled by GPSBabel such as " +"\"usb:\", \"/dev/ttyS0\", \"COM1:\", etc.. What is actually supported " +"depends on the used GPSBabel format." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:55 +msgid "" +"Alternatively, for a few selected GPSBabel formats, just specifying the " +"filename might be sufficient. The list includes for now :" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:58 +msgid "garmin_txt" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:59 +msgid "gtrnctr" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:60 +msgid "gdb" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:61 +msgid "magellan" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:62 +msgid "mapsend" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:63 +msgid "mapsource" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:64 +msgid "nmea" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:65 +msgid "osm" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:66 +msgid "ozi" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:67 +msgid "igc" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:69 +msgid "" +"The :config:`USE_TEMPFILE=YES` configuration option can be used to create" +" an on-disk temporary GPX file instead of a in-memory one, when reading " +"big amount of data." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:76 +msgid "" +"The driver relies on the GPX driver to create an intermediate file that " +"will be finally translated by GPSBabel to the desired GPSBabel format. " +"(The GPX driver does not need to be configured for read support for " +"GPSBabel write support.)." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:81 +msgid "" +"The support geometries, options and other creation issues are the ones of" +" the GPX driver. Please refer to its :ref:`documentation <vector.gpx>` " +"for more details." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:85 +msgid "" +"The syntax to specify an output datasource is : " +"*GPSBabel:gpsbabel_file_format[,gpsbabel_format_option]*:filename* where " +":" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:95 +msgid "" +"Alternatively, you can just pass a filename as output datasource name and" +" specify the dataset creation option " +"GPSBABEL_DRIVER=gpsbabel_file_format[,gpsbabel_format_option]\\*" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:99 +msgid "" +"When writing large datasets, the :config:`USE_TEMPFILE` configuration " +"option may be used:" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:113 +msgid "Reading the waypoints from a Garmin USB receiver :" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:119 +msgid "Converting a shapefile to Magellan Mapsend format :" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:128 +msgid "`GPSBabel Home Page <http://www.gpsbabel.org>`__" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:129 +msgid "`GPSBabel file formats <http://www.gpsbabel.org/capabilities.shtml>`__" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:131 +msgid ":ref:`GPX driver page <vector.gpx>`" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:4 +msgid "GPX - GPS Exchange Format" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:6 +msgid "GPX" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:10 +msgid "" +"GPX (the GPS Exchange Format) is a light-weight XML data format for the " +"interchange of GPS data (waypoints, routes, and tracks) between " +"applications and Web services on the Internet." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:14 +msgid "" +"OGR has support for GPX reading (if GDAL is build with *expat* library " +"support) and writing." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:17 +msgid "Version supported are GPX 1.0 and 1.1 for reading, GPX 1.1 for writing." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:19 +msgid "The OGR driver supports reading and writing of all the GPX feature types:" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:21 +msgid "*waypoints* : layer of features of OGR type wkbPoint" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:22 +msgid "*routes* : layer of features of OGR type wkbLineString" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:23 +msgid "*tracks* : layer of features of OGR type wkbMultiLineString" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:25 +msgid "" +"It also supports reading of route points and track points in standalone " +"layers (*route_points* and *track_points*), so that their own attributes " +"can be used by OGR." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:31 +msgid "" +"In addition to its GPX attributes, each route point of a route has a " +"*route_fid* (foreign key to the FID of its belonging route) and a " +"*route_point_id* which is its sequence number in the route." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:34 +msgid "" +"The same applies for track points with *track_fid*, *track_seg_id* and " +"*track_seg_point_id*. All coordinates are relative to the WGS84 datum " +"(EPSG:4326)." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:36 +msgid "" +"The OGR GPX driver reads and writes the GPX attributes for the waypoints," +" routes and tracks." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:39 +msgid "" +"Starting with GDAL 3.7, metadata from the top <metadata> element is " +"reported at dataset level." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:67 +#: ../../source/drivers/vector/gpx.rst:102 +msgid "\"track_seg_id\" to \"trksegid\"" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:68 +#: ../../source/drivers/vector/gpx.rst:103 +msgid "\"track_seg_point_id\" to \"trksegptid\"" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:69 +#: ../../source/drivers/vector/gpx.rst:104 +msgid "\"route_point_id\" to \"rteptid\"" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:71 +#: ../../source/drivers/vector/gpx.rst:106 +msgid "" +"But note that no particular processing will be done for any extension " +"field names." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:140 +msgid "" +"If your GPX file is not encoded in one of the previous encodings, it will" +" not be parsed by the GPX driver. You may convert it into one of the " +"supported encoding with the *iconv* utility for example and change " +"accordingly the *encoding* parameter value in the XML header." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:142 +msgid "When writing a GPX file, the driver expects UTF-8 content to be passed in." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:146 +msgid "Extensions element reading" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:148 +msgid "" +"If the *<extensions>* element is detected in a GPX file, OGR will expose " +"the content of its sub elements as fields. Complex content of sub " +"elements will be exposed as an XML blob." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:152 +msgid "The following sequence GPX content :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:188 +msgid "" +"Note : the GPX driver will output content of the extensions element only " +"if it is found in the first records of the GPX file. If extensions appear" +" later, you can force an explicit parsing of the whole file with the " +":config:`GPX_USE_EXTENSIONS` configuration option." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:194 +msgid "" +"On export all layers are written to a single GPX file. Update of existing" +" files is not currently supported." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:202 +msgid "Features of type wkbPoint/wkbPoint25D are written in the *wpt* element." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:204 +msgid "" +"Features of type wkbLineString/wkbLineString25D are written in the *rte* " +"element." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:206 +msgid "" +"Features of type wkbMultiLineString/wkbMultiLineString25D are written in " +"the *trk* element." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:208 +msgid "Other type of geometries are not supported." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:210 +msgid "" +"For route points and tracks points, if there is a Z coordinate, it is " +"used to fill the elevation element of the corresponding points." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:213 +msgid "" +"If a layer is named \"track_points\" with wkbPoint/wkbPoint25D " +"geometries, the tracks in the GPX file will be built from the sequence of" +" features in that layer. This is the way of setting GPX attributes for " +"each track point, in addition to the raw coordinates. Points belonging to" +" the same track are identified thanks to the same value of the " +"'track_fid' field (and it will be broken into track segments according to" +" the value of the 'track_seg_id' field). They must be written in sequence" +" so that track objects are properly reconstructed. The 'track_name' field" +" can be set on the first track point to fill the <name> element of the " +"track. Similarly, if a layer is named \"route_points\" with " +"wkbPoint/wkbPoint25D geometries, the routes in the GPX file will be built" +" from the sequence of points with the same value of the 'route_fid' " +"field. The 'route_name' field can be set on the first track point to fill" +" the <name> element of the route." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:296 +msgid "" +"Dataset creation options to fill the top <metadata> element have been " +"added in GDAL 3.7:" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:339 +msgid "" +"Waypoints, routes and tracks must be written into that order to be valid " +"against the XML Schema." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:342 +msgid "" +"When translating from a source dataset, it may be necessary to rename the" +" field names from the source dataset to the expected GPX attribute names," +" such as <name>, <desc>, etc... This can be done with a :ref:`OGR VRT " +"<vector.vrt>` dataset, or by using the \"-sql\" option of the ogr2ogr " +"utility." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:349 +msgid "Issues when translating to Shapefile" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:351 +msgid "" +"When translating the *track_points* layer to a Shapefile, the field names" +" \"track_seg_id\" and \"track_seg_point_id\" are truncated to 10 " +"characters in the .DBF file, thus leading to duplicate names." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:355 +msgid "" +"To avoid this, you can define the :config:`GPX_SHORT_NAMES` configuration" +" option to TRUE." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:358 +msgid "To translate the track_points layer of a GPX file to a set of shapefiles :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:365 +msgid "" +"Shapefile does not support fields of type DateTime. It only supports " +"fields of type Date. So by default, you will lose the hour:minute:second " +"part of the *Time* elements of a GPX file." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:369 +msgid "" +"You can use the OGR SQL CAST operator to convert the *time* field to a " +"string :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:376 +msgid "" +"There is a more convenient way to select all fields and ask for the " +"conversion of the ones of a given type to strings:" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:397 +msgid "The ogrinfo utility can be used to dump the content of a GPX datafile :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:403 +msgid "The ogr2ogr utility can be used to do GPX to GPX translation :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:412 +msgid "" +"Note : in the case of GPX to GPX translation, you need to specify the " +"layer names, in order to discard the route_points and track_points " +"layers." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:416 +msgid "Use of the *<extensions>* tag for output :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:422 +msgid "which will give an output like the following one :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:446 +msgid "" +"Use of -sql option to remap field names to the ones allowed by the GPX " +"schema:" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:454 +msgid "FAQ" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:456 +msgid "" +"How to solve \"ERROR 6: Cannot create GPX layer XXXXXX with unknown " +"geometry type\" ?" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:459 +msgid "" +"This error happens when the layer to create does not expose a precise " +"geometry type, but just a generic wkbUnknown type. This is for example " +"the case when using ogr2ogr with a SQL request to a PostgreSQL " +"datasource. You must then explicitly specify -nlt POINT (or LINESTRING or" +" MULTILINESTRING)." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:468 +msgid "`Home page for GPX format <http://www.topografix.com/gpx.asp>`__" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:469 +msgid "`GPX 1.1 format documentation <http://www.topografix.com/GPX/1/1/>`__" +msgstr "" + +#: ../../source/drivers/vector/grass.rst:10 +msgid "" +"The GDAL-GRASS driver can read GRASS GIS vector maps. The driver is " +"maintained at the `GDAL-GRASS GIS driver repository " +"<https://github.com/OSGeo/gdal-grass/>`__." +msgstr "" + +#: ../../source/drivers/vector/grass.rst:13 +msgid "" +"For the driver documentation, please visit the `GDAL-GRASS GIS vector " +"driver page <https://github.com/OSGeo/gdal-" +"grass/blob/main/docs/grass_vector.md>`__." +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:4 +msgid "GTFS - General Transit Feed Specification" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:8 +msgid "GTFS" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:12 +msgid "" +"This driver can read a .zip archive containing text files following the " +"GTFS specification." +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:15 +msgid "The driver presents layers with their original structure, and:" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:17 +msgid "enhances the ``stops`` layer with Point geometries" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:18 +msgid "" +"enhances the ``trips`` layer with LineString geometries reconstructed by " +"joining the ``trips`` layer with ``stops`` and ``stop_times`` layers" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:20 +msgid "" +"expose a ``shapes_geom`` layer, if the optional ``shapes`` is present by " +"constructing LineString geometries." +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:26 +msgid "The connection name can be:" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:28 +msgid "a .zip filename containing GTFS .txt files" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:29 +msgid "" +"a directory name prefixed with ``GTFS:`` (potentially a " +"``/vsizip/path/to/the.zip`` filename prefixed with ``GTFS:``)" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:32 +msgid "" +"Alternatively, starting with GDAL 3.10, specifying the ``-if GTFS`` " +"option to command line utilities accepting it, or ``GTFS`` as the only " +"value of the ``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also " +"forces the driver to recognize the passed filename." +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:46 +msgid "`GTFS Wikipedia page <https://en.wikipedia.org/wiki/GTFS>`__" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:6 +msgid "HANA" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:10 +msgid "" +"This driver implements read and write access for spatial data stored in " +"an `SAP HANA <https://www.sap.com/products/hana.html>`__ database." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:25 +msgid "" +"To connect to an SAP HANA database, use a connection string specifying " +"the database name, with additional parameters as necessary. The HANA: " +"prefix is used to mark the name as a HANA connection string." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:31 +#: ../../source/drivers/vector/pg.rst:49 +msgid "" +"In this syntax each parameter setting is in the form keyword = value. " +"Spaces around the equal sign are optional. To write an empty value, or a " +"value containing spaces, surround it with single quotes, e.g., keyword = " +"'a value'. Single quotes and backslashes within the value must be escaped" +" with a backslash, i.e., \\' and \\\\." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:39 +#: ../../source/drivers/vector/mssqlspatial.rst:83 +#: ../../source/drivers/vector/pg.rst:93 +msgid "SQL statements" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:41 +msgid "" +"The HANA driver passes SQL statements directly to HANA by default, rather" +" than evaluating them internally when using the ExecuteSQL() call on the " +"OGRDataSource, or the -sql command option to ogr2ogr. Attribute query " +"expressions are also passed directly through to HANA. It's also possible " +"to request the OGR HANA driver to handle SQL commands with the :ref:`OGR " +"SQL <ogr_sql_dialect>` engine, by passing **\"OGRSQL\"** string to the " +"ExecuteSQL() method, as the name of the SQL dialect." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:50 +msgid "" +"The HANA driver in OGR supports the OGRDataSource::StartTransaction(), " +"OGRDataSource::CommitTransaction() and " +"OGRDataSource::RollbackTransaction() calls in the normal SQL sense." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:57 +msgid "" +"The HANA driver does not support creation of new schemas, but it does " +"allow creation of new layers (tables) within an existing schema." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:61 +msgid "Dataset Open options" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:257 +msgid "Multitenant Database Containers" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:259 +msgid "" +"In order to connect to a tenant database, you need to specify a port " +"number assigned exactly to a desired instance. This port number can be " +"determined by executing the following query from the tenant database." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:267 +msgid "" +"For more details, see **Section 2.9 Connections for Multitenant Database " +"Containers** in `SAP HANA Multitenant Database Containers " +"<https://help.sap.com/doc/0987e3b51fb74e5a8631385fe4599c97/2.0.00/en-" +"us/sap_hana_multitenant_database_containers_en.pdf>`__." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:274 +msgid "" +"This example shows how to list HANA layers on a specified host using " +":ref:`ogrinfo` command." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:293 +msgid "" +"This example shows how to print summary information about a given layer, " +"i.e. 'planet_osm_line', using :ref:`ogrinfo`." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:332 +msgid "" +"This example shows how to export data from the 'points' table to a " +"shapefile called 'points_output.shp'." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:338 +msgid "" +"This example shows how to create and populate a table with data taken " +"from a shapefile." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:346 +msgid "For developers" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:348 +msgid "" +"To compile the SAP HANA driver, `odbc-cpp-wrapper <https://github.com/SAP" +"/odbc-cpp-wrapper/>`__ library needs to be linked or installed. For more " +"details, see comments in nmake.opt or configure.ac files to build the " +"driver for Windows or Linux/MacOS correspondingly." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:354 +msgid "`SAP HANA Home Page <https://www.sap.com/products/hana.html>`__" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:355 +msgid "" +"`SAP HANA Spatial Reference " +"<https://help.sap.com/viewer/cbbbfc20871e4559abfd45a78ad58c02/2.0.03/en-" +"US/e1c934157bd14021a3b43b5822b2cbe9.html>`__" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:356 +msgid "" +"`SAP HANA ODBC Connection Properties " +"<https://help.sap.com/viewer/0eec0d68141541d1b07893a39944924e/2.0.02/en-" +"US/7cab593774474f2f8db335710b2f5c50.html>`__" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:10 +msgid "" +"This driver implements support for access to spatial tables in IBM " +"Informix extended with the DataBlade spatial module." +msgstr "" + +#: ../../source/drivers/vector/idb.rst:13 +msgid "When opening a database, its name should be specified in the form" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:19 +msgid "The IDB: prefix is used to mark the name as a IDB connection string." +msgstr "" + +#: ../../source/drivers/vector/idb.rst:21 +msgid "" +"If the *geometry_columns* table exists, then all listed tables and named " +"views will be treated as OGR layers. Otherwise all regular user tables " +"will be treated as layers." +msgstr "" + +#: ../../source/drivers/vector/idb.rst:25 +msgid "" +"Regular (non-spatial) tables can be accessed, and will return features " +"with attributes, but not geometry. If the table has a \"st_*\" field, it " +"will be treated as a spatial table. The type of the field is inspected to" +" determine how to read it." +msgstr "" + +#: ../../source/drivers/vector/idb.rst:30 +msgid "Driver supports automatic FID detection." +msgstr "" + +#: ../../source/drivers/vector/idb.rst:42 +#: ../../source/drivers/vector/pgdump.rst:248 +msgid "Environment variables" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:44 +msgid "``INFORMIXDIR`` It should be set to Informix client SDK install dir" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:46 +msgid "``INFORMIXSERVER``: Default Informix server name" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:48 +msgid "``DB_LOCALE``: Locale of Informix database" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:50 +msgid "``CLIENT_LOCALE``: Client locale" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:52 +msgid "" +"For more information about Informix variables read documentation of " +"Informix Client SDK" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:69 +msgid "" +"This example shows using ogrinfo to list Informix DataBlade layers on a " +"different host." +msgstr "" + +#: ../../source/drivers/vector/idrisi.rst:6 +msgid "IDRISI" +msgstr "" + +#: ../../source/drivers/vector/idrisi.rst:10 +msgid "" +"This driver reads Idrisi vector files with .vct extension. The driver " +"recognized point, lines and polygons geometries." +msgstr "" + +#: ../../source/drivers/vector/idrisi.rst:13 +msgid "" +"For geographical referencing identification, the .vdc file contains " +"information that points to a file that holds the geographic reference " +"details. Those files uses extension REF and resides in the same folder as" +" the RST image or more likely in the Idrisi installation folders." +msgstr "" + +#: ../../source/drivers/vector/idrisi.rst:24 +msgid "" +"Note that the driver recognizes the name convention used in Idrisi for " +"UTM and State Plane geographic reference so it doesn't need to access the" +" REF files. That is the case for RDC file that specify \"utm-30n\" or " +"\"spc87ma1\" in the \"ref. system\" field. Note that exporting to RST in " +"any other geographical reference system will generate a suggested REF " +"content in the comment section of the RDC file." +msgstr "" + +#: ../../source/drivers/vector/idrisi.rst:31 +msgid "The driver can retrieve attributes from .ADC / .AVL ASCII files." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:6 +msgid "INTERLIS 1" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:8 +msgid "INTERLIS 2" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:12 +msgid "OGR has support for INTERLIS reading and writing." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:17 +msgid "" +"`INTERLIS <http://www.interlis.ch/>`__ is a standard which has been " +"especially composed in order to fulfill the requirements of modeling and " +"the integration of geodata into contemporary and future geographic " +"information systems. With the usage of unified, documented geodata and " +"the flexible exchange possibilities the following advantage may occur:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:19 +msgid "the standardized documentation" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:20 +msgid "the compatible data exchange" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:21 +msgid "the comprehensive integration of geodata e.g. from different data owners." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:23 +msgid "the quality proofing" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:24 +msgid "the long term data storage" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:25 +msgid "the contract-proof security and the availability of the software" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:27 +msgid "" +"OGR supports INTERLIS 1 and INTERLIS 2 (2.2 and 2.3) with the following " +"limitations:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:30 +msgid "Curves in Interlis 1 area polygons are converted to line segments" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:31 +msgid "" +"Interlis 1 Surface geometries with non-numeric IDENT field are not " +"included in the attribute layer" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:33 +msgid "Embedded INTERLIS 2 structures and line attributes are not supported" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:34 +msgid "Incremental transfer is not supported" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:35 +msgid "Transfer id (TID) is used as feature id" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:47 +msgid "Model support" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:49 +msgid "" +"Data is read and written into transfer files which have different formats" +" in INTERLIS 1 (.itf) and INTERLIS 2 (.xtf). Models are passed in " +"IlisMeta format by using \"a_filename.xtf,models.imd\" as a connection " +"string." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:54 +msgid "" +"IlisMeta files can be be generated with the ili2c compiler. Command line " +"example:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:61 +msgid "Some possible transformations using :ref:`ogr2ogr`." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:63 +msgid "Interlis 1 -> Shape:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:69 +msgid "Interlis 2 -> Shape:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:75 +msgid "or without model:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:81 +msgid "Example with curves and multiple geometries:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:87 +msgid "Shape -> Interlis 2:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:93 +msgid "Importing multiple Interlis 1 files into PostGIS:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:101 +msgid "Arc interpolation" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:104 +msgid "" +"Converting INTERLIS arc geometries to line segments can be forced by " +"setting the configuration variable :config:`OGR_STROKE_CURVE` to TRUE." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:108 +msgid "" +"The approximation of arcs as linestrings is done by splitting the arcs " +"into subarcs of no more than a threshold angle. This angle is the " +":config:`OGR_ARC_STEPSIZE`. This defaults to one degree, but may be " +"overridden by setting the configuration variable " +":config:`OGR_ARC_STEPSIZE`." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:113 +msgid "" +"`ogrtools <https://github.com/sourcepole/ogrtools>`__ library includes " +"extensions for the OGR Interlis driver" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:115 +msgid "" +"Development of the OGR INTERLIS driver was supported by `Swiss Federal " +"Administration <http://www.kogis.ch/>`__, `Canton Solothurn " +"<http://www.sogis.ch/>`__ and `Canton Thurgovia " +"<http://www.geoinformation.tg.ch/>`__." +msgstr "" + +#: ../../source/drivers/vector/index.rst:5 +msgid "Vector drivers" +msgstr "" + +#: ../../source/drivers/vector/index.rst:18 +msgid "" +"The following drivers have been retired and moved to the " +"https://github.com/OSGeo/gdal-extra-drivers repository: AeronavFAA, BNA, " +"HTF, OpenAir, SEGUKOOA, SEGY, SUA, XPlane" +msgstr "" + +#: ../../source/drivers/vector/jml.rst:6 +msgid "JML" +msgstr "" + +#: ../../source/drivers/vector/jml.rst:10 +msgid "" +"OGR has support for reading and writing .JML files used by the OpenJUMP " +"software. Read support is only available if GDAL is built with *expat* " +"library support" +msgstr "" + +#: ../../source/drivers/vector/jml.rst:14 +msgid "" +".jml is a variant of GML format. There is no formal definition of the " +"format. It supports a single layer per file, mixed geometry types, and " +"for each feature, a geometry and several attributes of type integer, " +"double, string, date or object. That object data type, used for example " +"to store 64 bit integers, but potentially arbitrary serialized Java " +"objects, is converted as string when reading. Contrary to GML, the " +"definition of fields is embedded in the .jml file, at its beginning." +msgstr "" + +#: ../../source/drivers/vector/jml.rst:22 +msgid "" +"Support for reading and writing spatial reference systems requires GDAL " +"2.3 or later." +msgstr "" + +#: ../../source/drivers/vector/jml.rst:45 +msgid "" +"The content returned by OGR will be encoded in UTF-8, after the " +"conversion from the encoding mentioned in the file header is. But files " +"produced by OpenJUMP are always UTF-8 encoded." +msgstr "" + +#: ../../source/drivers/vector/jml.rst:49 +msgid "When writing a JML file, the driver expects UTF-8 content to be passed in." +msgstr "" + +#: ../../source/drivers/vector/jml.rst:53 +msgid "Styling" +msgstr "" + +#: ../../source/drivers/vector/jml.rst:55 +msgid "" +"OpenJUMP uses an optional string attribute called \"R_G_B\" to determine " +"the color of objects. The field value is \"RRGGBB\" where RR, GG, BB are " +"respectively the value of the red, green and blue components expressed as" +" hexadecimal values from 00 to FF. When reading a .jml file, OGR will " +"translate the R_G_B attribute to the Feature Style encoding, unless a " +"OGR_STYLE attribute is present. When writing a .jml file, OGR will " +"extract from the Feature Style string the color of the PEN tool or the " +"forecolor of the BRUSH tool to write the R_G_B attribute, unless the " +"R_G_B attribute is defined in the provided feature. The addition of the " +"R_G_B attribute can be disabled by setting the CREATE_R_G_B_FIELD layer " +"creation option to NO." +msgstr "" + +#: ../../source/drivers/vector/jml.rst:70 +msgid "" +"|about-layer-creation-options| The JML writer supports the following " +"*layer* creation options:" +msgstr "" + +#: ../../source/drivers/vector/jml.rst:96 +msgid "" +"The author wishes to thank Jukka Rahkonen for funding the development of " +"this driver." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:4 +msgid "JSONFG -- OGC Features and Geometries JSON" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:8 +msgid "JSONFG" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:12 +msgid "" +"This driver implements read/write support for access to features encoded " +"in `OGC Features and Geometries JSON - Part 1: Core " +"<https://docs.ogc.org/DRAFTS/21-045.html>`__ format." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:15 +msgid "" +"JSON-FG is a set of extensions over the :ref:`GeoJSON<vector.geojson>` " +"format." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:17 +msgid "The following extensions are supported:" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:19 +msgid "" +"capturing the feature type in a ``featureType`` element to affect " +"features to separate" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:21 +msgid "" +"capturing a coordinate reference system (not necessarily WGS 84) in a " +"``coordRefSys`` element, that is the one used by geometries written in " +"the ``place`` element" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:24 +msgid "``time`` element at Feature level" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:25 +msgid "" +"minimum support for Polyhedron geometries (with a single outer shell) and" +" Prism with Point, LineString or Polygon base." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:30 +msgid "This driver implements a draft version of the standard." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:44 +msgid "The JSON-FG driver accepts three types of sources of data:" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:49 +msgid "Plain text file with JSON-FG data, typically with a .json extension" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:50 +msgid "Text passed directly and encoded in JSON-FG" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:52 +msgid "" +"The URL/filename/text might be prefixed with ``JSONFG:`` to avoid any " +"ambiguity with other drivers. Alternatively, starting with GDAL 3.10, " +"specifying the ``-if JSONFG`` option to command line utilities accepting " +"it, or ``JSONFG`` as the only value of the ``papszAllowedDrivers`` of " +":cpp:func:`GDALOpenEx`, also forces the driver to recognize the passed " +"URL/filename/text." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:60 +msgid "Time support" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:62 +msgid "On reading:" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:64 +msgid "" +"Feature.time.date elements are mapped to a OGR ``time`` field of type " +"Date. If there is a property also called ``time``, the OGR field for " +"Feature.time is called ``jsonfg_time``" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:68 +msgid "" +"Feature.time.timestamp elements are mapped to a OGR ``time`` field of " +"type DateTime" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:71 +msgid "" +"Feature.time.interval elements are mapped to a OGR ``time_start`` and " +"``time_end`` fields of type Date or DateTime. If there are properties " +"with those names, the OGR fields for Feature.time are prefixed with " +"``jsonfg_`` Unbounded intervals (``..``) are mapped to a unset OGR " +"feature field." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:76 +msgid "" +"On writing, if fields called ``time``, ``time_start``, ``time_end`` of " +"type Date or DateTime are created, their content is used to set the " +"Feature.time element with the reverse logic as the above explained " +"reading side. The field names may also be prefixed with ``jsonfg_`` to " +"distinguish them from fields ``time``, ``time_start``, ``time_end`` that " +"must be written in Feature.properties" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:207 +msgid "" +"The :lco:`COORDINATE_PRECISION_GEOMETRY` or " +":lco:`COORDINATE_PRECISION_PLACE` layer creation option has precedence " +"over the values set on the :cpp:class:`OGRGeomFieldDefn`." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:210 +msgid "" +"Implementation details: the coordinate precision is stored as " +"``xy_coordinate_resolution_place`` and ``z_coordinate_resolution_place`` " +"members at the FeatureCollection level, for the geometries written in the" +" ``place`` element. Their numeric value is expressed in the units of the " +"SRS." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:215 +msgid "" +"For the ``geometry`` standard GeoJSON element, the coordinate precision " +"is stored as ``xy_coordinate_resolution`` and ``z_coordinate_resolution``" +" members, and their numeric value is expressed in the units of the " +"OGC:CRS84 SRS (hence decimal degrees for ``xy_coordinate_resolution``)" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:236 +msgid "" +"`OGC Features and Geometries JSON - Part 1: Core " +"<https://docs.ogc.org/DRAFTS/21-045.html>`__" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:4 +msgid "KML - Keyhole Markup Language" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:6 +msgid "KML" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:10 +msgid "" +"Keyhole Markup Language (KML) is an XML-based language for managing the " +"display of 3D geospatial data. KML has been accepted as an OGC standard, " +"and is supported in one way or another on the major GeoBrowsers. Note " +"that KML by specification uses only a single projection, EPSG:4326. All " +"OGR KML output will be presented in EPSG:4326. As such OGR will create " +"layers in the correct coordinate system and transform any geometries." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:17 +msgid "" +"At this time, only vector layers are handled by the KML driver. *(there " +"are additional scripts supplied with the GDAL project that can build " +"other kinds of output)*" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:31 +msgid "KML Reading" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:33 +msgid "" +"KML reading is only available if GDAL/OGR is built with the Expat XML " +"Parser, otherwise only KML writing will be supported." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:36 +msgid "" +"Supported geometry types are ``Point``, ``Linestring``, ``Polygon``, " +"``MultiPoint``, ``MultiLineString``, ``MultiPolygon`` and " +"``MultiGeometry``. There are limitations, for example: the nested nature " +"of folders in a source KML file is lost; folder ``<description>`` tags " +"will not carry through to output. Folders containing multiple geometry " +"types, like POINT and POLYGON, are supported." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:44 +msgid "KML Writing" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:46 +msgid "" +"Since not all features of KML are able to be represented in the Simple " +"Features geometry model, you will not be able to generate many KML-" +"specific attributes from within GDAL/OGR. Please try a few test files to " +"get a sense of what is possible." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:51 +msgid "" +"When outputting KML, the OGR KML driver will translate each OGR Layer " +"into a KML Folder (you may encounter unexpected behavior if you try to " +"mix the geometry types of elements in a layer, e.g. ``LINESTRING`` and " +"``POINT`` data)." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:56 +msgid "" +"The KML Driver will rename some layers, or source KML folder names, into " +"new names it considers valid, for example '``Layer #0``', the default " +"name of the first unnamed Layer, becomes ``'Layer__0'``." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:60 +msgid "" +"KML is mix of formatting and feature data. The <description> tag of a " +"Placemark will be displayed in most geobrowsers as an HTML-filled " +"balloon. When writing KML, Layer element attributes are added as simple " +"schema fields. This best preserves feature type information." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:65 +msgid "" +"Limited support is available for fills, line color and other styling " +"attributes. Please try a few sample files to get a better sense of actual" +" behavior." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:86 +msgid "" +"If your KML file is not encoded in one of the previous encodings, it will" +" not be parsed by the KML driver. You may convert it into one of the " +"supported encoding with the *iconv* utility for example and change " +"accordingly the *encoding* parameter value in the XML header." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:88 +msgid "When writing a KML file, the driver expects UTF-8 content to be passed in." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:140 +msgid "" +"The ogr2ogr utility can be used to dump the results of a PostGIS query to" +" KML:" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:147 +msgid "How to dump contents of .kml file as OGR sees it:" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:154 +#: ../../source/drivers/vector/mysql.rst:44 +#: ../../source/drivers/vector/oci.rst:73 +msgid "Caveats" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:156 +msgid "" +"Google Earth seems to have some limits regarding the number of " +"coordinates in complex geometries like polygons. If the problem appears, " +"then problematic geometries are displayed completely or partially covered" +" by vertical stripes. Unfortunately, there are no exact number given in " +"the KML specification about this limitation, so the KML driver will not " +"warn about potential problems. One of possible and tested solutions is to" +" simplify a line or a polygon to remove some coordinates. Here is the " +"whole discussion about this issue on the `Google KML Developer Forum " +"<http://groups.google.com/group/kml-support>`__, in the `polygon displays" +" with vertical stripes <http://groups.google.com/group/kml-support-" +"getting-started/browse_thread/thread/e6995b8073e69c41>`__ thread." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:172 +msgid "`KML Specification <https://developers.google.com/kml/?csw=1>`__" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:173 +msgid "`KML Tutorial <https://developers.google.com/kml/documentation/kml_tut>`__" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:175 +msgid ":ref:`LIBKML driver <vector.libkml>` An alternative GDAL KML driver" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:6 +msgid "LIBKML" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:10 +msgid "" +"The LIBKML driver is a client of `Libkml " +"<https://github.com/libkml/libkml>`__ , a reference implementation of " +"`KML <http://www.opengeospatial.org/standards/kml/>`__ reading and " +"writing, in the form of a cross platform C++ library. You must build and " +"install Libkml in order to use this OGR driver. Note: you need to build " +"libkml 1.3 or master." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:17 +msgid "" +"Note that if you build and include this LIBKML driver, it will become the" +" default reader of KML for ogr, overriding the previous :ref:`KML driver " +"<vector.kml>`. You can still specify either KML or LIBKML as the output " +"driver via the command line" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:22 +msgid "" +"Libkml from Google provides reading services for any valid KML file. " +"However, please be advised that some KML facilities do not map into the " +"Simple Features specification OGR uses as its internal structure. " +"Therefore, a best effort will be made by the driver to understand the " +"content of a KML file read by libkml into ogr, but your mileage may vary." +" Please try a few KML files as samples to get a sense of what is " +"understood. In particular, nesting of feature sets more than one deep " +"will be flattened to support ogr's internal format." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:43 +msgid "" +"You may specify a datasource as a kml file ``somefile.kml`` , a directory" +" ``somedir/`` , or a kmz file ``somefile.kmz`` ." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:47 +msgid "" +"By default on directory and kmz datasources, an index file of all the " +"layers will be read from or written to doc.kml. It contains a " +"`<NetworkLink> " +"<https://developers.google.com/kml/documentation/kmlreference#networklink>`__" +" to each layer file in the datasource. This feature can be turned off by " +"setting the configuration option :config:`LIBKML_USE_DOC.KML` to \"NO\":" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:62 +msgid "StyleTable" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:64 +msgid "" +"Datasource style tables are written to the `<Document> " +"<https://developers.google.com/kml/documentation/kmlreference#document>`__" +" in a .kml, style/style.kml in a kmz file, or style.kml in a directory, " +"as one or more `<Style> " +"<https://developers.google.com/kml/documentation/kmlreference#style>`__ " +"elements. Not all of :ref:`ogr_feature_style` can translate into KML." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:75 +msgid "" +"|about-dataset-creation-options| The following dataset creation options " +"can be used to generate a `<atom:Author> " +"<https://developers.google.com/kml/documentation/kmlreference#atomauthor>`__" +" element at the top Document level." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:95 +msgid "Additional dataset creation options affecting the top Document level:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:117 +msgid "Container properties" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:119 +msgid "" +"The following dataset creation options can be used to set container " +"options :" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:148 +msgid "List style" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:150 +msgid "" +"The following dataset creation options can be used to control how the " +"main folder (folder of layers) appear in the Places panel of the Earth " +"browser, trough a `<ListStyle> " +"<https://developers.google.com/kml/documentation/kmlreference#liststyle>`__" +" element:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:171 +msgid "Balloon style" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:173 +msgid "" +"If a style *foo* is defined, it is possible to add a `<BalloonStyle> " +"<https://developers.google.com/kml/documentation/kmlreference#balloonstyle>`__" +" element to it, by specifying the **foo_BALLOONSTYLE_BGCOLOR** and/or " +"**foo_BALLOONSTYLE_TEXT** elements." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:179 +msgid "NetworkLinkControl" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:181 +msgid "" +"A `<NetworkLinkControl> " +"<https://developers.google.com/kml/documentation/kmlreference#networklinkcontrol>`__" +" element can be defined if at least one of the following dataset creation" +" option is specified:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:235 +msgid "Update documents" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:237 +msgid "" +"When defining the dataset creation option **UPDATE_TARGETHREF**, a " +"NetworkLinkControl KML file with an `<Update> " +"<https://developers.google.com/kml/documentation/kmlreference#update>`__ " +"element will be generated. See the `tutorial about update " +"<https://developers.google.com/kml/documentation/updates>`__." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:243 +msgid "" +"The CreateFeature() operation on a layer will be translated as a " +"`<Create> " +"<https://developers.google.com/kml/documentation/kmlreference#create>`__ " +"element." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:247 +msgid "" +"The SetFeature() operation on a layer will be translated as a `<Change> " +"<https://developers.google.com/kml/documentation/kmlreference#change>`__ " +"element." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:251 +msgid "" +"The DeleteFeature() operation on a layer will be translated as a " +"`<Delete> " +"<https://developers.google.com/kml/documentation/kmlreference#delete>`__ " +"element." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:258 +msgid "" +":cpp:class:`OGRLayer` are mapped to kml files as a `<Document> " +"<https://developers.google.com/kml/documentation/kmlreference#document>`__" +" or `<Folder> " +"<https://developers.google.com/kml/documentation/kmlreference#folder>`__," +" and in kmz files or directories as a separate kml file." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:266 +#: ../../source/drivers/vector/libkml.rst:519 +msgid "Style" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:268 +msgid "" +"Layer style tables can not be read from or written to a kml layer that is" +" a `<Folder> " +"<https://developers.google.com/kml/documentation/kmlreference#folder>`__," +" otherwise they are in the `<Document> " +"<https://developers.google.com/kml/documentation/kmlreference#document>`__" +" that is the layer." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:278 +msgid "" +"Read and write of `<Schema> " +"<https://developers.google.com/kml/documentation/kmlreference#schema>`__ " +"is supported for .kml files, .kmz files, and directories." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:285 +msgid "" +"|about-layer-creation-options| The following layer creation options can " +"be used to generate a `<LookAt> " +"<https://developers.google.com/kml/documentation/kmlreference#lookat>`__ " +"element at the layer level." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:305 +msgid "" +"Alternatively, a `<Camera> " +"<https://developers.google.com/kml/documentation/kmlreference#camera>`__ " +"element can be generated." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:325 +msgid "" +"A `<Region> " +"<https://developers.google.com/kml/documentation/kmlreference#region>`__ " +"element can be generated to control when objects of the layer are visible" +" or not. If :lco:`REGION_XMIN`, :lco:`REGION_YMIN`, :lco:`REGION_XMAX` " +"and :lco:`REGION_YMAX`, the region coordinates are determined from the " +"spatial extent of the features being written in the layer." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:376 +msgid "" +"A `<ScreenOverlay> " +"<https://developers.google.com/kml/documentation/kmlreference#screenoverlay>`__" +" element can be added to display a logo, a legend, etc..." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:405 +msgid "" +"The following option controls whether layers are written as a Document or" +" a Folder:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:417 +msgid "" +"The following layer creation options can be used to set container options" +" :" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:445 +msgid "Do not confuse them with the same named dataset creation options." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:447 +msgid "" +"The following layer creation options can be used to control how the " +"folder of a layer appear in the Places panel of the Earth browser, trough" +" a `<ListStyle> " +"<https://developers.google.com/kml/documentation/kmlreference#liststyle>`__" +" element:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:470 +msgid "" +"An :cpp:class:`OGRFeature` generally translates to kml as a `<Placemark> " +"<https://developers.google.com/kml/documentation/kmlreference#placemark>`__," +" and vice-versa." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:475 +msgid "" +"If the model field is defined, a `<Model> " +"<https://developers.google.com/kml/documentation/kmlreference#model>`__ " +"object within the Placemark will be generated." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:479 +msgid "" +"If the networklink field is defined, a `<NetworkLink> " +"<https://developers.google.com/kml/documentation/kmlreference#networklink>`__" +" will be generated. Other networklink fields are optional." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:483 +msgid "" +"If the photooverlay field is defined, a `<PhotoOverlay> " +"<https://developers.google.com/kml/documentation/kmlreference#photooverlay>`__" +" will be generated (provided that the camera_longitude, camera_latitude, " +"camera_altitude, camera_altitudemode, head and/or tilt and/or roll, " +"leftfov, rightfov, bottomfov, topfov, near fields are also set. The shape" +" field is optional." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:490 +msgid "" +"In case the PhotoOverlay is a big image, it is highly recommended to tile" +" it and generate overview levels, as explained in the `PhotoOverlay " +"tutorial <https://developers.google.com/kml/documentation/photos>`__. In " +"which case, the URL should contain the \"$[level]\", \"$[x]\" and " +"\"$[y]\" sub-strings in the photooverlay field, and the " +"imagepyramid_tilesize, imagepyramid_maxwidth, imagepyramid_maxheight and " +"imagepyramid_gridorigin fields should be set." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:498 +msgid "" +"Placemark, Model, NetworkLink and PhotoOverlay objects can have an " +"associated camera if the camera_longitude, camera_latitude, " +"camera_altitude, camera_altitudemode, head and/or tilt and/or roll fields" +" are defined." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:503 +msgid "" +"KML `<GroundOverlay> " +"<https://developers.google.com/kml/documentation/kmlreference#groundoverlay>`__" +" elements are supported for reading (unless the " +":config:`LIBKML_READ_GROUND_OVERLAY` configuration option is set to " +"FALSE). For such elements, there are icon and drawOrder fields." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:508 +msgid "The following configuration options affect reading of features:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:521 +msgid "" +"Style Strings at the feature level are Mapped to KML as either a `<Style>" +" <https://developers.google.com/kml/documentation/kmlreference#style>`__ " +"or `<StyleUrl> " +"<https://developers.google.com/kml/documentation/kmlreference#styleurl>`__" +" in each `<Placemark> " +"<https://developers.google.com/kml/documentation/kmlreference#placemark>`__." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:528 +msgid "The following configuration options affect handling of styles:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:556 +msgid "" +"When writing a kml, if there exist 2 styles of the form " +"\"astylename_normal\" and \"astylename_highlight\" (where astylename is " +"any string), then a StyleMap object will be creating from both styles and" +" called \"astylename\"." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:562 +msgid "Fields" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:564 +msgid "" +"OGR fields (feature attributes) are mapped to kml with `<Schema> " +"<https://developers.google.com/kml/documentation/kmlreference#schema>`__;" +" and `<SimpleData> " +"<https://developers.google.com/kml/documentation/kmlreference#simpledata>`__," +" except for some special fields as noted below." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:572 +msgid "" +"It is also possible to export fields as `<Data> " +"<https://developers.google.com/kml/documentation/kmlreference#data>`__ " +"elements using the following configuration option:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:581 +msgid "" +"A rich set of :ref:`configuration options <configoptions>` are available " +"to define how fields in input and output, map to a KML `<Placemark> " +"<https://developers.google.com/kml/documentation/kmlreference#placemark>`__." +" For example, if you want a field called 'Cities' to map to the `<name> " +"<https://developers.google.com/kml/documentation/kmlreference#name>`__; " +"tag in KML, you can set a configuration option. Note these are " +"independent of layer creation and dataset creation options' `<name>`." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:912 +msgid "" +"Translation of :cpp:class:`OGRGeometry` to KML Geometry is pretty " +"straightforward with only a couple of exceptions. Point to `<Point> " +"<https://developers.google.com/kml/documentation/kmlreference#point>`__ " +"(unless heading and/or tilt and/or roll field names are found, in which " +"case a `Camera " +"<https://developers.google.com/kml/documentation/kmlreference#camera>`__ " +"object will be generated), LineString to `<LineString> " +"<https://developers.google.com/kml/documentation/kmlreference#linestring>`__," +" LinearRing to `<LinearRing> " +"<https://developers.google.com/kml/documentation/kmlreference#linearring>`__," +" and Polygon to `<Polygon> " +"<https://developers.google.com/kml/documentation/kmlreference#polygon>`__." +" In OGR a polygon contains an array of LinearRings, the first one being " +"the outer ring. KML has the tags `<outerBoundaryIs> " +"<https://developers.google.com/kml/documentation/kmlreference#outerboundaryis>`__" +" and `<innerBoundaryIs> " +"<https://developers.google.com/kml/documentation/kmlreference#innerboundaryis>`__" +" to differentiate between the two. OGR has several Multi types of " +"geometry : GeometryCollection, MultiPolygon, MultiPoint, and " +"MultiLineString. When possible, OGR will try to map `<MultiGeometry> " +"<https://developers.google.com/kml/documentation/kmlreference#multigeometry>`__" +" to the more precise OGR geometry type (MultiPoint, MultiLineString or " +"MultiPolygon), and default to GeometryCollection in case of mixed " +"content." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:937 +msgid "The following configuration options control geometry translation:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:961 +msgid "" +"The following bash script will build a :ref:`csv <vector.csv>` file and a" +" :ref:`vrt <vector.vrt>` file, and then translate them to KML using " +":ref:`ogr2ogr` into a .kml file with timestamps and styling." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:1069 +msgid "" +"The following example shows how the three levels of `<name>` in LIBKML " +"relate to their controlling options:" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:9 +msgid "LVBAG" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:13 +msgid "" +"This driver can read XML files in the LV BAG 2.0 extract format as " +"provided by the Dutch Kadaster BAG products. All LV BAG 2.0 extract " +"products are supported. The driver supports all BAG layers including " +"those introduced in BAG 2.0." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:17 +#: ../../source/drivers/vector/ods.rst:14 +#: ../../source/drivers/vector/xlsx.rst:16 +msgid "" +"The driver is only available if GDAL/OGR is compiled against the Expat " +"library." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:20 +msgid "" +"Each extract XML file is presented as a single OGR layer. The layers are " +"georeferenced in their native (EPSG:28992) SRS." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:23 +msgid "" +"More information about the LV BAG 2.0 can be found at " +"https://www.kadaster.nl/zakelijk/producten/adressen-en-" +"gebouwen/bag-2.0-extract" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:25 +msgid "" +"LV BAG model definitions are available at " +"https://developer.kadaster.nl/schemas/-/categories/4119958" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:27 +msgid "" +"Note 1 : The earlier BAG 1.0 extract is **not supported**\\ by this " +"driver." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:29 +msgid "" +"Note 2 : The driver will only read ST (Standaard Levering) extract files." +" Mutation ML (Mutatie Levering) files are not supported." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:35 +msgid "" +"The following open options can be specified (typically with the **-oo**\\" +" name=value parameters of ogrinfo or ogr2ogr):" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:55 +msgid "" +"The driver supports reading from files managed by VSI Virtual File System" +" API, which include \"regular\" files, as well as files in the /vsizip/ " +"domain. See examples below." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:67 +msgid "" +"The ogr2ogr utility can be used to dump the results of a LV BAG extract " +"to WGS84 in GeoJSON:" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:74 +msgid "How to dump contents of extract file as OGR sees it:" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:80 +msgid "" +"Insert repaired features from LV BAG extract archive into PostgreSQL as " +"WGS84 geometries. The table 'pand' will be created with the features from" +" 9999PND18122019.zip. The database instance (lvbag) must already exist, " +"and the table 'pand' must not already exist." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:88 +msgid "Load a LV BAG extract directory into Postgres:" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:97 +msgid "Create GeoPackage from 'Nummeraanduiding' dataset:" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:108 +msgid "" +"`Kadaster LV BAG 2.0 page (Dutch) " +"<https://www.kadaster.nl/zakelijk/producten/adressen-en-" +"gebouwen/bag-2.0-extract>`__" +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:12 +msgid "" +"This driver implements read and write support for the `MapML " +"specification <https://maps4html.org/MapML/spec>`_. It only implements " +"reading and writing vector features." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:18 +msgid "" +"This driver implements an experimental specification, and inherits its " +"experimental status. This specification may change at a later point, or " +"not be adopted. Files written by this driver may no longer be readable in" +" later versions of GDAL." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:36 +msgid "Layers are identified with the ``class`` attribute of features." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:38 +msgid "" +"Fields are retrieved from the HTML table in the ``properties`` element of" +" features. This assumes that they are written following the exact same " +"structure as the write side of the driver. Otherwise no fields will be " +"retrieved. Field type is guessed from the values, and may consequently be" +" sometimes inaccurate." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:46 +msgid "Several layers can be written in the same MapML file." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:48 +msgid "" +"Only the following CRS are natively supports, EPSG:4326 (WGS 84), " +"EPSG:3857 (WebMercator), EPSG:3978 (NAD83 / Canada Atlas Lambert) and " +"EPSG:5936 (WGS 84 / EPSG Alaska Polar Stereographic). Layers in other CRS" +" will be automatically reprojected to EPSG:4326." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:53 +msgid "" +"Geometry types Point, LineString, Polygon, MultiPoint, MultiLineString, " +"MultiPolygon and GeometryCollection are supported." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:56 +msgid "Attributes are written as a HTML table." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:152 +msgid "`MapML specification <https://maps4html.org/MapML/spec>`_" +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:153 +msgid "`MapML schemas <https://github.com/Maps4HTML/MapML/tree/gh-pages/schema>`_" +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:154 +msgid ":ref:`gdal2tiles` mapml output" +msgstr "" + +#: ../../source/drivers/vector/memory.rst:10 +msgid "" +"This driver implements read and write access layers of features contained" +" entirely in memory. This is primarily useful as a high performance, and " +"highly malleable working data store. All update options, geometry types, " +"and field types are supported." +msgstr "" + +#: ../../source/drivers/vector/memory.rst:15 +msgid "" +"There is no way to open an existing Memory datastore. It must be created " +"with CreateDataSource() and populated and used from that handle. When the" +" datastore is closed all contents are freed and destroyed." +msgstr "" + +#: ../../source/drivers/vector/memory.rst:19 +msgid "" +"The driver does not implement spatial or attribute indexing, so spatial " +"and attribute queries are still evaluated against all features. Fetching " +"features by feature id should be very fast (just an array lookup and " +"feature copy)." +msgstr "" + +#: ../../source/drivers/vector/memory.rst:34 +msgid "" +"Any name may be used for a created datasource. There are no datasource or" +" layer creation options supported. Layer names need to be unique, but are" +" not otherwise constrained." +msgstr "" + +#: ../../source/drivers/vector/memory.rst:38 +msgid "" +"Before GDAL 2.1, feature ids passed to CreateFeature() are preserved " +"*unless* they exceed 10000000 in which case they will be reset to avoid a" +" requirement for an excessively large and sparse feature array. Starting " +"with GDAL 2.1, sparse IDs can be handled." +msgstr "" + +#: ../../source/drivers/vector/memory.rst:43 +msgid "New fields can be added or removed to a layer that already has features." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:8 +msgid "MiraMonVector" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:12 +msgid "" +"This driver is capable of translating (reading and writing) structured " +"vectors of point, arc (*linestrings*), and polygon types from MiraMon " +"vector format." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:15 +msgid "" +"In MiraMon the concepts of OGRMultiPoints and OGRMultiLineStrings are not" +" supported, but the driver translates a multipoint into N points and a " +"multistring into N arcs. When reading a MiraMon file of type *.pol*, the " +"corresponding layer will be reported as of type wkbPolygon, but depending" +" on the number of parts of each geometry, the actual type of the geometry" +" for each feature can be either OGRPolygon or OGRMultiPolygon." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:22 +msgid "" +"The reading driver verifies if multipart polygons adhere to the " +"specification (that is to say, the vertices of outer rings should be " +"oriented clockwise on the X/Y plane, and those of inner rings " +"counterclockwise). Otherwise, the driver corrects the orientation (in the" +" original format this specification is not the case as polygon files are " +"based on topological arc files, where the order of the vertices may be " +"relevant)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:30 +msgid "" +"Measures (M coordinate) are not supported. Symbolization is neither read " +"nor generated by this driver." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:33 +msgid "" +"A `look-up-table of MiraMon " +"<https://www.miramon.cat/help/eng/mm32/AP6.htm>`__ and `EPSG " +"<https://epsg.org/home.html>`__ Spatial Reference Systems allows matching" +" identifiers in both systems." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:37 +msgid "" +"If a layer contains an old *.rel* format file (used some decades ago), a " +"warning message will appear explaining how to convert it into a modern " +"*.rel 4* file." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:50 +msgid "Overview of MiraMon format" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:52 +msgid "" +"The MiraMon format is a binary format for vector layer data, linked to " +"one or more database tables, with or without topology and with rich " +"metadata. More information about the structured MiraMon vector format is " +"available `on the public specification " +"<https://www.miramon.cat/new_note/eng/notes/MiraMon_structured_vectors_file_format.pdf>`__." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:57 +msgid "" +"It is important to keep in mind that a MiraMon vector layer is composed " +"by several files as follows:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:59 +msgid "" +"To operate with a point layer, you must provide the name with the " +"extension .pnt (the T.dbf and T.rel files must accompany the .pnt)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:62 +msgid "" +"To operate with a linestring layer, you must provide the name with the " +"extension .arc (the A.dbf and A.rel, .nod, N.dbf, and N.rel files must " +"accompany the .arc)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:65 +msgid "" +"To operate with a polygon layer, you must provide the name with the " +"extension .pol (the P.dbf, P.rel, A.dbf and A.rel, .nod, N.dbf, and N.rel" +" files must accompany the .pol)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:68 +msgid "" +"By providing only the main file name, the driver will automatically use " +"the other sidecar files to obtain the necessary information. In the " +"creation of MiraMon layers, you only need to provide the name of the main" +" file (with or without extension), and the driver will create the rest of" +" the files." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:72 +msgid "The following outlines the information contained within each sidecar file:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:74 +msgid "" +"Preliminary note: *FileName* is, in the following explanations, the first" +" part of the name of the layer file." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:77 +msgid "" +"**Point layers**: These layers contain *point* type features which are " +"described by a single coordinate (x,y) or (x, y, z). Each layer is " +"composed by 3 files:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:80 +msgid "" +"*FileName.pnt* file: Contains the geographic database with the " +"coordinates that define the point vector features." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:83 +msgid "" +"*FileNameT.dbf* file (note the 'T' before the '.'): Contains the main " +"table of the database in dBASE (DBF) format, or in `extended DBF format " +"<https://www.miramon.cat/new_note/eng/notes/DBF_estesa.pdf>`__, if " +"necessary. It contains the information (usually alphanumeric, but also " +"file or web links, etc) of every feature. The Feature Identifier (FID) " +"field is a field called *ID_GRAFIC* and relates every geographical " +"feature to one or more records in the main table." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:89 +msgid "" +"*FileNameT.rel* file (note the 'T' before the '.'): Contains the layer " +"metadata, the relational structure of the database (links between the " +"main table and other tables [thesauruses, etc] if needed, and the " +"cardinality of the link) and the default symbolization description. In " +"the GDAL environment only some aspects are documented: the spatial " +"reference system, the language of the metadata (English), the extension " +"and a description of the fields." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:96 +msgid "" +"**Arc layers**: These layers contain *linestring* type features which are" +" lines described by a series of segments, each one defined by coordinates" +" (x, y) or (x, y, z). Both extreme vertices of each *linestring* are " +"called nodes. Each layer is composed by 6 files:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:100 +msgid "" +"*FileName.arc* file: Contains the geographic database with the " +"coordinates that define the linestring (arc) vector features." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:103 +msgid "" +"*FileNameA.dbf* file (note the 'A' before the '.'): Contains the main " +"table of the database in dBASE (DBF) format, or in `extended DBF format " +"<https://www.miramon.cat/new_note/eng/notes/DBF_estesa.pdf>`__, if " +"necessary. It contains the information (usually alphanumeric, but also " +"file or web links, etc) of every feature. The Feature Identifier (FID) " +"field is a field called *ID_GRAFIC* and relates every geographical " +"feature to one or more records in the main table." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:109 +msgid "" +"*FileNameA.rel* file (note the 'A' before the '.'): Contains the layer " +"metadata, the relational structure of the database (links between the " +"main table and other tables [thesauruses, etc] if needed, and the " +"cardinality of the link) and the default symbolization description. In " +"the GDAL environment only some aspects are documented: the spatial " +"reference system, the language of the metadata (English), the extension " +"and a description of the fields." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:116 +#: ../../source/drivers/vector/miramon.rst:169 +msgid "" +"*FileName.nod* file: Contains the geographic database with information " +"about the linestring needed to define each node. It is necessary in the " +"MiraMon vector format but not read by the GDAL MiraMon vector driver " +"because nodes contain topological information that is not transferred to " +"other formats." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:121 +#: ../../source/drivers/vector/miramon.rst:174 +msgid "" +"*FileNameN.dbf* file (note the 'N' before the '.'): Contains the main " +"table of the database in dBASE (DBF) format, or in extended DBF if " +"necessary. This table contains information about the relationships " +"between arcs and nodes, and other attributes of the nodes, if needed. It " +"is necessary in the MiraMon vector format but not read by the GDAL " +"MiraMon vector driver because nodes contain topological information that " +"is not transferred to other formats." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:127 +msgid "" +"*FileNameN.rel* file (note the 'N' before the '.'): Contains the layer " +"metadata, the relational structure of the database (links between the " +"main table and other tables [thesauruses, etc] if needed, and the " +"cardinality of the link) and the default symbolization description. It is" +" necessary in the MiraMon vector format but not read by the GDAL MiraMon " +"vector driver because nodes contain topological information that is not " +"transferred to other formats." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:134 +msgid "" +"**Polygon layers**: These layers contain *polygon* or *multipolygon* type" +" features. In MiraMon vector format a polygon is a closed shape described" +" by one or more arcs. A polygon can have holes inside it. A polygon can " +"also be linked to other polygons; in this case, it is termed a group " +"(*multipolygon*). Each layer is composed by 9 files:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:140 +msgid "" +"*FileName.pol* file: Contains the geographic database with information " +"about the linestring vector features needed to define the polygon (or " +"multipolygon) vector features." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:143 +msgid "" +"*FileNameP.dbf* file (note the 'P' before the '.'): Contains the main " +"table of the database in dBASE (DBF) format, or in `extended DBF format " +"<https://www.miramon.cat/new_note/eng/notes/DBF_estesa.pdf>`__, if " +"necessary. It contains the information (usually alphanumeric, but also " +"file or web links, etc) of every feature. The Feature Identifier (FID) " +"field is a field called *ID_GRAFIC* and relates every geographical " +"feature to one or more records in the main table." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:149 +msgid "" +"*FileNameP.rel* file (note the 'P' before the '.'): Contains the layer " +"metadata, the relational structure of the database (links between the " +"main table and other tables [thesauruses, etc] if needed, and the " +"cardinality of the link) and the default symbolization description. In " +"the GDAL environment only some aspects are documented: the spatial " +"reference system, the language of the metadata (English), the extension " +"and a description of the fields." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:156 +msgid "" +"*FileName.arc* file: Contains the geographic database with the " +"coordinates that define the arc vector features. The polygons within the " +"polygon file reference the arcs in this file by their index." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:159 +msgid "" +"*FileNameA.dbf* file (note the 'A' before the '.'): Contains the main " +"table of the database in dBASE (DBF) format, or in extended DBF if " +"necessary. This table contains information about the relationship between" +" arcs and polygons, not the main features information. It is necessary in" +" MiraMon but not read directly by the GDAL MiraMon vector driver because " +"it is redundant to the information on the linestring part." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:165 +msgid "" +"*FileNameA.rel* file (note the 'A' before the '.'): Contains additional " +"data about the data, the relations of the database and the symbolization " +"description. It is necessary in MiraMon but not read directly by the GDAL" +" MiraMon vector driver." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:180 +msgid "" +"*FileNameN.rel* file (note the 'N' before the '.'): Contains additional " +"data about the data, the relations of the database and the symbolization " +"description. It is necessary in MiraMon but not read directly by the GDAL" +" MiraMon vector driver." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:185 +#: ../../source/drivers/vector/shapefile.rst:66 +msgid "Encoding" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:187 +msgid "" +"When reading MiraMon files the code page setting in the header of the " +".dbf file is read and used to translate string fields to UTF-8 " +"(regardless of whether they are in ANSI, OEM or UTF-8)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:191 +msgid "" +"When writing MiraMon files the codepage of *.dbf* files can be ANSI or " +"UTF8 depending on the layer creation option DBFEncoding." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:197 +msgid "" +"MiraMon can only store one kind of geometry per layer (points, arcs or " +"polygons). Mixing different kinds of layers (including raster and " +"geoservices as WMS or WMTS) is possible through MiraMon maps (.mmm). " +"During creation the driver generates the necessary files to accommodate " +"each of the three possible types of geometries. For instance, if a layer " +"or a dataset contains points and arcs, a set of point files and a set of " +"arc files will be created." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:205 +msgid "" +"Consequently, during creation the MiraMon vector driver output can be a " +"folder or a set of files with the appropriate extension (*.pnt*, etc):" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:208 +msgid "" +"If the output is a **folder**, it will contain all the translated layers " +"with the original name in the origin dataset." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:210 +msgid "" +"In this case a *.mmm* file will be created referencing all layers in the " +"origin dataset to make an easy open of the dataset using the MiraMon " +"software." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:212 +msgid "" +"In this case, please specify the MiraMon file output format name using " +"the -f option (**-f MiraMonVector**)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:214 +msgid "" +"If the output is a **file** with extension all the translated layers in " +"the origin dataset will be created with the specified name. Use this " +"option only when you know that there is only one layer with one feature " +"type in the origin dataset." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:217 +msgid "" +"The attributes of the MiraMon feature are stored in an associated *.dbf*." +" If a classical DBF IV table could not be used (too many fields or " +"records, large text fields, etc) a file type called extended DBF is used." +" This is an improvement of dBASE IV DBF files. The specification of this " +"format can be found in `this file " +"<https://www.miramon.cat/new_note/eng/notes/DBF_estesa.pdf>`__." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:223 +msgid "" +"Note that extended *.dbf* files cannot be opened with Excel or other " +"typical programs. If the complete MiraMon Professional software is not " +"installed on the computer, the free and standalone MiraD application can " +"be downloaded from `this page <https://www.miramon.cat/USA/Prod-" +"MiraD.htm>`__ to open them." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:232 +msgid "The MiraMon driver accepts three types of sources of data:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:234 +msgid "" +"When translating from a MiraMon vector format, the MiraMon vector driver " +"input needs a file with one of the described extensions:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:237 +msgid "*.pnt* for *points*." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:238 +msgid "*.arc* for *linestrings*." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:239 +msgid "*.pol* for *polygons* (or *multipolygons*)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:241 +msgid "" +"The extension *.nod* is not valid for translation. Take in consideration " +"all auxiliary files described above." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:244 +#: ../../source/drivers/vector/shapefile.rst:227 +msgid "Field sizes" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:246 +msgid "" +"The driver will automatically extend string and integer fields to " +"dynamically accommodate the length of the data to be inserted." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:250 +#: ../../source/drivers/vector/shapefile.rst:251 +msgid "Size Issues" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:252 +msgid "" +"Geometry: The MiraMon vector format explicitly uses 32-bit offsets in the" +" 1.1 version and 64-bit offsets in the 2.0 version. It is better to " +"produce 1.1 version files if 2.0 version is not really necessary than " +"always use 2.0 version. Version 1.x files are smaller." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:256 +#: ../../source/drivers/vector/shapefile.rst:257 +msgid "" +"Attributes: The dbf format does not have any offsets in it, so it can be " +"arbitrarily large." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:262 +msgid "The following open options are available." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:315 +msgid "" +"As at the moment of this release, UTF-8 tables are not editable in the " +"`MiraD application <https://www.miramon.cat/USA/Prod-MiraD.htm>`__, so it" +" is recommended to use ANSI instead, if there are no coding problems." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:329 +msgid "" +"A translation from an *Example_1.dxf* file with one layer but some " +"different geometric types in the layer, will result 'file1.dxf' into a " +"new MiraMon set of layers in the 'output_folder'." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:337 +msgid "" +"A translation from a *Example_2.dxf* file with one polygon type layer " +"'file1.dxf' into a new MiraMon layer 'territories.pol' (with UTF-8 " +"encoding at the *.dbf* files) is performed like this:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:345 +msgid "" +"A translation from a MiraMon layer of arcs, 'rivers.arc', into a new " +"*.gml* file (taking only the first element of the multirecords in the " +"attributes table) is performed like this:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:352 +msgid "" +"A translation from a MiraMon layer 'tracks.arc' into a new *.gml* file " +"taking the first height of every point is performed like this:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:359 +msgid "" +"A translation from a MiraMon layer 'tracks.arc' into a new *.gml* file " +"taking the last height of every point and documenting the attribute " +"descriptors in Catalan (if the layer is multilingual and it has this " +"language available) is performed like this:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:371 +msgid "" +"`MiraMon's vector format specifications " +"<https://www.miramon.cat/new_note/eng/notes/MiraMon_structured_vectors_file_format.pdf>`__" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:372 +msgid "" +"`MiraMon Extended DBF format " +"<https://www.miramon.cat/new_note/eng/notes/DBF_estesa.pdf>`__" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:373 +msgid "" +"`MiraMon vector layer concepts " +"<https://www.miramon.cat/help/eng/mm32/ap2.htm#structured_vector>`__." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:374 +msgid "`MiraMon page <https://www.miramon.cat/Index_usa.htm>`__" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:375 +msgid "`MiraMon help guide <https://www.miramon.cat/help/eng>`__" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:376 +msgid "" +"`Grumets research group, the people behind MiraMon " +"<https://www.grumets.cat/index_eng.htm>`__" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:6 +msgid "MapInfo File" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:10 +msgid "" +"MapInfo datasets in native (TAB) format and in interchange (MIF/MID) " +"format are supported for reading and writing. Update of existing TAB " +"files is supported (append of new features, modifications and deletions " +"of existing features, adding/renaming/deleting fields, ...). Update of " +"existing MIF/MID files is not supported." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:17 +msgid "" +"Note: In the rest of this document \"MIF/MID File\" is used to refer to a" +" pair of .MIF + .MID files, and \"TAB file\" refers to the set of files " +"for a MapInfo table in binary form (usually with extensions .TAB, .DAT, " +".MAP, .ID, .IND)." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:22 +msgid "" +"The MapInfo driver treats a whole directory of files as a dataset, and a " +"single file within that directory as a layer. In this case the directory " +"name should be used as the dataset name." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:26 +msgid "" +"However, it is also possible to use one of the files (.tab or .mif) in a " +"MapInfo set as the dataset name, and then it will be treated as a dataset" +" with one single layer." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:30 +msgid "" +"MapInfo coordinate system information is supported for reading and " +"writing." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:45 +msgid "" +"The TAB File format requires that the bounds (geographical extents) of a " +"new file be set before writing the first feature." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:48 +msgid "" +"There is currently no automated setting of valid default bounds for each " +"spatial reference system, so for the time being, the MapInfo driver sets " +"the following default bounds when a new layer is created:" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:52 +msgid "" +"For a file in LAT/LON (geographic) coordinates: BOUNDS (-180, -90) (180, " +"90)" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:54 +msgid "" +"For any other projection: BOUNDS (-30000000 + false_easting, -15000000 + " +"false_northing) (30000000 + false_easting, 15000000 + false_northing)" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:58 +msgid "It is possible to override those bounds through two mechanisms." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:60 +msgid "" +"specify a user-defined file that contain projection definitions with " +"bounds. The name of this file must be specified with the " +":config:`MITAB_BOUNDS_FILE` configuration option. This allows users to " +"override the default bounds for existing projections, and to define " +"bounds for new projections not listed in the hard-coded table in the " +"driver. The format of the file is a simple text file with one CoordSys " +"string per line. The CoordSys lines should follow the MIF specs, and MUST" +" include the optional Bounds definition at the end of the line, e.g." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:74 +msgid "" +"It is also possible to establish a mapping between a source CoordSys and " +"a target CoordSys with bounds. Such a mapping is specified by adding a " +"line starting with \"Source = \" followed by a CoordSys (spaces before or" +" after the equal sign do not matter). The following line should start " +"with \"Destination = \" followed by a CoordSys with bounds, e.g." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:87 +msgid "use the :lco:`BOUNDS` layer creation option (see below)" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:89 +msgid "" +"If no coordinate system is provided when creating a layer, the projection" +" case is used, not geographic, which can result in very low precision if " +"the coordinates really are geographic. You can add \"-a_srs WGS84\" to " +"the **ogr2ogr** commandline during a translation to force geographic " +"mode." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:95 +msgid "MapInfo feature attributes suffer a number of limitations:" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:97 +msgid "" +"Only Integer, Real and String field types can be created. The various " +"list, and binary field types cannot be created." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:99 +msgid "" +"For String fields, the field width is used to establish storage size in " +"the .dat file. This means that strings longer than the field width will " +"be truncated" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:102 +msgid "String fields without an assigned width are treated as 254 characters." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:164 +msgid "Currently supported values for the encoding name are:" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:166 +msgid "MapInfo encodings" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ENCODING value" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "MapInfo charset" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "description" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "\"\" (empty string)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "Neutral" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "No character conversions performed." +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "UTF-8 (Works with recent MapInfo versions, since v15.2)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_1" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-1 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-2" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_2" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-2 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-3" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_3" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-3 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-4" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_4" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-4 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-5" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_5" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-5 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-6" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_6" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-6 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-7" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_7" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-7 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-8" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_8" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-8 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-9" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_9" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-9 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "EUC-JP" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "PackedEUCJapaese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "UNIX, standard Japanese implementation." +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1252" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsLatin1" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1250" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsLatin2" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1256" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsArabic" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1251" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsCyrillic" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1257" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsBalticRim" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1253" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsGreek" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1255" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsHebrew" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1254" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsTurkish" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "Windows Eastern Europe" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP950" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsTradChinese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "Windows Traditional Chinese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP936" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsSimpChinese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "Windows Simplified Chinese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP932" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsJapanese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP949" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsKorean" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP437" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage437" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 437 = IBM Extended ASCII" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP850" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage850" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 850 = Multilingual" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP852" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage852" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 852 = Eastern Europe" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP855" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage855" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 855 = Cyrillic" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP857" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage857" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP860" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage860" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 860 = Portuguese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP861" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage861" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 861 = Icelandic" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP863" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage863" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 863 = French Canadian" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP864" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage864" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 864 = Arabic" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP865" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage865" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 865 = Nordic" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP869" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage869" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 869 = Modern Greek" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "(no iconv match)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "LICS" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "Lotus worksheet release 1,2 character set" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "LMBCS" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "Lotus worksheet release 3,4 character set" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:206 +msgid "`MITAB Page <http://mitab.maptools.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:207 +msgid "" +"`About friendly layer names " +"<https://support.pitneybowes.com/SearchArticles/VFP05_KnowledgeWithSidebarHowTo?id=kA180000000CtuHCAS&popup=false&lang=en_US>`__" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:12 +msgid "This driver can connect to the a MongoDB service." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:14 +msgid "" +"The driver supports read, creation, update and delete operations of " +"documents/features and collections/layers. The MongoDB database must " +"exist before operating on it with OGR." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:18 +msgid "This driver requires the MongoDB C++ v3.4.0 client library." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:28 +msgid "MongoDB vs OGR concepts" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:30 +msgid "" +"A MongoDB collection within a database is considered as a OGR layer. A " +"MongoDB document is considered as a OGR feature." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:36 +msgid "There are two main possible syntaxes:" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:38 +msgid "" +"One using `MongoDB URI <https://docs.mongodb.com/manual/reference" +"/connection-string/index.html>`__ prefixed with *MONGODBV3:*, such as " +"MONGODBV3:mongodb://[usr:pwd@]host1[:port1]...[,hostN[:portN]]][/[db][?options]]" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:42 +msgid "" +"One using just MongoDBv3: as the name and open options to specify host, " +"port, user, password, database, etc..." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:45 +msgid "" +"Note: the MONGODBV3: prefix before a URI starting with *mongodb://* is " +"required to make it recognize by this driver, instead of the legacy " +"driver. If the URI is starting with *mongodb+srv://*, then it is not " +"needed." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:50 +msgid "|about-open-options| The open options available are:" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:149 +msgid "Whether to use bulk insert for feature creation." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:154 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server when a \"2d\" or \"2dsphere\" spatial index is available on " +"the geometry field." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:158 +msgid "" +"However, in the current state, SQL attribute filters set with " +"SetAttributeFilter() are evaluated only on client-side. To enable server-" +"side filtering, the string passed to SetAttributeFilter() must be a JSON " +"object in the `MongoDB filter syntax " +"<https://docs.mongodb.com/manual/reference/method/db.collection.find/index.html>`__." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:167 +msgid "" +"Features are retrieved from the server by chunks of 101 documents or just" +" enough documents to exceed 1 megabyte. Subsequent batch size is 4 " +"megabytes. This can be altered with the BATCH_SIZE open option." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:174 +msgid "" +"When reading a MongoDB collection, OGR must establish the schema of " +"attribute and geometry fields, since, contrary to MongoDB collections " +"which are schema-less, OGR has a fixed schema concept." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:178 +msgid "" +"In the general case, OGR will read the first 100 documents (can be " +"altered with the FEATURE_COUNT_TO_ESTABLISH_FEATURE_DEFN open option) of " +"the collection and build the schema that best fit to the found fields and" +" values." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:183 +msgid "" +"If the collection/layer has been previously created with OGR, a " +"\\_ogr_metadata special collection contains the OGR schema, in which case" +" it will be directly used. It might be possible to ignore the schema " +"written in \\_ogr_metadata by setting the USE_OGR_METADATA=NO open " +"option." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:189 +msgid "" +"It is also possible to set the JSON_FIELD=YES open option so that a " +"\\_json special field is added to the OGR schema. When reading MongoDB " +"documents as OGR features, the full JSON version of the document will be " +"stored in the \\_json field. This might be useful in case of complex " +"documents or with data types that do not translate well in OGR data " +"types. On creation/update of documents, if the \\_json field is present " +"and set, its content will be used directly (other fields will be " +"ignored)." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:201 +msgid "" +"MongoDB have a special \\_id field that contains the unique ID of the " +"document. This field is returned as an OGR field, but cannot be used as " +"the OGR special FeatureID field, which must be of integer type. By " +"default, OGR will try to read a potential 'ogc_fid' field to set the OGR " +"FeatureID. The name of this field to look up can be set with the FID open" +" option. If the field is not found, the FID returned by OGR will be a " +"sequential number starting at 1, but it is not guaranteed to be stable at" +" all." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:213 +msgid "" +"If specifying \"MongoDB\" as the dialect of ExecuteSQL(), a JSON string " +"with a serialized `MongoDB command " +"<https://docs.mongodb.com/manual/reference/command/index.html>`__ can be " +"passed. The result will be returned as a JSON string in a single OGR " +"feature." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:219 +msgid "Standard SQL requests will be executed on client-side." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:224 +msgid "Layer/collection creation and deletion is possible." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:229 +msgid "" +"When inserting a new feature with CreateFeature(), and if the command is " +"successful, OGR will fetch the returned \\_id and use it for the " +"SetFeature() operation." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:286 +msgid "Listing the tables of a MongoDB database:" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:292 +msgid "Filtering on a MongoDB field:" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:298 +msgid "Creating and populating a collection from a shapefile:" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:307 +msgid "" +"GDAL/OGR must be built against the `MongoDB C++ driver client library " +"<https://github.com/mongodb/mongo-cxx-driver>`__, v3.4.0, in order to the" +" MongoDBv3 driver to be compiled." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:311 +msgid "" +"You must first follow `MongoDB C++ driver client build instructions " +"<http://mongocxx.org/mongocxx-v3/installation/>`__." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:314 +msgid "Then:" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:316 +msgid "" +"On Linux/Unix, run ./configure --with-mongocxxv3 (potentially by " +"overriding PKG_CONFIG_PATH to point to the " +"{INSTALLATION_PREFIX_OF_MONGOCXX}/lib/pkgconfig" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:319 +msgid "" +"On Windows, uncomment and adapt the following in nmake.opt (or add in " +"nmake.local):" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:334 +msgid "`MongoDB C++ Driver <https://github.com/mongodb/mongo-cxx-driver>`__" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:335 +msgid "`MongoDB Manual <https://docs.mongodb.com/manual/>`__" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:4 +msgid "MSSQLSpatial - Microsoft SQL Server Spatial Database" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:6 +msgid "MSSQLSpatial" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:10 +msgid "" +"This driver implements support for access to spatial tables in Microsoft " +"SQL Server 2008+ which contains the geometry and geography data types to " +"represent the geometry columns." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:26 +msgid "" +"To connect to a MSSQL datasource, use a connection string specifying the " +"database name, with additional parameters as necessary. The connection " +"strings must be prefixed with '*MSSQL:*'." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:32 +msgid "" +"In addition to the standard parameters of the `ODBC driver connection " +"string <http://msdn.microsoft.com/en-us/library/ms130822.aspx>`__ format " +"the following custom parameters can also be used in the following syntax:" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:37 +msgid "" +"**Tables=schema1.table1(geometry column1),schema2.table2(geometry " +"column2)**: By using this parameter you can specify the subset of the " +"layers to be used by the driver. If this parameter is not set, the layers" +" are retrieved from the geometry_columns metadata table. You can omit " +"specifying the schema and the geometry column portions of the syntax." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:43 +msgid "" +"**GeometryFormat=native|wkb|wkt|wkbzm**: The desired format in which the " +"geometries should be retrieved from the server. The default value is " +"'native' in this case the native SqlGeometry and SqlGeography " +"serialization format is used. When using the 'wkb' or 'wkt' setting the " +"geometry representation is converted to 'Well Known Binary' and 'Well " +"Known Text' at the server. This conversion requires a significant " +"overhead at the server and makes the feature access slower than using the" +" native format. The wkbzm format can only be used with SQL Server 2012." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:53 +msgid "The parameter names are not case sensitive in the connection strings." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:55 +msgid "" +"Specifying the **Database** parameter is required by the driver in order " +"to select the proper database." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:58 +msgid "" +"The connection may contain the optional **Driver** parameter if a custom " +"SQL server driver should be loaded (like FreeTDS). The default is **{SQL " +"Server}**." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:62 +msgid "" +"Authentication is supported either through a **trusted_conection** or " +"through username (**UID**) and password (**PWD**). As providing username " +"and password on the commandline can be a security issue, login " +"credentials can also be more securely stored in user defined environment " +"variables *MSSQLSPATIAL_UID* and *MSSQLSPATIAL_PWD*." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:69 +#: ../../source/drivers/vector/netcdf.rst:140 +#: ../../source/drivers/vector/pg_advanced.rst:60 +msgid "Layers" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:71 +msgid "" +"If the user defines the environment variable " +":config:`MSSQLSPATIAL_LIST_ALL_TABLES=YES` (and does not specify Tables= " +"in the connection string), all regular user tables will be treated as " +"layers. This option is useful if you want tables with with no spatial " +"data" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:76 +msgid "" +"By default the MSSQL driver will only look for layers that are registered" +" in the *geometry_columns* metadata table. If the user defines the " +"environment variable :config:`MSSQLSPATIAL_USE_GEOMETRY_COLUMNS=NO` then " +"the driver will look for all user spatial tables found in the system " +"catalog" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:85 +msgid "" +"The MS SQL Spatial driver passes SQL statements directly to MS SQL by " +"default, rather than evaluating them internally when using the " +"ExecuteSQL() call on the OGRDataSource, or the -sql command option to " +"ogr2ogr. Attribute query expressions are also passed directly through to " +"MSSQL. It's also possible to request the OGR MSSQL driver to handle SQL " +"commands with the :ref:`OGR SQL <ogr_sql_dialect>` engine, by passing " +"**\"OGRSQL\"** string to the ExecuteSQL() method, as the name of the SQL " +"dialect." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:94 +msgid "" +"The MSSQL driver in OGR supports the OGRLayer::StartTransaction(), " +"OGRLayer::CommitTransaction() and OGRLayer::RollbackTransaction() calls " +"in the normal SQL sense." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:101 +msgid "" +"This driver doesn't support creating new databases, you might want to use" +" the *Microsoft SQL Server Client Tools* for this purpose, but it does " +"allow creation of new layers within an existing database." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:286 +msgid "The driver implements transactions at the dataset level, per :ref:`rfc-54`" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:291 +msgid "Creating a layer from an OGR data source" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:299 +msgid "Connecting to a layer and dump the contents" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:307 +msgid "Connecting with username/password" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:313 +msgid "Connecting with username/password stored in environment variables" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:8 +msgid "MVT" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:12 +msgid "" +"The MVT driver can read and write Mapbox Vector Tile files, as standalone" +" files, uncompressed or gzip-compressed (typical extensions are .pbf, " +".mvt, .mvt.gz), or a tileset at a given zoom level of such files. Write " +"support requires GDAL to be built with libsqlite3 and GEOS support." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:18 +msgid "" +"Mapbox Vector Tiles stored within a SQLite container conforming to the " +"MBTiles format are handled by the :ref:`MBTiles <raster.mbtiles>` driver." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:22 +msgid "" +"Tilesets of MVT files can for example be generated by `tippecanoe " +"<https://github.com/mapbox/tippecanoe>`__ or `tileserver-gl " +"<https://github.com/klokantech/tileserver-gl>`__. The output file " +"hierarchy will contain a :ref:`metadata.json <mvt_metadata_json>` file at" +" its root and {z}/{x}/{y}.pbf files with the tiles, where z is the zoom " +"level and (x, y) the coordinate of the tile in a given zoom level. The " +"origin of the tiling system is the top-left tile (XYZ convention). For " +"example, for zoom levels 0 and 1 :" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:45 +msgid "" +"The driver will assume by default EPSG:3857 (WebMercator) spatial " +"reference system and Z/X/Y tiling structure, if opening a filename with " +"{Z}/{X}/{Y}.pbf or {Z}-{X}-{Y}.pbf name, or a zoom level of a tileset. " +"Otherwise integer coordinates will be reported." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:50 +msgid "" +"Note: When opening a zoom level of a tileset, the driver will make no " +"effort of stitching together geometries for features that overlap several" +" tiles." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:66 +msgid "The following connection strings are supported:" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:68 +msgid "*/path/to/some.pbf*" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:69 +msgid "*MVT:http[s]://path/to/some.pbf*" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:70 +msgid "" +"*/path/to/{Z}*: where {Z} is a zoom level between 0 and 30, tiles are in " +"/path/to/{Z}/{X}/{Y}.pbf files, and /path/to/metadata.json or " +"/path/to.json should typically exist." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:73 +msgid "*MVT:http[s]://path/to/{Z]*" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:75 +msgid "" +"The MVT: prefix may be added before the filename or directory name to " +"help forcing identification of datasets in some rare cases where non-" +"guided identification would fail." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:82 +msgid "metadata.json" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:84 +msgid "" +"This file is typically generated by tippecanoe and has the following " +"content:" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:138 +msgid "" +"The MVT driver only uses the \"json\" key to retrieve the layer names, " +"their fields and the geometry type, and the \"bounds\" key for the layer " +"extent." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:142 +msgid "" +"If this file cannot be found, the layer schema is established by scanning" +" the features of the tile(s)." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:145 +msgid "" +"As an extension, OGR handles in reading and writing custom tiling schemes" +" by using the *crs*, *tile_origin_upper_left_x*, " +"*tile_origin_upper_left_y* and *tile_dimension_zoom_0* metadata items. " +"For example, for the Finnish ETRS-TM35FIN (EPSG:3067) tiling scheme:" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:216 +msgid "" +"Tiles are generated with WebMercator (EPSG:3857) projection by default " +"(custom tiling schemes can be defined with the TILING_SCHEME option). " +"Several layers can be written. It is possible to decide at which zoom " +"level ranges a given layer is written." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:269 +#: ../../source/drivers/vector/pmtiles.rst:133 +msgid "" +"Maximum zoom level at which tiles are generated. Maximum supported value " +"is 22." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:370 +#: ../../source/drivers/vector/pmtiles.rst:190 +msgid "Layer configuration" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:442 +msgid "" +"`Mapbox Vector Tile Specification <https://github.com/mapbox/vector-tile-" +"spec>`__" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:444 +msgid ":ref:`MBTiles <raster.mbtiles>` driver" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:445 +msgid "" +"`tippecanoe <https://github.com/mapbox/tippecanoe>`__: Builds vector " +"tilesets from large (or small) collections of GeoJSON, Geobuf, or CSV " +"features" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:448 +msgid "" +"`Links to tools dealing with Mapbox Vector Tiles " +"<https://github.com/mapbox/awesome-vector-tiles>`__" +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:10 +msgid "" +"This driver implements read and write access for spatial data in `MySQL " +"<http://www.mysql.org/>`__ tables." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:13 +msgid "" +"When opening a database, its name should be specified in the form " +"\"MYSQL:dbname[,options]\" where the options can include comma separated " +"items like \"user=*userid*\", \"password=*password*\", \"host=*host*\" " +"and \"port=*port*\"." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:18 +msgid "" +"As well, a \"tables=*table*;*table*...\" option can be added to restrict " +"access to a specific list of tables in the database. This option is " +"primarily useful when a database has a lot of tables, and scanning all " +"their schemas would take a significant amount of time." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:23 +msgid "" +"Currently all regular user tables are assumed to be layers from an OGR " +"point of view, with the table names as the layer names. Named views are " +"not currently supported." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:27 +msgid "" +"If a single integer field is a primary key, it will be used as the FID " +"otherwise the FID will be assigned sequentially, and fetches by FID will " +"be extremely slow." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:31 +msgid "" +"By default, SQL statements are passed directly to the MySQL database " +"engine. It's also possible to request the driver to handle SQL commands " +"with :ref:`OGR SQL <ogr_sql_dialect>` engine, by passing **\"OGRSQL\"** " +"string to the ExecuteSQL() method, as name of the SQL dialect." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:46 +msgid "" +"In the case of a layer defined by a SQL statement, fields either named " +"\"OGC_FID\" or those that are defined as NOT NULL, are a PRIMARY KEY, and" +" are an integer-like field will be assumed to be the FID." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:49 +msgid "" +"Geometry fields are read from MySQL using WKB format. Versions older than" +" 5.0.16 of MySQL are known to have issues with some WKB generation and " +"may not work properly." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:52 +msgid "" +"The OGR_FID column, which can be overridden with the MYSQL_FID layer " +"creation option, is implemented as a **INT UNIQUE NOT NULL " +"AUTO_INCREMENT** field. This appears to implicitly create an index on the" +" field." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:56 +msgid "" +"The geometry column, which defaults to *SHAPE* and can be overridden with" +" the :lco:`GEOMETRY_NAME` layer creation option, is created as a **NOT " +"NULL** column in unless :lco:`SPATIAL_INDEX` is disabled. By default a " +"spatial index is created at the point the table is created." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:60 +msgid "" +"SRS information is stored using the OGC Simple Features for SQL layout, " +"with *geometry_columns* and *spatial_ref_sys* metadata tables being " +"created in the specified database if they do not already exist. The " +"*spatial_ref_sys* table is **not** pre-populated with SRS and EPSG values" +" like PostGIS. If no EPSG code is found for a given table, the MAX(SRID) " +"value will be used. With MySQL 8.0 or later, the " +"*ST_SPATIAL_REFERENCE_SYSTEMS* table provided by the database is used " +"instead of *spatial_ref_sys*." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:68 +msgid "" +"Connection timeouts to the server can be specified with the " +"**MYSQL_TIMEOUT** environment variable. For example, SET " +"MYSQL_TIMEOUT=3600. It is possible this variable only has an impact when " +"the OS of the MySQL server is Windows." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:72 +msgid "" +"The MySQL driver opens a connection to the database using " +"CLIENT_INTERACTIVE mode. You can adjust this setting " +"(interactive_timeout) in your mysql.ini or mysql.cnf file of your server " +"to your liking." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:76 +msgid "" +"We are using WKT to insert geometries into the database. If you are " +"inserting big geometries, you will need to be aware of the " +"*max_allowed_packet* parameter in the MySQL configuration. By default it " +"is set to 1M, but this will not be large enough for really big " +"geometries. If you get an error message like: *Got a packet bigger than " +"'max_allowed_packet' bytes*, you will need to increase this parameter." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:87 +msgid "" +"The MySQL driver does not support creation of new datasets (a database " +"within MySQL), but it does allow creation of new layers within an " +"existing database." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:91 +msgid "" +"By default, the MySQL driver will attempt to preserve the precision of " +"OGR features when creating and reading MySQL layers. For integer fields " +"with a specified width, it will use **DECIMAL** as the MySQL field type " +"with a specified precision of 0. For real fields, it will use **DOUBLE** " +"with the specified width and precision. For string fields with a " +"specified width, **VARCHAR** will be used." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:98 +msgid "The MySQL driver makes no allowances for character encodings at this time." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:101 +msgid "The MySQL driver is not transactional at this time." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:164 +msgid "" +"The following example datasource name opens the database schema " +"*westholland* with password *psv9570* for userid *root* on the port " +"*3306*. No hostname is provided, so localhost is assumed. The tables= " +"directive means that only the bedrijven table is scanned and presented as" +" a layer for use." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:174 +msgid "" +"The following example uses ogr2ogr to create copy the world_borders layer" +" from a shapefile into a MySQL table. It overwrites a table with the " +"existing name *borders2*, sets a layer creation option to specify the " +"geometry column name to *SHAPE2*." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:183 +msgid "" +"The following example uses ogrinfo to return some summary information " +"about the borders2 layer in the test database." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:4 +msgid "NAS - ALKIS" +msgstr "" + +#: ../../source/drivers/vector/nas.rst:6 +msgid "NAS" +msgstr "" + +#: ../../source/drivers/vector/nas.rst:10 +msgid "" +"The NAS driver reads the NAS/ALKIS format used for cadastral data in " +"Germany. The format is a GML profile with fairly complex GML3 objects not" +" easily read with the general OGR GML driver." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:14 +msgid "" +"This driver depends on GDAL/OGR being built with the Xerces XML parsing " +"library." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:17 +msgid "" +"The driver looks for \"opengis.net/gml\" and one of the strings semicolon" +" separated strings listed in the configuration option **NAS_INDICATOR** " +"(which defaults to \"NAS-Operationen;AAA-Fachschema;aaa.xsd;aaa-suite\") " +"to determine if a input is a NAS file and ignores all files without any " +"matches." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:22 +msgid "" +"The configuration option **NAS_GFS_TEMPLATE** makes it possible to " +"cleanly map element paths to feature attributes using a GFS file like in " +"the GML driver. Multiple geometries per layer are also possible (eg. " +"ax_flurstueck.objektkoordinaten next to the regular wkb_geometry). " +"Starting with GDAL 3.7, defining the NAS_GFS_TEMPLATE configuration " +"option is required for the NAS driver to open a file. It may be set to " +"the empty string to mean that the driver should try to establish the " +"schema of the file from its content, but using one of templates mentioned" +" below is recommended. Alternatively, starting with GDAL 3.10, specifying" +" the ``-if NAS`` option to command line utilities accepting it, or " +"``NAS`` as the only value of the ``papszAllowedDrivers`` of " +":cpp:func:`GDALOpenEx`, also forces the driver to recognize the passed " +"filename." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:34 +msgid "" +"The GFS templates and PostgreSQL schemas are part of `norGIS ALKIS-Import" +" <http://www.norbit.de/68/>`__ (also featuring a shell script and PyQt " +"frontend which ease the import). There are currently two versions:" +msgstr "" + +#: ../../source/drivers/vector/nas.rst:38 +msgid "" +"GeoInfoDok 6: `GFS template " +"<https://github.com/norBIT/alkisimport/blob/master/alkis-schema.gfs>`__ " +"(for GDAL >=3.8 and `<3.8 " +"<https://github.com/norBIT/alkisimport/blob/master/alkis-" +"schema.37.gfs>`__) and `PostgreSQL schema " +"<https://github.com/norBIT/alkisimport/blob/master/alkis-schema.sql>`__" +msgstr "" + +#: ../../source/drivers/vector/nas.rst:39 +msgid "" +"GeoInfoDok 7.1.2: `GFS template " +"<https://github.com/norBIT/alkisimport/blob/gid7/alkis-schema.gfs>`__ and" +" `PostgreSQL schema <https://github.com/norBIT/alkisimport/blob/gid7" +"/alkis-schema.sql>`__" +msgstr "" + +#: ../../source/drivers/vector/nas.rst:41 +msgid "" +"The files were generated using `xmi2db " +"<https://github.com/norBIT/xmi2db/>`__ (fork of `xmi2db " +"<https://github.com/pkorduan/xmi2db>`__) from the official application " +"schema." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:45 +msgid "" +"In GDAL 3.8 the creation of the relation layer *alkis_beziehungen* was " +"removed. Prior the configuration option **NAS_NO_RELATION_LAYER** allowed" +" to disable its population - which was default in ALKIS-Import. The " +"information found there was redundant to the relation fields also " +"contained in original elements/tables. Enabling the option also made " +"progress reporting available." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:51 +msgid "" +"Duplicate data in datasets will usually causes errors. When importing " +"separate datasets into PostgreSQL it is useful to enable " +"\"OGR_PG_SKIP_CONFLICTS\" to skip conflicting features." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:55 +msgid "" +"This driver was implemented within the context of the `PostNAS project " +"<http://trac.wheregroup.com/PostNAS>`__, which has more information on " +"its use and other related projects." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:4 +msgid "NetCDF: Network Common Data Form - Vector" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:12 +msgid "" +"The netCDF driver supports read and write (creation from scratch and in " +"some cases append operations) to vector datasets (you can find " +"documentation for the :ref:`raster side <raster.netcdf>`)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:16 +msgid "" +"NetCDF is an interface for array-oriented data access and is used for " +"representing scientific data." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:19 +msgid "" +"The driver handles the \"point\", \"profile\" and \"trajectory\" (single " +"trajectory) `feature types <http://cfconventions.org/cf-" +"conventions/v1.6.0/cf-conventions.html#_features_and_feature_types>`__ of" +" the CF 1.6 convention. For CF-1.7 and below (as well as non-CF files), " +"it also supports a more custom approach for non-point geometries." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:24 +msgid "" +"The driver also supports writing and reading from CF-1.8 convention " +"compliant files that have simple geometry information encoded within " +"them." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:37 +msgid "Conventions and Data Formats" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:38 +msgid "" +"The netCDF vector driver supports reading and writing netCDF files " +"following the Climate and Forecast (CF) Metadata Conventions. Vector " +"datasets can be written using the simple geometry specification of the " +"CF-1.8 convention, or by using the CF-1.6 convention and by writing non-" +"point geometry items as WKT." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:43 +msgid "Distinguishing the Two Formats" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:44 +msgid "" +"Upon reading a netCDF file, the driver will attempt to read the global " +"*Conventions* attribute. If i's value is *CF-1.8* or higher (in this " +"exact format, as specified in the CF convention), then the driver will " +"check if the netCDF file has *CF-1.8* geometries contained within it. If " +"the *Conventions* attribute has a value lower than CF-1.8 or no CF-1.8 " +"geometries, the driver will try to detect \"point\", \"profile\" and " +"\"trajectory\" (single trajectory) feature types." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:49 +msgid "CF-1.8 Writing Limitations" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:50 +msgid "" +"Writing to a CF-1.8 netCDF dataset poses some limitations. Only writing " +"the feature types specified by the CF-1.8 standard (see section `Geometry" +" <#geometry>`__ for more details) are supported, and measured features " +"are only partially supported. Other geometries, such as non-simple curve " +"geometries, are not supported in any way." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:54 +msgid "CF-1.8 datasets also do not support the *append* access mode." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:56 +msgid "" +"There are what are considered *reserved variable names* for CF-1.8 " +"datasets. These variable names are used by the driver to store its " +"metadata. Refrain from using these names as layer names to avoid naming " +"conflicts when writing datasets with multiple layers." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:59 +msgid "" +"Suppose a layer in a CF-1.8 dataset has the name LAYER with a field with " +"name FIELD. Then the following names would be considered *reserved*:" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:61 +msgid "*LAYER_node_coordinates*: used to store point information" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:62 +msgid "" +"*LAYER_node_count*: used to store per shape point count information (not " +"created if LAYER has a geometry type of Point)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:63 +msgid "" +"*LAYER_part_node_count*: used to store per part point count information " +"(only created if LAYER consists of MultiLineStrings, MultiPolygons, or " +"has at least one Polygon with interior rings)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:64 +msgid "" +"*LAYER_interior_ring*: used to store interior ring information (only " +"created if LAYER consists of at least one Polygon with interior rings)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:65 +msgid "*LAYER_field_FIELD*: used to store field information for FIELD." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:67 +msgid "These names are the only reserved names applying to CF-1.8 datasets." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:69 +msgid "CF-1.6/WKT datasets are not limited to the aforementioned restrictions." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:72 +msgid "Mapping of concepts" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:75 +msgid "Field types" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:77 +msgid "" +"On creation of netCDF files, the mapping between OGR field types and " +"netCDF type is the following :" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:81 +#: ../../source/drivers/vector/netcdf.rst:120 +msgid "netCDF type" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:83 +#: ../../source/drivers/vector/netcdf.rst:124 +msgid "String(1)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:83 +msgid "char" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:84 +msgid "char (bi-dimensional), or string for NC4" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:85 +#: ../../source/drivers/vector/netcdf.rst:129 +msgid "int" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:86 +msgid "Integer(Boolean)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:87 +#: ../../source/drivers/vector/netcdf.rst:127 +msgid "Integer(Int16)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:88 +msgid "int64 for NC4, or double for NC3 as a fallback" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:90 +#: ../../source/drivers/vector/netcdf.rst:134 +msgid "Real(Float32)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:90 +#: ../../source/drivers/vector/netcdf.rst:134 +msgid "float" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:91 +#: ../../source/drivers/vector/netcdf.rst:130 +msgid "Date" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:91 +msgid "int (with units=\"days since 1970-1-1\")" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:92 +#: ../../source/drivers/vector/netcdf.rst:136 +msgid "double (with units=\"seconds since 1970-1-1 0:0:0\")" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:95 +msgid "" +"The driver also writes the following attributes for each OGR fields / " +"netCDF variables." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:98 +msgid "" +"*ogr_field_name*: OGR field name (useful if the netCDF variable name is " +"different, due to collision)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:100 +msgid "" +"*ogr_field_type*: OGR field type (such as " +"String,Integer,Date,DateTime,etc...)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:102 +msgid "" +"*ogr_field_width*: OGR field width. Only set if it is non-zero, except " +"for strings" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:104 +msgid "*ogr_field_precision*: OGR field precision. Only set if it is non-zero" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:106 +msgid "" +"*standard_name*\": (GDAL >= 3.7) OGR field alternative name, if it is " +"compatible of the convention for the value of standard_name." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:108 +msgid "" +"*long_name*: (GDAL >= 3.7) OGR field comment, or if not set, OGR field " +"alternative name if it is not compatible of standard_name, or \"Field " +"{ogr_field_name}\" otherwise." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:112 +msgid "" +"They are written by default (unless the `WRITE_GDAL_TAGS " +"<#WRITE_GDAL_TAGS>`__ dataset creation option is set to NO). They are not" +" required for reading, but may help to better identify field " +"characteristics" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:117 +msgid "On reading, the mapping is the following :" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:123 +msgid "ubyte (NC4 only)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:124 +msgid "char (mono dimensional)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:125 +msgid "char (bi dimensional)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:126 +msgid "string (NC4 only)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:128 +msgid "ushort (NC4 only)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:130 +msgid "int or double (with units=\"days since 1970-1-1\")" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:131 +msgid "uint (NC4 only)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:132 +msgid "int64 (NC4 only)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:133 +msgid "uint64 (NC4 only)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:141 +msgid "" +"In the CF-1.8 compliant driver, a single layer corresponds to a single " +"**geometry container** within a CF-1.8 compliant netCDF file. A geometry " +"container, per the CF-1.8 specification, is referred to by another " +"variable (presumably a data variable) through the **geometry** attribute." +" When reading a CF-1.8 compliant netCDF file, all geometry containers " +"within the netCDF file will be present in the opened dataset as separate " +"layers. Similarly, when writing to a CF-1.8 dataset, each layer will be " +"written to a geometry container whose variable name is that of the source" +" layer. When writing to a CF-1.8 dataset specifically, multiple layers " +"are always enabled and are always in a single netCDF file, regardless of " +"the :dsco:`MULTIPLE_LAYERS` option." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:151 +msgid "" +"When working with files made with older versions of the driver (pre " +"CF-1.8), a single netCDF file generally corresponds to a single OGR " +"layer, provided that it contains only mono-dimensional variables, indexed" +" by the same dimension (or bi-dimensional variables of type char). For " +"netCDF v4 files with multiple groups, each group may be seen as a " +"separate OGR layer. On writing, the :dsco:`MULTIPLE_LAYERS` dataset " +"creation option can be used to control whether multiple layers is " +"disabled, or if multiple layers should go in separate files, or separate " +"groups." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:161 +msgid "Strings" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:163 +msgid "" +"Variable length strings are not natively supported in netCDF v3 format. " +"To work around that, OGR uses bi-dimensional char variables, whose first " +"dimension is the record dimension, and second dimension the maximum width" +" of the string." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:168 +msgid "" +"By default, OGR implements a \"auto-grow\" mode in writing, where the " +"maximum width of the variable used to store a OGR string field is " +"extended when needed." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:172 +msgid "" +"For WKT datasets, this leads to a full rewrite of already written " +"records; although this process is transparent for the user, it can slow " +"down the creation process in non-linear ways. A similar mechanism is used" +" to handle layers with geometry types other than point to store the ISO " +"WKT representation of the geometries." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:178 +msgid "" +"For CF-1.8 datasets, growing the string width dimension is a relatively " +"inexpensive process which does not involve recopying of records, but " +"involves only a simple integer reassignment. Because of how inexpensive " +"dimension growth is with CF-1.8 datasets, auto growth of the string width" +" dimension is always on." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:183 +msgid "" +"When using a netCDF v4 output format (NC4), strings will be by default " +"written as netCDF v4 variable length strings." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:189 +msgid "" +"Supported feature types when reading from a CF-1.8 convention compliant " +"netCDF file include OGRPoint, OGRLineString, OGRPolygon, OGRMultiPoint, " +"OGRMultiLineString, and OGRMultiPolygon. Due to slight ambiguities " +"present in the CF-1.8 convention concerning Polygons versus " +"MultiPolygons, the driver will in most cases default to assuming a " +"MultiPolygon for the geometry of a layer with **geometry_type** polygon. " +"The one exception where a Polygon type will be used is when the attribute" +" **part_node_count** is not present within that layer's geometry " +"container. Per convention requirements, the driver supports reading and " +"writing from geometries with X, Y, and Z axes. Writing from source layers" +" with features containing an M axis is also partially supported. The X, " +"Y, and Z information of a measured feature will be able to be captured in" +" a CF-1.8 netCDF file, but the measure information will be lost " +"completely." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:200 +msgid "" +"When working with a CF-1.6/WKT dataset, layers with a geometry type of " +"Point or Point25D will cause the implicit creation of x,y(,z) variables " +"for a projected coordinate system, or lon,lat(,z) variables for " +"geographic coordinate systems. For other geometry types, a variable " +"\"ogc_wkt\" ( bi-dimensional char for NC3 output, or string for NC4 " +"output) is created and used to store the geometry as a ISO WKT string." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:209 +msgid "\"Profile\" feature type" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:211 +msgid "" +"The driver can handle \"profile\" feature type, i.e. phenomenons that " +"happen at a few positions along a vertical line at a fixed horizontal " +"position. In that representation, some variables are indexed by the " +"profile, and others by the observation." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:216 +msgid "" +"More precisely, the driver supports reading and writing profiles " +"organized accordingly with the \"`Indexed ragged array representation " +"<http://cfconventions.org/cf-conventions/v1.6.0/cf-" +"conventions.html#_indexed_ragged_array_representation_of_profiles>`__\" " +"of profiles." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:221 +msgid "" +"On reading, the driver will collect values of variables indexed by the " +"profile dimension and expose them as long as variables indexed by the " +"observation dimension, based on a variable such as \"parentIndex\" with " +"an attribute \"instance_dimension\" pointing to the profile dimension." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:226 +msgid "" +"On writing, the `FEATURE_TYPE <#FEATURE_TYPE>`__\\ =PROFILE layer " +"creation option must be set and the driver will need to be instructed " +"which OGR fields are indexed either by the profile or by the observation " +"dimension. The list of fields indexed by the profile can be specified " +"with the `PROFILE_VARIABLES <#PROFILE_VARIABLES>`__ layer creation " +"options (other fields are assumed to be indexed by the observation " +"dimension). Fields indexed by the profile are the horizontal geolocation " +"(created implicitly), and other user attributes such as the location " +"name, etc. Care should be taken into selecting which variables are " +"indexed by the profile dimension: given 2 OGR features (taking into " +"account only the variables indexed by the profile dimension), if they " +"have different values for such variables, they will be considered to " +"belong to different profiles." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:240 +msgid "" +"In the below example, the station_name and time variables may be indexed " +"by the profile dimension (the geometry is assumed to be also indexed by " +"the profile dimension), since all records that have the same value for " +"one of those variables have same values for the other ones, whereas " +"temperature and Z should be indexed by the default dimension." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:247 +msgid "station_name" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:247 +msgid "time" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:247 +msgid "geometry" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:247 +msgid "temperature" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:247 +msgid "Z" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:249 +#: ../../source/drivers/vector/netcdf.rst:251 +msgid "Paris" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:249 +#: ../../source/drivers/vector/netcdf.rst:251 +msgid "2016-03-01T00:00:00Z" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:249 +#: ../../source/drivers/vector/netcdf.rst:251 +msgid "POINT (2 49)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:249 +msgid "25" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:249 +#: ../../source/drivers/vector/netcdf.rst:250 +msgid "100" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:250 +#: ../../source/drivers/vector/netcdf.rst:252 +msgid "Vancouver" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:250 +#: ../../source/drivers/vector/netcdf.rst:252 +msgid "2016-04-01T12:00:00Z" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:250 +#: ../../source/drivers/vector/netcdf.rst:252 +msgid "POINT (-123 49.25)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:250 +msgid "5" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:251 +#: ../../source/drivers/vector/netcdf.rst:252 +msgid "500" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:252 +msgid "-15" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:255 +msgid "" +"An integer field, with the name of the profile dimension (whose default " +"name is \"profile\", which can be altered with the `PROFILE_DIM_NAME " +"<#PROFILE_DIM_NAME>`__ layer creation option), will be used to store the " +"automatically computed id of profile sites (unless a integer OGR field " +"with the same name exits)." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:261 +msgid "" +"The size of the profile dimension defaults to 100 for non-NC4 output " +"format, and is extended automatically in case of additional profiles " +"(with similar performance issues as growing strings). For NC4 output " +"format, the profile dimension is of unlimited size by default." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:295 +msgid "Whether to write GDAL specific information as netCDF attributes." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:304 +msgid "" +"The following option will only have effect when simultaneously specifying" +" :dsco:`GEOMETRY_ENCODING=WKT`:" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:321 +msgid "|about-layer-creation-options|" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:323 +msgid "The following option applies to both dataset types:" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:332 +msgid "" +"The following options require a dataset with " +":dsco:`GEOMETRY_ENCODING=WKT`:" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:394 +msgid "The following option requires a dataset with GEOMETRY_ENCODING=CF_1.8:" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:425 +msgid "XML configuration file" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:427 +msgid "" +"A XML configuration file conforming to the schema specified in " +":source_file:`frmts/netcdf/data/netcdf_config.xsd` can be used for very " +"precise control on the output format, in particular to set all needed " +"attributes (such as units) to conform to the `NetCDF CF-1.6 convention " +"<http://cfconventions.org/cf-conventions/v1.6.0/cf-conventions.html>`__." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:434 +msgid "" +"It has been designed in particular, but not exclusively, to be usable in " +"use cases involving the `MapServer OGR output " +"<http://mapserver.org/output/ogr_output.html>`__." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:438 +msgid "Such a file can be used to :" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:440 +msgid "set dataset and layer creation options." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:441 +msgid "set global netCDF attributes." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:442 +msgid "map OGR field names to netCDF variable names." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:443 +msgid "set netCDF attributes attached to netCDF variables." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:445 +msgid "" +"The scope of effect is either globally, when elements are defined as " +"direct children of the root <Configuration> node, or specifically to a " +"given layer, when defined as children of a <Layer> node." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:449 +msgid "" +"The filename is specified with the CONFIG_FILE dataset creation option. " +"Alternatively, the content of the file can be specified inline as the " +"value of the option (it must then begin strictly with the " +"\"<Configuration\" characters)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:454 +msgid "The following example shows all possibilities and precedence rules:" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:489 +msgid "The effect on the output can be checked by running the **ncdump** utility" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:493 +msgid "Further Reading" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:495 +msgid ":ref:`Raster side of the netCDF driver. <raster.netcdf>`" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:496 +msgid "" +"`NetCDF CF-1.6 convention <http://cfconventions.org/cf-conventions/v1.6.0" +"/cf-conventions.html>`__" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:498 +msgid "" +"`NetCDF CF-1.8 convention draft <https://github.com/cf-convention/cf-" +"conventions/blob/master/ch07.adoc>`__" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:508 +msgid "" +"Development of the read/write vector capabilities for netCDF was funded " +"by `Meteorological Service of Canada <https://www.ec.gc.ca/meteo-" +"weather/>`__ , `World Ozone and Ultraviolet Radiation Data Centre " +"<http://woudc.org>`__, and the `US Geological Survey " +"<https://www.usgs.gov>`__." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:43 +msgid "" +"The driver can connect to the services implementing the NextGIS Web REST " +"API. NGW driver requires cURL support in GDAL. The driver supports read " +"and write operations." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:53 +msgid "" +"**NextGIS Web URL** may be an URL to nextgis.com cloud service (for " +"example, https://demo.nextgis.com), or some other URL including port and " +"additional path (for example, http://192.168.1.1:8000/test)." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:61 +msgid "" +"All vector layers, PostGIS, raster layers, styles will list as child " +"resources if identifier is resource group. In other case this will be a " +"separate layer." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:70 +msgid ":copy-config:`NGW_USERPWD`" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:89 +msgid ":copy-config:`NGW_JSON_DEPTH`" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:91 +msgid "" +"The depth of json response that can be parsed. If depth is greater than " +"this value, parse error occurs." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:110 +msgid "" +"If the :oo:`NATIVE_DATA` open option is set to YES, the *extensions* json" +" object will store as a serialized json object in the NativeData property" +" of the OGRFeature object (and \"application/json\" in the " +"NativeMediaType property). If writing OGRFeature has NativeMediaType " +"property set to \"application/json\" and its NativeData property set to " +"serialized json object the new NGW feature *extensions* json object will " +"fill from this json object." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:118 +msgid "" +"Extensions json object structure see in `NextGIS Web API documentation " +"<https://docs.nextgis.com/docs_ngweb_dev/doc/developer/resource.html#feature>`__" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:124 +msgid "" +"NextGIS Web supports only one geometry column. Default spatial reference " +"is Web Mercator (EPSG:3857). The following geometry types are available:" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:127 +msgid "POINT" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:128 +msgid "LINESTRING" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:129 +msgid "POLYGON" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:130 +msgid "MULTIPOINT" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:131 +msgid "MULTILINESTRING" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:132 +msgid "MULTIPOLYGON" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:134 +msgid "Geometry with Z value also supported." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:137 +msgid "Field data types" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:139 +msgid "NextWeb supports only following field types:" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:145 +msgid "OFTDate" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:146 +msgid "OFTTime" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:147 +msgid "OFTDateTime" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:152 +msgid "" +"Features can retrieved from NextGIS Web by chunks if supported by server " +"(available since NextGIS Web 3.1). The chunk size can be altered with the" +" :config:`NGW_PAGE_SIZE` configuration option or :oo:`PAGE_SIZE` open " +"option." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:160 +msgid "" +"Datasource and layers creation and deletion is possible. Write support is" +" only enabled when the datasource is opened in update mode and user has " +"appropriate permissions. Vector and PostGIS layers insert and update " +"operations are cached if :oo:`BATCH_SIZE` is greater 0. Delete operation " +"executes immediately." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:209 +#: ../../source/drivers/vector/tiledb.rst:140 +#: ../../source/drivers/vector/vdv.rst:49 +msgid "" +"|about-dataset-creation-options| The following dataset creation options " +"are available:" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:241 +msgid "Whether to store the json *extensions* key in feature native data." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:281 +msgid "" +"NextGIS Web metadata are supported in datasource, vector, PostGIS, raster" +" layers and styles. Metadata are stored at specific domain \"NGW\". " +"NextGIS Web supported metadata are strings and numbers. Metadata keys " +"with decimal numbers will have suffix **.d** and for real numbers - " +"**.f**. To create new metadata item, add new key=value pair in NGW domain" +" using the *SetMetadataItem* function and appropriate suffix. During " +"transferring to NextGIS Web, suffix will be omitted. You must ensure that" +" numbers correctly transform from string to number." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:298 +msgid "" +"Vector layer field properties (alias, identifier, label field, grid " +"visibility) map to layer metadata the following way:" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:301 +msgid "field alias -> FIELD_{field number}_ALIAS (for example FIELD_0_ALIAS)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:302 +msgid "identifier -> FIELD_{field number}_ID (for example FIELD_0_ID)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:303 +msgid "" +"label field -> FIELD_{field number}_LABEL_FIELD (for example " +"FIELD_0_LABEL_FIELD)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:305 +msgid "" +"grid visibility -> FIELD_{field number}_GRID_VISIBILITY (for example " +"FIELD_0_GRID_VISIBILITY)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:308 +msgid "" +"Starting from GDAL 3.3 field alias can be set/get via " +"`SetAlternativeName` and `GetAlternativeNameRef`." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:312 +#: ../../source/drivers/vector/vfk.rst:152 +msgid "Filters" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:314 +msgid "" +"Vector and PostGIS layers support SetIgnoredFields method. When this " +"method executes any cached features will be freed." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:317 +msgid "" +"Vector and PostGIS layers support SetAttributeFilter and SetSpatialFilter" +" methods. The attribute filter will evaluate at server side if condition " +"is one of following comparison operators:" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:321 +msgid "greater (>)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:322 +msgid "lower (<)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:323 +msgid "greater or equal (>=)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:324 +msgid "lower or equal (<=)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:325 +msgid "equal (=)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:326 +msgid "not equal (!=)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:327 +msgid "LIKE SQL statement (for strings compare)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:328 +msgid "ILIKE SQL statement (for strings compare)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:330 +msgid "" +"Also only AND operator without brackets supported between comparison. For" +" example," +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:340 +msgid "In other cases attribute filter will evaluate on client side." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:342 +msgid "You can set attribute filter using NextGIS Web native format. For example," +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:349 +msgid "" +"Don't forget to add 'NGW:' perefix to where clause and 'fld\\_' prefix to" +" field name." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:352 +msgid "" +"Dataset supports ExecuteSQL method. Only the following queries are " +"supported:" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:355 +msgid "DELLAYER: layer_name; - delete layer with layer_name." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:356 +msgid "DELETE FROM layer_name; - delete any features from layer with layer_name." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:358 +msgid "DROP TABLE layer_name; - delete layer with layer_name." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:359 +msgid "ALTER TABLE src_layer RENAME TO dst_layer; - rename layer." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:360 +msgid "" +"SELECT field_1,field_2 FROM src_layer WHERE field_1 = 'Value 1' AND " +"field_2 = 'Value 2';" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:363 +msgid "" +"In SELECT statement field list or asterisk can be provided. The WHERE " +"clause has same limitations as SetAttributeFilter method input." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:369 +msgid "Read datasource contents (1730 is resource group identifier):" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:375 +msgid "" +"Read layer details (`1730` is resource group identifier, `Parks` is " +"vecror layer name):" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:382 +msgid "" +"Creating and populating a vector layer from a shapefile in existing " +"resource group with identifier 1730. New vector layer name will be \"some" +" new name\":" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:390 +msgid "" +"The `-update` key is mandatory, otherwise the destination datasource will" +" silently delete. The `-t_srs EPSG:3857` key is mandatory because vector " +"layers spatial reference in NextGIS Web can be only in EPSG:3857." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:395 +msgid "" +"The `-doo \"BATCH_SIZE=100\"` key is recommended for speed up feature " +"transferring." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:397 +msgid "" +"Creating and populating a vector layer from a shapefile in new resource " +"group with name \"new group\" and parent identifier 1730. New vector " +"layer name will be \"some new name\":" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:408 +msgid ":ref:`Raster side of the driver <raster.ngw>`" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:409 +msgid "" +"`NextGIS Web documentation " +"<https://docs.nextgis.com/docs_ngweb/source/toc.html>`__" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:411 +msgid "" +"`NextGIS Web for developers " +"<https://docs.nextgis.com/docs_ngweb_dev/doc/toc.html>`__" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:10 +msgid "" +"The National Transfer Format, mostly used by the UK Ordnance Survey, is " +"supported for read access." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:13 +msgid "" +"This driver treats a directory as a dataset and attempts to merge all the" +" .NTF files in the directory, producing a layer for each type of feature " +"(but generally not for each source file). Thus a directory containing " +"several Landline files will have three layers (LANDLINE_POINT, " +"LANDLINE_LINE and LANDLINE_NAME) regardless of the number of landline " +"files." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:20 +msgid "" +"NTF features are always returned with the British National Grid " +"coordinate system. This may be inappropriate for NTF files written by " +"organizations other than the UK Ordnance Survey." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:34 +msgid "" +"`General UK NTF Information " +"<https://web.archive.org/web/20130730111701/http://home.gdal.org/projects/ntf/index.html>`__" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:38 +msgid "Implementation Notes" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:41 +msgid "Products (and Layers) Supported" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:104 +msgid "" +"The dataset as a whole will also have a FEATURE_CLASSES layer containing " +"a pure table relating FEAT_CODE numbers with feature class names " +"(FC_NAME). This applies to all products in the dataset. A few layer types" +" (such as the Code Point, and Address Point products) don't include " +"feature classes. Some products use features classes that are not defined " +"in the file, and so they will not appear in the FEATURE_CLASSES layer." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:112 +msgid "Product Schemas" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:114 +msgid "" +"The approach taken in this reader is to treat one file, or a directory of" +" files as a single dataset. All files in the dataset are scanned on open." +" For each particular product (listed above) a set of layers are created; " +"however, these layers may be extracted from several files of the same " +"product." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:120 +msgid "" +"The layers are based on a low level feature type in the NTF file, but " +"will generally contain features of many different feature codes " +"(FEAT_CODE attribute). Different features within a given layer may have a" +" variety of attributes in the file; however, the schema is established " +"based on the union of all attributes possible within features of a " +"particular type (i.e. POINT) of that product family (i.e. OSCAR Network)." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:128 +msgid "" +"If an NTF product is read that doesn't match one of the known schema's it" +" will go through a different generic handler which has only layers of " +"type GENERIC_POINT and GENERIC_LINE. The features only have a FEAT_CODE " +"attribute." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:133 +msgid "" +"Details of what layers of what products have what attributes can be found" +" in the NTFFileReader::EstablishLayers() method at the end of " +"ntf_estlayers.cpp. This file also contains all the product specific " +"translation code." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:139 +msgid "Special Attributes" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:180 +msgid "Generic Products" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:182 +msgid "" +"In situations where a file is not identified as being part of an existing" +" known product it will be treated generically. In this case the entire " +"dataset is scanned to establish what features have what attributes. " +"Because of this, opening a generic dataset can be much slower than " +"opening a recognised dataset. Based on this scan a list of generic " +"features (layers) are defined from the following set:" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:199 +msgid "" +"Generic products are primarily handled by the ntf_generic.cpp module " +"whereas specific products are handled in ntf_estlayers.cpp." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:202 +msgid "" +"Because some data products (OSNI datasets) not from the Ordnance Survey " +"were found to have record groups in unusual orders compared to what the " +"UK Ordnance Survey does, it was found necessary to cache all the records " +"of level 3 and higher generic products, and construct record groups by id" +" reference from within this cache rather than depending on convenient " +"record orderings. This is accomplished by the NTFFileReader \"indexing\" " +"capability near the bottom of ntffilereader.cpp. Because of this in " +"memory indexing accessing generic datasets can be much more memory " +"intensive than accessing known data products, though it isn't necessary " +"for generic level 1 and 2 products." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:213 +msgid "" +"It is possible to force a known product to be treated as generic by " +"setting the FORCE_GENERIC option to \"ON\" using " +"OGRNTFDataSource::SetOptionsList() as is demonstrated in ntfdump.cpp. " +"This may also be accomplished from outside OGR applications by setting " +"the OGR_NTF_OPTIONS environment variable to \"FORCE_GENERIC=ON\"." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:8 +msgid "OAPIF" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:12 +msgid "" +"This driver can connect to a OGC API - Features service. It assumes that " +"the service supports OpenAPI 3.0/JSON/GeoJSON encoding for respectively " +"API description, feature collection metadata and feature collection data." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:18 +msgid "" +"In versions prior to GDAL 3.1, this driver was called the WFS3 driver, " +"and only supported draft versions of the specification." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:29 +msgid "" +"The syntax to open a OGC API - Features datasource is : " +"*OAPIF:http://path/to/OAPIF/endpoint*" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:32 +msgid "where endpoint is the landing page or a the path to collections/{id}." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:34 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if OAPIF`` option to command " +"line utilities accepting it, or ``OAPIF`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed URL without the ``OAPIF:`` prefix." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:40 +msgid "Layer schema" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:42 +msgid "" +"OGR needs a fixed schema per layer, but OGC API - Features Core doesn't " +"impose fixed schema. The driver will use the XML schema or JSON schema " +"pointed by the \"describedby\" relationship of a collection, if it " +"exists. The driver will also retrieve the first page of features (using " +"the selected page) and establish a schema from this." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:53 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server. In OGC API - Features Core, only a subset of attributes " +"allowed by the server can be queried for equalities, potentially combined" +" with a AND logical operator. More complex requests will be partly or " +"completely evaluated on client-side." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:59 +msgid "Rectangular spatial filtering is forward to the server as well." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:64 +msgid "" +"Starting with GDAL 3.7, the driver supports the `OGC API - Features - " +"Part 2: Coordinate Reference Systems by Reference " +"<https://docs.ogc.org/is/18-058/18-058.html>`__ extension. If a server " +"reports a storageCRS property, that property will be used to set the CRS " +"of the OGR layer. Otherwise the default will be OGC:CRS84 (WGS84 " +"longitude, latitude). As most all OGR drivers, the OAPIF driver will " +"report the SRS and geometries, and expect spatial filters, in the \"GIS-" +"friendly\" order, with longitude/easting first (X component), " +"latitude/northing second (Y component), potentially overriding the axis " +"order of the authority." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:74 +msgid "" +"The CRS of layers can also be controlled with the :oo:`CRS` or " +":oo:`PREFERRED_CRS` open options documented below." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:115 +msgid "" +"Set to YES to ignore the XML Schema or JSON schema that may be offered by" +" the server." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:147 +msgid "Listing the types of a OGC API - Features server :" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:157 +msgid "Listing the summary information of a OGC API - Features layer :" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:211 +msgid "" +"Filtering on a property (depending on if the server exposes filtering " +"capabilities of the properties, part or totally of the filter might be " +"evaluated on client side)" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:244 +#: ../../source/drivers/vector/openfilegdb.rst:40 +#: ../../source/drivers/vector/osm.rst:179 +msgid "Spatial filtering" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:279 +msgid "" +"`\"OGC API - Features - Part 1: Core\" Standard " +"<http://docs.opengeospatial.org/is/17-069r3/17-069r3.html>`__" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:281 +msgid "" +"`\"OGC API - Features - Part 2: Coordinate Reference Systems by " +"Reference\" Standard <https://docs.ogc.org/is/18-058/18-058.html>`__" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:283 +msgid ":ref:`WFS (1.0,1.1,2.0) driver documentation <vector.wfs>`" +msgstr "" + +#: ../../source/drivers/vector/oci.rst:6 +msgid "OCI" +msgstr "" + +#: ../../source/drivers/vector/oci.rst:10 +msgid "" +"This driver supports reading and writing data in Oracle Spatial (8.1.7 or" +" later) Object-Relational format. The Oracle Spatial driver is not " +"normally built into OGR, but may be built in on platforms where the " +"Oracle client libraries are available." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:15 +#, python-format +msgid "" +"When opening a database, its name should be specified in the form " +"\"OCI:userid/password@database_instance:table,table\". The list of tables" +" is optional. The database_instance portion may be omitted when accessing" +" the default local database instance. See the `Oracle Help Center " +"<https://docs.oracle.com/search/?q=oci%20driver>`_ for more information " +"about the OCI driver." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:22 +msgid "" +"If the list of tables is not provided, then all tables appearing in " +"ALL_SDO_GEOM_METADATA will be treated by OGR as layers with the table " +"names as the layer names. Non-spatial tables or spatial tables not listed" +" in the ALL_SDO_GEOM_METADATA view [#]_ are not accessible unless " +"explicitly listed in the datasource name. Even in databases where all " +"desired layers are in the ALL_SDO_GEOM_METADATA view, it may be desirable" +" to list only the tables to be used as this can substantially reduce " +"initialization time in databases with many tables." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:31 +msgid "" +"If the table has an integer column called OGR_FID it will be used as the " +"feature id by OGR (and it will not appear as a regular attribute). When " +"loading data into Oracle Spatial OGR will always create the OGR_FID " +"field." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:36 +msgid "" +"When reading data from one or more views, the view names should be " +"specified in the form " +"\"OCI:userid/password@database_instance:view,view\". What is written " +"above regarding tables, applies to views as well." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:41 +msgid "" +"It is the database user that is responsible for updating the " +"ALL_SDO_GEOM_METADATA view, by inserting an appropriate row into the " +"USER_SDO_GEOM_METADATA view. This is why it is possible that the table " +"you want to read from is not listed in the ALL_SDO_GEOM_METADATA." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:55 +msgid "SQL Issues" +msgstr "" + +#: ../../source/drivers/vector/oci.rst:57 +msgid "" +"By default, the Oracle driver passes SQL statements directly to Oracle " +"rather than evaluating them internally when using the ExecuteSQL() call " +"on the OGRDataSource, or the -sql command option to ogr2ogr. Attribute " +"query expressions are also passed through to Oracle." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:62 +msgid "" +"As well two special commands are supported via the ExecuteSQL() " +"interface. These are \"**DELLAYER:<table_name>**\" to delete a layer, and" +" \"**VALLAYER:<table_name>**\" to apply the SDO_GEOM.VALIDATE_GEOMETRY() " +"check to a layer. Internally these pseudo-commands are translated into " +"more complex SQL commands for Oracle." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:68 +msgid "" +"It is also possible to request the driver to handle SQL commands with " +":ref:`OGR SQL <ogr_sql_dialect>` engine, by passing **\"OGRSQL\"** string" +" to the ExecuteSQL() method, as name of the SQL dialect." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:75 +msgid "" +"The type recognition logic is currently somewhat impoverished. No effort " +"is made to preserve real width information for integer and real fields." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:78 +msgid "" +"Various types such as objects, and BLOBs in Oracle will be completely " +"ignored by OGR." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:80 +msgid "" +"Currently the OGR transaction semantics are not properly mapped onto " +"transaction semantics in Oracle." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:82 +msgid "" +"If an attribute called OGR_FID exists in the schema for tables being " +"read, it will be used as the FID. Random (FID based) reads on tables " +"without an identified (and indexed) FID field can be very slow. To force " +"use of a particular field name the :config:`OCI_FID` configuration option" +" (e.g. environment variable) can be set to the target field name." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:88 +msgid "" +"Curved geometry types are converted to linestrings or linear rings in six" +" degree segments when reading. The driver has no support for writing " +"curved geometries." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:91 +msgid "" +"There is no support for point cloud (SDO_PC), TIN (SDO_TIN) and " +"annotation text data types in Oracle Spatial." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:93 +msgid "" +"It might be necessary to define the environment variable NLS_LANG to " +"\"American_America.UTF8\" to avoid issues with floating point numbers " +"being truncated to integer on non-English environments." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:96 +msgid "" +"For developers: when running the driver under the memory error detection " +"tool Valgrind, specifying the database_instance, typically to localhost, " +"or with the TWO_TASK environment variable seems to be compulsory, " +"otherwise \"TNS:permission denied\" errors will be reported)" +msgstr "" + +#: ../../source/drivers/vector/oci.rst:101 +msgid "" +"The logic for finding the specified table or view first checks whether a " +"table with the given name exists, then a view, and then tries again with " +"quoted names. This may result in one or more errors of the following type" +" written to the output: \"ORA-04043: object <object_name> does not " +"exist\", even if the object actually is found later on." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:111 +msgid "" +"The Oracle Spatial driver does not support creation of new datasets " +"(database instances), but it does allow creation of new layers within an " +"existing database." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:115 +msgid "" +"Upon closing the OGRDataSource newly created layers will have a spatial " +"index automatically built. At this point the USER_SDO_GEOM_METADATA table" +" will also be updated with bounds for the table based on the features " +"that have actually been written. One consequence of this is that once a " +"layer has been loaded it is generally not possible to load additional " +"features outside the original extents without manually modifying the " +"DIMINFO information in USER_SDO_GEOM_METADATA and rebuilding the spatial " +"index." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:292 +msgid "Layer Open Options" +msgstr "" + +#: ../../source/drivers/vector/oci.rst:316 +msgid "" +"Simple translation of a shapefile into Oracle. The table 'ABC' will be " +"created with the features from abc.shp and attributes from abc.dbf." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:323 +#: ../../source/drivers/vector/pg.rst:490 +msgid "" +"This second example loads a political boundaries layer from VPF (via the " +":ref:`OGDI driver <vector.ogdi>`), and renames the layer from the cryptic" +" OGDI layer name to something more sensible. If an existing table of the " +"desired name exists it is overwritten." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:334 +msgid "" +"This example shows using ogrinfo to evaluate an SQL query statement " +"within Oracle. More sophisticated Oracle Spatial specific queries may " +"also be used via the -sql commandline switch to ogrinfo." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:342 +msgid "This example shows hows to list information about an Oracle view." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:348 +msgid "" +"This example shows hows to convert certain columns from an Oracle view to" +" a GeoPackage file, explicitly assigning the layer name and the " +"coordinate reference system, and converting timestamps to UTC." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:359 +msgid "" +"I would like to thank `SRC, LLC <http://www.extendthereach.com/>`__ for " +"its financial support of the development of this driver." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:4 +msgid "Open Design Alliance - ODA Platform" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:6 +msgid "" +"ODA Platform (previously named Teigha) is required to enable GDAL support" +" for reading AutoCAD DWG and Microstation DGN v8 files. GDAL/OGR must be " +"built with ODA support in order to enable these drivers." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:10 +msgid "ODA required products" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:12 +msgid "" +"ODA Platform includes several SDK. Drawings SDK provides access to all " +"data in .dwg and .dgn through an object-oriented API. It is required to " +"compile GDAL. Since Kernel SDK is required by all products, these two " +"products must be downloaded:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:15 +msgid "Kernel" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:16 +msgid "Drawings" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:18 +msgid "" +"These libraries are not publicly available. You have to became a member " +"to get access to the libraries. Upon authentication the libraries are " +"available from: `ODA Member Downloads " +"<https://www.opendesign.com/members/memberfiles>`__" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:23 +msgid "Get the libraries" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:25 +msgid "" +"To selected the appropriate files to download, consider the following ODA" +" name conventions (for Linux):" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:27 +msgid "lnx - Linux" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:28 +msgid "X86, X64 - indicates X86 or X64 platform" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:29 +msgid "4.4, 4.7, 4.8, 4.9, 5.2, 5.3, 6.3, 7.2, 8.3 - GCC versions" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:30 +msgid "dll - indicates a shared library version" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:31 +msgid "pic - compiled with Position Independent Code option" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:33 +msgid "" +"ODA archives also contains a release suffix in order to distinguish " +"between releases, like 21.2 or 21.6." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:35 +msgid "" +"To download the required files for Linux, the following files could be " +"downloaded:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:37 +msgid "`Kernel_lnxX64_7.2dll_21.6.tar.gz`" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:38 +msgid "`Drawings_lnxX64_7.2dll_21.6.tar.gz`" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:40 +msgid "In this example, the files names are:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:42 +msgid "`lnx` for Linux" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:43 +msgid "`X64` for X64 architecture" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:44 +msgid "`7.2` for gcc 7.2" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:45 +msgid "`dll` for shared library version" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:46 +msgid "`21.6` ODA 2021 release, build 6" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:49 +msgid "Compiling the libraries" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:51 +msgid "The libraries must be merged before compiling." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:60 +msgid "" +"To compile, an activation key is required. It can be requested from ODA " +"Products Activation. The activation key must be copied to " +"`ThirdParty/activation/`." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:67 +msgid "Compile the ODA libraries with:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:75 +msgid "" +"Make sure your gcc major version matches ODA libs gcc version. On Ubuntu," +" for example, you can install different gcc/g++ versions, like 7, 8 and " +"9. Switch between them with:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:83 +msgid "ODA libraries path" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:85 +msgid "" +"After compiling ODA, the resulting libs are in a non standard search " +"path. There is no `make install` included to copy the libraries to a " +"standard location. This might be an issue." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:89 +msgid "" +"You have different alternative options to compile and run GDAL/OGR with " +"ODA:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:91 +msgid "copy the ODA libraries to a standard location" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:92 +msgid "" +"set LD_LIBRARY_PATH (like " +"`LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/jgr/dev/cpp/ODA21.6/base_7.2/bin/lnxX64_7.2dll`)." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:93 +msgid "" +"Adding ODA folder to the system library path (`echo " +"\"/home/jgr/dev/cpp/ODA21.6/base_7.2/bin/lnxX64_7.2dll\" | sudo tee -a " +"/etc/ld.so.conf.d/z_gdal-ODA.conf`)" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:94 +msgid "" +"Setting a run time path (`rpath`) when compiling GDAL (like " +"`LDFLAGS=\"-Wl,-rpath=/home/jgr/dev/cpp/ODA21.6/base_7.2/bin/lnxX64_7.2dll\"`)." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:97 +msgid "ODA library names" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:99 +msgid "" +"Some ODA library names do not conform the usual Linux standard `lib*.so`." +" If you don't use `rpath`, for the other alternatives listed above, you " +"might have to create symbolic links from the actual names. Example:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:111 +msgid "Check with `ldconfig -v` if all ODA libraries are now visible." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:115 +msgid "Compiling GDAL" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:117 +msgid "" +"After compiling ODA libraries, GDAL can be build using two additional " +"options:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:119 +msgid "`--with-teigha=/home/jgr/dev/cpp/ODA21.6/base_7.2`" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:120 +msgid "`--with-teigha-plt=lnxX64_7.2dll`" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:122 +msgid "" +"The value of `--with-teigha` is the full path of the folder where the " +"libraries were merged and compiled." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:124 +msgid "" +"The value of `--with-teigha-plt` must match the platform name used by " +"ODA. The platform name is the folder name under `Platforms`:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:132 +msgid "GDAL compilation" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:134 +msgid "" +"Use your own GDAL build configuration and add the previous mentioned " +"options. After running `configure`, make sure that `Teigha (DWG and " +"DGNv8)` support is configured." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:136 +msgid "As an example, compiling GDAL can be:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:151 +msgid "" +"We added `LDFLAGS=\"-L/usr/lib/x86_64-linux-gnu\"` to use system libs " +"over ODA's `libpcre`, `libcurl`, etc." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:154 +msgid "Testing" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:156 +msgid "" +"After compiling GDAL, you can check if the new drivers `DGNV8` and `DWG` " +"are supported with:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:167 +msgid "" +"If a file is DGNv8, you will see that driver in action when opening the " +"file:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:177 +msgid "Troubleshooting" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:179 +msgid "" +"If you find linking errors, you can set `LD_LIBRARY_PATH` or `LDFLAGS` " +"environment variables to make sure you are able to get the ODA libraries " +"from their location." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:181 +msgid "Use `ldconfig -v` to check if ODA's library folder is listed." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:183 +msgid "For example, you can try:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:190 +msgid "You can force a run time location (with `rpath`) with:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:197 +msgid "Adjust these settings, according to your build environment." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:202 +msgid "`Introducing the ODA Platform <https://www.opendesign.com/products>`__" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:203 +msgid ":ref:`AutoCAD DWG <vector.dwg>`" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:204 +msgid ":ref:`Microstation DGN v8 <vector.dgnv8>`" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:6 +msgid "ODBC" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:10 +msgid "" +"OGR optionally supports spatial and non-spatial tables accessed via ODBC." +" ODBC is a generic access layer for access to many database systems, and " +"data that can be represented as a database (collection of tables). ODBC " +"support is potentially available on Unix and Windows platforms, but is " +"only included in unix builds by special configuration options." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:17 +msgid "" +"ODBC datasources are accessed using a datasource name of the form " +"**ODBC:\\ userid/password\\ @\\ dsn,\\ " +"schema.tablename(geometrycolname),...:srs_tablename(sridcolumn,srtextcolumn)**." +" With optional items dropped the following are also acceptable:" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:21 +msgid "**ODBC:\\ userid/password\\ @\\ dsn**" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:22 +msgid "**ODBC:\\ userid\\ @\\ dsn,\\ table_list**" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:23 +msgid "**ODBC:\\ dsn,\\ table_list**" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:24 +msgid "**ODBC:\\ dsn**" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:25 +msgid "**ODBC:\\ dsn,\\ table_list:srs_tablename**" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:27 +msgid "" +"The **dsn** is the ODBC Data Source Name. Normally ODBC datasources are " +"setup using an ODBC Administration tool, and assigned a DSN. That DSN is " +"what is used to access the datasource." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:31 +msgid "" +"By default the ODBC searches for GEOMETRY_COLUMNS table. If found it is " +"used to identify the set of spatial tables that should be treated as " +"layers by OGR. If not found, then all tables in the datasource are " +"returned as non-spatial layers. However, if a table list (a list of comma" +" separated table names) is provided, then only those tables will be " +"represented as layers (non-spatial). Fetching the full definition of all " +"tables in a complicated database can be quite time consuming, so the " +"ability to restrict the set of tables accessed is primarily a performance" +" issue." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:41 +msgid "" +"If the GEOMETRY_COLUMNS table is found, it is used to select a column to " +"be the geometry source. If the tables are passed in the datasource name, " +"then the geometry column associated with a table can be included in round" +" brackets after the tablename. It is currently a hardcoded assumption " +"that the geometry is in Well Known Binary (WKB) format if the field is " +"binary, or Well Known Text (WKT) otherwise. The GEOMETRY_COLUMNS table " +"should have at least the columns F_TABLE_NAME, F_GEOMETRY_COLUMN and " +"GEOMETRY_TYPE." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:50 +msgid "" +"If the table has a geometry column, and has fields called XMIN, YMIN, " +"XMAX and YMAX then direct table queries with a spatial filter accelerate " +"the spatial query. The XMIN, YMIN, XMAX and YMAX fields should represent " +"the extent of the geometry in the row in the tables coordinate system." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:55 +msgid "" +"By default, SQL statements are passed directly to the underlying database" +" engine. It's also possible to request the driver to handle SQL commands " +"with the :ref:`OGR SQL <ogr_sql_dialect>` engine, by passing " +"**\"OGRSQL\"** string to the ExecuteSQL() method, as name of the SQL " +"dialect." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:83 +msgid "Access Databases (.MDB) support" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:85 +msgid "" +"On Windows provided that the \"Microsoft Access Driver (\\*.mdb)\" ODBC " +"driver is installed, non-spatial MS Access Databases (not Personal " +"Geodabases or Geomedia databases) can be opened directly by their " +"filenames." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:90 +msgid "" +"On Linux opening non-spatial MS Access Databases using the ODBC driver is" +" possible via installation of unixODBC and mdbtools. See :ref:`MDB " +"<vector.pgeo>` for instructions on how to enable this." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:94 +msgid "" +"The driver supports either .mdb or .accdb extensions for Microsoft Access" +" databases. Additionally, it also supports opening files with the ESRI " +".style database extension (which is just an alias for the .mdb file " +"extension)." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:102 +msgid "" +"Currently the ODBC OGR driver is read-only, so new features, tables and " +"datasources cannot normally be created by OGR applications. This " +"limitation may be removed in the future." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:109 +msgid "" +"`MSDN ODBC API Reference <http://msdn.microsoft.com/en-" +"us/library/ms714562(VS.85).aspx>`__" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:111 +msgid ":ref:`PGeo driver <vector.pgeo>`" +msgstr "" + +#: ../../source/drivers/vector/ods.rst:4 +msgid "ODS - Open Document Spreadsheet" +msgstr "" + +#: ../../source/drivers/vector/ods.rst:6 +msgid "ODS" +msgstr "" + +#: ../../source/drivers/vector/ods.rst:10 +msgid "" +"This driver can read, write and update spreadsheets in Open Document " +"Spreadsheet format, used by applications like OpenOffice / LibreOffice / " +"KSpread / etc..." +msgstr "" + +#: ../../source/drivers/vector/ods.rst:17 +#: ../../source/drivers/vector/xls.rst:16 +#: ../../source/drivers/vector/xlsx.rst:19 +msgid "" +"Each sheet is presented as a OGR layer. No geometry support is available " +"directly (but you may use the OGR VRT capabilities for that)." +msgstr "" + +#: ../../source/drivers/vector/ods.rst:20 +msgid "Note 1 : spreadsheets with passwords are not supported." +msgstr "" + +#: ../../source/drivers/vector/ods.rst:22 +msgid "" +"Note 2 : when updating an existing document, all existing styles, " +"formatting, formulas and other concepts (charts, drawings, macros, ...) " +"not understood by OGR will be lost : the document is re-written from " +"scratch from the OGR data model." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:6 +msgid "OGDI" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:10 +msgid "" +"OGDI vector support is optional in OGR, and is normally only configured " +"if OGDI is installed on the build system. If available OGDI vectors are " +"supported for read access for the following family types:" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:15 +msgid "Line" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:16 +msgid "Area" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:17 +msgid "" +"Text (Currently returned as points with the text in the \"text\" " +"attribute)" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:20 +msgid "OGDI can (among other formats) read VPF products, such as DCW and VMAP." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:22 +msgid "" +"If an OGDI gltp url is opened directly the OGDI 3.1 capabilities for the " +"driver/server are queried to get a list of layers. One OGR layer is " +"created for each OGDI family available for each layer in the datastore. " +"For drivers such as VRF this can result in a lot of layers. Each of the " +"layers has an OGR name based on the OGDI name plus an underscore and the " +"family name. For instance a layer might be called " +"**watrcrsl@hydro(*)_line** if coming out of the VRF driver. (layer names " +"can be simplified with :config:`OGR_OGDI_LAUNDER_LAYER_NAMES=YES`)" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:31 +msgid "" +"Alternatively to accessing all the layers in a datastore, it is possible " +"to open a particular layer using a customized filename consisting of the " +"regular GLTP URL to which you append the layer name and family type " +"(separated by colons). This mechanism must be used to access layers of " +"pre OGDI 3.1 drivers as before OGDI 3.1 there was no regular way to " +"discover available layers in OGDI." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:42 +msgid "" +"Where <layer_name> is the OGDI Layer name, and <family> is one of: " +"\"line\", \"area\", \"point\", or \"text\"." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:45 +msgid "" +"OGDI coordinate system information is supported for most coordinate " +"systems. A warning will be produced when a layer is opened if the " +"coordinate system cannot be translated." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:49 +msgid "There is no update or creation support in the OGDI driver." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:57 +msgid "Error handling" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:59 +msgid "" +"Starting with GDAL 2.2 and OGDI > 3.2.0beta2, if the OGDI_STOP_ON_ERROR " +"environment variable is set to NO, some errors can be gracefully " +"recovered by OGDI (in VPF driver). They will still be caught by GDAL and " +"emitted as regular GDAL errors." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:64 +msgid "" +"Note: be aware that this is a work in progress. Not all recoverable " +"errors can be recovered, and some errors might be recovered silently." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:84 +msgid "Usage example 'ogrinfo':" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:90 +msgid "" +"In the dataset name 'gltp:/vrf/usr4/mpp1/v0eur/vmaplv0/eurnasia' the " +"gltp:/vrf part is not really in the filesystem, but has to be added. The " +"VPF data was at /usr4/mpp1/v0eur/. The 'eurnasia' directory should be at " +"the same level as the dht. and lat. files. The 'hydro' reference is a " +"subdirectory of 'eurnasia/' where watrcrsl.\\* is found." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:96 +msgid "Usage examples VMAP0 to SHAPE conversion with 'ogr2ogr':" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:103 +msgid "" +"An OGR SQL query against a VMAP dataset. Again, note the careful quoting " +"of the layer name." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:114 +msgid "`OGDI.SourceForge.Net <http://ogdi.sourceforge.net/>`__" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:115 +msgid "`VMap0 Coverages <http://www.terragear.org/docs/vmap0/coverage.html>`__" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:10 +msgid "" +"The OpenFileGDB driver provides read, write and update access to vector " +"layers of File Geodatabases (.gdb directories) created by ArcGIS 10 and " +"above (it has also read-only support for ArcGIS 9.x geodatabases). The " +"dataset name must be the directory/folder name, and it must end with the " +".gdb extension." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:19 +msgid "" +"A specific .gdbtable file (including \"system\" tables) can also be " +"opened directly." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:22 +msgid "Curve in geometries are supported with GDAL >= 2.2." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:24 +msgid "Write and update capabilities are supported since GDAL >= 3.6" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:26 +msgid "" +"The driver also supports :ref:`raster layers<raster.openfilegdb>` since " +"GDAL 3.7" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:33 +msgid "3.6" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:42 +msgid "" +"Since GDAL 3.2, the driver can use the native .spx spatial indices for " +"spatial filtering." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:45 +msgid "" +"In earlier versions, it uses the minimum bounding rectangle included at " +"the beginning of the geometry blobs to speed up spatial filtering. By " +"default, it also builds on the fly a in-memory spatial index during the " +"first sequential read of a layer. Following spatial filtering operations " +"on that layer will then benefit from that spatial index. The building of " +"this in-memory spatial index can be disabled by setting the " +":config:`OPENFILEGDB_IN_MEMORY_SPI` configuration option to NO." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:56 +msgid "" +"SQL statements are run through the OGR SQL engine. When attribute indexes" +" (.atx files) exist, the driver will use them to speed up WHERE clauses " +"or SetAttributeFilter() calls." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:63 +msgid "" +"\"GetLayerDefinition a_layer_name\" and \"GetLayerMetadata a_layer_name\"" +" can be used as special SQL requests to get respectively the definition " +"and metadata of a FileGDB table as XML content (only available in " +"Geodatabases created with ArcGIS 10 or above)" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:68 +msgid "" +"The \"CREATE INDEX idx_name ON layer_name(field_name)\" SQL request can " +"be used to create an attribute index. idx_name must have 16 characters or" +" less, start with a letter and contain only alphanumeric characters or " +"underscore." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:72 +msgid "" +"The \"RECOMPUTE EXTENT ON layer_name\" SQL request can be used to trigger" +" an update of the layer extent in layer metadata. This is useful when " +"updating or deleting features that modify the general layer extent." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:76 +msgid "" +"The \"REPACK\" or \"REPACK layer_name\" SQL requests can be used " +"respectively to compact the whole database or a given layer. This is " +"useful when doing editions (updates or feature deletions) that may leave " +"holes in .gdbtable files. The REPACK command causes the .gdbtable to be " +"rewritten without holes. Note that compaction does not involve extent " +"recomputation." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:149 +msgid "" +"On reading, this information is exposed in the ALIAS_NAME layer metadata " +"item (GDAL >= 3.8)." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:170 +msgid "" +"**XYTOLERANCE, ZTOLERANCE, MTOLERANCE**\\=value: These parameters control" +" the snapping tolerance used for advanced ArcGIS features like network " +"and topology rules. They won't effect any OGR operations, but they will " +"by used by ArcGIS. The units of the parameters are the units of the " +"coordinate reference system." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:181 +msgid "" +"**XORIGIN, YORIGIN, ZORIGIN, MORIGIN, XYSCALE, ZSCALE, ZORIGIN**\\=value:" +" These parameters control the `coordinate precision grid " +"<http://help.arcgis.com/en/sdk/10.0/java_ao_adf/conceptualhelp/engine/index.html#//00010000037m000000>`__" +" inside the file geodatabase. The dimensions of the grid are determined " +"by the origin, and the scale. The origin defines the location of a " +"reference grid point in space. The scale is the reciprocal of the " +"resolution. So, to get a grid with an origin at 0 and a resolution of " +"0.001 on all axes, you would set all the origins to 0 and all the scales " +"to 1000." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:239 +msgid "64-bit integer field support" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:243 +msgid "" +"On creation, 64-bit integer field support requires setting the " +":lco:`TARGET_ARCGIS_VERSION` layer creation option to " +"``ARCGIS_PRO_3_2_OR_LATER``. Note that Esri `recommends " +"<https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview" +"/arcgis-field-data-" +"types.htm#ESRI_SECTION2_8BF2454C879941258DC44AF6BB31F386>`__ to restrict " +"the range of 64-bit integer values to [-9007199254740991, " +"9007199254740991] for the larger compatibility. GDAL will allow writing " +"values outside of that range without warning, and can also read them " +"fine." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:255 +#: ../../source/drivers/vector/pgeo.rst:93 +msgid "Coded and range field domains are supported." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:262 +msgid "Relationship retrieval, creation, deletion and updating is supported." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:269 +msgid "" +"The hierarchical organization of tables and feature classes as top-level " +"element or within a feature dataset can be explored using the methods " +":cpp:func:`GDALDataset::GetRootGroup`, " +":cpp:func:`GDALGroup::GetGroupNames`, :cpp:func:`GDALGroup::OpenGroup`, " +":cpp:func:`GDALGroup::GetVectorLayerNames` and " +":cpp:func:`GDALGroup::OpenVectorLayer`" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:278 +msgid "" +"The driver implements transactions at the database level, through an " +"emulation (as per :ref:`rfc-54`). This works by backing up the current " +"state of the modified parts of a geodatabase after " +"StartTransaction(force=TRUE) is called. If the transaction is committed, " +"the backup copy is destroyed. If the transaction is rolled back, the " +"backup copy is restored." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:314 +msgid "Advantages of the OpenFileGDB driver, compared to the FileGDB driver" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:316 +msgid "Can read ArcGIS 9.X Geodatabases, and not only 10 or above." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:318 +msgid "Can open layers with any spatial reference system." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:320 +msgid "Thread-safe (i.e. datasources can be processed in parallel)." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:322 +msgid "" +"Uses the VSI Virtual File API, enabling the user to read a Geodatabase in" +" a ZIP file or stored on a HTTP server." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:325 +msgid "Faster on databases with a big number of fields." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:327 +msgid "Does not depend on a third-party library." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:329 +msgid "Robust against corrupted Geodatabase files." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:334 +msgid "" +"Reading data compressed in SDC format (Smart Data Compression) or in CDF " +"format (Compressed Data Format) is not supported. For CDF, the " +":ref:`FileGDB driver <vector.filegdb>` can be used." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:338 +msgid "" +"Support for tables with 64-bit OBJECTIDs (which require GDAL >= 3.10), " +"where OBJECTIDs are sparse, is read-only and incomplete. The driver will " +"emit a warning if such situation occurs, and will attribute non-faithful " +"OBJECTIDs." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:346 +msgid "Read layer from FileGDB and load into PostGIS:" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:352 +msgid "Get detailed info for FileGDB:" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:358 +msgid "Get detailed info for a zipped FileGDB:" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:367 +msgid ":ref:`OpenFileGDB raster <raster.openfilegdb>` documentation page" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:368 +msgid ":ref:`FileGDB driver <vector.filegdb>`, relying on the FileGDB API SDK" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:369 +msgid "" +"Reverse-engineered specification of the `FileGDB format " +"<https://github.com/rouault/dump_gdbtable/wiki/FGDB-Spec>`__" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:376 +msgid "" +"Edition/write capabilities of the driver have been funded by the " +"following organizations: Provincie Zuid-Holland, Provincie Gelderland and" +" Gemeente Amsterdam." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:4 +msgid "OSM - OpenStreetMap XML and PBF" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:6 +msgid "OSM" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:10 +msgid "" +"This driver reads OpenStreetMap files, in .osm (XML based) and .pbf " +"(optimized binary) formats." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:13 +msgid "" +"The driver is available if GDAL is built with SQLite support and, for " +".osm XML files, with Expat support." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:16 +msgid "The filenames must end with .osm or .pbf extension." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:18 +msgid "The driver will categorize features into 5 layers :" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:20 +msgid "**points** : \"node\" features that have significant tags attached." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:21 +msgid "**lines** : \"way\" features that are recognized as non-area." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:22 +msgid "" +"**multilinestrings** : \"relation\" features that form a " +"multilinestring(type = 'multilinestring' or type = 'route')." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:24 +msgid "" +"**multipolygons** : \"relation\" features that form a multipolygon (type " +"= 'multipolygon' or type = 'boundary'), and \"way\" features that are " +"recognized as area." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:27 +msgid "" +"**other_relations** : \"relation\" features that do not belong to the " +"above 2 layers." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:38 +#: ../../source/drivers/vector/pgeo.rst:128 +msgid "Configuration" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:40 +msgid "" +"In the *data* folder of the GDAL distribution, you can find an " +":source_file:`ogr/ogrsf_frmts/osm/data/osmconf.ini` file that can be " +"customized to fit your needs. You can also define an alternate path with " +"the :config:`OSM_CONFIG_FILE` configuration option." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:45 +msgid "" +"The customization is essentially which OSM attributes and keys should be " +"translated into OGR layer fields." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:48 +msgid "" +"Fields can be computed with SQL expressions (evaluated by SQLite engine) " +"from other fields/tags. For example to compute the z_order attribute." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:53 +msgid "\"other_tags\" field" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:55 +msgid "" +"When keys are not strictly identified in the *osmconf.ini* file, the " +"key/value pair is appended in a \"other_tags\" field, with a syntax " +"compatible with the PostgreSQL HSTORE type. See the *COLUMN_TYPES* layer " +"creation option of the :ref:`PG driver <vector.pg>`. The " +"``hstore_get_value()`` function can be used with the :ref:`OGRSQL " +"<ogr_sql_dialect>` or :ref:`SQLite <sql_sqlite_dialect>` SQL dialects to " +"extract the value of a given key." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:70 +msgid "" +"Starting with GDAL 3.7, it is possible to ask the format of this field to" +" be JSON encoded, by using the TAGS_FORMAT=JSON open option, or the " +"``tags_format=json`` setting in the *osmconf.ini* file." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:75 +msgid "\"all_tags\" field" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:77 +msgid "" +"Similar to \"other_tags\", except that it contains both keys specifically" +" identified to be reported as dedicated fields, as well as other keys." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:80 +msgid "" +"\"all_tags\" is disabled by default, and when enabled, it is exclusive " +"with \"other_tags\"." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:138 +msgid "Interleaved reading" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:140 +msgid "" +"Due to the nature of OSM files and how the driver works internally, the " +"default reading mode that works per-layer might not work correctly, " +"because too many features will accumulate in the layers before being " +"consumed by the user application." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:145 +msgid "" +"Starting with GDAL 2.2, applications should use the " +"``GDALDataset::GetNextFeature()`` API to iterate over features in the " +"order they are produced." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:149 +msgid "" +"For earlier versions, for large files, applications should set the " +":config:`OGR_INTERLEAVED_READING=YES` configuration option to turn on a " +"special reading mode where the following reading pattern must be used:" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:174 +msgid "" +"Note : the ogr2ogr application has been modified to use that " +":config:`OGR_INTERLEAVED_READING` mode without any particular user " +"action." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:181 +msgid "" +"Due to way .osm or .pbf files are structured and the parsing of the file " +"is done, for efficiency reasons, a spatial filter applied on the points " +"layer will also affect other layers. This may result in lines or polygons" +" that have missing vertices." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:186 +msgid "" +"To improve this, a possibility is using a larger spatial filter with some" +" buffer for the points layer, and then post-process the output to apply " +"the desired filter. This would not work however if a polygon has vertices" +" very far away from the interest area. In which case full conversion of " +"the file to another format, and filtering of the resulting lines or " +"polygons layers would be needed." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:194 +msgid "Reading .osm.bz2 files and/or online files" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:196 +msgid "" +".osm.bz2 are not natively recognized, however you can process them (on " +"Unix), with the following command :" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:203 +msgid "You can convert a .osm or .pbf file without downloading it :" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:215 +msgid "And to combine the above steps :" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:270 +msgid "`OpenStreetMap home page <http://www.openstreetmap.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:271 +msgid "" +"`OSM XML Format description " +"<http://wiki.openstreetmap.org/wiki/OSM_XML>`__" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:273 +msgid "" +"`OSM PBF Format description " +"<http://wiki.openstreetmap.org/wiki/PBF_Format>`__" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:8 +msgid "Parquet" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:12 +msgid "" +"From https://parquet.apache.org/: \"Apache Parquet is an open source, " +"column-oriented data file format designed for efficient data storage and " +"retrieval. It provides efficient data compression and encoding schemes " +"with enhanced performance to handle complex data in bulk. Parquet is " +"available in multiple languages including Java, C++, Python, etc...\"" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:17 +msgid "" +"This driver also supports geometry columns using the GeoParquet " +"specification." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:19 +msgid "" +"The GeoParquet 1.0.0 specification is supported since GDAL 3.8.0. The " +"GeoParquet 1.1.0 specification is supported since GDAL 3.9.0." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:70 +msgid "" +"Compression method. Available values depend on how the Parquet library " +"was compiled. Defaults to SNAPPY when available, otherwise NONE." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:152 +msgid "" +"Note however that enabling this option involves creating a temporary " +"GeoPackage file (in the same directory as the final Parquet file), and " +"thus requires temporary storage (possibly up to several times the size of" +" the final Parquet file, depending on Parquet compression) and additional" +" processing time." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:158 +msgid "" +"The efficiency of spatial filtering depends on the ROW_GROUP_SIZE. If it " +"is too large, too many features that are not spatially close will be " +"grouped together. If it is too small, the file size will increase, and " +"extra processing time will be necessary to browse through the row groups." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:163 +msgid "" +"Note also that when this option is enabled, the Arrow writing API (which " +"is for example triggered when using ogr2ogr to convert from Parquet to " +"Parquet), fallbacks to the generic implementation, which does not support" +" advanced Arrow types (lists, maps, etc.)." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:171 +msgid "" +"SQL statements are run through the OGR SQL engine. Statistics can be used" +" to speed-up evaluations of SQL requests like: \"SELECT MIN(colname), " +"MAX(colname), COUNT(colname) FROM layername\"" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:176 +msgid "Dataset/partitioning read support" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:178 +msgid "" +"Starting with GDAL 3.6.0, the driver can read directories that contain " +"several Parquet files, and expose them as a single layer. This support is" +" only enabled if the driver is built against the ``arrowdataset`` C++ " +"library." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:182 +msgid "" +"It is also possible to force opening single Parquet file in that mode by " +"prefixing their filename with ``PARQUET:``." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:185 +msgid "" +"Optimized spatial and attribute filtering for Arrow datasets is available" +" since GDAL 3.10." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:193 +msgid "" +"Layer metadata can be read and written. It is serialized as JSON content " +"in a ``gdal:metadata`` domain." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:197 +msgid "Multithreading" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:199 +msgid "" +"Starting with GDAL 3.6.0, the driver will use up to 4 threads for reading" +" (or the maximum number of available CPUs returned by " +":cpp:func:`CPLGetNumCPUs()` if it is lower by 4). This number can be " +"configured with the configuration option :config:`GDAL_NUM_THREADS`, " +"which can be set to an integer value or ``ALL_CPUS``." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:206 +msgid "Validation script" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:208 +msgid "" +"The :source_file:`swig/python/gdal-" +"utils/osgeo_utils/samples/validate_geoparquet.py` Python script can be " +"used to check compliance of a Parquet file against the GeoParquet " +"specification." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:212 +msgid "To validate only metadata:" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:219 +msgid "To validate metadata and check content of geometry column(s):" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:239 +msgid "`Apache Parquet home page <https://parquet.apache.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:241 +msgid "`Parquet file format <https://github.com/apache/parquet-format>`__" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:243 +msgid "" +"`GeoParquet specification " +"<https://github.com/opengeospatial/geoparquet>`__" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:245 +msgid "Related driver: :ref:`Arrow driver <vector.arrow>`" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:11 +msgid "" +"Refer to the :ref:`PDF raster <raster.pdf>` documentation page for common" +" documentation of the raster and vector sides of the driver." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:26 +msgid "" +"This driver can read and write geospatial PDF with vector features. " +"Vector read support requires linking to one of the above mentioned " +"dependent libraries, but write support does not. The driver can read " +"vector features encoded according to PDF's logical structure facilities " +"(as described by \"§10.6 - Logical Structure\" of PDF spec), or retrieve " +"only vector geometries for other vector PDF files." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:33 +msgid "" +"If there is no such logical structure, the driver will not try to " +"interpret the vector content of the PDF, unless you defined the " +":config:`OGR_PDF_READ_NON_STRUCTURED` configuration option to YES." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:38 +msgid "Feature style support" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:40 +msgid "" +"For write support, the driver has partial support for the style " +"information attached to features, encoded according to the " +":ref:`ogr_feature_style`." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:44 +msgid "The following tools are recognized:" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:46 +msgid "For points, LABEL and SYMBOL." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:47 +msgid "For lines, PEN." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:48 +msgid "For polygons, PEN and BRUSH." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:50 +msgid "" +"The supported attributes for each tool are summed up in the following " +"table:" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:58 +msgid "Supported attributes" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:62 +msgid "PEN(c:#FF0000,w:5px)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:65 +msgid "BRUSH(fc:#0000FF)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "GDAL >= 2.3.0: text (t), limited to ASCII strings; font name (f), see" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "note below; font size (s); bold (bo); italic (it); text color (c); x and" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "y offsets (dx, dy); angle (a); anchor point (p), values 1 through 9;" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "stretch (w)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "GDAL <= 2.2.x: text (t), limited to ASCII strings; font size (s); text" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "color (c); x and y offsets (dx, dy); angle (a)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:73 +msgid "LABEL(c:#000000,t:\"Hello World!\",s:5g)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:75 +msgid "" +"id (ogr-sym-0 to ogr-sym-9, and filenames for raster symbols); color (c);" +" size (s)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "SYMBOL(c:#00FF00,id:\"ogr- sym-3\",s:10)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "SYMBOL(c:#00000080,id:\"a_symbol.png\")" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:79 +#, python-format +msgid "" +"Alpha values are supported for colors to control the opacity. If not " +"specified, for BRUSH, it is set at 50% opaque." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:82 +msgid "" +"For SYMBOL with a bitmap name, only the alpha value of the color " +"specified with 'c' is taken into account." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:85 +msgid "" +"A font name starting with \"Times\" or containing the string \"Serif\" " +"(case sensitive) will be treated as Times. A font name starting with " +"\"Courier\" or containing the string \"Mono\" (case sensitive) will be " +"treated as Courier. All other font names will be treated as Helvetica." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:106 +msgid ":ref:`PDF raster <raster.pdf>` documentation page" +msgstr "" + +#: ../../source/drivers/vector/pds.rst:4 +msgid "PDS - Planetary Data Systems TABLE" +msgstr "" + +#: ../../source/drivers/vector/pds.rst:10 +msgid "" +"This driver reads TABLE objects from PDS datasets. Note there is a GDAL " +"PDS driver to read the raster IMAGE objects from PDS datasets." +msgstr "" + +#: ../../source/drivers/vector/pds.rst:13 +msgid "" +"The driver must be provided with the product label file (even when the " +"actual data is placed in a separate file)." +msgstr "" + +#: ../../source/drivers/vector/pds.rst:16 +msgid "" +"If the label file contains a *TABLE* object, it will be read as the only " +"layer of the dataset. If no *TABLE* object is found, the driver will look" +" for all objects containing the TABLE string and read each one in a " +"layer." +msgstr "" + +#: ../../source/drivers/vector/pds.rst:21 +msgid "" +"ASCII and BINARY tables are supported. The driver can retrieve the field " +"descriptions from inline COLUMN objects or from a separate file pointed " +"by ^STRUCTURE." +msgstr "" + +#: ../../source/drivers/vector/pds.rst:25 +msgid "" +"If the table has a LONGITUDE and LATITUDE columns of type REAL and with " +"UNIT=DEGREE, they will be used to return POINT geometries." +msgstr "" + +#: ../../source/drivers/vector/pds.rst:36 +msgid "" +"`Description of PDS format <https://pds.jpl.nasa.gov/tools/standards-" +"reference.shtml>`__ (see Annex A.29 from StdRef_20090227_v3.8.pdf)" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:6 +msgid "PostgreSQL" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:10 +msgid "" +"This driver implements support for access to spatial tables in PostgreSQL" +" extended with the `PostGIS <http://postgis.net/>`__ spatial data " +"support. Some support exists in the driver for use with PostgreSQL " +"without PostGIS but with less functionalities." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:15 +msgid "" +"This driver requires a connection to a Postgres database. If you want to " +"prepare a SQL dump to inject it later into a Postgres database, you can " +"instead use the :ref:`PostgreSQL SQL Dump driver <vector.pgdump>`." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:19 +msgid "" +"You can find additional information on the driver in the :ref:`Advanced " +"OGR PostgreSQL driver Information <vector.pg_advanced>` page." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:22 +msgid "" +"Starting with GDAL 3.9, only PostgreSQL >= 9 and PostGIS >= 2 are " +"supported." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:37 +msgid "" +"To connect to a Postgres datasource, use a connection string specifying " +"the database name, with additional parameters as necessary. The PG: " +"prefix is used to mark the name as a postgres connection string." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:43 +msgid "*or*" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:56 +msgid "Starting with GDAL 3.1 also this syntax is supported:" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:63 +msgid "Starting with GDAL 3.4, the URI syntax is also supported" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:70 +msgid "" +"It's also possible to omit the database name and connect to a *default* " +"database, with the same name as the user name." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:72 +msgid "" +"**Note**: We use PQconnectdb() to make the connection. See details from " +"`PostgreSQL libpq documentation <https://www.postgresql.org/docs/12" +"/libpq-connect.html>`__)." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:76 +msgid "Geometry columns" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:78 +msgid "" +"If the *geometry_columns* table exists (i.e. PostGIS is enabled for the " +"accessed database), then all tables and named views listed in the " +"*geometry_columns* table will be treated as OGR layers. Otherwise " +"(PostGIS disabled for the accessed database), all regular user tables and" +" named views will be treated as layers." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:84 +msgid "" +"The driver also supports the `geography " +"<http://postgis.net/docs/manual-1.5/ch04.html#PostGIS_Geography>`__ " +"column type." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:88 +msgid "" +"The driver also supports reading and writing the following non-linear " +"geometry types :CIRCULARSTRING, COMPOUNDCURVE, CURVEPOLYGON, MULTICURVE " +"and MULTISURFACE" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:95 +msgid "" +"The PostgreSQL driver passes SQL statements directly to PostgreSQL by " +"default, rather than evaluating them internally when using the " +"ExecuteSQL() call on the OGRDataSource, or the -sql command option to " +"ogr2ogr. Attribute query expressions are also passed directly through to " +"PostgreSQL. It's also possible to request the ogr Pg driver to handle SQL" +" commands with the :ref:`OGR SQL <ogr_sql_dialect>` engine, by passing " +"**\"OGRSQL\"** string to the ExecuteSQL() method, as the name of the SQL " +"dialect." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:104 +msgid "" +"Note that the PG driver uses PostgreSQL cursors to browse through the " +"result set of a ExecuteSQL() request, and that, at time of writing, " +"PostgreSQL default settings aren't optimized when the result set is small" +" enough to fit in one result page. If you experiment bad performance, " +"specifying the ``PRELUDE_STATEMENTS=SET cursor_tuple_fraction = 1.0;`` " +"open option might help." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:110 +msgid "" +"The PostgreSQL driver in OGR supports the " +"OGRDataSource::StartTransaction(), OGRDataSource::CommitTransaction() and" +" OGRDataSource::RollbackTransaction() calls in the normal SQL sense." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:117 +msgid "" +"The PostgreSQL driver does not support creation of new datasets (a " +"database within PostgreSQL), but it does allow creation of new layers " +"within an existing database." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:121 +msgid "" +"As mentioned above the type system is impoverished, and many OGR types " +"are not appropriately mapped into PostgreSQL." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:124 +msgid "" +"If the database has PostGIS types loaded (i.e. the geometry type), newly " +"created layers will be created with the PostGIS Geometry type. Otherwise " +"they will use OID." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:128 +msgid "" +"By default it is assumed that text being sent to Postgres is in the UTF-8" +" encoding. This is fine for plain ASCII, but can result in errors for " +"extended characters (ASCII 155+, LATIN1, etc). While OGR provides no " +"direct control over this, you can set the PGCLIENTENCODING environment " +"variable to indicate the format being provided. For instance, if your " +"text is LATIN1 you could set the environment variable to LATIN1 before " +"using OGR and input would be assumed to be LATIN1 instead of UTF-8. An " +"alternate way of setting the client encoding is to issue the following " +"SQL command with ExecuteSQL() : \"SET client_encoding TO encoding_name\" " +"where encoding_name is LATIN1, etc. Errors can be caught by enclosing " +"this command with a CPLPushErrorHandler()/CPLPopErrorHandler() pair." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:141 +msgid "Updating existing tables" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:142 +msgid "" +"When data is appended to an existing table (for example, using the " +"``-append`` option in ``ogr2ogr``) the driver will, by default, emit an " +"INSERT statement for each row of data to be added. This may be " +"significantly slower than the COPY-based approach taken when creating a " +"new table, but ensures consistency of unique identifiers if multiple " +"connections are accessing the table simultaneously." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:149 +msgid "" +"If only one connection is accessing the table when data is appended, the " +"COPY-based approach can be chosen by setting the config option " +"``PG_USE_COPY`` to ``YES``, which may significantly speed up the " +"operation." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:407 +msgid "" +"At time of writing, PgPoolII is not compatible with COPY mode as used by " +"the OGR PostgreSQL driver. Thus you should force PG_USE_COPY=NO when " +"using PgPoolII." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:481 +msgid "" +"Simple translation of a shapefile into PostgreSQL. The table 'abc' will " +"be created with the features from abc.shp and attributes from abc.dbf. " +"The database instance (warmerda) must already exist, and the table abc " +"must not already exist." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:501 +msgid "Export a single Postgres table to GeoPackage:" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:509 +msgid "Export many Postgres tables to GeoPackage:" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:517 +msgid "Export a whole Postgres database to GeoPackage:" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:526 +msgid "Load a single layer GeoPackage into Postgres:" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:536 +msgid "" +"In this example we merge tiger line data from two different directories " +"of tiger files into one table. Note that the second invocation uses " +"-append and no :lco:`OVERWRITE=yes`." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:547 +msgid "" +"This example shows using ogrinfo to evaluate an SQL query statement " +"within PostgreSQL. More sophisticated PostGIS specific queries may also " +"be used via the -sql commandline switch to ogrinfo." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:555 +msgid "" +"This example shows using ogrinfo to list PostgreSQL/PostGIS layers on a " +"different host." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:562 +msgid "" +"This example shows use of :oo:`PRELUDE_STATEMENTS` and " +":oo:`CLOSING_STATEMENTS` as destination open options of ogr2ogr." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:570 +msgid "FAQs" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:572 +msgid "" +"**Why can't I see my tables? PostGIS is installed and I have data** You " +"must have permissions on all tables you want to read *and* " +"geometry_columns and spatial_ref_sys. Misleading behavior may follow " +"without an error message if you do not have permissions to these tables. " +"Permission issues on geometry_columns and/or spatial_ref_sys tables can " +"be generally confirmed if you can see the tables by setting the " +"configuration option :config:`PG_LIST_ALL_TABLES` to YES. (e.g. ``ogrinfo" +" --config PG_LIST_ALL_TABLES YES PG:xxxxx``)" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:585 +msgid ":ref:`Advanced OGR PostgreSQL driver Information <vector.pg_advanced>`" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:586 +msgid ":ref:`OGR PostgreSQL SQL Dump driver Page <vector.pgdump>`" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:587 +#: ../../source/drivers/vector/pgdump.rst:286 +msgid "`PostgreSQL Home Page <http://www.postgresql.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:588 +#: ../../source/drivers/vector/pgdump.rst:287 +msgid "`PostGIS <http://postgis.net/>`__" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:589 +#: ../../source/drivers/vector/pgdump.rst:288 +msgid "" +"`PostGIS / OGR Wiki Examples Page " +"<http://trac.osgeo.org/postgis/wiki/UsersWikiOGR>`__" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:4 +msgid "PostgreSQL / PostGIS - Advanced Driver Information" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:6 +msgid "" +"The information collected in that page deal with advanced topics, not " +"found in the :ref:`OGR PostgreSQL driver Information <vector.pg>` page." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:10 +msgid "Connection options related to schemas and tables" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:12 +msgid "" +"The database opening should be significantly faster than in previous " +"versions, so using tables= or schemas= options will not bring further " +"noticeable speed-ups." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:16 +msgid "" +"The set of tables to be scanned can be overridden by specifying " +"*tables=[schema.]table[(geom_column_name)][,[schema2.]table2[(geom_column_name2)],...]*" +" within the connection string. If the parameter is found, the driver " +"skips enumeration of the tables as described in the next paragraph." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:22 +msgid "" +"It is possible to restrict the schemas that will be scanned while " +"establishing the list of tables. This can be done by specifying " +"*schemas=schema_name[,schema_name2]* within the connection string. This " +"can also be a way of speeding up the connection to a PostgreSQL database " +"if there are a lot of schemas. Note that if only one schema is listed, it" +" will also be made automatically the active schema (and the schema name " +"will not prefix the layer name). Otherwise, the active schema is still " +"'public', unless otherwise specified by the *active_schema=* option." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:32 +msgid "" +"The active schema ('public' being the default) can be overridden by " +"specifying *active_schema=schema_name* within the connection string. The " +"active schema is the schema where tables are created or looked for when " +"their name is not explicitly prefixed by a schema name. Note that this " +"does not restrict the tables that will be listed (see *schemas=* option " +"above). When getting the list of tables, the name of the tables within " +"that active schema will not be prefixed by the schema name. For example, " +"if you have a table 'foo' within the public schema, and a table 'foo' " +"within the 'bar_schema' schema, and that you specify " +"active_schema=bar_schema, 2 layers will be listed : 'foo' (implicitly " +"within 'bar_schema') and 'public.foo'." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:45 +msgid "Multiple geometry columns" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:47 +msgid "" +"The PostgreSQL driver supports accessing tables with multiple PostGIS " +"geometry columns." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:50 +msgid "" +"OGR supports reading, updating, creating tables with multiple PostGIS " +"geometry columns (following :ref:`rfc-41`) For such a table, a single OGR" +" layer will be reported with as many geometry fields as there are " +"geometry columns in the table." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:55 +msgid "" +"For backward compatibility, it is also possible to query a layer with " +"GetLayerByName() with a name formatted like 'foo(bar)' where 'foo' is a " +"table and 'bar' a geometry column." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:62 +msgid "" +"Even when PostGIS is enabled, if the user defines the environment " +"variable :config:`PG_LIST_ALL_TABLES=YES` (and does not specify tables=)," +" all regular user tables and named views will be treated as layers. " +"However, tables with multiple geometry column will only be reported once " +"in that mode. So this variable is mainly useful when PostGIS is enabled " +"to find out tables with no spatial data, or views without an entry in " +"*geometry_columns* table." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:70 +msgid "" +"In any case, all user tables can be queried explicitly with " +"GetLayerByName()" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:73 +msgid "" +"Regular (non-spatial) tables can be accessed, and will return features " +"with attributes, but not geometry. If the table has a \"wkb_geometry\" " +"field, it will be treated as a spatial table. The type of the field is " +"inspected to determine how to read it. It can be a PostGIS **geometry** " +"field, which is assumed to come back in OGC WKT, or type BYTEA or OID in " +"which case it is used as a source of OGC WKB geometry." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:80 +msgid "Tables inherited from spatial tables are supported." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:83 +msgid "" +"If there is an \"ogc_fid\" field, it will be used to set the feature id " +"of the features, and not treated as a regular field." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:86 +msgid "" +"The layer name may be of the form \"schema.table\". The schema must " +"exist, and the user needs to have write permissions for the target and " +"the public schema." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:90 +msgid "If the user defines the environment variable" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:96 +msgid "" +"(and does not specify tables=), only the regular user tables will be " +"treated as layers. The default action is to include the views. This " +"variable is particularly useful when you want to copy the data into " +"another format while avoiding the redundant data from the views." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:102 +msgid "Named views" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:104 +msgid "" +"When PostGIS is enabled for the accessed database, named views are " +"supported, provided that there is an entry in the *geometry_columns* " +"tables. But, note that the AddGeometryColumn() SQL function doesn't " +"accept adding an entry for a view (only for regular tables). So, that " +"must usually be done by hand with a SQL statement like :" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:114 +msgid "" +"It is also possible to use named views without inserting a row in the " +"geometry_columns table. For that, you need to explicitly specify the name" +" of the view in the \"tables=\" option of the connection string. See " +"above. The drawback is that OGR will not be able to report a valid SRS " +"and figure out the right geometry type." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:121 +msgid "Retrieving FID of newly inserted feature" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:123 +msgid "" +"The FID of a feature (i.e. usually the value of the OGC_FID column for " +"the feature) inserted into a table with CreateFeature(), in non-copy " +"mode, will be retrieved from the database and can be obtained with " +"GetFID(). One side-effect of this new behavior is that you must be " +"careful if you re-use the same feature object in a loop that makes " +"insertions. After the first iteration, the FID will be set to a non-null " +"value, so at the second iteration, CreateFeature() will try to insert the" +" new feature with the FID of the previous feature, which will fail as you" +" cannot insert 2 features with same FID. So in that case you must " +"explicitly reset the FID before calling CreateFeature(), or use a fresh " +"feature object." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:136 +msgid "Snippet example in Python :" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:146 +msgid "or :" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:155 +msgid "" +"Old GDAL behavior can be obtained by setting the configuration option " +":config:`OGR_PG_RETRIEVE_FID` to FALSE." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:159 +msgid "Issues with transactions" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:161 +msgid "" +"Efficient sequential reading in PostgreSQL requires to be done within a " +"transaction (technically this is a CURSOR WITHOUT HOLD). So the PG driver" +" will implicitly open such a transaction if none is currently opened as " +"soon as a feature is retrieved. This transaction will be released if " +"ResetReading() is called (provided that no other layer is still being " +"read)." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:168 +msgid "" +"If within such an implicit transaction, an explicit dataset level " +"StartTransaction() is issued, the PG driver will use a SAVEPOINT to " +"emulate properly the transaction behavior while making the active cursor " +"on the read layer still opened." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:173 +msgid "" +"If an explicit transaction is opened with dataset level " +"StartTransaction() before reading a layer, this transaction will be used " +"for the cursor that iterates over the layer. When explicitly committing " +"or rolling back the transaction, the cursor will become invalid, and " +"ResetReading() should be issued again to restart reading from the " +"beginning." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:180 +msgid "" +"As calling SetAttributeFilter() or SetSpatialFilter() implies an implicit" +" ResetReading(), they have the same effect as ResetReading(). That is to " +"say, while an implicit transaction is in progress, the transaction will " +"be committed (if no other layer is being read), and a new one will be " +"started again at the next GetNextFeature() call. On the contrary, if they" +" are called within an explicit transaction, the transaction is " +"maintained." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:188 +msgid "" +"With the above rules, the below examples show the SQL instructions that " +"are run when using the OGR API in different scenarios." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:281 +msgid "" +"Note: in reality, the PG drivers fetches 500 features at once. The FETCH " +"1 is for clarity of the explanation." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:285 +msgid "Advanced Examples" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:287 +msgid "" +"This example shows using ogrinfo to list only the layers specified by the" +" *tables=* options." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:294 +msgid "" +"This example shows using ogrinfo to query a table 'foo' with multiple " +"geometry columns ('geom1' and 'geom2')." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:301 +msgid "" +"This example show how to list only the layers inside the schema apt200810" +" and apt200812. The layer names will be prefixed by the name of the " +"schema they belong to." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:309 +msgid "" +"This example shows using ogrinfo to list only the layers inside the " +"schema named apt200810. Note that the layer names will not be prefixed by" +" apt200810 as only one schema is listed." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:317 +msgid "" +"This example shows how to convert a set of shapefiles inside the " +"apt200810 directory into an existing Postgres schema apt200810. In that " +"example, we could have use the schemas= option instead." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:325 +msgid "" +"This example shows how to convert all the tables inside the schema " +"apt200810 as a set of shapefiles inside the apt200810 directory. Note " +"that the layer names will not be prefixed by apt200810 as only one schema" +" is listed" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:334 +msgid "" +"This example shows how to overwrite an existing table in an existing " +"schema. Note the use of -nln to specify the qualified layer name." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:341 +msgid "" +"Note that using -lco SCHEMA=mytable instead of -nln would not have worked" +" in that case (see `#2821 <http://trac.osgeo.org/gdal/ticket/2821>`__ for" +" more details)." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:345 +msgid "" +"If you need to overwrite many tables located in a schema at once, the " +"-nln option is not the more appropriate, so it might be more convenient " +"to use the active_schema connection string. The following example will " +"overwrite, if necessary, all the PostgreSQL tables corresponding to a set" +" of shapefiles inside the apt200810 directory :" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:359 +msgid ":ref:`OGR PostgreSQL driver Information <vector.pg>`" +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:6 +msgid "PGDump" +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:10 +msgid "" +"This write-only driver implements support for generating a SQL dump file " +"that can later be injected into a live PostgreSQL instance. It supports " +"PostgreSQL extended with the `PostGIS <http://postgis.net/>`__ " +"geometries." +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:15 +msgid "This driver is very similar to the PostGIS shp2pgsql utility." +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:17 +msgid "Most creation options are shared with the regular PostgreSQL driver." +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:19 +msgid "" +"The PGDump driver supports creating tables with multiple PostGIS geometry" +" columns (following :ref:`rfc-41`)" +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:253 +msgid ":copy-config:`PG_USE_COPY`" +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:258 +msgid "" +"The driver supports writing to files managed by VSI Virtual File System " +"API, which include \"regular\" files, as well as files in the /vsizip/, " +"/vsigzip/ domains." +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:267 +msgid "" +"Simple translation of a shapefile into PostgreSQL into a file abc.sql. " +"The table 'abc' will be created with the features from abc.shp and " +"attributes from abc.dbf. The SRID is specified. :config:`PG_USE_COPY` is " +"set to YES to improve the performance." +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:276 +msgid "Pipe the output of the PGDump driver into the psql utility." +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:285 +msgid ":ref:`OGR PostgreSQL driver Page <vector.pg>`" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:6 +msgid "PGeo" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:10 +msgid "" +"OGR optionally supports reading ESRI Personal GeoDatabase .mdb files via " +"ODBC. Personal GeoDatabase is a Microsoft Access database with a set of " +"tables defined by ESRI for holding geodatabase metadata, and with " +"geometry for features held in a BLOB column in a custom format " +"(essentially Shapefile geometry fragments). This driver accesses the " +"personal geodatabase via ODBC but does not depend on any ESRI middle-" +"ware." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:18 +msgid "" +"Personal Geodatabases are accessed by passing the file name of the .mdb " +"file to be accessed as the data source name." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:21 +msgid "" +"In order to facilitate compatibility with different configurations, the " +":config:`PGEO_DRIVER_TEMPLATE` config option was added to provide a way " +"to programmatically set the DSN with the filename as an argument. In " +"cases where the driver name is known, this allows for the construction of" +" the DSN based on that information in a manner similar to the default " +"(used for Windows access to the Microsoft Access Driver)." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:29 +msgid "" +"OGR treats all feature tables as layers. Most geometry types should be " +"supported, including 3D data. Measure information (m value) is also " +"supported. Coordinate system information should be properly associated " +"with layers." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:33 +msgid "" +"Currently the OGR Personal Geodatabase driver does not take advantage of " +"spatial indexes for fast spatial queries, though that may be added in the" +" future." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:37 +msgid "" +"The Personal GeoDatabase format does not strictly differentiate between " +"multi and single geometry types for polygon or line layers, and it is " +"possible for a polygon or line layer to contain a mix of both single and " +"multi type geometries. Accordingly, in order to provide predictable " +"geometry types, the GDAL driver will always report the type of a line " +"layer as wkbMultiLineString, and a polygon layer as wkbMultiPolygon. " +"Single-part line or polygon features in the database will be promoted to " +"multilinestrings or multipolygons during reading." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:46 +msgid "" +"By default, SQL statements are passed directly to the MDB database " +"engine. It's also possible to request the driver to handle SQL commands " +"with :ref:`OGR SQL <ogr_sql_dialect>` engine, by passing **\"OGRSQL\"** " +"string to the ExecuteSQL() method, as name of the SQL dialect." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:54 +msgid "" +"\"GetLayerDefinition a_layer_name\" and \"GetLayerMetadata a_layer_name\"" +" can be used as special SQL requests to get respectively the definition " +"and metadata of a Personal GeoDatabase table as XML content." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:103 +msgid "How to use PGeo driver with unixODBC and MDB Tools (on Unix and Linux)" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:105 +msgid "" +"This article gives step-by-step explanation of how to use OGR with " +"unixODBC package and how to access Personal Geodatabase with PGeo driver." +" See also `GDAL wiki for other details " +"<http://trac.osgeo.org/gdal/wiki/mdbtools>`__" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:111 +msgid "Prerequisites" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:115 +msgid "Install `unixODBC <http://www.unixodbc.org>`__ >= 2.2.11" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:116 +msgid "" +"Install MDB Tools. The official upstream of MDB Tools is maintained at " +"`https://github.com/mdbtools/mdbtools " +"<https://github.com/mdbtools/mdbtools>`__ Version 0.9.4 or later is " +"recommended for best compatibility with the PGeo driver. With the latest " +"version no additional configuration (the followings) is required on " +"Debian Linux and :bash:`ogrinfo sample.mdb` works fine." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:123 +msgid "(On Ubuntu : sudo apt-get install unixodbc libmdbodbc)" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:125 +msgid "(On Debian : sudo apt-get install unixodbc odbc-mdbtools)" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:130 +msgid "There are two configuration files for unixODBC:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:132 +msgid "" +"odbcinst.ini - this file contains definition of ODBC drivers available to" +" all users; this file can be found in /etc directory or location given as" +" --sysconfdir if you did build unixODBC yourself." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:135 +msgid "" +"odbc.ini - this file contains definition of ODBC data sources (DSN " +"entries) available to all users." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:137 +msgid "" +"~/.odbc.ini - this is the private file where users can put their own ODBC" +" data sources." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:140 +msgid "" +"Editing the odbc.ini files is only required if you want to setup an ODBC " +"Data Source Name (DSN) so that Personal Geodatabase files can be directly" +" accessed via DSN. This is entirely optional, as the PGeo driver will " +"automatically handle the required connection parameters for you if a " +"direct .mdb file name is used instead." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:146 +msgid "Format of configuration files is very simple:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:154 +msgid "" +"For more details, refer to `unixODBC manual " +"<http://www.unixodbc.org/doc/>`__." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:158 +msgid "1. ODBC driver configuration" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:160 +msgid "" +"First, you need to configure ODBC driver to access Microsoft Access " +"databases with MDB Tools. Add following definition to your odbcinst.ini " +"file." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:174 +msgid "" +"[Microsoft Access Driver (\\*.mdb)] - remember to use \"Microsoft Access " +"Driver (\\*.mdb)\" as the name of section because PGeo driver composes " +"ODBC connection string for Personal Geodatabase using \"DRIVER=Microsoft " +"Access Driver (\\*.mdb);\" string." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:178 +msgid "Description - put short description of this driver definition." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:179 +msgid "Driver - full path of ODBC driver for MDB Tools." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:182 +msgid "2. ODBC data source configuration (optional)" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:184 +msgid "" +"In this section, I use 'sample.mdb' as a name of Personal Geodatabase, so" +" replace this name with your own database." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:187 +msgid "Create .odbc.ini file in your HOME directory:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:193 +msgid "Put following ODBC data source definition to your .odbc.ini file:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:208 +msgid "Step by step explanation of DSN entry:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:210 +msgid "" +"[sample_pgeo] - this is name of ODBC data source (DSN). You will refer to" +" your Personal Geodatabase using this name. You can use your own name " +"here." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:213 +msgid "Description - short description of the DSN entry." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:214 +msgid "Driver - full name of driver defined in step 1. above." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:215 +msgid "Database - full path to .mdb file with your Personal Geodatabase." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:216 +msgid "Host, Port, User and Password entries are not used by MDB Tools driver." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:220 +msgid "Testing PGeo driver with ogrinfo" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:222 +msgid "Now, you can try to access PGeo data source with ogrinfo." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:224 +msgid "First, check if you have PGeo driver built in OGR:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:235 +msgid "" +"Now, you can access your Personal Geodatabase. If you've setup a DSN for " +"the Personal Geodatabase (as detailed in section 2 above), the data " +"source should be PGeo:<DSN> where <DSN> is the name of DSN entry you put " +"to your .odbc.ini." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:239 +msgid "" +"Alternatively, you can pass a .mdb filename directly to OGR to avoid " +"manual creation of the DSN." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:249 +msgid "" +"After you run the command above, you should get list of layers stored in " +"your geodatabase." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:252 +msgid "Now, you can try to query details of particular layer:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:263 +msgid "Resources" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:265 +msgid "" +"`About ESRI Geodatabase " +"<http://www.esri.com/software/arcgis/geodatabase/index.html>`__" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:267 +msgid "`MDB Tools project home <https://github.com/mdbtools/mdbtools>`__" +msgstr "" + +#: ../../source/drivers/vector/plscenes.rst:6 +msgid "PLScenes" +msgstr "" + +#: ../../source/drivers/vector/plscenes.rst:10 +msgid "" +"This driver can connect to Planet Labs Data V1 API. GDAL/OGR must be " +"built with Curl support in order for the PLScenes driver to be compiled." +msgstr "" + +#: ../../source/drivers/vector/plscenes.rst:13 +msgid "Please consult the dedicated pages for each version of the API:" +msgstr "" + +#: ../../source/drivers/vector/plscenes.rst:23 +msgid "" +"`Documentation of Planet Scenes Data API V1 " +"<https://developers.planet.com/docs/apis/data/>`__" +msgstr "" + +#: ../../source/drivers/vector/plscenes.rst:25 +#: ../../source/drivers/vector/plscenes_data_v1.rst:256 +msgid ":ref:`Raster PLMosaic / Planet Mosaics API driver <raster.plmosaic>`" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:4 +msgid "PLScenes (Planet Labs Scenes), Data V1 API" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:8 +msgid "" +"The driver supports read-only operations to list scenes and their " +"metadata as a vector layer per item-types: \"PSOrthoTile\", " +"\"REOrthoTile\", \"PSScene3Band\", \"PSScene4Band\", \"REScene\", " +"\"Landsat8L1G\", \"Sentinel2L1C\". It can also access raster scenes." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:30 +msgid "**version**\\ =data_v1: To specify the API version to request." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:31 +msgid "" +"**api_key**\\ =value: To specify the Planet API KEY. It is mandatory, " +"unless it is supplied through the open option API_KEY, or the " +"configuration option :config:`PL_API_KEY`." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:34 +msgid "" +"**follow_links**\\ =YES/NO: Whether assets links should be followed for " +"each scene (vector). Getting assets links require a HTTP request per " +"scene, which might be costly when enumerating through a lot of products. " +"Defaults to NO." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:38 +msgid "" +"**scene**\\ =scene_id: To specify the scene ID, when accessing raster " +"data. Optional for vector layer access." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:40 +msgid "" +"**itemtypes**\\ =name: To specify the item types name. Optional for " +"vector layer access. Mandatory for raster access." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:42 +msgid "" +"**asset**\\ =value: To specify the asset type (for raster fetching). " +"Default is \"visual\". Optional for vector layer access. If the option is" +" not specified and the 'visual' asset category does not exist for the " +"scene (or if the value is set to 'list'), the returned dataset will have " +"subdatasets for the available asset categories." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:47 +msgid "" +"**medata**\\ =YES/NO: (Raster only) Whether scene metadata should be " +"fetch from the API and attached to the raster dataset. Defaults to YES." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:126 +msgid ":copy-config:`PL_API_KEY`" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:136 +msgid "" +"The layer field definition is built from the \"plscensconf.json\" file in" +" the GDAL configuration. The links to downloadable products are in " +"*asset_XXXXX_location* attributes where XXXXX is the asset category id, " +"when they are active. Otherwise they should be activated by sending a " +"POST request to the URL in the *asset_XXXXX_activate_link* attribute " +"(what the raster driver does automatically)" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:146 +msgid "" +"The footprint of each scene is reported as a MultiPolygon with a " +"longitude/latitude WGS84 coordinate system (EPSG:4326)." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:152 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server. It also makes the same for simple attribute filters set with" +" SetAttributeFilter(). Note that not all attributes support all " +"comparison operators. Refer to comparator column in `Metadata properties " +"<https://www.planet.com/docs/v0/scenes/#metadata>`__" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:161 +msgid "" +"Features are retrieved from the server by chunks of 250 by default (and " +"this is the maximum value accepted by the server). This number can be " +"altered with the :config:`PLSCENES_PAGE_SIZE` configuration option." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:167 +msgid "Vector layer (scene metadata) examples" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:169 +msgid "Listing all scenes available (with the rights of the account) :" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:187 +msgid "" +"Listing all scenes available on PSOrthoTile item types, under a point of " +"(lat,lon)=(40,-100) :" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:194 +msgid "" +"Listing all scenes available within a bounding box (lat,lon)=(40,-100) to" +" (lat,lon)=(39,-99)" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:201 +msgid "Listing all scenes available matching criteria :" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:207 +msgid "List all downloadable scenes:" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:214 +msgid "Raster access" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:216 +msgid "" +"Scenes can be accessed as raster datasets, provided that the scene ID is " +"specified with the 'scene' parameter / :oo:`SCENE` open option. The " +"'itemtypes' parameter / :oo:`ITEMTYPES` open option must also be " +"specified. The asset type (visual, analytic, ...) can be specified with " +"the 'asset' parameter / :oo:`ASSET` open option. The scene id is the " +"content of the value of the 'id' field of the features." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:223 +msgid "" +"If the product is not already generated on the server, it will be " +"activated, and the driver will wait for it to be available. The length of" +" this retry can be configured with the :oo:`ACTIVATION_TIMEOUT` open " +"option." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:228 +msgid "Raster access examples" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:230 +msgid "Displaying raster metadata :" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:242 +msgid "Converting/downloading a whole file:" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:252 +msgid ":ref:`General documentation page for PLScenes driver <vector.plscenes>`" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:254 +msgid "" +"`Documentation of Planet Scenes Data API v1 " +"<https://developers.planet.com/docs/apis/data/>`__" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:5 +msgid "PMTiles -- ProtoMaps Tiles" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:9 +msgid "PMTiles" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:13 +msgid "" +"This driver supports reading and writing `PMTiles " +"<https://github.com/protomaps/PMTiles>`__ datasets containing vector " +"tiles, encoded in the MapVector Tiles (MVT) format." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:16 +msgid "" +"PMTiles is a single-file archive format for tiled data. A PMTiles archive" +" can be hosted on a commodity storage platform such as S3, and enables " +"low-cost, zero-maintenance map applications that are \"serverless\" - " +"free of a custom tile backend or third party provider." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:21 +msgid "" +"This driver is compatible with all GDAL :ref:`network-based virtual file " +"systems <network_based_file_systems>`" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:27 +msgid "" +"The supported datasets must contain a JSON metadata document following " +"the `MBTiles specification <https://github.com/mapbox/mbtiles-" +"spec/blob/master/1.3/spec.md#vector-tileset-metadata>`__, containing at " +"least the ``vector_layers`` array." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:32 +msgid "" +"Note that the driver will make no effort of stitching together geometries" +" for linear or polygonal features that overlap several tiles. An " +"application that wishes to eliminate those interrupts could potentially " +"use the CLIP=NO open option to get larger boundaries, and use appropriate" +" clipping graphic primitives to hide those discontinuities." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:59 +msgid "" +"Vector tiles are generally produced with a buffer that provides overlaps " +"between adjacent tiles, and can be used to display them properly. When " +"using vector tiles as a vector layer source, like in OGR vector model, " +"this padding is undesirable, hence the default behavior of clipping." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:89 +msgid "" +"Tiles are generated with WebMercator (EPSG:3857) projection. Several " +"layers can be written. It is possible to decide at which zoom level " +"ranges a given layer is written." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:97 +msgid "" +"The driver implements also a direct translation mode when using " +":program:`ogr2ogr` with a MBTiles vector dataset as input and a PMTiles " +"output dataset, without any argument: ``ogr2ogr out.pmtiles in.mbtiles``." +" In that mode, existing MVT tiles from the MBTiles files are used as " +"such, contrary to the general writing mode that will involve computing " +"them by discretizing geometry coordinates." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:250 +msgid "/vsipmtiles/ virtual file system" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:252 +msgid "" +"The /vsipmtiles/ virtual file system offers a view of the content of a " +"PMTiles dataset has a file hierarchy, with the following structure:" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:263 +msgid "" +"The :source_file:`swig/python/gdal-utils/osgeo_utils/samples/gdal_ls.py` " +"and :source_file:`swig/python/gdal-utils/osgeo_utils/samples/gdal_cp.py` " +"sample utilities can be used to explore and extract data from a PMTiles " +"dataset" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:268 +msgid "Listing the content of a dataset:" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:274 +#: ../../source/drivers/vector/pmtiles.rst:296 +msgid "outputs:" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:290 +msgid "Displaying the metadata JSON file:" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:334 +msgid "Extracting all content in a local directory:" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:342 +msgid "" +"Simple translation of a single shapefile into PMTiles. Dataset creation " +"options (dsco) MINZOOM and MAXZOOM specifies tile zoom levels. ::" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:347 +msgid "" +"Merge all PostgreSQL/PostGIS tables in a schema into a single PMTiles " +"file. PostgreSQL table names are used as layer names. Dataset creation " +"options (dsco) MINZOOM and MAXZOOM specifies tile zoom levels. ::" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:356 +msgid "`PMTiles specification <https://github.com/protomaps/PMTiles>`__" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:358 +msgid ":ref:`MBTiles driver <raster.mbtiles>`" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:6 +msgid "S57" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:10 +msgid "" +"International Hydrographic Organisation (IHO) S-57 Electronic Navigation " +"Charts (ENC) datasets are supported for read access." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:13 +msgid "" +"The S-57 driver module produces features for all S-57 features in the " +"S-57 file, and associated updates. S-57 (ENC) files normally have the " +"extension \".000\"." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:17 +msgid "" +"S-57 feature objects are translated into features. S-57 geometry objects " +"are automatically collected and formed into geometries on the features." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:20 +msgid "" +"The S-57 reader depends on having two supporting files, " +"s57objectclasses.csv, and s57attributes.csv available at runtime in order" +" to translate features in an object class specific manner. These should " +"be in the directory pointed to by the environment variable S57_CSV, or in" +" the current working directory." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:26 +msgid "" +"S-57 update files contain information on how to update a distributed S-57" +" base data file. The base files normally have the extension .000 while " +"the update files have extensions like .001, .002 and so on. The S-57 " +"reader will normally read and apply all updates files to the in memory " +"version of the base file on the fly. The feature data provided to the " +"application therefore includes all the updates." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:43 +msgid "Feature Translation" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:45 +msgid "" +"Normally all features read from S-57 are assigned to a layer based on the" +" name of the object class (OBJL) to which they belong. For instance, with" +" an OBJL value of 2, the feature is an \"Airport / airfield\" and has a " +"short name of \"AIRARE\" which is used as the layer name. A typical S-57 " +"transfer will have in excess of 100 layers." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:51 +msgid "" +"Each feature type has a predefined set of attributes as defined by the " +"S-57 standard. For instance, the airport (AIRARE) object class can have " +"the AIRARE, CATAIR, CONDTN, CONVIS, NOBJNM, OBJNAM, STATUS, INFORM, " +"NINFOM, NTXTDS, PICREP, SCAMAX, SCAMIN, TXTDSC, RECDAT, RECIND, SORDAT, " +"and SORIND attributes. These short names can be related to longer, more " +"meaningful names using an S-57 object/attribute catalog such as the S-57 " +"standard document itself, or the catalog files (s57attributes.csv, and " +"s57objectclasses.csv). Such a catalog can also be used to establish all " +"the available object classes, and their attributes." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:61 +msgid "" +"The following are some common attributes, including generic attributes " +"which appear on all feature, regardless of object class. is turned on." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:100 +msgid "The following are present if LNAM_REFS is enabled:" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:116 +msgid "DSID layer" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:118 +msgid "" +"Dataset wide fields, such as DSID (Data Set Identification), DSSI (Data " +"Set Structure Information) and DSPM (Data Set Parameter) are exposed in a" +" layer ``DSID`` which has a single feature. See paragraph 7.3.1 \"Data " +"set general information record structure\" of `IHO S-57 Edition 3.1 " +"standard (main)`_" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:125 +msgid "Soundings" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:127 +msgid "" +"Depth soundings are handled somewhat specially in S-57 format, in order " +"to efficiently represent the many available data points. In S-57 one " +"sounding feature can have many sounding points. The S-57 reader splits " +"each of these out into its own feature type \\`SOUNDG' feature with an " +"s57_type of \\`s57_point3d'. All the soundings from a single feature " +"record will have the same AGEN, FIDN, FIDS and LNAM value." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:135 +msgid "S57 Control Options" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:137 +msgid "" +"There are several control options which can be used to alter the behavior" +" of the S-57 reader. Users can set these by appending them in the " +"OGR_S57_OPTIONS environment variable." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:141 +msgid "" +"They can also be specified independently as open options to the driver. " +"|about-open-options| The following open options are supported:" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:234 +msgid "S-57 Export" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:236 +msgid "" +"Preliminary S-57 export capability is intended only for specialized use, " +"and is not properly documented at this time. Setting the following " +"options is a minimum required to support S-57 to S-57 conversion via OGR." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:244 +msgid "" +"|about-dataset-creation-options| The following dataset creation options " +"are supported to supply basic information for the S-57 data set " +"descriptive records (DSID and DSPM, see the S-57 standard for a more " +"detailed description):" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:373 +msgid "`S-57 Online Object/Attribute Catalog <http://www.s-57.com/>`__" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:374 +msgid "" +"`Frank's S-57 Page (at archive.org) " +"<https://web.archive.org/web/20130730111701/http://home.gdal.org/projects/s57/index.html>`__:" +" Links to other resources, and sample datasets." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:377 +msgid "`IHO S-57 Edition 3.1 standard (main)`_" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:378 +msgid "" +"`S-57 Appendix B " +"<https://iho.int/uploads/user/pubs/standards/s-57/20ApB1.pdf>`__" +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:10 +msgid "" +"SDTS TVP (Topological Vector Profile) and Point Profile datasets are " +"supported for read access. Each primary attribute, node (point), line and" +" polygon module is treated as a distinct layer." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:14 +msgid "" +"To select an SDTS transfer, the name of the catalog file should be used. " +"For instance ``TR01CATD.DDF`` where the first four characters are all " +"that typically varies." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:18 +msgid "" +"SDTS coordinate system information is properly supported for most " +"coordinate systems defined in SDTS." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:21 +msgid "There is no update or creation support in the SDTS driver." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:23 +msgid "" +"Note that in TVP datasets the polygon geometry is formed from the " +"geometry in the line modules. Primary attribute module attributes should " +"be properly attached to their related node, line or polygon features, but" +" can be accessed separately as their own layers." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:28 +msgid "This driver has no support for raster (DEM) SDTS datasets." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:40 +msgid "" +"`SDTS Abstraction Library " +"<https://web.archive.org/web/20130730111701/http://home.gdal.org/projects/sdts/index.html>`__:" +" The base library used to implement this driver." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:43 +msgid "" +"`http://mcmcweb.er.usgs.gov/sdts <http://mcmcweb.er.usgs.gov/sdts/>`__: " +"Main USGS SDTS web page." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:6 +msgid "Selafin" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:10 +msgid "" +"OGR supports reading from 2D Selafin/Seraphin files. Selafin/Seraphin is " +"the generic output and input format of geographical files in the open-" +"source `Telemac hydraulic model <http://www.opentelemac.org>`__. The file" +" format is suited to the description of numerical attributes for a set of" +" point features at different time steps. Those features usually " +"correspond to the nodes in a finite-element model. The file also holds a " +"connectivity table which describes the elements formed by those nodes and" +" which can also be read by the driver." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:19 +msgid "The driver supports the use of VSI virtual files as Selafin datasources." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:21 +msgid "" +"The driver offers full read-write support on Selafin files. However, due " +"to the particular nature of Selafin files where element (polygon) " +"features and node (point) features are closely related, writing on " +"Selafin layers can lead to counter-intuitive results. In a general way, " +"writing on any layer of a Selafin data-source will cause side effects on " +"all the other layers. Also, it is very important **not to open the same " +"datasource more than once in update mode**. Having two processes write at" +" the same time on a single datasource can lead to irreversible data " +"corruption. The driver issues a warning each time a datasource is opened " +"in update mode." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:42 +msgid "Magic bytes" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:44 +msgid "" +"There is no generic extension to Selafin files. The adequate format is " +"tested by looking at a dozen of magic bytes at the beginning of the file:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:48 +msgid "" +"The first four bytes of the file should contain the values (in " +"hexadecimal): 00 00 00 50. This actually indicates the start of a string " +"of length 80 in the file." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:51 +msgid "" +"At position 84 in the file, the eight next bytes should read (in " +"hexadecimal): 00 00 00 50 00 00 00 04." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:54 +msgid "" +"Files which match those two criteria are considered to be Selafin files " +"and the driver will report it has opened them successfully." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:60 +msgid "" +"Selafin format is designed to hold data structures in a portable and " +"compact way, and to allow efficient random access to the data. To this " +"purpose, Selafin files are binary files with a generic structure." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:65 +msgid "Elements" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:67 +msgid "" +"Selafin files are made of the juxtaposition of elements. Elements have " +"one of the following types:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:70 +msgid "integer," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:71 +msgid "string," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:72 +msgid "floating point values," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:73 +msgid "arrays of integers," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:74 +msgid "arrays of floating point values." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:77 +msgid "Element" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:77 +msgid "Internal representation" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:80 +#: ../../source/drivers/vector/selafin.rst:91 +msgid "a b c d" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:80 +msgid "" +"Integers are stored on 4 bytes in big-endian format (most significant " +"byte first). The value of the integer is 2\\ :sup:`24`.a+2\\ :su " +"p:`16`.b+2\\ :sup:`8`. c+d." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:91 +msgid "Floating point" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:91 +msgid "" +"Floating point values are stored on 4 bytes in IEEE 754 format and under " +"big-endian convention (most significant byte first). Endianness is " +"detected at run time only once when the first floating point value is " +"read." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:103 +#: ../../source/drivers/vector/selafin.rst:121 +#: ../../source/drivers/vector/selafin.rst:142 +msgid "Length 1 2 ... Length" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:103 +msgid "Strings are stored in three parts:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:106 +msgid "an integer holding the length (in characters) of the string, over 4 bytes;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:111 +msgid "the sequence of characters of the string, each character on one byte;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:116 +msgid "the same integer with the length of the string repeated" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:121 +msgid "Array of integers" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:121 +msgid "Arrays of integers are stored in three parts:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:125 +#: ../../source/drivers/vector/selafin.rst:147 +msgid "" +"an integer holding the length (in bytes, thus 4 times the number of " +"elements) of the array, over 4 bytes;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:132 +msgid "" +"the sequence of integers in the array, each integer on 4 bytes as " +"described earlier;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:138 +#: ../../source/drivers/vector/selafin.rst:160 +msgid "the same integer with the length of the array repeated" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:142 +msgid "Array of floating point values" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:142 +msgid "Arrays of floating point values are stored in three parts:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:154 +msgid "" +"the sequence of floating point values in the array, each one on 4 bytes " +"as described earlier;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:166 +msgid "Full structure" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:168 +msgid "" +"The header of a Selafin file holds the following elements in that exact " +"order:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:171 +msgid "" +"a *string* of 80 characters with the title of the study; the last 8 " +"characters shall be \"SERAPHIN\" or \"SERAFIN\" or \"SERAFIND\";" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:173 +msgid "" +"an *array of integers* of exactly 2 elements, the first one being the " +"number of variables (attributes) *nVar*, and the second is ignored;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:175 +msgid "*nVar strings* with the names of the variables, each one with length 32;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:177 +msgid "an *array of integers* of exactly 10 elements:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:179 +msgid "the third element is the x-coordinate of the origin of the model;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:180 +msgid "the fourth element is the y-coordinate of the origin of the model;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:181 +msgid "" +"the tenth element *isDate* indicates if the date of the model has to be " +"read (see later);" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:183 +msgid "" +"in addition, the second element being unused by hydraulic software at the" +" moment, it is used by the driver to store the spatial reference system " +"of the datasource, in the form of a single integer with the EPSG number " +"of the projection;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:188 +msgid "" +"if *isDate*\\ =1, an *array of integers* of exactly 6 elements, with the " +"starting date of the model (year, month, day, hour, minute, second);" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:191 +msgid "an *array of integers* of exactly 4 elements:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:193 +msgid "the first element is the number of elements *nElements*," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:194 +msgid "the second element is the number of points *nPoints*," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:195 +msgid "" +"the third element is the number of points per element\\ " +"*nPointsPerElement*," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:197 +msgid "the fourth element must be 1;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:199 +msgid "" +"an *array of integers* of exactly *nElements*nPointsPerElement* elements," +" with each successive set of *nPointsPerElement* being the list of the " +"number of the points (number starting with 1) constituting an element;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:203 +msgid "" +"an *array of integers* of exactly *nPoints* elements ignored by the " +"driver (the elements shall be 0 for inner points and another value for " +"the border points where a limit condition is applied);" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:206 +msgid "" +"an *array of floating point values* of exactly *nPoints* elements with " +"the x-coordinates of the points;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:208 +msgid "" +"an *array of floating point values* of exactly *nPoints* elements with " +"the y-coordinates of the points;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:211 +msgid "" +"The rest of the file actually holds the data for each successive time " +"step. A time step contains the following elements:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:214 +msgid "" +"a *array of floating point values* of exactly 1 element, being the date " +"of the time step relative to the starting date of the simulation (usually" +" in seconds);" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:217 +msgid "" +"*nVar array of floating point values*, each with exactly *nPoints* " +"elements, with the values of each attribute for each point at the current" +" time step." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:222 +msgid "Mapping between file and layers" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:225 +msgid "Layers in a Selafin datasource" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:227 +msgid "The Selafin driver accepts only Selafin files as data sources." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:229 +msgid "" +"Each Selafin file can hold one or several time steps. All the time steps " +"are read by the driver and two layers are generated for each time step:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:232 +msgid "" +"one layer with the nodes (points) and their attributes: its name is the " +"base name of the data source, followed by \"_p\" (for Points);" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:234 +msgid "" +"one layer with the elements (polygons) and their attributes calculated as" +" the averages of the values of the attributes of their vertices: its name" +" is the base name of the data source, followed by \"_e\" (for Elements)." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:239 +msgid "" +"Finally, either the number of the time step, or the calculated date of " +"the time step (based on the starting date and the number of seconds " +"elapsed), is added to the name. A data source in a file called Results " +"may therefore be read as several layers:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:244 +msgid "" +"``Results_p2014_05_01_20_00_00``, meaning that the layers holds the " +"attributes for the nodes and that the results hold for the time step at " +"8:00 PM, on May 1st, 2014;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:247 +msgid "" +"``Results_e2014_05_01_20_00_00``, meaning that the layers holds the " +"attributes for the elements and that the results hold for the time step " +"at 8:00 PM, on May 1st, 2014;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:250 +msgid "" +"``Results_p2014_05_01_20_15_00``, meaning that the layers holds the " +"attributes for the elements and that the results hold for the time step " +"at 8:15 PM, on May 1st, 2014;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:256 +msgid "Constraints on layers" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:258 +msgid "" +"Because of the `format of the Selafin file <#format>`__, the layers in a " +"single Selafin datasource are not independent from each other. Changing " +"one layer will most certainly have side effects on all other layers. The " +"driver updates all the layers to match the constraints:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:263 +msgid "" +"All the point layers have the same number of features. When a feature is " +"added or removed in one layer, it is also added or removed in all other " +"layers." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:266 +msgid "" +"Features in different point layers share the same geometry. When the " +"position of one point is changed, it is also changed in all other layers." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:269 +msgid "" +"All the element layers have the same number of features. When a feature " +"is added or removed in one layer, it is also added or removed in all " +"other layers." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:272 +msgid "" +"All the polygons in element layers have the same number of vertices. The " +"number of vertices is fixed when the first feature is added to an element" +" layer, and can not be changed afterwards without recreating the " +"datasource from scratch." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:276 +msgid "" +"Features in different element layers share the same geometry. When an " +"element is added or removed in one layer, it is also added or removed in " +"all other layers." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:279 +msgid "" +"Every vertex of every feature in an element layer has a corresponding " +"point feature in the point layers. When an element feature is added, if " +"its vertices do not exist yet, they are created in the point layers." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:283 +msgid "" +"Points and elements layers only support attributes of type \"REAL\". The " +"format of real numbers (width and precision) can not be changed." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:287 +msgid "Layer filtering specification" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:289 +msgid "" +"As a single Selafin files may hold millions of layers, and the user is " +"generally interested in only a few of them, the driver supports syntactic" +" sugar to filter the layers before they are read." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:293 +msgid "" +"When the datasource is specified, it may be followed immediately by a " +"*layer filtering specification.*, as in ``Results[0:10]``. The effects of" +" the layer filtering specification is to indicate which time steps shall " +"be loaded from all Selafin files." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:298 +msgid "" +"The layer filtering specification is a comma-separated sequence of range " +"specifications, delimited by square brackets and maybe preceded by the " +"character 'e' or 'p'. The effect of characters 'e' and 'p' is to select " +"respectively either only elements or only nodes. If no character is " +"added, both nodes and elements are selected. Each range specification is:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:305 +msgid "" +"either a single number, representing one single time step (whose numbers " +"start with 0)," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:307 +msgid "" +"or a set of two numbers separated by a colon: in that case, all the time " +"steps between and including those two numbers are selected; if the first " +"number is missing, the range starts from the beginning of the file (first" +" time step); if the second number is missing, the range goes to the end " +"of the file (last time step);" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:313 +msgid "" +"Numbers can also be negative. In this case, they are counted from the end" +" of the file, -1 being the last time step." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:316 +msgid "Some examples of layer filtering specifications:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:319 +msgid "[0]" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:319 +msgid "First time step only, but return both points and elements" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:320 +msgid "[e:9]" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:320 +msgid "First 10 time steps only, and only layers with elements" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:321 +msgid "[p-4:]" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:321 +msgid "Last 4 time steps only, and only layers with nodes" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:322 +msgid "[3,10,-2:-1]" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:322 +msgid "" +"4\\ :sup:`th`, 11\\ :sup:`th`, and last two time steps, for both nodes " +"and elements" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:326 +msgid "Datasource creation options" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:345 +msgid "" +"An example of datasource creation option is: ``-dsco TITLE=\"My " +"simulation\" -dsco DATE=2014-05-01_10:00:00``." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:361 +msgid "An example of a layer creation option is: ``-lco DATE=24000``." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:364 +msgid "Notes about the creation and the update of a Selafin datasource" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:366 +msgid "" +"The driver supports creating and writing to Selafin datasources, but " +"there are some caveats when doing so." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:369 +msgid "" +"When a new datasource is created, it does not contain any layer, feature " +"or attribute." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:372 +msgid "" +"When a new layer is created, it automatically inherits the same number of" +" features and attributes as the other layers of the same type (points or " +"elements) already in the datasource. The features inherit the same " +"geometry as their corresponding ones in other layers. The attributes are " +"set to 0. If there was no layer in the datasource yet, the new layer is " +"created with no feature and attribute.In any case, when a new layer is " +"created, two layers are actually added: one for points and one for " +"elements." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:381 +msgid "" +"New features and attributes can be added to the layers or removed. The " +"behavior depends on the type of layer (points or elements). The following" +" table explains the behavior of the driver in the different cases." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:387 +msgid "Operation" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:387 +msgid "Points layers" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:387 +msgid "Element layers" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:389 +msgid "Change the geometry of a feature" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:389 +msgid "" +"The coordinates of the point are changed in the current layer and all " +"other layers in the datasource." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:389 +msgid "" +"The coordinates of all the vertices of the element are changed in the " +"current layer and all other layers in the datasource. It is not possible " +"to change the number of vertices. The order of the vertices matters." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:390 +msgid "Change the attributes of a feature" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:390 +msgid "The attributes of the point are changed in the current layer only." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:390 +msgid "No effect." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:391 +msgid "Add a new feature" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:391 +msgid "" +"A new point is added at the end of the list of features, for this layer " +"and all other layers. Its attributes are set to the values of the new " +"feature." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:391 +msgid "" +"The operation is only allowed if the new feature has the same number of " +"vertices as the other features in the layer. The vertices are checked to " +"see if they currently exist in the set of points. A vertex is considered " +"equal to a point if its distance is less than some maximum distance, " +"approximately equal to 1/1000\\ :sup:`th` of the average distance between" +" two points in the points layers. When a corresponding point is found, it" +" is used as a vertex for the element. If no point is found, a new is " +"created in all associated layers." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:392 +msgid "Delete a feature" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:392 +msgid "" +"The point is removed from the current layer and all point layers in the " +"datasource. All elements using this point as a vertex are also removed " +"from all element layers in the datasource." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:392 +msgid "" +"The element is removed from the current layer and all element layers in " +"the datasource." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:395 +msgid "" +"Typically, this implementation of operations is exactly what you'll " +"expect. For example, ogr2ogr can be used to reproject the file without " +"changing the inner link between points and elements." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:399 +msgid "" +"It should be noted that update operations on Selafin datasources are very" +" slow. This is because the format does no allow for quick insertions or " +"deletion of features and the file must be recreated for each operation." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:415 +msgid "" +"There is no SRS specification in the Selafin standard. The implementation" +" of SRS is an addition of the driver and stores the SRS in an unused data" +" field in the file. Future software using the Selafin standard may use " +"this field and break the SRS specification. In this case, Selafin files " +"will still be readable by the driver, but their writing will overwrite a " +"value which may have another purpose." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:6 +msgid "ESRI Shapefile" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:10 +msgid "" +"All varieties of ESRI Shapefiles should be available for reading, " +"creation and editing. The driver can also handle standalone DBF files " +"without associated .shp files." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:14 +msgid "" +"Normally the OGR Shapefile driver treats a whole directory of shapefiles " +"as a dataset, and a single shapefile within that directory as a layer. In" +" this case the directory name should be used as the dataset name. " +"However, it is also possible to use one of the files (.shp, .shx or .dbf)" +" in a shapefile set as the dataset name, and then it will be treated as a" +" dataset with one layer." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:21 +msgid "" +"Note that when reading a Shapefile of type SHPT_ARC, the corresponding " +"layer will be reported as of type wkbLineString, but depending on the " +"number of parts of each geometry, the actual type of the geometry for " +"each feature can be either OGRLineString or OGRMultiLineString. The same " +"applies for SHPT_POLYGON shapefiles, reported as layers of type " +"wkbPolygon, but depending on the number of parts of each geometry, the " +"actual type can be either OGRPolygon or OGRMultiPolygon." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:29 +msgid "" +"Measures (M coordinate) are supported. A Shapefile with measures is " +"created if the specified geometry type is measured or an appropriate " +"layer creation option is used. When a shapefile which may have measured " +"geometries is opened, the first shape is examined and if it uses " +"measures, the geometry type of the layer is set accordingly. This " +"behavior can be changed with the ADJUST_GEOM_TYPE open option." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:37 +msgid "" +"MultiPatch files are read and each patch geometry is turned into a TIN or" +" a GEOMETRYCOLLECTION of TIN representation for fans and meshes." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:40 +msgid "" +"If a .prj files in old Arc/Info style or new ESRI OGC WKT style is " +"present, it will be read and used to associate a projection with " +"features. Starting with GDAL 2.3, a match will be attempted with the EPSG" +" databases to identify the SRS of the .prj with an entry in the catalog." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:46 +msgid "" +"The read driver assumes that multipart polygons follow the specification," +" that is to say the vertices of outer rings should be oriented clockwise " +"on the X/Y plane, and those of inner rings counterclockwise. If a " +"Shapefile is broken w.r.t. that rule, it is possible to define the " +"configuration option :config:`OGR_ORGANIZE_POLYGONS` to DEFAULT to " +"proceed to a full analysis based on topological relationships of the " +"parts of the polygons so that the resulting polygons are correctly " +"defined in the OGC Simple Feature convention." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:68 +msgid "" +"An attempt is made to read the code page setting in the .cpg file, or as " +"a fallback in the LDID/codepage setting from the .dbf file, and use it to" +" translate string fields to UTF-8 on read, and back when writing. LDID " +"\"87 / 0x57\" is treated as ISO-8859-1 which may not be appropriate. The " +":config:`SHAPE_ENCODING` configuration option may be used to override the" +" encoding interpretation of the shapefile with any encoding supported by " +"CPLRecode or to \"\" to avoid any recoding." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:76 +msgid "" +"Starting with GDAL 3.1, the following metadata items are available in the" +" \"SHAPEFILE\" domain:" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:79 +msgid "" +"**LDID_VALUE**\\ =integer: Raw LDID value from the DBF header. Only " +"present if this value is not zero." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:81 +msgid "" +"**ENCODING_FROM_LDID**\\ =string: Encoding name deduced from LDID_VALUE. " +"Only present if LDID_VALUE is present" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:83 +msgid "" +"**CPG_VALUE**\\ =string: Content of the .cpg file. Only present if the " +"file exists." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:85 +msgid "" +"**ENCODING_FROM_CPG**\\ =string: Encoding name deduced from CPG_VALUE. " +"Only present if CPG_VALUE is present" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:87 +msgid "" +"**SOURCE_ENCODING**\\ =string: Encoding used by GDAL to encode/recode " +"strings. If the user has provided the :config:`SHAPE_ENCODING` " +"configuration option or ``ENCODING`` open option have been provided " +"(included to empty value), then their value is used to fill this metadata" +" item. Otherwise it is equal to ENCODING_FROM_CPG if it is present. " +"Otherwise it is equal to ENCODING_FROM_LDID." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:95 +msgid "Spatial and attribute indexing" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:97 +msgid "" +"The OGR Shapefile driver supports spatial indexing and a limited form of " +"attribute indexing." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:100 +msgid "" +"The spatial indexing uses the same .qix quadtree spatial index files that" +" are used by UMN MapServer. Spatial indexing can accelerate spatially " +"filtered passes through large datasets to pick out a small area quite " +"dramatically." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:105 +msgid "" +"It can also use the ESRI spatial index files (.sbn / .sbx), but writing " +"them is not supported currently." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:108 +msgid "" +"To create a spatial index (in .qix format), issue a SQL command of the " +"form" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:115 +msgid "" +"where optional DEPTH specifier can be used to control number of index " +"tree levels generated. If DEPTH is omitted, tree depth is estimated on " +"basis of number of features in a shapefile and its value ranges from 1 to" +" 12." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:120 +msgid "To delete a spatial index issue a command of the form" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:126 +msgid "" +"Otherwise, the `MapServer <http://mapserver.org>`__ shptree utility can " +"be used:" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:133 +msgid "" +"More information is available about this utility at the `MapServer " +"shptree page <http://mapserver.org/utilities/shptree.html>`__" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:136 +msgid "" +"Currently the OGR Shapefile driver only supports attribute indexes for " +"looking up specific values in a unique key column. To create an attribute" +" index for a column issue an SQL command of the form \"CREATE INDEX ON " +"tablename USING fieldname\". To drop the attribute indexes issue a " +"command of the form \"DROP INDEX ON tablename\". The attribute index will" +" accelerate WHERE clause searches of the form \"fieldname = value\". The " +"attribute index is actually stored as a mapinfo format index and is not " +"compatible with any other shapefile applications." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:148 +msgid "" +"The Shapefile driver treats a directory as a dataset, and each Shapefile " +"set (.shp, .shx, and .dbf) as a layer. The dataset name will be treated " +"as a directory name. If the directory already exists it is used and " +"existing files in the directory are ignored. If the directory does not " +"exist it will be created." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:154 +msgid "" +"As a special case attempts to create a new dataset with the extension " +".shp will result in a single file set being created instead of a " +"directory." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:158 +msgid "" +"ESRI shapefiles can only store one kind of geometry per layer " +"(shapefile). On creation this is may be set based on the source file (if " +"a uniform geometry type is known from the source driver), or it may be " +"set directly by the user with the layer creation option SHPT (shown " +"below). If not set the layer creation will fail. If geometries of " +"incompatible types are written to the layer, the output will be " +"terminated with an error." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:166 +msgid "" +"Note that this can make it very difficult to translate a mixed geometry " +"layer from another format into Shapefile format using ogr2ogr, since " +"ogr2ogr has no support for separating out geometries from a source layer." +" See the `FAQ " +"<http://trac.osgeo.org/gdal/wiki/FAQVector#HowdoItranslateamixedgeometryfiletoshapefileformat>`__" +" for a solution." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:173 +msgid "" +"Shapefile feature attributes are stored in an associated .dbf file, and " +"so attributes suffer a number of limitations:" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:176 +msgid "" +"Attribute names can only be up to 10 characters long. The OGR Shapefile " +"driver tries to generate unique field names. Successive duplicate field " +"names, including those created by truncation to 10 characters, will be " +"truncated to 8 characters and appended with a serial number from 1 to 99." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:184 +msgid "a → a, a → a_1, A → A_2;" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:185 +msgid "abcdefghijk → abcdefghij, abcdefghijkl → abcdefgh_1" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:187 +msgid "" +"Only Integer, Integer64, Real, String and Date (not DateTime, just " +"year/month/day) field types are supported. The various list, and binary " +"field types cannot be created." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:191 +msgid "" +"The field width and precision are directly used to establish storage size" +" in the .dbf file. This means that strings longer than the field width, " +"or numbers that don't fit into the indicated field format will suffer " +"truncation." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:196 +msgid "" +"Integer fields without an explicit width are treated as width 9, and " +"extended to 10 or 11 if needed." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:199 +msgid "" +"Integer64 fields without an explicit width are treated as width 18, and " +"extended to 19 or 20 if needed." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:202 +msgid "" +"Real (floating point) fields without an explicit width are treated as " +"width 24 with 15 decimal places of precision." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:205 +msgid "String fields without an assigned width are treated as 80 characters." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:207 +msgid "" +"Also, .dbf files are required to have at least one field. If none are " +"created by the application an \"FID\" field will be automatically created" +" and populated with the record number." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:211 +msgid "" +"The OGR shapefile driver supports rewriting existing shapes in a " +"shapefile as well as deleting shapes. Deleted shapes are marked for " +"deletion in the .dbf file, and then ignored by OGR. To actually remove " +"them permanently (resulting in renumbering of FIDs) invoke the SQL " +"'REPACK <tablename>' via the datasource ExecuteSQL() method." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:217 +msgid "" +"REPACK will also result in .shp being rewritten if a feature geometry has" +" been modified with SetFeature() and resulted in a change of the size the" +" binary encoding of the geometry in the .shp file." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:222 +msgid "" +"Starting with GDAL 2.2, REPACK is also done automatically at file " +"closing, or at FlushCache()/SyncToDisk() time, since shapefiles with " +"holes can cause interoperability issues with other software." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:229 +msgid "" +"The driver knows to auto-extend string and integer fields (up to the 255 " +"bytes limit imposed by the DBF format) to dynamically accommodate for the" +" length of the data to be inserted." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:233 +msgid "" +"It is also possible to force a resize of the fields to the optimal width " +"by issuing a SQL 'RESIZE <tablename>' via the datasource ExecuteSQL() " +"method. This is convenient in situations where the default column width " +"(80 characters for a string field) is bigger than necessary." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:239 +msgid "Spatial extent" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:241 +msgid "" +"Shapefiles store the layer spatial extent in the .SHP file. The layer " +"spatial extent is automatically updated when inserting a new feature in a" +" shapefile. However when updating an existing feature, if its previous " +"shape was touching the bounding box of the layer extent but the updated " +"shape does not touch the new extent, the computed extent will not be " +"correct. It is then necessary to force a recomputation by invoking the " +"SQL 'RECOMPUTE EXTENT ON <tablename>' via the datasource ExecuteSQL() " +"method. The same applies for the deletion of a shape." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:253 +msgid "" +"Geometry: The Shapefile format explicitly uses 32bit offsets and so " +"cannot go over 8GB (it actually uses 32bit offsets to 16bit words), but " +"the OGR shapefile implementation has a limitation to 4GB." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:260 +msgid "" +"However, for compatibility with other software implementation, it is not " +"recommended to use a file size over 2GB for both .SHP and .DBF files." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:263 +msgid "" +"The 2GB_LIMIT=YES layer creation option can be used to strictly enforce " +"that limit. For update mode, the :config:`SHAPE_2GB_LIMIT` configuration " +"option can be set to YES for similar effect. If nothing is set, a warning" +" will be emitted when the 2GB limit is reached." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:271 +msgid "" +"Starting with GDAL 3.1, the driver can also support reading, creating and" +" editing .shz files (ZIP files containing the .shp, .shx, .dbf and other " +"side-car files of a single layer) and .shp.zip files (ZIP files contains " +"one or several layers). Creation and editing involves the creation of " +"temporary files." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:427 +msgid "" +"Starting with GDAL 3.7, for Polygon/MultiPolygon, the default value is " +"NO, with the effect that the winding order of rings will be determined " +"from the outer/inner rings of the input Polygon/MultiPolygon, and not as " +"a post process topological analysis like done in previous GDAL versions, " +"which could cause troubles for non-planar 3D geometries." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:457 +msgid "" +"A merge of two shapefiles 'file1.shp' and 'file2.shp' into a new file " +"'file_merged.shp' is performed like this:" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:465 +msgid "" +"The second command is opening file_merged.shp in update mode, and trying " +"to find existing layers and append the features being copied." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:468 +msgid "The -nln option sets the name of the layer to be copied to." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:470 +msgid "Building a spatial index :" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:476 +msgid "Resizing columns of a DBF file to their optimal size :" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:486 +msgid "`Shapelib Page <http://shapelib.maptools.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:487 +msgid "" +"`User Notes on OGR Shapefile Driver " +"<http://trac.osgeo.org/gdal/wiki/UserDocs/Shapefiles>`__" +msgstr "" + +#: ../../source/drivers/vector/sosi.rst:7 +msgid "SOSI" +msgstr "" + +#: ../../source/drivers/vector/sosi.rst:11 +msgid "This driver requires the FYBA library." +msgstr "" + +#: ../../source/drivers/vector/sosi.rst:16 +msgid "" +"|about-open-options| Starting with GDAL 3.1, the following open options " +"can be specified:" +msgstr "" + +#: ../../source/drivers/vector/sosi.rst:31 +msgid "" +"This example will convert a sosi file to a shape a file where all " +"duplicate fields in a feature will be appended with a comma between." +msgstr "" + +#: ../../source/drivers/vector/sosi.rst:37 +msgid "" +"This example will convert a sosi file to a shape a file where only " +"duplicates for BEITEBRUKERID and OPPHAV will appended with a comma " +"between." +msgstr "" + +#: ../../source/drivers/vector/sosi.rst:43 +msgid "" +"This example will convert a sosi file to a shape a file where for " +"BEITEBRUKERID and OPPHAV will be appended with a semicolon and comma " +"between" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:10 +msgid "" +"OGR optionally supports spatial and non-spatial tables stored in SQLite " +"3.x database files. SQLite is a \"light weight\" single file based RDBMS " +"engine with fairly complete SQL semantics and respectable performance." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:14 +msgid "" +"The driver can handle \"regular\" SQLite databases, as well as Spatialite" +" databases (spatial enabled SQLite databases). The type of an existing " +"database can be checked from the SQLITE debug info value \"OGR style " +"SQLite DB found/ SpatiaLite DB found/SpatiaLite v4 DB found\" obtained by" +" running ``ogrinfo db.sqlite --debug on``" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:20 +msgid "" +"Starting with GDAL 2.2, the SQLite driver can also read databases with " +":ref:`RasterLite2 raster coverages <raster.rasterlite2>`." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:23 +msgid "" +"The SQLite database is essentially typeless, but the SQLite driver will " +"attempt to classify attributes field as text, integer or floating point " +"based on the contents of the first record in a table. Datetime field " +"types are also handled." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:28 +msgid "" +"Starting with GDAL 2.2, the \"JSonStringList\", \"JSonIntegerList\", " +"\"JSonInteger64List\" and \"JSonRealList\" SQLite declaration types are " +"used to map the corresponding OGR StringList, IntegerList, Integer64List " +"and RealList types. The field values are then encoded as JSON arrays, " +"with proper CSV escaping." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:34 +msgid "" +"SQLite databases often do not work well over NFS, or some other networked" +" file system protocols due to the poor support for locking. It is safest " +"to operate only on SQLite files on a physical disk of the local system." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:39 +msgid "" +"SQLite is an optionally compiled in driver. It is not compiled in by " +"default." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:42 +msgid "" +"By default, SQL statements are passed directly to the SQLite database " +"engine. It's also possible to request the driver to handle SQL commands " +"with :ref:`OGR SQL <ogr_sql_dialect>` engine, by passing **\"OGRSQL\"** " +"string to the ExecuteSQL() method, as name of the SQL dialect." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:47 +msgid "" +"The :config:`OGR_SQLITE_SYNCHRONOUS` configuration option has been added." +" When set to OFF, this issues a 'PRAGMA synchronous = OFF' command to the" +" SQLite database. This has the advantage of speeding-up some write " +"operations (e.g. on EXT4 filesystems), but at the expense of data safety " +"w.r.t system/OS crashes. So use it carefully in production environments " +"and read the SQLite `related documentation " +"<http://www.sqlite.org/pragma.html#pragma_synchronous>`__." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:55 +msgid "" +"Any SQLite `pragma <http://www.sqlite.org/pragma.html>`__ can be " +"specified with the :config:`OGR_SQLITE_PRAGMA` configuration option. The " +"syntax is ``OGR_SQLITE_PRAGMA = " +"\"pragma_name=pragma_value[,pragma_name2=pragma_value2]*\"``." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:70 +msgid "\"Regular\" SQLite databases" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:72 +msgid "" +"The driver looks for a geometry_columns table laid out as defined loosely" +" according to OGC Simple Features standards, particularly as defined in " +"`FDO RFC 16 <http://trac.osgeo.org/fdo/wiki/FDORfc16>`__. If found it is " +"used to map tables to layers." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:77 +msgid "" +"If geometry_columns is not found, each table is treated as a layer. " +"Layers with a WKT_GEOMETRY field will be treated as spatial tables, and " +"the WKT_GEOMETRY column will be read as Well Known Text geometry." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:81 +msgid "" +"If geometry_columns is found, it will be used to lookup spatial reference" +" systems in the spatial_ref_sys table." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:84 +msgid "" +"While the SQLite driver supports reading spatial data from records, there" +" is no support for spatial indexing, so spatial queries will tend to be " +"slow (use Spatialite for that). Attributes queries may be fast, " +"especially if indexes are built for appropriate attribute columns using " +"the \"CREATE INDEX ON ( )\" SQL command." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:90 +msgid "" +"The driver also supports reading and writing the following non-linear " +"geometry types :CIRCULARSTRING, COMPOUNDCURVE, CURVEPOLYGON, MULTICURVE " +"and MULTISURFACE. Note: this is not true for Spatialite databases, since " +"those geometry types are not supported by current Spatialite versions." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:97 +msgid "Tables with multiple geometry columns" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:99 +msgid "" +"Layers with multiple geometry columns can be created, modified or read, " +"following new API described in :ref:`rfc-41`" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:103 +msgid "REGEXP operator" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:105 +msgid "" +"By default, the REGEXP operator has no implementation in SQLite. With " +"OGRbuilt against the PCRE library, the REGEXP operator is available in " +"SQL statements run by OGR." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:110 +msgid "Using the SpatiaLite library (Spatial extension for SQLite)" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:112 +msgid "" +"The SQLite driver can read and write SpatiaLite databases. Creating or " +"updating a spatialite database requires explicit linking against " +"SpatiaLite library (version >= 2.3.1). Explicit linking against " +"SpatiaLite library also provides access to functions provided by this " +"library, such as spatial indexes, spatial functions, etc..." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:118 +msgid "A few examples :" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:130 +msgid "Opening with 'VirtualShape:'" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:132 +msgid "(Require Spatialite support)" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:134 +msgid "" +"It is possible to open on-the-fly a shapefile as a VirtualShape with " +"Spatialite. The syntax to use for the datasource is " +"\"VirtualShape:/path/to/shapefile.shp\" (the shapefile must be a \"real\"" +" file)." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:139 +msgid "" +"This gives the capability to use the spatial operations of Spatialite " +"(note that spatial indexes on virtual tables are not available)." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:143 +msgid "The SQLite SQL dialect" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:145 +msgid "" +"The SQLite SQL engine can be used to run SQL queries on any OGR " +"datasource if using the :ref:`sql_sqlite_dialect`." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:149 +msgid "The VirtualOGR SQLite extension" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:151 +msgid "" +"The GDAL/OGR library can be loaded as a `SQLite extension " +"<http://www.sqlite.org/lang_corefunc.html#load_extension>`__. The " +"extension is loaded with the load_extension(gdal_library_name) SQL " +"function, where gdal_library_name is typically libgdal.so on Unix/Linux, " +"gdal110.dll on Windows, etc.." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:157 +msgid "" +"After the extension is loaded, a virtual table, corresponding to a OGR " +"layer, can be created with one of the following SQL statement :" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:169 +msgid "*datasource_name* is the connection string to any OGR datasource." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:170 +msgid "*update_mode* = 0 for read-only mode (default value) or 1 for update mode." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:172 +msgid "*layer_name* = the name of a layer of the opened datasource." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:173 +msgid "" +"*expose_ogr_style* = 0 to prevent the OGR_STYLE special from being " +"displayed (default value) or 1 to expose it." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:176 +msgid "" +"Note: *layer_name* does not need to be specified if the datasource has " +"only one single layer." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:179 +msgid "From the sqlite3 console, a typical use case is :" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:201 +msgid "" +"Alternatively, you can use the " +"*ogr_datasource_load_layers(datasource_name[, update_mode[, prefix]])* " +"function to automatically load all the layers of a datasource." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:216 +msgid "" +"Refer to the :ref:`sql_sqlite_dialect` for an overview of the " +"capabilities of VirtualOGR tables." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:222 +msgid "" +"The SQLite driver supports creating new SQLite database files, or adding " +"tables to existing ones." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:235 +msgid "" +"Relationship retrieval is supported. Relationships will be reported for " +"tables which utilize FOREIGN KEY constraints." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:238 +msgid "" +"Relationship creation is supported since GDAL 3.7, for one-to-many " +"relationships only." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:270 +msgid "" +"The other database must be of a type recognized by this driver, so its " +"geometry blobs are properly recognized (so typically not a GeoPackage " +"one)" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:274 +msgid "Database creation options" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:295 +msgid "" +"Please note: OGR must be linked against *libspatialite* in order to " +"support insert/write on SpatiaLite; if not, *read-only* mode is enforced." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:299 +msgid "" +"Attempting to perform any insert/write on SpatiaLite skipping the " +"appropriate library support simply produces broken (corrupted) DB-files." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:303 +msgid "" +"Important notice: when the underlying *libspatialite* is v.2.3.1 (or any " +"previous version) any Geometry will be casted to 2D [XY], because earlier" +" versions of this library are simply able to support 2D [XY] dimensions. " +"Version 2.4.0 (or any subsequent) is required in order to support 2.5D " +"[XYZ]." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:509 +msgid "" +"SQLite is a Transactional DBMS; while many INSERT statements are executed" +" in close sequence, BEGIN TRANSACTION and COMMIT TRANSACTION statements " +"have to be invoked appropriately (with the OGR_L_StartTransaction() / " +"OGR_L_CommitTransaction()) in order to get optimal performance. By " +"default, if no transaction is explicitly started, SQLite will autocommit " +"on every statement, which will be slow. If using ogr2ogr, its default " +"behavior is to COMMIT a transaction every 100000 inserted rows. The " +"**-gt** argument allows explicitly setting the number of rows for each " +"transaction." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:519 +msgid "" +"SQLite usually has a very minimal memory foot-print; just about 20MB of " +"RAM are reserved to store the internal Page Cache [merely 2000 pages]. " +"This value too may well be inappropriate under many circumstances, most " +"notably when accessing some really huge DB-file containing many tables " +"related to a corresponding Spatial Index. Explicitly setting a much more " +"generously dimensioned internal Page Cache may often help to get a " +"noticeably better performance. You can explicitly set the internal Page " +"Cache size using the configuration option :config:`OGR_SQLITE_CACHE` " +"*value* [*value* being measured in MB]; if your HW has enough available " +"RAM, defining a Cache size as big as 512MB (or even 1024MB) may sometimes" +" help a lot in order to get better performance." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:532 +msgid "" +"Setting the :config:`OGR_SQLITE_SYNCHRONOUS` configuration option to " +"*OFF* might also increase performance when creating SQLite databases " +"(although at the expense of integrity in case of interruption/crash )." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:537 +msgid "" +"If many source files will be collected into the same Spatialite table, it" +" can be much faster to initialize the table without a spatial index by " +"using -lco :lco:`SPATIAL_INDEX=NO` and to create spatial index with a " +"separate command after all the data are appended. Spatial index can be " +"created with ogrinfo command" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:551 +msgid "" +"If a database has gone through editing operations, it might be useful to " +"run a `VACUUM <https://sqlite.org/lang_vacuum.html>`__ query to compact " +"and optimize it." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:563 +msgid "Convert a non-spatial SQLite table into a GeoPackage:" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:579 +msgid "Perform a join between 2 SQLite/Spatialite databases:" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:590 +msgid "" +"Development of the OGR SQLite driver was supported by `DM Solutions Group" +" <http://www.dmsolutions.ca/>`__ and `GoMOOS <http://www.gomoos.org/>`__." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:593 +msgid "" +"Full support for SpatiaLite was contributed by A.Furieri, with funding " +"from `Regione Toscana <http://www.regione.toscana.it/>`__" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:599 +msgid "`http://www.sqlite.org <http://www.sqlite.org/>`__: Main SQLite page." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:600 +msgid "" +"https://www.gaia-gis.it/fossil/libspatialite/index: SpatiaLite extension " +"to SQLite." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:601 +msgid "" +"`FDO RFC 16 <http://trac.osgeo.org/fdo/wiki/FDORfc16>`__: FDO Provider " +"for SQLite" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:603 +msgid ":ref:`RasterLite2 driver <raster.rasterlite2>`" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:4 +msgid "SVG - Scalable Vector Graphics" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:6 +msgid "SVG" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:10 +msgid "" +"OGR has support for SVG reading (if GDAL is built with *expat* library " +"support)." +msgstr "" + +#: ../../source/drivers/vector/svg.rst:13 +msgid "" +"Currently, it will only read SVG files that are the output from Cloudmade" +" Vector Stream Server" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:16 +msgid "All coordinates are relative to the Pseudo-mercator SRS (EPSG:3857)." +msgstr "" + +#: ../../source/drivers/vector/svg.rst:18 +msgid "The driver will return 3 layers :" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:20 +msgid "points" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:21 +msgid "lines" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:22 +msgid "polygons" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:34 +msgid "`W3C SVG page <http://www.w3.org/TR/SVG/>`__" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:35 +msgid "" +"`Cloudmade vector documentation <http://developers.cloudmade.com/wiki" +"/vector-stream-server/Documentation>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:4 +msgid "Storage and eXchange Format - SXF" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:10 +msgid "" +"This driver reads SXF files, open format often associated with Russian " +"GIS Software Panorama." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:13 +msgid "" +"The driver is read only, but supports deletion of data source. The driver" +" supports SXF binary files version 3.0 and higher." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:16 +msgid "The SXF layer support the following capabilities:" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:18 +msgid "Strings as UTF8" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:19 +msgid "Random Read" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:20 +msgid "Fast Feature Count" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:21 +msgid "Fast Get Extent" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:22 +msgid "Fast Set Next By Index" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:24 +msgid "" +"The driver uses classifiers (RSC files) to map feature from SXF to " +"layers. Features that do not belong to any layer are put to the layer " +"named \"Not_Classified\". The layers with zero features are not present " +"in data source." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:29 +msgid "" +"To be used automatically, the RSC file should have the same name as SXF " +"file. User can provide RSC file path using config option " +"**SXF_RSC_FILENAME**. This config option overrides the use of same name " +"RSC." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:34 +msgid "" +"The RSC file usually stores long and short layer name. The long name is " +"usually in Russian, and short in English. The **SXF_LAYER_FULLNAME** " +"config option allows choosing which layer names to use. If " +"SXF_LAYER_FULLNAME is TRUE - the driver uses long names, if FALSE - " +"short." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:40 +msgid "" +"The attributes are read from SXF file. Maximum number of fields is " +"created for the same layer features with different number of attributes. " +"If attribute has a code mapped to RSC file, driver adds only the code " +"(don't get real value from RSC, as the value type may differ from field " +"type)." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:46 +msgid "" +"If config option **SXF_SET_VERTCS** set to ON, the layers spatial " +"reference will include vertical coordinate system description if exist." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:49 +msgid "Since GDAL 3.1 config options can be passed as driver open options." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:61 +msgid "`Panorama web page <http://gisinfo.ru>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:62 +msgid "" +"`SXF binary format description v.4 (rus) - pdf " +"<http://gistoolkit.ru/download/doc/sxf4bin.pdf>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:64 +msgid "" +"`SXF binary format description v.4 (rus) - doc " +"<http://gistoolkit.ru/download/classifiers/formatsxf.zip>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:66 +msgid "" +"`SXF format description v.3 (rus) <http://loi.sscc.ru/gis/formats/Format-" +"geo/sxf/sxf3-231.txt>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:68 +msgid "" +"`RSC format description (rus) " +"<http://gistoolkit.ru/download/classifiers/formatrsc.zip>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:70 +msgid "" +"`Test spatial data in SXF format (rus) " +"<http://www.gisinfo.ru/price/price_map.htm>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:72 +msgid "" +"`Some RSC files (rus) " +"<http://www.gisinfo.ru/classifiers/classifiers.htm>`__" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:6 +msgid "TIGER" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:10 +msgid "TIGER/Line file sets are support for read access." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:12 +msgid "" +"TIGER/Line files are a digital database of geographic features, such as " +"roads, railroads, rivers, lakes, political boundaries, census statistical" +" boundaries, etc. covering the entire United States. The data base " +"contains information about these features such as their location in " +"latitude and longitude, the name, the type of feature, address ranges for" +" most streets, the geographic relationship to other features, and other " +"related information. They are the public product created from the Census " +"Bureau's TIGER (Topologically Integrated Geographic Encoding and " +"Referencing) data base of geographic information. TIGER was developed at " +"the Census Bureau to support the mapping and related geographic " +"activities required by the decennial census and sample survey programs." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:24 +msgid "" +"Note that the TIGER/Line product does not include census demographic " +"statistics. Those are sold by the Census Bureau in a separate format (not" +" directly supported by FME), but those statistics do relate back to " +"census blocks in TIGER/Line files." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:29 +msgid "" +"To open a TIGER/Line dataset, select the directory containing one or more" +" sets of data files. The regions are counties, or county equivalents. " +"Each county consists of a series of files with a common basename, and " +"different extensions. For instance, county 1 in state 26 (Michigan) " +"consists of the following file set in Tiger98." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:55 +msgid "" +"The TIGER/Line coordinate system is hardcoded to NAD83 lat/long degrees. " +"This should be appropriate for all recent years of TIGER/Line production." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:59 +msgid "There is no update or creation support in the TIGER/Line driver." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:61 +msgid "" +"The reader was implemented for TIGER/Line 1998 files, but some effort has" +" gone into ensuring compatibility with 1992, 1995, 1997, 1999, 2000, " +"2002, 2003 and 2004 TIGER/Line products as well. The 2005 products have " +"also been reported to work fine. It is believe that any TIGER/Line " +"product from the 1990's should work with the reader, with the possible " +"loss of some version specific information." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:76 +msgid "Feature Representation" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:78 +msgid "" +"With a few exceptions, a feature is created for each record of a " +"TIGER/Line data file. Each file (i.e. .RT1, .RTA) is translated to an " +"appropriate OGR feature type, with attribute names matching those in the " +"TIGER/Line product manual." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:83 +msgid "" +"The TIGER/Line RT (record type), and VERSION attributes are generally " +"discarded, but the MODULE attribute is added to each feature. The MODULE " +"attribute contains the basename (eg. TGR26001) of the county module from " +"which the feature originated. For some keys (such as LAND, POLYID, and " +"CENID) this MODULE attribute is needed to make the key unique when the " +"dataset (directory) consists of more than one county of data." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:90 +msgid "" +"Following is a list of feature types, and their relationship to the " +"TIGER/Line product." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:94 +msgid "CompleteChain" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:96 +msgid "" +"A CompleteChain is a polyline with an associated TLID (TIGER/Line ID). " +"The CompleteChain features are established from a type 1 record (Complete" +" Chain Basic Data Record), and if available it is associated type 3 " +"record (Complete Chain Geographic Entity Codes). As well, any type 2 " +"records (Complete Chain Shape Coordinates) available are used to fill in " +"intermediate shape points on the arc. The TLID is the primary key, and is" +" unique within the entire national TIGER/Line coverage." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:104 +msgid "These features always have a line geometry." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:107 +msgid "AltName" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:109 +msgid "" +"These features are derived from the type 4 record (Index to Alternate " +"Feature Identifiers), and relate a TLID to 1 to 4 alternate feature name " +"numbers (the FEAT attribute) which are kept separately as FeatureIds " +"features. The standard reader pipeline attaches the names from the " +"FeatureIds features as array attributes ALT_FEDIRS{}, ALT_FEDIRP{}, " +"ALT_FENAME{} and ALT_FETYPE{}. The ALT_FENAME{} is a list of feature " +"names associated with the TLID on the AltName feature." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:117 +msgid "" +"Note that zero, one or more AltName records may exist for a given TLID, " +"and each AltName record can contain between one and four alternate names." +" Because it is still very difficult to utilize AltName features to relate" +" altername names to CompleteChains, it is anticipated that the standard " +"reader pipeline for TIGER/Line files will be upgraded in the future, " +"resulting in a simplification of alternate names." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:124 +#: ../../source/drivers/vector/tiger.rst:136 +#: ../../source/drivers/vector/tiger.rst:147 +#: ../../source/drivers/vector/tiger.rst:170 +#: ../../source/drivers/vector/tiger.rst:179 +#: ../../source/drivers/vector/tiger.rst:201 +#: ../../source/drivers/vector/tiger.rst:210 +#: ../../source/drivers/vector/tiger.rst:222 +#: ../../source/drivers/vector/tiger.rst:239 +msgid "These features have no associated geometry." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:127 +msgid "FeatureIds" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:129 +msgid "" +"These features are derived from type 5 (Complete Chain Feature " +"Identifiers) records. Each feature contains a feature name (FENAME), and " +"it is associated feature id code (FEAT). The FEAT attribute is the " +"primary key, and is unique within the county module. FeatureIds have a " +"one to many relationship with AltName features, and KeyFeatures features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:139 +msgid "ZipCodes" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:141 +msgid "" +"These features are derived from type 6 (Additional Address Range and ZIP " +"Code Data) records. These features are intended to augment the ZIP Code " +"information kept directly on CompleteChain features, and there is a many " +"to one relationship between ZipCodes features and CompleteChain features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:150 +msgid "Landmarks" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:152 +msgid "" +"These features are derived from type 7 (Landmark Features) records. They " +"relate to point, or area landmarks. For area landmarks there is a one to " +"one relationship with an AreaLandmark record. The LAND attribute is the " +"primary key, and is unique within the county module." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:157 +msgid "" +"These features may have an associated point geometry. Landmarks " +"associated with polygons will not have the polygon geometry attached. It " +"would need to be collected (via the AreaLandmark feature) from a Polygon " +"feature." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:163 +msgid "AreaLandmarks" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:165 +msgid "" +"These features are derived from type 8 (Polygons Linked to Area " +"Landmarks) records. Each associates a Landmark feature (attribute LAND) " +"with a Polygon feature (attribute POLYID). This feature has a many to " +"many relationship with Polygon features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:173 +msgid "KeyFeatures" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:175 +msgid "" +"These features are derived from type 9 (Polygon Geographic Entity Codes) " +"records. They may be associated with a FeatureIds feature (via the FEAT " +"attribute), and a Polygon feature (via the POLYID attribute)." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:182 +msgid "Polygon" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:184 +msgid "" +"These features are derived from type A (Polygon Geographic Entity Codes) " +"records and if available the related type S (Polygon Additional " +"Geographic Entity Codes) records. The POLYID attribute is the primary " +"key, uniquely identifying a polygon within a county module." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:189 +msgid "" +"These features do not have any geometry associated with them as read by " +"the OGR TIGER driver. It needs to be externally related using the " +"PolyChainLink. The gdal/pymod/samples/tigerpoly.py script may be used to " +"read a TIGER dataset and extract the polygon layer **with geometry** as a" +" shapefile." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:196 +msgid "EntityNames" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:198 +msgid "These features are derived from type C (Geographic Entity Names) records." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:204 +msgid "IDHistory" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:206 +msgid "" +"These features are derived from type H (TIGER/Line ID History) records. " +"They can be used to trace the splitting, merging, creation and deletion " +"of CompleteChain features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:213 +msgid "PolyChainLink" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:215 +msgid "" +"These features are derived from type I (Link Between Complete Chains and " +"Polygons) records. They are normally all consumed by the standard reader " +"pipeline while attaching CompleteChain geometries to Polygon features to " +"establish their polygon geometries. PolyChainLink features have a many to" +" one relationship with Polygon features, and a one to one relationship " +"with CompleteChain features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:225 +msgid "PIP" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:227 +msgid "" +"These features are derived from type P (Polygon Internal Point) records. " +"They relate to a Polygon feature via the POLYID attribute, and can be " +"used to establish an internal point for Polygon features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:231 +msgid "These features have a point geometry." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:234 +msgid "ZipPlus4" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:236 +msgid "" +"These features are derived from type Z (ZIP+4 Codes) records. ZipPlus4 " +"features have a many to one relationship with CompleteChain features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:244 +msgid "" +"http://www.census.gov/geo/www/tiger/: More information on the TIGER/Line " +"file format, and data product can be found on this U.S. Census web page." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:5 +msgid "TileDB -- TileDB vector" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:13 +msgid "GDAL can read and write TileDB sparse arrays containing vector data." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:26 +msgid "Supported datasets" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:28 +msgid "" +"The driver can read TileDB sparse arrays that contain at least 2 " +"dimensions of type Float64. By default dimensions names ``_X`` and ``_Y``" +" are looked up, but this can be customized with the :oo:`DIM_X` and " +":oo:`DIM_Y` open options." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:32 +msgid "" +"Attributes (or extra dimensions) of the following TileDB data types are " +"recognized as OGR fields: Bool, Int16, Int32, Int64, Float32, Float64, " +"String_ASCII, String_UTF8, Blob, varying size UInt8 (as Binary), " +"DateTime_Day, DateTime_MS, Time_MS. Attributes of other data types will " +"be ignored." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:37 +msgid "" +"If a ``wkb_geometry`` named attribute of type Binary is found, it is used" +" as the geometry column, and is assumed to contain WKB encoded " +"geometries. If there is no such column, Point geometries are assumed and " +"the X, Y (and optional Z) dimensions are used to create the corresponding" +" OGR point geometries." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:44 +msgid "Dataset connection string" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:46 +msgid "" +"Valid dataset connection strings are paths to a local or remote TileDB " +"sparse array, or to a local or remote TileDB group that contains TileDB " +"sparse arrays." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:52 +msgid "" +"The bounding box of OGR spatial filters is forwarded to the TileDB query " +"engine." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:54 +msgid "" +"OGR attribute filters are translated to TileDB query conditions for the " +"following elements:" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:58 +msgid "OR" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:59 +msgid "NOT" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:60 +msgid "" +"comparisons of the form \"attribute_name operator constant\" where " +"operator is ``=``, ``<>``, ``<``, ``<=``, ``>``, ``>=``" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:62 +msgid "attribute_name IS NULL" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:63 +msgid "attribute_name IS NOT NULL" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:64 +msgid "attribute_name IN (value1, ... valueN)" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:65 +msgid "attribute_name BETWEEN min_val AND max_val" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:67 +#, python-format +msgid "" +"Other OGR attribute filter elements may be used, but this may cause the " +"filter to be fully or partially evaluated on OGR side. For example, given" +" the filter \"int_attribute = 5 AND string_attribute LIKE '%foo%'\", the " +"condition on int_attribute will be translated as a TileDB query " +"condition, and the right side of the AND operation will be evaluated as a" +" post-filter on OGR side." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:74 +msgid "Arrow C Stream data interface" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:76 +msgid "" +"The driver has an efficient implementation of the :ref:`Arrow C Stream " +"data interface <vector_api_tut_arrow_stream>`" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:79 +msgid "" +"The ``INCLUDE_FID=YES/NO`` and ``MAX_FEATURES_IN_BATCH=number`` options " +"of :cpp:func:`OGRLayer::GetArrowStream()` are supported. If " +"MAX_FEATURES_IN_BATCH is not specified, it defaults to the value of the " +"BATCH_SIZE open option." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:86 +msgid "" +"By default, when creating a layer, the driver will create a TileDB sparse" +" array at the location of the dataset connection string. Consequently " +"only one OGR layer can be created in that mode. If several layers need to" +" be created and accessible through a OGR dataset connection, a TileDB " +"group needs to be created to point to the different arrays (layers), by " +"specifying the :dsco:`CREATE_GROUP=YES` dataset creation option." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:93 +msgid "The driver supports appending features to exiting layers." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:95 +msgid "" +"The driver does not support adding new fields to a layer where features " +"have already been written." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:242 +msgid ":ref:`TileDB raster <raster.tiledb>` documentation page" +msgstr "" + +#: ../../source/drivers/vector/topojson.rst:6 +msgid "TopoJSON" +msgstr "" + +#: ../../source/drivers/vector/topojson.rst:13 +msgid "" +"The driver can read the `TopoJSON format <https://github.com/topojson" +"/topojson-specification/blob/master/README.md>`__" +msgstr "" + +#: ../../source/drivers/vector/topojson.rst:31 +msgid "" +"Plain text file with TopoJSON data - identified from the file extension " +".json or .topojson" +msgstr "" + +#: ../../source/drivers/vector/topojson.rst:33 +msgid "Text passed directly and encoded in Topo JSON" +msgstr "" + +#: ../../source/drivers/vector/topojson.rst:35 +msgid "" +"Starting with GDAL 2.3, the URL/filename/text might be prefixed with " +"TopoJSON: to avoid any ambiguity with other drivers. Alternatively, " +"starting with GDAL 3.10, specifying the ``-if TopoJSON`` option to " +"command line utilities accepting it, or ``TopoJSON`` as the only value of" +" the ``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the " +"driver to recognize the passed URL/filename/text." +msgstr "" + +#: ../../source/drivers/vector/topojson.rst:46 +msgid "" +"`TopoJSON Format Specification <https://github.com/topojson/topojson-" +"specification/blob/master/README.md>`__" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:4 +msgid "VDV - VDV-451/VDV-452/INTREST Data Format" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:8 +msgid "VDV" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:12 +msgid "" +"This driver can read and create text files following the VDV-451 file " +"format, which is a text format similar to CSV files, potentially " +"containing several layers within the same file." +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:16 +msgid "It supports in particular reading 2 \"profiles\" :" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:18 +msgid "(read/write) VDV-452 standard for route network / timetable" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:19 +msgid "" +"(read/only) \"INTREST Data format\" used by the `Austrian official open " +"government street graph <https://www.data.gv.at/katalog/dataset/3fefc838" +"-791d-4dde-975b-a4131a54e7c5>`__" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:23 +msgid "" +"The generic reader/writer for VDV-451/VDV-452 can support arbitrarily " +"large files. For the INTREST data case, for combined layers in a single " +"file, the driver ingests the whole file in memory to reconstruct the Link" +" layer." +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:28 +msgid "" +"Interleave reading among layers is supported in files with multiple " +"layers." +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:43 +msgid "" +"The driver can create new layers (either in the same file, or in separate" +" files in the same directory). It can append a new layer into an existing" +" file, but it cannot append/edit/delete features to an existing layer, or" +" modify the attribute structure of an existing layer after features have " +"been written." +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:154 +msgid "" +"`VDV-451 file format <https://www.vdv.de/vdv-" +"schrift-451.pdfx?forced=false>`__ (German)" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:157 +msgid "" +"`VDV-452 data model " +"<https://www.vdv.de/service/downloads_onp.aspx?id=4328&forced=false>`__ " +"(German)" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:159 +msgid "" +"`Austrian INTREST data format " +"<https://gip.gv.at/assets/downloads/1908_dokumentation_gipat_ogd.pdf>`__ " +"(German)" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:4 +msgid "VFK - Czech Cadastral Exchange Data Format" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:6 +msgid "VFK" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:10 +msgid "" +"This driver reads VFK files, i.e. data in the *Czech cadastral exchange " +"data format*. The VFK file is recognized as an datasource with multiple " +"layers." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:14 +msgid "The driver is compiled only if GDAL is *built with SQLite support*." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:16 +msgid "" +"Points are represented as wkbPoints, lines and boundaries as " +"wkbLineStrings and areas as wkbPolygons. wkbMulti\\* features are not " +"used. Feature types cannot be mixed in one layer." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:30 +msgid "" +"|about-open-options| Starting with GDAL 2.3, the following open options " +"can be specified:" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:98 +msgid "Internal working and performance tweaking" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:100 +msgid "" +"If backend SQLite database already exists then the driver reads features " +"directly from the database and not from input VFK file given as an input " +"datasource. This causes significant performance gain when reading " +"features by the driver." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:105 +msgid "" +"The driver reads by default all data blocks from VFK file when building " +"backend SQLite database. When configuration option " +":config:`OGR_VFK_DB_READ_ALL_BLOCKS` =NO is given, the driver reads only " +"data blocks which are requested by the user. This can be useful when the " +"user want to process only part of VFK data." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:114 +msgid "" +"Data related to a single cadastral area is typically distributed in " +"multiple VFK files. Example below is based on `sample VFK files " +"<https://services.cuzk.cz/vfk/anonym/>`__ provided by the Czech State " +"Administration of Land Surveying and Cadastre. In order to process all " +"VFK files related to a single cadastral area (in example below with ID " +"602515), the configuration option :config:`OGR_VFK_DB_NAME` has to be " +"defined." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:133 +msgid "Datasource name" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:135 +msgid "Datasource name is a full path to the VFK file." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:137 +msgid "" +"The driver supports reading files managed by VSI Virtual File System API," +" which include \"regular\" files, as well as files in the /vsizip/, " +"/vsigzip/, and /vsicurl/ read-only domains." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:141 +msgid "" +"Since GDAL 2.2 also a full path to the backend SQLite database can be " +"used as an datasource. By default, such datasource is read by SQLite " +"driver. If configuration option :config:`OGR_VFK_DB_READ` =YES is given, " +"such datasource is opened by VFK driver instead." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:147 +msgid "Layer names" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:149 +msgid "VFK data blocks are used as layer names." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:155 +msgid "Attribute filter" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:157 +msgid "" +"An internal SQL engine is used to evaluate the expression. Evaluation is " +"done once when the attribute filter is set." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:161 +msgid "Spatial filter" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:163 +msgid "" +"Bounding boxes of features stored in topology structure are used to " +"evaluate if a features matches current spatial filter. Evaluation is done" +" once when the spatial filter is set." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:168 +msgid "References" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:170 +msgid "" +"`OGR VFK Driver Implementation Issues " +"<https://www.researchgate.net/publication/238067945_OGR_VFK_Driver_Implementation_Issues>`__" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:172 +msgid "" +"`Czech cadastral exchange data format documentation " +"<http://www.cuzk.cz/Dokument.aspx?PRARESKOD=998&MENUID=0&AKCE=DOC:10-VF_ISKNTEXT>`__" +" (in Czech)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:4 +msgid "VRT -- Virtual Format" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:10 +msgid "" +"OGR Virtual Format is a driver that transforms features read from other " +"drivers based on criteria specified in an XML control file. It is " +"primarily used to derive spatial layers from flat tables with spatial " +"information in attribute columns. It can also be used to associate " +"coordinate system information with a datasource, merge layers from " +"different datasources into a single data source, or even just to provide " +"an anchor file for access to non-file oriented datasources." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:18 +msgid "The virtual files are currently normally prepared by hand." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:30 +msgid "" +"The CreateFeature(), SetFeature() and DeleteFeature() operations are " +"supported on a layer of a VRT dataset, if the following conditions are " +"met :" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:34 +msgid "the VRT dataset is opened in update mode" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:35 +msgid "the underlying source layer supports those operations" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:36 +msgid "the *SrcLayer* element is used (as opposed to the *SrcSQL* element)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:37 +msgid "" +"the FID of the VRT features is the same as the FID of the source " +"features, that is to say, the *FID* element is not specified" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:41 +msgid "Virtual File Format" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:43 +msgid "" +"The root element of the XML control file is **OGRVRTDataSource**. It has " +"an **OGRVRTLayer** (or **OGRVRTWarpedLayer** or **OGRVRTUnionLayer**) " +"child for each layer in the virtual datasource, and a **Metadata** " +"element." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:48 +msgid "" +"An XML schema of the OGR VRT format is provided in " +":source_file:`ogr/ogrsf_frmts/vrt/data/ogrvrt.xsd`. When GDAL is " +"configured with libXML2 support, that schema will be used to validate the" +" VRT documents. Non-conformities will be reported only as warnings. That " +"validation can be disabled by setting the :config:`GDAL_XML_VALIDATION` " +"configuration option to \"NO\"." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:56 +msgid "Metadata element" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:58 +msgid "" +"**Metadata** (optional): This element contains a list of metadata " +"name/value pairs associated with the dataset as a whole. It has <MDI> " +"(metadata item) subelements which have a \"key\" attribute and the value " +"as the data of the element. The Metadata element can be repeated multiple" +" times, in which case it must be accompanied with a \"domain\" attribute " +"to indicate the name of the metadata domain." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:66 +msgid "OGRVRTLayer element" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:68 +msgid "" +"A **OGRVRTLayer** element should have a **name** attribute with the layer" +" name, and may have the following subelements:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:71 +msgid "" +"**SrcDataSource** (mandatory): The value is the name of the datasource " +"that this layer will be derived from. The element may optionally have a " +"**relativeToVRT** attribute which defaults to \"0\", but if \"1\" " +"indicates that the source datasource should be interpreted as relative to" +" the virtual file. This can be any OGR supported dataset, including ODBC," +" CSV, etc. The element may also have a **shared** attribute to control " +"whether the datasource should be opened in shared mode. Defaults to OFF " +"for SrcLayer use and ON for SrcSQL use." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:80 +msgid "" +"**OpenOptions** (optional): This element may list a number of open " +"options as child elements of the form <OOI " +"key=\"key_name\">value_name</OOI>" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:84 +msgid "" +"**Metadata** (optional): This element contains a list of metadata " +"name/value pairs associated with the layer as a whole. It has <MDI> " +"(metadata item) subelements which have a \"key\" attribute and the value " +"as the data of the element. The Metadata element can be repeated multiple" +" times, in which case it must be accompanied with a \"domain\" attribute " +"to indicate the name of the metadata domain." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:91 +msgid "" +"**SrcLayer** (optional): The value is the name of the layer on the source" +" data source from which this virtual layer should be derived. If this " +"element isn't provided, then the SrcSQL element must be provided." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:95 +msgid "" +"**SrcSQL** (optional): An SQL statement to execute to generate the " +"desired layer result. This should be provided instead of the SrcLayer for" +" statement derived results. Some limitations may apply for SQL derived " +"layers. An optional **dialect** attribute can be specified on the SrcSQL " +"element to specify which SQL \"dialect\" should be used : possible values" +" are currently :ref:`OGRSQL <ogr_sql_dialect>` or :ref:`SQLITE " +"<sql_sqlite_dialect>`. If *dialect* is not specified, the default dialect" +" of the datasource will be used." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:105 +msgid "" +"**FID** (optional): Name of the source attribute column from which the " +"FID of features should be derived. If not provided, the FID of the source" +" features will be used directly." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:109 +msgid "Logic for GDAL >= 2.4: Different situations are possible:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:115 +msgid "" +"A FID column will be reported as source_field_name with the content of " +"source field source_field_name." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:122 +msgid "" +"A FID column will be reported as dest_field_name with the content of " +"source field source_field_name. dest_field_name can potentially be set to" +" the empty string." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:130 +msgid "" +"No FID column is reported. The FID value of VRT features is the FID value" +" of the source features." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:137 +msgid "" +"A FID column will be reported as dest_field_name with the content of the " +"implicit source FID column. The FID value of VRT features is the FID " +"value of the source features." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:141 +msgid "" +"Logic for GDAL < 2.4: The layer will report the FID column name only if " +"it is also reported as a regular field. A \"name\" attribute can be " +"specified on the FID element so that the FID column name is always " +"reported." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:146 +msgid "" +"**Style** (optional): Name of the attribute column from which the style " +"of features should be derived. If not provided, the style of the source " +"features will be used directly." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:150 +msgid "" +"**GeometryType** (optional): The geometry type to be assigned to the " +"layer. If not provided it will be taken from the source layer. The value " +"should be one of \"wkbNone\", \"wkbUnknown\", \"wkbPoint\", " +"\"wkbLineString\", \"wkbPolygon\", \"wkbMultiPoint\", " +"\"wkbMultiLineString\", \"wkbMultiPolygon\", or " +"\"wkbGeometryCollection\". Optionally \"25D\" may be appended to mark it " +"as including Z coordinates. Defaults to \"wkbUnknown\" indicating that " +"any geometry type is allowed." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:158 +msgid "" +"**LayerSRS** (optional): The value of this element is the spatial " +"reference to use for the layer. If not provided, it is inherited from the" +" source layer. The value may be WKT or any other input that is accepted " +"by the OGRSpatialReference::SetUserInput() method. If the value is NULL, " +"then no SRS will be used for the layer." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:164 +msgid "" +"**GeometryField** (optional): This element is used to define how the " +"geometry for features should be derived." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:167 +msgid "" +"The GeometryField element can be repeated as many times as necessary to " +"create multiple geometry fields. If no **GeometryField** element is " +"specified, all the geometry fields of the source layer will be exposed by" +" the VRT layer. In order not to expose any geometry field of the source " +"layer, you need to specify OGRVRTLayer-level **GeometryType** element to " +"wkbNone." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:174 +msgid "The following attributes can be defined:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:176 +msgid "" +"**name** = string (recommended, and mandatory if the VRT will expose " +"multiple geometry fields)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:178 +msgid "" +"Name that will be used to define the VRT geometry field name. If not set," +" empty string is used." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:181 +msgid "**encoding** = Direct/WKT/WKB/PointFromColumns (optional)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:183 +msgid "Type of geometry encoding." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:185 +msgid "" +"If the encoding is \"Direct\" or not specified, then the **field** " +"attribute must be set to the name of the source geometry field, if there " +"are multiple source geometry fields. If neither **encoding** nor " +"**field** are specified, it is assumed that the name of source geometry " +"field is the value of the **name** attribute." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:191 +msgid "" +"If the encoding is \"WKT\" or \"WKB\" then the **field** attribute must " +"be set to the name of the source field containing the WKT or WKB " +"geometry." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:194 +msgid "" +"If the encoding is \"PointFromColumns\" then the **x**, **y**, **z** and " +"**m** attributes must be set to the names of the columns to be used for " +"the X, Y, Z and M coordinates. The **z** and **m** attributes are " +"optional." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:198 +msgid "**field** = string (conditional)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:200 +msgid "" +"Name of the source field (or source geometry field for **encoding** = " +"Direct) from which this GeometryField should fetch geometries. This must " +"be set if **encoding** is WKT or WKB." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:204 +msgid "**x**, **y**, **z**, **m** = string (conditional)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:206 +msgid "" +"Name of the source fields for the X, Y, Z and M coordinates when " +"**encoding** = PointFromColumns" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:209 +msgid "**reportSrcColumn** = true/false (optional)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:211 +msgid "" +"Specify whether the source geometry fields (the fields set in the " +"**field**, **x**, **y**, **z**, **m** attributes) should also be included" +" as fields of the VRT layer. It defaults to true. If set to false, the " +"source geometry fields will only be used to build the geometry of the " +"features of the VRT layer." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:217 +msgid "" +"Note that reportSrcColumn=true is taken into account only if no explicit " +"**Field** element is defined and when **encoding** is not \"Direct\". If " +"at least one field is explicitly defined, and reporting of the source " +"geometry field is desired, an explicit **Field** element for it must be " +"defined." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:222 +msgid "**nullable** = true/false (optional)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:224 +msgid "" +"The optional **nullable** attribute can be used to specify whether the " +"geometry field is nullable. It defaults to \"true\"." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:228 +msgid "The following child elements of **GeometryField** can be defined:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:230 +msgid "" +"**GeometryType** (optional) : same syntax as OGRVRTLayer-level " +"**GeometryType**. Useful when there are multiple geometry fields." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:232 +msgid "" +"**SRS** (optional) : same syntax as OGRVRTLayer-level **LayerSRS** (note " +"SRS vs LayerSRS). Useful when there are multiple geometry fields." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:234 +msgid "" +"**SrcRegion** (optional) : same syntax as OGRVRTLayer-level " +"**SrcRegion**. Useful when there are multiple geometry fields." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:236 +msgid "" +"**ExtentXMin**, **ExtentYMin**, **ExtentXMax** and **ExtentXMax** " +"(optional) : same syntax as OGRVRTLayer-level elements of same name. " +"Useful when there are multiple geometry fields." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:239 +msgid "" +"**XYResolution** (optional, GDAL >= 3.9): Resolution for the coordinate " +"precision of the X and Y coordinates. Expressed in the units of the X and" +" Y axis of the SRS" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:242 +msgid "" +"**ZResolution** (optional, GDAL >= 3.9): Resolution for the coordinate " +"precision of the Z coordinates. Expressed in the units of the Z axis of " +"the SRS" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:245 +msgid "" +"**MResolution** (optional, GDAL >= 3.9): Resolution for the coordinate " +"precision of the M coordinates." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:249 +msgid "" +"**SrcRegion** (optional) : This element is used to define an initial " +"spatial filter for the source features. This spatial filter will be " +"combined with any spatial filter explicitly set on the VRT layer with the" +" SetSpatialFilter() method. The value of the element must be a valid WKT " +"string defining a polygon. An optional **clip** attribute can be set to " +"\"TRUE\" to clip the geometries to the source region, otherwise the " +"source geometries are not modified." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:257 +msgid "" +"**Field** (optional): One or more attribute fields may be defined with " +"Field elements. If no Field elements are defined, the fields of the " +"source layer/sql will be defined on the VRT layer. The Field may have the" +" following attributes:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:262 +msgid "**name** (required): the name of the field." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:263 +msgid "" +"**type**: the field type, one of \"Integer\", \"IntegerList\", \"Real\", " +"\"RealList\", \"String\", \"StringList\", \"Binary\", \"Date\", \"Time\"," +" or \"DateTime\". Defaults to \"String\"." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:266 +msgid "" +"**subtype**: the field subtype, one of \"None\", \"Boolean\", \"Int16\", " +"\"Float32\". Defaults to \"None\"." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:268 +msgid "**width**: the field width. Defaults to unknown." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:269 +msgid "**precision**: the field width. Defaults to zero." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:270 +msgid "" +"**src**: the name of the source field to be copied to this one. Defaults " +"to the value of \"name\"." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:272 +msgid "" +"**nullable** can be used to specify whether the field is nullable. It " +"defaults to \"true\"." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:274 +msgid "" +"**unique** can be used to specify whether the field has a unique " +"constraint. It defaults to \"false\". (GDAL >= 3.2)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:276 +msgid "**alternativeName**: the field alternative name. (GDAL >= 3.7)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:277 +msgid "**comment**: the field comment. (GDAL >= 3.7)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:279 +msgid "" +"**FeatureCount** (optional) : This element is used to define the feature " +"count of the layer (when no spatial or attribute filter is set). This can" +" be useful on static data, when getting the feature count from the source" +" layer is slow." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:284 +#: ../../source/drivers/vector/vrt.rst:303 +msgid "" +"**ExtentXMin**, **ExtentYMin**, **ExtentXMax** and **ExtentXMax** " +"(optional) : Those elements are used to define the extent of the layer. " +"This can be useful on static data, when getting the extent from the " +"source layer is slow." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:290 +msgid "OGRVRTWarpedLayer element" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:292 +msgid "" +"A **OGRVRTWarpedLayer** element is used to do on-the-fly reprojection of " +"a source layer. It may have the following subelements:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:296 +msgid "" +"**OGRVRTLayer**, **OGRVRTWarpedLayer** or **OGRVRTUnionLayer** " +"(mandatory): the source layer to reproject." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:298 +msgid "" +"**SrcSRS** (optional): The value of this element is the spatial reference" +" to use for the layer before reprojection. If not specified, it is " +"deduced from the source layer." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:301 +msgid "" +"**TargetSRS** (mandatory): The value of this element is the spatial " +"reference to use for the layer after reprojection." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:307 +msgid "" +"**WarpedGeomFieldName** (optional) : The value of this element is the " +"geometry field name of the source layer to wrap. If not specified, the " +"first geometry field will be used. If there are several geometry fields, " +"only the one matching WarpedGeomFieldName will be warped; the other ones " +"will be untouched." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:314 +msgid "OGRVRTUnionLayer element" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:316 +msgid "" +"A **OGRVRTUnionLayer** element is used to concatenate the content of " +"source layers. It should have a **name** and may have the following " +"subelements:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:320 +msgid "" +"**OGRVRTLayer**, **OGRVRTWarpedLayer** or **OGRVRTUnionLayer** (mandatory" +" and may be repeated): a source layer to add in the union." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:322 +msgid "" +"**PreserveSrcFID** (optional) : may be ON or OFF. If set to ON, the FID " +"from the source layer will be used, otherwise a counter will be used. " +"Defaults to OFF." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:325 +msgid "" +"**SourceLayerFieldName** (optional) : if specified, an additional field " +"(named with the value of SourceLayerFieldName) will be added in the layer" +" field definition. For each feature, the value of this field will be set " +"with the name of the layer from which the feature comes from." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:330 +msgid "" +"**GeometryType** (optional) : see above for the syntax. If not specified," +" the geometry type will be deduced from the geometry type of all source " +"layers." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:333 +msgid "" +"**LayerSRS** (optional) : see above for the syntax. If not specified, the" +" SRS will be the SRS of the first source layer." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:335 +msgid "" +"**FieldStrategy** (optional, exclusive with **Field** or " +"**GeometryField**) : may be **FirstLayer** to use the fields from the " +"first layer found, **Union** to use a super-set of all the fields from " +"all source layers, or **Intersection** to use a sub-set of all the common" +" fields from all source layers. Defaults to **Union**." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:340 +msgid "" +"**Field** (optional, exclusive with **FieldStrategy**) : see above for " +"the syntax. Note: the src attribute is not supported in the context of a " +"OGRVRTUnionLayer element (field names are assumed to be identical)." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:344 +msgid "" +"**GeometryField** (optional, exclusive with **FieldStrategy**): the " +"**name** attribute and the following sub-elements **GeometryType**, " +"**SRS** and **Extent[X|Y][Min|Max]** are available." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:347 +msgid "**FeatureCount** (optional) : see above for the syntax" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:348 +msgid "" +"**ExtentXMin**, **ExtentYMin**, **ExtentXMax** and **ExtentXMax** " +"(optional) : see above for the syntax" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:352 +msgid "Example: ODBC Point Layer" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:354 +msgid "" +"In the following example (disease.ovf) the worms table from the ODBC " +"database DISEASE is used to form a spatial layer. The virtual file uses " +"the \"x\" and \"y\" columns to get the spatial location. It also marks " +"the layer as a point layer, and as being in the WGS84 coordinate system." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:372 +msgid "Example: Renaming attributes" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:374 +msgid "" +"It can be useful in some circumstances to be able to rename the field " +"names from a source layer to other names. This is particularly true when " +"you want to transcode to a format whose schema is fixed, such as GPX " +"(<name>, <desc>, etc.). This can be accomplished using SQL this way:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:388 +msgid "This can also be accomplished using explicit field definitions:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:403 +msgid "Example: Transparent spatial filtering" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:405 +msgid "" +"The following example will only return features from the source layer " +"that intersect the (0,40)-(10,50) region. Furthermore, returned " +"geometries will be clipped to fit into that region." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:419 +msgid "Example: Reprojected layer" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:421 +msgid "" +"The following example will return the source.shp layer reprojected to " +"EPSG:4326." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:436 +msgid "Example: Union layer" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:438 +msgid "" +"The following example will return a layer that is the concatenation of " +"source1.shp and source2.shp." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:455 +msgid "Example: SQLite/Spatialite SQL dialect" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:457 +msgid "" +"The following example will return four different layers which are " +"generated in a fly from the same polygon shapefile. The first one is the " +"shapefile layer as it stands. The second layer gives simplified polygons " +"by applying SpatiaLite function \"Simplify\" with parameter tolerance=10." +" In the third layer the original geometries are replaced by their convex " +"hulls. In the fourth layer SpatiaLite function PointOnSurface is used for" +" replacing the original geometries by points which are inside the " +"corresponding source polygons. Note that for using the last three layers " +"of this VRT file GDAL must be compiled with SQLite and SpatiaLite." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:488 +msgid "Example: Multiple geometry fields" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:490 +msgid "" +"The following example will expose all the attribute and geometry fields " +"of the source layer:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:501 +msgid "To expose only part (or all!) of the fields:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:522 +msgid "To reproject the 'pg_geom_field_2' geometry field to EPSG:4326:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:536 +msgid "" +"To make the union of several multi-geometry layers and keep only a few of" +" them:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:565 +msgid "" +"When the *GeometryField* is \"WKT\" spatial filtering is applied after " +"extracting all rows from the source datasource. Essentially that means " +"there is no fast spatial filtering on WKT derived geometries." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:568 +msgid "" +"When the *GeometryField* is \"PointFromColumns\", and a *SrcLayer* (as " +"opposed to *SrcSQL*) is used, and a spatial filter is in effect on the " +"virtual layer then the spatial filter will be internally translated into " +"an attribute filter on the X and Y columns in the *SrcLayer*. In cases " +"where fast spatial filtering is important it can be helpful to index the " +"X and Y columns in the source datastore, if that is possible. For " +"instance if the source is an RDBMS. You can turn off that feature by " +"setting the *useSpatialSubquery* attribute of the GeometryField element " +"to FALSE." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:577 +msgid "" +".vrt files starting with - <OGRVRTDataSource> open with ogrinfo, etc. - " +"<VRTDataset> open with gdalinfo, etc." +msgstr "" + +#: ../../source/drivers/vector/wasp.rst:4 +msgid "WAsP - WAsP .map format" +msgstr "" + +#: ../../source/drivers/vector/wasp.rst:6 +msgid "WAsP" +msgstr "" + +#: ../../source/drivers/vector/wasp.rst:10 +msgid "" +"This driver writes .map files to be used with WAsP. The only allowed " +"geometries are linestrings." +msgstr "" + +#: ../../source/drivers/vector/wasp.rst:61 +msgid "" +"Note that if not option is specified, the layer is assumed to be an " +"elevation layer where the elevation is the z-components of the " +"linestrings' points." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:4 +msgid "WFS - OGC WFS service" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:6 +msgid "WFS" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:10 +msgid "" +"This driver can connect to a OGC WFS service. It supports WFS 1.0, 1.1 " +"and 2.0 protocols. GDAL/OGR must be built with Curl support in order for " +"the WFS driver to be compiled. Usually WFS requests return results in GML" +" format, so the GML driver should generally be set-up for read support " +"(thus requiring GDAL/OGR to be built with Xerces or Expat support). It is" +" sometimes possible to use alternate underlying formats when the server " +"supports them (such as OUTPUTFORMAT=json)." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:18 +msgid "" +"The driver supports read-only services, as well as transactional ones " +"(WFS-T)." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:29 +msgid "" +"The minimal syntax to open a WFS datasource is : " +"*WFS:http://path/to/WFS/service* or " +"*http://path/to/WFS/service?SERVICE=WFS*" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:33 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if WFS`` option to command " +"line utilities accepting it, or ``WFS`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed URL without the ``WFS:`` prefix." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:38 +msgid "" +"Additional optional parameters can be specified such as *TYPENAME*, " +"*VERSION*, *MAXFEATURES* (WFS < 2) or *COUNT* (WFS > 2) as specified in " +"WFS specification." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:41 +msgid "" +"The name provided to the TYPENAME parameter must be exactly the layer " +"name reported by OGR, in particular with its namespace prefix when its " +"exists. Note: several type names can be provided and separated by comma." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:45 +msgid "" +"It is also possible to specify the name of an XML file whose content " +"matches the following syntax (the <OGRWFSDataSource> element must be the " +"first bytes of the file):" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:55 +msgid "" +"Note: the URL must be XML-escaped, for example the *&* character must be " +"written as *&*" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:58 +msgid "" +"At the first opening, the content of the result of the *GetCapabilities* " +"request will be appended to the file, so that it can be cached for later " +"openings of the dataset. The same applies for the *DescribeFeatureType* " +"request issued to discover the field definition of each layer." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:63 +msgid "" +"The service description file has the following additional elements as " +"immediate children of the ``OGRWFSDataSource`` element that may be " +"optionally set." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:73 +msgid "**Version**: Set a specific WFS version to use (either 1.0.0 or 1.1.0)." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:75 +msgid "" +"**PagingAllowed**: Set to ON if paging must be enabled. See \"Request " +"paging\" section." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:77 +msgid "" +"**PageSize**: Page size when paging is enabled. See \"Request paging\" " +"section." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:79 +msgid "" +"**BaseStartIndex**: Base of the start index when paging is enabled (0 or " +"1). See \"Request paging\" section." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:81 +msgid "" +"**COOKIE**: HTTP cookies that are passed in HTTP requests, formatted as " +"COOKIE1=VALUE1; COOKIE2=VALUE2... Starting with GDAL 2.3, additional HTTP" +" headers can be sent by setting the :config:`GDAL_HTTP_HEADER_FILE` " +"configuration option to point to a filename of a text file with “key: " +"value” HTTP headers." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:88 +msgid "Request paging" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:90 +msgid "" +"The WFS driver will read the GML content as a stream instead as a whole " +"file, which will improve interactivity and help when the content cannot " +"fit into memory. This can be turned off by setting the " +":config:`OGR_WFS_USE_STREAMING` configuration option to NO if this is not" +" desirable (for example, when iterating several times on a layer that can" +" fit into memory). When streaming is enabled, GZip compression is also " +"requested. It has been observed that some WFS servers, that cannot do on-" +"the-fly compression, will cache on their side the whole content to be " +"sent before sending the first bytes on the wire. To avoid this, you can " +"set the :config:`CPL_CURL_GZIP` configuration option to NO." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:103 +msgid "Paging with WFS 2.0" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:105 +msgid "" +"The WFS driver will automatically detect if server supports paging, when " +"requesting a WFS 2.0 server. The page size (number of features fetched in" +" a single request) is limited to 100 by default when not declared by the " +"server. It can be changed by setting the :config:`OGR_WFS_PAGE_SIZE` " +"configuration option, or by specifying COUNT as a query parameter in the " +"URL of the connection string." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:112 +msgid "" +"If only the N first features must be downloaded and paging through the " +"whole layer is not desirable, the :config:`OGR_WFS_PAGING_ALLOWED` " +"configuration option should be set to OFF." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:116 +msgid "" +"Starting with GDAL 3.8, if the feature count is already known before " +"fetching the first feature, and the feature count is less than the page " +"size, then the WFS driver will not use paging (no ``STARTINDEX`` " +"parameter will be used in the requests). (This behavior improves " +"compatibility with Geoserver when datasources with no primary key.)" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:123 +msgid "Paging with WFS 1.0 or 1.1" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:125 +msgid "" +"Some servers (such as MapServer >= 6.0) support the use of STARTINDEX " +"that allows doing the requests per \"page\", and thus to avoid " +"downloading the whole content of the layer in a single request. Paging " +"was introduced in WFS 2.0.0 but servers may support it as an vendor " +"specific option also with WFS 1.0.0 and 1.1.0. The OGR WFS client will " +"use paging when the :config:`OGR_WFS_PAGING_ALLOWED` configuration option" +" is explicitly set to ON. The page size (number of features fetched in a " +"single request) is limited to 100 by default when not declared by the " +"server. It can be changed by setting the :config:`OGR_WFS_PAGE_SIZE` " +"configuration option." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:137 +msgid "" +"WFS 2.0.2 specification has clarified that the first feature in paging is" +" at index 0. But some server implementations of WFS paging have " +"considered that it was at index 1 (including MapServer <= 6.2). The " +"default base start index is 0, as mandated by the specification. The " +":config:`OGR_WFS_BASE_START_INDEX` configuration option can however be " +"set to 1 to be compatible with the server implementations that considered" +" the first feature to be at index 1." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:147 +msgid "Paging options" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:149 +msgid "" +"Those 3 options (:config:`OGR_WFS_PAGING_ALLOWED`, " +":config:`OGR_WFS_PAGE_SIZE`, :config:`OGR_WFS_BASE_START_INDEX`) can also" +" be set in a WFS XML description file with the elements of similar names " +"(PagingAllowed, PageSize, BaseStartIndex)." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:158 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server. It also makes its best effort to do the same for attribute " +"filters set with SetAttributeFilter() when possible (turning OGR SQL " +"language into OGC filter description). When this is not possible, it will" +" default to client-side only filtering, which can be a slow operation " +"because involving fetching all the features from the servers." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:166 +msgid "The following spatial functions can be used :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:168 +msgid "" +"the 8 spatial binary predicate: **ST_Equals, ST_Disjoint, ST_Touches, " +"ST_Contains, ST_Intersects, ST_Within, ST_Crosses and ST_Overlaps** that " +"take 2 geometry arguments. Typically the geometry column name, and a " +"constant geometry such as built with ST_MakeEnvelope or ST_GeomFromText." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:173 +msgid "**ST_DWithin(geom1,geom2,distance_in_meters)**" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:174 +msgid "**ST_Beyond(geom1,geom2,distance_in_meters)**" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:175 +msgid "" +"**ST_MakeEnvelope(xmin,ymin,xmax,ymax[,srs])**: to build an envelope. srs" +" can be an integer (an EPSG code), or a string directly set as the " +"srsName attribute of the gml:Envelope. GDAL will take care of needed axis" +" swapping, so coordinates should be expressed in the \"natural GIS " +"order\" (for example long,lat for geodetic systems)" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:180 +msgid "" +"**ST_GeomFromText(wkt,[srs])**: to build a geometry from its WKT " +"representation." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:183 +msgid "" +"Note that those spatial functions are only supported as server-side " +"filters." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:187 +msgid "Layer joins" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:189 +msgid "" +"For WFS 2.0 servers that support joins, SELECT statements that involve " +"joins will be run on server side. Spatial joins can also be done by using" +" the above mentioned spatial functions, if the server supports spatial " +"joins." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:194 +msgid "" +"There might be restrictions set by server on the complexity of the joins." +" The OGR WFS driver also restricts column selection to be column names, " +"potentially with aliases and type casts, but not expressions. The ON and " +"WHERE clauses must also be evaluated on server side, so no OGR special " +"fields are allowed for example. ORDER BY clauses are supported, but the " +"fields must belong to the primary table." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:201 +msgid "Example of valid statement :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:214 +msgid "Write support / WFS-T" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:216 +msgid "" +"The WFS-T protocol only enables the user to operate at feature level. No " +"datasource, layer or field creations are possible." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:222 +msgid "" +"The mapping between the operations of the WFS Transaction service and the" +" OGR concepts is the following:" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:225 +msgid "OGRFeature::CreateFeature() <==> WFS insert operation" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:226 +msgid "OGRFeature::SetFeature() <==> WFS update operation" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:227 +msgid "OGRFeature::DeleteFeature() <==> WFS delete operation" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:229 +msgid "Lock operations (LockFeature service) are not available at that time." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:231 +msgid "" +"There are a few caveats to keep in mind. OGR feature ID (FID) is an " +"integer based value, whereas WFS/GML gml:id attribute is a string. Thus " +"it is not always possible to match both values. The WFS driver exposes " +"then the gml:id attribute of a feature as a 'gml_id' field." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:236 +msgid "" +"When inserting a new feature with CreateFeature(), and if the command is " +"successful, OGR will fetch the returned gml:id and set the 'gml_id' field" +" of the feature accordingly. It will also try to set the OGR FID if the " +"gml:id is of the form layer_name.numeric_value. Otherwise the FID will be" +" left to its unset default value." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:242 +msgid "" +"When updating an existing feature with SetFeature(), the OGR FID field " +"will be ignored. The request issued to the driver will only take into " +"account the value of the gml:id field of the feature. The same applies " +"for DeleteFeature()." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:248 +msgid "Write support and OGR transactions" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:254 +msgid "" +"It is possible to surround those operations between " +"OGRLayer::StartTransaction() and OGRLayer::CommitTransaction(). The " +"operations will be stored into memory and only executed at the time " +"CommitTransaction() is called." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:259 +msgid "" +"The drawback for CreateFeature() is that the user cannot know which " +"gml:id have been assigned to the inserted features. A special SQL " +"statement has been introduced into the WFS driver to workaround this : by" +" issuing the \"SELECT \\_LAST_INSERTED_FIDS\\_ FROM layer_name\" (where " +"layer_name is to be replaced with the actual layer_name) command through " +"the OGRDataSource::ExecuteSQL(), a layer will be returned with as many " +"rows with a single attribute gml_id as the count of inserted features " +"during the last committed transaction." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:268 +msgid "" +"Note : currently, only CreateFeature() makes use of OGR transaction " +"mechanism. SetFeature() and DeleteFeature() will still be issued " +"immediately." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:273 +msgid "Special SQL commands" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:275 +msgid "" +"The following SQL / pseudo-SQL commands passed to " +"OGRDataSource::ExecuteSQL() are specific of the WFS driver :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:278 +msgid "" +"\"DELETE FROM layer_name WHERE expression\" : this will result into a WFS" +" delete operation. This can be a fast way of deleting one or several " +"features. In particularly, this can be a faster replacement for " +"OGRLayer::DeleteFeature() when the gml:id is known, but the feature has " +"not been fetched from the server." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:284 +msgid "\"SELECT \\_LAST_INSERTED_FIDS\\_ FROM layer_name\" : see above paragraph." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:287 +msgid "" +"Currently, any other SQL command will be processed by the generic layer, " +"meaning client-side only processing. Server side spatial and attribute " +"filtering must be done through the SetSpatialFilter() and " +"SetAttributeFilter() interfaces." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:293 +msgid "Special layer : WFSLayerMetadata" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:295 +msgid "" +"A \"hidden\" layer called \"WFSLayerMetadata\" is filled with records " +"with metadata for each WFS layer." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:298 +msgid "" +"Each record contains a \"layer_name\", \"title\" and \"abstract\" field, " +"from the document returned by GetCapabilities." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:301 +msgid "That layer is returned through GetLayerByName(\"WFSLayerMetadata\")." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:304 +msgid "Special layer : WFSGetCapabilities" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:306 +msgid "" +"A \"hidden\" layer called \"WFSGetCapabilities\" is filled with the raw " +"XML result of the GetCapabilities request." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:309 +msgid "That layer is returned through GetLayerByName(\"WFSGetCapabilities\")." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:392 +msgid "Listing the types of a WFS server :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:398 +msgid "" +"Listing the types of a WFS server whose layer structures are cached in a " +"XML file :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:405 +msgid "Listing the features of the dvg:nw_dvg2_rbz layer, with a spatial filter :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:411 +msgid "" +"Retrieving the features of GN \"Köln\" and \"Viersen\" from the " +"dvg:nw_dvg2_krs layer :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:418 +msgid "Display layer metadata :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:427 +msgid "`OGC WFS Standard <http://www.opengeospatial.org/standards/wfs>`__" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:429 +msgid ":ref:`OGC API - Features driver documentation <vector.oapif>`" +msgstr "" + +#: ../../source/drivers/vector/xls.rst:4 +msgid "XLS - MS Excel format" +msgstr "" + +#: ../../source/drivers/vector/xls.rst:6 +msgid "XLS" +msgstr "" + +#: ../../source/drivers/vector/xls.rst:10 +msgid "" +"This driver reads spreadsheets in MS Excel format. GDAL/OGR must be built" +" against the FreeXL library (GPL/LPL/MPL licensed), and the driver has " +"the same restrictions as the FreeXL library itself as far as which and " +"how Excel files are supported. (At the time of writing - with FreeXL " +"1.0.0a -, it means in particular that formulas are not supported.)" +msgstr "" + +#: ../../source/drivers/vector/xls.rst:47 +msgid "" +"`Homepage of the FreeXL library <https://www.gaia-" +"gis.it/fossil/freexl/index>`__" +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:5 +msgid "XLSX - MS Office Open XML spreadsheet" +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:7 +msgid "XLSX" +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:11 +msgid "" +"This driver can read, write and update spreadsheets in Microsoft Office " +"Open XML (a.k.a. OOXML) spreadsheet format, generated by applications " +"like Microsoft Office 2007 and later versions. LibreOffice/OpenOffice can" +" also export documents in that format since their v3 version." +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:22 +msgid "" +"Note 1 : depending on the application that produced the file, the driver " +"might succeed or not in retrieving the result of formulas. Some " +"applications write the evaluated result of formulas in the document, in " +"which case the driver will be able to retrieve it. Otherwise the raw " +"formula string will be returned." +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:28 +msgid "Note 2 : spreadsheets with passwords are not supported." +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:30 +msgid "" +"Note 3 : when updating an existing document, all existing styles, " +"formatting, formulas and other concepts (charts, drawings, macros, ...) " +"not understood by OGR will be lost : the document is re-written from " +"scratch from the OGR data model." +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:98 +msgid "" +"Transform CSV file input.csv to an Office Open XML file output.xlsx. The " +"spreadsheet will contain one sheet with name \"input\"." +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:105 +msgid "" +"Add the contents of CSV file input2.csv to the OOXML file output.xlsx " +"created in the first example. The spreadsheet will now contain two " +"sheets, \"input\" and \"input2\"." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:4 +msgid "XODR -- OpenDRIVE Road Description Format" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:8 +msgid "XODR" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:12 +msgid "" +"This driver provides read access to road network elements of OpenDRIVE " +"datasets." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:14 +msgid "" +"`OpenDRIVE <https://www.asam.net/standards/detail/opendrive/>`_ is an " +"open industry format for lane-detailed description of road networks, " +"commonly used in applications of the automotive and transportation " +"systems domains. It bundles polynomial, continuous road geometry " +"modelling with all necessary topological links and semantic information " +"from traffic-regulating infrastructure (signs and traffic lights)." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:24 +msgid "" +"The currently supported OpenDRIVE version is 1.4 and depends on what is " +"provided by libOpenDRIVE_." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:29 +msgid "Supported OpenDRIVE elements" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:31 +msgid "" +"The XODR driver exposes OpenDRIVE's different road elements as separate " +"layers by converting geometric elements into 3-dimensional OGR geometry " +"types. The following _`layer types` are currently implemented:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:33 +msgid "" +"*ReferenceLine*: Road reference line (``<planView>``) as " +":cpp:class:`OGRLineString`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:34 +msgid "*LaneBorder*: Outer road lane border as :cpp:class:`OGRLineString`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:35 +msgid "" +"*Lane*: Polygonal surface (TIN) of the lane mesh as " +":cpp:class:`OGRTriangulatedSurface`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:36 +msgid "" +"*RoadMark*: Polygonal surface (TIN) of the road mark mesh as " +":cpp:class:`OGRTriangulatedSurface`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:37 +msgid "" +"*RoadObject*: Polygonal surface (TIN) of the road object mesh as " +":cpp:class:`OGRTriangulatedSurface`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:38 +msgid "" +"*RoadSignal*: Polygonal surface (TIN) of the road signal mesh as " +":cpp:class:`OGRTriangulatedSurface`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:41 +msgid "Spatial reference" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:43 +msgid "" +"By definition, OpenDRIVE geometries are always referenced in a Cartesian " +"coordinate system which defaults to having its origin at ``(0, 0, 0)``. " +"If real-world coordinates are used, the OpenDRIVE header provides a " +"PROJ.4 string with the definition of a projected spatial reference " +"system:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:51 +msgid "" +"The XODR driver uses this PROJ definition as spatial reference for " +"creation of all OGR geometry layers." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:56 +msgid "" +"The supported content encoding of OpenDRIVE XML files is limited to what " +"pugixml is able to automatically guess (see `4.6. Encodings " +"<https://pugixml.org/docs/manual.html#loading.encoding>`_). The default " +"fallback encoding is UTF-8." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:61 +msgid "" +"The following open options can be specified (typically with the ``-oo " +"name=value`` parameters of :program:`ogrinfo` or :program:`ogr2ogr`):" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:80 +msgid "" +"Translate OpenDRIVE road *ReferenceLine* elements (``<planView>``) to " +":ref:`Shapefile <vector.shapefile>` using :program:`ogr2ogr`. The desired" +" :ref:`layer type <layer types>` which is to be extracted from the " +"dataset is specified as the last parameter of the function call." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:86 +msgid "" +"Convert the whole OpenDRIVE dataset with all its different layers into a " +":ref:`GeoPackage <vector.gpkg>` using:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:92 +msgid "" +"Convert the whole OpenDRIVE dataset with custom parameters :oo:`EPSILON` " +"and :oo:`DISSOLVE_TIN` into a :ref:`GeoPackage <vector.gpkg>`:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:99 +msgid "Convenient usage through docker image" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:101 +msgid "" +"To use the XODR driver through a docker image, first build the image from" +" the corresponding docker directory" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:108 +msgid "" +"For general usage information refer to `GDAL Docker images " +"<https://github.com/OSGeo/gdal/tree/master/docker#usage>`__. Usage " +"examples:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:110 +msgid "" +"Use :program:`ogrinfo` to extract detailed information about a local " +"`xodr` file by mounting your current working directory (`$PWD`) " +"containing the file into the Docker container:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:116 +msgid "" +"Use :program:`ogr2ogr` to convert a local `xodr` file into any other " +"supported OGR output format. The result will be automatically available " +"in your host machine's working directory which is mounted into the " +"container:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:123 +msgid "" +"Alternatively, you can run a docker container that enables using the XODR" +" driver in an isolated workspace from within the container" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:131 +msgid "General building notes" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:133 +msgid "Building of the driver as plugin is tested to work on" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:135 +msgid "Ubuntu 24.04 using GCC" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:136 +msgid "" +"Windows 10 using GCC 13.1.0 (with MCF threads) + MinGW-w64 11.0.0 (MSVCRT" +" runtime), which is obtainable from `WinLibs <https://winlibs.com/>`_." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:138 +msgid "Ensure to meet the following driver dependencies:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:140 +msgid "PROJ" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:141 +msgid "GEOS" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:142 +msgid "" +"libOpenDRIVE_ as shared library (built with CMake option " +"``-DBUILD_SHARED_LIBS=ON``)" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:144 +msgid "" +"Then, after checking out GDAL sources with this driver extension, create " +"the build directory:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:152 +msgid "" +"From the build directory configure CMake to activate our XODR driver as " +"plugin:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:158 +msgid "" +"The :file:`cmake/` path is usually automatically created when installing " +"libOpenDRIVE and contains the necessary configuration files for inclusion" +" into other project builds." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:160 +msgid "Now, build GDAL and install it:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:167 +msgid "" +"Afterwards you will find a new shared library file " +":file:`{path/to/GDAL/installdir}/lib/gdalplugins/ogr_XODR`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:170 +msgid "Verifying a successful build" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:172 +msgid "Check if XODR driver is found:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:179 +msgid "This should print basic capabilities of the driver:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:192 +msgid "" +"If you are on Linux, depending on your environment, you might experience " +"linker errors like:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:198 +msgid "" +"In such cases ensure that your environment variable ``LD_LIBRARY_PATH`` " +"points to the corresponding install directories of libOpenDRIVE and GDAL " +"and run ``ldconfig`` afterwards." +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/faq.po b/doc/source/locale/en/LC_MESSAGES/faq.po new file mode 100644 index 000000000000..cf6bb01040fb --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/faq.po @@ -0,0 +1,198 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: en\n" +"Language-Team: en <LL@li.org>\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/faq.rst:5 +msgid "FAQ" +msgstr "" + +#: ../../source/faq.rst:12 +msgid "Contents" +msgstr "" + +#: ../../source/faq.rst:16 +msgid "What does GDAL stand for?" +msgstr "" + +#: ../../source/faq.rst:18 +msgid "GDAL - Geospatial Data Abstraction Library" +msgstr "" + +#: ../../source/faq.rst:20 +msgid "" +"It is sometimes pronounced \"goo-doll\" (a bit like goo-gle), while " +"others pronounce it \"gee-doll,\" and others pronounce it \"gee-dall.\"" +msgstr "" + +#: ../../source/faq.rst:22 +msgid "" +"`Listen <https://soundcloud.com/danabauer/how-do-you-pronounce-" +"gdal#t=00:02:58>`__ how Frank Warmerdam prounounces it and the history " +"behind the acronym." +msgstr "" + +#: ../../source/faq.rst:25 +msgid "What is this OGR stuff?" +msgstr "" + +#: ../../source/faq.rst:27 +msgid "" +"OGR used to be a separate vector IO library inspired by OpenGIS Simple " +"Features which was separated from GDAL. With the GDAL 2.0 release, the " +"GDAL and OGR components were integrated together." +msgstr "" + +#: ../../source/faq.rst:30 +msgid "What does OGR stand for?" +msgstr "" + +#: ../../source/faq.rst:32 +msgid "" +"OGR used to stand for OpenGIS Simple Features Reference Implementation. " +"However, since OGR is not fully compliant with the OpenGIS Simple Feature" +" specification and is not approved as a reference implementation of the " +"spec the name was changed to OGR Simple Features Library. The only " +"meaning of OGR in this name is historical. OGR is also the prefix used " +"everywhere in the source of the library for class names, filenames, etc." +msgstr "" + +#: ../../source/faq.rst:35 +msgid "What does CPL stand for?" +msgstr "" + +#: ../../source/faq.rst:37 +msgid "" +"Common Portability Library. Think of it as GDAL internal cross-platform " +"standard library. Back in the early days of GDAL development, when cross-" +"platform development as well as compatibility and standard conformance of" +" compilers was a challenge (or PITA), CPL proved necessary for smooth " +"portability of GDAL/OGR." +msgstr "" + +#: ../../source/faq.rst:39 +msgid "" +"CPL, or parts of it, is used by some projects external to GDAL (eg. " +"MITAB, libgeotiff)." +msgstr "" + +#: ../../source/faq.rst:42 +msgid "When was the GDAL project started?" +msgstr "" + +#: ../../source/faq.rst:44 +msgid "" +"In late 1998, Frank Warmerdam started to work as independent professional" +" on the GDAL/OGR library." +msgstr "" + +#: ../../source/faq.rst:47 +msgid "Is GDAL/OGR proprietary software?" +msgstr "" + +#: ../../source/faq.rst:49 +msgid "No, GDAL/OGR is a Free and Open Source Software." +msgstr "" + +#: ../../source/faq.rst:52 +msgid "What license does GDAL/OGR use?" +msgstr "" + +#: ../../source/faq.rst:54 +msgid "See :ref:`license`" +msgstr "" + +#: ../../source/faq.rst:57 +msgid "What operating systems does GDAL-OGR run on?" +msgstr "" + +#: ../../source/faq.rst:59 +msgid "" +"You can use GDAL/OGR on all modern flavors of Unix: Linux, FreeBSD, Mac " +"OS X; all supported versions of Microsoft Windows; mobile environments " +"(Android and iOS). Both 32-bit and 64-bit architectures are supported." +msgstr "" + +#: ../../source/faq.rst:62 +msgid "Is there a graphical user interface to GDAL/OGR?" +msgstr "" + +#: ../../source/faq.rst:64 +msgid "See :ref:`software_using_gdal`:" +msgstr "" + +#: ../../source/faq.rst:72 +msgid "What compiler can I use to build GDAL/OGR?" +msgstr "" + +#: ../../source/faq.rst:74 +msgid "" +"GDAL/OGR must be compiled with a C++17 capable compiler since GDAL 3.9 " +"(C++11 in previous versions)" +msgstr "" + +#: ../../source/faq.rst:76 +msgid "Build requirements are described in :ref:`build_requirements`." +msgstr "" + +#: ../../source/faq.rst:79 +msgid "" +"I have a question that's not answered here. Where can I get more " +"information?" +msgstr "" + +#: ../../source/faq.rst:81 +msgid "See :ref:`community`" +msgstr "" + +#: ../../source/faq.rst:83 +msgid "" +"Keep in mind, the quality of the answer you get does bear some relation " +"to the quality of the question. If you need more detailed explanation of " +"this, you can find it in essay `How To Ask Questions The Smart Way " +"<http://www.catb.org/~esr/faqs/smart-questions.html>`_ by Eric S. " +"Raymond." +msgstr "" + +#: ../../source/faq.rst:86 +msgid "How do I add support for a new format?" +msgstr "" + +#: ../../source/faq.rst:88 +msgid "" +"To some extent this is now covered by the :ref:`raster_driver_tut` and " +":ref:`vector_driver_tut`" +msgstr "" + +#: ../../source/faq.rst:91 +msgid "Is GDAL thread-safe ?" +msgstr "" + +#: ../../source/faq.rst:93 +msgid "See :ref:`multithreading`" +msgstr "" + +#: ../../source/faq.rst:96 +msgid "How do I cite GDAL ?" +msgstr "" + +#: ../../source/faq.rst:98 +msgid "See `CITATION`_" +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/index.po b/doc/source/locale/en/LC_MESSAGES/index.po new file mode 100644 index 000000000000..6ea846e1e548 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/index.po @@ -0,0 +1,76 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: en\n" +"Language-Team: en <LL@li.org>\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/index.rst:12 +msgid "User" +msgstr "" + +#: ../../source/index.rst:3 +msgid "GDAL" +msgstr "" + +#: ../../source/about_no_title.rst:1 +msgid "" +"GDAL is a translator library for raster and vector geospatial data " +"formats that is released under an MIT style Open Source :ref:`license` by" +" the `Open Source Geospatial Foundation`_. As a library, it presents a " +"single raster abstract data model and single vector abstract data model " +"to the calling application for all supported formats. It also comes with " +"a variety of useful command line utilities for data translation and " +"processing. The `NEWS`_ page describes the June 2024 GDAL/OGR 3.9.1 " +"release." +msgstr "" + +#: ../../source/about_no_title.rst:-1 +msgid "OSGeo project" +msgstr "" + +#: ../../source/about_no_title.rst:10 +msgid "See :ref:`software_using_gdal`" +msgstr "" + +#: ../../source/about_no_title.rst:16 +msgid "" +"You may quote GDAL in publications by using the following Digital Object " +"Identifier: |DOI|" +msgstr "" + +#: ../../source/about_no_title.rst +msgid "DOI 10.5281/zenodo.5884351" +msgstr "" + +#: ../../source/index.rst:7 +msgid "" +"This documentation is also available as a `PDF file <gdal.pdf>`_, and `a " +".ZIP of individual HTML pages <https://github.com/OSGeo/gdal-" +"docs/archive/refs/heads/master.zip>`_ for offline browsing. (The .ZIP " +"also includes that .PDF.) The documentation reflects the latest state of " +"the development branch of the software." +msgstr "" + +#: ../../source/index.rst:30 +msgid "Index" +msgstr "" + +#: ../../source/index.rst:32 +msgid ":ref:`genindex`" +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/index_pdf.po b/doc/source/locale/en/LC_MESSAGES/index_pdf.po new file mode 100644 index 000000000000..7627b1ec1e16 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/index_pdf.po @@ -0,0 +1,29 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: en\n" +"Language-Team: en <LL@li.org>\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/index_pdf.rst:7 +msgid "User" +msgstr "" + +#: ../../source/index_pdf.rst:5 +msgid "GDAL" +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/license.po b/doc/source/locale/en/LC_MESSAGES/license.po new file mode 100644 index 000000000000..0f54e0c913a8 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/license.po @@ -0,0 +1,63 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: en\n" +"Language-Team: en <LL@li.org>\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/license.rst:5 ../../source/license.rst:8 +msgid "License" +msgstr "" + +#: ../../source/license.rst:10 +msgid "" +"In general GDAL/OGR is licensed under an MIT style license with the " +"following terms:" +msgstr "" + +#: ../../source/license.rst:13 +msgid "" +"Permission is hereby granted, free of charge, to any person obtaining a " +"copy of this software and associated documentation files (the " +"\"Software\"), to deal in the Software without restriction, including " +"without limitation the rights to use, copy, modify, merge, publish, " +"distribute, sublicense, and/or sell copies of the Software, and to permit" +" persons to whom the Software is furnished to do so, subject to the " +"following conditions:" +msgstr "" + +#: ../../source/license.rst:20 +msgid "" +"The above copyright notice and this permission notice shall be included " +"in all copies or substantial portions of the Software." +msgstr "" + +#: ../../source/license.rst:23 +msgid "" +"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS" +" OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF " +"MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN" +" NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM," +" DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR " +"OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE" +" USE OR OTHER DEALINGS IN THE SOFTWARE." +msgstr "" + +#: ../../source/license.rst:31 +msgid "The full licensing terms are available in the `LICENSE.TXT`_ file." +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/programs.po b/doc/source/locale/en/LC_MESSAGES/programs.po new file mode 100644 index 000000000000..a4909ab3aa3d --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/programs.po @@ -0,0 +1,10322 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: en\n" +"Language-Team: en <LL@li.org>\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/programs/argument_syntax.rst:5 +msgid "Syntax of arguments of command-line utilities" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:7 +msgid "" +"The following table describes the notation used to document the syntax of" +" arguments of command-line utilities." +msgstr "" + +#: ../../source/programs/argument_syntax.rst:13 +msgid "Notation" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:14 +#: ../../source/programs/gdal-config.rst:28 +#: ../../source/programs/gdal2tiles.rst:31 +#: ../../source/programs/gdal2xyz.rst:28 +#: ../../source/programs/gdal_contour.rst:27 +#: ../../source/programs/gdal_create.rst:35 +#: ../../source/programs/gdal_edit.rst:31 +#: ../../source/programs/gdal_fillnodata.rst:26 +#: ../../source/programs/gdal_footprint.rst:36 +#: ../../source/programs/gdal_grid.rst:34 +#: ../../source/programs/gdal_merge.rst:26 +#: ../../source/programs/gdal_pansharpen.rst:31 +#: ../../source/programs/gdal_polygonize.rst:25 +#: ../../source/programs/gdal_proximity.rst:27 +#: ../../source/programs/gdal_rasterize.rst:31 +#: ../../source/programs/gdal_retile.rst:32 +#: ../../source/programs/gdal_sieve.rst:23 +#: ../../source/programs/gdal_translate.rst:43 +#: ../../source/programs/gdal_viewshed.rst:31 +#: ../../source/programs/gdaladdo.rst:27 +#: ../../source/programs/gdalattachpct.rst:22 +#: ../../source/programs/gdalbuildvrt.rst:36 +#: ../../source/programs/gdalcompare.rst:26 +#: ../../source/programs/gdaldem.rst:84 ../../source/programs/gdalinfo.rst:27 +#: ../../source/programs/gdallocationinfo.rst:27 +#: ../../source/programs/gdalmanage.rst:23 +#: ../../source/programs/gdalmdiminfo.rst:26 +#: ../../source/programs/gdalmdimtranslate.rst:34 +#: ../../source/programs/gdalmove.rst:23 +#: ../../source/programs/gdalsrsinfo.rst:22 +#: ../../source/programs/gdaltindex.rst:34 +#: ../../source/programs/gdaltransform.rst:28 +#: ../../source/programs/gdalwarp.rst:51 +#: ../../source/programs/gnmanalyse.rst:27 +#: ../../source/programs/gnmmanage.rst:31 +#: ../../source/programs/nearblack.rst:25 ../../source/programs/ogr2ogr.rst:68 +#: ../../source/programs/ogr_layer_algebra.rst:31 +#: ../../source/programs/ogrinfo.rst:32 ../../source/programs/ogrlineref.rst:30 +#: ../../source/programs/ogrmerge.rst:36 ../../source/programs/ogrtindex.rst:28 +#: ../../source/programs/pct2rgb.rst:22 ../../source/programs/rgb2pct.rst:22 +#: ../../source/programs/sozip.rst:36 +msgid "Description" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:16 +msgid "Text without brackets or braces" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:17 +msgid "Text that must be typed as shown" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:19 +msgid "``<value>``" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:20 +msgid "Placeholder for which a value must be substituted." +msgstr "" + +#: ../../source/programs/argument_syntax.rst:22 +msgid "``[`` Text inside square brackets ``]``" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:23 +msgid "Optional item." +msgstr "" + +#: ../../source/programs/argument_syntax.rst:25 +msgid "``{`` Text inside braces ``}``" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:26 +msgid "Set of required items, separated by a vertical bar." +msgstr "" + +#: ../../source/programs/argument_syntax.rst:28 +msgid "Vertical bar (``|``)" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:29 +msgid "" +"Separator between mutually exclusive items. At least one must be " +"specified." +msgstr "" + +#: ../../source/programs/argument_syntax.rst:31 +msgid "Ellipsis (``...``)" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:32 +msgid "Placed after an item that can be repeated." +msgstr "" + +#: ../../source/programs/argument_syntax.rst:36 +#: ../../source/programs/gdal_contour.rst:138 +#: ../../source/programs/gdal_edit.rst:211 +#: ../../source/programs/gdal_pansharpen.rst:114 +#: ../../source/programs/gdal_viewshed.rst:158 +#: ../../source/programs/gdalinfo.rst:170 +#: ../../source/programs/gdalsrsinfo.rst:72 +#: ../../source/programs/ogrlineref.rst:164 +#: ../../source/programs/ogrtindex.rst:104 ../../source/programs/rgb2pct.rst:66 +msgid "Example" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:38 +msgid "Given the following synopsis:" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:45 +msgid "The following command lines are valid:" +msgstr "" + +#: ../../source/programs/gdal-config.rst:5 +msgid "gdal-config (Unix)" +msgstr "" + +#: ../../source/programs/gdal-config.rst:9 +msgid "Determines various information about a GDAL installation." +msgstr "" + +#: ../../source/programs/gdal-config.rst:14 +#: ../../source/programs/gdal2tiles.rst:14 +#: ../../source/programs/gdal2xyz.rst:14 ../../source/programs/gdal_calc.rst:14 +#: ../../source/programs/gdal_contour.rst:14 +#: ../../source/programs/gdal_create.rst:16 +#: ../../source/programs/gdal_edit.rst:14 +#: ../../source/programs/gdal_fillnodata.rst:14 +#: ../../source/programs/gdal_footprint.rst:16 +#: ../../source/programs/gdal_grid.rst:14 +#: ../../source/programs/gdal_merge.rst:14 +#: ../../source/programs/gdal_pansharpen.rst:16 +#: ../../source/programs/gdal_polygonize.rst:14 +#: ../../source/programs/gdal_proximity.rst:14 +#: ../../source/programs/gdal_rasterize.rst:14 +#: ../../source/programs/gdal_retile.rst:14 +#: ../../source/programs/gdal_sieve.rst:14 +#: ../../source/programs/gdal_translate.rst:14 +#: ../../source/programs/gdal_viewshed.rst:16 +#: ../../source/programs/gdaladdo.rst:14 +#: ../../source/programs/gdalattachpct.rst:14 +#: ../../source/programs/gdalbuildvrt.rst:14 +#: ../../source/programs/gdalcompare.rst:14 +#: ../../source/programs/gdaldem.rst:14 ../../source/programs/gdalinfo.rst:14 +#: ../../source/programs/gdallocationinfo.rst:14 +#: ../../source/programs/gdalmanage.rst:14 +#: ../../source/programs/gdalmdiminfo.rst:16 +#: ../../source/programs/gdalmdimtranslate.rst:16 +#: ../../source/programs/gdalmove.rst:14 +#: ../../source/programs/gdalsrsinfo.rst:14 +#: ../../source/programs/gdaltindex.rst:14 +#: ../../source/programs/gdaltransform.rst:14 +#: ../../source/programs/gdalwarp.rst:14 +#: ../../source/programs/gnmanalyse.rst:14 +#: ../../source/programs/gnmmanage.rst:14 +#: ../../source/programs/nearblack.rst:14 ../../source/programs/ogr2ogr.rst:14 +#: ../../source/programs/ogr_layer_algebra.rst:16 +#: ../../source/programs/ogrinfo.rst:15 ../../source/programs/ogrlineref.rst:14 +#: ../../source/programs/ogrmerge.rst:14 ../../source/programs/ogrtindex.rst:14 +#: ../../source/programs/pct2rgb.rst:14 ../../source/programs/rgb2pct.rst:14 +#: ../../source/programs/sozip.rst:16 +msgid "Synopsis" +msgstr "" + +#: ../../source/programs/gdal-config.rst:30 +msgid "" +"This utility script (available on Unix systems) can be used to determine " +"various information about a GDAL installation. It is normally just used " +"by configure scripts for applications using GDAL but can be queried by an" +" end user." +msgstr "" + +#: ../../source/programs/gdal-config.rst:37 +msgid "the top level directory for the GDAL installation." +msgstr "" + +#: ../../source/programs/gdal-config.rst:41 +msgid "The libraries and link directives required to use GDAL." +msgstr "" + +#: ../../source/programs/gdal-config.rst:45 +msgid "The include and macro definition required to compiled modules using GDAL." +msgstr "" + +#: ../../source/programs/gdal-config.rst:50 +msgid "Reports the GDAL version." +msgstr "" + +#: ../../source/programs/gdal-config.rst:54 +msgid "" +"Reports \"yes\" or \"no\" to standard output depending on whether OGR is " +"built into GDAL." +msgstr "" + +#: ../../source/programs/gdal-config.rst:59 +msgid "Reports which formats are configured into GDAL to stdout." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:5 +msgid "gdal2tiles" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:9 +msgid "Generates directory with TMS tiles, KMLs and simple web viewers." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:33 +msgid "" +"This utility generates a directory with small tiles and metadata, " +"following the OSGeo Tile Map Service Specification. Simple web pages with" +" viewers based on Google Maps, OpenLayers and Leaflet are generated as " +"well - so anybody can comfortably explore your maps on-line and you do " +"not need to install or configure any special software (like MapServer) " +"and the map displays very fast in the web browser. You only need to " +"upload the generated directory onto a web server." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:40 +msgid "" +"GDAL2Tiles also creates the necessary metadata for Google Earth (KML " +"SuperOverlay), in case the supplied map uses EPSG:4326 projection." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:43 +msgid "" +"World files and embedded georeferencing is used during tile generation, " +"but you can publish a picture without proper georeferencing too." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:48 +msgid "" +"Inputs with non-Byte data type (i.e. ``Int16``, ``UInt16``,...) will be " +"clamped to the ``Byte`` data type, causing wrong results. To avoid this " +"it is necessary to rescale input to the ``Byte`` data type using " +"`gdal_translate` utility." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:54 +msgid "" +"Config options of the input drivers may have an effect on the output of " +"gdal2tiles. An example driver config option is GDAL_PDF_DPI, which can be" +" found at :ref:`configoptions`" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:58 +msgid "" +"gdal2tiles is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/options/help.rst:3 +msgid "Show this help message and exit" +msgstr "" + +#: ../../source/programs/options/help_general.rst:3 +msgid "" +"Gives a brief usage message for the generic GDAL commandline options and " +"exit." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:67 +msgid "" +"Tile cutting profile (mercator, geodetic, raster) - default 'mercator' " +"(Google Maps compatible)." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:69 +msgid "" +"Starting with GDAL 3.2, additional profiles are available from " +"tms_XXXX.json files placed in GDAL data directory (provided all zoom " +"levels use same origin, tile dimensions, and resolution between " +"consecutive zoom levels vary by a factor of two)." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:75 +msgid "" +"Resampling method (average, near, bilinear, cubic, cubicspline, lanczos, " +"antialias, mode, max, min, med, q1, q3) - default 'average'." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:79 +msgid "The spatial reference system used for the source input data." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:83 +msgid "" +"Generate XYZ tiles (OSM Slippy Map standard) instead of TMS. In the " +"default mode (TMS), tiles at y=0 are the southern-most tiles, whereas in " +"XYZ mode (used by OGC WMTS too), tiles at y=0 are the northern-most " +"tiles." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:91 +msgid "" +"When using the geodetic profile, specifies the base resolution as " +"0.703125 or 2 tiles at zoom level 0." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:96 +msgid "Zoom levels to render (format:'2-5', '10-' or '10')." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:100 +#: ../../source/programs/gdal_retile.rst:133 +msgid "Resume mode. Generate only missing files." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:104 +msgid "" +"Value in the input dataset considered as transparent. If the input " +"dataset had already an associate nodata value, it is overridden by the " +"specified value." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:109 +msgid "Generate verbose output of tile generation." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:111 +msgid "" +"Starting with GDAL 3.7, that verbose output is emitted through the " +"``logging.getLogger(\"gdal2tiles\")`` object." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:116 +msgid "Exclude transparent tiles from result tileset." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:120 +msgid "Disable messages and status to stdout" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:126 +msgid "" +"Number of parallel processes to use for tiling, to speed-up the " +"computation." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:132 +msgid "" +"Assume launched by mpiexec, enable MPI parallelism and ignore " +"--processes. Requires working MPI environment and the MPI for Python " +"(mpi4py) package. User should set GDAL_CACHEMAX to an appropriate cache " +"size per process based on memory per node and the number of processes " +"launched per node." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:141 +msgid "Width and height in pixel of a tile. Default is 256." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:147 +msgid "" +"Which output driver to use for the tiles, determines the file format of " +"the tiles. Currently PNG, WEBP and JPEG (JPEG added in GDAL 3.9) are " +"supported. Default is PNG. Additional configuration for the WEBP and JPEG" +" drivers are documented below." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:155 +msgid "" +"Comma-separated tuple of values (thus typically \"R,G,B\"), that are " +"ignored as contributing source * pixels during resampling. The number of " +"values in the tuple must be the same as the number of bands, excluding " +"the alpha band. Several tuples of excluded values may be specified using " +"the \"(R1,G1,B2),(R2,G2,B2)\" syntax. Only taken into account by Average " +"currently. This concept is a bit similar to nodata/alpha, but the main " +"difference is that pixels matching one of the excluded value tuples are " +"still considered as valid, when determining the target pixel " +"validity/density." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:168 +msgid "" +"Minimum percentage of source pixels that must be set at one of the " +"--excluded-values to cause the excluded value, that is in majority among " +"source pixels, to be used as the target pixel value. Default value is " +"50(%)" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:175 +msgid "" +"Minimum percentage of source pixels that must be at nodata (or alpha=0 or" +" any other way to express transparent pixel) to cause the target pixel " +"value to be transparent. Default value is 100 (%), which means that a " +"target pixel is transparent only if all contributing source pixels are " +"transparent. Only taken into account for average resampling." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:185 +#: ../../source/programs/gdal2xyz.rst:87 +msgid "Show help message and exit." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:189 +msgid "Show program's version number and exit." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:193 +msgid "KML (Google Earth) options" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:195 +msgid "Options for generated Google Earth SuperOverlay metadata" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:199 +msgid "" +"Generate KML for Google Earth - default for 'geodetic' profile and " +"'raster' in EPSG:4326. For a dataset with different projection use with " +"caution!" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:203 +msgid "Avoid automatic generation of KML files for EPSG:4326." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:207 +msgid "URL address where the generated tiles are going to be published." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:211 +msgid "Web viewer options" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:213 +msgid "Options for generated HTML viewers a la Google Maps" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:217 +msgid "" +"Web viewer to generate (all, google, openlayers, leaflet, mapml, none) - " +"default 'all'." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:221 +msgid "Title of the map." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:225 +msgid "Copyright for the map." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:229 +msgid "Google Maps API key from http://code.google.com/apis/maps/signup.html." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:233 +msgid "Bing Maps API key from https://www.bingmapsportal.com/" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:237 +msgid "MapML options" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:239 +msgid "" +"MapML support is new to GDAL 3.2. When --webviewer=mapml is specified, " +"--xyz is implied, as well as --tmscompatible if --profile=geodetic." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:242 +msgid "The following profiles are supported:" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:244 +msgid "mercator: mapped to OSMTILE MapML tiling scheme" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:245 +msgid "geodetic: mapped to WGS84 MapML tiling scheme" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:246 +msgid "APSTILE: from the tms_MapML_APSTILE.json data file" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:248 +msgid "The generated MapML file in the output directory is ``mapml.mapl``" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:250 +msgid "Available options are:" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:254 +msgid "" +"Filename of a template mapml file where variables will be substituted. If" +" not specified, the generic template_tiles.mapml file from GDAL data " +"resources will be used" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:259 +msgid "" +"The --url option is also used to substitute ``${URL}`` in the template " +"MapML file." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:262 +msgid "WEBP options" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:264 +msgid "" +"WEBP tiledriver support is new to GDAL 3.6. It is enabled by using " +"--tiledriver=WEBP." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:267 +msgid "" +"The following configuration options are available to further customize " +"the WebP output:" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:271 +#: ../../source/programs/gdal2tiles.rst:295 +msgid "QUALITY is a integer between 1-100. Default is 75." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:275 +msgid "Use WEBP lossless compression, default is lossy" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:280 +msgid "GDAL :ref:`WEBP driver <raster.webp>` documentation can be consulted" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:284 +msgid "JPEG options" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:286 +msgid "" +"JPEG tiledriver support is new to GDAL 3.9. It is enabled by using " +"--tiledriver=JPEG." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:288 +msgid "" +"Note that JPEG does not support transparency, hence edge tiles will " +"display black pixels in areas not covered by the source raster." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:291 +msgid "" +"The following configuration options are available to further customize " +"the JPEG output:" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:299 +#: ../../source/programs/gdal2xyz.rst:100 +#: ../../source/programs/gdal_calc.rst:185 +#: ../../source/programs/gdal_create.rst:103 +#: ../../source/programs/gdal_footprint.rst:220 +#: ../../source/programs/gdal_grid.rst:506 +#: ../../source/programs/gdal_merge.rst:113 +#: ../../source/programs/gdal_rasterize.rst:223 +#: ../../source/programs/gdal_translate.rst:435 +#: ../../source/programs/gdaladdo.rst:281 +#: ../../source/programs/gdalbuildvrt.rst:236 +#: ../../source/programs/gdalcompare.rst:118 +#: ../../source/programs/gdallocationinfo.rst:148 +#: ../../source/programs/gdalmanage.rst:70 +#: ../../source/programs/gdalmdiminfo.rst:83 +#: ../../source/programs/gdalmdimtranslate.rst:173 +#: ../../source/programs/gdaltindex.rst:304 +#: ../../source/programs/gdaltransform.rst:167 +#: ../../source/programs/gdalwarp.rst:700 ../../source/programs/ogr2ogr.rst:688 +#: ../../source/programs/ogrinfo.rst:250 ../../source/programs/ogrmerge.rst:184 +#: ../../source/programs/sozip.rst:150 +msgid "Examples" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:301 +msgid "Basic example:" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:308 +msgid "MapML generation:" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:315 +msgid "MPI example:" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:5 +msgid "gdal2xyz" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:9 +msgid "Translates a raster file into `xyz` format." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:30 +msgid "" +"The :program:`gdal2xyz` utility can be used to translate a raster file " +"into xyz format. `gdal2xyz` can be used as an alternative to " +"`gdal_translate of=xyz`. Features include:" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:33 +msgid "Select more then one band" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:34 +msgid "Skip or replace nodata value" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:35 +msgid "Return the output as numpy arrays." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:39 +msgid "" +"gdal2xyz is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:47 +msgid "How many rows/cols to skip in each iteration." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:51 +#: ../../source/programs/gdal_translate.rst:189 +msgid "" +"Selects a subwindow from the source image for copying based on pixel/line" +" location." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:55 +msgid "" +"Select band *band* from the input spectral bands for output. Bands are " +"numbered from 1 in the order spectral bands are specified. Multiple " +"**-b** switches may be used. When no -b switch is used, the first band " +"will be used. In order to use all input bands set `-allbands` or `-b 0`." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:63 +msgid "Select all input bands." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:67 +msgid "Use comma instead of space as a delimiter." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:71 +msgid "Exclude the output lines with nodata value (as determined by srcnodata)" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:75 +msgid "" +"The nodata value of the dataset (for skipping or replacing) Default " +"(`None`) - Use the dataset nodata value; `Sequence`/`Number` - Use the " +"given nodata value (per band or per dataset)." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:81 +msgid "" +"Replace source nodata with a given nodata. Has an effect only if not " +"setting `-skipnodata`. Default(`None`) - Use `srcnodata`, no replacement;" +" `Sequence`/`Number` - Replace the `srcnodata` with the given nodata " +"value (per band or per dataset)." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:91 +#: ../../source/programs/gdal_translate.rst:410 +msgid "" +"The source dataset name. It can be either file name, URL of data source " +"or subdataset name for multi-dataset files." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:96 +#: ../../source/programs/gdal_create.rst:100 +#: ../../source/programs/gdal_translate.rst:415 +#: ../../source/programs/gdalmdimtranslate.rst:165 +#: ../../source/programs/gdalwarp.rst:490 +msgid "The destination file name." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:107 +msgid "" +"To create a text file in `xyz` format from the input file `input.tif`. " +"The first columns, x and y, are the coordinates of the centers of each " +"cell. The remaining columns represent the first and second bands. We also" +" replace the dataset nodata values with zeros." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:114 +msgid "Caveats" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:116 +msgid "" +"gdal2xyz output values with a limited precision. Use ``gdal_translate -of" +" XYZ`` if more precision is desired." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:5 +msgid "gdal_calc" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:9 +msgid "Command line raster calculator with numpy syntax." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:-1 +msgid "DESCRIPTION" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:25 +msgid "" +"Command line raster calculator with numpy syntax. Use any basic " +"arithmetic supported by numpy arrays such as ``+``, ``-``, ``*``, and " +"``/`` along with logical operators such as ``>``. Note that all files " +"must have the same dimensions (unless extent option is used), but no " +"projection checking is performed (unless projectionCheck option is used)." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:33 +msgid "" +"gdal_calc is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:39 +msgid "" +"Calculation in numpy syntax using ``+``, ``-``, ``/``, ``*``, or any " +"numpy array functions (i.e. ``log10()``). Multiple ``--calc`` options can" +" be listed to produce a multiband file (GDAL >= 3.2)." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:44 +msgid "" +"Input gdal raster file, you can use any letter (a-z, A-Z). (lower case " +"supported since GDAL 3.3)" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:46 +msgid "" +"A letter may be repeated, or several values (separated by space) can be " +"provided (GDAL >= 3.3). Since GDAL 3.5, wildcard exceptions (using ?, " +"\\*) are supported for all shells/platforms. The effect will be to create" +" a 3-dim numpy array. In such a case, the calculation formula must use " +"this input as a 3-dim array and must return a 2D array (see examples " +"below). In case the calculation does not return a 2D array an error would" +" be generated." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:54 +msgid "Number of raster band for file A (default 1)." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:58 +msgid "Output file to generate or fill." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:62 +msgid "" +"Output NoDataValue (default datatype specific value). To indicate not " +"setting a NoDataValue use --NoDataValue=none (GDAL >= 3.3)" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:66 +msgid "" +"Using the Python API: ``None`` value will indicate default datatype " +"specific value. ``'none'`` value will indicate not setting a NoDataValue." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:74 +msgid "" +"Ignores the input bands NoDataValue. By default, the input bands " +"NoDataValue are not participating in the calculation. By setting this " +"setting - no special treatment will be performed on the input " +"NoDataValue. and they will be participating in the calculation as any " +"other value. The output will not have a set NoDataValue, unless you " +"explicitly specified a specific value by setting --NoDataValue=<value>." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:81 +msgid "" +"Output datatype, must be one of [``Byte``, ``Int8``, ``UInt16``, " +"``Int16``, ``UInt32``, ``Int32``, ``UInt64``, ``Int64``, ``Float64``, " +"``Float32``, ``CInt16``, ``CInt32``, ``CFloat64``, ``CFloat32``]." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:85 +msgid "" +"Despite the datatype set using ``--type``, when doing intermediate " +"aritmethic operations using operands of the same type, the operation " +"result will honor the original datatype. This may lead into unexpected " +"results in the final result." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:90 +msgid "" +"UInt64, Int64, CInt16, CInt32, CFloat32, CFloat64 have been added in GDAL" +" 3.5.3 Int8 has been added in GDAL 3.7" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:95 +msgid "GDAL format for output file." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:99 +msgid "" +"Allows specifying a filename of a color table (or a ColorTable object) " +"(with Palette Index interpretation) to be used for the output raster. " +"Supported formats: txt (i.e. like gdaldem, but color names are not " +"supported), qlr, qml (i.e. exported from QGIS)" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:106 +msgid "" +"This option determines how to handle rasters with different extents. This" +" option is mutually exclusive with the `projwin` option, which is used " +"for providing a custom extent." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:109 +msgid "" +"For all the options below the pixel size (resolution) and SRS (Spatial " +"Reference System) of all the input rasters must be the same." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:111 +msgid "" +"``ignore`` (default) - only the dimensions of the rasters are compared. " +"if the dimensions do not agree the operation will fail." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:113 +msgid "" +"``fail`` - the dimensions and the extent (bounds) of the rasters must " +"agree, otherwise the operation will fail." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:115 +msgid "" +"``union`` - the extent (bounds) of the output will be the minimal " +"rectangle that contains all the input extents." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:117 +msgid "" +"``intersect`` - the extent (bounds) of the output will be the maximal " +"rectangle that is contained in all the input extents." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:123 +msgid "" +"This option provides a custom extent for the output, it is mutually " +"exclusive with the `extent` option." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:129 +msgid "" +"By default, no projection checking will be performed. By setting this " +"option, if the projection is not the same for all bands then the " +"operation will fail." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:136 +msgid "" +"Passes a creation option to the output format driver. Multiple options " +"may be listed. See format specific documentation for legal creation " +"options for each format." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:142 +msgid "The same as creation-option_." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:146 +msgid "" +"Process all bands of given raster (a-z, A-Z). Requires a single calc for " +"all bands." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:150 +msgid "" +"Overwrite output file if it already exists. Overwriting must be " +"understood here as deleting and recreating the file from scratch. Note " +"that if this option is *not* specified and the output file already " +"exists, it will be updated in place." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:157 +msgid "Print debugging information." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:161 +#: ../../source/programs/gdal_merge.rst:76 +msgid "Suppress progress messages." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:165 +msgid "Python options" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:169 +msgid "" +"The following options are available by using function the python " +"interface of gdal_calc. They are not available using the command prompt." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:174 +msgid "" +"A dictionary of custom functions or other names to be available for use " +"in the Calc expression." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:178 +msgid "" +"If enabled, the output dataset would be returned from the function and " +"not closed." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:182 +msgid "" +"Allows specifying a ColorTable object (with Palette Index interpretation)" +" to be used for the output raster." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:187 +msgid "Add two files together:" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:193 +msgid "Average of two layers:" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:201 +msgid "" +"In the previous example, beware that if A and B inputs are of the same " +"datatype, for example integers, you may need to force the conversion of " +"one of the operands before the division operation." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:208 +msgid "Add three files together (two options with the same result):" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:218 +msgid "Average of three layers (two options with the same result):" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:228 +msgid "Maximum of three layers (two options with the same result):" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:238 +msgid "Set values of zero and below to null:" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:244 +msgid "Using logical operator to keep a range of values from input:" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:250 +msgid "Work with multiple bands:" +msgstr "" + +#: ../../source/programs/gdal_contour.rst:5 +msgid "gdal_contour" +msgstr "" + +#: ../../source/programs/gdal_contour.rst:9 +msgid "Builds vector contour lines from a raster elevation model." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:29 +msgid "" +"The :program:`gdal_contour` generates a vector contour file from the " +"input raster elevation model (DEM)." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:32 +msgid "" +"The contour line-strings are oriented consistently and the high side will" +" be on the right, i.e. a line string goes clockwise around a top." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:41 +msgid "Picks a particular band to get the DEM from. Defaults to band 1." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:45 +msgid "" +"Provides a name for the attribute in which to put the elevation. If not " +"provided no elevation attribute is attached. Ignored in polygonal " +"contouring (:option:`-p`) mode." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:51 +msgid "" +"Provides a name for the attribute in which to put the minimum elevation " +"of contour polygon. If not provided no minimum elevation attribute is " +"attached. Ignored in default line contouring mode." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:59 +msgid "" +"Provides a name for the attribute in which to put the maximum elevation " +"of contour polygon. If not provided no maximum elevation attribute is " +"attached. Ignored in default line contouring mode." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:67 +msgid "" +"Force production of 3D vectors instead of 2D. Includes elevation at every" +" vertex." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:72 +msgid "" +"Ignore any nodata value implied in the dataset - treat all values as " +"valid." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:76 +msgid "Input pixel value to treat as \"nodata\"." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:80 +msgid "Create output in a particular format." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:84 +msgid "" +"If not specified, the format is guessed from the extension (previously " +"was ESRI Shapefile)." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:88 +#: ../../source/programs/gdal_footprint.rst:183 +#: ../../source/programs/gnmanalyse.rst:65 +#: ../../source/programs/ogr2ogr.rst:194 +#: ../../source/programs/ogrlineref.rst:68 +#: ../../source/programs/ogrmerge.rst:133 +msgid "Dataset creation option (format specific)" +msgstr "" + +#: ../../source/programs/gdal_contour.rst:92 +#: ../../source/programs/gdal_footprint.rst:179 +#: ../../source/programs/gdal_polygonize.rst:87 +#: ../../source/programs/gdaltindex.rst:137 +#: ../../source/programs/gnmanalyse.rst:69 +#: ../../source/programs/ogr2ogr.rst:198 ../../source/programs/ogrmerge.rst:137 +msgid "Layer creation option (format specific)" +msgstr "" + +#: ../../source/programs/gdal_contour.rst:96 +msgid "" +"Elevation interval between contours. Ignored if -fl is used. Must specify" +" either -i or -fl or -e." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:101 +msgid "" +"Offset from zero relative to which to interpret intervals. Ignored if -fl" +" is used." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:103 +msgid "" +"For example, `-i 100` requests contours at ...-100, 0, 100... Further " +"adding `-off 25` makes that request instead ...-75, 25, 125..." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:108 +msgid "" +"Name one or more \"fixed levels\" to extract. Must specify either -i or " +"-fl or -e." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:113 +msgid "" +"Generate levels on an exponential scale: `base ^ k`, for `k` an integer. " +"Must specify either -i or -fl or -e." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:120 +msgid "Provide a name for the output vector layer. Defaults to \"contour\"." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:124 +msgid "Generate contour polygons rather than contour lines." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:130 +msgid "Be quiet: do not print progress indicators." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:133 +#: ../../source/programs/gdal_footprint.rst:214 +#: ../../source/programs/gdal_grid.rst:501 +#: ../../source/programs/gdal_rasterize.rst:216 +#: ../../source/programs/gdal_translate.rst:428 +#: ../../source/programs/gdal_viewshed.rst:153 +#: ../../source/programs/gdaladdo.rst:276 +#: ../../source/programs/gdalbuildvrt.rst:264 +#: ../../source/programs/gdaldem.rst:395 ../../source/programs/gdalinfo.rst:163 +#: ../../source/programs/gdalmdiminfo.rst:78 +#: ../../source/programs/gdalmdimtranslate.rst:168 +#: ../../source/programs/gdaltindex.rst:336 +#: ../../source/programs/gdalwarp.rst:752 +#: ../../source/programs/nearblack.rst:125 +#: ../../source/programs/ogr2ogr.rst:681 ../../source/programs/ogrinfo.rst:243 +#: ../../source/programs/sozip.rst:144 +msgid "C API" +msgstr "" + +#: ../../source/programs/gdal_contour.rst:135 +msgid "" +"Functionality of this utility can be done from C with " +":cpp:func:`GDALContourGenerate`." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:140 +msgid "" +"This would create 10-meter contours from the DEM data in :file:`dem.tif` " +"and produce a shapefile in :file:`contour.shp|shx|dbf` with the contour " +"elevations in the ``elev`` attribute." +msgstr "" + +#: ../../source/programs/gdal_create.rst:5 +msgid "gdal_create" +msgstr "" + +#: ../../source/programs/gdal_create.rst:11 +msgid "Create a raster file (without source dataset)." +msgstr "" + +#: ../../source/programs/gdal_create.rst:37 +msgid "" +"The :program:`gdal_create` utility can be used to initialize a new raster" +" file, from its dimensions, band count and set various parameters, such " +"as CRS, geotransform, nodata value, metadata. It can be used also in " +"special cases, like creating a PDF file from a XML composition file." +msgstr "" + +#: ../../source/programs/options/ot.rst:3 +msgid "" +"Force the output image bands to have a specific data type supported by " +"the driver, which may be one of the following: ``Byte``, ``Int8``, " +"``UInt16``, ``Int16``, ``UInt32``, ``Int32``, ``UInt64``, ``Int64``, " +"``Float32``, ``Float64``, ``CInt16``, ``CInt32``, ``CFloat32`` or " +"``CFloat64``." +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:36 +#: ../../source/programs/options/of.rst:3 ../../source/programs/pct2rgb.rst:37 +msgid "" +"Select the output format. Starting with GDAL 2.3, if not specified, the " +"format is guessed from the extension (previously was GTiff). Use the " +"short format name." +msgstr "" + +#: ../../source/programs/gdal_create.rst:52 +msgid "" +"Set the size of the output file in pixels. First figure is width. Second " +"one is height." +msgstr "" + +#: ../../source/programs/gdal_create.rst:57 +msgid "Number of bands. Defaults to 1 if -outsize is specified, or 0 otherwise." +msgstr "" + +#: ../../source/programs/gdal_create.rst:61 +msgid "" +"A fixed value to burn into a band. A list of :option:`-burn` options can " +"be supplied, one per band (the first value will apply to the first band, " +"the second one to the second band, etc.). If a single value is specified," +" it will apply to all bands." +msgstr "" + +#: ../../source/programs/gdal_create.rst:68 +msgid "" +"Override the projection for the output file. The<srs_def> may be any of " +"the usual GDAL/OGR forms, complete WKT, PROJ.4, EPSG:n or a file " +"containing the WKT. No reprojection is done." +msgstr "" + +#: ../../source/programs/gdal_create.rst:74 +msgid "Assign the georeferenced bounds of the output file." +msgstr "" + +#: ../../source/programs/gdal_create.rst:78 +#: ../../source/programs/gdal_edit.rst:134 +#: ../../source/programs/gdal_merge.rst:98 +#: ../../source/programs/gdal_rasterize.rst:123 +msgid "Assign a specified nodata value to output bands." +msgstr "" + +#: ../../source/programs/gdal_create.rst:82 +#: ../../source/programs/gdal_translate.rst:308 +msgid "Passes a metadata key and value to set on the output dataset if possible." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:320 +#: ../../source/programs/options/co.rst:5 +msgid "" +"Many formats have one or more optional creation options that can be used " +"to control particulars about the file created. For instance, the GeoTIFF " +"driver supports creation options to control compression, and whether the " +"file should be tiled." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:325 +#: ../../source/programs/gdalmdimtranslate.rst:61 +#: ../../source/programs/options/co.rst:10 +msgid "" +"The creation options available vary by format driver, and some simple " +"formats have no creation options at all. A list of options supported for " +"a format can be listed with the :ref:`--formats " +"<raster_common_options_formats>` command line option but the " +"documentation for the format is the definitive source of information on " +"driver creation options. See :ref:`raster_drivers` format specific " +"documentation for legal creation options for each format." +msgstr "" + +#: ../../source/programs/gdal_create.rst:88 +#: ../../source/programs/gdal_footprint.rst:142 +#: ../../source/programs/gdal_grid.rst:165 +#: ../../source/programs/gdal_pansharpen.rst:94 +#: ../../source/programs/gdal_rasterize.rst:196 +#: ../../source/programs/gdal_translate.rst:383 +#: ../../source/programs/gdaldem.rst:161 +#: ../../source/programs/nearblack.rst:111 +msgid "Suppress progress monitor and other non-error output." +msgstr "" + +#: ../../source/programs/gdal_create.rst:94 +msgid "" +"Name of GDAL input dataset that serves as a template for default values " +"of options -outsize, -bands, -ot, -a_srs, -a_ullr and -a_nodata. Note " +"that the pixel values will *not* be copied." +msgstr "" + +#: ../../source/programs/gdal_create.rst:105 +msgid "Initialize a new GeoTIFF file with a uniform value of 10" +msgstr "" + +#: ../../source/programs/gdal_create.rst:112 +msgid "Create a PDF file from a XML composition file:" +msgstr "" + +#: ../../source/programs/gdal_create.rst:120 +msgid "Initialize a blank GeoTIFF file from an input one:" +msgstr "" + +#: ../../source/programs/gdal_edit.rst:5 +msgid "gdal_edit" +msgstr "" + +#: ../../source/programs/gdal_edit.rst:9 +msgid "Edit in place various information of an existing GDAL dataset." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:33 +msgid "" +":program:`gdal_edit` can be used to edit in place various information of " +"an existing GDAL dataset (projection, geotransform, nodata, metadata)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:37 +msgid "" +"It works only with raster formats that support update access to existing " +"datasets." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:41 +msgid "" +"Depending on the format, older values of the updated information might " +"still be found in the file in a \"ghost\" state, even if no longer " +"accessible through the GDAL API. This is for example the case of the " +":ref:`raster.gtiff` format (this is not a exhaustive list)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:48 +msgid "" +"gdal_edit is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:54 +msgid "" +"Open the dataset in read-only. Might be useful for drivers refusing to " +"use the dataset in update-mode. In which case, updated information will " +"go into PAM :file:`.aux.xml` files." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:60 +msgid "" +"Defines the target coordinate system. This coordinate system will be " +"written to the dataset. If the empty string or None is specified, then " +"the existing coordinate system will be removed (for TIFF/GeoTIFF, might " +"not be well supported besides that)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:68 +msgid "" +"Assign/override the coordinate epoch of the dataset, as a decimal year " +"(e.g., 2021.3)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:74 +msgid "Remove the coordinate epoch of the dataset." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:80 +msgid "Assign/override the georeferenced bounds of the dataset." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:84 +msgid "" +"Assign/override the georeferenced bounds of the dataset from three " +"points: upper-left, upper-right and lower-left. Unlike :option:`-a_ullr`," +" this also supports rotated datasets (edges not parallel to coordinate " +"system axes)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:92 +#: ../../source/programs/gdal_rasterize.rst:159 +msgid "" +"Set target resolution. The values must be expressed in georeferenced " +"units. Both must be positive values." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:97 +msgid "Remove the georeference information." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:101 +msgid "Remove RPC information." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:107 +msgid "Remove band statistics information." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:113 +msgid "Calculate and store band statistics." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:119 +msgid "" +"Store user-defined values for band statistics (minimum, maximum, mean and" +" standard deviation). If any of the values is set to None, the real " +"statistics are calclulated from the file and the ones set to None are " +"used from the real statistics." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:128 +msgid "Calculate and store approximate band statistics." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:138 +msgid "Remove existing nodata values." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:144 +msgid "" +"Assign a specified scale value to output bands. If a single scale value " +"is provided it will be set for all bands. Alternatively one scale value " +"per band can be provided, in which case the number of scale values must " +"match the number of bands. If no scale is needed, it it recommended to " +"set the value to 1. Scale and Offset are generally used together. For " +"example, scale and offset might be used to store elevations in a unsigned" +" 16bit integer file with a precision of 0.1, and starting from -100. True" +" values would be calculated as: true_value = (pixel_value * scale) + " +"offset" +msgstr "" + +#: ../../source/programs/gdal_edit.rst:154 +msgid "" +"These values can be applied using -unscale during a " +":program:`gdal_translate` run." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:160 +msgid "" +"Assign a specified offset value to output bands. If a single offset value" +" is provided it will be set for all bands. Alternatively one offset value" +" per band can be provided, in which case the number of offset values must" +" match the number of bands. If no offset is needed, it recommended to set" +" the value to 0. For more see scale." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:171 +msgid "Assign a unit to output band(s)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:177 +msgid "" +"Change the color interpretation of band X (where X is a valid band " +"number, starting at 1)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:184 +msgid "" +"Add the indicated ground control point to the dataset. This option may be" +" provided multiple times to provide a set of GCPs." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:189 +msgid "" +"Remove existing metadata (in the default metadata domain). Can be " +"combined with :option:`-mo`." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:196 +msgid "" +"Passes a metadata key and value to set on the output dataset if possible." +" This metadata is added to the existing metadata items, unless " +":option:`-unsetmd` is also specified." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:202 +msgid "Open option (format specific)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:206 +msgid "" +"The :option:`-a_ullr`, :option:`-a_ulurll`, :option:`-tr` and " +":option:`-unsetgt` options are exclusive." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:208 +msgid "" +"The :option:`-unsetstats` and either :option:`-stats` or " +":option:`-approx_stats` options are exclusive." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:5 +msgid "gdal_fillnodata" +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:9 +msgid "Fill raster regions by interpolation from edges." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:28 +msgid "" +":program:`gdal_fillnodata` fills selection regions (usually nodata areas)" +" by interpolating from valid pixels around the edges of the area." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:31 +msgid "" +"Additional details on the algorithm are available in the " +":cpp:func:`GDALFillNodata` docs." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:36 +msgid "" +"gdal_fillnodata is a Python utility, and is only available if GDAL Python" +" bindings are available." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:42 +msgid "" +"The script runs in quiet mode. The progress monitor is suppressed and " +"routine messages are not displayed." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:47 +msgid "" +"The maximum distance (in pixels) that the algorithm will search out for " +"values to interpolate. The default is 100 pixels." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:52 +msgid "" +"The number of 3x3 average filter smoothing iterations to run after the " +"interpolation to dampen artifacts. The default is zero smoothing " +"iterations." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:57 +msgid "Specify a special argument to the algorithm. Currently none are supported." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:61 +msgid "The band to operate on, by default the first band is operated on." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:65 +msgid "" +"Use the first band of the specified file as a validity mask (zero is " +"invalid, non-zero is valid)." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:70 +msgid "" +"Select the output format. The default is :ref:`raster.gtiff`. Use the " +"short format name." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:77 +msgid "" +"By default, pixels are interpolated using an inverse distance weighting " +"(``inv_dist``). It is also possible to choose a nearest neighbour " +"(``nearest``) strategy." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:83 +msgid "" +"The source raster file used to identify target pixels. Only one band is " +"used." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:88 +msgid "The new file to create with the interpolated result." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:5 +msgid "gdal_footprint" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:11 +msgid "Compute footprint of a raster." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:38 +msgid "" +"The :program:`gdal_footprint` utility can be used to compute the " +"footprint of a raster file, taking into account nodata values (or more " +"generally the mask band attached to the raster bands), and generating " +"polygons/multipolygons corresponding to areas where pixels are valid, and" +" write to an output vector file." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:43 +msgid "" +"The :program:`nearblack` utility may be run as a pre-processing step to " +"generate proper mask bands." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:53 +msgid "" +"Band(s) of interest. Between 1 and the number of bands of the raster. May" +" be specified multiple times. If not specified, all bands are taken into " +"account. The way multiple bands are combined is controlled by " +":option:`-combine_bands`" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:60 +msgid "" +"Defines how the mask bands of the selected bands are combined to generate" +" a single mask band, before being vectorized. The default value is " +"``union``: that is a pixel is valid if it is valid at least for one of " +"the selected bands. ``intersection`` means that a pixel is valid only " +"ifit is valid for all selected bands." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:69 +msgid "" +"To specify which overview level of source file must be used, when " +"overviews are available on the source raster. By default the full " +"resolution level is used. The index is 0-based, that is 0 means the first" +" overview level. This option is mutually exclusive with " +":option:`-srcnodata`." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:76 +msgid "" +"Set nodata values for input bands (different values can be supplied for " +"each band). If a single value is specified, it applies to all selected " +"bands. If more than one value is supplied, there should be as many values" +" as the number of selected bands, and all values should be quoted to keep" +" them together as a single operating system argument. If the option is " +"not specified, the intrinsic mask band of each selected bands will be " +"used." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:86 +msgid "" +"Target coordinate system. By default if the input dataset is " +"georeferenced, ``georef`` is implied, that is the footprint geometry will" +" be expressed as coordinates in the CRS of the raster (or the one " +"specified with :option:`-t_srs`). If specifying ``pixel``, the " +"coordinates of the footprint geometry are column and line indices." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:94 +msgid "" +"Target CRS of the output file. The <srs_def> may be any of the usual " +"GDAL/OGR forms, complete WKT, PROJ.4, EPSG:n or a file containing the " +"WKT. Specifying this option implies -t_cs georef The footprint is " +"reprojected from the CRS of the source raster to the specified CRS." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:103 +msgid "" +"When specified, multipolygons are split as several features each with one" +" single polygon." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:108 +msgid "When specified, the convex hull of (multi)polygons is computed." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:112 +msgid "" +"The specified value of this option is the maximum distance between 2 " +"consecutive points of the output geometry. The unit of the distance is in" +" pixels if :option:`-t_cs` equals ``pixel``, or otherwise in " +"georeferenced units of the source raster. This option is applied before " +"the reprojection implied by :option:`-t_srs`." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:120 +msgid "" +"The specified value of this option is the tolerance used to merge " +"consecutive points of the output geometry using the " +":cpp:func:`OGRGeometry::Simplify` method. The unit of the distance is in " +"pixels if :option:`-t_cs` equals ``pixel``, or otherwise in georeferenced" +" units of the target vector dataset. This option is applied after the " +"reprojection implied by :option:`-t_srs`." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:129 +msgid "" +"Minimum value for the area of a ring The unit of the area is in square " +"pixels if :option:`-t_cs` equals ``pixel``, or otherwise in georeferenced" +" units of the target vector dataset. This option is applied after the " +"reprojection implied by :option:`-t_srs`" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:136 +msgid "" +"Maximum number of points of each output geometry (not counting the " +"closing point of each ring, which is always identical to the first " +"point). The default value is 100. ``unlimited`` can be used to remove " +"that limitation." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:146 +#: ../../source/programs/gdal_translate.rst:406 +#: ../../source/programs/gdaladdo.rst:87 +#: ../../source/programs/gdalbuildvrt.rst:207 +#: ../../source/programs/gdallocationinfo.rst:77 +#: ../../source/programs/gdalwarp.rst:476 +msgid "Dataset open option (format specific)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:150 +msgid "" +"Select the output format. Use the short format name. Guessed from the " +"file extension if not specified" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:157 +msgid "" +"Specifies the name of the field in the resulting vector dataset where the" +" path of the input dataset will be stored. The default field name is " +"\"location\". To prevent writing the path of the input dataset, use " +":option:`-no_location`" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:166 +msgid "" +"Turns off the writing of the path of the input dataset as a field in the " +"output vector dataset." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:173 +msgid "" +"Enables writing the absolute path of the input dataset. By default, the " +"filename is written in the location field exactly as specified on the " +"command line." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:187 +msgid "Name of the target layer. ``footprint`` if not specified." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:191 +msgid "Overwrite the target layer if it exists." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:195 +msgid "The source raster file name." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:199 +msgid "" +"The destination vector file name. If the file and the output layer exist," +" the new footprint is appended to them, unless :option:`-overwrite` is " +"used." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:203 +msgid "" +"Post-vectorization geometric operations are applied in the following " +"order:" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:205 +msgid "optional splitting (:option:`-split_polys`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:206 +msgid "optional densification (:option:`-densify`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:207 +msgid "optional reprojection (:option:`-t_srs`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:208 +msgid "optional filtering by minimum ring area (:option:`-min_ring_area`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:209 +msgid "optional application of convex hull (:option:`-convex_hull`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:210 +msgid "optional simplification (:option:`-simplify`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:211 +msgid "limitation of number of points (:option:`-max_points`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:216 +msgid "This utility is also callable from C with :cpp:func:`GDALFootprint`." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:222 +msgid "" +"Compute the footprint of a GeoTIFF file as a GeoJSON file using WGS 84 " +"longitude, latitude coordinates" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:5 +msgid "gdal_grid" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:9 +msgid "Creates regular grid from the scattered data." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:36 +msgid "" +"This program creates a regular grid (raster) from the scattered data read" +" from the OGR datasource. Input data will be interpolated to fill grid " +"nodes with values, you can choose from various interpolation methods." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:40 +msgid "" +"It is possible to set the :config:`GDAL_NUM_THREADS` configuration option" +" to parallelize the processing. The value to specify is the number of " +"worker threads, or ``ALL_CPUS`` to use all the cores/CPUs of the " +"computer." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:51 +msgid "" +"If not set then a default type is used, which might not be supported by " +"the relevant driver, causing a error." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:58 +msgid "Set georeferenced X extents of output file to be created." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:62 +msgid "Set georeferenced Y extents of output file to be created." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:66 +msgid "" +"Set output file resolution (in target georeferenced units). Note that " +":option:`-tr` just works in combination with a valid input from " +":option:`-txe` and :option:`-tye`" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:73 +msgid "" +"Set the size of the output file in pixels and lines. Note that " +":option:`-outsize` cannot be used with :option:`-tr`" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:78 +msgid "" +"Override the projection for the output file. The *srs_def* may be any of" +" the usual GDAL/OGR forms, complete WKT, PROJ.4, EPSG:n or a file " +"containing the WKT. No reprojection is done." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:85 +msgid "" +"Identifies an attribute field on the features to be used to get a Z value" +" from. This value overrides the Z value read from the feature geometry " +"record (naturally, if you have a Z value in the geometry, otherwise you " +"have no choice and should specify a field name containing a Z value)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:93 +msgid "" +"Addition to the attribute field on the features to be used to get a Z " +"value from. The addition should be the same unit as the Z value. The " +"result value will be Z value + Z increase value. The default value is 0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:99 +msgid "" +"This is multiplication ratio for the Z field. This can be used for a " +"shift from e.g. feet to meters or from elevation to depth. The result " +"value will be (Z value + Z increase value) * Z multiply value. The " +"default value is 1." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:106 +msgid "" +"Set the interpolation algorithm or data metric name and (optionally) its " +"parameters. See the `Interpolation algorithms`_ and `Data metrics`_ " +"sections for further discussion of available options." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:112 +msgid "" +"Adds a spatial filter to select only features contained within the " +"bounding box described by (xmin, ymin) - (xmax, ymax)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:118 +msgid "" +"Adds a spatial filter to select only features contained within the " +"specified bounding box (expressed in source SRS), WKT geometry (POLYGON " +"or MULTIPOLYGON), from a datasource or to the spatial extent of the " +":option:`-spat` option if you use the ``spat_extent`` keyword. When " +"specifying a datasource, you will generally want to use it in combination" +" with the :option:`-clipsrclayer`, :option:`-clipsrcwhere` or " +":option:`-clipsrcsql` options." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:128 +msgid "Select desired geometries using an SQL query instead." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:132 +#: ../../source/programs/ogr2ogr.rst:413 +msgid "Select the named layer from the source clip datasource." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:136 +msgid "Restrict desired geometries based on an attribute query." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:140 +#: ../../source/programs/gdal_rasterize.rst:95 +msgid "" +"Indicates the layer(s) from the datasource that will be used for input " +"features. May be specified multiple times, but at least one layer name " +"or a :option:`-sql` option must be specified." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:147 +msgid "" +"An optional SQL WHERE style query expression to be applied to select " +"features to process from the input layer(s)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:152 +msgid "" +"An SQL statement to be evaluated against the datasource to produce a " +"virtual layer of features to be processed." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:159 +#: ../../source/programs/gdal_rasterize.rst:192 +#: ../../source/programs/gdalmdimtranslate.rst:157 +msgid "Source dataset open option (format specific)" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:169 +#: ../../source/programs/gdal_rasterize.rst:200 +msgid "Any OGR supported readable datasource." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:173 +msgid "The GDAL supported output file." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:177 +msgid "Interpolation algorithms" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:179 +msgid "There are a number of interpolation algorithms to choose from." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:181 +msgid "More details about them can also be found in :ref:`gdal_grid_tut`" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:186 +msgid "invdist" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:188 +msgid "" +"Inverse distance to a power. This is the default algorithm. It has the " +"following parameters:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:191 +#: ../../source/programs/gdal_grid.rst:228 +msgid "``power``: Weighting power (default 2.0)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:192 +#: ../../source/programs/gdal_grid.rst:229 +msgid "``smoothing``: Smoothing parameter (default 0.0)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:193 +msgid "" +"``radius1``: The first radius (X axis if rotation angle is 0) of the " +"search ellipse. Set this parameter to zero to use the whole point array. " +"Default is 0.0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:196 +msgid "" +"``radius2``: The second radius (Y axis if rotation angle is 0) of the " +"search ellipse. Set this parameter to zero to use the whole point array. " +"Default is 0.0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:199 +#: ../../source/programs/gdal_grid.rst:273 +#: ../../source/programs/gdal_grid.rst:323 +#: ../../source/programs/gdal_grid.rst:386 +msgid "" +"``radius``: Set first and second radius (mutually exclusive with radius1 " +"and radius2). Default is 0.0. Added in GDAL 3.6" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:201 +#: ../../source/programs/gdal_grid.rst:275 +#: ../../source/programs/gdal_grid.rst:325 +#: ../../source/programs/gdal_grid.rst:388 +msgid "" +"``angle``: Angle of search ellipse rotation in degrees (counter " +"clockwise, default 0.0)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:203 +msgid "" +"``max_points``: Maximum number of data points to use. Do not search for " +"more points than this number. This is only used if the search ellipse is " +"set (both radii are non-zero). Zero means that all found points should be" +" used. Default is 0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:207 +#: ../../source/programs/gdal_grid.rst:390 +msgid "" +"``min_points``: Minimum number of data points to use. If less amount of " +"points found the grid node considered empty and will be filled with " +"NODATA marker. This is only used if search ellipse is set (both radii are" +" non-zero). Default is 0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:211 +msgid "" +"``max_points_per_quadrant``: Maximum number of data points to use per " +"quadrant. Default is 0. Added in GDAL 3.6. When specified, this actually " +"uses invdistnn implementation." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:214 +msgid "" +"``min_points_per_quadrant``: Minimum number of data points to use per " +"quadrant. Default is 0. Added in GDAL 3.6. When specified, this actually " +"uses invdistnn implementation." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:217 +#: ../../source/programs/gdal_grid.rst:250 +#: ../../source/programs/gdal_grid.rst:297 +#: ../../source/programs/gdal_grid.rst:327 +#: ../../source/programs/gdal_grid.rst:350 +#: ../../source/programs/gdal_grid.rst:406 +msgid "``nodata``: NODATA marker to fill empty points (default 0.0)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:221 +msgid "invdistnn" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:225 +msgid "" +"Inverse distance to a power with nearest neighbor searching, ideal when " +"max_points is used. It has following parameters:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:230 +msgid "" +"``radius``: The radius of the search circle, which should be non-zero. " +"Default is 1.0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:232 +msgid "" +"``max_points``: Maximum number of data points to use. Do not search for " +"more points than this number. Found points will be ranked from nearest to" +" furthest distance when weighting. Default is 12." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:235 +msgid "" +"``min_points``: Minimum number of data points to use. If less amount of " +"points found the grid node is considered empty and will be filled with " +"NODATA marker. Default is 0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:238 +#: ../../source/programs/gdal_grid.rst:285 +#: ../../source/programs/gdal_grid.rst:394 +msgid "" +"``max_points_per_quadrant``: Maximum number of data points to use per " +"quadrant. Default is 0. Added in GDAL 3.6. When specified, the algorithm " +"will only take into account up to max_points_per_quadrant points for each" +" of the right-top, left-top, right-bottom and right-top quadrant relative" +" to the point being interpolated." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:243 +#: ../../source/programs/gdal_grid.rst:290 +#: ../../source/programs/gdal_grid.rst:399 +msgid "" +"``min_points_per_quadrant``: Minimum number of data points to use per " +"quadrant. Default is 0. Added in GDAL 3.6. If that number is not reached," +" the point being interpolated will be set with the NODATA marker. When " +"specified, the algorithm will collect at least min_points_per_quadrant " +"points for each of the right-top, left-top, right-bottom and right-top " +"quadrant relative to the point being interpolated." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:253 +#: ../../source/programs/gdal_grid.rst:303 +#: ../../source/programs/gdal_grid.rst:409 +msgid "" +"When ``min_points_per_quadrant`` or ``max_points_per_quadrant`` is " +"specified, the search will start with the closest point to the point " +"being interpolated from the first quadrant, then the closest point to the" +" point being interpolated from the second quadrant, etc. up to the 4th " +"quadrant, and will continue with the next closest point in the first " +"quadrant, etc. until ``max_points`` and/or ``max_points_per_quadrant`` " +"thresholds are reached." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:263 +msgid "average" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:265 +msgid "Moving average algorithm. It has following parameters:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:267 +#: ../../source/programs/gdal_grid.rst:317 +#: ../../source/programs/gdal_grid.rst:380 +msgid "" +"``radius1``: The first radius (X axis if rotation angle is 0) of search " +"ellipse. Set this parameter to zero to use whole point array. Default is " +"0.0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:270 +#: ../../source/programs/gdal_grid.rst:320 +#: ../../source/programs/gdal_grid.rst:383 +msgid "" +"``radius2``: The second radius (Y axis if rotation angle is 0) of search " +"ellipse. Set this parameter to zero to use whole point array. Default is " +"0.0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:277 +msgid "" +"``max_points``: Maximum number of data points to use. Do not search for " +"more points than this number. Found points will be ranked from nearest to" +" furthest distance when weighting. Default is 0. Added in GDAL 3.6 Only " +"taken into account if one or both of ``min_points_per_quadrant`` or " +"``max_points_per_quadrant`` is specified" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:282 +msgid "" +"``min_points``: Minimum number of data points to use. If less amount of " +"points found the grid node considered empty and will be filled with " +"NODATA marker. Default is 0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:300 +msgid "" +"Note, that it is essential to set search ellipse for moving average " +"method. It is a window that will be averaged when computing grid nodes " +"values." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:313 +msgid "nearest" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:315 +msgid "Nearest neighbor algorithm. It has following parameters:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:331 +msgid "linear" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:335 +msgid "Linear interpolation algorithm." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:337 +msgid "" +"The Linear method performs linear interpolation by computing a Delaunay " +"triangulation of the point cloud, finding in which triangle of the " +"triangulation the point is, and by doing linear interpolation from its " +"barycentric coordinates within the triangle. If the point is not in any " +"triangle, depending on the radius, the algorithm will use the value of " +"the nearest point or the nodata value." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:344 +msgid "It has following parameters:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:346 +msgid "" +"``radius``: In case the point to be interpolated does not fit into a " +"triangle of the Delaunay triangulation, use that maximum distance to " +"search a nearest neighbour, or use nodata otherwise. If set to -1, the " +"search distance is infinite. If set to 0, nodata value will be always " +"used. Default is -1." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:354 +msgid "Data metrics" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:356 +msgid "" +"Besides the interpolation functionality :program:`gdal_grid` can be used " +"to compute some data metrics using the specified window and output grid " +"geometry. These metrics are:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:360 +msgid "``minimum``: Minimum value found in grid node search ellipse." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:362 +msgid "``maximum``: Maximum value found in grid node search ellipse." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:364 +msgid "" +"``range``: A difference between the minimum and maximum values found in " +"grid node search ellipse." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:367 +msgid "``count``: A number of data points found in grid node search ellipse." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:369 +msgid "" +"``average_distance``: An average distance between the grid node (center " +"of the search ellipse) and all of the data points found in grid node " +"search ellipse." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:373 +msgid "" +"``average_distance_pts``: An average distance between the data points " +"found in grid node search ellipse. The distance between each pair of " +"points within ellipse is calculated and average of all distances is set " +"as a grid node value." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:378 +msgid "All the metrics have the same set of options:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:417 +msgid "Reading comma separated values" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:419 +msgid "" +"Often you have a text file with a list of comma separated XYZ values to " +"work with (so called CSV file). You can easily use that kind of data " +"source in :program:`gdal_grid`. All you need is to create a virtual " +"dataset header (VRT) for your CSV file and use it as an input datasource " +"for :program:`gdal_grid`. You can find details on the VRT format on the " +":ref:`vector.vrt` description page." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:425 +msgid "" +"Here is a small example. Let's say we have a CSV file called *dem.csv* " +"containing" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:437 +msgid "" +"For the above data we will create a *dem.vrt* header with the following " +"content:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:450 +msgid "" +"This description specifies so called 2.5D geometry with three " +"coordinates X, Y and Z. The Z value will be used for interpolation. Now " +"you can use *dem.vrt* with all OGR programs (start with :ref:`ogrinfo`" +" to test that everything works fine). The datasource will contain a " +"single layer called *\"dem\"* filled with point features constructed " +"from values in the CSV file. Using this technique you can handle CSV " +"files with more than three columns, switch columns, etc. OK, now the " +"final step:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:462 +msgid "Or, if we do not wish to use a VRT file:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:469 +msgid "" +"If your CSV file does not contain column headers then it can be handled " +"in the VRT file in the following way:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:476 +msgid "" +"The :ref:`vector.csv` description page contains details on CSV format " +"supported by GDAL/OGR." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:480 +msgid "Creating multiband files" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:482 +msgid "" +"Creating multiband files is not directly possible with gdal_grid. One " +"might use gdal_grid multiple times to create one band per file, and then " +"use :ref:`gdalbuildvrt` -separate and then :ref:`gdal_translate`:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:492 +msgid "" +"Or just use :ref:`gdal_merge`, to combine the one-band files into a " +"single one:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:503 +msgid "This utility is also callable from C with :cpp:func:`GDALGrid`." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:508 +msgid "" +"The following would create raster TIFF file from VRT datasource described" +" in `Reading comma separated values`_ section using the inverse distance " +"to a power method. Values to interpolate will be read from Z value of " +"geometry record." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:517 +msgid "" +"The next command does the same thing as the previous one, but reads " +"values to interpolate from the attribute field specified with **-zfield**" +" option instead of geometry record. So in this case X and Y coordinates " +"are being taken from geometry and Z is being taken from the " +"*\"Elevation\"* field. The :config:`GDAL_NUM_THREADS` is also set to " +"parallelize the computation." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:5 +msgid "gdal_merge" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:9 +msgid "Mosaics a set of images." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:28 +msgid "" +"This utility will automatically mosaic a set of images. All the images " +"must be in the same coordinate system and have a matching number of " +"bands, but they may be overlapping, and at different resolutions. In " +"areas of overlap, the last image will be copied over earlier ones. " +"Nodata/transparency values are considered on a band by band level, i.e. a" +" nodata/transparent pixel on one source band will not set a " +"nodata/transparent value on all bands for the target pixel in the " +"resulting raster nor will it overwrite a valid pixel value." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:38 +msgid "" +"gdal_merge is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:46 +msgid "" +"The name of the output file, which will be created if it does not already" +" exist (defaults to \"out.tif\")." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:57 +msgid "" +"Pixel size to be used for the output file. If not specified the " +"resolution of the first input file will be used." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:63 +msgid "" +"(target aligned pixels) align the coordinates of the extent of the output" +" file to the values of the -tr, such that the aligned extent includes the" +" minimum extent. Alignment means that xmin / resx, ymin / resy, xmax / " +"resx and ymax / resy are integer values." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:70 +msgid "" +"The extents of the output file. If not specified the aggregate extents of" +" all input files will be used." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:80 +msgid "Generate verbose output of mosaicing operations as they are done." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:84 +msgid "Place each input file into a separate band." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:88 +msgid "" +"Grab a pseudo-color table from the first input image, and use it for the " +"output. Merging pseudo-colored images this way assumes that all input " +"files use the same color table." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:94 +msgid "Ignore pixels from files being merged in with this pixel value." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:102 +#: ../../source/programs/gdal_rasterize.rst:127 +msgid "" +"Pre-initialize the output image bands with these values. However, it is " +"not marked as the nodata value in the output file. If only one value is " +"given, the same value is used in all the bands." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:108 +msgid "" +"The output file is created (and potentially pre-initialized) but no input" +" image data is copied into it." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:116 +msgid "Creating an image with the pixels in all bands initialized to 255" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:124 +msgid "Creating an RGB image that shows blue in pixels with no data" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:126 +msgid "" +"The first two bands will be initialized to 0 and the third band will be " +"initialized to 255." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:135 +msgid "Passing a large list of files to :program:`gdal_merge`" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:137 +msgid "" +"A large list of files can be passed to :program:`gdal_merge` by listing " +"them in a text file using:" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:144 +msgid "on Linux, or" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:150 +msgid "" +"on Windows. The text file can then be passed to :program:`gdal_merge` " +"using `--optfile`:" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:158 +msgid "Creating an RGB image by merging 3 different greyscale bands" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:160 +msgid "" +"Conduct \"merging by stacking\" with the :option:`-separate` flag. Given " +"three greyscale files that cover the same area, you can run:" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:167 +msgid "" +"This maps :file:`1.tif` to red, :file:`2.tif` to green and :file:`3.tif` " +"to blue." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:170 +msgid "Specifying overlap precedence" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:172 +msgid "" +"The last image in the input line comes out on top of the finished image " +"stack. You might also need to use :option:`-n` to note which value should" +" not be copied into the destination image if it is not already defined as" +" nodata." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:5 +msgid "gdal_pansharpen" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:9 +msgid "Perform a pansharpen operation." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:11 +msgid "(Since GDAL 2.1)" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:33 +msgid "" +":program:`gdal_pansharpen` performs a pan-sharpening operation. It can " +"create a \"classic\" output dataset (such as GeoTIFF), or a VRT dataset " +"describing the pan-sharpening operation." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:37 +msgid "More details can be found in the :ref:`gdal_vrttut_pansharpen` section." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:41 +msgid "" +"gdal_pansharpen is a Python utility, and is only available if GDAL Python" +" bindings are available." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:47 +msgid "" +"Select the output format. Starting with GDAL 2.3, if not specified, the " +"format is guessed from the extension (previously was ``GTiff``). Use the " +"short format name. ``VRT`` can also be used." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:53 +msgid "" +"Select band *band* from the input spectral bands for output. Bands are " +"numbered from 1 in the order spectral bands are specified. Multiple " +"**-b** switches may be used. When no -b switch is used, all input " +"spectral bands are set for output." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:60 +msgid "" +"Specify a weight for the computation of the pseudo panchromatic value. " +"There must be as many -w switches as input spectral bands." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:65 +msgid "Select a resampling algorithm. ``cubic`` is the default." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:69 +msgid "" +"Specify number of threads to use to do the resampling and pan-sharpening " +"itself. Can be an integer number or ``ALL_CPUS``." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:74 +msgid "" +"Specify the bit depth of the panchromatic and spectral bands (e.g. 12). " +"If not specified, the NBITS metadata item from the panchromatic band will" +" be used if it exists." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:80 +msgid "" +"Specify nodata value for bands. Used for the resampling and pan-" +"sharpening computation itself. If not set, deduced from the input bands, " +"provided they have a consistent setting." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:86 +msgid "" +"Select behavior when bands have not the same extent. See " +"*SpatialExtentAdjustment* documentation in :ref:`gdal_vrttut_pansharpen` " +"``union`` is the default." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:98 +msgid "Dataset with panchromatic band (first band will be used)." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:102 +msgid "" +"Dataset with one or several spectral bands. If the band option is not " +"specified, all bands of the datasets are taken into account. Otherwise, " +"only the specified (num)th band. The same dataset can be repeated several" +" times." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:109 +msgid "Output dataset" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:111 +msgid "Bands should be in the same projection." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:116 +msgid "With spectral bands in a single dataset :" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:122 +msgid "With a few spectral bands from a single dataset, reordered :" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:128 +msgid "With spectral bands in several datasets :" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:134 +msgid "Specify weights:" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:140 +msgid "" +"Specify RGB bands from a RGBNir multispectral dataset while computing the" +" pseudo panchromatic intensity on the 4 RGBNir bands:" +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:5 +msgid "gdal_polygonize" +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:9 +msgid "Produces a polygon feature layer from a raster." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:26 +msgid "" +"This utility creates vector polygons for all connected regions of pixels " +"in the raster sharing a common pixel value. Each polygon is created with" +" an attribute indicating the pixel value of that polygon. A raster mask " +"may also be provided to determine which pixels are eligible for " +"processing." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:31 +msgid "" +"The utility will create the output vector datasource if it does not " +"already exist, otherwise it will try to append to an existing one." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:34 +msgid "" +"The utility is based on the ::cpp:func:`GDALPolygonize` function which " +"has additional details on the algorithm." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:39 +msgid "" +"gdal_polygonize is a Python utility, and is only available if GDAL Python" +" bindings are available." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:47 +msgid "Use 8 connectedness. Default is 4 connectedness." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:51 +msgid "" +"Do not use the default validity mask for the input band (such as nodata, " +"or alpha masks)." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:56 +msgid "" +"Use the first band of the specified file as a validity mask (zero is " +"invalid, non-zero is valid). If not specified, the default validity mask " +"for the input band (such as nodata, or alpha masks) will be used (unless " +"-nomask is specified)" +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:62 +msgid "The source raster file from which polygons are derived." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:66 +msgid "" +"The band on <raster_file> to build the polygons from. Starting with GDAL " +"2.2, the value can also be set to \"mask\", to indicate that the mask " +"band of the first band must be used (or \"mask,band_number\" for the mask" +" of a specified band)" +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:73 +msgid "" +"Select the output format. Starting with GDAL 2.3, if not specified, the " +"format is guessed from the extension (previously was GML). Use the short " +"format name" +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:81 +msgid "Polygonize option. See ::cpp:func:`GDALPolygonize` documentation." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:93 +msgid "Overwrite the output layer if it already exists." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:97 +msgid "The destination vector file to which the polygons will be written." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:101 +msgid "The name of the layer created to hold the polygon features." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:105 +msgid "The name of the field to create (defaults to \"DN\")." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:109 +msgid "" +"The script runs in quiet mode. The progress monitor is suppressed and " +"routine messages are not displayed." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:5 +msgid "gdal_proximity" +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:9 +msgid "Produces a raster proximity map." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:29 +msgid "" +":program:`gdal_proximity` generates a raster proximity map indicating the" +" distance from the center of each pixel to the center of the nearest " +"pixel identified as a target pixel. Target pixels are those in the " +"source raster for which the raster pixel value is in the set of target " +"pixel values." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:36 +msgid "" +"gdal_proximity is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:44 +msgid "The source raster file used to identify target pixels." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:48 +msgid "" +"The destination raster file to which the proximity map will be written. " +"It may be a pre-existing file of the same size as srcfile. If it does not" +" exist it will be created." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:54 +msgid "Identifies the band in the source file to use (default is 1)." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:58 +msgid "Identifies the band in the destination file to use (default is 1)." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:66 +msgid "" +"Specify a data type supported by the driver, which may be one of the " +"following: ``Byte``, ``UInt16``, ``Int16``, ``UInt32``, ``Int32``, " +"``Float32`` (default), or ``Float64``." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:72 +msgid "" +"A list of target pixel values in the source image to be considered target" +" pixels. If not specified, all non-zero pixels will be considered target " +"pixels." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:77 +msgid "" +"Indicate whether distances generated should be in pixel or georeferenced " +"coordinates (default PIXEL)." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:82 +msgid "" +"The maximum distance to be generated. The nodata value will be used for " +"pixels beyond this distance. If a nodata value is not provided, the " +"output band will be queried for its nodata value. If the output band does" +" not have a nodata value, then the value 65535 will be used. Distance is " +"interpreted in pixels unless -distunits GEO is specified." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:90 +msgid "Specify a nodata value to use for the destination proximity raster." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:94 +msgid "" +"Indicate whether nodata pixels in the input raster should be nodata in " +"the output raster (default NO)." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:98 +msgid "" +"Specify a value to be applied to all pixels that are within the -maxdist " +"of target pixels (including the target pixels) instead of a distance " +"value." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:5 +msgid "gdal_rasterize" +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:9 +msgid "Burns vector geometries into a raster" +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:33 +msgid "" +"This program burns vector geometries (points, lines, and polygons) into " +"the raster band(s) of a raster image. Vectors are read from OGR " +"supported vector formats. If the output raster already exists, the " +"affected pixels are updated in-place." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:38 +msgid "" +"Note that on the fly reprojection of vector data to the coordinate system" +" of the raster data is only supported since GDAL 2.1.0." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:47 +msgid "" +"The band(s) to burn values into. Multiple -b arguments may be used to " +"burn into a list of bands. The default is to burn into band 1. Not used" +" when creating a new raster." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:53 +msgid "" +"Invert rasterization. Burn the fixed burn value, or the burn value " +"associated with the first feature into all parts of the image *not* " +"inside the provided polygon." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:59 +msgid "" +"When the vector features contain a polygon nested within another polygon " +"(like an island in a lake), GDAL must be built against GEOS to get " +"correct results." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:65 +msgid "" +"Enables the ALL_TOUCHED rasterization option so that all pixels touched " +"by lines or polygons will be updated, not just those on the line render " +"path, or whose center point is within the polygon (behavior is " +"unspecified when the polygon is just touching the pixel center). Defaults" +" to disabled for normal rendering rules." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:73 +msgid "" +"A fixed value to burn into a band for all objects. A list of " +":option:`-burn` options can be supplied, one per band being written to." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:78 +msgid "" +"Identifies an attribute field on the features to be used for a burn-in " +"value. The value will be burned into all output bands." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:83 +msgid "" +"Indicates that a burn value should be extracted from the \"Z\" values of " +"the feature. Works with points and lines (linear interpolation along each" +" segment). For polygons, works properly only if the are flat (same Z " +"value for all vertices)." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:90 +msgid "" +"Instead of burning a new value, this adds the new value to the existing " +"raster. Suitable for heatmaps for instance." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:101 +msgid "" +"An optional SQL WHERE style query expression to be applied to select " +"features to burn in from the input layer(s)." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:106 +msgid "" +"An SQL statement to be evaluated against the datasource to produce a " +"virtual layer of features to be burned in. Starting with GDAL 3.7, the " +"``@filename`` syntax can be used to indicate that the content is in the " +"pointed filename." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:113 +msgid "" +"SQL dialect. In some cases can be used to use (unoptimized) OGR SQL " +"instead of the native SQL of an RDBMS by passing OGRSQL. The \"SQLITE\" " +"dialect can also be used with any datasource." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:133 +msgid "" +"Override the projection for the output file. If not specified, the " +"projection of the input vector file will be used if available. When using" +" this option, no reprojection of features from the SRS of the input " +"vector to the specified SRS of the output raster, so use only this option" +" to correct an invalid source SRS. The <srs_def> may be any of the usual " +"GDAL/OGR forms, complete WKT, PROJ.4, EPSG:n or a file containing the " +"WKT." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:142 +msgid "" +"set a transformer option suitable to pass to " +":cpp:func:`GDALCreateGenImgProjTransformer2`. This is used when " +"converting geometries coordinates to target raster pixel space. For " +"example this can be used to specify RPC related transformer options." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:153 +msgid "" +"Set georeferenced extents. The values must be expressed in georeferenced " +"units. If not specified, the extent of the output file will be the extent" +" of the vector layers." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:164 +msgid "" +"(target aligned pixels) Align the coordinates of the extent of the output" +" file to the values of the :option:`-tr`, such that the aligned extent " +"includes the minimum extent. Alignment means that xmin / resx, ymin / " +"resy, xmax / resx and ymax / resy are integer values." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:171 +msgid "" +"Set output file size in pixels and lines. Note that :option:`-ts` cannot " +"be used with :option:`-tr`" +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:176 +msgid "" +"Force the output bands to be of the indicated data type. Defaults to " +"``Float64``" +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:180 +msgid "" +"Force the algorithm used (results are identical). The raster mode is used" +" in most cases and optimise read/write operations. The vector mode is " +"useful with a decent amount of input features and optimise the CPU use. " +"That mode have to be used with tiled images to be efficient. The auto " +"mode (the default) will chose the algorithm based on input and output " +"properties." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:204 +msgid "" +"The GDAL supported output file. Must support update mode access. This " +"file will be created if it does not already exist If the output raster " +"already exists, the affected pixels are updated in-place." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:208 +msgid "" +"The program creates a new target raster image when any of the " +":option:`-of`, :option:`-a_nodata`, :option:`-init`, :option:`-a_srs`, " +":option:`-co`, :option:`-te`, :option:`-tr`, :option:`-tap`, " +":option:`-ts`, or :option:`-ot` options are used. The resolution or size " +"must be specified using the :option:`-tr` or :option:`-ts` option for all" +" new rasters. The target raster will be overwritten if it already exists" +" and any of these creation-related options are used." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:218 +msgid "This utility is also callable from C with :cpp:func:`GDALRasterize`." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:225 +msgid "" +"The following would burn all polygons from mask.shp into the RGB TIFF " +"file work.tif with the color red (RGB = 255,0,0)." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:233 +msgid "" +"The following would burn all \"class A\" buildings into the output " +"elevation file, pulling the top elevation from the ROOF_H attribute." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:240 +msgid "" +"The following would burn all polygons from footprint.shp into a new " +"1000x1000 rgb TIFF as the color red. Note that :option:`-b` is not used;" +" the order of the :option:`-burn` options determines the bands of the " +"output raster." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:5 +msgid "gdal_retile" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:9 +msgid "Retiles a set of tiles and/or build tiled pyramid levels." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:34 +msgid "" +"This utility will retile a set of input tile(s). All the input tile(s) " +"must be georeferenced in the same coordinate system and have a matching " +"number of bands." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:37 +msgid "" +"Optionally pyramid levels are generated. All pyramid levels are generated" +" from the input tiles (not from previous levels)." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:40 +msgid "It is possible to generate shape file(s) for the tiled output." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:42 +msgid "" +"If your number of input tiles exhausts the command line buffer, use the " +"general :ref:`--optfile <raster_common_options_optfile>` option" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:47 +#: ../../source/programs/gdal_sieve.rst:39 +msgid "" +"gdal_retile is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:55 +msgid "" +"The directory where the tile result is created. Pyramids are stored in " +"sub-directories numbered from 1. Created tile names have a numbering " +"schema and contain the name of the source tiles(s)" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:67 +msgid "" +"Pixel size to be used for the output file. If not specified, 256 x 256 " +"is the default" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:72 +msgid "" +"Overlap in pixels between consecutive tiles. If not specified, 0 is the " +"default" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:78 +msgid "Number of pyramids levels to build." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:82 +msgid "Generate verbose output of tile operations as they are done." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:86 +msgid "No retiling, build only the pyramids" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:90 +msgid "Resampling algorithm, default is near" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:94 +msgid "" +"Source spatial reference to use. The coordinate systems that can be " +"passed are anything supported by the " +"OGRSpatialReference.SetFromUserInput() call, which includes EPSG, PCS," +" and GCSes (i.e. EPSG:4296), PROJ.4 declarations (as above), or the name " +"of a .prj file containing well known text. If no srs_def is given, " +"the srs_def of the source tiles is used (if there is any). The srs_def " +"will be propagated to created tiles (if possible) and to the optional " +"shape file(s)" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:104 +msgid "The name of shape file containing the result tile(s) index" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:108 +msgid "The name of the attribute containing the tile name" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:112 +msgid "" +"The name of the csv file containing the tile(s) georeferencing " +"information. The file contains 5 columns: tilename,minx,maxx,miny,maxy" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:117 +msgid "" +"The column delimiter used in the CSV file, default value is a semicolon " +"\";\"" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:121 +msgid "" +"Normally the tiles of the base image are stored as described in " +":option:`-targetDir`. For large images, some file systems have " +"performance problems if the number of files in a directory is too big, " +"causing gdal_retile not to finish in reasonable time. Using this " +"parameter creates a different output structure. The tiles of the base " +"image are stored in a sub-directory called 0, the pyramids in sub-" +"directories numbered 1,2,.... Within each of these directories another " +"level of sub-directories is created, numbered from 0...n, depending of " +"how many tile rows are needed for each level. Finally, a directory " +"contains only the tiles for one row for a specific level. For large " +"images a performance improvement of a factor N could be achieved." +msgstr "" + +#: ../../source/programs/gdal_sieve.rst:5 +msgid "gdal_sieve" +msgstr "" + +#: ../../source/programs/gdal_sieve.rst:9 +msgid "Removes small raster polygons." +msgstr "" + +#: ../../source/programs/gdal_sieve.rst:25 +msgid "" +":program:`gdal_sieve` removes raster polygons smaller than a provided " +"threshold size (in pixels) and replaces them with the pixel value of the " +"largest neighbour polygon. The result can be written back to the existing" +" raster band, or copied into a new file." +msgstr "" + +#: ../../source/programs/gdal_sieve.rst:30 +msgid "" +"The input dataset is read as integer data which means that floating point" +" values are rounded to integers. Re-scaling source data may be necessary " +"in some cases (e.g. 32-bit floating point data with min=0 and max=1)." +msgstr "" + +#: ../../source/programs/gdal_sieve.rst:34 +msgid "" +"Additional details on the algorithm are available in the " +":cpp:func:`GDALSieveFilter` docs." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:5 +msgid "gdal_translate" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:9 +msgid "Converts raster data between different formats." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:45 +msgid "" +"The :program:`gdal_translate` utility can be used to convert raster data " +"between different formats, potentially performing some operations like " +"subsettings, resampling, and rescaling pixels in the process." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:57 +msgid "" +"Don't be forgiving of mismatches and lost data when translating to the " +"output format." +msgstr "" + +#: ../../source/programs/options/if.rst:3 +msgid "" +"Format/driver name to be attempted to open the input file(s). It is " +"generally not necessary to specify it, but it can be used to skip " +"automatic driver detection, when it fails to select the appropriate " +"driver. This option can be repeated several times to specify several " +"candidate drivers. Note that it does not force those drivers to open the " +"dataset. In particular, some drivers have requirements on file " +"extensions." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:66 +msgid "" +"Select an input band **band** for output. Bands are numbered from 1. " +"Multiple :option:`-b` switches may be used to select a set of input bands" +" to write to the output file, or to reorder bands. **band** can also be " +"set to \"mask,1\" (or just \"mask\") to mean the mask band of the first " +"band of the input dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:74 +msgid "" +"Select an input band **band** to create output dataset mask band. Bands " +"are numbered from 1. **band** can be set to \"none\" to avoid copying the" +" global mask of the input dataset if it exists. Otherwise it is copied by" +" default (\"auto\"), unless the mask is an alpha channel, or if it is " +"explicitly used to be a regular band of the output dataset (\"-b mask\")." +" **band** can also be set to \"mask,1\" (or just \"mask\") to mean the " +"mask band of the 1st band of the input dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:84 +msgid "" +"To expose a dataset with 1 band with a color table as a dataset with 3 " +"(RGB) or 4 (RGBA) bands. Useful for output drivers such as JPEG, " +"JPEG2000, MrSID, ECW that don't support color indexed datasets. The " +"'gray' value enables to expand a dataset with a color table that only " +"contains gray levels to a gray indexed dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:92 +msgid "" +"Set the size of the output file. Outsize is in pixels and lines unless " +"'%' is attached in which case it is as a fraction of the input image " +"size. If one of the 2 values is set to 0, its value will be determined " +"from the other one, while maintaining the aspect ratio of the source " +"dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:99 +msgid "" +"set target resolution. The values must be expressed in georeferenced " +"units. Both must be positive values. This is mutually exclusive with " +":option:`-outsize`, :option:`-a_ullr`, and :option:`-a_gt`." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:107 +msgid "" +"To specify which overview level of source file must be used. The default " +"choice, AUTO, will select the overview level whose resolution is the " +"closest to the target resolution. Specify an integer value (0-based, i.e." +" 0=1st overview level) to select a particular level. Specify AUTO-n where" +" n is an integer greater or equal to 1, to select an overview level below" +" the AUTO one. Or specify NONE to force the base resolution to be used " +"(can be useful if overviews have been generated with a low quality " +"resampling method, and a higher quality resampling method is specified " +"with :option:`-r`." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:116 +msgid "" +"When :option:`-ovr` is specified to an integer value, and none of " +":option:`-outsize` and :option:`-tr` is specified, the size of the " +"overview will be used as the output size." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:120 +msgid "" +"When :option:`-ovr` is specified, values of :option:`-srcwin`, when " +"specified, should be expressed as pixel offset and size of the full " +"resolution source dataset. Similarly when using :option:`-outsize` with " +"percentage values, they refer to the size of the full resolution source " +"dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:127 +msgid "Select a resampling algorithm." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:129 +msgid "" +"``nearest`` (default) applies a nearest neighbour (simple sampling) " +"resampler" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:131 +#: ../../source/programs/gdaladdo.rst:49 +msgid "" +"``average`` computes the average of all non-NODATA contributing pixels. " +"Starting with GDAL 3.1, this is a weighted average taking into account " +"properly the weight of source pixels not contributing fully to the target" +" pixel." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:133 +#: ../../source/programs/gdaladdo.rst:51 +msgid "" +"``rms`` computes the root mean squared / quadratic mean of all non-NODATA" +" contributing pixels (GDAL >= 3.3)" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:135 +#: ../../source/programs/gdaladdo.rst:53 +msgid "``bilinear`` applies a bilinear convolution kernel." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:137 +#: ../../source/programs/gdaladdo.rst:60 +msgid "``cubic`` applies a cubic convolution kernel." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:139 +#: ../../source/programs/gdaladdo.rst:62 +msgid "``cubicspline`` applies a B-Spline convolution kernel." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:141 +#: ../../source/programs/gdaladdo.rst:64 +msgid "``lanczos`` applies a Lanczos windowed sinc convolution kernel." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:143 +#: ../../source/programs/gdaladdo.rst:68 +msgid "" +"``mode`` selects the value which appears most often of all the sampled " +"points." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:147 +msgid "" +"Rescale the input pixels values from the range **src_min** to **src_max**" +" to the range **dst_min** to **dst_max**. If omitted the output range is " +"0 to 255. If omitted the input range is automatically computed from the " +"source dataset, in its whole (not just the window of interest potentially" +" specified with :option:`-srcwin` or :option:`-projwin`). This may be a " +"slow operation on a large source dataset, and if using it multiple times " +"for several gdal_translate invocation, it might be beneficial to call " +"``gdalinfo -stats {source_dataset}`` priorly to precompute statistics, " +"for formats that support serializing statistics computations (GeoTIFF, " +"VRT...) Note that the values specified after :option:`-scale` are only " +"used to compute a scale and offset to apply to the input raster values. " +"In particular, ``src_min`` and ``src_max`` are not used to clip input " +"values. :option:`-scale` can be repeated several times (if specified only" +" once, it also applies to all bands of the output dataset), so as to " +"specify per band parameters. It is also possible to use the \"-scale_bn\"" +" syntax where bn is a band number (e.g. \"-scale_2\" for the 2nd band of " +"the output dataset) to specify the parameters of one or several specific " +"bands." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:168 +msgid "" +"To apply non-linear scaling with a power function. exp_val is the " +"exponent of the power function (must be positive). This option must be " +"used with the -scale option. If specified only once, -exponent applies to" +" all bands of the output image. It can be repeated several times so as to" +" specify per band parameters. It is also possible to use the " +"\"-exponent_bn\" syntax where bn is a band number (e.g. \"-exponent_2\" " +"for the 2nd band of the output dataset) to specify the parameters of one " +"or several specific bands." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:178 +msgid "" +"Apply the scale/offset metadata for the bands to convert scaled values to" +" unscaled values. It is also often necessary to reset the output " +"datatype with the :option:`-ot` switch. The unscaled value is computed " +"from the scaled raw value with the following formula:" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:184 +msgid "" +"{unscaled\\_value} = {scaled\\_value} * {scale} + {offset}\n" +"\n" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:193 +msgid "" +"Selects a subwindow from the source image for copying (like " +":option:`-srcwin`) but with the corners given in georeferenced " +"coordinates (by default expressed in the SRS of the dataset. Can be " +"changed with :option:`-projwin_srs`)." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:200 +msgid "" +"In GDAL 2.1.0 and 2.1.1, using -projwin with coordinates not aligned with" +" pixels will result in a sub-pixel shift. This has been corrected in " +"later versions. When selecting non-nearest neighbour resampling, starting" +" with GDAL 2.1.0, sub-pixel accuracy is however used to get better " +"results." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:208 +msgid "" +"Specifies the SRS in which to interpret the coordinates given with " +":option:`-projwin`. The <srs_def> may be any of the usual GDAL/OGR forms," +" complete WKT, PROJ.4, EPSG:n or a file containing the WKT." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:213 +msgid "This does not cause reprojection of the dataset to the specified SRS." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:217 +msgid "" +"(Error when Partially Outside) If this option is set, :option:`-srcwin` " +"or :option:`-projwin` values that falls partially outside the source " +"raster extent will be considered as an error. The default behavior is to " +"accept such requests, when they were considered as an error before." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:224 +msgid "" +"(Error when Completely Outside) Same as :option:`-epo`, except that the " +"criterion for erroring out is when the request falls completely outside " +"the source raster extent." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:230 +msgid "" +"Override the projection for the output file. Can be used with " +":option:`-a_ullr` or :option:`-a_gt` to specify the extent in this " +"projection." +msgstr "" + +#: ../../source/programs/options/srs_def.rst:1 +msgid "" +"The coordinate reference systems that can be passed are anything " +"supported by the :cpp:func:`OGRSpatialReference::SetFromUserInput` call, " +"which includes EPSG Projected, Geographic or Compound CRS (i.e. " +"EPSG:4296), a well known text (WKT) CRS definition, PROJ.4 declarations, " +"or the name of a .prj file containing a WKT CRS definition." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:235 +msgid "No reprojection is done." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:241 +msgid "" +"Assign a coordinate epoch, linked with the output SRS. Useful when the " +"output SRS is a dynamic CRS." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:246 +msgid "" +"Set band scaling value. No modification of pixel values is done. Note " +"that the :option:`-unscale` does not take into account " +":option:`-a_scale`. You may for example specify ``-scale 0 1 <offset> " +"<offset+scale>`` to apply a (offset, scale) tuple, for the equivalent of " +"the 2 steps: ``gdal_translate input.tif tmp.vrt -a_scale scale -a_offset " +"offset`` followed by ``gdal_translate tmp.vrt output.tif -unscale``" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:257 +msgid "" +"Set band offset value. No modification of pixel values is done. Note that" +" the :option:`-unscale` does not take into account :option:`-a_offset`. " +"You may for example specify ``-scale 0 1 <offset> <offset+scale>`` to " +"apply a (offset, scale) tuple, for the equivalent of the 2 steps: " +"``gdal_translate input.tif tmp.vrt -a_scale scale -a_offset offset`` " +"followed by ``gdal_translate tmp.vrt output.tif -unscale``" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:268 +msgid "" +"Assign/override the georeferenced bounds of the output file. This " +"assigns georeferenced bounds to the output file, ignoring what would have" +" been derived from the source file. So this does not cause reprojection " +"to the specified SRS. This is mutually exclusive with :option:`-a_gt`" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:276 +msgid "" +"Assign/override the geotransform of the output file. This assigns the " +"geotransform to the output file, ignoring what would have been derived " +"from the source file. So this does not cause reprojection to the " +"specified SRS. See :ref:`geotransforms_tut`. This is mutually exclusive " +"with :option:`-a_ullr`" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:286 +msgid "" +"Assign a specified nodata value to output bands. It can be set to " +"``none`` to avoid setting a nodata value to the output file if one exists" +" for the source file. Note that, if the input dataset has a nodata value," +" this does not cause pixel values that are equal to that nodata value to " +"be changed to the value specified with this option." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:294 +msgid "" +"Override the color interpretation of band X (where X is a valid band " +"number, starting at 1)" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:301 +msgid "" +"Override the color interpretation of all specified bands. For example " +"-colorinterp red,green,blue,alpha for a 4 band output dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:312 +msgid "" +"Passes a metadata key and value in specified domain to set on the output " +"dataset if possible." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:334 +msgid "" +"In addition to the driver-specific creation options, gdal_translate (and " +":cpp:func:`GDALTranslate` and :cpp:func:`GDALCreateCopy`) recognize the " +"following options:" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:342 +msgid "" +"Can be specified to YES to avoid prior destruction of existing dataset, " +"for drivers that support adding several subdatasets (e.g. GTIFF, NITF)" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:350 +msgid "" +"Defines if metadata domains of the source dataset should be copied to the" +" destination dataset. In the default AUTO mode, only \"safe\" domains " +"will be copied, which include the default metadata domain (some drivers " +"may include other domains such as IMD, RPC, GEOLOCATION). When setting " +"YES, all domains will be copied (but a few reserved ones like " +"IMAGE_STRUCTURE or DERIVED_SUBDATASETS). Currently only recognized by the" +" GTiff, COG, VRT, PNG and JPEG drivers." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:359 +msgid "When setting NO, no source metadata will be copied." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:365 +msgid "" +"Defines which source metadata domain should be copied. This option " +"restricts the list of source metadata domains to be copied (it implies " +"COPY_SRC_MDD=YES if it is not set). This option may be specified as many " +"times as they are source domains. The default metadata domain is the " +"empty string \"\" (\"_DEFAULT_\") may also be used when empty string is " +"not practical). Currently only recognized by the GTiff, COG, VRT, PNG and" +" JPEG drivers." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:374 +msgid "Do not copy the GCPs in the source dataset to the output dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:378 +msgid "" +"Add the indicated ground control point to the output dataset. This " +"option may be provided multiple times to provide a set of GCPs." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:387 +msgid "" +"Copy all subdatasets of this file to individual output files. Use with " +"formats like HDF that have subdatasets." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:392 +msgid "Force (re)computation of statistics." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:396 +msgid "Do not copy source RAT into destination dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:400 +msgid "" +"Do not copy the XMP metadata in the source dataset to the output dataset " +"when driver is able to copy it." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:419 +#: ../../source/programs/gdaladdo.rst:258 +msgid "Nodata / source validity mask handling during resampling" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:421 +msgid "" +"Masked values, either identified through a nodata value metadata set on " +"the source band, a mask band, an alpha band will not be used during " +"resampling (when using :option:`-outsize` or :option:`-tr`)." +msgstr "" + +#: ../../source/programs/nodata_handling_gdaladdo_gdal_translate.rst:1 +msgid "" +"The details of how it is taken into account depends on the resampling " +"kernel:" +msgstr "" + +#: ../../source/programs/nodata_handling_gdaladdo_gdal_translate.rst:3 +msgid "" +"for nearest resampling, for each target pixel, one of the potential " +"contributing source pixels is selected (in an implementation specific " +"way). Its value is used as it, be it valid or invalid." +msgstr "" + +#: ../../source/programs/nodata_handling_gdaladdo_gdal_translate.rst:7 +msgid "" +"for bilinear, cubic, cubicspline and lanczos, for each target pixel, the " +"weights of contributing source pixels is set to zero to ignore them when " +"they are masked. There is an extra specificity for cubic: given that some" +" of the weights in the kernel are negative, such strategy could lead to " +"strong overshoot/undershoot when there is an alternance of valid and " +"invalid pixels. Consequently, if any of the horizontal or vertical " +"direction, if the maximum number of valid source pixels in each dimension" +" is less than the radius of the resampling kernel, the target pixel is " +"considered as nodata." +msgstr "" + +#: ../../source/programs/nodata_handling_gdaladdo_gdal_translate.rst:16 +msgid "" +"for the other resampling methods, source pixels contributing to the " +"target pixel are ignored if masked. Only the valid ones are taken into " +"account. If there are none, the target pixel is considered as nodata." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:430 +msgid "This utility is also callable from C with :cpp:func:`GDALTranslate`." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:442 +msgid "To create a JPEG-compressed TIFF with internal mask from a RGBA dataset" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:450 +msgid "To create a RGBA dataset from a RGB dataset with a mask" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:457 +msgid "Subsetting using :option:`-projwin` and :option:`-outsize`:" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:5 +msgid "gdal_viewshed" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:11 +msgid "" +"Calculates a viewshed raster from an input raster DEM using method " +"defined in [Wang2000]_ for a user defined point." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:33 +msgid "" +"By default the :program:`gdal_viewshed` generates a binary visibility " +"raster from one band of the input raster elevation model (DEM). The " +"output raster will be of type Byte. With the -mode flag can also return a" +" minimum visible height raster of type Float64." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:38 +msgid "" +"The algorithm as implemented currently will only output meaningful " +"results if the georeferencing is in a projected coordinate reference " +"system." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:49 +msgid "" +"Select an input band **band** containing the DEM data. Bands are numbered" +" from 1. Only a single band can be used. Only the part of the raster " +"within the specified maximum distance around the observer point is " +"processed." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:55 +msgid "The value to be set for the cells in the output raster that have no data." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:58 +msgid "" +"Currently, no special processing of input cells at a nodata value is done" +" (which may result in erroneous results)." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:63 +msgid "The X position of the observer (in SRS units)." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:67 +msgid "The Y position of the observer (in SRS units)." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:71 +msgid "" +"The height of the observer above the DEM surface in the height unit of " +"the DEM. Default: 2" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:75 +msgid "" +"The height of the target above the DEM surface in the height unit of the " +"DEM. Default: 0" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:79 +msgid "" +"Maximum distance from observer to compute visibiliy. It is also used to " +"clamp the extent of the output raster." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:84 +msgid "" +"Coefficient to consider the effect of the curvature and refraction. When " +"calculating visibility between two points (i.e. Line Of Sight or " +"Viewshed), The magnitude of this effect varies with atmospheric " +"conditions and depends on the wavelength." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:88 +msgid "" +"Different applications for calculating visibility use different " +"interchangeable notation to describe this phenomena: Refraction " +"Coefficient, Curvature Coefficient, and Sphere Diameter Factor. " +"gdal_viewshed uses the Curvature Coefficient notation." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:92 +msgid "{CurvCoeff}=1-{RefractionCoeff}" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:96 +msgid "" +"Changes in air density curve the light downward causing an observer to " +"see further and the earth to appear less curved, as if the sphere (earth)" +" diameter is larger then it actually is. The ratio between that imaginary" +" sphere diameter and the actual sphere diameter is given by the formula:" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:100 +msgid "" +"{SphereDiameterFactor}=1/{CurvCoeff}=1/(1-{RefractionCoeff})\n" +"\n" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:103 +msgid "" +"For visible light, the standard atmospheric refraction coefficient that " +"is generally used is 1/7. Thus the default value (since GDAL 3.4) for " +"CurvCoeff that gdal_viewshed uses is 0.85714 (=~ 1-1/7) for Earth CRS. " +"Starting with GDAL 3.6, for non-Earth CRS (those whole semi-major axis " +"differs by more than 5% with the one of WGS 84), CurvCoeff default value " +"is 1.0, to account for the no refraction use case." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:109 +msgid "The height of the DEM is corrected according to the following formula:" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:111 +msgid "Height_{Corrected}=Height_{DEM}-{CurvCoeff}\\frac{{TargetDistance}^2}{SphereDiameter}" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:115 +msgid "" +"Typical coefficient values are given in the table below (use Curvature " +"Coeff value for the cc option)" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:118 +msgid "Use Case" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:118 +msgid "Refraction Coeff" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:118 +msgid "**Curvature Coeff**" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:118 +msgid "Sphere Diameter Factor" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:119 +msgid "No Refraction" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:119 +#: ../../source/programs/gdal_viewshed.rst:122 +msgid "0" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:119 +#: ../../source/programs/gdal_viewshed.rst:122 +msgid "1" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:120 +msgid "Visible Light" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:120 +msgid "1/7" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:120 +msgid "6/7 (=~0.85714)" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:120 +msgid "7/6 (=~1.1666)" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:121 +msgid "Radio Waves" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:121 +msgid "0.25 ~ 0.325" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:121 +msgid "0.75 ~ 0.675" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:121 +msgid "1.33 ~ 1.48" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:122 +msgid "Flat Earth" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:122 +msgid "inf" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:127 +msgid "Pixel value to set for invisible areas. Default: 0" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:131 +msgid "" +"Pixel value to set for the cells that fall outside of the range specified" +" by the observer location and the maximum distance. Default: 0" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:136 +msgid "Pixel value to set for visible areas. Default: 255" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:140 +msgid "Sets what information the output contains." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:142 +msgid "Possible values: NORMAL, DEM, GROUND" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:144 +msgid "NORMAL returns a raster of type Byte containing visible locations." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:146 +msgid "" +"DEM and GROUND will return a raster of type Float64 containing the " +"minimum target height for target to be visible from the DEM surface or " +"ground level respectively. Flags -tz, -iv and -vv will be ignored." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:150 +msgid "Default NORMAL" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:155 +msgid "" +"Functionality of this utility can be done from C with " +":cpp:func:`GDALViewshedGenerate`." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:160 +msgid "" +"Screenshot of 2 combined viewshed analysis, with the yellow pixels " +"showing the area that is visible from the both observation locations (the" +" green dots), while the small green area is only visible from one " +"location." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:168 +msgid "" +"Create a viewshed raster with a radius of 500 for a person standing at " +"location (-10147017, 5108065)." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:175 +msgid "Reference" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:177 +msgid "" +"Generating Viewsheds without Using Sightlines. Wang, Jianjun, Robinson, " +"Gary J., and White, Kevin. Photogrammetric Engineering and Remote " +"Sensing. p81. https://www.asprs.org/wp-" +"content/uploads/pers/2000journal/january/2000_jan_87-90.pdf" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:5 +msgid "gdaladdo" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:9 +msgid "Builds or rebuilds overview images." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:29 +msgid "" +"The :program:`gdaladdo` utility can be used to build or rebuild overview " +"images for most supported file formats with one of several downsampling " +"algorithms." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:38 +msgid "" +"Select a resampling algorithm. The default is ``nearest``, which is " +"generally not appropriate if sub-pixel accuracy is desired." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:41 +msgid "" +"Starting with GDAL 3.9, when refreshing existing TIFF overviews, the " +"previously used method, as noted in the RESAMPLING metadata item of the " +"overview, will be used if :option:`-r` is not specified." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:45 +msgid "The available methods are:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:47 +msgid "``nearest`` applies a nearest neighbour (simple sampling) resampler." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:55 +msgid "" +"``gauss`` applies a Gaussian kernel before computing the overview, which " +"can lead to better results than simple averaging in e.g case of sharp " +"edges with high contrast or noisy patterns. The advised level values " +"should be 2, 4, 8, ... so that a 3x3 resampling Gaussian kernel is " +"selected." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:66 +msgid "``average_magphase`` averages complex data in mag/phase space." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:72 +msgid "" +"Select an input band **band** for overview generation. Band numbering " +"starts from 1. Multiple :option:`-b` switches may be used to select a set" +" of input bands to generate overviews." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:78 +msgid "" +"open the dataset in read-only mode, in order to generate external " +"overview (for GeoTIFF especially)." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:83 +msgid "remove all overviews." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:91 +msgid "" +"Maximum width or height of the smallest overview level. Only taken into " +"account if explicit levels are not specified. Defaults to 256." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:100 +msgid "" +"This option performs a partial refresh of existing overviews, when " +"<filename> is a VRT file with an external overview. It checks the " +"modification timestamp of all the sources of the VRT and regenerate the " +"overview for areas corresponding to sources whose timestamp is more " +"recent than the external overview of the VRT. By default all existing " +"overview levels will be refreshed, unless explicit levels are specified." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:112 +msgid "" +"This option performs a partial refresh of existing overviews, in the " +"region of interest specified by georeference coordinates where <ulx> is " +"the X value of the upper left corner, <uly> is the Y value of the upper " +"left corner, <lrx> is the X value of the lower right corner and <lry> is " +"the Y value of the lower right corner. By default all existing overview " +"levels will be refreshed, unless explicit levels are specified." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:124 +msgid "" +"This option performs a partial refresh of existing overviews, in the " +"region of interest specified by one or several filenames (names separated" +" by comma). Note that the filenames are only used to determine the " +"regions of interest to refresh. The reference source pixels are the one " +"of the main dataset. By default all existing overview levels will be " +"refreshed, unless explicit levels are specified." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:133 +msgid "The file to build overviews for (or whose overviews must be removed)." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:137 +msgid "" +"A list of integral overview levels to build. Ignored with " +":option:`-clean` option." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:141 +msgid "" +"Levels are no longer required to build overviews. In which case, " +"appropriate overview power-of-two factors will be selected until the " +"smallest overview is smaller than the value of the -minsize switch." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:145 +msgid "" +"Starting with GDAL 3.9, if there are already existing overviews, the " +"corresponding levels will be used to refresh them if no explicit levels " +"are specified." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:150 +msgid "" +"gdaladdo will honour properly NODATA_VALUES tuples (special dataset " +"metadata) so that only a given RGB triplet (in case of a RGB image) will " +"be considered as the nodata value and not each value of the triplet " +"independently per band." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:154 +msgid "" +"Selecting a level value like ``2`` causes an overview level that is 1/2 " +"the resolution (in each dimension) of the base layer to be computed. If " +"the file has existing overview levels at a level selected, those levels " +"will be recomputed and rewritten in place." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:159 +msgid "" +"For internal GeoTIFF overviews (or external overviews in GeoTIFF format)," +" note that -clean does not shrink the file. A later run of gdaladdo with " +"overview levels will cause the file to be expanded, rather than reusing " +"the space of the previously deleted overviews. If you just want to change" +" the resampling method on a file that already has overviews computed, you" +" don't need to clean the existing overviews." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:165 +msgid "" +"Some format drivers do not support overviews at all. Many format drivers" +" store overviews in a secondary file with the extension .ovr that is " +"actually in TIFF format. By default, the GeoTIFF driver stores overviews" +" internally to the file operated on (if it is writable), unless the -ro " +"flag is specified." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:170 +msgid "" +"Most drivers also support an alternate overview format using Erdas " +"Imagine format. To trigger this use the :config:`USE_RRD=YES` " +"configuration option. This will place the overviews in an associated " +".aux file suitable for direct use with Imagine or ArcGIS as well as GDAL " +"applications. (e.g. --config USE_RRD YES)" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:176 +msgid "External overviews in GeoTIFF format" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:178 +msgid "" +"External overviews created in TIFF format may be compressed using the " +":config:`COMPRESS_OVERVIEW` configuration option. All compression " +"methods, supported by the GeoTIFF driver, are available here. (e.g. " +"``--config COMPRESS_OVERVIEW DEFLATE``). The photometric interpretation " +"can be set with the :config:`PHOTOMETRIC_OVERVIEW` =RGB/YCBCR/... " +"configuration option, and the interleaving with the " +":config:`INTERLEAVE_OVERVIEW` =PIXEL/BAND configuration option." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:185 +msgid "" +"Since GDAL 3.6, :config:`COMPRESS_OVERVIEW` and " +":config:`INTERLEAVE_OVERVIEW` are honoured when creating internal " +"overviews of TIFF files." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:188 +msgid "" +"For JPEG compressed external and internal overviews, the JPEG quality can" +" be set with ``--config JPEG_QUALITY_OVERVIEW value``." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:191 +msgid "" +"For WEBP compressed external and internal overviews, the WEBP quality " +"level can be set with ``--config WEBP_LEVEL_OVERVIEW value``. If not set," +" will default to 75." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:194 +msgid "" +"For WEBP compressed external and internal overviews, the WEBP " +"lossless/lossy switch can be set with ``--config WEBP_LOSSLESS_OVERVIEW " +"value``. If not set, will default to NO (lossy). Added in GDAL 3.6.0" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:197 +msgid "" +"For LERC compressed external and internal overviews, the max error " +"threshold can be set with ``--config MAX_Z_ERROR_OVERVIEW value``. If not" +" set, will default to 0 (lossless). Added in GDAL 3.4.1" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:200 +msgid "" +"For DEFLATE or LERC_DEFLATE compressed external and internal overviews, " +"the compression level can be set with ``--config ZLEVEL_OVERVIEW value``." +" If not set, will default to 6. Added in GDAL 3.4.1" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:203 +msgid "" +"For ZSTD or LERC_ZSTD compressed external and internal overviews, the " +"compression level can be set with ``--config ZSTD_LEVEL_OVERVIEW value``." +" If not set, will default to 9. Added in GDAL 3.4.1" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:206 +msgid "" +"For JPEG-XL compressed external and internal overviews, the following " +"settings can be set since GDAL 3.9.0:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:208 +msgid "" +"Whether compression should be lossless with ``--config " +"JXL_LOSSLESS_OVERVIEW YES|NO``. Default is YES" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:210 +msgid "" +"Level of effort with ``--config JXL_EFFORT_OVERVIEW value``, with value " +"between 1(fast) and 9(flow). Default is 5" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:212 +msgid "" +"Distance level for lossy compression with ``--config " +"JXL_DISTANCE_OVERVIEW value``, with value: 0=mathematically lossless, " +"1.0=visually lossless, usual range [0.5,3]. Default is 1.0. Ignored if " +"JXL_LOSSLESS_OVERVIEW is YES" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:214 +msgid "" +"Distance level for lossy compression of alpha channel with ``--config " +"JXL_ALPHA_DISTANCE_OVERVIEW value``, with value: 0=mathematically " +"lossless, 1.0=visually lossless, usual range [0.5,3]. Default is the same" +" value as JXL_DISTANCE_OVERVIEW. Ignored if JXL_LOSSLESS_OVERVIEW is YES" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:217 +msgid "" +"For LZW, ZSTD or DEFLATE compressed external overviews, the predictor " +"value can be set with ``--config PREDICTOR_OVERVIEW 1|2|3``." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:220 +msgid "To produce the smallest possible JPEG-In-TIFF overviews, you should use:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:226 +msgid "" +"External overviews can be created in the BigTIFF format by using the " +":config:`BIGTIFF_OVERVIEW` configuration option: ``--config " +"BIGTIFF_OVERVIEW {IF_NEEDED|IF_SAFER|YES|NO}``." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:230 +msgid "" +"The default value is IF_SAFER starting with GDAL 2.3.0 (previously was " +"IF_NEEDED). The behavior of this option is exactly the same as the " +"BIGTIFF creation option documented in the GeoTIFF driver documentation." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:234 +msgid "YES forces BigTIFF." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:235 +msgid "NO forces classic TIFF." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:236 +msgid "" +"IF_NEEDED will only create a BigTIFF if it is clearly needed " +"(uncompressed, and overviews larger than 4GB)." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:238 +msgid "IF_SAFER will create BigTIFF if the resulting file *might* exceed 4GB." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:240 +msgid "" +"Sparse GeoTIFF overview files (that is tiles which are omitted if all " +"their pixels are at the nodata value, when there's one, or at 0 " +"otherwise) can be obtained with ``--config SPARSE_OK_OVERVIEW ON``. Added" +" in GDAL 3.4.1" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:244 +msgid "" +"See the documentation of the :ref:`raster.gtiff` driver for further " +"explanations on all those options." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:247 +msgid "Setting blocksize in Geotiff overviews" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:249 +msgid "``--config GDAL_TIFF_OVR_BLOCKSIZE <size>``" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:251 +msgid "Example: ``--config GDAL_TIFF_OVR_BLOCKSIZE 256``" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:253 +msgid "" +"Default value is 128, or starting with GDAL 3.1, if creating overviews on" +" a tiled GeoTIFF file, the tile size of the full resolution image. Note: " +"without this setting, the file can have the full resolution image with a " +"blocksize different from overviews blocksize.(e.g. full resolution image " +"at blocksize 256, overviews at blocksize 128)" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:260 +msgid "" +"Invalid values in source pixels, either identified through a nodata value" +" metadata set on the source band, a mask band, an alpha band will not be " +"used during resampling." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:267 ../../source/programs/sozip.rst:137 +msgid "Multithreading" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:271 +msgid "" +"The :config:`GDAL_NUM_THREADS` configuration option can be set to " +"``ALL_CPUS`` or a integer value to specify the number of threads to use " +"for overview computation." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:278 +msgid "" +"Functionality of this utility can be done from C with " +":cpp:func:`GDALBuildOverviews`." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:283 +msgid "" +"Create overviews, embedded in the supplied TIFF file, with automatic " +"computation of levels (GDAL 2.3 or later)" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:290 +msgid "Create overviews, embedded in the supplied TIFF file:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:296 +msgid "" +"Create an external compressed GeoTIFF overview file from the ERDAS .IMG " +"file:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:302 +msgid "" +"Create an external JPEG-compressed GeoTIFF overview file from a 3-band " +"RGB dataset (if the dataset is a writable GeoTIFF, you also need to add " +"the -ro option to force the generation of external overview):" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:311 +msgid "Create an Erdas Imagine format overviews for the indicated JPEG file:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:317 +msgid "" +"Create overviews for a specific subdataset, like for example one of " +"potentially many raster layers in a GeoPackage (the \"filename\" " +"parameter must be driver prefix, filename and subdataset name, like e.g. " +"shown by gdalinfo):" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:324 +msgid "" +"Refresh overviews of a VRT file, for sources that have been modified " +"after the .vrt.ovr generation:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:335 +msgid "Refresh overviews of a TIFF file:" +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:5 +msgid "gdalattachpct" +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:9 +msgid "Attach a color table from one file to another file." +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:24 +msgid "" +"This utility will attach a color table file from an input raster file or " +"a color table file to another raster." +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:28 +msgid "" +"gdalattachpct is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:42 +msgid "" +"Extract the color table from <palette_file>. The<palette_file> must be " +"either a raster file in a GDAL supported format with a palette or a color" +" file in a supported format (txt, qml, qlr)." +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:48 +#: ../../source/programs/pct2rgb.rst:58 +msgid "The input file." +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:52 +#: ../../source/programs/pct2rgb.rst:62 +msgid "The output RGB file that will be created." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:5 +msgid "gdalbuildvrt" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:9 +msgid "Builds a VRT from a list of datasets." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:38 +msgid "" +"This program builds a VRT (Virtual Dataset) that is a mosaic of the list " +"of input GDAL datasets. The list of input GDAL datasets can be specified " +"at the end of the command line, or put in a text file (one filename per " +"line) for very long lists, or it can be a MapServer tileindex (see " +":ref:`gdaltindex` utility). In the later case, all entries in the tile " +"index will be added to the VRT." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:46 +msgid "" +"Starting with GDAL 3.9, for virtual mosaic with a very large number of " +"source rasters (typically hundreds of thousands of source rasters, or " +"more), it is advised to use the :ref:`gdaltindex` utility to generate a " +"tile index compatible of the :ref:`GTI <raster.gti>` driver." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:51 +msgid "" +"With -separate, each files goes into a separate band in the VRT dataset. " +"Otherwise, the files are considered as source rasters of a larger mosaic " +"and the VRT file has as many bands as one of the input files." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:55 +msgid "" +"If one GDAL dataset is made of several subdatasets and has 0 raster " +"bands, all the subdatasets will be added to the VRT rather than the " +"dataset itself." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:58 +msgid "" +"gdalbuildvrt does some amount of checks to assure that all files that " +"will be put in the resulting VRT have similar characteristics : number of" +" bands, projection, color interpretation... If not, files that do not " +"match the common characteristics will be skipped. (This is only true in " +"the default mode, and not when using the -separate option)" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:63 +msgid "" +"If there is some amount of spatial overlapping between files, the order " +"of files appearing in the list of source matter: files that are listed at" +" the end are the ones from which the content will be fetched. Note that " +"nodata will be taken into account to potentially fetch data from less " +"priority datasets, but currently, alpha channel is not taken into account" +" to do alpha compositing (so a source with alpha=0 appearing on top of " +"another source will override is content). This might be changed in later " +"versions." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:77 +msgid "" +"Use the specified value as the tile index field, instead of the default " +"value which is 'location'." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:82 +msgid "" +"In case the resolution of all input files is not the same, the " +"-resolution flag enables the user to control the way the output " +"resolution is computed." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:85 +msgid "" +"`highest` will pick the smallest values of pixel dimensions within the " +"set of source rasters." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:87 +msgid "" +"`lowest` will pick the largest values of pixel dimensions within the set " +"of source rasters." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:89 +msgid "" +"`average` is the default and will compute an average of pixel dimensions " +"within the set of source rasters." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:91 +msgid "" +"`user` must be used in combination with the :option:`-tr` option to " +"specify the target resolution." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:95 +msgid "" +"Set target resolution. The values must be expressed in georeferenced " +"units. Both must be positive values. Specifying those values is of course" +" incompatible with highest|lowest|average values for " +":option:`-resolution` option." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:102 +msgid "" +"(target aligned pixels) align the coordinates of the extent of the output" +" file to the values of the :option:`-tr`, such that the aligned extent " +"includes the minimum extent. Alignment means that xmin / resx, ymin / " +"resy, xmax / resx and ymax / resy are integer values." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:109 +msgid "" +"Set georeferenced extents of VRT file. The values must be expressed in " +"georeferenced units. If not specified, the extent of the VRT is the " +"minimum bounding box of the set of source rasters." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:114 +msgid "" +"Adds an alpha mask band to the VRT when the source raster have none. " +"Mainly useful for RGB sources (or grey-level sources). The alpha band is " +"filled on-the-fly with the value 0 in areas without any source raster, " +"and with value 255 in areas with source raster. The effect is that a RGBA" +" viewer will render the areas without source rasters as transparent and " +"areas with source rasters as opaque. This option is not compatible with " +":option:`-separate`." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:122 +msgid "" +"Even if any band contains nodata value, giving this option makes the VRT " +"band not report the NoData. Useful when you want to control the " +"background color of the dataset. By using along with the -addalpha " +"option, you can prepare a dataset which doesn't report nodata value but " +"is transparent in areas with no data." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:130 +msgid "" +"Set nodata values for input bands (different values can be supplied for " +"each band). If more than one value is supplied all values should be " +"quoted to keep them together as a single operating system argument. If " +"the option is not specified, the intrinsic nodata settings on the source " +"datasets will be used (if they exist). The value set by this option is " +"written in the NODATA element of each ComplexSource element. Use a value " +"of `None` to ignore intrinsic nodata settings on the source datasets." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:141 +msgid "" +"Starting with GDAL 3.3, if a source has a mask band (internal/external " +"mask band, or alpha band), a <ComplexSource> element is created by " +"default with a <UseMaskBand>true</UseMaskBand> child element, to instruct" +" the VRT driver to use the mask band of the source to mask pixels being " +"composited. This is a generalization of the NODATA element. When " +"specifying the -ignore_srcmaskband option, the mask band of sources will " +"not be taken into account, and in case of overlapping between sources, " +"the last one will override previous ones in areas of overlap." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:154 +msgid "" +"Insert a <NoDataFromMaskSource> source, which replaces the value of the " +"source with the value of :option:`-vrtnodata` (or 0 if not specified) " +"when the value of the mask band of the source is less or equal to the " +"threshold. This is typically used to transform a R,G,B,A image into a " +"R,G,B one with a NoData value." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:161 +msgid "" +"Select an input <band> to be processed. Bands are numbered from 1. If " +"input bands not set all bands will be added to vrt. Multiple :option:`-b`" +" switches may be used to select a set of input bands." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:167 +msgid "" +"If the input dataset contains several subdatasets, use a subdataset with " +"the specified number (starting from 1). This is an alternative of giving " +"the full subdataset name as an input to the utility." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:173 +msgid "" +"Set nodata values at the VRT band level (different values can be supplied" +" for each band). If more than one value is supplied all values should be" +" quoted to keep them together as a single operating system argument. If " +"the option is not specified, intrinsic nodata settings on the first " +"dataset will be used (if they exist). The value set by this option is " +"written in the NoDataValue element of each VRTRasterBand element. Use a " +"value of `None` to ignore intrinsic nodata settings on the source " +"datasets." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:182 +msgid "" +"Place each input file into a separate band. Contrary to the default mode," +" it is not required that all bands have the same datatype." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:185 +msgid "" +"Starting with GDAL 3.8, all bands of each input file are added as " +"separate VRT bands, unless :option:`-b` is specified to select a subset " +"of them. Before GDAL 3.8, only the first band of each input file was " +"placed into a new VRT band, and :option:`-b` was ignored." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:192 +msgid "" +"When this option is specified, the utility will accept to make a VRT even" +" if the input datasets have not the same projection. Note: this does not " +"mean that they will be reprojected. Their projection will just be " +"ignored." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:198 +msgid "" +"Override the projection for the output file. The <srs_def> may be any of" +" the usual GDAL/OGR forms, complete WKT, PROJ.4, EPSG:n or a file " +"containing the WKT. No reprojection is done." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:203 +msgid "Select a resampling algorithm. Nearest is the default" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:213 +msgid "To specify a text file with an input filename on each line" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:217 +msgid "To disable the progress bar on the console" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:221 +msgid "Overwrite the VRT if it already exists." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:225 +msgid "" +"Turn warnings as failures. This is mutually exclusive with -non_strict, " +"the latter which is the default." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:231 +msgid "" +"Skip source datasets that have issues with warnings, and continue " +"processing. This is the default." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:238 +msgid "Make a virtual mosaic from all TIFF files contained in a directory :" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:244 +msgid "Make a virtual mosaic from files whose name is specified in a text file :" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:251 +msgid "Make a RGB virtual mosaic from 3 single-band input files :" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:257 +msgid "Make a virtual mosaic with blue background colour (RGB: 0 0 255) :" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:266 +msgid "This utility is also callable from C with :cpp:func:`GDALBuildVRT`." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:5 +msgid "gdalcompare" +msgstr "" + +#: ../../source/programs/gdalcompare.rst:9 +msgid "Compare two images." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:28 +msgid "" +":program:`gdalcompare` compares two GDAL supported datasets and reports " +"the differences. In addition to reporting differences to the standard " +"output the script will also return the difference count in its exit " +"value." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:33 +msgid "" +"Image pixels, and various metadata are checked. There is also a byte by " +"byte comparison done which will count as one difference. So if it is only" +" important that the GDAL visible data is identical a difference count of " +"1 (the binary difference) should be considered acceptable." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:40 +msgid "" +"gdalcompare is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:50 +msgid "" +"Whether to output the difference in pixel content in a TIFF file in the " +"current directory." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:57 +msgid "Whether to skip exact comparison of binary content." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:63 +msgid "Whether to skip comparison of overviews." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:69 +msgid "Whether to skip comparison of GEOLOCATION metadata domain." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:75 +msgid "Whether to skip comparison of geotransform matrix." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:81 +msgid "Whether to skip comparison of metadata" +msgstr "" + +#: ../../source/programs/gdalcompare.rst:87 +msgid "" +"Whether to skip comparison of Rational Polynomial Coefficients (RPC) " +"metadata domain." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:93 +msgid "Whether to skip comparison of spatial reference systems (SRS)." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:97 +msgid "" +"If this flag is passed the script will compare all subdatasets that are " +"part of the dataset, otherwise subdatasets are ignored." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:102 +msgid "The file that is considered correct, referred to as the golden file." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:106 +msgid "The file being compared to the golden file, referred to as the new file." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:109 +msgid "" +"Note that the :program:`gdalcompare` script (like all the other scripts) " +"can also be called as a library from python code: `from osgeo_utils " +"import gdalcompare`. The primary entry point is " +"`gdalcompare.compare_db()` which takes a golden `gdal.Dataset` and a new " +"`gdal.Dataset` as arguments and returns a difference count (excluding the" +" binary comparison). The `gdalcompare.compare_sds()` entry point can be " +"used to compare subdatasets." +msgstr "" + +#: ../../source/programs/gdaldem.rst:5 +msgid "gdaldem" +msgstr "" + +#: ../../source/programs/gdaldem.rst:9 +msgid "Tools to analyze and visualize DEMs." +msgstr "" + +#: ../../source/programs/gdaldem.rst:20 +msgid "From any GDAL-supported elevation raster:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:22 +msgid "Generate a shaded relief map:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:32 +msgid "Generate a slope map:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:41 +msgid "" +"Generate an aspect map, outputs a 32-bit float raster with pixel values " +"from 0-360 indicating azimuth:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:51 +msgid "Generate a color relief map:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:61 +msgid "Generate a Terrain Ruggedness Index (TRI) map:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:69 +msgid "Generate a Topographic Position Index (TPI) map:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:76 +msgid "Generate a roughness map:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:86 +msgid "" +"The :program:`gdaldem` generally assumes that x, y and z units are " +"identical. If x (east-west) and y (north-south) units are identical, but " +"z (elevation) units are different, the scale (-s) option can be used to " +"set the ratio of vertical units to horizontal. For LatLong projections " +"near the equator, where units of latitude and units of longitude are " +"similar, elevation (z) units can be converted to be compatible by using " +"scale=370400 (if elevation is in feet) or scale=111120 (if elevation is " +"in meters). For locations not near the equator, it would be best to " +"reproject your grid using gdalwarp before using gdaldem." +msgstr "" + +#: ../../source/programs/gdaldem.rst:98 +#: ../../source/programs/ogr_layer_algebra.rst:46 +msgid "Where <mode> is one of the seven available modes:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:100 +msgid "``hillshade``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:102 +msgid "Generate a shaded relief map from any GDAL-supported elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:104 +msgid "``slope``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:106 +msgid "Generate a slope map from any GDAL-supported elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:108 +msgid "``aspect``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:110 +msgid "Generate an aspect map from any GDAL-supported elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:112 +msgid "``color-relief``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:114 +msgid "Generate a color relief map from any GDAL-supported elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:116 +msgid "``TRI``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:118 +msgid "" +"Generate a map of Terrain Ruggedness Index from any GDAL-supported " +"elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:120 +msgid "``TPI``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:122 +msgid "" +"Generate a map of Topographic Position Index from any GDAL-supported " +"elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:124 +msgid "``roughness``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:126 +msgid "Generate a map of roughness from any GDAL-supported elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:128 +msgid "The following general options are available:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:134 +msgid "The input DEM raster to be processed" +msgstr "" + +#: ../../source/programs/gdaldem.rst:138 +msgid "The output raster produced" +msgstr "" + +#: ../../source/programs/gdaldem.rst:142 +msgid "Select the output format." +msgstr "" + +#: ../../source/programs/gdaldem.rst:146 +msgid "" +"If not specified, the format is guessed from the extension (previously " +"was :ref:`raster.gtiff`). Use the short format name." +msgstr "" + +#: ../../source/programs/gdaldem.rst:151 +msgid "Do the computation at raster edges and near nodata values" +msgstr "" + +#: ../../source/programs/gdaldem.rst:155 +msgid "Select an input band to be processed. Bands are numbered from 1." +msgstr "" + +#: ../../source/programs/gdaldem.rst:163 +msgid "" +"For all algorithms, except color-relief, a nodata value in the target " +"dataset will be emitted if at least one pixel set to the nodata value is " +"found in the 3x3 window centered around each source pixel. The " +"consequence is that there will be a 1-pixel border around each image set " +"with nodata value." +msgstr "" + +#: ../../source/programs/gdaldem.rst:168 +msgid "" +"If :option:`-compute_edges` is specified, gdaldem will compute values at " +"image edges or if a nodata value is found in the 3x3 window, by " +"interpolating missing values." +msgstr "" + +#: ../../source/programs/gdaldem.rst:173 +msgid "Modes" +msgstr "" + +#: ../../source/programs/gdaldem.rst:176 +msgid "hillshade" +msgstr "" + +#: ../../source/programs/gdaldem.rst:178 +msgid "" +"This command outputs an 8-bit raster with a nice shaded relief effect. " +"It’s very useful for visualizing the terrain. You can optionally specify " +"the azimuth and altitude of the light source, a vertical exaggeration " +"factor and a scaling factor to account for differences between vertical " +"and horizontal units." +msgstr "" + +#: ../../source/programs/gdaldem.rst:180 +msgid "The value 0 is used as the output nodata value." +msgstr "" + +#: ../../source/programs/gdaldem.rst:182 ../../source/programs/gdaldem.rst:231 +msgid "The following specific options are available :" +msgstr "" + +#: ../../source/programs/gdaldem.rst:186 ../../source/programs/gdaldem.rst:235 +#: ../../source/programs/gdaldem.rst:254 +msgid "" +"The literature suggests Zevenbergen & Thorne to be more suited to smooth " +"landscapes, whereas Horn's formula to perform better on rougher terrain." +msgstr "" + +#: ../../source/programs/gdaldem.rst:190 +msgid "Vertical exaggeration used to pre-multiply the elevations" +msgstr "" + +#: ../../source/programs/gdaldem.rst:194 +msgid "" +"Ratio of vertical units to horizontal. If the horizontal unit of the " +"source DEM is degrees (e.g Lat/Long WGS84 projection), you can use " +"scale=111120 if the vertical units are meters (or scale=370400 if they " +"are in feet)" +msgstr "" + +#: ../../source/programs/gdaldem.rst:198 +msgid "" +"Azimuth of the light, in degrees. 0 if it comes from the top of the " +"raster, 90 from the east, ... The default value, 315, should rarely be " +"changed as it is the value generally used to generate shaded maps." +msgstr "" + +#: ../../source/programs/gdaldem.rst:202 +msgid "" +"Altitude of the light, in degrees. 90 if the light comes from above the " +"DEM, 0 if it is raking light." +msgstr "" + +#: ../../source/programs/gdaldem.rst:206 +msgid "combined shading, a combination of slope and oblique shading." +msgstr "" + +#: ../../source/programs/gdaldem.rst:210 +msgid "" +"multidirectional shading, a combination of hillshading illuminated from " +"225 deg, 270 deg, 315 deg, and 360 deg azimuth." +msgstr "" + +#: ../../source/programs/gdaldem.rst:216 +msgid "" +"shading which tries to minimize effects on other map features beneath. " +"Can't be used with -alt option." +msgstr "" + +#: ../../source/programs/gdaldem.rst:220 +msgid "" +"Multidirectional hillshading applies the formula of " +"http://pubs.usgs.gov/of/1992/of92-422/of92-422.pdf." +msgstr "" + +#: ../../source/programs/gdaldem.rst:222 +msgid "" +"Igor's hillshading uses formula from Maperitive " +"http://maperitive.net/docs/Commands/GenerateReliefImageIgor.html." +msgstr "" + +#: ../../source/programs/gdaldem.rst:225 +msgid "slope" +msgstr "" + +#: ../../source/programs/gdaldem.rst:227 +msgid "" +"This command will take a DEM raster and output a 32-bit float raster with" +" slope values. You have the option of specifying the type of slope value " +"you want: degrees or percent slope. In cases where the horizontal units " +"differ from the vertical units, you can also supply a scaling factor." +msgstr "" + +#: ../../source/programs/gdaldem.rst:229 +msgid "The value `-9999` is used as the output nodata value." +msgstr "" + +#: ../../source/programs/gdaldem.rst:239 +msgid "" +"If specified, the slope will be expressed as percent slope. Otherwise, it" +" is expressed as degrees" +msgstr "" + +#: ../../source/programs/gdaldem.rst:241 +msgid ":option:`-s`" +msgstr "" + +#: ../../source/programs/gdaldem.rst:243 +msgid "" +"Ratio of vertical units to horizontal. If the horizontal unit of the " +"source DEM is degrees (e.g Lat/Long WGS84 projection), you can use " +"scale=111120 if the vertical units are meters (or scale=370400 if they " +"are in feet)." +msgstr "" + +#: ../../source/programs/gdaldem.rst:246 +msgid "aspect" +msgstr "" + +#: ../../source/programs/gdaldem.rst:248 +msgid "" +"This command outputs a 32-bit float raster with values between 0° and " +"360° representing the azimuth that slopes are facing. The definition of " +"the azimuth is such that : 0° means that the slope is facing the North, " +"90° it's facing the East, 180° it's facing the South and 270° it's facing" +" the West (provided that the top of your input raster is north oriented)." +" The aspect value -9999 is used as the nodata value to indicate undefined" +" aspect in flat areas with slope=0." +msgstr "" + +#: ../../source/programs/gdaldem.rst:250 ../../source/programs/gdaldem.rst:273 +msgid "The following specifics options are available :" +msgstr "" + +#: ../../source/programs/gdaldem.rst:258 +msgid "" +"Return trigonometric angle instead of azimuth. Thus 0° means East, 90° " +"North, 180° West, 270° South." +msgstr "" + +#: ../../source/programs/gdaldem.rst:262 +msgid "Return 0 for flat areas with slope=0, instead of -9999." +msgstr "" + +#: ../../source/programs/gdaldem.rst:264 +msgid "" +"By using those 2 options, the aspect returned by gdaldem aspect should be" +" identical to the one of GRASS r.slope.aspect. Otherwise, it's identical " +"to the one of Matthew Perry's :file:`aspect.cpp` utility." +msgstr "" + +#: ../../source/programs/gdaldem.rst:269 +msgid "color-relief" +msgstr "" + +#: ../../source/programs/gdaldem.rst:271 +msgid "" +"This command outputs a 3-band (RGB) or 4-band (RGBA) raster with values " +"are computed from the elevation and a text-based color configuration " +"file, containing the association between various elevation values and the" +" corresponding wished color. By default, the colors between the given " +"elevation values are blended smoothly and the result is a nice colorized " +"DEM. The -exact_color_entry or -nearest_color_entry options can be used " +"to avoid that linear interpolation for values that don't match an index " +"of the color configuration file." +msgstr "" + +#: ../../source/programs/gdaldem.rst:277 +msgid "Text-based color configuration file" +msgstr "" + +#: ../../source/programs/gdaldem.rst:281 +msgid "Add an alpha channel to the output raster" +msgstr "" + +#: ../../source/programs/gdaldem.rst:285 +msgid "" +"Use strict matching when searching in the color configuration file. If " +"none matching color entry is found, the \"0,0,0,0\" RGBA quadruplet will " +"be used" +msgstr "" + +#: ../../source/programs/gdaldem.rst:290 +msgid "" +"Use the RGBA quadruplet corresponding to the closest entry in the color " +"configuration file." +msgstr "" + +#: ../../source/programs/gdaldem.rst:292 +msgid "" +"The color-relief mode is the only mode that supports VRT as output " +"format. In that case, it will translate the color configuration file into" +" appropriate LUT elements. Note that elevations specified as percentage " +"will be translated as absolute values, which must be taken into account " +"when the statistics of the source raster differ from the one that was " +"used when building the VRT." +msgstr "" + +#: ../../source/programs/gdaldem.rst:298 +msgid "" +"The text-based color configuration file generally contains 4 columns per " +"line: the elevation value and the corresponding Red, Green, Blue " +"component (between 0 and 255). The elevation value can be any floating " +"point value, or the nv keyword for the nodata value. The elevation can " +"also be expressed as a percentage: 0% being the minimum value found in " +"the raster, 100% the maximum value." +msgstr "" + +#: ../../source/programs/gdaldem.rst:305 +msgid "" +"An extra column can be optionally added for the alpha component. If it is" +" not specified, full opacity (255) is assumed." +msgstr "" + +#: ../../source/programs/gdaldem.rst:308 +msgid "Various field separators are accepted: comma, tabulation, spaces, ':'." +msgstr "" + +#: ../../source/programs/gdaldem.rst:310 +msgid "" +"Common colors used by GRASS can also be specified by using their name, " +"instead of the RGB triplet. The supported list is: white, black, red, " +"green, blue, yellow, magenta, cyan, aqua, grey/gray, orange, brown, " +"purple/violet and indigo." +msgstr "" + +#: ../../source/programs/gdaldem.rst:315 +msgid "" +"GMT :file:`.cpt` palette files are also supported (COLOR_MODEL = RGB " +"only)." +msgstr "" + +#: ../../source/programs/gdaldem.rst:317 +msgid "" +"Note: the syntax of the color configuration file is derived from the one " +"supported by GRASS r.colors utility. ESRI HDR color table files (.clr) " +"also match that syntax. The alpha component and the support of tab and " +"comma as separators are GDAL specific extensions." +msgstr "" + +#: ../../source/programs/gdaldem.rst:322 +msgid "For example:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:334 +msgid "" +"To implement a \"round to the floor value\" mode, the elevation value can" +" be duplicate with a new value being slightly above the threshold. For " +"example to have red in [0,10], green in ]10,20] and blue in ]20,30]:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:348 +msgid "TRI" +msgstr "" + +#: ../../source/programs/gdaldem.rst:350 +msgid "" +"This command outputs a single-band raster with values computed from the " +"elevation. `TRI` stands for Terrain Ruggedness Index, which measures the " +"difference between a central pixel and its surrounding cells." +msgstr "" + +#: ../../source/programs/gdaldem.rst:354 ../../source/programs/gdaldem.rst:379 +#: ../../source/programs/gdaldem.rst:390 +msgid "The value -9999 is used as the output nodata value." +msgstr "" + +#: ../../source/programs/gdaldem.rst:356 +msgid "The following option is available:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:360 +msgid "" +"Starting with GDAL 3.3, the Riley algorithm (see Riley, S.J., De Gloria, " +"S.D., Elliot, R. (1999): A Terrain Ruggedness that Quantifies Topographic" +" Heterogeneity. Intermountain Journal of Science, Vol.5, No.1-4, " +"pp.23-27) is available and the new default value. This algorithm uses the" +" square root of the sum of the square of the difference between a central" +" pixel and its surrounding cells. This is recommended for terrestrial use" +" cases." +msgstr "" + +#: ../../source/programs/gdaldem.rst:367 +msgid "" +"The Wilson (see Wilson et al 2007, Marine Geodesy 30:3-35) algorithm uses" +" the mean difference between a central pixel and its surrounding cells. " +"This is recommended for bathymetric use cases." +msgstr "" + +#: ../../source/programs/gdaldem.rst:372 +msgid "TPI" +msgstr "" + +#: ../../source/programs/gdaldem.rst:374 +msgid "" +"This command outputs a single-band raster with values computed from the " +"elevation. `TPI` stands for Topographic Position Index, which is defined " +"as the difference between a central pixel and the mean of its surrounding" +" cells (see Wilson et al 2007, Marine Geodesy 30:3-35)." +msgstr "" + +#: ../../source/programs/gdaldem.rst:381 ../../source/programs/gdaldem.rst:392 +msgid "There are no specific options." +msgstr "" + +#: ../../source/programs/gdaldem.rst:384 +msgid "roughness" +msgstr "" + +#: ../../source/programs/gdaldem.rst:386 +msgid "" +"This command outputs a single-band raster with values computed from the " +"elevation. Roughness is the largest inter-cell difference of a central " +"pixel and its surrounding cell, as defined in Wilson et al (2007, Marine " +"Geodesy 30:3-35)." +msgstr "" + +#: ../../source/programs/gdaldem.rst:397 +msgid "This utility is also callable from C with :cpp:func:`GDALDEMProcessing`." +msgstr "" + +#: ../../source/programs/gdaldem.rst:402 +msgid "Authors" +msgstr "" + +#: ../../source/programs/gdaldem.rst:404 +msgid "" +"Matthew Perry perrygeo@gmail.com, Even Rouault " +"even.rouault@spatialys.com, Howard Butler hobu.inc@gmail.com, Chris " +"Yesson chris.yesson@ioz.ac.uk" +msgstr "" + +#: ../../source/programs/gdaldem.rst:407 +msgid "" +"Derived from code by Michael Shapiro, Olga Waupotitsch, Marjorie Larson, " +"Jim Westervelt: U.S. Army CERL, 1993. GRASS 4.1 Reference Manual. U.S. " +"Army Corps of Engineers, Construction Engineering Research Laboratories, " +"Champaign, Illinois, 1-425." +msgstr "" + +#: ../../source/programs/gdaldem.rst:412 +#: ../../source/programs/gdaltindex.rst:341 +#: ../../source/programs/gdalwarp.rst:758 +msgid "See also" +msgstr "" + +#: ../../source/programs/gdaldem.rst:414 +msgid "Documentation of related GRASS utilities:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:416 +msgid "https://grass.osgeo.org/grass79/manuals/r.slope.aspect.html" +msgstr "" + +#: ../../source/programs/gdaldem.rst:418 +msgid "https://grass.osgeo.org/grass79/manuals/r.relief.html" +msgstr "" + +#: ../../source/programs/gdaldem.rst:420 +msgid "https://grass.osgeo.org/grass79/manuals/r.colors.html" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:5 +msgid "gdalinfo" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:9 +msgid "Lists information about a raster dataset." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:29 +msgid "" +":program:`gdalinfo` program lists various information about a GDAL " +"supported raster dataset." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:32 +#: ../../source/programs/gdalmdiminfo.rst:32 +msgid "The following command line parameters can appear in any order" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:40 +msgid "" +"Display the output in json format. Since GDAL 3.6, this includes key-" +"value pairs useful for building a `STAC item " +"<https://github.com/radiantearth/stac-spec/blob/v1.0.0/item-spec/item-" +"spec.md>`_ , including statistics and histograms if ``-stats`` or " +"``-hist`` flags are passed, respectively." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:48 +msgid "" +"Force computation of the actual min/max values for each band in the " +"dataset." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:53 +#: ../../source/programs/gdalmdiminfo.rst:69 +msgid "" +"Read and display image statistics. Force computation if no statistics are" +" stored in an image." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:58 +msgid "" +"Read and display image statistics. Force computation if no statistics are" +" stored in an image. However, they may be computed based on overviews or " +"a subset of all tiles. Useful if you are in a hurry and don't want " +"precise stats." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:65 +msgid "Report histogram information for all bands." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:69 +msgid "" +"Suppress ground control points list printing. It may be useful for " +"datasets with huge amount of GCPs, such as L1B AVHRR or HDF4 MODIS which " +"contain thousands of them." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:75 ../../source/programs/ogrinfo.rst:175 +msgid "" +"Suppress metadata printing. Some datasets may contain a lot of metadata " +"strings." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:80 +msgid "Suppress printing of raster attribute table." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:84 +msgid "Suppress printing of color table." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:88 +msgid "Force computation of the checksum for each band in the dataset." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:92 ../../source/programs/ogrinfo.rst:180 +msgid "List all metadata domains available for the dataset." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:96 +msgid "adds metadata using:" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:98 +msgid "``domain`` Report metadata for the specified domain." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:100 +msgid "``all`` Report metadata for all domains." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:104 +msgid "Only display the first file of the file list." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:108 +msgid "WKT format used to display the SRS. Currently the supported values are:" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:111 ../../source/programs/ogrinfo.rst:216 +msgid "``WKT1``" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:113 +msgid "``WKT2`` (latest WKT version, currently *WKT2_2019*)" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:115 ../../source/programs/ogrinfo.rst:220 +msgid "``WKT2_2015``" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:117 +msgid "``WKT2_2018`` (deprecated)" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:119 +msgid "``WKT2_2019``" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:125 +msgid "" +"If the input dataset contains several subdatasets read and display a " +"subdataset with specified ``n`` number (starting from 1). This is an " +"alternative of giving the full subdataset name." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:131 +msgid "Report a PROJ.4 string corresponding to the file's coordinate system." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:135 +msgid "Dataset open option (format specific)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:140 +msgid "The gdalinfo will report all of the following (if known):" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:142 +msgid "The format driver used to access the file." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:143 +msgid "Raster size (in pixels and lines)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:144 +msgid "The coordinate system for the file (in OGC WKT)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:145 +msgid "" +"The geotransform associated with the file (rotational coefficients are " +"currently not reported)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:147 +msgid "" +"Corner coordinates in georeferenced, and if possible lat/long based on " +"the full geotransform (but not GCPs)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:149 +msgid "Ground control points." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:150 +msgid "File wide (including subdatasets) metadata." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:151 +msgid "Band data types." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:152 +msgid "Band color interpretations." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:153 +msgid "Band block size." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:154 +msgid "Band descriptions." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:155 +msgid "Band min/max values (internally known and possibly computed)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:156 +msgid "Band checksum (if computation asked)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:157 +msgid "Band NODATA value." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:158 +msgid "Band overview resolutions available." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:159 +msgid "Band unit type (i.e.. \"meters\" or \"feet\" for elevation bands)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:160 +msgid "Band pseudo-color tables." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:165 +msgid "This utility is also callable from C with :cpp:func:`GDALInfo`." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:201 +msgid "" +"For corner coordinates formatted as decimal degree instead of the above " +"degree, minute, second, inspect the ``wgs84Extent`` member of gdalinfo " +"-json:" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:203 +msgid "Example of JSON output with ``gdalinfo -json byte.tif``" +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:5 +msgid "gdallocationinfo" +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:9 +msgid "Raster query tool" +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:29 +msgid "" +"The :program:`gdallocationinfo` utility provide a mechanism to query " +"information about a pixel given its location in one of a variety of " +"coordinate systems. Several reporting options are provided." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:39 +msgid "The output report will be XML formatted for convenient post processing." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:43 +msgid "" +"The only output is filenames production from the LocationInfo request " +"against the database (i.e. for identifying impacted file from VRT)." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:48 +msgid "" +"The only output is the pixel values of the selected pixel on each of the " +"selected bands. By default, the value of each band is output on a " +"separate line, unless :option:`-field_sep` is specified." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:54 +msgid "" +"Selects a band to query. Multiple bands can be listed. By default all " +"bands are queried." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:59 +msgid "" +"Query the (overview_level)th overview (overview_level=1 is the 1st " +"overview), instead of the base band. Note that the x,y location (if the " +"coordinate system is pixel/line) must still be given with respect to the " +"base band." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:65 +msgid "The coordinate system of the input x, y location." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:69 +msgid "Indicates input x,y points are in the georeferencing system of the image." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:73 +msgid "Indicates input x,y points are WGS84 long, lat." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:83 +msgid "" +"Set this flag to avoid extra non-numeric content at end of input lines to" +" be appended to the output lines in -valonly mode (requires " +":option:`-field_sep` to be also defined), or as a dedicated field in " +"default or :option:`-xml` modes." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:91 +msgid "" +"Enable Echo mode, where input coordinates are prepended to the output " +"lines in :option:`-valonly` mode." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:98 +msgid "" +"Defines the field separator, used in :option:`-valonly` mode, to separate" +" different values. It defaults to the new-line character, which means " +"that when querying a raster with several bands, the output will contain " +"one value per line, which may make it hard to recognize which value " +"belongs to which set of input x,y points when several ones are provided. " +"Defining the field separator is also needed" +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:107 +msgid "The source GDAL raster datasource name." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:111 +msgid "" +"X location of target pixel. By default the coordinate system is " +"pixel/line unless -l_srs, -wgs84 or -geoloc supplied." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:116 +msgid "" +"Y location of target pixel. By default the coordinate system is " +"pixel/line unless -l_srs, -wgs84 or -geoloc supplied." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:120 +msgid "" +"This utility is intended to provide a variety of information about a " +"pixel. Currently it reports:" +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:123 +msgid "The location of the pixel in pixel/line space." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:124 +msgid "" +"The result of a LocationInfo metadata query against the datasource. This " +"is implemented for VRT files which will report the file(s) used to " +"satisfy requests for that pixel, and by the :ref:`raster.mbtiles` driver." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:128 +msgid "The raster pixel value of that pixel for all or a subset of the bands." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:129 +msgid "The unscaled pixel value if a Scale and/or Offset apply to the band." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:131 +msgid "" +"The pixel selected is requested by x/y coordinate on the command line, or" +" read from stdin. More than one coordinate pair can be supplied when " +"reading coordinates from stdin. By default integer pixel/line coordinates" +" are expected. However with use of the :option:`-geoloc`, " +":option:`-wgs84`, or :option:`-l_srs` switches it is possible to specify " +"the location in other coordinate systems." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:137 +msgid "" +"The default report is in a human readable text format. It is possible to" +" instead request xml output with the -xml switch." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:140 +msgid "" +"For scripting purposes, the -valonly and -lifonly switches are provided " +"to restrict output to the actual pixel values, or the LocationInfo files " +"identified for the pixel." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:144 +msgid "" +"It is anticipated that additional reporting capabilities will be added to" +" gdallocationinfo in the future." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:150 +msgid "Simple example reporting on pixel (256,256) on the file utm.tif." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:160 +msgid "" +"Query a VRT file providing the location in WGS84, and getting the result " +"in xml." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:174 +msgid "Reading location from stdin." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:5 +msgid "gdalmanage" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:9 +msgid "Identify, delete, rename and copy raster data files." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:25 +msgid "" +"The :program:`gdalmanage` program can perform various operations on " +"raster data files, depending on the chosen *mode*. This includes " +"identifying raster data types and deleting, renaming or copying the " +"files." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:31 +msgid "Mode of operation" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:33 +msgid "**identify** *<datasetname>*:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:34 +msgid "List data format of file(s)." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:35 +msgid "**copy** *<datasetname>* *<newdatasetname>*:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:36 +msgid "Create a copy of the raster file with a new name." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:37 +msgid "**rename** *<datasetname>* *<newdatasetname>*:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:38 +msgid "Change the name of the raster file." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:39 +msgid "**delete** *<datasetname>*:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:40 +msgid "Delete raster file(s)." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:44 +msgid "Recursively scan files/folders for raster files." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:48 +msgid "" +"Recursively scan folders for raster files, forcing recursion in folders " +"recognized as valid formats." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:52 +msgid "Report failures if file type is unidentified." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:56 +msgid "" +"Specify format of raster file if unknown by the application. Uses short " +"data format name (e.g. *GTiff*)." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:61 +msgid "" +"Raster file to operate on. With **identify** may be repeated for multiple" +" files." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:65 +msgid "" +"For copy and rename modes, you provide a *source* filename and a *target*" +" filename, just like copy and move commands in an operating system." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:73 +msgid "Using identify mode" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:75 +msgid "" +"Report the data format of the raster file by using the *identify* mode " +"and specifying a data file name:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:84 +msgid "Recursive mode will scan subfolders and report the data format:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:101 +msgid "Using copy mode" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:103 +msgid "Copy the raster data:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:110 +msgid "Using rename mode" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:112 +msgid "Rename raster data:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:119 +msgid "Using delete mode" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:121 +msgid "Delete the raster data:" +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:5 +msgid "gdalmdiminfo" +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:11 +msgid "Reports structure and content of a multidimensional dataset." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:28 +msgid "" +":program:`gdalmdiminfo` program lists various information about a GDAL " +"supported multidimensional raster dataset as JSON output. It follows the " +"following `JSON schema " +"<https://github.com/OSGeo/gdal/blob/master/data/gdalmdiminfo_output.schema.json>`_" +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:40 +msgid "Most verbose output. Report attribute data types and array values." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:44 +msgid "Outputs on a single line without any indentation." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:48 +msgid "Name of the array used to restrict the output to the specified array." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:52 +msgid "" +"Number of values in each dimension that is used to limit the display of " +"array values. By default, unlimited. Only taken into account if used with" +" -detailed." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:58 +msgid "" +"Dataset open option (format specific). This option may be used several " +"times." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:63 +#: ../../source/programs/gdalmdimtranslate.rst:100 +msgid "" +"Option passed to :cpp:func:`GDALGroup::GetMDArrayNames` to filter " +"reported arrays. Such option is format specific. Consult driver " +"documentation. This option may be used several times." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:80 +msgid "This utility is also callable from C with :cpp:func:`GDALMultiDimInfo`." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:85 +msgid "Display general structure1" +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:194 +msgid "Display detailed information about a given array" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:5 +msgid "gdalmdimtranslate" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:11 +msgid "" +"Converts multidimensional data between different formats, and perform " +"subsetting." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:36 +msgid "" +":program:`gdalmdimtranslate` program converts multidimensional raster " +"between different formats, and/or can perform selective conversion of " +"specific arrays and groups, and/or subsetting operations." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:40 +msgid "The following command line parameters can appear in any order." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:50 +msgid "" +"Select the output format. This can be a format that supports " +"multidimensional output (such as :ref:`raster.netcdf`, " +":ref:`vrt_multidimensional`), or a \"classic\" 2D formats, if only one " +"single 2D array results of the other specified conversion operations. " +"When this option is not specified, the format is guessed when possible " +"from the extension of the destination filename." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:58 +msgid "" +"Many formats have one or more optional creation options that can be used " +"to control particulars about the file created." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:70 +msgid "" +"Array-level creation options may be passed by prefixing them with " +"``ARRAY:``. See :cpp:func:`GDALGroup::CopyFrom` for further details " +"regarding such options." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:75 +msgid "" +"Instead of converting the whole dataset, select one array, and possibly " +"perform operations on it. This option can be specified several times to " +"operate on different arrays." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:79 +msgid "" +"<array_spec> may be just an array name, potentially using a fully " +"qualified syntax (/group/subgroup/array_name). Or it can be a combination" +" of options with the syntax: " +"name={src_array_name}[,dstname={dst_array_name}][,resample=yes][,transpose=[{axis1},{axis2},...][,view={view_expr}]" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:84 +msgid "The following options are processed in that order:" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:86 +msgid "" +"``resample=yes`` asks for the array to run through " +":cpp:func:`GDALMDArray::GetResampled`." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:89 +msgid "" +"[{axis1},{axis2},...] is the argument of " +":cpp:func:`GDALMDArray::Transpose`." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:89 +msgid "For example, transpose=[1,0] switches the axis order of a 2D array." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:91 +msgid "" +"{view_expr} is the value of the *viewExpr* argument of " +":cpp:func:`GDALMDArray::GetView`" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:93 +msgid "" +"When specifying a view_expr that performs a slicing or subsetting on a " +"dimension, the equivalent operation will be applied to the corresponding " +"indexing variable." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:106 +msgid "" +"Instead of converting the whole dataset, select one group, and possibly " +"perform operations on it. This option can be specified several times to " +"operate on different groups. If only one group is specified, its content " +"will be copied directly to the target root group. If several ones are " +"specified, they are copied under the target root group" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:112 +msgid "" +"<group_spec> may be just a group name, potentially using a fully " +"qualified syntax (/group/subgroup/subsubgroup_name). Or it can be a " +"combination of options with the syntax: " +"name={src_group_name}[,dstname={dst_group_name}][,recursive=no]" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:119 +msgid "" +"Performs a subsetting (trimming or slicing) operation along a dimension, " +"provided that it is indexed by a 1D variable of numeric or string data " +"type, and whose values are monotically sorted. <subset_spec> follows " +"exactly the `OGC WCS 2.0 KVP encoding " +"<https://portal.opengeospatial.org/files/09-147r3>`__ for subsetting." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:125 +msgid "" +"That is dim_name(min_val,max_val) or dim_name(sliced_val) The first " +"syntax will subset the dimension dim_name to values in the " +"[min_val,max_val] range. The second syntax will slice the dimension " +"dim_name to value sliced_val (and this dimension will be removed from the" +" arrays that reference to it)" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:131 +msgid "Using -subset is incompatible of specifying a *view* option in -array." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:135 +msgid "" +"Applies a integral scale factor to one or several dimensions, that is " +"extract 1 value every N values (without resampling)." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:138 +msgid "" +"<scaleaxes_spec> follows exactly the syntax of the KVP encoding of the " +"SCALEAXES parameter of `OGC WCS 2.0 Scaling Extension " +"<https://portal.opengeospatial.org/files/12-039>`__, but limited to " +"integer scale factors." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:143 +msgid "That is <dim1_name>(<scale_factor>)[,<dim2_name>(<scale_factor>)]..." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:145 +msgid "Using -scaleaxes is incompatible of specifying a *view* option in -array." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:149 +msgid "" +"By default, some failures during the translation are tolerated, such as " +"not being able to write group attributes. When setting this option, such " +"failures will cause the process to fail." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:161 +msgid "The source dataset name." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:170 +msgid "" +"This utility is also callable from C with " +":cpp:func:`GDALMultiDimTranslate`." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:175 +msgid "Convert a netCDF file to a multidimensional VRT file" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:181 +msgid "Extract a 2D slice of a time,Y,X array" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:187 +msgid "Subsample along X and Y axis" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:193 +msgid "" +"Reorder the values of a time,Y,X array along the Y axis from top-to-" +"bottom to bottom-to-top (or the reverse)" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:200 +msgid "Transpose an array that has X,Y,time dimension order to time,Y,X" +msgstr "" + +#: ../../source/programs/gdalmove.rst:5 +msgid "gdalmove" +msgstr "" + +#: ../../source/programs/gdalmove.rst:9 +msgid "Transform georeferencing of raster file in place." +msgstr "" + +#: ../../source/programs/gdalmove.rst:25 +msgid "" +"The :program:`gdalmove` script transforms the bounds of a raster file " +"from one coordinate system to another, and then updates the coordinate " +"system and geotransform of the file. This is done without altering pixel " +"values at all. It is loosely similar to using gdalwarp to transform an " +"image but avoiding the resampling step in order to avoid image damage. It" +" is generally only suitable for transformations that are effectively " +"linear in the area of the file." +msgstr "" + +#: ../../source/programs/gdalmove.rst:32 +msgid "" +"If no error threshold value (:option:`-et`) is provided then the file is " +"not actually updated, but the errors that would be incurred are reported." +" If :option:`-et` is provided then the file is only modify if the " +"apparent error being introduced is less than the indicate threshold (in " +"pixels)." +msgstr "" + +#: ../../source/programs/gdalmove.rst:37 +msgid "" +"Currently the transformed geotransform is computed based on the " +"transformation of the top left, top right, and bottom left corners. A " +"reduced overall error could be produced using a least squares fit of at " +"least all four corner points." +msgstr "" + +#: ../../source/programs/gdalmove.rst:43 +msgid "" +"gdalmove is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdalmove.rst:49 +msgid "" +"Override the coordinate system of the file with the indicated coordinate " +"system definition. Optional. If not provided the source coordinate system" +" is read from the source file." +msgstr "" + +#: ../../source/programs/gdalmove.rst:55 +msgid "" +"Defines the target coordinate system. This coordinate system will be " +"written to the file after an update." +msgstr "" + +#: ../../source/programs/gdalmove.rst:60 +msgid "" +"The error threshold (in pixels) beyond which the file will not be " +"updated. If not provided no update will be applied to the file, but " +"errors will be reported." +msgstr "" + +#: ../../source/programs/gdalmove.rst:64 +msgid "<target_file>" +msgstr "" + +#: ../../source/programs/gdalmove.rst:66 +msgid "" +"The file to be operated on. To update this must be a file format that " +"supports in place updates of the geotransform and SRS." +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:5 +msgid "gdalsrsinfo" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:9 +msgid "Lists info about a given SRS in number of formats (WKT, PROJ.4, etc.)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:24 +msgid "" +"The :program:`gdalsrsinfo` utility reports information about a given SRS " +"from one of the following:" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:26 +msgid "" +"The filename of a dataset supported by GDAL/OGR which contains SRS " +"information" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:27 +msgid "" +"Any of the usual GDAL/OGR forms (complete WKT, PROJ.4, EPSG:n or a file " +"containing the SRS)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:36 +msgid "Print WKT on single line" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:40 +msgid "Validate SRS" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:44 +msgid "Search for EPSG number(s) corresponding to SRS" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:48 +msgid "Output types:" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:50 +msgid "``default``: proj4 and wkt (default option)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:51 +msgid "``all``: all options available" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:52 +msgid "``wkt_all``: all wkt options available" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:53 +msgid "``PROJJSON``: PROJJSON string (GDAL >= 3.1 and PROJ >= 6.2)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:54 +msgid "``proj4``: PROJ.4 string" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:55 +msgid "``wkt1``: OGC WKT format (full)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:56 +msgid "``wkt_simple``: OGC WKT 1 (simplified)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:57 +msgid "``wkt_noct``: OGC WKT 1 (without OGC CT params)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:58 +msgid "``wkt_esri``: ESRI WKT format" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:59 +msgid "``wkt``: Latest WKT version supported, currently wkt2_2019" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:60 +msgid "``wkt2``: Latest WKT2 version supported, currently wkt2_2019" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:61 +msgid "``wkt2_2015``: OGC WKT2:2015" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:62 +msgid "``wkt2_2019``: OGC WKT2:2019 (for GDAL < 3.6, use ``wkt2_2018``)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:63 +msgid "``mapinfo``: Mapinfo style CoordSys format" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:64 +msgid "``xml``: XML format (GML based)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:68 +msgid "" +"may be the filename of a dataset supported by GDAL/OGR from which to " +"extract SRS information OR any of the usual GDAL/OGR forms (complete WKT," +" PROJ.4, EPSG:n or a file containing the SRS)" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:5 +msgid "gdaltindex" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:9 +msgid "Creates an OGR-supported dataset as a raster tileindex." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:36 +msgid "" +"This program creates an OGR-supported dataset with a record for each " +"input raster file, an attribute containing the filename, and a polygon " +"geometry outlining the raster. This output is suitable for use with " +"`MapServer <http://mapserver.org/>`__ as a raster tileindex, or as input " +"for the :ref:`GTI <raster.gti>` driver." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:49 +msgid "Overwrite the tile index if it already exists." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:55 +msgid "" +"Whether directories specified in <file_or_dir> should be explored " +"recursively." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:61 +msgid "" +"Pattern that the filenames contained in directories pointed by " +"<file_or_dir> should follow. '*' is a wildcard character that matches any" +" number of any characters including none. '?' is a wildcard character " +"that matches a single character. Comparisons are done in a case " +"insensitive way. Several filters may be specified." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:68 +msgid "For example :``-filename_filter \"*.tif\" -filename_filter \"*.tiff\"``" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:74 +msgid "" +"Minimum pixel size in term of geospatial extent per pixel (resolution) " +"that a raster should have to be selected. The pixel size is evaluated " +"after reprojection of its extent to the target SRS defined by " +":option:`-t_srs`." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:83 +msgid "" +"Maximum pixel size in term of geospatial extent per pixel (resolution) " +"that a raster should have to be selected. The pixel size is evaluated " +"after reprojection of its extent to the target SRS defined by " +":option:`-t_srs`." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:90 +msgid "" +"The OGR format of the output tile index file. Starting with GDAL 2.3, if " +"not specified, the format is guessed from the extension (previously was " +"ESRI Shapefile)." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:96 +msgid "" +"The output field name to hold the file path/location to the indexed " +"rasters. The default tile index field name is ``location``." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:101 +msgid "" +"The absolute path to the raster files is stored in the tile index file. " +"By default the raster filenames will be put in the file exactly as they " +"are specified on the command line." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:107 +msgid "" +"Only files with same projection as files already inserted in the " +"tileindex will be inserted (unless :option:`-t_srs` is specified). " +"Default does not check projection and accepts all inputs." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:113 +msgid "" +"Geometries of input files will be transformed to the desired target " +"coordinate reference system. Default creates simple rectangular polygons " +"in the same coordinate reference system as the input rasters." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:120 +msgid "" +"The name of the field to store the SRS of each tile. This field name can " +"be used as the value of the TILESRS keyword in MapServer" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:125 +msgid "" +"The format in which the SRS of each tile must be written. Types can be " +"``AUTO``, ``WKT``, ``EPSG``, ``PROJ``. This option should be used " +"together with :option:`-src_srs_format`." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:131 +msgid "Layer name to create/append to in the output tile index file." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:141 +msgid "" +"The name of the output file to create/append to. The default dataset will" +" be created if it doesn't already exist, otherwise it will append to the " +"existing dataset." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:147 +msgid "" +"The input GDAL raster files, can be multiple files separated by spaces. " +"Wildcards may also be used. Stores the file locations in the same style " +"as specified here, unless :option:`-write_absolute_path` option is also " +"used." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:151 +msgid "" +"Starting with GDAL 3.9, this can also be a directory name. " +":option:`-recursive` can also be used to recurse down to sub-directories." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:154 +msgid "" +"It is also possible to use the generic option ``--optfile filelist.txt`` " +"to specify a list of source files." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:159 +msgid "Options specific to use by the GDAL GTI driver" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:161 +msgid "" +"gdaltindex can be used to generate a tile index suitable for use by the " +":ref:`GTI <raster.gti>` driver. There are two possibilities:" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:164 +msgid "" +"either use directly a vector tile index generated by gdaltindex as the " +"input of the GTI driver" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:167 +msgid "" +"or generate a small XML .gti wrapper file, for easier use with non-file-" +"based formats such as databases, or for vector formats that do not " +"support setting layer metadata items." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:171 +msgid "" +"Formats that support layer metadata are for example GeoPackage (``-f " +"GPKG``), FlatGeoBuf (``-f FlatGeoBuf``) or PostGIS (``-f PG``)" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:174 +msgid "" +"Setting :option:`-tr` and :option:`-ot` is recommended to avoid the GTI " +"driver to have to deduce them by opening the first tile in the index. If " +"the tiles have nodata or mask band, :option:`-nodata` and " +":option:`-mask` should also be set." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:179 +msgid "" +"In a GTI context, the extent of all tiles referenced in the tile index " +"must be expressed in a single SRS. Consequently, if input tiles may have " +"different SRS, either :option:`-t_srs` or " +":option:`-skip_different_projection` should be specified." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:189 +msgid "" +"Filename of the XML Virtual Tile Index file to generate, that can be used" +" as an input for the GDAL GTI / Virtual Raster Tile Index driver. This " +"can be useful when writing the tile index in a vector format that does " +"not support writing layer metadata items." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:198 +msgid "Target resolution in SRS unit per pixel." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:200 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``RESX`` and ``RESY`` layer metadata items for formats " +"that support layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:208 +msgid "Target extent in SRS unit." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:210 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``MINX``, ``MINY``, ``MAXX`` and ``MAXY`` layer metadata" +" items for formats that support layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:218 +msgid "" +"Data type of the tiles of the tile index: ``Byte``, ``Int8``, ``UInt16``," +" ``Int16``, ``UInt32``, ``Int32``, ``UInt64``, ``Int64``, ``Float32``, " +"``Float64``, ``CInt16``, ``CInt32``, ``CFloat32`` or ``CFloat64``" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:222 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``DATA_TYPE`` layer metadata item for formats that " +"support layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:230 +msgid "Number of bands of the tiles of the tile index." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:232 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``BAND_COUNT`` layer metadata item for formats that " +"support layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:236 +msgid "" +"A mix of tiles with N and N+1 bands is allowed, provided that the color " +"interpretation of the (N+1)th band is alpha. The N+1 value must be " +"written as the band count in that situation." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:240 +msgid "" +"If :option:`-nodata` or :option:`-colorinterp` are specified and have " +"multiple values, the band count is also inferred from that number." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:247 +msgid "Nodata value of the tiles of the tile index." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:249 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``NODATA`` layer metadata item for formats that support " +"layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:257 +msgid "" +"Color interpretation of of the tiles of the tile index: ``red``, " +"``green``, ``blue``, ``alpha``, ``gray``, ``undefined``." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:260 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``COLOR_INTERPRETATION`` layer metadata item for formats" +" that support layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:268 +msgid "Whether tiles in the tile index have a mask band." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:270 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``MASK_BAND`` layer metadata item for formats that " +"support layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:278 +msgid "" +"Write an arbitrary layer metadata item, for formats that support layer " +"metadata. This option may be repeated." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:282 +msgid "This option cannot be used together :option:`-gti_filename`" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:288 +msgid "" +"Fetch a metadata item from the raster tile and write it as a field in the" +" tile index." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:291 +msgid "" +"<gdal_md_name> should be the name of the raster metadata item. " +"``{PIXEL_SIZE}`` may be used as a special name to indicate the pixel " +"size." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:294 +msgid "<fld_name> should be the name of the field to create in the tile index." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:296 +msgid "" +"<fld_type> should be the name of the type to create. One of ``String``, " +"``Integer``, ``Integer64``, ``Real``, ``Date``, ``DateTime``" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:299 +msgid "This option may be repeated." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:301 +msgid "For example: ``-fetch_md TIFFTAG_DATETIME creation_date DateTime``" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:306 +msgid "" +"Produce a shapefile (``doq_index.shp``) with a record for every image " +"that the utility found in the ``doq`` folder. Each record holds " +"information that points to the location of the image and also a bounding " +"rectangle shape showing the bounds of the image:" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:315 +msgid "" +"Perform the same command as before, but now we create a GeoPackage " +"instead of a Shapefile." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:321 +msgid "" +"The :option:`-t_srs` option can also be used to transform all input " +"rasters into the same output projection:" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:328 +msgid "" +"Make a tile index from files listed in a text file, with metadata " +"suitable for use by the GDAL GTI / Virtual Raster Tile Index driver." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:338 +msgid "This utility is also callable from C with :cpp:func:`GDALTileIndex`." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:343 +msgid "" +":ref:`raster_common_options` for other command-line options, and in " +"particular the :ref:`--optfile <raster_common_options_optfile>` switch " +"that can be used to specify a list of input datasets." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:5 +msgid "gdaltransform" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:9 +msgid "Transforms coordinates" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:30 +msgid "" +"The gdaltransform utility reprojects a list of coordinates into any " +"supported projection,including GCP-based transformations." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:39 +msgid "" +"Set source spatial reference. The coordinate systems that can be passed " +"are anything supported by the OGRSpatialReference.SetFromUserInput() " +"call, which includes EPSG PCS and GCSes (i.e. EPSG:4296), PROJ.4 " +"declarations (as above), or the name of a .prj file containing well known" +" text." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:49 +#: ../../source/programs/gdalwarp.rst:129 ../../source/programs/ogr2ogr.rst:331 +msgid "" +"Assign a coordinate epoch, linked with the source SRS. Useful when the " +"source SRS is a dynamic CRS. Only taken into account if :option:`-s_srs` " +"is used." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:53 +#: ../../source/programs/gdaltransform.rst:72 +#: ../../source/programs/gdalwarp.rst:133 +#: ../../source/programs/gdalwarp.rst:154 ../../source/programs/ogr2ogr.rst:273 +#: ../../source/programs/ogr2ogr.rst:335 +msgid "" +"Before PROJ 9.4, :option:`-s_coord_epoch` and :option:`-t_coord_epoch` " +"were mutually exclusive, due to lack of support for transformations " +"between two dynamic CRS." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:58 +msgid "" +"set target spatial reference. The coordinate systems that can be passed " +"are anything supported by the OGRSpatialReference.SetFromUserInput() " +"call, which includes EPSG PCS and GCSes (i.e. EPSG:4296), PROJ.4 " +"declarations (as above), or the name of a .prj file containing well known" +" text." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:68 +msgid "" +"Assign a coordinate epoch, linked with the output SRS. Useful when the " +"output SRS is a dynamic CRS. Only taken into account if :option:`-t_srs` " +"is used." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:77 +msgid "" +"A PROJ string (single step operation or multiple step string starting " +"with +proj=pipeline), a WKT2 string describing a CoordinateOperation, or " +"a urn:ogc:def:coordinateOperation:EPSG::XXXX URN overriding the default " +"transformation from the source to the target CRS. It must take into " +"account the axis order of the source and target CRS." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:87 +msgid "" +"set a transformer option suitable to pass to " +":cpp:func:`GDALCreateGenImgProjTransformer2`." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:91 +#: ../../source/programs/gdalwarp.rst:200 +msgid "" +"order of polynomial used for warping (1 to 3). The default is to select a" +" polynomial order based on the number of GCPs." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:96 +#: ../../source/programs/gdalwarp.rst:205 ../../source/programs/ogr2ogr.rst:558 +msgid "Force use of thin plate spline transformer based on available GCPs." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:100 +#: ../../source/programs/gdalwarp.rst:209 +msgid "Force use of RPCs." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:104 +#: ../../source/programs/gdalwarp.rst:213 +msgid "Force use of Geolocation Arrays." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:108 +msgid "Inverse transformation: from destination to source." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:112 +msgid "" +"Provide a GCP to be used for transformation (generally three or more are " +"required). Pixel and line need not be integers." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:116 +msgid "Restrict output to \"x y\" instead of \"x y z\"" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:122 +msgid "" +"Set this flag to avoid extra non-numeric content at end of input lines to" +" be appended to the output lines." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:129 +msgid "" +"Enable Echo mode, where input coordinates are prepended to the output " +"lines." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:135 +msgid "" +"Defines the field separator, to separate different values. It defaults to" +" the space character." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:140 +msgid "" +"Raster dataset with source projection definition or GCPs. If not given, " +"source projection/GCPs are read from the command-line :option:`-s_srs` or" +" :option:`-gcp` parameters." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:144 +msgid "" +"Note that only the SRS and/or GCPs of this input file is taken into " +"account, and not its pixel content." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:148 +msgid "Raster dataset with destination projection definition." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:150 +msgid "" +"Coordinates are read as pairs, triples (for 3D,) or (since GDAL 3.0.0,) " +"quadruplets (for X,Y,Z,time) of numbers per line from standard input, " +"transformed, and written out to standard output in the same way. All " +"transformations offered by gdalwarp are handled, including gcp-based " +"ones." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:155 +msgid "" +"Starting with GDAL 3.9, additional non-numeric content (typically point " +"name) at the end of an input line will also be appended to the output " +"line, unless the :option:`-ignore_extra_input` is added." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:159 +msgid "" +"Note that input and output must always be in decimal form. There is " +"currently no support for DMS input or output." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:162 +msgid "" +"If an input image file is provided, input is in pixel/line coordinates on" +" that image. If an output file is provided, output is in pixel/line " +"coordinates on that image." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:170 +msgid "Reprojection Example" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:172 +msgid "Simple reprojection from one projected coordinate system to another:" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:179 +msgid "" +"Produces the following output in meters in the \"Belge 1972 / Belgian " +"Lambert 72\" projection:" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:187 +msgid "Image RPC Example" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:189 +msgid "" +"The following command requests an RPC based transformation using the RPC " +"model associated with the named file. Because the -i (inverse) flag is " +"used, the transformation is from output georeferenced (WGS84) coordinates" +" back to image coordinates." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:200 +msgid "Produces this output measured in pixels and lines on the image:" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:207 +msgid "X,Y,Z,time transform" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:209 +msgid "" +"15-term time-dependent Helmert coordinate transformation from ITRF2000 to" +" ITRF93 for a coordinate at epoch 2000.0" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:222 +msgid "" +"Produces this output measured in longitude degrees, latitude degrees and " +"ellipsoid height in meters:" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:229 +msgid "Ground control points" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:231 +msgid "" +"Task: find one address and assign another. We pick Salt Lake City, where " +"road names *are* their grid values. We first establish some ground " +"control points at road intersections. We'll use :ref:`--optfile " +"<raster_common_options_optfile>` for easy reuse of our GCPs." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:243 +msgid "Where is the address \"370 S. 300 E.\"?" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:250 +msgid "" +"Nearby, a newly constructed building needs an address assigned. We use " +":option:`-i`:" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:257 +msgid "(i.e., 143 E. 200 S. Or 144 if across the street.)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:5 +msgid "gdalwarp" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:9 +msgid "Image reprojection and warping utility" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:53 +msgid "" +"The :program:`gdalwarp` utility is an image mosaicing, reprojection and " +"warping utility. The program can reproject to any supported projection, " +"and can also apply GCPs stored with the image if the image is \"raw\" " +"with control information." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:68 +msgid "" +"Specify an input band number to warp (between 1 and the number of bands " +"of the source dataset)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:71 +msgid "" +"This option is used to warp a subset of the input bands. All input bands " +"are used when it is not specified." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:74 +msgid "" +"This option may be repeated multiple times to select several input bands." +" The order in which bands are specified will be the order in which they " +"appear in the output dataset (unless :option:`-dstband` is specified)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:78 +msgid "" +"The alpha band should not be specified in the list, as it will be " +"automatically retrieved (unless :option:`-nosrcalpha` is specified)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:81 +msgid "" +"The following invocation will warp an input datasets with bands ordered " +"as Blue, Green, Red, NearInfraRed in an output dataset with bands ordered" +" as Red, Green, Blue." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:94 +msgid "" +"Specify the output band number in which to warp. In practice, this option" +" is only useful when updating an existing dataset, e.g to warp one band " +"at at time." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:106 +msgid "" +"If :option:`-srcband` is specified, there must be as many occurrences of " +":option:`-dstband` as there are of :option:`-srcband`." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:109 +msgid "" +"The output alpha band should not be specified, as it will be " +"automatically created if the input dataset has an alpha band, or if " +":option:`-dstalpha` is specified." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:113 +msgid "" +"If :option:`-dstband` is not specified, then ``-dstband 1 -dstband 2 ... " +"-dstband N`` is assumed where N is the number of input bands (specified " +"explicitly either with :option:`-srcband` or implicitly)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:120 +msgid "" +"Set source spatial reference. If not specified the SRS found in the input" +" dataset will be used." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:150 +#: ../../source/programs/options/srs_def_gdalwarp.rst:1 +msgid "" +"The coordinate reference systems that can be passed are anything " +"supported by the OGRSpatialReference.SetFromUserInput() call, which " +"includes EPSG Projected, Geographic or Compound CRS (i.e. EPSG:4296), a " +"well known text (WKT) CRS definition, PROJ.4 declarations, or the name of" +" a .prj file containing a WKT CRS definition." +msgstr "" + +#: ../../source/programs/options/srs_def_gdalwarp.rst:6 +msgid "" +"Starting with GDAL 2.2, if the SRS has an explicit vertical datum that " +"points to a PROJ.4 geoidgrids, and the input dataset is a single band " +"dataset, a vertical correction will be applied to the values of the " +"dataset." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:138 +msgid "Set target spatial reference." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:140 +msgid "" +"A source SRS must be available for reprojection to occur. The source SRS " +"will be by default the one found in the input dataset when it is " +"available, or as overridden by the user with :option:`-s_srs`" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:150 +msgid "" +"Assign a coordinate epoch, linked with the target SRS. Useful when the " +"target SRS is a dynamic CRS. Only taken into account if :option:`-t_srs` " +"is used." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:159 ../../source/programs/ogr2ogr.rst:340 +msgid "" +"A PROJ string (single step operation or multiple step string starting " +"with +proj=pipeline), a WKT2 string describing a CoordinateOperation, or " +"a urn:ogc:def:coordinateOperation:EPSG::XXXX URN overriding the default " +"transformation from the source to the target CRS." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:164 ../../source/programs/ogr2ogr.rst:345 +msgid "" +"It must take into account the axis order of the source and target CRS, " +"that is typically include a ``step proj=axisswap order=2,1`` at the " +"beginning of the pipeline if the source CRS has northing/easting axis " +"order, and/or at the end of the pipeline if the target CRS has " +"northing/easting axis order." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:169 +msgid "" +"When creating a new output file, using :option:`-t_srs` is still " +"necessary to have the target CRS written in the metadata of the output " +"file, but the parameters of the CoordinateOperation will override those " +"of the standard transformation." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:178 +msgid "" +"Set a transformer option suitable to pass to " +":cpp:func:`GDALCreateGenImgProjTransformer2`. See " +":cpp:func:`GDALCreateRPCTransformerV2()` for RPC specific options." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:183 +msgid "" +"Force the use of vertical shift. This option is generally not necessary, " +"except when using an explicit coordinate transformation (:option:`-ct`), " +"and not specifying an explicit source and target SRS." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:191 +msgid "" +"Disable the use of vertical shift when one of the source or target SRS " +"has an explicit vertical datum, and the input dataset is a single band " +"dataset." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:194 +msgid "this option was named ``-novshiftgrid`` in GDAL 2.2 to 3.3." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:217 +msgid "" +"Error threshold for transformation approximation (in pixel units - " +"defaults to 0.125, unless, starting with GDAL 2.1, the RPC_DEM " +"transformer option is specified, in which case, an exact transformer, " +"i.e. err_threshold=0, will be used)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:224 +msgid "" +"Refines the GCPs by automatically eliminating outliers. Outliers will be " +"eliminated until minimum_gcps are left or when no outliers can be " +"detected. The tolerance is passed to adjust when a GCP will be " +"eliminated. Not that GCP refinement only works with polynomial " +"interpolation. The tolerance is in pixel units if no projection is " +"available, otherwise it is in SRS units. If minimum_gcps is not provided," +" the minimum GCPs according to the polynomial model is used." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:233 +msgid "" +"Set georeferenced extents of output file to be created (in target SRS by " +"default, or in the SRS specified with :option:`-te_srs`)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:238 +msgid "" +"Specifies the SRS in which to interpret the coordinates given with -te. " +"The <srs_def> may be any of the usual GDAL/OGR forms, complete WKT, " +"PROJ.4, EPSG:n or a file containing the WKT. This must not be confused " +"with -t_srs which is the target SRS of the output dataset. " +":option:`-te_srs` is a convenience e.g. when knowing the output " +"coordinates in a geodetic long/lat SRS, but still wanting a result in a " +"projected coordinate system." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:248 +msgid "Set output file resolution (in target georeferenced units)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:250 +msgid "" +"If not specified (or not deduced from -te and -ts), gdalwarp will, in the" +" general case, generate an output raster with xres=yres." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:253 +msgid "" +"Starting with GDAL 3.7, if neither :option:`-tr` nor :option:`-ts` are " +"specified, that no reprojection is involved (including taking into " +"account geolocation arrays or RPC), the resolution of the source file(s) " +"will be preserved (in previous version, an output raster with xres=yres " +"was always generated). It is possible to ask square pixels to still be " +"generated, by specifying ``square`` as the value for :option:`-tr`." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:262 +msgid "" +"(target aligned pixels) align the coordinates of the extent of the output" +" file to the values of the :option:`-tr`, such that the aligned extent " +"includes the minimum extent (edges lines/columns that are detected as " +"blank, before actual warping, will be removed starting with GDAL 3.8). " +"Alignment means that xmin / resx, ymin / resy, xmax / resx and ymax / " +"resy are integer values." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:271 +msgid "" +"Set output file size in pixels and lines. If width or height is set to 0," +" the other dimension will be guessed from the computed resolution. Note " +"that :option:`-ts` cannot be used with :option:`-tr`" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:277 +msgid "" +"To specify which overview level of source files must be used. The default" +" choice, AUTO, will select the overview level whose resolution is the " +"closest to the target resolution. Specify an integer value (0-based, i.e." +" 0=1st overview level) to select a particular level. Specify AUTO-n where" +" n is an integer greater or equal to 1, to select an overview level below" +" the AUTO one. Or specify NONE to force the base resolution to be used " +"(can be useful if overviews have been generated with a low quality " +"resampling method, and the warping is done using a higher quality " +"resampling method)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:288 +msgid "" +"Set a warp option. The :cpp:member:`GDALWarpOptions::papszWarpOptions` " +"docs show all options. Multiple :option:`-wo` options may be listed." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:295 +msgid "" +"Working pixel data type. The data type of pixels in the source image and " +"destination image buffers." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:300 +msgid "Resampling method to use. Available methods are:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:302 +msgid "" +"``near``: nearest neighbour resampling (default, fastest algorithm, worst" +" interpolation quality)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:304 +msgid "``bilinear``: bilinear resampling." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:306 +msgid "``cubic``: cubic resampling." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:308 +msgid "``cubicspline``: cubic spline resampling." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:310 +msgid "``lanczos``: Lanczos windowed sinc resampling." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:312 +msgid "" +"``average``: average resampling, computes the weighted average of all " +"non-NODATA contributing pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:314 +msgid "" +"``rms`` root mean square / quadratic mean of all non-NODATA contributing " +"pixels (GDAL >= 3.3)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:316 +msgid "" +"``mode``: mode resampling, selects the value which appears most often of " +"all the sampled points. In the case of ties, the first value identified " +"as the mode will be selected." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:318 +msgid "" +"``max``: maximum resampling, selects the maximum value from all non-" +"NODATA contributing pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:320 +msgid "" +"``min``: minimum resampling, selects the minimum value from all non-" +"NODATA contributing pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:322 +msgid "" +"``med``: median resampling, selects the median value of all non-NODATA " +"contributing pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:324 +msgid "" +"``q1``: first quartile resampling, selects the first quartile value of " +"all non-NODATA contributing pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:326 +msgid "" +"``q3``: third quartile resampling, selects the third quartile value of " +"all non-NODATA contributing pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:328 +msgid "" +"``sum``: compute the weighted sum of all non-NODATA contributing pixels " +"(since GDAL 3.1)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:332 +msgid "" +"When downsampling is performed (use of :option:`-tr` or :option:`-ts`), " +"existing overviews (either internal/implicit or external ones) on the " +"source image will be used by default by selecting the closest overview to" +" the desired output resolution. The resampling method used to create " +"those overviews is generally not the one you specify through the " +":option:`-r` option. Some formats, like JPEG2000, can contain significant" +" outliers due to wavelet compression works. It might thus be useful in " +"those situations to use the :option:`-ovr` ``NONE`` option to prevent " +"existing overviews to be used." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:344 +msgid "" +"Set nodata masking values for input bands (different values can be " +"supplied for each band). If more than one value is supplied all values " +"should be quoted to keep them together as a single operating system " +"argument. Masked values will not be used in interpolation (details given " +"in :ref:`gdalwarp_nodata`)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:349 +msgid "" +"Use a value of ``None`` to ignore intrinsic nodata settings on the source" +" dataset." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:351 +msgid "" +"When this option is set to a non-``None`` value, it causes the " +"``UNIFIED_SRC_NODATA`` warping option (see " +":cpp:member:`GDALWarpOptions::papszWarpOptions`) to be set to ``YES``, if" +" it is not explicitly set." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:355 +msgid "" +"If ``-srcnodata`` is not explicitly set, but the source dataset has " +"nodata values, they will be taken into account, with " +"``UNIFIED_SRC_NODATA`` at ``PARTIAL`` by default." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:361 +msgid "" +"Set nodata values for output bands (different values can be supplied for " +"each band). If more than one value is supplied all values should be " +"quoted to keep them together as a single operating system argument. New " +"files will be initialized to this value and if possible the nodata value " +"will be recorded in the output file. Use a value of ``None`` to ensure " +"that nodata is not defined. If this argument is not used then nodata " +"values will be copied from the source dataset." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:371 +msgid "" +"Force the last band of a source image to be considered as a source alpha " +"band." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:376 +msgid "" +"Prevent the alpha band of a source image to be considered as such (it " +"will be warped as a regular band)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:383 +msgid "Create an output alpha band to identify nodata (unset/transparent) pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:387 +msgid "" +"Set the amount of memory that the warp API is allowed to use for caching." +" The value is interpreted as being in megabytes if the value is less than" +" 10000. For values >=10000, this is interpreted as bytes." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:392 +msgid "" +"The warper will total up the memory required to hold the input and output" +" image arrays and any auxiliary masking arrays and if they are larger " +"than the \"warp memory\" allowed it will subdivide the chunk into smaller" +" chunks and try again." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:397 +msgid "" +"If the -wm value is very small there is some extra overhead in doing many" +" small chunks so setting it larger is better but it is a matter of " +"diminishing returns." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:403 +msgid "" +"Use multithreaded warping implementation. Two threads will be used to " +"process chunks of image and perform input/output operation " +"simultaneously. Note that computation is not multithreaded itself. To do " +"that, you can use the :option:`-wo` NUM_THREADS=val/ALL_CPUS option, " +"which can be combined with :option:`-multi`" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:411 +msgid "Be quiet." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:421 +msgid "" +"Enable use of a blend cutline from the name of a vector dataset. Starting" +" with GDAL 3.9, a WKT geometry string starting with POLYGON or " +"MULTIPOLYGON can also be specified." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:429 +msgid "Sets or overrides the SRS of the cutline." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:433 +msgid "Select the named layer from the cutline datasource." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:437 +msgid "Restrict desired cutline features based on attribute query." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:441 +msgid "" +"Select cutline features using an SQL query instead of from a layer with " +":option:`-cl`." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:445 +msgid "Set a blend distance to use to blend over cutlines (in pixels)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:449 +msgid "Crop the extent of the target dataset to the extent of the cutline." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:453 +msgid "" +"Overwrite the target dataset if it already exists. Overwriting must be " +"understood here as deleting and recreating the file from scratch. Note " +"that if this option is *not* specified and the output file already " +"exists, it will be updated in place." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:460 +msgid "" +"Do not copy metadata. Without this option, dataset and band metadata (as " +"well as some band information) will be copied from the first source " +"dataset. Items that differ between source datasets will be set to * (see " +":option:`-cvmd` option)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:466 +msgid "" +"Value to set metadata items that conflict between source datasets " +"(default is \"*\"). Use \"\" to remove conflicting items." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:471 +msgid "" +"Set the color interpretation of the bands of the target dataset from the " +"source dataset." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:480 +msgid "Output dataset open option (format specific)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:486 +msgid "The source file name(s)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:493 +msgid "" +"Mosaicing into an existing output file is supported if the output file " +"already exists. The spatial extent of the existing file will not be " +"modified to accommodate new data, so you may have to remove it in that " +"case, or use the -overwrite option." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:498 +msgid "" +"Polygon cutlines may be used as a mask to restrict the area of the " +"destination file that may be updated, including blending. If the OGR " +"layer containing the cutline features has no explicit SRS, the cutline " +"features must be in the SRS of the destination file. When writing to a " +"not yet existing target dataset, its extent will be the one of the " +"original raster unless -te or -crop_to_cutline are specified." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:505 +msgid "" +"Starting with GDAL 3.1, it is possible to use as output format a driver " +"that only supports the CreateCopy operation. This may internally imply " +"creation of a temporary file." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:512 +msgid "Nodata / source validity mask handling" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:514 +msgid "" +"Invalid values in source pixels, either identified through a nodata value" +" metadata set on the source band, a mask band, an alpha band or the use " +"of :option:`-srcnodata` will not be used in interpolation. The details of" +" how it is taken into account depends on the resampling kernel:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:519 +msgid "" +"for nearest resampling, for each target pixel, the coordinate of its " +"center is projected back to source coordinates and the source pixel " +"containing that coordinate is identified. If this source pixel is " +"invalid, the target pixel is considered as nodata." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:524 +msgid "" +"for bilinear, cubic, cubicspline and lanczos, for each target pixel, the " +"coordinate of its center is projected back to source coordinates and a " +"corresponding source pixel is identified. If this source pixel is " +"invalid, the target pixel is considered as nodata. Given that those " +"resampling kernels have a non-null kernel radius, this source pixel is " +"just one among other several source pixels, and it might be possible that" +" there are invalid values in those other contributing source pixels. The " +"weights used to take into account those invalid values will be set to " +"zero to ignore them." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:534 +msgid "" +"for the other resampling methods, source pixels contributing to the " +"target pixel are ignored if invalid. Only the valid ones are taken into " +"account. If there are none, the target pixel is considered as nodata." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:538 +msgid "" +"If using :option:`-srcnodata` for multiple images with different invalid " +"values, you need to either (a) pre-process them to have the same to-be-" +"ignored value, or (b) set the nodata flag for each file. Use (b) if you " +"need to preserve the original values for some reason, for example:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:559 +msgid "Approximate transformation" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:561 +msgid "" +"By default :program:`gdalwarp` uses a linear approximator for the " +"transformations with a permitted error of 0.125 pixels. The approximator " +"basically transforms three points on a scanline: the start, end and " +"middle. Then it compares the linear approximation of the center based on " +"the end points to the real thing and checks the error. If the error is " +"less than the error threshold then the remaining points are approximated " +"(in two chunks utilizing the center point). If the error exceeds the " +"threshold, the scanline is split into two sections, and the approximator " +"is recursively applied to each section until the error is less than the " +"threshold or all points have been exactly computed." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:572 +msgid "" +"The error threshold (in pixels) can be controlled with the gdalwarp " +":option:`-et` switch. If you want to compare a true pixel-by-pixel " +"reprojection use :option:`-et 0` which disables this approximator " +"entirely." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:577 +msgid "Vertical transformation" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:579 +msgid "" +"While gdalwarp can essentially perform coordinate transformations in the " +"2D space, it can perform as well vertical transformations. This is " +"automatically enabled when the 2 following conditions are met:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:583 +msgid "" +"at least one of the source or target CRS has an explicit vertical CRS (as" +" part of a compound CRS) or is a 3D (generally geographic) CRS," +msgstr "" + +#: ../../source/programs/gdalwarp.rst:585 +msgid "and the raster has a single band." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:587 +msgid "" +"This mode can also be forced by using the :option:`-vshift` (this is " +"essentially useful when the CRS involved are not explicitly 3D, but a " +"transformation pipeline is specified with :option:`-ct`), or disabled " +"with :option:`-novshift`." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:592 +msgid "" +"When a vertical transformation is involved, typically a shift value read " +"in a geoid grid will be applied. This may require such grid(s) to be " +"installed, or PROJ networking capabilities to be enabled. Consult `PROJ " +"<https://proj.org>`__ documentation for more details. In addition to a " +"shift, the raster values may be multiplied by a factor to take into " +"account vertical unit changes. In priority, the value returned by " +":cpp:func:`GDALRasterBand::GetUnitType` is used. The following values are" +" currently recognized: ``m``, ``metre``, ``metre``, ``ft``, ``foot``, " +"``US survey foot``. If there is no defined unit type at the band level, " +"the vertical unit of the source CRS is used. The vertical unit of the " +"target CRS is also used to determine that conversion factor. The " +"conversion factor may be overridden by setting the " +"``MULT_FACTOR_VERTICAL_SHIFT`` warping option with :option:`-wo`. For " +"example ``-wo MULT_FACTOR_VERTICAL_SHIFT=1`` to disable any vertical unit" +" change." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:607 +msgid "Memory usage" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:609 +msgid "" +"Adding RAM will almost certainly increase the speed of " +":program:`gdalwarp`. That's not at all the same as saying that it is " +"worth it, or that the speed increase will be significant. Disks are the " +"slowest part of the process. By default :program:`gdalwarp` won't take " +"much advantage of RAM. Using the flag :option:`-wm 500` will operate on " +"500MB chunks at a time which is better than the default. The warp memory " +"specified by :option:`-wm` is shared among all threads, so it is " +"especially beneficial to increase this value when running " +":program:`gdalwarp` with :option:`-wo NUM_THREADS` (or its equivalent " +":config:`GDAL_NUM_THREADS`) greater than 1." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:619 +msgid "" +"Increasing the I/O block cache size may also help. This can be done by " +"setting the :config:`GDAL_CACHEMAX` configuration like:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:626 +msgid "" +"This uses 500MB of RAM for read/write caching, and 500MB of RAM for " +"working buffers during the warp. Beyond that it is doubtful more memory " +"will make a substantial difference." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:630 +msgid "" +"Check CPU usage while :program:`gdalwarp` is running. If it is " +"substantially less than 100% then you know things are IO bound. Otherwise" +" they are CPU bound. The ``--debug`` option may also provide useful " +"information. For instance, after running the following:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:639 +msgid "a message like the following will be output:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:645 +msgid "" +"In this case it is saying that band 1 of :file:`utm.tif` has 32 blocks, " +"but that 224 block reads were done, implying that lots of data was having" +" to be re-read, presumably because of a limited IO cache. You will also " +"see messages like:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:655 +msgid "" +"The Src/Dst windows show you the \"chunk size\" being used. In this case " +"my whole image which is very small. If you find things are being broken " +"into a lot of chunks increasing :option:`-wm` may help somewhat." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:659 +msgid "" +"But far more important than memory are ensuring you are going through an " +"optimized path in the warper. If you ever see it reporting " +"``GDALWarpKernel()::GWKGeneralCase()`` you know things will be relatively" +" slow. Basically, the fastest situations are nearest neighbour resampling" +" on 8bit data without nodata or alpha masking in effect." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:667 +msgid "Compressed output" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:669 +msgid "" +"In some cases, the output of :program:`gdalwarp` may be much larger than " +"the original, even if the same compression algorithm is used. By default," +" :program:`gdalwarp` operates on chunks that are not necessarily aligned " +"with the boundaries of the blocks/tiles/strips of the output format, so " +"this might cause repeated compression/decompression of partial blocks, " +"leading to lost space in the output format." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:676 +msgid "" +"The situation can be improved by using the ``OPTIMIZE_SIZE`` warping " +"option (:option:`-wo OPTIMIZE_SIZE=YES`), but note that depending on the " +"source and target projections, it might also significantly slow down the " +"warping process." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:680 +msgid "" +"Another possibility is to use :program:`gdalwarp` without compression and" +" then follow up with :program:`gdal_translate` with compression:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:688 +msgid "" +"Alternatively, you can use a VRT file as the output format of " +":program:`gdalwarp`. The VRT file is just an XML file that will be " +"created immediately. The :program:`gdal_translate` operations will be of " +"course a bit slower as it will do the real warping operation." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:702 +msgid "Basic transformation:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:709 +msgid "" +"For instance, an eight bit spot scene stored in GeoTIFF with control " +"points mapping the corners to lat/long could be warped to a UTM " +"projection with a command like this:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:717 +msgid "" +"For instance, the second channel of an ASTER image stored in HDF with " +"control points mapping the corners to lat/long could be warped to a UTM " +"projection with a command like this:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:728 +msgid "" +"To apply a cutline on a un-georeferenced image and clip from pixel " +"(220,60) to pixel (1160,690):" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:735 +msgid "where cutline.csv content is like:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:742 +msgid "" +"To transform a DEM from geoid elevations (using EGM96) to WGS84 " +"ellipsoidal heights:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:754 +msgid "This utility is also callable from C with :cpp:func:`GDALWarp`." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:762 +msgid "" +"`Wiki page discussing options and behaviours of gdalwarp " +"<https://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp>`_" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:766 +msgid "" +"Wiki page discussing options and behaviours of gdalwarp: " +"https://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp" +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:5 +msgid "gnmanalyse" +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:9 +msgid "Analyses networks" +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:29 +msgid "" +"The :program:`gnmanalyse` program provides analysing capabilities of " +"geographical networks in GDAL. The results of calculations are return in " +"an OGRLayer format or as a console text output if such layer is " +"undefined. All calculations are made considering the blocking state of " +"features." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:37 +msgid "" +"Calculates the best path between two points using Dijkstra algorithm from" +" start_gfid point to end_gfid point." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:41 +msgid "" +"Calculates K shortest paths between two points using Yen's algorithm " +"(which internally uses Dijkstra algorithm for single path calculating) " +"from start_gfid point to end_gfid point." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:45 +msgid "" +"Calculates the \"resource distribution\". The connected components search" +" is performed using breadth-first search and starting from that features " +"which are marked by rules as 'EMITTERS'." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:49 +msgid "" +"The name and path of the dataset to save the layer with resulting paths. " +"Not need to be existed dataset." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:53 +msgid "Define this to set the format of newly created dataset." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:57 +msgid "" +"The name of the resulting layer. If the layer exist already - it will be " +"rewritten." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:61 +#: ../../source/programs/gnmmanage.rst:119 +msgid "The network to work with (path and name)." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:73 +msgid "Algorithm option (format specific)" +msgstr "" + +#: ../../source/programs/gnmmanage.rst:5 +msgid "gnmmanage" +msgstr "" + +#: ../../source/programs/gnmmanage.rst:9 +msgid "Manages networks" +msgstr "" + +#: ../../source/programs/gnmmanage.rst:33 +msgid "" +"The :program:`gnmmanage` program can perform various managing operations " +"on geographical networks in GDAL. In addition to creating and deleting " +"networks this includes capabilities of managing network's features, " +"topology and rules." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:41 +msgid "" +"Different information about network: system and class layers, network " +"metadata, network spatial reference." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:45 +msgid "Create network." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:49 +msgid "Output file format name." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:53 +msgid "Spatial reference input." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:57 +msgid "Network creation option set as pair name=value." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:61 +msgid "Import layer with dataset name to copy." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:65 +msgid "Layer name in dataset. If unset, 0 layer is copied." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:69 +msgid "" +"Make a topological connection, where the gfid_src and gfid_tgt are " +"vertices and gfid_con is edge (gfid_con can be -1, so the system edge " +"will be inserted)." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:71 +msgid "Manually assign the following values:" +msgstr "" + +#: ../../source/programs/gnmmanage.rst:75 +msgid "Cost / weight" +msgstr "" + +#: ../../source/programs/gnmmanage.rst:79 +msgid "Inverse cost" +msgstr "" + +#: ../../source/programs/gnmmanage.rst:83 +msgid "Direction of the edge." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:87 +msgid "Removes the connection from the graph." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:91 +msgid "Creates a rule in the network by the given rule_str string." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:95 +msgid "" +"Create topology automatically with the given double tolerance and layer " +"names. In no layer name provided all layers of network will be used." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:99 +msgid "Delete network." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:103 +msgid "Change blocking state of network edges or vertices." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:107 +msgid "" +"Block feature before the main operation. Blocking features are saved in " +"the special layer." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:111 +msgid "Unblock feature before the main operation." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:115 +msgid "Unblock all blocked features before the main operation." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:123 +msgid "The network layer name." +msgstr "" + +#: ../../source/programs/index.rst:23 ../../source/programs/index.rst:122 +msgid "Common options" +msgstr "" + +#: ../../source/programs/index.rst:5 +msgid "Programs" +msgstr "" + +#: ../../source/programs/index.rst:8 +msgid "General" +msgstr "" + +#: ../../source/programs/index.rst:18 +msgid ":ref:`argument_syntax`" +msgstr "" + +#: ../../source/programs/index.rst:21 +msgid "Raster programs" +msgstr "" + +#: ../../source/programs/index.rst:67 +msgid ":ref:`Common options <raster_common_options>`" +msgstr "" + +#: ../../source/programs/index.rst:68 +msgid "" +":ref:`gdal-config`: Determines various information about a GDAL " +"installation." +msgstr "" + +#: ../../source/programs/index.rst:69 +msgid "" +":ref:`gdal2tiles`: Generates directory with TMS tiles, KMLs and simple " +"web viewers." +msgstr "" + +#: ../../source/programs/index.rst:70 +msgid ":ref:`gdal2xyz`: Translates a raster file into xyz format." +msgstr "" + +#: ../../source/programs/index.rst:71 +msgid ":ref:`gdal_calc`: Command line raster calculator with numpy syntax." +msgstr "" + +#: ../../source/programs/index.rst:72 +msgid "" +":ref:`gdal_contour`: Builds vector contour lines from a raster elevation " +"model." +msgstr "" + +#: ../../source/programs/index.rst:73 +msgid ":ref:`gdal_create`: Create a raster file (without source dataset)." +msgstr "" + +#: ../../source/programs/index.rst:74 +msgid "" +":ref:`gdal_edit`: Edit in place various information of an existing GDAL " +"dataset." +msgstr "" + +#: ../../source/programs/index.rst:75 +msgid ":ref:`gdal_fillnodata`: Fill raster regions by interpolation from edges." +msgstr "" + +#: ../../source/programs/index.rst:76 +msgid ":ref:`gdal_footprint`: Compute footprint of a raster." +msgstr "" + +#: ../../source/programs/index.rst:77 +msgid ":ref:`gdal_grid`: Creates regular grid from the scattered data." +msgstr "" + +#: ../../source/programs/index.rst:78 +msgid ":ref:`gdal_merge`: Mosaics a set of images." +msgstr "" + +#: ../../source/programs/index.rst:79 +msgid ":ref:`gdal_pansharpen`: Perform a pansharpen operation." +msgstr "" + +#: ../../source/programs/index.rst:80 +msgid ":ref:`gdal_polygonize`: Produces a polygon feature layer from a raster." +msgstr "" + +#: ../../source/programs/index.rst:81 +msgid ":ref:`gdal_proximity`: Produces a raster proximity map." +msgstr "" + +#: ../../source/programs/index.rst:82 +msgid ":ref:`gdal_rasterize`: Burns vector geometries into a raster." +msgstr "" + +#: ../../source/programs/index.rst:83 +msgid "" +":ref:`gdal_retile`: Retiles a set of tiles and/or build tiled pyramid " +"levels." +msgstr "" + +#: ../../source/programs/index.rst:84 +msgid ":ref:`gdal_sieve`: Removes small raster polygons." +msgstr "" + +#: ../../source/programs/index.rst:85 +msgid ":ref:`gdal_translate`: Converts raster data between different formats." +msgstr "" + +#: ../../source/programs/index.rst:86 +msgid ":ref:`gdal_viewshed`: Compute a visibility mask for a raster." +msgstr "" + +#: ../../source/programs/index.rst:87 +msgid ":ref:`gdaladdo`: Builds or rebuilds overview images." +msgstr "" + +#: ../../source/programs/index.rst:88 +msgid "" +":ref:`gdalattachpct`: Attach a color table to a raster file from an input" +" file." +msgstr "" + +#: ../../source/programs/index.rst:89 +msgid ":ref:`gdalbuildvrt`: Builds a VRT from a list of datasets." +msgstr "" + +#: ../../source/programs/index.rst:90 +msgid ":ref:`gdalcompare`: Compare two images." +msgstr "" + +#: ../../source/programs/index.rst:91 +msgid ":ref:`gdaldem`: Tools to analyze and visualize DEMs." +msgstr "" + +#: ../../source/programs/index.rst:92 +msgid ":ref:`gdalinfo`: Lists information about a raster dataset." +msgstr "" + +#: ../../source/programs/index.rst:93 +msgid ":ref:`gdallocationinfo`: Raster query tool" +msgstr "" + +#: ../../source/programs/index.rst:94 +msgid ":ref:`gdalmanage`: Identify, delete, rename and copy raster data files." +msgstr "" + +#: ../../source/programs/index.rst:95 +msgid ":ref:`gdalmove`: Transform georeferencing of raster file in place." +msgstr "" + +#: ../../source/programs/index.rst:96 +msgid "" +":ref:`gdalsrsinfo`: Lists info about a given SRS in number of formats " +"(WKT, PROJ.4, etc.)" +msgstr "" + +#: ../../source/programs/index.rst:97 +msgid ":ref:`gdaltindex`: Builds an OGR-supported dataset as a raster tileindex." +msgstr "" + +#: ../../source/programs/index.rst:98 +msgid ":ref:`gdaltransform`: Transforms coordinates." +msgstr "" + +#: ../../source/programs/index.rst:99 +msgid ":ref:`gdalwarp`: Image reprojection and warping utility." +msgstr "" + +#: ../../source/programs/index.rst:100 +msgid ":ref:`nearblack`: Convert nearly black/white borders to black." +msgstr "" + +#: ../../source/programs/index.rst:101 +msgid ":ref:`pct2rgb`: Convert an 8bit paletted image to 24bit RGB." +msgstr "" + +#: ../../source/programs/index.rst:102 +msgid ":ref:`rgb2pct`: Convert a 24bit RGB image to 8bit paletted." +msgstr "" + +#: ../../source/programs/index.rst:105 +msgid "Multidimensional Raster programs" +msgstr "" + +#: ../../source/programs/index.rst:116 +msgid "" +":ref:`gdalmdiminfo`: Reports structure and content of a multidimensional " +"dataset." +msgstr "" + +#: ../../source/programs/index.rst:117 +msgid "" +":ref:`gdalmdimtranslate`: Converts multidimensional data between " +"different formats, and perform subsetting." +msgstr "" + +#: ../../source/programs/index.rst:120 +msgid "Vector programs" +msgstr "" + +#: ../../source/programs/index.rst:136 +msgid ":ref:`Common options <vector_common_options>`" +msgstr "" + +#: ../../source/programs/index.rst:137 +msgid ":ref:`ogrinfo`: Lists information about an OGR-supported data source." +msgstr "" + +#: ../../source/programs/index.rst:138 +msgid ":ref:`ogr2ogr`: Converts simple features data between file formats." +msgstr "" + +#: ../../source/programs/index.rst:139 +msgid ":ref:`ogrtindex`: Creates a tileindex." +msgstr "" + +#: ../../source/programs/index.rst:140 +msgid "" +":ref:`ogrlineref`: Create linear reference and provide some calculations " +"using it." +msgstr "" + +#: ../../source/programs/index.rst:141 +msgid ":ref:`ogrmerge`: Merge several vector datasets into a single one." +msgstr "" + +#: ../../source/programs/index.rst:142 +msgid "" +":ref:`ogr_layer_algebra`: Performs various Vector layer algebraic " +"operations." +msgstr "" + +#: ../../source/programs/index.rst:145 +msgid "Geographic network programs" +msgstr "" + +#: ../../source/programs/index.rst:156 +msgid ":ref:`gnmmanage`: Manages networks" +msgstr "" + +#: ../../source/programs/index.rst:157 +msgid ":ref:`gnmanalyse`: Analyses networks" +msgstr "" + +#: ../../source/programs/index.rst:160 +msgid "Other utilities" +msgstr "" + +#: ../../source/programs/index.rst:170 +msgid ":ref:`sozip`: Generate a seek-optimized ZIP (SOZip) file" +msgstr "" + +#: ../../source/programs/nearblack.rst:5 +msgid "nearblack" +msgstr "" + +#: ../../source/programs/nearblack.rst:9 +msgid "Convert nearly black/white borders to black." +msgstr "" + +#: ../../source/programs/nearblack.rst:27 +msgid "" +"This utility will scan an image and try to set all pixels that are nearly" +" or exactly black, white or one or more custom colors around the collar " +"to black or white. This is often used to \"fix up\" lossy compressed air " +"photos so that color pixels can be treated as transparent when mosaicing." +" The output format must use lossless compression if either alpha band or " +"mask band is not set." +msgstr "" + +#: ../../source/programs/nearblack.rst:39 +msgid "The name of the output file to be created." +msgstr "" + +#: ../../source/programs/nearblack.rst:43 +msgid "" +"Select the output format. Starting with GDAL 2.3, if not specified, the " +"format is guessed from the extension (previously was ERDAS Imagine .img)." +" Use the short format name (GTiff for GeoTIFF for example)." +msgstr "" + +#: ../../source/programs/nearblack.rst:50 +msgid "" +"Passes a creation option to the output format driver. Multiple " +":option:`-co` options may be listed. See :ref:`raster_drivers` format " +"specific documentation for legal creation options for each format." +msgstr "" + +#: ../../source/programs/nearblack.rst:54 +msgid "Only valid when creating a new file" +msgstr "" + +#: ../../source/programs/nearblack.rst:58 +msgid "Search for nearly white (255) pixels instead of nearly black pixels." +msgstr "" + +#: ../../source/programs/nearblack.rst:62 +msgid "" +"Search for pixels near the specified color. May be specified multiple " +"times. When -color is specified, the pixels that are considered as the " +"collar are set to 0." +msgstr "" + +#: ../../source/programs/nearblack.rst:67 +msgid "" +"Select how far from black, white or custom colors the pixel values can be" +" and still considered near black, white or custom color. Defaults to 15." +msgstr "" + +#: ../../source/programs/nearblack.rst:72 +msgid "" +"number of consecutive non-black pixels that can be encountered before the" +" giving up search inwards. Defaults to 2." +msgstr "" + +#: ../../source/programs/nearblack.rst:77 +msgid "" +"Adds an alpha band if the output file is specified and the input file has" +" 3 bands, or sets the alpha band of the output file if it is specified " +"and the input file has 4 bands, or sets the alpha band of the input file " +"if it has 4 bands and no output file is specified. The alpha band is set " +"to 0 in the image collar and to 255 elsewhere." +msgstr "" + +#: ../../source/programs/nearblack.rst:84 +msgid "" +"Adds a mask band to the output file, or adds a mask band to the input " +"file if it does not already have one and no output file is specified. The" +" mask band is set to 0 in the image collar and to 255 elsewhere." +msgstr "" + +#: ../../source/programs/nearblack.rst:92 +msgid "Selects the algorithm to apply." +msgstr "" + +#: ../../source/programs/nearblack.rst:94 +msgid "" +"``twopasses`` uses a top-to-bottom pass followed by a bottom-to-top pass." +" This is the only algorithm implemented before GDAL 3.8. It may miss with" +" concave areas. The algorithm processes the image one scanline at a time." +" A scan \"in\" is done from either end setting pixels to black or white " +"until at least \"non_black_pixels\" pixels that are more than \"dist\" " +"gray levels away from black, white or custom colors have been encountered" +" at which point the scan stops. The nearly black, white or custom color " +"pixels are set to black or white. The algorithm also scans from top to " +"bottom and from bottom to top to identify indentations in the top or " +"bottom." +msgstr "" + +#: ../../source/programs/nearblack.rst:104 +msgid "" +"``floodfill`` (added in GDAL 3.8) uses the `Flood Fill " +"<https://en.wikipedia.org/wiki/Flood_fill#Span_filling>`_ algorithm and " +"will work with concave areas. It requires creating a temporary dataset " +"and is slower than ``twopasses``. When a non-zero value for :option:`-nb`" +" is used, ``twopasses`` is actually called as an initial step of " +"``floodfill``." +msgstr "" + +#: ../../source/programs/nearblack.rst:115 +msgid "" +"The input file. Any GDAL supported format, any number of bands, normally" +" 8bit Byte bands." +msgstr "" + +#: ../../source/programs/nearblack.rst:119 +msgid "The processing is all done in 8bit (Bytes)." +msgstr "" + +#: ../../source/programs/nearblack.rst:121 +msgid "" +"If the output file is omitted, the processed results will be written back" +" to the input file - which must support update." +msgstr "" + +#: ../../source/programs/nearblack.rst:127 +msgid "This utility is also callable from C with :cpp:func:`GDALNearblack`." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:5 +msgid "ogr2ogr" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:9 +msgid "Converts simple features data between file formats." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:70 +msgid "" +":program:`ogr2ogr` can be used to convert simple features data between " +"file formats. It can also perform various operations during the process, " +"such as spatial or attribute selection, reducing the set of attributes, " +"setting the output coordinate system or even reprojecting the features " +"during translation." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:83 +msgid "" +"Output file format name, e.g. ``ESRI Shapefile``, ``MapInfo File``, " +"``PostgreSQL``. Starting with GDAL 2.3, if not specified, the format is " +"guessed from the extension (previously was ESRI Shapefile)." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:89 +msgid "" +"Append to existing layer instead of creating new. This option also " +"enables :option:`-update`." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:96 +msgid "" +"Variant of :option:`-append` where the " +":cpp:func:`OGRLayer::UpsertFeature` operation is used to insert or update" +" features instead of appending with :cpp:func:`OGRLayer::CreateFeature`." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:100 +msgid "" +"This is currently implemented only in a few drivers: :ref:`vector.gpkg` " +"and :ref:`vector.mongodbv3`." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:103 +msgid "" +"The upsert operation uses the FID of the input feature, when it is set " +"and is a \"significant\" (that is the FID column name is not the empty " +"string), as the key to update existing features. It is crucial to make " +"sure that the FID in the source and target layers are consistent." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:108 +msgid "" +"For the GPKG driver, it is also possible to upsert features whose FID is " +"unset or non-significant (:option:`-unsetFid` can be used to ignore the " +"FID from the source feature), when there is a UNIQUE column that is not " +"the integer primary key." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:115 +msgid "Delete the output layer and recreate it empty" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:119 +msgid "" +"Open existing output datasource in update mode rather than trying to " +"create a new one" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:124 +msgid "Comma-delimited list of fields from input layer to copy to the new layer." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:126 +msgid "" +"Starting with GDAL 3.9, field names with spaces, commas or double-quote " +"should be surrounded with a starting and ending double-quote character, " +"and double-quote characters in a field name should be escaped with " +"backslash." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:130 +msgid "" +"Depending on the shell used, this might require further quoting. For " +"example, to select ``regular_field``, ``a_field_with space, and comma`` " +"and ``a field with \" double quote`` with a Unix shell:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:138 +msgid "" +"A field is only selected once, even if mentioned several times in the " +"list and if the input layer has duplicate field names." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:141 +msgid "Geometry fields can also be specified in the list." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:143 +msgid "" +"All fields are selected when -select is not specified. Specifying the " +"empty string can be used to disable selecting any attribute field, and " +"only keep geometries." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:147 +msgid "" +"Note this setting cannot be used together with ``-append``. To control " +"the selection of fields when appending to a layer, use ``-fieldmap`` or " +"``-sql``." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:152 ../../source/programs/ogrmerge.rst:153 +msgid "" +"Display progress on terminal. Only works if input layers have the \"fast " +"feature count\" capability." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:157 +msgid "" +"SQL statement to execute. The resulting table/layer will be saved to the " +"output. Starting with GDAL 2.1, the ``@filename`` syntax can be used to " +"indicate that the content is in the pointed filename." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:163 +msgid "" +"SQL dialect. In some cases can be used to use the (unoptimized) " +":ref:`ogr_sql_dialect` instead of the native SQL of an RDBMS by passing " +"the ``OGRSQL`` dialect value. The :ref:`sql_sqlite_dialect` dialect can " +"be chosen with the ``SQLITE`` and ``INDIRECT_SQLITE`` dialect values, and" +" this can be used with any datasource." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:170 +msgid "" +"Attribute query (like SQL WHERE). Starting with GDAL 2.1, the " +"``@filename`` syntax can be used to indicate that the content is in the " +"pointed filename." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:175 ../../source/programs/ogrmerge.rst:158 +msgid "Continue after a failure, skipping the failed feature." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:179 +msgid "" +"spatial query extents, in the SRS of the source layer(s) (or the one " +"specified with ``-spat_srs``). Only features whose geometry intersects " +"the extents will be selected. The geometries will not be clipped unless " +"``-clipsrc`` is specified." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:186 +msgid "Override spatial filter SRS." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:190 +msgid "Name of the geometry field on which the spatial filter operates on." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:202 +msgid "Assign an alternate name to the new layer" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:206 +msgid "" +"Define the geometry type for the created layer. One of ``NONE``, " +"``GEOMETRY``, ``POINT``, ``LINESTRING``, ``POLYGON``, " +"``GEOMETRYCOLLECTION``, ``MULTIPOINT``, ``MULTIPOLYGON``, " +"``MULTILINESTRING``, ``CIRCULARSTRING``, ``COMPOUNDCURVE``, " +"``CURVEPOLYGON``, ``MULTICURVE``, and ``MULTISURFACE`` non-linear " +"geometry types. Add ``Z``, ``M``, or ``ZM`` to the type name to specify " +"coordinates with elevation, measure, or elevation and measure. " +"``PROMOTE_TO_MULTI`` can be used to automatically promote layers that mix" +" polygon or multipolygons to multipolygons, and layers that mix " +"linestrings or multilinestrings to multilinestrings. Can be useful when " +"converting shapefiles to PostGIS and other target drivers that implement " +"strict checks for geometry types. ``CONVERT_TO_LINEAR`` can be used to to" +" convert non-linear geometry types into linear geometry types by " +"approximating them, and ``CONVERT_TO_CURVE`` to promote a non-linear type" +" to its generalized curve type (``POLYGON`` to ``CURVEPOLYGON``, " +"``MULTIPOLYGON`` to ``MULTISURFACE``, ``LINESTRING`` to " +"``COMPOUNDCURVE``, ``MULTILINESTRING`` to ``MULTICURVE``). Starting with " +"version 2.1 the type can be defined as measured (\"25D\" remains as an " +"alias for single \"Z\"). Some forced geometry conversions may result in " +"invalid geometries, for example when forcing conversion of multi-part " +"multipolygons with ``-nlt POLYGON``, the resulting polygon will break the" +" Simple Features rules." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:228 +msgid "" +"Starting with GDAL 3.0.5, ``-nlt CONVERT_TO_LINEAR`` and ``-nlt " +"PROMOTE_TO_MULTI`` can be used simultaneously." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:233 +msgid "" +"Force the coordinate dimension to val (valid values are ``XY``, ``XYZ``, " +"``XYM``, and ``XYZM`` - for backwards compatibility ``2`` is an alias for" +" ``XY`` and ``3`` is an alias for ``XYZ``). This affects both the layer " +"geometry type, and feature geometries. The value can be set to " +"``layer_dim`` to instruct feature geometries to be promoted to the " +"coordinate dimension declared by the layer. Support for M was added in " +"GDAL 2.1." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:242 +msgid "" +"Assign an output SRS, but without reprojecting (use :option:`-t_srs` to " +"reproject)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:251 +msgid "" +"Assign a coordinate epoch, linked with the output SRS. Useful when the " +"output SRS is a dynamic CRS. Only taken into account if :option:`-a_srs` " +"is used." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:257 +msgid "Reproject/transform to this SRS on output, and assign it as output SRS." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:259 +msgid "" +"A source SRS must be available for reprojection to occur. The source SRS " +"will be by default the one found in the source layer when it is " +"available, or as overridden by the user with :option:`-s_srs`" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:269 +msgid "" +"Assign a coordinate epoch, linked with the output SRS. Useful when the " +"output SRS is a dynamic CRS. Only taken into account if :option:`-t_srs` " +"is used. It is also mutually exclusive with :option:`-a_coord_epoch`." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:278 +msgid "" +"Override source SRS. If not specified the SRS found in the input layer " +"will be used. This option has only an effect if used together with " +":option:`-t_srs` to reproject." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:288 +msgid "" +"Set/override the geometry X/Y coordinate resolution. If only a numeric " +"value is specified, it is assumed to be expressed in the units of the " +"target SRS. The m, mm or deg suffixes can be specified to indicate that " +"the value must be interpreted as being in meter, millimeter or degree." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:293 +msgid "" +"When specifying this option, the :cpp:func:`OGRGeometry::SetPrecision` " +"method is run on geometries (that are not curves) before passing them to " +"the output driver, to avoid generating invalid geometries due to the " +"potentially reduced precision (unless the " +":config:`OGR_APPLY_GEOM_SET_PRECISION` configuration option is set to " +"``NO``)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:299 +msgid "" +"If neither this option nor :option:`-unsetCoordPrecision` are specified, " +"the coordinate resolution of the source layer, if available, is used." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:306 +msgid "" +"Set/override the geometry Z coordinate resolution. If only a numeric " +"value is specified, it is assumed to be expressed in the units of the " +"target SRS. The m or mm suffixes can be specified to indicate that the " +"value must be interpreted as being in meter or millimeter. If neither " +"this option nor :option:`-unsetCoordPrecision` are specified, the " +"coordinate resolution of the source layer, if available, is used." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:317 +msgid "" +"Set/override the geometry M coordinate resolution. If neither this option" +" nor :option:`-unsetCoordPrecision` are specified, the coordinate " +"resolution of the source layer, if available, is used." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:325 +msgid "" +"Prevent the geometry coordinate resolution from being set on target " +"layer(s)." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:354 +msgid "" +"Use the FID of the source features instead of letting the output driver " +"automatically assign a new one (for formats that require a FID). If not " +"in append mode, this behavior is the default if the output driver has a " +"FID layer creation option, in which case the name of the source FID " +"column will be used and source feature IDs will be attempted to be " +"preserved. This behavior can be disabled by setting ``-unsetFid``. This " +"option is not compatible with ``-explodecollections``." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:364 +msgid "" +"If provided, only the feature with the specified feature id will be " +"processed. Operates exclusive of the spatial or attribute queries. Note:" +" if you want to select several features based on their feature id, you " +"can also use the fact the 'fid' is a special field recognized by OGR SQL." +" So, `-where \"fid in (1,3,5)\"` would select features 1, 3 and 5." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:372 ../../source/programs/ogrinfo.rst:95 +msgid "Limit the number of features per layer." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:376 +msgid "Input dataset open option (format specific)." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:380 +msgid "" +"Destination dataset open option (format specific), only valid in -update " +"mode." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:384 +msgid "" +"Group n features per transaction (default 100 000). Increase the value " +"for better performance when writing into DBMS drivers that have " +"transaction support. ``n`` can be set to unlimited to load the data into " +"a single transaction." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:391 +msgid "" +"Force the use of a dataset level transaction (for drivers that support " +"such mechanism), especially for drivers such as FileGDB that only support" +" dataset level transaction in emulation mode." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:397 +msgid "Clip geometries (before potential reprojection) to one of the following:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:399 +msgid "the specified bounding box (expressed in source SRS)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:400 +msgid "a WKT geometry (POLYGON or MULTIPOLYGON expressed in source SRS)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:401 ../../source/programs/ogr2ogr.rst:425 +msgid "one or more geometries selected from a datasource" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:402 +msgid "the spatial extent of the -spat option if you use the spat_extent keyword." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:404 +msgid "" +"When specifying a datasource, you will generally want to use -clipsrc in " +"combination of the -clipsrclayer, -clipsrcwhere or -clipsrcsql options." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:409 +msgid "" +"Select desired geometries from the source clip datasource using an SQL " +"query." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:417 +msgid "" +"Restrict desired geometries from the source clip layer based on an " +"attribute query." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:421 +msgid "Clip geometries (after potential reprojection) to one of the following:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:423 +msgid "the specified bounding box (expressed in destination SRS)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:424 +msgid "a WKT geometry (POLYGON or MULTIPOLYGON expressed in destination SRS)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:427 +msgid "" +"When specifying a datasource, you will generally want to use -clipdst in " +"combination with the -clipdstlayer, -clipdstwhere or -clipdstsql options." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:432 +msgid "" +"Select desired geometries from the destination clip datasource using an " +"SQL query." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:436 +msgid "Select the named layer from the destination clip datasource." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:440 +msgid "" +"Restrict desired geometries from the destination clip layer based on an " +"attribute query." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:444 +msgid "Split geometries crossing the dateline meridian (long. = +/- 180deg)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:448 +msgid "" +"Offset from dateline in degrees (default long. = +/- 10deg, geometries " +"within 170deg to -170deg will be split)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:453 +msgid "" +"Distance tolerance for simplification. Note: the algorithm used preserves" +" topology per feature, in particular for polygon geometries, but not for " +"a whole layer." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:457 +msgid "" +"The specified value of this option is the tolerance used to merge " +"consecutive points of the output geometry using the " +":cpp:func:`OGRGeometry::Simplify` method The unit of the distance is in " +"georeferenced units of the source vector dataset. This option is applied " +"before the reprojection implied by :option:`-t_srs`" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:466 +msgid "" +"The specified value of this option is the maximum distance between two " +"consecutive points of the output geometry before intermediate points are " +"added. The unit of the distance is georeferenced units of the source " +"raster. This option is applied before the reprojection implied by " +":option:`-t_srs`" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:473 +msgid "" +"Run the :cpp:func:`OGRGeometry::MakeValid` operation, followed by " +":cpp:func:`OGRGeometryFactory::removeLowerDimensionSubGeoms`, on " +"geometries to ensure they are valid regarding the rules of the Simple " +"Features specification." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:481 +msgid "" +"Converts any field of the specified type to a field of type string in the" +" destination layer. Valid types are : ``Integer``, ``Integer64``, " +"``Real``, ``String``, ``Date``, ``Time``, ``DateTime``, ``Binary``, " +"``IntegerList``, ``Integer64List``, ``RealList``, ``StringList``. Special" +" value ``All`` can be used to convert all fields to strings. This is an " +"alternate way to using the CAST operator of OGR SQL, that may avoid " +"typing a long SQL query. Note that this does not influence the field " +"types used by the source driver, and is only an afterwards conversion. " +"Also note that this option is without effects on fields whose presence " +"and type is hard-coded in the output driver (e.g KML, GPX)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:493 +msgid "" +"Converts any field of the specified type to another type. Valid types are" +" : ``Integer``, ``Integer64``, ``Real``, ``String``, ``Date``, ``Time``, " +"``DateTime``, ``Binary``, ``IntegerList``, ``Integer64List``, " +"``RealList``, ``StringList``. Types can also include subtype between " +"parenthesis, such as ``Integer(Boolean)``, ``Real(Float32)``, ... Special" +" value ``All`` can be used to convert all fields to another type. This is" +" an alternate way to using the CAST operator of OGR SQL, that may avoid " +"typing a long SQL query. This is a generalization of -fieldTypeToString. " +"Note that this does not influence the field types used by the source " +"driver, and is only an afterwards conversion. Also note that this option " +"is without effects on fields whose presence and type is hard-coded in the" +" output driver (e.g KML, GPX)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:510 +msgid "" +"Converts date time values from the timezone specified in the source value" +" to the target timezone expressed with :option:`-dateTimeTo`. Datetime " +"whose timezone is unknown or localtime are not modified." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:514 +msgid "HH must be in the [0,14] range and MM=00, 15, 30 or 45." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:518 +msgid "Set field width and precision to 0." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:522 +msgid "" +"Split fields of type StringList, RealList or IntegerList into as many " +"fields of type String, Real or Integer as necessary." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:527 +msgid "" +"To be combined with ``-splitlistfields`` to limit the number of subfields" +" created for each split field." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:532 +msgid "" +"Produce one feature for each geometry in any kind of geometry collection " +"in the source file, applied after any ``-sql`` option. This options is " +"not compatible with ``-preserve_fid`` but ``-sql \"SELECT fid AS " +"original_fid, * FROM ...\"`` can be used to store the original FID if " +"needed." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:539 +msgid "Uses the specified field to fill the Z coordinate of geometries." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:543 +msgid "" +"Use the indicated ground control point to compute a coordinate " +"transformation. The transformation method can be selected by specifying " +"the :option:`-order` or :option:`-tps` options. Note that unlike raster " +"tools such as gdal_edit or gdal_translate, GCPs are not added to the " +"output dataset. This option may be provided multiple times to provide a " +"set of GCPs (at least 2 GCPs are needed)." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:553 +msgid "" +"Order of polynomial used for warping (1 to 3). The default is to select a" +" polynomial order based on the number of GCPs." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:562 +msgid "" +"Specifies the list of field indexes to be copied from the source to the " +"destination. The (n)th value specified in the list is the index of the " +"field in the target layer definition in which the n(th) field of the " +"source layer must be copied. Index count starts at zero. To omit a field," +" specify a value of -1. There must be exactly as many values in the list " +"as the count of the fields in the source layer. We can use the 'identity'" +" setting to specify that the fields should be transferred by using the " +"same order. This setting should be used along with the ``-append`` " +"setting." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:573 +msgid "" +"This is a specialized version of ``-append``. Contrary to ``-append``, " +"``-addfields`` has the effect of adding, to existing target layers, the " +"new fields found in source layers. This option is useful when merging " +"files that have non-strictly identical structures. This might not work " +"for output formats that don't support adding fields to existing non-empty" +" layers. Note that if you plan to use -addfields, you may need to combine" +" it with -forceNullable, including for the initial import." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:583 +msgid "" +"Do field name matching between source and existing target layer in a more" +" relaxed way if the target driver has an implementation for it." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:588 +msgid "" +"Do not propagate not-nullable constraints to target layer if they exist " +"in source layer." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:593 +msgid "" +"Do not propagate default field values to target layer if they exist in " +"source layer." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:598 +msgid "" +"Can be specified to prevent the name of the source FID column and source " +"feature IDs from being re-used for the target layer. This option can for " +"example be useful if selecting source features with a ORDER BY clause." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:606 +msgid "Treat empty string values as null." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:612 +msgid "" +"When this is specified, any selected field that is linked to a coded " +"field domain will be accompanied by an additional field " +"(``{dstfield}_resolved``), that will contain the description of the coded" +" value." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:618 +msgid "" +"To disable copying of metadata from source dataset and layers into target" +" dataset and layers, when supported by output driver." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:623 +msgid "" +"Passes a metadata key and value to set on the output dataset, when " +"supported by output driver." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:628 +msgid "" +"To disable copying of native data, i.e. details of source format not " +"captured by OGR abstraction, that are otherwise preserved by some drivers" +" (like GeoJSON) when converting to same format." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:636 +msgid "Output dataset name." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:640 +msgid "Source dataset name." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:644 +msgid "" +"One or more source layer names to copy to the output dataset. If no layer" +" names are passed, then all source layers are copied." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:649 +msgid "Performance Hints" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:651 +msgid "" +"When writing into transactional DBMS (SQLite/PostgreSQL,MySQL, etc...), " +"it might be beneficial to increase the number of INSERT statements " +"executed between BEGIN TRANSACTION and COMMIT TRANSACTION statements. " +"This number is specified with the -gt option. For example, for SQLite, " +"explicitly defining -gt 65536 ensures optimal performance while " +"populating some table containing many hundreds of thousands or millions " +"of rows. However, note that -skipfailures overrides -gt and sets the size" +" of transactions to 1." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:659 +msgid "" +"For PostgreSQL, the :config:`PG_USE_COPY` config option can be set to YES" +" for a significant insertion performance boost. See the PG driver " +"documentation page." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:662 +msgid "" +"More generally, consult the documentation page of the input and output " +"drivers for performance hints." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:666 +msgid "Known issues" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:668 +msgid "" +"Starting with GDAL 3.8, ogr2ogr uses internally an Arrow array based API " +"(cf :ref:`rfc-86`) for some source formats (in particular GeoPackage or " +"FlatGeoBuf), and for the most basic types of operations, to improve " +"performance. This substantial change in the ogr2ogr internal logic has " +"required a number of fixes throughout the GDAL 3.8.x bugfix releases to " +"fully stabilize it, and we believe most issues are resolved with GDAL " +"3.9. If you hit errors not met with earlier GDAL versions, you may " +"specify ``--config OGR2OGR_USE_ARROW_API NO`` on the ogr2ogr command line" +" to opt for the classic algorithm using an iterative feature based " +"approach. If that flag is needed with GDAL >= 3.9, please file an issue " +"on the `GDAL issue tracker <https://github.com/OSGeo/gdal/issues>`__." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:683 +msgid "This utility is also callable from C with :cpp:func:`GDALVectorTranslate`." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:690 +msgid "Basic conversion from Shapefile to GeoPackage:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:696 +msgid "" +"Change the coordinate reference system from ``EPSG:4326`` to " +"``EPSG:3857``:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:702 +msgid "Example appending to an existing layer:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:708 +msgid "Clip input layer with a bounding box (<xmin> <ymin> <xmax> <ymax>):" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:714 +msgid "Filter Features by a ``-where`` clause:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:722 +msgid "More examples are given in the individual format pages." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:725 +msgid "Advanced examples" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:727 +msgid "" +"Reprojecting from ETRS_1989_LAEA_52N_10E to EPSG:4326 and clipping to a " +"bounding box:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:733 +msgid "" +"Using the ``-fieldmap`` setting. The first field of the source layer is " +"used to fill the third field (index 2 = third field) of the target layer," +" the second field of the source layer is ignored, the third field of the " +"source layer used to fill the fifth field of the target layer." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:742 +msgid "Outputting geometries with the CSV driver." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:744 +msgid "" +"By default, this driver does not preserve geometries on layer creation by" +" default. An explicit layer creation option is needed:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:751 +msgid "Extracting only geometries." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:753 +msgid "" +"There are different situations, depending if the input layer has a named " +"geometry column, or not. First check, with ogrinfo if there is a reported" +" geometry column." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:761 +msgid "" +"In that situation where the input format is a FileGeodatabase, it is " +"called SHAPE and can thus be referenced directly in a SELECT statement." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:769 +msgid "" +"For a shapefile with a unnamed geometry column, ``_ogr_geometry_`` can be" +" used as a special name to designate the implicit geometry column, when " +"using the default :ref:`OGR SQL <ogr_sql_dialect>` dialect. The name " +"begins with an underscore and SQL syntax requires that it must appear " +"between double quotes. In addition the command line interpreter may " +"require that double quotes are escaped and the final SELECT statement " +"could look like:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:781 +msgid "" +"If using the :ref:`SQL SQLite <sql_sqlite_dialect>` dialect, the special " +"geometry name is ``geometry`` when the source geometry column has no " +"name." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:5 +msgid "ogr_layer_algebra" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:11 +msgid "Performs various Vector layer algebraic operations." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:33 +msgid "" +"The :program:`ogr_layer_algebra` provides a command line utility to " +"perform various vector layer algebraic operations. The utility takes a " +"vector input source and a method source and generates the output of the " +"operation in the specified output file." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:38 +msgid "" +"ogr_layer_algebra is a Python utility, and is only available if GDAL " +"Python bindings are available." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:48 +msgid "``Union``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:50 +msgid "" +"A union is a set of features, which represent areas that are in either of" +" the operand layers." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:52 +msgid "``Intersection``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:54 +msgid "" +"An intersection is a set of features, which represent the common areas of" +" two layers." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:56 +msgid "``SymDifference``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:58 +msgid "" +"A symmetric difference is a set of features, which represent areas that " +"are in operand layers but which do not intersect." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:60 +msgid "``Identity``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:62 +msgid "" +"The identity method identifies features in the input layer with features " +"in the method layer possibly splitting features into several features. By" +" default the result layer has attributes from both operand layers." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:65 +msgid "``Update``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:67 +msgid "" +"The update method creates a layer, which add features into the input " +"layer from the method layer possibly cutting features in the input layer." +" By default the result layer has attributes only from the input layer." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:70 +msgid "``Clip``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:72 +msgid "" +"The clip method creates a layer, which has features from the input layer " +"clipped to the areas of the features in the method layer. By default the " +"result layer has attributes of the input layer." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:75 +msgid "``Erase``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:77 +msgid "" +"The erase method creates a layer, which has features from the input layer" +" whose areas are erased by the features in the method layer. By default " +"the result layer has attributes of the input layer." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:82 +msgid "" +"Input dataset path for the operation to be performed. For operations " +"involving two datasets, this is one of the datasets." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:87 +msgid "" +"Layer name of the ``input_ds`` for which the operations have to be " +"performed ( Optional )" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:91 +msgid "" +"Method data set path for the operation to be performed. This is usually " +"the conditional data set supplied to the operation ( ex: clip , erase , " +"update ) This is the Second data set in the operation ( ex : Union, " +"Intersection , SymDifference )" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:97 +msgid "" +"Layer name of the ``method_ds`` for which the operations have to be " +"performed ( Optional )" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:101 +msgid "" +"Output data set path for writing the result of the operations performed " +"by ``ogr_layer_algebra``." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:105 +msgid "" +"Layer name of the ``output_lyr_name`` where the output vector has to be " +"written. ( Optional )" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:109 +msgid "" +"Indicates whether the ``output_ds`` have to be overwritten with the " +"generated result of ``ogr_layer_algebra``." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:113 +msgid "" +"Attributes for which the operation has to run on ``input_ds`` and " +"``method_ds``." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:117 +msgid "" +"Select the output format.If not specified, the format is guessed from the" +" extension (previously was ESRI Shapefile). Use the short format name" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:123 +msgid "Dataset creation option (format specific)." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:127 +#: ../../source/programs/ogrlineref.rst:72 +msgid "Layer creation option (format specific)." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:131 +msgid "" +"Comma-delimited list of fields from input layer to copy to the output " +"layer , if eligible according to the operation." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:136 +msgid "" +"Comma-delimited list of fields from method layer to copy to the output " +"layer , if eligible according to the operation." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:141 +msgid "" +"Define the geometry type for the created layer. One of NONE, GEOMETRY, " +"POINT, LINESTRING, POLYGON, GEOMETRYCOLLECTION, MULTIPOINT, MULTIPOLYGON," +" GEOMETRY25D, POINT25D, LINESTRING25D, POLYGON25D, GEOMETRYCOLLECTION25D," +" MULTIPOINT25D, MULTIPOLYGON25D." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:148 +msgid "Assign an output SRS, but without reprojecting" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:5 +msgid "ogrinfo" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:9 +msgid "" +"Lists information about an OGR-supported data source. With SQL statements" +" it is also possible to edit data." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:34 +msgid "" +"The :program:`ogrinfo` program lists various information about an OGR-" +"supported data source to stdout (the terminal). By executing SQL " +"statements it is also possible to edit data." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:46 +msgid "" +"Display the output in json format, conforming to the " +"`ogrinfo_output.schema.json " +"<https://github.com/OSGeo/gdal/blob/master/apps/data/ogrinfo_output.schema.json>`__" +" schema." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:54 +msgid "Open the data source in read-only mode." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:58 +msgid "" +"List all layers (used instead of having to give layer names as " +"arguments). In the default text output, this also enables listing all " +"features, which can be disabled with :option:`-so`. In JSON output, -al " +"is implicit, but listing of features must be explicitly enabled with " +":option:`-features`." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:67 +msgid "" +"Enable random layer reading mode, i.e. iterate over features in the order" +" they are found in the dataset, and not layer per layer. This can be " +"significantly faster for some formats (for example OSM, GMLAS). -rl " +"cannot be used with -sql." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:77 +msgid "" +"Summary Only: suppress listing of individual features and show only " +"summary information like projection, schema, feature count and extents." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:82 +msgid "Enable listing of features. This has the opposite effect of :option:`-so`." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:84 +msgid "" +"This option should be used with caution if using the library function " +":cpp:func:`GDALVectorInfo` and/or :option:`-json`, as the whole output of" +" ogrinfo will be built in memory. Consequently, when used on a large " +"collection of features, RAM may be exhausted." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:99 +msgid "" +"Quiet verbose reporting of various information, including coordinate " +"system, layer schema, extents, and feature count." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:104 +msgid "" +"An attribute query in a restricted form of the queries used in the SQL " +"`WHERE` statement. Only features matching the attribute query will be " +"reported. Starting with GDAL 2.1, the ``@<filename>`` syntax can be used " +"to indicate that the content is in the pointed filename." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:109 +msgid "Example of ``-where`` and quoting:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:118 +msgid "" +"Execute the indicated SQL statement and return the result. Starting with " +"GDAL 2.1, the ``@<filename>`` syntax can be used to indicate that the " +"content is in the pointed filename (e.g ``@my_select.txt`` where " +"my_select.txt is a file in the current directory). Data can also be " +"edited with SQL INSERT, UPDATE, DELETE, DROP TABLE, ALTER TABLE etc. " +"Editing capabilities depend on the selected dialect with " +":option:`-dialect`." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:128 +msgid "" +"SQL dialect. In some cases can be used to use (unoptimized) " +":ref:`ogr_sql_dialect` instead of the native SQL of an RDBMS by passing " +"the ``OGRSQL`` dialect value. The :ref:`sql_sqlite_dialect` can be " +"selected with the ``SQLITE`` and ``INDIRECT_SQLITE`` dialect values, and " +"this can be used with any datasource." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:135 +msgid "The area of interest. Only features within the rectangle will be reported." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:139 +msgid "Name of the geometry field on which the spatial filter operates." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:143 +msgid "" +"If provided, only the feature with this feature id will be reported. " +"Operates exclusive of the spatial or attribute queries. Note: if you want" +" to select several features based on their feature id, you can also use " +"the fact the 'fid' is a special field recognized by OGR SQL. So, `-where " +"\"fid in (1,3,5)\"` would select features 1, 3 and 5." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:151 +msgid "" +"If set to ``NO``, the feature dump will not display field values. Default" +" value is ``YES``." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:158 +msgid "Display details about a field domain." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:162 +msgid "" +"If set to ``NO``, the feature dump will not display the geometry. If set " +"to ``SUMMARY``, only a summary of the geometry will be displayed. If set " +"to ``YES`` or ``ISO_WKT``, the geometry will be reported in full OGC WKT " +"format. If set to ``WKT`` the geometry will be reported in legacy " +"``WKT``. Default value is ``YES``. (WKT and ``ISO_WKT`` are available " +"starting with GDAL 2.1, which also changes the default to ISO_WKT)" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:171 +msgid "Dataset open option (format-specific)" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:184 +msgid "" +"Report metadata for the specified domain. ``all`` can be used to report " +"metadata in all domains." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:189 +msgid "Suppress feature count printing." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:193 +msgid "Suppress spatial extent printing." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:199 +msgid "" +"Request a 3D extent to be reported (the default is 2D only). Note that " +"this operation might be slower than requesting the 2D extent, depending " +"on format and driver capabilities." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:205 +msgid "Suppress layer geometry type printing." +msgstr "" + +#: ../../source/programs/options/formats_vector.rst:3 +msgid "" +"List all vector formats supported by this GDAL build (read-only and read-" +"write) and exit. The format support is indicated as follows:" +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:7 +#: ../../source/programs/options/formats_vector.rst:6 +msgid "``ro`` is read-only driver" +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:8 +#: ../../source/programs/options/formats_vector.rst:7 +msgid "``rw`` is read or write (i.e. supports :cpp:func:`GDALDriver::CreateCopy`)" +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:9 +#: ../../source/programs/options/formats_vector.rst:8 +msgid "" +"``rw+`` is read, write and update (i.e. supports " +":cpp:func:`GDALDriver::Create`)" +msgstr "" + +#: ../../source/programs/options/formats_vector.rst:9 +msgid "" +"A ``v`` is appended for formats supporting virtual IO (``/vsimem``, " +"``/vsigzip``, ``/vsizip``, etc)." +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:11 +#: ../../source/programs/options/formats_vector.rst:10 +msgid "A ``s`` is appended for formats supporting subdatasets." +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:13 +#: ../../source/programs/options/formats_vector.rst:12 +msgid "" +"The order in which drivers are listed is the one in which they are " +"registered, which determines the order in which they are successively " +"probed when opening a dataset. Most of the time, this order does not " +"matter, but in some situations, several drivers may recognize the same " +"file. The ``-if`` option of some utilities can be specified to restrict " +"opening the dataset with a subset of drivers (generally one). Note that " +"it does not force those drivers to open the dataset. In particular, some " +"drivers have requirements on file extensions. Alternatively, the " +":config:`GDAL_SKIP` configuration option can also be used to exclude one " +"or several drivers." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:213 +msgid "" +"The WKT format used to display the SRS. Currently supported values for " +"the ``format`` are:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:218 +msgid "``WKT2`` (latest WKT version, currently *WKT2_2018*)" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:222 +msgid "``WKT2_2018``" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:228 +msgid "" +"The data source to open. May be a filename, directory or other virtual " +"name. See the OGR Vector Formats list for supported datasources." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:233 +msgid "" +"One or more layer names may be reported. If no layer names are passed " +"then ogrinfo will report a list of available layers (and their layer wide" +" geometry type). If layer name(s) are given then their extents, " +"coordinate system, feature count, geometry type, schema and all features " +"matching query parameters will be reported to the terminal. If no query " +"parameters are provided, all features are reported." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:240 +msgid "Geometries are reported in OGC WKT format." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:245 +msgid "This utility is also callable from C with :cpp:func:`GDALVectorInfo`." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:252 +msgid "Example of reporting the names of the layers in a NTF file:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:265 +msgid "" +"Example of retrieving a summary (``-so``) of a layer without showing " +"details about every single feature:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:298 +msgid "" +"Example of retrieving information on a file in JSON format without " +"showing details about every single feature:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:502 +msgid "" +"Example of using -q and an attribute query, to restrict the output to " +"certain features in a layer:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:520 +msgid "" +"Example of updating a value of an attribute in a shapefile with SQL by " +"using the SQLite dialect:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:526 +msgid "Adding a column to an input file:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:532 +msgid "" +"Sometimes there is no input file involved in a calculation. In such cases" +" one may use the ``:memory:`` input file which is a in-memory empty " +"SQLite file (and the SQLite SQL dialect will be implicitly used)." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:5 +msgid "ogrlineref" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:9 +msgid "Create linear reference and provide some calculations using it" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:32 +msgid "The :program:`ogrlineref` program can be used to:" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:34 +msgid "create a linear reference file from input data" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:36 +msgid "" +"return the \"linear referenced\" distance for the projection of the input" +" coordinates (point) on the path" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:39 +msgid "" +"return the coordinates (point) on the path according to the \"linear " +"referenced\" distance" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:42 +msgid "" +"return the portion of the path according to the \"linear referenced\" " +"begin and end distances" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:45 +msgid "" +"The :program:`ogrlineref` utility creates a linear reference - a file " +"containing segments of a certain length (e.g. 1 km in reference units.) " +"The user can get coordinates, linear referenced distances or sublines " +"(subpaths) from this file. The utility does not require the ``M`` or " +"``Z`` components in the geometry. The results can be stored in any OGR " +"supported format. Also some information is written to the stdout." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:56 +msgid "Show progress." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:60 +msgid "Suppress all messages except errors and results." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:64 +#: ../../source/programs/ogrtindex.rst:50 +msgid "Select an output format name. The default is to create a shapefile." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:76 +msgid "Create the linear reference file (linestring of parts)." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:80 +msgid "The path to input linestring datasource (e.g. the road)" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:84 +#: ../../source/programs/ogrlineref.rst:97 +#: ../../source/programs/ogrlineref.rst:113 +#: ../../source/programs/ogrlineref.rst:121 +msgid "The layer name in datasource" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:88 +msgid "" +"The field name of unique values to separate the input lines (e.g. the set" +" of roads)." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:93 +msgid "The path to linear references points (e.g. the road mile-stones)" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:101 +msgid "The field name of distances along path (e.g. mile-stones values)" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:105 +msgid "The field name of unique values to map input reference points to lines." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:109 +msgid "The path to linear reference file." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:117 +msgid "The path to output linear reference file (linestring datasource)" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:125 +msgid "The field name for storing the unique values of input lines" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:129 +msgid "The part size in linear units" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:133 +msgid "Return linear referenced position for input X, Y" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:137 +msgid "Input X coordinate" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:141 +msgid "Input Y coordinate" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:145 +msgid "Return point on path for input linear distance" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:149 +msgid "The input linear distance" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:153 +msgid "Return the portion of the input path from and to input linear positions." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:157 +msgid "The input begin linear distance" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:161 +msgid "The input end linear distance" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:166 +msgid "" +"This example would create a shapefile (:file:`parts.shp`) containing a " +"data needed for linear referencing (1 km parts):" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:5 +msgid "ogrmerge" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:9 +msgid "Merge several vector datasets into a single one." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:27 +msgid "Options specific to the :ref:`-single <ogrmerge_single_option>` option:" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:40 +msgid "" +":program:`ogrmerge` takes as input several vector datasets, each of them " +"having one or several vector layers, and copies them into a target " +"dataset." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:44 +msgid "There are essentially two modes:" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:46 +msgid "" +"the default one, where each input vector layer, is copied as a separate " +"layer into the target dataset" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:49 +msgid "" +"another one, activated with the -single switch, where the content of all " +"input vector layers is appended into a single target layer. This assumes " +"that the schema of those vector layers is more or less the same." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:54 +msgid "" +"Internally this generates a :ref:`vector.vrt` file, and if the output " +"format is not VRT, final translation is done with :program:`ogr2ogr` or " +":py:func:`gdal.VectorTranslate`. So, for advanced uses, output to VRT, " +"potential manual editing of it and :program:`ogr2ogr` can be done." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:61 +msgid "" +"ogrmerge is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:69 +msgid "Output dataset name. Required." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:73 +msgid "One or several input vector datasets. Required" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:77 +msgid "" +"Select the output format. Starting with GDAL 2.3, if not specified, the " +"format is guessed from the extension (previously was ESRI Shapefile). Use" +" the short format name" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:84 +msgid "If specified, all input vector layers will be merged into a single one." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:88 +msgid "" +"Name of the output vector layer (in single mode, and the default is " +"\"merged\"), or template to name the output vector layers in default mode" +" (the default value is ``{AUTO_NAME}``). The template can be a string " +"with the following variables that will be susbstitued with a value " +"computed from the input layer being processed:" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:94 +msgid "" +"``{AUTO_NAME}``: equivalent to ``{DS_BASENAME}_{LAYER_NAME}`` if both " +"values are different, or ``{LAYER_NAME}`` when they are identical (case " +"of shapefile)." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:97 +msgid "``{DS_NAME}``: name of the source dataset" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:98 +msgid "``{DS_BASENAME}``: base name of the source dataset" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:99 +msgid "``{DS_INDEX}``: index of the source dataset" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:100 +msgid "``{LAYER_NAME}``: name of the source layer" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:101 +msgid "``{LAYER_INDEX}``: index of the source layer" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:105 +msgid "Open an existing dataset in update mode." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:109 +msgid "" +"Overwrite the existing dataset if it already exists (for file based " +"datasets)" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:114 +msgid "" +"Open an existing dataset in update mode, and if output layers already " +"exist, append the content of input layers to them." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:119 +msgid "" +"Open an existing dataset in update mode, and if output layers already " +"exist, replace their content with the one of the input layer." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:125 +msgid "" +"Only take into account input layers whose geometry type match the type(s)" +" specified. Valid values for geom_type_name are GEOMETRY, POINT, " +"LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, " +"GEOMETRYCOLLECTION, CIRCULARSTRING, CURVEPOLYGON, MULTICURVE, " +"MULTISURFACE, CURVE, SURFACE, TRIANGLE, POLYHEDRALSURFACE and TIN." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:141 +msgid "Assign an output SRS" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:145 +msgid "Reproject/transform to this SRS on output" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:149 +msgid "Override source SRS" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:162 +msgid "" +"Only used with :option:`-single`. Determines how the schema of the target" +" layer is built from the schemas of the input layers. May be FirstLayer " +"to use the fields from the first layer found, Union to use a super-set of" +" all the fields from all source layers, or Intersection to use a sub-set " +"of all the common fields from all source layers. Defaults to Union." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:171 +msgid "" +"Only used with :option:`-single`. If specified, the schema of the target " +"layer will be extended with a new field 'name', whose content is " +"determined by -src_layer_field_content." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:177 +msgid "" +"Only used with :option:`-single`. If specified, the schema of the target " +"layer will be extended with a new field (whose name is given by " +":option:`-src_layer_field_name`, or 'source_ds_lyr' otherwise), whose " +"content is determined by ``layer_name_template``. The syntax of " +"``layer_name_template`` is the same as for :option:`-nln`." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:186 +msgid "Create a VRT with a layer for each input shapefiles" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:192 +msgid "Same, but creates a GeoPackage file" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:198 +msgid "" +"Concatenate the content of france.shp and germany.shp in merged.shp, and " +"adds a 'country' field to each feature whose value is 'france' or " +"'germany' depending where it comes from." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:5 +msgid "ogrtindex" +msgstr "" + +#: ../../source/programs/ogrtindex.rst:9 +msgid "Creates a tileindex." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:30 +msgid "" +":program:`ogrtindex` program can be used to create a tileindex - a file " +"containing a list of the identities of a bunch of other files along with " +"their spatial extents. This is primarily intended to be used with " +"`MapServer <http://mapserver.org/>`__ for tiled access to layers using " +"the OGR connection type." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:42 +msgid "Add layer number ``n`` from each source file in the tile index." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:46 +msgid "Add the layer named ``name`` from each source file in the tile index." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:54 +msgid "The name to use for the dataset name. Defaults to LOCATION." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:58 +msgid "Filenames are written with absolute paths" +msgstr "" + +#: ../../source/programs/ogrtindex.rst:62 +msgid "" +"Only layers with same projection ref as layers already inserted in the " +"tileindex will be inserted." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:67 +msgid "" +"Extent of input files will be transformed to the desired target " +"coordinate reference system. Using this option generates files that are " +"not compatible with MapServer < 7.2. Default creates simple rectangular " +"polygons in the same coordinate reference system as the input vector " +"layers." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:77 +msgid "" +"The name of the field to store the SRS of each tile. This field name can " +"be used as the value of the TILESRS keyword in MapServer >= 7.2." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:84 +msgid "" +"The format in which the SRS of each tile must be written. Available " +"formats are: ``AUTO``, ``WKT``, ``EPSG``, ``PROJ``." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:91 +msgid "" +"By default ogrtindex checks that all layers inserted into the index have " +"the same attribute schemas. If you specify this option, this test will be" +" disabled. Be aware that resulting index may be incompatible with " +"MapServer!" +msgstr "" + +#: ../../source/programs/ogrtindex.rst:96 +msgid "" +"If no :option:`-lnum` or :option:`-lname` arguments are given it is " +"assumed that all layers in source datasets should be added to the tile " +"index as independent records." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:100 +msgid "" +"If the tile index already exists it will be appended to, otherwise it " +"will be created." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:106 +msgid "" +"This example would create a shapefile (:file:`tindex.shp`) containing a " +"tile index of the ``BL2000_LINK`` layers in all the NTF files in the " +":file:`wrk` directory:" +msgstr "" + +#: ../../source/programs/pct2rgb.rst:5 +msgid "pct2rgb" +msgstr "" + +#: ../../source/programs/pct2rgb.rst:9 +msgid "Convert an 8bit paletted image to 24bit RGB." +msgstr "" + +#: ../../source/programs/pct2rgb.rst:24 +msgid "" +"This utility will convert a pseudo-color band on the input file into an " +"output RGB file of the desired format." +msgstr "" + +#: ../../source/programs/pct2rgb.rst:29 +msgid "" +"pct2rgb is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/pct2rgb.rst:43 +msgid "Band to convert to RGB, defaults to 1." +msgstr "" + +#: ../../source/programs/pct2rgb.rst:47 +msgid "Generate a RGBA file (instead of a RGB file by default)." +msgstr "" + +#: ../../source/programs/pct2rgb.rst:51 +msgid "" +"Extract the color table from <palette_file> instead of getting it from " +"<source_file>. Can be used to have a consistent color table for multiple " +"files. The <palette_file> must be either a raster file in a GDAL " +"supported format with a palette or a color file in a supported format " +"(txt, qml, qlr)." +msgstr "" + +#: ../../source/programs/pct2rgb.rst:64 +msgid "" +"The '-expand rgb|rgba' option of :ref:`gdal_translate` obsoletes that " +"utility." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:5 +msgid "Common options for raster programs" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:7 +msgid "All GDAL command line programs support the following common options." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:11 +#: ../../source/programs/vector_common_options.rst:11 +msgid "Report the version of GDAL and exit." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:15 +#: ../../source/programs/vector_common_options.rst:15 +msgid "Report detailed information about GDAL in use." +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:3 +msgid "" +"List all raster formats supported by this GDAL build (read-only and read-" +"write) and exit." +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:5 +msgid "The format support is indicated as follows:" +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:10 +msgid "" +"A ``v`` is appended for formats supporting virtual IO (/vsimem, /vsigzip," +" /vsizip, etc)." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:22 +msgid "" +"List detailed information about a single format driver. The format should" +" be the short name reported in the --formats list, such as GTiff." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:27 +msgid "" +"Read the named file and substitute the contents into the command line " +"options list. Lines beginning with # will be ignored. Multi-word " +"arguments may be kept together with double quotes. Multiple --optfiles " +"may be used: --optfile file1 --optfile file2..." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:32 +msgid "" +"Sets the named configuration keyword to the given value, as opposed to " +"setting them as environment variables. Some common configuration keywords" +" are :config:`GDAL_CACHEMAX` (memory used internally for caching in " +"megabytes) and :config:`GDAL_DATA` (path of the GDAL \"data\" directory)." +" Individual drivers may be influenced by other :ref:`configuration " +"options <list_config_options>`." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:36 +msgid "" +"Control what debugging messages are emitted. A value of ON will enable " +"all debug messages. A value of OFF will disable all debug messages. " +"Another value will select only debug messages containing that string in " +"the debug prefix code." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:40 +msgid "" +"Gives a brief usage message for the generic GDAL command line options and" +" exit." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:43 +msgid "Creating new files" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:45 +msgid "" +"Access an existing file to read it is generally quite simple. Just " +"indicate the name of the file or dataset on the command line. However, " +"creating a file is more complicated. It may be necessary to indicate the " +"format to create, various creation options affecting how it will be " +"created and perhaps a coordinate system to be assigned. Many of these " +"options are handled similarly by different GDAL utilities, and are " +"introduced here." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:55 +msgid "" +"Select the format to create the new file as. The formats are assigned " +"short names such as GTiff (for GeoTIFF) or HFA (for Erdas Imagine). The " +"list of all format codes can be listed with the :option:`--formats` " +"switch. Only formats list as ``(rw)`` (read-write) can be written." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:62 +msgid "" +"If not specified, the format is guessed from the extension. Previously, " +"it was generally GTiff for raster, or ESRI Shapefile for vector." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:71 +msgid "" +"Several utilities (e.g. :command:`gdal_translate` and " +":command:`gdalwarp`) include the ability to specify coordinate systems " +"with command line options like :option:`-a_srs` (assign SRS to output), " +":option:`-s_srs` (source SRS) and :option:`-t_srs` (target SRS). These " +"utilities allow the coordinate system (SRS = spatial reference system) to" +" be assigned in a variety of formats." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:77 +msgid "``NAD27|NAD83|WGS84|WGS72``" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:79 +msgid "" +"These common geographic (lat/long) coordinate systems can be used " +"directly by these names." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:82 +msgid "``EPSG:n``" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:84 +msgid "" +"Coordinate systems (projected or geographic) can be selected based on " +"their EPSG codes. For instance, :samp:`EPSG:27700` is the British " +"National Grid. A list of EPSG coordinate systems can be found in the GDAL" +" data files :file:`gcs.csv` and :file:`pcs.csv`." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:89 +msgid "``PROJ.4 definition``" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:91 +msgid "" +"A PROJ.4 definition string can be used as a coordinate system. Take care " +"to keep the proj.4 string together as a single argument to the command " +"(usually by double quoting)." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:95 +msgid "For instance :samp:`+proj=utm +zone=11 +datum=WGS84`." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:97 +msgid "``OpenGIS Well Known Text``" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:99 +msgid "" +"The Open GIS Consortium has defined a textual format for describing " +"coordinate systems as part of the Simple Features specifications. This " +"format is the internal working format for coordinate systems used in " +"GDAL. The name of a file containing a WKT coordinate system definition " +"may be used a coordinate system argument, or the entire coordinate system" +" itself may be used as a command line option (though escaping all the " +"quotes in WKT is quite challenging)." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:107 +msgid "``ESRI Well Known Text``" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:109 +msgid "" +"ESRI uses a slight variation on OGC WKT format in their ArcGIS product " +"(ArcGIS :file:`.prj` files), and these may be used in a similar manner o " +"WKT files, but the filename should be prefixed with ``ESRI::``." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:113 +msgid "For example, `\"ESRI::NAD 1927 StatePlane Wyoming West FIPS 4904.prj\"`." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:115 +msgid "``Spatial References from URLs``" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:117 +msgid "" +"For example http://spatialreference.org/ref/user/north-pacific-albers-" +"conic-equal-area/." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:119 +msgid ":file:`filename`" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:121 +msgid "" +"File containing WKT, PROJ.4 strings, or XML/GML coordinate system " +"definitions can be provided." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:5 +msgid "rgb2pct" +msgstr "" + +#: ../../source/programs/rgb2pct.rst:9 +msgid "Convert a 24bit RGB image to 8bit paletted." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:24 +msgid "" +"This utility will compute an optimal pseudo-color table for a given RGB " +"image using a median cut algorithm on a downsampled RGB histogram. Then" +" it converts the image into a pseudo-colored image using the color table." +" This conversion utilizes Floyd-Steinberg dithering (error diffusion) to " +"maximize output image visual quality." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:32 +msgid "" +"rgb2pct is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:40 +msgid "" +"Select the number of colors in the generated color table. Defaults to " +"256. Must be between 2 and 256." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:45 +msgid "" +"Extract the color table from <palette_file> instead of computing it. Can " +"be used to have a consistent color table for multiple files. The " +"<palette_file> must be either a raster file in a GDAL supported format " +"with a palette or a color file in a supported format (txt, qml, qlr)." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:52 +msgid "" +"Select the output format. Starting with GDAL 2.3, if not specified, the " +"format is guessed from the extension (previously was GTiff). Use the " +"short format name. Only output formats supporting pseudo-color tables " +"should be used." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:59 +msgid "The input RGB file." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:63 +msgid "The output pseudo-colored file that will be created." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:68 +msgid "" +"If it is desired to hand create the palette, likely the simplest text " +"format is the GDAL VRT format. In the following example a VRT was " +"created in a text editor with a small 4 color palette with the RGBA " +"colors 238/238/238/255, 237/237/237/255, 236/236/236/255 and " +"229/229/229/255." +msgstr "" + +#: ../../source/programs/sozip.rst:5 +msgid "sozip" +msgstr "" + +#: ../../source/programs/sozip.rst:11 +msgid "Generate a seek-optimized ZIP (SOZip) file." +msgstr "" + +#: ../../source/programs/sozip.rst:38 +msgid "The :program:`sozip` utility can be used to:" +msgstr "" + +#: ../../source/programs/sozip.rst:40 +msgid "create a :ref:`sozip_intro` file" +msgstr "" + +#: ../../source/programs/sozip.rst:41 +msgid "append files to an existing ZIP/SOZip file" +msgstr "" + +#: ../../source/programs/sozip.rst:42 +msgid "list the contents of a ZIP/SOZip file" +msgstr "" + +#: ../../source/programs/sozip.rst:43 +msgid "validate a SOZip file" +msgstr "" + +#: ../../source/programs/sozip.rst:44 +msgid "convert an existing Zip file in a SOZip optimized one" +msgstr "" + +#: ../../source/programs/sozip.rst:53 +msgid "Quiet mode. No progress message is emitted on the standard output." +msgstr "" + +#: ../../source/programs/sozip.rst:57 +msgid "Verbose mode." +msgstr "" + +#: ../../source/programs/sozip.rst:62 +msgid "" +"Grow an existing zip file with the content of the specified filename(s). " +"This is the default mode of the utility. This switch is here for " +"compatibility with Info-ZIP :program:`zip` utility" +msgstr "" + +#: ../../source/programs/sozip.rst:68 +msgid "Overwrite the target zip file if it already exists." +msgstr "" + +#: ../../source/programs/sozip.rst:73 +msgid "" +"List the files contained in the zip file in an output similar to Info-ZIP" +" :program:`unzip` utility, but with the addition of a column indicating " +"whether each file is seek-optimized." +msgstr "" + +#: ../../source/programs/sozip.rst:79 +msgid "" +"Validates a SOZip file. Baseline ZIP validation is done in a light way, " +"limited to being able to browse through ZIP records with the InfoZIP-" +"based ZIP reader used by GDAL. But validation of the SOZip-specific " +"aspects is done in a more thoroughful way." +msgstr "" + +#: ../../source/programs/sozip.rst:87 +msgid "" +"Travels the directory structure of the specified directory/directories " +"recursively." +msgstr "" + +#: ../../source/programs/sozip.rst:92 +msgid "" +"Store just the name of a saved file (junk the path), and do not store " +"directory names. By default, sozip will store the full path (relative to " +"the current directory)." +msgstr "" + +#: ../../source/programs/sozip.rst:98 +msgid "" +"Re-process {input.zip} to generate a SOZip-optimized .zip. Options " +":option:`--enable-sozip`, :option:`--sozip-chunk-size` and :option" +":`--sozip-min-file-size` may be used in that mode." +msgstr "" + +#: ../../source/programs/sozip.rst:104 +msgid "" +"In ``auto`` mode, a file is seek-optimized only if its size is above the " +"value of :option:`--sozip-chunk-size`. In ``yes`` mode, all input files " +"will be seek-optimized. In ``no`` mode, no input files will be seek-" +"optimized." +msgstr "" + +#: ../../source/programs/sozip.rst:111 +msgid "" +"Chunk size for a seek-optimized file. Defaults to 32768 bytes. The value " +"is specified in bytes, or K and M suffix can be respectively used to " +"specify a value in kilo-bytes or mega-bytes." +msgstr "" + +#: ../../source/programs/sozip.rst:117 +msgid "" +"Minimum file size to decide if a file should be seek-optimized, in " +"--enable-sozip=auto mode. Defaults to 1 MB byte. The value is specified " +"in bytes, or K, M or G suffix can be respectively used to specify a value" +" in kilo-bytes, mega-bytes or giga-bytes." +msgstr "" + +#: ../../source/programs/sozip.rst:124 +msgid "" +"Store the Content-Type for the file being added as a key-value pair in " +"the extra field extension 'KV' (0x564b) dedicated to storing key-value " +"pair metadata" +msgstr "" + +#: ../../source/programs/sozip.rst:129 +msgid "Filename of the zip file to create/append to/list." +msgstr "" + +#: ../../source/programs/sozip.rst:133 +msgid "Filename of the file to add." +msgstr "" + +#: ../../source/programs/sozip.rst:139 +msgid "" +"The :config:`GDAL_NUM_THREADS` configuration option can be set to " +"``ALL_CPUS`` or a integer value to specify the number of threads to use " +"for SOZip-compressed files. Defaults to ``ALL_CPUS``." +msgstr "" + +#: ../../source/programs/sozip.rst:146 +msgid "" +"Functionality of this utility can be done from C with " +":cpp:func:`CPLAddFileInZip` or :cpp:func:`VSICopyFile`." +msgstr "" + +#: ../../source/programs/sozip.rst:152 +msgid "" +"Create a, potentially seek-optimized, ZIP file with the content of " +"my.gpkg:" +msgstr "" + +#: ../../source/programs/sozip.rst:159 +msgid "" +"Create a, potentially seek-optimized, ZIP file from the content of a " +"source directory:" +msgstr "" + +#: ../../source/programs/sozip.rst:167 +msgid "Create a, potentially seek-optimized, ZIP file from an existing ZIP file." +msgstr "" + +#: ../../source/programs/sozip.rst:174 +msgid "" +"List the contents of a ZIP file and display which files are seek-" +"optimized:" +msgstr "" + +#: ../../source/programs/sozip.rst:181 +msgid "Validates a SOZip file:" +msgstr "" + +#: ../../source/programs/vector_common_options.rst:5 +msgid "Common options for vector programs" +msgstr "" + +#: ../../source/programs/vector_common_options.rst:7 +msgid "All GDAL OGR command line programs support the following common options." +msgstr "" + +#: ../../source/programs/vector_common_options.rst:21 +msgid "" +"List detailed information about a single format driver. The format should" +" be the short name reported in the :option:`--formats` list, such as GML." +msgstr "" + +#: ../../source/programs/vector_common_options.rst:27 +msgid "" +"Read the named file and substitute the contents into the command line " +"options list. Lines beginning with ``#`` will be ignored. Multi-word " +"arguments may be kept together with double quotes." +msgstr "" + +#: ../../source/programs/vector_common_options.rst:33 +msgid "" +"Sets the named configuration keyword to the given value, as opposed to " +"setting them as environment variables. Some common configuration keywords" +" are :config:`SHAPE_ENCODING` (force shapefile driver to read DBF files " +"with the given character encoding) and :config:`CPL_TMPDIR` (define the " +"location of temporary files). Individual drivers may be influenced by " +"other :ref:`configuration options <list_config_options>`." +msgstr "" + +#: ../../source/programs/vector_common_options.rst:41 +msgid "" +"Control what debugging messages are emitted. A value of ON will enable " +"all debug messages. A value of OFF will disable all debug messages. " +"Otherwise, a debug message will be emitted if its category appears " +"somewhere in the value string." +msgstr "" + +#: ../../source/programs/vector_common_options.rst:49 +msgid "" +"Gives a brief usage message for the generic GDAL OGR command line options" +" and exit." +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/software_using_gdal.po b/doc/source/locale/en/LC_MESSAGES/software_using_gdal.po new file mode 100644 index 000000000000..9ea6db781070 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/software_using_gdal.po @@ -0,0 +1,731 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: en\n" +"Language-Team: en <LL@li.org>\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/software_using_gdal.rst:5 +msgid "Software using GDAL" +msgstr "" + +#: ../../source/software_using_gdal.rst:8 +msgid "Free and open source" +msgstr "" + +#: ../../source/software_using_gdal.rst:10 +msgid "" +"`actinia <https://actinia.mundialis.de/>`_ A cloud based geoprocessing " +"platform from mundialis (GPL v3)" +msgstr "" + +#: ../../source/software_using_gdal.rst:11 +msgid "" +"`Biodiverse <http://shawnlaffan.github.io/biodiverse>`_ A tool for the " +"spatial analysis of diversity. Uses GDAL for import/export of data (GPL " +"v3)" +msgstr "" + +#: ../../source/software_using_gdal.rst:12 +msgid "" +"`Bluemapia <https://sourceforge.net/projects/bluemapia/>`_ Multi-" +"Map(Google,Microsoft,Open Street Map, NOAA/BSB Charts,self-calibrated " +"raster) location-based GPS app for Windows Mobile. (GPL v2)" +msgstr "" + +#: ../../source/software_using_gdal.rst:13 +msgid "" +"`BRL-CAD <https://brlcad.org>`_ An open source solid modeling computer-" +"aided design system." +msgstr "" + +#: ../../source/software_using_gdal.rst:14 +msgid "" +"`Demeter <http://demeter.sourceforge.net/>`_ Another OpenGL based terrain" +" engine somewhat similar to VTP." +msgstr "" + +#: ../../source/software_using_gdal.rst:15 +msgid "" +"`EOxServer <http://eoxserver.org>`_ OGC-compliant server for Earth " +"Observation (EO) data supporting WMS and WCS with EO application profiles" +" (EOxServer Open License)" +msgstr "" + +#: ../../source/software_using_gdal.rst:16 +msgid "" +"`exactextract <https://github.com/isciences/exactextract>`_ Fast and " +"accurate raster/vector zonal statistics (Apache 2.0)" +msgstr "" + +#: ../../source/software_using_gdal.rst:17 +msgid "" +"`Feature Data Objects (FDO) <http://fdo.osgeo.org>`_ Open source " +"spatial data access libraries (LGPL)" +msgstr "" + +#: ../../source/software_using_gdal.rst:18 +msgid "" +"`Fiona <http://pypi.python.org/pypi/Fiona>`_ Fiona is OGR's neater " +"Python API – sleek and elegant on the outside, indomitable power on the " +"inside." +msgstr "" + +#: ../../source/software_using_gdal.rst:19 +msgid "" +"`gdal3.js.org <https://gdal3.js.org>`_ Convert raster and vector " +"geospatial data to various formats and coordinate systems entirely in the" +" browser." +msgstr "" + +#: ../../source/software_using_gdal.rst:20 +msgid "" +"`GdalToTiles <http://www.codeplex.com/gdal2tilescsharp>`_ C# Program " +"(open source) for making image tiles for Google Earth with KML " +"Superoverlay." +msgstr "" + +#: ../../source/software_using_gdal.rst:21 +msgid "" +"`GeoDa <http://geodacenter.github.io/index.html>`_ Introduction to " +"Spatial Data Analysis (spatial autocorrelation and spatial regression) " +"(GPL)" +msgstr "" + +#: ../../source/software_using_gdal.rst:22 +msgid "" +"`GeoDjango <https://docs.djangoproject.com/en/dev/ref/contrib/gis/>`_ A" +" framework for building geographic web applications." +msgstr "" + +#: ../../source/software_using_gdal.rst:23 +msgid "" +"`GeoKettle " +"<https://live.osgeo.org/archive/10.0/en/overview/geokettle_overview.html>`_" +" An open source spatial ETL (Extract, Transform and Load) tool (LGPL)" +msgstr "" + +#: ../../source/software_using_gdal.rst:24 +msgid "" +"`GeoNotebook <https://github.com/OpenGeoscience/geonotebook>`_ a " +"Jupyter notebook extension for geospatial visualization and analysis. " +"(Apache 2.0)" +msgstr "" + +#: ../../source/software_using_gdal.rst:25 +msgid "" +"`GeoServer <http://geoserver.org>`_ a open source software server " +"written in Java that allows users to share and edit geospatial data." +msgstr "" + +#: ../../source/software_using_gdal.rst:26 +msgid "" +"`GMT (Generic Mapping Tools) <http://gmt.soest.hawaii.edu>`_ an open " +"source collection of tools for processing and displaying xy and xyz " +"datasets." +msgstr "" + +#: ../../source/software_using_gdal.rst:27 +msgid "" +"`GRASS GIS <http://grass.osgeo.org>`_ A raster/vector open source GIS " +"that uses GDAL for raster/vector import and export (via " +"r.in.gdal/r.out.gdal)" +msgstr "" + +#: ../../source/software_using_gdal.rst:28 +msgid "`gstat <http://www.gstat.org>`_ a geostatistical modelling package." +msgstr "" + +#: ../../source/software_using_gdal.rst:29 +msgid "" +"`GuidosToolbox " +"<https://forest.jrc.ec.europa.eu/en/activities/lpa/gtb/>`_ A multi-" +"platform desktop application for generic image object analysis." +msgstr "" + +#: ../../source/software_using_gdal.rst:30 +msgid "`gvSIG <http://www.gvsig.com>`_ Desktop GIS Client." +msgstr "" + +#: ../../source/software_using_gdal.rst:31 +msgid "" +"`ILWIS <http://www.itc.nl/ilwis>`_ Remote Sensing and GIS Desktop " +"Package." +msgstr "" + +#: ../../source/software_using_gdal.rst:32 +msgid "" +"`Image I/O-Ext <https://github.com/geosolutions-it/imageio-ext>`_ " +"includes gdalframework, a framework leveraging on GDAL via SWIG's " +"generated JAVA bindings to provide support for a broad set of data " +"formats." +msgstr "" + +#: ../../source/software_using_gdal.rst:33 +msgid "" +"`libLAS <https://liblas.org>`_ Open Source LAS 1.0/1.1 ASPRS LiDAR data" +" translation toolset" +msgstr "" + +#: ../../source/software_using_gdal.rst:34 +msgid "" +"`Loader <https://github.com/AstunTechnology/Loader>`_ A simple loader " +"for geographic data in GML and KML that needs some preparation before " +"loading via ogr2ogr." +msgstr "" + +#: ../../source/software_using_gdal.rst:35 +msgid "`MapGuide <http://mapguide.osgeo.org>`_ Open source web mapping server." +msgstr "" + +#: ../../source/software_using_gdal.rst:36 +msgid "`Mapnik <http://mapnik.org>`_ C++/ Python mapping toolkit" +msgstr "" + +#: ../../source/software_using_gdal.rst:37 +msgid "" +"`MapServer <http://mapserver.org/index.html>`_ A popular web mapping " +"application with GDAL support." +msgstr "" + +#: ../../source/software_using_gdal.rst:38 +msgid "" +"`MapWindow <http://www.mapwindow.org>`_ open source ActiveX control " +"with GIS functionality." +msgstr "" + +#: ../../source/software_using_gdal.rst:39 +msgid "" +"`MultiSpec <https://github.com/larrybiehl/MultiSpec>`_ Application for " +"interactively analyzing multispectral/hyperspectral image data." +msgstr "" + +#: ../../source/software_using_gdal.rst:40 +msgid "" +"`NASA Ames Stereo Pipeline " +"<https://github.com/NeoGeographyToolkit/StereoPipeline>`_ Software for " +"creating terrain models and ortho images from planetary stereo images. " +"(Apache 2.0)" +msgstr "" + +#: ../../source/software_using_gdal.rst:41 +msgid "" +"`NASA WorldWind <https://worldwind.arc.nasa.gov/>`_ Multiplatform " +"virtual globe library to quickly and easily create interactive " +"visualizations of 3D globes, map and geographical information." +msgstr "" + +#: ../../source/software_using_gdal.rst:42 +msgid "" +"`NextGIS Formbuilder <http://nextgis.com/nextgis-formbuilder>`_ Desktop " +"application for creating and editing forms." +msgstr "" + +#: ../../source/software_using_gdal.rst:43 +msgid "" +"`NextGIS Web <http://nextgis.com/nextgis-web>`_ Server-side Web GIS and " +"a framework for storage, visualization and permissions management of all " +"kinds" +msgstr "" + +#: ../../source/software_using_gdal.rst:44 +msgid "" +"`Ogr2 GUI <https://sourceforge.net/projects/ogr2gui/>`_ Graphical user " +"interface for ogr2ogr" +msgstr "" + +#: ../../source/software_using_gdal.rst:45 +msgid "" +"`OpenCPN <http://opencpn.org>`_ A concise ChartPlotter/Navigator. A " +"cross-platform ship-borne GUI application." +msgstr "" + +#: ../../source/software_using_gdal.rst:46 +msgid "" +"`OpenEV <http://openev.sourceforge.net>`_ An OpenGL/GTK/Python based " +"graphical viewer which exclusively uses GDAL for raster access." +msgstr "" + +#: ../../source/software_using_gdal.rst:47 +msgid "" +"`OFGT <https://github.com/openforis/geospatial-toolkit>`_ a collection " +"of utilities for multipurpose forest monitoring under the `Open Foris " +"Initiative <http://km.fao.org/OFwiki/index.php/Main_Page>`_ Open Foris " +"Initiative." +msgstr "" + +#: ../../source/software_using_gdal.rst:48 +msgid "" +"`OpenFLUID <https://www.openfluid-project.org>`_ a software platform " +"for spatial modelling of landscapes dynamics" +msgstr "" + +#: ../../source/software_using_gdal.rst:49 +msgid "" +"`OpenSceneGraph <http://www.openscenegraph.org>`_ 3D rendering engine " +"with `osgdem " +"<http://www.openscenegraph.org/projects/osg/wiki/Support/UserGuides/osgdem>`_" +" and `osgEarth <http://wush.net/trac/osgearth/wiki/Downloads>`_ plugins." +msgstr "" + +#: ../../source/software_using_gdal.rst:50 +msgid "" +"`Opticks <http://opticks.org>`_ an open source remote sensing " +"application and development framework, with a GDAL plugin." +msgstr "" + +#: ../../source/software_using_gdal.rst:51 +msgid "" +"`Orfeo Toolbox (OTB) <http://www.orfeo-toolbox.org>`_ a general remote " +"sensing image processing library." +msgstr "" + +#: ../../source/software_using_gdal.rst:52 +msgid "" +"`OSSIM <http://www.ossim.org>`_ Another geospatial viewing and analysis" +" environment which uses GDAL as one of several plugins." +msgstr "" + +#: ../../source/software_using_gdal.rst:53 +msgid "`PDAL <https://pdal.io>`_ Point Cloud Data Abstraction Library" +msgstr "" + +#: ../../source/software_using_gdal.rst:54 +msgid "" +"`pktools <http://pktools.nongnu.org/html/index.html>`_ open source " +"(GPLv3) tools written in C++ for remote sensing image processing" +msgstr "" + +#: ../../source/software_using_gdal.rst:55 +msgid "" +"`PNMapcalc <http://pawel.netzel.pl/index.php?id=software#a_mapcalc>`_ A" +" raster map calculator with C-like scripting language." +msgstr "" + +#: ../../source/software_using_gdal.rst:56 +msgid "" +"`PostGIS <http://www.postgis.net>`_ spatial database extender for " +"PostgreSQL: The raster loader and many of the raster SQL functions rely " +"on GDAL." +msgstr "" + +#: ../../source/software_using_gdal.rst:57 +msgid "" +"`PostgreSQL OGR Foreign Data Wrapper <https://github.com/pramsey/pgsql-" +"ogr-fdw>`_ Expose OGR layer as PostgreSQL foreign tables." +msgstr "" + +#: ../../source/software_using_gdal.rst:58 +msgid "`QGIS <http://www.qgis.org>`_ A cross platform desktop GIS." +msgstr "" + +#: ../../source/software_using_gdal.rst:59 +msgid "" +"`R <http://www.r-project.org>`_ A free software environment for " +"statistical computing and graphics, with bindings to GDAL via the rgdal " +"package." +msgstr "" + +#: ../../source/software_using_gdal.rst:60 +msgid "" +"`Rasterio <https://rasterio.readthedocs.io>`_ Python library and " +"command line utilities to read and write GDAL rasters." +msgstr "" + +#: ../../source/software_using_gdal.rst:61 +msgid "" +"`Rasterix <https://github.com/mogasw/rasterix/>`_ A cross platform open" +" source utility to process raster data based on Qt and GDAL." +msgstr "" + +#: ../../source/software_using_gdal.rst:62 +msgid "" +"`SAGA GIS <http://www.saga-gis.org/en/index.html>`_ A free geographic " +"information system (GIS), with a special 'Application Programming " +"Interface' (API) for geographic data processing." +msgstr "" + +#: ../../source/software_using_gdal.rst:63 +msgid "" +"`SNAP <http://step.esa.int/main/toolboxes/snap>`_ Sentinel Application " +"Platform for Earth Observation processing and analysis." +msgstr "" + +#: ../../source/software_using_gdal.rst:64 +msgid "" +"`StarSpan <https://github.com/Ecotrust/starspan>`_ raster/vector " +"analysis." +msgstr "" + +#: ../../source/software_using_gdal.rst:65 +msgid "" +"`t-rex <http://t-rex.tileserver.ch>`_ Vector tile server written in " +"Rust." +msgstr "" + +#: ../../source/software_using_gdal.rst:66 +msgid "" +"`Thuban <http://thuban.intevation.org>`_ A multi-platform interactive " +"geographic data viewer." +msgstr "" + +#: ../../source/software_using_gdal.rst:67 +msgid "" +"`Vertual Terrain Project <http://www.vterrain.org>`_ fostering tools " +"for easy construction of the real world in interactive, 3D digital form." +msgstr "" + +#: ../../source/software_using_gdal.rst:68 +msgid "" +"`ViRGiS <https://www.virgis.org/>`__ Creating a GIS Platform in Virtual " +"Reality / Mixed Reality" +msgstr "" + +#: ../../source/software_using_gdal.rst:71 +msgid "Proprietary license / Other" +msgstr "" + +#: ../../source/software_using_gdal.rst:73 +msgid "" +"`3D DEM Viewer <http://www.msmacrosystem.nl/Ilwis/index.html>`_ from MS " +"MacroSystem." +msgstr "" + +#: ../../source/software_using_gdal.rst:74 +msgid "" +"`Cadcorp SIS: <http://www.cadcorp.com>`_ A Windows GIS with a GDAL and " +"OGR plugins." +msgstr "" + +#: ../../source/software_using_gdal.rst:75 +msgid "" +"`Carmenta Engine <http://www.carmenta.com>`_ (previously known as " +"SpatialAce): A GIS Rapid Application Development environment" +msgstr "" + +#: ../../source/software_using_gdal.rst:76 +msgid "" +"`CARTO <http://www.carto.com>`_ A cloud mapping platform to analyze and " +"visualize geospatial data." +msgstr "" + +#: ../../source/software_using_gdal.rst:77 +msgid "`Cartographica <http://www.macgis.com>`_ Macintosh GIS package." +msgstr "" + +#: ../../source/software_using_gdal.rst:78 +msgid "" +"`CatchmentSIM <https://csse.com.au/index.php/products/catchmentsim>`_ A " +"Windows terrain analysis model for hydrologic applications." +msgstr "" + +#: ../../source/software_using_gdal.rst:79 +msgid "" +"`Daylon Leveller <https://www.daylongraphics.com/products/leveller.php>`_" +" A terrain/heightfield/bumpmap modeler" +msgstr "" + +#: ../../source/software_using_gdal.rst:80 +msgid "" +"`Eonfusion <http://www.eonfusion.com>`_ Analysis and visualization of " +"time-varying spatial datasets integrated via true data fusion." +msgstr "" + +#: ../../source/software_using_gdal.rst:81 +msgid "" +"`ERDAS ER Viewer <https://www.hexagongeospatial.com/products/power-" +"portfolio/other-producer-products/erdas-er-viewer>`_ Image viewer for " +"very large JPEG 2000 and ECW files." +msgstr "" + +#: ../../source/software_using_gdal.rst:82 +msgid "`ESRI ArcGIS 9.2+ <http://www.esri.com>`_ A popular GIS platform." +msgstr "" + +#: ../../source/software_using_gdal.rst:83 +msgid "" +"`Eternix Blaze <http://www.eternix.co.il>`_ Advanced geo-spatial " +"visualization application and SDK." +msgstr "" + +#: ../../source/software_using_gdal.rst:84 +msgid "" +"`FalconView <http://www.falconview.org>`_ Windows-based GIS platform " +"with roots in military mission planning, now available as a free GIS " +"visualization and analysis package." +msgstr "" + +#: ../../source/software_using_gdal.rst:85 +msgid "" +"`flighttrack <http://flighttrack.sourceforge.net>`_ GPS track viewing " +"and downloading software for Mac." +msgstr "" + +#: ../../source/software_using_gdal.rst:86 +msgid "" +"`FME <http://www.safe.com>`_ A GIS translator package includes a GDAL " +"plugin." +msgstr "" + +#: ../../source/software_using_gdal.rst:87 +msgid "" +"`GenGIS <http://kiwi.cs.dal.ca/GenGIS>`_ Software for geospatial " +"analysis of genetic data." +msgstr "" + +#: ../../source/software_using_gdal.rst:88 +msgid "" +"`Geographic Imager <https://www.avenza.com/geographic-imager>`_ DEM / " +"aerial / satellite image processing GIS plug-in for Adobe Photoshop, by " +"Avenza Systems." +msgstr "" + +#: ../../source/software_using_gdal.rst:89 +msgid "" +"`GeoDMS <http://www.objectvision.hosting.it-rex.nl/geodms>`_ A " +"framework for building spatial calculation models." +msgstr "" + +#: ../../source/software_using_gdal.rst:90 +msgid "`GeoFusion <http://www.geofusion.com>`_ 3D visualization." +msgstr "" + +#: ../../source/software_using_gdal.rst:91 +msgid "" +"`GeoView Pro <https://apps.apple.com/lu/app/geoview-" +"pro/id590559352?l=fr>`_ IOS mobile mapping application." +msgstr "" + +#: ../../source/software_using_gdal.rst:92 +msgid "" +"`Geoweb3d <http://www.geoweb3d.com>`_ A 3D virtual globe that provides " +"on-the-fly, game-quality visualization of GIS data." +msgstr "" + +#: ../../source/software_using_gdal.rst:93 +msgid "`Google Earth <http://earth.google.com>`_ A 3D world viewer." +msgstr "" + +#: ../../source/software_using_gdal.rst:94 +msgid "" +"`GPSeismic <http://www.gpseismic.com>`_ A suite of applications for " +"seismic survey." +msgstr "" + +#: ../../source/software_using_gdal.rst:95 +msgid "" +"`HydroDaVE Explorer <http://www.hydrodave.com>`_ A web-enabled client " +"that provides users an easy to use, secure, and reliable data management " +"platform to efficiently manage, access, and analyze environmental data." +msgstr "" + +#: ../../source/software_using_gdal.rst:96 +msgid "" +"`IDRISI <http://www.idrisi.com>`_ A GIS and Image Processing Windows " +"Desktop application. Uses GDAL to import/export/warp raster data." +msgstr "" + +#: ../../source/software_using_gdal.rst:97 +msgid "" +"`Infraworks <https://www.autodesk.com/products/infraworks/overview>`_ a" +" BIM software for infrastructure project design, part of the Autodesk " +"suite." +msgstr "" + +#: ../../source/software_using_gdal.rst:98 +msgid "" +"`iShare <https://www.astuntechnology.com/cloud-products/ishare/>`_ Web " +"data integration and publishing platform by Astun Technology." +msgstr "" + +#: ../../source/software_using_gdal.rst:99 +msgid "" +"`Makai Voyager <http://voyager.makai.com>`_ An advanced 3D/4D " +"geospatial visualization platform." +msgstr "" + +#: ../../source/software_using_gdal.rst:100 +msgid "" +"`MapInfo Professional <http://www.mapinfo.com/product/mapinfo-" +"professional>`_ Desktop GIS and mapping application" +msgstr "" + +#: ../../source/software_using_gdal.rst:101 +msgid "" +"`MapTiler <http://www.maptiler.com>`_ Generator of tiles for " +"interactive maps and overlays made from raster images and geodata." +msgstr "" + +#: ../../source/software_using_gdal.rst:102 +msgid "" +"`Maptitude Mapping Software " +"<http://www.caliper.com/maptitude/mappingsoftware.htm>`_ Desktop GIS and" +" business mapping application" +msgstr "" + +#: ../../source/software_using_gdal.rst:103 +msgid "" +"`MicroImages TNT <http://www.microimages.com>`_ advanced software for " +"geospatial analysis (Windows, Linux, Mac OS X and UNIX)" +msgstr "" + +#: ../../source/software_using_gdal.rst:104 +msgid "" +"`Micromine <http://www.micromine.com>`_ A mining software solution that" +" uses GDAL for reading/writing various geospatial file formats." +msgstr "" + +#: ../../source/software_using_gdal.rst:105 +msgid "" +"`Mirone <http://joa-quim.pt/mirone/main.html>`_ Matlab based package " +"for geospatial, oceanographic and geophysical analysis of grids" +msgstr "" + +#: ../../source/software_using_gdal.rst:106 +msgid "" +"`Mygeodata Converter " +"<http://mygeodata.eu/apps/converter/index_EN.html>`_ Online converter of" +" GDAL raster and OGR vector formats" +msgstr "" + +#: ../../source/software_using_gdal.rst:107 +msgid "" +"`OPALS <https://opals.geo.tuwien.ac.at/html/stable/index.html>`_ " +"Orientation and Processing of Airborne Laser Scanning Data" +msgstr "" + +#: ../../source/software_using_gdal.rst:108 +msgid "" +"`Procura <http://www.michellcomputing.co.uk/procura.html>`_ Landholding " +"inspection system developed for the UK Homes and Communities Agency. GDAL" +" is used for checking out background mapping." +msgstr "" + +#: ../../source/software_using_gdal.rst:109 +msgid "" +"`ScanMagic " +"<https://www.scanex.ru/en/software/vizualizatsiya-i-katalogizatsiya/scan-" +"magic/>`_ Win32 application for visualization, analysis and processing of" +" remote sensing data." +msgstr "" + +#: ../../source/software_using_gdal.rst:110 +msgid "" +"`Scalable Algorithmics (SCALGO) <http://scalgo.com>`_ Software for " +"efficiently constructing and performing computations on very large raster" +" and TIN terrain models." +msgstr "" + +#: ../../source/software_using_gdal.rst:111 +msgid "" +"`Scenomics <http://www.scenomics.com>`_ Software for building terrain " +"databases uses GDAL for projection and data import/export." +msgstr "" + +#: ../../source/software_using_gdal.rst:112 +msgid "" +"`scenProc <http://www.scenerydesign.org/scenproc>`_ scenProc: A tool to " +"create scenery for Microsoft Flight Simulator and Lockheed Martin " +"Prepar3D by processing G" +msgstr "" + +#: ../../source/software_using_gdal.rst:113 +msgid "" +"`SeaView <https://www.seaviewgis.com>`_ A 3D GIS package for " +"geophysical and hydrographical data (side scan sonar, subbottom profiler," +" magnetometer, multibeam, etc." +msgstr "" + +#: ../../source/software_using_gdal.rst:114 +msgid "" +"`SkylineGlobe <http://www.skylineglobe.com>`_ The Skyline suite of " +"interactive applications allows you to build, view, query and analyze " +"customized, virtual 3D landscapes." +msgstr "" + +#: ../../source/software_using_gdal.rst:115 +msgid "" +"`SpacEyes3D <http://www.spaceyes.com>`_ 3D visualization software for " +"cartographic data." +msgstr "" + +#: ../../source/software_using_gdal.rst:116 +msgid "" +"`Spatial Manager <http://www.spatialmanager.com>`_ A product suite " +"designed designed to manage spatial data in a simple, fast and " +"inexpensive way. Uses GDAL to import/export data." +msgstr "" + +#: ../../source/software_using_gdal.rst:117 +msgid "" +"`TacitView <https://www.insitu.com/information-delivery/information-" +"processing/tacitview>`_ An imagery visualization and exploitation " +"package for military intelligence." +msgstr "" + +#: ../../source/software_using_gdal.rst:118 +msgid "" +"`TatukGIS <http://www.tatukgis.com>`_ Desktop GIS mapping and data " +"editing application." +msgstr "" + +#: ../../source/software_using_gdal.rst:119 +msgid "" +"`Team Awareness Kit <https://tak.gov>`_ Suite of georeferenced imagery " +"and situational awareness tools developed for military planning and " +"execution, now available for civilian use." +msgstr "" + +#: ../../source/software_using_gdal.rst:120 +msgid "" +"`TerraGo Technologies <http://www.terragotech.com>`_ The GeoPDF file " +"format is used to distribute and collaborate geospatial data and uses " +"GDAL for data import/export." +msgstr "" + +#: ../../source/software_using_gdal.rst:121 +msgid "" +"`TerrainView <http://www.viewtec.net>`_ Interactive real-time 3D GIS " +"Software." +msgstr "" + +#: ../../source/software_using_gdal.rst:122 +msgid "" +"`TransCAD GIS <http://www.caliper.com>`_ Desktop Transportation " +"Analysis Software" +msgstr "" + +#: ../../source/software_using_gdal.rst:123 +msgid "" +"`TravTime <https://travtime.software.informer.com/download/>`_ .NET " +"Application for visualizing, processing and analyzing GPS data for travel" +" time, speed, and de" +msgstr "" + +#: ../../source/software_using_gdal.rst:124 +msgid "" +"`VectorWorks <http://www.vectorworks.net>`_ The Vectorworks line of " +"software products provides professional design solutions in the AEC, " +"entertainment and landscape design industries." +msgstr "" + +#: ../../source/software_using_gdal.rst:125 +msgid "" +"`WindNinja <https://www.firelab.org/project/windninja>`_ wind model for" +" fire behavior modeling." +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/sponsors.po b/doc/source/locale/en/LC_MESSAGES/sponsors.po new file mode 100644 index 000000000000..d503e804ce17 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/sponsors.po @@ -0,0 +1,312 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: en\n" +"Language-Team: en <LL@li.org>\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/sponsors/faq.rst:5 +msgid "Sponsoring FAQ" +msgstr "" + +#: ../../source/sponsors/faq.rst:8 +msgid "Why does GDAL need sponsorship?" +msgstr "" + +#: ../../source/sponsors/faq.rst:10 +msgid "" +"GDAL is the most central piece of `Critical Digital Infrastructure`_ in " +"the geospatial world, serving as the primary building block for data " +"management and processing in open source, commercial, and government " +"geospatial software. But most of its resources have gone to the " +"development of new features, while the maintenance burden has only " +"increased with more functionality." +msgstr "" + +#: ../../source/sponsors/faq.rst:18 +msgid "" +"The purpose of sponsor funding is to provide substantial long-acting " +"resources that give the project the ability to address software, testing," +" and project challenges that do not attract individual sponsorship " +"attention. With a pool of resources that are not earmarked for features, " +"it can attack usability, performance, and modernization challenges that " +"benefit everyone. Sustained funding enables multi-year efforts that do " +"not disrupt the existing GDAL user base, and it will provide the baseline" +" resources to allow day-to-day maintenance operations to continue " +"uninterrupted." +msgstr "" + +#: ../../source/sponsors/faq.rst:27 +msgid "" +"The larger funding levels enabled by sponsorship aim to help GDAL grow to" +" a team of maintainers, as is typical in other leading open source " +"projects. The past few years have seen only one maintainer, who has been " +"stretched thin. The resources provided by this effort allow maintenance " +"activities to continue *and* allow the project to support on-boarding " +"additional developers to tackle various needs of the project that have " +"been ignored due to lack of direct funding interest." +msgstr "" + +#: ../../source/sponsors/faq.rst:34 +msgid "My organization wants to sponsor. How can we do that?" +msgstr "" + +#: ../../source/sponsors/faq.rst:36 +msgid "" +"To learn about the benefits of becoming a sponsor at various levels start" +" with the `Sustainable GDAL Sponsorship Prospectus`_. If you are " +"interested, need help convincing your key decision-makers, or have any " +"questions, don't hesitate to contact gdal-sponsors@osgeo.org." +msgstr "" + +#: ../../source/sponsors/faq.rst:44 +msgid "" +"What is NumFOCUS and why is the project using that foundation rather than" +" using OSGeo for this effort?" +msgstr "" + +#: ../../source/sponsors/faq.rst:46 +msgid "" +"`NumFOCUS <https://numfocus.org>`__ is a US-based 501(c)(3) tax-exempt " +"non-profit that is already managing funding for many individual software " +"projects using this model such as Numpy, Jupyter, pandas, Julia, and " +"SciPy. They have staff, policies, procedures, and infrastructure for " +"managing the financial support of open source software projects with this" +" funding model. Many organizations in the initial list of sponsors are " +"already funding projects through NumFOCUS, and adding GDAL to the roster " +"improves efficiency on their side." +msgstr "" + +#: ../../source/sponsors/faq.rst:54 +msgid "" +"`OSGeo <https://www.osgeo.org>`__ does not have staff and procedures to " +"manage tracking workloads and payments. OSGeo also does not provide tax-" +"exempt status for contributions. NumFOCUS has established relationships " +"with a large number of the initial sponsors. These properties are why the" +" GDAL PSC has chosen the NumFOCUS path for management of this effort." +msgstr "" + +#: ../../source/sponsors/faq.rst:61 +msgid "So GDAL is a NumFOCUS project now?" +msgstr "" + +#: ../../source/sponsors/faq.rst:63 +msgid "" +"Not exactly. GDAL will be a project within NumFOCUS under the \"Grantor-" +"Grantee Model\". OSGeo is still the primary foundational \"home\" of GDAL" +" such as it is, but NumFOCUS is providing this financial vehicle and " +"service to the project under the purview of its charter." +msgstr "" + +#: ../../source/sponsors/faq.rst:69 +msgid "What is the project going to do with the money?" +msgstr "" + +#: ../../source/sponsors/faq.rst:71 +msgid "" +"The GDAL PSC will control the purse strings. Contributors seeking " +"resources will submit a proposal to the PSC (RFC-style, but not public) " +"describing the tasks and efforts they will seek to achieve. Any " +"substantial efforts with external impacts will continue to be required to" +" use the GDAL RFC process as described in :ref:`rfc-1`." +msgstr "" + +#: ../../source/sponsors/faq.rst:77 +msgid "" +"Developers will be able submit requests to the GDAL PSC for 'maintenance " +"work units', which could encompass ticket i/o and related code " +"improvements, CI grooming, mailing list gardening, and fuzzing response " +"activities." +msgstr "" + +#: ../../source/sponsors/faq.rst:81 +msgid "" +"A significant portion (25% per year if possible) of the resources will be" +" targeted toward *growing* new active developers into the project. " +"Examples of this include soliciting ticket and code contributors with " +"funding if they show interest and aptitude, and providing resources to " +"mentor and support junior developers who are working into roles in the " +"project. These activities are extremely hard to do without financial " +"support." +msgstr "" + +#: ../../source/sponsors/faq.rst:88 +msgid "" +"Spot resources will be available to attack needs that have difficulty " +"finding funded attention, such as API improvements in support of specific" +" application niches and subsystem refreshes like build, tests, and CI. " +"The GDAL PSC could fund significant RFCs that demonstrate need and " +"agreement on an ad hoc basis." +msgstr "" + +#: ../../source/sponsors/faq.rst:93 +msgid "" +"The GDAL PSC will delegate some resources to GDAL-related projects and " +"dependencies – libtiff, libgeotiff, PROJ, shapelib, and the various " +"language bindings and libraries. If more resources than the GDAL project " +"itself can use are available for a particular year, the project will open" +" them up to the wider community of related libraries and users to " +"repurpose them." +msgstr "" + +#: ../../source/sponsors/faq.rst:100 +msgid "How can the resources be used?" +msgstr "" + +#: ../../source/sponsors/faq.rst:102 +msgid "" +"The funds cannot be used to benefit an individual contributor or be " +"directed by a contributor through the non-profit organization. For " +"example, a fictional Imagery Corp cannot fund NumFOCUS with explicit " +"intent to have those resources used to fix bugs or add features that " +"benefit Imagery Corp. Imagery Corp can still continue to solicit GDAL " +"active contributors, or actively contribute the fixes themselves, to " +"achieve their goals with the software." +msgstr "" + +#: ../../source/sponsors/faq.rst:110 +msgid "How is this going to impact GDAL software releases?" +msgstr "" + +#: ../../source/sponsors/faq.rst:112 +msgid "" +"A primary goal of this effort is to provide resources needed to allow the" +" current GDAL maintainer to keep up the existing release schedule and " +"cadence. Without these resources, the schedule was likely to have " +"significantly stretched out to one or two maintenance releases per year." +msgstr "" + +#: ../../source/sponsors/faq.rst:119 +msgid "Can I use some of the funding to support fixing something?" +msgstr "" + +#: ../../source/sponsors/faq.rst:121 +msgid "" +"Quite possibly. The GDAL PSC will provide a proposal template where you " +"will need to describe the issue(s), propose the approach and impacts of " +"it, and state your cost to complete the effort." +msgstr "" + +#: ../../source/sponsors/index.rst:5 +msgid "Sponsors" +msgstr "" + +#: ../../source/sponsors/index.rst:7 +msgid "" +"GDAL is a truly collaborative effort, with many diverse organizations " +"contributing resources to its success. The following organizations take " +"an extra step, providing unrestricted funding every year to maintain and " +"improve the health of the project:" +msgstr "" + +#: ../../source/sponsors/index.rst:12 +msgid "Gold level:" +msgstr "" + +#: ../../source/sponsors/index.rst:47 +msgid "Silver level:" +msgstr "" + +#: ../../source/sponsors/index.rst:70 +msgid "Bronze level:" +msgstr "" + +#: ../../source/sponsors/index.rst:113 +msgid "Supporter level:" +msgstr "" + +#: ../../source/sponsors/index.rst:120 +msgid "Myles Sutherland" +msgstr "" + +#: ../../source/sponsors/index.rst:124 +msgid "`Dynamic Graphics, Inc. <https://www.dgi.com/>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:128 +msgid "`Kaplan Open Source Consulting <https://kaplanopensource.co.il/>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:132 +msgid "`PIX4D <https://www.pix4d.com/>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:136 +msgid "`Regrid <https://regrid.com>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:140 +msgid "`Satelligence <https://satelligence.com/>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:144 +msgid "`Space Intelligence <https://www.space-intelligence.com>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:148 +msgid "`Umbra <https://umbra.space/>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:152 +msgid "`Vortex f.d.c. <https://vortexfdc.com/>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:194 +msgid "" +"The GDAL Project is hosted by `OSGeo <https://www.osgeo.org>`__, and a " +"fiscally sponsored project of `NumFOCUS <https://numfocus.org>`__, a " +"nonprofit dedicated to supporting the open-source scientific computing " +"community. If you like GDAL and want to support our mission, please " +"consider making a `donation <https://numfocus.org/donate-to-gdal>`__ to " +"support our efforts." +msgstr "" + +#: ../../source/sponsors/index.rst:200 +msgid "" +"NumFOCUS is 501(c)(3) non-profit charity in the United States; as such, " +"donations to NumFOCUS are tax-deductible as allowed by law. As with any " +"donation, you should consult with your personal tax adviser or the IRS " +"about your particular tax situation." +msgstr "" + +#: ../../source/sponsors/index.rst:221 +msgid "Sponsoring" +msgstr "" + +#: ../../source/sponsors/index.rst:223 +msgid "" +"If your organization benefits from GDAL we recommend joining the group of" +" sponsors above to \"pay it forward\" and ensure the project has the " +"resources to stay healthy and grow. To learn about the benefits of " +"becoming a sponsor at various levels start with the `Sustainable GDAL " +"Sponsorship Prospectus`_. If you are interested, need help convincing " +"your key decision-makers, or have any questions, don't hesitate to " +"contact gdal-sponsors@osgeo.org." +msgstr "" + +#: ../../source/sponsors/index.rst:231 +msgid "Related resources" +msgstr "" + +#: ../../source/sponsors/index.rst:233 +msgid "`Sustainable GDAL Sponsorship Prospectus`_." +msgstr "" + +#: ../../source/sponsors/index.rst:234 +msgid ":ref:`Sponsoring frequently asked questions (FAQ) <sponsoring-faq>`." +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/tutorials.po b/doc/source/locale/en/LC_MESSAGES/tutorials.po new file mode 100644 index 000000000000..df3b8fde19db --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/tutorials.po @@ -0,0 +1,4534 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: en\n" +"Language-Team: en <LL@li.org>\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/tutorials/gdal_grid_tut.rst:5 +msgid "GDAL Grid Tutorial" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:8 +msgid "Introduction to Gridding" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:10 +msgid "" +"Gridding is a process of creating a regular grid (or call it a raster " +"image) from the scattered data. Typically you have a set of arbitrary " +"data scattered over the region of survey measurements and you would like " +"to convert them into the regular grid for further processing and " +"combining with other grids." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:-1 +msgid "Scattered data gridding" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:25 +msgid "" +"This problem can be solved using data interpolation or approximation " +"algorithms. But you are not limited by interpolation here. Sometimes you " +"don't need to interpolate your data but rather compute some statistics or" +" data metrics over the region. Statistics are valuable themselves or " +"could be used for better choosing the interpolation algorithm and " +"parameters." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:31 +msgid "" +"That is what GDAL Grid API is about. It helps you to interpolate your " +"data (see `Interpolation of the Scattered Data`_) or compute data metrics" +" (see `Data Metrics Computation`_)." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:35 +msgid "" +"There are two ways of using this interface. Programmatically it is " +"available through the :cpp:func:`GDALGridCreate` C function; for end " +"users there is a :ref:`gdal_grid` utility (which see for an up-to-date " +"list of all current features). The rest of this document discusses " +"details on algorithms and their parameters implemented in GDAL Grid API." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:42 +msgid "Interpolation of the Scattered Data" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:45 +msgid "Inverse Distance to a Power" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:47 +msgid "" +"The Inverse Distance to a Power gridding method is a weighted average " +"interpolator. You should supply the input arrays with the scattered data " +"values including coordinates of every data point and output grid " +"geometry. The function will compute an interpolated value for the given " +"position in the output grid." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:53 +msgid "" +"For every grid node the resulting value :math:`Z` will be calculated " +"using the formula:" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:56 +msgid "Z=\\frac{\\sum_{i=1}^n{\\frac{Z_i}{r_i^p}}}{\\sum_{i=1}^n{\\frac{1}{r_i^p}}}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:60 +#: ../../source/tutorials/gdal_grid_tut.rst:103 +#: ../../source/tutorials/gdal_grid_tut.rst:139 +#: ../../source/tutorials/gdal_grid_tut.rst:155 +#: ../../source/tutorials/gdal_grid_tut.rst:172 +msgid "where:" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:62 +#: ../../source/tutorials/gdal_grid_tut.rst:106 +#: ../../source/tutorials/gdal_grid_tut.rst:142 +#: ../../source/tutorials/gdal_grid_tut.rst:158 +#: ../../source/tutorials/gdal_grid_tut.rst:175 +msgid ":math:`Z_i` is a known value at point :math:`i`," +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:63 +msgid ":math:`r_i` is a distance from the grid node to point :math:`i`," +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:64 +msgid ":math:`p` is a weighting power," +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:65 +#: ../../source/tutorials/gdal_grid_tut.rst:143 +#: ../../source/tutorials/gdal_grid_tut.rst:159 +#: ../../source/tutorials/gdal_grid_tut.rst:176 +msgid ":math:`n` is a number of points in `Search Ellipse`_." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:67 +msgid "" +"The smoothing parameter :math:`s` is used as an additive term in the " +"Euclidean distance calculation:" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:69 +msgid "{r_i}=\\sqrt{{r_{ix}}^2 + {r_{iy}}^2 + s^2}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:73 +msgid "" +"where :math:`r_{ix}` and :math:`r_{iy}` are the horizontal and vertical " +"distances between the grid node to point :math:`i` respectively." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:76 +msgid "In this method the weighting factor :math:`w` is" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:78 +msgid "w=\\frac{1}{r^p}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:82 +msgid "" +"See :cpp:class:`GDALGridInverseDistanceToAPowerOptions` for the list of " +":cpp:func:`GDALGridCreate` parameters and :ref:`gdal_grid_invdist` for " +"the list of :ref:`gdal_grid` options." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:87 +msgid "Moving Average" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:89 +msgid "" +"The Moving Average is a simple data averaging algorithm. It uses a moving" +" window of elliptic form to search values and averages all data points " +"within the window. `Search Ellipse`_ can be rotated by specified angle, " +"the center of ellipse located at the grid node. Also the minimum number " +"of data points to average can be set. If there are not enough points in " +"window, the grid node is considered empty and will be filled with " +"specified NODATA value." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:97 +msgid "Mathematically it can be expressed with the formula:" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:99 +msgid "Z=\\frac{\\sum_{i=1}^n{Z_i}}{n}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:105 +#: ../../source/tutorials/gdal_grid_tut.rst:141 +#: ../../source/tutorials/gdal_grid_tut.rst:157 +#: ../../source/tutorials/gdal_grid_tut.rst:174 +msgid ":math:`Z` is a resulting value at the grid node," +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:107 +msgid ":math:`n` is a number of points in search `Search Ellipse`_." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:109 +msgid "" +"See :cpp:class:`GDALGridMovingAverageOptions` for the list of " +":cpp:func:`GDALGridCreate` parameters and :ref:`gdal_grid_average` for " +"the list of :ref:`gdal_grid` options." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:113 +msgid "Nearest Neighbor" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:115 +msgid "" +"The Nearest Neighbor method doesn't perform any interpolation or " +"smoothing, it just takes the value of nearest point found in the grid " +"node search ellipse and returns it as a result. If there are no points " +"found, the specified NODATA value will be returned." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:120 +msgid "" +"See :cpp:class:`GDALGridNearestNeighborOptions` for the list of " +":cpp:func:`GDALGridCreate` parameters and :ref:`gdal_grid_nearest` for " +"the list of :ref:`gdal_grid` options." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:124 +msgid "Data Metrics Computation" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:126 +msgid "" +"All the metrics have the same set controlling options. See the " +":cpp:class:`GDALGridDataMetricsOptions`." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:130 +msgid "Minimum Data Value" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:132 +msgid "" +"Minimum value found in grid node `Search Ellipse`_. If there are no " +"points found, the specified NODATA value will be returned." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:135 +msgid "Z=\\min{(Z_1,Z_2,\\ldots,Z_n)}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:146 +msgid "Maximum Data Value" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:148 +msgid "" +"Maximum value found in grid node `Search Ellipse`_. If there are no " +"points found, the specified NODATA value will be returned." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:151 +msgid "Z=\\max{(Z_1,Z_2,\\ldots,Z_n)}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:162 +msgid "Data Range" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:164 +msgid "" +"A difference between the minimum and maximum values found in grid `Search" +" Ellipse`_. If there are no points found, the specified NODATA value will" +" be returned." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:168 +msgid "Z=\\max{(Z_1,Z_2,\\ldots,Z_n)}-\\min{(Z_1,Z_2,\\ldots,Z_n)}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:179 +msgid "Search Ellipse" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:181 +msgid "" +"Search window in gridding algorithms specified in the form of rotated " +"ellipse. It is described by the three parameters:" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:184 +msgid "" +":math:`radius_1` is the first radius (:math:`x` axis if rotation angle is" +" 0)," +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:185 +msgid "" +":math:`radius_2` is the second radius (:math:`y` axis if rotation angle " +"is 0)," +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:186 +msgid "" +":math:`angle` is a search ellipse rotation angle (rotated counter " +"clockwise)." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:-1 +msgid "Search ellipse" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:198 +msgid "" +"Only points located inside the search ellipse (including its border line)" +" will be used for computation." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:5 +msgid "Geotransform Tutorial" +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:8 +msgid "Introduction to Geotransforms:" +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:9 +msgid "" +"A geotransform is an affine transformation from the image coordinate " +"space (row, column), also known as (pixel, line) to the georeferenced " +"coordinate space (projected or geographic coordinates)." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:13 +msgid "A geotransform consists in a set of 6 coefficients:" +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:15 +msgid "``GT(0)`` x-coordinate of the upper-left corner of the upper-left pixel." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:16 +msgid "``GT(1)`` w-e pixel resolution / pixel width." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:17 +msgid "``GT(2)`` row rotation (typically zero)." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:18 +msgid "``GT(3)`` y-coordinate of the upper-left corner of the upper-left pixel." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:19 +msgid "``GT(4)`` column rotation (typically zero)." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:20 +msgid "" +"``GT(5)`` n-s pixel resolution / pixel height (negative value for a " +"north-up image)." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:23 +msgid "" +"Transformation from image coordinate space to georeferenced coordinate " +"space:" +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:30 +msgid "" +"Note that the pixel/line coordinates in the above are from (0.0,0.0) at " +"the top left corner of the top left pixel to " +"(width_in_pixels,height_in_pixels) at the bottom right corner of the " +"bottom right pixel. The pixel/line location of the center of the top left" +" pixel would therefore be (0.5,0.5)." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:35 +msgid "In case of north up images:" +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:36 +msgid "``GT(2)``, ``GT(4)`` coefficients are zero." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:37 +msgid "``GT(1)``, ``GT(5)`` is the pixel size." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:38 +msgid "" +"``GT(0)``, ``GT(3)`` position is the top left corner of the top left " +"pixel of the raster." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:5 +msgid "GNM API tutorial" +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:9 +msgid "" +"This document is intended to describe using the GNM C++ classes to work " +"with networks. It is advised to read the :ref:`gnm_data_model` before to " +"understand the purpose and structure of GNM classes." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:12 +msgid "Managing networks" +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:14 +msgid "" +"In the first example we will create a small water network on the base of " +"the set of spatial data (two shapefiles: pipes and wells which are " +"situated at the GDAL source tree: autotest\\\\gnm\\\\data). The use of " +"the common network format - :cpp:class:`GNMGdalNetwork` class - will " +"allow us to select one of the GDAL-supported vector formats for our " +"network - ESRI Shapefile. After the creation we will build a topology and" +" add some additional data: pumps layer, in order to manually edit network" +" topology." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:16 +msgid "" +"Initially we register GDAL drivers and create some options (string " +"pairs), which will be passed as parameters during network creation. Here " +"we create a network's name." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:33 +msgid "" +"Some options are obligatory. The following parameters must be specified " +"during the network creation: the path/name; format of network storage; " +"spatial reference system (EPSG, WKT, etc.). The according dataset with " +"the \"network part\" will be created and the resulting network will be " +"returned." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:43 +msgid "" +"For now we have a void network consisted of only \"system layers\". We " +"need to populate it with \"class layers\" full of features, so we open a " +"certain foreign dataset and copy layers from it to our network. Note, " +"that we use GDALDataset:: methods for working with \"class layers\", " +"because :cpp:class:`GNMNetwork` inherited from GDALDataset." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:58 +msgid "" +"After the successful copying we have the network full of features, but " +"with no topology. The features were added and registered in the network " +"but they are still not connected with each other. Now it is time to build" +" the network topology. There are two ways of doing this in GNM: manually " +"or automatically. In the most cases automatic building is more " +"convenient, while manual is useful for small editings. Automatic building" +" requires some parameters: we must specify which \"class layers\" will " +"participate in topology building (we select our two layers), a snap " +"tolerance, direct and inverse cost, direction, which is equal 0.00005 in " +"our case. If the building will be successful the network's graph will be " +"filled with the according connections." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:81 +msgid "" +"At this point we have a ready network with topological and spatial data, " +"which can be used now for different purposes (analysis, converting into " +"different formats, etc). But sometimes it is necessary to modify some " +"network's data. For example we need to add additional features and attach" +" them to our built topology (modify topology). We create a new \"class " +"layer\" in the network and add one feature to it." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:114 +msgid "" +"After the successful creation the feature will be registered in the " +"network and we can connect it with others. There can be two possible ways" +" to do this. In the first case we need a real feature which will be an " +"edge in the connection, while in the second case we do not need such " +"feature, and passing -1 into the " +":cpp:func:`GNMGenericNetwork::ConnectFeatures` method means that the " +"special system edge will be created for this connection and added to the " +"graph automatically. In our case we had added only one point feature and " +"we have not got the line one to be an edge, so we will use the " +"\"virtual\" connection. We pass the GFID of our point as the source, the " +"GFID of one of the existed features as the target and -1 as the " +"connector. Note that we also set the costs (direct and inverse) and the " +"direction of our edge manually and these values will be written to the " +"graph. When we used the automatic connection (which also uses " +"ConnectFeatures() internally) such vales were set automatically according" +" to the rule which we also set before." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:124 +msgid "" +"After all we correctly close the network which frees the allocated " +"resources." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:131 +#: ../../source/tutorials/gnm_api_tut.rst:299 +msgid "All in one block:" +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:237 +msgid "Analysing networks" +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:239 +msgid "" +"In the second example we will analyse the network which we have built in " +"the first example. We will calculate the shortest path between two points" +" via Dijkstra algorithm performing the feature blockings and saving the " +"resulting path into the file." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:241 +msgid "Initially we open our network, passing the path to its Shapefile dataset." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:259 +msgid "" +"Before any calculations we open the dataset which will hold the layer " +"with the resulting path." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:275 +msgid "" +"Finally we use the Dijkstra shortest path method to calculations. This " +"path will be found passing over the blocked feature and saved into " +"internal memory OGRLayer, which we copy to the real dataset. Now it can " +"be visualized by GIS." +msgstr "" + +#: ../../source/tutorials/index.rst:5 +msgid "Tutorials" +msgstr "" + +#: ../../source/tutorials/index.rst:8 +msgid "Raster" +msgstr "" + +#: ../../source/tutorials/index.rst:20 +msgid "Multidimensional raster" +msgstr "" + +#: ../../source/tutorials/index.rst:28 +msgid "Vector" +msgstr "" + +#: ../../source/tutorials/index.rst:38 +msgid "Geographic Network Model" +msgstr "" + +#: ../../source/tutorials/index.rst:46 +msgid "" +"Projections and Spatial Reference Systems tutorial (OSR - " +"OGRSpatialReference)" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:5 +msgid "Multidimensional raster API tutorial" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:8 +msgid "Read the content of an array" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:11 +msgid "In C++" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:53 +msgid "In C" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:131 +msgid "In Python" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:141 +msgid "If NumPy is available:" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:153 +#: ../../source/tutorials/vector_python_driver.rst:631 +msgid "Other examples" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:155 +msgid "Test scripts from the GDAL autotest suite" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:157 +msgid "" +":ref:`MEM <raster.mem>` driver: " +":source_file:`autotest/gdrivers/memmultidim.py`" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:158 +msgid "" +":ref:`netCDF <raster.netcdf>` driver: " +":source_file:`autotest/gdrivers/netcdf_multidim.py`" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:159 +msgid "" +":ref:`HDF5 <raster.hdf5>` driver: " +":source_file:`autotest/gdrivers/hdf5multidim.py`" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:160 +msgid "" +":ref:`VRT <raster.vrt>` driver: " +":source_file:`autotest/gdrivers/vrtmultidim.py`" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:161 +msgid "" +":ref:`gdalmdiminfo` tests: " +":source_file:`autotest/utilities/test_gdalmdiminfo_lib.py`" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:162 +msgid "" +":ref:`gdalmdimtranslate` tests: " +":source_file:`autotest/utilities/test_gdalmdimtranslate_lib.py`" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:5 +msgid "OGR Coordinate Reference Systems and Coordinate Transformation tutorial" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:16 +#: ../../source/tutorials/vector_python_driver.rst:12 +msgid "Introduction" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:18 +msgid "" +"The :cpp:class:`OGRSpatialReference` and " +":cpp:class:`OGRCoordinateTransformation` classes provide respectively " +"services to represent coordinate reference systems (known as CRS or SRS, " +"such as typically a projected CRS associating a map projection with a " +"geodetic datums) and to transform between them. These services are " +"loosely modeled on the OpenGIS Coordinate Transformations specification, " +"and rely on the Well Known Text (WKT) format (in its various versions: " +"OGC WKT 1, ESRI WKT, WKT2:2015 and WKT2:2018) for describing coordinate " +"systems." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:27 +msgid "References and applicable standards" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:29 +msgid "" +"`PROJ documentation <https://proj4.org>`_: projection methods and " +"coordinate operations" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:30 +msgid "" +"`ISO:19111 and WKT standards " +"<https://proj4.org/development/reference/cpp/cpp_general.html#standards>`_" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:31 +msgid "" +"`GeoTIFF Projections Transform List " +"<http://geotiff.maptools.org/proj_list>`_: understanding formulations of " +"projections in WKT for GeoTIFF" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:32 +msgid "`EPSG Geodesy web page <http://www.epsg.org>`_ is also a useful resource" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:35 +msgid "Defining a Geographic Coordinate Reference System" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:37 +msgid "" +"CRS are encapsulated in the :cpp:class:`OGRSpatialReference` class. There" +" are a number of ways of initializing an OGRSpatialReference object to a " +"valid coordinate reference system. There are two primary kinds of CRS. " +"The first is geographic (positions are measured in long/lat) and the " +"second is projected (such as UTM - positions are measured in meters or " +"feet)." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:43 +msgid "" +"A Geographic CRS contains information on the datum (which implies a " +"spheroid described by a semi-major axis, and inverse flattening), prime " +"meridian (normally Greenwich), and an angular units type which is " +"normally degrees. The following code initializes a geographic CRS on " +"supplying all this information along with a user visible name for the " +"geographic CRS." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:63 +msgid "" +"The abbreviation CS in :cpp:func:`OGRSpatialReference::SetGeogCS` is not " +"appropriate according to current geodesic terminology, and should be " +"understood as CRS" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:66 +msgid "" +"Of these values, the names \"My geographic CRS\", \"My WGS84 Spheroid\", " +"\"Greenwich\" and \"degree\" are not keys, but are used for display to " +"the user. However, the datum name \"World Geodetic System 1984\" is used" +" as a key to identify the datum, and should be set to a known value from " +"the EPSG registry, so that appropriate datum transformations can be done " +"during coordinate operations. The list of valid geodetic datum can be " +"seen in the 3rd column of the `geodetic_datum.sql " +"<https://github.com/OSGeo/PROJ/blob/master/data/sql/geodetic_datum.sql>`_" +" file." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:77 +msgid "" +"In WKT 1, space characters in datum names are normally replaced by " +"underscore. And WGS_1984 is used as an alias of \"World Geodetic System " +"1984\"" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:80 +msgid "" +"The OGRSpatialReference has built in support for a few well known CRS, " +"which include \"NAD27\", \"NAD83\", \"WGS72\" and \"WGS84\" which can be " +"defined in a single call to " +":cpp:func:`OGRSpatialReference::SetWellKnownGeogCS`." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:91 +msgid "" +"The abbreviation CS in SetWellKnownGeogCS() is not appropriate according " +"to current geodesic terminology, and should be understood as CRS" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:94 +msgid "" +"Furthermore, any geographic CRS in the EPSG database can be set by its " +"GCS code number if the EPSG database is available." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:101 +msgid "" +"For serialization, and transmission of projection definitions to other " +"packages, the OpenGIS Well Known Text format for coordinate systems is " +"used. An OGRSpatialReference can be initialized from WKT, or converted " +"back into WKT. As of GDAL 3.0, the default format for WKT export is still" +" OGC WKT 1." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:115 +msgid "outputs:" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:125 +msgid "or in more readable form:" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:142 +msgid "" +"Starting with GDAL 3.0, the :cpp:func:`OGRSpatialReference::exportToWkt` " +"method accepts options," +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:170 +msgid "" +"This method with options is available in C as the " +":cpp:func:`OSRExportToWktEx` function." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:172 +msgid "" +"The :cpp:func:`OGRSpatialReference::importFromWkt` method can be used to " +"set an OGRSpatialReference from a WKT CRS definition." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:176 +msgid "CRS and axis order" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:178 +msgid "" +"One \"detail\" that has been omitted in previous sections is the topic of" +" the order of coordinate axis in a CRS. A Geographic CRS is, according to" +" ISO:19111 modeling, made of two main components: a geodetic datum and a " +"`coordinate system " +"<http://docs.opengeospatial.org/as/18-005r4/18-005r4.html#42>`_. For 2D " +"geographic CRS, the coordinate system axes are the longitude and the " +"latitude, and the values along those axes are expressed generally in " +"degree (ancient French-based CRS may use grad)." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:185 +msgid "" +"The order in which they are specified, that is latitude first, longitude " +"second, or the reverse, is a constant matter of confusion and vary " +"depending on conventions used by geodetic authorities, GIS user, file " +"format and protocol specifications, etc. This is the source of various " +"interoperability issues." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:190 +msgid "" +"Before GDAL 3.0, the :cpp:class:`OGRSpatialReference` class did not " +"honour the axis order mandated by the authority defining a CRS and " +"consequently stripped axis order information from the WKT string when the" +" order was latitude first, longitude second. Coordinate transformations " +"using the OGRCoordinateTransformation class also assumed that geographic " +"coordinates passed or returned by the Transform() method of this class " +"used the longitude, latitude order." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:197 +msgid "" +"Starting with GDAL 3.0, the axis order mandated by the authority defining" +" a CRS is by default honoured by the OGRCoordinateTransformation class, " +"and always exported in WKT1. Consequently CRS created with the " +"\"EPSG:4326\" or \"WGS84\" strings use the latitude first, longitude " +"second axis order." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:202 +msgid "" +"In order to help migration from code bases still using coordinates with " +"the longitude, latitude order, it is possible to attach a metadata " +"information to a OGRSpatialReference instance, to specify that for the " +"purpose of coordinate transformations, the order of values effectively " +"passed or returned, will be longitude, latitude. For that, the following " +"must be called" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:212 +msgid "" +"The argument passed to " +":cpp:func:`OGRSpatialReference::SetAxisMappingStrategy` is the data axis " +"to CRS axis mapping strategy." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:215 +msgid "" +":c:macro:`OAMS_TRADITIONAL_GIS_ORDER` means that for geographic CRS with " +"lat/long order, the data will still be long/lat ordered. Similarly for a " +"projected CRS with northing/easting order, the data will still be " +"easting/northing ordered." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:216 +msgid "" +":c:macro:`OAMS_AUTHORITY_COMPLIANT` means that the data axis will be " +"identical to the CRS axis. This is the default value when instantiating " +"OGRSpatialReference." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:217 +msgid "" +":c:macro:`OAMS_CUSTOM` means that the data axes are customly defined with" +" SetDataAxisToSRSAxisMapping()." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:219 +msgid "" +"What has been discussed in this section for the particular case of " +"Geographic CRS also applies to Projected CRS. While most of them use " +"Easting first, Northing second convention, some defined in the EPSG " +"registry use the reverse convention." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:223 +msgid "" +"Another way to keep using the Traditional GIS order for some specific " +"well known CRS is to calling to " +":cpp:func:`OGRSpatialReference::SetWellKnownGeogCS` with \"CRS27\", " +"\"CRS83\" or \"CRS84\" instead of \"NAD27\", \"NAD83\" and \"WGS84\" " +"respectively." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:232 +msgid "Defining a Projected CRS" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:234 +msgid "" +"A projected CRS (such as UTM, Lambert Conformal Conic, etc.) requires and" +" underlying geographic CRS as well as a definition for the projection " +"transform used to translate between linear positions (in meters or feet) " +"and angular long/lat positions. The following code defines a UTM zone 17" +" projected CRS with an underlying geographic CRS (datum) of WGS84." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:249 +msgid "" +"Calling :cpp:func:`OGRSpatialReference::SetProjCS` sets a user name for " +"the projected CRS and establishes that the system is projected. The " +":cpp:func:`OGRSpatialReference::SetWellKnownGeogCS` associates a " +"geographic coordinate system, and the " +":cpp:func:`OGRSpatialReference::SetUTM` call sets detailed projection " +"transformation parameters. At this time the above order is important in " +"order to create a valid definition, but in the future the object will " +"automatically reorder the internal representation as needed to remain " +"valid." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:259 +msgid "For now, be careful of the order of steps defining an OGRSpatialReference!" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:261 +msgid "" +"The above definition would give a WKT version that looks something like " +"the following. Note that the UTM 17 was expanded into the details " +"transverse mercator definition of the UTM zone." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:286 +msgid "" +"There are methods for many projection methods including " +":cpp:func:`OGRSpatialReference::SetTM` (Transverse Mercator), " +":cpp:func:`OGRSpatialReference::SetLCC` (Lambert Conformal Conic), and " +":cpp:func:`OGRSpatialReference::SetMercator`." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:290 +msgid "Querying Coordinate Reference System" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:292 +msgid "" +"Once an OGRSpatialReference has been established, various information " +"about it can be queried. It can be established if it is a projected or " +"geographic CRS using the :cpp:func:`OGRSpatialReference::IsProjected` and" +" :cpp:func:`OGRSpatialReference::IsGeographic` methods. The " +":cpp:func:`OGRSpatialReference::GetSemiMajor`, " +":cpp:func:`OGRSpatialReference::GetSemiMinor` and " +":cpp:func:`OGRSpatialReference::GetInvFlattening` methods can be used to " +"get information about the spheroid. The " +":cpp:func:`OGRSpatialReference::GetAttrValue` method can be used to get " +"the PROJCS, GEOGCS, DATUM, SPHEROID, and PROJECTION names strings. The " +":cpp:func:`OGRSpatialReference::GetProjParm` method can be used to get " +"the projection parameters. The " +":cpp:func:`OGRSpatialReference::GetLinearUnits` method can be used to " +"fetch the linear units type, and translation to meters." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:303 +msgid "" +"Note that the names of the projection method and parameters is the one of" +" WKT 1." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:306 +msgid "" +"The following code demonstrates use of " +":cpp:func:`OGRSpatialReference::GetAttrValue` to get the projection, and " +":cpp:func:`OGRSpatialReference::GetProjParm` to get projection " +"parameters. The GetAttrValue() method searches for the first \"value\" " +"node associated with the named entry in the WKT text representation. The " +"#define'ed constants for projection parameters (such as " +"SRS_PP_CENTRAL_MERIDIAN) should be used when fetching projection " +"parameter with GetProjParm(). The code for the Set methods of the various" +" projections in ogrspatialreference.cpp can be consulted to find which " +"parameters apply to which projections." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:340 +msgid "Coordinate Transformation" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:342 +msgid "" +"The :cpp:class:`OGRCoordinateTransformation` class is used for " +"translating positions between different CRS. New transformation objects " +"are created using :cpp:func:`OGRCreateCoordinateTransformation`, and then" +" the :cpp:func:`OGRCoordinateTransformation::Transform` method can be " +"used to convert points between CRS." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:373 +msgid "" +"There are a couple of points at which transformations can fail. First, " +"OGRCreateCoordinateTransformation() may fail, generally because the " +"internals recognize that no transformation between the indicated systems " +"can be established, and will return a NULL pointer." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:379 +msgid "" +"The OGRCoordinateTransformation::Transform() method itself can also fail." +" This may be as a delayed result of one of the above problems, or as a " +"result of an operation being numerically undefined for one or more of the" +" passed in points. The Transform() function will return TRUE on success," +" or FALSE if any of the points fail to transform. The point array is " +"left in an indeterminate state on error." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:387 +msgid "" +"Though not shown above, the coordinate transformation service can take 3D" +" points, and will adjust elevations for elevation differences in " +"spheroids, and datums. Elevations given on a geographic or projected CRS " +"are assumed to be ellipsoidal heights. When using a compound CRS made of " +"a horizontal CRS (geographic or projected) and a vertical CRS, elevations" +" will be related to a vertical datum (mean sea level, gravity based, " +"etc.)." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:394 +msgid "" +"Starting with GDAL 3.0, a time value (generally as a value in decimal " +"years) can also be specified for time-dependent coordinate operations." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:397 +msgid "" +"The following example shows how to conveniently create a long/lat " +"coordinate system using the same geographic CRS as a projected coordinate" +" system, and using that to transform between projected coordinates and " +"long/lat. The returned coordinates will be in longitude, latitude order " +"due to the call to SetAxisMappingStrategy(OAMS_TRADITIONAL_GIS_ORDER)" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:427 +msgid "Advanced Coordinate Transformation" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:429 +msgid "" +"OGRCreateCoordinateTransformation() under-the-hood may determine several " +"candidate coordinate operations transforming from the source CRS to the " +"target CRS. Those candidate coordinate operations each have their own " +"area of use. When Transform() is invoked, it will determine the most " +"appropriate coordinate operation based on the coordinates of the point to" +" transform and area of use. For example, there are several dozens of " +"possible coordinate operations for the NAD27 to WGS84 transformation." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:437 +msgid "" +"If a bounding box of the area of interest into which coordinates to " +"transform are located is known, it is possible to specify it to restrict " +"the candidate coordinate operations to consider:" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:447 +msgid "" +"For cases where a particular coordinate operation must be used, it is " +"possible to specify it as as a PROJ string (single step operation or " +"multiple step string starting with +proj=pipeline), a WKT2 string " +"describing a CoordinateOperation, or a " +"urn:ogc:def:coordinateOperation:EPSG::XXXX URN" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:473 +msgid "Alternate Interfaces" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:475 +msgid "" +"A C interface to the coordinate system services is defined in " +"ogr_srs_api.h, and Python bindings are available via the osr.py module. " +"Methods are close analogs of the C++ methods but C and Python bindings " +"are missing for some C++ methods." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:481 +msgid "C bindings" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:577 +msgid "Python bindings" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:604 +msgid "History and implementation considerations" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:606 +msgid "" +"Before GDAL 3.0, the OGRSpatialReference class was strongly tied to OGC " +"WKT (WKT 1) format specified by `Coordinate Transformation Services (CT) " +"specification (01-009) " +"<http://portal.opengeospatial.org/files/?artifact_id=999>`_, and the way " +"it was interpreted by GDAL, which various caveats detailed in the " +":ref:`wktproblems` page. The class mostly contained an in-memory tree-" +"like representation of WKT 1 strings. The class used to directly " +"implement import and export to OGC WKT 1, WKT-ESRI and PROJ.4 formats. " +"Reprojection services were only available if GDAL had been build against " +"the PROJ library." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:616 +msgid "" +"Starting with GDAL 3.0, the `PROJ <https://proj4.org>`_ >= 6.0 library " +"has become a required dependency of GDAL. PROJ 6 has built-in support for" +" OGC WKT 1, ESRI WKT, OGC WKT 2:2015 and OGC WKT 2:2018 representations. " +"PROJ 6 also implements a C++ object class hierarchy of the ISO-19111 / " +"OGC Abstract Topic 2 \"Referencing by coordinate\" standard. Consequently" +" the OGRSpatialReference class has been modified to act mostly as a " +"wrapper on top of PROJ PJ* CRS objects, and tries to abstract away from " +"the OGC WKT 1 representation as much as possible. However, for backward " +"compatibility, some methods still expect arguments or return values that " +"are specific of OGC WKT 1. The design of th OGRSpatialReference class is " +"also still monolithic. Users wanting direct and fine grained access to " +"CRS representations might want to directly use the PROJ 6 C or C++ API." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:5 +msgid "Raster API tutorial" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:8 +msgid "Opening the File" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:10 +msgid "" +"Before opening a GDAL supported raster datastore it is necessary to " +"register drivers. There is a driver for each supported format. Normally " +"this is accomplished with the :cpp:func:`GDALAllRegister` function which " +"attempts to register all known drivers, including those auto-loaded from " +".so files using :cpp:func:`GDALDriverManager::AutoLoadDrivers`. If for " +"some applications it is necessary to limit the set of drivers it may be " +"helpful to review the code from gdalallregister.cpp. Python automatically" +" calls GDALAllRegister() when the gdal module is imported." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:12 +msgid "" +"Once the drivers are registered, the application should call the free " +"standing :cpp:func:`GDALOpen` function to open a dataset, passing the " +"name of the dataset and the access desired (GA_ReadOnly or GA_Update)." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:14 +#: ../../source/tutorials/raster_api_tut.rst:98 +#: ../../source/tutorials/raster_api_tut.rst:163 +#: ../../source/tutorials/raster_api_tut.rst:241 +#: ../../source/tutorials/raster_api_tut.rst:314 +#: ../../source/tutorials/raster_api_tut.rst:369 +#: ../../source/tutorials/raster_api_tut.rst:410 +#: ../../source/tutorials/raster_api_tut.rst:458 +#: ../../source/tutorials/raster_api_tut.rst:485 +#: ../../source/tutorials/vector_api_tut.rst:1160 +msgid "In C++:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:40 +#: ../../source/tutorials/raster_api_tut.rst:119 +#: ../../source/tutorials/raster_api_tut.rst:190 +#: ../../source/tutorials/raster_api_tut.rst:254 +#: ../../source/tutorials/raster_api_tut.rst:332 +#: ../../source/tutorials/raster_api_tut.rst:383 +#: ../../source/tutorials/raster_api_tut.rst:426 +#: ../../source/tutorials/raster_api_tut.rst:467 +#: ../../source/tutorials/raster_api_tut.rst:506 +#: ../../source/tutorials/vector_api_tut.rst:1175 +msgid "In C:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:67 +#: ../../source/tutorials/raster_api_tut.rst:143 +#: ../../source/tutorials/raster_api_tut.rst:217 +#: ../../source/tutorials/raster_api_tut.rst:267 +#: ../../source/tutorials/raster_api_tut.rst:349 +#: ../../source/tutorials/raster_api_tut.rst:396 +#: ../../source/tutorials/raster_api_tut.rst:442 +#: ../../source/tutorials/raster_api_tut.rst:476 +#: ../../source/tutorials/raster_api_tut.rst:529 +#: ../../source/tutorials/vector_api_tut.rst:390 +#: ../../source/tutorials/vector_api_tut.rst:700 +msgid "In Python:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:76 +msgid "" +"Note that if :cpp:func:`GDALOpen` returns NULL it means the open failed, " +"and that an error messages will already have been emitted via " +":cpp:func:`CPLError`. If you want to control how errors are reported to " +"the user review the :cpp:func:`CPLError` documentation. Generally " +"speaking all of GDAL uses :cpp:func:`CPLError` for error reporting. Also," +" note that pszFilename need not actually be the name of a physical file " +"(though it usually is). It's interpretation is driver dependent, and it " +"might be an URL, a filename with additional parameters added at the end " +"controlling the open or almost anything. Please try not to limit GDAL " +"file selection dialogs to only selecting physical files." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:79 +msgid "Getting Dataset Information" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:81 +msgid "" +"As described in the :ref:`raster_data_model`, a :cpp:class:`GDALDataset` " +"contains a list of raster bands, all pertaining to the same area, and " +"having the same resolution. It also has metadata, a coordinate system, a " +"georeferencing transform, size of raster and various other information." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:83 +msgid "" +"In the particular, but common, case of a \"north up\" image without any " +"rotation or shearing, the georeferencing transform " +":ref:`geotransforms_tut` takes the following form :" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:94 +msgid "In the general case, this is an affine transform." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:96 +msgid "" +"If we wanted to print some general information about the dataset we might" +" do the following:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:159 +msgid "Fetching a Raster Band" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:161 +msgid "" +"At this time access to raster data via GDAL is done one band at a time. " +"Also, there is metadata, block sizes, color tables, and various other " +"information available on a band by band basis. The following codes " +"fetches a :cpp:class:`GDALRasterBand` object from the dataset (numbered 1" +" through :cpp:func:`GDALRasterBand::GetRasterCount`) and displays a " +"little information about it." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:237 +msgid "Reading Raster Data" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:239 +msgid "" +"There are a few ways to read raster data, but the most common is via the " +":cpp:func:`GDALRasterBand::RasterIO` method. This method will " +"automatically take care of data type conversion, up/down sampling and " +"windowing. The following code will read the first scanline of data into a" +" similarly sized buffer, converting it to floating point as part of the " +"operation." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:252 +#: ../../source/tutorials/raster_api_tut.rst:265 +msgid "" +"The pafScanline buffer should be freed with CPLFree() when it is no " +"longer used." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:276 +msgid "" +"Note that the returned scanline is of type string, and contains xsize*4 " +"bytes of raw binary floating point data. This can be converted to Python " +"values using the struct module from the standard library:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:283 +msgid "The RasterIO call takes the following arguments." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:294 +msgid "" +"Note that the same RasterIO() call is used to read, or write based on the" +" setting of eRWFlag (either GF_Read or GF_Write). The nXOff, nYOff, " +"nXSize, nYSize argument describe the window of raster data on disk to " +"read (or write). It doesn't have to fall on tile boundaries though access" +" may be more efficient if it does." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:296 +msgid "" +"The pData is the memory buffer the data is read into, or written from. " +"It's real type must be whatever is passed as eBufType, such as " +"GDT_Float32, or GDT_Byte. The RasterIO() call will take care of " +"converting between the buffer's data type and the data type of the band. " +"Note that when converting floating point data to integer RasterIO() " +"rounds down, and when converting source values outside the legal range of" +" the output the nearest legal value is used. This implies, for instance, " +"that 16bit data read into a GDT_Byte buffer will map all values greater " +"than 255 to 255, the data is not scaled!" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:298 +msgid "" +"The nBufXSize and nBufYSize values describe the size of the buffer. When " +"loading data at full resolution this would be the same as the window " +"size. However, to load a reduced resolution overview this could be set to" +" smaller than the window on disk. In this case the RasterIO() will " +"utilize overviews to do the IO more efficiently if the overviews are " +"suitable." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:300 +msgid "" +"The nPixelSpace, and nLineSpace are normally zero indicating that default" +" values should be used. However, they can be used to control access to " +"the memory data buffer, allowing reading into a buffer containing other " +"pixel interleaved data for instance." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:303 +msgid "Closing the Dataset" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:305 +msgid "" +"Please keep in mind that :cpp:class:`GDALRasterBand` objects are owned by" +" their dataset, and they should never be destroyed with the C++ delete " +"operator. :cpp:class:`GDALDataset`'s can be closed by calling " +":cpp:func:`GDALClose` (it is NOT recommended to use the delete operator " +"on a GDALDataset for Windows users because of known issues when " +"allocating and freeing memory across module boundaries. See the relevant " +"topic on the FAQ). Calling GDALClose will result in proper cleanup, and " +"flushing of any pending writes. Forgetting to call GDALClose on a dataset" +" opened in update mode in a popular format like GTiff will likely result " +"in being unable to open it afterwards." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:308 +msgid "Techniques for Creating Files" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:310 +msgid "" +"New files in GDAL supported formats may be created if the format driver " +"supports creation. There are two general techniques for creating files, " +"using CreateCopy() and Create(). The CreateCopy method involves calling " +"the CreateCopy() method on the format driver, and passing in a source " +"dataset that should be copied. The Create method involves calling the " +"Create() method on the driver, and then explicitly writing all the " +"metadata, and raster data with separate calls. All drivers that support " +"creating new files support the CreateCopy() method, but only a few " +"support the Create() method." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:312 +msgid "" +"To determine if a particular format supports Create or CreateCopy it is " +"possible to check the DCAP_CREATE and DCAP_CREATECOPY metadata on the " +"format driver object. Ensure that :cpp:func:`GDALAllRegister` has been " +"called before calling :cpp:func:`GDALDriverManager::GetDriverByName`. In " +"this example we fetch a driver, and determine whether it supports " +"Create() and/or CreateCopy()." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:362 +msgid "" +"Note that a number of drivers are read-only and won't support Create() or" +" CreateCopy()." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:365 +msgid "Using CreateCopy()" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:367 +msgid "" +"The :cpp:func:`GDALDriver::CreateCopy` method can be used fairly simply " +"as most information is collected from the source dataset. However, it " +"includes options for passing format specific creation options, and for " +"reporting progress to the user as a long dataset copy takes place. A " +"simple copy from the a file named pszSrcFilename, to a new file named " +"pszDstFilename using default options on a format whose driver was " +"previously fetched might look like this:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:406 +msgid "" +"Note that the CreateCopy() method returns a writable dataset, and that it" +" must be closed properly to complete writing and flushing the dataset to " +"disk. In the Python case this occurs automatically when \"dst_ds\" goes " +"out of scope. The FALSE (or 0) value used for the bStrict option just " +"after the destination filename in the CreateCopy() call indicates that " +"the CreateCopy() call should proceed without a fatal error even if the " +"destination dataset cannot be created to exactly match the input dataset." +" This might be because the output format does not support the pixel " +"datatype of the input dataset, or because the destination cannot support " +"writing georeferencing for instance." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:408 +msgid "" +"A more complex case might involve passing creation options, and using a " +"predefined progress monitor like this:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:454 +msgid "Using Create()" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:456 +msgid "" +"For situations in which you are not just exporting an existing file to a " +"new file, it is generally necessary to use the " +":cpp:func:`GDALDriver::Create` method (though some interesting options " +"are possible through use of virtual files or in-memory files). The " +"Create() method takes an options list much like CreateCopy(), but the " +"image size, number of bands and band type must be provided explicitly." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:483 +msgid "" +"Once the dataset is successfully created, all appropriate metadata and " +"raster data must be written to the file. What this is will vary according" +" to usage, but a simple case with a projection, geotransform and raster " +"data is covered here." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:5 +msgid "Raster driver implementation tutorial" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:10 +#: ../../source/tutorials/vector_driver_tut.rst:10 +msgid "Overall Approach" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:12 +msgid "" +"In general new formats are added to GDAL by implementing format specific " +"drivers as subclasses of :cpp:class:`GDALDataset`, and band accessors as " +"subclasses of :cpp:class:`GDALRasterBand`. As well, a " +":cpp:class:`GDALDriver` instance is created for the format, and " +"registered with the :cpp:class:`GDALDriverManager`, to ensure that the " +"system knows about the format." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:14 +msgid "" +"This tutorial will start with implementing a simple read-only driver " +"(based on the JDEM driver), and then proceed to utilizing the " +"RawRasterBand helper class, implementing creatable and updatable formats," +" and some esoteric issues." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:16 +msgid "" +"It is strongly advised that the :ref:`raster_data_model` be reviewed and " +"understood before attempting to implement a GDAL driver." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:19 +msgid "Implementing the Dataset" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:21 +msgid "" +"We will start showing minimal implementation of a read-only driver for " +"the Japanese DEM format (:source_file:`frmts/jdem/jdemdataset.cpp`). " +"First we declare a format specific dataset class, JDEMDataset in this " +"case." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:44 +msgid "" +"In general we provide capabilities for a driver, by overriding the " +"various virtual methods on the GDALDataset base class. However, the " +"Open() method is special. This is not a virtual method on the base class," +" and we will need a freestanding function for this operation, so we " +"declare it static. Implementing it as a method in the JDEMDataset class " +"is convenient because we have privileged access to modify the contents of" +" the database object." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:46 +msgid "The open method itself may look something like this:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:102 +msgid "" +"The first step in any database Open function is to verify that the file " +"being passed is in fact of the type this driver is for. It is important " +"to realize that each driver's Open function is called in turn till one " +"succeeds. Drivers must quietly return nullptr if the passed file is not " +"of their format. They should only produce an error if the file does " +"appear to be of their supported format, but is for some reason " +"unsupported or corrupt. The information on the file to be opened is " +"passed in contained in a GDALOpenInfo object. The GDALOpenInfo includes " +"the following public data members:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:124 +msgid "" +"The driver can inspect these to establish if the file is supported. If " +"the `pszFilename` refers to an object in the file system, the `bStatOK` " +"flag will be set to TRUE. As well, if the file was successfully opened, " +"the first kilobyte or so is read in, and put in pabyHeader, with the " +"exact size in `nHeaderBytes`." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:126 +msgid "" +"In this typical testing example it is verified that the file was " +"successfully opened, that we have at least enough header information to " +"perform our test, and that various parts of the header are as expected " +"for this format. In this case, there are no magic numbers for JDEM format" +" so we check various date fields to ensure they have reasonable century " +"values. If the test fails, we quietly return NULL indicating this file " +"isn't of our supported format." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:128 +msgid "The identification is in fact delegated to a Identify() static function :" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:173 +msgid "" +"It is important to make the \"is this my format\" test as stringent as " +"possible. In this particular case, we check that dates are in the 19th " +"or 20th centry, but as this might also be too weak, we check that the " +"geospatial extent is consistent, and valid for Japan. Once we are " +"satisfied that the file is of our format, we can do any other tests that " +"are necessary to validate the file is usable, and in particular that we " +"can provide the level of access desired. Since the JDEM driver does not " +"provide update support, error out in that case." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:192 +msgid "" +"Next we need to create an instance of the database class in which we will" +" set various information of interest. We create it as a " +"std::unique_ptr<JDEMDataset> with the cpl::make_unique<> utility " +"(equivalent to std::make_unique<> available in C++14 and later), to make " +"memory management easier in error code paths." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:209 +msgid "" +"At this point we \"borrow\" the file handle that was held by " +"GDALOpenInfo* (we did make sure that poDS->m_fp is initialized to nullptr" +" in the inline member definition). This file pointer uses the VSI*L GDAL " +"API to access files on disk. This virtualized POSIX-style API allows some" +" special capabilities like supporting large files, in-memory files and " +"zipped files." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:213 +msgid "" +"Next the X and Y size are extracted from the header. The `nRasterXSize` " +"and `nRasterYSize` are data fields inherited from the GDALDataset base " +"class, and must be set by the Open() method." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:230 +msgid "" +"All the bands related to this dataset must be created and attached using " +"the SetBand() method. We will explore the JDEMRasterBand() class shortly." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:237 +msgid "" +"Finally we assign a name to the dataset object, and call the " +"GDALPamDataset TryLoadXML() method which can initialize auxiliary " +"information from an .aux.xml file if available. We also initialize for " +"external overviews (in a .ovr side car file). For more details on these " +"services review the GDALPamDataset and related classes." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:253 +msgid "Implementing the RasterBand" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:255 +msgid "" +"Similar to the customized JDEMDataset class subclassed from GDALDataset, " +"we also need to declare and implement a customized JDEMRasterBand derived" +" from :cpp:class:`GDALRasterBand` for access to the band(s) of the JDEM " +"file. For JDEMRasterBand the declaration looks like this:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:275 +msgid "" +"The constructor may have any signature, and is only called from the " +"Open() method. Other virtual methods, such as " +":cpp:func:`GDALRasterBand::IReadBlock` must be exactly matched to the " +"method signature in gdal_priv.h." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:277 +msgid "The constructor implementation looks like this:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:294 +msgid "" +"The following data members are inherited from GDALRasterBand, and should " +"generally be set in the band constructor." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:304 +msgid "" +"The full set of possible GDALDataType values are declared in gdal.h, and " +"include GDT_Byte, GDT_UInt16, GDT_Int16, and GDT_Float32. The block size " +"is used to establish a natural or efficient block size to access the data" +" with. For tiled datasets this will be the size of a tile, while for most" +" other datasets it will be one scanline, as in this case." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:306 +msgid "" +"Next we see the implementation of the code that actually reads the image " +"data, IReadBlock()." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:363 +msgid "Key items to note are:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:365 +msgid "" +"It is typical to cast the GDALRasterBand::poDS member to the derived type" +" of the owning dataset. If your RasterBand class will need privileged " +"access to the owning dataset object, ensure it is declared as a friend " +"(omitted above for brevity)." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:366 +msgid "" +"If an error occurs, report it with CPLError(), and return CE_Failure. " +"Otherwise return CE_None." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:367 +msgid "" +"The pImage buffer should be filled with one block of data. The block is " +"the size declared in nBlockXSize and nBlockYSize for the raster band. The" +" type of the data within pImage should match the type declared in " +"eDataType in the raster band object." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:368 +msgid "" +"The nBlockXOff and nBlockYOff are block offsets, so with 128x128 tiled " +"datasets values of 1 and 1 would indicate the block going from (128,128) " +"to (255,255) should be loaded." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:371 +msgid "The Driver" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:373 +msgid "" +"While the JDEMDataset and JDEMRasterBand are now ready to use to read " +"image data, it still isn't clear how the GDAL system knows about the new " +"driver. This is accomplished via the :cpp:class:`GDALDriverManager`. To " +"register our format we implement a registration function. The declaration" +" goes in gcore/gdal_frmts.h: void CPL_DLL GDALRegister_JDEM(void);" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:376 +msgid "The definition in the driver file is:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:405 +msgid "" +"Note the use of GDAL_CHECK_VERSION macro. This is a macro that should be " +"used by drivers that can be built as a plugin. As the GDAL C++ ABI may, " +"and will, change between GDAL feature releases (for example from GDAL " +"3.x.0 to 3.y.0), it is necessary to recompile your driver against the " +"header files of the GDAL feature version with which you want to make it " +"work. The GDAL_CHECK_VERSION macro will check that the GDAL version with " +"which the driver was compiled and the version against which it is running" +" are compatible (checking that the major and minor version numbers are " +"equal). The C++ ABI will however remain stable for releases of the same " +"release branch (that is for bug fixes releases x.y.z of a given feature " +"release x.y.0)." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:407 +msgid "" +"The registration function will create an instance of a GDALDriver object " +"when first called, and register it with the GDALDriverManager. The " +"following fields can be set in the driver before registering it with the " +"GDALDriverManager." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:409 +msgid "" +"The description is the short name for the format. This is a unique name " +"for this format, often used to identity the driver in scripts and command" +" line programs. Normally 3-5 characters in length, and matching the " +"prefix of the format classes. (mandatory)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:410 +msgid "" +"GDAL_DCAP_RASTER: set to YES to indicate that this driver handles raster " +"data. (mandatory)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:411 +msgid "" +"GDAL_DMD_LONGNAME: A longer descriptive name for the file format, but " +"still no longer than 50-60 characters. (mandatory)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:412 +msgid "" +"GDAL_DMD_HELPTOPIC: The name of a help topic to display for this driver, " +"if any. In this case JDEM format is contained within the various format " +"web page held in gdal/html. (optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:413 +msgid "" +"GDAL_DMD_EXTENSIONS: The extensions used for files of this type, without " +"the leading '.'. If more than one, they should be separated with space. " +"(optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:414 +msgid "" +"GDAL_DMD_MIMETYPE: The standard mime type for this file format, such as " +"\"image/png\". (optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:415 +msgid "" +"GDAL_DMD_CREATIONOPTIONLIST: There is evolving work on mechanisms to " +"describe creation options. See the geotiff driver for an example of this." +" (optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:416 +msgid "" +"GDAL_DMD_CREATIONDATATYPES: A list of space separated data types " +"supported by this create when creating new datasets. If a Create() method" +" exists, these will be will supported. If a CreateCopy() method exists, " +"this will be a list of types that can be losslessly exported but it may " +"include weaker data types than the type eventually written. For instance," +" a format with a CreateCopy() method, and that always writes Float32 " +"might also list Byte, Int16, and UInt16 since they can losslessly " +"translated to Float32. An example value might be \"Byte Int16 UInt16\". " +"(required - if creation supported)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:417 +msgid "" +"GDAL_DCAP_VIRTUALIO: set to YES to indicate that this driver can deal " +"with files opened with the VSI*L GDAL API. Otherwise this metadata item " +"should not be defined. (optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:418 +msgid "" +"pfnOpen: The function to call to try opening files of this format. " +"(optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:419 +msgid "" +"pfnIdentify: The function to call to try identifying files of this " +"format. A driver should return 1 if it recognizes the file as being of " +"its format, 0 if it recognizes the file as being NOT of its format, or -1" +" if it cannot reach to a firm conclusion by just examining the header " +"bytes. (optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:420 +msgid "" +"pfnCreate: The function to call to create new updatable datasets of this " +"format. (optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:421 +msgid "" +"pfnCreateCopy: The function to call to create a new dataset of this " +"format copied from another source, but not necessary updatable. " +"(optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:422 +msgid "" +"pfnDelete: The function to call to delete a dataset of this format. " +"(optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:423 +msgid "" +"pfnUnloadDriver: A function called only when the driver is destroyed. " +"Could be used to cleanup data at the driver level. Rarely used. " +"(optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:425 +#: ../../source/tutorials/vector_driver_tut.rst:66 +msgid "" +"For a driver that can be built as a plugin (that is to say a standalone " +"shared object, loaded at runtime by GDAL), since GDAL 3.9 and " +":ref:`rfc-96`, there is a way to implement the driver in a way where the " +"plugin will be loaded only when necessary, and not immediately at " +":cpp:func:`GDALAllRegister` time. Consult :ref:`rfc96_example_driver` for" +" the changes needed to make the driver compatible of deferred plugin " +"loading." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:428 +msgid "Adding Driver to GDAL Tree" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:430 +msgid "" +"Note that the GDALRegister_JDEM() method must be called by the higher " +"level program in order to have access to the JDEM driver. Normal practice" +" when writing new drivers is to:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:432 +msgid "" +"Add a driver directory under frmts, with the directory name the same as " +"the short name." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:433 +msgid "" +"Add a CMakeLists.txt in that directory modeled on those from other " +"similar directories (i.e. the jdem directory)." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:434 +msgid "" +"Reference the new driver in frmts/CMakeLists.txt, using the " +"gdal_optional_format() or gdal_dependent_format() functions depending if " +"it requires no external dependency or it has at least one." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:435 +msgid "" +"Add the module with the dataset, and rasterband implementation. Generally" +" this is called <short_name>dataset.cpp, with all the GDAL specific code " +"in one file, though that is not required." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:436 +msgid "" +"Add the registration entry point declaration (i.e. GDALRegister_JDEM()) " +"to gcore/gdal_frmts.h." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:437 +msgid "" +"Add a call to the registration function to frmts/gdalallregister.cpp, " +"protected by an appropriate #ifdef." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:439 +msgid "" +"Once this is all done, it should be possible to rebuild GDAL, and have " +"the new format available in all the utilities. The :ref:`gdalinfo` " +"utility can be used to test that opening and reporting on the format is " +"working, and the :ref:`gdal_translate` utility can be used to test image " +"reading." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:442 +msgid "Adding Georeferencing" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:444 +msgid "" +"Now we will take the example a step forward, adding georeferencing " +"support. We add the following two virtual method overrides to " +"JDEMDataset, taking care to exactly match the signature of the method on " +"the GDALDataset base class." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:451 +msgid "" +"The implementation of :cpp:func:`GDALDataset::GetGeoTransform` just " +"copies the usual geotransform matrix into the supplied buffer. Note that " +":cpp:func:`GDALDataset::GetGeoTransform` may be called a lot, so it isn't" +" generally wise to do a lot of computation in it. In many cases the " +"Open() will collect the geotransform, and this method will just copy it " +"over. Also note that the geotransform return is based on an anchor point " +"at the top left corner of the top left pixel, not the center of pixel " +"approach used in some packages." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:475 +msgid "" +"The :cpp:func:`GDALDataset::GetSpatialRef` method returns a pointer to an" +" internal OGRSpatialReference object." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:484 +msgid "" +"In this case the coordinate system is fixed for all files of this format," +" and has been initialized in the JDEMDataset constructor. But in more " +"complex cases, a definition may need to be composed on the fly, in which " +"case it may be helpful to use the :cpp:class:`OGRSpatialReference` class " +"to help build the definition." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:498 +msgid "" +"This completes explanation of the features of the JDEM driver. The full " +"source for jdemdataset.cpp can be reviewed as needed." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:501 +msgid "Overviews" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:503 +msgid "" +"GDAL allows file formats to make pre-built overviews available to " +"applications via the :cpp:func:`GDALRasterBand::GetOverview` and related " +"methods. However, implementing this is pretty involved, and goes beyond " +"the scope of this document for now. The GeoTIFF driver " +"(gdal/frmts/gtiff/geotiff.cpp) and related source can be reviewed for an " +"example of a file format implementing overview reporting and creation " +"support." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:505 +msgid "" +"Formats can also report that they have arbitrary overviews, by overriding" +" the :cpp:func:`GDALRasterBand::HasArbitraryOverviews` method on the " +"GDALRasterBand, returning TRUE. In this case the raster band object is " +"expected to override the :cpp:func:`GDALRasterBand::RasterIO` method " +"itself, to implement efficient access to imagery with resampling. This is" +" also involved, and there are a lot of requirements for correct " +"implementation of the RasterIO() method. An example of this can be found " +"in the OGDI and ECW formats." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:507 +msgid "" +"However, by far the most common approach to implementing overviews is to " +"use the default support in GDAL for external overviews stored in TIFF " +"files with the same name as the dataset, but the extension .ovr appended." +" In order to enable reading and creation of this style of overviews it is" +" necessary for the GDALDataset to initialize the `oOvManager` object " +"within itself. This is typically accomplished with a call like the " +"following near the end of the Open() method (after the PAM " +":cpp:func:`GDALDataset::TryLoadXML`)." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:513 +msgid "" +"This will enable default implementations for reading and creating " +"overviews for the format. It is advised that this be enabled for all " +"simple file system based formats unless there is a custom overview " +"mechanism to be tied into." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:516 +msgid "File Creation" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:518 +msgid "" +"There are two approaches to file creation. The first method is called the" +" :cpp:func:`GDALDriver::CreateCopy` method, and involves implementing a " +"function that can write a file in the output format, pulling all imagery " +"and other information needed from a source GDALDataset. The second " +"method, the dynamic creation method, involves implementing a Create " +"method to create the shell of the file, and then the application writes " +"various information by calls to set methods." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:520 +msgid "" +"The benefits of the first method are that that all the information is " +"available at the point the output file is being created. This can be " +"especially important when implementing file formats using external " +"libraries which require information like color maps, and georeferencing " +"information at the point the file is created. The other advantage of this" +" method is that the CreateCopy() method can read some kinds of " +"information, such as min/max, scaling, description and GCPs for which " +"there are no equivalent set methods." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:522 +msgid "" +"The benefits of the second method are that applications can create an " +"empty new file, and write results to it as they become available. A " +"complete image of the desired data does not have to be available in " +"advance." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:524 +msgid "" +"For very important formats both methods may be implemented, otherwise do " +"whichever is simpler, or provides the required capabilities." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:527 +msgid "CreateCopy" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:529 +msgid "" +"The GDALDriver::CreateCopy() method call is passed through directly, so " +"that method should be consulted for details of arguments. However, some " +"things to keep in mind are:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:531 +msgid "" +"If the `bStrict` flag is FALSE the driver should try to do something " +"reasonable when it cannot exactly represent the source dataset, " +"transforming data types on the fly, dropping georeferencing and so forth." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:532 +msgid "" +"Implementing progress reporting correctly is somewhat involved. The " +"return result of the progress function needs always to be checked for " +"cancellation, and progress should be reported at reasonable intervals. " +"The JPEGCreateCopy() method demonstrates good handling of the progress " +"function." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:533 +msgid "" +"Special creation options should be documented in the on-line help. If the" +" options take the format \"NAME=VALUE\" the papszOptions list can be " +"manipulated with :cpp:func:`CPLFetchNameValue` as demonstrated in the " +"handling of the QUALITY and PROGRESSIVE flags for JPEGCreateCopy()." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:534 +msgid "" +"The returned GDALDataset handle can be in ReadOnly or Update mode. Return" +" it in Update mode if practical, otherwise in ReadOnly mode is fine." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:536 +msgid "" +"The full implementation of the CreateCopy function for JPEG (which is " +"assigned to pfnCreateCopy in the GDALDriver object) is here. static " +"GDALDataset *" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:644 +msgid "Dynamic Creation" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:646 +msgid "" +"In the case of dynamic creation, there is no source dataset. Instead the " +"size, number of bands, and pixel data type of the desired file is " +"provided but other information (such as georeferencing, and imagery data)" +" would be supplied later via other method calls on the resulting " +"GDALDataset." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:648 +msgid "" +"The following sample implement PCI .aux labeled raw raster creation. It " +"follows a common approach of creating a blank, but valid file using non-" +"GDAL calls, and then calling GDALOpen(,GA_Update) at the end to return a " +"writable file handle. This avoids having to duplicate the various setup " +"actions in the Open() function." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:753 +msgid "" +"File formats supporting dynamic creation, or even just update-in-place " +"access also need to implement an IWriteBlock() method on the raster band " +"class. It has semantics similar to IReadBlock(). As well, for various " +"esoteric reasons, it is critical that a FlushCache() method be " +"implemented in the raster band destructor. This is to ensure that any " +"write cache blocks for the band be flushed out before the destructor is " +"called." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:756 +msgid "RawDataset/RawRasterBand Helper Classes" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:758 +msgid "" +"Many file formats have the actual imagery data stored in a regular, " +"binary, scanline oriented format. Rather than re-implement the access " +"semantics for this for each formats, there are provided " +":cpp:class:`RawDataset` and :cpp:class:`RawRasterBand` classes declared " +"in gcore/ that can be utilized to implement efficient and convenient " +"access." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:760 +msgid "" +"In these cases the format specific band class may not be required, or if " +"required it can be derived from RawRasterBand. The dataset class should " +"be derived from RawDataset." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:762 +msgid "" +"The Open() method for the dataset then instantiates raster bands passing " +"all the layout information to the constructor. For instance, the PNM " +"driver uses the following calls to create it's raster bands." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:785 +msgid "The RawRasterBand takes the following arguments." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:787 +msgid "" +"poDS: The GDALDataset this band will be a child of. This dataset must be " +"of a class derived from RawRasterDataset." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:788 +msgid "nBand: The band it is on that dataset, 1 based." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:789 +msgid "fpRaw: The FILE * handle to the file containing the raster data." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:790 +msgid "" +"nImgOffset: The byte offset to the first pixel of raster data for the " +"first scanline." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:791 +msgid "" +"nPixelOffset: The byte offset from the start of one pixel to the start of" +" the next within the scanline." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:792 +msgid "" +"nLineOffset: The byte offset from the start of one scanline to the start " +"of the next." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:793 +msgid "eDataType: The GDALDataType code for the type of the data on disk." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:794 +msgid "" +"bNativeOrder: FALSE if the data is not in the same endianness as the " +"machine GDAL is running on. The data will be automatically byte swapped." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:796 +msgid "" +"Simple file formats utilizing the Raw services are normally placed all " +"within one file in the gdal/frmts/raw directory. There are numerous " +"examples there of format implementation." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:799 +msgid "Metadata, and Other Exotic Extensions" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:801 +msgid "" +"There are various other items in the GDAL data model, for which virtual " +"methods exist on the GDALDataset and GDALRasterBand. They include:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:803 +msgid "" +"Metadata: Name/value text values about a dataset or band. The " +"GDALMajorObject (base class for GDALRasterBand and GDALDataset) has " +"built-in support for holding metadata, so for read access it only needs " +"to be set with calls to SetMetadataItem() during the Open(). The SAR_CEOS" +" (frmts/ceos2/sar_ceosdataset.cpp) and GeoTIFF drivers are examples of " +"drivers implementing readable metadata." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:805 +msgid "" +"ColorTables: GDT_Byte raster bands can have color tables associated with " +"them. The frmts/png/pngdataset.cpp driver contains an example of a format" +" that supports colortables." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:807 +msgid "" +"ColorInterpretation: The PNG driver contains an example of a driver that " +"returns an indication of whether a band should be treated as a Red, " +"Green, Blue, Alpha or Greyscale band." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:809 +msgid "" +"GCPs: GDALDatasets can have a set of ground control points associated " +"with them (as opposed to an explicit affine transform returned by " +"GetGeotransform()) relating the raster to georeferenced coordinates. The " +"MFF2 (gdal/frmts/raw/hkvdataset.cpp) format is a simple example of a " +"format supporting GCPs." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:811 +msgid "" +"NoDataValue: Bands with known \"nodata\" values can implement the " +"GetNoDataValue() method. See the PAux (frmts/raw/pauxdataset.cpp) for an " +"example of this." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:813 +msgid "" +"Category Names: Classified images with names for each class can return " +"them using the GetCategoryNames() method though no formats currently " +"implement this." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:5 +msgid "Vector API tutorial" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:7 +msgid "" +"This document is intended to document using the OGR C++ classes to read " +"and write data from a file. It is strongly advised that the reader first" +" review the :ref:`vector_data_model` document describing the key classes " +"and their roles in OGR." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:12 +msgid "" +"It also includes code snippets for the corresponding functions in C and " +"Python." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:15 +msgid "Reading From OGR" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:17 +msgid "" +"For purposes of demonstrating reading with OGR, we will construct a small" +" utility for dumping point layers from an OGR data source to stdout in " +"comma-delimited format." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:21 +msgid "" +"Initially it is necessary to register all the format drivers that are " +"desired. This is normally accomplished by calling " +":cpp:func:`GDALAllRegister` which registers all format drivers built into" +" GDAL/OGR." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:25 +#: ../../source/tutorials/vector_api_tut.rst:57 +#: ../../source/tutorials/vector_api_tut.rst:88 +#: ../../source/tutorials/vector_api_tut.rst:287 +#: ../../source/tutorials/vector_api_tut.rst:335 +#: ../../source/tutorials/vector_api_tut.rst:431 +#: ../../source/tutorials/vector_api_tut.rst:537 +#: ../../source/tutorials/vector_api_tut.rst:1040 +#: ../../source/tutorials/vector_api_tut.rst:1121 +#: ../../source/tutorials/vector_api_tut.rst:1213 +#: ../../source/tutorials/vector_api_tut.rst:1237 +#: ../../source/tutorials/vector_api_tut.rst:1263 +#: ../../source/tutorials/vector_api_tut.rst:1303 +#: ../../source/tutorials/vector_api_tut.rst:1528 +#: ../../source/tutorials/vector_api_tut.rst:1598 +msgid "In C++ :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:37 +#: ../../source/tutorials/vector_api_tut.rst:70 +#: ../../source/tutorials/vector_api_tut.rst:96 +#: ../../source/tutorials/vector_api_tut.rst:234 +#: ../../source/tutorials/vector_api_tut.rst:310 +#: ../../source/tutorials/vector_api_tut.rst:365 +#: ../../source/tutorials/vector_api_tut.rst:438 +#: ../../source/tutorials/vector_api_tut.rst:615 +#: ../../source/tutorials/vector_api_tut.rst:1060 +#: ../../source/tutorials/vector_api_tut.rst:1103 +#: ../../source/tutorials/vector_api_tut.rst:1135 +#: ../../source/tutorials/vector_api_tut.rst:1222 +#: ../../source/tutorials/vector_api_tut.rst:1248 +#: ../../source/tutorials/vector_api_tut.rst:1276 +#: ../../source/tutorials/vector_api_tut.rst:1382 +#: ../../source/tutorials/vector_api_tut.rst:1557 +#: ../../source/tutorials/vector_api_tut.rst:1624 +msgid "In C :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:48 +msgid "" +"Next we need to open the input OGR datasource. Datasources can be files," +" RDBMSes, directories full of files, or even remote web services " +"depending on the driver being used. However, the datasource name is " +"always a single string. In this case we are hardcoded to open a " +"particular shapefile. The second argument (GDAL_OF_VECTOR) tells the " +":cpp:func:`OGROpen` method that we want a vector driver to be use and " +"that don't require update access. On failure NULL is returned, and we " +"report an error." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:83 +msgid "" +"A GDALDataset can potentially have many layers associated with it. The " +"number of layers available can be queried with " +":cpp:func:`GDALDataset::GetLayerCount` and individual layers fetched by " +"index using :cpp:func:`GDALDataset::GetLayer`. However, we will just " +"fetch the layer by name." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:105 +msgid "" +"Now we want to start reading features from the layer. Before we start we" +" could assign an attribute or spatial filter to the layer to restrict the" +" set of feature we get back, but for now we are interested in getting all" +" features." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:109 +#: ../../source/tutorials/vector_api_tut.rst:155 +msgid "With GDAL 2.3 and C++11:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:116 +msgid "With GDAL 2.3 and C:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:123 +msgid "" +"If using older GDAL versions, while it isn't strictly necessary in this " +"circumstance since we are starting fresh with the layer, it is often wise" +" to call :cpp:func:`OGRLayer::ResetReading` to ensure we are starting at " +"the beginning of the layer. We iterate through all the features in the " +"layer using OGRLayer::GetNextFeature(). It will return NULL when we run " +"out of features." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:129 +#: ../../source/tutorials/vector_api_tut.rst:195 +msgid "With GDAL < 2.3 and C++ :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:140 +msgid "With GDAL < 2.3 and C :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:150 +msgid "" +"In order to dump all the attribute fields of the feature, it is helpful " +"to get the :cpp:class:`OGRFeatureDefn`. This is an object, associated " +"with the layer, containing the definitions of all the fields. We loop " +"over all the fields, and fetch and report the attributes based on their " +"type." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:276 +msgid "" +"There are a few more field types than those explicitly handled above, but" +" a reasonable representation of them can be fetched with the " +":cpp:func:`OGRFeature::GetFieldAsString` method. In fact we could " +"shorten the above by using GetFieldAsString() for all the types." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:281 +msgid "" +"Next we want to extract the geometry from the feature, and write out the " +"point geometry x and y. Geometries are returned as a generic " +":cpp:class:`OGRGeometry` pointer. We then determine the specific geometry" +" type, and if it is a point, we cast it to point and operate on it. If " +"it is something else we write placeholders." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:327 +msgid "" +"The :cpp:func:`wkbFlatten` macro is used above to convert the type for a " +"wkbPoint25D (a point with a z coordinate) into the base 2D geometry type " +"code (wkbPoint). For each 2D geometry type there is a corresponding 2.5D " +"type code. The 2D and 2.5D geometry cases are handled by the same C++ " +"class, so our code will handle 2D or 3D cases properly." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:333 +msgid "Several geometry fields can be associated to a feature." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:402 +msgid "" +"Note that :cpp:func:`OGRFeature::GetGeometryRef` and " +":cpp:func:`OGRFeature::GetGeomFieldRef` return a pointer to the internal " +"geometry owned by the OGRFeature. There we don't actually delete the " +"return geometry." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:408 +msgid "" +"With GDAL 2.3 and C++11, the looping over features is simply terminated " +"by a closing curly bracket." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:415 +msgid "" +"With GDAL 2.3 and C, the looping over features is simply terminated by " +"the following." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:424 +msgid "" +"For GDAL < 2.3, as the :cpp:func:`OGRLayer::GetNextFeature` method " +"returns a copy of the feature that is now owned by us. So at the end of " +"use we must free the feature. We could just \"delete\" it, but this can " +"cause problems in windows builds where the GDAL DLL has a different " +"\"heap\" from the main program. To be on the safe side we use a GDAL " +"function to delete the feature." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:446 +msgid "" +"The OGRLayer returned by :cpp:func:`GDALDataset::GetLayerByName` is also " +"a reference to an internal layer owned by the GDALDataset so we don't " +"need to delete it. But we do need to delete the datasource in order to " +"close the input file. Once again we do this with a custom delete method " +"to avoid special win32 heap issues." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:452 +#: ../../source/tutorials/vector_api_tut.rst:1293 +msgid "In C/C++ :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:460 +msgid "All together our program looks like this." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:462 +msgid "With GDAL 2.3 and C++11 :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:744 +msgid "Reading From OGR using the Arrow C Stream data interface" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:748 +msgid "" +"Instead of retrieving features one at a time, it is also possible to " +"retrieve them by batches, with a column-oriented memory layout, using the" +" :cpp:func:`OGRLayer::GetArrowStream` method. Note that this method is " +"more difficult to use than the traditional " +":cpp:func:`OGRLayer::GetNextFeature` approach, and is only advised when " +"compatibility with the `Apache Arrow C Stream interface " +"<https://arrow.apache.org/docs/format/CStreamInterface.html>`_ is needed," +" or when column-oriented consumption of layers is required." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:756 +msgid "" +"Pending using an helper library, consumption of the Arrow C Stream " +"interface requires reading of the following documents:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:759 +msgid "" +"`Arrow C Stream interface " +"<https://arrow.apache.org/docs/format/CStreamInterface.html>`_" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:760 +#: ../../source/tutorials/vector_api_tut.rst:1686 +msgid "" +"`Arrow C data interface " +"<https://arrow.apache.org/docs/format/CDataInterface.html>`_" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:761 +#: ../../source/tutorials/vector_api_tut.rst:1687 +msgid "" +"`Arrow Columnar Format " +"<https://arrow.apache.org/docs/format/Columnar.html>`_." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:763 +msgid "" +"The Arrow C Stream interface interface consists of a set of C structures," +" ArrowArrayStream, that provides two main callbacks to get:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:766 +msgid "" +"a ArrowSchema with the get_schema() callback. A ArrowSchema describes a " +"set of field descriptions (name, type, metadata). All OGR data types have" +" a corresponding Arrow data type." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:770 +msgid "" +"a sequence of ArrowArray with the get_next() callback. A ArrowArray " +"captures a set of values for a specific column/field in a subset of " +"features. This is the equivalent of a `Series " +"<https://arrow.apache.org/docs/python/pandas.html#series>`_ in a Pandas " +"DataFrame. This is a potentially hiearchical structure that can aggregate" +" sub arrays, and in OGR usage, the main array will be a StructArray which" +" is the collection of OGR attribute and geometry fields. The layout of " +"buffers and children arrays per data type is detailed in the `Arrow " +"Columnar Format <https://arrow.apache.org/docs/format/Columnar.html>`_." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:780 +msgid "" +"If a layer consists of 4 features with 2 fields (one of integer type, one" +" of floating-point type), the representation as a ArrowArray is " +"*conceptually* the following one:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:789 +msgid "" +"The content of a whole layer can be seen as a sequence of record batches," +" each record batches being an ArrowArray of a subset of features. Instead" +" of iterating over individual features, one iterates over a batch of " +"several features at once." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:794 +msgid "" +"The ArrowArrayStream, ArrowSchema, ArrowArray structures are defined in a" +" ogr_recordbatch.h public header file, directly derived from " +"https://github.com/apache/arrow/blob/main/cpp/src/arrow/c/abi.h to get " +"API/ABI compatibility with Apache Arrow C++. This header file must be " +"explicitly included when the related array batch API is used." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:800 +msgid "The GetArrowStream() method has the following signature:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:807 +msgid "It is also available in the C API as :cpp:func:`OGR_L_GetArrowStream`." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:809 +msgid "" +"out_stream is a pointer to a ArrowArrayStream structure, that can be in a" +" uninitialized state (the method will ignore any initial content)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:812 +msgid "" +"On successful return, and when the stream interfaces is no longer needed," +" it must must be freed with out_stream->release(out_stream)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:815 +msgid "" +"There are extra precautions to take into account in a OGR context. Unless" +" otherwise specified by a particular driver implementation, the " +"ArrowArrayStream structure, and the ArrowSchema or ArrowArray objects its" +" callbacks have returned, should no longer be used (except for " +"potentially being released) after the OGRLayer from which it was " +"initialized has been destroyed (typically at dataset closing). " +"Furthermore, unless otherwise specified by a particular driver " +"implementation, only one ArrowArrayStream can be active at a time on a " +"given layer (that is the last active one must be explicitly released " +"before a next one is asked). Changing filter state, ignored columns, " +"modifying the schema or using ResetReading()/GetNextFeature() while using" +" a ArrowArrayStream is strongly discouraged and may lead to unexpected " +"results. As a rule of thumb, no OGRLayer methods that affect the state of" +" a layer should be called on a layer, while an ArrowArrayStream on it is " +"active." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:829 +msgid "" +"The papszOptions that may be provided is a NULL terminated list of " +"key=value strings, that may be driver specific." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:832 +msgid "OGRLayer has a base implementation of GetArrowStream() that is such:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:834 +msgid "" +"The get_schema() callback returns a schema whose top-level object " +"returned is of type Struct, and whose children consist of the FID column," +" all OGR attribute fields and geometry fields to Arrow fields. The FID " +"column may be omitted by providing the INCLUDE_FID=NO option." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:839 +msgid "" +"When get_schema() returns 0, and the schema is no longer needed, it must " +"be released with the following procedure, to take into account that it " +"might have been released by other code, as documented in the Arrow C data" +" interface:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:850 +msgid "The get_next() callback retrieve the next record batch over the layer." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:852 +msgid "" +"out_array is a pointer to a ArrowArray structure, that can be in a " +"uninitialized state (the method will ignore any initial content)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:855 +msgid "" +"The default implementation uses GetNextFeature() internally to retrieve " +"batches of up to 65,536 features (configurable with the " +"MAX_FEATURES_IN_BATCH=num option). The starting address of buffers " +"allocated by the default implementation is aligned on 64-byte boundaries." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:860 +msgid "" +"The default implementation outputs geometries as WKB in a binary field, " +"whose corresponding entry in the schema is marked with the metadata item " +"``ARROW:extension:name`` set to ``ogc.wkb``. Specialized implementations " +"may output by default other formats (particularly the Arrow driver that " +"can return geometries encoded according to the GeoArrow specification " +"(using a list of coordinates). The GEOMETRY_ENCODING=WKB option can be " +"passed to force the use of WKB (through the default implementation)" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:868 +msgid "" +"The method may take into account ignored fields set with " +"SetIgnoredFields() (the default implementation does), and should take " +"into account filters set with SetSpatialFilter() and " +"SetAttributeFilter(). Note however that specialized implementations may " +"fallback to the default (slower) implementation when filters are set." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:873 +msgid "" +"Mixing calls to GetNextFeature() and get_next() is not recommended, as " +"the behavior will be unspecified (but it should not crash)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:876 +msgid "" +"When get_next() returns 0, and the array is no longer needed, it must be " +"released with the following procedure, to take into account that it might" +" have been released by other code, as documented in the Arrow C data " +"interface:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:886 +msgid "" +"Drivers that have a specialized implementation advertise the new " +"OLCFastGetArrowStream layer capability." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:889 +msgid "" +"Using directly (as a producer or a consumer) a ArrowArray is admittedly " +"not trivial, and requires good intimacy with the Arrow C data interface " +"and columnar array specifications, to know, in which buffer of an array, " +"data is to be read, which data type void* buffers should be cast to, how " +"to use buffers that contain null/not_null information, how to use offset " +"buffers for data types of type List, etc. The study of the " +"gdal_array._RecordBatchAsNumpy() method of the SWIG Python bindings " +"(:source_file:`swig/include/gdal_array.i`) can give a good hint of how to" +" use an ArrowArray object, in conjunction with the associated " +"ArrowSchema." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:899 +msgid "" +"The below example illustrates how to read the content of a layer that " +"consists of a integer field and a geometry field:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1028 +msgid "" +"To write features by batches using an ArrowArray, consult " +":ref:`vector_api_tut_arrow_write`." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1031 +msgid "Writing To OGR" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1033 +msgid "" +"As an example of writing through OGR, we will do roughly the opposite of " +"the above. A short program that reads comma separated values from input " +"text will be written to a point shapefile via OGR." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1037 +msgid "" +"As usual, we start by registering all the drivers, and then fetch the " +"Shapefile driver as we will need it to create our output file." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1080 +msgid "" +"Next we create the datasource. The ESRI Shapefile driver allows us to " +"create a directory full of shapefiles, or a single shapefile as a " +"datasource. In this case we will explicitly create a single file by " +"including the extension in the name. Other drivers behave differently. " +"The second, third, fourth and fifth argument are related to raster " +"dimensions (in case the driver has raster capabilities). The last " +"argument to the call is a list of option values, but we will just be " +"using defaults in this case. Details of the options supported are also " +"format specific." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1089 +msgid "In C ++ :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1116 +msgid "" +"Now we create the output layer. In this case since the datasource is a " +"single file, we can only have one layer. We pass wkbPoint to specify the" +" type of geometry supported by this layer. In this case we aren't " +"passing any coordinate system information or other special layer creation" +" options." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1149 +msgid "" +"Now that the layer exists, we need to create any attribute fields that " +"should appear on the layer. Fields must be added to the layer before any" +" features are written. To create a field we initialize an " +":cpp:union:`OGRField` object with the information about the field. In " +"the case of Shapefiles, the field width and precision is significant in " +"the creation of the output .dbf file, so we set it specifically, though " +"generally the defaults are OK. For this example we will just have one " +"attribute, a name string associated with the x,y point." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1157 +msgid "" +"Note that the template OGRField we pass to " +":cpp:func:`OGRLayer::CreateField` is copied internally. We retain " +"ownership of the object." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1194 +msgid "" +"The following snipping loops reading lines of the form \"x,y,name\" from " +"stdin, and parsing them." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1197 +msgid "In C++ and in C :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1208 +msgid "" +"To write a feature to disk, we must create a local OGRFeature, set " +"attributes and attach geometry before trying to write it to the layer. " +"It is imperative that this feature be instantiated from the " +"OGRFeatureDefn associated with the layer it will be written to." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1231 +msgid "" +"We create a local geometry object, and assign its copy (indirectly) to " +"the feature. The :cpp:func:`OGRFeature::SetGeometryDirectly` differs from" +" :cpp:func:`OGRFeature::SetGeometry` in that the direct method gives " +"ownership of the geometry to the feature. This is generally more " +"efficient as it avoids an extra deep object copy of the geometry." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1260 +msgid "" +"Now we create a feature in the file. The " +":cpp:func:`OGRLayer::CreateFeature` does not take ownership of our " +"feature so we clean it up when done with it." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1290 +msgid "" +"Finally we need to close down the datasource in order to ensure headers " +"are written out in an orderly way and all resources are recovered." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1301 +msgid "The same program all in one block looks like this:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1461 +#: ../../source/tutorials/vector_api_tut.rst:1653 +msgid "In Python :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1522 +msgid "" +"Several geometry fields can be associated to a feature. This capability " +"is just available for a few file formats, such as PostGIS." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1525 +msgid "" +"To create such datasources, geometry fields must be first created. " +"Spatial reference system objects can be associated to each geometry " +"field." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1593 +msgid "" +"To write a feature to disk, we must create a local OGRFeature, set " +"attributes and attach geometries before trying to write it to the layer." +" It is imperative that this feature be instantiated from the " +"OGRFeatureDefn associated with the layer it will be written to." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1671 +msgid "Writing to OGR using the Arrow C Data interface" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1675 +msgid "" +"Instead of writing features one at a time, it is also possible to write " +"them by batches, with a column-oriented memory layout, using the " +":cpp:func:`OGRLayer::WriteArrowBatch` method. Note that this method is " +"more difficult to use than the traditional " +":cpp:func:`OGRLayer::CreateFeature` approach, and is only advised when " +"compatibility with the `Apache Arrow C Data interface " +"<https://arrow.apache.org/docs/format/CDataInterface.html>`_ is needed, " +"or when column-oriented writing of layers is required." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1683 +msgid "" +"Pending using an helper library, generation of the Arrow C Data interface" +" requires reading of the following documents:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1689 +msgid "" +"Consult :ref:`vector_api_tut_arrow_stream` for introduction to the " +"ArrowSchema and ArrowArray basic types involved for batch writing." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1692 +msgid "The WriteArrowBatch() method has the following signature:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1708 +msgid "It is also available in the C API as :cpp:func:`OGR_L_WriteArrowBatch`." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1710 +msgid "" +"This is semantically close to calling " +":cpp:func:`OGRLayer::CreateFeature()` with multiple features at once." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1713 +msgid "" +"The ArrowArray must be of type struct (format=+s), and its children " +"generally map to a OGR attribute or geometry field (unless they are " +"struct themselves)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1716 +msgid "" +"Method :cpp:func:`OGRLayer::IsArrowSchemaSupported` can be called to " +"determine if the schema will be supported by WriteArrowBatch()." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1719 +msgid "" +"OGR fields for the corresponding children arrays must exist and be of a " +"compatible type. For attribute fields, they should be created with " +":cpp:func:`OGRLayer::CreateFieldFromArrowSchema`." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1723 +msgid "" +"Arrays for geometry columns should be of binary or large binary type and " +"contain WKB geometry." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1726 +msgid "" +"Note that the passed array may be set to a released state " +"(array->release==NULL) after this call (not by the base implementation, " +"but in specialized ones such as Parquet or Arrow for example)" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1730 +msgid "Supported options of the base implementation are:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1732 +msgid "" +"FID=name. Name of the FID column in the array. If not provided, " +"GetFIDColumn() is used to determine it. The special name " +"OGRLayer::DEFAULT_ARROW_FID_NAME is also recognized if neither FID nor " +"GetFIDColumn() are set. The corresponding ArrowArray must be of type " +"int32 (i) or int64 (l). On input, values of the FID column are used to " +"create the feature. On output, the values of the FID column may be set " +"with the FID of the created feature (if the array is not released)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1741 +msgid "" +"GEOMETRY_NAME=name. Name of the geometry column. If not provided, " +"GetGeometryColumn() is used. The special name " +"OGRLayer::DEFAULT_ARROW_GEOMETRY_NAME is also recognized if neither " +"GEOMETRY_NAME nor GetGeometryColumn() are set. Geometry columns are also " +"identified if they have ARROW:extension:name=ogc.wkb as a field metadata." +" The corresponding ArrowArray must be of type binary (w) or large binary " +"(W)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1750 +msgid "" +"Drivers that have a specialized implementation (such as " +":ref:`vector.parquet` and :ref:`vector.arrow`) advertise the " +"OLCFastWriteArrowBatch layer capability." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1753 +msgid "" +"The following example in Python demonstrates how to copy a layer from one" +" format to another one (assuming it has at most a single geometry " +"column):" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1821 +msgid "" +"For the Python bindings, in addition to the above " +"ogr.Layer.IsArrowSchemaSupported(), " +"ogr.Layer.CreateFieldFromArrowSchema() and ogr.Layer.WriteArrowBatch() " +"methods, 3 similar methods exist using the `PyArrow " +"<https://arrow.apache.org/docs/python/index.html>`__ data types:" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:5 +msgid "Vector driver implementation tutorial" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:12 +msgid "" +"In general new formats are added to OGR by implementing format specific " +"drivers with instantiating a :cpp:class:`GDALDriver` and subclasses of " +":cpp:class:`GDALDataset` and :cpp:class:`OGRLayer`. The GDALDriver " +"instance is registered with the :cpp:class:`GDALDriverManager` at " +"runtime." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:17 +msgid "" +"Before following this tutorial to implement an OGR driver, please review " +"the :ref:`vector_data_model` document carefully." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:20 +msgid "The tutorial will be based on implementing a simple ascii point format." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:23 +msgid "Implementing GDALDriver" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:25 +msgid "" +"The format specific driver class is implemented as a instance of " +"GDALDriver. One instance of the driver will normally be created, and " +"registered with the GDALDriverManager. The instantiation of the driver " +"is normally handled by a global C callable registration function, similar" +" to the following placed in the same file as the driver class." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:55 +msgid "" +"The :cpp:func:`GDALDriver::SetDescription` sets the name of the driver. " +"This name is specified on the commandline when creating datasources so it" +" is generally good to keep it short and without any special characters or" +" spaces." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:59 +msgid "" +"SetMetadataItem( GDAL_DCAP_VECTOR, \"YES\" ) is specified to indicate " +"that the driver will handle vector data." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:62 +msgid "" +"SetMetadataItem( GDAL_DCAP_VIRTUALIO, \"YES\" ) is specified to indicate " +"that the driver can deal with files opened with the VSI*L GDAL API. " +"Otherwise this metadata item should not be defined." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:68 +msgid "" +"The driver declaration generally looks something like this for a format " +"with read or read and update access (the Open() method) and creation " +"support (the Create() method)." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:81 +msgid "" +"The Open() method is called by :cpp:func:`GDALOpenEx`. It should quietly " +"return NULL if the passed filename is not of the format supported by the " +"driver. If it is the target format, then a new GDALDataset object for " +"the dataset should be returned." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:85 +msgid "" +"It is common for the Open() method to be delegated to an Open() method on" +" the actual format's GDALDataset class." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:106 +msgid "The Identify() method is implemented as such :" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:118 +msgid "" +"Examples of the Create() method is left for the section on creation and " +"update." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:121 +msgid "Basic Read Only Data Source" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:123 +msgid "" +"We will start implementing a minimal read-only datasource. No attempt is" +" made to optimize operations, and default implementations of many methods" +" inherited from GDALDataset are used." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:127 +msgid "" +"The primary responsibility of the datasource is to manage the list of " +"layers. In the case of the SPF format a datasource is a single file " +"representing one layer so there is at most one layer. The \"name\" of a " +"datasource should generally be the name passed to the Open() method." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:132 +msgid "" +"The Open() method below is not overriding a base class method, but we " +"have it to implement the open operation delegated by the driver class." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:135 +msgid "" +"For this simple case we provide a stub " +":cpp:func:`GDALDataset::TestCapability` that returns FALSE for all " +"extended capabilities. The TestCapability() method is pure virtual, so " +"it does need to be implemented." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:159 +msgid "" +"The constructor is a simple initializer to a default state. The Open() " +"will take care of actually attaching it to a file. The destructor is " +"responsible for orderly cleanup of layers." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:180 +msgid "" +"The Open() method is the most important one on the datasource, though in " +"this particular instance it passes most of its work off to the " +"OGRSPFLayer constructor if it believes the file is of the desired format." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:184 +msgid "" +"Note that Open() methods should try and determine that a file isn't of " +"the identified format as efficiently as possible, since many drivers may " +"be invoked with files of the wrong format before the correct driver is " +"reached. In this particular Open() we just test the file extension but " +"this is generally a poor way of identifying a file format. If available," +" checking \"magic header values\" or something similar is preferable." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:191 +msgid "" +"In the case of the SPF format, update in place is not supported, so we " +"always fail if bUpdate is FALSE." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:218 +msgid "" +"A GetLayer() method also needs to be implemented. Since the layer list " +"is created in the Open() this is just a lookup with some safety testing." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:234 +msgid "Read Only Layer" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:236 +msgid "" +"The OGRSPFLayer is implements layer semantics for an .spf file. It " +"provides access to a set of feature objects in a consistent coordinate " +"system with a particular set of attribute columns. Our class definition " +"looks like this:" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:263 +msgid "" +"The layer constructor is responsible for initialization. The most " +"important initialization is setting up the :cpp:class:`OGRFeatureDefn` " +"for the layer. This defines the list of fields and their types, the " +"geometry type and the coordinate system for the layer. In the SPF format" +" the set of fields is fixed - a single string field and we have no " +"coordinate system info to set." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:269 +msgid "" +"Pay particular attention to the reference counting of the OGRFeatureDefn." +" As OGRFeature's for this layer will also take a reference to this " +"definition, it is important that we also establish a reference on behalf " +"of the layer itself." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:295 +msgid "" +"Note that the destructor uses :cpp:func:`OGRFeatureDefn::Release` on the " +"OGRFeatureDefn. This will destroy the feature definition if the " +"reference count drops to zero, but if the application is still holding " +"onto a feature from this layer, then that feature will hold a reference " +"to the feature definition and it will not be destroyed here (which is " +"good!)." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:311 +msgid "" +"The :cpp:func:`OGRLayer::GetNextFeature` method is usually the work horse" +" of OGRLayer implementations. It is responsible for reading the next " +"feature according to the current spatial and attribute filters installed." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:315 +msgid "" +"The while() loop is present to loop until we find a satisfactory feature." +" The first section of code is for parsing a single line of the SPF text " +"file and establishing the x, y and name for the line." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:351 +msgid "" +"The next section turns the x, y and name into a feature. Also note that " +"we assign a linearly incremented feature id. In our case we started at " +"zero for the first feature, though some drivers start at 1." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:364 +msgid "" +"Next we check if the feature matches our current attribute or spatial " +"filter if we have them. Methods on the OGRLayer base class support " +"maintain filters in the OGRLayer member fields " +":cpp:member:`OGRLayer::m_poFilterGeom` (spatial filter) and " +":cpp:member:`OGRLayer::m_poAttrQuery` (attribute filter) so we can just " +"use these values here if they are non-NULL. The following test is " +"essentially \"stock\" and done the same in all formats. Some formats " +"also do some spatial filtering ahead of time using a spatial index." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:372 +msgid "" +"If the feature meets our criteria we return it. Otherwise we destroy it," +" and return to the top of the loop to fetch another to try." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:387 +msgid "" +"While in the middle of reading a feature set from a layer, or at any " +"other time the application can call :cpp:func:`OGRLayer::ResetReading` " +"which is intended to restart reading at the beginning of the feature set." +" We implement this by seeking back to the beginning of the file, and " +"resetting our feature id counter." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:400 +msgid "" +"In this implementation we do not provide a custom implementation for the " +"GetFeature() method. This means an attempt to read a particular feature " +"by its feature id will result in many calls to GetNextFeature() until the" +" desired feature is found. However, in a sequential text format like spf" +" there is little else we could do anyway." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:406 +msgid "There! We have completed a simple read-only feature file format driver." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:5 +msgid "Vector driver in Python implementation tutorial" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:14 +msgid "" +"Since GDAL 3.1, the capability of writing read-only vector drivers in " +"Python has been added. It is strongly advised to read the " +":ref:`vector_driver_tut` first, which will give the general principles of" +" how a vector driver works." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:18 +msgid "" +"This capability does not require the use of the GDAL/OGR SWIG Python " +"bindings (but a vector Python driver may use them.)" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:21 +msgid "" +"Note: per project policies, this is considered as an \"experimental\" " +"feature and the GDAL project will not accept such Python drivers to be " +"included in the GDAL repository. Drivers aiming at inclusion in GDAL " +"master should priorly be ported to C++. The rationale for this is that:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:26 +msgid "" +"the correctness of the Python code can mostly be checked at runtime, " +"whereas C++ benefits from static analysis (at compile time, and other " +"checkers)." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:28 +msgid "" +"Python code is executed under the Python Global Interpreter Lock, which " +"makes them not scale." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:30 +msgid "Not all builds of GDAL have Python available." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:34 +msgid "Linking mechanism to a Python interpreter" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:36 +msgid "See :ref:`linking_mechanism_to_python_interpreter`" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:39 +msgid "Driver location" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:41 +msgid "" +"Driver filenames must start with `gdal_` or `ogr_` and have the `.py` " +"extension. They will be searched in the following directies:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:44 +msgid "" +"the directory pointed by the ``GDAL_PYTHON_DRIVER_PATH`` configuration " +"option (there may be several paths separated by `:` on Unix or `;` on " +"Windows)" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:46 +msgid "" +"if not defined, the directory pointed by the ``GDAL_DRIVER_PATH`` " +"configuration option." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:48 +msgid "" +"if not defined, in the directory (hardcoded at compilation time on Unix " +"builds) where native plugins are located." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:51 +msgid "" +"GDAL does not try to manage Python dependencies that are imported by the " +"driver .py script. It is up to the user to make sure its current Python " +"environment has all required dependencies installed." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:56 +msgid "Import section" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:58 +msgid "Drivers must have the following import section to load the base classes." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:64 +msgid "" +"The ``gdal_python_driver`` module is created dynamically by GDAL and is " +"not present on the file system." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:68 +msgid "Metadata section" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:70 +msgid "" +"In the first 1000 lines of the .py file, a number of required and " +"optional KEY=VALUE driver directives must be defined. They are parsed by " +"C++ code, without using the Python interpreter, so it is vital to respect" +" the following constraints:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:75 +msgid "" +"each declaration must be on a single line, and start with ``# gdal: " +"DRIVER_`` (space character between sharp character and gdal, and between " +"colon character and DRIVER\\_)" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:77 +msgid "" +"the value must be a literal value of type string (except for # gdal: " +"DRIVER_SUPPORTED_API_VERSION which can accept an array of integers), " +"without expressions, function calls, escape sequences, etc." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:80 +msgid "strings may be single or double-quoted" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:82 +msgid "The following directives must be declared:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:84 +msgid "``# gdal: DRIVER_NAME = \"NAME\"``: the short name of the driver" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:85 +msgid "" +"``# gdal: DRIVER_SUPPORTED_API_VERSION = [1]``: the API version(s) " +"supported by the driver. Must include 1, which is the only currently " +"supported version in GDAL 3.1" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:87 +msgid "``# gdal: DRIVER_DCAP_VECTOR = \"YES\"``: declares a vector driver" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:88 +msgid "``# gdal: DRIVER_DMD_LONGNAME = \"a longer name of the driver\"``" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:90 +msgid "Additional directives:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:92 +msgid "" +"``# gdal: DRIVER_DMD_EXTENSIONS = \"ext1 ext2\"``: list of extension(s) " +"recognized by the driver, without the dot, and separated by space" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:94 +msgid "" +"``# gdal: DRIVER_DMD_HELPTOPIC = \"https://example.com/my_help.html\"``: " +"URL to a help page for the driver" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:96 +msgid "" +"``# gdal: DRIVER_DMD_OPENOPTIONLIST = \"<OpenOptionList><Option " +"name='OPT1' type='boolean' description='bla' " +"default='NO'/></OpenOptionList>\"`` where the XML is an " +"``OptionOptionList``." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:98 +msgid "" +"and all other metadata items found in gdal.h starting with ``GDAL_DMD_`` " +"or ``GDAL_DCAP`` by creating an item name which starts with ``# gdal: " +"DRIVER_`` and the value of the ``GDAL_DMD_`` or ``GDAL_DCAP`` metadata " +"item. For example ``#define GDAL_DMD_CONNECTION_PREFIX " +"\"DMD_CONNECTION_PREFIX\"`` becomes ``# gdal: " +"DRIVER_DMD_CONNECTION_PREFIX``" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:104 +#: ../../source/tutorials/vector_python_driver.rst:144 +#: ../../source/tutorials/vector_python_driver.rst:175 +#: ../../source/tutorials/vector_python_driver.rst:201 +msgid "Example:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:116 +msgid "Driver class" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:118 +msgid "" +"The entry point .py script must contains a single class that inherits " +"from ``gdal_python_driver.BaseDriver``." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:121 +msgid "That class must define the following methods:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst +msgid "Parameters" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:126 +#: ../../source/tutorials/vector_python_driver.rst:137 +msgid "File name, or more generally, connection string." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:127 +#: ../../source/tutorials/vector_python_driver.rst:138 +msgid "" +"First bytes of the file (if it is a file). At least 1024 (if the file has" +" at least 1024 bytes), or more if a native driver in the driver probe " +"sequence has requested more previously." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:129 +#: ../../source/tutorials/vector_python_driver.rst:140 +msgid "Open flags. To be ignored for now." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:130 +#: ../../source/tutorials/vector_python_driver.rst:141 +msgid "Open options." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst +msgid "Returns" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:131 +msgid "" +"True if the file is recognized by the driver, False if not, or -1 if that" +" cannot be known from the first bytes." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:142 +msgid "an object deriving from gdal_python_driver.BaseDataset or None" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:162 +msgid "Dataset class" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:164 +msgid "" +"The Driver.open() method on success should return an object from a class " +"that inherits from ``gdal_python_driver.BaseDataset``." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:168 +msgid "Layers" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:170 +msgid "" +"The role of this object is to store vector layers. There are two " +"implementation options. If the number of layers is small or they are fast" +" to construct, then the ``__init__`` method can defined a ``layers`` " +"attribute that is a sequence of objects from a class that inherits from " +"``gdal_python_driver.BaseLayer``." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:184 +msgid "Otherwise, the following two methods should be defined:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:189 +msgid "the number of layers" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:194 +msgid "" +"Index of the layer to return. Normally between 0 and self.layer_count() -" +" 1, but calling code might pass any value. In case of invalid index, None" +" should be returned." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:197 +msgid "" +"an object deriving from gdal_python_driver.BaseLayer or None. The C++ " +"code will take care of caching that object, and this method will only be " +"called once for a given idx value." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:214 +msgid "Metadata" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:216 +msgid "" +"The dataset may define a ``metadata`` dictionary, in ``__init__`` of key:" +" value of type string, for the default metadata domain. Alternatively, " +"the following method may be implemented." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:223 +msgid "metadata domain. Empty string for the default one" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:224 +msgid "None, or a dictionary of key:value pairs of type string;" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:227 +msgid "Other methods" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:229 +msgid "The following method may be optionally implemented:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:234 +msgid "" +"Called at the destruction of the C++ peer GDALDataset object. Useful to " +"close database connections for example." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:239 +msgid "Layer class" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:241 +msgid "" +"The Dataset object will instantiate one or several objects from a class " +"that inherits from ``gdal_python_driver.BaseLayer``." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:245 +msgid "Metadata, and other definitions" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:247 +msgid "The following attributes are required and must defined at __init__ time:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:252 +msgid "Layer name, of type string. If not set, a ``name`` method must be defined." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:257 +msgid "" +"Sequence of field definitions (may be empty). Each field is a dictionary " +"with the following properties:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:263 +msgid "Required" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:268 +msgid "" +"A integer value of type ogr.OFT\\_ (from the SWIG Python bindings), or " +"one of the following string values: ``String``, ``Integer``, " +"``Integer16``, ``Integer64``, ``Boolean``, ``Real``, ``Float``, " +"``Binary``, ``Date``, ``Time``, ``DateTime``" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:272 +msgid "" +"If that attribute is not set, a ``fields`` method must be defined and " +"return such a sequence." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:278 +msgid "" +"Sequence of geometry field definitions (may be empty). Each field is a " +"dictionary with the following properties:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:284 +msgid "Required. May be empty" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:289 +msgid "" +"Required. A integer value of type ogr.wkb\\_ (from the SWIG Python " +"bindings), or one of the following string values: ``Unknown``, ``Point``," +" ``LineString``, ``Polygon``, ``MultiPoint``, ``MultiLineString``, " +"``MultiPolygon``, ``GeometryCollections`` or all other values returned by" +" :cpp:func:`OGRGeometryTypeToName`" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:297 +msgid "" +"The SRS attached to the geometry field as a string that can be ingested " +"by :cpp:func:`OGRSpatialReference::SetFromUserInput`, such as a PROJ " +"string, WKT string, or ``AUTHORITY:CODE``." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:301 +msgid "" +"If that attribute is not set, a ``geometry_fields`` method must be " +"defined and return such a sequence." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:304 +msgid "The following attributes are optional:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:309 +msgid "" +"Feature ID column name, of type string. May be empty string. If not set, " +"a ``fid_name`` method may be defined." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:315 +msgid "" +"A dictionary of key: value strings, corresponding to metadata of the " +"default metadata domain. Alternatively, a ``metadata`` method that " +"accepts a domain argument may be defined." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:322 +msgid "" +"Can be set to True if the feature iterator takes into account the " +"``attribute_filter`` attribute that can be set on the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:328 +msgid "" +"Can be set to True if the feature iterator takes into account the " +"``spatial_filter`` attribute that can be set on the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:334 +msgid "" +"Can be set to True if the feature_count method takes into account the " +"``attribute_filter`` attribute that can be set on the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:340 +msgid "" +"Can be set to True if the feature_count method takes into account the " +"``spatial_filter`` attribute that can be set on the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:344 +msgid "Feature iterator" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:346 +msgid "" +"The Layer class must implement the iterator interface, so typically with " +"a ``__iter__`` method." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:349 +msgid "" +"The resulting iterator must produce dictionaries for each feature's " +"content. The keys allowed in the returned dictionary are:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:355 +msgid "" +"Strongly recommended. The value must be an integer to be recognized as a " +"FID." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:360 +msgid "Required. The value must be the string ``\"OGRFeature\"``" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:365 +msgid "" +"Required. The value must be either a dictionary whose keys are field " +"names; or None" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:370 +msgid "" +"Required. the value must be a dictionary whose keys are geometry field " +"names (possibly the empty string for unnamed geometry columns); or None." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:373 +msgid "" +"The value of each key must be either a geometry encoded as a WKT string; " +"a geometry encoded as ISO WKB as a `bytes-like object " +"<https://docs.python.org/3/glossary.html#term-bytes-like-object>`__; or " +"None." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:380 +msgid "" +"Optional. The value must be a string conforming to the " +":ref:`ogr_feature_style`." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:383 +msgid "Filtering" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:385 +msgid "" +"By default, any attribute or spatial filter set by the user of the OGR " +"API will be evaluated by the generic C++ side of the driver, by iterating" +" over all features of the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:389 +msgid "" +"If the ``iterator_honour_attribute_filter`` (resp. " +"``iterator_honour_spatial_filter``) attribute of the layer object is set " +"to ``True``, the attribute filter (resp. spatial filter) must be honoured" +" by the feature iterator method." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:393 +msgid "" +"The attribute filter is set in the ``attribute_filter`` attribute of the " +"layer object. It is a string conforming to :ref:`OGR SQL " +"<ogr_sql_dialect>`. When the attribute filter is changed by the OGR API, " +"the ``attribute_filter_changed`` optional method is called (see below " +"paragraph about optional methods). An implementation of " +"``attribute_filter_changed`` may decide to fallback on evaluation by the " +"generic C++ side of the driver by calling the ``SetAttributeFilter`` " +"method (see below passthrough example)" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:401 +msgid "" +"The geometry filter is set in the ``spatial_filter`` attribute of the " +"layer object. It is a string encoding as ISO WKT. It is the " +"responsibility of the user of the OGR API to express it in the CRS of the" +" layer. When the attribute filter is changed by the OGR API, the " +"``spatial_filter_changed`` optional method is called (see below paragraph" +" about optional methods). An implementation of ``spatial_filter_changed``" +" may decide to fallback on evaluation by the generic C++ side of the " +"driver by calling the ``SetSpatialFilter`` method (see below passthrough " +"example)" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:411 +msgid "Optional methods" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:413 +msgid "The following methods may be optionally implemented:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:418 +msgid "the list [xmin,ymin,xmax,ymax] with the spatial extent of the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:423 +msgid "the number of features of the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:425 +msgid "" +"If self.feature_count_honour_attribute_filter or " +"self.feature_count_honour_spatial_filter are set to True, the attribute " +"filter and/or spatial filter must be honoured by this method." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:432 +msgid "feature ID" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:433 +msgid "" +"a feature object in one of the formats of the ``__next__`` method " +"described above, or None if no object matches fid" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:439 +msgid "" +"This method is called whenever self.attribute_filter has been changed. It" +" is the opportunity for the driver to potentially change the value of " +"self.iterator_honour_attribute_filter or " +"feature_count_honour_attribute_filter attributes." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:447 +msgid "" +"This method is called whenever self.spatial_filter has been changed (its " +"value is a geometry encoded in WKT) It is the opportunity for the driver " +"to potentially change the value of self.iterator_honour_spatial_filter or" +" feature_count_honour_spatial_filter attributes." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:456 +msgid "" +"potential values are BaseLayer.FastGetExtent, " +"BaseLayer.FastSpatialFilter, BaseLayer.FastFeatureCount, " +"BaseLayer.RandomRead, BaseLayer.StringsAsUTF8 or other strings supported " +"by :cpp:func:`OGRLayer::TestCapability`" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:460 +msgid "True if the capability is supported, False otherwise." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:463 +msgid "Full example" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:465 +msgid "" +"The following example is a passthrough driver that forwards the calls to " +"the SWIG Python GDAL API. It has no practical use, and is just intended " +"to show case most possible uses of the API. A real-world driver will only" +" use part of the API demonstrated. For example, the passthrough driver " +"implements attribute and spatial filters in a completely dummy way, by " +"calling back the C++ part of the driver. The " +"``iterator_honour_attribute_filter`` and " +"``iterator_honour_spatial_filter`` attributes, and the " +"``attribute_filter_changed`` and ``spatial_filter_changed`` method " +"implementations, could have omitted with the same result." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:474 +msgid "" +"The connection strings recognized by the drivers are " +"``PASSHTROUGH:connection_string_supported_by_non_python_drivers``. Note " +"that the prefixing by the driver name is absolutely not a requirement, " +"but something specific to this particular driver which is a bit " +"artificial (without the prefix, the connection string would go directly " +"to the native driver). The CityJSON driver mentioned in the :ref:`Other " +"examples <other_examples>` paragraph does not need it." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:633 +msgid "" +"Other examples, including a CityJSON driver, may be found at " +"https://github.com/OSGeo/gdal/tree/master/examples/pydrivers" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:5 +msgid "GDAL Warp API tutorial (Reprojection, ...)" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:10 +msgid "Overview" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:12 +msgid "" +"The GDAL Warp API (declared in :ref:`gdalwarper.h <gdalwarp_cpp>`) " +"provides services for high performance image warping using application " +"provided geometric transformation functions (GDALTransformerFunc), a " +"variety of resampling kernels, and various masking options. Files much " +"larger than can be held in memory can be warped." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:14 +msgid "" +"This tutorial demonstrates how to implement an application using the Warp" +" API. It assumes implementation in C++ as C and Python bindings are " +"incomplete for the Warp API. It also assumes familiarity with the " +":ref:`raster_data_model`, and the general GDAL API." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:16 +msgid "" +"Applications normally perform a warp by initializing a " +":cpp:class:`GDALWarpOptions` structure with the options to be utilized, " +"instantiating a GDALWarpOperation based on these options, and then " +"invoking the :cpp:func:`GDALWarpOperation::ChunkAndWarpImage` method to " +"perform the warp options internally using the :cpp:class:`GDALWarpKernel`" +" class." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:19 +msgid "A Simple Reprojection Case" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:20 +msgid "" +"First we will construct a relatively simple example for reprojecting an " +"image, assuming an appropriate output file already exists, and with " +"minimal error checking." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:70 +msgid "" +"This example opens the existing input and output files (in.tif and " +"out.tif). A :cpp:class:`GDALWarpOptions` structure is allocated " +"(:cpp:func:`GDALCreateWarpOptions` sets lots of sensible defaults for " +"stuff, always use it for defaulting things), and the input and output " +"file handles, and band lists are set. The panSrcBands and panDstBands " +"lists are dynamically allocated here and will be free automatically by " +":cpp:func:`GDALDestroyWarpOptions`. The simple terminal output progress " +"monitor (GDALTermProgress) is installed for reporting completion progress" +" to the user." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:72 +msgid "" +":cpp:func:`GDALCreateGenImgProjTransformer` is used to initialize the " +"reprojection transformation between the source and destination images. We" +" assume that they already have reasonable bounds and coordinate systems " +"set. Use of GCPs is disabled." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:74 +msgid "" +"Once the options structure is ready, a GDALWarpOperation is instantiated " +"using them, and the warp actually performed with " +":cpp:func:`GDALWarpOperation::ChunkAndWarpImage`. Then the transformer, " +"warp options and datasets are cleaned up." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:76 +msgid "" +"Normally error check would be needed after opening files, setting up the " +"reprojection transformer (returns NULL on failure), and initializing the " +"warp." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:79 +msgid "Other Warping Options" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:81 +msgid "" +"The GDALWarpOptions structures contains a number of items that can be set" +" to control warping behavior. A few of particular interest are:" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:83 +msgid "" +":cpp:member:`GDALWarpOptions::dfWarpMemoryLimit` - Set the maximum amount" +" of memory to be used by the GDALWarpOperation when selecting a size of " +"image chunk to operate on. The value is in bytes, and the default is " +"likely to be conservative (small). Increasing the chunk size can help " +"substantially in some situations but care should be taken to ensure that " +"this size, plus the GDAL cache size plus the working set of GDAL, your " +"application and the operating system are less than the size of RAM or " +"else excessive swapping is likely to interfere with performance. On a " +"system with 256MB of RAM, a value of at least 64MB (roughly 64000000 " +"bytes) is reasonable. Note that this value does not include the memory " +"used by GDAL for low level block caching." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:85 +msgid "" +":cpp:member:`GDALWarpOptions::eResampleAlg` - One of GRA_NearestNeighbour" +" (the default, and fastest), GRA_Bilinear (2x2 bilinear resampling) or " +"GRA_Cubic. The GRA_NearestNeighbour type should generally be used for " +"thematic or color mapped images. The other resampling types may give " +"better results for thematic images, especially when substantially " +"changing resolution." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:87 +msgid "" +":cpp:member:`GDALWarpOptions::padfSrcNoDataReal` - This array (one entry " +"per band being processed) may be setup with a \"nodata\" value for each " +"band if you wish to avoid having pixels of some background value copied " +"to the destination image." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:89 +msgid "" +":cpp:member:`GDALWarpOptions::papszWarpOptions` - This is a string list " +"of NAME=VALUE options passed to the warper. See the " +":cpp:member:`GDALWarpOptions::papszWarpOptions` docs for all options. " +"Supported values include:" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:91 +msgid "" +"INIT_DEST=[value] or INIT_DEST=NO_DATA: This option forces the " +"destination image to be initialized to the indicated value (for all " +"bands) or indicates that it should be initialized to the NO_DATA value in" +" padfDstNoDataReal/padfDstNoDataImag. If this value isn't set the " +"destination image will be read and the source warp overlaid on it." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:93 +msgid "" +"WRITE_FLUSH=YES/NO: This option forces a flush to disk of data after each" +" chunk is processed. In some cases this helps ensure a serial writing of " +"the output data otherwise a block of data may be written to disk each " +"time a block of data is read for the input buffer resulting in a lot of " +"extra seeking around the disk, and reduced IO throughput. The default at " +"this time is NO." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:96 +msgid "Creating the Output File" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:98 +msgid "" +"In the previous case an appropriate output file was already assumed to " +"exist. Now we will go through a case where a new file with appropriate " +"bounds in a new coordinate system is created. This operation doesn't " +"relate specifically to the warp API. It is just using the transformation " +"API." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:168 +msgid "Some notes on this logic:" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:170 +msgid "" +"We need to create the transformer to output coordinates such that the " +"output of the transformer is georeferenced, not pixel line coordinates " +"since we use the transformer to map pixels around the source image into " +"destination georeferenced coordinates." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:172 +msgid "" +"The :cpp:func:`GDALSuggestedWarpOutput` function will return an " +"adfDstGeoTransform, nPixels and nLines that describes an output image " +"size and georeferenced extents that should hold all pixels from the " +"source image. The resolution is intended to be comparable to the source, " +"but the output pixels are always square regardless of the shape of input " +"pixels." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:174 +msgid "" +"The warper requires an output file in a format that can be \"randomly\" " +"written to. This generally limits things to uncompressed formats that " +"have an implementation of the Create() method (as opposed to " +"CreateCopy()). To warp to compressed formats, or CreateCopy() style " +"formats it is necessary to produce a full temporary copy of the image in " +"a better behaved format, and then CreateCopy() it to the desired final " +"format." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:176 +msgid "" +"The Warp API copies only pixels. All color maps, georeferencing and other" +" metadata must be copied to the destination by the application." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:179 +msgid "Performance Optimization" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:181 +msgid "" +"There are a number of things that can be done to optimize the performance" +" of the warp API:" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:183 +msgid "" +"Increase the amount of memory available for the Warp API chunking so that" +" larger chunks can be operated on at a time. This is the " +":cpp:member:`GDALWarpOptions::dfWarpMemoryLimit` parameter. In theory the" +" larger the chunk size operated on the more efficient the I/O strategy, " +"and the more efficient the approximated transformation will be. However, " +"the sum of the warp memory and the GDAL cache should be less than RAM " +"size, likely around 2/3 of RAM size." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:185 +msgid "" +"Increase the amount of memory for GDAL caching. This is especially " +"important when working with very large input and output images that are " +"scanline oriented. If all the input or output scanlines have to be re-" +"read for each chunk they intersect performance may degrade greatly. Use " +":cpp:func:`GDALSetCacheMax` to control the amount of memory available for" +" caching within GDAL." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:187 +msgid "" +"Use an approximated transformation instead of exact reprojection for each" +" pixel to be transformed. This code illustrates how an approximated " +"transformation could be created based on a reprojection transformation, " +"but with a given error threshold (dfErrorThreshold in output pixels)." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:196 +msgid "" +"When writing to a blank output file, use the INIT_DEST option in the " +":cpp:member:`GDALWarpOptions::papszWarpOptions` to cause the output " +"chunks to be initialized to a fixed value, instead of being read from the" +" output. This can substantially reduce unnecessary IO work." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:198 +msgid "" +"Use tiled input and output formats. Tiled formats allow a given chunk of " +"source and destination imagery to be accessed without having to touch a " +"great deal of extra image data. Large scanline oriented files can result " +"in a great deal of wasted extra IO." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:200 +msgid "" +"Process all bands in one call. This ensures the transformation " +"calculations don't have to be performed for each band." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:202 +msgid "" +"Use the :cpp:func:`GDALWarpOperation::ChunkAndWarpMulti` method instead " +"of :cpp:func:`GDALWarpOperation::ChunkAndWarpImage`. It uses a separate " +"thread for the IO and the actual image warp operation allowing more " +"effective use of CPU and IO bandwidth. For this to work GDAL needs to " +"have been built with multi-threading support (default on Win32, default " +"on Unix, for previous versions -with-threads was required in configure)." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:204 +msgid "" +"The resampling kernels vary in work required from nearest neighbour being" +" least complex, to more complex with bilinear and then cubic. Don't use a" +" more complex resampling kernel than needed." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:206 +msgid "" +"Avoid use of esoteric masking options so that special simplified logic " +"case be used for common special cases. For instance, nearest neighbour " +"resampling with no masking on 8bit data is highly optimized compared to " +"the general case." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:209 +msgid "Other Masking Options" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:211 +msgid "" +"The GDALWarpOptions include a bunch of esoteric masking capabilities, for" +" validity masks, and density masks on input and output. Some of these are" +" not yet implemented and others are implemented but poorly tested. Other " +"than per-band validity masks it is advised that these features be used " +"with caution at this time." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:5 +msgid "OGC WKT Coordinate System Issues" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:7 +msgid "" +"This document is intended to discuss some issues that arise in attempting" +" to use OpenGIS Well Known Text descriptions of coordinate systems. It " +"discusses various vendor implementations and issues between the original " +"`\"Simple Features\" specification (ie. SF-SQL 99-049) " +"<http://portal.opengeospatial.org/files/?artifact_id=829>`__ and the " +"newer `Coordinate Transformation Services (CT) specification (01-009) " +"<http://portal.opengeospatial.org/files/?artifact_id=999>`__ which " +"defines an extended form of WKT." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:17 +msgid "WKT Implementations" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:19 +msgid "" +"At this time I am aware of at least the following software packages that " +"use some form of WKT internally, or for interchange of coordinate system " +"descriptions:" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:23 +msgid "Oracle Spatial (WKT is used internally in MDSYS.WKT, loosely SFSQL based)" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:25 +msgid "" +"ESRI - The Arc8 system's projection engine uses a roughly simple features" +" compatible description for projections. I believe ESRI provided the WKT " +"definition for the simple features spec." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:28 +msgid "" +"Cadcorp - Has the ability to read and write CT 1.0 style WKT. Cadcorp " +"wrote the CT spec." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:30 +msgid "" +"OGR/GDAL - reads/writes WKT as its internal coordinate system description" +" format. Attempts to support old and new forms as well as forms from " +"ESRI." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:33 +msgid "FME - Includes WKT read/write capabilities built on OGR." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:34 +msgid "MapGuide - Uses WKT in the SDP data access API. Roughly SF compliant." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:35 +msgid "" +"PostGIS - Keeps WKT in the spatial_ref_sys table, but it is up to clients" +" to translate to PROJ.4 format for actual use. I believe the " +"spatial_ref_sys table is populated using OGR generated translations." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:40 +msgid "Projection Parameters" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:42 +msgid "" +"The various specs do not list a set of projections, and the parameters " +"associated with them. This leads to various selection of parameter names " +"(and sometimes projection names) from different vendors. I have attempted" +" to maintain a list of WKT bindings for different projections as part of " +"my `GeoTIFF Projections List <https://gdal.org/proj_list>`__ registry. " +"Please try to adhere to the projection names and parameters listed there." +" That list also tries to relate the projections to the GeoTIFF, EPSG and " +"PROJ.4 formulations where possible." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:52 +msgid "" +"The one case where it isn't followed by a vendor that I am aware of ESRIs" +" definition of Lambert Conformal Conic. In EPSG there is a 1SP and a 2SP " +"form of this. ESRI merges them, and just have different parameters " +"depending on the type." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:57 +msgid "" +"One other issue is that the CT specification does explicitly list " +"parameters for the Transverse Mercator, LCC 1SP and LCC 2SP projections; " +"however, it lists standard_parallel1 and standard_parallel2 as parameters" +" for LCC 2SP which conflicts with the existing usage of " +"standard_parallel_1 and standard_parallel_2 and conflicts with examples " +"in the same CT spec. My position is that the table in section 10.x of the" +" CT spec is in error and that the widely used form is correct. Note that " +"the table in the CT spec conflicts with other examples in the same spec." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:67 +msgid "" +"A third issue is the formulation for Albers. While I have used " +"longitude_of_center and latitude_of_center ESRI uses Central_meridian and" +" latitude_of_origin." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:71 +msgid "ESRI:" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:83 +msgid "OGR:" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:96 +msgid "Datum Names" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:98 +msgid "" +"In Simple Features style WKT, the name associated with a datum is the " +"only way to identify the datum. In CT WKT the datum can also have a " +"TOWGS84 parameter indicating its relationship to WGS84, and an AUTHORITY " +"parameter relating it to EPSG or some other authority space. However, in " +"SF WKT the name itself is the only key." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:104 +msgid "" +"By convention OGR and Cadcorp have translated the datum names in a " +"particular way from the EPSG database in order to produce comparible " +"names. The rule is to convert all non alphanumeric characters to " +"underscores, then to strip any leading, trailing or repeating " +"underscores. This produces well behaved datum names like " +"\"Nouvelle_Triangulation_Francaise\"." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:111 +msgid "" +"However, other vendors have done different things. ESRI seems to follow a" +" similar convention but prefixes all datum names with \"D\\_\" as well, " +"giving names like \"D_WGS_1972\". Also they have lots of other " +"differences for reasons that are not clear. For instance for what Cadcorp" +" and OGR call \"Nouvelle_Triangulation_Francaise\", they call it " +"\"D_NTF\". Oracle appears to use the raw names without cleanup. So for " +"NTF they use \"NTF (Paris meridian)\"." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:119 +msgid "" +"The short result of this is that it is almost impossible to recognise and" +" compare datums between different Simple Features implementations, though" +" I have had some success in translating ESRI datum names to match " +"Cadcorp/OGR conventions, with some special casing." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:125 +msgid "Parameter Ordering" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:127 +msgid "" +"It is worthwhile keeping in mind that the BNF grammars for WKT in the SF " +"specs, and the CT spec imply specific orders for most items. For instance" +" the BNF for the PROJCS item in the CT spec is" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:136 +msgid "" +"This clearly states that the PROJECTION keyword follows the GEOGCS, " +"followed by the UNIT, AXIS and AUTHORITY items. Providing them out of " +"order is technically a violation of the spec. On the other hand, WKT " +"consumers are encouraged to be flexible on ordering." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:142 +msgid "Units of PARAMETERs" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:144 +msgid "" +"The linear PARAMETER values in a PROJCS must be in terms of the linear " +"units for that PROJCS. I think the only linear units are the false " +"easting and northing type values. Thus, in common cases like a state " +"plane zone in feet, the false easting and northing will also be in feet." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:149 +msgid "" +"The angular PARAMETER values in a PROJCS must be in terms of the angular " +"units of the GEOGCS. If the GEOGCS is in gradians, for instance, then all" +" the projection angles must also be in gradians!" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:154 +msgid "Units of PRIMEM" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:156 +msgid "What units should the prime meridian appear in?" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:158 +msgid "" +"The CT 1.0 specification (7.3.14 PRIMEM) says *\"The units of the must be" +" inferred from the context. If the PRIMEM clause occurs inside a GEOGCS, " +"then the longitude units will match those of the geographic coordinate " +"system.\"* Note: for a geocentric coordinate system, it says *\"If the " +"PRIMEM clause occurs inside a GEOCCS, then the units will be in " +"degrees\"*." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:164 +msgid "" +"The SF-SQL spec (99-049) does not attempt to address the issue of units " +"of the prime meridian." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:166 +msgid "" +"Existing ESRI EPSG translation to WKT uses degrees for prime meridian, " +"even when the GEOGCS is in gradians as shown in their translation of EPSG" +" 4807:" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:178 +msgid "" +"OGR implements the same interpretation as ESRI for its " +"OGRSpatialReference class: the PRIMEM longitude is always in degrees. See" +" `GDAL Ticket #4524 <https://trac.osgeo.org/gdal/ticket/4524>`__" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:196 +msgid "" +"Cadcorp implements according to the CT 1.0 specification as shown in " +"their translation of EPSG 4807:" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:215 +msgid "" +"Oracle Spatial 8.1.7 uses the following definition for what I assume is " +"supposed to be EPSG 4807. Interestingly it does not bother with using " +"gradians, and it appears that the prime meridian is expressed in radians " +"with very low precision!" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:229 +msgid "Sign of TOWGS84 Rotations" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:232 +msgid "Discussion" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:234 +msgid "" +"In EPSG there are two methods of defining the 7 parameter Bursa-Wolf " +"parameters, 9606 (position vector 7-parameter) and 9607 (coordinate frame" +" rotation). The only difference is that the sign of the rotation " +"coefficients is reversed between them." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:239 +msgid "" +"I (Frank Warmerdam) had somehow convinced myself that the TOWGS84 values " +"in WKT were supposed to be done using the sense in 9606 (position vector " +"7-parameter) and that if I read a 9607 I would need to switch the " +"rotation signs before putting it into a TOWGS84 chunk in WKT." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:244 +msgid "" +"However, I see in the WKT dump you (Martin from Cadcorp) sent me you are " +"using the 9607 sense. For instance, this item appears to use 9607 values " +"directly without switching the sign." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:259 +msgid "" +"I read over the TOWGS84[] clause in the 1.0 CT spec, and it just talks " +"about them being the Bursa Wolf transformation parameters (on page 22, " +"7.3.18). I also scanned through to 12.3.15.2 and 12.3.27 and they are " +"nonspecific as to the handedness of the TOWGS84 rotations." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:264 +msgid "" +"I am seeking a clarification of whether TOWGS84 matches EPSG 9606 or EPSG" +" 9607. Furthermore, I would like to see any future rev of the spec " +"clarify this, referencing the EPSG method definitions." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:268 +msgid "" +"Martin wrote back that he was uncertain on the correct signage and that " +"the Adam had programmed the Cadcorp implementation empirically, according" +" to what seemed to work for the test data available." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:272 +msgid "" +"I am prepared to adhere to the Cadorp sign usage (as per EPSG 9607) if " +"this can be clarified in the specification." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:276 +msgid "Current state of OGR implementation" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:278 +msgid "" +"OGR imports from/exports to WKT assumes EPSG 9606 convention (position " +"vector 7-parameter), as `proj does <https://proj.org/>`__." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:282 +msgid "" +"When importing from EPSG parameters expressed with EPSG 9607, it does the" +" appropriate conversion (negating the sign of the rotation terms)." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:286 +msgid "Longitudes Relative to PRIMEM?" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:288 +msgid "" +"Another related question is whether longtiudinal projection parameters " +"(ie. central meridian) are relative to the GEOGCS prime meridian or " +"relative to greenwich. While the simplest approach is to treat all " +"longitudes as relative to Greenwich, I somehow convinced myself at one " +"point that the longitudes were intended to be relative to the prime " +"meridian. However, a review of 7.3.11 (describing PARAMETER) in the CT " +"1.0 spec provides no support for this opinion, and an inspection of EPSG " +"25700 in Cadcorp also suggests that the central meridian is relative to " +"greenwich, not the prime meridian." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:327 +msgid "" +"Based on this, I am proceeding on the assumption that while parameters " +"are in the units of the GEOGCS they are not relative the GEOGCS prime " +"meridian." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:332 +msgid "Numerical Precision in WKT" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:334 +msgid "" +"The specification does not address the precision to which values in WKT " +"should be stored. Some implementations, such as Oracles apparently, use " +"rather limited precision for parameters such as Scale Factor making it " +"difficult to compare coordinate system descriptions or even to get " +"comparable numerical results." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:340 +#, python-format +msgid "" +"The best practice is to preserve the original precision as specified in " +"the source database, such as EPSG where possible. Given that many systems" +" do not track precision, at least it is advisable to produce values with " +"the equivalent of the C \"%.16g\" format, maintaining 16 digits of " +"precision, capturing most of the precision of a double precision IEEE " +"floating point value." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:348 +msgid "Other Notes" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:350 +msgid "" +"ESRI seems to use Equidistant_Cylindrical for what I know as " +"Equirectangular." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:355 +msgid "History" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:357 +msgid "" +"2018: Even Rouault: make it clear that OGR implements EPSG 9606 " +"convention for TOWGS84." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:359 +msgid "" +"2018: Even Rouault: remove mention about CT 1.0 specification (7.3.14 " +"PRIMEM) having an error, and explicitly mentions that OGR uses degrees " +"for PRIMEM longitude." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:362 +msgid "2018: Even Rouault: add hyperlinks" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:363 +msgid "" +"2007 or before: Originally written by `Frank Warmerdam " +"<https://web.archive.org/web/20130728081442/http://pobox.com/~warmerdam>`__." +msgstr "" + diff --git a/doc/source/locale/en/LC_MESSAGES/user.po b/doc/source/locale/en/LC_MESSAGES/user.po new file mode 100644 index 000000000000..2847659714d5 --- /dev/null +++ b/doc/source/locale/en/LC_MESSAGES/user.po @@ -0,0 +1,7545 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: en\n" +"Language-Team: en <LL@li.org>\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/user/configoptions.rst:5 +msgid "Configuration options" +msgstr "" + +#: ../../source/user/configoptions.rst:7 +msgid "" +"This page discusses runtime configuration options for GDAL. These are " +"distinct from options to the build-time configure script. Runtime " +"configuration options apply on all platforms, and are evaluated at " +"runtime. They can be set programmatically, by commandline switches or in " +"the environment by the user." +msgstr "" + +#: ../../source/user/configoptions.rst:12 +msgid "" +"Configuration options are normally used to alter the default behavior of " +"GDAL/OGR drivers and in some cases the GDAL/OGR core. They are " +"essentially global variables the user can set." +msgstr "" + +#: ../../source/user/configoptions.rst:17 +msgid "How to set configuration options?" +msgstr "" + +#: ../../source/user/configoptions.rst:19 +msgid "" +"One example of a configuration option is the :config:`GDAL_CACHEMAX` " +"option. It controls the size of the GDAL block cache, in megabytes. It " +"can be set in the environment on Unix (bash/bourne) shell like this:" +msgstr "" + +#: ../../source/user/configoptions.rst:29 +msgid "In a DOS/Windows command shell it is done like this:" +msgstr "" + +#: ../../source/user/configoptions.rst:35 +msgid "" +"It can also be set on the commandline for most GDAL and OGR utilities " +"with the ``--config`` switch, though in a few cases these switches are " +"not evaluated in time to affect behavior." +msgstr "" + +#: ../../source/user/configoptions.rst:43 +msgid "" +"Since GDAL 3.9, it is also possible to set a config option in a more " +"conventional way by using a single ``<NAME>``=``<VALUE>`` command line " +"string instead of having ``<NAME>`` and ``<VALUE>`` as two space-" +"separated strings." +msgstr "" + +#: ../../source/user/configoptions.rst:51 +msgid "" +"In C/C++ configuration switches can be set programmatically with " +":cpp:func:`CPLSetConfigOption`:" +msgstr "" + +#: ../../source/user/configoptions.rst:60 +msgid "" +"Normally a configuration option applies to all threads active in a " +"program, but they can be limited to only the current thread with " +":cpp:func:`CPLSetThreadLocalConfigOption`" +msgstr "" + +#: ../../source/user/configoptions.rst:68 +msgid "" +"For boolean options, the values YES, TRUE or ON can be used to turn the " +"option on; NO, FALSE or OFF to turn it off." +msgstr "" + +#: ../../source/user/configoptions.rst:75 +msgid "GDAL configuration file" +msgstr "" + +#: ../../source/user/configoptions.rst:79 +msgid "" +"On driver registration, loading of configuration is attempted from a set " +"of predefined files." +msgstr "" + +#: ../../source/user/configoptions.rst:82 +msgid "" +"The following locations are tried by " +":cpp:func:`CPLLoadConfigOptionsFromPredefinedFiles`:" +msgstr "" + +#: ../../source/user/configoptions.rst:84 +msgid "" +"the location pointed by the environment variable (or configuration " +"option) :config:`GDAL_CONFIG_FILE` is attempted first. If it is set, the " +"next steps are not attempted" +msgstr "" + +#: ../../source/user/configoptions.rst:88 +msgid "" +"for Unix builds, the location pointed by ${sysconfdir}/gdal/gdalrc is " +"first attempted (where ${sysconfdir} evaluates to ${prefix}/etc, unless " +"the ``--sysconfdir`` switch of ./configure has been invoked). Then " +"$(HOME)/.gdal/gdalrc is tried, potentially overriding what was loaded " +"with the sysconfdir" +msgstr "" + +#: ../../source/user/configoptions.rst:93 +msgid "" +"for Windows builds, the location pointed by $(USERPROFILE)/.gdal/gdalrc " +"is attempted." +msgstr "" + +#: ../../source/user/configoptions.rst:96 +msgid "" +"A configuration file is a text file in a .ini style format. Lines " +"starting with `#` are comment lines." +msgstr "" + +#: ../../source/user/configoptions.rst:99 +msgid "" +"The file may contain a ``[configoptions]`` section, that lists " +"configuration options and their values." +msgstr "" + +#: ../../source/user/configoptions.rst:102 +#: ../../source/user/configoptions.rst:136 +#: ../../source/user/virtual_file_systems.rst:14 +msgid "Example:" +msgstr "" + +#: ../../source/user/configoptions.rst:111 +msgid "" +"Configuration options set in the configuration file can later be " +"overridden by calls to :cpp:func:`CPLSetConfigOption` or " +":cpp:func:`CPLSetThreadLocalConfigOption`, or through the ``--config`` " +"command line switch." +msgstr "" + +#: ../../source/user/configoptions.rst:115 +msgid "" +"The value of environment variables set before GDAL starts will be used " +"instead of the value set in the configuration files, unless, starting " +"with GDAL 3.6, the configuration file starts with a ``[directives]`` " +"section that contains a ``ignore-env-variables=yes`` entry." +msgstr "" + +#: ../../source/user/configoptions.rst:129 +msgid "" +"Starting with GDAL 3.5, a configuration file can also contain credentials" +" (or more generally options related to a virtual file system) for a given" +" path prefix, that can also be set with " +":cpp:func:`VSISetPathSpecificOption`. Credentials should be put under a " +"``[credentials]`` section, and for each path prefix, under a relative " +"subsection whose name starts with \"[.\" (e.g. " +"\"[.some_arbitrary_name]\"), and whose first key is \"path\"." +msgstr "" + +#: ../../source/user/configoptions.rst:154 +msgid "Global configuration options" +msgstr "" + +#: ../../source/user/configoptions.rst:157 +msgid "Logging" +msgstr "" + +#: ../../source/user/configoptions.rst:175 +msgid "" +"At the commandline this can also be set with --debug <value> as well as " +"with --config CPL_DEBUG <value>." +msgstr "" + +#: ../../source/user/configoptions.rst:202 +msgid "Performance and caching" +msgstr "" + +#: ../../source/user/configoptions.rst:257 +msgid "" +"Number of datasets that can be opened simultaneously by the GDALProxyPool" +" mechanism (used by VRT for example). Can be increased to get better " +"random I/O performance with VRT mosaics made of numerous underlying " +"raster files. Be careful: on Linux systems, the number of file handles " +"that can be opened by a process is generally limited to 1024. This is " +"currently clamped between 2 and 1000." +msgstr "" + +#: ../../source/user/configoptions.rst:269 +#, python-format +msgid "" +"The value can also be suffixed with ``MB`` or ``GB`` to respectively " +"express it in megabytes or gigabytes. The default value is 25% of the " +"usable physical RAM minus the :config:`GDAL_CACHEMAX` value." +msgstr "" + +#: ../../source/user/configoptions.rst:278 +msgid "" +"Size of the swath when copying raster data from one dataset to another " +"one (in bytes). Should not be smaller than :config:`GDAL_CACHEMAX`." +msgstr "" + +#: ../../source/user/configoptions.rst:292 +msgid "" +"If set to EMPTY_DIR, only the file that is being opened will be seen when" +" a GDAL driver will request sibling files, so this is a way to disable " +"loading side-car/auxiliary files." +msgstr "" + +#: ../../source/user/configoptions.rst:312 +msgid "" +"When enabled, this cache is used for most I/O in GDAL, including local " +"files." +msgstr "" + +#: ../../source/user/configoptions.rst:323 +msgid "Driver management" +msgstr "" + +#: ../../source/user/configoptions.rst:330 +msgid "" +"This option can be used to unregister one or several GDAL drivers. This " +"can be useful when a driver tries to open a dataset that it should not " +"recognize, or when several drivers are built-in that can open the same " +"datasets (for example JP2MrSID, JP2ECW, JPEG2000 and JP2KAK for JPEG2000 " +"datasets). The value of this option must be a space delimited list of the" +" short name of the GDAL drivers to unregister." +msgstr "" + +#: ../../source/user/configoptions.rst:337 +msgid "" +"This option must be set before calling :cpp:func:`GDALAllRegister`, or an" +" explicit call to :cpp:func:`GDALDriverManager::AutoSkipDrivers` will be " +"required." +msgstr "" + +#: ../../source/user/configoptions.rst:354 +msgid "" +"This function will automatically load drivers from shared libraries. It " +"searches the \"driver path\" for .so (or .dll) files that start with the " +"prefix \"gdal_X.so\". It then tries to load them and then tries to call a" +" function within them called GDALRegister_X() where the 'X' is the same " +"as the remainder of the shared library basename ('X' is case sensitive), " +"or failing that to call GDALRegisterMe()." +msgstr "" + +#: ../../source/user/configoptions.rst:361 +msgid "" +"There are a few rules for the driver path. If the ``GDAL_DRIVER_PATH`` " +"environment variable it set, it is taken to be a list of directories to " +"search separated by colons on UNIX, or semi-colons on Windows. Otherwise " +"the /usr/local/lib/gdalplugins directory, and (if known) the " +"lib/gdalplugins subdirectory of the gdal home directory are searched on " +"UNIX and $(BINDIR)\\gdalplugins on Windows." +msgstr "" + +#: ../../source/user/configoptions.rst:368 +msgid "" +"Auto loading can be completely disabled by setting the " +"``GDAL_DRIVER_PATH`` config option to \"disable\"." +msgstr "" + +#: ../../source/user/configoptions.rst:371 +msgid "" +"This option must be set before calling :cpp:func:`GDALAllRegister`, or an" +" explicit call to :cpp:func:`GDALDriverManager::AutoLoadDrivers` will be " +"required." +msgstr "" + +#: ../../source/user/configoptions.rst:381 +msgid "General options" +msgstr "" + +#: ../../source/user/configoptions.rst:389 +msgid "" +"This option is read by the GDAL and OGR driver registration functions. It" +" is used to expand EPSG codes into their description in the OSR model " +"(WKT based)." +msgstr "" + +#: ../../source/user/configoptions.rst:393 +msgid "" +"On some builds (Unix), the value can be hard-coded at compilation time to" +" point to the path after installation (/usr/share/gdal/data for example)." +" On Windows platform, this option must be generally declared." +msgstr "" + +#: ../../source/user/configoptions.rst:487 +msgid "" +"Can be set to YES to use Erdas Imagine format (.aux) as overview format. " +"See :program:`gdaladdo` documentation." +msgstr "" + +#: ../../source/user/configoptions.rst:498 +msgid "Vector related options" +msgstr "" + +#: ../../source/user/configoptions.rst:508 +msgid "" +"The approximation of arcs as linestrings is done by splitting the arcs " +"into subarcs of no more than the angle specified by this option." +msgstr "" + +#: ../../source/user/configoptions.rst:533 +msgid "" +"``DEFAULT``: perform a full analysis of the topological relationships " +"between all rings, classifying them as shells or holes and associating " +"them according to the OGC Simple Features convention. If the topological " +"analysis determines that a valid geometry cannot be constructed, the " +"result will be the same as with :config:`OGR_ORGANIZE_POLYGONS=SKIP`." +msgstr "" + +#: ../../source/user/configoptions.rst:539 +msgid "" +"``ONLY_CCW``: assume that rings with clockwise orientation represent " +"shells and rings with counterclockwise orientation represent holes. " +"Perform a limited topological analysis to determine which shell contains " +"each hole. The Shapefile driver defaults to this method." +msgstr "" + +#: ../../source/user/configoptions.rst:544 +msgid "" +"``CCW_INNER_JUST_AFTER_CW_OUTER``: assume that rings with clockwise " +"orientation represent shells and rings with counterclockwise orientation " +"represent holes and immediately follow the outer ring with which they are" +" associated." +msgstr "" + +#: ../../source/user/configoptions.rst:549 +msgid "" +"``SKIP``: avoid attempting to classify rings as shells or holes. A single" +" geometry (Polygon/MultiPolygon/CurvePolygon/MultiSurface) will be " +"returned with all polygons as top-level polygons. If non-polygonal " +"elements are present, a GeometryCollection will be returned." +msgstr "" + +#: ../../source/user/configoptions.rst:569 +msgid "" +"Those XML based drivers should write UTF8 content. If they are provided " +"with non UTF8 content, they will replace each non-ASCII character by '?' " +"when OGR_FORCE_ASCII=YES." +msgstr "" + +#: ../../source/user/configoptions.rst:573 +msgid "" +"Set to NO to preserve the content, but beware that the resulting XML file" +" will not be valid and will require manual edition of the encoding in the" +" XML header." +msgstr "" + +#: ../../source/user/configoptions.rst:592 +msgid "Networking options" +msgstr "" + +#: ../../source/user/configoptions.rst:601 +msgid "For example:" +msgstr "" + +#: ../../source/user/configoptions.rst:870 +msgid "" +"When using NTLM, you can set the domain by prepending it to the user name" +" and separating the domain and name with a forward (/) or backward slash " +"(\\). Like this: \"domain/user:password\" or \"domain\\user:password\". " +"Some HTTP servers (on Windows) support this style even for Basic " +"authentication." +msgstr "" + +#: ../../source/user/configoptions.rst:897 +msgid "" +"GDAL respects the environment variables http_proxy, ftp_proxy, all_proxy " +"etc, if any of those are set. GDAL_HTTP_PROXY option does however " +"override any possibly set environment variables." +msgstr "" + +#: ../../source/user/configoptions.rst:943 +msgid "Persistent Auxiliary Metadata (PAM) options" +msgstr "" + +#: ../../source/user/configoptions.rst:963 +msgid "PROJ options" +msgstr "" + +#: ../../source/user/configoptions.rst:972 +msgid "" +"This option can be used to control the behavior of gdalwarp when warping " +"global datasets or when transforming from/to polar projections, which " +"causes coordinate discontinuities. See " +"http://trac.osgeo.org/gdal/ticket/2305." +msgstr "" + +#: ../../source/user/configoptions.rst:976 +msgid "" +"The background is that PROJ does not guarantee that converting from " +"src_srs to dst_srs and then from dst_srs to src_srs will yield to the " +"initial coordinates. This can lead to errors in the computation of the " +"target bounding box of gdalwarp, or to visual artifacts." +msgstr "" + +#: ../../source/user/configoptions.rst:981 +msgid "" +"If CHECK_WITH_INVERT_PROJ option is not set, gdalwarp will check that the" +" the computed coordinates of the edges of the target image are in the " +"validity area of the target projection. If they are not, it will retry " +"computing them by setting :config:`CHECK_WITH_INVERT_PROJ=TRUE` that " +"forces ogrct.cpp to check the consistency of each requested projection " +"result with the invert projection." +msgstr "" + +#: ../../source/user/configoptions.rst:987 +msgid "If set to NO, gdalwarp will not attempt to use the invert projection." +msgstr "" + +#: ../../source/user/configoptions.rst:994 +msgid "" +"Used in combination with :config:`CHECK_WITH_INVERT_PROJ=TRUE`. Define " +"the acceptable threshold used to check if the roundtrip from src_srs to " +"dst_srs and from dst_srs to srs_srs yield to the initial coordinates. The" +" value must be expressed in the units of the source SRS (typically " +"degrees for a geographic SRS, meters for a projected SRS)" +msgstr "" + +#: ../../source/user/configoptions.rst:1007 +msgid "" +"Can be set to YES to remove points that cannot be reprojected. This can " +"for example help reproject lines that have an extremity at a pole, when " +"the reprojection does not support coordinates at poles." +msgstr "" + +#: ../../source/user/configoptions.rst:1071 +msgid "List of configuration options and where they are documented" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:5 +msgid "Coordinate epoch support" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:10 +msgid "Dynamic CRS and coordinate epoch" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:12 +msgid "" +"This document is intended to document the support for coordinate epoch, " +"linked to dynamic CRS." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:15 +msgid "" +"In a dynamic CRS, coordinates of a point on the surface of the Earth may " +"change with time. To be unambiguous the coordinates must always be " +"qualified with the epoch at which they are valid. The coordinate epoch is" +" not necessarily the epoch at which the observation was collected." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:20 +msgid "" +"Examples of dynamic CRS are ``WGS 84 (G1762)``, ``ITRF2014``, " +"``ATRF2014``." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:22 +msgid "" +"The generic EPSG:4326 WGS 84 CRS is also considered dynamic, although it " +"is not recommended to use it due to being based on a datum ensemble whose" +" positional accuracy is 2 meters, but prefer one of its realizations, " +"such as WGS 84 (G1762)" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:26 +msgid "" +"The :cpp:func:`OGRSpatialReference::IsDynamic` method can be used to test" +" if a CRS is a dynamic one." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:29 +msgid "" +"The :cpp:func:`OGRSpatialReference::SetCoordinateEpoch` and " +":cpp:func:`OGRSpatialReference::GetCoordinateEpoch` methods can be used " +"to set/retrieve a coordinate epoch associated with a CRS. The coordinate " +"epoch is expressed as a decimal year (e.g. 2021.3 for April 21, 2021)." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:34 +msgid "" +"Formally, the coordinate epoch of an observation belongs to the " +"observation. However, almost all formats do not allow for storing per-" +"observation epoch, and typical usage is a set of observations with the " +"same epoch. Therefore we store the epoch as property of the CRS, and " +"assume that it is valid for every observation. This choice eases " +"processing, storage and format complexity for most usage. For now, this " +"means that a dataset containing observations or points with different " +"epochs cannot be handled." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:42 +msgid "" +"For vector formats, per-geometry coordinate epoch could also make sense, " +"but as most formats only support a per-layer CRS, we also for now limit " +"support of coordinate epoch at the layer level. The underlying coordinate" +" transformation mechanics can support per-vertex coordinate epoch." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:48 +msgid "Support in raster and vector formats" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:50 +msgid "" +"At time of writing, no formats handled by GDAL/OGR have a standardized " +"way of encoding a coordinate epoch. We consequently have made choices how" +" to encode it, with the aim of being as much as possible backward " +"compatible with existing readers. Those encodings might change if " +"corresponding official specifications evolve to take this concept into " +"account. The coordinate epoch is only written when attached to the SRS of" +" the layer/dataset that is created." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:59 +msgid "FlatGeoBuf" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:61 +msgid "" +"The coordinate epoch is encoded as a WKT:2019 string using the ``EPOCH`` " +"subnode of the `COORDINATEMETADATA " +"<http://docs.opengeospatial.org/is/18-010r7/18-010r7.html#130>`__ " +"construct, set in the ``Crs.wkt`` header field of the FlatGeoBuf file." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:82 +msgid "" +"Such construct will not be understood by GDAL < 3.4, but if the CRS has " +"an associated EPSG code, this will not cause issues in those older GDAL " +"versions." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:87 +msgid "GeoPackage vector/raster" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:89 +msgid "" +"Each vector/raster table which has an associated coordinate epoch encodes" +" it in the ``epoch`` column of the ``gpkg_spatial_ref_sys`` table, using " +"an extended version of the CRS WKT extension " +"(https://github.com/opengeospatial/geopackage/pull/600)." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:94 +msgid "GeoTIFF" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:96 +msgid "" +"The coordinate epoch is encoded as a new GeoTIFF GeoKey, " +"``CoordinateEpochGeoKey`` of code 5120 and type DOUBLE." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:125 +#: ../../source/user/virtual_file_systems.rst:334 +msgid "JPEG2000" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:127 +msgid "GeoJP2 boxes use the above mentioned GeoTIFF encoding." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:131 +msgid "Persistent Auxiliary Metadata (.aux.xml)" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:133 +#: ../../source/user/coordinate_epoch.rst:146 +msgid "" +"The coordinate epoch is encoded as ``coordinateEpoch`` attribute of the " +"``SRS`` element." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:144 +msgid "GDAL VRT" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:159 +msgid "Support in utilities" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:161 +msgid "" +":program:`gdalinfo` and :program:`ogrinfo` report the coordinate epoch, " +"when attached to a dataset/layer SRS." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:164 +msgid "" +":program:`gdal_edit.py` has a ``-a_coord_epoch`` option to define the " +"epoch of a dataset in place." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:166 +msgid "" +":program:`gdal_translate` and :program:`ogr2ogr` have a " +"``-a_coord_epoch`` option to be used together with ``-a_srs``, and " +"otherwise preserve the coordinate epoch in the output SRS from the source" +" SRS when no SRS related options are specified." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:170 +msgid "" +":program:`gdalwarp` and :program:`ogr2ogr` have a ``-s_coord_epoch`` " +"option to be used together with ``-s_srs`` (resp. ``-t_coord_epoch`` " +"option to be used together with ``-t_srs``) to override/set the " +"coordinate epoch of the source (resp. target) CRS." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:174 +msgid "" +"Before PROJ 9.4, ``-s_coord_epoch`` and ``-t_coord_epoch`` were mutually " +"exclusive, due to lack of support for transformations between two dynamic" +" CRS." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:177 +msgid "" +":program:`gdalwarp` preserves the coordinate epoch in the output SRS when" +" appropriate." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:181 +msgid "Support in coordinate transformation" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:183 +msgid "" +"The :cpp:class:`OGRCoordinateTransformation` class can perform time-" +"dependent transformations between a static and dynamic CRS based on the " +"coordinate epoch passed per vertex." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:187 +msgid "" +"It can also take into account the coordinate epoch associated with a " +"dynamic CRS, when doing time-dependent transformations between a static " +"and dynamic CRS. The :config:`OGR_CT_USE_SRS_COORDINATE_EPOCH` " +"configuration option can be set to ``NO`` to disable using the coordinate" +" epoch associated with the source or target CRS." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:193 +msgid "" +"If a per-vertex time is specified, it overrides the one associated with " +"the CRS." +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:5 +msgid "GDAL Python Utilities" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:7 +msgid "" +"The GDAL python utilities are included with GDAL. If you've installed " +"GDAL you already have them. However you may want to use a newer or older " +"version of the utilities without changing GDAL. This is where **gdal-" +"utils** comes in." +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:12 +msgid "" +"**gdal-utils**: is the GDAL Python Utilities *distribution*. This is what" +" you install. Its home page is https://pypi.org/project/gdal-utils/ . " +"Install with ``pip install gdal-utils``." +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:16 +msgid "" +"**osgeo_utils**: is the python *package*. This is what you use in your " +"code after installing, e.g. ``from osgeo_utils import ...``. If you're " +"not writing code, ignore it." +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:20 +msgid "Commonly used utilities include:" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:22 +msgid "gdal_merge" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:23 +msgid "gdal_edit" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:24 +msgid "gdal_calc" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:25 +msgid "ogrmerge" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:28 +msgid "Developers" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:30 +msgid "Read the :ref:`gdal-utils project charter <rfc-78>`." +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:32 +msgid "Clone or download the gdal project: https://github.com/OSGeo/gdal/" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:34 +msgid "" +"In your IDE set gdal-utils as the root folder, `.../swig/python/gdal-" +"utils <https://github.com/OSGeo/gdal/tree/master/swig/python/gdal-" +"utils/>`__." +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:37 +msgid "" +"**./osgeo_utils** - contains the Programs (those scripts that have launch" +" wrappers created by pip and added to PYTHONHOME/Scripts)" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:40 +msgid "" +"**./osgeo_utils/samples** - working python scripts but not typically " +"available in path (run them with ``python3 " +"path/to/samples/something.py``)" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:44 +msgid "" +"Improve the docs by editing the RST pages in `.../doc/source " +"<https://github.com/OSGeo/gdal/tree/master/doc/source>`__ which generate " +"the web pages:" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:48 +msgid "https://gdal.org/api/index.html#python-api" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:49 +msgid "https://gdal.org/programs/index.html#programs" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:50 +msgid "https://gdal.org/api/python_samples.html" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:52 +msgid "" +"Contribute changes with `Pull Requests " +"<https://github.com/OSGeo/gdal/pulls>`__ from your fork to main GDAL " +"project and use *gdal-utils* label." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:5 +msgid "Geographic Networks Data Model" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:7 +msgid "" +"This document is intended to describe the purpose and the structure of " +"Geographic Network Model classes. GNM is the part of GDAL and provides " +"the methods of creating, managing and analysing geographical networks." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:9 +msgid "" +"The key purpose of GNM classes: - To provide an abstraction for different" +" existed network formats, like GDAL (previously OGR) provides one for " +"spatial vector formats; - To provide a network functionality to those " +"spatial formats which does not have it at all." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:14 +msgid "General concept" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:16 +msgid "" +"Any real-world network can be represented as a set of vector data, which " +"can be itself represented in GDAL as a GDALDataset. In GNM this data " +"consists of two parts. Network's topology (graph), network's metadata " +"(name/description), set of special feature identifiers, etc. belong to " +"the \"network part\", while the common for GDAL layers, features, " +"geometries belong to the \"spatial/attribute part\". In order to work " +"with the datasets of different formats the following classes were " +"designed in GNM." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:19 +msgid "Network" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:21 +msgid "" +":cpp:class:`GNMNetwork` represents an abstract network. The network data " +"and spatial/attribute data in a dataset of some format in fact can be not" +" separable (just additional layers/fields/tags), while the concrete " +"implementation of GNMNetwork \"knows\" which data from the whole dataset " +"refers to \"network part\" and is able to operate it. GNMNetwork allows " +"user the following:" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:23 +msgid "" +"-Setting/unsetting connections. These generic methods of building the " +"network topology (automatically and manually) receive the identifiers of " +"features being connected in a common way, while the concrete " +"implementation knows where and how to store and build the topology; " +"-Reading connections. The generic methods return the connections in the " +"common way; -Adding/removing layers/features. When the feature or layer " +"is being added to the network some actions can be initiated (weights " +"change in a graph, cascade changes in connected features). Concrete " +"GNMNetwork describes how it is done. -Defining network's business logic " +"or behavior. It can be expressed in network rules or " +"constraints/restrictions. Expected that each rule can be set from a " +"string and each concrete GNMNetwork will transform it to the internal " +"look." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:29 +msgid "Format" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:31 +msgid "" +"GNMNetwork inherits GDALDataset and looks like OGRDatasource with " +"additional functionality. There are a set of GDAL drivers for networks. " +"The generic network implementation in GDAL provides additional " +"functionality like rules, virtual edges and vertices. Also, while editing" +" the feature the network control the network rules and other specific, " +"and can deny saving edits. The other network drivers (pgRouting, OSRM, " +"GraphHopper, etc.) should provide the basic functionality via the " +"GNMNetwork class." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:34 +msgid "Network formats" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:36 +msgid "" +"To add a ``native`` support of the existed network format (like PostGIS " +"pgRouting, Oracle Spatial Networks, topology in GML, etc.) to GNM the " +"developer should implement the corresponding GNMDriver-GNMNetwork " +"interface. But there is also a capability to use the ``generic`` network " +"format, which is already implemented in GNM as a special class. It can be" +" extremely useful when there is a need to create and use a network in the" +" format that initially does not have its \"network part\" (like ESRI " +"Shapefile) directly." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:39 +msgid "GNMGenericNetwork" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:41 +msgid "" +":cpp:class:`GNMGenericNetwork` is a concrete implementation of the " +"GNMNetwork. GNMGenericNetwork intends to support the most GDALDataset " +"drivers (depends on the corresponding driver capabilities). Technically " +"the network format abstraction is achieved with the help of GDAL " +"abstraction: datasets and layers approach. GNMGdalNetwork aggregates a " +"GDALDataset instance where the \"network part\" is represented as a set " +"of \"system layers\" (wkbNone geometry, specific attribute fields) and " +"the spatial/attribute data is regarded as the set of \"class layers\" or " +"\"classes\" (layers with geometries and attributes, as usual). The " +"\"network part\" is created and maintained by GNMGenericNetwork " +"automatically and provides methods to work with it." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:43 +msgid "" +"The way of describing real-world networks by GNMGenericNetwork intends to" +" be a generic, because: -The most general type of graph is used, which " +"holds every useful information: directions of edges " +"(directed/undirected), edge costs (weighted/unweighted). This graph is " +"stored as an incidence list: source vertex feature id, target vertex " +"feature id, edge feature id, direct cost, inverse cost, direction of " +"edge; -Any feature with any geometry can be the vertex or the edge in a " +"graph. Also, it may be no feature “under” the connection's edge at all " +"(actually the virtual edge is created for this case). All this means that" +" user operates with the feature identifiers, while the GNMGenericNetwork " +"guaranties the connections integrity among features; -Any feature in the " +"network will gain the unique identifier – Global Feature Identifier " +"(GFID) which allows unify any amount of \"class layers\" under one " +"network; -GNMGenericNetwork uses its own way to determine the network's " +"business logic. See :cpp:func:`GNMGenericNetwork::CreateRule` for more " +"details." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:49 +msgid "" +"See the :cpp:class:`GNMGenericNetwork` class documentation for more " +"details." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:51 +msgid "" +"The network of common format has also the following important features: " +"-The single spatial reference system is used in the network, that means " +"that each feature which appears in the network will be transformed to " +"this SRS; -The network always created void and there is a need to import " +"or create features; -It is not possible to remove the \"network part\" " +"from the dataset – only delete the whole network with all data. The " +"deletion is made layer by layer and deletes only system and class layers " +"which registered in the network." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:57 +msgid "Network analysis" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:59 +msgid "" +"The network analysis in GNM is implemented in :cpp:class:`GNMNetwork` " +"object." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:61 +msgid "" +":cpp:class:`GNMGenericNetwork` holds the graph in memory in STL " +"containers and provides basic algorithms which return the results in the " +"array-form (e.g. std::vector full of path's edges and vertices GFIDs). " +"But the caller get a result as OGRLayer there features get from layers " +"consist the network. Also some additional fields created (VERTEX/EDGE " +"indicator field, GFID, layer name, etc.). The caller have to free the " +"result OGRLayer via :cpp:func:`GDALDataset::ReleaseResultSet`" +msgstr "" + +#: ../../source/user/index.rst:7 +msgid "GDAL Virtual File Systems" +msgstr "" + +#: ../../source/user/index.rst:5 +msgid "User oriented documentation" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:5 +msgid "Multidimensional Raster Data Model" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:7 +msgid "" +"This document attempts to describe the GDAL multidimensional data model, " +"that has been added in GDAL 3.1. That is the types of information that a " +"GDAL multidimensional dataset can contain, and their semantics." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:11 +msgid "" +"The multidimensional raster API is a generalization of the traditional " +":ref:`raster_data_model`, to address 3D, 4D or higher dimension datasets." +" Currently, it is limited to basic read/write API, and is not that much " +"plugged into other higher level utilities." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:17 +msgid "" +"It is strongly inspired from the netCDF and HDF5 API and data models. See" +" `HDF5 format and data model " +"<https://portal.opengeospatial.org/files/81716>`_." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:20 +msgid "" +"A :cpp:class:`GDALDataset` with multidimensional content contains a root " +":cpp:class:`GDALGroup`." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:24 +msgid "Group" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:26 +msgid "" +"A :cpp:class:`GDALGroup` (modelling a `HDF5 Group " +"<https://portal.opengeospatial.org/files/81716#_hdf5_group>`_) is a named" +" container of GDALAttribute, GDALMDArray or other GDALGroup. Hence " +"GDALGroup can describe a hierarchy of objects." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:31 +msgid "Attribute" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:33 +msgid "" +"A :cpp:class:`GDALAttribute` (modelling a `HDF5 Attribute " +"<https://portal.opengeospatial.org/files/81716#_hdf5_attribute>`_) has a " +"name and a value, and is typically used to describe a metadata item. The " +"value can be (for the HDF5 format) in the general case a multidimensional" +" array of \"any\" type (in most cases, this will be a single value of " +"string or numeric type)" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:39 +msgid "Multidimensional array" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:41 +msgid "" +"A :cpp:class:`GDALMDArray` (modelling a `HDF5 Dataset " +"<https://portal.opengeospatial.org/files/81716#_hdf5_dataset>`_) has a " +"name, a multidimensional array, references a number of GDALDimension, and" +" has a list of GDALAttribute." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:45 +msgid "" +"Most drivers use the row-major convention for dimensions: that is, when " +"considering that the array elements are stored consecutively in memory, " +"the first dimension is the slowest varying one (in a 2D image, the row), " +"and the last dimension the fastest varying one (in a 2D image, the " +"column). That convention is the default convention used for NumPy arrays," +" the MEM driver and the HDF5 and netCDF APIs. The GDAL API is mostly " +"agnostic about that convention, except when passing a NULL array as the " +"*stride* parameter for the :cpp:func:`GDALAbstractMDArray::Read` and " +":cpp:func:`GDALAbstractMDArray::Write` methods. You can refer to `NumPy " +"documentation about multidimensional array indexing order issues " +"<https://docs.scipy.org/doc/numpy/reference/internals.html" +"#multidimensional-array-indexing-order-issues>`_" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:55 +msgid "a GDALMDArray has also optional properties:" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:57 +msgid "Coordinate reference system: :cpp:class:`OGRSpatialReference`" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:58 +msgid "No data value:" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:59 +msgid "Unit" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:60 +msgid "Offset, such that unscaled_value = offset + scale * raw_value" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:61 +msgid "Scale, such that unscaled_value = offset + scale * raw_value" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:63 +msgid "" +"Number of operations can be applied on an array to get modified views of " +"it: :cpp:func:`GDALMDArray::Transpose()`, " +":cpp:func:`GDALMDArray::GetView()`, etc." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:66 +msgid "" +"The :cpp:func:`GDALMDArray::Cache()` method can be used to cache the " +"value of a view array into a sidecar file." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:70 +msgid "Dimension" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:72 +msgid "" +"A :cpp:class:`GDALDimension` describes a dimension / axis used to index " +"multidimensional arrays. It has the following properties:" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:75 +msgid "a name" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:76 +msgid "" +"a size, that is the number of values that can be indexed along the " +"dimension" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:78 +msgid "" +"a type, which is a string giving the nature of the dimension. Predefined " +"values are: HORIZONTAL_X, HORIZONTAL_Y, VERTICAL, TEMPORAL, PARAMETRIC " +"Other values might be used. Empty value means unknown." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:81 +msgid "" +"a direction. Predefined values are: EAST, WEST, SOUTH, NORTH, UP, DOWN, " +"FUTURE, PAST Other values might be used. Empty value means unknown." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:84 +msgid "" +"a reference to a GDALMDArray variable, typically one-dimensional, " +"describing the values taken by the dimension. For a georeferenced " +"GDALMDArray and its X dimension, this will be typically the values of the" +" easting/longitude for each grid point." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:90 +msgid "Data Type" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:92 +msgid "" +"A :cpp:class:`GDALExtendedDataType` (modelling a `HDF5 datatype " +"<https://portal.opengeospatial.org/files/81716#_hdf5_datatype>`_) " +"describes the type taken by an individual value of a GDALAttribute or " +"GDALMDArray. Its class can be NUMERIC, STRING or COMPOUND. For NUMERIC, " +"the existing :cpp:enum:`GDALDataType` enumerated values are supported. " +"For COMPOUND, the data type is a list of members, each member being " +"described by a name, a offset in byte in the compound structure and a " +"GDALExtendedDataType." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:103 +msgid "The HDF5 modelisation allows for more complex datatypes." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:107 +msgid "" +"HDF5 does not have native data types for complex values whereas " +"GDALDataType does. So a driver may decide to expose a GDT\\_Cxxxx " +"datatype from a HDF5 Compound data type representing a complex value." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:112 +msgid "Differences with the GDAL 2D raster data model" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:114 +msgid "" +"The concept of GDALRasterBand is no longer used for multidimensional. " +"This can be modelled as either different GDALMDArray, or using a compound" +" data type." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:119 +msgid "" +"Bridges between GDAL 2D classic raster data model and multidimensional " +"data model" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:121 +msgid "" +"The :cpp:func:`GDALRasterBand::AsMDArray` and " +":cpp:func:`GDALMDArray::AsClassicDataset` can be used to respectively " +"convert a raster band to a MD array or a 2D dataset to a MD array." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:126 +msgid "Applications" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:128 +msgid "" +"The following applications can be used to inspect and manipulate " +"multidimensional datasets:" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:131 +msgid ":ref:`gdalmdiminfo`" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:132 +msgid ":ref:`gdalmdimtranslate`" +msgstr "" + +#: ../../source/user/multithreading.rst:5 +msgid "Multi-threading" +msgstr "" + +#: ../../source/user/multithreading.rst:8 +msgid "GDAL API: re-entrant, but not thread-safe" +msgstr "" + +#: ../../source/user/multithreading.rst:10 +msgid "" +"The exact meaning of the terms ``thread-safe`` or ``re-entrant`` is not " +"fully standardized. We will use here the `QT definitions " +"<https://doc.qt.io/qt-5/threads-reentrancy.html>`__. In particular, a C " +"function or C++ method is said to be re-entrant if it can be called " +"simultaneously from multiple threads, *but* only if each invocation uses " +"its own data." +msgstr "" + +#: ../../source/user/multithreading.rst:16 +msgid "All GDAL public C functions and C++ methods are re-entrant, except:" +msgstr "" + +#: ../../source/user/multithreading.rst:18 +msgid "the general initialization functions, like :cpp:func:`GDALAllRegister`." +msgstr "" + +#: ../../source/user/multithreading.rst:19 +msgid "" +"the general cleanup functions like :cpp:func:`GDALDestroy` or " +":cpp:func:`OSRCleanup`." +msgstr "" + +#: ../../source/user/multithreading.rst:21 +msgid "" +"Those functions should not be called concurrently from several threads, " +"and it is general best practice to call them from the main thread of the " +"program at program initialization and termination." +msgstr "" + +#: ../../source/user/multithreading.rst:25 +msgid "" +"Unless otherwise stated, no GDAL public C functions and C++ methods " +"should be assumed to be thread-safe. That is you should not call " +"simultaneously GDAL functions from multiple threads on the same data " +"instance, or even instances that are closely related through ownership " +"relationships. For example, for a multi-band raster dataset, it is not " +"safe to call concurrently GDAL functions on different " +":cpp:class:`GDALRasterBand` instances owned by the same " +":cpp:class:`GDALDataset` instance (each thread should instead manipulate " +"a distinct GDALDataset). Similarly for a GDALDataset owning several " +":cpp:class:`OGRLayer`." +msgstr "" + +#: ../../source/user/multithreading.rst:34 +msgid "" +"The reason is that most implementations of GDALDataset or GDALRasterBand " +"are stateful. A GDALDataset typically owns a file handle, and performs " +"seek/read operations on it, thus not allowing concurrent access. Block " +"cache related structures for a given GDALDataset are not thread-safe. " +"Drivers also often implement lazy initialization strategies to access " +"various metadata which are resolved only the first time the method to " +"access them is invoked. Drivers may also rely on third-party libraries " +"that expose objects that are not thread-safe." +msgstr "" + +#: ../../source/user/multithreading.rst:43 +msgid "" +"Those restrictions apply to the C and C++ ABI, and all languages bindings" +" (unless they would take special precautions to serialize calls)" +msgstr "" + +#: ../../source/user/multithreading.rst:47 +msgid "GDAL block cache and multi-threading" +msgstr "" + +#: ../../source/user/multithreading.rst:49 +msgid "" +"The current design of the GDAL raster block cache allows concurrent reads" +" of several datasets. However performance issues may arise when writing " +"several datasets from several threads, due to lock contention in the " +"global structures of the block cache mechanism." +msgstr "" + +#: ../../source/user/multithreading.rst:54 +msgid "RAM fragmentation and multi-threading" +msgstr "" + +#: ../../source/user/multithreading.rst:56 +msgid "" +"It has been observed that scenarios that involve multi-threading reading " +"or writing of raster datasets are prone to cause a high RAM usage, in " +"particular when using the default dynamic memory allocator of Linux. " +"Using the alternate `tcmalloc <https://github.com/google/tcmalloc>`__ " +"memory allocator helps reducing the amount of virtual and resident memory" +" used." +msgstr "" + +#: ../../source/user/multithreading.rst:62 +msgid "" +"For example, with Debian/Ubuntu distributions, this can be done by " +"installing the ``libtcmalloc-minimal4`` package and running the binary " +"that executes GDAL with:" +msgstr "" + +#: ../../source/user/multithreading.rst:71 +msgid "GDAL and multi-processing" +msgstr "" + +#: ../../source/user/multithreading.rst:73 +msgid "" +"POSIX fork() API should not be called during the middle of a GDAL " +"operation, otherwise some structures like mutexes might appear to be " +"locked forever in the forked process. If multi-processing is done, we " +"recommend that processes are forked before any GDAL operation is done. " +"Operating on the same GDALDataset instance in several sub-processes will " +"generally lead to wrong results due to the underlying file descriptors " +"being shared." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:5 +msgid "Feature Style Specification" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:7 +msgid "Version 0.016 - 2018-12-03" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:10 +msgid "1. Overview" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:12 +msgid "" +"This document defines the way feature style information (i.e. colors, " +"line width, symbols, etc.) should be handled at the various levels in " +"GDAL's vector drivers (OGR)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:16 +msgid "" +"The following GDAL vector drivers have varying levels of support for " +"feature styles: :ref:`DWG (libopencad) <vector.cad>`, :ref:`DWG (Teigha) " +"<vector.dwg>`, :ref:`DXF <vector.dxf>`, :ref:`KML (libkml) " +"<vector.libkml>`, :ref:`MapInfo <vector.mitab>`, :ref:`MicroStation DGN " +"v7 <vector.dgn>` and :ref:`DGN v8 <vector.dgnv8>`, :ref:`OpenJUMP JML " +"<vector.jml>` and :ref:`PDF <raster.pdf>`." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:24 +msgid "1.1 Style is a property of Feature object" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:26 +msgid "" +"Conceptually, the feature style should be seen as a property of a " +"feature. Even though some systems store style information in a special " +"attribute, in GDAL it is more consistent to see the style as a property, " +"just the same way the geometry of a feature is also a property." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:31 +msgid "" +"This does not prevent us from storing the style information in an " +"attribute when writing to some formats that have no provision for styles " +"(e.g. E00). But then at the time such a dataset is opened through GDAL, " +"the name of the attribute that contains style information should either " +"be specified in some metadata, or be specified by the user." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:37 +msgid "" +"Also, in the SFCOM interface, the style information will be stored in an " +"attribute just like the geometry is." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:41 +msgid "1.2 Feature Styles can be stored at 2 levels" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:43 +msgid "" +"The style defines the way a feature should be drawn, but it is very " +"common to have several features that share the same style. In those " +"cases, instead of duplicating the style information on each feature, we " +"will provide a more efficient way to share style information." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:48 +msgid "There are two levels at which style information can be found:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:50 +msgid "" +"A **dataset** can have a table of pre-defined styles that can then be " +"referred to by the layers or by the individual features. The mechanism " +"for that is defined further down in this document." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:53 +msgid "" +"A **feature (OGRFeature object)** can have its own complete style " +"definition. Alternatively, a feature can be linked to a style in the " +"dataset's table of styles. This can save storage space when the same " +"styles are reused often." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:58 +msgid "" +"It should be possible to have style information stored at one or more of " +"the various levels while working on a given dataset. The level(s) where " +"the style is actually stored will depend on the most efficient approach " +"for the format we are dealing with." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:64 +msgid "1.3 Drawing Tools" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:66 +msgid "" +"We define a small set of drawing tools that are used to build style " +"definitions:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:69 +msgid "**PEN**: For linear styles" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:70 +msgid "**BRUSH**: For filling areas" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:71 +msgid "**SYMBOL**: Point symbols" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:72 +msgid "**LABEL**: For annotations" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:74 +msgid "" +"Each drawing tool can take a number of parameters, all optional. The " +"style syntax is built in a way that a system that cannot support all " +"possible parameters can safely skip and ignore the parameters it does not" +" support. This will also make it easy to extend the specification in the " +"future without breaking existing code or applications." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:80 +msgid "" +"A style can use a single tool, or use a combination of one or more tools." +" By combining the use of several tools in a style, one can build " +"virtually any type of graphical representation. For instance, the SYMBOL " +"tool can be used to place spaced symbols along a line. Also, the LABEL " +"tool can be used to place text on a point, stretch it along a line, or " +"even, by combining the PEN tool with the LABEL tool, use the line as a " +"leader to the text label, and draw the text string on the last vertex of " +"the line." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:89 +msgid "" +"Of course, few systems can support all that. But the intention here is to" +" have a style specification that is powerful and flexible enough to allow" +" all types of formats to exchange style information with the least " +"possible loss." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:95 +msgid "1.4 Feature attributes can be used by style definitions" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:97 +msgid "" +"In some cases, it might be useful for a style definition to refer to an " +"attribute field on the feature for a given tool parameter's value instead" +" of having a hardcoded value inside the style itself." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:101 +msgid "" +"Example of this are text angle, text string, etc... these values change " +"for every single text label, but we can share the rest of the label style" +" at the layer level if we lookup the angle and text string in an " +"attribute on each feature." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:106 +msgid "" +"The syntax of the style string provides a way that any parameter value " +"can be either a constant value, or a lookup to an attribute field." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:110 +msgid "1.5 Tool parameter units" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:112 +msgid "" +"Several parameter values can be expressed in different measurement units " +"depending on the file format you are dealing with. For instance, some " +"systems express line width, or text height in points, other in pixels, " +"and others use ground units. In order to accommodate all that, all " +"parameters can be specified in one of the following units systems:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:118 +msgid "**g**: Map Ground Units (whatever the map coordinate units are)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:119 +msgid "**px**: Pixels" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:120 +msgid "**pt**: Points (1/72 inch)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:121 +msgid "**mm**: Millimeters" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:122 +msgid "**cm**: Centimeters" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:123 +msgid "**in**: Inches" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:125 +msgid "" +"Some tools will have to be provided at the GDAL client level to simplify " +"the conversion of any value from one units system to another. This would " +"imply that the GDAL client has to specify a map scale so that conversions" +" from ground units to paper/pixel units can be performed." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:133 +msgid "2. Feature Style String" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:135 +msgid "" +"As was mentioned earlier, styles definitions will usually be stored as " +"strings, either in a per-layer (or per-dataset) table, or directly in the" +" features." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:140 +msgid "2.1 Examples" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:142 +msgid "Here are some example style definition strings:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:144 +msgid "A 5 pixels wide red line: ``PEN(c:#FF0000,w:5px)``" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:146 +msgid "" +"A polygon filled in blue, with a black outline: " +"``BRUSH(fc:#0000FF);PEN(c:#000000)``" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:148 +msgid "A point symbol: ``SYMBOL(c:#00FF00,id:\"points.sym-45,ogr-sym-7\")``" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:150 +msgid "" +"A text label, taking the text string from the \"text_attribute\" " +"attribute field: ``LABEL(f:\"Times New " +"Roman\",s:12pt,t:{text_attribute})\"``" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:154 +msgid "" +"Here is what a style table that contains all the above styles could look " +"like:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:164 +msgid "" +"Then individual features can refer to styles from the table above using " +"the \"@\" character followed by the style name in their style property." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:167 +msgid "" +"For instance, a feature with its style set to \"@road\" would be drawn as" +" a red line." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:171 +msgid "2.2 Style String Syntax" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:173 +msgid "Each feature object has a style property (a string):" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:179 +msgid "``<style_def>`` is defined later in this section." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:180 +msgid "" +"An empty style string means that the feature's style is unspecified. It " +"does not indicate that the feature is invisible – an invisible feature " +"may be indicated using a fully transparent color, like PEN(c:#00000000)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:184 +msgid "" +"``@<style_name>`` is a reference to a predefined style in the layer or " +"the dataset's style table. The layer's table is looked up first, and if " +"style_name is not found there then the dataset's table will be looked up." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:188 +msgid "" +"Finally, ``{<field_name>}`` means that the style property should be read " +"from the specified attribute field." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:191 +msgid "" +"The <style_def> is the real style definition. It is a combination of 1 or" +" more style parts separated by semicolons. Each style_part uses a drawing" +" tool to define a portion of the complete graphical representation:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:214 +msgid "" +"By default, style parts are drawn in the order that they appear in the " +"style_def string unless each part is assigned a different level parameter" +" value (see the level parameter definition)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:218 +msgid "" +"All drawing tool parameters are optional. So it is legal to have a " +"style_part with an empty drawing tool parameter list (e.g. \"PEN()\"). " +"For each parameter that does not have any specified value, it is up to " +"the client application to use its own default value. This document " +"provides advisory default values for most parameters, but it is not " +"mandatory for an application to use those default values." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:225 +msgid "" +"When {<field_name>} is used for a tool_param value, several options are " +"available with respect to the units. The units can be specified after the" +" field name as in PEN(c:#FF0000,w:{line_width}pt) or can be left " +"unspecified as in PEN(c:#FF0000,w:{line_width}). In the first case, the " +"default units will be points (pt), but if the attribute field line_width " +"contains a value followed by a units abbreviation (e.g. \"5px\") then the" +" units specified in the attribute fields have precedence (in this case " +"pixels). Note that the attribute field does not have to contain a units " +"value and probably won't in most cases; it is just an optional feature to" +" be able to override the default units from inside an attribute field's " +"value." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:238 +msgid "2.3 Pen Tool Parameters" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:240 +#: ../../source/user/ogr_feature_style.rst:364 +#: ../../source/user/ogr_feature_style.rst:459 +#: ../../source/user/ogr_feature_style.rst:586 +msgid "**Applicable geometry types:**" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:242 +msgid "" +"Point: When applied to a point, a PEN tool can only define the color and " +"the size of the point to draw." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:244 +msgid "Polyline: This is the most obvious case." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:245 +msgid "Polygon: Defines the way the outline of a polygon should be drawn." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:247 +msgid "" +"Here is the current list of PEN tool parameters. While this is sufficient" +" to cover all the cases that we have encountered so far, new parameters " +"might be added in the future to handle new types of graphical " +"representation. Note again that all parameters are optional:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:252 +msgid "``c``: **Pen Color**, expressed hexadecimal (#RRGGBB[AA])" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:254 +#: ../../source/user/ogr_feature_style.rst:377 +#: ../../source/user/ogr_feature_style.rst:386 +#: ../../source/user/ogr_feature_style.rst:519 +msgid "" +"[AA]: the last 2 digits define the alpha channel value, with 0 being " +"transparent and FF being opaque. The default is FF (opaque)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:256 +msgid "Suggested default: black (c:#000000)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:257 +msgid "Example: PEN(c:#FF0000), or PEN(C:#FF0000FF)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:260 +msgid "" +"``w``: **Pen Width**, expressed as a numeric value with units (g, px, pt," +" mm, cm, in)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:263 +msgid "Suggested default: 1 pixel" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:264 +msgid "Examples: PEN(c:#FF0000,w:5px), PEN(w:3pt), PEN(w:50g)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:266 +msgid "" +"``p``: **Pattern**. To create dash lines. A list of pen-down/pen-up " +"distances" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:268 +#: ../../source/user/ogr_feature_style.rst:319 +#: ../../source/user/virtual_file_systems.rst:79 +#: ../../source/user/virtual_file_systems.rst:168 +#: ../../source/user/virtual_file_systems.rst:195 +#: ../../source/user/virtual_file_systems.rst:1092 +#: ../../source/user/virtual_file_systems.rst:1110 +#: ../../source/user/virtual_file_systems.rst:1221 +#: ../../source/user/virtual_file_systems.rst:1303 +msgid "Examples:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:270 +msgid "|style_pen1| = PEN(c:#FF0000,w:2px,p:\"4px 5px\"). short-dash line" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:276 +msgid "style_pen1" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:272 +msgid "|style_pen2| = PEN(c:#FF0000,w:2px,p:\"10px 5px\"). long-dash line" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:279 +msgid "style_pen2" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:274 +msgid "" +"|style_pen3| = PEN(c:#FF0000,w:2px,p:\"10px 5px 4px 5px\"). long/short " +"dash" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:282 +msgid "style_pen3" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:287 +msgid "" +"``id``: **Comma-delimited list of Pen Names or Ids** For systems that " +"identify pens with a name or an id. The names in the comma-delimited list" +" of ids are scanned until one is recognized by the target system. Pen Ids" +" can be either system-specific ids (see further below) or be one of the " +"pre-defined OGR pen ids for known line patterns. The id parameter should " +"always include one of the OGR ids at the end of the comma-delimited list " +"of ids so that an application never has to rely on understanding system-" +"specific ids." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:296 +msgid "Here is the current list of OGR pen ids (this could grow time):" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:298 +msgid "ogr-pen-0: solid (the default when no id is provided)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:299 +msgid "ogr-pen-1: null pen (invisible)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:300 +msgid "ogr-pen-2: dash" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:301 +msgid "ogr-pen-3: short-dash" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:302 +msgid "ogr-pen-4: long-dash" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:303 +msgid "ogr-pen-5: dot line" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:304 +msgid "ogr-pen-6: dash-dot line" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:305 +msgid "ogr-pen-7: dash-dot-dot line" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:306 +msgid "ogr-pen-8: alternate-line (sets every other pixel)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:308 +msgid "" +"System-specific ids are very likely to be meaningful only to that " +"specific system that created them. The ids should start with the system's" +" name, followed by a dash (-), followed by whatever information is " +"meaningful to that system (a number, a name, a filename, etc.). e.g. " +"\"mapinfo-5\", or \"mysoft-lines.sym-123\", or \"othersystems-funnyline\"" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:314 +msgid "" +"System-specific ids are allowed in order to prevent loss of information " +"when dealing with data from systems that store line patterns in external " +"files or that have their own pre-defined set of line styles (for " +"instance, to do a MapInfo MIF to TAB translation without any loss." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:321 +msgid "PEN(c:#00FF00,id:\"ogr-pen-0\") - simple solid line" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:322 +msgid "" +"PEN(c:#00FF00,id:\"mapinfo-5,ogr-pen-7\") - corresponds to MapInfo's Pen " +"#5, and a system that can't understand MapInfo pens falls back on the " +"default \"ogr-pen-7\" pen (dot-dot line)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:327 +msgid "``cap``: **Pen Cap** - Set the shape of end points of lines." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:329 +msgid "" +"\"cap:b\" - Butt: The ends of the line don't extend beyond the end " +"points. This is the default." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:331 +msgid "" +"\"cap:r\" - Round: Terminate lines with a circle whose diameter is equal " +"to the line width." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:333 +msgid "" +"\"cap:p\" - Projecting: Similar to Butt, but the ends of the line extend " +"by half of line width beyond the end points." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:337 +msgid "``j``: **Pen Join** - Set the shape of the join point (vertex) of lines." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:339 +msgid "" +"\"j:m\" - Miter: Extend the outer edge of the lines until they touch. " +"This is the default." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:341 +msgid "" +"\"j:r\" - Rounded: Join lines with an arc whose center is at the join " +"point and whose diameter is equal to the line width." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:343 +msgid "" +"\"j:b\" - Bevel: Join the lines with butt end caps and fill the resulting" +" triangular notch at the join position." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:347 +msgid "" +"``dp``: **Perpendicular Offset**, expressed as a numeric value units (g, " +"px, pt, mm, cm, in)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:350 +msgid "" +"Offset from the line center. If the offset is negative then the pen will " +"be drawn left of the main segment and right otherwise." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:354 +#: ../../source/user/ogr_feature_style.rst:449 +#: ../../source/user/ogr_feature_style.rst:566 +#: ../../source/user/ogr_feature_style.rst:713 +msgid "" +"``l``: **Priority Level** - Numeric value defining the order in which " +"style parts should be drawn." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:357 +#: ../../source/user/ogr_feature_style.rst:452 +#: ../../source/user/ogr_feature_style.rst:569 +#: ../../source/user/ogr_feature_style.rst:716 +msgid "" +"Lower priority style parts are drawn first, and higher priority ones are " +"drawn on top. If priority level is unspecified, the default is 1." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:362 +msgid "2.4 Brush Tool Parameters" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:366 +msgid "Point: Not applicable." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:367 +msgid "Polyline: Not applicable." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:368 +msgid "Polygon: Defines the way the surface of a polygon is filled." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:370 +msgid "" +"Here is the current list of BRUSH tool parameters. Note again that that " +"this list may be extended in the future, and all parameters are optional:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:374 +msgid "" +"``fc``: **Brush ForeColor**, expressed in hexadecimal (#RRGGBB[AA]). Used" +" for painting the brush pattern itself." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:379 +#, python-format +msgid "Suggested default: 50% grey (c:#808080)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:380 +msgid "Example: BRUSH(fc:#FF0000)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:383 +msgid "" +"``bc``: **Brush BackColor**, expressed in hexadecimal (#RRGGBB[AA]). Used" +" for painting the area behind the brush pattern." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:388 +msgid "Suggested default: transparent (c:#FFFFFF00)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:389 +msgid "Example: BRUSH(fc:#FF0000,bc:#FFEEDD)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:392 +msgid "" +"``id``: **Brush Name or Brush Id** - Comma-delimited list of brush names " +"or ids. The names in the comma-delimited list of ids are scanned until " +"one is recognized by the target system." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:396 +msgid "" +"Brush Ids can be either system-specific ids (see furtherbelow) or be one " +"of the pre-defined OGR brush ids for well known brush patterns. The id " +"parameter should always include one of the OGR ids at the end of the " +"comma-delimited list of ids so that an application never has to rely on " +"understanding system-specific ids." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:402 +msgid "Here is the current list of OGR brush ids (this could grow over time):" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:406 +msgid "ogr-brush-0: solid foreground color (the default when no id is provided)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:407 +msgid "" +"ogr-brush-1: null brush (transparent - no fill, irrespective of fc or bc " +"values" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:409 +msgid "ogr-brush-2: horizontal hatch" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:410 +msgid "ogr-brush-3: vertical hatch" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:411 +msgid "ogr-brush-4: top-left to bottom-right diagonal hatch" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:412 +msgid "ogr-brush-5: bottom-left to top-right diagonal hatch" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:413 +msgid "ogr-brush-6: cross hatch" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:414 +msgid "ogr-brush-7: diagonal cross hatch" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:416 +msgid "" +"Like with Pen Ids, system-specific brush ids are very likely to be " +"meaningful only to that specific system that created them. The ids should" +" start with the system's name, followed by a dash (-), followed by " +"whatever information is meaningful to that system (a number, a name, a " +"filename, etc.)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:421 +msgid "" +"The following conventions will be used for common system-specific brush " +"ids:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:423 +msgid "\"bmp-filename.bmp\" for Windows BMP patterns" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:425 +msgid "" +"Other conventions may be added in the future (such as vector symbols, " +"WMF, etc)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:429 +msgid "" +"``a``: **Angle** - Rotation angle (in degrees, counterclockwise) to apply" +" to the brush pattern." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:433 +msgid "``s``: **Size or Scaling Factor** - Numeric value with or without units." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:435 +msgid "" +"If units are specified, then this value is the absolute size to draw the " +"brush or symbol. If no units are specified then it is taken as a scaling " +"factor relative to the symbol's default size." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:440 +msgid "" +"``dx``, ``dy``: **Spacing**, expressed as a numeric value with units (g, " +"px, pt, mm, cm, in)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:443 +msgid "" +"If filling an area using point symbols, these values will define the " +"spacing to use between them. \"dx\" is the horizontal distance between " +"the center of two adjacent symbols and \"dy\" is the vertical distance. " +"The default is to use the symbol's bounding box width and height for dx " +"and dy respectively." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:457 +msgid "2.5 Symbol Tool Parameters" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:461 +msgid "Point: Place a symbol at the point's location" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:462 +msgid "" +"Polyline: Place symbols along the polyline, either at each vertex, or " +"equally spaced." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:464 +msgid "Polygon: Place the symbols on the outline of the polygon." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:466 +msgid "" +"Here is the current list of SYMBOL tool parameters. Note again that that " +"this list may be extended in the future, and all parameters are optional:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:470 +msgid "" +"``id``: **Symbol Name or Id** - Comma-delimited list of symbol names or " +"ids." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:472 +msgid "" +"The names in the comma-delimited list of ids are scanned until one is " +"recognized by the target system." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:475 +msgid "" +"Symbol Ids can be either system-specific ids (see further below) or be " +"one of the pre-defined OGR symbol ids for well known symbols. The id " +"parameter should always include one of the OGR ids at the end of the " +"comma-delimited list of ids so that an application never has to rely on " +"understanding system-specific ids." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:481 +msgid "Here is the current list of OGR symbol ids (this could grow over time):" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:485 +msgid "ogr-sym-0: cross (+)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:486 +msgid "ogr-sym-1: diagcross (X)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:487 +msgid "ogr-sym-2: circle (not filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:488 +msgid "ogr-sym-3: circle (filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:489 +msgid "ogr-sym-4: square (not filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:490 +msgid "ogr-sym-5: square (filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:491 +msgid "ogr-sym-6: triangle (not filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:492 +msgid "ogr-sym-7: triangle (filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:493 +msgid "ogr-sym-8: star (not filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:494 +msgid "ogr-sym-9: star (filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:495 +msgid "" +"ogr-sym-10: vertical bar (can be rotated using angle attribute to produce" +" diagonal bar)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:498 +msgid "" +"Like with Pen Ids, system-specific symbol ids are very likely to be " +"meaningful only to that specific system that created them. The ids should" +" start with the system's name, followed by a dash (-), followed by " +"whatever information is meaningful to that system (a number, a name, a " +"filename, etc.)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:503 +msgid "" +"The following conventions will be used for common system-specific symbol " +"ids:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:505 +msgid "\"bmp-filename.bmp\" for Windows BMP symbols" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:506 +#, python-format +msgid "" +"\"font-sym-%d\" for a font symbols, where %d is a glyph number inside a " +"font, font family is defined by **f** style field." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:509 +msgid "" +"Other conventions may be added in the future (such as vector symbols, " +"WMF, etc.)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:513 +msgid "" +"``a``: **Angle** - Rotation angle (in degrees, counterclockwise) to apply" +" to the symbol." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:517 +msgid "``c``: **Symbol Color**, expressed in hexadecimal (#RRGGBB[AA])" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:521 +msgid "Suggested default symbol color: black (c:#000000)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:522 +#: ../../source/user/ogr_feature_style.rst:561 +#: ../../source/user/ogr_feature_style.rst:578 +#: ../../source/user/ogr_feature_style.rst:603 +msgid "Example ::" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:526 +msgid "``o``: **Symbol Outline Color**, expressed in hexadecimal (#RRGGBB[AA])." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:528 +msgid "" +"If this parameter is set, an additional halo or border of this color is " +"drawn around the symbol." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:532 +msgid "``s``: **Size or Scaling Factor** - Numeric value with or without units." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:534 +msgid "" +"If units are specified, then this value is the absolute size to draw the " +"symbol. If no units are specified then it is taken as a scaling factor " +"relative to the symbol's default size." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:539 +msgid "" +"``dx``, ``dy``: **X and Y offset**, of the symbol's insertion point, " +"expressed as a numeric value with units (g, px, pt, mm, cm, in)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:542 +msgid "" +"Applies to point geometries, and to symbols placed at each vertex of a " +"polyline." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:546 +msgid "" +"``ds``, ``dp``, ``di``: **Spacing parameters** for symbols spaced along a" +" line, expressed as a numeric value with units (g, px, pt, mm, cm, in)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:549 +msgid "" +"``ds`` is the step to use when placing symbols along the line. By " +"default, symbols applied to a feature with a line geometry are placed at " +"each vertex, butsetting \"ds\" triggers the placement of symbols at an " +"equal distance along the line. \"ds\" has no effect for a feature with a " +"point geometry." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:555 +msgid "" +"``dp`` can be used together with \"ds\" to specify the perpendicular " +"distance between the symbols' center and the line along which they're " +"placed." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:558 +msgid "" +"``di`` can be used to specify an initial offset from the beginning of the" +" line." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:573 +#: ../../source/user/ogr_feature_style.rst:598 +msgid "``f``: **Font Name** - Comma-delimited list of fonts names." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:575 +#: ../../source/user/ogr_feature_style.rst:600 +msgid "" +"Works like the CSS font-family property: the list of font names is " +"scanned until a known font name is encountered." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:584 +msgid "2.6 Label Tool Parameters" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:588 +msgid "Point: Place a text label at the point's location" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:589 +msgid "Polyline: Place text along the polyline." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:590 +msgid "" +"Polygon: Place a label at the centroid of the polygon. All parameters " +"behave exactly as if the geometry was a point located at the polygon's " +"centroid." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:594 +msgid "" +"Here is the current list of LABEL tool parameters. Note again that that " +"this list may be extended in the future, and all parameters are optional:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:608 +msgid "" +"``s``: **Font Size**, expressed as a numeric value with units (g, px, pt," +" mm, cm, in)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:611 +msgid "" +"In the CAD world, font size, or \"text height\", determines the height of" +" a capital letter - what typographers call \"cap height\". But in the " +"worlds of typesetting, graphics and cartography, font size refers to the " +"\"em height\" of the font, which is taller than the cap height. This " +"means that text assigned a height of 1 inch in a DXF file will look " +"larger (often about 45% larger) than 72-point text in a PDF file or " +"MapInfo map. At present, GDAL vector drivers treat the \"s:\" style " +"string value as whichever font size measurement (cap height or em height)" +" is used natively by that format, which may result in incorrect text " +"sizing when using the ogr2ogr tool. This parameter could be subject to " +"clearer specification in the future." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:623 +msgid "" +"``t``: **Text String** - Can be a constant string, or a reference to an " +"attribute field's value." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:626 +msgid "" +"If a double-quote character or backslash (\\) character is present in the" +" string, it is escaped with a backslash character before it." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:629 +msgid "Examples ::" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:636 +msgid "``a``: **Angle** - Rotation angle (in degrees, counterclockwise)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:638 +msgid "" +"``c``: **Text Foreground Color**, expressed in hexadecimal (#RRGGBB[AA]) " +"Suggested default: black (c:#000000)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:641 +msgid "" +"``b``: **Text Background Color** - Color of the filled box to draw behind" +" the label, expressed in hexadecimal (#RRGGBB[AA]). No box drawn if not " +"set." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:644 +msgid "" +"``o``: **Text Outline Color** - Color of the text outline (halo in " +"MapInfo terminology), expressed in hexadecimal (#RRGGBB[AA]). No outline " +"if not set." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:647 +msgid "" +"``h``: **Shadow Color** - Color of the text shadow, expressed in " +"hexadecimal (#RRGGBB[AA]). No shadow if not set." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:650 +#, python-format +msgid "" +"``w``: **Stretch** - The stretch factor changes the width of all " +"characters in the font by the given percentage. For example, a setting of" +" 150 results in all characters in the font being stretched to 150% of " +"their usual width. The default stretch factor is 100." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:655 +msgid "" +"``m``: **Label Placement Mode** - How the text is drawn relative to the " +"feature's geometry." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:658 +msgid "" +"\"m:p\" - The default. A simple label is attached to a point or to the " +"first vertex of a polyline." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:660 +msgid "" +"\"m:l\" - Text is attached to the last vertex of a polyline. A PEN tool " +"can be combined with this LABEL tool to draw the polyline as a leader to " +"the label." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:663 +msgid "" +"\"m:s\" - Stretch the text string along a polyline, with an equal spacing" +" between each character." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:665 +msgid "" +"\"m:m\" - Place text as a single label at the middle of a polyline (based" +" on total line length)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:667 +msgid "\"m:w\" - One word per line segment in a polyline." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:668 +msgid "" +"\"m:h\" - Every word of text attached to polyline is placed horizontally " +"in its segment, anchor point is a center of segment." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:670 +msgid "" +"\"m:a\" - Every word of text attached to polyline is stretched to fit the" +" segment of polyline and placed along that segment. The anchor point is a" +" start of a segment." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:675 +msgid "" +"``p``: **Anchor Position** - A value from 1 to 12 defining the label's " +"position relative to the point to which it is attached" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:678 +msgid "" +"There are four vertical alignment modes: *baseline*, *center*, *top* and " +"*bottom*; and three horizontal modes: *left*, *center* and *right*." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:683 +msgid "" +"Currently, the precise interpretation of these values (for example, " +"whether accents on uppercase letters sit above or below the alignment " +"point with p:7) differs from file format to file format. This parameter " +"could be subject to clearer specification in the future." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:689 +msgid "" +"``dx``, ``dy``: **X and Y offset** of the label's insertion point, " +"expressed as a numeric value with units (g, px, pt, mm, cm, in)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:692 +msgid "Applies to text placed on a point, or at each vertex of a polyline." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:695 +msgid "" +"``dp``: **Perpendicular Offset** for labels placed along a line, " +"expressed as a numeric value with units (g, px, pt, mm, cm, in)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:698 +msgid "" +"\"dp\" specifies the perpendicular distance between the label and the " +"line along which it is placed. If the offset is negative then the label " +"will be shifted left of the main segment, and right otherwise." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:703 +msgid "``bo``: **Bold** - Set to 1 for bold text. Set to 0 or omitted otherwise." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:705 +msgid "" +"``it``: **Italic** - Set to 1 for italic text. Set to 0 or omitted " +"otherwise." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:707 +msgid "" +"``un``: **Underline** - Set to 1 for underlined text. Set to 0 or omitted" +" otherwise." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:710 +msgid "" +"``st``: **Strikethrough** - Set to 1 for struck-through text. Set to 0 " +"or omitted otherwise." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:721 +msgid "2.7 Styles Table Format" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:723 +msgid "" +"For file formats that support tables of styles, then the predefined " +"styles would be stored in that format." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:726 +msgid "" +"For file formats that do not support tables of styles, then the style " +"table could be stored in a text file with a .ofs (OGR Feature Styles) " +"extension and the same basename as the dataset. This would apply to " +"formats like Esri Shapefile." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:731 +msgid "Here is an example of a .ofs file:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:744 +msgid "" +"The first line is a signature with a version number, which must be " +"present." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:747 +msgid "" +"The second line (StyleField: \"style\") is the name of the attribute " +"field in which the Feature Style String is stored for each object in the " +"corresponding layer. This is optional, if not set, then the objects in " +"the layer will all share the same style defined in DefaultStyle." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:752 +msgid "" +"The third line (DefaultStyle:...) defines the style that applies by " +"default to all objects that have no explicit style." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:755 +msgid "Then the list of style definitions follow." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:758 +msgid "2.8 Using OGR SQL to transfer the style between the data sources" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:760 +msgid "" +"You can use the **OGR_STYLE** special field to extract the feature level " +"style, and ogr2ogr can be used to transfer the style string between data " +"sources according to the following example:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:768 +msgid "" +"Without specifying the length of the style field, the output driver may " +"truncate the length to a default value. Therefore it may be necessary to " +"specify the target length manually, like:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:776 +msgid "" +"OGR is aware of using the OGR_STYLE field if it exists, and " +"OGRFeature::GetStyleString will return the value of this field if no " +"style string has been specified programmatically." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:785 +msgid "3. OGR Support Classes" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:787 +msgid "" +"The :cpp:class:`OGRFeature` class has member functions " +":cpp:func:`OGRFeature::GetStyleString`, " +":cpp:func:`OGRFeature::SetStyleString` and " +":cpp:func:`OGRFeature::SetStyleStringDirectly` which may be used to " +"interact with a feature's style string as a C-style string. Additionally," +" there are :cpp:func:`OGRFeature::GetStyleTable`, " +":cpp:func:`OGRFeature::SetStyleTable` and " +":cpp:func:`OGRFeature::SetStyleTableDirectly` for managing style tables " +"as instances of the :cpp:class:`OGRStyleTable` class." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:794 +msgid "" +"The :cpp:class:`OGRLayer` and :cpp:class:`GDALDataset` classes also have " +":cpp:func:`OGRLayer::GetStyleTable`, :cpp:func:`OGRLayer::SetStyleTable` " +"and :cpp:func:`OGRLayer::SetStyleTableDirectly` member functions." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:797 +msgid "" +"To parse style strings, the :cpp:class:`OGRStyleMgr` class is used. Each " +"style tool in the string is accessed as an instance of the " +":cpp:class:`OGRStyleTool` class. Lastly, four helper classes exist, one " +"for each tool (:cpp:class:`OGRStylePen`, :cpp:class:`OGRStyleBrush`, " +":cpp:class:`OGRStyleSymbol`, :cpp:class:`OGRStyleLabel`), with each " +"available parameter represented by a getter and setter member function. " +"To understand these classes better, it may be useful to read the " +":source_file:`ogr/ogr_featurestyle.h` and " +":source_file:`ogr/ogrfeaturestyle.cpp` code files." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:810 +msgid "Here is some example C++ code:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:888 +msgid "Revision history" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:890 +msgid "" +"**Version 0.016 - 2018-12-03 - Andrew Sudorgin** Restored and documented " +"font property for point symbols" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:892 +msgid "" +"**Version 0.015 - 2018-01-08 - Alan Thomas** Update outdated material; " +"minor changes to BRUSH 'id' and LABEL 't', 'bo', 'it', 'un', 'st'; " +"clarify BRUSH 'fc', 'bc', SYMBOL 'o' and LABEL 's', 'w', 'p'" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:896 +msgid "" +"**Version 0.014 - 2011-07-24 - Even Rouault** Mention the escaping of " +"double-quote characters in the text string of a LABEL (ticket #3675)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:899 +msgid "" +"**Version 0.013 - 2008-07-29 - Daniel Morissette** Added 'o:' for font " +"point symbol outline color (ticket #2509)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:901 +msgid "" +"**Version 0.012 - 2008-07-21 - Daniel Morissette** Added 'o:' for text " +"outline color and updated 'b:' to be specifically a filled label " +"background box (ticket #2480)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:904 +msgid "" +"**Version 0.011 - 2008-02-28 - Tamas Szekeres** Note about OGR SQL to " +"transfer the style between the data sources" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:906 +msgid "" +"**Version 0.010 - 2006-09-23- Andrey Kiselev** Added label styles 'w', " +"'st', 'h', 'm:h', 'm:a', 'p:{10,11,12}'" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:908 +msgid "" +"**Version 0.009 - 2005-03-11- Frank Warmerdam** Remove reference to " +"OGRWin, move into ogr distribution" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:910 +msgid "" +"**Version 0.008 - 2001-03-21- Frank Warmerdam** Fix minor typos (h:12pt " +"instead of s:12pt in examples)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:912 +msgid "" +"**Version 0.008 - 2000-07-15 - Stephane Villeneuve** Remove style table " +"in Layer. Add forecolor and backcolor to brush." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:914 +msgid "" +"**Version 0.007 - 2000-06-22 - Daniel Morissette** Fixed typo and added " +"offset param for PEN." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:916 +msgid "" +"**Version 0.006 - 2000-06-20 - Daniel Morissette** Added the OGR-Win idea" +" and made small changes here and there." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:918 +msgid "" +"**Version 0.005 - 2000-06-12 - Daniel Morissette** Allow passing of " +"comma-delimited list of names in PEN's \"id\" parameter. Defined system-" +"independent pen style names." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:922 +msgid "" +"**Version 0.004 - 2000-06-09 - Stephane Villeneuve** Added PEN cap and " +"join parameters More clearly defined the API" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:925 +msgid "" +"**Version 0.003 - 2000-02-15 - Daniel Morissette** First kind-of-complete" +" version." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:5 +msgid "OGR SQL dialect" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:9 +msgid "" +"The GDALDataset supports executing commands against a datasource via the " +":cpp:func:`GDALDataset::ExecuteSQL` method. While in theory any sort of " +"command could be handled this way, in practice the mechanism is used to " +"provide a subset of SQL SELECT capability to applications. This page " +"discusses the generic SQL implementation implemented within OGR, and " +"issues with driver specific SQL support." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:16 +msgid "" +"The ``OGRSQL`` dialect can be requested with the ``OGRSQL`` string passed" +" as the dialect parameter of :cpp:func:`GDALDataset::ExecuteSQL`, or with" +" the `-dialect` option switch of the :ref:`ogrinfo` or :ref:`ogr2ogr` " +"utilities." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:20 +msgid "" +"An alternate dialect, the ``SQLite`` dialect, can be used instead of the " +"``OGRSQL`` dialect. Refer to the :ref:`sql_sqlite_dialect` page for more " +"details." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:23 +msgid "" +"The OGRLayer class also supports applying an attribute query filter to " +"features returned using the :cpp:func:`OGRLayer::SetAttributeFilter()` " +"method. The syntax for the attribute filter is the same as the WHERE " +"clause in the OGR SQL SELECT statement. So everything here with regard " +"to the WHERE clause applies in the context of the " +"``SetAttributeFilter()`` method." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:30 +msgid "SELECT" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:32 +msgid "" +"The SELECT statement is used to fetch layer features (analogous to table " +"rows in an RDBMS) with the result of the query represented as a temporary" +" layer of features. The layers of the datasource are analogous to tables " +"in an RDBMS and feature attributes are analogous to column values. The " +"simplest form of OGR SQL SELECT statement looks like this:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:42 +msgid "" +"In this case all features are fetched from the layer named \"polylayer\"," +" and all attributes of those features are returned. This is essentially " +"equivalent to accessing the layer directly. In this example the \"*\" is " +"the list of fields to fetch from the layer, with \"*\" meaning that all " +"fields should be fetched." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:48 +msgid "" +"This slightly more sophisticated form still pulls all features from the " +"layer but the schema will only contain the geometry column and the EAS_ID" +" and PROP_VALUE attributes. With OGR SQL dialect the geometry column is " +"always included in the result so it does not need to appear in the SQL " +"statement." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:57 +msgid "" +"A much more ambitious SELECT, restricting the features fetched with a " +"WHERE clause, and sorting the results might look like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:64 +msgid "" +"This select statement will produce a table with just one feature, with " +"geometry and one attribute (named something like \"count_eas_id\") " +"containing the number of distinct values of the eas_id attribute." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:73 +msgid "General syntax" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:75 +msgid "The general syntax of a SELECT statement is:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:84 +msgid "List Operators" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:86 +msgid "" +"The field list is a comma-separated list of the fields to be carried into" +" the output features from the source layer. They will appear on output " +"features in the order they appear on in the field list, so the field list" +" may be used to re-order the fields. The special character ``*`` is taken" +" to mean \"all fields\". The syntax ``* EXCLUDE ([fields])`` can be used " +"to select all fields except those listed in parentheses." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:93 +msgid "" +"A special form of the field list uses the DISTINCT keyword. This returns" +" a list of all the distinct values of the named attribute. When the " +"DISTINCT keyword is used, only one attribute may appear in the field " +"list. The DISTINCT keyword may be used against any type of field. " +"Currently the distinctness test against a string value is case " +"insensitive in OGR SQL. The result of a SELECT with a DISTINCT keyword " +"is a layer with one column (named the same as the field operated on), and" +" one feature per distinct value. Geometries are discarded. The distinct" +" values are assembled in memory, so a lot of memory may be used for " +"datasets with a large number of distinct values." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:108 +msgid "" +"There are also several summarization operators that may be applied to " +"columns. When a summarization operator is applied to any field, then all " +"fields must have summarization operators applied. The summarization " +"operators are COUNT (a count of instances), AVG (numerical average), SUM " +"(numerical sum), MIN (lexical or numerical minimum), and MAX (lexical or " +"numerical maximum). This example produces a variety of summarization " +"information on parcel property values:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:121 +msgid "" +"It is also possible to apply the COUNT() operator to a DISTINCT SELECT to" +" get a count of distinct values, for instance:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:128 +msgid "" +"As a special case, the COUNT() operator can be given a \"*\" argument " +"instead of a field name which is a short form for count all the records." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:136 +msgid "" +"Field names can also be prefixed by a table name though this is only " +"really meaningful when performing joins. It is further demonstrated in " +"the JOIN section." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:140 +msgid "" +"Field definitions can also be complex expressions using arithmetic, and " +"functional operators. However, the DISTINCT keyword, and summarization " +"operators like MIN, MAX, AVG and SUM may not be applied to expression " +"fields. Boolean resulting expressions (comparisons, logical operators) " +"can also be used." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:149 +msgid "or" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:157 +msgid "Functions" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:159 +msgid "" +"The SUBSTR function can be used to extract a substring from a string. Its" +" syntax is the following one : SUBSTR(string_expr, start_offset [, " +"length]). It extracts a substring of string_expr, starting at offset " +"start_offset (1 being the first character of string_expr, 2 the second " +"one, etc...). If start_offset is a negative value, the substring is " +"extracted from the end of the string (-1 is the last character of the " +"string, -2 the character before the last character, ...). If length is " +"specified, up to length characters are extracted from the string. " +"Otherwise the remainder of the string is extracted." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:167 +msgid "" +"Note: for the time being, the character as considered to be equivalent to" +" bytes, which may not be appropriate for multi-byte encodings like UTF-8." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:176 +msgid "" +"The ``hstore_get_value()`` function can be used to extract a value " +"associate to a key from a HSTORE string, formatted like " +"'key=>value,other_key=>other_value,...'" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:184 +msgid "Using the field name alias" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:186 +msgid "" +"OGR SQL supports renaming the fields following the SQL92 specification by" +" using the AS keyword according to the following example:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:193 +msgid "" +"The field name alias can be used as the last operation in the column " +"specification. Therefore we cannot rename the fields inside an operator, " +"but we can rename whole column expression, like these two:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:203 +msgid "Changing the type of the fields" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:205 +msgid "" +"OGR SQL supports changing the type of the columns by using the SQL92 " +"compliant CAST operator according to the following example:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:212 +msgid "Currently casting to the following target types are supported:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:214 +msgid "boolean" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:215 +msgid "character(field_length). By default, field_length=1." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:216 +msgid "float(field_length)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:217 +msgid "numeric(field_length, field_precision)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:218 +msgid "smallint(field_length) : 16 bit signed integer" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:219 +msgid "integer(field_length)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:220 +msgid "bigint(field_length), 64 bit integer, extension to SQL92" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:221 +msgid "date(field_length)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:222 +msgid "time(field_length)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:223 +msgid "timestamp(field_length)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:224 +msgid "geometry, geometry(geometry_type), geometry(geometry_type,epsg_code)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:226 +msgid "" +"Specifying the field_length and/or the field_precision is optional. An " +"explicit value of zero can be used as the width for character() to " +"indicate variable width. Conversion to the 'integer list', 'double list'" +" and 'string list' OGR data types are not supported, which doesn't " +"conform to the SQL92 specification." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:232 +msgid "" +"While the CAST operator can be applied anywhere in an expression, " +"including in a WHERE clause, the detailed control of output field format " +"is only supported if the CAST operator is the \"outer most\" operators on" +" a field in the field definition list. In other contexts it is still " +"useful to convert between numeric, string and date data types." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:238 +msgid "" +"Casting a WKT string to a geometry is allowed. geometry_type can be " +"POINT[Z], LINESTRING[Z], POLYGON[Z], MULTIPOINT[Z], MULTILINESTRING[Z], " +"MULTIPOLYGON[Z], GEOMETRYCOLLECTION[Z] or GEOMETRY[Z]." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:243 +msgid "String literals and identifiers quoting" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:245 +msgid "" +"Strict SQL92 rules are applied regarding string literals and identifiers " +"quoting." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:247 +msgid "" +"String literals (constants) must be surrounded with single-quote " +"characters. e.g. WHERE a_field = 'a_value'" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:250 +msgid "" +"Identifiers (column names and tables names) can be used unquoted if they " +"don't contain special characters or are not a SQL reserved keyword. " +"Otherwise they must be surrounded with double-quote characters. e.g. " +"WHERE \"from\" = 5." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:255 +msgid "WHERE" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:257 +msgid "" +"The argument to the WHERE clause is a logical expression used select " +"records from the source layer. In addition to its use within the WHERE " +"statement, the WHERE clause handling is also used for OGR attribute " +"queries on regular layers via :cpp:func:`OGRLayer::SetAttributeFilter`." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:262 +msgid "" +"In addition to the arithmetic and other functional operators available in" +" expressions in the field selection clause of the SELECT statement, in " +"the WHERE context logical operators are also available and the evaluated " +"value of the expression should be logical (true or false)." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:267 +msgid "" +"The available logical operators are ``=``, ``!=``, ``<>``, ``<``, ``>``, " +"``<=``, ``>=``, ``LIKE`` and ``ILIKE``, ``BETWEEN`` and ``IN``. Most of " +"the operators are self explanatory, but it is worth noting that ``!=`` is" +" the same as ``<>``, the string equality is case insensitive, but the " +"``<``, ``>``, ``<=`` and ``>=`` operators *are* case sensitive." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:283 +msgid "" +"Starting with GDAL 3.1, LIKE is case sensitive, and ILIKE is case " +"insensitive. In previous versions, LIKE was also case insensitive. If the" +" old behavior is wished in GDAL 3.1, the :config:`OGR_SQL_LIKE_AS_ILIKE` " +"can be set to ``YES``." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:287 +msgid "" +"Starting with GDAL 3.9, for layers declaring the OLCStringsAsUTF8 " +"capability (that is the content of their fields of String type is UTF-8 " +"encoded), UTF-8 characters are taken into account by ``LIKE`` and " +"``ILIKE`` operators. For ILIKE case insensitive comparisons, this is " +"restricted to the `ASCII " +"<https://en.wikipedia.org/wiki/Basic_Latin_(Unicode_block)>`__, `Latin-1 " +"Supplement <https://en.wikipedia.org/wiki/Latin-" +"1_Supplement_(Unicode_block)>`__, `Latin Extended-A " +"<https://en.wikipedia.org/wiki/Latin_Extended-A>`__, `Latin Extended-B " +"<https://en.wikipedia.org/wiki/Latin_Extended-B>`__, `Greek and Coptic " +"<https://en.wikipedia.org/wiki/Greek_and_Coptic>`__ and `Cyrillic " +"<https://en.wikipedia.org/wiki/Greek_and_Coptic>`__ Unicode categories." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:298 +msgid "" +"The value argument to the ``LIKE`` and ``ILIKE`` operators is a pattern " +"against which the value string is matched. In this pattern percent (%) " +"matches any number of characters, and underscore ( _ ) matches any one " +"character. An optional ESCAPE escape_char clause can be added so that the" +" percent or underscore characters can be searched as regular characters, " +"by being preceded with the escape_char." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:318 +msgid "" +"The ``IN`` takes a list of values as its argument and tests the attribute" +" value for membership in the provided set." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:330 +msgid "" +"The syntax of the ``BETWEEN`` operator is \"field_name BETWEEN value1 AND" +" value2\" and it is equivalent to \"field_name >= value1 AND field_name " +"<= value2\"." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:333 +msgid "" +"In addition to the above binary operators, there are additional operators" +" for testing if a field is null or not. These are the ``IS NULL`` and " +"``IS NOT NULL`` operators." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:337 +msgid "" +"Basic field tests can be combined in more complicated predicates using " +"logical operators include ``AND``, ``OR``, and the unary logical ``NOT``." +" Subexpressions should be bracketed to make precedence clear. Some more " +"complicated predicates are:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:349 +msgid "WHERE Limitations" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:351 +msgid "" +"Fields must all come from the primary table (the one listed in the FROM " +"clause)." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:353 +msgid "" +"All string comparisons are case insensitive except for ``<``, ``>``, " +"``<=`` and ``>=``" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:356 +msgid "ORDER BY" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:358 +msgid "" +"The ``ORDER BY`` clause is used force the returned features to be " +"reordered into sorted order (ascending or descending) on one or multiple " +"fields. Ascending (increasing) order is the default if neither the ASC or" +" DESC keyword is provided. For example:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:371 +msgid "" +"Note that ORDER BY clauses cause two passes through the feature set. One" +" to build an in-memory table of field values corresponded with feature " +"ids, and a second pass to fetch the features by feature id in the sorted " +"order. For formats which cannot efficiently randomly read features by " +"feature id this can be a very expensive operation." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:377 +msgid "" +"Sorting of string field values is case sensitive, not case insensitive " +"like in most other parts of OGR SQL." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:381 +msgid "LIMIT and OFFSET" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:383 +msgid "" +"Starting with GDAL 2.2, the ``LIMIT`` clause can be used to limit the " +"number of features returned. For example" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:390 +msgid "" +"The ``OFFSET`` clause can be used to skip the first features of the " +"result set. The value after OFFSET is the number of features skipped. For" +" example, to skip the first 3 features from the result set:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:398 +msgid "Both clauses can be combined:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:405 +msgid "JOINs" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:407 +msgid "" +"OGR SQL supports a limited form of one to one JOIN. This allows records " +"from a secondary table to be looked up based on a shared key between it " +"and the primary table being queried. For instance, a table of city " +"locations might include a **nation_id** column that can be used as a " +"reference into a secondary **nation** table to fetch a nation name. A " +"joined query might look like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:419 +msgid "" +"This query would result in a table with all the fields from the city " +"table, and an additional \"nation.name\" field with the nation name " +"pulled from the nation table by looking for the record in the nation " +"table that has the \"id\" field with the same value as the city.nation_id" +" field." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:424 +msgid "" +"Joins introduce a number of additional issues. One is the concept of " +"table qualifiers on field names. For instance, referring to " +"city.nation_id instead of just nation_id to indicate the nation_id field " +"from the city layer. The table name qualifiers may only be used in the " +"field list, and within the ``ON`` clause of the join." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:430 +msgid "" +"Wildcards are also somewhat more involved. All fields from the primary " +"table (**city** in this case) and the secondary table (**nation** in this" +" case) may be selected using the usual ``*`` wildcard. But the fields of" +" just one of the primary or secondary table may be selected by prefixing " +"the asterix with the table name." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:436 +msgid "" +"The field names in the resulting query layer will be qualified by the " +"table name, if the table name is given as a qualifier in the field list." +" In addition field names will be qualified with a table name if they " +"would conflict with earlier fields. For instance, the following select " +"would result might result in a results set with a **name, nation_id, " +"nation.nation_id** and ** nation.name** field if the city and nation " +"tables both have the **nation_id** and **name** fieldnames." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:448 +msgid "" +"On the other hand if the nation table had a **continent_id** field, but " +"the city table did not, then that field would not need to be qualified in" +" the result set. However, if the selected instead looked like the " +"following statement, all result fields would be qualified by the table " +"name." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:458 +msgid "" +"In the above examples, the **nation** table was found in the same " +"datasource as the **city** table. However, the OGR join support " +"includes the ability to join against a table in a different data source, " +"potentially of a different format. This is indicated by qualifying the " +"secondary table name with a datasource name. In this case the secondary " +"datasource is opened using normal OGR semantics and utilized to access " +"the secondary table until the query result is no longer needed." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:471 +msgid "" +"While not necessarily very useful, it is also possible to introduce table" +" aliases to simplify some SELECT statements. This can also be useful to " +"disambiguate situations where tables of the same name are being used from" +" different data sources. For instance, if the actual tables names were " +"messy we might want to do something like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:483 +msgid "It is possible to do multiple joins in a single query." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:491 +msgid "" +"The expression after ON is typically of the form " +"\"{primary_table}.{field_name} = {secondary_table}.{field_name}\", and in" +" that order. It is also possible to use a more complex boolean " +"expression, involving multiple comparison operators, but with the " +"restrictions mentioned in the below \"JOIN limitations\" section. In " +"particular, in case of multiple joins (3 tables or more) the fields " +"compared in a JOIN must belong to the primary table (the one after FROM) " +"and the table of the active JOIN." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:501 +msgid "JOIN Limitations" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:503 +msgid "" +"Joins can be very expensive operations if the secondary table is not " +"indexed on the key field being used." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:504 +msgid "" +"Joined fields may not be used in WHERE clauses, or ORDER BY clauses at " +"this time. The join is essentially evaluated after all primary table " +"subsetting is complete, and after the ORDER BY pass." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:505 +msgid "" +"Joined fields may not be used as keys in later joins. So you could not " +"use the province id in a city to lookup the province record, and then use" +" a nation id from the province id to lookup the nation record. This is a" +" sensible thing to want and could be implemented, but is not currently " +"supported." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:506 +msgid "" +"Datasource names for joined tables are evaluated relative to the current " +"processes working directory, not the path to the primary datasource." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:507 +msgid "" +"These are not true LEFT or RIGHT joins in the RDBMS sense. Whether or " +"not a secondary record exists for the join key or not, one and only one " +"copy of the primary record is returned in the result set. If a secondary" +" record cannot be found, the secondary derived fields will be NULL. If " +"more than one matching secondary field is found only the first will be " +"used." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:510 +msgid "UNION ALL" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:512 +msgid "" +"The SQL engine can deal with several SELECT combined with UNION ALL. The " +"effect of UNION ALL is to concatenate the rows returned by the right " +"SELECT statement to the rows returned by the left SELECT statement." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:523 +msgid "UNION ALL restrictions" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:525 +msgid "" +"The processing of UNION ALL in OGR differs from the SQL standard, in " +"which it accepts that the columns from the various SELECT are not " +"identical. In that case, it will return a super-set of all the fields " +"from each SELECT statement." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:529 +msgid "" +"There is also a restriction : ORDER BY can only be specified for each " +"SELECT, and not at the level of the result of the union." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:533 +msgid "SPECIAL FIELDS" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:535 +msgid "" +"The OGR SQL query processor treats some attributes of the features as " +"built-in special fields which can be used in SQL statements alongside the" +" other fields. These fields can be placed in the SELECT list, the WHERE " +"clause and the ORDER BY clause respectively. Special fields will not be " +"included in the result by default but they may be explicitly included by " +"adding them to the SELECT list. When accessing field values, the special " +"fields will take precedence over other fields in the data source with the" +" same names." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:545 +#: ../../source/user/sql_sqlite_dialect.rst:161 +msgid "Feature id (FID)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:547 +msgid "" +"Normally the feature id is a special property of a feature and not " +"treated as an attribute of the feature. In some cases it is convenient " +"to be able to utilize the feature id in queries and result sets as a " +"regular field. To do so use the name ``FID``. If the layer has a named " +"FID column (:cpp:func:`OGRLayer::GetFIDColumn` != \"\"), this name may " +"also be used." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:554 +#: ../../source/user/sql_sqlite_dialect.rst:171 +#: ../../source/user/sql_sqlite_dialect.rst:179 +msgid "" +"The field wildcard expansions will not include the feature id, but it may" +" be explicitly included using a syntax like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:562 +#: ../../source/user/sql_sqlite_dialect.rst:120 +msgid "Geometry field" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:564 +msgid "" +"The OGR SQL dialect adds the geometry field of the datasource to the " +"result set by default. Users do not need to select the geometry " +"explicitly but it is still possible to do so. Common use case is when " +"geometry is the only field that is needed. In this case the name of the " +"geometry field to be used in the SQL statement is the name returned by " +":cpp:func:`OGRLayer::GetGeometryColumn`, and also \"Geometry Column = " +"...\" in :program:`ogrinfo` output. If the method returns an empty string" +" then a special name \"_ogr_geometry_\" must be used. The name begins " +"with an underscore and SQL syntax requires that it must appear between " +"double quotes. In addition the command line interpreter may require that " +"double quotes are escaped and the final SELECT statement could look like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:580 +msgid "OGR_GEOMETRY" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:582 +msgid "" +"Some of the data sources (like MapInfo tab) can handle geometries of " +"different types within the same layer. The ``OGR_GEOMETRY`` special field" +" represents the geometry type returned by " +":cpp:func:`OGRGeometry::getGeometryName` and can be used to distinguish " +"the various types. By using this field one can select particular types of" +" the geometries like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:593 +msgid "OGR_GEOM_WKT" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:595 +msgid "" +"The Well Known Text representation of the geometry can also be used as a " +"special field. To select the WKT of the geometry ``OGR_GEOM_WKT`` might " +"be included in the select list, like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:603 +msgid "" +"Using the ``OGR_GEOM_WKT`` and the ``LIKE`` operator in the WHERE clause " +"we can get similar effect as using OGR_GEOMETRY:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:612 +msgid "OGR_GEOM_AREA" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:614 +msgid "" +"The ``OGR_GEOM_AREA`` special field returns the area of the feature's " +"geometry computed by the OGRSurface::get_Area() method. For " +"OGRGeometryCollection and OGRMultiPolygon the value is the sum of the " +"areas of its members. For non-surface geometries the returned area is " +"0.0." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:619 +msgid "For example, to select only polygon features larger than a given area:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:626 +msgid "OGR_STYLE" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:628 +#: ../../source/user/sql_sqlite_dialect.rst:195 +msgid "" +"The ``OGR_STYLE`` special field represents the style string of the " +"feature returned by OGRFeature::GetStyleString(). By using this field and" +" the ``LIKE`` operator the result of the query can be filtered by the " +"style. For example we can select the annotation features as:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:638 +msgid "" +"It is possible to use the ``OGR_STYLE`` field name as a special field " +"name in the field selection as an alternate way of setting the " +":cpp:func:`OGRFeature::SetStyleString` value, typically by aliasing " +"another field or a string literal." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:647 +msgid "" +"By default, the OGR_STYLE field will still be visible as a regular field." +" If this is undesirable, starting with GDAL 3.10, it can be hidden by " +"adding the HIDDEN keyword at the end of the field specification." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:657 +msgid "CREATE INDEX" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:659 +msgid "" +"Some OGR SQL drivers support creating of attribute indexes. Currently " +"this includes the Shapefile driver. An index accelerates very simple " +"attribute queries of the form **fieldname = value**, which is what is " +"used by the ``JOIN`` capability. To create an attribute index on the " +"nation_id field of the nation table a command like this would be used:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:670 +msgid "Index Limitations" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:672 +msgid "" +"Indexes are not maintained dynamically when new features are added to or " +"removed from a layer." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:673 +msgid "" +"Very long strings (longer than 256 characters?) cannot currently be " +"indexed." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:674 +msgid "" +"To recreate an index it is necessary to drop all indexes on a layer and " +"then recreate all the indexes." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:675 +msgid "" +"Indexes are not used in any complex queries. Currently the only query " +"the will accelerate is a simple \"field = value\" query." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:678 +msgid "DROP INDEX" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:680 +msgid "" +"The OGR SQL DROP INDEX command can be used to drop all indexes on a " +"particular table, or just the index for a particular column." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:689 +msgid "ALTER TABLE" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:691 +msgid "The following OGR SQL ALTER TABLE commands can be used." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:693 +msgid "" +"-\"ALTER TABLE tablename ADD [COLUMN] columnname columntype\" to add a " +"new field. Supported if the layer declares the OLCCreateField capability." +" -\"ALTER TABLE tablename RENAME [COLUMN] oldcolumnname TO " +"newcolumnname\" to rename an existing field. Supported if the layer " +"declares the OLCAlterFieldDefn capability. -\"ALTER TABLE tablename ALTER" +" [COLUMN] columnname TYPE columntype\" to change the type of an existing " +"field. Supported if the layer declares the OLCAlterFieldDefn capability. " +"-\"ALTER TABLE tablename DROP [COLUMN] columnname\" to delete an existing" +" field. Supported if the layer declares the OLCDeleteField capability." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:698 +msgid "" +"The columntype value follows the syntax of the types supported by the " +"CAST operator described above." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:708 +msgid "DROP TABLE" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:710 +msgid "" +"The OGR SQL DROP TABLE command can be used to delete a table. This is " +"only supported on datasources that declare the ODsCDeleteLayer " +"capability." +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:5 +msgid "OGR SQL dialect and SQLITE SQL dialect" +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:7 +msgid "" +"The GDALDataset supports executing commands against a datasource via the " +":cpp:func:`GDALDataset::ExecuteSQL` method. How such commands are " +"evaluated is dependent on the datasets." +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:11 +msgid "" +"For most file formats (e.g. Shapefiles, GeoJSON, MapInfo files), the " +"built-in :ref:`ogr_sql_dialect` dialect will be used by defaults. It is " +"also possible to request the :ref:`sql_sqlite_dialect` alternate dialect " +"to be used, which will use the SQLite engine to evaluate commands on GDAL" +" datasets." +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:16 +msgid "" +"All OGR drivers for database systems: :ref:`vector.mysql`, " +":ref:`vector.pg`, :ref:`vector.oci`, :ref:`vector.sqlite`, " +":ref:`vector.gpkg`, :ref:`vector.odbc`, :ref:`vector.pgeo`, " +":ref:`vector.hana` and :ref:`vector.mssqlspatial`, override the " +":cpp:func:`GDALDataset::ExecuteSQL` function with dedicated " +"implementation and, by default, pass the SQL statements directly to the " +"underlying RDBMS. In these cases the SQL syntax varies in some " +"particulars from OGR SQL. Also, anything possible in SQL can then be " +"accomplished for these particular databases. Generally, only the result " +"of SELECT statements will be returned as layers. For those drivers, it is" +" also possible to explicitly request the ``OGRSQL`` and ``SQLITE`` " +"dialects, although performance will generally be much less as the native " +"SQL engine of those database systems." +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:29 +msgid "Dialects" +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:39 +msgid "ExecuteSQL()" +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:41 +msgid "" +"SQL is executed against an GDALDataset, not against a specific layer. " +"The call looks like this:" +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:50 +msgid "" +"The ``pszDialect`` argument is in theory intended to allow for support of" +" different command languages against a provider, but for now applications" +" should always pass an empty (not NULL) string to get the default " +"dialect." +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:54 +msgid "" +"The ``poSpatialFilter`` argument is a geometry used to select a bounding " +"rectangle for features to be returned in a manner similar to the " +":cpp:func:`OGRLayer::SetSpatialFilter` method. It may be NULL for no " +"special spatial restriction." +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:59 +msgid "" +"The result of an ExecuteSQL() call is usually a temporary OGRLayer " +"representing the results set from the statement. This is the case for a " +"SELECT statement for instance. The returned temporary layer should be " +"released with :cpp:func:`GDALDataset::ReleaseResultsSet` method when no " +"longer needed. Failure to release it before the datasource is destroyed " +"may result in a crash." +msgstr "" + +#: ../../source/user/raster_data_model.rst:5 +msgid "Raster Data Model" +msgstr "" + +#: ../../source/user/raster_data_model.rst:7 +msgid "" +"This document attempts to describe the GDAL data model. That is the types" +" of information that a GDAL data store can contain, and their semantics." +msgstr "" + +#: ../../source/user/raster_data_model.rst:10 +#: ../../source/user/vector_data_model.rst:123 +msgid "Dataset" +msgstr "" + +#: ../../source/user/raster_data_model.rst:12 +msgid "" +"A dataset (represented by the :cpp:class:`GDALDataset` class) is an " +"assembly of related raster bands and some information common to them all." +" In particular the dataset has a concept of the raster size (in pixels " +"and lines) that applies to all the bands. The dataset is also responsible" +" for the georeferencing transform and coordinate system definition of all" +" bands. The dataset itself can also have associated metadata, a list of " +"name/value pairs in string form." +msgstr "" + +#: ../../source/user/raster_data_model.rst:14 +msgid "" +"Note that the GDAL dataset, and raster band data model is loosely based " +"on the OpenGIS Grid Coverages specification." +msgstr "" + +#: ../../source/user/raster_data_model.rst:17 +msgid "Coordinate System" +msgstr "" + +#: ../../source/user/raster_data_model.rst:18 +msgid "" +"Dataset coordinate systems are represented as OpenGIS Well Known Text " +"strings. This can contain:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:20 +msgid "An overall coordinate system name." +msgstr "" + +#: ../../source/user/raster_data_model.rst:21 +msgid "A geographic coordinate system name." +msgstr "" + +#: ../../source/user/raster_data_model.rst:22 +msgid "A datum identifier." +msgstr "" + +#: ../../source/user/raster_data_model.rst:23 +msgid "An ellipsoid name, semi-major axis, and inverse flattening." +msgstr "" + +#: ../../source/user/raster_data_model.rst:24 +msgid "A prime meridian name and offset from Greenwich." +msgstr "" + +#: ../../source/user/raster_data_model.rst:25 +msgid "A projection method type (e.g., Transverse Mercator)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:26 +msgid "A list of projection parameters (e.g., central_meridian)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:27 +msgid "A units name, and conversion factor to meters or radians." +msgstr "" + +#: ../../source/user/raster_data_model.rst:28 +msgid "Names and ordering for the axes." +msgstr "" + +#: ../../source/user/raster_data_model.rst:29 +msgid "" +"Codes for most of the above in terms of predefined coordinate systems " +"from authorities such as EPSG." +msgstr "" + +#: ../../source/user/raster_data_model.rst:31 +msgid "" +"For more information on OpenGIS WKT coordinate system definitions, and " +"mechanisms to manipulate them, refer to the osr_tutorial document and/or " +"the OGRSpatialReference class documentation." +msgstr "" + +#: ../../source/user/raster_data_model.rst:33 +msgid "" +"The coordinate system returned by " +":cpp:func:`GDALDataset::GetProjectionRef` describes the georeferenced " +"coordinates implied by the affine georeferencing transform returned by " +":cpp:func:`GDALDataset::GetGeoTransform`. The coordinate system returned " +"by :cpp:func:`GDALDataset::GetGCPProjection` describes the georeferenced " +"coordinates of the GCPs returned by :cpp:func:`GDALDataset::GetGCPs`." +msgstr "" + +#: ../../source/user/raster_data_model.rst:35 +msgid "" +"Note that a returned coordinate system strings of \"\" indicates nothing " +"is known about the georeferencing coordinate system." +msgstr "" + +#: ../../source/user/raster_data_model.rst:40 +msgid "Affine GeoTransform" +msgstr "" + +#: ../../source/user/raster_data_model.rst:42 +msgid "" +"GDAL datasets have two ways of describing the relationship between raster" +" positions (in pixel/line coordinates) and georeferenced coordinates. The" +" first, and most commonly used is the affine transform (the other is " +"GCPs)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:44 +msgid "" +"The affine transform consists of six coefficients returned by " +":cpp:func:`GDALDataset::GetGeoTransform` which map pixel/line coordinates" +" into georeferenced space using the following relationship:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:51 +msgid "" +"In case of north up images, the GT(2) and GT(4) coefficients are zero, " +"and the GT(1) is pixel width, and GT(5) is pixel height. The " +"(GT(0),GT(3)) position is the top left corner of the top left pixel of " +"the raster." +msgstr "" + +#: ../../source/user/raster_data_model.rst:53 +msgid "" +"Note that the pixel/line coordinates in the above are from (0.0,0.0) at " +"the top left corner of the top left pixel to " +"(width_in_pixels,height_in_pixels) at the bottom right corner of the " +"bottom right pixel. The pixel/line location of the center of the top left" +" pixel would therefore be (0.5,0.5)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:56 +msgid "GCPs" +msgstr "" + +#: ../../source/user/raster_data_model.rst:58 +msgid "" +"A dataset can have a set of control points relating one or more positions" +" on the raster to georeferenced coordinates. All GCPs share a " +"georeferencing coordinate system (returned by " +":cpp:func:`GDALDataset::GetGCPProjection`). Each GCP (represented as the " +"GDAL_GCP class) contains the following:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:73 +msgid "" +"The pszId string is intended to be a unique (and often, but not always " +"numerical) identifier for the GCP within the set of GCPs on this dataset." +" The pszInfo is usually an empty string, but can contain any user defined" +" text associated with the GCP. Potentially this can also contain machine " +"parsable information on GCP status though that isn't done at this time." +msgstr "" + +#: ../../source/user/raster_data_model.rst:75 +msgid "" +"The (Pixel,Line) position is the GCP location on the raster. The (X,Y,Z) " +"position is the associated georeferenced location with the Z often being " +"zero." +msgstr "" + +#: ../../source/user/raster_data_model.rst:77 +msgid "" +"The GDAL data model does not imply a transformation mechanism that must " +"be generated from the GCPs ... this is left to the application. However " +"1st to 5th order polynomials are common." +msgstr "" + +#: ../../source/user/raster_data_model.rst:79 +msgid "" +"Normally a dataset will contain either an affine geotransform, GCPs or " +"neither. It is uncommon to have both, and it is undefined which is " +"authoritative." +msgstr "" + +#: ../../source/user/raster_data_model.rst:82 +msgid "Metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:84 +msgid "" +"GDAL metadata is auxiliary format and application specific textual data " +"kept as a list of name/value pairs. The names are required to be well " +"behaved tokens (no spaces, or odd characters). The values can be of any " +"length, and contain anything except an embedded null (ASCII zero)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:86 +msgid "" +"The metadata handling system is not well tuned to handling very large " +"bodies of metadata. Handling of more than 100K of metadata for a dataset " +"is likely to lead to performance degradation." +msgstr "" + +#: ../../source/user/raster_data_model.rst:88 +msgid "" +"Some formats will support generic (user defined) metadata, while other " +"format drivers will map specific format fields to metadata names. For " +"instance the TIFF driver returns a few information tags as metadata " +"including the date/time field which is returned as:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:94 +msgid "" +"Metadata is split into named groups called domains, with the default " +"domain having no name (NULL or \"\"). Some specific domains exist for " +"special purposes. Note that currently there is no way to enumerate all " +"the domains available for a given object, but applications can \"test\" " +"for any domains they know how to interpret." +msgstr "" + +#: ../../source/user/raster_data_model.rst:96 +msgid "" +"The following metadata items have well defined semantics in the default " +"domain:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:98 +msgid "" +"AREA_OR_POINT: May be either \"Area\" (the default) or \"Point\". " +"Indicates whether a pixel value should be assumed to represent a sampling" +" over the region of the pixel or a point sample at the center of the " +"pixel. This is not intended to influence interpretation of georeferencing" +" which remains area oriented." +msgstr "" + +#: ../../source/user/raster_data_model.rst:99 +msgid "" +"NODATA_VALUES: The value is a list of space separated pixel values " +"matching the number of bands in the dataset that can be collectively used" +" to identify pixels that are nodata in the dataset. With this style of " +"nodata a pixel is considered nodata in all bands if and only if all bands" +" match the corresponding value in the NODATA_VALUES tuple. This metadata " +"is not widely honoured by GDAL drivers, algorithms or utilities at this " +"time." +msgstr "" + +#: ../../source/user/raster_data_model.rst:100 +msgid "" +"MATRIX_REPRESENTATION: This value, used for Polarimetric SAR datasets, " +"contains the matrix representation that this data is provided in. The " +"following are acceptable values:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:102 +msgid "SCATTERING" +msgstr "" + +#: ../../source/user/raster_data_model.rst:103 +msgid "SYMMETRIZED_SCATTERING" +msgstr "" + +#: ../../source/user/raster_data_model.rst:104 +msgid "COVARIANCE" +msgstr "" + +#: ../../source/user/raster_data_model.rst:105 +msgid "SYMMETRIZED_COVARIANCE" +msgstr "" + +#: ../../source/user/raster_data_model.rst:106 +msgid "COHERENCY" +msgstr "" + +#: ../../source/user/raster_data_model.rst:107 +msgid "SYMMETRIZED_COHERENCY" +msgstr "" + +#: ../../source/user/raster_data_model.rst:108 +msgid "KENNAUGH" +msgstr "" + +#: ../../source/user/raster_data_model.rst:109 +msgid "SYMMETRIZED_KENNAUGH" +msgstr "" + +#: ../../source/user/raster_data_model.rst:110 +msgid "" +"POLARIMETRIC_INTERP: This metadata item is defined for Raster Bands for " +"polarimetric SAR data. This indicates which entry in the specified matrix" +" representation of the data this band represents. For a dataset provided " +"as a scattering matrix, for example, acceptable values for this metadata " +"item are HH, HV, VH, VV. When the dataset is a covariance matrix, for " +"example, this metadata item will be one of Covariance_11, Covariance_22, " +"Covariance_33, Covariance_12, Covariance_13, Covariance_23 (since the " +"matrix itself is a hermitian matrix, that is all the data that is " +"required to describe the matrix)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:111 +msgid "" +"METADATATYPE: If IMAGERY Domain present, the item consist the reader " +"which processed the metadata. Now present such readers:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:113 +msgid "DG: DigitalGlobe imagery metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:114 +msgid "GE: GeoEye (or formally SpaceImaging) imagery metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:115 +msgid "OV: OrbView imagery metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:116 +msgid "DIMAP: Pleiades imagery metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:117 +msgid "MSP: Resurs DK-1 imagery metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:118 +msgid "ODL: Landsat imagery metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:119 +msgid "" +"CACHE_PATH: A cache directory path. Now this metadata item sets only by " +"WMS driver. This is useful when dataset deletes with cached data or when " +"external program need to put tiles in cache for some area of interest." +msgstr "" + +#: ../../source/user/raster_data_model.rst:122 +msgid "SUBDATASETS Domain" +msgstr "" + +#: ../../source/user/raster_data_model.rst:124 +msgid "" +"The SUBDATASETS domain holds a list of child datasets. Normally this is " +"used to provide pointers to a list of images stored within a single multi" +" image file." +msgstr "" + +#: ../../source/user/raster_data_model.rst:126 +msgid "" +"For example, an NITF with two images might have the following subdataset " +"list." +msgstr "" + +#: ../../source/user/raster_data_model.rst:135 +msgid "" +"The value of the _NAME is the string that can be passed to " +":cpp:func:`GDALOpen` to access the file. The _DESC value is intended to " +"be a more user friendly string that can be displayed to the user in a " +"selector." +msgstr "" + +#: ../../source/user/raster_data_model.rst:137 +msgid "" +"Drivers which support subdatasets advertise the ``DMD_SUBDATASETS`` " +"capability. This information is reported when the --format and --formats " +"options are passed to the command line utilities." +msgstr "" + +#: ../../source/user/raster_data_model.rst:139 +msgid "" +"Currently, drivers which support subdatasets are: ADRG, ECRGTOC, " +"GEORASTER, GTiff, HDF4, HDF5, netCDF, NITF, NTv2, OGDI, PDF, " +"PostGISRaster, Rasterlite, RPFTOC, RS2, TileDB, WCS, and WMS." +msgstr "" + +#: ../../source/user/raster_data_model.rst:142 +msgid "IMAGE_STRUCTURE Domain" +msgstr "" + +#: ../../source/user/raster_data_model.rst:144 +msgid "" +"Metadata in the default domain is intended to be related to the image, " +"and not particularly related to the way the image is stored on disk. That" +" is, it is suitable for copying with the dataset when it is copied to a " +"new format. Some information of interest is closely tied to a particular " +"file format and storage mechanism. In order to prevent this getting " +"copied along with datasets it is placed in a special domain called " +"IMAGE_STRUCTURE that should not normally be copied to new formats." +msgstr "" + +#: ../../source/user/raster_data_model.rst:146 +msgid "" +"Currently the following items are defined by :ref:`rfc-14` as having " +"specific semantics in the IMAGE_STRUCTURE domain." +msgstr "" + +#: ../../source/user/raster_data_model.rst:148 +msgid "" +"COMPRESSION: The compression type used for this dataset or band. There is" +" no fixed catalog of compression type names, but where a given format " +"includes a COMPRESSION creation option, the same list of values should be" +" used here as there." +msgstr "" + +#: ../../source/user/raster_data_model.rst:149 +msgid "" +"NBITS: The actual number of bits used for this band, or the bands of this" +" dataset. Normally only present when the number of bits is non-standard " +"for the datatype, such as when a 1 bit TIFF is represented through GDAL " +"as GDT_Byte." +msgstr "" + +#: ../../source/user/raster_data_model.rst:150 +msgid "" +"INTERLEAVE: This only applies on datasets, and the value should be one of" +" PIXEL, LINE or BAND. It can be used as a data access hint." +msgstr "" + +#: ../../source/user/raster_data_model.rst:151 +msgid "" +"PIXELTYPE: This may appear on a GDT_Byte band (or the corresponding " +"dataset) and have the value SIGNEDBYTE to indicate the unsigned byte " +"values between 128 and 255 should be interpreted as being values between " +"-128 and -1 for applications that recognise the SIGNEDBYTE type. Starting" +" with GDAL 3.7, this metadata item is no longer used, as the Int8 data " +"type is used for signed bytes." +msgstr "" + +#: ../../source/user/raster_data_model.rst:158 +msgid "RPC Domain" +msgstr "" + +#: ../../source/user/raster_data_model.rst:160 +msgid "" +"The RPC metadata domain holds metadata describing the Rational Polynomial" +" Coefficient geometry model for the image if present. This geometry model" +" can be used to transform between pixel/line and georeferenced locations." +" The items defining the model are:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:162 +msgid "" +"ERR_BIAS: Error - Bias. The RMS bias error in meters per horizontal axis " +"of all points in the image (-1.0 if unknown)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:163 +msgid "" +"ERR_RAND: Error - Random. RMS random error in meters per horizontal axis " +"of each point in the image (-1.0 if unknown)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:164 +msgid "LINE_OFF: Line Offset" +msgstr "" + +#: ../../source/user/raster_data_model.rst:165 +msgid "SAMP_OFF: Sample Offset" +msgstr "" + +#: ../../source/user/raster_data_model.rst:166 +msgid "LAT_OFF: Geodetic Latitude Offset" +msgstr "" + +#: ../../source/user/raster_data_model.rst:167 +msgid "LONG_OFF: Geodetic Longitude Offset" +msgstr "" + +#: ../../source/user/raster_data_model.rst:168 +msgid "HEIGHT_OFF: Geodetic Height Offset" +msgstr "" + +#: ../../source/user/raster_data_model.rst:169 +msgid "LINE_SCALE: Line Scale" +msgstr "" + +#: ../../source/user/raster_data_model.rst:170 +msgid "SAMP_SCALE: Sample Scale" +msgstr "" + +#: ../../source/user/raster_data_model.rst:171 +msgid "LAT_SCALE: Geodetic Latitude Scale" +msgstr "" + +#: ../../source/user/raster_data_model.rst:172 +msgid "LONG_SCALE: Geodetic Longitude Scale" +msgstr "" + +#: ../../source/user/raster_data_model.rst:173 +msgid "HEIGHT_SCALE: Geodetic Height Scale" +msgstr "" + +#: ../../source/user/raster_data_model.rst:174 +msgid "" +"LINE_NUM_COEFF (1-20): Line Numerator Coefficients. Twenty coefficients " +"for the polynomial in the Numerator of the rn equation. (space separated)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:175 +msgid "" +"LINE_DEN_COEFF (1-20): Line Denominator Coefficients. Twenty coefficients" +" for the polynomial in the Denominator of the rn equation. (space " +"separated)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:176 +msgid "" +"SAMP_NUM_COEFF (1-20): Sample Numerator Coefficients. Twenty coefficients" +" for the polynomial in the Numerator of the cn equation. (space " +"separated)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:177 +msgid "" +"SAMP_DEN_COEFF (1-20): Sample Denominator Coefficients. Twenty " +"coefficients for the polynomial in the Denominator of the cn equation. " +"(space separated)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:179 +msgid "" +"These fields are directly derived from the document prospective GeoTIFF " +"RPC document (http://geotiff.maptools.org/rpc_prop.html) which in turn is" +" closely modeled on the NITF RPC00B definition." +msgstr "" + +#: ../../source/user/raster_data_model.rst:181 +msgid "" +"The line and pixel offset expressed with LINE_OFF and SAMP_OFF are with " +"respect to the center of the pixel." +msgstr "" + +#: ../../source/user/raster_data_model.rst:184 +msgid "IMAGERY Domain (remote sensing)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:186 +msgid "" +"For satellite or aerial imagery the IMAGERY Domain may be present. It " +"depends on the existence of special metadata files near the image file. " +"The files at the same directory with image file tested by the set of " +"metadata readers, if files can be processed by the metadata reader, it " +"fill the IMAGERY Domain with the following items:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:188 +msgid "SATELLITEID: A satellite or scanner name" +msgstr "" + +#: ../../source/user/raster_data_model.rst:189 +msgid "" +"CLOUDCOVER: Cloud coverage. The value between 0 - 100 or 999 if not " +"available" +msgstr "" + +#: ../../source/user/raster_data_model.rst:190 +msgid "ACQUISITIONDATETIME: The image acquisition date time in UTC" +msgstr "" + +#: ../../source/user/raster_data_model.rst:193 +msgid "xml: Domains" +msgstr "" + +#: ../../source/user/raster_data_model.rst:195 +msgid "" +"Any domain name prefixed with \"xml:\" is not normal name/value metadata." +" It is a single XML document stored in one big string." +msgstr "" + +#: ../../source/user/raster_data_model.rst:198 +msgid "Raster Band" +msgstr "" + +#: ../../source/user/raster_data_model.rst:200 +msgid "" +"A raster band is represented in GDAL with the :cpp:class:`GDALRasterBand`" +" class. It represents a single raster band/channel/layer. It does not " +"necessarily represent a whole image. For instance, a 24bit RGB image " +"would normally be represented as a dataset with three bands, one for red," +" one for green and one for blue." +msgstr "" + +#: ../../source/user/raster_data_model.rst:202 +msgid "A raster band has the following properties:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:204 +msgid "" +"A width and height in pixels and lines. This is the same as that defined " +"for the dataset, if this is a full resolution band." +msgstr "" + +#: ../../source/user/raster_data_model.rst:205 +msgid "" +"A datatype (GDALDataType). One of Byte, Int8, UInt16, Int16, UInt32, " +"Int32, UInt64, Int64, Float32, Float64, and the complex types CInt16, " +"CInt32, CFloat32, and CFloat64." +msgstr "" + +#: ../../source/user/raster_data_model.rst:207 +msgid "" +"UInt64 and Int64 data types have been added in GDAL 3.5. Beyond reading " +"and write pixel values, their support is limited. Some algorithms might " +"use 64-bit floating-point internally (warping), as well as some methods " +"returning only double values (GetMinimum(), GetMaximum(), etc.), or even " +"32-bit floating point (overview, RasterIO resampling). Hence the range " +"where exact values are preserved can be [0, 2^53] (or less if 32-bit " +"floating-point is used)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:209 +msgid "Int8 data type has been added in GDAL 3.7." +msgstr "" + +#: ../../source/user/raster_data_model.rst:211 +msgid "" +"A block size. This is a preferred (efficient) access chunk size. For " +"tiled images this will be one tile. For scanline oriented images this " +"will normally be one scanline." +msgstr "" + +#: ../../source/user/raster_data_model.rst:212 +msgid "" +"A list of name/value pair metadata in the same format as the dataset, but" +" of information that is potentially specific to this band." +msgstr "" + +#: ../../source/user/raster_data_model.rst:213 +msgid "An optional description string." +msgstr "" + +#: ../../source/user/raster_data_model.rst:214 +msgid "" +"An optional single nodata pixel value (see also NODATA_VALUES metadata on" +" the dataset for multi-band style nodata values)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:215 +msgid "" +"An optional nodata mask band marking pixels as nodata or in some cases " +"transparency as discussed in RFC 15: Band Masks and documented in " +"GDALRasterBand::GetMaskBand()." +msgstr "" + +#: ../../source/user/raster_data_model.rst:216 +msgid "" +"An optional list of category names (effectively class names in a thematic" +" image)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:217 +msgid "An optional minimum and maximum value." +msgstr "" + +#: ../../source/user/raster_data_model.rst:218 +msgid "Optional statistics stored in metadata:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:220 +msgid "STATISTICS_MEAN: mean" +msgstr "" + +#: ../../source/user/raster_data_model.rst:221 +msgid "STATISTICS_MINIMUM: minimum" +msgstr "" + +#: ../../source/user/raster_data_model.rst:222 +msgid "STATISTICS_MAXIMUM: maximum" +msgstr "" + +#: ../../source/user/raster_data_model.rst:223 +msgid "STATISTICS_STDDEV: standard deviation" +msgstr "" + +#: ../../source/user/raster_data_model.rst:224 +msgid "" +"STATISTICS_APPROXIMATE: only present if GDAL has computed approximate " +"statistics" +msgstr "" + +#: ../../source/user/raster_data_model.rst:225 +msgid "STATISTICS_VALID_PERCENT: percentage of valid (not nodata) pixel" +msgstr "" + +#: ../../source/user/raster_data_model.rst:227 +msgid "" +"An optional offset and scale for transforming raster values into meaning " +"full values (e.g., translate height to meters)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:228 +msgid "" +"An optional raster unit name. For instance, this might indicate linear " +"units for elevation data." +msgstr "" + +#: ../../source/user/raster_data_model.rst:229 +msgid "A color interpretation for the band. This is one of:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:231 +msgid "GCI_Undefined: the default, nothing is known." +msgstr "" + +#: ../../source/user/raster_data_model.rst:232 +msgid "GCI_GrayIndex: this is an independent gray-scale image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:233 +msgid "GCI_PaletteIndex: this raster acts as an index into a color table" +msgstr "" + +#: ../../source/user/raster_data_model.rst:234 +msgid "GCI_RedBand: this raster is the red portion of an RGB or RGBA image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:235 +msgid "GCI_GreenBand: this raster is the green portion of an RGB or RGBA image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:236 +msgid "GCI_BlueBand: this raster is the blue portion of an RGB or RGBA image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:237 +msgid "GCI_AlphaBand: this raster is the alpha portion of an RGBA image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:238 +msgid "GCI_HueBand: this raster is the hue of an HLS image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:239 +msgid "GCI_SaturationBand: this raster is the saturation of an HLS image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:240 +msgid "GCI_LightnessBand: this raster is the hue of an HLS image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:241 +msgid "GCI_CyanBand: this band is the cyan portion of a CMY or CMYK image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:242 +msgid "GCI_MagentaBand: this band is the magenta portion of a CMY or CMYK image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:243 +msgid "GCI_YellowBand: this band is the yellow portion of a CMY or CMYK image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:244 +msgid "GCI_BlackBand: this band is the black portion of a CMYK image." +msgstr "" + +#: ../../source/user/raster_data_model.rst:246 +msgid "A color table, described in more detail later." +msgstr "" + +#: ../../source/user/raster_data_model.rst:247 +msgid "Knowledge of reduced resolution overviews (pyramids) if available." +msgstr "" + +#: ../../source/user/raster_data_model.rst:250 +msgid "Color Table" +msgstr "" + +#: ../../source/user/raster_data_model.rst:252 +msgid "" +"A color table consists of zero or more color entries described in C by " +"the following structure:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:271 +msgid "" +"The color table also has a palette interpretation value " +"(GDALPaletteInterp) which is one of the following values, and indicates " +"how the c1/c2/c3/c4 values of a color entry should be interpreted." +msgstr "" + +#: ../../source/user/raster_data_model.rst:273 +msgid "GPI_Gray: Use c1 as gray scale value." +msgstr "" + +#: ../../source/user/raster_data_model.rst:274 +msgid "GPI_RGB: Use c1 as red, c2 as green, c3 as blue and c4 as alpha." +msgstr "" + +#: ../../source/user/raster_data_model.rst:275 +msgid "GPI_CMYK: Use c1 as cyan, c2 as magenta, c3 as yellow and c4 as black." +msgstr "" + +#: ../../source/user/raster_data_model.rst:276 +msgid "GPI_HLS: Use c1 as hue, c2 as lightness, and c3 as saturation." +msgstr "" + +#: ../../source/user/raster_data_model.rst:278 +msgid "" +"To associate a color with a raster pixel, the pixel value is used as a " +"subscript into the color table. That means that the colors are always " +"applied starting at zero and ascending. There is no provision for " +"indicating a pre-scaling mechanism before looking up in the color table." +msgstr "" + +#: ../../source/user/raster_data_model.rst:281 +msgid "Overviews" +msgstr "" + +#: ../../source/user/raster_data_model.rst:283 +msgid "" +"A band may have zero or more overviews. Each overview is represented as a" +" \"free standing\" :cpp:class:`GDALRasterBand`. The size (in pixels and " +"lines) of the overview will be different than the underlying raster, but " +"the geographic region covered by overviews is the same as the full " +"resolution band." +msgstr "" + +#: ../../source/user/raster_data_model.rst:285 +msgid "" +"The overviews are used to display reduced resolution overviews more " +"quickly than could be done by reading all the full resolution data and " +"downsampling." +msgstr "" + +#: ../../source/user/raster_data_model.rst:287 +msgid "" +"Bands also have a HasArbitraryOverviews property which is TRUE if the " +"raster can be read at any resolution efficiently but with no distinct " +"overview levels. This applies to some FFT encoded images, or images " +"pulled through gateways where downsampling can be done efficiently at the" +" remote point." +msgstr "" + +#: ../../source/user/raster_data_model.rst:289 +msgid "" +"How overviews are selected depends on the software logic. The " +":cpp:func:`GDALRasterBand::RasterIO` or :cpp:func:`GDALDataset::RasterIO`" +" methods document their logic." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:5 +msgid "SQL SQLite dialect" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:9 +msgid "" +"The ``SQLite`` dialect can be used as an alternate SQL dialect to the " +":ref:`ogr_sql_dialect`. This assumes that GDAL/OGR is built with support " +"for SQLite, and preferably with `Spatialite <https://www.gaia-" +"gis.it/fossil/libspatialite/index>`_ support too to benefit from spatial " +"functions." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:14 +msgid "" +"The SQLite dialect may be used with any OGR datasource, like the OGR SQL " +"dialect. The ``SQLite`` dialect can be requested with the ``SQLite`` " +"string passed as the dialect parameter of " +":cpp:func:`GDALDataset::ExecuteSQL`, or with the `-dialect` option of the" +" :ref:`ogrinfo` or :ref:`ogr2ogr` utilities." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:19 +msgid "" +"This is mainly aimed to execute SELECT statements, but, for datasources " +"that support update, INSERT/UPDATE/DELETE statements can also be run. " +"GDAL is internally using `the Virtual Table Mechanism of SQLite " +"<https://sqlite.org/vtab.html>`_ and therefore operations like ALTER " +"TABLE are not supported. For executing ALTER TABLE or DROP TABLE use " +":ref:`ogr_sql_dialect`" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:25 +msgid "" +"If the datasource is SQLite database (GeoPackage, SpatiaLite) then SQLite" +" dialect acts as native SQL dialect and Virtual Table Mechanism is not " +"used. It is possible to force GDAL to use Virtual Tables even in this " +"case by specifying \"-dialect INDIRECT_SQLITE\". This should be used only" +" when necessary, since going through the virtual table mechanism might " +"affect performance." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:31 +msgid "" +"The syntax of the SQL statements is fully the one of the SQLite SQL " +"engine. You can refer to the following pages:" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:34 +msgid "`SELECT <http://www.sqlite.org/lang_select.html>`_" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:35 +msgid "`INSERT <http://www.sqlite.org/lang_insert.html>`_" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:36 +msgid "`UPDATE <http://www.sqlite.org/lang_update.html>`_" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:37 +msgid "`DELETE <http://www.sqlite.org/lang_delete.html>`_" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:40 +msgid "SELECT statement" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:42 +msgid "" +"The SELECT statement is used to fetch layer features (analogous to table " +"rows in an RDBMS) with the result of the query represented as a temporary" +" layer of features. The layers of the datasource are analogous to tables " +"in an RDBMS and feature attributes are analogous to column values. The " +"simplest form of OGR SQLITE SELECT statement looks like this:" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:52 +msgid "" +"More complex statements can of course be used, including WHERE, JOIN, " +"USING, GROUP BY, ORDER BY, sub SELECT, ..." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:55 +msgid "" +"The table names that can be used are the layer names available in the " +"datasource on which the ExecuteSQL() method is called." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:58 +msgid "" +"Similarly to OGRSQL, it is also possible to refer to layers of other " +"datasources with the following syntax : " +"\"other_datasource_name\".\"layer_name\"." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:65 +msgid "" +"If the master datasource is SQLite database (GeoPackage, SpatiaLite) it " +"is necessary to use indirect SQLite dialect. Otherwise additional " +"datasources are never opened but tables to be used in joins are searched " +"from the master database." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:74 +msgid "" +"The column names that can be used in the result column list, in WHERE, " +"JOIN, ... clauses are the field names of the layers. Expressions, SQLite " +"functions, spatial functions, etc... can also be used." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:79 +msgid "" +"The conditions on fields expressed in WHERE clauses, or in JOINs are " +"translated, as far as possible, as attribute filters that are applied on " +"the underlying OGR layers. Joins can be very expensive operations if the " +"secondary table is not indexed on the key field being used." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:85 +msgid "LIKE operator" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:87 +msgid "" +"In SQLite, the LIKE operator is case insensitive, unless ``PRAGMA " +"case_sensitive_like = 1`` has been issued." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:90 +msgid "" +"Starting with GDAL 3.9, GDAL installs a custom LIKE comparison, such that" +" UTF-8 characters are taken into account by ``LIKE`` and ``ILIKE`` " +"operators. For ILIKE case insensitive comparisons, this is restricted to " +"the `ASCII " +"<https://en.wikipedia.org/wiki/Basic_Latin_(Unicode_block)>`__, `Latin-1 " +"Supplement <https://en.wikipedia.org/wiki/Latin-" +"1_Supplement_(Unicode_block)>`__, `Latin Extended-A " +"<https://en.wikipedia.org/wiki/Latin_Extended-A>`__, `Latin Extended-B " +"<https://en.wikipedia.org/wiki/Latin_Extended-B>`__, `Greek and Coptic " +"<https://en.wikipedia.org/wiki/Greek_and_Coptic>`__ and `Cyrillic " +"<https://en.wikipedia.org/wiki/Greek_and_Coptic>`__ Unicode categories." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:101 +msgid "Delimited identifiers" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:103 +msgid "" +"If names of layers or attributes are reserved keywords in SQL like 'FROM'" +" or they begin with a number or underscore they must be handled as " +"\"delimited identifiers\" and enclosed between double quotation marks in " +"queries. Double quotes can be used even when they are not strictly " +"needed." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:112 +msgid "" +"When SQL statements are used in the command shell and the statement " +"itself is put between double quotes, the internal double quotes must be " +"escaped with \\\\" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:122 +msgid "" +"The ``GEOMETRY`` special field represents the geometry of the feature " +"returned by OGRFeature::GetGeometryRef(). It can be explicitly specified " +"in the result column list of a SELECT, and is automatically selected if " +"the * wildcard is used." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:127 +msgid "" +"For OGR layers that have a non-empty geometry column name (generally for " +"RDBMS datasources), as returned by OGRLayer::GetGeometryColumn(), the " +"name of the geometry special field in the SQL statement will be the name " +"of the geometry column of the underlying OGR layer. If the name of the " +"geometry column in the source layer is empty, like with shapefiles etc., " +"the name to use in the SQL statement is always \"geometry\". Here we'll " +"use it case-insensitively (as all field names are in a SELECT statement):" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:138 +#: ../../source/user/sql_sqlite_dialect.rst:150 +#: ../../source/user/sql_sqlite_dialect.rst:216 +#: ../../source/user/sql_sqlite_dialect.rst:343 +#: ../../source/user/sql_sqlite_dialect.rst:354 +msgid "returns:" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:163 +msgid "" +"The feature id is a special property of a feature and not treated as an " +"attribute of the feature. In some cases it is convenient to be able to " +"utilize the feature id in queries and result sets as a regular field. To" +" do so use the name ``rowid``." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:168 +msgid "" +"Starting with GDAL 3.8, if the layer has a named FID column " +"(:cpp:func:`OGRLayer::GetFIDColumn` != \"\"), this name may also be used." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:186 +msgid "It is of course possible to rename it:" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:193 +msgid "OGR_STYLE special field" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:205 +msgid "Spatialite SQL functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:207 +msgid "" +"When GDAL/OGR is build with support for the `Spatialite <https://www" +".gaia-gis.it/fossil/libspatialite/index>`_ library, a lot of `extra SQL " +"functions <http://www.gaia-gis.it/gaia-sins/spatialite-sql-" +"latest.html>`_, in particular spatial functions, can be used in results " +"column fields, WHERE clauses, etc...." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:232 +msgid "" +"Note that due to the loose typing mechanism of SQLite, if a geometry " +"expression returns a NULL value for the first row, this will generally " +"cause OGR not to recognize the column as a geometry column. It might be " +"then useful to sort the results by making sure that non-null geometries " +"are returned first:" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:242 +msgid "OGR datasource SQL functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:244 +msgid "" +"The ``ogr_datasource_load_layers(datasource_name[, update_mode[, " +"prefix]])`` function can be used to automatically load all the layers of " +"a datasource as :ref:`VirtualOGR tables <vector.sqlite>`." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:260 +msgid "OGR layer SQL functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:262 +msgid "" +"The following SQL functions are available and operate on a layer name : " +"``ogr_layer_Extent()``, ``ogr_layer_SRID()``, " +"``ogr_layer_GeometryType()`` and ``ogr_layer_FeatureCount()``" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:280 +msgid "OGR compression functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:282 +msgid "" +"``ogr_deflate(text_or_blob[, compression_level])`` returns a binary blob " +"compressed with the ZLib deflate algorithm. See " +":cpp:func:`CPLZLibDeflate`" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:285 +msgid "" +"``ogr_inflate(compressed_blob)`` returns the decompressed binary blob, " +"from a blob compressed with the ZLib deflate algorithm. If the " +"decompressed binary is a string, use CAST(ogr_inflate(compressed_blob) AS" +" VARCHAR). See CPLZLibInflate()." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:291 +msgid "Other functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:293 +msgid "" +"The ``hstore_get_value()`` function can be used to extract a value " +"associate to a key from a HSTORE string, formatted like " +"\"key=>value,other_key=>other_value,...\"" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:303 +msgid "Raster related functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:305 +msgid "" +"The ``gdal_get_pixel_value()`` function (added in GDAL 3.7) can be used " +"to extract the value of a pixel in a GDAL dataset. It requires the " +"configuration option OGR_SQLITE_ALLOW_EXTERNAL_ACCESS to be set to YES " +"(for security reasons)." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:309 +msgid "It takes 5 arguments:" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:311 +msgid "a string with the dataset name" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:312 +msgid "a band number (numbering starting at 1)" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:313 +msgid "" +"a string being \"georef\" to indicate that subsequent values will be " +"georeferenced coordinates, or \"pixel\" to indicate that subsequent " +"values will be in column, line pixel space" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:316 +msgid "georeferenced X value or column number" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:317 +msgid "georeferenced Y value or line number" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:326 +msgid "OGR geocoding functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:328 +msgid "" +"The following SQL functions are available : ``ogr_geocode(...)`` and " +"``ogr_geocode_reverse(...)``." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:330 +msgid "" +"``ogr_geocode(name_to_geocode [, field_to_return [, option1 [, option2, " +"...]]])`` where name_to_geocode is a literal or a column name that must " +"be geocoded. field_to_return if specified can be \"geometry\" for the " +"geometry (default), or a field name of the layer returned by " +":cpp:func:`OGRGeocode`. The special field \"raw\" can also be used to " +"return the raw response (XML string) of the geocoding service. option1, " +"option2, etc.. must be of the key=value format, and are options " +"understood by :cpp:func:`OGRGeocodeCreateSession` or OGRGeocode()." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:337 +msgid "" +"This function internally uses the OGRGeocode() API. Refer to it for more " +"details." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:389 +msgid "" +"``ogr_geocode_reverse(longitude, latitude, field_to_return [, option1 [, " +"option2, ...]])`` where longitude, latitude is the coordinate to query. " +"field_to_return must be a field name of the layer returned by " +"OGRGeocodeReverse() (for example 'display_name'). The special field " +"\"raw\" can also be used to return the raw response (XML string) of the " +"geocoding service. option1, option2, etc.. must be of the key=value " +"format, and are options understood by OGRGeocodeCreateSession() or " +"OGRGeocodeReverse()." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:396 +msgid "" +"``ogr_geocode_reverse(geometry, field_to_return [, option1 [, option2, " +"...]])`` is also accepted as an alternate syntax where geometry is a " +"(Spatialite) point geometry." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:399 +msgid "" +"This function internally uses the :cpp:func:`OGRGeocodeReverse` API. " +"Refer to it for more details." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:402 +msgid "Spatialite spatial index" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:404 +msgid "" +"Spatialite spatial index mechanism can be triggered by making sure a " +"spatial index virtual table is mentioned in the SQL (of the form " +"idx_layername_geometrycolumn), or by using the more recent SpatialIndex " +"from the VirtualSpatialIndex extension. In which case, a in-memory RTree " +"will be built to be used to speed up the spatial queries." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:409 +msgid "" +"For example, a spatial intersection between 2 layers, by using a spatial " +"index on one of the layers to limit the number of actual geometry " +"intersection computations :" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:421 +msgid "or more elegantly :" +msgstr "" + +#: ../../source/user/vector_data_model.rst:5 +msgid "Vector Data Model" +msgstr "" + +#: ../../source/user/vector_data_model.rst:7 +msgid "" +"This page documents the classes used to handle vector data. Many data " +"types and method names are based on the OGC Simple Features data model, " +"so it may be helpful to review the `specifications published by OGC " +"<https://www.ogc.org/standard/sfa/>`__. For historical reasons, GDAL uses" +" the \"OGR\" prefix to denote types and functions that apply only to " +"vector data." +msgstr "" + +#: ../../source/user/vector_data_model.rst:11 +msgid "Class Overview" +msgstr "" + +#: ../../source/user/vector_data_model.rst:13 +msgid "The following classes form the core of the vector data model:" +msgstr "" + +#: ../../source/user/vector_data_model.rst:15 +msgid "" +"Geometry (:ref:`ogr_geometry.h <ogrgeometry_cpp>`): The geometry classes " +"(:cpp:class:`OGRGeometry`, etc) encapsulate the OGC vector data types. " +"They provide some geometry operations and translation to/from well known " +"binary and text format. A geometry includes a spatial reference system " +"(projection)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:16 +msgid "" +"Spatial Reference (:ref:`ogr_spatialref.h <ogrspatialref>`): An " +":cpp:class:`OGRSpatialReference` encapsulates the definition of a " +"projection and datum." +msgstr "" + +#: ../../source/user/vector_data_model.rst:17 +msgid "" +"Feature (:ref:`ogr_feature.h <ogrfeature_cpp>`): The " +":cpp:class:`OGRFeature` encapsulates the definition of a whole feature, " +"that is a set of geometries and attributes relating to a single entity." +msgstr "" + +#: ../../source/user/vector_data_model.rst:18 +msgid "" +"Feature Class Definition (:ref:`ogr_feature.h <ogrfeature_cpp>`): The " +":cpp:class:`OGRFeatureDefn` class captures the schema (set of field " +"definitions) for a group of related features (normally a whole layer)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:19 +msgid "" +"Layer (:ref:`ogrsf_frmts.h <ogrlayer_cpp>`): :cpp:class:`OGRLayer` is an " +"abstract class representing a layer of features in a " +":cpp:class:`GDALDataset`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:20 +msgid "" +"Dataset (:ref:`gdal_priv.h <gdaldataset_cpp>`): A " +":cpp:class:`GDALDataset` is an abstract base class representing a file or" +" database containing one or more :cpp:class:`OGRLayer` objects." +msgstr "" + +#: ../../source/user/vector_data_model.rst:21 +msgid "" +"Drivers (:ref:`gdal_priv.h <gdaldriver_cpp>`): A :cpp:class:`GDALDriver` " +"represents a translator for a specific format, capable of opening and " +"possibly writing :cpp:class:`GDALDataset` objects. All available drivers " +"are managed by the :cpp:class:`GDALDriverManager`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:24 +msgid "Geometry" +msgstr "" + +#: ../../source/user/vector_data_model.rst:26 +msgid "" +"Individual geometry classes are used to represent the different types of " +"vector geometry. All the geometry classes derive from " +":cpp:class:`OGRGeometry` which defines the common functionality of all " +"geometries. Geometry types include :cpp:class:`OGRPoint`, " +":cpp:class:`OGRLineString`, :cpp:class:`OGRPolygon`, " +":cpp:class:`OGRGeometryCollection`, :cpp:class:`OGRMultiPoint`, " +":cpp:class:`OGRMultiLineString`, :cpp:class:`OGRMultiPolygon`, and " +":cpp:class:`OGRPolyhedralSurface`. The special case of a triangular " +"polygon can be represented as a :cpp:class:`OGRTriangle`, a non-" +"overlapping collection of which can be represented by an " +":cpp:class:`OGRTriangulatedSurface`. An additional set of types is used " +"to store non-linear geometries: :cpp:class:`OGRCircularString`, " +":cpp:class:`OGRCompoundCurve`, :cpp:class:`OGRCurvePolygon`, " +":cpp:class:`OGRMultiCurve` and :cpp:class:`OGRMultiSurface`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:30 +msgid "" +"Any of the above geometry classes can store coordinates in two (XY), " +"three (XYZ or XYM), or four (XYZM) dimensions." +msgstr "" + +#: ../../source/user/vector_data_model.rst:32 +msgid "" +"Additional intermediate classes contain functionality that is used by " +"multiple geometry types. These include :cpp:class:`OGRCurve` (base class " +"for :cpp:class:`OGRLineString`) and :cpp:class:`OGRSurface` (base class " +"for :cpp:class:`OGRPolygon`). Some intermediate interfaces modeled in the" +" simple features abstract model and SFCOM are not modeled in OGR at this " +"time. In most cases the methods are aggregated into other classes." +msgstr "" + +#: ../../source/user/vector_data_model.rst:-1 +msgid "Diagram of OGRGeometry and subclasses" +msgstr "" + +#: ../../source/user/vector_data_model.rst:37 +msgid "" +"The :cpp:class:`OGRGeometryFactory` is used to convert well known text " +"(WKT) and well known binary (WKB) format data into the appropriate " +":cpp:class:`OGRGeometry` subclass. These are predefined ASCII and binary " +"formats for representing all the types of simple features geometries." +msgstr "" + +#: ../../source/user/vector_data_model.rst:39 +msgid "" +"The :cpp:class:`OGRGeometry` includes a reference to an " +":cpp:class:`OGRSpatialReference` object, defining the spatial reference " +"system of that geometry. This is normally a reference to a shared spatial" +" reference object with reference counting for each of the " +":cpp:class:`OGRGeometry` objects using it." +msgstr "" + +#: ../../source/user/vector_data_model.rst:41 +msgid "" +"While it is theoretically possible to derive other or more specific " +"geometry classes from the existing :cpp:class:`OGRGeometry` classes, this" +" isn't an aspect that has been well thought out. In particular, it would " +"be possible to create specialized classes using the " +":cpp:class:`OGRGeometryFactory` without modifying it." +msgstr "" + +#: ../../source/user/vector_data_model.rst:44 +msgid "Compatibility issues with non-linear geometries" +msgstr "" + +#: ../../source/user/vector_data_model.rst:46 +msgid "" +"Generic mechanisms have been introduced so that creating or modifying a " +"feature with a non-linear geometry in a layer of a driver that does not " +"support it will transform that geometry in the closest matching linear " +"geometry. This linearization can be controlled using " +":ref:`configoptions_vector`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:48 +msgid "" +"On the other side, when retrieving data from the OGR C API, the " +":cpp:func:`OGRSetNonLinearGeometriesEnabledFlag` function can be used, so" +" that geometries and layer geometry type returned are also converted to " +"their linear approximation if necessary." +msgstr "" + +#: ../../source/user/vector_data_model.rst:51 +msgid "Spatial Reference" +msgstr "" + +#: ../../source/user/vector_data_model.rst:53 +msgid "" +"The :cpp:class:`OGRSpatialReference` class is intended to store an " +"OpenGIS Spatial Reference System definition. Currently local, geographic " +"and projected coordinate systems are supported. Vertical coordinate " +"systems, geocentric coordinate systems, and compound (horizontal + " +"vertical) coordinate systems are as well supported in recent GDAL " +"versions." +msgstr "" + +#: ../../source/user/vector_data_model.rst:55 +msgid "" +"The spatial coordinate system data model is inherited from the OpenGIS " +"Well Known Text format. A simple form of this is defined in the Simple " +"Features specifications. A more sophisticated form is found in the " +"Coordinate Transformation specification. The " +":cpp:class:`OGRSpatialReference` is built on the features of the " +"Coordinate Transformation specification but is intended to be compatible " +"with the earlier simple features form." +msgstr "" + +#: ../../source/user/vector_data_model.rst:57 +msgid "" +"There is also an associated :cpp:class:`OGRCoordinateTransformation` " +"class that encapsulates use of |PROJ| for converting between different " +"coordinate systems." +msgstr "" + +#: ../../source/user/vector_data_model.rst:60 +msgid "Feature / Feature Definition" +msgstr "" + +#: ../../source/user/vector_data_model.rst:62 +msgid "" +"The :cpp:class:`OGRGeometry` captures the geometry of a vector feature. " +"The :cpp:class:`OGRFeature` contains geometry, and adds feature " +"attributes, feature id, and a feature class identifier. It may also " +"contain styling information. Several geometries can be associated with an" +" :cpp:class:`OGRFeature`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:64 +msgid "" +"The set of attributes (:cpp:class:`OGRFieldDefn`), their types, names and" +" so forth is represented via the :cpp:class:`OGRFeatureDefn` class. One " +":cpp:class:`OGRFeatureDefn` normally exists for a layer of features. The " +"same definition is shared in a reference counted manner by the feature of" +" that type (or feature class)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:66 +msgid "" +"The feature id (FID) of a feature is intended to be a unique identifier " +"for the feature within the layer it is a member of. Freestanding " +"features, or features not yet written to a layer may have a null " +"(OGRNullFID) feature id. The feature ids are modeled in OGR as a 64-bit " +"integer; however, this is not sufficiently expressive to model the " +"natural feature ids in some formats. For instance, the GML feature id is " +"a string." +msgstr "" + +#: ../../source/user/vector_data_model.rst:68 +msgid "" +"The :cpp:class:`OGRFeatureDefn` also contains an indicator of the types " +"of geometry allowed for that feature class (returned as an " +":cpp:enum:`OGRwkbGeometryType` from " +":cpp:func:`OGRFeatureDefn::GetGeomType`). If this is " +":cpp:enumerator:`OGRwkbGeometryType::wkbUnknown` then any type of " +"geometry is allowed. This implies that features in a given layer can " +"potentially be of different geometry types though they will always share " +"a common attribute schema." +msgstr "" + +#: ../../source/user/vector_data_model.rst:70 +msgid "" +"Several geometry fields (:cpp:class:`OGRGeomFieldDefn`) can be associated" +" with an :cpp:class:`OGRFeatureDefn`. Each geometry field has its own " +"indicator of geometry type allowed, returned by " +":cpp:func:`OGRGeomFieldDefn::GetType`, and its spatial reference system, " +"returned by :cpp:func:`OGRGeomFieldDefn::GetSpatialRef`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:72 +msgid "" +"The :cpp:class:`OGRFeatureDefn` also contains a feature class name " +"(normally used as a layer name)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:75 +msgid "Field Definitions" +msgstr "" + +#: ../../source/user/vector_data_model.rst:77 +msgid "" +"The behavior of each field in a feature class is defined by a shared " +":cpp:class:`OGRFieldDefn`. The :cpp:class:`OGRFieldDefn` specifies the " +"field type from the values of :cpp:enum:`OGRFieldType`. Values stored in " +"this field may be further restricted according to a " +":cpp:enum:`OGRFieldSubType`. For example, a field may have a type of " +":cpp:enumerator:`OGRFieldType::OFTInteger` with a subtype of " +":cpp:enumerator:`OGRFieldSubType::OFSTBoolean`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:82 +msgid "" +"The :cpp:class:`OGRFieldDefn` can also track whether a field is allowed " +"to be null (:cpp:func:`OGRFieldDefn::IsNullable`), whether its value must" +" be unique (:cpp:func:`OGRFieldDefn::IsUnique`), and formatting " +"information such as the number of decimal digits, width, and " +"justification. It may also define a default value in case one is not " +"manually specified." +msgstr "" + +#: ../../source/user/vector_data_model.rst:85 +msgid "Field Domains" +msgstr "" + +#: ../../source/user/vector_data_model.rst:87 +msgid "" +"Some formats support the use of field domains that describe the values " +"that can be stored in a given attribute field. An " +":cpp:class:`OGRFieldDefn` may reference a single " +":cpp:class:`OGRFieldDomain` that is associated with a " +":cpp:class:`GDALDataset`. Programs using GDAL may use the " +":cpp:class:`OGRFieldDomain` to appropriately constrain user input. GDAL " +"does not perform validation itself and will allow the storage of values " +"that violate a field's associated :cpp:class:`OGRFieldDomain`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:90 +msgid "Available types of :cpp:class:`OGRFieldDomain` include:" +msgstr "" + +#: ../../source/user/vector_data_model.rst:92 +msgid "" +":cpp:class:`OGRCodedFieldDomain`, which constrains values those present " +"in a specified enumeration" +msgstr "" + +#: ../../source/user/vector_data_model.rst:93 +msgid "" +":cpp:class:`OGRRangeFieldDomain`, which constrains values to a specified " +"range" +msgstr "" + +#: ../../source/user/vector_data_model.rst:94 +msgid "" +":cpp:class:`OGRGlobFieldDomain`, which constrains values to those " +"matching a specified pattern" +msgstr "" + +#: ../../source/user/vector_data_model.rst:96 +msgid "" +"Additionally, an :cpp:class:`OGRFieldDomain` may define policies " +"describing the values that should be assigned to domain-controlled fields" +" when features are split or merged." +msgstr "" + +#: ../../source/user/vector_data_model.rst:99 +msgid "Layer" +msgstr "" + +#: ../../source/user/vector_data_model.rst:101 +msgid "" +"An :cpp:class:`OGRLayer` represents a layer of features within a data " +"source. All features in an :cpp:class:`OGRLayer` share a common schema " +"and are of the same :cpp:class:`OGRFeatureDefn`. An :cpp:class:`OGRLayer`" +" class also contains methods for reading features from the data source. " +"The :cpp:class:`OGRLayer` can be thought of as a gateway for reading and " +"writing features from an underlying data source such as a file on disk, " +"or the result of a database query." +msgstr "" + +#: ../../source/user/vector_data_model.rst:103 +msgid "" +"The :cpp:class:`OGRLayer` includes methods for sequential and random " +"reading and writing. Read access (via the " +":cpp:func:`OGRLayer::GetNextFeature` method) normally reads all features," +" one at a time sequentially; however, it can be limited to return " +"features intersecting a particular geographic region by installing a " +"spatial filter on the :cpp:class:`OGRLayer` (via the " +":cpp:func:`OGRLayer::SetSpatialFilter` method). A filter on attributes " +"can only be set with the :cpp:func:`OGRLayer::SetAttributeFilter` method." +" By default, all available attributes and geometries are read but this " +"can be controlled by flagging fields as ignored " +"(:cpp:func:`OGRLayer::SetIgnoredFields`)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:105 +msgid "" +"Starting with GDAL 3.6, as an alternative to getting features through " +"``GetNextFeature``, it is possible to retrieve them by batches, with a " +"column-oriented memory layout, using the " +":cpp:func:`OGRLayer::GetArrowStream` method (cf " +":ref:`vector_api_tut_arrow_stream`)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:107 +msgid "" +"An :cpp:class:`OGRLayer` may also store an :cpp:class:`OGRStyleTable` " +"that provides a set of styles that may be used by features in the layer. " +"More information on GDAL's handling of feature styles can be found in the" +" :ref:`ogr_feature_style`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:109 +msgid "" +"One flaw in the current OGR architecture is that the spatial and " +"attribute filters are set directly on the :cpp:class:`OGRLayer` which is " +"intended to be the only representative of a given layer in a data source." +" This means it isn't possible to have multiple read operations active at " +"one time with different spatial filters on each." +msgstr "" + +#: ../../source/user/vector_data_model.rst:114 +msgid "" +"Another question that might arise is why the :cpp:class:`OGRLayer` and " +":cpp:class:`OGRFeatureDefn` classes are distinct. An " +":cpp:class:`OGRLayer` always has a one-to-one relationship to an " +":cpp:class:`OGRFeatureDefn`, so why not amalgamate the classes? There are" +" two reasons:" +msgstr "" + +#: ../../source/user/vector_data_model.rst:116 +msgid "" +"As defined now :cpp:class:`OGRFeature` and :cpp:class:`OGRFeatureDefn` " +"don't depend on :cpp:class:`OGRLayer`, so they can exist independently in" +" memory without regard to a particular layer in a data store." +msgstr "" + +#: ../../source/user/vector_data_model.rst:117 +msgid "" +"The SF CORBA model does not have a concept of a layer with a single fixed" +" schema the way that the SFCOM and SFSQL models do. The fact that " +"features belong to a feature collection that is potentially not directly " +"related to their current feature grouping may be important to " +"implementing SFCORBA support using OGR." +msgstr "" + +#: ../../source/user/vector_data_model.rst:119 +msgid "" +"The :cpp:class:`OGRLayer` class is an abstract base class. An " +"implementation is expected to be subclassed for each file format driver " +"implemented. OGRLayers are normally owned directly by their " +":cpp:class:`GDALDataset`, and aren't instantiated or destroyed directly." +msgstr "" + +#: ../../source/user/vector_data_model.rst:125 +msgid "" +"A :cpp:class:`GDALDataset` represents a set of :cpp:class:`OGRLayer` " +"objects. This usually represents a single file, set of files, database or" +" gateway. A :cpp:class:`GDALDataset` has a list of :cpp:class:`OGRLayer` " +"which it owns but can return references to." +msgstr "" + +#: ../../source/user/vector_data_model.rst:127 +msgid "" +":cpp:class:`GDALDataset` is an abstract base class. An implementation is " +"expected to be subclassed for each file format driver implemented. " +":cpp:class:`GDALDataset` objects are not normally instantiated directly " +"but rather with the assistance of an :cpp:class:`GDALDriver`. Deleting an" +" :cpp:class:`GDALDataset` closes access to the underlying persistent data" +" source, but does not normally result in deletion of that file." +msgstr "" + +#: ../../source/user/vector_data_model.rst:129 +msgid "" +"A :cpp:class:`GDALDataset` has a name (usually a filename or database " +"connection string) that can be used to reopen the data source with a " +":cpp:class:`GDALDriver`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:131 +msgid "" +"The :cpp:class:`GDALDataset` also has support for executing a datasource " +"specific command, normally a form of SQL. This is accomplished via the " +":cpp:func:`GDALDataset::ExecuteSQL` method. While some datasources (such " +"as PostGIS and Oracle) pass the SQL through to an underlying database, " +"OGR also includes support for evaluating a subset of the SQL SELECT " +"statement against any datasource (see :ref:`ogr_sql_sqlite_dialect`.)" +msgstr "" + +#: ../../source/user/vector_data_model.rst:133 +msgid "" +"When using some drivers, the :cpp:class:`GDALDataset` also offers a " +"mechanism for to start, commit, and rollback transactions when " +"interacting with the underlying data store." +msgstr "" + +#: ../../source/user/vector_data_model.rst:136 +msgid "" +"A :cpp:class:`GDALDataset` may also be aware of relationships between " +"layers (e.g., a foreign key relationship between database tables). " +"Information about these relationships is stored in a " +":cpp:class:`GDALRelationshp`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:140 +msgid "" +"Earlier versions of GDAL represented vector datasets using the " +":cpp:class:`OGRDataSource` class. This class has been maintained for " +"backwards compatibility but is functionally equivalent to a " +":cpp:class:`GDALDataset` for vector data." +msgstr "" + +#: ../../source/user/vector_data_model.rst:143 +msgid "Drivers" +msgstr "" + +#: ../../source/user/vector_data_model.rst:145 +msgid "" +"A :cpp:class:`GDALDriver` object is instantiated for each file format " +"supported. The :cpp:class:`GDALDriver` objects are registered with the " +":cpp:class:`GDALDriverManager`, a singleton class that is normally used " +"to open new datasets." +msgstr "" + +#: ../../source/user/vector_data_model.rst:147 +msgid "" +"It is intended that a new :cpp:class:`GDALDriver` object is instantiated " +"and define function pointers for operations like Identify(), Open() for " +"each file format to be supported (along with a file format specific " +":cpp:class:`GDALDataset`, and :cpp:class:`OGRLayer` classes)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:149 +msgid "" +"On application startup registration functions are normally called for " +"each desired file format. These functions instantiate the appropriate " +":cpp:class:`GDALDriver` objects, and register them with the " +":cpp:class:`GDALDriverManager`. When a dataset is to be opened, the " +"driver manager will normally try each :cpp:class:`GDALDataset` in turn, " +"until one succeeds, returning a :cpp:class:`GDALDataset` object." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:5 +msgid "" +"GDAL Virtual File Systems (compressed, network hosted, etc...): /vsimem, " +"/vsizip, /vsitar, /vsicurl, ..." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:8 +msgid "Introduction" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:10 +msgid "" +"GDAL can access files located on \"standard\" file systems, i.e. in the /" +" hierarchy on Unix-like systems or in C:\\, D:\\, etc... drives on " +"Windows. But most GDAL raster and vector drivers use a GDAL-specific " +"abstraction to access files. This makes it possible to access less " +"standard types of files, such as in-memory files, compressed files (.zip," +" .gz, .tar, .tar.gz archives), encrypted files, standard input and output" +" (STDIN, STDOUT), files stored on network (either publicly accessible, or" +" in private buckets of commercial cloud storage services), etc." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:12 +msgid "" +"Each special file system has a prefix, and the general syntax to name a " +"file is /vsiPREFIX/..." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:21 +msgid "Chaining" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:23 +msgid "It is possible to chain multiple file system handlers." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:35 +msgid "" +"(Note is also OK to say /vsizip/vsicurl/... with a single slash. (But " +"when writing documentation please still use two.))" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:38 +msgid "Drivers supporting virtual file systems" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:40 +msgid "" +"Virtual file systems can only be used with GDAL or OGR drivers supporting" +" the \"large file API\", which is now the vast majority of file based " +"drivers. The full list of these formats can be obtained by looking at the" +" driver marked with 'v' when running either ``gdalinfo --formats`` or " +"``ogrinfo --formats``." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:42 +msgid "A notable exception is the HDF4 driver." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:47 +msgid "/vsizip/ (.zip archives)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:50 +msgid "Read capabilities" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:52 +msgid "" +"/vsizip/ is a file handler that allows reading ZIP archives on-the-fly " +"without decompressing them beforehand." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:54 +msgid "" +"To point to a file inside a zip file, the filename must be of the form " +":file:`/vsizip/path/to/the/file.zip/path/inside/the/zip/file`, where " +":file:`path/to/the/file.zip` is relative or absolute and " +":file:`path/inside/the/zip/file` is the relative path to the file inside " +"the archive." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:56 +msgid "" +"To use the .zip as a directory, you can use " +":file:`/vsizip/path/to/the/file.zip` or " +":file:`/vsizip/path/to/the/file.zip/subdir`. Directory listing is " +"available with :cpp:func:`VSIReadDir`. A :cpp:func:`VSIStatL` " +"(\"/vsizip/...\") call will return the uncompressed size of the file. " +"Directories inside the ZIP file can be distinguished from regular files " +"with the VSI_ISDIR(stat.st_mode) macro as for regular file systems. " +"Getting directory listing and file statistics are fast operations." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:58 +msgid "" +"Note: in the particular case where the .zip file contains a single file " +"located at its root, just mentioning :file:`/vsizip/path/to/the/file.zip`" +" will work." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:60 +msgid "The following configuration options are specific to the /zip/ handler:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:87 +msgid "" +".kmz, .ods and .xlsx extensions are also detected as valid extensions for" +" zip-compatible archives." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:89 +msgid "" +"Starting with GDAL 2.2, an alternate syntax is available so as to enable " +"chaining and not being dependent on .zip extension, e.g.: " +"``/vsizip/{/path/to/the/archive}/path/inside/the/zip/file``. Note that " +":file:`/path/to/the/archive` may also itself use this alternate syntax." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:92 +msgid "Write capabilities" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:94 +msgid "" +"Write capabilities are also available. They allow creating a new zip file" +" and adding new files to an already existing (or just created) zip file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:96 +msgid "Creation of a new zip file:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:106 +msgid "Addition of a new file to an existing zip:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:114 +msgid "" +"Starting with GDAL 2.4, the :config:`GDAL_NUM_THREADS` configuration " +"option can be set to an integer or ``ALL_CPUS`` to enable multi-threaded " +"compression of a single file. This is similar to the pigz utility in " +"independent mode. By default the input stream is split into 1 MB chunks " +"(the chunk size can be tuned with the " +":config:`CPL_VSIL_DEFLATE_CHUNK_SIZE` configuration option, with values " +"like \"x K\" or \"x M\"), and each chunk is independently compressed (and" +" terminated by a nine byte marker 0x00 0x00 0xFF 0xFF 0x00 0x00 0x00 0xFF" +" 0xFF, signaling a full flush of the stream and dictionary, enabling " +"potential independent decoding of each chunk). This slightly reduces the " +"compression rate, so very small chunk sizes should be avoided. Starting " +"with GDAL 3.7, this technique is reused to generate .zip files following " +":ref:`sozip_intro`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:117 +msgid "" +"Read and write operations cannot be interleaved. The new zip must be " +"closed before being re-opened in read mode." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:122 +msgid "SOZip (Seek-Optimized ZIP)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:124 +msgid "" +"GDAL (>= 3.7) has full read and write support for .zip files following " +"the `SOZip (Seek-Optimized ZIP) <https://sozip.org>`__ profile." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:127 +msgid "" +"The ``/vsizip/`` virtual file system uses the SOZip index to perform fast" +" random access within a compressed SOZip-enabled file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:130 +msgid "" +"The :ref:`vector.shapefile` and :ref:`vector.gpkg` drivers can directly " +"generate SOZip-enabled .shz/.shp.zip or .gpkg.zip files." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:133 +msgid "" +"The :cpp:func:`CPLAddFileInZip` C function, which can compress a file and" +" add it to an new or existing ZIP file, enables the SOZip optimization " +"when relevant (ie when a file to be compressed is larger than 1 MB). " +"SOZip optimization can be forced by setting the " +":config:`CPL_SOZIP_ENABLED` configuration option to YES. Or totally " +"disabled by setting it to NO." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:139 +msgid "" +"The :cpp:func:`VSIGetFileMetadata` method can be called on a filename of " +"the form :file:`/vsizip/path/to/the/file.zip/path/inside/the/zip/file` " +"and with domain = \"ZIP\" to get information if a SOZip index is " +"available for that file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:143 +msgid "" +"The :ref:`sozip` new command line utility can be used to create a seek-" +"optimized ZIP file, to append files to an existing ZIP file, list the " +"contents of a ZIP file and display the SOZip optimization status or " +"validate a SOZip file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:151 +msgid "/vsigzip/ (gzipped file)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:153 +msgid "" +"/vsigzip/ is a file handler that allows on-the-fly reading of GZip (.gz) " +"files without decompressing them in advance." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:155 +msgid "" +"To view a gzipped file as uncompressed by GDAL, you must use the " +":file:`/vsigzip/path/to/the/file.gz` syntax, where " +":file:`path/to/the/file.gz` is relative or absolute." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:157 +msgid "The following configuration options are specific to the /vsigzip/ handler:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:176 +msgid "" +":cpp:func:`VSIStatL` will return the uncompressed file size, but this is " +"potentially a slow operation on large files, since it requires " +"uncompressing the whole file. Seeking to the end of the file, or at " +"random locations, is similarly slow. To speed up that process, " +"\"snapshots\" are internally created in memory so as to be able being " +"able to seek to part of the files already decompressed in a faster way. " +"This mechanism of snapshots also apply to /vsizip/ files." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:178 +msgid "" +"Write capabilities are also available, but read and write operations " +"cannot be interleaved." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:180 +msgid "" +"Starting with GDAL 2.4, the :config:`GDAL_NUM_THREADS` configuration " +"option can be set to an integer or ``ALL_CPUS`` to enable multi-threaded " +"compression of a single file. This is similar to the pigz utility in " +"independent mode. By default the input stream is split into 1 MB chunks " +"(the chunk size can be tuned with the " +":config:`CPL_VSIL_DEFLATE_CHUNK_SIZE` configuration option, with values " +"like \"x K\" or \"x M\"), and each chunk is independently compressed (and" +" terminated by a nine byte marker 0x00 0x00 0xFF 0xFF 0x00 0x00 0x00 0xFF" +" 0xFF, signaling a full flush of the stream and dictionary, enabling " +"potential independent decoding of each chunk). This slightly reduces the " +"compression rate, so very small chunk sizes should be avoided." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:185 +msgid "/vsitar/ (.tar, .tgz archives)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:187 +msgid "" +"/vsitar/ is a file handler that allows on-the-fly reading in regular " +"uncompressed .tar or compressed .tgz or .tar.gz archives, without " +"decompressing them in advance." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:189 +msgid "" +"To point to a file inside a .tar, .tgz .tar.gz file, the filename must be" +" of the form " +":file:`/vsitar/path/to/the/file.tar/path/inside/the/tar/file`, where " +":file:`path/to/the/file.tar` is relative or absolute and " +":file:`path/inside/the/tar/file` is the relative path to the file inside " +"the archive." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:191 +msgid "" +"To use the .tar as a directory, you can use " +":file:`/vsizip/path/to/the/file.tar` or " +":file:`/vsitar/path/to/the/file.tar/subdir`. Directory listing is " +"available with :cpp:func:`VSIReadDir`. A :cpp:func:`VSIStatL` " +"(\"/vsitar/...\") call will return the uncompressed size of the file. " +"Directories inside the TAR file can be distinguished from regular files " +"with the VSI_ISDIR(stat.st_mode) macro as for regular file systems. " +"Getting directory listing and file statistics are fast operations." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:193 +msgid "" +"Note: in the particular case where the .tar file contains a single file " +"located at its root, just mentioning :file:`/vsitar/path/to/the/file.tar`" +" will work." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:203 +msgid "" +"Starting with GDAL 2.2, an alternate syntax is available so as to enable " +"chaining and not being dependent on .tar extension, e.g.: " +":file:`/vsitar/{/path/to/the/archive}/path/inside/the/tar/file`. Note " +"that :file:`/path/to/the/archive` may also itself use this alternate " +"syntax." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:208 +msgid "/vsi7z/ (.7z archives)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:212 +msgid "" +"/vsi7z/ is a file handler that allows reading `7z " +"<https://en.wikipedia.org/wiki/7z>`__ archives on-the-fly without " +"decompressing them beforehand. This file system is read-only. Directory " +"listing and :cpp:func:`VSIStatL` are available, similarly to above " +"mentioned file systems." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:217 +#: ../../source/user/virtual_file_systems.rst:249 +msgid "" +"It requires GDAL to be built against `libarchive " +"<https://libarchive.org/>`__ (and libarchive having LZMA support to be of" +" practical use)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:220 +msgid "" +"To point to a file inside a 7z file, the filename must be of the form " +":file:`/vsi7z/path/to/the/file.7z/path/inside/the/7z/file`, where " +":file:`path/to/the/file.7z` is relative or absolute and " +":file:`path/inside/the/7z/file` is the relative path to the file inside " +"the archive.`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:225 +msgid "" +"Default extensions recognized by this virtual file system are: ``7z``, " +"``lpk`` (Esri ArcGIS Layer Package), ``lpkx``, ``mpk`` (Esri ArcGIS Map " +"Package), ``mpkx`` and ``ppkx`` (Esri ArcGIS Pro Project Package)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:229 +msgid "" +"An alternate syntax is available so as to enable chaining and not being " +"dependent on those extensions, e.g.: " +":file:`/vsi7z/{/path/to/the/archive}/path/inside/the/archive`. Note that " +":file:`/path/to/the/archive` may also itself use this alternate syntax." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:233 +#: ../../source/user/virtual_file_systems.rst:263 +msgid "" +"Note that random seeking within a large compressed file will be " +"inefficient when backward seeking is needed (decompression will be " +"restarted from the start of the file). Performance will be the best in " +"sequential reading." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:240 +msgid "/vsirar/ (.rar archives)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:244 +msgid "" +"/vsirar/ is a file handler that allows reading `RAR " +"<https://en.wikipedia.org/wiki/RAR_(file_format)>`__ archives on-the-fly " +"without decompressing them beforehand. This file system is read-only. " +"Directory listing and :cpp:func:`VSIStatL` are available, similarly to " +"above mentioned file systems." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:252 +msgid "" +"To point to a file inside a RAR file, the filename must be of the form " +":file:`/vsirar/path/to/the/file.rar/path/inside/the/rar/file`, where " +":file:`path/to/the/file.rar` is relative or absolute and " +":file:`path/inside/the/rar/file` is the relative path to the file inside " +"the archive.`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:257 +msgid "The default extension recognized by this virtual file system is: ``rar``" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:259 +msgid "" +"An alternate syntax is available so as to enable chaining and not being " +"dependent on those extensions, e.g.: " +":file:`/vsirar/{/path/to/the/archive}/path/inside/the/archive`. Note that" +" :file:`/path/to/the/archive` may also itself use this alternate syntax." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:270 +msgid "Network based file systems" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:272 +msgid "" +"A generic :ref:`/vsicurl/ <vsicurl>` file system handler exists for " +"online resources that do not require particular signed authentication " +"schemes. It is specialized into sub-filesystems for commercial cloud " +"storage services, such as :ref:`/vsis3/ <vsis3>`, :ref:`/vsigs/ " +"<vsigs>`, :ref:`/vsiaz/ <vsiaz>`, :ref:`/vsioss/ <vsioss>` or " +":ref:`/vsiswift/ <vsiswift>`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:274 +msgid "" +"When reading of entire files in a streaming way is possible, prefer using" +" the :ref:`/vsicurl_streaming/ <vsicurl_streaming>`, and its variants for" +" the above cloud storage services, for more efficiency." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:277 +msgid "How to set credentials ?" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:279 +msgid "" +"Cloud storage services require setting credentials. For some of them, " +"they can be provided through configuration files (~/.aws/config, ~/.boto," +" ..) or through environment variables / configuration options." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:283 +msgid "" +"Starting with GDAL 3.6, :cpp:func:`VSISetPathSpecificOption` can be used " +"to set configuration options with a granularity at the level of a file " +"path, which makes it easier if using the same virtual file system but " +"with different credentials (e.g. different credentials for bucket " +"\"/vsis3/foo\" and \"/vsis3/bar\")" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:288 +msgid "" +"Starting with GDAL 3.5, credentials (or path specific options) can be " +"specified in a :ref:`GDAL configuration file <gdal_configuration_file>`, " +"either in a specific one explicitly loaded with " +":cpp:func:`CPLLoadConfigOptionsFromFile`, or one of the default " +"automatically loaded by " +":cpp:func:`CPLLoadConfigOptionsFromPredefinedFiles`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:293 +msgid "" +"They should be put under a ``[credentials]`` section, and for each path " +"prefix, under a relative subsection whose name starts with ``[.`` (e.g. " +"``[.some_arbitrary_name]``), and whose first key is ``path``. ` .. code-" +"block::" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:311 +msgid "Network/cloud-friendliness and file formats" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:313 +msgid "" +"While most GDAL raster and vector file systems can be accessed in a " +"remote way with /vsicurl/ and other derived virtual file systems, " +"performance is highly dependent on the format, and even for a given " +"format on the special data arrangement. Performance also depends on the " +"particular access pattern made to the file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:319 +msgid "" +"For interactive visualisation of raster files, the file should ideally " +"have the following characteristics:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:322 +msgid "it should be tiled in generally square-shaped tiles." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:323 +msgid "it should have an index of the tile location within the file" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:324 +msgid "it should have overviews/pyramids" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:327 +msgid "TIFF/GeoTIFF" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:329 +msgid "" +"Cloud-optimized GeoTIFF files as generated by the :ref:`raster.cog` " +"driver are suitable for network access. More generally tiled GeoTIFF " +"files with overviews are." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:336 +msgid "" +"JPEG2000 is generally not suitable for network access, unless using a " +"layout carefully designed for that purpose, and when using a JPEG200 " +"library that is heavily optimized." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:340 +msgid "" +"JPEG2000 files can come in many flavors : single-tiled vs tiled, with " +"different progression order (this is of particular importance for single-" +"tiled access), and with optional markers" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:344 +msgid "" +"The OpenJPEG library (usable through the :ref:`raster.jp2openjpeg` " +"driver), at the time of writing, needs to ingest each tile-part that " +"participates to the area of interest of the pixel query in a whole (and " +"thus for a single-tiled file, to ingest the whole file). It also does not" +" make use of the potentially present TLM (Tile-Part length) marker, which" +" is the equivalent of a tile index, nor PLT (Packed Length, tile-part " +"header), which is an index of packets within a tile. The Kakadu library " +"(usable through the :ref:`raster.jp2kak` driver), can use those markers " +"to limit the number of bytes to ingest (but for single-tiled raster, " +"performance might still suffer.)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:354 +msgid "" +"The `dump_jp2.py " +"<https://raw.githubusercontent.com/OSGeo/gdal/master/swig/python/gdal-" +"utils/osgeo_utils/samples/dump_jp2.py>`__ Python script can be used to " +"check the characteristics of a given JPEG200 file. Fields of interest to " +"examine in the output are:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:358 +msgid "" +"the tile size (given by the ``XTsiz`` and ``YTsiz`` fields in the ``SIZ``" +" marker)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:359 +msgid "the presence of ``TLM`` markers" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:360 +msgid "the presence of ``PLT`` markers" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:365 +msgid "/vsicurl/ (http/https/ftp files: random access)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:367 +msgid "" +"/vsicurl/ is a file system handler that allows on-the-fly random reading " +"of files available through HTTP/FTP web protocols, without prior download" +" of the entire file. It requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:369 +msgid "" +"Recognized filenames are of the form " +":file:`/vsicurl/http[s]://path/to/remote/resource` or " +":file:`/vsicurl/ftp://path/to/remote/resource`, where " +":file:`path/to/remote/resource` is the URL of a remote resource." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:371 +msgid "Example using :program:`ogrinfo` to read a shapefile on the internet:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:377 +msgid "" +"Starting with GDAL 2.3, options can be passed in the filename with the " +"following syntax: ``/vsicurl?[option_i=val_i&]*url=http://...`` where " +"each option name and value (including the value of \"url\") is URL-" +"encoded. Currently supported options are:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:379 +msgid "" +"use_head=yes/no: whether the HTTP HEAD request can be emitted. Default to" +" YES. Setting this option overrides the behavior of the " +":config:`CPL_VSIL_CURL_USE_HEAD` configuration option." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:380 +msgid "" +"max_retry=number: default to 0. Setting this option overrides the " +"behavior of the :config:`GDAL_HTTP_MAX_RETRY` configuration option." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:381 +msgid "" +"retry_delay=number_in_seconds: default to 30. Setting this option " +"overrides the behavior of the :config:`GDAL_HTTP_RETRY_DELAY` " +"configuration option." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:382 +msgid "" +"retry_codes=``ALL`` or comma-separated list of HTTP error codes. Setting " +"this option overrides the behavior of the :config:`GDAL_HTTP_RETRY_CODES`" +" configuration option. (GDAL >= 3.10)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:383 +msgid "" +"list_dir=yes/no: whether an attempt to read the file list of the " +"directory where the file is located should be done. Default to YES." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:384 +msgid "useragent=value: HTTP UserAgent header" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:385 +msgid "referer=value: HTTP Referer header" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:386 +msgid "cookie=value: HTTP Cookie header" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:387 +msgid "" +"header_file=value: Filename that contains one or several \"Header: " +"Value\" lines" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:388 +msgid "unsafessl=yes/no" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:389 +msgid "low_speed_time=value" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:390 +msgid "low_speed_limit=value" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:391 +msgid "proxy=value" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:392 +msgid "proxyauth=value" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:393 +msgid "proxyuserpwd=value" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:394 +msgid "" +"pc_url_signing=yes/no: whether to use the URL signing mechanism of " +"Microsoft Planetary Computer " +"(https://planetarycomputer.microsoft.com/docs/concepts/sas/). (GDAL >= " +"3.5.2). Note that starting with GDAL 3.9, this may also be set with the " +"path-specific option ( cf :cpp:func:`VSISetPathSpecificOption`) " +"``VSICURL_PC_URL_SIGNING`` set to ``YES``." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:395 +msgid "" +"pc_collection=name: name of the collection of the dataset for Planetary " +"Computer URL signing. Only used when pc_url_signing=yes. (GDAL >= 3.5.2)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:397 +msgid "" +"Partial downloads (requires the HTTP server to support random reading) " +"are done with a 16 KB granularity by default. Starting with GDAL 2.3, the" +" chunk size can be configured with the :config:`CPL_VSIL_CURL_CHUNK_SIZE`" +" configuration option, with a value in bytes. If the driver detects " +"sequential reading, it will progressively increase the chunk size up to " +"128 times :config:`CPL_VSIL_CURL_CHUNK_SIZE` (so 2 MB by default) to " +"improve download performance." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:399 +msgid "" +"In addition, a global least-recently-used cache of 16 MB shared among all" +" downloaded content is used, and content in it may be reused after a file" +" handle has been closed and reopen, during the life-time of the process " +"or until :cpp:func:`VSICurlClearCache` is called. Starting with GDAL 2.3," +" the size of this global LRU cache can be modified by setting the " +"configuration option :config:`CPL_VSIL_CURL_CACHE_SIZE` (in bytes)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:401 +msgid "" +"When increasing the value of :config:`CPL_VSIL_CURL_CHUNK_SIZE` to " +"optimize sequential reading, it is recommended to increase " +":config:`CPL_VSIL_CURL_CACHE_SIZE` as well to 128 times the value of " +":config:`CPL_VSIL_CURL_CHUNK_SIZE`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:403 +msgid "" +"Starting with GDAL 2.3, the :config:`GDAL_INGESTED_BYTES_AT_OPEN` " +"configuration option can be set to impose the number of bytes read in one" +" GET call at file opening (can help performance to read Cloud optimized " +"geotiff with a large header)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:405 +#: ../../source/user/virtual_file_systems.rst:455 +msgid "" +"The :config:`GDAL_HTTP_PROXY` (for both HTTP and HTTPS protocols), " +":config:`GDAL_HTTPS_PROXY` (for HTTPS protocol only), " +":config:`GDAL_HTTP_PROXYUSERPWD` and :config:`GDAL_PROXY_AUTH` " +"configuration options can be used to define a proxy server. The syntax to" +" use is the one of Curl ``CURLOPT_PROXY``, ``CURLOPT_PROXYUSERPWD`` and " +"``CURLOPT_PROXYAUTH`` options." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:407 +#: ../../source/user/virtual_file_systems.rst:457 +msgid "" +"Starting with GDAL 2.1.3, the :config:`CURL_CA_BUNDLE` or " +":config:`SSL_CERT_FILE` configuration options can be used to set the path" +" to the Certification Authority (CA) bundle file (if not specified, curl " +"will use a file in a system location)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:409 +msgid "" +"Starting with GDAL 2.3, additional HTTP headers can be sent by setting " +"the :config:`GDAL_HTTP_HEADER_FILE` configuration option to point to a " +"filename of a text file with \"key: value\" HTTP headers." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:411 +msgid "" +"As an alternative, starting with GDAL 3.6, the " +":config:`GDAL_HTTP_HEADERS` configuration option can also be used to " +"specify headers. :config:`CPL_CURL_VERBOSE=YES` allows one to see them " +"and more, when combined with ``--debug``." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:415 +msgid "" +"Starting with GDAL 2.3, the :config:`GDAL_HTTP_MAX_RETRY` (number of " +"attempts) and :config:`GDAL_HTTP_RETRY_DELAY` (in seconds) configuration " +"option can be set, so that request retries are done in case of HTTP " +"errors 429, 502, 503 or 504." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:417 +msgid "" +"Starting with GDAL 3.6, the following configuration options control the " +"TCP keep-alive functionality (cf https://daniel.haxx.se/blog/2020/02/10" +"/curl-ootw-keepalive-time/ for a detailed explanation):" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:419 +msgid "" +":config:`GDAL_HTTP_TCP_KEEPALIVE` = YES/NO. whether to enable TCP keep-" +"alive. Defaults to NO" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:420 +msgid "" +":config:`GDAL_HTTP_TCP_KEEPIDLE` = integer, in seconds. Keep-alive idle " +"time. Defaults to 60. Only taken into account if " +"GDAL_HTTP_TCP_KEEPALIVE=YES." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:421 +msgid "" +":config:`GDAL_HTTP_TCP_KEEPINTVL` = integer, in seconds. Interval time " +"between keep-alive probes. Defaults to 60. Only taken into account if " +"GDAL_HTTP_TCP_KEEPALIVE=YES." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:423 +msgid "" +"Starting with GDAL 3.7, the following configuration options control " +"support for SSL client certificates:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:425 +msgid "" +":config:`GDAL_HTTP_SSLCERT` = filename. Filename of the the SSL client " +"certificate. Cf https://curl.se/libcurl/c/CURLOPT_SSLCERT.html" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:426 +msgid "" +":config:`GDAL_HTTP_SSLCERTTYPE` = string. Format of the SSL certificate: " +"\"PEM\" or \"DER\". Cf https://curl.se/libcurl/c/CURLOPT_SSLCERTTYPE.html" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:427 +msgid "" +":config:`GDAL_HTTP_SSLKEY` = filename. Private key file for TLS and SSL " +"client certificate. Cf https://curl.se/libcurl/c/CURLOPT_SSLKEY.html" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:428 +msgid "" +":config:`GDAL_HTTP_KEYPASSWD` = string. Passphrase to private key. Cf " +"https://curl.se/libcurl/c/CURLOPT_KEYPASSWD.html" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:430 +msgid "" +"More generally options of :cpp:func:`CPLHTTPFetch` available through " +"configuration options are available. Starting with GDAL 3.7, the above " +"configuration options can also be specified as path-specific options with" +" :cpp:func:`VSISetPathSpecificOption`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:434 +msgid "" +"The file can be cached in RAM by setting the configuration option " +":config:`VSI_CACHE` to ``TRUE``. The cache size defaults to 25 MB, but " +"can be modified by setting the configuration option " +":config:`VSI_CACHE_SIZE` (in bytes). Content in that cache is discarded " +"when the file handle is closed." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:436 +msgid "" +"Starting with GDAL 2.3, the :config:`CPL_VSIL_CURL_NON_CACHED` " +"configuration option can be set to values like " +":file:`/vsicurl/http://example.com/foo.tif:/vsicurl/http://example.com/some_directory`," +" so that at file handle closing, all cached content related to the " +"mentioned file(s) is no longer cached. This can help when dealing with " +"resources that can be modified during execution of GDAL related code. " +"Alternatively, :cpp:func:`VSICurlClearCache` can be used." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:438 +msgid "" +"Starting with GDAL 2.1, ``/vsicurl/`` will try to query directly " +"redirected URLs to Amazon S3 signed URLs during their validity period, so" +" as to minimize round-trips. This behavior can be disabled by setting the" +" configuration option :config:`CPL_VSIL_CURL_USE_S3_REDIRECT` to ``NO``." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:440 +#: ../../source/user/virtual_file_systems.rst:461 +msgid "" +":cpp:func:`VSIStatL` will return the size in st_size member and file " +"nature- file or directory - in st_mode member (the later only reliable " +"with FTP resources for now)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:442 +msgid "" +":cpp:func:`VSIReadDir` should be able to parse the HTML directory listing" +" returned by the most popular web servers, such as Apache and Microsoft " +"IIS." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:447 +msgid "/vsicurl_streaming/ (http/https/ftp files: streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:449 +msgid "" +"/vsicurl_streaming/ is a file system handler that allows on-the-fly " +"sequential reading of files streamed through HTTP/FTP web protocols, " +"without prior download of the entire file. It requires GDAL to be built " +"against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:451 +msgid "" +"Although this file handler is able seek to random offsets in the file, " +"this will not be efficient. If you need efficient random access and that " +"the server supports range downloading, you should use the :ref:`/vsicurl/" +" <vsicurl>` file system handler instead." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:453 +msgid "" +"Recognized filenames are of the form " +":file:`/vsicurl_streaming/http[s]://path/to/remote/resource` or " +":file:`/vsicurl_streaming/ftp://path/to/remote/resource`, where " +":file:`path/to/remote/resource` is the URL of a remote resource." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:459 +msgid "" +"The file can be cached in RAM by setting the configuration option " +":config:`VSI_CACHE` to ``TRUE``. The cache size defaults to 25 MB, but " +"can be modified by setting the configuration option " +":config:`VSI_CACHE_SIZE` (in bytes)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:466 +msgid "/vsis3/ (AWS S3 files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:468 +msgid "" +"/vsis3/ is a file system handler that allows on-the-fly random reading of" +" (primarily non-public) files available in AWS S3 buckets, without prior " +"download of the entire file. It requires GDAL to be built against " +"libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:470 +msgid "" +"It also allows sequential writing of files. No seeks or read operations " +"are then allowed, so in particular direct writing of GeoTIFF files with " +"the GTiff driver is not supported, unless, if, starting with GDAL 3.2, " +"the :config:`CPL_VSIL_USE_TEMP_FILE_FOR_RANDOM_WRITE` configuration " +"option is set to ``YES``, in which case random-write access is possible " +"(involves the creation of a temporary local file, whose location is " +"controlled by the :config:`CPL_TMPDIR` configuration option). Deletion of" +" files with :cpp:func:`VSIUnlink` is also supported. Starting with GDAL " +"2.3, creation of directories with :cpp:func:`VSIMkdir` and deletion of " +"(empty) directories with :cpp:func:`VSIRmdir` are also possible." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:474 +msgid "" +"Recognized filenames are of the form :file:`/vsis3/bucket/key`, where " +"``bucket`` is the name of the S3 bucket and ``key`` is the S3 object " +"\"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:476 +#: ../../source/user/virtual_file_systems.rst:690 +#: ../../source/user/virtual_file_systems.rst:804 +#: ../../source/user/virtual_file_systems.rst:935 +#: ../../source/user/virtual_file_systems.rst:991 +#: ../../source/user/virtual_file_systems.rst:1119 +msgid "The generalities of :ref:`/vsicurl/ <vsicurl>` apply." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:478 +msgid "The following configuration options are specific to the /vsis3/ handler:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:533 +msgid "" +"Path to file with identity token for use for authentication via the " +"`AssumeRoleWithWebIdentity API " +"<https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithWebIdentity.html>`_." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:609 +#: ../../source/user/virtual_file_systems.rst:758 +#: ../../source/user/virtual_file_systems.rst:861 +msgid "" +"Several authentication methods are possible, and are attempted in the " +"following order:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:611 +msgid "" +"If :config:`AWS_NO_SIGN_REQUEST=YES` configuration option is set, request" +" signing is disabled. This option might be used for buckets with public " +"access rights. Available since GDAL 2.3" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:612 +msgid "" +"The :config:`AWS_SECRET_ACCESS_KEY` and :config:`AWS_ACCESS_KEY_ID` " +"configuration options can be set. The :config:`AWS_SESSION_TOKEN` " +"configuration option must be set when temporary credentials are used." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:613 +msgid "" +"Starting with GDAL 2.3, alternate ways of providing credentials similar " +"to what the \"aws\" command line utility or Boto3 support can be used. If" +" the above mentioned environment variables are not provided, the " +"``~/.aws/credentials`` or ``%UserProfile%/.aws/credentials`` file will be" +" read (or the file pointed by :config:`CPL_AWS_CREDENTIALS_FILE`). The " +"profile may be specified with the :config:`AWS_DEFAULT_PROFILE` " +"environment variable, or starting with GDAL 3.2 with the " +":config:`AWS_PROFILE` environment variable (the default profile is " +"\"default\")." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:614 +msgid "" +"The ``~/.aws/config`` or ``%UserProfile%/.aws/config`` file may also be " +"used (or the file pointer by :config:`AWS_CONFIG_FILE`) to retrieve " +"credentials and the AWS region." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:615 +msgid "" +"Starting with GDAL 3.6, if :config:`AWS_ROLE_ARN` and " +":config:`AWS_WEB_IDENTITY_TOKEN_FILE` are defined we will rely on " +"credentials mechanism for web identity token based AWS STS action " +"AssumeRoleWithWebIdentity (See.: " +"https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-" +"accounts.html)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:616 +msgid "" +"If none of the above method succeeds, instance profile credentials will " +"be retrieved when GDAL is used on EC2 instances (cf :ref:`vsis3_imds`)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:618 +msgid "" +"On writing, the file is uploaded using the S3 multipart upload API. The " +"size of chunks is set to 50 MB by default, allowing creating files up to " +"500 GB (10000 parts of 50 MB each). If larger files are needed, then " +"increase the value of the :config:`VSIS3_CHUNK_SIZE` config option to a " +"larger value (expressed in MB). In case the process is killed and the " +"file not properly closed, the multipart upload will remain open, causing " +"Amazon to charge you for the parts storage. You'll have to abort yourself" +" with other means such \"ghost\" uploads (e.g. with the s3cmd utility) " +"For files smaller than the chunk size, a simple PUT request is used " +"instead of the multipart upload API." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:620 +#: ../../source/user/virtual_file_systems.rst:877 +msgid "" +"Since GDAL 3.1, the :cpp:func:`VSIRename` operation is supported (first " +"doing a copy of the original file and then deleting it)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:622 +msgid "" +"Since GDAL 3.1, the :cpp:func:`VSIRmdirRecursive` operation is supported " +"(using batch deletion method). The " +":config:`CPL_VSIS3_USE_BASE_RMDIR_RECURSIVE` configuration option can be " +"set to YES if using a S3-like API that doesn't support batch deletion " +"(GDAL >= 3.2). Starting with GDAL 3.6, this can be set as a path-specific" +" option in the :ref:`GDAL configuration file <gdal_configuration_file>`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:624 +msgid "" +"The :config:`CPL_VSIS3_CREATE_DIR_OBJECT` configuration option can be set" +" to NO to prevent the :cpp:func:`VSIMkdir` operation from creating an " +"empty object with the name of the directory terminated with a slash " +"directory. By default GDAL creates such object, so that empty directories" +" can be modeled, but this may cause compatibility problems with " +"applications that do not expect such empty objects." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:627 +msgid "" +"Starting with GDAL 3.5, profiles that use IAM role assumption (see " +"https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-role.html)" +" are handled. The ``role_arn`` and ``source_profile`` keywords are " +"required in such profiles. The optional ``external_id``, ``mfa_serial`` " +"and ``role_session_name`` can be specified. ``credential_source`` is not " +"supported currently." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:632 +msgid "/vsis3/ and AWS Instance Metadata Service (IMDS)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:634 +msgid "" +"On EC2 instances, GDAL will try to use the `IMDSv2 " +"<https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-" +"instance-metadata-service.html>`__ protocol in priority to get the " +"authentication tokens for AWS S3, and fallback to IMDSv1 in case of " +"failure. Note however that on recent Amazon Linux instances, IMDSv1 is no" +" longer accessible, and thus IMDSv2 must be correctly configured (and " +"even if IMDSv1 is available, mis-configured IMDSv2 will cause delays in " +"the authentication step)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:636 +msgid "" +"There are known issues when running inside a Docker instance in a EC2 " +"instance that require extra configuration of the instance. For example, " +"you need to `increase the hop limit to 2 " +"<https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-" +"retrieval.html#imds-considerations>`__" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:638 +msgid "There are several ways to do this. One way is to run this command: ::" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:646 +msgid "" +"Another is to set the HttpPutResponseHopLimit metadata on an " +"AutoScalingGroup LaunchTemplate: - " +"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_InstanceMetadataOptionsRequest.html" +" - https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-" +"properties-ec2-launchtemplate-metadataoptions.html" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:650 +msgid "" +"Another possibility is to start the Docker container with host networking" +" (``--network=host``), although this breaks isolation of containers by " +"exposing all ports of the host to the container and has thus `security " +"implications <https://stackoverflow.com/a/57051970/40785>`__." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:653 +msgid "Configuring /vsis3/ with Minio" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:655 +msgid "" +"The following configuration options can be set to access a `Minio Docker " +"image <https://min.io/docs/minio/container/index.html>`__" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:658 +msgid "AWS_VIRTUAL_HOSTING=FALSE" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:659 +msgid "AWS_HTTPS=NO" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:660 +msgid "AWS_S3_ENDPOINT=\"localhost:9000\"" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:661 +msgid "AWS_REGION=\"us-east-1\"" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:662 +msgid "AWS_SECRET_ACCESS_KEY=\"your_secret_access_key\"" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:663 +msgid "AWS_ACCESS_KEY_ID=\"your_access_key\"" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:668 +msgid "/vsis3_streaming/ (AWS S3 files: streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:670 +msgid "" +"/vsis3_streaming/ is a file system handler that allows on-the-fly " +"sequential reading of (primarily non-public) files available in AWS S3 " +"buckets, without prior download of the entire file. It requires GDAL to " +"be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:672 +msgid "" +"Recognized filenames are of the form :file:`/vsis3_streaming/bucket/key` " +"where ``bucket`` is the name of the S3 bucket and ``key`` is the S3 " +"object \"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:674 +msgid "" +"Authentication options, and read-only features, are identical to " +":ref:`/vsis3/ <vsis3>`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:681 +msgid "/vsigs/ (Google Cloud Storage files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:683 +msgid "" +"/vsigs/ is a file system handler that allows on-the-fly random reading of" +" (primarily non-public) files available in Google Cloud Storage buckets, " +"without prior download of the entire file. It requires GDAL to be built " +"against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:685 +msgid "" +"Starting with GDAL 2.3, it also allows sequential writing of files. No " +"seeks or read operations are then allowed, so in particular direct " +"writing of GeoTIFF files with the GTiff driver is not supported, unless, " +"if, starting with GDAL 3.2, the " +":config:`CPL_VSIL_USE_TEMP_FILE_FOR_RANDOM_WRITE` configuration option is" +" set to ``YES``, in which case random-write access is possible (involves " +"the creation of a temporary local file, whose location is controlled by " +"the :config:`CPL_TMPDIR` configuration option). Deletion of files with " +":cpp:func:`VSIUnlink`, creation of directories with :cpp:func:`VSIMkdir` " +"and deletion of (empty) directories with :cpp:func:`VSIRmdir` are also " +"possible." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:688 +msgid "" +"Recognized filenames are of the form :file:`/vsigs/bucket/key` where " +"``bucket`` is the name of the bucket and ``key`` is the object \"key\", " +"i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:692 +msgid "The following configuration options are specific to the /vsigs/ handler:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:760 +msgid "" +"If :config:`GS_NO_SIGN_REQUEST=YES` configuration option is set, request " +"signing is disabled. This option might be used for buckets with public " +"access rights. Available since GDAL 3.4" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:761 +msgid "" +"The :config:`GS_SECRET_ACCESS_KEY` and :config:`GS_ACCESS_KEY_ID` " +"configuration options can be set for AWS-style authentication" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:762 +msgid "" +"The :config:`GDAL_HTTP_HEADER_FILE` configuration option to point to a " +"filename of a text file with \"key: value\" headers. Typically, it must " +"contain a \"Authorization: Bearer XXXXXXXXX\" line." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:763 +msgid "" +"(GDAL >= 3.7) The :config:`GDAL_HTTP_HEADERS` configuration option can " +"also be set. It must contain at least a line starting with " +"\"Authorization:\" to be used as an authentication method." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:764 +msgid "" +"(GDAL >= 2.3) The :config:`GS_OAUTH2_REFRESH_TOKEN` configuration option " +"can be set to use OAuth2 client authentication. See " +"http://code.google.com/apis/accounts/docs/OAuth2.html This refresh token " +"can be obtained with the ``gdal_auth.py -s storage`` or ``gdal_auth.py -s" +" storage-rw`` script Note: instead of using the default GDAL application " +"credentials, you may define the :config:`GS_OAUTH2_CLIENT_ID` and " +":config:`GS_OAUTH2_CLIENT_SECRET` configuration options (need to be " +"defined both for gdal_auth.py and later execution of /vsigs)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:765 +msgid "" +"(GDAL >= 2.3) The :config:`GOOGLE_APPLICATION_CREDENTIALS` configuration " +"option can be set to point to a JSON file containing OAuth2 service " +"account credentials (``type: service_account``), in particular a private " +"key and a client email. See " +"https://developers.google.com/identity/protocols/OAuth2ServiceAccount for" +" more details on this authentication method. The bucket must grant the " +"\"Storage Legacy Bucket Owner\" or \"Storage Legacy Bucket Reader\" " +"permissions to the service account. The :config:`GS_OAUTH2_SCOPE` " +"configuration option can be set to change the default permission scope " +"from \"https://www.googleapis.com/auth/devstorage.read_write\" to " +"\"https://www.googleapis.com/auth/devstorage.read_only\" if needed." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:766 +msgid "" +"(GDAL >= 3.4.2) The :config:`GOOGLE_APPLICATION_CREDENTIALS` " +"configuration option can be set to point to a JSON file containing OAuth2" +" user credentials (``type: authorized_user``)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:767 +msgid "" +"(GDAL >= 2.3) Variant of the previous method. The " +":config:`GS_OAUTH2_PRIVATE_KEY` (or :config:`GS_OAUTH2_PRIVATE_KEY_FILE` " +"and :config:`GS_OAUTH2_CLIENT_EMAIL` can be set to use OAuth2 service " +"account authentication. See " +"https://developers.google.com/identity/protocols/OAuth2ServiceAccount for" +" more details on this authentication method. The " +":config:`GS_OAUTH2_PRIVATE_KEY` configuration option must contain the " +"private key as a inline string, starting with ``-----BEGIN PRIVATE " +"KEY-----``. Alternatively the :config:`GS_OAUTH2_PRIVATE_KEY_FILE` " +"configuration option can be set to indicate a filename that contains such" +" a private key. The bucket must grant the \"Storage Legacy Bucket Owner\"" +" or \"Storage Legacy Bucket Reader\" permissions to the service account. " +"The :config:`GS_OAUTH2_SCOPE` configuration option can be set to change " +"the default permission scope from " +"\"https://www.googleapis.com/auth/devstorage.read_write\" to " +"\"https://www.googleapis.com/auth/devstorage.read_only\" if needed." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:768 +msgid "" +"(GDAL >= 2.3) An alternate way of providing credentials similar to what " +"the \"gsutil\" command line utility or Boto3 support can be used. If the " +"above mentioned environment variables are not provided, the " +":file:`~/.boto` or :file:`UserProfile%/.boto` file will be read (or the " +"file pointed by :config:`CPL_GS_CREDENTIALS_FILE`) for the " +"gs_secret_access_key and gs_access_key_id entries for AWS style " +"authentication. If not found, it will look for the " +"gs_oauth2_refresh_token (and optionally client_id and client_secret) " +"entry for OAuth2 client authentication." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:769 +msgid "" +"(GDAL >= 2.3) Finally if none of the above method succeeds, the code will" +" check if the current machine is a Google Compute Engine instance, and if" +" so will use the permissions associated to it (using the default service " +"account associated with the VM). To force a machine to be detected as a " +"GCE instance (for example for code running in a container with no access " +"to the boot logs), you can set :config:`CPL_MACHINE_IS_GCE` to ``YES``." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:771 +msgid "" +"Since GDAL 3.1, the Rename() operation is supported (first doing a copy " +"of the original file and then deleting it)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:778 +msgid "/vsigs_streaming/ (Google Cloud Storage files: streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:780 +msgid "" +"/vsigs_streaming/ is a file system handler that allows on-the-fly " +"sequential reading of files (primarily non-public) files available in " +"Google Cloud Storage buckets, without prior download of the entire file. " +"It requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:782 +msgid "" +"Recognized filenames are of the form :file:`/vsigs_streaming/bucket/key` " +"where ``bucket`` is the name of the bucket and ``key`` is the object " +"\"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:784 +msgid "" +"Authentication options, and read-only features, are identical to " +":ref:`/vsigs/ <vsigs>`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:791 +msgid "/vsiaz/ (Microsoft Azure Blob files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:793 +msgid "" +"/vsiaz/ is a file system handler that allows on-the-fly random reading of" +" (primarily non-public) files available in Microsoft Azure Blob " +"containers, without prior download of the entire file. It requires GDAL " +"to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:795 +msgid "" +"See :ref:`/vsiadls/ <vsiadls>` for a related filesystem for Azure Data " +"Lake Storage Gen2." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:797 +msgid "" +"It also allows sequential writing of files. No seeks or read operations " +"are then allowed, so in particular direct writing of GeoTIFF files with " +"the GTiff driver is not supported, unless, if, starting with GDAL 3.2, " +"the :config:`CPL_VSIL_USE_TEMP_FILE_FOR_RANDOM_WRITE` configuration " +"option is set to ``YES``, in which case random-write access is possible " +"(involves the creation of a temporary local file, whose location is " +"controlled by the :config:`CPL_TMPDIR` configuration option). A block " +"blob will be created if the file size is below 4 MB. Beyond, an append " +"blob will be created (with a maximum file size of 195 GB)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:800 +msgid "" +"Deletion of files with :cpp:func:`VSIUnlink`, creation of directories " +"with :cpp:func:`VSIMkdir` and deletion of (empty) directories with " +":cpp:func:`VSIRmdir` are also possible. Note: when using " +":cpp:func:`VSIMkdir`, a special hidden :file:`.gdal_marker_for_dir` empty" +" file is created, since Azure Blob does not natively support empty " +"directories. If that file is the last one remaining in a directory, " +":cpp:func:`VSIRmdir` will automatically remove it. This file will not be " +"seen with :cpp:func:`VSIReadDir`. If removing files from directories not " +"created with :cpp:func:`VSIMkdir`, when the last file is deleted, its " +"directory is automatically removed by Azure, so the sequence " +"``VSIUnlink(\"/vsiaz/container/subdir/lastfile\")`` followed by " +"``VSIRmdir(\"/vsiaz/container/subdir\")`` will fail on the " +":cpp:func:`VSIRmdir` invocation." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:802 +msgid "" +"Recognized filenames are of the form :file:`/vsiaz/container/key`, where " +"``container`` is the name of the container and ``key`` is the object " +"\"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:806 +msgid "The following configuration options are specific to the /vsiaz/ handler:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:863 +msgid "The :config:`AZURE_STORAGE_CONNECTION_STRING` configuration option" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:865 +msgid "" +"The :config:`AZURE_STORAGE_ACCOUNT` configuration option is set to " +"specify the account name AND" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:867 +msgid "" +"(GDAL >= 3.5) The :config:`AZURE_STORAGE_ACCESS_TOKEN` configuration " +"option is set to specify the access token, that will be included in a " +"\"Authorization: Bearer ${AZURE_STORAGE_ACCESS_TOKEN}\" header. This " +"access token is typically obtained using Microsoft Authentication Library" +" (MSAL)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:868 +msgid "" +"The :config:`AZURE_STORAGE_ACCESS_KEY` configuration option is set to " +"specify the secret key." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:869 +msgid "" +"The :config:`AZURE_NO_SIGN_REQUEST=YES` configuration option is set, so " +"as to disable any request signing. This option might be used for accounts" +" with public access rights. Available since GDAL 3.2" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:870 +msgid "" +"The :config:`AZURE_STORAGE_SAS_TOKEN` configuration option (``AZURE_SAS``" +" if GDAL < 3.5) is set to specify a Shared Access Signature. This SAS is " +"appended to URLs built by the /vsiaz/ file system handler. Its value " +"should already be URL-encoded and should not contain any leading '?' or " +"'&' character (e.g. a valid one may look like " +"\"st=2019-07-18T03%3A53%3A22Z&se=2035-07-19T03%3A53%3A00Z&sp=rl&sv=2018-03-28&sr=c&sig=2RIXmLbLbiagYnUd49rgx2kOXKyILrJOgafmkODhRAQ%3D\")." +" Available since GDAL 3.2" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:871 +msgid "" +"The current machine is a Azure Virtual Machine with Azure Active " +"Directory permissions assigned to it (see https://docs.microsoft.com/en-" +"us/azure/active-directory/managed-identities-azure-resources/qs-" +"configure-portal-windows-vm). Available since GDAL 3.3." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:873 +msgid "" +"Authentication using Azure Active Directory Workload Identity (using " +"AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_FEDERATED_TOKEN_FILE and " +"AZURE_AUTHORITY_HOST environment variables), typically for Azure " +"Kubernetes, is available since GDAL 3.7.2" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:875 +msgid "" +"Starting with GDAL 3.5, the `configuration file " +"<https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-" +"conceptual/azure-cli-configuration.md>` of the \"az\" command line " +"utility can be used. The following keys of the ``[storage]`` section will" +" be used in the following priority: ``connection_string``, ``account`` + " +"``key`` or ``account`` + ``sas_token``" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:879 +msgid "" +"Since GDAL 3.3, the :cpp:func:`VSIGetFileMetadata` and " +":cpp:func:`VSISetFileMetadata` operations are supported." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:886 +msgid "/vsiaz_streaming/ (Microsoft Azure Blob files: streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:888 +msgid "" +"/vsiaz_streaming/ is a file system handler that allows on-the-fly " +"sequential reading of files (primarily non-public) files available in " +"Microsoft Azure Blob containers, buckets, without prior download of the " +"entire file. It requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:890 +msgid "" +"Recognized filenames are of the form " +":file:`/vsiaz_streaming/container/key` where ``container`` is the name of" +" the container and ``key`` is the object \"key\", i.e. a filename " +"potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:892 +msgid "" +"Authentication options, and read-only features, are identical to " +":ref:`/vsiaz/ <vsiaz>`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:899 +msgid "/vsiadls/ (Microsoft Azure Data Lake Storage Gen2)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:901 +msgid "" +"/vsiadls/ is a file system handler that allows on-the-fly random reading " +"of (primarily non-public) files available in Microsoft Azure Data Lake " +"Storage file systems, without prior download of the entire file. It " +"requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:906 +msgid "" +"It has similar capabilities as :ref:`/vsiaz/ <vsiaz>`, and in particular " +"uses the same configuration options for authentication. Its advantages " +"over /vsiaz/ are a real management of directory and Unix-style ACL " +"support. Some features require the Azure storage to have hierarchical " +"support turned on. Consult its `documentation <https://docs.microsoft.com" +"/en-us/azure/storage/blobs/data-lake-storage-introduction>`__" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:912 +msgid "The main enhancements over /vsiaz/ are:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:914 +msgid "" +"True directory support (no need for the artificial " +":file:`.gdal_marker_for_dir` empty file that is used for /vsiaz/ to have " +"empty directories)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:916 +msgid "One-call recursive directory deletion with :cpp:func:`VSIRmdirRecursive`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:917 +msgid "Atomic renaming with :cpp:func:`VSIRename`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:918 +msgid "" +":cpp:func:`VSIGetFileMetadata` support for the \"STATUS\" and \"ACL\" " +"metadata domains" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:919 +msgid "" +":cpp:func:`VSISetFileMetadata` support for the \"PROPERTIES\" and \"ACL\"" +" metadata domains" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:926 +msgid "/vsioss/ (Alibaba Cloud OSS files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:928 +msgid "" +"/vsioss/ is a file system handler that allows on-the-fly random reading " +"of (primarily non-public) files available in Alibaba Cloud Object Storage" +" Service (OSS) buckets, without prior download of the entire file. It " +"requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:930 +#: ../../source/user/virtual_file_systems.rst:986 +#: ../../source/user/virtual_file_systems.rst:1116 +msgid "" +"It also allows sequential writing of files. No seeks or read operations " +"are then allowed, so in particular direct writing of GeoTIFF files with " +"the GTiff driver is not supported, unless, if, starting with GDAL 3.2, " +"the :config:`CPL_VSIL_USE_TEMP_FILE_FOR_RANDOM_WRITE` configuration " +"option is set to ``YES``, in which case random-write access is possible " +"(involves the creation of a temporary local file, whose location is " +"controlled by the :config:`CPL_TMPDIR` configuration option). Deletion of" +" files with :cpp:func:`VSIUnlink` is also supported. Creation of " +"directories with :cpp:func:`VSIMkdir` and deletion of (empty) directories" +" with :cpp:func:`VSIRmdir` are also possible." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:933 +msgid "" +"Recognized filenames are of the form :file:`/vsioss/bucket/key` where " +"``bucket`` is the name of the OSS bucket and ``key`` is the OSS object " +"\"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:937 +#: ../../source/user/virtual_file_systems.rst:993 +msgid "The following configuration options are specific to the /vsioss/ handler:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:960 +msgid "" +"The :config:`OSS_SECRET_ACCESS_KEY` and :config:`OSS_ACCESS_KEY_ID` " +"configuration options must be set. The :config:`OSS_ENDPOINT` " +"configuration option should normally be set to the appropriate value, " +"which reflects the region attached to the bucket. If the bucket is stored" +" in another region than oss-us-east-1, the code logic will redirect to " +"the appropriate endpoint." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:962 +msgid "" +"On writing, the file is uploaded using the OSS multipart upload API. The " +"size of chunks is set to 50 MB by default, allowing creating files up to " +"500 GB (10000 parts of 50 MB each). If larger files are needed, then " +"increase the value of the :config:`VSIOSS_CHUNK_SIZE` config option to a " +"larger value (expressed in MB). In case the process is killed and the " +"file not properly closed, the multipart upload will remain open, causing " +"Alibaba to charge you for the parts storage. You'll have to abort " +"yourself with other means. For files smaller than the chunk size, a " +"simple PUT request is used instead of the multipart upload API." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:969 +msgid "/vsioss_streaming/ (Alibaba Cloud OSS files: streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:971 +msgid "" +"/vsioss_streaming/ is a file system handler that allows on-the-fly " +"sequential reading of files (primarily non-public) files available in " +"Alibaba Cloud Object Storage Service (OSS) buckets, without prior " +"download of the entire file. It requires GDAL to be built against " +"libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:973 +msgid "" +"Recognized filenames are of the form :file:`/vsioss_streaming/bucket/key`" +" where ``bucket`` is the name of the bucket and ``key`` is the object " +"\"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:975 +msgid "" +"Authentication options, and read-only features, are identical to " +":ref:`/vsioss/ <vsioss>`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:982 +msgid "/vsiswift/ (OpenStack Swift Object Storage)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:984 +msgid "" +"/vsiswift/ is a file system handler that allows on-the-fly random reading" +" of (primarily non-public) files available in OpenStack Swift Object " +"Storage (swift) buckets, without prior download of the entire file. It " +"requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:989 +msgid "" +"Recognized filenames are of the form :file:`/vsiswift/bucket/key` where " +"``bucket`` is the name of the swift bucket and ``key`` is the swift " +"object \"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1015 +msgid "" +"Three authentication methods are possible, and are attempted in the " +"following order:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1017 +msgid "" +"The :config:`SWIFT_STORAGE_URL` and :config:`SWIFT_AUTH_TOKEN` " +"configuration options are set respectively to the storage URL (e.g " +"http://127.0.0.1:12345/v1/AUTH_something) and the value of the x-auth-" +"token authorization token." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1018 +msgid "" +"The :config:`SWIFT_AUTH_V1_URL`, :config:`SWIFT_USER` and " +":config:`SWIFT_KEY` configuration options are set respectively to the " +"endpoint of the Auth V1 authentication (e.g " +"http://127.0.0.1:12345/auth/v1.0), the user name and the key/password. " +"This authentication endpoint will be used to retrieve the storage URL and" +" authorization token mentioned in the first authentication method." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1019 +msgid "" +"Authentication with Keystone v3 is using the same options as python-" +"swiftclient, see https://docs.openstack.org/python-" +"swiftclient/latest/cli/index.html#authentication for more details. GDAL " +"(>= 3.1) supports the following options:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1021 +#: ../../source/user/virtual_file_systems.rst:1032 +msgid "`OS_IDENTITY_API_VERSION=3`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1022 +#: ../../source/user/virtual_file_systems.rst:1034 +msgid "`OS_AUTH_URL`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1023 +msgid "`OS_USERNAME`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1024 +msgid "`OS_PASSWORD`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1025 +msgid "`OS_USER_DOMAIN_NAME`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1026 +msgid "`OS_PROJECT_NAME`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1027 +msgid "`OS_PROJECT_DOMAIN_NAME`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1028 +#: ../../source/user/virtual_file_systems.rst:1037 +msgid "`OS_REGION_NAME`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1030 +msgid "" +"Application Credential Authentication via Keystone v3, GDAL (>= 3.3.1) " +"supports application-credential authentication with the following " +"options:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1033 +msgid "`OS_AUTH_TYPE=v3applicationcredential`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1035 +msgid "`OS_APPLICATION_CREDENTIAL_ID`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1036 +msgid "`OS_APPLICATION_CREDENTIAL_SECRET`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1039 +msgid "" +"This file system handler also allows sequential writing of files (no " +"seeks or read operations are then allowed)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1041 +msgid "" +"In some versions of OpenStack Swift, the access to large (segmented) " +"files fails unless they are explicitly marked as static large objects, " +"instead of being dynamic large objects which is the default. Using the " +"python-swiftclient this can be achieved when uploading the file by " +"passing the ``--use-slo`` flag (see https://docs.openstack.org/python-" +"swiftclient/latest/cli/index.html#swift-upload for all options). For more" +" information about large objects see " +"https://docs.openstack.org/swift/latest/api/large_objects.html." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1048 +msgid "/vsiswift_streaming/ (OpenStack Swift Object Storage: streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1050 +msgid "" +"/vsiswift_streaming/ is a file system handler that allows on-the-fly " +"sequential reading of files (primarily non-public) files available in " +"OpenStack Swift Object Storage (swift) buckets, without prior download of" +" the entire file. It requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1052 +msgid "" +"Recognized filenames are of the form " +":file:`/vsiswift_streaming/bucket/key` where ``bucket`` is the name of " +"the bucket and ``key`` is the object \"key\", i.e. a filename potentially" +" containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1054 +msgid "" +"Authentication options, and read-only features, are identical to " +":ref:`/vsiswift/ <vsiswift>`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1061 +msgid "/vsihdfs/ (Hadoop File System)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1063 +msgid "" +"/vsihdfs/ is a file system handler that provides read access to HDFS. " +"This handler requires GDAL to have been built with Java support (CMake " +"`FindJNI <https://cmake.org/cmake/help/latest/module/FindJNI.html>`__) " +"and :ref:`HDFS <building_from_source_hdfs>` support. Support for this " +"handler is currently only available on Unix-like systems." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1069 +msgid "" +"Note: support for the HTTP REST API (webHdfs) is also available with " +":ref:`vsiwebhdfs`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1071 +msgid "" +"The LD_LIBRARY_PATH and CLASSPATH environment variables must be typically" +" set up as following." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1081 +msgid "" +"Failure to properly define the CLASSPATH will result in hard crashes in " +"the native libhdfs." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1084 +msgid "Relevant Hadoop documentation links:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1086 +msgid "" +"`C API libhdfs <https://hadoop.apache.org/docs/stable/hadoop-project-dist" +"/hadoop-hdfs/LibHdfs.html>`__" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1087 +msgid "" +"`HDFS Users Guide <https://hadoop.apache.org/docs/stable/hadoop-project-" +"dist/hadoop-hdfs/HdfsUserGuide.html>`__" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1088 +msgid "" +"`Hadoop: Setting up a Single Node Cluster " +"<https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-" +"common/SingleCluster.html>`__" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1090 +msgid "" +"Recognized filenames are of the form :file:`/vsihdfs/hdfsUri` where " +"``hdfsUri`` is a valid HDFS URI." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1104 +msgid "/vsiwebhdfs/ (Web Hadoop File System REST API)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1106 +msgid "" +"/vsiwebhdfs/ is a file system handler that provides read and write access" +" to HDFS through its HTTP REST API." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1108 +msgid "" +"Recognized filenames are of the form " +":file:`/vsiwebhdfs/http://hostname:port/webhdfs/v1/path/to/filename`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1121 +msgid "The following configuration options are available:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1145 +msgid "" +"This file system handler also allows sequential writing of files (no " +"seeks or read operations are then allowed)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1152 +msgid "/vsistdin/ (standard input streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1154 +msgid "" +"/vsistdin/ is a file handler that allows reading from the standard input " +"stream." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1156 +msgid "" +"The filename syntax must be only :file:`/vsistdin/`, (not e.g., " +"/vsistdin/path/to/f.csv , but \"/vsistdin?buffer_limit=value\" is OK.)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1159 +msgid "" +"The file operations available are of course limited to Read() and forward" +" Seek(). Full seek in the first MB of a file is possible, and it is " +"cached so that closing, re-opening :file:`/vsistdin/` and reading within " +"this first megabyte is possible multiple times in the same process." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1164 +msgid "" +"The size of the in-memory cache can be controlled with the " +":config:`CPL_VSISTDIN_BUFFER_LIMIT` configuration option:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1174 +msgid "The \"/vsistdin?buffer_limit=value\" syntax can also be used." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1176 +msgid "" +"/vsistdin filenames can be combined with other file system. For example, " +"to read a file within a potentially big ZIP file streamed to " +"gdal_translate:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1187 +msgid "/vsistdout/ (standard output streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1189 +msgid "" +"/vsistdout/ is a file handler that allows writing into the standard " +"output stream." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1191 +msgid "The filename syntax must be only :file:`/vsistdout/`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1193 +msgid "The file operations available are of course limited to Write()." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1195 +msgid "" +"A variation of this file system exists as the " +":file:`/vsistdout_redirect/` file system handler, where the output " +"function can be defined with :cpp:func:`VSIStdoutSetRedirection`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1200 +msgid "/vsimem/ (in-memory files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1202 +msgid "" +"/vsimem/ is a file handler that allows block of memory to be treated as " +"files. All portions of the file system underneath the base path " +":file:`/vsimem/` will be handled by this driver." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1204 +msgid "" +"Normal VSI*L functions can be used freely to create and destroy memory " +"arrays, treating them as if they were real file system objects. Some " +"additional methods exist to efficiently create memory file system objects" +" without duplicating original copies of the data or to \"steal\" the " +"block of memory associated with a memory file. See " +":cpp:func:`VSIFileFromMemBuffer` and :cpp:func:`VSIGetMemFileBuffer`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1206 +msgid "Directory related functions are supported." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1208 +msgid "" +"/vsimem/ files are visible within the same process. Multiple threads can " +"access the same underlying file in read mode, provided they used " +"different handles, but concurrent write and read operations on the same " +"underlying file are not supported (locking is left to the responsibility " +"of calling code)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1213 +msgid "/vsisubfile/ (portions of files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1215 +msgid "" +"The /vsisubfile/ virtual file system handler allows access to subregions " +"of files, treating them as a file on their own to the virtual file system" +" functions (VSIFOpenL(), etc)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1217 +msgid "" +"A special form of the filename is used to indicate a subportion of " +"another file: :file:`/vsisubfile/<offset>[_<size>],<filename>`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1219 +msgid "" +"The size parameter is optional. Without it the remainder of the file from" +" the start offset as treated as part of the subfile. Otherwise only " +"<size> bytes from <offset> are treated as part of the subfile. The " +"<filename> portion may be a relative or absolute path using normal rules." +" The <offset> and <size> values are in bytes." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1228 +msgid "" +"Unlike the /vsimem/ or conventional file system handlers, there is no " +"meaningful support for filesystem operations for creating new files, " +"traversing directories, and deleting files within the /vsisubfile/ area. " +"Only the :cpp:func:`VSIStatL`, :cpp:func:`VSIFOpenL` and operations based" +" on the file handle returned by :cpp:func:`VSIFOpenL` operate properly." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1233 +msgid "/vsisparse/ (sparse files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1235 +msgid "" +"The /vsisparse/ virtual file handler allows a virtual file to be composed" +" from chunks of data in other files, potentially with large spaces in the" +" virtual file set to a constant value. This can make it possible to test " +"some sorts of operations on what seems to be a large file with image data" +" set to a constant value. It is also helpful when wanting to add test " +"files to the test suite that are too large, but for which most of the " +"data can be ignored. It could, in theory, also be used to treat several " +"files on different file systems as one large virtual file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1237 +msgid "" +"The file referenced by /vsisparse/ should be an XML control file " +"formatted something like:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1271 +msgid "Hopefully the values and semantics are fairly obvious." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1277 +msgid "/vsicached/ (File caching)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1279 +msgid "" +"The :cpp:func:`VSICreateCachedFile` function takes a virtual file handle " +"and returns a new handle that caches read-operations on the input file " +"handle. The cache is RAM based and the content of the cache is discarded " +"when the file handle is closed. The cache is a least-recently used lists " +"of blocks of 32KB each (default size)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1281 +msgid "" +"This is mostly useful for files accessible through slow local/operating-" +"system-mounted filesystems." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1283 +msgid "" +"That is implicitly used by a number of the above mentioned file systems " +"(namely the default one for standard file system operations, and the " +"/vsicurl/ and other related network file systems) if the ``VSI_CACHE`` " +"configuration option is set to ``YES``." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1285 +msgid "" +"The default size of caching for each file is 25 MB (25 MB for each file " +"that is cached), and can be controlled with the ``VSI_CACHE_SIZE`` " +"configuration option (value in bytes)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1287 +msgid "" +"The :cpp:class:`VSICachedFile` class only handles read operations at that" +" time, and will error out on write operations." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1289 +msgid "" +"Starting with GDAL 3.8, a ``/vsicached?`` virtual file system also exists" +" to cache a particular file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1291 +msgid "" +"The syntax is the following one: " +"``/vsicached?[option_i=val_i&]*file=<filename>`` where each option name " +"and value (including the value of ``file``) is URL-encoded (actually, " +"only required for the ampersand character. It might be desirable to have " +"forward slash character uncoded). It is important that the ``file`` " +"option appears at the end, so that code that tries to look for side-car " +"files, list directory content, can work properly." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1298 +msgid "Currently supported options are:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1300 +msgid "" +"``chunk_size=<value>`` where value is the` size of the chunk size in " +"bytes. ``KB`` or ``MB`` suffixes can be also appended (without space " +"after the numeric value). The maximum supported value is 1 GB." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1301 +msgid "" +"``cache_size=<value>`` where value is the size of the cache size in " +"bytes, for each file. ``KB`` or ``MB`` suffixes can be also appended." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1305 +msgid "``/vsicached?chunk_size=1MB&file=/home/even/byte.tif``" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1306 +msgid "``/vsicached?file=./byte.tif``" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1312 +msgid "/vsicrypt/ (encrypted files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1314 +msgid "" +"/vsicrypt/ is a special file handler is installed that allows " +"reading/creating/update encrypted files on the fly, with random access " +"capabilities." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1316 +msgid "Refer to :cpp:func:`VSIInstallCryptFileHandler` for more details." +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/about.mo b/doc/source/locale/ja/LC_MESSAGES/about.mo new file mode 100644 index 0000000000000000000000000000000000000000..2a71bfe21e6bdefc7dd511c4980afe4734448365 GIT binary patch literal 2071 zcma)6-ES0C6dw)7WD{R}@x_?qGtRPw24VOJg_gS7vZUQ;ASUhI-Mib1voqt|JHSRB zm>IAi*p!GA1ht5T+Ez*kF%+cbKk?;u+Tyc+fal)XZ5ynKo1L8daqc<4^ZT89|9pGL zbpwBI;P)<mooce>XXE(q*9@bM_AUHMuN%gDXg##2(N3Tp$Nj(1uH$!phhe;f>*P(t zcpq&8?N?}TqcyraJ9>a|ARv6=aGMC%2b-0A;y0j*W1nzAeIQN+&eF2ltx=bIL@;7Q zg$Sa&>O^o5Lqw=hKD8;~v;u)s(I=rdUj!~1Hid#m9q4xhzf8gMY1JCES(!SV4nnDc z5hx69b?M$rb=<{pnALR#2eQzi5I13d08D`AQ%)U3L4Y%-hN)V>OB^dJixg|!tx#JR z)AVZAM7Hq~t_D;lwv7>icphTa2sAOc3_S2W*B4l8lY}hf1rVFNP<HE-!#O5~5Yk!V zGb$S3Rw3ZD8rW*Pt~kZe6av9)CK&oF#x<!eHLzX{*Yn*n<qC8bii)NaU7z(24uD5$ z6e^ULeOAKriouTq47oeEyB(Ccy9(WXuqV4e+tv~$YZUsCSftE7gNhpcw50`itKuB- z=|G?o4b&>c9yCt50n|wYz6@MJbx2?ictNSf23OMQ6FPm>wQcvDVyu(Zn7}S6lvEzb zS5P2UWz@IeLT4d=!8n;BF!L4jQ|fc9)k+g&`l#a7?Bz99F^>i{ZWdh&GA9c~^O#Sy z2xcb{)Y65Txev`;8|3y_?R$6T_UCfwX!g;wOoeRvo$Bi7GkXhWX9s*#uzK@5PZv&f zWqPo?&EiJqTX4!{<sk;2kOrv}IM~qB>=$}^q*f=)&Z2aOKX-bFQwxxM3(gP>v(3aT zQc_pjaImN6h|RLDUpt&RX$L;B&Et4!xCM@<r~FXc0Z503atAWK`QENgM%uEu%rVyy z$evkjc$iVp^J1506XqO%@(}Sk6^8;*HTP}$sgkPHH@lp&TR|}_*jHjA(@h=fBX3A* z!-AuvgtuXLwyhmgq)&kiAIf-EMo(q*LdMT!_^XV+m(j!4bYX4w*~`gmG9FgD(Tim1 zZt{FWM&IH;nI2u8xGh8UzoLUo%Xm@^;yD@4sP&7H46n)P8_c2~g=U@z9p_(t4`jFi zGMZCq;u|u4ETbiz@~OfU-jLz_|MgaY46n#&G`alS%gHM;ysop~m*FKDE+eEY{0nI_ zI_6jRM-hU^LrjaO7G(6hjDOUiM$$^RFmP8Ros-ccjr56(XB6-h!1&FT#fvIJi{90- zrS(TYZ!jriJdUi+qkppLyh(n`f5WW_G#Qy)`wqv7_SM;`^>_)jSe>}KvW!|No;Hfr z{A1NqX<;Y{iro@26)(E9xiWSqd2&xln<^Sk$tc7ElIdH?(kv>vvit&b%Mc5GEaRV4 zsqtuwP8{FYG<_|jUsMOgdhp-KVB<}b@h#2Yq70FYhv{3kcl8G(eBsqMO-I&Ef-S4u zr**YTs@3>%a_5l@vD+dUjiq`c1?lsrrFtNvMH$Vg{*FhCWFlI-Jk#vMZQsI`Kklt8 zVi%!^!}=)Rk$K&ulUpOLKe(BU+)Ex@RhOcvjuIjnezrC`vNo#7(-PqJ^XnVpsk@<i P8v&y<<0)WhJ(m9f=+>`C literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/about.po b/doc/source/locale/ja/LC_MESSAGES/about.po new file mode 100644 index 000000000000..0bec2ec31c07 --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/about.po @@ -0,0 +1,61 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Yoichi Kayama <yoichi.kayama@gmail.com>\\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/about.rst:5 +msgid "What is GDAL?" +msgstr "" + +#: ../../source/about_no_title.rst:1 +msgid "" +"GDAL is a translator library for raster and vector geospatial data " +"formats that is released under an MIT style Open Source :ref:`license` by" +" the `Open Source Geospatial Foundation`_. As a library, it presents a " +"single raster abstract data model and single vector abstract data model " +"to the calling application for all supported formats. It also comes with " +"a variety of useful command line utilities for data translation and " +"processing. The `NEWS`_ page describes the June 2024 GDAL/OGR 3.9.1 " +"release." +msgstr "" +"GDAL はラスターとベクターの空間データ形式をを変換するライブラリです。これは MIT スタイル :ref:`license` の " +"オープンソースとして `Open Source Geospatial Foundation`_ から公開されています. " +"ライブラリとしてのGDALはすべてのサポートする形式をアプリケーションから単一のラスタ抽象データモデルか単一のベクター抽象モデルとして利用する機能を提供しています。またGDALではデータ変換やデータ加工をするための多彩で便利なコマンドラインユーティリティを提供しています。" +" `NEWS`_ ページには 2024 6月の GDAL/OGR 3.9.1 リリースについての情報があります。" + +#: ../../source/about_no_title.rst:-1 +msgid "OSGeo project" +msgstr "OSGeoプロジェクト" + +#: ../../source/about_no_title.rst:10 +msgid "See :ref:`software_using_gdal`" +msgstr "参照 :ref:`software_using_gdal`" + +#: ../../source/about_no_title.rst:16 +msgid "" +"You may quote GDAL in publications by using the following Digital Object " +"Identifier: |DOI|" +msgstr "" +"以下のデジタルオブジェクト識別子を利用して出版物でGDALを引用することができます " +": |DOI|" + +#: ../../source/about_no_title.rst +msgid "DOI 10.5281/zenodo.5884351" +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/about_no_title.mo b/doc/source/locale/ja/LC_MESSAGES/about_no_title.mo new file mode 100644 index 0000000000000000000000000000000000000000..2a71bfe21e6bdefc7dd511c4980afe4734448365 GIT binary patch literal 2071 zcma)6-ES0C6dw)7WD{R}@x_?qGtRPw24VOJg_gS7vZUQ;ASUhI-Mib1voqt|JHSRB zm>IAi*p!GA1ht5T+Ez*kF%+cbKk?;u+Tyc+fal)XZ5ynKo1L8daqc<4^ZT89|9pGL zbpwBI;P)<mooce>XXE(q*9@bM_AUHMuN%gDXg##2(N3Tp$Nj(1uH$!phhe;f>*P(t zcpq&8?N?}TqcyraJ9>a|ARv6=aGMC%2b-0A;y0j*W1nzAeIQN+&eF2ltx=bIL@;7Q zg$Sa&>O^o5Lqw=hKD8;~v;u)s(I=rdUj!~1Hid#m9q4xhzf8gMY1JCES(!SV4nnDc z5hx69b?M$rb=<{pnALR#2eQzi5I13d08D`AQ%)U3L4Y%-hN)V>OB^dJixg|!tx#JR z)AVZAM7Hq~t_D;lwv7>icphTa2sAOc3_S2W*B4l8lY}hf1rVFNP<HE-!#O5~5Yk!V zGb$S3Rw3ZD8rW*Pt~kZe6av9)CK&oF#x<!eHLzX{*Yn*n<qC8bii)NaU7z(24uD5$ z6e^ULeOAKriouTq47oeEyB(Ccy9(WXuqV4e+tv~$YZUsCSftE7gNhpcw50`itKuB- z=|G?o4b&>c9yCt50n|wYz6@MJbx2?ictNSf23OMQ6FPm>wQcvDVyu(Zn7}S6lvEzb zS5P2UWz@IeLT4d=!8n;BF!L4jQ|fc9)k+g&`l#a7?Bz99F^>i{ZWdh&GA9c~^O#Sy z2xcb{)Y65Txev`;8|3y_?R$6T_UCfwX!g;wOoeRvo$Bi7GkXhWX9s*#uzK@5PZv&f zWqPo?&EiJqTX4!{<sk;2kOrv}IM~qB>=$}^q*f=)&Z2aOKX-bFQwxxM3(gP>v(3aT zQc_pjaImN6h|RLDUpt&RX$L;B&Et4!xCM@<r~FXc0Z503atAWK`QENgM%uEu%rVyy z$evkjc$iVp^J1506XqO%@(}Sk6^8;*HTP}$sgkPHH@lp&TR|}_*jHjA(@h=fBX3A* z!-AuvgtuXLwyhmgq)&kiAIf-EMo(q*LdMT!_^XV+m(j!4bYX4w*~`gmG9FgD(Tim1 zZt{FWM&IH;nI2u8xGh8UzoLUo%Xm@^;yD@4sP&7H46n)P8_c2~g=U@z9p_(t4`jFi zGMZCq;u|u4ETbiz@~OfU-jLz_|MgaY46n#&G`alS%gHM;ysop~m*FKDE+eEY{0nI_ zI_6jRM-hU^LrjaO7G(6hjDOUiM$$^RFmP8Ros-ccjr56(XB6-h!1&FT#fvIJi{90- zrS(TYZ!jriJdUi+qkppLyh(n`f5WW_G#Qy)`wqv7_SM;`^>_)jSe>}KvW!|No;Hfr z{A1NqX<;Y{iro@26)(E9xiWSqd2&xln<^Sk$tc7ElIdH?(kv>vvit&b%Mc5GEaRV4 zsqtuwP8{FYG<_|jUsMOgdhp-KVB<}b@h#2Yq70FYhv{3kcl8G(eBsqMO-I&Ef-S4u zr**YTs@3>%a_5l@vD+dUjiq`c1?lsrrFtNvMH$Vg{*FhCWFlI-Jk#vMZQsI`Kklt8 zVi%!^!}=)Rk$K&ulUpOLKe(BU+)Ex@RhOcvjuIjnezrC`vNo#7(-PqJ^XnVpsk@<i P8v&y<<0)WhJ(m9f=+>`C literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/about_no_title.po b/doc/source/locale/ja/LC_MESSAGES/about_no_title.po new file mode 100644 index 000000000000..a9143edf1c60 --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/about_no_title.po @@ -0,0 +1,57 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Yoichi Kayama <yoichi.kayama@gmail.com>\\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/about_no_title.rst:1 +msgid "" +"GDAL is a translator library for raster and vector geospatial data " +"formats that is released under an MIT style Open Source :ref:`license` by" +" the `Open Source Geospatial Foundation`_. As a library, it presents a " +"single raster abstract data model and single vector abstract data model " +"to the calling application for all supported formats. It also comes with " +"a variety of useful command line utilities for data translation and " +"processing. The `NEWS`_ page describes the June 2024 GDAL/OGR 3.9.1 " +"release." +msgstr "" +"GDAL はラスターとベクターの空間データ形式をを変換するライブラリです。これは MIT スタイル :ref:`license` の " +"オープンソースとして `Open Source Geospatial Foundation`_ から公開されています. " +"ライブラリとしてのGDALはすべてのサポートする形式をアプリケーションから単一のラスタ抽象データモデルか単一のベクター抽象モデルとして利用する機能を提供しています。またGDALではデータ変換やデータ加工をするための多彩で便利なコマンドラインユーティリティを提供しています。" +" `NEWS`_ ページには 2024 6月の GDAL/OGR 3.9.1 リリースについての情報があります。" + +#: ../../source/about_no_title.rst:-1 +msgid "OSGeo project" +msgstr "OSGeoプロジェクト" + +#: ../../source/about_no_title.rst:10 +msgid "See :ref:`software_using_gdal`" +msgstr "参照 :ref:`software_using_gdal`" + +#: ../../source/about_no_title.rst:16 +msgid "" +"You may quote GDAL in publications by using the following Digital Object " +"Identifier: |DOI|" +msgstr "" +"以下のデジタルオブジェクト識別子を利用して出版物でGDALを引用することができます " +": |DOI|" + +#: ../../source/about_no_title.rst +msgid "DOI 10.5281/zenodo.5884351" +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/api.mo b/doc/source/locale/ja/LC_MESSAGES/api.mo new file mode 100644 index 0000000000000000000000000000000000000000..366061355b2aac6aec98d199f421aeea4c8fa480 GIT binary patch literal 701 zcmZvY&ubGw6vs#L=N>%t>|yR@;wA>Io2E2vwl$bFAuK|rm&s<bow_>{W@p8K2k9ad ztDuKQ6crRb1Vx16Nm2g;kKROB66t^8+ceM~9Qf?_y*J-^Gy8teoY+OM&H(3u^(;BE zUO;>rcnO>Y-T`NU_kaO>2F?LLfXw$3$a?((9vwsI59ldC96!)_s&_$Wpq@;10Gjn3 zPIV6yRaut{79m^2VT4v<;b|^Kgql>*kZGnMjN1YCu*1T3mbRFV6*$~}k9AlV_LbaZ zo+h;pxd8?^ZsFBxrH+jj>q(`F6ZyPDmSR65uC%bxY`A1uF`C^(s#G%z7tBJDn3su} z$L2+=cxl$WVwzwiEq0q{EvLRUyV4>~gH$W{YQu7Bvo{;pZKF;jO<YAq6i_Xdh1Vqa zHaNaU`!u9@zCTHGw<hVLA5tFVJQ*&mi#ip4OnrF4CWSWtNr=m6m~G?vdVMkAIjQ^w zqZ!1C24qF5FtV`dP12~GFX4l*Y?chC=Gcc5$>&UCSqjYrJQYS~Va@L73%!7HQNrE^ zRT0zWSa-?Xp)dQTE>px7p6qbpTX?R`wXw<sQ!qCeYTv?3w9Nus$mNT01sZ*P{`cDu zjkceTA3j6-gE!;dPbf{Eq{%Q%UZ=^|bn82O(dhn%{lU(pw3jB2v(k9`OS<)7bnh)1 Jz1o@f`3HA1*-Zcd literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/api.po b/doc/source/locale/ja/LC_MESSAGES/api.po new file mode 100644 index 000000000000..5c8e0462435b --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/api.po @@ -0,0 +1,10030 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Yoichi Kayama <yoichi.kayama@gmail.com>\\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/api/cpl.rst:10 +msgid "Common Portability Library C API" +msgstr "" + +#: ../../source/api/cpl.rst:13 +msgid "cpl_conv.h" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/gdal_alg.rst +#: ../../source/api/gdalwarp_cpp.rst ../../source/api/gnm_cpp.rst +#: ../../source/api/ogr_srs_api.rst ../../source/api/ogrspatialref.rst +#: ../../source/api/raster_c_api.rst ../../source/api/vector_c_api.rst +msgid "Defines" +msgstr "定義" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdal_alg.rst ../../source/api/gdal_utils.rst +#: ../../source/api/gdalwarp_cpp.rst ../../source/api/gnm_cpp.rst +#: ../../source/api/ogr_srs_api.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/raster_c_api.rst ../../source/api/vector_c_api.rst +msgid "Typedefs" +msgstr "型定義" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdal_alg.rst ../../source/api/gdal_utils.rst +#: ../../source/api/gdalwarp_cpp.rst ../../source/api/ogr_srs_api.rst +#: ../../source/api/ogrspatialref.rst ../../source/api/raster_c_api.rst +#: ../../source/api/vector_c_api.rst +msgid "Functions" +msgstr "関数" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdal_alg.rst ../../source/api/gdal_utils.rst +#: ../../source/api/gdalabstractmdarray_cpp.rst +#: ../../source/api/gdalattribute_cpp.rst ../../source/api/gdaldataset_cpp.rst +#: ../../source/api/gdaldimension_cpp.rst ../../source/api/gdaldriver_cpp.rst +#: ../../source/api/gdalextendeddatatype_cpp.rst +#: ../../source/api/gdalgroup_cpp.rst ../../source/api/gdalmdarray_cpp.rst +#: ../../source/api/gdalrasterband_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/gnm_cpp.rst ../../source/api/ogr_srs_api.rst +#: ../../source/api/ogrfeature_cpp.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/ogrgeometry_cpp.rst ../../source/api/ogrlayer_cpp.rst +#: ../../source/api/ogrspatialref.rst ../../source/api/raster_c_api.rst +#: ../../source/api/vector_c_api.rst of osgeo.gdal.BuildVRT +#: osgeo.gdal.BuildVRTOptions osgeo.gdal.DEMProcessing +#: osgeo.gdal.DEMProcessingOptions osgeo.gdal.Grid osgeo.gdal.GridOptions +#: osgeo.gdal.Info osgeo.gdal.MultiDimInfo osgeo.gdal.MultiDimTranslate +#: osgeo.gdal.MultiDimTranslateOptions osgeo.gdal.Nearblack +#: osgeo.gdal.NearblackOptions osgeo.gdal.Rasterize osgeo.gdal.RasterizeOptions +#: osgeo.gdal.Translate osgeo.gdal.TranslateOptions osgeo.gdal.VectorTranslate +#: osgeo.gdal.VectorTranslateOptions osgeo.gdal.Warp osgeo.gdal.WarpOptions +#: osgeo.ogr.DataSource.CopyLayer osgeo.ogr.DataSource.CreateLayer +#: osgeo.ogr.DataSource.DeleteLayer osgeo.ogr.DataSource.ExecuteSQL +#: osgeo.ogr.DataSource.GetDriver osgeo.ogr.DataSource.GetLayerByName +#: osgeo.ogr.DataSource.GetLayerCount osgeo.ogr.DataSource.GetName +#: osgeo.ogr.DataSource.ReleaseResultSet osgeo.ogr.DataSource.TestCapability +#: osgeo.ogr.Feature.Clone osgeo.ogr.Feature.DumpReadable +#: osgeo.ogr.Feature.Equal osgeo.ogr.Feature.FillUnsetWithDefault +#: osgeo.ogr.Feature.GetDefnRef osgeo.ogr.Feature.GetFID +#: osgeo.ogr.Feature.GetFieldAsBinary osgeo.ogr.Feature.GetFieldAsDateTime +#: osgeo.ogr.Feature.GetFieldAsDouble osgeo.ogr.Feature.GetFieldAsDoubleList +#: osgeo.ogr.Feature.GetFieldAsInteger osgeo.ogr.Feature.GetFieldAsInteger64 +#: osgeo.ogr.Feature.GetFieldAsInteger64List +#: osgeo.ogr.Feature.GetFieldAsIntegerList osgeo.ogr.Feature.GetFieldAsString +#: osgeo.ogr.Feature.GetFieldAsStringList osgeo.ogr.Feature.GetFieldCount +#: osgeo.ogr.Feature.GetFieldDefnRef osgeo.ogr.Feature.GetFieldIndex +#: osgeo.ogr.Feature.GetGeomFieldCount osgeo.ogr.Feature.GetGeomFieldDefnRef +#: osgeo.ogr.Feature.GetGeomFieldIndex osgeo.ogr.Feature.GetGeomFieldRef +#: osgeo.ogr.Feature.GetNativeData osgeo.ogr.Feature.GetNativeMediaType +#: osgeo.ogr.Feature.GetStyleString osgeo.ogr.Feature.IsFieldNull +#: osgeo.ogr.Feature.IsFieldSet osgeo.ogr.Feature.IsFieldSetAndNotNull +#: osgeo.ogr.Feature.SetFID osgeo.ogr.Feature.SetFieldDoubleList +#: osgeo.ogr.Feature.SetFieldInteger64 osgeo.ogr.Feature.SetFieldInteger64List +#: osgeo.ogr.Feature.SetFieldIntegerList osgeo.ogr.Feature.SetFieldNull +#: osgeo.ogr.Feature.SetFieldString osgeo.ogr.Feature.SetFieldStringList +#: osgeo.ogr.Feature.SetFrom osgeo.ogr.Feature.SetFromWithMap +#: osgeo.ogr.Feature.SetGeomField osgeo.ogr.Feature.SetGeomFieldDirectly +#: osgeo.ogr.Feature.SetGeometry osgeo.ogr.Feature.SetGeometryDirectly +#: osgeo.ogr.Feature.SetNativeData osgeo.ogr.Feature.SetNativeMediaType +#: osgeo.ogr.Feature.SetStyleString osgeo.ogr.Feature.UnsetField +#: osgeo.ogr.Feature.Validate osgeo.ogr.FeatureDefn.AddFieldDefn +#: osgeo.ogr.FeatureDefn.AddGeomFieldDefn +#: osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn +#: osgeo.ogr.FeatureDefn.GetFieldCount osgeo.ogr.FeatureDefn.GetFieldDefn +#: osgeo.ogr.FeatureDefn.GetFieldIndex osgeo.ogr.FeatureDefn.GetGeomFieldCount +#: osgeo.ogr.FeatureDefn.GetGeomFieldDefn +#: osgeo.ogr.FeatureDefn.GetGeomFieldIndex osgeo.ogr.FeatureDefn.GetGeomType +#: osgeo.ogr.FeatureDefn.GetName osgeo.ogr.FeatureDefn.GetReferenceCount +#: osgeo.ogr.FeatureDefn.IsGeometryIgnored osgeo.ogr.FeatureDefn.IsSame +#: osgeo.ogr.FeatureDefn.IsStyleIgnored osgeo.ogr.FeatureDefn.SetGeomType +#: osgeo.ogr.FeatureDefn.SetGeometryIgnored +#: osgeo.ogr.FeatureDefn.SetStyleIgnored +#: osgeo.ogr.FieldDefn.GetAlternativeNameRef osgeo.ogr.FieldDefn.GetDefault +#: osgeo.ogr.FieldDefn.GetDomainName osgeo.ogr.FieldDefn.GetJustify +#: osgeo.ogr.FieldDefn.GetNameRef osgeo.ogr.FieldDefn.GetPrecision +#: osgeo.ogr.FieldDefn.GetSubType osgeo.ogr.FieldDefn.GetType +#: osgeo.ogr.FieldDefn.GetWidth osgeo.ogr.FieldDefn.IsDefaultDriverSpecific +#: osgeo.ogr.FieldDefn.IsIgnored osgeo.ogr.FieldDefn.IsNullable +#: osgeo.ogr.FieldDefn.IsUnique osgeo.ogr.FieldDefn.SetAlternativeName +#: osgeo.ogr.FieldDefn.SetDefault osgeo.ogr.FieldDefn.SetDomainName +#: osgeo.ogr.FieldDefn.SetIgnored osgeo.ogr.FieldDefn.SetJustify +#: osgeo.ogr.FieldDefn.SetName osgeo.ogr.FieldDefn.SetNullable +#: osgeo.ogr.FieldDefn.SetPrecision osgeo.ogr.FieldDefn.SetSubType +#: osgeo.ogr.FieldDefn.SetType osgeo.ogr.FieldDefn.SetUnique +#: osgeo.ogr.FieldDefn.SetWidth osgeo.ogr.FieldDefn.justify +#: osgeo.ogr.FieldDefn.precision osgeo.ogr.FieldDefn.type +#: osgeo.ogr.FieldDefn.width osgeo.ogr.Geometry.AssignSpatialReference +#: osgeo.ogr.Geometry.Buffer osgeo.ogr.Geometry.Contains +#: osgeo.ogr.Geometry.Crosses osgeo.ogr.Geometry.DelaunayTriangulation +#: osgeo.ogr.Geometry.Difference osgeo.ogr.Geometry.Disjoint +#: osgeo.ogr.Geometry.Distance osgeo.ogr.Geometry.Distance3D +#: osgeo.ogr.Geometry.Equals osgeo.ogr.Geometry.ExportToIsoWkb +#: osgeo.ogr.Geometry.ExportToWkb osgeo.ogr.Geometry.Intersection +#: osgeo.ogr.Geometry.Intersects osgeo.ogr.Geometry.MakeValid +#: osgeo.ogr.Geometry.Overlaps osgeo.ogr.Geometry.Segmentize +#: osgeo.ogr.Geometry.Set3D osgeo.ogr.Geometry.SetCoordinateDimension +#: osgeo.ogr.Geometry.SetMeasured osgeo.ogr.Geometry.Simplify +#: osgeo.ogr.Geometry.SimplifyPreserveTopology osgeo.ogr.Geometry.SymDifference +#: osgeo.ogr.Geometry.Touches osgeo.ogr.Geometry.Transform +#: osgeo.ogr.Geometry.TransformTo osgeo.ogr.Geometry.Union +#: osgeo.ogr.Geometry.Within osgeo.ogr.Layer.AlterFieldDefn +#: osgeo.ogr.Layer.Clip osgeo.ogr.Layer.CreateFeature +#: osgeo.ogr.Layer.CreateField osgeo.ogr.Layer.CreateGeomField +#: osgeo.ogr.Layer.DeleteFeature osgeo.ogr.Layer.DeleteField +#: osgeo.ogr.Layer.Erase osgeo.ogr.Layer.GetExtent osgeo.ogr.Layer.GetFeature +#: osgeo.ogr.Layer.GetFeatureCount osgeo.ogr.Layer.GetGeometryTypes +#: osgeo.ogr.Layer.Identity osgeo.ogr.Layer.Intersection +#: osgeo.ogr.Layer.ReorderField osgeo.ogr.Layer.ReorderFields +#: osgeo.ogr.Layer.SetAttributeFilter osgeo.ogr.Layer.SetFeature +#: osgeo.ogr.Layer.SetIgnoredFields osgeo.ogr.Layer.SetNextByIndex +#: osgeo.ogr.Layer.SetSpatialFilter osgeo.ogr.Layer.SetSpatialFilterRect +#: osgeo.ogr.Layer.SymDifference osgeo.ogr.Layer.TestCapability +#: osgeo.ogr.Layer.Union osgeo.ogr.Layer.Update osgeo.ogr.Layer.UpsertFeature +msgid "Parameters" +msgstr "パラメーター" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdal_alg.rst ../../source/api/gdal_utils.rst +#: ../../source/api/gdalabstractmdarray_cpp.rst +#: ../../source/api/gdalattribute_cpp.rst ../../source/api/gdaldataset_cpp.rst +#: ../../source/api/gdaldimension_cpp.rst ../../source/api/gdaldriver_cpp.rst +#: ../../source/api/gdalgroup_cpp.rst ../../source/api/gdalmdarray_cpp.rst +#: ../../source/api/gdalrasterband_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/gnm_cpp.rst ../../source/api/ogr_srs_api.rst +#: ../../source/api/ogrfeature_cpp.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/ogrgeometry_cpp.rst ../../source/api/ogrlayer_cpp.rst +#: ../../source/api/ogrspatialref.rst ../../source/api/raster_c_api.rst +#: ../../source/api/vector_c_api.rst of osgeo.ogr.DataSource.CopyLayer +#: osgeo.ogr.DataSource.CreateLayer osgeo.ogr.DataSource.DeleteLayer +#: osgeo.ogr.DataSource.ExecuteSQL osgeo.ogr.DataSource.GetDriver +#: osgeo.ogr.DataSource.GetLayerByName osgeo.ogr.DataSource.GetLayerCount +#: osgeo.ogr.DataSource.GetName osgeo.ogr.DataSource.TestCapability +#: osgeo.ogr.Feature.Clone osgeo.ogr.Feature.Equal osgeo.ogr.Feature.GetDefnRef +#: osgeo.ogr.Feature.GetFID osgeo.ogr.Feature.GetFieldAsBinary +#: osgeo.ogr.Feature.GetFieldAsDateTime osgeo.ogr.Feature.GetFieldAsDouble +#: osgeo.ogr.Feature.GetFieldAsDoubleList osgeo.ogr.Feature.GetFieldAsInteger +#: osgeo.ogr.Feature.GetFieldAsInteger64 +#: osgeo.ogr.Feature.GetFieldAsInteger64List +#: osgeo.ogr.Feature.GetFieldAsIntegerList osgeo.ogr.Feature.GetFieldAsString +#: osgeo.ogr.Feature.GetFieldAsStringList osgeo.ogr.Feature.GetFieldCount +#: osgeo.ogr.Feature.GetFieldDefnRef osgeo.ogr.Feature.GetFieldIndex +#: osgeo.ogr.Feature.GetGeomFieldCount osgeo.ogr.Feature.GetGeomFieldDefnRef +#: osgeo.ogr.Feature.GetGeomFieldIndex osgeo.ogr.Feature.GetGeometryRef +#: osgeo.ogr.Feature.GetNativeData osgeo.ogr.Feature.GetNativeMediaType +#: osgeo.ogr.Feature.GetStyleString osgeo.ogr.Feature.IsFieldNull +#: osgeo.ogr.Feature.IsFieldSet osgeo.ogr.Feature.IsFieldSetAndNotNull +#: osgeo.ogr.Feature.SetFID osgeo.ogr.Feature.SetFrom +#: osgeo.ogr.Feature.SetFromWithMap osgeo.ogr.Feature.SetGeomField +#: osgeo.ogr.Feature.SetGeomFieldDirectly osgeo.ogr.Feature.SetGeometry +#: osgeo.ogr.Feature.SetGeometryDirectly osgeo.ogr.Feature.Validate +#: osgeo.ogr.Feature.geometry osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn +#: osgeo.ogr.FeatureDefn.GetFieldCount osgeo.ogr.FeatureDefn.GetFieldDefn +#: osgeo.ogr.FeatureDefn.GetFieldIndex osgeo.ogr.FeatureDefn.GetGeomFieldCount +#: osgeo.ogr.FeatureDefn.GetGeomFieldDefn +#: osgeo.ogr.FeatureDefn.GetGeomFieldIndex osgeo.ogr.FeatureDefn.GetGeomType +#: osgeo.ogr.FeatureDefn.GetName osgeo.ogr.FeatureDefn.GetReferenceCount +#: osgeo.ogr.FeatureDefn.IsGeometryIgnored osgeo.ogr.FeatureDefn.IsSame +#: osgeo.ogr.FeatureDefn.IsStyleIgnored +#: osgeo.ogr.FieldDefn.GetAlternativeNameRef osgeo.ogr.FieldDefn.GetDefault +#: osgeo.ogr.FieldDefn.GetDomainName osgeo.ogr.FieldDefn.GetJustify +#: osgeo.ogr.FieldDefn.GetNameRef osgeo.ogr.FieldDefn.GetPrecision +#: osgeo.ogr.FieldDefn.GetSubType osgeo.ogr.FieldDefn.GetType +#: osgeo.ogr.FieldDefn.GetWidth osgeo.ogr.FieldDefn.IsDefaultDriverSpecific +#: osgeo.ogr.FieldDefn.IsIgnored osgeo.ogr.FieldDefn.IsNullable +#: osgeo.ogr.FieldDefn.IsUnique osgeo.ogr.FieldDefn.justify +#: osgeo.ogr.FieldDefn.precision osgeo.ogr.FieldDefn.type +#: osgeo.ogr.FieldDefn.width osgeo.ogr.Geometry.Boundary +#: osgeo.ogr.Geometry.Buffer osgeo.ogr.Geometry.Clone +#: osgeo.ogr.Geometry.Contains osgeo.ogr.Geometry.ConvexHull +#: osgeo.ogr.Geometry.CoordinateDimension osgeo.ogr.Geometry.Crosses +#: osgeo.ogr.Geometry.DelaunayTriangulation osgeo.ogr.Geometry.Difference +#: osgeo.ogr.Geometry.Disjoint osgeo.ogr.Geometry.Distance +#: osgeo.ogr.Geometry.Distance3D osgeo.ogr.Geometry.Equals +#: osgeo.ogr.Geometry.GetCoordinateDimension osgeo.ogr.Geometry.GetDimension +#: osgeo.ogr.Geometry.GetEnvelope osgeo.ogr.Geometry.GetEnvelope3D +#: osgeo.ogr.Geometry.GetGeometryType osgeo.ogr.Geometry.Intersection +#: osgeo.ogr.Geometry.Intersects osgeo.ogr.Geometry.Is3D +#: osgeo.ogr.Geometry.IsEmpty osgeo.ogr.Geometry.IsMeasured +#: osgeo.ogr.Geometry.IsRing osgeo.ogr.Geometry.IsSimple +#: osgeo.ogr.Geometry.IsValid osgeo.ogr.Geometry.MakeValid +#: osgeo.ogr.Geometry.Normalize osgeo.ogr.Geometry.Overlaps +#: osgeo.ogr.Geometry.PointOnSurface osgeo.ogr.Geometry.Polygonize +#: osgeo.ogr.Geometry.Simplify osgeo.ogr.Geometry.SimplifyPreserveTopology +#: osgeo.ogr.Geometry.SymDifference osgeo.ogr.Geometry.Touches +#: osgeo.ogr.Geometry.Transform osgeo.ogr.Geometry.TransformTo +#: osgeo.ogr.Geometry.Union osgeo.ogr.Geometry.UnionCascaded +#: osgeo.ogr.Geometry.Within osgeo.ogr.Layer.AlterFieldDefn +#: osgeo.ogr.Layer.Clip osgeo.ogr.Layer.CommitTransaction +#: osgeo.ogr.Layer.CreateFeature osgeo.ogr.Layer.CreateField +#: osgeo.ogr.Layer.CreateGeomField osgeo.ogr.Layer.DeleteFeature +#: osgeo.ogr.Layer.DeleteField osgeo.ogr.Layer.Erase +#: osgeo.ogr.Layer.FindFieldIndex osgeo.ogr.Layer.GetExtent +#: osgeo.ogr.Layer.GetFIDColumn osgeo.ogr.Layer.GetFeature +#: osgeo.ogr.Layer.GetFeatureCount osgeo.ogr.Layer.GetGeomType +#: osgeo.ogr.Layer.GetGeometryColumn osgeo.ogr.Layer.GetGeometryTypes +#: osgeo.ogr.Layer.GetLayerDefn osgeo.ogr.Layer.GetName +#: osgeo.ogr.Layer.GetNextFeature osgeo.ogr.Layer.GetSpatialFilter +#: osgeo.ogr.Layer.GetSpatialRef osgeo.ogr.Layer.Identity +#: osgeo.ogr.Layer.Intersection osgeo.ogr.Layer.ReorderField +#: osgeo.ogr.Layer.ReorderFields osgeo.ogr.Layer.RollbackTransaction +#: osgeo.ogr.Layer.SetAttributeFilter osgeo.ogr.Layer.SetFeature +#: osgeo.ogr.Layer.SetIgnoredFields osgeo.ogr.Layer.SetNextByIndex +#: osgeo.ogr.Layer.StartTransaction osgeo.ogr.Layer.SymDifference +#: osgeo.ogr.Layer.SyncToDisk osgeo.ogr.Layer.TestCapability +#: osgeo.ogr.Layer.Union osgeo.ogr.Layer.Update osgeo.ogr.Layer.UpsertFeature +msgid "Returns" +msgstr "戻り値" + +#: ../../source/api/cpl.rst ../../source/api/gdal_alg.rst +#: ../../source/api/gdaldataset_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/ogr_srs_api.rst ../../source/api/raster_c_api.rst +#: ../../source/api/vector_c_api.rst +msgid "Public Members" +msgstr "公開メンバー" + +#: ../../source/api/cpl.rst:19 +msgid "cpl_csv.h" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/gdal_alg.rst +#: ../../source/api/gdalwarp_cpp.rst ../../source/api/gnm_cpp.rst +#: ../../source/api/ogr_srs_api.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/raster_c_api.rst ../../source/api/vector_c_api.rst +msgid "Enums" +msgstr "列挙" + +#: ../../source/api/cpl.rst:25 +msgid "cpl_compressor.h" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param input_data" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param input_size" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param output_data" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param output_size" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param options" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param compressor_user_data" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/gdal_alg.rst +#: ../../source/api/gdalabstractmdarray_cpp.rst +#: ../../source/api/raster_c_api.rst +msgid "Return" +msgstr "" + +#: ../../source/api/cpl.rst:31 +msgid "cpl_error.h" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdalabstractmdarray_cpp.rst +#: ../../source/api/gdalattribute_cpp.rst ../../source/api/gdaldataset_cpp.rst +#: ../../source/api/gdaldimension_cpp.rst ../../source/api/gdaldriver_cpp.rst +#: ../../source/api/gdalextendeddatatype_cpp.rst +#: ../../source/api/gdalgroup_cpp.rst ../../source/api/gdalmdarray_cpp.rst +#: ../../source/api/gdalrasterband_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/gnm_cpp.rst ../../source/api/ogrfeature_cpp.rst +#: ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/ogrgeometry_cpp.rst ../../source/api/ogrlayer_cpp.rst +#: ../../source/api/ogrspatialref.rst ../../source/api/vector_c_api.rst +msgid "Public Functions" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdalwarp_cpp.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/ogrspatialref.rst +msgid "Private Members" +msgstr "" + +#: ../../source/api/cpl.rst:37 +msgid "cpl_http.h" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pszURL" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param papszOptions" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pfnProgress" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pProgressArg" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pfnWrite" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pWriteArg" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/gdalabstractmdarray_cpp.rst +#: ../../source/api/raster_c_api.rst +msgid "Param pUserData" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdalabstractmdarray_cpp.rst +#: ../../source/api/gdaldataset_cpp.rst ../../source/api/ogrgeometry_cpp.rst +#: ../../source/api/ogrlayer_cpp.rst +msgid "Public Types" +msgstr "" + +#: ../../source/api/cpl.rst:43 +msgid "cpl_minixml.h" +msgstr "" + +#: ../../source/api/cpl.rst:49 +msgid "cpl_multiproc.h" +msgstr "" + +#: ../../source/api/cpl.rst:55 +msgid "cpl_port.h" +msgstr "" + +#: ../../source/api/cpl.rst:61 +msgid "cpl_progress.h" +msgstr "" + +#: ../../source/api/cpl.rst:67 +msgid "cpl_string.h" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/cpl_cpp.rst +#: ../../source/api/gdaldataset_cpp.rst ../../source/api/gdaldriver_cpp.rst +#: ../../source/api/gdalextendeddatatype_cpp.rst +#: ../../source/api/gdalrasterband_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/ogrfeature_cpp.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/ogrgeometry_cpp.rst ../../source/api/ogrlayer_cpp.rst +#: ../../source/api/ogrspatialref.rst +msgid "Public Static Functions" +msgstr "" + +#: ../../source/api/cpl.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/gnm_cpp.rst ../../source/api/ogrfeaturestyle_cpp.rst +#: ../../source/api/ogrspatialref.rst +msgid "Private Functions" +msgstr "" + +#: ../../source/api/cpl.rst:73 +msgid "cpl_time.h" +msgstr "" + +#: ../../source/api/cpl.rst:79 +msgid "cpl_virtualmem.h" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param ctxt" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param nOffset" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pPageToFill" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param nToFill" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pPageToBeEvicted" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param nToBeEvicted" +msgstr "" + +#: ../../source/api/cpl.rst:85 +msgid "cpl_vsi_error.h" +msgstr "" + +#: ../../source/api/cpl.rst:91 +msgid "cpl_vsi.h" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param pFile" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param nRanges" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param panOffsets" +msgstr "" + +#: ../../source/api/cpl.rst +msgid "Param panSizes" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Install /vsisubfile/ virtual file handler." +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsisubfile/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Install /vsicurl/ HTTP/FTP file system handler (requires libcurl)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsicurl/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Since GDAL 1.8.0" +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Install /vsicurl_streaming/ HTTP/FTP file system handler (requires " +"libcurl)." +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsicurl_streaming/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Since GDAL 1.10" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Install /vsis3/ Amazon S3 file system handler (requires libcurl)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsis3/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Since GDAL 2.1" +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Install /vsis3_streaming/ Amazon S3 file system handler (requires " +"libcurl)." +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsis3_streaming/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Install /vsigs/ Google Cloud Storage file system handler (requires " +"libcurl)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsigs/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Since GDAL 2.2" +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Install /vsigs_streaming/ Google Cloud Storage file system handler " +"(requires libcurl)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsigs_streaming/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Install /vsiaz/ Microsoft Azure Blob file system handler (requires " +"libcurl)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsiaz/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Since GDAL 2.3" +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Install /vsiaz_streaming/ Microsoft Azure Blob file system handler " +"(requires libcurl)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsiaz_streaming/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Install /vsiaz/ Microsoft Azure Data Lake Storage Gen2 file system " +"handler (requires libcurl)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsiadls/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Since GDAL 3.3" +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Install /vsioss/ Alibaba Cloud Object Storage Service (OSS) file system " +"handler (requires libcurl)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsioss/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Install /vsiaz_streaming/ Alibaba Cloud Object Storage Service (OSS) " +"(requires libcurl)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsioss_streaming/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Install /vsiswift/ OpenStack Swif Object Storage (Swift) file system " +"handler (requires libcurl)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsiswift/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Install /vsiswift_streaming/ OpenStack Swif Object Storage (Swift) file " +"system handler (requires libcurl)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsiswift_streaming/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Install /vsi7z/ 7zip file system handler (requires libarchive)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsi7z/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Since GDAL 3.7" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Install /vsirar/ RAR file system handler (requires libarchive)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsirar/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Install GZip file system handler." +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"A special file handler is installed that allows reading on-the-fly and " +"writing in GZip (.gz) files." +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"All portions of the file system underneath the base path \"/vsigzip/\" " +"will be handled by this driver." +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsigzip/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Since GDAL 1.6.0" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Install ZIP file system handler." +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"A special file handler is installed that allows reading on-the-fly in ZIP" +" (.zip) archives." +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"All portions of the file system underneath the base path \"/vsizip/\" " +"will be handled by this driver." +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsizip/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Install /vsistdin/ file system handler." +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"A special file handler is installed that allows reading from the standard" +" input stream." +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"The file operations available are of course limited to Read() and forward" +" Seek() (full seek in the first MB of a file by default)." +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Starting with GDAL 3.6, this limit can be configured either by setting " +"the CPL_VSISTDIN_BUFFER_LIMIT configuration option to a number of bytes " +"(can be -1 for unlimited), or using the \"/vsistdin?buffer_limit=value\" " +"filename." +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsistdin/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"Install /vsiwebhdfs/ WebHDFS (Hadoop File System) REST API file system " +"handler (requires libcurl)" +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsiwebhdfs/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Since GDAL 2.4" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Install /vsistdout/ file system handler." +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"A special file handler is installed that allows writing to the standard " +"output stream." +msgstr "" + +#: ../../<breathe>:-1 +msgid "The file operations available are of course limited to Write()." +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"A variation of this file system exists as the /vsistdout_redirect/ file " +"system handler, where the output function can be defined with " +"VSIStdoutSetRedirection()." +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsistdout/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Install /vsisparse/ virtual file handler." +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsisparse/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Install /vsitar/ file system handler." +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"A special file handler is installed that allows reading on-the-fly in TAR" +" (regular .tar, or compressed .tar.gz/.tgz) archives." +msgstr "" + +#: ../../<breathe>:-1 +msgid "" +"All portions of the file system underneath the base path \"/vsitar/\" " +"will be handled by this driver." +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsitar/ documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Install /vsicached? file system handler." +msgstr "" + +#: ../../<breathe>:-1 +msgid "See /vsicached? documentation" +msgstr "" + +#: ../../<breathe>:-1 +msgid "Since GDAL 3.8.0" +msgstr "" + +#: ../../source/api/cpl.rst:98 +msgid ":ref:`cpl_cpp_api`." +msgstr "" + +#: ../../source/api/cpl_cpp.rst:10 +msgid "Common Portability Library C++ API" +msgstr "" + +#: ../../source/api/cpl_cpp.rst:13 +msgid "cpl_odbc.h" +msgstr "" + +#: ../../source/api/cpl_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/ogrspatialref.rst +msgid "Private Static Functions" +msgstr "" + +#: ../../source/api/cpl_cpp.rst:19 +msgid "cpl_vsi_virtual.h" +msgstr "" + +#: ../../source/api/cpl_cpp.rst +msgid "Variables" +msgstr "" + +#: ../../source/api/cpl_cpp.rst:26 +msgid ":ref:`cpl_api`." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:5 +msgid "Compiling the C# bindings - CMake Scripts" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:7 +msgid "" +"This page describes the primary steps when creating the GDAL/OGR C# " +"binaries from the source using the new CMake scripts." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:9 +#: ../../source/api/csharp/csharp_compile_legacy.rst:9 +msgid "" +"In most cases this is not necessary and it is better to use one of the " +"pre-compiled sources, such as `GisInternals " +"<https://gisinternals.com/>`__ or Conda." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:11 +msgid "" +"You can either build the bindings as part of a full GDAL build - or " +"standalone on top of an existing installation." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:14 +#: ../../source/api/csharp/csharp_compile_legacy.rst:18 +#: ../../source/api/csharp/csharp_compile_legacy.rst:105 +msgid "Requirements" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:16 +#: ../../source/api/csharp/csharp_compile_legacy.rst:20 +#: ../../source/api/csharp/csharp_compile_legacy.rst:107 +msgid "The build environment has the following dependencies:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:18 +msgid "CMake 3.10 or later" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:19 +msgid "the appropriate C++ build environment (i.e. gcc or Visual Studio etc)." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:20 +msgid "SWIG 4" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:21 +msgid ".NET 5.0 or Mono" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:24 +msgid ".NET Build Toolchain" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:26 +msgid "" +"The build scripts can use either .NET 5.0 and :file:`dotnet.exe` or Mono" +" and :file:`msc.exe` to compile the bindings." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:28 +msgid "" +".NET is used for preference if it found on all platforms but the use of " +"Mono can be forced using a command line variable." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:31 +msgid "Building as part of a GDAL Build" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:33 +msgid "The build environment uses the following variables:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:36 +msgid "CSHARP_MONO" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:36 +#: ../../source/api/csharp/csharp_compile_cmake.rst:42 +#: ../../source/api/csharp/csharp_compile_cmake.rst:44 +msgid "Boolean" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:36 +msgid "Forces the use of Mono" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:38 +msgid "CSHARP_LIBRARY_VERSION" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:38 +#: ../../source/api/csharp/csharp_compile_cmake.rst:40 +msgid "String" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:38 +msgid "Set the .NET version for the shared libraries" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:40 +msgid "CSHARP_APPLICATION_VERSION" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:40 +msgid "Set the .NET version for the sample apps" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:42 +msgid "GDAL_CSHARP_ONLY" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:42 +msgid "Build standalone on GDAL binaries" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:44 +msgid "BUILD_CSHARP_BINDINGS" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:44 +msgid "Build the C# bindings DEFAULT ON" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:48 +msgid "Building with .NET" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:50 +msgid "" +"If the build environment has .NET 5.0 installed and GDAL is built, then " +"the c# bindings will be built using .NET by default." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:52 +msgid "" +"The details of building GDAL are documented elsewhere, but there are " +"likely to be variants of the following commands run from the root " +"directory of the gdal repository:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:60 +#: ../../source/api/csharp/csharp_compile_cmake.rst:115 +msgid "" +"The C# bindings and sample apps are installed in the install directory " +"(in the above case that would be `../install`, in the `share/csharp` sub " +"folder. There would be the following files:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:62 +#: ../../source/api/csharp/csharp_compile_cmake.rst:117 +#: ../../source/api/csharp/csharp_compile_legacy.rst:66 +msgid ":file:`gdal_csharp.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:63 +#: ../../source/api/csharp/csharp_compile_cmake.rst:118 +#: ../../source/api/csharp/csharp_compile_legacy.rst:67 +msgid ":file:`ogr_csharp.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:64 +#: ../../source/api/csharp/csharp_compile_cmake.rst:119 +#: ../../source/api/csharp/csharp_compile_legacy.rst:68 +msgid ":file:`osr_csharp.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:65 +#: ../../source/api/csharp/csharp_compile_cmake.rst:120 +#: ../../source/api/csharp/csharp_compile_legacy.rst:69 +msgid ":file:`gdalconst_csharp.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:66 +#: ../../source/api/csharp/csharp_compile_cmake.rst:121 +msgid "" +":file:`gdal_wrap.dll` or :file:`libgdal_wrap.so` or " +":file:`libgdal_wrap.dylib`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:67 +#: ../../source/api/csharp/csharp_compile_cmake.rst:122 +msgid "" +":file:`ogr_wrap.dll` or :file:`libogr_wrap.so` or " +":file:`libogr_wrap.dylib`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:68 +#: ../../source/api/csharp/csharp_compile_cmake.rst:69 +#: ../../source/api/csharp/csharp_compile_cmake.rst:123 +#: ../../source/api/csharp/csharp_compile_cmake.rst:124 +msgid "" +":file:`osr_wrap.dll` or :file:`libosr_wrap.so` or " +":file:`libosr_wrap.dylib`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:70 +#: ../../source/api/csharp/csharp_compile_cmake.rst:125 +msgid "" +":file:`gdalconst_wrap.dll` or :file:`libgdalconst_wrap.so` or " +":file:`libgdalconst_wrap.dylib`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:71 +msgid "" +"various sample applications - as \\*.exe on Windows, or just as \\* on " +"Unix, along with \\*.dll for each app and the runtime config files." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:73 +msgid "" +"There are also subdirectories for each of the sample apps, holding the " +"config files." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:75 +msgid "There are also the following NuGET packages:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:77 +msgid ":file:`OSGeo.GDAL`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:78 +msgid ":file:`OSGeo.OGR`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:79 +msgid ":file:`OSgeo.OSR`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:80 +msgid ":file:`OSGeo.GDAL.CONST`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:81 +msgid "various sample application" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:84 +msgid "Using the .NET Bindings" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:86 +msgid "" +"The easiest way to use the bindings in development would be use the NuGET" +" packages created." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:88 +msgid "" +"To do this you need to add a local repistory pointing to the GDAL install" +" directory. `This is explained here <https://docs.microsoft.com/en-" +"us/nuget/hosting-packages/local-feeds>`__ ." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:90 +msgid "Once this is done, you add the GDAL packages into your project as normal." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:92 +msgid "" +"These packages only install the bindings and do not install core GDAL. It" +" is for you as the developer to make sure that the GDAL binaries are " +"available in the search path." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:95 +msgid "" +"The NuGET packages are created with the same version number as the " +"version of GDAL in the build system. If you are building in a GIT " +"repository, then the build system automatically makes the version with a " +"x.y.z-dev pre-release tag. This means that to load the package into " +"Visual Studio (for instance), you have to tick the pre-release box. This " +"is all intentional and not a bug." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:102 +msgid "Building on Mono" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:104 +msgid "" +"If the build environment does not have .NET 5.0 or msbuild installed and " +"GDAL is built, then the c# bindings will be built using Mono by default. " +"Mono building can also be forced by setting CSHARP_MONO." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:107 +msgid "" +"The details of building GDAL are documented elsewhere, but the there are " +"likely to be variants of the following commands run from the root " +"directory of the gdal repository:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:126 +msgid "various sample applications as \\*.exe on all platforms." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:129 +msgid "Using the Mono Bindings" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:131 +msgid "Note that the bindings created by this process will only work with Mono." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:133 +#: ../../source/api/csharp/csharp_compile_legacy.rst:177 +msgid "" +"To run one of the prebuilt executables - you can run them with Mono as " +"follows :" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:135 +#: ../../source/api/csharp/csharp_compile_legacy.rst:179 +msgid ":program:`mono GDALInfo.exe`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:137 +#: ../../source/api/csharp/csharp_compile_legacy.rst:181 +msgid "" +"Both the managed libraries (i.e. the DLLs) and the unmanaged libraries " +"must be available to Mono. This is in more detail in `the Mono " +"documentation <https://www.mono-project.com/docs/advanced/pinvoke/>`__" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:141 +msgid "Building Standalone" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:143 +msgid "" +"The Bindings using both the .NET or Mono toolchains can be build on top " +"of an existing implementation of GDAL that includes the include files and" +" libs - for instance the Conda distribution." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:146 +msgid "" +"To do this, Cmake must be run with the GDAL_CSHARP_ONLY flag set and only" +" one of the following targets should be built:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:150 +msgid "csharp_binding" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:150 +msgid "Just the bindings" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:152 +msgid "csharp_samples" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:152 +msgid "The bindings and the sample apps" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:155 +msgid "Do not build the install target when running standalone, it will fail!" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:157 +msgid "" +"Do not run a bare ctest command on this build, it will likely fail! Use " +"something like `ctest -R \"^csharp.*\"` instead." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:159 +msgid "As an example:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:166 +msgid "" +"The output from this build is axactly the same as documented as above, " +"except that the outputs will be in `../build/swig/csharp` and some of the" +" sub folders." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:169 +msgid "Signing of build artifacts" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_cmake.rst:171 +msgid "" +"The CSharp assemblies are strong name signed by default with the provided" +" key file in :source_file:`swig/csharp/gdal.snk`. If authenticode signing" +" of the assemblies is wished, it should be done in a post-build manual " +"step, for example with:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:5 +msgid "Compiling the C# bindings - Legacy Scripts" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:7 +msgid "" +"This page describes the primary steps when creating the GDAL/OGR C# " +"binaries from the source." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:12 +msgid "Building on Windows" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:14 +msgid "" +"To building the C# interface, you need a compiled version of the GDAL " +"core. This can be the result of a manual compilation or can be linking to" +" one of the prebuilt binaries. In the former case the following should be" +" run in the clone of the GitHub repository used to build GDAL and the " +"steps to create the environment should not be necessary." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:22 +msgid "nmake / Visual Studio" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:23 +#: ../../source/api/csharp/csharp_compile_legacy.rst:110 +msgid "SWIG 3/4" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:25 +msgid "" +"The `GDAL test scripts " +"<https://github.com/OSGeo/gdal/blob/master/.github/workflows/windows_build.yml>`__" +" use VS 2019 (MSVC Ver 1920) so it would make sense to use the same " +"versions." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:27 +msgid "" +"`SWIG <http://www.swig.org/>`__ is used to build the API bindings. The " +"GDAL test scripts use version 3 and the conda build use version 4. Both " +"Work." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:30 +#: ../../source/api/csharp/csharp_compile_legacy.rst:114 +msgid "Build Environment" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:32 +msgid "" +"You need to set up the build environment. If you are using VS 2019, this " +"might be the command:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:34 +msgid ":program:`VsDevCmd.bat -arch=x64`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:36 +msgid "" +"The :program:`VsDevCmd.bat` command can usually be found in " +":file:`C:\\\\Program Files (x86)\\\\Microsoft Visual " +"Studio\\\\2019\\\\Enterprise\\\\Common7\\\\Tools` or the equivalent for " +"the Community Edition." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:38 +msgid "" +"If you don't want to bother with executing the proper vcvars*.bat you " +"might use the development environment specific command prompt to " +"accomplish this task. When using a Win64 compilation be careful to " +"activate the x64 version of the command prompt installed on your system." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:40 +msgid "" +"If you are not running in an environment that has been used to compile " +"GDAL locally, then there are a number of variables that need to be " +"configured. The Conda ``gdal-feedstock`` configuration app can be used as" +" a guideline about how to do that - `build.bat <https://github.com/conda-" +"forge/gdal-feedstock/blob/master/recipe/set_bld_opts.bat>`__." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:43 +#: ../../source/api/csharp/csharp_compile_legacy.rst:121 +msgid "Creating the SWIG interface code" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:45 +msgid "" +"The first step is to generate the SWIG interface code. This will create a" +" set of ``.cs`` definitions that will be compiled into the ``.dll`` files" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:47 +msgid "" +"To create the interface execute the following command (from the " +"``swig\\csharp`` directory):" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:53 +msgid "" +"You should edit nmake.opt adding the actual location of the " +":file:`swig.exe` file." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:56 +#: ../../source/api/csharp/csharp_compile_legacy.rst:134 +msgid "Compiling the code" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:58 +msgid "" +"After creating the interface the code can be compiled using this command " +"(from the ``swig\\csharp`` directory):" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:64 +#: ../../source/api/csharp/csharp_compile_legacy.rst:142 +msgid "Upon a successful compilation the following files are created:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:70 +msgid ":file:`gdal_wrap.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:71 +msgid ":file:`ogr_wrap.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:72 +msgid ":file:`osr_wrap.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:73 +msgid ":file:`gdalconst_wrap.dll`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:74 +msgid "various sample applications" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:76 +msgid "" +"The :file:`\\*_csharp.dll` binaries are the managed part of the " +"interface. You should add a reference to these assemblies for using the " +"classes of the interface. These :file:`\\*_csharp.dll` files will load " +"the corresponding :file:`\\*_wrap.dll` files, which are the unmanaged " +"part of the interface hosting the code of the gdal core." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:79 +#: ../../source/api/csharp/csharp_compile_legacy.rst:160 +msgid "Testing the successful compilation" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:81 +#: ../../source/api/csharp/csharp_compile_legacy.rst:162 +msgid "To test the compiled binaries, you can use:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:87 +#: ../../source/api/csharp/csharp_compile_legacy.rst:168 +msgid "This command will invoke some of the sample applications." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:89 +msgid "" +"For the tests to work the location of the proj and gdal DLLs should be " +"available in the PATH." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:92 +msgid "Using MONO on Windows" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:94 +msgid "" +"If you have the Windows version of the MONO package installed you can " +"compile the C# code using the MONO compiler. In this case uncomment the " +"following entry in csharp.opt:" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:96 +msgid ":program:`MONO = YES`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:98 +msgid "mcs.exe must be in the PATH." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:102 +msgid "Building on Linux/OSX" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:109 +msgid "make" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:111 +msgid "mono (probably any reasonable version)" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:116 +msgid "" +"The build environment needs to be correctly configured. If you are not " +"running in an environment that has been used to locally build GDAL then " +"you should run the :program:`configure` command from the GDAL root " +"directory." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:118 +msgid "" +"The conda gdal-feedstock recipe provides an example of how to do that - " +"`build.sh <https://github.com/conda-forge/gdal-" +"feedstock/blob/master/recipe/build.sh>`__" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:123 +msgid "" +"The first step is to generate the SWIG interface code. This will create a" +" set of :file:`.cs` definitions that will be compiled into the " +":file:`.dll` files" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:125 +msgid "" +"To create the interface execute the following command (from the " +":file:`swig/ csharp` directory):" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:131 +msgid "" +"In versions of GDAL < 3.3.0 - this command will create incorrect " +"interfaces without the correct namespace. See `#3670 " +"<https://github.com/OSGeo/gdal/pull/3670/commits/777c9d0e86602740199cf9a4ab44e040c52c2283>`__." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:136 +msgid "" +"After creating the interface the code can be compiled using this command " +"(from the :file:`swig/csharp` directory):" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:144 +msgid ":file:`gdal_csharp.dll` and :file:`gdal_csharp.dll.config`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:145 +msgid ":file:`ogr_csharp.dll` and :file:`ogr_csharp.dll.config`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:146 +msgid ":file:`osr_csharp.dll` and :file:`osr_csharp.dll.config`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:147 +msgid ":file:`gdalconst_csharp.dll` and :file:`gdalconst_csharp.dll.config`" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:148 +msgid ":file:`libgdalcsharp.so / .dylib` etc" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:149 +msgid ":file:`libogrcsharp.so / .dylib` etc" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:150 +msgid ":file:`libosrcsharp.so / .dylib` etc" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:151 +msgid ":file:`libgdalconst_wrap.so / .dylib` etc" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:152 +msgid "various sample applications (:file:`\\*.exe`)" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:154 +msgid "" +"The :file:`\\*_csharp.dll` binaries are the managed part of the " +"interface. You should add a reference to these assemblies for using the " +"classes of the interface." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:156 +msgid "" +"The :file:`\\*_csharp.dll` files will try to load the corresponding " +":file:`\\*_wrap.dll` and are redirected to the :file:`libxxxcsharp.\\*` " +"libraries, which are the unmanaged part of the interface hosting the code" +" of the gdal core, by the :file:`\\*.dll.config` definitions." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:170 +msgid "" +"For the tests to work the location of the proj and gdal libraries should " +"be available in the PATH." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:173 +msgid "Using The Bindings on Unix" +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:175 +msgid "" +"Note that the bindings created by this process will only work with Mono " +"at the moment." +msgstr "" + +#: ../../source/api/csharp/csharp_compile_legacy.rst:184 +msgid "" +"This document was amended from the previous version at " +"`https://trac.osgeo.org/gdal/wiki/GdalOgrCsharpCompile " +"<https://trac.osgeo.org/gdal/wiki/GdalOgrCsharpCompile>`__" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:5 +msgid "C# Bindings Conda Package" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:7 +msgid "The GDAL C# Bindings Conda Package is a community supported project." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:10 +#: ../../source/api/python_bindings.rst:22 +msgid "Installation" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:12 +msgid "GDAL with the C# bindings and example applications can be loaded using" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:19 +#: ../../source/api/csharp/csharp_conda.rst:51 +#: ../../source/api/python_bindings.rst:117 +msgid "Usage" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:21 +msgid "" +"The Conda package for GDAL version 3.5.0 and later uses the CMAKE build " +"scripts and therefore there have been changes in the build process and " +"the artifacts produced." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:23 +msgid ":ref:`csharp_conda_35`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:25 +msgid ":ref:`csharp_conda_34`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:32 +msgid "GDAL 3.5.0 and later" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:34 +msgid "" +"The Conda package for GDAL version 3.5.0 and later is built using the new" +" Cmake build scripts." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:37 +msgid ".NET Target Framework" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:39 +msgid "" +"On all architectures (i.e. Windows, Linux and Mac), the bindings are " +"compiled using .NET6.0 as the current (at the time of writing) LTS " +"version." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:42 +msgid "Package Artifacts" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:44 +msgid "The Conda package contains two sets of artifacts:" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:46 +msgid "" +"The SWIG wrapper Dynamic Shared Objects (DSO) - :file:`gdal_wrap.dll` or " +":file:`libgdal_wrap.so` or :file:`libgdal_wrap.dylib` etc. These are " +"loaded as one would expect for a Conda package (i.e. in the :file:`bin` " +"folder in Windows and the :file:`lib` folder in Unix) and thus will " +"automatically link to the correct version of the GDAL DSO and the " +"dependencies, and" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:48 +msgid "" +"Local NuGet packages for the actual C# bindings (i.e. " +":file:`gdal_csharp.dll`, :file:`gdalconst_csharp.dll`, " +":file:`osr_csharp.dll` and :file:`ogr_csharp.dll`). These are created as " +"packages called :file:`OSGeo.GDAL`, :file:`OSGeo.OSR` and " +":file:`OSGeo.OGR`. These are loaded into the :file:`share/gdal` folder." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:53 +msgid "" +"To use the bindings in your application, you will need to basically do " +"the following:" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:55 +msgid "Add the relevant Packages to you application as local packages, and" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:56 +msgid "Add the DSOs to the search path for the application." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:58 +msgid "" +"The former is not complicated and can be done by defining a local source," +" either global (as `is explained here <https://docs.microsoft.com/en-" +"us/nuget/hosting-packages/local-feeds>`__ ) or in the build command as is" +" shown below." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:60 +msgid "" +"The latter can be based on Conda for a console application, as is shown " +"below, but if you are working in an IDE (which being a .NET IDE knows " +"nothing about Conda) and/or working on a GUI application (which is not " +"going to be running in a Conda environment) you are going to have to sort" +" out the DSOs your self; probably involving copying the relevant DSOs " +"into the application package." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:63 +msgid "Usage Example - Windows" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:65 +msgid "The most simple example would be:" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:67 +#: ../../source/api/csharp/csharp_conda.rst:104 +msgid "Create a new application (in a dedicated empty folder)" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:69 +#: ../../source/api/csharp/csharp_conda.rst:106 +msgid ":program:`dotnet new console`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:71 +#: ../../source/api/csharp/csharp_conda.rst:108 +msgid "" +"Create a small application (by replacing the contents of " +":file:`Program.cs`)." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:91 +#: ../../source/api/csharp/csharp_conda.rst:128 +msgid "Add the GDAL package" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:93 +msgid "" +":program:`dotnet add package OSGeo.GDAL -s " +"%CONDA_PREFIX%\\\\Library\\\\share\\\\gdal`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:95 +#: ../../source/api/csharp/csharp_conda.rst:132 +msgid "Compile or run" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:97 +#: ../../source/api/csharp/csharp_conda.rst:134 +msgid ":program:`dotnet run`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:99 +msgid "" +"Provided you run these commands in a Conda environment (containing the " +"gdal-csharp package) this should just work." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:102 +msgid "Usage Example - Unix" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:130 +msgid ":program:`dotnet add package OSGeo.GDAL -s $CONDA_PREFIX/share/gdal`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:136 +msgid "" +"This will not just work under Unix since, unlike Windows, the Library " +"Search Path is separate from the Process Search path and is not set by " +"Conda." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:138 +msgid "" +"To make this work, you will probably have to change the Library search " +"path, which is ok for development but should not be accepted for " +"production (which means that you will need to copy the DSOs to the " +"application search path)." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:140 +msgid "Under Linux:" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:142 +msgid ":program:`export LD_LIBRARY_PATH=$CONDA_PREFIX/lib`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:144 +msgid "Under OSX:" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:146 +msgid ":program:`export DYLD_LIBRARY_PATH=$CONDA_PREFIX/lib`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:153 +msgid "GDAL 3.4.x and earlier" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:156 +msgid "Windows" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:158 +msgid "" +"You can test if the C# bindings are working in a Conda environment by " +"running :program:`%CONDA_PREFIX%\\\\Library\\\\bin\\\\gcs\\\\gdal_test`." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:160 +msgid "" +"The DLLs are loaded into the :file:`%CONDA_PREFIX%\\\\Library\\\\bin` " +"folder, as is normal for a Conda environment." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:162 +msgid "" +"The C# sample .EXEs are loaded into " +":file:`%CONDA_PREFIX%\\\\Library\\\\bin\\\\gcs`, because otherwise they " +"over write the standard GDAL tools." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:164 +msgid "" +"To run a sample application - eg GDALinfo.exe - add " +":file:`%CONDA_PREFIX%\\\\Library\\\\bin\\\\gcs` to the path and just run " +":program:`gdalinfo`." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:166 +msgid "" +"To link the DLLs into your code, you will need to include the DLLs into " +"the project (which will almost certainly mean copying them to the project" +" directory)." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:168 +msgid "" +"For a console app that is run from within the Conda environment (i.e. run" +" :program:`conda activate`) then they should work once compiled." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:170 +msgid "" +"For GUI apps or other apps that cannot be run from with the Conda " +"environment then you will have to setup the environment to make the GDAL " +"DLLs available to the app." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:174 +msgid "Mac / Linux" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:176 +msgid "" +"You test if the C# bindings are working in a Conda environment by running" +" :program:`mono $CONDA_PREFIX/lib/gdal_test.exe`" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:178 +msgid "" +"The shared objects (i.e. :file:`\\*.so` / :file:`\\*.dylib`), the .EXE " +"and .DLL files are all loaded into the :file:`$CONDA_PREFIX/lib` folder " +"(not the :file:`bin` folder as you might expect). This is in line with " +"`the Mono documentation <https://www.mono-project.com/docs/getting-" +"started/application-deployment/>`__." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:181 +msgid "" +"To run one of the sample applications (e.g. :file:`GDALinfo.exe`), run " +":program:`mono $CONDA_PREFIX/lib/GDALinfo.exe`." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:183 +msgid "" +"To build a console app in Mono, you can do this in a conda environment " +"simple using a command similar to this (changing the source name to your " +"own):" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:189 +msgid "" +"If the compiled executable is run in the conda environment, this should " +"work. For something more portable or a GUI app, then you have to work out" +" the dependencies your self." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:191 +msgid "" +"The DLLs can also be used in a .NET project, for instance built in VS. " +"Just link the DLLs in as dependencies." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:194 +msgid "Differences in the Conda build" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:196 +msgid "" +"The Conda build is in some ways different from the \"standard\" GDAL " +"3.4.x build:" +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:198 +msgid "" +"On Mac and Linux, the SWIG files are built as :file:`\\*_wrap` in line " +"with the windows versions. This means that there are no :file:`.config` " +"files. Most importantly, this means that the DLLs can be used in .NET and" +" Unity projects as well as Mono." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:199 +msgid "On Windows, the sample apps are built in .NET5 and not .NET CORE 2.1." +msgstr "" + +#: ../../source/api/csharp/csharp_conda.rst:201 +msgid "These changes anticipated the standard build for GDAL 3.5.x." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:5 +msgid "C# Raster Interface" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:7 +msgid "" +"The GDAL C# interface supports transferring raster data between the C# " +"application and GDAL." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:9 +msgid "" +"The various :file:`Band.ReadRaster`, :file:`Band.WriteRaster`, " +":file:`Dataset.ReadRaster`, :file:`Dataset.WriteRaster` overloads are " +"involved in transferring raster data between the managed and the " +"unmanaged parts of the application." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:12 +msgid "" +"This page will summarize the main aspects of raster data handling related" +" exclusively to the C# interface." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:14 +msgid "" +"The :file:`Band` class contains the following " +":file:`ReadRaster`/:file:`WriteRaster` overloads:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:54 +msgid "" +"The only difference between these functions is the actual type of the " +"buffer parameter. The last 2 overloads are the generic overloads and the " +"caller should write the proper marshaling code for the buffer holding the" +" raster data. The overloads that have a C# array as the buffer parameter " +"implement the proper marshaling code for the caller." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:60 +msgid "Reading the raster image" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:62 +msgid "" +"When reading raster data from GDAL, the user will probably create a .NET " +"image to hold C# representation of the data. The raster data can be read " +"directly or in a buffered fashion." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:66 +msgid "Using the buffered read approach" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:68 +msgid "" +"When reading the image this way the C# API will copy the image data " +"between the C and the C# arrays:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:88 +msgid "" +"In this case the interface implementation uses an internally created " +"unmanaged array to transfer the data between the C and C++ part of the " +"code, like:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:106 +msgid "Using the direct read approach" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:108 +msgid "" +"Raster data can be read into the C# bitmap directly using the following " +"approach:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:127 +msgid "" +"This approach is more performant than the previous since there's no need " +"to allocate an intermediary array for transferring the data." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:130 +msgid "Using /unsafe code and the fixed statement" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:132 +msgid "" +"In the previous examples the programmer could ignore bothering with " +"implementing the marshaling code for the raster arrays. Both of the " +"examples prevent the garbage collector from relocating the array during " +"the execution of the P/Invoke call. Without using an intermediary array " +"the programmer can also use the following method to read the raster data:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:143 +msgid "" +"When using this approach the application must be compiled using the " +":program:`/unsafe` command line option." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:146 +msgid "Using indexed / grayscale images" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:148 +msgid "" +"The :file:`PaletteInterp` enumeration can be used to distinguish between " +"the various type of the image color interpretations." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:159 +msgid "" +"When reading images with indexed color representations, the programmer " +"might have to do some extra work copying the palette over:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:192 +msgid "" +"When reading grayscale images, the programmer should create a sufficient " +"palette for the .NET image." +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:220 +#: ../../source/api/csharp/csharp_vector.rst:212 +msgid "Related C# examples" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:222 +msgid "" +"The following examples demonstrate the usage of the GDAL raster " +"operations mentioned previously:" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:224 +msgid ":source_file:`swig/csharp/apps/GDALRead.cs`" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:225 +#: ../../source/api/csharp/csharp_raster.rst:226 +msgid ":source_file:`swig/csharp/apps/GDALReadDirect.cs`" +msgstr "" + +#: ../../source/api/csharp/csharp_raster.rst:228 +msgid "" +"This document was amended from the previous version at " +"`https://trac.osgeo.org/gdal/wiki/GdalOgrCsharpRaster " +"<https://trac.osgeo.org/gdal/wiki/GdalOgrCsharpRaster>`__" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:5 +msgid "C# Bindings Usage Advice" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:8 +msgid "Adding reference to the GDAL/OGR assemblies" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:10 +#: ../../source/api/csharp/csharp_usage.rst:15 +msgid "TODO" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:13 +msgid "Using the interface classes" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:19 +msgid "Modifying Local Search Path" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:22 +msgid "" +"If you want to add a folder to PATH during run-time, so you don't have to" +" pollute system PATH permanently, you can do it this way, in C#" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:43 +msgid "MSDN documentation:" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:45 +msgid "" +"`http://msdn2.microsoft.com/en-us/library/ms686206.aspx " +"<http://msdn2.microsoft.com/en-us/library/ms686206.aspx>`__" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:46 +msgid "" +"`http://msdn2.microsoft.com/en-" +"us/library/system.environment.setenvironmentvariable.aspx " +"<http://msdn2.microsoft.com/en-" +"us/library/system.environment.setenvironmentvariable.aspx>`__" +msgstr "" + +#: ../../source/api/csharp/csharp_usage.rst:48 +msgid "" +"Instead of the P/Invoke call to :program:`SetEnvironmentVariable()`, you " +"can use C# native method :program:`Environment.SetEnvironmentVariable()`." +" Read the doc carefully, because there are two versions of this method. " +"Unlike the Win32 API call accessed through P/Invoke, the method " +":program:`Environment.SetEnvironmentVariable()` has an overload that " +"*may* change environment permanently, across processes." +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:5 +msgid "C# Vector and Spatial Reference Interfaces" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:8 +msgid "Basic Architecture" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:10 +msgid "" +"The vector interface is within the :file:`OSGeo.OGR` namespace and the " +"spatial reference interface is within the :file:`OSGeo.OSR` namespace." +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:12 +msgid "The **main** classes are as follows" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:35 +msgid "Accessing Feature Geometries" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:37 +msgid "" +"The basic process is :file:`DataSource` => :file:`Layer` => " +":file:`Feature` => :file:`Geometry`" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:40 +msgid "Open a DataSource" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:42 +msgid "" +"A :file:`DataSource` wraps a OGR source (e.g a filename) and is created " +"as follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:63 +msgid "Access the Layers" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:65 +msgid "" +"Each :file:`DataSource` will have one or more layers that can be iterated" +" as follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:85 +msgid "Access a Layer's Features" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:87 +msgid "" +"Each :file:`Layer` can have zero or more :file:`Feature` s. These should " +"be accessed as follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:100 +msgid "Access a Features's Geometry" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:107 +msgid ":file:`Geometry` objects are nested - so for instance:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:109 +msgid "" +"a :file:`Geometry` of type :file:`wkbGeometryType.wkbTIN` has multiple " +"daughter :file:`Geometry` objects of type " +":file:`wkbGeometryType.wkbTriangle`," +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:110 +msgid "" +"each :file:`Geometry` object of type :file:`wkbGeometryType.wkbTriangle` " +"has a daughter :file:`Geometry` object of type " +":file:`wkbGeometryType.LinearRing`," +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:111 +msgid "" +"each :file:`Geometry` of type :file:`wkbGeometryType.LinearRing` contains" +" a number of points." +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:113 +msgid "" +"When you get to the most basic type - which usually seems to be " +":file:`wkbGeometryType.wkbPoint`, :file:`wkbGeometryType.wkbLineString` " +"or :file:`wkbGeometryType.wkbLinearRing` or their multi- versions or 25D " +"or ZM versions, you can access the point coordinates as follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:126 +msgid "" +"The size of the :file:`double[]` depends on the number of dimensions of " +"the :file:`Geometry`." +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:129 +msgid "Access a Feature's data fields" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:131 +msgid "" +"Each :file:`Feature` object can have a number of data fields associated. " +"The schema for the data fields is defined in a :file:`FieldDefn` object. " +"The fields can be fetched a follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:162 +msgid "Access a Geometry's CRS" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:164 +msgid "" +"If there is a CRS (aka SRS) defined for the :file:`Geometry` it can be " +"retrieved as follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:170 +msgid "" +"The :file:`SpatialReference` is the main class for representing the CRS /" +" projection. The CRS can be turned into a WKT string, e.g. for display " +"purposes, as follows:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:178 +msgid "" +"Sometimes the CRS defined on the layer does not cascade down to the " +"Feature - you need to refer bak to the Layer" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:182 +msgid "Reproject a Geometry" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:184 +msgid "" +"If the :file:`Geometry` has a valid :file:`SpatialReference` defined, " +"then the :file:`Geometry` can be transformed to a new CRS using this " +"command:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:192 +msgid "" +"However, often it is better to explicitly define the " +":file:`CoordinateTransform` to be used" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:214 +msgid "" +"The following examples demonstrate the usage of the OGR vector operations" +" mentioned above:" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:216 +msgid ":source_file:`swig/csharp/apps/ogrinfo.cs`" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:217 +msgid ":source_file:`swig/csharp/apps/OGRLayerAlg.cs`" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:218 +msgid ":source_file:`swig/csharp/apps/OGRFeatureEdit.cs`" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:219 +msgid ":source_file:`swig/csharp/apps/OSRTransform.cs`" +msgstr "" + +#: ../../source/api/csharp/csharp_vector.rst:220 +msgid ":source_file:`swig/csharp/apps/GetCRSInfo.cs`" +msgstr "" + +#: ../../source/api/csharp/index.rst:5 +msgid "C# bindings" +msgstr "" + +#: ../../source/api/csharp/index.rst:7 +msgid "" +"The GDAL project (primarily Tamas Szekeres) maintains SWIG generated C# " +"bindings for GDAL and OGR." +msgstr "" + +#: ../../source/api/csharp/index.rst:9 +msgid "" +"Generally speaking the classes and methods mostly match those of the GDAL" +" and OGR C++ classes, but there is currently no C# specific documentation" +" beyond this site." +msgstr "" + +#: ../../source/api/csharp/index.rst:11 +msgid "The C# bindings are also usable from other .NET languages, such as VB.Net." +msgstr "" + +#: ../../source/api/csharp/index.rst:13 +msgid "" +"The C# interface has been built upon the same libraries as the other SWIG" +" generated wrappers (like Python, Java). Therefore, the class names, " +"class member names, and the method signatures are driven by the GDAL+SWIG" +" conventions and might not follow the conventional .NET naming " +"guidelines. However, one can easily identify the matching members in the " +"GDAL/OGR API documentation." +msgstr "" + +#: ../../source/api/csharp/index.rst:17 +msgid "" +"The GDAL/OGR C# classes use the .NET P/Invoke mechanism for the " +"communication between the managed and unmanaged code. Every class " +"implements the IDisposable interface to control the finalization of the " +"underlying unmanaged memory referenced by every the wrapper class." +msgstr "" + +#: ../../source/api/csharp/index.rst:21 +msgid "Supported platforms" +msgstr "" + +#: ../../source/api/csharp/index.rst:23 +msgid "Currently the interface is compilable on and supports:" +msgstr "" + +#: ../../source/api/csharp/index.rst:25 +msgid "" +"the various Win32 and Win64 platforms targeting the Microsoft.NET and the" +" MONO frameworks," +msgstr "" + +#: ../../source/api/csharp/index.rst:26 +msgid "GNU Linux/OSX systems using the MONO framework, and" +msgstr "" + +#: ../../source/api/csharp/index.rst:27 +msgid "" +"Unity systems on Windows, OSX and Linux (currently only the MONO " +"framework and not IL2CPP)." +msgstr "" + +#: ../../source/api/csharp/index.rst:30 +msgid "Getting GDAL for C#" +msgstr "" + +#: ../../source/api/csharp/index.rst:32 +msgid "" +"There are a number of ways to get the C# bindings, including but not " +"limited to:" +msgstr "" + +#: ../../source/api/csharp/index.rst:34 +msgid "" +"The `gisinternals <http://www.gisinternals.com/sdk>`__ site, see below " +"under \"Windows Build SDK\"," +msgstr "" + +#: ../../source/api/csharp/index.rst:35 +msgid "" +"The `Conda package <https://anaconda.org/conda-forge/gdal-csharp>`__, see" +" instructions below" +msgstr "" + +#: ../../source/api/csharp/index.rst:36 +msgid "The gdal.netcore NuGet package, see link below, and" +msgstr "" + +#: ../../source/api/csharp/index.rst:37 +msgid "" +"For Unity, there is a UPM package that installs GDAL, `available from " +"here <https://openupm.com/packages/com.virgis.gdal/?subPage=readme>`__ " +"(available on Windows, Mac and Linux)" +msgstr "" + +#: ../../source/api/csharp/index.rst:39 +msgid "(all of these are community supported)" +msgstr "" + +#: ../../source/api/csharp/index.rst:43 +msgid "Related Documents" +msgstr "" + +#: ../../source/api/csharp/index.rst:56 ../../source/api/java/index.rst:69 +msgid "Useful Links" +msgstr "" + +#: ../../source/api/csharp/index.rst:58 +msgid "" +"A variety of example programs in CSharp are available at the " +"`/swig/csharp/apps " +"<https://github.com/OSGeo/gdal/tree/master/swig/csharp/apps>`__ folder of" +" the GDAL project tree." +msgstr "" + +#: ../../source/api/csharp/index.rst:60 +msgid "The Conda Feedstock" +msgstr "" + +#: ../../source/api/csharp/index.rst:62 +msgid "" +"A simple (as is) build engine of GDAL 3.2 library for .NET Core. `MaxRev-" +"Dev/gdal.netcore <https://github.com/MaxRev-Dev/gdal.netcore>`__" +msgstr "" + +#: ../../source/api/csharp/index.rst:64 +msgid "" +"The `ViRGiS project <https://www.virgis.org/>`__ makes extensive use of " +"GDAL in c# in a Unity environment." +msgstr "" + +#: ../../source/api/csharp/index.rst:66 +msgid "(Please add your project to this section)" +msgstr "" + +#: ../../source/api/csharp/index.rst:70 +msgid "Windows Build SDKs" +msgstr "" + +#: ../../source/api/csharp/index.rst:72 +msgid "" +"Tamas Szekeres maintains `build SDK packages " +"<http://www.gisinternals.com/sdk>`__ in order to compile GDAL from the " +"sources on Windows. The build system provides daily build binary packages" +" for the latest stable and development versions." +msgstr "" + +#: ../../source/api/gdal_alg.rst:10 +msgid "gdal_alg.h: GDAL Algorithms C API" +msgstr "" + +#: ../../source/api/gdal_alg.rst:13 +msgid "gdal_alg.h" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param pTransformerArg" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param bDstToSrc" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param nPointCount" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param x" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param y" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param z" +msgstr "" + +#: ../../source/api/gdal_alg.rst +msgid "Param panSuccess" +msgstr "" + +#: ../../source/api/gdal_utils.rst:10 +msgid "gdal_utils.h: GDAL Algorithms C API" +msgstr "" + +#: ../../source/api/gdalabstractmdarray_cpp.rst:10 +msgid "GDALAbstractMDArray C++ API" +msgstr "" + +#: ../../source/api/gdalabstractmdarray_cpp.rst +msgid "Param array" +msgstr "" + +#: ../../source/api/gdalabstractmdarray_cpp.rst +msgid "Param chunkArrayStartIdx" +msgstr "" + +#: ../../source/api/gdalabstractmdarray_cpp.rst +msgid "Param chunkCount" +msgstr "" + +#: ../../source/api/gdalabstractmdarray_cpp.rst +msgid "Param iCurChunk" +msgstr "" + +#: ../../source/api/gdalabstractmdarray_cpp.rst +msgid "Param nChunkCount" +msgstr "" + +#: ../../source/api/gdalattribute_cpp.rst:10 +msgid "GDALAttribute C++ API" +msgstr "" + +#: ../../source/api/gdalattribute_cpp.rst:13 +msgid "GDALAttribute class" +msgstr "" + +#: ../../source/api/gdalattribute_cpp.rst:20 +msgid "GDALIHasAttribute interface" +msgstr "" + +#: ../../source/api/gdaldataset_cpp.rst:10 +msgid "GDALDataset C++ API" +msgstr "" + +#: ../../source/api/gdaldimension_cpp.rst:10 +msgid "GDALDimension C++ API" +msgstr "" + +#: ../../source/api/gdaldriver_cpp.rst:10 +msgid "GDALDriver C++ API" +msgstr "" + +#: ../../source/api/gdaldriver_cpp.rst:13 +msgid "GDALDriver class" +msgstr "" + +#: ../../source/api/gdaldriver_cpp.rst:20 +msgid "GDALDriverManager class" +msgstr "" + +#: ../../source/api/gdalextendeddatatype_cpp.rst:10 +msgid "GDALExtendedDataType C++ API" +msgstr "" + +#: ../../source/api/gdalextendeddatatype_cpp.rst:13 +msgid "GDALExtendedDataType class" +msgstr "" + +#: ../../source/api/gdalextendeddatatype_cpp.rst:20 +msgid "GDALEDTComponent class" +msgstr "" + +#: ../../source/api/gdalgroup_cpp.rst:10 +msgid "GDALGroup C++ API" +msgstr "" + +#: ../../source/api/gdalmdarray_cpp.rst:10 +msgid "GDALMDArray C++ API" +msgstr "" + +#: ../../source/api/gdalrasterband_cpp.rst:10 +msgid "GDALRasterBand C++ API" +msgstr "" + +#: ../../source/api/gdalrasterband_cpp.rst ../../source/api/gdalwarp_cpp.rst +#: ../../source/api/gnm_cpp.rst +msgid "Protected Functions" +msgstr "" + +#: ../../source/api/gdalwarp_cpp.rst:10 +msgid "Warper C++ API" +msgstr "" + +#: ../../source/api/gdalwarp_cpp.rst +msgid "Friends" +msgstr "" + +#: ../../source/api/gnm_cpp.rst:10 +msgid "Geographic Network C++ API" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Go" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Julia" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Lua" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Original Node.js bindings" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Node.js fork with full Promise-based async and TypeScript support" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Perl" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "PHP" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "R" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Ruby" +msgstr "" + +#: ../../source/api/index.rst:115 +msgid "Rust" +msgstr "" + +#: ../../source/api/index.rst:136 +msgid "Fiona" +msgstr "" + +#: ../../source/api/index.rst:136 +msgid "Rasterio" +msgstr "" + +#: ../../source/api/index.rst:144 +msgid "Godal" +msgstr "" + +#: ../../source/api/index.rst:5 ../../source/api/python_bindings.rst:133 +msgid "API" +msgstr "" + +#: ../../source/api/index.rst:10 +msgid "`Full Doxygen output <../doxygen/index.html>`_" +msgstr "" + +#: ../../source/api/index.rst:13 +msgid "C API" +msgstr "" + +#: ../../source/api/index.rst:26 +msgid "C++ API" +msgstr "" + +#: ../../source/api/index.rst:29 +msgid "Raster API" +msgstr "" + +#: ../../source/api/index.rst:40 +msgid "Vector API" +msgstr "" + +#: ../../source/api/index.rst:51 +msgid "Spatial reference system API" +msgstr "" + +#: ../../source/api/index.rst:59 +msgid "Multi-dimensional array API" +msgstr "" + +#: ../../source/api/index.rst:72 +msgid "Miscellaneous C++ API" +msgstr "" + +#: ../../source/api/index.rst:81 +msgid "Python API" +msgstr "" + +#: ../../source/api/index.rst:99 +msgid "`Java API <../java/index.html>`_" +msgstr "" + +#: ../../source/api/index.rst:103 +msgid "GDAL/OGR In Other Languages" +msgstr "" + +#: ../../source/api/index.rst:105 +msgid "" +"There is a set of generic `SWIG <http://www.swig.org/>`__ interface files" +" in the GDAL source tree (subdirectory swig) and a set of language " +"bindings based on those. Currently active ones are:" +msgstr "" + +#: ../../source/api/index.rst:113 +msgid "" +"There are also other bindings that are developed outside of the GDAL " +"source tree (**note**: those offer APIs not strictly coupled to the " +"GDAL/OGR C/C++ API). These include bindings for" +msgstr "" + +#: ../../source/api/index.rst:130 +msgid "" +"For Perl, since GDAL 3.5 the link `Perl " +"<https://trac.osgeo.org/gdal/wiki/GdalOgrInPerl>`__ is deprecated, use " +"above link instead." +msgstr "" + +#: ../../source/api/index.rst:134 +msgid "There are also more Pythonic ways of using the vector/OGR functions with" +msgstr "" + +#: ../../source/api/index.rst:142 +msgid "There is a more idiomatic Golang way of using the raster functions with" +msgstr "" + +#: ../../source/api/index.rst:151 +msgid "" +"API is omitted in this PDF document. You can consult it on " +"https://gdal.org/api/index.html" +msgstr "" + +#: ../../source/api/java/index.rst:5 +msgid "Java bindings" +msgstr "" + +#: ../../source/api/java/index.rst:7 +msgid "The GDAL project has SWIG generated Java bindings for GDAL and OGR." +msgstr "" + +#: ../../source/api/java/index.rst:9 +msgid "" +"Generally speaking the classes and methods mostly match those of the GDAL" +" and OGR C++ classes. You can find the `​Javadoc " +"<http://gdal.org/java>`__ of the API of the Java bindings." +msgstr "" + +#: ../../source/api/java/index.rst:11 +msgid "" +"Due to the fact the Java garbage collector works in a separate thread " +"from the main thread, it is necessary to configure GDAL with multi-" +"threading support, even if you do not use GDAL API from several Java " +"threads." +msgstr "" + +#: ../../source/api/java/index.rst:14 +msgid "How to build bindings" +msgstr "" + +#: ../../source/api/java/index.rst:16 +msgid "" +"Please consult the CMake :ref:`building_from_source_java` paragraph for " +"CMake options controlling how to enable the Java bindings and where to " +"install its artifacts" +msgstr "" + +#: ../../source/api/java/index.rst:21 +msgid "How to use the bindings" +msgstr "" + +#: ../../source/api/java/index.rst:23 +msgid "" +"The result of the build of the Java bindings will be both a " +":file:`gdal.jar` and a companion :file:`libgdalalljni.so` / " +":file:`libgdalalljni.dylib` / :file:`gdalalljni.dll` native library. To " +"limit potential compatibility problems, you should ensure that gdal.jar " +"and gdalalljni come from the same GDAL sources." +msgstr "" + +#: ../../source/api/java/index.rst:28 +msgid "" +"The native gdalalljni library, as well as the core libgdal library (and " +"its dependencies) should be accessible through the mechanism of the " +"operating system to locate shared libraries. Typically on Linux, this " +"means that the path to those libraries should be set in the " +"``LD_LIBRARY_PATH`` environment variable (or in :file:`/etc/ld.so.conf`)." +" On MacOSX, it should be in the ``DYLD_LIBRARY_PATH`` environment " +"variable. And on Windows, in the ``PATH`` environment variable." +msgstr "" + +#: ../../source/api/java/index.rst:36 +msgid "" +"For example, to test on Linux that the bindings are working, you can " +"lanch, from the build directory:" +msgstr "" + +#: ../../source/api/java/index.rst:44 +msgid "On Windows:" +msgstr "" + +#: ../../source/api/java/index.rst:53 +msgid "Maven Users" +msgstr "" + +#: ../../source/api/java/index.rst:55 +msgid "" +"The Java bindings are available from the ​`Maven Central " +"<http://search.maven.org/>`__ repository. All that is needed is to " +"declare a dependency." +msgstr "" + +#: ../../source/api/java/index.rst:71 +msgid "​`Javadoc <http://gdal.org/java>`__ of the API of the Java bindings." +msgstr "" + +#: ../../source/api/java/index.rst:72 +msgid "" +"`gdalinfo.java " +"<https://github.com/OSGeo/gdal/tree/master/swig/java/apps/gdalinfo.java>`__" +" Sample Java program similar to gdalinfo utility." +msgstr "" + +#: ../../source/api/java/index.rst:73 +msgid "" +"`All Java sample programs " +"<https://github.com/OSGeo/gdal/tree/master/swig/java/apps/>`__" +msgstr "" + +#: ../../source/api/java/index.rst:74 +msgid "" +"`Tamas Szekeres' Windows daily builds " +"<http://www.gisinternals.com/sdk>`__ : Tamas Szekeres maintains a " +"complete set of Win32 and Win64 binary packages that include the GDAL " +"Java bindings. These packages are based on the current development and " +"stable branches built from the GDAL source repository." +msgstr "" + +#: ../../source/api/java/index.rst:75 +msgid "" +"`Image I/O-Ext <https://imageio-ext.dev.java.net/>`__ : The main core " +"module of the project is gdalframework, a framework leveraging on GDAL " +"via SWIG's generated JAVA bindings to provide support for a reach set of " +"data formats. (**Note**: this framework doesn't necessarily ship the " +"latest released GDAL version)" +msgstr "" + +#: ../../source/api/ogr_srs_api.rst:10 +msgid "ogr_srs_api.h: Spatial Reference System C API" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:10 +msgid "OGRFeature C++ API" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:13 +msgid "OGRFeature class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:20 +msgid "OGRFeatureDefn class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:27 +msgid "OGRFieldDefn class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:34 +msgid "OGRGeomFieldDefn class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:41 +msgid "OGRFieldDomain class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:48 +msgid "OGRCodedFieldDomain class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:55 +msgid "OGRRangeFieldDomain class" +msgstr "" + +#: ../../source/api/ogrfeature_cpp.rst:62 +msgid "OGRGlobFieldDomain class" +msgstr "" + +#: ../../source/api/ogrfeaturestyle_cpp.rst:10 +msgid "OGRFeature Style C++ API" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:10 +msgid "OGRGeometry C++ API" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:12 +msgid "Include file: ogr_geometry.h" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:15 +msgid "OGRGeometryFactory class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:22 +msgid "OGRGeometry class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:29 +msgid "OGRPoint class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:36 +msgid "OGRLineString class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:43 +msgid "OGRLinearRing class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:50 +msgid "OGRCircularString class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:57 +msgid "OGRCurve class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:64 +msgid "OGRSurface class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:71 +msgid "OGRPolygon class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:78 +msgid "OGRCurvePolygon class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:85 +msgid "OGRMultiPoint class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:92 +msgid "OGRMultiLineString class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:99 +msgid "OGRMultiPolygon class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:106 +msgid "OGRGeometryCollection class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:113 +msgid "OGRMultiCurve class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:120 +msgid "OGRMultiSurface class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:127 +msgid "OGRPolyhedralSurface class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:134 +msgid "OGRTriangle class" +msgstr "" + +#: ../../source/api/ogrgeometry_cpp.rst:141 +msgid "OGRTriangulatedSurface class" +msgstr "" + +#: ../../source/api/ogrlayer_cpp.rst:10 +msgid "OGRLayer C++ API" +msgstr "" + +#: ../../source/api/ogrlayer_cpp.rst ../../source/api/ogrspatialref.rst +msgid "Public Static Attributes" +msgstr "" + +#: ../../source/api/ogrspatialref.rst:10 +msgid "Spatial Reference System C++ API" +msgstr "" + +#: ../../source/api/python/general.rst:9 +msgid "Python General API" +msgstr "" + +#: ../../source/api/python/general.rst:12 +msgid "Configuration Management" +msgstr "" + +#: ../../source/api/python/general.rst:58 +msgid "Error Handling" +msgstr "" + +#: of osgeo.gdal.ConfigurePythonLogging:1 +msgid "Configure GDAL to use Python's logging framework" +msgstr "" + +#: ../../source/api/python/general.rst:96 +msgid "File Management" +msgstr "" + +#: of osgeo.gdal.DirEntry:1 +msgid "Proxy of C++ DirEntry class." +msgstr "" + +#: of osgeo.gdal.DirEntry.extra:1 +msgid "p.p.char" +msgstr "" + +#: of osgeo.gdal.Band.DataType osgeo.gdal.Band.XSize osgeo.gdal.Band.YSize +#: osgeo.gdal.ColorEntry.c1 osgeo.gdal.ColorEntry.c2 osgeo.gdal.ColorEntry.c3 +#: osgeo.gdal.ColorEntry.c4 osgeo.gdal.Dataset.RasterCount +#: osgeo.gdal.Dataset.RasterXSize osgeo.gdal.Dataset.RasterYSize +#: osgeo.gdal.DirEntry.extra osgeo.gdal.DirEntry.mode +#: osgeo.gdal.DirEntry.modeKnown osgeo.gdal.DirEntry.mtime +#: osgeo.gdal.DirEntry.mtimeKnown osgeo.gdal.DirEntry.name +#: osgeo.gdal.DirEntry.size osgeo.gdal.DirEntry.sizeKnown +#: osgeo.gdal.Driver.HelpTopic osgeo.gdal.Driver.LongName +#: osgeo.gdal.Driver.ShortName osgeo.gdal.GCP.GCPLine osgeo.gdal.GCP.GCPPixel +#: osgeo.gdal.GCP.GCPX osgeo.gdal.GCP.GCPY osgeo.gdal.GCP.GCPZ +#: osgeo.gdal.GCP.Id osgeo.gdal.GCP.Info osgeo.gdal.StatBuf.mode +#: osgeo.gdal.StatBuf.mtime osgeo.gdal.StatBuf.size osgeo.gdal.Statistics.max +#: osgeo.gdal.Statistics.mean osgeo.gdal.Statistics.min +#: osgeo.gdal.Statistics.std_dev osgeo.gdal.Statistics.valid_count +#: osgeo.ogr.DataSource.name osgeo.ogr.Driver.name +#: osgeo.osr.AreaOfUse.east_lon_degree osgeo.osr.AreaOfUse.name +#: osgeo.osr.AreaOfUse.north_lat_degree osgeo.osr.AreaOfUse.south_lat_degree +#: osgeo.osr.AreaOfUse.west_lon_degree osgeo.osr.CRSInfo.area_name +#: osgeo.osr.CRSInfo.auth_name osgeo.osr.CRSInfo.bbox_valid +#: osgeo.osr.CRSInfo.code osgeo.osr.CRSInfo.deprecated +#: osgeo.osr.CRSInfo.east_lon_degree osgeo.osr.CRSInfo.name +#: osgeo.osr.CRSInfo.north_lat_degree osgeo.osr.CRSInfo.projection_method +#: osgeo.osr.CRSInfo.south_lat_degree osgeo.osr.CRSInfo.type +#: osgeo.osr.CRSInfo.type:3 osgeo.osr.CRSInfo.west_lon_degree +msgid "type" +msgstr "" + +#: of osgeo.gdal.DirEntry.extra:3 +msgid "extra" +msgstr "" + +#: of osgeo.gdal.Band.XSize:1 osgeo.gdal.Band.YSize:1 +#: osgeo.gdal.Dataset.RasterCount:1 osgeo.gdal.Dataset.RasterXSize:1 +#: osgeo.gdal.Dataset.RasterYSize:1 osgeo.gdal.DirEntry.mode:1 +#: osgeo.gdal.StatBuf.mode:1 +msgid "int" +msgstr "" + +#: of osgeo.gdal.DirEntry.mode:3 osgeo.gdal.StatBuf.mode:3 +msgid "mode" +msgstr "" + +#: of osgeo.gdal.DirEntry.modeKnown:1 osgeo.gdal.DirEntry.mtimeKnown:1 +#: osgeo.gdal.DirEntry.sizeKnown:1 osgeo.osr.CRSInfo.bbox_valid:1 +#: osgeo.osr.CRSInfo.deprecated:1 +msgid "bool" +msgstr "" + +#: of osgeo.gdal.DirEntry.modeKnown:3 +msgid "modeKnown" +msgstr "" + +#: of osgeo.gdal.DirEntry.mtime:1 osgeo.gdal.DirEntry.size:1 +#: osgeo.gdal.StatBuf.mtime:1 osgeo.gdal.StatBuf.size:1 +#: osgeo.gdal.Statistics.valid_count:1 +msgid "GIntBig" +msgstr "" + +#: of osgeo.gdal.DirEntry.mtime:3 osgeo.gdal.StatBuf.mtime:3 +msgid "mtime" +msgstr "" + +#: of osgeo.gdal.DirEntry.mtimeKnown:3 +msgid "mtimeKnown" +msgstr "" + +#: of osgeo.gdal.DirEntry.name:1 osgeo.gdal.GCP.Id:1 osgeo.gdal.GCP.Info:1 +#: osgeo.osr.AreaOfUse.name:1 osgeo.osr.CRSInfo.area_name:1 +#: osgeo.osr.CRSInfo.auth_name:1 osgeo.osr.CRSInfo.code:1 +#: osgeo.osr.CRSInfo.name:1 osgeo.osr.CRSInfo.projection_method:1 +msgid "p.char" +msgstr "" + +#: of osgeo.gdal.DirEntry.name:3 osgeo.ogr.DataSource.name:3 +#: osgeo.ogr.Driver.name:3 osgeo.osr.AreaOfUse.name:3 osgeo.osr.CRSInfo.name:3 +msgid "name" +msgstr "" + +#: of osgeo.gdal.DirEntry.size:3 osgeo.gdal.StatBuf.size:3 +msgid "size" +msgstr "" + +#: of osgeo.gdal.DirEntry.sizeKnown:3 +msgid "sizeKnown" +msgstr "" + +#: of osgeo.gdal.DirEntry.thisown:1 osgeo.gdal_array.VirtualMem.thisown:1 +#: osgeo.gnm.GenericNetwork.thisown:1 osgeo.gnm.Network.thisown:1 +msgid "The membership flag" +msgstr "" + +#: ../../source/api/python/mdim_api.rst:9 +msgid "Python Multi-dimensional array API" +msgstr "" + +#: of osgeo.gdal.Group:1 +msgid "Proxy of C++ GDALGroupHS class." +msgstr "" + +#: of osgeo.gdal.Dimension:1 +msgid "Proxy of C++ GDALDimensionHS class." +msgstr "" + +#: of osgeo.gdal.MDArray:1 +msgid "Proxy of C++ GDALMDArrayHS class." +msgstr "" + +#: of osgeo.gdal.MDArray.GetShape:1 +msgid "Return the shape of the array" +msgstr "" + +#: of osgeo.gdal.MDArray.ReadAsMaskedArray:1 +msgid "Return a numpy masked array of ReadAsArray() with GetMask()" +msgstr "" + +#: of osgeo.gdal.MDArray.shape:1 +msgid "Returns the shape of the array." +msgstr "" + +#: of osgeo.gdal.Attribute:1 +msgid "Proxy of C++ GDALAttributeHS class." +msgstr "" + +#: of osgeo.gdal.Attribute.Read:1 +msgid "Read an attribute and return it with the most appropriate type" +msgstr "" + +#: of osgeo.gdal.ExtendedDataType:1 +msgid "Proxy of C++ GDALExtendedDataTypeHS class." +msgstr "" + +#: ../../source/api/python/osgeo.rst:4 +msgid "Miscellaneous Python API" +msgstr "" + +#: ../../source/api/python/osgeo.rst:8 +msgid "Submodules" +msgstr "" + +#: ../../source/api/python/osgeo.rst:21 +msgid "Module contents" +msgstr "" + +#: ../../source/api/python/osgeo.gdal.rst:7 +msgid "osgeo.gdal module" +msgstr "" + +#: of osgeo.gdal.AsyncReader:1 osgeo.gdal.EDTComponent:1 +#: osgeo.gdal.GDALTransformerInfoShadow:1 osgeo.gdal.MajorObject:1 +#: osgeo.gdal.StatBuf:1 osgeo.gdal.Statistics:1 osgeo.gdal.VSILFILE:1 +#: osgeo.gdal.VirtualMem:1 osgeo.gdal_array.VirtualMem:1 osgeo.ogr.ArrowArray:1 +#: osgeo.ogr.ArrowArrayStream:1 osgeo.ogr.ArrowSchema:1 +#: osgeo.ogr.GeomTransformer:1 osgeo.ogr.MajorObject:1 +#: osgeo.ogr.PreparedGeometry:1 osgeo.osr.AreaOfUse:1 osgeo.osr.CRSInfo:1 +msgid "Bases: :py:class:`object`" +msgstr "" + +#: of osgeo.gdal.AsyncReader:1 +msgid "Proxy of C++ GDALAsyncReaderShadow class." +msgstr "" + +#: of osgeo.gdal.EDTComponent:1 +msgid "Proxy of C++ GDALEDTComponentHS class." +msgstr "" + +#: of osgeo.gdal.GDALTransformerInfoShadow:1 +msgid "Proxy of C++ GDALTransformerInfoShadow class." +msgstr "" + +#: of osgeo.gdal.MajorObject:1 osgeo.ogr.MajorObject:1 +msgid "Proxy of C++ GDALMajorObjectShadow class." +msgstr "" + +#: of osgeo.gdal.StatBuf:1 +msgid "Proxy of C++ StatBuf class." +msgstr "" + +#: of osgeo.gdal.Statistics:1 +msgid "Proxy of C++ Statistics class." +msgstr "" + +#: of osgeo.gdal.GCP.GCPLine:1 osgeo.gdal.GCP.GCPPixel:1 osgeo.gdal.GCP.GCPX:1 +#: osgeo.gdal.GCP.GCPY:1 osgeo.gdal.GCP.GCPZ:1 osgeo.gdal.Statistics.max:1 +#: osgeo.gdal.Statistics.mean:1 osgeo.gdal.Statistics.min:1 +#: osgeo.gdal.Statistics.std_dev:1 osgeo.osr.AreaOfUse.east_lon_degree:1 +#: osgeo.osr.AreaOfUse.north_lat_degree:1 +#: osgeo.osr.AreaOfUse.south_lat_degree:1 osgeo.osr.AreaOfUse.west_lon_degree:1 +#: osgeo.osr.CRSInfo.east_lon_degree:1 osgeo.osr.CRSInfo.north_lat_degree:1 +#: osgeo.osr.CRSInfo.south_lat_degree:1 osgeo.osr.CRSInfo.west_lon_degree:1 +msgid "double" +msgstr "" + +#: of osgeo.gdal.Statistics.max:3 +msgid "max" +msgstr "" + +#: of osgeo.gdal.Statistics.mean:3 +msgid "mean" +msgstr "" + +#: of osgeo.gdal.Statistics.min:3 +msgid "min" +msgstr "" + +#: of osgeo.gdal.Statistics.std_dev:3 +msgid "std_dev" +msgstr "" + +#: of osgeo.gdal.Statistics.valid_count:3 +msgid "valid_count" +msgstr "" + +#: of osgeo.gdal.VSILFILE:1 +msgid "Proxy of C++ VSILFILE class." +msgstr "" + +#: of osgeo.gdal.VirtualMem:1 osgeo.gdal_array.VirtualMem:1 +msgid "Proxy of C++ CPLVirtualMemShadow class." +msgstr "" + +#: of osgeo.gdal.listdir:1 +msgid "Iterate over a directory." +msgstr "" + +#: of osgeo.gdal.listdir:3 +msgid "recursionLevel = -1 means unlimited level of recursion." +msgstr "" + +#: ../../source/api/python/osgeo.gdal_array.rst:7 +msgid "osgeo.gdal\\_array module" +msgstr "" + +#: of osgeo.gdal_array.BandReadAsArray:1 +msgid "" +"Pure python implementation of reading a chunk of a GDAL file into a numpy" +" array. Used by the gdal.Band.ReadAsArray method." +msgstr "" + +#: of osgeo.gdal_array.BandWriteArray:1 +msgid "" +"Pure python implementation of writing a chunk of a GDAL file from a numpy" +" array. Used by the gdal.Band.WriteArray method." +msgstr "" + +#: of osgeo.gdal_array.CopyDatasetInfo:1 +msgid "" +"Copy georeferencing information and metadata from one dataset to another." +" src: input dataset dst: output dataset - It can be a ROI - xoff, yoff: " +"dst's offset with respect to src in pixel/line." +msgstr "" + +#: of osgeo.gdal_array.CopyDatasetInfo:6 +msgid "Notes: Destination dataset must have update access. Certain formats" +msgstr "" + +#: of osgeo.gdal_array.CopyDatasetInfo:7 +msgid "do not support creation of geotransforms and/or gcps." +msgstr "" + +#: of osgeo.gdal_array.DatasetReadAsArray:1 +msgid "" +"Pure python implementation of reading a chunk of a GDAL file into a numpy" +" array. Used by the gdal.Dataset.ReadAsArray method." +msgstr "" + +#: of osgeo.gdal_array.DatasetWriteArray:1 +msgid "" +"Pure python implementation of writing a chunk of a GDAL file from a numpy" +" array. Used by the gdal.Dataset.WriteArray method." +msgstr "" + +#: of osgeo.gdal_array.RATReadArray:1 +msgid "" +"Pure Python implementation of reading a chunk of the RAT into a numpy " +"array. Called from RasterAttributeTable.ReadAsArray" +msgstr "" + +#: of osgeo.gdal_array.RATWriteArray:1 +msgid "" +"Pure Python implementation of writing a chunk of the RAT from a numpy " +"array. Type of array is coerced to one of the types (int, double, string)" +" supported. Called from RasterAttributeTable.WriteArray" +msgstr "" + +#: ../../source/api/python/osgeo.gdalconst.rst:7 +msgid "osgeo.gdalconst module" +msgstr "" + +#: ../../source/api/python/osgeo.gnm.rst:7 +msgid "osgeo.gnm module" +msgstr "" + +#: of osgeo.gnm.GenericNetwork:1 +msgid "Bases: :py:class:`~osgeo.gnm.Network`" +msgstr "" + +#: of osgeo.gnm.GenericNetwork:1 +msgid "Proxy of C++ GNMGenericNetworkShadow class." +msgstr "" + +#: of osgeo.gnm.Network:1 osgeo.ogr.DataSource:1 osgeo.ogr.Driver:1 +msgid "Bases: :py:class:`~osgeo.ogr.MajorObject`" +msgstr "" + +#: of osgeo.gnm.Network:1 +msgid "Proxy of C++ GNMNetworkShadow class." +msgstr "" + +#: ../../source/api/python/osgeo.ogr.rst:7 +msgid "osgeo.ogr module" +msgstr "" + +#: of osgeo.ogr.ArrowArray:1 +msgid "Proxy of C++ ArrowArray class." +msgstr "" + +#: of osgeo.ogr.ArrowArrayStream:1 +msgid "Proxy of C++ ArrowArrayStream class." +msgstr "" + +#: of osgeo.ogr.ArrowSchema:1 +msgid "Proxy of C++ ArrowSchema class." +msgstr "" + +#: of osgeo.ogr.DataSource:1 +msgid "Proxy of C++ OGRDataSourceShadow class." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:1 +msgid "" +"OGRLayerH OGR_DS_CopyLayer(OGRDataSourceH hDS, OGRLayerH hSrcLayer, const" +" char \\*pszNewName, char \\*\\*papszOptions)" +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:5 +msgid "Duplicate an existing layer." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:7 +msgid "" +"This function creates a new layer, duplicate the field definitions of the" +" source layer and then duplicate each features of the source layer. The " +"papszOptions argument can be used to control driver specific creation " +"options. These options are normally documented in the format specific " +"documentation. The source layer may come from another dataset." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:14 +msgid "Deprecated Use GDALDatasetCopyLayer() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:16 +msgid "handle to the data source where to create the new layer" +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:17 +msgid "handle to the source layer." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:18 +msgid "the name of the layer to create." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:19 +msgid "a StringList of name=value options. Options are driver specific." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer:22 +msgid "a handle to the layer, or NULL if an error occurs." +msgstr "" + +#: of osgeo.ogr.DataSource.CopyLayer osgeo.ogr.DataSource.CreateLayer +#: osgeo.ogr.DataSource.DeleteLayer osgeo.ogr.DataSource.ExecuteSQL +#: osgeo.ogr.DataSource.GetDriver osgeo.ogr.DataSource.GetLayerByName +#: osgeo.ogr.DataSource.GetLayerCount osgeo.ogr.DataSource.GetName +#: osgeo.ogr.DataSource.TestCapability osgeo.ogr.Feature.Clone +#: osgeo.ogr.Feature.Equal osgeo.ogr.Feature.GetDefnRef +#: osgeo.ogr.Feature.GetFID osgeo.ogr.Feature.GetFieldAsBinary +#: osgeo.ogr.Feature.GetFieldAsDateTime osgeo.ogr.Feature.GetFieldAsDouble +#: osgeo.ogr.Feature.GetFieldAsDoubleList osgeo.ogr.Feature.GetFieldAsInteger +#: osgeo.ogr.Feature.GetFieldAsInteger64 +#: osgeo.ogr.Feature.GetFieldAsInteger64List +#: osgeo.ogr.Feature.GetFieldAsIntegerList osgeo.ogr.Feature.GetFieldAsString +#: osgeo.ogr.Feature.GetFieldAsStringList osgeo.ogr.Feature.GetFieldCount +#: osgeo.ogr.Feature.GetFieldDefnRef osgeo.ogr.Feature.GetFieldIndex +#: osgeo.ogr.Feature.GetGeomFieldCount osgeo.ogr.Feature.GetGeomFieldDefnRef +#: osgeo.ogr.Feature.GetGeomFieldIndex osgeo.ogr.Feature.GetGeometryRef +#: osgeo.ogr.Feature.GetNativeData osgeo.ogr.Feature.GetNativeMediaType +#: osgeo.ogr.Feature.GetStyleString osgeo.ogr.Feature.IsFieldNull +#: osgeo.ogr.Feature.IsFieldSet osgeo.ogr.Feature.IsFieldSetAndNotNull +#: osgeo.ogr.Feature.SetFID osgeo.ogr.Feature.SetFrom +#: osgeo.ogr.Feature.SetFromWithMap osgeo.ogr.Feature.SetGeomField +#: osgeo.ogr.Feature.SetGeomFieldDirectly osgeo.ogr.Feature.SetGeometry +#: osgeo.ogr.Feature.SetGeometryDirectly osgeo.ogr.Feature.Validate +#: osgeo.ogr.Feature.geometry osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn +#: osgeo.ogr.FeatureDefn.GetFieldCount osgeo.ogr.FeatureDefn.GetFieldDefn +#: osgeo.ogr.FeatureDefn.GetFieldIndex osgeo.ogr.FeatureDefn.GetGeomFieldCount +#: osgeo.ogr.FeatureDefn.GetGeomFieldDefn +#: osgeo.ogr.FeatureDefn.GetGeomFieldIndex osgeo.ogr.FeatureDefn.GetGeomType +#: osgeo.ogr.FeatureDefn.GetName osgeo.ogr.FeatureDefn.GetReferenceCount +#: osgeo.ogr.FeatureDefn.IsGeometryIgnored osgeo.ogr.FeatureDefn.IsSame +#: osgeo.ogr.FeatureDefn.IsStyleIgnored +#: osgeo.ogr.FieldDefn.GetAlternativeNameRef osgeo.ogr.FieldDefn.GetDefault +#: osgeo.ogr.FieldDefn.GetDomainName osgeo.ogr.FieldDefn.GetJustify +#: osgeo.ogr.FieldDefn.GetNameRef osgeo.ogr.FieldDefn.GetPrecision +#: osgeo.ogr.FieldDefn.GetSubType osgeo.ogr.FieldDefn.GetType +#: osgeo.ogr.FieldDefn.GetWidth osgeo.ogr.FieldDefn.IsDefaultDriverSpecific +#: osgeo.ogr.FieldDefn.IsIgnored osgeo.ogr.FieldDefn.IsNullable +#: osgeo.ogr.FieldDefn.IsUnique osgeo.ogr.FieldDefn.justify +#: osgeo.ogr.FieldDefn.precision osgeo.ogr.FieldDefn.type +#: osgeo.ogr.FieldDefn.width osgeo.ogr.Geometry.Boundary +#: osgeo.ogr.Geometry.Buffer osgeo.ogr.Geometry.Centroid +#: osgeo.ogr.Geometry.Clone osgeo.ogr.Geometry.Contains +#: osgeo.ogr.Geometry.ConvexHull osgeo.ogr.Geometry.CoordinateDimension +#: osgeo.ogr.Geometry.Crosses osgeo.ogr.Geometry.DelaunayTriangulation +#: osgeo.ogr.Geometry.Difference osgeo.ogr.Geometry.Disjoint +#: osgeo.ogr.Geometry.Distance osgeo.ogr.Geometry.Distance3D +#: osgeo.ogr.Geometry.Equals osgeo.ogr.Geometry.ExportToIsoWkb +#: osgeo.ogr.Geometry.ExportToIsoWkt osgeo.ogr.Geometry.ExportToWkb +#: osgeo.ogr.Geometry.ExportToWkt osgeo.ogr.Geometry.GetCoordinateDimension +#: osgeo.ogr.Geometry.GetDimension osgeo.ogr.Geometry.GetGeometryName +#: osgeo.ogr.Geometry.GetGeometryType osgeo.ogr.Geometry.GetSpatialReference +#: osgeo.ogr.Geometry.Intersection osgeo.ogr.Geometry.Intersects +#: osgeo.ogr.Geometry.Is3D osgeo.ogr.Geometry.IsEmpty +#: osgeo.ogr.Geometry.IsMeasured osgeo.ogr.Geometry.IsRing +#: osgeo.ogr.Geometry.IsSimple osgeo.ogr.Geometry.IsValid +#: osgeo.ogr.Geometry.MakeValid osgeo.ogr.Geometry.Normalize +#: osgeo.ogr.Geometry.Overlaps osgeo.ogr.Geometry.PointOnSurface +#: osgeo.ogr.Geometry.Polygonize osgeo.ogr.Geometry.Simplify +#: osgeo.ogr.Geometry.SimplifyPreserveTopology osgeo.ogr.Geometry.SymDifference +#: osgeo.ogr.Geometry.Touches osgeo.ogr.Geometry.Transform +#: osgeo.ogr.Geometry.TransformTo osgeo.ogr.Geometry.Union +#: osgeo.ogr.Geometry.UnionCascaded osgeo.ogr.Geometry.Within +#: osgeo.ogr.Geometry.WkbSize osgeo.ogr.Layer.AlterFieldDefn +#: osgeo.ogr.Layer.Clip osgeo.ogr.Layer.CommitTransaction +#: osgeo.ogr.Layer.CreateFeature osgeo.ogr.Layer.CreateField +#: osgeo.ogr.Layer.CreateGeomField osgeo.ogr.Layer.DeleteFeature +#: osgeo.ogr.Layer.DeleteField osgeo.ogr.Layer.Erase +#: osgeo.ogr.Layer.FindFieldIndex osgeo.ogr.Layer.GetFIDColumn +#: osgeo.ogr.Layer.GetFeature osgeo.ogr.Layer.GetFeatureCount +#: osgeo.ogr.Layer.GetGeomType osgeo.ogr.Layer.GetGeometryColumn +#: osgeo.ogr.Layer.GetGeometryTypes osgeo.ogr.Layer.GetLayerDefn +#: osgeo.ogr.Layer.GetName osgeo.ogr.Layer.GetNextFeature +#: osgeo.ogr.Layer.GetSpatialFilter osgeo.ogr.Layer.GetSpatialRef +#: osgeo.ogr.Layer.Identity osgeo.ogr.Layer.Intersection +#: osgeo.ogr.Layer.ReorderField osgeo.ogr.Layer.ReorderFields +#: osgeo.ogr.Layer.RollbackTransaction osgeo.ogr.Layer.SetAttributeFilter +#: osgeo.ogr.Layer.SetFeature osgeo.ogr.Layer.SetIgnoredFields +#: osgeo.ogr.Layer.SetNextByIndex osgeo.ogr.Layer.StartTransaction +#: osgeo.ogr.Layer.SymDifference osgeo.ogr.Layer.SyncToDisk +#: osgeo.ogr.Layer.TestCapability osgeo.ogr.Layer.Union osgeo.ogr.Layer.Update +#: osgeo.ogr.Layer.UpsertFeature +msgid "Return type" +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:1 +msgid "" +"OGRLayerH OGR_DS_CreateLayer(OGRDataSourceH hDS, const char \\*pszName, " +"OGRSpatialReferenceH hSpatialRef, OGRwkbGeometryType eType, char " +"\\*\\*papszOptions)" +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:6 +msgid "" +"This function attempts to create a new layer on the data source with the " +"indicated name, coordinate system, geometry type." +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:9 +msgid "" +"The papszOptions argument can be used to control driver specific creation" +" options. These options are normally documented in the format specific " +"documentation." +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:13 +msgid "Deprecated Use GDALDatasetCreateLayer() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:15 +msgid "" +"The dataset handle.pszName: the name for the new layer. This should " +"ideally not match any existing layer on the datasource." +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:17 +msgid "" +"handle to the coordinate system to use for the new layer, or NULL if no " +"coordinate system is available. The driver might only increase the " +"reference counter of the object to take ownership, and not make a full " +"copy, so do not use OSRDestroySpatialReference(), but OSRRelease() " +"instead when you are done with the object." +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:22 +msgid "" +"the geometry type for the layer. Use wkbUnknown if there are no " +"constraints on the types geometry to be written." +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:24 +msgid "" +"a StringList of name=value options. Options are driver specific, and " +"driver information can be found at the following " +"url:http://www.gdal.org/ogr_formats.html" +msgstr "" + +#: of osgeo.ogr.DataSource.CreateLayer:28 +msgid "NULL is returned on failure, or a new OGRLayer handle on success." +msgstr "" + +#: of osgeo.ogr.DataSource.DeleteLayer:1 +msgid "Delete the indicated layer from the datasource." +msgstr "" + +#: of osgeo.ogr.DataSource.DeleteLayer:3 +msgid "For more details: :c:func:`OGR_DS_DeleteLayer`" +msgstr "" + +#: of osgeo.ogr.DataSource.DeleteLayer:5 +msgid "index or name of the layer to delete." +msgstr "" + +#: of osgeo.ogr.DataSource.DeleteLayer:8 +msgid "" +":py:const:`osgeo.ogr.OGRERR_NONE` on success, or " +":py:const:`osgeo.ogr.OGRERR_UNSUPPORTED_OPERATION` if deleting layers is " +"not supported for this datasource." +msgstr "" + +#: of osgeo.ogr.DataSource.Dereference:1 osgeo.ogr.DataSource.Reference:1 +#: osgeo.ogr.Layer.Dereference:1 osgeo.ogr.Layer.Reference:1 +msgid "For backwards compatibility only." +msgstr "" + +#: of osgeo.ogr.DataSource.Destroy:1 osgeo.ogr.DataSource.Release:1 +#: osgeo.ogr.Feature.Destroy:1 osgeo.ogr.FeatureDefn.Destroy:1 +#: osgeo.ogr.FieldDefn.Destroy:1 +msgid "" +"Once called, self has effectively been destroyed. Do not access. For " +"backwards compatibility only" +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:1 +msgid "" +"OGRLayerH OGR_DS_ExecuteSQL(OGRDataSourceH hDS, const char " +"\\*pszStatement, OGRGeometryH hSpatialFilter, const char \\*pszDialect)" +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:5 +msgid "Execute an SQL statement against the data store." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:7 +msgid "" +"The result of an SQL query is either NULL for statements that are in " +"error, or that have no results set, or an OGRLayer handle representing a " +"results set from the query. Note that this OGRLayer is in addition to the" +" layers in the data store and must be destroyed with " +"OGR_DS_ReleaseResultSet() before the data source is closed (destroyed)." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:14 +msgid "" +"For more information on the SQL dialect supported internally by OGR " +"review theOGR SQL document. Some drivers (i.e. Oracle and PostGIS) pass " +"the SQL directly through to the underlying RDBMS." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:18 +msgid "TheSQLITE dialect can also be used." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:20 +msgid "Deprecated Use GDALDatasetExecuteSQL() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:22 +msgid "handle to the data source on which the SQL query is executed." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:23 +msgid "the SQL statement to execute." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:24 +msgid "handle to a geometry which represents a spatial filter. Can be NULL." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:26 +msgid "" +"allows control of the statement dialect. If set to NULL, the OGR SQL " +"engine will be used, except for RDBMS drivers that will use their " +"dedicated SQL engine, unless OGRSQL is explicitly passed as the dialect. " +"The SQLITE dialect can also be used." +msgstr "" + +#: of osgeo.ogr.DataSource.ExecuteSQL:31 +msgid "" +"a handle to a OGRLayer containing the results of the query. Deallocate " +"with OGR_DS_ReleaseResultSet()." +msgstr "" + +#: of osgeo.ogr.DataSource.GetDriver:1 +msgid "OGRSFDriverH OGR_DS_GetDriver(OGRDataSourceH hDS)" +msgstr "" + +#: of osgeo.ogr.DataSource.GetDriver:4 +msgid "Returns the driver that the dataset was opened with." +msgstr "" + +#: of osgeo.ogr.DataSource.GetDriver:6 +msgid "" +"NOTE: Starting with GDAL 2.0, it is NOT safe to cast the returned handle " +"to OGRSFDriver\\*. If a C++ object is needed, the handle should be cast " +"to GDALDriver\\*." +msgstr "" + +#: of osgeo.ogr.DataSource.GetDriver:10 +msgid "Deprecated Use GDALGetDatasetDriver() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.GetDriver:12 +msgid "handle to the datasource" +msgstr "" + +#: of osgeo.ogr.DataSource.GetDriver:14 +msgid "" +"NULL if driver info is not available, or pointer to a driver owned by the" +" OGRSFDriverManager." +msgstr "" + +#: of osgeo.gdal.Dataset.GetLayer:1 osgeo.ogr.DataSource.GetLayer:1 +msgid "Return the layer given an index or a name" +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:1 +msgid "" +"OGRLayerH OGR_DS_GetLayerByName(OGRDataSourceH hDS, const char " +"\\*pszLayerName)" +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:4 +msgid "Fetch a layer by name." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:6 +msgid "" +"The returned layer remains owned by the OGRDataSource and should not be " +"deleted by the application." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:9 +msgid "Deprecated Use GDALDatasetGetLayerByName() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:11 +msgid "handle to the data source from which to get the layer." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:12 +msgid "Layer the layer name of the layer to fetch." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerByName:14 +msgid "" +"a handle to the layer, or NULL if the layer is not found or an error " +"occurs." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerCount:1 +msgid "int OGR_DS_GetLayerCount(OGRDataSourceH hDS)" +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerCount:4 +msgid "Get the number of layers in this data source." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerCount:6 +msgid "Deprecated Use GDALDatasetGetLayerCount() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerCount:8 +msgid "handle to the data source from which to get the number of layers." +msgstr "" + +#: of osgeo.ogr.DataSource.GetLayerCount:11 +msgid "layer count." +msgstr "" + +#: of osgeo.ogr.DataSource.GetName:1 +msgid "const char\\* OGR_DS_GetName(OGRDataSourceH hDS)" +msgstr "" + +#: of osgeo.ogr.DataSource.GetName:4 +msgid "Returns the name of the data source." +msgstr "" + +#: of osgeo.ogr.DataSource.GetName:6 +msgid "" +"This string should be sufficient to open the data source if passed to the" +" same OGRSFDriver that this data source was opened with, but it need not " +"be exactly the same string that was used to open the data source. " +"Normally this is a filename." +msgstr "" + +#: of osgeo.ogr.DataSource.GetName:11 +msgid "Deprecated Use GDALGetDescription() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.GetName:13 +msgid "handle to the data source to get the name from." +msgstr "" + +#: of osgeo.ogr.DataSource.GetName:15 +msgid "" +"pointer to an internal name string which should not be modified or freed " +"by the caller." +msgstr "" + +#: of osgeo.ogr.DataSource.GetRefCount:1 +msgid "int OGR_DS_GetRefCount(OGRDataSourceH hDataSource)" +msgstr "" + +#: of osgeo.ogr.DataSource.GetStyleTable:1 +msgid "OGRStyleTableH OGR_DS_GetStyleTable(OGRDataSourceH hDS)" +msgstr "" + +#: of osgeo.ogr.DataSource.GetStyleTable:4 osgeo.ogr.Layer.GetStyleTable:1 +msgid "Get style table." +msgstr "" + +#: of osgeo.ogr.DataSource.GetSummaryRefCount:1 +msgid "int OGR_DS_GetSummaryRefCount(OGRDataSourceH hDataSource)" +msgstr "" + +#: of osgeo.ogr.DataSource.ReleaseResultSet:1 +msgid "void OGR_DS_ReleaseResultSet(OGRDataSourceH hDS, OGRLayerH hLayer)" +msgstr "" + +#: of osgeo.ogr.DataSource.ReleaseResultSet:4 +msgid "Release results of OGR_DS_ExecuteSQL()." +msgstr "" + +#: of osgeo.ogr.DataSource.ReleaseResultSet:6 +msgid "" +"This function should only be used to deallocate OGRLayers resulting from " +"an OGR_DS_ExecuteSQL() call on the same OGRDataSource. Failure to " +"deallocate a results set before destroying the OGRDataSource may cause " +"errors." +msgstr "" + +#: of osgeo.ogr.DataSource.ReleaseResultSet:11 +msgid "Deprecated Use GDALDatasetReleaseResultSet() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.ReleaseResultSet:13 +msgid "a handle to the data source on which was executed an SQL query." +msgstr "" + +#: of osgeo.ogr.DataSource.ReleaseResultSet:14 +msgid "handle to the result of a previous OGR_DS_ExecuteSQL() call." +msgstr "" + +#: of osgeo.ogr.DataSource.SetStyleTable:1 +msgid "void OGR_DS_SetStyleTable(OGRDataSourceH hDS, OGRStyleTableH hStyleTable)" +msgstr "" + +#: of osgeo.ogr.DataSource.SetStyleTable:4 osgeo.ogr.Layer.SetStyleTable:1 +msgid "Set style table." +msgstr "" + +#: of osgeo.ogr.DataSource.SyncToDisk:1 +msgid "OGRErr OGR_DS_SyncToDisk(OGRDataSourceH hDS)" +msgstr "" + +#: of osgeo.ogr.DataSource.SyncToDisk:4 osgeo.ogr.Layer.SyncToDisk:1 +msgid "Flush pending changes to disk." +msgstr "" + +#: of osgeo.ogr.DataSource.SyncToDisk:6 +msgid "See GDALDataset::FlushCache()" +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:1 +msgid "int OGR_DS_TestCapability(OGRDataSourceH hDS, const char \\*pszCapability)" +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:4 +msgid "Test if capability is available." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:6 +msgid "" +"One of the following data source capability names can be passed into this" +" function, and a TRUE or FALSE value will be returned indicating whether " +"or not the capability is available for this object." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:10 +msgid "ODsCCreateLayer: True if this datasource can create new layers." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:12 +msgid "ODsCDeleteLayer: True if this datasource can delete existing layers." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:14 +msgid "" +"ODsCCreateGeomFieldAfterCreateLayer: True if the layers of this " +"datasource support CreateGeomField() just after layer creation." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:17 +msgid "" +"ODsCCurveGeometries: True if this datasource supports writing curve " +"geometries. (GDAL 2.0). In that case, OLCCurveGeometries must also be " +"declared in layers of that dataset." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:21 +msgid "" +"The #define macro forms of the capability names should be used in " +"preference to the strings themselves to avoid misspelling." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:24 +msgid "Deprecated Use GDALDatasetTestCapability() in GDAL 2.0" +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:26 +msgid "handle to the data source against which to test the capability." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:27 +msgid "the capability to test." +msgstr "" + +#: of osgeo.ogr.DataSource.TestCapability:29 +msgid "TRUE if capability available otherwise FALSE." +msgstr "" + +#: of osgeo.gdal.Driver.HelpTopic:1 osgeo.gdal.Driver.LongName:1 +#: osgeo.gdal.Driver.ShortName:1 osgeo.ogr.DataSource.name:1 +#: osgeo.ogr.Driver.name:1 +msgid "p.q(const).char" +msgstr "" + +#: of osgeo.ogr.Driver:1 +msgid "Proxy of C++ OGRDriverShadow class." +msgstr "" + +#: of osgeo.ogr.GeomTransformer:1 +msgid "Proxy of C++ OGRGeomTransformerShadow class." +msgstr "" + +#: of osgeo.ogr.PreparedGeometry:1 +msgid "Proxy of C++ OGRPreparedGeometryShadow class." +msgstr "" + +#: ../../source/api/python/osgeo.osr.rst:7 +msgid "osgeo.osr module" +msgstr "" + +#: of osgeo.osr.AreaOfUse:1 +msgid "Proxy of C++ OSRAreaOfUse class." +msgstr "" + +#: of osgeo.osr.AreaOfUse.east_lon_degree:3 osgeo.osr.CRSInfo.east_lon_degree:3 +msgid "east_lon_degree" +msgstr "" + +#: of osgeo.osr.AreaOfUse.north_lat_degree:3 +#: osgeo.osr.CRSInfo.north_lat_degree:3 +msgid "north_lat_degree" +msgstr "" + +#: of osgeo.osr.AreaOfUse.south_lat_degree:3 +#: osgeo.osr.CRSInfo.south_lat_degree:3 +msgid "south_lat_degree" +msgstr "" + +#: of osgeo.osr.AreaOfUse.west_lon_degree:3 osgeo.osr.CRSInfo.west_lon_degree:3 +msgid "west_lon_degree" +msgstr "" + +#: of osgeo.osr.CRSInfo:1 +msgid "Proxy of C++ OSRCRSInfo class." +msgstr "" + +#: of osgeo.osr.CRSInfo.area_name:3 +msgid "area_name" +msgstr "" + +#: of osgeo.osr.CRSInfo.auth_name:3 +msgid "auth_name" +msgstr "" + +#: of osgeo.osr.CRSInfo.bbox_valid:3 +msgid "bbox_valid" +msgstr "" + +#: of osgeo.osr.CRSInfo.code:3 +msgid "code" +msgstr "" + +#: of osgeo.osr.CRSInfo.deprecated:3 +msgid "deprecated" +msgstr "" + +#: of osgeo.osr.CRSInfo.projection_method:3 +msgid "projection_method" +msgstr "" + +#: of osgeo.osr.CRSInfo.type:1 +msgid "OSRCRSType" +msgstr "" + +#: ../../source/api/python/raster_api.rst:9 +msgid "Python Raster API" +msgstr "" + +#: ../../source/api/python/raster_api.rst:11 +msgid "" +"This page contains classes, methods, functions that relate to the GDAL " +":ref:`raster_data_model`:" +msgstr "" + +#: ../../source/api/python/raster_api.rst:13 +msgid "`Driver`_" +msgstr "" + +#: ../../source/api/python/raster_api.rst:14 +msgid "`Dataset`_" +msgstr "" + +#: ../../source/api/python/raster_api.rst:15 +msgid "`Band`_" +msgstr "" + +#: ../../source/api/python/raster_api.rst:16 +msgid "`Other`_" +msgstr "" + +#: ../../source/api/python/raster_api.rst:21 +msgid "Driver" +msgstr "" + +#: of osgeo.gdal.Driver:1 +msgid "Proxy of C++ GDALDriverShadow class." +msgstr "" + +#: of osgeo.gdal.Driver.HelpTopic:3 +msgid "HelpTopic" +msgstr "" + +#: of osgeo.gdal.Driver.LongName:3 +msgid "LongName" +msgstr "" + +#: of osgeo.gdal.Driver.ShortName:3 +msgid "ShortName" +msgstr "" + +#: ../../source/api/python/raster_api.rst:41 +msgid "Dataset" +msgstr "" + +#: of osgeo.gdal.Dataset:1 +msgid "Proxy of C++ GDALDatasetShadow class." +msgstr "" + +#: of osgeo.gdal.Dataset.DeleteLayer:1 +msgid "Deletes the layer given an index or layer name" +msgstr "" + +#: of osgeo.gdal.Dataset.GetTiledVirtualMemArray:1 +msgid "" +"Return a NumPy array for the dataset, seen as a virtual memory mapping " +"with a tile organization. If there are several bands and " +"tile_organization = gdal.GTO_TIP, an element is accessed with " +"array[tiley][tilex][y][x][band]. If there are several bands and " +"tile_organization = gdal.GTO_BIT, an element is accessed with " +"array[tiley][tilex][band][y][x]. If there are several bands and " +"tile_organization = gdal.GTO_BSQ, an element is accessed with " +"array[band][tiley][tilex][y][x]. If there is only one band, an element is" +" accessed with array[tiley][tilex][y][x]. Any reference to the array must" +" be dropped before the last reference to the related dataset is also " +"dropped." +msgstr "" + +#: of osgeo.gdal.Dataset.GetVirtualMemArray:1 +msgid "" +"Return a NumPy array for the dataset, seen as a virtual memory mapping. " +"If there are several bands and band_sequential = True, an element is " +"accessed with array[band][y][x]. If there are several bands and " +"band_sequential = False, an element is accessed with array[y][x][band]. " +"If there is only one band, an element is accessed with array[y][x]. Any " +"reference to the array must be dropped before the last reference to the " +"related dataset is also dropped." +msgstr "" + +#: of osgeo.gdal.Dataset.RasterCount:3 +msgid "RasterCount" +msgstr "" + +#: of osgeo.gdal.Dataset.RasterXSize:3 +msgid "RasterXSize" +msgstr "" + +#: of osgeo.gdal.Dataset.RasterYSize:3 +msgid "RasterYSize" +msgstr "" + +#: of osgeo.gdal.Band.ReadAsArray:1 osgeo.gdal.Dataset.ReadAsArray:1 +msgid "" +"Reading a chunk of a GDAL band into a numpy array. The optional " +"(buf_xsize,buf_ysize,buf_type) parameters should generally not be " +"specified if buf_obj is specified. The array is returned" +msgstr "" + +#: ../../source/api/python/raster_api.rst:55 +msgid "Band" +msgstr "" + +#: of osgeo.gdal.Band:1 +msgid "Proxy of C++ GDALRasterBandShadow class." +msgstr "" + +#: of osgeo.gdal.Band.DataType:1 +msgid "GDALDataType" +msgstr "" + +#: of osgeo.gdal.Band.DataType:3 +msgid "DataType" +msgstr "" + +#: of osgeo.gdal.Band.GetTiledVirtualMemArray:1 +msgid "" +"Return a NumPy array for the band, seen as a virtual memory mapping with " +"a tile organization. An element is accessed with " +"array[tiley][tilex][y][x]. Any reference to the array must be dropped " +"before the last reference to the related dataset is also dropped." +msgstr "" + +#: of osgeo.gdal.Band.GetVirtualMemArray:1 +#: osgeo.gdal.Band.GetVirtualMemAutoArray:1 +msgid "" +"Return a NumPy array for the band, seen as a virtual memory mapping. An " +"element is accessed with array[y][x]. Any reference to the array must be " +"dropped before the last reference to the related dataset is also dropped." +msgstr "" + +#: of osgeo.gdal.Band.XSize:3 +msgid "XSize" +msgstr "" + +#: of osgeo.gdal.Band.YSize:3 +msgid "YSize" +msgstr "" + +#: ../../source/api/python/raster_api.rst:67 +msgid "Other" +msgstr "" + +#: of osgeo.gdal.RasterAttributeTable:1 +msgid "Proxy of C++ GDALRasterAttributeTableShadow class." +msgstr "" + +#: of osgeo.gdal.ColorTable:1 +msgid "Proxy of C++ GDALColorTableShadow class." +msgstr "" + +#: of osgeo.gdal.ColorEntry:1 +msgid "Proxy of C++ GDALColorEntry class." +msgstr "" + +#: of osgeo.gdal.ColorEntry.c1:1 osgeo.gdal.ColorEntry.c2:1 +#: osgeo.gdal.ColorEntry.c3:1 osgeo.gdal.ColorEntry.c4:1 +msgid "short" +msgstr "" + +#: of osgeo.gdal.ColorEntry.c1:3 +msgid "c1" +msgstr "" + +#: of osgeo.gdal.ColorEntry.c2:3 +msgid "c2" +msgstr "" + +#: of osgeo.gdal.ColorEntry.c3:3 +msgid "c3" +msgstr "" + +#: of osgeo.gdal.ColorEntry.c4:3 +msgid "c4" +msgstr "" + +#: of osgeo.gdal.GCP:1 +msgid "Proxy of C++ GDAL_GCP class." +msgstr "" + +#: of osgeo.gdal.GCP.GCPLine:3 +msgid "GCPLine" +msgstr "" + +#: of osgeo.gdal.GCP.GCPPixel:3 +msgid "GCPPixel" +msgstr "" + +#: of osgeo.gdal.GCP.GCPX:3 +msgid "GCPX" +msgstr "" + +#: of osgeo.gdal.GCP.GCPY:3 +msgid "GCPY" +msgstr "" + +#: of osgeo.gdal.GCP.GCPZ:3 +msgid "GCPZ" +msgstr "" + +#: of osgeo.gdal.GCP.Id:3 +msgid "Id" +msgstr "" + +#: of osgeo.gdal.GCP.Info:3 +msgid "Info" +msgstr "" + +#: ../../source/api/python/spatial_ref_api.rst:9 +msgid "Python Spatial Reference System API" +msgstr "" + +#: ../../source/api/python/spatial_ref_api.rst:11 +msgid "" +"This page contains classes, methods and functions that relate to spatial " +"reference systems:" +msgstr "" + +#: ../../source/api/python/spatial_ref_api.rst:13 +msgid "`SpatialReference`_" +msgstr "" + +#: ../../source/api/python/spatial_ref_api.rst:14 +msgid "`CoordinateTransformation`_" +msgstr "" + +#: ../../source/api/python/spatial_ref_api.rst:17 +msgid "SpatialReference" +msgstr "" + +#: of osgeo.osr.SpatialReference:1 +msgid "Proxy of C++ OSRSpatialReferenceShadow class." +msgstr "" + +#: ../../source/api/python/spatial_ref_api.rst:25 +msgid "CoordinateTransformation" +msgstr "" + +#: of osgeo.osr.CoordinateTransformation:1 +msgid "Proxy of C++ OSRCoordinateTransformationShadow class." +msgstr "" + +#: of osgeo.osr.CoordinateTransformationOptions:1 +msgid "Proxy of C++ OGRCoordinateTransformationOptions class." +msgstr "" + +#: ../../source/api/python/utilities.rst:9 +msgid "Python Utilities" +msgstr "" + +#: ../../source/api/python/utilities.rst:12 +msgid "Raster Utilities" +msgstr "" + +#: of osgeo.gdal.BuildVRT:1 +msgid "Build a VRT from a list of datasets." +msgstr "" + +#: of osgeo.gdal.BuildVRT:3 +msgid "Output dataset name." +msgstr "" + +#: of osgeo.gdal.BuildVRT:4 +msgid "" +"An array of Dataset objects or filenames, or a Dataset object or a " +"filename." +msgstr "" + +#: of osgeo.gdal.BuildVRT:5 +msgid "" +"options: return of gdal.BuildVRTOptions(), string or array of strings, " +"other keywords arguments of gdal.BuildVRTOptions(). If options is " +"provided as a gdal.BuildVRTOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:1 +msgid "Create a BuildVRTOptions() object that can be passed to gdal.BuildVRT()" +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:3 osgeo.gdal.DEMProcessingOptions:3 +#: osgeo.gdal.GridOptions:3 osgeo.gdal.MultiDimTranslateOptions:3 +#: osgeo.gdal.NearblackOptions:3 osgeo.gdal.RasterizeOptions:3 +#: osgeo.gdal.TranslateOptions:3 osgeo.gdal.VectorTranslateOptions:3 +#: osgeo.gdal.WarpOptions:3 +msgid "" +"can be be an array of strings, a string or let empty and filled from " +"other keywords." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:5 +msgid "'highest', 'lowest', 'average', 'user'." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:6 +msgid "output bounds as (minX, minY, maxX, maxY) in target SRS." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:8 osgeo.gdal.BuildVRTOptions:9 +msgid "output resolution in target SRS." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:10 +msgid "whether to force output bounds to be multiple of output resolution." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:11 +msgid "" +"whether each source file goes into a separate stacked band in the VRT " +"band." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:12 +msgid "array of band numbers (index start at 1)." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:13 +msgid "" +"whether to add an alpha mask band to the VRT when the source raster have " +"none." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:14 +msgid "resampling mode." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:15 +msgid "assigned output SRS." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:16 +msgid "" +"whether to accept input datasets have not the same projection. Note: they" +" will *not* be reprojected." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:18 +msgid "source nodata value(s)." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:19 +msgid "nodata values at the VRT band level." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:20 +msgid "whether to make the VRT band not report the NoData value." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:21 +msgid "set to True if warnings should be failures" +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:22 +msgid "callback method." +msgstr "" + +#: of osgeo.gdal.BuildVRTOptions:23 +msgid "user data for callback." +msgstr "" + +#: of osgeo.gdal.DEMProcessing:1 +msgid "Apply a DEM processing." +msgstr "" + +#: of osgeo.gdal.DEMProcessing:3 osgeo.gdal.Grid:3 +#: osgeo.gdal.MultiDimTranslate:3 osgeo.gdal.Translate:3 +msgid "Output dataset name" +msgstr "" + +#: of osgeo.gdal.DEMProcessing:4 osgeo.gdal.Grid:4 osgeo.gdal.Info:3 +#: osgeo.gdal.MultiDimInfo:3 osgeo.gdal.Nearblack:4 osgeo.gdal.Rasterize:4 +#: osgeo.gdal.Translate:4 osgeo.gdal.VectorTranslate:4 +msgid "a Dataset object or a filename" +msgstr "" + +#: of osgeo.gdal.DEMProcessing:5 +msgid "" +"one of \"hillshade\", \"slope\", \"aspect\", \"color-relief\", \"TRI\", " +"\"TPI\", \"Roughness\"" +msgstr "" + +#: of osgeo.gdal.DEMProcessing:6 +msgid "" +"options: return of gdal.DEMProcessingOptions(), string or array of " +"strings, other keywords arguments of gdal.DEMProcessingOptions(). If " +"options is provided as a gdal.DEMProcessingOptions() object, other " +"keywords are ignored." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:1 +msgid "" +"Create a DEMProcessingOptions() object that can be passed to " +"gdal.DEMProcessing()" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:4 +msgid "" +"(mandatory for \"color-relief\") name of file that contains palette " +"definition for the \"color-relief\" processing." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:5 osgeo.gdal.GridOptions:4 +#: osgeo.gdal.MultiDimTranslateOptions:4 osgeo.gdal.NearblackOptions:4 +#: osgeo.gdal.RasterizeOptions:4 osgeo.gdal.TranslateOptions:4 +#: osgeo.gdal.WarpOptions:4 +msgid "output format (\"GTiff\", etc...)" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:6 osgeo.gdal.GridOptions:8 +#: osgeo.gdal.MultiDimTranslateOptions:5 osgeo.gdal.NearblackOptions:5 +#: osgeo.gdal.RasterizeOptions:6 osgeo.gdal.TranslateOptions:14 +#: osgeo.gdal.WarpOptions:23 +msgid "list of creation options" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:7 +msgid "whether to compute values at raster edges." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:8 +msgid "" +"'Horn' (default) or 'ZevenbergenThorne' for hillshade, slope or aspect. " +"'Wilson' (default) or 'Riley' for TRI" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:9 +msgid "source band number to use" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:10 +msgid "" +"(hillshade only) vertical exaggeration used to pre-multiply the " +"elevations." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:11 +msgid "ratio of vertical units to horizontal." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:12 +msgid "" +"(hillshade only) azimuth of the light, in degrees. 0 if it comes from the" +" top of the raster, 90 from the east, ... The default value, 315, should " +"rarely be changed as it is the value generally used to generate shaded " +"maps." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:13 +msgid "" +"(hillshade only) altitude of the light, in degrees. 90 if the light comes" +" from above the DEM, 0 if it is raking light." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:14 +msgid "" +"(hillshade only) whether to compute combined shading, a combination of " +"slope and oblique shading. Only one of combined, multiDirectional and " +"igor can be specified." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:15 +msgid "" +"(hillshade only) whether to compute multi-directional shading. Only one " +"of combined, multiDirectional and igor can be specified." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:16 +msgid "" +"(hillshade only) whether to use Igor's hillshading from Maperitive. Only" +" one of combined, multiDirectional and igor can be specified." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:17 +msgid "(slope only) \"degree\" or \"percent\"." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:18 +msgid "" +"(aspect only) whether to return trigonometric angle instead of azimuth. " +"Thus 0deg means East, 90deg North, 180deg West, 270deg South." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:19 +msgid "" +"(aspect only) whether to return 0 for flat areas with slope=0, instead of" +" -9999." +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:20 +msgid "" +"adds an alpha band to the output file (only for processing = 'color-" +"relief')" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:21 +msgid "" +"(color-relief only) Determines how color entries are selected from an " +"input value. Can be \"nearest_color_entry\", \"exact_color_entry\" or " +"\"linear_interpolation\". Defaults to \"linear_interpolation\"" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:22 osgeo.gdal.GridOptions:26 +#: osgeo.gdal.MultiDimTranslateOptions:14 osgeo.gdal.NearblackOptions:12 +#: osgeo.gdal.RasterizeOptions:41 osgeo.gdal.TranslateOptions:34 +#: osgeo.gdal.VectorTranslateOptions:31 osgeo.gdal.WarpOptions:42 +msgid "callback method" +msgstr "" + +#: of osgeo.gdal.DEMProcessingOptions:23 osgeo.gdal.GridOptions:27 +#: osgeo.gdal.MultiDimTranslateOptions:15 osgeo.gdal.NearblackOptions:13 +#: osgeo.gdal.RasterizeOptions:42 osgeo.gdal.TranslateOptions:35 +#: osgeo.gdal.VectorTranslateOptions:32 osgeo.gdal.WarpOptions:43 +msgid "user data for callback" +msgstr "" + +#: of osgeo.gdal.Grid:1 +msgid "Create raster from the scattered data." +msgstr "" + +#: of osgeo.gdal.Grid:5 +msgid "" +"options: return of gdal.GridOptions(), string or array of strings, other " +"keywords arguments of gdal.GridOptions() If options is provided as a " +"gdal.GridOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.GridOptions:1 +msgid "Create a GridOptions() object that can be passed to gdal.Grid()" +msgstr "" + +#: of osgeo.gdal.GridOptions:5 osgeo.gdal.RasterizeOptions:5 +#: osgeo.gdal.TranslateOptions:5 osgeo.gdal.WarpOptions:17 +msgid "output type (gdalconst.GDT_Byte, etc...)" +msgstr "" + +#: of osgeo.gdal.GridOptions:6 osgeo.gdal.RasterizeOptions:11 +#: osgeo.gdal.TranslateOptions:8 osgeo.gdal.WarpOptions:10 +msgid "width of the output raster in pixel" +msgstr "" + +#: of osgeo.gdal.GridOptions:7 osgeo.gdal.RasterizeOptions:12 +#: osgeo.gdal.TranslateOptions:9 osgeo.gdal.WarpOptions:11 +msgid "height of the output raster in pixel" +msgstr "" + +#: of osgeo.gdal.GridOptions:9 osgeo.gdal.TranslateOptions:22 +msgid "assigned output bounds: [ulx, uly, lrx, lry]" +msgstr "" + +#: of osgeo.gdal.GridOptions:11 osgeo.gdal.RasterizeOptions:9 +#: osgeo.gdal.TranslateOptions:24 +msgid "assigned output SRS" +msgstr "" + +#: of osgeo.gdal.GridOptions:12 osgeo.gdal.RasterizeOptions:16 +msgid "nodata value" +msgstr "" + +#: of osgeo.gdal.GridOptions:13 +msgid "" +"e.g " +"\"invdist:power=2.0:smoothing=0.0:radius1=0.0:radius2=0.0:angle=0.0:max_points=0:min_points=0:nodata=0.0\"" +msgstr "" + +#: of osgeo.gdal.GridOptions:14 osgeo.gdal.VectorTranslateOptions:21 +msgid "list of layers to convert" +msgstr "" + +#: of osgeo.gdal.GridOptions:15 osgeo.gdal.RasterizeOptions:36 +#: osgeo.gdal.VectorTranslateOptions:10 +msgid "SQL statement to apply to the source dataset" +msgstr "" + +#: of osgeo.gdal.GridOptions:16 osgeo.gdal.RasterizeOptions:38 +#: osgeo.gdal.VectorTranslateOptions:12 +msgid "WHERE clause to apply to source layer(s)" +msgstr "" + +#: of osgeo.gdal.GridOptions:17 osgeo.gdal.VectorTranslateOptions:17 +msgid "spatial filter as (minX, minY, maxX, maxY) bounding box" +msgstr "" + +#: of osgeo.gdal.GridOptions:18 +msgid "" +"Identifies an attribute field on the features to be used to get a Z value" +" from. This value overrides Z value read from feature geometry record." +msgstr "" + +#: of osgeo.gdal.GridOptions:20 +msgid "" +"Addition to the attribute field on the features to be used to get a Z " +"value from. The addition should be the same unit as Z value. The result " +"value will be Z value + Z increase value. The default value is 0." +msgstr "" + +#: of osgeo.gdal.GridOptions:23 +msgid "" +"Multiplication ratio for Z field. This can be used for shift from e.g. " +"foot to meters or from elevation to deep. The result value will be (Z " +"value + Z increase value) * Z multiply value. The default value is 1." +msgstr "" + +#: of osgeo.gdal.Info:1 osgeo.gdal.MultiDimInfo:1 +msgid "Return information on a dataset." +msgstr "" + +#: of osgeo.gdal.Info:4 +msgid "" +"options: return of gdal.InfoOptions(), string or array of strings other " +"keywords arguments of gdal.InfoOptions(). If options is provided as a " +"gdal.InfoOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.InfoOptions:1 +msgid "" +"Create a InfoOptions() object that can be passed to gdal.Info() options " +"can be be an array of strings, a string or let empty and filled from " +"other keywords." +msgstr "" + +#: of osgeo.gdal.Nearblack:1 +msgid "Convert nearly black/white borders to exact value." +msgstr "" + +#: of osgeo.gdal.Nearblack:3 osgeo.gdal.Rasterize:3 +#: osgeo.gdal.VectorTranslate:3 osgeo.gdal.Warp:3 +msgid "Output dataset name or object" +msgstr "" + +#: of osgeo.gdal.Nearblack:5 +msgid "" +"options: return of gdal.NearblackOptions(), string or array of strings, " +"other keywords arguments of gdal.NearblackOptions(). If options is " +"provided as a gdal.NearblackOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.NearblackOptions:1 +msgid "Create a NearblackOptions() object that can be passed to gdal.Nearblack()" +msgstr "" + +#: of osgeo.gdal.NearblackOptions:6 +msgid "" +"whether to search for nearly white (255) pixels instead of nearly black " +"pixels." +msgstr "" + +#: of osgeo.gdal.NearblackOptions:7 +msgid "" +"list of colors to search for, e.g. ((0,0,0),(255,255,255)). The pixels " +"that are considered as the collar are set to 0" +msgstr "" + +#: of osgeo.gdal.NearblackOptions:8 +msgid "" +"number of non-black (or other searched colors specified with white / " +"colors) pixels that can be encountered before the giving up search " +"inwards. Defaults to 2." +msgstr "" + +#: of osgeo.gdal.NearblackOptions:9 +msgid "" +"select how far from black, white or custom colors the pixel values can be" +" and still considered near black, white or custom color. Defaults to 15." +msgstr "" + +#: of osgeo.gdal.NearblackOptions:10 +msgid "adds an alpha band to the output file." +msgstr "" + +#: of osgeo.gdal.NearblackOptions:11 +msgid "adds a mask band to the output file." +msgstr "" + +#: of osgeo.gdal.Rasterize:1 +msgid "Burns vector geometries into a raster" +msgstr "" + +#: of osgeo.gdal.Rasterize:5 +msgid "" +"options: return of gdal.RasterizeOptions(), string or array of strings, " +"other keywords arguments of gdal.RasterizeOptions() If options is " +"provided as a gdal.RasterizeOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:1 +msgid "Create a RasterizeOptions() object that can be passed to gdal.Rasterize()" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:7 +msgid "assigned output bounds: [minx, miny, maxx, maxy]" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:10 osgeo.gdal.WarpOptions:31 +msgid "list of transformer options" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:13 osgeo.gdal.RasterizeOptions:14 +#: osgeo.gdal.WarpOptions:7 osgeo.gdal.WarpOptions:8 +msgid "output resolution in target SRS" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:15 osgeo.gdal.WarpOptions:9 +msgid "whether to force output bounds to be multiple of output resolution" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:17 +msgid "" +"Value or list of values to pre-initialize the output image bands with. " +"However, it is not marked as the nodata value in the output file. If " +"only one value is given, the same value is used in all the bands." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:19 +msgid "Value or list of values to pre-initialize the output image bands with." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:19 +msgid "However, it is not marked as the nodata value in the output file." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:20 +msgid "If only one value is given, the same value is used in all the bands." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:21 +msgid "list of output bands to burn values into" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:22 +msgid "" +"whether to invert rasterization, i.e. burn the fixed burn value, or the " +"burn value associated with the first feature into all parts of the image " +"not inside the provided a polygon." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:25 +msgid "" +"whether to enable the ALL_TOUCHED rasterization option so that all pixels" +" touched by lines or polygons will be updated, not just those on the line" +" render path, or whose center point is within the polygon." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:28 +msgid "" +"list of fixed values to burn into each band for all objects. Excusive " +"with attribute." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:30 +msgid "" +"identifies an attribute field on the features to be used for a burn-in " +"value. The value will be burned into all output bands. Excusive with " +"burnValues." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:32 +msgid "" +"whether to indicate that a burn value should be extracted from the \"Z\" " +"values of the feature. These values are added to the burn value given by " +"burnValues or attribute if provided. As of now, only points and lines are" +" drawn in 3D." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:35 +msgid "list of layers from the datasource that will be used for input features." +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:37 osgeo.gdal.VectorTranslateOptions:11 +msgid "SQL dialect ('OGRSQL', 'SQLITE', ...)" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:39 +msgid "optimization mode ('RASTER', 'VECTOR')" +msgstr "" + +#: of osgeo.gdal.RasterizeOptions:40 +msgid "set to True to use additive mode instead of replace when burning values" +msgstr "" + +#: of osgeo.gdal.Translate:1 +msgid "Convert a dataset." +msgstr "" + +#: of osgeo.gdal.Translate:5 +msgid "" +"options: return of gdal.TranslateOptions(), string or array of strings " +"other keywords arguments of gdal.TranslateOptions(). If options is " +"provided as a gdal.TranslateOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.TranslateOptions:1 +msgid "Create a TranslateOptions() object that can be passed to gdal.Translate()" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:6 +msgid "array of band numbers (index start at 1)" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:7 +msgid "mask band to generate or not (\"none\", \"auto\", \"mask\", 1, ...)" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:10 +msgid "width of the output raster in percentage (100 = original width)" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:11 +msgid "height of the output raster in percentage (100 = original height)" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:12 +msgid "output horizontal resolution" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:13 +msgid "output vertical resolution" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:15 +msgid "subwindow in pixels to extract: [left_x, top_y, width, height]" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:16 +msgid "subwindow in projected coordinates to extract: [ulx, uly, lrx, lry]" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:17 +msgid "SRS in which projWin is expressed" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:18 +msgid "strict mode" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:19 +msgid "unscale values with scale and offset metadata" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:20 +msgid "" +"list of scale parameters, each of the form [src_min,src_max] or " +"[src_min,src_max,dst_min,dst_max]" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:21 +msgid "list of exponentiation parameters" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:23 +msgid "list of metadata options" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:25 +msgid "ignore GCP in the raster" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:26 +msgid "list of GCPs" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:27 +msgid "nodata value (or \"none\" to unset it)" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:28 +msgid "Color palette expansion mode: \"gray\", \"rgb\", \"rgba\"" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:29 +msgid "whether to calculate statistics" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:30 +msgid "whether to write source RAT" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:31 +msgid "whether to copy XMP metadata" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:32 osgeo.gdal.WarpOptions:22 +msgid "resampling mode" +msgstr "" + +#: of osgeo.gdal.TranslateOptions:33 osgeo.gdal.WarpOptions:41 +msgid "To specify which overview level of source files must be used" +msgstr "" + +#: of osgeo.gdal.Warp:1 +msgid "Warp one or several datasets." +msgstr "" + +#: of osgeo.gdal.MultiDimTranslate:4 osgeo.gdal.Warp:4 +msgid "" +"an array of Dataset objects or filenames, or a Dataset object or a " +"filename" +msgstr "" + +#: of osgeo.gdal.Warp:5 +msgid "" +"options: return of gdal.WarpOptions(), string or array of strings, other " +"keywords arguments of gdal.WarpOptions(). If options is provided as a " +"gdal.WarpOptions() object, other keywords are ignored." +msgstr "" + +#: of osgeo.gdal.WarpOptions:1 +msgid "Create a WarpOptions() object that can be passed to gdal.Warp()" +msgstr "" + +#: of osgeo.gdal.WarpOptions:5 +msgid "output bounds as (minX, minY, maxX, maxY) in target SRS" +msgstr "" + +#: of osgeo.gdal.WarpOptions:6 +msgid "" +"SRS in which output bounds are expressed, in the case they are not " +"expressed in dstSRS" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:6 osgeo.gdal.WarpOptions:12 +msgid "source SRS" +msgstr "" + +#: of osgeo.gdal.WarpOptions:13 +msgid "output SRS" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:8 osgeo.gdal.WarpOptions:14 +msgid "coordinate operation as a PROJ string or WKT string" +msgstr "" + +#: of osgeo.gdal.WarpOptions:15 +msgid "" +"whether to force the last band of the input dataset to be considered as " +"an alpha band" +msgstr "" + +#: of osgeo.gdal.WarpOptions:16 +msgid "whether to force the creation of an output alpha band" +msgstr "" + +#: of osgeo.gdal.WarpOptions:18 +msgid "working type (gdalconst.GDT_Byte, etc...)" +msgstr "" + +#: of osgeo.gdal.WarpOptions:19 +msgid "list of warping options" +msgstr "" + +#: of osgeo.gdal.WarpOptions:20 +msgid "error threshold for approximation transformer (in pixels)" +msgstr "" + +#: of osgeo.gdal.WarpOptions:21 +msgid "size of working buffer in MB" +msgstr "" + +#: of osgeo.gdal.WarpOptions:24 +msgid "source nodata value(s)" +msgstr "" + +#: of osgeo.gdal.WarpOptions:25 +msgid "output nodata value(s)" +msgstr "" + +#: of osgeo.gdal.WarpOptions:26 +msgid "whether to multithread computation and I/O operations" +msgstr "" + +#: of osgeo.gdal.WarpOptions:27 +msgid "whether to use Thin Plate Spline GCP transformer" +msgstr "" + +#: of osgeo.gdal.WarpOptions:28 +msgid "whether to use RPC transformer" +msgstr "" + +#: of osgeo.gdal.WarpOptions:29 +msgid "whether to use GeoLocation array transformer" +msgstr "" + +#: of osgeo.gdal.WarpOptions:30 +msgid "order of polynomial GCP interpolation" +msgstr "" + +#: of osgeo.gdal.WarpOptions:32 +msgid "cutline dataset name" +msgstr "" + +#: of osgeo.gdal.WarpOptions:33 +msgid "cutline layer name" +msgstr "" + +#: of osgeo.gdal.WarpOptions:34 +msgid "cutline WHERE clause" +msgstr "" + +#: of osgeo.gdal.WarpOptions:35 +msgid "cutline SQL statement" +msgstr "" + +#: of osgeo.gdal.WarpOptions:36 +msgid "cutline blend distance in pixels" +msgstr "" + +#: of osgeo.gdal.WarpOptions:37 +msgid "whether to use cutline extent for output bounds" +msgstr "" + +#: of osgeo.gdal.WarpOptions:38 +msgid "whether to copy source metadata" +msgstr "" + +#: of osgeo.gdal.WarpOptions:39 +msgid "metadata data conflict value" +msgstr "" + +#: of osgeo.gdal.WarpOptions:40 +msgid "whether to force color interpretation of input bands to output bands" +msgstr "" + +#: ../../source/api/python/utilities.rst:75 +msgid "Multidimensional Raster Utilities" +msgstr "" + +#: of osgeo.gdal.MultiDimInfo:4 +msgid "" +"options: return of gdal.MultiDimInfoOptions(), string or array of strings" +" other keywords arguments of gdal.MultiDimInfoOptions(). If options is " +"provided as a gdal.MultiDimInfoOptions() object, other keywords are " +"ignored." +msgstr "" + +#: of osgeo.gdal.MultiDimInfoOptions:1 +msgid "" +"Create a MultiDimInfoOptions() object that can be passed to " +"gdal.MultiDimInfo() options can be be an array of strings, a string or " +"let empty and filled from other keywords." +msgstr "" + +#: of osgeo.gdal.MultiDimTranslate:1 +msgid "MultiDimTranslate one or several datasets." +msgstr "" + +#: of osgeo.gdal.MultiDimTranslate:5 +msgid "" +"options: return of gdal.MultiDimTranslateOptions(), string or array of " +"strings other keywords arguments of gdal.MultiDimTranslateOptions(). If " +"options is provided as a gdal.MultiDimTranslateOptions() object, other " +"keywords are ignored." +msgstr "" + +#: of osgeo.gdal.MultiDimTranslateOptions:1 +msgid "" +"Create a MultiDimTranslateOptions() object that can be passed to " +"gdal.MultiDimTranslate()" +msgstr "" + +#: of osgeo.gdal.MultiDimTranslateOptions:6 +msgid "" +"list of array specifications, each of them being an array name or " +"\"name={src_array_name},dstname={dst_name},transpose=[1,0],view=[:,::-1]\"" +msgstr "" + +#: of osgeo.gdal.MultiDimTranslateOptions:8 +msgid "" +"list of group specifications, each of them being a group name or " +"\"name={src_array_name},dstname={dst_name},recursive=no\"" +msgstr "" + +#: of osgeo.gdal.MultiDimTranslateOptions:10 +msgid "" +"list of subset specifications, each of them being like " +"\"{dim_name}({min_val},{max_val})\" or \"{dim_name}({slice_va})\"" +msgstr "" + +#: of osgeo.gdal.MultiDimTranslateOptions:12 +msgid "" +"list of dimension scaling specifications, each of them being like " +"\"{dim_name}({scale_factor})\"" +msgstr "" + +#: ../../source/api/python/utilities.rst:86 +msgid "Vector Utilities" +msgstr "" + +#: of osgeo.gdal.VectorTranslate:1 +msgid "Convert one vector dataset" +msgstr "" + +#: of osgeo.gdal.VectorTranslate:5 +msgid "" +"options: return of gdal.VectorTranslateOptions(), string or array of " +"strings, other keywords arguments of gdal.VectorTranslateOptions(). If " +"options is provided as a gdal.VectorTranslateOptions() object, other " +"keywords are ignored." +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:1 +msgid "" +"Create a VectorTranslateOptions() object that can be passed to " +"gdal.VectorTranslate()" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:4 +msgid "format (\"ESRI Shapefile\", etc...)" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:5 +msgid "None for creation, 'update', 'append', 'upsert', 'overwrite'" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:7 +msgid "output SRS (with reprojection if reproject = True)" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:9 +msgid "whether to do reprojection" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:13 +msgid "list of fields to select" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:14 +msgid "" +"whether to add new fields found in source layers (to be used with " +"accessMode == 'append' or 'upsert')" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:15 +msgid "whether to drop NOT NULL constraints on newly created fields" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:16 +msgid "whether to treat empty string values as NULL" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:18 +msgid "" +"SRS in which the spatFilter is expressed. If not specified, it is assumed" +" to be the one of the layer(s)" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:19 +msgid "list of dataset creation options" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:20 +msgid "list of layer creation options" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:22 +msgid "output layer name" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:23 +msgid "output layer geometry type ('POINT', ....)" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:24 +msgid "output dimension ('XY', 'XYZ', 'XYM', 'XYZM', 'layer_dim')" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:25 +msgid "maximum distance between consecutive nodes of a line geometry" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:26 +msgid "run MakeValid() on geometries" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:27 +msgid "name of field to use to set the Z component of geometries" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:28 +msgid "" +"whether to create an additional field for each field associated with a " +"coded field domain." +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:29 +msgid "whether to skip failures" +msgstr "" + +#: of osgeo.gdal.VectorTranslateOptions:30 +msgid "maximum number of features to read per layer" +msgstr "" + +#: ../../source/api/python/vector_api.rst:9 +msgid "Python Vector API" +msgstr "" + +#: ../../source/api/python/vector_api.rst:11 +msgid "" +"This page contains classes, methods, functions that relate to the GDAL " +":ref:`vector_data_model`. The :py:class:`Driver` and :py:class:`Dataset` " +"classes, which applies to both vector and raster data, are documented " +"with the :ref:`python_raster_api`." +msgstr "" + +#: ../../source/api/python/vector_api.rst:13 +msgid "`Layer`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:14 +msgid "`Feature`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:15 +msgid "`Geometry`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:16 +msgid "`FeatureDefn`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:17 +msgid "`FieldDefn`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:18 +msgid "`GeomFieldDefn`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:19 +msgid "`FieldDomain`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:20 +msgid "`Relationship`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:21 +msgid "`StyleTable`_" +msgstr "" + +#: ../../source/api/python/vector_api.rst:24 +msgid "Layer" +msgstr "" + +#: of osgeo.ogr.Layer:1 +msgid "Proxy of C++ OGRLayerShadow class." +msgstr "" + +#: of osgeo.ogr.Layer.AlterFieldDefn:1 +msgid "Alter the definition of an existing field on a layer." +msgstr "" + +#: of osgeo.ogr.Layer.AlterFieldDefn:3 +msgid "For more details: :cpp:func:`OGR_L_AlterFieldDefn`" +msgstr "" + +#: of osgeo.ogr.Layer.AlterFieldDefn:5 +msgid "index of the field whose definition must be altered." +msgstr "" + +#: of osgeo.ogr.Layer.AlterFieldDefn:7 +msgid "new field definition" +msgstr "" + +#: of osgeo.ogr.Layer.AlterFieldDefn:9 +msgid "" +"Combination of :py:const:`osgeo.ogr.ALTER_NAME_FLAG`, " +":py:const:`osgeo.ogr.ALTER_TYPE_FLAG`, " +":py:const:`osgeo.ogr.ALTER_WIDTH_PRECISION_FLAG`, " +":py:const:`osgeo.ogr.ALTER_NULLABLE_FLAG` and " +":py:const:`osgeo.ogr.ALTER_DEFAULT_FLAG` to indicate which of the name " +"and/or type and/or width and precision fields and/or nullability from the" +" new field definition must be taken into account." +msgstr "" + +#: of osgeo.ogr.Layer.AlterFieldDefn:20 osgeo.ogr.Layer.CommitTransaction:5 +#: osgeo.ogr.Layer.CreateFeature:10 osgeo.ogr.Layer.CreateField:11 +#: osgeo.ogr.Layer.CreateGeomField:11 osgeo.ogr.Layer.DeleteField:8 +#: osgeo.ogr.Layer.ReorderField:12 osgeo.ogr.Layer.ReorderFields:10 +#: osgeo.ogr.Layer.RollbackTransaction:5 osgeo.ogr.Layer.StartTransaction:5 +#: osgeo.ogr.Layer.UpsertFeature:8 +msgid ":py:const:`osgeo.ogr.OGRERR_NONE` on success." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:1 +msgid "Clip off areas that are not covered by the method layer." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:3 +msgid "For more details: :cpp:func:`OGR_L_Clip`" +msgstr "" + +#: of osgeo.ogr.Layer.Clip:5 osgeo.ogr.Layer.Erase:5 osgeo.ogr.Layer.Identity:5 +#: osgeo.ogr.Layer.Intersection:5 osgeo.ogr.Layer.SymDifference:5 +#: osgeo.ogr.Layer.Union:7 osgeo.ogr.Layer.Update:5 +msgid "the method layer. Should not be None." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:7 osgeo.ogr.Layer.Erase:7 osgeo.ogr.Layer.Identity:7 +#: osgeo.ogr.Layer.Intersection:7 osgeo.ogr.Layer.SymDifference:7 +#: osgeo.ogr.Layer.Union:9 osgeo.ogr.Layer.Update:7 +msgid "" +"the layer where the features resulting from the operation are inserted. " +"Should not be None." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:10 osgeo.ogr.Layer.Erase:10 +#: osgeo.ogr.Layer.Identity:10 osgeo.ogr.Layer.Intersection:10 +#: osgeo.ogr.Layer.SymDifference:10 osgeo.ogr.Layer.Union:12 +#: osgeo.ogr.Layer.Update:10 +msgid "" +"List of options (empty list is allowed). For example " +"[\"PROMOTE_TO_MULTI=YES\"]." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:12 osgeo.ogr.Layer.Erase:12 +#: osgeo.ogr.Layer.Identity:12 osgeo.ogr.Layer.Intersection:12 +#: osgeo.ogr.Layer.SymDifference:12 osgeo.ogr.Layer.Union:14 +#: osgeo.ogr.Layer.Update:12 +msgid "" +"a GDALProgressFunc() compatible callback function for reporting progress " +"or None." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:15 osgeo.ogr.Layer.Erase:15 +#: osgeo.ogr.Layer.GetGeometryTypes:14 osgeo.ogr.Layer.Identity:15 +#: osgeo.ogr.Layer.Intersection:15 osgeo.ogr.Layer.SymDifference:15 +#: osgeo.ogr.Layer.Union:17 osgeo.ogr.Layer.Update:15 +msgid "Argument to be passed to 'callback'. May be None." +msgstr "" + +#: of osgeo.ogr.Layer.Clip:17 osgeo.ogr.Layer.Erase:17 +#: osgeo.ogr.Layer.Identity:17 osgeo.ogr.Layer.Intersection:17 +#: osgeo.ogr.Layer.SymDifference:17 osgeo.ogr.Layer.Union:19 +#: osgeo.ogr.Layer.Update:17 +msgid "" +"An error code if there was an error or the execution was interrupted, " +":py:const:`osgeo.ogr.OGRERR_NONE` otherwise." +msgstr "" + +#: of osgeo.ogr.Layer.CommitTransaction:1 +msgid "For datasources which support transactions, this commits a transaction." +msgstr "" + +#: of osgeo.ogr.Layer.CommitTransaction:3 +msgid "For more details: :cpp:func:`OGR_L_CommitTransaction`" +msgstr "" + +#: of osgeo.ogr.Layer.CreateFeature:1 +msgid "Create and write a new feature within a layer." +msgstr "" + +#: of osgeo.ogr.Layer.CreateFeature:3 +msgid "For more details: :cpp:func:`OGR_L_CreateFeature`" +msgstr "" + +#: of osgeo.ogr.Layer.CreateFeature:5 +msgid "" +"To create a feature, but set it if it exists see " +":py:meth:`.Layer.UpsertFeature`." +msgstr "" + +#: of osgeo.ogr.Layer.CreateFeature:7 osgeo.ogr.Layer.UpsertFeature:5 +msgid "The feature to write to disk." +msgstr "" + +#: of osgeo.ogr.Layer.CreateField:1 +msgid "Create a new field on a layer." +msgstr "" + +#: of osgeo.ogr.Layer.CreateField:3 +msgid "For more details: :cpp:func:`OGR_L_CreateField`" +msgstr "" + +#: of osgeo.ogr.Layer.CreateField:5 +msgid "The field definition to write to disk." +msgstr "" + +#: of osgeo.ogr.Layer.CreateField:7 osgeo.ogr.Layer.CreateGeomField:7 +msgid "" +"If True, the field may be created in a slightly different form depending " +"on the limitations of the format driver." +msgstr "" + +#: of osgeo.ogr.Layer.CreateFields:1 +msgid "Create a list of fields on the Layer" +msgstr "" + +#: of osgeo.ogr.Layer.CreateGeomField:1 +msgid "Create a new geometry field on a layer." +msgstr "" + +#: of osgeo.ogr.Layer.CreateGeomField:3 +msgid "For more details: :cpp:func:`OGR_L_CreateGeomField`" +msgstr "" + +#: of osgeo.ogr.Layer.CreateGeomField:5 +msgid "The geometry field definition to write to disk." +msgstr "" + +#: of osgeo.ogr.Layer.DeleteFeature:1 +msgid "Delete feature from layer." +msgstr "" + +#: of osgeo.ogr.Layer.DeleteFeature:3 +msgid "For more details: :cpp:func:`OGR_L_DeleteFeature`" +msgstr "" + +#: of osgeo.ogr.Layer.DeleteFeature:5 +msgid "The feature id to be deleted from the layer" +msgstr "" + +#: of osgeo.ogr.Layer.DeleteFeature:8 +msgid "" +":py:const:`osgeo.ogr.OGRERR_NONE` if the operation works, otherwise an " +"appropriate error code (e.g " +":py:const:`osgeo.ogr.OGRERR_NON_EXISTING_FEATURE`) if the feature does " +"not exist." +msgstr "" + +#: of osgeo.ogr.Layer.DeleteField:1 +msgid "Delete an existing field on a layer." +msgstr "" + +#: of osgeo.ogr.Layer.DeleteField:3 +msgid "For more details: :cpp:func:`OGR_L_DeleteField`" +msgstr "" + +#: of osgeo.ogr.Layer.DeleteField:5 +msgid "index of the field to delete." +msgstr "" + +#: of osgeo.ogr.Layer.Erase:1 +msgid "Remove areas that are covered by the method layer." +msgstr "" + +#: of osgeo.ogr.Layer.Erase:3 +msgid "For more details: :cpp:func:`OGR_L_Erase`" +msgstr "" + +#: of osgeo.ogr.Layer.FindFieldIndex:1 +msgid "Find the index of field in a layer." +msgstr "" + +#: of osgeo.ogr.Layer.FindFieldIndex:3 +msgid "For more details: :cpp:func:`OGR_L_FindFieldIndex`" +msgstr "" + +#: of osgeo.ogr.Layer.FindFieldIndex:5 +msgid "field index, or -1 if the field doesn't exist" +msgstr "" + +#: of osgeo.ogr.Layer.GetArrowStreamAsNumPy:1 +msgid "" +"Return an ArrowStream as NumPy Array objects. A specific option to this " +"method is USE_MASKED_ARRAYS=YES/NO (default is YES)." +msgstr "" + +#: of osgeo.ogr.Layer.GetArrowStreamAsPyArrow:1 +msgid "Return an ArrowStream as PyArrow Schema and Array objects" +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:1 +msgid "Fetch the extent of this layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:3 osgeo.ogr.Layer.SetSpatialFilter:3 +#: osgeo.ogr.Layer.SetSpatialFilterRect:3 +msgid "For more details:" +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:5 +msgid ":cpp:func:`OGR_L_GetExtent`" +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:6 +msgid ":cpp:func:`OGR_L_GetExtentEx`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:6 osgeo.ogr.Geometry.GetEnvelope3D:6 +#: osgeo.ogr.Layer.GetExtent:8 +msgid "Check the return order of the bounds." +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:10 +msgid "" +"Flag indicating whether the extent should be computed even if it is " +"expensive." +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:13 +msgid "Whether None can be returned in the response." +msgstr "" + +#: of osgeo.ogr.Layer.GetExtent:15 +msgid "" +"Ithe index of the geometry field on which to compute the extent. Can be " +"iterated over using :py:func:`range` and :py:func:`GetGeomFieldCount`." +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:8 osgeo.ogr.Layer.GetExtent:19 +msgid "" +"* **minx** (*float*) * **maxx** (*float*) * **miny** (*float*) * **maxy**" +" (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:8 osgeo.ogr.Geometry.GetEnvelope3D:8 +#: osgeo.ogr.Layer.GetExtent:19 +msgid "**minx** (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:9 osgeo.ogr.Geometry.GetEnvelope3D:9 +#: osgeo.ogr.Layer.GetExtent:20 +msgid "**maxx** (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:10 osgeo.ogr.Geometry.GetEnvelope3D:10 +#: osgeo.ogr.Layer.GetExtent:21 +msgid "**miny** (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:11 osgeo.ogr.Geometry.GetEnvelope3D:11 +#: osgeo.ogr.Layer.GetExtent:22 +msgid "**maxy** (*float*)" +msgstr "" + +#: of osgeo.ogr.Layer.GetFIDColumn:1 +msgid "" +"This method returns the name of the underlying database column being used" +" as the FID column, or '' if not supported." +msgstr "" + +#: of osgeo.ogr.Layer.GetFIDColumn:4 +msgid "For more details: :cpp:func:`OGR_L_GetFIDColumn`" +msgstr "" + +#: of osgeo.ogr.Layer.GetFIDColumn:6 +msgid "fid column name." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeature:1 +msgid "Fetch a feature by its identifier." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeature:3 +msgid "For more details: :cpp:func:`OGR_L_GetFeature`" +msgstr "" + +#: of osgeo.ogr.Layer.GetFeature:5 +msgid "" +"Use :py:func:`TestCapability` with (:py:const:`osgeo.ogr.OLCRandomRead`) " +"to establish if this layer supports efficient random access reading via " +":py:func:`GetFeature`; However, the call should always work if the " +"feature exists." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeature:9 +msgid "" +"Sequential reads (with :py:func:`GetNextFeature`) are generally " +"considered interrupted by a :py:func:`GetFeature` call." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeature:12 +msgid "The feature id of the feature to read." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeature:15 +msgid "" +"A new feature now owned by the caller, or None on failure. The returned " +"feature should be deleted with :py:func:`Destroy`." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeatureCount:1 +msgid "Fetch the feature count in this layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeatureCount:3 +msgid "For more details: :cpp:func:`OGR_L_GetFeatureCount`" +msgstr "" + +#: of osgeo.ogr.Layer.GetFeatureCount:5 +msgid "" +"Flag indicating whether the count should be computed even if it is " +"expensive." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeatureCount:9 +msgid "Feature count, -1 if count not known." +msgstr "" + +#: of osgeo.ogr.Layer.GetFeaturesRead:1 +msgid "For more details: :cpp:func:`OGR_L_GetFeaturesRead`" +msgstr "" + +#: of osgeo.ogr.Layer.GetGeomType:1 +msgid "Return the layer geometry type." +msgstr "" + +#: of osgeo.ogr.Layer.GetGeomType:3 +msgid "For more details: :cpp:func:`OGR_L_GetGeomType`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetGeometryType:5 osgeo.ogr.Layer.GetGeomType:5 +msgid "" +"The geometry type code. The types can be found with 'osgeo.ogr.wkb' " +"prefix. For example :py:const:`osgeo.ogr.wkbPolygon`." +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryColumn:1 +msgid "" +"This method returns the name of the underlying database column being used" +" as the geometry column, or '' if not supported." +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryColumn:4 +msgid "For more details: :cpp:func:`OGR_L_GetGeometryColumn`" +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryColumn:6 +msgid "geometry column name." +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryTypes:1 +msgid "Get actual geometry types found in features." +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryTypes:3 +msgid "For more details: :cpp:func:`OGR_L_GetGeometryTypes`" +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryTypes:5 +msgid "index of the geometry field" +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryTypes:7 +msgid "" +"0, or a combination of :py:const:`osgeo.ogr.GGT_COUNT_NOT_NEEDED`, " +":py:const:`osgeo.ogr.GGT_STOP_IF_MIXED` and " +":py:const:`osgeo.ogr.GGT_GEOMCOLLECTIONZ_TINZ`" +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryTypes:11 +msgid "" +"a GDALProgressFunc() compatible callback function for cancellation or " +"None." +msgstr "" + +#: of osgeo.ogr.Layer.GetGeometryTypes:16 +msgid "" +"A dictionary whose keys are :py:const:`osgeo.ogr.wkbXXXX` constants and " +"values the corresponding number of geometries of that type in the layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetLayerDefn:1 +msgid "Fetch the schema information for this layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetLayerDefn:3 +msgid "For more details: :cpp:func:`OGR_L_GetLayerDefn`" +msgstr "" + +#: of osgeo.ogr.Layer.GetLayerDefn:5 +msgid "The feature definition." +msgstr "" + +#: of osgeo.ogr.Layer.GetName:1 +msgid "Return the layer name." +msgstr "" + +#: of osgeo.ogr.Layer.GetName:3 +msgid "For more details: :cpp:func:`OGR_L_GetName`" +msgstr "" + +#: of osgeo.ogr.Layer.GetName:5 +msgid "The layer name" +msgstr "" + +#: of osgeo.ogr.Layer.GetNextFeature:1 +msgid "Fetch the next available feature from this layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetNextFeature:3 +msgid "For more details: :cpp:func:`OGR_L_GetNextFeature`" +msgstr "" + +#: of osgeo.ogr.Layer.GetNextFeature:5 +msgid "A feature or None if no more features are available." +msgstr "" + +#: of osgeo.ogr.Layer.GetRefCount:1 +msgid "For more details: :cpp:func:`OGR_L_GetRefCount`" +msgstr "" + +#: of osgeo.ogr.Layer.GetSpatialFilter:1 +msgid "This function returns the current spatial filter for this layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetSpatialFilter:3 +msgid "For more details: :cpp:func:`OGR_L_GetSpatialFilter`" +msgstr "" + +#: of osgeo.ogr.Layer.GetSpatialFilter:5 +msgid "The spatial filter geometry." +msgstr "" + +#: of osgeo.ogr.Layer.GetSpatialRef:1 +msgid "Fetch the spatial reference system for this layer." +msgstr "" + +#: of osgeo.ogr.Layer.GetSpatialRef:3 +msgid "For more details: :cpp:func:`OGR_L_GetSpatialRef`" +msgstr "" + +#: of osgeo.ogr.Layer.GetSpatialRef:5 +msgid "spatial reference, or None if there isn't one." +msgstr "" + +#: of osgeo.ogr.Layer.GetStyleTable:3 +msgid "For more details: :cpp:func:`OGR_L_GetStyleTable`" +msgstr "" + +#: of osgeo.ogr.Layer.Identity:1 +msgid "Identify the features of this layer with the ones from the identity layer." +msgstr "" + +#: of osgeo.ogr.Layer.Identity:3 +msgid "For more details: :cpp:func:`OGR_L_Identity`" +msgstr "" + +#: of osgeo.ogr.Layer.Intersection:1 +msgid "Intersection of two layers." +msgstr "" + +#: of osgeo.ogr.Layer.Intersection:3 +msgid "For more details: :cpp:func:`OGR_L_Intersection`" +msgstr "" + +#: of osgeo.ogr.Layer.ReorderField:1 +msgid "Reorder an existing field on a layer." +msgstr "" + +#: of osgeo.ogr.Layer.ReorderField:3 +msgid "For more details: :cpp:func:`OGR_L_ReorderField`" +msgstr "" + +#: of osgeo.ogr.Layer.ReorderField:5 +msgid "" +"previous position of the field to move. Must be in the range " +"[0,GetFieldCount()-1]." +msgstr "" + +#: of osgeo.ogr.Layer.ReorderField:8 +msgid "" +"new position of the field to move. Must be in the range " +"[0,GetFieldCount()-1]." +msgstr "" + +#: of osgeo.ogr.Layer.ReorderFields:1 +msgid "Reorder all the fields of a layer." +msgstr "" + +#: of osgeo.ogr.Layer.ReorderFields:3 +msgid "For more details: :cpp:func:`OGR_L_ReorderFields`" +msgstr "" + +#: of osgeo.ogr.Layer.ReorderFields:5 +msgid "" +"A list of GetLayerDefn().GetFieldCount() elements which is a permutation " +"of [0, GetLayerDefn().GetFieldCount()-1]." +msgstr "" + +#: of osgeo.ogr.Layer.ResetReading:1 +msgid "Reset feature reading to start on the first feature." +msgstr "" + +#: of osgeo.ogr.Layer.ResetReading:3 +msgid "For more details: :cpp:func:`OGR_L_ResetReading`" +msgstr "" + +#: of osgeo.ogr.Layer.RollbackTransaction:1 +msgid "" +"Roll back a datasource to its state before the start of the current " +"transaction." +msgstr "" + +#: of osgeo.ogr.Layer.RollbackTransaction:3 +msgid "For more details: :cpp:func:`OGR_L_RollbackTransaction`" +msgstr "" + +#: of osgeo.ogr.Layer.SetAttributeFilter:1 +msgid "Set a new attribute query." +msgstr "" + +#: of osgeo.ogr.Layer.SetAttributeFilter:3 +msgid "For more details: :cpp:func:`OGR_L_SetAttributeFilter`" +msgstr "" + +#: of osgeo.ogr.Layer.SetAttributeFilter:5 +msgid "query in restricted SQL WHERE format, or None to clear the current query." +msgstr "" + +#: of osgeo.ogr.Layer.SetAttributeFilter:9 +msgid "" +":py:const:`osgeo.ogr.OGRERR_NONE` if successfully installed, or an error " +"code if the query expression is in error, or some other failure occurs." +msgstr "" + +#: of osgeo.ogr.Layer.SetFeature:1 +msgid "Rewrite an existing feature." +msgstr "" + +#: of osgeo.ogr.Layer.SetFeature:3 +msgid "For more details: :cpp:func:`OGR_L_SetFeature`" +msgstr "" + +#: of osgeo.ogr.Layer.SetFeature:5 +msgid "" +"To set a feature, but create it if it doesn't exist see " +":py:meth:`.Layer.UpsertFeature`." +msgstr "" + +#: of osgeo.ogr.Layer.SetFeature:7 +msgid "The feature to write." +msgstr "" + +#: of osgeo.ogr.Layer.SetFeature:10 +msgid "" +":py:const:`osgeo.ogr.OGRERR_NONE` if the operation works, otherwise an " +"appropriate error code (e.g " +":py:const:`osgeo.ogr.OGRERR_NON_EXISTING_FEATURE` if the feature does not" +" exist)." +msgstr "" + +#: of osgeo.ogr.Layer.SetIgnoredFields:1 +msgid "Set which fields can be omitted when retrieving features from the layer." +msgstr "" + +#: of osgeo.ogr.Layer.SetIgnoredFields:4 +msgid "For more details: :cpp:func:`OGR_L_SetIgnoredFields`" +msgstr "" + +#: of osgeo.ogr.Layer.SetIgnoredFields:6 +msgid "" +"A list of field names. If an empty list is passed, the ignored list is " +"cleared." +msgstr "" + +#: of osgeo.ogr.Layer.SetIgnoredFields:10 +msgid "" +":py:const:`osgeo.ogr.OGRERR_NONE` if all field names have been resolved " +"(even if the driver does not support this method)" +msgstr "" + +#: of osgeo.ogr.Layer.SetNextByIndex:1 +msgid "Move read cursor to the nIndex'th feature in the current resultset." +msgstr "" + +#: of osgeo.ogr.Layer.SetNextByIndex:3 +msgid "For more details: :cpp:func:`OGR_L_SetNextByIndex`" +msgstr "" + +#: of osgeo.ogr.Layer.SetNextByIndex:5 +msgid "The index indicating how many steps into the result set to seek." +msgstr "" + +#: of osgeo.ogr.Layer.SetNextByIndex:8 +msgid ":py:const:`osgeo.ogr.OGRERR_NONE` on success or an error code." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilter:1 +msgid "Set a new spatial filter." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilter:5 +msgid ":cpp:func:`OGR_L_SetSpatialFilter`" +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilter:6 +msgid ":cpp:func:`OGR_L_SetSpatialFilterEx`" +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilter:8 osgeo.ogr.Layer.SetSpatialFilterRect:8 +msgid "index of the geometry field on which the spatial filter operates." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilter:10 +msgid "" +"The geometry to use as a filtering region. None may be passed indicating " +"that the current spatial filter should be cleared, but no new one " +"instituted." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:1 +msgid "Set a new rectangular spatial filter." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:5 +msgid ":cpp:func:`OGR_L_SetSpatialFilterRect`" +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:6 +msgid ":cpp:func:`OGR_L_SetSpatialFilterRectEx`" +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:10 +msgid "the minimum X coordinate for the rectangular region." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:12 +msgid "the minimum Y coordinate for the rectangular region." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:14 +msgid "the maximum X coordinate for the rectangular region." +msgstr "" + +#: of osgeo.ogr.Layer.SetSpatialFilterRect:16 +msgid "the maximum Y coordinate for the rectangular region." +msgstr "" + +#: of osgeo.ogr.Layer.SetStyleTable:3 +msgid "For more details: :cpp:func:`OGR_L_SetStyleTable`" +msgstr "" + +#: of osgeo.ogr.Layer.StartTransaction:1 +msgid "For datasources which support transactions, this creates a transaction." +msgstr "" + +#: of osgeo.ogr.Layer.StartTransaction:3 +msgid "For more details: :cpp:func:`OGR_L_StartTransaction`" +msgstr "" + +#: of osgeo.ogr.Layer.SymDifference:1 +msgid "Symmetrical difference of two layers." +msgstr "" + +#: of osgeo.ogr.Layer.SymDifference:3 +msgid "For more details: :cpp:func:`OGR_L_SymDifference`" +msgstr "" + +#: of osgeo.ogr.Layer.SyncToDisk:3 +msgid "For more details: :cpp:func:`OGR_L_SyncToDisk`" +msgstr "" + +#: of osgeo.ogr.Layer.SyncToDisk:5 +msgid "" +":py:const:`osgeo.ogr.OGRERR_NONE` if no error occurs (even if nothing is " +"done) or an error code." +msgstr "" + +#: of osgeo.ogr.Layer.TestCapability:1 +msgid "Test if this layer supported the named capability." +msgstr "" + +#: of osgeo.ogr.Layer.TestCapability:3 +msgid "For more details: :cpp:func:`OGR_L_TestCapability`" +msgstr "" + +#: of osgeo.ogr.Layer.TestCapability:5 +msgid "" +"The name of the capability to test. These can be found in the `osgeo.ogr`" +" namespace. For example, :py:const:`osgeo.ogr.OLCRandomRead`." +msgstr "" + +#: of osgeo.ogr.Layer.TestCapability:10 +msgid "" +"True if the layer has the requested capability, or False otherwise. Will " +"return False for any unrecognized capabilities." +msgstr "" + +#: of osgeo.ogr.Layer.Union:1 +msgid "Union of two layers." +msgstr "" + +#: of osgeo.ogr.Layer.Union:3 +msgid "For more details: :cpp:func:`OGR_L_Union`" +msgstr "" + +#: of osgeo.ogr.Layer.Union:5 +msgid "The first geometry field is always used." +msgstr "" + +#: of osgeo.ogr.Layer.Update:1 +msgid "Update this layer with features from the update layer." +msgstr "" + +#: of osgeo.ogr.Layer.Update:3 +msgid "For more details: :cpp:func:`OGR_L_Update`" +msgstr "" + +#: of osgeo.ogr.Layer.UpsertFeature:1 +msgid "Rewrite an existing feature or create a new feature within a layer." +msgstr "" + +#: of osgeo.ogr.Layer.UpsertFeature:3 +msgid "For more details: :cpp:func:`OGR_L_UpsertFeature`" +msgstr "" + +#: ../../source/api/python/vector_api.rst:32 +msgid "Feature" +msgstr "" + +#: of osgeo.ogr.Feature:1 +msgid "Proxy of C++ OGRFeatureShadow class." +msgstr "" + +#: of osgeo.ogr.Feature.Clone:1 +msgid "OGRFeatureH OGR_F_Clone(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.Clone:3 +msgid "Duplicate feature." +msgstr "" + +#: of osgeo.ogr.Feature.Clone:5 +msgid "" +"The newly created feature is owned by the caller, and will have its own " +"reference to the OGRFeatureDefn." +msgstr "" + +#: of osgeo.ogr.Feature.Clone:8 +msgid "This function is the same as the C++ method OGRFeature::Clone()." +msgstr "" + +#: of osgeo.ogr.Feature.Clone:10 +msgid "handle to the feature to clone." +msgstr "" + +#: of osgeo.ogr.Feature.Clone:12 +msgid "a handle to the new feature, exactly matching this feature." +msgstr "" + +#: of osgeo.ogr.Feature.DumpReadable:1 +msgid "void OGR_F_DumpReadable(OGRFeatureH hFeat, FILE \\*fpOut)" +msgstr "" + +#: of osgeo.ogr.Feature.DumpReadable:4 +msgid "Dump this feature in a human readable form." +msgstr "" + +#: of osgeo.ogr.Feature.DumpReadable:6 +msgid "" +"This dumps the attributes, and geometry; however, it doesn't definition " +"information (other than field types and names), nor does it report the " +"geometry spatial reference system." +msgstr "" + +#: of osgeo.ogr.Feature.DumpReadable:10 +msgid "This function is the same as the C++ method OGRFeature::DumpReadable()." +msgstr "" + +#: of osgeo.ogr.Feature.DumpReadable:13 +msgid "handle to the feature to dump." +msgstr "" + +#: of osgeo.ogr.Feature.DumpReadable:14 +msgid "the stream to write to, such as strout." +msgstr "" + +#: of osgeo.ogr.Feature.Equal:1 +msgid "int OGR_F_Equal(OGRFeatureH hFeat, OGRFeatureH hOtherFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.Equal:4 +msgid "Test if two features are the same." +msgstr "" + +#: of osgeo.ogr.Feature.Equal:6 +msgid "" +"Two features are considered equal if the share them (handle equality) " +"same OGRFeatureDefn, have the same field values, and the same geometry " +"(as tested by OGR_G_Equal()) as well as the same feature id." +msgstr "" + +#: of osgeo.ogr.Feature.Equal:10 +msgid "This function is the same as the C++ method OGRFeature::Equal()." +msgstr "" + +#: of osgeo.ogr.Feature.Equal:12 +msgid "handle to one of the feature." +msgstr "" + +#: of osgeo.ogr.Feature.Equal:13 +msgid "handle to the other feature to test this one against." +msgstr "" + +#: of osgeo.ogr.Feature.Equal:15 +msgid "TRUE if they are equal, otherwise FALSE." +msgstr "" + +#: of osgeo.ogr.Feature.ExportToJson:1 +msgid "" +"Exports a GeoJSON object which represents the Feature. The as_object " +"parameter determines whether the returned value should be a Python object" +" instead of a string. Defaults to False. The options parameter is passed " +"to Geometry.ExportToJson()" +msgstr "" + +#: of osgeo.ogr.Feature.FillUnsetWithDefault:1 +msgid "" +"void OGR_F_FillUnsetWithDefault(OGRFeatureH hFeat, int bNotNullableOnly, " +"char \\*\\*papszOptions)" +msgstr "" + +#: of osgeo.ogr.Feature.FillUnsetWithDefault:5 +msgid "Fill unset fields with default values that might be defined." +msgstr "" + +#: of osgeo.ogr.Feature.FillUnsetWithDefault:7 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::FillUnsetWithDefault()." +msgstr "" + +#: of osgeo.ogr.Feature.FillUnsetWithDefault:12 +#: osgeo.ogr.Feature.GetNativeData:28 osgeo.ogr.Feature.GetNativeMediaType:18 +#: osgeo.ogr.Feature.SetNativeData:18 osgeo.ogr.Feature.SetNativeMediaType:20 +msgid "handle to the feature." +msgstr "" + +#: of osgeo.ogr.Feature.FillUnsetWithDefault:13 +msgid "if we should fill only unset fields with a not-null constraint." +msgstr "" + +#: of osgeo.ogr.Feature.FillUnsetWithDefault:15 +msgid "unused currently. Must be set to NULL." +msgstr "" + +#: of osgeo.ogr.Feature.GetDefnRef:1 +msgid "OGRFeatureDefnH OGR_F_GetDefnRef(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetDefnRef:3 +msgid "Fetch feature definition." +msgstr "" + +#: of osgeo.ogr.Feature.GetDefnRef:5 +msgid "This function is the same as the C++ method OGRFeature::GetDefnRef()." +msgstr "" + +#: of osgeo.ogr.Feature.GetDefnRef:7 +msgid "handle to the feature to get the feature definition from." +msgstr "" + +#: of osgeo.ogr.Feature.GetDefnRef:9 +msgid "a handle to the feature definition object on which feature depends." +msgstr "" + +#: of osgeo.ogr.Feature.GetFID:1 +msgid "GIntBig OGR_F_GetFID(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFID:4 +msgid "Get feature identifier." +msgstr "" + +#: of osgeo.ogr.Feature.GetFID:6 +msgid "" +"This function is the same as the C++ method OGRFeature::GetFID(). Note: " +"since GDAL 2.0, this method returns a GIntBig (previously a long)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFID:10 +msgid "handle to the feature from which to get the feature" +msgstr "" + +#: of osgeo.ogr.Feature.GetFID:13 +msgid "feature id or OGRNullFID if none has been assigned." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:1 +msgid "" +"GByte\\* OGR_F_GetFieldAsBinary(OGRFeatureH hFeat, int iField, int " +"\\*pnBytes)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:4 +msgid "Fetch field value as binary." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:6 +msgid "This method only works for OFTBinary and OFTString fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:8 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsBinary()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:11 +#: osgeo.ogr.Feature.GetFieldAsDateTime:16 +#: osgeo.ogr.Feature.GetFieldAsDouble:12 +#: osgeo.ogr.Feature.GetFieldAsDoubleList:12 +#: osgeo.ogr.Feature.GetFieldAsInteger:12 +#: osgeo.ogr.Feature.GetFieldAsInteger64:15 +#: osgeo.ogr.Feature.GetFieldAsInteger64List:14 +#: osgeo.ogr.Feature.GetFieldAsIntegerList:11 +#: osgeo.ogr.Feature.GetFieldAsString:12 +#: osgeo.ogr.Feature.GetFieldAsStringList:14 +#: osgeo.ogr.Feature.SetFieldDoubleList:18 +#: osgeo.ogr.Feature.SetFieldInteger64:21 +#: osgeo.ogr.Feature.SetFieldInteger64List:20 +#: osgeo.ogr.Feature.SetFieldIntegerList:18 osgeo.ogr.Feature.SetFieldString:21 +#: osgeo.ogr.Feature.SetFieldStringList:17 +msgid "handle to the feature that owned the field." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:12 +#: osgeo.ogr.Feature.GetFieldAsDateTime:17 +#: osgeo.ogr.Feature.GetFieldAsDouble:13 +#: osgeo.ogr.Feature.GetFieldAsDoubleList:13 +#: osgeo.ogr.Feature.GetFieldAsInteger:13 +#: osgeo.ogr.Feature.GetFieldAsInteger64:16 +#: osgeo.ogr.Feature.GetFieldAsInteger64List:15 +#: osgeo.ogr.Feature.GetFieldAsIntegerList:12 +#: osgeo.ogr.Feature.GetFieldAsString:13 +#: osgeo.ogr.Feature.GetFieldAsStringList:15 +#: osgeo.ogr.Feature.GetFieldDefnRef:9 osgeo.ogr.Feature.SetFieldInteger64:22 +#: osgeo.ogr.Feature.SetFieldString:22 +msgid "the field to fetch, from 0 to GetFieldCount()-1." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:13 +msgid "location to place count of bytes returned." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsBinary:15 +#: osgeo.ogr.Feature.GetFieldAsStringList:17 +msgid "" +"the field value. This list is internal, and should not be modified, or " +"freed. Its lifetime may be very brief." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:1 +msgid "" +"int OGR_F_GetFieldAsDateTime(OGRFeatureH hFeat, int iField, int " +"\\*pnYear, int \\*pnMonth, int \\*pnDay, int \\*pnHour, int \\*pnMinute, " +"int \\*pnSecond, int \\*pnTZFlag)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:6 +msgid "Fetch field value as date and time." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:8 +msgid "" +"Currently this method only works for OFTDate, OFTTime and OFTDateTime " +"fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:11 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsDateTime()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:14 +msgid "Use OGR_F_GetFieldAsDateTimeEx() for second with millisecond accuracy." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:18 +msgid "(including century)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:19 +msgid "(1-12)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:20 +msgid "(1-31)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:21 +msgid "(0-23)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:22 +#: osgeo.ogr.Feature.GetFieldAsDateTime:23 +msgid "(0-59)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:24 +msgid "(0=unknown, 1=localtime, 100=GMT, see data model for" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDateTime:27 +msgid "TRUE on success or FALSE on failure." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDouble:1 +msgid "double OGR_F_GetFieldAsDouble(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDouble:3 +msgid "Fetch field value as a double." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDouble:5 +msgid "" +"OFTString features will be translated using CPLAtof(). OFTInteger fields " +"will be cast to double. Other field types, or errors will result in a " +"return value of zero." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDouble:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsDouble()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDouble:15 +#: osgeo.ogr.Feature.GetFieldAsInteger:15 +#: osgeo.ogr.Feature.GetFieldAsInteger64:18 +msgid "the field value." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDoubleList:1 +msgid "" +"const double\\* OGR_F_GetFieldAsDoubleList(OGRFeatureH hFeat, int iField," +" int \\*pnCount)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDoubleList:5 +msgid "Fetch field value as a list of doubles." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDoubleList:7 +msgid "Currently this function only works for OFTRealList fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDoubleList:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsDoubleList()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDoubleList:14 +msgid "an integer to put the list count (number of doubles) into." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsDoubleList:16 +#: osgeo.ogr.Feature.GetFieldAsInteger64List:18 +#: osgeo.ogr.Feature.GetFieldAsIntegerList:15 +msgid "" +"the field value. This list is internal, and should not be modified, or " +"freed. Its lifetime may be very brief. If \\*pnCount is zero on return " +"the returned pointer may be NULL or non-NULL." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger:1 +msgid "int OGR_F_GetFieldAsInteger(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger:3 +msgid "Fetch field value as integer." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger:5 +msgid "" +"OFTString features will be translated using atoi(). OFTReal fields will " +"be cast to integer. Other field types, or errors will result in a return " +"value of zero." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsInteger()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64:1 +msgid "GIntBig OGR_F_GetFieldAsInteger64(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64:3 +msgid "Fetch field value as integer 64 bit." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64:5 +msgid "" +"OFTInteger are promoted to 64 bit. OFTString features will be translated " +"using CPLAtoGIntBig(). OFTReal fields will be cast to integer. Other " +"field types, or errors will result in a return value of zero." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64:10 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsInteger64()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64List:1 +msgid "" +"const GIntBig\\* OGR_F_GetFieldAsInteger64List(OGRFeatureH hFeat, int " +"iField, int \\*pnCount)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64List:5 +msgid "Fetch field value as a list of 64 bit integers." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64List:7 +msgid "Currently this function only works for OFTInteger64List fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64List:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsInteger64List()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsInteger64List:16 +#: osgeo.ogr.Feature.GetFieldAsIntegerList:13 +msgid "an integer to put the list count (number of integers) into." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsIntegerList:1 +msgid "" +"const int\\* OGR_F_GetFieldAsIntegerList(OGRFeatureH hFeat, int iField, " +"int \\*pnCount)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsIntegerList:4 +msgid "Fetch field value as a list of integers." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsIntegerList:6 +msgid "Currently this function only works for OFTIntegerList fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsIntegerList:8 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsIntegerList()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsString:1 +msgid "const char\\* OGR_F_GetFieldAsString(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsString:3 +msgid "Fetch field value as a string." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsString:5 +msgid "" +"OFTReal and OFTInteger fields will be translated to string using " +"sprintf(), but not necessarily using the established formatting rules. " +"Other field types, or errors will result in a return value of zero." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsString:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsString()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsString:15 +msgid "" +"the field value. This string is internal, and should not be modified, or " +"freed. Its lifetime may be very brief." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsStringList:1 +msgid "char\\*\\* OGR_F_GetFieldAsStringList(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsStringList:4 +msgid "Fetch field value as a list of strings." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsStringList:6 +msgid "Currently this method only works for OFTStringList fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsStringList:8 +msgid "" +"The returned list is terminated by a NULL pointer. The number of elements" +" can also be calculated using CSLCount()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldAsStringList:11 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetFieldAsStringList()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldCount:1 +msgid "int OGR_F_GetFieldCount(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldCount:3 +msgid "" +"Fetch number of fields on this feature This will always be the same as " +"the field count for the OGRFeatureDefn." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldCount:6 +msgid "This function is the same as the C++ method OGRFeature::GetFieldCount()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldCount:9 +msgid "handle to the feature to get the fields count from." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldCount:11 osgeo.ogr.FeatureDefn.GetFieldCount:10 +msgid "count of fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldDefnRef:1 +msgid "OGRFieldDefnH OGR_F_GetFieldDefnRef(OGRFeatureH hFeat, int i)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldDefnRef:3 +msgid "Fetch definition for this field." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldDefnRef:5 +msgid "This function is the same as the C++ method OGRFeature::GetFieldDefnRef()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldDefnRef:8 osgeo.ogr.Feature.GetFieldIndex:10 +#: osgeo.ogr.Feature.GetGeomFieldDefnRef:10 +msgid "handle to the feature on which the field is found." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldDefnRef:11 +#: osgeo.ogr.Feature.GetGeomFieldDefnRef:13 +msgid "" +"a handle to the field definition (from the OGRFeatureDefn). This is an " +"internal reference, and should not be deleted or modified." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldIndex:1 +msgid "int OGR_F_GetFieldIndex(OGRFeatureH hFeat, const char \\*pszName)" +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldIndex:3 +msgid "Fetch the field index given field name." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldIndex:5 +msgid "This is a cover for the OGRFeatureDefn::GetFieldIndex() method." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldIndex:7 +msgid "This function is the same as the C++ method OGRFeature::GetFieldIndex()." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldIndex:11 +msgid "the name of the field to search for." +msgstr "" + +#: of osgeo.ogr.Feature.GetFieldIndex:13 +msgid "the field index, or -1 if no matching field is found." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldCount:1 +msgid "int OGR_F_GetGeomFieldCount(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldCount:3 +msgid "" +"Fetch number of geometry fields on this feature This will always be the " +"same as the geometry field count for the OGRFeatureDefn." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldCount:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetGeomFieldCount()." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldCount:11 +msgid "handle to the feature to get the geometry fields count from." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldCount:13 +#: osgeo.ogr.FeatureDefn.GetGeomFieldCount:13 +msgid "count of geometry fields." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldDefnRef:1 +msgid "OGRGeomFieldDefnH OGR_F_GetGeomFieldDefnRef(OGRFeatureH hFeat, int i)" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldDefnRef:3 +msgid "Fetch definition for this geometry field." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldDefnRef:5 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetGeomFieldDefnRef()." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldDefnRef:11 +msgid "the field to fetch, from 0 to GetGeomFieldCount()-1." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:1 +msgid "int OGR_F_GetGeomFieldIndex(OGRFeatureH hFeat, const char \\*pszName)" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:3 +msgid "Fetch the geometry field index given geometry field name." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:5 +msgid "This is a cover for the OGRFeatureDefn::GetGeomFieldIndex() method." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:7 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::GetGeomFieldIndex()." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:12 +msgid "handle to the feature on which the geometry field is found." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:13 +msgid "the name of the geometry field to search for." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldIndex:15 +msgid "the geometry field index, or -1 if no matching geometry field is found." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldRef:1 +msgid "OGRGeometryH OGR_F_GetGeomFieldRef(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldRef:4 +msgid "Fetch a handle to feature geometry." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldRef:6 +msgid "This function is the same as the C++ method OGRFeature::GetGeomFieldRef()." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldRef:9 +msgid "handle to the feature to get geometry from." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeomFieldRef:10 +msgid "geometry field to get." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeometryRef:1 osgeo.ogr.Feature.geometry:1 +msgid "Return the feature geometry" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeometryRef:3 osgeo.ogr.Feature.geometry:3 +msgid "" +"The lifetime of the returned geometry is bound to the one of its " +"belonging feature." +msgstr "" + +#: of osgeo.ogr.Feature.GetGeometryRef:6 osgeo.ogr.Feature.geometry:6 +msgid "For more details: :cpp:func:`OGR_F_GetGeometryRef`" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeometryRef:8 +msgid "The geometry() method is also available as an alias of GetGeometryRef()" +msgstr "" + +#: of osgeo.ogr.Feature.GetGeometryRef:10 osgeo.ogr.Feature.geometry:10 +msgid "the geometry, or None." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:1 +msgid "const char\\* OGR_F_GetNativeData(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:4 +msgid "Returns the native data for the feature." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:6 osgeo.ogr.Feature.SetNativeData:6 +msgid "" +"The native data is the representation in a \"natural\" form that comes " +"from the driver that created this feature, or that is aimed at an output " +"driver. The native data may be in different format, which is indicated by" +" OGR_F_GetNativeMediaType()." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:11 +msgid "" +"Note that most drivers do not support storing the native data in the " +"feature object, and if they do, generally the NATIVE_DATA open option " +"must be passed at dataset opening." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:15 +msgid "" +"The \"native data\" does not imply it is something more performant or " +"powerful than what can be obtained with the rest of the API, but it may " +"be useful in round-tripping scenarios where some characteristics of the " +"underlying format are not captured otherwise by the OGR abstraction." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:21 +msgid "This function is the same as the C++ method OGRFeature::GetNativeData()." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:24 +#: osgeo.ogr.Feature.GetNativeMediaType:14 osgeo.ogr.Feature.SetNativeData:14 +#: osgeo.ogr.Feature.SetNativeMediaType:15 +msgid "See https://trac.osgeo.org/gdal/wiki/rfc60_improved_roundtripping_in_ogr" +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeData:30 osgeo.ogr.Feature.SetNativeData:19 +msgid "a string with the native data, or NULL if there is none." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeMediaType:1 +msgid "const char\\* OGR_F_GetNativeMediaType(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeMediaType:4 +msgid "Returns the native media type for the feature." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeMediaType:6 +#: osgeo.ogr.Feature.SetNativeMediaType:7 +msgid "" +"The native media type is the identifier for the format of the native " +"data. It follows the IANA RFC 2045 " +"(seehttps://en.wikipedia.org/wiki/Media_type), e.g. " +"\"application/vnd.geo+json\" for JSon." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeMediaType:11 +msgid "This function is the same as the C function OGR_F_GetNativeMediaType()." +msgstr "" + +#: of osgeo.ogr.Feature.GetNativeMediaType:20 +#: osgeo.ogr.Feature.SetNativeMediaType:21 +msgid "a string with the native media type, or NULL if there is none." +msgstr "" + +#: of osgeo.ogr.Feature.GetStyleString:1 +msgid "const char\\* OGR_F_GetStyleString(OGRFeatureH hFeat)" +msgstr "" + +#: of osgeo.ogr.Feature.GetStyleString:4 +msgid "Fetch style string for this feature." +msgstr "" + +#: of osgeo.ogr.Feature.GetStyleString:6 +msgid "" +"Set the OGR Feature Style Specification for details on the format of this" +" string, and ogr_featurestyle.h for services available to parse it." +msgstr "" + +#: of osgeo.ogr.Feature.GetStyleString:10 +msgid "This function is the same as the C++ method OGRFeature::GetStyleString()." +msgstr "" + +#: of osgeo.ogr.Feature.GetStyleString:13 +msgid "handle to the feature to get the style from." +msgstr "" + +#: of osgeo.ogr.Feature.GetStyleString:15 +msgid "" +"a reference to a representation in string format, or NULL if there isn't " +"one." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldNull:1 +msgid "int OGR_F_IsFieldNull(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldNull:3 +msgid "Test if a field is null." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldNull:5 +msgid "This function is the same as the C++ method OGRFeature::IsFieldNull()." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldNull:9 osgeo.ogr.Feature.IsFieldSet:7 +#: osgeo.ogr.Feature.IsFieldSetAndNotNull:10 osgeo.ogr.Feature.SetFieldNull:10 +#: osgeo.ogr.Feature.UnsetField:7 +msgid "handle to the feature on which the field is." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldNull:10 osgeo.ogr.Feature.IsFieldSet:8 +#: osgeo.ogr.Feature.IsFieldSetAndNotNull:11 +msgid "the field to test." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldNull:12 +msgid "TRUE if the field is null, otherwise false." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSet:1 +msgid "int OGR_F_IsFieldSet(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSet:3 +msgid "Test if a field has ever been assigned a value or not." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSet:5 +msgid "This function is the same as the C++ method OGRFeature::IsFieldSet()." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSet:10 +msgid "TRUE if the field has been set, otherwise false." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSetAndNotNull:1 +msgid "int OGR_F_IsFieldSetAndNotNull(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSetAndNotNull:3 +msgid "Test if a field is set and not null." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSetAndNotNull:5 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::IsFieldSetAndNotNull()." +msgstr "" + +#: of osgeo.ogr.Feature.IsFieldSetAndNotNull:13 +msgid "TRUE if the field is set and not null, otherwise false." +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:1 +msgid "OGRErr OGR_F_SetFID(OGRFeatureH hFeat, GIntBig nFID)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:4 +msgid "Set the feature identifier." +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:6 +msgid "" +"For specific types of features this operation may fail on illegal " +"features ids. Generally it always succeeds. Feature ids should be greater" +" than or equal to zero, with the exception of OGRNullFID (-1) indicating " +"that the feature id is unknown." +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:11 +msgid "This function is the same as the C++ method OGRFeature::SetFID()." +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:13 +msgid "handle to the feature to set the feature id to." +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:14 +msgid "the new feature identifier value to assign." +msgstr "" + +#: of osgeo.ogr.Feature.SetFID:16 +msgid "On success OGRERR_NONE, or on failure some other value." +msgstr "" + +#: of osgeo.ogr.Feature.SetField:1 +msgid "SetField(self, int id, int year, int month, int day, int hour, int minute," +msgstr "" + +#: of osgeo.ogr.Feature.SetField:2 +msgid "int second, int tzflag)" +msgstr "" + +#: of osgeo.ogr.Feature.SetField:3 +msgid "SetField(self, char name, int year, int month, int day, int hour," +msgstr "" + +#: of osgeo.ogr.Feature.SetField:4 +msgid "int minute, int second, int tzflag)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:1 +msgid "" +"void OGR_F_SetFieldDoubleList(OGRFeatureH hFeat, int iField, int nCount, " +"const double \\*padfValues)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:5 +msgid "Set field to list of doubles value." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:7 +msgid "" +"This function currently on has an effect of OFTIntegerList, " +"OFTInteger64List, OFTRealList fields." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:10 +#: osgeo.ogr.Feature.SetFieldInteger64:11 +#: osgeo.ogr.Feature.SetFieldInteger64List:10 +#: osgeo.ogr.Feature.SetFieldIntegerList:10 osgeo.ogr.Feature.SetFieldString:13 +#: osgeo.ogr.Feature.SetFieldStringList:9 +msgid "This function is the same as the C++ method OGRFeature::SetField()." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:12 +#: osgeo.ogr.Feature.SetFieldInteger64:13 +#: osgeo.ogr.Feature.SetFieldInteger64List:12 +#: osgeo.ogr.Feature.SetFieldIntegerList:12 osgeo.ogr.Feature.SetFieldString:15 +#: osgeo.ogr.Feature.SetFieldStringList:11 osgeo.ogr.Feature.SetGeometry:11 +#: osgeo.ogr.Feature.SetGeometryDirectly:12 +msgid "" +"This method has only an effect on the in-memory feature object. If this " +"object comes from a layer and the modifications must be serialized back " +"to the datasource, OGR_L_SetFeature() must be used afterwards. Or if this" +" is a new feature, OGR_L_CreateFeature() must be used afterwards." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:19 +#: osgeo.ogr.Feature.SetFieldInteger64List:21 +#: osgeo.ogr.Feature.SetFieldIntegerList:19 +#: osgeo.ogr.Feature.SetFieldStringList:18 +msgid "the field to set, from 0 to GetFieldCount()-1." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:20 +#: osgeo.ogr.Feature.SetFieldInteger64List:22 +#: osgeo.ogr.Feature.SetFieldIntegerList:20 +msgid "the number of values in the list being assigned." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldDoubleList:21 +#: osgeo.ogr.Feature.SetFieldInteger64List:23 +#: osgeo.ogr.Feature.SetFieldIntegerList:21 +msgid "the values to assign." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64:1 +msgid "" +"void OGR_F_SetFieldInteger64(OGRFeatureH hFeat, int iField, GIntBig " +"nValue)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64:4 +msgid "Set field to 64 bit integer value." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64:6 +msgid "" +"OFTInteger, OFTInteger64 and OFTReal fields will be set directly. " +"OFTString fields will be assigned a string representation of the value, " +"but not necessarily taking into account formatting constraints on this " +"field. Other field types may be unaffected." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64:23 +#: osgeo.ogr.Feature.SetFieldString:23 +msgid "the value to assign." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64List:1 +msgid "" +"void OGR_F_SetFieldInteger64List(OGRFeatureH hFeat, int iField, int " +"nCount, const GIntBig \\*panValues)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64List:5 +msgid "Set field to list of 64 bit integers value." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldInteger64List:7 +#: osgeo.ogr.Feature.SetFieldIntegerList:7 +msgid "" +"This function currently on has an effect of OFTIntegerList, " +"OFTInteger64List and OFTRealList fields." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldIntegerList:1 +msgid "" +"void OGR_F_SetFieldIntegerList(OGRFeatureH hFeat, int iField, int nCount," +" const int \\*panValues)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldIntegerList:5 +msgid "Set field to list of integers value." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldNull:1 +msgid "void OGR_F_SetFieldNull(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldNull:3 +msgid "Clear a field, marking it as null." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldNull:5 +msgid "This function is the same as the C++ method OGRFeature::SetFieldNull()." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldNull:11 +msgid "the field to set to null." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldString:1 +msgid "" +"void OGR_F_SetFieldString(OGRFeatureH hFeat, int iField, const char " +"\\*pszValue)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldString:5 +msgid "Set field to string value." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldString:7 +msgid "" +"OFTInteger fields will be set based on an atoi() conversion of the " +"string. OFTInteger64 fields will be set based on an CPLAtoGIntBig() " +"conversion of the string. OFTReal fields will be set based on an " +"CPLAtof() conversion of the string. Other field types may be unaffected." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldStringList:1 +msgid "" +"void OGR_F_SetFieldStringList(OGRFeatureH hFeat, int iField, CSLConstList" +" papszValues)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldStringList:5 +msgid "Set field to list of strings value." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldStringList:7 +msgid "This function currently on has an effect of OFTStringList fields." +msgstr "" + +#: of osgeo.ogr.Feature.SetFieldStringList:19 +msgid "the values to assign. List of NUL-terminated string," +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:1 +msgid "" +"OGRErr OGR_F_SetFrom(OGRFeatureH hFeat, OGRFeatureH hOtherFeat, int " +"bForgiving)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:4 osgeo.ogr.Feature.SetFromWithMap:5 +msgid "Set one feature from another." +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:6 +msgid "" +"Overwrite the contents of this feature from the geometry and attributes " +"of another. The hOtherFeature does not need to have the same " +"OGRFeatureDefn. Field values are copied by corresponding field names. " +"Field types do not have to exactly match. OGR_F_SetField\\*() function " +"conversion rules will be applied as needed." +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:12 osgeo.ogr.Feature.SetFromWithMap:16 +msgid "This function is the same as the C++ method OGRFeature::SetFrom()." +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:14 osgeo.ogr.Feature.SetFromWithMap:18 +msgid "handle to the feature to set to." +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:15 osgeo.ogr.Feature.SetFromWithMap:19 +msgid "" +"handle to the feature from which geometry, and field values will be " +"copied." +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:17 osgeo.ogr.Feature.SetFromWithMap:26 +msgid "" +"TRUE if the operation should continue despite lacking output fields " +"matching some of the source fields." +msgstr "" + +#: of osgeo.ogr.Feature.SetFrom:20 osgeo.ogr.Feature.SetFromWithMap:29 +msgid "" +"OGRERR_NONE if the operation succeeds, even if some values are not " +"transferred, otherwise an error code." +msgstr "" + +#: of osgeo.ogr.Feature.SetFromWithMap:1 +msgid "" +"OGRErr OGR_F_SetFromWithMap(OGRFeatureH hFeat, OGRFeatureH hOtherFeat, " +"int bForgiving, const int \\*panMap)" +msgstr "" + +#: of osgeo.ogr.Feature.SetFromWithMap:7 +msgid "" +"Overwrite the contents of this feature from the geometry and attributes " +"of another. The hOtherFeature does not need to have the same " +"OGRFeatureDefn. Field values are copied according to the provided indices" +" map. Field types do not have to exactly match. OGR_F_SetField\\*() " +"function conversion rules will be applied as needed. This is more " +"efficient than OGR_F_SetFrom() in that this doesn't lookup the fields by " +"their names. Particularly useful when the field names don't match." +msgstr "" + +#: of osgeo.ogr.Feature.SetFromWithMap:21 +msgid "" +"Array of the indices of the destination feature's fields stored at the " +"corresponding index of the source feature's fields. A value of -1 should " +"be used to ignore the source's field. The array should not be NULL and be" +" as long as the number of fields in the source feature." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:1 +msgid "" +"OGRErr OGR_F_SetGeomField(OGRFeatureH hFeat, int iField, OGRGeometryH " +"hGeom)" +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:4 osgeo.ogr.Feature.SetGeomFieldDirectly:3 +msgid "Set feature geometry of a specified geometry field." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:6 osgeo.ogr.Feature.SetGeometry:5 +msgid "" +"This function updates the features geometry, and operate exactly as " +"SetGeometryDirectly(), except that this function does not assume " +"ownership of the passed geometry, but instead makes a copy of it." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:10 +msgid "This function is the same as the C++ OGRFeature::SetGeomField()." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:12 osgeo.ogr.Feature.SetGeometry:17 +msgid "handle to the feature on which new geometry is applied to." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:13 +#: osgeo.ogr.Feature.SetGeomFieldDirectly:15 +msgid "geometry field to set." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:14 +#: osgeo.ogr.Feature.SetGeomFieldDirectly:16 osgeo.ogr.Feature.SetGeometry:18 +#: osgeo.ogr.Feature.SetGeometryDirectly:19 +msgid "handle to the new geometry to apply to feature." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomField:16 osgeo.ogr.Feature.SetGeometry:20 +#: osgeo.ogr.Feature.SetGeometryDirectly:21 +msgid "" +"OGRERR_NONE if successful, or OGR_UNSUPPORTED_GEOMETRY_TYPE if the " +"geometry type is illegal for the OGRFeatureDefn (checking not yet " +"implemented)." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomFieldDirectly:1 +msgid "" +"OGRErr OGR_F_SetGeomFieldDirectly(OGRFeatureH hFeat, int iField, " +"OGRGeometryH hGeom)" +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomFieldDirectly:5 +msgid "" +"This function updates the features geometry, and operate exactly as " +"SetGeomField(), except that this function assumes ownership of the passed" +" geometry (even in case of failure of that function)." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomFieldDirectly:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::SetGeomFieldDirectly." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomFieldDirectly:14 +#: osgeo.ogr.Feature.SetGeometryDirectly:18 +msgid "handle to the feature on which to apply the geometry." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeomFieldDirectly:18 +msgid "" +"OGRERR_NONE if successful, or OGRERR_FAILURE if the index is invalid, or " +"OGR_UNSUPPORTED_GEOMETRY_TYPE if the geometry type is illegal for the " +"OGRFeatureDefn (checking not yet implemented)." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeometry:1 +msgid "OGRErr OGR_F_SetGeometry(OGRFeatureH hFeat, OGRGeometryH hGeom)" +msgstr "" + +#: of osgeo.ogr.Feature.SetGeometry:3 osgeo.ogr.Feature.SetGeometryDirectly:3 +msgid "Set feature geometry." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeometry:9 +msgid "This function is the same as the C++ OGRFeature::SetGeometry()." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeometryDirectly:1 +msgid "OGRErr OGR_F_SetGeometryDirectly(OGRFeatureH hFeat, OGRGeometryH hGeom)" +msgstr "" + +#: of osgeo.ogr.Feature.SetGeometryDirectly:5 +msgid "" +"This function updates the features geometry, and operate exactly as " +"SetGeometry(), except that this function assumes ownership of the passed " +"geometry (even in case of failure of that function)." +msgstr "" + +#: of osgeo.ogr.Feature.SetGeometryDirectly:9 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::SetGeometryDirectly." +msgstr "" + +#: of osgeo.ogr.Feature.SetNativeData:1 +msgid "void OGR_F_SetNativeData(OGRFeatureH hFeat, const char \\*pszNativeData)" +msgstr "" + +#: of osgeo.ogr.Feature.SetNativeData:4 +msgid "Sets the native data for the feature." +msgstr "" + +#: of osgeo.ogr.Feature.SetNativeData:11 +msgid "This function is the same as the C++ method OGRFeature::SetNativeData()." +msgstr "" + +#: of osgeo.ogr.Feature.SetNativeMediaType:1 +msgid "" +"void OGR_F_SetNativeMediaType(OGRFeatureH hFeat, const char " +"\\*pszNativeMediaType)" +msgstr "" + +#: of osgeo.ogr.Feature.SetNativeMediaType:5 +msgid "Sets the native media type for the feature." +msgstr "" + +#: of osgeo.ogr.Feature.SetNativeMediaType:12 +msgid "" +"This function is the same as the C++ method " +"OGRFeature::SetNativeMediaType()." +msgstr "" + +#: of osgeo.ogr.Feature.SetStyleString:1 +msgid "void OGR_F_SetStyleString(OGRFeatureH hFeat, const char \\*pszStyle)" +msgstr "" + +#: of osgeo.ogr.Feature.SetStyleString:4 +msgid "Set feature style string." +msgstr "" + +#: of osgeo.ogr.Feature.SetStyleString:6 +msgid "" +"This method operate exactly as OGR_F_SetStyleStringDirectly() except that" +" it does not assume ownership of the passed string, but instead makes a " +"copy of it." +msgstr "" + +#: of osgeo.ogr.Feature.SetStyleString:10 +msgid "This function is the same as the C++ method OGRFeature::SetStyleString()." +msgstr "" + +#: of osgeo.ogr.Feature.SetStyleString:13 +msgid "handle to the feature to set style to." +msgstr "" + +#: of osgeo.ogr.Feature.SetStyleString:14 +msgid "the style string to apply to this feature, cannot be NULL." +msgstr "" + +#: of osgeo.ogr.Feature.UnsetField:1 +msgid "void OGR_F_UnsetField(OGRFeatureH hFeat, int iField)" +msgstr "" + +#: of osgeo.ogr.Feature.UnsetField:3 +msgid "Clear a field, marking it as unset." +msgstr "" + +#: of osgeo.ogr.Feature.UnsetField:5 +msgid "This function is the same as the C++ method OGRFeature::UnsetField()." +msgstr "" + +#: of osgeo.ogr.Feature.UnsetField:8 +msgid "the field to unset." +msgstr "" + +#: of osgeo.ogr.Feature.Validate:1 +msgid "int OGR_F_Validate(OGRFeatureH hFeat, int nValidateFlags, int bEmitError)" +msgstr "" + +#: of osgeo.ogr.Feature.Validate:4 +msgid "Validate that a feature meets constraints of its schema." +msgstr "" + +#: of osgeo.ogr.Feature.Validate:6 +msgid "The scope of test is specified with the nValidateFlags parameter." +msgstr "" + +#: of osgeo.ogr.Feature.Validate:8 +msgid "" +"Regarding OGR_F_VAL_WIDTH, the test is done assuming the string width " +"must be interpreted as the number of UTF-8 characters. Some drivers might" +" interpret the width as the number of bytes instead. So this test is " +"rather conservative (if it fails, then it will fail for all " +"interpretations)." +msgstr "" + +#: of osgeo.ogr.Feature.Validate:14 +msgid "This function is the same as the C++ method OGRFeature::Validate()." +msgstr "" + +#: of osgeo.ogr.Feature.Validate:18 +msgid "handle to the feature to validate." +msgstr "" + +#: of osgeo.ogr.Feature.Validate:19 +msgid "" +"OGR_F_VAL_ALL or combination of OGR_F_VAL_NULL, OGR_F_VAL_GEOM_TYPE, " +"OGR_F_VAL_WIDTH and OGR_F_VAL_ALLOW_NULL_WHEN_DEFAULT with '|' operator" +msgstr "" + +#: of osgeo.ogr.Feature.Validate:22 +msgid "TRUE if a CPLError() must be emitted when a check fails" +msgstr "" + +#: of osgeo.ogr.Feature.Validate:24 +msgid "TRUE if all enabled validation tests pass." +msgstr "" + +#: of osgeo.ogr.Feature.geometry:8 +msgid "The GetGeometryRef() method is also available as an alias of geometry()" +msgstr "" + +#: of osgeo.ogr.Feature.items:1 +msgid "" +"Return a dictionary with the field names as key, and their value in the " +"feature" +msgstr "" + +#: of osgeo.ogr.Feature.keys:1 +msgid "Return the list of field names (of the layer definition)" +msgstr "" + +#: ../../source/api/python/vector_api.rst:40 +msgid "Geometry" +msgstr "" + +#: of osgeo.ogr.Geometry:1 +msgid "Proxy of C++ OGRGeometryShadow class." +msgstr "" + +#: of osgeo.ogr.Geometry.AssignSpatialReference:1 +msgid "Assign spatial reference to this object." +msgstr "" + +#: of osgeo.ogr.Geometry.AssignSpatialReference:3 +msgid "For more details: :cpp:func:`OGR_G_AssignSpatialReference`" +msgstr "" + +#: of osgeo.ogr.Geometry.AssignSpatialReference:5 +msgid "The new spatial reference system to apply." +msgstr "" + +#: of osgeo.ogr.Geometry.Boundary:1 +msgid "Compute boundary." +msgstr "" + +#: of osgeo.ogr.Geometry.Boundary:3 +msgid "For more details: :cpp:func:`OGR_G_Boundary`" +msgstr "" + +#: of osgeo.ogr.Geometry.Boundary:5 osgeo.ogr.Geometry.Polygonize:5 +msgid "A new geometry or None on failure." +msgstr "" + +#: of osgeo.ogr.Geometry.Buffer:1 +msgid "Compute buffer of geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.Buffer:3 +msgid "For more details: :cpp:func:`OGR_G_Buffer`" +msgstr "" + +#: of osgeo.ogr.Geometry.Buffer:5 +msgid "" +"The buffer distance to be applied. Should be expressed into the same unit" +" as the coordinates of the geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.Buffer:8 +msgid "" +"The number of segments used to approximate a 90 degree (quadrant) of " +"curvature." +msgstr "" + +#: of osgeo.ogr.Geometry.Buffer:12 +msgid "The newly created geometry or None if an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.Centroid:1 +msgid "Compute the geometry centroid." +msgstr "" + +#: of osgeo.ogr.Geometry.Centroid:3 +msgid "For more details: :cpp:func:`OGR_G_Centroid`" +msgstr "" + +#: of osgeo.ogr.Geometry.Clone:1 +msgid "Make a copy of this object." +msgstr "" + +#: of osgeo.ogr.Geometry.Clone:3 +msgid "For more details: :cpp:func:`OGR_G_Clone`" +msgstr "" + +#: of osgeo.ogr.Geometry.Clone:5 +msgid "" +"The copy of the geometry with the same spatial reference system as the " +"original." +msgstr "" + +#: of osgeo.ogr.Geometry.CloseRings:1 +msgid "Force rings to be closed." +msgstr "" + +#: of osgeo.ogr.Geometry.CloseRings:3 +msgid "For more details: :cpp:func:`OGR_G_CloseRings`" +msgstr "" + +#: of osgeo.ogr.Geometry.Contains:1 osgeo.ogr.Geometry.Within:1 +msgid "Test for containment." +msgstr "" + +#: of osgeo.ogr.Geometry.Contains:3 +msgid "For more details: :cpp:func:`OGR_G_Contains`" +msgstr "" + +#: of osgeo.ogr.Geometry.Contains:5 osgeo.ogr.Geometry.Crosses:5 +#: osgeo.ogr.Geometry.Overlaps:5 osgeo.ogr.Geometry.Touches:5 +#: osgeo.ogr.Geometry.Within:5 +msgid "the other geometry to compare." +msgstr "" + +#: of osgeo.ogr.Geometry.Contains:8 +msgid "True if this contains the other geometry, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.ConvexHull:1 +msgid "Compute convex hull." +msgstr "" + +#: of osgeo.ogr.Geometry.ConvexHull:3 +msgid "For more details: :cpp:func:`OGR_G_ConvexHull`" +msgstr "" + +#: of osgeo.ogr.Geometry.ConvexHull:5 +msgid "" +"a handle to A newly allocated geometry now owned by the caller, or None " +"on failure." +msgstr "" + +#: of osgeo.ogr.Geometry.CoordinateDimension:1 +#: osgeo.ogr.Geometry.GetCoordinateDimension:1 +msgid "Get the dimension of the coordinates in this geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.CoordinateDimension:3 +msgid "For more details: :cpp:func:`OGR_G_CoordinateDimension`" +msgstr "" + +#: of osgeo.ogr.Geometry.CoordinateDimension:7 +msgid "This will return 2 for XY, 3 for XYZ and XYM, and 4 for XYZM data." +msgstr "" + +#: of osgeo.ogr.Geometry.Crosses:1 +msgid "Test for crossing." +msgstr "" + +#: of osgeo.ogr.Geometry.Crosses:3 +msgid "For more details: :cpp:func:`OGR_G_Crosses`" +msgstr "" + +#: of osgeo.ogr.Geometry.Crosses:8 +msgid "True if they are crossing, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.DelaunayTriangulation:1 +msgid "Return a Delaunay triangulation of the vertices of the geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.DelaunayTriangulation:3 +msgid "For more details: :cpp:func:`OGR_G_DelaunayTriangulation`" +msgstr "" + +#: of osgeo.ogr.Geometry.DelaunayTriangulation:7 +msgid "optional snapping tolerance to use for improved robustness" +msgstr "" + +#: of osgeo.ogr.Geometry.DelaunayTriangulation:9 +msgid "" +"If True, will return a MULTILINESTRING, otherwise it will return a " +"GEOMETRYCOLLECTION containing triangular POLYGONs." +msgstr "" + +#: of osgeo.ogr.Geometry.DelaunayTriangulation:13 +msgid "" +"The geometry resulting from the Delaunay triangulation or None if an " +"error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.Difference:1 +msgid "Compute difference." +msgstr "" + +#: of osgeo.ogr.Geometry.Difference:3 +msgid "For more details: :cpp:func:`OGR_G_Difference`" +msgstr "" + +#: of osgeo.ogr.Geometry.Difference:5 osgeo.ogr.Geometry.Intersection:5 +#: osgeo.ogr.Geometry.Union:5 +msgid "The other geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.Difference:8 +msgid "" +"A new geometry representing the difference or None if the difference is " +"empty or an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.Disjoint:1 +msgid "Test for disjointness." +msgstr "" + +#: of osgeo.ogr.Geometry.Disjoint:3 +msgid "For more details: :cpp:func:`OGR_G_Disjoint`" +msgstr "" + +#: of osgeo.ogr.Geometry.Disjoint:5 +msgid "The other geometry to compare." +msgstr "" + +#: of osgeo.ogr.Geometry.Disjoint:8 +msgid "True if they are disjoint, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.Distance:1 +msgid "Compute distance between two geometries." +msgstr "" + +#: of osgeo.ogr.Geometry.Distance:3 +msgid "For more details: :cpp:func:`OGR_G_Distance`" +msgstr "" + +#: of osgeo.ogr.Geometry.Distance:5 osgeo.ogr.Geometry.Distance3D:7 +msgid "The other geometry to compare against." +msgstr "" + +#: of osgeo.ogr.Geometry.Distance:8 osgeo.ogr.Geometry.Distance3D:10 +msgid "The distance between the geometries or -1 if an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.Distance3D:1 +msgid "Returns the 3D distance between two geometries." +msgstr "" + +#: of osgeo.ogr.Geometry.Distance3D:3 +msgid "For more details: :cpp:func:`OGR_G_Distance3D`" +msgstr "" + +#: of osgeo.ogr.Geometry.Empty:1 +msgid "Clear geometry information." +msgstr "" + +#: of osgeo.ogr.Geometry.Empty:3 +msgid "For more details: :cpp:func:`OGR_G_Empty`" +msgstr "" + +#: of osgeo.ogr.Geometry.Equals:1 +msgid "Returns True if two geometries are equivalent." +msgstr "" + +#: of osgeo.ogr.Geometry.Equals:3 +msgid "For more details: :cpp:func:`OGR_G_Equals`" +msgstr "" + +#: of osgeo.ogr.Geometry.Equals:5 osgeo.ogr.Geometry.Intersects:5 +msgid "The other geometry to test against." +msgstr "" + +#: of osgeo.ogr.Geometry.Equals:8 +msgid "True if equivalent or False otherwise." +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToIsoWkb:1 +msgid "" +"Convert a geometry into SFSQL 1.2 / ISO SQL/MM Part 3 well known binary " +"format." +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToIsoWkb:4 +msgid "For more details: :cpp:func:`OGR_G_ExportToIsoWkb`" +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToIsoWkb:8 osgeo.ogr.Geometry.ExportToWkb:5 +msgid "One of wkbXDR or wkbNDR indicating MSB or LSB byte order respectively." +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToIsoWkt:1 +msgid "" +"Convert a geometry into SFSQL 1.2 / ISO SQL/MM Part 3 well known text " +"format." +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToIsoWkt:4 +msgid "For more details: :cpp:func:`OGR_G_ExportToIsoWkt`" +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToWkb:1 +msgid "Convert a geometry well known binary format." +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToWkb:3 +msgid "For more details: :cpp:func:`OGR_G_ExportToWkb`" +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToWkt:1 +msgid "Convert a geometry into well known text format." +msgstr "" + +#: of osgeo.ogr.Geometry.ExportToWkt:3 +msgid "For more details: :cpp:func:`OGR_G_ExportToWkt`" +msgstr "" + +#: of osgeo.ogr.Geometry.FlattenTo2D:1 +msgid "Convert geometry to strictly 2D." +msgstr "" + +#: of osgeo.ogr.Geometry.FlattenTo2D:3 +msgid "For more details: :cpp:func:`OGR_G_FlattenTo2D`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetBoundary:1 +msgid "Compute boundary (deprecated)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetBoundary:3 +msgid "For more details: :cpp:func:`OGR_G_GetBoundary`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetBoundary:5 +msgid "..warning:: Deprecated" +msgstr "" + +#: of osgeo.ogr.Geometry.GetBoundary:7 +msgid "See: :cpp:func:`OGR_G_Boundary`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetCoordinateDimension:3 +msgid "For more details: :cpp:func:`OGR_G_GetCoordinateDimension`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetCoordinateDimension:5 +msgid "" +"Deprecated. Use :py:func:`CoordinateDimension`, :py:func:`Is3D`, or " +":py:func:`IsMeasured`." +msgstr "" + +#: of osgeo.ogr.Geometry.GetCoordinateDimension:8 +msgid "This will return 2 or 3." +msgstr "" + +#: of osgeo.ogr.Geometry.GetDimension:1 +msgid "Get the dimension of this geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.GetDimension:3 +msgid "For more details: :cpp:func:`OGR_G_GetDimension`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetDimension:5 +msgid "0 for points, 1 for lines, and 2 for surfaces." +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:1 +msgid "" +"Computes and returns the bounding envelope for this geometry in the " +"passed psEnvelope structure." +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope:4 +msgid "For more details: :cpp:func:`OGR_G_GetEnvelope`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope3D:1 +msgid "" +"Computes and returns the bounding envelope (3D) for this geometry in the " +"passed psEnvelope structure." +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope3D:4 +msgid "For more details: :cpp:func:`OGR_G_GetEnvelope3D`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope3D:8 +msgid "" +"* **minx** (*float*) * **maxx** (*float*) * **miny** (*float*) * **maxy**" +" (*float*) * **minz** (*float*) * **maxz** (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope3D:12 +msgid "**minz** (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetEnvelope3D:13 +msgid "**maxz** (*float*)" +msgstr "" + +#: of osgeo.ogr.Geometry.GetGeometryName:1 +msgid "Fetch WKT name for geometry type." +msgstr "" + +#: of osgeo.ogr.Geometry.GetGeometryName:3 +msgid "For more details: :cpp:func:`OGR_G_GetGeometryName`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetGeometryName:5 +msgid "geometry to get name from." +msgstr "" + +#: of osgeo.ogr.Geometry.GetGeometryType:1 +msgid "Fetch geometry type." +msgstr "" + +#: of osgeo.ogr.Geometry.GetGeometryType:3 +msgid "For more details: :cpp:func:`OGR_G_GetGeometryType`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetSpatialReference:1 +msgid "For more details: :cpp:func:`OGR_G_GetSpatialReference`" +msgstr "" + +#: of osgeo.ogr.Geometry.GetSpatialReference:3 +msgid "Returns spatial reference system for geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.Intersection:1 +msgid "Compute intersection." +msgstr "" + +#: of osgeo.ogr.Geometry.Intersection:3 +msgid "For more details: :cpp:func:`OGR_G_Intersection`" +msgstr "" + +#: of osgeo.ogr.Geometry.Intersection:8 +msgid "" +"A new geometry representing the intersection or None if there is no " +"intersection or an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.Intersects:1 +msgid "Determines whether two geometries intersect." +msgstr "" + +#: of osgeo.ogr.Geometry.Intersects:3 +msgid "For more details: :cpp:func:`OGR_G_Intersects`" +msgstr "" + +#: of osgeo.ogr.Geometry.Intersects:8 +msgid "True if the geometries intersect, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.Is3D:1 +msgid "See whether this geometry has Z coordinates." +msgstr "" + +#: of osgeo.ogr.Geometry.Is3D:3 +msgid "For more details: :cpp:func:`OGR_G_Is3D`" +msgstr "" + +#: of osgeo.ogr.Geometry.Is3D:7 +msgid "True if the geometry has Z coordinates." +msgstr "" + +#: of osgeo.ogr.Geometry.IsEmpty:1 +msgid "Test if the geometry is empty." +msgstr "" + +#: of osgeo.ogr.Geometry.IsEmpty:3 +msgid "For more details: :cpp:func:`OGR_G_IsEmpty`" +msgstr "" + +#: of osgeo.ogr.Geometry.IsEmpty:5 osgeo.ogr.Geometry.IsRing:5 +#: osgeo.ogr.Geometry.IsValid:5 +msgid "True if the geometry has no points, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.IsMeasured:1 +msgid "See whether this geometry is measured." +msgstr "" + +#: of osgeo.ogr.Geometry.IsMeasured:3 +msgid "For more details: :cpp:func:`OGR_G_IsMeasured`" +msgstr "" + +#: of osgeo.ogr.Geometry.IsMeasured:7 +msgid "True if the geometry has M coordinates." +msgstr "" + +#: of osgeo.ogr.Geometry.IsRing:1 +msgid "Test if the geometry is a ring." +msgstr "" + +#: of osgeo.ogr.Geometry.IsRing:3 +msgid "For more details: :cpp:func:`OGR_G_IsRing`" +msgstr "" + +#: of osgeo.ogr.Geometry.IsSimple:1 +msgid "Returns True if the geometry is simple." +msgstr "" + +#: of osgeo.ogr.Geometry.IsSimple:3 +msgid "For more details: :cpp:func:`OGR_G_IsSimple`" +msgstr "" + +#: of osgeo.ogr.Geometry.IsSimple:5 +msgid "True if object is simple, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.IsValid:1 +msgid "Test if the geometry is valid." +msgstr "" + +#: of osgeo.ogr.Geometry.IsValid:3 +msgid "For more details: :cpp:func:`OGR_G_IsValid`" +msgstr "" + +#: of osgeo.ogr.Geometry.MakeValid:1 +msgid "Attempts to make an invalid geometry valid without losing vertices." +msgstr "" + +#: of osgeo.ogr.Geometry.MakeValid:3 +msgid "For more details: :cpp:func:`OGR_G_MakeValidEx`" +msgstr "" + +#: of osgeo.ogr.Geometry.MakeValid:6 +msgid "options" +msgstr "" + +#: of osgeo.ogr.Geometry.MakeValid:8 +msgid "papszOptions to be passed in. For example: [\"METHOD=STRUCTURE\"]." +msgstr "" + +#: of osgeo.ogr.Geometry.MakeValid:11 osgeo.ogr.Geometry.Normalize:7 +msgid "A newly allocated geometry now owned by the caller, or None on failure." +msgstr "" + +#: of osgeo.ogr.Geometry.Normalize:1 +msgid "Attempts to bring geometry into normalized/canonical form." +msgstr "" + +#: of osgeo.ogr.Geometry.Normalize:3 +msgid "For more details: :cpp:func:`OGR_G_Normalize`" +msgstr "" + +#: of osgeo.ogr.Geometry.Overlaps:1 +msgid "Test for overlap." +msgstr "" + +#: of osgeo.ogr.Geometry.Overlaps:3 +msgid "For more details: :cpp:func:`OGR_G_Overlaps`" +msgstr "" + +#: of osgeo.ogr.Geometry.Overlaps:8 +msgid "True if they are overlapping, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.PointOnSurface:1 +msgid "Returns a point guaranteed to lie on the surface." +msgstr "" + +#: of osgeo.ogr.Geometry.PointOnSurface:3 +msgid "For more details: :cpp:func:`OGR_G_PointOnSurface`" +msgstr "" + +#: of osgeo.ogr.Geometry.PointOnSurface:5 +msgid "A point guaranteed to lie on the surface or None if an error occurred." +msgstr "" + +#: of osgeo.ogr.Geometry.Polygonize:1 +msgid "Polygonizes a set of sparse edges." +msgstr "" + +#: of osgeo.ogr.Geometry.Polygonize:3 +msgid "For more details: :cpp:func:`OGR_G_Polygonize`" +msgstr "" + +#: of osgeo.ogr.Geometry.Segmentize:1 +msgid "Modify the geometry such it has no segment longer then the given distance." +msgstr "" + +#: of osgeo.ogr.Geometry.Segmentize:4 +msgid "For more details: :cpp:func:`OGR_G_Segmentize`" +msgstr "" + +#: of osgeo.ogr.Geometry.Segmentize:6 +msgid "the maximum distance between 2 points after segmentization" +msgstr "" + +#: of osgeo.ogr.Geometry.Set3D:1 +msgid "Add or remove the Z coordinate dimension." +msgstr "" + +#: of osgeo.ogr.Geometry.Set3D:3 +msgid "For more details: :cpp:func:`OGR_G_Set3D`" +msgstr "" + +#: of osgeo.ogr.Geometry.Set3D:7 +msgid "Should the geometry have a Z dimension, either True or False." +msgstr "" + +#: of osgeo.ogr.Geometry.SetCoordinateDimension:1 +msgid "Set the coordinate dimension." +msgstr "" + +#: of osgeo.ogr.Geometry.SetCoordinateDimension:3 +msgid "For more details: :cpp:func:`OGR_G_SetCoordinateDimension`" +msgstr "" + +#: of osgeo.ogr.Geometry.SetCoordinateDimension:5 +msgid "Deprecated. Use :py:func:`Set3D` or :py:func:`SetMeasured`." +msgstr "" + +#: of osgeo.ogr.Geometry.SetCoordinateDimension:7 +msgid "New coordinate dimension value, either 2 or 3." +msgstr "" + +#: of osgeo.ogr.Geometry.SetMeasured:1 +msgid "Add or remove the M coordinate dimension." +msgstr "" + +#: of osgeo.ogr.Geometry.SetMeasured:3 +msgid "For more details: :cpp:func:`OGR_G_SetMeasured`" +msgstr "" + +#: of osgeo.ogr.Geometry.SetMeasured:7 +msgid "Should the geometry have a M dimension, either True or False." +msgstr "" + +#: of osgeo.ogr.Geometry.Simplify:1 +msgid "Compute a simplified geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.Simplify:3 +msgid "For more details: :cpp:func:`OGR_G_Simplify`" +msgstr "" + +#: of osgeo.ogr.Geometry.Simplify:5 +#: osgeo.ogr.Geometry.SimplifyPreserveTopology:5 +msgid "The distance tolerance for the simplification." +msgstr "" + +#: of osgeo.ogr.Geometry.Simplify:8 +#: osgeo.ogr.Geometry.SimplifyPreserveTopology:8 +msgid "The simplified geometry or None if an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.SimplifyPreserveTopology:1 +msgid "Simplify the geometry while preserving topology." +msgstr "" + +#: of osgeo.ogr.Geometry.SimplifyPreserveTopology:3 +msgid "For more details: :cpp:func:`OGR_G_SimplifyPreserveTopology`" +msgstr "" + +#: of osgeo.ogr.Geometry.SwapXY:1 +msgid "Swap x and y coordinates." +msgstr "" + +#: of osgeo.ogr.Geometry.SwapXY:3 +msgid "For more details: :cpp:func:`OGR_G_SwapXY`" +msgstr "" + +#: of osgeo.ogr.Geometry.SymDifference:1 +msgid "Compute symmetric difference." +msgstr "" + +#: of osgeo.ogr.Geometry.SymDifference:3 +msgid "For more details: :cpp:func:`OGR_G_SymDifference`" +msgstr "" + +#: of osgeo.ogr.Geometry.SymDifference:5 +msgid "the other geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.SymDifference:7 +msgid "" +"A new geometry representing the symmetric difference or None if the " +"difference is empty or an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.SymmetricDifference:1 +msgid "Compute symmetric difference (deprecated)" +msgstr "" + +#: of osgeo.ogr.Geometry.SymmetricDifference:3 +msgid "For more details: :cpp:func:`OGR_G_SymmetricDifference`" +msgstr "" + +#: of osgeo.ogr.Geometry.SymmetricDifference:5 +msgid "Deprecated" +msgstr "" + +#: of osgeo.ogr.Geometry.Touches:1 +msgid "Test for touching." +msgstr "" + +#: of osgeo.ogr.Geometry.Touches:3 +msgid "For more details: :cpp:func:`OGR_G_Touches`" +msgstr "" + +#: of osgeo.ogr.Geometry.Touches:7 +msgid "True if they are touching, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.Transform:1 +msgid "Apply arbitrary coordinate transformation to geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.Transform:3 +msgid "For more details: :cpp:func:`OGR_G_Transform`" +msgstr "" + +#: of osgeo.ogr.Geometry.Transform:5 +msgid "The transformation to apply." +msgstr "" + +#: of osgeo.ogr.Geometry.Transform:8 +msgid "The transformed geometry." +msgstr "" + +#: of osgeo.ogr.Geometry.TransformTo:1 +msgid "Transform geometry to new spatial reference system." +msgstr "" + +#: of osgeo.ogr.Geometry.TransformTo:3 +msgid "For more details: :cpp:func:`OGR_G_TransformTo`" +msgstr "" + +#: of osgeo.ogr.Geometry.TransformTo:5 +msgid "The spatial reference system to apply." +msgstr "" + +#: of osgeo.ogr.Geometry.TransformTo:8 +msgid ":py:const:`osgeo.ogr.OGRERR_NONE` on success, or an error code." +msgstr "" + +#: of osgeo.ogr.Geometry.Union:1 +msgid "Compute union." +msgstr "" + +#: of osgeo.ogr.Geometry.Union:3 +msgid "For more details: :cpp:func:`OGR_G_Union`" +msgstr "" + +#: of osgeo.ogr.Geometry.Union:8 osgeo.ogr.Geometry.UnionCascaded:5 +msgid "A new geometry representing the union or None if an error occurs." +msgstr "" + +#: of osgeo.ogr.Geometry.UnionCascaded:1 +msgid "Compute union using cascading." +msgstr "" + +#: of osgeo.ogr.Geometry.UnionCascaded:3 +msgid "For more deails: :cpp:func:`OGR_G_UnionCascaded`" +msgstr "" + +#: of osgeo.ogr.Geometry.Within:3 +msgid "For more details: :cpp:func:`OGR_G_Within`" +msgstr "" + +#: of osgeo.ogr.Geometry.Within:8 +msgid "True if this is within other, otherwise False." +msgstr "" + +#: of osgeo.ogr.Geometry.WkbSize:1 +msgid "Returns size of related binary representation." +msgstr "" + +#: of osgeo.ogr.Geometry.WkbSize:3 +msgid "For more details: :cpp:func:`OGR_G_WkbSize`" +msgstr "" + +#: ../../source/api/python/vector_api.rst:98 +msgid "FeatureDefn" +msgstr "" + +#: of osgeo.ogr.FeatureDefn:1 +msgid "Proxy of C++ OGRFeatureDefnShadow class." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:1 +msgid "void OGR_FD_AddFieldDefn(OGRFeatureDefnH hDefn, OGRFieldDefnH hNewField)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:4 +#: osgeo.ogr.FeatureDefn.AddGeomFieldDefn:5 +msgid "Add a new field definition to the passed feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:6 +msgid "" +"To add a new field definition to a layer definition, do not use this " +"function directly, but use OGR_L_CreateField() instead." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:9 +msgid "" +"This function should only be called while there are no OGRFeature objects" +" in existence based on this OGRFeatureDefn. The OGRFieldDefn passed in is" +" copied, and remains the responsibility of the caller." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:13 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::AddFieldDefn()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:16 +msgid "handle to the feature definition to add the field definition to." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddFieldDefn:17 +#: osgeo.ogr.FeatureDefn.AddGeomFieldDefn:22 +msgid "handle to the new field definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddGeomFieldDefn:1 +msgid "" +"void OGR_FD_AddGeomFieldDefn(OGRFeatureDefnH hDefn, OGRGeomFieldDefnH " +"hNewGeomField)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddGeomFieldDefn:7 +msgid "" +"To add a new field definition to a layer definition, do not use this " +"function directly, but use OGR_L_CreateGeomField() instead." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddGeomFieldDefn:10 +msgid "" +"This function should only be called while there are no OGRFeature objects" +" in existence based on this OGRFeatureDefn. The OGRGeomFieldDefn passed " +"in is copied, and remains the responsibility of the caller." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddGeomFieldDefn:15 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::AddGeomFieldDefn()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.AddGeomFieldDefn:20 +msgid "handle to the feature definition to add the geometry field definition to." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:1 +msgid "OGRErr OGR_FD_DeleteGeomFieldDefn(OGRFeatureDefnH hDefn, int iGeomField)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:4 +msgid "Delete an existing geometry field definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:6 +msgid "" +"To delete an existing geometry field definition from a layer definition, " +"do not use this function directly, but use OGR_L_DeleteGeomField() " +"instead ( not implemented yet)." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:10 +msgid "" +"This method should only be called while there are no OGRFeature objects " +"in existence based on this OGRFeatureDefn." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:13 +msgid "" +"This method is the same as the C++ method " +"OGRFeatureDefn::DeleteGeomFieldDefn()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:18 +msgid "handle to the feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:19 +msgid "the index of the geometry field definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.DeleteGeomFieldDefn:21 +msgid "OGRERR_NONE in case of success." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldCount:1 +msgid "int OGR_FD_GetFieldCount(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldCount:4 +msgid "Fetch number of fields on the passed feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldCount:6 +msgid "This function is the same as the C++ OGRFeatureDefn::GetFieldCount()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldCount:8 +#: osgeo.ogr.FeatureDefn.GetGeomFieldCount:11 +msgid "handle to the feature definition to get the fields count from." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldDefn:1 +msgid "OGRFieldDefnH OGR_FD_GetFieldDefn(OGRFeatureDefnH hDefn, int iField)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldDefn:4 +msgid "Fetch field definition of the passed feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldDefn:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::GetFieldDefn()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldDefn:9 +#: osgeo.ogr.FeatureDefn.GetGeomFieldDefn:11 +msgid "handle to the feature definition to get the field definition from." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldDefn:10 +msgid "the field to fetch, between 0 and GetFieldCount()-1." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldDefn:12 +#: osgeo.ogr.FeatureDefn.GetGeomFieldDefn:14 +msgid "" +"a handle to an internal field definition object or NULL if invalid index." +" This object should not be modified or freed by the application." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:1 +msgid "" +"int OGR_FD_GetFieldIndex(OGRFeatureDefnH hDefn, const char " +"\\*pszFieldName)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:4 +msgid "Find field by name." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:6 +msgid "" +"The field index of the first field matching the passed field name (case " +"insensitively) is returned." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:9 +msgid "This function is the same as the C++ method OGRFeatureDefn::GetFieldIndex." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:12 +#: osgeo.ogr.FeatureDefn.GetGeomFieldIndex:13 +msgid "handle to the feature definition to get field index from." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:13 +msgid "the field name to search for." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetFieldIndex:15 +msgid "the field index, or -1 if no match found." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldCount:1 +msgid "int OGR_FD_GetGeomFieldCount(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldCount:4 +msgid "Fetch number of geometry fields on the passed feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldCount:6 +msgid "This function is the same as the C++ OGRFeatureDefn::GetGeomFieldCount()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldDefn:1 +msgid "" +"OGRGeomFieldDefnH OGR_FD_GetGeomFieldDefn(OGRFeatureDefnH hDefn, int " +"iGeomField)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldDefn:4 +msgid "Fetch geometry field definition of the passed feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldDefn:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::GetGeomFieldDefn()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldDefn:12 +msgid "the geometry field to fetch, between 0 and GetGeomFieldCount() - 1." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldIndex:1 +msgid "" +"int OGR_FD_GetGeomFieldIndex(OGRFeatureDefnH hDefn, const char " +"\\*pszGeomFieldName)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldIndex:5 +msgid "Find geometry field by name." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldIndex:7 +msgid "" +"The geometry field index of the first geometry field matching the passed " +"field name (case insensitively) is returned." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldIndex:10 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::GetGeomFieldIndex." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldIndex:14 +msgid "the geometry field name to search for." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomFieldIndex:16 +msgid "the geometry field index, or -1 if no match found." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomType:1 +msgid "OGRwkbGeometryType OGR_FD_GetGeomType(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomType:4 +msgid "Fetch the geometry base type of the passed feature definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomType:6 +msgid "This function is the same as the C++ method OGRFeatureDefn::GetGeomType()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomType:9 +msgid "" +"Starting with GDAL 1.11, this method returns " +"GetGeomFieldDefn(0)->GetType()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomType:12 +msgid "handle to the feature definition to get the geometry type from." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetGeomType:14 +msgid "the base type for all geometry related to this definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetName:1 +msgid "const char\\* OGR_FD_GetName(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetName:4 +msgid "Get name of the OGRFeatureDefn passed as an argument." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetName:6 +msgid "This function is the same as the C++ method OGRFeatureDefn::GetName()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetName:8 +msgid "handle to the feature definition to get the name from." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetName:10 +msgid "the name. This name is internal and should not be modified, or freed." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetReferenceCount:1 +msgid "int OGR_FD_GetReferenceCount(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetReferenceCount:4 +msgid "Fetch current reference count." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetReferenceCount:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::GetReferenceCount()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetReferenceCount:9 +#: osgeo.ogr.FeatureDefn.IsGeometryIgnored:12 osgeo.ogr.FeatureDefn.IsSame:8 +#: osgeo.ogr.FeatureDefn.SetGeometryIgnored:12 +#: osgeo.ogr.FeatureDefn.SetStyleIgnored:9 +msgid "handle to the feature definition on witch OGRFeature are based on." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.GetReferenceCount:11 +msgid "the current reference count." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsGeometryIgnored:1 +msgid "int OGR_FD_IsGeometryIgnored(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsGeometryIgnored:4 +msgid "Determine whether the geometry can be omitted when fetching features." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsGeometryIgnored:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::IsGeometryIgnored()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsGeometryIgnored:9 +msgid "" +"Starting with GDAL 1.11, this method returns " +"GetGeomFieldDefn(0)->IsIgnored()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsGeometryIgnored:14 +#: osgeo.ogr.FeatureDefn.IsStyleIgnored:11 +#: osgeo.ogr.FeatureDefn.SetGeometryIgnored:13 +#: osgeo.ogr.FeatureDefn.SetStyleIgnored:10 osgeo.ogr.FieldDefn.IsIgnored:10 +#: osgeo.ogr.FieldDefn.SetIgnored:9 +msgid "ignore state" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsSame:1 +msgid "int OGR_FD_IsSame(OGRFeatureDefnH hFDefn, OGRFeatureDefnH hOtherFDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsSame:4 +msgid "Test if the feature definition is identical to the other one." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsSame:9 +msgid "handle to the other feature definition to compare to." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsSame:11 +msgid "TRUE if the feature definition is identical to the other one." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsStyleIgnored:1 +msgid "int OGR_FD_IsStyleIgnored(OGRFeatureDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsStyleIgnored:4 +msgid "Determine whether the style can be omitted when fetching features." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsStyleIgnored:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::IsStyleIgnored()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.IsStyleIgnored:9 +msgid "handle to the feature definition on which OGRFeature are based on." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:1 +msgid "void OGR_FD_SetGeomType(OGRFeatureDefnH hDefn, OGRwkbGeometryType eType)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:4 +msgid "" +"Assign the base geometry type for the passed layer (the same as the " +"feature definition)." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:7 +msgid "" +"All geometry objects using this type must be of the defined type or a " +"derived type. The default upon creation is wkbUnknown which allows for " +"any geometry type. The geometry type should generally not be changed " +"after any OGRFeatures have been created against this definition." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:12 +msgid "This function is the same as the C++ method OGRFeatureDefn::SetGeomType()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:15 +msgid "Starting with GDAL 1.11, this method calls GetGeomFieldDefn(0)->SetType()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:18 +msgid "handle to the layer or feature definition to set the geometry type to." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeomType:19 +msgid "the new type to assign." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeometryIgnored:1 +msgid "void OGR_FD_SetGeometryIgnored(OGRFeatureDefnH hDefn, int bIgnore)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeometryIgnored:4 +msgid "Set whether the geometry can be omitted when fetching features." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeometryIgnored:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::SetGeometryIgnored()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetGeometryIgnored:9 +msgid "" +"Starting with GDAL 1.11, this method calls " +"GetGeomFieldDefn(0)->SetIgnored()." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetStyleIgnored:1 +msgid "void OGR_FD_SetStyleIgnored(OGRFeatureDefnH hDefn, int bIgnore)" +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetStyleIgnored:4 +msgid "Set whether the style can be omitted when fetching features." +msgstr "" + +#: of osgeo.ogr.FeatureDefn.SetStyleIgnored:6 +msgid "" +"This function is the same as the C++ method " +"OGRFeatureDefn::SetStyleIgnored()." +msgstr "" + +#: ../../source/api/python/vector_api.rst:106 +msgid "FieldDefn" +msgstr "" + +#: of osgeo.ogr.FieldDefn:1 +msgid "Proxy of C++ OGRFieldDefnShadow class." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:1 +msgid "const char\\* OGR_Fld_GetAlternativeNameRef(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:4 +msgid "Fetch the alternative name (or \"alias\") for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:6 +#: osgeo.ogr.FieldDefn.SetAlternativeName:7 +msgid "" +"The alternative name is an optional attribute for a field which can " +"provide a more user-friendly, descriptive name of a field which is not " +"subject to the usual naming constraints defined by the data provider." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:10 +#: osgeo.ogr.FieldDefn.SetAlternativeName:11 +msgid "" +"This is a metadata style attribute only: the alternative name cannot be " +"used in place of the actual field name during SQL queries or other field " +"name dependent API calls." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:14 +msgid "" +"This function is the same as the CPP method " +"OGRFieldDefn::GetAlternativeNameRef()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:19 +#: osgeo.ogr.FieldDefn.GetDefault:11 osgeo.ogr.FieldDefn.GetNameRef:9 +#: osgeo.ogr.FieldDefn.SetDefault:29 +msgid "handle to the field definition." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetAlternativeNameRef:21 +msgid "the alternative name of the field definition." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDefault:1 +msgid "const char\\* OGR_Fld_GetDefault(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDefault:4 +msgid "Get default field value." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDefault:6 +msgid "This function is the same as the C++ method OGRFieldDefn::GetDefault()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDefault:13 +msgid "default field value or NULL." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:1 +msgid "const char\\* OGR_Fld_GetDomainName(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:4 +msgid "Return the name of the field domain for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:6 +msgid "By default, none (empty string) is returned." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:8 +msgid "" +"Field domains ( OGRFieldDomain class) are attached at the GDALDataset " +"level and should be retrieved with GDALDatasetGetFieldDomain()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:11 +msgid "This method is the same as the C++ method OGRFieldDefn::GetDomainName()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:16 +#: osgeo.ogr.FieldDefn.IsDefaultDriverSpecific:16 +#: osgeo.ogr.FieldDefn.IsIgnored:8 osgeo.ogr.FieldDefn.IsNullable:17 +#: osgeo.ogr.FieldDefn.IsUnique:12 osgeo.ogr.FieldDefn.SetDomainName:13 +#: osgeo.ogr.FieldDefn.SetIgnored:8 osgeo.ogr.FieldDefn.SetNullable:16 +#: osgeo.ogr.FieldDefn.SetUnique:17 +msgid "handle to the field definition" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetDomainName:18 +msgid "the field domain name, or an empty string if there is none." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetJustify:1 +msgid "OGRJustification OGR_Fld_GetJustify(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetJustify:4 osgeo.ogr.FieldDefn.justify:5 +msgid "Get the justification for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetJustify:6 osgeo.ogr.FieldDefn.justify:7 +msgid "This function is the same as the CPP method OGRFieldDefn::GetJustify()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetJustify:9 osgeo.ogr.FieldDefn.SetJustify:6 +#: osgeo.ogr.FieldDefn.justify:10 +msgid "Note: no driver is know to use the concept of field justification." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetJustify:11 osgeo.ogr.FieldDefn.justify:12 +msgid "handle to the field definition to get justification from." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetJustify:13 osgeo.ogr.FieldDefn.justify:14 +msgid "the justification." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetNameRef:1 +msgid "const char\\* OGR_Fld_GetNameRef(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetNameRef:4 +msgid "Fetch name of this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetNameRef:6 +msgid "This function is the same as the CPP method OGRFieldDefn::GetNameRef()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetNameRef:11 +msgid "the name of the field definition." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetPrecision:1 +msgid "int OGR_Fld_GetPrecision(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetPrecision:4 osgeo.ogr.FieldDefn.precision:5 +msgid "Get the formatting precision for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetPrecision:6 osgeo.ogr.FieldDefn.SetPrecision:6 +#: osgeo.ogr.FieldDefn.precision:7 +msgid "This should normally be zero for fields of types other than OFTReal." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetPrecision:8 osgeo.ogr.FieldDefn.precision:9 +msgid "This function is the same as the CPP method OGRFieldDefn::GetPrecision()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetPrecision:11 osgeo.ogr.FieldDefn.precision:12 +msgid "handle to the field definition to get precision from." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetPrecision:13 osgeo.ogr.FieldDefn.precision:14 +msgid "the precision." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetSubType:1 +msgid "OGRFieldSubType OGR_Fld_GetSubType(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetSubType:4 +msgid "Fetch subtype of this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetSubType:6 +msgid "This function is the same as the CPP method OGRFieldDefn::GetSubType()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetSubType:11 +msgid "handle to the field definition to get subtype from." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetSubType:13 +msgid "field subtype." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetType:1 +msgid "OGRFieldType OGR_Fld_GetType(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetType:4 osgeo.ogr.FieldDefn.type:5 +msgid "Fetch type of this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetType:6 osgeo.ogr.FieldDefn.type:7 +msgid "This function is the same as the CPP method OGRFieldDefn::GetType()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetType:8 osgeo.ogr.FieldDefn.type:9 +msgid "handle to the field definition to get type from." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetType:10 osgeo.ogr.FieldDefn.type:11 +msgid "field type." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetWidth:1 +msgid "int OGR_Fld_GetWidth(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetWidth:4 osgeo.ogr.FieldDefn.width:5 +msgid "Get the formatting width for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetWidth:6 osgeo.ogr.FieldDefn.width:7 +msgid "This function is the same as the CPP method OGRFieldDefn::GetWidth()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetWidth:8 osgeo.ogr.FieldDefn.width:9 +msgid "handle to the field definition to get width from." +msgstr "" + +#: of osgeo.ogr.FieldDefn.GetWidth:10 osgeo.ogr.FieldDefn.width:11 +msgid "the width, zero means no specified width." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsDefaultDriverSpecific:1 +msgid "int OGR_Fld_IsDefaultDriverSpecific(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsDefaultDriverSpecific:4 +msgid "Returns whether the default value is driver specific." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsDefaultDriverSpecific:6 +msgid "" +"Driver specific default values are those that are not NULL, a numeric " +"value, a literal value enclosed between single quote characters, " +"CURRENT_TIMESTAMP, CURRENT_TIME, CURRENT_DATE or datetime literal value." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsDefaultDriverSpecific:11 +msgid "" +"This function is the same as the C++ method " +"OGRFieldDefn::IsDefaultDriverSpecific()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsDefaultDriverSpecific:18 +msgid "TRUE if the default value is driver specific." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsIgnored:1 +msgid "int OGR_Fld_IsIgnored(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsIgnored:4 +msgid "Return whether this field should be omitted when fetching features." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsIgnored:6 +msgid "This method is the same as the C++ method OGRFieldDefn::IsIgnored()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsNullable:1 +msgid "int OGR_Fld_IsNullable(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsNullable:4 +msgid "Return whether this field can receive null values." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsNullable:6 +msgid "By default, fields are nullable." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsNullable:8 +msgid "" +"Even if this method returns FALSE (i.e not-nullable field), it doesn't " +"mean that OGRFeature::IsFieldSet() will necessary return TRUE, as fields " +"can be temporary unset and null/not-null validation is usually done when " +"OGRLayer::CreateFeature()/SetFeature() is called." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsNullable:13 +msgid "This method is the same as the C++ method OGRFieldDefn::IsNullable()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsNullable:19 +msgid "TRUE if the field is authorized to be null." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsUnique:1 +msgid "int OGR_Fld_IsUnique(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsUnique:4 +msgid "Return whether this field has a unique constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsUnique:6 +msgid "By default, fields have no unique constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsUnique:8 +msgid "This method is the same as the C++ method OGRFieldDefn::IsUnique()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.IsUnique:14 +msgid "TRUE if the field has a unique constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetAlternativeName:1 +msgid "" +"void OGR_Fld_SetAlternativeName(OGRFieldDefnH hDefn, const char " +"\\*pszAlternativeName)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetAlternativeName:5 +msgid "Reset the alternative name (or \"alias\") for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetAlternativeName:15 +msgid "" +"This function is the same as the CPP method " +"OGRFieldDefn::SetAlternativeName()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetAlternativeName:20 +msgid "handle to the field definition to apply the new alternative name to." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetAlternativeName:21 +msgid "the new alternative name to apply." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:1 +msgid "void OGR_Fld_SetDefault(OGRFieldDefnH hDefn, const char \\*pszDefault)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:4 +msgid "Set default field value." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:6 +msgid "" +"The default field value is taken into account by drivers (generally those" +" with a SQL interface) that support it at field creation time. OGR will " +"generally not automatically set the default field value to null fields by" +" itself when calling OGRFeature::CreateFeature() / " +"OGRFeature::SetFeature(), but will let the low-level layers to do the " +"job. So retrieving the feature from the layer is recommended." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:13 +msgid "" +"The accepted values are NULL, a numeric value, a literal value enclosed " +"between single quote characters (and inner single quote characters " +"escaped by repetition of the single quote character), CURRENT_TIMESTAMP, " +"CURRENT_TIME, CURRENT_DATE or a driver specific expression (that might be" +" ignored by other drivers). For a datetime literal value, format should " +"be 'YYYY/MM/DD HH:MM:SS[.sss]' (considered as UTC time)." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:21 +msgid "" +"Drivers that support writing DEFAULT clauses will advertise the " +"GDAL_DCAP_DEFAULT_FIELDS driver metadata item." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:24 +msgid "This function is the same as the C++ method OGRFieldDefn::SetDefault()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDefault:30 +msgid "new default field value or NULL pointer." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDomainName:1 +msgid "" +"void OGR_Fld_SetDomainName(OGRFieldDefnH hDefn, const char " +"\\*pszFieldName)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDomainName:4 +msgid "Set the name of the field domain for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDomainName:6 +msgid "Field domains ( OGRFieldDomain) are attached at the GDALDataset level." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDomainName:8 +msgid "This method is the same as the C++ method OGRFieldDefn::SetDomainName()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetDomainName:14 +msgid "Field domain name." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetIgnored:1 +msgid "void OGR_Fld_SetIgnored(OGRFieldDefnH hDefn, int ignore)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetIgnored:4 +msgid "Set whether this field should be omitted when fetching features." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetIgnored:6 +msgid "This method is the same as the C++ method OGRFieldDefn::SetIgnored()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetJustify:1 +msgid "void OGR_Fld_SetJustify(OGRFieldDefnH hDefn, OGRJustification eJustify)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetJustify:4 +msgid "Set the justification for this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetJustify:8 +msgid "This function is the same as the CPP method OGRFieldDefn::SetJustify()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetJustify:11 +msgid "handle to the field definition to set justification to." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetJustify:12 +msgid "the new justification." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetName:1 +msgid "void OGR_Fld_SetName(OGRFieldDefnH hDefn, const char \\*pszName)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetName:4 +msgid "Reset the name of this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetName:6 +msgid "This function is the same as the CPP method OGRFieldDefn::SetName()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetName:8 +msgid "handle to the field definition to apply the new name to." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetName:9 +msgid "the new name to apply." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetNullable:1 +msgid "void OGR_Fld_SetNullable(OGRFieldDefnH hDefn, int bNullableIn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetNullable:4 +msgid "Set whether this field can receive null values." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetNullable:6 +msgid "" +"By default, fields are nullable, so this method is generally called with " +"FALSE to set a not-null constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetNullable:9 +msgid "" +"Drivers that support writing not-null constraint will advertise the " +"GDAL_DCAP_NOTNULL_FIELDS driver metadata item." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetNullable:12 +msgid "This method is the same as the C++ method OGRFieldDefn::SetNullable()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetNullable:17 +msgid "FALSE if the field must have a not-null constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetPrecision:1 +msgid "void OGR_Fld_SetPrecision(OGRFieldDefnH hDefn, int nPrecision)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetPrecision:4 +msgid "Set the formatting precision for this field in characters." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetPrecision:8 +msgid "This function is the same as the CPP method OGRFieldDefn::SetPrecision()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetPrecision:11 +msgid "handle to the field definition to set precision to." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetPrecision:12 +msgid "the new precision." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetSubType:1 +msgid "void OGR_Fld_SetSubType(OGRFieldDefnH hDefn, OGRFieldSubType eSubType)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetSubType:4 +msgid "Set the subtype of this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetSubType:6 osgeo.ogr.FieldDefn.SetType:6 +msgid "" +"This should never be done to an OGRFieldDefn that is already part of an " +"OGRFeatureDefn." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetSubType:9 +msgid "This function is the same as the CPP method OGRFieldDefn::SetSubType()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetSubType:14 osgeo.ogr.FieldDefn.SetType:11 +msgid "handle to the field definition to set type to." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetSubType:15 +msgid "the new field subtype." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetType:1 +msgid "void OGR_Fld_SetType(OGRFieldDefnH hDefn, OGRFieldType eType)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetType:4 +msgid "Set the type of this field." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetType:9 +msgid "This function is the same as the CPP method OGRFieldDefn::SetType()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetType:12 +msgid "the new field type." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetUnique:1 +msgid "void OGR_Fld_SetUnique(OGRFieldDefnH hDefn, int bUniqueIn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetUnique:4 +msgid "Set whether this field has a unique constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetUnique:6 +msgid "" +"By default, fields have no unique constraint, so this method is generally" +" called with TRUE to set a unique constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetUnique:9 +msgid "" +"Drivers that support writing unique constraint will advertise the " +"GDAL_DCAP_UNIQUE_FIELDS driver metadata item. field can receive null " +"values." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetUnique:13 +msgid "This method is the same as the C++ method OGRFieldDefn::SetUnique()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetUnique:18 +msgid "TRUE if the field must have a unique constraint." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetWidth:1 +msgid "void OGR_Fld_SetWidth(OGRFieldDefnH hDefn, int nNewWidth)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetWidth:4 +msgid "Set the formatting width for this field in characters." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetWidth:6 +msgid "This function is the same as the CPP method OGRFieldDefn::SetWidth()." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetWidth:8 +msgid "handle to the field definition to set width to." +msgstr "" + +#: of osgeo.ogr.FieldDefn.SetWidth:9 +msgid "the new width." +msgstr "" + +#: of osgeo.ogr.FieldDefn.justify:1 +msgid "" +"GetJustify(FieldDefn self) -> OGRJustification OGRJustification " +"OGR_Fld_GetJustify(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.name:1 +msgid "GetName(FieldDefn self) -> char const *" +msgstr "" + +#: of osgeo.ogr.FieldDefn.precision:1 +msgid "" +"GetPrecision(FieldDefn self) -> int int " +"OGR_Fld_GetPrecision(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.type:1 +msgid "" +"GetType(FieldDefn self) -> OGRFieldType OGRFieldType " +"OGR_Fld_GetType(OGRFieldDefnH hDefn)" +msgstr "" + +#: of osgeo.ogr.FieldDefn.width:1 +msgid "GetWidth(FieldDefn self) -> int int OGR_Fld_GetWidth(OGRFieldDefnH hDefn)" +msgstr "" + +#: ../../source/api/python/vector_api.rst:118 +msgid "GeomFieldDefn" +msgstr "" + +#: of osgeo.ogr.GeomFieldDefn:1 +msgid "Proxy of C++ OGRGeomFieldDefnShadow class." +msgstr "" + +#: of osgeo.ogr.GeomFieldDefn.name:1 +msgid "GetName(GeomFieldDefn self) -> char const *" +msgstr "" + +#: of osgeo.ogr.GeomFieldDefn.srs:1 +msgid "GetSpatialRef(GeomFieldDefn self) -> SpatialReference" +msgstr "" + +#: of osgeo.ogr.GeomFieldDefn.type:1 +msgid "GetType(GeomFieldDefn self) -> OGRwkbGeometryType" +msgstr "" + +#: ../../source/api/python/vector_api.rst:126 +msgid "FieldDomain" +msgstr "" + +#: of osgeo.ogr.FieldDomain:1 +msgid "Proxy of C++ OGRFieldDomainShadow class." +msgstr "" + +#: ../../source/api/python/vector_api.rst:140 +msgid "Relationship" +msgstr "" + +#: of osgeo.gdal.Relationship:1 +msgid "Proxy of C++ GDALRelationshipShadow class." +msgstr "" + +#: ../../source/api/python/vector_api.rst:148 +msgid "StyleTable" +msgstr "" + +#: of osgeo.ogr.StyleTable:1 +msgid "Proxy of C++ OGRStyleTableShadow class." +msgstr "" + +#: ../../source/api/python_bindings.rst:5 +msgid "General information" +msgstr "" + +#: ../../source/api/python_bindings.rst:7 +msgid "" +"This Python package and extensions are a number of tools for programming " +"and manipulating the GDAL_ Geospatial Data Abstraction Library." +msgstr "" + +#: ../../source/api/python_bindings.rst:9 +msgid "" +"The GDAL project maintains SWIG generated Python bindings for GDAL/OGR. " +"Generally speaking the classes and methods mostly match those of the GDAL" +" and OGR C++ classes. There is no Python specific reference " +"documentation, but the :ref:`tutorials <tutorials>` includes Python " +"examples." +msgstr "" + +#: ../../source/api/python_bindings.rst:15 +msgid "Dependencies" +msgstr "" + +#: ../../source/api/python_bindings.rst:17 +msgid "libgdal and header files (gdal-devel)" +msgstr "" + +#: ../../source/api/python_bindings.rst:18 +msgid "" +"numpy (1.0.0 or greater) and header files (numpy-devel) (not explicitly " +"required, but many examples and utilities will not work without it)" +msgstr "" + +#: ../../source/api/python_bindings.rst:25 +msgid "Conda" +msgstr "" + +#: ../../source/api/python_bindings.rst:27 +msgid "" +"GDAL can be quite complex to build and install, particularly on Windows " +"and MacOS. Pre built binaries are provided for the conda system:" +msgstr "" + +#: ../../source/api/python_bindings.rst:30 +msgid "https://docs.conda.io/en/latest/" +msgstr "" + +#: ../../source/api/python_bindings.rst:32 +msgid "By the conda-forge project:" +msgstr "" + +#: ../../source/api/python_bindings.rst:34 +msgid "https://conda-forge.org/" +msgstr "" + +#: ../../source/api/python_bindings.rst:36 +msgid "" +"Once you have Anaconda or Miniconda installed, you should be able to " +"install GDAL with:" +msgstr "" + +#: ../../source/api/python_bindings.rst:38 +msgid "``conda install -c conda-forge gdal``" +msgstr "" + +#: ../../source/api/python_bindings.rst:41 +msgid "Unix" +msgstr "" + +#: ../../source/api/python_bindings.rst:43 +msgid "The GDAL Python bindings requires setuptools." +msgstr "" + +#: ../../source/api/python_bindings.rst:46 +msgid "pip" +msgstr "" + +#: ../../source/api/python_bindings.rst:48 +msgid "" +"GDAL can be installed from the `Python Package Index " +"<https://pypi.org/project/GDAL>`__:" +msgstr "" + +#: ../../source/api/python_bindings.rst:55 +msgid "" +"In order to enable numpy-based raster support, libgdal and its " +"development headers must be installed as well as the Python packages " +"numpy, setuptools, and wheel. To install the Python dependencies and " +"build numpy-based raster support:" +msgstr "" + +#: ../../source/api/python_bindings.rst:65 +msgid "Users can verify that numpy-based raster support has been installed with:" +msgstr "" + +#: ../../source/api/python_bindings.rst:72 +msgid "" +"If this command raises an ImportError, numpy-based raster support has not" +" been properly installed:" +msgstr "" + +#: ../../source/api/python_bindings.rst:83 +msgid "" +"This is most often due to pip reusing a cached GDAL installation. Verify " +"that the necessary dependencies have been installed and then run the " +"following to force a clean build:" +msgstr "" + +#: ../../source/api/python_bindings.rst:92 +msgid "Potential issues with GDAL >= 3.9, Python >= 3.9 and NumPy 2.0" +msgstr "" + +#: ../../source/api/python_bindings.rst:94 +msgid "" +"The pyproject.toml file of GDAL 3.9 requires numpy >= 2.0.0rc1 (for " +"Python >= 3.9) at build time to be able to build bindings that are " +"compatible of both NumPy 1 and NumPy 2. If for some reason the numpy >= " +"2.0.0rc1 build dependency can not be installed, it is possible to " +"manually install the build requirements, and invoke ``pip install`` with " +"the ``--no-build-isolation`` flag." +msgstr "" + +#: ../../source/api/python_bindings.rst:108 +msgid "Building as part of the GDAL library source tree" +msgstr "" + +#: ../../source/api/python_bindings.rst:110 +msgid "" +"Python bindings are generated by default when building GDAL from source. " +"For more detail, see :ref:`building-python-bindings`." +msgstr "" + +#: ../../source/api/python_bindings.rst:113 +msgid "" +"The GDAL Python package is built using `SWIG <https://www.swig.org>`__. " +"The currently supported version is SWIG >= 4" +msgstr "" + +#: ../../source/api/python_bindings.rst:120 +msgid "Imports" +msgstr "" + +#: ../../source/api/python_bindings.rst:122 +msgid "" +"There are five major modules that are included with the GDAL_ Python " +"bindings.:" +msgstr "" + +#: ../../source/api/python_bindings.rst:135 +msgid "API documentation is available at :ref:`python_osgeo`" +msgstr "" + +#: ../../source/api/python_bindings.rst:138 +msgid "Numpy" +msgstr "" + +#: ../../source/api/python_bindings.rst:140 +msgid "" +"One advanced feature of the GDAL Python bindings not found in the other " +"language bindings is integration with the Python numerical array " +"facilities. The gdal.Dataset.ReadAsArray() method can be used to read " +"raster data as numerical arrays, ready to use with the Python numerical " +"array capabilities." +msgstr "" + +#: ../../source/api/python_bindings.rst:147 +msgid "Tutorials" +msgstr "" + +#: ../../source/api/python_bindings.rst:149 +msgid "" +"Chris Garrard has given courses at Utah State University on " +"\"Geoprocessing with Python using Open Source GIS\" " +"(`http://www.gis.usu.edu/~chrisg/python " +"<http://www.gis.usu.edu/~chrisg/python>`__). There a re many slides, " +"examples, test data... and homework ;-) that can -be greatly helpful for " +"beginners with GDAL/OGR in Python." +msgstr "" + +#: ../../source/api/python_bindings.rst:153 +msgid "" +"A cookbook full of recipes for using the Python GDAL/OGR bindings : " +"`http://pcjericks.github.io/py-gdalogr-cookbook/index.html " +"<http://pcjericks.github.io/py-gdalogr-cookbook/index.html>`__" +msgstr "" + +#: ../../source/api/python_bindings.rst:156 +msgid "Gotchas" +msgstr "" + +#: ../../source/api/python_bindings.rst:158 +msgid "" +"Although GDAL's and OGR's Python bindings provide a fairly \"Pythonic\" " +"wrapper around the underlying C++ code, there are several ways in which " +"the Python bindings differ from typical Python libraries. These " +"differences can catch Python programmers by surprise and lead to " +"unexpected results. These differences result from the complexity of " +"developing a large, long-lived library while continuing to maintain " +"backward compatibility. They are being addressed over time, but until " +"they are all gone, please review this list of :ref:`python_gotchas`." +msgstr "" + +#: ../../source/api/python_bindings.rst:163 +msgid "Examples" +msgstr "" + +#: ../../source/api/python_bindings.rst:165 +msgid "" +"An assortment of other samples are available in the `Python github " +"samples directory <https://github.com/OSGeo/gdal/tree/master/swig/python" +"/gdal-utils/osgeo_utils/samples>`__ with some description in the " +":ref:`python_samples`." +msgstr "" + +#: ../../source/api/python_bindings.rst:167 +msgid "" +"Several `GDAL utilities " +"<https://github.com/OSGeo/gdal/tree/master/swig/python/gdal-" +"utils/osgeo_utils/>`__ are implemented in Python and can be useful " +"examples." +msgstr "" + +#: ../../source/api/python_bindings.rst:169 +msgid "" +"The majority of GDAL regression tests are written in Python. They are " +"available at `https://github.com/OSGeo/gdal/tree/master/autotest " +"<https://github.com/OSGeo/gdal/tree/master/autotest>`__" +msgstr "" + +#: ../../source/api/python_bindings.rst:171 +msgid "" +"Some examples of GDAL/numpy integration can be found is found in the " +"following scripts:" +msgstr "" + +#: ../../source/api/python_bindings.rst:173 +msgid "`gdal_calc.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:174 +msgid "`val_repl.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:175 +msgid "`gdal_merge.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:176 +msgid "`gdal2tiles.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:177 +msgid "`gdal2xyz.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:178 +msgid "`pct2rgb.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:179 +msgid "`gdallocationinfo.py`" +msgstr "" + +#: ../../source/api/python_bindings.rst:181 +msgid "" +"One example of GDAL/numpy integration is found in the `val_repl.py " +"<https://github.com/OSGeo/gdal/tree/master/swig/python/gdal-" +"utils/osgeo_utils/samples/val_repl.py>`__ script." +msgstr "" + +#: ../../source/api/python_bindings.rst:184 +msgid "**Performance Notes**" +msgstr "" + +#: ../../source/api/python_bindings.rst:186 +msgid "" +"ReadAsArray expects to make an entire copy of a raster band or dataset " +"unless the data are explicitly subsetted as part of the function call. " +"For large data, this approach is expected to be prohibitively memory " +"intensive." +msgstr "" + +#: ../../source/api/python_gotchas.rst:5 +msgid "Python Gotchas in the GDAL and OGR Python Bindings" +msgstr "" + +#: ../../source/api/python_gotchas.rst:7 +msgid "" +"This page lists aspects of GDAL's and OGR's Python bindings that may " +"catch Python programmers by surprise. If you find something new, feel " +"free to open a pull request adding it to the list. Consider discussing it" +" on the `gdal-dev mailing list <https://lists.osgeo.org/mailman/listinfo" +"/gdal-dev>`__ first, to make sure you fully understand the issue and " +"that others agree that it is unexpected, \"non-Pythonic\", or something " +"that would catch many Python programmers by surprise. Be sure to " +"reference email threads, GitHub tickets, and other sources of additional " +"information." +msgstr "" + +#: ../../source/api/python_gotchas.rst:13 +msgid "" +"This list is not the place to report bugs. If you believe something is a " +"bug, please `open a ticket <https://github.com/OSGeo/gdal/issues>`__ and " +"report the problem to gdal-dev. Then consider listing it here if it is " +"something related to Python specifically. Do not list it here if it " +"relates to GDAL or OGR generally, and not the Python bindings " +"specifically." +msgstr "" + +#: ../../source/api/python_gotchas.rst:16 +msgid "" +"Not all items listed here are bugs. Some of these are just how GDAL and " +"OGR work and cannot be fixed easily without breaking existing code. If " +"you don't like how something works and think it should be changed, feel " +"free to discuss it on gdal-dev and see what can be done." +msgstr "" + +#: ../../source/api/python_gotchas.rst:21 +msgid "Gotchas that are by design... or per history" +msgstr "" + +#: ../../source/api/python_gotchas.rst:23 +msgid "" +"These are unexpected behaviors that are not considered by the GDAL and " +"OGR teams to be bugs and are unlikely to be changed due to effort " +"required, or whose fixing might affect backward compatibility, etc." +msgstr "" + +#: ../../source/api/python_gotchas.rst:27 +msgid "" +"Python bindings do not raise exceptions unless you explicitly call " +"``UseExceptions()``" +msgstr "" + +#: ../../source/api/python_gotchas.rst:29 +msgid "" +"By default, the GDAL and OGR Python bindings do not raise exceptions when" +" errors occur. Instead they return an error value such as ``None`` and " +"write an error message to ``sys.stdout``. For example, when you try to " +"open a non-existing dataset with GDAL:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:41 +msgid "" +"In Python, it is traditional to report errors by raising exceptions. You " +"can enable this behavior in GDAL and OGR by calling the " +"``UseExceptions()`` function:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:58 +msgid "" +"It is planned that exceptions will be enabled by default in GDAL 4.0. " +"Code that does not want exceptions to be raised in a future version of " +"GDAL should explicitly disable them with ``gdal.DontUseExceptions()``." +msgstr "" + +#: ../../source/api/python_gotchas.rst:62 +msgid "" +"Python crashes or throws an exception if you use an object after deleting" +" a related object" +msgstr "" + +#: ../../source/api/python_gotchas.rst:64 +msgid "Consider this example:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:74 +msgid "" +"In this example, ``band`` has a relationship with ``dataset`` that " +"requires ``dataset`` to remain allocated in order for ``band`` to work. " +"If we delete ``dataset`` and then try to use ``band``, Python will throw " +"a confusing exception:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:88 +msgid "" +"In GDAL 3.7 and earlier, using a band after the dataset has been " +"destroyed will cause a crash instead of an exception." +msgstr "" + +#: ../../source/api/python_gotchas.rst:90 +msgid "" +"This problem can manifest itself in subtle ways. For example, it can " +"occur if you try to instantiate a temporary dataset instance within a " +"single line of code:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:98 +msgid "" +"In this example, the dataset instance was no longer needed after the call" +" to ``GetRasterBand()`` so Python deallocated it *before* calling " +"``Checksum()``." +msgstr "" + +#: ../../source/api/python_gotchas.rst:112 +msgid "" +"This example is the same case as above but it looks different. The " +"dataset object is only available in the ``load_band`` function and will " +"be deleted right after leaving the function." +msgstr "" + +#: ../../source/api/python_gotchas.rst:116 +msgid "" +"The problem is not restricted to GDAL band and dataset objects and " +"happens in other areas where objects have relationships with each other. " +"The issue occurs because deleting an object in Python causes not only the" +" C++ object behind it to be deallocated, but also other objects for which" +" that C++ object maintains ownership (e.g., a Dataset owning a Band, a " +"Feature owning a Geometry.) If the Python object associated with one of " +"these child objects retains a reference to that object, Python will crash" +" when the object is accessed. In common cases such as the Band/Dataset " +"relationship above, the GDAL bindings invalidate references to objects " +"that no longer exist so that an exception is thrown instead of a crash, " +"but the work is not complete." +msgstr "" + +#: ../../source/api/python_gotchas.rst:127 +msgid "" +"Unfortunately there is no complete list of such relationships, so you " +"have to watch for it yourself." +msgstr "" + +#: ../../source/api/python_gotchas.rst:130 +msgid "" +"Python crashes if you add a new field to an OGR layer when features " +"deriving from this layer definition are still active" +msgstr "" + +#: ../../source/api/python_gotchas.rst:132 +msgid "For example:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:142 +msgid "" +"For more information, please see `#3552 " +"<https://trac.osgeo.org/gdal/ticket/3552>`__." +msgstr "" + +#: ../../source/api/python_gotchas.rst:145 +msgid "" +"Layers with attribute filters (``SetAttributeFilter()``) will only return" +" filtered features when using ``GetNextFeature()``" +msgstr "" + +#: ../../source/api/python_gotchas.rst:147 +msgid "" +"If you read the documentation for ``SetAttributeFilter()`` carefully you " +"will see the caveat about ``OGR_L_GetNextFeature()``. This means that if " +"you use ``GetFeature()``, instead of ``GetNextFeature()``, then you can " +"still access and work with features from the layer that are not covered " +"by the filter. ``GetFeatureCount()`` will respect the filter and show the" +" correct number of features filtered. However, working with " +"``GetFeatureCount()`` in a loop can lead to some subtle confusion. " +"Iterating over the Layer object or using ``GetNextFeature()`` should be " +"the default method for accessing features:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:162 +msgid "" +"Certain objects contain a ``Destroy()`` method, but you should never use " +"it" +msgstr "" + +#: ../../source/api/python_gotchas.rst:164 +msgid "" +"You may come across examples that call the ``Destroy()`` method. `This " +"tutorial " +"<https://www.gis.usu.edu/~chrisg/python/2009/lectures/ospy_slides2.pdf>`__" +" even gives specific advice on page 12 about when to call ``Destroy``." +msgstr "" + +#: ../../source/api/python_gotchas.rst:166 +msgid "" +"Calling ``Destroy`` forces the underlying native object to be destroyed." +" This is typically unnecessary because these objects are automatically " +"destroyed during garbage collection when no references to the Python " +"object remain." +msgstr "" + +#: ../../source/api/python_gotchas.rst:170 +msgid "" +"In most situations, it is not necessary to force the object to be " +"destroyed at a specific point in time. However, because the contents of " +"``gdal.Dataset`` and ``ogr.DataSource`` objects are only guaranteed to be" +" written to disk when the backing native object is destroyed, it may be " +"necessary to explicitly destroy these objects. In these cases, a context " +"manager (``with`` block) is often a good solution, e.g.:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:187 +msgid "" +"If this is not possible, for example if the object needs to be destroyed " +"within a function, then the ``Close()`` method may be called." +msgstr "" + +#: ../../source/api/python_gotchas.rst:192 +msgid "" +"Context managers and the ``Close()`` method are available beginning in " +"GDAL 3.8. In earlier versions, ``Destroy()`` can be used for " +"``ogr.DataSource`` objects, or garbage collection may be forced by " +"destroying reference using ``del`` or setting variables to ``None``." +msgstr "" + +#: ../../source/api/python_gotchas.rst:197 +msgid "" +"With some drivers, raster datasets can be intermittently saved without " +"closing using ``FlushCache()``. Similarly, vector datasets can be saved " +"using ``SyncToDisk()``. However, neither of these methods guarantee that" +" the data are written to disk, so the preferred method is to use a " +"context manager or call ``Close()``." +msgstr "" + +#: ../../source/api/python_gotchas.rst:205 +msgid "Exceptions raised in custom error handlers do not get caught" +msgstr "" + +#: ../../source/api/python_gotchas.rst:207 +msgid "" +"The python bindings allow you to specify a python callable as an error " +"handler (`#4993 <https://trac.osgeo.org/gdal/ticket/4993>`__). However, " +"these error handlers appear to be called in a separate thread and any " +"exceptions raised do not propagate back to the main thread (`#5186 " +"<https://trac.osgeo.org/gdal/ticket/5186>`__)." +msgstr "" + +#: ../../source/api/python_gotchas.rst:210 +msgid "" +"So if you want to `catch warnings as well as errors " +"<https://gis.stackexchange.com/questions/43404/how-to-detect-a-gdal-ogr-" +"warning/68042>`__, something like this won't work:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:228 +msgid "But you can do something like this instead:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:283 +msgid "Gotchas that result from bugs or behaviors of other software" +msgstr "" + +#: ../../source/api/python_gotchas.rst:286 +msgid "Python crashes in GDAL functions when you upgrade or downgrade numpy" +msgstr "" + +#: ../../source/api/python_gotchas.rst:288 +msgid "" +"Much of GDAL's Python bindings are implemented in C++. Much of the core " +"of numpy is implemented in C. The C++ part of GDAL's Python bindings " +"interacts with the C part of numpy through numpy's ABI (application " +"binary interface). This requires GDAL's Python bindings to be compiled " +"using numpy header files that define numpy C data structures. Those data " +"structures sometimes change between numpy versions. When this happens, " +"the new version of numpy is not be compatible at the binary level with " +"the old version, and the GDAL Python bindings must be recompiled before " +"they will work with the new version of numpy. And when they are " +"recompiled, they probably won't work with the old version." +msgstr "" + +#: ../../source/api/python_gotchas.rst:292 +msgid "" +"If you obtained a precompiled version of GDAL's Python bindings, such as " +"the Windows packages from `http://gisinternals.com/sdk.php " +"<http://gisinternals.com/sdk.php>`__ be sure you look up what version of " +"numpy was used to compile them, and install that version of numpy on your" +" machine." +msgstr "" + +#: ../../source/api/python_gotchas.rst:295 +msgid "" +"Python bindings cannot be used successfully from ArcGIS in-process " +"geoprocessing tools (ArcGIS 9.3 and later)" +msgstr "" + +#: ../../source/api/python_gotchas.rst:297 +msgid "" +"ArcGIS allows the creation of custom, Python-based geoprocessing tools. " +"Until ArcGIS 10, there was no easy way to read raster data into memory. " +"GDAL provides such a mechanism." +msgstr "" + +#: ../../source/api/python_gotchas.rst:299 +msgid "" +"Starting with ArcGIS 9.3, geoprocessing tools can either run in the " +"ArcGIS process itself (ArcCatalog.exe or ArcMap.exe) or run in a separate" +" python.exe worker process. Unfortunately ArcGIS contains a bug in how it" +" runs in-process tools. Thus, if you use GDAL from an in-process tool, it" +" will run fine the first time but after that it may fail with " +"``TypeError`` exceptions until you restart the ArcGIS process. For " +"example, band.ReadAsArray() fails with:" +msgstr "" + +#: ../../source/api/python_gotchas.rst:301 +msgid "" +"``TypeError: in method 'BandRasterIONumpy', argument 1 of type " +"'GDALRasterBandShadow *``'" +msgstr "" + +#: ../../source/api/python_gotchas.rst:303 +msgid "" +"This is a bug in ArcGIS. Please see `#3672 " +"<https://trac.osgeo.org/gdal/ticket/3672>`__ for complete details and " +"advice on workarounds." +msgstr "" + +#: ../../source/api/python_samples.rst:5 +msgid "Python Sample scripts" +msgstr "" + +#: ../../source/api/python_samples.rst:7 +msgid "" +"The following are sample scripts intended to give an idea how to use the " +"GDAL's Python interface. Please feel free to use them in your " +"applications." +msgstr "" + +#: ../../source/api/python_samples.rst:10 +msgid "" +"From GDAL 3.2, Python utility scripts :ref:`programs` are located inside " +"the `osgeo_utils` module. From GDAL 3.3, Python sample scripts are " +"located inside the `osgeo_utils.samples` sub-module." +msgstr "" + +#: ../../source/api/python_samples.rst:14 +msgid "Python Raster Sample scripts" +msgstr "" + +#: ../../source/api/python_samples.rst:18 +msgid "" +"assemblepoly: Script demonstrates how to assemble polygons from arcs. " +"Demonstrates various aspects of OGR Python API." +msgstr "" + +#: ../../source/api/python_samples.rst:19 +msgid "" +"fft: Script to perform forward and inverse two-dimensional fast Fourier " +"transform." +msgstr "" + +#: ../../source/api/python_samples.rst:20 +msgid "" +"gdal2grd: Script to write out ASCII GRD rasters (used in Golden Software " +"Surfer). from any source supported by GDAL." +msgstr "" + +#: ../../source/api/python_samples.rst:21 +msgid "gdal_vrtmerge: Similar to gdal_merge, but produces a VRT file." +msgstr "" + +#: ../../source/api/python_samples.rst:22 +msgid "" +"gdalcopyproj: Duplicate the geotransform, projection and/or GCPs from one" +" raster dataset to another, which can be useful after performing image " +"manipulations with other software that ignores or discards georeferencing" +" metadata." +msgstr "" + +#: ../../source/api/python_samples.rst:24 +msgid "" +"gdalfilter: Example script for applying kernel based filters to an image" +" using GDAL. Demonstrates use of virtual files as an intermediate " +"representation." +msgstr "" + +#: ../../source/api/python_samples.rst:26 +msgid "" +"get_soundg: Script to copy the SOUNDG layer from an S-57 file to a " +"Shapefile, splitting up features with MULTIPOINT geometries into many " +"POINT features, and appending the point elevations as an attribute." +msgstr "" + +#: ../../source/api/python_samples.rst:29 +msgid "histrep: Module to extract data from many rasters into one output." +msgstr "" + +#: ../../source/api/python_samples.rst:30 +msgid "" +"load2odbc: Load ODBC table to an ODBC datastore. Uses direct SQL since " +"the ODBC driver is read-only for OGR." +msgstr "" + +#: ../../source/api/python_samples.rst:31 +msgid "" +"rel: Script to produce a shaded relief image from the elevation data. " +"(similar functionality in gdaldem now)" +msgstr "" + +#: ../../source/api/python_samples.rst:32 +msgid "" +"tigerpoly: Script demonstrating how to assemble polygons from arcs in " +"TIGER/Line datasource, writing results to a newly created shapefile." +msgstr "" + +#: ../../source/api/python_samples.rst:34 +msgid "" +"tolatlong: Script to read coordinate system and geotransformation matrix " +"from input file and report latitude/longitude coordinates for the " +"specified pixel." +msgstr "" + +#: ../../source/api/python_samples.rst:36 +msgid "" +"val_repl: Script to replace specified values from the input raster file " +"with the new ones. May be useful in cases when you don't like value, used" +" for NoData indication and want replace it with other value. Input file " +"remains unchanged, results stored in other file." +msgstr "" + +#: ../../source/api/python_samples.rst:39 +msgid "" +"vec_tr: Example of applying some algorithm to all the geometries in the " +"file, such as a fixed offset." +msgstr "" + +#: ../../source/api/python_samples.rst:40 +msgid "" +"vec_tr_spat: Example of using Intersect() to filter based on only those " +"features that truly intersect a given rectangle. Easily extended to " +"general polygon!" +msgstr "" + +#: ../../source/api/python_samples.rst:42 +msgid "" +"classify: Demonstrates using numpy for simple range based classification " +"of an image. This is only an example that has stuff hardcoded." +msgstr "" + +#: ../../source/api/python_samples.rst:44 +msgid "" +"gdal_lut: Read a LUT from a text file, and apply it to an image. Sort of " +"a '1 band' version of pct2rgb." +msgstr "" + +#: ../../source/api/python_samples.rst:46 +msgid "" +"magphase: Example script computing magnitude and phase images from a " +"complex image." +msgstr "" + +#: ../../source/api/python_samples.rst:47 +msgid "hsv_merge: Merge greyscale image into RGB image as intensity in HSV space." +msgstr "" + +#: ../../source/api/python_samples.rst:48 +msgid "" +"gdal_ls: Display the list of files in a virtual directory, like /vsicurl " +"or /vsizip" +msgstr "" + +#: ../../source/api/python_samples.rst:49 +msgid "gdal_cp: Copy a virtual file" +msgstr "" + +#: ../../source/api/python_samples.rst:52 +msgid "Python Vector Sample scripts" +msgstr "" + +#: ../../source/api/python_samples.rst:56 +msgid "" +"ogrupdate: Update a target datasource with the features of a source " +"datasource. Contrary to ogr2ogr, this script tries to match features " +"between the datasources, to decide whether to create a new feature, or to" +" update an existing one." +msgstr "" + +#: ../../source/api/python_samples.rst:59 +msgid "ogr_layer_algebra: Application for executing OGR layer algebra operations." +msgstr "" + +#: ../../source/api/python_samples.rst:60 +msgid "" +"ogr_dispatch: Dispatch features into layers according to the value of " +"some fields or the geometry type." +msgstr "" + +#: ../../source/api/python_samples.rst:61 +msgid "" +"wcs_virtds_params: Generates MapServer WCS layer definition from a " +"tileindex with mixed SRS" +msgstr "" + +#: ../../source/api/python_samples.rst:62 +msgid "" +"ogr_build_junction_table: Create junction tables for layers coming from " +"GML datasources that reference other objects in _href fields" +msgstr "" + +#: ../../source/api/python_samples.rst:64 +msgid "gcps2ogr: Outputs GDAL GCPs as OGR points" +msgstr "" + +#: ../../source/api/python_samples.rst:68 +msgid "Python Coordinate Reference System Sample scripts" +msgstr "" + +#: ../../source/api/python_samples.rst:72 +msgid "" +"crs2crs2grid: A script to produce PROJ.4 grid shift files from HTDP " +"program." +msgstr "" + +#: ../../source/api/python_samples.rst:75 +msgid "Python direct ports of c++ programs" +msgstr "" + +#: ../../source/api/python_samples.rst:79 +msgid ":ref:`gdalinfo`: A direct port of apps/gdalinfo.c" +msgstr "" + +#: ../../source/api/python_samples.rst:80 +msgid ":ref:`ogrinfo`: A direct port of apps/ogrinfo.cpp" +msgstr "" + +#: ../../source/api/python_samples.rst:81 +msgid ":ref:`gdallocationinfo`: A direct port of apps/gdallocationinfo.cpp" +msgstr "" + +#: ../../source/api/python_samples.rst:84 +msgid "Python sample scripts that are now programs" +msgstr "" + +#: ../../source/api/python_samples.rst:86 +msgid "" +"Sample scripts might be upgraded to proper gdal utilities (programs) in " +"next versions with added functionality and documentation. The following " +"samples from previous versions are now programs." +msgstr "" + +#: ../../source/api/python_samples.rst:92 +msgid ":ref:`gdal2xyz`: Translates a raster file into xyz format." +msgstr "" + +#: ../../source/api/python_samples.rst:93 +msgid "" +":ref:`gdal_retile`: Script for restructuring data in a tree of regular " +"tiles." +msgstr "" + +#: ../../source/api/python_samples.rst:94 +msgid "val_at_coord: see :ref:`gdallocationinfo`" +msgstr "" + +#: ../../source/api/raster_c_api.rst:10 +msgid "gdal.h: Raster C API" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param pszFuncName" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param papszFunctionArgs" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param nInBands" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param eInDT" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param padfInNoData" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param pnOutBands" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param peOutDT" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param ppadfOutNoData" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param pszVRTPath" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param ppWorkingData" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param pWorkingData" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param nBufXSize" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param nBufYSize" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param pInBuffer" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param nInBufferSize" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param pOutBuffer" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param nOutBufferSize" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param eOutDT" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param nOutBands" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param padfOutNoData" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param dfSrcXOff" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param dfSrcYOff" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param dfSrcXSize" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param dfSrcYSize" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param adfSrcGT" +msgstr "" + +#: ../../source/api/raster_c_api.rst +msgid "Param papszExtra" +msgstr "" + +#: ../../source/api/vector_c_api.rst:10 +msgid "ogr_core.h and ogr_api.h: Vector C API" +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/community.mo b/doc/source/locale/ja/LC_MESSAGES/community.mo new file mode 100644 index 0000000000000000000000000000000000000000..4f8bb2015e6f25f67b7bb8d9792cf6ff765fe7cf GIT binary patch literal 429 zcmYk2%TB{E5Jii`DofTZykJ)*IHiK(KGatz6$z=T2&wGc)J<IyJF*=_R(u7&$G6}V zL>XzMIpb^3_<o(8el~2J*gUs+QNzEuwDpHQgu1s-a?cV2^9?*RrMVOY&8DLOIZIYZ zWgyfk-@v#`HN=u2XA#9PQH&ZZg()?RpcZbm0p9}l5WXhun<l=)*a~6E-gy1wuWsd! zmJmiT9ifMag!AT0^yE7M)dpfkh0dsvilCL`$&RB(TG5=MUUfkC^?<`Pr#y2LnGftm zk(M;I3+(A1K+I@fcTg_~h8cIIN(as&D;3S)UaDLZB#Hy-zSl)RWgmB)a31<c4?Gt; z6DbT6cDbssLkxR2S4Bp-=%Qptm1d@2nk{sWy807arob18+;EW+)LC=m%$Q)xI%RFF Q2pZEh%TUYp+IB?a8=ks;`v3p{ literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/community.po b/doc/source/locale/ja/LC_MESSAGES/community.po new file mode 100644 index 000000000000..15e6d92e8549 --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/community.po @@ -0,0 +1,691 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Yoichi Kayama <yoichi.kayama@gmail.com>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/community/code_of_conduct.rst:5 +#: ../../source/community/index.rst:16 +msgid "行動規範" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:7 +msgid "" +"This code of conduct governs how we behave in any GDAL forum or event and" +" whenever we will be judged by our actions. We expect it to be honored by" +" everyone who participates in the GDAL community formally or informally, " +"or claims any affiliation with the project." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:13 +msgid "Introduction" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:15 +msgid "" +"This code of conduct governs how we behave in any GDAL forum or event and" +" whenever we will be judged by our actions. We expect it to be honored by" +" everyone who participates in the GDAL community formally or informally, " +"or claims any affiliation with the GDAL project." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:20 +msgid "" +"It applies to in-person events (such as conferences and related social " +"events), IRC, public and private mailing lists, the issue tracker, the " +"wiki, blogs, Twitter, and any other forums which the community uses for " +"communication and interactions." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:25 +msgid "" +"This code is not exhaustive or complete. It serves to distill our common " +"understanding of a collaborative, shared environment and goals. We expect" +" it to be followed in spirit as much as in the letter, so that it can " +"enrich all of us and the technical communities in which we participate." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:31 +msgid "Diversity Statement" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:33 +msgid "" +"GDAL welcomes and encourages participation by everyone. We are committed " +"to being a community that everyone feels good about joining, and we will " +"always work to treat everyone well. No matter how you identify yourself " +"or how others perceive you: we welcome you. Specific Guidelines" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:39 +msgid "We strive to:" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:41 +msgid "Be open." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:43 +msgid "" +"We invite anyone to participate in our community. We preferably use " +"public methods of communication for project-related messages, unless " +"discussing something sensitive. This applies to messages for help or " +"project-related support, too; not only is a public support request much " +"more likely to result in an answer to a question, it also makes sure that" +" any inadvertent mistakes made by people answering will be more easily " +"detected and corrected." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:50 +msgid "Be empathetic, welcoming, friendly, and patient." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:52 +msgid "" +"We work together to resolve conflict, assume good intentions, and do our " +"best to act in an empathetic fashion. We may all experience some " +"frustration from time to time, but we do not allow frustration to turn " +"into a personal attack. A community where people feel uncomfortable or " +"threatened is not a productive one. Note that we have a multi-cultural, " +"multi-lingual community and some of us are non-native speakers. We should" +" be respectful when dealing with other community members as well as with " +"people outside our community." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:60 +msgid "Be collaborative." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:62 +msgid "" +"Our work will be used by other people, and in turn we will depend on the " +"work of others. When we make something for the benefit of GDAL, we are " +"willing to explain to others how it works, so that they can build on the " +"work to make it even better. Any decision we make will affect users and " +"colleagues, and we take those consequences seriously when making " +"decisions." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:68 +msgid "Be inquisitive." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:70 +msgid "" +"Nobody knows everything! Asking questions early avoids many problems " +"later, so questions are encouraged, though they may be directed to the " +"appropriate forum. Those who are asked should be responsive and helpful, " +"within the context of our shared goal of improving GDAL." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:75 +msgid "Be careful in the words that we choose." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:77 +msgid "" +"Whether we are participating as professionals or volunteers, we value " +"professionalism in all interactions, and take responsibility for our own " +"speech. Be kind to others. Do not insult or put down other participants." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:81 +msgid "Be concise." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:83 +msgid "" +"Keep in mind that what you write once will be read by hundreds of " +"persons. Writing a short email means people can understand the " +"conversation as efficiently as possible. Short emails should always " +"strive to be empathetic, welcoming, friendly and patient. When a long " +"explanation is necessary, consider adding a summary." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:89 +msgid "" +"Try to bring new ideas to a conversation so that each mail adds something" +" unique to the thread, keeping in mind that the rest of the thread still " +"contains the other messages with arguments that have already been made." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:93 +msgid "" +"Try to stay on topic, especially in discussions that are already fairly " +"large." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:95 +msgid "Step down considerately." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:97 +msgid "" +"Members of every project come and go. When somebody leaves or disengages " +"from the project they should tell people they are leaving and take the " +"proper steps to ensure that others can pick up where they left off. In " +"doing so, they should remain respectful of those who continue to " +"participate in the project and should not misrepresent the project's " +"goals or achievements. Likewise, community members should respect any " +"individual's choice to leave the project." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:106 +msgid "Anti-Harassment" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:108 +msgid "" +"Harassment and other exclusionary behavior are not acceptable. This " +"includes, but is not limited to:" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:111 +msgid "" +"Personal insults or discriminatory jokes and language, especially those " +"using racist or sexist terms." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:112 +msgid "Offensive comments, excessive or unnecessary profanity." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:113 +msgid "Intimidation, violent threats or demands." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:114 +msgid "Sustained disruption of sessions or events." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:115 +msgid "Stalking, harassing photography or recording." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:116 +msgid "Unwelcome physical contact or sexual attention." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:117 +msgid "" +"Repeated harassment of others. In general, if someone asks you to stop, " +"then stop." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:118 +msgid "" +"Posting (or threatening to post) other people's personally identifying " +"information (\"doxing\")." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:119 +msgid "" +"Sharing private content, such as emails sent privately or non-publicly, " +"or unlogged forums such as IRC channel history." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:120 +msgid "Advocating for, or encouraging, any of the above behavior." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:123 +msgid "Reporting Guidelines" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:125 +msgid "" +"If you believe someone is breaking this code of conduct, you may reply to" +" them, and point to this code of conduct. Such messages may be in public " +"or in private, whatever is most appropriate. Assume good faith; it is " +"more likely that participants are unaware of their bad behavior than that" +" they intentionally try to degrade the quality of the discussion. Should " +"there be difficulties in dealing with the situation, you may report your " +"concerns to event staff, a forum leader or the GDAL Board. Serious or " +"persistent offenders may be expelled from the event or forum by event " +"organizers or forum leaders." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:134 +msgid "" +"To privately email the code of conduct committee leadership use " +"coc@osgeo.org." +msgstr "" + +#: ../../source/community/code_of_conduct.rst:137 +msgid "Credits" +msgstr "" + +#: ../../source/community/code_of_conduct.rst:139 +msgid "" +"GDAL re-uses the `OSGeo Code of Conduct <https://www.osgeo.org/resources" +"/osgeo-code-of-conduct/>`__" +msgstr "" + +#: ../../source/community/index.rst:5 +msgid "Community" +msgstr "" + +#: ../../source/community/index.rst:7 +msgid "" +"GDAL's community interacts through `Mailing List`_, `GitHub`_, and " +"`Chat`_. Please feel welcome to ask questions and participate in all of " +"the venues. The `Mailing List`_ communication channel is for general " +"questions, development discussion, and feedback. The `GitHub`_ " +"communication channel is for development activities, bug reports, and " +"testing. The `Chat`_ room is for real-time chat activities such as " +"meetings and interactive debugging sessions." +msgstr "" + +#: ../../source/community/index.rst:20 +msgid "" +"GDAL uses a :ref:`code_of_conduct` which governs how we behave in any " +"GDAL forum or event and whenever we will be judged by our actions. We " +"expect it to be honored by everyone who participates in the GDAL " +"community formally or informally, or claims any affiliation with the " +"project." +msgstr "" + +#: ../../source/community/index.rst:32 +msgid "Mailing List" +msgstr "" + +#: ../../source/community/index.rst:34 +msgid "" +"Developers and users of GDAL participate on the GDAL mailing list. It is " +"OK to ask questions about how to use GDAL, how to integrate GDAL into " +"your own software, and report issues that you might have." +msgstr "" + +#: ../../source/community/index.rst:38 +msgid "http://lists.osgeo.org/mailman/listinfo/gdal-dev" +msgstr "" + +#: ../../source/community/index.rst:42 +msgid "GitHub" +msgstr "" + +#: ../../source/community/index.rst:44 +msgid "" +"Visit http://github.com/OSGeo/GDAL to file issues you might be having " +"with the software. GitHub is also where you can obtain a current " +"development version of the software in the `git`_ revision control " +"system. The GDAL project is eager to take contributions in all forms, and" +" we welcome those who are willing to roll up their sleeves and start " +"filing tickets, pushing code, generating builds, and answering questions." +msgstr "" + +#: ../../source/community/index.rst:54 +msgid "Chat" +msgstr "" + +#: ../../source/community/index.rst:56 +msgid "" +"You can find some GDAL developers in the IRC channel #gdal on " +"`Libera.Chat`_. This mechanism is usually reserved for active meetings " +"and other outreach with the community. The `Mailing List`_ and `GitHub`_ " +"avenues are going to be more productive communication channels in most " +"situations." +msgstr "" + +#: ../../source/community/index.rst:67 +msgid "Social media" +msgstr "" + +#: ../../source/community/index.rst:69 +msgid "" +"You can follow GDAL official news on Mastodon: " +"https://mastodon.social/@gdal / @gdal@mastodon.social" +msgstr "" + +#: ../../source/community/index.rst:73 +msgid "Conference" +msgstr "" + +#: ../../source/community/index.rst:-1 +msgid "FOSS4G 2023" +msgstr "" + +#: ../../source/community/index.rst:79 +msgid "" +"`FOSS4G 2023 <https://2023.foss4g.org/>`_ is the leading annual " +"conference for free and open source geospatial software. It will include " +"presentations related to GDAL/OGR, and some of the GDAL/OGR development " +"community will be attending. It is the event for those interested in " +"GDAL/OGR, other FOSS geospatial technologies and the community around " +"them. The conference will be held at Prizren, Kosovo from June 26th to " +"July 2nd 2023." +msgstr "" + +#: ../../source/community/index.rst:82 +msgid "Governance and Community Participation" +msgstr "" + +#: ../../source/community/index.rst:85 +msgid "OSGeo Project Membership" +msgstr "" + +#: ../../source/community/index.rst:87 +msgid "" +"Originally, GDAL has been lead by Frank Warmerdam, the original author of" +" much of GDAL/OGR, though with contributions and input from a variety of " +"people. As of February 2006 GDAL/OGR became a founding project of the " +"`Open Source Geospatial Foundation (OSGeo) <https://www.osgeo.org/>`_ and" +" began a transition to a more community oriented governance model - in " +"keeping with OSGeo expectations." +msgstr "" + +#: ../../source/community/index.rst:94 +msgid "" +"Membership as an OSGeo project provides assurances that a variety of best" +" practices are being employed by the GDAL/OGR project, and that users and" +" contributors can be assured of responsible project operation and " +"continuity of the project. In particular:" +msgstr "" + +#: ../../source/community/index.rst:98 +msgid "" +"A consensus oriented Project Management Committee will be in charge of " +"the project." +msgstr "" + +#: ../../source/community/index.rst:99 +msgid "" +"Project source code and contributions will be vetted to ensure code is " +"properly made available, protecting contributors and users of GDAL/OGR." +msgstr "" + +#: ../../source/community/index.rst:101 +msgid "" +"Part of the systems infrastructure used by the project is provided by the" +" foundation, with responsible backup and redundancy to minimize " +"disruptions." +msgstr "" + +#: ../../source/community/index.rst:107 +msgid "Project Steering Committee" +msgstr "" + +#: ../../source/community/index.rst:109 +msgid "" +"As of April 2006 (following the GDAL/OGR 1.3.2 release) the project has " +"been placed in the hands of a Project Steering Committee. This project " +"steering committee operates under the rules of :ref:`rfc-1`, and is " +"overall responsible for decisions related to the GDAL/OGR project. The " +"current members are (@github username):" +msgstr "" + +#: ../../source/community/index.rst:114 +msgid "Frank Warmerdam (@warmerdam)" +msgstr "" + +#: ../../source/community/index.rst:115 +msgid "Daniel Morissette (@dmorissette)" +msgstr "" + +#: ../../source/community/index.rst:116 +msgid "Howard Butler (@hobu)" +msgstr "" + +#: ../../source/community/index.rst:117 +msgid "Tamas Szekeres (@szekerest)" +msgstr "" + +#: ../../source/community/index.rst:118 +msgid "Even Rouault (chair) (@rouault)" +msgstr "" + +#: ../../source/community/index.rst:119 +msgid "Jukka Rahkonen (@jratike80)" +msgstr "" + +#: ../../source/community/index.rst:120 +msgid "Kurt Schwehr (@schwehr)" +msgstr "" + +#: ../../source/community/index.rst:121 +msgid "Norman Barker (@normanb)" +msgstr "" + +#: ../../source/community/index.rst:122 +msgid "Sean Gillies (@sgillies)" +msgstr "" + +#: ../../source/community/index.rst:123 +msgid "Javier Jimenez Shaw (@jjimenezshaw)" +msgstr "" + +#: ../../source/community/index.rst:125 +msgid "Past members:" +msgstr "" + +#: ../../source/community/index.rst:127 +msgid "Andrey Kiselev (@strezen) (retired in 2019)" +msgstr "" + +#: ../../source/community/index.rst:128 +msgid "Mateusz Łoskot (@mloskot) (retired in 2023)" +msgstr "" + +#: ../../source/community/index.rst:130 +msgid "" +"Note that discussion of proposals to the PSC take place on gdal-dev, and " +"input from all subscribers is welcome. A :ref:`list of past RFC " +"<rfclist>` is available for review." +msgstr "" + +#: ../../source/community/index.rst:135 +#: ../../source/community/service_providers.rst:5 +msgid "GDAL Service Providers" +msgstr "" + +#: ../../source/community/index.rst:139 +msgid "" +"GDAL is developed and supported by a rich ecosystem of businesses and " +"individuals around the world. You can consult a list of " +":ref:`service_providers` who can assist you in getting the best out of " +"your GDAL investment." +msgstr "" + +#: ../../source/community/service_providers.rst:7 +msgid "" +"GDAL is developed and supported by a rich ecosystem of businesses and " +"individuals around the world." +msgstr "" + +#: ../../source/community/service_providers.rst:10 +msgid "" +"In this page we provide a list of service providers who can assist you in" +" getting the best out of your GDAL investment. Their services can range " +"from training and technical support to help you get started, all the way " +"to specialized development and support services to advance the software " +"and support your organization's mission-critical applications." +msgstr "" + +#: ../../source/community/service_providers.rst:20 +msgid "" +"This list is non-exhaustive, and there are quite likely other service " +"providers in your region of the world who are not listed here. If you " +"think your organization should be listed here, please submit a pull " +"request to add it to this page." +msgstr "" + +#: ../../source/community/service_providers.rst:26 +msgid "" +"We take responsibility for the accuracy, reliability or completeness of " +"the provided information for Core Contributors only." +msgstr "" + +#: ../../source/community/service_providers.rst:32 +msgid "Service Providers order is randomized on page load." +msgstr "" + +#: ../../source/community/service_providers.rst:35 +msgid "Core Contributors" +msgstr "" + +#: ../../source/community/service_providers.rst:37 +msgid "" +"Core Contributor organizations have GDAL Committers and/or PSC members as" +" part of their team and as such they are the closest to the core " +"development of the software and are usually the best to go to for " +"support." +msgstr "" + +#: ../../source/community/service_providers.rst:41 +msgid "" +"They are close enough to the architecture to know what is possible, and " +"to ensure that any improvement to be made to GDAL gets done in the right " +"way and will be included in future releases of the software." +msgstr "" + +#: ../../source/community/service_providers.rst:45 +msgid "" +"They wrote the software that you use, so you can trust them to help you " +"get the most out of it." +msgstr "" + +#: ../../source/community/service_providers.rst:50 +msgid "|logo_spatialys|" +msgstr "" + +#: ../../source/community/service_providers.rst +msgid "logo_spatialys" +msgstr "" + +#: ../../source/community/service_providers.rst:54 +msgid "" +"`Spatialys`_ (France) is a company founded by Even Rouault that is " +"dedicated to providing to its clients the best of its expertise around " +"Open Source geospatial software - such as GDAL/OGR, PROJ, MapServer, and " +"QGIS - and Open standards." +msgstr "" + +#: ../../source/community/service_providers.rst:60 +msgid "|logo_hobu|" +msgstr "" + +#: ../../source/community/service_providers.rst +msgid "logo_hobu" +msgstr "" + +#: ../../source/community/service_providers.rst:64 +msgid "" +"`Hobu, Inc.`_ (United States) is a `sam.gov " +"<https://sam.gov>`__-registered company founded by Howard Butler with " +"more than twenty years experience supporting the creation, enhancement, " +"and management of geospatial open source geospatial software such as " +"`PDAL <https://pdal.io>`__, GDAL/OGR, PROJ, and open standards such as " +"`GeoJSON <https://datatracker.ietf.org/doc/html/rfc7946>`__, `PROJJSON " +"<https://proj.org/en/latest/specifications/projjson.html>`__, and `Cloud " +"Optimized Point Cloud <https://copc.io/>`__." +msgstr "" + +#: ../../source/community/service_providers.rst:74 +msgid "Contributors" +msgstr "" + +#: ../../source/community/service_providers.rst:76 +msgid "" +"The Contributors listed here usually have power users and experienced " +"integrators as part of their team who are recognized in the GDAL " +"community for their contributions to various aspects of the software over" +" the years and are very well positioned to assist you with GDAL." +msgstr "" + +#: ../../source/community/service_providers.rst:83 +msgid "None listed yet." +msgstr "" + +#: ../../source/community/service_providers.rst:87 +msgid "Other Service Providers" +msgstr "" + +#: ../../source/community/service_providers.rst:89 +msgid "" +"The service providers in this category offer services around GDAL and " +"related Open Source technologies." +msgstr "" + +#: ../../source/community/service_providers.rst:94 +msgid "|logo_faunalia|" +msgstr "" + +#: ../../source/community/service_providers.rst +msgid "logo_faunalia" +msgstr "" + +#: ../../source/community/service_providers.rst:98 +msgid "" +"`Faunalia`_ (Italy) is a company that operates since more than 15 years " +"in the field of Geographic Information Systems (GIS) based on free and " +"open source software (chiefly QGIS, PostGIS, and more). Our main " +"customers are public administrations, private companies, associations. " +"Faunalia has its main branch in Italy, and operates worldwide. Faunalia " +"provides training services on GDAL." +msgstr "" + +#: ../../source/community/service_providers.rst:102 +msgid "|logo_kartoza|" +msgstr "" + +#: ../../source/community/service_providers.rst +msgid "logo_kartoza" +msgstr "" + +#: ../../source/community/service_providers.rst:106 +msgid "" +"`Kartoza`_ (South Africa) is a South Africa-based Free and Open Source " +"GIS (FOSSGIS) service provider. We use GIS software to solve complex " +"location-related problems for individuals, businesses and governments " +"around the world. Kartoza provides training services on GDAL." +msgstr "" + +#: ../../source/community/service_providers.rst:110 +msgid "|logo_mundialis|" +msgstr "" + +#: ../../source/community/service_providers.rst +msgid "logo_mundialis" +msgstr "" + +#: ../../source/community/service_providers.rst:114 +msgid "" +"`mundialis`_ (Germany) is specialized in the processing of massive " +"geospatial and remote sensing data. Our services centered on the Open " +"Source geospatial systems GRASS GIS, actinia and QGIS are incorporated " +"into our process chains, projects and tailored solutions. We analyse " +"satellite, aerial and drone imagery for land degradation and landuse " +"change. We offer support and training for GRASS GIS and GDAL." +msgstr "" + +#: ../../source/community/service_providers.rst:155 +msgid "" +"Search for GDAL service providers with the `OSGeo Service Providers " +"<https://www.osgeo.org/service-providers/>`__" +msgstr "" + +#: ../../source/community/service_providers.rst:158 +msgid "How to Add a Company" +msgstr "" + +#: ../../source/community/service_providers.rst:160 +msgid "" +"The steps to add a company to the service providers list are outlined in " +"the :ref:`rfc-79` document." +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/contributing.mo b/doc/source/locale/ja/LC_MESSAGES/contributing.mo new file mode 100644 index 0000000000000000000000000000000000000000..87a77f9ab65b917b194fa49f2a88d68f97ff7ffe GIT binary patch literal 622 zcmZuu&ubGw6dr$^_Si%5;NjiNq?;IQoiu6FCbq$>2_Xpe<YY71Ox@iHGqbHZ$)*QE zdyVK-#EYP!APC~0;$<QB&+u&&tKh&l?|n1hy!Yn4?<-g51lJYBbwoKQf2}t9D+mv< zfp~y;e2I`3Xjc)}E)!BiyN;F|s1vXXd=*<Q2Z<Hiq(2r~07n>cEHn?{gij5Ol!n9z zZT{8gY`;-&Gt$-SNcfhvhV&lFq>9<{2ArOlC~c`{0y(6+NnmJSF>tz_KHbxTTa?lU zw}L^*EtRReLER#_H(2@RntRK2QAm5@Smq&r>kgas9`!o3QHO&L^IB{7J9nE-n;T2} zn#U&OR%r%@O8R37cleY?9JZ!QT6nmmJ3+){SnyR;!-sK@@Bj-q;(rM33m)Ysu+?tw zgtDM?P;<Irf-Rx9m5vO9c(SCXTCBh?x9V0LujMr_dQdF5&K~wx#8}*Pf=R4+WY;Gl zmvIIBG1o@eYGOxp^Fo(@Vk9(e#=aWLIAE|jkk;83F;2t^Y~z%{E+2>xN`+z>Q;_qI zuYR1p%hH$G?AhY^m&K=fmcHL6+3B0?^lLWzobTybKC3K!`(N?->nDr(hb*0Cv!_}5 I4MQ>V6WmhMe*gdg literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/contributing.po b/doc/source/locale/ja/LC_MESSAGES/contributing.po new file mode 100644 index 000000000000..d5c59d6f939c --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/contributing.po @@ -0,0 +1,45 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Yoichi Kayama <yoichi.kayama@gmail.com>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/contributing/index.rst:5 +msgid "How to contribute?" +msgstr "貢献する方法は?" + +#: ../../source/contributing/index.rst:7 +msgid "There are several ways for users to contribute to GDAL:" +msgstr "ユーザーがGDALに貢献する方法は複数あります:" + +#: ../../source/contributing/index.rst:9 +msgid ":ref:`contributing code<development>` (bug fixes or enhancements)" +msgstr "" + +#: ../../source/contributing/index.rst:10 +msgid "filing high-quality `bug reports <https://github.com/osgeo/gdal/issues>`_" +msgstr "" + +#: ../../source/contributing/index.rst:11 +msgid "improving :ref:`documentation<dev_documentation>`" +msgstr "" + +#: ../../source/contributing/index.rst:12 +msgid ":ref:`financial sponsorship<sponsors>`" +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/development.mo b/doc/source/locale/ja/LC_MESSAGES/development.mo new file mode 100644 index 0000000000000000000000000000000000000000..007ed966ce3d254c45c38ea69a26c3be1c3fac0a GIT binary patch literal 507 zcmYjO!EO^V5Zxk9d+ZH~!$=&<EKZ1^I7!u{2_<TlL{U^!Ztlj}y6oDK?M38-nw+X0 zt9}I%cO>|Z-g?;|VK%KOBRzTE=#6Lme7F7dCZKpicusg(k^iDa`7=VB@O>)?KGFGt za7%g6EmSsBI)%etX9#m^a&V@wi44ZpoXf=HV1~!iI%PD!7ljkKFxF%2QZ>VFkvg0j z4&it-#RDsaCn@%XmmKP>-az&iSq<20-gvXa-Z4f(oXD@Ly7EDH((g<#9$~KoA4WVL z?0g=5?1w|)JWj39E)(8Z4ktz>X9|wQQse?!%MFdbZ0LTP3zbEQ$@i#Hr-evqfphVX z;8cpdsz7Tv+|N{GY`PbYv%-oD-y54d4tlYnu3c-wecEQtFdoGHM-OTd3lEI;QqywF z1r71?n}4;)gwjn&&V+T+w+lbV-A7&Zh`F@b*NLg@=CFIJe0V6ewB!`oxa80kr!s?j mRBO<PVDlm6#m{o}r(FLoSHH@Ot8#T&Ro2(#`bW9G4E_RCFP{zo literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/development.po b/doc/source/locale/ja/LC_MESSAGES/development.po new file mode 100644 index 000000000000..08e9e743162e --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/development.po @@ -0,0 +1,31662 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Yoichi Kayama <yoichi.kayama@gmail.com>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/development/building_from_source.rst:5 +msgid "Building GDAL from source" +msgstr "GDAL のソースからのビルド" + +#: ../../source/development/building_from_source.rst:10 +#: ../../source/development/dev_environment.rst:8 +msgid "Build requirements" +msgstr "" + +#: ../../source/development/building_from_source.rst:12 +msgid "The minimum requirements to build GDAL are:" +msgstr "" + +#: ../../source/development/building_from_source.rst:14 +msgid "" +"CMake >= 3.16, and an associated build system (make, ninja, Visual " +"Studio, etc.)" +msgstr "" + +#: ../../source/development/building_from_source.rst:15 +msgid "C99 compiler" +msgstr "" + +#: ../../source/development/building_from_source.rst:16 +msgid "C++17 compiler since GDAL 3.9 (C++11 in previous versions)" +msgstr "" + +#: ../../source/development/building_from_source.rst:17 +msgid "PROJ >= 6.3.1" +msgstr "" + +#: ../../source/development/building_from_source.rst:19 +msgid "Additional requirements to run the GDAL test suite are:" +msgstr "" + +#: ../../source/development/building_from_source.rst:21 +msgid "SWIG >= 4, for building bindings to other programming languages" +msgstr "" + +#: ../../source/development/building_from_source.rst:22 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:25 +msgid "Python >= 3.8" +msgstr "" + +#: ../../source/development/building_from_source.rst:23 +msgid "Python packages listed in `autotest/requirements.txt`" +msgstr "" + +#: ../../source/development/building_from_source.rst:25 +msgid "" +"A number of optional libraries are also strongly recommended for most " +"builds: SQLite3, expat, libcurl, zlib, libtiff, libgeotiff, libpng, " +"libjpeg, etc. Consult :ref:`raster_drivers` and :ref:`vector_drivers` " +"pages for information on dependencies of optional drivers." +msgstr "" + +#: ../../source/development/building_from_source.rst:31 +msgid "CMake (GDAL versions >= 3.5.0)" +msgstr "" + +#: ../../source/development/building_from_source.rst:33 +msgid "" +"Since version 3.5.0, GDAL can be built using the CMake build system. With" +" the CMake build system you can compile and install GDAL on more or less " +"any platform. After unpacking the source distribution archive (or cloning" +" the repository) step into the source tree:" +msgstr "" + +#: ../../source/development/building_from_source.rst:42 +msgid "Create a build directory and step into it:" +msgstr "" + +#: ../../source/development/building_from_source.rst:49 +msgid "" +"From the build directory you can now configure CMake, build and install " +"the binaries:" +msgstr "" + +#: ../../source/development/building_from_source.rst:59 +msgid "" +"For a minimal build, add these options to the initial ``cmake`` command: " +"``-DGDAL_BUILD_OPTIONAL_DRIVERS=OFF -DOGR_BUILD_OPTIONAL_DRIVERS=OFF``. " +"To enable specific drivers, add ``-DGDAL_ENABLE_DRIVER_<driver_name>=ON``" +" or ``-DOGR_ENABLE_DRIVER_<driver_name>=ON``. See :ref:`selection-of-" +"drivers` for more details." +msgstr "" + +#: ../../source/development/building_from_source.rst:65 +msgid "" +"The ``--prefix /installation/prefix`` option of CMake (>= 3.14) is " +"supported since GDAL 3.7.0, but note that contrary to setting the " +"CMAKE_INSTALL_PREFIX at configuration time, it will not result in the " +"GDAL_DATA path to be hardcoded into the libgdal binary, and is thus not " +"recommended. It is also not supported on Windows multi-configuration " +"generator (such as VisualStudio)." +msgstr "" + +#: ../../source/development/building_from_source.rst:72 +msgid "" +"If a dependency is installed in a custom location, specify the paths to " +"the include directory and the library:" +msgstr "" + +#: ../../source/development/building_from_source.rst:79 +msgid "Alternatively, a custom prefix can be specified:" +msgstr "" + +#: ../../source/development/building_from_source.rst:85 +msgid "" +"It is strongly recommended (and sometimes compulsory) to specify paths on" +" Windows using forward slashes as well, e.g.: ``c:/path/to/include``." +msgstr "" + +#: ../../source/development/building_from_source.rst:88 +msgid "" +"You can unset existing cached variables, by using the -U switch of cmake," +" for example with wildcards:" +msgstr "" + +#: ../../source/development/building_from_source.rst:94 +msgid "" +"You can assemble dependency settings in a file ``ConfigUser.cmake`` and " +"use it with the -C option. The file contains set() commands that use the " +"CACHE option. You can set for example a different name for the shared " +"lib, *e.g.* ``set (GDAL_LIB_OUTPUT_NAME gdal_x64 CACHE STRING \"\" " +"FORCE)``:" +msgstr "" + +#: ../../source/development/building_from_source.rst:104 +msgid "" +"When iterating to configure GDAL to add/modify/remove dependencies, some " +"cache variables can remain in CMakeCache.txt from previous runs, and " +"conflict with new settings. If strange errors appear during cmake run, " +"you may try removing CMakeCache.txt to start from a clean state." +msgstr "" + +#: ../../source/development/building_from_source.rst:109 +msgid "" +"Refer to :ref:`using_gdal_in_cmake` for how to use GDAL in a CMake " +"project." +msgstr "" + +#: ../../source/development/building_from_source.rst:112 +msgid "Building on Windows" +msgstr "" + +#: ../../source/development/building_from_source.rst:114 +msgid "On Windows, one may need to specify generator:" +msgstr "" + +#: ../../source/development/building_from_source.rst:122 +msgid "Building on MacOS" +msgstr "" + +#: ../../source/development/building_from_source.rst:124 +msgid "" +"On MacOS, there are a couple of libraries that do not function properly " +"when the GDAL build requirements are installed using Homebrew." +msgstr "" + +#: ../../source/development/building_from_source.rst:126 +msgid "" +"The `Apache Arrow <https://arrow.apache.org/docs/index.html>`_ library " +"included in the current distribution of Homebrew is broken, and causes a " +"detection issue. In order to build GDAL successfully, configure CMake to " +"not find the Arrow package:" +msgstr "" + +#: ../../source/development/building_from_source.rst:133 +msgid "" +"Similarly, recent versions of Homebrew no longer bundle `Boost " +"<https://www.boost.org/>`_ with libkml, causing a failure to find Boost " +"headers. You should either install Boost manually or disable libkml when " +"building on MacOS:" +msgstr "" + +#: ../../source/development/building_from_source.rst:141 +msgid "CMake general configure options" +msgstr "" + +#: ../../source/development/building_from_source.rst:143 +msgid "" +"Options to configure a CMake are provided using ``-D<var>=<value>``. All " +"cached entries can be viewed using ``cmake -LAH`` from a build directory." +msgstr "" + +#: ../../source/development/building_from_source.rst:148 +msgid "Build applications. Default is ON." +msgstr "" + +#: ../../source/development/building_from_source.rst:152 +msgid "" +"Build GDAL library shared. Default is ON. See also the CMake " +"documentation for `BUILD_SHARED_LIBS " +"<https://cmake.org/cmake/help/v3.10/variable/BUILD_SHARED_LIBS.html>`_." +msgstr "" + +#: ../../source/development/building_from_source.rst:158 +msgid "" +"Choose the type of build, options are: None (default), Debug, Release, " +"RelWithDebInfo, or MinSizeRel. See also the CMake documentation for " +"`CMAKE_BUILD_TYPE " +"<https://cmake.org/cmake/help/v3.10/variable/CMAKE_BUILD_TYPE.html>`_." +msgstr "" + +#: ../../source/development/building_from_source.rst:164 +msgid "" +"A default build is not optimized without specifying " +"``-DCMAKE_BUILD_TYPE=Release`` (or similar) during configuration, or by " +"specifying ``--config Release`` with CMake multi-configuration build " +"tools (see example below)." +msgstr "" + +#: ../../source/development/building_from_source.rst:171 +msgid "C compiler. Ignored for some generators, such as Visual Studio." +msgstr "" + +#: ../../source/development/building_from_source.rst:175 +msgid "" +"Flags used by the C compiler during all build types. This is initialized " +"by the :envvar:`CFLAGS` environment variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:180 +msgid "C++ compiler. Ignored for some generators, such as Visual Studio." +msgstr "" + +#: ../../source/development/building_from_source.rst:184 +msgid "" +"Flags used by the C++ compiler during all build types. This is " +"initialized by the :envvar:`CXXFLAGS` environment variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:189 +msgid "Where to install the software. Default for Unix-like is ``/usr/local/``." +msgstr "" + +#: ../../source/development/building_from_source.rst:194 +msgid "" +"List of directories specifying installation prefixes to be searched when " +"external dependencies are looked for." +msgstr "" + +#: ../../source/development/building_from_source.rst:197 +msgid "" +"Starting with CMake 3.12, it is also possible to use a " +"``<Packagename>_ROOT`` variable to define the prefix for a particular " +"package. See " +"https://cmake.org/cmake/help/latest/release/3.12.html?highlight=root#commands" +msgstr "" + +#: ../../source/development/building_from_source.rst:205 +msgid "" +"Default is OFF. This can be set to ON to build GDAL using the " +"https://cmake.org/cmake/help/latest/variable/CMAKE_UNITY_BUILD.html " +"feature. This helps speeding GDAL build times. This feature is still " +"considered experimental for now, and could hide subtle bugs (we are not " +"aware of any at writing time though). We don't recommend it for mission " +"critical builds." +msgstr "" + +#: ../../source/development/building_from_source.rst:214 +msgid "" +"Build library using the compiler's `interprocedural optimization " +"<https://en.wikipedia.org/wiki/Interprocedural_optimization>`_ (IPO), if " +"available, default OFF." +msgstr "" + +#: ../../source/development/building_from_source.rst:220 +msgid "" +"Set to ON so that the rpath of installed binaries is written as a " +"relative path to the library. This option overrides the " +"`CMAKE_INSTALL_RPATH " +"<https://cmake.org/cmake/help/latest/variable/CMAKE_INSTALL_RPATH.html>`__" +" variable, and assumes that the `CMAKE_SKIP_INSTALL_RPATH " +"<https://cmake.org/cmake/help/latest/variable/CMAKE_SKIP_INSTALL_RPATH.html>`__" +" variable is not set." +msgstr "" + +#: ../../source/development/building_from_source.rst:228 +msgid "CMake package dependent options" +msgstr "" + +#: ../../source/development/building_from_source.rst:232 +msgid "" +"Generally speaking, packages (external dependencies) will be " +"automatically found if they are in default locations used by CMake. This " +"can be also tuned for example with the ``CMAKE_PREFIX_PATH`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:236 +msgid "" +"Starting with CMake 3.12, it is also possible to use a " +"``<Packagename>_ROOT`` variable to define the prefix for a particular " +"package. See " +"https://cmake.org/cmake/help/latest/release/3.12.html?highlight=root#commands" +" Note that the case of the package name matters for the _ROOT, " +"_INCLUDE_DIR and _LIBRARY variables." +msgstr "" + +#: ../../source/development/building_from_source.rst:242 +msgid "" +"Most dependencies that would be found can also be disabled by setting the" +" following option:" +msgstr "" + +#: ../../source/development/building_from_source.rst:247 +msgid "Control whether a found dependency can be used for the GDAL build." +msgstr "" + +#: ../../source/development/building_from_source.rst:249 +msgid "" +"It is also possible to ask GDAL to disable the use of any external " +"dependency (besides the required one, PROJ) by default by setting the " +"following option to OFF. Individual libraries shall then be enabled " +"explicitly with GDAL_USE_<Packagename_in_upper_case>:BOOL=ON." +msgstr "" + +#: ../../source/development/building_from_source.rst:256 +msgid "" +"Defaults to ON. When set to OFF, all external dependencies (but mandatory" +" ones) will be disabled, unless individually enabled with " +"GDAL_USE_<Packagename_in_upper_case>:BOOL=ON. This option should be set " +"before CMakeCache.txt is created. If it is set to OFF after " +"CMakeCache.txt is created, then cmake should be reinvoked with " +"\"-UGDAL_USE_*\" to cancel the activation of previously detected " +"libraries." +msgstr "" + +#: ../../source/development/building_from_source.rst:263 +msgid "" +"Some of the GDAL dependencies (GEOTIFF, GIF, JPEG, JSONC, LERC, OPENCAD, " +"PNG, QHULL, TIFF, ZLIB) have a copy of their source code inside the GDAL " +"source code tree. It is possible to enable this internal copy by setting " +"the GDAL_USE_<Packagename_in_upper_case>_INTERNAL:BOOL=ON variable. When " +"set, this has precedence over the external library that may be detected. " +"The behavior can also be globally controlled with the following variable:" +msgstr "" + +#: ../../source/development/building_from_source.rst:271 +msgid "" +"Control how internal libraries should be used. If set to ON, they will " +"always be used. If set to OFF, they will never be used (unless " +"individually enabled with " +"GDAL_USE_<Packagename_in_upper_case>_INTERNAL:BOOL=ON) If set to " +"WHEN_NO_EXTERNAL (default value), they will be used only if no " +"corresponding external library is found and enabled. This option should " +"be set before CMakeCache.txt is created." +msgstr "" + +#: ../../source/development/building_from_source.rst:282 +msgid "" +"Using together GDAL_USE_EXTERNAL_LIBS=OFF and GDAL_USE_INTERNAL_LIBS=OFF " +"will result in a CMake configuration failure, because the following " +"libraries (either as external dependencies or using the internal copy) " +"are at least required: ZLIB, TIFF, GEOTIFF and JSONC. Enabling them as " +"external or internal libraries is thus required." +msgstr "" + +#: ../../source/development/building_from_source.rst:290 +msgid "Archive" +msgstr "" + +#: ../../source/development/building_from_source.rst:292 +msgid "" +"`libarchive <https://www.libarchive.org/>`_ is a library that supports a " +"variety of archive and compression formats. It might be used since GDAL " +"3.7 to enable the :ref:`/vsi7z/ <vsi7z>` virtual file system." +msgstr "" + +#: ../../source/development/building_from_source.rst:298 +msgid "Path to an include directory with the ``archive.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:302 +#: ../../source/development/building_from_source.rst:363 +#: ../../source/development/building_from_source.rst:405 +#: ../../source/development/building_from_source.rst:559 +#: ../../source/development/building_from_source.rst:614 +#: ../../source/development/building_from_source.rst:707 +#: ../../source/development/building_from_source.rst:730 +#: ../../source/development/building_from_source.rst:749 +#: ../../source/development/building_from_source.rst:862 +#: ../../source/development/building_from_source.rst:981 +#: ../../source/development/building_from_source.rst:1006 +#: ../../source/development/building_from_source.rst:1055 +#: ../../source/development/building_from_source.rst:1076 +#: ../../source/development/building_from_source.rst:1100 +#: ../../source/development/building_from_source.rst:1153 +#: ../../source/development/building_from_source.rst:1198 +#: ../../source/development/building_from_source.rst:1387 +#: ../../source/development/building_from_source.rst:1426 +#: ../../source/development/building_from_source.rst:1445 +#: ../../source/development/building_from_source.rst:1464 +#: ../../source/development/building_from_source.rst:1495 +#: ../../source/development/building_from_source.rst:1543 +#: ../../source/development/building_from_source.rst:1638 +#: ../../source/development/building_from_source.rst:1689 +#: ../../source/development/building_from_source.rst:1785 +#: ../../source/development/building_from_source.rst:1817 +#: ../../source/development/building_from_source.rst:1966 +#: ../../source/development/building_from_source.rst:1987 +#: ../../source/development/building_from_source.rst:2038 +msgid "Path to a shared or static library file." +msgstr "" + +#: ../../source/development/building_from_source.rst:306 +msgid "" +"Control whether to use libarchive. Defaults to ON when libarchive is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:310 +msgid "Armadillo" +msgstr "" + +#: ../../source/development/building_from_source.rst:312 +msgid "" +"The `Armadillo <http://arma.sourceforge.net/>`_ C++ library is used to " +"speed up computations related to the Thin Plate Spline transformer. See " +"https://cmake.org/cmake/help/latest/module/FindArmadillo.html for " +"details. On Windows builds using Conda-Forge dependencies, the following " +"packages may also need to be installed: ``blas blas-devel libblas " +"libcblas liblapack liblapacke``" +msgstr "" + +#: ../../source/development/building_from_source.rst:320 +msgid "Control whether to use Armadillo. Defaults to ON when Armadillo is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:324 +msgid "Arrow" +msgstr "" + +#: ../../source/development/building_from_source.rst:326 +msgid "" +"The `Apache Arrow C++ <https://github.com/apache/arrow/tree/master/cpp>` " +"library is required for the :ref:`vector.arrow` and :ref:`vector.parquet`" +" drivers. Specify install prefix in the ``CMAKE_PREFIX_PATH`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:332 +msgid "Control whether to use Arrow. Defaults to ON when Arrow is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:336 +msgid "" +"Control whether to use statically built Arrow libraries. Defaults to OFF " +"when Arrow is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:339 +msgid "basisu" +msgstr "" + +#: ../../source/development/building_from_source.rst:341 +msgid "" +"The `Basis Universal " +"<https://github.com/rouault/basis_universal/tree/cmake>` library is " +"required for the :ref:`raster.basisu` and :ref:`raster.ktx2` drivers. " +"Specify install prefix in the ``CMAKE_PREFIX_PATH`` variable or " +"``basisu_ROOT`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:347 +msgid "Control whether to use basisu. Defaults to ON when basisu is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:351 +msgid "Blosc" +msgstr "" + +#: ../../source/development/building_from_source.rst:353 +msgid "" +"`Blosc <https://github.com/Blosc/c-blosc>`_ is a library which offers a " +"meta-compression, with different backends (LZ4, Snappy, Zlib, Zstd, " +"etc.). It is used by the :ref:`raster.zarr` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:359 +msgid "Path to an include directory with the ``blosc.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:367 +msgid "Control whether to use Blosc. Defaults to ON when Blosc is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:371 +msgid "BRUNSLI" +msgstr "" + +#: ../../source/development/building_from_source.rst:373 +msgid "" +"The `Brunsli <https://github.com/google/brunsli>`_ JPEG repacking " +"library, used by the :ref:`raster.marfa` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:378 +msgid "" +"Path to an include directory with the ``brunsli/decode.h`` and " +"``brunsli\\encode.h`` header files." +msgstr "" + +#: ../../source/development/building_from_source.rst:382 +msgid "Path to the brunslienc-c library file." +msgstr "" + +#: ../../source/development/building_from_source.rst:386 +msgid "Path to the brunslidec-c library file." +msgstr "" + +#: ../../source/development/building_from_source.rst:390 +msgid "Control whether to use BRUNSLI. Defaults to ON when Brunsli is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:394 +msgid "CFITSIO" +msgstr "" + +#: ../../source/development/building_from_source.rst:396 +msgid "" +"The `C FITS I/O <https://heasarc.gsfc.nasa.gov/fitsio/>`_ library is " +"required for the :ref:`raster.fits` driver. It can be detected with pkg-" +"config." +msgstr "" + +#: ../../source/development/building_from_source.rst:401 +msgid "Path to an include directory with the ``fitsio.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:409 +msgid "Control whether to use CFITSIO. Defaults to ON when CFITSIO is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:413 +msgid "Crnlib" +msgstr "" + +#: ../../source/development/building_from_source.rst:415 +msgid "" +"`Crnlib / crunch <https://github.com/rouault/crunch/tree/build_fixes>`_ " +"is required for the :ref:`raster.dds` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:420 +msgid "Path to Crnlib include directory with ``crunch/crnlib.h`` header." +msgstr "" + +#: ../../source/development/building_from_source.rst:424 +msgid "Path to Crnlib library to be linked." +msgstr "" + +#: ../../source/development/building_from_source.rst:428 +msgid "Control whether to use Crnlib. Defaults to ON when Crnlib is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:432 +msgid "CURL" +msgstr "" + +#: ../../source/development/building_from_source.rst:434 +msgid "" +"`libcurl <https://curl.se/>`_ is required for all network accesses (HTTP," +" etc.)." +msgstr "" + +#: ../../source/development/building_from_source.rst:438 +msgid "Path to an include directory with the ``curl`` directory." +msgstr "" + +#: ../../source/development/building_from_source.rst:442 +msgid "" +"Path to a shared or static library file, such as ``libcurl.so``, " +"``libcurl.lib``, or other name." +msgstr "" + +#: ../../source/development/building_from_source.rst:449 +msgid "Must be set to ON when linking against a static build of Curl." +msgstr "" + +#: ../../source/development/building_from_source.rst:453 +msgid "Control whether to use Curl. Defaults to ON when Curl is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:457 +msgid "CryptoPP" +msgstr "" + +#: ../../source/development/building_from_source.rst:459 +msgid "" +"The `Crypto++ <https://github.com/weidai11/cryptopp>`_ library can be " +"used for the RSA SHA256 signing functionality used by some authentication" +" methods of Google Cloud. It might be required to use the " +":ref:`raster.eedai` images or use the :ref:`/vsigs/ <vsigs>` virtual file" +" system. It is also required for the :ref:`/vsicrypt/ <vsicrypt>` virtual" +" file system." +msgstr "" + +#: ../../source/development/building_from_source.rst:467 +#: ../../source/development/building_from_source.rst:1114 +#: ../../source/development/building_from_source.rst:1194 +#: ../../source/development/building_from_source.rst:1854 +#: ../../source/development/building_from_source.rst:1983 +msgid "Path to the base include directory." +msgstr "" + +#: ../../source/development/building_from_source.rst:471 +msgid "" +"Path to a shared or static library file. A similar variable " +"``CRYPTOPP_LIBRARY_DEBUG`` can also be specified to a similar library for" +" building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:477 +msgid "" +"Defaults to OFF. Might be required to set to ON when linking against " +"cryptopp.dll" +msgstr "" + +#: ../../source/development/building_from_source.rst:482 +msgid "Control whether to use CryptoPP. Defaults to ON when CryptoPP is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:486 +msgid "Deflate" +msgstr "" + +#: ../../source/development/building_from_source.rst:488 +msgid "" +"`libdeflate <https://github.com/ebiggers/libdeflate>`_ is a compression " +"library which offers the lossless Deflate/Zip compression algorithm. It " +"offers faster performance than ZLib, but is not a full replacement for " +"it, consequently it must be used as a complement to ZLib." +msgstr "" + +#: ../../source/development/building_from_source.rst:496 +msgid "Path to an include directory with the ``libdeflate.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:500 +msgid "" +"Path to a shared or static library file. A similar variable " +"``Deflate_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:506 +msgid "Control whether to use Deflate. Defaults to ON when Deflate is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:510 +#: ../../source/development/rfc/rfc11_fastidentify.rst:207 +#: ../../source/development/rfc/rfc34_license_policy.rst:175 +msgid "ECW" +msgstr "" + +#: ../../source/development/building_from_source.rst:512 +msgid "" +"The Hexagon ECW SDK (closed source/proprietary) is required for the " +":ref:`raster.ecw` driver. Currently only support for ECW SDK 3.3 and 5.5 " +"is offered." +msgstr "" + +#: ../../source/development/building_from_source.rst:515 +msgid "" +"For ECW SDK 5.5, ECW_ROOT or CMAKE_PREFIX_PATH should point to the " +"directory into which there are include and lib subdirectories, typically " +"ending with ERDAS-ECW_JPEG_2000_SDK-5.5.0/Desktop_Read-Only." +msgstr "" + +#: ../../source/development/building_from_source.rst:521 +msgid "Path to the include directory with the ``NCSECWClient.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:525 +msgid "Path to library file libNCSEcw" +msgstr "" + +#: ../../source/development/building_from_source.rst:529 +msgid "Path to library file libNCSCnet (only needed for SDK 3.3)" +msgstr "" + +#: ../../source/development/building_from_source.rst:533 +msgid "Path to library file libNCSEcwC (only needed for SDK 3.3)" +msgstr "" + +#: ../../source/development/building_from_source.rst:537 +msgid "Path to library file libNCSUtil (only needed for SDK 3.3)" +msgstr "" + +#: ../../source/development/building_from_source.rst:541 +msgid "Control whether to use ECW. Defaults to ON when ECW is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:545 +msgid "EXPAT" +msgstr "" + +#: ../../source/development/building_from_source.rst:547 +msgid "" +"`Expat <https://github.com/libexpat/libexpat>`_ is a stream-oriented XML " +"parser library which is required to enable XML parsing capabilities in an" +" important number of OGR drivers (GML, GeoRSS, GPX, KML, LVBAG, OSM, ODS," +" SVG, WFS, XSLX, etc.). It is strongly recommended. Other driver such as " +"ILI or GMLAS may also require the XercesC library." +msgstr "" + +#: ../../source/development/building_from_source.rst:555 +msgid "Path to the include directory with the ``expat.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:565 +msgid "Must be set to ON when linking against a static build of Expat." +msgstr "" + +#: ../../source/development/building_from_source.rst:569 +msgid "Control whether to use EXPAT. Defaults to ON when EXPAT is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:573 +#: ../../source/development/rfc/rfc34_license_policy.rst:185 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:113 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:68 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:587 +msgid "FileGDB" +msgstr "" + +#: ../../source/development/building_from_source.rst:575 +msgid "" +"The `FileGDB SDK <https://github.com/Esri/file-geodatabase-api>`_ (closed" +" source/proprietary) is required for the :ref:`vector.filegdb` driver " +"(not to be confused with the :ref:`vector.openfilegdb` driver that has no" +" external requirements)" +msgstr "" + +#: ../../source/development/building_from_source.rst:579 +msgid "" +"FileGDB_ROOT or CMAKE_PREFIX_PATH should point to the directory of the " +"SDK." +msgstr "" + +#: ../../source/development/building_from_source.rst:583 +msgid "Path to the include directory with the ``FileGDBAPI.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:587 +msgid "Path to library file" +msgstr "" + +#: ../../source/development/building_from_source.rst:591 +msgid "Path to Release library file (only used on Windows)" +msgstr "" + +#: ../../source/development/building_from_source.rst:595 +msgid "Path to Debug library file (only used on Windows)" +msgstr "" + +#: ../../source/development/building_from_source.rst:599 +msgid "Control whether to use FileGDB. Defaults to ON when FileGDB is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:603 +msgid "FreeXL" +msgstr "" + +#: ../../source/development/building_from_source.rst:605 +msgid "" +"The `FreeXL <https://www.gaia-gis.it/fossil/freexl/index>`_ library is " +"required for the :ref:`vector.xls` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:610 +msgid "Path to an include directory with the ``freexl.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:618 +msgid "Control whether to use FreeXL. Defaults to ON when FreeXL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:622 +msgid "FYBA" +msgstr "" + +#: ../../source/development/building_from_source.rst:624 +msgid "" +"The `OpenFyba <https://github.com/kartverket/fyba>`_ libraries are needed" +" to build the :ref:`vector.sosi` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:628 +msgid "Path to an include directory with the ``fyba.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:632 +msgid "Path to a library file ``fyba``" +msgstr "" + +#: ../../source/development/building_from_source.rst:636 +msgid "Path to a library file ``fygm``" +msgstr "" + +#: ../../source/development/building_from_source.rst:640 +msgid "Path to a library file ``fyut``" +msgstr "" + +#: ../../source/development/building_from_source.rst:644 +msgid "Control whether to use FYBA. Defaults to ON when FYBA is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:648 +msgid "GEOTIFF" +msgstr "" + +#: ../../source/development/building_from_source.rst:650 +msgid "" +"It is required for the :ref:`raster.gtiff` drivers, and a few other " +"drivers. If not found, an internal copy of libgeotiff can be used." +msgstr "" + +#: ../../source/development/building_from_source.rst:655 +msgid "Path to an include directory with the libgeotiff header files." +msgstr "" + +#: ../../source/development/building_from_source.rst:659 +msgid "" +"Path to a shared or static library file, such as ``libgeotiff.so``, " +"``geotiff.lib``, or other name. A similar variable " +"``GEOTIFF_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:666 +msgid "" +"Control whether to use external libgeotiff. Defaults to ON when external " +"libgeotiff is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:670 +msgid "" +"Control whether to use internal libgeotiff copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_GEOTIFF=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:675 +msgid "GEOS" +msgstr "" + +#: ../../source/development/building_from_source.rst:677 +msgid "" +"`GEOS <https://github.com/libgeos/geos>`_ is a C++ library for performing" +" operations on two-dimensional vector geometries. It is used as the " +"backend for most geometry processing operations available in OGR " +"(intersection, buffer, etc.). The ``geos-config`` program can be used to " +"detect it." +msgstr "" + +#: ../../source/development/building_from_source.rst:684 +msgid "Path to an include directory with the ``geos_c.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:688 +msgid "Path to a shared or static library file (libgeos_c)." +msgstr "" + +#: ../../source/development/building_from_source.rst:692 +msgid "Control whether to use GEOS. Defaults to ON when GEOS is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:696 +#: ../../source/development/rfc/rfc11_fastidentify.rst:201 +msgid "GIF" +msgstr "" + +#: ../../source/development/building_from_source.rst:698 +msgid "" +"`giflib <http://giflib.sourceforge.net/>`_ is required for the " +":ref:`raster.gif` driver. If not found, an internal copy can be used." +msgstr "" + +#: ../../source/development/building_from_source.rst:703 +msgid "Path to an include directory with the ``gif_lib.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:711 +msgid "" +"Control whether to use external giflib. Defaults to ON when external " +"giflib is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:715 +msgid "" +"Control whether to use internal giflib copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_GIF=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:720 +msgid "GTA" +msgstr "" + +#: ../../source/development/building_from_source.rst:722 +msgid "" +"The `GTA <https://marlam.de/gta/>`_ library is required for the " +":ref:`raster.gta` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:726 +msgid "Path to an include directory with the ``gta/gta.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:734 +msgid "Control whether to use GTA. Defaults to ON when GTA is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:738 +msgid "HEIF" +msgstr "" + +#: ../../source/development/building_from_source.rst:740 +msgid "" +"The `HEIF <https://github.com/strukturag/libheif>`_ (>= 1.1) library used" +" by the :ref:`raster.heif` driver. It can be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:745 +msgid "Path to an include directory with the ``libheif/heif.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:753 +msgid "Control whether to use HEIF. Defaults to ON when HEIF is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:756 +#: ../../source/development/rfc/rfc11_fastidentify.rst:202 +msgid "HDF4" +msgstr "" + +#: ../../source/development/building_from_source.rst:758 +msgid "" +"The `HDF4 <https://support.hdfgroup.org/products/hdf4/>`_ C library is " +"needed for the :ref:`raster.hdf4` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:763 +msgid "Path to an include directory with the ``hdf.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:767 +msgid "" +"Path to a shared or static ``dfalt`` or ``df`` library file. A similar " +"variable ``HDF4_df_LIBRARY_DEBUG`` can also be specified to a similar " +"library for building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:773 +msgid "" +"Path to a shared or static ``mfhdfalt`` or ``mfhdf`` library file. A " +"similar variable ``HDF4_mfhdf_LIBRARY_DEBUG`` can also be specified to a " +"similar library for building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:779 +msgid "" +"Path to a shared or static ``xdr`` library file. A similar variable " +"``HDF4_xdr_LIBRARY_DEBUG`` can also be specified to a similar library for" +" building Debug releases. It is generally not needed for Linux builds" +msgstr "" + +#: ../../source/development/building_from_source.rst:786 +msgid "" +"Path to a shared or static ``szip`` library file. A similar variable " +"``HDF4_szip_LIBRARY_DEBUG`` can also be specified to a similar library " +"for building Debug releases. It is generally not needed for Linux builds" +msgstr "" + +#: ../../source/development/building_from_source.rst:793 +msgid "" +"The value of this option is a list which defaults to " +"``df;mfhdf;xdr;szip``. It may be customized if the linking of HDF4 " +"require different libraries, in which case " +"HDF4_{comp_name}_LIBRARY_[RELEASE/DEBUG] variables will be available to " +"configure the library file." +msgstr "" + +#: ../../source/development/building_from_source.rst:800 +msgid "Control whether to use HDF4. Defaults to ON when HDF4 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:804 +msgid "HDF5" +msgstr "" + +#: ../../source/development/building_from_source.rst:806 +msgid "" +"The `HDF5 <https://github.com/HDFGroup/hdf5>`_ C library is needed for " +"the :ref:`raster.hdf5` and :ref:`raster.bag` drivers. The HDF5 CXX " +"library is needed for the :ref:`raster.kea` driver. The " +"https://cmake.org/cmake/help/latest/module/FindHDF5.html module is used " +"to detect the HDF5 library." +msgstr "" + +#: ../../source/development/building_from_source.rst:814 +msgid "Control whether to use HDF5. Defaults to ON when HDF5 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:818 +msgid "" +"Control whether to add a global lock around calls to HDF5 library. This " +"is needed if the HDF5 library is not built with thread-safety enabled and" +" if the HDF5 driver is used in a multi-threaded way. On Unix, a " +"heuristics try to detect if the HDF5 library has been built with thread-" +"safety enabled when linking against a HDF5 library. In other situations, " +"the setting must be manually set when needed." +msgstr "" + +#: ../../source/development/building_from_source.rst:829 +msgid "HDFS" +msgstr "" + +#: ../../source/development/building_from_source.rst:831 +msgid "" +"The `Hadoop File System <https://hadoop.apache.org/docs/stable/hadoop-" +"project-dist/hadoop-hdfs/LibHdfs.html>`_ native library is needed for the" +" :ref:`/vsihdfs/ <vsihdfs>` virtual file system." +msgstr "" + +#: ../../source/development/building_from_source.rst:836 +msgid "Path to an include directory with the ``hdfs.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:840 +msgid "Path to a shared or static ``hdfs`` library file." +msgstr "" + +#: ../../source/development/building_from_source.rst:844 +msgid "Control whether to use HDFS. Defaults to ON when HDFS is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:848 +msgid "Iconv" +msgstr "" + +#: ../../source/development/building_from_source.rst:850 +msgid "" +"The `Iconv <https://www.gnu.org/software/libiconv/>`_ library is used to " +"convert text from one encoding to another encoding. It is generally " +"available as a system library for Unix-like systems. On Windows, GDAL can" +" leverage the API of the operating system for a few base conversions, but" +" using Iconv will provide additional capabilities." +msgstr "" + +#: ../../source/development/building_from_source.rst:858 +msgid "Path to an include directory with the ``iconv.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:866 +msgid "Control whether to use Iconv. Defaults to ON when Iconv is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:870 +msgid "IDB" +msgstr "" + +#: ../../source/development/building_from_source.rst:872 +msgid "" +"The Informix DataBase Client SDK (closed source/proprietary) is needed " +"to build the :ref:`vector.idb` driver. IDB_ROOT or CMAKE_PREFIX_PATH " +"should point to the directory of the SDK." +msgstr "" + +#: ../../source/development/building_from_source.rst:879 +msgid "" +"Path to an include directory (typically ending with ``incl``) with the " +"``c++/it.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:883 +msgid "" +"Path to a library file ``ifc++`` (typically in the ``lib/c++`` sub " +"directory)" +msgstr "" + +#: ../../source/development/building_from_source.rst:887 +msgid "" +"Path to a library file ``ifdmi`` (typically in the ``lib/dmi`` sub " +"directory)" +msgstr "" + +#: ../../source/development/building_from_source.rst:891 +msgid "" +"Path to a library file ``ifsql`` (typically in the ``lib/esql`` sub " +"directory)" +msgstr "" + +#: ../../source/development/building_from_source.rst:895 +msgid "" +"Path to a library file ``ifcli`` (typically in the ``lib/cli`` sub " +"directory)" +msgstr "" + +#: ../../source/development/building_from_source.rst:899 +msgid "Control whether to use IDB. Defaults to ON when IDB is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:903 +#: ../../source/development/rfc/rfc11_fastidentify.rst:199 +msgid "JPEG" +msgstr "" + +#: ../../source/development/building_from_source.rst:905 +msgid "" +"libjpeg is required for the :ref:`raster.jpeg` driver, and may be used by" +" a few other drivers (:ref:`raster.gpkg`, :ref:`raster.marfa`, internal " +"libtiff, etc.) If not found, an internal copy of libjpeg (6b) can be " +"used. Using `libjpeg-turbo <https://github.com/libjpeg-turbo/libjpeg-" +"turbo>`_ is highly recommended to get best performance. See " +"https://cmake.org/cmake/help/latest/module/FindJPEG.html for more details" +" on how the library is detected." +msgstr "" + +#: ../../source/development/building_from_source.rst:915 +msgid "" +"When using libjpeg-turbo, JPEG_LIBRARY[_RELEASE/_DEBUG] should point to a" +" library with libjpeg ABI, not TurboJPEG. See https://libjpeg-" +"turbo.org/About/TurboJPEG for the difference." +msgstr "" + +#: ../../source/development/building_from_source.rst:921 +msgid "Path to an include directory with the ``jpeglib.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:925 +msgid "" +"Path to a shared or static library file. A similar variable " +"``JPEG_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:931 +msgid "" +"Control whether to use external libjpeg. Defaults to ON when external " +"libjpeg is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:935 +msgid "" +"Control whether to use internal libjpeg copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_JPEG=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:940 +msgid "" +"Used with external libjpeg. number is for example 80, for libjpeg 8 ABI. " +"This can be used to check a build time that the expected JPEG library is " +"the one that is included by GDAL." +msgstr "" + +#: ../../source/development/building_from_source.rst:946 +msgid "JPEG12" +msgstr "" + +#: ../../source/development/building_from_source.rst:948 +msgid "" +"libjpeg-12 bit can be used by the :ref:`raster.jpeg`, :ref:`raster.gtiff`" +" (when using internal libtiff), :ref:`raster.jpeg`, :ref:`raster.marfa` " +"and :ref:`raster.nitf` drivers to handle JPEG images with a 12 bit depth." +" It is only supported with the internal libjpeg (6b). This can be used " +"independently of if for regular 8 bit JPEG an external or internal " +"libjpeg is used." +msgstr "" + +#: ../../source/development/building_from_source.rst:956 +msgid "Control whether to use internal libjpeg-12 copy. Defaults to ON." +msgstr "" + +#: ../../source/development/building_from_source.rst:960 +msgid "" +"Starting with GDAL 3.7, if using libjpeg-turbo >= 2.2, which adds native " +"support for dual 8/12-bit, using internal libjpeg-12 is no longer needed " +"to get 12-bit JPEG support in the JPEG, MRF, NITF or GeoTIFF (when built " +"with internal libtiff) drivers. If using external libtiff, libtiff >= 4.5" +" built against libjpeg-turbo >= 2.2 is needed to get 12-bit JPEG support " +"in the GeoTIFF support." +msgstr "" + +#: ../../source/development/building_from_source.rst:968 +msgid "JSON-C" +msgstr "" + +#: ../../source/development/building_from_source.rst:970 +msgid "" +"The `json-c <https://github.com/json-c/json-c>`_ library is required to " +"read and write JSON content. It can be detected with pkg-config. If not " +"found, an internal copy of json-c can be used." +msgstr "" + +#: ../../source/development/building_from_source.rst:977 +msgid "Path to an include directory with the ``json.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:985 +msgid "Control whether to use JSON-C. Defaults to ON when JSON-C is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:989 +msgid "" +"Control whether to use internal JSON-C copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_JSONC=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:994 +msgid "JXL" +msgstr "" + +#: ../../source/development/building_from_source.rst:996 +msgid "" +"The `libjxl <https://github.com/libjxl/libjxl>` library used by the " +":ref:`raster.gtiff` driver, when built against internal libtiff. It can " +"be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:1002 +msgid "Path to an include directory with the ``jxl/decode.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1010 +msgid "Control whether to use JXL. Defaults to ON when JXL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1014 +msgid "KDU" +msgstr "" + +#: ../../source/development/building_from_source.rst:1016 +msgid "" +"The Kakadu library (proprietary) is required for the :ref:`raster.jp2kak`" +" and :ref:`raster.jpipkak` drivers. There is no standardized installation" +" layout, nor fixed library file names, so finding Kakadu artifacts is a " +"bit challenging. Currently automatic finding of it from the KDU_ROOT " +"variable is only implemented for Linux, Mac and Windows x86_64 builds. " +"For other platforms, users need to manually specify the KDU_LIBRARY and " +"KDU_AUX_LIBRARY variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:1026 +msgid "" +"Path to the root of the Kakadu build tree, from which the " +"``coresys/common/kdu_elementary.h`` header file should be found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1031 +msgid "" +"Path to a shared library file whose name is like libkdu_vXYR.so on Unix " +"or kdu_vXYR.lib on Windows, where X.Y is the Kakadu version." +msgstr "" + +#: ../../source/development/building_from_source.rst:1036 +msgid "" +"Path to a shared library file whose name is like libkdu_aXYR.so on Unix " +"or kdu_aXYR.lib on Windows, where X.Y is the Kakadu version." +msgstr "" + +#: ../../source/development/building_from_source.rst:1041 +msgid "Control whether to use KDU. Defaults to ON when KDU is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1044 +msgid "KEA" +msgstr "" + +#: ../../source/development/building_from_source.rst:1046 +msgid "" +"The `KEA <http://www.kealib.org/>`_ library is required for the " +":ref:`raster.kea` driver. The HDF5 CXX library is also required." +msgstr "" + +#: ../../source/development/building_from_source.rst:1051 +msgid "Path to an include directory with the ``libkea/KEACommon.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1059 +msgid "Control whether to use KEA. Defaults to ON when KEA is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1063 +msgid "LERC" +msgstr "" + +#: ../../source/development/building_from_source.rst:1065 +msgid "" +"`LERC <https://github.com/esri/lerc>`_ is an open-source image or raster " +"format which supports rapid encoding and decoding for any pixel type (not" +" just RGB or Byte). Users set the maximum compression error per pixel " +"while encoding, so the precision of the original input image is preserved" +" (within user defined error bounds)." +msgstr "" + +#: ../../source/development/building_from_source.rst:1072 +msgid "Path to an include directory with the ``Lerc_c_api.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1080 +msgid "Control whether to use LERC. Defaults to ON when LERC is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1084 +msgid "" +"Control whether to use the LERC internal library. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_LERC=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:1088 +msgid "LIBAEC" +msgstr "" + +#: ../../source/development/building_from_source.rst:1090 +msgid "" +"`libaec <https://gitlab.dkrz.de/k202009/libaec>`_ is a compression " +"library which offers the extended Golomb-Rice coding as defined in the " +"CCSDS recommended standard 121.0-B-3. It is used by the " +":ref:`raster.grib` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1096 +msgid "Path to an include directory with the ``libaec.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1104 +msgid "Control whether to use LIBAEC. Defaults to ON when LIBAEC is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1107 +msgid "LibKML" +msgstr "" + +#: ../../source/development/building_from_source.rst:1109 +msgid "" +"`LibKML <https://github.com/libkml/libkml>`_ is required for the " +":ref:`vector.libkml` driver. It can be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:1118 +msgid "Path to a shared or static library file for ``kmlbase``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1122 +msgid "Path to a shared or static library file for ``kmldom``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1126 +msgid "Path to a shared or static library file for ``kmlengine``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1130 +msgid "Path to a shared or static library file for ``minizip``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1134 +msgid "Path to a shared or static library file for ``uriparser``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1138 +msgid "Control whether to use LibKML. Defaults to ON when LibKML is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1141 +msgid "LibLZMA" +msgstr "" + +#: ../../source/development/building_from_source.rst:1143 +msgid "" +"`LibLZMA <https://tukaani.org/xz/>`_ is a compression library which " +"offers the lossless LZMA2 compression algorithm. It is used by the " +"internal libtiff library or the :ref:`raster.zarr` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1149 +msgid "Path to an include directory with the ``lzma.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1157 +msgid "Control whether to use LibLZMA. Defaults to ON when LibLZMA is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1161 +msgid "libOpenDRIVE" +msgstr "" + +#: ../../source/development/building_from_source.rst:1163 +msgid "" +"`libOpenDRIVE <https://github.com/pageldev/libOpenDRIVE>`_ is required " +"for the :ref:`vector.xodr` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1167 +msgid "" +"Path to libOpenDRIVE CMake configuration directory " +"``<installDir>/cmake/``. The :file:`cmake/` path is usually automatically" +" created when installing libOpenDRIVE and contains the necessary " +"configuration files for inclusion into other project builds." +msgstr "" + +#: ../../source/development/building_from_source.rst:1171 +msgid "" +"Control whether to use libOpenDRIVE. Defaults to ON when libOpenDRIVE is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1175 +msgid "LibQB3" +msgstr "" + +#: ../../source/development/building_from_source.rst:1177 +msgid "" +"The `QB3 <https://github.com/lucianpls/QB3>`_ compression, used by the " +":ref:`raster.marfa` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1182 +msgid "Control whether to use LibQB3. Defaults to ON when LibQB3 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1186 +msgid "LibXml2" +msgstr "" + +#: ../../source/development/building_from_source.rst:1188 +msgid "" +"The `LibXml2 <http://xmlsoft.org/>`_ processing library is used to do " +"validation of XML files against a XML Schema (.xsd) in a few drivers " +"(PDF, GMLAS, GML OGR VRT) and for advanced capabilities in GMLJP2v2 " +"generation." +msgstr "" + +#: ../../source/development/building_from_source.rst:1202 +msgid "Control whether to use LibXml2. Defaults to ON when LibXml2 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1206 +msgid "LURATECH" +msgstr "" + +#: ../../source/development/building_from_source.rst:1208 +msgid "" +"The Luratech JPEG2000 SDK (closed source/proprietary) is required for the" +" :ref:`raster.jp2lura` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1211 +msgid "" +"LURATECH_ROOT or CMAKE_PREFIX_PATH should point to the directory of the " +"SDK." +msgstr "" + +#: ../../source/development/building_from_source.rst:1215 +msgid "Path to the include directory with the ``lwf_jp2.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1219 +msgid "Path to library file lib_lwf_jp2.a / lwf_jp2.lib" +msgstr "" + +#: ../../source/development/building_from_source.rst:1223 +msgid "Control whether to use LURATECH. Defaults to ON when LURATECH is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1227 +msgid "LZ4" +msgstr "" + +#: ../../source/development/building_from_source.rst:1229 +msgid "" +"`LZ4 <https://github.com/lz4/lz4>`_ is a compression library which offers" +" the lossless LZ4 compression algorithm. It is used by the " +":ref:`raster.zarr` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1235 +msgid "Path to an include directory with the ``lz4.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1239 +msgid "" +"Path to a shared or static library file. A similar variable " +"``LZ4_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:1245 +msgid "Control whether to use LZ4. Defaults to ON when LZ4 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1249 +msgid "MONGOCXX" +msgstr "" + +#: ../../source/development/building_from_source.rst:1251 +msgid "" +"The `MongoCXX <https://github.com/mongodb/mongo-cxx-driver>`_ and BsonCXX" +" libraries are needed to build the :ref:`vector.mongodbv3` driver. They " +"can be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:1257 +msgid "Path to an include directory with the ``mongocxx/client.hpp`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1261 +msgid "" +"Path to an include directory with the ``bsoncxx/config/version.hpp`` " +"header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1265 +msgid "Path to a library file ``mongocxx``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1269 +msgid "Path to a library file ``bsoncxx``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1273 +msgid "Control whether to use MONGOCXX. Defaults to ON when MONGOCXX is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1277 +#: ../../source/development/rfc/rfc34_license_policy.rst:177 +msgid "MRSID" +msgstr "" + +#: ../../source/development/building_from_source.rst:1279 +msgid "" +"The MRSID Raster DSDK (closed source/proprietary) is required for the " +":ref:`raster.mrsid` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1282 +msgid "" +"MRSID_ROOT or CMAKE_PREFIX_PATH should point to the directory of the SDK " +"ending with Raster_DSDK. Note that on Linux, its lib subdirectory should " +"be in the LD_LIBRARY_PATH so that the linking of applications succeeds " +"and libtbb.so can be found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1289 +msgid "Path to the include directory with the ``lt_base.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1293 +msgid "Path to library file libltidsdk" +msgstr "" + +#: ../../source/development/building_from_source.rst:1297 +msgid "" +"Whether to enable JPEG2000 support through the MrSID SDK. The default " +"value of this option is OFF." +msgstr "" + +#: ../../source/development/building_from_source.rst:1302 +msgid "Control whether to use MRSID. Defaults to ON when MRSID is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1306 +msgid "MSSQL_NCLI" +msgstr "" + +#: ../../source/development/building_from_source.rst:1308 +msgid "" +"The Microsoft SQL Native Client Library (closed source/proprietary) is " +"required to enable bulk copy in the :ref:`vector.mssqlspatial` driver. If" +" both MSSQL_NCLI and MSSQL_ODBC are found and enabled, MSSQL_ODBC will be" +" used. The library is normally found if installed in standard location, " +"and at version 11." +msgstr "" + +#: ../../source/development/building_from_source.rst:1315 +msgid "Major version of the Native Client, typically 11" +msgstr "" + +#: ../../source/development/building_from_source.rst:1319 +msgid "Path to include directory with ``sqlncli.h`` header." +msgstr "" + +#: ../../source/development/building_from_source.rst:1323 +#: ../../source/development/building_from_source.rst:1348 +#: ../../source/development/building_from_source.rst:1367 +msgid "Path to library to be linked." +msgstr "" + +#: ../../source/development/building_from_source.rst:1327 +msgid "" +"Control whether to use MSSQL_NCLI. Defaults to ON when MSSQL_NCLI is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1331 +msgid "MSSQL_ODBC" +msgstr "" + +#: ../../source/development/building_from_source.rst:1333 +msgid "" +"The Microsoft SQL Native ODBC driver Library (closed source/proprietary) " +"is required to enable bulk copy in the :ref:`vector.mssqlspatial` driver." +" If both MSSQL_NCLI and MSSQL_ODBC are found and enabled, MSSQL_ODBC will" +" be used. The library is normally found if installed in standard " +"location, and at version 17." +msgstr "" + +#: ../../source/development/building_from_source.rst:1340 +msgid "Major version of the Native Client, typically 17" +msgstr "" + +#: ../../source/development/building_from_source.rst:1344 +msgid "Path to include directory with ``msodbcsql.h`` header." +msgstr "" + +#: ../../source/development/building_from_source.rst:1352 +msgid "" +"Control whether to use MSSQL_ODBC. Defaults to ON when MSSQL_ODBC is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1356 +msgid "MYSQL" +msgstr "" + +#: ../../source/development/building_from_source.rst:1358 +msgid "" +"The MySQL or MariaDB client library is required to enable the " +":ref:`vector.mysql` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1363 +msgid "Path to include directory with ``mysql.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1371 +msgid "Control whether to use MYSQL. Defaults to ON when MYSQL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1375 +msgid "NetCDF" +msgstr "" + +#: ../../source/development/building_from_source.rst:1377 +msgid "" +"The `netCDF <https://github.com/Unidata/netcdf-c>`_ is required to enable" +" the :ref:`raster.netcdf` driver. The ``nc-config`` program can be used " +"to detect it." +msgstr "" + +#: ../../source/development/building_from_source.rst:1383 +msgid "Path to an include directory with the ``netcdf.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1391 +msgid "Control whether to use netCDF. Defaults to ON when netCDF is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1395 +msgid "ODBC" +msgstr "" + +#: ../../source/development/building_from_source.rst:1397 +msgid "" +"ODBC is required for various drivers: :ref:`vector.odbc`, " +":ref:`vector.pgeo`, :ref:`vector.hana` and :ref:`vector.mssqlspatial`. It" +" is normally automatically found in system directories on Unix and " +"Windows." +msgstr "" + +#: ../../source/development/building_from_source.rst:1403 +msgid "Path to ODBC include directory with ``sql.h`` header." +msgstr "" + +#: ../../source/development/building_from_source.rst:1407 +msgid "Path to ODBC library to be linked." +msgstr "" + +#: ../../source/development/building_from_source.rst:1411 +msgid "Control whether to use ODBC. Defaults to ON when ODBC is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1415 +msgid "ODBC-CPP" +msgstr "" + +#: ../../source/development/building_from_source.rst:1417 +msgid "" +"The `odbc-cpp-wrapper library <https://github.com/SAP/odbc-cpp-wrapper>`_" +" is required for the :ref:`vector.hana` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1422 +msgid "Path to an include directory with the ``odbc/Environment.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1430 +msgid "Control whether to use ODBC-CPP. Defaults to ON when ODBC-CPP is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1434 +msgid "OGDI" +msgstr "" + +#: ../../source/development/building_from_source.rst:1436 +msgid "" +"The `OGDI <https://github.com/libogdi/ogdi/>`_ library is required for " +"the :ref:`vector.ogdi` driver. It can be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:1441 +msgid "Path to an include directory with the ``ecs.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1449 +msgid "Control whether to use OGDI. Defaults to ON when OGDI is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1453 +msgid "OpenCAD" +msgstr "" + +#: ../../source/development/building_from_source.rst:1455 +msgid "" +"`libopencad <https://github.com/nextgis-borsch/lib_opencad>`_ is required" +" for the :ref:`vector.cad` driver. If not found, an internal copy can be " +"used." +msgstr "" + +#: ../../source/development/building_from_source.rst:1460 +msgid "Path to an include directory with the ``opencad.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1468 +msgid "" +"Control whether to use external libopencad. Defaults to ON when external " +"libopencad is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1472 +msgid "" +"Control whether to use internal libopencad copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_OPENCAD=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:1478 +msgid "OpenCL" +msgstr "" + +#: ../../source/development/building_from_source.rst:1480 +msgid "" +"The OpenCL library may be used to accelerate warping computations, " +"typically with a GPU." +msgstr "" + +#: ../../source/development/building_from_source.rst:1483 +msgid "" +"(GDAL 3.5 and 3.6) It is disabled by default even when detected, since " +"the current OpenCL warping implementation lags behind the generic " +"implementation. Starting with GDAL 3.7, build support is enabled by " +"default when OpenCL is detected, but it is disabled by default at " +"runtime. The warping option USE_OPENCL or the configuration option " +"GDAL_USE_OPENCL must be set to YES to enable it." +msgstr "" + +#: ../../source/development/building_from_source.rst:1491 +msgid "Path to an include directory with the ``CL/cl.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1499 +msgid "Control whether to use OPENCL. Defaults to *OFF* when OPENCL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1503 +msgid "OpenEXR" +msgstr "" + +#: ../../source/development/building_from_source.rst:1505 +msgid "" +"`OpenEXR <https://github.com/AcademySoftwareFoundation/openexr>`_ is " +"required for the :ref:`raster.exr` driver" +msgstr "" + +#: ../../source/development/building_from_source.rst:1507 +msgid "" +"Specify ``OpenEXR_ROOT`` variable pointing to the parent directory of " +"/lib and /include subdirectories, i.e. /DEV/lib/openexr-3.0. For OpenEXR " +">= 3 additionally specify ``Imath_ROOT`` as this is a separate library " +"now, i.e. /DEV/lib/imath-3.1.3" +msgstr "" + +#: ../../source/development/building_from_source.rst:1512 +#: ../../source/development/building_from_source.rst:1517 +msgid "or" +msgstr "" + +#: ../../source/development/building_from_source.rst:1514 +msgid "" +"Specify root directory adding to the ``CMAKE_PREFIX_PATH`` variable to " +"find OpenEXR's pkgconfig. For example " +"-DCMAKE_PREFIX_PATH=/DEV/lib/openexr-3.0;/DEV/lib/imath-3.1.3" +msgstr "" + +#: ../../source/development/building_from_source.rst:1519 +msgid "" +"Get real specific and set ``OpenEXR_INCLUDE_DIR``, ``Imath_INCLUDE_DIR``," +" ``OpenEXR_LIBRARY``, ``OpenEXR_UTIL_LIBRARY``, ``OpenEXR_HALF_LIBRARY``," +" ``OpenEXR_IEX_LIBRARY`` explicitly" +msgstr "" + +#: ../../source/development/building_from_source.rst:1527 +msgid "Control whether to use OpenEXR. Defaults to ON when OpenEXR is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1531 +msgid "OpenJPEG" +msgstr "" + +#: ../../source/development/building_from_source.rst:1533 +msgid "" +"The `OpenJPEG <https://github.com/uclouvain/openjpeg>`_ library is an " +"open-source JPEG-2000 codec written in C language. It is required for the" +" :ref:`raster.jp2openjpeg` driver, or other drivers that use JPEG-2000 " +"functionality." +msgstr "" + +#: ../../source/development/building_from_source.rst:1539 +msgid "Path to an include directory with the ``openjpeg.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1547 +msgid "Control whether to use OpenJPEG. Defaults to ON when OpenJPEG is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1553 +msgid "" +"Control the mode used for find_package(OpenJPEG). Defaults to MODULE for " +"compatibility with OpenJPEG < 2.5.1. If set to CONFIG, only Config mode " +"search is attempted. If set to empty string, default CMake logic " +"(https://cmake.org/cmake/help/latest/command/find_package.html) applies." +msgstr "" + +#: ../../source/development/building_from_source.rst:1560 +msgid "OpenSSL" +msgstr "" + +#: ../../source/development/building_from_source.rst:1562 +msgid "" +"The Crypto component of the `OpenSSL " +"<https://github.com/openssl/openssl>`_ library can be used for the RSA " +"SHA256 signing functionality used by some authentication methods of " +"Google Cloud. It might be required to use the :ref:`raster.eedai` images " +"or use the :ref:`/vsigs/ <vsigs>` virtual file system." +msgstr "" + +#: ../../source/development/building_from_source.rst:1567 +msgid "" +"See https://cmake.org/cmake/help/latest/module/FindOpenSSL.html for " +"details on how to configure the library. For static linking, the " +"following options may be needed: -DOPENSSL_USE_STATIC_LIBS=TRUE " +"-DOPENSSL_MSVC_STATIC_RT=TRUE" +msgstr "" + +#: ../../source/development/building_from_source.rst:1573 +msgid "Control whether to use OpenSSL. Defaults to ON when OpenSSL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1577 +msgid "Oracle" +msgstr "" + +#: ../../source/development/building_from_source.rst:1579 +msgid "" +"The Oracle Instant Client SDK (closed source/proprietary) is required for" +" the :ref:`vector.oci` and the :ref:`raster.georaster` drivers" +msgstr "" + +#: ../../source/development/building_from_source.rst:1584 +msgid "Path to the root directory of the Oracle Instant Client SDK." +msgstr "" + +#: ../../source/development/building_from_source.rst:1588 +msgid "Control whether to use Oracle. Defaults to ON when Oracle is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1592 +msgid "Parquet" +msgstr "" + +#: ../../source/development/building_from_source.rst:1594 +msgid "" +"The Parquet component of the `Apache Arrow C++ " +"<https://github.com/apache/arrow/tree/master/cpp>` library is required " +"for the :ref:`vector.parquet` driver. Specify install prefix in the " +"``CMAKE_PREFIX_PATH`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:1600 +msgid "Control whether to use Parquet. Defaults to ON when Parquet is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1604 +msgid "" +"Control whether to use statically built Arrow libraries. Defaults to OFF " +"when Parquet is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1608 +msgid "PCRE2" +msgstr "" + +#: ../../source/development/building_from_source.rst:1610 +msgid "" +"`PCRE2 <https://github.com/PhilipHazel/pcre2>`_ implements Perl-" +"compatible Regular Expressions support. It is used for the REGEXP " +"operator in drivers using SQLite3." +msgstr "" + +#: ../../source/development/building_from_source.rst:1615 +msgid "Path to an include directory with the ``pcre2.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1619 +msgid "Path to a shared or static library file with \"pcre2-8\" in its name." +msgstr "" + +#: ../../source/development/building_from_source.rst:1623 +msgid "Control whether to use PCRE2. Defaults to ON when PCRE2 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1627 +msgid "PDFIUM" +msgstr "" + +#: ../../source/development/building_from_source.rst:1629 +msgid "" +"The `PDFium <https://github.com/rouault/pdfium_build_gdal_3_5>`_ library " +"is one of the possible backends for the :ref:`raster.pdf` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1634 +msgid "Path to an include directory with the ``public/fpdfview.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1642 +msgid "Control whether to use PDFIUM. Defaults to ON when PDFIUM is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1646 +#: ../../source/development/rfc/rfc11_fastidentify.rst:200 +msgid "PNG" +msgstr "" + +#: ../../source/development/building_from_source.rst:1648 +msgid "" +"`libpng <https://github.com/glennrp/libpng>`_ is required for the " +":ref:`raster.png` driver, and may be used by a few other drivers " +"(:ref:`raster.grib`, :ref:`raster.gpkg`, etc.) If not found, an internal " +"copy of libpng can be used. See " +"https://cmake.org/cmake/help/latest/module/FindPNG.html for more details " +"on how the library is detected." +msgstr "" + +#: ../../source/development/building_from_source.rst:1656 +msgid "Path to an include directory with the ``png.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1660 +msgid "" +"Path to a shared or static library file. A similar variable " +"``PNG_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:1666 +msgid "" +"Control whether to use external libpng. Defaults to ON when external " +"libpng is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1670 +msgid "" +"Control whether to use internal libpng copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_PNG=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:1675 +msgid "Poppler" +msgstr "" + +#: ../../source/development/building_from_source.rst:1677 +msgid "" +"The `Poppler <https://poppler.freedesktop.org/>`_ library is one of the " +"possible backends for the :ref:`raster.pdf` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1680 +msgid "" +"Note that GDAL requires Poppler private headers, that are only installed " +"if configuring Poppler with -DENABLE_UNSTABLE_API_ABI_HEADERS." +msgstr "" + +#: ../../source/development/building_from_source.rst:1685 +msgid "Path to an include directory with the ``poppler-config.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1693 +msgid "Control whether to use Poppler. Defaults to ON when Poppler is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1697 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:46 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:60 +msgid "PostgreSQL" +msgstr "" + +#: ../../source/development/building_from_source.rst:1699 +msgid "" +"The `PostgreSQL client library <https://www.postgresql.org/>`_ is " +"required for the :ref:`vector.pg` and :ref:`raster.postgisraster` " +"drivers." +msgstr "" + +#: ../../source/development/building_from_source.rst:1704 +msgid "Path to an include directory with the ``libpq-fe.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1708 +msgid "" +"Path to a shared or static library file ``pq`` / ``libpq``. A similar " +"variable ``PostgreSQL_LIBRARY_DEBUG`` can also be specified to a similar " +"library for building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:1714 +msgid "" +"Control whether to use PostgreSQL. Defaults to ON when PostgreSQL is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1718 +msgid "PROJ" +msgstr "" + +#: ../../source/development/building_from_source.rst:1720 +msgid "" +"`PROJ <https://github.com/OSGeo/PROJ/>`_ >= 6.3 is a *required* " +"dependency for GDAL." +msgstr "" + +#: ../../source/development/building_from_source.rst:1724 +msgid "Path to an include directory with the ``proj.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1728 +msgid "" +"Path to a shared or static library file, such as ``libproj.so``, " +"``proj.lib``, or other name. A similar variable ``PROJ_LIBRARY_DEBUG`` " +"can also be specified to a similar library for building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:1737 +msgid "" +"Control the mode used for find_package(PROJ). Alters how the default " +"CMake search logic " +"(https://cmake.org/cmake/help/latest/command/find_package.html) applies. " +"Defaults to CUSTOM, where the CONFIG mode is applied for PROJ >= 8, and " +"fallbacks to default MODULE mode otherwise. Other values are passed " +"directly to find_package()" +msgstr "" + +#: ../../source/development/building_from_source.rst:1745 +msgid "QHULL" +msgstr "" + +#: ../../source/development/building_from_source.rst:1747 +msgid "" +"The `QHULL <https://github.com/qhull/qhull>`_ library is used for the " +"linear interpolation of gdal_grid. If not found, an internal copy can be " +"used." +msgstr "" + +#: ../../source/development/building_from_source.rst:1752 +msgid "" +"Name of the pkg-config package, typically ``qhull_r`` or " +"``qhullstatic_r``. Defaults to ``qhull_r``" +msgstr "" + +#: ../../source/development/building_from_source.rst:1756 +msgid "" +"Path to an include directory with the ``libqhull_r/libqhull_r.h`` header " +"file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1760 +msgid "Path to a shared or static library file to the reentrant library." +msgstr "" + +#: ../../source/development/building_from_source.rst:1764 +msgid "Control whether to use QHULL. Defaults to ON when QHULL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1768 +msgid "" +"Control whether to use internal QHULL copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_QHULL=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:1773 +msgid "RASTERLITE2" +msgstr "" + +#: ../../source/development/building_from_source.rst:1775 +msgid "" +"The `RasterLite2 <https://www.gaia-gis.it/fossil/librasterlite2/index>`_ " +"(>= 1.1.0) library used by the :ref:`raster.rasterlite2` driver. It can " +"be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:1781 +msgid "" +"Path to an include directory with the ``rasterlite2/rasterlite2.h`` " +"header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1789 +msgid "" +"Control whether to use RasterLite2. Defaults to ON when RasterLite2 is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1793 +msgid "rdb" +msgstr "" + +#: ../../source/development/building_from_source.rst:1795 +msgid "" +"The `RDB <https://repository.riegl.com/software/libraries/rdblib>` " +"(closed source/proprietary) library is required for the :ref:`raster.rdb`" +" driver. Specify install prefix in the ``CMAKE_PREFIX_PATH`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:1801 +msgid "Control whether to use rdb. Defaults to ON when rdb is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1805 +msgid "SPATIALITE" +msgstr "" + +#: ../../source/development/building_from_source.rst:1807 +msgid "" +"The `Spatialite <https://www.gaia-gis.it/fossil/libspatialite/index>`_ " +"library used by the :ref:`vector.sqlite` and :ref:`vector.gpkg` drivers, " +"and the :ref:`sql_sqlite_dialect`. It can be detected with pkg-config." +msgstr "" + +#: ../../source/development/building_from_source.rst:1813 +msgid "Path to an include directory with the ``spatialite.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1821 +msgid "" +"Control whether to use Spatialite. Defaults to ON when Spatialite is " +"found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1825 +msgid "SQLite3" +msgstr "" + +#: ../../source/development/building_from_source.rst:1827 +msgid "" +"The `SQLite3 <https://sqlite.org/index.html>`_ library is required for " +"the :ref:`vector.sqlite` and :ref:`vector.gpkg` drivers (and also used by" +" other drivers), and the :ref:`sql_sqlite_dialect`." +msgstr "" + +#: ../../source/development/building_from_source.rst:1833 +msgid "Path to an include directory with the ``sqlite3.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1837 +msgid "" +"Path to a shared or static library file, such as ``libsqlite3.so``, " +"``sqlite3.lib`` or other name." +msgstr "" + +#: ../../source/development/building_from_source.rst:1842 +msgid "Control whether to use SQLite3. Defaults to ON when SQLite3 is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1846 +msgid "SFCGAL" +msgstr "" + +#: ../../source/development/building_from_source.rst:1848 +msgid "" +"`SFCGAL <https://github.com/Oslandia/SFCGAL>`_ is a geometry library " +"which supports ISO 19107:2013 and OGC Simple Features Access 1.2 for 3D " +"operations (PolyhedralSurface, TINs, ...)" +msgstr "" + +#: ../../source/development/building_from_source.rst:1858 +msgid "" +"Path to a shared or static library file. A similar variable " +"``SFCGAL_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:1864 +msgid "Control whether to use SFCGAL. Defaults to ON when SFCGAL is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1868 +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:213 +msgid "SWIG" +msgstr "" + +#: ../../source/development/building_from_source.rst:1870 +msgid "" +"`SWIG <http://swig.org/>`_ is a software development tool that connects " +"programs written in C and C++ with a variety of high-level programming " +"languages. It is used for the Python, Java and CSharp bindings." +msgstr "" + +#: ../../source/development/building_from_source.rst:1876 +msgid "Path to the SWIG executable." +msgstr "" + +#: ../../source/development/building_from_source.rst:1878 +msgid "" +"Note that setting it explicitly might be needed, and that putting the " +"directory of the installed binary into the PATH might not be sufficient. " +"The reason is that when building from source, a \"swig\" binary will be " +"generated, but FindSWIG will prefer a \"swig-4.0\" binary if found " +"elsewhere in the PATH." +msgstr "" + +#: ../../source/development/building_from_source.rst:1886 +msgid "TEIGHA" +msgstr "" + +#: ../../source/development/building_from_source.rst:1888 +msgid "" +"The TEIGHA / Open Design Alliance libraries (closed source/proprietary) " +"are required for the :ref:`vector.dwg` and :ref:`vector.dgnv8` drivers. " +"Note that on Linux, with a SDK consisting of shared libraries, the " +"bin/{platform_name} subdirectory of the SDK should be in the " +"LD_LIBRARY_PATH so that the linking of applications succeeds. The " +"TEIGHA_ROOT variable must be set." +msgstr "" + +#: ../../source/development/building_from_source.rst:1897 +msgid "" +"Path to the base directory where the Kernel and Drawings package must be " +"extracted." +msgstr "" + +#: ../../source/development/building_from_source.rst:1902 +msgid "" +"Path to a directory where a ``OdActivationInfo`` file is located. If the " +"file is somewhere under TEIGHA_ROOT, it will be automatically discovered." +" Otherwise this variable must be set for recent SDK versions (at least " +"with 2021 and later)." +msgstr "" + +#: ../../source/development/building_from_source.rst:1909 +msgid "Control whether to use TEIGHA. Defaults to ON when TEIGHA is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1913 +msgid "TIFF" +msgstr "" + +#: ../../source/development/building_from_source.rst:1915 +msgid "" +"`libtiff <https://gitlab.com/libtiff/libtiff/>`_ is required for the " +":ref:`raster.gtiff` drivers, and a few other drivers. If not found, an " +"internal copy of libtiff can be used." +msgstr "" + +#: ../../source/development/building_from_source.rst:1921 +msgid "Path to an include directory with the ``tiff.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1925 +msgid "" +"Path to a shared or static library file, such as ``libtiff.so``, " +"``tiff.lib``, or other name. A similar variable ``TIFF_LIBRARY_DEBUG`` " +"can also be specified to a similar library for building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:1932 +msgid "" +"Control whether to use external libtiff. Defaults to ON when external " +"libtiff is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1936 +msgid "" +"Control whether to use internal libtiff copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_TIFF=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:1941 +msgid "TileDB" +msgstr "" + +#: ../../source/development/building_from_source.rst:1943 +msgid "" +"The `TileDB <https://github.com/TileDB-Inc/TileDB>` library is required " +"for the :ref:`raster.tiledb` driver. Specify install prefix in the " +"``CMAKE_PREFIX_PATH`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:1946 +msgid "TileDB >= 2.15 is required since GDAL 3.9" +msgstr "" + +#: ../../source/development/building_from_source.rst:1950 +msgid "Control whether to use TileDB. Defaults to ON when TileDB is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1954 +msgid "WebP" +msgstr "" + +#: ../../source/development/building_from_source.rst:1956 +msgid "" +"`WebP <https://github.com/webmproject/libwebp>`_ is a image compression " +"library. It is required for the :ref:`raster.webp` driver, and may be " +"used by the :ref:`raster.gpkg` and the internal libtiff library." +msgstr "" + +#: ../../source/development/building_from_source.rst:1962 +msgid "Path to an include directory with the ``webp/encode.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:1970 +msgid "Control whether to use WebP. Defaults to ON when WebP is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1974 +msgid "XercesC" +msgstr "" + +#: ../../source/development/building_from_source.rst:1976 +msgid "" +"`Xerces-C <https://github.com/apache/xerces-c>`_ is a stream-oriented XML" +" parser library which is required to enable XML parsing capabilities in " +"the :ref:`vector.nas`, :ref:`vector.ili` and :ref:`vector.gmlas` drivers." +" It can also be used as an alternative to Expat for the GML driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:1991 +msgid "Control whether to use XercesC. Defaults to ON when XercesC is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:1995 +msgid "ZLIB" +msgstr "" + +#: ../../source/development/building_from_source.rst:1997 +msgid "" +"`ZLib <https://github.com/madler/zlib>`_ is a compression library which " +"offers the lossless Deflate/Zip compression algorithm." +msgstr "" + +#: ../../source/development/building_from_source.rst:2002 +msgid "Path to an include directory with the ``zlib.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:2006 +msgid "" +"Path to a shared or static library file. A similar variable " +"``ZLIB_LIBRARY_DEBUG`` can also be specified to a similar library for " +"building Debug releases." +msgstr "" + +#: ../../source/development/building_from_source.rst:2012 +msgid "" +"Link to static external ZLIB directory. Only used if " +"GDAL_USE_ZLIB_INTERNAL=OFF and MSVC." +msgstr "" + +#: ../../source/development/building_from_source.rst:2017 +msgid "Control whether to use ZLIB. Defaults to ON when ZLIB is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:2021 +msgid "" +"Control whether to use internal zlib copy. Defaults depends on " +"GDAL_USE_INTERNAL_LIBS. When set to ON, has precedence over " +"GDAL_USE_ZLIB=ON" +msgstr "" + +#: ../../source/development/building_from_source.rst:2026 +msgid "ZSTD" +msgstr "" + +#: ../../source/development/building_from_source.rst:2028 +msgid "" +"`ZSTD <https://github.com/facebook/zstd>`_ is a compression library which" +" offers the lossless ZStd compression algorithm (faster than Deflate/ZIP," +" but incompatible with it). It is used by the internal libtiff library or" +" the :ref:`raster.zarr` driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:2034 +msgid "Path to an include directory with the ``zstd.h`` header file." +msgstr "" + +#: ../../source/development/building_from_source.rst:2042 +msgid "Control whether to use ZSTD. Defaults to ON when ZSTD is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:2048 +msgid "Selection of drivers" +msgstr "" + +#: ../../source/development/building_from_source.rst:2050 +msgid "" +"By default, all drivers that have their build requirements satisfied will" +" be built-in in the GDAL core library." +msgstr "" + +#: ../../source/development/building_from_source.rst:2053 +msgid "The following options are available to select a subset of drivers:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2059 +#: ../../source/development/building_from_source.rst:2198 +msgid "" +"Independently of options that control global behavior, drivers can be " +"individually enabled or disabled with those options." +msgstr "" + +#: ../../source/development/building_from_source.rst:2064 +msgid "" +"<driver_name> above and below is *generally*, but not systematically the " +"short driver name." +msgstr "" + +#: ../../source/development/building_from_source.rst:2066 +msgid "Some drivers may also be grouped together for build purposes." +msgstr "" + +#: ../../source/development/building_from_source.rst:2068 +msgid "" +"A number of \"raw\" raster drivers (ACE2, BT, BYN, CPG, CTable2, DIPEx, " +"DOQ1, DOQ2, EHDR, EIR, ENVI, FAST, GenBIN, GSC, GTX, MFF2, ISCE, KRO, " +"MFF, LAN, LCP, LOSLAS, NDF, NTv2, PAUX, PNM, ROIPAC, RRASTER, SNODAS) are" +" controlled by the GDAL_ENABLE_DRIVER_RAW option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2073 +msgid "" +"Planetary raster formats (PDS, PDS4, ISIS2, ISIS3, VICAR) are controlled " +"by the GDAL_ENABLE_DRIVER_PDS option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2076 +msgid "" +"The AAIGRID, GRASSASCIIGRID and ISG raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_AAIGRID option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2078 +msgid "" +"The ECW and JP2ECW raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_ECW option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2080 +msgid "" +"The vector EEDA and raster EEDAI drivers are controlled by the " +"GDAL_ENABLE_DRIVER_EEDA option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2082 +msgid "" +"The GSAG, GSBG and GS7BG raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_GSG option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2084 +msgid "" +"The HDF5 and BAG raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_HDF5 option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2086 +msgid "" +"The MrSID and JP2MrSID raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_MRSID option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2088 +msgid "" +"The NITF, RPFTOC and ECRGTOC raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_NITF option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2090 +msgid "" +"The NWT_GRD and NWT_GRC raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_NORTHWOOD option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2092 +msgid "" +"The SRP and ADRG raster drivers are controlled by the " +"GDAL_ENABLE_DRIVER_ADRG option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2094 +msgid "" +"The Interlis 1 and Interlis 2 vector drivers are controlled by the " +"GDAL_ENABLE_DRIVER_ILI option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2096 +msgid "" +"The WFS and OAPIF vector drivers are controlled by the " +"GDAL_ENABLE_DRIVER_WFS option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2098 +msgid "" +"The AVCBIN and AVCE00 vector drivers are controlled by the " +"GDAL_ENABLE_DRIVER_AVC option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2100 +msgid "" +"The DWG and DGNv8 vector drivers are controlled by the " +"GDAL_ENABLE_DRIVER_DWG option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2102 +msgid "There might be variations in naming, e.g. :" +msgstr "" + +#: ../../source/development/building_from_source.rst:2104 +msgid "the \"AIG\" raster driver is controlled by GDAL_ENABLE_DRIVER_AIGRID." +msgstr "" + +#: ../../source/development/building_from_source.rst:2106 +msgid "the \"ESAT\" raster driver is controlled by GDAL_ENABLE_DRIVER_ENVISAT." +msgstr "" + +#: ../../source/development/building_from_source.rst:2108 +msgid "the \"GeoRaster\" raster driver is controlled by GDAL_ENABLE_DRIVER_GEOR." +msgstr "" + +#: ../../source/development/building_from_source.rst:2110 +msgid "the \"RST\" raster driver is controlled by GDAL_ENABLE_DRIVER_IDRISI." +msgstr "" + +#: ../../source/development/building_from_source.rst:2112 +msgid "" +"the \"ElasticSearch\" vector driver is controlled by " +"OGR_ENABLE_DRIVER_ELASTIC." +msgstr "" + +#: ../../source/development/building_from_source.rst:2114 +msgid "the \"PostgreSQL\" vector driver is controlled by OGR_ENABLE_DRIVER_PG." +msgstr "" + +#: ../../source/development/building_from_source.rst:2116 +msgid "the \"UK .NTF\" vector driver is controlled by OGR_ENABLE_DRIVER_NTF." +msgstr "" + +#: ../../source/development/building_from_source.rst:2120 +msgid "" +"Drivers that have both a raster and vector side (and are internally " +"implemented by a single GDALDriver instance) are controlled by either a " +"GDAL_ENABLE_DRIVER_<driver_name> option or a " +"OGR_ENABLE_DRIVER_<driver_name> one, but not both:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2124 +msgid "The CAD drivers are controlled by the OGR_ENABLE_DRIVER_CAD option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2125 +msgid "The netCDF drivers are controlled by the GDAL_ENABLE_DRIVER_NETCDF option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2126 +msgid "The PDF drivers are controlled by the GDAL_ENABLE_DRIVER_PDF option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2127 +msgid "The GPKG drivers are controlled by the OGR_ENABLE_DRIVER_GPKG option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2128 +msgid "The NGW drivers are controlled by the OGR_ENABLE_DRIVER_NGW option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2129 +msgid "The SQLite drivers are controlled by the OGR_ENABLE_DRIVER_SQLITE option." +msgstr "" + +#: ../../source/development/building_from_source.rst:2133 +msgid "" +"The GDAL_ENABLE_DRIVER_<driver_name> and OGR_ENABLE_DRIVER_<driver_name> " +"options are only created when their required dependencies are found." +msgstr "" + +#: ../../source/development/building_from_source.rst:2141 +msgid "" +"Globally enable/disable all optional GDAL/raster, resp. all optional " +"OGR/vector drivers. More exactly, setting those variables to ON affect " +"the default value of the ``GDAL_ENABLE_DRIVER_<driver_name>`` or " +"``OGR_ENABLE_DRIVER_<driver_name>`` variables (when they are not yet " +"set)." +msgstr "" + +#: ../../source/development/building_from_source.rst:2146 +msgid "" +"This can be combined with individual activation of a subset of drivers by" +" using the ``GDAL_ENABLE_DRIVER_<driver_name>:BOOL=ON`` or " +"``OGR_ENABLE_DRIVER_<driver_name>:BOOL=ON`` variables. Note that changing" +" the value of GDAL_BUILD_OPTIONAL_DRIVERS/ OGR_BUILD_OPTIONAL_DRIVERS " +"after a first run of CMake does not change the activation of individual " +"drivers. It might be needed to pass ``-UGDAL_ENABLE_DRIVER_* " +"-UOGR_ENABLE_DRIVER_*`` to reset their state." +msgstr "" + +#: ../../source/development/building_from_source.rst:2155 +msgid "" +"The following GDAL drivers cannot be disabled: VRT, DERIVED, GTiff, COG, " +"HFA, MEM. The following OGR drivers cannot be disabled: \"ESRI " +"Shapefile\", \"MapInfo File\", OGR_VRT, Memory, KML, GeoJSON, GeoJSONSeq," +" ESRIJSON, TopoJSON." +msgstr "" + +#: ../../source/development/building_from_source.rst:2160 +msgid "" +"Disabling all OGR/vector drivers with -DOGR_BUILD_OPTIONAL_DRIVERS=OFF " +"may affect the ability to enable some GDAL/raster drivers that require " +"some vector drivers to be enabled (and reciprocally with some GDAL/raster" +" drivers depending on vector drivers). When such dependencies are not " +"met, a CMake error will be emitted with a hint for the way to resolve the" +" issue. It is also possible to anticipate such errors by looking at files" +" :source_file:`frmts/CMakeLists.txt` for dependencies of raster drivers " +"and :source_file:`ogr/ogrsf_frmts/CMakeLists.txt` for dependencies of " +"vector drivers." +msgstr "" + +#: ../../source/development/building_from_source.rst:2171 +msgid "Example of minimal build with the JP2OpenJPEG and SVG drivers enabled::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2179 +msgid "Build drivers as plugins" +msgstr "" + +#: ../../source/development/building_from_source.rst:2181 +msgid "" +"An important subset, but not all, drivers can be also built as plugin, " +"that is to say as standalone .dll/.so shared libraries, to be installed " +"in the ``gdalplugins`` subdirectory of the GDAL installation. This can be" +" useful in particular for drivers that depend on libraries that have a " +"license different (proprietary, copyleft, ...) from the core GDAL " +"library." +msgstr "" + +#: ../../source/development/building_from_source.rst:2187 +msgid "The list of drivers that can be built as plugins can be obtained with::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2191 +msgid "" +"The following options are available to select the plugin/builtin status " +"of a driver:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2201 +msgid "" +"Note that for the driver to be built, the corresponding base " +"``GDAL_ENABLE_DRIVER_{driver_name}:BOOL=ON`` or " +"``OGR_ENABLE_DRIVER_{driver_name}:BOOL=ON`` option must be set." +msgstr "" + +#: ../../source/development/building_from_source.rst:2207 +msgid "" +"Globally enable/disable building all (plugin capable), GDAL and OGR, " +"drivers as plugins. More exactly, setting that variable to ON affects the" +" default value of the ``GDAL_ENABLE_DRIVER_<driver_name>_PLUGIN`` or " +"``OGR_ENABLE_DRIVER_<driver_name>_PLUGIN`` variables (when they are not " +"yet set)." +msgstr "" + +#: ../../source/development/building_from_source.rst:2212 +msgid "" +"This can be combined with individual activation/deactivation of the " +"plugin status with the ``GDAL_ENABLE_DRIVER_{driver_name}_PLUGIN:BOOL`` " +"or ``OGR_ENABLE_DRIVER_{driver_name}_PLUGIN:BOOL`` variables. Note that " +"changing the value of GDAL_ENABLE_PLUGINS after a first run of CMake does" +" not change the activation of the plugin status of individual drivers. It" +" might be needed to pass ``-UGDAL_ENABLE_DRIVER_* -UOGR_ENABLE_DRIVER_*``" +" to reset their state." +msgstr "" + +#: ../../source/development/building_from_source.rst:2218 +msgid "" +"Example of build with all potential drivers as plugins, except the " +"JP2OpenJPEG one::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2224 +msgid "" +"There is a subtelty regarding ``GDAL_ENABLE_PLUGINS:BOOL=ON``. It only " +"controls the plugin status of plugin-capable drivers that have external " +"dependencies, that are not part of GDAL core dependencies (e.g. are " +"netCDF, HDF4, Oracle, PDF, etc.)." +msgstr "" + +#: ../../source/development/building_from_source.rst:2230 +msgid "" +"Globally enable/disable building all (plugin capable), GDAL and OGR, " +"drivers as plugins, for drivers that have no external dependencies (e.g. " +"BMP, FlatGeobuf), or that have dependencies that are part of GDAL core " +"dependencies (e.g GPX). Building such drivers as plugins is generally not" +" necessary, hence the use of a different option from GDAL_ENABLE_PLUGINS." +msgstr "" + +#: ../../source/development/building_from_source.rst:2236 +msgid "" +"In some circumstances, it might be desirable to prevent loading of GDAL " +"plugins. This can be done with:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2241 +msgid "Set to OFF to disable loading of GDAL plugins. Default is ON." +msgstr "" + +#: ../../source/development/building_from_source.rst:2245 +msgid "Deferred loaded plugins" +msgstr "" + +#: ../../source/development/building_from_source.rst:2247 +msgid "" +"Starting with GDAL 3.9, a number of in-tree drivers, that can be built as" +" plugins, are loaded in a deferred way. This involves that some part of " +"their code, which does not depend on external libraries, is included in " +"core libgdal, whereas most of the driver code is in a separated " +"dynamically loaded library. For builds where libgdal and its plugins are " +"built in a single operation, this is fully transparent to the user." +msgstr "" + +#: ../../source/development/building_from_source.rst:2254 +msgid "" +"When a plugin driver is known of core libgdal, but not available as a " +"plugin at runtime, GDAL will inform the user that the plugin is not " +"available, but could be installed. It is possible to give more hints on " +"how to install a plugin by setting the following option:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2263 +msgid "Custom message to give a hint to the user how to install a missing plugin" +msgstr "" + +#: ../../source/development/building_from_source.rst:2266 +msgid "For example, if doing a build with::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2270 +msgid "" +"and opening a Parquet file while the plugin is not installed will display" +" the following error::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2277 +msgid "" +"For more specific builds where libgdal would be first built, and then " +"plugin drivers built in later incremental builds, this approach would not" +" work, given that the core libgdal built initially would lack code needed" +" to declare the plugin(s)." +msgstr "" + +#: ../../source/development/building_from_source.rst:2282 +msgid "" +"In that situation, the user building GDAL will need to explicitly declare" +" at initial libgdal build time that one or several plugin(s) will be " +"later built. Note that it is safe to distribute such a libgdal library, " +"even if the plugins are not always available at runtime." +msgstr "" + +#: ../../source/development/building_from_source.rst:2287 +#: ../../source/development/building_from_source.rst:2329 +msgid "This can be done with the following option:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2293 +msgid "Declares that a driver will be later built as a plugin." +msgstr "" + +#: ../../source/development/building_from_source.rst:2295 +msgid "" +"Setting this option to drivers not ready for it will lead to an explicit " +"CMake error." +msgstr "" + +#: ../../source/development/building_from_source.rst:2299 +msgid "" +"For some drivers (ECW, HEIF, JP2KAK, JPEG, JPEGXL, KEA, LERC, MrSID, " +"MSSQLSpatial, netCDF, OpenJPEG, PDF, TileDB, WEBP), the metadata and/or " +"dataset identification code embedded on libgdal, will depend on optional " +"capabilities of the dependent library (e.g. libnetcdf for netCDF) In that" +" situation, it is desirable that the dependent library is available at " +"CMake configuration time for the core libgdal built, but disabled with " +"GDAL_USE_<driver_name>=OFF. It must of course be re-enabled later when " +"the plugin is built." +msgstr "" + +#: ../../source/development/building_from_source.rst:2308 +msgid "For example for netCDF::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2317 +msgid "" +"For other drivers, GDAL_REGISTER_DRIVER_<driver_name>_FOR_LATER_PLUGIN / " +"OGR_REGISTER_DRIVER_<driver_name>_FOR_LATER_PLUGIN can be declared at " +"libgdal build time without requiring the dependent libraries needed to " +"build the plugin later to be available." +msgstr "" + +#: ../../source/development/building_from_source.rst:2323 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:315 +msgid "Out-of-tree deferred loaded plugins" +msgstr "" + +#: ../../source/development/building_from_source.rst:2325 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:317 +msgid "" +"Out-of-tree drivers can also benefit from the deferred loading " +"capability, provided libgdal is built with CMake variable(s) pointing to " +"external code containing the code for registering a proxy driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:2333 +msgid "" +"The pointed file must declare a ``void " +"DeclareDeferred<driver_name>(void)`` method with C linkage that takes " +"care of creating a GDALPluginDriverProxy instance and calling " +":cpp:func:`GDALDriverManager::DeclareDeferredPluginDriver` on it." +msgstr "" + +#: ../../source/development/building_from_source.rst:2340 +msgid "Python bindings options" +msgstr "" + +#: ../../source/development/building_from_source.rst:2344 +msgid "" +"Whether Python bindings should be built. It is ON by default, but only " +"effective if a Python installation is found." +msgstr "" + +#: ../../source/development/building_from_source.rst:2347 +msgid "" +"A nominal Python installation should comprise the Python runtime (>= 3.6)" +" and the setuptools module. numpy and its header and development library " +"are also strongly recommended." +msgstr "" + +#: ../../source/development/building_from_source.rst:2351 +msgid "" +"The Python installation is normally found if found in the path or " +"registered through other standard installation mechanisms of the Python " +"installers. It is also possible to specify it using several variables, as" +" detailed in https://cmake.org/cmake/help/git-" +"stage/module/FindPython.html" +msgstr "" + +#: ../../source/development/building_from_source.rst:2356 +msgid "GDAL also provides the following option:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2360 +msgid "" +"When it is specified, Python_FIND_STRATEGY=VERSION is assumed. Note that " +"the patch number must be provided, as the EXACT strategy is used" +msgstr "" + +#: ../../source/development/building_from_source.rst:2363 +msgid "Other useful options:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2367 +msgid "Specify 'ONLY' to use virtualenv activated." +msgstr "" + +#: ../../source/development/building_from_source.rst:2371 +msgid "Specify Python installation prefix." +msgstr "" + +#: ../../source/development/building_from_source.rst:2373 +msgid "Examples::" +msgstr "" + +#: ../../source/development/building_from_source.rst:2380 +msgid "" +"The following options are advanced ones and only taken into account " +"during the ``install`` CMake target." +msgstr "" + +#: ../../source/development/building_from_source.rst:2385 +msgid "" +"This option can be specified to a directory name, to override the " +"``CMAKE_INSTALL_PREFIX`` option. It is used to set the value of the " +"``--prefix`` option of ``python3 setup.py install``." +msgstr "" + +#: ../../source/development/building_from_source.rst:2391 +msgid "" +"This option can be specified to set the value of the ``--install-layout``" +" option of ``python3 setup.py install``. The install layout is by default" +" set to ``deb`` when it is detected that the Python installation looks " +"for the ``site-packages`` subdirectory. Otherwise it is unspecified." +msgstr "" + +#: ../../source/development/building_from_source.rst:2398 +msgid "" +"This option can be specified to set the value of the ``--install-lib`` " +"option of ``python3 setup.py install``. It is only taken into account on " +"MacOS systems, when the Python installation is a framework." +msgstr "" + +#: ../../source/development/building_from_source.rst:2404 +msgid "" +"The Python bindings are made of several modules (osgeo.gdal, osgeo.ogr, " +"etc.) which link each against libgdal. Consequently, a static build of " +"libgdal is not compatible with the bindings." +msgstr "" + +#: ../../source/development/building_from_source.rst:2411 +msgid "Java bindings options" +msgstr "" + +#: ../../source/development/building_from_source.rst:2415 +msgid "" +"Whether Java bindings should be built. It is ON by default, but only " +"effective if Java runtime and development packages are found. The " +"relevant options that can be set are described in " +"https://cmake.org/cmake/help/latest/module/FindJava.html and " +"https://cmake.org/cmake/help/latest/module/FindJNI.html. The ``ant`` " +"binary must also be available in the PATH." +msgstr "" + +#: ../../source/development/building_from_source.rst:2424 +msgid "" +"Subdirectory into which to install the :file:`gdal.jar` file. It defaults" +" to \"${CMAKE_INSTALL_DATADIR}/java\"" +msgstr "" + +#: ../../source/development/building_from_source.rst:2428 +msgid "" +"Prior to GDAL 3.8, the gdalalljni library was also installed in that " +"directory. Starting with GDAL 3.8, this is controlled by the " +"``GDAL_JAVA_JNI_INSTALL_DIR`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:2436 +msgid "" +"Subdirectory into which to install the :file:`libgdalalljni.so` / " +":file:`libgdalalljni.dylib` / :file:`gdalalljni.dll` library. It defaults" +" to \"${CMAKE_INSTALL_LIBDIR}/jni\"." +msgstr "" + +#: ../../source/development/building_from_source.rst:2441 +msgid "" +"Prior to GDAL 3.8, the gdalalljni library was installed in the directory " +"controlled by the ``GDAL_JAVA_INSTALL_DIR`` variable." +msgstr "" + +#: ../../source/development/building_from_source.rst:2447 +msgid "" +"The Java bindings are made of several modules (org.osgeo.gdal, " +"org.osgeo.ogr, etc.) which link each against libgdal. Consequently, a " +"static build of libgdal is not compatible with the bindings." +msgstr "" + +#: ../../source/development/building_from_source.rst:2451 +msgid "Option only to be used by maintainers:" +msgstr "" + +#: ../../source/development/building_from_source.rst:2455 +msgid "GPG key to sign build artifacts. Needed to generate bundle.jar." +msgstr "" + +#: ../../source/development/building_from_source.rst:2459 +msgid "GPG pass phrase to sign build artifacts." +msgstr "" + +#: ../../source/development/building_from_source.rst:2462 +msgid "C# bindings options" +msgstr "" + +#: ../../source/development/building_from_source.rst:2464 +msgid "" +"For more details on how to build and use the C# bindings read the " +"dedicated section :ref:`csharp_compile_cmake`." +msgstr "" + +#: ../../source/development/building_from_source.rst:2468 +msgid "" +"Whether C# bindings should be built. It is ON by default, but only " +"effective if C# runtime and development packages are found. Either .NET " +"SDK can be used or Mono. The relevant options that can be set are " +"described in ``cmake/modules/thirdparty/FindDotNetFrameworkSdk.cmake`` " +"and ``cmake/modules/thirdparty/FindMono.cmake``." +msgstr "" + +#: ../../source/development/building_from_source.rst:2476 +msgid "Forces the use of Mono as opposed to .NET to compile the C# bindings." +msgstr "" + +#: ../../source/development/building_from_source.rst:2480 +msgid "" +"Sets the .NET (or Mono) target SDK to be used when compiling the C# " +"binding libraries. `List of acceptable contents for .NET " +"<https://docs.microsoft.com/en-us/dotnet/standard/frameworks#supported-" +"target-frameworks>`_" +msgstr "" + +#: ../../source/development/building_from_source.rst:2484 +msgid "" +"Sets the .NET (or Mono) target SDK to be used when compiling the C# " +"sample applications. `List of acceptable contents for .NET " +"<https://docs.microsoft.com/en-us/dotnet/standard/frameworks#supported-" +"target-frameworks>`_" +msgstr "" + +#: ../../source/development/building_from_source.rst:2488 +msgid "" +"Build the C# bindings without building GDAL. This should be used when " +"building the bindings on top of an existing GDAL installation - for " +"instance on top of the CONDA package." +msgstr "" + +#: ../../source/development/building_from_source.rst:2492 +msgid "" +"The C# bindings are made of several modules (OSGeo.GDAL, OSGeo.OGR, etc.)" +" which link each against libgdal. Consequently, a static build of libgdal" +" is not compatible with the bindings." +msgstr "" + +#: ../../source/development/building_from_source.rst:2497 +msgid "Driver specific options" +msgstr "" + +#: ../../source/development/building_from_source.rst:2501 +msgid "" +"The :ref:`raster.msg` driver is built only if this option is set to ON " +"(default is OFF). Its effect is to download the " +"https://gitlab.eumetsat.int/open-source/PublicDecompWT.git repository " +"(requires the ``git`` binary to be available at configuration time) into " +"the build tree and build the needed files from it into the driver." +msgstr "" + +#: ../../source/development/building_from_source.rst:2508 +msgid "Cross-compiling for Android" +msgstr "" + +#: ../../source/development/building_from_source.rst:2510 +msgid "" +"First refer to https://cmake.org/cmake/help/latest/manual/cmake-" +"toolchains.7.html#cross-compiling-for-android and to " +":source_file:`.github/workflows/android_cmake/start.sh` for an example of" +" a build script to cross-compile from Ubuntu." +msgstr "" + +#: ../../source/development/building_from_source.rst:2516 +msgid "Typical build issues" +msgstr "" + +#: ../../source/development/building_from_source.rst:2519 +msgid "How do I get PROJ ?" +msgstr "" + +#: ../../source/development/building_from_source.rst:2521 +msgid "" +"PROJ is the only required build-time dependency of GDAL that is not " +"vendorized in the GDAL source code tree. Consequently, the PROJ header " +"and library must be available when configuring GDAL's CMake. Consult " +"`PROJ installation <https://proj.org/install.html>`__." +msgstr "" + +#: ../../source/development/building_from_source.rst:2526 +msgid "Conflicting PROJ libraries" +msgstr "" + +#: ../../source/development/building_from_source.rst:2528 +msgid "" +"If using a custom PROJ build (that is a PROJ build that does not come " +"from a distribution channel), it can sometimes happen that this custom " +"PROJ build conflicts with packaged dependencies, such as spatialite or " +"libgeotiff, that themselves link to another copy of PROJ." +msgstr "" + +#: ../../source/development/building_from_source.rst:2533 +msgid "" +"The clean way to solve this is to rebuild from sources those other " +"libraries against the custom PROJ build. For Linux based systems, given " +"that C API/ABI has been preserved in the PROJ 6, 7, 8, 9 series, if the " +"custom PROJ build is more recent than the PROJ used by those other " +"libraries, doing aliases of the older ``libproj.so.XX`` name to the newer" +" ``libproj.so.YY`` (with ``ln -s``) should work, although it is " +"definitely not recommended to use this solution in a production " +"environment." +msgstr "" + +#: ../../source/development/building_from_source.rst:2541 +msgid "" +"In any case, if ``ldd libgdal.so | grep libproj`` reports more than one " +"line, crashes will occur at runtime (often at process termination with a " +"``malloc_consolidate(): invalid chunk size`` and/or ``Aborted (core " +"dumped)`` error message)" +msgstr "" + +#: ../../source/development/building_from_source.rst:2547 +msgid "Autoconf/nmake (GDAL versions < 3.5.0)" +msgstr "" + +#: ../../source/development/building_from_source.rst:2549 +msgid "" +"See https://trac.osgeo.org/gdal/wiki/BuildHints for hints for GDAL < 3.5 " +"autoconf and nmake build systems." +msgstr "" + +#: ../../source/development/cmake.rst:5 +msgid "Using GDAL in CMake projects" +msgstr "" + +#: ../../source/development/cmake.rst:9 +msgid "" +"The recommended way to use the GDAL library 3.5 or higher in a CMake " +"project is to link to the imported library target ``GDAL::GDAL`` provided" +" by the CMake configuration which comes with the library. Typical usage " +"is:" +msgstr "" + +#: ../../source/development/cmake.rst:19 +msgid "" +"By adding the imported library target ``GDAL::GDAL`` to the target link " +"libraries, CMake will also pass the include directories to the compiler." +msgstr "" + +#: ../../source/development/cmake.rst:23 +msgid "" +"The CMake command ``find_package`` will look for the configuration in a " +"number of places. The lookup can be adjusted for all packages by setting " +"the cache variable or environment variable ``CMAKE_PREFIX_PATH``. In " +"particular, CMake will consult (and set) the cache variable ``GDAL_DIR``." +msgstr "" + +#: ../../source/development/cmake.rst:29 +msgid "" +"Before GDAL 3.5, it is recommended to use `find module supplied with " +"CMake <https://cmake.org/cmake/help/latest/module/FindGDAL.html>`__. This" +" also creates the ``GDAL::GDAL`` target. It requires CMake version 3.14." +msgstr "" + +#: ../../source/development/dev_documentation.rst:5 +#: ../../source/development/dev_documentation.rst:20 +msgid "Building documentation" +msgstr "" + +#: ../../source/development/dev_documentation.rst:8 +msgid "Documentation overview" +msgstr "" + +#: ../../source/development/dev_documentation.rst:10 +msgid "" +"GDAL's documentation includes C and C++ :ref:`API documentation <api>` " +"built automatically from source comments using Doxygen and " +"reStructuredText (rst) files containing manually-edited content." +msgstr "" + +#: ../../source/development/dev_documentation.rst:14 +msgid "" +"|Sphinx| is used to combine the above components into a complete set of " +"documentation in HTML, PDF, and other formats." +msgstr "" + +#: ../../source/development/dev_documentation.rst:16 +msgid "" +"|Sphinx| and extensions used by GDAL can be installed by running " +"``python3 -m pip install -r requirements.txt`` from the ``doc`` " +"subdirectory." +msgstr "" + +#: ../../source/development/dev_documentation.rst:22 +msgid "" +"Documentation can be generated with Makefile targets, from the ``doc`` " +"subdirectory of the GDAL source repository (only on Unix systems)." +msgstr "" + +#: ../../source/development/dev_documentation.rst:25 +msgid "The following targets are available:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:27 +msgid "" +"``html``: build HTML documentation into the ``doc/build/html`` directory," +" where they can be viewed using a web browser." +msgstr "" + +#: ../../source/development/dev_documentation.rst:30 +msgid "``man``: build MAN pages into the ``doc/build/man`` directory." +msgstr "" + +#: ../../source/development/dev_documentation.rst:32 +msgid "``latexpdf``: build PDF documentation into the ``doc/build/pdf`` directory" +msgstr "" + +#: ../../source/development/dev_documentation.rst:34 +msgid "" +"``doxygen``: regenerate API Doxygen XML and HTML output, that is used by " +"the ``html`` target. Doxygen content is not automatically rebuilt when " +"source files are modified, hence this target must be explicitly run to " +"refresh it." +msgstr "" + +#: ../../source/development/dev_documentation.rst:38 +msgid "" +"``doxygen_check_warnings``: same as ``doxygen``, but errors out when " +"Doxygen emits a warning (the ``doxygen`` target is tolerant to Doxygen " +"warnings). This can be useful to reproduce one of the continuous " +"integration checks that verifies that there are no Doxygen warnings. " +"Requires Doxygen >= 1.9.3 to be warning free." +msgstr "" + +#: ../../source/development/dev_documentation.rst:44 +msgid "``clean``: clean the ``doc/build`` directory." +msgstr "" + +#: ../../source/development/dev_documentation.rst:46 +msgid "" +"It is also possible to run those targets as CMake targets. In that case, " +"the output directory will be the ``doc/build`` subdirectory of the CMake " +"build directory. To only clean the documentation, the ``clean_doc`` " +"target can be invoked. Note: those CMake targets are only available if " +"the CMake BUILD_DOCS=ON variable is set (it is set by default if build " +"preconditions are met, that is if Doxygen, Sphinx and make are available)" +msgstr "" + +#: ../../source/development/dev_documentation.rst:54 +msgid "" +"To visualize documentation changes while editing, it may be useful to " +"install the |sphinx-autobuild| python package. Once installed, running " +"``sphinx-autobuild -b html source build`` from the ``doc`` subdirectory " +"will build documentation and serve it on a local web server at " +"``http://127.0.0.1:8000``. The pages served will be automatically " +"refreshed as changes are made to underlying ``rst`` documentation files." +msgstr "" + +#: ../../source/development/dev_documentation.rst:60 +msgid "Python API documentation" +msgstr "" + +#: ../../source/development/dev_documentation.rst:62 +msgid "" +"Sphinx uses the `autodoc <https://www.sphinx-" +"doc.org/en/master/usage/extensions/autodoc.html>`_ extension to generate " +"documentation for the Python API from Python function docstrings. To be " +"correctly parsed by ``autodoc``, docstrings should follow the `numpydoc " +"Style guide <https://numpydoc.readthedocs.io/en/latest/format.html>`_. " +"Docstrings may be found in two locations. If the function was defined in " +"Python (i.e., using a ``%pythoncode`` SWIG directive), then the docstring" +" must be placed within the function definition. If the function is " +"defined in C++ only, then the docstring should be placed in a separate " +"file containing only docstrings (located in " +":source_file:`swig/include/python/docs`). Sphinx loads the Python " +"bindings when generating documentation, so for it to see any changes the " +"following steps must be completed:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:73 +msgid "" +"rebuild the Python bindings from the build directory (``cmake --build . " +"--target python_binding``)" +msgstr "" + +#: ../../source/development/dev_documentation.rst:74 +msgid "" +"make the updated Python bindings visible to Python, either by installing " +"them, or by running ``scripts/setdevenv.sh`` from the build directory" +msgstr "" + +#: ../../source/development/dev_documentation.rst:76 +msgid "" +"update the timestamp of the ``rst`` files associated with the page where " +"the documentation appears (e.g., ``touch " +"doc/source/api/python/osgeo.ogr.rst``)" +msgstr "" + +#: ../../source/development/dev_documentation.rst:82 +msgid "Sphinx RST Style guide" +msgstr "" + +#: ../../source/development/dev_documentation.rst:84 +msgid "" +"This section contains syntax rules, tips, and tricks for using Sphinx and" +" reStructuredText. For more information, please see this `comprehensive" +" guide to reStructuredText " +"<http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html>`_, " +"as well as the `Sphinx reStructuredText Primer " +"<http://sphinx.pocoo.org/rest.html>`_." +msgstr "" + +#: ../../source/development/dev_documentation.rst:87 +msgid "Basic markup" +msgstr "" + +#: ../../source/development/dev_documentation.rst:89 +msgid "" +"A reStructuredText document is written in plain text. Without the need " +"for complex formatting, one can be composed simply, just like one would " +"any plain text document. For basic formatting, see this table:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:95 +msgid "**Format**" +msgstr "" + +#: ../../source/development/dev_documentation.rst:96 +msgid "**Syntax**" +msgstr "" + +#: ../../source/development/dev_documentation.rst:97 +msgid "**Output**" +msgstr "" + +#: ../../source/development/dev_documentation.rst:98 +msgid "Italics" +msgstr "" + +#: ../../source/development/dev_documentation.rst:99 +msgid "``*italics*`` (single asterisk)" +msgstr "" + +#: ../../source/development/dev_documentation.rst:100 +msgid "*italics*" +msgstr "" + +#: ../../source/development/dev_documentation.rst:101 +msgid "Bold" +msgstr "" + +#: ../../source/development/dev_documentation.rst:102 +msgid "``**bold**`` (double asterisk)" +msgstr "" + +#: ../../source/development/dev_documentation.rst:103 +msgid "**bold**" +msgstr "" + +#: ../../source/development/dev_documentation.rst:104 +msgid "Monospace" +msgstr "" + +#: ../../source/development/dev_documentation.rst:105 +msgid "`` ``monospace`` `` (double back quote)" +msgstr "" + +#: ../../source/development/dev_documentation.rst:106 +msgid "``monospace``" +msgstr "" + +#: ../../source/development/dev_documentation.rst:108 +msgid "" +"Use of basic markup is **not recommend**! Where possible use sphinx " +"inline directives (described below) to logically mark commands, " +"parameters, options, input, and files. By using directives consistently " +"these items can be styled appropriately." +msgstr "" + +#: ../../source/development/dev_documentation.rst:111 +msgid "Lists" +msgstr "" + +#: ../../source/development/dev_documentation.rst:113 +msgid "" +"There are two types of lists, bulleted lists and numbered lists. A " +"**bulleted list** looks like this:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:115 +msgid "An item" +msgstr "" + +#: ../../source/development/dev_documentation.rst:116 +msgid "Another item" +msgstr "" + +#: ../../source/development/dev_documentation.rst:117 +msgid "Yet another item" +msgstr "" + +#: ../../source/development/dev_documentation.rst:119 +#: ../../source/development/dev_documentation.rst:131 +msgid "This is accomplished with the following code::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:125 +msgid "A **numbered list** looks like this:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:127 +msgid "First item" +msgstr "" + +#: ../../source/development/dev_documentation.rst:128 +msgid "Second item" +msgstr "" + +#: ../../source/development/dev_documentation.rst:129 +msgid "Third item" +msgstr "" + +#: ../../source/development/dev_documentation.rst:137 +msgid "" +"Note that numbers are automatically generated, making it easy to " +"add/remove items." +msgstr "" + +#: ../../source/development/dev_documentation.rst:140 +msgid "List-tables" +msgstr "" + +#: ../../source/development/dev_documentation.rst:142 +msgid "" +"Bulleted lists can sometimes be cumbersome and hard to follow. When " +"dealing with a long list of items, use list-tables. For example, to talk" +" about a list of options, create a table that looks like this:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:148 +msgid "Shapes" +msgstr "" + +#: ../../source/development/dev_documentation.rst:149 +msgid "Description" +msgstr "" + +#: ../../source/development/dev_documentation.rst:150 +msgid "Square" +msgstr "" + +#: ../../source/development/dev_documentation.rst:151 +msgid "Four sides of equal length, 90 degree angles" +msgstr "" + +#: ../../source/development/dev_documentation.rst:152 +msgid "Rectangle" +msgstr "" + +#: ../../source/development/dev_documentation.rst:153 +msgid "Four sides, 90 degree angles" +msgstr "" + +#: ../../source/development/dev_documentation.rst:155 +msgid "This is done with the following code::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:169 +msgid "Page labels" +msgstr "" + +#: ../../source/development/dev_documentation.rst:171 +msgid "" +"**Ensure every page has a label that matches the name of the file.** For " +"example if the page is named ``foo_bar.rst`` then the page should have " +"the label::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:175 +msgid "Other pages can then link to that page by using the following code::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:182 +msgid "Linking" +msgstr "" + +#: ../../source/development/dev_documentation.rst:184 +msgid "" +"Links to other pages should never be titled as \"here\". Sphinx makes " +"this easy by automatically inserting the title of the linked document." +msgstr "" + +#: ../../source/development/dev_documentation.rst:186 +msgid "Bad" +msgstr "" + +#: ../../source/development/dev_documentation.rst:187 +msgid "More information about linking can be found :ref:`here <linking>`." +msgstr "" + +#: ../../source/development/dev_documentation.rst:189 +msgid "Good" +msgstr "" + +#: ../../source/development/dev_documentation.rst:189 +msgid "For more information, please see the section on :ref:`linking`." +msgstr "" + +#: ../../source/development/dev_documentation.rst:191 +msgid "To insert a link to an external website::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:195 +msgid "" +"The resulting link would look like this: `Text of the link " +"<http://example.com>`__" +msgstr "" + +#: ../../source/development/dev_documentation.rst:197 +msgid "" +"It is very easy to have two links with the same text resulting in the " +"following error::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:201 +msgid "To avoid these warnings use of a double `__` generates an anonymous link." +msgstr "" + +#: ../../source/development/dev_documentation.rst:205 +msgid "Sections" +msgstr "" + +#: ../../source/development/dev_documentation.rst:207 +msgid "" +"Use sections to break up long pages and to help Sphinx generate tables of" +" contents." +msgstr "" + +#: ../../source/development/dev_documentation.rst:228 +msgid "Notes and warnings" +msgstr "" + +#: ../../source/development/dev_documentation.rst:230 +msgid "" +"When it is beneficial to have a section of text stand out from the main " +"text, Sphinx has two such boxes, the note and the warning. They function" +" identically, and only differ in their coloring. You should use notes " +"and warnings sparingly, however, as adding emphasis to everything makes " +"the emphasis less effective." +msgstr "" + +#: ../../source/development/dev_documentation.rst:232 +msgid "Here is an example of a note:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:234 +msgid "This is a note." +msgstr "" + +#: ../../source/development/dev_documentation.rst:236 +msgid "This note is generated with the following code::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:240 +msgid "Similarly, here is an example of a warning:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:242 +msgid "Beware of dragons." +msgstr "" + +#: ../../source/development/dev_documentation.rst:244 +msgid "This warning is generated by the following code::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:249 +msgid "Images" +msgstr "" + +#: ../../source/development/dev_documentation.rst:251 +msgid "" +"Add images to your documentation when possible. Images, such as " +"screenshots, are a very helpful way of making documentation " +"understandable. When making screenshots, try to crop out unnecessary " +"content (browser window, desktop, etc). Avoid scaling the images, as the" +" Sphinx theme automatically resizes large images. It is also helpful to " +"include a caption underneath the image.::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:258 +msgid "" +"In this example, the image file exists in the same directory as the " +"source page. If this is not the case, you can insert path information in" +" the above command. The root :file:`/` is the directory of the " +":file:`conf.py` file.::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:263 +msgid "External files" +msgstr "" + +#: ../../source/development/dev_documentation.rst:265 +msgid "" +"Text snippets, large blocks of downloadable code, and even zip files or " +"other binary sources can all be included as part of the documentation." +msgstr "" + +#: ../../source/development/dev_documentation.rst:267 +msgid "To include link to sample file, use the ``download`` directive::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:271 +msgid "" +"The result of this code will generate a standard link to an " +":download:`external file <example.txt>`" +msgstr "" + +#: ../../source/development/dev_documentation.rst:273 +msgid "To include the contents of a file, use ``literalinclude`` directive::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:279 +msgid "Example of :command:`gdalinfo` use:" +msgstr "" + +#: ../../source/development/dev_documentation.rst:283 +msgid "" +"The ``literalinclude`` directive has options for syntax highlighting, " +"line numbers and extracting just a snippet::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:295 +msgid "Reference files and paths" +msgstr "" + +#: ../../source/development/dev_documentation.rst:297 +msgid "Use the following syntax to reference files and paths::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:301 +msgid "This will output: :file:`myfile.txt`." +msgstr "" + +#: ../../source/development/dev_documentation.rst:303 +msgid "You can reference paths in the same way::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:307 +msgid "This will output: :file:`path/to/myfile.txt`." +msgstr "" + +#: ../../source/development/dev_documentation.rst:309 +msgid "For Windows paths, use double backslashes::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:313 +msgid "This will output: :file:`C:\\\\myfile.txt`." +msgstr "" + +#: ../../source/development/dev_documentation.rst:315 +msgid "If you want to reference a non-specific path or file name::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:319 +msgid "This will output: :file:`{your/own/path/to}/myfile.txt`" +msgstr "" + +#: ../../source/development/dev_documentation.rst:321 +msgid "To reference a file in the GDAL source tree, use::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:325 +msgid "" +"This will output a link to the file on GitHub: " +":source_file:`gcore/gdaldriver.cpp`" +msgstr "" + +#: ../../source/development/dev_documentation.rst:328 +msgid "Reference code" +msgstr "" + +#: ../../source/development/dev_documentation.rst:330 +msgid "To reference a class::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:334 +msgid "To reference a method or function::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:342 +msgid "Define and reference configuration options" +msgstr "" + +#: ../../source/development/dev_documentation.rst:344 +msgid "To define a configuration option, use::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:353 +msgid "" +"Similar syntax can be used to define opening options (``.. oo::``), " +"creation options (``.. co::``), dataset creation options (``.. dsco::``)," +" or layer creation options (``.. lco::``)." +msgstr "" + +#: ../../source/development/dev_documentation.rst:357 +msgid "" +"To reference a configuration option, such as **GDAL_CACHEMAX**, use the " +"syntax in the table below." +msgstr "" + +#: ../../source/development/dev_documentation.rst:363 +msgid "Option type" +msgstr "" + +#: ../../source/development/dev_documentation.rst:364 +msgid "Syntax" +msgstr "" + +#: ../../source/development/dev_documentation.rst:365 +msgid "Configuration option" +msgstr "" + +#: ../../source/development/dev_documentation.rst:369 +msgid "Creation option" +msgstr "" + +#: ../../source/development/dev_documentation.rst:373 +msgid "Open option" +msgstr "" + +#: ../../source/development/dev_documentation.rst:377 +msgid "Dataset creation option" +msgstr "" + +#: ../../source/development/dev_documentation.rst:381 +msgid "Layer creation option" +msgstr "" + +#: ../../source/development/dev_documentation.rst:388 +msgid "Reference commands" +msgstr "" + +#: ../../source/development/dev_documentation.rst:390 +msgid "" +"Reference commands (such as :program:`gdalinfo`) with the following " +"syntax::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:394 +msgid "Use ``option`` directive for command line options::" +msgstr "" + +#: ../../source/development/dev_documentation.rst:400 +msgid "Use ``describe`` to document create parameters::" +msgstr "" + +#: ../../source/development/dev_environment.rst:5 +msgid "Setting up a development environment" +msgstr "" + +#: ../../source/development/dev_environment.rst:10 +msgid "See :ref:`build_requirements`" +msgstr "" + +#: ../../source/development/dev_environment.rst:13 +msgid "Vagrant" +msgstr "" + +#: ../../source/development/dev_environment.rst:15 +msgid "" +"`Vagrant <https://www.vagrantup.com>`_ is a tool that works with a " +"virtualization product such as VirtualBox to create a reproducible " +"development environment. GDAL includes a Vagrant configuration file that " +"sets up an Ubuntu virtual machine with a comprehensive set of " +"dependencies." +msgstr "" + +#: ../../source/development/dev_environment.rst:19 +msgid "" +"Once Vagrant has been installed and the GDAL source downloaded, the " +"virtual machine can be set up by running the following from the source " +"root directory:" +msgstr "" + +#: ../../source/development/dev_environment.rst:27 +msgid "" +"The source root directory is exposed inside the virtual machine at " +"``/vagrant``, so changes made to GDAL source files on the host are seen " +"inside the VM. To rebuild GDAL after changing source files, you can " +"connect to the VM and re-run the build command:" +msgstr "" + +#: ../../source/development/dev_environment.rst:36 +msgid "" +"Note that the following directories on the host will be created (and can " +"be removed if the Vagrant environment is no longer needed):" +msgstr "" + +#: ../../source/development/dev_environment.rst:39 +msgid "" +"``../apt-cache/ubuntu/jammy64``: contains a cache of Ubuntu packages of " +"the VM, to allow faster VM reconstruction" +msgstr "" + +#: ../../source/development/dev_environment.rst:41 +msgid "``build_vagrant``: CMake build directory" +msgstr "" + +#: ../../source/development/dev_environment.rst:42 +msgid "``ccache_vagrant``: CCache directory" +msgstr "" + +#: ../../source/development/dev_environment.rst:45 +msgid "Docker" +msgstr "" + +#: ../../source/development/dev_environment.rst:47 +msgid "" +"The Linux environments used for building and testing GDAL on GitHub " +"Actions are defined by Docker images that can be pulled to any machine " +"for development. The Docker image used for each build is specified in " +":source_file:`.github/workflows/linux_build.yml`. As an example, the " +"following commands can be run from the GDAL source root to build and test" +" GDAL using the clang address sanitizer (ASAN) in the same environment " +"that is used in GitHub Actions:" +msgstr "" + +#: ../../source/development/dev_environment.rst:65 +msgid "" +"To avoid built objects being owned by root, it may be desirable to add " +"``-u $(id -u):$(id -g) -v /etc/passwd:/etc/passwd`` to the ``docker run``" +" command above." +msgstr "" + +#: ../../source/development/dev_environment.rst:69 +msgid "Building on Windows with Conda dependencies and Visual Studio" +msgstr "" + +#: ../../source/development/dev_environment.rst:71 +msgid "" +"It is less appropriate for Debug builds of GDAL, than other methods, such" +" as using vcpkg." +msgstr "" + +#: ../../source/development/dev_environment.rst:74 +msgid "Install git" +msgstr "" + +#: ../../source/development/dev_environment.rst:76 +msgid "Install `git <https://git-scm.com/download/win>`_" +msgstr "" + +#: ../../source/development/dev_environment.rst:79 +msgid "Install miniconda" +msgstr "" + +#: ../../source/development/dev_environment.rst:81 +msgid "" +"Install `miniconda <https://repo.anaconda.com/miniconda/Miniconda3" +"-latest-Windows-x86_64.exe>`_" +msgstr "" + +#: ../../source/development/dev_environment.rst:84 +msgid "Install GDAL dependencies" +msgstr "" + +#: ../../source/development/dev_environment.rst:86 +msgid "Start a Conda enabled console and assuming there is a c:\\\\dev directory" +msgstr "" + +#: ../../source/development/dev_environment.rst:103 +msgid "" +"The ``compilers`` package will install ``vs2017_win-64`` (at time of " +"writing) to set the appropriate environment for cmake to pick up. It is " +"also possible to use the ``vs2019_win-64`` package if Visual Studio 2019 " +"is to be used." +msgstr "" + +#: ../../source/development/dev_environment.rst:108 +msgid "Checkout GDAL sources" +msgstr "" + +#: ../../source/development/dev_environment.rst:116 +msgid "Build GDAL" +msgstr "" + +#: ../../source/development/dev_environment.rst:118 +msgid "From a Conda enabled console" +msgstr "" + +#: ../../source/development/dev_environment.rst:132 +msgid "Run GDAL tests" +msgstr "" + +#: ../../source/development/dev_environment.rst:144 +msgid "Setting development environment variables" +msgstr "" + +#: ../../source/development/dev_environment.rst:146 +msgid "" +"Once GDAL has been built, a number of environment variables must be set " +"to be able to execute C++ or Python utilities of the build directory, or " +"run tests." +msgstr "" + +#: ../../source/development/dev_environment.rst:149 +msgid "This can be done by sourcing the following from the build directory:" +msgstr "" + +#: ../../source/development/dev_environment.rst:155 +msgid "" +"(with adjustments to the above path if the build directory is not a " +"subdirectory of the GDAL source root)." +msgstr "" + +#: ../../source/development/dev_environment.rst:157 +msgid "" +"For Windows, a similar ``scripts/setdevenv.bat`` script exists (it " +"currently assumes a Release build)." +msgstr "" + +#: ../../source/development/dev_environment.rst:159 +msgid "" +"To verify that environment variables have been set correctly, you can " +"check the version of a GDAL binary:" +msgstr "" + +#: ../../source/development/dev_environment.rst:166 +msgid "and the Python bindings:" +msgstr "" + +#: ../../source/development/dev_practices.rst:5 +msgid "Development practices" +msgstr "" + +#: ../../source/development/dev_practices.rst:8 +msgid "Making changes to GDAL" +msgstr "" + +#: ../../source/development/dev_practices.rst:10 +msgid "" +"Minor changes to GDAL, such as bug fixes, may be made by opening a GitHub" +" pull request." +msgstr "" + +#: ../../source/development/dev_practices.rst:12 +msgid "" +"Major changes should be discussed on the |gdal-dev| listserv and may " +"require the drafting of a RFC (request for comment) document." +msgstr "" + +#: ../../source/development/dev_practices.rst:15 +msgid "" +"GDAL's policy on substantial code additions is documented at " +":ref:`rfc-85`." +msgstr "" + +#: ../../source/development/dev_practices.rst:18 +#: ../../source/development/rfc/rfc45_virtualmem.rst:1045 +msgid "Portability" +msgstr "" + +#: ../../source/development/dev_practices.rst:20 +msgid "" +"GDAL strives to be widely portable to 32 bit and 64 bit computing " +"environments, as well as little-endian and big-endian ordered CPUs. CPL " +"functions in the port directory provide services to abstract platform " +"specific operations." +msgstr "" + +#: ../../source/development/dev_practices.rst:25 +msgid "" +"Generally speaking, where available CPL functions should be used in " +"preference to operating system functions for operations like memory " +"allocation, path parsing, filesystem I/O (using VSILFILE* / " +"VSIVirtualFile*), ODBC access, etc." +msgstr "" + +#: ../../source/development/dev_practices.rst:31 +msgid "C/C++ standards" +msgstr "" + +#: ../../source/development/dev_practices.rst:33 +msgid "" +"The current C and C++ standards adopted by GDAL/OGR are C99 and C++17 " +"(last updated per :ref:`rfc-98`)." +msgstr "" + +#: ../../source/development/dev_practices.rst:37 +msgid "Variable naming" +msgstr "" + +#: ../../source/development/dev_practices.rst:39 +msgid "" +"Much of the existing GDAL/OGR code uses an adapted Hungarian naming " +"convention. Use of this convention is not mandatory, but when maintaining" +" code using this convention it is desirable to continue adhering to it " +"with changes. Most importantly, please avoiding using it improperly as " +"that can be very confusing." +msgstr "" + +#: ../../source/development/dev_practices.rst:45 +msgid "" +"In Hungarian prefixing the prefix tells something about about the type, " +"and potentially semantics of a variable. The following are some prefixes " +"used in GDAL/OGR." +msgstr "" + +#: ../../source/development/dev_practices.rst:49 +msgid "*a*: array" +msgstr "" + +#: ../../source/development/dev_practices.rst:50 +msgid "" +"*b*: C/C++ bool. In C code that pre-dates C99 adoption, it is also used " +"for ints with only TRUE/FALSE values." +msgstr "" + +#: ../../source/development/dev_practices.rst:51 +msgid "*by*: byte (GByte / unsigned char)." +msgstr "" + +#: ../../source/development/dev_practices.rst:52 +msgid "*df*: floating point value (double precision)" +msgstr "" + +#: ../../source/development/dev_practices.rst:53 +msgid "*e*: enumeration" +msgstr "" + +#: ../../source/development/dev_practices.rst:54 +msgid "*i*: integer number used as a zero based array or loop index." +msgstr "" + +#: ../../source/development/dev_practices.rst:55 +msgid "*f*: floating point value (single precision)" +msgstr "" + +#: ../../source/development/dev_practices.rst:56 +msgid "*h*: an opaque handle (such as GDALDatasetH)." +msgstr "" + +#: ../../source/development/dev_practices.rst:57 +msgid "*n*: integer number (size unspecified)" +msgstr "" + +#: ../../source/development/dev_practices.rst:58 +msgid "*o*: C++ object" +msgstr "" + +#: ../../source/development/dev_practices.rst:59 +msgid "*os*: CPLString or std::string" +msgstr "" + +#: ../../source/development/dev_practices.rst:60 +msgid "*p*: pointer" +msgstr "" + +#: ../../source/development/dev_practices.rst:61 +msgid "*psz*: pointer to a null-terminated string. (eg. \"char \\*pszName;\")" +msgstr "" + +#: ../../source/development/dev_practices.rst:62 +msgid "*sz*: null-terminated string (eg.\" char szName[100];\")" +msgstr "" + +#: ../../source/development/dev_practices.rst:63 +msgid "*k*: compile-time constant" +msgstr "" + +#: ../../source/development/dev_practices.rst:65 +msgid "" +"Prefixes can be stacked. The following are some examples of meaningful " +"variables." +msgstr "" + +#: ../../source/development/dev_practices.rst:68 +msgid "\\*char !\\*\\ *papszTokens*: Pointer to an array of strings." +msgstr "" + +#: ../../source/development/dev_practices.rst:69 +msgid "\\*int *panBands*: Pointer to the first element of an array of numbers." +msgstr "" + +#: ../../source/development/dev_practices.rst:71 +msgid "" +"\\*double *padfScanline*: Pointer to the first element of an array of " +"doubles." +msgstr "" + +#: ../../source/development/dev_practices.rst:73 +msgid "\\*double *pdfMeanRet*: Pointer to a single double." +msgstr "" + +#: ../../source/development/dev_practices.rst:74 +msgid "\\*GDALRasterBand *poBand*: Pointer to a single object." +msgstr "" + +#: ../../source/development/dev_practices.rst:75 +msgid "\\*GByte *pabyHeader*: Pointer to an array of bytes." +msgstr "" + +#: ../../source/development/dev_practices.rst:77 +msgid "" +"It may also be noted that the standard convention for variable names is " +"to capitalize each word in a variable name." +msgstr "" + +#: ../../source/development/dev_practices.rst:81 +msgid "Function and class naming" +msgstr "" + +#: ../../source/development/dev_practices.rst:83 +msgid "" +"Functions and classes should have a selective enough namespace (\"GDAL\" " +"or \"OGR\" prefix, or use of C++ namespace) to avoid symbol collision." +msgstr "" + +#: ../../source/development/dev_practices.rst:86 +msgid "File naming and code formatting" +msgstr "" + +#: ../../source/development/dev_practices.rst:88 +msgid "" +"All source files (.h, .c, .cpp, .py, etc.) should have a header with " +"copyright attribution and the text of the GDAL X/MIT license." +msgstr "" + +#: ../../source/development/dev_practices.rst:89 +msgid "Use lower case filenames." +msgstr "" + +#: ../../source/development/dev_practices.rst:90 +msgid "Use .cpp extension for C++ files (not .cc)." +msgstr "" + +#: ../../source/development/dev_practices.rst:91 +msgid "" +"C/C++ code formatting rules are defined in :source_file:`.clang-format`. " +"Python code formatting is enforced by Black. The pre-commit utility " +"should be used to enforce them automatically. See :ref:`commit_hooks`." +msgstr "" + +#: ../../source/development/dev_practices.rst:95 +msgid "Memory allocation" +msgstr "" + +#: ../../source/development/dev_practices.rst:97 +msgid "" +"Large memory allocations should be performed using the " +":cpp:func:`VSIMalloc` family of functions, which will return ``nullptr`` " +"on allocation failure. As per :ref:`rfc-19`, you can use ``VSIMalloc2(x, " +"y)`` instead of doing ``CPLMalloc(x * y)`` or ``VSIMalloc(x * y)``. " +":cpp:func:`VSIMalloc2` will detect potential overflows in the " +"multiplication and return a NULL pointer if it happens. This can be " +"useful in GDAL raster drivers where x and y are related to the raster " +"dimensions or raster block sizes. Similarly, ``VSIMalloc3(x, y, z)`` can " +"be used as a replacement for ``CPLMalloc(x * y * z)``." +msgstr "" + +#: ../../source/development/dev_practices.rst:105 +msgid "" +"When working with standard library data structures such as " +"``std::vector`` that may throw ``std::bad_alloc``, a try/catch block " +"should be used around blocks that may allocate a large amount of memory." +msgstr "" + +#: ../../source/development/dev_practices.rst:108 +msgid "Adding a new driver" +msgstr "" + +#: ../../source/development/dev_practices.rst:110 +msgid "" +"If the driver depends on a third-party library, compilation of the driver" +" must be made conditional on the presence of the library. Drivers should " +"try to re-use existing library dependencies as much as possible, e.g. " +"Expat for SAX XML parsing." +msgstr "" + +#: ../../source/development/dev_practices.rst:111 +msgid "" +"For a vector driver, check that the Open() method of the driver (often " +"delegated to a Open() method of the datasource) is selective enough (i.e." +" it will not accept data files that are not meant for the driver), and " +"robust enough (it will not crash for small variations w.r.t content that " +"it would recognize). Check that it can deal with unusual filenames. For a" +" GDAL driver, similar checks, as well for the optional Identify() method." +msgstr "" + +#: ../../source/development/dev_practices.rst:112 +msgid "" +"A set of tests covering the driver should be added to the Python test " +"suite. If appropriate, small sample data files may be added to " +"autotest/gdrivers/data or autotest/ogr/data. The ``test_ogrsf`` utility " +"and ``GDALTest`` class may simplify testing of basic driver " +"functionality." +msgstr "" + +#: ../../source/development/dev_practices.rst:113 +msgid "" +"A documentation page should be created for the driver. Documentation " +"should, at a minimum, briefly describe the format handled by the driver " +"and, when relevant, describe the particular syntax for the connection " +"string, creation options, configuration options, etc. The documentation " +"should provide a link to a more detailed format description and mention " +"needed third-party libraries." +msgstr "" + +#: ../../source/development/dev_practices.rst:116 +msgid "Writing tests" +msgstr "" + +#: ../../source/development/dev_practices.rst:118 +msgid "See :ref:`writing_tests`." +msgstr "" + +#: ../../source/development/dev_practices.rst:121 +msgid "Git usage" +msgstr "" + +#: ../../source/development/dev_practices.rst:123 +msgid "" +"This section collects a few best practices for git usage for GDAL " +"development." +msgstr "" + +#: ../../source/development/dev_practices.rst:126 +msgid "Initiating your work repository" +msgstr "" + +#: ../../source/development/dev_practices.rst:128 +msgid "Fork |OSGeo/gdal| from the GitHub UI, and then run:" +msgstr "" + +#: ../../source/development/dev_practices.rst:137 +msgid "Working with a feature branch" +msgstr "" + +#: ../../source/development/dev_practices.rst:173 +msgid "From the GitHub UI, issue a pull request." +msgstr "" + +#: ../../source/development/dev_practices.rst:175 +msgid "" +"If the pull request discussion or automated checks require changes, " +"commit locally and push. To get a reasonable history, you may need to " +"combine commits using ``git rebase -i master``, in which case you will " +"have to force-push your branch with ``git push -f my_user_name " +"my_new_feature_branch``." +msgstr "" + +#: ../../source/development/dev_practices.rst:182 +msgid "Updating your local master against upstream master" +msgstr "" + +#: ../../source/development/dev_practices.rst:193 +msgid "Commit messages" +msgstr "" + +#: ../../source/development/dev_practices.rst:195 +msgid "" +"Commit messages should indicate a component name (eg a driver name), a " +"short description, and when relevant, a reference to a issue (with 'fixes" +" #' if it actually fixes it)" +msgstr "" + +#: ../../source/development/dev_practices.rst:208 +msgid "Commit hooks" +msgstr "" + +#: ../../source/development/dev_practices.rst:210 +msgid "" +"GDAL provides pre-commit hooks to run code formatters and linters before " +"a commit is made. The hooks are cloned with the repository and can be " +"installed using `pre-commit <https://pre-commit.com>`_:" +msgstr "" + +#: ../../source/development/dev_practices.rst:220 +msgid "" +"Once installed, the hooks can be run manually via ``pre-commit run --all-" +"files``." +msgstr "" + +#: ../../source/development/dev_practices.rst:223 +msgid "Blame ignore file" +msgstr "" + +#: ../../source/development/dev_practices.rst:225 +msgid "" +"Due to whole-tree code reformatting done during GDAL 3.7 development, " +"``git blame`` information might be misleading. To avoid that, you need to" +" modify your git configuration as following to ignore the revision of the" +" whole-tree reformatting:" +msgstr "" + +#: ../../source/development/dev_practices.rst:236 +msgid "Backporting bugfixes from master to a stable branch" +msgstr "" + +#: ../../source/development/dev_practices.rst:248 +msgid "If changes are needed, do them and ``git commit -a --amend``" +msgstr "" + +#: ../../source/development/dev_practices.rst:252 +msgid "Things you should NOT do" +msgstr "" + +#: ../../source/development/dev_practices.rst:254 +msgid "" +"(For anyone with push rights to |OSGeo/gdal|) Never modify a commit or " +"the history of anything that has been committed to " +"https://github.com/OSGeo/gdal" +msgstr "" + +#: ../../source/development/dev_practices.rst:258 +msgid "" +"Committing symbolic links is allowed only under the .github directory in " +"order to avoid potential problems on Windows." +msgstr "" + +#: ../../source/development/index.rst:6 +#: ../../source/development/rfc/rfc14_imagestructure.rst:66 +msgid "Development" +msgstr "" + +#: ../../source/development/rfc/index.rst:5 +msgid "RFC list" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:5 +msgid "RFC 10: OGR Open Parameters (not implemented)" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:7 +#: ../../source/development/rfc/rfc5_unicode.rst:7 +msgid "Author: Andrey Kiselev" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:9 +#: ../../source/development/rfc/rfc5_unicode.rst:9 +msgid "Contact: dron@ak4719.spb.edu" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:11 +msgid "Status: Development, *not* implemented" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:14 +#: ../../source/development/rfc/rfc11_fastidentify.rst:14 +#: ../../source/development/rfc/rfc12_filemanagement.rst:14 +#: ../../source/development/rfc/rfc14_imagestructure.rst:14 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:14 +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:14 +#: ../../source/development/rfc/rfc17_python_namespaces.rst:14 +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:14 +#: ../../source/development/rfc/rfc19_safememalloc.rst:14 +#: ../../source/development/rfc/rfc1_pmc.rst:14 +#: ../../source/development/rfc/rfc20_srs_axes.rst:14 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:14 +#: ../../source/development/rfc/rfc22_rpc.rst:14 +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:14 +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:14 +#: ../../source/development/rfc/rfc25_fast_open.rst:15 +#: ../../source/development/rfc/rfc27_supportdata.rst:14 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:14 +#: ../../source/development/rfc/rfc29_desired_fields.rst:14 +#: ../../source/development/rfc/rfc2_svn.rst:14 +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:14 +#: ../../source/development/rfc/rfc31_ogr_64.rst:14 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:14 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:14 +#: ../../source/development/rfc/rfc34_license_policy.rst:14 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:14 +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:16 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:16 +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:14 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:8 +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:12 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:12 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:14 +#: ../../source/development/rfc/rfc45_virtualmem.rst:14 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:14 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:14 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:14 +#: ../../source/development/rfc/rfc4_geolocate.rst:14 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:14 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:14 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:14 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:14 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:14 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:14 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:16 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:16 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:16 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:16 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:14 +#: ../../source/development/rfc/rfc5_unicode.rst:14 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:16 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:16 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:16 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:16 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:16 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:16 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:16 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:16 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:19 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:24 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:14 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:16 +#: ../../source/development/rfc/rfc71_github_migration.rst:15 +#: ../../source/development/rfc/rfc72_pytest.rst:15 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:16 +#: ../../source/development/rfc/rfc74_sphinx.rst:16 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:16 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:16 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:16 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:16 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:16 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:17 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:15 +#: ../../source/development/rfc/rfc84_cmake.rst:19 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:15 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:17 +#: ../../source/development/rfc/rfc87_signed_int8.rst:16 +#: ../../source/development/rfc/rfc88_googletest.rst:16 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:16 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:16 +#: ../../source/development/rfc/rfc91_dataset_close.rst:16 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:16 +#: ../../source/development/rfc/rfc93_update_feature.rst:16 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:16 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:16 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:16 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:16 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:15 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:16 +msgid "Summary" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:16 +msgid "" +"It is proposed that OGRSFDriver::Open() and OGRSFDriverRegistrar::Open() " +"calls should be changed to accept additional parameter containing " +"arbitrary additional parameters supplied by caller. OGROpenEx() function " +"will be introduced to map this new functionality into C interface. In " +"addition it is proposed to add an \"update\" flag to " +"OGRSFDriverRegistrar::Open() call to avoid using " +"OGRSFDriverRegistrar::OpenShared() method." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:25 +msgid "Open parameters" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:27 +msgid "" +"Sometimes it is needed to pass additional information to OGR driver along" +" with the name of the dataset to be opened. It can be, for example, the " +"style table name (some drivers allow to choose from the various style " +"tables) or any other additional data. The old method for doing this was " +"to encode the extra info in the dataset name string. It was inconvenient " +"approach, so it proposed to use separate parameter in OGRSFDriver::Open()" +" and OGRSFDriverRegistrar::Open() calls representing open options, just " +"like it is implemented in OGRDataSource::CreateLayer() call." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:37 +msgid "" +"It is supposed that open options will be supplied in form of NAME=VALUE " +"pairs forming the string list." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:40 +msgid "" +"In addition to options parameter the special \"shared\" flag will be " +"added to OGRSFDriverRegistrar::Open() call, so there will be no need in " +"separate OGRSFDriverRegistrar::OpenShared() method." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:45 +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:139 +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:106 +#: ../../source/development/rfc/rfc20_srs_axes.rst:217 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:101 +#: ../../source/development/rfc/rfc22_rpc.rst:266 +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:165 +#: ../../source/development/rfc/rfc25_fast_open.rst:24 +#: ../../source/development/rfc/rfc26_blockcache.rst:114 +#: ../../source/development/rfc/rfc26_blockcache.rst:210 +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:206 +#: ../../source/development/rfc/rfc31_ogr_64.rst:378 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:114 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:129 +#: ../../source/development/rfc/rfc34_license_policy.rst:232 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:278 +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:47 +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:101 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:38 +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:39 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:639 +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:19 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:29 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:29 +#: ../../source/development/rfc/rfc45_virtualmem.rst:1259 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:679 +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:89 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:613 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:169 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:253 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:56 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:500 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:590 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:85 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:167 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:133 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:105 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:782 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:202 +#: ../../source/development/rfc/rfc5_unicode.rst:79 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:285 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:394 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:134 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:279 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:480 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:90 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:276 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:192 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:243 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:191 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:53 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:118 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:530 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:225 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:454 +#: ../../source/development/rfc/rfc7_vsilapi.rst:96 +msgid "Implementation" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:47 +msgid "All Open() functions will be changed in the following way:" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:71 +msgid "" +"The last change needs to be propagated in all OGR drivers. The change " +"itself is pretty simple: one additional parameter should be added to " +"function definition. But it has impact on third-party OGR drivers: they " +"are not source compatible anymore and should be changed too." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:76 +msgid "Also appropriate C functions will be added:" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:90 +msgid "New Options for OGR Utilities" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:92 +msgid "" +"Proposed functionality will be available in OGR utilities ogr2ogr and " +"ogrinfo via the '-doo NAME=VALUE' (\"Datasource Open Option\") format " +"specific parameter." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:97 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:126 +#: ../../source/development/rfc/rfc26_blockcache.rst:178 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:65 +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:50 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:224 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:332 +#: ../../source/development/rfc/rfc5_unicode.rst:174 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:415 +msgid "Backward Compatibility" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:99 +msgid "" +"Proposed additions will not have any impact on C binary compatibility. " +"C++ binary interface will be broken, source level compatibility will be " +"broken for third-party OGR drivers only. There will be no impact for " +"high-level applications on source level." +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:105 +msgid "Responsibility and Timeline" +msgstr "" + +#: ../../source/development/rfc/rfc10_ogropen.rst:107 +msgid "" +"Andrey Kiselev is responsible to implement this proposal. New API will be" +" available in GDAL 1.5.0." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:5 +msgid "RFC 11: Fast Format Identification" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:7 +#: ../../source/development/rfc/rfc12_filemanagement.rst:7 +#: ../../source/development/rfc/rfc14_imagestructure.rst:7 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:7 +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:7 +#: ../../source/development/rfc/rfc1_pmc.rst:7 +#: ../../source/development/rfc/rfc20_srs_axes.rst:7 +#: ../../source/development/rfc/rfc22_rpc.rst:7 +#: ../../source/development/rfc/rfc27_supportdata.rst:7 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:7 +#: ../../source/development/rfc/rfc2_svn.rst:7 +#: ../../source/development/rfc/rfc3_commiters.rst:7 +#: ../../source/development/rfc/rfc4_geolocate.rst:7 +#: ../../source/development/rfc/rfc8_devguide.rst:7 +#: ../../source/development/rfc/rfc9_maintainer.rst:7 +msgid "Author: Frank Warmerdam" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:9 +#: ../../source/development/rfc/rfc12_filemanagement.rst:9 +#: ../../source/development/rfc/rfc14_imagestructure.rst:9 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:9 +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:9 +#: ../../source/development/rfc/rfc1_pmc.rst:9 +#: ../../source/development/rfc/rfc20_srs_axes.rst:9 +#: ../../source/development/rfc/rfc22_rpc.rst:9 +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:9 +#: ../../source/development/rfc/rfc25_fast_open.rst:9 +#: ../../source/development/rfc/rfc27_supportdata.rst:9 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:9 +#: ../../source/development/rfc/rfc2_svn.rst:9 +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:9 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:9 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:9 +#: ../../source/development/rfc/rfc34_license_policy.rst:9 +#: ../../source/development/rfc/rfc3_commiters.rst:9 +#: ../../source/development/rfc/rfc4_geolocate.rst:9 +#: ../../source/development/rfc/rfc8_devguide.rst:9 +#: ../../source/development/rfc/rfc9_maintainer.rst:9 +msgid "Contact: warmerdam@pobox.com" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:11 +msgid "Status: Adopted (and Implemented)" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:16 +msgid "" +"This RFC aims to add the ability for applications to quickly identify " +"what files in the file system are GDAL supported file formats without " +"necessarily opening any of them. It is mainly intended to allow GUI file " +"browsers based on file types." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:21 +msgid "" +"This is accomplished by extending the GDALOpenInfo structure to hold more" +" directory context, and by adding an Identify() method on the GDALDriver " +"which a driver can implement to quickly identify that a file is of a " +"given format without doing a more expensive Open() operation." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:27 +msgid "GDALOpenInfo" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:29 +msgid "" +"The Open() (or Identify()) methods of many drivers need to probe for " +"files associated with the target file in order to open or identify a file" +" as being of a particular format. For instance, in order to open an ESRI " +"BIL file (EHDR driver) it is necessary to probe for a driver with the " +"same basename as the target file, but the extension .hdr. Currently this " +"is typically accomplished with VSIFStatL() calls or similar which can be " +"fairly expensive." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:37 +msgid "" +"In order to reduce the need for such searches touch the operating system " +"file system machinery, the GDALOpenInfo structure will be extended to " +"hold an optional list of files. This is the list of all files at the same" +" level in the file system as the target file, including the target file. " +"The filenames will *not* include any path components, are an essentially " +"just the output of CPLReadDir() on the parent directory. If the target " +"object does not have filesystem semantics then the file list should be " +"NULL." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:46 +msgid "The following is added to GDALOpenInfo:" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:53 +msgid "" +"The new constructor allows the file list to be passed in to populate the " +"papszSiblingFiles member (the argument will be copied). The existing " +"default constructor will use CPLGetDirname() to get the directory of the " +"passed pszFile, and CPLReadDir() to read the corresponding file list. The" +" new constructor is primarily aimed at efficient implementation of the " +"later GDALIdentifyDriver() function, avoiding re-reading the file list " +"for each file to be tested." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:62 +msgid "Identify()" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:64 +msgid "The GDALDriver class will be extended with the following function:" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:70 +msgid "" +"When implemented by a driver, the function is intended to return TRUE " +"(non-zero) if the driver determines that the file passed in via " +"GDALOpenInfo appears to be of the format the driver is implemented for. " +"To call this applications should call the new function:" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:79 +msgid "Internally GDALIdentifyDriver() will do the following" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:81 +msgid "" +"A GDALOpenInfo structure will be initialized based on pszDatasource and " +"papszDirFiles." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:83 +msgid "" +"It will iterate over all drivers similarly to GDALOpen(). For each driver" +" it will use the pfnIdentify function if available, otherwise it will use" +" the pfnOpen() method to establish if the driver supports the file." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:87 +msgid "" +"It will return the driver handle for the first driver to respond " +"positively or NULL if none accept it." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:91 +msgid "Driver Changes" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:93 +msgid "" +"In theory it is not necessary for any drivers to be modified, since " +"GDALIdentifyDriver() will fallback to using the pfnOpen function to test." +" But in practice, no optimization is achieved unless at least some " +"drivers (hopefully those for which Open can be very expensive) are " +"updated. Part of the ongoing effort then is to implement identify " +"functions for GDAL drivers." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:100 +msgid "" +"Generally speaking it should be easy to craft an identify function from " +"the initial test logic in the open function. For instance, the GeoTIFF " +"driver might be changed like this:" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:139 +msgid "" +"The open might then be modified to use the identify function to avoid " +"duplicating the test logic." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:162 +msgid "" +"Drivers which require header files such as the EHdr driver might " +"implement Identify() like this:" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:192 +msgid "" +"During the initial implementation a variety of drivers will be updated, " +"including the following. As well some performance and file system " +"activity logging will be done to identify drivers that are currently " +"expensive." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:197 +msgid "HFA" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:198 +msgid "GTiff" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:203 +msgid "DTED" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:204 +msgid "USGS DEM" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:205 +msgid "MrSID" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:206 +#: ../../source/development/rfc/rfc34_license_policy.rst:181 +msgid "JP2KAK" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:208 +msgid "EHdr" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:209 +msgid "RST" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:212 +msgid "CPLReadDir()" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:214 +msgid "" +"Currently the VSIMemFilesystemHandler implemented in cpl_vsi_mem.cpp " +"which provides \"filesystem like\" access to objects in memory does not " +"implement directory reading services. In order to properly populate the " +"directory listing this will need to be added." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:219 +msgid "" +"To do this the CPLReadDir() function will also need to be reimplemented " +"to use VSIFilesystemHandler::ReadDir() instead of direct implementation " +"in cpl_dir.cpp. The win32 and unix/posix implementations of " +"VSIFilesystemHandler::ReadDir() already exist. This should essentially " +"complete the virtualization of filesystem access services." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:225 +msgid "" +"CPLReadDir() will also be renamed VSIReadDir() but with a stub under the " +"old name available for backward compatibility." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:229 +#: ../../source/development/rfc/rfc29_desired_fields.rst:115 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:628 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:146 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:220 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:70 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:138 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:108 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:462 +#: ../../source/development/rfc/rfc84_cmake.rst:133 +msgid "Compatibility" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:231 +msgid "" +"There are no anticipated backward compatibility problems. However forward" +" compatibility will be affected, in that drivers updated in trunk with " +"the Identify function will not be able to be ported back into 1.4 builds " +"and used their. Unmodified drivers, and externally maintained drivers " +"should not be impacted by this development." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:238 +#: ../../source/development/rfc/rfc12_filemanagement.rst:192 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:176 +msgid "SWIG Implications" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:240 +msgid "" +"The GDALIdentifyDriver() and VSIReadDir() functions will need to be " +"exposed via SWIG." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:244 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:429 +msgid "Regression Testing" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:246 +msgid "" +"A test script for the Identify() function will be added to the " +"autotest/gcore directory. It will include testing of identify in a " +"/vsimem memory collection." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:251 +#: ../../source/development/rfc/rfc12_filemanagement.rst:186 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:170 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:169 +msgid "Implementation Plan" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:253 +msgid "" +"The new features will be implemented by Frank Warmerdam in *trunk* for " +"the GDAL/OGR 1.5.0 release." +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:257 +msgid "Performance Tests" +msgstr "" + +#: ../../source/development/rfc/rfc11_fastidentify.rst:259 +msgid "" +"A very quick test introducing the Identify without actually opening " +"changed the time to identify all files in a directory with 70 TIFF files " +"(on an NFS share) from 2 seconds to 0.5 seconds. So saving the overhead " +"of actually opening files can be significant for some formats, including " +"very common ones like GeoTIFF." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:5 +msgid "RFC 12: Improved File Management" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:11 +msgid "Status: Adopted / Implemented" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:16 +msgid "" +"Some applications using GDAL have a requirement to provide file " +"management operations through the GUI. This includes deleting, renaming, " +"moving and packaging up datasets which often requires operations on " +"several associated files. This RFC introduces an operation on a " +"GDALDataset to identify all the dataset files, and operations to move or " +"copy them." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:24 +msgid "GetFileList()" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:26 +msgid "" +"The following new virtual method is added on the GDALDataset class, with " +"an analygous C function." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:33 +msgid "" +"The method is intended to return a list of files associated with this " +"open dataset. The return is a NULL terminated string list which becomes " +"owned by the caller and should be deallocated with CSLDestroy()." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:37 +msgid "" +"The default implementation tests the name of the datasource to see if it " +"is a file, and if so it is returned otherwise an empty list is returned. " +"If the default overview manager is active, and has overviews, those will " +"also be included in the file list. The default implementation also checks" +" for world files, but only those with extensions based on the original " +"files extension (ie. .tfw or .tifw for .tif) but does not search for .wld" +" since that is not very specific." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:45 +msgid "" +"The GDALPamDataset::GetFileList() method will add the ability to find " +".aux and .aux.xml files associated with a dataset to the core default " +"behavior." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:50 +msgid "pfnRename()" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:52 +#: ../../source/development/rfc/rfc12_filemanagement.rst:105 +msgid "The following new function is added to the GDALDriver class." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:58 +#: ../../source/development/rfc/rfc12_filemanagement.rst:111 +msgid "Also a corresponding function is added to the C API." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:64 +msgid "" +"Note that renaming is done by the driver, but the dataset to be operated " +"on should *not* be open at the time. GDALRenameDataset() will invoke " +"pfnRename if it is non-NULL." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:68 +msgid "" +"If pfnRename is NULL the default implementation will be used which will " +"open the dataset, fetch the file list, close the dataset, and then try to" +" rename all the files (based on shared basenames). The default rename " +"operation will fail if it is unable to establish a relationship between " +"the files (ie. a common basename or stem) to indicate how the group of " +"files should be rename to the new pattern." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:75 +#: ../../source/development/rfc/rfc12_filemanagement.rst:129 +msgid "" +"Optionally a NULL hDriver argument may be passed in, in which case the " +"appropriate driver will be selected by first opening the datasource." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:79 +msgid "CPLMoveFile()" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:81 +msgid "" +"The POSIX rename() function on which VSIRename() is usually based does " +"not normally allow renaming files between file systems or between " +"different kinds of file systems (ie. /vsimem to C:/abc). In order to " +"implement GDALRenameDataset() such that it works efficiently within a " +"file system, but still works between file systems, a new operation will " +"be added to gdal/port. This is the CPLMoveFile() function which will " +"first try a VSIRename(). If that fails it will use CPLCopyFile() to copy " +"the whole file and then VSIUnlink() to get rid of the old file." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:94 +msgid "The return value will be zero on success, otherwise an errno style value." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:97 +msgid "" +"It should be noted that in some error conditions, such as the destination" +" file system running out of space during a copy, it may happen that some " +"files for a dataset get renamed, and some do not leaving things in an " +"inconsistent state." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:103 +msgid "pfnCopyFiles()" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:117 +msgid "" +"Note that copying is done by the driver. The dataset may be opened, but " +"if opened in update mode it may be prudent to first do a flush to " +"synchronize the in-process state with what is on disk. " +"GDALCopyDatasetFiles() will invoke pfnCopyFiles if it is non-NULL." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:122 +msgid "" +"If pfnCopy is NULL the default implementation will be used which will " +"open the dataset, fetch the file list, close the dataset, and then try to" +" copy all the files (based on shared basenames). The default copy " +"operation will fail if it is unable to establish a relationship between " +"the files (ie. a common basename or stem) to indicate how the group of " +"files should be renamed to the new pattern." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:132 +msgid "" +"Copy is essentially the same as Rename, but the original files are " +"unaltered. Note that this form of copy is distinct from CreateCopy() in " +"that it preserves the exact binary files on disk in the new location " +"while CreateCopy() just attempts to reproduce a new dataset with " +"essentially the same data as modelled and carried through GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:139 +msgid "pfnDelete()" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:142 +msgid "" +"The delete operations default implementation will be extended to use the " +"GetFileList() results." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:146 +msgid "Supporting Functions" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:148 +msgid "" +"Some sort of supporting functions should be provided to make it easy to " +"identify worldfiles, .aux files and .prj files associated with a file." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:152 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:144 +msgid "Drivers Updated" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:154 +msgid "" +"It is anticipated that a majority of the commonly used drivers will be " +"updated with custom GetFileList() methods that account for world files " +"and other idiosyncratic files. A particular emphasis will made to handle " +"the various formats in gdal/frmts/raw that consist of a header file and a" +" raw binary file." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:160 +msgid "" +"Drivers for \"one file formats\" that are not updated will still use the " +"default logic which should work fairly well, but might neglect auxiliary " +"world files." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:164 +msgid "" +"VRT: I do not anticipate updating the VRT driver at this time since it " +"gets quite complicated to collect a file list for some kinds of virtual " +"files. It is also not exactly clear whether related files should be " +"considered \"owned\" by the virtual dataset or not." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:168 +msgid "" +"AIGRID: I will implement a custom rename operation in an attempt to " +"handle this directory oriented format gracefully." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:172 +msgid "Additional Notes" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:174 +msgid "" +"Subdatasets will generally return an empty file list from GetFileList(), " +"and will not be manageable via Rename or Delete though a very " +"sophisticated driver could implement these operations." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:177 +msgid "" +"There is no mechanism anticipated to ensure that files are closed before " +"they are removed. If an application does not ensure this rename/move " +"operations may fail on win32 since it doesn't allow rename/delete " +"operations on open files. Things could easily be left in an inconsistent " +"state." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:182 +msgid "" +"Datasets without associated files in the file system will return an empty" +" file list. This essentially identifies them as \"unmanagable\"." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:188 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:172 +msgid "" +"This change will be implemented by Frank Warmerdam in trunk in time for " +"the 1.5.0 release." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:194 +msgid "" +"The GDALRenameDataset(), and GDALCopyDatasetFiles() operations on the " +"driver, and the GetFileList() operation on the dataset will need to be " +"exposed through SWIG." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:199 +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:184 +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:128 +#: ../../source/development/rfc/rfc22_rpc.rst:272 +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:228 +#: ../../source/development/rfc/rfc25_fast_open.rst:100 +#: ../../source/development/rfc/rfc26_blockcache.rst:198 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:175 +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:66 +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:92 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:231 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:340 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:664 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:605 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:160 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:242 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:100 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:159 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:127 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:472 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:230 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:112 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:513 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:219 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:439 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:209 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:212 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:80 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:410 +#: ../../source/development/rfc/rfc87_signed_int8.rst:99 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:126 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:403 +#: ../../source/development/rfc/rfc91_dataset_close.rst:174 +#: ../../source/development/rfc/rfc93_update_feature.rst:257 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:161 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:168 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:486 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:306 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:139 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:683 +msgid "Testing" +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:201 +msgid "" +"Rename and CopyFiles testing will be added to the regression tests for a " +"few representative formats. These rename operations will be between one " +"directory and another, and will not test cross file system copying which " +"will have to be tested manually." +msgstr "" + +#: ../../source/development/rfc/rfc12_filemanagement.rst:206 +msgid "" +"A small gdalmanage utility will be implemented allowing use and testing " +"of the identify, rename, copy and delete operations from the commandline " +"in a convenient fashion." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:5 +msgid "RFC 13: Improved Feature Insertion/Update/Delete Performance in Batch Mode" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:15 +msgid "*Withdrawn*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:17 +msgid "" +"I have withdrawn this RFC based on some comments from `Frank " +"<http://lists.osgeo.org/pipermail/gdal-dev/2007-May/013132.html>`__ and " +"`Tamas <http://lists.osgeo.org/pipermail/gdal-" +"dev/2007-May/013130.html>`__ on GDAL-dev." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:23 +msgid "*Summary*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:25 +msgid "" +"Some OGR drivers can dramatically increase the speed of and optimize the " +"insertion, update, and deletion of a set of features, if the driver " +"knows, that there is a whole set of features that should/could be " +"inserted, updated, or deleted at once (instead of just one by one)." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:30 +msgid "*CreateFeatures()*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:32 +#: ../../source/development/rfc/rfc13_createfeatures.rst:61 +#: ../../source/development/rfc/rfc13_createfeatures.rst:90 +msgid "" +"The following new virtual method is added to the OGRLayer class, with an " +"analogous C function:" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:39 +#: ../../source/development/rfc/rfc13_createfeatures.rst:68 +#: ../../source/development/rfc/rfc13_createfeatures.rst:97 +msgid "A default implementation is given as below:" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:54 +msgid "This triggers the old behavior of an unoptimized insertion." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:56 +msgid "" +"Individual drivers can override the default implementation and can " +"implement an optimized algorithm for inserting a set of features." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:59 +msgid "*SetFeatures()*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:83 +msgid "This triggers the old behavior of an unoptimized update." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:85 +msgid "" +"Individual drivers can override the default implementation and can " +"implement an optimized algorithm for updating a set of features." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:88 +msgid "*DeleteFeatures()*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:112 +msgid "This triggers the old behavior of an unoptimized deletion." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:114 +msgid "" +"Individual drivers can override the default implementation and can " +"implement an optimized algorithm for deleting a set of features." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:117 +msgid "*C API functions*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:119 +msgid "The following C functions are added:" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:127 +msgid "" +"However, there are some issues with adding plain C arrays to the public " +"OGR interface due to the SWIG based wrapping, see for example `GDAL-Dev " +"Mail from Tamas <http://lists.gdal.org/pipermail/gdal-" +"dev/2007-May/013092.html>`__..." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:132 +msgid "*Additional Notes*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:134 +msgid "" +"Based in this new interface functions, I was able to increase the " +"insertion speed of features in the MySQL driver from 40 per second to up " +"to 800-2000 per second. I think other drivers can benefit from this " +"change, too." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:139 +msgid "See also ticket #1633." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:141 +msgid "*Implementation Plan*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:143 +msgid "A patch for the describe additions can be trivially provided." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:145 +msgid "" +"I can provide another patch based on this interface which contains the " +"optimized implementation for the MySQL driver." +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:148 +msgid "*History*" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:150 +msgid "14-May-2007: initial version created" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:152 +msgid "15-May-2007: SetFeatures() added" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:154 +msgid "16-May-2007: DeleteFeatures() added" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:156 +msgid "17-May-2007: C API functions added; SWIG wrapping issues mentioned" +msgstr "" + +#: ../../source/development/rfc/rfc13_createfeatures.rst:158 +msgid "23-May-2007: Withdrawn due some concerns on GDAL-dev" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:5 +msgid "RFC 14: Image Structure Metadata" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:11 +msgid "Status: Adopted, amended per :ref:`rfc-87`" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:16 +msgid "" +"This RFC attempts to formalize the semantics of the \"IMAGE_STRUCTURE\" " +"domain of metadata. This metadata domain is used to hold structural " +"information about image organization that would not normally be carried " +"with an image when translated into another format. The IMAGE_STRUCTURE " +"metadata may occur on the GDALDataset or on individual bands, and most " +"items are meaningful in both contexts. When items like NBITS are found on" +" the dataset it is assumed they apply to all bands of that dataset." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:25 +msgid "IMAGE_STRUCTURE items" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:27 +msgid "" +"COMPRESSION:: The compression type used for this dataset or band. There " +"is no fixed catalog of compression type names, but where a given format " +"includes a COMPRESSION creation option, the same list of values should be" +" used here as there." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:32 +msgid "" +"NBITS:: The actual number of bits used for this band, or the bands of " +"this dataset. Normally only present when the number of bits is non-" +"standard for the datatype, such as when a 1 bit TIFF is represented " +"through GDAL as GDT_Byte." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:37 +msgid "" +"INTERLEAVE:: This only applies on datasets, and the value should be one " +"of PIXEL, LINE or BAND. It can be used as a data access hint." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:40 +msgid "" +"PIXELTYPE:: This may appear on a GDT_Byte band (or the corresponding " +"dataset) and have the value SIGNEDBYTE to indicate the unsigned byte " +"values between 128 and 255 should be interpreted as being values between " +"-128 and -1 for applications that recognise the SIGNEDBYTE type." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:47 +msgid "" +"Starting with GDAL 3.7, with the implementation of :ref:`rfc-87`, " +"PIXELTYPE is no longer used, as the Int8 data type is used for signed " +"bytes." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:51 +#: ../../source/development/rfc/rfc20_srs_axes.rst:224 +#: ../../source/development/rfc/rfc31_ogr_64.rst:306 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:70 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:237 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:447 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:549 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:79 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:94 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:772 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:169 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:274 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:351 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:128 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:274 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:79 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:262 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:164 +msgid "Compatibility Issues" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:53 +msgid "" +"This RFC has two changes from existing practise that may cause " +"compatibility issues:" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:56 +msgid "" +"Traditionally the NBITS metadata appeared in the default metadata domain " +"on datasets, instead of in the IMAGE_STRUCTURE domain." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:58 +msgid "" +"Traditionally the COMPRESSION metadata appeared only on the dataset, " +"never one the band." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:61 +msgid "" +"I am only aware of one application previously making systematic use of " +"these items, and it will be updated to reflect the new usage as GDAL " +"1.5.0 is adopted." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:68 +msgid "" +"Beyond adopting the definition for the semantics of the IMAGE_STRUCTURE " +"metadata, the following development steps will be taken:" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:71 +msgid "" +"The PNG, GTiff, NITF and EHdr drivers will be updated to place NBITS in " +"the IMAGE_STRUCTURE metadata domain." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:73 +msgid "The HFA driver will be updated to return NBITS metadata." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:74 +msgid "" +"The HFA, GTiff, JP2KAK, ECW, JPEG, and PNG drivers will be updated to " +"return INTERLEAVE metadata." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:76 +msgid "The HFA and GTiff drivers will be updated to return PIXELTYPE metadata." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:79 +msgid "" +"The development will be done by Frank Warmerdam in trunk in time for " +"GDAL/OGR 1.5.0 release. Changes to other drivers that these definitions " +"might be useful for while be done as time permits by interested " +"developers - not necessarily in time for GDAL/OGR 1.5.0." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:85 +msgid "Notes" +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:87 +msgid "" +"The gdalinfo utility already reports IMAGE_STRUCTURE metadata when it is " +"available." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:89 +msgid "" +"The GTiff, and HFA drivers CreateCopy() methods check the source for " +"NBITS, and PIXELTYPE metadata to create specialized output files types." +msgstr "" + +#: ../../source/development/rfc/rfc14_imagestructure.rst:92 +msgid "" +"The GTiff, HFA and default CreateCopy() implementations have been " +"reworked to use the new GDALDatasetCopyWholeRaster() function which uses " +"the INTERLEAVE metadata as a clue whether to do interleaved copies if the" +" source dataset is interleaved." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:5 +msgid "RFC 15: Band Masks" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:11 +#: ../../source/development/rfc/rfc17_python_namespaces.rst:11 +#: ../../source/development/rfc/rfc1_pmc.rst:11 +#: ../../source/development/rfc/rfc20_srs_axes.rst:11 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:11 +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:11 +#: ../../source/development/rfc/rfc29_desired_fields.rst:11 +#: ../../source/development/rfc/rfc2_svn.rst:11 +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:11 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:11 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:11 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:11 +#: ../../source/development/rfc/rfc3_commiters.rst:11 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:11 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:11 +#: ../../source/development/rfc/rfc7_vsilapi.rst:11 +msgid "Status: Adopted" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:16 +msgid "" +"Some file formats support a concept of a bitmask to identify pixels that " +"are not valid data. This can be particularly valuable with byte image " +"formats where a nodata pixel value can not be used because all pixel " +"values have a valid meaning. This RFC tries to formalize a way of " +"recognising and accessing such null masks through the GDAL API, while " +"moving to a uniform means of representing other kinds of masking (nodata " +"values, and alpha bands)." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:24 +msgid "" +"The basic approach is to treat such masks as raster bands, but not " +"regular raster bands on the datasource. Instead they are freestanding " +"raster bands in a manner similar to the overview raster band objects. The" +" masks are represented as GDT_Byte bands with a value of zero indicating " +"nodata and non-zero values indicating valid data. Normally the value 255 " +"will be used for valid data pixels." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:32 +msgid "API" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:34 +msgid "GDALRasterBand is extended with the following methods:" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:42 +msgid "GDALDataset is extended with the following method:" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:48 +msgid "" +"Note that the GetMaskBand() should always return a GDALRasterBand mask, " +"even if it is only an all 255 mask with the flags indicating " +"GMF_ALL_VALID." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:52 +msgid "" +"The GetMaskFlags() method returns an bitwise OR-ed set of status flags " +"with the following available definitions that may be extended in the " +"future:" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:56 +msgid "" +"GMF_ALL_VALID(0x01): There are no invalid pixels, all mask values will be" +" 255. When used this will normally be the only flag set." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:58 +msgid "" +"GMF_PER_DATASET(0x02): The mask band is shared between all bands on the " +"dataset." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:60 +msgid "" +"GMF_ALPHA(0x04): The mask band is actually an alpha band and may have " +"values other than 0 and 255." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:62 +msgid "" +"GMF_NODATA(0x08): Indicates the mask is actually being generated from " +"nodata values. (mutually exclusive of GMF_ALPHA)" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:65 +msgid "" +"The CreateMaskBand() method will attempt to create a mask band associated" +" with the band on which it is invoked, issuing an error if it is not " +"supported. Currently the only flag that is meaningful to pass in when " +"creating a mask band is GMF_PER_DATASET. The rest are used to represent " +"special system provided mask bands. GMF_PER_DATASET is assumed when " +"CreateMaskBand() is called on a dataset." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:73 +msgid "Default GetMaskBand() / GetMaskFlags() Implementation" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:75 +msgid "" +"The GDALRasterBand class will include a default implementation of " +"GetMaskBand() that returns one of three default implementations." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:78 +msgid "If a corresponding .msk file exists it will be used for the mask band." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:80 +msgid "" +"If the band has a nodata value set, an instance of the new " +"GDALNodataMaskRasterBand class will be returned. GetMaskFlags() will " +"return GMF_NODATA." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:83 +msgid "" +"If there is no nodata value, but the dataset has an alpha band that seems" +" to apply to this band (specific rules yet to be determined) and that is " +"of type GDT_Byte then that alpha band will be returned, and the flags " +"GMF_PER_DATASET and GMF_ALPHA will be returned in the flags." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:88 +msgid "" +"If neither of the above apply, an instance of the new " +"GDALAllValidRasterBand class will be returned that has 255 values for all" +" pixels. The null flags will return GMF_ALL_VALID." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:92 +msgid "" +"The GDALRasterBand will include a protected poMask instance variable and " +"a bOwnMask flag. The first call to the default GetMaskBand() will result " +"in creation of the GDALNodataMaskRasterBand, GDALAllValidMaskRasterBand " +"and their assignment to poMask with bOwnMask set TRUE. If an alpha band " +"is identified for use, it will be assigned to poMask and bOwnMask set to " +"FALSE. The GDALRasterBand class will take care of deleting the poMask if " +"set and bOwnMask is true in the destructor. Derived band classes may " +"safely use the poMask and bOwnMask flag similarly as long as the " +"semantics are maintained." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:102 +msgid "" +"For an external .msk file to be recognized by GDAL, it must be a valid " +"GDAL dataset, with the same name as the main dataset and suffixed with " +".msk, with either one band (in the GMF_PER_DATASET case), or as many " +"bands as the main dataset. It must have INTERNAL_MASK_FLAGS_xx metadata " +"items set at the dataset level, where xx matches the band number of a " +"band of the main dataset. The value of those items is a combination of " +"the flags GMF_ALL_VALID, GMF_PER_DATASET, GMF_ALPHA and GMF_NODATA. If a " +"metadata item is missing for a band, then the other rules explained above" +" will be used to generate a on-the-fly mask band." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:113 +msgid "Default CreateMaskBand()" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:115 +msgid "" +"The default implementation of the CreateMaskBand() method will be " +"implemented based on similar rules to the .ovr handling implemented using" +" the GDALDefaultOverviews object. A TIFF file with the extension .msk " +"will be created with the same basename as the original file, and it will " +"have as many bands as the original image (or just one for " +"GMF_PER_DATASET). The mask images will be deflate compressed tiled images" +" with the same block size as the original image if possible." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:123 +msgid "" +"The default implementation of GetFileList() will also be modified to know" +" about the .msk files." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:127 +msgid "CreateCopy()" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:129 +msgid "" +"The GDALDriver::DefaultCreateCopy(), and GDALPamDataset::CloneInfo() " +"methods will be updated to copy mask information if it seems necessary " +"and is possible. Note that NODATA, ALL_VALID and ALPHA type masks are not" +" copied since they are just derived information." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:135 +msgid "Alpha Bands" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:137 +msgid "" +"When a dataset has a normal GDT_Byte alpha (transparency) band that " +"applies, it should be returned as the null mask, but the GetMaskFlags() " +"method should include GMF_ALPHA. For processing purposes any value other " +"than 0 should be treated as valid data, though some algorithms will treat" +" values between 1 and 254 as partially transparent." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:146 +msgid "These drivers will be updated:" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:148 +msgid "" +"JPEG Driver: support the \"zlib compressed mask appended to the file\" " +"approach used by a few data providers." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:150 +msgid "GRASS Driver: updated to support handling null values as masks." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:152 +msgid "Possibly updated:" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:154 +msgid "" +"HDF4 Driver: This driver might possibly be updated to return real mask if" +" we can figure out a way." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:156 +msgid "" +"SDE Driver: This driver might be updated if Howard has sufficient time " +"and enthusiasm." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:160 +#: ../../source/development/rfc/rfc31_ogr_64.rst:176 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:507 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:353 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:529 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:61 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:79 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:732 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:151 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:251 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:322 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:112 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:243 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:64 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:234 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:147 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:606 +msgid "Utilities" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:162 +msgid "" +"The gdalwarp utility and the gdal warper algorithm will be updated to use" +" null masks on input. The warper algorithm already uses essentially this " +"model internally. For now gdalwarp output (nodata or alpha band) will " +"remain unchanged, though at some point in the future support may be added" +" for explicitly generating null masks, but for most purposes producing an" +" alpha band is producing a null mask." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:178 +msgid "" +"The GetMaskBand(), GetMaskFlags() and CreateMaskBand() methods (and " +"corresponding defines) will need to be added. The mask should work like a" +" normal raster band for swig purposes so minimal special work should be " +"required." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:186 +msgid "The gdalautotest will be extended with the following:" +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:188 +msgid "" +"gcore/mask.py: test default mask implementation for nodata, alpha and all" +" valid cases." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:190 +msgid "" +"gdriver/jpeg.py: extend with a test for \"appended bitmask\" case - " +"creation and reading." +msgstr "" + +#: ../../source/development/rfc/rfc15_nodatabitmask.rst:193 +msgid "Interactive testing will be done for gdalwarp." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:5 +msgid "RFC 16: OGR Thread Safety" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:11 +#: ../../source/development/rfc/rfc27_supportdata.rst:11 +#: ../../source/development/rfc/rfc34_license_policy.rst:11 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:11 +#: ../../source/development/rfc/rfc5_unicode.rst:11 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:11 +msgid "Status: Development" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:16 +msgid "" +"In an effort to better support thread safety in OGR some methods are " +"added as internal infrastructure is updated." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:20 +#: ../../source/development/rfc/rfc34_license_policy.rst:22 +msgid "Definitions" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:22 +msgid "" +"*Reentrant*: A reentrant function can be called simultaneously by " +"multiple threads provided that each invocation of the function references" +" unique data." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:26 +msgid "" +"*Thread-safe*: A thread-safe function can be called simultaneously by " +"multiple threads when each invocation references shared data. All access " +"to the shared data is serialized." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:31 +#: ../../source/development/rfc/rfc17_python_namespaces.rst:28 +msgid "Objective" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:33 +msgid "" +"To make all of the OGR core and selected drivers reentrant, and to make " +"the driver registrar, drivers and datasources at least potentially " +"thread-safe." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:38 +msgid "TestCapability()" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:40 +msgid "" +"The TestCapability() method on the driver, and datasource will be " +"extended to include ways of testing for reentrancy and thread safety on " +"particular instances. The following macros will be added:" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:51 +msgid "Meaning:" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:53 +msgid "" +"OLCReentrant: The layer class is reentrant. Multiple threads can operate " +"on distinct instances of this class - including different layers on a " +"single datasource." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:56 +msgid "" +"ODsCReentrant: The datasource class is reentrant. Multiple threads can " +"operate on distinct instances of this class." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:58 +msgid "" +"ODsCThreadSafe: The datasource class is thread-safe. Multiple threads can" +" operate on a single instance of this class." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:60 +msgid "" +"ODsCLayerClones: The OGRDataSource::GetLayerClone() method is supported, " +"and returns a layer instance with distinct state from the default layer " +"returned by GetLayer()." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:64 +msgid "" +"Note that a single layer instance cannot be threadsafe as long as layer " +"feature reading status is implicit in the layer object. The default " +"return value for all test values is FALSE, as is normal for the " +"TestCapability() method, but specific drivers can return TRUE after " +"determining that the driver datasources or layers are in fact reentrant " +"and/or threadsafe." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:72 +msgid "OGRSFDriverRegistrar" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:74 +msgid "" +"Various changes have already been made to make the driver registrar " +"thread safe, primarily by protecting operations on it with a mutex." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:78 +msgid "OGRSFDriver" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:80 +msgid "" +"No changes are required to the OGRSFDriver base class for thread safety, " +"primarily because it does almost nothing." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:84 +msgid "OGRDataSource" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:86 +msgid "" +"This class has been modified to include an m_hMutex class data member " +"which is a mutex used to ensure thread safe access to internal " +"datastructures such as the layer list. Classes derived from OGRDataSource" +" that wish to implement threadsafe operation should use this mutex when " +"exclusivity is required." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:92 +msgid "A new method is added to this class:" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:98 +msgid "" +"The default implementation of this method returns NULL. If the " +"ODsCLayerClones capability is true for the datasource, this method must " +"return duplicates of the requested layer that have distinct feature " +"reading state. That is they can have their own spatial and attribute " +"filter settings, and the internal feature iterator (for GetNextFeature() " +"and ResetReading()) is distinct from other OGRLayer instances referencing" +" the same underlying datasource layer." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:106 +msgid "" +"The intention of this method in the multi-threaded context is that " +"different threads can have clones of a layer with distinct read state. A " +"sort of poor-mans threadsafety, even though in fact it is just " +"reentrancy." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:111 +msgid "" +"Layers return by GetLayerClone() should be released with the " +"OGRDataSource::ReleaseResultSet() method, much like layers returned by " +"ExecuteSQL()." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:116 +msgid "ExecuteSQL()" +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:118 +msgid "" +"The default OGR implementation of OGRDataSource::ExecuteSQL() internally " +"uses and modifies the layer state (feature iterators and filters) and as " +"such is not appropriate to use on a datasource that is attempting to be " +"threadsafe even though it is understood that individual layers are not " +"threadsafe." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:124 +msgid "" +"The proposed solution is that this code will be modified to use " +"GetLayerClone() if the datasource supports GetLayerClone()." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:130 +msgid "" +"A multi-threaded C++ test harnass will be implemented for read-only " +"stress testing of datasources claiming to support reentrancy and " +"threadsafety." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:134 +msgid "" +"No testing of reentrancy and threadsafety will be incorporated into the " +"regression test suite (gdalautotest) as it does not appear to be " +"practical." +msgstr "" + +#: ../../source/development/rfc/rfc16_ogr_reentrancy.rst:141 +msgid "" +"Frank Warmerdam will implement all the core features of this RFC for the " +"GDAL/OGR 1.5.0 release. As well the Shapefile, Personal Geodatabase, ODBC" +" and Oracle drivers will implement OLCReentrant, ODsCLayerClones, " +"ODsCReentrant and ODsThreadSafe." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:5 +msgid "RFC 17: Python Namespaces" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:7 +msgid "Author: Howard Butler" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:9 +msgid "Contact: hobu.inc@gmail.com" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:17 +msgid "" +"GDAL bindings for Python have historically dodged the normal Python " +"practices of using packages and namespaces to provide organization." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:25 +msgid "" +"This RFC implements a new namespace for Python, called *osgeo*, where the" +" GDAL Python bindings henceforth will reside. Backward compatibility is " +"provided, so that current code will continue to run unchanged, but new " +"developments should utilize the namespace for code organization and " +"global namespace pollution reasons. As of 10/1/2007, the changes " +"described here in RFC 17 only pertain to the \"next-gen\" Python " +"bindings. It is expected that these bindings will be the default bindings" +" for GDAL 1.5." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:30 +msgid "" +"To provide the GDAL Python bindings in a Python package that is properly " +"namespaced, eliminating pollution of Python's global namespace." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:34 +msgid "Past Usage" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:36 +msgid "GDAL's Python bindings previously used globally-aware Python modules:" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:47 +msgid "New Usage" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:49 +msgid "RFC 17 now provides these modules under the *osgeo* namespace:" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:59 +msgid "" +"Additionally, the old module-style imports continue to work with a " +"deprecation warning:" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:68 +msgid "" +"It is planned that we will remove the GDAL-specific global modules at " +"some point in the future." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:72 +msgid "Other Sprint Updates" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:74 +msgid "" +"The work for this RFC was done at the FOSS4G2007 GDAL code sprint by " +"Howard Butler and Chris Barker. In addition to the Python namespacing, " +"some minor issues were dealt with respect to building the GDAL bindings." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:78 +msgid "" +"The next-gen Python bindings now use setuptools by default if it is " +"available." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:80 +msgid "" +"The ./swig/python directory was slightly reorganized to separate " +"extension building from pure python modules." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:82 +msgid "" +"gdal2tiles, a Google Summer of Code project by Petr Klokan, was " +"integrated into the next-gen bindings" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:86 +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:120 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:153 +#: ../../source/development/rfc/rfc26_blockcache.rst:230 +#: ../../source/development/rfc/rfc29_desired_fields.rst:132 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:463 +#: ../../source/development/rfc/rfc7_vsilapi.rst:114 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:134 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:231 +msgid "Voting History" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:88 +msgid "A voice vote (our first ever!) commenced at the FOSS4G2007 sprint." +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:90 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:155 +#: ../../source/development/rfc/rfc29_desired_fields.rst:134 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:465 +msgid "Frank Warmerdam +1" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:91 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:159 +msgid "Howard Butler +1" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:92 +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:157 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:467 +msgid "Daniel Morissette +1" +msgstr "" + +#: ../../source/development/rfc/rfc17_python_namespaces.rst:93 +msgid "Tamas Szekerest +1" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:5 +msgid "RFC 18: OGR Style Support in C API" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:7 +msgid "Author: Daniel Morissette" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:9 +msgid "Contact: dmorissette@mapgears.com" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:11 +msgid "Status: Adopted (2007-12-05)" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:16 +msgid "" +"OGR has a number of C++ classes that deal with the encoding of style " +"information and attaching that to features. More information is available" +" in the :ref:`ogr_feature_style` document." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:20 +msgid "" +"With GDAL/OGR version 1.4.x and older, it was not possible to deal with " +"style information using the C API. This RFC proposes the addition of " +"functions to the C API to manipulate style information in GDAL/OGR 1.5." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:25 +msgid "Implementation Details" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:27 +msgid "The following enums will be moved from ogr_featurestyle.h to ogr_core.h:" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:39 +msgid "" +"The OGRStyleMgrH (corresponding to the OGRStyleMgr C++ class) will be " +"added to the C API:" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:53 +msgid "" +"The OGRStyleToolH (corresponding to the OGRStyleTool C++ class) will be " +"added to the C API:" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:77 +msgid "" +"Note: at implementation time, the OGR_ST_GetParamIsNull() has been " +"removed and replaced by an 'int \\*bValueIsNull' argument on all the " +"OGR_ST_GetParam...() functions in order to map more closely to the C++ " +"methods." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:82 +msgid "" +"NO wrappers will be needed for the following C++ classes which are " +"handled internally by the OGR\\_ST\\_\\* wrappers above:" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:92 +msgid "" +"Note that ogr_featurestyle.h also contains a OGRSTVectorParam enum and a " +"corresponding OGRStyleVector class but this class is currently unused and" +" may eventually be removed, so we will not implement support for it in " +"the C API (and the OGRSTVectorParam enum will NOT be moved to " +"ogr_core.h)." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:99 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:621 +msgid "Python and other language bindings" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:101 +msgid "" +"The initial implementation will be for the C API only and will not be " +"ported/tested with the Python and other scripting language bindings. This" +" will have to wait for a later release." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:108 +msgid "" +"Daniel Morissette will implement the changes to the C API described in " +"this RFC for the GDAL/OGR 1.5.0 release." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:111 +msgid "" +"The first test of the new C API functions will be the conversion of " +"MapServer's mapogr.cpp to use them." +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:115 +msgid "Related Ticket(s)" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:117 +msgid "#2061" +msgstr "" + +#: ../../source/development/rfc/rfc18_ogr_styles_c_api.rst:122 +#: ../../source/development/rfc/rfc19_safememalloc.rst:90 +msgid "+1 from all PSC members (FrankW, DanielM, HowardB, TamasS, AndreyK)" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:5 +msgid "RFC 19: Safer memory allocation in GDAL" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:7 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:7 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:7 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:7 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:7 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:7 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:7 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:7 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:7 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:7 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:7 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:7 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:7 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:7 +msgid "Author: Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:9 +msgid "Contact: even.rouault@spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:11 +#: ../../source/development/rfc/rfc26_blockcache.rst:11 +#: ../../source/development/rfc/rfc45_virtualmem.rst:11 +#: ../../source/development/rfc/rfc4_geolocate.rst:11 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:11 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:11 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:11 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:11 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:11 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:11 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:11 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:11 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:11 +msgid "Status: Adopted, implemented" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:16 +msgid "" +"This document contains proposal on how to make GDAL safer (prevent " +"crashes) when doing memory allocations. The starting point of this " +"discussion is ticket #2075." +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:21 +#: ../../source/development/rfc/rfc29_desired_fields.rst:31 +#: ../../source/development/rfc/rfc2_svn.rst:22 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:20 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:32 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:53 +#: ../../source/development/rfc/rfc84_cmake.rst:111 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:54 +#: ../../source/development/rfc/rfc87_signed_int8.rst:50 +#: ../../source/development/rfc/rfc93_update_feature.rst:55 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:42 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:82 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:56 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:37 +msgid "Details" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:23 +msgid "" +"In many places in GDAL source code, multiplications are done to compute " +"the size of the memory buffer to allocate, like raster blocks, scanlines," +" whole image buffers, etc.. Currently no overflow checking is done, thus " +"leading to potential allocation of not large enough buffers. Overflow can" +" occur when raster dimensions are very large (this can be the case with a" +" WMS raster source for example) or when a dataset is corrupted, " +"intentionnaly or unintentionnaly. This can lead to latter crash." +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:32 +msgid "" +"This RFC introduces new API to allocate memory when the computation of " +"the size to allocate is based on multiplications. These new API report " +"overflows when they occur. Overflows are detected by checking that " +"((a*b)/b) == a. This does not require to make assumptions on the size of " +"the variable types, their signedness, etc." +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:58 +msgid "" +"The behavior of VSIMalloc2 and VSIMalloc3 is consistent with the behavior" +" of VSIMalloc. Implementation of already existing memory allocation API " +"(CPLMalloc, CPLCalloc, CPLRealloc, VSIMalloc, VSICalloc, VSIRealloc) will" +" not be changed." +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:63 +msgid "" +":ref:`rfc-8` will be updated to promote new API for safer memory " +"allocation. For example using VSIMalloc2(x, y) instead of doing " +"CPLMalloc(x \\* y) or VSIMalloc(x \\* y)." +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:69 +msgid "Implementation steps" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:71 +msgid "Introduce the new API in gdal/port" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:73 +msgid "" +"Use the new API in GDAL core where it is relevant. The following files " +"have been identified as candidates : gcore/gdalnodatamaskband.cpp, " +"gcore/overview.cpp, gcore/gdaldriver.cpp, gcore/gdalrasterblock.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:78 +msgid "" +"Use the new API in GDAL drivers. This step can be done incrementally. " +"Transition from CPL to VSI allocation can be necessary in some cases too." +" Candidate drivers : Idrisi, PNG, GXF, BSB, VRT, MEM, JP2KAK, RPFTOC, " +"AIRSAIR, AIGRIB, XPM, USGDEM, BMP, GSG, HFA, AAIGRID. (See " +"gdal_svn_trunk_use_vsi_safe_mul_in_frmts.patch in ticket #2075)" +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:84 +msgid "" +"Even Rouault will implement the changes described in this RFC for the " +"GDAL 1.6.0 release." +msgstr "" + +#: ../../source/development/rfc/rfc19_safememalloc.rst:88 +#: ../../source/development/rfc/rfc31_ogr_64.rst:392 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:287 +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:96 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:652 +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:52 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:245 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:352 +#: ../../source/development/rfc/rfc45_virtualmem.rst:1266 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:691 +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:224 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:628 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:184 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:267 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:105 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:515 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:605 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:100 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:181 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:146 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:113 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:791 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:213 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:297 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:402 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:167 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:290 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:491 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:95 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:288 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:201 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:265 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:228 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:129 +#: ../../source/development/rfc/rfc71_github_migration.rst:117 +#: ../../source/development/rfc/rfc72_pytest.rst:242 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:542 +#: ../../source/development/rfc/rfc74_sphinx.rst:117 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:232 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:462 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:231 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:232 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:91 +#: ../../source/development/rfc/rfc84_cmake.rst:195 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:87 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:682 +#: ../../source/development/rfc/rfc87_signed_int8.rst:117 +#: ../../source/development/rfc/rfc88_googletest.rst:231 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:132 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:456 +#: ../../source/development/rfc/rfc91_dataset_close.rst:200 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:295 +#: ../../source/development/rfc/rfc93_update_feature.rst:275 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:167 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:181 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:558 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:318 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:163 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:738 +msgid "Voting history" +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:5 +msgid "RFC 1: Project Management Committee Guidelines" +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:16 +msgid "" +"This document describes how the GDAL/OGR Project Management Committee " +"determines membership, and makes decisions on GDAL/OGR project issues." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:19 +msgid "" +"In brief the committee votes on proposals on gdal-dev. Proposals are " +"available for review for at least two days, and a single veto is " +"sufficient to delay progress though ultimately a majority of members can " +"pass a proposal." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:25 +msgid "Detailed Process" +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:27 +msgid "" +"Proposals are written up and submitted on the gdal-dev mailing list for " +"discussion and voting, by any interested party, not just committee " +"members." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:30 +msgid "" +"Proposals need to be available for review for at least two business days " +"before a final decision can be made." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:32 +msgid "" +"Respondents may vote \"+1\" to indicate support for the proposal and a " +"willingness to support implementation." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:34 +msgid "" +"Respondents may vote \"-1\" to veto a proposal, but must provide clear " +"reasoning and alternate approaches to resolving the problem within the " +"two days." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:37 +msgid "" +"A vote of -0 indicates mild disagreement, but has no effect. A 0 " +"indicates no opinion. A +0 indicate mild support, but has no effect." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:39 +msgid "" +"Anyone may comment on proposals on the list, but only members of the " +"Project Management Committee's votes will be counted." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:41 +msgid "" +"A proposal will be accepted if it receives +2 (including the proposer) " +"and no vetos (-1)." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:43 +msgid "" +"If a proposal is vetoed, and it cannot be revised to satisfy all parties," +" then it can be resubmitted for an override vote in which a majority of " +"all eligible voters indicating +1 is sufficient to pass it. Note that " +"this is a majority of all committee members, not just those who actively " +"vote." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:48 +msgid "" +"Upon completion of discussion and voting the proposer should announce " +"whether they are proceeding (proposal accepted) or are withdrawing their " +"proposal (vetoed)." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:51 +msgid "The Chair gets a vote." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:52 +msgid "" +"The Chair is responsible for keeping track of who is a member of the " +"Project Management Committee." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:54 +msgid "" +"Addition and removal of members from the committee, as well as selection " +"of a Chair should be handled as a proposal to the committee. The " +"selection of a new Chair also requires approval of the OSGeo board." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:58 +msgid "The Chair adjudicates in cases of disputes about voting." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:61 +msgid "When is Vote Required?" +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:63 +msgid "Anything that could cause backward compatibility issues." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:64 +msgid "Adding substantial amounts of new code." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:65 +msgid "Changing inter-subsystem APIs, or objects." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:66 +msgid "Issues of procedure." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:67 +msgid "When releases should take place." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:68 +msgid "Anything that might be controversial." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:71 +msgid "Observations" +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:73 +msgid "The Chair is the ultimate adjudicator if things break down." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:74 +msgid "" +"The absolute majority rule can be used to override an obstructionist " +"veto, but it is intended that in normal circumstances vetoers need to be " +"convinced to withdraw their veto. We are trying to reach consensus." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:80 +msgid "Bootstrapping" +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:82 +msgid "" +"Frank Warmerdam is declared initial Chair of the Project Management " +"Committee." +msgstr "" + +#: ../../source/development/rfc/rfc1_pmc.rst:85 +msgid "" +"Daniel Morissette, Frank Warmerdam, Andrey Kiselev and Howard Butler are " +"declared to be the founding Project Management Committee. The current " +"membership list can be found on the :ref:`psc` page." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:5 +msgid "RFC 20: OGRSpatialReference Axis Support" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:16 +msgid "" +"The OGRSpatialReference and OGRCoordinateTransformation classes assume " +"that all coordinate systems use (easting, northing) coordinate order (or " +"in geographic terms (longitude, latitude)). In practice some coordinate " +"systems use alternate axis orientations (such as the Krovak projection), " +"and some standards (GML, WMS 1.3, WCS 1.1) require honouring the EPSG " +"declaration that all it's geographic coordinates have (latitude, " +"longitude) coordinate ordering." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:24 +msgid "" +"This RFC attempts to extend the OGRSpatialReference, and " +"OGRCoordinateTransformation classes to support alternate axis " +"orientations, and to update selected drivers (GML, WMS, WCS, GMLJP2) to " +"properly support axis ordering." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:30 +msgid "WKT Axis Representation" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:32 +msgid "" +"The OGC WKT SRS format (per OGC 01-???) already indicates a way of " +"defining coordinate system axes as shown in this example:" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:51 +msgid "" +"There is one AXIS definition per axis with order relating to position " +"within a tuple. The first argument is the user name for the axis and " +"exact values are not specified. The second argument is a direction and " +"may be one of NORTH, SOUTH, EAST or WEST." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:57 +msgid "Dilemma" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:59 +msgid "" +"The core challenge of this RFC is adding support for axes orders, " +"including honouring EPSG desired axis order for geographic coordinate " +"systems where appropriate without breaking existing files and code that " +"make extensive use of EPSG coordinate systems but override axis " +"orientations and assume they should be treated as long, lat regardless of" +" what EPSG says." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:66 +msgid "" +"In particular, we come up with appropriate policies and mechanisms to " +"decide when a file in a geographic coordinate system like EPSG:4326 is to" +" be treated as lat/long and when it should be long/lat. Because of the " +"extensive existing practice it behooves us to err on the side of past " +"practice, and require \"opting in\" to honouring EPSG axis ordering." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:73 +msgid "The Hack" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:75 +msgid "" +"The main mechanism by I propose to work around the dilemma is to " +"differentiate between geographic coordinate systems with the AXIS values " +"set and those without. In particular, a WKT coordinate system with the " +"EPSG authority code (ie. 4326) set, but no axis declarations will be " +"assumed to be long, lat even though that is contrary to the definition " +"from EPSG of 4326. Only in cases where we really *know* we want to honour" +" EPSG's axis order will we actually populate the axis declarations " +"indicating lat, long." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:84 +msgid "" +"The hope is that this will let us continue to (mis)use EPSG:4326 " +"definitions without necessary honouring the EPSG axis ordering except in " +"specific circumstances." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:89 +msgid "OGRSpatialReference" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:92 +msgid "New Enumeration" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:106 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:194 +msgid "New methods" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:113 +msgid "Fetch information about one axis (iAxis is zero based)." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:122 +msgid "Defines the X and Y axes for a given target key (PROJCS or GEOGCS)." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:128 +msgid "" +"Returns true based on the EPSG code if EPSG would like this coordinate " +"system to be treated as lat/long. This is useful in contexts like WMS 1.3" +" where EPSG:4326 needs to be interpreted as lat/long due to the standard." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:137 +msgid "" +"This works like importFromEPSG() but will assign the EPSG defined AXIS " +"definition." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:140 +msgid "" +"Note that OGRSpatialReference::StripNodes( \"AXIS\" ); can be used to " +"strip axis definitions where they are not desired." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:144 +msgid "importFromURN" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:146 +msgid "" +"Modify importFromURN() to set AXIS values properly for EPSG and OGC " +"geographic coordinate systems. So urn:...:EPSG: will be assumed to really" +" honour EPSG conventions." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:151 +msgid "SetWellKnownGeogCS()" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:153 +msgid "This method appears to be the only code" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:155 +msgid "" +"Modify SetWellKnownGeogCS() to *not* set AXIS values, and strip AXIS " +"values out of any other hardcoded WKT definitions." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:159 +msgid "importFromEPSG()" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:161 +msgid "" +"importFromEPSG() will continue to *not* set AXIS values for GEOGCS " +"coordinate systems." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:163 +msgid "" +"importFromEPSG() will now set axis values for projected coordinate " +"systems (at least in cases like Krovak where it is a non-default axis " +"orientation)." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:166 +msgid "" +"importFromEPSG() will be implemented by calling importFromEPSGA() and " +"stripping off axis definitions from the geographic portion of the " +"returned definition." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:171 +msgid "SetFromUserInput()" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:173 +msgid "" +"This method will have one new option which is a value prefixed by EPSGA: " +"will be passed to importFromEPSGA() (similarly to EPSG:n being passed to " +"importFromEPSG())." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:178 +msgid "OGRCoordinateTransformation" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:180 +msgid "" +"If AXIS values are set on source and/or destination coordinate system, " +"the OGRCoordinateTransformation code will take care of converting into " +"normal easting/northing before calling PROJ." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:184 +msgid "" +"The CPL config option \"GDAL_IGNORE_AXIS_ORIENTATION\" may also be set to" +" \"TRUE\" to disable OGRCoordinateTransformation's checking, and " +"application of axis orientation changes. Effectively this is a backdoor " +"to disable the core effects of the RFC." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:190 +#: ../../source/development/rfc/rfc34_license_policy.rst:171 +msgid "Drivers Affected" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:192 +msgid "" +"GMLJP2 (classes in gcore/gdalgmlcoverage.cpp and " +"gcore/gdaljp2metadata.cpp)." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:194 +msgid "WCS (based on interpretation of urns)." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:195 +msgid "" +"WMS (maybe? actually, I suspect we don't actually get the coordinate " +"system from the capabalities)" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:197 +msgid "OGR GML (maybe? only GML3 affected?)" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:198 +msgid "" +"BSB, SAR_CEOS, ENVISAT, HDF4, JDEM, L1B, LAN, SRTMHGT: Like " +"SetWellKnownGeogCS() these all include lat/long AXIS specifications in " +"their hardcoded WGS84 coordinate systems. These need to be removed so " +"they will default to being interpreted as long/lat." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:204 +msgid "Versions" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:206 +msgid "" +"Work will be in trunk for GDAL/OGR 1.6.0 with the following exceptions " +"which will be address in 1.5.x:" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:209 +msgid "" +"Existing use of AXIS specifier will for geographic coordinate systems " +"will be stripped from SetWellKnownGeogCS() and the various drivers with " +"hard coded WKT strings." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:212 +msgid "" +"Some sort of hack will need to be introduced into the GMLJP2 (and " +"possibly WCS) code to flip EPSG authority lat/long values (details to be " +"worked out)." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:219 +msgid "" +"Implementation would be done by Frank Warmerdam. Some aspects (such as " +"properly capturing axis ordering for projected coordinate systems) might " +"not be implemented immediately." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:226 +msgid "" +"The greatest concern is that any existing WKT coordinate systems with " +"LAT/LONG axis ordering (in VRT files, or .aux.xml files for instance) " +"will be interpreted differently by GDAL/OGR 1.6.0 than they were by " +"1.5.0. This could easily occur if files in formats like BSB, or HDF4 were" +" copied to a format using WKT coordinate systems (such as JPEG with a " +".aux.xml file). To partially mitigate this I am proposing that AXIS " +"definitions be removed from GDAL 1.5.1." +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:235 +msgid "Supporting Information" +msgstr "" + +#: ../../source/development/rfc/rfc20_srs_axes.rst:237 +msgid "" +"OSGeo Wiki Summary: `http://wiki.osgeo.org/index.php/Axis_Order_Confusion" +" <http://wiki.osgeo.org/index.php/Axis_Order_Confusion>`__" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:5 +msgid "RFC 21: OGR SQL type cast and field name alias" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:7 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:7 +msgid "Author: Tamas Szekeres" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:9 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:9 +msgid "Contact: szekerest@gmail.com" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:16 +msgid "" +"This proposal provides support for changing the column name and the " +"column type in the OGR SQL select list." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:19 +msgid "" +"The main motivation of this change is to provide better control when " +"transferring the OGR_STYLE special field from each data source to the " +"other. For example we can use ogr2ogr for this purpose using the " +"following command line:" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:28 +msgid "" +"The shape driver will truncate the OGR_STYLE field to 80 characters by " +"default in length that may not be enough to hold the actual value. So as " +"to fix this issue we might want to specify the desired length in the " +"select list, like:" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:37 +msgid "" +"In some cases it would also be useful to change the name of the field in " +"the target data source:" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:45 +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:21 +#: ../../source/development/rfc/rfc26_blockcache.rst:45 +#: ../../source/development/rfc/rfc5_unicode.rst:20 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:29 +msgid "Main concepts" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:47 +msgid "" +"To support these new features we will extend the current OGR SQL syntax. " +"The proposed addition will keep the syntax conform to the SQL92 " +"specification:" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:95 +msgid "" +"This RFC doesn't address implementing conversion to the 'integer list', " +"'double list' and 'string list' OGR data types, which doesn't conform to " +"the SQL92 specification and the necessary conversion routines are missing" +" in the OGR code." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:103 +msgid "" +"To implement the addition the following changes should be made in the OGR" +" codebase:" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:106 +msgid "" +"In ogr_swq.h I'll have to add to 4 fields to swq_col_def to hold the " +"field_alias the target_type, the field_length, and field_precision" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:109 +msgid "" +"In ogr_swq.h SWQ_DATE, SWQ_TIME, SWQ_TIMESTAMP will be added to " +"swq_field_type enum." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:112 +msgid "" +"In swq.c I'll have to change swq_select_preparse to take care of the " +"field alias and the CAST specification." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:115 +msgid "" +"A new function (swq_parse_typename) will be added to parse the supported " +"typenames." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:118 +msgid "" +"In ogr_gensql.cpp the .ctor of OGRGenSQLResultsLayer will be changed to " +"set up the field name and the field length to the target data source" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:122 +msgid "" +"In ogr_gensql.cpp TranslateFeature will be modified to take care of the " +"type change if specified." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:128 +msgid "" +"The backward compatibility for the current SQL syntax will be retained. " +"This addition doesn't require changes in the OGR C and SWIG API." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:132 +#: ../../source/development/rfc/rfc22_rpc.rst:260 +#: ../../source/development/rfc/rfc26_blockcache.rst:193 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:182 +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:200 +#: ../../source/development/rfc/rfc31_ogr_64.rst:194 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:108 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:119 +#: ../../source/development/rfc/rfc34_license_policy.rst:227 +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:96 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:615 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:656 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:598 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:154 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:237 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:383 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:535 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:66 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:153 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:121 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:84 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:737 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:156 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:264 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:339 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:118 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:263 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:457 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:69 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:250 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:154 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:435 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:505 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:210 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:433 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:203 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:207 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:74 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:404 +#: ../../source/development/rfc/rfc87_signed_int8.rst:91 +#: ../../source/development/rfc/rfc93_update_feature.rst:252 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:163 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:479 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:298 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:134 +msgid "Documentation" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:134 +msgid "" +"The OGR SQL document will be updated to reflect the new features. I'll " +"take care of updating the OGR Style Documentation with the support of " +"transferring the styles between the data sources." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:139 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:441 +msgid "Implementation Staffing" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:141 +msgid "Tamas Szekeres will implement the RFC in the development version." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:143 +msgid "" +"Frank Warmerdam will implement the regression test scripts according to " +"this new functionality." +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:147 +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:175 +#: ../../source/development/rfc/rfc26_blockcache.rst:217 +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:41 +#: ../../source/development/rfc/rfc5_unicode.rst:191 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:156 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:209 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:452 +msgid "References" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:149 +msgid "" +"Tracking bug for this feature (containing all of the proposed code " +"changes): #2171" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:161 +msgid "Even Rouault +1" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:163 +#: ../../source/development/rfc/rfc29_desired_fields.rst:135 +msgid "Tamas Szekeres +1" +msgstr "" + +#: ../../source/development/rfc/rfc21_ogrsqlcast.rst:165 +msgid "Andrey Kiselev +0" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:5 +msgid "RFC 22: RPC Georeferencing" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:11 +#: ../../source/development/rfc/rfc28_sqlfunc.rst:11 +msgid "Status: Adopted, Implemented" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:16 +msgid "" +"It is proposed that GDAL support an additional mechanism for geolocation " +"of imagery based on rational polynomial coefficients (RPCs) represented " +"as metadata." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:20 +msgid "" +"Many modern raw satellite products are distributed with RPCs, including " +"products from GeoEye, and DigitalGlobe. RPCs provide a higher systematic " +"description of georeferencing over an image, and also contain information" +" on the viewing geometry that in theory makes orthocorrection (given a " +"DEM) and some 3D operations like building height computation possible." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:28 +msgid "RPC Domain Metadata" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:30 +msgid "" +"Datasets with RPCs will include the following dataset level metadata " +"items in the \"RPC\" domain to identify the rational polynomials." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:33 +msgid "" +"ERR_BIAS: Error - Bias. The RMS bias error in meters per horizontal axis " +"of all points in the image (-1.0 if unknown)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:35 +msgid "" +"ERR_RAND: Error - Random. RMS random error in meters per horizontal axis " +"of each point in the image (-1.0 if unknown)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:37 +msgid "LINE_OFF: Line Offset" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:38 +msgid "SAMP_OFF: Sample Offset" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:39 +msgid "LAT_OFF: Geodetic Latitude Offset" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:40 +msgid "LONG_OFF: Geodetic Longitude Offset" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:41 +msgid "HEIGHT_OFF: Geodetic Height Offset" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:42 +msgid "LINE_SCALE: Line Scale" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:43 +msgid "SAMP_SCALE: Sample Scale" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:44 +msgid "LAT_SCALE: Geodetic Latitude Scale" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:45 +msgid "LONG_SCALE: Geodetic Longitude Scale" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:46 +msgid "HEIGHT_SCALE: Geodetic Height Scale" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:47 +msgid "" +"LINE_NUM_COEFF (1-20): Line Numerator Coefficients. Twenty coefficients " +"for the polynomial in the Numerator of the rn equation. (space separated)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:50 +msgid "" +"LINE_DEN_COEFF (1-20): Line Denominator Coefficients. Twenty coefficients" +" for the polynomial in the Denominator of the rn equation. (space " +"separated)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:53 +msgid "" +"SAMP_NUM_COEFF (1-20): Sample Numerator Coefficients. Twenty coefficients" +" for the polynomial in the Numerator of the cn equation. (space " +"separated)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:56 +msgid "" +"SAMP_DEN_COEFF (1-20): Sample Denominator Coefficients. Twenty " +"coefficients for the polynomial in the Denominator of the cn equation. " +"(space separated)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:60 +msgid "" +"These fields are directly derived from the document prospective GeoTIFF " +"RPC document at:" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:63 +msgid "" +"`http://geotiff.maptools.org/rpc_prop.html " +"<http://geotiff.maptools.org/rpc_prop.html>`__" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:65 +msgid "" +"The line and pixel offset expressed with LINE_OFF and SAMP_OFF are with " +"respect to the center of the pixel (#5993)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:69 +msgid "Updating NITF Driver" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:71 +msgid "" +"Already supports RPCs in this model, but will be modified to put them in " +"the RPC domain instead of the primary metadata domain." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:73 +msgid "Add support for reading Digital Globe .RPB files." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:74 +msgid "No support for writing RPCs for now." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:77 +msgid "Updating GeoTIFF Driver" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:79 +msgid "Upgrade to support reading Digital Globe .RPB files." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:80 +msgid "Possible support reading Space Imaging (GeoEye?) rpc.txt files." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:81 +msgid "" +"Support reading RPC TIFF tag (per " +"`http://geotiff.maptools.org/rpc_prop.html " +"<http://geotiff.maptools.org/rpc_prop.html>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:83 +msgid "Support writing RPC TIFF tag." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:84 +msgid "Support writing .RPB files (if RPB=YES or PROFILE not GDALGeoTIFF)." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:87 +msgid "Changes to GenImgProj Transformer" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:89 +msgid "" +"Currently it is difficult to reliably create a warp transformer based on " +"RPCs using GDALGenImgProjTransformer() as it will use a geotransform in " +"preference to RPCs if available. Many images with useful RPC information " +"also include a geotransform (approximate or accurate). It is therefore " +"proposed to modify the GDALCreateGenImgProjTransformer() function to make" +" it practical to provide more direction in the creation of the " +"transformer. The proposed new function is:" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:103 +msgid "Supported Options:" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:105 +msgid "SRC_SRS: WKT SRS to be used as an override for hSrcDS." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:106 +msgid "DST_SRS: WKT SRS to be used as an override for hDstDS." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:107 +msgid "GCPS_OK: If false, GCPs will not be used, default is TRUE." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:108 +msgid "" +"MAX_GCP_ORDER: the maximum order to use for GCP derived polynomials if " +"possible. The default is to autoselect based on the number of GCPs. A " +"value of -1 triggers use of Thin Plate Spline instead of polynomials." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:112 +msgid "" +"METHOD: may have a value which is one of GEOTRANSFORM, GCP_POLYNOMIAL, " +"GCP_TPS, GEOLOC_ARRAY, RPC to force only one geolocation method to be " +"considered on the source dataset." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:115 +msgid "RPC_HEIGHT: A fixed height to be used with RPC calculations." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:117 +msgid "" +"This replaces the older function which did not include support for " +"passing arbitrary options, and was thus not easily extended. The old " +"function will be re-implemented with a call to the new functions." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:121 +msgid "" +"The most important addition is the METHOD option which can be set to " +"specifically use one of the image to georeferenced coordinate system " +"methods instead of leaving it up to the code to pick the one it thinks is" +" best." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:127 +msgid "Changes to gdalwarp and gdaltransform" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:129 +msgid "" +"In order to facilitate passing transformer options into the updated " +"GDALCreateGenImgProjTransformer2(), the gdalwarp and gdaltransform " +"programs (built on this function) will be updated to include a -to " +"(transformer option) switch, and to use the new function." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:135 +#: ../../source/development/rfc/rfc4_geolocate.rst:146 +msgid "Preserving Geolocation Through Translation" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:137 +msgid "" +"The RPC information needs to be copied and preserved through translations" +" that do not alter the spatial arrangement of the data. To that end RPC " +"metadata copying will be added to:" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:141 +msgid "VRT driver's CreateCopy()." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:142 +msgid "GDALDriver's default CreateCopy()." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:143 +msgid "GDALPamDataset::CopyInfo()" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:144 +msgid "" +"gdal_translate will be updated to copy RPC metadata to the intermediate " +"internal VRT if, and only if, no resizing or subsetting is being done." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:149 +msgid "Changes to RPC Transformer" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:151 +msgid "" +"Implement iterative \"back transform\" from pixel/line to lat/long/height" +" instead of simple linear approximator." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:153 +msgid "" +"Add support for RPC_HEIGHT offset, so all Z values to transformer are " +"assumed to be relative to this offset (normally really and average " +"elevation for the scene)." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:156 +msgid "Make RPC Transformer serializable (in VRT files, etc)." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:159 +#: ../../source/development/rfc/rfc25_fast_open.rst:92 +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:60 +msgid "Backward Compatibility Issues" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:161 +msgid "" +"Previously the NITF driver returned RPC metadata in the default domain. " +"With the implementation of this RFC for GDAL 1.6.0 any applications using" +" this metadata would need to consult the RPC domain instead. The RPC\\_ " +"prefix on the metadata values has also been removed." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:166 +msgid "" +"The GDALCreateGenImgProjTransformer() function is preserved, so no " +"compatibility issues are anticipated by the addition of the new " +"generalized factory." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:171 +msgid "SWIG Bindings Issues" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:173 +msgid "" +"The raw access is by the established metadata api, so no changes are " +"needed for this." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:175 +msgid "" +"The Warp API is only bound at a high level, so there should be no changes" +" in this regard." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:177 +msgid "" +"For testing purposes it is desirable to provide a binding around the GDAL" +" transformer API. The following planned binding is based loosely on " +"OGRCoordinateTransformation API binding. So far I have only found the " +"TransformPoint( bDstToSrc, x, y, z ) entry point to be useful in Python " +"and even that ends up returning a (bSuccess, (x, y, z)) result which is " +"somewhat awkward. Is there a better way of doing this?" +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:262 +msgid "" +"In addition to standard API documentation, the RPC metadata mechanism " +"will be introduced into the \"GDAL Data Model\" document." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:268 +msgid "" +"This work will be implemented by Frank Warmerdam with support from the " +"Canadian Nuclear Safety Commission." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:274 +msgid "" +"A test script for the transformer API covering RPC, GCP_TPS, " +"GCP_POLYNOMIAL, GEOLOC and GEOTRANSFORM methods will be implemented." +msgstr "" + +#: ../../source/development/rfc/rfc22_rpc.rst:276 +msgid "" +"A test script for reading and writing RPB, and GeoTIFF RPC tags will be " +"written." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:5 +msgid "RFC 23.1: Unicode support in OGR" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:7 +#: ../../source/development/rfc/rfc25_fast_open.rst:7 +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:7 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:7 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:7 +#: ../../source/development/rfc/rfc34_license_policy.rst:7 +msgid "Authors: Frank Warmerdam" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:11 +msgid "Status: Adopted (implemented)" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:16 +msgid "" +"This document proposes preliminary steps towards GDAL/OGR handling " +"strings internally in UTF-8, and supporting conversion between different " +"encodings." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:23 +#: ../../source/development/rfc/rfc5_unicode.rst:22 +msgid "GDAL should be modified in a way to support three following main ideas:" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:25 +msgid "" +"C Functions will be provided to support a variety of encoding " +"conversions, including conversion between representations (ie. UTF-8 to " +"UCS-16/wchar_t)." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:28 +msgid "Character encodings will be identified by iconv() style strings." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:29 +msgid "" +"OFTString/OFTStringList feature attributes in OGR will be treated as " +"being in UTF-8." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:32 +msgid "" +"This RFC specifically does not attempt to address issues of using non-" +"ascii filenames. It also does not attempt to make definitions about the " +"encoding of other strings used in GDAL/OGR (such as field names, " +"metadata, etc). These would presumably be addressed in a later RFC " +"building on this one." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:39 +msgid "CPLRecode API" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:41 +msgid "" +"The following three C callable functions will be introduced for recoding " +"strings, and for converting between wchar_t (wide character) and char " +"(multi-byte) formats:" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:57 +msgid "" +"In each case the returned string is zero terminated, as is the input " +"string, and the returned string should be deallocated with CPLFree(). In " +"case of error the returned string will be NULL, and the function will " +"issue a CPLError(). The functions will be marked with CPL_DLL and " +"considered part of the public GDAL/OGR API for use of applications as " +"well as internal use." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:65 +msgid "Encoding Names" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:67 +msgid "" +"It is proposed that the encoding names will be the same sorts of names " +"used by iconv(). So stuff like \"UTF-8\", \"LATIN5\", \"CP850\" and " +"\"ISO_8859-1\". It does not appear that these names for encodings are a " +"1:1 match with C library locale names (like \"en_CA.utf8\" for instance) " +"which may cause some issues." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:73 +msgid "Some particular names of interest:" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:75 +msgid "" +"\"\": The current locale. Use this when converting from/to the users " +"locale." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:77 +msgid "" +"\"UTF-8\": Unicode in multi-byte encoding. Most of the time this will be " +"our internal linga-franca." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:79 +msgid "" +"\"POSIX\": I think this is roughly ASCII (perhaps with some extended " +"characters?)." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:81 +msgid "" +"\"UCS-2\": Two byte unicode. This is a wide character format and only " +"suitable for use with the wchar_t methods." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:84 +msgid "" +"On some systems you can use \"iconv --list\" to get a list of supported " +"encodings." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:88 +msgid "iconv()" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:90 +msgid "" +"It is proposed to implement the CPLRecode() method using the iconv() and " +"related functions when available." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:93 +msgid "" +"There is an excellent implementation of this API as GNU libiconv(), which" +" is used by the C libraries on Linux. Also some operating systems provide" +" the iconv() API as part of the C library (all unix?); however, the " +"system iconv() often has a restricted set of conversions supported so it " +"may be desirable to use libiconv in preference to the system iconv() even" +" when it is available." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:100 +msgid "" +"If iconv() is not available, a stub implementation of the recode services" +" will be provided which:" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:103 +msgid "" +"implements UCS-2 / UTF-8 interconversion using either mbtowc/wctomb, or " +"an implementation derived from " +"`http://www.cl.cam.ac.uk/~mgk25/unicode.html " +"<http://www.cl.cam.ac.uk/~mgk25/unicode.html>`__." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:106 +msgid "" +"Implements recoding from \"\" to and from \"UTF-8\" by doing nothing, but" +" issuing a warning on the first use if the current locale does not appear" +" to be the \"C\" locale." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:109 +msgid "Implements recoding from \"ASCII\" to \"UTF-8\" as a null operation." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:110 +msgid "" +"Implements recoding from \"UTF-8\" to \"ASCII\" by turning all non-ASCII " +"multi-byte characters to '?'." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:113 +msgid "" +"This hopefully gives us a weak operational status when built without " +"iconv(), but full operation when it is available." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:116 +msgid "" +"The --with-iconv= option will be added to configure. The argument can be " +"the path to a libiconv installation or the special value 'system' " +"indicating that the system lib should be used. Alternatively, --without-" +"iconv can be used to avoid using iconv." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:122 +msgid "OFTString/OFTStringList Fields" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:124 +msgid "" +"It is declared that OGR string attribute values will be in UTF-8. This " +"means that OGR drivers are responsible for translating format specific " +"representations to UTF-8 when reading, and back to the format specific " +"representation when writing. In many cases (of simple ASCII text) this " +"requires no transformation." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:130 +msgid "" +"This implies that the arguments to methods like OGRFeature::SetField( int" +" i, const char \\*) should be UTF-8, and that GetFieldAsString() will " +"return UTF-8." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:134 +msgid "" +"The same issues apply to OFTStringList lists of strings. Each string will" +" be assumed to be UTF-8." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:138 +msgid "OLCStringsAsUTF8 Capability Flag" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:140 +msgid "" +"Some drivers (ie. CSV) can effectively not know the encoding of their " +"inputs. Therefore, it isn't always practical to turn things into UTF-8 in" +" a guaranteed way. So, the new layer level capability called " +"\"StringsAsUTF8\" represented with the macro \"OLCStringsAsUTF8\" will be" +" testable at the layer level with TestCapability(). Drivers which are " +"certain to return string attributes as UTF-8 should return TRUE, while " +"drivers that do not know the encoding they return should return FALSE. " +"Any driver which knows it's encoding should convert to UTF-8." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:150 +msgid "OGR Driver Updates" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:152 +msgid "" +"The following OGR drivers could benefit immediately from recoding to " +"UTF-8 support in one way or another." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:155 +msgid "ODBC (add support for wchar_t / NVARSHAR fields)" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:156 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:58 +msgid "Shapefile" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:157 +msgid "" +"GML (I'm not sure how the XML encoding values all map to our concept of " +"encoding)" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:159 +msgid "Postgres" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:161 +msgid "" +"I'm sure a number of the other drivers, particularly the RDBMS drivers, " +"could benefit from an update." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:167 +msgid "" +"Frank Warmerdam will implement the core iconv() capabilities, the " +"CPLRecode() additions and update the ODBC driver. Other OGR drivers would" +" be updated as time and demand mandates to conform to the definitions in " +"this RFC by interested developers." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:172 +msgid "The core work will be completed for GDAL/OGR 1.6.0 release." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:177 +#: ../../source/development/rfc/rfc5_unicode.rst:193 +msgid "" +"`The Unicode Standard, Version 4.0 - Implementation Guidelines " +"<http://unicode.org/versions/Unicode4.0.0/ch05.pdf>`__ - Chapter 5 (PDF)" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:180 +#: ../../source/development/rfc/rfc5_unicode.rst:196 +msgid "" +"FAQ on how to use Unicode in software: " +"`http://www.cl.cam.ac.uk/~mgk25/unicode.html " +"<http://www.cl.cam.ac.uk/~mgk25/unicode.html>`__" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:182 +#: ../../source/development/rfc/rfc5_unicode.rst:198 +msgid "" +"FLTK implementation of string conversion functions: " +"`http://svn.easysw.com/public/fltk/fltk/trunk/src/utf.c " +"<http://svn.easysw.com/public/fltk/fltk/trunk/src/utf.c>`__" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:184 +#: ../../source/development/rfc/rfc5_unicode.rst:200 +msgid "" +"`http://www.easysw.com/~mike/fltk/doc-2.0/html/utf_8h.html " +"<http://www.easysw.com/~mike/fltk/doc-2.0/html/utf_8h.html>`__" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:185 +#: ../../source/development/rfc/rfc5_unicode.rst:201 +msgid "Ticket #1494 : UTF-8 encoding for GML output." +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:186 +msgid "" +"Libiconv: `http://www.gnu.org/software/libiconv/ " +"<http://www.gnu.org/software/libiconv/>`__" +msgstr "" + +#: ../../source/development/rfc/rfc23_ogr_unicode.rst:188 +msgid "" +"ICU (another i18n library): `http://www.icu-project.org/ <http://www.icu-" +"project.org/>`__" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:5 +msgid "RFC 24: GDAL Progressive Data Support" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:7 +msgid "Author: Norman Barker, Frank Warmerdam" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:9 +msgid "Contact: nbarker@ittvis.com, warmerdam@pobox.com" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:16 +msgid "" +"Provide an interface for asynchronous/streaming data access in GDAL. The " +"initial implementation is for JPIP, but should be generic enough to apply" +" to other streaming / progressive approaches. Background on the JPIP " +"(Kakadu) implementation can be found in [wiki:rfc24_jpipkak]." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:22 +msgid "Interfaces" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:25 +msgid "GDALAsyncReader" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:27 +msgid "" +"This new class is intended to represent an active asynchronous raster " +"imagery request. The request includes information on a source window on " +"the dataset, a target buffer size (implies level of decimation or " +"replication), the buffer type, buffer interleaving, data buffer and bands" +" being requested. Essentially the same sort of information that is passed" +" in a GDALDataset::!RasterIO() request." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:34 +msgid "" +"The GetNextUpdatedRegion() method can be used to wait for an update to " +"the imagery buffer, and to find out what area was updated. The " +"LockBuffer() and UnlockBuffer() methods can be used to temporarily " +"disable updates to the buffer while application code accesses the buffer." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:40 +msgid "" +"While an implementation of the simple accessors is provided as part of " +"the class, it is intended that the class be subclassed as part of " +"implementation of a particular driver, and custom implementations of " +"GetNextUpdatedRegion(), LockBuffer() and UnlockBuffer() provided." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:45 +msgid "" +"{{{ class CPL_DLL GDALAsyncReader { protected: GDALDataset\\* poDS; int " +"nXOff; int nYOff; int nXSize; int nYSize; void \\* pBuf; int nBufXSize; " +"int nBufYSize; GDALDataType eBufType; int nBandCount; int\\* panBandMap; " +"int nPixelSpace; int nLineSpace; int nBandSpace; long nDataRead;" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:50 +msgid "" +"public: GDALAsyncReader(GDALDataset\\* poDS = NULL); virtual " +"~GDALAsyncReader();" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:81 +msgid "}; }}}" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:84 +msgid "GetNextUpdatedRegion()" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:105 +msgid "" +"The async return status list is as follows, and will be declared in " +"gdal.h." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:119 +msgid "The meaning as a return value is:" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:121 +msgid "" +"GARIO_PENDING: No imagery was altered in the buffer, but there is still " +"activity pending, and the application should continue to call " +"GetNextUpdatedRegion() as time permits." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:124 +msgid "" +"GARIO_UPDATE: Some of the imagery has been updated, but there is still " +"activity pending." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:126 +msgid "" +"GARIO_ERROR: Something has gone wrong. The asynchronous request should be" +" ended." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:128 +msgid "" +"GARIO_COMPLETE: An update has occurred and there is no more pending work " +"on this request. The request should be ended and the buffer used." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:133 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:122 +msgid "GDALDataset" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:135 +msgid "" +"The GDALDataset class is extended with methods to create an asynchronous " +"reader, and to cleanup the asynchronous reader. It is intended that these" +" methods would be subclassed by drivers implementing asynchronous data " +"access." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:151 +msgid "" +"It is expected that as part of gdal/gcore a default !GDALAsyncReader " +"implementation will be provided that just uses GDALDataset::!RasterIO() " +"to perform the request as a single blocking request. However, this " +"default implementation will ensure that applications can use the " +"asynchronous interface without worrying whether a particular format will " +"actually operate asynchronously." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:159 +msgid "GDALDriver" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:161 +msgid "" +"In order to provide a hint to applications whether particular formats " +"support asynchronous IO, we will add a new metadata item on the " +"GDALDriver of implementing formats. The metadata item will be " +"\"DCAP_ASYNCIO\" (macro GDAL_DCAP_ASYNCIO) and will have the value " +"\"YES\" if asynchronous IO is available." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:167 +msgid "" +"Implementing drivers will do something like this in their driver setup " +"code:" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:175 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:147 +msgid "GDALRasterBand" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:177 +msgid "" +"There are no changes to the GDALRasterBand interface for asynchronous " +"raster IO. Asynchronous IO requests can only be made at the dataset " +"level, not the band." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:182 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:364 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:183 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:219 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:144 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:87 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:152 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:382 +#: ../../source/development/rfc/rfc91_dataset_close.rst:135 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:146 +msgid "C API" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:184 +msgid "" +"The following C API wrappers for the C++ classes and methods will be " +"added. Note that at this time there is no intention to provide C wrappers" +" for all the GDALAsyncReader accessors since the provided information is " +"already available in the application from the call launching the async " +"io." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:215 +msgid "" +"It is intended that all the above functions in the C API will be wrapped " +"for SWIG." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:219 +msgid "Driver Implementations" +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:221 +msgid "" +"A full implementation of the Asynchronous API will be provided as the " +"JPIPKAK driver - a JPIP protocol implementation using the Kakadu library." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:225 +msgid "At this time, no other implementations are planned." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:230 +msgid "" +"Some testing of the asynchronous api against normal drivers will be added" +" in the test suite, as well as testing of the JPIPKAK driver in " +"asynchronous and conventional data access methods." +msgstr "" + +#: ../../source/development/rfc/rfc24_progressive_data_support.rst:234 +msgid "" +"Also, a new commandline program, gdalasyncread, is implemented which " +"provides a mechanism to test the async API from the commandline. It takes" +" a subset of the gdal_translate commandline options." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:5 +msgid "RFC 25: Fast Open (withdrawn)" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:11 +msgid "" +"Status: Withdrawn (in favor of some specific improvements in #2957 - rfc " +"may be renewed at a later date)" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:17 +msgid "" +"This document proposes a mechanism for application to indicate a desire " +"for the fastest possible open of a raster file, even if a variety of " +"metadata and supporting information may not be available. It is primarily" +" intended to optimize applications working with catalogs containing many " +"raster files." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:26 +msgid "" +"An application can request fast open mode by setting the " +"\"GDAL_FAST_OPEN\" configuration option to \"YES\" - the default is " +"assumed to be no. When this option is set to YES selected drivers can " +"operate differently so as to optimize the speed of opening a dataset. " +"Acceleration options include:" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:32 +msgid "" +"Skip establishing a coordinate system - particularly helpful if it avoids" +" an EPSG lookup." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:34 +msgid "Skip probing for supporting .aux.xml, world files and other files." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:36 +msgid "" +"It is anticipated that fast open mode will be used primarily for fast " +"raster display from datasets where required metadata is already provided " +"by a catalog of some sort. Because of this it is essential that in fast " +"open mode datasets will still accurately return a list of bands, their " +"datatypes, and their overviews." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:43 +msgid "Thread Local Configuration Options" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:45 +msgid "" +"In multi-threaded applications use of a process-global configuration " +"option - turned on just while calling GDALOpen() - may not be " +"appropriate. In particular, it is hard to ensure that this configuration " +"option won't affect GDALOpen()'s in other threads of the same process. " +"This problem also affects other configuration options that. To resolve " +"this problem it is intended to add a new function to set \"thread local\"" +" configuration options." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:57 +msgid "" +"This mechanism will be implemented using normal thread local data " +"handling (CPLGetTLS(), etc)." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:60 +msgid "" +"It should be noted that CPLSetConfigOption() will continue to set " +"configuration options to apply to all threads. CPLGetConfigOption() will " +"first search thread local values, then process global values and then the" +" environment." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:66 +msgid "Work Plan" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:68 +msgid "" +"For the time being the following changes will be made to drivers to " +"accelerate them in fast open mode." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:71 +msgid "GDALOpenInfo will avoid loading a list of all files in a directory." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:72 +msgid "GTIFF driver will avoid collecting a coordinate systems." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:74 +msgid "" +"This work will be completed in trunk in time for the GDAL 1.7.0 release " +"by Frank Warmerdam." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:78 +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:53 +msgid "Utilization" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:80 +msgid "" +"There is no plan to do this immediately, but the GDAL VRT driver would be" +" a good candidate to utilize this mechanism." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:83 +msgid "" +"In theory, it would also be desirable for MapServer to utilize this mode " +"for tileindexed rasters - except that MapServer depends on the " +"geotransform coming from the underlying raster file rather than coming " +"from the raster catalog. MapServer also assumes the color table, and " +"nodata values will be available." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:89 +msgid "ArcGIS is also expected to utilize this feature." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:94 +msgid "" +"There are no known backward compatibility issues. However, there may be " +"forward compatibility issues if we are not precise and consistent from " +"version to version on what supporting info is allowed to be omitted in " +"fast open mode." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:102 +msgid "" +"Tests would be added to the appropriate driver test scripts to test fast " +"open mode - confirming that expected information is discarded, and kept." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:107 +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:71 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:119 +msgid "Issues" +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:109 +msgid "" +"Potentially desirable things like ignoring .aux.xml files are not " +"possible as they are also sometimes the source of overview information." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:112 +msgid "" +"Potentially discarding all metadata including color tables, nodata " +"values, and geotransforms makes this mode not useful for applications " +"like MapServer that don't keep such information in their catalog." +msgstr "" + +#: ../../source/development/rfc/rfc25_fast_open.rst:115 +msgid "" +"This RFC does not discuss a way of accelerating GDALOpen() by skipping " +"unnecessary drivers, though that would also potentially help quite a bit." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:5 +msgid "RFC 26: GDAL Block Cache Improvements" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:7 +msgid "Authors: Tamas Szekeres, Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:9 +msgid "Contact: szekerest@gmail.com, even.rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:13 +msgid "Implementation version: GDAL 2.1" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:16 +msgid "Summary and rationale" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:18 +msgid "" +"GDAL maintains an in-memory cache for the raster blocks fetched from the " +"drivers and ensures that the second attempt to access the same block will" +" be served from the cache instead of the driver. This cache is maintained" +" in a per-band fashion and an array is allocated for the pointers for " +"each blocks (or sub-blocks). This approach is not sufficient with large " +"raster dimensions (or large virtual rasters ie. with the WMS/TMS driver)," +" which may cause out of memory errors in GDALRasterBand::InitBlockInfo, " +"as raised in #3224" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:27 +msgid "" +"For example, a band of a dataset at level 21 with a GoogleMaps tiling " +"requires 2097152x2097152 tiles of 256x256 pixels. This means that GDAL " +"will try to allocate an array of 32768x32768 = 1 billion elements (32768 " +"= 2097152 / 64). The size of this array is 4 GB on a 32-bit build, so it " +"cannot be allocated at all. And it is 8 GB on a 64-bit build (even if " +"this is generally only virtual memory reservation but not actually " +"allocation of physical pages of memory, due to over-commit mechanism of " +"the operating system). At dataset closing, this means that those 1 " +"billion cells will have to be explored to discover remaining cached " +"blocks. In reality, all above figures must be multiplied by 3 for a RGB " +"(or 4 for a RGBA) dataset." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:39 +msgid "" +"In the hash set implementation, memory allocation depends directly on the" +" number of cached blocks. Typically with the default GDAL_CACHEMAX size " +"of 40 MB, only 640 blocks of 256x256 pixels can be simultaneously cached " +"(for all datasets)." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:47 +msgid "" +"Awareness of thread-safety issues is crucial in the design of block " +"caching. In gdalrasterblock.cpp, a static linked list is maintained so as" +" to track the access order of the blocks and keep the size of the cache " +"within a desired limit by dropping the oldest blocks out of the list. " +"This linked list is shared among all the datasets and bands in GDAL " +"(protected by a hRBMutex) and a thread on each band, when reading a new " +"block, may also trigger a GDALRasterBand::UnreferenceBlock call on " +"another band within the scope of this mutex. GDALRasterBand::FlushBlock " +"will also access the data structure of the band level cache by removing " +"the corresponding tile from the array or the hashtable." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:58 +msgid "" +"In GDAL 2.0, some issues related to thread-safety (#3225, #3226) have " +"been fixed and this RFC still preserves those scenarios as safe." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:61 +msgid "" +"The changes of this RFC consist in moving away from the GDALRasterBand " +"class the logic to access to a cached block, to add or remove it. This is" +" done with the new GDALAbstractBandBlockCache class. The current array " +"based logic is moved into the new GDALArrayBandBlockCache class, and the " +"new hashset based logic in GDALHashsetBandBlockCache." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:67 +msgid "" +"For the array based implementation, due to the \"static\" nature of the " +"hosting structure (an array), no special care is needed when reading or " +"writing a cell from concurrent threads. The only special care that must " +"be taken is to prevent a given cell (block) to be accessed concurrently. " +"For example we want to avoid TryGetLockedBlockRef() to return a block " +"that is being freed by another thread from " +"GDALRasterBlock::FlushCacheBlock() or Internalize(). For that, the " +"nRefCount member of GDALRasterBlock is now accessed and modified only " +"through atomic functions to increase, decrease or compare-and-swap its " +"value." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:78 +msgid "" +"For the hash set based implementation, the base implementation of hash " +"set data structure done in in cpl_hash_set.h / cpl_hash_set.cpp is not " +"thread safe by default. So GDALHashsetBandBlockCache has a dedicated " +"mutex to protect all reads, additions and removals from the hash set. No " +"dead-lock with the hRBMutex can occurs since no operations done under the" +" hashset mutex involves calling any method from GDALRasterBlock." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:85 +msgid "" +"We could potentially have reused the hRBMutex to protect the hash set, " +"but this would have increased the contention of the hRBMutex " +"unnecessarily." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:89 +msgid "" +"By default, the selection between the array based and the hashtable based" +" approaches is based on the following rule: if the dataset has more than " +"1 million blocks, the hashset based implementation is used, otherwise the" +" array based implementation is used. The new GDAL_OF_ARRAY_BLOCK_ACCESS " +"and GDAL_OF_HASHSET_BLOCK_ACCESS open flags can also be passed to " +"GDALOpenEx() to override this choice. The :config:`GDAL_BAND_BLOCK_CACHE`" +" configuration option can also be set to ARRAY or HASHSET." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:98 +msgid "" +"The hashset based implementation could potentially be the default " +"implementation in all cases (performance comparisons done with the " +"autotest/cpp/testblockcache utility with 4 or 8 cores show non measurable" +" differences), but in theory the array based implementation offers less " +"contention of the hRBMutex, so should be more scalable when using lots of" +" cores. And as work has been done during GDAL 2.0 to improve the " +"scalability, it might be prudent for now to remain on the array based " +"implementation on rasters of modest size." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:107 +msgid "" +"Not completely linked with this RFC, a few changes have been done to " +"limit the number of allocation/deallocation of objects (GDALRasterBlock " +"instances, as well as an internal element of CPLHashSet), which has an " +"effect on scalability since memory allocation routines involve " +"synchronization between threads." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:116 +msgid "" +"To implement the addition the following changes is made in the GDAL " +"codebase:" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:119 +msgid "" +"port/cpl_hash_set.cpp / port/cpl_hash_set.h: CPLHashSetClear() function " +"added to remove all the elements in one operation." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:122 +msgid "" +"port/cpl_hash_set.cpp / port/cpl_hash_set.h: " +"CPLHashSetRemoveDeferRehash() function added to remove one element " +"quickly. That is to say the potential resizing of the array used " +"internally is deferred to a later operation" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:127 +msgid "" +"port/cpl_hash_set.cpp / port/cpl_hash_set.h: improvements to \"recycle\" " +"links from the linked lists and avoid useless malloc()/free()." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:131 +msgid "port/cpl_atomic_ops.cpp: addition of CPLAtomicCompareAndExchange()" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:133 +msgid "" +"gcore/gdal.h: additions of GDAL_OF_DEFAULT_BLOCK_ACCESS, " +"GDAL_OF_ARRAY_BLOCK_ACCESS and GDAL_OF_HASHSET_BLOCK_ACCESS values." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:136 +msgid "" +"gcore/gdal_priv.h: definition of GDALAbstractBandBlockCache class, and " +"GDALArrayBandBlockCacheCreate() and GDALHashSetBandBlockCacheCreate() " +"functions. Modifications of GDALRasterBand, GDALDataset and " +"GDALRasterBlock definitions." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:141 +msgid "" +"gcore/gdalrasterband.cpp: InitBlockInfo() instantiates the appropriate " +"band block cache implementation." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:144 +msgid "" +"gcore/gdalrasterband.cpp: the AdoptBlock(), UnreferenceBlock(), " +"FlushBlock() and TryGetLockedBlockRef() methods delegate to the actual " +"band block cache implementation." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:148 +msgid "" +"gcore/gdalrasterband.cpp: AddBlockToFreeList() is added and delegate to " +"GDALAbstractBandBlockCache" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:151 +msgid "gcore/gdalrasterblock.cpp: SafeLockBlock() is replaced by TakeLock()" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:153 +msgid "" +"gcore/gdalrasterblock.cpp: RecycleFor() method added to recycle an " +"existing block object to save a few new/delete calls (used by " +"GDALAbstractBandBlockCache::CreateBlock())" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:157 +msgid "" +"gcore/gdalrasterblock.cpp: Internalize() or FlushCacheBlock() no longer " +"directly free a block (they still free or recycle its pData member), but " +"provide it to GDALRasterBand::AddBlockToFreeList() for layer reuse." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:162 +msgid "" +"gcore/gdalrasterblock.cpp: DropLockForRemovalFromStorage() is added to " +"avoid racing destruction of blocks between GDALRasterBand::FlushCache() " +"or FlushBlock() with GDALRasterBlock::Internalize() or FlushCacheBlock()." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:167 +msgid "" +"gcore/gdalabstractbandblockcache.cpp: added. Contains logic to keep " +"instantiated GDALRasterBlock that were discarded by the global block " +"manager for their later reuse. Saves a few new/delete calls." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:171 +msgid "" +"gcore/gdalarraybandblockcache.cpp: the GDALArrayBandBlockCache class " +"implementation with mostly the existing code" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:174 +msgid "" +"gcore/gdalhashsetbandblockcache.cpp: the new GDALHashsetBandBlockCache " +"class implementation" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:180 +msgid "" +"This implementation retains the backward compatibility with the existing " +"API. The C++ ABI of GDALRasterBand, GDALDataset and GDALRasterBlock is " +"modified." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:185 +msgid "Performance impacts" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:187 +msgid "" +"The array based implementation after this RFC should still show the same " +"performance than the current implementation (potentially very slightly " +"improved with the recycling of blocks). Confirmed by tests with " +"autotest/cpp/testblockcache." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:195 +msgid "This change doesn't affect the existing user documentation." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:200 +msgid "" +"The autotest/cpp/testblockcache utility is now run by the \"quick_test\" " +"target of autotest/cpp/Makefile with " +":config:`GDAL_BAND_BLOCK_CACHE=HASHSET` in additions to the array based " +"implementation." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:204 +msgid "" +"A new autotest/cpp/testblockcachelimits utility has been developed to " +"test a few racing situations. As races are hard to trigger, the code of " +"GDALRasterBlock has been instrumented to allow sleeping in particular " +"places, enabling races to be reliably simulated." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:212 +msgid "" +"Tamas Szekeres had provided an initial version of this RFC. It has been " +"restructured and ported on GDAL 2.0 by Even Rouault (sponsored by `LINZ " +"(Land Information New Zealand) <http://www.linz.govt.nz/>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:219 +msgid "" +"The proposed implementation lies in the \"rfc26_bandblockcache\" branch " +"of the `https://github.com/rouault/gdal2/tree/rfc26_bandblockcache " +"<https://github.com/rouault/gdal2/tree/rfc26_bandblockcache>`__ " +"repository." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:224 +msgid "" +"The list of changes: " +"`https://github.com/rouault/gdal2/compare/rfc26_bandblockcache " +"<https://github.com/rouault/gdal2/compare/rfc26_bandblockcache>`__" +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:227 +msgid "Related bugs: #3264, #3224." +msgstr "" + +#: ../../source/development/rfc/rfc26_blockcache.rst:232 +msgid "+1 from EvenR, DanielM, TamasS. +0 from JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:5 +msgid "RFC 27: Improved Supporting Data File Options" +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:16 +msgid "" +"Currently GDAL depends on a variety of supporting data files from the " +"`gdal data <http://svn.osgeo.org/gdal/trunk/gdal/data>`__ directory. The " +"largest part of these are coordinate system dictionaries from EPSG and " +"other sources. It also includes S-57 dictionaries, seed DGN and DXF " +"files, and project logos. Uncompressed it currently comes to roughly " +"1.8MB and it is expected to grow as additional dictionaries are added " +"(for PCI and IAU coordinate systems for instance)." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:24 +msgid "" +"It has also been a frequent problem at run time to find the data files " +"when they are installed in unusual locations." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:27 +msgid "" +"This RFC aims to overhaul support file handling with two new major " +"features." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:30 +msgid "" +"The ability to read from compressed data files to reduce the disk " +"footprint of GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:32 +msgid "" +"The ability to embed the data files with the GDAL DLL or shared library " +"to remove the \"finding\" problem." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:36 +msgid "CPL CSV Access via VSI*L" +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:38 +msgid "" +"The large majority of the support data file access is via the CPL CSV API" +" (gdal/port/cpl_csv.cpp). Finding support data files is done via " +"CPLFindFile(). It turns out these functions are still using the old VSI " +"API which does not support special handlers (like /vsizip/), or in at " +"least one case direct fopen() calls. So the first stage of this RFC is to" +" convert these functions to all use the VSI*L API. A `patch " +"<http://trac.osgeo.org/gdal/attachment/wiki/rfc27_supportdata/rfc27_csv_vsil.patch>`__" +" has been prepared that demonstrates the bulk of the required changes. " +"With this patch it is possible to access files from a GDAL_DATA setting " +"like /vsizip//home/warmerda/gdal/data/gdaldata.zip." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:49 +msgid "" +"Note that we are explicitly changing the contract about the nature of the" +" FILE\\* passed to functions like CSVReadParseLine() (real FILE\\* vs. " +"VSI\\ *L style FILE*). It is possible, though relatively unlikely that " +"application code, or private driver implementations will be using the SV " +"functions and will need to be changed. This change should be noted in the" +" GDAL 1.8 release notes." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:56 +msgid "" +"It is also unclear if there will be bad interactions with the cpl_csv " +"implementation embedded in libgeotiff in some situations, such as when " +"using libgeotiff as an external library. Some review will be needed." +msgstr "" + +#: ../../source/development/rfc/rfc27_supportdata.rst:60 +msgid "" +"Another point to investigate is what the performance impact of doing all " +"the file finding through the VSI*L API will be." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:5 +msgid "RFC 28: OGR SQL Generalized Expressions" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:16 +msgid "" +"The OGR SQL evaluation engine currently does not allow general purpose " +"functions to be applied to columns in SELECT statements. Some special " +"purpose functions are supported (ie. CAST, COUNT, AVG, MAX, MIN, and " +"SUM), but not as part of more general expressions and generally in very " +"constrained arrangements. It is the intent of this work item to extend " +"the OGR SQL engine to support fairly general purpose expression " +"evaluation in the output field list of OGR SQL SELECT statements and to " +"implement a few preliminary processing functions in a fashion compatible " +"with standard SQL. As well, expressions used in WHERE clauses will be " +"generalized to support evaluation of non-logical operations, such as math" +" and functions. For example, after implementation it is intended the " +"following could be evaluated." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:35 +msgid "" +"A prototype implementation is now available for review in " +"`http://svn.osgeo.org/gdal/sandbox/warmerdam/gdal-rfc28 " +"<http://svn.osgeo.org/gdal/sandbox/warmerdam/gdal-rfc28>`__" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:39 +msgid "Technical Approach" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:41 +msgid "" +"Currently logical expressions take a very constrained format with the " +"base elements having to be of the form * <constant_value>*. As part of " +"the generalization non-logical expressions will be supported and the left" +" and right side of operators will be equally treated. The current OGR SQL" +" parser is ad hoc and cannot be practically extended to this generalized " +"form of expression. So at this point we will move to a yacc/bison based " +"parser grammar for expressions." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:49 +msgid "" +"Since it is not really practical to continue to use the existing ad hoc " +"SELECT parsing when parts of the SELECT statement are expressions, the " +"yacc/bison based parser will also be used to parse the whole SELECT " +"statement." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:54 +msgid "" +"The current expression node will be generalized to have 0-n children (for" +" arguments to functions), and to treat field references and constant " +"values as distinct leaf nodes rather than embedding this information in a" +" node defining an operation." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:59 +msgid "" +"It should be noted that as a side effect WHERE clauses will also support " +"more general expressions - not just logical comparisons. For instance:" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:62 +msgid "SELECT \\* WHERE (subtotal+salestax) > 100.0" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:65 +msgid "New Functions" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:67 +msgid "Math: +, -, \\*, /, \\*\\*" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:68 +msgid "String: CONCAT, SUBSTR" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:71 +msgid "SELECT Rules" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:120 +msgid "Special Notes" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:122 +msgid "" +"The existing CAST, and column summary functions COUNT, AVG, MIN, MAX and " +"SUM will be treated more-or-less as functions but constrained to be root " +"operations on column definitions and treated as a special case (still)." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:127 +msgid "Compatibility Implications" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:129 +msgid "" +"Some identifiers that were previously allowed as unquoted field names " +"will likely now have to be quoted as they will be keywords in the " +"grammar. The keyword set is:" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:133 +msgid "IN" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:134 +msgid "LIKE" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:135 +msgid "NULL" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:136 +msgid "IS" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:137 +msgid "SELECT" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:138 +msgid "LEFT" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:139 +msgid "JOIN" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:140 +msgid "WHERE" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:141 +msgid "ON" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:142 +msgid "ORDER" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:143 +msgid "BY" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:144 +msgid "FROM" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:145 +msgid "AS" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:146 +msgid "ASC" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:147 +msgid "DESC" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:148 +msgid "DISTINCT" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:149 +msgid "CAST" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:151 +msgid "" +"The previous implementation was written in C and avoided all use of " +"GDAL/OGR services so that it could be easily used in other contexts, " +"including as the where clause evaluator of the OGDI library. After this " +"update the code is C++, and direct use of CPL error and other services " +"has been directly incorporated. This means the implementation used by " +"GDAL and OGDI will diverge." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:158 +msgid "" +"For the most part the change results in some OGR SQL statements to work " +"that would previously have generated an error." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:162 +msgid "Performance Implications" +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:164 +msgid "" +"I am hopeful that the evaluation speed will not be significantly " +"different for simple selections, but each output field will need to be " +"evaluated as an expression (with presumably one value-from-field node)." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:171 +msgid "" +"Frank Warmerdam will implement, test and document for the GDAL/OGR 1.8 " +"release." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:177 +msgid "" +"All existing OGR SQL test suite tests should pass. A new " +"autotest/ogr/ogr_sql_rfc28.py script will be introduced to test new " +"functionality." +msgstr "" + +#: ../../source/development/rfc/rfc28_sqlfunc.rst:184 +msgid "" +"The :ref:`OGR SQL <ogr_sql_dialect>` document will be extended to " +"describe the new capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:5 +msgid "RFC 29: OGR Set Ignored Fields" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:7 +msgid "Author: Martin Dobias" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:9 +msgid "Contact: wonder.sk@gmail.com" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:16 +msgid "" +"To improve performance when fetching features, this RFC proposes a way " +"how to tell OGR which fields are not going to be required in subsequent " +"GetFeature() / GetNextFeature() calls. Such fields will be ignored by the" +" driver and their value will be kept null. The RFC counts also with the " +"possibility to ignore feature geometry and style." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:22 +msgid "Common use cases:" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:24 +msgid "" +"the client renders the layer: all (or most) fields can be ignored, only " +"the geometry is required" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:27 +msgid "" +"the client shows attribute table: all fields are required, the geometry " +"can be ignored" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:33 +msgid "" +"A new function will be added to OGRLayer class to allow the client to set" +" which fields will *not* be fetched:" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:40 +msgid "and an equivalent call for C API:" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:46 +msgid "" +"The argument is a list of fields to be ignored, by name, and the special " +"field names \"OGR_GEOMETRY\" and \"OGR_STYLE\" will be interpreted to " +"refer to the geometry and style values of a feature." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:50 +msgid "" +"Passing by field name has been chosen so that we could handle " +"OGR_GEOMETRY, OGR_STYLE and possibly some other special fields in the " +"future. Instead of specifying \"desired\" fields, it has been decided to " +"specify \"ignored\" fields so that we wouldn't accidentally drop things " +"like geometry and style just because they weren't explicitly listed in a " +"desired list." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:57 +msgid "Passing NULL for papszFields will clear the ignored list." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:59 +msgid "" +"The method will return OGRERR_NONE as long as all the field names are " +"able to be resolved, even if the method does not support selection of " +"fields." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:63 +msgid "" +"The drivers supporting this method will return TRUE to OLCIgnoreFields " +"(\"IgnoreFields\") capability." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:66 +msgid "" +"The method will be implemented at the level of OGRLayer class: it will " +"resolve indexes of the fields and set the following new member variables " +"which indicate what should be ignored. The flags will be stored within " +"OGRFeatureDefn and OGRFieldDefn classes and available with these getter " +"functions:" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:78 +msgid "" +"The getter member functions will be complemented by setter functions for " +"use by OGRLayer. Setting the \"ignored\" flags directly by clients will " +"be forbidden." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:82 +msgid "" +"Optionally the method ``SetIgnoredFields()`` can be overridden in driver " +"implementation if the driver has some special needs." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:86 +msgid "Implementation in drivers" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:88 +msgid "" +"The implementation of drivers will require small adjustments in order to " +"support this RFC. Drivers not making use of this addition will simply " +"continue to fetch also fields/geometry/style that are not requested by " +"the caller." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:93 +msgid "The adjustments in driver implementation will look as follows:" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:117 +msgid "" +"This change is fully backwards compatible: OGR will continue to fetch " +"geometry, style and all fields by default. Only applications using the " +"proposed API will experience the new behavior." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:121 +msgid "" +"Initially, only some drivers (Shapefile and few others) will implement " +"this RFC. There is no need to modify all existing drivers when adopting " +"the RFC - drivers that do not consider the ignored fields will simply " +"fetch all attributes as before. To check whether a driver supports this " +"RFC, OLCIgnoreFields capability can be checked." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:127 +msgid "" +"ogr2ogr command line tool will make use of this RFC in cases it receives " +"-select argument with a list of required fields. Other than the specified" +" fields will be ignored." +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:136 +msgid "Daniel Morissette +0" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:137 +#: ../../source/development/rfc/rfc6_sqlgeom.rst:469 +msgid "Howard Butler +0" +msgstr "" + +#: ../../source/development/rfc/rfc29_desired_fields.rst:138 +msgid "Even Rouault +0" +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:5 +msgid "RFC 2: Migration to OSGeo Subversion Repository" +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:16 +msgid "" +"It is proposed that the GDAL source tree be moved a subversion repository" +" in such a manner as to preserve the history existing in the CVS " +"repository. A 1.3.x branch will be created after automatic updating of " +"the header format." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:24 +msgid "The conversion will be done by Howard Butler using the cvs2svn tool." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:25 +msgid "" +"At least 24 hours notice will be provided before the transition starts to" +" allow committers to commit any outstanding work that is ready to into " +"the repository." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:28 +msgid "" +"When the conversion starts, the GDAL (and gdalautotest) trees will be " +"removed from cvs.maptools.org, and archived to avoid any confusion." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:30 +msgid "" +"Frank Warmerdam will modify the \"daily cvs snapshot\" capability to work" +" from SVN." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:32 +msgid "" +"Frank will be responsible for updating the source control information in " +"the documentation." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:34 +msgid "" +"All source files in SVN will have the svn:keywords property set to \"Id\"" +" by Frank after they are created." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:36 +msgid "" +"Committers will need to get a login on osgeo.org and notify Frank to " +"regain commit access. Committer access on the new repository will be " +"enabled after the above changes are all complete." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:39 +msgid "" +"The GDAL committers document should be updated, removing non-GDAL " +"committers (ie. libtiff, geotiff, etc)." +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:43 +msgid "Header Format" +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:45 +msgid "" +"SVN does not support history insertion in source files, and to keep the " +"old history listings around without keeping them up to date would be very" +" confusing. So it is proposed that Frank Warmerdam write a script to " +"strip the history logs out. Changing this:" +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:75 +msgid "to this:" +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:98 +msgid "Branch for 1.3" +msgstr "" + +#: ../../source/development/rfc/rfc2_svn.rst:100 +msgid "" +"Once the headers have been updated appropriately, a 1.3 branch will be " +"established in subversion. The intent is that further 1.3.x releases " +"would be made against this \"stable branch\" while trunk work is towards " +"a 1.4.0 release targeted for around the time of the OSGeo conference." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:5 +msgid "RFC 30: Unicode Filenames" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:16 +msgid "" +"This document describes steps to generally handle filenames as UTF-8 " +"strings in GDAL/OGR. In brief it will be assumed that filenames passed " +"into and returned by GDAL/OGR interfaces are UTF-8. On some operating " +"systems, notably Windows, this will require use of \"wide character\" " +"interfaces in the low level VSI*L API." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:23 +msgid "Key Interfaces" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:26 +msgid "VSI*L API" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:28 +msgid "" +"All filenames in the VSI*L API will be treated as UTF-8, which means the " +"cpl_vsil_win32.cpp implementation will need substantial updates to use " +"wide character interfaces." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:32 +msgid "VSIFOpenL()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:33 +msgid "VSIFStatL()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:34 +msgid "VSIReadDir()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:35 +msgid "VSIMkdir()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:36 +msgid "VSIRmdir()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:37 +msgid "VSIUnlink()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:38 +msgid "VSIRename()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:41 +msgid "Old (small file) VSI API" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:43 +msgid "" +"The old VSIFOpen() function will be adapted to use \\_wfopen() on windows" +" instead of fopen() so that utf-8 filenames will be supported." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:46 +msgid "VSIFOpen()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:47 +msgid "VSIStat()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:50 +msgid "Filename Parsing" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:52 +msgid "" +"Because the path/extension delimiter characters '.', '', '/' and ':' will" +" never appear in the non-ascii portion of utf-8 strings we can safely " +"leave the existing path parsing functions working as they do now. They do" +" not need to be aware of the real character boundaries for exotic " +"characters in utf-8 paths. The following will be left unchanged." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:58 +msgid "CPLGetPath()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:59 +msgid "CPLGetDirname()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:60 +msgid "CPLGetFilename()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:61 +msgid "CPLGetBasename()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:62 +msgid "CPLGetExtension()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:63 +msgid "CPLResetExtension()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:66 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:506 +msgid "Other" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:68 +msgid "CPLStat()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:69 +msgid "CPLGetCurrentDir()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:70 +msgid "GDALDataset::GetFileList()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:72 +msgid "These will all also need to treat filenames as utf-8." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:75 +msgid "Windows" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:77 +msgid "" +"Currently Windows's cpl_vsil_win32.cpp module uses CreateFile() with " +"ascii filenames. It needs to be converted to use CreateFileW() and other " +"wide character functions for stat(), rename, mkdir, etc. Prototype " +"implementation already developed (r20620)." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:85 +msgid "Linux / Unix / MacOS X" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:87 +msgid "" +"On modern linux, unix and MacOS operating systems the fopen(), stat(), " +"readdir() functions already support UTF-8 strings. It is not currently " +"anticipated that any work will be needed on Linux/Unix/MacOS X though " +"there is some question about this. It is considered permissible under the" +" definition of this RFC for old, and substandard operating systems " +"(WinCE?) to support only ASCII, not UTF-8 filenames." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:95 +msgid "Metadata" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:97 +msgid "" +"There are a variety of places where general text may contain filenames. " +"One obvious case is the subdataset filenames returned from the SUBDATASET" +" domain. Previously these were just exposed as plain text and " +"interpretation of the character set was undefined. As part of this RFC we" +" state that such filenames should be considered to be in utf-8 format." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:104 +msgid "Python Changes" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:106 +msgid "" +"I observe with Python 2.6 that functions like gdal.Open() do not accept " +"unicode strings, but they do accept utf-8 string objects. One possible " +"solution is to update the bindings in selective places to identify " +"unicode strings passed in, and transform them to utf-8 strings." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:111 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:87 +msgid "eg." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:119 +msgid "" +"I'm not sure what the easiest way is to accomplish this in the bindings. " +"The key entries are:" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:122 +msgid "gdal.Open()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:123 +msgid "ogr.Open()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:124 +msgid "gdal.ReadDir()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:125 +msgid "gdal.PushFinderLocation()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:126 +msgid "gdal.FindFile()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:127 +msgid "gdal.Unlink()" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:129 +msgid "" +"Similarly all interfaces (ie. gdal.ReadDir()) that return filenames will " +"hereafter return unicode objects rather than string objects." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:132 +msgid "Also note that in Python 3.x strings are always unicode." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:135 +msgid "C# Changes" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:137 +msgid "" +"Tamas notes that in C# we normally convert the unicode C# strings into C " +"string with the PtrToStringAnsi marshaller. Presumably we will need to " +"use a utf-8 converter for all interface strings considered to be " +"filenames. I would note this should also apploy to OGR string attribute " +"values which are also intended to be treated as utf-8." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:143 +msgid "" +"(It is unclear who will take care of this aspect since the primary author" +" (FrankW) is not C#-binding-competent." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:147 +msgid "Perl Changes" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:149 +msgid "" +"The general rule in Perl is that all strings should be decoded before " +"giving them to Perl and encoded when they are output. In practice things " +"usually just work. To be sure, I (Ari) have added an explicit decode from" +" utf8 to FindFile and ReadDir (#20800)." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:155 +msgid "Java Changes" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:157 +msgid "" +"No changes are needed for Java. Java strings are unicode, and they are " +"already converted to utf-8 in the java swig bindings. That is, the java " +"bindings already assumed passing and receiving utf-8 strings to/from " +"GDAL/OGR." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:163 +msgid "Commandline Issues" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:165 +msgid "" +"On windows argv[] as passed into main() will not generally be able to " +"represent exotic filenames that can't be represented in the locale " +"charset. It is possible to fetch the commandline and parse it as wide " +"characters using GetCommandLineW() and CommandLinetoArgvW() to capture " +"ucs-16 filenames (easily converted to utf-8); however, this interferes " +"with the use of setargv.obj to expand wildcards on windows." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:172 +msgid "" +"I have not been able to come up with a good solution, so for now I am not" +" intending to make any changes to the GDAL/OGR commandline utilities to " +"allow passing exotic filenames. So this RFC is mainly aimed at ensuring " +"that other applications using GDAL/OGR can utilize exotic filenames." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:179 +#: ../../source/development/rfc/rfc31_ogr_64.rst:201 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:388 +msgid "File Formats" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:181 +msgid "" +"The proposed implementation really only addresses file format drivers " +"that use VSIFOpenL(), VSIFOpen() and related functions. Some drivers " +"dependent on external libraries (ie. netcdf) do not have a way to hook " +"the file IO API and may not support utf-8 filenames. It might be nice to " +"be able to distinguish these." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:187 +msgid "" +"At the very least any driver marked with GDAL_DCAP_VIRTUALIO as \"YES\" " +"will support UTF-8. Perhaps this opportunity ought to be used to more " +"uniformly apply this driver metadata (done)." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:192 +#: ../../source/development/rfc/rfc31_ogr_64.rst:295 +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:102 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:109 +#: ../../source/development/rfc/rfc34_license_policy.rst:222 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:269 +#: ../../source/development/rfc/rfc45_virtualmem.rst:1250 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:435 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:541 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:73 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:89 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:742 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:161 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:269 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:344 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:123 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:268 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:74 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:255 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:159 +msgid "Test Suite" +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:194 +msgid "" +"We will need to introduce some test suite tests with multibyte utf-8 " +"filenames. In support of that aspects of the VSI*L API - particularly the" +" rename, mkdir, rmdir, functions and VSIFOpenL itself have been exposed " +"in python." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:202 +msgid "" +"Appropriate API entry points will be documented as taking and return " +"UTF-8 strings." +msgstr "" + +#: ../../source/development/rfc/rfc30_utf8_filenames.rst:208 +msgid "Implementation is underway and being tracked in ticket #3766." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:5 +msgid "RFC 31: OGR 64bit Integer Fields and FIDs" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:7 +msgid "Authors: Frank Warmerdam, Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:9 +msgid "Contact: warmerdam@pobox.com, even dot rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:11 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:11 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:11 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:11 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:11 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:11 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:11 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:11 +msgid "Status: Adopted, implemented in GDAL 2.0" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:16 +msgid "" +"This RFC addresses steps to upgrade OGR to support 64bit integer fields " +"and feature ids. Many feature data formats support wide integers, and the" +" inability to transform these through OGR causes increasing numbers of " +"problems." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:24 +msgid "64bit FID, feature index and feature count" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:26 +msgid "" +"Feature id's will be handled as type \"GIntBig\" instead of \"long\" " +"internally. This will include the nFID field of the OGRFeature. The " +"existing GetFID() and SetFID() methods on the OGRFeature use type long " +"and are changed to return (respectively accept) GIntBig instead. The " +"change of return type for GetFID() will require application code to " +"carefully adapt to avoid potential issues (for example if GetFID() is " +"used in printf-like expression). SetFID() change should be mostly " +"transparent. So the changes in the OGRFeature class are:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:40 +msgid "At the C API level:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:47 +msgid "" +"Note that the old interfaces using \"long\" are already 64bit on 64bit " +"operating systems (excluding Windows target compilers where long is 32bit" +" even on 64bit builds), so there is little harm to applications " +"continuing to use these interfaces on 64bit operating systems." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:52 +msgid "" +"A layer that can discover in a relatively cheap way that it holds " +"features with 64bit FID should advertise the OLMD_FID64 metadata item to " +"\"YES\", so ogr2ogr can pass the FID64 creation option to drivers that " +"support it." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:57 +msgid "" +"The OGRLayer class allows several operations based on the FID. The " +"signature of these will be *altered* to accept GIntBig instead of long. " +"In theory this should not require any changes to application code since " +"long can be converted to GIntBig losslessly. However, all existing OGR " +"drivers require changes, including private drivers. This will also result" +" in a backwards incompatible change in the C ABI. While we are at it, we " +"want GetFeatureCount() to be able to return more than 2 billion record " +"(currently returning 32 bit integer), and thus it will return GIntBig. " +"Similarly to GetFID(), this change of return type will require caution in" +" application code." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:68 +msgid "So at the OGRLayer C++ class level:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:77 +msgid "At the C API level :" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:89 +msgid "64bit Fields" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:91 +msgid "New field types will be introduced for 64bit integers:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:98 +msgid "The OGRField union will be extended to include:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:108 +msgid "The OGRFeature class will be extended with these new methods:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:124 +msgid "At the C level, the following functions are added :" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:133 +msgid "" +"Furthermore, the new interfaces will internally support setting/getting " +"integer fields, and the integer field methods will support " +"getting/setting 64bit integer fields so that one case can be used for " +"both field types where convenient (except GetFieldAsInteger64List() that " +"can only operate on Integer64List fields)" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:139 +msgid "" +"A GDAL_DMD_CREATIONFIELDDATATYPES = \"DMD_CREATIONFIELDDATATYPES\" driver" +" metadata item is added so as drivers to be able to declare the field " +"types they support on creation. For example \"Integer Integer64 Real " +"String Date DateTime Time IntegerList Integer64List RealList StringList " +"Binary\". Commonly used drivers will be updated to declare it." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:146 +#: ../../source/development/rfc/rfc31_ogr_64.rst:302 +msgid "OGR SQL" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:148 +msgid "" +"A SWQ_INTEGER64 internal type is added so as to be able to map/from " +"OFTInteger64 fields. The int_value member of the swq_expr_node class is " +"extended from int to GIntBig (so both SWQ_INTEGER and SWQ_INTEGER64 refer" +" to that member)." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:156 +msgid "Python / Java / C# / perl Changes" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:158 +msgid "The following changes have been done :" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:160 +msgid "GetFID(), GetFeatureCount() have been changed to return a 64 bit integer" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:162 +msgid "" +"SetFID(), GetFeature(), DeleteFeature(), SetNextByIndex() have been " +"changed to accept a 64 bit integer as argument" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:164 +msgid "GetFieldAsInteger64() and SetFieldInteger64() have been added" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:165 +msgid "In Python, GetField(), SetField() can accept/return 64 bit values" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:166 +msgid "" +"GetFieldAsInteger64List() and SetFieldInteger64List() have been added " +"(Python only, due to lack of relevant typemaps for other languages, but " +"could potentially be done)" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:170 +msgid "" +"The change in return type of GetFID() and GetFeatureCount() might cause " +"warnings at compilation time in some languages (Java YES, Python not " +"relevant, Perl/C# ?). All changes to existing methods will are an ABI " +"change for Java bytecode." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:178 +msgid "ogr2ogr and ogrinfo are updated to support the new 64bit interfaces." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:180 +msgid "" +"A new option is added to ogr2ogr : -mapFieldType. Can be used like this " +"-mapFieldType Integer64=Integer,Date=String to mean that Integer64 field " +"in the source layer should be created as Integer, and Date as String. " +"ogr2ogr will also warn if attempting to create a field in an output " +"driver that advertises a GDAL_DMD_CREATIONFIELDDATATYPES metadata item " +"that does not mention the required field type. For Integer64 fields, if " +"it is not advertized in GDAL_DMD_CREATIONFIELDDATATYPES metadata item or " +"GDAL_DMD_CREATIONFIELDDATATYPES is missing, conversion to Real is done by" +" default with a warning. ogr2ogr will also query the source layer to " +"check if the OLMD_FID64 metadata item is declared and if the output " +"driver has the FID64 layer creation option. In which case it will set it." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:196 +msgid "" +"New/modified API are documented. Updates in drivers with new " +"options/behaviours are documented. MIGRATION_GUIDE.TXT extended with a " +"section related to this RFC. OGR API updated." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:203 +msgid "" +"As appropriate, existing OGR drivers have been updated to support the " +"new/updated interfaces. In particular an effort has been made to update a" +" few database drivers to support 64bit integer columns for use as feature" +" id, though they don't always create FID columns as 64bit by default when" +" creating new layers as this may cause problems for other applications." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:210 +msgid "" +"Apart from the mechanical changes due to interface changes, the detailed " +"list of changes is :" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:213 +msgid "" +"Shapefile: OFTInteger fields are created by default with a width of 9 " +"characters, so to be unambiguously read as OFTInteger (and if specifying " +"integer that require 10 or 11 characters. the field is dynamically " +"extended like managed since a few versions). OFTInteger64 fields are " +"created by default with a width of 18 digits, so to be unambiguously read" +" as OFTInteger64, and extended to 19 or 20 if needed. Integer fields of " +"width between 10 and 18 will be read as OFTInteger64. Above they will be " +"treated as OFTReal. In previous GDAL versions, Integer fields were " +"created with a default with of 10, and thus will be now read as " +"OFTInteger64. An open option, ADJUST_TYPE=YES, can be specified so as OGR" +" does a full scan of the DBF file to see if integer fields of size 10 or " +"11 hold 32 bit or 64 bit values and adjust the type accordingly (and same" +" for integer fields of size 19 or 20, in case of overflow of 64 bit " +"integer, OFTReal is chosen)" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:228 +msgid "" +"PG: updated to read and create OFTInteger64 as INT8 and OFTInteger64List " +"as bigint[]. 64 bit FIDs are supported. By default, on layer creation, " +"the FID field is created as a SERIAL (32 bit integer) to avoid " +"compatibility issues. The FID64=YES creation option can be passed to " +"create it as a BIGSERIAL instead. If needed, the drivers will dynamically" +" alter the schema to extend a 32 bit integer FID field to 64 bit. " +"GetFeatureCount() modified to return 64 bit values. OLMD_FID64 = \"YES\" " +"advertized as soon as the FID column is 64 bit." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:237 +msgid "" +"PGDump: Integer64, Integer64List and 64 bit FID supported in read/write. " +"FID64=YES creation option available." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:239 +msgid "" +"GeoJSON: Integer64, Integer64List and 64 bit FID supported in read/write." +" The 64 bit variants are reported only if needed, otherwise " +"OFTInteger/OFTIntegerList is used. OLMD_FID64 = \"YES\" advertized if " +"needed" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:243 +msgid "" +"CSV: Integer64 supported in read/write, including the autodetection " +"feature of field types." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:245 +msgid "" +"GPKG: Integer64 and 64 bit FID supported in read/write. Conforming with " +"the GeoPackage spec, \"INT\" or \"INTEGER\" columns are considered 64 " +"bits, whereas \"MEDIUMINT\" is considered 32 bit. OLMD_FID64 = \"YES\" " +"advertized as soon as MAX(fid_column) is 64 bit. GetFeatureCount() " +"modified to return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:250 +msgid "" +"SQLite: Integer64 and 64 bit FID supported in read/write. On write, " +"Integer64 are createad as \"BIGINT\" and on read BIGINT or INT8 are " +"considered as Integer64. However it might be possible that databases " +"produced by other tools are created with \"INTEGER\" and hold 64 bit " +"values, in which case OGR will not be able to detect it. The " +":config:`OGR_PROMOTE_TO_INTEGER64=YES` configuration option can then be " +"passed to workaround that issue. OLMD_FID64 = \"YES\" advertized as soon " +"as MAX(fid_column) is 64 bit. GetFeatureCount() modified to return 64 bit" +" values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:259 +msgid "" +"MySQL: Integer64 and 64 bit FID supported in read/write. Similarly to PG," +" FID column is created as 32 bit by default, unless FID64=YES creation " +"option is specified. OLMD_FID64 = \"YES\" advertized as soon as the FID " +"column is 64 bit. GetFeatureCount() modified to return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:264 +msgid "" +"OCI: Integer64 and 64 bit FID supported in read/write. Detecting " +"Integer/Integer64 on read is tricky since there's only a NUMBER SQL type " +"with a field width. It is assumed that if the width is <= 9 or if it is " +"the unspecified value (38), then it is a Integer. On creation, OGR will " +"set a width of 20 for OFTInteger64, so a NUMBER without decimal part and " +"with a width of 20 will be considered as a Integer64." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:271 +msgid "" +"MEM: Integer64 and 64 bit FID supported in read/write. GetFeatureCount() " +"modified to return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:273 +msgid "" +"VRT: Integer64, Integer64List and 64 bit FID supported in read/write. " +"GetFeatureCount() modified to return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:275 +msgid "" +"JML: Integer64 supported on creation (created as \"OBJECT\"). On read, " +"returned as String" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:277 +msgid "" +"GML: Integer64, Integer64List and 64 bit FID supported in read/write. " +"GetFeatureCount() modified to return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:279 +msgid "" +"WFS: Integer64, Integer64List and 64 bit FID supported in read/write. " +"GetFeatureCount() modified to return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:281 +msgid "" +"CartoDB: Integer64 supported on creation. On read returned as Real " +"(CartoDB only advertises a 'Number' type). GetFeatureCount() modified to " +"return 64 bit values." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:284 +msgid "XLSX: Integer64 supported in read/write." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:285 +msgid "ODS: Integer64 supported in read/write." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:286 +msgid "" +"MSSQLSpatial: GetFeatureCount() modified to return 64 bit values. No " +"Integer64 support implemented although could likely be done." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:288 +msgid "OSM: FID is now always set even when sizeof(long) != 8" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:289 +msgid "LIBKML: KML 'uint' advertized as Integer64." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:290 +msgid "" +"MITAB: Change the way FID of Seamless tables are generated to make it " +"more robust and accept arbitrary number of index tables made of an " +"arbitrary number of features, by using full 64bit width of IDs" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:297 +msgid "The test suite is extended to test the new capabilities:" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:299 +msgid "core SetField/GetField methods" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:300 +msgid "" +"updated drivers: Shapefile, PG, GeoJSON, CSV, GPKG, SQLite, MySQL, VRT, " +"GML, XLSX, ODS, MITAB" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:303 +msgid "option -mapFieldType of ogr2ogr" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:309 +msgid "Driver Code Changes" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:311 +msgid "" +"All drivers implementing SetNextByIndex(), DeleteFeature(), GetFeature()," +" GetFeatureCount() will need to change their prototype and do modest " +"changes." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:315 +msgid "" +"Drivers supporting CreateField() likely ought to be extended to support " +"OFTInteger64 as an integer/real/string field if nothing else is available" +" (and if bApproxOK is TRUE). ogr2ogr will convert Integer64 to Real if " +"Integer64 support is not advertized" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:320 +msgid "" +"Drivers reporting FIDs via Debug statements, printf's or using sprintfs " +"like statements to format them for output have been updated to use " +"CPL_FRMT_GIB to format the FID. Failure to make these changes may result " +"in code crashing. Due to the use of GCC annotation to advertise " +"printf()-like formatting syntax in CPL functions, we are reasonably " +"confident to have done the required changes in in-tree drivers (except in" +" some proprietary drivers, like SDE, IDB, INGRES, ArcObjects, where this " +"couldn't be compiled-checked). The same holds true for GetFeatureCount()" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:331 +msgid "Application Code" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:333 +msgid "" +"Application code may need to be updated to use GIntBig for FIDs and " +"feature count in order to avoid warnings about downcasting." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:336 +msgid "" +"Application code formatting FIDs or feature count using printf like " +"facilities may also need to be changed to downcast explicitly or to use " +"CPL_FRMT_GIB." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:340 +msgid "" +"Application code may need to add Integer64 handling in order to utilize " +"wide fields." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:344 +msgid "Behavioral Changes" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:346 +msgid "" +"Wide integer fields that were previously treated as \"real\" or Integer " +"by the shapefile driver will now be treated as Integer64 which will " +"likely not work with some applications, and translation to other formats " +"may fail." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:352 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:580 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:388 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:131 +msgid "Related tickets" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:354 +msgid "" +"`#3747 OGR FID needs to be 64 bit " +"<http://trac.osgeo.org/gdal/ticket/3747>`__" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:356 +msgid "" +"`#3615 Shapefile : A 10-digit value doesn't necessarily fit into a 32 bit" +" integer. <http://trac.osgeo.org/gdal/ticket/3615>`__" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:358 +msgid "" +"`#3150 Precision Problem for Numeric on OGR/OCI driver " +"<http://trac.osgeo.org/gdal/ticket/3150>`__" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:362 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:465 +msgid "Related topics out of scope of this RFC" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:364 +msgid "" +"The possibility of having a Numeric type that corresponds to the matching" +" SQL type, i.e. a decimal number with an arbitrary number of significant " +"figures has been considered. In OGR, this could be implemented as a full " +"type like Integer, Integer64 etc., or possibly as a subtype of String " +"(see `RFC 50: OGR field subtypes <./rfc50_ogr_field_subtype>`__). The " +"latter approach would be easier to implement and mostly useful for " +"lossless conversion between database drivers (and shapefile). The former " +"approach would require more work, and would ideally involve OGR SQL " +"support, which would require supporting arithmetic of arbitrary length. " +"The use cases for such a numeric type have been considered marginal " +"enough to let that aside for now." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:380 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:502 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:592 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:87 +msgid "" +"Implementation will be done by Even Rouault (`Spatialys " +"<http://spatialys.com>`__), and sponsored by `LINZ (Land Information New " +"Zealand) <http://www.linz.govt.nz/>`__." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:384 +msgid "" +"The proposed implementation lies in the \"rfc31_64bit\" branch of the " +"`https://github.com/rouault/gdal2/tree/rfc31_64bit " +"<https://github.com/rouault/gdal2/tree/rfc31_64bit>`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:388 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/rfc31_64bit " +"<https://github.com/rouault/gdal2/compare/rfc31_64bit>`__" +msgstr "" + +#: ../../source/development/rfc/rfc31_ogr_64.rst:394 +msgid "+1 from JukkaR, DanielM, TamasS, HowardB and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:5 +msgid "RFC 32: gdallocationinfo utility" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:16 +msgid "" +"This document proposes the addition of a new standard commandline utility" +" for GDAL to report details about a location (pixel) in a raster." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:20 +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:23 +#: ../../source/development/rfc/rfc34_license_policy.rst:41 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:21 +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:21 +#: ../../source/development/rfc/rfc45_virtualmem.rst:21 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:24 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:21 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:24 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:24 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:23 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:22 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:22 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:29 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:23 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:25 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:22 +msgid "Rationale" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:22 +msgid "" +"A user has a use case where they would like to be able to identify the " +"VRT file used to satisfy requests for a particular pixel / location." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:26 +msgid "" +"Many users have requested a tool to find the value of a location, often " +"expressed in a coordinate system different than that of the image. For " +"instance, \"what is the elevation at a given lat/long location?\"." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:31 +msgid "" +"The gdallocationinfo utility is intended to address both sorts of " +"requests, and hopefully in a way that will have some general value as a " +"\"raster point query\" tool." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:36 +msgid "gdallocationinfo" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:38 +msgid "Full docs are available at :ref:`gdallocationinfo`" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:46 +msgid "" +"The key aspects of the utility are control over the coordinate system of " +"the location (-s_srs, -geoloc, -wgs84) and various controls over the " +"output format (-xml, -lifonly, -valonly). An example of full output in " +"xml might be:" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:64 +msgid "LocationInfo Metadata Domain" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:66 +msgid "" +"The pixel values and location transformation logic is all built into " +"gdallocationinfo and doesn't require much elaboration. The more exotic " +"portion is reporting of \"LocationInfo\" queried from the datasource." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:70 +msgid "" +"For our immediate needs the requirement is to have the " +"VRTSourcedRasterBand return information on the file(s) overlapping the " +"target pixel. But, in theory different drivers might return different " +"sorts of information about a location. For instance, a WMS driver might " +"issue a GetFeatureInfo for the location and return the result." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:76 +msgid "" +"The mechanism to query the datasource is a specially named " +"GetMetadataItem() request against the \"LocationInfo\" domain of the " +"target band(s). The following requested item name is of the form " +"\"Pixel_x_y\" where x and y are the pixel and line of the pixel being " +"queried." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:82 +msgid "" +"The returned value from this item should either be NULL, or an XML " +"documented with the root element \"\". The contents of the document are " +"otherwise undefined as long as they are well formed XML. The VRT driver " +"returns a series of xxx entries for each of the files at that location." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:93 +msgid "might return:" +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:104 +msgid "" +"A test will be introduced in the gdal utilities suite, and the " +"gdrivers/vrt.py script for the utility and VRT behavior respectively." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:110 +msgid "" +"Documentation for the utility has already been prepared and is referenced" +" above." +msgstr "" + +#: ../../source/development/rfc/rfc32_gdallocationinfo.rst:116 +msgid "" +"Implementation is already complete, and in trunk. Adjustments can be made" +" by Frank Warmerdam as needed due to RFC revisions." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:5 +msgid "RFC 33: GTiff - Fixing PixelIsPoint Interpretation" +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:16 +msgid "" +"This document proposes changes in the GDAL GTiff (GeoTIFF) driver's " +"interpretation of PixelIsPoint when constructing the geotransform and " +"interpreting control points. An RFC is used due to the fundamental role " +"of GeoTIFF in GDAL and the GDAL user community and the risk for " +"significant backward compatibility problems with this adjustment." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:25 +msgid "" +"The GeoTIFF specification includes a data item, GTRasterTypeGeoKey, which" +" may be set to either RasterPixelIsArea (the default), or " +"RasterPixelIsPoint. RasterPixelIsArea defines that a pixel represents an " +"area in the real world, while RasterPixelIsPoint defines a pixel to " +"represent a point in the real world. Often this is useful to distinguish " +"the behavior of optical sensors that average light values over an area " +"vs. raster data which is point oriented like an elevation sample at a " +"point." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:34 +msgid "" +"Traditionally GDAL has treated this flag as having no relevance to the " +"georeferencing of the image despite disputes from a variety of other " +"software developers and data producers. This was based on the authors " +"interpretation of something said once by the GeoTIFF author. However, a " +"recent review of section [`section 2.5.2.2 " +"<http://www.remotesensing.org/geotiff/spec/geotiff2.5.html#2.5.2.2>`__] " +"of the GeoTIFF specificaiton has made it clear that GDAL behavior is " +"incorrect and that PixelIsPoint georeferencing needs to be offset by a " +"half a pixel when transformed to the GDAL georeferencing model. This " +"issue is documented in the following tickets including #3837, #3838, ...." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:46 +msgid "" +"This RFC attempts to manage this transition with a minimum of disruption " +"for the users of GDAL/OGR." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:50 +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:35 +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:50 +msgid "Planned Changes" +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:52 +msgid "" +"Interpretation of the raster space from the GeoTIFF tie points will be " +"offset by half a pixel in the PixelIsPoint case in " +"gdal/frmts/gtiff/geotiff.cpp. This will impact the formation of the " +"geotransform and the formation of GCPs when there are multiple tie " +"points. geotransmatrix conversion to geotransform will also be affected." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:58 +msgid "" +"Conversely if writing files with PixelIsPoint (as driven by the " +"\"AREA_OR_POINT\" metadata item being set to \"POINT\") the written " +"raster space coordinates would be offset by half a pixel." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:62 +msgid "" +"In trunk the above behavior may be disabled by setting the " +"GTIFF_POINT_GEO_IGNORE configuration option to TRUE (it will default to " +"FALSE)." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:66 +msgid "" +"In GDAL 1.7 and 1.6 branch the same changes will be applied, except the " +"GTIFF_POINT_GEO_IGNORE configuration option will default to TRUE." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:72 +msgid "" +"This change will alter the apparent georeferencing of all GeoTIFF files " +"with PixelIsPoint set. It is not clear how large a proportion of GeoTIFF " +"files this will apply to, but it is significant. This isn't too bad for " +"files coming from non-GDAL sources as most other produces have made the " +"correct interpretation of PixelIsPoint for years. However, unfortunately," +" files produced in the past by GDAL with PixelIsPoint will now be " +"interpreted differently and the values will be off by half a pixel." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:81 +msgid "" +"In practice it was not particularly convenient or well documented how to " +"produce PixelIsPoint GeoTIFF files with GDAL, so these files should be " +"fairly rare. Thee easiest way to produce them was by copying from another" +" PixelIsPoint GeoTIFF file in which the error on write just undid the " +"error when reading the source GeoTIFF file." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:88 +msgid "Reporting Extents" +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:90 +msgid "" +"Folks have at various points in the past requested that we report the " +"extents differently for files with an AREA_OR_POINT value of POINT, much " +"as listgeo does for GeoTIFF files that have a PixelIsPoint " +"interpretation. I do *not* plan to do this, and for the purpose of GDAL " +"the GCPs, RPCs and GeoTransform will always be based on an area " +"interpretation of pixels. The AREA_OR_POINT will *only* be used to " +"control setting of the PixelIsPoint value in GeoTIFF files, and as " +"metadata about the physical interpretation of pixels." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:100 +msgid "World Files" +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:102 +msgid "" +"These changes will have no impact on how world files are treated or " +"written. They are always based on the assumption of a area based pixel, " +"but with the origin at the center of the top left pixel. This is " +"effectively the same as the values for PixelIsPoint, but is not in any " +"way tried to this metadata." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:111 +msgid "The 1.6 and 1.7 branch test suites will not be altered." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:113 +msgid "" +"The trunk branch test suite will be altered to check for the updated " +"values and will be extended with a test to confirm that setting the " +"config option GTIFF_POINT_GEO_IGNORE to TRUE suppresses the altered " +"behavior." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:121 +msgid "" +"The situation will be noted in the 1.8.0, 1.7.4 and 1.6.4 release notes " +"as well as in the GeoTIFF driver documentation in trunk." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:124 +msgid "" +"The GeoTIFF web site GeoTIFF FAQ will be updated to clarify the " +"interpretation of PixelIsPoint and note that up to GDAL 1.8 it was " +"improperly interpreted by GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:131 +msgid "All code implementation will be by Frank Warmerdam in the next few weeks." +msgstr "" + +#: ../../source/development/rfc/rfc33_gtiff_pixelispoint.rst:134 +msgid "" +"Applied in trunk (r21158), 1.7 (r21159), 1.6 (r21160) and 1.6-esri " +"(r21161)." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:5 +msgid "RFC 34: License Policy Enforcement" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:16 +msgid "" +"This document proposes the addition of a new mechanisms so that " +"applications and end users can define a license policy, and so that GDAL " +"can help avoid license conflicts between proprietary and reciprocally " +"licensed applications and format drivers." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:24 +msgid "" +"Reciprocal FOSS License: A open source software license, such as the GPL," +" that requires all other software components linked into the same " +"executable and distributed beyond the creator to also be offered under " +"open source terms." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:29 +msgid "" +"Non-Reciprocal FOSS License: A open source software license, such as MIT," +" BSD or LGPL, that does not place any requirements on other linked " +"components in the same executable at distribution time." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:33 +msgid "" +"Proprietary License: Software provided under terms that do not adhere to " +"the requirements of the open source definition, such as libraries from " +"Oracle (OCI), Lizardtech (MrSID) and Erdas (ECW). While often offered for" +" zero cost, these components are incompatible with reciprocal FOSS " +"licenses and may place a variety of other restrictions on the distributor" +" or end user." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:43 +msgid "" +"GDAL/OGR is distributed under the Non-Reciprocal MIT open source license " +"which facilitates it's use by proprietary and open source applications, " +"and facilitates the inclusion of proprietary format drivers along side " +"the open source format drivers. However, it is still a license violation " +"to distribute reciprocally licensed applications (like QGIS and GRASS) " +"which use GDAL with proprietary licensed drivers (such as the MrSID, ECW " +"or Oracle drivers). Likewise, it is a license violation to distribute " +"proprietary applications with reciprocally licensed drivers such as the " +"GDAL GRASS driver, or the PDF driver." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:53 +msgid "" +"This RFC, and the improvements it promotes are intended to facilitate " +"users, applications and drivers setting and following license policies to" +" avoid unintentional license violations. One area this can be " +"particularly helpful is broad software distributions like `OSGeo4W " +"<http://osgeo4w.osgeo.org>`__." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:60 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:85 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:22 +msgid "Approach" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:62 +msgid "" +"The general approach proposed is that drivers will declare their license " +"category, and applications or end users will declare a policy for what " +"sorts of drivers may be used in combination with them. The " +"GDALDriverManager and OGRDriverRegistrar classes will apply this " +"information to avoid unintentional license violations." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:69 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:449 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:210 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:305 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:102 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:185 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:225 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:116 +msgid "Drivers" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:71 +msgid "" +"Drivers will declare one of these three driver specific licensing " +"policies via the \"LICENSE_POLICY\" (DMD_LICENSE_POLICY) metadata item on" +" the driver:" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:75 +msgid "" +"\"RECIPROCAL\": the driver is available under a reciprocal FOSS license " +"such as the GPL, and should not be mixed with proprietary drivers or " +"applications." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:78 +msgid "" +"\"NONRECIPROCAL\": the driver is available under a non-reciprocal FOSS " +"license such as MIT, or LGPL. This is the default if no licensing policy " +"is declared and is the natural policy of drivers provided as part of GDAL" +" without outside dependencies." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:82 +msgid "" +"\"PROPRIETARY\": the driver, usually due to use of proprietary libraries," +" has some licensing restrictions which make it ineligible for " +"distribution with reciprocally licensed software. This would include " +"MrSID, ECW, and Oracle related drivers." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:88 +msgid "Application License Policy" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:90 +msgid "" +"Applications are encouraged to set one of the following licensing " +"policies reflective of the applications nature. The policy should be set " +"as the value of the GDAL_APPLICATION_LICENSE_POLICY configuration " +"variable, typically via a call to GDALSetConfigOption() *before* the call" +" to GDALAllRegister() or OGRRegisterAll()." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:96 +msgid "" +"\"RECIPROCAL\": the application is licensed under a reciprocal license " +"such as the GPL, and no proprietary drivers should be loaded." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:98 +msgid "" +"\"PROPRIETARY\": the application has some licensing restrictions which " +"make it ineligible for distribution with reciprocally licensed software. " +"Care will be taken to avoid loading reciprocally licensed drivers, such " +"as the GRASS and PDF drivers." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:102 +msgid "" +"\"DEFAULT\": the application does not apply any licensing restrictions. " +"This is typical of non-GPL open source applications such as MapServer, " +"and will be the default policy if nothing is declared." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:107 +msgid "User License Policy" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:109 +msgid "" +"The restrictions on mixing proprietary and reciprocally licensed software" +" generally applies at the point of distribution. In particular, it is not" +" intended to prevent the end user from assembling a variety of components" +" for their own use as they see fit, for their own use. To that end it is " +"important to provide a mechanism for the end user to deliberately " +"override the restrictions on mixing reciprocally licensed, and " +"proprietary components. This is accomplished via the GDAL_LICENSE_POLICY " +"configuration variable which might typically be set via the environment " +"or via the --config commandline switch to most GDAL applications. It may " +"have the following values:" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:120 +msgid "\"USE_ALL\": do not discard any drivers based on licensing restrictions." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:122 +msgid "" +"\"PREFER_PROPRIETARY\": If there is a conflict between proprietary and " +"reciprocally licensed drivers, use the proprietary ones." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:124 +msgid "" +"\"PREFER_RECIPROCAL\": If there is a conflict between proprietary and " +"reciprocally licensed drivers, use the reciprocally licensed ones." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:127 +msgid "" +"In addition to setting this via config variables, there will also be a " +"configure / nmake.opt declaration to alter the default " +"GDAL_LICENSE_POLICY. Thus a local build could be configured to USE_ALL at" +" build time instead of having to set environment variables or commandline" +" switches. This would not be suitable for software that will be " +"redistributed." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:135 +msgid "Policy Logic" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:137 +msgid "" +"If the user selected a GDAL_LICENSE_POLICY of \"USE_ALL\" then no drivers" +" are unloaded on the basis of licensing." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:139 +msgid "" +"If the user selected a GDAL_LICENSE_POLICY of \"PREFER_PROPRIETARY\" or " +"\"PREFER_RECIPROCAL\" then ignore the GDAL_APPLICATION_LICENSE_POLICY." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:141 +msgid "" +"if the application select a GDAL_APPLICATION_LICENSE_POLICY of " +"\"PROPRIETARY\" or \"RECIPROCAL\" then use that." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:143 +msgid "" +"In the absence of a user or application level policy, default to a policy" +" of \"PREFER_PROPRIETARY\"." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:146 +msgid "" +"The policy will be applied in the GDALDriverManager::AutoSkipDrivers() " +"method and in the newly introduced OGRSFDriverManager::AutoSkipDrivers() " +"method. The AutoSkipDrivers() method is already used to unload drivers " +"based on GDAL_SKIP (and soon OGR_SKIP) and is generally called after the " +"preliminary registration of drivers." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:153 +msgid "Strict Link Level Compliance" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:155 +msgid "" +"The GPL, the leading reciprocal license, talks about distribution of GPL " +"applications with proprietary code linked in. In a literal sense we may " +"still have running processes with mixed code linked in. Instead of " +"addressing the problem at the point of linking we are disabling use of " +"incompatible components at runtime. There is some small risk that this " +"may be considered not to be compliant with the requirements of the GPL " +"license in a literal sense, though it is clear we are making every " +"reasonable effort to enforce it in a practical sense." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:164 +msgid "" +"In the situation of standalone software packages being distributed with " +"GDAL, it may still be best for those preparing the package to completely " +"omit any components incompatible with the license of the applications. " +"This RFC is primarily intended to support complex mixed-component " +"distributions such as OSGeo4W." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:173 +msgid "I believe the following drivers should be marked as \"PROPRIETARY\":" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:176 +msgid "JP2ECW" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:178 +msgid "JP2MRSID" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:179 +msgid "MG4Lidar" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:180 +msgid "GEORASTER" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:182 +msgid "JPIPKAK" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:183 +msgid "ArcObjects" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:184 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:106 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:63 +msgid "OCI" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:186 +msgid "FME" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:187 +msgid "ArcSDE (raster and vector)" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:189 +msgid "I believe the following drivers should be marked as \"RECIPROCAL\":" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:191 +msgid "grass (raster and vector)" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:192 +msgid "EPSILON" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:193 +msgid "MySQL (depending on active license terms!)" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:194 +msgid "PDF" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:196 +msgid "Unresolved:" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:198 +msgid "" +"The OGR SOSI driver should probably be marked as proprietary currently as" +" it relies on linking with binary objects with unknown licencing terms, " +"even if apparently the ultimate goal seems to open source them." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:202 +msgid "" +"I'm a bit confused by :ref:`raster.msg`. Seems that it relies on third " +"party stuff with both proprietary and GPL code." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:205 +msgid "" +"I am unsure about the ODBC based drivers. I suppose PGEO and MSSQLSPATIAL" +" drivers ought to be marked proprietary too? Might it depend on the " +"actual license terms of the odbc library?" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:209 +msgid "Please let me know of other drivers needing marking." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:212 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:121 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:398 +#: ../../source/development/rfc/rfc91_dataset_close.rst:160 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:156 +msgid "SWIG Bindings" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:214 +msgid "" +"Some (all?) swig bindings automatically call GDALAllRegister() and/or " +"OGRRegisterAll() at the point the bindings are loaded making it hard to " +"set the application level GDAL_LICENSE_POLICY in a script before the " +"registration takes place. To address that I believe we should expose the " +"AutoSkipDrivers() methods via SWIG so that scripts can set the policy and" +" then \"clean\" the drivers based on the policy in force." +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:224 +msgid "How to test?" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:229 +msgid "How to document?" +msgstr "" + +#: ../../source/development/rfc/rfc34_license_policy.rst:234 +msgid "" +"Frank Warmerdam will do the core implementation in trunk. Driver " +"maintainers may need to update the metadata for particular drivers." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:5 +msgid "RFC 35: Delete, reorder and alter field definitions of OGR layers" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:7 +#: ../../source/development/rfc/rfc45_virtualmem.rst:7 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:7 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:7 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:7 +msgid "Authors: Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:9 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:9 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:9 +#: ../../source/development/rfc/rfc45_virtualmem.rst:9 +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:9 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:9 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:9 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:9 +msgid "Contact: even dot rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:16 +msgid "" +"This document proposes changes in OGR to add the capability to delete " +"fields, reorder fields and alter field definitions, in OGR layer " +"definitions." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:23 +msgid "" +"Currently, an OGR layer definition can only be altered to add a new field" +" definition with OGRLayer::CreateField()." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:26 +msgid "" +"It is desirable to extend OGR capabilities to be able to delete, reorder " +"and alter field definitions of existing layers. Such wish has been " +"expressed in ticket #2671 and comes back regularly on QGIS mailing list " +"(e.g. `http://lists.osgeo.org/pipermail/qgis-user/2011-May/011935.html " +"<http://lists.osgeo.org/pipermail/qgis-user/2011-May/011935.html>`__). " +"QGIS currently has a \"Table Manager\" extension to work around the lack " +"of DeleteField(), so a proper solution is clearly needed." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:37 +msgid "The OGRLayer class will be extended with the following methods :" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:48 +msgid "The documentation of those new methods is :" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:183 +msgid "Three new layer capabilities are added :" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:196 +msgid "The new methods are mapped to the C API :" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:205 +msgid "" +"For the purpose of the implementation, new methods are also added to the " +"OGRFeatureDefn class :" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:213 +msgid "" +"A OGRErr OGRCheckPermutation(int\\* panPermutation, int nSize) function " +"is added to ogrutils.cpp to check that the array is a permutation of " +"[0,nSize-1]. It is used by OGRFeatureDefn::ReorderFieldDefns() and can be" +" used by all drivers implementing OGRLayer::ReorderFields() to validate " +"the panMap argument." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:220 +msgid "Altering field types" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:222 +msgid "" +"This RFC does not attempt to guarantee which type conversions will be " +"possible. It will depend on the capabilities of the implementing drivers." +" For example, for database drivers, the operation will be directly done " +"on the server side (through a 'ALTER TABLE my_table ALTER COLUMN " +"my_column TYPE new_type' command for the PG driver). So some conversions " +"might be possible, others not..." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:229 +msgid "" +"It is however expected that converting from any type to OFTString will be" +" supported in most cases when AlterFieldDefn() is supported." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:232 +msgid "" +"Drivers that don't support a conversion and that were required to do it " +"(ALTER_TYPE_FLAG set and new_type != old_type) should emit an explicit " +"error." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:239 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:61 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:189 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:405 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:126 +msgid "None" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:242 +msgid "Changed drivers" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:244 +msgid "" +"The shapefile driver will implement DeleteField(), ReorderFields() and " +"AlterFieldDefn(). Shapelib will be extended with DBFReorderFields() and " +"DBFAlterFieldDefn()." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:248 +msgid "" +"Note: The implementation of AlterFieldDefn() in the Shapefile driver does" +" not support altering the field type, except when converting to " +"OFTString. It will not reformat numeric values of existing features if " +"width or precision are changed. However, appropriate field truncation or " +"expansion will occur if the width is altered." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:254 +msgid "" +"Other drivers, mainly database drivers (PG, MySQL, SQLite), could be " +"easily extended to implement the new API by issuing the appropriate SQL " +"command (ALTER TABLE foo DROP COLUMN bar, ALTER TABLE foo ALTER COLUMN " +"bar, ...). The implementation of DeleteField() and AlterFieldDefn() in " +"the PG driver is indeed planned, provided this RFC is adopted. The Memory" +" driver will also updated to support DeleteField(), ReorderFields() and " +"AlterFieldDefn()." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:263 +#: ../../source/development/rfc/rfc45_virtualmem.rst:1168 +#: ../../source/development/rfc/rfc84_cmake.rst:125 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:88 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:262 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:656 +msgid "SWIG bindings" +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:265 +msgid "" +"DeleteField(), ReorderField(), ReorderFields() and AlterFieldDefn() will " +"be mapped to SWIG." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:271 +msgid "" +"The autotest suite will be extended to test the implementation of the new" +" API for the Shapefile driver. An example of the use of the new API is " +"attached to ticket #2671 (`rfc35_test.py " +"<http://trac.osgeo.org/gdal/attachment/ticket/2671/rfc35_test.py>`__) and" +" will be turned into unit tests." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:280 +msgid "" +"Implementation will be done by Even Rouault in GDAL/OGR trunk. Changes in" +" Shapelib will need to be pushed into upstream CVS by a Shapelib " +"committer. The proposed implementation is attached as a patch in ticket " +"#2671 (`rfc35_v3.patch " +"<http://trac.osgeo.org/gdal/attachment/ticket/2671/rfc35_v3.patch>`__)." +msgstr "" + +#: ../../source/development/rfc/rfc35_deletereorderalterfielddefn.rst:289 +msgid "+1 from FrankW, DanielM, HowardB, TamasS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:5 +msgid "RFC 36: Allow specification of intended driver on GDALOpen (withdrawn)" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:7 +msgid "Authors: Ivan Lucena" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:9 +msgid "Contact: ivan.lucena@pmldnet.com" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:11 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:11 +msgid "Status: Withdrawn." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:13 +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:13 +msgid "Covered by `RFC 46: GDAL/OGR unification <./rfc46_gdal_ogr_unification>`__" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:18 +msgid "" +"This document proposes a mechanism to explicitly tell GDAL what driver " +"should open a particular dataset." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:22 +msgid "Justification" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:24 +msgid "" +"By selecting the driver, users can optimize processing time and avoid " +"incorrect or undesirable driver selection due to the driver probing " +"mechanism." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:29 +msgid "Concept" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:31 +msgid "" +"The idea is to pass to GDALOpen a string containing the token \"driver=\"" +" followed by the driver name and a comma separating it from the file-" +"name." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:35 +msgid "[driver=driver-name,]file-name" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:37 +msgid "Examples:" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:39 +msgid "$ gdalinfo driver=nitf:imagefile01.ntf" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:41 +msgid "" +"In that case no probing is necessary, since the user has indicated to use" +" the specific driver. If for some reason that process fails the function " +"returns NULL and no other attempt is made to open the file by another " +"driver." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:49 +msgid "" +"The amount of code is minimal and there is already a proposed patch on " +"ticket #3043." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:55 +msgid "" +"Any application that uses GDAL API or any GDAL command line tool's user " +"that, at one point, wants to force the use of a particular driver to open" +" a datasets." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:62 +msgid "" +"That optional entry on GDALOpen process should not affect the current " +"logic." +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:68 +msgid "Extra tests would be added to the test script" +msgstr "" + +#: ../../source/development/rfc/rfc36_open_by_drivername.rst:73 +msgid "" +"For gdalbuildvrt and gdaltindex it will not be possible to use the driver" +" selection with wildcard, as in \"driver=gtiff,*.tif\"." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:5 +msgid "RFC 37: User data callbacks in CPLError" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst +msgid "Date" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:7 +msgid "2011/10/25" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst +msgid "Author" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:8 +#: ../../source/development/rfc/rfc3_commiters.rst:218 +#: ../../source/development/rfc/rfc74_sphinx.rst:8 +msgid "Howard Butler" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst +msgid "Contact" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:9 +msgid "hobu.inc at gmail dot com" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst +msgid "Status" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:10 +msgid "Implemented" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst +msgid "Version" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:11 +msgid "GDAL 1.9" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst +msgid "Voting" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:12 +msgid "+1 Frank, Howard, Tamas, Daniel, Even" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:15 +msgid "" +"Description: This RFC proposes to implement user context data in " +"CPLErrorHandler callback functions. It does so without disrupting " +"existing callback patterns already in use, and provides completely " +"auxiliary functionality to CPLErrorHandler." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:23 +msgid "" +"It could be argued that users could already manage user context of error " +"handling functions with application-level globals that control its " +"interaction. While this sentiment is technically true, this approach adds" +" a ton of complication for library users. A scenario that has error " +"callbacks pass back user context data means simpler code for users " +"wishing to have the state of their application be returned along with " +"errors from inside of GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:30 +msgid "The case for user data be passed in callbacks:" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:32 +msgid "" +"It is a common idiom for signal-based APIs (of which CPLErrorHandler is " +"one)" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:33 +msgid "" +"It is simpler than requiring library users to manage the state of " +"internal library error handling externally in their own applications" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:38 +msgid "Implementation Concerns" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:40 +msgid "" +"GDAL's (and OGR and OSR's) error handling callback mechanisms are in wide" +" use and changes to the base library that were to break either the " +"callback signatures *or* the behavior of existing callback operations " +"should be rejected. Adding support for user data in the call back is to " +"be provided in addition to existing functionality that already exists in " +"the error handling, and an approach that mimics and looks similar to the " +"existing operations is likely the best approach for GDAL -- if not the " +"cleanest approach in general." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:52 +msgid "The first change will add a void* to CPLErrorHandlerNode:" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:63 +msgid "and to methods to add error handlers with user data will be provided:" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:70 +msgid "" +"``CPLSetErrorHandler`` and ``CPLPushErrorHandler`` will simply use the " +"``Ex`` functions and pass NULL in for the pUserData member." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:73 +msgid "" +"Finally, similar to ``CPLGetLastErrorType`` and ``CPLGetLastErrorMsg`` " +"methods, a ``CPLGetErrorHandlerUserData``" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:81 +msgid "SWIG bindings consideration" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:83 +msgid "" +"The SWIG bindings will *not* be updated to provide access to user data " +"for the currently active error handler for implementation of this RFC. " +"SWIG bindings maintainers can take advantage of this new functionality at" +" their discretion, however." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:89 +msgid "Ticket History" +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:91 +msgid "" +"`http://trac.osgeo.org/gdal/ticket/4295 " +"<http://trac.osgeo.org/gdal/ticket/4295>`_ contains a patch that " +"implements the proposed solution and provides context and discussion " +"about this feature. " +"http://trac.osgeo.org/gdal/attachment/ticket/4295/4295-hobu-rfc.patch " +"contains the current patch to implemented the proposed functionality." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:98 +msgid "Documentation of the added functions is provided as part of the patch." +msgstr "" + +#: ../../source/development/rfc/rfc37_cplerror_userdata.rst:103 +msgid "" +"All code will be implemented in trunk by Howard Butler after passage of " +"the RFC." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:5 +msgid "RFC 38: OGR Faster Open (withdrawn)" +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:18 +msgid "" +"It is proposed that the OGR datasource opening mechanism relies on the " +"GDALOpenInfo class, already used by GDAL drivers, to speed-up datasource " +"opening. The speed-up is due to the fact that the file passed to " +"OGROpen() will be opened and stat'ed only once, whereas currently, it is " +"opened and closed as many times as there are OGR drivers. This should be " +"particularly beneficial for network filesystems, or when trying to open a" +" file that is not a OGR datasource at all." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:26 +msgid "" +"E.g., trying to open a file that is not a OGR datasource currently " +"requires 45 file opening or stat operations :" +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:34 +msgid "" +"It is expected that if/once all drivers are migrated, it will decrease to" +" 2 operations only." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:40 +msgid "" +"Similarly to GDALDriver, the OGRSFDriver class is extended to have a " +"pfnOpen member, that drivers will set to point to their own Open method." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:52 +msgid "" +"The OGRSFDriverRegistrar::Open() method is updated to call pfnOpen when " +"iterating over the drivers. When pfnOpen is not set, it will try to call " +"the Open() method of OGRSFDriver (which enables a progressive migration " +"of drivers)." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:57 +msgid "" +"Mainly for compatibility reasons, the virtual method Open() of " +"OGRSFDriver that is currently pure virtual, will now be a regular virtual" +" method, that will have a default implementation, that will try to call " +"pfnOpen." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:62 +msgid "The patch with the changes to OGR core is attached to this page." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:67 +msgid "Proposed additions will not have any impact on C binary compatibility." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:69 +msgid "" +"C++ binary interface will be broken (due to the addition of a new member " +"in OGRSFDriver class and the Open() method changed from pure virtual to " +"virtual)." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:73 +msgid "Source level compatibility will be preserved for third-party OGR drivers." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:77 +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:61 +msgid "Impact on drivers" +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:79 +msgid "" +"Existing drivers are *not* required to migrate to RFC38, but are strongly" +" encouraged to. New drivers *should* use RFC38 mechanism to preserve the " +"overall faster opening." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:83 +msgid "An example of the migration for a few drivers is attached to this page." +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:86 +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:66 +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:99 +msgid "Timeline" +msgstr "" + +#: ../../source/development/rfc/rfc38_ogr_faster_open.rst:88 +msgid "" +"Even Rouault is responsible to implement this proposal. New API will be " +"available in GDAL 2.0. Most in-tree OGR drivers will be migrated to the " +"new mechanism." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:5 +msgid "RFC 39: OGR Layer Algebra" +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:7 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:7 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:7 +msgid "Author: Ari Jolma" +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:9 +msgid "Contact: ari dot jolma at aalto dot fi" +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:11 +msgid "Status: Adopted, implemented in GDAL 1.10" +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:16 +msgid "" +"It is proposed that the OGR layer class and the C API contains methods " +"for commonly needed overlay analysis methods." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:19 +msgid "" +"The basic functionality for spatial analysis with GDAL is provided by " +"GEOS. However, GEOS operates on geometries and typically people work with" +" geospatial data layers. Vector data layers are represented in GDAL by " +"OGRLayer objects. Thus, there is a need for spatial analaysis operations " +"that work on layers." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:25 +msgid "" +"Unfortunately there is no standard for spatial analysis operations API, " +"but it is possible to create a useful set by using existing software as " +"example." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:29 +msgid "" +"The methods are fundamentally dependent on comparison of all the features" +" of two layers. There would possibly be huge performance improvements " +"achievable with layer specific spatial indexes. This is considered out of" +" the scope of these methods and belonging to the general problem of " +"iterating features in a layer and accessing features randomly. For these " +"reasons these methods should be only considered convenience methods and " +"not replacements for analysis in relational databases for example." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:41 +msgid "" +"The methods are implemented by new methods in OGRLayer class " +"(ogrsf_frmts.h and ogrlayer.cpp) and new calls in the C API (ogr_api.h). " +"The Swig bindings (ogr.i) are also extended with these methods." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:45 +msgid "" +"The patch with the changes to OGR core and to the Swig bindings is " +"attached to this page. The patch has been superficially tested but it is " +"not written or formatted according to the GDAL tradition." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:52 +msgid "" +"Proposed additions will have an impact on C binary compatibility because " +"they change the API." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:55 +msgid "" +"C++ binary interface will be broken (due to the addition of a new members" +" in OGRLayer class)." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:58 +msgid "The changes are purely extensions and have no impact on existing code." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:63 +msgid "The changes do not have any impacts on drivers." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:68 +msgid "" +"Ari Jolma is responsible to implement this proposal. New API should be " +"available in GDAL 1.11." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:71 +msgid "" +"There needs to be a discussion on the names of the methods and on the " +"internal logic of the methods (this refers especially to the handling of " +"attributes and error conditions)." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:75 +msgid "" +"In addition to the methods in the attached patch, there should be some " +"discussion on additional methods. For example Append and Buffer methods " +"could be easily added to the set. An illustration of what is currently " +"available in the common software is for example this page: " +"`http://courses.washington.edu/gis250/lessons/Model_Builder/ " +"<http://courses.washington.edu/gis250/lessons/Model_Builder/>`__" +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:82 +msgid "Comments on performance" +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:84 +msgid "" +"Profiling Intersection of a layer of 46288 line string features with a " +"layer of one polygon feature (~1/3 of features within and many only " +"partly within the one feature) showed that when the method layer was a " +"Shapefile, most of the time was spent in reading the feature from the " +"Shapefile. When the method layer was copied into memory, most of the time" +" (83 %) was spent in OGRLineString::getEnvelope. The 6th version of the " +"patch contains a test against a pre-computed layer envelope, which speeds" +" up the computation in this case ~30% (from 2.44 s to 1.76 in my " +"machine). Still the most of the time (82 %) is spent in " +"OGRLineString::getEnvelope." +msgstr "" + +#: ../../source/development/rfc/rfc39_ogr_layer_algebra.rst:98 +msgid "(June 2012) +1 from Even, Frank, Howard, Tamas, Daniel" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:5 +msgid "RFC 3: GDAL Committer Guildlines" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:14 +#: ../../source/development/rfc/rfc7_vsilapi.rst:14 +#: ../../source/development/rfc/rfc8_devguide.rst:14 +#: ../../source/development/rfc/rfc9_maintainer.rst:14 +msgid "Purpose" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:16 +msgid "" +"To formalize SVN (or CVS) commit access, and specify some guidelines for " +"SVN committers." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:20 +msgid "Election to SVN Commit Access" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:22 +msgid "" +"Permission for SVN commit access shall be provided to new developers only" +" if accepted by the GDAL/OGR Project Steering Committee. A proposal " +"should be written to the PSC for new committers and voted on normally. It" +" is not necessary to write an RFC document for these votes, a proposal to" +" gdal-dev is sufficient." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:28 +msgid "Removal of SVN commit access should be handled by the same process." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:30 +msgid "" +"The new committer should have demonstrated commitment to GDAL/OGR and " +"knowledge of the GDAL/OGR source code and processes to the committee's " +"satisfaction, usually by reporting bugs, submitting patches, and/or " +"actively participating in the GDAL/OGR mailing list(s)." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:35 +msgid "" +"The new committer should also be prepared to support any new feature or " +"changes that he/she commits to the GDAL/OGR source tree in future " +"releases, or to find someone to which to delegate responsibility for them" +" if he/she stops being available to support the portions of code that " +"he/she is responsible for." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:41 +msgid "" +"All committers should also be a member of the gdal-dev mailing list so " +"they can stay informed on policies, technical developments and release " +"preparation." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:45 +msgid "" +"New committers are responsible for having read, and understood this " +"document." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:49 +msgid "Committer Tracking" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:51 +msgid "" +"A list of all project committers will be kept in the main gdal directory " +"(called COMMITTERS) listing for each SVN committer:" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:54 +msgid "Userid: the id that will appear in the SVN logs for this person." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:55 +msgid "Full name: the users actual name." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:56 +msgid "" +"Email address: A current email address at which the committer can be " +"reached. It may be altered in normal ways to make it harder to auto-" +"harvest." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:59 +msgid "A brief indication of areas of responsibility." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:62 +msgid "SVN Administrator" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:64 +msgid "" +"One member of the Project Steering Committee will be designed the SVN " +"Administrator. That person will be responsible for giving SVN commit " +"access to folks, updating the COMMITTERS file, and other SVN related " +"management. That person will need login access on the SVN server of " +"course." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:70 +msgid "Initially Frank Warmerdam will be the SVN Administrator." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:73 +msgid "SVN Commit Practices" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:75 +msgid "" +"The following are considered good SVN commit practices for the GDAL/OGR " +"project." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:78 +msgid "Use meaningful descriptions for SVN commit log entries." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:79 +msgid "" +"Add a bug reference like \"(#1232)\" at the end of SVN commit log entries" +" when committing changes related to a ticket in Trac. The '#' character " +"enables Trac to create a hyperlink from the changeset to the mentioned " +"ticket." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:83 +msgid "" +"After committing changes related to a ticket in Trac, write the tree and " +"revision in which it was fixed in the ticket description. Such as \"Fixed" +" in trunk (r12345) and in branches/1.7 (r12346)\". The 'r' character " +"enables Trac to create a hyperlink from the ticket to the changeset." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:88 +msgid "" +"Changes should not be committed in stable branches without a " +"corresponding bug id. Any change worth pushing into the stable version is" +" worth a bug entry." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:91 +msgid "" +"Never commit new features to a stable branch without permission of the " +"PSC or release manager. Normally only fixes should go into stable " +"branches." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:94 +msgid "New features go in the main development trunk." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:95 +msgid "" +"Only bug fixes should be committed to the code during pre-release code " +"freeze, without permission from the PSC or release manager." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:97 +msgid "" +"Significant changes to the main development version should be discussed " +"on the gdal-dev list before you make them, and larger changes will " +"require a RFC approved by the PSC." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:100 +msgid "" +"Do not create new branches without the approval of the PSC. Release " +"managers are assumed to have permission to create a branch." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:102 +msgid "" +"All source code in SVN should be in Unix text format as opposed to DOS " +"text mode." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:104 +msgid "" +"When committing new features or significant changes to existing source " +"code, the committer should take reasonable measures to insure that the " +"source code continues to build and work on the most commonly supported " +"platforms (currently Linux and Windows), either by testing on those " +"platforms directly, running [wiki:Buildbot] tests, or by getting help " +"from other developers working on those platforms. If new files or library" +" dependencies are added, then the configure.in, Makefile.in, Makefile.vc " +"and related documentations should be kept up to date." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:115 +msgid "Relationship with other upstream projects imported in GDAL/OGR code base" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:117 +msgid "" +"Some parts of the GDAL/OGR code base are regularly refreshed from other " +"upstream projects. So changes in those areas should go first into those " +"upstream projects, otherwise they may be lost during a later refresh. " +"Note that those directories may contain a mix of GDAL specific files and " +"upstream files. This has to be checked on a case-by-case basis (any file " +"with CVS changelog at its beginning is a good candidate for belonging to " +"the upstream project)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:125 +msgid "Currently the list of those areas is :" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:127 +msgid "" +"frmts/gtiff/libtiff : from libtiff CVS " +"(`http://www.remotesensing.org/libtiff/ " +"<http://www.remotesensing.org/libtiff/>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:129 +msgid "" +"frmts/gtiff/libgeotiff : from libgeotiff SVN " +"(`http://trac.osgeo.org/geotiff/ <http://trac.osgeo.org/geotiff/>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:131 +msgid "" +"frmts/jpeg/libjpeg : from libjpeg project " +"(`http://sourceforge.net/projects/libjpeg/ " +"<http://sourceforge.net/projects/libjpeg/>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:133 +msgid "" +"frmts/png/libpng : from libpng project " +"(`http://www.libpng.org/pub/png/libpng.html " +"<http://www.libpng.org/pub/png/libpng.html>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:135 +msgid "" +"frmts/gif/giflib : from giflib project " +"(`http://sourceforge.net/projects/giflib " +"<http://sourceforge.net/projects/giflib>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:137 +msgid "" +"frmts/zlib : from zlib project (`http://www.zlib.net/ " +"<http://www.zlib.net/>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:139 +msgid "" +"ogr/ogrsf_frmts/mitab : from MITAB CVS (`http://mitab.maptools.org/ " +"<http://mitab.maptools.org/>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:141 +msgid "" +"ogr/ogrsf_frmts/avc : from AVCE00 CVS (`http://avce00.maptools.org/ " +"<http://avce00.maptools.org/>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:143 +msgid "" +"ogr/ogrsf_frmts/shape/[dbfopen.c, shpopen.c, shptree.c, shapefil.h] : " +"from shapelib project (`http://shapelib.maptools.org/ " +"<http://shapelib.maptools.org/>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:146 +msgid "data/ : some .csv files related to CRS come from libgeotiff" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:149 +msgid "Legal" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:151 +msgid "" +"Committers are the front line gatekeepers to keep the code base clear of " +"improperly contributed code. It is important to the GDAL/OGR users, " +"developers and the OSGeo foundation to avoid contributing any code to the" +" project without it being clearly licensed under the project license." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:156 +msgid "" +"Generally speaking the key issues are that those providing code to be " +"included in the repository understand that the code will be released " +"under the MIT license, and that the person providing the code has the " +"right to contribute the code. For the committer themselves understanding " +"about the license is hopefully clear. For other contributors, the " +"committer should verify the understanding unless the committer is very " +"comfortable that the contributor understands the license (for instance " +"frequent contributors)." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:165 +msgid "" +"If the contribution was developed on behalf of an employer (on work time," +" as part of a work project, etc) then it is important that an appropriate" +" representative of the employer understand that the code will be " +"contributed under the MIT license. The arrangement should be cleared with" +" an authorized supervisor/manager, etc." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:171 +msgid "" +"The code should be developed by the contributor, or the code should be " +"from a source which can be rightfully contributed such as from the public" +" domain, or from an open source project under a compatible license." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:176 +msgid "All unusual situations need to be discussed and/or documented." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:178 +msgid "" +"Committers should adhere to the following guidelines, and may be " +"personally legally liable for improperly contributing code to the source " +"repository:" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:182 +msgid "" +"Make sure the contributor (and possibly employer) is aware of the " +"contribution terms." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:184 +msgid "" +"Code coming from a source other than the contributor (such as adapted " +"from another project) should be clearly marked as to the original source," +" copyright holders, license terms and so forth. This information can be " +"in the file headers, but should also be added to the project licensing " +"file if not exactly matching normal project licensing (gdal/LICENSE.txt)." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:190 +msgid "" +"Existing copyright headers and license text should never be stripped from" +" a file. If a copyright holder wishes to give up copyright they must do " +"so in writing to the foundation before copyright messages are removed. If" +" license terms are changed it has to be by agreement (written in email is" +" ok) of the copyright holders." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:195 +msgid "" +"Code with licenses requiring credit, or disclosure to users should be " +"added to /trunk/gdal/LICENSE.TXT." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:197 +msgid "" +"When substantial contributions are added to a file (such as substantial " +"patches) the author/contributor should be added to the list of copyright " +"holders for the file." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:200 +msgid "" +"If there is uncertainty about whether a change it proper to contribute to" +" the code base, please seek more information from the project steering " +"committee, or the foundation legal counsel." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:205 +msgid "Bootstraping" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:207 +msgid "" +"The following existing committers will be considered authorized GDAL/OGR " +"committers as long as they each review the committer guidelines, and " +"agree to adhere to them. The SVN administrator will be responsible for " +"checking with each person." +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:212 +msgid "Daniel Morissette" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:213 +msgid "Frank Warmerdam" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:214 +msgid "Gillian Walter" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:215 +msgid "Andrey Kiselev" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:216 +msgid "Alessandro Amici" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:217 +msgid "Kor de Jong" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:219 +msgid "Lichun Wang" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:220 +msgid "Norman Vine" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:221 +msgid "Ken Melero" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:222 +msgid "Kevin Ruland" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:223 +msgid "Marek Brudka" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:224 +msgid "Pirmin Kalberer" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:225 +msgid "Steve Soule" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:226 +msgid "Frans van der Bergh" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:227 +msgid "Denis Nadeau" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:228 +msgid "Oleg Semykin" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:229 +msgid "Julien-Samuel Lacroix" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:230 +msgid "Daniel Wallner" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:231 +msgid "Charles F. I. Savage" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:232 +msgid "Mateusz Loskot" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:233 +msgid "Peter Nagy" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:234 +msgid "Simon Perkins" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:235 +msgid "Radim Blazek" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:236 +msgid "Steve Halasz" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:237 +msgid "Nacho Brodin" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:238 +msgid "Benjamin Collins" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:239 +msgid "Ivan Lucena" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:240 +msgid "Ari Jolma" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:241 +msgid "Tamas Szekeres" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:245 +msgid "" +"`COMMITTERS <http://trac.osgeo.org/gdal/browser/trunk/gdal/COMMITTERS>`__" +" file" +msgstr "" + +#: ../../source/development/rfc/rfc3_commiters.rst:247 +msgid "" +"`Edit GDAL Subversion Group <https://www.osgeo.org/cgi-" +"bin/auth/ldap_group.py?group=gdal>`__" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:5 +msgid "" +"RFC 40: Improving performance of Raster Attribute Table implementation " +"for large tables" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:8 +msgid "Summary:" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:10 +msgid "" +"Raster Attrbute Tables from some applications (notably segmentation) can " +"be very large and are slow to access with the current API due to the way " +"only one element can get read or written at a time. Also, when an " +"attribute table is requested by the application the whole table must be " +"read - there is no way of delaying this so just the required subset is " +"read off disk. These changes will bring the attribute table support more " +"in line with the way raster data is accessed." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:19 +msgid "Implementation:" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:21 +msgid "" +"It is proposed that GDALRasterAttributeTable be re-written as a virtual " +"base class. This will allow drivers to have their own implementation that" +" only reads and writes data when requested. A new derived class, " +"GDALDefaultRasterAttributeTable will be provided that provides the " +"functionality of the GDAL 1.x GDALRasterAttributeTable (ie holds all data" +" in memory)." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:28 +msgid "" +"Additional methods will be provided in the GDALRasterAttributeTable class" +" that allow 'chunks' of data from a column to be read/written in one " +"call. As with the GetValueAs functions columns of different types would " +"be able to read as a value of a different type (i.e., read a int column " +"as a double) with the appropriate conversion taking place. The following " +"overloaded methods will be available:" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:41 +msgid "" +"It is expected that the application will allocate the required space for " +"reading in the same way as with the RasterIO() call." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:44 +msgid "" +"The char*\\* type will be used for reading and writing strings. When " +"reading strings, it is expected that the array is created of the correct " +"size and ValuesIO will just create the individual strings for each row. " +"The application should call CPLFree on each of the strings before de-" +"allocating the array." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:50 +msgid "" +"These methods will be available from C as GDALRATValuesIOAsDouble, " +"GDALRATValuesIOAsInteger and GDALRATValuesIOAsString." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:53 +msgid "" +"This is also an opportunity to remove unused functions on the attribute " +"table such as GetRowMin(), GetRowMax() and GetColorOfValue()." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:57 +msgid "Language Bindings:" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:59 +msgid "" +"The Python bindings will be altered so ValuesIO will be supported using " +"numpy arrays for the data with casting of types as appropriate. Strings " +"will be supported using the numpy support for string arrays." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:64 +msgid "Backward Compatibility:" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:66 +msgid "" +"The proposed additions will extend the C API. However, the C++ binary " +"interface will be broken and so GDAL 2.0 is suggested as an appropriate " +"time to introduce the changes." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:70 +msgid "" +"Care will be taken to still support the use of Clone() and Serialize() in" +" derived implementations of the GDALRasterAttributeTable class as these " +"are called by existing code. For implementations where the table is not " +"held in memory these may fail if the table is larger than some suitable " +"limit (for example, GetRowCount() \\* GetColCount() < 1 000 000). Clone()" +" should return a instance of GDALDefaultRasterAttributeTable to prevent " +"problems with sharing memory between objects." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:79 +msgid "" +"Existing code may need to be altered to use create instances of " +"GDALDefaultRasterAttributeTable rather than GDALRasterAttributeTable if " +"an in memory implementation is still required." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:84 +msgid "Impact on Drivers" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:86 +msgid "" +"The HFA driver will be updated to support all aspects of the new " +"interface, such as the new functions and reading/writing upon request. " +"Other drivers will be modified to continue to use the in memory " +"implementation (GDALDefaultRasterAttributeTable)." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:94 +msgid "" +"The Python autotest suite will be extended to test the new API, both for " +"the default implementation and specialised implementation in the HFA " +"driver." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:101 +msgid "" +"We (Sam Gillingham and Pete Bunting) are prepared undertake the work " +"required and have it ready for inclusion in GDAL 1.11 There needs to be a" +" discussion on the names of the methods and on the internal logic of the " +"methods." +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:107 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:237 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:347 +msgid "Ticket" +msgstr "" + +#: ../../source/development/rfc/rfc40_enhanced_rat_support.rst:109 +msgid "Ticket #5129 has been opened to track the progress of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:5 +msgid "RFC 41 : Support for multiple geometry fields in OGR" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:10 +msgid "" +"Add read/write support in the OGR data model for features with multiple " +"geometry fields." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:14 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:30 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:33 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:24 +#: ../../source/development/rfc/rfc72_pytest.rst:26 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:25 +#: ../../source/development/rfc/rfc74_sphinx.rst:23 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:22 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:21 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:21 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:37 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:22 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:23 +#: ../../source/development/rfc/rfc84_cmake.rst:30 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:22 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:28 +#: ../../source/development/rfc/rfc87_signed_int8.rst:22 +#: ../../source/development/rfc/rfc88_googletest.rst:27 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:23 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:31 +#: ../../source/development/rfc/rfc91_dataset_close.rst:26 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:25 +#: ../../source/development/rfc/rfc93_update_feature.rst:22 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:24 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:24 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:27 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:25 +msgid "Motivation" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:16 +msgid "" +"The OGR data model is currently tied to a single geometry field per " +"feature, feature definition and layer. But a number of data formats " +"support multiple geometry fields. The OGC Simple Feature Specifications " +"also do not limit to one geometry field per layer (e.g. §7.1.4 of `OGC " +"06-104r4 \"OpenGIS® Implementation Standard for Geographic information - " +"Simple feature access -Part 2: SQL option " +"<http://portal.opengeospatial.org/files/?artifact_id=25354>`__)." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:24 +msgid "" +"There are workarounds : using geometries of type GEOMETRYCOLLECTION, or " +"advertizing as many layers as there are geometry columns in the layer " +"(like currently done in the PostGIS or SQLite drivers). All those " +"approach are at best workarounds that suffer from limitations :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:29 +msgid "" +"GEOMETRYCOLLECTION approach : no way to know the name/semantics of each " +"sub-geometry. All sub-geometries must be expressed in the same SRS. No " +"way of guaranteeing that the GEOMETRYCOLLECTION has always the same " +"number of sub-geometries or that there are of a consistent geometry type." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:34 +msgid "" +"one layer per geometry column approach : only appropriate for read-only " +"scenarios. Cannot work in write scenarios." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:37 +msgid "" +"The purpose of this RFC is to make support for multiple geometry fields " +"per feature to be properly taken into account in the OGR data model." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:41 +msgid "Proposed solution" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:43 +msgid "" +"(Note: alternative solutions have also been studied. They are explained " +"in a following section of this RFC.)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:46 +msgid "" +"To sum it up, geometry fields will be treated similarly as attribute " +"fields are handled at the OGRFeatureDefn and OGRFeature levels, but they " +"will be kept separate. Attribute fields and geometry fields will have " +"their own separate indexing in the feature definition." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:51 +msgid "" +"This choice has been mainly made to maximize backward compatibility, " +"while offering new capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:54 +msgid "" +"Its involves creating a OGRGeomFieldDefn class, and changes in " +"OGRFieldDefn, OGRFeatureDefn, OGRFeature and OGRLayer classes." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:58 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:206 +msgid "OGRGeomFieldDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:60 +msgid "" +"The OGRGeomFieldDefn is a new class. Its structure is directly inspired " +"from the OGRFieldDefn class." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:92 +msgid "" +"One can notice that the member variables were to be found at OGRLayer " +"level previously." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:95 +msgid "" +"The SRS object is ref-counted. The reference count is increased in the " +"constructor and in SetSpatialRef(), and decreased in the destructor." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:98 +msgid "" +"GetSpatialRef() is deliberately set virtual, so that lazy evaluation can " +"be implemented (getting SRS can have a noticeable cost in some driver " +"implementations, like reading an extra file, or issuing a SQL request)." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:103 +msgid "OGRFeatureDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:105 +msgid "The OGRFeatureDefn class will be extended as the following :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:131 +msgid "" +"At instantiation, OGRFeatureDefn would create a default geometry field " +"definition of name \"\" and type wkbUnknown. If SetGeomType() is called, " +"this will be routed on papoGeomFieldDefn[0]. If only one geometry field " +"definition exists, SetGeomType(wkbNone) will remove it." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:136 +msgid "" +"GetGeomType() will be routed on papoGeomFieldDefn[0] if it exists. " +"Otherwise it will return wkbNone." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:139 +msgid "" +"It is strongly advised that there is name uniqueness among the combined " +"set of regular field names and the geometry field names. Failing to do so" +" will result in unspecified behavior in SQL queries. This advice will not" +" be checked by the code (it is currently not done for regular fields)." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:145 +msgid "" +"Another change is to make all the existing methods of OGRFeatureDefn " +"virtual (and change private visibility to protected), so this class can " +"be subclassed if needed. This will enable lazy creation of the object. " +"Justification: establishing the full feature definition can be costly. " +"But applications may want to list all the layers of a datasource, and " +"only present some information that is important, but cheap to establish. " +"In the past, OGRLayer::GetName() and OGRLayer::GetGeomType() have been " +"introduced in order to workaround for that." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:154 +msgid "" +"Note also that ReorderGeomFieldDefns() is not foreseen for the moment. It" +" could be added in a later step, should the need arises. " +"DeleteGeomFieldDefn() is mostly there for the own benefit of " +"OGRFeatureDefn itself when calling SetGeomType(wkbNone)." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:160 +msgid "OGRFeature class" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:162 +msgid "The OGRFeature class will be extended as following :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:188 +msgid "" +"Note: before RFC41, SetGeometry() or SetGeometryDirectly() could work on " +"a feature whose feature definition had a GetGeomType() == wkbNone (which " +"was inconsistent). This will be no longer the case since the size of the " +"papoGeometries array is now based on GetGeomFieldCount(), and when " +"GetGeomType() == wkbNone, the geometry field count is 0. The VRT and CSV " +"drivers will be fixed to declare their geometry type consistently." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:196 +msgid "OGRLayer class" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:198 +msgid "Impact on OGRLayer class :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:200 +msgid "" +"Spatial filter: the option considered is to only allow one spatial filter" +" at the time." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:203 +msgid "" +"the need for spatial filters applied simultaneously on several geometry " +"fields is not obvious." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:205 +msgid "" +"the m_poFilterGeom protected member is used more than 250 times in the " +"OGR code base, so turning it into an array would be a tedious task..." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:209 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:415 +msgid "Additions:" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:228 +msgid "" +"GetGeomType() : unchanged. For other fields, use " +"GetLayerDefn()->GetGeomField(i)->GetType()" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:231 +msgid "" +"GetSpatialRef(): Currently the default implementation returns NULL. It " +"will be changed to return " +"GetLayerDefn()->GetGeomField(0)->GetSpatialRef() (if there is at least " +"one geometry field). New drivers are encouraged not to specialize " +"GetSpatialRef() anymore, but to appropriately set the SRS of their first " +"geometry field. For other fields, use " +"GetLayerDefn()->GetGeomField(i)->GetSpatialRef()." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:239 +msgid "" +"Caveat: as SRS wasn't previously stored at the OGRFeatureDefn level, all " +"existing drivers, if not updated, will have " +"GetGeomField(0)->GetSpatialRef() returning NULL. The test_ogrsf utility " +"will check and warn about this. Update of existing drivers will be made " +"progressively. In the mean time, using OGRLayer::GetSpatialRef() will be " +"advized to get the SRS of the first geometry field in a reliable way." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:247 +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:258 +msgid "add :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:264 +msgid "" +"no DeleteGeomField(), ReorderGeomFields() or AlterGeomFieldDefn() for " +"now. Could be added later if the need arises." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:267 +msgid "" +"GetGeometryColumn() : unchanged. Routed onto the first geometry field. " +"For other fields, use GetLayerDefn()->GetGeomField(i)->GetNameRef()" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:271 +msgid "" +"SetIgnoredFields() : iterate over the geometry fields in addition to " +"regular fields. The special \"OGR_GEOMETRY\" value will only apply to the" +" first geometry field." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:275 +msgid "" +"Intersection(), Union(), etc... : unchanged. Later improvements could use" +" the papszOptions parameter to specify an alternate geometry field" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:278 +msgid "" +"TestCapability(): add a OLCCreateGeomField capability to inform if " +"CreateGeomField() is implemented." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:282 +msgid "OGRDataSource class" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:284 +msgid "Impact on OGRDataSource class :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:286 +msgid "" +"CreateLayer() : signature will be unchanged. If more than one geometry " +"fields are needed, OGRLayer::CreateGeomField() must be used. If the name " +"of the first geometry field must be specified, for datasources supporting" +" ODsCCreateGeomFieldAfterCreateLayer, using code should call " +"CreateLayer() with eGType = wkbNone and then add all geometry fields with" +" OGRLayer::CreateGeomField()." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:293 +msgid "" +"CopyLayer() : adapted to replicate all geometry fields (if supported by " +"target layer)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:296 +msgid "" +"ExecuteSQL() : takes a spatial filter. In the case of the generic OGR SQL" +" implementation, this filter is a facility. It could also as well be " +"applied on the returned layer object. So there is no real need for adding" +" a way of specifying the geometry field at the ExecuteSQL() API level." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:302 +msgid "" +"TestCapability(): add a ODsCCreateGeomFieldAfterCreateLayer capability to" +" inform if CreateGeomField() is implemented after layer creation and that" +" CreateLayer() can be safely called with eGType = wkbNone." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:308 +msgid "Explored alternative solutions" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:310 +msgid "" +"( This paragraph can be skipped if you are totally convinced by the " +"proposed approach detailed above :-) )" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:313 +msgid "" +"A possible alternative solution would have been to extend the existing " +"OGRFieldDefn object with information related to the geometry. That would " +"have involved adding a OFTGeometry value in the OGRFieldType enumeration," +" and adding the OGRwkbGeometryType eGeomType and OGRSpatialReference\\* " +"poSRS members to OGRFieldDefn. At OGRFeature class level, the OGRField " +"union could have been extended with a OGRGeometry\\* field. Similarly at " +"OGRLayer level, CreateField() could have been used to create new geometry" +" fields." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:322 +msgid "" +"The main drawback of this approach, which seems the most natural way, is " +"backward compatibility. This would have affected all places in OGR own " +"code or external code where fields are retrieved and geometry is not " +"expected. For example, in code like the following (very common in the " +"CreateFeature() of most drivers, or in user code consuming features " +"returned by GetNextFeature()) :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:338 +msgid "" +"This would lead, for legacy code, to geometry being handled as regular " +"field. We could imagine that GetFieldAsString() converts the geometry as " +"WKT, but it is doubtfull that this would really be desired. " +"Fundamentally, the handling of attribute and geometry fields is different" +" in most use cases." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:344 +msgid "" +"(On the other side, if we introduce 64bit integer as a OGR type (this is " +"an RFC that is waiting for implementation...), the above code would still" +" produce a meaningful result. The string reprentation of a 64bit integer " +"is not that bad as a default behavior.)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:349 +msgid "" +"GetFieldCount() would also take into account geometry fields, but in most" +" cases, you would need to subtract them." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:352 +msgid "" +"A possible way of avoiding the above compatibility issue would be to have" +" 2 sets of API at OGRFeatureDefn and OGRFeature level. The current one, " +"that would ignore the geometry fields, and an \"extended\" one that would" +" take them into account. For example, OGRFeatureDefn::GetFieldCountEx(), " +"OGRFeatureDefn::GetFieldIndexEx(), OGRFeatureDefn::GetFieldDefnEx(), " +"OGRFeature::GetFieldEx(), OGRFeature::SetFieldAsXXXEx() would take into " +"account both attribute and geometry fields. The annoying thing with that " +"approach is the duplication of the ~ 20 methods GetField() and " +"SetFieldXXX() in OGRFeature." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:366 +msgid "The following functions are added to the C API :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:420 +msgid "OGR SQL engine" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:422 +msgid "" +"Currently, \"SELECT fieldname1[, ...fieldnameN] FROM layername\" returns " +"the specified fields, as well as the associated geometry. This behavior " +"is clearly not following the behavior of spatial RDBMS where the geometry" +" field must be explicitly specified." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:427 +msgid "" +"The following compromise between backward compatibility and the new " +"capabilities of this RFC is adopted :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:430 +msgid "" +"if no geometry field is explicitly specified in the SELECT clause, and " +"there is only one geometry fields associated with the layer, then return " +"it implicitly" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:433 +msgid "" +"otherwise, only return the explicitly mentioned geometry fields (or all " +"geometry fields if \"*\" is used)." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:437 +#: ../../source/development/rfc/rfc45_virtualmem.rst:1113 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:192 +#: ../../source/development/rfc/rfc91_dataset_close.rst:152 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:330 +msgid "Limitations" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:439 +msgid "Geometries from joined layers will not be fetched, as currently." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:440 +msgid "" +"UNION ALL will only handle the default geometry, as currently. (could be " +"extended in later work.)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:442 +msgid "" +"The special fields OGR_GEOMETRY, OGR_GEOM_WKT and OGR_GEOM_AREA will " +"operate on the first geometry field. It does not seem wise to extend this" +" ad-hoc syntax. A better alternative will be the OGR SQLite dialect (with" +" Spatialite support), once it is updated to support multi-geometry (not " +"in the scope of this RFC)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:452 +msgid "Updated drivers in the context of this RFC" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:454 +msgid "PostGIS:" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:456 +msgid "" +"a ad-hoc form of support already exists. Tables with multiple geometries " +"are reported currently as layers called \"table_name(geometry_col_name)\"" +" (as many layers as geometry columns). This behavior will be changed so " +"that the table is reported only once as a OGR layer." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:462 +msgid "PGDump:" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:464 +msgid "add write support for multi-geometry tables." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:466 +msgid "Memory:" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:468 +msgid "updated as a simple illustration of the new capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:470 +msgid "Interlis:" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:472 +msgid "" +"updated to support multiple geometry fields (as well as other changes " +"unrelated to this RFC)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:476 +msgid "Other candidate drivers (upgrade not originally covered by this RFC)" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:478 +msgid "" +"GML driver : currently, only one geometry per feature reported. " +"Possibility of changing this by hand-editing of the .gfs file --> " +"implemented post RFC in GDAL 1.11" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:481 +msgid "SQLite driver :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:483 +msgid "currently, same behavior as current PostGIS driver." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:484 +msgid "" +"both the driver and the SQLite dialect could be updated to support multi-" +"geometry layers. --> implemented post RFC in GDAL 2.0" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:487 +msgid "" +"Google Fusion Tables driver : currently, only the first found geometry " +"column used. Possibility of specifying " +"\"table_name(geometry_column_name)\" as the layer name passed to " +"GetLayerByName()." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:491 +msgid "" +"VRT : some thoughts needed to find the syntax to support multiple " +"geometries. Impacted XML syntax : . at OGRVRTLayer element level : " +"GeometryType, LayerSRS, GeomField, SrcRegion, ExtentXMin/YMin/XMax/YMax, " +". at OGRVRTWarpedLayer element level : add new element to select the " +"geometry field . at OGRVRTUnionLayer element level : GeometryType, " +"LayerSRS, ExtentXMin/YMin/XMax/YMax --> implemented post RFC in GDAL 1.11" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:498 +msgid "" +"CSV : currently, take geometries from column named \"WKT\". To be " +"extended to support multiple geometry columns. Not sure worth the effort." +" Could be done with the extended VRT driver. --> implemented post RFC in " +"GDAL 1.11" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:502 +msgid "" +"WFS : currently, only single-geometry layers supported. The standard " +"allows multi-geometry. Would require GML driver support first." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:504 +msgid "Other RDBMS based drivers: MySQL ?, MSSQLSpatial ? Oracle Spatial ?" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:510 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:326 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:609 +msgid "ogrinfo" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:512 +msgid "" +"ogrinfo will be updated to report information related to multi-geometry " +"support. Output is expected to be unchanged w.r.t current output in the " +"case of single-geometry datasource." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:516 +msgid "Expected output for multi-geometry datasource:" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:580 +msgid "" +"A \"-geomfield\" option will be added to specify on which field the -spat" +" option applies." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:584 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:186 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:615 +msgid "ogr2ogr" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:586 +msgid "Enhancements :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:588 +msgid "" +"will translate multi-geometry layers into multi-geometry layers if " +"supported by output layer (OLCCreateGeomField capability). In case it is " +"not supported, only translates the first geometry." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:591 +msgid "" +"\"-select\" option. If only attribute field names are specified, all " +"input geometries will be implicitly selected (backward compatible " +"behavior). If one or several geometry field names are specified, only " +"those ones will be selected." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:595 +msgid "" +"add a \"-geomfield\" option to specify on which field the -spat option " +"applies" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:597 +msgid "" +"the various geometry transformations (reprojection, clipping, etc.) will " +"be applied on all geometry fields." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:601 +msgid "test_ogrsf" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:603 +msgid "Will be enhanced with a few consistency checks :" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:605 +msgid "" +"OGRLayer::GetSpatialRef() == " +"OGRFeatureDefn::GetGeomField(0)->GetSpatialRef()" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:607 +msgid "OGRLayer::GetGeomType() == OGRFeatureDefn::GetGeomField(0)->GetGeomType()" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:609 +msgid "" +"OGRLayer::GetGeometryColumn() == " +"OGRFeatureDefn::GetGeomField(0)->GetNameRef()" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:612 +msgid "Spatial filtering tests will loop over all geometry fields." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:617 +msgid "" +"In addition to function level documentation, the new capability will be " +"documented in the :ref:`vector_data_model` and :ref:`vector_api_tut` " +"documents." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:623 +msgid "" +"The new C API will be mapped to SWIG bindings. It will be only tested " +"with the Python bindings. No new typemaps are expected, so this should " +"work with other languages in a straightforward way." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:630 +msgid "" +"Changes are only additions to the existing API, and existing behavior " +"should be preserved, so this will be backwards compatible." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:633 +msgid "C++ ABI changes" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:635 +msgid "" +"Change of behavior in PostGIS driver w.r.t GDAL 1.10 for tables with " +"multiple geometries." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:641 +msgid "" +"Even Rouault will implement the above described changes for GDAL 1.11 " +"release, except the upgrade of the Interlis driver that will be done by " +"Pirmin Kalberer." +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:646 +#: ../../source/development/rfc/rfc84_cmake.rst:188 +msgid "Funding" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:648 +msgid "" +"This work is funded by the `Federal Office of Topography (swisstopo), " +"COGIS " +"<http://www.swisstopo.admin.ch/internet/swisstopo/en/home/swisstopo/org/kogis.html>`__" +msgstr "" + +#: ../../source/development/rfc/rfc41_multiple_geometry_fields.rst:654 +msgid "+1 from EvenR, FrankW, HowardB, DanielM and TamasS" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:5 +msgid "RFC 42: OGR Layer laundered field lookup" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:7 +msgid "Author: Jürgen Fischer" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:9 +msgid "Contact: jef at norbit dot de" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:14 +msgid "" +"This (mini)RFC proposes a new method in the OGR layer class (and a C API)" +" to lookup the field index of fields, whose names have been altered by " +"drivers (eg. by LAUNDER in OCI or Pg)." +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:21 +msgid "" +"There is already a pull request on github " +"(`https://github.com/OSGeo/gdal/pull/23 " +"<https://github.com/OSGeo/gdal/pull/23>`__) that implements this RFC. It " +"adds the virtual method OGRLayer::FindFieldIndex(), that implements the " +"usual mapping, which can be overloaded by drivers. The OCI driver does " +"this to optionally return the index of the LAUNDERed field in case the " +"original field does not exists. The pull request also modifies ogr2ogr to" +" make use of that method and offers a switch -relaxedFieldNameMatch to " +"enable it." +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:31 +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:19 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:19 +msgid "Background" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:33 +msgid "" +"This is a particular problem when using NAS as that usually operates on a" +" pre-existing schema. This schema had to be adapted for Oracle as Oracle " +"has a identifier length restrictions that quite a number of identifiers " +"in NAS exceed. Hence ogr2ogr failed to make the mapping between the short" +" names and their long counter parts and leaves those fields empty." +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:43 +msgid "" +"`https://github.com/OSGeo/gdal/pull/23 " +"<https://github.com/OSGeo/gdal/pull/23>`__" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:44 +msgid "" +"PostgreSQL NAS schema: " +"`http://trac.wheregroup.com/PostNAS/browser/trunk/import/alkis_PostNAS_schema.sql" +" " +"<http://trac.wheregroup.com/PostNAS/browser/trunk/import/alkis_PostNAS_schema.sql>`__" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:46 +msgid "" +"Oracle NAS schema: " +"`http://trac.wheregroup.com/PostNAS/browser/trunk/import/alkis_PostNAS_ORACLE_schema.sql" +" " +"<http://trac.wheregroup.com/PostNAS/browser/trunk/import/alkis_PostNAS_ORACLE_schema.sql>`__" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:48 +msgid "" +"conversion script from Pg to OCI: " +"`http://trac.wheregroup.com/PostNAS/browser/trunk/import/pg-to-oci.pl " +"<http://trac.wheregroup.com/PostNAS/browser/trunk/import/pg-to-oci.pl>`__" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:54 +msgid "+1 from DanielM, EvenR, FrankW, TamasS, JukkaR and jef" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:57 +msgid "Commits" +msgstr "" + +#: ../../source/development/rfc/rfc42_find_laundered_fields.rst:59 +msgid "r26572 & r26573" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:5 +msgid "RFC 43: GDALMajorObject::GetMetadataDomainList" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:14 +msgid "" +"This (mini)RFC proposes a new virtual method, GetMetadataDomainList(), in" +" the GDALMajorObject class (and a C API) to return the list of all " +"available metadata domains." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:21 +msgid "" +"GDALMajorObject currently offers the GetMetadata() and GetMetadataItem() " +"methods that both accept a metadata domain argument. But there is no way " +"to auto-discover which metadata domains are valid for a given " +"GDALMajorObject (i.e. a dataset or raster band). This make it impossible " +"to have generic code that can exhaustively discover all metadata in a " +"dataset/raster band." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:31 +msgid "" +"The base implementation in GDALMajorObject just calls GetDomainList() on " +"the internal oMDMD member." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:57 +msgid "" +"This method is also available in the C API ( char \\*\\* CPL_STDCALL " +"GDALGetMetadataDomainList( GDALMajorObjectH hObject) ) and Swig bindings." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:62 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:314 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:250 +#: ../../source/development/rfc/rfc93_update_feature.rst:152 +msgid "Impacted drivers" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:64 +msgid "" +"Drivers that have custom implementations of GetMetadata() and/or " +"GetMetadataItem() will generally have to also implement " +"GetMetadataDomainList(), when they don't modify the oMDMD member." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:68 +msgid "" +"To make it easy to implement the specialized GetMetadataDomainList(), " +"GDALMajorObject will offer a protected BuildMetadataDomainList() method " +"that can be used like the following :" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:87 +msgid "" +"The TRUE parameter means that the list of domains that follows are " +"potential domains, and thus BuildMetadataDomainList() will check for each" +" one that GetMetadata() returns a non-NULL value." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:91 +msgid "" +"An exhaustive search in GDAL drivers has been made and all drivers that " +"needed to be updated to implement GetMetadataDomainList() have been " +"updated: ADRG, BAG, CEOS2, DIMAP, ECW, ENVISAT, ERS, GeoRaster (cannot " +"check myself that it compiles), GIF, GTiff, HDF4, JPEG, MBTILES, netCDF, " +"NITF, OGDI, PCIDSK, PDF, PNG, PostgisRaster, RasterLite, RS2, VRT, WCS, " +"WebP, WMS." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:98 +msgid "A few caveats :" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:100 +msgid "" +"For MBTiles, WMS and VRT, GetMetadataDomainList(), at the band level, " +"will return \"LocationInfo\" as a valid metadata domain (used by the " +"gdallocationinfo utility), even if GetMetadata(\"LocationInfo\") itself " +"does not return metadata : you have to call " +"GetMetadataItem(\"Pixel_someX_someY\", \"LocationInfo\") or " +"GetMetadataItem(\"GeoPixel_someX_someY\", \"LocationInfo\")." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:106 +msgid "" +"For CEOS2 and ENVISAT, the list of metadata domains cannot be established" +" easily. GetMetadataDomainList() will return the pattern of accepted " +"domain names." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:111 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:319 +msgid "Impacted utilities" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:113 +msgid "The gdalinfo utility is extended to accept :" +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:115 +msgid "a \"-listmdd\" option that will print the metadata domains available," +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:139 +msgid "and \"-mdd all\" will display the content of all metadata domains." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:226 +msgid "" +"This change has no impact on backward compatibility at the C API/ABI and " +"C++ API levels. But it impacts C++ ABI, so it requires a full rebuild of " +"all GDAL drivers." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:233 +msgid "" +"The Python autotest suite will be extended to test the new API in a few " +"drivers." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:239 +msgid "Ticket #5275 has been opened to track the progress of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:241 +msgid "" +"The implementation is available in `an attachment to ticket 5275 " +"<http://trac.osgeo.org/gdal/attachment/ticket/5275/getmetadatadomainlist.patch>`__." +msgstr "" + +#: ../../source/development/rfc/rfc43_getmetadatadomainlist.rst:247 +msgid "+1 from EvenR, DanielM and JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:5 +msgid "RFC 44: Add Parseable Output Formats for ogrinfo and gdalinfo" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:7 +msgid "Authors: Dan \"Ducky\" Little, Faza Mahamood" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:9 +msgid "Contacts: danlittle at yahoo dot com, fazamhd at live dot com" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:11 +msgid "Status: Development. gdalinfo -json implemented in GDAL 2.0" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:16 +msgid "Add XML and JSON output to the ogrinfo and gdalinfo utilities." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:21 +msgid "" +"ogrinfo and gdalinfo are incredibly useful metadata gathering tools. " +"Their native text-based output formats, however, are not easily parseable" +" by common external tools. Both XML and JSON are easily parsed and adding" +" those output formats would substantially increase the utility for those " +"looking to add the ogrinfo and gdalinfo utilities to a scripting stack." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:31 +msgid "" +"An example implementation can be seen at the following github fork " +"`https://github.com/theduckylittle/gdal/blob/trunk/gdal/apps/ogrinfo.cpp " +"<https://github.com/theduckylittle/gdal/blob/trunk/gdal/apps/ogrinfo.cpp>`__" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:34 +msgid "" +"To add the XML output to each utility will require \"breaking up\" the " +"main loop into contingent chunks. All diagnostic messages will also need " +"to be moved to STDERR to ensure that output on STDOUT is always " +"parseable. The XML representation will be constructed using the MiniXML " +"library built into GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:41 +msgid "Proposed json format for gdalinfo" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:316 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:189 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:194 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:199 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:204 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:115 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:147 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:153 +msgid "None." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:321 +msgid "gdalinfo" +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:323 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:328 +msgid "Adds a \"-xml\" output option." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:324 +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:329 +msgid "Adds a \"-json\" output option." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:334 +msgid "" +"This change has no impact on backward compatibility at the C API/ABI and " +"C++ API/ABI levels. Default output will remain the same. The new XML " +"output will only effect users who specify \"-xml\" or \"-json\" on the " +"command line." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:342 +msgid "" +"The Python autotest suite will be extended to test the new XML/JSON " +"outputs and existing tests will be modified to check STDERR for " +"diagnostic messages." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:349 +msgid "No tickets." +msgstr "" + +#: ../../source/development/rfc/rfc44_gdalinfoxml.rst:354 +msgid "Proposed." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:5 +msgid "RFC 45: GDAL datasets and raster bands as virtual memory mappings" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:16 +msgid "" +"This document proposes additions to GDAL so that image data of GDAL " +"datasets and raster bands can be seen as virtual memory mappings, for " +"hopefully simpler usage." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:23 +msgid "" +"When one wants to read or write image data from/into a GDAL dataset or " +"raster band, one must use the RasterIO() interface for the regions of " +"interest that are read or written. For small images, the most convenient " +"solution is usually to read/write the whole image in a single request " +"where the region of interest is the full raster extent. For larger " +"images, particularly when they do not fit entirely in RAM, this is not " +"possible, and if one wants to operate on the whole image, one must use a " +"windowing strategy to avoid memory issues : typically by proceeding " +"scanline (or group of scanlines) by scanline, or by blocks for tiled " +"images. This can make the writing of algorithms more complicated when " +"they need to access a neighbourhood of pixels around each pixel of " +"interest, since the size of this extra window must be taken into account," +" leading to overlapping regions of interests. Nothing that cannot be " +"solved, but that requires some additional thinking that distracts from " +"the followed main purpose." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:39 +msgid "" +"The proposed addition of this RFC is to make the image data appear as a " +"single array accessed with a pointer, without being limited by the size " +"of RAM with respect to the size of the dataset (excepted limitations " +"imposed by the CPU architecture and the operating system)" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:45 +msgid "Technical solution" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:48 +msgid "Low-level machinery : cpl_virtualmem.h" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:50 +msgid "" +"The low-level machinery to support this new capability is a CPLVirtualMem" +" object that represents an area of virtual memory ( on Linux, an area of " +"virtual memory allocated by the mmap() function ). This virtual memory " +"area is initially just reserved in terms of virtual memory space, but has" +" no actual allocation in physical memory. This reserved virtual memory " +"space is protected with an access permission that cause any attempt to " +"access it to result in an exception - a page fault, that on POSIX systems" +" triggers a SIGSEGV signal (segmentation fault). Fortunately, " +"segmentation faults can be caught by the software with a signal handler. " +"When such a segmentation fault occurs, our specialized signal handler " +"will check if it occurs in a virtual memory region under its " +"responsibility and, if so, it will proceed to fill the part (a \"page\") " +"of the virtual memory area that has been accessed with sensible values " +"(thanks to a user provided callback). It will then set appropriate " +"permissions to the page (read-only or read-write), before attempting " +"again the instruction that triggered the segmentation fault. From the " +"point of view of the user code that accesses the memory mapping, this is " +"completely transparent, and this is equivalent as if the whole virtual " +"memory area had been filled from the start." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:70 +msgid "" +"For very large mappings that are larger than RAM, this would still cause " +"disk swapping to occur at a certain point. To avoid that, the " +"segmentation fault handler will evict the least recently used pages, once" +" a threshold defined at the creation of the CPLVirtualMem object has been" +" reached." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:76 +msgid "" +"For write support, another callback can be passed. It will be called " +"before a page is evicted so that user code has a chance to flush its " +"content to a more persistent storage." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:80 +msgid "" +"We also offer an alternative way of creating a CPLVirtualMem object, by " +"using memory file mapping mechanisms. This may be used by \"raw\" " +"datasets (EHdr driver for example) where the organization of data on disk" +" directly matches the organization of a in-memory array." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:86 +msgid "High-level usage" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:88 +msgid "Four new API are introduced (detailed in further section):" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:90 +msgid "" +"GDALDatasetGetVirtualMem() : takes almost the same arguments as " +"GDALDatasetRasterIO(), with the notable exception of a pData buffer. It " +"returns a CPLVirtualMem\\* object, from which the base address of the " +"virtual memory mapping can be obtained with CPLVirtualMemGetAddr()." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:98 +msgid "" +"GDALRasterBandGetVirtualMem(): equivalent of GDALDatasetGetVirtualMem() " +"that operates on a raster band object rather than a dataset object." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:102 +msgid "" +"GDALDatasetGetTiledVirtualMem(): this is a rather original API. Instead " +"of presenting a 2D view of the image data (i.e. organized rows by rows), " +"the mapping exposes it as an array of tiles, which is more suitable, " +"performance wise, when the dataset is itself tiled." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:109 +msgid "" +"When they are several bands, 3 different organizations of band components" +" are possible. To the best of our knowledge, there is no standard way of " +"calling those organizations, which consequently will be best illustrated " +"by the following schemas :" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:-1 +#: ../../source/development/rfc/rfc45_virtualmem.rst:114 +msgid "TIP / Tile Interleaved by Pixel" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:-1 +#: ../../source/development/rfc/rfc45_virtualmem.rst:119 +msgid "BIT / Band Interleaved by Tile" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:-1 +#: ../../source/development/rfc/rfc45_virtualmem.rst:124 +msgid "BSQ / Band SeQuential organization" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:129 +msgid "" +"GDALRasterBandGetTiledVirtualMem(): equivalent of " +"GDALDatasetGetTiledVirtualMem() that operates on a raster band object " +"rather than a dataset object." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:133 +msgid "" +"GDALGetVirtualMemAuto(): simplified version of " +"GDALRasterBandGetVirtualMem() where the user only specifies the access " +"mode. The pixel spacing and line spacing are returned by the function. " +"This is implemented as a virtual method at the GDALRasterBand level, so " +"that drivers have a chance of overriding the base implementation. The " +"base implementation just uses GDALRasterBandGetVirtualMem(). Overridden " +"implementation may use the memory file mapping mechanism instead. Such " +"implementations will be done in the RawRasterBand object and in the " +"GeoTIFF driver." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:144 +msgid "Details of new API" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:149 +msgid "Implemented by cpl_virtualmem.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:503 +msgid "Implemented by gdalvirtualmem.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:972 +msgid "Implemented by gdalrasterband.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1047 +msgid "" +"The CPLVirtualMem low-level machinery is only implemented for Linux now. " +"It assumes that returning from a SIGSEGV handler is possible, which is a " +"blatant violation of POSIX, but in practice it seems that most POSIX (and" +" non POSIX such as Windows) systems should be able to resume execution " +"after a segmentation fault." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1053 +msgid "" +"Porting to other POSIX operating systems such as MacOSX should be doable " +"with moderate effort. Windows has API that offer similar capabilities as " +"POSIX API with VirtualAlloc(), VirtualProtect() and " +"SetUnhandledExceptionFilter(), although the porting would undoubtly " +"require more effort." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1059 +msgid "" +"The existence of `libsigsegv <http://www.gnu.org/software/libsigsegv>`__ " +"that run on various OS is an evidence on its capacity of being ported to " +"other platforms." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1063 +msgid "" +"The trickiest part is ensuring that things will work reliably when two " +"concurrent threads that try to access the same initially unmapped page. " +"Without special care, one thread could manage to access the page that is " +"being filled by the other thread, before it is completely filled. On " +"Linux this can be easily avoided with the mremap() call. When a page is " +"filled, we don't actually pass the target page to the user callback, but " +"a temporary page. When the callback has finished its job, this temporary " +"page is mremap()'ed to its target location, which is an atomic operation." +" An alternative implementation for POSIX systems that don't have this " +"mremap() call has been tested : any declared threads that can access the " +"memory mapping are paused before the temporary page is memcpy'ed to its " +"target location, and are resumed afterwards. This requires threads to " +"priorly declare their \"interest\" for a memory mapping with " +"CPLVirtualMemDeclareThread(). Pausing a thread is interestingly non-" +"obvious : the solution found to do so is to send it a SIGUSR1 signal and " +"make it wait in a signal handler for this SIGUSR1 signal... It has not " +"been investigated if/how this could be done on Windows. " +"CPLVirtualMemIsAccessThreadSafe() has been introduced for that purpose." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1083 +msgid "" +"As far as CPLVirtualMemFileMapNew() is concerned, memory file mapping on " +"POSIX systems with mmap() should be portable. Windows has " +"CreateFileMapping() and MapViewOfFile() API that have similar " +"capabilities as mmap()." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1089 +msgid "Performance" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1091 +msgid "" +"No miraculous performance gain should be expected from this new " +"capability, when compared to code that carefully uses GDALRasterIO(). " +"Handling segmentation faults has a cost ( the operating system catches a " +"hardware exception, then calls the user program segmentation fault " +"handler, which does the normal GDAL I/O operations, and plays with page " +"mappings and permissions which invalidate some CPU caches, etc... ). " +"However, when a page has been realized, access to it should be really " +"fast, so with appropriate access patterns and cache size, good " +"performance should be expected." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1101 +msgid "" +"It should also be noted that in the current implementation, the " +"realization of pages is done in a serialized way, that is to say if 2 " +"threads which use 2 different memory mappings cause a segmentation fault " +"at the same time, they will not be dealt by 2 different threads, but one " +"after the other one." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1107 +msgid "" +"The overhead of virtual memory objects returned by GetVirtualMemAuto(), " +"when using the memory file mapping, should be lesser than the manual " +"management of page faults. However, GDAL has no control of the strategy " +"used by the operating system to cache pages." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1115 +msgid "" +"The maximum size of the virtual memory space (and thus a virtual memory " +"mapping) depends on the CPU architecture and OS limitations :" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1118 +msgid "on Linux AMD64, 128 TB." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1119 +msgid "on Linux x86, 2 GB." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1120 +msgid "On Windows AMD64 (unsupported by the current implementation), 8 TB." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1121 +msgid "On Windows x86 (unsupported by the current implementation), 2 GB." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1123 +msgid "" +"Clearly, the main interest of this new functionality is for AMD64 " +"platforms." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1126 +msgid "" +"On a Linux AMD64 machine with 4 GB RAM, the Python binding of " +"GDALDatasetGetTiledVirtualMem() has been successfully used to access " +"random points on the new `Europe 3'' DEM dataset " +"<http://www.eea.europa.eu/data-and-maps/data/eu-dem/#tab-original-" +"data>`__, which is a 20 GB compressed GeoTIFF ( and 288000 \\* 180000 \\*" +" 4 = 193 GB uncompressed )" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1134 +msgid "Related thoughts" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1136 +msgid "" +"Some issues with system calls such as read() or write(), or easier multi-" +"threading could potentially be solved by making a FUSE (File system in " +"USEr space) driver that would expose a GDAL dataset as a file, and the " +"mmap()'ing the file itself. However FUSE drivers are only available on " +"POSIX OS, and need root privilege to be mounted (a FUSE filesystem does " +"not need root privilege to run, but the mounting operation does)." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1145 +msgid "Open questions" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1147 +msgid "" +"Due to the fact that it currently only works on Linux, should we mark the" +" API as experimental for now ?" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1151 +msgid "Backward compatibility issues" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1153 +msgid "" +"C/C++ API --> compatible (new API). C ABI --> compatible (new API). C++ " +"ABI --> incompatibility because GDALRasterBand has a new virtual method." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1157 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:37 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:56 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:54 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:268 +msgid "Updated drivers" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1159 +msgid "" +"The RawRasterBand object and GeoTIFF drivers will be updated to implement" +" GetVirtualMemAuto() and offer memory file mapping when possible (see " +"above documented restrictions on when this is possible)." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1163 +msgid "" +"In future steps, other drivers such as the VRT driver (for " +"VRTRawRasterBand) could also offer a specialized implementation of " +"GetVirtualMemAuto()." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1170 +msgid "" +"The high level API (dataset and raster band) API is available in Python " +"bindings." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1173 +msgid "" +"GDALDatasetGetVirtualMem() is mapped as Dataset.GetVirtualArray(), which " +"returns a NumPy array." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1192 +msgid "Similarly for GDALDatasetGetTiledVirtualMem() :" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1213 +msgid "And the Band object has the following 3 methods :" +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1243 +msgid "" +"Note: dataset/Band.GetVirtualMem()/GetTiledVirtualMem() methods are also " +"available. They return a VirtualMem python object that has a GetAddr() " +"method that returns a Python memoryview object (Python 2.7 or later " +"required). However, using such object does not seem practical for non-" +"Byte data types." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1252 +msgid "" +"The autotest suite will be extended to test the Python API of this RFC. " +"It will also test the specialized implementations of GetVirtualMemAuto() " +"in RawRasterBand and the GeoTIFF drivers. In autotest/cpp, a " +"test_virtualmem.cpp file tests concurrent access to the same pages by 2 " +"threads." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1261 +msgid "" +"Implementation will be done by Even Rouault in GDAL/OGR trunk. The " +"proposed implementation is attached as a `patch " +"<http://trac.osgeo.org/gdal/attachment/wiki/rfc45_virtualmem/virtualmem.patch>`__." +msgstr "" + +#: ../../source/development/rfc/rfc45_virtualmem.rst:1268 +msgid "+1 from EvenR, FrankW, DanielM and JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:5 +msgid "RFC 46: GDAL/OGR unification" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:16 +msgid "" +"In the 1.X series of GDAL/OGR, the GDAL/raster and OGR/vector sides are " +"quite different on some aspects even where there is no strong reason for " +"them to be different, particularly in the structure of drivers. This RFC " +"aims at unifying the OGR driver structure with the GDAL driver structure." +" The main advantages of using the GDAL driver structure are :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:22 +msgid "" +"metadata capabilities : description of driver, extensions, creation " +"options, virtual IO capability ..." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:24 +msgid "efficient driver identification and opening." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:26 +msgid "" +"Similarly, OGR datasource and layer classes lack the metadata mechanisms " +"offered by the corresponding GDAL dataset and raster band classes." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:29 +msgid "" +"Another aspect is that the separation between GDAL \"datasets\" and OGR " +"\"datasources\" is sometimes artificial. Various data containers can " +"accept both data types. The list of drivers that have a GDAL side and OGR" +" side is : SDTS, PDS, GRASS, KML, Spatialite/Rasterlite, GeoPackage " +"(raster side not yet implemented), PostGIS/PostGIS Raster, PDF, PCIDSK, " +"FileGDB (raster side not yet implemented). For applications that are " +"interested in both, this currently means to open the file twice with " +"different API. And for update mode, for file-based drivers, the updates " +"must be done sequentially to avoid opening a file twice simultaneously in" +" update mode and making conflicting changes." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:41 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:249 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:158 +msgid "Related RFCs" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:43 +msgid "" +"There are a few related past RFCs that have never been adopted but " +"strongly relate to RFC 46 :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:46 +msgid "" +"`RFC 10: OGR Open Parameters <./rfc10_ogropen>`__. All the functionality " +"described in RFC 10 is included in RFC 46, mainly the GDALOpenEx() new " +"API" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:49 +msgid "" +"`RFC 25: Fast Open <./rfc25_fast_open>`__. RFC 25 mentions avoiding to " +"systematically listing the sibling files to the file being opened. This " +"can now achieved in RFC 46 by lazy loading with " +"GDALOpenInfo::GetSiblingFiles(). At least Identify() should not trigger " +"GetSiblingFiles()." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:54 +msgid "" +"`RFC 36: Allow specification of intended on GDALOpen " +"<./rfc36_open_by_drivername>`__. The new GDALOpenEx() accepts a list of a" +" subset drivers that must be probed, as suggested by RFC36. The " +"specification of the drivers on the command line of utilities could be " +"easily done through a new option, but that's not in the scope of RFC 46." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:60 +msgid "" +"`RFC 38: OGR Faster Open <./rfc38_ogr_faster_open>`__ is completely " +"included in RFC 46 through the possibility of using Open(GDALOpenInfo*) " +"in OGR drivers" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:65 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:162 +msgid "Self-assigned development constraints" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:67 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:164 +msgid "" +"The changes should have moderate impact on the existing GDAL/OGR code " +"base, and particularly on most of its code, that lies in drivers. " +"Existing users of the GDAL/OGR API should also be moderately impacted by " +"the changes, if they do not need to use the new offered capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:73 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:174 +msgid "Core changes: summary" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:75 +msgid "OGRSFDriver extends GDALDriver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:76 +msgid "Vector drivers can be implemented as GDALDriver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:77 +msgid "" +"OGRSFDriverRegistrar is a compatibility wrapper around GDALDriverManager " +"for legacy OGRSFDriver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:79 +msgid "OGRDataSource extends GDALDataSource." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:80 +msgid "GDALOpenEx() API is added to be able to open \"mixed\" datasets." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:81 +msgid "OGRLayer extends GDALMajorObject, thus adding metadata capability." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:82 +msgid "" +"The methods of OGRDataSource related to layers are moved to GDALDataset, " +"making it both a raster and vector capable container." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:84 +msgid "Performance improvements in GDALOpenInfo() mechanism." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:85 +msgid "" +"New driver metadata item to describe open options (i.e. deprecate the use" +" of configuration option)." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:87 +msgid "New driver metadata item to describe layer creation options." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:90 +msgid "Core changes: details" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:93 +msgid "Drivers and driver registration" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:95 +msgid "" +"The OGRSFDriver now extends GDALDriver and is meant as being a legacy way" +" of implementing a vector driver. It is kept mainbly because, in the " +"current implementation, not all drivers have been migrated to being " +"\"pure\" GDALDriver. The CopyDataSource() virtual method has been removed" +" since no in-tree drivers implement it. The inheritance to GDALDriver " +"make it possible to manage vector drivers by the GDALDriverManager, and " +"to be able to attach metadata to them, to document driver long name, link" +" to documentation, file extension, datasource creation options with the " +"existing GDAL\\_DMD\\_\\* metadata items." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:106 +msgid "" +"Drivers directly inheriting from GDALDriver (to be opposed to those " +"inheriting from OGRSFDriver) should : - declare SetMetadataItem( " +"GDAL_DCAP_VECTOR, \"YES\" ). - implement pfnOpen() for dataset opening - " +"optionally, implement pfnCreate() for dataset creation. For vector " +"drivers, the nBands parameter of Create() is supposed to be passed to 0. " +"- optionally, implement pfnDelete() for dataset deletion" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:113 +msgid "" +"The *C* OGR Driver API will still work with drivers that have been " +"converted as \"pure\" GDALDrivers (this is not true of the C++ OGR Driver" +" API). For example OGR_Dr_GetName() calls GDALDriver::GetDescription(), " +"OGR_Dr_CreateDatasource() calls GDALDriver::Create(), etc..." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:119 +msgid "" +"The C++ definition of GDALDriver is extended with the following function " +"pointers so that it can work with legacy OGRSFDriver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:140 +msgid "GDALDriver::Create() can accept nBands == 0 for a vector capable driver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:143 +msgid "" +"GDALDriver::DefaultCreateCopy() can accept a dataset with 0 bands for a " +"vector capable driver, and if the output dataset has layer creation " +"capability and the source dataset has layers, it copies the layers from " +"the source dataset into the target dataset." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:148 +msgid "" +"GDALDriver::Identify() now iterates over all kinds of drivers. It has " +"been modified to do a first pass on drivers that have an implementation " +"of Identify(). If no match is found, it does a second pass on all drivers" +" and use the potentially slower Open() as the identification method." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:154 +msgid "" +"Related to the above point, the implementations of " +"GDALDriver::pfnIdentify function pointer used to return a boolean value " +"to indicate if the passed GDALOpenInfo was a match for the driver. For " +"some drivers, this was too restrictive so that they were able to " +"implement Identify(). For example where the detection logic can return " +"\"yes, I definitely recognize that file\", \"no, it is not for me\" or " +"\"I have not enough elements in GDALOpenInfo to be able to tell\". That " +"last state can now be advertized with a negative return value." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:164 +msgid "" +"The OGRSFDriverRegistrar is trimmed down to be mostly a wrapper around " +"GDALDriverManager. In particular, it does not contain any longer a list " +"of drivers. The Open(), OpenShared(), ReleaseDataSource(), " +"DeregisterDriver() and AutoLoadDrivers() methods are removed from the " +"class. This change can have impact on C++ code. A few adaptations in OGR " +"utilities have been done to accommodate for those changes. The " +"RegisterDriver() API has been kept for legacy OGR drivers and it " +"automatically sets SetMetadataItem( GDAL_DCAP_VECTOR, \"YES\" ). The " +"GetDriverCount(), GetDriver() and GetDriverByName() methods delegate to " +"GDALDriverManager and make sure to only take into account drivers that " +"have the GDAL_DCAP_VECTOR capability. In the case a driver has the same " +"name as GDAL and OGR driver, the OGR variant is internally prefixed with " +"OGR\\_, and GetDriverByName() will first try the OGR\\_ variant. The " +"GetOpenDSCount() and GetOpenDS() have now a dummy implementation " +"returning 0/NULL. For reference, neither MapServer nor QGIS use those " +"functions." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:181 +msgid "" +"OGRRegisterAll() is now an alias of GDALAllRegister(). The past " +"OGRRegisterAll() is now renamed OGRRegisterAllInternal() and called by " +"GDALAllRegister(). So, GDALAllRegister() and OGRRegisterAll() are now " +"equivalent and register all drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:186 +msgid "GDALDriverManager has received a few changes :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:188 +msgid "" +"use of a map from driver name to driver object to speed-up " +"GetDriverByName()" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:190 +msgid "" +"accept OGR_SKIP and OGR_DRIVER_PATH configuration options for backward " +"compatibility." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:192 +msgid "" +"The recommended separator for driver names in GDAL_SKIP is now comma " +"instead of space (similarly to what OGR_SKIP does). This is to make it " +"possible to define OGR driver names in GDAL_SKIP that have spaces in " +"their names like \"ESRI Shapefile\" or \"MapInfo File\". If there is no " +"comma in the GDAL_SKIP value, then space separator is assumed (backward " +"compatibility)." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:198 +msgid "" +"removal of GetHome()/SetHome() methods whose purpose seemed to define an " +"alternate path for the search directory of plugins. Those methods only " +"existed at the C++ level, and are redundant with GDAL_DRIVER_PATH " +"configuration option" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:203 +msgid "" +"Raster-capable drivers should declare SetMetadataItem( GDAL_DCAP_RASTER, " +"\"YES\" ). All in-tree GDAL drivers have been patched to declare it. But " +"the registration code detects if a driver does not declare any of " +"GDAL_DCAP_RASTER nor GDAL_DCAP_VECTOR, in which case it declares " +"GDAL_DCAP_RASTER on behalf of the un-patched driver, with a debug message" +" inviting to explicitly set it." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:210 +msgid "New metadata items :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:212 +msgid "" +"GDAL_DCAP_RASTER=YES / GDAL_DCAP_VECTOR=YES at driver level. To declare " +"that a driver has raster/vector capabilities. A driver can declare both." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:215 +msgid "" +"GDAL_DMD_EXTENSIONS (with a final S) at driver level. This is a small " +"evolution of GDAL_DMD_EXTENSION where one can specify several extensions " +"in the value string. The extensions are space-separated. For example " +"\"shp dbf\", \"tab mif mid\", etc... For ease of use, " +"GDALDriver::SetMetadataItem(GDAL_DMD_EXTENSION) also sets the passed " +"value as GDAL_DMD_EXTENSIONS, if it is not already set. So new code can " +"always use GDAL_DMD_EXTENSIONS." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:222 +msgid "" +"GDAL_DMD_OPENOPTIONLIST at driver level. The value of this item is an XML" +" snippet with a format similar to creation options. GDALOpenEx(), once it" +" has identified with Identify() that a driver accepts the file, will " +"validate the passed open option list with the authorized open option " +"list. Below an example of such an authorized open option list in the S57 " +"driver" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:295 +msgid "Datasets / Datasources" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:297 +msgid "The main methods from OGRDataSource have been moved to GDALDataset :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:376 +msgid "" +"OGRDataSource::SyncToDisk() has been removed. The equivalent " +"functionality should be implemented in existing FlushCache(). " +"GDALDataset::FlushCache() nows does the job of the previous generic " +"implementation of OGRDataSource::SyncToDisk(), i.e. iterate over all " +"layers and call SyncToDisk() on them." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:382 +msgid "GDALDataset has now a protected ICreateLayer() method." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:402 +msgid "" +"GDALOpenEx() is added to be able to open raster-only, vector-only, or " +"raster-vector datasets. It accepts read-only/update mode, shared/non-" +"shared mode. A list of potential candidate drivers can be passed. If " +"NULL, all drivers are probed. A list of open options (NAME=VALUE syntax) " +"can be passed. If the list of sibling files has already been established," +" it can also be passed. Otherwise GDALOpenInfo will establish it." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:457 +msgid "GDALOpenInfo class. The following changes are done :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:459 +msgid "" +"the second argument of the constructor is now nOpenFlags instead of " +"GDALAccess, with same semantics as GDALOpenEx(). GDALOpenInfo uses the " +"read-only/update bit to \"compute\" the eAccess flag that is heavily used" +" in existing drivers. Drivers with both raster and vector capabilities " +"can use the GDAL_OF_VECTOR/GDAL_OF_RASTER bits to determine the intent of" +" the caller. For example if a caller opens with GDAL_OF_RASTER only and " +"the dataset only contains vector data, the driver might decide to not " +"open the dataset (if it is a read-only driver. If it is a driver with " +"update capability, it should do that only if the opening is done in read-" +"only mode)." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:470 +msgid "" +"the open options passed to GDALOpenEx() are stored into a " +"papszOpenOptions member of GDALOpenInfo, so that drivers can use them." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:473 +msgid "" +"the \"FILE\\* fp\" member is transformed into \"VSILFILE\\* fpL\". This " +"change is motivated by the fact that most popular drivers now use the VSI" +" Virtual File API, so they can now directly use the fpL member instead of" +" re-opening again the file. A global pass on all in-tree GDAL drivers " +"that used fp has been made." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:478 +msgid "" +"A VSIStatExL() was done previously to determine the nature of the file " +"passed. Now, we optimistically begin with a VSIFOpenL(), assuming that in" +" most use cases the passed filename is a file. If the opening fails, " +"VSIStatExL() is done to determine the nature of the filename." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:483 +msgid "" +"If the requested access mode is update, the opening of the file with " +"VSIFOpenL() is done with \"rb+\" permissions to be directly usable." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:486 +msgid "" +"The papszSiblingFiles member is now private. It is accessed by a " +"GetSiblingFiles() method that does the ReadDir() on demand. This can " +"speed up the Identify() method that generally does not require to know " +"sibling files." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:490 +msgid "" +"A new method, TryToIngest(), is added to read more than the first 1024 " +"bytes of a file. This is useful for a few vector drivers, like GML or " +"NAS, that must fetch a bit more bytes to be able to identify the file." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:496 +msgid "Layer" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:498 +msgid "" +"OGRLayer extends GDALMajorObject. Drivers can now define layer metadata " +"items that can be retrieved with the usual " +"GetMetadata()/GetMetadateItem() API." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:502 +msgid "" +"The GetInfo() method has been removed. It has never been implemented in " +"any in-tree drivers and has been deprecated for a long time." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:508 +msgid "" +"The deprecated and unused GDALProjDefH and GDALOptionDefinition types " +"have been removed from gdal.h" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:511 +msgid "" +"GDALGeneralCmdLineProcessor() now interprets the nOptions (combination of" +" GDAL_OF_RASTER and GDAL_OF_RASTER) argument as the type of drivers that " +"should be displayed with the --formats option. If set to 0, " +"GDAL_OF_RASTER is assumed." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:516 +msgid "" +"the --formats option of GDAL utilities outputs whether drivers have " +"raster and/or vector capabilities" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:519 +msgid "" +"the --format option of GDAL utilities outputs GDAL_DMD_EXTENSIONS, " +"GDAL_DMD_OPENOPTIONLIST, GDAL_DS_LAYER_CREATIONOPTIONLIST." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:522 +msgid "" +"OGRGeneralCmdLineProcessor() use GDALGeneralCmdLineProcessor() " +"implementation, restricting --formats to vector capable drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:526 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:438 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:96 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:185 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:113 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:87 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:304 +msgid "Changes in drivers" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:528 +msgid "OGR PCIDSK driver has been merged into GDAL PCIDSK driver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:530 +msgid "OGR PDF driver has been merged into GDAL PDF driver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:532 +msgid "" +"A global pass has been made to in-tree OGR drivers that have to open a " +"file to determine if they recognize it. They have been converted to " +"GDALDriver to accept a GDALOpenInfo argument and they now use its " +"pabyHeader field to examine the first bytes of files. The number of " +"system calls realated to file access (open/stat), in order to determine " +"that a file is not recognized by any OGR driver, has now dropped from 46 " +"in GDAL 1.11 to 1. The converted drivers are : AeronavFAA, ArcGEN, " +"AVCBin, AVCE00, BNA, CSV, DGN, EDIGEO, ESRI Shapefile, GeoJSON, GeoRSS, " +"GML, GPKG, GPSBabel, GPX, GTM, HTF, ILI1, ILI2, KML, LIBKML, MapInfo " +"File, MySQL, NAS, NTF, OpenAIR, OSM, PDS, REC, S57, SDTS, SEGUKOOA, SEGY," +" SOSI, SQLite, SUA, SVG, TIGER, VFK, VRT, WFS" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:545 +msgid "Long driver description is set for most OGR drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:547 +msgid "" +"All classes deriving from OGRLayer have been modified to call " +"SetDescription() with the value of GetName()/poFeatureDefn->GetName(). " +"test_ogrsf tests that it is properly set." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:552 +msgid "" +"Following drivers are kept as OGRSFDriver, but their Open() method does " +"early extension/prefix testing to avoid datasource object to be " +"instantiated : CartoDB, CouchDB, DXF, EDIGEO, GeoConcept, GFT, GME, " +"IDRISI, OGDI, PCIDSK, PG, XPlane." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:557 +msgid "" +"Identify() has been implemented for CSV, DGN, DXF, EDIGEO, GeoJSON, GML, " +"KML, LIBKML, MapInfo File, NAS, OpenFileGDB, OSM, S57, Shape, SQLite, " +"VFK, VRT." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:561 +msgid "" +"GDAL_DMD_EXTENSION/GDAL_DMD_EXTENSIONS set for following drivers: AVCE00," +" BNA, CSV, DGN, DWG, DXF, EDIGEO, FileGDB, Geoconcept, GeoJSON, Geomedia," +" GML, GMT, GPKG, GPX, GPSTrackMaker, IDRISI Vector, Interlis 1, Interlis " +"2, KML, LIBKML, MDB, MapInfo File, NAS, ODS, OpenFileGDB, OSM, PGDump, " +"PGeo, REC, S57, ESRI Shapefile, SQLite, SVG, WaSP, XLS, XLSX, XPlane." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:568 +msgid "" +"Document dataset and layer creation options of BNA, DGN, FileGDB, " +"GeoConccept, GeoJSON, GeoRSS, GML, GPKG, KML, LIBKML, PG, PGDump and ESRI" +" Shapefile drivers as GDAL_DMD_CREATIONOPTIONLIST / " +"GDAL_DS_LAYER_CREATIONOPTIONLIST." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:573 +msgid "Add open options AAIGRID, PDF, S57 and ESRI Shapefile drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:575 +msgid "GetFileList() implemented in OpenFileGDB, Shapefile and OGR VRT drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:578 +msgid "" +"Rename datasource SyncToDisk() as FlushCache() for LIBKML, OCI, ODS, XLSX" +" drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:581 +msgid "" +"Use poOpenInfo->fpL to avoid useless file re-opening in GTiff, PNG, JPEG," +" GIF, VRT, NITF, DTED." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:584 +msgid "HTTP driver: declared as GDAL_DCAP_RASTER and GDAL_DCAP_VECTOR driver." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:587 +msgid "RIK: implement Identify()" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:589 +msgid "" +"Note: the compilation and good working of the following OGR drivers " +"(mostly proprietary) could not be tested: ArcObjects, DWG, DODS, SDE, " +"FME, GRASS, IDB, OCI, MSSQLSpatial(compilation OK, but not runtime " +"tested)" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:595 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:503 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:112 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:201 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:93 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:413 +msgid "Changes in utilities" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:597 +msgid "gdalinfo accepts a -oo option to define open options" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:598 +msgid "ogrinfo accepts a -oo option to define open options" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:599 +msgid "" +"ogr2ogr accepts a -oo option to define input dataset open options, and " +"-doo to define destination dataset open options" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:603 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:518 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:136 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:211 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:132 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:98 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:191 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:77 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:124 +msgid "Changes in SWIG bindings" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:605 +msgid "Python and Java bindings:" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:607 +msgid "" +"add new GDALDataset methods taken from OGRDataSource : CreateLayer(), " +"CopyLayer(), DeleteLayer(), GetLayerCount(), GetLayerByIndex(), " +"GetLayerByName(), TestCapability(), ExecuteSQL(), ReleaseResultSet(), " +"GetStyleTable() and SetStyleTable()." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:612 +msgid "make OGR Driver, DataSource and Layer objects derive from MajorObject" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:615 +msgid "" +"Perl and CSharp: make sure that it still compiles but some work would " +"have to be done by their mainteners to be able to use the new " +"capabilities" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:620 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:197 +msgid "Potential changes that are *NOT* included in this RFC" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:622 +msgid "\"Natural\" evolutions of current RFC :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:624 +msgid "Unifying the GDAL MEM and OGR Memory drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:625 +msgid "Unifying the GDAL VRT and OGR VRT drivers." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:627 +msgid "Further unification steps :" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:629 +msgid "" +"Source tree changes to move OGR drivers from ogr/ogrsf_frmts/ to frmts/ ," +" to move ogr/ogrsf_frmts/generic/\\* to gcore/\\*, etc..." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:631 +msgid "Documentation unification (pages with list of drivers, etc...)" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:632 +msgid "Renaming to remove traces of OGR namespace : OGRLayer -> GDALLayer, etc..." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:634 +msgid "" +"Kill --without-ogr compilation option ? It has been preserved in a " +"working state even if it embeds now ogr/ogrsf_frmts/generic and " +"ogr/ogrsf_frmts/mitab for conveniency." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:637 +msgid "" +"Unification of some utilities : \"gdal info XXX\", \"gdal convert XXX\" " +"that would work on all kind of datasets." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:641 +#: ../../source/development/rfc/rfc49_curve_geometries.rst:551 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:221 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:99 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:471 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:205 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:428 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:150 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:60 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:381 +#: ../../source/development/rfc/rfc87_signed_int8.rst:83 +#: ../../source/development/rfc/rfc88_googletest.rst:218 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:113 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:390 +#: ../../source/development/rfc/rfc91_dataset_close.rst:140 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:151 +#: ../../source/development/rfc/rfc93_update_feature.rst:244 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:151 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:94 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:360 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:276 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:129 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:688 +msgid "Backward compatibility" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:643 +msgid "" +"GDALDriverManager::GetDriverCount(), GetDriver() now returns OGR drivers," +" as well as GDAL drivers" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:646 +msgid "" +"The reference counting in GDAL datasets and GDAL 1.X OGR datasources was " +"a bit different. It starts at 1 for GDAL datasets, and started at 0 for " +"OGR datasources. Now that OGRDataSource is basically a GDALDataset, it " +"starts at 1 for both cases. Hopefully there are very few users of the " +"OGR_DS_GetRefCount() API. If it was deemed necessary we could restore the" +" previous behavior at the C API, but that would not be possible at the " +"C++ level. For reference, neither MapServer nor QGIS use " +"OGR_DS_GetRefCount()." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:658 +msgid "" +"A pass should be made on the documentation to check that all new methods " +"are properly documented. The OGR general documentation (especially C++ " +"API Read/Write tutorial, Driver implementation tutorial and OGR " +"architecture) should be updated to reflect the changes." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:666 +msgid "" +"Very few changes have been made so that the existing autotest suite still" +" passes. Additions have been made to test the GDALOpenEx() API and the " +"methods \"imported\" from OGRDataSource into GDALDataset." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:671 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:235 +msgid "Version numbering" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:673 +msgid "" +"Although the above describes changes should have very few impact on " +"existing applications of the C API, some behavior changes, C++ level " +"changes and the conceptual changes are thought to deserve a 2.0 version " +"number." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:681 +msgid "Implementation will be done by Even Rouault." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:683 +msgid "" +"The proposed implementation lies in the \"unification\" branch of the " +"`https://github.com/rouault/gdal2/tree/unification " +"<https://github.com/rouault/gdal2/tree/unification>`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:687 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/unification " +"<https://github.com/rouault/gdal2/compare/unification>`__" +msgstr "" + +#: ../../source/development/rfc/rfc46_gdal_ogr_unification.rst:693 +msgid "+1 from JukkaR, FrankW, DanielM, TamasS and EvenR." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:5 +msgid "" +"RFC 47: Per Dataset Caching and GDALRasterBand Multithreading (not " +"implemented)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:7 +msgid "Author: Blake Thompson" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:9 +msgid "Contact: flippmoke at gmail dot com" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:16 +msgid "" +"When utilizing GDAL in multithread code, it was found that often the " +"limiting portion of the code was often the LRU block cache within GDAL. " +"This is an attempt to make the LRU cache more efficient in multithreaded " +"situations by making it possible to have multiple LRU per dataset and " +"optimizing when locking occurs. Additionally, the changes outlined " +"attempt to find an efficient manner to manage data within the cache." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:23 +msgid "*This change attempts to:*" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:25 +msgid "Make the caching system within raster datasets:" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:27 +msgid "Thread Safe" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:28 +msgid "Provide performance more linearly with an increasing number of threads" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:31 +msgid "Reduce the scope of the current cache locking." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:32 +msgid "Optionally enable a per dataset cache (rather then a global cache)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:33 +msgid "Make Mem datasets READ thread safe per dataset." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:34 +msgid "" +"Lay the ground work for future development to increase thread safety in " +"drivers." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:37 +msgid "*This change does NOT attempt to:*" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:39 +msgid "Make all drivers thread safe" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:40 +msgid "Make datasets thread safe" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:43 +msgid "Two Different Solutions" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:45 +msgid "" +"Two different ways for solving this problem are being proposed and both " +"have been coded up (test code for each still to be written). However, " +"both share some common solutions. First I will go over the common changes" +" for the two different methods, then the ways in which the two solutions " +"differ." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:52 +msgid "Pull Requests" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:54 +msgid "" +"`Pull Request #1 <https://github.com/OSGeo/gdal/pull/38>`__ - SOLUTION 1 " +"(Dataset RW Locking)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:56 +msgid "" +"`Pull Request #2 <https://github.com/OSGeo/gdal/pull/39>`__ - SOLUTION 2 " +"(Block RW Locking)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:60 +msgid "Common Solution" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:63 +msgid "Dataset Caching" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:65 +msgid "" +"The static global mutex that is limiting performance is located within " +"gcore/gdalrasterblock.cpp. This mutex is there to protect the setting of " +"the maximum cache, the LRU cache itself itself, and the current size of " +"the cache. The current scope of this mutex makes it lock for extended " +"periods once the cache is full, and new memory is being initialized in " +"GDALRasterBlock::Internalize()." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:72 +msgid "" +"In order to remove the need for this LRU cache to be locked more often a " +"new global config option is introducted \"GDAL_DATASET_CACHING\". This " +"causes the LRU cache to be per dataset when set to \"YES\", rather then a" +" global cache (\"NO\" Default). Doing this will also allow threaded " +"applications to flush only the cache for a single dataset, improving " +"performance in some situations for two reasons. First a cache of a more " +"commonly used dataset, might be set separately from other datasets, " +"meaning that it is more likely to remain cached. The second is that the " +"lack of a common global mutex will result in a less likely situation of " +"two threads locking the same mutex if operations are being performed on " +"different datasets." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:84 +msgid "" +"In order to have management of the different caches, a " +"GDALRasterBlockManager class is introduced. This class is responsible for" +" the management of the cache in the global or per dataset situations." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:89 +msgid "GDALRasterBlockManager" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:118 +msgid "" +"Many of the operations originally done by statistics:* within " +"GDALRasterBlock are now moved into the GDALRasterBlockManager." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:124 +msgid "Every GDALDataset now has a:" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:130 +msgid "This is set at initialization of the dataset via:" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:149 +msgid "" +"In order to make caching safer and more efficient, a mutex as also " +"introduced in GDALRasterBand as well. The job of this mutex is to protect" +" the RasterBlock array per band (papoBlocks)." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:154 +msgid "Thread Safety and the Two Solutions" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:156 +msgid "" +"The multithreading of GDAL is a complicated thing, while these changes do" +" seek to *improve* threading within GDAL. It does not *solve* threading " +"problems within GDAL and make it truly thread safe. The goal of this " +"change is simply to make the cache thread safe, in order to achieve this " +"three mutexes are utilized. Where these three mutexes are located is " +"different between the two solutions proposed." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:166 +msgid "Solution 1 (RW Mutex in GDALDataset )" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:169 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:234 +msgid "Mutexes" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:171 +msgid "For solution 1 the three mutexes are:" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:173 +msgid "Dataset RW Mutex (per GDALDataset)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:174 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:238 +msgid "Band Mutex (per GDALRasterBand)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:175 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:240 +msgid "RBM Mutex (per GDALRasterBlockManager)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:177 +msgid "" +"In order to prevent deadlocks, a priority of the mutexes is established " +"in the order they are listed. For example if you have the Band Mutex, you" +" may not obtain the Dataset RW Mutex, unless it was obtained prior to the" +" Band Mutex being obtained. However, the goal should always be to never " +"have more then mutex at a time!" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:184 +msgid "Dataset RW Mutex" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:186 +msgid "" +"The objective of the Dataset RW Mutex is to protect the data stored " +"within the GDALRasterBlocks associated with a dataset, and lock during " +"large Read or Write operations. This prevents two different threads from " +"using memcpy on the same GDALRasterBlock at the same time. This mutex " +"normally lies within the GDALDataset, but in the case of a standalone " +"GDALRasterBand, it utilizes a new mutex on the Band." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:194 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:251 +msgid "Band Mutex" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:196 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:253 +msgid "" +"The objective of the Band Mutex is to manage the control of the array of " +"blocks in the GDALRasterBand, and manages the locking of the " +"GDALRasterBlocks. This is a per GDALRasterBand Mutex." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:201 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:260 +msgid "RBM Mutex" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:203 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:262 +msgid "" +"The objective of the RBM Mutex is to manage control of the LRU cache. " +"This mutex is responsible for the control of the management of the " +"cache's linked list and total amount of data stored in the cache." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:208 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:278 +msgid "Pros" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:210 +msgid "" +"This is a much more simple solution of the two different possible " +"solutions. Since the protection of the Blocks are done at the Dataset " +"level, it prevents the problem of some drivers such as geotiff where more" +" then one band might be accessed in the reading or writing of one band. " +"Therefore with out this protection here it could cause issues if locking " +"was just at a band level per block's data." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:218 +#: ../../source/development/rfc/rfc47_dataset_caching.rst:294 +msgid "Cons" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:220 +msgid "" +"This solution is not perhaps the most optimal way to lock because the " +"protection of the IReadBlock, IWriteBlock, and IRasterIO routines is over" +" the entire dataset. This is very limiting when you are reading the same " +"dataset in a threaded environment, because it is not possible to read " +"more then one block at a time." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:229 +msgid "Solution 2 (RW Mutex in GDALRasterBlock )" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:236 +msgid "For solution 2 the three mutexes are:" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:241 +msgid "Block RW Mutex (per GDALRasterBlock)" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:243 +msgid "" +"In order to prevent deadlocks the band mutex has priority. This means " +"that you can not get the Band Mutex if you have the RBM or Blow RW Mutex," +" unless you already had the Band Mutex prior to this. You may not obtain " +"the Block mutex and the RBM mutex at the same time." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:267 +msgid "Block RW Mutex" +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:269 +msgid "" +"The objective of the Block RW Mutex is to protect the data stored within " +"the GDALRasterBlocks associated with a dataset, and lock during large " +"Read or Write operations. This prevents two different threads from using " +"memcpy on the same GDALRasterBlock at the same time. It is created on a " +"per block basis." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:280 +msgid "" +"This is probably the most complete solution to making an intensive and " +"fast threaded solution for the blocking. This is because the IReadWrite, " +"IWriteBlock, and IRasterIO now are able to possibly pass a mutex with " +"their calls, as a void pointer pointer. A change was made to the mutex as" +" well such that a void pointer pointer that is NULL passed to " +"CPLMutexHolderD, will not result in any pointer being created or any " +"locking to occur. This means much of the behavior of the existing code " +"can be maintained by simply passing a NULL value for the mutex. All of " +"these changes allow the drivers to maintain much more control over the " +"way that locking occurs when protecting the data inside a block." +msgstr "" + +#: ../../source/development/rfc/rfc47_dataset_caching.rst:296 +msgid "" +"Obviously, this is a much more complex solution and therefore is harder " +"to manage. It means that writing a driver is not as trivial as before and" +" care must be taken in how locking is done within the driver in order to " +"prevent deadlocks and maintain thread safety. The other issue that might " +"arise from this is a slight slow down in non-threaded code because of the" +" extra cycles spent locking data that will not be accessed in a threaded " +"manner. Additionally, it might have issues in windows if too many mutexes" +" are created (as there are quite a few more since it is a per " +"GDALRasterBlock mutex). (Note: Not sure how I will be able to test this " +"properly?)" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:5 +msgid "RFC 48: Geographical networks support" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:7 +msgid "Author: Mikhail Gusev, Dmitry Baryshnikov" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:9 +msgid "Contact: gusevmihs at gmail dot com, polimax@mail.ru" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:11 +msgid "Status: adopted, implemented in GDAL 2.1" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:14 +msgid "Introduction" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:16 +msgid "" +"This document proposes the integration of the results of GSoC 2014 " +"project “GDAL/OGR Geography Network support” into GDAL library. GNM " +"(Geographical Network Model) intends to bring the capabilities to create," +" manage and analyse networks built over spatial data in GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:21 +msgid "" +"GSoC project description: " +"`http://trac.osgeo.org/gdal/wiki/geography_network_support " +"<http://trac.osgeo.org/gdal/wiki/geography_network_support>`__" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:24 +msgid "" +"GDAL fork with all changes in trunk: `https://github.com/MikhanGusev/gdal" +" <https://github.com/MikhanGusev/gdal>`__" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:27 +msgid "" +"GSoC blog: `http://gsoc2014gnm.blogspot.ru/ " +"<http://gsoc2014gnm.blogspot.ru/>`__" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:31 +msgid "Purpose and description" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:33 +msgid "" +"There is a need to have an instrument in GDAL which on the one hand " +"provides an abstraction for different existed network formats (pgRouting," +" OSRM, GraphHopper, SpatiaLite networks, etc.), like GDAL (previously " +"OGR) provides one for spatial vector formats, and on the other hand " +"provides a network functionality to those spatial formats which does not " +"have it at all (Shapefiles)." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:40 +msgid "" +"Such instrument is implemented as a separate set of C++ classes, called " +"GNM. The two main of them represent an abstract network (GNMNetwork " +"class) and the network of ”GDAL-native” or generic format " +"(GNMGenericNetwork class). An abstract network is used by user as a " +"common interface to manage his network data. The list of underlying " +"format-specific classes can be extended anytime like a list of GDAL " +"drivers to support more network formats. The ”GDAL-native” format " +"implements the abstract network and is used to provide the network " +"functionality to the spatial formats which are already supported by GDAL." +" All the network data of this format is stored in the special set of " +"layers along with spatial data in a spatial dataset (internally " +"GDALDataset and OGRLayer are widely used)." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:53 +msgid "What does the interface of working with networks include:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:64 +msgid "" +"See the class architecture document (gdal/gnm/gnm_arch.dox) for more " +"details and how this set of classes internally works." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:68 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:107 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:236 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:262 +#: ../../source/development/rfc/rfc87_signed_int8.rst:75 +#: ../../source/development/rfc/rfc93_update_feature.rst:194 +msgid "Bindings" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:70 +msgid "" +"The C API wrapper functions are declared in gdal/gnm/gnm_api.h. All " +"current python bindings are implemented in a swig interface file and use " +"these C functions." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:75 +msgid "Set of applications" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:77 +msgid "" +"It is proposed to include the two following apps which use the GNM into " +"GDAL source tree:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:85 +msgid "" +"See the description of these applications in according documentation for " +"more details." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:91 +msgid "" +"There is already a pull request on github " +"(`https://github.com/OSGeo/gdal/pull/60 " +"<https://github.com/OSGeo/gdal/pull/60>`__) that implements this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:96 +msgid "Building GDAL with GNM support" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:98 +msgid "" +"By default the building of GNM support is disabled. To build GNM support " +"one have to add --with-gnm key to configure or uncomment the appropriate " +"line in nmake.opt." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:103 +msgid "Set of tests" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:105 +msgid "" +"All public methods of GNMNetwork tested in autotest gnm tests. The " +"several tests for GNMGenericNetwork added. The console applications " +"(gnmmanage and gnmanalyse) tested in autotest/utilities." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:109 +msgid "" +"All tests were implemented according to the general rules: they are " +"written on Python and situated in /autotest folder:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:118 +msgid "Documentation structure" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:120 +msgid "" +"All new methods and GNM classes are documented. GDAL documentation is " +"updated when necessary." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:123 +msgid "" +"The following new Doxyfiles in /gnm and /apps directories will be " +"automatically built into the main auto-generated html into the “Related " +"pages” section. All them are similar to OGR docs:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:136 +msgid "Source code tree organization" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:138 +msgid "*What is being added:*" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:140 +msgid "" +"The integration will cause the *addition* of new folders with header, " +"source, make and doc files:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:152 +msgid "*What is being modified:*" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:154 +msgid "The *changing* of the existed GDAL files *will be insignificant*:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:166 +msgid "Future ideas" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:168 +msgid "I see many useful and interesting ways of GNM expending in future:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:170 +msgid "" +"More formats support. The important thing, which must be firstly " +"implemented in future, while the GNM intends to work with as many network" +" formats as possible. It includes not only the support of GNMGdalNetwork " +"formats – i.e. the testing to work with other GDAL spatial formats " +"(currently tested only for Shapefiles and PostGIS). For example:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:177 +msgid "GNMPGRoutingNetwork. Works with pgRouting tables. Some ideas:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:179 +msgid "" +"GNMPGRoutingNetwork::ConnectFeatures() will add to \"source\" and " +"\"target\" columns according values via OGRFeature::setField()" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:181 +msgid "" +"GNMPGRoutingNetwork::AutoConnect() will internally call " +"pgr_createTopology method" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:184 +msgid "" +"GNMSQLiteNetwork. Works with SpatiaLite VirtualNetwork networks. Some " +"ideas:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:187 +msgid "" +"write all network data to the Roads_net_data table and to corresponding " +"NodeFrom and NodeTo columns" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:190 +msgid "GNMGMLNetwork. Works with the GML topology. Some ideas:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:192 +msgid "" +"write network data to the `gml::TopoComplex <gml::TopoComplex>`__, " +"`gml::Node <gml::Node>`__ and `gml::Edge <gml::Edge>`__ directly" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:197 +msgid "" +"More effective algorithm of topology building in GDAL-networks. The " +"current one is implemented as the default for any network format and can " +"connect any amount of line and point layers but is not so efficient – the" +" large networks are being connected too long. GNMGenericNetwork can have " +"more effective default algorithm." +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:203 +msgid "" +"More rules in GDAL-networks, i.e. more complex syntax describing the " +"following:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:206 +msgid "costs extracted from geometrical lengths of lines" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:207 +msgid "turn restriction roles of features" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:208 +msgid "" +"more complex connection rules: set the limit of features can be connected" +" and more complex expressions" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:211 +msgid "" +"Applications. May be one of the most useful application which can be " +"build with GNM is *network2network*, which converts the network and " +"spatial data of the dataset from the one format to another (for example " +"from pgRouting to Oracle Spatial networks);" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:216 +msgid "" +"Analysis. The support of different graph types and the algorithms working" +" with them, for different routing and even engineering purposes. For " +"example:" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:220 +msgid "Boost library" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:221 +msgid "Contraction Hierarchies technology (for large graphs)" +msgstr "" + +#: ../../source/development/rfc/rfc48_geographical_networks_support.rst:226 +msgid "+1 from JukkaR, TamasS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:5 +msgid "RFC 49: Curve geometries" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:9 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:9 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:9 +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:9 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:9 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:9 +msgid "Contact: even dot rouault at spatialys dot com" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:16 +msgid "" +"The current geometry model in GDAL 1.X makes use of points, lines, " +"polygons and aggregations of them (multipoints, multilines, multipolygons" +" and geometry collections). It was modeled from the geometry class " +"hierarchy of the \"OpenGIS Simple Feature Access Part 1 : Common " +"Architecture\" (in its 1.1.0 version)." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:22 +msgid "" +"This RFC covers the addition of new geometry types that have been added " +"in ISO/IEC 13249 Part 3 Spatial (abbreviated as ISO SQL/MM Part 3):" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:25 +msgid "" +"circular string: a circular arc, or a sequence of connected circular " +"arcs, each of them describe by 3 points: the first point of the arc, an " +"intermediate point and the final point" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:28 +msgid "" +"compound curve: a sequence of connected curves, either line strings or " +"circular strings" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:30 +msgid "" +"curve polygon: polygon consisting of one outer ring, and zero or more " +"inner rings. Each ring can be one of the curve implementations: line " +"strings, circular strings, compound curves." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:33 +msgid "" +"multicurve: a collection of curves (line strings, circular strings, " +"compound curves)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:35 +msgid "multisurface: a collection of surfaces (polygons, curve polygons)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:37 +msgid "The scope of this RFC consists in :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:39 +msgid "" +"adding the new geometry classes to the existing geometry class hierarchy," +" with the corresponding importer and exporter of WKT (Well Known Text) " +"and WKB (Well Known Binary) encodings" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:42 +msgid "" +"adding methods to convert those curve geometries into their approximated " +"linear version, and to do the reverse operation" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:44 +msgid "" +"upgrading some of the drivers that can support such geometries : GML (and" +" indirectly NAS, WFS), PostGIS/PGDump, GeoPackage, SQLite, CSV, VRT." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:49 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:36 +msgid "Reference documents" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:51 +msgid "The following documents have been used for the implementation :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:53 +msgid "" +"`Old draft version of ISO/IEC 13249 Part 3 Spatial, dating from " +"2004-05-09 <http://jtc1sc32.org/doc/N1101-1150/32N1107-WD13249-3--" +"spatial.pdf>`__, a.k.a SQL/MM Part 3 : Caution the WKB codes given at " +"page 137 and following are not the latest ones used. Refer to SFA 1.2.1" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:58 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:38 +msgid "" +"`OpenGIS Simple Feature Access Part 1 : Common Architecture,v 1.2.1 " +"<http://portal.opengeospatial.org/files/?artifact_id=25355>`__, a.k.a. " +"SFA 1.2.1" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:62 +msgid "" +"`BNF of WKT encoding <https://github.com/postgis/postgis/blob/svn-" +"trunk/doc/bnf-wkt.txt>`__: extracted from SQL/MM Part 3" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:66 +msgid "" +"`BNF of WKB encoding <https://github.com/postgis/postgis/blob/svn-" +"trunk/doc/bnf-wkb.txt>`__: extracted from SQL/MM Part 3" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:71 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:24 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:22 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:24 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:26 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:49 +msgid "Core changes" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:74 +msgid "New cass hierarchy" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:76 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:51 +msgid "" +"The new class hierarchy is the following and is mostly consistent with " +"SQL/MM Part 3" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:81 +msgid "The only exceptions are :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:83 +msgid "" +"OGRLinearRing: this class present in GDAL 1.X is kept for backward " +"compatibility and also because it is still present in SFA 1.2.1, even if " +"absent from SQL/MM Part 3" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:86 +msgid "" +"OGRSimpleCurve: this abstract class is an implementation detail in OGR " +"that simplifies the implementation of OGRCircularString, by sharing code " +"with what was in OGRLineString only." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:91 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:279 +msgid "Geometry types" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:93 +msgid "" +"The OGRwkbGeometryType enumeration has been extended with the following " +"values :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:113 +msgid "" +"The codes have been taken from SFA 1.2.1, and are consistent with the " +"PostGIS 2 implementation. Note that ISO SQL/MM Part 3 allows alternates " +"values for wkbCircularString (8 or 1000001) : see Table 15 in the above " +"mentioned draft. The values in the range 10000XX probably date back from " +"an earlier draft version. OGR will import them, but will use the values " +"from SFA 1.2.1 when exporting WKB." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:120 +msgid "" +"It has been considered if it would worth to modify the enumeration values" +" of the existing 2.5D geometries (wkbPoint25D, etc...) to conform with " +"the WKB codes of ISO SQL/MM Part 3 / SFA 1.2.1, but there was not a clear" +" advantage in doing so, with respect to the impact on existing users of " +"OGR API." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:126 +msgid "" +"Note: the mix of different ways of expression the Z dimension (wkb25DBit " +"bit for \"old\" geometry types, and +1000 for \"new\" geometry types) has" +" no direct impact on the export of geometries as WKB. There is no direct " +"coupling between the values of OGRwkbGeometryType and what goes to WKB " +"geometries. The exportToWkb() method of OGRGeometry takes a wkbVariant " +"parameter to select the variant of WKB that is wished." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:133 +msgid "" +"The use of the wkb25DBit value (0x8000000) that was sometimes used to " +"test if a geometry type was 3D is now clearly deprecated since it will " +"not work for the new geometry type. The wkbHasZ() and wkbSetZ() have been" +" added to respectively test if a geometry type is 3D, or modify a " +"geometry type to be 3D. The wkb25DBit constant is now disabled for all " +"code in GDAL (but still accessible by user code) and all drivers have " +"been converted to use the new macros." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:141 +msgid "A new family of functions have been used to operate on geometry types :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:189 +msgid "" +"The existing wkbFlatten() is an alias of OGR_GT_Flatten(), the new " +"wkbHasZ() an alias of OGR_GT_HasZ() and wkbSetZ() an alias of " +"OGR_GT_SetZ()." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:196 +msgid "In OGRGeometry class :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:261 +msgid "In OGRGeometryFactory class :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:364 +msgid "Implementation of existing OGRGeometry methods" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:366 +msgid "" +"As GEOS does not support curve geometries for now, all GEOS related " +"operations, the ones returning a boolean value such as Intersects(), or " +"the ones returning a new geometry such as Intersection(), have been " +"adapted so that non-linear geometries are first converted to their linear" +" approximation (this might be revisited if GEOS supports curve geometries" +" in the future) When GEOS returns a geometry, and that one of the input " +"parameters was a non-linear geometry, the reverse operation is done to " +"attempt retrieving as much as possible of the curve geometry. Of course, " +"the result will not generally perfect, but it is better than nothing." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:377 +msgid "Simple example doing the union of 2 half-circles that are contiguous:" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:386 +msgid "" +"Or using GetCurveGeometry() explicitly on the result of a buffer " +"operation:" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:396 +msgid "" +"The Length() operation on OGRCircularString (and thus OGRCompoundCurve) " +"uses circle geometry to compute the exact length, without falling back to" +" linear approximation. The Area() operation on OGRCurvePolygon will " +"generally need to go to linear approximation. When operating on a full " +"circle, or a curve polygon that is convex, an optimization is done to " +"avoid this (by computing the area of the polygon formed with all the " +"vertex including in the circular parts of the description, and adding the" +" area of the `circular segments " +"<http://en.wikipedia.org/wiki/Circular_segment>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:407 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:72 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:159 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:99 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:53 +msgid "C API changes" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:409 +msgid "Deprecation:" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:411 +msgid "" +"wkb25DBit still present, but deprecated since incompatible with the new " +"geometry type. Use the wkbFlatten(), wkbHasZ(), wkbSetZ() macros instead" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:417 +msgid "OGR_GT_xxxx (for Geometry Type): described above" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:418 +msgid "" +"OGRErr OGR_G_ExportToIsoWkb( OGRGeometryH, OGRwkbByteOrder, unsigned " +"char*) : Export geometry as WKB conforming to ISO SQL/MM Part 3." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:420 +msgid "" +"OGRErr OGR_G_ExportToIsoWkt( OGRGeometryH, char \\*\\* ) : Export " +"geometry as WKT conforming to ISO SQL/MM Part 3, i.e. 2.5D geometries " +"names are suffixed by \" Z\", e.g. \"POINT Z (1 2 3)\"." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:423 +msgid "" +"OGRGeometryH OGR_G_Value( OGRGeometryH, double dfDistance ) : mapping of " +"existing OGRGeometry::Value()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:425 +msgid "" +"int OGR_G_HasCurveGeometry( OGRGeometryH, int bLookForNonLinear ) : " +"mapping of OGRGeometry::hasCurveGeometry()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:427 +msgid "" +"OGRGeometryH OGR_G_GetLinearGeometry( OGRGeometryH hGeom, double " +"dfMaxAngleStepSizeDegrees, char*\\* papszOptions) : mapping of " +"OGRGeometry::hasCurveGeometry()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:430 +msgid "" +"OGRGeometryH OGR_G_GetCurveGeometry( OGRGeometryH hGeom, char*\\* " +"papszOptions ) : mapping of OGRGeometry::hasCurveGeometry()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:432 +msgid "" +"void OGRSetNonLinearGeometriesEnabledFlag(int bFlag) : discussed in " +"Backward compatibility section" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:434 +msgid "" +"int OGRGetNonLinearGeometriesEnabledFlag() : discussed in Backward " +"compatibility section" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:440 +msgid "" +"GML geometry importer: Arc, ArcString, ArcByBulge, ArcByCenterPoint, " +"Circle and CircleByCenterPoints GML elements will be returned as circular" +" string OGR geometries. If they are included in other GML elements such " +"as CurveComposite, MultiCurve, Surface, corresponding non-linear OGR " +"geometries will be returned as well. When reading geometries that are " +"made of or consist of Surface, MultiSurface, Curve, MultiCurve, an effort" +" is made to return the OGR geometry class of a linear type as much as " +"possible, i.e. OGRCurvePolygon, OGRCompoundCurve, etc... will only be " +"returned if there's a circular string in the geometry." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:451 +msgid "" +"GML geometry exporter: can generate ArcString and Circle GML elements " +"when passed a geometry with circular string in it." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:454 +msgid "" +"GML driver: Can read/write all the new geometry types. When reading GML3 " +"application schemas, declarations of geometry fields such as " +"CurvePropertyType, SurfacePropertyType, MultiCurvePropertyType or " +"MultiSurfacePropertyType will be also interpreted as being potential non-" +"linear geometries, and corresponding OGR geometry type will be used for " +"the layer geometry type, and the geometries of the feature will also " +"follow that layer geometry type. This can affect the WFS drivers." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:463 +msgid "" +"NAS driver: Can return the new geometry types. NAS layers will use the " +"new geometry types only if the NAS file contains arcs." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:466 +msgid "" +"PG/PostGIS: Can read/write all the new geometry types for both PostGIS " +"2.X and PostGIS 1.X. For PostGIS 1.X compatibility, special processing " +"must be done in the importFromWkb()/exportToWkb() to deal with the non " +"standard codes used by PostGIS 1.X for curvepolygon, multicurve and " +"multisurface. This is done with a wkbVariantPostGIS1 value added to " +"OGRwkbVariant enumeration used by those methods." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:473 +msgid "" +"PGDump: Can write all new geometry types. Above remark related to the " +"differences among version make it important to specify correctly the " +"POSTGIS_VERSION dataset creation option." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:477 +msgid "" +"GeoPackage: Can read/write all the new geometry types. Note: this isn't " +"in the core of the GeoPackage specification, but it is still a registered" +" extension." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:481 +msgid "" +"SQLite: Can read/write all the new geometry types for databases that are " +"NOT Spatialite databases, since Spatialite does no support curve geometry" +" types. However an attempt (well a hack) is done so that the SQLite SQL " +"dialect can still be used. Basically when converting a OGR geometry to " +"Spatialite, if it is of one of the curve geometry type, the resulting " +"blob will first contain the spatialite compatible blob of the linear " +"geometry, and afterwards the WKB of the curve geometry. Spatialite " +"functions, if called with a ST\\_ function for example, will ignore the " +"later one. When reading a blob from sqlite, if the added WKB of the curve" +" geometry is still there, it will be used. Otherwise the spatialite " +"geometry blob will be used. So SELECT statement just selecting the " +"geometry column without doing any operation on it should preserve curve " +"geometries." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:495 +msgid "MEM: Can read/write all the new geometry types." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:497 +msgid "CSV: Can read/write all the new geometry types." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:499 +msgid "" +"VRT: Declared as compatible with all the new geometry types. Actual " +"capability will depend on the underlying layers wrapped by the VRT." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:505 +msgid "" +"ogr2ogr: the new geometry names (CIRCULARSTRING, etc...) are supported in" +" the -nlt option. \"-nlt CONVERT_TO_LINEAR\" can also be used to ask " +"curve geometries to be converted into their linear approximation ( what " +"is used to do that is forceTo(xxx, OGR_GT_GetLinear()) ). Note: this " +"isn't strictly necessary as all drivers should be able to deal with the " +"non-linear geometry types with the compatibility mechanism described in " +"Backward compatibility. But this might be useful to produce a PostGIS " +"table or GeoPackage database with linear geometry types even if the " +"source contains non-linear geometries. \"-nlt CONVERT_TO_LINEAR\" can be " +"combined with \"-nlt PROMOTE_TO_MULTI\"." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:520 +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:138 +msgid "Addition of :" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:522 +msgid "the new geometry types as ogr.wkbXXXXX" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:523 +msgid "ogr.ForceTo()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:524 +msgid "Geometry.ExportToIsoWkt()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:525 +msgid "Geometry.ExportToIsoWkb()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:526 +msgid "Geometry.HasCurveGeometry(int bLookForCircular = FALSE)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:527 +msgid "" +"Geometry.GetLinearGeometry(double dfMaxAngleStepSizeDegrees = " +"0.0,char*\\* options = NULL)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:529 +msgid "Geometry.GetCurveGeometry(char*\\* options = NULL)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:530 +msgid "ogr.SetNonLinearGeometriesEnabledFlag(int bFlag)" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:531 +msgid "ogr.GetNonLinearGeometriesEnabledFlag()" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:532 +msgid "ogr.GT_xxxxx functions" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:534 +msgid "Using ogr.wkb25DBit will issue a deprecation warning" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:537 +msgid "Related changes that are *NOT* included in this RFC" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:539 +msgid "" +"Support for other ISO SQL/MM geometries such as Polyhedral Surface, " +"Triangulated Irregular Network (TIN), Triangle." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:541 +msgid "Support for the M (Measure) dimension of geometries." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:542 +msgid "" +"Upgrade of other drivers that could make use of curve geometries : MSSQL " +"Spatial, Oracle Spatial, DXF, DWG, ..." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:544 +msgid "" +"Support for arbitrary new geometry types: Conceptually one could hope " +"that a new class extending OGRCurve (Bezier or Spline curve) for example " +"could be added without touching OGR core. This isn't currently possible: " +"changes in OGRGeometryFactory and the OGR_GT\\_ functions would be needed" +" to remove a few hardcoded assumptions." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:554 +msgid "Regarding code using GDAL" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:556 +msgid "" +"Many applications will not be able to properly deal with the new geometry" +" types that may now be returned by some drivers. If they don't want to " +"test the geometry type and explicitly calling the conversion function, " +"they can call OGRSetNonLinearGeometriesEnabledFlag(FALSE) (the default " +"value is TRUE, i.e. non-linear geometries can be returned). In which " +"case, they will be transformed into their closest linear geometry, by " +"doing linear approximation, with OGR_G_ForceTo()." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:564 +msgid "" +"This flag has only an effect on the OGR_F_GetGeometryRef(), " +"OGR_F_GetGeomFieldRef(), OGR_L_GetGeomType(), OGR_GFld_GetType() and " +"OGR_FD_GetGeomType() C API, and corresponding methods in the SWIG " +"bindings." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:569 +msgid "" +"Libraries should generally *not* use that method, since that could " +"interfere with other libraries or applications." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:572 +msgid "" +"Note that it does *not* affect the behavior of the C++ API. It has been " +"deemed dangerous/complicated to try doing that at the C++ level as it " +"could confuse drivers since they might call GetGeomType() for example." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:577 +msgid "Regarding OGR drivers" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:579 +msgid "" +"Drivers that can deal with the new geometry types SHOULD declare the new " +"dataset level ODsCCurveGeometries AND layer level OLCCurveGeometries " +"capabilities. The virtual methods CreateFeature() and SetFeature() " +"implemented by drivers have been renamed ICreateFeature() and " +"ISetFeature(). OGRLayer has now a non-virtual CreateFeature() and " +"SetFeature() that checks if the layer has curve geometry capability. If " +"it has not, and that the passed feature has non-linear geometries, they " +"will be transparently converted to their linear approximation before " +"calling the driver ICreateFeature()/ISetFeature() method. Similarly the " +"CreateLayer() method at datasource level will convert the passed geometry" +" type to a non-linear corresponding type if necessary." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:591 +msgid "" +"All in-tree drivers have been converted to switch from CreateFeature() to" +" ICreateFeature() and SetFeature() to ISetFeature(). Out-of-tree drivers " +"will have to be adapted similarly otherwise those methods will fails (the" +" now non-virtual methods in OGRLayer class will try to create the default" +" implementation of the same class, which will fail)." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:600 +msgid "" +"All new methods and OGR geometry classes are documented. Driver " +"documentation is updated when necessary. MIGRATION_GUIDE.TXT is updated " +"with a summary of the text of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:607 +msgid "" +"Very few changes have been made so that the existing autotest suite still" +" passes. Very comprehensive testing of new geometry classes and " +"conversion methods has been added to ogr_geom.py and ogr_gml_geom.py. " +"Updated drivers have received new tests also." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:615 +msgid "" +"Implementation will be done by Even Rouault. Coordinated with Sourcepole " +"(see `QGIS Enhancement 8: Geometry redesign <https://github.com/mhugent" +"/QGIS-Enhancement-Proposals/blob/master/QEP-8-geometry_redesign.rst>`__)," +" sponsored by Swiss QGIS User Group." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:620 +msgid "" +"The proposed implementation lies in the \"curve_geometries\" branch of " +"the `https://github.com/rouault/gdal2/tree/curve_geometries " +"<https://github.com/rouault/gdal2/tree/curve_geometries>`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:624 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/curve_geometries " +"<https://github.com/rouault/gdal2/compare/curve_geometries>`__" +msgstr "" + +#: ../../source/development/rfc/rfc49_curve_geometries.rst:630 +msgid "+1 from TamasS, JukkaR and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:5 +msgid "RFC 4: Geolocation Arrays" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:16 +msgid "" +"It is proposed that GDAL support an additional mechanism for geolocation " +"of imagery based on large arrays of points associating pixels and lines " +"with geolocation coordinates. These arrays would be represented as raster" +" bands themselves." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:21 +msgid "" +"It is common in AVHRR, Envisat, HDF and netCDF data products to " +"distribute geolocation for raw or projected data in this manner, and " +"current approaches to representing this as very large numbers of GCPs, or" +" greatly subsampling the geolocation information to provide more " +"reasonable numbers of GCPs are inadequate for many applications." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:28 +msgid "Geolocation Domain Metadata" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:30 +msgid "" +"Datasets with geolocation information will include the following dataset " +"level metadata items in the \"GEOLOCATION\" domain to identify the " +"geolocation arrays, and the details of the coordinate system and " +"relationship back to the original pixels and lines." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:35 +msgid "SRS: wkt encoding of spatial reference system." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:36 +msgid "X_DATASET: dataset name (defaults to same dataset if not specified)" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:37 +msgid "X_BAND: band number within X_DATASET." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:38 +msgid "Y_DATASET: dataset name (defaults to same dataset if not specified)" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:39 +msgid "Y_BAND: band number within Y_DATASET." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:40 +msgid "Z_DATASET: dataset name (defaults to same dataset if not specified)" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:41 +msgid "Z_BAND: band number within Z_DATASET. (optional)" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:42 +msgid "PIXEL_OFFSET: pixel offset into geo-located data of left geolocation pixel" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:44 +msgid "LINE_OFFSET: line offset into geo-located data of top geolocation pixel" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:46 +msgid "PIXEL_STEP: each geolocation pixel represents this many geolocated pixels." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:48 +msgid "LINE_STEP: each geolocation pixel represents this many geolocated lines." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:50 +msgid "" +"GEOREFERENCING_CONVENTION: (added in GDAL 3.5) either TOP_LEFT_CORNER to " +"indicate that the X/Y values refer to the top-left corner of the pixel, " +"or PIXEL_CENTER to indicate that they refer to the center of the pixel. " +"The default is TOP_LEFT_CORNER." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:55 +msgid "" +"In the common case where two of the bands of a dataset are actually " +"latitude and longitude, and so the geolocation arrays are the same size " +"as the base image, the metadata might look like:" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:69 +msgid "" +"For AVHRR datasets, there are only 11 points (note, the more recent NOAA " +"AVHRR datasets have 51 points), but for every line. So the result for a " +"LAC dataset might look like:" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:85 +msgid "" +"This assumes the L1B driver is modified to support the special access to " +"GCPs as bands using the L1BGCPS: prefix." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:89 +msgid "Updating Drivers" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:91 +msgid "" +"HDF4: Client needs mandate immediate incorporation of geolocation array " +"support in the HDF4 driver (specifically for swath products). (complete)" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:94 +msgid "" +"HDF5: Some HDF5 products include geolocation information that should be " +"handled as arrays. No timetable for update." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:96 +msgid "" +"AVHRR: Has 11/51 known locations per-scanline. These are currently " +"substantially downsampled and returned as GCPs, but this format would be " +"an excellent candidate for treating as geolocation arrays. Planned in " +"near future." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:100 +msgid "" +"Envisat: Envisat raw products use geolocation information currently " +"subsampled as GCPs, good candidate for upgrade. No timetable for update." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:103 +msgid "" +"netCDF: NetCDF files can have differently varying maps in x and y " +"directions, which are represented as geolocation arrays when they are " +"encoded as CF conventions \"two-dimensional coordinate variables\". See " +"the netcdf driver page for details." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:107 +msgid "" +"OPeNDAP: Can have differently varying maps in x and y directions which " +"could be represented as geolocation arrays when they are irregular. No " +"timetable for update." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:112 +msgid "Changes to Warp API and gdalwarp" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:114 +msgid "" +"Introduce a new geolocation array based transformation method, following " +"the existing GDALTransformer mechanism. A geolocation array transformer " +"will be created with the following function call. The \"char \\**\" array" +" is the list of metadata from the GEOLOCATION metadata domain." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:125 +msgid "" +"This transformer is currently partially implemented, but in a manner that" +" potentially uses a great deal of memory (twice the memory needed for the" +" geolocation arrays), and with still dubious correctness, but once " +"approved this will be fixup up to at least be correct, though likely not " +"efficient for the time being." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:131 +msgid "" +"The GDALGenImgProjTransformer will be upgraded to instantiate the GeoLoc " +"transformer (instead of an affine, gcp, or rpc transformer) if only " +"geolocation information is available (done). However, the current " +"GDALCreateGenImgProjTransformer() function does not provide a mechanism " +"to select which transformation mechanism is used. So, for instance, if an" +" affine transform is available it will be used in preference to " +"geolocation data. If bGCPUseOK is TRUE, gcps will be used in preference " +"to geolocation data." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:140 +msgid "" +"The gdalwarp program currently always sets bGCPUseOK to TRUE so there is " +"no means for gdalwarp users select use of geolocation data in preference " +"to gcps. Some modification to gdalwarp may be needed in the future in " +"this regard." +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:150 +msgid "" +"''How do we preserve access to geolocation information when translating a" +" dataset? Do applications like gdal_translate need special handling?" +msgstr "" + +#: ../../source/development/rfc/rfc4_geolocate.rst:152 +msgid "" +"Placement of the geolocation data in a special metadata domain means it " +"won't be transferred in default translations.''" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:5 +msgid "RFC 50: OGR field subtypes" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:16 +msgid "" +"This RFC aims at adding the capability of specifying sub-types to OGR " +"fields, like boolean, 16 bit integers or 32 bit floating point values. " +"The sub-type of a field definition is an additional attribute that " +"specifies a hint or a restriction to the main type. The subtype can be " +"used by applications and drivers that know how to handle it, and can " +"generally be safely ignored by applications and drivers that do not." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:27 +msgid "Field subtypes" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:29 +msgid "The OGRFieldSubType enumeration is added :" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:55 +msgid "New attributes and methods" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:57 +msgid "In OGRFieldDefn class :" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:67 +msgid "" +"OGRFeature::SetField() will check that the passed value is in the " +"accepted range for boolean and int16 subtypes. If not, it will emit a " +"warning and correct/clamp the value to fit the subtype." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:74 +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:161 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:101 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:55 +msgid "Only additions :" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:85 +msgid "Changes in OGR SQL" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:87 +msgid "" +"Subtypes are preserved when a field name (or \\*) is specified in the " +"list of fields of a SELECT" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:89 +msgid "CAST(xxx AS BOOLEAN) and CAST(xxx AS SMALLINT) are now supported." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:90 +msgid "" +"The field list of a SELECT can now accept boolean expressions, such as " +"\"SELECT x IS NULL, x >= 5 FROM foo\"" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:92 +msgid "" +"The WHERE clause of a SELECT can now accept boolean fields, such as " +"\"SELECT \\* FROM foo WHERE a_boolean_field\"" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:98 +msgid "GeoJSON: can read/write OFSTBoolean" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:99 +msgid "GML: can read/write OFSTBoolean, OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:100 +msgid "" +"CSV: can read/write OFSTBoolean (explicitly with CSVT or with " +"autodetection), OFSTInt16 and OFSTFloat32 (explicitly with CSVT)" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:102 +msgid "PG: can read/write OFSTBoolean, OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:103 +msgid "PGDump: can write OFSTBoolean, OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:104 +msgid "GeoPackage: can read/write OFSTBoolean, OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:105 +msgid "SQLite: can read/write OFSTBoolean and OFSTInt16" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:106 +msgid "SQLite dialect: can read/write OFSTBoolean, OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:107 +msgid "FileGDB: can read/write OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:108 +msgid "OpenFileGDB: can read OFSTInt16 and OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:109 +msgid "VRT: 'subtype' property added to be able to handle any subtype." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:114 +msgid "" +"ogrinfo: the output of ogrinfo is slightly modified in presence of a " +"subtype. A field with a non-default subtype will be described as " +"\"field_type(field_subtype)\". For example" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:140 +msgid "ogr.OFSTNone, ogr.OFSTBoolean, ogr.OFSTInt16 and ogr.OFSTFloat32" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:141 +msgid "ogr.GetFieldSubTypeName()" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:142 +msgid "FieldDefn.GetSubType()" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:143 +msgid "FieldDefn.SetSubType()" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:148 +msgid "" +"This should have no impact on read-only operations done by applications. " +"Update operations could be impacted if an out-of-range value for the " +"subtype is written (but such a behavior probably already caused issues, " +"either ignored or notified by the backend)" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:156 +msgid "" +"All new methods are documented. Driver documentation is updated when " +"necessary." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:162 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:161 +msgid "The various aspects of this RFC are tested:" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:164 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:163 +msgid "core changes" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:165 +msgid "OGR SQL changes" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:166 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:164 +msgid "driver changes" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:171 +msgid "" +"Implementation will be done by Even Rouault (`Spatialys " +"<http://spatialys.com>`__), and sponsored by `CartoDB " +"<https://cartodb.com>`__." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:175 +msgid "" +"The proposed implementation lies in the \"ogr_field_subtype\" branch of " +"the `https://github.com/rouault/gdal2/tree/ogr_field_subtype " +"<https://github.com/rouault/gdal2/tree/ogr_field_subtype>`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:180 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/ogr_field_subtype " +"<https://github.com/rouault/gdal2/compare/ogr_field_subtype>`__" +msgstr "" + +#: ../../source/development/rfc/rfc50_ogr_field_subtype.rst:186 +msgid "+1 JukkaR, TamasS, FrankW and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:5 +msgid "RFC 51: RasterIO() improvements : resampling and progress callback" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:16 +msgid "" +"This RFC aims at extending the RasterIO() API to allow specifying a " +"resampling algorithm when doing requests involving subsampling or " +"oversampling. A progress callback can also be specified to be notified of" +" progression and allow the user to interrupt the operation." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:25 +msgid "Addition of GDALRasterIOExtraArg structure" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:27 +msgid "A new structure GDALRasterIOExtraArg is added to contain the new options." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:75 +msgid "" +"There are several reasons to prefer a structure rather than new " +"parameters to the RasterIO() methods :" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:78 +msgid "code readability (GDALDataset::IRasterIO() has already 14 parameters...)" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:80 +msgid "allow future extensions without changing the prototype in all drivers" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:81 +msgid "" +"to a lesser extent, efficiency: it is common for RasterIO() calls to be " +"chained between generic/specific and/or dataset/rasterband " +"implementations. Passing just the pointer is more efficient." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:85 +msgid "" +"The structure is versioned. In the future if further options are added, " +"the new members will be added at the end of the structure and the version" +" number will be incremented. Code in GDAL core&drivers can check the " +"version number to determine which options are available." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:91 +msgid "Addition of GDALRIOResampleAlg structure" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:93 +msgid "The following resampling algorithms are available :" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:113 +msgid "" +"Those new resampling methods can be used by the " +"GDALRasterBand::IRasterIO() default implementation when the size of the " +"buffer (nBufXSize x nBufYSize) is different from the size of the area of " +"interest (nXSize x nYSize). The code heavily relies on the algorithms " +"used for overview computation, with adjustments to be also able to deal " +"with oversampling. Bilinear, CubicSpline and Lanczos are now available in" +" overview computation as well, and rely on the generic infrastructure for" +" convolution computation introduced lately for improved cubic overviews. " +"Some algorithms are not available on raster bands with color palette. A " +"warning will be emitted if an attempt of doing so is done, and nearest " +"neighbour will be used as a fallback." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:125 +msgid "" +"The GDAL_RASTERIO_RESAMPLING configuration option can be set as an " +"alternate way of specifying the resampling algorithm. Mainly useful for " +"tests with applications that do not yet use the new API." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:129 +msgid "" +"Currently, the new resampling methods are only available for GF_Read " +"operations. The use case for GF_Write operations isn't obvious, but could" +" be added without API changes if needed." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:134 +msgid "C++ changes" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:136 +msgid "" +"GDALDataset and GDALRasterBand (non virtual) RasterIO() and (virtual) " +"IRasterIO() methods have a new final argument psExtraArg of type " +"GDALRasterIOExtraArg*. This extra argument defaults to NULL for code " +"using GDAL, but is required for all in-tree code, so as to avoid that in-" +"tree code forgets to forwards psExtraArg it might have returned from a " +"caller." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:143 +msgid "" +"GDALDataset::RasterIO() and GDALRasterBand::RasterIO() can accept a NULL " +"pointer for that argument in which case they will instantiate a default " +"GDALRasterIOExtraArg structure to be passed to IRasterIO(). Any other " +"code that calls IRasterIO() directly (a few IReadBlock() implementations)" +" should make sure of doing so, so that IRasterIO() can assume that its " +"psExtraArg is not NULL." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:150 +msgid "" +"As a provision to be able to deal with very large requests with buffers " +"larger than several gigabytes, the nPixelSpace, nLineSpace and nBandSpace" +" parameters have been promoted from the int datatype to the new GSpacing " +"datatype, which is an alias of a signed 64 bit integer." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:155 +msgid "" +"GDALRasterBand::IRasterIO() and GDALDataset::BlockBasedRasterIO() now use" +" the progress callback when available." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:180 +msgid "" +"Those are the same as the existing functions with a final " +"GDALRasterIOExtraArg\\* psExtraArg argument, and the spacing parameters " +"promoted to GSpacing." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:187 +msgid "" +"All in-tree drivers that implemented or used RasterIO have been edited to" +" accept the GDALRasterIOExtraArg\\* psExtraArg parameter, and forward it " +"when needed. Those who had a custom RasterIO() implementation now use the" +" progress callback when available." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:191 +msgid "" +"VRT: the and elements can accept a 'resampling' attribute. The VRT driver" +" will also set the dfXOff, dfYOff, dfXSize and dfYSize fields of " +"GDALRasterIOExtraArg\\* to have source sub-pixel accuracy, so that " +"GDALRasterBand::IRasterIO() leads to consistent results when operating on" +" a small area of interest or the whole raster. If that was not done, " +"chunking done in GDALDatasetCopyWholeRaster() or other algorithms could " +"lead to repeated lines due to integer rounding issues." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:203 +msgid "" +"gdal_translate: accept a -r parameter to specify the resampling " +"algorithm. Defaults to NEAR. Can be set to bilinear, cubic, cubicspline, " +"lanczos, average or mode. (Under the hood, this sets the new resampling " +"property at the VRT source level.)" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:207 +msgid "" +"gdaladdo: -r parameter now accepts bilinear, cubicspline and lanczos as " +"additional algorithms to the existing ones." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:213 +msgid "" +"For Python and Perl bindings: Band.ReadRaster(), Dataset.ReadRaster() now" +" accept optional resample_alg, callback and callback_data arguments. " +"(untested for Perl, but the existing tests pass)" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:216 +msgid "" +"For Python bindings, Band.ReadAsArray() and Dataset.ReadAsArray() now " +"accept optional resample_alg, callback and callback_data arguments." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:222 +msgid "C API/ABI preserved." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:224 +msgid "" +"C++ users of the GDALRasterBand::RasterIO() and GDALDataset::RasterIO() " +"API do not need to change their code, since the new " +"GDALRasterIOExtraArg\\* psExtraArg argument is optional for out-of-tree " +"code." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:229 +msgid "" +"Out-of-tree drivers that implement IRasterIO() must be changed to accept " +"the new GDALRasterIOExtraArg\\* psExtraArg argument. Note: failing to do " +"so will be undetected at compile time (due to how C++ virtual method " +"overloading work)." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:234 +msgid "Both issues will be mentioned in MIGRATION_GUIDE.TXT" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:239 +msgid "All new methods are documented." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:244 +msgid "The various aspects of this RFC are tested in the Python bindings:" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:246 +msgid "" +"use of the new options of Band.ReadRaster(), Dataset.ReadRaster(), " +"Band.ReadAsArray() and Dataset.ReadAsArray()." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:248 +msgid "resampling algorithms in subsampling and oversampling RasterIO() requests." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:250 +msgid "\"-r\" option of gdal_translate" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:255 +msgid "" +"Implementation will be done by Even Rouault (`Spatialys " +"<http://spatialys.com>`__), and sponsored by `R3 GIS " +"<http://r3-gis.com>`__." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:259 +msgid "" +"The proposed implementation lies in the \"rasterio\" branch of the " +"`https://github.com/rouault/gdal2/tree/rasterio " +"<https://github.com/rouault/gdal2/tree/rasterio>`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:263 +msgid "" +"The list of changes : `https://github.com/rouault/gdal2/compare/rasterio " +"<https://github.com/rouault/gdal2/compare/rasterio>`__" +msgstr "" + +#: ../../source/development/rfc/rfc51_rasterio_resampling_progress.rst:269 +msgid "+1 from FrankW, JukkaR, HowardB, DanielM, TamasS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:5 +msgid "RFC 52: Strict OGR SQL quoting" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:11 +msgid "Status: adopted, implemented in GDAL 2.0" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:16 +msgid "" +"This RFC proposes that OGR SQL enforces strict quoting rules for SQL " +"literals and identifiers" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:22 +msgid "" +"Currently the OGR SQL engine deals indifferently with single quote " +"characters (') and double quote characters (\"), although they can be " +"used in 2 different contexts :" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:26 +msgid "to specify string literals" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:27 +msgid "to specify column or table names (when they need quoting)" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:29 +msgid "" +"SQL 92 mandates that string literals are surrounded with single quote " +"characters whereas quoted identifiers (column, table names) are " +"surrounded with double quote characters." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:33 +msgid "" +"From `http://savage.net.au/SQL/sql-92.bnf.html " +"<http://savage.net.au/SQL/sql-92.bnf.html>`__:" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:41 +msgid "" +"Current OGR behavior is generally fine, except in some situations when " +"specifying columns in a SELECT statement or in a WHERE expression. The " +"OGR SQL engine tries to determine the intent with the following rule : if" +" the quoted string matches a column name, then it is assumed to be a " +"column identifier, otherwise a string literal. But sometimes (see " +"`http://trac.osgeo.org/gdal/ticket/5428 " +"<http://trac.osgeo.org/gdal/ticket/5428>`__), there are situations where " +"filters such as \"MyField\" = 'MYFIELD' are needed, and currently they " +"always evaluate to TRUE." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:50 +msgid "" +"To avoid any ambiguities and more conformant to SQL, string literals " +"should be single-quoted, and identifiers (column/table names) unquoted or" +" surrounded by double-quote character if conflicting with reserved " +"keywords." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:58 +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:169 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:135 +msgid "" +"Implementation will be done by Even Rouault (`Spatialys " +"<http://spatialys.com>`__)." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:61 +msgid "" +"The proposed implementation lies in the \"rfc52_stricter_sql\" branch of " +"the `https://github.com/rouault/gdal2/tree/rfc52_stricter_sql " +"<https://github.com/rouault/gdal2/tree/rfc52_stricter_sql>`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:66 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/rfc52_stricter_sql " +"<https://github.com/rouault/gdal2/compare/rfc52_stricter_sql>`__" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:72 +msgid "" +"This change affects compatibility in the sense that users that relied on " +"the current permissive behavior will have to adapt their SQL expressions." +" This might be quite tricky to detect as it will not always cause obvious" +" runtime failures. For example \" SELECT " +"'i_thought_this_would_be_interpreted_as_a_column_name_but_now_it_is_a_string_litteral'" +" FROM atable \" will run without error but not produce the previously " +"expected result. So applications will have to review how they build SQL " +"filters ( SetAttributeFilter() ) and expressions ( ExecuteSQL() )" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:81 +msgid "" +"Expressions fixed to be compliant with stricter rules will also work with" +" older GDAL versions." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:84 +msgid "" +"A prominent warning should also be put on the OGR SQL documentation page " +"to advertise the change of behavior" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:88 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:201 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:251 +msgid "Discussion" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:90 +msgid "" +"Tests done with SQLite show that it is sometimes tolerant to misuse of " +"quote characters, but in the reverse way as current OGR. So it will " +"accept SELECT \"non_existing_column\" FROM 'atable' and interpret it as " +"SELECT 'non_existing_column' FROM \"atable\". On the contrary, PostgreSQL" +" will not accept it. I'd be rather inclined to follow PostgreSQL stricter" +" approach to keep things simple and understandable: \"string literals " +"should be single-quoted, and identifiers (column/table names) unquoted or" +" surrounded by double-quote character\"" +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:102 +msgid "The Python autotest suite will be fixed to still pass." +msgstr "" + +#: ../../source/development/rfc/rfc52_strict_sql_quoting.rst:107 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:131 +msgid "+1 from JukkaR, TamasS, DanielM and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:5 +msgid "RFC 53: OGR not-null constraints and default values" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:16 +msgid "" +"This RFC addresses handling of NOT NULL constraints and DEFAULT values " +"for OGR fields. NOT NULL constraints are useful to maintain basic data " +"integrity and are handled by most (all?) drivers that have SQL " +"capabilities. Default fields values may be used complementary or " +"independently of NOT NULL constraints to specify the value a field must " +"be assigned to if it is not provided when inserting a feature into the " +"layer." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:25 +msgid "NOT NULL constraint" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:27 +msgid "" +"Up to now, OGR fields did not have NOT NULL constraints, i.e. fields in " +"layers/tables were created with the possibility for a field of a " +"feature/record to be unset (i.e. having a NULL value). This will still be" +" the default, i.e. fields are assumed to be nullable. The OGRFieldDefn " +"class is extended with a boolean attribute bNullable that defaults to " +"TRUE and can be set to FALSE to express a NOT NULL constraint (bNullable " +"has been preferred over bNotNullable to avoid confusion with double " +"negation). Drivers that can translate NOT NULL constraints in their " +"storage will use that attribute to determine if the field definition must" +" include a NOT NULL constraint. When opening a datasource, their metadata" +" will be inspected to set the nullable attribute properly, so that round-" +"tripping works." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:40 +msgid "The following methods are added to the OGRFieldDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:79 +msgid "" +"As this holds true for geometry fields, those 2 methods are also add to " +"the OGRGeometryFieldDefn class." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:82 +msgid "" +"Note that adding a field with a NOT NULL constraint on a non-empty layer " +"is generally impossible, unless a DEFAULT value is associated with it." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:85 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:292 +msgid "The following method is added to the OGRFeature class :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:111 +msgid "where nValidateFlags is a combination of :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:148 +msgid "" +"Validation of NOT NULL constraints is generally let to the driver low-" +"level layer, so OGRFeature::Validate() is only useful on a few cases (one" +" of such case is the GML driver)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:152 +msgid "" +"A new flag ALTER_NULLABLE_FLAG = 0x8 is added to be passed to " +"OGRLayer::AlterFieldDefn() so as to set or drop NULL / NOT-NULL " +"constraints (for drivers that implement it)." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:156 +msgid "" +"Drivers that handle NOT NULL constraint for regular attribute fields " +"should advertise the new GDAL_DCAP_NOTNULL_FIELDS and/or " +"GDAL_DCAP_NOTNULL_GEOMFIELDS driver metadata items." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:160 +msgid "" +"Drivers that do not implement the OGRLayer::CreateGeomField() interface " +"(i.e. the ones that support single geometry field), but can create a " +"layer with a NOT NULL constraint on the geometry field can expose a " +"GEOMETRY_NULLABLE=YES/NO layer creation option." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:165 +msgid "" +"Note: due to the way they are commonly written, the CreateField() " +"implementations of drivers that do not support NOT NULL constraint will " +"generally copy the value of the nullable flag, which may be a bit " +"misleading if querying the field definition just after having adding it " +"(the same holds true for width/precision as well)." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:171 +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:328 +msgid "All above methods are mapped into the C API :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:184 +msgid "Default field values" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:186 +msgid "" +"Fields with NOT NULL constraints are sometimes accompanied with a DEFAULT" +" clause so as to be able to create a new feature without filling all " +"fields, while maintaining integrity. DEFAULT values can also be set on " +"nullable fields but for reasons exposed later it is recommended to avoid " +"that." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:192 +msgid "" +"Drivers that can translate DEFAULT values in their storage will use that " +"attribute to determine if the field definition must include a DEFAULT " +"value. When opening a datasource, their metadata will be inspected to set" +" the default value attribute properly, so that round-tripping works." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:197 +msgid "" +"There was an embryonic support for default values in GDAL 1.X but that " +"never got implemented beyond the getter/setter methods on OGRFieldDefn. " +"It relied on a \"OGRField uDefault\" member. The choice of OGRField " +"restricts the default values to be expressed with the type of the field, " +"but in some situations we want to be able to assign expressions or " +"special keywords for non-string fields. For example the SQL standard " +"defines CURRENT_TIMESTAMP for DateTime fields. So as to be general, we " +"have remove this uDefault member and replaced it with a \"char\\* " +"pszDefault\" string." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:207 +msgid "The values that can be set as default values are :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:209 +msgid "" +"literal string values enclosed in single-quote characters and properly " +"escaped like: ``'Nice weather. Isn''t it ?'``" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:211 +msgid "numeric values (unquoted)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:212 +msgid "" +"reserved keywords (unquoted): CURRENT_TIMESTAMP, CURRENT_DATE, " +"CURRENT_TIME, NULL" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:214 +msgid "" +"datetime literal values enclosed in single-quote characters with the " +"following defined format: 'YYYY/MM/DD HH:MM:SS[.sss]'" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:216 +#, python-format +msgid "" +"any other driver specific expression. e.g. for SQLite: " +"(strftime('%Y-%m-%dT%H:%M:%fZ','now'))" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:219 +msgid "The following methods are added/modified to the OGRFieldDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:281 +msgid "" +"SetDefault() validates that a string literal beginning with ' is properly" +" escaped." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:284 +msgid "" +"IsDefaultDriverSpecific() returns TRUE if the value set does not belong " +"to one of the 4 bullets in the above enumeration. This is used by drivers" +" to determine if they can handle or not a default value." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:288 +msgid "" +"Drivers should do some effort to interpret and reformat default values in" +" the above 4 standard formats so as to be able to propagate default " +"values from one driver to another one." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:309 +msgid "" +"It will replace unset fields of a feature with their default values, but " +"should rarely be used as most drivers will do that substitution " +"automatically in their low-level layer. CreateFeature() cannot be trusted" +" to automatically modify the passed OGRFeature object to set unset fields" +" to their default values. For that, an explicit GetFeature() call should " +"be issued to retrieve the record as stored in the database." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:316 +msgid "" +"A new flag ALTER_DEFAULT_FLAG = 0x8 is added to be passed to " +"OGRLayer::AlterFieldDefn() so as to set, drop or modify default values " +"(for drivers that implement it)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:320 +msgid "" +"Drivers that handle default values should advertise the new " +"GDAL_DCAP_DEFAULT_FIELDS driver metadata items." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:323 +msgid "" +"Note: due to the way they are commonly written, the CreateField() " +"implementations of drivers that do not support default values will " +"generally copy the value of the default value string, which may be a bit " +"misleading if querying the field definition just after having adding it." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:341 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:518 +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:55 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:74 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:156 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:64 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:204 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:293 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:59 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:214 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:111 +msgid "SWIG bindings (Python / Java / C# / Perl) changes" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:343 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:520 +msgid "The following additions have been done :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:345 +msgid "SetNullable(), IsNullable() added on FieldDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:346 +msgid "SetNullable(), IsNullable() added on GeomFieldDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:347 +msgid "Validate() added on Feature class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:348 +msgid "" +"SetDefault(), GetDefault(), IsDefaultDriverSpecific() available on " +"FieldDefn class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:350 +msgid "FillUnsetWithDefault() added on Feature class" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:355 +msgid "" +"ogrinfo has been updated to expose NOT NULL constraints and DEFAULT " +"values. e.g." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:370 +msgid "2 news options have been added to ogr2ogr :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:372 +msgid "" +"-forceNullable to remove NOT NULL constraint (NOT NULL constraints are " +"propagated by default from source to target layer)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:374 +msgid "" +"-unsetDefault to remove DEFAULT values (DEFAULT values are propagated by " +"default from source to target layer)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:377 +msgid "" +"Unless it is explicitly specified, ogr2ogr will also automatically set " +"the GEOMETRY_NULLABLE=NO creation option to target layers that support " +"it, if the source layer has its first geometry field with a NOT NULL " +"constraint." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:385 +msgid "New/modified API are documented." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:390 +msgid "The following OGR drivers have been updated to support the new interfaces." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:393 +msgid "" +"PG: supports NOT NULL (for attribute and multiple geometry fields) and " +"DEFAULT on creation/read. AlterFieldDefn() implementation modified to " +"support ALTER_NULLABLE_FLAG and ALTER_DEFAULT_FLAG." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:396 +msgid "" +"PGDump: supports NOT NULL (for attribute and multiple geometry fields) " +"and DEFAULT on creation." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:398 +msgid "" +"CartoDB: supports NOT NULL (for attribute and single geometry fields) and" +" DEFAULT on creation. Supported also on read with authenticated login " +"only (relies on queries on PostgreSQL system tables)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:401 +msgid "" +"GPKG: supports NOT NULL (for attribute and its single geometry field) and" +" DEFAULT on creation/read. GEOMETRY_NULLABLE layer creation added." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:403 +msgid "" +"SQLite: supports NOT NULL (for attribute and multiple geometry fields. " +"Support for multiple geometry fields has been added recently per #5494) " +"and DEFAULT on creation/read. AlterFieldDefn() implementation modified to" +" support ALTER_NULLABLE_FLAG and ALTER_DEFAULT_FLAG." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:408 +msgid "" +"MySQL: supports NOT NULL (for attribute fields only) and DEFAULT on " +"creation/read." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:410 +msgid "" +"OCI: supports NOT NULL (for attribute and its single geometry field) and " +"DEFAULT on creation/read. GEOMETRY_NULLABLE layer creation added." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:412 +msgid "" +"VRT: supports NOT NULL (for attribute and multiple geometry fields) and " +"DEFAULT on read, through new attributes \"nullable\" and \"default\" " +"(driver documentation and data/ogrvrt.xsd updated)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:415 +msgid "" +"GML: supports NOT NULL (for attribute and multiple geometry field) on " +"creation/read. DEFAULT not truly supported (no way to express it in .xsd " +"AFAIK), but on creation, unset fields with a NOT NULL constraint and " +"DEFAULT values will be filled by using FillUnsetWithDefault() so as to " +"generate valid XML." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:420 +msgid "WFS: supports NOT NULL (for attribute fields only) on read" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:421 +msgid "" +"FileGDB: supports NOT NULL (for attribute and its single geometry field) " +"on read/write. GEOMETRY_NULLABLE layer creation added. DEFAULT supported " +"for String,Integer and Real fieds on creation/read (with some bugs/weird " +"behavior seen in FileGDB SDK and E$RI tools, workarounded by using the " +"OpenFileGDB driver in problematic cases...). DEFAULT supported for " +"DateTime on read, but unsupported on creation to bug in FileGDB SDK." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:428 +msgid "" +"OpenFileGDB: supports NOT NULL (for attribute and its single geometry " +"field) and DEFAULT on read" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:431 +msgid "" +"MSSQLSpatial could probably support NOT NULL / DEFAULT, but has not been " +"updated as part of this work." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:437 +msgid "The test suite is extended to test:" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:439 +msgid "" +"all new methods of OGRFieldDefn, OGRGeomFieldDefn and OGRFeature in " +"ogr_feature.py" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:441 +msgid "" +"updated drivers: PG, PGDump, CartoDB, GPKG, SQLite, MySQL, OCI, VRT, GML," +" FileGDB, OpenFileGDB" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:443 +msgid "" +"new options of ogr2ogr, and default behavior with NOT NULL / DEFAULT " +"propagation" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:449 +msgid "This RFC should cause few compatibility issues." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:451 +msgid "" +"Regarding API, the existing OGRFieldDefn::SetDefault() has been changed " +"and GetDefaultRef() has been removed. Impact should be low as this wasn't" +" used in any drivers, was documented as being prone to be removed in the " +"future, and so was unlikely to be used in applications either (there was " +"no C binding)" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:457 +msgid "" +"When not using the new API, behavior should remain unchanged w.r.t GDAL " +"1.X when operating on layers created by GDAL. If reading layers created " +"by other tools, then NOT NULL and/or DEFAULT can be read, and propagated." +" We cannot exclude that propagation of NOT NULL / DEFAULT can cause " +"problems in some situations. In which case the new options of ogr2ogr " +"will revert to a behavior that was the one of the GDAL 1.X era." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:467 +msgid "" +"There might be an ambiguity between a field that has not been set and a " +"field that is set to NULL. Both concepts are not distinguished in OGR " +"currently, but most RDBMS are able to make such a distinction." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:471 +msgid "Consider the 2 following statements :" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:478 +msgid "They are not equivalent when COL2 has a default value." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:480 +msgid "" +"The behavior of the modified drivers by this RFC is to *NOT* emit NULL at" +" CreateFeature() time when a field is unset, so that the low-level layer " +"of the driver can replace it with its default value if it exists. This is" +" generally the wished behavior." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:485 +msgid "" +"If explicit NULL insertion is wanted, then using SetFeature() afterwards " +"might be needed, if supported by the drivers (some drivers will likely " +"not force unset OGR fields to be NULL when composing an UPDATE " +"statement), otherwise with a direct SQL UPDATE statement." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:490 +msgid "" +"In fact, this confusion between unset or NULL hurts only in the case of " +"fields that are nullable and have a DEFAULT value. If making sure to " +"always associate DEFAULT with NOT NULL, then it becomes a non-issue as " +"the database would refuse explicit NULL values." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:495 +msgid "" +"Solving the confusion would require to add a new state to an instantiated" +" field within a feature to distinguish explicit NULL from unset, but this" +" would have deep impact in drivers and application code." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:506 +msgid "" +"The proposed implementation lies in the \"rfc53_ogr_notnull_default\" " +"branch of the " +"`https://github.com/rouault/gdal2/tree/rfc53_ogr_notnull_default " +"<https://github.com/rouault/gdal2/tree/rfc53_ogr_notnull_default>`__ " +"repository." +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:511 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/rfc53_ogr_notnull_default " +"<https://github.com/rouault/gdal2/compare/rfc53_ogr_notnull_default>`__" +msgstr "" + +#: ../../source/development/rfc/rfc53_ogr_notnull_default.rst:517 +msgid "+1 from JukkaR, DanielM and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:5 +msgid "RFC 54: Dataset transactions" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:16 +msgid "" +"This RFC introduces an API to offer a transaction mechanism at dataset " +"level and uses it in the PostgreSQL, SQLite and GPKG drivers. It also " +"reworks significantly how transactions are handled in the PostgreSQL " +"driver. It also introduces a generic mechanism to implement an emulation " +"of transactions for datasources that would not natively support it, and " +"uses it in the FileGDB driver." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:26 +msgid "" +"The current abstraction offers a transaction API at the layer level. " +"However, this is generally misleading since, when it is implemented in " +"DBMS with BEGIN/COMMIT/ROLLBACK sql statements (PostgreSQL, SQLite, GPKG," +" PGDump, MSSQLSpatial), the semantics is really a transaction at database" +" level that spans over all layers/tables. So even if calling " +"StartTransaction() on a layer, it also extends on the changes done on " +"other layers. In a very few drivers " +"StartTransaction()/CommitTransaction() is sometimes used as a mechanism " +"to do bulk insertion. This is for example the case of WFS, CartoDB, GFT, " +"GME. For some of them, it could rather be at dataset level too since " +"potentially multiple layer modifications could be stacked together." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:38 +msgid "" +"Furthermode some use cases require updating several layers consistently, " +"hence the need for a real database level transaction abstraction." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:41 +msgid "" +"The current situation of various drivers is the following (some of the " +"below observations resulting from the analysis are kept mainly for the " +"benefit of developers that would need to work in the drivers) :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:48 +msgid "A few facts about cursors used to run GetNextFeature() requests:" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:50 +msgid "" +"Cursors are needed for retrieval of huge amount of data without being " +"memory bound." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:52 +msgid "Cursors need transactions to run." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:53 +msgid "" +"Default cursors (WITHOUT HOLD) cannot be used outside of the transaction " +"that created tem" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:55 +msgid "" +"You cannot modify the structure of a table while the transaction (yes, " +"the transaction, not the cursor) is still active and if you do that on " +"another connection, it hangs until the other connection commits or " +"rollbacks)" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:59 +msgid "" +"Within a transaction, deleted/modified rows are only visible if they are " +"done before declaring the cursor." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:61 +msgid "" +"Cursors WITH HOLD: may be used outside of transaction but cause a copy of" +" the table to be done --> bad for performance" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:64 +msgid "Current flaws are :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:66 +msgid "" +"one cannot do interleaved layer reading (beyond the first 500 features " +"fetched, can be easily seen with OGR_PG_CURSOR_PAGE=1) due to the " +"underlying implicit transaction created to read layer A being closed when" +" the reading of layer B starts." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:70 +msgid "" +"GetFeature() flushes the current transaction and starts a new one to do a" +" cursor SELECT. Which is unnecessary since we retrieve only one record" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:73 +msgid "" +"SetAttributeFilter() issues a ResetReading() which currently " +"FlushSoftTransaction() the ongoing transaction. Can be annoying in a " +"scenario with long update where you need transactional guarantee" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:77 +msgid "What works :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:79 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:90 +msgid "Transaction support at the layer level forwarded to datasource." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:80 +msgid "Interleaved writing works (even with copy mode)" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:83 +msgid "SQLite/GPKG" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:85 +msgid "" +"Mechanisms used to read table content (sqlite3_prepare() / " +"sqlite3_step()) do not need transactions." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:87 +msgid "" +"Step sees structure modifications (e.g. column addition) if run after " +"prepared statement but before first step." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:89 +msgid "Step sees row modifications/additions as soon as they occur." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:93 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:61 +msgid "MySQL" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:95 +msgid "" +"Cannot do interleaved layer reading (reading in one layer resets the " +"other reading) because of the use of mysql_use_result() that can work " +"with one single request at a time. mysql_store_result() would be a " +"solution but requires ingesting the whole result set into memory, which " +"is inpractical for big layers." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:100 +msgid "" +"step does not set row changes once the query has started (if done through" +" another connection, because if done through ExecuteSQL() the long " +"transaction is interrupted)" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:103 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:110 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:117 +msgid "No transaction support" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:108 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:115 +msgid "Interleaved layer reading works" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:109 +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:116 +msgid "Changes done after SELECT seem not to be seen." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:120 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:38 +msgid "Proposed changes" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:123 +msgid "GDALDataset changes" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:125 +msgid "" +"The following methods are added to GDALDataset (and usable by " +"OGRDataSource which inherits from GDALDataset)." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:218 +msgid "" +"Note: in the GDALDataset class itself, those methods have an empty " +"implementation that returns OGRERR_UNSUPPORTED_OPERATION." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:221 +msgid "Those 3 methods are mapped at the C level as :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:229 +msgid "Two news dataset capabilities are added :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:231 +msgid "" +"ODsCTransactions: True if this datasource supports (efficient) " +"transactions." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:233 +msgid "" +"ODsCEmulatedTransactions: True if this datasource supports transactions " +"through emulation." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:237 +msgid "Emulated transactions" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:239 +msgid "" +"A new function OGRCreateEmulatedTransactionDataSourceWrapper() is added " +"for used by drivers that do not natively support transactions but want an" +" emulation of them. It could potentially be adopted by any datasource " +"whose data is supported by files/directories." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:279 +msgid "The definition of the IOGRTransactionBehaviour interface is the following:" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:343 +msgid "OPGRLayer changes" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:345 +msgid "" +"At the OGRLayer level, the documentation of GetNextFeature() receives the" +" following additional information to clarify its semantics :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:359 +msgid "PG driver changes" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:361 +msgid "" +"Dataset level transactions have been implemented, and use of implicitly " +"created transactions reworked." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:364 +msgid "Interleaved layer reading is now possible." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:366 +msgid "" +"GetFeature() has been modified to run without a cursor or a transaction, " +"and all other calls to transactions have been checked/modified to not " +"reset accidentally a transaction initiated by the user." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:370 +msgid "" +"Below the new behavior as described in the updated drv_pg_advanced.html " +"help page :" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:493 +msgid "" +"It is recommended to do operations within explicit transactions for ease " +"of mind (some troubles fixing ogr_pg.py, but which does admittedly weird " +"things like reopening connections, which does not fly very well with " +"'implicit' transactions)" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:499 +msgid "GPKG and SQLite driver changes" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:501 +msgid "" +"Dataset level transactions have been implemented. A few fixes made here " +"and there to avoid resetting accidentally a transaction initiated by the " +"user." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:506 +msgid "FileGDB driver changes" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:508 +msgid "" +"The FileGDB driver uses the above described emulation to offer a " +"transaction mechanism. This works by backing up the current state of a " +"geodatabase when StartTransaction(force=TRUE) is called. If the " +"transaction is committed, the backup copy is destroyed. If the " +"transaction is rolled back, the backup copy is restored. So this might be" +" costly when operating on huge geodatabases. Note that this emulation has" +" an unspecified behavior in case of concurrent updates (with different " +"connections in the same or another process)." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:522 +msgid "Dataset.StartTransaction(int force=FALSE)" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:523 +msgid "Dataset.CommitTransaction()" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:524 +msgid "Dataset.RollbackTransaction()" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:525 +msgid "ogr.ODsCTransactions constant" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:526 +msgid "ogr.ODsCEmulatedTransactions constant" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:531 +msgid "" +"ogr2ogr now uses dataset transactions (instead of layer transactions) if " +"ODsCTransactions is advertized." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:537 +msgid "" +"New/modified API are documented. MIGRATION_GUIDE.TXT updated with mention" +" to below compatibility issues." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:543 +msgid "The test suite is extended to test" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:545 +msgid "updated drivers: PG, GPKG, SQLite, FileGDB" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:546 +msgid "use of database transactions by ogr2ogr" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:551 +msgid "" +"As described above, subtle behavior changes can be observed with the PG " +"driver, related to implicit transactions that were flushed before and are" +" no longer now, but this should hopefully be restricted to non-typical " +"use cases. So some cases that \"worked\" before might no longer work, but" +" the new behavior should hopefully be more understandable." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:558 +msgid "" +"The PG and SQLite drivers could accept apparently nested calls to " +"StartTransaction() (at the layer level). This is no longer possible since" +" they are now redirected to dataset transactions, that explicitly do not " +"support it." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:564 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:642 +msgid "Out of scope" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:566 +msgid "" +"The following drivers that implement BEGIN/COMMIT/ROLLBACK could be later" +" enhanced to support dataset transactions: OCI, MySQL, MSSQLSpatial." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:570 +msgid "GFT, CartoDB, WFS could also benefit for dataset transactions." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:572 +msgid "" +"VRT currently supports layer transactions (if the underlying dataset " +"support it, and excluding union layers). If dataset transaction were to " +"be implemented, should it consist in forwarding dataset transaction to " +"source dataset(s) ? Implementation might be complicated in case the same " +"dataset is used by multiple sources, but more fundamentally one cannot " +"guarantee ACID on multiple datasets." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:582 +msgid "" +"A proposed revision on how transactions are implemented in the PG driver " +"was proposed a long time ago (`https://trac.osgeo.org/gdal/ticket/1265 " +"<https://trac.osgeo.org/gdal/ticket/1265>`__) to solve some of the above " +"issues. The patch no longer applies but it is expected that the changes " +"done for this RFC cover the issues that the ticket wanted to address." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:596 +msgid "" +"The proposed implementation lies in the \"rfc54_dataset_transactions\" " +"branch of the " +"`https://github.com/rouault/gdal2/tree/rfc54_dataset_transactions " +"<https://github.com/rouault/gdal2/tree/rfc54_dataset_transactions>`__ " +"repository." +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:601 +msgid "" +"The list of changes: " +"`https://github.com/rouault/gdal2/compare/rfc54_dataset_transactions " +"<https://github.com/rouault/gdal2/compare/rfc54_dataset_transactions>`__" +msgstr "" + +#: ../../source/development/rfc/rfc54_dataset_transactions.rst:607 +msgid "+1 from JukkaR, HowardB and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:5 +msgid "RFC 55: Refined SetFeature() and DeleteFeature() semantics" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:16 +msgid "" +"This RFC refines the semantics of SetFeature() and DeleteFeature() so as " +"to be able to distinguish nominal case, attempts of updating/deleting " +"non-existing features, from failures to update/delete existing features." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:23 +msgid "" +"Currently, depending on the drivers, calling SetFeature() or " +"DeleteFeature() on a non-existing feature may succeed, or fail. It is " +"generally not desirable that those functions return the OGRERR_NONE code," +" as in most situations, it might be a sign of invalid input. Therefore " +"the OGRERR_NON_EXISTING_FEATURE return code is introduced so that drivers" +" can inform the calling code that it has attempted to update or delete a " +"non-existing feature." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:32 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:49 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:31 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:29 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:130 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:33 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:99 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:177 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:40 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:55 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:44 +msgid "Changes" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:34 +msgid "#define OGRERR_NON_EXISTING_FEATURE 9 is added to ogr_core.h" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:39 +msgid "" +"The following drivers are updated to implement the new semantics: " +"PostgreSQL, CartoDB, SQLite, GPKG, MySQL, OCI, FileGDB, Shape, MITAB" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:42 +msgid "Note: MSSQL could also likely be updated" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:45 +msgid "Caveats" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:47 +msgid "" +"The behavior of the shapefile driver is a bit particular, in that, its " +"SetFeature() implementation accepts to recreate a feature that had been " +"deleted (and its CreateFeature() implementation ignores any set FID on " +"the passed feature to append a new feature). So " +"OGRERR_NON_EXISTING_FEATURE will effictively been returned only if the " +"FID is negative or greater or equal to the maximum feature count." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:57 +msgid "" +"OGRERR_NON_EXISTING_FEATURE is added. All OGRERR_xxxx constants are " +"exposed to the Python bindings" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:63 +msgid "No impact" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:68 +msgid "" +"Documentation of SetFeature() and DeleteFeature() mentions the new error " +"code. MIGRATION_GUIDE.TXT updated with mention to below compatibility " +"issues." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:75 +msgid "" +"The test suite is extended to test the modified drivers. test_ogrsf also " +"tests the behavior of drivers updating/deleting non-existing features." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:81 +msgid "" +"Code that expected update or deleting of non-existing features to succeed" +" will have to be updated." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:91 +msgid "" +"The proposed implementation lies in the " +"\"rfc55_refined_setfeature_deletefeature_semantics\" branch of the " +"`https://github.com/rouault/gdal2/tree/rfc55_refined_setfeature_deletefeature_semantics" +" " +"<https://github.com/rouault/gdal2/tree/rfc55_refined_setfeature_deletefeature_semantics>`__" +" repository." +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:96 +msgid "" +"The list of changes: " +"`https://github.com/rouault/gdal2/compare/rfc55_refined_setfeature_deletefeature_semantics" +" " +"<https://github.com/rouault/gdal2/compare/rfc55_refined_setfeature_deletefeature_semantics>`__" +msgstr "" + +#: ../../source/development/rfc/rfc55_refined_setfeature_deletefeature_semantics.rst:102 +msgid "+1 from from DanielM, HowardB, JukkaR and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:5 +msgid "RFC 56: OFTTime/OFTDateTime millisecond accuracy" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:13 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:13 +msgid "Version: 2.0" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:18 +msgid "" +"This RFC aims at adding millisecond accuracy to OFTTime and OFTDateTime " +"fields, as a number of formats support it explicitly or implicitly : " +"MapInfo, GPX, Atom (GeoRSS driver), GeoPackage, SQLite, PostgreSQL, CSV, " +"GeoJSON, ODS, XLSX, KML (potentially GML too)..." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:26 +msgid "The OGRField enumeration is modified as such :" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:46 +msgid "" +"So the \"GByte Second\" field is removed and replaced by a padding Byte " +"reserved for potential later uses. A \"float Second\" field is added." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:49 +msgid "" +"On 32 bit builds, the size of OGRField is now 12 bytes instead of 8 " +"bytes. On 64 bit builds, the size of OGRField remains 16 bytes." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:53 +msgid "New/modified methods" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:55 +msgid "" +"OGRFeature::SetFieldAsDateTime() methods that took a int nSecond now take" +" a float fSecond parameter. The GetFieldAsDateTime() method that took a " +"int\\* pnSecond is kept, and a new GetFieldAsDateTime() method that takes" +" a float\\* pfSecond is added." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:60 +msgid "In OGRFeature class :" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:80 +msgid "" +"OGRFeature::GetFieldAsString() is modified to output milliseconds if the " +"Second member of OGRField.Date is not integral" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:83 +msgid "OGRParseDate() is modified to parse second as floating point number." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:85 +msgid "" +"The following utility functions have their signature modified to take a " +"OGRField (instead of the full year, month, day, hour, minute, second, " +"TZFlag decomposition) and accept decimal seconds as input/output :" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:115 +msgid "The following drivers now accept milliseconds as input/output :" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:117 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:56 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:437 +msgid "GeoJSON" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:118 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:504 +msgid "CSV" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:119 +msgid "PG" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:120 +msgid "PGDump (output only)" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:121 +msgid "CartoDB" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:122 +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:434 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:514 +msgid "GeoPackage" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:123 +msgid "SQLite" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:124 +msgid "MapInfo .tab and .mif" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:125 +msgid "LIBKML" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:126 +msgid "ODS" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:127 +msgid "XLSX" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:128 +msgid "GeoRSS (Atom format)" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:129 +msgid "GPX" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:134 +msgid "" +"Feature.GetFieldAsDateTime() and Feature.SetFieldAsDateTime() now " +"takes/returns a floating point number for seconds" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:140 +msgid "This modifies the C/C++ API and ABI." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:142 +msgid "" +"Output of above mentioned drivers will now include milliseconds if a " +"DateTime/Time field has such precision." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:146 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:116 +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:100 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:779 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:199 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:280 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:85 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:187 +msgid "Related ticket" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:148 +msgid "" +"The need came from `http://trac.osgeo.org/gdal/ticket/2680 " +"<http://trac.osgeo.org/gdal/ticket/2680>`__ for MapInfo driver." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:155 +msgid "" +"All new/modified methods are documented. MIGRATION_GUIDE.TXT is updated " +"with a new section for this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:172 +msgid "" +"The proposed implementation lies in the \"subsecond_accuracy\" branch of " +"the `https://github.com/rouault/gdal2/tree/subsecond_accuracy " +"<https://github.com/rouault/gdal2/tree/subsecond_accuracy>`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:177 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/subsecond_accuracy " +"<https://github.com/rouault/gdal2/compare/subsecond_accuracy>`__" +msgstr "" + +#: ../../source/development/rfc/rfc56_millisecond_precision.rst:183 +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:148 +msgid "+1 from DanielM, JukkaR and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:5 +msgid "RFC 57: 64-bit bucket counts for histograms" +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:18 +msgid "" +"This RFC modifies the GDALRasterBand GetHistogram(), " +"GetDefaultHistogram() and SetDefaultHistogram() methods to accept arrays " +"of 64-bit integer instead of the current arrays of 32-bit integer for " +"bucket counts. It also changes GetRasterSampleOverview() to take a 64-bit" +" integer. This will fix issues when operating on large rasters that have " +"more than 2 billion pixels." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:28 +msgid "" +"The following methods of GDALRasterBand class are modified to take a " +"GUIntBig\\* argument for GetHistogram() and SetDefaultHistograph(), " +"GUIntBig*\\* for GetDefaultHistogram() and GUIntBig for " +"GetRasterSampleOverview()" +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:50 +msgid "PAM serialization/deserialization is also updated." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:80 +msgid "" +"The existing methods GDALGetRasterHistogram(), GDALGetDefaultHistogram() " +"and GDALSetDefaultHistogram() are marked deprecated. They internally call" +" the 64-bit methods, and, for GDALGetRasterHistogram() and " +"GDALGetDefaultHistogram(), warn if a 32-bit overflow would occur, in " +"which case the bucket count is set to INT_MAX." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:89 +msgid "" +"All in-tree drivers that use/implement the C++ histogram methods are " +"modified: ECW, VRT, MEM and HFA." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:95 +msgid "gdalinfo and gdalenhance are modified to use the modified methods." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:100 +msgid "" +"For Python bindings only, RasterBand.GetHistogram(), " +"GetDefaultHistogram() and SetDefaultHistogram() use the new 64-bit C " +"functions." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:104 +msgid "" +"Other bindings could be updated, but likely need new typemaps for (int, " +"GUIntBig*). In the meantime, they still use the 32-bit C functions." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:110 +msgid "This modifies the C++ API and ABI." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:112 +msgid "" +"Out-of-tree drivers must make sure to take into account the updated C++ " +"API if they implement some of the 4 modified virtual methods." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:118 +msgid "#5159" +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:123 +msgid "" +"All new/modified methods/functions are documented. MIGRATION_GUIDE.TXT is" +" updated with a new section for this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:129 +msgid "Setting/getting 64 bit values is tested in gcore/pam.y and gdrivers/mem.py" +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:138 +msgid "" +"The proposed implementation lies in the \"histogram_64bit_count\" branch " +"of the `https://github.com/rouault/gdal2/tree/histogram_64bit_count " +"<https://github.com/rouault/gdal2/tree/histogram_64bit_count>`__." +msgstr "" + +#: ../../source/development/rfc/rfc57_histogram_64bit_count.rst:142 +msgid "" +"The list of changes : " +"`https://github.com/rouault/gdal2/compare/histogram_64bit_count " +"<https://github.com/rouault/gdal2/compare/histogram_64bit_count>`__" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:5 +msgid "RFC 58: Removing Dataset Nodata Value" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:7 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:7 +msgid "Authors: Sean Gillies" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:9 +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:9 +msgid "Contact: sean at mapbox.com" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:13 +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:13 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:13 +msgid "Implementation version: 2.1" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:18 +msgid "" +"This RFC concerns addition of a ``DeleteNoDataValue()`` function to the " +"C++ GDALRasterBand API. This function removes the nodata value of a " +"raster band. When it succeeds, the raster band will have no nodata value." +" When it fails, the nodata value will be unchanged." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:26 +msgid "" +"The nodata value has accessors ``GetNoDataValue()`` and " +"``SetNoDataValue()``. For GeoTIFFs, the value is stored in a " +"TIFFTAG_GDAL_NODATA TIFF tag. Newly created GeoTIFF files can have no " +"nodata value (no tag), but once a nodata value is set and stored it can " +"only be given new values, it can not be removed. Nor can it be set to a " +"value outside the range of the data type; for 8-bit data passing ``nan``," +" ``-inf``, or ``256`` to ``GDALSetNoDataValue()`` has the same effect as " +"passing 0." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:35 +msgid "The problem with un-removable nodata values is this:" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:37 +msgid "" +"Nodata masks (see GDAL RFC 15) can cover up a nodata value but if the " +".msk file gets lost (and this is ever the problem with sidecar files), " +"the nodata value you were hiding is exposed again." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:40 +msgid "" +"Nodata masks are not available everywhere in GDAL, nodata values are the " +"only definition of valid data in some parts of GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:43 +msgid "" +"The current recommended practice for removing a nodata value is to copy " +"the GeoTIFF using gdal_translate, specifying that the nodata tag not be " +"copied over along with the data. By making the nodata value fully " +"editable and removable we could avoid copying unnecessarily." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:51 +msgid "" +"The ``virtual CPLErr DeleteNoDataValue()`` method will be added to the " +"GDALRasterBand method in gdal_priv.h (C++ API), and ``CPLErr " +"GDALDeleteRasterNoDataValue()`` to gdal.h (C API)" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:58 +msgid "The following drivers will be updated: GTiff, MEM, VRT and KEA." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:60 +msgid "" +"For GTiff, the TIFFTAG_GDAL_NODATA TIFF tag is unset if GDAL is built " +"against libtiff 4.X, which is the appropriate behavior. For libtiff 3.X " +"where TIFFUnsetField() does not exist, the tag is set to the empty string" +" : GDAL 2.0 will detect that as the absence of a nodata value, older " +"versions will parse it as 0." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:66 +msgid "" +"The ``GDALPamRasterBand`` class will also be updated (for drivers that " +"have no built-in mechanism nodata mechanism and rely on .aux.xml " +"sidecars). Note that this only removes the tag from the .aux.xml, so in " +"the situation where a driver would have a internal way of storing nodata," +" but would be opened in read-only mode (so defaulting to PAM), " +"DeleteNoData() would have no effect." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:76 +msgid "The DeleteNoDataValue() method is added to the RasterBand object." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:81 +msgid "The gdal_edit.py script is enhanced with a -unsetnodata option." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:86 +msgid "The new method and function are documented." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:91 +msgid "The tests of the updated drivers test the effect of the new method." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:96 +msgid "" +"None for the C API. ABI change for the C++ API because of introduction of" +" a new virtual method." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:102 +msgid "#2020 mentions the issue." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:107 +msgid "Implementation will be done by Even Rouault and be sponsored by Mapbox." +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:109 +msgid "" +"A proposed implementation is available in " +"`https://github.com/OSGeo/gdal/compare/trunk...rouault:rfc58_removing_nodata_value" +" " +"<https://github.com/OSGeo/gdal/compare/trunk...rouault:rfc58_removing_nodata_value>`__" +msgstr "" + +#: ../../source/development/rfc/rfc58_removing_dataset_nodata_value.rst:115 +msgid "+1 from EvenR, HowardB, DanielM and JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:5 +msgid "RFC 59.1 : GDAL/OGR utilities as a library" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:7 +msgid "Authors: Faza Mahamood, Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:9 +msgid "Contact: fazamhd at gmail dot com, even.rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:18 +msgid "" +"This RFC defines how to expose GDAL/OGR C/C++ utilities as C callable " +"functions. The utility code is modified to call the new function. This " +"RFC gives a general frame and principles, demonstrated with a few " +"utilities, but aimed at being extended with other utilities." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:26 +msgid "" +"There is a need for calling GDAL utilities from code without involving " +"system calls, to be able to work on in-memory datasets and use " +"progress/cancellation callback functions." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:33 +msgid "" +"A public header file gdal_utils.h is created which contains the public " +"declarations of GDAL utilities. The current header(still in progress) can" +" be found `here " +"<https://github.com/rouault/gdal2/blob/rfc59.1/gdal/apps/gdal_utils.h>`__." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:38 +msgid "" +"Each utility has a function (XXXXOptionsNew) to create an option " +"structure from arguments specified as an array of strings. This function " +"also accepts as argument an extra semi-private structure used to " +"cooperate with the code of the command line utility itself." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:43 +msgid "For GDALInfo():" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:83 +msgid "Similarly for GDALTranslate():" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:105 +msgid "Similarly for GDALWarp():" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:130 +msgid "Similarly for GDALVectorTranslate() (equivalent of ogr2ogr):" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:152 +msgid "" +"For other utilities, see `gdal_utils.h " +"<http://svn.osgeo.org/gdal/trunk/gdal/apps/gdal_utils.h>`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:159 +msgid "All bindings" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:161 +msgid "For all bindings, the above functions are mapped to SWIG with :" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:276 +msgid "" +"For other utilities, see `gdal.i " +"<http://svn.osgeo.org/gdal/trunk/gdal/swig/python/gdal.i>`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:280 +msgid "Python bindings" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:282 +msgid "" +"For Python bindings, convenience wrappers are created to allow specifying" +" options in a more user friendly way." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:306 +msgid "" +"gdal.Info() can be used either with setting the attributes of " +"gdal.InfoOptions() or inlined arguments of gdal.Info(). Arguments can be " +"specified as array of strings, command line syntax or dedeicated " +"keywords. So various combinations are possible :" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:734 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:153 +msgid "Utilities are modified to call the respective function." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:739 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:158 +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:266 +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:341 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:252 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:156 +msgid "All new methods/functions are documented." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:744 +msgid "" +"gdal.Info method is tested in `test_gdalinfo_lib.py " +"<http://svn.osgeo.org/gdal/trunk/autotest/utilities/test_gdalinfo_lib.py>`__." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:747 +msgid "" +"gdal.Translate method is tested in `test_gdal_translate_lib.py " +"<http://svn.osgeo.org/gdal/trunk/autotest/utilities/test_gdal_translate_lib.py>`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:750 +msgid "" +"gdal.Warp method is tested in `test_gdalwarp_lib.py " +"<http://svn.osgeo.org/gdal/trunk/autotest/utilities/test_gdalwarp_lib.py>`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:753 +msgid "" +"gdal.VectorTranslate method is tested in `test_ogr2ogr_lib.py " +"<http://svn.osgeo.org/gdal/trunk/autotest/utilities/test_ogr2ogr_lib.py>`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:756 +msgid "" +"gdal.DEMProcessing method is tested in `test_gdaldem_lib.py " +"<http://svn.osgeo.org/gdal/trunk/autotest/utilities/test_gdaldem_lib.py>`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:759 +msgid "" +"gdal.Nearblack method is tested in `test_nearblack_lib.py " +"<http://svn.osgeo.org/gdal/trunk/autotest/utilities/test_nearblack_lib.py>`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:762 +msgid "" +"gdal.Grid method is tested in `test_gdal_grid_lib.py " +"<http://svn.osgeo.org/gdal/trunk/autotest/utilities/test_gdal_grid_lib.py>`__" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:765 +msgid "" +"gdal.Rasterize method is tested in `test_gdal_rasterize_lib.py " +"<http://svn.osgeo.org/gdal/trunk/autotest/utilities/test_gdal_rasterize_lib.py>`__." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:768 +msgid "" +"gdal.BuildVRT method is tested in `test_gdalbuildvrt_lib.py " +"<http://svn.osgeo.org/gdal/trunk/autotest/utilities/test_gdalbuildvrt_lib.py>`__." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:774 +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:171 +msgid "" +"None expected. Command line utilities will keep the same interface. It " +"will be checked by ensuring their tests in autotest/utilities still pass." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:784 +msgid "Implementation will be done by Faza Mahamood and Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:786 +msgid "" +"The proposed implementation for gdalinfo and gdal_translate lies in the " +"\"rfc59.1\" branch of the `https://github.com/rouault/gdal2/tree/rfc59.1 " +"<https://github.com/rouault/gdal2/tree/rfc59.1>`__." +msgstr "" + +#: ../../source/development/rfc/rfc59.1_utilities_as_a_library.rst:793 +msgid "+1 from DanielM and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:5 +msgid "RFC 59 : GDAL/OGR utilities as a library" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:7 +msgid "Authors: Faza Mahamood" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:9 +msgid "Contact: fazamhd at gmail dot com" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:11 +msgid "Status: Retracted in favor of :ref:`rfc-59.1`" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:16 +msgid "" +"This RFC defines new function for each GDAL utility. The new utility " +"functions can be used to work on in-memory datasets. The utility code is " +"modified to call the new function. This RFC gives a general frame and " +"principles, demonstrated with gdalinfo, but aimed at being extended with " +"other utilities." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:25 +msgid "" +"There is need for calling GDAL utilities from the code. But this involves" +" using system calls and cannot work on in-memory datasets." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:31 +msgid "" +"New library libgdalutils is created. Both Unix and Windows build have " +"been modified to take into account the new lib. The GDAL utilities are " +"modified to use the new functions. New header file gdal_utils.h is " +"created which contains the public declarations of GDAL utilities. The " +"current header(still in progress) can be found `here " +"<https://github.com/fazam/gdal/blob/gdalinfo/gdal/apps/gdal_utils.h>`__." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:66 +msgid "" +"For Python bindings only, new functions Info(), Translate() and Warp() " +"are added in the gdal module which uses the new GDALInfo(), " +"GDALTranslate() and GDALWarp() function respectively. Translate() is " +"added in the ogr module which uses the new OGR2OGR() function." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:71 +msgid "" +"gdal.Info() can be used either with setting the attributes of " +"gdal.InfoOptions() or inlined arguments of gdal.Info()." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:163 +msgid "" +"gdal.Info method is tested in test_gdalinfo_lib.py. gdal.Translate method" +" is tested in test_gdal_translate_lib.py. gdal.Warp method is tested in " +"test_gdalwarp_lib.py. ogr.Translate method is tested in " +"test_ogr2ogr_lib.py." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:176 +msgid "Open question" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:178 +msgid "" +"What name should be given for librarified ogr2ogr? OGR2OGR() or " +"OGRTranslate() ?" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:181 +msgid "" +"The order of arguments in GDALTranslate(), GDALWarp() and OGR2OGR() is " +"currently dest then source(s)." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:194 +msgid "" +"It is similar to GDALCreateCopy(const char\\* pszDestFilename, " +"GDALDatasetH hSrcDS, ....), so at least there's a form of consistency at " +"the API level. Any comments?" +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:204 +msgid "Implementation will be done by Faza Mahamood." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:206 +msgid "" +"The proposed implementation lies in the \"gdalinfo\" branch of the " +"`https://github.com/fazam/gdal/tree/gdalinfo " +"<https://github.com/fazam/gdal/tree/gdalinfo>`__." +msgstr "" + +#: ../../source/development/rfc/rfc59_utilities_as_a_library.rst:209 +msgid "" +"The list of changes : `https://github.com/fazam/gdal/compare/gdalinfo " +"<https://github.com/fazam/gdal/compare/gdalinfo>`__" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:5 +msgid "RFC 5: Unicode support in GDAL" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:16 +msgid "" +"This document contains proposal on how to make GDAL core locale " +"independent preserving support for native character sets." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:24 +msgid "" +"Users work in localized environment using their native languages. That " +"means we can not assume ASCII character set when working with string data" +" passed to GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:27 +msgid "GDAL uses UTF-8 encoding internally when working with strings." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:28 +msgid "GDAL uses Unicode version of third-party APIs when it is possible." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:30 +msgid "" +"So all strings, used in GDAL, are in UTF-8, not in plain ASCII. That " +"means we should convert user's input from the local encoding to UTF-8 " +"during interactive sessions. The opposite should be done for GDAL output." +" For example, when user passes a filename as a command-line parameter to " +"GDAL utilities, that filename should be immediately converted to UTF-8 " +"and only afetrwards passed to functions like GDALOpen() or OGROpen(). All" +" functions, which take character strings as parameters, assume UTF-8 " +"(with except of several ones, which will do the conversion between " +"different encodings, see Implementation). The same is valid for output " +"functions. Output functions (CPLError/CPLDebug), embedded in GDAL, should" +" convert all strings from UTF-8 to local encoding just before printing " +"them. Custom error handlers should be aware of UTF-8 issue and do the " +"proper transformation of strings passed to them." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:45 +msgid "" +"The string encoding pops up again when GDAL needs to call the third-party" +" API. UTF-8 should be converted to encoding suitable for that API. In " +"particular, that means we should convert UTF-8 to UTF-16 before calling " +"CreateFile() function in Windows implementation of VSIFOpenL(). Another " +"example is a PostgreSQL API. PostgreSQL stores strings in UTF-8 encoding " +"internally, so we should notify server that passed string is already in " +"UTF-8 and it will be stored as is without any conversions and losses." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:54 +msgid "" +"For file format drivers the string representation should be worked out on" +" per-driver basis. Not all file formats support non-ASCII characters. For" +" example, various .HDR labeled rasters are just 7-bit ASCII text files " +"and it is not a good idea to write 8-bit strings in such a files. When we" +" need to pass strings, extracted from such file outside the driver (e.g.," +" in SetMetadata() call), we should convert them to UTF-8. If you just " +"want to use extracted strings internally in driver, there is no need in " +"any conversions." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:63 +msgid "" +"In some cases the file encoding can differ from the local system encoding" +" and we do not have a way to know the file encoding other than ask a user" +" (for example, imagine a case when someone added a 8-bit non-ASCII string" +" field to mentioned above plain text .HDR file). That means we can't use " +"conversion form the local encoding to UTF-8, but from the file encoding " +"to UTF-8. So we need a way to get file encoding in some way on per " +"datasource basis. The natural solution of the problem is to introduce " +"optional open parameter \"ENCODING\" to GDALOpen/OGROpen functions. " +"Unfortunately, those functions do not accept options. That should be " +"introduced in another RFC. Fortunately, tehre is no need to add encoding " +"parameter immediately, because it is independent from the general i18n " +"process. We can add UTF-8 support as it is defined in this RFC and add " +"support for forcing per-datasource encoding later, when the open options " +"will be introduced." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:81 +msgid "" +"New character conversion functions will be introduced in CPLString class." +" Objects of that class always contain UTF-8 string internally." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:106 +msgid "" +"In order to use non-ASCII characters in user input every application " +"should call setlocale(LC_ALL, \"\") function right after the entry point." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:110 +msgid "" +"Code example. Let's look how the gdal utilities and core code should be " +"changed in regard to Unicode." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:113 +msgid "For input instead of" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:121 +#: ../../source/development/rfc/rfc5_unicode.rst:136 +msgid "we should do" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:129 +msgid "For output instead of" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:145 +msgid "" +"The filename passed to GDALOpen() in UTF-8 encoding in the code snippet " +"above will be further processed in the GDAL core. On Windows instead of" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:155 +msgid "we do" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:167 +msgid "" +"The actual implementation of the character conversion functions does not " +"specified in this document yet. It needs additional discussion. The main " +"problem is that we need not only local<->UTF-8 encoding conversions, but " +"*arbitrary*\\ <->UTF-8 ones. That requires significant support on " +"software part." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:176 +msgid "" +"The GDAL/OGR backward compatibility will be broken by this new " +"functionality in the way how 8-bit characters handled. Before users may " +"rely on that all 8-bit character strings will be passed through the " +"GDAL/OGR without change and will contain exact the same data all the way." +" Now it is only true for 7-bit ASCII and 8-bit UTF-8 encoded strings. " +"Note, that if you used only ASCII subset with GDAL, you are not affected " +"by these changes." +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:184 +msgid "From The Unicode Standard, chapter 5:" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:186 +msgid "" +"*The width of wchar_t is compiler-specific and can be as small as 8 bits." +" Consequently, programs that need to be portable across any C or C++ " +"compiler should not use wchar_t for storing Unicode text.*" +msgstr "" + +#: ../../source/development/rfc/rfc5_unicode.rst:202 +msgid "Filenames also covered in [[wiki:rfc30_utf8_filenames]]" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:5 +msgid "RFC 60 : Improved round-tripping in OGR" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:9 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:9 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:9 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:9 +msgid "Contact: even.rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:18 +msgid "" +"This RFC defines how to improve better round-tripping in conversion of " +"vector formats, in particular for GeoJSON extensions." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:24 +msgid "" +"Some formats have concepts that are not well modeled by the OGR " +"abstraction, but that are desirable to be preserved in transformation " +"scenarios involving reprojection, spatial/attribute filtering, clipping, " +"etc... where the target format is the source format." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:29 +msgid "" +"Various extensions exist above the core GeoJSON specification: at the " +"FeatureCollection, Feature or Geometry levels." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:32 +msgid "" +"See `https://github.com/mapbox/carmen/blob/master/carmen-geojson.md " +"<https://github.com/mapbox/carmen/blob/master/carmen-geojson.md>`__," +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:72 +msgid "" +"`https://github.com/geocoders/geocodejson-" +"spec/blob/master/draft/README.md <https://github.com/geocoders" +"/geocodejson-spec/blob/master/draft/README.md>`__:" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:108 +msgid "" +"or `https://github.com/geojson/draft-" +"geojson/issues/80#issuecomment-138037554 <https://github.com/geojson" +"/draft-geojson/issues/80#issuecomment-138037554>`__ for a few examples." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:133 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:72 +msgid "OGRFeature" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:135 +msgid "" +"Two new members will be added to the OGRFeature class, m_pszNativeData " +"(string) and m_pszNativeMediaType (string). m_pszNativeData will contain " +"the representation (or part of the representation) of the original " +"feature, and m_pszNativeMediaType the `media type " +"<https://en.wikipedia.org/wiki/Media_type>`__" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:141 +msgid "The following methods will be added to OGRFeature class:" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:151 +msgid "" +"Thus, in the GeoJSON case, nativeData would contain the full " +"serialization of a GeoJSON Feature. m_pszNativeMediaType would be set to " +"\"application/vnd.geo+json\" The writer side of the GeoJSON driver would " +"start from the nativeData if present (and if nativeMediaType = " +"\"application/vnd.geo+json\", replace its properties member with the " +"content of the OGR fields and patch its geometry to include additional " +"JSON objects." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:159 +msgid "" +"The OGRFeature::Clone() and ::SetFrom() methods will propagate nativeData" +" and nativeMediaType." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:163 +msgid "OGRLayer" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:165 +msgid "" +"A dedicated metadata domain \"NATIVE_DATA\" in which there would be a " +"\"NATIVE_DATA\" and \"NATIVE_MEDIA_TYPE\" items would be used. In the " +"GeoJSON case, this would contain JSON members at the FeatureCollection " +"level (excluding the features array of course)." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:171 +msgid "Driver open options and layer creation options" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:173 +msgid "" +"Drivers that support nativeData on read should expose a NATIVE_DATA " +"boolean open option, and disable it by default so as not to impact " +"performance. ogr2ogr will by default turn this option on." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:177 +msgid "" +"Drivers that support nativeData on write at the layer level should expose" +" a NATIVE_DATA string and NATIVE_MEDIA_TYPE string layer creation " +"options, so that ogr2ogr can fill them with the content of the " +"NATIVE_DATA metadata domain of the source layer(s)." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:185 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:89 +msgid "The following functions will be added:" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:195 +msgid "SQL result layers" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:197 +msgid "" +"Both OGR SQL and SQLite SQL dialect implementations have been modified to" +" propagate the content of the NATIVE_DATA metadata domain of the source " +"layer (the one of the FROM table) to the target layer, and NativeData and" +" NativeMediaType from source features are copied into target features." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:206 +msgid "" +"The new functions will mapped to SWIG as GetNativeData(), " +"SetNativeData(), GetNativeMediaType() and SetNativeMediaType()" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:212 +msgid "" +"The GeoJSON driver will be modified to implement this RFC, in read and " +"write, and thus will\\* :" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:215 +msgid "" +"declare a NATIVE_DATA open option to enable storing layer and feature " +"native data." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:217 +msgid "" +"and NATIVE_DATA & NATIVE_MEDIA_TYPE layer creation options so as to be " +"able to write native data at FeatureCollection levels" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:219 +msgid "use OGRFeature nativeData on write." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:221 +msgid "" +"The effect of this is that ogr2ogr will be able to preserve the members " +"marked between ``***`` in the below snippet:" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:246 +msgid "" +"Other drivers like ElasticSearch and MongoDB drivers, that use a \\_json " +"OGR field for round-tripping could potentially be upgraded to benefit " +"from the mechanism of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:253 +msgid "" +"ogr2ogr will be modified to automatically copy nativeData at layer and " +"feature level. A -noNativeData flag will be added to avoid doing so, when" +" this is not desirable." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:257 +msgid "" +"By default, ogr2ogr will open datasources with the NATIVE_DATA=YES open " +"option so that drivers that can store nativeData do so. And if the output" +" datasource supports the NATIVE_DATA and NATIVE_MEDIA_TYPE layer creation" +" options, it will feel them with the content of the source layer " +"NATIVE_DATA metadata domain." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:271 +msgid "The GeoJSON and ogr2ogr related tests will be extended" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:276 +msgid "" +"Nothing severe expected. Potentially existing scripts might need to add " +"-noNativeData to get previous behavior." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:282 +msgid "" +"`https://trac.osgeo.org/gdal/ticket/5310 " +"<https://trac.osgeo.org/gdal/ticket/5310>`__" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:287 +msgid "" +"The implementation will be done by Even Rouault (Spatialys) and be " +"sponsored by Mapbox." +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:290 +msgid "" +"The proposed implementation lies in the \"rfc60_native_data\" branch of " +"the ​\\ `https://github.com/rouault/gdal2/tree/rfc60_native_data " +"<https://github.com/rouault/gdal2/tree/rfc60_native_data>`__, in pull " +"request `https://github.com/OSGeo/gdal/pull/75 " +"<https://github.com/OSGeo/gdal/pull/75>`__" +msgstr "" + +#: ../../source/development/rfc/rfc60_improved_roundtripping_in_ogr.rst:299 +msgid "+1 from HowardB, KurtS, TamasS, JukkaR and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:5 +msgid "RFC 61 : Support for measured geometries" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:9 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:9 +msgid "Contact: ari.jolma at gmail.com" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:13 +msgid "Implementation in version: 2.1" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:18 +msgid "" +"This RFC defines how to implement measured geometries (geometries, where " +"the points have M coordinate, i.e., they are XYM or XYZM)." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:24 +msgid "" +"An M coordinate, which is also known as \"measure\", is an additional " +"value that can be stored for each point of a geometry (IBM Technical " +"Note, `https://www-304.ibm.com/support/docview.wss?uid=swg21054384 " +"<https://www-304.ibm.com/support/docview.wss?uid=swg21054384>`__)." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:29 +msgid "" +"M coordinate is in the OGC simple feature model and it is used in many " +"vector data formats." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:35 +msgid "" +"Changes are required into the C++ API and the C API needs to be enhanced." +" Several drivers need to be changed to take advantage of this enhancement" +" but also due to the changes in the C++ API." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:40 +msgid "Common API" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:42 +msgid "" +"New OGRwkbGeometryType values are needed. SFSQL 1.2 and ISO SQL/MM Part 3" +" will be used, i.e., 2D type + 2000 for M and 2D type + 3000 for ZM. " +"(Also types such as Tin, PolyhedralSurface and Triangle types can be " +"added for completeness, even if unimplemented currently). wkbCurve and " +"wkbSurface have been moved from #define to the OGRwkbGeometryType " +"enumerations, and their Z/M/ZM variants have been added as well (per " +"#6401)" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:50 +msgid "" +"On a more general note, there could (should?) be a path to using a clean " +"set of values and have legacy support as an exception." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:53 +msgid "Abstract types are defined and not part of the enum." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:115 +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:41 +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:58 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:56 +msgid "C++ API" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:117 +msgid "" +"The property int nCoordinateDimension in class OGRGeometry will be " +"replaced by int flags. It may have the following flags:" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:127 +msgid "" +"The \"ignore\" flag is needed internally for backwards compatibility. The" +" flag OGR_G_NOT_EMPTY_POINT is used only to denote the emptiness of an " +"OGRPoint object." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:131 +msgid "" +"Currently a hack to set nCoordDimension negative is used to denote an " +"empty point." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:134 +msgid "" +"The removal of nCoordinateDimension may imply changes to drivers etc. " +"which get or set it." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:137 +msgid "The tests are" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:144 +msgid "The setters and getters are implemented with \\|= and &=." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:146 +msgid "" +"When any of these flags is set or unset, the corresponding data becomes " +"invalid and may be discarded." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:149 +msgid "" +"Keep the following methods with original semantics, i.e., coordinate " +"dimension is 2 or 3, but deprecate. There is some discrepancy in " +"documentation. Their documentation says that they may return zero for " +"empty points while in ogrpoint.cpp it says that negative nCoordDimension " +"values are used for empty points and the getCoordinateDimension method of" +" point returns absolute value of nCoordDimension - thus not zero. A fix " +"to the doc is probably enough." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:163 +msgid "" +"It is proposed to possibly add a new method to replace " +"getCoordinateDimension. set3D and setMeasured would replace " +"setCoordinateDimension and flattenTo2D. See below." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:167 +msgid "class OGRGeometry:" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:190 +msgid "" +"int CoordinateDimension() should have the new semantics. The method name " +"in simple features documents actually is without prefix get." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:193 +msgid "" +"Whether set3D and setMeasured should affect the children geometries in a " +"collection is an issue. Currently doc for setCoordinateDimension says " +"\"Setting the dimension of a geometry collection will affect the children" +" geometries.\", thus we have already committed to maintaining dimensions " +"of children in collections. It is proposed that set3D and setMeasured " +"either add or strip Z or M values to or from the geometry (including " +"possible children). In general the strategy should be to follow the " +"existing strategy regarding Z (i.e., to strip or add)." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:202 +msgid "" +"Add property double m to class OGRPoint. Add constructor, getters, and " +"setters for it." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:205 +msgid "" +"Add property double \\*padfM to class OGRSimpleCurve. Add constructor, " +"getters, and setters for it. New setters with postfix M are needed for " +"XYM data since the object may be upgraded to XYZ from XY in setters. Add " +"also methods RemoveM() and AddM() with similar semantics as Make3D and " +"Make2D." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:211 +msgid "" +"Override methods set3D and setMeasured in those classes where " +"setCoordinateDimension is overridden." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:214 +msgid "" +"Change the semantics of methods whose name begins with \\_ and have a " +"parameter \"int b3D\". The parameter will be \"int coordinates\", i.e., a" +" flags like int, which tells about Z and M." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:221 +msgid "ogr_core.h:" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:228 +msgid "" +"The current behavior is that calling SetPoint on a geometry with " +"coordinate dimension 2 upgrades the coordinate dimension 3. To keep 2D " +"points 2D SetPoint_2D must be used. Thus we need separate functions for M" +" and ZM geometries. The proposal is to use postfixes M and ZM, i.e., " +"SetPointM, SetPointZM. Similarly for AddPoint." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:234 +msgid "" +"Currently there is no SetPoints_2D function. The doc at pabyZ param at " +"SetPoints comments that \"defaults to NULL for 2D objects\" but that does" +" not seem to be the case. See #6344. If that is fixed as written there, " +"then only SetPointsZM is needed." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:239 +msgid "" +"GetPoint and GetPoints do not have a 2D version, so only \\*ZM version is" +" needed." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:242 +msgid "ogr_api.h:" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:254 +msgid "ogr_p.h (This is public header, so new functions are needed)" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:267 +msgid "pggeometry.h is internal, so we can change the function prototype" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:280 +msgid "Use of padfM requires changes to openfilegdb driver." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:283 +msgid "GEOS, filters, and other issues" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:285 +msgid "" +"When a geometry with measures is sent to GEOS or used as a filter the M " +"coordinate is ignored." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:288 +msgid "" +"LocateAlong and LocateBetween are the only standard methods, which use M " +"but there could be others, which for example get the extent of M. Such " +"are not intended to be added now but they can be added later." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:295 +msgid "" +"The new C API functions need to be exposed through swig. Further changes " +"depend on whether the language bindings are aware of coordinates. At " +"least Python and Perl are." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:299 +msgid "The new geometry types will be included into the i files." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:301 +msgid "" +"Some new setters and getters are needed for M. Is3D, IsMeasured, Set3D " +"and SetMeasured methods should be added. Also OGR_GT_HasM." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:307 +msgid "" +"Drivers that are probably affected by the C++ changes are at least (these" +" use the CoordinateDimension API) pg, mssqlspatial, sqlite, db2, mysql, " +"gml, pgdump, geojson, libkml, gpkg, wasp, gpx, filegdb, vfk, bna, dxf." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:312 +msgid "" +"The now deprecated CoordinateDimension API is proposed to be replaced " +"with calls to \\*3D and \\*Measured." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:315 +msgid "" +"Once the support for M coordinates is in place the driver will advertise " +"the support." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:318 +msgid "" +"Within the work of this RFC the support is built into memory, shape and " +"pg drivers. Support for other drivers are left for further work." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:324 +msgid "There is a minimum requirement and new possibilities." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:326 +msgid "ogrinfo: report measured geom type, report measures" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:328 +msgid "ogr2ogr: support measured geom types" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:330 +msgid "ogrlineref: seems to deal specifically with measures, needs more thought" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:332 +msgid "gdal_rasterize: measure could be used for the burn-in value" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:334 +msgid "gdal_contour: measure could be used as the \"elevation\" value" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:336 +msgid "gdal_grid: measure could be used as the \"Z\" value" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:346 +msgid "" +"At least the initial tests will be done with Perl unit tests " +"(swi/perl/t/measures-\\*.t). Later autotest suite will be extended. " +"Existing tests should not fail." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:353 +msgid "" +"Many drivers (actually datasets and layers) which support measures need " +"to have the support added. Support should be advertised using" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:361 +msgid "" +"The entry point for a creating a layer is CreateLayer method in " +"GDALDataset. If the dataset does not support measured geometries it will " +"strip the measured flag from the geometry type it gets as a parameter. " +"This is in line with current behavior non linear geometry types and " +"datasets not supporting them." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:367 +msgid "" +"ICreateLayer, which all drivers that have create layer capability " +"implement, have geometry type as an argument. The method should call " +"CPLError() with CPLE_NotSupported and return NULL if the driver does not " +"support measures. Similarly for ICreateFeature and ISetFeature." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:372 +msgid "" +"The user-oriented API functions (CreateLayer, CreateFeature, and " +"SetFeature) should (silently) strip out the measures before continuing to" +" the I\\* methods in drivers that do not support measures. This (side " +"effect) may not be what is wanted in some usage scenarios but it would " +"follow the pattern of what is already done with nonlinear geometries. " +"This should be documented." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:379 +msgid "" +"An alternative would be to store M value(s) (or WKT or WKB) as attribute " +"(scalar or vector, depending on the geometry type)." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:382 +msgid "Needs a decision." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:384 +msgid "" +"Some incompatibilities will necessarily be introduced. For example when " +"the current XYM-as-XYZ hack in shape will be replaced by proper XYM." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:390 +msgid "" +"`https://trac.osgeo.org/gdal/ticket/6063 " +"<https://trac.osgeo.org/gdal/ticket/6063>`__ " +"`https://trac.osgeo.org/gdal/ticket/6331 " +"<https://trac.osgeo.org/gdal/ticket/6331>`__" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:396 +msgid "The implementation will be done by Ari Jolma." +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:398 +msgid "" +"The proposed implementation will be in `https://github.com/ajolma/GDAL-" +"XYZM <https://github.com/ajolma/GDAL-XYZM>`__" +msgstr "" + +#: ../../source/development/rfc/rfc61_support_for_measured_geometries.rst:404 +msgid "+1 from Even, Tamas, Jukka and Daniel" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:5 +msgid "RFC 62 : Raster algebra" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:13 +msgid "Implementation in version:" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:18 +msgid "" +"It is proposed that a set of functions or methods are written for raster " +"band objects to support \"raster algebra\", i.e., a set of operations, " +"which modify bands or compute values from bands. An example of a " +"modification is adding a value to all the cells of the band. An example " +"of a computation is the maximum cell value in the band. Operations may or" +" may not take arguments, in addition to the band itself, and if they " +"take, the argument may be a numeric value, a data structure, or another " +"band. Similarly, the computed value may be a simple numeric value, a data" +" structure, or another band." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:31 +msgid "" +"Raster algebra is a well known branch of geospatial science and " +"technology and an often needed tool. Currently GDAL does not have " +"comprehensive support for raster algebra in core." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:36 +msgid "Related work" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:38 +msgid "" +"Python bindings: raster bands or parts of raster bands can be read into /" +" written from numpy array objects. Huge rasters can be iterated block by " +"block. numpy methods allow efficient implementation of many raster " +"algebra methods using python. There is some support for parallel " +"processing using numpy." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:44 +msgid "" +"Perl bindings: raster bands or parts of raster bands can be read into / " +"written from PDL objects. Huge rasters can be iterated block by block. " +"PDL methods allow efficient implementation of many raster algebra methods" +" using perl. There is some support for parallel processing using PDL." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:50 +msgid "" +"QGIS raster calculator: raster calculation string is parsed into an " +"expression tree and output band is computed row by row from the inputs. " +"All computations are done with double precision floating point numbers. " +"The calculation does not support parallel processing." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:55 +msgid "PostGIS raster: raster algebra is supported by callback functions." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:57 +msgid "There is existing research, which may be exploited:" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:59 +msgid "" +"Parallel Priority-Flood depression filling for trillion cell digital " +"elevation models on desktops or clusters " +"`http://www.sciencedirect.com/science/article/pii/S0098300416301704 " +"<http://www.sciencedirect.com/science/article/pii/S0098300416301704>`__" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:63 +msgid "" +"Parallel Non-divergent Flow Accumulation For Trillion Cell Digital " +"Elevation Models On Desktops Or Clusters " +"`https://arxiv.org/abs/1608.04431 <https://arxiv.org/abs/1608.04431>`__" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:68 +msgid "Requirements (Goals)" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:70 +msgid "" +"The implementation should be data type aware. This may mean code written " +"with templates." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:73 +msgid "The implementation should be parallel processing friendly." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:75 +msgid "" +"The implementation should allow a relatively easy to use C++ / C API. " +"This may mean interface, which does not use templates." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:78 +msgid "" +"The implementation should allow arbitrary functions on cell values. I.e.," +" be extensible by the user." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:81 +msgid "" +"The implementation should allow focal methods. I.e., methods, where the " +"value of a cell depends on its neighborhood." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:87 +msgid "" +"The implementation does not need to be tightly integrated with the core. " +"This means an \"add-on\" type solution is ok." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:90 +msgid "" +"GDAL design sets some constraints/requirements to raster algebra " +"implementation: 1) the access to data is based on blocks, 2) GDAL " +"supports several datatypes, even complex values, 3) there is no immediate" +" support for the not-simple data structures needed by some methods (by " +"\"method\" I refer to functions of raster algebra in this text), 4) data " +"can be read from a band in parallel but writing needs to be exclusive." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:104 +msgid "Drivers are not affected." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:109 +msgid "The functionality will be added to the bindings." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:114 +msgid "" +"Existing utilities are not affected but new utilities may be written " +"taking advantage of the new functionality." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:120 +#: ../../source/development/rfc/rfc62_raster_algebra.rst:125 +msgid "Must be written." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:136 +msgid "" +"A proposed implementation is developed at " +"`https://github.com/ajolma/raster_algebra " +"<https://github.com/ajolma/raster_algebra>`__" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:139 +msgid "" +"This code attempts to solve the problem as follows. (The source is in " +"transition from an old approach, which was based on operators as methods," +" while the new approach is based on operator classes)" +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:143 +msgid "" +"Classes 'operand' and 'operator' are defined. An operand is an object, " +"which holds data and an operator is an object, which computes a result " +"(essentially an operand) from operands." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:147 +msgid "" +"Raster algebra computation is a tree of operand and operator objects, " +"which is executed in a recursive fashion." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:150 +msgid "" +"There are interface classes and templated concrete classes. The concrete " +"classes inherit from the interface classes." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:153 +msgid "" +"Two operand classes are defined: a number and a band. There is a need for" +" other types of operands. For example a classifier would map integer " +"values or real number ranges into numbers. Code for such exists in the " +"source but it is not organized to reflect the new approach." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:158 +msgid "" +"A central method is 'compute' in band class, which is basically the " +"effective block loop code presented in the documentation for " +"GDALRasterBand::ReadBlock." +msgstr "" + +#: ../../source/development/rfc/rfc62_raster_algebra.rst:162 +msgid "" +"Multiple data types are supported by template concrete class for bands " +"and by overloaded get_value method, which returns the value in required " +"data type." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:5 +msgid "RFC 63 : Sparse datasets improvements" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:13 +msgid "Version: 2.2" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:18 +msgid "" +"This RFC covers an improvement to manage sparse datasets, that is to say " +"datasets that contain substantial empty regions." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:24 +msgid "" +"There are use cases where one needs to read or generate a dataset that " +"covers a large spatial extent, but in which significant parts are not " +"covered by data. There is no way in the GDAL API to quickly know which " +"areas are covered or not by data, hence requiring to process all pixels, " +"which is rather inefficient. Whereas some formats like GeoTIFF, VRT or " +"GeoPackage can potentially give such an information without processing " +"pixels." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:32 +msgid "" +"It is thus proposed to add a new method GetDataCoverageStatus() in the " +"GDALRasterBand class, that takes as input a window of interest and " +"returns whether it is made of data, empty blocks or a mix of them." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:36 +msgid "" +"This method will be used by the GDALDatasetCopyWholeRaster() method (used" +" by CreateCopy() / gdal_translate) to avoid processing sparse regions " +"when the output driver instructs it to do so." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:43 +msgid "In GDALRasterBand class, a new virtual method is added :" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:128 +msgid "" +"This method has a dumb default implementation that returns " +"GDAL_DATA_COVERAGE_STATUS_UNIMPLEMENTED \\| " +"GDAL_DATA_COVERAGE_STATUS_DATA" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:132 +msgid "The public API is made of :" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:173 +msgid "" +"GDALRasterBand::GetDataCoverageStatus() does basic checks on the validity" +" of the window before calling IGetDataCoverageStatus()" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:179 +msgid "" +"GDALDatasetCopyWholeRaster() and GDALRasterBandCopyWholeRaster() accepts " +"a SKIP_HOLES option that can be set to YES by the output driver to cause " +"GetDataCoverageStatus() to be called on each chunk of the source dataset " +"to determine if contains only holes or not." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:187 +msgid "" +"This RFC upgrades the GeoTIFF and VRT drivers to implement the " +"IGetDataCoverageStatus() method." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:190 +msgid "" +"The GeoTIFF driver has also receive a number of prior enhancements, " +"related to that topic, for example to accept the SPARSE_OK=YES creation " +"option in CreateCopy() mode (or the SPARSE_OK open option in update " +"mode)." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:195 +msgid "Extract of the documentation of the driver:" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:238 +msgid "" +"The Python bindings has a mapping of GDALGetDataCoverageStatus(). Other " +"bindings could be updated (need to figure out how to return both a status" +" flag and a percentage)" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:245 +msgid "No direct changes in utilities." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:248 +msgid "Results" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:250 +msgid "" +"With this new capability, a VRT of size 200 000 x 200 000 pixels that " +"contains 2 regions of 20x20 pixels each can be gdal_translated as a " +"sparse tiled GeoTIFF in 2 seconds. The resulting GeoTIFF can be itself " +"translated into another sparse tiled GeoTIFF in the same time." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:256 +msgid "Future work" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:258 +msgid "" +"Future work using the new capability could be done in overview building " +"or warping. Other drivers could also benefit from that new capability: " +"GeoPackage, ERDAS Imagine, ..." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:265 +msgid "The new method is documented." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:270 +msgid "" +"Tests of the VRT and GeoTIFF drivers are enhanced to test their " +"IGetDataCoverageStatus() implementation." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:276 +msgid "C++ ABI change. No functional incompatibility foreseen." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:281 +msgid "The implementation will be done by Even Rouault." +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:283 +msgid "" +"The proposed implementation is in " +"`https://github.com/rouault/gdal2/tree/sparse_datasets " +"<https://github.com/rouault/gdal2/tree/sparse_datasets>`__" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:286 +msgid "" +"Changes can be seen with " +"`https://github.com/OSGeo/gdal/compare/trunk...rouault:sparse_datasets?expand=1" +" " +"<https://github.com/OSGeo/gdal/compare/trunk...rouault:sparse_datasets?expand=1>`__" +msgstr "" + +#: ../../source/development/rfc/rfc63_sparse_datasets_improvements.rst:292 +msgid "+1 from EvenR and DanielM" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:5 +msgid "RFC 64: Triangle, Polyhedral surface and TIN" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:7 +msgid "Authors: Avyav Kumar Singh, Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:9 +msgid "Contact: avyavkumar at gmail dot com, even.rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:13 +msgid "Implementation version: GDAL 2.2" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:18 +msgid "" +"As of now, the :cpp:class:`OGRGeometry` class (the base class from which " +"all the subtypes are derived) is limited to OGRCompoundCurve, " +"OGRCircularString, OGRLinearRing, OGRMultiLineString, OGRMultiPoint, " +"OGRMultiPolygon, OGRMultiCurve, OGRSimpleCurve, OGRCurvePolygon and " +"OGRPolygon." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:24 +msgid "" +"This RFC addresses the addition of the following new geometries in " +"OGRGeometry:" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:27 +msgid "" +"Triangle - A subset of polygons, the fundamental difference is that it is" +" made of 3 nodes only (actually 4, with the last one being the repetition" +" of the first one) and ONLY ONE exterior boundary and NO interior " +"polygons." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:31 +msgid "PolyhedralSurface - A 3D figure made exclusively of Polygons." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:32 +msgid "" +"TriangulatedSurface - A subset of PolyhedralSurface; a 3D figure which " +"consists exclusively of Triangles." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:41 +msgid "" +"`BNF of WKT encoding <https://github.com/postgis/postgis/blob/master/doc" +"/bnf-wkt.txt>`__: extracted from SQL/MM Part 3" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:44 +msgid "" +"`BNF of WKB encoding <https://github.com/postgis/postgis/blob/master/doc" +"/bnf-wkb.txt>`__: extracted from SQL/MM Part 3" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:56 +msgid "" +"Some prelimenary work had already been done prior to this proposal, such " +"as including the necessary WKB codes in <ogr_core.h>." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:59 +msgid "" +"Additionally, the `SFCGAL <http://www.sfcgal.org/>`__ library is a new " +"optional dependency of GDAL (build support only done for Unix for now). " +"The minimum version tested to build is 1.2.2 (as found in Ubuntu 16.04). " +"As mentioned in its home page, \"SFCGAL is a C++ wrapper library around " +"CGAL with the aim of supporting ISO 19107:2013 and OGC Simple Features " +"Access 1.2 for 3D operations.\" It is mostly used as a potential geometry" +" backend by PostGIS. It has a C API, that is the one we use." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:67 +msgid "" +"SFCGAL functions may be used by methods of OGRGeometry (currently " +"IsValid(), Distance(), ConvexHull(), Intersection(), Union(), " +"Difference(), SymDifference(), Crosses()), as soon as one of the geometry" +" operands is a Triangle, PolyhedralSurface or TIN." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:72 +msgid "" +"Two new OGRGeometry methods are used to convert SFCGAL geometries <-> OGR" +" geometries." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:80 +msgid "" +"Besides SFCGAL, GEOS methods are still used in some cases, but with the " +"following limitations - a Triangle is converted to a Polygon with one " +"exterior ring; Polyhedral Surfaces and Triangulated Surfaces are " +"converted to geometry collection of polygons. (each Triangle in a " +"Triangulated Surface is converted to a Polygon as described previously)" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:86 +msgid "The API for the new geometries introduced includes -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:88 +msgid "" +"Overwriting existing methods for Polygon in the case of Triangle API. A " +"complete API is provided below -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:129 +msgid "" +"The PolyhedralSurface API is derived from OGRSurface. Internally, it uses" +" an OGRMultiPolygon to store all the Polygons comprising the Polyhedral " +"Surface. Most of the implementations of the methods just reference " +"corresponding OGRMultiPolygon methods with checks to ensure that " +"conditions are maintained." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:200 +msgid "" +"The Triangulated Surface API is similar to Polyhedral Surface, and the " +"MultiPolygon class was tweaked slightly to include methods to run which " +"consisted of subgeometries of the form Triangle. (A MultiPolygon is " +"strictly a collection of Polygons). These methods are internal to " +"OGRMultiPolygon and cannot be accessed by a public user. For instance, " +"the ``OGRMultiPolygon::addGeometryDirectly`` method has a check that the " +"subgeometry added to it should be of the type POLYGON. Rather than mess " +"around with the existing function, a new function has been written which " +"does not implement this check -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:247 +msgid "The Triangulated Surface API is as follows -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:281 +msgid "The new geometry WKB values can be seen as below -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:284 +msgid "Geometry Type" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:284 +msgid "2D" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:284 +msgid "Z" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:284 +msgid "M" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:284 +msgid "ZM" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:286 +msgid "PolyhedralSurface" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:286 +msgid "0015" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:286 +msgid "1015" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:286 +msgid "2015" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:286 +msgid "3015" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:287 +msgid "TIN" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:287 +msgid "0016" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:287 +msgid "1016" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:287 +msgid "2016" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:287 +msgid "3016" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:288 +msgid "Triangle" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:288 +msgid "0017" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:288 +msgid "1017" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:288 +msgid "2017" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:288 +msgid "3017" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:292 +msgid "Geometry conversions" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:294 +msgid "" +"The OGRGeometryFactory::forceTo() and forceToMultiPolygon() methods have " +"been enhanced to support conversions between the new geometry types, and " +"towards multipolygon. Note that converting a TIN or a PolyhedralSurface " +"into a MultiPolygon is semantically incorrect since a MultiPolygon is " +"suppose to contain geometries in the same plane, but it might help when " +"converting those new geometry types into a format that doesn't support " +"them (and such conversion was for example implicitly done in the reading " +"side of the shapefile driver previously)" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:307 +msgid "PostGIS" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:309 +msgid "" +"No changes done to the driver explicitly, but it has been ensured that PG" +" <-> OGR compatibility has been maintained. PostGIS 3D functions work on " +"OGR, simple scripts work, for example from ``autotest/ogr/ogr_pg.py``, we" +" have -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:324 +msgid "ShapeFile" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:326 +msgid "" +"Shapefiles have the concept of a \"MultiPatch\" object. The MultiPatch " +"can be made of several parts, which are" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:329 +msgid "" +"A TriangleStrip is a linked strip of triangles, where every vertex (after" +" the first two) completes a new triangle. A new triangle is always formed" +" by connecting the new vertex with its two immediate predecessors." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:333 +msgid "" +"A TriangleFan is a linked fan of triangles, where every vertex (after the" +" first two) completes a new triangle. A new triangle is always formed by " +"connecting the new vertex with its immediate predecessor and the first " +"vertex of the part." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:337 +msgid "" +"Rings (outer ring, inner ring, first ring, \"non-typed\" ring) Up to now " +"multipatch were read as MultiPolygon. Now, in general, a " +"GeometryCollection will be returned, with zero or several TIN " +"corresponding to the TriangleStrip/TriangleFan and zero or one " +"MultiPolygon with all the rings. If there's only one TIN or one " +"MultiPolygon, it will be returned as a top-level geometry. The layer type" +" will be Unknown On writing, the SHPT layer creation option is extended " +"to recognize the MULTIPATCH value, and the current logic to guess the " +"shape type from the layer geometry type or the geometry type of the first" +" feature is extended to support MULTIPATCH. On a MULTIPATCH layer, " +"geometries of type TIN, POLYHEDRALSURFACE, MULTIPOLYGON or " +"GEOMETRYCOLLECTION (whose subgeometries are on of the 3 previous types) " +"are accepted and converted to a MultiPatch object, trying to use " +"TriangleStrip and TriangleFan if the triangles are in the expected order." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:354 +msgid "FileGDB, OpenFileGDB" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:356 +msgid "" +"The FileGDB format support the MultiPatch object as well, with one " +"extension. There is a new type of part, which is made of several " +"triangles whose organization is not TriangleStrip or TriangleFan. Both " +"drivers have been upgraded to work like the ShapeFile driver on the " +"reading side. On the writing side, the FileGDB driver will automatically " +"write a MultiPatch if the layer geometry type is TIN or " +"PolyhedralSurface. The layer option that existed before " +"CREATE_MULTIPATCH=YES can still be used to force writing as MultiPatch" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:366 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:69 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:480 +msgid "GML" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:368 +msgid "" +"The GML driver has been modified for both input and output -> Triangle, " +"PolyhedralSurface and TriangulatedSurface are capable of being " +"read/written from/to a GML document. Sample examples include -" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:417 +msgid "" +"Note that on the writing side those geometries are only generated for a " +"GML 3 output." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:421 +msgid "DXF" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:423 +msgid "" +"The changes in the DXF driver include converting a PolyFaceMesh (a " +"subtype of PolyLine) to PolyhedralSurface. This is illustrated by a bug " +"on the GDAL trac - `https://trac.osgeo.org/gdal/ticket/6246 " +"<https://trac.osgeo.org/gdal/ticket/6246>`__. A PolyFace Mesh consists of" +" points defined initially using specific codes, then these points are " +"described as part of a polygon (a polygon can have four points at the " +"maximum). Reading the PolyFace Mesh is supported in OGR as of now, but " +"write support for it as well (though not implemented by me in this " +"changeset) should be possible as well now." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:436 +msgid "" +"The GeoPackage specification supports [Multi]Point, [Multi]LineString, " +"[Multi]Polygon and GeometryCollection in its core. Curve geometry types " +"are mentioned as a registered extension. But Triangle, PolyhedralSurface " +"or TIN are not mentioned at all. However the GeoPackage geometry blob " +"format being based on ISO WKB, support for the new geometry types did not" +" really require new code. Hence we have kepts this possibility of " +"reading/writing the 3 new geometry types, but with a warning emitted that" +" a non-standard extension will be used on the writing side." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:447 +msgid "Other drivers" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:449 +msgid "" +"The CSV, VRT, PGDump, SQLite (but not Spatialite) drivers support the new" +" geometry types. A couple of drivers have been modified, so as not to " +"crash on the writing side when being provided with the new geometry " +"types. Besides the previously mentioned drivers, the following drivers " +"have been verified to not crash (but potentially error out, or skip " +"unrecognized geometries): MySQL, OCI, KML, LIBKML, GeoJSON, MapInfo" +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:459 +msgid "Using standard Doxygen documentation procedure." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:464 +msgid "" +"Many applications will not be able to properly deal with the new geometry" +" types that may now be returned by some drivers. In GDAL 2.1, the new " +"types were introduced mentioning that they might be returned by GDAL in " +"the future. Code should either skip the new geometries, deal with them " +"properly or use the OGR_G_ForceTo() function to convert to a geometry " +"type it supports." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:474 +msgid "" +"Very few changes have been made so that the existing autotest suite still" +" passes. New geometry classes and conversion methods has been added to " +"ogr_geom.py and ogr_gml_geom.py. Updated drivers have received new tests " +"also." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:482 +msgid "" +"Done by Avyav Kumar Singh, under the Google Summer of Code 2016 program, " +"and fine tuned / extended / integrated by Even Rouault." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:485 +msgid "" +"The proposed implementation lies in the \"gsoc-triangle-ps-tin-rebased\" " +"branch of the `https://github.com/rouault/gdal2/tree/gsoc-triangle-ps-" +"tin-rebased <https://github.com/rouault/gdal2/tree/gsoc-triangle-ps-tin-" +"rebased>`__ repository." +msgstr "" + +#: ../../source/development/rfc/rfc64_triangle_polyhedralsurface_tin.rst:493 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:203 +msgid "+1 from JukkaR, DanielM, HowardB and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:5 +msgid "RFC 65: RFC 7946 GeoJSON" +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:13 +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:13 +msgid "Implementation version: 2.2" +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:18 +msgid "" +"GeoJSON has been standardized by the IETF: `RFC 7946 " +"<https://tools.ietf.org/html/rfc7946>`__. Updates to the OGR GeoJSON " +"driver are needed so that it may write RFC 7946 GeoJSON." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:25 +msgid "" +"The RFC 7946 standard is backwards compatible with the legacy definition " +"of GeoJSON, but has a few differences (see " +"`https://tools.ietf.org/html/rfc7946#appendix-B " +"<https://tools.ietf.org/html/rfc7946#appendix-B>`__). For OGR, the most " +"significant are: removal of \"crs\" (CRS84 only), counter-clockwise " +"winding of polygons, geometry splitting at the antimeridian, and " +"representation of bounding boxes at the antimeridian and poles. Note: RFC" +" 7946 explicitly restricts to 2D and 3D coordinates, and forbid use of " +"the M dimension for example. This was already the case in the existing " +"driver for the GeoJSON 2008 output." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:35 +msgid "" +"Consensus on the gdal-dev list is that developers should be able to " +"require RFC 7946 GeoJSON by configuring layer creation with an option and" +" that it be an all-or-nothing switch." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:42 +msgid "" +"A layer creation option will be added for the GeoJSON driver, e.g., " +"``RFC7946=TRUE``. When \"on\", OGR will write GeoJSON with CRS84 " +"coordinates (reprojecting as needed) with 7 places of precision by " +"default, polygons wound properly, and geometries split at the " +"antimeridian." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:48 +msgid "" +"Related to that work, the OGRGeometryFactory::transformWithOptions() " +"method has been improved to better deal with reprojection of geometries " +"from polar projections, and projections that span the antimeridian, to " +"EPSG:4326" +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:66 +msgid "Utilities will implement RFC 7946 by using the layer creation option." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:71 +msgid "Documentation of the new layer creation option will reference RFC 7946." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:76 +msgid "The ogr_geojson.py file tests the effect of the new option." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:81 +msgid "" +"As this is a opt-in parameter, no backward compatibility issue. GeoJSON " +"files conformant to RFC 7646 can be read by previous GDAL/OGR versions." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:87 +msgid "#6705" +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:92 +msgid "Implementation has been done by Even Rouault and sponsored by Mapbox." +msgstr "" + +#: ../../source/development/rfc/rfc65_rfc7946_geojson.rst:97 +msgid "+1 from JukkaR, HowardB, DanielM and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:5 +msgid "RFC 66 : OGR random layer read/write capabilities" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:11 +msgid "Status: Implemented" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:13 +msgid "Implementing version: 2.2" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:18 +msgid "" +"This RFC introduces a new API to be able to iterate over vector features " +"at dataset level, in addition to the existing capability of doing it at " +"the layer level. The existing capability of writing features in layers in" +" random order, that is supported by most drivers with output " +"capabilities, is formalized with a new dataset capability flag." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:27 +msgid "" +"Some vector formats mix features that belong to different layers in an " +"interleaved way, which make the current feature iteration per layer " +"rather inefficient (this requires for each layer to read the whole file)." +" One example of such drivers is the OSM driver. For this driver, a hack " +"had been developed in the past to be able to use the " +"OGRLayer::GetNextFeature() method, but with a really particular " +"semantics. See \"Interleaved reading\" paragraph of :ref:`vector.osm` for" +" more details. A similar need arises with the development of a new " +"driver, GMLAS (for GML Application Schemas), that reads GML files with " +"arbitrary element nesting, and thus can return them in a apparent random " +"order, because it works in a streaming way. For example, let's consider " +"the following simplified XML content :" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:50 +msgid "" +"The driver will be first able to complete the building of feature B " +"before emitting feature A. So when reading sequences of this pattern, the" +" driver will emit features in the order B,A,B,A,..." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:60 +msgid "Two new methods are added at the GDALDataset level :" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:62 +msgid "GetNextFeature():" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:115 +msgid "and ResetReading():" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:134 +msgid "New capabilities" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:136 +msgid "The following 2 new dataset capabilities are added :" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:146 +msgid "The above 2 new methods are available in the C API with :" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:159 +msgid "Discussion about a few design choices of the new API" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:161 +msgid "" +"Compared to OGRLayer::GetNextFeature(), GDALDataset::GetNextFeature() has" +" a few differences :" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:164 +msgid "" +"it returns the layer which the feature belongs to. Indeed, there's no " +"easy way from a feature to know which layer it belongs too (since in the " +"data model, features can exist outside of any layer). One possibility " +"would be to correlate the OGRFeatureDefn\\* object of the feature with " +"the one of the layer, but that is a bit inconvenient to do (and " +"theoretically, one could imagine several layers sharing the same feature " +"definition object, although this probably never happen in any in-tree " +"driver)." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:172 +msgid "" +"even if the feature returned is not NULL, the returned layer might be " +"NULL. This is just a provision for now, since that cannot currently " +"happen. This could be interesting to address schema-less datasources " +"where basically each feature could have a different schema (GeoJSON for " +"example) without really belonging to a clearly identified layer." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:177 +msgid "" +"it returns a progress percentage. When using OGRLayer API, one has to " +"count the number of features returned with the total number returned by " +"GetFeatureCount(). For the use cases we want to address knowing quickly " +"the total number of features of the dataset is not doable. But knowing " +"the position of the file pointer regarding the total size of the size is " +"easy. Hence the decision to make GetNextFeature() return the progress " +"percentage. Regarding the choice of the range [0,1], this is to be " +"consistent with the range accepted by GDAL progress functions." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:186 +#, python-format +msgid "" +"it accepts a progress and cancellation callback. One could wonder why " +"this is needed given that GetNextFeature() is an \"elementary\" method " +"and that it can already returns the progress percentage. However, in some" +" circumstances, it might take a rather long time to complete a " +"GetNextFeature() call. For example in the case of the OSM driver, as an " +"optimization you can ask the driver to return features of a subset of " +"layers. For example all layers except nodes. But generally the nodes are " +"at the beginning of the file, so before you get the first feature, you " +"have typically to process 70% of the whole file. In the GMLAS driver, the" +" first GetNextFeature() call is also the opportunity to do a preliminary " +"quick scan of the file to determine the SRS of geometry columns, hence " +"having progress feedback is welcome." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:199 +msgid "" +"The progress percentage output is redundant with the progress callback " +"mechanism, and the latter could be used to get the former, however it may" +" be a bit convoluted. It would require doing things like:" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:216 +msgid "" +"GDALDatasetGetNextFeature is mapped as gdal::Dataset::GetNextFeature() " +"and GDALDatasetResetReading as gdal::Dataset::ResetReading()." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:219 +msgid "" +"Regarding gdal::Dataset::GetNextFeature(), currently only Python has been" +" modified to return both the feature and its belonging layer. Other " +"bindings just return the feature for now (would need specialized " +"typemaps)" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:227 +msgid "The OSM and GMLAS driver are updated to implement the new API." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:229 +msgid "" +"Existing drivers that support ODsCRandomLayerWrite are updated to " +"advertise it (that is most drivers that have layer creation capabilities," +" with the exceptions of KML, JML and GeoJSON)." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:236 +msgid "" +"ogr2ogr / GDALVectorTranslate() is changed internally to remove the hack " +"that was used for the OSM driver to use the new API, when " +"ODsCRandomLayerRead is advertized. It checks if the output driver " +"advertises ODsCRandomLayerWrite, and if it does not, emit a warning, but " +"still goes on proceeding with the conversion using random layer " +"reading/writing." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:243 +msgid "" +"ogrinfo is extended to accept a -rl (for random layer) flag that " +"instructs it to use the GDALDataset::GetNextFeature() API. It was " +"considered to use it automatically when ODsCRandomLayerRead was " +"advertized, but the output can be quite... random and thus not very " +"practical for the user." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:257 +msgid "" +"The specialized GetNextFeature() implementation of the OSM and GMLAS " +"driver is tested in their respective tests. The default implementation of" +" GDALDataset::GetNextFeature() is tested in the MEM driver tests." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:264 +msgid "None for existing users of the C/C++ API." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:266 +msgid "" +"Since there is a default implementation, the new functions/methods can be" +" safely used on drivers that don't have a specialized implementation." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:269 +msgid "" +"The addition of the new virtual methods GDALDataset::ResetReading() and " +"GDALDataset::GetNextFeature() may cause issues for out-of-tree drivers " +"that would already use internally such method names, but with different " +"semantics, or signatures. We have encountered such issues with a few in-" +"tree drivers, and fixed them." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:278 +msgid "" +"The implementation will be done by Even Rouault, and is mostly triggered " +"by the needs of the new GMLAS driver (initial development funded by the " +"European Earth observation programme Copernicus)." +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:282 +msgid "" +"The proposed implementation is in " +"`https://github.com/rouault/gdal2/tree/gmlas_randomreadwrite " +"<https://github.com/rouault/gdal2/tree/gmlas_randomreadwrite>`__ (commit:" +" " +"`https://github.com/rouault/gdal2/commit/8447606d68b9fac571aa4d381181ecfffed6d72c" +" " +"<https://github.com/rouault/gdal2/commit/8447606d68b9fac571aa4d381181ecfffed6d72c>`__)" +msgstr "" + +#: ../../source/development/rfc/rfc66_randomlayerreadwrite.rst:290 +msgid "+1 from TamasS, HowardB, JukkaR, DanielM and EvenR." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:5 +msgid "RFC 67 : Null values in OGR" +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:18 +msgid "" +"This RFC implement the concept of null value for the field of a feature, " +"in addition to the existing unset status." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:24 +msgid "" +"Currently, OGR supports one single concept to indicate that a field value" +" is missing : the concept of unset field." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:27 +msgid "" +"So assuming a JSON feature collection with 2 features would properties " +"would be { \"foo\": \"bar\" } and { \"foo\": \"bar\", \"other_field\": " +"null }, OGR currently returns that the other_field is unset in both " +"cases." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:31 +msgid "" +"What is proposed here is that in the first case where the \"other_field\"" +" keyword is totally absent, we use the current unset field concept. And " +"for the other case, we add a new concept of null field." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:35 +msgid "" +"This distinction between both concepts apply to all GeoJSON based formats" +" and protocols, so GeoJSON, ElasticSearch, MongoDB, CouchDB, Cloudant." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:39 +msgid "" +"This also applies for GML where the semantics of a missing element would " +"be mapped to unset field and an element with a xsi:nil=\"true\" attribute" +" would be mapped to a null field." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:47 +msgid "OGRField" +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:49 +msgid "" +"The Set structure in the \"raw field\" union is modified to add a third " +"marker" +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:60 +msgid "" +"This is not strictly related to this work but the 3rd marker decreases " +"the likelihood of a genuine value to be misinterpreted as unset / null. " +"This does not increase the size of the structure that is already at least" +" 12 bytes large." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:65 +msgid "" +"The current special value of OGRUnsetMarker = -21121 will be set in the 3" +" markers for unset field (currently set to the first 2 markers)." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:68 +msgid "" +"Similarly for the new Null state, the new value OGRNullMarker = -21122 " +"will be set to the 3 markers." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:74 +msgid "" +"The methods int IsFieldNull( int nFieldIdx ) and void SetNullField ( int " +"nFieldIdx ) are added." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:77 +msgid "" +"The accessors GetFieldXXXX() are modified to take into account the null " +"case, in the same way as if they are called on a unset field, so " +"returning 0 for numeric field types, empty string for string fields, " +"FALSE for date time fields and NULL for list-based types." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:82 +msgid "" +"A convenience method OGRFeature::IsFieldSetAndNotNull() is added to ease " +"the porting of existing code that used previously IsFieldSet() and " +"doesn't need to distinguish between the unset and null states." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:99 +msgid "" +"Lower-level functions will be added to manipulate directly the raw field " +"union (for use mostly in core and a few drivers), instead of directly " +"testing/ setting the markers :" +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:113 +msgid "The new methods will mapped to SWIG." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:118 +msgid "" +"The following drivers will be modified to take into account the unset and" +" NULL state as distinct states: GeoJSON, ElasticSearch, MongoDB, CouchDB," +" Cloudant, GML, GMLAS, WFS." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:122 +msgid "" +"Note: regarding the GMLAS driver, the previous behavior to have both xxxx" +" and xxxx_nil fields when xxxx is an optional nillable XML elements is " +"preserved by default (can be changed through a configuration setting in " +"the gmlasconf.xml file). The rationale is that the GMLAS driver is mostly" +" used to convert to SQL capable formats that cannot distinguish between " +"the unset and null states, hence the need for the 2 dedicated fields." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:130 +msgid "" +"The CSV driver will be modified so that when EMPTY_STRING_AS_NULL open " +"option is specified, the new Null state is used." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:133 +msgid "" +"All drivers that in their writing part test if the source feature has a " +"field unset will also test if the field is null." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:136 +msgid "" +"For SQL based drivers (PG, PGDump, Carto, MySQL, OCI, SQLite, GPKG), on " +"reading a SQL NULL value will be mapped to the new Null state. On " +"writing, a unset field will not be mentioned in the corresponding INSERT " +"or UPDATE statement. Whereas a Null field will be mentioned and set to " +"NULL. On insertion, there will generally be no difference of behavior, " +"unless a default value is defined on the field, in which case it will be " +"used by the database engine to set the value in the unset case. On " +"update, a unset field will not see its content updated by the database, " +"where as a field set to NULL will be updated to NULL." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:149 +msgid "" +"No direct changes, but as the OGRFeature::DumpReadable() method is " +"modified so that unset fields of features are no longer displayed, the " +"output of ogrinfo will be affected." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:161 +msgid "Core changes and updated drivers will be tested." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:166 +msgid "" +"All code, in GDAL source code, and in calling external code, that " +"currently uses OGRFeature::IsFieldSet() / OGR_F_IsFieldSet() should also " +"be updated to used IsFieldNull() / OGR_F_IsFieldNull(), either to act " +"exactly as in the unset case, or add a new appropriate behavior. A " +"convenience method and function OGRFeature::IsFieldSetAndNotNull() / " +"OGR_F_IsFieldSetAndNotNull() is added to ease the porting of existing " +"code." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:174 +msgid "" +"Failure to do so, the existing code will see 0 for numeric field types, " +"empty string for string fields, FALSE for date time fields and NULL for " +"list-based types." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:178 +msgid "" +"On the write side, for the GeoJSON driver, in GDAL 2.1 or before, a unset" +" field was written as field_name: null. Starting with GDAL 2.2, only " +"fields explicitly set as null with OGR_F_SetFieldNull() will be written " +"with a null value. Unset fields of a feature will not be present in the " +"corresponding JSON feature element." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:184 +msgid "MIGRATION_GUIDE.TXT is updated to discuss those compatibility issues." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:194 +msgid "" +"The implementation will be done by Even Rouault (Spatialys) and be " +"sponsored by Safe Software." +msgstr "" + +#: ../../source/development/rfc/rfc67_nullfieldvalues.rst:197 +msgid "" +"The proposed implementation is available in " +"`https://github.com/rouault/gdal2/tree/rfc67 " +"<https://github.com/rouault/gdal2/tree/rfc67>`__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:5 +msgid "RFC 68: C++11 Compilation Mode" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:8 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:11 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:8 +#: ../../source/development/rfc/rfc71_github_migration.rst:8 +#: ../../source/development/rfc/rfc72_pytest.rst:8 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:8 +#: ../../source/development/rfc/rfc74_sphinx.rst:8 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:8 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:8 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:8 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:8 +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:8 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:8 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:8 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:8 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:8 +#: ../../source/development/rfc/rfc87_signed_int8.rst:8 +#: ../../source/development/rfc/rfc88_googletest.rst:8 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:8 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:8 +#: ../../source/development/rfc/rfc91_dataset_close.rst:8 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:8 +#: ../../source/development/rfc/rfc93_update_feature.rst:8 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:8 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:8 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:8 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:8 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:7 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:8 +msgid "Author:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:8 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:11 +msgid "Kurt Schwehr" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:9 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:12 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:14 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:9 +#: ../../source/development/rfc/rfc71_github_migration.rst:9 +#: ../../source/development/rfc/rfc72_pytest.rst:9 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:9 +#: ../../source/development/rfc/rfc74_sphinx.rst:10 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:9 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:9 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:9 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:9 +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:9 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:9 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:9 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:9 +#: ../../source/development/rfc/rfc84_cmake.rst:10 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:9 +#: ../../source/development/rfc/rfc87_signed_int8.rst:9 +#: ../../source/development/rfc/rfc88_googletest.rst:9 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:9 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:9 +#: ../../source/development/rfc/rfc91_dataset_close.rst:9 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:9 +#: ../../source/development/rfc/rfc93_update_feature.rst:9 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:9 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:9 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:9 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:9 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:8 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:9 +msgid "Contact:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:9 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:12 +msgid "schwehr@google.com / schwehr@gmail.com" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:10 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:15 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:10 +#: ../../source/development/rfc/rfc71_github_migration.rst:10 +#: ../../source/development/rfc/rfc72_pytest.rst:10 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:10 +#: ../../source/development/rfc/rfc74_sphinx.rst:11 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:10 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:10 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:10 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:10 +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:10 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:10 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:10 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:10 +#: ../../source/development/rfc/rfc84_cmake.rst:13 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:10 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:10 +#: ../../source/development/rfc/rfc87_signed_int8.rst:10 +#: ../../source/development/rfc/rfc88_googletest.rst:10 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:10 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:10 +#: ../../source/development/rfc/rfc91_dataset_close.rst:10 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:10 +#: ../../source/development/rfc/rfc93_update_feature.rst:10 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:10 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:10 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:10 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:10 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:9 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:10 +msgid "Started:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:10 +msgid "2017-Apr-11" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:11 +msgid "Passed:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:11 +msgid "2017-Sep-11" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:12 +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:16 +#: ../../source/development/rfc/rfc70_output_format_guess.rst:11 +#: ../../source/development/rfc/rfc71_github_migration.rst:11 +#: ../../source/development/rfc/rfc72_pytest.rst:11 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:12 +#: ../../source/development/rfc/rfc74_sphinx.rst:12 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:12 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:12 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:12 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:12 +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:12 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:12 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:12 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:11 +#: ../../source/development/rfc/rfc84_cmake.rst:15 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:11 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:12 +#: ../../source/development/rfc/rfc87_signed_int8.rst:11 +#: ../../source/development/rfc/rfc88_googletest.rst:11 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:11 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:11 +#: ../../source/development/rfc/rfc91_dataset_close.rst:11 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:11 +#: ../../source/development/rfc/rfc93_update_feature.rst:11 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:11 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:11 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:11 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:11 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:10 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:11 +msgid "Status:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:12 +msgid "Adopted, implemented in GDAL 2.3" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:15 +msgid "" +"This RFC is based on `GEOS RFC 5 " +"<http://trac.osgeo.org/geos/wiki/RFC5>`__ by Mateusz Łoskot." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:21 +msgid "" +"The document proposes to switch to `C++11 " +"<http://en.wikipedia.org/wiki/C%2B%2B11>`__ compilation mode as default " +"throughout the whole C++ source code of GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:25 +msgid "" +"The goal of the document is to request and achieve agreement on using " +"C++11 as the minimum required version of the C++ programming language " +"standard." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:32 +msgid "" +"C++11 is the first major update of the C++ standard since 1998. (`C++03 " +"<https://en.wikipedia.org/wiki/C%2B%2B03>`__ was a bug fix release.)" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:36 +msgid "" +"Having fewer versions of C++ to support will reduce the load on " +"developers and testing systems." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:39 +msgid "" +"C++11 features aim to promote writing clean, compact, type-safe and fast " +"code. It also delivers better feature-wise compatibility with the C " +"language (C99)." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:43 +msgid "" +"The Wikipedia article at `http://en.wikipedia.org/wiki/C++11 " +"<http://en.wikipedia.org/wiki/C++11>`__ does a great job describing all " +"changes in C++11 extensively." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:47 +msgid "" +"The ``std::auto_ptr`` smart pointer, together with a bunch of other " +"features, were deprecated and will be removed from C++17. Features like " +"``std::unique_ptr`` provide much stronger replacements." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:51 +msgid "" +"Enabling C++11 compilation mode will improve the programming environment " +"making it much friendlier than C++98." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:54 +msgid "" +"A social factor: since (many) C++ programmers no longer enjoy C++98, " +"allowing C++11 mode may increase potential for new contributions." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:58 +msgid "Compilers Landscape" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:60 +msgid "" +"Summary of compilers supported by GDAL with their minimal versions " +"required to compile source code based on" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:63 +msgid "" +"`http://en.cppreference.com/w/cpp/compiler_support " +"<http://en.cppreference.com/w/cpp/compiler_support>`__ C++11 features." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:67 +msgid "C++11" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:70 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:82 +msgid "GCC" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:70 +msgid "4.8.1+" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:70 +msgid "`C++11 status <https://gcc.gnu.org/projects/cxx-status.html#cxx11>`__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:70 +msgid "" +"Debian 8 (stable), Ubuntu 15.04+, Ubuntu 14.04 ``ppa:ubuntu-" +"toolchain-r/test``, Fedora 19+, RHEL7" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:72 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:84 +msgid "Clang" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:72 +msgid "3.3+" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:72 +msgid "`C++11 status <https://clang.llvm.org/cxx_status.html#cxx11>`__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:72 +msgid "Debian 8 (stable), Ubuntu 14.04+, Fedora 19+, CentOS 6(?)" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:73 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:85 +msgid "MSVC" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:73 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:85 +msgid "14.0+ (2015)" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:73 +msgid "`C++11 status <https://msdn.microsoft.com/en-us/library/hh567368.aspx>`__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:73 +msgid "n/a" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:77 +#: ../../source/development/rfc/rfc68_cplusplus11.rst:140 +msgid "C++14" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:79 +msgid "The C++14 compilers are listed for comparison only:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:82 +msgid "4.9+" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:84 +msgid "3.4+" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:89 +msgid "Plan" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:91 +msgid "" +"This proposal only requests agreement for the C++11 compilation mode " +"switch in the current ``trunk`` branch only." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:94 +msgid "" +"This proposal does not suggest any detailed roadmap of large refactoring " +"of the GDAL C++ codebase." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:97 +msgid "" +"The GDAL codebase is > 1.3M LOC and given the available man-power to LOCs" +" ratio, such one-step refactoring would not be feasible." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:100 +msgid "" +"Instead, the task will be tackled with the baby step approach gradually " +"transforming the codebase according to priorities set along the way. Any " +"disruptive refactoring, changes in interfaces of C++ classes, breaking " +"changes in C++ API must be announced and discussed on the mailing list or" +" the bug tracker." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:106 +msgid "" +"*IMPORTANT*: C++11 refactoring must not change the C API or break C API " +"compatibility, unless agreed upon based on prior RFC proposed." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:109 +msgid "" +"However, if the proposal is accepted, any new C++ code written for GDAL " +"must be C++11-compliant." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:112 +msgid "" +"Prior acceptance of this proposal is necessary in order to start any " +"source code refactoring using C++11 features." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:115 +msgid "" +"Once accepted, first step will be to update the build configurations to " +"require C++11-compliant compiler." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:121 +msgid "" +"This section outlines issues potentially caused by upgrade to C++11 " +"language." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:124 +msgid "" +"C++11 destructors, by default, have now the new exception specification " +"of ``nothrow(true)``. Destructors of GDAL classes should be reviewed and " +"any that are allowed/expected to throw exceptions must be marked with " +"``nothrow(false)``. Otherwise, any user of the existing GDAL codebase " +"would find the program terminating whenever GDAL destructor throws an " +"exception. Such review would be beneficial anyway." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:133 +msgid "Release" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:135 +msgid "First release of GDAL with C++11 compiler requirement could be 2.3.0." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:142 +msgid "This section clarifies status of C++14 support in GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:144 +msgid "" +"Once C++11 is adopted as default compilation mode, GDAL developers and " +"maintainers must ensure it also successfully compiles in C++14 and C++17 " +"modes." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:148 +msgid "" +"Are contributors allowed to add ``ifdef``'s for C++14 and C++17? No. Not " +"at this time." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:151 +msgid "" +"Is there a plan to upgrade to C++14 or C++17 to allow use of the C++ " +"latest features? No, there is no plan. It is, however, recognized, such " +"motion may be put to the vote around 2020." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:158 +msgid "" +"`http://en.cppreference.com/w/cpp/compiler_support " +"<http://en.cppreference.com/w/cpp/compiler_support>`__ C++ compiler " +"support" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:169 +msgid "" +"GDAL has been working well with C++11 builds for a number of years now, " +"so there should be no externally visible changes for the initial removal " +"of C++03 support." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:176 +msgid "" +"Change configure.ac to remove ``with_cpp11`` flag, always use C++11, and " +"fail if ``AX_CXX_COMPILE_STDCXX_11`` does not find C++11" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:178 +msgid "Remove @CXX11_SUPPORT@ in GDALmake.opt.in and anywhere else it occurs" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:179 +msgid "" +"Remove continuous build targets that do not support C++11 from Travis-CI " +"and AppVeyor" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:181 +msgid "Remove #if HAVE_CXX11 and leave only the C++11 code" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:183 +msgid "``find . -name \\*.h -o -name \\*.cpp | xargs egrep 'HAVE_CXX11'``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:185 +msgid "CPL_STATIC_ASSERT -> ``static_assert``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:186 +msgid "``NULL`` -> ``nullptr`` (Only for C++ code)" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:187 +msgid "CPL_OVERRIDE -> override and remove redundant virtual" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:188 +msgid "-MAX or -max() -> ``std::numeric_limits<T>::lowest()``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:193 +msgid "" +"The switch does not impact the ``C`` API used by the SWIG bindings. " +"However, there may be some code that can be removed." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:199 +msgid "" +"There are many C++11 features not address in this RFC. See " +"`https://en.wikipedia.org/wiki/C%2B%2B11 " +"<https://en.wikipedia.org/wiki/C%2B%2B11>`__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:202 +msgid "attributes" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:203 +msgid "``auto``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:204 +msgid "``consexpr``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:205 +msgid "``cstdint``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:206 +msgid "``delete`` and ``default`` for member functions" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:207 +msgid "enum classes" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:208 +msgid "initializer lists and ``std::initializer_list``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:209 +msgid "lambda" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:210 +msgid "range based for loops" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:211 +msgid "std::regex" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:212 +msgid "rvalue references" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:213 +msgid "smart pointers ``std::unique_ptr`` and ``std::shared_ptr``" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:214 +msgid "" +"New string literals: u8\"An UTF-8 string\", u\"An UTF-16 str\", U\"An " +"UTF-32 str\", R\"xml(raw content)xml\"" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:216 +msgid "``std::thread``, ``thread_local`` and related" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:217 +msgid "tuples" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:218 +msgid "And more..." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:223 +msgid "Any code using the C++ API must use C++11 or newer." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:225 +msgid "The C API should not be impacted." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:227 +msgid "GDAL 2.2.x and older will continue to have C++03 support." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:232 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:141 +msgid "The existing autotest suite should continue to pass." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:237 +msgid "" +"Although the above describes changes should have very few impact on " +"existing applications of the C API, some behavior changes, C++ level " +"changes and the conceptual changes are thought to deserve a 2.3 version " +"number." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:245 +msgid "" +"Implementation will be done by Kurt Schwehr. Others are welcome to pitch " +"in." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:251 +msgid "Related RFCs:" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:253 +msgid "" +"`GEOS RFC 5: C++11 Compilation Mode " +"<http://trac.osgeo.org/geos/wiki/RFC5>`__: GEOS is switching to requiring" +" C++11 to build." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:256 +msgid "" +"`Move OTB to C++14 <https://wiki.orfeo-" +"toolbox.org/index.php/Request_for_Comments-36:_Move_OTB_to_C%2B%2B14>`__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:260 +msgid "Amendments" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:262 +msgid "This RFC is superseded per :ref:`rfc-98`." +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:267 +msgid "" +"`https://lists.osgeo.org/pipermail/gdal-dev/2017-September/047139.html " +"<https://lists.osgeo.org/pipermail/gdal-" +"dev/2017-September/047139.html>`__" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:269 +msgid "EvenR +1" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:270 +msgid "JukkaR +1" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:271 +msgid "DanielM +0" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:272 +msgid "HowardB +1" +msgstr "" + +#: ../../source/development/rfc/rfc68_cplusplus11.rst:273 +msgid "KurtS +1" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:5 +msgid "RFC 69: C/C++ Code Formatting" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:7 +msgid "" +"This document proposes and describes desired code formatting style used " +"across C and C++ source code in GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:13 +msgid "Co-Author:" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:13 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:8 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:8 +msgid "Alessandro Pasotti" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:14 +msgid "elpaso@itopen.it" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:15 +msgid "2017-May-04" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:16 +msgid "Adpoted, implemented" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:19 +msgid "" +"This RFC is based on `GEOS RFC 4 " +"<https://trac.osgeo.org/geos/wiki/RFC4>`__ by Mateusz Łoskot." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:26 +msgid "" +"The document proposes and describes desired default code formatting style" +" guidelines for GDAL programming in C and C++ languages." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:29 +msgid "" +"The goal of this document is to initiate process to reach an agreement " +"for the default code formatting style." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:35 +msgid "" +"There is a need to decide on format of GDAL source code and apply such " +"globally consistent format to GDAL C/C++ codebase." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:38 +msgid "" +"A uniform, codebase-wide formatting style makes reading and comprehending" +" existing code easier, writing code focused on important aspects of new " +"developments and more pleasant, removes burden during a patch or pull " +"request code reviews and prevents `bikeshedding religious arguments " +"<http://wiki.c2.com/?WhereDoTheBracesGo>`__. Even in small projects, " +"contributing developers discover the problems of working without an " +"agreed upon code format." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:46 +msgid "" +"The utility of such guidelines has been proven by many open source " +"software projects." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:49 +msgid "" +"The scope of the proposal is specifically limited to formatting style " +"guidelines. It is not an intention to develop a general coding guide " +"covering other aspects of writing software like naming, etc." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:54 +#: ../../source/development/rfc/rfc72_pytest.rst:55 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:90 +#: ../../source/development/rfc/rfc74_sphinx.rst:51 +msgid "Proposal" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:56 +msgid "" +"It is important to make effortless for developers to produce properly " +"formatted code." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:59 +msgid "" +"The proposal suggests to use `clang-format " +"<https://clang.llvm.org/docs/ClangFormat.html>`__ version 3.8 or higher " +"to define C++ code formatting rules for GDAL code." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:63 +msgid "" +"The ``clang-format`` is a tool to automatically format C/C++ code, so " +"that developers don't need to worry about style issues. Unlike other " +"tools which use own parsers, ``clang-format`` uses the Clang tokenizer " +"and supports the same C++ source code as the Clang compiler. This " +"guarantees correct output is produced and offers unique features (eg. " +"wrapping long lines whether of code, strings, arrays - something which " +"AStyle has no way of doing)." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:71 +msgid "" +"The style settings can be defined in a ``.clang-format`` configuration " +"file, however to make it as easy as possible, we will use the default " +"style (LLVM style?)." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:75 +msgid "" +"The ``clang-format`` is straightforward to run and can support " +"development workflow as standalone tool or as one of many editor " +"integrations or other bespoke utilities (eg. ``git cl format`` " +"[Chromium])." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:80 +msgid "" +"A new pre-commit hook will be added to the current configuration in " +"``.pre-commit-config.yaml`` to run [clang-format pre-commit]." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:83 +msgid "" +"To enforce the code formatting, a gatekeeper will be installed in CI, " +"rejecting commits with code not conforming to the code formatting style " +"and a brief textual hint to install or update the pre-commit hooks will " +"be added to failure message." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:91 +msgid "Code Formatting Rules" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:93 +msgid "What code formatting rules to use?" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:95 +msgid "" +"*\"A mature engineers know that a standard is more important than which " +"standard.\"* ~[MongoDB]" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:98 +msgid "" +"``clang-format`` offers several defaults (eg. LLVM, Mozilla, Linux, " +"Google C++ Style)." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:101 +msgid "" +"The proposal recommends to use one of the base styles without any " +"modification. It is possible to fine-tune the configuration, but this RFC" +" aims for simplicity." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:105 +msgid "The reasons are two-fold:" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:107 +msgid "" +"make GDAL code unified with the wide spectrum of well-established C/C++ " +"projects" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:109 +msgid "long arguments and religious wars prevention." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:112 +msgid "``.clang-format``" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:114 +msgid "The hope is to avoid requiring a .clang-format file in the code base." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:117 +msgid "``.editorconfig``" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:119 +msgid "" +"`EditorConfig <http://editorconfig.org/>`__ is currently in use and " +"``.editorconfig`` file is provided to automatically tell popular code " +"editors about the basic style settings like indentation, whitespaces and " +"end-of-line markers for distinguished types of plain text files." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:124 +msgid "" +"The ``.editorconfig`` file will have to be updated to match the chosen " +"``.clang-format`` settings if they are required." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:128 +msgid "EOL" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:130 +msgid "``clang-format`` does not enforce line endings." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:132 +msgid "" +"The EOL marker is considered to be `a part of a file encoding decision " +"<http://lists.llvm.org/pipermail/cfe-commits/Week-of-" +"Mon-20130930/090200.html>`__ and not part of any coding style." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:136 +msgid "" +"The EOL marker can be enforced as project-wide setting controlled with " +"``.gitattributes`` and ``.editorconfig``." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:139 +msgid "" +"However, it shall still be left as configurable setting in developer's " +"environment of choice (eg. ``git config``) independently from the " +"project-wide setting." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:144 +msgid "Big Reformat" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:146 +msgid "What to do about the existing code?" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:148 +msgid "The proposal recommends to just do one big reformat of the codebase." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:150 +msgid "" +"While it may seem causing clutter in the repository log (eg. ``svn " +"blame``), if it occurs infrequently (eg. yearly) and is applied to the " +"entire codebase at that time, it should not be very disruptive to the " +"source code history. One way to cope with skewed history is to use ``git " +"blame -w`` which ignores whitespace when comparing commits." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:156 +msgid "" +"Partial application of the code formatting rules would create more work " +"without delivering the full benefit [MongoDB] leading to codebase with " +"different styles mixed." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:160 +msgid "" +"To skip the \"big reformat\" commit from ``git blame``, git offers a " +"mechanism to [git_blame_ignore] , a pre-configured ignore file ``.git-" +"blame-ignore-revs`` will be provided in the source tree with the \"big " +"reformat\" commit hash in it." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:165 +msgid "" +"The ignore file can be specified on the command line with ``git blame " +"--ignore-revs-file .git-blame-ignore-revs`` or it can be set permanently " +"with ``git config blame.ignoreRevsFile .git-blame-ignore-revs``." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:169 +msgid "" +"The a.m. instructions will be added to the `developers documentation " +"<https://gdal.org/development/dev_practices.html>`__." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:173 +msgid "Branches" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:175 +msgid "Branches to run the big reformat in are:" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:177 +msgid "``master``" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:178 +msgid "current stable version (to make backports easier)" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:181 +msgid "After Big Reformat" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:183 +msgid "" +"The pre-commit hook will automatically take care of formatting the code " +"before every commit, the CI test will reject not formatted code." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:187 +msgid "" +"*\"After all, every moment of time wasted on code formatting or " +"discussion thereof is eliminated.\"* ~[MongoDB]" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:193 +msgid "add clang-format to pre-commit configuration file" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:194 +msgid "Set up GitHub workflow [clang-format-check]" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:196 +msgid "" +"A draft of the implementation is available at `this branch " +"<https://github.com/elpaso/gdal/tree/rfc69_cplusplus_formatting_revival>`__." +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:198 +msgid "The relevant files are:" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:200 +msgid "" +"`pre-commit " +"<https://github.com/elpaso/gdal/blob/rfc69_cplusplus_formatting_revival" +"/.pre-commit-config.yaml#L30>`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:201 +msgid "" +"`.clang-format style " +"<https://github.com/elpaso/gdal/blob/rfc69_cplusplus_formatting_revival" +"/.clang-format>`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:202 +msgid "" +"`GH workflow " +"<https://github.com/elpaso/gdal/blob/rfc69_cplusplus_formatting_revival/.github/workflows" +"/clang-format-check.yml>`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:203 +msgid "" +"`clang-format script " +"<https://github.com/elpaso/gdal/blob/rfc69_cplusplus_formatting_revival/scripts" +"/clang-format.sh>`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:211 +msgid "" +"[clang-format pre-commit] `Clang-Format Pre-Commit <https://github.com" +"/pre-commit/mirrors-clang-format>`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:212 +msgid "" +"[clang-format-check] `Clang-Format Check Workflow " +"<https://github.com/marketplace/actions/clang-format-check>`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:213 +msgid "" +"[MongoDB] Succeeding With ClangFormat: `Part 1 " +"<https://engineering.mongodb.com/post/succeeding-with-clangformat-part-1" +"-pitfalls-and-planning/>`__, `Part 2 " +"<https://engineering.mongodb.com/post/succeeding-with-clangformat-part-2" +"-the-big-reformat/>`__, `Part 3 <https://engineering.mongodb.com/post" +"/succeeding-with-clangformat-part-3-persisting-the-change/>`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:219 +msgid "" +"[Chromium] `Using clang-format on Chromium C++ Code " +"<https://chromium.googlesource.com/chromium/src/+/master/docs/clang_format.md>`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:221 +msgid "" +"`https://clangformat.com <https://clangformat.com>`__ - ``clang-format`` " +"interactive guide and builder" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:223 +msgid "" +"`https://zed0.co.uk/clang-format-configurator/ <https://zed0.co.uk/clang-" +"format-configurator/>`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:224 +msgid "" +"`https://trac.osgeo.org/geos/wiki/RFC4 " +"<https://trac.osgeo.org/geos/wiki/RFC4>`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:225 +msgid "" +"[git_blame_ignore] `Ignore Commits in Blame View` <Git " +"https://docs.github.com/en/repositories/working-with-files/using-" +"files/viewing-a-file#ignore-commits-in-the-blame-view>`__" +msgstr "" + +#: ../../source/development/rfc/rfc69_cplusplus_formatting.rst:230 +msgid "+1 from PSC members KurtS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:5 +msgid "RFC 6: Geometry and Feature Style as OGR Special Fields" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:16 +msgid "" +"This proposal addresses and issue have been discovered long ago, and OGR " +"provides no equivalent solution so far." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:19 +msgid "" +"Some of the supported formats like Mapinfo.tab may contain multiple " +"geometry types and style information. In order to handle this kind of " +"data sources properly a support for selecting the layers by geometry type" +" or by the style info would be highly required. For more details see the " +"following MapServer related bugs later in this document." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:25 +msgid "" +"All of the proposed changes can be found at the tracking bug of this RFC " +"referenced later in this document." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:31 +msgid "" +"The most reasonable way to support this feature is to extend the " +"currently existing 'special field' approach to allow specifying more than" +" one fields. Along with the already defined 'FID' field we will add the " +"following ones:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:36 +msgid "'OGR_GEOMETRY' containing the geometry type like 'POINT' or 'POLYGON'." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:38 +msgid "'OGR_STYLE' containing the style string." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:39 +msgid "'OGR_GEOM_WKT' containing the full WKT of the geometry." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:41 +msgid "" +"By providing the aforementioned fields one can make for example the " +"following selections:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:44 +msgid "" +"select FID, OGR_GEOMETRY, OGR_STYLE, OGR_GEOM_WKT, \\* from MyTable where" +" OGR_GEOMETRY='POINT' OR OGR_GEOMETRY='POLYGON'" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:46 +msgid "" +"select FID, OGR_GEOMETRY, OGR_STYLE, OGR_GEOM_WKT, \\* from MyTable where" +" OGR_STYLE LIKE '%BRUSH%'" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:48 +msgid "" +"select FID, OGR_GEOMETRY, OGR_STYLE, OGR_GEOM_WKT, \\* from MyTable where" +" OGR_GEOM_WKT LIKE 'POLYGON%'" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:50 +msgid "select distinct OGR_GEOMETRY from MyTable order by OGR_GEOMETRY desc" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:55 +msgid "There are two distinct areas where this feature plays a role" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:57 +msgid "Feature query implemented at ogrfeaturequery.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:59 +msgid "SQL based selection implemented at ogr_gensql.cpp and ogrdatasource.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:62 +msgid "" +"To specify arbitrary number of special fields we will declare an array " +"for the field names and types in ogrfeaturequery.cpp as" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:72 +msgid "" +"So as to make this array accessible to the other files the followings " +"will be added to ogr_p.h" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:90 +msgid "" +"In ogrfeature.cpp the field accessor functions (GetFieldAsString, " +"GetFieldAsInteger, GetFieldAsDouble) will be modified providing the " +"values of the special fields by the field index" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:94 +msgid "" +"The following code will be added to the beginning of " +"OGRFeature::GetFieldAsInteger:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:112 +msgid "" +"The following code will be added to the beginning of " +"OGRFeature::GetFieldAsDouble:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:130 +msgid "" +"The following code will be added to the beginning of " +"OGRFeature::GetFieldAsString:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:160 +msgid "" +"The current implementation of OGRFeature::GetFieldAsString uses a static " +"string to hold the const char\\* return value that is highly avoidable " +"and makes the code thread unsafe. In this regard the 'static char " +"szTempBuffer[80]' will be changed to non static and a new member will be " +"added to OGRFeature in ogrfeature.h as:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:170 +msgid "" +"This member will be initialized to NULL at the constructor, and will be " +"freed using CPLFree() at the destructor of OGRFeature." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:173 +msgid "" +"In OGRFeature::GetFieldAsString all of the occurrences of 'return " +"szTempBuffer;' will be changed to 'return m_pszTmpFieldValue = CPLStrdup(" +" szTempBuffer );'" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:177 +msgid "" +"OGRFeature::GetFieldAsString is responsible to destroy the old value of " +"m_pszTmpFieldValue at the beginning of the function:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:185 +msgid "" +"In ogrfeaturequery.cpp we should change OGRFeatureQuery::Compile to add " +"the special fields like:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:198 +msgid "" +"In ogrfeaturequery.cpp OGRFeatureQueryEvaluator() should be modifyed " +"according to the field specific actions like" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:226 +msgid "" +"In ogrfeaturequery.cpp OGRFeatureQuery::FieldCollector should be modifyed" +" to add the field names like:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:235 +msgid "" +"In ogrdatasource.cpp ExecuteSQL() will allocate the arrays according to " +"the number of the special fields:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:249 +msgid "And the fields will be added as" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:262 +msgid "" +"For supporting the SQL based queries we should also modify the " +"constructor of OGRGenSQLResultsLayer in ogr_gensql.cpp and set the field " +"type properly:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:284 +msgid "" +"Some of the queries will require to modify " +"OGRGenSQLResultsLayer::PrepareSummary in ogr_gensql.cpp will be " +"simplified (GetFieldAsString will be used in all cases to access the " +"field values):" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:294 +msgid "" +"OGRGenSQLResultsLayer::TranslateFeature should also be modifyed when " +"copying the fields from primary record to the destination feature" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:311 +msgid "" +"For supporting the 'order by' queries we should also modify " +"OGRGenSQLResultsLayer::CreateOrderByIndex() as:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:332 +msgid "" +"All of the strings allocated previously should be deallocated later in " +"the same function as:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:352 +msgid "" +"When ordering by the field values the OGRGenSQLResultsLayer::Compare " +"should also be modifyed:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:386 +msgid "Adding New Special Fields" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:388 +msgid "" +"Adding a new special field in a subsequent development phase is fairly " +"straightforward and the following steps should be made:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:391 +msgid "" +"In ogr_p.h a new constant should be added with the value of the " +"SPECIAL_FIELD_COUNT and SPECIAL_FIELD_COUNT should be incremented by one." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:395 +msgid "" +"In ogrfeaturequery.cpp the special field string and the type should be " +"added to SpecialFieldNames and SpecialFieldTypes respectively" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:398 +msgid "" +"The field value accessors (OGRFeature::GetFieldAsString, " +"OGRFeature::GetFieldAsInteger, OGRFeature::GetFieldAsDouble) should be " +"modifyed to provide the value of the new special field. All of these " +"functions provide const return values so GetFieldAsString should retain " +"the value in the m_pszTmpFieldValue member." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:404 +msgid "" +"When adding a new value with a type other than SWQ_INTEGER and SWQ_STRING" +" the following functions might also be modified accordingly:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:408 +msgid "OGRGenSQLResultsLayer::OGRGenSQLResultsLayer" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:409 +msgid "OGRGenSQLResultsLayer::TranslateFeature" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:410 +msgid "OGRGenSQLResultsLayer::CreateOrderByIndex" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:411 +msgid "OGRGenSQLResultsLayer::Compare" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:412 +msgid "OGRFeatureQueryEvaluator" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:417 +msgid "" +"In most cases the backward compatibility of the OGR library will be " +"retained. However the special fields will potentially conflict with " +"regard fields with the given names. When accessing the field values the " +"special fields will take pecedence over the other fields with the same " +"names." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:423 +msgid "" +"When using OGRFeature::GetFieldAsString the returned value will be stored" +" as a member variable instead of a static variable. The string will be " +"deallocated and will no longer be usable after the destruction of the " +"feature." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:431 +msgid "" +"A new gdalautotest/ogr/ogr_sqlspecials.py script to test support for all " +"special fields in the ExecuteSQL() call and with WHERE clauses." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:437 +msgid "" +"The OGR SQL document will be updated to reflect the support for special " +"fields." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:443 +msgid "" +"Tamas Szekeres will implement the bulk of the RFC in time for GDAL/OGR " +"1.4.0." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:446 +msgid "" +"Frank Warmerdam will consider how the backward compatibility issues (with" +" special regard to the modified lifespan of the GetFieldAsString returned" +" value) will affect the other parts of the OGR project and will write the" +" Python regression testing script." +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:454 +msgid "" +"Tracking bug for this feature (containing all of the proposed code " +"changes): #1333" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:457 +msgid "MapServer related bugs:" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:459 +msgid "`1129 <http://trac.osgeo.org/mapserver/ticket/1129>`__" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:460 +msgid "`1438 <http://trac.osgeo.org/mapserver/ticket/1438>`__" +msgstr "" + +#: ../../source/development/rfc/rfc6_sqlgeom.rst:471 +msgid "Andrey Kiselev +1" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:5 +msgid "" +"RFC 70: Guessing output format from output file name extension for " +"utilities" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:8 +#: ../../source/development/rfc/rfc71_github_migration.rst:8 +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:8 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:8 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:8 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:8 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:8 +#: ../../source/development/rfc/rfc87_signed_int8.rst:8 +#: ../../source/development/rfc/rfc88_googletest.rst:8 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:8 +#: ../../source/development/rfc/rfc91_dataset_close.rst:8 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:8 +#: ../../source/development/rfc/rfc93_update_feature.rst:8 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:8 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:8 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:8 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:7 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:8 +msgid "Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:9 +#: ../../source/development/rfc/rfc71_github_migration.rst:9 +msgid "even.rouault@spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:10 +msgid "Aug 2017" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:11 +#: ../../source/development/rfc/rfc71_github_migration.rst:11 +#: ../../source/development/rfc/rfc88_googletest.rst:11 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:11 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:11 +#: ../../source/development/rfc/rfc91_dataset_close.rst:11 +#: ../../source/development/rfc/rfc93_update_feature.rst:11 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:11 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:11 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:11 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:10 +msgid "Adopted, implemented" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:12 +msgid "Implementation version:" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:12 +msgid "2.3.0" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:18 +msgid "" +"This proposal is to add syntaxic sugar to make GDAL and OGR command line " +"utilities, so they take into account the extension of the output filename" +" to guess which output driver to use, when it is not explicitly specified" +" with -f / -of switch." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:26 +msgid "" +"Currently command line utilities require to explicitly specify the output" +" format when not wishing to use the default format (generally GeoTIFF for" +" raster, and Shapefile for vector). But this is rather counter-intuitive." +" For example \"gdal_translate in.tif out.png\" will generate a GeoTIFF, " +"and \"ogr2ogr out.gpkg in.shp\" a shapefile. So you have to specify " +"respectively -of PNG and -f GPKG to get the expected result." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:34 +msgid "" +"Guessing the output format from the extension of the output filename is " +"for example a behavior found in ImageMagick convert utility, or in " +"OpenJPEG opj_compress/opj_decompress utilities." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:39 +msgid "Changes in C/C++ and Python utilities" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:41 +msgid "" +"Command line utilities, when neither -f nor -of are specified (note: " +"since r39878 both switches can be indifferently used), will loop through " +"the registered drivers and check if one or several drivers, with output " +"capabilities, declare to recognize the extension of the output filename." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:46 +msgid "" +"When one and only one driver declares this extension (.tif, .png, .jpg " +"etc), it will be used automatically" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:48 +msgid "" +"When several drivers declare this extension (for example KML and LIBKML " +"for .kml), the utility will select the first registered driver (except " +"netCDF instead of GMT for .nc files), and a warning is emitted specifying" +" which driver is used" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:52 +msgid "" +"When no driver declares this extension, and the extension is not empty " +"(e.g a .mpg filename), the utility will error out" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:55 +msgid "For completeness:" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:57 +msgid "" +"When there's no extension, and no prefix is recognized (see below), the " +"default output driver will be silently used, as currently" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:60 +msgid "" +"Since at least GDAL 1.10, the base of this logic already exists since a " +"warning is emitted for C/C++ utilities, when the extension of the output " +"format is known to be recognized by another driver than the default " +"output driver." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:65 +msgid "" +"Similarly, for vector output, if doing something like \"ogr2ogr " +"PG:dbname=mydb out.shp\", a PG:dbname=mydb directory is created with " +"shapefiles, instead of ingesting the shapefile into PostgreSQL. A warning" +" is emitted in that case since the PG driver declares the PG: prefix in " +"its metadata. The new behavior will be to imply the -update switch in " +"such situation." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:72 +msgid "" +"When the utilities are available as library functions (GDALTranslate(), " +"etc.), output format guessing will also be applied if the -f/-of switch " +"is not specified" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:79 +msgid "" +"For librarified utilities (gdal.Translate, etc.), the format argument now" +" defaults to None." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:83 +msgid "Potential issues" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:85 +msgid "" +"There might be some fragility with the new logic in the situation where a" +" GDAL version has only one driver that supports extension xxx, but a " +"later version adds another driver that also supports extension xxx (or " +"another distribution of the same version has a plugin that handles xxx). " +"So scripts that did \"gdal_translate in out.xxx\" would now error out in " +"the next version since several drivers are available." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:92 +msgid "" +"Bottom line: always specify the output driver when " +"reliability/reproducibility is desired." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:95 +msgid "" +"This RFC mostly helps for interactive conversions where the less you type" +" the better." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:101 +msgid "" +"This will break scripts that use an output filename whose extension is " +"matched by a driver which is not the default one. This incompatibility is" +" rather unlikely since previous GDAL versions already emit a warning in " +"this situation (for C/C++ utilities only. for Python utilities default " +"driver is silently used), so people have likely specified the output " +"driver if they really want to do \"gdal_translate in.tif out.png -of " +"GTiff\"." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:109 +msgid "MIGRATION_GUIDE.TXT will mention those potential caveats." +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:114 +msgid "" +"The existing autotest suite should continue to pass (with a few changes " +"related to tests for the current behavior)" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:120 +msgid "Implementation will be done by Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:122 +msgid "" +"Proposed implementation is in " +"`https://github.com/rouault/gdal2/tree/rfc70 " +"<https://github.com/rouault/gdal2/tree/rfc70>`__" +msgstr "" + +#: ../../source/development/rfc/rfc70_output_format_guess.rst:125 +msgid "" +"Diff: `https://github.com/OSGeo/gdal/compare/trunk...rouault:rfc70 " +"<https://github.com/OSGeo/gdal/compare/trunk...rouault:rfc70>`__" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:5 +msgid "RFC 71: Migration to GitHub" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:10 +msgid "March 2018" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:17 +msgid "" +"It is proposed that the GDAL source tree and ticket database moves from " +"the OSGeo hosted Subversion repository/Trac database to GitHub. Full " +"source code history will be preserved. To make the migration simpler, " +"existing tickets will remain in OSGeo Trac and will not be migrated to " +"GitHub. New tickets will have to be opened in GitHub." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:24 +msgid "Motivations" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:26 +msgid "" +"It is considered that most developers interested by GDAL development are " +"nowadays more used to git than Subversion, and the use of Subversion as " +"the main source control management makes contributions less attractive." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:30 +msgid "" +"The `https://github.com/OSGeo/gdal <https://github.com/OSGeo/gdal>`__ " +"mirror has existed since 2012 and has over time become the preferred way " +"for contributors without direct SVN access (or even those with SVN " +"access) to submit their contributions, in particular because of the " +"coupling with the continuous integratations services of Travis-CI and " +"!AppVeyor that enable maintainers to check that the contribution doesn't " +"introduce known regressions + the friendly way of commenting a pull " +"request. However the manual porting of !GitHub pull requests to Trac is a" +" bit painful for GDAL maintainers." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:39 +msgid "" +"GitHub has become the de-facto hosting platform for a lot of open-source " +"projects." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:43 +msgid "Details of the migration" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:45 +msgid "" +"The existing GitHub git repository will be pushed to " +"`https://github.com/OSGeo/gdal_svn_mirror_backup " +"<https://github.com/OSGeo/gdal_svn_mirror_backup>`__ (eventually removed " +"once we are confident further steps have not messed things up)" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:49 +msgid "" +"As GitHub also uses the syntax \"#1234\" to link commit messages to its " +"issues that was also used in Trac, currently when following links in " +"!GitHub that point to a Trac ticket, one ends up to a non-existing or " +"unrelated !GitHub issue/pull request. So the commit messages of the " +"current !GitHub mirror will be rewritten by a \"git filter-branch --msg-" +"filter 'python rewrite.py' -- --all\" command to replace \"#1234\" with " +"\"`https://trac.osgeo.org/gdal/ticket/1234 " +"<https://trac.osgeo.org/gdal/ticket/1234>`__\"" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:57 +msgid "" +"The git 'trunk' branch will be renamed 'master' to follow git best " +"practices" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:59 +msgid "The existing 'tag/x.y.z' branches will be replaced by proper git tags." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:61 +msgid "" +"This modified repository will be forced push to " +"`https://github.com/OSGeo/gdal <https://github.com/OSGeo/gdal>`__ This " +"will have the consequence of invalidating existing pull request or forks " +"of repository that will have to be rebased to the new one. From that " +"point, \"svn commit\" should be avoided and changes should go to the git " +"repository." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:67 +msgid "" +"The cron job on the OSGeo server that refreshes the website from sources " +"will be modified to pull from !GitHub rather than SVN." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:69 +msgid "" +"Ticket creation permissions will be removed in Trac. Modification or " +"closing of existing open tickets will still be possible. From that point," +" if closing a Trac ticket, one will have manually to reference the github" +" commit." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:73 +msgid "" +"The settings of the GDAL GitHub repository will be changed allow tickets " +"to be filed. Labels and Milestones will be populated with relevant " +"content" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:77 +msgid "" +"Further actions required, in no particular order, and for which help from" +" other GDAL developers/contributors would be welcome:" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:80 +msgid "" +"Most visible Trac wiki documentation will have to be revised to point to " +"GitHub" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:82 +msgid "HOWTO-RELEASE will have to be revised." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:83 +msgid "" +"Existing SVN committers still interested in the project will have to " +"request commit access to the GitHub repo." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:85 +msgid "" +"Some support from OSGeo SAC will be needed to turn the GDAL SVN " +"repository to read-only (a complementary option would be to rename it to " +"gdal_historical so that people pulling from the old one are well aware of" +" the migration by having their scripts 'cleanly' error out)" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:89 +msgid "" +"Some guidelines on how we intend to use git/GitHub features will have to " +"be rewritten." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:93 +msgid "Exit strategy" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:95 +msgid "" +"GitHub is a closed platform. In case it would close or would start askin " +"to pay unreasonable fees, some backup strategy of the tickets would be " +"needed. The solutions might be:" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:99 +msgid "" +"`https://github.com/josegonzalez/python-github-backup " +"<https://github.com/josegonzalez/python-github-backup>`__" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:100 +msgid "" +"GitLab has an import module from GitHub. Although some experimentation " +"has been done with those, this RFC does *not* cover setting up those " +"solutions as a regular backup system." +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:105 +msgid "Not covered by this RFC" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:107 +msgid "" +"Migration of Trac wiki content to GitHub wiki is not in the scope of this" +" RFC. Can be done later" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:111 +msgid "Previous related discussions" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:113 +msgid "" +"`https://lists.osgeo.org/pipermail/gdal-dev/2018-March/048240.html " +"<https://lists.osgeo.org/pipermail/gdal-dev/2018-March/048240.html>`__" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:114 +msgid "" +"`https://lists.osgeo.org/pipermail/gdal-dev/2017-September/047060.html " +"<https://lists.osgeo.org/pipermail/gdal-" +"dev/2017-September/047060.html>`__" +msgstr "" + +#: ../../source/development/rfc/rfc71_github_migration.rst:119 +msgid "+1 from HowardB, JukkaR, KurtS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:5 +msgid "RFC 72: Update autotest suite to use pytest" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:8 +msgid "Craig de Stigter" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:9 +msgid "craig.destigter@koordinates.com" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:10 +msgid "2018-Sep-27" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:11 +msgid "*Implemented in GDAL 2.4*" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:17 +msgid "" +"The document proposes and describes conversion of the existing Python " +"autotest suite to use the `pytest framework " +"<https://docs.pytest.org/en/latest/>`__." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:21 +msgid "" +"Using pytest provides significant productivity gains for writing, reading" +" and debugging python tests, compared with the current home-grown " +"approach." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:28 +msgid "" +"The current autotest framework dates back to 2007 (at least), and while " +"reasonably comprehensive (and 186,000 lines of Python) is difficult for " +"developers to use and extend." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:32 +msgid "" +"As a homegrown framework it'll never get any better than the effort GDAL " +"developers put in. For example: reporting, test coverage, " +"parallelisation, resumption, log/output handling, parameterisation." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:35 +msgid "" +"Test failures are typically only as descriptive as \"fail\", determining " +"the cause requires editing the tests." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:37 +msgid "It is difficult to run/rerun individual tests" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:38 +msgid "" +"The tests often assume a set of compile options that may not be valid for" +" the local build." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:40 +msgid "" +"Tests are patched/disabled in various CI environments by scripts outside " +"the test tree. This is opaque to developers working locally." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:42 +msgid "" +"Some tests depend on each other and a specific execution order, making it" +" difficult to debug and extend." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:44 +msgid "Shared functionality is repeated across tests and modules" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:45 +msgid "" +"Tests are typically only written for new functionality, not regressions. " +"(Crudely, from the 2663 commits in the last year only 725 touched the " +"autotest tree)" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:49 +msgid "" +"By adopting an OSS test framework in widespread use we can leverage the " +"ecosystem to provide GDAL with benefits and improvements going forward. " +"The utility of automated testing has been proven for GDAL, and we need to" +" make test writing as easy as possible." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:57 +msgid "" +"Port the existing Python autotest suite to use the `pytest framework " +"<https://docs.pytest.org/en/latest/>`__. Why pytest? It's in widespread " +"use, has a wide set of features, is extensible via plugins, and focuses " +"on making writing and debugging tests as easy as possible - minimising " +"boilerplate code and maximising reuse. `This presentation " +"<http://thesoftjaguar.com/pres_pytest.html>`__ (despite dating back to " +"2014) gives a brief overview of the key benefits." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:65 +msgid "" +"Do the bulk of this port using automated code refactoring tools so the " +"autotest suite matches the preferred pytest approach. While pytest does " +"support all sorts of custom test collection and execution methods, in " +"order to increase the benefits to developers going forward we should do a" +" proper conversion. Initial goal is to get the tests ported, remove as " +"much boilerplate as feasible, all while keeping the existing CI green. " +"Future goals are to continue to reduce boilerplate code and increase " +"isolation between tests." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:74 +msgid "At a minimum we still need to preserve the existing ability to:" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:76 +msgid "" +"Run all existing CI tests in all environments using the existing " +"configuration" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:78 +msgid "Run individual test modules" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:79 +msgid "Support existing subprocess/multiprocess tests" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:80 +msgid "Support testing under Python 2.7 & Python 3" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:81 +msgid "Stacktraces for assertion failures" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:83 +msgid "" +"The new test suite will be in place for the GDAL 2.4.0 release in " +"December 2018. Changes will not be backported to the 2.3.x or earlier " +"release branches." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:87 +#: ../../source/development/rfc/rfc74_sphinx.rst:110 +msgid "References:" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:89 +msgid "`issue #949 <https://github.com/OSGeo/gdal/issues/949>`__." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:90 +msgid "" +"`gdal-dev post <https://lists.osgeo.org/pipermail/gdal-" +"dev/2018-October/049081.html>`__, Oct 2018" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:95 +msgid "Example" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:97 +msgid "A typical existing GDAL python unit test:" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:124 +msgid "Could *eventually* become something like this" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:135 +msgid "" +"It's a lot clearer what it is actually testing, and all support " +"functionality is handled by shared-use fixtures (``gdaladdo`` & " +"``require_files``), including cleanup and conditional-skipping." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:140 +msgid "Test output" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:142 +msgid "" +"Pytest out-of-the-box produces readable output, and is augmented by the " +"``pytest-sugar`` plugin which makes it even nicer:" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:145 +msgid "" +"Successful tests don't produce much output (a single ``.`` or ``✓`` per " +"test, by default)" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:147 +msgid "" +"Failed tests produce a traceback. Any logs, stdout and stderr produced by" +" the failing tests are printed too. This is a great start for debugging " +"the cause of the failure." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:150 +msgid "Any expressions used in failing asserts are printed." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:151 +msgid "Test output is clearly colourised (red/green) if the terminal supports it." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:154 +msgid "![](pytest-output-example.png, 626px, center)" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:157 +msgid "Plan Phase 1" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:159 +msgid "Progress at `pull request 963 <https://github.com/OSGeo/gdal/pull/963>`__." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:162 +msgid "" +"Using code automation, convert the existing Python autotest suite to use " +"pytest-style assertions." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:165 +msgid "" +"rename all tests to ``test_*()``. Pytest finds tests by matching names " +"against a regex and this is the default regex." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:168 +msgid "" +"generate assertions from ``post_reason()``/``return 'fail'`` calls where " +"possible" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:171 +msgid "replace all ``skip``/``fail``/``success`` return values" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:173 +msgid "" +"remove extra ``../pymod`` entries from ``sys.path``. All tests now run in" +" a single process" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:176 +msgid "remove ``__main__`` block and ``gdaltest_list`` from test files" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:178 +msgid "" +"these collectively achieve better test collection/selection, output " +"capturing, and improved assertions and reporting" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:181 +msgid "" +"Manually convert the dynamically-generated tests to use `parametrization " +"<https://docs.pytest.org/en/latest/parametrize.html>`__" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:184 +msgid "" +"Ensure the slow/internet tests are still marked as such and skipped by " +"default." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:187 +msgid "" +"Use `pytest-sugar <https://pivotfinland.com/pytest-sugar/>`__ to make " +"test output pretty. Disable it in CI since it doesn't work well with " +"travis CI's output buffering." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:191 +msgid "" +"Move environment-specific test-skipping from CI to the test suite, " +"possibly with additional tag/marks." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:194 +msgid "Ensure the existing CI tests pass & debug any failures" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:196 +msgid "Add documentation and a straightforward install process for pytest itself" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:200 +msgid "Notable changes and their implications" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:202 +msgid "" +"tests are now run with ``cd autotest ; pytest``. (The first time you may " +"need to ``pip install -r requirements.txt`` to install pytest)" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:204 +msgid "" +"All tests now run in a single process (they were previously forked for " +"each test module). This means that:" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:207 +msgid "" +"errors during test collection are now loud, and immediately fail the " +"entire test run with a traceback. Previously things like syntax errors in" +" files and errors at module level were easy to miss." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:211 +msgid "a single segfault will kill the entire test run dead." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:213 +msgid "" +"It's now possible to run individual tests, instead of just entire files. " +"However, tests are *not yet independent of each other*. So that might " +"cause the tests to behave differently than if you ran the whole module." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:217 +msgid "" +"``test_py_scripts.run_py_script`` was modified to always run the script " +"as a subprocess. The stdout capturing of the original method did strange " +"things with pytest. This change broke some tests that relied on passing " +"files in the ``/vsimem/`` root to scripts, so those have been changed to " +"use the ``tmp/`` root instead." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:222 +msgid "no test suite support for Python <2.7" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:227 +msgid "Plan Phase 2 / Future Work" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:229 +msgid "" +"Improving test isolation, so running an entire module at a time isn't " +"required." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:231 +msgid "" +"Removing the global ``gdaltest.<drivername>_drv`` variables and replace " +"them with pytest fixtures." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:233 +msgid "Use fixtures for temporary file handling and cleanup" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:234 +msgid "More automated test skipping based on what's actually compiled." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:235 +msgid "Automated style cleanup using `Black <https://github.com/ambv/black>`__." +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:237 +msgid "" +"Consider parallelising test runs by default (there are several `plugins " +"available <https://github.com/pytest-dev/pytest-xdist>`__ for this)" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:244 +msgid "Adopted with the following votes from PSC members:" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:246 +msgid "+1 from EvenR, DanielM, HowardB and KurtS" +msgstr "" + +#: ../../source/development/rfc/rfc72_pytest.rst:247 +msgid "+0 from JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:5 +msgid "" +"RFC 73: Integration of PROJ6 for WKT2, late binding capabilities, time-" +"support and unified CRS database" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:9 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:9 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:9 +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:9 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:9 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:9 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:9 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:9 +#: ../../source/development/rfc/rfc87_signed_int8.rst:9 +#: ../../source/development/rfc/rfc88_googletest.rst:9 +#: ../../source/development/rfc/rfc93_update_feature.rst:9 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:9 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:9 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:9 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:8 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:9 +msgid "even.rouault @ spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:10 +msgid "2019-Jan-08" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:11 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:11 +msgid "Last modified:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:11 +msgid "2019-May-02" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:12 +msgid "Implemented in GDAL 3.0" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:18 +msgid "" +"The document describe work related to integration of PROJ 6 with GDAL, " +"which adds different capabilities: support for CRS WKT 2 version, \"late " +"binding\" capabilities for coordinate transformations between CRS, " +"support of time-dimension for coordinate operations and the use of a " +"unified CRS database." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:27 +msgid "" +"The motivations are those exposed in `https://gdalbarn.com/#why " +"<https://gdalbarn.com/#why>`__ , which are copied here" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:31 +msgid "" +"Coordinate systems in GDAL, PROJ, and libgeotiff are missing modern " +"capabilities and need a thorough refactoring:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:34 +msgid "" +"The dreaded ad hoc CSV databases in PROJ_LIB and GDAL_DATA are " +"frustrating for users, pose challenges for developers, and impede " +"interoperability of definitions." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:37 +msgid "GDAL and PROJ are missing OGC WKT2 support." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:38 +msgid "" +"PROJ 5.0+ no longer requires datum transformation pivots through WGS84, " +"which can introduce errors of up to 2m, but the rest of the tools do not " +"take advantage of it." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:43 +msgid "CSV database" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:45 +msgid "" +"The use of a SQLite-based database for EPSG and other definitions will " +"allow the projects to add more capability (area-aware validation), " +"transition the custom peculiar data structures of the projects to " +"something more universally consumable, and promote definition " +"interoperability between many coordinate system handling software tools." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:52 +msgid "WKT2" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:54 +msgid "" +"`OGC WKT2 <http://docs.opengeospatial.org/is/12-063r5/12-063r5.html>`__ " +"fixes longstanding interoperability coordinate system definition " +"discrepancies. WKT2 contains tools for describing time-dependent " +"coordinate reference systems. PROJ 5+ is now capable of time-dependent " +"transformations, but GDAL and other tools do not yet support them." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:60 +msgid "" +"Several countries are updating their geodetic infrastructure to include " +"time-dependent coordinate systems. For example, Australia and the United " +"States are adapting time-dependent coordinate systems in 2020 and 2022, " +"respectively. The familiar NAD83 and NAVD88 in North America being " +"replaced by NATRF2022 and NAPGD2022, and the industry WILL have to adapt " +"to these challenges sooner or later." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:68 +msgid "WGS84 Pivot" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:70 +msgid "" +"PROJ previously required datum transformation that pivoted through WGS84 " +"via a 7-parameter transform. This pivot is a practical solution, but it " +"can introduce error of about two meters, and many legacy datums cannot be" +" defined in terms of WGS84. PROJ 5+ now provides the tools to support " +"late-binding through its `transformation pipeline framework " +"<https://proj4.org/usage/transformation.html#geodetic-transformation>`__," +" but GDAL and the rest of the tools cannot use it yet. Higher accuracy " +"transformations avoid stepping through WGS84 and eliminates extra " +"transformation steps with side-car data from a local geodetic authority." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:81 +msgid "Related work in other libraries" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:83 +msgid "" +"This RFC is the last step in the \"gdalbarn\" work. Previous steps have " +"consisted in implementing the related changes in PROJ master per `PROJ " +"RFC 2 <https://proj4.org/community/rfc/rfc-2.html>`__ and in libgeotiff " +"master per `libgeotiff pull request 2 " +"<https://github.com/OSGeo/libgeotiff/pull/2>`__." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:93 +msgid "Third-party library requirements" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:95 +msgid "" +"GDAL master (future 3.0) will require PROJ master (future PROJ 6.0) and " +"libgeotiff master (future libgeotiff 1.5 or 2.0) for build and execution." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:99 +msgid "" +"Regarding PROJ, no internal copy of PROJ will be embedded in GDAL master." +" It is not doable of supporting older versions of PROJ, as the " +"OGRSpatialReference class has been largely rewritten to take advantage of" +" functionality that has been completely moved from GDAL to PROJ: PROJ " +"string import and export, WKT string import and export, EPSG database " +"exploitation. To be able to use more easily GDAL master and PROJ master " +"in complex setups where some GDAL dependencies use a libproj provided by " +"the system, and where mixing naively PROJ master and this older libproj " +"would result in runtime crashes, PROJ master can be built with " +"CFLAGS/CXXFLAGS=-DPROJ_RENAME_SYMBOLS to alias its public symbols, and " +"GDAL will be able to use this custom build. Note that this is not " +"intended to be used in a long term, since proper packaging solutions will" +" eventually use PROJ 6 to rebuild all its reverse dependencies. It should" +" be noted also that PROJ is required at configure / nmake time, that is " +"the dynamic loading at runtime through dlopen() / LoadLibrary() is no " +"longer available." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:116 +msgid "" +"Regarding libgeotiff, the internal copy in frmts/gtiff/libgeotiff has " +"been refreshed with the content of upstream libgeotiff master." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:119 +msgid "" +"All continuous integration systems (Travis-CI and AppVeyor) have been " +"updated to build PROJ master as part of the GDAL build." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:123 +msgid "OGRSpatialReference rewrite" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:125 +msgid "" +"The OGRSpatialReference class is central in GDAL/OGR for all coordinate " +"reference systems (CRS) manipulations. Up to GDAL 2.4, this class " +"contained mostly a OGR_SRSNode root node of a WKT 1 representation, and " +"all getters and setters manipulated this tree representation. As part of " +"this work, the main object contained internally by OGRSpatialReference is" +" now a PROJ PJ object, and methods call PROJ C API getters and setters on" +" this PJ object. This enables to be, mostly (*), representation " +"independent." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:134 +msgid "" +"WKT1, WKT2, ESRI WKT, PROJ strings import and export is now delegated to " +"PROJ. The same holds for import of CRS from the EPSG database, that now " +"relies on proj.db SQLite database. Consequently all the data/\\*.csv " +"files that contained CRS related information have been removed from GDAL." +" It should be noted that \"morphing\" from ESRI WKT is now done " +"automatically when importing WKT." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:141 +msgid "" +"While general semantics of methods like IsSame() or FindMatches() remain " +"the same, underneath implementations are substantially different, which " +"can lead to different results than previous GDAL versions in some cases. " +"In the FindMatches() case, identification of CRS to EPSG entries is " +"generally improved due to enhanced query capabilities in the database." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:147 +msgid "" +"(*) The \"mostly\" precision is here since it was not practical to do " +"this rewrite in every place. So for some methods, an internal WKT1 export" +" is still done. This is the case for methods that take a path to a SRS " +"node (like \"GEOGCS|UNIT\") as an argument, or some methods like " +"SetProjection(), GetProjParm(), that expect a OGC WKT1 specific name. " +"Those are thought to be used mostly be drivers. Changing them to be EPSG " +"names would impact a number of drivers, some of them little tested " +"regarding SRS support, and which furthermore mostly support WKT1 " +"representation only." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:158 +msgid "OGRCoordinateTransformation changes" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:160 +msgid "" +"Since GDAL 2.3 and initial PROJ 5 support, when transforming between two " +"CRS we still relied on the PROJ.4 string export of the source and target " +"CRS to create a coordinate operation pipeline. So this limited to " +"\"early-binding\" operations, that is using the WGS84 pivot through " +"towgs84 or nadgrids PROJ keywords. Now PROJ new capabilities to find " +"appropriate coordinate operations between two CRS is used, offering " +"\"late-binding\" capabilities to take into account other pivots than " +"WGS84 or area of uses." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:169 +msgid "" +"OGRCreateCoordinateOperation() now takes an extra optional arguments to " +"define options." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:172 +msgid "" +"One of those options is to define an area of interest that will be taken " +"into account when searching candidate operations. If several operations " +"match, the \"best\" (according to PROJ sorting criterion) will be " +"selected. Note: it will systematically be used even if later calls to " +"Transform() use coordinates outside of the initial area of interest." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:178 +msgid "" +"Another option is the ability to specify the coordinate operation to " +"apply, so as an override of what GDAL / PROJ would have automatically " +"computed, either as a PROJ string (generally a +proj=pipeline), or a WKT " +"coordinate operation/concatenated operation. Users can typically select a" +" specific coordinate operation by using the new PROJ projinfo utility " +"that can return the candidate operations from a source_crs / target_crs " +"tuple." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:186 +msgid "" +"When no option is specified, GDAL will use PROJ to list all candidate " +"coordinate operations. For each call to Transform(), it will compute the " +"average coordinate of the input coordinates and use it to determine the " +"best coordinate operation from the candidate ones." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:191 +msgid "" +"The Transform() method now takes an extra argument to contain the " +"coordinate epoch (generally as a decimal year value) for coordinate " +"operations that are time-dependent. Related, the transform options of the" +" GDALTransform mechanism typically used by gdalwarp now accepts a " +"COORDINATE_EPOCH for the same purpose." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:198 +msgid "Use of OGRSpatialReference in GDAL" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:200 +msgid "" +"Currently GDAL datasets accept and return a WKT 1 string to describe the " +"SRS. To be more independent of the actual encoding, and for example " +"allowing a GeoPackage raster dataset to be able to use WKT 2, it is " +"desirable to be able to attach a SRS that is not dependent of the " +"representation (WKT 1 or WKT 2), hence using a OGRSpatialReference object" +" instead of a const char\\* string." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:207 +msgid "The following new methods are added in GDALDataset:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:209 +msgid "virtual const OGRSpatialReference\\* GetSpatialRef() const;" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:210 +msgid "virtual CPLErr SetSpatialRef(const OGRSpatialReference*);" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:211 +msgid "virtual const OGRSpatialReference\\* GetGCPSpatialRef() const;" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:212 +msgid "" +"virtual CPLErr SetGCPs(int nGCPCount, const GDAL_GCP *pasGCPList, const " +"OGRSpatialReference*);" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:215 +msgid "" +"To ease the transition, the following non virtual methods are added in " +"GDALDataset:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:218 +msgid "const OGRSpatialReference\\* GetSpatialRefFromOldGetProjectionRef() const;" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:220 +msgid "" +"CPLErr OldSetProjectionFromSetSpatialRef(const OGRSpatialReference\\* " +"poSRS);" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:222 +msgid "" +"const OGRSpatialReference\\* GetGCPSpatialRefFromOldGetGCPProjection() " +"const;" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:224 +msgid "" +"CPLErr OldSetGCPsFromNew( int nGCPCount, const GDAL_GCP \\*pasGCPList, " +"const OGRSpatialReference \\* poGCP_SRS );" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:227 +msgid "" +"and the previous GetProjectionRef(), SetProjection(), GetGCPProjection() " +"and SetGCPs() are available as projected virtual methods, prefixed by an " +"underscore" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:231 +msgid "" +"This way to convert an existing driver, it is a matter of renaming its " +"GetProjectionRef() method as \\_GetProjectionRef(), and adding:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:241 +msgid "Default WKT version" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:243 +msgid "" +"OGRSpatialReference::exportToWkt() without options will report WKT 1 " +"(with explicit AXIS nodes. See below \"Axis order issues\" paragraph) for" +" CRS compatibles of this representation, and otherwise use WKT2:2018 " +"(typically for Geographic 3D CRS)." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:248 +msgid "" +"An enhanced version of exportToWkt() accepts options to specify the exact" +" WKT version used, if multi-line or single-line output must be used, etc." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:252 +msgid "" +"Alternatively the OSR_WKT_FORMAT configuration option can be used to " +"modify the WKT version used by exportToWk() (when no explicit version is " +"passed in the options of exportToWkt())" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:256 +msgid "" +"The gdalinfo, ogrinfo and gdalsrsinfo utililies will default to " +"outputting WKT2:2018" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:260 +msgid "Axis order issues" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:262 +msgid "" +"This is a recurring pain point. This RFC proposes a new approach (without" +" pretending to solving it completely) to what was initially done per `RFC" +" 20: OGRSpatialReference Axis Support <./rfc20_srs_axes>`__. The issue is" +" that CRS official definitions use axis orders that do not conform to the" +" way raster or vector data is traditionally encoded in GIS applications. " +"The typical example is the Geographic \"WGS 84\" definition from EPSG, " +"EPSG:4326, which uses latitude as the first axis and longitude as the " +"second axis. RFC 20 decided that by default the AXIS definition would be " +"stripped off from the WKT when the axis order from the authority did not " +"match the GIS friendly one (and use a custom EPSGA authority to have WKT " +"with official AXIS elements)" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:274 +msgid "" +"This was technically possible since the WKT 1 grammar makes the AXIS " +"element definition. However removal of the AXIS definitions was a " +"potential source of confusion as it was unclear which axis order was " +"actually used. Furthermore, in WKT2, the AXIS element is compulsory, and " +"the internal PROJ representation requires also a coordinate system to be " +"defined. So there would have been two unsatisfactory options:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:281 +msgid "" +"return patched versions of the official definition with the GIS friendly " +"order, while still using the official authority code. Practical since we " +"keep the link with the source code, but a lie since we modify it. Users " +"would not know whether they must trust the encoded order, or the official" +" order from the authority." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:286 +msgid "" +"return patched versions of the official definition with the GIS friendly " +"order, but without the official authority code. This would be compliant, " +"but we would lose the link with the authority code." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:290 +msgid "" +"The solution put forward in this RFC is to add a \"data axis to SRS axis " +"mapping\" concept, which is a bit similar to what is done in WCS " +"DescribeCoverage response to explain how the SRS axis map to the grid " +"axis of a coverage" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:295 +msgid "" +"Extract from " +"`https://docs.geoserver.org/stable/en/user/extensions/wcs20eo/index.html " +"<https://docs.geoserver.org/stable/en/user/extensions/wcs20eo/index.html>`__" +" for a coverage that uses EPSG:4326" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:308 +msgid "" +"A similar mapping is added to define how the 'x' and 'y' components in " +"the geotransform matrix or in a OGRGeometry map to the axis defined by " +"the CRS definition." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:312 +msgid "Such mapping is given by a new method in OGRSpatialReference" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:318 +msgid "" +"To explain its semantics, imagine that it return 2,-1,3. That is " +"interpreted as:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:321 +msgid "2: the first axis of the CRS maps to the second axis of the data" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:322 +msgid "" +"-1: the second axis of the CRS maps to the first axis of the data, with " +"values negated" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:324 +msgid "3: the third axis of the CRS maps to the third axis of the data" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:326 +msgid "" +"This is similar to the PROJ axisswap operation: " +"`https://proj4.org/operations/conversions/axisswap.html " +"<https://proj4.org/operations/conversions/axisswap.html>`__" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:329 +msgid "" +"By default, on a newly create OGRSpatialReference object, " +"GetDataAxisToSRSAxisMapping() returns the identity 1,2[,3], that is, " +"conform to the axis order defined by the authority." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:333 +msgid "" +"As all GDAL and a vast majority of OGR drivers depend on using the \"GIS " +"axis mapping\", a method SetAxisMappingStrategy( " +"OAMS_TRADITIONAL_GIS_ORDER or OAMS_AUTHORITY_COMPLIANT or OAMS_CUSTOM ) " +"is added to make their job of specifying the axis mapping easier;" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:338 +msgid "OAMS_TRADITIONAL_GIS_ORDER means:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:340 +msgid "for geographic 2D CRS," +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:342 +msgid "" +"for Latitude NORTH, Longitude EAST (such as EPSG:4326), " +"GetDataAxisToSRSAxisMapping() returns {2,1}, meaning that the data order " +"is longitude, latitude" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:345 +msgid "for Longitude EAST, Latitude NORTH (such as OGC:CRS84), returns {1,2}" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:348 +msgid "for projected CRS," +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:350 +msgid "for EAST, NORTH (ie most projected CRS), return {1,2}" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:351 +msgid "for NORTH, EAST, return {2,1}" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:352 +msgid "" +"for North Pole CRS, with East/SOUTH, North/SOUTH, such as EPSG:5041 " +"(\"WGS 84 / UPS North (E,N)\"), would return {1,2}" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:354 +msgid "" +"for North Pole CRS, with northing/SOUTH, easting/SOUTH, such as " +"EPSG:32661 (\"WGS 84 / UPS North (N,E)\"), would return {2,1}" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:356 +msgid "similarly for South Pole CRS" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:357 +msgid "for all other cases, return {1,2}" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:359 +msgid "" +"OGRCreateCoordinateTransformation() now honors the data axis to srs axis " +"mapping." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:362 +msgid "" +"Note: contrary to what I indicated in a previous email, gdaltransform " +"behavior is unchanged, since internally the GDALTransform mechanism " +"forces the GIS friendly order." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:366 +msgid "" +"Raster datasets are modified to call " +"SetAxisMappingStrategy(OAMS_TRADITIONAL_GIS_ORDER) on the " +"OGRSpatialReference\\* they return, and assumes it in SetSpatialRef() " +"(assumed and unchecked for now)" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:371 +msgid "" +"Vector layers mostly all call " +"SetAxisMappingStrategy(OAMS_TRADITIONAL_GIS_ORDER) on the " +"OGRSpatialReference\\* returned by GetSpatialRef(). In the case of the " +"GML driver, if the user defines the INVERT_AXIS_ORDER_IF_LAT_LONG open " +"option, axis swapping is not done (as previously) and the " +"AUTHORITY_COMPLIANT strategy is used. ICreateLayer() when receiving a " +"OGRSpatialReference\\* may decide (and most will do it) to change the " +"axis mapping strategy. That is: if it receives a OGRSpatialReference with" +" AUTHORITY_COMPLIANT order, it may decide to switch to " +"TRADITIONAL_GIS_ORDER and GetSpatialRef()::GetDataAxisToSRSAxisMapping() " +"will reflect that. ogr2ogr is modified to do the geometry axis swapping " +"in that case." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:384 +msgid "" +"Related to that change, WKT 1 export now always return the AXIS element, " +"and EPSG:xxxx thus behaves identically to EPSGA:xxxx" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:387 +msgid "" +"So a summary view of this approach is that in the formal SRS definition, " +"we no longer do derogations regarding axis order, but we add an " +"additional interface to describe how we actually make our match match " +"with the SRS definition." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:393 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:158 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:432 +msgid "Driver changes" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:395 +msgid "" +"Raster drivers that returned / accepted a SRS as a WKT string through the" +" GetProjectionRef(), SetProjection(), GetGCPProjection() and SetGCPs() " +"methods have been upgraded to use the new virtual methods, in most cases " +"by using the compatibility layer." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:400 +msgid "" +"The GDALPamDataset (PAM .aux.xml files) and the GDAL VRT drivers have " +"been fully upgraded to support the new interfaces, and " +"serialize/deserialize the data axis to SRS axis mapping values." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:404 +msgid "" +"The GeoPackage driver now fully supports the official \"gpkg_crs_wkt\" " +"extension used to store WKT 2 string definitions in the " +"gpkg_spatial_ref_sys table. The driver attempts at not using the " +"extension when SRS can be encoded as WKT1 strings, and will automatically" +" add the \"definition_12_063\" column to an existing gpkg_spatial_ref_sys" +" table if a SRS requiring WKT2 (typically a Geographic 3D CRS) is " +"inserted." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:415 +msgid "" +"gdalinfo and ogrinfo reports the data axis to CRS axis mapping whenever a" +" CRS is reported. They will also output WKT2_2018 by default, unless " +"\"-wkt_format wkt1\" is specified." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:447 +msgid "" +"gdalwarp, ogr2ogr and gdaltransform have gained a -ct switch that can be " +"used by advanced users to specify a coordinate operation, either as a " +"PROJ string (generally a +proj=pipeline), or a WKT coordinate " +"operation/concatenated operation, as explained in the above " +"\"OGRCoordinateTransformation changes\" paragraph. Note: the pipeline " +"must take into account the axis order of the CRS, even if the underlying " +"raster/vector drivers use the \"GIS friendly\" order. For example " +"\"+proj=pipeline +step +proj=axisswap +order=2,1 +step +proj=unitconvert " +"+xy_in=deg +xy_out=rad +step +proj=utm +zone=31 +ellps=WGS84\" when " +"transforming from EPSG:4326 to EPSG:32631." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:458 +msgid "" +"gdalsrsinfo is enhanced to be able to specify the 2 new supported WKT " +"variants: WKT2_2015 and WKT2_2018. It will default to outputting " +"WKT2_2018" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:463 +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:184 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:403 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:184 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:192 +msgid "SWIG binding changes" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:465 +msgid "" +"The enhanced ExportToWkt() and OGRCoordinateTransformation methods are " +"available through SWIG bindings. May require additional typemaps for non-" +"Python languages (particularly for the support of 4D X,Y,Z,time " +"coordinates)" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:473 +msgid "" +"This work is intended to be *mostly* backward compatible, yet inevitable " +"differences will be found. For example the WKT 1 and PROJ string export " +"has been completely rewritten in PROJ, and so while being hopefully " +"equivalent to what GDAL 2.4 or earlier generated, this is not strictly " +"identical: number of significant digits, order of PROJ parameters, " +"rounding, etc etc..." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:480 +msgid "MIGRATION_GUIDE.TXT has been updated to reflect some differences:" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:482 +msgid "OSRImportFromEPSG() takes into account official axis order." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:483 +msgid "" +"removal of OPTGetProjectionMethods(), OPTGetParameterList() and " +"OPTGetParameterInfo() No equivalent." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:485 +msgid "" +"removal of OSRFixup() and OSRFixupOrdering(): no longer needed since " +"objects constructed are always valid" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:487 +msgid "" +"removal of OSRStripCTParms(). Use OSRExportToWktEx() instead with the " +"FORMAT=SQSQL option" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:489 +msgid "exportToWkt() outputs AXIS nodes" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:490 +msgid "" +"OSRIsSame(): now takes into account data axis to CRS axis mapping, unless" +" IGNORE_DATA_AXIS_TO_SRS_AXIS_MAPPING=YES is set as an option to " +"OSRIsSameEx()" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:493 +msgid "" +"ogr_srs_api.h: SRS_WKT_WGS84 macro is no longer declared by default since" +" WKT without AXIS is too ambiguous. Preferred remediation: use " +"SRS_WKT_WGS84_LAT_LONG. Or #define USE_DEPRECATED_SRS_WKT_WGS84 before " +"including ogr_srs_api.h" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:498 +msgid "" +"Out-of-tree raster drivers will be impacted by the introduction of the " +"new virtual methods GetSpatialRef(), SetSpatialRef(), GetGCPSpatialRef() " +"and SetGCPs(..., const OGRSpatialReference\\* poSRS), and the removal of " +"their older equivalents using WKT strings instead of a " +"OGRSpatialReference\\* instance." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:507 +msgid "" +"New methods have been documented, and documentation of existing methods " +"has been changed when appropriate during the development. That said, a " +"more thorough pass will be needed. The tutorials will also have to be " +"updated." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:515 +msgid "" +"The autotest suite has been adapted in a number of places since the " +"expected results have changed for a number of reasons (AXIS node exported" +" in WKT, differences in WKT and PROJ string generation). New tests have " +"been added for the new capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:520 +msgid "" +"It should be noted that autotest not necessarily checks everything, and " +"issues have been discovered and fixed through manual testing. The " +"introduction of the \"data axis to CRS axis mapping\" concept is also " +"quite error prone, as it requires setting the OAMS_TRADITIONAL_GIS_ORDER " +"strategy in a lot of different places." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:526 +msgid "" +"So users and developers are kindly invited to thoroughly test GDAL once " +"this work has landed in master." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:532 +msgid "" +"Done by Even Rouault, `Spatialys <http://www.spatialys.com>`__. Available" +" per `PR 1185 <https://github.com/OSGeo/gdal/pull/1185>`__ Funded through" +" `gdalbarn <https://gdalbarn.com/>`__ sponsoring." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:536 +msgid "" +"While it is provided as a multiple commit for \"\"\"easier\"\"\" review, " +"it will be probably squashed in a single commit for inclusion in master, " +"as intermediate steps are not all buildable, due to PROJ symbol renames " +"having occurred during the development, which would break bisectability." +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:544 +msgid "Adopted with +1 from PSC members HowardB, JukkaR, DanielM and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:547 +msgid "Modifications" +msgstr "" + +#: ../../source/development/rfc/rfc73_proj6_wkt2_srsbarn.rst:549 +msgid "2019-May-02: change mentions of GDAL 2.5 to GDAL 3.0" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:5 +msgid "RFC 74: Migrate gdal.org to RTD-style Sphinx infrastructure" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:10 +msgid "howard@hobu.co" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:11 +msgid "2019-May-19" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:12 +msgid "*Adopted*" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:18 +msgid "" +"The document proposes migrating the GDAL documentation from a Doxygen to " +"`Sphinx <http://www.sphinx-doc.org/en/master/>`__ in `ReadTheDocs " +"<https://readthedocs.org>`__ format." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:25 +msgid "" +"Casual contribution to the GDAL documentation is challenging. Wiki-style " +"contribution is possible through the Trac instance, but that requires " +"getting an OSGeo login, which is a high bar, and the Trac information is " +"disconnected from the primary documentation. Other projects such as PROJ " +"and `MapServer <https://mapserver.org>`__ have seen significant uptick in" +" contributed documentation by adopting Sphinx-based systems, and we hope " +"the adoption of this approach for GDAL will ignite a renaissance of " +"documentation contribution as it did for those projects." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:34 +msgid "" +"The current approach has some significant deficiencies that have not been" +" overcome by waiting for new versions of Doxygen to arrive. These " +"include:" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:38 +msgid "" +"The Doxygen build buries the source of the documentation deep into the " +"source tree, which makes it hard to find where to properly add " +"information." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:41 +msgid "" +"The structure of the website is indirect from the source code that " +"creates it." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:43 +msgid "" +"New features such as convenient mobile-friendly styling, alternative " +"serializations such as PDF, and tighter API and user-level documentation " +"integration are not within easy reach." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:46 +msgid "" +"Editing of raw HTML means that convenient output of other serialization " +"types, such as PDF, Windows Compiled Help, or manpage output is " +"challenging." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:53 +msgid "" +"The GDAL team will refactor the GDAL.org website to be based on Sphinx " +"with the following properties:" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:56 +msgid "Convert the bulk of the existing documentation to reStructuredText" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:57 +msgid "" +"Adapt the `ReadTheDocs theme <https://sphinx-rtd-" +"theme.readthedocs.io/en/stable/>`__" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:59 +msgid "" +"Apply an \"Edit this Page on GitHub\" link to every page on the site for " +"convenient contribution" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:61 +msgid "" +"Utilize `GitHub Pages <https://pages.github.com/>`__ to host gdal.org, " +"with updates being regenerated and committed to a repository by `Azure " +"Pipelines <https://dev.azure.com/osgeo/gdal/_build>`__ continuous " +"integration." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:66 +msgid "" +"Output a PDF serialization of the website for documentation version " +"posterity." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:70 +msgid "Considerations" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:72 +msgid "" +"Numerous hard links to driver pages exist in source code. Care must be " +"taken to attempt to preserve these links as well as possible with " +"redirects to adapt to any new organization." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:75 +msgid "" +"Porting of existing Trac content to the new data structure will allow " +"decommission of that piece of infrastructure. Significant content porting" +" investment may be required to achieve this." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:78 +msgid "" +"Doxygen API-style documents are still valuable, and we propose to keep a " +"rendering of them at ``/doxygen`` for users who wish to continue with " +"that approach. Internal API documentation will continue to use Doxygen, " +"and it will be reflected into the Sphinx website using the Breathe " +"capability." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:83 +msgid "" +"Initial content organization will attempt to mimic the existing website " +"as well as can be achieved, but no requirement to maintain adherence to " +"the previous structure is required if other organization approaches are " +"more convenient given the features and capabilities of Sphinx." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:88 +msgid "" +"Existing translations will not be ported. Adaptation and continuation of " +"porting of translations is beyond the scope of this RFC, but there are " +"capabilities for managing translations in Sphinx (MapServer.org provides " +"an excellent example), and follow-on contributors can keep moving forward" +" with the architecture once the initial effort is complete." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:94 +msgid "" +"Content may be missed during the transition. Please file tickets in " +"GitHub for any items that became more difficult to find or are gone after" +" the transition." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:99 +msgid "Logistics" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:101 +msgid "" +"A current example of the site lives at `https://gdal.dev " +"<https://gdal.dev>`__ This example is set to noindex. Once the RFC is " +"passed, adaptation of the infrastructure that builds it will be migrated " +"to `https://gdal.org <https://gdal.org>`__ and the example website will " +"be completely decommissioned. Currently, `https://github.com/hobu/gdal " +"<https://github.com/hobu/gdal>`__ ``doc-sprint`` branch is the fork that " +"drives this content. It will be squash-merged to the main repository at " +"the passing of the RFC." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:112 +msgid "`issue #1204 <https://github.com/OSGeo/gdal/issues/1204>`__." +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:113 +msgid "" +"`2019 OSGeo Community Code Sprint " +"<https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2019>`__" +msgstr "" + +#: ../../source/development/rfc/rfc74_sphinx.rst:119 +msgid "+1 from KurtS, HowardB, DanielM, NormanB, JukkaR and EvenR." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:5 +msgid "RFC 75: Multidimensional arrays" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:10 +msgid "2019-May-24" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:11 +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:11 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:11 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:11 +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:11 +msgid "Last updated:" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:11 +msgid "2019-Jul-22" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:12 +msgid "Implemented in GDAL 3.1" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:18 +msgid "" +"This document describes the addition of read/write support for " +"multidimensional arrays, in particular of dimension 3 or above, in GDAL " +"core and a few select drivers." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:24 +msgid "" +"Multidimensional arrays (also known as hypercubes) are a way of mоdelling" +" spatio-temporal (time series of 2D raster) or spatio-vertical-temporal " +"(2D + Z dimension + time dimension) data which are becoming increasingly " +"more available. GDAL current raster model is however strongly 2D " +"oriented. A number of drivers, such as netCDF, HDF4, HDF5, work around " +"that limitation by using raster bands or subdatasets to expose muliple 2D" +" slices of what is intrinsically a N>2 Multidimensional dataset. It is " +"desirable to have a proper API, and driver support, to be able to expose " +"those multidimensional arrays as such, and be able to perform slice and " +"trim operations on them." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:34 +msgid "" +"That topic had already been discussed in the past, in particular in this " +"`mailing list thread <https://lists.osgeo.org/pipermail/gdal-" +"dev/2017-October/047472.html>`_" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:40 +msgid "" +"A lot of existing GDAL raster API are strongly 2D oriented. Rather than " +"upgrading all those API, and driver code, to be ready for N arbitrary " +"dimensions, which would be a enormous effort for the benefit of only a " +"small fraction of drivers, we propose to add a new dedicated API to " +"support multidimensional arrays. We also want to support hierarchical " +"structure of data as found in the `HDF5 format and data model " +"<https://portal.opengeospatial.org/files/81716>`_. This model can " +"encompass the needs of other formats/drivers that have multidimensional " +"capabilities such as HDF4, netCDF, GRIB, WCS. Therefore the proposed API " +"will be strongly inspired by the API of the HDF5 library itself." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:51 +msgid "Data model" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:52 +msgid "" +"The data model is described in: " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/user/multidim_raster_data_model.rst" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:58 +msgid "" +"New classes and methods will be added. See " +"https://github.com/rouault/gdal/blob/rfc75/gdal/gcore/gdal_priv.h#L1715" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:61 +msgid "" +"A new driver capability will be added for drivers supporting " +"multidimensional rasters:" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:69 +msgid "" +"A new open flag, ``GDAL_OF_MULTIDIM_RASTER``, for :cpp:func:`GDALOpenEx` " +"will be added. When this is specified, drivers supporting " +"multidimensional raster will return a root GDALGroup. Otherwise their " +"current traditional 2D mode will still be used." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:74 +msgid "" +"New creation options metadata items are added to documents " +"multidimensional dataset, group, dimension, array and attribute creation " +"options." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:104 +msgid "Examples with the netCDF driver:" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:154 +msgid "" +"All C++ methods are mapped to the C API. See " +"https://github.com/rouault/gdal/blob/rfc75/gdal/gcore/gdal.h#L1397" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:160 +msgid "The MEM driver will implement read and write support." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:161 +msgid "" +"The VRT driver will allow extraction of 2D slices from multidimensional " +"drivers to 2D/classic drivers, as well as " +"multidimensional->multidimensional slicing/trimming" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:164 +msgid "The netCDF driver will implement read and write support." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:165 +msgid "The HDF4 and HDF5 drivers will implement read support." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:166 +msgid "" +"The GRIB driver will implement read support (exposing X,Y,Time arrays for" +" GRIB messages only differing by timestamp)" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:170 +msgid "New Utilities" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:172 +msgid "" +"A new gdalmdiminfo utility is added to report the hierarchical structure " +"and content. Its output format is JSON. See " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/programs/gdalmdiminfo.rst" +" for its documentation." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:176 +msgid "" +"A new gdalmdimtranslate utility is added to convert multidimensional " +"raster between different formats, and/or can perform selective conversion" +" of specific arrays and groups, and/or subsetting operations. It can also" +" do extraction of 2D slices from multidimensional drivers to 2D/classic " +"drivers. See " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/programs/gdalmdimtranslate.rst" +" for its documentation." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:186 +msgid "" +"The C API is mapped to the SWIG bindings. The scope is complete for the " +"Python bindings. Other languages would need to add missing typemaps, but " +"this is not in the scope of the work of this RFC. For Python bindings, " +"NumPy integration is done." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:194 +msgid "" +"This is intended to be a preliminary work on that topic. While the aim is" +" for it to be be usable for the defined scope, it will probably require " +"future enhancements to fill functional and/or performance gaps." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:198 +msgid "No block cache mechanism (not sure this is needed)" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:199 +msgid "No sub-pixel requests, or non-nearest subsampling" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:200 +msgid "" +"Upgrade of WCS driver or other drivers with potential multidimensional " +"capabilities are not part of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:202 +msgid "SWIG bindings: full scope only for Python bindings." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:207 +msgid "No backward incompatibility. Only API and utility additions." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:212 +msgid "" +"Data model: " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/user/multidim_raster_data_model.rst" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:213 +msgid "" +"API tutorial: " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/tutorials/multidimensional_api_tut.rst" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:214 +msgid "" +"gdalmdiminfo: " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/programs/gdalmdiminfo.rst" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:215 +msgid "" +"gdalmdimtranslate: " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/programs/gdalmdimtranslate.rst" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:216 +msgid "" +"VRT driver: " +"https://github.com/rouault/gdal/blob/rfc75/gdal/doc/source/drivers/raster/vrt_multidimensional.rst" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:221 +msgid "" +"The gdalautotest suite is extended to test the modified drivers and the " +"new utilities." +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:227 +msgid "" +"The implementation will be done by Even Rouault. A preliminary " +"implementation is available at https://github.com/OSGeo/gdal/pull/1704" +msgstr "" + +#: ../../source/development/rfc/rfc75_multidimensional_arrays.rst:234 +msgid "+1 from HowardB, NormanB and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:5 +msgid "RFC 76: OGR Python drivers" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:10 +msgid "2019-Nov-5" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:11 +msgid "2019-Nov-15" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:12 +msgid "Adopted, implemented in GDAL 3.1" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:18 +msgid "This RFC adds the capability to write OGR/vector drivers in Python." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:23 +msgid "" +"For some use cases that do not require lighting speed, or to deal with " +"very niche formats (possibly in house format), it might be faster and " +"more efficient to write a vector driver in Python rather than a GDAL C++ " +"driver as currently required, or an ad-hoc converter." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:30 +msgid "" +"QGIS has now a way to create Python-based providers such as in " +"https://github.com/qgis/QGIS/blob/master/tests/src/python/provider_python.py" +" Having a way to do in GDAL itself also allows the rest of GDAL/OGR based" +" tools to use the OGR Python driver." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:36 +msgid "How does that work ?" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:39 +msgid "Driver registration" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:41 +msgid "" +"The driver registration mechanism is extended to look for .py scripts in " +"a dedicated directory:" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:44 +msgid "" +"the directory pointed by the :config:`GDAL_PYTHON_DRIVER_PATH` " +"configuration option (there may be several paths separated by `:` on Unix" +" or `;` on Windows)" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:46 +msgid "" +"if not defined, the directory pointed by the :config:`GDAL_DRIVER_PATH` " +"configuration option." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:48 +msgid "" +"if not defined, in the directory (hardcoded at compilation time on Unix " +"builds) where native plugins are located." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:51 +msgid "Those Python script must set in their first lines at least 2 directives:" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:53 +msgid "``# gdal: DRIVER_NAME = \"short_name\"``" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:54 +msgid "" +"``# gdal: DRIVER_SUPPORTED_API_VERSION = 1`` . Currently only 1 " +"supported. If the interface changed in a backward incompatible way, we " +"would increment internally the supported API version number. This item " +"enables us to check if we are able to \"safely\" load a Python driver. If" +" a Python driver would support several API versions (not clear if that's " +"really possible at that point), it might use an array syntax to indicate " +"that, like ``[1,2]``" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:60 +msgid "``# gdal: DRIVER_DCAP_VECTOR = \"YES\"``" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:61 +msgid "``# gdal: DRIVER_DMD_LONGNAME = \"my super plugin\"``" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:63 +msgid "" +"Optional metadata such as ``# gdal: DRIVER_DMD_EXTENSIONS`` or ``# gdal: " +"DRIVER_DMD_HELPTOPIC`` can be defined (basically, any driver metadata key" +" string prefixed by ``# gdal: DRIVER_``" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:67 +msgid "" +"These directives will be parsed in a pure textual way, without invocation" +" of the Python interpreter, both for efficiency consideration and also " +"because we want to delay the research or launch of the Python interpreter" +" as much as possible (the typical use case if GDAL used by QGIS: we want " +"to make sure that QGIS has itself started Python, to reuse that Python " +"interpreter)" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:73 +msgid "" +"From the short metadata, the driver registration code can instantiate " +"GDALDriver C++ objects. When the Identify() or Open() method is invoked " +"on that object, the C++ code will:" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:77 +msgid "" +"if not already done, find Python symbols, or start Python (see below " +"paragraph for more details)" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:79 +msgid "if not already done, load the .py file as a Python module" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:80 +msgid "" +"if not already done, instantiate an instance of the Python class of the " +"module deriving from ``gdal_python_driver.BaseDriver``" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:82 +msgid "" +"call the ``identify`` and ``open`` method depending on the originated " +"API call." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:84 +msgid "" +"The ``open`` method will return a Python ``BaseDataset`` object with " +"required and optional methods that will be invoked by the corresponding " +"GDAL API calls. And likewise for the ``BaseLayer`` object. See the " +"example_." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:89 +msgid "Connection with the Python interpreter" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:91 +msgid "" +"The logic will be shared with the VRT pixel functions written in Python " +"functionality It relies on runtime linking to the Python symbols already " +"available in the process (for example the python executable or a binary " +"embedding Python and using GDAL, such as QGIS), or loading of the Python " +"library in case no Python symbols are found, rather than compile time " +"linking. The reason is that we do not know in advance with which Python " +"version GDAL can potentially be linked, and we do not want " +"gdal.so/gdal.dll to be explicitly linked with a particular Python " +"library." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:100 +msgid "This is both embedding and extending Python." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:102 +msgid "The steps are:" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:104 +msgid "" +"through dlopen() + dlsym() on Unix and " +"EnumProcessModules()+GetProcAddress() on Windows, look for Python " +"symbols. If found, use it. This is for example the case if GDAL is used " +"from a Python module (GDAL Python bindings, rasterio, etc.) or an " +"application like QGIS that starts a Python interpreter." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:108 +msgid "" +"otherwise, look for the PYTHONSO environment variable that should point " +"to a pythonX.Y[...].so/.dll" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:110 +msgid "" +"otherwise, look for the python binary in the path and try to identify the" +" correspond Python .so/.dll" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:112 +msgid "" +"otherwise, try to load with dlopen()/LoadLibrary() well-known names of " +"Python .so/.dll" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:116 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:173 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:187 +msgid "Impacts on GDAL core" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:118 +msgid "" +"They are minimal. The GDALAllRegister() method has an added call to " +"GDALDriverManager::AutoLoadPythonDrivers() that implements the above " +"mentioned logic. The GDALDriver class has been extended to support a new " +"function pointer, IdentifyEx(), which is used by the C++ shim that loads " +"the Python code." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:127 +msgid "" +"This extended IdentifyEx() function pointer, which adds the GDALDriver* " +"argument, is used in priority by GDALIdentify() and GDALOpen() methods. " +"The need for that is purely boring. For normal C++ drivers, there is no " +"need to pass the driver, as there is a one-to-one correspondence between " +"a driver and the function that implements the driver. But for the Python " +"driver, there is a single C++ method that does the interface with the " +"Python Identify() method of several Python drivers, hence the need of a " +"GDALDriver* argument to forward the call to the appropriate driver." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:139 +msgid "Example of such a driver" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:141 +msgid "" +"Note that the prefixing by the driver name in the connection string is " +"absolutely not a requirement, but something specific to this particular " +"driver which is a bit artificial. The CityJSON driver mentioned below " +"does not need it." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:356 +msgid "Other examples:" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:358 +msgid "" +"a PASSTHROUGH driver that forwards calls to the GDAL SWIG Python API: " +"https://github.com/OSGeo/gdal/blob/master/examples/pydrivers/ogr_PASSTHROUGH.py" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:360 +msgid "" +"a driver implemented a simple parsing of `CityJSON " +"<https://www.cityjson.org/>`_: " +"https://github.com/OSGeo/gdal/blob/master/examples/pydrivers/ogr_CityJSON.py" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:364 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:179 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:129 +msgid "Limitations and scope" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:366 +msgid "Vector and read-only for now. This could later be extended of course." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:368 +msgid "" +"No connection between the Python code of the plugin and the OGR Python " +"API that is built on top of SWIG. This does not appear to be doable in a " +"reasonable way. Nothing prevents people from using the GDAL/OGR/OSR " +"Python API but the objects exchanged between the OGR core and the Python " +"code will not be OGR Python SWIG objects. A typical example is that a " +"plugin will return its CRS as a string (WKT, PROJSON, or deprecated " +"PROJ.4 string), but not as a osgeo.osr.SpatialReference object. But it is" +" possible to use the osgeo.osr.SpatialReference API to generate this WKT " +"string." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:378 +msgid "" +"This RFC does not try to cover the management of Python dependencies. It " +"is up to the user to do the needed \"pip install\" or whatever Python " +"package management solution it uses." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:382 +msgid "" +"The Python \"Global Interpreter Lock\" is held in the Python drivers, as " +"required for safe use of Python. Consequently scaling of such drivers is " +"limited." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:385 +msgid "" +"Given the above restrictions, this will remain an \"experimental\" " +"feature and the GDAL project will not accept such Python drivers to be " +"included in the GDAL repository. This is similar to the situation of the " +"QGIS project that allows Python plugins outside of the main QGIS " +"repository. If a QGIS plugin want to be moved into the main repository, " +"it has to be converted to C++. The rationale for this is that the " +"correctness of the Python code can mostly be checked at runtime, whereas " +"C++ benefits from static analysis (at compile time, and other checkers). " +"In the context of GDAL, this rationale also applies. GDAL drivers are " +"also stress-tested by the OSS Fuzz infrastructure, and that requires them" +" to be written in C++." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:396 +msgid "" +"The interface between the C++ and Python code might break between GDAL " +"feature releases. In that case we will increment the expected API version" +" number to avoid loading incompatible Python drivers. We will likely not " +"make any effort to be able to deal with plugins of incompatible " +"(previous) API version." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:408 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:191 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:197 +msgid "Security implications" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:410 +msgid "" +"Similar to the existing native code plugin mechanism of GDAL. If the user" +" defines the GDAL_PYTHON_DRIVER_PATH environment variable or " +"GDAL_DRIVER_PATH, annd put .py scripts in them (or in " +"{prefix}/lib/gdalplugins/python as a fallback), they will be executed." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:415 +msgid "" +"However, opening a .py file with GDALOpen() or similar mechanisms will " +"not lead to its execution, so this is safe for normal GDAL usage." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:418 +msgid "" +"The GDAL_NO_AUTOLOAD compile time #define, already used to disable " +"loading of native plugins, is also honoured to disable the loading of " +"Python plugins." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:422 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:197 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:202 +msgid "Performance impact" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:424 +msgid "" +"If no .py script exists in the researched location, the performance " +"impact on GDALAllRegister() should be within the noise." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:430 +msgid "No backward incompatibility. Only functionality addition." +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:435 +msgid "" +"A tutorial will be added to explain how to write such a Python driver: " +"https://github.com/rouault/gdal/blob/pythondrivers/gdal/doc/source/tutorials/vector_python_driver.rst" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:441 +msgid "" +"The gdalautotest suite will be extended with the above test Python " +"driver, and a few error cases: " +"https://github.com/rouault/gdal/blob/pythondrivers/autotest/ogr/ogr_pythondrivers.py" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:446 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:216 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:217 +msgid "Previous discussions" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:448 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:218 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:219 +msgid "This topic has been discussed in the past in :" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:450 +msgid "https://lists.osgeo.org/pipermail/gdal-dev/2017-April/thread.html#46526" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:451 +msgid "https://lists.osgeo.org/pipermail/gdal-dev/2018-November/thread.html#49294" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:456 +msgid "" +"A candidate implementation is available at in " +"https://github.com/rouault/gdal/tree/pythondrivers" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:459 +msgid "https://github.com/OSGeo/gdal/compare/master...rouault:pythondrivers" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:464 +msgid "+1 from EvenR, JukkaR, MateuzL, DanielM" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:465 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:238 +msgid "-0 from SeanG" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:466 +msgid "+0 from HowardB" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:469 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:238 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:241 +msgid "Credits" +msgstr "" + +#: ../../source/development/rfc/rfc76_ogrpythondrivers.rst:471 +msgid "Sponsored by OpenGeoGroep" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:5 +msgid "RFC 77: Drop Python 2 support in favour of Python 3.6" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:8 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:8 +msgid "Idan Miara" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:9 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:9 +msgid "idan@miara.com" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:10 +msgid "2020-Nov-3" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:11 +msgid "2020-Nov-29" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:12 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:12 +msgid "Adopted, implemented in GDAL 3.3" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:18 +msgid "" +"This RFC drops Python 2 support and sets Python 3.6 as the new minimum " +"supported Python version." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:23 +msgid "" +"Currently GDAL Python bindings support Python 2.7 and Python 3 (so only " +"the common between the two). Python 2 is at End Of Life, and is no longer" +" supported since the January 2020. https://www.python.org/doc/sunset-" +"python-2/" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:27 +msgid "" +"\"We did not want to hurt the people using Python 2. So, in 2008, we " +"announced that we would sunset Python 2 in 2015, and asked people to " +"upgrade before then. Some did, but many did not. So, in 2014, we extended" +" that sunset till 2020.\"" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:30 +msgid "" +"While keeping Python 2.7 support might serve those who didn't upgrade " +"their code to Python 3 in the 12 year transition period, This PR suggests" +" that the time has come and the benefits of dropping Python 2 support " +"outnumber the drawbacks. Virtually all supported OS and relevant programs" +" already use Python 3. Moreover, most of the related projects that " +"usually is used with GDAL already dropped Python 2 support (as can be " +"seen below). It makes sense that people who didn't upgrade their code in " +"12 years are still using a much older version of GDAL anyway..." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:36 +msgid "" +"The drawbacks of keeping Python 2 support puts unnecessary maintenance " +"burden on the GDAL maintainers, As maintainers need to make sure their " +"new code is backwards compatible with Python 2. Furthermore, many " +"important features that added in Python 3 cannot be used in GDAL to " +"maintain backwards compatibility with Python 2." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:41 +msgid "Related projects that dropped Python 2 support:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:43 +msgid "QGIS since v3.0 - February 2018. (now supports Python 3.7)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:45 +msgid "" +"https://www.qgis.org/en/site/forusers/visualchangelog30/index.html " +"https://qgis.org/api/api_break.html" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:48 +msgid "GRASS GIS since v7.8 - September 2019 (now supports Python 3.7)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:50 +msgid "https://trac.osgeo.org/grass/wiki/Python3Support" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:52 +msgid "pyproj since v2.3 - August 2019 (now supports Python 3.5-3.7)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:54 +msgid "https://pyproj4.github.io/pyproj/stable/history.html" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:56 +msgid "numpy since v1.19 - June 2020 (now supports Python Python 3.6-3.8)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:58 +msgid "https://numpy.org/devdocs/release/1.19.0-notes.html" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:60 +msgid "RasterIO since v1.1 - October 2019 (now supports Python 3.6)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:62 +msgid "" +"https://sgillies.net/2019/10/10/rasterio-1-1-0.html " +"https://github.com/mapbox/rasterio/issues/1813" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:66 +msgid "Python 3 version status:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:68 +msgid "" +"Python 3.5 (Released: Sep 2015) is End Of Life. Many related projects " +"already dropped support of it." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:69 +msgid "" +"Python 3.6 (Released: Dec 2016) will be End Of Life on Dec 2021. Python " +"3.6 brings many important features." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:70 +msgid "" +"Python 3.7 (Released: Jun 2018) will be End Of Life on Jun 2023. Python " +"3.7 is already widely adopted and supported by all the related projects " +"listed above." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:71 +msgid "" +"Python 3.8 (Released: Oct 2019) will be End Of Life on Oct 2024. Python " +"3.8 is too new to be set as the minimum supported version." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:73 +#, python-format +msgid "https://endoflife.date/python#:~:text=The%20support%20for%20Python%202.7,dropping%20support%20for%20Python%202.7." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:76 +msgid "Python 3 OS Support:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:79 +msgid "Linux:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:82 +msgid "Distribution" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:82 +msgid "Release date" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:82 +msgid "End Of Life" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:82 +msgid "Python Version" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:83 +msgid "Ubuntu 16.04 Xenial LTS" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:83 +msgid "April 2016" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:83 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:85 +msgid "April 2021" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:83 +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:86 +msgid "Python 3.5" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:84 +msgid "Ubuntu 18.04 Bionic LTS" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:84 +msgid "April 2018" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:84 +msgid "April 2023" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:84 +msgid "Python 3.6 (3.7 in universe)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:85 +msgid "Ubuntu 20.04 Xenial LTS" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:85 +msgid "April 2020" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:85 +msgid "Python 3.8" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:86 +msgid "Debian 9.0 Stretch LTS" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:86 +msgid "June 2017" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:86 +msgid "July 2022" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:87 +msgid "Debian 10.0 Buster LTS" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:87 +msgid "July 2019" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:87 +msgid "~2022" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:87 +msgid "Python 3.7" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:88 +msgid "Centos/RHEL 8" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:88 +msgid "September 2019" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:88 +msgid "?" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:88 +msgid "Python 3.6 (?)" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:89 +msgid "Amazon Linux" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:89 +msgid "December 2021" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:89 +msgid "Python 3.6" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:92 +msgid "https://wiki.python.org/moin/Python3LinuxDistroPortingStatus" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:96 +msgid "Windows:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:98 +msgid "Conda: Python 3.6-3.9" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:99 +msgid "OSGeo4W: Python 3.7" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:100 +msgid "gisinternals: Python 2.7, 3.4-3.7" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:103 +msgid "MacOS:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:105 +msgid "" +"It appears the even though Python 2.7 is preinstalled on Mac OS X, Python" +" 3.5-3.9 can be installed alongside Python 2 on Mac OS X 10.8 (Released: " +"July 2012) and newer." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:108 +msgid "https://docs.python.org/3.6/using/mac.html." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:111 +msgid "Which version should be the new minimum version ?" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:113 +msgid "" +"This RFC suggest the new minimum supported Python version should be 3.6 " +"for the following reasons:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:115 +msgid "Python < 3.6 is End of Life." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:120 +msgid "" +"Long list of great new features that were introduced in Python 3.6, " +"Several of which are immediately useful to simplify code or improve " +"testing:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:117 +msgid "f-strings" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:118 +msgid "builtin pathlib" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:119 +msgid "underscores in numeric literals" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:120 +msgid "type annotations" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:121 +msgid "malloc debugging" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:122 +msgid "Python 3.6 is supported out of the box in virtually every relevant OS." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:123 +msgid "" +"Python 3.6 is probably the safest choice for now in respect to other " +"related projects." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:124 +msgid "" +"Python 3.7 (and newer) isn't available seamlessly in some popular LTS " +"Linux distributions." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:125 +msgid "" +"We want to make the transition as smooth and easy as possible. Setting " +"the minimum to Python 3.7 might make the transition harder for the CI " +"because of the above reason." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:126 +msgid "" +"Dropping Python 3.6 in favour of Python 3.7 or newer in future versions " +"shouldn't be as hard as this drop (see next section for a suggested " +"approach)." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:129 +msgid "GDAL Release cycle and regular Python version dropping" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:131 +msgid "" +"When releasing GDAL 3.1.0, Even Rouault suggested GDAL would use fixed " +"release cycles of 6 months between major versions:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:133 +msgid "" +"http://osgeo-org.1560.x6.nabble.com/gdal-dev-Reconsidering-release-cycle-" +"length-td5436163.html#a5436242" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:135 +msgid "" +"Projecting from that suggestion, GDAL 3.3.0 should be released around " +"April-May 2021." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:137 +msgid "" +"We could potentially synchronize with NEP 29 - Recommend Python and Numpy" +" version support as a community policy standard. Which suggests when to " +"drop each Python version." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:141 +msgid "https://numpy.org/neps/nep-0029-deprecation_policy.html" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:143 +msgid "" +"NEP 29 suggests to drop support for Python 3.6 support on Jun 23, 2020 " +"(in favour of Python 3.7)." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:145 +msgid "" +"We could potentially discuss similar/more conservative approaches and " +"delay each drop by a few more months, or only drop Python versions that " +"have reached End Of Life (As of today, Python < 3.6 have reached End Of " +"Life). Further discussion on the matter of dropping other Python versions" +" is a subject for another RFC." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:152 +msgid "" +"Currently, GDAL Python code itself is compatible with Python 2 and Python" +" 3. Once this PR is accepted, GDAL 3.3.0 would not be compatible with " +"Python 2. Thus any \"Python 2 only\" code that uses GDAL would need to be" +" upgraded to Python 3 and at the same time the respective Python " +"interpreter would need to be upgraded to a supported Python version." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:159 +msgid "Will GDAL 3.2 be a LTS?" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:161 +msgid "" +"Currently - No. So far, nobody has stepped up to make a LTS, So there " +"won't be one unless someone takes it up upon themselves or raise funds to" +" make it happen. GDAL only provide bugfix releases of the current stable " +"branch for 6 months." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:166 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:181 +msgid "CI Impacts:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:168 +msgid "" +"Impacts on our CI should be analyzed. It seems that all our CI builds use" +" Python 2.7 or 3.5, so all of them would need to be adjusted. In " +"particular, builds that use older Linux distributions would need to be " +"upgraded." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:175 +msgid "" +"There should be no impacts on GDAL core, As the Python bindings are " +"generated by SWIG on top of the binary form of GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:181 +msgid "" +"The scope of this RFC should be the GDAL Python code alone. There " +"shouldn't be effect on any other language supported by GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:186 +msgid "" +"To begin with, the SWIG Python bindings already support Python 3.6. " +"Dropping Python 2 support might allow us to use a newer SWIG version or " +"to make some improvements to the bindings, but it doesn't have to be in " +"the first step." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:193 +msgid "" +"Python 3.6 is the minimum Python version that is not End Of Life, thus " +"still receiving security updates." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:199 +msgid "" +"There might be some performance gain for this upgrade for some uses as " +"there were many performance improvements between Python 2.7-3.6. The " +"scope of the improvements could be limited because most of GDAL Python " +"code is a thin wrapper around the C++ code." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:205 +msgid "" +"The GDAL Python documentation is generated automatically in should " +"already support Python 3. If there are sections in the documentation that" +" are Python 2 specific, they should be removed or refactored." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:211 +msgid "" +"While upgrading the CI, Python 2 tests should be removed or upgraded. A " +"simple test that fails on Python < 3.6 should be added. No any additional" +" tests should be needed." +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:220 +msgid "https://github.com/OSGeo/gdal/issues/3114" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:221 +msgid "https://github.com/OSGeo/gdal/pull/3142" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:224 +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:224 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:86 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:415 +msgid "Related PRs:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:226 +msgid "" +"Adding a deprecation warning if running a Python version that is known to" +" be unsupported in the next GDAL version:" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:228 +msgid "https://github.com/OSGeo/gdal/pull/3165" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:233 +msgid "https://lists.osgeo.org/pipermail/gdal-dev/2020-November/053039.html" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:235 +msgid "+1 from EvenR, HowardB, KurtS, JukkaR, DanielM" +msgstr "" + +#: ../../source/development/rfc/rfc77_drop_python2_support.rst:240 +msgid "implemented by Even Rouault, Robert Coup and Idan Miara" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:5 +msgid "RFC 78: gdal-utils package" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:10 +msgid "2020-Dec-3" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:11 +msgid "2021-March-26" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:18 +msgid "" +"This RFC suggests to put all the GDAL python modules (formly scripts), " +"except from the GDAL core SWIG bindings, into their own distribution on " +"pypi. The GDAL python sub-package `osgeo.utils` (introduced in GDAL 3.2) " +"would be renamed into a package named `osgeo_utils`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:22 +msgid "" +"The standalone python scripts from GDAL <= 3.1 were transformed to " +"`osgeo.utils` in GDAL 3.2. For backwards compatibility these scripts " +"still exist and function as tiny wrappers around the python modules. " +"Users of these scripts would not be effected from this RFC as the scripts" +" would continue to function in GDAL 3.3 in the same way as in GDAL <= " +"3.2." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:27 +msgid "" +"To allow maximum backwards compatibility, The `osgeo` package (which " +"includes the GDAL core SWIG bindings) and the `osgeo_utils` package will " +"continue to be distributed in a single `sdist` named `gdal` in `pypi`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:30 +msgid "" +"In addition, a new pure python `wheel` distribution named `gdal-utils` " +"will be available in `pypi` under the name `gdal-utils`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:33 +msgid "" +"This will allow users who wish to upgrade the utils without upgrading the" +" bindings to do so with `pip install --upgrade gdal-utils` (see more " +"details in the following sections)." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:47 +msgid "" +"Making gdal Python developers life easier on Windows (and maybe other " +"platforms):" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:40 +msgid "" +"The straightforward way of cloning `gdal` and adding `gdal/swig/python` " +"to Python path (In PyCharm: marking the it as a `Source Root`) won't work" +" because the `pyc` files are missing from `gdal/swig/python/osgeo`, thus " +"by adding `osgeo` to Python path we would be masking a binary " +"installation of gdal that might be already installed (i.e. `osgeo4w` or " +"Christoph Gohlke's binary Windows wheels). Workarounds, like copying the " +"`pyc` files to the `osgeo` dir, cause their own problems, like: * " +"Switching interpreters that have different versions of `gdal` causes more" +" problems. * Non clean git working tree so committing the changes to git " +"is harder. By moving the `gdal-utils` into another root this problem is " +"completely avoid." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:79 +msgid "Allow mixing `gdal` and `gdal-utils` versions" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:50 +msgid "" +"As the Python code evolves semi-independently of the GDAL core and is not" +" directly dependent on a specific GDAL version, one might want use the " +"latest `gdal-utils` package with an older version of `gdal` core " +"bindings, or vice versa. Currently, One would need to mix the contents " +"different `gdal` packages to do so." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:54 +msgid "" +"As the `gdal` package is platform specific, and requires compilation, In " +"some distributions upgrading to a new GDAL version might take more time, " +"so one could upgrade the `gdal-utils` package easily and independently of" +" upgrading the `gdal` package, using `pip install --upgrade gdal-utils`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:58 +msgid "" +"On the other hand, if we drop another Python version, like we just did " +"with Python 2.7, One might be still be able to use newer gdal core " +"bindings (which might still support an older version of Python) with an " +"older `gdal-utils`, Which might drop Python versions sooner." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:62 +msgid "Reasons why users wouldn't be able to upgrade to recent GDAL:" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:64 +msgid "" +"They use some LTS distribution (like Debian), or application (like QGIS " +"LTS)." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:65 +msgid "" +"Recent GDAL is not available for their platform or distribution (even if " +"not LTS)." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:66 +msgid "" +"Their code dependents on some binary gdal-plugin which is available for a" +" specific GDAL version." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:68 +msgid "" +"A concrete example would be someone who uses QGIS (or QGIS LTS) that " +"currently comes with GDAL 3.1, and wants to use the neat stuff added to " +"`gdal_calc`, With this RFC he could just `pip install --upgrade gdal-" +"utils`. Because this package package is Pure Python, upgrades should be " +"easy." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:72 +msgid "" +"Although each version of `gdal-utils` would only be tested against the " +"equivalent version of `gdal`, In most cases different versions would " +"still be compatible, but without guarantee." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:75 +msgid "" +"This RFC would make further testing the compatibility between different " +"versions of these packages easier and could be considered the first step " +"into making the `gdal-utils` package completely independent of the `gdal`" +" package. It would also potentially allow forward compatibility in case " +"we ever decide to remove the utils from the `gdal` wheel and keep them " +"only in the `gdal-utils` wheel." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:82 +msgid "Package Names and PyPi release:" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:84 +msgid "" +"This RFC suggests to keep the all-in-one package and in addition to " +"distribute a utils only package, In order to keep the required changes " +"from users to a minimum and at the same time allow mixing versions:" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:87 +msgid "https://pypi.org/project/GDAL/" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:89 +msgid "" +"Distribution of a single `pypi.org` wheel named `gdal` will be retained " +"and will includes both packages. This will insure smooth transition and " +"maximum backwards compatibility." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:92 +msgid "https://pypi.org/project/gdal-utils/" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:94 +msgid "" +"A new `pypi.org` package is introduced to include with just the " +"`osgeo_utils` package, which will allow upgrading the utils without " +"upgrading the bindings." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:97 +msgid "" +"To be consistent with the `gdal` `pypi` package name, the utils `pypi` " +"package is named `gdal-utils`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:99 +msgid "" +"the name `osgeo_utils` is consistent with the `osgeo` namespace and " +"module names." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:114 +msgid "How to upgrade the utils without upgrading the bindings:" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:116 +msgid "" +"> If someone installs the \"gdal\" all-in-one package and the \"gdal-" +"utils\" one. Wouldn't that conflict ?" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:118 +msgid "" +"`pip install` a wheel overwrites whichever files already exist (even if " +"installed by a different package) If you `pip install gdal` then `pip " +"install gdal-utils` you'd get the utils from `gdal-utils`. If later you " +"do again `pip install gdal` with a different version then you'd get the " +"utils from `gdal` again, and so on. (it doesn't seem that it matters " +"which version is a bigger number, just which one you installed later)" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:123 +msgid "" +"If you `pip install gdal` then `pip install gdal-utils` and then `pip " +"uninstall gdal-utils` then the utils would be uninstalled and you'd be " +"left with gdal without utils. Then you could `pip install gdal-utils` or " +"`pip install gdal --ignore-installed` to get them back again (`--ignore-" +"installed` is not required if you install a different version)" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:131 +msgid "" +"The scope of this RFC is the GDAL Python code, except for the SWIG " +"bindings. There is no effect on any other language supported by GDAL. " +"Because gdal core is tested using the Python SWIG bindings - this RFC " +"does not suggest changing them in any way. Binary wheel distribution - " +"discussed in the past and related to ideas in this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:138 +msgid "`gdal` and `gdal-utils` Compatibility" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:140 +msgid "" +"This RFC suggests that `gdal-utils` would continue to be only tested " +"against the same version of `gdal`. In most cases different versions " +"would still be compatible, but without guarantee." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:143 +msgid "" +"A minimum energy approach might keep `gdal-utils` compatible with some " +"`gdal` versions != `x.y`. `gdal-utils` might officially drop support of " +"some too old version of GDAL by specifying a newer minimum version of " +"GDAL in the `setup.py` of `gdal-utils`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:147 +msgid "" +"For maximum backwards compatibility and because we would only test `gdal`" +" against the same version of `gdal-utils` - `osgeo` and `osgeo_utils` " +"will continue to be distributed inside a single wheel in addition to the " +"new separate wheel for the utils only." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:151 +msgid "" +"In cases were an `gdal-utils` module or function actually does need a " +"minimum specific version of `gdal` (i.e. dependence on a new GDAL C API) " +"Compatibility could be checked at runtime by comparing to " +"`osgeo.__version__`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:155 +msgid "Versioning" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:157 +msgid "" +"As development of `gdal-utils` will be still tied with the development of" +" GDAL and will be released together with the same `x.y.z` version number." +" In case a hotfix to `gdal-utils` is required for some reason, a " +"`x.y.z.p` version might be used, Which will not effect the distribution " +"of version `z+1`, i.e. `3.3.0` < `3.3.0.1` < `3.3.1`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:164 +msgid "Backward compatibility issues:" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:166 +msgid "`osgeo.utils` will need be replaced with `osgeo_utils`" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:167 +msgid "" +"This is the only breaking change, only for GDAL=3.2, and only a single " +"character." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:168 +msgid "" +"`swig/python/scripts` - users of the gdal scripts (which are thin " +"wrappers around the utils) wouldn't be effected." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:172 +msgid "Folder structure change" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:174 +msgid "" +"`gdal/swig/python/osgeo/utils` -> `gdal/swig/python/gdal-" +"utils/osgeo_utils`" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:176 +msgid "" +"`gdal/swig/python/osgeo/setup.py` - was updated to include the utils from" +" the new location under the `gdal-utils` folder." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:178 +msgid "" +"`gdal/swig/python/gdal-utils/setup.py` - additional setup was added for " +"`gdal-utils`." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:183 +msgid "" +"`gdal-utils` wheel building could be added to the CI, i.e. like in " +"https://github.com/OSGeo/gdal/pull/3579 No other CI Impacts." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:209 +msgid "Implications of this change shell documented in the README." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:214 +msgid "Minor changes were made to pytest." +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:221 +msgid "" +"http://osgeo-org.1560.x6.nabble.com/gdal-dev-Call-for-discussion-on-RFC77" +"-Drop-Python-2-support-td5449659.html" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:226 +msgid "https://gdal.org/development/rfc/rfc77_drop_python2_support.html" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:227 +msgid "https://github.com/OSGeo/gdal/pull/3131" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:228 +msgid "https://github.com/OSGeo/gdal/pull/3117" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:229 +msgid "https://github.com/OSGeo/gdal/pull/3247" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:234 +msgid "" +"http://osgeo-org.1560.x6.nabble.com/gdal-dev-Motion-RFC-78-gdal-utils-" +"package-td5482707.html" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:236 +msgid "+1 from EvenR, HowardB" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:237 +msgid "+0 from KurtS, JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc78_gdal_utils_package.rst:243 +msgid "Implemented by the author of this RFC, Idan Miara." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:5 +msgid "RFC 79: Listing of Service Providers on GDAL website" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:8 +msgid "Daniel Morissette, Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:10 +msgid "2021-Feb-22" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:11 +msgid "2021-Mar-01" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:12 +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:12 +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:12 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:11 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:11 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:12 +msgid "Adopted" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:16 +msgid "1. Motivation" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:18 +msgid "" +"GDAL is developed and supported by a rich ecosystem of businesses and " +"individuals around the world but we do not do a good job of promoting " +"those service providers and making them easy to find by our users at the " +"moment." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:22 +msgid "" +"In this RFC, we propose a plan to address this by adding a Service " +"Providers page to the GDAL website." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:26 +msgid "2. Proposed plan" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:28 +msgid "A new Service Providers page will be added to the Sphinx documentation." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:30 +msgid "" +"The service providers will be grouped in three categories. The " +"descriptions below should make it relatively easy to determine in which " +"group a given organization belongs." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:34 +msgid "" +"Each qualified organization who wishes to be listed is responsible for " +"adding themselves to the correct category in the page through a pull " +"request (or a direct commit in case of core committers). We are " +"intentionally not providing instructions here for preparing the pull " +"request as it is expected that a qualified service provider should have " +"people on staff who can figure it out. Yes, we intentionally try to keep " +"the bar at a minimum level." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:42 +msgid "" +"A PSC vote is NOT required in order to add a new service provider, i.e. " +"any core committer can validate and commit the pull request (or their own" +" entry) but in case of doubts or disagreements on the interpretation of " +"the rules, the GDAL PSC will be the ultimate authority to resolve the " +"question." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:48 +msgid "" +"Organizations in each category are displayed in randomized order (except " +"in the PDF docs which are static). However entries should be added to the" +" source file in alphabetical order (for PDF docs purpose). The output " +"will be similar to https://mapserver.org/community/service_providers.html" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:55 +msgid "2.1 Core Contributors" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:57 +msgid "" +"Core Contributors are the organizations that have one or more Core " +"Committer (a person with merge rights in the GDAL GitHub repository) " +"and/or PSC members as part of their staff and who provide GDAL related " +"services to customers." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:62 +msgid "" +"To qualify, the Core Committers and/or PSC members must be directly " +"employed by the organization and not part time contractors." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:65 +msgid "" +"They get to add a 200px max high or wide logo with a descriptive text " +"outlining their qualifications and services." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:68 +msgid "2.2 Contributors" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:70 +msgid "" +"Contributors are organizations who provide GDAL related services and have" +" one or more people on their staff who are well known in the GDAL " +"community for their long term contributions to the project. Contributions" +" are not limited to source code and can also be in the form of " +"documentation, binary builds, active user support via the public forums, " +"etc." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:76 +msgid "" +"They get to add a 150px max high or wide logo with a descriptive text " +"outlining their qualifications and services." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:79 +msgid "2.3 Other Service Providers" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:81 +msgid "" +"Organization with GDAL expertise and providing services around GDAL can " +"fit in this category. While proprietary solutions providers are welcome, " +"we expect organizations listed here to be providing legitimate services " +"to users of the Open Source software as well. This is not an " +"advertisement board for proprietary products." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:87 +msgid "" +"They get to add a 100px max high or wide logo with a descriptive text " +"outlining their qualifications and services." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:90 +msgid "2.4 Refreshing the service providers list" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:92 +msgid "" +"If at some point (every 2 years?) we feel that the list is or might be no" +" longer current, we could bring it up to date as follows:" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:95 +msgid "create a GitHub ticket dedicated for the refresh" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:96 +msgid "" +"send an email to the list with this message \"in 4 weeks, we are going to" +" remove all currently listed service providers to refresh the site. If " +"you are still interested, add a note to ticket XXXX\"." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:100 +msgid "" +"Instead of the ticket we could just ask people to reply to the email but " +"the advantage of the ticket is to generate less email traffic for those " +"not interested. It leaves a trace of the list of organizations who " +"responded in a single place inside the ticket." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:105 +msgid "3. FAQ" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:107 +msgid "" +"Should we also recognize sponsors or organizations that are funding " +"significant features in this page?" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:110 +msgid "" +"No. This is a service provider page and not a sponsorship page. However " +"if the organization in question is also offering GDAL related services " +"they can be added to the relevant category. They just won't get special " +"status due to their financial contributions." +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:116 +msgid "4. Credits" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:118 +msgid "" +"This RFC is a straightforward adaptation of the equivalent MapServer one:" +" https://mapserver.org/development/rfc/ms-rfc-116.html" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:122 +msgid "5. Voting History" +msgstr "" + +#: ../../source/development/rfc/rfc79_listing_service_providers.rst:124 +msgid "+1 from PSC members MateuszL, KurtS, JukkaR, DanielM and EvenR." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:5 +msgid "RFC 7: Use VSILFILE for VSI*L Functions" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:7 +msgid "Author: Even Rouault (Eric Doenges is original author)" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:9 +msgid "Contact: even dot rouault at spatialys.com, Eric.Doenges@gmx.net" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:16 +msgid "" +"To change the API for the VSI*L family of functions to use a new data-" +"type VSILFILE instead of the current FILE." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:20 +msgid "Background, Rationale" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:22 +msgid "" +"Currently, GDAL offers two APIs to abstract file access functions " +"(referred to as VSI\\* and VSI\\ *L in this document). Both APIs claim to" +" operate on FILE pointers; however, the VSI*\\ L functions can only " +"operate on FILE pointers created by the VSIFOpenL function. This is " +"because VSIFOpenL returns a pointer to an internal C++ class typecast to " +"a FILE pointer, not an actual FILE pointer. This makes it impossible for " +"the compiler to warn when the VSI\\* and VSI*L functions are " +"inappropriately mixed." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:32 +msgid "Proposed Fix" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:34 +msgid "" +"A new opaque data-type VSILFILE shall be declared. All VSI\\ *L functions" +" shall be changed to use this new type instead of FILE. Additionally, any" +" GDAL code that uses the VSI*\\ L functions must be changed to use this " +"data-type as well." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:40 +msgid "RawRasterBand changes" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:42 +msgid "" +"The 2 constructors are changed to accept a void\\* fpRaw instead of a " +"FILE\\*" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:44 +msgid "" +"A new member VSILFILE\\* fpRawL is added. The existing member FILE\\* " +"fpRaw is kept. The constructors will set the adequate member according to" +" the value of the bIsVSIL parameter." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:47 +msgid "A new method VSILFILE\\* GetFPL() is added." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:48 +msgid "" +"The old FILE\\* GetFP() is adapted to have same behavior as before (can " +"return a standard FILE handle or a VSI*L handle depending on the handle " +"that was passed to the constructor)" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:52 +msgid "" +"Those changes are meant to minimize the need for casting when using " +"RawRasterBand. Backward API compatibility is preserved." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:56 +msgid "Compatibility Issues, Transition timeline" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:58 +msgid "" +"In order to allow the compiler to detect inappropriate parameters passed " +"to any of the VSI*L functions, VSILFILE will be declared with the help of" +" an empty forward declaration, i.e." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:66 +msgid "with the struct \\_VSILFILE itself left undefined." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:68 +msgid "" +"However, this would break source compatibility for any existing code " +"using the VSI*L API. Therefore, for now, VSILFILE is defined to be an " +"alias of FILE, unless the VSIL_STRICT_ENFORCE macro is defined." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:80 +msgid "" +"In a future release (GDAL 2.0 ?), the behavior will be changed to enforce" +" the new strong typing." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:83 +msgid "" +"Any future development done since the adoption of this RFC should use " +"VSILFILE when dealing with the VSIF*L API." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:87 +msgid "Questions" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:89 +msgid "Should we define VSIL_STRICT_ENFORCE by default when DEBUG is defined ?" +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:92 +msgid "" +"This would make life easier for GDAL developers to use the appropriate " +"typing, but not affect API/ABI when using release mode." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:98 +msgid "" +"The whole source tree ( port, gcore, frmts, ogr, swig/include ) will be " +"altered adequatly so that the compilation works in VSIL_STRICT_ENFORCE " +"mode. Ticket #3799 contains a patch with the implementation. The " +"compilation doesn't add any new warning. The autotest suite still works " +"after this change." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:104 +msgid "" +"The GeoRaster and JPIPKAK drivers have been modified during the " +"conversion process, but I'm not in position to compile them. Testing " +"appreciated. All other drivers that have been altered in the conversion " +"process have been compiled." +msgstr "" + +#: ../../source/development/rfc/rfc7_vsilapi.rst:109 +msgid "" +"In the conversion process, a misuse of POSIX FILE API with a large file " +"handler was discovered in the ceos2 driver, but the function happened to " +"be unusued." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:5 +msgid "RFC 80: NumFOCUS relationship and sponsorship program" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:8 +msgid "Even Rouault (with content from Chris Holmes)" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:10 +msgid "2021-Apr-15" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:11 +msgid "2021-Jun-07" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:18 +msgid "" +"The GDAL project will apply for Fiscal sponsorship to `NumFOCUS " +"<https://numfocus.org>`__, under the \"Grantor-Grantee\" model" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:24 +msgid "" +"GDAL's funding model to date has been using the overhead of new feature " +"implementation to support the maintenance activities. While this is a " +"common open source funding model, it is no longer sustainable given the " +"maturity that GDAL has reached. Undirected financial resources will give " +"the project the ability to target challenges that have proven too big or " +"too structural to otherwise attack." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:34 +msgid "" +"The GDAL project has determined that joining NumFOCUS for Fiscal " +"sponsorship will help address those challenges. NumFOCUS will receive " +"donations given by sponsors of the GDAL project." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:38 +msgid "" +"GDAL is well aligned with the requirements for a project to join " +"NumFOCUS, most of them are inherited from being an OSGeo project:" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:41 +msgid "Be scientifically oriented." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:42 +msgid "Be open." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:43 +msgid "Be kind." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:45 +msgid "" +"More precisely, GDAL will apply for Fiscal sponsorship under the " +"\"Grantor-Grantee\" model. It is described at https://numfocus.org" +"/projects-overview and put inline below for convenience:" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:60 +msgid "" +"Funds donated to GDAL will be earmarked to it (minus the commission " +"received by NumFOCUS for its operations, typically 15%, to be confirmed)." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:63 +msgid "" +"The project has already submitted a `first document " +"<https://docs.google.com/document/d/1-cZzyctrfvpqF_Cymkn0M9yKYClCA_5MGAmJ_frAi98/edit#heading=h.iq2vc7xizie0>`__" +" presenting what GDAL is and why it wants to join NumFOCUS:" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:65 +msgid "" +"We now need to formally apply through their `application form " +"<https://numfocus.typeform.com/to/VUPE35>`__ so that the application is " +"passed to the NumFOCUS board for approval." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:68 +msgid "" +"The proposed answers to that application form are at: " +"https://docs.google.com/document/d/1bc5jdpCe1axdyBHxbJnun7e0DTyDoZI_eFYgJYnOhB8/edit" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:71 +msgid "" +"A `Pre-approved Grantor/ Grantee Agreement " +"<https://docs.google.com/document/d/12KGmSD_EGWqlzh0fiaHNIiN6xPWgdTy" +"--NYf4QR-5k8/edit>`__ will also have to be signed by 3 members of the " +"GDAL PSC." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:75 +msgid "General use of funds" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:77 +msgid "" +"This topic will be refined in a further document, but we will underline " +"here the general principles." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:80 +msgid "" +"Funds obtained through NumFOCUS should be used in a way that is for the " +"general good of the project, as well as its key open source dependencies " +"(such as PROJ, libgeotiff, libtiff, shapelib, etc.)." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:84 +msgid "The tasks candidate to funding will be along (non-exhaustive list):" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:87 +msgid "ticket triaging and fixing," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:88 +msgid "code contribution review," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:89 +msgid "continuous integration maintenance and improvements," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:90 +msgid "monitoring of mailing list," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:91 +msgid "addressing reports raised by security monitoring infrastructure," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:92 +msgid "documentation improvement," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:93 +msgid "software releases," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:94 +msgid "co-operation with other funded developers (in particular onboarding)," +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:95 +msgid "reports of those activities" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:97 +msgid "" +"More generally, all tasks that are needed for a project to strive on the " +"long term, but are typically hard to get directly funding from, as not " +"being directly tied to a particular feature. It is expected that new " +"features and improvements will go on being submitted as code " +"contributions by the interested parties in capacity to develop them, or " +"through service providers they might hire for that purpose." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:104 +msgid "" +"Sponsors will not be able to direct particular developments, nor receive " +"priority support through the sponsorship program. For such purposes, they" +" may use community support or refer to service providers, as for other " +"GDAL users. However, we will offer a way to sponsors to give feedback, as" +" detailed afterwards." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:110 +msgid "GDAL Advisory Council" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:112 +msgid "" +"The GDAL Advisory Council is a newly forming group that is tasked with " +"ensuring the project is evolving to meet the needs of its largest " +"supporters. There will be periodic meetings with the advisory board, GDAL" +" PSC members wishing to participate, and persons benefiting from funding," +" providing a forum to give feedback on the latest GDAL work. Board " +"members will also be expected to share how they are using GDAL in their " +"organization (in as much detail as is possible, understanding that some " +"can only talk in general terms). Though the GDAL PSC owns the decision " +"making around how the sponsorship money is allocated, the advisory board " +"will provide key input on the maintenance priorities of the sponsors." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:114 +msgid "" +"Our hope is that these sessions can also lead to new feature development " +"in GDAL through joint funding initiatives between top sponsors, providing" +" more structure to the way GDAL features are funded today. This ideally " +"leads to more cost-sharing as organizations will be able to be more " +"strategic when they know what everyone else is interested in. These " +"efforts will be above and beyond the core maintenance sponsorship, but " +"the Advisory Council will be a key forum to enable it." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:116 +msgid "" +"The Advisory board will have an email list, with members of the GDAL PSC " +"on it, and will meet on a periodic schedule, to be determined as the " +"group forms. It will consist of one representative from each of the Gold " +"sponsors, one representative for every three Silver sponsors, and one " +"representative from Bronze sponsors." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:119 +msgid "Acknowledgment of NumFOCUS and sponsors" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:121 +msgid "" +"The GDAL website will be updated to have a page dedicated to the " +"sponsoring program, acknowledging sponsors and NumFOCUS, providing a " +"detailed FAQ on what the sponsorship program consists in and a " +"\"sponsoring prospectus\" that can be used by candidate sponsors. A work-" +"in-progress version of this update is available at " +"https://github.com/OSGeo/gdal/pull/3681" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:128 +msgid "Impacts on OSGeo relationship" +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:130 +msgid "" +"GDAL and will continue to remain a OSGeo project for all other concerns " +"than NumFOCUS-related sponsorship." +msgstr "" + +#: ../../source/development/rfc/rfc80_numfocus_relationship.rst:136 +msgid "" +"+1 from PSC members EvenR, KurtS, FrankW, MateuszL, DanielM, HowardB and " +"NormanB" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:5 +msgid "RFC 81: Support for coordinate epochs in geospatial formats" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:10 +msgid "2021-May-10" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:11 +msgid "Last Updated:" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:11 +msgid "2021-Jun-18" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:13 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:13 +#: ../../source/development/rfc/rfc87_signed_int8.rst:12 +#: ../../source/development/rfc/rfc88_googletest.rst:12 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:12 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:12 +#: ../../source/development/rfc/rfc91_dataset_close.rst:12 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:12 +#: ../../source/development/rfc/rfc93_update_feature.rst:12 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:12 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:12 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:12 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:12 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:11 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:12 +msgid "Target:" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:13 +msgid "GDAL 3.4" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:19 +msgid "" +"This RFC describes support for coordinate epochs in a few key geospatial " +"formats and in GDAL/OGR API and utilities" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:25 +msgid "" +"A number of coordinate reference systems (CRS) are called \"dynamic " +"CRS\", that is the coordinates of a point on the surface of the Earth in " +"those CRS may change with time. To be unambiguous the coordinates must " +"always be qualified with the epoch at which they are valid. The " +"coordinate epoch is not necessarily the epoch at which the observation " +"was collected." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:31 +msgid "" +"Examples of dynamic CRS are ``WGS 84 (G1762)``, ``ITRF2014``, " +"``ATRF2014``." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:33 +msgid "" +"The generic EPSG:4326 WGS 84 CRS is also considered dynamic, although it " +"is not recommended to use it due to being based on a datum ensemble whose" +" positional accuracy is 2 meters, but prefer one of its realizations, " +"such as WGS 84 (G1762)" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:37 +msgid "" +"At time of writing, no formats handled by GDAL/OGR have a standardized " +"way of encoding a coordinate epoch. We consequently have made choices how" +" to encode it, admittedly not always elegant, with the aim of being as " +"much as possible backward compatible with existing readers. Those " +"encodings might change if corresponding official specifications evolve to" +" take this concept into account. But, as this is a bit of a chicken-and-" +"egg problem (\"why should we care about storing coordinate epoch if no " +"software can make use of it ?\"), let's start with this initial solution." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:46 +msgid "" +"PROJ can handle a number of time-dependent transformations between static" +" CRS and dynamic CRS, e.g a GDA2020 (static CRS/datum for Australia) to " +"ATRF2014 (dynamic CRS/datum for Australia), taking into account plate " +"motion. Having support to store coordinate epoch will make it easier to " +"have more accurate coordinate transformation." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:55 +msgid "" +"See :ref:`coordinate_epoch` for impacts on the API, encoding of CRS in a " +"number of formats, and impacts on existing utilities." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:62 +msgid "At the API level, only additions." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:64 +msgid "" +"Regarding creation of new datasets, no backward incompatibility at all if" +" datasets are created without a coordinate epoch associated to their CRS," +" as its encoding is only added when needed." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:68 +msgid "" +"And when it is used, it is done in a way that shouldn't affect existing " +"reader. The only exception would be the FlatGeobuf format if writing a " +"non-EPSG coded CRS, and with a coordinate epoch (a backport to the 3.3 " +"branch will be done to avoid an error in that case)." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:76 +msgid "" +"New methods are documented, and the page mentioned in the Details " +"paragraph will be part of the user documentation." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:82 +msgid "" +"New methods are tested. Formats extended with coordinate epoch support " +"have also received new tests." +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:88 +msgid "https://github.com/OSGeo/gdal/pull/4011" +msgstr "" + +#: ../../source/development/rfc/rfc81_coordinate_epoch.rst:93 +msgid "+1 from JukkaR and EvenR, -0 from HowardB and +0 from KurtS" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:5 +msgid "RFC 83: guidelines for the use of GDAL project sponsorship" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:8 +msgid "Even Rouault (with content from RFC 9)" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:10 +msgid "2021-May-19" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:17 +msgid "" +"Per :ref:`rfc-80`, the GDAL project benefits from a multi-year budget " +"coming from sponsorship. This document formalizes guidelines for how that" +" budget will be spent by the project and supersedes :ref:`rfc-9`" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:21 +msgid "There are two different type of tasks that will be funded:" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:23 +msgid "" +"Day-to-day maintenance tasks. They will be filled by several co-" +"maintainers." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:24 +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:163 +msgid "Tasks to achieve a specific development" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:27 +msgid "Day-to-day maintenance tasks" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:30 +msgid "Scope" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:32 +msgid "Bug tracker maintenance:" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:34 +msgid "Validating completeness of bug reports to ensure reproducibility" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:35 +msgid "Closing reports that don't respect the guidelines, or are invalid." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:36 +msgid "Tagging the issue with appropriate labels and milestones." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:37 +msgid "When a fix is relevant, addressing the issue with a pull request." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:38 +msgid "" +"Adding / enhancing tests in the regression test suite should be done as " +"much as practical" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:40 +msgid "" +"Tasks that are expected, or are found, to take more than a given time " +"should be confirmed with the supervisor." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:43 +msgid "" +"Continuous Integration maintenance and improvements: the project has " +"several Continuous Integration configurations. Some of them break " +"regularly due to external causes (network resources no longer available, " +"change in dependencies, etc.). The co-maintainer will take the necessary " +"actions to keep them in working state." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:48 +msgid "" +"Review of code and documentation contributions. Such contributions are " +"made currently through GitHub pull requests. The co-maintainer will " +"review the contribution and guide the proponent through the steps to make" +" it accepted: identifying issues reported by Continuous Integration, " +"asking for new tests to be developed whenever possible, etc. When the " +"contributor is not in capacity to polish his/her contribution, the co-" +"maintainer may do it themself." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:54 +msgid "" +"Ensuring that fixes that are appropriate for backporting in stable " +"branche(s) are backported." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:56 +msgid "" +"Monitoring of project communication channels (mailing list, IRC, Slack " +"channels, etc.). The co-maintainer will in particular identify issues " +"that are reported through those means and ensures that they are captured " +"by a corresponding ticket. The co-maintainer may also occasionally answer" +" questions on usage of the library and tools, but in-depth support of " +"users is not in the scope of the covered tasks (users may use service " +"providers for that purpose)." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:63 +msgid "" +"Proactive tracking of new versions of libraries that GDAL depends on, and" +" address needed changes for compilation and proper runtime behavior" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:65 +msgid "" +"Monitor and address reports of static and dynamic analyzers. Currently: " +"OSS-Fuzz, cppcheck, Clang Static Analyzer, Coverity Scan, gcc&clang " +"memory/undefined behavior/etc. analyzers." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:68 +msgid "Documentation improvements" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:69 +msgid "" +"Activities related to software releases: writing the release notes, " +"issuing release candidates, addressing feedback, finalizing releases" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:71 +msgid "" +"For experienced contributors, help less experienced contributors get on " +"board and along with GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:74 +msgid "" +"Projects that are concerned by such activities: GDAL itself of course, " +"but also other, generally smaller, free and open source projects that " +"have been strongly tied to it as being required or very common " +"dependencies for GDAL, and don't benefit from similar maintenance funds " +"(on the contrary, projects that use GDAL don't qualify for being funded " +"by the GDAL sponsorship funds). The current list includes PROJ, libtiff, " +"libgeotiff, shapelib, GEOS, OpenJPEG. If during the investigation of an " +"issue, a co-maintainer finds an issue in another open source component " +"and can come up with a patch, they are also welcome to do it." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:83 +#, python-format +msgid "" +"A typical share of time could be 75% for GDAL and 25% for the other " +"projects." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:85 +msgid "" +"GDAL is a vast and complex project. It is not expected that each co-" +"maintainer has expertise in all its aspects. Applicants will mention " +"their domains of interest, which can evolve over time, and coordinate " +"with other stakeholders in how tasks are assigned." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:91 +#: ../../source/development/rfc/rfc9_maintainer.rst:42 +msgid "Direction" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:96 +msgid "" +"The co-maintainer is generally subject to the project PSC. However, for " +"day to day decisions one PSC member might be designated as the supervisor" +" for the co-maintainer (PSC members that are funded through this program " +"will use existing decision making processes to prioritize their work). " +"This supervisor will coordinate with the co-maintainer via email or IRC " +"discussions." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:106 +msgid "" +"The supervisor will try to keep the following in mind when prioritizing " +"tasks:" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:108 +msgid "" +"Tickets that are regressions compared to a previous release are of higher" +" priority than other tasks" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:110 +msgid "" +"Bug reports should be given higher priority than other tasks. (bug " +"reports from sponsors will *not* qualify as such for higher priority " +"treatment)" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:112 +msgid "" +"Areas of focus identified by the PSC should be given higher priority than" +" other tasks." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:114 +#: ../../source/development/rfc/rfc9_maintainer.rst:56 +msgid "Bugs or needs that affect many users should have higher priority." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:115 +msgid "" +"The co-maintainer should be used to take care of work that no one else is" +" willing and able to do (i.e. fill the holes, rather than displacing " +"volunteers)" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:117 +msgid "" +"Try to avoid tying up the co-maintainer on one big task for many weeks " +"unless directed by the PSC." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:119 +msgid "" +"The co-maintainer should not be directed to do work for which someone " +"else is getting paid." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:122 +msgid "" +"Substantial new development projects will only be taken on by the co-" +"maintainer with the direction of a PSC motion (or possibly an RFC " +"designating the co-maintainer to work on a change)." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:126 +msgid "" +"Note that the co-maintainer and the co-maintainer supervisor are subject " +"to the normal RFC process for any substantial change to GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:130 +#: ../../source/development/rfc/rfc9_maintainer.rst:73 +msgid "Reporting" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:132 +msgid "" +"The co-maintainer will produce a monthly report (typically in a shared " +"spreadsheet) with the tasks they have tackled, typically pointing at " +"tickets and pull requests, and the amount of hours spent during the " +"reported period." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:137 +msgid "Who can apply ?" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:139 +msgid "" +"Applicants should be individuals, either self-employed or employed by a " +"company agreeing to allocate some of their time to such activities, that " +"have been a proven public track record of meeting the following " +"qualities:" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:143 +msgid "" +"Knowledge of the programming languages required for the task: C/C++ for " +"GDAL library and some knowledge of Python for the test suite, appropriate" +" language for any of the SWIG bindings." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:146 +msgid "" +"Knowledge of the geospatial field, ideally with one or several open " +"source geospatial projects, and/or experience with file formats and low-" +"level considerations." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:149 +msgid "" +"Ability to interact with members of an open source community in " +"accordance to the Code of Conduct." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:151 +msgid "Good knowledge of written English is necessary." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:153 +msgid "" +"We cannot put formal criteria on that, but applicants should ideally aim " +"for a multi-year involvement with the project, so that their onboarding " +"time is amortized." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:156 +msgid "" +"Each co-maintainer will be allocated a maximum number of hours per " +"quarter (they will indicate their planned availability and the PSC will " +"decide on the effective allocation), and will invoice on the time " +"effectively spent within that allocation." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:160 +msgid "" +"Applicants will provide their hourly rate, in US dollars, to the PSC " +"(privately)" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:169 +msgid "" +"The GDAL PSC will call for proposals (frequency to be adjusted, but could" +" be per quarter year) of proponents that want to achieve a specific " +"development. The PSC will indicate the total budget available and other " +"conditions. The PSC may suggest a few ideas that it would want to receive" +" proposals for." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:174 +msgid "" +"Generally speaking, priority will be given to proposals that address " +"housekeeping tasks, non-directly user oriented aspects of the " +"project(s), rather than user-oriented features (new drivers, new " +"utilities, etc. are more prone to be funded by interested parties), but " +"the later ones can be proposed if they are deemed of sufficiently large " +"interest." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:180 +msgid "" +"A non-exhaustive list of topics that are meant to be addressed per this " +"vehicle are:" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:182 +msgid "Improving/rewriting a part of the code base" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:183 +msgid "Changes that affect a large part of the code base" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:184 +msgid "Speed optimizations" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:185 +msgid "Adding / improving support for some platforms" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:186 +msgid "Improvements in test suite / Continuous Integration" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:187 +msgid "Improvements in build system" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:188 +msgid "Improvements in documentation" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:189 +msgid "" +"Packaging efforts (provided that they use fully reproducible open source " +"build recipes)" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:191 +msgid "" +"Applicants will provide the amount to be funded. Proposals may be put " +"together by one or several individuals (in the later case, to be " +"determined if we can let the team have a \"invoicing point of contact\" " +"and let them arrange how to dispatch it amongst members, or if each team " +"member should ask for its part of funding). An applicant may submit " +"proposals for several subjects." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:198 +msgid "" +"Applicants will submit the technical details of their proposal as an " +"issue in the bug tracker where it can be collaboratively discussed with " +"interested members of the community (or as an RFC for changes that would " +"usually qualify for a RFC)." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:205 +msgid "Criteria for applicants are the same as in the above section." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:208 +msgid "Decision process" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:210 +msgid "" +"The allocation of funds, through the selection of co-maintainers and " +"grantees of specific developments, will be decided by the PSC." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:213 +msgid "" +"The input provided by the Advisory Board regarding maintenance priorities" +" will be taken into account by the PSC, on an equal footing as other " +"input provided by the community, and PSC's own analysis of priorities." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:218 +msgid "" +"PSC members that apply for funds, or that have a conflict of interest " +"(e.g. working in the same company as an applicant), or any other " +"situation of conflict or interest, may take part in discussions, but " +"should abstain from voting on decisions related to fund allocation." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:224 +msgid "Note" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:226 +msgid "" +"As this is a new way of operating for the project, it is expected that " +"this RFC will evolve over time with the gained experience in the " +"management of the sponsorship program." +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:233 +msgid "https://lists.osgeo.org/pipermail/gdal-dev/2021-June/thread.html#54249" +msgstr "" + +#: ../../source/development/rfc/rfc83_use_of_project_sponsorship.rst:235 +msgid "" +"+1 from PSC members MateuszL, HowardB, FrankW, KurtS, SeanG, JukkaR, " +"DanielM and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:5 +msgid "RFC 84: Migrating build systems to CMake" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:8 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:8 +msgid "Authors:" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:8 +msgid "Even Rouault, Nyall Dawson, Howard Butler" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:10 +msgid "" +"even.rouault at spatialys.com, nyall.dawson at gmail.com, howard at " +"hobu.co" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:13 +msgid "2021-09-22" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:14 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:11 +msgid "Updated:" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:14 +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:10 +msgid "2022-01-17" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:15 +msgid "Adopted (implementation in progress)" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:21 +msgid "The document proposes :" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:23 +msgid "to develop a CMake build system, officially integrated in the source tree." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:25 +msgid "" +"and remove the current GNU makefiles and nmake build systems, when the " +"CMake build system has matured enough and reached feature parity. We " +"don't want to end up with a https://xkcd.com/927/ situation." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:32 +msgid "" +"A dual build system means editing twice, which increases the amount of " +"work and the chance for bugs." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:35 +msgid "" +"For Unix, we have a rather custom and non-idiomatic build system using " +"autoconf, but not automake." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:38 +msgid "" +"The makefiles in both build systems are hand-written. One of their main " +"deficiency from the point of view of a GDAL developer is the lack of " +"tracking of header dependencies. It is this very easy to produce a " +"corrupted GDAL build, if forgetting to manually clean a previous build. " +"This is a serious obstacle to embed regular or occasional GDAL developers" +" that hit that issue, generally not found in other projects." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:45 +msgid "Neither Unix or Windows builds support out-of-tree builds." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:47 +msgid "" +"Windows builds have poor support for parallel build: it is limited to the" +" files in one directory." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:50 +msgid "" +"There is generally no consistency in the naming of build options in our " +"Unix and Windows build systems, which makes life harder for users having " +"to build GDAL on multiple platforms." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:54 +msgid "" +"The two existing build systems do not have the same features. For " +"example, configure now offers the option to selectively disable drivers, " +"including ones that do not depend on external dependencies, using a opt-" +"out or opt-in strategies, whereas the NMake build does not." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:59 +msgid "" +"CMake has become the defacto solution with the widest adoption for C/C++ " +"software that want to address multiple platforms. Most of GDAL " +"dependencies have at least a CMake build system, and some have now CMake " +"as the only option (GEOS 3.10 will only have a CMake build system, and " +"the same is proposed for PROJ 9 in " +"https://github.com/OSGeo/PROJ/pull/2880), making soon CMake a de-facto " +"requirement for a GDAL build. Looking a bit in the FOSS4G field for C/C++" +" project, CMake is ubiquitous, so there is a widespread knowledge of it " +"among existing or potential contributors to GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:69 +msgid "" +"A CMake build system has been asked repeatedly by many developers or " +"users of GDAL over the past years. We are aware of a least two public " +"out-of-tree CMake efforts: https://github.com/miurahr/cmake4gdal and " +"https://github.com/nextgis-borsch/lib_gdal" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:73 +msgid "" +"CMake has the widest industry tooling support. A number of Modern C++ " +"IDEs offer good support for CMake: Visual Studio, qtcreator, etc. This " +"should help reduce the barrier for contribution." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:77 +msgid "" +"CMake development is active with regular feature releases, whereas the " +"technologies behind our existing build systems are more in a maintenance " +"mode." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:81 +msgid "Why not CMake?" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:83 +msgid "" +"Other modern cross-platform build systems exist, including Meson and " +"Bazel, which have many advantages over CMake. However, they are currently" +" not widely familiar or used by active GDAL contributors. CMake represent" +" the current \"least worse\" solution for multiple platform builds when " +"comparing its capabilities and its maturity." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:89 +msgid "" +"CMake does not address simultaneously building shared and static " +"libraries. This can however be worked around by doing 2 builds and " +"merging build artifacts." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:93 +msgid "Phases / Schedule" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:95 +msgid "The following is the planned schedule:" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:97 +msgid "" +"Add CMake as a new build system, and formally deprecate GNUmakefile and " +"NMake base file systems. Users and packagers are encouraged to switch to " +"CMake and actively report (and help fixing) issues the find in the " +"process. GDAL 3.5.x point releases will be used to address reported " +"issues." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:103 +msgid "==> Target: GDAL 3.5 / May 2022" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:105 +msgid "" +"Completely remove GNUmakefile and NMake base file systems, and make CMake" +" the only build system in GDAL source tree." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:108 +msgid "==> Target: GDAL 3.6 / November 2022" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:113 +msgid "" +"The above mentioned cmake4gdal repository seems to us the best starting " +"point. It respects the current tree organization of the GDAL repository " +"and targets a not too old CMake version (3.10)." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:117 +msgid "" +"We will start by running the scripts that deploy the CMakeLists.txt and " +"other cmake support files, and commit them into the GDAL repository." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:120 +msgid "" +"A checklist of all features of our current build systems that will need " +"to be ported and checked has been initiated in: " +"https://docs.google.com/spreadsheets/d/1SsUXiZxKim6jhLjlJFCRs1zwMvNpbJbBMB6yl0ms01c/edit" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:127 +msgid "" +"The Python, Java and CSharp bindings will be available as options of the " +"CMake build options." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:130 +msgid "" +"The Perl bindings will not be available, as being planned for removal in " +"GDAL 3.5" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:135 +msgid "" +"The addition of the CMake build system, being mostly an addition during " +"the transient phase where it will be available alongside the existing " +"build systems, should moderately impact existent files. However, it is " +"likely that there will be some improvements that affect C++ files (for " +"example, to use consistently ``#include <project/header.h>`` style of " +"inclusion instead of the``#include <header.h>`` with " +"``-I${include_prefix}/project`` pattern sometimes used) and the " +"GNUmakefile/makefile.vc files." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:142 +msgid "" +"We may use of PRIVATE linking of vendored and intermediate libraries to " +"hide non-public symbols. This might change a bit from existing builds " +"that can leak them." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:146 +msgid "Minimum CMake version" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:148 +msgid "" +"cmake4gdal uses CMake 3.10 as the minimum version. This is a reasonable " +"choice, as it would be compatible with the cmake version provided by " +"Ubuntu 18.04 for example, the current old-stable Ubuntu LTS." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:152 +msgid "" +"Given the mentioned schedule, CMake will become a requirement in May " +"2023, at a time where the new old-stable LTS will be Ubuntu 20.04. So we " +"can't exclude we will bump this minimum version if it is found to be more" +" practical. For example, CMake 3.12 adds an easier way for handling " +"\"object libraries\", that can help solving issues regarding static " +"builds and vendored dependencies (cf " +"https://github.com/libgeos/geos/issues/463)" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:160 +msgid "Supported platforms" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:162 +msgid "" +"Our continuous integration \"only\" tests Linux (Intel/AMD, ARM64 and " +"s390x architectures), Android (build only), MacOSX and Windows. We will " +"welcome involvement at some point from users/developers of other " +"environments to test and help address any outstanding issues." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:167 +msgid "General requirements" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:169 +msgid "" +"The following lists a few requirements to consider the new build system " +"be ready, and the existing ones can be removed:" +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:172 +msgid "" +"The build system works on most environments where the build systems are " +"known to work. For CI-tested environments, this will involve porting to " +"them and checking that the builds are functional. For other build " +"systems, we will depend on manual testing from users." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:177 +msgid "objdir / out-of-source builds are supported." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:179 +msgid "cross builds are supported." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:181 +msgid "" +"Explicit testing of OSes through ``if(THIS_OS)`` should be limited, and " +"replaced by testing of feature wherever doable." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:184 +msgid "" +"There has been a formal release (presumably 3.6) with existing build " +"systems and cmake where cmake meets the above requirements, as verified " +"by packager feedback." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:190 +msgid "" +"Even Rouault and Nyall Dawson will use project sponsorship funding to " +"complete that work. An estimate of 2 man-months of effort has been made " +"recently to provide an initial build out of CMake support for GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc84_cmake.rst:197 +msgid "+1 from PSC members: HowardB, MateuszL, KurtS, DanielM and JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:5 +msgid "RFC 85: Policy regarding substantial code additions" +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:8 +msgid "Howard Butler, Even Rouault" +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:17 +msgid "" +"This document describes the policies that the GDAL project will apply to " +"assess substantial code additions, typically new drivers, in particular " +"coming from new contributors to the project." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:24 +msgid "" +"The GDAL project has historically been quite open to new code additions, " +"including drivers that rely on proprietary licensed and/or closed-source " +"SDKs (called \"binary SDK\" in the rest of this document). This approach " +"is part of its strengths, but also comes at a price, with the software " +"becoming larger and larger, and with contributions sometimes being " +"abandoned by their authors without new maintainers." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:31 +msgid "" +"Being a free & open-source project, the GDAL project will apply stronger " +"scrutiny to code that requires a binary SDK and encourage contributors to" +" submit code additions that do not depend on such binary SDK, or license " +"SDKs under free & open-source license terms." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:37 +msgid "Policy" +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:39 +msgid "" +"Drivers require a designated responsible contact, tracked in " +"https://github.com/OSGeo/gdal/wiki/Maintainers-per-sub-system" +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:42 +msgid "" +"Contributions should follow other RFCs describing development rules, and " +"come with test scripts and sufficient documentation, covering usage and " +"build instructions." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:45 +msgid "" +"If the driver require a binary SDK not downloadable without cost, or that" +" requires a complicated registration process, the GDAL team is unlikely " +"to support driver inclusion." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:48 +msgid "" +"GDAL supports multiple operating systems, and new drivers should support " +"as many as is practical. At a minimum, drivers should work with the " +"latest and OS-vendor supported releases of operating systems the driver " +"is documented to work with." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:52 +msgid "" +"If the binary SDK is no longer supported, or modernized to work with " +"current compilers and GDAL, the driver can be dropped. This rule also " +"applies to open-source dependencies that are no longer maintained or are " +"superseded by other alternatives." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:56 +msgid "" +"If the driver has unaddressed bugs, is breaking continuous integration " +"(CI), has caused CI bits to be disabled, or has not caught up to API " +"modifications requiring updates (extremely rare), the driver will be " +"dropped from build scripts, and thus will not be built without " +"significant user intervention." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:61 +msgid "" +"If critical/blocking issues reported in a driver are not addressed within" +" a 2 month time-frame, it can be dropped from the tree entirely by a " +"designated GDAL maintainer for all releases going forward." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:65 +msgid "" +"Contributors of significant code additions are expected to participate in" +" the day-to-day life of the GDAL project, and need to monitor closely the" +" communication channels of the project: issue tracker, mailing lists, " +"etc." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:69 +msgid "" +"Maintainers are expected to support their contributions by triaging bug " +"reports, reviewing related pull requests and RFCs, making functional " +"enhancements, testing releases, and improving documentation, tests, and " +"infrastructure." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:73 +msgid "" +"In addition, maintainers are expected to respond in a timely manner to " +"wider project changes (CI, build scripts, upgrade of dependencies, build " +"tools, documentation, etc.) as it pertains to their contributions." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:77 +msgid "" +"New contributions may require a significant review effort from a GDAL " +"committer (ie someone with direct modification rights to the source " +"repository). While the project has funded maintainers, it must be " +"understood that they might not be immediately available to do reviews of " +"significant code additions. Contributors may contract GDAL committers to " +"have such task done within a more predictable timeline." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:83 +msgid "" +"The above rules are not exhaustive. The PSC reserves the right to reject " +"a proposed code addition depending on its particular nature and other " +"contextual elements." +msgstr "" + +#: ../../source/development/rfc/rfc85_policy_code_additions.rst:89 +msgid "" +"+1 from PSC members MateuszL, KurtS, TamasS, SeanG, HowardB, JukkaR and " +"EvenR." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:5 +msgid "RFC 86: Column-oriented read API for vector layers" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:10 +msgid "2022-May-24" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:11 +msgid "2022-June-14" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:13 +msgid "GDAL 3.6" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:19 +msgid "" +"This RFC describes the addition of new methods to the " +":cpp:class:`OGRLayer` class to retrieve batches of features with a " +"column-oriented memory layout, that suits formats that have that " +"organization or downstream consumers that expect data to be presented in " +"such a way, in particular the `Apache Arrow " +"<https://arrow.apache.org/docs/>`_, `Pandas " +"<https://pandas.pydata.org/>`_ / `GeoPandas <https://geopandas.org/>`_ " +"ecosystem, R spatial packages, and many modern (data analytics focused) " +"databases / engines which are column oriented (eg Snowflake, Google " +"BigQuery, ..)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:30 +msgid "" +"Currently, to retrieve feature information, users must iterate over each " +"feature of a layer with GetNextFeature(), which returns a C++ object, on " +"which query attributes and geometries are retrieved with various \"get\" " +"methods. When invoked from binding languages, a overhead typically occurs" +" each time the other language calls native code. So to retrieve all " +"information on a layer made of N_features and N_fields, you need of the " +"order of N_features * N_fields calls. That overhead is significant. See " +"below :ref:`rfc-86-benchmarks`." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:38 +msgid "" +"Another inconvenience of the C API is that processings that involve many " +"rows of a same field (e.g computing statistics on a field) may require " +"data to be contiguously placed in RAM, for the most efficient processing " +"(use of vectorized CPU instruction). The current OGR API does not allow " +"that directly, and require the users to shuffle itself data into " +"appropriate data structures. Similarly the above mentioned frameworks " +"(Arrow, Pandas/GeoPandas) require such memory layouts, and currently " +"require reorganizing data when reading from OGR. The `pyogrio " +"<https://github.com/geopandas/pyogrio>`_ project is for example an " +"attempt at addressing that need." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:48 +msgid "" +"Furthermore, the :ref:`vector.arrow` and :ref:`vector.parquet` drivers, " +"whose file organization is columnar, and batch oriented, have been added " +"in GDAL 3.5.0. Consequently a columnar-oriented API will enable the best " +"performance for those formats." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:56 +msgid "" +"The new proposed API implements the `Apache Arrow C Stream interface " +"<https://arrow.apache.org/docs/format/CStreamInterface.html>`_. Reading " +"that document, as well of the first paragraphs of the `Apache Arrow C " +"data interface " +"<https://arrow.apache.org/docs/format/CDataInterface.html>`_. (details on" +" the various data types can be skipped) is strongly encouraged for a " +"better understanding of the rest of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:63 +msgid "" +"The Arrow C Stream interface is currently marked as experimental, but it " +"has not evolved since its introduction in Nov 2020 and is already used in" +" ABI sensitive places like the interface between the Arrow R bindings and" +" DuckDB." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:67 +msgid "" +"This interface consists of a set of C structures, ArrowArrayStream, that " +"provides two main callbacks to get:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:70 +msgid "" +"a ArrowSchema with the get_schema() callback. A ArrowSchema describes a " +"set of field descriptions (name, type, metadata). All OGR data types have" +" a corresponding Arrow data type." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:74 +msgid "" +"a sequence of ArrowArray with the get_next() callback. A ArrowArray " +"captures a set of values for a specific column/field in a subset of " +"features. This is the equivalent of a `Series " +"<https://arrow.apache.org/docs/python/pandas.html#series>`_ in a Pandas " +"DataFrame. This is a potentially hiearchical structure that can aggregate" +" sub arrays, and in OGR usage, the main array will be a StructArray which" +" is the collection of OGR attribute and geometry fields. The layout of " +"buffers and children arrays per data type is detailed in the `Arrow " +"Columnar Format <https://arrow.apache.org/docs/format/Columnar.html>`_." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:84 +msgid "" +"If a layer consists of 4 features with 2 fields (one of integer type, one" +" of floating-point type), the representation as a ArrowArray is " +"*conceptually* the following one:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:93 +msgid "" +"The content of a whole layer can be seen as a sequence of record batches," +" each record batches being an ArrowArray of a subset of features. Instead" +" of iterating over individual features, one iterates over a batch of " +"several features at once." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:98 +msgid "" +"The ArrowArrayStream, ArrowSchema, ArrowArray structures are defined in a" +" ogr_recordbatch.h public header file, directly derived from " +"https://github.com/apache/arrow/blob/main/cpp/src/arrow/c/abi.h to get " +"API/ABI compatibility with Apache Arrow C++. This header file must be " +"explicitly included when the related array batch API is used." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:103 +msgid "The following virtual method is added to the OGRLayer class:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:110 +msgid "This method is also available in the C API as OGR_L_GetArrowStream()." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:112 +msgid "" +"out_stream is a pointer to a ArrowArrayStream structure, that can be in a" +" uninitialized state (the method will ignore any initial content)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:115 +msgid "" +"On successful return, and when the stream interfaces is no longer needed," +" it must must be freed with out_stream->release(out_stream)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:118 +msgid "" +"There are extra precautions to take into account in a OGR context. Unless" +" otherwise specified by a particular driver implementation, the " +"ArrowArrayStream structure, and the ArrowSchema or ArrowArray objects its" +" callbacks have returned, should no longer be used (except for " +"potentially being released) after the OGRLayer from which it was " +"initialized has been destroyed (typically at dataset closing). " +"Furthermore, unless otherwise specified by a particular driver " +"implementation, only one ArrowArrayStream can be active at a time on a " +"given layer (that is the last active one must be explicitly released " +"before a next one is asked). Changing filter state, ignored columns, " +"modifying the schema or using ResetReading()/GetNextFeature() while using" +" a ArrowArrayStream is strongly discouraged and may lead to unexpected " +"results. As a rule of thumb, no OGRLayer methods that affect the state of" +" a layer should be called on a layer, while an ArrowArrayStream on it is " +"active." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:132 +msgid "A potential usage can be:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:164 +msgid "" +"The papszOptions that may be provided is a NULL terminated list of " +"key=value strings, that may be driver specific." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:167 +msgid "OGRLayer has a base implementation of GetArrowStream() that is such:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:169 +msgid "" +"The get_schema() callback returns a schema whose top-level object " +"returned is of type Struct, and whose children consist in the FID column," +" all OGR attribute fields and geometry fields to Arrow fields. The FID " +"column may be omitted by providing the INCLUDE_FID=NO option." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:174 +msgid "" +"When get_schema() returns 0, and the schema is no longer needed, it must " +"be released with the following procedure, to take into account that it " +"might have been released by other code, as documented in the Arrow C data" +" interface:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:185 +msgid "The get_next() callback retrieve the next record batch over the layer." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:187 +msgid "" +"out_array is a pointer to a ArrowArray structure, that can be in a " +"uninitialized state (the method will ignore any initial content)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:190 +msgid "" +"The default implementation uses GetNextFeature() internally to retrieve " +"batches of up to 65,536 features (configurable with the " +"MAX_FEATURES_IN_BATCH=num option). The starting address of buffers " +"allocated by the default implementation is aligned on 64-byte boundaries." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:195 +msgid "" +"The default implementation outputs geometries as WKB in a binary field, " +"whose corresponding entry in the schema is marked with the metadata item " +"``ARROW:extension:name`` set to ``ogc.wkb``. Specialized implementations " +"may output by default other formats (particularly the Arrow driver that " +"can return geometries encoded according to the GeoArrow specification " +"(using a list of coordinates). The GEOMETRY_ENCODING=WKB option can be " +"passed to force the use of WKB (through the default implementation)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:203 +msgid "" +"The method may take into account ignored fields set with " +"SetIgnoredFields() (the default implementation does), and should take " +"into account filters set with SetSpatialFilter() and " +"SetAttributeFilter(). Note however that specialized implementations may " +"fallback to the default (slower) implementation when filters are set." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:208 +msgid "" +"Mixing calls to GetNextFeature() and get_next() is not recommended, as " +"the behavior will be unspecified (but it should not crash)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:211 +msgid "" +"When get_next() returns 0, and the array is no longer needed, it must be " +"released with the following procedure, to take into account that it might" +" have been released by other code, as documented in the Arrow C data " +"interface:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:221 +msgid "" +"Drivers that have a specialized implementation should advertise the new " +"OLCFastGetArrowStream layer capability." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:225 +msgid "Other remarks" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:227 +msgid "" +"Using directly (as a producer or a consumer) a ArrowArray is admittedly " +"not trivial, and requires good intimacy with the Arrow C data interface " +"and columnar array specifications, to know, in which buffer of an array, " +"data is to be read, which data type void* buffers should be cast to, how " +"to use buffers that contain null/not_null information, how to use offset " +"buffers for data types of type List, etc." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:233 +msgid "" +"For the consuming side, the new API will be best used with the (Py)Arrow," +" Pandas, GeoPandas, Numpy libraries which offer easier and safer access " +"to record batches. The study of the gdal_array._RecordBatchAsNumpy() " +"method added to the SWIG Python bindings can give a good hint of how to " +"use an ArrowArray object, in conjunction with the associated ArrowSchema." +" DuckDB is also another example of using the ArrowArray interface: " +"https://github.com/duckdb/duckdb/blob/master/src/common/types/data_chunk.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:240 +msgid "" +"It is not expected that most drivers will have a dedicated implementation" +" of GetArrowStream() or its callbacks. Implementing it requires a non-" +"trivial effort, and significant gains are to be expected only for those " +"for which I/O is very fast, and thus in-memory shuffling of data takes a " +"substantial time relatively to the total time (I/O + shuffling)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:246 +msgid "" +"Potential future work, not in the scope of this RFC, could be the " +"addition of a column-oriented method to write new features, a " +"WriteRecordBatch() method." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:252 +msgid "" +"Arrow and Parquet: get_schema() and get_next() have a specialized " +"implementation in those drivers that directly map to methods of the " +"arrow-cpp library that bridges at near zero cost (no data copying) the " +"internal C++ implementation with the C data interface." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:257 +msgid "" +"FlatGeoBuf and GeoPackage: a specialized implementation of get_next() has" +" been done, which saves going through the OGRFeature abstraction. See " +"below benchmarks for measurement of the efficiency." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:264 +msgid "" +"Per this RFC, only the Python bindings are extended to map the new " +"functionality." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:266 +msgid "The ogr.Layer class receives the following new methods:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:268 +msgid "" +"GetArrowStreamAsPyArrow(): wrapper over OGRLayer::GetArrowStream() that " +"has a ``schema`` property with the C ArrowSchema into a corresponding " +"PyArrow Schema object and which implements a Python iterator exposing the" +" C ArrowArray returned by the get_next() callback as a corresponding " +"PyArrow Array object. This is a almost zero-cost call." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:274 +msgid "" +"GetArrowStreamAsNumPy(): wrapper over OGRLayer::GetArrowStream() which " +"implements a Python iterator exposing the C ArrowArray returned by the " +"get_next() callback as a Python dictionary whose keys are field names and" +" values a Numpy array representing the values of the ArrowArray. The " +"mapping of types is done for all Arrow data types returned by the base " +"implementation of OGRLayer::GetArrowStream(), but may not cover " +"\"exotic\" data types that can be returned by specialized implementations" +" such as the one in the Arrow/Parquet driver. For numeric data types, the" +" Numpy array is a zero-copy adaptation of the C buffer. For other data " +"types, a copy is involved, with potentially arrays of Python objects." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:289 +msgid "Benchmarks" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:291 +msgid "" +"The test programs referenced in :ref:`rfc-86-annexes` have been run on a " +"dataset with 3.3 millions features, with 13 fields each (2 fields of type" +" Integer, 8 of type String, 3 of type DateTime) and polygon geometries." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:295 +msgid "" +":ref:`rfc-86-bench-ogr-py`, :ref:`rfc-86-bench-fiona` and :ref:`rfc-86" +"-bench-ogr-cpp` have similar functionality: iterating over features with " +"GetNextFeature()." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:298 +msgid "" +":ref:`rfc-86-bench-pyogrio-raw` does a little more by building Arrow " +"arrays." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:300 +msgid "" +":ref:`rfc-86-bench-pyogrio`, :ref:`rfc-86-bench-geopandas` and " +":ref:`rfc-86-bench-ogr-to-geopandas` have all similar functionality: " +"building a GeoPandas GeoDataFrame" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:303 +msgid "" +":ref:`rfc-86-bench-ogr-batch-cpp` can be used to measure the raw " +"performance of the proposed GetArrowStream() API." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:306 +msgid "nz-building-outlines.fgb (FlatGeoBuf, 1.8 GB)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:309 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:331 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:350 +msgid "Bench program" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:309 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:331 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:350 +msgid "Timing (s)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:311 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:333 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:352 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:427 +msgid "bench_ogr.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:311 +msgid "6.3" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:312 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:334 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:353 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:485 +msgid "bench_ogr.py" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:312 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:353 +msgid "71" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:313 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:335 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:354 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:518 +msgid "bench_fiona.py" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:313 +msgid "68" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:314 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:336 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:355 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:539 +msgid "bench_pyogrio_raw.py" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:314 +msgid "40" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:315 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:337 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:356 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:555 +msgid "bench_pyogrio.py" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:315 +msgid "108" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:316 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:338 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:357 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:570 +msgid "bench_geopandas.py" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:316 +msgid "232" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:317 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:339 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:358 +msgid "bench_ogr_batch.cpp (driver impl.)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:317 +msgid "4.5" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:318 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:340 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:359 +msgid "bench_ogr_batch.cpp (base impl.)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:318 +msgid "14" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:319 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:341 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:360 +msgid "bench_ogr_to_geopandas.py (driver impl.)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:319 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:360 +msgid "10" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:320 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:342 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:361 +msgid "bench_ogr_to_geopandas.py (base impl.)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:320 +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:342 +msgid "20" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:323 +msgid "" +"\"driver impl.\" means that the specialized implementation of " +"GetArrowStream() is used. \"base impl.\" means that the generic " +"implementation of GetArrowStream(), using GetNextFeature() underneath, is" +" used." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:328 +msgid "nz-building-outlines.parquet (GeoParquet, 436 MB)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:333 +msgid "6.4" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:334 +msgid "72" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:335 +msgid "70" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:336 +msgid "46" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:337 +msgid "115" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:338 +msgid "228" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:339 +msgid "1.6" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:340 +msgid "13.8" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:341 +msgid "6.8" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:345 +msgid "" +"Note: Fiona slightly modified to accept Parquet driver as a recognized " +"one." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:347 +msgid "nz-building-outlines.gpkg (GeoPackage, 1.7 GB)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:352 +msgid "7.6" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:354 +msgid "63" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:355 +msgid "41" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:356 +msgid "103" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:357 +msgid "227" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:358 +msgid "4.8" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:359 +msgid "15.5" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:361 +msgid "21" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:365 +msgid "This demonstrates that:" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:367 +msgid "" +"the new API can yield significant performance gains to ingest a OGR layer" +" as a GeoPandas GeoDataFrame, of the order of a 4x - 10x speed-up " +"compared to pyogrio, even without a specialized implementation of " +"GetArrowStream(), and with formats that have a natural row organization " +"(FlatGeoBuf, GeoPackage)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:373 +msgid "" +"the Parquet driver is where this shines most due to the file organization" +" being columnar, and its native access layer being ArrowArray compatible." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:376 +msgid "" +"for drivers that don't have a specialized implementation of " +"GetArrowStream() and whose layout is row oriented, the GetNextFeature() " +"approach is (a bit) faster than GetArrowStream()." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:383 +msgid "Only API additions, fully backward compatible." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:385 +msgid "The C++ ABI changes due to the addition of virtual methods." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:388 +msgid "New dependencies" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:390 +msgid "For libgdal: none" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:392 +msgid "" +"The Apache Arrow C data interface just defines 2 C structures. GDAL " +"itself does not need to link against the Apache Arrow C++ libraries (it " +"might link against them, if the Arrow and/or Parquet drivers are enabled," +" but that's orthogonal to the topic discussed in this RFC)." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:397 +msgid "" +"For Python bindings: none at compile time. At runtime, pyarrow is " +"imported by GetArrowStreamAsPyArrow(). The GetArrowStreamAsNumPy() method" +" is implemented internally by the gdal_array module, and thus is only " +"available if Numpy is available at compile time and runtime." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:406 +msgid "" +"New methods are documented, and a new documentation page will be added in" +" the documentation." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:412 +msgid "New methods are tested." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:417 +msgid "https://github.com/OSGeo/gdal/compare/master...rouault:arrow_batch_new?expand=1" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:422 +msgid "Annexes" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:429 +msgid "Use of traditional GetNextFeature() and related API from C" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:487 +msgid "" +"Use of traditional GetNextFeature() and related API from Python (port of " +"bench_ogr.cpp)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:520 +msgid "" +"Use of the Fiona Python library which uses the OGR C GetNextFeature() " +"underneath to expose them as GeoJSON features holded by a Python " +"dictionary." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:532 +msgid "" +"Changing the above loop to ``list(features)`` to accumulate features has " +"a significant negative impact on memory usage on big datasets, and on " +"memory usage." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:541 +msgid "" +"Use of the pyogrio Python library which uses the OGR C GetNextFeature() " +"underneath to expose a layer as a set of Arrow arrays." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:557 +msgid "" +"Use of the pyogrio Python library which uses the OGR C GetNextFeature() " +"underneath to expose a layer as GeoPandas GeoDataFrame (which involves " +"parsing WKB as GEOS objects)" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:572 +msgid "" +"Use of the GeoPandas Python library which uses Fiona underneath to expose" +" a layer as GeoPandas GeoDataFrame." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:585 +msgid "bench_ogr_batch.cpp" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:587 +msgid "Use of the proposed GetNextRecordBatch() API from C++" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:626 +msgid "bench_ogr_to_geopandas.py" +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:628 +msgid "" +"Use of the proposed GetNextRecordBatchAsPyArrow API from Python, to build" +" a GeoPandas GeoDataFrame from the concatenation of the returned arrays." +msgstr "" + +#: ../../source/development/rfc/rfc86_column_oriented_api.rst:684 +msgid "+1 from PSC members MateuszL, JukkaR, HowardB and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:5 +msgid "RFC 87: Signed int8 data type for raster" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:10 +msgid "2022-Nov-8" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:11 +msgid "Adopted and implemented" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:12 +#: ../../source/development/rfc/rfc88_googletest.rst:12 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:12 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:12 +#: ../../source/development/rfc/rfc91_dataset_close.rst:12 +#: ../../source/development/rfc/rfc93_update_feature.rst:12 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:12 +msgid "GDAL 3.7" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:18 +msgid "" +"This RFC describes the addition of a new GDT_Int8 data type, for signed " +"8-bit integer data, to the GDALDataType enumeration." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:24 +msgid "" +":ref:`rfc-14` introduced in GDAL 1.5.0 a way of specifying that a 8-bit " +"integer should be interpreted as signed, by (ab)using the GDT_Byte type, " +"with the addition of the PIXELTYPE=SIGNEDBYTE metadata item in the " +"IMAGE_STRUCTURE metadata domain of bands for which this is desired." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:29 +msgid "" +"While this approach avoided the introduction of a new data type, which " +"has consequences internally in the GDAL code base at all places where a " +"\"switch\" is done on a GDALDataType variable, as well as impact on " +"external code using GDAL, this historical approach had the following " +"shortcomings:" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:34 +msgid "" +"drivers that need to support reading signed 8-bit integers must remind to" +" expose the PIXELTYPE=SIGNEDBYTE metadata item." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:37 +msgid "" +"drivers that need to support writing signed 8-bit integers must provide a" +" creation option for that purpose (generally called PIXELTYPE=SIGNEDBYTE " +"itself)." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:41 +msgid "" +"but more importantly, the absence of a proper data type means that it is " +"easy to forget to test the PIXELTYPE=SIGNEDBYTE metadata item in all " +"places where the value of pixels is taken into account. There were " +"special cases for statistics computations, but most of the other code, " +"such as the overview or warping computation code had no provision for it," +" and consequently mis-interpreted negative values in the range [-128,-1] " +"as positive values in the range [128,255]." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:52 +msgid "" +"A new ``GDT_Int8`` = 14 item is added to the :cpp:enum:`GDALDataType` " +"enumeration." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:54 +msgid "" +"It is taken into account in all places in gcore/ and alg/ that have " +"specific behavior depending on the value of GDALDataType. All places that" +" only dealt specifically with a subset of types (e.g Byte, Float32) and " +"promoted other types to the closest one will automatically have proper " +"support for the new data type (e.g overview computation)." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:60 +msgid "" +"Existing drivers that, on reading, reported GDT_Byte + " +"PIXELTYPE=SIGNEDBYTE are modified to report GDT_Int8. This has backward " +"compatibility impact to external code. This affects the EEDAI, ERS, GTA, " +"GTiff, HFA, netCDF, PostGISRaster, EHDR, RRaster, Rasterlite2 and Zarr " +"drivers." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:65 +msgid "" +"Existing drivers that, on writing, accepted the PIXELTYPE=SIGNEDBYTE, are" +" modified to accept GDT_Int8 as a valid data type in their " +"Create()/CreateCopy() implementations, and advertise \"GDT_Int8\" in " +"their GDAL_DMD_CREATIONDATATYPES metadata item. The PIXELTYPE=SIGNEDBYTE " +"creation option is kept but deprecated and discouraged: working with it " +"prior to this RFC was clunky at times, and will remain such." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:71 +msgid "" +"The MEM, HDF4, HDF5, KEA and PDS4 drivers are extended to support " +"GDT_Int8 on reading (and writing, except HDF5 that is read-only)." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:77 +msgid "The GDT_Int8 constant is made available in SWIG bindings." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:79 +msgid "" +"The numpy interface of the Python bindings is modified to map GDT_Int8 to" +" ``numpy.int8``." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:85 +msgid "" +"The PIXELTYPE=SIGNEDBYTE band metadata item in IMAGE_STRUCTURE is no " +"longer reported. Code that depended on it needs to switch testing for " +"GDT_Int8. Code that has \"switch\"-like constructs on GDALDataType must " +"also account for GDT_Int8." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:93 +msgid "" +"Documentation of utilities that have a ``-ot`` switch is modified to " +"mention Int8." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:95 +msgid "" +":ref:`rfc-14` will be amended to point to this RFC, and mention that " +"starting with GDAL 3.7.0, PIXELTYPE=SIGNEDBYTE is no longer the technical" +" solution." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:101 +msgid "" +"The test_gdal.cpp and testcopywords.cpp test files are extended to test " +"functions like :cpp:func:`GDALDataTypeIsInteger`, " +":cpp:func:`GDALDataTypeIsFloating`, :cpp:func:`GDALDataTypeIsComplex`, " +"etc. and all data type conversion combinations from/into GInt8." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:106 +msgid "" +"Parts of autotest, in driver specific tests, that were testing GByte + " +"PIXELTYPE=SIGNEDBYTE on reading or writing are adapted to the new " +"technical solution." +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:110 +#: ../../source/development/rfc/rfc88_googletest.rst:224 +msgid "Related tickets and PRs:" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:112 +msgid "https://github.com/OSGeo/gdal/issues/4002" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:114 +msgid "https://github.com/OSGeo/gdal/pull/6633" +msgstr "" + +#: ../../source/development/rfc/rfc87_signed_int8.rst:119 +msgid "+1 from KurtS, JukkaR, MateuszL and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:5 +msgid "RFC 88: Use GoogleTest framework for C/C++ unit tests" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:10 +msgid "2022-Nov-16" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:18 +msgid "" +"The document proposes and describes conversion of the existing C/C++ " +"autotest suite to use the `GoogleTest framework " +"<https://github.com/google/googletest>`__." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:22 +msgid "" +"GoogleTest is a popular and maintained framework for C/C++ test writing, " +"that is a better replacement for the `TUT framework " +"<https://github.com/mrzechonek/tut-framework>`__ that we use currently." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:29 +msgid "" +"The current TUT framework was adopted in 2006, and copied from the GEOS " +"project. While it works reasonably well, its use has the following " +"drawbacks:" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:32 +msgid "" +"TUT has little upstream activity. The last tagged release was apparently " +"in 2016." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:35 +msgid "We have an internal copy in our repository that might have diverged." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:37 +msgid "" +"TUT is, to the best of our understanding, not very popular among C/C++ " +"projects that have a regression test suite, which adds a (small) learning" +" curve to new contributors." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:41 +msgid "" +"One of TUT main practical disadvantages is that it is not obvious to know" +" which assertion has failed in a given test, unless adding a text string " +"describing the assertion, and often redundant with it. Like " +"``ensure_equals(\"x = 2\", x, 2);`` or some number like " +"``ensure_equals(\"(1)\", x, 2);``. In GoogleTest, you just write " +"``EXPECT_EQ(x, 2);`` and if it fails the filename and line number will be" +" printed in the error log, as well as the value of ``x``. With " +"GoogleTest, you may also provide additional context that will be output " +"when an assertion fails to help diagnose the reason of the failure, e.g.:" +" ``EXPECT_EQ(x, 2) << \"if that matters, y = \" << y;``" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:52 +msgid "" +"Another issue I stumbled upon a few months ago is that the default limit " +"for a given test group is 50 steps. If you don't increase it explicitly, " +"tests beyond the 50th one will be compiled but not run, without any " +"compile or runtime failure. One might easily believe they are successful " +"when they are not run at all!" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:57 +msgid "A few GoogleTest advantages:" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:59 +msgid "" +"It has been adopted by PROJ as its C/C++ test framework, and it makes " +"sense to use the same technologies whenever it makes sense given the " +"relationship of the 2 projects." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:63 +msgid "It has extensive documentation: https://google.github.io/googletest/" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:65 +msgid "" +"GoogleTest distinguishes assertions that must abort the test when failed " +"(ASSERT_xxxx) from those where the test can continue (EXPECT_xxxx), which" +" can be useful." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:69 +msgid "" +"The only noticed inconvenience of GoogleTest-based tests is that they " +"might be quite slow to compile in optimized mode (probably related to " +"https://github.com/google/googletest/issues/1478). I've found that " +"forcing non-optimized mode when building tests reduces build time of " +"tests to a reasonable amount, while not having practical disadvantages: " +"it still allows to test the library built in optimized mode. This is what" +" is done in the candidate implementation." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:77 +msgid "" +"This RFC doesn't change the logic of deciding when C/C++-based vs Python-" +"based tests should be written. My own position is that Python-based tests" +" should be preferred when possible, as productivity is higher in Python " +"and there is no associated compilation time (compilation time affects " +"feedback received from continuous integration). C/C++-based test should " +"be reserved for C++-specific aspects that cannot be tested with the SWIG " +"Python bindings, which use the C interface. For example testing of C++ " +"operators (copy/move constructors/assignment operators, iterator " +"interfaces, etc.) or C/C++ functionality not mapped to SWIG (e.g. CPL " +"utility functions/classes)" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:88 +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:36 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:94 +#: ../../source/development/rfc/rfc91_dataset_close.rst:50 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:67 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:93 +msgid "Technical details" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:90 +msgid "" +"GoogleTest >= 1.10 will be required. If available in the system, the " +"system GoogleTest library will be used. Otherwise the CMake " +"ExternalProject_Add() functionality is used to download and built it " +"transparently. Use of system vs downloaded framework can be controlled " +"with the USE_EXTERNAL_GTEST=YES/NO CMake variable. This logic is copied &" +" pasted from PROJ." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:96 +msgid "" +"All assertion based tests will be migrated to GoogleTest. The few " +"performance tests that don't have any assertions and do not use TUT will " +"be kept unmodified (at least for now)." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:100 +msgid "The autotest/cpp/tut directory will be removed." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:102 +msgid "The migration from TUT to GoogleTest is mostly mechanical:" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:104 +msgid "TUT groups ==> GoogleTest test suite or fixture" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:105 +msgid "``ensure_equals(a,b)`` ==> ``ASSERT_EQ(a,b)`` or ``EXPECT(a,b)``" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:106 +msgid "``ensure(a)`` ==> ``ASSERT_TRUE(a)`` or ``EXPECT(a)``" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:107 +msgid "" +"``ensure_almost_equal(a,b)`` ==> ``ASSERT_NEAR(a,b,tolerance)`` or " +"``EXPECT_NEAR(a,b,tolerance)``" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:108 +msgid "``ensure(a >= b)`` ==> ``ASSERT_GE(a,b)`` or ``EXPECT_GE(a,b)``" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:109 +msgid "etc." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:111 +msgid "" +"Customized ensure logic like ``ensure_equal_geometries(geom1, geom2)`` " +"can also be migrated cleanly as functions that result an AssertionResult:" +" https://google.github.io/googletest/advanced.html#using-a-function-that-" +"returns-an-assertionresult" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:115 +msgid "" +"``GTEST_SKIP() << \"reason for the skip\"`` can be used to skip tests for" +" which a build-time or run-time requirement is missing." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:118 +msgid "" +"GoogleTest also offers capabilities for parametrized tests that were not " +"existing in TUT and can be adopted where it makes sense." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:121 +msgid "" +"For example the following test in TUT that tested GDALDataTypeUnion() on " +"all potential combinations of (datatype1, datatype2)" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:147 +msgid "can be written in GoogleTest as" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:197 +msgid "" +"While it is admittedly more verbose (which is an exception, as for " +"simpler tests, the GoogleTest way is generally smaller than the TUT way) " +"but much more expressive when looking at the test run output, where each " +"combination is run as a given named test, and thus if failure occurs, it " +"is easy to spot which combination failed, whereas with TUT you had to add" +" manual instrumentation:" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:220 +msgid "" +"None. This doesn't affect the library, nor the release source code " +"archive which don't include the autotest/ directory." +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:226 +msgid "Ticket: https://github.com/OSGeo/gdal/issues/3525" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:228 +msgid "Implementation: https://github.com/OSGeo/gdal/pull/6732" +msgstr "" + +#: ../../source/development/rfc/rfc88_googletest.rst:233 +msgid "" +"+1from PSC members MateuszL, HowardB, JukkaR, KurtS , FrankW, DanielM and" +" EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:5 +msgid "RFC 89: SQL logging callback" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:9 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:9 +msgid "elpaso @ itopen.it" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:10 +msgid "2022-Nov-30" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:18 +msgid "" +"The document proposes and describes the introduction of a new callback " +"function to allow applications that use the GDAL library to monitor the " +"SQL queries actually sent from GDAL to the database." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:25 +msgid "" +"Applications (for example QGIS) may provide a debugging panel that allow " +"users to monitor the SQL command that are sent to the layers stored on " +"databases." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:29 +msgid "" +"This panel implemented in QGIS is very useful to identify erroneous or " +"inefficient queries and also made the users more conscious about what is " +"going on in the application when layers are loaded and features are " +"fetched." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:38 +msgid "" +"The implementation details are still to be defined, a possible " +"implementation would provide a method to `GDALDataset` that allows client" +" code to set the callback function (with some opaque context to be passed" +" back to client code)." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:43 +msgid "" +"The callback function will then be called from the drivers that make " +"database calls each time a SQL command is sent to the backend, in case of" +" prepared queries the actual SQL after parameter substitutions should be " +"sent." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:48 +msgid "" +"The callback will provide additional information about the executed query" +" (if available):" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:51 +msgid "error string message" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:52 +msgid "number of affected/retrieved records" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:53 +msgid "time taken to execute the query" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:56 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:118 +msgid "Example API:" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:77 +msgid "" +"The callback function will be initially used by the SQLite-based drivers " +"only (GPKG included)." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:79 +msgid "" +"The callback may be called by multiple threads in a concurrent way, for " +"this reason the implementation of the callback should be robust to that " +"(use of lock typically). That problem may arise in drivers that use " +"multi-threading as an optimization implementation detail. And this is " +"typically the case of the GeoPackage driver in its Arrow stream " +"interface." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:87 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:145 +msgid "Efficiency considerations" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:89 +msgid "" +"Drivers that support the query logger callback function would need to " +"check if the function pointer is `nullptr` and call the function if it is" +" not. The cost of thish check is probably negligible on most " +"architectures." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:93 +msgid "" +"In order to catch SQLite prepare errors, a prepare function wrapper will " +"be called instead of the sqlite3 API C function, this implies the cost of" +" a function call (which might be inlined if necessary)." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:97 +msgid "" +"Comparison of current master release build with the proposed " +"implementation on a 145665553 feature 15GB GPKG Point layer stored on " +"fast SSD:" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:101 +#: ../../source/development/rfc/rfc93_update_feature.rst:199 +msgid "Benchmark" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:101 +msgid "Master" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:101 +msgid "Proposed implementation" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:103 +msgid "bench_ogr_batch" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:103 +msgid "0.13m" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:103 +msgid "0.12m" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:105 +msgid "bench_ogr_c_capi" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:105 +msgid "2.57m" +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:117 +msgid "" +"The callback would be set from a new method, no changes to the class " +"constructor would be needed." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:123 +msgid "This implementation will not be exposed to bindings." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:128 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:163 +msgid "A C++ test will be added to the test suite." +msgstr "" + +#: ../../source/development/rfc/rfc89_sql_logging_callback.rst:134 +msgid "+1 from PSC members MateuszL, JukkaR, TamasS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc8_devguide.rst:5 +msgid "RFC 8: Developer Guidelines" +msgstr "" + +#: ../../source/development/rfc/rfc8_devguide.rst:11 +msgid "Status: draft" +msgstr "" + +#: ../../source/development/rfc/rfc8_devguide.rst:16 +msgid "" +"This document used to document developer practices for the GDAL/OGR " +"project. As it was an evolving document, its content has been moved to " +":ref:`development_practices`." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:5 +msgid "RFC 90: Direct access to compressed raster data" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:9 +#: ../../source/development/rfc/rfc91_dataset_close.rst:9 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:9 +msgid "even.rouault at spatialys.com" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:10 +msgid "2023-Jan-03" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:18 +msgid "" +"The document proposes 2 new methods to directly obtain the content of a " +"window of interest of a raster dataset in its native compressed format. " +"Those methods can be optionally implemented and used by drivers to " +"perform:" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:22 +msgid "" +"extraction of a compressed tile as a standalone file from a container " +"format (GeoTIFF, GeoPackage, etc.)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:25 +msgid "creation of mosaics from a set of tiles in individual files" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:27 +msgid "" +"lossless conversion between container formats using the same compression " +"method" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:33 +msgid "" +"When converting data between formats, calls to RasterIO(GF_Read, ...) " +"followed by RasterIO(GF_Write, ...) must be currently done. For " +"compressed formats, this causes decompression and recompression of data." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:37 +msgid "" +"In some particular cases, we could avoid decompressing and recompressing " +"when the underlying compression method is the same (or compatible), and " +"when requesting data aligned on the boundaries of the encoded data " +"(typically whole tiles). This would save execution time and would avoid " +"extra quality loss due to recompression cycles for lossy compression " +"methods." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:43 +msgid "" +"This RFC offers the framework to potentially address the following use " +"cases (non exhaustive list):" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:46 +msgid "" +"extraction of a JPEG (resp. WEBP, JPEGXL)-compressed whole tile from a " +"GeoTIFF file to a standalone JPEG (resp. WEBP, JPEGXL) file. Typical " +"scenario of tile servers using a GeoTIFF file as a tile backend." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:50 +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:55 +msgid "" +"similarly as above, but with GeoPackage and JPEG/PNG/WEBP compression " +"methods." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:52 +msgid "" +"extraction of a subset of whole tiles of a JPEG/WEBP/JPEGXL-compressed " +"tiled GeoTIFF to a tiled GeoTIFF using the same compression method." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:57 +msgid "" +"lossless conversion of a mosaic of JPEG, WEBP, etc. non-overlapping and " +"contiguous tiles, each in a separate file, assembled as a VRT mosaic, to " +"a tiled GeoTIFF using the same compression method, with the tile " +"dimension being the one of each source file." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:62 +msgid "" +"lossless conversion of a JPEG-compressed (resp. WEBP-compressed) tiled " +"GeoTIFF to a JPEG-compressed (resp. WEBP-compressed) GeoPackage file and " +"vice-versa. Or a subset of the file, provided that the window of interest" +" is aligned on tiles boundaries." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:67 +msgid "" +"lossless conversion of JPEG to JPEGXL (currently implemented in master in" +" a rather ad-hoc way in the JPEGXL driver)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:70 +msgid "" +"lossless conversion of JPEGXL that has JPEG reconstruction box back to " +"JPEG (currently implemented in master in a rather ad-hoc way in the " +"JPEGXL and JPEGXL drivers)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:74 +msgid "" +"lossless conversion of JPEG-compressed tiled GeoTIFF to a JPEGXL-" +"compressed tiled GeoTIFF (and the reverse if JPEG reconstruction box is " +"included). Or a subset of the file, provided that the window of interest " +"is aligned on tiles boundaries." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:79 +msgid "" +"extraction of a subset of a JPEG-compressed tiled GeoTIFF to a standalone" +" JPEG file, with a window of interest not necessarily aligned on tile " +"boundaries, but just on the JPEG MCU (Minimum Code Unit), which is equal " +"to 8 pixels in the general case, and 16 for YCbCr data. And when " +"intersecting several tiles, provided that they share the same quality " +"settings (which is usually the case!) Or lossless retiling of JPEG-" +"compressed tiled GeoTIFF (e.g 256x256 -> 512x512)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:88 +msgid "" +"The proposed candidate implementation only covers a subset of those use " +"cases (some of them would require significant implementation effort), but" +" the proposed API addition makes them possible pending further " +"developments." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:96 +msgid "" +"The following 2 new methods are added at the :cpp:class:`GDALDataset` " +"level:" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:99 +msgid "GetCompressionFormats()" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:158 +msgid "" +"For example, to check if native compression format(s) are available on " +"the whole image:" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:179 +msgid "ReadCompressedData()" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:263 +msgid "" +"For example, to request JPEG content on the whole image and let GDAL deal" +" with the buffer allocation." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:295 +msgid "Or to manage the buffer allocation on your side:" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:342 +msgid "LOSSLESS_COPY creation option" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:344 +msgid "" +"Those methods are typically used by a GDALDriver::CreateCopy() " +"implementation to short-circuit the nominal logic of acquiring pixels " +"from the source and compressing them and use instead the compressed data " +"if available in the desired target compression format." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:349 +msgid "" +"Drivers that implement such short-circuit should expose a LOSSLESS_COPY " +"creation option, whose default value is AUTO, to mean that use of source " +"compressed data should be done in priority, and fallback to the regular " +"code path otherwise. Users might set it to YES to require the use of " +"lossless copy, and, when it is not possible to use it, the driver should " +"error out. Users might also set it to NO to ask for the regular code path" +" to be taken. Setting it to NO should be uncommon. This is a provision in" +" case the optimized code path would have bugs, or if for any other " +"reason, the regular code path must be taken (if the source compressed " +"data was not fully conformant for example)." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:361 +msgid "Miscellaneous" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:363 +msgid "" +"A helper ``bool GDALDataset::IsAllBands(int nBandCount, const int " +"*panBandList) const`` method is also added to check if (nBandCount, " +"panBandList) requests all the bands of the dataset." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:369 +msgid "Intended use" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:371 +msgid "" +"This RFC does *not* deprecate the traditional RasterIO() usage by any " +"means. Its main intended users are (some) CreateCopy() implementations." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:374 +msgid "" +"Clearly, the use of ReadCompressedData() is an advanced one, which often " +"requires a good understanding of some low-level characteristics of the " +"compression methods to be used properly (e.g. not all formulations of " +"JPEG codestreams are usable as a JPEG-in-TIFF or supported by libjxl in " +"JPEG lossless transcoding, which requires to examine the output of the " +"new helper GDALGetCompressionFormatForJPEG() function)." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:384 +msgid "" +"The 2 above C++ methods are available in the C API as " +"``GDALDatasetGetCompressionFormats()`` and " +"``GDALDatasetReadCompressedData()``. The return of " +"GDALDatasetGetCompressionFormats() should be freed with " +":cpp:func:`CSLDestroy`." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:392 +msgid "No backward incompatibility. Only API addition." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:394 +msgid "" +"For driver using ReadCompressedData() in their CreateCopy() " +"implementation, generated files might be changed, with more frequent " +"lossless conversions." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:400 +msgid "The new functions will *not* be exposed to bindings currently." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:405 +msgid "" +"The scenarios covered by the below proposed implementation will be tested" +" by C++ unit tests (unit testing of GetCompressionFormats() and " +"ReadCompressedData() implementations), and in Python autotest suite for " +"end-to-end tests (e.g lossless JPEG -> JPEGXL -> JPEG)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:411 +#: ../../source/development/rfc/rfc91_dataset_close.rst:183 +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:281 +msgid "Issues / pull requests" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:413 +msgid "" +"https://github.com/OSGeo/gdal/compare/master...rouault:gdal:ReadCompressedData?expand=1" +" contains a candidate implementation with the following capabilities:" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:416 +msgid "" +"core empty implementation of GetCompressionFormats() and " +"ReadCompressedData()" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:418 +msgid "" +"implement ReadCompressedData() in the GeoTIFF driver for JPEG/WEBP/JPEGXL" +" compression (limited to extracting a single tile for now)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:421 +msgid "" +"implement ReadCompressedData() in the VRT driver (limited to a single " +"source for now, which forwards the call to the source)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:424 +msgid "implement ReadCompressedData() in the JPEG driver." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:426 +msgid "" +"use ReadCompressedData() in the JPEG driver (with pszFormat equal to " +"\"JPEG\") in its CreateCopy() implementation, and expose the " +"LOSSLESS_COPY creation option" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:430 +msgid "" +"implement ReadCompressedData() in the JPEGXL driver, returning both " +"\"JXL\" of course, but also \"JPEG\" if the JPEGXL file includes a JPEG " +"reconstruction box." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:433 +msgid "" +"use ReadCompressedData() in the JPEGXL driver, with pszFormat equal to " +"\"JPEG\" or \"JXL\", in its CreateCopy() implementation, and expose the " +"LOSSLESS_COPY creation option" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:437 +msgid "implement ReadCompressedData() in the WEBP driver." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:439 +msgid "" +"use ReadCompressedData() in the WEBP driver (with pszFormat equal to " +"\"WEBP\") in its CreateCopy() implementation, and expose the " +"LOSSLESS_COPY creation option" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:443 +msgid "Given the above, the following scenarios are for example covered:" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:445 +msgid "" +"gdal_translate -srcwin of a tile of a JPEG (resp. JPEGXL, " +"WEBP)-compressed tiled GeoTIFF to JPEG (resp. JPEGXL, WEBP). (involves " +"the GTiff and VRT drivers as producers, the JPEG/JPEGXL/WEBP drivers as " +"consumers)" +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:450 +msgid "" +"gdal_translate of a JPEGXL file with JPEG reconstruction box to JPEG " +"(involves the JPEGXL driver as producer, the JPEG driver as consumer). " +"And the reverse operation: lossless conversion of JPEG to JPEGXL with a " +"JPEG reconstruction box." +msgstr "" + +#: ../../source/development/rfc/rfc90_read_compressed_data.rst:458 +msgid "+1 from PSC members JukkaR, FrankW, SeanG, MateuzL and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:5 +msgid "RFC 91: GDALDataset::Close() method" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:10 +msgid "2023-Jan-20" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:18 +msgid "" +"This RFC aims at providing more robust error detection during dataset " +"closing, in particular for datasets in creation/update mode." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:21 +msgid "" +"It modifies the GDALDataset::FlushCache() method and GDALFlushCache() " +"function to return an error code, adds a GDALDataset::Close() virtual " +"method and modifies GDALClose() to return an error code." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:28 +msgid "" +"A lot of drivers that have write capabilities may do write operations in " +"their destructors, or just close the file descriptor owned by the " +"dataset. Currently there is no clean way of catching errors that might " +"occur. This recently bit `Fiona " +"<https://github.com/Toblerity/Fiona/issues/1169>` where the GeoJSON " +"driver may emit an error in its dataset destructor when writing the " +"content of a file to a cloud object storage." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:35 +msgid "" +"Code that currently wants to detect if GDALClose() causes an error has to" +" do something like the following:" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:45 +msgid "" +"This is awkward and there is a risk that something in the chain of calls " +"would clean the error state. It is thus desirable for the GDALClose() " +"method to return an error code." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:52 +msgid "" +"The GDALDataset::FlushCache() method is modified to return a CPLErr " +"return value." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:54 +msgid "A new virtual method GDALDataset::Close() is added." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:81 +msgid "A typical implementation might look as the following:" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:131 +msgid "" +"The default GDALDataset::Close() implementation sets nOpenFlags to " +"OPEN_FLAGS_CLOSED" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:137 +msgid "" +"GDALClose() and GDALFlushCache() are modified to return a CPLErr return " +"value." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:142 +msgid "" +"This is an ABI change that should not require more than rebuilding " +"applications against GDAL headers." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:145 +msgid "" +"For out-of-tree drivers that implement GDALDataset::FlushCache(), they " +"need to take into account the change in its signature." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:148 +msgid "" +"Out-of-tree drivers that have write capabilities are also encouraged to " +"implement GDALDataset::Close()." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:154 +msgid "" +"Not all drivers will be modified to implement Close() in the candidate " +"implementation, and even those modified might call internal methods of " +"the driver that do not do error propagation. Consequently, further work " +"might be needed on a case-by-case to improve driver implementations." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:162 +msgid "" +"The destructor of gdal.Dataset is modified to test the return value of " +"GDALClose() and emits a CPLError(CE_Failure, ...) if the error state is " +"clean (normally it should not)" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:167 +msgid "C/C++ command line utilities" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:169 +msgid "" +"C/C++ command line utilities are modified to test the return value of " +"GDALClose() on output datasets, and return a non-zero return code for the" +" process if GDALClose() returns an error." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:176 +msgid "" +"autotest/pymod/gdaltest.py::testCreate() is modified to call FlushCache()" +" and test its return value." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:179 +msgid "" +"The existing tests of the C/C++ command line utilities test GDALClose() " +"modified behavior." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:185 +msgid "Addresses https://github.com/OSGeo/gdal/issues/6886" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:187 +msgid "" +"https://github.com/OSGeo/gdal/compare/master...rouault:gdal:dataset_FlushCache_return_CPLErr?expand=1" +" contains a candidate implementation." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:190 +msgid "The candidate implementation does the following:" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:192 +msgid "Update all drivers that implements GDALDataset::FlushCache()." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:193 +msgid "" +"Implements GDALDataset::Close() for all drivers that derive from " +"RawDataset." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:194 +msgid "" +"Implements GDALDataset::Close() in the GeoJSON, GTiff, ODS, XLSX, SQLite," +" GPKG, netCDF, JP2OpenJPEG, FlatGeoBuf and OpenFileGDB drivers." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:196 +msgid "" +"Modifies all C/C++ command line utilities to test the return value of " +"GDALClose()" +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:197 +msgid "Tests GDALClose() return value in gdal.Dataset destructor." +msgstr "" + +#: ../../source/development/rfc/rfc91_dataset_close.rst:202 +msgid "+1 from PSC members KurtS, MateuszL and me, and +0 from JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:5 +msgid "RFC 92: WKB Only geometries (on hold)" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:10 +msgid "2023-Jan-31" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:11 +msgid "On hold" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:12 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:64 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:68 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:70 +msgid "N/A" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:18 +msgid "" +"This RFC provides shortcuts to avoid instantiation of full OGRGeometry " +"instances in scenarios where only the WKB representation of geometries is" +" needed. The hope is to save CPU time." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:22 +msgid "This RFC is on hold." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:27 +msgid "" +"Some consumers of the OGR feature API only use the WKB representation of " +"the geometry. This is typically the case in the QGIS OGR provider (a QGIS" +" \"provider\" ~= a GDAL driver) which creates the corresponding " +"QgsGeometry instance from WKB." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:32 +msgid "" +"The format of geometries of some popular formats like GeoPackage or " +"PostGIS is based on WKB. Consequently the chain of processings done by " +"QGIS reading GeoPackage is:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:36 +msgid "GDAL side:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:38 +msgid "" +"acquire GeoPackage geometry blob (WKB with a GeoPackage specific header) " +"from the database" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:40 +msgid "" +"instantiate the relevant OGRGeometry subclass instance (OGRPoint, " +"OGRLineString, OGRPolygon, etc.) from WKB" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:42 +msgid "store it in a OGRFeature" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:44 +msgid "QGIS side:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:46 +msgid "get the OGRGeometry from the OGRFeature" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:47 +msgid "" +"asks for its WKB representation, build from the subclass members (not the" +" original WKB of step 2.)" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:49 +msgid "instantiate QgsGeometry from WKB" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:51 +msgid "" +"One can see that if we were able to store the original WKB representation" +" and get it back we could save OGRGeometry subclass object creation, " +"destruction and WKB deserialization and serialization." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:55 +msgid "" +":ref:`rfc-86` has seen related performance boosts since ArrowArray " +"batches store the WKB representation of geometries and not OGRGeometry " +"instances. This RFC borrows the same idea, but applying it to the " +"traditional feature API, as switching to ArrowArray API is a significant " +"undertaking for GDAL users." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:60 +msgid "" +"That could also be used in the future for a generic implementation of a " +"potential OGRLayer::WriteArrowArray() method that would build temporary " +"OGRFeature objects from the rows of the array to call the " +"ICreateFeature() implementation: the temporary geometries could be " +"OGRWKBOnlyGeometry instances for drivers such as GeoPackage that use WKB " +"natively." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:69 +msgid "" +"The proposal mostly contains in adding a new subclass of OGRGeometry " +"called `OGRWKBOnlyGeometry`" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:111 +msgid "A new method is added to the OGRLayer class:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:122 +msgid "Two new capabilities are added at the OGRLayer level:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:124 +msgid "" +"OLCReadWKBGeometries: a layer must return TRUE for it when the layer can " +"honour RequestWKBOnlyGeometries(true)" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:126 +msgid "" +"OLCWriteWKBGeometries: a layer must return TRUE for it if its " +"CreateFeature() and SetFeature() implementations support being passed " +"OGRWKBOnlyGeometry instances." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:130 +msgid "" +"ogr2ogr is modified to call RequestWKBOnlyGeometries(true) on the source " +"layer:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:132 +msgid "if the source layer advertises OLCReadWKBGeometries" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:133 +msgid "if the target layer advertises OLCWriteWKBGeometries" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:134 +msgid "if no command line switch requires a \"materialized\" geometry." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:136 +msgid "" +"So basically this is for requests like \"ogr2ogr out.gpkg in.gpkg [layer " +"or SQL request] [attribute filter] [spatial filter]\"" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:139 +msgid "" +"To be noted that while bounding box intersection in the case of " +"GeoPackage is done at the SQLite RTree level, the GeoPackage driver " +"currently does a \"client-side\" post filtering using GEOSIntersects() " +"(in situations where bounding box analysis only cannot conclude), so " +"geometry materialization is done in OGRLayer::FilterGeometry() for a " +"subset of features." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:148 +msgid "OGR_L_RequestWKBOnlyGeometries() is added." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:153 +msgid "No issue. Only API additions" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:156 +msgid "Benchmarking" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:159 +msgid "bench_ogr_c_api" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:161 +msgid "" +"The `bench_ogr_c_api " +"<https://github.com/OSGeo/gdal/blob/master/perftests/bench_ogr_c_api.cpp>`_" +" benchmark utility which uses the C API to iterate over features and get " +"their WKB representation is enhanced with a `-wkb_only_geometry` switch " +"to call OGR_L_RequestWKBOnlyGeometries()." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:166 +msgid "" +"On a 1.6 GB GeoPackage (nz-building-outlines.gpkg) made of 3.2 million " +"features with simple polygons (typically quadrilaterals, building " +"footprints) and 13 attributes:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:170 +msgid "bench_ogr_c_api runs in 6.4 s" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:171 +msgid "bench_ogr_c_api -wkb_only_geometry runs in 5.0 s" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:173 +#, python-format +msgid "==> 22% faster" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:175 +#, python-format +msgid "" +"Other synthetic benchmarks show that the maximum speed-up is about 30% on" +" a dataset with 10 millions polygonal features of 10 points each." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:178 +msgid "" +"Conversely, the gain is much more modest, or close to null, with just a " +"few thousands of features that hold larger geometries (several thousands " +"of points each)." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:182 +msgid "" +"The gain is more in saving instantiation of OGRPolygon and OGRLinearRing " +"objects that in the size of their coordinate set." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:193 +#, python-format +msgid "" +"runs in 15.8 second in WKBOnlyGeometry mode vs 19.1 second without it " +"(master), hence a 17% speed-up." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:196 +#, python-format +msgid "" +"With spatial index creation enabled (multi-threaded), the wall clock time" +" difference is within measurement noise. And for singe threaded creation," +" the WKBOnlyGeometry mode is 5% faster." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:203 +msgid "Is it a good idea... ?" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:205 +msgid "" +"The design of OGRWKBOnlyGeometry is admittedly a bit clunky, or at least " +"at odds with other OGRGeometry subclasses, but nothing more elegant, " +"concise, performant and that doesn't change the whole OGRGeometry API and" +" driver implementations comes to mind." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:210 +msgid "" +"The scope is limited to a few drivers: GeoPackage, PostGIS (but the " +"current throughput of the driver is probably not sufficient for " +"OGRGeometry overhead to be noticeable), what else?" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:214 +msgid "" +"Should methods of OGRWKBOnlyGeometry that cannot work without " +"materialization of the real geometry return an error like done currently," +" or do the materialization on-the-fly when needed ? The motivation for " +"erroring out is to avoid silent performance issues related to " +"materialization." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:220 +msgid "Points raised during discussion" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:222 +msgid "" +"Sean Gillies: Wouldn't it be possible for all OGRFeatures to carry WKB " +"data by default and add a method to provide it to callers?" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:225 +msgid "" +"Even: That involve massive code rewrites in all drivers and wouldn't be " +"desirable from a performance point of view, because most drivers can't " +"generate WKB easily (PostGIS and GPKG are the exceptions rather the " +"norm). So either all other drivers should be modified to compose WKB at " +"hand (massive coding effort. Probably several weeks of effort and " +"significant risk of regressions). Or get it from the ExportToWkb() method" +" of the OGRGeometry instance they currently build, but then you pay the " +"price in memory and CPU time to generate WKB that might not be consumed " +"by users." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:234 +msgid "" +"Sean Gillies: And only construct an OGRGeometry when it's asked for? Such" +" as when GetGeometryRef is called?" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:237 +msgid "" +"Even: we could both make GetGeometryRef() and GetGeomFieldRef() virtual " +"methods whose default implementation would be the same as currently, ie. " +"return the value of the corresponding member variable in the base " +"OGRFeature class stored with " +"SetGeometry[Directly]()/SetGeomField[Directly]()" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:242 +msgid "And add a new virtual method:" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:244 +msgid "" +"virtual GByte* OGRFeature::GetWKBGeometry(int iGeomField, size_t* " +"pnOutSize) const" +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:246 +msgid "" +"whose default implementation would just use " +"GetGeomFieldRef(iGeomField)->ExportToWkb()." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:248 +msgid "" +"The few drivers that can provide a more efficient implementation (GPKG " +"typically) would create a derived class OGRFeatureGPKG with a specific " +"implementation of those new virtual methods to avoid systematic " +"OGRGeometry instantiation. The only drawback I see is that making " +"GetGeometryRef() and GetGeomFieldRef() virtual would have a slight " +"performance impact, but probably small enough." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:254 +msgid "" +"Dan Baston: I'm wondering about a more broad application of this. Would " +"it be helpful to have the ability to lazy-initialize an OGRGeometry from " +"multiple source types such as WKB and GEOS, initially storing only a " +"reference to the external data in WKB/GEOS/etc and actually materializing" +" the geometry when required? Then methods such as " +"OGRGeometry::exportToWkb and OGRGeometry::exportToGEOS could check the " +"external data type and use it directly if it is compatible, avoiding " +"materialization. This would avoid multiple conversions to/from GEOS in " +"cases where operations are chained, as well as allowing WKB to pass " +"directly between input and output drivers that support it. Relatedly, " +"this ability could be used to cache external-format data when it is " +"generated for an OGRGeometry, avoiding inefficiencies such as two " +"conversions to GEOS when checking to see if two geometries intersect " +"before calculating their intersection." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:268 +msgid "" +"Even: That's definitely something doable. At a minimum, you would have to" +" inspect the top geometry type to instantiate the appropriate OGRGeometry" +" subclass, and then its members could be lazy initialized, but that means" +" that all methods of OGRGeometry and its subclasses would have to do a " +"check whether the object has been fully initialized. There might be " +"performance implications for people doing for example " +"lineString->getX(idx) to iterate on big geometries, although branch " +"predictors of modern CPUs are probably very good at repeatedly evaluating" +" stuff like \"if (!materialized) materialize();\". The main drawback is " +"that is a substantial & risky change that requires to revisit *all* " +"methods of the geometry classes. For setters, you would also have to make" +" sure to invalidate the potentially initial WKB / GEOS source." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:283 +msgid "" +"https://github.com/OSGeo/gdal/compare/master...rouault:gdal:rfc92_implementation?expand=1" +" contains a preliminary candidate implementation." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:286 +msgid "" +"Not all subtleties have been taken into account in the prototype " +"implementation (like doing OGRSQL and requesting the OGR_GEOMETRY special" +" attribute)." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:289 +msgid "" +"OGRLayer::FilterGeometry() (used for spatial filter evaluation by " +"GetNextFeature()) uses OGRWKBOnlyGeometry::Materialize() for convenience " +"currently. This could be improved for geometry types that are directly " +"compatible of GEOS to pass directly the WKB to GEOS." +msgstr "" + +#: ../../source/development/rfc/rfc92_wkb_only_geometries.rst:297 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:183 +msgid "TBD" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:5 +msgid "RFC 93: OGRLayer::UpdateFeature() method" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:10 +msgid "2023-Feb-15" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:18 +msgid "" +"This RFC adds a new method in the OGRLayer class, UpdateFeature(), to be " +"able to update a subset of the attributes and geometry fields of a " +"feature." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:24 +msgid "" +"There are currently 2 ways of updating (in a broad sense) existing " +"features in drivers that support editing an existing feature:" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:27 +msgid "" +"through the SetFeature() method, which has roughly a Replace semantics. " +"All the fields of the passed feature are used to update the feature" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:29 +msgid "" +"through the UpsertFeature() method. UpsertFeature() semantics is: \"if " +"the passed feature doesn't exist, considering its feature id, then create" +" it, otherwise replace it with the existing feature\". So UpsertFeature()" +" is conceptually CreateFeature() or UpdateFeature()." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:34 +msgid "" +"However a number of use cases only involve updating a subset of the " +"fields of a feature, and not a full replacement:" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:37 +msgid "" +"Typically QGIS changeAttributeValues() and changeGeometryValues() " +"currently have to call GetFeature() on features they want to edit, modify" +" the desired fields and call SetFeature() to update the feature. This is " +"suboptimal from a performance point of view. Similarly pgsql-ogr-fdw " +"could potentially be enhanced to map its implementation of the UPDATE on " +"a OGR foreign table to use UpdateFeature() instead of a full replacement " +"with SetFeature()." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:43 +msgid "" +"SQL based drivers implement SetFeature() through the SQL UPDATE " +"statement, which does not require the full set of attributes to be " +"provided. Consequently UpdateFeature() would be a better match with their" +" native capability. SetFeature() updating all fields, even those not " +"modified, may cause triggers to be unnecessarily run (for example the " +"GeoPackage triggers related to updating the RTree of the spatial index)" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:49 +msgid "" +"no-SQL based drivers such as MongoDB have separate API to replace, upsert" +" or update features." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:51 +msgid "" +"The transactional profile of WFS 2 also distinguishes Update and Replace " +"commands." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:57 +msgid "" +"Similarly to CreateFeature(), SetFeature() and UpsertFeature(), two " +"methods are added in OGRLayer:" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:60 +msgid "" +"UpdateFeature(), non-virtual, and aimed at being the one called by the " +"end user. This method does a few sanity checks on the passed arguments " +"(the arrays containing the indices of the attributes to updated) and " +"convert curve geometries to linear ones if needed for layers that do not " +"support curve geometries (similarly as CreateFeature(), SetFeature() and " +"UpdateFeature())" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:67 +msgid "" +"IUpdateFeature(), virtual method implemented by drivers. A default " +"implementation is provided in the base OGRLayer class for drivers that " +"expose the OLCRandomWrite capability. The default implementation calls " +"GetFeature() to retrieve the current version of the feature, updates it " +"with the feature passed as argument to IUpdateFeature() and calls " +"ISetFeature() to replace the feature." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:74 +msgid "The prototype of UpdateFeature() is the following one:" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:145 +msgid "The corresponding C function ``OGR_L_UpdateFeature`` is added." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:147 +msgid "" +"The OGRLayerDecorator, OGRLayerPool, OGRMutexedLayer, OGRUnionLayer, " +"OGRWarpedLayer and OGREditableLayer utility classes that wrap other " +"layers are modified to take the new IUpdateFeature() virtual method into " +"account." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:154 +msgid "" +"The proposed implementation adds a dedicated implementation of " +"IUpdateFeature() in the following drivers: memory driver, PostgreSQL, " +"GPKG, MongoDB." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:157 +msgid "" +"Other drivers could potentially benefit from it, e.g Shapefile, where " +"separate updates of the .shp (geometries) and .dbf (attributes) files. " +"But not in scope of the initial implementation." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:162 +msgid "Design choices" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:164 +msgid "" +"Q: Why is it necessary to specify which fields of the feature passed to " +"UpdateFeature() should be taken into account?" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:167 +msgid "" +"A: For attributes, it could have been possible to rely on the set/unset " +"status of the fields, but for drivers that distinguish unset from NULL " +"(typically all JSON based drivers, or no-SQL driver which map to " +"key/value documents with a non-fixed schema), this would have make it " +"impossible to unset a field in the stored feature. And geometry fields " +"don't have a unset status, so it would be otherwise be impossible to " +"distinguish between setting the geometry to NULL or not modifying the " +"existing geometry." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:175 +msgid "" +"Q: Why having a default implementation of IUpdateFeature() in the " +"OGRLayer base class and not just returning OGRERR_UNSUPPORTED_OPERATION ?" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:178 +msgid "" +"A: The rationale is to make it easier for code to use UpdateFeature(), " +"even when the underlying driver does not have a specialized " +"implementation. User code that needs to know if a specialized " +"implementation is available (in particular if atomicity of changes is a " +"requirement) can test the OLCUpdateFeature capability (UpdateFeature() is" +" available as soon as the OLCRandomWrite capability is advertized)." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:185 +msgid "" +"Q: Is it appropriate that IUpdateFeature() implementations may alter the " +"feature passed to them ?" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:188 +msgid "" +"A: given that the purpose of UpdateFeature() is to only require the " +"modified fields to be specified, the feature generally cannot be used to " +"reflect the full state of the corresponding stored object. Consequently " +"modifying it has no anticipated drawbacks for intended use cases." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:196 +msgid "OGR_L_UpdateFeature() is mapped to SWIG's ogr.Feature.UpdateFeature()." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:201 +msgid "" +"A benchmark using the below Python script has been run to compare " +"updating a single field on a GeoPackage layer with 3.2 million features, " +"each with 13 attributes and small polygons, of a total size of 1.6 GB." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:205 +msgid "" +"The runtime using the new UpdateFeature() method is 38.5 seconds, versus " +"168 seconds using GetFeature() + SetFeature(), hence a x4.4 speed-up. The" +" speed-up should generally increase with the number of attributes per " +"feature." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:209 +msgid "" +"This is a good simulation of the benefit QGIS changeAttributeValues() " +"implementation could get by using UpdateFeature()." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:246 +msgid "None, new functionality." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:248 +msgid "" +"C++ ABI breakage due to a new virtual method, typical of functionality " +"introduced in GDAL minor versions." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:254 +msgid "The new functions and methods are documented." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:259 +msgid "" +"The API, base implementation and dedicated UpdateFeature() are tested by " +"new autotest checks." +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:263 +#: ../../source/development/rfc/rfc95_standard_int_types.rst:173 +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:493 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:313 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:725 +msgid "Related issues and PRs" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:265 +msgid "" +"https://github.com/OSGeo/gdal/issues/6544: Extend OGR API SetFeature to " +"control Replace vs Update behavior" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:268 +msgid "" +"https://github.com/qgis/QGIS/issues/46355: Saving a large edited point " +"layer takes far too long" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:271 +msgid "" +"Proposed implementation in " +"https://github.com/OSGeo/gdal/compare/master...rouault:gdal:update_feature?expand=1" +msgstr "" + +#: ../../source/development/rfc/rfc93_update_feature.rst:277 +msgid "+1 from PSC members Jukka, MateuszL and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:5 +msgid "RFC 94: Numeric fields width/precision metadata" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:10 +msgid "2023-Feb-17" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:18 +msgid "" +"The document proposes and describes the introduction of a couple of new " +"vector driver metadata that return information for numeric real fields " +"about how the precision and width have been calculated by the driver and " +"have to be interpreted." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:26 +msgid "" +"Applications (for example OGR/GDAL utils and QGIS) may require " +"information about the field width and precision in order to convert " +"between different formats or to validate user input on editing." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:30 +msgid "" +"Different drivers may calculate the width and precision differently by " +"including or not the decimal separator and/or the minus sign into the " +"calculated length." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:33 +msgid "" +"There is currently no way for an application to access this information " +"and this can lead to loss of width or precision while converting between " +"formats or when the application decides to stay on the safe side and " +"reduce the width reported by GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:37 +msgid "" +"Additionally, attention must be paid to the meaning of \"width\" and " +"\"precision\": OGR \"width\" corresponds to SQL \"precision\" and OGR " +"\"precision\" corresponds to SQL \"scale\"." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:41 +msgid "For reference:" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:43 +msgid "https://trac.osgeo.org/gdal/ticket/6960" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:44 +msgid "https://issues.qgis.org/issues/11755" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:45 +msgid "https://issues.qgis.org/issues/15188#note-8" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:46 +msgid "https://github.com/qgis/QGIS/issues/51849" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:50 +msgid "Current drivers behavior" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:52 +msgid "" +"Here is a list of the drivers and how they behave with respect to the " +"width and precision, (for databases we refer to the `NUMERIC` data type)." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:56 +msgid "Driver" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:56 +msgid "Width Includes Decimal Separator" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:56 +msgid "Width Includes Sign" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:58 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:59 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:65 +msgid "YES" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:59 +msgid "MapInfo" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:60 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:61 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:62 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:63 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:66 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:67 +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:69 +msgid "NO" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:62 +msgid "MSSQL" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:64 +msgid "GPKG" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:65 +msgid "CSV (from .csvt)" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:66 +msgid "HANA" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:67 +msgid "FlatGeoBuf" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:70 +msgid "MEM" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:75 +msgid "Notes about specific drivers" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:77 +msgid "GPKG: SQLite column affinity storage is 8-byte IEEE floating point number" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:78 +msgid "" +"GML: `xsd:decimal` with `totalDigits` and `fractionDigits`, " +"`xs:totalDigits` defines the maximum number of digits of decimal and " +"derived datatypes (both after and before the decimal point, not counting " +"the decimal point itself). `xs:fractionDigits`` defines the maximum " +"number of fractional digits (i.e., digits that are after the decimal " +"point) of an xs:decimal datatype." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:83 +msgid "" +"FlatGeoBuf: for Float fields, OGR_width = flatgeobuf_precision and " +"OGR_precision = flatgeobuf_scale (if flatgeobuf_scale != -1, or 0 if " +"flatgeobuf_scale == -1)" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:85 +msgid "" +"FileGDB: Scale is the number of digits to the right of the decimal point " +"in a number. For example, the number 56.78 has a scale of 2. Scale " +"applies only to fields that are double. Scale is always returned as 0 " +"from personal or File geodatabase fields. Precision is the number of " +"digits in a number. For example, the number 56.78 has a precision of 4. " +"Precision is only valid for fields that are numeric. Precision is always " +"returned as 0 from personal or File geodatabase fields" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:95 +msgid "" +"The change will be done at the driver metadata level with a couple of " +"flags that report the capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:98 +msgid "" +"The vector drivers will expose a metadata entry to define if the width of" +" the fields includes the decimal separator and/or the sign." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:101 +msgid "" +"If the metadata entry is undefined the feature is not supported (there is" +" no client-accessible width or precision constraint for numeric fields)." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:104 +msgid "" +"The feature will be exposed to the `ogr2ogr` application with a switch to" +" enable/disable the width reduction when converting from a format where " +"width includes the minus sign to a format where it doesn't. This is " +"useful when the user knows that the input data are all negative values " +"because in that that case it won't be necessary to add the extra width to" +" store it." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:109 +msgid "" +"To clarify, when converting from DBF to SQL the width is decreased by 1, " +"when converting from SQL to DBF the width is increased by 2." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:112 +msgid "" +"\"-1.23\" for .DBF needs width=5 and precision=2. In SQL, it needs " +"precision=3 and scale=2 \"12.34\" for DBF needs width=5 and precision=2. " +"In SQL, it needs precision=4 and scale=2" +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:115 +msgid "" +"This means that when converting from DBF to SQL we can safely reduce the " +"width by 1 but we cannot safely reduce it by 2 unless we are sure all " +"values are negative." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:158 +msgid "This implementation will be exposed to bindings." +msgstr "" + +#: ../../source/development/rfc/rfc94_field_precision_width_metadata.rst:169 +msgid "+1 from PSC members EvenR and JukkaR" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:5 +msgid "RFC 95: Use standard C/C++ integer types (proposed, *NOT* adopted)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:10 +msgid "2023-Sep-15" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:11 +msgid "Proposed, but *not* adopted" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:12 +msgid "GDAL 4.0" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:18 +msgid "" +"This RFC replaces the use of the custom integer types defined in " +"cpl_port.h (G[U]Int[8/16/32/64/Big]) by their standard " +"[u]int[8/16/32/64]_t C99/C++11 counterparts, as well as other derived " +"integer data types. Due to the API and ABI break, this will be " +"implemented in GDAL 4.0." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:26 +msgid "" +"The existing Gxxxxx typedefs have been defined at a time that predates " +"C99 and C++11 which introduced those fixed with integer types. If GDAL " +"would be created today, we would use C99 data types." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:30 +msgid "" +"Using those aliases, particularly GIntBig/GUIntBig which are not self-" +"explanatory on their actual width (64 bit), adds cognitive load to " +"developers." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:34 +msgid "" +"Due to their poor namespacing, those short typenames may occasionally " +"clash with other libraries. At a time, Poppler used a ``GBool`` data type" +" as well, which was clashing with GDAL's one." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:38 +msgid "" +"Other projects (e.g. libtiff), have recently switched from the use of " +"similar custom types to C99 ones." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:44 +msgid "The following data types replacement are done in the whole code base:" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:46 +msgid "``GBool`` --> ``bool`` (``GBool`` was aliased to ``int``)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:47 +msgid "``GInt8`` --> ``int8_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:48 +msgid "``GInt16`` --> ``int16_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:49 +msgid "``GUInt16`` --> ``uint16_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:50 +msgid "``GInt32`` --> ``int32_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:51 +msgid "``GUInt32`` --> ``uint32_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:52 +msgid "``GInt64`` --> ``int64_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:53 +msgid "``GUInt64`` --> ``uint64_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:54 +msgid "``GIntBig`` --> ``int64_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:55 +msgid "``GUIntBig`` --> ``uint64_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:57 +msgid "Other changes have been done for other integer data types:" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:59 +msgid "``vsi_l_offset``--> ``uint64_t``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:60 +msgid "``GSpacing`` --> ``int64_t`` (affects mostly C++ raster drivers)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:61 +msgid "" +"``GPtrDiff_t`` --> ``ptrdiff_t`` (affects the multidimensional C and " +"C++ API)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:63 +msgid "The following macro replacement are done in the whole code base:" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:65 +msgid "``CPL_FRMT_GIB`` --> ``\"%\" PRId64``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:66 +msgid "``CPL_FRMT_GUIB`` --> ``\"%\" PRIu64``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:67 +msgid "``GINT64_MAX`` --> ``std::numeric_limits<int64_t>::max()``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:68 +msgid "``GINT64_MIN`` --> ``std::numeric_limits<int64_t>::min()``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:69 +msgid "``GUINT64_MAX`` --> ``std::numeric_limits<uint64_t>::max()``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:70 +msgid "``GINTBIG_MAX`` --> ``std::numeric_limits<int64_t>::max()``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:71 +msgid "``GINTBIG_MIN`` --> ``std::numeric_limits<int64_t>::min()``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:72 +msgid "``GUINTBIG_MAX`` --> ``std::numeric_limits<uint64_t>::max()``" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:74 +msgid "" +"The old types are no longer used in the GDAL code base since their " +"definition is protected by ``#ifdef GDAL_USE_OLD_INT_TYPES``, which " +"external code might define to help for the migration (particularly if " +"supporting GDAL < 4.0 and GDAL >= 4.0 is needed)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:80 +msgid "Impacts in the code base" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:82 +msgid "" +"Significant part of the code base (735 files changed). Most changes have " +"been done in a automated way, with manual changes specifically for the " +"CPL_FRMT_GIB/CPL_FRMT_GUIB replacement which was harder to automate." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:90 +msgid "" +"While .i files are impacted to cope with the C type changes, the language" +" specific API of SWIG bindings is not impacted." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:96 +msgid "C and C++ API and ABI are impacted." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:98 +msgid "Main impacts are:" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:100 +msgid "" +"GBool was aliased to ``int``: changing to ``bool`` in C++ methods of the " +"OGRStyleXXXX classes affect the API and ABI. Impact should be modest as " +"this functionality is thought to be marginally used, and this only " +"impacts the C++ API (the C API for those methods uses ``int`` and not " +"``GBool``)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:105 +msgid "" +"GIntBig/GInt64 was aliased to ``long long`` and GUIntBig/GUInt64 to " +"```unsigned long long``. While ``int64_t`` and ``long long`` have in " +"practice same width and signedness, they are formally different data " +"types. For scalar usage of those types, compilers shouldn't warn. But for" +" usage of those types as pointers, compilers warn in C (``-Wincompatible-" +"pointer-types`` with gcc) and error outs in C++ (unless ``-fpermissive`` " +"is passed), when mixing a ``int64_t`` pointer and a ``long long`` pointer" +" (similarly for their unsigned counterparts)." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:115 +msgid "C Raster API impacts (and equivalent C++ methods):" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:117 +msgid ":cpp:func:`GDALGetDefaultHistogramEx` (e.g. used by QGIS)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:118 +msgid ":cpp:func:`GDALSetDefaultHistogramEx`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:119 +msgid ":cpp:func:`GDALGetRasterHistogramEx` (e.g. used by QGIS)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:120 +msgid ":cpp:func:`GDALGetVirtualMemAuto`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:122 +msgid "C Vector API impacts (and equivalent C++ methods):" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:124 +msgid ":cpp:func:`OGR_F_GetFieldAsInteger64List`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:125 +msgid ":cpp:func:`OGR_F_SetFieldInteger64List`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:127 +msgid "C Multidimension API impacts (and equivalent C++ methods):" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:129 +msgid ":cpp:func:`GDALGroupCreateDimension`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:130 +msgid ":cpp:func:`GDALGroupCreateAttribute`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:131 +msgid ":cpp:func:`GDALMDArrayRead`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:132 +msgid ":cpp:func:`GDALMDArrayWrite`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:133 +msgid ":cpp:func:`GDALMDArrayAdviseRead`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:134 +msgid ":cpp:func:`GDALMDArrayAdviseReadEx`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:135 +msgid ":cpp:func:`GDALMDArrayCreateAttribute`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:136 +msgid ":cpp:func:`GDALMDArrayResize`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:137 +msgid ":cpp:func:`GDALMDArrayGetBlockSize`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:138 +msgid ":cpp:func:`GDALMDArrayGetStatistics`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:139 +msgid ":cpp:func:`GDALMDArrayComputeStatistics`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:140 +msgid ":cpp:func:`GDALMDArrayComputeStatisticsEx`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:141 +msgid ":cpp:func:`GDALAttributeGetDimensionsSize`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:143 +msgid "Out-of-tree drivers are also impacted:" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:145 +msgid "" +"the vector ones that implement :cpp:func:`OGRLayer::ISetFeature`, " +":cpp:func:`OGRLayer::SetNextByIndex`, " +":cpp:func:`OGRLayer::DeleteFeature`, " +":cpp:func:`OGRLayer::GetFeatureCount`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:149 +msgid "" +"the ones that implement the multidimensional API (no publicly ones known " +"by us)" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:152 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:287 +msgid "Risks" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:154 +msgid "" +"The changes of this RFC are somewhat risky, particularly the replacement " +"of the formatting macros CPL_FRMT_GIB/CPL_FRMT_GUIB with the " +"PRId64/PRIu64 ones, which requires to add a ``%`` formatting character. " +"While compilers caught most of the mismatches, there were remaining ones " +"undetected at compilation time. Manual corrections have been done to make" +" the regression test suite pass. Additional \"grep\"-based searches in " +"the code base have been done to find faulty patterns, but we cannot " +"exclude that some might have been missed." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:165 +msgid "MIGRATION_GUIDE.TXT will be updated to point to this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:170 +msgid "No changes in Python tests. Updates in the C++ test suite.`" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:175 +msgid "" +"https://github.com/OSGeo/gdal/issues/8288: Consider using standard C/C++ " +"integer types" +msgstr "" + +#: ../../source/development/rfc/rfc95_standard_int_types.rst:178 +msgid "https://github.com/OSGeo/gdal/pull/8396: candidate implementation" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:5 +msgid "RFC 96: Deferred C++ plugin loading" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:10 +msgid "2023-Nov-01" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:12 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:12 +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:11 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:12 +msgid "GDAL 3.9" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:18 +msgid "" +"This RFC adds a mechanism to defer the loading of C++ plugin drivers to " +"the point where their executable code is actually needed, and converts a " +"number of relevant drivers to use that mechanism. The aim is to allow for" +" more modular GDAL builds, while improving the performance of plugin " +"loading." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:23 +msgid "" +"It mostly targets in-tree plugin drivers, but it also provides a way for " +"out-of-tree plugin drivers to benefit from deferred loading capabilities," +" provided libgdal is built in a specific way" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:28 +msgid "Context and motivation" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:30 +msgid "There are currently two ways of loading a GDAL C++ driver:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:32 +msgid "" +"embedded in the core libgdal library. This is the default behavior for " +"drivers in the official GDAL source repository." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:35 +msgid "" +"available in a shared library (.so, .dll, .dylib) in a directory where it" +" is dynamically loaded when GDALAllRegister() is called. This is what " +"out-of-tree drivers use, or in-tree drivers if enabling the " +"[GDAL|OGR]_ENABLE_DRIVER_FOO_PLUGIN=ON or GDAL_ENABLE_PLUGINS=ON CMake " +"options (cf https://gdal.org/development/building_from_source.html#build-" +"drivers-as-plugins) to build them as plugins." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:42 +msgid "" +"For packagers/distributors, the second option is convenient for in-tree " +"drivers that depend on external libraries that are big and/or have a big " +"number of dependencies (libparquet, etc) and that would substantially " +"increase the size of the core libgdal library, or which have licenses " +"more restrictive than the MIT license used by libgdal." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:48 +msgid "" +"However, there is a penalty at GDALAllRegister() time. For example, on " +"Linux, it takes ~ 300 ms to complete for a build with 126 plugins, which " +"is a substantial time for short lived GDAL-based processes (for example a" +" script which would run gdalinfo or ogrinfo on many files). This time is " +"entirely spent in the dlopen() method of the operating system and there " +"is, to the best of our knowledge, nothing we can do to reduce it... " +"besides limiting the amount of dynamic loading (attempts have been made " +"to load plugins in parallel in multiple threads, but this does not " +"improve total loading time) For developers, that plugin loading phase is " +"actually considerably slower, of the order of ten seconds or more, when " +"debugging GDAL under GDB with many plugin drivers." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:60 +msgid "" +"Furthermore, loading drivers that are not needed also involves some " +"startup/teardown code of external libraries to be run, as well as more " +"virtual memory to be consumed. Hence this proposal of deferring the " +"actual loading of the shared library of the plugins until it is really " +"needed." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:66 +msgid "Design constraints" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:68 +msgid "We want the new mechanism to be opt-in and fully backwards compatible:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:70 +msgid "to still allow out-of-tree drivers." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:72 +msgid "" +"to still allow in-tree drivers, that are compatible of being built as " +"plugins, to be built in libgdal core, or as plugins depending on the " +"CMake variables." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:75 +msgid "to progressively convert existing in-tree drivers to use it." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:77 +msgid "" +"to provide the capability to out-of-tree drivers to optionally benefit " +"from the new capability, provided they build GDAL with the code needed to" +" declared a plugin proxy driver." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:84 +msgid "" +"The main idea if that drivers using the new capability will register a " +"proxy driver (of type GDALPluginDriverProxy, or extending it) with a new " +"GDALDriverManager::DeclareDeferredPluginDriver() method." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:134 +msgid "" +"The proxy driver uses the metadata items that have been set on it to " +"declare a minimum set of capabilities (GDAL_DCAP_RASTER, " +"GDAL_DCAP_MULTIDIM_RASTER, GDAL_DCAP_VECTOR, GDAL_DCAP_OPEN, etc.) to " +"which it can answer directly, and which are the ones used by GDALOpen() " +"to open a dataset. For other metadata items, it will fallback to loading " +"the actual driver and forward the requests to it." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:152 +msgid "" +"DeclareDeferredPluginDriver() method will also keep track of the plugin " +"filename to avoid automatically loading it in the " +"GDALDriverManager::AutoLoadDrivers() method (that method will only load " +"out-of-tree drivers or in-tree drivers that have not been converted to " +"use DeclareDeferredPluginDriver())." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:157 +msgid "" +"The main point is that drivers set the Identify() method on the proxy " +"driver. That Identify() method must be compiled in libgdal itself, and " +"thus be defined in a C++ file that does not depend on any external " +"library. Similarly for the GetSubdatasetInfoFunc() optional method." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:162 +msgid "" +"When loading the actual driver, the " +"GDALPluginDriverProxy::GetRealDriver() method will check that all " +"information set in its metadata is consistent with the actual metadata of" +" the underlying driver, and will warn when there are differences." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:167 +msgid "" +"GDALDataset::Open(), Create(), CreateCopy() methods are modified to not " +"use directly the pfnOpen, pfnCreate, pfnCreateCopy callbacks (that would " +"be the ones of the proxy driver, and thus nullptr), but to call new " +"GetOpenCallback()/ GetCreateCallback()/GetCreateCopyCallback() methods " +"that the GDALProxyDriver class overloads to return the function pointers " +"of the real driver, once it has loaded it." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:174 +msgid "" +"The DeclareDeferredPluginDriver() method checks if the file of the plugin" +" exists before registering it. If it is not available, a CPLDebug() " +"message is emitted. This allows to build a \"universal\" core libgdal, " +"with plugins that can be optionally available at runtime." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:179 +msgid "" +"Cherry-on-the-cake: GDALOpen() will given an explicit error message if it" +" identifies a dataset to a plugin that is not available at runtime. " +"Example::" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:188 +msgid "" +"For each driver supporting deferred plugin loading, GDALAllRegister() " +"must be modified to call a driver-specific function that calls " +"GDALDriverManager::DeclareDeferredPluginDriver() (see example in below " +"paragraph). This code path is enabled only when the driver is built as " +"plugin." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:196 +msgid "Example of changes to do on a simplified driver" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:198 +msgid "" +"In the :file:`CMakeLists.txt` file of a driver, the new option " +"CORE_SOURCES can be passed to ``add_gdal_driver()`` to define source " +"file(s) that must be built in libgdal, even when the driver is built as a" +" plugin." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:214 +msgid "A typical :file:`mydrivercore.h`` header will declare the identify method:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:227 +msgid "" +"And :file:`mydrivercore.cpp` will contain the implementation of the " +"identify method, a ``FOODriverSetCommonMetadata()`` method (with most of " +"the content of the normal driver registration method, except for function" +" pointers such as pfnOpen, pfnCreate, pfnCreateCopy or " +"pfnCreateMultiDimensional), as well as a ``DeclareDeferredXXXPlugin()`` " +"method that will be called by GDALAllRegister() when the driver is built " +"as a plugin (the PLUGIN_FILENAME macro is automatically set by the CMake " +"scripts with the filename of the plugin, e.g. \"gdal_FOO.so\"):" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:268 +msgid "" +"The GDALRegisterFoo() method itself, which is defined in the plugin code," +" calls ``FOODriverSetCommonMetadata``, and defines the pfnOpen, " +"pfnCreate, pfnCreateCopy, pfnCreateMultiDimensional callbacks when they " +"exist:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:290 +msgid "The modified :file:`gdalallregister.cpp` file will look like:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:321 +msgid "This can be done with the following CMake option:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:325 +msgid "" +"The pointed file must declare a ``void " +"DeclareDeferred<driver_name>(void)`` method with C linkage that takes " +"care of creating a GDALPluginDriverProxy instance and calling " +"GDALDriverManager::DeclareDeferredPluginDriver() on it." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:332 +msgid "" +"One could imagine a further enhancement for out-of-tree plugins where " +"they would be accompanied by a sidecar text file that would for example " +"declare the driver capabilities, as well as a limited implementation of " +"the identify method as a regular expression. But that is out-of-scope of " +"this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:338 +msgid "" +"Changes in the loading of OGR Python drivers (see :ref:`rfc-76`) are also" +" out-of-scope of this RFC (they will continue to be loaded at " +":cpp:func:`GDALAllRegister` time)." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:343 +msgid "Candidate implementation" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:345 +msgid "" +"A candidate implementation has been started to implement all the core " +"mechanism, and convert the Parquet, netCDF and HDF5 drivers. The HDF5 " +"plugin is actually a good stress test for the deferred loading mechanism," +" since it incorporates 4 drivers (HDF5, HDF5Image, BAG and S102) in the " +"same shared object. The plan is to update progressively all in-tree " +"drivers that depend on third-party libraries (that is the one that are " +"built as plugins when setting the GDAL_ENABLE_PLUGINS=YES CMake options)." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:353 +msgid "" +"Tests have also been done with QGIS (with the changes at " +"https://github.com/qgis/QGIS/pull/55115) to check that the declared set " +"of metadata items in GDALPluginDriverFeatures is sufficient to avoid " +"loading of the actual drivers at QGIS startup (they are only loaded when " +"a dataset of the format handled by the driver is identified)" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:362 +msgid "Expected to be backward compatible for most practical purposes." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:364 +msgid "" +"Drivers that would request a driver instance with GDALGetDriverByName() " +"may now get a GDALPluginDriverProxy instance instead of the \"real\" " +"driver instance. This is usually not an issue as few drivers subclass " +"GDALDriver, but that issue was hit on the PostGISRasterDriver that did " +"subclass it. The solution was to store the real PostGISRasterDriver " +"instance when it is built in a global variable, and use that global " +"variable instead of the one returned by GDALGetDriverByName()." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:371 +msgid "" +"Another potential issue is that if external code would directly use the " +"pfnOpen, pfnCreate, pfnCreateCopy, etc. function pointers of a GDALDriver" +" instance, it would see them null before the actual driver is loading, " +"but direct access to those function pointers has never been documented " +"(instead users should use GDALOpen(), GDALCreate(), GDALCreateCopy() " +"etc), and is not expected to be done by code external to libgdal core." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:378 +msgid "" +"However, the candidate implementation hits an issue with the way the GDAL" +" CondaForge builds work currently. At time of writing, the GDAL " +"CondaForge build recipee does:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:382 +msgid "" +"a regular GDAL build without Arrow/Parquet dependency (and thus without " +"the driver), whose libgdal.so goes in to the libgdal package." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:384 +msgid "installs libarrow and libparquet" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:385 +msgid "" +"does an incremental GDAL build with -DOGR_ENABLE_DRIVER_FOO_PLUGIN=ON to " +"generate ogr_Arrow.so and ogr_Parquet.so. However with the above new " +"mechanism, this will result in libgdal to be modified to have a " +"DeclareDeferredOGRParquetPlugin function, as well as including the " +"identification method of the Parquet plugin. But that modified libgdal.so" +" is discarded currently, and the ogr_Parquet.so plugin then depends on a " +"identify method that is not implemented." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:392 +msgid "" +"The initial idea was that the build recipee would have to be modified to " +"produce all artifacts (libgdal.so and libparquet.so) at a single time, " +"and dispatch them appropriately in libgdal and libgdal-arrow-parquet " +"packages, rather than doing two builds. However, CondaForge builds " +"support several libarrow versions, and produce thus different " +"Arrow/Parquet plugins, so this approach would not be practical." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:399 +msgid "" +"To solve this, the following idea has been implemented. Extract from the " +"updated :ref:`building_from_source` document::" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:481 +msgid "" +":ref:`raster_driver_tut` and :ref:`vector_driver_tut` will be updated to " +"point to this RFC. :ref:`building_from_source` will receive the new " +"paragraph mentioned above." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:488 +msgid "" +"A C++ test will be added testing that for one of the updated drivers, the" +" plugin is loaded in a deferred way in situations where this is expected," +" and is not loaded in other situations." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:495 +msgid "https://github.com/OSGeo/gdal/pull/8695: candidate implementation" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:498 +msgid "Adjustments done post GDAL 3.9.0, for GDAL 3.9.1" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:500 +msgid "" +"After GDAL 3.9.0 release, it has been noticed that the following setup " +"which used to work in prior releases no longer worked:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:503 +msgid "Step 1: building libgdal without support for driver X" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:504 +msgid "" +"Step 2: building driver X as a plugin, discarding the libgdal share " +"library," +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:505 +msgid "built at that stage" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:507 +msgid "" +"Step 3: using driver X built as a plugin against libgdal built at step 1." +" In that" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:507 +msgid "" +"scenario, driver X is expected to be loaded as if it was an out-of-tree " +"drivers." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:509 +msgid "" +"Such scenario is used when delivering a fully open-source libgdal without" +" any prior knowledge of which drivers could be later built as plugins, or" +" for which pre-configuring libgdal to support such drivers is not " +"practical because they rely on a proprietary SDK and the identification " +"method and/or driver metadata depends on the availability of the SDK " +"include files (e.g. MrSID)." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:515 +msgid "" +"Starting with GDAL 3.9.1, the ``add_gdal_driver()`` function in the " +"CMakeLists.txt of drivers which use the ``CORE_SOURCES`` keyword must " +"also declare the ``NO_SHARED_SYMBOL_WITH_CORE`` keyword, so that the " +"files pointed by CORE_SOURCES are built twice: once in libgdal with a " +"``GDAL_core_`` prefix, and another time in the plugin itself with a " +"``GDAL_driver_`` prefix, by using the PLUGIN_SYMBOL_NAME() macro of " +":file:`gdal_priv.h`." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:522 +msgid "Example in ogr/ogrsf_frmsts/oci/CMakeLists.txt:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:533 +msgid "Example in ogrocidrivercore.h:" +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:547 +msgid "" +"A consequence of that change is that drivers built as a plugin against " +"GDAL 3.9.0 will not be loadable by GDAL 3.9.1 (or later patch in the 3.9 " +"series), because they relied on driver-specific functions that are no " +"longer exported by libgdal >= 3.9.1." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:551 +msgid "" +"After that, things should work as they used to, and drivers built against" +" libgdal 3.9.1 should work against libgdal 3.9.2 for example." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:554 +msgid "" +"Also note that the above only affects *in-tree* plugin drivers. Out-of-" +"tree plugin drivers are not affected." +msgstr "" + +#: ../../source/development/rfc/rfc96_deferred_plugin_loading.rst:560 +msgid "+1 from PSC members KurtS, HowardB, JukkaR, JavierJS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:5 +msgid "RFC 97: OGRFeatureDefn, OGRFieldDefn and OGRGeomFieldDefn \"sealing\"" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:10 +msgid "2023-Nov-16" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:18 +msgid "" +"This RFC aims at avoiding common misuse of the setter methods of the " +"OGRFeatureDefn, OGRFieldDefn and OGRGeomFieldDefn classes. Indeed, the " +"setter methods of those classes should not be used directly by user code " +"(that is non driver implementations), on instances that are owned by a " +"OGRLayer. It is quite frequent for users (even seasoned ones) to neglect " +"that constraint. Hence this RFC introduces an optional \"sealing\" " +"capability that drivers can enable to avoid users modifying instances " +"that they should not." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:29 +msgid "" +"Let's take an example to clarify. We want to prevent a user from doing " +"the following:" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:36 +msgid "" +"The above code will not raise any warning or error at runtime, but will " +"not change the underlying on-disk dataset to reflect the new field name. " +"Indeed poLayer->GetLayerDefn() and its child objects should be considered" +" immutable, unless using dedicated methods of OGRLayer to modify them. " +"The correct way of renaming an existing field is (for drivers that " +"support such capability):" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:48 +msgid "" +"For other operations, such as calling " +":cpp:func:`OGRFieldDefn::AddFieldDefn()` or " +":cpp:func:`OGRFieldDefn::DeleteFieldDefn()` on an instance of " +"OGRLayer::GetLayerDefn(), crashes could potentially occur in drivers that" +" are not ready to see the number of fields to change behind their back. " +"The correct way of adding or deleting fields to a layer is to use " +":cpp:func:`OGRLayer::CreateField()` or " +":cpp:func:`OGRLayer::DeleteField()`" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:58 +msgid "" +"A ``bool m_bSealed`` member variable is added to the " +":cpp:class:`OGRFieldDefn` and :cpp:class:`OGRGeomFieldDefn` classes. Its " +"default value is false, meaning that calling setters method on instances " +"of those classes is allowed by default." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:63 +msgid "" +"The following methods are added on :cpp:class:`OGRFieldDefn` (and " +"similarly for :cpp:class:`OGRGeomFieldDefn`)" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:97 +msgid "" +"All setter methods of those classes are modified to check the value of " +"``m_bSealed``. If it is set, a CE_Failure CPLError() is emitted " +"indicating that the object is sealed. Unfortunately most setters return " +"``void``, so there is no way to advertise the error through an error " +"code. However, when using the Python bindings with exceptions enabled, a " +"Python exception will be thrown." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:103 +msgid "" +"A convenience method is also offered to use the Resource Acquisition Is " +"Initialization (RAII) paradygm to temporary unseal an instance, which is " +"an operation that drivers implementing AlterFieldDefn() / " +"AlterGeomFieldDefn() will need to do on fields they have priorly sealed." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:124 +msgid "Typical usage is by AlterFieldDefn() / AlterGeomFieldDefn() is:" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:138 +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:215 +msgid "" +"For punctual changes, a convenience ``whileUnsealing`` function is also " +"provided." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:141 +msgid "It can be used as in the following:" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:148 +msgid "" +"For OGRFeatureDefn, similar changes are done but with an extra subtelty. " +"For convenience of drivers, we want a driver to be able to call " +"GetTemporaryUnsealer() in a nested way, where only the first/most " +"external call does something, and next/nested ones are a no-operation. " +"This is similar to using a recursive mutex from the same thread. The user" +" can also indicate if it wishes fields and geometry fields owned by the " +"OGRFeatureDefn to be sealed/unsealed at the same time." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:218 +msgid "" +"In practice, the only Seal() invocation in driver core should be done on " +"the OGRFeatureDefn instance they return with GetLayerDefn(). All " +"subsequent sealing/unsealing operations should be done through " +"OGRFeatureDefn::GetTemporaryUnsealer()" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:224 +msgid "Example of a typical driver" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:226 +msgid "Constructor of the OGRLayer subclass:" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:240 +msgid "Simple CreateField() implementation:" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:253 +msgid "" +"Why not just having a ``const OGRFeatureDefn* OGRLayer::GetLayerDefn() " +"const`` method ?" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:256 +msgid "" +"That would only work when using the C++ API (and would require changes in" +" all drivers to modify the signature, as well as doing changes at places " +"where drivers require a non-const OGRFeatureDefn*), because const " +"correctness is not available in the C API and the SWIG bindings." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:264 +msgid "" +"No impact. Those C++ methods are intended to be used by driver " +"implementation only." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:270 +msgid "" +"For the initial implementation, the following drivers are updated to seal" +" their layer definition: GeoPackage, PostgreSQL, Shapefile, OpenFileGDB, " +"MITAB, Memory, GeoJSON, JSONFG, TopoJSON, ESRIJSON, ODS, XLSX." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:278 +msgid "" +"C API is unchanged. Backwards compatible addition to the C++ API (ABI " +"change)" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:280 +msgid "" +"There is the possibility to break user code that mis-used the API. For " +"example, this was the case of a few tests in the autotest suite that have" +" had to be modified." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:284 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:695 +msgid "MIGRATION_GUIDE.TXT will mention that and point to this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:289 +msgid "" +"Drivers that implement sealing should make sure they unseal at the " +"appropriate places: OGRLayer::Rename(), CreateField(), DeleteField(), " +"CreateGeomField(), DeleteGeomField(), ReorderFields(), AlterFieldDefn() " +"AlterGeomFieldDefn() and any other places where they might modify " +"objects. Failure to do so will result in failures, and potentially " +"crashes. Hence implementation of sealing should only be done on drivers " +"that have sufficient test coverage." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:300 +msgid "" +"The documentation of the setters as well as the introduction text of " +"OGRFeatureDefn, OGRFieldDefn and OGRGeomFieldDefn is modified to reflect " +"that setters of those classes should not be called on instances returned " +"by OGRLayer::GetLayerDefn()." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:308 +msgid "The autotest suite is modified to comply with sealing" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:309 +msgid "" +"Calls to setters on sealed instances will be done to test that an error " +"is triggered." +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:315 +msgid "Candidate implementation in https://github.com/OSGeo/gdal/pull/8733" +msgstr "" + +#: ../../source/development/rfc/rfc97_feature_and_fielddefn_sealing.rst:320 +msgid "+1 from PSC members JukkaR, JavierJS and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:5 +msgid "RFC 98: Build requirements for GDAL 3.9" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:9 +msgid "2023-Nov-23" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:17 +msgid "" +"The document updates :ref:`rfc-68` with the new build requirements for " +"GDAL 3.9:" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:19 +msgid "C++ >= 17" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:20 +msgid "CMake >= 3.16" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:21 +msgid "PROJ >= 6.3.1." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:23 +msgid "" +"The minimum version for the following optional dependencies is also " +"updated:" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:26 +msgid "GEOS >= 3.8" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:27 +msgid "Poppler >= 0.86" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:28 +msgid "libtiff >= 4.1" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:29 +msgid "libcurl >= 7.68" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:30 +msgid "libpng >= 1.6.0" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:31 +msgid "libsqlite3 >= 3.31" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:32 +msgid "libopenjp2 >= 2.3.1" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:33 +msgid "libnetcdf >= 4.7 and built with NC4 enabled" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:34 +msgid "libhdf5 >= 1.10" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:39 +msgid "" +"Our past build requirements were C++11, CMake 3.9, and PROJ 6.0.0. All of" +" them correspond to now outdated versions of those components, and it " +"makes sense to update to more up-to-date versions to be able to clean up " +"code, leverage new capabilities and be consistent with the current state " +"of our software environment." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:44 +msgid "" +"The proposed updates are all compatible with versions of those components" +" available by default in the old LTS (Long Term Support) Ubuntu 20.04, " +"which corresponds to the oldest environment used by our continuous " +"integration:" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:48 +msgid "" +"C++17 is the minimum version required by the latest versions of some of " +"our C++ dependencies, including Poppler, PDFium, PoDoFo, TileDB, " +"libarrow-cpp. Ubuntu 20.04 includes GCC 9.4, which supports C++17. While " +"we want to allow C++17 features to build GDAL, for now, we will stick to " +"exposing at most C++11 features in the exported headers of the library to" +" minimize disruption for GDAL C++ users. That might be revisited later. " +"At the time of writing, the C++17 requirement has already been " +"implemented in master / 3.9.0dev." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:57 +msgid "" +"CMake 3.16.0 was released in November 2019. Updating to CMake 3.16 " +"enables us to make a number of cleanups in GDAL CMakeLists.txt scripts, " +"and in particular to make it possible to use the " +"[CMAKE_UNITY_BUILD](https://cmake.org/cmake/help/latest/variable/CMAKE_UNITY_BUILD.html)" +" feature. Ubuntu 20.04 includes CMake 3.16.4." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:63 +msgid "" +"PROJ 6.3.1 was released in February 2020. Updating to that version " +"implies PROJ >= 6.2 and the availability of PROJJSON output, and PROJ >= " +"6.3 enables us to remove a few specific code paths in ogrct.cpp. Ubuntu " +"20.04 includes PROJ 6.3.1. Earlier PROJ 6.x versions had a number of " +"annoying issues." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:68 +msgid "" +"By the time GDAL 3.9 is released (May 2024), all the above requirements " +"correspond to versions of the tools/libraries that have been released " +"more than 4 years earlier." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:72 +msgid "" +"More generally, we also update requirements for optional dependencies to " +"be consistent with the versions available in Ubuntu 20.04, to eliminate " +"code paths that are no longer exercised by our continuous integration:" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:76 +msgid "" +"Python >= 3.8: Python 3.7 is already end-of-life " +"(https://devguide.python.org/versions/) Python 3.8 is the minimum version" +" used by our CI" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:78 +msgid "" +"GEOS >= 3.8: ensures that MakeValid() is available when GEOS is " +"available, which simplifies the code base and test suite" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:80 +msgid "Poppler >= 0.86: removes a lot of #ifdef trickery in the PDF driver" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:81 +msgid "libtiff >= 4.1: simplifies a few code paths in the GeoTIFF driver" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:82 +msgid "libcurl >= 7.68: removes outdated code paths in CPL networking code" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:83 +msgid "libpng >= 1.6.0: removes outdated code paths in the PNG driver" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:84 +msgid "" +"libsqlite3 >= 3.31: removes outdated code paths in the SQLite and GPKG " +"drivers" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:85 +msgid "libopenjp2 >= 2.3.1: removes outdated code paths in the OpenJPEG driver" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:86 +msgid "" +"libnetcdf >= 4.7 built with NC4 support enabled (i.e. libnetcdf built " +"against libhdf5): removes #ifdef code paths in netCDF driver. The netCDF " +"multidimensional code already requires NC4." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:89 +msgid "libhdf5 >= 1.10: removes outdated code paths in the HDF5 driver" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:92 +msgid "C++17 capable compilers" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:94 +msgid "" +"From https://en.wikipedia.org/wiki/C%2B%2B17, compilers supporting C++17 " +"are:" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:96 +msgid "GCC >= 8" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:97 +msgid "clang >= 5" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:98 +msgid "Visual Studio >= 2017 15.8 (MSVC 19.15)" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:101 +msgid "C++14 and C++17 features" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:103 +msgid "Features that can be used in the code base (not an exhaustive list):" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:105 +msgid "Use of ``std::make_unique<>`` instead of ``cpl::make_unique<>``" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:106 +msgid "Use of ``[[fallthrough]]`` instead of ``CPL_FALLTHROUGH``" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:107 +msgid "Use of ``[[maybe_unused]]`` instead of ``CPL_UNUSED``" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:108 +msgid "" +"Nicer iteration in ``std::map`` with ``for (const auto &[key, value]: " +"my_map )`` (more generally \"structured binding declarations\")" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:111 +msgid "Banned features:" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:113 +msgid "" +"Use of ``std::filesystem`` (https://en.cppreference.com/w/cpp/filesystem)" +" is not appropriate since our existing :cpp:class:`VSIFilesystemHandler` " +"mechanism has broader support for all our /vsi specific file systems." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:118 +msgid "Changes in continuous integration" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:120 +msgid "" +"Continuous integration is modified to test configurations that have at " +"least the new set of build requirements." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:131 +msgid "No change in API and ABI" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:136 +msgid "The Build requirements documentation page will be updated." +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:144 +msgid "Related tickets / pull requests" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:146 +msgid "" +"https://github.com/OSGeo/gdal/pull/8680: CI: Remove Ubuntu 18.04 " +"configurations" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:147 +msgid "https://github.com/OSGeo/gdal/issues/8270: Bump to C++17" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:148 +msgid "" +"https://github.com/OSGeo/gdal/pull/8687: Switch default C++ standard to " +"C++17" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:149 +msgid "https://github.com/OSGeo/gdal/pull/8710: Cxx17 tunings" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:150 +msgid "" +"https://github.com/OSGeo/gdal/pull/8716: C++17: use if constexpr() " +"construct" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:151 +msgid "" +"https://github.com/OSGeo/gdal/pull/8723: C++17: replace CPL_FALLTHROUGH " +"by standard [[fallthrough]];" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:152 +msgid "" +"https://github.com/OSGeo/gdal/pull/8725: C++17: use structured bindings " +"declaration and class template argument deduction for std::pair()" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:153 +msgid "" +"https://github.com/OSGeo/gdal/issues/8751: Bumping minimum CMake version " +"to 3.16" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:154 +msgid "" +"https://github.com/OSGeo/gdal/issues/8796: Add CI test we can use GDAL " +"public/installed headers with C++11" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:155 +msgid "" +"https://github.com/OSGeo/gdal/pull/8804: Make build compatible of " +"-DCMAKE_UNITY_BUILD=ON for faster builds" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:160 +msgid "This RFC supersedes :ref:`rfc-68`" +msgstr "" + +#: ../../source/development/rfc/rfc98_build_requirements_gdal_3_9.rst:165 +msgid "+1 from PSC members JavierJS, KurstS, HowardB, JukkaR and EvenR" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:5 +msgid "RFC 99: Geometry coordinate precision" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:10 +msgid "2024-Feb-24" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:11 +msgid "Adopted, implemented in GDAL 3.9" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:18 +msgid "" +"This RFC aims at introducing optional metadata to specify the coordinate " +"precision of geometries, to be able to round appropriately coordinates " +"and limit the number of decimals when exporting to text-based formats or " +"nullify least-significant bits for binary formats. That metadata will be " +"stored into and read from formats that can support it." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:27 +msgid "The aim is multiple:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:29 +msgid "" +"reducing file size. For text-based formats, rounding and truncating to " +"the specified precision directly reduce file size. For binary formats, " +"using that information to zero least-significant bits can increase the " +"potential when applying afterwards lossless compression methods " +"(typically zipping a file)." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:34 +msgid "" +"presenting the user with hints on the precision of the data he/she " +"accesses. This can be used by user interfaces build on top of GDAL to " +"display geometry coordinates with an appropriate number of decimals." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:38 +msgid "" +"a few drivers (GeoJSON, JSONFG, OpenFileGDB) have layer creation options " +"to specify coordinate precision, but there is currently no driver " +"agnostic way of specifying it." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:42 +msgid "" +"For example, currently, when exporting a file to GML, 15 significant " +"decimal digits (ie the total of digits for the integral and decimal " +"parts) are used, which corresponds to a 0.1 micrometer precision for " +"geography coordinates. The same holds for regular GeoJSON export, unless " +"the RFC 7946 variant is selected, in which case only 7 decimal digits " +"after decimal separators are used. However this is a layer creation " +"option, which means that it is no longer remembered when data is " +"edited/appended to an existing layer (see " +"https://github.com/qgis/QGIS/issues/56335)." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:51 +#, python-format +msgid "" +"For binary formats using IEEE-754 double-precision encoding of real " +"numbers, one can show that at least the last 16 least-significants bits " +"(ie the last 2 bytes of 8) of a coordinate can be set to zero while " +"keeping a 1 mm precision (which corresponds to about 8.9e-9 degree). On a" +" test dataset, setting a 1 mm precision reduced the size of the .zip of " +"the .gpkg file from 766 MB to 667 MB (13% size decrease). If only a 1 " +"meter precision is wished, this increases to 26 useless least-significant" +" bits." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:76 +msgid "C and C++ API extensions and changes" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:79 +msgid "OGRGeomCoordinatePrecision class" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:81 +msgid "" +"A new ``OGRGeomCoordinatePrecision`` class is introduced in the " +"``ogr_geomcoordinateprecision.h`` file:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:170 +msgid "Corresponding additions at the C API level:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:208 +msgid "" +"The existing :cpp:class:`OGRGeomFieldDefn` is extended with a new " +"OGRGeomCoordinatePrecision member, and associated getter and setter " +"methods." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:224 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:261 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:358 +msgid "New corresponding C API:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:234 +msgid "OGRGeometry class" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:236 +msgid "" +"The existing :cpp:class:`OGRGeometry` is extended with the following new " +"``SetPrecision`` method which is a wrapper of the " +"``GEOSGeom_setPrecision_r`` function:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:276 +msgid "" +"Note that this method is not automatically run by the writing side of " +"drivers, which assume that the passed geometries are valid once rounded " +"with the specified coordinate precision metadata." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:280 +msgid "However it is invoked when the `-xyRes` switch of ogr2ogr is passed." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:282 +msgid "" +"It may also be triggered by setting the new " +"``OGR_APPLY_GEOM_SET_PRECISION`` configuration option to ``YES``, for " +"geometries passed to :cpp:func:`OGRLayer::CreateFeature` and " +":cpp:func:`OGRLayer::SetFeature` before they are passed to the driver." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:288 +msgid "A closely related ``roundCoordinates`` method is also introduced:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:310 +msgid "WKB export" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:312 +msgid "" +"WKB export methods will be modified in a similar way as in the prototype " +"https://github.com/OSGeo/gdal/pull/6974 to nullify least significant bits" +" from the precision specifications." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:316 +msgid "More specifically the following 2 new classes are added:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:346 +msgid "" +"And the C++ OGRGeometry ``exportToWkb`` virtual method is modified to " +"have the following prototype:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:355 +msgid "" +"The existing method with signature ``OGRErr exportToWkb(OGRwkbByteOrder, " +"unsigned char *, OGRwkbVariant = wkbVariantOldOgc) const`` is kept and " +"call the new virtual method." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:378 +msgid "OGRLayer CreateLayer()/ICreateLayer() changes" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:380 +msgid "" +"The signature of the current :cpp:func:`OGRLayer::ICreateLayer()` " +"protected method (implemented by drivers) will be changed from" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:389 +msgid "to" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:398 +msgid "This will require changes to out-of-tree drivers that implement it." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:400 +msgid "A corresponding non-virtual public method will also be added:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:409 +msgid "" +"And the current CreateLayer() signature will be adapted to call the " +"modified ICreateLayer()." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:412 +msgid "And for the C API:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:422 +msgid "" +"A new ``GDAL_DCAP_HONOR_GEOM_COORDINATE_PRECISION`` driver capability " +"will be added to advertise that a driver honours " +"OGRGeomFieldDefn::GetCoordinatePrecision() when writing geometries. This " +"may be useul for user interfaces that could offer an option to the user " +"to specify the coordinate precision. Note however that the driver may not" +" be able to store that precision in the dataset metadata." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:428 +msgid "" +"There will be *no* provision to modify the coordinate precision of an " +"existing layer geometry field with :cpp:func:`OGRLayer::AlterFieldDefn`." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:434 +msgid "" +"The following drivers will be modified to honour " +"``GDAL_DCAP_HONOR_GEOM_COORDINATE_PRECISION``" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:439 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:452 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:482 +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:506 +msgid "" +"The driver will compute the number of decimal digits after the decimal " +"point to write as ``ceil(1. / log10(resolution))``" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:442 +msgid "" +"The driver will be able to store and retrieve the coordinate precision " +"metadata in the files it generates, by adding " +"``xy_coordinate_resolution`` and ``z_coordinate_resolution`` members at " +"the FeatureCollection level." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:446 +msgid "" +"The existing COORDINATE_PRECISION layer creation option, if specified, " +"will take precedence over the settings coming from " +"OGRGeomFieldDefn::GetCoordinatePrecision()." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:450 +msgid "GeoJSONSeq" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:455 +msgid "It will *not* be able to store it in its metadata." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:458 +msgid "JSONFG" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:460 +msgid "" +"Similar to GeoJSON. One subtelty is that this driver may write both the " +"\"place\" geometry (generally in a non-WGS84 CRS) and the GeoJSON RFC7946" +" WGS84 \"geometry\"." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:463 +msgid "" +"The OGRGeomFieldDefn::GetCoordinatePrecision() will qualify the \"place\"" +" geometry. The coordinate precision of the WGS84 \"geometry\" will be " +"derived from the one of the \"place\" geometry with appropriate " +"geographic/projected CRS and axis unit changes." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:468 +msgid "" +"The coordinate precision metadata of the \"place\" member will be stored " +"in ``xy_coordinate_resolution_place`` and " +"``z_coordinate_resolution_place`` members at the FeatureCollection level." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:472 +msgid "" +"For the \"geometry\" member, the same ``xy_coordinate_resolution`` and " +"``z_coordinate_resolution`` members as the GeoJSON driver will be used." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:475 +msgid "" +"The existing COORDINATE_PRECISION_PLACE or COORDINATE_PRECISION_GEOMETRY " +"layer creation option, if specified, will take precedence over the " +"settings coming from OGRGeomFieldDefn::GetCoordinatePrecision()." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:485 +msgid "" +"The driver will be able to store the coordinate precision metadata in the" +" XML schema it generates by adding a ``xs:annotation/xs:appinfo`` element" +" in the declaration of the geometry property, and with " +"``ogr:xy_coordinate_resolution`` and ``ogr:z_coordinate_resolution`` sub-" +"elements. This should hopefully be ignored by readers that don't " +"recognize that metadata (this will be the case of GDAL < 3.9)" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:509 +msgid "" +"It will *not* be able to store it in its metadata. The possibility of " +"storing the coordinate metadata in the .csvt side-car file has been " +"considered, but it would not be backwards-compatible." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:516 +msgid "" +"The GeoPackage driver will support reading and writing the geometry " +"coordinate precision. By default, the geometry coordinate precision will " +"only noted in metadata, and does not cause geometries that are written to" +" be modified to comply with this precision." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:521 +msgid "Several settings may be combined to apply further processing:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:523 +msgid "" +"the ``OGR_APPLY_GEOM_SET_PRECISION`` configuration option as described " +"previously." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:526 +msgid "" +"if the new ``DISCARD_COORD_LSB`` layer creation option is set to YES, the" +" less-significant bits of the WKB geometry encoding which are not " +"relevant for the requested precision are set to zero. This can improve " +"further lossless compression stages, for example when putting a " +"GeoPackage in an archive. Note however that when reading back such " +"geometries and displaying them to the maximum precision, they will not " +"\"exactly\" match the original OGRGeomCoordinatePrecision settings. " +"However, they will round back to it. The value of the " +"``DISCARD_COORD_LSB`` layer creation option is written in the dataset " +"metadata, and will be re-used for later edition sessions." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:537 +msgid "" +"if the new ``UNDO_DISCARD_COORD_LSB_ON_READING`` layer creation option is" +" set to YES (only makes sense if the ``DISCARD_COORD_LSB`` layer creation" +" option is also set to YES), when *reading* back geometries from a " +"dataset, the ``OGRGeometry::roundCoordinates`` method will be applied so " +"that the geometry coordinates exactly match the original specified " +"coordinate precision. That option will only be honored by GDAL 3.9 or " +"later." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:545 +msgid "" +"Implementation details: the coordinate precision is stored in a record in" +" each of the ``gpkg_metadata`` and ``gpkg_metadata_reference`` table, " +"with the following additional constraints on top of the ones imposed by " +"the GeoPackage specification:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:550 +msgid "gpkg_metadata.md_standard_uri = 'http://gdal.org'" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:551 +msgid "gpkg_metadata.mime_type = 'text/xml'" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:552 +msgid "" +"gpkg_metadata.metadata = '<CoordinatePrecision " +"xy_resolution=\"{xy_resolution}\" z_resolution=\"{z_resolution}\" " +"m_resolution=\"{m_resolution}\" discard_coord_lsb={true or false} " +"undo_discard_coord_lsb_on_reading={true or false} />'" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:553 +msgid "gpkg_metadata_reference.reference_scope = 'column'" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:554 +msgid "gpkg_metadata_reference.table_name = '{table_name}'" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:555 +msgid "gpkg_metadata_reference.column_name = '{geometry_column_name}'" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:557 +msgid "" +"Note that the xy_resolution, z_resolution or m_resolution attributes of " +"the XML CoordinatePrecision element are optional. Their numeric value is " +"expressed in the units of the SRS for xy_resolution and z_resolution." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:568 +msgid "OpenFileGDB" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:570 +msgid "" +"OGRGeomCoordinatePrecision::dfXYResolution (resp. dfZResolution, " +"dfMResolution) directly map to 1. / xyscale (resp. 1 / zscale, 1 / " +"mscale) in the declaration of the coordinate grid precision options of " +"the FileGeodatabase format (cf " +"https://help.arcgis.com/en/sdk/10.0/java_ao_adf/conceptualhelp/engine/index.html#//00010000037m000000)." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:575 +msgid "" +"Consequently the OpenFileGDB driver can be modified in reading and " +"writing to fully honour OGRGeomCoordinatePrecision." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:578 +msgid "" +"The driver will also get and set other coordinate grid precision options," +" such as the origin and tolerance, values in the ``FileGeodatabase`` key " +"of the ``OGRGeomCoordinatePrecision::oFormatSpecificOptions`` member." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:582 +msgid "" +"The existing ``XYSCALE``, ``ZSCALE`` and ``MSCALE`` layer creation " +"options, if specified, will take precedence over the settings coming from" +" OGRGeomFieldDefn::GetCoordinatePrecision()." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:589 +msgid "Modified to have exactly the same behavior as OpenFileGDB." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:592 +msgid "OGR VRT" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:594 +msgid "" +"The driver will read the geometry coordinate precision from the source " +"geometry field, or possibly overridden with the following elements in the" +" XML VRT:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:611 +msgid "" +"ogrinfo will be modified to honour OGRGeomCoordinatePrecision when " +"outputting WKT geometries (or GeoJSON geometries for the -json output)" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:617 +msgid "" +"ogr2ogr will forward by default the OGRGeomCoordinatePrecision of the " +"input layer to the output layer, but of course it will only have effects " +"for drivers honouring ``GDAL_DCAP_HONOR_GEOM_COORDINATE_PRECISION``." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:621 +msgid "" +"When reprojection occurs, the coordinate precision will be adjusted to " +"take into account geographic vs projected CRS changes and unit changes." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:624 +msgid "The following options will be added:" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:626 +msgid "" +"``-xyRes <val>``: XY coordinate resolution. Nominally in the unit of the " +"X and Y SRS axis. Appending a ``m``, ``mm`` or ``deg`` suffix will be " +"also supported. A warning will be emitted if the user specifies this " +"option when creating a new layer for a driver that does not advertise " +"``GDAL_DCAP_HONOR_GEOM_COORDINATE_PRECISION``." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:633 +msgid "" +"``-zRes <val>``: Z coordinate resolution. Nominally in the unit of the Z " +"SRS axis. Appending a ``m`` or ``mm`` suffix will be also supported." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:636 +msgid "``-mRes <val>``: M coordinate resolution." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:638 +msgid "" +"``-unsetCoordPrecision``: to disable automatic propagation of the input " +"coordinate precision to the output." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:644 +msgid "" +"While there is an obvious logical connection with GEOS' PrecisionModel " +"(https://libgeos.org/doxygen/classgeos_1_1geom_1_1PrecisionModel.html), " +"this RFC does not tie the introduced OGR coordinate precision metadata " +"with it. Tying both would require either adding a reference to a " +"OGRGeomCoordinatePrecision as a member of the OGRGeometry class (which " +"would have some extra RAM usage implications), or as a parameter in " +"OGRGeometry GEOS related methods." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:652 +msgid "" +"Quantization of raster pixel values (e.g. the ``DISCARD_LSB`` creation " +"option of the GeoTIFF driver) is also slightly connected." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:658 +msgid "The new C functions are bound to SWIG." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:685 +msgid "Tests will be added for the new API and the modified drivers." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:690 +msgid "The C and C++ API are extended." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:692 +msgid "" +"The change of the ICreateLayer() virtual method is an ABI change, and " +"will require source code changes to out-of-tree drivers implementing it." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:698 +msgid "Design discussion" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:700 +msgid "" +"This paragraph discusses a number of thoughts that arose during the " +"writing of this RFC but were not kept." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:703 +msgid "" +"While changing ICreateLayer() prototype, which requires the tedious " +"process of changing it in more than 50 drivers, I've also considered " +"introducing an additional OGRLayerCreationContext argument, but I've " +"decided against if, as it is unclear if it would be that useful. For " +"example, in most ogr2ogr scenarios, the final extent and feature count is" +" unknown at the start of the process." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:727 +msgid "Candidate implementation: https://github.com/OSGeo/gdal/pull/9378" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:729 +msgid "" +"A prior implementation with a different and reduced scope was done last " +"year in https://github.com/OSGeo/gdal/pull/6974. The GeoPackage driver " +"specific creation options of this pull request will no longer be needed " +"in the implementation of this RFC." +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:734 +msgid "" +"Related QGIS issue about coordinate precision not being preserved when " +"appending to GeoJSON: https://github.com/qgis/QGIS/issues/56335" +msgstr "" + +#: ../../source/development/rfc/rfc99_geometry_coordinate_precision.rst:740 +msgid "+1 from PSC members EvenR and HowardB. +0 from KurtS" +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:5 +msgid "RFC 9: GDAL Paid Maintainer Guidelines" +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:11 +msgid "Status: Approved, but superseded per :ref:`rfc-83`" +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:16 +msgid "" +"To formalize guidelines for the work of maintainers paid out of GDAL " +"project sponsorship funds." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:20 +msgid "Responsibilities" +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:22 +msgid "Analyse and where possible fix bugs reported against GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:23 +msgid "Run, review and extend the test suite (via buildbot, etc)." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:24 +msgid "Maintain and extend documentation." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:25 +msgid "Assist integrating new contributed features." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:26 +msgid "" +"Help maintain project infrastructure (mailing lists, buildbot, source " +"control, etc)" +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:28 +msgid "Provide user support on the project mailing lists, and in other venues." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:30 +msgid "Develop new capabilities." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:32 +msgid "" +"Bug fixing and maintenance should be focused on GDAL/OGR, but as needed " +"will extend into sub-projects such as libtiff, libgeotiff, Shapelib and " +"MITAB as long it is to serve a need of the GDAL/OGR project." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:36 +msgid "" +"In order to provide reasonable response times the maintainer is expected " +"spend some time each week addressing new bugs and user support. If the " +"maintainer will be unavailable for an extended period of time (vacation, " +"etc) then the supervisor should be notified." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:44 +msgid "" +"The maintainer is generally subject to the project PSC. However, for day " +"to day decisions one PSC member will be designated as the supervisor for " +"the maintainer. This supervisor will prioritize work via email, bug " +"assignments, and IRC discussions." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:49 +msgid "" +"The supervisor will try to keep the following in mind when prioritizing " +"tasks." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:52 +msgid "" +"Bug reports, and support needs of Sponsors should be given higher " +"priority than other tasks." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:54 +msgid "" +"Areas of focus identified by the PSC (ie. multi-threading, SWIG " +"scripting) should be given higher priority than other tasks." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:57 +msgid "" +"The maintainer should be used to take care of work that no one else is " +"willing and able to do (ie. fill the holes, rather than displacing " +"volunteers)" +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:60 +msgid "" +"Try to avoid tying up the maintainer on one big task for many weeks " +"unless directed by the PSC." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:62 +msgid "" +"The maintainer should not be directed to do work for which someone else " +"is getting paid." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:65 +msgid "" +"Substantial new development projects will only be taken on by the " +"maintainer with the direction of a PSC motion (or possibly an RFC " +"designating the maintainer to work on a change)." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:69 +msgid "" +"Note that the maintainer and the maintainer supervisor are subject to the" +" normal RFC process for any substantial change to GDAL." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:75 +msgid "" +"The maintainer will produce a brief bi-weekly report to the gdal-dev list" +" indicating tasks worked on, and a more detailed timesheet for the " +"supervisor." +msgstr "" + +#: ../../source/development/rfc/rfc9_maintainer.rst:79 +msgid "" +"This is intended to provide visibility into status, accomplishments, and " +"time allocation. It also gives an opportunity for the PSC to request a " +"\"course correction\" fairly promptly." +msgstr "" + +#: ../../source/development/testing.rst:5 +msgid "Automated testing" +msgstr "" + +#: ../../source/development/testing.rst:7 +msgid "" +"GDAL includes a comprehensive test suite, implemented using a combination" +" of Python (via pytest) and C++ (via gtest)." +msgstr "" + +#: ../../source/development/testing.rst:9 +msgid "" +"After building GDAL using CMake, the complete test suite can be run using" +" ``ctest -v --output-on-failure``. This will automatically set " +"environment variables so that tests are run on the the built version of " +"GDAL, rather than an installed system copy." +msgstr "" + +#: ../../source/development/testing.rst:13 +msgid "Running a subset of tests using ``ctest``" +msgstr "" + +#: ../../source/development/testing.rst:15 +msgid "" +"The complete set of test suites known to ``ctest`` can be viewed running " +"``ctest -N``." +msgstr "" + +#: ../../source/development/testing.rst:17 +msgid "" +"A subset of tests can be run using the ``-R`` argument to ``ctest``, " +"which selects tests using a provided regular expression. For example, " +"``ctest -R autotest`` would run the Python-based tests." +msgstr "" + +#: ../../source/development/testing.rst:20 +msgid "" +"The ``-E`` argument can be used to exclude tests using a regular " +"expression. For example, ``ctest -E gdrivers`` would exclude the suite of" +" driver tests." +msgstr "" + +#: ../../source/development/testing.rst:23 +msgid "Running a subset of tests using ``pytest``" +msgstr "" + +#: ../../source/development/testing.rst:25 +msgid "" +"The test subsets exposed by ``ctest`` are still rather large and some may" +" take several minutes to run. If a higher level of specificity is needed," +" ``pytest`` can be called directly to run groups of tests or individual " +"tests. Before running ``pytest``, it is important to set " +":ref:`development environment variables " +"<setting_dev_environment_variables>` so that the development build of " +"GDAL is tested, rather than a system version." +msgstr "" + +#: ../../source/development/testing.rst:29 +msgid "" +"Tests can then be run by calling ``pytest``, for example on an individual" +" file. On Linux and MacOS builds, the tests are symlinked into the build " +"directory, so this can be done by running the following from the build " +"directory:" +msgstr "" + +#: ../../source/development/testing.rst:37 +msgid "" +"On Windows, the test files remain in the source tree, but the pytest " +"configuration file ``pytest.ini`` is only available in the build " +"directory. To accommodate this, the above command would be modified as " +"follows:" +msgstr "" + +#: ../../source/development/testing.rst:43 +msgid "" +"A subset of tests within an individual test file can be run by providing " +"a regular expression to the ``-k`` argument to ``pytest``." +msgstr "" + +#: ../../source/development/testing.rst:49 +msgid "" +"``pytest`` can also report information on the tests without running them." +" For example, to list tests containing \"tiff\" in the name:" +msgstr "" + +#: ../../source/development/testing.rst:57 +msgid "" +"Not all Python tests can be run independently; some tests depend on state" +" set by a previous tests in the same file." +msgstr "" + +#: ../../source/development/testing.rst:61 +msgid "Checking for memory leaks and access errors using Valgrind" +msgstr "" + +#: ../../source/development/testing.rst:63 +msgid "" +"The GDAL unit test suite can be run using the Valgrind tool to detect " +"memory errors such as leaks and incorrect reads/writes." +msgstr "" + +#: ../../source/development/testing.rst:66 +msgid "" +"The test suite will run considerably slower under Valgrind (perhaps by a " +"factor of ten) so it is generally advisable to run a subset of the tests " +"using the methods described above." +msgstr "" + +#: ../../source/development/testing.rst:70 +msgid "" +"Calling ``valgrind ctest`` will _not_ run the tests under ``valgrind``. " +"Although it is possible to use Valgrind with ctest, it is simpler to call" +" ``pytest`` or ``gdal_unit_test`` directly." +msgstr "" + +#: ../../source/development/testing.rst:74 +msgid "" +"The following preparatory steps are necessary to avoid numerous false-" +"positive errors from Valgrind:" +msgstr "" + +#: ../../source/development/testing.rst:77 +msgid "" +"Many false-positive errors are generated by Python itself. Most of these " +"can be removed by obtaining a suppression file that corresponds to the " +"version of the Python interpreter used to run the tests. This file can be" +" located in a source distribution of Python, or downloaded directly from " +"GitHub (for example, at " +"https://raw.githubusercontent.com/python/cpython/3.11/Misc/valgrind-" +"python.supp)" +msgstr "" + +#: ../../source/development/testing.rst:84 +msgid "" +"A few false-positive errors are generated by the GDAL test suite or " +"libraries that it uses (e.g., SWIG, numpy). These can be removed by " +"``autotest/valgrind-gdal.supp`` file in the GDAL repository." +msgstr "" + +#: ../../source/development/testing.rst:88 +msgid "" +"When running Python unit tests, the default system memory allocator " +"should be used instead of Python's internal memory allocator. This can be" +" done by setting the ``PYTHONMALLOC`` environment variable to ``malloc``." +msgstr "" + +#: ../../source/development/testing.rst:92 +msgid "" +"When running Python unit tests, Valgrind will report numerous \"Invalid " +"file descriptor\" warnings that cannot currently be suppressed. These can" +" be removed from the output using ``grep -v \"invalid file " +"descriptor\\|alternative log fd\"``." +msgstr "" + +#: ../../source/development/testing.rst:97 +msgid "" +"Combining the following, we can run valgrind for a subset of Python tests" +" as follows:" +msgstr "" + +#: ../../source/development/testing.rst:108 +msgid "" +"To avoid verbose commands such as the one above, it may be useful to " +"reference the suppression files and other common arguments in a " +"``~/.valgrindrc`` file." +msgstr "" + +#: ../../source/development/testing.rst:116 +msgid "Recommendations on how to write new tests" +msgstr "" + +#: ../../source/development/testing.rst:118 +msgid "" +"Python-based tests should be preferred when possible, as productivity is " +"higher in Python and there is no associated compilation time (compilation" +" time affects feedback received from continuous integration)." +msgstr "" + +#: ../../source/development/testing.rst:122 +msgid "" +"C/C++-based test should be reserved for C++-specific aspects that cannot " +"be tested with the SWIG Python bindings, which use the C interface. For " +"example testing of C++ operators (copy/move constructors/assignment " +"operators, iterator interfaces, etc.) or C/C++ functionality not mapped " +"to SWIG (e.g. CPL utility functions/classes)" +msgstr "" + +#: ../../source/development/testing.rst:128 +msgid "Python tests" +msgstr "" + +#: ../../source/development/testing.rst:130 +msgid "" +"Python tests use the `pytest <https://docs.pytest.org/en/latest/>`__ " +"framework since :ref:`rfc-72`." +msgstr "" + +#: ../../source/development/testing.rst:133 +msgid "" +"Test cases should be written in a way where they are independent from " +"other ones, so they can potentially be run in a isolated way or in " +"parallel of other test cases. In particular temporary files should be " +"created with a name that cannot conflict with other tests: preferably use" +" pytest's ```tmp_path`` fixture <https://docs.pytest.org/en/7.1.x/how-" +"to/tmp_path.html#the-tmp-path-fixture>`__." +msgstr "" + +#: ../../source/development/testing.rst:138 +msgid "" +"Use ``@pytest.mark.require_driver(driver_name)`` as an annotation for a " +"test case that requires an optional driver to be present." +msgstr "" + +#: ../../source/development/testing.rst:141 +msgid "" +"Use ``pytestmark = pytest.mark.require_driver(\"driver_name\")`` towards " +"the beginning of a test file that requires a given driver to be available" +" for all its test cases. This is typically when writing tests for a " +"particular driver." +msgstr "" + +#: ../../source/development/testing.rst:146 +msgid "" +"Use ``@pytest.mark.require_run_on_demand`` as an annotation to signal a " +"test that should not be run by default, typically because it requires " +"special pre-conditions, use a lot of RAM, etc. and is thus not " +"appropriate to be automatically run by continuous integration." +msgstr "" + +#: ../../source/development/testing.rst:151 +msgid "" +"Use ``@pytest.mark.parametrize(...)`` as an annotation for test functions" +" that test for variations, instead of for() constructs. More details at " +"https://docs.pytest.org/en/latest/parametrize.html" +msgstr "" + +#: ../../source/development/testing.rst:155 +msgid "e.g.:" +msgstr "" + +#: ../../source/development/testing.rst:164 +msgid "instead of" +msgstr "" + +#: ../../source/development/testing.rst:173 +msgid "" +"`Fixtures <https://docs.pytest.org/en/latest/how-to/fixtures.html>`__ can" +" be used to share set-up and tear-down code between test cases." +msgstr "" + +#: ../../source/development/testing.rst:176 +msgid "" +"e.g. a fixture automatically loaded for all test cases of a test file, " +"that takes care to unregister a given driver before the test case is run," +" and re-register it afterwards:" +msgstr "" + +#: ../../source/development/testing.rst:195 +msgid "" +"or a fixture that runs preliminary checks to discover if a driver has " +"some optional capabilities, and skip a test case if not:" +msgstr "" + +#: ../../source/development/testing.rst:220 +msgid "C++ tests" +msgstr "" + +#: ../../source/development/testing.rst:222 +msgid "" +"GDAL C++ tests use the `GoogleTest " +"<https://github.com/google/googletest>`__ framework since :ref:`rfc-88`." +msgstr "" + +#: ../../source/development/testing.rst:225 +msgid "" +"Common non-failing assertions are: ``EXPECT_TRUE(cond)``, " +"``EXPECT_FALSE(cond)``, ``EXPECT_EQ(a, b)``, ``EXPECT_NE(a, b)``, " +"``EXPECT_STREQ(a, b)``, ``EXPECT_LE(a, b)``, ``EXPECT_LT(a, b)``, " +"``EXPECT_GE(a, b)``, ``EXPECT_GT(a, b)``, ``EXPECT_NEAR(a, b, " +"tolerance)`` If one of those assertions fail, the execution of the rest " +"of the test cases continues, hence they should not typically be used if " +"testing a pointer against NULL and dereferencing it unconditionally " +"afterwards. The ASSERT_xxxx family of assertions should be used for such " +"cases where early exit of the test case is desired." +msgstr "" + +#: ../../source/development/testing.rst:234 +msgid "GoogleTest also offers capabilities for parametrized tests. For example:" +msgstr "" + +#: ../../source/development/testing.rst:286 +msgid "Test coverage reports" +msgstr "" + +#: ../../source/development/testing.rst:288 +msgid "" +"GDAL continuous integration has a ``coverage`` configuration that builds " +"GDAL with the ``gcov`` GCC module to get the line coverage of running " +"Python and C++ autotest tests." +msgstr "" + +#: ../../source/development/testing.rst:292 +msgid "" +"This is used by the `Coveralls GitHub Action " +"<https://github.com/marketplace/actions/coveralls-github-action>`__ to " +"upload results to https://coveralls.io/github/OSGeo/gdal, for both push " +"and pull requests events." +msgstr "" + +#: ../../source/development/testing.rst:296 +msgid "" +"A somewhat nicer looking output of line coverage results for the latest " +"master build, generated by ``lcov``, is also available at https" +"://gdalautotest-coverage-results.github.io/coverage_html/index.html" +msgstr "" + +#: ../../source/development/testing.rst:301 +msgid "Post-commit testing" +msgstr "" + +#: ../../source/development/testing.rst:303 +msgid "" +"A weekly static analysis is run by `Coverity " +"<https://scan.coverity.com>`__. Developers/maintainers can request access" +" on the `GDAL project page <https://scan.coverity.com/projects/749>`__." +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/download.mo b/doc/source/locale/ja/LC_MESSAGES/download.mo new file mode 100644 index 0000000000000000000000000000000000000000..a63703bc837145e48fc22a199ea3cf664856447e GIT binary patch literal 609 zcmYjNL2uJA6gCJD3J0W}kl<i(ogC6q!ARF>T~kIyvsNWS8aFTTvJA(rY-i9DD3K7H zIC0vE3kMinI87RVg^MNl8@z;y@#Ih6`<_4h+3)Adr4I<=GT;^<sKtN5A-@X90oMUX zOZ^7;8sI(P)dhr(fv*5=UPR~y@NM7~;O>%lfYCq-!-UajP$&fno-xj-W+;#^1eY{H zPh_EDh6gfXXsYBPiwzki<SA1+lfuW_L4S;$8JkOGNT|~+AzMYNNhE#jOeYZ;C`Juf zNk9$raocNmh<BfOE$rR(JNH(-2c8E;GGj+sedW@(JM7O$I3YnFKbrXAX!Y4-XXuQn zHY8G1Xikk(KHimCe30SCbU|~9*B6a+pEq(d&1uHnSmqmWP^1M-;Q@#ApCA#Vd0oNl z<MAfXT&dCxXUYpjIe92mu6-=#jnutX7ynIrUe^gn;qZJ0E!T6FlO)k%4owVuY3|H9 z%|sW+2UKZhdWG31Yv;cD6Z=e&p@?OYiPXnydzo>znP3Vg1!G+Jc#G~aj@xdl11-?+ z<8QxCJ|bIwvDJyKzT4`ptv)yF%$BFfR<CXOsoD5yt20}@1MiPID^G0+_NMd)>YTv( literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/download.po b/doc/source/locale/ja/LC_MESSAGES/download.po new file mode 100644 index 000000000000..7a7a5d964d92 --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/download.po @@ -0,0 +1,251 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Yoichi Kayama <yoichi.kayama@gmail.com>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/download.rst:5 +msgid "Download" +msgstr "ダウンロード" + +#: ../../source/download.rst:10 +msgid "Contents" +msgstr "目次" + +#: ../../source/download.rst:13 +msgid "" +"The GDAL project distributes GDAL as source code and :ref:`Containers` " +"only. :ref:`Binaries` produced by others are available for a variety of " +"platforms and package managers." +msgstr "" + +#: ../../source/download.rst:16 +msgid "Source Code" +msgstr "ソースコード" + +#: ../../source/download.rst:19 +msgid "Current Release" +msgstr "カレントリリース" + +#: ../../source/download.rst:21 +msgid "**2024-06-26** `gdal-3.9.1.tar.gz`_ `3.9.1 Release Notes`_ (`3.9.1 md5`_)" +msgstr "" + +#: ../../source/download.rst:28 +msgid "Past Releases" +msgstr "" + +#: ../../source/download.rst:30 +msgid "Links to :ref:`download_past` are also available." +msgstr "" + +#: ../../source/download.rst:35 +msgid "Development Source" +msgstr "" + +#: ../../source/download.rst:37 +msgid "" +"The main repository for GDAL is located on GitHub at " +"https://github.com/OSGeo/GDAL." +msgstr "" + +#: ../../source/download.rst:40 +msgid "" +"You can obtain a copy of the active source code by issuing the following " +"command" +msgstr "" + +#: ../../source/download.rst:48 +msgid "" +"Additional information is available about :ref:`build_requirements` and " +":ref:`building_from_source`." +msgstr "" + +#: ../../source/download.rst:54 +msgid "Binaries" +msgstr "" + +#: ../../source/download.rst:56 +msgid "" +"In this section we list a number of the binary distributions of GDAL all " +"of which should have fully reproducible open source build recipes." +msgstr "" + +#: ../../source/download.rst:59 +msgid "" +"Note that the maintainers of those distributions are generally not the " +"maintainers of the GDAL sources, so please report any issue specific to " +"those builds through their own support channels." +msgstr "" + +#: ../../source/download.rst:64 +msgid "Windows" +msgstr "" + +#: ../../source/download.rst:66 +msgid "" +"Windows builds are available via `Conda Forge`_ (64-bit only). See the " +":ref:`conda` section for more detailed information. GDAL is also " +"distributed by `GISInternals`_ and `OSGeo4W`_ and through the `NuGet`_ " +"and :ref:`vcpkg` package managers." +msgstr "" + +#: ../../source/download.rst:76 +msgid "Linux" +msgstr "" + +#: ../../source/download.rst:78 +msgid "" +"Packages are available for `Debian`_, `Alpine_`, `Fedora_`, and other " +"distributions." +msgstr "" + +#: ../../source/download.rst:86 +msgid "Mac OS" +msgstr "" + +#: ../../source/download.rst:88 +msgid "GDAL packages are available on `Homebrew`_." +msgstr "" + +#: ../../source/download.rst:94 +msgid "Cross-Platform Package Managers" +msgstr "" + +#: ../../source/download.rst:99 +msgid "Conda" +msgstr "" + +#: ../../source/download.rst:101 +msgid "" +"`Conda <https://anaconda.org>`__ can be used on multiple platforms " +"(Windows, macOS, and Linux) to install software packages and manage " +"environments. Conda packages for GDAL are available through `conda-forge " +"<https://anaconda.org/conda-forge/gdal>`__." +msgstr "" + +#: ../../source/download.rst:107 +msgid "Latest version: |Conda badge|" +msgstr "" + +#: ../../source/download.rst +msgid "Conda badge" +msgstr "" + +#: ../../source/download.rst:122 +msgid "To install the Arrow and Parquet drivers as plugins:" +msgstr "" + +#: ../../source/download.rst:130 +msgid "GDAL master Conda builds" +msgstr "" + +#: ../../source/download.rst:132 +msgid "" +"GDAL master builds are available in the `gdal-master " +"<https://anaconda.org/gdal-master/gdal>`__ channel. They are based on " +"dependencies from the ``conda-forge`` channel." +msgstr "" + +#: ../../source/download.rst:135 +msgid "" +"First, install mamba into the ``base`` environment, create a dedicated " +"``gdal_master_env`` environment, and then activate the dedicated " +"``gdal_master_env`` environment." +msgstr "" + +#: ../../source/download.rst:145 +msgid "Then install GDAL from the ``gdal-master`` channel:" +msgstr "" + +#: ../../source/download.rst:156 +msgid "vcpkg" +msgstr "" + +#: ../../source/download.rst:158 +msgid "" +"The GDAL port in the `vcpkg <https://github.com/Microsoft/vcpkg>`__ " +"dependency manager is kept up to date by Microsoft team members and " +"community contributors. You can download and install GDAL using the vcpkg" +" as follows:" +msgstr "" + +#: ../../source/download.rst:169 +msgid "" +"If the version is out of date, please `create an issue or pull request " +"<https://github.com/Microsoft/vcpkg>`__ on the vcpkg repository." +msgstr "" + +#: ../../source/download.rst:172 +msgid "Spack" +msgstr "" + +#: ../../source/download.rst:174 +msgid "" +"Spack is a package management tool designed to support multiple versions " +"and configurations of software on a wide variety of platforms and " +"environments. It was designed for large supercomputing centers. Spack " +"builds packages from sources, and allows tweaking their configurations." +msgstr "" + +#: ../../source/download.rst:179 +msgid "" +"You can find information about GDAL in Spack at " +"https://packages.spack.io/package.html?name=gdal" +msgstr "" + +#: ../../source/download.rst:182 +msgid "For the default GDAL build with a reduced number of drivers:" +msgstr "" + +#: ../../source/download.rst:190 +msgid "For a build with netcdf driver enabled:" +msgstr "" + +#: ../../source/download.rst:200 +msgid "Containers" +msgstr "" + +#: ../../source/download.rst:202 +msgid "" +"Docker images with nightly builds of GDAL master and tagged releases are " +"available at `GitHub Container registry " +"<https://github.com/OSGeo/gdal/pkgs/container/gdal>`_." +msgstr "" + +#: ../../source/download.rst:205 +msgid "" +"Information on the content of the different configurations can be found " +"at `https://github.com/OSGeo/gdal/tree/master/docker " +"<https://github.com/OSGeo/gdal/tree/master/docker>`_." +msgstr "" + +#: ../../source/download.rst:210 +msgid "Documentation" +msgstr "" + +#: ../../source/download.rst:212 +msgid "" +"Besides being included when downloading the software, the documentation " +"is also available independently as a `PDF file " +"<https://gdal.org/gdal.pdf>`_, and `a ZIP of individual HTML pages " +"<https://github.com/OSGeo/gdal-docs/archive/refs/heads/master.zip>`_ for " +"offline browsing. (The ZIP also includes the PDF.) The documentation " +"reflects the latest state of the development branch of the software." +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/download_past.mo b/doc/source/locale/ja/LC_MESSAGES/download_past.mo new file mode 100644 index 0000000000000000000000000000000000000000..500a0d30cfe9861a9cb9f6eb09ba3d389fdaf02b GIT binary patch literal 481 zcmYjN!EO^V5M2<bmAD{r<1qI!ixVO!PEs{(LW!CsQ4}GS+jKMCy6oDK?NsE13isal z2@c#5`~m;KCE~zeFbRk<@{`}Qo;}a=<KCT*iPUYu1Hr?M_^&#`?+Uttcej${SoZsZ z@4}M_g$Prwm;#4n;@t%o5r=bp#XcBkH5~POBS@#ba6V!lN;AiUWf^ehG^CU93=ch1 z6f5>AvWBK=wopAq)d2Nax1Q{%XG)0?r+jHPPyY3t40=<{$Jp<|i?Pm!JFmwt2kA)i z;LMW^6-DPYoH$dQ8#tyF)dZc@R%UOua=)y}R9WHbJ-KMhC6yB3g8m7dG1Z$B=!{1D zmC2kh_tHtV^i<(<=j))sF19js8*TVQyQ-b$!+dZvgGQ#(LuVsf3Ab8ElgMx5qeVr= zwxKvDA2@cG@eFrwe49_4vB!Ze+}zkw!|thx=@DD@GASA3O2Yx2as|z-(UKO)udC~y T*I(CHpVuEgZP&N;`!C6F%nOs@ literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/download_past.po b/doc/source/locale/ja/LC_MESSAGES/download_past.po new file mode 100644 index 000000000000..08bd69ff807c --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/download_past.po @@ -0,0 +1,411 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Yoichi Kayama <yoichi.kayama@gmail.com>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/download_past.rst:6 +msgid "Past Releases" +msgstr "過去のリリース" + +#: ../../source/download_past.rst:8 +msgid "**2024-05-10** `gdal-3.9.0.tar.gz`_ `3.9.0 Release Notes`_ (`3.9.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:14 +msgid "**2024-04-04** `gdal-3.8.5.tar.gz`_ `3.8.5 Release Notes`_ (`3.8.5 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:20 +msgid "**2024-02-18** `gdal-3.8.4.tar.gz`_ `3.8.4 Release Notes`_ (`3.8.4 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:26 +msgid "**2024-01-08** `gdal-3.8.3.tar.gz`_ `3.8.3 Release Notes`_ (`3.8.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:32 +msgid "**2023-12-20** `gdal-3.8.2.tar.gz`_ `3.8.2 Release Notes`_ (`3.8.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:38 +msgid "**2023-11-30** `gdal-3.8.1.tar.gz`_ `3.8.1 Release Notes`_ (`3.8.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:44 +msgid "**2023-11-13** `gdal-3.8.0.tar.gz`_ `3.8.0 Release Notes`_ (`3.8.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:50 +msgid "**2023-11-03** `gdal-3.7.3.tar.gz`_ `3.7.3 Release Notes`_ (`3.7.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:56 +msgid "**2023-09-13** `gdal-3.7.2.tar.gz`_ `3.7.2 Release Notes`_ (`3.7.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:62 +msgid "**2023-07-13** `gdal-3.7.1.tar.gz`_ `3.7.1 Release Notes`_ (`3.7.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:68 +msgid "**2023-05-10** `gdal-3.7.0.tar.gz`_ `3.7.0 Release Notes`_ (`3.7.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:74 +msgid "**2023-04-21** `gdal-3.6.4.tar.gz`_ `3.6.4 Release Notes`_ (`3.6.4 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:80 +msgid "**2023-03-13** `gdal-3.6.3.tar.gz`_ `3.6.3 Release Notes`_ (`3.6.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:86 +msgid "**2023-01-05** `gdal-3.6.2.tar.gz`_ `3.6.2 Release Notes`_ (`3.6.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:92 +msgid "**2022-12-11** `gdal-3.6.1.tar.gz`_ `3.6.1 Release Notes`_ (`3.6.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:98 +msgid "" +"**2022-11-06** `3.6.0 Release Notes`_ *Warning*: this version has been " +"officially retracted and superseded per 3.6.1" +msgstr "" + +#: ../../source/download_past.rst:102 +msgid "**2022-10-21** `gdal-3.5.3.tar.gz`_ `3.5.3 Release Notes`_ (`3.5.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:108 +msgid "**2022-09-12** `gdal-3.5.2.tar.gz`_ `3.5.2 Release Notes`_ (`3.5.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:114 +msgid "**2022-07-06** `gdal-3.5.1.tar.gz`_ `3.5.1 Release Notes`_ (`3.5.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:120 +msgid "**2022-05-13** `gdal-3.5.0.tar.gz`_ `3.5.0 Release Notes`_ (`3.5.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:126 +msgid "**2022-04-22** `gdal-3.4.3.tar.gz`_ `3.4.3 Release Notes`_ (`3.4.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:132 +msgid "**2022-03-08** `gdal-3.4.2.tar.gz`_ `3.4.2 Release Notes`_ (`3.4.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:138 +msgid "**2021-12-27** `gdal-3.4.1.tar.gz`_ `3.4.1 Release Notes`_ (`3.4.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:144 +msgid "**2021-11-08** `gdal-3.4.0.tar.gz`_ `3.4.0 Release Notes`_ (`3.4.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:150 +msgid "**2021-10-29** `gdal-3.3.3.tar.gz`_ `3.3.3 Release Notes`_ (`3.3.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:156 +msgid "**2021-09-01** `gdal-3.3.2.tar.gz`_ `3.3.2 Release Notes`_ (`3.3.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:162 +msgid "**2021-07-05** `gdal-3.3.1.tar.gz`_ `3.3.1 Release Notes`_ (`3.3.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:168 +msgid "**2021-05-03** `gdal-3.3.0.tar.gz`_ `3.3.0 Release Notes`_ (`3.3.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:174 +msgid "**2021-05-04** `gdal-3.2.3.tar.gz`_ `3.2.3 Release Notes`_ (`3.2.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:180 +msgid "**2021-03-10** `gdal-3.2.2.tar.gz`_ `3.2.2 Release Notes`_ (`3.2.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:186 +msgid "**2020-12-28** `gdal-3.2.1.tar.gz`_ `3.2.1 Release Notes`_ (`3.2.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:192 +msgid "**2020-10-26** `gdal-3.2.0.tar.gz`_ `3.2.0 Release Notes`_ (`3.2.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:198 +msgid "**2020-10-23** `gdal-3.1.4.tar.gz`_ `3.1.4 Release Notes`_ (`3.1.4 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:204 +msgid "**2020-09-01** `gdal-3.1.3.tar.gz`_ `3.1.3 Release Notes`_ (`3.1.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:210 +msgid "**2020-07-07** `gdal-3.1.2.tar.gz`_ `3.1.2 Release Notes`_ (`3.1.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:216 +msgid "**2020-06-22** `gdal-3.1.1.tar.gz`_ `3.1.1 Release Notes`_ (`3.1.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:223 +msgid "**2020-05-03** `gdal-3.1.0.tar.gz`_ `3.1.0 Release Notes`_ (`3.1.0 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:229 +msgid "**2020-01-28** `gdal-3.0.4.tar.gz`_ `3.0.4 Release Notes`_ (`3.0.4 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:235 +msgid "**2020-01-08** `gdal-2.4.4.tar.gz`_ `2.4.4 Release Notes`_ (`2.4.4 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:241 +msgid "**2020-01-08** `gdal-3.0.3.tar.gz`_ `3.0.3 Release Notes`_ (`3.0.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:247 +msgid "**2019-10-28** `gdal-3.0.2.tar.gz`_ `3.0.2 Release Notes`_ (`3.0.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:253 +msgid "**2019-10-28** `gdal-2.4.3.tar.gz`_ `2.4.3 Release Notes`_ (`2.4.3 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:260 +msgid "**2019-06-28** `gdal-3.0.1.tar.gz`_ `3.0.1 Release Notes`_ (`3.0.1 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:267 +msgid "**2019-06-28** `gdal-2.4.2.tar.gz`_ `2.4.2 Release Notes`_ (`2.4.2 md5`_)" +msgstr "" + +#: ../../source/download_past.rst:274 ../../source/download_past.rst:295 +msgid "**2019-05** `gdal-3.0.0.tar.gz`_ `3.0.0 Release Notes`_ (`3.0.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:281 ../../source/download_past.rst:302 +msgid "**2019-03** `gdal-2.4.1.tar.gz`_ `2.4.1 Release Notes`_ (`2.4.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:288 ../../source/download_past.rst:309 +msgid "**2018-12** `gdal-2.4.0.tar.gz`_ `2.4.0 Release Notes`_ (`2.4.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:316 +msgid "**2018-12** `gdal-2.3.3.tar.gz`_ `2.3.3 Release Notes`_ (`2.3.3 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:323 +msgid "**2018-09** `gdal-2.3.2.tar.gz`_ `2.3.2 Release Notes`_ (`2.3.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:330 +msgid "**2018-06** `gdal-2.3.1.tar.gz`_ `2.3.1 Release Notes`_ (`2.3.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:337 +msgid "**2018-05** `gdal-2.3.0.tar.gz`_ `2.3.0 Release Notes`_ (`2.3.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:344 +msgid "**2018-03** `gdal-2.2.4.tar.gz`_ `2.2.4 Release Notes`_ (`2.2.4 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:351 +msgid "**2017-11** `gdal-2.2.3.tar.gz`_ `2.2.3 Release Notes`_ (`2.2.3 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:358 +msgid "**2017-09** `gdal-2.2.2.tar.gz`_ `2.2.2 Release Notes`_ (`2.2.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:365 +msgid "**2017-06** `gdal-2.2.1.tar.gz`_ `2.2.1 Release Notes`_ (`2.2.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:372 +msgid "**2017-06** `gdal-2.1.4.tar.gz`_ `2.1.4 Release Notes`_ (`2.1.4 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:379 +msgid "**2017-04** `gdal-2.2.0.tar.gz`_ `2.2.0 Release Notes`_ (`2.2.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:386 +msgid "**2017-01** `gdal-2.1.3.tar.gz`_ `2.1.3 Release Notes`_ (`2.1.3 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:393 +msgid "**2016-10** `gdal-2.1.2.tar.gz`_ `2.1.2 Release Notes`_ (`2.1.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:400 +msgid "**2016-07** `gdal-2.1.1.tar.gz`_ `2.1.1 Release Notes`_ (`2.1.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:407 +msgid "**2016-07** `gdal-2.0.3.tar.gz`_ `2.0.3 Release Notes`_ (`2.0.3 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:414 +msgid "**2016-07** `gdal-1.11.5.tar.gz`_ `1.11.5 Release Notes`_ (`1.11.5 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:421 +msgid "**2016-04** `gdal-2.1.0.tar.gz`_ `2.1.0 Release Notes`_ (`2.1.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:428 +msgid "**2016-01** `gdal-2.0.2.tar.gz`_ `2.0.2 Release Notes`_ (`2.0.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:435 +msgid "**2016-01** `gdal-1.11.4.tar.gz`_ `1.11.4 Release Notes`_ (`1.11.4 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:442 +msgid "**2015-09** `gdal-2.0.1.tar.gz`_ `2.0.1 Release Notes`_ (`2.0.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:449 +msgid "**2015-09** `gdal-1.11.3.tar.gz`_ `1.11.3 Release Notes`_ (`1.11.3 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:456 +msgid "**2015-06** `gdal-2.0.0.tar.gz`_ `2.0.0 Release Notes`_ (`2.0.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:463 +msgid "**2015-02** `gdal-1.11.2.tar.gz`_ `1.11.2 Release Notes`_ (`1.11.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:470 +msgid "**2014-09** `gdal-1.11.1.tar.gz`_ `1.11.1 Release Notes`_ (`1.11.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:477 +msgid "**2014-04** `gdal-1.11.0.tar.gz`_ `1.11.0 Release Notes`_ (`1.11.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:484 +msgid "**2013-08** `gdal-1.10.1.tar.gz`_ `1.10.1 Release Notes`_ (`1.10.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:491 +msgid "**2013-04** `gdal-1.10.0.tar.gz`_ `1.10.0 Release Notes`_ (`1.10.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:498 +msgid "**2012-10** `gdal-1.9.2.tar.gz`_ `1.9.2 Release Notes`_ (`1.9.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:505 +msgid "**2012-05** `gdal-1.9.1.tar.gz`_ `1.9.1 Release Notes`_ (`1.9.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:512 +msgid "**2011-12** `gdal-1.9.0.tar.gz`_ `1.9.0 Release Notes`_ (`1.9.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:519 +msgid "**2011-07** `gdal-1.8.1.tar.gz`_ `1.8.1 Release Notes`_ (`1.8.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:526 +msgid "**2011-01** `gdal-1.8.0.tar.gz`_ `1.8.0 Release Notes`_ (`1.8.0 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:533 +msgid "**2010-11** `gdal-1.7.3.tar.gz`_ `1.7.3 Release Notes`_ (`1.7.3 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:539 +msgid "**2010-04** `gdal-1.7.2.tar.gz`_ `1.7.2 Release Notes`_ (`1.7.2 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:546 +msgid "**2010-02** `gdal-1.7.1.tar.gz`_ `1.7.1 Release Notes`_ (`1.7.1 md5`)_" +msgstr "" + +#: ../../source/download_past.rst:553 +msgid "**2010-01** `1.7.0 (retracted) Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:558 +msgid "**2009-11** `gdal-1.6.3.tar.gz`_ `1.6.3 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:564 +msgid "**2009-08** `gdal-1.6.2.tar.gz`_ `1.6.2 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:570 +msgid "**2009-05** `gdal-1.6.1.tar.gz`_ `1.6.1 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:576 +msgid "**2008-12** `gdal-1.6.0.tar.gz`_ `1.6.0 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:582 +msgid "**2009-01** `gdal-1.5.4.tar.gz`_ `1.5.4 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:588 +msgid "**2008-10** `gdal-1.5.3.tar.gz`_ `1.5.3 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:594 +msgid "**2008-05** `gdal-1.5.2.tar.gz`_ `1.5.2 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:600 +msgid "**2008-03** `gdal-1.5.1.tar.gz`_ `1.5.1 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:606 +msgid "**2007-12** `gdal-1.5.0.tar.gz`_ `1.5.0 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:612 +msgid "**2008-12** `gdal-1.4.5.tar.gz`_ `1.4.5 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:618 +msgid "**2007-11** `gdal-1.4.4.tar.gz`_ `1.4.4 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:624 +msgid "**2007-06** `gdal-1.4.2.tar.gz`_ `1.4.2 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:630 +msgid "**2007-04** `gdal-1.4.1.tar.gz`_ `1.4.1 Release Notes`_" +msgstr "" + +#: ../../source/download_past.rst:636 +msgid "**2007-01** `gdal-1.4.0.tar.gz`_" +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/drivers.mo b/doc/source/locale/ja/LC_MESSAGES/drivers.mo new file mode 100644 index 0000000000000000000000000000000000000000..e2267788ba9b0b286d5bc42a09828116e4c130f8 GIT binary patch literal 415 zcmYk2&rZTX5XLd_)T3t)bMS_PTO^9hpHOJQCM_kUn&@qTrIwW4y4@Oi5MR${ajQn0 zWRm%2f0=J~KF>}+8YWImo}0X=#lN^T^{aWry0=hr$JZMD4L)*JW>Qd?xlRC9%nPYB zhGm*<a9pJ&CX#}+h!UJA&a^?%WtvlHlXeHmEfO2ZHSOFq$sHjE#F)Qj^~hiD$#Y^1 zBXk|Ok7(#OpQE{F1+3JVC??9BX{jhoAA$hpPUu133mrcgIj$Rf%jM9ZBCS|zEO+cr zV8YqH?m#~XMtRnfDjiyjyizR3sZ{%tf+)UaIk0>1Qw~Va3jNSK{@QL4Ya)f_!mM*B zjEUy&`l`rTCVH@bVXEYMQ0Xmpk6gX>mMiqcT5d9tQs}NSZOypg%G|~r?m%J8Ry>Dx J%kCJ9#urd-cUS-b literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/drivers.po b/doc/source/locale/ja/LC_MESSAGES/drivers.po new file mode 100644 index 000000000000..d6f107e47c37 --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/drivers.po @@ -0,0 +1,51208 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/drivers/raster/Idrisi.rst:5 +msgid "RST -- Idrisi Raster Format" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:-1 +#: ../../source/drivers/raster/aaigrid.rst:-1 +#: ../../source/drivers/raster/ace2.rst:-1 +#: ../../source/drivers/raster/adrg.rst:-1 +#: ../../source/drivers/raster/aig.rst:-1 +#: ../../source/drivers/raster/airsar.rst:-1 +#: ../../source/drivers/raster/bag.rst:-1 +#: ../../source/drivers/raster/basisu.rst:-1 +#: ../../source/drivers/raster/blx.rst:-1 +#: ../../source/drivers/raster/bmp.rst:-1 +#: ../../source/drivers/raster/bsb.rst:-1 ../../source/drivers/raster/bt.rst:-1 +#: ../../source/drivers/raster/byn.rst:-1 +#: ../../source/drivers/raster/cad.rst:-1 +#: ../../source/drivers/raster/cals.rst:-1 +#: ../../source/drivers/raster/ceos.rst:-1 +#: ../../source/drivers/raster/coasp.rst:-1 +#: ../../source/drivers/raster/cog.rst:-1 +#: ../../source/drivers/raster/cosar.rst:-1 +#: ../../source/drivers/raster/cpg.rst:-1 +#: ../../source/drivers/raster/ctable2.rst:-1 +#: ../../source/drivers/raster/ctg.rst:-1 +#: ../../source/drivers/raster/daas.rst:-1 +#: ../../source/drivers/raster/dds.rst:-1 +#: ../../source/drivers/raster/derived.rst:-1 +#: ../../source/drivers/raster/dimap.rst:-1 +#: ../../source/drivers/raster/dipex.rst:-1 +#: ../../source/drivers/raster/doq1.rst:-1 +#: ../../source/drivers/raster/doq2.rst:-1 +#: ../../source/drivers/raster/dted.rst:-1 +#: ../../source/drivers/raster/ecrgtoc.rst:-1 +#: ../../source/drivers/raster/ecw.rst:-1 +#: ../../source/drivers/raster/eedai.rst:-1 +#: ../../source/drivers/raster/ehdr.rst:-1 +#: ../../source/drivers/raster/eir.rst:-1 +#: ../../source/drivers/raster/elas.rst:-1 +#: ../../source/drivers/raster/envi.rst:-1 +#: ../../source/drivers/raster/ers.rst:-1 +#: ../../source/drivers/raster/esat.rst:-1 +#: ../../source/drivers/raster/esric.rst:-1 +#: ../../source/drivers/raster/exr.rst:-1 +#: ../../source/drivers/raster/fast.rst:-1 +#: ../../source/drivers/raster/fit.rst:-1 +#: ../../source/drivers/raster/fits.rst:-1 +#: ../../source/drivers/raster/genbin.rst:-1 +#: ../../source/drivers/raster/georaster.rst:-1 +#: ../../source/drivers/raster/gff.rst:-1 +#: ../../source/drivers/raster/gif.rst:-1 +#: ../../source/drivers/raster/gpkg.rst:-1 +#: ../../source/drivers/raster/grass.rst:-1 +#: ../../source/drivers/raster/grassasciigrid.rst:-1 +#: ../../source/drivers/raster/grib.rst:-1 +#: ../../source/drivers/raster/gs7bg.rst:-1 +#: ../../source/drivers/raster/gsag.rst:-1 +#: ../../source/drivers/raster/gsbg.rst:-1 +#: ../../source/drivers/raster/gsc.rst:-1 +#: ../../source/drivers/raster/gta.rst:-1 +#: ../../source/drivers/raster/gti.rst:-1 +#: ../../source/drivers/raster/gtiff.rst:-1 +#: ../../source/drivers/raster/gxf.rst:-1 +#: ../../source/drivers/raster/hdf4.rst:-1 +#: ../../source/drivers/raster/hdf5.rst:-1 +#: ../../source/drivers/raster/heif.rst:-1 +#: ../../source/drivers/raster/hf2.rst:-1 +#: ../../source/drivers/raster/hfa.rst:-1 +#: ../../source/drivers/raster/ilwis.rst:-1 +#: ../../source/drivers/raster/iris.rst:-1 +#: ../../source/drivers/raster/isce.rst:-1 +#: ../../source/drivers/raster/isg.rst:-1 +#: ../../source/drivers/raster/isis2.rst:-1 +#: ../../source/drivers/raster/isis3.rst:-1 +#: ../../source/drivers/raster/jdem.rst:-1 +#: ../../source/drivers/raster/jp2ecw.rst:-1 +#: ../../source/drivers/raster/jp2kak.rst:-1 +#: ../../source/drivers/raster/jp2lura.rst:-1 +#: ../../source/drivers/raster/jp2mrsid.rst:-1 +#: ../../source/drivers/raster/jp2openjpeg.rst:-1 +#: ../../source/drivers/raster/jpeg.rst:-1 +#: ../../source/drivers/raster/jpegxl.rst:-1 +#: ../../source/drivers/raster/jpipkak.rst:-1 +#: ../../source/drivers/raster/kea.rst:-1 +#: ../../source/drivers/raster/kmlsuperoverlay.rst:-1 +#: ../../source/drivers/raster/kro.rst:-1 +#: ../../source/drivers/raster/ktx2.rst:-1 +#: ../../source/drivers/raster/l1b.rst:-1 +#: ../../source/drivers/raster/lan.rst:-1 +#: ../../source/drivers/raster/lcp.rst:-1 +#: ../../source/drivers/raster/leveller.rst:-1 +#: ../../source/drivers/raster/loslas.rst:-1 +#: ../../source/drivers/raster/map.rst:-1 +#: ../../source/drivers/raster/marfa.rst:-1 +#: ../../source/drivers/raster/mbtiles.rst:-1 +#: ../../source/drivers/raster/mem.rst:-1 +#: ../../source/drivers/raster/mff.rst:-1 +#: ../../source/drivers/raster/mff2.rst:-1 +#: ../../source/drivers/raster/mrsid.rst:-1 +#: ../../source/drivers/raster/msg.rst:-1 +#: ../../source/drivers/raster/msgn.rst:-1 +#: ../../source/drivers/raster/ndf.rst:-1 +#: ../../source/drivers/raster/netcdf.rst:-1 +#: ../../source/drivers/raster/ngsgeoid.rst:-1 +#: ../../source/drivers/raster/ngw.rst:-1 +#: ../../source/drivers/raster/nitf.rst:-1 +#: ../../source/drivers/raster/noaa_b.rst:-1 +#: ../../source/drivers/raster/nsidcbin.rst:-1 +#: ../../source/drivers/raster/ntv2.rst:-1 +#: ../../source/drivers/raster/nwtgrd.rst:-1 +#: ../../source/drivers/raster/ogcapi.rst:-1 +#: ../../source/drivers/raster/openfilegdb.rst:-1 +#: ../../source/drivers/raster/ozi.rst:-1 +#: ../../source/drivers/raster/palsar.rst:-1 +#: ../../source/drivers/raster/paux.rst:-1 +#: ../../source/drivers/raster/pcidsk.rst:-1 +#: ../../source/drivers/raster/pcraster.rst:-1 +#: ../../source/drivers/raster/pdf.rst:-1 +#: ../../source/drivers/raster/pds.rst:-1 +#: ../../source/drivers/raster/pds4.rst:-1 +#: ../../source/drivers/raster/plmosaic.rst:-1 +#: ../../source/drivers/raster/png.rst:-1 +#: ../../source/drivers/raster/pnm.rst:-1 +#: ../../source/drivers/raster/postgisraster.rst:-1 +#: ../../source/drivers/raster/prf.rst:-1 ../../source/drivers/raster/r.rst:-1 +#: ../../source/drivers/raster/rasterlite.rst:-1 +#: ../../source/drivers/raster/rasterlite2.rst:-1 +#: ../../source/drivers/raster/rdb.rst:-1 +#: ../../source/drivers/raster/rik.rst:-1 +#: ../../source/drivers/raster/rmf.rst:-1 +#: ../../source/drivers/raster/roi_pac.rst:-1 +#: ../../source/drivers/raster/rpftoc.rst:-1 +#: ../../source/drivers/raster/rraster.rst:-1 +#: ../../source/drivers/raster/rs2.rst:-1 +#: ../../source/drivers/raster/s102.rst:-1 +#: ../../source/drivers/raster/s104.rst:-1 +#: ../../source/drivers/raster/s111.rst:-1 +#: ../../source/drivers/raster/safe.rst:-1 +#: ../../source/drivers/raster/sar_ceos.rst:-1 +#: ../../source/drivers/raster/sdat.rst:-1 +#: ../../source/drivers/raster/sdts.rst:-1 +#: ../../source/drivers/raster/sentinel2.rst:-1 +#: ../../source/drivers/raster/sgi.rst:-1 +#: ../../source/drivers/raster/sigdem.rst:-1 +#: ../../source/drivers/raster/snodas.rst:-1 +#: ../../source/drivers/raster/srp.rst:-1 +#: ../../source/drivers/raster/srtmhgt.rst:-1 +#: ../../source/drivers/raster/stacit.rst:-1 +#: ../../source/drivers/raster/stacta.rst:-1 +#: ../../source/drivers/raster/terragen.rst:-1 +#: ../../source/drivers/raster/tga.rst:-1 +#: ../../source/drivers/raster/til.rst:-1 +#: ../../source/drivers/raster/tiledb.rst:-1 +#: ../../source/drivers/raster/tsx.rst:-1 +#: ../../source/drivers/raster/usgsdem.rst:-1 +#: ../../source/drivers/raster/vicar.rst:-1 +#: ../../source/drivers/raster/vrt.rst:-1 +#: ../../source/drivers/raster/wcs.rst:-1 +#: ../../source/drivers/raster/webp.rst:-1 +#: ../../source/drivers/raster/wms.rst:-1 +#: ../../source/drivers/raster/wmts.rst:-1 +#: ../../source/drivers/raster/xpm.rst:-1 +#: ../../source/drivers/raster/xyz.rst:-1 +#: ../../source/drivers/raster/zarr.rst:-1 +#: ../../source/drivers/raster/zmap.rst:-1 +#: ../../source/drivers/vector/amigocloud.rst:-1 +#: ../../source/drivers/vector/arrow.rst:-1 +#: ../../source/drivers/vector/avcbin.rst:-1 +#: ../../source/drivers/vector/avce00.rst:-1 +#: ../../source/drivers/vector/cad.rst:-1 +#: ../../source/drivers/vector/carto.rst:-1 +#: ../../source/drivers/vector/csv.rst:-1 +#: ../../source/drivers/vector/csw.rst:-1 +#: ../../source/drivers/vector/dgn.rst:-1 +#: ../../source/drivers/vector/dgnv8.rst:-1 +#: ../../source/drivers/vector/dwg.rst:-1 +#: ../../source/drivers/vector/dxf.rst:-1 +#: ../../source/drivers/vector/edigeo.rst:-1 +#: ../../source/drivers/vector/eeda.rst:-1 +#: ../../source/drivers/vector/elasticsearch.rst:-1 +#: ../../source/drivers/vector/esrijson.rst:-1 +#: ../../source/drivers/vector/filegdb.rst:-1 +#: ../../source/drivers/vector/flatgeobuf.rst:-1 +#: ../../source/drivers/vector/geoconcept.rst:-1 +#: ../../source/drivers/vector/geojson.rst:-1 +#: ../../source/drivers/vector/geojsonseq.rst:-1 +#: ../../source/drivers/vector/georss.rst:-1 +#: ../../source/drivers/vector/gml.rst:-1 +#: ../../source/drivers/vector/gmlas.rst:-1 +#: ../../source/drivers/vector/gmt.rst:-1 +#: ../../source/drivers/vector/gpkg.rst:-1 +#: ../../source/drivers/vector/gpsbabel.rst:-1 +#: ../../source/drivers/vector/gpx.rst:-1 +#: ../../source/drivers/vector/grass.rst:-1 +#: ../../source/drivers/vector/gtfs.rst:-1 +#: ../../source/drivers/vector/hana.rst:-1 +#: ../../source/drivers/vector/idb.rst:-1 +#: ../../source/drivers/vector/idrisi.rst:-1 +#: ../../source/drivers/vector/ili.rst:-1 +#: ../../source/drivers/vector/jml.rst:-1 +#: ../../source/drivers/vector/jsonfg.rst:-1 +#: ../../source/drivers/vector/kml.rst:-1 +#: ../../source/drivers/vector/libkml.rst:-1 +#: ../../source/drivers/vector/lvbag.rst:-1 +#: ../../source/drivers/vector/mapml.rst:-1 +#: ../../source/drivers/vector/memory.rst:-1 +#: ../../source/drivers/vector/miramon.rst:-1 +#: ../../source/drivers/vector/mitab.rst:-1 +#: ../../source/drivers/vector/mongodbv3.rst:-1 +#: ../../source/drivers/vector/mssqlspatial.rst:-1 +#: ../../source/drivers/vector/mvt.rst:-1 +#: ../../source/drivers/vector/mysql.rst:-1 +#: ../../source/drivers/vector/nas.rst:-1 +#: ../../source/drivers/vector/netcdf.rst:-1 +#: ../../source/drivers/vector/ngw.rst:-1 +#: ../../source/drivers/vector/ntf.rst:-1 +#: ../../source/drivers/vector/oapif.rst:-1 +#: ../../source/drivers/vector/oci.rst:-1 +#: ../../source/drivers/vector/odbc.rst:-1 +#: ../../source/drivers/vector/ods.rst:-1 +#: ../../source/drivers/vector/ogdi.rst:-1 +#: ../../source/drivers/vector/openfilegdb.rst:-1 +#: ../../source/drivers/vector/osm.rst:-1 +#: ../../source/drivers/vector/parquet.rst:-1 +#: ../../source/drivers/vector/pdf.rst:-1 +#: ../../source/drivers/vector/pds.rst:-1 ../../source/drivers/vector/pg.rst:-1 +#: ../../source/drivers/vector/pgdump.rst:-1 +#: ../../source/drivers/vector/pgeo.rst:-1 +#: ../../source/drivers/vector/plscenes.rst:-1 +#: ../../source/drivers/vector/pmtiles.rst:-1 +#: ../../source/drivers/vector/s57.rst:-1 +#: ../../source/drivers/vector/sdts.rst:-1 +#: ../../source/drivers/vector/selafin.rst:-1 +#: ../../source/drivers/vector/shapefile.rst:-1 +#: ../../source/drivers/vector/sosi.rst:-1 +#: ../../source/drivers/vector/sqlite.rst:-1 +#: ../../source/drivers/vector/svg.rst:-1 +#: ../../source/drivers/vector/sxf.rst:-1 +#: ../../source/drivers/vector/tiger.rst:-1 +#: ../../source/drivers/vector/tiledb.rst:-1 +#: ../../source/drivers/vector/topojson.rst:-1 +#: ../../source/drivers/vector/vdv.rst:-1 +#: ../../source/drivers/vector/vfk.rst:-1 +#: ../../source/drivers/vector/vrt.rst:-1 +#: ../../source/drivers/vector/wasp.rst:-1 +#: ../../source/drivers/vector/wfs.rst:-1 +#: ../../source/drivers/vector/xls.rst:-1 +#: ../../source/drivers/vector/xlsx.rst:-1 +#: ../../source/drivers/vector/xodr.rst:-1 +msgid "Driver short name" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:7 +msgid "RST" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:11 +msgid "" +"This format is basically a raw one. There is just one band per files, " +"except in the RGB24 data type where the Red, Green and Blue bands are " +"store interleaved by pixels in the order Blue, Green and Red. The others " +"data type are unsigned 8 bits integer with values from 0 to 255 or signed" +" 16 bits integer with values from -32.768 to 32.767 or 32 bits single " +"precision floating point.32 bits. The description of the file is stored " +"in a accompanying text file, extension RDC." +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:19 +msgid "" +"The RDC image description file doesn't include color table, or detailed " +"geographic referencing information. The color table if present can be " +"obtained by another accompanying file using the same base name as the RST" +" file and SMP as extension." +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:24 +msgid "" +"For geographical referencing identification, the RDC file contains " +"information that points to a file that holds the geographic reference " +"details. Those files uses extension REF and  resides in the same folder " +"as the RST image or more likely in the Idrisi installation folders." +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:29 +#: ../../source/drivers/vector/idrisi.rst:18 +msgid "" +"Therefore the presence or absence of the Idrisi software in the running " +"operation system will determine the way that this driver will work. By " +"setting the environment variable IDRISIDIR pointing to the Idrisi main " +"installation folder will enable GDAL to find more detailed information " +"about geographical reference and projection in the REF files." +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:35 +msgid "" +"Note that the RST driver recognizes the name convention used in Idrisi " +"for UTM and State Plane geographic reference so it doesn't need to access" +" the REF files. That is the case for RDC file that specify \"utm-30n\" or" +" \"spc87ma1\" in the \"ref. system\" field. Note that exporting to RST in" +" any other geographical reference system will generate a suggested REF " +"content in the comment section of the RDC file." +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:42 +msgid "\".rst\" the raw image file" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:43 +msgid "\".rdc\" the description file" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:44 +msgid "\".smp\" the color table file" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:45 +msgid "\".ref\" the geographical reference file" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:48 +#: ../../source/drivers/raster/aaigrid.rst:65 +#: ../../source/drivers/raster/ace2.rst:23 +#: ../../source/drivers/raster/adrg.rst:33 +#: ../../source/drivers/raster/aig.rst:31 +#: ../../source/drivers/raster/airsar.rst:49 +#: ../../source/drivers/raster/bag.rst:33 +#: ../../source/drivers/raster/basisu.rst:35 +#: ../../source/drivers/raster/blx.rst:25 +#: ../../source/drivers/raster/bmp.rst:27 +#: ../../source/drivers/raster/bsb.rst:32 ../../source/drivers/raster/bt.rst:33 +#: ../../source/drivers/raster/byn.rst:44 +#: ../../source/drivers/raster/cad.rst:24 +#: ../../source/drivers/raster/cals.rst:28 +#: ../../source/drivers/raster/ceos.rst:25 +#: ../../source/drivers/raster/cog.rst:24 +#: ../../source/drivers/raster/cosar.rst:27 +#: ../../source/drivers/raster/cpg.rst:14 +#: ../../source/drivers/raster/ctable2.rst:14 +#: ../../source/drivers/raster/ctg.rst:38 +#: ../../source/drivers/raster/daas.rst:26 +#: ../../source/drivers/raster/dds.rst:34 +#: ../../source/drivers/raster/dimap.rst:30 +#: ../../source/drivers/raster/dipex.rst:14 +#: ../../source/drivers/raster/doq1.rst:18 +#: ../../source/drivers/raster/doq2.rst:24 +#: ../../source/drivers/raster/dted.rst:17 +#: ../../source/drivers/raster/ecrgtoc.rst:29 +#: ../../source/drivers/raster/ecw.rst:17 +#: ../../source/drivers/raster/eedai.rst:17 +#: ../../source/drivers/raster/ehdr.rst:46 +#: ../../source/drivers/raster/eir.rst:25 +#: ../../source/drivers/raster/elas.rst:16 +#: ../../source/drivers/raster/envi.rst:53 +#: ../../source/drivers/raster/ers.rst:22 +#: ../../source/drivers/raster/esat.rst:33 +#: ../../source/drivers/raster/esric.rst:14 +#: ../../source/drivers/raster/exr.rst:105 +#: ../../source/drivers/raster/fast.rst:28 +#: ../../source/drivers/raster/fit.rst:14 +#: ../../source/drivers/raster/fits.rst:366 +#: ../../source/drivers/raster/genbin.rst:32 +#: ../../source/drivers/raster/georaster.rst:53 +#: ../../source/drivers/raster/gff.rst:30 +#: ../../source/drivers/raster/gif.rst:26 +#: ../../source/drivers/raster/gpkg.rst:50 +#: ../../source/drivers/raster/grassasciigrid.rst:25 +#: ../../source/drivers/raster/grib.rst:85 +#: ../../source/drivers/raster/gs7bg.rst:19 +#: ../../source/drivers/raster/gsag.rst:20 +#: ../../source/drivers/raster/gsbg.rst:23 +#: ../../source/drivers/raster/gsc.rst:14 +#: ../../source/drivers/raster/gta.rst:19 +#: ../../source/drivers/raster/gtiff.rst:29 +#: ../../source/drivers/raster/gxf.rst:26 +#: ../../source/drivers/raster/hdf4.rst:24 +#: ../../source/drivers/raster/hdf5.rst:20 +#: ../../source/drivers/raster/heif.rst:30 +#: ../../source/drivers/raster/hf2.rst:25 +#: ../../source/drivers/raster/hfa.rst:30 +#: ../../source/drivers/raster/ilwis.rst:38 +#: ../../source/drivers/raster/iris.rst:33 +#: ../../source/drivers/raster/isce.rst:30 +#: ../../source/drivers/raster/isg.rst:22 +#: ../../source/drivers/raster/isis2.rst:29 +#: ../../source/drivers/raster/isis3.rst:35 +#: ../../source/drivers/raster/jdem.rst:27 +#: ../../source/drivers/raster/jp2ecw.rst:22 +#: ../../source/drivers/raster/jp2kak.rst:50 +#: ../../source/drivers/raster/jp2lura.rst:20 +#: ../../source/drivers/raster/jp2mrsid.rst:18 +#: ../../source/drivers/raster/jp2openjpeg.rst:31 +#: ../../source/drivers/raster/jpeg.rst:67 +#: ../../source/drivers/raster/jpegxl.rst:36 +#: ../../source/drivers/raster/jpipkak.rst:17 +#: ../../source/drivers/raster/kea.rst:36 +#: ../../source/drivers/raster/kmlsuperoverlay.rst:15 +#: ../../source/drivers/raster/kro.rst:24 +#: ../../source/drivers/raster/ktx2.rst:36 +#: ../../source/drivers/raster/l1b.rst:18 +#: ../../source/drivers/raster/lan.rst:29 +#: ../../source/drivers/raster/lcp.rst:38 +#: ../../source/drivers/raster/leveller.rst:25 +#: ../../source/drivers/raster/loslas.rst:17 +#: ../../source/drivers/raster/map.rst:14 +#: ../../source/drivers/raster/marfa.rst:21 +#: ../../source/drivers/raster/mbtiles.rst:53 +#: ../../source/drivers/raster/mem.rst:85 +#: ../../source/drivers/raster/mff.rst:37 +#: ../../source/drivers/raster/mff2.rst:39 +#: ../../source/drivers/raster/mrsid.rst:30 +#: ../../source/drivers/raster/msg.rst:31 +#: ../../source/drivers/raster/msgn.rst:28 +#: ../../source/drivers/raster/ndf.rst:28 +#: ../../source/drivers/raster/netcdf.rst:22 +#: ../../source/drivers/raster/ngsgeoid.rst:15 +#: ../../source/drivers/raster/ngw.rst:36 +#: ../../source/drivers/raster/nitf.rst:52 +#: ../../source/drivers/raster/noaa_b.rst:17 +#: ../../source/drivers/raster/nsidcbin.rst:36 +#: ../../source/drivers/raster/ntv2.rst:14 +#: ../../source/drivers/raster/ogcapi.rst:25 +#: ../../source/drivers/raster/openfilegdb.rst:32 +#: ../../source/drivers/raster/ozi.rst:17 +#: ../../source/drivers/raster/palsar.rst:40 +#: ../../source/drivers/raster/paux.rst:38 +#: ../../source/drivers/raster/pcidsk.rst:58 +#: ../../source/drivers/raster/pcraster.rst:63 +#: ../../source/drivers/raster/pdf.rst:28 +#: ../../source/drivers/raster/pds.rst:33 +#: ../../source/drivers/raster/pds4.rst:36 +#: ../../source/drivers/raster/plmosaic.rst:23 +#: ../../source/drivers/raster/png.rst:40 +#: ../../source/drivers/raster/pnm.rst:33 +#: ../../source/drivers/raster/postgisraster.rst:22 +#: ../../source/drivers/raster/prf.rst:35 ../../source/drivers/raster/r.rst:22 +#: ../../source/drivers/raster/rasterlite.rst:37 +#: ../../source/drivers/raster/rasterlite2.rst:34 +#: ../../source/drivers/raster/rdb.rst:18 +#: ../../source/drivers/raster/rik.rst:21 +#: ../../source/drivers/raster/rmf.rst:22 +#: ../../source/drivers/raster/roi_pac.rst:27 +#: ../../source/drivers/raster/rpftoc.rst:63 +#: ../../source/drivers/raster/rraster.rst:51 +#: ../../source/drivers/raster/rs2.rst:34 +#: ../../source/drivers/raster/s102.rst:29 +#: ../../source/drivers/raster/s104.rst:30 +#: ../../source/drivers/raster/s111.rst:34 +#: ../../source/drivers/raster/safe.rst:33 +#: ../../source/drivers/raster/sar_ceos.rst:68 +#: ../../source/drivers/raster/sdat.rst:35 +#: ../../source/drivers/raster/sdts.rst:26 +#: ../../source/drivers/raster/sentinel2.rst:47 +#: ../../source/drivers/raster/sgi.rst:31 +#: ../../source/drivers/raster/sigdem.rst:26 +#: ../../source/drivers/raster/snodas.rst:21 +#: ../../source/drivers/raster/srp.rst:29 +#: ../../source/drivers/raster/srtmhgt.rst:34 +#: ../../source/drivers/raster/stacit.rst:101 +#: ../../source/drivers/raster/stacta.rst:85 +#: ../../source/drivers/raster/terragen.rst:20 +#: ../../source/drivers/raster/tga.rst:26 +#: ../../source/drivers/raster/til.rst:14 +#: ../../source/drivers/raster/tiledb.rst:19 +#: ../../source/drivers/raster/tsx.rst:15 +#: ../../source/drivers/raster/usgsdem.rst:34 +#: ../../source/drivers/raster/vicar.rst:23 +#: ../../source/drivers/raster/vrt.rst:2154 +#: ../../source/drivers/raster/wcs.rst:52 +#: ../../source/drivers/raster/webp.rst:32 +#: ../../source/drivers/raster/wms.rst:15 +#: ../../source/drivers/raster/wmts.rst:18 +#: ../../source/drivers/raster/xpm.rst:25 +#: ../../source/drivers/raster/xyz.rst:94 +#: ../../source/drivers/raster/zarr.rst:32 +#: ../../source/drivers/raster/zmap.rst:32 +#: ../../source/drivers/vector/amigocloud.rst:19 +#: ../../source/drivers/vector/arrow.rst:44 +#: ../../source/drivers/vector/avcbin.rst:53 +#: ../../source/drivers/vector/avce00.rst:46 +#: ../../source/drivers/vector/cad.rst:27 +#: ../../source/drivers/vector/carto.rst:17 +#: ../../source/drivers/vector/csv.rst:70 +#: ../../source/drivers/vector/csw.rst:19 +#: ../../source/drivers/vector/dgn.rst:33 +#: ../../source/drivers/vector/dgnv8.rst:31 +#: ../../source/drivers/vector/dxf.rst:19 +#: ../../source/drivers/vector/edigeo.rst:32 +#: ../../source/drivers/vector/eeda.rst:16 +#: ../../source/drivers/vector/elasticsearch.rst:21 +#: ../../source/drivers/vector/esrijson.rst:33 +#: ../../source/drivers/vector/filegdb.rst:19 +#: ../../source/drivers/vector/flatgeobuf.rst:18 +#: ../../source/drivers/vector/geoconcept.rst:21 +#: ../../source/drivers/vector/geojson.rst:30 +#: ../../source/drivers/vector/geojsonseq.rst:28 +#: ../../source/drivers/vector/georss.rst:41 +#: ../../source/drivers/vector/gml.rst:27 +#: ../../source/drivers/vector/gmlas.rst:25 +#: ../../source/drivers/vector/gmt.rst:22 +#: ../../source/drivers/vector/gpkg.rst:36 +#: ../../source/drivers/vector/gpsbabel.rst:17 +#: ../../source/drivers/vector/gpx.rst:43 +#: ../../source/drivers/vector/gtfs.rst:38 +#: ../../source/drivers/vector/hana.rst:14 +#: ../../source/drivers/vector/idb.rst:33 +#: ../../source/drivers/vector/idrisi.rst:34 +#: ../../source/drivers/vector/ili.rst:38 +#: ../../source/drivers/vector/jml.rst:26 +#: ../../source/drivers/vector/jsonfg.rst:33 +#: ../../source/drivers/vector/kml.rst:22 +#: ../../source/drivers/vector/libkml.rst:32 +#: ../../source/drivers/vector/lvbag.rst:60 +#: ../../source/drivers/vector/mapml.rst:25 +#: ../../source/drivers/vector/memory.rst:25 +#: ../../source/drivers/vector/miramon.rst:41 +#: ../../source/drivers/vector/mitab.rst:34 +#: ../../source/drivers/vector/mongodbv3.rst:21 +#: ../../source/drivers/vector/mssqlspatial.rst:15 +#: ../../source/drivers/vector/mvt.rst:55 +#: ../../source/drivers/vector/mysql.rst:37 +#: ../../source/drivers/vector/nas.rst:60 +#: ../../source/drivers/vector/netcdf.rst:28 +#: ../../source/drivers/vector/ngw.rst:36 +#: ../../source/drivers/vector/ntf.rst:25 +#: ../../source/drivers/vector/oapif.rst:22 +#: ../../source/drivers/vector/oci.rst:48 +#: ../../source/drivers/vector/odbc.rst:78 +#: ../../source/drivers/vector/ods.rst:28 +#: ../../source/drivers/vector/ogdi.rst:52 +#: ../../source/drivers/vector/openfilegdb.rst:29 +#: ../../source/drivers/vector/osm.rst:31 +#: ../../source/drivers/vector/parquet.rst:23 +#: ../../source/drivers/vector/pdf.rst:15 +#: ../../source/drivers/vector/pds.rst:29 ../../source/drivers/vector/pg.rst:25 +#: ../../source/drivers/vector/pgdump.rst:23 +#: ../../source/drivers/vector/pgeo.rst:83 +#: ../../source/drivers/vector/plscenes_data_v1.rst:14 +#: ../../source/drivers/vector/pmtiles.rst:39 +#: ../../source/drivers/vector/s57.rst:34 +#: ../../source/drivers/vector/sdts.rst:31 +#: ../../source/drivers/vector/selafin.rst:33 +#: ../../source/drivers/vector/shapefile.rst:57 +#: ../../source/drivers/vector/sqlite.rst:61 +#: ../../source/drivers/vector/svg.rst:25 +#: ../../source/drivers/vector/sxf.rst:52 +#: ../../source/drivers/vector/tiger.rst:69 +#: ../../source/drivers/vector/tiledb.rst:19 +#: ../../source/drivers/vector/topojson.rst:17 +#: ../../source/drivers/vector/vdv.rst:32 +#: ../../source/drivers/vector/vfk.rst:21 +#: ../../source/drivers/vector/vrt.rst:21 +#: ../../source/drivers/vector/wasp.rst:14 +#: ../../source/drivers/vector/wfs.rst:22 +#: ../../source/drivers/vector/xlsx.rst:36 +#: ../../source/drivers/vector/xodr.rst:17 +msgid "Driver capabilities" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:59 +#: ../../source/drivers/raster/airsar.rst:54 +#: ../../source/drivers/raster/bag.rst:472 +#: ../../source/drivers/raster/bmp.rst:50 +#: ../../source/drivers/raster/byn.rst:78 +#: ../../source/drivers/raster/cals.rst:71 +#: ../../source/drivers/raster/cog.rst:612 +#: ../../source/drivers/raster/cosar.rst:32 +#: ../../source/drivers/raster/dted.rst:116 +#: ../../source/drivers/raster/ecrgtoc.rst:37 +#: ../../source/drivers/raster/ecw.rst:294 +#: ../../source/drivers/raster/eedai.rst:178 +#: ../../source/drivers/raster/ehdr.rst:57 +#: ../../source/drivers/raster/elas.rst:27 +#: ../../source/drivers/raster/ers.rst:65 +#: ../../source/drivers/raster/esric.rst:162 +#: ../../source/drivers/raster/fast.rst:118 +#: ../../source/drivers/raster/gif.rst:64 +#: ../../source/drivers/raster/gpkg.rst:815 +#: ../../source/drivers/raster/grass.rst:18 +#: ../../source/drivers/raster/gta.rst:39 +#: ../../source/drivers/raster/gtiff.rst:1202 +#: ../../source/drivers/raster/hdf4.rst:271 +#: ../../source/drivers/raster/hdf5.rst:238 +#: ../../source/drivers/raster/hfa.rst:194 +#: ../../source/drivers/raster/isis2.rst:67 +#: ../../source/drivers/raster/isis3.rst:350 +#: ../../source/drivers/raster/jp2ecw.rst:372 +#: ../../source/drivers/raster/jp2kak.rst:288 +#: ../../source/drivers/raster/jp2lura.rst:389 +#: ../../source/drivers/raster/jp2mrsid.rst:127 +#: ../../source/drivers/raster/jp2openjpeg.rst:667 +#: ../../source/drivers/raster/jpeg.rst:479 +#: ../../source/drivers/raster/jpegxl.rst:193 +#: ../../source/drivers/raster/jpipkak.rst:255 +#: ../../source/drivers/raster/kea.rst:132 +#: ../../source/drivers/raster/l1b.rst:129 +#: ../../source/drivers/raster/mbtiles.rst:646 +#: ../../source/drivers/raster/msg.rst:205 +#: ../../source/drivers/raster/palsar.rst:47 +#: ../../source/drivers/raster/pds.rst:119 +#: ../../source/drivers/raster/plmosaic.rst:215 +#: ../../source/drivers/raster/postgisraster.rst:130 +#: ../../source/drivers/raster/prf.rst:40 +#: ../../source/drivers/raster/rasterlite.rst:290 +#: ../../source/drivers/raster/rasterlite2.rst:192 +#: ../../source/drivers/raster/rraster.rst:62 +#: ../../source/drivers/raster/rs2.rst:68 +#: ../../source/drivers/raster/s102.rst:76 +#: ../../source/drivers/raster/s104.rst:55 +#: ../../source/drivers/raster/s111.rst:59 +#: ../../source/drivers/raster/safe.rst:146 +#: ../../source/drivers/raster/sentinel2.rst:455 +#: ../../source/drivers/raster/stacit.rst:124 +#: ../../source/drivers/raster/stacta.rst:90 +#: ../../source/drivers/raster/terragen.rst:72 +#: ../../source/drivers/raster/tiledb.rst:189 +#: ../../source/drivers/raster/vicar.rst:249 +#: ../../source/drivers/raster/wcs.rst:315 +#: ../../source/drivers/raster/webp.rst:72 +#: ../../source/drivers/raster/wms.rst:529 +#: ../../source/drivers/raster/wmts.rst:469 +#: ../../source/drivers/vector/amigocloud.rst:213 +#: ../../source/drivers/vector/avcbin.rst:60 +#: ../../source/drivers/vector/avce00.rst:53 +#: ../../source/drivers/vector/cad.rst:48 +#: ../../source/drivers/vector/carto.rst:235 +#: ../../source/drivers/vector/csw.rst:126 +#: ../../source/drivers/vector/edigeo.rst:81 +#: ../../source/drivers/vector/elasticsearch.rst:763 +#: ../../source/drivers/vector/esrijson.rst:83 +#: ../../source/drivers/vector/flatgeobuf.rst:122 +#: ../../source/drivers/vector/geoconcept.rst:286 +#: ../../source/drivers/vector/geojson.rst:550 +#: ../../source/drivers/vector/geojsonseq.rst:143 +#: ../../source/drivers/vector/georss.rst:309 +#: ../../source/drivers/vector/gml.rst:1365 +#: ../../source/drivers/vector/gmlas.rst:471 +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:351 +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:159 +#: ../../source/drivers/vector/gpkg.rst:809 +#: ../../source/drivers/vector/gpsbabel.rst:126 +#: ../../source/drivers/vector/gpx.rst:466 +#: ../../source/drivers/vector/grass.rst:18 +#: ../../source/drivers/vector/hana.rst:352 +#: ../../source/drivers/vector/jml.rst:89 +#: ../../source/drivers/vector/jsonfg.rst:234 +#: ../../source/drivers/vector/kml.rst:170 +#: ../../source/drivers/vector/lvbag.rst:106 +#: ../../source/drivers/vector/miramon.rst:369 +#: ../../source/drivers/vector/mitab.rst:204 +#: ../../source/drivers/vector/mongodbv3.rst:332 +#: ../../source/drivers/vector/ntf.rst:32 +#: ../../source/drivers/vector/oapif.rst:277 +#: ../../source/drivers/vector/oda.rst:200 +#: ../../source/drivers/vector/odbc.rst:107 +#: ../../source/drivers/vector/ogdi.rst:112 +#: ../../source/drivers/vector/osm.rst:268 +#: ../../source/drivers/vector/pdf.rst:104 +#: ../../source/drivers/vector/pds.rst:34 +#: ../../source/drivers/vector/pg.rst:583 +#: ../../source/drivers/vector/pg_advanced.rst:357 +#: ../../source/drivers/vector/pgdump.rst:283 +#: ../../source/drivers/vector/plscenes.rst:21 +#: ../../source/drivers/vector/plscenes_data_v1.rst:250 +#: ../../source/drivers/vector/pmtiles.rst:354 +#: ../../source/drivers/vector/s57.rst:371 +#: ../../source/drivers/vector/sdts.rst:38 +#: ../../source/drivers/vector/shapefile.rst:484 +#: ../../source/drivers/vector/svg.rst:32 +#: ../../source/drivers/vector/sxf.rst:59 +#: ../../source/drivers/vector/tiger.rst:242 +#: ../../source/drivers/vector/tiledb.rst:238 +#: ../../source/drivers/vector/topojson.rst:43 +#: ../../source/drivers/vector/wfs.rst:425 +#: ../../source/drivers/vector/xls.rst:45 +msgid "See Also" +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:61 +msgid "Implemented as :source_file:`frmts/idrisi/IdrisiDataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/Idrisi.rst:62 +msgid "`www.idrisi.com <http://www.idrisi.com>`__" +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:5 +msgid "AAIGrid -- Arc/Info ASCII Grid" +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:7 +msgid "AAIGrid" +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:11 +msgid "" +"Supported for read and write access, including reading of an affine " +"georeferencing transform and some projections. This format is the ASCII " +"interchange format for Arc/Info Grid, and takes the form of an ASCII " +"file, plus sometimes an associated .prj file. It is normally produced " +"with the Arc/Info ASCIIGRID command." +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:17 +msgid "" +"The projections support (read if a \\*.prj file is available) is quite " +"limited. Additional sample .prj files may be sent to the maintainer, " +"warmerdam@pobox.com." +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:21 +msgid "" +"The NODATA value for the grid read is also preserved when available in " +"the same format as the band data." +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:24 +msgid "The following configuration options are supported:" +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:59 +msgid "" +"The :ref:`raster.aig` driver is also available for Arc/Info Binary Grid " +"format." +msgstr "" + +#: ../../source/drivers/raster/aaigrid.rst:62 +#: ../../source/drivers/raster/grassasciigrid.rst:22 +#: ../../source/drivers/raster/isg.rst:19 +msgid "NOTE: Implemented as :source_file:`frmts/aaigrid/aaigriddataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ace2.rst:5 +msgid "ACE2 -- ACE2" +msgstr "" + +#: ../../source/drivers/raster/ace2.rst:7 +#: ../../source/drivers/raster/driver_summary.rst:24 +msgid "ACE2" +msgstr "" + +#: ../../source/drivers/raster/ace2.rst:11 +msgid "" +"This is a convenience driver to read ACE2 DEMs. Those files contain raw " +"binary data. The georeferencing is entirely determined by the filename. " +"Quality, source and confidence layers are of Int16 type, whereas " +"elevation data is returned as Float32." +msgstr "" + +#: ../../source/drivers/raster/ace2.rst:16 +msgid "" +"`ACE2 product overview " +"<http://tethys.eaprs.cse.dmu.ac.uk/ACE2/shared/overview>`__" +msgstr "" + +#: ../../source/drivers/raster/ace2.rst:19 +msgid "NOTE: Implemented as :source_file:`frmts/raw/ace2dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:5 +msgid "ADRG -- ADRG/ARC Digitized Raster Graphics (.gen/.thf)" +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:7 +msgid "ADRG" +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:11 +msgid "" +"Supported by GDAL for read access. Creation is possible, but it must be " +"considered as experimental and a means of testing read access (although " +"files created by the driver can be read successfully on another GIS " +"software)" +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:16 +msgid "" +"An ADRG dataset is made of several files. The file recognised by GDAL is " +"the General Information File (.GEN). GDAL will also need the image file " +"(.IMG), where the actual data is." +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:20 +msgid "" +"The Transmission Header File (.THF) can also be used as an input to GDAL." +" If the THF references more than one image, GDAL will report the images " +"it is composed of as subdatasets. If the THF references just one image, " +"GDAL will open it directly." +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:25 +msgid "" +"Overviews, legends and insets are not used. Polar zones (ARC zone 9 and " +"18) are not supported (due to the lack of test data)." +msgstr "" + +#: ../../source/drivers/raster/adrg.rst:28 +msgid "" +"See also : the `ADRG specification (MIL-A-89007) <http://earth-" +"info.nga.mil/publications/specs/printed/89007/89007_ADRG.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/aig.rst:5 +msgid "AIG -- Arc/Info Binary Grid" +msgstr "" + +#: ../../source/drivers/raster/aig.rst:7 +msgid "AIG" +msgstr "" + +#: ../../source/drivers/raster/aig.rst:11 +msgid "" +"Supported by GDAL for read access. This format is the internal binary " +"format for Arc/Info Grid, and takes the form of a coverage level " +"directory in an Arc/Info database. To open the coverage select the " +"coverage directory, or an .adf file (such as hdr.adf) from within it. If " +"the directory does not contain file(s) with names like w001001.adf then " +"it is not a grid coverage." +msgstr "" + +#: ../../source/drivers/raster/aig.rst:18 +msgid "" +"Support includes reading of an affine georeferencing transform, some " +"projections, and a color table (.clr) if available." +msgstr "" + +#: ../../source/drivers/raster/aig.rst:21 +msgid "" +"This driver is implemented based on a reverse engineering of the format. " +"See the :ref:`raster.arcinfo_grid_format` for more details." +msgstr "" + +#: ../../source/drivers/raster/aig.rst:24 +msgid "" +"The projections support (read if a prj.adf file is available) is quite " +"limited. Additional sample prj.adf files may be sent to the maintainer, " +"warmerdam@pobox.com." +msgstr "" + +#: ../../source/drivers/raster/aig.rst:28 +msgid "NOTE: Implemented as :source_file:`frmts/aigrid/aigdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:5 +msgid "AIRSAR -- AIRSAR Polarimetric Format" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:7 +msgid "AIRSAR" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:11 +msgid "" +"Most variants of the AIRSAR Polarimetric Format produced by the AIRSAR " +"Integrated Processor are supported for reading by GDAL. AIRSAR products " +"normally include various associated data files, but only the imagery data" +" themselves is supported. Normally these are named *mission*\\ \\_l.dat " +"(L-Band) or *mission*\\ \\_c.dat (C-Band)." +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:17 +msgid "" +"AIRSAR format contains a polarimetric image in compressed stokes matrix " +"form. Internally GDAL decompresses the data into a stokes matrix, and " +"then converts that form into a covariance matrix. The returned six bands " +"are the six values needed to define the 3x3 Hermitian covariance matrix. " +"The convention used to represent the covariance matrix in terms of the " +"scattering matrix elements HH, HV (=VH), and VV is indicated below. Note " +"that the non-diagonal elements of the matrix are complex values, while " +"the diagonal values are real (though represented as complex bands)." +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:26 +#: ../../source/drivers/raster/sar_ceos.rst:56 +msgid "Band 1: Covariance_11 (Float32) = HH*conj(HH)" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:27 +#: ../../source/drivers/raster/sar_ceos.rst:57 +msgid "Band 2: Covariance_12 (CFloat32) = sqrt(2)*HH*conj(HV)" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:28 +#: ../../source/drivers/raster/sar_ceos.rst:58 +msgid "Band 3: Covariance_13 (CFloat32) = HH*conj(VV)" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:29 +#: ../../source/drivers/raster/sar_ceos.rst:59 +msgid "Band 4: Covariance_22 (Float32) = 2*HV*conj(HV)" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:30 +#: ../../source/drivers/raster/sar_ceos.rst:60 +msgid "Band 5: Covariance_23 (CFloat32) = sqrt(2)*HV*conj(VV)" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:31 +#: ../../source/drivers/raster/sar_ceos.rst:61 +msgid "Band 6: Covariance_33 (Float32) = VV*conj(VV)" +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:33 +msgid "" +"The identities of the bands are also reflected in metadata and in the " +"band descriptions." +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:36 +msgid "" +"The AIRSAR product format includes (potentially) several headers of " +"information. This information is captured and represented as metadata on " +"the file as a whole. Information items from the main header are prefixed " +"with \"MH\\_\", items from the parameter header are prefixed with " +"\"PH\\_\" and information from the calibration header are prefixed with " +"\"CH\\_\". The metadata item names are derived automatically from the " +"names of the fields within the header itself." +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:44 +msgid "" +"No effort is made to read files associated with the AIRSAR product such " +"as *mission*\\ \\_l.mocomp, *mission*\\ \\_meta.airsar or *mission*\\ " +"\\_meta.podaac." +msgstr "" + +#: ../../source/drivers/raster/airsar.rst:56 +msgid "" +"`AIRSAR Data Format " +"<http://airsar.jpl.nasa.gov/documents/dataformat.htm>`__" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:5 +msgid "Arc/Info Binary Grid Format" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:7 +msgid "" +"*by* `Frank Warmerdam <http://pobox.com/~warmerdam>`__ " +"(warmerdam@pobox.com)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:10 +msgid "" +"The Arc/Info Binary Grid format is the internal working format of the " +"Arc/Info Grid product. It is also usable and creatable within the spatial" +" analyst component of ArcView. It is a tiled (blocked) format with run " +"length compression capable of holding raster data of up to 4 byte " +"integers or 4 byte floating data." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:16 +msgid "" +"This format should not be confused with the Arc/Info ASCII Grid format " +"which is the interchange format for grids. Files can be converted between" +" binary and ASCII format with the GRIDASCII and ASCIIGRID commands in " +"Arc/Info. This format is also different than the flat binary raster " +"output of the GRIDFLOAT command. The Arc/Info binary float, and ASCII " +"formats are also accessible from within ArcView." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:23 +msgid "" +"This format should also not be confused with what I know as ESRI BIL " +"format. This is really a standard ESRI way of creating a header file " +"(.HDR) describing the data layout a binary raster file containing raster " +"data." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:29 +msgid "Version" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:31 +msgid "" +"I am not sure yet how the versions work for grid files. I have been " +"working primarily with grid files generated by ArcView 3.x, and its " +"associated gridio API. The hdr.adf files I have examined start with the " +"string **GRID1.2** for what that's worth. Certainly the file naming " +"conventions seem to follow the Arc/Info 7.x conventions rather than that " +"of earlier versions." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:39 +msgid "File Set" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:41 +msgid "" +"A grid coverage actually consists of a number of files. A grid normally " +"lives in its own directory named after the grid. For instance, the grid " +"**nwgrd1** lives in the directory **nwgrd1**, and has the following " +"component files:" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:55 +msgid "" +"Sometimes datasets will also include a prj.adf files containing the " +"projection definition in the usual ESRI format. Grids also normally have " +"associated tables in the info directory. This is beyond the scope of my " +"discussion for now." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:60 +msgid "The files have the following roles:" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:62 +msgid "" +"`dblbnd.adf <#dblbnd>`__: Contains the bounds (LLX, LLY, URX, URY) of the" +" portion of utilized portion of the grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:64 +msgid "" +"`hdr.adf <#hdr.adf>`__: This is the header, and contains information on " +"the tile sizes, and number of tiles in the dataset. It also contains " +"assorted other information I have yet to identify." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:67 +msgid "" +"`sta.adf <#sta>`__: This contains raster statistics. In particular, the " +"raster min, max, mean and standard deviation." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:69 +msgid "" +"**vat.adf**: This relates to the value attribute table. This is the table" +" corresponding integer raster values with a set of attributes. I presume " +"it is really just a pointer into info in a manner similar to the pat.adf " +"file in a vector coverage, but I haven't investigated yet." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:74 +msgid "" +"`w001001.adf <#w001001>`__: This is the file containing the actual raster" +" data." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:76 +msgid "" +"`w001001x.adf <#w001001x>`__: This is an index file containing pointers " +"to each of the tiles in the w001001.adf raster file." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:82 +msgid "dblbnd.adf - Georef Bounds" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:84 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:173 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:232 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:316 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:604 +msgid "Fields:" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:86 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:175 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:234 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:318 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:606 +msgid "Start Byte" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:88 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:177 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:236 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:320 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:608 +msgid "# of Bytes" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:90 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:179 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:238 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:322 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:610 +#: ../../source/drivers/vector/csv.rst:79 +#: ../../source/drivers/vector/selafin.rst:58 +msgid "Format" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:92 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:240 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:324 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:612 +msgid "Name" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:94 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:181 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:242 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:326 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:614 +#: ../../source/drivers/raster/lcp.rst:247 +#: ../../source/drivers/raster/vrt.rst:1109 +#: ../../source/drivers/vector/geopackage_aspatial.rst:96 +msgid "Description" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:96 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:183 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:244 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:328 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:616 +#: ../../source/drivers/raster/lcp.rst:171 +msgid "0" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:98 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:107 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:109 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:120 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:131 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:185 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:190 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:246 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:254 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:256 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:266 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:276 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:330 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:337 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:618 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:626 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:628 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:668 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:679 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:690 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:700 +#: ../../source/drivers/raster/lcp.rst:173 +#: ../../source/drivers/raster/lcp.rst:174 +#: ../../source/drivers/raster/lcp.rst:175 +#: ../../source/drivers/raster/lcp.rst:176 +#: ../../source/drivers/raster/lcp.rst:177 +#: ../../source/drivers/raster/lcp.rst:220 +#: ../../source/drivers/raster/lcp.rst:221 +#: ../../source/drivers/raster/lcp.rst:222 +#: ../../source/drivers/raster/lcp.rst:223 +#: ../../source/drivers/raster/lcp.rst:225 +#: ../../source/drivers/raster/lcp.rst:226 +msgid "8" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:100 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:111 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:122 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:133 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:248 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:258 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:268 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:278 +msgid "MSB double" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:102 +msgid "D_LLX" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:104 +msgid "" +"Lower left X (easting) of the grid. Generally -0.5 for an ungeoreferenced" +" grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:113 +msgid "D_LLY" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:115 +msgid "" +"Lower left Y (northing) of the grid. Generally -0.5 for an " +"ungeoreferenced grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:118 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:192 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:264 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:339 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:636 +msgid "16" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:124 +msgid "D_URX" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:126 +msgid "" +"Upper right X (easting) of the grid. Generally #Pixels-0.5 for an " +"ungeoreferenced grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:129 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:196 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:274 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:343 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:656 +msgid "24" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:135 +msgid "D_URY" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:137 +msgid "" +"Upper right Y (northing) of the grid. Generally #Lines-0.5 for an " +"ungeoreferenced grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:140 +msgid "" +"This file is always 32 bytes long. The bounds apply to the portion of the" +" grid that is in use, not the whole thing." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:146 +msgid "w001001x.adf - Tile Index" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:148 +msgid "This is a binary dump of the first 320 bytes of a w001001x.adf file." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:187 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:334 +msgid "" +"Magic Number (always hex 00 00 27 0A FF FF \\*\\* \\**, usually ending in" +" FC 14, FB F8 or FC 08)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:194 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:209 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:341 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:358 +msgid "zero fill" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:198 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:213 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:221 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:345 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:638 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:648 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:710 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:721 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:732 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:742 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:750 +#: ../../source/drivers/raster/jpeg.rst:357 +#: ../../source/drivers/raster/jpeg.rst:363 +#: ../../source/drivers/raster/jpeg.rst:381 +#: ../../source/drivers/raster/jpeg.rst:412 +#: ../../source/drivers/raster/jpeg.rst:423 +#: ../../source/drivers/raster/lcp.rst:171 +#: ../../source/drivers/raster/lcp.rst:172 +#: ../../source/drivers/raster/lcp.rst:173 +#: ../../source/drivers/raster/lcp.rst:178 +#: ../../source/drivers/raster/lcp.rst:179 +#: ../../source/drivers/raster/lcp.rst:180 +#: ../../source/drivers/raster/lcp.rst:182 +#: ../../source/drivers/raster/lcp.rst:183 +#: ../../source/drivers/raster/lcp.rst:184 +#: ../../source/drivers/raster/lcp.rst:186 +#: ../../source/drivers/raster/lcp.rst:187 +#: ../../source/drivers/raster/lcp.rst:188 +#: ../../source/drivers/raster/lcp.rst:190 +#: ../../source/drivers/raster/lcp.rst:191 +#: ../../source/drivers/raster/lcp.rst:192 +#: ../../source/drivers/raster/lcp.rst:194 +#: ../../source/drivers/raster/lcp.rst:195 +#: ../../source/drivers/raster/lcp.rst:196 +#: ../../source/drivers/raster/lcp.rst:198 +#: ../../source/drivers/raster/lcp.rst:199 +#: ../../source/drivers/raster/lcp.rst:200 +#: ../../source/drivers/raster/lcp.rst:202 +#: ../../source/drivers/raster/lcp.rst:203 +#: ../../source/drivers/raster/lcp.rst:204 +#: ../../source/drivers/raster/lcp.rst:206 +#: ../../source/drivers/raster/lcp.rst:207 +#: ../../source/drivers/raster/lcp.rst:208 +#: ../../source/drivers/raster/lcp.rst:210 +#: ../../source/drivers/raster/lcp.rst:211 +#: ../../source/drivers/raster/lcp.rst:212 +#: ../../source/drivers/raster/lcp.rst:214 +#: ../../source/drivers/raster/lcp.rst:215 +#: ../../source/drivers/raster/lcp.rst:216 +#: ../../source/drivers/raster/lcp.rst:218 +#: ../../source/drivers/raster/lcp.rst:219 +#: ../../source/drivers/raster/lcp.rst:224 +msgid "4" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:200 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:215 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:223 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:347 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:640 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:650 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:712 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:723 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:734 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:744 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:752 +msgid "MSB Int32" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:202 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:351 +msgid "Size of whole file in shorts (multiply by two to get file size in bytes)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:205 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:354 +#: ../../source/drivers/raster/lcp.rst:176 +msgid "28" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:207 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:356 +msgid "72" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:211 +msgid "100 + **t**\\ \\*8" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:217 +msgid "Offset to tile **t** in w001001.adf measured in two byte shorts." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:219 +msgid "104 + **t**\\ \\*8" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:225 +msgid "Size of tile **t** in 2 byte shorts." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:230 +msgid "sta.adf - Raster Statistics" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:250 +msgid "SMin" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:252 +msgid "Minimum value of a raster cell in this grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:260 +msgid "SMax" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:262 +msgid "Maximum value of a raster cell in this grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:270 +msgid "SMean" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:272 +msgid "Mean value of a raster cells in this grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:280 +msgid "SStdDev" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:282 +msgid "Standard deviation of raster cells in this grid." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:284 +msgid "This file is always 32 bytes long." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:289 +msgid "w001001.adf - Raster Data" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:291 +msgid "This is a binary dump of the first 320 bytes of a w001001.adf file." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:332 +msgid "RMagic" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:349 +msgid "RFileSize" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:360 +msgid "100, ..." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:362 +#: ../../source/drivers/raster/jpeg.rst:339 +#: ../../source/drivers/raster/jpeg.rst:391 +#: ../../source/drivers/raster/jpeg.rst:424 +#: ../../source/drivers/raster/jpeg.rst:426 +#: ../../source/drivers/raster/jpeg.rst:432 +#: ../../source/drivers/raster/jpeg.rst:433 +#: ../../source/drivers/raster/jpeg.rst:435 +#: ../../source/drivers/raster/jpeg.rst:437 +#: ../../source/drivers/raster/jpeg.rst:439 +#: ../../source/drivers/raster/jpeg.rst:442 +#: ../../source/drivers/raster/jpeg.rst:444 +#: ../../source/drivers/raster/jpeg.rst:446 +#: ../../source/drivers/raster/jpeg.rst:448 +#: ../../source/drivers/raster/lcp.rst:227 +#: ../../source/drivers/raster/lcp.rst:228 +#: ../../source/drivers/raster/lcp.rst:229 +#: ../../source/drivers/raster/lcp.rst:230 +#: ../../source/drivers/raster/lcp.rst:231 +#: ../../source/drivers/raster/lcp.rst:232 +#: ../../source/drivers/raster/lcp.rst:233 +#: ../../source/drivers/raster/lcp.rst:234 +#: ../../source/drivers/raster/lcp.rst:235 +#: ../../source/drivers/raster/lcp.rst:236 +#: ../../source/drivers/raster/vrt.rst:1111 +#: ../../source/drivers/raster/vrt.rst:1115 +#: ../../source/drivers/raster/vrt.rst:1135 +#: ../../source/drivers/raster/vrt.rst:1139 +#: ../../source/drivers/raster/vrt.rst:1143 +#: ../../source/drivers/raster/vrt.rst:1195 +msgid "2" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:364 +msgid "MSB Int16" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:366 +msgid "RTileSize" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:368 +msgid "" +"Size of this tiles data measured in shorts. This matches the size in the " +"index file, and does not include the tile size itself. The next tile " +"starts **2*n+2** bytes after the start of this tile, where **n** is the " +"value of this field." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:373 +msgid "102, ..." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:375 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:386 +#: ../../source/drivers/raster/fits.rst:73 +#: ../../source/drivers/raster/fits.rst:88 +#: ../../source/drivers/raster/fits.rst:98 +#: ../../source/drivers/raster/fits.rst:103 +#: ../../source/drivers/raster/fits.rst:108 +#: ../../source/drivers/raster/fits.rst:128 +#: ../../source/drivers/raster/fits.rst:133 +#: ../../source/drivers/raster/fits.rst:138 +#: ../../source/drivers/raster/fits.rst:158 +#: ../../source/drivers/raster/fits.rst:163 +#: ../../source/drivers/raster/fits.rst:188 +#: ../../source/drivers/raster/fits.rst:193 +#: ../../source/drivers/raster/fits.rst:208 +#: ../../source/drivers/raster/fits.rst:218 +#: ../../source/drivers/raster/fits.rst:228 +#: ../../source/drivers/raster/jpeg.rst:331 +#: ../../source/drivers/raster/jpeg.rst:332 +#: ../../source/drivers/raster/jpeg.rst:333 +#: ../../source/drivers/raster/jpeg.rst:334 +#: ../../source/drivers/raster/jpeg.rst:342 +#: ../../source/drivers/raster/jpeg.rst:345 +#: ../../source/drivers/raster/jpeg.rst:346 +#: ../../source/drivers/raster/jpeg.rst:347 +#: ../../source/drivers/raster/jpeg.rst:351 +#: ../../source/drivers/raster/jpeg.rst:352 +#: ../../source/drivers/raster/jpeg.rst:353 +#: ../../source/drivers/raster/jpeg.rst:354 +#: ../../source/drivers/raster/jpeg.rst:355 +#: ../../source/drivers/raster/jpeg.rst:356 +#: ../../source/drivers/raster/jpeg.rst:364 +#: ../../source/drivers/raster/jpeg.rst:365 +#: ../../source/drivers/raster/jpeg.rst:366 +#: ../../source/drivers/raster/jpeg.rst:367 +#: ../../source/drivers/raster/jpeg.rst:368 +#: ../../source/drivers/raster/jpeg.rst:369 +#: ../../source/drivers/raster/jpeg.rst:370 +#: ../../source/drivers/raster/jpeg.rst:371 +#: ../../source/drivers/raster/jpeg.rst:372 +#: ../../source/drivers/raster/jpeg.rst:373 +#: ../../source/drivers/raster/jpeg.rst:374 +#: ../../source/drivers/raster/jpeg.rst:382 +#: ../../source/drivers/raster/jpeg.rst:383 +#: ../../source/drivers/raster/jpeg.rst:384 +#: ../../source/drivers/raster/jpeg.rst:386 +#: ../../source/drivers/raster/jpeg.rst:388 +#: ../../source/drivers/raster/jpeg.rst:389 +#: ../../source/drivers/raster/jpeg.rst:390 +#: ../../source/drivers/raster/jpeg.rst:392 +#: ../../source/drivers/raster/jpeg.rst:393 +#: ../../source/drivers/raster/jpeg.rst:394 +#: ../../source/drivers/raster/jpeg.rst:395 +#: ../../source/drivers/raster/jpeg.rst:397 +#: ../../source/drivers/raster/jpeg.rst:398 +#: ../../source/drivers/raster/jpeg.rst:399 +#: ../../source/drivers/raster/jpeg.rst:400 +#: ../../source/drivers/raster/jpeg.rst:401 +#: ../../source/drivers/raster/jpeg.rst:402 +#: ../../source/drivers/raster/jpeg.rst:403 +#: ../../source/drivers/raster/jpeg.rst:404 +#: ../../source/drivers/raster/jpeg.rst:405 +#: ../../source/drivers/raster/jpeg.rst:406 +#: ../../source/drivers/raster/jpeg.rst:408 +#: ../../source/drivers/raster/jpeg.rst:428 +#: ../../source/drivers/raster/jpeg.rst:429 +#: ../../source/drivers/raster/jpeg.rst:434 +#: ../../source/drivers/raster/jpeg.rst:436 +#: ../../source/drivers/raster/jpeg.rst:438 +#: ../../source/drivers/raster/jpeg.rst:440 +#: ../../source/drivers/raster/jpeg.rst:447 +#: ../../source/drivers/raster/jpeg.rst:449 +#: ../../source/drivers/raster/jpeg.rst:453 +#: ../../source/drivers/raster/jpeg.rst:454 +#: ../../source/drivers/raster/vrt.rst:1119 +#: ../../source/drivers/raster/vrt.rst:1123 +#: ../../source/drivers/raster/vrt.rst:1127 +#: ../../source/drivers/raster/vrt.rst:1131 +#: ../../source/drivers/raster/vrt.rst:1147 +#: ../../source/drivers/raster/vrt.rst:1151 +#: ../../source/drivers/raster/vrt.rst:1155 +#: ../../source/drivers/raster/vrt.rst:1167 +#: ../../source/drivers/raster/vrt.rst:1171 +#: ../../source/drivers/raster/vrt.rst:1183 +#: ../../source/drivers/raster/vrt.rst:1191 +#: ../../source/drivers/raster/vrt.rst:1199 +#: ../../source/drivers/raster/vrt.rst:1203 +#: ../../source/drivers/raster/vrt.rst:1207 +msgid "1" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:377 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:388 +#: ../../source/drivers/vector/netcdf.rst:86 +#: ../../source/drivers/vector/netcdf.rst:122 +msgid "byte" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:379 +msgid "RTileType" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:381 +msgid "" +"Tile type code indicating the organization of the following data (integer" +" coverages only)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:384 +msgid "103, ..." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:390 +msgid "RMinSize" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:392 +msgid "" +"Number of bytes following to form the minimum value for the tile (integer" +" coverages only)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:395 +msgid "104, ..." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:397 +msgid "(RMinSize bytes)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:399 +msgid "MSB Int (var size)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:401 +msgid "RMin" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:403 +msgid "" +"The minimum value pixels for this tile. This number is added to the pixel" +" values for each pixel in this tile (integer coverages only). I must " +"stress that if RMinSize is less than 4 this is still a signed quantity. " +"For instance, if RMinSize is 2, the value is 65536 - byte0*256 - byte1 if" +" byte0 is > 127." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:409 +msgid "104+RMinSize, ..." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:411 +msgid "RTileSize*2 - 3 - RMinSize" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:413 +#: ../../source/drivers/raster/jpeg.rst:327 +#: ../../source/drivers/raster/jpeg.rst:328 +#: ../../source/drivers/raster/jpeg.rst:329 +#: ../../source/drivers/raster/jpeg.rst:330 +#: ../../source/drivers/raster/jpeg.rst:336 +#: ../../source/drivers/raster/jpeg.rst:338 +#: ../../source/drivers/raster/jpeg.rst:344 +#: ../../source/drivers/raster/jpeg.rst:348 +#: ../../source/drivers/raster/jpeg.rst:349 +#: ../../source/drivers/raster/jpeg.rst:350 +#: ../../source/drivers/raster/jpeg.rst:375 +#: ../../source/drivers/raster/jpeg.rst:376 +#: ../../source/drivers/raster/jpeg.rst:377 +#: ../../source/drivers/raster/jpeg.rst:378 +#: ../../source/drivers/raster/jpeg.rst:379 +#: ../../source/drivers/raster/jpeg.rst:380 +#: ../../source/drivers/raster/jpeg.rst:387 +#: ../../source/drivers/raster/jpeg.rst:396 +#: ../../source/drivers/raster/jpeg.rst:407 +#: ../../source/drivers/raster/jpeg.rst:410 +#: ../../source/drivers/raster/jpeg.rst:411 +#: ../../source/drivers/raster/jpeg.rst:413 +#: ../../source/drivers/raster/jpeg.rst:414 +#: ../../source/drivers/raster/jpeg.rst:415 +#: ../../source/drivers/raster/jpeg.rst:431 +#: ../../source/drivers/raster/jpeg.rst:441 +#: ../../source/drivers/raster/jpeg.rst:450 +#: ../../source/drivers/raster/jpeg.rst:451 +msgid "variable" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:415 +msgid "RTileData" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:417 +msgid "" +"The data for this tile. Format varies according to RTileType for integer " +"coverages." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:420 +msgid "" +"The fields RTileSize, RTileType, RMinSize, RMin, and RTileData occur in " +"the file for each tile of data present. They are usually packed one after" +" the other, but this isn't necessarily guaranteed. The index file " +"(w001001x.adf) should be used to establish the tile locations. Note that " +"tiles that appear in the index file with a size of zero will appear as " +"just two bytes (zeros) for the RTileSize for that tile." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:428 +msgid "Raster Size" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:430 +msgid "" +"The size of a the grid isn't as easy to deduce as one might expect. The " +"hdr.adf file contains the HTilesPerRow, HTilesPerColumn, HTileXSize, and " +"HTileYSize fields which imply a particular raster space. However, it " +"seems that this is created much larger than necessary to hold the users " +"raster data. I have created 3x1 rasters which resulted in the standard " +"8x512 tiles of 256x4 pixels each." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:437 +msgid "" +"It seems that the user portion of the raster has to be computed based on " +"the georeferenced bounds in the dblbnd.adf file (assumed to be anchored " +"at the top left of the total raster space), and the HPixelSizeX, and " +"HPixelSizeY fields from hdr.adf." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:442 +msgid "**#Pixels = (D_URX - D_LRX) / HPixelSizeX**" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:444 +msgid "**#Lines = (D_URY - D_LRY) / HPixelSizeY**" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:446 +msgid "" +"Based on this number of pixels and lines, it is possible to establish " +"what portion out of the top left of the raster is really *of interest*. " +"All regions outside this appear to empty tiles, or filled with no data " +"markers." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:452 +msgid "RTileType/RTileData" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:454 +msgid "" +"Each tile contains HBlockXSize \\* HBlockYSize pixels of data. For " +"floating point and uncompressed integer files the data is just the tile " +"size (in two bytes) followed by the pixel data as 4 byte MSB order IEEE " +"floating point words. For compressed integer tiles it is necessary to " +"interpret the RTileType to establish the details of the tile " +"organization:" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:462 +msgid "RTileType = 0x00 (constant block)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:464 +msgid "" +"All pixels take the value of the RMin. Data is ignored. It appears there " +"is sometimes a bit of meaningless data (up to four bytes) in the block." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:468 +msgid "RTileType = 0x01 (raw 1bit data)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:470 +msgid "" +"One full tile worth of data pixel values follows the RMin field, with " +"1bit per pixel." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:474 +msgid "RTileType = 0x04 (raw 4bit data)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:476 +msgid "" +"One full tiles worth of data pixel values follows the RMin field, with 4 " +"bits per pixel. The high order four bits of a byte comes before the low " +"order four bits." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:481 +msgid "RTileType = 0x08 (raw byte data)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:483 +msgid "" +"One full tiles worth of data pixel values (one byte per pixel) follows " +"the RMin field." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:487 +msgid "RTileType = 0x10 (raw 16bit data)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:489 +msgid "" +"One full tiles worth of data pixel values follows the RMin field, with 16" +" bits per pixel (MSB)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:493 +msgid "RTileType = 0x20 (raw 32bit data)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:495 +msgid "" +"One full tiles worth of data pixel values follows the RMin field, with 32" +" bits per pixel (MSB)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:499 +msgid "RTileType = 0xCF (16 bit literal runs/nodata runs)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:501 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:513 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:525 +msgid "" +"The data is organized in a series of runs. Each run starts with a marker " +"which should be interpreted as:" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:504 +msgid "" +"**Marker < 128**: The marker is followed by **Marker** pixels of literal " +"data with two MSB bytes per pixel." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:506 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:518 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:530 +msgid "" +"**Marker > 127**: The marker indicates that **256-Marker** pixels of *no " +"data* pixels should be put into the output stream. No data (other than " +"the next marker) follows this marker." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:511 +msgid "RTileType = 0xD7 (literal runs/nodata runs)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:516 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:528 +msgid "" +"**Marker < 128**: The marker is followed by **Marker** pixels of literal " +"data with one byte per pixel." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:523 +msgid "RTileType = 0xDF (RMin runs/nodata runs)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:534 +msgid "" +"This is similar to 0xD7, except that the data size is zero bytes instead " +"of 1, so only RMin values are inserted into the output stream." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:538 +msgid "RTileType = 0xE0 (run length encoded 32bit)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:540 +msgid "" +"The data is organized in a series of runs. Each run starts with a marker " +"which should be interpreted as a **count**. The four bytes following the " +"count should be interpreted as an MSB Int32 **value**. They indicate that" +" **count** pixels of **value** should be inserted into the output stream." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:547 +msgid "RTileType = 0xF0 (run length encoded 16bit)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:549 +msgid "" +"The data is organized in a series of runs. Each run starts with a marker " +"which should be interpreted as a **count**. The two bytes following the " +"count should be interpreted as an MSB Int16 **value**. They indicate that" +" **count** pixels of **value** should be inserted into the output stream." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:556 +msgid "RTileType = 0xFC/0xF8 (run length encoded 8bit)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:558 +msgid "" +"The data is organized in a series of runs. Each run starts with a marker " +"which should be interpreted as a **count**. The following byte is the " +"**value**. They indicate that **count** pixels of **value** should be " +"inserted into the output stream." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:563 +msgid "" +"The interpretation is the same for 0xFC, and 0xF8. I believe that 0xFC " +"has a lower dynamic (2 bit) range than 0xF8 (4 or 8 bit)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:567 +msgid "RTileType = 0xFF (RMin CCITT RLE 1Bit)" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:569 +msgid "" +"The data stream for this file is CCITT RLE (G1 fax) compressed. The " +"format is complex but source is provided with the sample program (derived" +" from libtiff) for reading it. The result of uncompressing is 1bit data " +"so which the RMin value should be added." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:577 +msgid "hdr.adf - Header" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:579 +msgid "This is a binary dump of the first 308 bytes of a hdr.adf file." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:620 +msgid "Char" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:622 +msgid "HMagic" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:624 +msgid "Magic Number - always \"GRID1.2\\0\"" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:634 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:664 +msgid "assorted data, I don't know the purpose." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:642 +msgid "HCellType" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:644 +msgid "1 = int cover, 2 = float cover." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:646 +#: ../../source/drivers/raster/jpeg.rst:337 +#: ../../source/drivers/raster/jpeg.rst:358 +#: ../../source/drivers/raster/jpeg.rst:359 +#: ../../source/drivers/raster/lcp.rst:175 +#: ../../source/drivers/raster/sentinel2.rst:31 +#: ../../source/drivers/raster/sentinel2.rst:35 +#: ../../source/drivers/raster/sentinel2.rst:36 +#: ../../source/drivers/raster/sentinel2.rst:37 +#: ../../source/drivers/raster/sentinel2.rst:39 +#: ../../source/drivers/raster/sentinel2.rst:40 +#: ../../source/drivers/raster/sentinel2.rst:42 +#: ../../source/drivers/raster/sentinel2.rst:43 +msgid "20" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:652 +msgid "CompFlag" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:654 +msgid "0 = compressed, 1 = uncompressed" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:658 +msgid "232" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:666 +#: ../../source/drivers/raster/lcp.rst:237 +#: ../../source/drivers/raster/lcp.rst:238 +#: ../../source/drivers/raster/lcp.rst:239 +#: ../../source/drivers/raster/lcp.rst:240 +#: ../../source/drivers/raster/lcp.rst:241 +#: ../../source/drivers/raster/lcp.rst:242 +#: ../../source/drivers/raster/lcp.rst:243 +#: ../../source/drivers/raster/lcp.rst:244 +#: ../../source/drivers/raster/lcp.rst:245 +#: ../../source/drivers/raster/lcp.rst:246 +msgid "256" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:670 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:681 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:692 +#: ../../source/drivers/raster/arcinfo_grid_format.rst:702 +msgid "MSB Double" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:672 +msgid "HPixelSizeX" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:674 +msgid "" +"Width of a pixel in georeferenced coordinates. Generally 1.0 for " +"ungeoreferenced rasters." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:677 +msgid "264" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:683 +msgid "HPixelSizeY" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:685 +msgid "" +"Height of a pixel in georeferenced coordinates. Generally 1.0 for " +"ungeoreferenced rasters." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:688 +msgid "272" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:694 +msgid "XRef" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:696 +msgid "dfLLX-(nBlocksPerRow*nBlockXSize*dfCellSizeX)/2.0" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:698 +msgid "280" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:704 +msgid "YRef" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:706 +msgid "dfURY-(3*nBlocksPerColumn*nBlockYSize*dfCellSizeY)/2.0" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:708 +msgid "288" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:714 +msgid "HTilesPerRow" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:716 +msgid "" +"The width of the file in tiles (often 8 for files of less than 2K in " +"width)." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:719 +msgid "292" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:725 +msgid "HTilesPerColumn" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:727 +msgid "" +"The height of the file in tiles. Note this may be much more than the " +"number of tiles actually represented in the index file." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:730 +msgid "296" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:736 +msgid "HTileXSize" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:738 +msgid "The width of a file in pixels. Normally 256." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:740 +msgid "300" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:746 +msgid "Unknown, usually 1." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:748 +msgid "304" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:754 +msgid "HTileYSize" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:756 +msgid "Height of a tile in pixels, usually 4." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:761 +msgid "Acknowledgements" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:763 +msgid "" +"I would like to thank `Geosoft Inc. <http://www.geosoft.com/>`__ for " +"partial funding of my research into this format. I would also like to " +"thank:" +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:767 +msgid "Kenneth R. McVay for providing the statistics file format." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:768 +msgid "" +"Noureddine Farah of ThinkSpace who dug up lots of datasets that caused " +"problems." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:770 +msgid "Luciano Fonseca who worked out RTileType 0x01." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:771 +msgid "Martin Manningham of Global Geomatics for additional problem sample files." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:773 +msgid "" +"Harry Anderson of EDX Engineering, for showing me that floating point " +"tiles don't have RTileType." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:775 +msgid "" +"Ian Turton for supplying a sample files demonstrating the need to be " +"careful with the sign of \"short\" RMin values." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:777 +msgid "Duncan Chaundy at PCI for poking hard till I finally deduced 0xFF tiles." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:779 +msgid "Stephen Cheeseman of GeoSoft for yet more problem files." +msgstr "" + +#: ../../source/drivers/raster/arcinfo_grid_format.rst:780 +msgid "Geoffrey Williams for a files demonstrating tile type 0x20." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:5 +msgid "BAG -- Bathymetry Attributed Grid" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:7 +msgid "BAG" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:-1 +#: ../../source/drivers/raster/basisu.rst:-1 +#: ../../source/drivers/raster/cad.rst:-1 +#: ../../source/drivers/raster/daas.rst:-1 +#: ../../source/drivers/raster/dds.rst:-1 +#: ../../source/drivers/raster/ecw.rst:-1 +#: ../../source/drivers/raster/eedai.rst:-1 +#: ../../source/drivers/raster/exr.rst:-1 +#: ../../source/drivers/raster/fits.rst:-1 +#: ../../source/drivers/raster/georaster.rst:-1 +#: ../../source/drivers/raster/gif.rst:-1 +#: ../../source/drivers/raster/gpkg.rst:-1 +#: ../../source/drivers/raster/grass.rst:-1 +#: ../../source/drivers/raster/gta.rst:-1 +#: ../../source/drivers/raster/hdf4.rst:-1 +#: ../../source/drivers/raster/hdf5.rst:-1 +#: ../../source/drivers/raster/heif.rst:-1 +#: ../../source/drivers/raster/jp2ecw.rst:-1 +#: ../../source/drivers/raster/jp2kak.rst:-1 +#: ../../source/drivers/raster/jp2lura.rst:-1 +#: ../../source/drivers/raster/jp2mrsid.rst:-1 +#: ../../source/drivers/raster/jp2openjpeg.rst:-1 +#: ../../source/drivers/raster/jpeg.rst:-1 +#: ../../source/drivers/raster/jpegxl.rst:-1 +#: ../../source/drivers/raster/jpipkak.rst:-1 +#: ../../source/drivers/raster/kea.rst:-1 +#: ../../source/drivers/raster/ktx2.rst:-1 +#: ../../source/drivers/raster/mbtiles.rst:-1 +#: ../../source/drivers/raster/mrsid.rst:-1 +#: ../../source/drivers/raster/msg.rst:-1 +#: ../../source/drivers/raster/netcdf.rst:-1 +#: ../../source/drivers/raster/ngw.rst:-1 +#: ../../source/drivers/raster/ogcapi.rst:-1 +#: ../../source/drivers/raster/pcraster.rst:-1 +#: ../../source/drivers/raster/pdf.rst:-1 +#: ../../source/drivers/raster/pdf.rst:672 +#: ../../source/drivers/raster/plmosaic.rst:-1 +#: ../../source/drivers/raster/postgisraster.rst:-1 +#: ../../source/drivers/raster/rasterlite.rst:-1 +#: ../../source/drivers/raster/rasterlite2.rst:-1 +#: ../../source/drivers/raster/rdb.rst:-1 +#: ../../source/drivers/raster/rik.rst:-1 +#: ../../source/drivers/raster/s102.rst:-1 +#: ../../source/drivers/raster/s104.rst:-1 +#: ../../source/drivers/raster/s111.rst:-1 +#: ../../source/drivers/raster/tiledb.rst:-1 +#: ../../source/drivers/raster/wcs.rst:-1 +#: ../../source/drivers/raster/webp.rst:-1 +#: ../../source/drivers/raster/wms.rst:-1 +#: ../../source/drivers/raster/wmts.rst:-1 +#: ../../source/drivers/raster/zarr.rst:-1 +#: ../../source/drivers/vector/amigocloud.rst:-1 +#: ../../source/drivers/vector/arrow.rst:-1 +#: ../../source/drivers/vector/cad.rst:-1 +#: ../../source/drivers/vector/carto.rst:-1 +#: ../../source/drivers/vector/csw.rst:-1 +#: ../../source/drivers/vector/dgnv8.rst:-1 +#: ../../source/drivers/vector/dwg.rst:-1 +#: ../../source/drivers/vector/eeda.rst:-1 +#: ../../source/drivers/vector/elasticsearch.rst:-1 +#: ../../source/drivers/vector/filegdb.rst:-1 +#: ../../source/drivers/vector/georss.rst:-1 +#: ../../source/drivers/vector/gml.rst:-1 +#: ../../source/drivers/vector/gmlas.rst:-1 +#: ../../source/drivers/vector/gpkg.rst:-1 +#: ../../source/drivers/vector/gpsbabel.rst:-1 +#: ../../source/drivers/vector/gpx.rst:-1 +#: ../../source/drivers/vector/grass.rst:-1 +#: ../../source/drivers/vector/hana.rst:-1 +#: ../../source/drivers/vector/idb.rst:-1 +#: ../../source/drivers/vector/ili.rst:-1 +#: ../../source/drivers/vector/jml.rst:-1 +#: ../../source/drivers/vector/kml.rst:-1 +#: ../../source/drivers/vector/libkml.rst:-1 +#: ../../source/drivers/vector/lvbag.rst:-1 +#: ../../source/drivers/vector/mongodbv3.rst:-1 +#: ../../source/drivers/vector/mssqlspatial.rst:-1 +#: ../../source/drivers/vector/mvt.rst:-1 +#: ../../source/drivers/vector/mysql.rst:-1 +#: ../../source/drivers/vector/nas.rst:-1 +#: ../../source/drivers/vector/netcdf.rst:-1 +#: ../../source/drivers/vector/ngw.rst:-1 +#: ../../source/drivers/vector/oapif.rst:-1 +#: ../../source/drivers/vector/oci.rst:-1 +#: ../../source/drivers/vector/odbc.rst:-1 +#: ../../source/drivers/vector/ods.rst:-1 +#: ../../source/drivers/vector/ogdi.rst:-1 +#: ../../source/drivers/vector/osm.rst:-1 +#: ../../source/drivers/vector/parquet.rst:-1 +#: ../../source/drivers/vector/pdf.rst:-1 ../../source/drivers/vector/pg.rst:-1 +#: ../../source/drivers/vector/pgeo.rst:-1 +#: ../../source/drivers/vector/plscenes.rst:-1 +#: ../../source/drivers/vector/sosi.rst:-1 +#: ../../source/drivers/vector/sqlite.rst:-1 +#: ../../source/drivers/vector/svg.rst:-1 +#: ../../source/drivers/vector/tiledb.rst:-1 +#: ../../source/drivers/vector/vfk.rst:-1 +#: ../../source/drivers/vector/wfs.rst:-1 +#: ../../source/drivers/vector/xls.rst:-1 +#: ../../source/drivers/vector/xlsx.rst:-1 +#: ../../source/drivers/vector/xodr.rst:-1 +msgid "Build dependencies" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:9 +#: ../../source/drivers/raster/driver_summary.rst:52 +#: ../../source/drivers/raster/driver_summary.rst:382 +#: ../../source/drivers/raster/driver_summary.rst:820 +#: ../../source/drivers/raster/driver_summary.rst:826 +#: ../../source/drivers/raster/driver_summary.rst:832 +#: ../../source/drivers/raster/hdf5.rst:11 +#: ../../source/drivers/raster/s102.rst:9 +#: ../../source/drivers/raster/s104.rst:9 +#: ../../source/drivers/raster/s111.rst:9 +msgid "libhdf5" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:11 +msgid "" +"This driver provides read-only support, and starting with GDAL 2.4 for " +"creation, for bathymetry data in the BAG format. BAG files are actually a" +" specific product profile in an HDF5 file, but a custom driver exists to " +"present the data in a more convenient manner than is available through " +"the generic HDF5 driver." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:17 +msgid "" +"BAG files have two image bands representing Elevation (band 1), " +"Uncertainty (band 2) values for each cell in a raster grid area. Nominal " +"Elevation values may also be present, and starting with GDAL 3.2, any 2D " +"array of numeric data type and with the same dimensions as Elevation " +"present under BAG_root will be reported as a GDAL band." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:23 +msgid "" +"The geotransform and coordinate system is extracted from the internal XML" +" metadata provided with the dataset. However, some products may have " +"unsupported coordinate system formats, if using the non-WKT way of " +"encoding the spatial reference system." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:28 +msgid "The full XML metadata is available in the \"xml:BAG\" metadata domain." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:30 +#: ../../source/drivers/raster/s102.rst:26 +msgid "Nodata, minimum and maximum values for each band are also reported." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:39 +msgid "This driver supports the :cpp:func:`GDALDriver::Create` operation" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:48 +#: ../../source/drivers/raster/daas.rst:93 +#: ../../source/drivers/raster/eedai.rst:36 +#: ../../source/drivers/raster/esric.rst:143 +#: ../../source/drivers/raster/grib.rst:125 +#: ../../source/drivers/raster/gti.rst:363 +#: ../../source/drivers/raster/gtiff.rst:305 +#: ../../source/drivers/raster/hdf4.rst:227 +#: ../../source/drivers/raster/netcdf.rst:275 +#: ../../source/drivers/raster/ngw.rst:123 +#: ../../source/drivers/raster/nitf.rst:63 +#: ../../source/drivers/raster/ogcapi.rst:74 +#: ../../source/drivers/raster/openfilegdb.rst:52 +#: ../../source/drivers/raster/plmosaic.rst:62 +#: ../../source/drivers/raster/s102.rst:36 +#: ../../source/drivers/raster/s104.rst:37 +#: ../../source/drivers/raster/s111.rst:41 +#: ../../source/drivers/raster/sentinel2.rst:176 +#: ../../source/drivers/raster/stacit.rst:42 +#: ../../source/drivers/raster/stacta.rst:56 +#: ../../source/drivers/raster/tiledb.rst:30 +#: ../../source/drivers/raster/wcs.rst:207 +#: ../../source/drivers/raster/wmts.rst:87 +#: ../../source/drivers/raster/xyz.rst:51 +#: ../../source/drivers/raster/zarr.rst:256 +#: ../../source/drivers/vector/carto.rst:118 +#: ../../source/drivers/vector/csv.rst:266 +#: ../../source/drivers/vector/csw.rst:50 +#: ../../source/drivers/vector/eeda.rst:33 +#: ../../source/drivers/vector/esrijson.rst:60 +#: ../../source/drivers/vector/flatgeobuf.rst:41 +#: ../../source/drivers/vector/geojson.rst:185 +#: ../../source/drivers/vector/gml.rst:502 +#: ../../source/drivers/vector/gmlas.rst:186 +#: ../../source/drivers/vector/gpx.rst:89 +#: ../../source/drivers/vector/jsonfg.rst:97 +#: ../../source/drivers/vector/lvbag.rst:33 +#: ../../source/drivers/vector/miramon.rst:260 +#: ../../source/drivers/vector/ngw.rst:167 +#: ../../source/drivers/vector/oapif.rst:78 +#: ../../source/drivers/vector/ods.rst:35 +#: ../../source/drivers/vector/osm.rst:223 +#: ../../source/drivers/vector/parquet.rst:32 +#: ../../source/drivers/vector/plscenes_data_v1.rst:54 +#: ../../source/drivers/vector/shapefile.rst:277 +#: ../../source/drivers/vector/sosi.rst:14 +#: ../../source/drivers/vector/tiledb.rst:99 +#: ../../source/drivers/vector/vfk.rst:28 +#: ../../source/drivers/vector/wfs.rst:312 +#: ../../source/drivers/vector/xlsx.rst:43 +#: ../../source/drivers/vector/xodr.rst:59 +msgid "Open options" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:50 +msgid "" +"|about-open-options| For open options specific to variable resolution, " +"see following chapter." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:53 +msgid "Other open options are:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:65 +msgid "Variable resolution (VR) grid support" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:67 +msgid "" +"Starting with GDAL 2.4, GDAL can handle BAG files with `variable " +"resolution grids " +"<https://bitbucket.org/ccomjhc/openns/raw/master/docs/VariableResolution/2017-08-10_VariableResolution.docx>`__." +" Such datasets are made of a low-resolution grid, which is the one " +"presented by default by the driver, and for each of those low-resolution " +"cells, a higher resolution grid can be present in the file. Such higher " +"resolution grids are dubbed \"supergrids\" in GDAL." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:75 +msgid "" +"The driver has different modes of working which can be controlled by the " +"MODE open option:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:84 +msgid "" +"MODE=LOW_RES_GRID: this is the default mode (unless opening a supergrid)." +" The driver will expose the low resolution grid, and indicate in the " +"dataset metadata if the dataset has supergrids (HAS_SUPERGRIDS=TRUE), as " +"well as the minimum and maximum resolution of those grids." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:89 +msgid "" +"MODE=LIST_SUPERGRIDS: in this mode, the driver will report the various " +"supergrids in the subdataset list. It is possible to apply in this mode " +"additional open options to restrict the search" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:100 +msgid "" +"MINX=value: Minimum georeferenced X value to use as a filter for the " +"supergrids to list." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:102 +msgid "" +"MINY=value: Minimum georeferenced Y value to use as a filter for the " +"supergrids to list." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:104 +msgid "" +"MAXX=value: Maximum georeferenced X value to use as a filter for the " +"supergrids to list." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:106 +msgid "" +"MAXY=value: Maximum georeferenced Y value to use as a filter for the " +"supergrids to list." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:108 +msgid "" +"RES_FILTER_MIN=value: Minimum resolution of supergrids to take into " +"account (excluded bound)" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:110 +msgid "" +"RES_FILTER_MAX=value: Maximum resolution of supergrids to take into " +"account (included bound)" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:113 +msgid "" +"Opening a supergrid. This mode is triggered by using as a dataset name a " +"string formatted like BAG:my.bag:supergrid:{y}:{x}, which is the value of" +" the SUBDATASET_x_NAME metadata items reported by the above described " +"mode. {y} is the index (starting from 0, from the south of the grid), and" +" {x} is the index (starting from 0, from the west of the grid) of the " +"supergrid to open." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:120 +msgid "" +"MODE=RESAMPLED_GRID: in this mode, the user specify the extent and " +"resolution of a target grid, and for each cell of this target grid, the " +"driver will find the nodes of the supergrids that fall into that cell. By" +" default, it will select the node with the maximum elevation value to " +"populate the cell value. Or if no node of any supergrid are found, the " +"cell value will be set to the nodata value. Overviews are reported: note " +"that, those overviews correspond to resampled grids computed with " +"different values of the RESX and RESY parameters, but using the same " +"value population rules (and not nearest neighbour resampling of the full " +"resolution resampled grid). The last overview level is the low-resolution" +" grid (if SUPERGRIDS_MASK=NO)" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:133 +msgid "The available open options in this mode are:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:135 +msgid "" +"MINX=value: Minimum georeferenced X value for the resampled grid. By " +"default, the corresponding value of the low resolution grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:137 +msgid "" +"MINY=value: Minimum georeferenced Y value for the resampled grid. By " +"default, the corresponding value of the low resolution grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:139 +msgid "" +"MAXX=value: Maximum georeferenced X value for the resampled grid. By " +"default, the corresponding value of the low resolution grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:141 +msgid "" +"MAXY=value: Maximum georeferenced Y value for the resampled grid. By " +"default, the corresponding value of the low resolution grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:143 +msgid "" +"RESX=value: Horizontal resolution. By default, and if RES_STRATEGY is set" +" to AUTO, this will be the minimum resolution among all the supergrids." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:146 +msgid "" +"RESY=value: Vertical resolution (positive value). By default, and if " +"RES_STRATEGY is set to AUTO, this will be the minimum resolution among " +"all the supergrids." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:149 +msgid "" +"RES_STRATEGY=AUTO/MIN/MAX/MEAN: Which strategy to apply to set the " +"resampled grid resolution. By default, if none of RESX, RESY, " +"RES_FILTER_MIN and RES_FILTER_MAX is specified, the AUTO strategy will " +"correspond to the MIN strategy: that is the minimum resolution among all " +"the supergrids is used. If MAX is specified, the maximum resolution among" +" all the supergrids is used. If MEAN is specified, the mean resolution " +"among all the supergrids is used. RESX and RESY, if defined, will " +"override the resolution determined by RES_STRATEGY." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:158 +msgid "" +"RES_FILTER_MIN=value: Minimum resolution of supergrids to take into " +"account (excluded bound, except if it is the minimum resolution of " +"supergrids). By default, the minimum resolution of supergrids available. " +"If this value is specified and none of RES_STRATEGY, RES_FILTER_MAX, RESX" +" or RESY is specified, the maximum resolution among all the supergrids " +"will be used as the resolution for the resampled grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:165 +msgid "" +"RES_FILTER_MAX=value: Maximum resolution of supergrids to take into " +"account (included bound). By default, the maximum resolution of " +"supergrids available. If this value is specified and none of " +"RES_STRATEGY, RESX or RESY is specified, this will also be used as the " +"resolution for the resampled grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:170 +msgid "" +"VALUE_POPULATION=MIN/MAX/MEAN/COUNT: Which value population strategy to " +"apply to compute the resampled cell values. This default to MAX: the " +"elevation value of a target cell is the maximum elevation of all " +"supergrid nodes (potentially filtered with RES_FILTER_MIN and/or " +"RES_FILTER_MAX) that fall into this cell; the corresponding uncertainty " +"will be the uncertainty of the source node where this maximum elevation " +"si reached. If no supergrid node fall into the target cell, the nodata " +"value is set. The MIN strategy is similar, except that this is the " +"minimum elevation value among intersecting nodes that is selected. The " +"MEAN strategy uses the mean value of the elevation of intersecting nodes," +" and the maximum uncertainty of those nodes. The COUNT strategy (GDAL >= " +"3.2) exposes one single UInt32 band where each target cell contains the " +"count of supergrid nodes that fall into it." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:184 +msgid "" +"SUPERGRIDS_MASK=YES/NO. Default to NO. If set to YES, instead of the " +"elevation and uncertainty band, the dataset contains a single Byte band " +"which is boolean valued. For a target cell, if at least one supergrids " +"nodes (potentially filtered with RES_FILTER_MIN and/or RES_FILTER_MAX) " +"falls into the cell, the cell value is set at 255. Otherwise it is set at" +" 0. This can be used to distinguish if elevation values at nodata are due" +" to no source supergrid node falling into them, or if that/those " +"supergrid nodes were themselves at the nodata value." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:193 +msgid "NODATA_VALUE=value. Override the default value, which is usually 1000000." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:196 +msgid "" +"MODE=INTERPOLATED: (GDAL >= 3.8) in this mode, the user specify the " +"extent and resolution of a target grid, and for each cell of this target " +"grid, the driver will interpolate the value from the surrounding nodes of" +" the supergrid(s) that applies to the cell, using in priority bilinear " +"interpolation (for a node that falls within a supergrid and when all 4 " +"surrounding nodes of the supergrid are not at nodata value), and " +"fallbacks to barycentric interpolation or inverse distance weighting in " +"other situations." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:205 +msgid "" +"Overviews are reported. Note that those overviews correspond to resampled" +" grids computed with different values of the RESX and RESY parameters, " +"but for performance reasons, the interpolation is still limited to the " +"immediate neighbours of the target grid in the supergrid(s), which result" +" in the equivalent of nearest-neighbour downsampling of the full " +"resolution raster. The last overview level is the low-resolution grid." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:212 +msgid "" +"The available open options in this mode are MINX, MINY, MAXX, MAXY, RESX," +" RESY, RES_STRATEGY, RES_FILTER_MIN, RES_FILTER_MAX and NODATA_VALUE (cf " +"their above description for the MODE=RESAMPLED_GRID)" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:217 +#: ../../source/drivers/raster/s102.rst:64 +msgid "Spatial metadata support" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:219 +msgid "" +"Starting with GDAL 3.2, GDAL can expose BAG files with `spatial metadata " +"<https://github.com/OpenNavigationSurface/BAG/issues/2>`__." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:222 +msgid "" +"When such spatial metadata is present, the subdataset list will include " +"names of the form 'BAG:\"{filename}\":georef_metadata:{name_of_layer}' " +"where ``name_of_layer`` is the name of a subgroup under " +"``/BAG_root/Georef_metadata``" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:226 +msgid "" +"The values of the ``keys`` dataset under each metadata layer are used as " +"the GDAL raster value. And the corresponding ``values`` dataset is " +"exposed as a GDAL Raster Attribute Table associated to the GDAL raster " +"band. If ``keys`` is absent, record 1 of ``values`` is assumed to be met " +"for each elevation point that does not match the nodata value of the " +"elevation band." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:232 +msgid "" +"When variable resolution grids are present, the MODE=LIST_SUPERGRIDS open" +" option will cause subdatasets of names of the form " +"'BAG:\"{filename}\":georef_metadata:{name_of_layer}:{y}:{x}' to be " +"reported. When opening such a subdataset, the ``varres_keys`` dataset " +"will be used to populate the GDAL raster value. If ``varres_keys`` is " +"absent, record 1 of ``values`` is assumed to be met for each elevation " +"point that does not match the nodata value of the variable resolution " +"elevation band." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:241 +msgid "Tracking list support" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:243 +msgid "" +"When the dataset is opened in vector mode (ogrinfo, ogr2ogr, etc.), the " +"tracking_list dataset will be reported as a OGR vector layer" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:247 +#: ../../source/drivers/raster/isis3.rst:154 +#: ../../source/drivers/raster/pds4.rst:91 +#: ../../source/drivers/raster/vicar.rst:181 +#: ../../source/drivers/vector/gmlas.rst:286 +msgid "Creation support" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:249 +msgid "" +"Starting with GDAL 2.4, the driver can create a BAG dataset (without " +"variable resolution extension) with the elevation and uncertainty bands " +"from a source dataset. The source dataset must be georeferenced, and have" +" one or two bands. The first band is assumed to be the elevation band, " +"and the second band the uncertainty band. If the second band is missing, " +"the uncertainty will be set to nodata." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:256 +msgid "" +"The driver will instantiate the BAG XML metadata by using a template " +"file, which is by default, `bag_template.xml " +"<https://raw.githubusercontent.com/OSGeo/gdal/master/data/bag_template.xml>`__," +" found in the GDAL data definition files. This template contains " +"variables, present as ${KEYNAME} or ${KEYNAME:default_value} in the XML " +"file, that can be substituted by providing a creation option whose name " +"is the VAR\\_ string prefixed to the key name." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:264 +#: ../../source/drivers/raster/blx.rst:42 +#: ../../source/drivers/raster/bmp.rst:40 +#: ../../source/drivers/raster/ecw.rst:73 +#: ../../source/drivers/raster/ers.rst:35 +#: ../../source/drivers/raster/exr.rst:24 +#: ../../source/drivers/raster/georaster.rst:112 +#: ../../source/drivers/raster/gif.rst:40 +#: ../../source/drivers/raster/gta.rst:28 +#: ../../source/drivers/raster/hdf4.rst:208 +#: ../../source/drivers/raster/hf2.rst:36 +#: ../../source/drivers/raster/hfa.rst:50 +#: ../../source/drivers/raster/isis2.rst:49 +#: ../../source/drivers/raster/jp2kak.rst:147 +#: ../../source/drivers/raster/jpeg.rst:165 +#: ../../source/drivers/raster/pcidsk.rst:31 +#: ../../source/drivers/raster/rasterlite.rst:87 +#: ../../source/drivers/raster/rasterlite2.rst:68 +#: ../../source/drivers/raster/rmf.rst:59 +#: ../../source/drivers/raster/rraster.rst:29 +#: ../../source/drivers/raster/usgsdem.rst:59 +#: ../../source/drivers/raster/vrt.rst:64 +msgid "|about-creation-options| The following creation options are supported:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:337 +msgid "" +"Other required variables found in the template, such as RES, RESX, RESY, " +"RES_UNIT, HEIGHT, WIDTH, CORNER_POINTS and HORIZ_WKT will be " +"automatically filled from the input dataset metadata." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:341 +msgid "The other following creation options are available:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:380 +#: ../../source/drivers/raster/esric.rst:48 +msgid "Usage examples" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:382 +msgid "Opening in low resolution mode:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:398 +msgid "Displaying available supergrids:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:415 +msgid "Opening a particular supergrid:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:421 +msgid "" +"Converting a BAG in resampling mode with default parameters (use of " +"minimum resolution of supergrids, MAX value population rule):" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:428 +msgid "" +"Converting a BAG in resampling mode with a particular grid origin and " +"resolution" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:435 +msgid "" +"Converting a BAG in resampling mode, with a mask indicating where " +"supergrids nodes intersect the cell of the resampled dataset." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:442 +msgid "" +"Converting a BAG in resampling mode, by filtering on supergrid " +"resolutions (and the resampled grid will use 4 meter resolution by " +"default)" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:450 +msgid "" +"Converting a GeoTIFF file to a BAG dataset, and provide a custom value " +"for the ABSTRACT substituable variable." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:457 +msgid "" +"Converting a (VR) BAG in resampling mode with a particular grid " +"resolution (5m) to a BAG dataset (without variable resolution extension)," +" and provide a custom value for the ABSTRACT metadata:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:465 +msgid "Displaying the tracking list:" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:474 +msgid "Implemented as :source_file:`frmts/hdf5/bagdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/bag.rst:475 +msgid "`The Open Navigation Surface Project <http://www.opennavsurf.org>`__" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:476 +msgid "" +"`Description of Bathymetric Attributed Grid Object (BAG) Version 1.6 " +"<https://github.com/OpenNavigationSurface/BAG/raw/master/docs/BAG_FSD_Release_1.6.3.doc>`__" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:478 +msgid "" +"`Variable resolution grid extension for BAG files " +"<https://github.com/OpenNavigationSurface/BAG/raw/master/docs/VariableResolution/2017-08-10_VariableResolution.docx>`__" +msgstr "" + +#: ../../source/drivers/raster/bag.rst:480 +#: ../../source/drivers/raster/s104.rst:60 +#: ../../source/drivers/raster/s111.rst:64 +msgid ":ref:`S-102 driver <raster.s102>`" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:5 +msgid "BASISU -- Basis Universal" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:9 +msgid "BASISU" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:11 +#: ../../source/drivers/raster/driver_summary.rst:54 +#: ../../source/drivers/raster/driver_summary.rst:58 +#: ../../source/drivers/raster/driver_summary.rst:520 +#: ../../source/drivers/raster/ktx2.rst:11 +msgid "Basis Universal" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:14 +#: ../../source/drivers/raster/ktx2.rst:14 +msgid "From https://github.com/BinomialLLC/basis_universal," +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:16 +#: ../../source/drivers/raster/ktx2.rst:16 +msgid "" +"Basis Universal is a \"supercompressed\" GPU texture data interchange " +"system that supports two highly compressed intermediate file formats " +"(.basis or the .KTX2 open standard from the Khronos Group) that can be " +"quickly transcoded to a very wide variety of GPU compressed and " +"uncompressed pixel formats." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:22 +msgid "" +"This driver handles textures with the .basis extension. For KTX2, refer " +"to the :ref:`raster.ktx2` driver." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:25 +#: ../../source/drivers/raster/ktx2.rst:26 +msgid "" +"Note that while the file format supports direct transcoding to other GPU " +"pixel formats, this GDAL driver supports only conversion between " +"uncompressed RGB(A) data and Basis Universal textures." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:29 +msgid "" +"When a file is made of several images, they are exposed as subdataset, " +"with the `BASISU:filename:image_idx` syntax." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:32 +#: ../../source/drivers/raster/ktx2.rst:33 +msgid "Mipmaps levels are exposed as GDAL overviews." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:42 +#: ../../source/drivers/raster/gpkg.rst:422 +#: ../../source/drivers/raster/gta.rst:26 +#: ../../source/drivers/raster/hf2.rst:34 +#: ../../source/drivers/raster/kea.rst:49 +#: ../../source/drivers/raster/ktx2.rst:43 +#: ../../source/drivers/raster/mbtiles.rst:255 +#: ../../source/drivers/raster/rasterlite.rst:85 +#: ../../source/drivers/raster/rasterlite2.rst:66 +#: ../../source/drivers/raster/tiledb.rst:58 +#: ../../source/drivers/raster/vrt.rst:62 +#: ../../source/drivers/raster/webp.rst:39 +#: ../../source/drivers/raster/xyz.rst:64 +#: ../../source/drivers/raster/zarr.rst:339 +#: ../../source/drivers/vector/pgdump.rst:32 +msgid "Creation options" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:44 +#: ../../source/drivers/raster/ktx2.rst:45 +msgid "" +"The format supports 2 modes: a high quality mode which is internally " +"based off the `UASTC compressed texture format " +"<https://richg42.blogspot.com/2020/01/uastc-block-format-" +"encoding.html>`_, and the original lower quality mode which is based off " +"a subset of ETC1 called \"ETC1S\". The default is ETC1S. Only input of " +"type Byte and with 1 (grey), 2 (grey+alpha), 3 (RGB) or 4 (RGB + alpha) " +"bands is supported. Refer to " +"https://github.com/BinomialLLC/basis_universal for more details on those " +"modes and their options." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:53 +#: ../../source/drivers/raster/gpkg.rst:424 +#: ../../source/drivers/raster/jp2lura.rst:80 +#: ../../source/drivers/raster/jp2openjpeg.rst:125 +#: ../../source/drivers/raster/jpegxl.rst:79 +#: ../../source/drivers/raster/ktx2.rst:54 +#: ../../source/drivers/raster/mbtiles.rst:257 +#: ../../source/drivers/raster/netcdf.rst:430 +#: ../../source/drivers/raster/nitf.rst:114 +#: ../../source/drivers/raster/nwtgrd.rst:68 +#: ../../source/drivers/raster/pdf.rst:223 ../../source/drivers/raster/r.rst:31 +msgid "|about-creation-options| The following creation options are available:" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:111 +msgid "" +"Defaults to the maximum number of virtual CPUs available. Can also be " +"controlled with the :config:`GDAL_NUM_THREADS` configuration option." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:119 +#: ../../source/drivers/raster/ktx2.rst:126 +msgid "Whether to enable MIPMAP generation." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:129 +#: ../../source/drivers/raster/dds.rst:40 +#: ../../source/drivers/raster/ktx2.rst:136 +#: ../../source/drivers/vector/mongodbv3.rst:305 +msgid "Build instructions" +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:131 +#: ../../source/drivers/raster/ktx2.rst:138 +msgid "" +"Building basisu as a library requires currently building the `cmake` " +"branch of the https://github.com/rouault/basis_universal/tree/cmake fork." +msgstr "" + +#: ../../source/drivers/raster/basisu.rst:143 +#: ../../source/drivers/raster/ktx2.rst:150 +msgid "" +"Once basisu is built, GDAL CMake options must be configured by pointing " +"the basisu install prefix in the ``CMAKE_PREFIX_PATH`` variable or " +"``basisu_ROOT`` variable." +msgstr "" + +#: ../../source/drivers/raster/blx.rst:5 +msgid "BLX -- Magellan BLX Topo File Format" +msgstr "" + +#: ../../source/drivers/raster/blx.rst:7 +msgid "BLX" +msgstr "" + +#: ../../source/drivers/raster/blx.rst:11 +msgid "" +"BLX is the format for storing topographic data in Magellan GPS units. " +"This driver supports both reading and writing. In addition the 4 overview" +" levels inherent in the BLX format can be used with the driver." +msgstr "" + +#: ../../source/drivers/raster/blx.rst:15 +msgid "" +"The BLX format is tile based, for the moment the tile size is fixed to " +"128x128 size. Furthermore the dimensions must be a multiple of the tile " +"size." +msgstr "" + +#: ../../source/drivers/raster/blx.rst:19 +msgid "" +"The data type is fixed to Int16 and the value for undefined values is " +"fixed to -32768. In the BLX format undefined values are only really " +"supported on tile level. For undefined pixels in non-empty tiles see the " +"FILLUNDEF/FILLUNDEFVAL options." +msgstr "" + +#: ../../source/drivers/raster/blx.rst:34 +#: ../../source/drivers/raster/gtiff.rst:40 +#: ../../source/drivers/raster/jp2ecw.rst:49 +#: ../../source/drivers/raster/jp2kak.rst:97 +#: ../../source/drivers/raster/jp2lura.rst:29 +#: ../../source/drivers/raster/jp2mrsid.rst:27 +#: ../../source/drivers/raster/jp2openjpeg.rst:40 +#: ../../source/drivers/raster/pds.rst:54 +msgid "Georeferencing" +msgstr "" + +#: ../../source/drivers/raster/blx.rst:36 +msgid "" +"The BLX projection is fixed to WGS84 and georeferencing from BLX is " +"supported in the form of one tiepoint and pixelsize." +msgstr "" + +#: ../../source/drivers/raster/blx.rst:40 +#: ../../source/drivers/raster/bmp.rst:38 +#: ../../source/drivers/raster/cog.rst:33 +#: ../../source/drivers/raster/ecw.rst:44 +#: ../../source/drivers/raster/ers.rst:33 +#: ../../source/drivers/raster/exr.rst:22 +#: ../../source/drivers/raster/georaster.rst:110 +#: ../../source/drivers/raster/gtiff.rst:375 +#: ../../source/drivers/raster/isis2.rst:47 +#: ../../source/drivers/raster/jp2lura.rst:78 +#: ../../source/drivers/raster/jp2mrsid.rst:62 +#: ../../source/drivers/raster/jp2openjpeg.rst:123 +#: ../../source/drivers/raster/jpeg.rst:148 +#: ../../source/drivers/raster/jpegxl.rst:68 +#: ../../source/drivers/raster/lcp.rst:76 +#: ../../source/drivers/raster/mem.rst:76 +#: ../../source/drivers/raster/netcdf.rst:428 +#: ../../source/drivers/raster/nwtgrd.rst:66 +#: ../../source/drivers/raster/pcidsk.rst:29 +#: ../../source/drivers/raster/pdf.rst:221 +#: ../../source/drivers/raster/pnm.rst:18 ../../source/drivers/raster/r.rst:29 +#: ../../source/drivers/raster/rmf.rst:57 +#: ../../source/drivers/vector/kml.rst:92 +msgid "Creation Options" +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:5 +msgid "BMP -- Microsoft Windows Device Independent Bitmap" +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:7 +msgid "BMP" +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:11 +msgid "" +"MS Windows Device Independent Bitmaps supported by the Windows kernel and" +" mostly used for storing system decoration images. Due to the nature of " +"the BMP format it has several restrictions and could not be used for " +"general image storing. In particular, you can create only 1-bit " +"monochrome, 8-bit pseudocoloured and 24-bit RGB images only. Even " +"grayscale images must be saved in pseudocolour form." +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:18 +msgid "" +"This driver supports reading almost any type of the BMP files and could " +"write ones which should be supported on any Windows system. Only single- " +"or three- band files could be saved in BMP file. Input values will be " +"resampled to 8 bit." +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:23 +msgid "" +"If an ESRI world file exists with the .bpw, .bmpw or .wld extension, it " +"will be read and used to establish the geotransform for the image." +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:52 +msgid "Implemented as :source_file:`frmts/bmp/bmpdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/bmp.rst:53 +msgid "" +"`Wikipedia BMP file format " +"<https://en.wikipedia.org/wiki/BMP_file_format>`__" +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:5 +msgid "BSB -- Maptech/NOAA BSB Nautical Chart Format" +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:7 +msgid "BSB" +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:11 +msgid "" +"BSB Nautical Chart format is supported for read access, including reading" +" the colour table and the reference points (as GCPs). Note that the .BSB " +"files cannot be selected directly. Instead select the .KAP files. " +"Versions 1.1, 2.0 and 3.0 have been tested successfully." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:16 +msgid "" +"This driver should also support GEO/NOS format as supplied by Softchart. " +"These files normally have the extension .nos with associated .geo files " +"containing georeferencing ... the .geo files are currently ignored." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:20 +msgid "" +"This driver is based on work by Mike Higgins. See the " +":source_file:`frmts/bsb/bsb_read.c` files for details on patents " +"affecting BSB format." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:23 +msgid "" +"It is possible to select an alternate color palette via the BSB_PALETTE " +"configuration option. The default value is RGB. Other common values that " +"can be found are : DAY, DSK, NGT, NGR, GRY, PRC, PRG..." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:28 +msgid "NOTE: Implemented as :source_file:`frmts/bsb/bsbdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:39 +#: ../../source/drivers/raster/cals.rst:35 +#: ../../source/drivers/raster/eedai.rst:150 +#: ../../source/drivers/raster/fast.rst:106 +#: ../../source/drivers/raster/gpkg.rst:638 +#: ../../source/drivers/raster/gtiff.rst:164 +#: ../../source/drivers/raster/hdf4.rst:220 +#: ../../source/drivers/raster/isis3.rst:46 +#: ../../source/drivers/raster/jp2ecw.rst:338 +#: ../../source/drivers/raster/l1b.rst:67 +#: ../../source/drivers/raster/lcp.rst:47 +#: ../../source/drivers/raster/mrsid.rst:37 +#: ../../source/drivers/raster/ngw.rst:181 +#: ../../source/drivers/raster/nwtgrd.rst:51 +#: ../../source/drivers/raster/openfilegdb.rst:77 +#: ../../source/drivers/raster/pdf.rst:42 +#: ../../source/drivers/raster/pds4.rst:47 +#: ../../source/drivers/raster/rmf.rst:33 +#: ../../source/drivers/raster/sentinel2.rst:139 +#: ../../source/drivers/raster/vicar.rst:35 +#: ../../source/drivers/vector/dgnv8.rst:93 +#: ../../source/drivers/vector/gpkg.rst:525 +#: ../../source/drivers/vector/ngw.rst:279 +#: ../../source/drivers/vector/parquet.rst:189 +msgid "Metadata" +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:41 +msgid "The following metadata items may be reported:" +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:43 +msgid "" +"**BSB_KNP**: content of the KNP/ header field, giving information on the " +"coordinate reference system." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:46 +msgid "" +"**BSB_KNQ**: content of the KNQ/ header field, giving information on the " +"coordinate reference system." +msgstr "" + +#: ../../source/drivers/raster/bsb.rst:49 +msgid "" +"**BSB_CUTLINE**: (starting with GDAL 3.1). When PLY/ header is present, " +"Well-Known text representation of a polygon with coordinates in " +"longitude, latitude order, representing the cutline of the chart." +msgstr "" + +#: ../../source/drivers/raster/bt.rst:5 +msgid "BT -- VTP .bt Binary Terrain Format" +msgstr "" + +#: ../../source/drivers/raster/bt.rst:7 +msgid "BT" +msgstr "" + +#: ../../source/drivers/raster/bt.rst:11 +msgid "" +"The .bt format is used for elevation data in the VTP software. The driver" +" includes support for reading and writing .bt 1.3 format including " +"support for Int16, Int32 and Float32 pixel data types." +msgstr "" + +#: ../../source/drivers/raster/bt.rst:15 +msgid "" +"The driver does **not** support reading or writing gzipped (.bt.gz) .bt " +"files even though this is supported by the VTP software. Please unpack " +"the files before using with GDAL using the \"gzip -d file.bt.gz\"." +msgstr "" + +#: ../../source/drivers/raster/bt.rst:19 +msgid "" +"Projections in external .prj files are read and written, and support for " +"most internally defined coordinate systems is also available." +msgstr "" + +#: ../../source/drivers/raster/bt.rst:22 +msgid "" +"Read/write imagery access with the GDAL .bt driver is terribly slow due " +"to a very inefficient access strategy to this column oriented data. This " +"could be corrected, but it would be a fair effort." +msgstr "" + +#: ../../source/drivers/raster/bt.rst:26 +msgid "NOTE: Implemented as :source_file:`frmts/raw/btdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/bt.rst:28 +msgid "" +"See Also: The `BT file format " +"<http://www.vterrain.org/Implementation/Formats/BT.html>`__ is defined on" +" the `VTP <http://www.vterrain.org/>`__ web site." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:5 +msgid "BYN - Natural Resources Canada's Geoid file format (.byn)" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:7 +msgid "BYN" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:11 +msgid "" +"Files with extension \".byn\" have a binary format. The format includes " +"two sections which are the Header and the Data. The data are stored by " +"rows starting from the north. Each row is stored from the west to the " +"east. The data are either short (2 bytes) or standard (4 bytes) integers." +" The size of the bytes is defined in the header." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:17 +msgid "" +"The total size of the file is 80 bytes + (Row x Column x (2 or 4) bytes) " +"where Row is the number of rows in the grid and Column is the number of " +"columns in the grid. Row and Column can be calculated by these two " +"equations:" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:22 +msgid "Row = (North Boundary - South Boundary) / (NS Spacing) + 1" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:24 +msgid "Column = (East Boundary - West Boundary) / (EW Spacing) + 1" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:26 +msgid "" +"The \".byn\" files may contain undefined data. Depending if the data are " +"stored as 2-byte or 4-byte integers, the undefined data are expressed the" +" following way:" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:30 +msgid "" +"4-byte data (Standard integer): 9999.0 \\* Factor, the Factor is given in" +" the header" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:33 +msgid "2 byte data (Short integer): 32767" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:35 +msgid "" +"Most of the parameters in the \".byn\" header can be read by clicking the" +" “Information” icon in software GPS-H." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:38 +msgid "" +"NOTE: Files with extension \".err\" are also in the \".byn\" format. An " +"\".err\" file usually contains the error estimates of the \".byn\" file " +"of the same name (e.g., CGG2013n83.byn and CGG2013n83.err). The \".err\" " +"file will have variable Data equal to 1 or 3." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:55 +msgid "Factor" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:57 +msgid "" +"When translating from or into BYN file to or from another formats the " +"scale will affect the result profoundly." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:60 +msgid "" +"Translating to a format that supports Scale (GTIFF for example) will " +"maintain the data type and thescale information. The pixel values are " +"perfectly preserved." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:64 +msgid "" +"Translating to a format that does not support Scale will maintain the " +"data type but without the Scale, meaning loss of information on every " +"pixels." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:68 +msgid "" +"The solution to the problem above is to use \"-unscale\" and \"-ot " +"Float32\" when using gdal_translate or GDAL API. That will produce a " +"dataset without scale but with the correct pixel information. Ex.:" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:72 +msgid "gdal_translate CGG2013an83.err test2.tif -unscale -ot Float32" +msgstr "" + +#: ../../source/drivers/raster/byn.rst:74 +msgid "" +"NOTE: The BYN header variable **Factor** is the inverse of GDAL " +"**Scale**. (Scale = 1.0 / Factor)." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:80 +msgid "Implemented as :source_file:`frmts/raw/byndataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/byn.rst:81 +msgid "`www.nrcan.gc.ca <https://www.nrcan.gc.ca>`__" +msgstr "" + +#: ../../source/drivers/raster/cad.rst:5 +msgid "CAD -- AutoCAD DWG raster layer" +msgstr "" + +#: ../../source/drivers/raster/cad.rst:7 ../../source/drivers/vector/cad.rst:7 +msgid "CAD" +msgstr "" + +#: ../../source/drivers/raster/cad.rst:11 +#: ../../source/drivers/raster/driver_summary.rst:94 +#: ../../source/drivers/vector/cad.rst:9 +#: ../../source/drivers/vector/driver_summary.rst:40 +msgid "(internal libopencad provided)" +msgstr "" + +#: ../../source/drivers/raster/cad.rst:13 +msgid "" +"OGR DWG support is based on libopencad, so the list of supported DWG " +"(DXF) versions can be seen in libopencad documentation. All drawing " +"entities are separated into layers as they are in DWG file. The rasters " +"are usually a separate georeferenced files (GeoTiff, Jpeg, Png etc.) " +"which exist in DWG file as separate layers. The driver try to get spatial" +" reference and other methadata from DWG Image description and set it to " +"GDALDataset." +msgstr "" + +#: ../../source/drivers/raster/cad.rst:21 +msgid "" +"NOTE: Implemented as " +":source_file:`ogr/ogrsf_frmts/cad/gdalcaddataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:5 +msgid "CALS -- CALS Type 1" +msgstr "" + +#: ../../source/drivers/raster/cals.rst:7 +msgid "CALS" +msgstr "" + +#: ../../source/drivers/raster/cals.rst:13 +msgid "" +"CALS Type 1 rasters are untiled back and white rasters made of a " +"2048-byte text header in the MIL-STD-1840 standard, followed by a single " +"datastream compressed with CCITT/ITU-T Recommendation 6, aka Group 6, aka" +" CCITT FAX 4. CALS Type 1 rasters are one of the 4 types of formats " +"described by MIL-PRF-28002C (this standard is now deprecated). Other " +"types are not handled by this driver." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:20 +msgid "" +"This driver supports reading and creation of CALS Type 1 rasters. Update " +"of existing rasters is not supported." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:23 +msgid "" +"A CALS dataset is exposed by the driver as a single-band 1-bit raster " +"with a 2-entry color table. The first entry (0) is white " +"(RGB=255,255,255) and the second entry (1) is black (RGB=0,0,0)." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:37 +msgid "" +"The following metadata items might be exposed by the driver (or read from" +" the input dataset to generate a cor" +msgstr "" + +#: ../../source/drivers/raster/cals.rst:40 +msgid "" +"**PIXEL_PATH**: First value of the \"rorient\" header field, measured in " +"degrees counterclockwise from the positive horizontal axis (east). The " +"pel path value represents the number of degrees the image would have to " +"be rotated counterclockwise in order to display the image with proper " +"viewing orientation. The permissible values for the pixel path direction " +"shall be \"0\", \"90\", \"180\", or \"270\". 0 is the typical value. If " +"PIXEL_PATH=0 and LINE_PROGRESSION=270, neither are reported." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:48 +msgid "" +"**LINE_PROGRESSION**: Second value of the \"rorient\" header field. The " +"line progression direction is measured in degrees counterclockwise from " +"the pel path direction. The permissible values for the line progression " +"direction shall be \"90\" or \"270\". 270 is the typical value. If " +"PIXEL_PATH=0 and LINE_PROGRESSION=270, neither are reported." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:54 +msgid "" +"**TIFFTAG_XRESOLUTION**: Scan X resolution in dot per inch, from the " +"\"rdensty\" header field. TIFFTAG_XRESOLUTION and TIFFTAG_YRESOLUTION are" +" always equal in CALS." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:57 +msgid "" +"**TIFFTAG_YRESOLUTION**: Scan Y resolution in dot per inch, from the " +"\"rdensty\" header field. TIFFTAG_XRESOLUTION and TIFFTAG_YRESOLUTION are" +" always equal in CALS." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:62 +#: ../../source/drivers/raster/gpkg.rst:173 +#: ../../source/drivers/raster/rasterlite.rst:64 +#: ../../source/drivers/vector/arrow.rst:53 +#: ../../source/drivers/vector/gpkg.rst:256 +#: ../../source/drivers/vector/mvt.rst:214 +#: ../../source/drivers/vector/parquet.rst:57 +#: ../../source/drivers/vector/pmtiles.rst:87 +#: ../../source/drivers/vector/tiledb.rst:84 +#: ../../source/drivers/vector/vdv.rst:41 +msgid "Creation issues" +msgstr "" + +#: ../../source/drivers/raster/cals.rst:64 +msgid "" +"Only single band 1-bit rasters are valid input to create a new CALS file." +" If the input raster has no color table, 0 is assumed to be black and 1 " +"to be white. If the input raster has a (2 entries) color table, the value" +" for the black and white color will be determined from the color table." +msgstr "" + +#: ../../source/drivers/raster/cals.rst:73 +msgid "" +"`MIL-PRF-28002C <http://everyspec.com/MIL-PRF/MIL-PRF-010000-29999/MIL-" +"PRF-28002C_4830/>`__" +msgstr "" + +#: ../../source/drivers/raster/cals.rst:74 +msgid "" +"`MIL-STD-1840C <http://everyspec.com/MIL-STD/MIL-STD-1800-1999/MIL-STD-" +"1840C_4779/>`__" +msgstr "" + +#: ../../source/drivers/raster/ceos.rst:5 +msgid "CEOS -- CEOS Image" +msgstr "" + +#: ../../source/drivers/raster/ceos.rst:7 +msgid "CEOS" +msgstr "" + +#: ../../source/drivers/raster/ceos.rst:11 +msgid "" +"This is a simple, read-only reader for ceos image files. To use, select " +"the main imagery file. This driver reads only the image data, and does " +"not capture any metadata, or georeferencing." +msgstr "" + +#: ../../source/drivers/raster/ceos.rst:15 +msgid "" +"This driver is known to work with CEOS data produced by Spot Image, but " +"will have problems with many other data sources. In particular, it will " +"only work with eight bit unsigned data." +msgstr "" + +#: ../../source/drivers/raster/ceos.rst:19 +msgid "" +"See the separate :ref:`raster.sar_ceos` driver for access to SAR CEOS " +"data products." +msgstr "" + +#: ../../source/drivers/raster/ceos.rst:22 +msgid "NOTE: Implemented as :source_file:`frmts/ceos/ceosdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/coasp.rst:5 +msgid "COASP -- DRDC COASP SAR Processor Raster" +msgstr "" + +#: ../../source/drivers/raster/coasp.rst:7 +msgid "COASP" +msgstr "" + +#: ../../source/drivers/raster/coasp.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/coasp/coasp_dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:5 +msgid "COG -- Cloud Optimized GeoTIFF generator" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:9 +msgid "COG" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:13 +msgid "This driver supports the creation of Cloud Optimized GeoTIFF (COG)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:15 +msgid "" +"It essentially relies upon the :ref:`raster.gtiff` driver with the " +"``COPY_SRC_OVERVIEWS=YES`` creation option, but automatically does the " +"needed preprocessing stages (reprojection if asked and creation of " +"overviews on imagery and/or mask) if not already done, and also takes " +"care of morphing the input dataset into the expected form when using some" +" compression types (for example a RGBA dataset will be transparently " +"converted to a RGB+mask dataset when selecting JPEG compression)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:35 +msgid "|about-creation-options|" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:38 +msgid "General creation options" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:53 +msgid "" +"``JPEG`` should generally only be used with Byte data (8 bit per " +"channel). But if GDAL is built with internal libtiff and libjpeg, it is" +" possible to read and write TIFF files with 12bit JPEG compressed TIFF" +" files (seen as UInt16 bands with NBITS=12). See the `\"8 and 12 bit JPEG" +" in TIFF\" <http://trac.osgeo.org/gdal/wiki/TIFF12BitJPEG>`__ wiki page " +"for more details. For the COG driver, JPEG compression for 3 or 4-band " +"images automatically selects the PHOTOMETRIC=YCBCR colorspace with a " +"4:2:2 subsampling of the Y,Cb,Cr components. For a input dataset (single-" +"band or 3-band), plus an alpha band, the alpha band will be converted as " +"a 1-bit DEFLATE compressed mask." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:65 +#: ../../source/drivers/raster/gtiff.rst:463 +msgid "" +"``LZW``, ``DEFLATE`` and ``ZSTD`` compressions can be used with the " +"PREDICTOR creation option." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:67 +msgid "" +"``ZSTD`` is available when using internal libtiff and if GDAL built " +"against libzstd >=1.0, or if built against external libtiff with zstd " +"support." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:70 +msgid "``LERC`` is available when using internal libtiff." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:72 +#: ../../source/drivers/raster/gtiff.rst:472 +msgid "``LERC_ZSTD`` is available when ``LERC`` and ``ZSTD`` are available." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:74 +msgid "" +"``JXL`` is for JPEG-XL, and is only available when using internal libtiff" +" and building GDAL against https://github.com/libjxl/libjxl . JXL " +"compression may only be used on datasets with 4 bands or less. Option " +"added in GDAL 3.4" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:86 +msgid "" +"For DEFLATE/LZMA, 9 is the slowest/higher compression rate (or 12 when " +"using a libtiff with libdeflate support). The default is 6." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:88 +msgid "For ZSTD, 22 is the slowest/higher compression rate. The default is 9." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:194 +#: ../../source/drivers/raster/gtiff.rst:686 +msgid "``YES`` forces BigTIFF." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:195 +#: ../../source/drivers/raster/gtiff.rst:687 +msgid "``NO`` forces classic TIFF." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:196 +#: ../../source/drivers/raster/gtiff.rst:688 +msgid "" +"``IF_NEEDED`` will only create a BigTIFF if it is clearly needed (in the " +"uncompressed case, and image larger than 4GB. So no effect when using a " +"compression)." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:199 +msgid "" +"``IF_SAFER`` will create BigTIFF if the resulting file \\*might\\* exceed" +" 4GB. Note: this is only a heuristics that might not always work " +"depending on compression ratios." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:203 +msgid "" +"BigTIFF is a TIFF variant which can contain more than 4GiB of data (size " +"of classic TIFF is limited by that value). This option is available if " +"GDAL is built with libtiff library version 4.0 or higher. The default is " +"IF_NEEDED." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:208 +msgid "" +"When creating a new GeoTIFF with no compression, GDAL computes in advance" +" the size of the resulting file. If that computed file size is over 4GiB," +" GDAL will automatically decide to create a BigTIFF file. However, when " +"compression is used, it is not possible in advance to known the final " +"size of the file, so classical TIFF will be chosen. In that case, the " +"user must explicitly require the creation of a BigTIFF with BIGTIFF=YES " +"if the final file is anticipated to be too big for classical TIFF format." +" If BigTIFF creation is not explicitly asked or guessed and the resulting" +" file is too big for classical TIFF, libtiff will fail with an error " +"message like \"TIFFAppendToStrip:Maximum TIFF file size exceeded\"." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:250 +msgid "" +"``AUTO`` (default): source overviews will be used if present. If not " +"present, overviews will be automatically generated in the output file." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:254 +msgid "" +"``IGNORE_EXISTING``: potential existing overviews on the source dataset " +"will be ignored and new overviews will be automatically generated." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:257 +msgid "" +"``FORCE_USE_EXISTING``: potential existing overviews on the source will " +"be used. If there is no source overview, this is equivalent to specifying" +" ``NONE``." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:261 +msgid "" +"``NONE``: potential source overviews will be ignored, and no overview " +"will be generated." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:266 +msgid "" +"When using the gdal_translate utility, source overviews will not be " +"available if general options (i.e. options which are not creation " +"options, like subsetting, etc.) are used." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:281 +msgid "" +"If not specified, the driver will use all the overviews available in the " +"source raster, in :co:`OVERVIEWS=AUTO` or ``FORCE_USE_EXISTING`` modes. " +"In situations where GDAL generates overviews, the default number of " +"overview levels is such that the dimensions of the smallest overview are " +"smaller or equal to the :co:`BLOCKSIZE` value." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:292 +msgid "" +"By default (``AUTO``) the overviews will be created with the same " +"compression method as the COG." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:324 +#: ../../source/drivers/raster/gtiff.rst:774 +msgid "Write support for GeoTIFF 1.1 requires libgeotiff 1.6.0 or later." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:354 +msgid "Reprojection related creation options" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:366 +msgid "" +"The tile size indicated in the tiling scheme definition (generally 256 " +"pixels) will be used, unless the user has specified a value with the " +":co:`BLOCKSIZE` creation option, in which case the user specified one " +"will be taken into account (that is if setting a higher value than 256, " +"the original tiling scheme is modified to take into account the size of " +"the HiDPi tiles)." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:372 +msgid "" +"In non-CUSTOM mode, TARGET_SRS, RES and EXTENT options are ignored. " +"Starting with GDAL 3.2, the value of :co:`TILING_SCHEME` can also be the " +"filename of a JSON file according to the `OGC Two Dimensional Tile Matrix" +" Set standard`_, a URL to such file, the radical of a definition file in " +"the GDAL data directory (e.g. ``FOO`` for a file named ``tms_FOO.json``) " +"or the inline JSON definition. The list of available tiling schemes can " +"be obtained by looking at values of the TILING_SCHEME option reported by " +"``gdalinfo --format COG``." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:441 +msgid "Update" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:443 +msgid "" +"Updating a COG file generally breaks part of the optimizations, but still" +" produces a valid GeoTIFF file. Starting with GDAL 3.8, to avoid " +"undesired loss of the COG characteristics, opening such a file in update " +"mode will be rejected, unless the IGNORE_COG_LAYOUT_BREAK open option is " +"also explicitly set to YES." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:448 +msgid "" +"Note that a subset of operations are possible when opening a COG file in " +"read-only mode, like metadata edition (including statistics storage), " +"that will be stored in a auxiliary .aux.xml side-car file." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:453 +msgid "File format details" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:456 +msgid "High level" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:458 +msgid "A Cloud optimized GeoTIFF has the following characteristics:" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:460 +msgid "TIFF or BigTIFF file" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:461 +msgid "Tiled (512 pixels by default) for imagery, mask and overviews" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:462 +msgid "" +"Overviews until the maximum dimension of the smallest overview level is " +"lower than 512 pixels." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:464 +msgid "Compressed or not" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:465 +msgid "Pixel interleaving for multi-band dataset" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:466 +msgid "" +"Optimized layout of TIFF sections to minimize the number of GET requests " +"needed by a reader doing random read access." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:470 +msgid "Low level" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:472 +msgid "" +"A COG file is organized as the following (if using libtiff >= 4.0.11 or " +"GDAL internal libtiff. For other versions, the layout will be different " +"and some of the optimizations will not be available)." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:476 +msgid "" +"TIFF/BigTIFF header/signature and pointer to first IFD (Image File " +"Directory)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:477 +msgid "\"ghost area\" with COG optimizations (see `Header ghost area`_)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:478 +msgid "" +"IFD of the full resolution image, followed by TIFF tags values, excluding" +" the TileOffsets and TileByteCounts arrays." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:480 +msgid "" +"IFD of the mask of the full resolution image, if present, followed by " +"TIFF tags values, excluding the TileOffsets and TileByteCounts arrays." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:482 +msgid "IFD of the first (largest in dimensions) overview level, if present" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:483 +#: ../../source/drivers/raster/cog.rst:486 +#: ../../source/drivers/raster/cog.rst:492 +#: ../../source/drivers/vector/selafin.rst:253 +msgid "..." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:484 +msgid "IFD of the last (smallest) overview level, if present" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:485 +msgid "" +"IFD of the first (largest in dimensions) overview level of the mask, if " +"present" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:487 +msgid "IFD of the last (smallest) overview level of the mask, if present" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:488 +msgid "TileOffsets and TileByteCounts arrays of the above IFDs" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:489 +msgid "" +"tile data of the smallest overview, if present (with each tile followed " +"by the corresponding tile of mask data, if present), with :ref:`leader " +"and trailer bytes <cog.tile_data_leader_trailer>`" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:493 +msgid "" +"tile data of the largest overview, if present (interleaved with mask data" +" if present)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:494 +msgid "" +"tile data of the full resolution image, if present (interleaved with " +"corresponding mask data if present)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:497 +msgid "Header ghost area" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:499 +msgid "" +"To describe the specific layout of COG files, a description of the " +"features used is located at the beginning of the file, so that optimized " +"readers (like GDAL) can use them and take shortcuts. Those features are " +"described as ASCII strings \"hidden\" just after the 8 first bytes of a " +"ClassicTIFF (or after the 16 first ones for a BigTIFF). That is the first" +" IFD starts just after those strings. It is completely valid to have " +"*ghost* areas like this in a TIFF file, and readers will normally skip " +"over them. So for a COG file with a transparency mask, those strings will" +" be:" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:520 +msgid "A newline character `\\\\n` is used to separate those strings." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:521 +msgid "" +"A space character is inserted after the newline following " +"`KNOWN_INCOMPATIBLE_EDITION=NO`" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:522 +msgid "" +"For a COG without mask, the `MASK_INTERLEAVED_WITH_IMAGERY` item will not" +" be present of course." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:524 +msgid "" +"The ghost area starts with ``GDAL_STRUCTURAL_METADATA_SIZE=XXXXXX " +"bytes\\n`` (of a fixed size of 43 bytes) where XXXXXX is a 6-digit number" +" indicating the remaining size of the section (that is starting after the" +" linefeed character of this starting line)." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:529 +msgid "" +"``LAYOUT=IFDS_BEFORE_DATA``: the IFDs are located at the beginning of the" +" file. GDAL will also makes sure that the tile index arrays are written " +"just after the IFDs and before the imagery, so that a first range request" +" of 16 KB will always get all the IFDs" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:534 +msgid "" +"``BLOCK_ORDER=ROW_MAJOR``: (strile is a contraction of 'strip or tile') " +"the data for tiles is written in increasing tile id order. Future " +"enhancements could possibly implement other layouts." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:538 +msgid "" +"``BLOCK_LEADER=SIZE_AS_UINT4``: each tile data is preceded by 4 bytes, in" +" a *ghost* area as well, indicating the real tile size (in little endian " +"order). See `Tile data leader and trailer`_ for more details." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:542 +msgid "" +"``BLOCK_TRAILER=LAST_4_BYTES_REPEATED``: just after the tile data, the " +"last 4 bytes of the tile data are repeated. See `Tile data leader and " +"trailer`_ for more details." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:545 +msgid "" +"``KNOWN_INCOMPATIBLE_EDITION=NO``: when a COG is generated this is always" +" written. If GDAL is then used to modify the COG file, as most of the " +"changes done on an existing COG file, will break the optimized structure," +" GDAL will change this metadata item to KNOWN_INCOMPATIBLE_EDITION=YES, " +"and issue a warning on writing, and when reopening such file, so that " +"users know they have *broken* their COG file" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:552 +msgid "" +"``MASK_INTERLEAVED_WITH_IMAGERY=YES``: indicates that mask data " +"immediately follows imagery data. So when reading data at " +"offset=TileOffset[i] - 4 and size=TileOffset[i+1]-TileOffset[i]+4, you'll" +" get a buffer with:" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:556 +msgid "leader with imagery tile size (4 bytes)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:557 +msgid "imagery data (starting at TileOffsets[i] and of size TileByteCounts[i])" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:558 +msgid "trailer of imagery (4 bytes)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:559 +msgid "leader with mask tilesize (4 bytes)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:560 +msgid "" +"mask data (starting at mask.TileOffsets[i] and of size " +"mask.TileByteCounts[i], but none of them actually need to be read)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:562 +msgid "trailer of mask data (4 bytes)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:566 +msgid "" +"The content of the header ghost area can be retrieved by getting the " +"``GDAL_STRUCTURAL_METADATA`` metadata item of the ``TIFF`` metadata " +"domain on the datasett object (with GetMetadataItem())" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:573 +msgid "Tile data leader and trailer" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:575 +msgid "" +"Each tile data is immediately preceded by a leader, consisting of a " +"unsigned 4-byte integer, in little endian order, giving the number of " +"bytes of *payload* of the tile data that follows it. This leader is " +"*ghost* in the sense that the TileOffsets[] array does not point to it, " +"but points to the real payload. Hence the offset of the leader is " +"TileOffsets[i]-4." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:581 +msgid "" +"An optimized reader seeing the ``BLOCK_LEADER=SIZE_AS_UINT4`` metadata " +"item will thus look for TileOffset[i] and TileOffset[i+1] to deduce it " +"must fetch the data starting at offset=TileOffset[i] - 4 and of " +"size=TileOffset[i+1]-TileOffset[i]+4. It then checks the 4 first bytes to" +" see if the size in this leader marker is consistent with " +"TileOffset[i+1]-TileOffset[i]. When there is no mask, they should " +"normally be equal (modulo the size taken by BLOCK_LEADER and " +"BLOCK_TRAILER). In the case where there is a mask and " +"MASK_INTERLEAVED_WITH_IMAGERY=YES, then the tile size indicated in the " +"leader will be < TileOffset[i+1]-TileOffset[i] since the data for the " +"mask will follow the imagery data (see MASK_INTERLEAVED_WITH_IMAGERY=YES)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:592 +msgid "" +"Each tile data is immediately followed by a trailer, consisting of the " +"repetition of the last 4 bytes of the payload of the tile data. The size " +"of this trailer is *not* included in the TileByteCounts[] array. The " +"purpose of this trailer is forces readers to be able to check if TIFF " +"writers, not aware of those optimizations, have modified the TIFF file " +"in a way that breaks the optimizations. If an optimized reader detects an" +" inconsistency, it can then fallbacks to the regular/slower method of " +"using TileOffsets[i] + TileByteCounts[i]." +msgstr "" + +#: ../../source/drivers/raster/cog.rst:601 +#: ../../source/drivers/raster/eedai.rst:163 +#: ../../source/drivers/raster/fits.rst:282 +#: ../../source/drivers/raster/gpkg.rst:739 +#: ../../source/drivers/raster/grib.rst:446 +#: ../../source/drivers/raster/isis3.rst:309 +#: ../../source/drivers/raster/ngw.rst:201 +#: ../../source/drivers/raster/openfilegdb.rst:83 +#: ../../source/drivers/raster/pdf.rst:774 +#: ../../source/drivers/raster/plmosaic.rst:108 +#: ../../source/drivers/raster/postgisraster.rst:108 +#: ../../source/drivers/raster/rasterlite.rst:184 +#: ../../source/drivers/raster/rasterlite2.rst:144 +#: ../../source/drivers/raster/safe.rst:54 +#: ../../source/drivers/raster/sentinel2.rst:198 +#: ../../source/drivers/raster/stacit.rst:106 +#: ../../source/drivers/raster/vrt.rst:1392 +#: ../../source/drivers/raster/wcs.rst:285 +#: ../../source/drivers/raster/wms.rst:382 +#: ../../source/drivers/raster/zarr.rst:511 +#: ../../source/drivers/vector/amigocloud.rst:140 +#: ../../source/drivers/vector/carto.rst:209 +#: ../../source/drivers/vector/csv.rst:517 +#: ../../source/drivers/vector/csw.rst:97 +#: ../../source/drivers/vector/eeda.rst:182 +#: ../../source/drivers/vector/elasticsearch.rst:664 +#: ../../source/drivers/vector/flatgeobuf.rst:104 +#: ../../source/drivers/vector/geoconcept.rst:171 +#: ../../source/drivers/vector/geojson.rst:522 +#: ../../source/drivers/vector/gml.rst:1348 +#: ../../source/drivers/vector/gmlas.rst:449 +#: ../../source/drivers/vector/gpkg.rst:763 +#: ../../source/drivers/vector/gpsbabel.rst:111 +#: ../../source/drivers/vector/hana.rst:272 +#: ../../source/drivers/vector/libkml.rst:959 +#: ../../source/drivers/vector/lvbag.rst:65 +#: ../../source/drivers/vector/miramon.rst:327 +#: ../../source/drivers/vector/mongodbv3.rst:284 +#: ../../source/drivers/vector/mssqlspatial.rst:289 +#: ../../source/drivers/vector/mvt.rst:430 +#: ../../source/drivers/vector/ngw.rst:367 +#: ../../source/drivers/vector/oapif.rst:145 +#: ../../source/drivers/vector/ogdi.rst:82 +#: ../../source/drivers/vector/openfilegdb.rst:344 +#: ../../source/drivers/vector/pg.rst:479 +#: ../../source/drivers/vector/pmtiles.rst:341 +#: ../../source/drivers/vector/shapefile.rst:455 +#: ../../source/drivers/vector/sosi.rst:29 +#: ../../source/drivers/vector/vfk.rst:112 +#: ../../source/drivers/vector/wfs.rst:390 +#: ../../source/drivers/vector/xlsx.rst:96 +#: ../../source/drivers/vector/xodr.rst:78 +msgid "Examples" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:614 +msgid ":ref:`raster.gtiff` driver" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:615 +msgid "" +"`How to generate and read cloud optimized GeoTIFF files " +"<https://trac.osgeo.org/gdal/wiki/CloudOptimizedGeoTIFF>`__ (before GDAL " +"3.1)" +msgstr "" + +#: ../../source/drivers/raster/cog.rst:617 +msgid "" +"If your source dataset is an internally tiled geotiff with the desired " +"georeferencing and compression, using `cogger " +"<https://github.com/airbusgeo/cogger>`__ (possibly along with gdaladdo to" +" create overviews) will be much faster than the COG driver." +msgstr "" + +#: ../../source/drivers/raster/cosar.rst:5 +msgid "COSAR -- TerraSAR-X Complex SAR Data Product" +msgstr "" + +#: ../../source/drivers/raster/cosar.rst:7 +msgid "COSAR" +msgstr "" + +#: ../../source/drivers/raster/cosar.rst:11 +msgid "" +"This driver provides the capability to read TerraSAR-X complex data. " +"While most users will receive products in GeoTIFF format (representing " +"detected radiation reflected from the targets, or geocoded data), ScanSAR" +" products will be distributed in COSAR format." +msgstr "" + +#: ../../source/drivers/raster/cosar.rst:16 +msgid "" +"Essentially, COSAR is an annotated binary matrix, with each sample held " +"in 4 bytes (16 bits real, 16 bits imaginary) stored with the most " +"significant byte first (Big Endian). Within a COSAR container there are " +"one or more \"bursts\" which represent individual ScanSAR bursts. Note " +"that if a Stripmap or Spotlight product is held in a COSAR container it " +"is stored in a single burst." +msgstr "" + +#: ../../source/drivers/raster/cosar.rst:23 +msgid "" +"Support for ScanSAR data is currently under way, due to the difficulties " +"in fitting the ScanSAR \"burst\" identifiers into the GDAL model." +msgstr "" + +#: ../../source/drivers/raster/cosar.rst:34 +msgid "DLR Document TX-GS-DD-3307 \"Level 1b Product Format Specification.\"" +msgstr "" + +#: ../../source/drivers/raster/cpg.rst:5 +msgid "CPG -- Convair PolGASP data" +msgstr "" + +#: ../../source/drivers/raster/cpg.rst:7 +msgid "CPG" +msgstr "" + +#: ../../source/drivers/raster/cpg.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/raw/cpgdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ctable2.rst:5 +msgid "CTable2 -- CTable2 Datum Grid Shift" +msgstr "" + +#: ../../source/drivers/raster/ctable2.rst:7 +msgid "CTable2" +msgstr "" + +#: ../../source/drivers/raster/ctable2.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/raw/ctable2dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:5 +msgid "CTG -- USGS LULC Composite Theme Grid" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:7 +msgid "CTG" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:11 +msgid "" +"This driver can read USGS Land Use and Land Cover (LULC) grids encoded in" +" the Character Composite Theme Grid (CTG) format. Each file is reported " +"as a 6-band dataset of type Int32. The meaning of each band is the " +"following one :" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:16 +msgid "Land Use and Land Cover Code" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:17 +msgid "Political units Code" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:18 +msgid "Census county subdivisions and SMSA tracts Code" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:19 +msgid "Hydrologic units Code" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:20 +msgid "Federal land ownership Code" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:21 +msgid "State land ownership Code" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:23 +msgid "" +"Those files are typically named grid_cell.gz, grid_cell1.gz or " +"grid_cell2.gz on the USGS site." +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:26 +msgid "" +"`Land Use and Land Cover Digital Data (Data Users Guide 4) " +"<http://edc2.usgs.gov/geodata/LULC/LULCDataUsersGuide.pdf>`__ - PDF " +"version from USGS" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:29 +msgid "" +"`Land Use and Land Cover Digital Data (Data Users Guide 4) " +"<http://www.vterrain.org/Culture/LULC/Data_Users_Guide_4.html>`__ - HTML " +"version converted by Ben Discoe" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:32 +msgid "" +"`USGS LULC data at 250K and 100K " +"<http://edcftp.cr.usgs.gov/pub/data/LULC>`__" +msgstr "" + +#: ../../source/drivers/raster/ctg.rst:35 +msgid "NOTE: Implemented as :source_file:`frmts/ctg/ctgdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:5 +#: ../../source/drivers/raster/driver_summary.rst:144 +msgid "DAAS (Airbus DS Intelligence Data As A Service driver)" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:7 +msgid "DAAS" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:11 +#: ../../source/drivers/raster/driver_summary.rst:148 +#: ../../source/drivers/raster/driver_summary.rst:208 +#: ../../source/drivers/raster/driver_summary.rst:628 +#: ../../source/drivers/raster/driver_summary.rst:670 +#: ../../source/drivers/raster/driver_summary.rst:730 +#: ../../source/drivers/raster/driver_summary.rst:958 +#: ../../source/drivers/raster/driver_summary.rst:970 +#: ../../source/drivers/raster/driver_summary.rst:976 +#: ../../source/drivers/raster/eedai.rst:11 +#: ../../source/drivers/raster/ngw.rst:10 +#: ../../source/drivers/raster/ogcapi.rst:11 +#: ../../source/drivers/raster/plmosaic.rst:9 +#: ../../source/drivers/raster/wcs.rst:9 ../../source/drivers/raster/wms.rst:9 +#: ../../source/drivers/raster/wmts.rst:11 +#: ../../source/drivers/vector/amigocloud.rst:11 +#: ../../source/drivers/vector/carto.rst:9 +#: ../../source/drivers/vector/csw.rst:8 +#: ../../source/drivers/vector/driver_summary.rst:20 +#: ../../source/drivers/vector/driver_summary.rst:45 +#: ../../source/drivers/vector/driver_summary.rst:55 +#: ../../source/drivers/vector/driver_summary.rst:85 +#: ../../source/drivers/vector/driver_summary.rst:90 +#: ../../source/drivers/vector/driver_summary.rst:270 +#: ../../source/drivers/vector/driver_summary.rst:280 +#: ../../source/drivers/vector/driver_summary.rst:345 +#: ../../source/drivers/vector/driver_summary.rst:430 +#: ../../source/drivers/vector/eeda.rst:10 +#: ../../source/drivers/vector/elasticsearch.rst:8 +#: ../../source/drivers/vector/ngw.rst:10 +#: ../../source/drivers/vector/oapif.rst:10 +#: ../../source/drivers/vector/plscenes.rst:8 +#: ../../source/drivers/vector/wfs.rst:8 +msgid "libcurl" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:13 +msgid "" +"This driver can connect to the Airbus DS Intelligence Data As A Service " +"API. GDAL/OGR must be built with Curl support in order for the DAAS " +"driver to be compiled." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:17 +msgid "" +"Orthorectified (with geotransform) and raw (with RPCs) images are " +"supported." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:20 +msgid "Overviews are supported." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:22 +msgid "" +"The API is not publicly available but will be released soon. Further " +"information will be found here: https://api.oneatlas.airbus.com/" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:31 +#: ../../source/drivers/raster/eedai.rst:22 +#: ../../source/drivers/raster/ngw.rst:65 +#: ../../source/drivers/raster/plmosaic.rst:28 +#: ../../source/drivers/vector/amigocloud.rst:28 +#: ../../source/drivers/vector/carto.rst:24 +#: ../../source/drivers/vector/csw.rst:24 +#: ../../source/drivers/vector/eeda.rst:21 +#: ../../source/drivers/vector/mongodbv3.rst:34 +#: ../../source/drivers/vector/ngw.rst:48 +#: ../../source/drivers/vector/oapif.rst:27 +#: ../../source/drivers/vector/plscenes_data_v1.rst:19 +#: ../../source/drivers/vector/wfs.rst:27 +msgid "Dataset name syntax" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:33 +msgid "The nominal syntax to open a datasource is :" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:39 +msgid "A more minimal syntax can be used:" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:45 +msgid "provided that the GET_METADATA_URL open option is filled." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:48 +#: ../../source/drivers/raster/ngw.rst:115 +#: ../../source/drivers/vector/amigocloud.rst:59 +#: ../../source/drivers/vector/carto.rst:43 +#: ../../source/drivers/vector/ngw.rst:100 +msgid "Authentication" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:50 +msgid "" +"Access to the API requires an authentication token. There are two methods" +" supported:" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:53 +msgid "" +"Authentication with an API key and a client id. They must be provided " +"respectively with the :oo:`API_KEY` open option (or " +":config:`GDAL_DAAS_API_KEY` configuration option) and the :oo:`CLIENT_ID`" +" open option (or :config:`GDAL_DAAS_CLIENT_ID` configuration option). In " +"that case, the driver will authenticate against the authentication " +"endpoint to get an access token." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:59 +msgid "" +"Directly providing the access token with the :oo:`ACCESS_TOKEN` open " +"option (or :config:`GDAL_DAAS_ACCESS_TOKEN` configuration option)." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:62 +msgid "" +"In both cases, the :oo:`X_FORWARDED_USER` open option (or " +":config:`GDAL_DAAS_X_FORWARDED_USER` configuration option) can be " +"specified to fill the HTTP X-Forwarded-User header in requests sent to " +"the DAAS service endpoint with the user from which the request originates" +" from." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:67 +msgid "" +"See https://api.oneatlas.airbus.com/guides/g-authentication/ for further " +"details" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:71 +#: ../../source/drivers/raster/dted.rst:26 +#: ../../source/drivers/raster/eedai.rst:82 +#: ../../source/drivers/raster/grib.rst:94 +#: ../../source/drivers/raster/gtiff.rst:913 +#: ../../source/drivers/raster/jpeg.rst:90 +#: ../../source/drivers/raster/mbtiles.rst:64 +#: ../../source/drivers/raster/ngw.rst:83 +#: ../../source/drivers/raster/pdf.rst:56 +#: ../../source/drivers/raster/pds.rst:40 +#: ../../source/drivers/raster/plmosaic.rst:69 +#: ../../source/drivers/raster/rasterlite.rst:137 +#: ../../source/drivers/raster/stacta.rst:25 +#: ../../source/drivers/raster/wms.rst:354 +#: ../../source/drivers/vector/amigocloud.rst:125 +#: ../../source/drivers/vector/carto.rst:180 +#: ../../source/drivers/vector/csv.rst:493 +#: ../../source/drivers/vector/csw.rst:89 +#: ../../source/drivers/vector/dwg.rst:39 +#: ../../source/drivers/vector/edigeo.rst:39 +#: ../../source/drivers/vector/eeda.rst:63 +#: ../../source/drivers/vector/elasticsearch.rst:622 +#: ../../source/drivers/vector/filegdb.rst:244 +#: ../../source/drivers/vector/geojson.rst:151 +#: ../../source/drivers/vector/geojsonseq.rst:56 +#: ../../source/drivers/vector/gml.rst:36 +#: ../../source/drivers/vector/gpkg.rst:485 +#: ../../source/drivers/vector/gpx.rst:52 +#: ../../source/drivers/vector/idb.rst:56 +#: ../../source/drivers/vector/jsonfg.rst:84 +#: ../../source/drivers/vector/mitab.rst:186 +#: ../../source/drivers/vector/mssqlspatial.rst:216 +#: ../../source/drivers/vector/ngw.rst:65 +#: ../../source/drivers/vector/oci.rst:125 +#: ../../source/drivers/vector/ods.rst:62 +#: ../../source/drivers/vector/ogdi.rst:68 +#: ../../source/drivers/vector/openfilegdb.rst:83 +#: ../../source/drivers/vector/osm.rst:85 +#: ../../source/drivers/vector/pdf.rst:91 +#: ../../source/drivers/vector/pgeo.rst:59 +#: ../../source/drivers/vector/plscenes_data_v1.rst:121 +#: ../../source/drivers/vector/shapefile.rst:412 +#: ../../source/drivers/vector/sqlite.rst:425 +#: ../../source/drivers/vector/vfk.rst:52 +#: ../../source/drivers/vector/wasp.rst:23 +#: ../../source/drivers/vector/wfs.rst:364 +#: ../../source/drivers/vector/xls.rst:20 +#: ../../source/drivers/vector/xlsx.rst:71 +msgid "Configuration options" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:73 +#: ../../source/drivers/raster/eedai.rst:84 +#: ../../source/drivers/raster/jpeg.rst:92 +#: ../../source/drivers/raster/plmosaic.rst:71 +msgid "|about-config-options| The following configuration options are available :" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:95 +#: ../../source/drivers/raster/eedai.rst:38 +msgid "|about-open-options| The following open options are available :" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:139 +msgid "" +"**AUTO**: for 1, 3 or 4-band images of type Byte, resolves to PNG. " +"Otherwise to RAW" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:141 +msgid "" +"**RAW**: compatible of all images. Pixels are requested in a uncompressed" +" raw format." +msgstr "" + +#: ../../source/drivers/raster/daas.rst:143 +msgid "**PNG**: compatible of 1, 3 or 4-band images of type Byte" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:144 +msgid "**JPEG**: compatible of 1 or 3-band images of type Byte" +msgstr "" + +#: ../../source/drivers/raster/daas.rst:145 +msgid "" +"**JPEG2000**: compatible of all images. Requires GDAL to be built with " +"one of its JPEG2000-capable drivers." +msgstr "" + +#: ../../source/drivers/raster/dds.rst:5 +msgid "DDS -- DirectDraw Surface" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:7 +msgid "DDS" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:9 +#: ../../source/drivers/raster/driver_summary.rst:154 +msgid "Crunch Lib" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:11 +msgid "" +"The DirectDraw Surface file format (uses the filename extension DDS), " +"from Microsoft, is a standard for storing data compressed with the lossy " +"S3 Texture Compression (S3TC) algorithm. The DDS format and compression " +"are provided by the crunch library." +msgstr "" + +#: ../../source/drivers/raster/dds.rst:17 +msgid "" +"Support for reading has been added in GDAL 3.1. Previous versions have " +"write-only support." +msgstr "" + +#: ../../source/drivers/raster/dds.rst:20 +msgid "" +"The driver supports the following texture formats: DXT1, DXT1A, DXT3 " +"(default), DXT5 and ETC1. You can set the texture format using the " +"creation option FORMAT." +msgstr "" + +#: ../../source/drivers/raster/dds.rst:24 +msgid "" +"The driver supports the following compression quality: SUPERFAST, FAST, " +"NORMAL (default), BETTER and UBER. You can set the compression quality " +"using the creation option QUALITY." +msgstr "" + +#: ../../source/drivers/raster/dds.rst:28 +msgid "" +"More information about `Crunch Lib " +"<https://github.com/BinomialLLC/crunch>`__ (see below for build " +"instructions of a working fork of that repository)" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:31 +msgid "NOTE: Implemented as :source_file:`frmts/dds/ddsdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/dds.rst:42 +msgid "" +"Building crunch can be a bit difficult. The `build_fixes` branch of " +"https://github.com/rouault/crunch/ includes a CMake build system, as well" +" as a few fixes that are not found in the upstream repository" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:47 +msgid "Build crunch" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:50 +#: ../../source/drivers/raster/dds.rst:77 +#: ../../source/drivers/raster/fits.rst:351 +msgid "Linux" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:62 +#: ../../source/drivers/raster/dds.rst:84 +msgid "Windows" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:74 +msgid "Build GDAL against crunch" +msgstr "" + +#: ../../source/drivers/raster/dds.rst:86 +msgid "In nmake.local, add the following lines:" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:5 +msgid "DERIVED -- Derived subdatasets driver" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:7 +msgid "DERIVED" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:11 +msgid "" +"This driver allows accessing subdatasets derived from a given dataset. " +"Those derived datasets have the same projection reference, geo-transform " +"and metadata than the original dataset, but derives new pixel values " +"using gdal pixel functions." +msgstr "" + +#: ../../source/drivers/raster/derived.rst:17 +msgid "Available functions" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:19 +msgid "Available derived datasets are:" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:21 +msgid "AMPLITUDE: Amplitude of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:22 +msgid "PHASE: Phase of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:23 +msgid "REAL: Real part of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:24 +msgid "IMAG: Imaginary part of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:25 +msgid "CONJ: Conjugate of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:26 +msgid "INTENSITY: Intensity (squared amplitude) of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:27 +msgid "LOGAMPLITUDE: Log10 of amplitude of pixels from input bands" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:29 +msgid "Note: for non-complex data types, only LOGAMPLITUDE will be listed." +msgstr "" + +#: ../../source/drivers/raster/derived.rst:31 +msgid "" +"A typical use is to directly access amplitude, phase or log-amplitude of " +"any complex dataset." +msgstr "" + +#: ../../source/drivers/raster/derived.rst:35 +msgid "Accessing derived subdatasets" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:37 +msgid "" +"Derived subdatasets are stored in the DERIVED_SUBDATASETS metadata " +"domain, and can be accessed using the following syntax:" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:44 +msgid "" +"where function is one of AMPLITUDE, PHASE, REAL, IMAG, CONJ, INTENSITY, " +"LOGAMPLITUDE. So as to ensure numerical precision, all derived " +"subdatasets bands will have Float64 or CFloat64 precision (depending on " +"the function used)." +msgstr "" + +#: ../../source/drivers/raster/derived.rst:49 +msgid "For instance:" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:164 +msgid "Listing available subdatasets" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:166 +msgid "" +"Available subdatasets are reported in the DERIVED_SUBDATASETS metadata " +"domain. Only functions that make sense will be reported for a given " +"dataset, which means that AMPLITUDE, PHASE, REAL, IMAG, CONJ and " +"INTENSITY will only be reported if the dataset has at least one complex " +"band. Nevertheless, even if not reported, those derived datasets are " +"still reachable with the syntax presented above." +msgstr "" + +#: ../../source/drivers/raster/derived.rst:247 +#: ../../source/drivers/raster/grib.rst:456 +#: ../../source/drivers/raster/leveller.rst:74 +#: ../../source/drivers/raster/map.rst:21 +#: ../../source/drivers/raster/mrsid.rst:67 +#: ../../source/drivers/raster/netcdf.rst:735 +#: ../../source/drivers/raster/pcidsk.rst:69 +#: ../../source/drivers/raster/pds4.rst:547 +#: ../../source/drivers/raster/r.rst:48 ../../source/drivers/raster/rmf.rst:112 +#: ../../source/drivers/raster/rpftoc.rst:55 +#: ../../source/drivers/raster/sgi.rst:21 +#: ../../source/drivers/raster/srtmhgt.rst:24 +#: ../../source/drivers/raster/zarr.rst:540 +#: ../../source/drivers/vector/eeda.rst:209 +#: ../../source/drivers/vector/mvt.rst:440 +msgid "See Also:" +msgstr "" + +#: ../../source/drivers/raster/derived.rst:249 +msgid "" +":ref:`Using Derived Bands part of the GDAL VRT tutorial " +"<vrt_derived_bands>`" +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:5 +msgid "DIMAP -- Spot DIMAP" +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:7 +msgid "DIMAP" +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:11 +msgid "" +"This is a read-only read for Spot DIMAP described images. To use, select " +"the METADATA.DIM (DIMAP 1), VOL_PHR.XML (DIMAP 2) or VOL_PNEO.XML (DIMAP " +"2 VHR-2020) file in a product directory, or the product directory itself." +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:15 +msgid "" +"The imagery is in a distinct imagery file, often a TIFF file, but the " +"DIMAP dataset handles accessing that file, and attaches geolocation and " +"other metadata to the dataset from the metadata xml file." +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:19 +msgid "" +"The content of the <Spectral_Band_Info> node is reported as metadata at " +"the level of the raster band. Note that the content of the " +"Spectral_Band_Info of the first band is still reported as metadata of the" +" dataset, but this should be considered as a deprecated way of getting " +"this information." +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:25 +msgid "" +"For multi-component products, each component will be exposed in a " +"subdataset." +msgstr "" + +#: ../../source/drivers/raster/dimap.rst:27 +msgid "NOTE: Implemented as :source_file:`frmts/dimap/dimapdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/dipex.rst:5 +msgid "DIPEx -- ELAS DIPEx" +msgstr "" + +#: ../../source/drivers/raster/dipex.rst:7 +msgid "DIPEx" +msgstr "" + +#: ../../source/drivers/raster/dipex.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/raw/dipxdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/doq1.rst:5 +msgid "DOQ1 -- First Generation USGS DOQ" +msgstr "" + +#: ../../source/drivers/raster/doq1.rst:7 +msgid "DOQ1" +msgstr "" + +#: ../../source/drivers/raster/doq1.rst:11 +msgid "" +"Support for read access, including reading of an affine georeferencing " +"transform, and capture of the projection string. This format is the old, " +"unlabelled DOQ (Digital Ortho Quad) format from the USGS." +msgstr "" + +#: ../../source/drivers/raster/doq1.rst:15 +msgid "NOTE: Implemented as :source_file:`frmts/raw/doq1dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/doq2.rst:5 +msgid "DOQ2 -- New Labelled USGS DOQ" +msgstr "" + +#: ../../source/drivers/raster/doq2.rst:7 +msgid "DOQ2" +msgstr "" + +#: ../../source/drivers/raster/doq2.rst:11 +msgid "" +"Support for read access, including reading of an affine georeferencing " +"transform, capture of the projection string and reading of other " +"auxiliary fields as metadata. This format is the new, labelled DOQ " +"(Digital Ortho Quad) format from the USGS." +msgstr "" + +#: ../../source/drivers/raster/doq2.rst:16 +msgid "This driver was implemented by Derrick J Brashear." +msgstr "" + +#: ../../source/drivers/raster/doq2.rst:18 +msgid "NOTE: Implemented as :source_file:`frmts/raw/doq2dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/doq2.rst:20 +msgid "" +"See Also: `USGS DOQ Standards " +"<http://rockyweb.cr.usgs.gov/nmpstds/doqstds.html>`__" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:11 +#: ../../source/drivers/vector/driver_summary.rst:11 +msgid "Short name" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:12 +#: ../../source/drivers/vector/driver_summary.rst:12 +msgid "Long name" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:13 +msgid "Creation (1)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:14 +msgid "Copy (2)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:15 +#: ../../source/drivers/vector/driver_summary.rst:14 +msgid "Geo-referencing" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:16 +#: ../../source/drivers/vector/driver_summary.rst:15 +msgid "Build requirements" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:17 +msgid ":ref:`AAIGrid <raster.aaigrid>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:18 +msgid "Arc/Info ASCII Grid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:19 +#: ../../source/drivers/raster/driver_summary.rst:25 +#: ../../source/drivers/raster/driver_summary.rst:26 +#: ../../source/drivers/raster/driver_summary.rst:37 +#: ../../source/drivers/raster/driver_summary.rst:38 +#: ../../source/drivers/raster/driver_summary.rst:43 +#: ../../source/drivers/raster/driver_summary.rst:44 +#: ../../source/drivers/raster/driver_summary.rst:45 +#: ../../source/drivers/raster/driver_summary.rst:55 +#: ../../source/drivers/raster/driver_summary.rst:57 +#: ../../source/drivers/raster/driver_summary.rst:61 +#: ../../source/drivers/raster/driver_summary.rst:73 +#: ../../source/drivers/raster/driver_summary.rst:74 +#: ../../source/drivers/raster/driver_summary.rst:91 +#: ../../source/drivers/raster/driver_summary.rst:92 +#: ../../source/drivers/raster/driver_summary.rst:97 +#: ../../source/drivers/raster/driver_summary.rst:99 +#: ../../source/drivers/raster/driver_summary.rst:103 +#: ../../source/drivers/raster/driver_summary.rst:104 +#: ../../source/drivers/raster/driver_summary.rst:105 +#: ../../source/drivers/raster/driver_summary.rst:109 +#: ../../source/drivers/raster/driver_summary.rst:110 +#: ../../source/drivers/raster/driver_summary.rst:111 +#: ../../source/drivers/raster/driver_summary.rst:115 +#: ../../source/drivers/raster/driver_summary.rst:121 +#: ../../source/drivers/raster/driver_summary.rst:122 +#: ../../source/drivers/raster/driver_summary.rst:123 +#: ../../source/drivers/raster/driver_summary.rst:127 +#: ../../source/drivers/raster/driver_summary.rst:128 +#: ../../source/drivers/raster/driver_summary.rst:139 +#: ../../source/drivers/raster/driver_summary.rst:140 +#: ../../source/drivers/raster/driver_summary.rst:145 +#: ../../source/drivers/raster/driver_summary.rst:146 +#: ../../source/drivers/raster/driver_summary.rst:151 +#: ../../source/drivers/raster/driver_summary.rst:153 +#: ../../source/drivers/raster/driver_summary.rst:157 +#: ../../source/drivers/raster/driver_summary.rst:158 +#: ../../source/drivers/raster/driver_summary.rst:159 +#: ../../source/drivers/raster/driver_summary.rst:163 +#: ../../source/drivers/raster/driver_summary.rst:164 +#: ../../source/drivers/raster/driver_summary.rst:169 +#: ../../source/drivers/raster/driver_summary.rst:170 +#: ../../source/drivers/raster/driver_summary.rst:175 +#: ../../source/drivers/raster/driver_summary.rst:176 +#: ../../source/drivers/raster/driver_summary.rst:181 +#: ../../source/drivers/raster/driver_summary.rst:182 +#: ../../source/drivers/raster/driver_summary.rst:187 +#: ../../source/drivers/raster/driver_summary.rst:193 +#: ../../source/drivers/raster/driver_summary.rst:194 +#: ../../source/drivers/raster/driver_summary.rst:205 +#: ../../source/drivers/raster/driver_summary.rst:206 +#: ../../source/drivers/raster/driver_summary.rst:217 +#: ../../source/drivers/raster/driver_summary.rst:218 +#: ../../source/drivers/raster/driver_summary.rst:241 +#: ../../source/drivers/raster/driver_summary.rst:242 +#: ../../source/drivers/raster/driver_summary.rst:243 +#: ../../source/drivers/raster/driver_summary.rst:247 +#: ../../source/drivers/raster/driver_summary.rst:248 +#: ../../source/drivers/raster/driver_summary.rst:259 +#: ../../source/drivers/raster/driver_summary.rst:260 +#: ../../source/drivers/raster/driver_summary.rst:265 +#: ../../source/drivers/raster/driver_summary.rst:277 +#: ../../source/drivers/raster/driver_summary.rst:278 +#: ../../source/drivers/raster/driver_summary.rst:279 +#: ../../source/drivers/raster/driver_summary.rst:289 +#: ../../source/drivers/raster/driver_summary.rst:290 +#: ../../source/drivers/raster/driver_summary.rst:291 +#: ../../source/drivers/raster/driver_summary.rst:295 +#: ../../source/drivers/raster/driver_summary.rst:297 +#: ../../source/drivers/raster/driver_summary.rst:307 +#: ../../source/drivers/raster/driver_summary.rst:308 +#: ../../source/drivers/raster/driver_summary.rst:309 +#: ../../source/drivers/raster/driver_summary.rst:313 +#: ../../source/drivers/raster/driver_summary.rst:314 +#: ../../source/drivers/raster/driver_summary.rst:319 +#: ../../source/drivers/raster/driver_summary.rst:331 +#: ../../source/drivers/raster/driver_summary.rst:343 +#: ../../source/drivers/raster/driver_summary.rst:344 +#: ../../source/drivers/raster/driver_summary.rst:345 +#: ../../source/drivers/raster/driver_summary.rst:349 +#: ../../source/drivers/raster/driver_summary.rst:355 +#: ../../source/drivers/raster/driver_summary.rst:356 +#: ../../source/drivers/raster/driver_summary.rst:357 +#: ../../source/drivers/raster/driver_summary.rst:367 +#: ../../source/drivers/raster/driver_summary.rst:368 +#: ../../source/drivers/raster/driver_summary.rst:379 +#: ../../source/drivers/raster/driver_summary.rst:380 +#: ../../source/drivers/raster/driver_summary.rst:385 +#: ../../source/drivers/raster/driver_summary.rst:386 +#: ../../source/drivers/raster/driver_summary.rst:387 +#: ../../source/drivers/raster/driver_summary.rst:391 +#: ../../source/drivers/raster/driver_summary.rst:415 +#: ../../source/drivers/raster/driver_summary.rst:416 +#: ../../source/drivers/raster/driver_summary.rst:427 +#: ../../source/drivers/raster/driver_summary.rst:428 +#: ../../source/drivers/raster/driver_summary.rst:445 +#: ../../source/drivers/raster/driver_summary.rst:446 +#: ../../source/drivers/raster/driver_summary.rst:457 +#: ../../source/drivers/raster/driver_summary.rst:463 +#: ../../source/drivers/raster/driver_summary.rst:469 +#: ../../source/drivers/raster/driver_summary.rst:475 +#: ../../source/drivers/raster/driver_summary.rst:481 +#: ../../source/drivers/raster/driver_summary.rst:487 +#: ../../source/drivers/raster/driver_summary.rst:493 +#: ../../source/drivers/raster/driver_summary.rst:494 +#: ../../source/drivers/raster/driver_summary.rst:505 +#: ../../source/drivers/raster/driver_summary.rst:513 +#: ../../source/drivers/raster/driver_summary.rst:517 +#: ../../source/drivers/raster/driver_summary.rst:519 +#: ../../source/drivers/raster/driver_summary.rst:523 +#: ../../source/drivers/raster/driver_summary.rst:524 +#: ../../source/drivers/raster/driver_summary.rst:530 +#: ../../source/drivers/raster/driver_summary.rst:535 +#: ../../source/drivers/raster/driver_summary.rst:547 +#: ../../source/drivers/raster/driver_summary.rst:548 +#: ../../source/drivers/raster/driver_summary.rst:553 +#: ../../source/drivers/raster/driver_summary.rst:554 +#: ../../source/drivers/raster/driver_summary.rst:589 +#: ../../source/drivers/raster/driver_summary.rst:590 +#: ../../source/drivers/raster/driver_summary.rst:595 +#: ../../source/drivers/raster/driver_summary.rst:596 +#: ../../source/drivers/raster/driver_summary.rst:601 +#: ../../source/drivers/raster/driver_summary.rst:602 +#: ../../source/drivers/raster/driver_summary.rst:607 +#: ../../source/drivers/raster/driver_summary.rst:608 +#: ../../source/drivers/raster/driver_summary.rst:619 +#: ../../source/drivers/raster/driver_summary.rst:620 +#: ../../source/drivers/raster/driver_summary.rst:625 +#: ../../source/drivers/raster/driver_summary.rst:626 +#: ../../source/drivers/raster/driver_summary.rst:637 +#: ../../source/drivers/raster/driver_summary.rst:638 +#: ../../source/drivers/raster/driver_summary.rst:643 +#: ../../source/drivers/raster/driver_summary.rst:644 +#: ../../source/drivers/raster/driver_summary.rst:667 +#: ../../source/drivers/raster/driver_summary.rst:668 +#: ../../source/drivers/raster/driver_summary.rst:673 +#: ../../source/drivers/raster/driver_summary.rst:674 +#: ../../source/drivers/raster/driver_summary.rst:679 +#: ../../source/drivers/raster/driver_summary.rst:680 +#: ../../source/drivers/raster/driver_summary.rst:685 +#: ../../source/drivers/raster/driver_summary.rst:686 +#: ../../source/drivers/raster/driver_summary.rst:693 +#: ../../source/drivers/raster/driver_summary.rst:709 +#: ../../source/drivers/raster/driver_summary.rst:715 +#: ../../source/drivers/raster/driver_summary.rst:716 +#: ../../source/drivers/raster/driver_summary.rst:727 +#: ../../source/drivers/raster/driver_summary.rst:728 +#: ../../source/drivers/raster/driver_summary.rst:733 +#: ../../source/drivers/raster/driver_summary.rst:741 +#: ../../source/drivers/raster/driver_summary.rst:745 +#: ../../source/drivers/raster/driver_summary.rst:751 +#: ../../source/drivers/raster/driver_summary.rst:752 +#: ../../source/drivers/raster/driver_summary.rst:753 +#: ../../source/drivers/raster/driver_summary.rst:757 +#: ../../source/drivers/raster/driver_summary.rst:759 +#: ../../source/drivers/raster/driver_summary.rst:763 +#: ../../source/drivers/raster/driver_summary.rst:769 +#: ../../source/drivers/raster/driver_summary.rst:775 +#: ../../source/drivers/raster/driver_summary.rst:776 +#: ../../source/drivers/raster/driver_summary.rst:781 +#: ../../source/drivers/raster/driver_summary.rst:782 +#: ../../source/drivers/raster/driver_summary.rst:799 +#: ../../source/drivers/raster/driver_summary.rst:800 +#: ../../source/drivers/raster/driver_summary.rst:811 +#: ../../source/drivers/raster/driver_summary.rst:812 +#: ../../source/drivers/raster/driver_summary.rst:817 +#: ../../source/drivers/raster/driver_summary.rst:818 +#: ../../source/drivers/raster/driver_summary.rst:823 +#: ../../source/drivers/raster/driver_summary.rst:824 +#: ../../source/drivers/raster/driver_summary.rst:829 +#: ../../source/drivers/raster/driver_summary.rst:830 +#: ../../source/drivers/raster/driver_summary.rst:835 +#: ../../source/drivers/raster/driver_summary.rst:836 +#: ../../source/drivers/raster/driver_summary.rst:841 +#: ../../source/drivers/raster/driver_summary.rst:842 +#: ../../source/drivers/raster/driver_summary.rst:853 +#: ../../source/drivers/raster/driver_summary.rst:854 +#: ../../source/drivers/raster/driver_summary.rst:859 +#: ../../source/drivers/raster/driver_summary.rst:860 +#: ../../source/drivers/raster/driver_summary.rst:867 +#: ../../source/drivers/raster/driver_summary.rst:871 +#: ../../source/drivers/raster/driver_summary.rst:877 +#: ../../source/drivers/raster/driver_summary.rst:878 +#: ../../source/drivers/raster/driver_summary.rst:883 +#: ../../source/drivers/raster/driver_summary.rst:884 +#: ../../source/drivers/raster/driver_summary.rst:889 +#: ../../source/drivers/raster/driver_summary.rst:895 +#: ../../source/drivers/raster/driver_summary.rst:896 +#: ../../source/drivers/raster/driver_summary.rst:897 +#: ../../source/drivers/raster/driver_summary.rst:901 +#: ../../source/drivers/raster/driver_summary.rst:902 +#: ../../source/drivers/raster/driver_summary.rst:903 +#: ../../source/drivers/raster/driver_summary.rst:913 +#: ../../source/drivers/raster/driver_summary.rst:914 +#: ../../source/drivers/raster/driver_summary.rst:915 +#: ../../source/drivers/raster/driver_summary.rst:919 +#: ../../source/drivers/raster/driver_summary.rst:920 +#: ../../source/drivers/raster/driver_summary.rst:931 +#: ../../source/drivers/raster/driver_summary.rst:932 +#: ../../source/drivers/raster/driver_summary.rst:937 +#: ../../source/drivers/raster/driver_summary.rst:955 +#: ../../source/drivers/raster/driver_summary.rst:956 +#: ../../source/drivers/raster/driver_summary.rst:961 +#: ../../source/drivers/raster/driver_summary.rst:963 +#: ../../source/drivers/raster/driver_summary.rst:967 +#: ../../source/drivers/raster/driver_summary.rst:973 +#: ../../source/drivers/raster/driver_summary.rst:974 +#: ../../source/drivers/raster/driver_summary.rst:979 +#: ../../source/drivers/raster/driver_summary.rst:981 +#: ../../source/drivers/raster/driver_summary.rst:985 +#: ../../source/drivers/raster/driver_summary.rst:992 +#: ../../source/drivers/raster/driver_summary.rst:997 +#: ../../source/drivers/vector/driver_summary.rst:28 +#: ../../source/drivers/vector/driver_summary.rst:33 +#: ../../source/drivers/vector/driver_summary.rst:38 +#: ../../source/drivers/vector/driver_summary.rst:53 +#: ../../source/drivers/vector/driver_summary.rst:68 +#: ../../source/drivers/vector/driver_summary.rst:69 +#: ../../source/drivers/vector/driver_summary.rst:74 +#: ../../source/drivers/vector/driver_summary.rst:78 +#: ../../source/drivers/vector/driver_summary.rst:83 +#: ../../source/drivers/vector/driver_summary.rst:93 +#: ../../source/drivers/vector/driver_summary.rst:133 +#: ../../source/drivers/vector/driver_summary.rst:158 +#: ../../source/drivers/vector/driver_summary.rst:159 +#: ../../source/drivers/vector/driver_summary.rst:163 +#: ../../source/drivers/vector/driver_summary.rst:164 +#: ../../source/drivers/vector/driver_summary.rst:178 +#: ../../source/drivers/vector/driver_summary.rst:213 +#: ../../source/drivers/vector/driver_summary.rst:214 +#: ../../source/drivers/vector/driver_summary.rst:238 +#: ../../source/drivers/vector/driver_summary.rst:258 +#: ../../source/drivers/vector/driver_summary.rst:268 +#: ../../source/drivers/vector/driver_summary.rst:273 +#: ../../source/drivers/vector/driver_summary.rst:278 +#: ../../source/drivers/vector/driver_summary.rst:288 +#: ../../source/drivers/vector/driver_summary.rst:294 +#: ../../source/drivers/vector/driver_summary.rst:298 +#: ../../source/drivers/vector/driver_summary.rst:308 +#: ../../source/drivers/vector/driver_summary.rst:323 +#: ../../source/drivers/vector/driver_summary.rst:324 +#: ../../source/drivers/vector/driver_summary.rst:338 +#: ../../source/drivers/vector/driver_summary.rst:343 +#: ../../source/drivers/vector/driver_summary.rst:344 +#: ../../source/drivers/vector/driver_summary.rst:358 +#: ../../source/drivers/vector/driver_summary.rst:373 +#: ../../source/drivers/vector/driver_summary.rst:374 +#: ../../source/drivers/vector/driver_summary.rst:383 +#: ../../source/drivers/vector/driver_summary.rst:388 +#: ../../source/drivers/vector/driver_summary.rst:393 +#: ../../source/drivers/vector/driver_summary.rst:399 +#: ../../source/drivers/vector/driver_summary.rst:403 +#: ../../source/drivers/vector/driver_summary.rst:413 +#: ../../source/drivers/vector/driver_summary.rst:418 +#: ../../source/drivers/vector/driver_summary.rst:428 +#: ../../source/drivers/vector/driver_summary.rst:433 +#: ../../source/drivers/vector/driver_summary.rst:434 +#: ../../source/drivers/vector/driver_summary.rst:439 +#: ../../source/drivers/vector/driver_summary.rst:443 +#: ../../source/drivers/vector/eeda.rst:105 +#: ../../source/drivers/vector/eeda.rst:109 +#: ../../source/drivers/vector/eeda.rst:112 +#: ../../source/drivers/vector/eeda.rst:114 +#: ../../source/drivers/vector/eeda.rst:127 +#: ../../source/drivers/vector/eeda.rst:129 +#: ../../source/drivers/vector/eeda.rst:131 +#: ../../source/drivers/vector/eeda.rst:133 +#: ../../source/drivers/vector/eeda.rst:135 +#: ../../source/drivers/vector/eeda.rst:137 +#: ../../source/drivers/vector/eeda.rst:139 +#: ../../source/drivers/vector/eeda.rst:141 +#: ../../source/drivers/vector/eeda.rst:143 +#: ../../source/drivers/vector/eeda.rst:145 +#: ../../source/drivers/vector/gpkg.rst:674 +#: ../../source/drivers/vector/gpkg.rst:677 +msgid "No" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:20 +#: ../../source/drivers/raster/driver_summary.rst:21 +#: ../../source/drivers/raster/driver_summary.rst:27 +#: ../../source/drivers/raster/driver_summary.rst:31 +#: ../../source/drivers/raster/driver_summary.rst:32 +#: ../../source/drivers/raster/driver_summary.rst:33 +#: ../../source/drivers/raster/driver_summary.rst:39 +#: ../../source/drivers/raster/driver_summary.rst:49 +#: ../../source/drivers/raster/driver_summary.rst:50 +#: ../../source/drivers/raster/driver_summary.rst:51 +#: ../../source/drivers/raster/driver_summary.rst:56 +#: ../../source/drivers/raster/driver_summary.rst:62 +#: ../../source/drivers/raster/driver_summary.rst:63 +#: ../../source/drivers/raster/driver_summary.rst:67 +#: ../../source/drivers/raster/driver_summary.rst:68 +#: ../../source/drivers/raster/driver_summary.rst:69 +#: ../../source/drivers/raster/driver_summary.rst:75 +#: ../../source/drivers/raster/driver_summary.rst:79 +#: ../../source/drivers/raster/driver_summary.rst:80 +#: ../../source/drivers/raster/driver_summary.rst:81 +#: ../../source/drivers/raster/driver_summary.rst:85 +#: ../../source/drivers/raster/driver_summary.rst:86 +#: ../../source/drivers/raster/driver_summary.rst:87 +#: ../../source/drivers/raster/driver_summary.rst:93 +#: ../../source/drivers/raster/driver_summary.rst:98 +#: ../../source/drivers/raster/driver_summary.rst:116 +#: ../../source/drivers/raster/driver_summary.rst:117 +#: ../../source/drivers/raster/driver_summary.rst:129 +#: ../../source/drivers/raster/driver_summary.rst:133 +#: ../../source/drivers/raster/driver_summary.rst:134 +#: ../../source/drivers/raster/driver_summary.rst:135 +#: ../../source/drivers/raster/driver_summary.rst:141 +#: ../../source/drivers/raster/driver_summary.rst:147 +#: ../../source/drivers/raster/driver_summary.rst:152 +#: ../../source/drivers/raster/driver_summary.rst:165 +#: ../../source/drivers/raster/driver_summary.rst:171 +#: ../../source/drivers/raster/driver_summary.rst:177 +#: ../../source/drivers/raster/driver_summary.rst:183 +#: ../../source/drivers/raster/driver_summary.rst:188 +#: ../../source/drivers/raster/driver_summary.rst:189 +#: ../../source/drivers/raster/driver_summary.rst:195 +#: ../../source/drivers/raster/driver_summary.rst:199 +#: ../../source/drivers/raster/driver_summary.rst:200 +#: ../../source/drivers/raster/driver_summary.rst:201 +#: ../../source/drivers/raster/driver_summary.rst:207 +#: ../../source/drivers/raster/driver_summary.rst:211 +#: ../../source/drivers/raster/driver_summary.rst:212 +#: ../../source/drivers/raster/driver_summary.rst:213 +#: ../../source/drivers/raster/driver_summary.rst:219 +#: ../../source/drivers/raster/driver_summary.rst:223 +#: ../../source/drivers/raster/driver_summary.rst:224 +#: ../../source/drivers/raster/driver_summary.rst:225 +#: ../../source/drivers/raster/driver_summary.rst:229 +#: ../../source/drivers/raster/driver_summary.rst:230 +#: ../../source/drivers/raster/driver_summary.rst:231 +#: ../../source/drivers/raster/driver_summary.rst:235 +#: ../../source/drivers/raster/driver_summary.rst:236 +#: ../../source/drivers/raster/driver_summary.rst:237 +#: ../../source/drivers/raster/driver_summary.rst:249 +#: ../../source/drivers/raster/driver_summary.rst:253 +#: ../../source/drivers/raster/driver_summary.rst:254 +#: ../../source/drivers/raster/driver_summary.rst:255 +#: ../../source/drivers/raster/driver_summary.rst:261 +#: ../../source/drivers/raster/driver_summary.rst:266 +#: ../../source/drivers/raster/driver_summary.rst:267 +#: ../../source/drivers/raster/driver_summary.rst:271 +#: ../../source/drivers/raster/driver_summary.rst:272 +#: ../../source/drivers/raster/driver_summary.rst:273 +#: ../../source/drivers/raster/driver_summary.rst:283 +#: ../../source/drivers/raster/driver_summary.rst:284 +#: ../../source/drivers/raster/driver_summary.rst:285 +#: ../../source/drivers/raster/driver_summary.rst:296 +#: ../../source/drivers/raster/driver_summary.rst:301 +#: ../../source/drivers/raster/driver_summary.rst:302 +#: ../../source/drivers/raster/driver_summary.rst:303 +#: ../../source/drivers/raster/driver_summary.rst:315 +#: ../../source/drivers/raster/driver_summary.rst:320 +#: ../../source/drivers/raster/driver_summary.rst:321 +#: ../../source/drivers/raster/driver_summary.rst:325 +#: ../../source/drivers/raster/driver_summary.rst:326 +#: ../../source/drivers/raster/driver_summary.rst:327 +#: ../../source/drivers/raster/driver_summary.rst:332 +#: ../../source/drivers/raster/driver_summary.rst:333 +#: ../../source/drivers/raster/driver_summary.rst:337 +#: ../../source/drivers/raster/driver_summary.rst:338 +#: ../../source/drivers/raster/driver_summary.rst:339 +#: ../../source/drivers/raster/driver_summary.rst:350 +#: ../../source/drivers/raster/driver_summary.rst:351 +#: ../../source/drivers/raster/driver_summary.rst:361 +#: ../../source/drivers/raster/driver_summary.rst:362 +#: ../../source/drivers/raster/driver_summary.rst:363 +#: ../../source/drivers/raster/driver_summary.rst:369 +#: ../../source/drivers/raster/driver_summary.rst:373 +#: ../../source/drivers/raster/driver_summary.rst:374 +#: ../../source/drivers/raster/driver_summary.rst:375 +#: ../../source/drivers/raster/driver_summary.rst:381 +#: ../../source/drivers/raster/driver_summary.rst:392 +#: ../../source/drivers/raster/driver_summary.rst:393 +#: ../../source/drivers/raster/driver_summary.rst:397 +#: ../../source/drivers/raster/driver_summary.rst:398 +#: ../../source/drivers/raster/driver_summary.rst:399 +#: ../../source/drivers/raster/driver_summary.rst:403 +#: ../../source/drivers/raster/driver_summary.rst:404 +#: ../../source/drivers/raster/driver_summary.rst:405 +#: ../../source/drivers/raster/driver_summary.rst:409 +#: ../../source/drivers/raster/driver_summary.rst:410 +#: ../../source/drivers/raster/driver_summary.rst:411 +#: ../../source/drivers/raster/driver_summary.rst:417 +#: ../../source/drivers/raster/driver_summary.rst:421 +#: ../../source/drivers/raster/driver_summary.rst:422 +#: ../../source/drivers/raster/driver_summary.rst:423 +#: ../../source/drivers/raster/driver_summary.rst:429 +#: ../../source/drivers/raster/driver_summary.rst:433 +#: ../../source/drivers/raster/driver_summary.rst:434 +#: ../../source/drivers/raster/driver_summary.rst:435 +#: ../../source/drivers/raster/driver_summary.rst:439 +#: ../../source/drivers/raster/driver_summary.rst:440 +#: ../../source/drivers/raster/driver_summary.rst:441 +#: ../../source/drivers/raster/driver_summary.rst:447 +#: ../../source/drivers/raster/driver_summary.rst:451 +#: ../../source/drivers/raster/driver_summary.rst:452 +#: ../../source/drivers/raster/driver_summary.rst:453 +#: ../../source/drivers/raster/driver_summary.rst:458 +#: ../../source/drivers/raster/driver_summary.rst:459 +#: ../../source/drivers/raster/driver_summary.rst:464 +#: ../../source/drivers/raster/driver_summary.rst:465 +#: ../../source/drivers/raster/driver_summary.rst:470 +#: ../../source/drivers/raster/driver_summary.rst:471 +#: ../../source/drivers/raster/driver_summary.rst:476 +#: ../../source/drivers/raster/driver_summary.rst:477 +#: ../../source/drivers/raster/driver_summary.rst:482 +#: ../../source/drivers/raster/driver_summary.rst:483 +#: ../../source/drivers/raster/driver_summary.rst:488 +#: ../../source/drivers/raster/driver_summary.rst:489 +#: ../../source/drivers/raster/driver_summary.rst:495 +#: ../../source/drivers/raster/driver_summary.rst:499 +#: ../../source/drivers/raster/driver_summary.rst:500 +#: ../../source/drivers/raster/driver_summary.rst:501 +#: ../../source/drivers/raster/driver_summary.rst:506 +#: ../../source/drivers/raster/driver_summary.rst:507 +#: ../../source/drivers/raster/driver_summary.rst:511 +#: ../../source/drivers/raster/driver_summary.rst:512 +#: ../../source/drivers/raster/driver_summary.rst:518 +#: ../../source/drivers/raster/driver_summary.rst:525 +#: ../../source/drivers/raster/driver_summary.rst:529 +#: ../../source/drivers/raster/driver_summary.rst:531 +#: ../../source/drivers/raster/driver_summary.rst:536 +#: ../../source/drivers/raster/driver_summary.rst:537 +#: ../../source/drivers/raster/driver_summary.rst:541 +#: ../../source/drivers/raster/driver_summary.rst:542 +#: ../../source/drivers/raster/driver_summary.rst:543 +#: ../../source/drivers/raster/driver_summary.rst:549 +#: ../../source/drivers/raster/driver_summary.rst:555 +#: ../../source/drivers/raster/driver_summary.rst:559 +#: ../../source/drivers/raster/driver_summary.rst:560 +#: ../../source/drivers/raster/driver_summary.rst:561 +#: ../../source/drivers/raster/driver_summary.rst:565 +#: ../../source/drivers/raster/driver_summary.rst:566 +#: ../../source/drivers/raster/driver_summary.rst:567 +#: ../../source/drivers/raster/driver_summary.rst:571 +#: ../../source/drivers/raster/driver_summary.rst:572 +#: ../../source/drivers/raster/driver_summary.rst:573 +#: ../../source/drivers/raster/driver_summary.rst:577 +#: ../../source/drivers/raster/driver_summary.rst:578 +#: ../../source/drivers/raster/driver_summary.rst:579 +#: ../../source/drivers/raster/driver_summary.rst:583 +#: ../../source/drivers/raster/driver_summary.rst:584 +#: ../../source/drivers/raster/driver_summary.rst:585 +#: ../../source/drivers/raster/driver_summary.rst:591 +#: ../../source/drivers/raster/driver_summary.rst:597 +#: ../../source/drivers/raster/driver_summary.rst:603 +#: ../../source/drivers/raster/driver_summary.rst:609 +#: ../../source/drivers/raster/driver_summary.rst:613 +#: ../../source/drivers/raster/driver_summary.rst:614 +#: ../../source/drivers/raster/driver_summary.rst:615 +#: ../../source/drivers/raster/driver_summary.rst:621 +#: ../../source/drivers/raster/driver_summary.rst:627 +#: ../../source/drivers/raster/driver_summary.rst:631 +#: ../../source/drivers/raster/driver_summary.rst:632 +#: ../../source/drivers/raster/driver_summary.rst:633 +#: ../../source/drivers/raster/driver_summary.rst:639 +#: ../../source/drivers/raster/driver_summary.rst:645 +#: ../../source/drivers/raster/driver_summary.rst:649 +#: ../../source/drivers/raster/driver_summary.rst:650 +#: ../../source/drivers/raster/driver_summary.rst:651 +#: ../../source/drivers/raster/driver_summary.rst:655 +#: ../../source/drivers/raster/driver_summary.rst:656 +#: ../../source/drivers/raster/driver_summary.rst:657 +#: ../../source/drivers/raster/driver_summary.rst:661 +#: ../../source/drivers/raster/driver_summary.rst:662 +#: ../../source/drivers/raster/driver_summary.rst:663 +#: ../../source/drivers/raster/driver_summary.rst:669 +#: ../../source/drivers/raster/driver_summary.rst:675 +#: ../../source/drivers/raster/driver_summary.rst:681 +#: ../../source/drivers/raster/driver_summary.rst:687 +#: ../../source/drivers/raster/driver_summary.rst:691 +#: ../../source/drivers/raster/driver_summary.rst:692 +#: ../../source/drivers/raster/driver_summary.rst:697 +#: ../../source/drivers/raster/driver_summary.rst:698 +#: ../../source/drivers/raster/driver_summary.rst:699 +#: ../../source/drivers/raster/driver_summary.rst:703 +#: ../../source/drivers/raster/driver_summary.rst:704 +#: ../../source/drivers/raster/driver_summary.rst:705 +#: ../../source/drivers/raster/driver_summary.rst:710 +#: ../../source/drivers/raster/driver_summary.rst:711 +#: ../../source/drivers/raster/driver_summary.rst:717 +#: ../../source/drivers/raster/driver_summary.rst:721 +#: ../../source/drivers/raster/driver_summary.rst:722 +#: ../../source/drivers/raster/driver_summary.rst:723 +#: ../../source/drivers/raster/driver_summary.rst:729 +#: ../../source/drivers/raster/driver_summary.rst:734 +#: ../../source/drivers/raster/driver_summary.rst:735 +#: ../../source/drivers/raster/driver_summary.rst:739 +#: ../../source/drivers/raster/driver_summary.rst:740 +#: ../../source/drivers/raster/driver_summary.rst:746 +#: ../../source/drivers/raster/driver_summary.rst:747 +#: ../../source/drivers/raster/driver_summary.rst:758 +#: ../../source/drivers/raster/driver_summary.rst:764 +#: ../../source/drivers/raster/driver_summary.rst:765 +#: ../../source/drivers/raster/driver_summary.rst:770 +#: ../../source/drivers/raster/driver_summary.rst:771 +#: ../../source/drivers/raster/driver_summary.rst:777 +#: ../../source/drivers/raster/driver_summary.rst:783 +#: ../../source/drivers/raster/driver_summary.rst:787 +#: ../../source/drivers/raster/driver_summary.rst:788 +#: ../../source/drivers/raster/driver_summary.rst:789 +#: ../../source/drivers/raster/driver_summary.rst:793 +#: ../../source/drivers/raster/driver_summary.rst:794 +#: ../../source/drivers/raster/driver_summary.rst:795 +#: ../../source/drivers/raster/driver_summary.rst:801 +#: ../../source/drivers/raster/driver_summary.rst:805 +#: ../../source/drivers/raster/driver_summary.rst:806 +#: ../../source/drivers/raster/driver_summary.rst:807 +#: ../../source/drivers/raster/driver_summary.rst:813 +#: ../../source/drivers/raster/driver_summary.rst:819 +#: ../../source/drivers/raster/driver_summary.rst:825 +#: ../../source/drivers/raster/driver_summary.rst:831 +#: ../../source/drivers/raster/driver_summary.rst:837 +#: ../../source/drivers/raster/driver_summary.rst:843 +#: ../../source/drivers/raster/driver_summary.rst:847 +#: ../../source/drivers/raster/driver_summary.rst:848 +#: ../../source/drivers/raster/driver_summary.rst:849 +#: ../../source/drivers/raster/driver_summary.rst:855 +#: ../../source/drivers/raster/driver_summary.rst:861 +#: ../../source/drivers/raster/driver_summary.rst:865 +#: ../../source/drivers/raster/driver_summary.rst:866 +#: ../../source/drivers/raster/driver_summary.rst:872 +#: ../../source/drivers/raster/driver_summary.rst:873 +#: ../../source/drivers/raster/driver_summary.rst:879 +#: ../../source/drivers/raster/driver_summary.rst:885 +#: ../../source/drivers/raster/driver_summary.rst:890 +#: ../../source/drivers/raster/driver_summary.rst:891 +#: ../../source/drivers/raster/driver_summary.rst:907 +#: ../../source/drivers/raster/driver_summary.rst:908 +#: ../../source/drivers/raster/driver_summary.rst:909 +#: ../../source/drivers/raster/driver_summary.rst:921 +#: ../../source/drivers/raster/driver_summary.rst:925 +#: ../../source/drivers/raster/driver_summary.rst:926 +#: ../../source/drivers/raster/driver_summary.rst:927 +#: ../../source/drivers/raster/driver_summary.rst:933 +#: ../../source/drivers/raster/driver_summary.rst:938 +#: ../../source/drivers/raster/driver_summary.rst:939 +#: ../../source/drivers/raster/driver_summary.rst:943 +#: ../../source/drivers/raster/driver_summary.rst:944 +#: ../../source/drivers/raster/driver_summary.rst:945 +#: ../../source/drivers/raster/driver_summary.rst:949 +#: ../../source/drivers/raster/driver_summary.rst:950 +#: ../../source/drivers/raster/driver_summary.rst:951 +#: ../../source/drivers/raster/driver_summary.rst:957 +#: ../../source/drivers/raster/driver_summary.rst:962 +#: ../../source/drivers/raster/driver_summary.rst:968 +#: ../../source/drivers/raster/driver_summary.rst:969 +#: ../../source/drivers/raster/driver_summary.rst:975 +#: ../../source/drivers/raster/driver_summary.rst:980 +#: ../../source/drivers/raster/driver_summary.rst:986 +#: ../../source/drivers/raster/driver_summary.rst:987 +#: ../../source/drivers/raster/driver_summary.rst:991 +#: ../../source/drivers/raster/driver_summary.rst:993 +#: ../../source/drivers/raster/driver_summary.rst:998 +#: ../../source/drivers/raster/driver_summary.rst:999 +#: ../../source/drivers/vector/driver_summary.rst:18 +#: ../../source/drivers/vector/driver_summary.rst:19 +#: ../../source/drivers/vector/driver_summary.rst:23 +#: ../../source/drivers/vector/driver_summary.rst:24 +#: ../../source/drivers/vector/driver_summary.rst:29 +#: ../../source/drivers/vector/driver_summary.rst:34 +#: ../../source/drivers/vector/driver_summary.rst:39 +#: ../../source/drivers/vector/driver_summary.rst:43 +#: ../../source/drivers/vector/driver_summary.rst:44 +#: ../../source/drivers/vector/driver_summary.rst:48 +#: ../../source/drivers/vector/driver_summary.rst:49 +#: ../../source/drivers/vector/driver_summary.rst:54 +#: ../../source/drivers/vector/driver_summary.rst:58 +#: ../../source/drivers/vector/driver_summary.rst:59 +#: ../../source/drivers/vector/driver_summary.rst:63 +#: ../../source/drivers/vector/driver_summary.rst:64 +#: ../../source/drivers/vector/driver_summary.rst:73 +#: ../../source/drivers/vector/driver_summary.rst:79 +#: ../../source/drivers/vector/driver_summary.rst:84 +#: ../../source/drivers/vector/driver_summary.rst:88 +#: ../../source/drivers/vector/driver_summary.rst:89 +#: ../../source/drivers/vector/driver_summary.rst:94 +#: ../../source/drivers/vector/driver_summary.rst:98 +#: ../../source/drivers/vector/driver_summary.rst:99 +#: ../../source/drivers/vector/driver_summary.rst:103 +#: ../../source/drivers/vector/driver_summary.rst:104 +#: ../../source/drivers/vector/driver_summary.rst:108 +#: ../../source/drivers/vector/driver_summary.rst:109 +#: ../../source/drivers/vector/driver_summary.rst:113 +#: ../../source/drivers/vector/driver_summary.rst:114 +#: ../../source/drivers/vector/driver_summary.rst:118 +#: ../../source/drivers/vector/driver_summary.rst:119 +#: ../../source/drivers/vector/driver_summary.rst:123 +#: ../../source/drivers/vector/driver_summary.rst:124 +#: ../../source/drivers/vector/driver_summary.rst:128 +#: ../../source/drivers/vector/driver_summary.rst:129 +#: ../../source/drivers/vector/driver_summary.rst:134 +#: ../../source/drivers/vector/driver_summary.rst:138 +#: ../../source/drivers/vector/driver_summary.rst:139 +#: ../../source/drivers/vector/driver_summary.rst:143 +#: ../../source/drivers/vector/driver_summary.rst:144 +#: ../../source/drivers/vector/driver_summary.rst:148 +#: ../../source/drivers/vector/driver_summary.rst:149 +#: ../../source/drivers/vector/driver_summary.rst:153 +#: ../../source/drivers/vector/driver_summary.rst:154 +#: ../../source/drivers/vector/driver_summary.rst:168 +#: ../../source/drivers/vector/driver_summary.rst:169 +#: ../../source/drivers/vector/driver_summary.rst:173 +#: ../../source/drivers/vector/driver_summary.rst:174 +#: ../../source/drivers/vector/driver_summary.rst:179 +#: ../../source/drivers/vector/driver_summary.rst:183 +#: ../../source/drivers/vector/driver_summary.rst:184 +#: ../../source/drivers/vector/driver_summary.rst:188 +#: ../../source/drivers/vector/driver_summary.rst:189 +#: ../../source/drivers/vector/driver_summary.rst:193 +#: ../../source/drivers/vector/driver_summary.rst:194 +#: ../../source/drivers/vector/driver_summary.rst:198 +#: ../../source/drivers/vector/driver_summary.rst:199 +#: ../../source/drivers/vector/driver_summary.rst:203 +#: ../../source/drivers/vector/driver_summary.rst:204 +#: ../../source/drivers/vector/driver_summary.rst:208 +#: ../../source/drivers/vector/driver_summary.rst:209 +#: ../../source/drivers/vector/driver_summary.rst:218 +#: ../../source/drivers/vector/driver_summary.rst:219 +#: ../../source/drivers/vector/driver_summary.rst:223 +#: ../../source/drivers/vector/driver_summary.rst:224 +#: ../../source/drivers/vector/driver_summary.rst:228 +#: ../../source/drivers/vector/driver_summary.rst:229 +#: ../../source/drivers/vector/driver_summary.rst:233 +#: ../../source/drivers/vector/driver_summary.rst:234 +#: ../../source/drivers/vector/driver_summary.rst:239 +#: ../../source/drivers/vector/driver_summary.rst:243 +#: ../../source/drivers/vector/driver_summary.rst:244 +#: ../../source/drivers/vector/driver_summary.rst:248 +#: ../../source/drivers/vector/driver_summary.rst:249 +#: ../../source/drivers/vector/driver_summary.rst:253 +#: ../../source/drivers/vector/driver_summary.rst:254 +#: ../../source/drivers/vector/driver_summary.rst:259 +#: ../../source/drivers/vector/driver_summary.rst:263 +#: ../../source/drivers/vector/driver_summary.rst:264 +#: ../../source/drivers/vector/driver_summary.rst:269 +#: ../../source/drivers/vector/driver_summary.rst:274 +#: ../../source/drivers/vector/driver_summary.rst:279 +#: ../../source/drivers/vector/driver_summary.rst:283 +#: ../../source/drivers/vector/driver_summary.rst:284 +#: ../../source/drivers/vector/driver_summary.rst:289 +#: ../../source/drivers/vector/driver_summary.rst:293 +#: ../../source/drivers/vector/driver_summary.rst:299 +#: ../../source/drivers/vector/driver_summary.rst:303 +#: ../../source/drivers/vector/driver_summary.rst:304 +#: ../../source/drivers/vector/driver_summary.rst:309 +#: ../../source/drivers/vector/driver_summary.rst:313 +#: ../../source/drivers/vector/driver_summary.rst:314 +#: ../../source/drivers/vector/driver_summary.rst:318 +#: ../../source/drivers/vector/driver_summary.rst:319 +#: ../../source/drivers/vector/driver_summary.rst:328 +#: ../../source/drivers/vector/driver_summary.rst:329 +#: ../../source/drivers/vector/driver_summary.rst:333 +#: ../../source/drivers/vector/driver_summary.rst:334 +#: ../../source/drivers/vector/driver_summary.rst:339 +#: ../../source/drivers/vector/driver_summary.rst:348 +#: ../../source/drivers/vector/driver_summary.rst:349 +#: ../../source/drivers/vector/driver_summary.rst:353 +#: ../../source/drivers/vector/driver_summary.rst:354 +#: ../../source/drivers/vector/driver_summary.rst:359 +#: ../../source/drivers/vector/driver_summary.rst:363 +#: ../../source/drivers/vector/driver_summary.rst:364 +#: ../../source/drivers/vector/driver_summary.rst:368 +#: ../../source/drivers/vector/driver_summary.rst:369 +#: ../../source/drivers/vector/driver_summary.rst:378 +#: ../../source/drivers/vector/driver_summary.rst:379 +#: ../../source/drivers/vector/driver_summary.rst:384 +#: ../../source/drivers/vector/driver_summary.rst:389 +#: ../../source/drivers/vector/driver_summary.rst:394 +#: ../../source/drivers/vector/driver_summary.rst:398 +#: ../../source/drivers/vector/driver_summary.rst:404 +#: ../../source/drivers/vector/driver_summary.rst:408 +#: ../../source/drivers/vector/driver_summary.rst:409 +#: ../../source/drivers/vector/driver_summary.rst:414 +#: ../../source/drivers/vector/driver_summary.rst:419 +#: ../../source/drivers/vector/driver_summary.rst:423 +#: ../../source/drivers/vector/driver_summary.rst:424 +#: ../../source/drivers/vector/driver_summary.rst:429 +#: ../../source/drivers/vector/driver_summary.rst:438 +#: ../../source/drivers/vector/driver_summary.rst:444 +msgid "**Yes**" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:22 +#: ../../source/drivers/raster/driver_summary.rst:28 +#: ../../source/drivers/raster/driver_summary.rst:34 +#: ../../source/drivers/raster/driver_summary.rst:40 +#: ../../source/drivers/raster/driver_summary.rst:46 +#: ../../source/drivers/raster/driver_summary.rst:64 +#: ../../source/drivers/raster/driver_summary.rst:70 +#: ../../source/drivers/raster/driver_summary.rst:76 +#: ../../source/drivers/raster/driver_summary.rst:82 +#: ../../source/drivers/raster/driver_summary.rst:88 +#: ../../source/drivers/raster/driver_summary.rst:100 +#: ../../source/drivers/raster/driver_summary.rst:106 +#: ../../source/drivers/raster/driver_summary.rst:112 +#: ../../source/drivers/raster/driver_summary.rst:118 +#: ../../source/drivers/raster/driver_summary.rst:124 +#: ../../source/drivers/raster/driver_summary.rst:130 +#: ../../source/drivers/raster/driver_summary.rst:136 +#: ../../source/drivers/raster/driver_summary.rst:142 +#: ../../source/drivers/raster/driver_summary.rst:160 +#: ../../source/drivers/raster/driver_summary.rst:166 +#: ../../source/drivers/raster/driver_summary.rst:172 +#: ../../source/drivers/raster/driver_summary.rst:178 +#: ../../source/drivers/raster/driver_summary.rst:184 +#: ../../source/drivers/raster/driver_summary.rst:190 +#: ../../source/drivers/raster/driver_summary.rst:196 +#: ../../source/drivers/raster/driver_summary.rst:214 +#: ../../source/drivers/raster/driver_summary.rst:220 +#: ../../source/drivers/raster/driver_summary.rst:226 +#: ../../source/drivers/raster/driver_summary.rst:232 +#: ../../source/drivers/raster/driver_summary.rst:238 +#: ../../source/drivers/raster/driver_summary.rst:244 +#: ../../source/drivers/raster/driver_summary.rst:250 +#: ../../source/drivers/raster/driver_summary.rst:262 +#: ../../source/drivers/raster/driver_summary.rst:268 +#: ../../source/drivers/raster/driver_summary.rst:280 +#: ../../source/drivers/raster/driver_summary.rst:292 +#: ../../source/drivers/raster/driver_summary.rst:316 +#: ../../source/drivers/raster/driver_summary.rst:322 +#: ../../source/drivers/raster/driver_summary.rst:328 +#: ../../source/drivers/raster/driver_summary.rst:334 +#: ../../source/drivers/raster/driver_summary.rst:340 +#: ../../source/drivers/raster/driver_summary.rst:346 +#: ../../source/drivers/raster/driver_summary.rst:358 +#: ../../source/drivers/raster/driver_summary.rst:364 +#: ../../source/drivers/raster/driver_summary.rst:370 +#: ../../source/drivers/raster/driver_summary.rst:394 +#: ../../source/drivers/raster/driver_summary.rst:400 +#: ../../source/drivers/raster/driver_summary.rst:406 +#: ../../source/drivers/raster/driver_summary.rst:412 +#: ../../source/drivers/raster/driver_summary.rst:418 +#: ../../source/drivers/raster/driver_summary.rst:424 +#: ../../source/drivers/raster/driver_summary.rst:430 +#: ../../source/drivers/raster/driver_summary.rst:436 +#: ../../source/drivers/raster/driver_summary.rst:442 +#: ../../source/drivers/raster/driver_summary.rst:448 +#: ../../source/drivers/raster/driver_summary.rst:508 +#: ../../source/drivers/raster/driver_summary.rst:514 +#: ../../source/drivers/raster/driver_summary.rst:526 +#: ../../source/drivers/raster/driver_summary.rst:532 +#: ../../source/drivers/raster/driver_summary.rst:538 +#: ../../source/drivers/raster/driver_summary.rst:544 +#: ../../source/drivers/raster/driver_summary.rst:550 +#: ../../source/drivers/raster/driver_summary.rst:556 +#: ../../source/drivers/raster/driver_summary.rst:562 +#: ../../source/drivers/raster/driver_summary.rst:574 +#: ../../source/drivers/raster/driver_summary.rst:580 +#: ../../source/drivers/raster/driver_summary.rst:586 +#: ../../source/drivers/raster/driver_summary.rst:604 +#: ../../source/drivers/raster/driver_summary.rst:610 +#: ../../source/drivers/raster/driver_summary.rst:622 +#: ../../source/drivers/raster/driver_summary.rst:634 +#: ../../source/drivers/raster/driver_summary.rst:640 +#: ../../source/drivers/raster/driver_summary.rst:646 +#: ../../source/drivers/raster/driver_summary.rst:652 +#: ../../source/drivers/raster/driver_summary.rst:658 +#: ../../source/drivers/raster/driver_summary.rst:664 +#: ../../source/drivers/raster/driver_summary.rst:676 +#: ../../source/drivers/raster/driver_summary.rst:682 +#: ../../source/drivers/raster/driver_summary.rst:688 +#: ../../source/drivers/raster/driver_summary.rst:694 +#: ../../source/drivers/raster/driver_summary.rst:700 +#: ../../source/drivers/raster/driver_summary.rst:718 +#: ../../source/drivers/raster/driver_summary.rst:724 +#: ../../source/drivers/raster/driver_summary.rst:736 +#: ../../source/drivers/raster/driver_summary.rst:742 +#: ../../source/drivers/raster/driver_summary.rst:754 +#: ../../source/drivers/raster/driver_summary.rst:760 +#: ../../source/drivers/raster/driver_summary.rst:790 +#: ../../source/drivers/raster/driver_summary.rst:796 +#: ../../source/drivers/raster/driver_summary.rst:802 +#: ../../source/drivers/raster/driver_summary.rst:808 +#: ../../source/drivers/raster/driver_summary.rst:814 +#: ../../source/drivers/raster/driver_summary.rst:838 +#: ../../source/drivers/raster/driver_summary.rst:844 +#: ../../source/drivers/raster/driver_summary.rst:850 +#: ../../source/drivers/raster/driver_summary.rst:856 +#: ../../source/drivers/raster/driver_summary.rst:862 +#: ../../source/drivers/raster/driver_summary.rst:868 +#: ../../source/drivers/raster/driver_summary.rst:874 +#: ../../source/drivers/raster/driver_summary.rst:880 +#: ../../source/drivers/raster/driver_summary.rst:886 +#: ../../source/drivers/raster/driver_summary.rst:892 +#: ../../source/drivers/raster/driver_summary.rst:898 +#: ../../source/drivers/raster/driver_summary.rst:904 +#: ../../source/drivers/raster/driver_summary.rst:910 +#: ../../source/drivers/raster/driver_summary.rst:916 +#: ../../source/drivers/raster/driver_summary.rst:922 +#: ../../source/drivers/raster/driver_summary.rst:934 +#: ../../source/drivers/raster/driver_summary.rst:940 +#: ../../source/drivers/raster/driver_summary.rst:946 +#: ../../source/drivers/raster/driver_summary.rst:952 +#: ../../source/drivers/raster/driver_summary.rst:982 +#: ../../source/drivers/raster/driver_summary.rst:988 +#: ../../source/drivers/raster/driver_summary.rst:1000 +#: ../../source/drivers/vector/driver_summary.rst:30 +#: ../../source/drivers/vector/driver_summary.rst:35 +#: ../../source/drivers/vector/driver_summary.rst:50 +#: ../../source/drivers/vector/driver_summary.rst:60 +#: ../../source/drivers/vector/driver_summary.rst:75 +#: ../../source/drivers/vector/driver_summary.rst:80 +#: ../../source/drivers/vector/driver_summary.rst:95 +#: ../../source/drivers/vector/driver_summary.rst:105 +#: ../../source/drivers/vector/driver_summary.rst:110 +#: ../../source/drivers/vector/driver_summary.rst:115 +#: ../../source/drivers/vector/driver_summary.rst:120 +#: ../../source/drivers/vector/driver_summary.rst:140 +#: ../../source/drivers/vector/driver_summary.rst:165 +#: ../../source/drivers/vector/driver_summary.rst:180 +#: ../../source/drivers/vector/driver_summary.rst:200 +#: ../../source/drivers/vector/driver_summary.rst:220 +#: ../../source/drivers/vector/driver_summary.rst:225 +#: ../../source/drivers/vector/driver_summary.rst:230 +#: ../../source/drivers/vector/driver_summary.rst:235 +#: ../../source/drivers/vector/driver_summary.rst:275 +#: ../../source/drivers/vector/driver_summary.rst:305 +#: ../../source/drivers/vector/driver_summary.rst:325 +#: ../../source/drivers/vector/driver_summary.rst:335 +#: ../../source/drivers/vector/driver_summary.rst:350 +#: ../../source/drivers/vector/driver_summary.rst:355 +#: ../../source/drivers/vector/driver_summary.rst:360 +#: ../../source/drivers/vector/driver_summary.rst:365 +#: ../../source/drivers/vector/driver_summary.rst:370 +#: ../../source/drivers/vector/driver_summary.rst:390 +#: ../../source/drivers/vector/driver_summary.rst:395 +#: ../../source/drivers/vector/driver_summary.rst:405 +#: ../../source/drivers/vector/driver_summary.rst:410 +#: ../../source/drivers/vector/driver_summary.rst:420 +#: ../../source/drivers/vector/driver_summary.rst:425 +msgid "Built-in by default" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:23 +msgid ":ref:`ACE2 <raster.ace2>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:29 +msgid ":ref:`ADRG <raster.adrg>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:30 +msgid "ADRG/ARC Digitized Raster Graphics (.gen/.thf)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:35 +msgid ":ref:`AIG <raster.aig>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:36 +msgid "Arc/Info Binary Grid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:41 +msgid ":ref:`AIRSAR <raster.airsar>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:42 +msgid "AIRSAR Polarimetric Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:47 +msgid ":ref:`BAG <raster.bag>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:48 +msgid "Bathymetry Attributed Grid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:53 +msgid ":ref:`BASISU <raster.basisu>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:59 +msgid ":ref:`BLX <raster.blx>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:60 +msgid "Magellan BLX Topo File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:65 +msgid ":ref:`BMP <raster.bmp>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:66 +msgid "Microsoft Windows Device Independent Bitmap" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:71 +msgid ":ref:`BSB <raster.bsb>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:72 +msgid "Maptech/NOAA BSB Nautical Chart Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:77 +msgid ":ref:`BT <raster.bt>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:78 +msgid "VTP .bt Binary Terrain Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:83 +msgid ":ref:`BYN <raster.byn>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:84 +msgid "Natural Resources Canada's Geoid file format (.byn)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:89 +msgid ":ref:`CAD <raster.cad>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:90 +msgid "AutoCAD DWG raster layer" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:95 +msgid ":ref:`CALS <raster.cals>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:96 +msgid "CALS Type 1" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:101 +msgid ":ref:`CEOS <raster.ceos>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:102 +msgid "CEOS Image" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:107 +msgid ":ref:`COASP <raster.coasp>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:108 +msgid "DRDC COASP SAR Processor Raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:113 +msgid ":ref:`COG <raster.cog>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:114 +msgid "Cloud Optimized GeoTIFF generator" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:119 +msgid ":ref:`COSAR <raster.cosar>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:120 +msgid "TerraSAR-X Complex SAR Data Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:125 +msgid ":ref:`CPG <raster.cpg>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:126 +msgid "Convair PolGASP data" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:131 +msgid ":ref:`CTable2 <raster.ctable2>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:132 +msgid "CTable2 Datum Grid Shift" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:137 +msgid ":ref:`CTG <raster.ctg>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:138 +msgid "USGS LULC Composite Theme Grid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:143 +msgid ":ref:`DAAS <raster.daas>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:149 +msgid ":ref:`DDS <raster.dds>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:150 +msgid "DirectDraw Surface" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:155 +msgid ":ref:`DERIVED <raster.derived>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:156 +msgid "Derived subdatasets driver" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:161 +msgid ":ref:`DIMAP <raster.dimap>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:162 +msgid "Spot DIMAP" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:167 +msgid ":ref:`DIPEx <raster.dipex>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:168 +msgid "ELAS DIPEx" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:173 +msgid ":ref:`DOQ1 <raster.doq1>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:174 +msgid "First Generation USGS DOQ" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:179 +msgid ":ref:`DOQ2 <raster.doq2>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:180 +msgid "New Labelled USGS DOQ" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:185 +msgid ":ref:`DTED <raster.dted>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:186 +msgid "Military Elevation Data" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:191 +msgid ":ref:`ECRGTOC <raster.ecrgtoc>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:192 +msgid "ECRG Table Of Contents (TOC.xml)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:197 +msgid ":ref:`ECW <raster.ecw>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:198 +msgid "Enhanced Compressed Wavelets (.ecw)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:202 +#: ../../source/drivers/raster/driver_summary.rst:454 +#: ../../source/drivers/raster/ecw.rst:9 +#: ../../source/drivers/raster/jp2ecw.rst:9 +msgid "ECW SDK" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:203 +msgid ":ref:`EEDAI <raster.eedai>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:204 +msgid "Google Earth Engine Data API Image" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:209 +msgid ":ref:`EHdr <raster.ehdr>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:210 +msgid "ESRI .hdr Labelled" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:215 +msgid ":ref:`EIR <raster.eir>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:216 +msgid "Erdas Imagine Raw" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:221 +msgid ":ref:`ELAS <raster.elas>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:222 +msgid "Earth Resources Laboratory Applications Software" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:227 +msgid ":ref:`ENVI <raster.envi>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:228 +msgid "ENVI .hdr Labelled Raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:233 +msgid ":ref:`ERS <raster.ers>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:234 +msgid "ERMapper .ERS" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:239 +msgid ":ref:`ESAT <raster.esat>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:240 +msgid "Envisat Image Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:245 +msgid ":ref:`ESRIC <raster.esric>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:246 +msgid "Esri Compact Cache" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:251 +msgid ":ref:`EXR <raster.exr>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:252 +msgid "Extended Dynamic Range Image File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:256 +#: ../../source/drivers/raster/exr.rst:11 +msgid "libopenexr" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:257 +msgid ":ref:`FAST <raster.fast>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:258 +msgid "EOSAT FAST Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:263 +msgid ":ref:`FIT <raster.fit>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:264 +#: ../../source/drivers/raster/fit.rst:7 +msgid "FIT" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:269 +msgid ":ref:`FITS <raster.fits>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:270 +msgid "Flexible Image Transport System" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:274 +#: ../../source/drivers/raster/fits.rst:9 +msgid "libcfitsio" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:275 +msgid ":ref:`GenBin <raster.genbin>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:276 +msgid "Generic Binary (.hdr labelled)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:281 +msgid ":ref:`GeoRaster <raster.georaster>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:282 +#: ../../source/drivers/raster/georaster.rst:5 +msgid "Oracle Spatial GeoRaster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:286 +#: ../../source/drivers/raster/georaster.rst:9 +msgid "Oracle client libraries" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:287 +msgid ":ref:`GFF <raster.gff>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:288 +msgid "Sandia National Laboratories GSAT File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:293 +msgid ":ref:`GIF <raster.gif>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:294 +msgid "Graphics Interchange Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:298 +#: ../../source/drivers/raster/gif.rst:9 +msgid "(internal GIF library provided)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:299 +msgid ":ref:`GPKG <raster.gpkg>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:300 +msgid "GeoPackage raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:304 +#: ../../source/drivers/raster/gpkg.rst:9 +msgid "libsqlite3 (and any or all of PNG, JPEG, WEBP drivers)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:305 +msgid ":ref:`GRASS <raster.grass>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:306 +#: ../../source/drivers/raster/grass.rst:4 +msgid "GRASS Raster Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:310 +#: ../../source/drivers/raster/grass.rst:8 +#: ../../source/drivers/vector/driver_summary.rst:160 +#: ../../source/drivers/vector/grass.rst:8 +msgid "gdal-grass-driver" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:311 +msgid ":ref:`GRASSASCIIGrid <raster.grassasciigrid>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:312 +msgid "GRASS ASCII Grid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:317 +msgid ":ref:`GRIB <raster.grib>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:318 +msgid "WMO General Regularly-distributed Information in Binary form" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:323 +msgid ":ref:`GS7BG <raster.gs7bg>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:324 +msgid "Golden Software Surfer 7 Binary Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:329 +msgid ":ref:`GSAG <raster.gsag>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:330 +msgid "Golden Software ASCII Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:335 +msgid ":ref:`GSBG <raster.gsbg>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:336 +msgid "Golden Software Binary Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:341 +msgid ":ref:`GSC <raster.gsc>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:342 +msgid "GSC Geogrid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:347 +msgid ":ref:`GTA <raster.gta>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:348 +msgid "Generic Tagged Arrays" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:352 +#: ../../source/drivers/raster/gta.rst:9 +msgid "libgta" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:353 +msgid ":ref:`GTI <raster.gti>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:354 +msgid "GDAL Raster Tile Index" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:359 +msgid ":ref:`GTiff <raster.gtiff>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:360 +msgid "GeoTIFF File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:365 +msgid ":ref:`GXF <raster.gxf>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:366 +msgid "Grid eXchange File" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:371 +msgid ":ref:`HDF4 <raster.hdf4>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:372 +msgid "Hierarchical Data Format Release 4 (HDF4)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:376 +#: ../../source/drivers/raster/hdf4.rst:11 +msgid "libdf" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:377 +msgid ":ref:`HDF5 <raster.hdf5>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:378 +msgid "Hierarchical Data Format Release 5 (HDF5)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:383 +msgid ":ref:`HEIF <raster.heif>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:384 +msgid "ISO/IEC 23008-12:2017 High Efficiency Image File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:388 +#: ../../source/drivers/raster/heif.rst:11 +msgid "libheif (>= 1.1), built against libde265" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:389 +msgid ":ref:`HF2 <raster.hf2>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:390 +msgid "HF2/HFZ heightfield raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:395 +msgid ":ref:`HFA <raster.hfa>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:396 +msgid "Erdas Imagine .img" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:401 +msgid ":ref:`RST <raster.Idrisi>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:402 +msgid "Idrisi Raster Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:407 +msgid ":ref:`ILWIS <raster.ilwis>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:408 +msgid "Raster Map" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:413 +msgid ":ref:`IRIS <raster.iris>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:414 +msgid "Vaisala's weather radar software format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:419 +msgid ":ref:`ISCE <raster.isce>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:420 +#: ../../source/drivers/raster/isce.rst:7 +msgid "ISCE" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:425 +msgid ":ref:`ISG <raster.isg>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:426 +msgid "International Service for the Geoid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:431 +msgid ":ref:`ISIS2 <raster.isis2>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:432 +msgid "USGS Astrogeology ISIS Cube (Version 2)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:437 +msgid ":ref:`ISIS3 <raster.isis3>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:438 +msgid "USGS Astrogeology ISIS Cube (Version 3)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:443 +msgid ":ref:`JDEM <raster.jdem>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:444 +msgid "Japanese DEM (.mem)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:449 +msgid ":ref:`JP2ECW <raster.jp2ecw>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:450 +msgid "ERDAS JPEG2000 (.jp2)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:455 +msgid ":ref:`JP2KAK <raster.jp2kak>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:456 +msgid "JPEG 2000 (based on Kakadu SDK)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:460 +#: ../../source/drivers/raster/jp2kak.rst:9 +msgid "Kakadu SDK" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:461 +msgid ":ref:`JP2LURA <raster.jp2lura>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:462 +msgid "JPEG2000 driver based on Lurawave library" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:466 +#: ../../source/drivers/raster/jp2lura.rst:11 +msgid "Lurawave library" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:467 +msgid ":ref:`JP2MrSID <raster.jp2mrsid>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:468 +msgid "JPEG2000 via MrSID SDK" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:472 +#: ../../source/drivers/raster/driver_summary.rst:592 +#: ../../source/drivers/raster/jp2mrsid.rst:9 +#: ../../source/drivers/raster/mrsid.rst:9 +msgid "MrSID SDK" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:473 +msgid ":ref:`JP2OpenJPEG <raster.jp2openjpeg>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:474 +msgid "JPEG2000 driver based on OpenJPEG library" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:478 +#: ../../source/drivers/raster/jp2openjpeg.rst:9 +msgid "openjpeg >= 2.1" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:479 +msgid ":ref:`JPEG <raster.jpeg>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:480 +msgid "JPEG JFIF File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:484 +#: ../../source/drivers/raster/jpeg.rst:9 +msgid "(internal libjpeg provided)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:485 +msgid ":ref:`JPEGXL <raster.jpegxl>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:486 +msgid "JPEG-XL File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:490 +#: ../../source/drivers/raster/jpegxl.rst:11 +msgid "libjxl" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:491 +msgid ":ref:`JPIPKAK <raster.jpipkak>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:492 +msgid "JPIP Streaming" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:496 +#: ../../source/drivers/raster/jpipkak.rst:9 +msgid "Kakadu library" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:497 +msgid ":ref:`KEA <raster.kea>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:498 +#: ../../source/drivers/raster/kea.rst:5 ../../source/drivers/raster/kea.rst:7 +msgid "KEA" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:502 +#: ../../source/drivers/raster/kea.rst:9 +msgid "libkea and libhdf5 libraries" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:503 +msgid ":ref:`KMLSuperoverlay <raster.kmlsuperoverlay>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:504 +#: ../../source/drivers/raster/kmlsuperoverlay.rst:7 +msgid "KMLSuperoverlay" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:509 +msgid ":ref:`KRO <raster.kro>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:510 +msgid "KOLOR Raw format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:515 +msgid ":ref:`KTX2 <raster.ktx2>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:516 +#: ../../source/drivers/raster/ktx2.rst:5 +#: ../../source/drivers/raster/ktx2.rst:9 +msgid "KTX2" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:521 +msgid ":ref:`L1B <raster.l1b>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:522 +msgid "NOAA Polar Orbiter Level 1b Data Set (AVHRR)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:527 +msgid ":ref:`LAN <raster.lan>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:528 +msgid "Erdas 7.x .LAN and .GIS" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:533 +msgid ":ref:`LCP <raster.lcp>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:534 +msgid "FARSITE v.4 LCP Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:539 +msgid ":ref:`Leveller <raster.leveller>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:540 +msgid "Daylon Leveller Heightfield" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:545 +msgid ":ref:`LOSLAS <raster.loslas>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:546 +msgid "NADCON .los/.las Datum Grid Shift" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:551 +msgid ":ref:`MAP <raster.map>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:552 +msgid "OziExplorer .MAP" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:557 +msgid ":ref:`MRF <raster.marfa>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:558 +msgid "Meta Raster Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:563 +msgid ":ref:`MBTiles <raster.mbtiles>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:564 +#: ../../source/drivers/raster/mbtiles.rst:5 +#: ../../source/drivers/raster/mbtiles.rst:7 +msgid "MBTiles" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:568 +#: ../../source/drivers/raster/driver_summary.rst:766 +#: ../../source/drivers/raster/mbtiles.rst:9 +#: ../../source/drivers/raster/rasterlite.rst:9 +#: ../../source/drivers/vector/driver_summary.rst:145 +#: ../../source/drivers/vector/driver_summary.rst:415 +#: ../../source/drivers/vector/gpkg.rst:8 ../../source/drivers/vector/vfk.rst:8 +msgid "libsqlite3" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:569 +msgid ":ref:`MEM <raster.mem>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:570 +msgid "In Memory Raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:575 +msgid ":ref:`MFF <raster.mff>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:576 +msgid "Vexcel MFF Raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:581 +msgid ":ref:`MFF2 <raster.mff2>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:582 +msgid "Vexcel MFF2 Image" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:587 +msgid ":ref:`MrSID <raster.mrsid>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:588 +msgid "Multi-resolution Seamless Image Database" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:593 +msgid ":ref:`MSG <raster.msg>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:594 +msgid "Meteosat Second Generation" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:598 +#: ../../source/drivers/raster/msg.rst:9 +msgid "msg library" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:599 +msgid ":ref:`MSGN <raster.msgn>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:600 +msgid "Meteosat Second Generation (MSG) Native Archive Format (.nat)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:605 +msgid ":ref:`NDF <raster.ndf>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:606 +msgid "NLAPS Data Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:611 +msgid ":ref:`netCDF <raster.netcdf>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:612 +#: ../../source/drivers/raster/netcdf.rst:5 +msgid "NetCDF: Network Common Data Form" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:616 +#: ../../source/drivers/raster/netcdf.rst:9 +#: ../../source/drivers/vector/driver_summary.rst:265 +#: ../../source/drivers/vector/netcdf.rst:10 +msgid "libnetcdf" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:617 +msgid ":ref:`NGSGEOID <raster.ngsgeoid>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:618 +msgid "NOAA NGS Geoid Height Grids" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:623 +msgid ":ref:`NGW <raster.ngw>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:624 +#: ../../source/drivers/vector/driver_summary.rst:267 +msgid "NextGIS Web" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:629 +msgid ":ref:`NITF <raster.nitf>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:630 +msgid "National Imagery Transmission Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:635 +msgid ":ref:`NOAA_B <raster.noaa_b>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:636 +msgid "NOAA GEOCON/NADCON5 .b format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:641 +msgid ":ref:`NSIDCbin <raster.nsidcbin>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:642 +msgid "National Snow and Ice Data Centre Sea Ice Concentrations" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:647 +msgid ":ref:`NTv2 <raster.ntv2>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:648 +msgid "NTv2 Datum Grid Shift" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:653 +msgid ":ref:`NWT_GRD <raster.nwtgrd>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:654 +#: ../../source/drivers/raster/driver_summary.rst:660 +msgid "Northwood/Vertical Mapper File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:659 +msgid ":ref:`NWT_GRC <raster.nwtgrd>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:665 +msgid ":ref:`OGCAPI <raster.ogcapi>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:666 +msgid "OGC API Tiles / Maps / Coverage" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:671 +msgid ":ref:`OpenFileGDB <raster.openfilegdb>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:672 +#: ../../source/drivers/raster/openfilegdb.rst:4 +msgid "ESRI File Geodatabase raster (OpenFileGDB)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:677 +msgid ":ref:`OZI <raster.ozi>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:678 +msgid "OZF2/OZFX3 raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:683 +msgid ":ref:`JAXAPALSAR <raster.palsar>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:684 +#: ../../source/drivers/raster/palsar.rst:5 +msgid "JAXA PALSAR Processed Products" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:689 +msgid ":ref:`PAux <raster.paux>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:690 +msgid "PCI .aux Labelled Raw Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:695 +msgid ":ref:`PCIDSK <raster.pcidsk>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:696 +msgid "PCI Geomatics Database File" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:701 +msgid ":ref:`PCRaster <raster.pcraster>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:702 +msgid "PCRaster raster file format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:706 +#: ../../source/drivers/raster/pcraster.rst:9 +msgid "(internal libcf provided)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:707 +msgid ":ref:`PDF <raster.pdf>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:708 +#: ../../source/drivers/vector/driver_summary.rst:317 +msgid "Geospatial PDF" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:712 +#: ../../source/drivers/raster/pdf.rst:9 +#: ../../source/drivers/vector/driver_summary.rst:320 +#: ../../source/drivers/vector/pdf.rst:9 +msgid "none for write support, Poppler/PoDoFo/PDFium for read support" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:713 +msgid ":ref:`PDS <raster.pds>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:714 +msgid "Planetary Data System v3" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:719 +msgid ":ref:`PDS4 <raster.pds4>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:720 +msgid "NASA Planetary Data System (Version 4)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:725 +msgid ":ref:`PLMosaic <raster.plmosaic>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:726 +#: ../../source/drivers/raster/plmosaic.rst:5 +msgid "PLMosaic (Planet Labs Mosaics API)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:731 +msgid ":ref:`PNG <raster.png>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:732 +msgid "Portable Network Graphics" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:737 +msgid ":ref:`PNM <raster.pnm>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:738 +msgid "Netpbm (.pgm, .ppm)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:743 +msgid ":ref:`PostGISRaster <raster.postgisraster>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:744 +msgid "PostGIS Raster driver" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:748 +#: ../../source/drivers/raster/postgisraster.rst:9 +msgid "PostgreSQL library" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:749 +msgid ":ref:`PRF <raster.prf>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:750 +#: ../../source/drivers/raster/prf.rst:5 +msgid "PHOTOMOD Raster File" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:755 +msgid ":ref:`R <raster.r>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:756 +msgid "R Object Data Store" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:761 +msgid ":ref:`Rasterlite <raster.rasterlite>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:762 +#: ../../source/drivers/raster/driver_summary.rst:768 +msgid "Rasters in SQLite DB" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:767 +msgid ":ref:`SQLite <raster.rasterlite2>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:772 +#: ../../source/drivers/raster/rasterlite2.rst:14 +msgid "libsqlite3, librasterlite2, libspatialite" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:773 +msgid ":ref:`RDB <raster.rdb>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:774 +msgid "*RIEGL* Database" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:778 +#: ../../source/drivers/raster/rdb.rst:11 +msgid "rdblib >= 2.2.0." +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:779 +msgid ":ref:`RIK <raster.rik>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:780 +msgid "Swedish Grid Maps" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:784 +#: ../../source/drivers/raster/rik.rst:9 +msgid "(internal zlib is used if necessary)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:785 +msgid ":ref:`RMF <raster.rmf>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:786 +msgid "Raster Matrix Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:791 +msgid ":ref:`ROI_PAC <raster.roi_pac>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:792 +#: ../../source/drivers/raster/roi_pac.rst:7 +msgid "ROI_PAC" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:797 +msgid ":ref:`RPFTOC <raster.rpftoc>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:798 +msgid "Raster Product Format/RPF (a.toc)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:803 +msgid ":ref:`RRASTER <raster.rraster>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:804 +msgid "R Raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:809 +msgid ":ref:`RS2 <raster.rs2>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:810 +msgid "RadarSat 2 XML Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:815 +msgid ":ref:`S102 <raster.s102>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:816 +msgid "S-102 Bathymetric Surface Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:821 +msgid ":ref:`S104 <raster.s104>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:822 +msgid "S-104 Water Level Information for Surface Navigation Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:827 +msgid ":ref:`S111 <raster.s111>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:828 +msgid "S-111 Surface Currents Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:833 +msgid ":ref:`SAFE <raster.safe>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:834 +msgid "Sentinel-1 SAFE XML Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:839 +msgid ":ref:`SAR_CEOS <raster.sar_ceos>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:840 +msgid "CEOS SAR Image" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:845 +msgid ":ref:`SAGA <raster.sdat>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:846 +msgid "SAGA GIS Binary Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:851 +msgid ":ref:`SDTS <raster.sdts>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:852 +msgid "USGS SDTS DEM" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:857 +msgid ":ref:`SENTINEL2 <raster.sentinel2>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:858 +msgid "Sentinel-2 Products" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:863 +msgid ":ref:`SGI <raster.sgi>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:864 +msgid "SGI Image Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:869 +msgid ":ref:`SIGDEM <raster.sigdem>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:870 +msgid "Scaled Integer Gridded DEM" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:875 +msgid ":ref:`SNODAS <raster.snodas>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:876 +msgid "Snow Data Assimilation System" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:881 +msgid ":ref:`SRP <raster.srp>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:882 +msgid "Standard Product Format (ASRP/USRP) (.gen)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:887 +msgid ":ref:`SRTMHGT <raster.srtmhgt>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:888 +msgid "SRTM HGT Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:893 +msgid ":ref:`STACIT <raster.stacit>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:894 +msgid "Spatio-Temporal Asset Catalog Items" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:899 +msgid ":ref:`STACTA <raster.stacta>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:900 +msgid "Spatio-Temporal Asset Catalog Tiled Assets" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:905 +msgid ":ref:`Terragen <raster.terragen>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:906 +msgid "Terragen™ Terrain File" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:911 +msgid ":ref:`TGA <raster.tga>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:912 +msgid "TARGA Image File Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:917 +msgid ":ref:`TIL <raster.til>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:918 +msgid "EarthWatch/DigitalGlobe .TIL" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:923 +msgid ":ref:`TileDB <raster.tiledb>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:924 +msgid "TileDB raster" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:928 +#: ../../source/drivers/raster/tiledb.rst:11 +msgid "TileDB (>= 2.7 starting with GDAL 3.7)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:929 +msgid ":ref:`TSX <raster.tsx>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:930 +msgid "TerraSAR-X Product" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:935 +msgid ":ref:`USGSDEM <raster.usgsdem>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:936 +msgid "USGS ASCII DEM (and CDED)" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:941 +msgid ":ref:`VICAR <raster.vicar>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:942 +#: ../../source/drivers/raster/vicar.rst:7 +msgid "VICAR" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:947 +msgid ":ref:`VRT <raster.vrt>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:948 +msgid "GDAL Virtual Format" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:953 +msgid ":ref:`WCS <raster.wcs>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:954 +msgid "OGC Web Coverage Service" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:959 +msgid ":ref:`WEBP <raster.webp>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:960 +#: ../../source/drivers/raster/gtiff.rst:1181 +#: ../../source/drivers/raster/webp.rst:7 +msgid "WEBP" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:964 +#: ../../source/drivers/raster/webp.rst:9 +msgid "libwebp" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:965 +msgid ":ref:`WMS <raster.wms>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:966 +msgid "Web Map Services" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:971 +msgid ":ref:`WMTS <raster.wmts>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:972 +msgid "OGC Web Map Tile Service" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:977 +msgid ":ref:`XPM <raster.xpm>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:978 +msgid "X11 Pixmap" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:983 +msgid ":ref:`XYZ <raster.xyz>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:984 +msgid "ASCII Gridded XYZ" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:989 +msgid ":ref:`Zarr <raster.zarr>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:990 +#: ../../source/drivers/raster/zarr.rst:5 +#: ../../source/drivers/raster/zarr.rst:9 +msgid "Zarr" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:994 +msgid "Built-in by default, but liblz4, libxz (lzma), libzstd and libblosc" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:995 +msgid ":ref:`ZMAP <raster.zmap>`" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:996 +msgid "ZMap Plus Grid" +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:1002 +msgid "(1): Creation refers to implementing :cpp:func:`GDALCreate`." +msgstr "" + +#: ../../source/drivers/raster/driver_summary.rst:1003 +msgid "(2): Copy refers to implementing :cpp:func:`GDALCreateCopy`." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:5 +msgid "DTED -- Military Elevation Data" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:7 +msgid "DTED" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:11 +msgid "" +"GDAL supports DTED Levels 0, 1, and 2 elevation data for read access. " +"Elevation data is returned as 16 bit signed integer. Appropriate " +"projection and georeferencing information is also returned. A variety of " +"header fields are returned dataset level metadata." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:28 +msgid "" +"|about-config-options| This paragraph lists the configuration options " +"that can be set to alter the default behavior of the DTED driver." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:65 +msgid "Read Issues" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:68 +msgid "Read speed" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:70 +msgid "" +"Elevation data in DTED files are organized per columns. This data " +"organization doesn't fit very well with some scanline oriented algorithms" +" and can cause slowdowns, especially for DTED Level 2 datasets. By " +"defining :config:`GDAL_DTED_SINGLE_BLOCK=TRUE`, a whole DTED dataset will" +" be considered as a single block. The first access to the file will be " +"slow, but further accesses will be much quicker. Only use that option if " +"you need to do processing on a whole file." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:79 +msgid "Georeferencing Issues" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:87 +msgid "" +"The DTED specification (`MIL-PRF-89020B <http://earth-" +"info.nga.mil/publications/specs/printed/89020B/89020B.pdf>`__) states " +"that *horizontal datum shall be the World Geodetic System (WGS 84)*. The " +"vertical datum is defined as EGM96, or EPSG:5773. However, there are " +"still people using old data files georeferenced in WGS 72. A header field" +" indicates the horizontal datum code, so we can detect and handle this " +"situation." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:89 +msgid "" +"If the horizontal datum specified in the DTED file is WGS84, the DTED " +"driver will report WGS 84 as SRS." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:91 +msgid "" +"If the horizontal datum specified in the DTED file is WGS72, the DTED " +"driver will report WGS 72 as SRS and issue a warning." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:93 +msgid "" +"If the horizontal datum specified in the DTED file is neither WGS84 nor " +"WGS72, the DTED driver will report WGS 84 as SRS and issue a warning." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:98 +msgid "Checksum Issues" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:100 +msgid "" +"The default behavior of the DTED driver is to ignore the checksum while " +"reading data from the files. However, you may specify the environment " +"variable ``DTED_VERIFY_CHECKSUM=YES`` if you want the checksums to be " +"verified. In some cases, the checksum written in the DTED file is wrong " +"(the data producer did a wrong job). This will be reported as a warning. " +"If the checksum written in the DTED file and the checksum computed from " +"the data do not match, an error will be issued." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:109 +#: ../../source/drivers/raster/gif.rst:33 +#: ../../source/drivers/raster/gtiff.rst:354 +#: ../../source/drivers/raster/hdf4.rst:193 +#: ../../source/drivers/raster/hfa.rst:41 +#: ../../source/drivers/raster/isis2.rst:40 +#: ../../source/drivers/raster/jp2kak.rst:137 +#: ../../source/drivers/raster/netcdf.rst:330 +#: ../../source/drivers/raster/nitf.rst:88 +#: ../../source/drivers/raster/pdf.rst:208 +#: ../../source/drivers/raster/usgsdem.rst:43 +#: ../../source/drivers/vector/csv.rst:417 +#: ../../source/drivers/vector/dgn.rst:98 +#: ../../source/drivers/vector/dgnv8.rst:100 +#: ../../source/drivers/vector/flatgeobuf.rst:94 +#: ../../source/drivers/vector/geoconcept.rst:52 +#: ../../source/drivers/vector/georss.rst:126 +#: ../../source/drivers/vector/gml.rst:638 +#: ../../source/drivers/vector/gmt.rst:31 +#: ../../source/drivers/vector/gpx.rst:192 +#: ../../source/drivers/vector/hana.rst:55 +#: ../../source/drivers/vector/jml.rst:68 +#: ../../source/drivers/vector/memory.rst:32 +#: ../../source/drivers/vector/miramon.rst:195 +#: ../../source/drivers/vector/mitab.rst:43 +#: ../../source/drivers/vector/mssqlspatial.rst:99 +#: ../../source/drivers/vector/mysql.rst:85 +#: ../../source/drivers/vector/oci.rst:109 +#: ../../source/drivers/vector/odbc.rst:100 +#: ../../source/drivers/vector/pg.rst:115 +#: ../../source/drivers/vector/shapefile.rst:146 +#: ../../source/drivers/vector/sqlite.rst:220 +#: ../../source/drivers/vector/vrt.rst:28 +msgid "Creation Issues" +msgstr "" + +#: ../../source/drivers/raster/dted.rst:111 +msgid "" +"The DTED driver does support creating new files, but the input data must " +"be exactly formatted as a Level 0, 1 or 2 cell. That is the size, and " +"bounds must be appropriate for a cell." +msgstr "" + +#: ../../source/drivers/raster/dted.rst:118 +msgid "Implemented as :source_file:`frmts/dted/dteddataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:5 +msgid "ECRGTOC -- ECRG Table Of Contents (TOC.xml)" +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:7 +msgid "ECRGTOC" +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:11 +msgid "" +"This is a read-only reader for ECRG (Enhanced Compressed Raster Graphic) " +"products, that uses the table of content file, TOC.xml, and exposes it as" +" a virtual dataset whose coverage is the set of ECRG frames contained in " +"the table of content." +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:16 +msgid "" +"The driver will report a different subdataset for each subdataset found " +"in the TOC.xml file. Each subdataset consists of the frames of same " +"product id, disk id, and with same scale." +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:20 +msgid "Result of a gdalinfo on a TOC.xml file." +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:39 +msgid ":ref:`raster.nitf`: format of the ECRG frames" +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:40 +#: ../../source/drivers/raster/nitf.rst:355 +msgid "" +"`MIL-PRF-32283 <http://www.everyspec.com/MIL-PRF/MIL-" +"PRF+%28030000+-+79999%29/MIL-PRF-32283_26022/>`__ : specification of ECRG" +" products" +msgstr "" + +#: ../../source/drivers/raster/ecrgtoc.rst:43 +msgid "NOTE: Implemented as :source_file:`frmts/nitf/ecrgtocdataset.cpp`" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:5 +msgid "ECW -- Enhanced Compressed Wavelets (.ecw)" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:7 +msgid "ECW" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:11 +msgid "" +"GDAL supports reading and writing ECW files using the ERDAS ECW/JP2 SDK " +"developed by Hexagon Geospatial (formerly Intergraph, ERDAS, ERMapper). " +"Support is optional and requires linking in the libraries available from " +"the ECW/JP2 SDK Download page." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:28 +#: ../../source/drivers/raster/jp2ecw.rst:33 +msgid "Licensing" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:30 +#: ../../source/drivers/raster/jp2ecw.rst:35 +msgid "" +"The ERDAS ECW/JP2 SDK v5.x is available under multiple license types. For" +" Desktop usage, decoding any sized ECW/JP2 image is made available free " +"of charge. To compress, deploy on a Server platform, or decode unlimited " +"sized files on Mobile platforms a license must be purchased from Hexagon " +"Geospatial." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:37 +#: ../../source/drivers/raster/jp2ecw.rst:42 +msgid "History" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:39 +#: ../../source/drivers/raster/jp2ecw.rst:44 +msgid "v3.x - Last release, 2006" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:40 +#: ../../source/drivers/raster/jp2ecw.rst:45 +msgid "v4.x - Last release, 2012" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:41 +#: ../../source/drivers/raster/jp2ecw.rst:46 +msgid "v5.x - Active development, 2013 - current" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:46 +msgid "" +"The ERDAS ECW/JP2 v4.x and v5.x SDK is only free for image decompression." +" To compress images it is necessary to build with the read/write SDK and " +"to provide an OEM licensing key at runtime which may be purchased from " +"ERDAS." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:51 +msgid "" +"For those still using the ECW 3.3 SDK, images less than 500MB may be " +"compressed for free, while larger images require licensing from ERDAS. " +"See the licensing agreement and the LARGE_OK option." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:55 +msgid "" +"Files to be compressed into ECW format must also be at least 128x128. ECW" +" currently only supports 8 bits per channel for ECW Version 2 files. ECW " +"Version 3 files supports 16 bits per channel (as Uint16 data type). " +"Please see Creation options to enable ECW V3 files writing" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:60 +msgid "" +"When writing coordinate system information to ECW files, many less common" +" coordinate systems are not mapped properly. If you know the ECW name for" +" the coordinate system you can force it to be set at creation time with " +"the PROJ and DATUM creation options." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:65 +msgid "" +"ECW format does not support creation of overviews since the ECW format is" +" already considered to be optimized for \"arbitrary overviews\"." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:71 +#: ../../source/drivers/raster/envi.rst:28 +#: ../../source/drivers/raster/jp2ecw.rst:89 +#: ../../source/drivers/raster/paux.rst:20 +msgid "Creation Options:" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:131 +#: ../../source/drivers/raster/hfa.rst:142 +#: ../../source/drivers/raster/jp2ecw.rst:297 +#: ../../source/drivers/raster/jp2kak.rst:59 +#: ../../source/drivers/raster/jp2lura.rst:50 +#: ../../source/drivers/raster/netcdf.rst:584 +#: ../../source/drivers/vector/pg.rst:396 +msgid "Configuration Options" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:133 +msgid "" +"|about-config-options| The ERDAS ECW SDK supports a variety of " +"configuration options to control various features. See the ECW SDK " +"documentation for full details on the meaning of these options." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:203 +msgid "The GDAL-specific options:" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:218 +msgid "ECW Version 3 Files" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:220 +msgid "ECW 5.x SDK introduces a new file format version which," +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:222 +msgid "" +"Storage of data statistics, histograms, metadata, RPC information within " +"the file header" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:224 +msgid "Support for UInt16 data type" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:225 +msgid "Ability to update regions within an existing ECW v3 file" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:226 +msgid "Introduces other space saving optimizations" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:228 +msgid "" +"Note: This version is not backward compatible and will fail to decode in " +"v3.x or v4.x ECW/JP2 SDK's. The File VERSION Metadata will advertise " +"whether the file is ECW v2 or ECW v3." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:233 +msgid "ECWP" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:235 +msgid "" +"In addition to local files, this driver also supports access to streaming" +" network imagery services using the proprietary \"ECWP\" protocol from " +"the ERDAS APOLLO product. Use the full ecwp:// prefixed dataset url as " +"input. When built with ECW/JP2 SDK v4.1 or newer it is also possible to " +"take advantage of :ref:`rfc-24` for asynchronous / progressive streaming " +"access to ECWP services." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:243 +msgid "Metadata / Georeferencing" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:245 +msgid "" +"The PROJ, DATUM and UNITS found in the ECW header are reported in the ECW" +" metadata domain. They can also be set with the SetMetadataItem() method," +" in order to update the header information of an existing ECW file, " +"opened in update mode, without modifying the imagery." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:250 +msgid "" +"The geotransform and projection can also be modified with the " +"SetGeoTransform() and SetProjection() methods. If the projection is set " +"with SetProjection() and the PROJ, DATUM or UNITS with SetMetadataItem()," +" the later values will override the values built from the projection " +"string." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:256 +msgid "" +"All those can for example be modified with the -a_ullr, -a_srs or -mo " +"switches of the :ref:`gdal_edit` utility." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:259 +#: ../../source/drivers/raster/isis3.rst:51 +#: ../../source/drivers/raster/mem.rst:30 +#: ../../source/drivers/raster/vicar.rst:40 +#: ../../source/drivers/raster/vicar.rst:145 +#: ../../source/drivers/raster/vrt.rst:1957 +#: ../../source/drivers/raster/wld.rst:19 +#: ../../source/drivers/vector/gpkg.rst:584 +#: ../../source/drivers/vector/shapefile.rst:182 +msgid "For example:" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:268 +msgid "File Metadata Keys:" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:270 +msgid "FILE_METADATA_ACQUISITION_DATE" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:271 +msgid "FILE_METADATA_ACQUISITION_SENSOR_NAME" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:272 +msgid "FILE_METADATA_ADDRESS" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:273 +msgid "FILE_METADATA_AUTHOR" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:274 +msgid "FILE_METADATA_CLASSIFICATION" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:275 +msgid "FILE_METADATA_COMPANY - should be set to ECW_ENCODE_COMPANY" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:276 +msgid "FILE_METADATA_COMPRESSION_SOFTWARE - updated during recompression" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:277 +msgid "FILE_METADATA_COPYRIGHT" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:278 +msgid "FILE_METADATA_EMAIL" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:279 +msgid "FILE_METADATA_TELEPHONE" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:280 +msgid "CLOCKWISE_ROTATION_DEG" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:281 +msgid "COLORSPACE" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:282 +msgid "COMPRESSION_DATE" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:283 +msgid "COMPRESSION_RATE_ACTUAL" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:284 +msgid "" +"COMPRESSION_RATE_TARGET. This is the percentage of the target compressed " +"file size divided by the uncompressed file size. This is equal to 100 / " +"(100 - TARGET) where TARGET is the value of the TARGET creation option " +"used at file creation, so a COMPRESSION_RATE_TARGET=1 is equivalent to a " +"TARGET=0 (ie no compression), COMPRESSION_RATE_TARGET=5 is equivalent to " +"TARGET=80 (ie dividing uncompressed file size by 5), etc..." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:291 +msgid "VERSION" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:296 +#: ../../source/drivers/raster/jp2ecw.rst:374 +msgid "Implemented as :source_file:`frmts/ecw/ecwdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:297 +msgid "" +"ERDAS ECW/JP2 SDK Read-Only Redistributable available at " +"`www.hexagongeospatial.com <https://supportsi.hexagon.com/help/s/article" +"/ERDAS-ECW-JP2-SDK-Read-Only-Redistributable-download>`__" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:299 +msgid "" +"Further product information available in the `User Guide " +"<https://bynder.hexagon.com/m/5af86a8895f6696f/original/Hexagon_GSP_ERDAS_ECW_JP2_SDK_5_5_User_Guide.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:301 +msgid "" +"Support for non-GDAL specific issues should be directed to the `Hexagon " +"Geospatial public forum <https://supportsi.hexagon.com/help/s/erdas-" +"apollo>`__" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:304 +msgid "" +"Community contributed `patches " +"<https://github.com/rouault/libecwj2-3.3-builds/blob/main/libecwj2-3.3.patch>`__" +" to apply to ECW SDK 3.3 sources" +msgstr "" + +#: ../../source/drivers/raster/ecw.rst:305 +#: ../../source/drivers/raster/jp2ecw.rst:382 +msgid "`GDAL ECW Build Hints <http://trac.osgeo.org/gdal/wiki/ECW>`__" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:5 +msgid "EEDAI - Google Earth Engine Data API Image" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:7 +msgid "EEDAI" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:13 +msgid "" +"The driver supports read-only operations to access image content, using " +"Google Earth Engine REST API." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:24 +#: ../../source/drivers/raster/plmosaic.rst:30 +#: ../../source/drivers/vector/plscenes_data_v1.rst:21 +msgid "The minimal syntax to open a datasource is :" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:30 +msgid "" +"where asset is something like projects/earthengine-" +"public/assets/COPERNICUS/S2/20170430T190351_20170430T190351_T10SEG, and " +"band_names a comma separated list of band names (typically indicated by " +"subdatasets on the main image)" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:64 +#: ../../source/drivers/vector/eeda.rst:44 +msgid "Authentication methods" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:66 +#: ../../source/drivers/vector/eeda.rst:46 +msgid "The following authentication methods can be used:" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:68 +msgid "" +"Authentication Bearer header passed through the :config:`EEDA_BEARER` or " +":config:`EEDA_BEARER_FILE` configuration options." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:70 +#: ../../source/drivers/vector/eeda.rst:50 +msgid "" +"Service account private key file, through the " +":config:`GOOGLE_APPLICATION_CREDENTIALS` configuration option." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:72 +#: ../../source/drivers/vector/eeda.rst:52 +msgid "" +"OAuth2 Service Account authentication through the " +":config:`EEDA_PRIVATE_KEY`/ :config:`EEDA_PRIVATE_KEY_FILE` + " +":config:`EEDA_CLIENT_EMAIL` configuration options." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:74 +msgid "" +"Finally if none of the above method succeeds, the code will check if the " +"current machine is a Google Compute Engine instance, and if so will use " +"the permissions associated to it (using the default service account " +"associated with the VM). To force a machine to be detected as a GCE " +"instance (for example for code running in a container with no access to " +"the boot logs), you can set :config:`CPL_MACHINE_IS_GCE=YES`." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:136 +#: ../../source/drivers/raster/gpkg.rst:623 +#: ../../source/drivers/raster/gtiff.rst:114 +#: ../../source/drivers/raster/rasterlite.rst:148 +#: ../../source/drivers/raster/vrt.rst:746 +msgid "Overviews" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:138 +msgid "" +"The driver expose overviews, following a logic of decreasing power of 2 " +"factors, until both dimensions of the smallest overview are lower than " +"256 pixels." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:143 +#: ../../source/drivers/raster/gtiff.rst:777 +#: ../../source/drivers/raster/l1b.rst:102 +#: ../../source/drivers/raster/stacit.rst:94 +#: ../../source/drivers/raster/stacta.rst:78 +msgid "Subdatasets" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:145 +msgid "" +"When all bands don't have the same georeferencing, resolution, CRS or " +"image dimensions, the driver will expose subdatasets. Each subdataset " +"groups together bands of the same dimension, extent, resolution and CRS." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:152 +msgid "" +"The driver will expose metadata reported in \"properties\" as dataset-" +"level or band-level metadata." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:156 +msgid "Pixel encoding" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:158 +msgid "" +"By default (:oo:`PIXEL_ENCODING=AUTO`), the driver will request pixels in" +" a format compatible of the number and data types of the bands. The PNG, " +"JPEG and AUTO_JPEG_PNG can only be used with bands of type Byte." +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:165 +msgid "Get metadata on an image:" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:171 +#: ../../source/drivers/raster/fast.rst:72 +#: ../../source/drivers/raster/fast.rst:76 +#: ../../source/drivers/raster/fast.rst:80 +#: ../../source/drivers/raster/fast.rst:84 +#: ../../source/drivers/raster/gtiff.rst:898 +#: ../../source/drivers/raster/isis3.rst:144 +#: ../../source/drivers/raster/mem.rst:38 +#: ../../source/drivers/raster/plmosaic.rst:116 +#: ../../source/drivers/raster/plmosaic.rst:122 +#: ../../source/drivers/raster/vicar.rst:130 +#: ../../source/drivers/vector/amigocloud.rst:184 +#: ../../source/drivers/vector/eeda.rst:190 +#: ../../source/drivers/vector/hana.rst:281 +#: ../../source/drivers/vector/hana.rst:287 +#: ../../source/drivers/vector/plscenes_data_v1.rst:175 +#: ../../source/drivers/vector/plscenes_data_v1.rst:181 +#: ../../source/drivers/vector/plscenes_data_v1.rst:236 +#: ../../source/drivers/vector/wfs.rst:207 +msgid "or" +msgstr "" + +#: ../../source/drivers/raster/eedai.rst:180 +msgid ":ref:`Google Earth Engine Data API driver <vector.eeda>`" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:5 +msgid "EHdr -- ESRI .hdr Labelled" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:7 +msgid "EHdr" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:11 +msgid "" +"GDAL supports reading and writing the ESRI .hdr labeling format, often " +"referred to as ESRI BIL format. Eight, sixteen and thirty-two bit integer" +" raster data types are supported as well as 32 bit floating point. " +"Coordinate systems (from a .prj file), and georeferencing are supported. " +"Unrecognized options in the .hdr file are ignored. To open a dataset " +"select the file with the image file (often with the extension .bil). If " +"present .clr color table files are read, but not written. If present, " +"image.rep file will be read to extract the projection system of " +"SpatioCarte Defense 1.0 raster products." +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:21 +msgid "" +"This driver does not always do well differentiating between floating " +"point and integer data. The GDAL extension to the .hdr format to " +"differentiate is to add a field named PIXELTYPE with values of either " +"FLOAT, SIGNEDINT or UNSIGNEDINT. In combination with the NBITS field it " +"is possible to described all variations of pixel types." +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:27 +msgid "eg." +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:41 +msgid "This driver may be sufficient to read GTOPO30 data." +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:43 +msgid "NOTE: Implemented as :source_file:`frmts/raw/ehdrdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:59 +msgid "" +"`ESRI whitepaper: + Extendable Image Formats for ArcView GIS 3.1 and 3.2 " +"<http://downloads.esri.com/support/whitepapers/other_/eximgav.pdf>`__ " +"(BIL, see p. 5)" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:62 +msgid "" +"`GTOPO30 - Global Topographic Data " +"<http://edcdaac.usgs.gov/gtopo30/gtopo30.html>`__" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:64 +msgid "`GTOPO30 Documentation <http://edcdaac.usgs.gov/gtopo30/README.html>`__" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:66 +msgid "" +"`SpatioCarte Defense 1.0 specification " +"<http://eden.ign.fr/download/pub/doc/emabgi/spdf10.pdf/download>`__ (in " +"French)" +msgstr "" + +#: ../../source/drivers/raster/ehdr.rst:69 +msgid "`SRTMHGT Driver <#SRTMHGT>`__" +msgstr "" + +#: ../../source/drivers/raster/eir.rst:5 +msgid "EIR -- Erdas Imagine Raw" +msgstr "" + +#: ../../source/drivers/raster/eir.rst:7 +msgid "EIR" +msgstr "" + +#: ../../source/drivers/raster/eir.rst:11 +msgid "" +"GDAL supports the Erdas Imagine Raw format for read access including 1, " +"2, 4, 8, 16 and 32bit unsigned integers, 16 and 32bit signed integers and" +" 32 and 64bit complex floating point. Georeferencing is supported." +msgstr "" + +#: ../../source/drivers/raster/eir.rst:15 +msgid "" +"To open a dataset select the file with the header information. The driver" +" finds the image file from the header information. Erdas documents call " +"the header file the \"raw\" file and it may have the extension .raw while" +" the image file that contains the actual raw data may have the extension " +".bl." +msgstr "" + +#: ../../source/drivers/raster/eir.rst:21 +msgid "NOTE: Implemented as :source_file:`frmts/raw/eirdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/elas.rst:5 +msgid "ELAS - Earth Resources Laboratory Applications Software" +msgstr "" + +#: ../../source/drivers/raster/elas.rst:7 +msgid "ELAS" +msgstr "" + +#: ../../source/drivers/raster/elas.rst:11 +msgid "" +"ELAS is an old remote sensing system still used for a variety of research" +" projects within NASA. The ELAS format support can be found in " +":source_file:`frmts/elas`." +msgstr "" + +#: ../../source/drivers/raster/elas.rst:29 +msgid "" +"`Short announcement of ELAS driver in GDAL " +"<http://lists.osgeo.org/pipermail/gdal-dev/1999-May/002942.html>`__" +msgstr "" + +#: ../../source/drivers/raster/elas.rst:31 +msgid "" +"`NASA Software Used In Imaging Service " +"<http://nctn.hq.nasa.gov/innovation/innovation102/4-advtech3.html>`__ " +"includes ELAS overview" +msgstr "" + +#: ../../source/drivers/raster/envi.rst:5 +msgid "ENVI -- ENVI .hdr Labelled Raster" +msgstr "" + +#: ../../source/drivers/raster/envi.rst:7 +msgid "ENVI" +msgstr "" + +#: ../../source/drivers/raster/envi.rst:11 +msgid "" +"GDAL supports some variations of raw raster files with associated ENVI " +"style .hdr files describing the format. To select an existing ENVI raster" +" file select the binary file containing the data (as opposed to the .hdr " +"file), and GDAL will find the .hdr file by replacing the dataset " +"extension with .hdr." +msgstr "" + +#: ../../source/drivers/raster/envi.rst:17 +msgid "" +"GDAL should support reading bil, bip and bsq interleaved formats, and " +"most pixel types are supported, including 8bit unsigned, 16 and 32bit " +"signed and unsigned integers, 32bit and 64 bit floating point, and 32bit " +"and 64bit complex floating point. There is limited support for " +"recognising map_info keywords with the coordinate system and " +"georeferencing. In particular, UTM and State Plane should work." +msgstr "" + +#: ../../source/drivers/raster/envi.rst:24 +msgid "" +"All ENVI header fields are stored in the ENVI metadata domain, and all of" +" these can then be written out to the header file." +msgstr "" + +#: ../../source/drivers/raster/envi.rst:50 +msgid "NOTE: Implemented as :source_file:`frmts/raw/envidataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ers.rst:5 +msgid "ERS -- ERMapper .ERS" +msgstr "" + +#: ../../source/drivers/raster/ers.rst:7 +msgid "ERS" +msgstr "" + +#: ../../source/drivers/raster/ers.rst:11 +msgid "" +"GDAL supports reading and writing raster files with .ers header files, " +"with some limitations. The .ers ascii format is used by ERMapper for " +"labeling raw data files, as well as for providing extended metadata, and " +"georeferencing for some other file formats. The .ERS format, or variants " +"are also used to hold descriptions of ERMapper algorithms, but these are " +"not supported by GDAL." +msgstr "" + +#: ../../source/drivers/raster/ers.rst:18 +msgid "" +"The PROJ, DATUM and UNITS values found in the ERS header are reported in " +"the ERS metadata domain." +msgstr "" + +#: ../../source/drivers/raster/ers.rst:67 +msgid "Implemented as :source_file:`frmts/ers/ersdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/esat.rst:5 +msgid "ESAT -- Envisat Image Product" +msgstr "" + +#: ../../source/drivers/raster/esat.rst:7 +msgid "ESAT" +msgstr "" + +#: ../../source/drivers/raster/esat.rst:11 +msgid "" +"GDAL supports the Envisat product format for read access. All sample " +"types are supported. Files with two matching measurement datasets (MDS) " +"are represented as having two bands. Currently all ASAR Level 1 and above" +" products, and some MERIS and AATSR products are supported." +msgstr "" + +#: ../../source/drivers/raster/esat.rst:16 +msgid "" +"The control points of the GEOLOCATION GRID ADS dataset are read if " +"available, generally giving a good coverage of the dataset. The GCPs are " +"in WGS84." +msgstr "" + +#: ../../source/drivers/raster/esat.rst:20 +msgid "" +"Virtually all key/value pairs from the MPH and SPH (primary and secondary" +" headers) are copied through as dataset level metadata." +msgstr "" + +#: ../../source/drivers/raster/esat.rst:23 +msgid "" +"ASAR and MERIS parameters contained in the ADS and GADS records (excluded" +" geolocation ones) can be retrieved as key/value pairs using the " +"\"RECORDS\" metadata domain." +msgstr "" + +#: ../../source/drivers/raster/esat.rst:27 +msgid "NOTE: Implemented as :source_file:`frmts/envisat/envisatdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/esat.rst:29 +msgid "" +"See Also: `Envisat <https://earth.esa.int/eogateway/missions/envisat>`__ " +"at ESA." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:5 +msgid "ESRIC -- Esri Compact Cache" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:7 +msgid "ESRIC" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:11 +msgid "Read Esri Compact Cache V2 as a single raster" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:21 +msgid "Esri Compact Cache V2" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:23 +msgid "" +"A reader for `Esri Compact Cache V2 <https://github.com/Esri/raster-" +"tiles-compactcache>`__. The cache is stored in multiple files located in " +"a specific folder structure. From the point of view of this driver the " +"raster is represented by the file named conf.xml, which resides in the " +"root folder of the cache. The exact content of this XML file is not " +"fully documented by Esri, and is subject to change. This driver uses only" +" a few of the XML fields, as necessary to read the raster." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:32 +msgid "Esri Tile Package (.tpkx)" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:34 +msgid "" +"Starting from GDAL 3.8, the driver supports reading the `Esri Tile " +"Package Specification <https://github.com/Esri/tile-package-spec>`__. A " +"tile package is a compressed file with \".tpkx\" extension. It has a " +"simplified structure, containing image tiles stored in Compact Cache V2 " +"storage format and tiling scheme and other metadata stored in a JSON " +"file." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:43 +msgid "" +"Tile packages with \".tpk\" extension, use compact storage V1 format for " +"cache tiles. The spec for this package type is not available and it is " +"not supported by GDAL." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:50 +msgid "" +"If the /path/Layers contains an Esri Compact Cache in V2 format in the " +"normal Web Mercator tile grid, this command will copy the level 2 content" +" into a TIF file." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:54 +msgid "``gdal_translate -outsize 1024 1024 path/Layers/conf.xml output.tif``" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:56 +msgid "To convert a .tpkx file to a GeoTIFF:" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:58 +msgid "``gdal_translate -outsize 1024 1024 \"/path/to/my.tpkx output.tif``" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:61 +msgid "Features and Limitations" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:63 +msgid "" +"Only V2 Compact cache is supported. This format is identified by the " +"value **esriMapCacheStorageModeCompactV2** in the " +"**CacheInfo.TileCacheInfo.StorageFormat** element of the conf.xml file. " +"Other legacy Esri cache formats are not supported." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:68 +msgid "" +"Only caches with tiles of 256 by 256 pixels are supported. These are " +"stored as the values of the **CacheInfo.TileCacheInfo.TileRows** and " +"**CacheInfo.TileCacheInfo.TileCols** elements." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:73 +msgid "" +"Tiles in the cache can be in different formats, including JPEG and PNG. " +"The most common are 8 bit color or grayscale JPEG and color PNG with or " +"without opacity. These caches will have the value **JPEG**, **PNG** or " +"**MIXED** in the **CacheInfo.TileImageInfo.CacheTileFormat** element. " +"Other tile formats, such as **PNG8** are not supported. The raster will " +"be promoted to RGB or RGBA by this driver, even if the source is " +"grayscale." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:82 +msgid "" +"Only caches with 128 by 128 tiles in a bundle file are supported. This " +"value, the linear number of tiles in a bundle, is contained in the " +"**CacheInfo.CacheStorageInfo.PacketSize** element." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:87 +msgid "" +"The spatial reference is obtained from the " +"**CacheInfo.TileCacheInfo.SpatialReference.WKT** field. If this field is " +"not present, the default value of EPSG:4326 is assumed." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:91 +msgid "" +"As defined in the standard conf.xml file, the cache tile grid has an " +"origin location, stored in the **CacheInfo.TileCacheInfo.TileOrigin** " +"element, which has X and Y components. The cache size is not explicitly " +"defined. The ESRIC format driver will assume a symmetric area around the " +"0,0 coordinates, in the reference system coordinates. This is true for " +"the standard Web Mercator and GCS reference systems. If this assumption " +"is not valid, the conf.xml file can be modified, adding a non-standard " +"**CacheInfo.TileCacheInfo.TileEnd** element with the appropriate values " +"for the X and Y components, similar to the **TileOrigin**. Note that the " +"grid origin and size is different from the raster data extent. For " +"example, it is common to generate a cache in the standard Web Mercator " +"tile grid, which is defined for the whole Earth, even if data is only " +"available for a small region of the globe." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:108 +msgid "" +"A bundled cache has multiple resolution levels, encoded in a series of " +"**CacheInfo.TileCacheInfo.LODInfos.LODInfo** nodes. The **LODInfo** XML " +"nodes are identified by the **LevelID** value, which have to be " +"successive, starting with 0 for the level with the largest value for the " +"**Resolution** and increasing towards the **LODInfo** node with smallest " +"**Resolution** value. The level convention is similar to other Level, Row" +" and Column tile addressing schemes used in WMTS for example. While " +"common, it is not a requirement to have the resolutions of two successive" +" levels differ by a factor of two. Each cache level will be read as an " +"overview, at the appropriate resolution. The resolution values are in " +"spatial reference distance units per pixel." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:122 +msgid "" +"Many caches are built level by level from different sources, similar to " +"many web map tile protocols supported by the GDAL WMS driver. This means " +"that the content of a specific level might be from a different source " +"than an adjacent one, or content for a specific level can be missing " +"altogether. This driver will return opaque black when reading areas which" +" do not have tiles in the cache at a given resolution level, even if data" +" does exist at other levels at the same location." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:131 +msgid "" +"Starting from GDAL 3.8, the driver can automatically expand the paletted " +"images to RGBA. The same cache may contain tiles with different color " +"representations." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:135 +msgid "" +"A cache can exceed the maximum size supported by GDAL, which is " +"INT32_MAX, in either dimension. This driver will generate an error when " +"opening such caches. Removing the **LODInfo** nodes with the highest " +"**LevelID** from the conf.xml file until the raster size drops below " +"INT32_MAX is a possible workaround, but the highest resolution levels " +"will not be read." +msgstr "" + +#: ../../source/drivers/raster/esric.rst:145 +#: ../../source/drivers/raster/gpkg.rst:83 +#: ../../source/drivers/raster/jp2ecw.rst:72 +#: ../../source/drivers/raster/jp2kak.rst:120 +#: ../../source/drivers/raster/jp2openjpeg.rst:86 +#: ../../source/drivers/raster/jpeg.rst:127 +#: ../../source/drivers/raster/jpegxl.rst:55 +#: ../../source/drivers/raster/mbtiles.rst:77 +#: ../../source/drivers/raster/netcdf.rst:277 +#: ../../source/drivers/raster/ngw.rst:125 +#: ../../source/drivers/raster/ogcapi.rst:76 +#: ../../source/drivers/raster/openfilegdb.rst:54 +#: ../../source/drivers/vector/eeda.rst:35 +#: ../../source/drivers/vector/gpkg.rst:194 +#: ../../source/drivers/vector/gpx.rst:93 +#: ../../source/drivers/vector/mvt.rst:163 +#: ../../source/drivers/vector/ngw.rst:169 +#: ../../source/drivers/vector/oapif.rst:80 +#: ../../source/drivers/vector/ods.rst:37 +#: ../../source/drivers/vector/plscenes_data_v1.rst:56 +#: ../../source/drivers/vector/pmtiles.rst:50 +#: ../../source/drivers/vector/tiledb.rst:101 +#: ../../source/drivers/vector/wfs.rst:314 +#: ../../source/drivers/vector/xlsx.rst:45 +msgid "|about-open-options| The following open options are available:" +msgstr "" + +#: ../../source/drivers/raster/esric.rst:163 +msgid "Implemented as :source_file:`frmts/esric/esric_dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:5 +msgid "EXR -- Extended Dynamic Range Image File Format" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:9 +msgid "EXR" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:13 +msgid "" +"OpenEXR is a high dynamic range raster file format. The driver supports " +"reading and writing images in that format." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:16 +msgid "" +"Georeferencing is written as a WKT CRS string and a 3x3 geotransform " +"matrix in EXR header metadata." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:19 +msgid "\"Deep images\" are not supported." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:39 +msgid "``HALF`` corresponds to a IEEE-754 16-bit floating point value." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:40 +msgid "``FLOAT`` corresponds to a IEEE-754 32-bit floating point value." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:41 +msgid "``UINT`` corresponds to a 32-bit unsigned integer value." +msgstr "" + +#: ../../source/drivers/raster/exr.rst:43 +msgid "" +"If not specified, the following GDAL data types will be mapped as " +"following:" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:45 +msgid "``Byte`` ==> HALF" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:46 +msgid "``Int16`` ==> HALF (potentially lossy)" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:47 +msgid "``UInt16`` ==> HALF (potentially lossy)" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:48 +msgid "``Int32`` ==> FLOAT (potentially lossy)" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:49 +msgid "``UInt32`` ==> UINT" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:50 +msgid "``Float32`` ==> FLOAT" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:51 +msgid "``Float64`` ==> FLOAT (generally lossy)" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:-1 +msgid "Supports Create()" +msgstr "" + +#: ../../source/drivers/raster/exr.rst:111 +msgid "" +"With the caveat, that it is only for tiled data, and each tile must be " +"written at most once, and written tiles cannot be read back before " +"dataset closing." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:5 +msgid "FAST -- EOSAT FAST Format" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:7 +msgid "FAST" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:11 +msgid "" +"Supported reading from FAST-L7A format (Landsat TM data) and EOSAT Fast " +"Format Rev. C (IRS-1C/1D data). If you want to read other datasets in " +"this format (SPOT), write to me (Andrey Kiselev, dron@ak4719.spb.edu). " +"You should share data samples with me." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:16 +msgid "" +"Datasets in FAST format represented by several files: one or more " +"administrative headers and one or more files with actual image data in " +"raw format. Administrative files contains different information about " +"scene parameters including filenames of images. You can read files with " +"administrative headers with any text viewer/editor, it is just plain " +"ASCII text." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:23 +msgid "" +"This driver wants administrative file for input. Filenames of images will" +" be extracted and data will be imported, every file will be interpreted " +"as band." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:35 +#: ../../source/drivers/raster/l1b.rst:57 +msgid "Data" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:38 +msgid "FAST-L7A" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:40 +msgid "" +"FAST-L7A consists form several files: big ones with image data and three " +"small files with administrative information. You should give to driver " +"one of the administrative files:" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:44 +msgid "L7fppprrr_rrrYYYYMMDD_HPN.FST: panchromatic band header file with 1 band" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:46 +msgid "L7fppprrr_rrrYYYYMMDD_HRF.FST: VNIR/ SWIR bands header file with 6 bands" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:48 +msgid "L7fppprrr_rrrYYYYMMDD_HTM.FST: thermal bands header file with 2 bands" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:50 +msgid "" +"All raw images corresponded to their administrative files will be " +"imported as GDAL bands." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:53 +msgid "" +"From the \\`\\` `Level 1 Product Output Files Data Format Control Book " +"<http://ltpwww.gsfc.nasa.gov/IAS/pdfs/DFCB_V5_B2_R4.pdf>`__'':" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:56 +msgid "" +"``The file naming convention for the FAST-L7A product files is " +"L7fppprrr_rrrYYYYMMDD_AAA.FST where L7 = Landsat 7 mission f = ETM+ " +"format (1 or 2) (data not pertaining to a specific format defaults to 1)" +" ppp = starting path of the product rrr_rrr = starting and ending rows " +"of the product YYYYMMDD = acquisition date of the image AAA = file " +"type: HPN = panchromatic band header file HRF = VNIR/ SWIR bands header " +"file HTM = thermal bands header file B10 = band 1 B20 = band 2 B30 = band" +" 3 B40 = band 4 B50 = band 5 B61 = band 6L B62 = band 6H B70 = band 7 B80" +" = band 8 FST = FAST file extension``" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:58 +msgid "" +"So you should give to driver one of the " +"``L7fppprrr_rrrYYYYMMDD_HPN.FST``, ``L7fppprrr_rrrYYYYMMDD_HRF.FST`` or " +"``L7fppprrr_rrrYYYYMMDD_HTM.FST`` files." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:63 +msgid "IRS-1C/1D" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:65 +msgid "" +"Fast Format REV. C does not contain band filenames in administrative " +"header. So we should guess band filenames, because different data " +"distributors name their files differently. Several naming schemes " +"hardcoded in GDAL's FAST driver. These are:" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:70 +msgid "``<header>.<ext> <header>.1.<ext> <header>.2.<ext> ...``" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:74 +msgid "``<header>.<ext> band1.<ext> band2.<ext> ...``" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:78 +msgid "``<header>.<ext> band1.dat band2.dat ...``" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:82 +msgid "``<header>.<ext> imagery1.<ext> imagery2.<ext> ...``" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:86 +msgid "``<header>.<ext> imagery1.dat imagery2.dat ...``" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:88 +msgid "" +"in lower or upper case. Header file could be named arbitrarily. This " +"should cover majority of distributors fantasy in naming files. But if you" +" out of luck and your datasets named differently you should rename them " +"manually before importing data with GDAL." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:93 +msgid "" +"GDAL also supports the logic for naming band files for datasets produced " +"by Euromap GmbH for IRS-1C/IRS-1D PAN, LISS3 and WIFS sensors. Their " +"filename logic is explained in the `Euromap Naming Conventions " +"<http://www.euromap.de/download/em_names.pdf>`__ document." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:99 +#: ../../source/drivers/raster/hdf4.rst:171 +#: ../../source/drivers/raster/hdf5.rst:197 +#: ../../source/drivers/raster/l1b.rst:25 +#: ../../source/drivers/raster/mrsid.rst:56 +#: ../../source/drivers/raster/netcdf.rst:245 +msgid "Georeference" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:101 +msgid "" +"All USGS projections should be supported (namely UTM, LCC, PS, PC, TM, " +"OM, SOM). Contact me if you have troubles with proper projection " +"extraction." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:108 +msgid "Calibration coefficients for each band reported as metadata items." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:110 +msgid "**ACQUISITION_DATE**: First scene acquisition date in yyyyddmm format." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:112 +msgid "**SATELLITE**: First scene satellite name." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:113 +msgid "**SENSOR**: First scene sensor name." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:114 +msgid "**BIASn**: Bias value for the channel **n**." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:115 +msgid "**GAINn**: Gain value for the channel **n**." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:120 +msgid "Implemented as :source_file:`frmts/raw/fastdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/fast.rst:122 +msgid "" +"Landsat FAST L7A format description available from " +"http://ltpwww.gsfc.nasa.gov/IAS/htmls/l7_review.html (see `ESDIS Level 1 " +"Product Generation System (LPGS) Output Files DFCB, Vol. 5, Book 2 " +"<http://ltpwww.gsfc.nasa.gov/IAS/pdfs/DFCB_V5_B2_R4.pdf>`__)" +msgstr "" + +#: ../../source/drivers/raster/fast.rst:127 +msgid "" +"EOSAT Fast Format REV. C description available from " +"http://www.euromap.de/docs/doc_001.html" +msgstr "" + +#: ../../source/drivers/raster/fit.rst:5 +msgid "FIT -- FIT" +msgstr "" + +#: ../../source/drivers/raster/fit.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/fit/fitdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:5 +msgid "FITS -- Flexible Image Transport System" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:7 +msgid "FITS" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:11 +msgid "" +"FITS is a format used mainly by astronomers, but it is a relatively " +"simple format that supports arbitrary image types and multi-spectral " +"images, and so has found its way into GDAL. FITS support is implemented " +"in terms of the standard `CFITSIO library " +"<http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html>`__, which" +" you must have on your system in order for FITS support to be enabled " +"(see :ref:`notes on CFITSIO linking <notes-on-cfitsio-linking>`). Both " +"reading and writing of FITS files is supported." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:20 +msgid "" +"Starting from version 3.0 georeferencing system support is implemented " +"via the conversion of WCS (World Coordinate System) keywords. Only " +"Latitude - Longitude systems (see the `FITS standard document " +"<https://fits.gsfc.nasa.gov/standard40/fits_standard40aa-" +"le.pdf#subsection.8.3>`_) have been implemented, those for which remote " +"sensing processing is commonly used. As 3D Datum information is missing " +"in FITS/WCS standard, Radii and target bodies are translated using the " +"planetary extension proposed `here " +"<https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2018EA000388>`_." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:30 +msgid "" +"Non-standard header keywords that are present in the FITS file will be " +"copied to the dataset's metadata when the file is opened, for access via " +"GDAL methods. Similarly, non-standard header keywords that the user " +"defines in the dataset's metadata will be written to the FITS file when " +"the GDAL handle is closed." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:36 +msgid "" +"Note to those familiar with the CFITSIO library: The automatic rescaling " +"of data values, triggered by the presence of the BSCALE and BZERO header " +"keywords in a FITS file, is disabled in GDAL < v3.0. Those header " +"keywords are accessible and updatable via dataset metadata, in the same " +"was as any other header keywords, but they do not affect reading/writing " +"of data values from/to the file. Starting from version 3.0 BZERO and " +"BSCALE keywords are managed via standard " +":cpp:func:`GDALRasterBand::GetOffset` / " +":cpp:func:`GDALRasterBand::SetOffset` and " +":cpp:func:`GDALRasterBand::GetScale` / " +":cpp:func:`GDALRasterBand::SetScale` GDAL functions and no more referred " +"as metadata." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:47 +msgid "Multiple image support" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:49 +msgid "" +"Starting with GDAL 3.2, Multi-Extension FITS (MEF) files that contain one" +" or more extensions following the primary HDU are supported. When more " +"than 2 image HDUs are found, they are reported as subdatasets." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:53 +msgid "" +"The connection string for a given subdataset/HDU is " +"``FITS:\"filename.fits\":hdu_number``" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:56 +msgid "Binary table support" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:58 +msgid "" +"Starting with GDAL 3.2, binary tables will be exposed as vector layers " +"(update and creation support from GDAL 3.2.1)." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:61 +msgid "The FITS data types are mapped to OGR data types as the following:" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:63 +msgid "Data types" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:66 +msgid "TFORM value" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:67 +msgid "TSCAL, TOFFSET value" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:68 +msgid "Occurrence count" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:69 +#: ../../source/drivers/vector/netcdf.rst:81 +#: ../../source/drivers/vector/netcdf.rst:120 +msgid "OGR field type" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:70 +msgid "OGR field subtype" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:71 +#: ../../source/drivers/raster/fits.rst:76 +msgid "'L' (Logical)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:72 +#: ../../source/drivers/raster/fits.rst:77 +#: ../../source/drivers/raster/fits.rst:82 +#: ../../source/drivers/raster/fits.rst:177 +#: ../../source/drivers/raster/fits.rst:182 +msgid "ignored" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:74 +#: ../../source/drivers/raster/fits.rst:84 +#: ../../source/drivers/raster/fits.rst:89 +#: ../../source/drivers/raster/fits.rst:99 +#: ../../source/drivers/raster/fits.rst:104 +#: ../../source/drivers/raster/fits.rst:129 +#: ../../source/drivers/raster/fits.rst:134 +#: ../../source/drivers/vector/ngw.rst:141 +msgid "OFTInteger" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:75 +#: ../../source/drivers/raster/fits.rst:80 +msgid "OFSTBoolean" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:78 +#: ../../source/drivers/raster/fits.rst:93 +#: ../../source/drivers/raster/fits.rst:123 +#: ../../source/drivers/raster/fits.rst:153 +#: ../../source/drivers/raster/fits.rst:168 +#: ../../source/drivers/raster/fits.rst:173 +#: ../../source/drivers/raster/fits.rst:198 +#: ../../source/drivers/raster/fits.rst:203 +#: ../../source/drivers/raster/fits.rst:213 +#: ../../source/drivers/raster/fits.rst:223 +#: ../../source/drivers/raster/fits.rst:233 +msgid "> 1" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:79 +#: ../../source/drivers/raster/fits.rst:94 +#: ../../source/drivers/raster/fits.rst:114 +#: ../../source/drivers/raster/fits.rst:119 +#: ../../source/drivers/raster/fits.rst:144 +#: ../../source/drivers/raster/fits.rst:149 +msgid "OFTIntegerList" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:81 +msgid "'X' (bit)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:83 +msgid "each bit mapped to a OGR field" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:85 +#: ../../source/drivers/raster/fits.rst:90 +#: ../../source/drivers/raster/fits.rst:95 +#: ../../source/drivers/raster/fits.rst:105 +#: ../../source/drivers/raster/fits.rst:110 +#: ../../source/drivers/raster/fits.rst:120 +#: ../../source/drivers/raster/fits.rst:125 +#: ../../source/drivers/raster/fits.rst:130 +#: ../../source/drivers/raster/fits.rst:135 +#: ../../source/drivers/raster/fits.rst:140 +#: ../../source/drivers/raster/fits.rst:145 +#: ../../source/drivers/raster/fits.rst:150 +#: ../../source/drivers/raster/fits.rst:155 +#: ../../source/drivers/raster/fits.rst:160 +#: ../../source/drivers/raster/fits.rst:165 +#: ../../source/drivers/raster/fits.rst:170 +#: ../../source/drivers/raster/fits.rst:175 +#: ../../source/drivers/raster/fits.rst:180 +#: ../../source/drivers/raster/fits.rst:185 +#: ../../source/drivers/raster/fits.rst:195 +#: ../../source/drivers/raster/fits.rst:205 +#: ../../source/drivers/raster/fits.rst:210 +#: ../../source/drivers/raster/fits.rst:215 +#: ../../source/drivers/raster/fits.rst:220 +#: ../../source/drivers/raster/fits.rst:225 +#: ../../source/drivers/raster/fits.rst:230 +#: ../../source/drivers/raster/fits.rst:235 +msgid "OFSTNone" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:86 +#: ../../source/drivers/raster/fits.rst:91 +msgid "'B' (unsigned byte)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:87 +#: ../../source/drivers/raster/fits.rst:92 +msgid "1, 0 (unsigned byte) or 1, -128 (signed byte)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:96 +#: ../../source/drivers/raster/fits.rst:106 +#: ../../source/drivers/raster/fits.rst:121 +msgid "'I' (16 bit signed integer)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:97 +#: ../../source/drivers/raster/fits.rst:112 +#: ../../source/drivers/raster/fits.rst:127 +#: ../../source/drivers/raster/fits.rst:142 +#: ../../source/drivers/raster/fits.rst:157 +#: ../../source/drivers/raster/fits.rst:167 +#: ../../source/drivers/raster/fits.rst:187 +#: ../../source/drivers/raster/fits.rst:197 +msgid "1, 0" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:100 +#: ../../source/drivers/raster/fits.rst:115 +msgid "OFSTInt16" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:101 +#: ../../source/drivers/raster/fits.rst:116 +msgid "'I' (16 bit integer, interpreted as unsigned)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:102 +#: ../../source/drivers/raster/fits.rst:117 +msgid "1, 32768" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:107 +msgid "other than (1,0) and (1,32768)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:109 +#: ../../source/drivers/raster/fits.rst:139 +#: ../../source/drivers/raster/fits.rst:164 +#: ../../source/drivers/raster/fits.rst:189 +#: ../../source/drivers/raster/fits.rst:194 +#: ../../source/drivers/raster/fits.rst:209 +#: ../../source/drivers/vector/ngw.rst:143 +msgid "OFTReal" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:111 +msgid "'I' (16 bit integer)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:113 +#: ../../source/drivers/raster/fits.rst:118 +#: ../../source/drivers/raster/fits.rst:143 +#: ../../source/drivers/raster/fits.rst:148 +msgid ">1" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:122 +msgid "other than (1, 0) and (1, 32768)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:124 +#: ../../source/drivers/raster/fits.rst:154 +#: ../../source/drivers/raster/fits.rst:174 +#: ../../source/drivers/raster/fits.rst:199 +#: ../../source/drivers/raster/fits.rst:204 +#: ../../source/drivers/raster/fits.rst:214 +msgid "OFTRealList" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:126 +#: ../../source/drivers/raster/fits.rst:136 +#: ../../source/drivers/raster/fits.rst:151 +msgid "'J' (32 bit signed integer)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:131 +#: ../../source/drivers/raster/fits.rst:146 +msgid "'J' (32 bit integer, interpreted as unsigned)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:132 +#: ../../source/drivers/raster/fits.rst:147 +msgid "1, 2147483648" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:137 +#: ../../source/drivers/raster/fits.rst:152 +msgid "other than (1, 0) and (1, 2147483648)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:141 +msgid "'J' (32 bit integer)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:156 +#: ../../source/drivers/raster/fits.rst:161 +#: ../../source/drivers/raster/fits.rst:166 +#: ../../source/drivers/raster/fits.rst:171 +msgid "'K' (64 bit signed integer)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:159 +#: ../../source/drivers/raster/fits.rst:169 +#: ../../source/drivers/vector/ngw.rst:142 +msgid "OFTInteger64" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:162 +#: ../../source/drivers/raster/fits.rst:172 +#: ../../source/drivers/raster/fits.rst:192 +#: ../../source/drivers/raster/fits.rst:202 +msgid "other than (1, 0)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:176 +#: ../../source/drivers/raster/fits.rst:181 +msgid "'A' (character)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:178 +msgid "if TFORM='Axxx' and no TDIM header" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:179 +#: ../../source/drivers/vector/ngw.rst:144 +msgid "OFTString" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:183 +msgid "TDIM for 2D field, or variable length ('PA')" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:184 +msgid "OFTStringList" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:186 +#: ../../source/drivers/raster/fits.rst:191 +#: ../../source/drivers/raster/fits.rst:196 +#: ../../source/drivers/raster/fits.rst:201 +msgid "'E' (single precision floating point)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:190 +#: ../../source/drivers/raster/fits.rst:200 +msgid "OFSTFloat32" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:206 +#: ../../source/drivers/raster/fits.rst:211 +msgid "'D' (double precision floating point)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:207 +#: ../../source/drivers/raster/fits.rst:212 +#: ../../source/drivers/raster/fits.rst:217 +#: ../../source/drivers/raster/fits.rst:222 +#: ../../source/drivers/raster/fits.rst:227 +#: ../../source/drivers/raster/fits.rst:232 +msgid "any" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:216 +#: ../../source/drivers/raster/fits.rst:221 +msgid "'C' (single precision complex)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:219 +#: ../../source/drivers/raster/fits.rst:229 +msgid "OFTString whose value is of the form \"x + yj\"" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:224 +#: ../../source/drivers/raster/fits.rst:234 +msgid "OFTStringList whose values are of the form \"x + yj\"" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:226 +#: ../../source/drivers/raster/fits.rst:231 +msgid "'M' (double precision complex)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:237 +msgid "" +"Fields with a repeat count > 1 expressing fixed size arrays, or fields " +"using array descriptors 'P' and 'Q' for variable length arrays are mapped" +" to OGR OFTxxxxxList data types. The potential 2D structure of such field" +" has no direct equivalence in OGR, so OGR will expose a linear structure." +" For fixed size arrays, the user can retrieve the value of the TDIMxx " +"header in the layer metadata to recover the dimensionality of the field." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:244 +msgid "" +"Fields that have TSCAL and/or TZERO headers are automatically scaled and " +"offset to the physical value (only applies to numeric data types)" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:247 +msgid "" +"TNULL headers are used for integer numeric data types and for a single-" +"occurence field to set a OGR field to NULL." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:251 +#: ../../source/drivers/vector/amigocloud.rst:106 +#: ../../source/drivers/vector/arrow.rst:58 +#: ../../source/drivers/vector/carto.rst:138 +#: ../../source/drivers/vector/dgnv8.rst:204 +#: ../../source/drivers/vector/elasticsearch.rst:447 +#: ../../source/drivers/vector/geojson.rst:279 +#: ../../source/drivers/vector/geojsonseq.rst:64 +#: ../../source/drivers/vector/gpkg.rst:343 +#: ../../source/drivers/vector/gpx.rst:229 +#: ../../source/drivers/vector/jsonfg.rst:130 +#: ../../source/drivers/vector/libkml.rst:283 +#: ../../source/drivers/vector/memory.rst:46 +#: ../../source/drivers/vector/miramon.rst:294 +#: ../../source/drivers/vector/mongodbv3.rst:234 +#: ../../source/drivers/vector/mvt.rst:400 +#: ../../source/drivers/vector/netcdf.rst:319 +#: ../../source/drivers/vector/ngw.rst:256 +#: ../../source/drivers/vector/parquet.rst:62 +#: ../../source/drivers/vector/pmtiles.rst:220 +#: ../../source/drivers/vector/selafin.rst:349 +#: ../../source/drivers/vector/shapefile.rst:346 +#: ../../source/drivers/vector/sqlite.rst:323 +#: ../../source/drivers/vector/tiledb.rst:160 +msgid "Layer creation options" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:253 +#: ../../source/drivers/raster/mbtiles.rst:474 +#: ../../source/drivers/vector/amigocloud.rst:108 +#: ../../source/drivers/vector/gpkg.rst:345 +#: ../../source/drivers/vector/memory.rst:48 +#: ../../source/drivers/vector/ngw.rst:258 +#: ../../source/drivers/vector/tiledb.rst:162 +#: ../../source/drivers/vector/vdv.rst:59 +msgid "" +"|about-layer-creation-options| The following layer creation options are " +"available:" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:277 +msgid "" +"When using ogr2ogr or :cpp:func:`GDALVectorTranslate` with a FITS source," +" the FITS header will be taken into account, in particular to help to " +"determine the FITS data type of target columns." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:284 +msgid "Listing subdatasets in a MEF .fits:" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:307 +msgid "Opening a given raster HDU:" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:326 +msgid "Listing potential binary tables in a FITS file:" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:333 +msgid "Converting a GeoPackage layer into a FITS binary table:" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:342 +msgid "Other" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:344 +msgid "NOTE: Implemented as :source_file:`frmts/fits/fitsdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:349 +msgid "Notes on CFITSIO linking in GDAL" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:353 +msgid "From source" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:354 +msgid "" +"Install CFITSIO headers from your distro (eg, cfitsio-devel on Fedora; " +"libcfitsio-dev on Debian-Ubuntu), then compile GDAL as usual. CFITSIO " +"will be automatically detected and linked." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:357 +msgid "From distros" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:358 +msgid "" +"On Fedora/CentOS install CFITSIO then GDAL with dnf (yum): cfitsio is " +"automatically linked." +msgstr "" + +#: ../../source/drivers/raster/fits.rst:361 +msgid "MacOSX" +msgstr "" + +#: ../../source/drivers/raster/fits.rst:362 +msgid "" +"The last versions of the MacOSX packages are not linked against CFITSIO. " +"Install CFITSIO as described in the `official documentation " +"<https://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio_macosx.html>`__." +msgstr "" + +#: ../../source/drivers/raster/genbin.rst:5 +msgid "GenBin -- Generic Binary (.hdr labelled)" +msgstr "" + +#: ../../source/drivers/raster/genbin.rst:7 +msgid "GenBin" +msgstr "" + +#: ../../source/drivers/raster/genbin.rst:11 +msgid "" +"This driver supporting reading \"Generic Binary\" files labelled with a " +".hdr file, but distinct from the more common ESRI labelled .hdr format " +"(EHdr driver). The origin of this format is not entirely clear. The .hdr " +"files supported by this driver are look something like this:" +msgstr "" + +#: ../../source/drivers/raster/genbin.rst:25 +msgid "" +"Pixel data types of U8, U16, S16, F32, F64, and U1 (bit) are supported. " +"Georeferencing and coordinate system information should be supported when" +" provided." +msgstr "" + +#: ../../source/drivers/raster/genbin.rst:29 +msgid "NOTE: Implemented as :source_file:`frmts/raw/genbindataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:7 +msgid "GeoRaster" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:11 +msgid "" +"This driver supports reading and writing raster data in Oracle Spatial " +"GeoRaster format (10g or later). The Oracle Spatial GeoRaster driver is " +"optionally built as a GDAL plugin, but it requires Oracle client " +"libraries." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:16 +msgid "When opening a GeoRaster, its name should be specified in the form:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:18 +msgid "georaster:<user>{,/}<pwd>{,@}[db],[schema.][table],[column],[where]" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:19 +msgid "georaster:<user>{,/}<pwd>{,@}[db],<rdt>,<rid>" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:21 +msgid "Where:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:23 +msgid "user   = Oracle server user's name login" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:24 +msgid "pwd    = user password" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:25 +msgid "db     = Oracle server identification (database name)" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:26 +msgid "schema = name of a schema" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:28 +msgid "table  = name of a GeoRaster table (table that contains GeoRaster columns)" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:29 +msgid "column = name of a column data type MDSYS.SDO_GEORASTER" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:31 +msgid "where  = a simple where clause to identify one or multiples GeoRaster(s)" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:32 +msgid "rdt    = name of a raster data table" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:33 +msgid "rid    = numeric identification of one GeoRaster" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:35 +#: ../../source/drivers/raster/mbtiles.rst:528 +msgid "Examples:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:37 +msgid "geor:scott,tiger,demodb,table,column,id=1" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:38 +msgid "geor:scott,tiger,demodb,table,column,\"id = 1\"" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:39 +msgid "\"georaster:scott/tiger@demodb,table,column,gain>10\"" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:40 +msgid "\"georaster:scott/tiger@demodb,table,column,city='Brasilia'\"" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:41 +msgid "georaster:scott,tiger,,rdt_10$,10" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:42 +msgid "geor:scott/tiger,,rdt_10$,10" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:44 +msgid "Note: do note use space around the field values and the commas." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:46 +msgid "" +"Note: like in the last two examples, the database name field could be " +"left empty (\",,\") and the TNSNAME will be used." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:49 +msgid "" +"Note: If  the query results in more than one GeoRaster it will be treated" +" as a GDAL metadata's list of sub-datasets (see below)" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:64 +msgid "Browsing the database for GeoRasters" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:66 +msgid "" +"By providing some basic information the GeoRaster driver is capable of " +"listing the existing rasters stored on the server:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:69 +msgid "" +"To list all the GeoRaster table on the server that belongs to that user " +"name and database:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:76 +msgid "To list all the GeoRaster type columns that exist in that table:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:82 +msgid "That will list all the GeoRaster objects stored in that table." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:88 +msgid "" +"That will list all the GeoRaster existing on that table according to a " +"Where clause." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:96 +msgid "" +"Note that the result of those queries are returned as GDAL metadata sub-" +"datasets, e.g.:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:258 +msgid "" +"When this value is set to FALSE, then the bin function to use is the one " +"generated dynamically as previously described." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:271 +msgid "A valid function defined in the GeoRaster metadata." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:272 +msgid "The same bin function generated when :co:`GENSTATS_USEBIN` is FALSE." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:284 +msgid "" +"A NODATA value is used for cells whose values are either not known or " +"meaningless" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:368 +msgid "Importing GeoRaster" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:370 +msgid "" +"During the process of importing raster into a GeoRaster object it is " +"possible to give the driver a simple SQL table definition and also a SQL " +"insert/values clause to inform the driver about the table to be created " +"and the values to be added to the newly created row. The following " +"example does that:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:384 +msgid "" +"Note that the create option DESCRIPTION requires to inform table name (in" +" bold). And column name (underlined) should match the description:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:393 +msgid "" +"If the table \"landsat\" exist, the option \"DESCRIPTION\" is ignored. " +"The driver can only update one GeoRaster column per run of " +"gdal_translate. Oracle create default names and values for RDT and RID " +"during the initialization of the SDO_GEORASTER object but user are also " +"able to specify a name and value of their choice." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:404 +msgid "" +"If no information is given about where to store the raster the driver " +"will create (if doesn't exist already) a default table named GDAL_IMPORT " +"with just one GeoRaster column named RASTER and a table GDAL_RDT as the " +"RDT, the RID will be given automatically by the server, example:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:414 +msgid "Exporting GeoRaster" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:416 +msgid "A GeoRaster can be identified by a Where clause or by a pair of RDT & RID:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:424 +msgid "Cross schema access" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:426 +msgid "" +"As long as the user was granted full access the GeoRaster table and the " +"Raster Data Table, e.g.:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:435 +msgid "" +"It is possible to an user access to extract and load GeoRaster from " +"another user/schema by informing the schema name as showed here:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:438 +msgid "Browsing:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:446 +msgid "Extracting:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:453 +msgid "" +"Note: On the above example that accessing by RDT/RID doesn't need schame " +"name as long as the users is granted full access to both tables." +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:457 +msgid "Loading:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:466 +msgid "General use of GeoRaster" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:468 +msgid "" +"GeoRaster can be used in any GDAL command line tool with all the " +"available options. Like a image subset extraction or re-project:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:478 +msgid "" +"Two different GeoRaster can be used as input and output on the same " +"operation:" +msgstr "" + +#: ../../source/drivers/raster/georaster.rst:485 +msgid "" +"Applications that use GDAL can theoretically read and write from " +"GeoRaster just like any other format but most of then are more inclined " +"to try to access files on the file system so one alternative is to create" +" VRT to represent the GeoRaster description, e.g.:" +msgstr "" + +#: ../../source/drivers/raster/gff.rst:5 +msgid "GFF -- Sandia National Laboratories GSAT File Format" +msgstr "" + +#: ../../source/drivers/raster/gff.rst:7 +msgid "GFF" +msgstr "" + +#: ../../source/drivers/raster/gff.rst:11 +msgid "" +"This read-only GDAL driver is designed to provide access to processed " +"data from Sandia National Laboratories' various experimental sensors. The" +" format is essentially an arbitrary length header containing instrument " +"configuration and performance parameters along with a binary matrix of " +"16- or 32-bit complex or byte real data." +msgstr "" + +#: ../../source/drivers/raster/gff.rst:17 +msgid "" +"The GFF format was implemented based on the Matlab code provided by " +"Sandia to read the data. The driver supports all types of data (16-bit or" +" 32-bit complex, real bytes) theoretically, however due to a lack of data" +" only 32-bit complex data has been tested." +msgstr "" + +#: ../../source/drivers/raster/gff.rst:22 +msgid "" +"Sandia provides some sample data at http://www.sandia.gov/radar/complex-" +"data/." +msgstr "" + +#: ../../source/drivers/raster/gff.rst:25 +msgid "The extension for GFF formats is .gff." +msgstr "" + +#: ../../source/drivers/raster/gff.rst:27 +msgid "NOTE: Implemented as :source_file:`frmts/gff/gff_dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:5 +msgid "GIF -- Graphics Interchange Format" +msgstr "" + +#: ../../source/drivers/raster/gif.rst:7 +msgid "GIF" +msgstr "" + +#: ../../source/drivers/raster/gif.rst:11 +msgid "" +"GDAL supports reading and writing of normal, and interlaced GIF files. " +"Gif files always appear as having one colormapped eight bit band. GIF " +"files have no support for georeferencing." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:15 +msgid "" +"A GIF image with transparency will have that entry marked as having an " +"alpha value of 0.0 (transparent). Also, the transparent value will be " +"returned as the NoData value for the band." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:19 +msgid "" +"If an ESRI world file exists with the .gfw, .gifw or .wld extension, it " +"will be read and used to establish the geotransform for the image." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:22 +#: ../../source/drivers/raster/jpeg.rst:60 +#: ../../source/drivers/raster/pdf.rst:48 +#: ../../source/drivers/raster/png.rst:36 +#: ../../source/drivers/raster/webp.rst:28 +msgid "" +"XMP metadata can be extracted from the file, and will be stored as XML " +"raw content in the xml:XMP metadata domain." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:35 +msgid "" +"GIF files can only be created as 1 8bit band using the \"CreateCopy\" " +"mechanism. If written from a file that is not colormapped, a default " +"greyscale colormap is generated. Transparent GIFs are not currently " +"supported on creation." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:55 +msgid "" +"GDAL's internal GIF support is implemented based on source from the " +"giflib 4.1.6 library (written by Gershon Elbor, Eric Raymond and Toshio " +"Kuratomi), hence generating LZW compressed GIF." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:59 +msgid "" +"The driver was written with the financial support of the `DM Solutions " +"Group <http://www.dmsolutions.ca/>`__, and `CIET International " +"<http://www.ciet.org/>`__." +msgstr "" + +#: ../../source/drivers/raster/gif.rst:66 +msgid "`giflib Home Page <http://sourceforge.net/projects/giflib/>`__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:5 +msgid "GPKG -- GeoPackage raster" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:7 +#: ../../source/drivers/vector/gpkg.rst:6 +msgid "GPKG" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:11 +msgid "" +"This driver implements full read/creation/update of tables containing " +"raster tiles in the `OGC GeoPackage format standard " +"<http://www.geopackage.org/spec/>`__. The GeoPackage standard uses a " +"SQLite database file as a generic container, and the standard defines:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:17 +msgid "" +"Expected metadata tables (``gpkg_contents``, ``gpkg_spatial_ref_sys``, " +"``gpkg_tile_matrix``, ``gpkg_tile_matrix_set``, ...)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:20 +msgid "" +"Tile format encoding (PNG and JPEG for base specification, WebP as " +"extension) and tiling conventions" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:22 +msgid "Naming and conventions for extensions" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:24 +#: ../../source/drivers/vector/gpkg.rst:24 +msgid "" +"This driver reads and writes SQLite files from the file system, so it " +"must be run by a user with read/write access to the files it is working " +"with." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:28 +msgid "" +"The driver can also handle GeoPackage vectors. See :ref:`GeoPackage " +"vector <vector.gpkg>` documentation page" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:31 +msgid "Various kind of input datasets can be converted to GeoPackage raster :" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:33 +msgid "Single band grey level" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:34 +msgid "Single band with R,G,B or R,G,B,A color table" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:35 +msgid "Two bands: first band with grey level, second band with alpha channel" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:36 +msgid "Three bands: Red, Green, Blue" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:37 +msgid "Four band: Red, Green, Blue, Alpha" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:39 +msgid "GeoPackage rasters only support Byte data type." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:41 +msgid "" +"All raster extensions standardized by the GeoPackage specification are " +"supported in read and creation :" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:44 +msgid "" +"*gpkg_webp*: when storing WebP tiles, provided that GDAL is compiled " +"against libwebp." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:46 +msgid "" +"*gpkg_zoom_other*: when resolution of consecutive zoom levels does not " +"vary with a factor of 2." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:61 +#: ../../source/drivers/raster/mbtiles.rst:75 +#: ../../source/drivers/vector/mvt.rst:161 +#: ../../source/drivers/vector/pmtiles.rst:48 +msgid "Opening options" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:63 +msgid "" +"By default, the driver will expose a GeoPackage dataset as a four band " +"(Red,Green, Blue,Alpha) dataset, which gives the maximum compatibility " +"with the various encodings of tiles that can be stored. It is possible to" +" specify an explicit number of bands with the BAND_COUNT opening option. " +"Starting with GDAL 3.6, a special metadata item is written when creating " +"a GeoPackage raster with GDAL (when using the default CUSTOM tiling " +"scheme), and it is used on reading as the default number of bands." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:72 +msgid "" +"The driver will use the geographic/projected extent indicated in the " +"`gpkg_contents <http://www.geopackage.org/spec/#_contents>`__ table, and " +"do necessary clipping, if needed, to respect that extent. However that " +"information being optional, if omitted, the driver will use the extent " +"provided by the `gpkg_tile_matrix_set " +"<http://www.geopackage.org/spec/#_tile_matrix_set>`__, which covers the " +"extent at all zoom levels. The user can also specify the " +"USE_TILE_EXTENT=YES open option to use the actual extent of tiles at the " +"maximum zoom level. Or it can specify any of MINX/MINY/MAXX/MAXY to have " +"a custom extent." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:169 +msgid "" +"Note: open options are typically specified with \"-oo name=value\" syntax" +" in most GDAL utilities, or with the GDALOpenEx() API call." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:175 +msgid "" +"Depending of the number of bands of the input dataset and the tile format" +" selected, the driver will do the necessary conversions to be compatible " +"with the tile format." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:179 +msgid "" +"To add several tile tables to a GeoPackage dataset (seen as GDAL " +"subdatasets), or to add a tile table to an existing vector-only " +"GeoPackage, the generic APPEND_SUBDATASET=YES creation option must be " +"provided." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:184 +#: ../../source/drivers/raster/mbtiles.rst:189 +msgid "" +"Fully transparent tiles will not be written to the database, as allowed " +"by the format." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:187 +msgid "" +"The driver implements the Create() and IWriteBlock() methods, so that " +"arbitrary writing of raster blocks is possible, enabling the direct use " +"of GeoPackage as the output dataset of utilities such as gdalwarp." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:191 +#: ../../source/drivers/raster/mbtiles.rst:196 +msgid "" +"On creation, raster blocks can be written only if the geotransformation " +"matrix has been set with SetGeoTransform() This is effectively needed to " +"determine the zoom level of the full resolution dataset based on the " +"pixel resolution, dataset and tile dimensions." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:196 +msgid "" +"Technical/implementation note: when a dataset is opened with a non-" +"default area of interest (i.e. use of MINX,MINY,MAXX,MAXY or " +"USE_TILE_EXTENT open option), or when creating/ opening a dataset with a " +"non-custom tiling scheme, it is possible that GDAL blocks do not exactly " +"match a single GeoPackage tile. In which case, each GDAL block will " +"overlap four GeoPackage tiles. This is easily handled on the read side, " +"but on creation/update side, such configuration could cause numerous " +"decompression/ recompression of tiles to be done, which might cause " +"unnecessary quality loss when using lossy compression (JPEG, WebP). To " +"avoid that, the driver will create a temporary database next to the main " +"GeoPackage file to store partial GeoPackage tiles in a lossless (and " +"uncompressed) way. Once a tile has received data for its four quadrants " +"and for all the bands (or the dataset is closed or explicitly flushed " +"with FlushCache()), those uncompressed tiles are definitely transferred " +"to the GeoPackage file with the appropriate compression. All of this is " +"transparent to the user of GDAL API/utilities" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:213 +#: ../../source/drivers/vector/gpkg.rst:263 +msgid "" +"The driver updates the GeoPackage ``last_change`` timestamp when the file" +" is created or modified. If consistent binary output is required for " +"reproducibility, the timestamp can be forced to a specific value by " +"setting the :config:`OGR_CURRENT_DATE` global configuration option. When " +"setting the option, take care to meet the specific time format " +"requirement of the GeoPackage standard, e.g. `for version 1.2 " +"<https://www.geopackage.org/spec120/#r15>`__." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:225 +#: ../../source/drivers/raster/mbtiles.rst:216 +msgid "Tile formats" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:228 +msgid "Tiled rasters" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:230 +msgid "This section only applies for raster of Byte data type." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:232 +msgid "" +"GeoPackage can store tiles in different formats, PNG and/or JPEG for the " +"baseline specification, and WebP for extended GeoPackage. Support for " +"those tile formats depend if the underlying drivers are available in " +"GDAL, which is generally the case for PNG and JPEG, but not necessarily " +"for WebP since it requires GDAL to be compiled against the optional " +"libwebp." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:239 +msgid "" +"By default, GDAL will use a mix of PNG and JPEG tiles (PNG_JPEG tile " +"format, or AUTO). PNG tiles will be used to store tiles that are not " +"completely opaque, either because input dataset has an alpha channel with" +" non fully opaque content, or because tiles are partial due to clipping " +"at the right or bottom edges of the raster, or when a dataset is opened " +"with a non-default area of interest, or with a non-custom tiling scheme. " +"On the contrary, for fully opaque tiles, JPEG format will be used. " +"Starting with GDAL 3.6, if the raster has only one band, the default is " +"PNG." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:249 +msgid "" +"It is possible to select one unique tile format by setting the " +"creation/open option TILE_FORMAT to one of PNG, JPEG or WEBP. When using " +"JPEG, the alpha channel will not be stored. When using WebP, the " +"`gpkg_webp <http://www.geopackage.org/spec/#extension_tiles_webp>`__ " +"extension will be registered. The lossy compression of WebP is used. Note" +" that a recent enough libwebp (>=0.1.4) must be used to support alpha " +"channel in WebP tiles." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:257 +#: ../../source/drivers/raster/mbtiles.rst:226 +msgid "" +"PNG8 can be selected to use 8-bit PNG with a color table up to 256 " +"colors. On creation, an optimized color table is computed for each tile. " +"The DITHER option can be set to YES to use Floyd/Steinberg dithering " +"algorithm, which spreads the quantization error on neighbouring pixels " +"for better rendering (note however than when zooming in, this can cause " +"non desirable visual artifacts). Setting it to YES will generally cause " +"less effective compression. Note that at that time, such an 8-bit PNG " +"formulation is only used for fully opaque tiles, as the median-cut " +"algorithm currently implemented to compute the optimal color table does " +"not support alpha channel (even if PNG8 format would potentially allow " +"color table with transparency). So when selecting PNG8, non fully opaque " +"tiles will be stored as 32-bit PNG." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:271 +msgid "Tiled gridded coverage data" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:273 +msgid "" +"Since GDAL 2.3, `tiled gridded coverage data " +"<http://docs.opengeospatial.org/is/17-066r1/17-066r1.html#27>`__ can be " +"stored using PNG unsigned 16bit tiles (with potential offset and scaling " +"so as to be able to represent floating point data) or TIFF 32-bit " +"floating-point LZW compressed tiles." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:279 +msgid "" +"When converting a GDAL Int16 or UInt16 dataset, PNG tiles will be used. " +"When converting a GDAL Float32 dataset, TIFF tiles will be used by " +"default, unless PNG is explicitly selected, in which case scaling and " +"offsetting will be automatically computed for each tile." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:286 +msgid "" +"The `tiled gridded extension " +"<http://www.geopackage.org/spec/#extension_tiled_gridded_elevation_data>`__" +" initially implemented in GDAL 2.2 was not officially adopted and had " +"been later reworked by OGC. The adopted `tiled gridded coverage data " +"<http://docs.opengeospatial.org/is/17-066r1/17-066r1.html#27>`__ has a " +"few differences that will make GDAL 2.2 datasets not be compliant with " +"the final extension. GDAL 2.3 can open those GDAL 2.2-generated files." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:298 +msgid "Tiling schemes" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:300 +msgid "" +"By default, conversion to GeoPackage will create a custom tiling scheme, " +"such that the input dataset can be losslessly converted, both at the " +"pixel and georeferencing level (if using a lossless tile format such as " +"PNG). That tiling scheme is such that its origin (*min_x*, *max_y*) in " +"the `gpkg_tile_matrix_set " +"<http://www.geopackage.org/spec/#_tile_matrix_set>`__ table perfectly " +"matches the top left corner of the dataset, and the selected resolution " +"(*pixel_x_size*, *pixel_y_size*) at the computed maximum zoom_level of " +"the `gpkg_tile_matrix <http://www.geopackage.org/spec/#_tile_matrix>`__ " +"table will match the pixel width and height of the raster." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:312 +msgid "" +"However to ease interoperability with other implementations, and enable " +"use of GeoPackage with tile servicing software, it is possible to select " +"a predefined tiling scheme that has world coverage. The available tiling " +"schemes are :" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:317 +msgid "" +"*GoogleMapsCompatible*, as described in WMTS 1.0 specification, Annex " +"E.4. That tiling schemes consists of a single 256x256 tile at its zoom " +"level 0, in EPSG:3857 CRS, with extent in easting and northing in the " +"range [-20037508.34,20037508.34]." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:321 +msgid "" +"*InspireCRS84Quad*, as described in `Inspire View Services " +"<http://inspire.ec.europa.eu/documents/Network_Services/TechnicalGuidance_ViewServices_v3.0.pdf>`__." +" That tiling schemes consists of two 256x256 tiles at its zoom level 0, " +"in EPSG:4326 CRS, with extent in longitude in the range [-180,180] and in" +" latitude in the range [-90,90]." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:326 +msgid "" +"*PseudoTMS_GlobalGeodetic*, based on the `global-geodetic " +"<http://wiki.osgeo.org/wiki/Tile_Map_Service_Specification#global-" +"geodetic>`__ profile of OSGeo TMS (Tile Map Service) specification. This " +"has exactly the same definition as *InspireCRS84Quad* tiling scheme. Note" +" however that full interoperability with TMS is not possible due to the " +"origin of numbering of tiles being the top left corner in GeoPackage " +"(consistently with WMTS convention), whereas TMS uses the bottom left " +"corner as origin." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:334 +msgid "" +"*PseudoTMS_GlobalMercator*, based on the `global-mercator " +"<http://wiki.osgeo.org/wiki/Tile_Map_Service_Specification#global-" +"mercator>`__ profile of OSGeo TMS (Tile Map Service) specification. That " +"tiling schemes consists of four 256x256 tiles at its zoom level 0, in " +"EPSG:3857 CRS, with extent extent in easting and northing in the range " +"[-20037508.34,20037508.34]. The same remark as with " +"PseudoTMS_GlobalGeodetic applies regarding interoperability with TMS." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:341 +msgid "" +"*GoogleCRS84Quad*, as described in `OGC 07-057r7 WMTS 1.0 " +"<http://portal.opengeospatial.org/files/?artifact_id=35326>`__ " +"specification, Annex E.3. That tiling schemes consists of a single " +"256x256 tile at its zoom level 0, in EPSG:4326 CRS, with extent in " +"longitude and latitude in the range [-180,180]. Consequently, at zoom " +"level 0, 64 lines are unused at the top and bottom of that tile. This may" +" cause issues with some implementations of the specification, and there " +"are some ambiguities about the exact definition of this tiling scheme. " +"Using InspireCRS84Quad/PseudoTMS_GlobalGeodetic instead is therefore " +"recommended. NOTE: `OGC WMTS Simple Profile 13-082r2 " +"<http://docs.opengeospatial.org/is/13-082r2/13-082r2.html#30>`__ changed " +"the definition of GoogleCRS84Quad (so not implemented by the driver). The" +" new definition includes a -1 level (that cannot be modeled in GeoPackage" +" given constraints on zoom_level being positive or 0), with a single tile" +" at origin -180,90 and whose bottom 128 lines are empty. Levels 0 or " +"greater are identical to the InspireCRS84Quad tiling scheme. So for " +"practical purposes, InspireCRS84Quad in GeoPackage is conformant to the " +"new GoogleCRS84Quad definition." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:362 +msgid "" +"In all the above tiling schemes, consecutive zoom levels defer by a " +"resolution of a factor of two." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:365 +msgid "" +"Starting with GDAL 3.2, it is also possible to use a Tile Matrix Set " +"definition, encoded as a JSON file, according to the `OGC Two Dimensional" +" Tile Matrix Set standard`_ Examples of such files can be found at " +"http://schemas.opengis.net/tms/1.0/json/examples/ The GDAL data directory" +" also contains files prefixed with ``tms_`` and with a ``.json`` " +"extension. If there is a ``tms_FOO.json`` file, then ``FOO`` can be used " +"as the value of the TILING_SCHEME creation option. There are restrictions" +" on the types of tile matrix set supported:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:373 +msgid "all zoom levels must have the same origin" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:374 +msgid "consecutive zoom levels defer by a resolution of a factor of two." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:375 +msgid "all zoom levels must have the same tile dimension" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:376 +msgid "variable matrix width tile set are not supported." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:381 +#: ../../source/drivers/raster/gtiff.rst:241 +msgid "Nodata value" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:383 +msgid "" +"The concept of the nodata value is only supported for tiled gridded " +"elevation datasets. For regular tiled rasters, the alpha band must rather" +" be used." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:387 +msgid "" +"For Float32 datasets with TIFF tiles, the concepts of nodata in GDAL and " +"null_value in the GeoPackage internals perfectly match." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:390 +msgid "" +"For Int16, UInt16 or Float32 with PNG tiles, GDAL will generally remap " +"the input nodata value to another value." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:393 +msgid "On writing, for PNG tiles, the behavior is the following one:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:396 +#: ../../source/drivers/raster/gpkg.rst:405 +#: ../../source/drivers/raster/gpkg.rst:415 +msgid "GDAL data type" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:396 +msgid "Input GDAL nodata value" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:396 +#: ../../source/drivers/raster/gpkg.rst:405 +#: ../../source/drivers/raster/gpkg.rst:415 +msgid "null_value in GPKG gpkg_2d_gridded_coverage_ancillary" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:397 +#: ../../source/drivers/raster/gpkg.rst:406 +#: ../../source/drivers/raster/gpkg.rst:407 +#: ../../source/drivers/raster/gpkg.rst:416 +msgid "Int16" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:397 +#: ../../source/drivers/raster/gpkg.rst:399 +msgid "Any" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:397 +#: ../../source/drivers/raster/gpkg.rst:399 +#: ../../source/drivers/raster/gpkg.rst:416 +#: ../../source/drivers/raster/gpkg.rst:418 +msgid "65535" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:398 +#: ../../source/drivers/raster/gpkg.rst:408 +#: ../../source/drivers/raster/gpkg.rst:417 +msgid "UInt16" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:398 +#: ../../source/drivers/raster/gpkg.rst:417 +msgid "X (if coverage offset == 0 and coverage scale == 1)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:398 +#: ../../source/drivers/raster/gpkg.rst:407 +#: ../../source/drivers/raster/gpkg.rst:408 +#: ../../source/drivers/raster/gpkg.rst:409 +#: ../../source/drivers/raster/gpkg.rst:417 +msgid "X" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:399 +#: ../../source/drivers/raster/gpkg.rst:409 +#: ../../source/drivers/raster/gpkg.rst:418 +msgid "Float32" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:402 +msgid "On reading, for PNG tiles, the behavior is the following one:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:405 +msgid "Exposed GDAL nodata value" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:406 +msgid ">= 32768" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:406 +#: ../../source/drivers/raster/gpkg.rst:416 +msgid "-32768" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:407 +msgid "X <= 32767" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:412 +msgid "Thus, perfect roundtripping is achieved in the following cases:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:415 +msgid "GDAL nodata value" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:502 +msgid "" +"Starting with GDAL 3.2, the value of TILING_SCHEME can also be the " +"filename of a JSON file according to the `OGC Two Dimensional Tile Matrix" +" Set standard`_, a URL to such file, the radical of a definition file in " +"the GDAL data directory (e.g. ``FOO`` for a file named ``tms_FOO.json``) " +"or the inline JSON definition. Note: the TILING_SCHEME option with a non-" +"CUSTOM value is best used with the gdal_translate utility / CreateCopy() " +"API operation. If used with gdalwarp, it requires setting the -tr switch " +"to the exact value expected by one zoom level of the tiling scheme." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:511 +msgid "" +"In non-CUSTOM mode, the actual resolution can be controlled with the " +":co:`ZOOM_LEVEL` or :co:`ZOOM_LEVEL_STRATEGY` options." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:625 +msgid "" +"gdaladdo / BuildOverviews() can be used to compute overviews. Power-of-" +"two overview factors (2,4,8,16,...) should be favored to be conformant " +"with the baseline GeoPackage specification. Use of other overview factors" +" will work with the GDAL driver, and cause the `gpkg_zoom_other " +"<http://www.geopackage.org/spec/#extension_zoom_other_intervals>`__ " +"extension to be registered, but that could potentially cause " +"interoperability problems with other implementations that do not support " +"that extension." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:634 +#: ../../source/drivers/raster/mbtiles.rst:510 +msgid "" +"Overviews can also be cleared with the -clean option of gdaladdo (or " +"BuildOverviews() with nOverviews=0)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:640 +msgid "" +"GDAL uses the standardized `gpkg_metadata " +"<http://www.geopackage.org/spec/#_metadata_table>`__ and " +"`gpkg_metadata_reference " +"<http://www.geopackage.org/spec/#_metadata_reference_table>`__ tables to " +"read and write metadata." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:646 +msgid "" +"GDAL metadata, from the default metadata domain and possibly other " +"metadata domains, is serialized in a single XML document, conformant with" +" the format used in GDAL PAM (Persistent Auxiliary Metadata) .aux.xml " +"files, and registered with md_scope=dataset and " +"md_standard_uri=http://gdal.org in gpkg_metadata. In " +"gpkg_metadata_reference, this entry is referenced with a " +"reference_scope=table and table_name={name of the raster table}" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:654 +msgid "" +"It is possible to read and write metadata that applies to the global " +"GeoPackage, and not only to the raster table, by using the *GEOPACKAGE* " +"metadata domain." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:658 +#: ../../source/drivers/vector/gpkg.rst:543 +msgid "" +"Metadata not originating from GDAL can be read by the driver and will be " +"exposed as metadata items with keys of the form GPKG_METADATA_ITEM_XXX " +"and values the content of the *metadata* columns of the gpkg_metadata " +"table. Update of such metadata is not currently supported through GDAL " +"interfaces ( although it can be through direct SQL commands)." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:664 +#: ../../source/drivers/vector/gpkg.rst:549 +msgid "" +"The specific DESCRIPTION and IDENTIFIER metadata item of the default " +"metadata domain can be used in read/write to read from/update the " +"corresponding columns of the gpkg_contents table." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:668 +msgid "" +"You can set the CREATE_METADATA_TABLES configuration option to NO to " +"avoid creating and filling the metadata tables." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:672 +msgid "IMAGE_STRUCTURE metadata item" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:676 +msgid "" +"Implementation details, normally transparent to GDAL users, but useful " +"for other implementations." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:679 +msgid "" +"Starting with GDAL 3.6.1, the following optional metadata items can be " +"read and write into the ``IMAGE_STRUCTURE`` metadata domain, in the " +"``<GDALMultiDomainMetadata>`` XML element:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:683 +msgid "" +"BAND_COUNT=1, 2, 3 or 4. Applies only for Byte data. Set when creating a " +"dataset so that GDAL knows the number of bands when reopening it." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:686 +msgid "" +"COLOR_TABLE={{r0,g0,b0,a0},...{r255,g255,b255,a255}}. Applies only for " +"Byte data and a single band dataset. Set when creating a dataset from a " +"source dataset that has a color table." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:690 +msgid "" +"TILE_FORMAT=PNG/PNG8/PNG_JPEG/JPEG/WEBP. Set when creating a dataset so " +"that GDAL knows the tile format when reopening it, for updates." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:693 +msgid "NODATA_VALUE=integer between 0 and 255. Applies only for Byte data." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:696 +#: ../../source/drivers/raster/netcdf.rst:351 +#: ../../source/drivers/raster/nitf_advanced.rst:328 +#: ../../source/drivers/raster/vrt.rst:562 +#: ../../source/drivers/vector/geojson.rst:510 +#: ../../source/drivers/vector/gml.rst:1334 +#: ../../source/drivers/vector/jsonfg.rst:220 +#: ../../source/drivers/vector/s57.rst:227 +msgid "Example:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:712 +#: ../../source/drivers/vector/gpkg.rst:648 +msgid "Level of support of GeoPackage Extensions" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:714 +msgid "(Restricted to those have a raster scope)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:716 +#: ../../source/drivers/vector/gpkg.rst:652 +msgid "Extensions" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:719 +#: ../../source/drivers/vector/gpkg.rst:655 +msgid "Extension name" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:720 +#: ../../source/drivers/vector/gpkg.rst:656 +msgid "OGC adopted extension ?" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:721 +#: ../../source/drivers/vector/gpkg.rst:657 +msgid "Supported by GDAL?" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:722 +msgid "" +"`Zoom Other intervals " +"<http://www.geopackage.org/guidance/extensions/zoom_other_intervals.html>`__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:723 +#: ../../source/drivers/raster/gpkg.rst:724 +#: ../../source/drivers/raster/gpkg.rst:726 +#: ../../source/drivers/raster/gpkg.rst:727 +#: ../../source/drivers/raster/gpkg.rst:729 +#: ../../source/drivers/raster/gpkg.rst:730 +#: ../../source/drivers/raster/gpkg.rst:732 +#: ../../source/drivers/raster/gpkg.rst:735 +#: ../../source/drivers/vector/gpkg.rst:659 +#: ../../source/drivers/vector/gpkg.rst:662 +#: ../../source/drivers/vector/gpkg.rst:663 +#: ../../source/drivers/vector/gpkg.rst:665 +#: ../../source/drivers/vector/gpkg.rst:666 +#: ../../source/drivers/vector/gpkg.rst:668 +#: ../../source/drivers/vector/gpkg.rst:671 +#: ../../source/drivers/vector/gpkg.rst:680 +msgid "Yes" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:725 +msgid "" +"`Tiles Encoding WebP " +"<http://www.geopackage.org/guidance/extensions/tiles_encoding_webp.html>`__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:728 +#: ../../source/drivers/vector/gpkg.rst:664 +msgid "`Metadata <http://www.geopackage.org/guidance/extensions/metadata.html>`__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:731 +#: ../../source/drivers/vector/gpkg.rst:670 +msgid "" +"`WKT for Coordinate Reference Systems " +"<http://www.geopackage.org/guidance/extensions/wkt_for_crs.md>`__ (WKT " +"v2)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:733 +msgid "" +"Partially, since GDAL 2.2. GDAL can read databases using this extension. " +"GDAL 3.0 brings support for the WKT v2 entry." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:734 +msgid "" +"`Tiled Gridded Coverage Data " +"<http://www.geopackage.org/guidance/extensions/tiled_gridded_coverage_data.html>`__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:736 +msgid "" +"Yes, since GDAL 2.3 (GDAL 2.2 supported a preliminary version of this " +"extension)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:741 +msgid "" +"Simple translation of a GeoTIFF into GeoPackage. The table 'byte' will be" +" created with the tiles." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:748 +msgid "Translation of a GeoTIFF into GeoPackage using WebP tiles" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:754 +msgid "" +"Translation of a GeoTIFF into GeoPackage using GoogleMapsCompatible " +"tiling scheme (with reprojection and resampling if needed)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:761 +msgid "Building of overviews of an existing GeoPackage, and forcing JPEG tiles" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:768 +msgid "" +"Addition of a new subdataset to an existing GeoPackage, and choose a non " +"default name for the raster table." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:775 +msgid "Reprojection of an input dataset to GeoPackage" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:781 +msgid "Open a specific raster table in a GeoPackage" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:790 +msgid "Raster SQL functions" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:792 +msgid "" +"The raster SQL functions mentioned at " +":ref:`sql_sqlite_dialect_raster_functions` are also available." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:795 +msgid "" +"The ``gdal_get_layer_pixel_value()`` function (added in GDAL 3.7), " +"variant of the generic ``gdal_get_pixel_value()``, can be used to extract" +" the value of a pixel in a raster layer of the current dataset." +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:799 +msgid "It takes 5 arguments:" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:801 +msgid "a string with the layer/table name" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:802 +msgid "a band number (numbering starting at 1)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:803 +msgid "" +"a string being \"georef\" to indicate that subsequent values will be " +"georeferenced coordinates, or \"pixel\" to indicate that subsequent " +"values will be in column, line pixel space" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:806 +msgid "georeferenced X value or column number" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:807 +msgid "georeferenced Y value or line number" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:817 +msgid ":ref:`GeoPackage vector <vector.gpkg>` documentation page" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:818 +#: ../../source/drivers/vector/gpkg.rst:812 +msgid "" +"`Getting Started With GeoPackage <http://www.geopackage.org/guidance" +"/getting-started.html>`__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:820 +#: ../../source/drivers/vector/gpkg.rst:814 +msgid "" +"`OGC GeoPackage format standard <http://www.geopackage.org/spec/>`__ " +"specification, HTML format (current/development version of the standard)" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:823 +#: ../../source/drivers/vector/gpkg.rst:817 +msgid "" +"`OGC GeoPackage Encoding Standard " +"<http://www.opengeospatial.org/standards/geopackage>`__ page" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:825 +#: ../../source/drivers/vector/gpkg.rst:819 +msgid "`SQLite <http://sqlite.org/>`__" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:826 +msgid ":ref:`PNG driver <raster.png>` documentation page" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:827 +msgid ":ref:`JPEG driver <raster.jpeg>` documentation page" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:828 +msgid ":ref:`WEBP driver <raster.webp>` documentation page" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:829 +msgid "" +"`OGC 07-057r7 WMTS 1.0 " +"<http://portal.opengeospatial.org/files/?artifact_id=35326>`__ " +"specification" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:832 +msgid "" +"`OSGeo TMS (Tile Map Service) " +"<http://wiki.osgeo.org/wiki/Tile_Map_Service_Specification>`__ " +"specification" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:837 +#: ../../source/drivers/vector/selafin.rst:413 +msgid "Other notes" +msgstr "" + +#: ../../source/drivers/raster/gpkg.rst:839 +msgid "" +"Development of raster support in the GeoPackage driver was financially " +"supported by `Safe Software <http://www.safe.com>`__." +msgstr "" + +#: ../../source/drivers/raster/grass.rst:6 +#: ../../source/drivers/vector/grass.rst:6 +msgid "GRASS" +msgstr "" + +#: ../../source/drivers/raster/grass.rst:10 +msgid "" +"The GDAL-GRASS driver can read GRASS GIS raster maps. The driver is " +"maintained at the `GDAL-GRASS GIS driver repository " +"<https://github.com/OSGeo/gdal-grass/>`__." +msgstr "" + +#: ../../source/drivers/raster/grass.rst:13 +msgid "" +"For the driver documentation, please visit the `GDAL-GRASS GIS raster " +"driver page <https://github.com/OSGeo/gdal-" +"grass/blob/main/docs/grass_raster.md>`__." +msgstr "" + +#: ../../source/drivers/raster/grass.rst:20 +#: ../../source/drivers/vector/grass.rst:20 +msgid "`GRASS GIS home page <http://grass.osgeo.org>`__" +msgstr "" + +#: ../../source/drivers/raster/grassasciigrid.rst:5 +msgid "GRASSASCIIGrid -- GRASS ASCII Grid" +msgstr "" + +#: ../../source/drivers/raster/grassasciigrid.rst:7 +msgid "GRASSASCIIGrid" +msgstr "" + +#: ../../source/drivers/raster/grassasciigrid.rst:11 +msgid "" +"Supports reading GRASS ASCII grid format (similar to Arc/Info ASCIIGRID " +"command)." +msgstr "" + +#: ../../source/drivers/raster/grassasciigrid.rst:14 +msgid "" +"By default, the datatype returned for GRASS ASCII grid datasets by GDAL " +"is autodetected, and set to Float32 for grid with floating point values " +"or Int32 otherwise. This is done by analysing the format of the null " +"value and the first 100k bytes of data of the grid. You can also " +"explicitly specify the datatype by setting the GRASSASCIIGRID_DATATYPE " +"configuration option (Int32, Float32 and Float64 values are supported " +"currently)" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:5 +msgid "GRIB -- WMO General Regularly-distributed Information in Binary form" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:7 +msgid "GRIB" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:11 +msgid "" +"GDAL supports GRIB1 (reading) and GRIB2 (reading and writing) format " +"raster data, with support for common coordinate system, georeferencing " +"and other metadata. GRIB format is commonly used for distribution of " +"Meteorological information, and is propagated by the World Meteorological" +" Organization." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:17 +msgid "" +"The GDAL GRIB driver is based on a modified version of the degrib " +"application which is written primarily by Arthur Taylor of NOAA NWS NDFD " +"(MDL). The degrib application (and the GDAL GRIB driver) are built on the" +" g2clib grib decoding library written primarily by John Huddleston of " +"NOAA NWS NCEP." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:23 +msgid "" +"GRIB2 files without projection on lon/lat grids have the peculiarity of " +"using longitudes in the [0,360] range and wrapping around the " +"antimeridian as opposed to the usual wrapping around the prime meridian " +"of other raster datasets. Starting with GDAL 3.4.0, when reading such " +"files, a transparent conversion of the longitudes to [-180,180] will be " +"performed and the data will be rewrapped around the prime meridian - the " +"split&swap mode. This behavior can be disabled by setting the " +":config:`GRIB_ADJUST_LONGITUDE_RANGE` configuration option to `NO`." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:32 +msgid "" +"There are several encoding schemes for raster data in GRIB format. Most " +"common ones should be supported including PNG encoding. JPEG2000 encoded " +"GRIB files will generally be supported if GDAL is also built with " +"JPEG2000 support via one of the GDAL JPEG2000 drivers." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:37 +msgid "" +"GRIB files may a be represented in GDAL as having many bands, with some " +"sets of bands representing a time sequence. GRIB bands are represented as" +" Float64 (double precision floating point) regardless of the actual " +"values. GRIB metadata is captured as per-band metadata and used to set " +"band descriptions, similar to this:" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:54 +msgid "" +"GRIB2 files may also include an extract of other metadata, such as the " +"`identification section " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_sect1.shtml>`__," +" `product definition " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_sect4.shtml>`__" +" template number (GRIB_PDS_PDTN, octet 8-9), and the product definition " +"template values (GRIB_PDS_TEMPLATE_NUMBERS, octet 10+) as metadata like " +"this:" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:71 +msgid "" +"GRIB_DISCIPLINE was added in GDAL 2.3.0 and is the `Discipline " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table0-0.shtml>`__" +" field of the Section 0 of the message." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:75 +msgid "" +"GRIB_IDS was added in GDAL 2.3.0 and is the `identification section " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table0-0.shtml>`__" +" / Section 1 of the message." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:79 +msgid "" +"GRIB_PDS_TEMPLATE_ASSEMBLED_VALUES was added in GDAL 2.3.0, and use " +"template definitions to assemble several bytes that make a template item " +"into a 16 or 32 bit signed/unsigned integers, whereas " +"GRIB_PDS_TEMPLATE_NUMBERS expose raw bytes" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:96 +msgid "" +"|about-config-options| This paragraph lists the configuration options " +"that can be set to alter the default behavior of the GRIB driver." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:127 +#: ../../source/drivers/raster/rmf.rst:46 +#: ../../source/drivers/raster/s102.rst:38 +#: ../../source/drivers/raster/s104.rst:39 +#: ../../source/drivers/raster/s111.rst:43 +#: ../../source/drivers/raster/stacit.rst:44 +#: ../../source/drivers/raster/stacta.rst:58 +#: ../../source/drivers/vector/csv.rst:268 +#: ../../source/drivers/vector/csw.rst:52 +#: ../../source/drivers/vector/elasticsearch.rst:40 +#: ../../source/drivers/vector/esrijson.rst:62 +#: ../../source/drivers/vector/flatgeobuf.rst:43 +#: ../../source/drivers/vector/gml.rst:504 +#: ../../source/drivers/vector/gmlas.rst:188 +#: ../../source/drivers/vector/hana.rst:63 +#: ../../source/drivers/vector/jsonfg.rst:99 +#: ../../source/drivers/vector/oci.rst:294 +#: ../../source/drivers/vector/odbc.rst:64 +#: ../../source/drivers/vector/openfilegdb.rst:105 +#: ../../source/drivers/vector/osm.rst:225 +#: ../../source/drivers/vector/parquet.rst:34 +#: ../../source/drivers/vector/pg.rst:156 +#: ../../source/drivers/vector/pgeo.rst:72 +#: ../../source/drivers/vector/shapefile.rst:279 +#: ../../source/drivers/vector/sqlite.rst:243 +msgid "|about-open-options| The following open options are supported:" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:152 +msgid "GRIB2 write support" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:154 +msgid "" +"GRIB2 write support is available since GDAL 2.3.0, through the " +"CreateCopy() / gdal_translate interface." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:157 +msgid "" +"Each band of the input dataset is translated as a GRIB2 message, and all " +"of them are concatenated in a single file, conforming to the usual " +"practice." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:161 +msgid "" +"The input dataset must be georeferenced, and the supported projections " +"are: Geographic Longitude/Latitude, Mercator 1SP/2SP, Transverse " +"Mercator, Polar Stereographic, Lambert Conformal Conic 1SP/2SP, Albers " +"Conic Equal Area and Lambert Azimuthal Equal Area." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:166 +msgid "" +"A number of creation options are available as detailed in below sections." +" Those creation options are valid for all bands. But it is possible to " +"override those global settings in a per-band way, by defining creation " +"options that use the same key and are prefixed by BAND_X\\_ where X is " +"the band number between 1 and the total number of bands. For example " +"BAND_1_PDS_PDTN" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:174 +msgid "Product identification and definition" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:176 +msgid "" +"Users are strongly advised to provide necessary information to " +"appropriately fill the `Section 0 / \"Indicator\" " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_sect0.shtml>`__," +" `Section 1 / \"Identification section\" " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_sect1.shtml>`__" +" and `Section 4 / \"Product definition section\" " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_sect4.shtml>`__" +" with the following creation options. Otherwise, GDAL will fill with " +"default values, but readers might have trouble exploiting GRIB2 datasets " +"generating with those defaults. |about-creation-options|" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:195 +msgid "0: Meteorological Products. Default value" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:196 +msgid "1: Hydrological Products" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:197 +msgid "2: Land Surface Products" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:198 +msgid "3, 4: Space Products" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:199 +msgid "10: Oceanographic Product" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:318 +msgid "Data encoding" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:320 +msgid "" +"In GRIB2, a number of data encoding schemes exist (see `Section 5 / " +"\"Data representation section\" " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_sect5.shtml>`__)." +" By default, GDAL will select an appropriate data encoding that will " +"preserve the range of input data. with the :co:`DATA_ENCODING`, " +":co:`NBITS`, :co:`DECIMAL_SCALE_FACTOR`, :co:`JPEG2000_DRIVER`, " +":co:`COMPRESSION_RATIO` and :co:`SPATIAL_DIFFERENCING_ORDER` creation " +"options." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:328 +msgid "Users can override those defaults with the following creation options are:" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:338 +msgid "" +"In AUTO mode, COMPLEX_PACKING is selected if input band has a nodata " +"value. Otherwise if input band datatype is Float32 or Float64, " +"IEEE_FLOATING_POINT is selected. Otherwise SIMPLE_PACKING is selected." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:342 +msgid "" +"`SIMPLE_PACKING " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_temp5-0.shtml>`__:" +" use integer representation internally, with offset and decimal and/or " +"binary scaling. So can be used for any datatype." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:345 +msgid "" +"COMPLEX_PACKING: evolution of SIMPLE_PACKING with nodata handling. By " +"default, a `non-spatial differencing encoding is used " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_temp5-2.shtml>`__," +" but if SPATIAL_DIFFERENCING_ORDER=1 or 2, `complex packing with spatial " +"differencing " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_temp5-3.shtml>`__" +" is used" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:352 +msgid "" +"`IEEE_FLOATING_POINT " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_temp5-4.shtml>`__:" +" store values as IEEE-754 single or double precision numbers." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:354 +msgid "" +"`PNG " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_temp5-41.shtml>`__:" +" uses the same preparation steps as SIMPLE_PACKING but with PNG encoding " +"of the integer values." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:357 +msgid "" +"`JPEG2000 " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_temp5-40.shtml>`__:" +" uses the same preparation steps as SIMPLE_PACKING but with JPEG2000 " +"encoding of the integer values." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:414 +msgid "Data units" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:416 +msgid "" +"Internally GRIB stores values in the units of the international system " +"(ie Metric system). So temperatures must be stored as Kelvin degrees. But" +" on the reading side of the driver, fields with temperatures are exposed " +"in Celsius degrees (unless the :config:`GRIB_NORMALIZE_UNITS` " +"configuration option is set to NO). For consistency, the writing side of " +"the driver also assumed that temperature (detected if the first value of " +"a product definition template, ie the *Parameter category* is " +"0=Temperature) values in the input dataset will be in Celsius degrees, " +"and will automatically offset them to Kelvin degrees. It is possible to " +"control that behavior using the :co:`INPUT_UNIT` creation option:" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:435 +msgid "GRIB2 to GRIB2 conversions" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:437 +msgid "" +"If GRIB2 to GRIB2 translation is done with gdal_translate (or " +"CreateCopy()), the GRIB_DISCIPLINE, GRIB_IDS, GRIB_PDS_PDTN and " +"GRIB_PDS_TEMPLATE_NUMBERS metadata items of the bands of the source " +"dataset are used by default (unless creation options override them)." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:442 +msgid "" +"DECIMAL_SCALE_FACTOR and NBITS will also be attempted to be retrieved " +"from the GRIB special metadata domain." +msgstr "" + +#: ../../source/drivers/raster/grib.rst:458 +msgid "" +"`NOAA NWS NDFD \"degrib\" GRIB2 Decoder " +"<https://www.weather.gov/mdl/degrib_archive>`__" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:460 +msgid "" +"`NOAA NWS NCEP g2clib grib decoding library " +"<http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2/>`__" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:462 +msgid "" +"`WMO GRIB1 Format Documents <http://www.wmo.int/pages/prog/www/WDM/Guides" +"/Guide-binary-2.html>`__" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:464 +msgid "" +"`NCEP WMO GRIB2 Documentation " +"<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/>`__" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:468 +#: ../../source/drivers/raster/openfilegdb.rst:105 +#: ../../source/drivers/raster/postgisraster.rst:121 +#: ../../source/drivers/raster/sentinel2.rst:464 +#: ../../source/drivers/vector/gml.rst:1380 +#: ../../source/drivers/vector/gmlas.rst:479 +#: ../../source/drivers/vector/jml.rst:94 +#: ../../source/drivers/vector/netcdf.rst:506 +#: ../../source/drivers/vector/oci.rst:357 +#: ../../source/drivers/vector/openfilegdb.rst:374 +#: ../../source/drivers/vector/sqlite.rst:588 +msgid "Credits" +msgstr "" + +#: ../../source/drivers/raster/grib.rst:470 +msgid "" +"Support for GRIB2 write capabilities has been funded by Meteorological " +"Service of Canada." +msgstr "" + +#: ../../source/drivers/raster/gs7bg.rst:5 +msgid "GS7BG -- Golden Software Surfer 7 Binary Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/gs7bg.rst:7 +msgid "GS7BG" +msgstr "" + +#: ../../source/drivers/raster/gs7bg.rst:11 +msgid "" +"This is the binary (non-human-readable) version of one of the raster " +"formats used by Golden Software products (such as the Surfer series). " +"This format differs from the :ref:`raster.gsbg` format (also known as " +"Surfer 6 binary grid format), it is more complicated and flexible." +msgstr "" + +#: ../../source/drivers/raster/gs7bg.rst:16 +msgid "NOTE: Implemented as :source_file:`frmts/gsg/gs7bgdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/gsag.rst:5 +msgid "GSAG -- Golden Software ASCII Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/gsag.rst:7 +msgid "GSAG" +msgstr "" + +#: ../../source/drivers/raster/gsag.rst:11 +msgid "" +"This is the ASCII-based (human-readable) version of one of the raster " +"formats used by Golden Software products (such as the Surfer series). " +"This format is supported for both reading and writing (copy mode only). " +"Currently the associated formats for color, metadata, and shapes are not " +"supported." +msgstr "" + +#: ../../source/drivers/raster/gsag.rst:17 +msgid "NOTE: Implemented as :source_file:`frmts/gsg/gsagdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/gsbg.rst:5 +msgid "GSBG -- Golden Software Binary Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/gsbg.rst:7 +msgid "GSBG" +msgstr "" + +#: ../../source/drivers/raster/gsbg.rst:11 +msgid "" +"This is the binary (non-human-readable) version of one of the raster " +"formats used by Golden Software products (such as the Surfer series). " +"Like the ASCII version, this format is supported for both reading and " +"writing (including create, delete, and copy). Currently the associated " +"formats for color, metadata, and shapes are not supported." +msgstr "" + +#: ../../source/drivers/raster/gsbg.rst:17 +msgid "" +"Surfer 8 uses a fixed nodata value at 1.701410009187828e+38. When writing" +" a GSBG dataset, GDAL remaps the user-specified input nodata value to " +"1.701410009187828e+38." +msgstr "" + +#: ../../source/drivers/raster/gsbg.rst:20 +msgid "NOTE: Implemented as :source_file:`frmts/gsg/gsbgdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/gsc.rst:5 +msgid "GSC -- GSC Geogrid" +msgstr "" + +#: ../../source/drivers/raster/gsc.rst:7 +msgid "GSC" +msgstr "" + +#: ../../source/drivers/raster/gsc.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/raw/gscdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/gta.rst:5 +msgid "GTA - Generic Tagged Arrays" +msgstr "" + +#: ../../source/drivers/raster/gta.rst:7 +msgid "GTA" +msgstr "" + +#: ../../source/drivers/raster/gta.rst:11 +msgid "GDAL can read and write GTA data files through the libgta library." +msgstr "" + +#: ../../source/drivers/raster/gta.rst:14 +msgid "" +"GTA is a file format that can store any kind of multidimensional array " +"data, allows generic manipulations of array data, and allows easy " +"conversion to and from other file formats." +msgstr "" + +#: ../../source/drivers/raster/gta.rst:41 +msgid "`GTA home page <http://gta.nongnu.org>`__" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:5 +msgid "GTI -- GDAL Raster Tile Index" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:9 +msgid "GTI" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:14 +#: ../../source/drivers/raster/vrt.rst:12 +#: ../../source/drivers/vector/geopackage_aspatial.rst:18 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:16 +msgid "Introduction" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:16 +msgid "" +"The GTI driver is a driver that allows to handle catalogs with a large " +"number of raster files (called \"tiles\" in the rest of this document, " +"even if a regular tiling is not required by the driver), and build a " +"virtual mosaic from them. Each tile may be in any GDAL supported raster " +"format, and be a file stored on a regular filesystem, or any GDAL " +"supported virtual filesystem (for raster drivers that support such " +"files)." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:23 +msgid "" +"This driver offers similar functionality as the :ref:`VRT <raster.vrt>` " +"driver with the following main differences:" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:26 +msgid "" +"The tiles are listed as features of any GDAL supported vector format. Use" +" of formats with efficient spatial filtering is recommended, such as " +":ref:`GeoPackage <vector.gpkg>`, :ref:`FlatGeoBuf <vector.flatgeobuf>` or" +" :ref:`PostGIS <vector.pg>`. The GTI driver can thus use a larger number " +"of tiles than the VRT driver (hundreds of thousands or more), provided " +"the underlying vector format is efficient." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:33 +msgid "" +"The tiles may have different SRS. The GTI driver is capable of on-the-fly" +" reprojection" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:36 +msgid "" +"The GTI driver offers control on the order in which tiles are composited," +" when they overlap (z-order)" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:39 +msgid "" +"The GTI driver honours the mask/alpha band when compositing together " +"overlapping tiles." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:42 +msgid "" +"Contrary to the VRT driver, the GTI driver does not enable to alter " +"characteristics of referenced tiles, such as their georeferencing, nodata" +" value, etc. If such behavior is desired, the tiles must be for example " +"wrapped individually in a VRT file before being referenced in the GTI " +"index." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:48 +#: ../../source/drivers/vector/mvt.rst:64 +msgid "Connection strings" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:50 +msgid "The GTI driver accepts different types of connection strings:" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:52 +msgid "" +"a vector file in GeoPackage format with a ``.gti.gpkg`` extension, or in " +"FlatGeoBuf format with a ``.gti.fgb`` extension, meeting the minimum " +"requirements for a GTI compatible tile index, detailed later." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:56 +msgid "For example: ``tileindex.gti.gpkg``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:58 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if GTI`` option to command " +"line utilities accepting it, or ``GTI`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename if its extension is just ``.gpkg`` or " +"``.fgb``." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:63 +msgid "" +"any vector file in a GDAL supported format, with its filename (or " +"connection string prefixed with ``GTI:``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:66 +msgid "" +"For example: ``GTI:tileindex.shp`` or ``GTI:PG:database=my_db " +"schema=tileindex``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:68 +msgid "" +"a XML file, following the below GTI XML format, generally with the " +"recommended ``.gti`` extension, referencing a vector file. Using such XML" +" file may be more practical for tile indexes not stored in a file, or if " +"some additional metadata must be defined at the dataset or band level of " +"the virtual mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:74 +msgid "For example: ``tileindex.gti``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:77 +msgid "Tile index requirements" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:79 +msgid "" +"The minimum requirements for a GTI compatible tile index is to be a " +"vector format supported by GDAL, with a geometry column storing polygons " +"with the extent of the tiles, and an attribute field of type string, " +"storing the path to each tile. The default name for this attribute field " +"is ``location``. If relative filenames are stored in the tile index, they" +" are considered to be relative to the path of the tile index." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:86 +msgid "" +"In addition, for formats that can store layer metadata (GeoPackage, " +"FlatGeoBuf, PostGIS, ...), the following layer metadata items may be set:" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:89 +msgid "" +"``RESX=<float>`` and ``RESY=<float>``: resolution along X and Y axis, in " +"SRS units / pixel." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:92 +msgid "" +"Setting those metadata items is recommended, otherwise the driver will " +"try to open one of the tiles referenced in the tile index, and use its " +"resolution as the resolution for the mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:96 +msgid "" +"``BAND_COUNT=<int>``: number of bands of the virtual mosaic. The tiles " +"stored in an index should generally have the same number of bands." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:99 +msgid "" +"Setting that metadata item is recommended, otherwise the driver will try " +"to open one of the tiles referenced in the tile index, and use it as the " +"number of bands for the mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:103 +msgid "" +"A mix of tiles with N and N+1 bands is allowed, provided that the color " +"interpretation of the (N+1)th band is alpha. The N+1 value must be " +"written as the band count in that situation." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:107 +msgid "" +"If tiles contains a single band with a color table, and that the color " +"table may differ among tiles, BAND_COUNT should be set to 3 (resp. 4) to " +"perform expansion to Red, Green, Blue components (resp. Red, Green, Blue," +" Alpha). If the color table is identical between the tiles, and it is " +"desired to preserve it, the VRRTI XML file format may be used to include " +"the ColorTable element." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:115 +msgid "" +"``DATA_TYPE=<val>``: data type of the tiles of the tile index ``Byte``, " +"``Int8``, ``UInt16``, ``Int16``, ``UInt32``, ``Int32``, ``UInt64``, " +"``Int64``, ``Float32``, ``Float64``, ``CInt16``, ``CInt32``, ``CFloat32``" +" or ``CFloat64``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:120 +msgid "" +"Setting that metadata item is recommended, otherwise the driver will try " +"to open one of the tiles referenced in the tile index, and use it as the " +"data type for the mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:124 +msgid "" +"``NODATA=<val>[,<val]...``: nodata value of the bands of the virtual " +"mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:126 +msgid "" +"Note that source tiles may have or may not have a nodata value " +"themselves, and it may be different than the nodata value of the virtual " +"mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:129 +msgid "" +"``MINX=<float>``, ``MINY=<float>``, ``MAXX=<float>`` and " +"``MAXY=<float>``: defines the extent of the virtual mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:132 +msgid "" +"For vector formats that have efficient retrieval of the layer extent, " +"setting those items is not needed." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:135 +msgid "" +"``GEOTRANSFORM=<gt0>,<gt1>,<gt2>,<gt3>,<gt4>,<gt5>``: defines the " +"GeoTransform. Used together with ``XSIZE`` and ``YSIZE``, this is an " +"alternate way of defining the extent and resolution os the virtual " +"mosaic." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:139 +msgid "" +"It is not necessary to define this item if ``RESX=`` and ``RESY`` are set" +" (potentially accompanied with ``MINX``, ``MINY``, ``MAXX`` and ``MAXY``)" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:142 +msgid "``XSIZE=<int>``, ``YSIZE=<int>``: size of the virtual mosaic in pixel." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:144 +msgid "" +"``COLOR_INTERPRETATION=<val>[,<val]...``: color interpretation of the " +"bands of the mosaic. Possible values are ``red``, ``green``, ``blue``, " +"``alpha``, ``undefined``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:148 +msgid "" +"``SRS=<string>``: defines the SRS of the virtual mosaic, using any value " +"supported by the :cpp:func:`OGRSpatialReference::SetFromUserInput` call, " +"which includes EPSG Projected, Geographic or Compound CRS (i.e. " +"EPSG:4296), a well known text (WKT) CRS definition, PROJ.4 declarations, " +"etc." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:153 +msgid "" +"It is not necessary to define this element if the virtual mosaic SRS is " +"recorded as the SRS of the vector layer of the tile index." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:156 +msgid "" +"``LOCATION_FIELD=<string>``: name of the field where the tile location is" +" stored. Defaults to ``location``." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:159 +msgid "" +"``SORT_FIELD=<string>``: name of a field to use to control the order in " +"which tiles are composited, when they overlap (z-order). That field may " +"be of type String, Integer, Integer64, Date or DateTime. By default, the " +"higher the value in that field, the last the corresponding tile will be " +"rendered in the virtual mosaic (unless SORT_FIELD_ASC=NO is set)" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:165 +msgid "" +"``SORT_FIELD_ASC=YES|NO``: whether the values in SORT_FIELD should be " +"sorted in ascendent or descent order. Defaults to YES (ascendent)" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:168 +msgid "" +"``BLOCKXSIZE=<int>`` and ``BLOCKYSIZE=<int>``: Block size of bands of the" +" virtual mosaic. Defaults to 256x256." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:171 +msgid "" +"``MASK_BAND=YES|NO``: whether a dataset-level mask band should be " +"exposed. Defaults to NO." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:174 +msgid "" +"``RESAMPLING=<val>``: Resampling method to use for on-the-fly " +"reprojection, or rendering of tiles whose origin coordinates are not at " +"an offset multiple of the resolution of the mosaic compared to the origin" +" of the mosaic. In that later case, RESAMPLING is only taken into account" +" when requesting pixels with the default nearest resampling mode." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:180 +msgid "" +"Possible values: ``nearest``, ``cubic``, ``cubicspline``, ``lanczos``, " +"``average``, ``rms``, ``gauss``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:182 +msgid "Defaults to ``nearest``" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:184 +msgid "" +"``BAND_<number>_OFFSET=<val>`` where number is an integer index starting " +"at 1." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:186 +msgid "Additive offset to apply to the raw numbers of the band." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:188 +msgid "" +"``BAND_<number>_SCALE=<val>`` where number is an integer index starting " +"at 1." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:190 +msgid "Multiplicative factor to apply to the raw numbers of the band." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:192 +msgid "" +"``BAND_<number>_UNITTYPE=<val>`` where number is an integer index " +"starting at 1." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:194 +msgid "Unit of the band." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:196 +msgid "" +"``OVERVIEW_<idx>_DATASET=<string>`` where idx is an integer index " +"starting at 0." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:198 +msgid "" +"Name of the dataset to use as the first overview level. This may be a " +"raster dataset (for example a GeoTIFF file, or another GTI dataset). This" +" may also be a vector dataset with a GTI compatible layer, potentially " +"specified with ``OVERVIEW_<idx>_LAYER``." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:203 +msgid "" +"``OVERVIEW_<idx>_OPEN_OPTIONS=<key1=value1>[,key2=value2]...`` where idx " +"is an integer index starting at 0." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:205 +msgid "Open options(s) to use to open ``OVERVIEW_<idx>_DATASET``." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:207 +msgid "" +"``OVERVIEW_<idx>_LAYER=<string>`` where idx is an integer index starting " +"at 0." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:209 +msgid "" +"Name of the vector layer to use as the first overview level, assuming " +"``OVERVIEW_<idx>_DATASET`` points to a vector dataset. " +"``OVERVIEW_<idx>_DATASET`` may also not be specified, in which case the " +"vector dataset of the full resolution virtual mosaic is used." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:214 +msgid "" +"``OVERVIEW_<idx>_FACTOR=<int>`` where idx is an integer index starting at" +" 0." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:216 +msgid "" +"Sub-sampling factor, strictly greater than 1. If " +"``OVERVIEW_<idx>_DATASET`` and ``OVERVIEW_<idx>_LAYER`` are not " +"specified, then all tiles of the full resolution virtual mosaic are used," +" with the specified sub-sampling factor (it is recommended, but not " +"required, that those tiles do have a corresponding overview). " +"``OVERVIEW_<idx>_DATASET`` and/or ``OVERVIEW_<idx>_LAYER`` may also be " +"specified to point to another tile index." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:223 +msgid "" +"All overviews *must* have exactly the same extent as the full resolution " +"virtual mosaic. The GTI driver does not check that, and if that condition" +" is not met, subsampled pixel request will lead to incorrect result." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:227 +msgid "" +"In addition to those layer metadata items, the dataset-level metadata " +"item ``TILE_INDEX_LAYER`` may be set to indicate, for dataset with " +"multiple layers, which one should be used as the tile index layer." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:231 +msgid "" +"Alternatively to setting those metadata items individually, the " +"corresponding information can be grouped together in a GTI XML document, " +"attached in the ``xml:GTI`` metadata domain of the layer (for drivers " +"that support alternate metadata domains such as GeoPackage)" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:237 +msgid "GTI XML format" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:239 +msgid "" +"A `XML schema of the GDAL GTI format " +"<https://raw.githubusercontent.com/OSGeo/gdal/master/data/gdaltileindex.xsd>`_" +" is available." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:242 +msgid "" +"The following artificial example contains all potential elements and " +"attributes. A number of them have similar name and same semantics as " +"layer metadata items mentioned in the previous section." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:334 +msgid "At the GDALTileIndexDataset level, the elements specific to GTI XML are:" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:336 +msgid "" +"``Filter``: value of a SQL WHERE clause, used to select a subset of the " +"features of the index." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:339 +msgid "" +"``BlockXSize`` / ``BlockYSize``: dimension of the block size of bands. " +"Defaults to 256x256" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:342 +msgid "" +"``Metadata``: defines dataset-level metadata. You can refer to the " +"documentation of the :ref:`VRT <raster.vrt>` driver for its syntax." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:345 +msgid "" +"At the Band level, the elements specific to GTI XML are: Description, " +"Offset, Scale, UnitType, ColorTable, CategoryNames, " +"GDALRasterAttributeTable, Metadata. You can refer to the documentation of" +" the :ref:`VRT <raster.vrt>` driver for their syntax and semantics." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:353 +msgid "How to build a GTI comptatible index ?" +msgstr "" + +#: ../../source/drivers/raster/gti.rst:355 +msgid "" +"The :ref:`gdaltindex` program may be used to generate both a vector tile " +"index, and optionally a wrapping .gti XML file." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:358 +msgid "" +"A GTI comptatible index may also be created by any programmatic means, " +"provided the above format specifications are met." +msgstr "" + +#: ../../source/drivers/raster/gti.rst:365 +msgid "" +"|about-open-options| The following open options are available. Most of " +"them can be also defined as layer metadata items or in the .gti XML file" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:5 +msgid "GTiff -- GeoTIFF File Format" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:7 +msgid "GTiff" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:11 +msgid "" +"Most forms of TIFF and GeoTIFF files are supported by GDAL for reading, " +"and somewhat less varieties can be written." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:14 +msgid "" +"GDAL also supports reading and writing BigTIFF files (evolution of the " +"TIFF format to support files larger than 4 GB)." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:17 +msgid "" +"Currently band types of Byte, UInt16, Int16, UInt32, Int32, Float32, " +"Float64, CInt16, CInt32, CFloat32 and CFloat64 are supported for reading " +"and writing. Paletted images will return palette information associated " +"with the band. The compression formats listed below should be supported " +"for reading as well." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:23 +msgid "" +"As well, one bit files, and some other unusual formulations of GeoTIFF " +"file, such as YCbCr color model files, are automatically translated into " +"RGBA (red, green, blue, alpha) form, and treated as four eight bit bands." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:42 +msgid "" +"Most GeoTIFF projections should be supported, with the caveat that in " +"order to translate uncommon Projected, and Geographic coordinate systems " +"into OGC WKT it is necessary to have the PROJ proj.db database available." +" It must be found at the location pointed to by the PROJ_LIB environment " +"variable, or at one of the locations set programmatically via " +"OSRSetPROJSearchPaths()." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:49 +msgid "" +"Georeferencing from GeoTIFF is supported in the form of one tiepoint and " +"pixel size, a transformation matrix, or a list of GCPs." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:52 +msgid "" +"If no georeferencing information is available in the TIFF file itself, " +"GDAL will also check for, and use an ESRI :ref:`world file <raster.wld>` " +"with the extension .tfw, .tifw/.tiffw or .wld, as well as a MapInfo .tab " +"file." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:57 +msgid "" +"By default, information is fetched in following order (first listed is " +"the highest priority): PAM (Persistent Auxiliary metadata) .aux.xml " +"sidecar file, INTERNAL (GeoTIFF keys and tags), TABFILE (.tab), WORLDFILE" +" (.tfw, .tifw/.tiffw or .wld), XML (.xml)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:62 +msgid "" +"Starting with GDAL 2.2, the allowed sources and their priority order can " +"be changed with the :config:`GDAL_GEOREF_SOURCES` configuration option " +"(or :oo:`GEOREF_SOURCES` open option) whose value is a comma-separated " +"list of the following keywords : PAM, INTERNAL, TABFILE, WORLDFILE, XML " +"(added in 3.7), NONE. Earlier mentioned sources take priority over later " +"ones. A non mentioned source will be ignored." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:69 +msgid "" +"For example setting it to \"WORLDFILE,PAM,INTERNAL\" will make a " +"geotransformation matrix from a potential worldfile priority over PAM or " +"GeoTIFF." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:73 +msgid "" +"Minimum support for extracting the CRS from ESRI .xml side car files has " +"been added in GDAL 3.7, using the " +"metadata.refSysInfo.RefSystem.refSysID.identCode.code CRS code." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:77 +msgid "" +"GDAL can read and write the *RPCCoefficientTag* as described in the `RPCs" +" in GeoTIFF <http://geotiff.maptools.org/rpc_prop.html>`__ proposed " +"extension. The tag is written only for files created with the default " +"profile GDALGeoTIFF. For other profiles, a .RPB file is created. In GDAL " +"data model, the RPC coefficients are stored into the RPC metadata domain." +" For more details, see the :ref:`rfc-22`. If .RPB or \\_RPC.TXT files are" +" found, they will be used to read the RPCs, even if the " +"*RPCCoefficientTag* tag is set." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:87 +msgid "Internal nodata masks" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:89 +msgid "" +"TIFF files can contain internal transparency masks. The GeoTIFF driver " +"recognizes an internal directory as being a transparency mask when the " +"FILETYPE_MASK bit value is set on the TIFFTAG_SUBFILETYPE tag. According " +"to the TIFF specification, such internal transparency masks contain 1 " +"sample of 1-bit data. Although the TIFF specification allows for higher " +"resolutions for the internal transparency mask, the GeoTIFF driver only " +"supports internal transparency masks of the same dimensions as the main " +"image. Transparency masks of internal overviews are also supported." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:98 +msgid "" +"When the :config:`GDAL_TIFF_INTERNAL_MASK` configuration option is set to" +" YES (which is the case starting with GDAL 3.9 when CreateMaskBand() is " +"invoked on the dataset, or when it is invoked on a raster band with the " +"GMF_PER_DATASET flag), and the GeoTIFF file is opened in update mode, the" +" CreateMaskBand() method on a TIFF dataset or rasterband will create an " +"internal transparency mask. Otherwise, the default behavior of nodata " +"mask creation will be used, that is to say the creation of a .msk file, " +"as per :ref:`rfc-15`." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:106 +msgid "" +"1-bit internal mask band are deflate compressed. When reading them back, " +"to make conversion between mask band and alpha band easier, mask bands " +"are exposed to the user as being promoted to full 8 bits (i.e. the value " +"for unmasked pixels is 255) unless the " +":config:`GDAL_TIFF_INTERNAL_MASK_TO_8BIT` configuration option is set to " +"NO. This does not affect the way the mask band is written (it is always " +"1-bit)." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:116 +msgid "" +"The GeoTIFF driver supports reading, creation and update of internal " +"overviews. Internal overviews can be created on GeoTIFF files opened in " +"update mode (with gdaladdo for instance). If the GeoTIFF file is opened " +"as read only, the creation of overviews will be done in an external .ovr " +"file. Overview are only updated on request with the BuildOverviews() " +"method." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:123 +msgid "" +"The block size (tile width and height) used for overviews (internal or " +"external) can be specified by setting the GDAL_TIFF_OVR_BLOCKSIZE " +"environment variable to a power-of-two value between 64 and 4096. The " +"default is 128, or starting with GDAL 3.1 to use the same block size as " +"the full-resolution dataset if possible (i.e. block height and width are " +"equal, a power-of-two, and between 64 and 4096)." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:131 +msgid "Overviews and nodata masks" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:133 +msgid "" +"The following configurations can be encountered depending if overviews " +"and nodata masks are internal or not." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:136 +msgid "" +"Internal overviews, internal nodata mask: If a GeoTIFF file has a " +"internal transparency mask and the GeoTIFF file is opened in update mode," +" BuildOverviews() will automatically create overviews for the internal " +"transparency mask." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:140 +msgid "" +"External overviews, external nodata mask: When opened in read-only mode, " +"BuildOverviews() will automatically create overviews for the external " +"transparency mask (in a .msk.ovr file)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:143 +msgid "" +"Internal overviews, external nodata mask: when running BuildOverviews() " +"in update mode on the .tif file, starting with GDAL 3.9, overviews of the" +" main bands and of the external .msk will be generated ( as internal " +"overview of the .msk). Prior to GDAL 3.9, only the overviews of the main " +"bands are generated. Overviews of the external .msk file had to be " +"explicitly generated by running BuildOverviews() on the .msk." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:151 +msgid "For the remaining configuration, behavior is less obvious:" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:153 +msgid "" +"External overviews, internal nodata mask: when running BuildOverviews() " +"in read-only mode on the .tif file, only the overviews of the main bands " +"will be generated. Generating the overviews of the internal nodata mask " +"is not currently supported by the driver." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:159 +msgid "" +"Practical note: for a command line point of view, BuildOverview() in " +"update mode means \"gdaladdo the.tiff\" (without -ro). Whereas " +"BuildOverviews() in read-only mode means \"gdaladdo -ro the.tiff\"." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:166 +msgid "" +"GDAL can deal with the following baseline TIFF tags as dataset-level " +"metadata :" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:169 +msgid "TIFFTAG_DOCUMENTNAME" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:170 +msgid "TIFFTAG_IMAGEDESCRIPTION" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:171 +msgid "TIFFTAG_SOFTWARE" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:172 +msgid "TIFFTAG_DATETIME" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:173 +msgid "TIFFTAG_ARTIST" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:174 +msgid "TIFFTAG_HOSTCOMPUTER" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:175 +msgid "TIFFTAG_COPYRIGHT" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:176 +msgid "TIFFTAG_XRESOLUTION" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:177 +msgid "TIFFTAG_YRESOLUTION" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:178 +msgid "TIFFTAG_RESOLUTIONUNIT" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:179 +msgid "TIFFTAG_MINSAMPLEVALUE (read only)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:180 +msgid "TIFFTAG_MAXSAMPLEVALUE (read only)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:181 +msgid "" +"`GEO_METADATA " +"<https://www.awaresystems.be/imaging/tiff/tifftags/geo_metadata.html>`__:" +" This tag may be used for embedding XML-encoded instance documents " +"prepared using 19139-based schema (GeoTIFF DGIWG) (GDAL >= 2.3)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:184 +msgid "" +"`TIFF_RSID " +"<https://www.awaresystems.be/imaging/tiff/tifftags/tiff_rsid.html>`__: " +"This tag specifies a File Universal Unique Identifier, or RSID, according" +" to DMF definition (GeoTIFF DGIWG) (GDAL >= 2.3)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:188 +msgid "" +"The name of the metadata item to use is one of the above names " +"(\"TIFFTAG_DOCUMENTNAME\", ...). On creation, those tags can for example " +"be set with" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:196 +msgid "" +"Other non standard metadata items can be stored in a TIFF file created " +"with the profile GDALGeoTIFF (the default, see below in the Creation " +"issues section). Those metadata items are grouped together into a XML " +"string stored in the non standard TIFFTAG_GDAL_METADATA ASCII tag (code " +"42112). When BASELINE or GeoTIFF profile are used, those non standard " +"metadata items are stored into a PAM .aux.xml file." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:203 +msgid "" +"The value of GDALMD_AREA_OR_POINT (\"AREA_OR_POINT\") metadata item is " +"stored in the GeoTIFF key RasterPixelIsPoint for GDALGeoTIFF or GeoTIFF " +"profiles." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:207 +msgid "" +"XMP metadata can be extracted from the file, and will be reported as XML " +"raw content in the xml:XMP metadata domain." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:210 +msgid "" +"EXIF metadata can be extracted from the file, and will be reported in the" +" EXIF metadata domain." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:214 +#: ../../source/drivers/raster/jpeg.rst:76 +#: ../../source/drivers/raster/jpegxl.rst:45 +#: ../../source/drivers/raster/png.rst:49 +msgid "Color Profile Metadata" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:216 +#: ../../source/drivers/raster/jpeg.rst:78 +#: ../../source/drivers/raster/jpegxl.rst:47 +#: ../../source/drivers/raster/png.rst:51 +msgid "" +"GDAL can deal with the following color profile metadata in the " +"COLOR_PROFILE domain:" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:219 +#: ../../source/drivers/raster/png.rst:54 +msgid "" +"SOURCE_ICC_PROFILE (Base64 encoded ICC profile embedded in file. If " +"available, other tags are ignored.)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:221 +#: ../../source/drivers/raster/png.rst:58 +msgid "SOURCE_PRIMARIES_RED (xyY in \"x,y,1\" format for red primary.)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:222 +#: ../../source/drivers/raster/png.rst:59 +msgid "SOURCE_PRIMARIES_GREEN (xyY in \"x,y,1\" format for green primary)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:223 +#: ../../source/drivers/raster/png.rst:60 +msgid "SOURCE_PRIMARIES_BLUE (xyY in \"x,y,1\" format for blue primary)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:224 +#: ../../source/drivers/raster/png.rst:61 +msgid "SOURCE_WHITEPOINT (xyY in \"x,y,1\" format for whitepoint)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:225 +msgid "TIFFTAG_TRANSFERFUNCTION_RED (Red table of TIFFTAG_TRANSFERFUNCTION)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:226 +msgid "TIFFTAG_TRANSFERFUNCTION_GREEN (Green table of TIFFTAG_TRANSFERFUNCTION)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:228 +msgid "TIFFTAG_TRANSFERFUNCTION_BLUE (Blue table of TIFFTAG_TRANSFERFUNCTION)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:230 +msgid "TIFFTAG_TRANSFERRANGE_BLACK (Min range of TIFFTAG_TRANSFERRANGE)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:231 +msgid "TIFFTAG_TRANSFERRANGE_WHITE (Max range of TIFFTAG_TRANSFERRANGE)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:233 +#: ../../source/drivers/raster/png.rst:64 +msgid "" +"Note that these metadata properties can only be used on the original raw " +"pixel data. If automatic conversion to RGB has been done, the color " +"profile information cannot be used." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:237 +msgid "All these metadata tags can be overridden and/or used as creation options." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:243 +msgid "" +"GDAL stores band nodata value in the non standard TIFFTAG_GDAL_NODATA " +"ASCII tag (code 42113) for files created with the default profile " +"GDALGeoTIFF. Note that all bands must use the same nodata value. When " +"BASELINE or GeoTIFF profile are used, the nodata value is stored into a " +"PAM .aux.xml file." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:250 +msgid "Sparse files" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:252 +msgid "" +"GDAL makes a special interpretation of a TIFF tile or strip whose offset " +"and byte count are set to 0, that is to say a tile or strip that has no " +"corresponding allocated physical storage. On reading, such tiles or " +"strips are considered to be implicitly set to 0 or to the nodata value " +"when it is defined. On writing, it is possible to enable generating such " +"files through the Create() interface by setting the :co:`SPARSE_OK` " +"creation option to YES. Then, blocks that are never written through the " +"IWriteBlock()/IRasterIO() interfaces will have their offset and byte " +"count set to 0. This is particularly useful to save disk space and time " +"when the file must be initialized empty before being passed to a further " +"processing stage that will fill it. To avoid ambiguities with another " +"sparse mechanism discussed in the next paragraphs, we will call such " +"files with implicit tiles/strips \"TIFF sparse files\". They will be " +"likely **not** interoperable with TIFF readers that are not GDAL based " +"and would consider such files with implicit tiles/strips as defective." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:268 +msgid "" +"Starting with GDAL 2.2, this mechanism is extended to the CreateCopy() " +"and Open() interfaces (for update mode) as well. If the :co:`SPARSE_OK` " +"creation option (or the :oo:`SPARSE_OK` open option for Open()) is set to" +" YES, even an attempt to write a all 0/nodata block will be detected so " +"that the tile/strip is not allocated (if it was already allocated, then " +"its content will be replaced by the 0/nodata content)." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:275 +msgid "" +"Starting with GDAL 2.2, in the case where :co:`SPARSE_OK` is **not** " +"defined (or set to its default value FALSE), for uncompressed files whose" +" nodata value is not set, or set to 0, in Create() and CreateCopy() mode," +" the driver will delay the allocation of 0-blocks until file closing, so " +"as to be able to write them at the very end of the file, and in a way " +"compatible of the filesystem sparse file mechanisms (to be distinguished " +"from the TIFF sparse file extension discussed earlier). That is that all " +"the empty blocks will be seen as properly allocated from the TIFF point " +"of view (corresponding strips/tiles will have valid offsets and byte " +"counts), but will have no corresponding physical storage. Provided that " +"the filesystem supports such sparse files, which is the case for most " +"Linux popular filesystems (ext2/3/4, xfs, btfs, ...) or NTFS on Windows. " +"If the file system does not support sparse files, physical storage will " +"be allocated and filled with zeros." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:291 +msgid "Raw mode" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:293 +msgid "" +"For some TIFF formulations that have \"odd\" photometric color spaces, " +"on-the-fly decoding as RGBA is done. This might not be desirable in some " +"use cases. This behavior can be disabled by prefixing the filename with " +"GTIFF_RAW:" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:298 +msgid "For example to translate a CMYK file to another one :" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:307 +#: ../../source/drivers/raster/xyz.rst:53 +#: ../../source/drivers/vector/geojson.rst:187 +msgid "|about-open-options| This driver supports the following open options:" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:-1 +msgid "" +"NUM_THREADS=[<number_of_threads>/ALL_CPUS]: Enable multi-threaded " +"compression by specifying the number of worker threads. Worth it for slow" +" compression algorithms such as DEFLATE or LZMA. Default is compression " +"in the main thread. Starting with GDAL 3.6, this option also enables " +"multi-threaded decoding when RasterIO() requests intersect several " +"tiles/strips. The GDAL_NUM_THREADS configuration option can also be used " +"as an alternative to setting the open option." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:-1 +msgid "" +"GEOREF_SOURCES=comma-separated list with one or several of PAM, INTERNAL," +" TABFILE, WORLDFILE or XML (XML added in 3.7): Define which " +"georeferencing sources are allowed and their priority order. See " +"Georeferencing paragraph." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:-1 +msgid "" +"SPARSE_OK=[TRUE/FALSE]: Defaults to FALSE. Should empty blocks be " +"omitted on disk? When this option is set, any attempt of writing a block " +"whose all pixels are 0 or the nodata value will cause it not to be " +"written at all (unless there is a corresponding block already allocated " +"in the file). Sparse files have 0 tile/strip offsets for blocks never " +"written and save space; however, most non-GDAL packages cannot read such " +"files." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:344 +msgid "" +"**IGNORE_COG_LAYOUT_BREAK=YES/NO** (GDAL >= 3.8): Updating a COG (Cloud " +"Optimized GeoTIFF) file generally breaks part of the optimizations, but " +"still produces a valid GeoTIFF file. Starting with GDAL 3.8, to avoid " +"undesired loss of the COG characteristics, opening such a file in update " +"mode will be rejected, unless this option is also set to YES (default is " +"NO). This option has only effect on COG files and when opening in update " +"mode, and is ignored on regular (Geo)TIFF files." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:356 +msgid "" +"GeoTIFF files can be created with any GDAL defined band type, including " +"the complex types. Created files may have any number of bands. Files of " +"type Byte with exactly 3 bands will be given a photometric interpretation" +" of RGB, files of type Byte with exactly four bands will have a " +"photometric interpretation of RGBA, while all other combinations will " +"have a photometric interpretation of MIN_IS_BLACK. Starting with GDAL " +"2.2, non-standard (regarding to the intrinsics TIFF capabilities) band " +"color interpretation, such as BGR ordering, will be handled in creation " +"and reading, by storing them in the GDAL internal metadata TIFF tag." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:367 +msgid "" +"The TIFF format only supports R,G,B components for palettes / color " +"tables. Thus on writing the alpha information will be silently discarded." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:371 +msgid "" +"You may want to read hints to `generate and read cloud optimized GeoTIFF " +"files <https://trac.osgeo.org/gdal/wiki/CloudOptimizedGeoTIFF>`__" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:377 +msgid "" +"|about-creation-options| This driver supports the following creation " +"options:" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:449 +msgid "" +"``JPEG`` should generally only be used with Byte data (8 bit per " +"channel). Better compression for RGB images can be obtained by using the " +"PHOTOMETRIC=YCBCR colorspace with a 4:2:2 subsampling of the Y,Cb,Cr " +"components." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:453 +msgid "" +"Starting with GDAL 3.4, if GDAL is built with its internal libtiff, read " +"and write support for JPEG-in-TIFF compressed images with 12-bit sample " +"is enabled by default (if JPEG support is also enabled), using GDAL " +"internal libjpeg (based on IJG libjpeg-6b, with additional changes for " +"12-bit sample support). Support for JPEG with 12-bit sample is " +"independent of whether 8-bit JPEG support is enabled through internal IJG" +" libjpeg-6b or external libjpeg (like libjpeg-turbo)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:461 +msgid "" +"``CCITTFAX3``, ``CCITTFAX4`` or ``CCITRLE`` compression should only be " +"used with 1bit (NBITS=1) data" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:465 +msgid "" +"``ZSTD`` is available since GDAL 2.3 when using internal libtiff and if " +"GDAL built against libzstd >=1.0, or if built against external libtiff " +"with zstd support." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:468 +msgid "" +"``LERC`` and ``LERC_DEFLATE`` are available only when using internal " +"libtiff for GDAL < 3.3.0. Since GDAL 3.3.0, LERC compression is also " +"available when building GDAL against external libtiff >= 4.3.0, built " +"itself against https://github.com/esri/lerc" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:474 +msgid "" +"``JXL`` is for JPEG-XL, and is only available when using internal libtiff" +" and building GDAL against https://github.com/libjxl/libjxl . Supported " +"data types are ``Byte``, ``UInt16`` and ``Float32`` only. For GDAL < " +"3.6.0, JXL compression may only be used alongside ``INTERLEAVE=PIXEL`` " +"(the default) on datasets with 4 bands or less." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:479 +msgid "``NONE`` is the default." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:527 +#: ../../source/drivers/raster/jpeg.rst:180 +msgid "" +"Low values result in higher compression ratios, but poorer image quality " +"with strong blocking artifacts. Values above 95 are not meaningfully " +"better quality but can be substantially larger." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:540 +msgid "" +"0: JpegTables is not written. Each strip/tile contains its own " +"quantization tables and use optimized Huffman coding." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:542 +msgid "" +"1: JpegTables is written with only the quantization tables. Each " +"strip/tile refers to those quantized tables and use optimized Huffman " +"coding. This is generally the optimal choice for smallest file size, and " +"consequently is the default." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:546 +msgid "" +"2: JpegTables is written with only the default Huffman tables. Each " +"strip/tile refers to those Huffman tables (thus no optimized Huffman " +"coding) and contains its own quantization tables (identical). This option" +" has no anticipated practical value." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:550 +msgid "" +"3: JpegTables is written with the quantization and default Huffman " +"tables. Each strip/tile refers to those tables (thus no optimized Huffman" +" coding). This option could perhaps with some data be more efficient than" +" 1, but this should only occur in rare circumstances." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:673 +msgid "" +"With ``GDALGeoTIFF`` (the default) various GDAL custom tags may be " +"written." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:675 +msgid "With ``GeoTIFF`` only GeoTIFF tags will be added to the baseline." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:676 +msgid "" +"With ``BASELINE`` no GDAL or GeoTIFF tags will be written. BASELINE is " +"occasionally useful when writing files to be read by applications " +"intolerant of unrecognized tags." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:691 +msgid "" +"``IF_SAFER`` will create BigTIFF if the resulting file \\*might\\* exceed" +" 4GB. Note: this is only a heuristic that might not always work depending" +" on compression ratios." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:695 +msgid "" +"BigTIFF is a TIFF variant which can contain more than 4GiB of data (size " +"of classic TIFF is limited by that value). This option is available if " +"GDAL is built with libtiff library version 4.0 or higher." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:700 +msgid "" +"When creating a new GeoTIFF with no compression, GDAL computes in advance" +" the size of the resulting file. If that computed file size is over 4GiB," +" GDAL will automatically decide to create a BigTIFF file. However, when " +"compression is used, it is not possible in advance to known the final " +"size of the file, so classical TIFF will be chosen. In that case, the " +"user must explicitly require the creation of a BigTIFF with " +":co:`BIGTIFF=YES` if the final file is anticipated to be too big for " +"classical TIFF format. If BigTIFF creation is not explicitly asked or " +"guessed and the resulting file is too big for classical TIFF, libtiff " +"will fail with an error message like \"TIFFAppendToStrip:Maximum TIFF " +"file size exceeded\"." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:779 +msgid "" +"Multi-page TIFF files are exposed as subdatasets. On opening, a " +"subdataset name is GTIFF_DIR:{index}:filename.tif, where {index} starts " +"at 1." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:783 +msgid "" +"Starting with GDAL 3.0, subdataset creation is possible by using the " +"APPEND_SUBDATASET=YES creation option. The filename passed to Create() / " +"CreateCopy() should be the regular filename (not with GTIFF_DIR: syntax. " +"Creating overviews on a multi-page TIFF is not supported." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:788 +msgid "" +"Starting with GDAL 3.2, read-only access to subdataset overviews and " +"masks is possible provided that they are referenced by their parent IFD " +"through the `TIFFTAG_SUBIFD " +"<https://www.awaresystems.be/imaging/tiff/tifftags/subifds.html>`__ tag." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:793 +msgid "About JPEG compression of RGB images" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:795 +msgid "" +"When translating a RGB image to JPEG-In-TIFF, using PHOTOMETRIC=YCBCR can" +" make the size of the image typically 2 to 3 times smaller than the " +"default photometric value (RGB). When using PHOTOMETRIC=YCBCR, the " +"INTERLEAVE option must be kept to its default value (PIXEL), otherwise " +"libtiff will fail to compress the data." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:801 +msgid "" +"Note also that the dimensions of the tiles or strips must be a multiple " +"of 8 for PHOTOMETRIC=RGB or 16 for PHOTOMETRIC=YCBCR" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:805 +msgid "Lossless conversion of JPEG into JPEG-in-TIFF" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:807 +msgid "" +"The conversion of a JPEG file (but *not* a JPEG-in-TIFF file) to a JPEG-" +"in-TIFF file without decompression and compression cycles, and thus " +"without any additional quality loss, can be done with gdal_translate (or " +"the CreateCopy() API), if all the following conditions are met:" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:812 +msgid "" +"the source dataset is a JPEG file (or a VRT with a JPEG as a single " +"SimpleSource)" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:813 +msgid "the target dataset is a JPEG-in-TIFF file" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:814 +msgid "no explicitly target JPEG quality is specified" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:815 +msgid "no change in colorspace is specified" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:816 +msgid "no sub-windowing is requested" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:817 +msgid "and more generally, no change that alters pixel values" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:819 +msgid "" +"The generation of a tiled JPEG-in-TIFF from the original JPEG image is " +"possible. Explicit assignment of target SRS and bounds are also possible." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:822 +msgid "So, the following commands will use the lossless copy method :" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:833 +msgid "" +"whereas the following commands will *not* (and thus cause JPEG " +"decompression and compression):" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:844 +msgid "Streaming operations" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:846 +msgid "" +"The GeoTIFF driver can support reading or writing TIFF files (with some " +"restrictions detailed below) in a streaming compatible way." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:850 +msgid "" +"When reading a file from /vsistdin/, a named pipe (on Unix), or if " +"forcing streamed reading by setting the :config:`TIFF_READ_STREAMING` " +"configuration option to YES, the GeoTIFF driver will assume that the TIFF" +" Image File Directory (IFD) is at the beginning of the file, i.e. at " +"offset 8 for a classical TIFF file or at offset 16 for a BigTIFF file. " +"The values of the tags of array type must be contained at the beginning " +"of file, after the end of the IFD and before the first image strip/tile. " +"The reader must read the strips/tiles in the order they are written in " +"the file. For a pixel interleaved file (PlanarConfiguration=Contig), the " +"recommended order for a writer, and thus for a reader, is from top to " +"bottom for a strip-organized file or from top to bottom, which a chunk of" +" a block height, and left to right for a tile-organized file. For a band " +"organized file (PlanarConfiguration=Separate), the above order is " +"recommended with the content of the first band, then the content of the " +"second band, etc... Technically this order corresponds to increasing " +"offsets in the TileOffsets/StripOffsets tag. This is the order that the " +"GDAL raster copy routine will assume." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:868 +msgid "" +"If the order is not the one described above, the UNORDERED_BLOCKS=YES " +"dataset metadata item will be set in the TIFF metadata domain. Each block" +" offset can be determined by querying the " +"\"BLOCK_OFFSET_[xblock]_[yblock]\" band metadata items in the TIFF " +"metadata domain (where xblock, yblock is the coordinate of the block), " +"and a reader could use that information to determine the appropriate " +"reading order for image blocks." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:876 +msgid "" +"The files that are streamed into the GeoTIFF driver may be compressed, " +"even if the GeoTIFF driver cannot produce such files in streamable output" +" mode (regular creation of TIFF files will produce such compatible files " +"for streamed reading)." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:881 +msgid "" +"When writing a file to /vsistdout/, a named pipe (on Unix), or when " +"defining the :co:`STREAMABLE_OUTPUT=YES` creation option, the " +"CreateCopy() method of the GeoTIFF driver will generate a file with the " +"above defined constraints (related to position of IFD and block order), " +"and this is only supported for a uncompressed file. The Create() method " +"also supports creating streamable compatible files, but the writer must " +"be careful to set the projection, geotransform or metadata before writing" +" image blocks (so that the IFD is written at the beginning of the file). " +"And when writing image blocks, the order of blocks must be the one of the" +" above paragraph, otherwise errors will be reported." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:892 +msgid "Some examples :" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:906 +msgid "" +"Note: not all utilities are compatible with such input or output " +"streaming operations, and even those which may deal with such files may " +"not manage to deal with them in all circumstances, for example if the " +"reading driver driven by the output file is not compatible with the block" +" order of the streamed input." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:915 +msgid "" +"|about-config-options| This paragraph lists the configuration options " +"that can be set to alter the default behavior of the GTiff driver." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1012 +msgid "" +":config:`USE_RRD`: Can be set to TRUE to force external overviews in the " +"RRD format." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1097 +msgid "" +":config:`GDAL_NUM_THREADS` enables multi-threaded compression by " +"specifying the number of worker threads. Worth it for slow compression " +"algorithms such as DEFLATE or LZMA. Will be ignored for JPEG. Default is " +"compression in the main thread. Note: this configuration option also " +"apply to other parts to GDAL (warping, gridding, ...). Starting with GDAL" +" 3.6, this option also enables multi-threaded decoding when RasterIO() " +"requests intersect several tiles/strips." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1156 +msgid "Codec Recommendations" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1160 +msgid "LZW" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1162 +msgid "If you don't know what to choose, choose this one." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1165 +msgid "DEFLATE" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1167 +msgid "" +"The most commonly supported TIFF codec, especially with older non-geo " +"software." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1170 +msgid "LERC" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1172 +msgid "" +"Used for storing quantized floating point data. " +"https://github.com/esri/lerc" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1176 +msgid "ZSTD" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1178 +msgid "Smaller and faster than DEFLATE, but not as commonly supported." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1183 +msgid "A smaller and faster JPEG." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1186 +msgid "JXL" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1188 +msgid "Next-gen JPG from the JPG group." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1192 +msgid "LZMA" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1194 +msgid "Slow but storage efficient." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1197 +msgid "CCITTRLE/CCITTFAX3/CCITTFAX4" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1199 +msgid "Did you happen to have fax files from the 1990s? Use these." +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1204 +msgid "`GeoTIFF Information Page <https://trac.osgeo.org/geotiff>`__" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1205 +msgid "`libtiff Page <http://www.simplesystems.org/libtiff/>`__" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1206 +msgid "" +"`Details on BigTIFF file format " +"<http://www.awaresystems.be/imaging/tiff/bigtiff.html>`__" +msgstr "" + +#: ../../source/drivers/raster/gtiff.rst:1208 +msgid ":ref:`raster.cog` driver" +msgstr "" + +#: ../../source/drivers/raster/gxf.rst:5 +msgid "GXF -- Grid eXchange File" +msgstr "" + +#: ../../source/drivers/raster/gxf.rst:7 +msgid "GXF" +msgstr "" + +#: ../../source/drivers/raster/gxf.rst:11 +msgid "" +"This is a raster exchange format propagated by Geosoft, and made a " +"standard in the gravity/magnetics field. GDAL supports reading (but not " +"writing) GXF-3 files, including support for georeferencing information, " +"and projections." +msgstr "" + +#: ../../source/drivers/raster/gxf.rst:16 +msgid "" +"By default, the datatype returned for GXF datasets by GDAL is Float32. " +"You can specify the datatype by setting the GXF_DATATYPE configuration " +"option (Float64 supported currently)" +msgstr "" + +#: ../../source/drivers/raster/gxf.rst:20 +msgid "" +"Details on the supporting code, and format can be found on the `GXF-3 " +"<https://web.archive.org/web/20130730111701/http://home.gdal.org/projects/gxf/index.html>`__" +" page." +msgstr "" + +#: ../../source/drivers/raster/gxf.rst:23 +msgid "NOTE: Implemented as :source_file:`frmts/gxf/gxfdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:5 +msgid "HDF4 -- Hierarchical Data Format Release 4 (HDF4)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:7 +msgid "HDF4" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:9 +msgid "HDF4Image" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:13 +msgid "" +"There are two HDF formats, HDF4 (4.x and previous releases) and HDF5. " +"These formats are completely different and NOT compatible. This driver " +"intended for HDF4 file formats importing. NASA's Earth Observing System " +"(EOS) maintains its own HDF modification called HDF-EOS. This " +"modification is suited for use with remote sensing data and fully " +"compatible with underlying HDF. This driver can import HDF4-EOS files. " +"Currently EOS use HDF4-EOS for data storing (telemetry from \"Terra\" and" +" \"Aqua\" satellites). In the future they will switch to HDF5-EOS format," +" which will be used for telemetry from \"Aura\" satellite." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:33 +#: ../../source/drivers/raster/hdf5.rst:29 +#: ../../source/drivers/raster/netcdf.rst:31 +msgid "Multiple Image Handling (Subdatasets)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:35 +msgid "" +"Hierarchical Data Format is a container for several different datasets. " +"For data storing Scientific Datasets (SDS) used most often. SDS is a " +"multidimensional array filled by data. One HDF file may contain several " +"different SDS arrays. They may differ in size, number of dimensions and " +"may represent data for different regions." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:41 +msgid "" +"If the file contains only one SDS that appears to be an image, it may be " +"accessed normally, but if it contains multiple images it may be necessary" +" to import the file via a two step process. The first step is to get a " +"report of the components images (SDS arrays) in the file using " +"**gdalinfo**, and then to import the desired images using gdal_translate." +" The **gdalinfo** utility lists all multidimensional subdatasets from the" +" input HDF file. The name of individual images (subdatasets) are assigned" +" to the **SUBDATASET_n_NAME** metadata item. The description for each " +"image is found in the **SUBDATASET_n_DESC** metadata item. For HDF4 " +"images the subdataset names will be formatted like this:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:53 +msgid "*HDF4_SDS:subdataset_type:file_name:subdataset_index*" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:55 +msgid "" +"where *subdataset_type* shows predefined names for some of the well known" +" HDF datasets, *file_name* is the name of the input file, and " +"*subdataset_index* is the index of the image to use (for internal use in " +"GDAL)." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:60 +#: ../../source/drivers/raster/hdf5.rst:58 +msgid "" +"On the second step you should provide this name for **gdalinfo** or " +"**gdal_translate** for actual reading of the data." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:63 +msgid "For example, we want to read data from the MODIS Level 1B dataset:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:78 +msgid "...a lot of metadata output skipped..." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:124 +msgid "" +"Now select one of the subdatasets, described as ``[12x2040x1354] " +"EV_1KM_RefSB (16-bit unsigned integer)``:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:136 +msgid "...metadata skipped..." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:159 +msgid "" +"Or you may use **gdal_translate** for reading image bands from this " +"dataset." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:162 +msgid "" +"Note that you should provide exactly the contents of the line marked " +"**SUBDATASET_n_NAME** to GDAL, including the **HDF4_SDS:** prefix." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:165 +msgid "" +"This driver is intended only for importing remote sensing and geospatial " +"datasets in form of raster images. If you want explore all data contained" +" in HDF file you should use another tools (you can find information about" +" different HDF tools using links at end of this page)." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:173 +#: ../../source/drivers/raster/hdf5.rst:199 +msgid "" +"There is no universal way of storing georeferencing in HDF files. " +"However, some product types have mechanisms for saving georeferencing, " +"and some of these are supported by GDAL. Currently supported are " +"(*subdataset_type* shown in parenthesis):" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:178 +msgid "HDF4 files created by GDAL (**GDAL_HDF4**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:179 +msgid "ASTER Level 1A (**ASTER_L1A**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:180 +msgid "ASTER Level 1B (**ASTER_L1B**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:181 +msgid "ASTER Level 2 (**ASTER_L2**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:182 +msgid "ASTER DEM (**AST14DEM**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:183 +msgid "MODIS Level 1B Earth View products (**MODIS_L1B**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:184 +msgid "MODIS Level 3 products (**MODIS_L3**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:185 +msgid "SeaWiFS Level 3 Standard Mapped Image Products (**SEAWIFS_L3**)" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:187 +msgid "" +"By default the hdf4 driver only reads the gcps from every 10th row and " +"column from EOS_SWATH datasets. You can change this behavior by setting " +"the GEOL_AS_GCPS environment variable to PARTIAL (default), NONE, or " +"FULL." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:195 +msgid "" +"This driver supports creation of the HDF4 Scientific Datasets. You may " +"create set of 2D datasets (one per each input band) or single 3D dataset " +"where the third dimension represents band numbers. All metadata and band " +"descriptions from the input dataset are stored as HDF4 attributes. " +"Projection information (if it exists) and affine transformation " +"coefficients also stored in form of attributes. Files, created by GDAL " +"have the special attribute:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:203 +msgid "\"Signature=Created with GDAL (http://www.remotesensing.org/gdal/)\"" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:205 +msgid "" +"and are automatically recognised when read, so the projection info and " +"transformation matrix restored back." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:-1 +msgid "" +"RANK=[2/3]: Defaults to 3. Create n-dimensional SDS. Currently only 2D " +"and 3D datasets supported. By default a 3-dimensional dataset will be " +"created." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:222 +msgid "" +"All HDF4 attributes are transparently translated as GDAL metadata. In the" +" HDF file attributes may be assigned assigned to the whole file as well " +"as to particular subdatasets." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:229 +msgid "|about-open-options| The following open option is supported:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:-1 +msgid "" +"LIST_SDS=[AUTO/YES/NO]: (GDAL >= 3.2) Whether to report Scientific Data " +"Sets (SDS). By default, when a HDF file contains EOS_SWATH or EOS_GRID, " +"SDS will not be listed as GDAL subdatasets (as this would cause them to " +"be reported twice). Listing them can be forced by setting LIST_SDS to " +"YES." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:243 +#: ../../source/drivers/raster/hdf5.rst:220 +#: ../../source/drivers/raster/mem.rst:94 +#: ../../source/drivers/raster/netcdf.rst:661 +#: ../../source/drivers/raster/tiledb.rst:133 +msgid "Multidimensional API support" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:247 +msgid "" +"The HDF4 driver supports the :ref:`multidim_raster_data_model` for " +"reading operations." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:251 +#: ../../source/drivers/raster/hdf5.rst:228 +#: ../../source/drivers/raster/netcdf.rst:724 +msgid "Driver building" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:253 +msgid "" +"This driver built on top of NCSA HDF library, so you need one to compile " +"GDAL with HDF4 support. You may search your operating system distribution" +" for the precompiled binaries or download source code or binaries from " +"the NCSA HDF Home Page (see links below)." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:258 +msgid "" +"Please note, that NCSA HDF library compiled with several defaults which " +"is defined in *hlimits.h* file. For example, *hlimits.h* defines the " +"maximum number of opened files:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:266 +msgid "" +"If you need open more HDF4 files simultaneously you should change this " +"value and rebuild HDF4 library (and relink GDAL if using static HDF " +"libraries)." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:273 +msgid "" +"Implemented as :source_file:`frmts/hdf4/hdf4dataset.cpp` and " +":source_file:`frmts/hdf4/hdf4imagedataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:275 +msgid "`The HDF Group <http://www.hdfgroup.org/>`__" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:276 +msgid "" +"Sources of the data in HDF4 and HDF4-EOS formats: `Earth Observing System" +" Data Gateway <http://edcimswww.cr.usgs.gov/pub/imswelcome/>`__" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:280 +#: ../../source/drivers/raster/hdf5.rst:251 +msgid "Documentation to individual products, supported by this driver:" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:282 +msgid "" +"`Geo-Referencing ASTER L1B Data " +"<http://edcdaac.usgs.gov/aster/ASTER_GeoRef_FINAL.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:284 +msgid "" +"`ASTER Standard Data Product Specifications Document " +"<http://asterweb.jpl.nasa.gov/documents/ASTERHigherLevelUserGuideVer2May01.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:286 +msgid "" +"`MODIS Level 1B Product Information and Status " +"<http://www.mcst.ssai.biz/mcstweb/L1B/product.html>`__" +msgstr "" + +#: ../../source/drivers/raster/hdf4.rst:288 +msgid "" +"`MODIS Ocean User's Guide <http://modis-" +"ocean.gsfc.nasa.gov/userguide.html>`__" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:5 +msgid "HDF5 -- Hierarchical Data Format Release 5 (HDF5)" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:7 +msgid "HDF5" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:9 +msgid "HDF5Image" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:13 +msgid "This driver intended for HDF5 file formats importing." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:15 +msgid "" +"Starting with GDAL 3.7, the driver can parse HDF-EOS5 encoded grid and " +"swath metadata to establish projection and geotransform (for grids), and " +"geolocation array (for swaths)" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:31 +msgid "" +"Hierarchical Data Format is a container for several different datasets. " +"For data storing. HDF contains multidimensional arrays filled by data. " +"One HDF file may contain several arrays. They may differ in size, number " +"of dimensions." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:36 +msgid "" +"The first step is to get a report of the components images (arrays) in " +"the file using **gdalinfo**, and then to import the desired images using " +"gdal_translate. The **gdalinfo** utility lists all multidimensional " +"subdatasets from the input HDF file. The name of individual images " +"(subdatasets) are assigned to the **SUBDATASET_n_NAME** metadata item. " +"The description for each image is found in the **SUBDATASET_n_DESC** " +"metadata item. For HDF5 images the subdataset names will be formatted " +"like this:" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:45 +msgid "*HDF5:file_name:subdataset*" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:47 +msgid "where:" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:48 +msgid "*file_name* is the name of the input file, and" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:50 +msgid "" +"*subdataset* is the dataset name of the array to use (for internal use in" +" GDAL)." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:52 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if HDF5`` option to command " +"line utilities accepting it, or ``HDF5`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename, when it is not using subdataset syntax" +" (it can typically be used to force open a netCDF file that would be " +"nominally recognized by the netCDF driver)." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:61 +msgid "For example, we want to read data from the OMI/Aura Ozone (O3) dataset:" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:140 +msgid "" +"Now select one of the subdatasets, described as ``[1645x60] CloudFraction" +" (32-bit floating-point)``:" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:179 +msgid "" +"Corner Coordinates: Upper Left ( 0.0, 0.0) Lower Left ( 0.0, 1645.0) " +"Upper Right ( 60.0, 0.0) Lower Right ( 60.0, 1645.0) Center ( 30.0, " +"822.5) Band 1 Block=60x1 Type=Float32, ColorInterp=Undefined Open GDAL " +"Datasets: 1 N DriverIsNULL 512x512x0" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:184 +msgid "You may use **gdal_translate** for reading image bands from this dataset." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:187 +msgid "" +"Note that you should provide exactly the contents of the line marked " +"**SUBDATASET_n_NAME** to GDAL, including the **HDF5:** prefix." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:190 +msgid "" +"This driver is intended only for importing remote sensing and geospatial " +"datasets in form of raster images(2D or 3D arrays). If you want explore " +"all data contained in HDF file you should use another tools (you can find" +" information about different HDF tools using links at end of this page)." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:204 +msgid "" +"HDF5 OMI/Aura Ozone (O3) Total Column 1-Orbit L2 Swath 13x24km (**Level-2" +" OMTO3**)" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:207 +msgid "HDF-EOS5 grids (starting with GDAL 3.7)" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:209 +msgid "HDF-EOS5 swaths (starting with GDAL 3.7)" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:212 +msgid "Multi-file support" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:214 +msgid "" +"Starting with GDAL 3.1, the driver supports opening datasets split over " +"several files using the 'family' HDF5 file driver. For that, GDAL must be" +" provided with the filename of the first part, containing in it a single " +"'0' (zero) character, or ending with 0.h5 or 0.hdf5" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:224 +msgid "" +"The HDF5 driver supports the :ref:`multidim_raster_data_model` for " +"reading operations." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:230 +msgid "" +"This driver built on top of NCSA HDF5 library, so you need to download " +"prebuild HDF5 libraries: HDF5-1.6.4 library or higher. You also need zlib" +" 1.2 and szlib 2.0. For windows user be sure to set the attributes " +"writable (especially if you are using Cygwin) and that the DLLs can be " +"located somewhere by your PATH environment variable. You may also " +"download source code NCSA HDF Home Page (see links below)." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:240 +msgid "" +"Implemented as :source_file:`frmts/hdf5/hdf5dataset.cpp` and " +":source_file:`frmts/hdf5/hdf5imagedataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:243 +msgid "" +"`The NCSA HDF5 Download Page " +"<http://hdf.ncsa.uiuc.edu/HDF5/release/obtain5.html>`__ at the `National " +"Center for Supercomputing Applications <http://www.ncsa.uiuc.edu/>`__" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:248 +msgid "" +"`The HDFView is a visual tool for browsing and editing NCSA HDF4 and HDF5" +" files. <http://hdf.ncsa.uiuc.edu/hdf-java-html/hdfview/>`__" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:253 +msgid "" +"`OMTO3: OMI/Aura Ozone (O3) Total Column 1-Orbit L2 Swath 13x24km V003 " +"<https://disc.gsfc.nasa.gov/uui/datasets/OMTO3_V003/summary>`__" +msgstr "" + +#: ../../source/drivers/raster/hdf5.rst:256 +msgid "" +"`HDF-EOS5 Data Model, File Format and Library " +"<https://www.earthdata.nasa.gov/s3fs-public/imported/ESDS-" +"RFC-008-v1.1.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:5 +msgid "HEIF / HEIC -- ISO/IEC 23008-12:2017 High Efficiency Image File Format" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:9 +msgid "HEIF" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:13 +msgid "" +"High Efficiency Image File Format (HEIF) is a container format for " +"individual images and image sequences. The driver has mostly been " +"developed and tested to be able to read images using the High Efficiency " +"Video Coding (HEVC, ITU-T H.265) codec. Such images are usually called " +"HEIC (HEVC in HEIF) files, and have the .heic extension. iOS 11 can " +"generate such files." +msgstr "" + +#: ../../source/drivers/raster/heif.rst:19 +msgid "" +"libheif 1.4 or later is needed to support images with more than 8-bits " +"per channel." +msgstr "" + +#: ../../source/drivers/raster/heif.rst:21 +msgid "" +"The driver can read EXIF metadata (exposed in the ``EXIF`` metadata " +"domain) and XMP metadata (exposed in the ``xml:XMP`` metadata domain)" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:24 +msgid "" +"The driver will expose the thumbnail as an overview (when its number of " +"bands matches the one of the full resolution image)" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:27 +msgid "" +"If a file contains several top-level images, they will be exposed as GDAL" +" subdatasets." +msgstr "" + +#: ../../source/drivers/raster/heif.rst:-1 +msgid "Supports VirtualIO" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:32 +msgid "if libheif >= 1.4" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:36 +msgid "Built hints on Windows" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:38 +msgid "" +"Download source archives for libheif at " +"https://github.com/strukturag/libheif and libde265 at " +"https://github.com/strukturag/libde265" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:42 +msgid "" +"Unpack the archives (for example libde265-1.0.5.tar.gz and " +"libheif-1.7.0.tar.gz)" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:44 +msgid "Build libde265:" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:58 +msgid "Build libheif with libde265 support:" +msgstr "" + +#: ../../source/drivers/raster/heif.rst:73 +msgid "Add in GDAL's nmake.local the following lines before building GDAL:" +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:5 +msgid "HF2 -- HF2/HFZ heightfield raster" +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:7 +msgid "HF2" +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:11 +msgid "" +"GDAL supports reading and writing HF2/HFZ/HF2.GZ heightfield raster " +"datasets." +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:14 +msgid "" +"HF2 is a heightfield format that records difference between consecutive " +"cell values. HF2 files can also optionally be compressed by the gzip " +"algorithm, and so the HF2.GZ files (or HFZ, equivalently) may be " +"significantly smaller than the uncompressed data. The file format enables" +" the user to have control on the desired accuracy through the vertical " +"precision parameter." +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:21 +msgid "" +"GDAL can read and write georeferencing information through extended " +"header blocks." +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:58 +#: ../../source/drivers/raster/ngsgeoid.rst:22 +#: ../../source/drivers/raster/ngw.rst:216 +#: ../../source/drivers/raster/noaa_b.rst:24 +#: ../../source/drivers/raster/ozi.rst:24 +#: ../../source/drivers/raster/pdf.rst:800 +#: ../../source/drivers/raster/xyz.rst:103 +#: ../../source/drivers/vector/dxf.rst:432 +#: ../../source/drivers/vector/ngw.rst:406 +msgid "See also" +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:60 +msgid "" +"`Specification of HF2/HFZ format " +"<http://www.bundysoft.com/docs/doku.php?id=l3dt:formats:specs:hf2>`__" +msgstr "" + +#: ../../source/drivers/raster/hf2.rst:62 +msgid "" +"`Specification of HF2 extended header blocks " +"<http://www.bundysoft.com/docs/doku.php?id=l3dt:formats:specs:hf2#extended_header>`__" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:5 +msgid "HFA -- Erdas Imagine .img" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:7 +msgid "HFA" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:11 +msgid "" +"GDAL supports Erdas Imagine .img format for read access and write. The " +"driver supports reading overviews, palettes, and georeferencing. It " +"supports the Erdas band types u8, s8, u16, s16, u32, s32, f32, f64, c64 " +"and c128." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:16 +msgid "" +"Compressed and missing tiles in Erdas files should be handled properly on" +" read. Files between 2GiB and 4GiB in size should work on Windows NT, and" +" may work on some Unix platforms. Files with external spill files (needed" +" for datasets larger than 2GiB) are also supported for reading and " +"writing." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:22 +msgid "" +"Metadata reading and writing is supported at the dataset and band level. " +"But this is GDAL specific metadata, not metadata in an Imagine recognized" +" form. The metadata is stored in a table called GDAL_MetaData which as " +"many columns as metadata items. The title of the column is the ``key`` of" +" the ``key``=``value`` metadata item pair and the value of row 1 is " +"``value``." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:43 +msgid "" +"Erdas Imagine files can be created with any GDAL defined band type, " +"including the complex types. Created files may have any number of bands. " +"Pseudo-Color tables will be written if using the GDALDriver::CreateCopy()" +" methodology. Most projections should be supported, though translation of" +" unusual datums (other than WGS84, WGS72, NAD83, and NAD27) may be " +"problematic." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:128 +msgid "" +"Erdas Imagine supports external creation of overviews (with gdaladdo for " +"instance). To force them to be created in an .rrd file (rather than " +"inside the original .img) set the global config option HFA_USE_RRD=YES)." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:132 +msgid "" +"Layer names can be set and retrieved with the " +"GDALSetDescription/GDALGetDescription calls on the Raster Band objects." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:135 +msgid "Some HFA band metadata exported to GDAL metadata:" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:137 +msgid "LAYER_TYPE - layer type (athematic, ... )" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:138 +msgid "" +"OVERVIEWS_ALGORITHM - layer overviews algorithm ('IMAGINE 2X2 " +"Resampling', 'IMAGINE 4X4 Resampling', and others)" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:144 +msgid "" +"|about-config-options| Currently the following configuration options are " +"supported by the HFA driver:" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:162 +msgid "" +"This configuration option can be used when building external overviews " +"for a base image that is not in Erdas Imagine format. Resulting overview " +"file will use the rrd structure and have .aux extension." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:171 +msgid "" +"Erdas Imagine and older ArcGIS versions may recognize overviews for some " +"image formats only if they have .rrd extension. In this case use:" +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:196 +msgid "Implemented as :source_file:`frmts/hfa/hfadataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:197 +msgid "" +"More information, and other tools are available on the `Imagine (.img) " +"Reader " +"<http://web.archive.org/web/20130730133056/http://home.gdal.org/projects/imagine/hfa_index.html>`__" +" page as saved by archive.org." +msgstr "" + +#: ../../source/drivers/raster/hfa.rst:201 +msgid "`Erdas.com <http://www.erdas.com/>`__" +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:5 +msgid "ILWIS -- Raster Map" +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:7 +msgid "ILWIS" +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:11 +msgid "" +"This driver implements reading and writing of ILWIS raster maps and map " +"lists. Select the raster files with ``the.mpr`` (for raster map) or " +"``the.mpl`` (for maplist) extensions." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:15 +msgid "Features:" +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:17 +msgid "Support for Byte, Int16, Int32 and Float64 pixel data types." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:18 +msgid "Supports map lists with an associated set of ILWIS raster maps." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:19 +msgid "" +"Read and write geo-reference (.grf). Support for geo-referencing " +"transform is limited to north-oriented GeoRefCorner only. If possible the" +" affine transform is computed from the corner coordinates." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:22 +msgid "" +"Read and write coordinate files (.csy). Support is limited to: Projection" +" type of Projection and Lat/Lon type that are defined in .csy file, the " +"rest of pre-defined projection types are ignored." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:26 +msgid "Limitations:" +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:28 +msgid "" +"Map lists with internal raster map storage (such as produced through " +"Import General Raster) are not supported." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:30 +msgid "ILWIS domain (.dom) and representation (.rpr) files are currently ignored." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:33 +msgid "NOTE: Implemented in :source_file:`frmts/ilwis`." +msgstr "" + +#: ../../source/drivers/raster/ilwis.rst:35 +msgid "See Also: http://www.itc.nl/ilwis/default.asp ." +msgstr "" + +#: ../../source/drivers/raster/index.rst:5 +msgid "Raster drivers" +msgstr "" + +#: ../../source/drivers/raster/index.rst:17 +msgid "" +"The following drivers have been retired and moved to the " +"https://github.com/OSGeo/gdal-extra-drivers repository: BPG, E00GRID, " +"EPSILON, IGNFHeightASCIIGrid, NTv1" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:5 +msgid "IRIS -- Vaisala's weather radar software format" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:7 +msgid "IRIS" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:11 +msgid "" +"This read-only GDAL driver is designed to provide access to the products " +"generated by the IRIS weather radar software." +msgstr "" + +#: ../../source/drivers/raster/iris.rst:14 +msgid "" +"IRIS software format includes a lot of products, and some of them aren't " +"even raster. The driver can read currently:" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:17 +msgid "PPI (reflectivity and speed): Plan position indicator" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:18 +msgid "CAPPI: Constant Altitude Plan position indicator" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:19 +msgid "RAIN1: Hourly rainfall accumulation" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:20 +msgid "RAINN: N-Hour rainfall accumulation" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:21 +msgid "TOPS: Height for selectable dBZ contour" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:22 +msgid "VIL: Vertically integrated liquid for selected layer" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:23 +msgid "MAX: Column Max Z WF W/NS Sections" +msgstr "" + +#: ../../source/drivers/raster/iris.rst:25 +msgid "Most of the metadata is read." +msgstr "" + +#: ../../source/drivers/raster/iris.rst:27 +msgid "" +"Vaisala provides information about the format and software at " +"http://www.vaisala.com/en/defense/products/weatherradar/Pages/IRIS.aspx." +msgstr "" + +#: ../../source/drivers/raster/iris.rst:30 +msgid "NOTE: Implemented as :source_file:`frmts/iris/irisdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/isce.rst:5 +msgid "ISCE -- ISCE" +msgstr "" + +#: ../../source/drivers/raster/isce.rst:11 +msgid "" +"Driver for the image formats used in the JPL's Interferometric synthetic " +"aperture radar Scientific Computing Environment (ISCE). Only images with " +"data types mappable to GDAL data types are supported." +msgstr "" + +#: ../../source/drivers/raster/isce.rst:15 +msgid "" +"Image properties are stored under the ISCE metadata domain, but there is " +"currently no support to access underlying components elements and their " +"properties. Likewise, ISCE domain metadata will be saved as properties in" +" the image XML file." +msgstr "" + +#: ../../source/drivers/raster/isce.rst:20 +msgid "Georeferencing is not yet implemented." +msgstr "" + +#: ../../source/drivers/raster/isce.rst:22 +msgid "The ACCESS_MODE property is not currently honored." +msgstr "" + +#: ../../source/drivers/raster/isce.rst:24 +msgid "" +"The only creation option currently is SCHEME, which value (BIL, BIP, BSQ)" +" determine the interleaving (default is BIP)." +msgstr "" + +#: ../../source/drivers/raster/isce.rst:27 +msgid "NOTE: Implemented as :source_file:`frmts/raw/iscedataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/isg.rst:5 +msgid "ISG -- International Service for the Geoid" +msgstr "" + +#: ../../source/drivers/raster/isg.rst:9 +msgid "ISG" +msgstr "" + +#: ../../source/drivers/raster/isg.rst:13 +msgid "" +"Supports reading grids in the International Service for the Geoid text " +"format, used for number of geoid models at " +"http://www.isgeoid.polimi.it/Geoid/reg_list.html" +msgstr "" + +#: ../../source/drivers/raster/isg.rst:17 +msgid "" +"Format specification is at " +"https://www.isgeoid.polimi.it/Geoid/format_specs.html" +msgstr "" + +#: ../../source/drivers/raster/isg.rst:28 +msgid "" +"WGS84 will always be arbitrarily reported as the interpolation CRS of the" +" grid. Consult grid documentation for exact CRS to apply." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:5 +msgid "ISIS2 -- USGS Astrogeology ISIS Cube (Version 2)" +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:7 +msgid "ISIS2" +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:11 +msgid "" +"ISIS2 is a format used by the USGS Planetary Cartography group to store " +"and distribute planetary imagery data. GDAL provides read and write " +"access to ISIS2 formatted imagery data." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:15 +msgid "" +"ISIS2 files often have the extension .cub, sometimes with an associated " +".lbl (label) file. When a .lbl file exists it should be used as the " +"dataset name rather than the .cub file." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:19 +msgid "" +"In addition to support for most ISIS2 imagery configurations, this driver" +" also reads georeferencing and coordinate system information as well as " +"selected other header metadata." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:23 +#: ../../source/drivers/raster/isis3.rst:29 +#: ../../source/drivers/raster/pds.rst:23 +#: ../../source/drivers/raster/pds4.rst:26 +msgid "" +"Implementation of this driver was supported by the United States " +"Geological Survey." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:26 +msgid "ISIS2 is part of a family of related formats including PDS and ISIS3." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:42 +msgid "" +"Currently the ISIS2 writer writes a very minimal header with only the " +"image structure information. No coordinate system, georeferencing or " +"other metadata is captured." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:69 +msgid "Implemented as :source_file:`frmts/pds/isis2dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:70 +msgid ":ref:`raster.pds` driver" +msgstr "" + +#: ../../source/drivers/raster/isis2.rst:71 +msgid ":ref:`raster.isis3` driver" +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:5 +msgid "ISIS3 -- USGS Astrogeology ISIS Cube (Version 3)" +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:7 +msgid "ISIS3" +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:11 +msgid "" +"ISIS3 is a format used by the USGS Planetary Cartography group to store " +"and distribute planetary imagery data. GDAL provides read/creation/update" +" access to ISIS3 formatted imagery data." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:15 +msgid "" +"ISIS3 files often have the extension .cub, sometimes with an associated " +".lbl (label) file. When a .lbl file exists it should be used as the " +"dataset name rather than the .cub file. Since GDAL 2.2, the driver also " +"supports imagery stored in a separate GeoTIFF file." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:20 +msgid "" +"In addition to support for most ISIS3 imagery configurations, this driver" +" also reads georeferencing and coordinate system information as well as " +"selected other header metadata." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:24 +msgid "" +"Starting with GDAL 2.2, a mask band is attached to each source band. The " +"value of this mask band is 0 when the pixel value is the NULL value or " +"one of the low/high on-intstrument/processed saturation value, or 255 " +"when the pixel value is valid." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:32 +msgid "ISIS3 is part of a family of related formats including PDS and ISIS2." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:48 +msgid "" +"Starting with GDAL 2.2, the ISIS3 label can be retrieved as JSON-" +"serialized content in the json:ISIS3 metadata domain." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:150 +msgid "" +"On creation, a source template label can be passed to the SetMetadata() " +"interface in the \"json:ISIS3\" metadata domain." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:156 +msgid "" +"Starting with GDAL 2.2, the ISIS3 driver supports updating imagery of " +"existing datasets, creating new datasets through the CreateCopy() and " +"Create() interfaces." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:160 +msgid "" +"When using CreateCopy(), gdal_translate or gdalwarp, an effort is made to" +" preserve as much as possible of the original label when doing ISIS3 to " +"ISIS3 conversions. This can be disabled with the USE_SRC_LABEL=NO " +"creation option." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:165 +#: ../../source/drivers/raster/vicar.rst:192 +msgid "|about-creation-options| The available creation options are:" +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:311 +msgid "" +"How to create a copy of a source ISIS3 dataset to another ISIS3 dataset " +"while modifying a parameter of IsisCube.Mapping group, by using GDAL " +"Python :" +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:352 +msgid "Implemented as :source_file:`frmts/pds/isis3dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:353 +msgid ":ref:`GDAL PDS Driver <raster.pds>`" +msgstr "" + +#: ../../source/drivers/raster/isis3.rst:354 +msgid ":ref:`GDAL ISIS2 Driver <raster.isis2>`" +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:5 +msgid "JDEM -- Japanese DEM (.mem)" +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:7 +msgid "JDEM" +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:11 +msgid "" +"GDAL includes read support for Japanese DEM files, normally having the " +"extension .mem. These files are a product of the Japanese Geographic " +"Survey Institute." +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:15 +msgid "" +"These files are represented as having one 32bit floating band with " +"elevation data. The georeferencing of the files is returned as well as " +"the coordinate system (always lat/long on the Tokyo datum)." +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:19 +msgid "There is no update or creation support for this format." +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:21 +msgid "NOTE: Implemented as :source_file:`frmts/jdem/jdemdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/jdem.rst:23 +msgid "" +"See Also: `Geographic Survey Institute (GSI) Web Site. " +"<http://www.gsi.go.jp/ENGLISH/>`__" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:5 +msgid "JP2ECW -- ERDAS JPEG2000 (.jp2)" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:7 +msgid "JP2ECW" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:11 +msgid "" +"GDAL supports reading and writing JPEG2000 files using the ERDAS ECW/JP2 " +"SDK developed by Hexagon Geospatial (formerly Intergraph, ERDAS, " +"ERMapper). Support is optional and requires linking in the libraries " +"available from the ECW/JP2 SDK Download page." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:16 +msgid "" +"Coordinate system and georeferencing transformations are read, and some " +"degree of support is included for GeoJP2 (tm) (GeoTIFF-in-JPEG2000), " +"ERDAS GML-in-JPEG2000, and the new GML-in-JPEG2000 specification " +"developed at OGC." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:51 +#: ../../source/drivers/raster/jp2kak.rst:99 +#: ../../source/drivers/raster/jp2lura.rst:31 +#: ../../source/drivers/raster/jp2mrsid.rst:29 +#: ../../source/drivers/raster/jp2openjpeg.rst:42 +msgid "" +"Georeferencing information can come from different sources : internal " +"(GeoJP2 or GMLJP2 boxes), worldfile .j2w/.wld sidecar files, or PAM " +"(Persistent Auxiliary metadata) .aux.xml sidecar files. By default, " +"information is fetched in following order (first listed is the highest " +"priority): PAM, GeoJP2, GMLJP2, WORLDFILE." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:57 +#: ../../source/drivers/raster/jp2kak.rst:105 +#: ../../source/drivers/raster/jp2mrsid.rst:35 +#: ../../source/drivers/raster/jp2openjpeg.rst:48 +msgid "" +"Starting with GDAL 2.2, the allowed sources and their priority order can " +"be changed with the :config:`GDAL_GEOREF_SOURCES` configuration option " +"(or :oo:`GEOREF_SOURCES` open option) whose value is a comma-separated " +"list of the following keywords : PAM, GEOJP2, GMLJP2, INTERNAL (shortcut " +"for GEOJP2,GMLJP2), WORLDFILE, NONE. Earlier mentioned sources take " +"priority over later ones. A non mentioned source will be ignored." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:64 +#: ../../source/drivers/raster/jp2kak.rst:112 +#: ../../source/drivers/raster/jp2lura.rst:44 +#: ../../source/drivers/raster/jp2mrsid.rst:42 +#: ../../source/drivers/raster/jp2openjpeg.rst:55 +msgid "" +"For example setting it to \"WORLDFILE,PAM,INTERNAL\" will make a " +"geotransformation matrix from a potential worldfile priority over PAM or " +"internal JP2 boxes. Setting it to \"PAM,WORLDFILE,GEOJP2\" will use the " +"mentioned sources and ignore GMLJP2 boxes." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:70 +#: ../../source/drivers/raster/jp2lura.rst:66 +#: ../../source/drivers/raster/jp2mrsid.rst:48 +#: ../../source/drivers/raster/jp2openjpeg.rst:84 +#: ../../source/drivers/raster/jpeg.rst:125 +#: ../../source/drivers/raster/jpegxl.rst:53 +#: ../../source/drivers/raster/pdf.rst:121 +#: ../../source/drivers/raster/rmf.rst:44 +msgid "Open Options" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:91 +msgid "|about-creation-options| Supported creation options are listed below." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:94 +msgid "" +"Note: Only Licensing and compression target need to be specified. The " +"ECW/JP2 SDK will default all other options to recommended settings based " +"on the input characteristics. Changing other options can *substantially* " +"impact decoding speed and compatibility with other JPEG2000 toolkits." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:267 +msgid "" +"If there are metadata domain whose name starts with \"xml:BOX\\_\", they " +"will be written each as separate JP2 XML box." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:270 +msgid "" +"If there is a metadata domain whose name is \"xml:XMP\", its content will" +" be written as a JP2 UUID XMP box." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:281 +msgid "" +"\"JPEG2000 format does not support creation of GDAL overviews since the " +"format is already considered to be optimized for \"arbitrary overviews\"." +" JP2ECW driver also arranges JP2 codestream to allow optimal access to " +"power of two overviews. This is controlled with the creation option " +"LEVELS.\"" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:288 +msgid "Create support" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:290 +msgid "" +"While the driver advertises the Create() capability, contrary to most " +"other drivers that implement it, the implementation of RasterIO() and " +"WriteBlock() in the JP2ECW driver does not support arbitrary random " +"writing. Data must be written in the dataset from top to bottom, whole " +"line(s) at a time." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:299 +msgid "" +"|about-config-options| The ERDAS ECW/JP2 SDK supports a variety of " +"runtime configuration options to control various features. See the " +"ECW/JP2 SDK documentation for full details on the meaning of these " +"options." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:304 +msgid ":copy-config:`ECW_CACHE_MAXMEM`" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:306 +msgid ":copy-config:`ECW_TEXTURE_DITHER`" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:340 +#: ../../source/drivers/raster/jp2openjpeg.rst:18 +#: ../../source/drivers/raster/mrsid.rst:51 +msgid "" +"XMP metadata can be extracted from JPEG2000 files, and will be stored as " +"XML raw content in the xml:XMP metadata domain." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:344 +msgid "" +"ECW/JP2 SDK v5.1+ also advertises JPEG2000 structural information as " +"generic File Metadata reported under \"JPEG2000\" metadata domain (-mdd):" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:347 +msgid "**ALL_COMMENTS**: Generic comment text field" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:348 +msgid "" +"**PROFILE**: Profile type (0,1,2). Refer to ECW/JP2 SDK documentation for" +" more info" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:350 +msgid "**TILES_X**: Number of tiles on X (horizontal) Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:351 +msgid "**TILES_Y**: Number of tiles on Y (vertical) Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:352 +msgid "**TILE_WIDTH**: Tile size on X Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:353 +msgid "**TILE_HEIGHT**: Tile size on Y Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:354 +msgid "" +"**PRECINCT_SIZE_X**: Precinct size for each resolution level (smallest to" +" largest) on X Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:356 +msgid "" +"**PRECINCT_SIZE_Y**: Precinct size for each resolution level (smallest to" +" largest) on Y Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:358 +msgid "**CODE_BLOCK_SIZE_X**: Code block size on X Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:359 +msgid "**CODE_BLOCK_SIZE_Y**: Code block size on Y Axis" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:360 +msgid "" +"**PRECISION**: Precision / Bit-depth of each component eg. 8,8,8 for 8bit" +" 3 band imagery." +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:362 +msgid "**RESOLUTION_LEVELS**: Number of resolution levels" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:363 +msgid "**QUALITY_LAYERS**: Number of quality layers" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:364 +msgid "**PROGRESSION_ORDER**: Progression order (RPCL, LRCP, CPRL, RLCP)" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:365 +msgid "**TRANSFORMATION_TYPE**: Filter transformation used (9x7, 5x3)" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:366 +msgid "**USE_SOP**: Start of Packet marker detected (TRUE/FALSE)" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:367 +msgid "**USE_EPH**: End of Packet header marker detected (TRUE/FALSE)" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:368 +msgid "**GML_JP2_DATA**: OGC GML GeoReferencing box detected (TRUE/FALSE)" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:369 +msgid "**COMPRESSION_RATE_TARGET**: Target compression rate used on encoding" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:375 +msgid "" +"ECW/JP2 SDK available at `www.hexagongeospatial.com " +"<http://hexagongeospatial.com/products/data-management-compression/ecw" +"/erdas-ecw-jp2-sdk>`__" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:377 +msgid "" +"Further product information available in the `User Guide " +"<http://hexagongeospatial.com/products/data-management-compression/ecw" +"/erdas-ecw-jp2-sdk/literature>`__" +msgstr "" + +#: ../../source/drivers/raster/jp2ecw.rst:379 +msgid "" +"Support for non-GDAL specific issues should be directed to the `Hexagon " +"Geospatial public forum " +"<https://sgisupport.intergraph.com/infocenter/index?page=forums&forum=507301383c17ef4e013d8dfa30c2007ef1>`__" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:5 +msgid "JP2KAK -- JPEG 2000 (based on Kakadu SDK)" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:7 +msgid "JP2KAK" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:11 +msgid "" +"The JP2KAK driver, which uses the proprietary `Kakadu SDK " +"<http://www.kakadusoftware.com/>`__, supports JPEG 2000 images, which are" +" specified in the Rec. ITU-T T.8xx | ISO/IEC 15444 family of standards. " +"JPEG 2000 uses a substantially different format and compression mechanism" +" than the traditional JPEG compression and JPEG JFIF format. JPEG and " +"JPEG 2000 are distinct compression standards produced by the same group. " +"JPEG 2000 is based on wavelet compression." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:18 +msgid "The driver includes support for:" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:20 +msgid "" +"reading both JPEG 2000 codestreams (.j2c or .jpc) and JP2 files (.jp2). " +"New images can be also written, but existing images cannot be updated in " +"place." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:23 +msgid "" +"lossy and lossless compression of 8-bit and 16-bit images with 1 or more " +"bands (components)." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:26 +msgid "" +"GeoTIFF style coordinate system and georeferencing information in JP2 " +"file via the `GeoJP2(tm) " +"<https://web.archive.org/web/20151028081930/http://www.lizardtech.com/download/geo/geotiff_box.txt>`__" +" mechanism." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:31 +msgid "" +"JPEG 2000 Part 1 (Rec. ITU-T T.800 | ISO/IEC 15444-1), Part 2 (Rec. ITU-T" +" T.801 | ISO/IEC 15444-2) and Part 15 (HTJ2K) (Rec. ITU-T T.814 | ISO/IEC" +" 15444-15)" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:34 +msgid "" +"The Kakadu SDK is a high quality and high performance JPEG 2000 library " +"in wide used in the geospatial and general imaging community. However, it" +" is not free, and, by default, a builds of GDAL from source does not " +"include support for the JP2KAK driver. The builder must acquire a license" +" for the Kakadu SDK and configure GDAL accordingly." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:40 +msgid "" +"When reading images this driver will represent the bands as being Byte " +"(8-bit unsigned), 16-bit signed/unsigned, and 32-bit signed/unsigned. " +"Georeferencing and coordinate system information will be available if the" +" file is a GeoJP2 (tm) file. Files color encoded in YCbCr color space " +"will be automatically translated to RGB. Paletted images are also " +"supported." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:46 +msgid "" +"XMP metadata can be extracted from JPEG 2000 files, and will be stored as" +" XML raw content in the xml:XMP metadata domain." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:61 +msgid "" +"|about-config-options| The JP2KAK driver supports the following " +"configuration options:" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:118 +msgid "Option Options" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:139 +msgid "" +"JPEG 2000 files can only be created using the CreateCopy mechanism to " +"copy from an existing dataset." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:142 +msgid "" +"JPEG 2000 overviews are maintained as part of the mathematical " +"description of the image. Overviews cannot be built as a separate " +"process, but on read the image will generally be represented as having " +"overview levels at various power of two factors." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:233 +msgid "" +"The following creation options are tightly tied to the Kakadu SDK, and " +"are considered to be for advanced use only. Consult the Kakadu SDK " +"documentation to better understand their meaning." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:237 +msgid "**Corder**: Defaults to \"PRCL\"." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:238 +msgid "" +"**Cprecincts**: Defaults to " +"\"{512,512},{256,512},{128,512},{64,512},{32,512},{16,512},{8,512},{4,512},{2,512}\"." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:240 +msgid "**ORGgen_plt**: Defaults to \"yes\"." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:241 +msgid "**ORGgen_tlm**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:242 +msgid "**ORGtparts**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:243 +msgid "**Cmodes**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:244 +msgid "**Clevels**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:245 +msgid "**Rshift**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:246 +msgid "**Rlevels**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:247 +msgid "**Rweight**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:248 +msgid "**Qguard**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:249 +msgid "" +"**Creversible**: If not set and QUALITY >= 99.5, set to \"yes\", " +"otherwise to \"false\"." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:250 +msgid "**Sprofile**: Kakadu SDK defaults used." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:251 +msgid "" +"**RATE**: Kakadu SDK defaults used. One or more bit-rates, expressed in " +"terms of the ratio between the total number of compressed bits (including" +" headers) and the product of the largest horizontal and vertical image " +"component dimensions. A dash, -, may be used in place of the first bit-" +"rate in the list to indicate that the final quality layer should include " +"all compressed bits. If Clayers is not used, the number of layers is set " +"to the number of rates specified here. If Clayers is used to specify an " +"actual number of quality layers, one of the following must be true: 1) " +"the number of rates specified here is identical to the specified number " +"of layers; or 2) one or two rates are specified using this argument. " +"When two rates are specified, the number of layers must be 2 or more and " +"intervening layers will be assigned roughly logarithmically spaced bit-" +"rates. When only one rate is specified, an internal heuristic determines " +"a lower bound and logarithmically spaces the layer rates over the range. " +"The rates have to be in ASC order." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:263 +msgid "Known Kakadu SDK Issues" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:266 +msgid "Alpha Channel Writing in v7.8" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:268 +msgid "" +"Kakadu SDK v7.8 has a bug in jp2_channels::set_opacity_mapping that can " +"cause an error when writing images with an alpha channel. Please upgrade " +"to version 7.9." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:279 +msgid "kdu_get_num_processors always returns 0 for some platforms" +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:281 +msgid "" +"On non-windows / non-mac installs (e.g. Linux), Kakadu SDK might not " +"include unistd.h in kdu_arch.cpp. This means that \\_SC_NPROCESSORS_ONLN " +"and \\_SC_NPROCESSORS_CONF are not defined and kdu_get_num_processors " +"will always return 0. Therefore the jp2kak driver might not default to " +"creating worker threads." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:290 +msgid "Implemented as :source_file:`frmts/jp2kak/jp2kakdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:291 +msgid "" +"If you're using a Kakadu SDK release before v7.5, configure & compile " +"GDAL with eg. `CXXFLAGS=\"-DKDU_MAJOR_VERSION=7 -DKDU_MINOR_VERSION=3 " +"-DKDU_PATCH_VERSION=2\"` for Kakadu SDK version 7.3.2." +msgstr "" + +#: ../../source/drivers/raster/jp2kak.rst:295 +msgid "Alternate :ref:`raster.jp2openjpeg` driver." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:5 +msgid "JP2Lura -- JPEG2000 driver based on Lurawave library" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:7 +msgid "JP2LURA" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:13 +msgid "" +"This driver is an implementation of a JPEG2000 reader/writer based on " +"Lurawave library." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:16 +#: ../../source/drivers/raster/jp2openjpeg.rst:15 +msgid "" +"The driver uses the VSI Virtual File API, so it can read JPEG2000 " +"compressed NITF files." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:37 +msgid "" +"The allowed sources and their priority order can be changed with the " +":config:`GDAL_GEOREF_SOURCES` configuration option (or " +":oo:`GEOREF_SOURCES` open option) whose value is a comma-separated list " +"of the following keywords : PAM, GEOJP2, GMLJP2, INTERNAL (shortcut for " +"GEOJP2,GMLJP2), WORLDFILE, NONE. Earlier mentioned sources take priority " +"over later ones. A non mentioned source will be ignored." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:52 +#: ../../source/drivers/raster/pdf.rst:58 +#: ../../source/drivers/vector/idb.rst:58 +msgid "|about-config-options| The following configuration options are supported:" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:68 +#: ../../source/drivers/raster/jp2mrsid.rst:50 +msgid "|about-open-options| The following open option is available:" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:330 +#: ../../source/drivers/raster/jp2openjpeg.rst:417 +msgid "" +"If there are metadata domain whose name starts with \"xml:BOX\\_\", they " +"will be written each as separate JP2 'xml ' box." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:333 +#: ../../source/drivers/raster/jp2openjpeg.rst:420 +msgid "" +"If there is a metadata domain whose name is \"xml:XMP\", its content will" +" be written as a JP2 'uuid' XMP box." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:355 +#: ../../source/drivers/raster/jp2openjpeg.rst:450 +msgid "Lossless compression" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:357 +msgid "" +"Lossless compression can be achieved if REVERSIBLE=YES is used (and RATE " +"is not specified)." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:361 +#: ../../source/drivers/raster/jp2openjpeg.rst:646 +msgid "Vector information" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:363 +#: ../../source/drivers/raster/jp2openjpeg.rst:648 +msgid "" +"A JPEG2000 file containing a GMLJP2 v2 box with GML feature collections " +"and/or KML annotations embedded can be opened as a vector file with the " +"OGR API. For example:" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:377 +#: ../../source/drivers/raster/jp2openjpeg.rst:662 +msgid "" +"Feature collections can be linked from the GMLJP2 v2 box to a remote " +"location. By default, the link is not followed. It will be followed if " +"the open option OPEN_REMOTE_GML is set to YES." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:382 +msgid "Bugs" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:384 +msgid "" +"Proper support of JPEG-2000 images with " +"Int32/UInt32/Float32-IEEE754-split on Linux 64 bits require a v2.1.00.17 " +"or later SDK." +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:391 +msgid "" +"`LuraTech JPEG-2000 SDK " +"<https://www.luratech.com/en/solutions/applications/data-compression-" +"imaging-with-jpeg-2000/>`__" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:394 +#: ../../source/drivers/raster/jp2openjpeg.rst:687 +msgid "Other JPEG2000 GDAL drivers :" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:396 +msgid "" +":ref:`JP2OpenJPEG: based on Openjpeg library (open source) " +"<raster.jp2openjpeg>`" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:399 +#: ../../source/drivers/raster/jp2openjpeg.rst:689 +msgid ":ref:`JP2ECW: based on Erdas ECW library (proprietary) <raster.jp2ecw>`" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:402 +#: ../../source/drivers/raster/jp2openjpeg.rst:692 +msgid "" +":ref:`JP2MRSID: based on LizardTech MrSID library (proprietary) " +"<raster.jp2mrsid>`" +msgstr "" + +#: ../../source/drivers/raster/jp2lura.rst:405 +#: ../../source/drivers/raster/jp2openjpeg.rst:695 +msgid ":ref:`JP2KAK: based on Kakadu library (proprietary) <raster.jp2kak>`" +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:5 +msgid "JP2MrSID -- JPEG2000 via MrSID SDK" +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:7 +msgid "JP2MrSID" +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:11 +msgid "" +"JPEG2000 file format is supported for reading with the MrSID DSDK. It is " +"also supported for writing with the MrSID ESDK." +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:14 +msgid "" +"JPEG2000 MrSID support is only available with the version 5.x or newer " +"DSDK and ESDK." +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:64 +msgid "" +"If you have the MrSID ESDK (5.x or newer), it can be used to write " +"JPEG2000 files. |about-creation-options| The following creation options " +"are supported." +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:129 +#: ../../source/drivers/raster/mrsid.rst:69 +msgid "Implemented as :source_file:`frmts/mrsid/mrsiddataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/jp2mrsid.rst:130 +#: ../../source/drivers/raster/mrsid.rst:70 +msgid "`Extensis web site <http://www.extensis.com/support/developers>`__" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:5 +msgid "JP2OpenJPEG -- JPEG2000 driver based on OpenJPEG library" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:7 +msgid "JP2OpenJPEG" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:12 +msgid "" +"This driver is an implementation of a JPEG2000 reader/writer based on " +"OpenJPEG library **v2**." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:21 +msgid "" +"The driver supports writing georeferencing information as GeoJP2 and " +"GMLJP2 boxes." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:24 +msgid "" +"The driver supports creating files with transparency, arbitrary band " +"count, and adding/reading metadata. Update of georeferencing or metadata " +"of existing file is also supported. Optional intellectual property " +"metadata can be read/written in the xml:IPR box." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:61 +msgid "Thread support" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:63 +msgid "" +"By default, if the JPEG2000 file has internal tiling, GDAL will try to " +"decode several tiles in multiple threads if the RasterIO() request it " +"receives intersect several tiles. This behavior can be controlled with " +"the :config:`GDAL_NUM_THREADS` configuration option that defaults to " +"ALL_CPUS in that context. In case RAM is limited, it can be needed to set" +" this configuration option to 1 to disable multi-threading" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:70 +msgid "" +"Starting with OpenJPEG 2.2.0, multi-threaded decoding can also be enabled" +" at the code-block level. This must be enabled with the OPJ_NUM_THREADS " +"environment variable (note: this is a system environment variable, not a " +"GDAL configuration option), which can be set to a numeric value or " +"NUM_CPUS. Its default value is 1. Starting with GDAL 2.3, this multi-" +"threading at code-block level is automatically enabled by GDAL. Starting " +"with GDAL 3.0.1 and OpenJPEG 2.3.2, multi-threaded encoding is " +"automatically enabled and can be controlled with the OPJ_NUM_THREADS " +"environment variable or the :config:`GDAL_NUM_THREADS` configuration " +"option." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:81 +msgid "Both multi-threading mechanism can be combined together." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:354 +msgid "" +"(OpenJPEG >= 2.3.0) Style of the code-block coding passes. The following " +"6 independent settings can be combined together (values should be comma " +"separated):" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:358 +msgid "" +"*BYPASS* (1): enable selective arithmetic coding bypass (can " +"substantially improve coding/decoding speed, at the expense of larger " +"file size)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:361 +msgid "*RESET* (2): reset context probabilities on coding pass boundaries" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:362 +msgid "*TERMALL* (4): enable termination on each coding pass" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:363 +msgid "*VSC* (8): enable vertically causal context" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:364 +msgid "" +"*PREDICTABLE* (16): enable predictable termination (helps for error " +"detection)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:366 +msgid "*SEGSYM* (32): enable segmentation symbols (helps for error detection)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:369 +msgid "" +"Instead of specifying them by text, it is also possible to give the " +"corresponding numeric value of the global codeblock style, by adding the " +"selected options (for example \"BYPASS,TERMALL\" is equivalent to " +"\"5\"=1+4)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:374 +msgid "" +"By default, none of them are enabled. Enabling them will generally " +"increase codestream size, but improve either coding/decoding speed or " +"resilience/error detection." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:423 +msgid "" +"If there is a metadata domain whose name is \"xml:IPR\", its content will" +" be written as a JP2 'jp2i' box." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:452 +msgid "" +"Lossless compression can be achieved if ALL the following creation " +"options are defined :" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:455 +msgid ":co:`QUALITY=100`" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:456 +msgid ":co:`REVERSIBLE=YES`" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:457 +msgid ":co:`YCBCR420=NO` (which is the default)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:462 +msgid "GMLJP2v2 definition file" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:464 +msgid "" +"A GMLJP2v2 box typically contains a GMLJP2RectifiedGridCoverage with the " +"SRS information and geotransformation matrix. It is also possible to add " +"metadata, vector features (GML feature collections), annotations (KML), " +"styles (typically SLD, or other XML format) or any XML content as an " +"extension. The value of the GMLJP2V2_DEF creation option should be a file" +" that conforms with the below syntax (elements starting with \"#\" are " +"documentation, and can be omitted):" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:629 +msgid "" +"Metadata can be dynamically generated from a template file (in that " +"context, with a XML structure) and a XML source file. The template file " +"is processed by searching for patterns like {{{XPATH(xpath_expr)}}} and " +"replacing them by their evaluation against the content of the source " +"file. xpath_expr must be a XPath 1.0 compatible expression, with the " +"addition of the following functions :" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:636 +msgid "" +"**if(cond_expr,expr_if_true,expr_if_false)**: if cond_expr evaluates to " +"true, returns expr_if_true. Otherwise returns expr_if_false" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:638 +msgid "**uuid()**: evaluates to a random UUID" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:640 +msgid "" +"A template file to process XML metadata of Pleiades imagery can be found " +"`here <eoptemplate_pleiades.xml>`__, and a template file to process XML " +"metadata of GeoEye/WorldView imagery can be found `here " +"<eoptemplate_worldviewgeoeye.xml>`__." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:669 +msgid "Implemented as :source_file:`frmts/openjpeg/openjpegdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:671 +msgid "`Official JPEG-2000 page <http://www.jpeg.org/jpeg2000/index.html>`__" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:673 +msgid "`The OpenJPEG library home page <https://github.com/uclouvain/openjpeg>`__" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:676 +msgid "" +"`OGC GML in JPEG2000, version 2.0 " +"<http://docs.opengeospatial.org/is/08-085r4/08-085r4.html>`__ (GDAL 2.0 " +"and 2.1)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:680 +msgid "" +"`OGC GML in JPEG2000, version 2.0.1 " +"<http://docs.opengeospatial.org/is/08-085r5/08-085r5.html>`__ (GDAL 2.2 " +"and above)" +msgstr "" + +#: ../../source/drivers/raster/jp2openjpeg.rst:684 +msgid "" +"`Inspire Data Specification on Orthoimagery - Technical Guidelines " +"<http://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_OI_v3.0.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:5 +msgid "JPEG -- JPEG JFIF File Format" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:7 +msgid "JPEG" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:11 +msgid "" +"The JPEG JFIF format is supported for reading, and batch writing, but not" +" update in place. JPEG files are represented as one band (greyscale) or " +"three band (RGB) datasets with Byte valued bands." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:15 +msgid "" +"The driver will automatically convert images whose color space is YCbCr, " +"CMYK or YCbCrK to RGB, unless :config:`GDAL_JPEG_TO_RGB` is set to NO " +"(YES is the default). When color space translation to RGB is done, the " +"source color space is indicated in the SOURCE_COLOR_SPACE metadata of the" +" IMAGE_STRUCTURE domain." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:21 +msgid "" +"EXIF metadata can be read from JPEG files (but this will not result in a " +"georeferenced image even if the EXIF_GPSLatitude and EXIF_GPSLongitude " +"tags are set). But if an ESRI world file exists with the .jgw, " +".jpgw/.jpegw or .wld suffixes, it will be read and used to establish the " +"geotransform for the image. If available a MapInfo .tab file will also be" +" used for georeferencing. Overviews can be built for JPEG files as an " +"external .ovr file." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:29 +msgid "" +"The driver also supports the \"zlib compressed mask appended to the " +"file\" approach used by a few data providers to add a bitmask to identify" +" pixels that are not valid data. See :ref:`rfc-15` for further details." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:34 +msgid "" +"The driver can deal with bitmask where the bits are ordered with most " +"significant bit first (whereas the usual convention is least significant " +"bit first). The driver will try to autodetect that situation, but the " +"heuristics may fail. In that circumstance, you can set the " +":config:`JPEG_MASK_BIT_ORDER` configuration option to MSB. Bitmask can " +"also be completely ignored by specifying :config:`JPEG_READ_MASK=NO`." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:42 +msgid "" +"The GDAL JPEG Driver is built using the Independent JPEG Group's jpeg " +"library. Also note that the GeoTIFF driver supports tiled TIFF with JPEG " +"compressed tiles. This can be used to apply JPEG compression to datasets " +"that exceed the maximum dimensions of 65,535x65,535 pixels for a single " +"JPEG image." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:48 +msgid "" +"It is also possible to use the JPEG driver with the libjpeg-turbo, a " +"version of libjpeg, API and ABI compatible with IJG libjpeg-6b, which " +"uses MMX, SSE, and SSE2 SIMD instructions to accelerate baseline JPEG " +"compression/decompression." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:53 +msgid "" +"Starting with GDAL 3.4, read and write support for JPEG images with " +"12-bit sample is enabled by default (if JPEG support is also enabled), " +"using GDAL internal libjpeg (based on IJG libjpeg-6b, with additional " +"changes for 12-bit sample support). Support for JPEG with 12-bit sample " +"is independent of whether 8-bit JPEG support is enabled through internal " +"IJG libjpeg-6b or external libjpeg (like libjpeg-turbo)" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:63 +msgid "" +"Embedded EXIF thumbnails (with JPEG compression) can be used as " +"overviews, and generated by GDAL." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:81 +#: ../../source/drivers/raster/jpegxl.rst:50 +msgid "SOURCE_ICC_PROFILE (Base64 encoded ICC profile embedded in file.)" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:83 +msgid "" +"Note that this metadata property can only be used on the original raw " +"pixel data. If automatic conversion to RGB has been done, the color " +"profile information cannot be used." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:87 +msgid "This metadata tag can be used as creation options." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:150 +msgid "" +"JPEG files are created using the \"JPEG\" driver code. Only Byte band " +"types are supported." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:153 +msgid "" +"Only 1 (greyscale), 3 band (input should be in RGB colorspace. the driver" +" will convert it automatically to YCbCr colorspace for storage, and will " +"expose it back as RGB on reading) or 4 band (input should already by in " +"CMYK colorspace. It will be exposed as RGB on reading by default, unless " +"the :config:`GDAL_JPEG_TO_RGB` configuration option is set to NO) " +"configurations." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:160 +msgid "" +"JPEG file creation is implemented by the batch (CreateCopy) method. " +"YCbCrK colorspace is not supported in creation. If the source dataset has" +" a nodata mask, it will be appended as a zlib compressed mask to the JPEG" +" file." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:276 +msgid "EXIF and GPS tags" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:278 +msgid "The below tables list the EXIF and GPS tags that can be written." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:280 +msgid "" +"The \"Metadata item name\" column presents the name of the metadata item " +"to attach to the source dataset." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:282 +msgid "" +"The \"Hex code\" column is the value of the corresponding TIFF EXIF/GPS " +"tag (for reference only)" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst +msgid "The \"Type\" column is the TIFF type associated." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:286 +msgid "" +"ASCII is for text values that are NUL-terminated (for a fixed length tag," +" the length includes this NUL-terminating characters). e.g " +"EXIF_Make=the_make" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:289 +msgid "" +"BYTE/UNDEFINED is for values that can be made of any byte value. The " +"value of the corresponding GDAL metadata item must be a string of " +"hexadecimal formatted values, e.g EXIF_GPSVersionID=0x02 0x00 0x00 0x00. " +"GDAL also accepts an ASCII string: e.g. EXIF_ExifVersion=0231" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:294 +msgid "" +"SHORT is for unsigned integer values in the range [0,65535]. Some tags " +"may accept multiple values, in which case they must be separated by " +"space." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:297 +msgid "" +"LONG is for unsigned integer values in the range [0,4294967295]. Some " +"tags may accept multiple values, in which case they must be separated by " +"space." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:300 +msgid "" +"RATIONAL is for positive floating-point values. Some tags may accept " +"multiple values, in which case they must be separated by space. e.g " +"EXIF_GPSLatitude=49 2 3.5" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:303 +msgid "" +"SRATIONAL is for positive or negative floating-point values. Some tags " +"may accept multiple values, in which case they must be separated by " +"space." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:307 +msgid "" +"When an item accepts a fixed number of values and that more are provided," +" they will be truncated with a warning. In the case they are less values " +"provided than needed, they will be padded with appropriate spaces / " +"zeroes" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:312 +msgid "" +"The \"Number of values\" column is the number of values for the item. " +"Might be \"variable\" if there is no restriction, or a fixed value. For " +"Type=ASCII, the fixed value includes the NUL-terminating byte, so the " +"number of actual printable characters is number of values - 1." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:316 +msgid "" +"The \"Optionality\" column indicates whether the item should be present " +"(\"Mandatory\"), is \"Recommended\" or \"Optional\". GDAL does not " +"enforce this." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:320 +msgid "" +"Many items have more restrictions on the valid content that are not " +"expressed in the below tables. Consult the EXIF specification for more " +"information." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:325 +#: ../../source/drivers/raster/jpeg.rst:421 +msgid "Metadata item name" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:325 +#: ../../source/drivers/raster/jpeg.rst:421 +msgid "Hex code" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:325 +#: ../../source/drivers/raster/jpeg.rst:421 +#: ../../source/drivers/vector/eeda.rst:103 +#: ../../source/drivers/vector/geopackage_aspatial.rst:95 +msgid "Type" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:325 +#: ../../source/drivers/raster/jpeg.rst:421 +msgid "Number of values" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:325 +#: ../../source/drivers/raster/jpeg.rst:421 +msgid "Optionality" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:327 +msgid "EXIF_Document_Name" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:327 +msgid "0x010D" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:327 +#: ../../source/drivers/raster/jpeg.rst:328 +#: ../../source/drivers/raster/jpeg.rst:329 +#: ../../source/drivers/raster/jpeg.rst:330 +#: ../../source/drivers/raster/jpeg.rst:336 +#: ../../source/drivers/raster/jpeg.rst:337 +#: ../../source/drivers/raster/jpeg.rst:338 +#: ../../source/drivers/raster/jpeg.rst:344 +#: ../../source/drivers/raster/jpeg.rst:348 +#: ../../source/drivers/raster/jpeg.rst:358 +#: ../../source/drivers/raster/jpeg.rst:359 +#: ../../source/drivers/raster/jpeg.rst:360 +#: ../../source/drivers/raster/jpeg.rst:361 +#: ../../source/drivers/raster/jpeg.rst:362 +#: ../../source/drivers/raster/jpeg.rst:378 +#: ../../source/drivers/raster/jpeg.rst:379 +#: ../../source/drivers/raster/jpeg.rst:380 +#: ../../source/drivers/raster/jpeg.rst:385 +#: ../../source/drivers/raster/jpeg.rst:409 +#: ../../source/drivers/raster/jpeg.rst:410 +#: ../../source/drivers/raster/jpeg.rst:411 +#: ../../source/drivers/raster/jpeg.rst:413 +#: ../../source/drivers/raster/jpeg.rst:414 +#: ../../source/drivers/raster/jpeg.rst:415 +#: ../../source/drivers/raster/jpeg.rst:424 +#: ../../source/drivers/raster/jpeg.rst:426 +#: ../../source/drivers/raster/jpeg.rst:431 +#: ../../source/drivers/raster/jpeg.rst:432 +#: ../../source/drivers/raster/jpeg.rst:433 +#: ../../source/drivers/raster/jpeg.rst:435 +#: ../../source/drivers/raster/jpeg.rst:437 +#: ../../source/drivers/raster/jpeg.rst:439 +#: ../../source/drivers/raster/jpeg.rst:441 +#: ../../source/drivers/raster/jpeg.rst:442 +#: ../../source/drivers/raster/jpeg.rst:444 +#: ../../source/drivers/raster/jpeg.rst:446 +#: ../../source/drivers/raster/jpeg.rst:448 +#: ../../source/drivers/raster/jpeg.rst:452 +msgid "ASCII" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:327 +#: ../../source/drivers/raster/jpeg.rst:335 +#: ../../source/drivers/raster/jpeg.rst:336 +#: ../../source/drivers/raster/jpeg.rst:338 +#: ../../source/drivers/raster/jpeg.rst:339 +#: ../../source/drivers/raster/jpeg.rst:340 +#: ../../source/drivers/raster/jpeg.rst:341 +#: ../../source/drivers/raster/jpeg.rst:343 +#: ../../source/drivers/raster/jpeg.rst:344 +#: ../../source/drivers/raster/jpeg.rst:346 +#: ../../source/drivers/raster/jpeg.rst:347 +#: ../../source/drivers/raster/jpeg.rst:348 +#: ../../source/drivers/raster/jpeg.rst:349 +#: ../../source/drivers/raster/jpeg.rst:350 +#: ../../source/drivers/raster/jpeg.rst:351 +#: ../../source/drivers/raster/jpeg.rst:352 +#: ../../source/drivers/raster/jpeg.rst:353 +#: ../../source/drivers/raster/jpeg.rst:354 +#: ../../source/drivers/raster/jpeg.rst:355 +#: ../../source/drivers/raster/jpeg.rst:356 +#: ../../source/drivers/raster/jpeg.rst:358 +#: ../../source/drivers/raster/jpeg.rst:359 +#: ../../source/drivers/raster/jpeg.rst:360 +#: ../../source/drivers/raster/jpeg.rst:361 +#: ../../source/drivers/raster/jpeg.rst:362 +#: ../../source/drivers/raster/jpeg.rst:364 +#: ../../source/drivers/raster/jpeg.rst:365 +#: ../../source/drivers/raster/jpeg.rst:366 +#: ../../source/drivers/raster/jpeg.rst:367 +#: ../../source/drivers/raster/jpeg.rst:368 +#: ../../source/drivers/raster/jpeg.rst:369 +#: ../../source/drivers/raster/jpeg.rst:370 +#: ../../source/drivers/raster/jpeg.rst:371 +#: ../../source/drivers/raster/jpeg.rst:372 +#: ../../source/drivers/raster/jpeg.rst:374 +#: ../../source/drivers/raster/jpeg.rst:375 +#: ../../source/drivers/raster/jpeg.rst:376 +#: ../../source/drivers/raster/jpeg.rst:377 +#: ../../source/drivers/raster/jpeg.rst:378 +#: ../../source/drivers/raster/jpeg.rst:379 +#: ../../source/drivers/raster/jpeg.rst:380 +#: ../../source/drivers/raster/jpeg.rst:385 +#: ../../source/drivers/raster/jpeg.rst:386 +#: ../../source/drivers/raster/jpeg.rst:387 +#: ../../source/drivers/raster/jpeg.rst:388 +#: ../../source/drivers/raster/jpeg.rst:389 +#: ../../source/drivers/raster/jpeg.rst:390 +#: ../../source/drivers/raster/jpeg.rst:391 +#: ../../source/drivers/raster/jpeg.rst:392 +#: ../../source/drivers/raster/jpeg.rst:393 +#: ../../source/drivers/raster/jpeg.rst:394 +#: ../../source/drivers/raster/jpeg.rst:395 +#: ../../source/drivers/raster/jpeg.rst:396 +#: ../../source/drivers/raster/jpeg.rst:397 +#: ../../source/drivers/raster/jpeg.rst:400 +#: ../../source/drivers/raster/jpeg.rst:401 +#: ../../source/drivers/raster/jpeg.rst:403 +#: ../../source/drivers/raster/jpeg.rst:404 +#: ../../source/drivers/raster/jpeg.rst:405 +#: ../../source/drivers/raster/jpeg.rst:406 +#: ../../source/drivers/raster/jpeg.rst:407 +#: ../../source/drivers/raster/jpeg.rst:408 +#: ../../source/drivers/raster/jpeg.rst:409 +#: ../../source/drivers/raster/jpeg.rst:410 +#: ../../source/drivers/raster/jpeg.rst:411 +#: ../../source/drivers/raster/jpeg.rst:412 +#: ../../source/drivers/raster/jpeg.rst:413 +#: ../../source/drivers/raster/jpeg.rst:414 +#: ../../source/drivers/raster/jpeg.rst:415 +#: ../../source/drivers/raster/jpeg.rst:423 +#: ../../source/drivers/raster/jpeg.rst:424 +#: ../../source/drivers/raster/jpeg.rst:425 +#: ../../source/drivers/raster/jpeg.rst:426 +#: ../../source/drivers/raster/jpeg.rst:427 +#: ../../source/drivers/raster/jpeg.rst:428 +#: ../../source/drivers/raster/jpeg.rst:429 +#: ../../source/drivers/raster/jpeg.rst:430 +#: ../../source/drivers/raster/jpeg.rst:431 +#: ../../source/drivers/raster/jpeg.rst:432 +#: ../../source/drivers/raster/jpeg.rst:433 +#: ../../source/drivers/raster/jpeg.rst:434 +#: ../../source/drivers/raster/jpeg.rst:435 +#: ../../source/drivers/raster/jpeg.rst:436 +#: ../../source/drivers/raster/jpeg.rst:437 +#: ../../source/drivers/raster/jpeg.rst:438 +#: ../../source/drivers/raster/jpeg.rst:439 +#: ../../source/drivers/raster/jpeg.rst:440 +#: ../../source/drivers/raster/jpeg.rst:441 +#: ../../source/drivers/raster/jpeg.rst:442 +#: ../../source/drivers/raster/jpeg.rst:443 +#: ../../source/drivers/raster/jpeg.rst:444 +#: ../../source/drivers/raster/jpeg.rst:445 +#: ../../source/drivers/raster/jpeg.rst:446 +#: ../../source/drivers/raster/jpeg.rst:447 +#: ../../source/drivers/raster/jpeg.rst:448 +#: ../../source/drivers/raster/jpeg.rst:449 +#: ../../source/drivers/raster/jpeg.rst:450 +#: ../../source/drivers/raster/jpeg.rst:451 +#: ../../source/drivers/raster/jpeg.rst:452 +#: ../../source/drivers/raster/jpeg.rst:453 +#: ../../source/drivers/raster/jpeg.rst:454 +msgid "Optional" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:328 +msgid "EXIF_ImageDescription" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:328 +msgid "0x010E" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:328 +#: ../../source/drivers/raster/jpeg.rst:329 +#: ../../source/drivers/raster/jpeg.rst:330 +#: ../../source/drivers/raster/jpeg.rst:331 +#: ../../source/drivers/raster/jpeg.rst:337 +#: ../../source/drivers/raster/jpeg.rst:345 +#: ../../source/drivers/raster/jpeg.rst:373 +#: ../../source/drivers/raster/jpeg.rst:398 +#: ../../source/drivers/raster/jpeg.rst:399 +#: ../../source/drivers/raster/jpeg.rst:402 +msgid "Recommended" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:329 +msgid "EXIF_Make" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:329 +msgid "0x010F" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:330 +msgid "EXIF_Model" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:330 +msgid "0x0110" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:331 +msgid "EXIF_Orientation" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:331 +msgid "0x0112" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:331 +#: ../../source/drivers/raster/jpeg.rst:334 +#: ../../source/drivers/raster/jpeg.rst:335 +#: ../../source/drivers/raster/jpeg.rst:342 +#: ../../source/drivers/raster/jpeg.rst:347 +#: ../../source/drivers/raster/jpeg.rst:349 +#: ../../source/drivers/raster/jpeg.rst:351 +#: ../../source/drivers/raster/jpeg.rst:371 +#: ../../source/drivers/raster/jpeg.rst:372 +#: ../../source/drivers/raster/jpeg.rst:373 +#: ../../source/drivers/raster/jpeg.rst:375 +#: ../../source/drivers/raster/jpeg.rst:382 +#: ../../source/drivers/raster/jpeg.rst:390 +#: ../../source/drivers/raster/jpeg.rst:391 +#: ../../source/drivers/raster/jpeg.rst:393 +#: ../../source/drivers/raster/jpeg.rst:397 +#: ../../source/drivers/raster/jpeg.rst:398 +#: ../../source/drivers/raster/jpeg.rst:399 +#: ../../source/drivers/raster/jpeg.rst:401 +#: ../../source/drivers/raster/jpeg.rst:402 +#: ../../source/drivers/raster/jpeg.rst:404 +#: ../../source/drivers/raster/jpeg.rst:405 +#: ../../source/drivers/raster/jpeg.rst:406 +#: ../../source/drivers/raster/jpeg.rst:408 +#: ../../source/drivers/raster/jpeg.rst:453 +msgid "SHORT" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:332 +msgid "EXIF_XResolution" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:332 +msgid "0x011A" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:332 +#: ../../source/drivers/raster/jpeg.rst:333 +#: ../../source/drivers/raster/jpeg.rst:339 +#: ../../source/drivers/raster/jpeg.rst:340 +#: ../../source/drivers/raster/jpeg.rst:341 +#: ../../source/drivers/raster/jpeg.rst:343 +#: ../../source/drivers/raster/jpeg.rst:345 +#: ../../source/drivers/raster/jpeg.rst:346 +#: ../../source/drivers/raster/jpeg.rst:364 +#: ../../source/drivers/raster/jpeg.rst:366 +#: ../../source/drivers/raster/jpeg.rst:369 +#: ../../source/drivers/raster/jpeg.rst:370 +#: ../../source/drivers/raster/jpeg.rst:374 +#: ../../source/drivers/raster/jpeg.rst:386 +#: ../../source/drivers/raster/jpeg.rst:388 +#: ../../source/drivers/raster/jpeg.rst:389 +#: ../../source/drivers/raster/jpeg.rst:392 +#: ../../source/drivers/raster/jpeg.rst:400 +#: ../../source/drivers/raster/jpeg.rst:403 +#: ../../source/drivers/raster/jpeg.rst:412 +#: ../../source/drivers/raster/jpeg.rst:425 +#: ../../source/drivers/raster/jpeg.rst:427 +#: ../../source/drivers/raster/jpeg.rst:429 +#: ../../source/drivers/raster/jpeg.rst:430 +#: ../../source/drivers/raster/jpeg.rst:434 +#: ../../source/drivers/raster/jpeg.rst:436 +#: ../../source/drivers/raster/jpeg.rst:438 +#: ../../source/drivers/raster/jpeg.rst:440 +#: ../../source/drivers/raster/jpeg.rst:443 +#: ../../source/drivers/raster/jpeg.rst:445 +#: ../../source/drivers/raster/jpeg.rst:447 +#: ../../source/drivers/raster/jpeg.rst:449 +#: ../../source/drivers/raster/jpeg.rst:454 +msgid "RATIONAL" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:332 +#: ../../source/drivers/raster/jpeg.rst:333 +#: ../../source/drivers/raster/jpeg.rst:334 +#: ../../source/drivers/raster/jpeg.rst:342 +#: ../../source/drivers/raster/jpeg.rst:357 +#: ../../source/drivers/raster/jpeg.rst:363 +#: ../../source/drivers/raster/jpeg.rst:381 +#: ../../source/drivers/raster/jpeg.rst:382 +#: ../../source/drivers/raster/jpeg.rst:383 +#: ../../source/drivers/raster/jpeg.rst:384 +msgid "**Mandatory**" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:333 +msgid "EXIF_YResolution" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:333 +msgid "0x011B" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:334 +msgid "EXIF_ResolutionUnit" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:334 +msgid "0x0128" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:335 +msgid "EXIF_TransferFunction" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:335 +msgid "0x012D" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:335 +msgid "768" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:336 +msgid "EXIF_Software" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:336 +msgid "0x0131" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:337 +msgid "EXIF_DateTime" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:337 +msgid "0x0132" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:338 +msgid "EXIF_Artist" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:338 +msgid "0x013B" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:339 +msgid "EXIF_WhitePoint" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:339 +msgid "0x013E" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:340 +msgid "EXIF_PrimaryChromaticities" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:340 +msgid "0x013F" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:340 +#: ../../source/drivers/raster/jpeg.rst:343 +msgid "6" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:341 +msgid "EXIF_YCbCrCoefficients" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:341 +msgid "0x0211" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:341 +#: ../../source/drivers/raster/jpeg.rst:425 +#: ../../source/drivers/raster/jpeg.rst:427 +#: ../../source/drivers/raster/jpeg.rst:430 +#: ../../source/drivers/raster/jpeg.rst:443 +#: ../../source/drivers/raster/jpeg.rst:445 +#: ../../source/drivers/vector/netcdf.rst:251 +msgid "3" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:342 +msgid "EXIF_YCbCrPositioning" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:342 +msgid "0x0213" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:343 +msgid "EXIF_ReferenceBlackWhite" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:343 +msgid "0x0214" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:344 +msgid "EXIF_Copyright" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:344 +msgid "0x8298" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:345 +msgid "EXIF_ExposureTime" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:345 +msgid "0x829A" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:346 +msgid "EXIF_FNumber" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:346 +msgid "0x829D" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:347 +msgid "EXIF_ExposureProgram" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:347 +msgid "0x8822" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:348 +msgid "EXIF_SpectralSensitivity" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:348 +msgid "0x8824" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:349 +msgid "EXIF_ISOSpeedRatings" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:349 +msgid "0x8827" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:350 +msgid "EXIF_OECF" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:350 +msgid "0x8828" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:350 +#: ../../source/drivers/raster/jpeg.rst:357 +#: ../../source/drivers/raster/jpeg.rst:363 +#: ../../source/drivers/raster/jpeg.rst:376 +#: ../../source/drivers/raster/jpeg.rst:377 +#: ../../source/drivers/raster/jpeg.rst:381 +#: ../../source/drivers/raster/jpeg.rst:387 +#: ../../source/drivers/raster/jpeg.rst:394 +#: ../../source/drivers/raster/jpeg.rst:395 +#: ../../source/drivers/raster/jpeg.rst:396 +#: ../../source/drivers/raster/jpeg.rst:407 +#: ../../source/drivers/raster/jpeg.rst:450 +#: ../../source/drivers/raster/jpeg.rst:451 +msgid "UNDEFINED" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:351 +msgid "EXIF_SensitivityType" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:351 +msgid "0x8830" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:352 +msgid "EXIF_StandardOutputSensitivity" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:352 +msgid "0x8831" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:352 +#: ../../source/drivers/raster/jpeg.rst:353 +#: ../../source/drivers/raster/jpeg.rst:354 +#: ../../source/drivers/raster/jpeg.rst:355 +#: ../../source/drivers/raster/jpeg.rst:356 +#: ../../source/drivers/raster/jpeg.rst:383 +#: ../../source/drivers/raster/jpeg.rst:384 +msgid "LONG" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:353 +msgid "EXIF_RecommendedExposureIndex" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:353 +msgid "0x8832" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:354 +msgid "EXIF_ISOSpeed" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:354 +msgid "0x8833" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:355 +msgid "EXIF_ISOSpeedLatitudeyyy" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:355 +msgid "0x8834" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:356 +msgid "EXIF_ISOSpeedLatitudezzz" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:356 +msgid "0x8835" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:357 +msgid "EXIF_ExifVersion" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:357 +msgid "0x9000" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:358 +msgid "EXIF_DateTimeOriginal" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:358 +msgid "0x9003" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:359 +msgid "EXIF_DateTimeDigitized" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:359 +msgid "0x9004" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:360 +msgid "EXIF_OffsetTime" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:360 +msgid "0x9010" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:360 +#: ../../source/drivers/raster/jpeg.rst:361 +#: ../../source/drivers/raster/jpeg.rst:362 +msgid "7" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:361 +msgid "EXIF_OffsetTimeOriginal" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:361 +msgid "0x9011" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:362 +msgid "EXIF_OffsetTimeDigitized" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:362 +msgid "0x9012" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:363 +msgid "EXIF_ComponentsConfiguration" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:363 +msgid "0x9101" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:364 +msgid "EXIF_CompressedBitsPerPixel" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:364 +msgid "0x9102" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:365 +msgid "EXIF_ShutterSpeedValue" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:365 +msgid "0x9201" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:365 +#: ../../source/drivers/raster/jpeg.rst:367 +#: ../../source/drivers/raster/jpeg.rst:368 +msgid "SRATIONAL" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:366 +msgid "EXIF_ApertureValue" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:366 +msgid "0x9202" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:367 +msgid "EXIF_BrightnessValue" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:367 +msgid "0x9203" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:368 +msgid "EXIF_ExposureBiasValue" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:368 +msgid "0x9204" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:369 +msgid "EXIF_MaxApertureValue" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:369 +msgid "0x9205" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:370 +msgid "EXIF_SubjectDistance" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:370 +msgid "0x9206" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:371 +msgid "EXIF_MeteringMode" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:371 +msgid "0x9207" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:372 +msgid "EXIF_LightSource" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:372 +msgid "0x9208" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:373 +msgid "EXIF_Flash" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:373 +msgid "0x9209" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:374 +msgid "EXIF_FocalLength" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:374 +msgid "0x920A" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:375 +msgid "EXIF_SubjectArea" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:375 +msgid "0x9214" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:376 +msgid "EXIF_MakerNote" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:376 +msgid "0x927C" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:377 +msgid "EXIF_UserComment" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:377 +msgid "0x9286" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:378 +msgid "EXIF_SubSecTime" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:378 +msgid "0x9290" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:379 +msgid "EXIF_SubSecTime_Original" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:379 +msgid "0x9291" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:380 +msgid "EXIF_SubSecTime_Digitized" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:380 +msgid "0x9292" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:381 +msgid "EXIF_FlashpixVersion" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:381 +msgid "0xA000" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:382 +msgid "EXIF_ColorSpace" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:382 +msgid "0xA001" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:383 +msgid "EXIF_PixelXDimension" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:383 +msgid "0xA002" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:384 +msgid "EXIF_PixelYDimension" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:384 +msgid "0xA003" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:385 +msgid "EXIF_RelatedSoundFile" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:385 +msgid "0xA004" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:385 +msgid "13" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:386 +msgid "EXIF_FlashEnergy" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:386 +msgid "0xA20B" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:387 +msgid "EXIF_SpatialFrequencyResponse" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:387 +msgid "0xA20C" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:388 +msgid "EXIF_FocalPlaneXResolution" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:388 +msgid "0xA20E" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:389 +msgid "EXIF_FocalPlaneYResolution" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:389 +msgid "0xA20F" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:390 +msgid "EXIF_FocalPlaneResolutionUnit" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:390 +msgid "0xA210" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:391 +msgid "EXIF_SubjectLocation" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:391 +msgid "0xA214" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:392 +msgid "EXIF_ExposureIndex" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:392 +msgid "0xA215" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:393 +msgid "EXIF_SensingMethod" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:393 +msgid "0xA217" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:394 +msgid "EXIF_FileSource" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:394 +msgid "0xA300" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:395 +msgid "EXIF_SceneType" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:395 +msgid "0xA301" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:396 +msgid "EXIF_CFAPattern" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:396 +msgid "0xA302" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:397 +msgid "EXIF_CustomRendered" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:397 +msgid "0xA401" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:398 +msgid "EXIF_ExposureMode" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:398 +msgid "0xA402" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:399 +msgid "EXIF_WhiteBalance" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:399 +msgid "0xA403" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:400 +msgid "EXIF_DigitalZoomRatio" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:400 +msgid "0xA404" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:401 +msgid "EXIF_FocalLengthIn35mmFilm" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:401 +msgid "0xA405" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:402 +msgid "EXIF_SceneCaptureType" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:402 +msgid "0xA406" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:403 +msgid "EXIF_GainControl" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:403 +msgid "0xA407" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:404 +msgid "EXIF_Contrast" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:404 +msgid "0xA408" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:405 +msgid "EXIF_Saturation" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:405 +msgid "0xA409" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:406 +msgid "EXIF_Sharpness" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:406 +msgid "0xA40A" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:407 +msgid "EXIF_DeviceSettingDescription" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:407 +msgid "0xA40B" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:408 +msgid "EXIF_SubjectDistanceRange" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:408 +msgid "0xA40C" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:409 +msgid "EXIF_ImageUniqueID" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:409 +msgid "0xA420" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:409 +msgid "33" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:410 +msgid "EXIF_CameraOwnerName" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:410 +msgid "0xA430" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:411 +msgid "EXIF_BodySerialNumber" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:411 +msgid "0xA431" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:412 +msgid "EXIF_LensSpecification" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:412 +msgid "0xA432" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:413 +msgid "EXIF_LensMake" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:413 +msgid "0xA433" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:414 +msgid "EXIF_LensModel" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:414 +msgid "0xA434" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:415 +msgid "EXIF_LensSerialNumber" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:415 +msgid "0xA435" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:418 +msgid "GPS tags:" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:423 +msgid "EXIF_GPSVersionID" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:423 +msgid "0x0000" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:423 +#: ../../source/drivers/raster/jpeg.rst:428 +msgid "BYTE" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:424 +msgid "EXIF_GPSLatitudeRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:424 +msgid "0x0001" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:425 +msgid "EXIF_GPSLatitude" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:425 +msgid "0x0002" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:426 +msgid "EXIF_GPSLongitudeRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:426 +msgid "0x0003" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:427 +msgid "EXIF_GPSLongitude" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:427 +msgid "0x0004" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:428 +msgid "EXIF_GPSAltitudeRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:428 +msgid "0x0005" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:429 +msgid "EXIF_GPSAltitude" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:429 +msgid "0x0006" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:430 +msgid "EXIF_GPSTimeStamp" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:430 +msgid "0x0007" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:431 +msgid "EXIF_GPSSatellites" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:431 +msgid "0x0008" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:432 +msgid "EXIF_GPSStatus" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:432 +msgid "0x0009" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:433 +msgid "EXIF_GPSMeasureMode" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:433 +msgid "0x000A" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:434 +msgid "EXIF_GPSDOP" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:434 +msgid "0x000B" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:435 +msgid "EXIF_GPSSpeedRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:435 +msgid "0x000C" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:436 +msgid "EXIF_GPSSpeed" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:436 +msgid "0x000D" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:437 +msgid "EXIF_GPSTrackRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:437 +msgid "0x000E" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:438 +msgid "EXIF_GPSTrack" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:438 +msgid "0x000F" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:439 +msgid "EXIF_GPSImgDirectionRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:439 +msgid "0x0010" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:440 +msgid "EXIF_GPSImgDirection" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:440 +msgid "0x0011" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:441 +msgid "EXIF_GPSMapDatum" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:441 +msgid "0x0012" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:442 +msgid "EXIF_GPSDestLatitudeRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:442 +msgid "0x0013" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:443 +msgid "EXIF_GPSDestLatitude" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:443 +msgid "0x0014" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:444 +msgid "EXIF_GPSDestLongitudeRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:444 +msgid "0x0015" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:445 +msgid "EXIF_GPSDestLongitude" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:445 +msgid "0x0016" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:446 +msgid "EXIF_GPSDestBearingRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:446 +msgid "0x0017" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:447 +msgid "EXIF_GPSDestBearing" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:447 +msgid "0x0018" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:448 +msgid "EXIF_GPSDestDistanceRef" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:448 +msgid "0x0019" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:449 +msgid "EXIF_GPSDestDistance" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:449 +msgid "0x001A" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:450 +msgid "EXIF_GPSProcessingMethod" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:450 +msgid "0x001B" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:451 +msgid "EXIF_GPSAreaInformation" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:451 +msgid "0x001C" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:452 +msgid "EXIF_GPSDateStamp" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:452 +msgid "0x001D" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:452 +msgid "11" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:453 +msgid "EXIF_GPSDifferential" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:453 +msgid "0x001E" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:454 +msgid "EXIF_GPSHPositioningError" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:454 +msgid "0x001F" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:458 +msgid "FLIR metadata" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:462 +msgid "" +"Metadata encoded according to the FLIR convention (infrared images) is " +"available in the ``FLIR`` metadata domain." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:465 +msgid "Metadata from the following sections is supported:" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:467 +msgid "Header" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:468 +msgid "RawData" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:469 +msgid "CameraInfo" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:470 +msgid "PaletteInfo" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:471 +msgid "GPSInfo" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:473 +msgid "Consult https://exiftool.org/TagNames/FLIR.html for details." +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:475 +msgid "" +"The thermal image data, stored either as raw data or in PNG, is exposed " +"as a GDAL subdataset whose name is " +"``JPEG:\"filename.jpg\":FLIR_RAW_THERMAL_IMAGE``" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:481 +msgid "`Independent JPEG Group <http://www.ijg.org/>`__" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:482 +msgid "`libjpeg-turbo <http://sourceforge.net/projects/libjpeg-turbo/>`__" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:483 +msgid ":ref:`raster.gtiff`" +msgstr "" + +#: ../../source/drivers/raster/jpeg.rst:484 +msgid "" +"`EXIF v2.31 specification " +"<http://www.cipa.jp/std/documents/e/DC-008-Translation-2016-E.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:5 +msgid "JPEGXL -- JPEG-XL File Format" +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:9 +msgid "JPEGXL" +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:13 +msgid "" +"The JPEG-XL format is supported for reading, and batch writing " +"(CreateCopy()), but not update in place." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:16 +msgid "" +"The driver supports reading and writing: - georeferencing: encoded as a " +"GeoJP2 UUID box within a JUMBF box. - XMP in the xml:XMP metadata domain " +"- EXIF in the EXIF metadata domain - color profile in the COLOR_PROFILE " +"metadata domain." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:22 +msgid "" +"Reading or writing involves ingesting the whole uncompressed image in " +"memory. Compression is in particular very memory hungry with current " +"libjxl implementation. For large images (let's say width or height larger" +" than 10,000 pixels), using JPEGXL compression as a :ref:`raster.gtiff` " +"codec is thus recommended." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:27 +msgid "" +"The number of worker threads for multi-threaded compression and " +"decompression can be set with the :config:`GDAL_NUM_THREADS` " +"configuration option to an integer value or ``ALL_CPUS`` (the later is " +"the default)." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:32 +msgid "" +"Support for reading and writing XMP and EXIF, and writing georeferencing," +" requires a libjxl version build from its main branch, post 0.6.1 " +"release." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:70 +msgid "" +"With libjxl 0.6.1, only 1 (greyscale), 2 band (greyscale + alpha), 3 band" +" (RGB) or 4 band (RGBA) source images are supported. With later libjxl " +"versions, any number of bands can be written. Supported data types are " +"Byte, UInt16 and Float32." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:75 +msgid "" +"When copying from a (regular) JPEG file, and not specifying lossy " +"compression options, its content is re-encoded in a lossless way, and " +"with reconstruction data that enables to recreate a JPEG file from the " +"JPEGXL codestream." +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:195 +msgid "`JPEG-XL home page <https://jpeg.org/jpegxl/>`__" +msgstr "" + +#: ../../source/drivers/raster/jpegxl.rst:196 +msgid "`libjxl <https://github.com/libjxl/libjxl/>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:5 +msgid "JPIPKAK - JPIP Streaming" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:7 +msgid "JPIPKAK" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:11 +msgid "" +"JPEG 2000 Interactive Protocol (JPIP) flexibility with respect to random " +"access, code stream reordering and incremental decoding is highly " +"exploitable in a networked environment allowing access to remote large " +"files using limited bandwidth connections or high contention networks." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:22 +msgid "JPIPKAK - JPIP Overview" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:24 +msgid "" +"A brief overview of the JPIP event sequence is presented in this section," +" more information can be found at `JPEG 2000 Interactive Protocol (Part 9" +" – JPIP) <http://www.jpeg.org/jpeg2000/j2kpart9.html>`__ and the " +"specification can (and should) be purchased from `ISO " +"<http://www.iso.org>`__." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:30 +msgid "" +"An earlier version of JPEG 2000 Part 9 is available here " +"http://www.jpeg.org/public/fcd15444-9v2.pdf, noting the ISO copyright, " +"diagrams are not replicated in this documentation." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:34 +msgid "" +"The JPIP protocol has been abstracted in this format driver, requests are" +" made at the 1:1 resolution level." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:37 +msgid "|JPIP Sequence Diagram|" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:270 +msgid "JPIP Sequence Diagram" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:39 +msgid "" +"Initial JPIP request for a target image, a target id, a session over " +"http, data to be returned as a jpp-stream are requested and a maximum " +"length is put on the response. In this case no initial window is " +"requested, though it can be. Server responds with a target identifier " +"that can be used to identify the image on the server and a JPIP-cnew " +"response header which includes the path to the JPIP server which will " +"handle all future requests and a cid session identifier. A session is " +"required so that that the server can model the state of the client " +"connection, only sending the data that is required." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:48 +msgid "" +"Client requests particular view windows on the target image with a " +"maximum response length and includes the session identifier established " +"in the previous communication. 'fsiz' is used to identify the resolution " +"associated with the requested view-window. The values 'fx' and 'fy' " +"specify the dimensions of the desired image resolution. 'roff' is used to" +" identify the upper left hand corner off the spatial region associated " +"with the requested view-windw. 'rsiz' is used to identify the horizontal " +"and vertical extents of the spatial region associated with the requested " +"view-window." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:59 +msgid "JPIPKAK -approach" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:61 +msgid "" +"The JPIPKAK driver uses an approach that was first demonstrated here, " +"`J2KViewer <http://www.drc-dev.ohiolink.edu/browser/J2KViewer>`__, by " +"Juan Pablo Garcia Ortiz of separating the communication layer (socket / " +"http) from the Kakadu kdu_cache object. Separating the communication " +"layer from the data object is desirable since it allows the use of " +"optimized http client libraries such as libcurl, Apache HttpClient (note " +"that jportiz used a plain Java socket) and allows SSL communication " +"between the client and server." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:70 +msgid "" +"Kakadu's implementation of client communication with a JPIP server uses a" +" socket, and this socket connection holds the state for this client " +"session. A client session with Kakadu can be recreated using the JPIP " +"cache operations between client and server, but no use of traditional " +"HTTP cookies is supported since JPIP is neutral to the transport layer." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:76 +msgid "" +"The JPIPKAK driver is written using a HTTP client library with the Kakadu" +" cache object and supports optimized communication with a JPIP server " +"(which may or may not support HTTP sessions) and the high performance of " +"the kakadu kdu_region_decompressor." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:81 +msgid "|Component Diagram|" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:271 +msgid "Component Diagram" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:84 +msgid "JPIPKAK - implementation" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:86 +msgid "" +"The implementation supports the GDAL C++ and C API, and provides an " +"initial SWIG wrapper for this driver with a Java ImageIO example " +"(**TODO** - qGIS Example)." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:90 +msgid "" +"The driver uses a simple threading model to support requesting reads of " +"the data and remote fetching. This threading model supports two separate " +"client windows, with just one connection to the server. Requests to the " +"server are multiplexed to utilize available bandwidth efficiently. The " +"client identifies these windows by using “0” (low) or “1” (high) values " +"to a “PRIORITY” metadata request option." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:97 +msgid "Note: SSL support" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:99 +msgid "" +"If the client is built with support for SSL, then driver determines " +"whether to use SSL if the request is a jpips:// protocol as opposed to " +"jpip:// . Note that the driver does not verify server certificates using " +"the Curl certificate bundle and is currently set to accept all SSL server" +" certificates." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:105 +msgid "Note: libCurl" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:107 +msgid "" +"JPIP sets client/server values using HTTP headers, modifications have " +"been made to the GDAL HTTP portability library to support this." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:110 +msgid "|GDAL Sequence Diagram|" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:272 +msgid "GDAL Sequence Diagram" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:112 +msgid "GDALGetDatasetDriver" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:114 +msgid "Fetch the driver to which this dataset relates." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:116 +msgid "Open" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:118 +msgid "" +"If the filename contained in the ``GDALOpenInfo`` object has a case " +"insensitive URI scheme of JPIP or JPIPS the ``JPIPKAKDataset`` is created" +" and initialized, otherwise NULL is returned." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:122 +msgid "Initialize" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:124 +msgid "" +"Initialization involves making an initial connection to the JPIP Server " +"to establish a session and to retrieve the initial metadata about the " +"image (ref. `JPIP Sequence Diagram <#initJPIP>`__)." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:128 +msgid "" +"If the connection fails, the function returns false and the ``Open`` " +"function returns NULL indicating that opening the dataset with this " +"driver failed." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:132 +msgid "" +"If the connection is successful, then subsequent requests to the JPIP " +"server are made to retrieve all the available metadata about the image. " +"Metadata items are set using the ``GDALMajorObject->SetMetadataItem`` in " +"the \"JPIP\" domain." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:137 +msgid "" +"If the metadata returned from the server includes GeoJP2 UUID box, or a " +"GMLJP2 XML box then this metadata is parsed and sets the geographic " +"metadata of this dataset." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:141 +msgid "GDALGetMetadata" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:143 +msgid "C API to ``JPIPKAKDataset->GetMetadata``" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:145 +msgid "GetMetadata" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:147 +msgid "" +"returns metadata for the \"JPIP\" domain, keys are " +"\"JPIP_NQUALITYLAYERS\", \"JPIP_NRESOLUTIONLEVELS\", \"JPIP_NCOMPS\" and " +"\"JPIP_SPRECISION\"" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:151 +msgid "GDALEndAsyncRasterIO" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:153 +msgid "" +"If the asynchronous raster IO is active and not required, the C API calls" +" ``JPIPKAKDataset->EndAsyncRasterIO``" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:156 +msgid "EndAsyncRasterIO" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:158 +msgid "The JPIPKAKAsyncRasterIO object is deleted" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:160 +msgid "delete" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:161 +msgid "GDALBeginAsyncRasterIO" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:163 +msgid "C API to ``JPIPKAKDataset->BeginAsyncRasterIO``" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:165 +msgid "BeginAsyncRasterIO" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:167 +msgid "" +"The client has set the requested view window at 1:1 and have optionally " +"set the discard level, quality layers and thread priority metadata items." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:171 +msgid "Create" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:173 +msgid "Creates a JPIPKAKAsyncRasterIO Object" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:175 +msgid "Start" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:177 +msgid "" +"Configures the kakadu machinery and starts a background thread (if not " +"already running) to communicate to the server the current view window " +"request. The background thread results in the ``kdu_cache`` object being " +"updated until the JPIP server sends an \"End Of Response\" (EOR) message " +"for the current view window request." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:183 +msgid "GDALLockBuffer" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:185 +msgid "C API to LockBuffer" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:187 +msgid "LockBuffer" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:189 +#: ../../source/drivers/raster/jpipkak.rst:227 +msgid "" +"Not implemented in ``JPIPKAKAsyncRasterIO``, a lock is acquired in " +"``JPIPKAKAsyncRasterIO->GetNextUpdatedRegion``" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:192 +msgid "GDALGetNextUpdatedRegion" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:194 +msgid "C API to GetNextUpdatedRegion" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:196 +msgid "GetNextUpdatedRegion" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:198 +msgid "" +"The function decompresses the available data to generate an image " +"(according to the dataset buffer type set in " +"``JPIPKAKDataset->BeginAsyncRasterIO``) The window width, height (at the " +"requested discard level) decompressed is returned in the region pointer " +"and can be rendered by the client. The status of the rendering operation " +"is one of ``GARIO_PENDING, GARIO_UPDATE, GARIO_ERROR, GARIO_COMPLETE`` " +"from the ``GDALAsyncStatusType`` structure. ``GARIO_UPDATE, " +"GARIO_PENDING`` require more reads of GetNextUpdatedRegion to get the " +"full image data, this is the progressive rendering of JPIP. " +"``GARIO_COMPLETE`` indicates the window is complete." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:210 +msgid "" +"``GDALAsyncStatusType`` is a structure used by\\ ``GetNextUpdatedRegion``" +" to indicate whether the function should be called again when either " +"kakadu has more data in its cache to decompress, or the server has not " +"sent an End Of Response (EOR) message to indicate the request window is " +"complete." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:216 +msgid "" +"The region passed into this function is passed by reference, and the " +"caller can read this region when the result returns to find the region " +"that has been decompressed. The image data is packed into the buffer, " +"e.g. RGB if the region requested has 3 components." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:221 +msgid "GDALUnlockBuffer" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:223 +msgid "C Api to UnlockBuffer" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:225 +msgid "UnlockBuffer" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:230 +msgid "Draw" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:232 +msgid "Client renders image data" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:234 +msgid "`GDALLockBuffer <#GDALLockBuffer>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:235 +msgid "`LockBuffer <#LockBuffer>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:236 +msgid "`GDALGetNextUpdatedRegion <#GDALGetNextUpdatedRegion>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:237 +msgid "`GetNextUpdatedRegion <#GetNextUpdatedRegion>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:238 +msgid "`GDALUnlockBuffer <#GDALUnlockBuffer>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:239 +msgid "`UnlockBuffer <#UnlockBuffer>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:240 +msgid "`Draw <#Draw>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:243 +msgid "JPIPKAK - installation requirements" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:245 +msgid "`Libcurl 7.9.4 <http://curl.haxx.se/>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:246 +msgid "" +"`OpenSSL 0.9.8K <http://www.openssl.org/>`__ (if SSL is required, a JPIPS" +" connection)" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:248 +msgid "`Kakadu <http://www.kakadusoftware.com>`__ (tested with v5.2.6 and v6)" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:251 +msgid "" +"Currently only a Windows makefile is provided, however this should " +"compile on Linux as well as there are no Windows dependencies." +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:257 +msgid "" +"`JPEG 2000 Interactive Protocol (Part 9 – JPIP) " +"<http://www.jpeg.org/jpeg2000/j2kpart9.html>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:259 +msgid "http://www.opengeospatial.org/standards/gmljp2" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:260 +msgid "`Kakadu Software <http://www.kakadusoftware.com>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:261 +msgid "`IAS demo (example JPIP(S) streams) <http://iasdemo.ittvis.com/>`__" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:264 +msgid "NOTES" +msgstr "" + +#: ../../source/drivers/raster/jpipkak.rst:266 +msgid "" +"Driver originally developed by `ITT VIS <http://www.ittvis.com>`__ and " +"donated to GDAL to enable SSL enabled JPIP client streaming of remote " +"JPEG 2000 datasets." +msgstr "" + +#: ../../source/drivers/raster/kea.rst:11 +msgid "" +"GDAL can read, create and update files in the KEA format, through the " +"libkea library." +msgstr "" + +#: ../../source/drivers/raster/kea.rst:13 +msgid "" +"KEA is an image file format, named after the New Zealand bird, that " +"provides a full implementation of the GDAL data model and is implemented " +"within a HDF5 file. A software library, libkea, is used to access the " +"file format. The format has comparable performance with existing formats " +"while producing smaller file sizes and is already within active use for a" +" number of projects within Landcare Research, New Zealand, and the wider " +"community." +msgstr "" + +#: ../../source/drivers/raster/kea.rst:21 +msgid "The KEA format supports the following features of the GDAL data model:" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:23 +msgid "" +"Multiple-band support, with possible different datatypes. Bands can be " +"added to an existing dataset with AddBand() API" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:25 +msgid "Image blocking support" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:26 +msgid "Reading, creation and update of data of image blocks" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:27 +msgid "Affine geotransform, WKT projection, GCP" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:28 +msgid "Metadata at dataset and band level" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:29 +msgid "Per-band description" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:30 +msgid "Per-band nodata and color interpretation" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:31 +msgid "Per-band color table" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:32 +msgid "Per-band RAT (Raster Attribute Table) of arbitrary size" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:33 +msgid "Internal overviews and mask bands" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:51 +msgid "" +"|about-creation-options| The following creation options are available. " +"Some are rather esoteric and should rarely be specified, unless the user " +"has good knowledge of the working of the underlying HDF5 format." +msgstr "" + +#: ../../source/drivers/raster/kea.rst:134 +msgid "`libkea GitHub repository <https://github.com/ubarsc/kealib>`__" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:136 +msgid "" +"`The KEAimage file format, by Peter Bunting and Sam Gillingham, published" +" in Computers&Geosciences " +"<http://www.sciencedirect.com/science/article/pii/S0098300413001015>`__" +msgstr "" + +#: ../../source/drivers/raster/kea.rst:139 +msgid ":ref:`HDF5 driver page <raster.hdf5>`" +msgstr "" + +#: ../../source/drivers/raster/kmlsuperoverlay.rst:5 +msgid "KMLSuperoverlay -- KMLSuperoverlay" +msgstr "" + +#: ../../source/drivers/raster/kmlsuperoverlay.rst:11 +msgid "" +"NOTE: Implemented as " +":source_file:`frmts/kmlsuperoverlay/kmlsuperoverlaydataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/kro.rst:5 +msgid "KRO -- KOLOR Raw format" +msgstr "" + +#: ../../source/drivers/raster/kro.rst:7 +msgid "KRO" +msgstr "" + +#: ../../source/drivers/raster/kro.rst:11 +msgid "" +"Supported for read access, update and creation. This format is a binary " +"raw format, that supports data of several depths ( 8 bit, unsigned " +"integer 16 bit and floating point 32 bit) and with several band number (3" +" or 4 typically, for RGB and RGBA). There is no file size limit, except " +"the limitation of the file system." +msgstr "" + +#: ../../source/drivers/raster/kro.rst:17 +msgid "" +"`Specification of the format <http://www.autopano.net/wiki-" +"en/Format_KRO>`__" +msgstr "" + +#: ../../source/drivers/raster/kro.rst:20 +msgid "NOTE: Implemented as :source_file:`frmts/raw/krodataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ktx2.rst:22 +msgid "" +"This driver handles textures with the .ktx2 extension. For .basic, refer " +"to the :ref:`raster.basisu` driver. Note that this driver does *not* " +"handle KTX(1) files." +msgstr "" + +#: ../../source/drivers/raster/ktx2.rst:30 +msgid "" +"When a file is made of several images, they are exposed as subdataset, " +"with the `KTX2:filename:layer_idx:face_idx` syntax." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:5 +msgid "L1B -- NOAA Polar Orbiter Level 1b Data Set (AVHRR)" +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:7 +msgid "L1B" +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:11 +msgid "" +"GDAL supports NOAA Polar Orbiter Level 1b Data Set format for reading. " +"Now it can read NOAA-9(F) -- NOAA-17(M) datasets. NOTE: only AVHRR " +"instrument supported now, if you want read data from other instruments, " +"write to me (Andrey Kiselev, dron@ak4719.spb.edu). AVHRR LAC/HRPT (1 km " +"resolution) and GAC (4 km resolution) should be processed correctly." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:27 +msgid "" +"Note that GDAL simple affine georeference model is completely unsuitable " +"for the NOAA data. So you should not rely on it. It is recommended to use" +" the thin plate spline warper (tps). Automatic image rectification can be" +" done with ground control points (GCPs) from the input file." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:32 +msgid "" +"NOAA stores 51 GCPs per scanline both in the LAC and GAC datasets. In " +"fact you may get less than 51 GCPs, especially at end of scanlines. " +"Another approach to rectification is manual selection of the GCPs using " +"external source of georeference information." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:37 +msgid "" +"A high density of GCPs will be reported, unless the L1B_HIGH_GCP_DENSITY " +"configuration option is set to NO." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:40 +msgid "" +"Precision of the GCPs determination depends from the satellite type. In " +"the NOAA-9 -- NOAA-14 datasets geographic coordinates of the GCPs stored " +"in integer values as a 128th of a degree. So we can't determine positions" +" more precise than 1/128=0.0078125 of degree (~28\"). In NOAA-15 -- " +"NOAA-17 datasets we have much more precise positions, they are stored as " +"10000th of degree." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:47 +msgid "" +"The GCPs will also be reported as a :ref:`geolocation array <rfc-41>`, " +"with Lagrangian interpolation of the 51 GCPs per scanline to the number " +"of pixels per scanline width." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:52 +msgid "" +"Image will be always returned with most northern scanline located at the " +"top of image. If you want determine actual direction of the satellite " +"moving you should look at **LOCATION** metadata record." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:59 +msgid "In case of NOAA-10 in channel 5 you will get repeated channel 4 data." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:64 +msgid "" +"AVHRR/3 instrument (NOAA-15 -- NOAA-17) is a six channel radiometer, but " +"only five channels are transmitted to the ground at any given time. " +"Channels 3A and 3B cannot operate simultaneously. Look at channel " +"description field reported by ``gdalinfo`` to determine what kind of " +"channel contained in processed file." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:69 +msgid "Several parameters, obtained from the dataset stored as metadata records." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:72 +msgid "Metadata records:" +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:74 +msgid "**SATELLITE**: Satellite name" +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:75 +msgid "" +"**DATA_TYPE**: Type of the data, stored in the Level 1b dataset (AVHRR " +"HRPT/LAC/GAC)." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:77 +msgid "" +"**REVOLUTION**: Orbit number. Note that it can be 1 to 2 off the correct " +"orbit number (according to documentation)." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:79 +msgid "**SOURCE**: Receiving station name." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:80 +msgid "**PROCESSING_CENTER**: Name of data processing center." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:81 +msgid "" +"**START**: Time of first scanline acquisition (year, day of year, " +"millisecond of day)." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:83 +msgid "" +"**STOP**: Time of last scanline acquisition (year, day of year, " +"millisecond of day)." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:85 +msgid "" +"**LOCATION**: AVHRR Earth location indication. Will be **Ascending** when" +" satellite moves from low latitudes to high latitudes and **Descending** " +"in other case." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:89 +msgid "" +"Most metadata records can be written to a .CSV file when the " +"L1B_FETCH_METADATA configuration file is set to YES. By default, the " +"filename will be called \"[l1b_dataset_name]_metadata.csv\", and located " +"in the same directory as the L1B dataset. By defining the " +"L1B_METADATA_DIRECTORY configuration option, it is possible to create " +"that file in another directory. The documentation to interpret those " +"metadata is `PODUG 3.1 <http://www.ncdc.noaa.gov/oa/pod-" +"guide/ncdc/docs/podug/html/c3/sec3-1.htm>`__ for NOAA <=14 and `KLM " +"8.3.1.3.3.1 <http://www.ncdc.noaa.gov/oa/pod-" +"guide/ncdc/docs/klm/html/c8/sec83133-1.htm>`__ for NOAA >=15." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:104 +msgid "" +"NOAA <=14 datasets advertise a " +"L1B_SOLAR_ZENITH_ANGLES:\"l1b_dataset_name\" subdataset that contains a " +"maximum of 51 solar zenith angles for each scanline ( beginning at sample" +" 5 with a step of 8 samples for GAC data, beginning at sample 25 with a " +"step of 40 samples for HRPT/LAC/FRAC data)." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:110 +msgid "" +"NOAA >=15 datasets advertise a L1B_ANGLES:\"l1b_dataset_name\" subdataset" +" that contains 3 bands (solar zenith angles, satellite zenith angles and " +"relative azimuth angles) with 51 values for each scanline ( beginning at " +"sample 5 with a step of 8 samples for GAC data, beginning at sample 25 " +"with a step of 40 samples for HRPT/LAC/FRAC data)." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:116 +msgid "" +"NOAA >=15 datasets advertise a L1B_CLOUDS:\"l1b_dataset_name\" subdataset" +" that contains a band of same dimensions as bands of the main L1B " +"dataset. The values of each pixel are 0 = unknown; 1 = clear; 2 = cloudy;" +" 3 = partly cloudy." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:122 +msgid "Nodata mask" +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:124 +msgid "" +"NOAA >=15 datasets that report in their header to have missing scan lines" +" will expose a per-dataset mask band (following :ref:`rfc-15`) to " +"indicate such scan lines." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:131 +msgid "Implemented as :source_file:`frmts/l1b/l1bdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:132 +msgid "" +"NOAA Polar Orbiter Level 1b Data Set documented in the \\``POD User's " +"Guide'' (TIROS-N -- NOAA-14 satellites) and in the \\``NOAA KLM User's " +"Guide'' (NOAA-15 -- NOAA-16 satellites). You can find this manuals at " +"`NOAA Technical Documentation Introduction Page " +"<http://www2.ncdc.noaa.gov/docs/intro.htm>`__" +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:137 +msgid "" +"There are a great variety of L1B datasets, sometimes with variations in " +"header locations that are not documented in the official NOAA " +"documentation. In case a dataset is not recognized by the GDAL L1B " +"driver, the `pytroll <http://www.pytroll.org/>`__ package might be able " +"to recognize it." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:142 +msgid "" +"Excellent and complete review contained in the printed book \\``The " +"Advanced Very High Resolution Radiometer (AVHRR)'' by Arthur P. " +"Cracknell, Taylor and Francis Ltd., 1997, ISBN 0-7484-0209-8." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:145 +msgid "" +"NOAA data can be downloaded from the `Comprehensive Large Array-data " +"Stewardship System (CLASS) <http://www.class.noaa.gov/>`__ (former SAA). " +"Actually it is only source of Level 1b datasets for me, so my " +"implementation tested with that files only." +msgstr "" + +#: ../../source/drivers/raster/l1b.rst:149 +msgid "`NOAA spacecrafts status page <http://www.oso.noaa.gov/poesstatus/>`__" +msgstr "" + +#: ../../source/drivers/raster/lan.rst:5 +msgid "LAN -- Erdas 7.x .LAN and .GIS" +msgstr "" + +#: ../../source/drivers/raster/lan.rst:7 +msgid "LAN" +msgstr "" + +#: ../../source/drivers/raster/lan.rst:11 +msgid "" +"GDAL supports reading and writing Erdas 7.x .LAN and .GIS raster files. " +"Currently 4bit, 8bit and 16bit pixel data types are supported for reading" +" and 8bit and 16bit for writing." +msgstr "" + +#: ../../source/drivers/raster/lan.rst:15 +msgid "" +"GDAL does read the map extents (geotransform) from LAN/GIS files, and " +"attempts to read the coordinate system information. However, this format " +"of file does not include complete coordinate system information, so for " +"state plane and UTM coordinate systems a LOCAL_CS definition is returned " +"with valid linear units but no other meaningful information." +msgstr "" + +#: ../../source/drivers/raster/lan.rst:21 +msgid "The .TRL, .PRO and worldfiles are ignored at this time." +msgstr "" + +#: ../../source/drivers/raster/lan.rst:23 +msgid "NOTE: Implemented as :source_file:`frmts/raw/landataset.cpp`" +msgstr "" + +#: ../../source/drivers/raster/lan.rst:25 +msgid "" +"Development of this driver was financially supported by Kevin Flanders of" +" (`PeopleGIS <http://www.peoplegis.com>`__)." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:5 +msgid "LCP -- FARSITE v.4 LCP Format" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:7 +msgid "LCP" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:11 +msgid "" +"FARSITE v. 4 landscape file (LCP) is a multi-band raster format used by " +"wildland fire behavior and fire effect simulation models such as FlamMap " +"(`firelab.org <https://www.firelab.org/project/flammap>`__). The bands of" +" an LCP file store data describing terrain, tree canopy, and surface " +"fuel. The `LANDFIRE Program <https://www.landfire.gov/>`__ provides " +"geospatial data in LCP format to support fire simulation modeling." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:18 +msgid "" +"An LCP file (.lcp) is basically a raw format with a 7,316-byte header " +"described below. The data type for all bands is 16-bit signed integer. " +"Bands are interleaved by pixel. Five bands are required: elevation, " +"slope, aspect, fuel model, and tree canopy cover. Crown fuel bands " +"(canopy height, canopy base height, canopy bulk density), and surface " +"fuel bands (duff, coarse woody debris) are optional. The LCP driver " +"reports several band-level metadata items described below. The band names" +" used are: ELEVATION, SLOPE, ASPECT, FUEL_MODEL, CANOPY_COV, CANOPY_HT, " +"CBH, CBD, DUFF and CWD." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:29 +msgid "" +"The LCP driver reads the linear unit, cell size, and extent, but the .lcp" +" file does not specify a projection internally. UTM projections are " +"typical, but other projections are possible. The driver will look for a " +"file with .prj extension and read the coordinate system in ESRI pseudo-" +"OGC WKT format." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:34 +msgid "" +"LCP does not support an inherent no data value, but -9999 is used by " +"convention to mark pixels that are not valid data." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:49 +msgid "The GDAL LCP driver reports dataset- and band-level metadata:" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:52 +msgid "Dataset" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "LATITUDE: Latitude of the dataset, negative for southern hemisphere" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "LINEAR_UNIT: Feet or meters" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "DESCRIPTION: LCP file description" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:59 +msgid "Band" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "<band>_UNIT or <band>_OPTION: units or options code for the band" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "<band>_UNIT_NAME or <band>_OPTION_DESC: descriptive name of units/options" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "<band>_MIN: minimum value" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "<band>_MAX: maximum value" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "<band>_NUM_CLASSES: number of classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "<band>_VALUES: comma-delimited list of class values (fuel model band only)" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst +msgid "<band>_FILE: original input raster file name for the band" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:71 +msgid "" +"**Note:** The LCP driver derives from the RawDataset helper class " +"declared in `frmts/raw`. It should be implemented as " +":source_file:`frmts/raw/lcpdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:78 +msgid "" +"|about-creation-options| The LCP driver supports CreateCopy() and " +"metadata values can be set via creation options. Below is a list of " +"options with default values listed first." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:160 +msgid "" +"Creation options that are units of linear measure are fairly lenient. " +"METERS=METER and FOOT=FEET for the most part." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:163 +msgid "" +"**Note:** CreateCopy does not scale or change any data. By setting the " +"units for various bands, it is assumed that the values are in the " +"specified units." +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:167 +msgid "**LCP header format:**" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:170 +msgid "**Start byte**" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:170 +msgid "**No. of bytes**" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:170 +msgid "**Format**" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:170 +msgid "**Name**" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:170 +msgid "**Description**" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:171 +#: ../../source/drivers/raster/lcp.rst:172 +#: ../../source/drivers/raster/lcp.rst:173 +#: ../../source/drivers/raster/lcp.rst:178 +#: ../../source/drivers/raster/lcp.rst:179 +#: ../../source/drivers/raster/lcp.rst:180 +#: ../../source/drivers/raster/lcp.rst:181 +#: ../../source/drivers/raster/lcp.rst:182 +#: ../../source/drivers/raster/lcp.rst:183 +#: ../../source/drivers/raster/lcp.rst:184 +#: ../../source/drivers/raster/lcp.rst:185 +#: ../../source/drivers/raster/lcp.rst:186 +#: ../../source/drivers/raster/lcp.rst:187 +#: ../../source/drivers/raster/lcp.rst:188 +#: ../../source/drivers/raster/lcp.rst:189 +#: ../../source/drivers/raster/lcp.rst:190 +#: ../../source/drivers/raster/lcp.rst:191 +#: ../../source/drivers/raster/lcp.rst:192 +#: ../../source/drivers/raster/lcp.rst:193 +#: ../../source/drivers/raster/lcp.rst:194 +#: ../../source/drivers/raster/lcp.rst:195 +#: ../../source/drivers/raster/lcp.rst:196 +#: ../../source/drivers/raster/lcp.rst:197 +#: ../../source/drivers/raster/lcp.rst:198 +#: ../../source/drivers/raster/lcp.rst:199 +#: ../../source/drivers/raster/lcp.rst:200 +#: ../../source/drivers/raster/lcp.rst:201 +#: ../../source/drivers/raster/lcp.rst:202 +#: ../../source/drivers/raster/lcp.rst:203 +#: ../../source/drivers/raster/lcp.rst:204 +#: ../../source/drivers/raster/lcp.rst:205 +#: ../../source/drivers/raster/lcp.rst:206 +#: ../../source/drivers/raster/lcp.rst:207 +#: ../../source/drivers/raster/lcp.rst:208 +#: ../../source/drivers/raster/lcp.rst:209 +#: ../../source/drivers/raster/lcp.rst:210 +#: ../../source/drivers/raster/lcp.rst:211 +#: ../../source/drivers/raster/lcp.rst:212 +#: ../../source/drivers/raster/lcp.rst:213 +#: ../../source/drivers/raster/lcp.rst:214 +#: ../../source/drivers/raster/lcp.rst:215 +#: ../../source/drivers/raster/lcp.rst:216 +#: ../../source/drivers/raster/lcp.rst:217 +#: ../../source/drivers/raster/lcp.rst:218 +#: ../../source/drivers/raster/lcp.rst:219 +#: ../../source/drivers/raster/lcp.rst:224 +msgid "long" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:171 +msgid "crown fuels" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:171 +msgid "" +"20 if no crown fuels, 21 if crown fuels exist (crown fuels = canopy " +"height, canopy base height, canopy bulk density)" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:172 +msgid "ground fuels" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:172 +msgid "" +"20 if no ground fuels, 21 if ground fuels exist (ground fuels = duff " +"loading, coarse woody)" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:173 +msgid "latitude" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:173 +msgid "latitude (negative for southern hemisphere)" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:174 +msgid "12" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:174 +#: ../../source/drivers/raster/lcp.rst:175 +#: ../../source/drivers/raster/lcp.rst:176 +#: ../../source/drivers/raster/lcp.rst:177 +#: ../../source/drivers/raster/lcp.rst:220 +#: ../../source/drivers/raster/lcp.rst:221 +#: ../../source/drivers/raster/lcp.rst:222 +#: ../../source/drivers/raster/lcp.rst:223 +#: ../../source/drivers/raster/lcp.rst:225 +#: ../../source/drivers/raster/lcp.rst:226 +#: ../../source/drivers/vector/netcdf.rst:89 +#: ../../source/drivers/vector/netcdf.rst:135 +msgid "double" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:174 +msgid "loeast" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:174 +#: ../../source/drivers/raster/lcp.rst:175 +#: ../../source/drivers/raster/lcp.rst:176 +#: ../../source/drivers/raster/lcp.rst:177 +msgid "offset to preserve coordinate precision (legacy from 16-bit OS days)" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:175 +msgid "hieast" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:176 +msgid "lonorth" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:177 +msgid "36" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:177 +msgid "hinorth" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:178 +msgid "44" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:178 +msgid "loelev" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:178 +msgid "minimum elevation" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:179 +msgid "48" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:179 +msgid "hielev" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:179 +msgid "maximum elevation" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:180 +msgid "52" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:180 +msgid "numelev" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:180 +msgid "number of elevation classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:181 +msgid "56" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:181 +#: ../../source/drivers/raster/lcp.rst:185 +#: ../../source/drivers/raster/lcp.rst:189 +#: ../../source/drivers/raster/lcp.rst:193 +#: ../../source/drivers/raster/lcp.rst:197 +#: ../../source/drivers/raster/lcp.rst:201 +#: ../../source/drivers/raster/lcp.rst:205 +#: ../../source/drivers/raster/lcp.rst:209 +#: ../../source/drivers/raster/lcp.rst:213 +#: ../../source/drivers/raster/lcp.rst:217 +msgid "400" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:181 +msgid "elevation values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:181 +msgid "list of elevation values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:182 +msgid "456" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:182 +msgid "loslope" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:182 +msgid "minimum slope" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:183 +msgid "460" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:183 +msgid "hislope" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:183 +msgid "maximum slope" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:184 +msgid "464" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:184 +msgid "numslope" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:184 +msgid "number of slope classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:185 +msgid "468" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:185 +msgid "slope values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:185 +msgid "list of slope values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:186 +msgid "868" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:186 +msgid "loaspect" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:186 +msgid "minimum aspect" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:187 +msgid "872" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:187 +msgid "hiaspect" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:187 +msgid "maximum aspect" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:188 +msgid "876" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:188 +msgid "numaspects" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:188 +msgid "number of aspect classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:189 +msgid "880" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:189 +msgid "aspect values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:189 +msgid "list of aspect values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:190 +msgid "1280" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:190 +msgid "lofuel" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:190 +msgid "minimum fuel model value" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:191 +msgid "1284" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:191 +msgid "hifuel" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:191 +msgid "maximum fuel model value" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:192 +msgid "1288" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:192 +msgid "numfuel" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:192 +msgid "number of fuel models -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:193 +msgid "1292" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:193 +msgid "fuel values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:193 +msgid "list of fuel model values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:194 +msgid "1692" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:194 +msgid "locover" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:194 +msgid "minimum canopy cover" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:195 +msgid "1696" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:195 +msgid "hicover" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:195 +msgid "maximum canopy cover" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:196 +msgid "1700" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:196 +msgid "numcover" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:196 +msgid "number of canopy cover classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:197 +msgid "1704" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:197 +msgid "cover values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:197 +msgid "list of canopy cover values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:198 +msgid "2104" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:198 +msgid "loheight" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:198 +msgid "minimum canopy height" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:199 +msgid "2108" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:199 +msgid "hiheight" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:199 +msgid "maximum canopy height" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:200 +msgid "2112" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:200 +msgid "numheight" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:200 +msgid "number of canopy height classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:201 +msgid "2116" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:201 +msgid "height values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:201 +msgid "list of canopy height values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:202 +msgid "2516" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:202 +msgid "lobase" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:202 +msgid "minimum canopy base height" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:203 +msgid "2520" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:203 +msgid "hibase" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:203 +msgid "maximum canopy base height" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:204 +msgid "2524" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:204 +msgid "numbase" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:204 +msgid "number of canopy base height classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:205 +msgid "2528" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:205 +msgid "base values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:205 +msgid "list of canopy base height values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:206 +msgid "2928" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:206 +msgid "lodensity" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:206 +msgid "minimum canopy bulk density" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:207 +msgid "2932" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:207 +msgid "hidensity" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:207 +msgid "maximum canopy bulk density" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:208 +msgid "2936" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:208 +msgid "numdensity" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:208 +msgid "number of canopy bulk density classes, -1 if >100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:209 +msgid "2940" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:209 +msgid "density values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:209 +msgid "list of canopy bulk density values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:210 +msgid "3340" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:210 +msgid "loduff" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:210 +msgid "minimum duff" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:211 +msgid "3344" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:211 +msgid "hiduff" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:211 +msgid "maximum duff" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:212 +msgid "3348" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:212 +msgid "numduff" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:212 +msgid "number of duff classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:213 +msgid "3352" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:213 +msgid "duff values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:213 +msgid "list of duff values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:214 +msgid "3752" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:214 +msgid "lowoody" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:214 +msgid "minimum coarse woody" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:215 +msgid "3756" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:215 +msgid "hiwoody" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:215 +msgid "maximum coarse woody" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:216 +msgid "3760" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:216 +msgid "numwoodies" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:216 +msgid "number of coarse woody classes, -1 if > 100" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:217 +msgid "3764" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:217 +msgid "woody values" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:217 +msgid "list of coarse woody values as longs" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:218 +msgid "4164" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:218 +msgid "numeast" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:218 +msgid "number of raster columns" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:219 +msgid "4168" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:219 +msgid "numnorth" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:219 +msgid "number of raster rows" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:220 +msgid "4172" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:220 +msgid "EastUtm" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:220 +msgid "max X" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:221 +msgid "4180" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:221 +msgid "WestUtm" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:221 +msgid "min X" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:222 +msgid "4188" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:222 +msgid "NorthUtm" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:222 +msgid "max Y" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:223 +msgid "4196" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:223 +msgid "SouthUtm" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:223 +msgid "min Y" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:224 +msgid "4204" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:224 +msgid "GridUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:224 +msgid "linear unit: 0 = meters, 1 = feet, 2 = kilometers" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:225 +msgid "4208" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:225 +msgid "XResol" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:225 +msgid "cell size width in GridUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:226 +msgid "4216" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:226 +msgid "YResol" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:226 +msgid "cell size height in GridUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:227 +msgid "4224" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:227 +#: ../../source/drivers/raster/lcp.rst:228 +#: ../../source/drivers/raster/lcp.rst:229 +#: ../../source/drivers/raster/lcp.rst:230 +#: ../../source/drivers/raster/lcp.rst:231 +#: ../../source/drivers/raster/lcp.rst:232 +#: ../../source/drivers/raster/lcp.rst:233 +#: ../../source/drivers/raster/lcp.rst:234 +#: ../../source/drivers/raster/lcp.rst:235 +#: ../../source/drivers/raster/lcp.rst:236 +#: ../../source/drivers/vector/netcdf.rst:87 +#: ../../source/drivers/vector/netcdf.rst:127 +msgid "short" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:227 +msgid "EUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:227 +msgid "elevation units: 0 = meters, 1 = feet" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:228 +msgid "4226" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:228 +msgid "SUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:228 +msgid "slope units: 0 = degrees, 1 = percent" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:229 +msgid "4228" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:229 +msgid "AUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:229 +msgid "aspect units: 0 = Grass categories, 1 = Grass degrees, 2 = azimuth degrees" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:230 +msgid "4230" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:230 +msgid "FOptions" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:230 +msgid "" +"fuel model options: 0 = no custom models AND no conversion file, 1 = " +"custom models BUT no conversion file, 2 = no custom models BUT conversion" +" file, 3 = custom models AND conversion file needed" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:231 +msgid "4232" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:231 +msgid "CUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:231 +msgid "canopy cover units: 0 = categories (0-4), 1 = percent" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:232 +msgid "4234" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:232 +msgid "HUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:232 +msgid "canopy height units: 1 = meters, 2 = feet, 3 = m x 10, 4 = ft x 10" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:233 +msgid "4236" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:233 +msgid "BUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:233 +msgid "canopy base height units: 1 = meters, 2 = feet, 3 = m x 10, 4 = ft x 10" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:234 +msgid "4238" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:234 +msgid "PUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:234 +msgid "" +"canopy bulk density units: 1 = kg/m^3, 2 = lb/ft^3, 3 = kg/m^3 x 100, 4 =" +" lb/ft^3 x 1000" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:235 +msgid "4240" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:235 +msgid "DUnits" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:235 +msgid "duff units: 1 = Mg/ha x 10, 2 = t/ac x 10" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:236 +msgid "4242" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:236 +msgid "WOptions" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:236 +msgid "coarse woody options (1 if coarse woody band is present)" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:237 +msgid "4244" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:237 +#: ../../source/drivers/raster/lcp.rst:238 +#: ../../source/drivers/raster/lcp.rst:239 +#: ../../source/drivers/raster/lcp.rst:240 +#: ../../source/drivers/raster/lcp.rst:241 +#: ../../source/drivers/raster/lcp.rst:242 +#: ../../source/drivers/raster/lcp.rst:243 +#: ../../source/drivers/raster/lcp.rst:244 +#: ../../source/drivers/raster/lcp.rst:245 +#: ../../source/drivers/raster/lcp.rst:246 +#: ../../source/drivers/raster/lcp.rst:247 +msgid "char[]" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:237 +msgid "ElevFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:237 +msgid "elevation file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:238 +msgid "4500" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:238 +msgid "SlopeFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:238 +msgid "slope file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:239 +msgid "4756" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:239 +msgid "AspectFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:239 +msgid "aspect file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:240 +msgid "5012" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:240 +msgid "FuelFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:240 +msgid "fuel model file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:241 +msgid "5268" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:241 +msgid "CoverFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:241 +msgid "canopy cover file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:242 +msgid "5524" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:242 +msgid "HeightFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:242 +msgid "canopy height file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:243 +msgid "5780" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:243 +msgid "BaseFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:243 +msgid "canopy base file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:244 +msgid "6036" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:244 +msgid "DensityFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:244 +msgid "canopy bulk density file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:245 +msgid "6292" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:245 +msgid "DuffFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:245 +msgid "duff file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:246 +msgid "6548" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:246 +msgid "WoodyFile" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:246 +msgid "coarse woody file name" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:247 +msgid "6804" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:247 +msgid "512" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:247 +msgid "LCP file description" +msgstr "" + +#: ../../source/drivers/raster/lcp.rst:250 +msgid "*Chris Toney, 2009-02-14*" +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:5 +msgid "Leveller -- Daylon Leveller Heightfield" +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:7 +msgid "Leveller" +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:11 +msgid "" +"Leveller heightfields store 32-bit elevation values. Format versions 4 " +"through 9 are supported with various caveats (see below). The file " +"extension for Leveller heightfields is \"TER\" (which is the same as " +"Terragen, but the driver only recognizes Leveller files)." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:16 +msgid "" +"Blocks are organized as pixel-high scanlines (rows), with the first " +"scanline at the top (north) edge of the DEM, and adjacent pixels on each " +"line increasing from left to right (west to east)." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:20 +msgid "" +"The band type is always Float32, even though format versions 4 and 5 " +"physically use 16.16 fixed-point. The driver auto-converts them to " +"floating-point." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:36 +#: ../../source/drivers/raster/terragen.rst:31 +msgid "Reading" +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:38 +msgid "" +"``dataset::GetProjectionRef()`` will return only a local coordinate " +"system for file versions 4 through 6." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:41 +msgid "" +"``dataset::GetGeoTransform()`` returns a simple world scaling with a " +"centered origin for formats 4 through 6. For versions 7 and higher, it " +"returns a real-world transform except for rotations. The identity " +"transform is not considered an error condition; Leveller documents often " +"use them." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:47 +msgid "" +"``band::GetUnitType()`` will report the measurement units used by the " +"file instead of converting unusual types to meters. A list of unit types " +"is in the ``levellerdataset.cpp`` module." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:51 +msgid "" +"``band::GetScale()`` and ``band::GetOffset()`` will return the physical-" +"to-logical (i.e., raw to real-world) transform for the elevation data." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:56 +#: ../../source/drivers/raster/terragen.rst:44 +msgid "Writing" +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:58 +msgid "The ``dataset::Create()`` call is supported, but for version 7 files only." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:61 +msgid "" +"``band::SetUnitType()`` can be set to any of the unit types listed in the" +" ``levellerdataset.cpp`` module." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:64 +msgid "``dataset::SetGeoTransform()`` should not include rotation data." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:66 +msgid "" +"As with the Terragen driver, the ``MINUSERPIXELVALUE`` option must be " +"specified. This lets the driver correctly map from logical (real-world) " +"elevations to physical elevations." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:70 +msgid "" +"Header information is written out on the first call to " +"``band::IWriteBlock``." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:76 +msgid "Implemented as :source_file:`frmts/leveller/levellerdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/leveller.rst:77 +msgid "" +"Visit `Daylon Graphics <http://www.daylongraphics.com>`__ for the " +"Leveller SDK, which documents the Leveller format." +msgstr "" + +#: ../../source/drivers/raster/loslas.rst:5 +msgid "LOSLAS -- NADCON .los/.las Datum Grid Shift" +msgstr "" + +#: ../../source/drivers/raster/loslas.rst:7 +msgid "LOSLAS" +msgstr "" + +#: ../../source/drivers/raster/loslas.rst:11 +msgid "" +"Starting with GDAL 3.1, can also open geoid models of extension .geo such" +" as https://geodesy.noaa.gov/GEOID/MEXICO97/" +msgstr "" + +#: ../../source/drivers/raster/loslas.rst:14 +msgid "NOTE: Implemented as :source_file:`frmts/raw/loslasdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/map.rst:5 +msgid "MAP -- OziExplorer .MAP" +msgstr "" + +#: ../../source/drivers/raster/map.rst:7 +msgid "MAP" +msgstr "" + +#: ../../source/drivers/raster/map.rst:11 +msgid "OziExplorer MAP files." +msgstr "" + +#: ../../source/drivers/raster/map.rst:23 +msgid "Implemented as :source_file:`frmts/map/mapdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/map.rst:24 +msgid "" +"`OziExplorer Map File Format " +"<http://www.oziexplorer3.com/eng/help/map_file_format.html>`__" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:5 +msgid "MRF -- Meta Raster Format" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:7 +msgid "MRF" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:13 +msgid "" +"Access to a indexed heap of regular tiles (blocks). Controlled by an xml " +"file, usually organized as a pyramid of overviews, with level zero being " +"the full resolution image. None, PNG, JPEG, ZLIB tile packing are " +"implemented" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:18 +msgid "For file creation options, see \"gdalinfo --format MRF\"" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:32 +#: ../../source/drivers/raster/nitf.rst:345 +#: ../../source/drivers/raster/openfilegdb.rst:99 +#: ../../source/drivers/raster/tga.rst:31 +#: ../../source/drivers/vector/arrow.rst:121 +#: ../../source/drivers/vector/filegdb.rst:313 +#: ../../source/drivers/vector/gtfs.rst:44 +#: ../../source/drivers/vector/mapml.rst:150 +#: ../../source/drivers/vector/openfilegdb.rst:365 +#: ../../source/drivers/vector/parquet.rst:237 +#: ../../source/drivers/vector/sqlite.rst:597 +#: ../../source/drivers/vector/vdv.rst:152 +msgid "Links" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:34 +msgid "" +"`MRF User Guide <https://github.com/nasa-" +"gibs/mrf/blob/master/doc/MUG.md>`__" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:35 +msgid "" +"`MRF Specification <https://github.com/nasa-" +"gibs/mrf/blob/master/spec/mrf_spec.md>`__" +msgstr "" + +#: ../../source/drivers/raster/marfa.rst:36 +msgid "`Source repository nasa-gibs/mrf <https://github.com/nasa-gibs/mrf>`__" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:11 +msgid "" +"The MBTiles driver allows reading rasters in the MBTiles format, which is" +" a specification for storing tiled map data in SQLite databases." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:15 +msgid "" +"Starting with GDAL 2.1, the MBTiles driver has creation and write support" +" for MBTiles raster datasets." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:18 +msgid "" +"Starting with GDAL 2.3, the MBTiles driver has read and write support for" +" MBTiles vector datasets. For standalone Mapbox Vector Tile files or set " +"of MVT files, see the :ref:`MVT <vector.mvt>` driver. Note: vector write " +"support requires GDAL to be built with GEOS." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:23 +msgid "" +"GDAL/OGR must be compiled with OGR SQLite driver support, and JPEG and " +"PNG drivers." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:26 +#: ../../source/drivers/vector/pmtiles.rst:24 +msgid "" +"The SRS is always the `Pseudo-Mercator " +"<https://en.wikipedia.org/wiki/Web_Mercator_projection>`__ (a.k.a Google " +"Mercator) projection, EPSG:3857." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:29 +msgid "" +"Starting with GDAL 2.3, the driver will open a dataset as RGBA. For " +"previous versions, the driver will try to determine the number of bands " +"by probing the content of one tile. It is possible to alter this behavior" +" by defining the :config:`MBTILES_BAND_COUNT` configuration option (or " +"starting with GDAL 2.1, the :oo:`BAND_COUNT` open option) to the number " +"of bands. The values supported are 1, 2, 3 or 4. Four band " +"(Red,Green,Blue,Alpha) dataset gives the maximum compatibility with the " +"various encodings of tiles that can be stored." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:38 +msgid "" +"The driver will use the 'bounds' metadata in the metadata table and do " +"necessary tile clipping, if needed, to respect that extent. However that " +"information being optional, if omitted, the driver will use the extent of" +" the tiles at the maximum zoom level. The user can also specify the " +":oo:`USE_BOUNDS=NO` open option to force the use of the actual extent of " +"tiles at the maximum zoom level. Or it can specify any of " +"MINX/MINY/MAXX/MAXY to have a custom extent." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:46 +msgid "" +"The driver can retrieve pixel attributes encoded according to the UTFGrid" +" specification available in some MBTiles files. They can be obtained with" +" the gdallocationinfo utility, or with a " +"GetMetadataItem(\"Pixel_iCol_iLine\", \"LocationInfo\") call on a band " +"object." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:66 +#: ../../source/drivers/raster/pds.rst:42 +#: ../../source/drivers/vector/geojsonseq.rst:58 +msgid "|about-config-options| The following configuration option is available:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:80 +#: ../../source/drivers/raster/mbtiles.rst:260 +#: ../../source/drivers/raster/pds4.rst:184 +msgid "Raster and vector:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:118 +#: ../../source/drivers/raster/mbtiles.rst:279 +#: ../../source/drivers/raster/pds4.rst:104 +msgid "Raster only:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:160 +msgid "Vector only:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:180 +msgid "Raster creation issues" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:182 +msgid "" +"Depending of the number of bands of the input dataset and the tile format" +" selected, the driver will do the necessary conversions to be compatible " +"with the tile format. When using the CreateCopy() API (such as with " +":ref:`gdal_translate`), automatic reprojection of the input dataset to " +"EPSG:3857 (Pseudo-Mercator) will be done, with selection of the " +"appropriate zoom level." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:192 +msgid "" +"The driver implements the Create() and IWriteBlock() methods, so that " +"arbitrary writing of raster blocks is possible, enabling the direct use " +"of MBTiles as the output dataset of utilities such as gdalwarp." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:201 +msgid "" +"Technical/implementation note: in the general case, GDAL blocks do not " +"exactly match a single MBTiles tile. In which case, each GDAL block will " +"overlap four MBTiles tiles. This is easily handled on the read side, but " +"on creation/update side, such configuration could cause numerous " +"decompression/ recompression of tiles to be done, which might cause " +"unnecessary quality loss when using lossy compression (JPEG). To avoid " +"that, the driver will create a temporary database next to the main " +"MBTiles file to store partial MBTiles tiles in a lossless (and " +"uncompressed) way. Once a tile has received data for its four quadrants " +"and for all the bands (or the dataset is closed or explicitly flushed " +"with FlushCache()), those uncompressed tiles are definitely transferred " +"to the MBTiles file with the appropriate compression. All of this is " +"transparent to the user of GDAL API/utilities" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:218 +msgid "" +"MBTiles can store tiles in PNG, JPEG or WEBP (since 3.8). Support for " +"those tile formats depend if the underlying drivers are available in " +"GDAL. By default, GDAL will PNG tiles." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:222 +msgid "" +"It is possible to select the tile format by setting the creation/open " +"option TILE_FORMAT to one of PNG, PNG8, JPEG or WEBP. When using JPEG, " +"the alpha channel will not be stored." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:240 +msgid "Vector creation issues" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:242 +msgid "" +"Tiles are generated with WebMercator (EPSG:3857) projection. It is " +"possible to decide at which zoom level ranges a given layer is written. " +"Several layers can be written but the driver has only write-once support " +"for vector data. For writing several vector datasets into MBTiles file an" +" intermediate format like GeoPackage must be used as a container so that " +"all layers can be converted at the same time. Write-once support means " +"also that existing vector layers can't be edited." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:250 +#: ../../source/drivers/vector/mvt.rst:221 +#: ../../source/drivers/vector/pmtiles.rst:93 +msgid "" +"Part of the conversion is multi-threaded by default, using as many " +"threads as there are cores. The number of threads used can be controlled " +"with the :config:`GDAL_NUM_THREADS` configuration option." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:344 +msgid "Vector only (GDAL >= 2.3):" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:442 +msgid "Layer configuration (vector)" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:444 +#: ../../source/drivers/vector/mvt.rst:372 +#: ../../source/drivers/vector/pmtiles.rst:192 +msgid "" +"The above mentioned CONF dataset creation option can be set to a string " +"whose value is a JSON serialized document such as the below one:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:463 +#: ../../source/drivers/vector/mvt.rst:391 +#: ../../source/drivers/vector/pmtiles.rst:211 +msgid "" +"*boundaries_lod0* and *boundaries_lod1* are the name of the OGR layers " +"that are created into the target MVT dataset. They are mapped to the MVT " +"target layer *boundaries*." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:467 +#: ../../source/drivers/vector/mvt.rst:395 +#: ../../source/drivers/vector/pmtiles.rst:215 +msgid "" +"It is also possible to get the same behavior with the below layer " +"creation options, although that is not convenient in the ogr2ogr use " +"case." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:472 +msgid "Layer creation options (vector)" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:502 +msgid "Overviews (raster)" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:504 +msgid "" +"gdaladdo / BuildOverviews() can be used to compute overviews. Only power-" +"of-two overview factors (2,4,8,16,...) are supported." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:507 +msgid "" +"If more overview levels are specified than available, the extra ones are " +"silently ignored." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:514 +msgid "Vector tiles" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:516 +msgid "" +"Starting with GDAL 2.3, the MBTiles driver can read MBTiles files " +"containing vector tiles conforming to the Mapbox Vector Tile format " +"(format=pbf)." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:520 +msgid "" +"The driver requires the 'metadata' table to contain a name='json' entry, " +"that has a 'vector_layers' array describing layers and their schema. See " +":ref:`metadata.json <mvt_metadata_json>`" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:524 +msgid "" +"Note: The driver will make no effort of stitching together geometries for" +" features that overlap several tiles." +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:530 +msgid "Accessing a remote MBTiles raster :" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:536 +#: ../../source/drivers/raster/mbtiles.rst:598 +#: ../../source/drivers/raster/rasterlite.rst:192 +#: ../../source/drivers/raster/rasterlite.rst:231 +#: ../../source/drivers/raster/wms.rst:124 +msgid "Output:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:591 +msgid "Reading pixel attributes encoded according to the UTFGrid specification :" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:612 +msgid "Converting a dataset to MBTiles and adding overviews :" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:619 +msgid "Opening a vector MBTiles:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:639 +msgid "Converting a GeoPackage to a Vector tile MBTILES:" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:648 +msgid "`MBTiles specification <https://github.com/mapbox/mbtiles-spec>`__" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:649 +msgid "" +"`UTFGrid specification <https://github.com/mapbox/utfgrid-" +"spec/blob/master/1.0/utfgrid.md>`__" +msgstr "" + +#: ../../source/drivers/raster/mbtiles.rst:651 +#: ../../source/drivers/vector/pmtiles.rst:357 +msgid ":ref:`Mapbox Vector tiles driver <vector.mvt>`" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:5 +msgid "MEM -- In Memory Raster" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:7 +msgid "MEM" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:11 +msgid "" +"GDAL supports the ability to hold rasters in a temporary in-memory " +"format. This is primarily useful for temporary datasets in scripts or " +"internal to applications. It is not generally of any use to application " +"end-users." +msgstr "" + +#: ../../source/drivers/raster/mem.rst:16 +msgid "" +"Memory datasets should support for most kinds of auxiliary information " +"including metadata, coordinate systems, georeferencing, GCPs, color " +"interpretation, nodata, color tables and all pixel data types." +msgstr "" + +#: ../../source/drivers/raster/mem.rst:21 +msgid "Dataset Name Format" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:23 +msgid "" +"It is possible to open an existing array in memory. To do so, construct a" +" dataset name with the following format:" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:46 +msgid "" +"DATAPOINTER: address of the first pixel of the first band. The address " +"can be represented as a hexadecimal or decimal value. Hexadecimal values " +"must be prefixed with '0x'. Some implementations (notably Windows) " +"doesn't print hexadecimal pointer values with a leading '0x', so the " +"prefix must be added. You can use CPLPrintPointer to create a string with" +" format suitable for use as a DATAPOINTER." +msgstr "" + +#: ../../source/drivers/raster/mem.rst:53 +msgid "PIXELS: Width of raster in pixels. (required)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:54 +msgid "LINES: Height of raster in lines. (required)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:55 +msgid "BANDS: Number of bands, defaults to 1. (optional)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:56 +msgid "" +"DATATYPE: Name of the data type, as returned by GDALGetDataTypeName() " +"(eg. Byte, Int16) Defaults to Byte. (optional)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:58 +msgid "" +"PIXELOFFSET: Offset in bytes between the start of one pixel and the next " +"on the same scanline. (optional)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:60 +msgid "" +"LINEOFFSET: Offset in bytes between the start of one scanline and the " +"next. (optional)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:62 +msgid "" +"BANDOFFSET: Offset in bytes between the start of one bands data and the " +"next." +msgstr "" + +#: ../../source/drivers/raster/mem.rst:64 +msgid "" +"GEOTRANSFORM: Set the affine transformation coefficients. 6 real numbers " +"with '/' as separator (optional)" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:66 +msgid "" +"SPATIALREFERENCE: (GDAL >= 3.7) Set the projection. The coordinate " +"reference systems that can be passed are anything supported by the " +"OGRSpatialReference.SetFromUserInput() as per '-a_srs' in " +":ref:`gdal_translate`. If the passed string includes comma or double-" +"quote characters (typically WKT), it should be surrounded by double-quote" +" characters and the double-quote characters inside it should be escaped " +"with anti-slash. e.g ``SPATIALREFERENCE=\"GEOGCRS[\\\"WGS 84\\\",[... " +"snip ...],ID[\\\"EPSG\\\",4326]]\"``" +msgstr "" + +#: ../../source/drivers/raster/mem.rst:78 +msgid "There are no supported creation options." +msgstr "" + +#: ../../source/drivers/raster/mem.rst:80 +msgid "" +"The MEM format is one of the few that supports the AddBand() method. The " +"AddBand() method supports DATAPOINTER, PIXELOFFSET and LINEOFFSET options" +" to reference an existing memory array." +msgstr "" + +#: ../../source/drivers/raster/mem.rst:98 +msgid "The MEM driver supports the :ref:`multidim_raster_data_model`." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:5 +msgid "MFF -- Vexcel MFF Raster" +msgstr "" + +#: ../../source/drivers/raster/mff.rst:7 +msgid "MFF" +msgstr "" + +#: ../../source/drivers/raster/mff.rst:11 +msgid "" +"GDAL includes read, update, and creation support for Vexcel's MFF raster " +"format. MFF dataset consist of a header file (typically with the " +"extension .hdr) and a set of data files with extensions like .x00, .b00 " +"and so on. To open a dataset select the .hdr file." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:16 +msgid "" +"Reading lat/long GCPs (TOP_LEFT_CORNER, ...) is supported but there is no" +" support for reading affine georeferencing or projection information." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:19 +msgid "Unrecognized keywords from the .hdr file are preserved as metadata." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:21 +msgid "" +"All data types with GDAL equivalents are supported, including 8, 16, 32 " +"and 64 bit data precisions in integer, real and complex data types. In " +"addition tile organized files (as produced by the Vexcel SAR Processor - " +"APP) are supported for reading." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:26 +msgid "" +"On creation (with a format code of MFF) a simple, ungeoreferenced raster " +"file is created." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:29 +msgid "" +"MFF files are not normally portable between systems with different byte " +"orders. However GDAL honours the new BYTE_ORDER keyword which can take a " +"value of LSB (Integer - little endian), and MSB (Motorola - big endian). " +"This may be manually added to the .hdr file if required." +msgstr "" + +#: ../../source/drivers/raster/mff.rst:34 +msgid "NOTE: Implemented as :source_file:`frmts/raw/mffdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:5 +msgid "MFF2 -- Vexcel MFF2 Image" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:7 +msgid "MFF2" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:11 +msgid "" +"GDAL supports MFF2 Image raster file format for read, update, and " +"creation. The MFF2 (Multi-File Format 2) format was designed to fit into " +"Vexcel Hierarchical Key-Value (HKV) databases, which can store binary " +"data as well as ASCII parameters. This format is primarily used " +"internally to the Vexcel InSAR processing system." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:17 +msgid "" +"To select an MFF2 dataset, select the directory containing the " +"``attrib``, and ``image_data`` files for the dataset." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:20 +msgid "" +"Currently only latitude/longitude and UTM projection are supported " +"(georef.projection.name = ll or georef.projection.name = utm), with the " +"affine transform computed from the lat/long control points. In any event," +" if GCPs are available in a georef file, they are returned with the " +"dataset." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:26 +msgid "" +"Newly created files (with a type of ``MFF2``) are always just raw rasters" +" with no georeferencing information. For read, and creation all data " +"types (real, integer and complex in bit depths of 8, 16, 32) should be " +"supported." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:31 +msgid "" +"IMPORTANT: When creating a new MFF2, be sure to set the projection before" +" setting the geotransform (this is necessary because the geotransform is " +"stored internally as 5 latitude-longitude ground control points, and the " +"projection is needed to do the conversion)." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:36 +msgid "NOTE: Implemented as :source_file:`frmts/raw/hkvdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:50 +msgid "Format Details" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:53 +msgid "MFF2 Top-level Structure" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:55 +msgid "" +"An MFF2 \"file\" is actually a set of files stored in a directory " +"containing an ASCII header file entitled \"attrib\", and binary image " +"data entitled \"image_data\". Optionally, there may be an ASCII " +"\"georef\" file containing georeferencing and projection information, and" +" an \"image_data_ovr\" (for \"image_data\" binary image data) file " +"containing tiled overviews of the image in TIFF format. The ASCII files " +"are arranged in key=value pairs. The allowable pairs for each file are " +"described below." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:65 +msgid "The \"attrib\" File" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:67 +msgid "" +"As a minimum, the \"attrib\" file must specify the image extents, pixel " +"size in bytes, pixel encoding and datatype, and pixel byte order. For " +"example," +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:81 +msgid "" +"specifies an image that is 1040 lines by 800 pixels in extent. The pixels" +" are 32 bits of real data in \"most significant byte first\" (msbf) " +"order, encoded according to the ieee_754 specification. In MFF2, when a " +"value must belong to a certain subset (eg. pixel.order must be either " +"lsbf or msbf), all options are displayed between curly brackets, and the " +"one appropriate for the current file is indicated with a \"*\"." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:88 +msgid "" +"The file may also contain the following lines indicating the number of " +"channels of data, and how they are interleaved within the binary data " +"file." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:98 +msgid "The \"image_data\" File" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:100 +msgid "" +"The \"image_data\" file consists of raw binary data, with extents, pixel " +"encoding, and number of channels as indicated in the \"attrib\" file." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:104 +msgid "The \"georef\" File" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:106 +msgid "" +"The \"georef\" file is used to describe the geocoding and projection " +"information for the binary data. For example," +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:125 +msgid "" +"describes an orthogonal latitude/longitude (ll) projected image, with " +"latitudes and longitudes based on the wgs-84 ellipsoid." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:128 +msgid "" +"Since MFF2 version 1.1, top_left refers to the top left corner of the top" +" left pixel. top_right refers to the top right corner of the top right " +"pixel. bottom_left refers to the bottom left corner of the bottom left " +"pixel. bottom_right refers to the bottom right corner of the bottom right" +" pixel. centre refers to the centre of the four corners defined above " +"(center of the image)." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:135 +msgid "" +"Mathematically, for an Npix by Nline image, the corners and centre in " +"(pixel,line) coordinates for MFF2 version 1.1 are:" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:146 +msgid "" +"These calculations are done using floating point arithmetic (i.e. centre " +"coordinates may take on non-integer values)." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:149 +msgid "" +"Note that the corners are always expressed in latitudes/longitudes, even " +"for projected images." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:153 +msgid "Supported projections" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:155 +msgid "" +"ll- Orthogonal latitude/longitude projected image, with latitude parallel" +" to the rows, longitude parallel to the columns. Parameters: spheroid " +"name, projection.origin_longitude (longitude at the origin of the " +"projection coordinates). If not set, this should default to the central " +"longitude of the output image based on its projection boundaries." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:162 +msgid "" +"utm- Universal Transverse Mercator projected image. Parameters: spheroid " +"name, projection.origin_longitude (central meridian for the utm " +"projection). The central meridian must be the meridian at the centre of a" +" UTM zone, i.e. 3 degrees, 9 degrees, 12 degrees, etc. If this is not " +"specified or set a valid UTM central meridian, the reader should reset " +"the value to the nearest valid central meridian based on the central " +"longitude of the output image. The latitude at the origin of the UTM " +"projection is always 0 degrees." +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:172 +msgid "Recognized ellipsoids" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:174 +msgid "" +"MFF2 format associates the following names with ellipsoid equatorial " +"radius and inverse flattening parameters:" +msgstr "" + +#: ../../source/drivers/raster/mff2.rst:211 +msgid "Explanation of fields" +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:5 +msgid "MrSID -- Multi-resolution Seamless Image Database" +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:7 +msgid "MrSID" +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:11 +msgid "" +"MrSID is a wavelet-based image compression technology which can utilize " +"both lossy and lossless encoding. This technology was acquired in its " +"original form from Los Alamos National Laboratories (LANL), where it was " +"developed under the aegis of the U.S. government for storing fingerprints" +" for the FBI. Now it is developed and distributed by Extensis." +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:18 +msgid "" +"This driver supports reading of MrSID image files using Extensis' " +"decoding software development kit (DSDK). **This DSDK is not free " +"software, you should contact Extensis to obtain it (see link at end of " +"this page).** If you are using GCC, please, ensure that you have the same" +" compiler as was used for DSDK compilation. It is C++ library, so you may" +" get incompatibilities in C++ name mangling between different GCC " +"versions (2.95.x and 3.x)." +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:26 +msgid "" +"Latest versions of the DSDK also support decoding JPEG2000 file format, " +"so this driver can be used for JPEG2000 too." +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:39 +msgid "" +"MrSID metadata transparently translated into GDAL metadata strings. Files" +" in MrSID format contain a set of standard metadata tags such as: " +"IMAGE__WIDTH (contains the width of the image), IMAGE__HEIGHT (contains " +"the height of the image), IMAGE__XY_ORIGIN (contains the x and y " +"coordinates of the origin), IMAGE__INPUT_NAME (contains the name or names" +" of the files used to create the MrSID image) etc. GDAL's metadata keys " +"cannot contain characters \\`:' and \\`=', but standard MrSID tags always" +" contain double colons in tag names. These characters replaced in GDAL " +"with \\`_' during translation. So if you are using other software to work" +" with MrSID be ready that names of metadata keys will be shown " +"differently in GDAL." +msgstr "" + +#: ../../source/drivers/raster/mrsid.rst:58 +msgid "" +"MrSID images may contain georeference and coordinate system information " +"in form of GeoTIFF GeoKeys, translated in metadata records. All those " +"GeoKeys properly extracted and used by the driver. Unfortunately, there " +"is one caveat: old MrSID encoders has a bug which resulted in wrong " +"GeoKeys, stored in MrSID files. This bug was fixed in MrSID software " +"version 1.5, but if you have older encoders or files, created with older " +"encoders, you cannot use georeference information from them." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:5 +msgid "MSG -- Meteosat Second Generation" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:7 +msgid "MSG" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:11 +msgid "" +"This driver implements reading support for Meteosat Second Generation " +"files. These are files with names like " +"``H-000-MSG1\\_\\_-MSG1\\_\\_\\_\\_\\_\\_\\_\\_-HRV\\_\\_\\_\\_\\_\\_-000007\\_\\_\\_-200405311115-C\\_``," +" commonly distributed into a folder structure with dates (e.g. " +"``2004\\05\\31`` for the file mentioned)." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:17 +msgid "" +"The MSG files are wavelet-compressed. A decompression library licensed " +"from `EUMETSAT <http://www.eumetsat.int/>`__ is needed (`Public Wavelet " +"Transform Decompression Library Software <https://gitlab.eumetsat.int" +"/open-source/PublicDecompWT>`__, shorter *Wavelet Transform Software*). " +"The software is compilable on Microsoft Windows, Linux and Solaris " +"Operating Systems, and it works on 32 bits and 64 bits as well as mixed " +"architectures. It is licensed under Apache v2." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:28 +msgid "" +"This driver is not \"enabled\" by default. See `Build Instructions " +"<#MSG_Build_Instructions>`__ on how to include this driver in your GDAL " +"library." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:36 +msgid "Build Instructions" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:39 +msgid "CMake builds" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:41 +msgid "See the ``GDAL_USE_PUBLICDECOMPWT`` option of :ref:`building_from_source`." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:44 +msgid "Other build systems" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:46 +msgid "Clone the EUMETSAT library for wavelet decompression into ``frmts/msg``." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:48 +msgid "" +"If you are building with Visual Studio 6.0, extract the .vc makefiles for" +" the PublicDecompWT from the file `PublicDecompWTMakefiles.zip` stored in" +" that directory." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:52 +msgid "" +"If you build using the GNUMakefile, use *--with-msg* option to enable MSG" +" driver:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:59 +msgid "" +"If you find that some adjustments are needed in the makefile and/or the " +"msg source files, please \"commit\" them. The EUMETSAT library promises " +"to be \"platform independent\", but as we are working with Microsoft " +"Windows and Visual Studio 6.0, we did not have the facilities to check if" +" the rest of the msg driver is. Furthermore, apply steps 4 to 7 from the " +":ref:`raster_driver_tut`, section \"Adding Driver to GDAL Tree\"." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:66 +msgid "" +"MSG Wiki page is available at http://trac.osgeo.org/gdal/wiki/MSG. It's " +"dedicated to document building and usage hints" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:70 +msgid "Specification of Source Dataset" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:72 +msgid "" +"It is possible to select individual files for opening. In this case, the " +"driver will gather the files that correspond to the other strips of the " +"same image, and correctly compose the image." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:76 +msgid "Example with gdal_translate.exe:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:84 +msgid "It is also possible to use the following syntax for opening the MSG files:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:87 +msgid "MSG(source_folder,timestamp,(channel,channel,...,channel),use_root_folder,data_conversion,nr_cycles,step)" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:90 +msgid "source_folder: a path to a folder structure that contains the files" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:92 +msgid "" +"timestamp: 12 digits representing a date/time that identifies the 114 " +"files of the 12 images of that time, e.g. 200501181200" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:94 +msgid "" +"channel: a number between 1 and 12, representing each of the 12 available" +" channels. When only specifying one channel, the brackets are optional." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:97 +msgid "" +"use_root_folder: Y to indicate that the files reside directly into the " +"source_folder specified. N to indicate that the files reside in date " +"structured folders: source_folder/YYYY/MM/DD" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:100 +msgid "data_conversion:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:103 +msgid "N to keep the original 10 bits DN values. The result is UInt16." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:104 +msgid "" +"B to convert to 8 bits (handy for GIF and JPEG images). The result is " +"Byte." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:106 +msgid "" +"R to perform radiometric calibration and get the result in " +"mW/m2/sr/(cm-1)-1. The result is Float32." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:108 +msgid "" +"L to perform radiometric calibration and get the result in W/m2/sr/um. " +"The result is Float32." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:110 +msgid "" +"T to get the reflectance for the visible bands (1, 2, 3 and 12) and the " +"temperature in degrees Kelvin for the infrared bands (all other bands). " +"The result is Float32." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:114 +msgid "" +"nr_cycles: a number that indicates the number of consecutive cycles to be" +" included in the same file (time series). These are appended as " +"additional bands." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:117 +msgid "" +"step: a number that indicates what is the stepsize when multiple cycles " +"are chosen. E.g. every 15 minutes: step = 1, every 30 minutes: step = 2 " +"etc. Note that the cycles are exactly 15 minutes apart, so you can not " +"get images from times in-between (the step is an integer)." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:123 +msgid "Examples with gdal_translate utility:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:125 +msgid "" +"Example call to fetch an MSG image of 200501181200 with bands 1, 2 and 3 " +"in IMG format:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:132 +msgid "" +"In JPG format, and converting the 10 bits image to 8 bits by dividing all" +" values by 4:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:139 +msgid "The same, but reordering the bands in the JPEG image to resemble RGB:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:145 +msgid "Geotiff output, only band 2, original 10 bits values:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:151 +msgid "Band 12:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:157 +msgid "The same band 12 with radiometric calibration in mW/m2/sr/(cm-1)-1:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:163 +msgid "" +"Retrieve data from c:\\hrit-data\\2005\\01\\18 instead of " +"\\\\\\pc2133-24002\\RawData\\... :" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:170 +msgid "" +"Another option to do the same (note the difference in the Y and the N for" +" the “use_root_folder” parameter:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:177 +msgid "" +"Without radiometric calibration, but for 10 consecutive cycles (thus from" +" 1200 to 1415):" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:184 +msgid "10 cycles, but every hour (thus from 1200 to 2100):" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:190 +msgid "10 cycles, every hour, and bands 3, 2 and 1:" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:197 +msgid "Georeference and Projection" +msgstr "" + +#: ../../source/drivers/raster/msg.rst:199 +msgid "" +"The images are using the Geostationary Satellite View projection. Most " +"GIS packages don't recognize this projection (we only know of ILWIS that " +"does have this projection), but gdalwarp.exe can be used to re-project " +"the images." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:207 +msgid "Implemented as :source_file:`frmts/msg/msgdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/msg.rst:208 +msgid "" +"http://www.eumetsat.int - European Organisation for the Exploitation of " +"Meteorological Satellites" +msgstr "" + +#: ../../source/drivers/raster/msgn.rst:5 +msgid "MSGN -- Meteosat Second Generation (MSG) Native Archive Format (.nat)" +msgstr "" + +#: ../../source/drivers/raster/msgn.rst:7 +msgid "MSGN" +msgstr "" + +#: ../../source/drivers/raster/msgn.rst:11 +msgid "" +"GDAL supports reading only of MSG native files. These files may have " +"anything from 1 to 12 bands, all at 10-bit resolution." +msgstr "" + +#: ../../source/drivers/raster/msgn.rst:14 +msgid "" +"Includes support for the 12th band (HRV - High Resolution Visible). This " +"is implemented as a subset, i.e., it is accessed by prefixing the " +"filename with the tag \"HRV:\"." +msgstr "" + +#: ../../source/drivers/raster/msgn.rst:18 +msgid "" +"Similarly, it is possible to obtain floating point radiance values in " +"stead of the usual 10-bit digital numbers (DNs). This subset is accessed " +"by prefixing the filename with the tag \"RAD:\"." +msgstr "" + +#: ../../source/drivers/raster/msgn.rst:22 +msgid "" +"Georeferencing is currently supported, but the results may not be " +"acceptable (accurate enough), depending on your requirements. The current" +" workaround is to implement the CGMS Geostationary projection directly, " +"using the code available from EUMETSAT." +msgstr "" + +#: ../../source/drivers/raster/ndf.rst:5 +msgid "NDF -- NLAPS Data Format" +msgstr "" + +#: ../../source/drivers/raster/ndf.rst:7 +msgid "NDF" +msgstr "" + +#: ../../source/drivers/raster/ndf.rst:11 +msgid "" +"GDAL has limited support for reading NLAPS Data Format files. This is a " +"format primarily used by the Eros Data Center for distribution of Landsat" +" data. NDF datasets consist of a header file (often with the extension " +".H1) and one or more associated raw data files (often .I1, .I2, ...). To " +"open a dataset select the header file, often with the extension .H1, .H2 " +"or .HD." +msgstr "" + +#: ../../source/drivers/raster/ndf.rst:18 +msgid "" +"The NDF driver only supports 8bit data. The only supported projection is " +"UTM. NDF version 1 (NDF_VERSION=0.00) and NDF version 2 are both " +"supported." +msgstr "" + +#: ../../source/drivers/raster/ndf.rst:22 +msgid "NOTE: Implemented as :source_file:`frmts/raw/ndfdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/ndf.rst:24 +msgid "" +"See Also: `NLAPS Data Format Specification " +"<http://landsat.usgs.gov/documents/NLAPSII.pdf>`__." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:7 +#: ../../source/drivers/vector/netcdf.rst:8 +msgid "netCDF" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:11 +msgid "" +"This format is supported for read and write access. This page only " +"describes the raster support (you can find documentation for the " +":ref:`vector side <vector.netcdf>`) NetCDF is an interface for array-" +"oriented data access and is used for representing scientific data." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:16 +msgid "" +"The fill value metadata or missing_value backward compatibility is " +"preserved as NODATA value when available." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:19 +msgid "NOTE: Implemented as :source_file:`frmts/netcdf/netcdfdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:33 +msgid "" +"Network Command Data Form is a container for several different arrays " +"most used for storing scientific dataset. One NetCDF file may contain " +"several datasets. They may differ in size, number of dimensions and may " +"represent data for different regions." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:38 +msgid "" +"If the file contains only one NetCDF array which appears to be an image, " +"it may be accessed directly, but if the file contains multiple images it " +"may be necessary to import the file via a two step process." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:42 +msgid "" +"The first step is to get a report of the components images (dataset) in " +"the file using gdalinfo, and then to import the desired images using " +"gdal_translate. The gdalinfo utility lists all multidimensional " +"subdatasets from the input NetCDF file." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:47 +msgid "" +"The name of individual images are assigned to the SUBDATASET_n_NAME " +"metadata item. The description for each image is found in the " +"SUBDATASET_n_DESC metadata item. For NetCDF images will follow this " +"format: *NETCDF:filename:variable_name*" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:52 +msgid "" +"where *filename* is the name of the input file, and *variable_name* is " +"the dataset selected within the file." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:55 +msgid "" +"On the second step you provide this name for **gdalinfo** to get " +"information about the dataset or **gdal_translate** to read dataset." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:58 +msgid "For example, we want to read data from a NetCDF file:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:95 +msgid "" +"This NetCDF files contain 4 datasets, lon_bnds, lat_bnds, tim_bnds and " +"tos. Now select the subdataset, described as: ``NETCDF:\"sst.nc\":tos`` " +"``[24x17x180] sea_surface_temperature (32-bit floating-point)`` and get " +"the information about the number of bands there is inside this variable." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:113 +msgid ".... More metadata" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:143 +msgid ".... More Bands" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:166 +msgid "" +"gdalinfo displays the number of bands into this subdataset. There are " +"metadata attached to each band. In this example, the metadata informs us " +"that each band correspond to an array of monthly sea surface temperature " +"from January 2001. There are 24 months of data in this subdataset. You " +"may also use **gdal_translate** for reading the subdataset." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:172 +msgid "" +"Note that you should provide exactly the contents of the line marked " +"**SUBDATASET_n_NAME** to GDAL, including the **NETCDF:** prefix." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:175 +msgid "" +"The **NETCDF** prefix must be first. It triggers the subdataset NetCDF " +"driver. This driver is intended only for importing remote sensing and " +"geospatial datasets in form of raster images. If you want explore all " +"data contained in NetCDF file you should use another tools." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:180 +msgid "" +"Starting with GDAL 3.5, the :oo:`VARIABLES_AS_BANDS=YES` open option can " +"be used to indicate to the driver that if the netCDF file only contains " +"2D variables of the same type and indexed by the same dimensions, then " +"they should be reported as multiple bands of a same dataset." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:225 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if netCDF`` option to command " +"line utilities accepting it, or ``netCDF`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename, when it is not using subdataset syntax" +" (it can typically be used to force open a HDF5 file that would be " +"nominally recognized by the HDF5 driver)." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:232 +msgid "Dimension" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:234 +msgid "" +"The NetCDF driver assume that data follows the CF-1 convention from " +"`UNIDATA " +"<http://www.unidata.ucar.edu/software/netcdf/docs/conventions.html>`__ " +"The dimensions inside the NetCDF file use the following rules: (Z,Y,X). " +"If there are more than 3 dimensions, the driver will merge them into " +"bands. For example if you have an 4 dimension arrays of the type (P, T, " +"Y, X). The driver will multiply the last 2 dimensions (P*T). The driver " +"will display the bands in the following order. It will first increment T " +"and then P. Metadata will be displayed on each band with its " +"corresponding T and P values." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:247 +msgid "" +"There is no universal way of storing georeferencing in NetCDF files. The " +"driver first tries to follow the CF-1 Convention from UNIDATA looking for" +" the Metadata named \"grid_mapping\". If \"grid_mapping\" is not present," +" the driver will try to find an lat/lon grid array to set geotransform " +"array. The NetCDF driver verifies that the Lat/Lon array is equally " +"spaced." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:254 +msgid "crs_wkt attribute support" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:256 +msgid "" +"If those 2 methods fail, NetCDF driver will try to read the following " +"metadata directly and set up georeferencing." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:259 +msgid "spatial_ref (Well Known Text)" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:261 +msgid "GeoTransform (GeoTransform array)" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:263 +msgid "or," +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:265 +msgid "Northernmost_Northing" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:266 +msgid "Southernmost_Northing" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:267 +msgid "Easternmost_Easting" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:268 +msgid "Westernmost_Easting" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:270 +msgid "" +"See also the configuration options **GDAL_NETCDF_VERIFY_DIMS** and " +"**GDAL_NETCDF_IGNORE_XY_AXIS_NAME_CHECKS** which control this behavior." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:332 +msgid "" +"This driver supports creation of NetCDF file following the CF-1 " +"convention. You may create set of 2D datasets. Each variable array is " +"named Band1, Band2, ... BandN." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:336 +msgid "" +"Each band will have metadata tied to it giving a short description of the" +" data it contains." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:340 +msgid "GDAL NetCDF Metadata" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:342 +msgid "All NetCDF attributes are transparently translated as GDAL metadata." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:344 +msgid "The translation follow these directives:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:346 +msgid "Global NetCDF metadata have a **NC_GLOBAL** tag prefixed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:347 +msgid "Dataset metadata have their **variable name** prefixed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:348 +msgid "Each prefix is followed by a **#** sign." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:349 +msgid "The NetCDF attribute follows the form: **name=value**." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:363 +msgid "NetCDF global attributes" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:369 +msgid "Variables attributes for: tos, lon, lat and time" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:402 +msgid "" +"On writing, when using the CreateCopy() interface or gdal_translate, " +"dataset level metadata that follows the naming convention " +"NC_GLOBAL#key=value will be used to write the netCDF attributes. Metadata" +" set at the band level using key=value will also be used to write " +"variable attributes." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:408 +msgid "Product specific behavior" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:411 +msgid "Sentinel 5" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:415 +msgid "" +"The most verbose metadata is reported in the ``json:ISO_METADATA``, " +"``json:ESA_METADATA``, ``json:EOP_METADATA``, ``json:QA_STATISTICS``, " +"``json:GRANULE_DESCRIPTION``, ``json:ALGORITHM_SETTINGS`` and " +"``json:SUPPORT_DATA`` metadata domains." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:420 +msgid "Can be discovered for example with:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:532 +msgid "Creation of multidimensional files with CreateCopy() 2D raster API" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:534 +msgid "" +"Starting with GDAL 3.1, the preferred way of creating > 2D files is to " +"use the the :ref:`multidim_raster_data_model` API. However it is possible" +" to create such files with the 2D raster API using the CreateCopy() " +"method (note that at time of writing, this is not supported using the " +"Create() method)." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:539 +msgid "" +"The ``NETCDF_DIM_EXTRA={dim1_name,...dimN_name}`` metadata item must be " +"set on the source dataset, where dim1_name is the name of the slowest " +"varying dimension and dimN_name the name of the fastest varying one." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:543 +msgid "" +"For each extra dimension, the " +"``NETCDF_DIM_{dim_name}_DEF={dimension_size,netcdf_data_type}`` metadata " +"item must be set where dimension_size is the size of the dimension " +"(number of samples along that dimension) and netcdf_data_type is the " +"integer value for the netCDF data type of the corresponding indexing " +"variable. Among the most useful data types:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:549 +msgid "4 for Int" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:550 +msgid "5 for Float" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:551 +msgid "6 for Double" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:552 +msgid "10 for Int64" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:554 +msgid "" +"The ``NETCDF_DIM_{dim_name}_VALUES={value1,...valueN}`` is set to define " +"the values of the indexing variable corresponding to dimension." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:557 +msgid "" +"``dim_name#attribute`` metadata items can also be set to define the " +"attributes of the indexing variable of the dimension." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:560 +msgid "Example of creation of a Time,Z,Y,X 4D file in Python:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:621 +#: ../../source/drivers/vector/csv.rst:252 +#: ../../source/drivers/vector/geojson.rst:415 +#: ../../source/drivers/vector/georss.rst:238 +#: ../../source/drivers/vector/gml.rst:792 +#: ../../source/drivers/vector/gpx.rst:385 +#: ../../source/drivers/vector/jsonfg.rst:186 +#: ../../source/drivers/vector/kml.rst:128 +#: ../../source/drivers/vector/libkml.rst:949 +#: ../../source/drivers/vector/lvbag.rst:53 +#: ../../source/drivers/vector/pgdump.rst:256 +#: ../../source/drivers/vector/selafin.rst:405 +msgid "VSI Virtual File System API support" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:623 +msgid "" +"Since GDAL 2.4, and with Linux kernel >=4.3 and libnetcdf >=4.5, read " +"operations on /vsi file systems are supported using the userfaultfd Linux" +" system call. If running from a container, that system call may be " +"unavailable by default. For example with Docker, ``--security-opt " +"seccomp=unconfined`` might be needed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:628 +msgid "" +"Corollary: operations on /vsi file systems are *not* supported on Windows" +" or MacOSX. If the netCDF file is a NetCDF 4 / HDF5 file, and the HDF5 " +"driver is available, you may set the :config:`GDAL_SKIP` configuration " +"option to ``netCDF`` to force the use of the HDF5 driver. Note that " +"specificities of the netCDF driver, such as support georeferencing with " +"the netCDF CF conventions, will not be available." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:637 +msgid "NetCDF-4 groups support on reading (GDAL >= 3.0)" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:639 +msgid "" +"The driver has undergone significant changes in GDAL 3.0 to support " +"NetCDF-4 groups on reading:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:642 +msgid "Explore recursively all nested groups to create the subdatasets list" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:644 +msgid "" +"Subdatasets in nested groups use the /group1/group2/.../groupn/var " +"standard NetCDF-4 convention, except for variables in the root group " +"which do not have a leading slash for backward compatibility with the " +"NetCDF-3 driver" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:649 +msgid "" +"Global attributes of each nested group are also collected in the GDAL " +"dataset metadata, using the same convention " +"/group1/group2/.../groupn/NC_GLOBAL#attr_name, except for the root group " +"which do not have a leading slash for backward compatibility" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:654 +msgid "" +"When searching for a variable containing auxiliary information on the " +"selected subdataset, like coordinate variables or grid_mapping, we now " +"also search in parent groups and their children as specified in `Support " +"of groups in CF <https://github.com/cf-convention/cf-" +"conventions/issues/144>`__" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:665 +msgid "" +"The netCDF driver supports the :ref:`multidim_raster_data_model` for " +"reading and creation operations." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:668 +msgid "" +"The :cpp:func:`GDALGroup::GetGroupNames` method supports the following " +"options:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:670 +msgid "" +"GROUP_BY=SAME_DIMENSION. If set, single-dimensional variables will be " +"exposed as a \"virtual\" subgroup. This enables the user to get a clearer" +" organization of variables, for example in datasets where variables " +"belonging to different trajectories are indexed by different dimensions " +"but mixed in the same netCDF group." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:676 +msgid "" +"The :cpp:func:`GDALGroup::OpenGroup` method supports the following " +"options:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:678 +msgid "GROUP_BY=SAME_DIMENSION. See above description" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:680 +msgid "" +"The :cpp:func:`GDALGroup::GetMDArrayNames` method supports the following " +"options:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:682 +msgid "" +"SHOW_ALL=YES/NO. Defaults to NO. If set to YES, all variables will be " +"listed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:683 +msgid "" +"SHOW_ZERO_DIM=YES/NO. Defaults to NO. If set to NO, variables with " +"0-dimension will not be listed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:685 +msgid "" +"SHOW_COORDINATES=YES/NO. Defaults to YES. If set to NO, variables " +"refererenced in the ``coordinates`` attribute of another variable will " +"not be listed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:687 +msgid "" +"SHOW_BOUNDS=YES/NO. Defaults to YES. If set to NO, variables refererenced" +" in the ``bounds`` attribute of another variable will not be listed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:689 +msgid "" +"SHOW_INDEXING=YES/NO. Defaults to YES. If set to NO, single-dimensional " +"variables whose name is equal to the name of their indexing variable will" +" not be listed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:692 +msgid "" +"SHOW_TIME=YES/NO. Defaults to YES. If set to NO, single-dimensional " +"variables whose ``standard_name`` attribute is \"time\" will not be " +"listed." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:695 +msgid "" +"GROUP_BY=SAME_DIMENSION. If set, single-dimensional variables will not be" +" listed" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:697 +msgid "" +"The :cpp:func:`GDALGroup::OpenMDArray` method supports the following " +"options:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:699 +msgid "" +"USE_DEFAULT_FILL_AS_NODATA=YES/NO. (GDAL >= 3.6) Defaults to NO. If set " +"to YES, the default fill value will be used as nodata when there is no " +"_FillValue or missing_value attribute (except on variables of type Byte, " +"UByte, Char)" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:703 +msgid "" +"The :cpp:func:`GDALGroup::CreateMDArray` method supports the following " +"options:" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:705 +msgid "" +"NC_TYPE=NC_CHAR/NC_BYTE/NC_INT64/NC_UINT64: to overload the netCDF data " +"type normally deduced from the GDAL data type passed to CreateMDArray(). " +"NC_CHAR can only be used for strings of a fixed size." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:708 +msgid "" +"BLOCKSIZE=size_dim0,size_dim1,...,size_dimN: to set the netCDF chunk " +"size, as set by nc_def_var_chunking(). There must be exactly as many " +"values as the number of dimensions passed to CreateMDArray()" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:711 +msgid "COMPRESS=DEFLATE: to ask for deflate compression" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:712 +msgid "ZLEVEL=number: DEFLATE compression level (1-9)" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:713 +msgid "" +"CHECKSUM=YES/NO: Whether to turn on Fletcher32 checksums. Checksum " +"generation requires chunking, and if no explicit chunking has been asked " +"with the BLOCKSIZE option, a default one will be used. Defaults to NO." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:716 +msgid "" +"FILTER=filterid,param1,...,paramN: Define a filter (typically a " +"compression method) used for writing. This should be a list of numeric " +"values, separated by commas. The first value is the filter id (list of " +"potential values at " +"https://support.hdfgroup.org/services/contributions.html#filters) and " +"following values are per-filter parameters. More details about netCDF-4 " +"filter support at https://www.unidata.ucar.edu/software/netcdf/docs" +"/md__Users_wfisher_Desktop_docs_netcdf-c_docs_filters.html" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:726 +msgid "This driver is compiled with the UNIDATA NetCDF library." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:728 +msgid "" +"You need to download or compile the NetCDF library before configuring " +"GDAL with NetCDF support." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:731 +msgid "" +"See `NetCDF GDAL wiki <http://trac.osgeo.org/gdal/wiki/NetCDF>`__ for " +"build instructions and information regarding HDF4, NetCDF-4 and HDF5." +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:737 +msgid ":ref:`Vector side of the netCDF driver. <vector.netcdf>`" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:738 +msgid "" +"`NetCDF CF-1.5 convention <http://cf-pcmdi.llnl.gov/documents/cf-" +"conventions/1.5/cf-conventions.html>`__" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:740 +#: ../../source/drivers/vector/netcdf.rst:500 +msgid "" +"`NetCDF compiled libraries " +"<http://www.unidata.ucar.edu/downloads/netcdf/index.jsp>`__" +msgstr "" + +#: ../../source/drivers/raster/netcdf.rst:742 +#: ../../source/drivers/vector/netcdf.rst:502 +msgid "" +"`NetCDF Documentation " +"<http://www.unidata.ucar.edu/software/netcdf/docs/>`__" +msgstr "" + +#: ../../source/drivers/raster/ngsgeoid.rst:5 +msgid "NGSGEOID - NOAA NGS Geoid Height Grids" +msgstr "" + +#: ../../source/drivers/raster/ngsgeoid.rst:7 +msgid "NGSGEOID" +msgstr "" + +#: ../../source/drivers/raster/ngsgeoid.rst:11 +msgid "" +"GDAL supports reading NOAA NGS geoid height grids in binary format (.bin " +"files). Those files can be used for vertical datum transformations." +msgstr "" + +#: ../../source/drivers/raster/ngsgeoid.rst:24 +msgid "" +"`Description of NGS Geoid Height Grids format " +"<http://www.ngs.noaa.gov/GEOID/USGG2009/s2009rme.txt>`__" +msgstr "" + +#: ../../source/drivers/raster/ngsgeoid.rst:26 +msgid "`GEOID09 main page <http://www.ngs.noaa.gov/PC_PROD/GEOID09/>`__" +msgstr "" + +#: ../../source/drivers/raster/ngsgeoid.rst:27 +msgid "`USGG2009 main page <http://www.ngs.noaa.gov/PC_PROD/USGG2009/>`__" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:4 ../../source/drivers/vector/ngw.rst:4 +msgid "NGW -- NextGIS Web" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:8 ../../source/drivers/vector/ngw.rst:8 +msgid "NGW" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:12 +#: ../../source/drivers/vector/ngw.rst:12 +msgid "" +"NextGIS Web - is a server GIS, which allows storing and editing geodata " +"and to display maps in web browser. Also NextGIS Web can share geodata " +"with other NextGIS software." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:16 +#: ../../source/drivers/vector/ngw.rst:16 +msgid "NextGIS Web has the following features:" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:18 +#: ../../source/drivers/vector/ngw.rst:18 +msgid "" +"Display maps in a web browser (different maps with different layers and " +"styles)" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:20 +#: ../../source/drivers/vector/ngw.rst:20 +msgid "Flexible permissions management" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:21 +#: ../../source/drivers/vector/ngw.rst:21 +msgid "" +"Load geodata from PostGIS or import from GIS formats (ESRI Shape, GeoJSON" +" or GeoTIFF)" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:23 +#: ../../source/drivers/vector/ngw.rst:23 +msgid "" +"Load vector geodata in the following formats: GeoJSON, CSV, ESRI Shape, " +"Mapinfo tab" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:25 +#: ../../source/drivers/vector/ngw.rst:25 +msgid "Import map styles from QGIS project or set them manually" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:26 +#: ../../source/drivers/vector/ngw.rst:26 +msgid "Act as a server for TMS, WMS, MVT, WFS" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:27 +#: ../../source/drivers/vector/ngw.rst:27 +msgid "Act as a client for WMS" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:28 +#: ../../source/drivers/vector/ngw.rst:28 +msgid "" +"User can add photos to records, change record attributes via web " +"interface or WFS-T protocol" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:31 +#: ../../source/drivers/vector/ngw.rst:31 +msgid "" +"NextGIS Web - is an open source software (license GPL v2+, see `GNU " +"General Public License, version 2 <https://www.gnu.org/licenses/old-" +"licenses/gpl-2.0.en.html>`__)." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:41 +#: ../../source/drivers/vector/ngw.rst:41 +msgid "Driver" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:43 +msgid "NextGIS Web supports several raster types:" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:45 +msgid "Raster style" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:46 +msgid "Vector style" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:47 +msgid "WMS layer" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:48 +msgid "WMS Service" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:49 +msgid "Web map as combination of raster and vector styles" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:51 +msgid "" +"Each NextGIS Web raster layer can have one or more raster styles. Each " +"NextGIS Web vector or PostGIS layer can have one or more vector styles " +"(QGIS qml or MapServer xml). WMS layers from external WMS service have no" +" styles. WMS Service is usual WMS protocol implementation." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:57 +msgid "" +"NGW driver supports only raster and vector styles and WMS layers. You can" +" get raster data as tiles or image (only tiles are supported now)." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:61 +msgid "" +"The driver supports read and copy from existing source dataset operations" +" on rasters." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:67 +#: ../../source/drivers/vector/ngw.rst:50 +msgid "" +"The minimal syntax to open a NGW datasource is: NGW:[NextGIS Web " +"URL][/resource/][resource identifier]" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:70 +msgid "" +"**NextGIS Web URL** may be an url to nextgis.com cloud service (for " +"example, https://demo.nextgis.com), or some other url including port and " +"additional path (for example, http://192.168.1.1:8000/test)." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:73 +#: ../../source/drivers/vector/ngw.rst:56 +msgid "" +"**resource** is mandatory keyword dividing resource identifier from the " +"rest of URL." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:75 +#: ../../source/drivers/vector/ngw.rst:58 +msgid "" +"**resource identifier** this is positive number from 0 and above. This " +"may be a resource group, vector, PostGIS or raster layer, style." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:78 +msgid "" +"If identifier is resource group, all vector layers, PostGIS, raster " +"layers, styles will be listed as child resources. In other case this will" +" be a separate raster." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:85 +#: ../../source/drivers/raster/stacta.rst:27 +#: ../../source/drivers/vector/amigocloud.rst:127 +#: ../../source/drivers/vector/carto.rst:182 +#: ../../source/drivers/vector/csv.rst:495 +#: ../../source/drivers/vector/csw.rst:91 +#: ../../source/drivers/vector/dwg.rst:41 +#: ../../source/drivers/vector/edigeo.rst:41 +#: ../../source/drivers/vector/eeda.rst:65 +#: ../../source/drivers/vector/filegdb.rst:246 +#: ../../source/drivers/vector/geojson.rst:153 +#: ../../source/drivers/vector/gml.rst:38 +#: ../../source/drivers/vector/gpkg.rst:487 +#: ../../source/drivers/vector/gpx.rst:54 +#: ../../source/drivers/vector/jsonfg.rst:86 +#: ../../source/drivers/vector/mitab.rst:188 +#: ../../source/drivers/vector/mssqlspatial.rst:218 +#: ../../source/drivers/vector/ngw.rst:67 +#: ../../source/drivers/vector/oci.rst:127 +#: ../../source/drivers/vector/ods.rst:64 +#: ../../source/drivers/vector/ogdi.rst:70 +#: ../../source/drivers/vector/openfilegdb.rst:85 +#: ../../source/drivers/vector/osm.rst:87 +#: ../../source/drivers/vector/pdf.rst:93 +#: ../../source/drivers/vector/pg.rst:398 +#: ../../source/drivers/vector/pgdump.rst:250 +#: ../../source/drivers/vector/pgeo.rst:61 +#: ../../source/drivers/vector/plscenes_data_v1.rst:123 +#: ../../source/drivers/vector/shapefile.rst:414 +#: ../../source/drivers/vector/sqlite.rst:427 +#: ../../source/drivers/vector/vfk.rst:54 +#: ../../source/drivers/vector/wasp.rst:25 +#: ../../source/drivers/vector/wfs.rst:366 +#: ../../source/drivers/vector/xls.rst:22 +#: ../../source/drivers/vector/xlsx.rst:73 +msgid "|about-config-options| The following configuration options are available:" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:117 +#: ../../source/drivers/vector/ngw.rst:102 +msgid "" +"Any operations (read, write, get metadata, change properties, etc.) may " +"require an authenticated access. Authenticated access is obtained by " +"specifying user name and password in open, create or configuration " +"options." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:154 +msgid "Create copy options" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:156 +msgid "" +"NextGIS Web supports only GeoTIFF file format. Prior version 3.1 " +"supported only 3 (RGB) or 4 (RGBA) bands rasters with datatype Byte. In " +"CreateCopy function if source dataset has GeoTIFF file format it will " +"copy as is. For other formats the additional transformation to temporary " +"GeoTIFF file will execute." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:161 +msgid "The following copy options are available:" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:163 +msgid "KEY - Key value. Must be unique in whole NextGIS Web instance. Optional." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:164 +msgid "DESCRIPTION - Resource description. Optional." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:165 +msgid "" +"RASTER_STYLE_NAME - Raster style name. Optional. Default is same as " +"raster layer name." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:167 +msgid "" +"RASTER_QML_PATH - Path to QGIS QML raster style file. Optional for " +"RGB/RGBA, for other bands count/pixel types is mandatory." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:169 +msgid "USERPWD - Username and password, separated by colon." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:170 +msgid "" +"CACHE_EXPIRES=604800 - Time in seconds cached files will stay valid. If " +"cached file expires it is deleted when maximum size of cache is reached. " +"Also expired file can be overwritten by the new one from web. Defaults to" +" 604800 (7 days)." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:174 +msgid "" +"CACHE_MAX_SIZE=67108864 - The cache maximum size in bytes. If cache " +"reached maximum size, expired cached files will be deleted. Defaults to " +"67108864 (64Mb)." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:177 +msgid "" +"JSON_DEPTH=32 - The depth of json response that can be parsed. If depth " +"is greater than this value, parse error occurs." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:183 +msgid "" +"NextGIS Web metadata are supported in datasource, vector, PostGIS, raster" +" layers and styles. Metadata are stored at specific domain \"NGW\". " +"NextGIS Web supported metadata are strings and numbers. Metadata keys " +"with decimal numbers will have suffix **.d** and for real numbers - " +"**.f**. To create new metadata item, add new key=value pair in NGW domain" +" use the *SetMetadataItem* function and appropriate suffix. During " +"transferring to NextGIS Web, suffix will be omitted. You must ensure that" +" numbers correctly transform from string to number." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:192 +#: ../../source/drivers/vector/ngw.rst:290 +msgid "" +"Resource description and key map to appropriate *description* and " +"*keyname* metadata items in default domain. Changing those metadata items" +" will cause an update of resource properties." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:196 +#: ../../source/drivers/vector/ngw.rst:294 +msgid "" +"Resource creation date, type and parent identifier map to appropriate " +"read-only metadata items *creation_date*, *resource_type* and *parent_id*" +" in default domain." +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:203 +msgid "Read datasource contensts (1730 is resource group identifier):" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:209 +msgid "Read raster details (1734 is raster layer identifier):" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:218 +msgid ":ref:`Vector side of the driver <vector.ngw>`" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:219 +msgid "" +"`NextGIS Web documentation " +"<http://docs.nextgis.com/docs_ngweb/source/toc.html>`__" +msgstr "" + +#: ../../source/drivers/raster/ngw.rst:221 +msgid "" +"`NextGIS Web for developers " +"<http://docs.nextgis.com/docs_ngweb_dev/doc/toc.html>`__" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:5 +msgid "NITF -- National Imagery Transmission Format" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:7 +msgid "NITF" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:17 +msgid "" +"GDAL supports reading of several subtypes of NITF (National Imagery " +"Transmission Format) image files, and writing simple NITF 2.1 files. NITF" +" 1.1, NITF 2.0, NITF 2.1 and NSIF 1.0 files with uncompressed, ARIDPCM " +"(Adaptive Recursive Interpolated Differential Pulse Code Modulation), " +"JPEG compressed, JPEG2000 (with Kakadu, ECW SDKs or other JPEG2000 " +"capable driver) or VQ (Vector Quantized) compressed images should be " +"readable." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:23 +msgid "" +"The read support test has been tested on various products, including CIB " +"(Controlled Image Base) and CADRG (Compressed ARC Digitized Raster " +"Graphics) frames from RPF (Raster Product Format) products, ECRG " +"(Enhanced Compressed Raster Graphics) frames, HRE (High Resolution " +"Elevation) products." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:28 +msgid "" +"Color tables for pseudocolored images are read. In some cases nodata " +"values may be identified." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:31 +msgid "" +"Lat/Long extents are read from the IGEOLO (Image GeoLocation) information" +" in the image header if available. If high precision lat/long " +"georeferencing information is available in RPF auxiliary data it will be " +"used in preference to the low precision IGEOLO information. In case a " +"BLOCKA (Image Block Information) instance is found, the higher precision " +"coordinates of BLOCKA are used if the block data covers the complete " +"image - that is the L_LINES field with the row count for that block is " +"equal to the row count of the image. Additionally, all BLOCKA instances " +"are returned as metadata. If GeoSDE TRE (Tagged Record Extension) are " +"available, they will be used to provide higher precision coordinates. If " +"the RPC00B (or RPC00A) TRE is available, it is used to report RPC (Rapid " +"Positioning Capability / Rational Polynomial Coefficients) metadata. " +"Starting with GDAL 2.2, RPC information can be retrieved from \\_rpc.txt " +"files, and they will be used in priority over internal RPC00B values, " +"since the latter have less precision than the ones stored in external " +"\\_rpc.txt." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:48 +msgid "" +"Most file header and image header fields are returned as dataset level " +"metadata." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:90 +msgid "" +"On export NITF files are always written as NITF 2.1 with one image and no" +" other auxiliary layers. Images are uncompressed by default, but JPEG and" +" JPEG2000 compression are also available. Georeferencing can only be " +"written for images using a geographic coordinate system or a UTM WGS84 " +"projection. Coordinates are implicitly treated as WGS84 even if they are " +"actually in a different geographic coordinate system. Pseudo-color tables" +" may be written for 8bit images." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:98 +msgid "" +"In addition to the export oriented CreateCopy() API, it is also possible " +"to create a blank NITF file using Create() and write imagery on demand. " +"However, using this methodology writing of pseudocolor tables and " +"georeferencing is not supported unless appropriate IREP (Image " +"Representation) and ICORDS (Image Coordinate) creation options are " +"supplied." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:104 +msgid "" +"Most file header, imagery header metadata and security fields can be set " +"with appropriate **creation options** (although they are reported as " +"metadata item, but must not be set as metadata). For instance setting " +"`\"FTITLE=Image of abandoned missile silo south west of Karsk\"` in the " +"creation option list would result in setting of the FTITLE field in the " +"NITF file header. Use the official field names from the NITF " +"specification document; do not put the \"NITF\\_\" prefix that is " +"reported when asking the metadata list." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:123 +msgid "NC is the default value, and means no compression." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:124 +msgid "" +"C3 means JPEG compression and is only available for the CreateCopy() " +"method. The QUALITY and PROGRESSIVE JPEG-specific creation options can be" +" used. See the :ref:`raster.jpeg` driver. Multi-block images can be " +"written." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:128 +msgid "" +"M3 is a variation of C3. The only difference is that a block map is " +"written, which allow for fast seeking to any block." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:130 +msgid "" +"C8 means JPEG2000 compression (one block) and is available for " +"CreateCopy() and/or Create() methods. See below paragraph for " +"specificities." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:303 +msgid "JPEG2000 compression (write support)" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:305 +msgid "" +"JPEG2000 compression is available when using the IC=C8 creation option, " +"if the JP2ECW (SDK 3.3, or for later versions assuming the user has the " +"key to enable JPEG2000 writing), JP2KAK or JP2OpenJPEG driver are " +"available." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:309 +msgid "" +"They are tried in that order when several ones are available, unless the " +"JPEG2000_DRIVER creation option (added in GDAL 3.4) is set to explicitly " +"specify the JPEG2000 capable driver to use." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:313 +msgid "" +":ref:`JP2ECW <raster.jp2ecw>`: The :co:`drivers/raster/jp2ecw TARGET` " +"(target size reduction as a percentage of the original) and " +":co:`drivers/raster/jp2ecw PROFILE`\\ " +"=BASELINE_0/BASELINE_1/BASELINE_2/NPJE/EPJE JP2ECW-specific creation " +"options can be used. Both CreateCopy() and/or Create() methods are " +"available. By default the NPJE PROFILE will be used (thus implying " +"BLOCKXSIZE=BLOCKYSIZE=1024)." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:319 +msgid "" +":ref:`JP2KAK <raster.jp2kak>`: The :co:`drivers/raster/jp2kak QUALITY`, " +":co:`drivers/raster/jp2kak BLOCKXSIZE`, :co:`drivers/raster/jp2kak " +"BLOCKYSIZE`, :co:`drivers/raster/jp2kak LAYERS`, " +":co:`drivers/raster/jp2kak ROI` JP2KAK-specific creation options can be " +"used. Only CreateCopy() method is available." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:327 +msgid "" +":ref:`JP2OpenJPEG <raster.jp2openjpeg>`: (only in the CreateCopy() case)." +" The :co:`drivers/raster/jp2openjpeg QUALITY`, " +":co:`drivers/raster/jp2openjpeg BLOCKXSIZE` and " +":co:`drivers/raster/jp2openjpeg BLOCKYSIZE` JP2OpenJPEG-specific creation" +" options can be used. By default BLOCKXSIZE=BLOCKYSIZE=1024 will be used." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:335 +msgid "" +"Starting with GDAL 3.4.0 and OpenJPEG 2.5, the " +"PROFILE=NPJE_VISUALLY_LOSSLESS/NPJE_NUMERICALLY_LOSSLESS creation option " +"can be used to create files that comply with `STDI-0006 NITF Version 2.1 " +"Commercial Dataset Requirements Document (NCDRD) " +"<https://gwg.nga.mil/ntb/baseline/docs/stdi0006/STDI-0006-NCDRD-" +"16Feb06.doc>`__. For NPJE_VISUALLY_LOSSLESS, the last quality layer " +"defaults to 3.9 bits per pixel and per band. It can be adjusted with the " +"QUALITY creation option. When those profiles are specified, the J2KLRA " +"TRE will also be written, unless the ``J2KLRA=NO`` creation option is " +"specified." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:347 +msgid ":ref:`Advanced GDAL NITF Driver Information <raster.nitf_advanced>`" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:348 +msgid "`NITFS Technical Board Public Page <http://www.gwg.nga.mil/ntb/>`__" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:349 +msgid "" +"`DIGEST Part 2 Annex D (describe encoding of NITF Spatial Data " +"Extensions) " +"<http://www.gwg.nga.mil/ntb/baseline/docs/digest/part2_annex_d.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:351 +msgid "" +":ref:`raster.rpftoc`: to read the Table Of Contents of CIB and CADRG " +"products." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:352 +#: ../../source/drivers/raster/rpftoc.rst:57 +msgid "" +"`MIL-PRF-89038 <http://www.everyspec.com/MIL-PRF/MIL-" +"PRF+%28080000+-+99999%29/MIL-PRF-89038_25371/>`__ : specification of RPF," +" CADRG, CIB products" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:354 +msgid ":ref:`raster.ecrgtoc`: to read the Table Of Contents of ECRG products." +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:359 +msgid "Credit" +msgstr "" + +#: ../../source/drivers/raster/nitf.rst:361 +msgid "" +"The author wishes to thank `AUG Signals <http://www.augsignals.com/>`__ " +"and the `GeoConnections <http://geoconnections.org/>`__ program for " +"supporting development of this driver, and to thank Steve Rawlinson " +"(JPEG), Reiner Beck (BLOCKA) for assistance adding features." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:5 +msgid "NITF -- Advanced Driver Information" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:7 +msgid "" +"The NITF (National Imagery Transmission Format) driver in GDAL includes a" +" number of advanced, and somewhat esoteric options not suitable for the " +":ref:`general end user documentation <raster.nitf>` for the driver. This " +"information is collected here, and is primarily aimed at developers and " +"advanced users." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:14 +msgid "CGM Segments" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:16 +msgid "" +"NITF files that have CGM data (that is segment type GR - graphics, or SY " +"with an STYPE value of 'C') will make that information available as " +"metadata in the CGM domain. The returned metadata will look something " +"like:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:32 +msgid "" +"The SLOC_ROW and SLOC_COL values are the placement of the CGM object " +"relative to the base (SALVL) image. The CCS_ROW/COL values are relative " +"to the common coordinate system. The \\_SDLVL is the display level. The " +"DATA is the raw CGM data with \"backslash quotable\" escaping applied. " +"All occurrences of ASCII zero will be translated to '\\0', and all " +"backslashes and double quotes will be backslashed escaped. The " +"CPLUnescapeString() function can be used to unescape the data into binary" +" format using scheme CPLES_BackslashQuotable." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:41 +msgid "" +"To add CGM data to a NITF image, you can pass creation options in the " +"following format:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:53 +msgid "" +"Notice that passing CGM as creation options will overwrite existing CGM " +"segment read in the CGM metadata domain." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:56 +msgid "" +"While GDAL does not support parsing or rendering CGM data, at least one " +"user has found the `UniConverter " +"<http://sk1project.org/modules.php?name=Products&product=uniconvertor>`__" +" library useful for this purpose." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:62 +msgid "Multi-Image NITF Files" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:64 +msgid "" +"NITF files with more than one image segment (IM) will present the image " +"segments as subdatasets. Opening a multiple NITF file by filename will " +"provide access to the first image segment. The subdataset metadata for a " +"3 image NITF file might look like:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:79 +msgid "" +"In this case opening \"multi_image_jpeg_2.0.ntf\" directly will give " +"access to \"NITF_IM:0:multi_image_jpeg_2.0.ntf\". To open the others use " +"the corresponding subdataset names. The Subdataset mechanism is generic " +"GDAL concept discussed in the :ref:`raster_data_model` document." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:85 +msgid "Text Segments" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:87 +msgid "" +"NITF files that have text segments (that is segment type TX) will make " +"that information available as metadata in the TEXT domain. The returned " +"metadata will look something like:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:108 +msgid "" +"The argument to DATA_n is the raw text of the n'th (zero based) text " +"segment with no escaping of any kind applied." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:111 +msgid "" +"The TEXT segment header data is preserved in HEADER_n metadata item. The " +"CreateCopy() method on the NITF driver also supports creating text " +"segments on the output file as long as the input file has metadata in the" +" TEXT domain as defined above." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:116 +msgid "" +"To add TEXT data to a NITF image, you can also pass creation options in " +"the following format:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:126 +msgid "" +"Notice that passing TEXT as creation options will overwrite existing text" +" segment read in the TEXT metadata domain." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:130 +msgid "TREs" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:132 +msgid "" +"NITF files with registered (or unregistered?) extensions on the file " +"header, or the referenced image header will make them available in a raw " +"form in metadata via the TRE domain. The TRE domain will hold one " +"metadata item per TRE which will have the name of the TRE as the name, " +"and the data of the TRE as the contents. The data contents will be " +"\"backslash escaped\" like CGM data above." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:139 +msgid "" +"In case of multiple occurrences of the same TRE, the second occurrence " +"will be named \"TRENAME_2\", the third \"TRENAME_3\" where TRENAME is the" +" TRE name." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:157 +msgid "TREs as xml:TRE" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:159 +msgid "" +"All TREs found in file and matching one of the TRE description of the " +"`nitf_spec.xml " +"<http://trac.osgeo.org/gdal/browser/trunk/gdal/data/nitf_spec.xml>`__ in " +"GDAL data directory will be reported as XML content in the xml:TRE " +"metadata domain." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:217 +msgid "TRE creation from hexadecimal data" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:219 +msgid "" +"TRE data can be added to a newly created NITF file in hexadecimal format " +"to encode binary data such as unsigned int or floating point types. The " +"hexadecimal TRE creation option is supplied as " +"\"TRE=HEX/<tre_name>=<hex_tre_data>\" or " +"\"FILE_TRE=HEX/<tre_name>=<hex_tre_data>" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:229 +msgid "TRE creation as TRE_OVERFLOW DES" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:231 +msgid "" +"The following example shows how to create a CSEPHA TRE as a TRE_OVERFLOW " +"DES:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:262 +msgid "" +"Note the use of the RESERVE_SPACE_FOR_TRE_OVERFLOW=YES creation option to" +" reserve space for the IXSOFL field in the image subheader pointed by " +"DESITEM." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:267 +msgid "Data Extension Segments (xml:DES)" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:268 +msgid "" +"Data Extension Segments (DESs) are user-defined metadata extensions to " +"the NITF format. The DES metadata is available through the xml\\:DES " +"metadata domain. The xml\\:DES domain returns an XML string with " +"standard and user-defined DES fields in plain text, and the user-defined " +"DES data as Base64 encoded text. The following is an example XML " +"structure:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:289 +msgid "Raw File / Image Headers" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:291 +msgid "" +"In some cases application may need to recover very specific information " +"from the image or file headers that isn't normally available as metadata." +" In this case it is possible to query the \"NITF_METADATA\" metadata " +"domain. The complete file and image headers will be returned as metadata " +"in base64 encoded format. Something like:" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:303 +msgid "" +"Note that the ascii encoded numeric values prefixing the base64 encoded " +"header is the length (decoded) in bytes, followed by one space." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:307 +msgid "Writing multiple Image Segments" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:309 +msgid "(GDAL >= 3.4)" +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:311 +msgid "" +"Writing a NITF file with several image segments is done with the " +"``APPEND_SUBDATASET=YES`` creation option but requires some care." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:314 +msgid "" +"The file must be created with the content of the first image segment with" +" the ``NUMI`` creation option to specify the total number of image " +"segments and optionally with the ``NUMDES`` creation option with the " +"number of DE segments. TREs that apply to the whole file should also be " +"specified at that stage. The ``APPEND_SUBDATASET`` creation option must " +"NOT be specified." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:320 +msgid "" +"Subsequent images are appended with the ``APPEND_SUBDATASET=YES`` " +"creation option. The ``IDLVL``, ``IALVL``, ``ILOCROW`` and ``ILOCCOL`` " +"creation option may be specified." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:323 +msgid "" +"On the last image segment, the DES content, if any must be specified with" +" the ``DES`` creation option." +msgstr "" + +#: ../../source/drivers/raster/nitf_advanced.rst:326 +msgid "The file will only be valid if all NUMI images have been actually written." +msgstr "" + +#: ../../source/drivers/raster/noaa_b.rst:5 +msgid "NOAA_B -- NOAA GEOCON/NADCON5 .b format" +msgstr "" + +#: ../../source/drivers/raster/noaa_b.rst:9 +msgid "NOAA_B" +msgstr "" + +#: ../../source/drivers/raster/noaa_b.rst:13 +msgid "" +"GDAL supports reading geodetic grids in the NOAA .b binary format used " +"for GEOCON and NADCON5 grids." +msgstr "" + +#: ../../source/drivers/raster/noaa_b.rst:26 +msgid "" +"`Format specification " +"<https://geodesy.noaa.gov/library/pdfs/NOAA_TR_NOS_NGS_0063.pdf>`__: See " +"paragraph 10.2, \".b grids (GEOCON and NADCON 5.0)\"" +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:5 +msgid "NSIDCbin -- National Snow and Ice Data Centre Sea Ice Concentrations" +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:7 +msgid "NSIDCbin" +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:14 +msgid "" +"Supported by GDAL for read access. This format is a raw binary format for" +" the Nimbus-7 SMMR and DMSP SSM/I-SSMIS Passive Microwave Data sea ice " +"concentrations. There are daily and monthly maps in the north and south " +"hemispheres supported by this driver." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:19 +msgid "" +"Support includes an affine georeferencing transform, and projection - " +"these are both 25000m resolution polar stereographic grids centred on the" +" north and south pole respectively. Metadata from the file including " +"julian day and year are recorded." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:24 +msgid "" +"This driver is implemented based on the NSIDC documentation in the `User " +"Guide <https://nsidc.org/data/nsidc-0051>`__." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:26 +msgid "" +"Band values are Byte, sea ice concentration (fractional coverage scaled " +"by 250)." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:28 +msgid "" +"The dataset band implements GetScale() which will convert the values from" +" 0,255 to 0.0,102.0 by multiplying by 0.4. Unscaled values above 250 have" +" specific meanings, 251 is Circular mask used in the Arctic, 252 is " +"Unused, 253 is Coastlines, 254 is Superimposed land mask, 255 is Missing " +"data." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:33 +msgid "NOTE: Implemented as :source_file:`frmts/raw/nsidcbindataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:43 +#: ../../source/drivers/vector/esrijson.rst:73 +#: ../../source/drivers/vector/georss.rst:248 +#: ../../source/drivers/vector/gpx.rst:395 +#: ../../source/drivers/vector/idb.rst:67 +#: ../../source/drivers/vector/kml.rst:138 +#: ../../source/drivers/vector/oci.rst:314 +#: ../../source/drivers/vector/pdf.rst:59 +#: ../../source/drivers/vector/pgdump.rst:265 +#: ../../source/drivers/vector/sqlite.rst:561 +msgid "Example" +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:45 +msgid "" +"For example, we want to read monthly data from September 2019, with data " +"from this source (requires authentication)." +msgstr "" + +#: ../../source/drivers/raster/nsidcbin.rst:47 +msgid "<https://n5eil01u.ecs.nsidc.org/PM/NSIDC-0051.001/2018.09.01/nt_201809_f17_v1.1_s.bin>" +msgstr "" + +#: ../../source/drivers/raster/ntv2.rst:5 +msgid "NTv2 -- NTv2 Datum Grid Shift" +msgstr "" + +#: ../../source/drivers/raster/ntv2.rst:7 +msgid "NTv2" +msgstr "" + +#: ../../source/drivers/raster/ntv2.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/raw/ntv2dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:5 +msgid "NWT_GRD/NWT_GRC -- Northwood/Vertical Mapper File Format" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:7 +msgid "NWT_GRD" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:9 +msgid "NWT_GRC" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:13 +msgid "" +"Support for reading & writing Northwood GRID raster formats. This format " +"is also known as Vertical Mapper Grid or MapInfo Grid and is commonly " +"used in MapInfo Pro software" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:17 +msgid "" +"Full read/write support of \\*.grd (grid) files is available, read-only " +"support is available for classified grids (\\*.grc)." +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:20 +msgid "For writing, Float32 is the only supported band type." +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:23 +msgid "Driver capabilities (NWT_GRD)" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:34 +msgid "Driver capabilities (NWT_GRC)" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:41 +msgid "Color Information" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:43 +msgid "" +"The grid formats have color information embedded in the grid file header." +" This describes how to scale data values to RGB values. When opening in " +"read mode, the driver will report 4 bands - R, G, B and the data band. In" +" reality there is 1 band and the RGB bands are 'virtual', made from " +"scaling data. For this reason, when opening in write mode only 1 band is " +"reported and the RGB bands are unavailable." +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:53 +msgid "GDAL Metadata items are stored in the PAM .aux.xml file" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:55 +msgid "Northwood Grid itself does not natively support arbitrary metadata" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:58 +msgid "Nodata values" +msgstr "" + +#: ../../source/drivers/raster/nwtgrd.rst:60 +msgid "" +"In write mode, it is possible to designate any value as the nodata value." +" These values are translated to the Vertical Mapper no data value when " +"writing. Therefore, in read mode the nodata value is always reported as " +"-1e37." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:5 +msgid "OGCAPI -- OGC API Tiles / Maps / Coverage" +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:9 +msgid "OGCAPI" +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:13 +msgid "" +"Access to server implementing OGC API - Tiles, OGC API - Maps or OGC API " +"- Coverages. This driver has raster and vector capabilities." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:18 +msgid "" +"This driver is experimental, and has been developed to demonstrate work " +"related to the \"Modular OGC API Workflows\" initiative. It implements " +"non-finalized versions of OGC API - Tiles, - Maps and - Coverages. Its " +"interface may change at any time, or it might be removed. It might also " +"be eventually merged with the OGC API - Features driver." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:30 +msgid "Dataset opening" +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:32 +msgid "The driver supports opening by:" +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:34 +msgid "" +"passing a filename (with .moaw extension) containing a JSON document, " +"like the following, specifying a deferred processing" +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:51 +msgid "" +"passing a string \"OGCAPI:{url}\" where {url} is the URL to a OGC API " +"landing page In that case the driver will return subdatasets with the " +"different collections." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:54 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if OGCAPI`` option to command " +"line utilities accepting it, or ``OGCAPI`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed URL, without the ``OGCAPI:`` prefix." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:59 +msgid "" +"passing a string \"OGCAPI:{url}\" where {url} is the URL to a OGC API " +"collection description" +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:62 +msgid "" +"When the driver opens a collection, for raster, it will look if tiles or " +"maps API are advertized for it. It will use tiles API by default, and " +"fallback to maps API when not available. It will also look at the image " +"formats, and will prefer PNG When available." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:67 +msgid "" +"For vector collections, this driver handles the tiles API, with GeoJSON " +"or Mapbox Vector tiles." +msgstr "" + +#: ../../source/drivers/raster/ogcapi.rst:70 +msgid "" +"When using the tiles API, the driver will use by default the " +"WorldCRS84Quad tile matrix set when available" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:8 +#: ../../source/drivers/vector/openfilegdb.rst:6 +msgid "OpenFileGDB" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:12 +msgid "" +"The OpenFileGDB driver provides read access to raster layers of File " +"Geodatabases (.gdb directories). The dataset name must be the " +"directory/folder name, and it must end with the .gdb extension." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:16 +#: ../../source/drivers/vector/openfilegdb.rst:16 +msgid "" +"It can also read directly zipped .gdb directories (with .gdb.zip " +"extension), provided they contain a .gdb directory at their first level." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:19 +msgid "The driver supports:" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:21 +msgid "reading CRS information" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:22 +msgid "reading geotransform" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:23 +msgid "exposing overviews" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:24 +msgid "exposing nodata mask band or nodata value" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:25 +msgid "uncompressed, LZ77, JPEG and JPEG2000 compression methods." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:26 +msgid "exposing value attribute tables as GDAL Raster attribute tables." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:28 +msgid "" +"Support for FileGDB created by ArcGIS v10 has been added in GDAL 3.7 " +"Support for FileGDB created by ArcGIS v9 has been added in GDAL 3.8" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:39 +#: ../../source/drivers/vector/jsonfg.rst:42 +#: ../../source/drivers/vector/miramon.rst:230 +msgid "Connection string" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:41 +msgid "" +"When a File Geodatabase contains several raster layers, the raster layer " +"that must be opened is specified with the following connection string" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:48 +msgid "" +"When opening a dataset with pointing only to the .gdb directory, and if " +"it contains several raster layers, a list of subdatasets is returned by " +"the driver" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:62 +msgid "" +"In AUTO mode, the driver will expose a dataset nodata mask band, unless " +"the band data type is Float32 or Float64, in which case a nodata value is" +" used." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:65 +msgid "" +"In MASK mode, the driver will expose a dataset nodata mask band for all " +"data types." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:68 +msgid "" +"In NONE mode, the driver will not expose a nodata mask band or a nodata " +"value." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:71 +msgid "" +"When specifying a numeric nodata value (``nan`` accepted for Float32 or " +"Float64), it is used as the band nodata value. The nodata value should be" +" selected outside the range of valid values (but within the range of the " +"data type)." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:79 +msgid "" +"The ``xml:documentation`` and ``xml:definition`` metadata domains contain" +" the XML content from the ``GDB_Items`` table related to the raster " +"layer." +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:85 +msgid "List raster layers from a FileGDB" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:91 +msgid "Open a given subdataset:" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:101 +msgid ":ref:`OpenFileGDB vector <vector.openfilegdb>` documentation page" +msgstr "" + +#: ../../source/drivers/raster/openfilegdb.rst:107 +msgid "" +"Thanks to Richard Barnes and his ArcRescue tool for the deciphering of " +"the band_types field which indicates the compression method and the data " +"type." +msgstr "" + +#: ../../source/drivers/raster/ozi.rst:5 +msgid "OZI -- OZF2/OZFX3 raster" +msgstr "" + +#: ../../source/drivers/raster/ozi.rst:7 +msgid "OZI" +msgstr "" + +#: ../../source/drivers/raster/ozi.rst:11 +msgid "GDAL supports reading OZF2/OZFX3 raster datasets." +msgstr "" + +#: ../../source/drivers/raster/ozi.rst:13 +msgid "" +"Either the image file or the .map file can be passed to GDAL. To retrieve" +" georeferencing, you need to specify the .map file." +msgstr "" + +#: ../../source/drivers/raster/ozi.rst:26 +msgid "" +"`Specification of OZF2/OZFX3 format " +"<http://trac.osgeo.org/gdal/browser/sandbox/klokan/ozf/ozf-binary-format-" +"description.txt>`__" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:7 +msgid "JAXAPALSAR" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:11 +msgid "" +"This driver provides enhanced support for processed PALSAR products from " +"the JAXA PALSAR processor. This encompasses products acquired from the " +"following organizations:" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:15 +msgid "JAXA (Japanese Aerospace eXploration Agency)" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:16 +msgid "AADN (Alaska Satellite Facility)" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:17 +msgid "ESA (European Space Agency)" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:19 +msgid "" +"This driver does not support products created using the Vexcel processor " +"(i.e. products distributed by ERSDAC and affiliated organizations)." +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:22 +msgid "Support is provided for the following features of PALSAR products:" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:24 +msgid "Reading Level 1.1 and 1.5 processed products" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:25 +msgid "Georeferencing for Level 1.5 products" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:26 +msgid "Basic metadata (sensor information, ground pixel spacing, etc.)" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:27 +msgid "Multi-channel data (i.e. dual-polarization or fully polarimetric datasets)" +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:30 +msgid "This is a read-only driver." +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:32 +msgid "" +"To open a PALSAR product, select the volume directory file (for example, " +"VOL-ALPSR000000000-P1.5_UA or VOL-ALPSR000000000-P1.1__A). The driver " +"will then use the information contained in the volume directory file to " +"find the various image files (the IMG-\\* files), as well as the Leader " +"file. Note that the Leader file is essential for correct operation of the" +" driver." +msgstr "" + +#: ../../source/drivers/raster/palsar.rst:49 +msgid "" +"`RESTEC Sample Data <http://www.alos-restec.jp/en/staticpages/index.php" +"/service-sampledata>`__" +msgstr "" + +#: ../../source/drivers/raster/paux.rst:5 +msgid "PAux -- PCI .aux Labelled Raw Format" +msgstr "" + +#: ../../source/drivers/raster/paux.rst:7 +msgid "PAux" +msgstr "" + +#: ../../source/drivers/raster/paux.rst:11 +msgid "" +"GDAL includes a partial implementation of the PCI .aux labelled raw " +"raster file for read, write and creation. To open a PCI labelled file, " +"select the raw data file itself. The .aux file (which must have a common " +"base name) will be checked for automatically." +msgstr "" + +#: ../../source/drivers/raster/paux.rst:16 +msgid "" +"The format type for creating new files is ``PAux``. All PCI data types " +"(8U, 16U, 16S, and 32R) are supported. Currently georeferencing, " +"projections, and other metadata is ignored." +msgstr "" + +#: ../../source/drivers/raster/paux.rst:32 +msgid "NOTE: Implemented as :source_file:`frmts/raw/pauxdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/paux.rst:34 +msgid "" +"See Also: `PCI's .aux Format Description <http://www.pcigeomatics.com" +"/cgi-" +"bin/pcihlp/GDB%7CSupported+File+Formats%7CRaw+Binary+Image+Format+(RAW)%7CRaw+.aux+Format>`__" +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:5 +msgid "PCIDSK -- PCI Geomatics Database File" +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:7 +msgid "PCIDSK" +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:11 +msgid "" +"PCIDSK database file used by PCI EASI/PACE software for image analysis. " +"It is supported for reading, and writing by GDAL. All pixel data types, " +"and data organizations (pixel interleaved, band interleaved, file " +"interleaved and tiled) should be supported. Currently LUT segments are " +"ignored, but PCT segments should be treated as associated with the bands." +" Overall file, and band specific metadata should be correctly associated " +"with the image or bands." +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:19 +msgid "" +"Georeferencing is supported though there may be some limitations in " +"support of datums and ellipsoids. GCP segments are ignored. RPC segments " +"will be returned as GDAL style RPC metadata." +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:23 +msgid "" +"Internal overview (pyramid) images will also be correctly read though " +"newly requested overviews will be built externally as an .ovr file." +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:26 +msgid "Vector segments are also supported by the driver." +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:34 +msgid "" +"Note that PCIDSK files are always produced pixel interleaved, even though" +" other organizations are supported for read." +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:71 +msgid "Implemented as :source_file:`frmts/pcidsk/pcidskdataset2.cpp`." +msgstr "" + +#: ../../source/drivers/raster/pcidsk.rst:72 +msgid "" +"`PCIDSK SDK " +"<https://web.archive.org/web/20130730111701/http://home.gdal.org/projects/pcidsk/index.html>`__" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:5 +msgid "PCRaster -- PCRaster raster file format" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:7 +msgid "PCRaster" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:11 +msgid "" +"GDAL includes support for reading and writing PCRaster raster files. " +"PCRaster is a dynamic modeling system for distributed simulation models. " +"The main applications of PCRaster are found in environmental modeling: " +"geography, hydrology, ecology to name a few. Examples include models for " +"research on global hydrology, vegetation competition models, slope " +"stability models and land use change models." +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:18 +msgid "" +"The driver reads all types of PCRaster maps: booleans, nominal, ordinals," +" scalar, directional and ldd. The same cell representation used to store " +"values in the file is used to store the values in memory." +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:22 +msgid "" +"The driver detects whether the source of the GDAL raster is a PCRaster " +"file. When such a raster is written to a file the value scale of the " +"original raster will be used. The driver **always** writes values using " +"UINT1, INT4 or REAL4 cell representations, depending on the value scale:" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:28 +msgid "Value scale" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:28 +msgid "Cell representation" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:30 +#: ../../source/drivers/raster/pcraster.rst:43 +msgid "VS_BOOLEAN" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:30 +#: ../../source/drivers/raster/pcraster.rst:35 +#: ../../source/drivers/raster/pcraster.rst:43 +msgid "CR_UINT1" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:31 +#: ../../source/drivers/raster/pcraster.rst:44 +msgid "VS_NOMINAL" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:31 +#: ../../source/drivers/raster/pcraster.rst:32 +#: ../../source/drivers/raster/pcraster.rst:44 +msgid "CR_INT4" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:32 +msgid "VS_ORDINAL" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:33 +#: ../../source/drivers/raster/pcraster.rst:45 +#: ../../source/drivers/raster/pcraster.rst:46 +msgid "VS_SCALAR" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:33 +#: ../../source/drivers/raster/pcraster.rst:34 +#: ../../source/drivers/raster/pcraster.rst:45 +#: ../../source/drivers/raster/pcraster.rst:46 +msgid "CR_REAL4" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:34 +msgid "VS_DIRECTION" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:35 +msgid "VS_LDD" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:38 +msgid "" +"For rasters from other sources than a PCRaster raster file a value scale " +"and cell representation is determined according to the following rules:" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:42 +msgid "Source type" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:42 +msgid "Target value scale" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:42 +msgid "Target cell representation" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:43 +msgid "GDT_Byte" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:44 +msgid "GDT_Int32" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:45 +msgid "GDT_Float32" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:46 +msgid "GDT_Float64" +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:49 +msgid "" +"The driver can convert values from one supported cell representation to " +"another. It cannot convert to unsupported cell representations. For " +"example, it is not possible to write a PCRaster raster file from values " +"which are used as CR_INT2 (GDT_Int16)." +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:54 +msgid "" +"Although the de-facto file extension of a PCRaster raster file is .map, " +"the PCRaster software does not require a standardized file extension." +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:57 +msgid "NOTE: Implemented as :source_file:`frmts/pcraster/pcrasterdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/pcraster.rst:59 +msgid "" +"See also: `PCRaster website at Utrecht University " +"<http://pcraster.geo.uu.nl>`__." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:5 ../../source/drivers/vector/pdf.rst:5 +msgid "PDF -- Geospatial PDF" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:7 ../../source/drivers/vector/pdf.rst:7 +msgid "PDF" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:11 +msgid "" +"GDAL supports reading Geospatial PDF documents, by extracting " +"georeferencing information and rasterizing the data. Non-geospatial PDF " +"documents will also be recognized by the driver." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:15 +msgid "" +"PDF documents can be created from other GDAL raster datasets, and OGR " +"datasources can also optionally be drawn on top of the raster layer (see " +"OGR\\_\\* creation options in the below section)." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:20 +msgid "" +"The driver supports reading georeferencing encoded in either of the 2 " +"current existing ways : according to the OGC encoding best practice, or " +"according to the Adobe Supplement to ISO 32000." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:24 +msgid "" +"Multipage documents are exposed as subdatasets, one subdataset par page " +"of the document." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:37 +#: ../../source/drivers/vector/pdf.rst:24 +msgid "Vector support" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:39 +msgid "See the :ref:`PDF vector <vector.pdf>` documentation page" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:44 +msgid "" +"The neatline (for OGC best practice) or the bounding box (Adobe style) " +"will be reported as a NEATLINE metadata item, so that it can be later " +"used as a cutline for the warping algorithm." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:51 +msgid "" +"Additional metadata, such as found in USGS Topo PDF can be extracted from" +" the file, and will be stored as XML raw content in the EMBEDDED_METADATA" +" metadata domain." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:123 +msgid "" +"|about-open-options| Above configuration options are also available as " +"open options." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:161 +msgid "LAYERS Metadata domain" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:163 +msgid "" +"When GDAL is compiled against Poppler or PDFium, the LAYERS metadata " +"domain can be queried to retrieve layer names that can be turned ON or " +"OFF. This is useful to know which values to specify for the " +":config:`GDAL_PDF_LAYERS` or :config:`GDAL_PDF_LAYERS_OFF` configuration " +"options." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:169 +#: ../../source/drivers/vector/osm.rst:63 +msgid "For example :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:189 +msgid "Restrictions" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:191 +msgid "" +"The opening of a PDF document (to get the georeferencing) is fast, but at" +" the first access to a raster block, the whole page will be rasterized " +"(with Poppler), which can be a slow operation." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:195 +msgid "" +"Note: some raster-only PDF files (such as some USGS GeoPDF files), that " +"are regularly tiled are exposed as tiled dataset by the GDAL PDF driver, " +"and can be rendered with any backends." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:199 +msgid "" +"Only a few of the possible Datums available in the OGC best practice spec" +" have been currently mapped in the driver. Unrecognized datums will be " +"considered as being based on the WGS84 ellipsoid." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:203 +msgid "" +"For documents that contain several neatlines in a page (insets), the " +"georeferencing will be extracted from the inset that has the largest area" +" (in term of screen points)." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:210 +msgid "" +"PDF documents can be created from other GDAL raster datasets, that have 1" +" band (graylevel or with color table), 3 bands (RGB) or 4 bands (RGBA)." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:213 +msgid "" +"Georeferencing information will be written by default according to the " +"ISO32000 specification. It is also possible to write it according to the " +"OGC Best Practice conventions (but limited to a few datum and projection " +"types)." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:218 +msgid "Note: PDF write support does not require linking to any backend." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:523 +msgid "Update of existing files" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:525 +msgid "" +"Existing PDF files (created or not with GDAL) can be opened in update " +"mode in order to set or update the following elements :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:528 +msgid "" +"Geotransform and associated projection (with SetGeoTransform() and " +"SetProjection())" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:530 +msgid "GCPs (with SetGCPs())" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:531 +msgid "Neatline (with SetMetadataItem(\"NEATLINE\", polygon_definition_in_wkt))" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:533 +msgid "" +"Content of Info object (with SetMetadataItem(key, value) where key is one" +" of AUTHOR, CREATOR, CREATION_DATE, KEYWORDS, PRODUCER, SUBJECT and " +"TITLE)" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:536 +msgid "xml:XMP metadata (with SetMetadata(md, \"xml:XMP\"))" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:538 +msgid "" +"For geotransform or GCPs, the Geo encoding method used by default is " +"ISO32000. OGC_BP can be selected by setting the GDAL_PDF_GEO_ENCODING " +"configuration option to OGC_BP." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:542 +msgid "" +"Updated elements are written at the end of the file, following the " +"incremental update method described in the PDF specification." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:546 +msgid "Creation of PDF file from a XML composition file (GDAL >= 3.0)" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:548 +msgid "" +"A PDF file can be generate from a XML file that describes the composition" +" of the PDF:" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:551 +msgid "number of pages" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:552 +msgid "layer tree, with visibility state, exclusion groups" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:553 +msgid "definition or 0, 1 or several georeferenced areas per page" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:554 +msgid "page content made of rasters, vectors or labels" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:556 +msgid "" +"The GDALCreate() API must be used with width = height = bands = 0 and " +"datatype = GDT_Unknown and :co:`COMPOSITION_FILE` must be the single " +"creation option." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:560 +msgid "" +"The XML schema against which the composition file must validate is " +"`pdfcomposition.xsd " +"<https://raw.githubusercontent.com/OSGeo/gdal/master/data/pdfcomposition.xsd>`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:563 +msgid "Example on how to use the API:" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:573 +msgid "" +"A sample Python script `gdal_create_pdf.py " +"<https://raw.githubusercontent.com/OSGeo/gdal/master/swig/python/gdal-" +"utils/osgeo_utils/samples/gdal_create_pdf.py>`__ is also available. " +"Starting with GDAL 3.2, the :ref:`gdal_create` utility can also be used." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:578 +msgid "Example of a composition XML file:" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:674 +msgid "" +"For read support, GDAL must be built against one of the following " +"libraries :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:677 +msgid "`Poppler <http://poppler.freedesktop.org/>`__ (GPL-licensed)" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:678 +msgid "`PoDoFo <http://podofo.sourceforge.net/>`__ (LGPL-licensed)" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:679 +msgid "" +"`PDFium <https://code.google.com/p/pdfium/>`__ (New BSD-licensed, " +"supported since GDAL 2.1.0)" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:682 +msgid "" +"Note: it is also possible to build against a combination of several of " +"the above libraries. PDFium will be used in priority over Poppler, itself" +" used in priority over PoDoFo." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:687 +msgid "Unix build" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:689 +msgid "" +"The relevant configure options are --with-poppler, --with-podofo, --with-" +"podofo-lib and --with-podofo-extra-lib-for-test." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:692 +msgid "" +"Starting with GDAL 2.1.0, --with-pdfium, --with-pdfium-lib, --with-" +"pdfium-extra-lib-for-test and --enable-pdf-plugin are also available." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:697 +msgid "Poppler" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:699 +msgid "" +"libpoppler itself must have been configured with " +"-DENABLE_UNSTABLE_API_ABI_HEADERS=ON so that the xpdf C++ headers are " +"available. Note: the poppler C++ API isn't stable, so the driver " +"compilation may fail with too old or too recent poppler versions." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:706 +msgid "PoDoFo" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:708 +msgid "" +"As a partial alternative, the PDF driver can be compiled against " +"libpodofo to avoid the libpoppler dependency. This is sufficient to get " +"the georeferencing and vector information. However, for getting the " +"imagery, the pdftoppm utility that comes with the poppler distribution " +"must be available in the system PATH. A temporary file will be generated " +"in a directory determined by the following configuration options : " +":config:`CPL_TMPDIR`, ``TMPDIR`` or ``TEMP`` (in that order). If none are" +" defined, the current directory will be used. Successfully tested " +"versions are libpodofo 0.8.4, 0.9.1 and 0.9.3. Important note: using " +"PoDoFo 0.9.0 is strongly discouraged, as it could cause crashes in GDAL " +"due to a bug in PoDoFo." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:721 +msgid "PDFium" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:723 +msgid "" +"Using PDFium as a backend allows access to raster, vector, georeferencing" +" and other metadata. The PDFium backend has also support for arbitrary " +"overviews, for fast zoom-out." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:727 +msgid "" +"Only GDAL builds against static builds of PDFium have been tested. " +"Building PDFium can be challenging, and particular builds must be used to" +" work properly with GDAL." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:732 +msgid "With GDAL >= 3.9" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:734 +msgid "" +"The scripts in the `<https://github.com/rouault/pdfium_build_gdal_3_9>`__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:738 +msgid "With GDAL = 3.8" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:740 +msgid "" +"The scripts in the `<https://github.com/rouault/pdfium_build_gdal_3_8>`__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:744 +msgid "With GDAL 3.7" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:746 +msgid "" +"The scripts in the `<https://github.com/rouault/pdfium_build_gdal_3_7>`__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:750 +msgid "With GDAL 3.5 and 3.6" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:752 +msgid "" +"The scripts in the `<https://github.com/rouault/pdfium_build_gdal_3_5>`__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:756 +msgid "With GDAL 3.4" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:758 +msgid "" +"The scripts in the `<https://github.com/rouault/pdfium_build_gdal_3_4>`__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:762 +msgid "With GDAL 3.2 and 3.3" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:764 +msgid "" +"The scripts in the `<https://github.com/rouault/pdfium_build_gdal_3_2>`__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:768 +msgid "With GDAL 3.1.x" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:770 +msgid "" +"The scripts in the `<https://github.com/rouault/pdfium_build_gdal_3_1>`__" +" repository must be used to build a patched version of PDFium." +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:776 +msgid "" +"Create a PDF from 2 rasters (main_raster and another_raster), such that " +"main_raster is initially displayed, and they are exclusively displayed :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:786 +msgid "Create of PDF with some JavaScript :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:792 +msgid "where script.js is :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:802 +msgid ":ref:`PDF vector <vector.pdf>` documentation page" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:804 +msgid "Specifications :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:806 +msgid "" +"`OGC GeoPDF Encoding Best Practice Version 2.2 (08-139r3) " +"<http://portal.opengeospatial.org/files/?artifact_id=40537>`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:808 +msgid "" +"`Adobe Supplement to ISO 32000 " +"<http://www.adobe.com/devnet/acrobat/pdfs/adobe_supplement_iso32000.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:810 +msgid "" +"`PDF Reference, version 1.7 " +"<http://www.adobe.com/devnet/acrobat/pdfs/pdf_reference_1-7.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:812 +msgid "" +"`Acrobat(R) JavaScript Scripting Reference " +"<http://partners.adobe.com/public/developer/en/acrobat/sdk/AcroJS.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:815 +msgid "Libraries :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:817 +msgid "`Poppler homepage <http://poppler.freedesktop.org/>`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:818 +msgid "`PoDoFo homepage <http://podofo.sourceforge.net/>`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:819 +msgid "`PDFium homepage <https://code.google.com/p/pdfium/>`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:820 +msgid "" +"`PDFium forked version for simpler builds " +"<https://github.com/rouault/pdfium>`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:823 +msgid "Samples :" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:825 +msgid "" +"`A few Geospatial PDF samples <https://www.terragotech.com/learn-more" +"/sample-geopdfs>`__" +msgstr "" + +#: ../../source/drivers/raster/pdf.rst:827 +msgid "" +"`Tutorial to generate Geospatial PDF maps from OSM data " +"<http://latuviitta.org/documents/Geospatial_PDF_maps_from_OSM_with_GDAL.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:5 +msgid "PDS -- Planetary Data System v3" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:7 ../../source/drivers/vector/pds.rst:6 +msgid "PDS" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:11 +msgid "" +"PDS is a format used primarily by NASA to store and distribute solar, " +"lunar and planetary imagery data. GDAL provides read-only access to PDS " +"formatted imagery data." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:15 +msgid "" +"PDS files often have the extension .img, sometimes with an associated " +".lbl (label) file. When a .lbl file exists it should be used as the " +"dataset name rather than the .img file." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:19 +msgid "" +"In addition to support for most PDS imagery configurations, this driver " +"also reads georeferencing and coordinate system information as well as " +"selected other header metadata." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:27 +msgid "" +"PDS3 datasets can incorporate a VICAR header. By default, GDAL will use " +"the PDS driver in that situation. Starting with GDAL 3.1, if the " +":config:`GDAL_TRY_PDS3_WITH_VICAR` configuration option is set to YES, " +"the dataset will be opened by the :ref:`VICAR <raster.vicar>` driver." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:56 +msgid "" +"Due to ambiguities in the PDS specification, the georeferencing of some " +"products is subtly or grossly incorrect. There are configuration " +"variables which may be set for these products to correct the " +"interpretation of the georeferencing. Some details are available in " +"`ticket #5941 <http://trac.osgeo.org/gdal/ticket/5941>`__ and `ticket " +"#3940 <http://trac.osgeo.org/gdal/ticket/3940>`__." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:63 +msgid "" +"As a test, download both the label and image for the lunar `LOLA DEM " +"<http://pds-geosciences.wustl.edu/missions/lro/lola.htm>`__ (digital " +"elevation file) `LOLA PDS label <http://pds-" +"geosciences.wustl.edu/lro/lro-l-lola-3-rdr-v1/lrolol_1xxx/data/lola_gdr/cylindrical/img/ldem_4.lbl>`__" +" and `LOLA PDS v3 image <http://pds-" +"geosciences.wustl.edu/lro/lro-l-lola-3-rdr-v1/lrolol_1xxx/data/lola_gdr/cylindrical/img/ldem_4.img>`__." +" Using gdalinfo, the reported centered should be perfectly at 0.0, 0.0 " +"meters in Cartesian space without any configuration options." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:73 +msgid "$ gdalinfo ldem_4.lbl" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:75 +msgid "Example conversion to GeoTiff:" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:77 +msgid "$ gdal_translate ldem_4.lbl out_LOLA.tif" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:79 +#: ../../source/drivers/raster/pds.rst:106 +msgid "" +"Example conversion and applying offset and multiplier values as defined " +"in some PDS labels:" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:82 +msgid "$ gdal_translate -ot Float32 -unscale ldem_4.lbl out_LOLA_32bit.tif" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:86 +msgid "" +"To show an example to correct an offset issue we can use the `MOLA DEM " +"<http://pds-geosciences.wustl.edu/missions/mgs/megdr.html>`__ from the " +"PDS. Download both the `MOLA PDS label <http://pds-" +"geosciences.wustl.edu/mgs/mgs-m-mola-5-megdr-l3-v1/mgsl_300x/meg004/megt90n000cb.lbl>`__" +" and `MOLA PDS v3 image <http://pds-" +"geosciences.wustl.edu/mgs/mgs-m-mola-5-megdr-l3-v1/mgsl_300x/meg004/megt90n000cb.img>`__." +" The MOLA labels currently contain a one pixel offset. To read this file " +"correctly, use GDAL with these options." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:95 +msgid "" +"$ gdalinfo --config PDS_SampleProjOffset_Shift -0.5 --config " +"PDS_LineProjOffset_Shift -0.5 megt90n000cb.lbl" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:98 +msgid "" +"Again with these optional parameters, the center should be perfectly 0.0," +" 0.0 meters in Cartesian space." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:101 +msgid "Example conversion for MOLA:" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:103 +msgid "" +"$ gdal_translate --config PDS_SampleProjOffset_Shift -0.5 --config " +"PDS_LineProjOffset_Shift -0.5 megt90n000cb.lbl out_MOLA_4ppd.tif" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:109 +msgid "" +"$ gdal_translate -ot Float32 -unscale --config PDS_SampleProjOffset_Shift" +" -0.5 --config PDS_LineProjOffset_Shift -0.5 megt90n000cb.lbl " +"out_MOLA_4ppd_32bit.tif" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:115 +msgid "PDS is part of a family of related formats including ISIS2 and ISIS3." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:121 +msgid "Implemented as :source_file:`frmts/pds/pdsdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:122 +msgid "`NASA Planetary Data System <http://pds.nasa.gov/>`__" +msgstr "" + +#: ../../source/drivers/raster/pds.rst:123 +msgid ":ref:`raster.isis2` driver." +msgstr "" + +#: ../../source/drivers/raster/pds.rst:124 +#: ../../source/drivers/raster/pds4.rst:555 +msgid ":ref:`raster.isis3` driver." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:5 +msgid "PDS4 -- NASA Planetary Data System (Version 4)" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:7 +msgid "PDS4" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:11 +msgid "" +"PDS4 is a format used primarily by NASA to store and distribute solar, " +"lunar and planetary imagery data. GDAL provides read-write access to PDS4" +" formatted imagery data." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:15 +msgid "" +"PDS4 files are compose of a .xml (label) file which references a raw " +"imagery file. The driver also supports imagery stored in a separate " +"uncompressed GeoTIFF file with a strip organization compatible of a raw " +"imagery file." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:20 +msgid "" +"The driver also reads and write georeferencing and coordinate system " +"information as well as selected other header metadata." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:23 +msgid "" +"A mask band is attached to each source band. The value of this mask band " +"is 0 when the pixel value is one of the missing constants." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:29 +msgid "PDS4 is part of a family of related formats including PDS and ISIS3." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:31 +msgid "" +"Starting with GDAL 2.5, the PDS4 driver supports reading and writing " +"ASCII fixed-with, binary fixed-with and delimited(CSV) tables as OGR " +"vector layers." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:49 +msgid "" +"The PDS4 label can be retrieved as XML-serialized content in the xml:PDS4" +" metadata domain." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:52 +msgid "" +"On creation, a source template label can be passed to the SetMetadata() " +"interface in the \"xml:PDS4\" metadata domain." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:56 +msgid "Open options (vector only)" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:60 +msgid "" +"|about-open-options| When opening a PDS4 vector dataset, the following " +"open options are available:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:93 +msgid "" +"The PDS4 driver supports updating imagery of existing datasets, creating " +"new datasets through the CreateCopy() and Create() interfaces." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:96 +msgid "" +"When using CreateCopy(), gdal_translate or gdalwarp, an effort is made to" +" preserve as much as possible of the original label when doing PDS4 to " +"PDS4 conversions. This can be disabled with the :co:`USE_SRC_LABEL=NO` " +"creation option." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:101 +msgid "" +"|about-creation-options| The following dataset creation options are " +"available:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:186 +msgid "" +"**VAR_\\***\\ =string. If options like VAR_XXXX=yyyy are specified, any " +"{XXXX} string in the template label will be replaced by the yyyy value." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:193 +msgid "" +"Template label to use. If not specified and not creating from an existing" +" PDS4 file, the data/pds4_template.xml file will be used. For GDAL " +"utilities to find this default PDS4 template, GDAL's data directory " +"should be defined in your environment (typically on Windows builds). " +"Consult the `wiki " +"<https://trac.osgeo.org/gdal/wiki/FAQInstallationAndBuilding#HowtosetGDAL_DATAvariable>`__" +" for more information." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:231 +msgid "Layer creation options (vector/table datasets)" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:233 +msgid "" +"|about-layer-creation-options| (Starting with GDAL 3.0) When creating a " +"PDS4 vector dataset, or appending a new table to an existing table, the " +"following layer creation options are available:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:316 +msgid "Subdataset / multiple image support" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:318 +msgid "" +"If several Array objects are present in the label, they will be reported " +"as separate subdatasets (typically the main subdataset is an Array3D, and" +" backplanes are represented as Array2D)." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:322 +msgid "" +"Since GDAL 3.0, creation of new datasets with subdatasets is supported " +"(through the :co:`APPEND_SUBDATASET=YES` creation option). One important " +"restriction is that, given that the georeferencing information in the " +"PDS4 XML label is global for the whole dataset, all subdatasets must " +"share the same georeferencing information: coordinate reference system, " +"georegistration and resolution. Appending to both RAW and GEOTIFF raster " +"is supported. In append mode, most creation options are ignored, except " +":co:`INTERLEAVE` (if GeoTIFF output image), :co:`ARRAY_TYPE` and " +":co:`ARRAY_IDENTIFIER`." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:333 +msgid "PDS4 raster examples" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:335 +msgid "Listing bands and subdatasets:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:383 +msgid "" +"The information displayed by default is the one of the first subdataset " +"(SUBDATASET_1_NAME)" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:386 +msgid "Getting information on a subdataset:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:406 +msgid "Conversion to GeoTIFF of a given subdatasets:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:412 +msgid "Conversion to GeoTIFF of a all subdatasets:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:418 +msgid "This will create b0011_p237201_01_01v02_X.tif files where X=1,....,N" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:420 +msgid "" +"Creation of a new PDS4 dataset, using the default template and setting " +"its parameterized variables:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:434 +msgid "" +"Creation of the same PDS4 dataset as above, using the default template " +"but setting its parameterized variables from a text file. Helps with long" +" command lines:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:438 +msgid "Create a text file \"myOptions.txt\" with the below content" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:457 +msgid "" +"For more on --optfile, consult `the general documentation on GDAL " +"utilities <gdal_utilities.html>`__." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:460 +msgid "" +"Creation of a PDS4 dataset, using a non default template (here on a HTTP " +"server, but local filename also possible):" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:468 +msgid "" +"Creation of a PDS4 dataset from a source PDS4 dataset (using the XML file" +" of this source PDS4 dataset as an implicit template), with subsetting:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:476 +msgid "" +"In Python, creation of a PDS4 dataset from a GeoTIFF, using a base " +"template into which one substitute one element with a new value:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:502 +msgid "Appending a new image (subdataset) to an existing PDS4 dataset." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:511 +msgid "Adding a PDS4 label to an existing ISIS3 dataset. (GDAL >= 3.1)" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:518 +msgid "PDS4 vector examples" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:520 +msgid "Displaying the content of a PDS4 dataset with a table:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:526 +msgid "" +"Converting a PDS4 dataset with a table to shapefile, by specifying " +"columns that contain longitude and latitude:" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:533 +msgid "" +"Converting a shapefile to a PDS4 dataset with a CSV-delimited table (with" +" an implicit WKT column to store the geometry):" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:541 +#: ../../source/drivers/vector/filegdb.rst:285 +#: ../../source/drivers/vector/gpkg.rst:55 +#: ../../source/drivers/vector/openfilegdb.rst:332 +#: ../../source/drivers/vector/xodr.rst:54 +msgid "Limitations" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:543 +msgid "" +"As a new driver and new format, please report any issues to the bug " +"tracker, as explained on the `wiki <https://trac.osgeo.org/gdal/wiki>`__" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:549 +msgid "Implemented as :source_file:`frmts/pds/pds4dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:550 +msgid "`Official documentation <https://pds.nasa.gov/pds4/doc/index.shtml>`__" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:552 +msgid "" +"`Schemas, including the cartography extension " +"<https://pds.nasa.gov/pds4/schema/released/>`__" +msgstr "" + +#: ../../source/drivers/raster/pds4.rst:554 +msgid ":ref:`raster.pds` driver." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:7 +msgid "PLMosaic" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:11 +msgid "" +"This driver can connect to Planet Labs Mosaics API. GDAL/OGR must be " +"built with Curl support in order for the PLMosaic driver to be compiled." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:14 +msgid "" +"The driver supports listing mosaics and reading them. Mosaics are " +"accessed at their highest resolution. Mosaics are typically composed of " +"quads of 4096x4096 pixels." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:18 +msgid "" +"For mosaics of type Byte, overviews are available by using the tile API. " +"For other data types, there is no support for overviews, so requests that" +" involve downsampling may take a long time to complete." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:36 +#: ../../source/drivers/vector/amigocloud.rst:36 +#: ../../source/drivers/vector/plscenes_data_v1.rst:27 +msgid "" +"Additional optional parameters can be specified after the ':' sign. " +"Currently the following one is supported :" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:39 +msgid "" +"**api_key**\\ =value: To specify the Planet API key. It is mandatory, " +"unless it is supplied through the open option API_KEY, or the " +"configuration option PL_API_KEY." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:42 +msgid "**mosaic**\\ =mosaic_name: To specify the mosaic name." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:43 +msgid "" +"**cache_path**\\ =path: To specify the path to a directory where cached " +"quads (and tiles) are stored. A plmosaic_cache/{mosaic_name} subdirectory" +" will be created under that path. The empty string can be used to disable" +" any disk caching." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:47 +msgid "" +"**trust_cache**\\ =YES/NO: Whether already cached quads should be reused " +"directly, without prior checking if the server has a more recent version." +" Note: this only applies to quads, and not tiles. Default is NO." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:51 +msgid "" +"**use_tiles**\\ =YES/NO: Whether to use the tile API to access full " +"resolution data, instead of downloading quads. Only apply for Byte " +"mosaics. Default is NO." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:55 +#: ../../source/drivers/vector/plscenes_data_v1.rst:51 +msgid "If several parameters are specified, they must be separated by a comma." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:57 +msgid "" +"If no mosaic parameter is supplied, the list of available mosaics will be" +" returned as subdatasets. If only one mosaic is available, it will be " +"directly opened." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:64 +msgid "" +"|about-open-options| The following open options are available : API_KEY, " +"MOSAIC, CACHE_PATH, TRUST_CACHE and USE_TILES. They have the same " +"semantics as the above-described parameters of same name." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:-1 +msgid "PL_API_KEY=value: To specify the Planet API key." +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:79 +msgid "Location information" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:81 +msgid "" +"The special *Pixel_{x}_{y}* metadata item of the *LocationInfo* metadata " +"domain, where x is the column and y is the line in the mosaic, can be " +"queried to get information about the scenes that compose the underneath " +"quad. This is the syntax used by the gdallocationinfo utility (see " +":ref:`rfc-32`)" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:86 +msgid "Below an example of the return :" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:110 +msgid "Listing all mosaics available (with the rights of the account) :" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:128 +msgid "returns (in case of multiple mosaics):" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:149 +msgid "Open a particular mosaic :" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:155 +msgid "returns:" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:217 +msgid "" +"`Documentation of Planet Mosaics API <https://docs.planet.com/reference" +"#basemaps-and-mosaics>`__" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:219 +msgid "" +"`API Authentication <https://docs.planet.com/docs/api-mechanics#section-" +"authentication>`__" +msgstr "" + +#: ../../source/drivers/raster/plmosaic.rst:221 +msgid ":ref:`Vector PLScenes / Planet Scenes API driver <vector.plscenes>`" +msgstr "" + +#: ../../source/drivers/raster/png.rst:5 +msgid "PNG -- Portable Network Graphics" +msgstr "" + +#: ../../source/drivers/raster/png.rst:7 +msgid "PNG" +msgstr "" + +#: ../../source/drivers/raster/png.rst:-1 +#: ../../source/drivers/raster/sentinel2.rst:-1 +msgid "Driver built-in by default" +msgstr "" + +#: ../../source/drivers/raster/png.rst:9 +msgid "internal libpng provided" +msgstr "" + +#: ../../source/drivers/raster/png.rst:11 +msgid "" +"GDAL includes support for reading, and creating .png files. Greyscale, " +"pseudo-colored, Paletted, RGB and RGBA PNG files are supported as well as" +" precisions of eight and sixteen bits per sample." +msgstr "" + +#: ../../source/drivers/raster/png.rst:15 +msgid "" +"The GDAL PNG Driver is built using the libpng library. Also note that the" +" GeoTIFF driver supports tiled TIFF with DEFLATE compressed tiles, which " +"is the same compression algorithm that PNG at its core uses." +msgstr "" + +#: ../../source/drivers/raster/png.rst:19 +msgid "" +"PNG files are linearly compressed, so random reading of large PNG files " +"can be very inefficient (resulting in many restarts of decompression from" +" the start of the file). The maximum dimension of a PNG file that can be " +"created by GDAL is set to 1,000,000x1,000,000 pixels by libpng." +msgstr "" + +#: ../../source/drivers/raster/png.rst:24 +msgid "" +"Text chunks are translated into metadata, typically with multiple lines " +"per item. :ref:`raster.wld` with the extensions of .pgw, .pngw or .wld " +"will be read. Single transparency values in greyscale files will be " +"recognised as a nodata value in GDAL. Transparent index in paletted " +"images are preserved when the color table is read." +msgstr "" + +#: ../../source/drivers/raster/png.rst:30 +msgid "" +"PNG files can be created with a type of PNG, using the CreateCopy() " +"method, requiring a prototype to read from. Writing includes support for " +"the various image types, and will preserve transparency/nodata values. " +"Georeferencing .wld files are written if creation option :co:`WORLDFILE` " +"is set. All pixel types other than 16bit unsigned will be written as " +"eight bit." +msgstr "" + +#: ../../source/drivers/raster/png.rst:56 +msgid "" +"SOURCE_ICC_PROFILE_NAME : ICC profile name. sRGB is recognized as a " +"special value." +msgstr "" + +#: ../../source/drivers/raster/png.rst:62 +msgid "PNG_GAMMA" +msgstr "" + +#: ../../source/drivers/raster/png.rst:68 +msgid "" +"All these metadata tags can be used as creation options. |about-creation-" +"options| The following creation options are available:" +msgstr "" + +#: ../../source/drivers/raster/png.rst:116 +msgid "NOTE: Implemented as :source_file:`frmts/png/pngdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/png.rst:118 +msgid "" +"PNG support is implemented based on the libpng reference library. More " +"information is available at http://www.libpng.org/pub/png." +msgstr "" + +#: ../../source/drivers/raster/pnm.rst:5 +msgid "PNM -- Netpbm (.pgm, .ppm)" +msgstr "" + +#: ../../source/drivers/raster/pnm.rst:7 +msgid "PNM" +msgstr "" + +#: ../../source/drivers/raster/pnm.rst:11 +msgid "" +"GDAL includes support for reading, and creating .pgm (greyscale), and " +".ppm (RGB color) files compatible with the Netpbm tools. Only the binary " +"(raw) formats are supported." +msgstr "" + +#: ../../source/drivers/raster/pnm.rst:15 +msgid "Netpbm files can be created with a type of PNM." +msgstr "" + +#: ../../source/drivers/raster/pnm.rst:20 +msgid "|about-creation-options| The following creation option is available:" +msgstr "" + +#: ../../source/drivers/raster/pnm.rst:30 +msgid "NOTE: Implemented as :source_file:`frmts/raw/pnmdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:5 +msgid "PostGISRaster -- PostGIS Raster driver" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:7 +msgid "PostGISRaster" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:11 +msgid "" +"PostGIS Raster (previously known as WKT Raster) is the project that " +"provides raster support on PostGIS. Since September 26st, 2010, is an " +"official part of PostGIS 2.0+." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:15 +msgid "" +"This driver was started during the Google Summer of Code 2009, and " +"significantly improved since then." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:18 +msgid "" +"Currently, the driver provides read-only support to PostGIS Raster data " +"sources." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:29 +#: ../../source/drivers/vector/hana.rst:21 +#: ../../source/drivers/vector/mssqlspatial.rst:22 +#: ../../source/drivers/vector/pg.rst:32 +msgid "Connecting to a database" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:31 +msgid "" +"To connect to a PostGIS Raster datasource, use a connection string " +"specifying the database name, with additional parameters as necessary" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:38 +msgid "" +"Note that the string, up to the part starting with \"table='\" is a " +"libpq-style connection string. That means that you can leave out " +"unnecessary fields (like password, in some cases)." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:42 +msgid "" +"**schema** - name of PostgreSQL schema where requested raster table is " +"stored." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:44 +msgid "" +"**table** - name of PostGIS Raster table. The table was created by the " +"raster loader (eg. raster2pgsql utility)." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:46 +msgid "**column** - name of raster column in raster table" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:47 +msgid "" +"**where** - option is used to filter the results of the raster table. Any" +" SQL-WHERE expression is valid." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:49 +msgid "" +"**mode** - option is used to know the expected arrangement of the raster " +"table. There are 2 possible values" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:52 +msgid "" +"**mode=1** - ONE_RASTER_PER_ROW mode. In this case, a raster table is " +"considered as a bunch of different raster files. This mode is intended " +"for raster tables storing different raster files. It's the default mode " +"if you don't provide this field in connection string." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:57 +msgid "" +"**mode=2** - ONE_RASTER_PER_TABLE mode. In this case, a raster table is " +"considered as a unique raster file, even if the table has more than one " +"row. This mode is intended for reading tiled rasters from database." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:62 +msgid "" +"**outdb_resolution** - (GDAL >= 2.3.1) option to specify how out-database" +" rasters should be resolved. Default is server_side." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:65 +msgid "" +"**server_side**: The outDB raster will be fetched by the PostgreSQL " +"server. This implies that outdb rasters are enabled on the server." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:68 +msgid "" +"**client_side**: The outDB raster filenames will be returned to the GDAL " +"PostGISRaster client, which will open it on the client side. This implies" +" that the filename stored on te server can be accessed by the client." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:72 +msgid "" +"**client_side_if_possible**: The outDB raster filenames will be returned " +"to the GDAL PostGISRaster client, which will check if it can access them." +" If it can, that's equivalent to client_side. Otherwise that's equivalent" +" to server_side. Note that this mode involves extra queries to the " +"server." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:79 +msgid "Additional notes" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:81 +msgid "" +"If a table stores a tiled raster and you execute the driver with mode=1, " +"each image tile will be considered as a different image, and will be " +"reported as a subdataset. There are use cases the driver can't still work" +" with. For example: non-regular blocked rasters. That cases are detected " +"and an error is raised. Anyway, as I've said, the driver is under " +"development, and will work with more raster arrangements ASAP." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:88 +msgid "" +"There's an additional working mode. If you don't provide a table name, " +"the driver will look for existing raster tables in all allowed database' " +"schemas, and will report each table as a subdataset." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:92 +msgid "" +"You must use this connection string's format in all the gdal tools, like " +"gdalinfo, gdal_translate, gdalwarp, etc." +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:96 +#: ../../source/drivers/raster/rasterlite.rst:165 +#: ../../source/drivers/vector/gpkg.rst:757 +#: ../../source/drivers/vector/sqlite.rst:507 +msgid "Performance hints" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:98 +msgid "" +"To get the maximum performance from the driver, it is best to load the " +"raster in PostGIS raster with the following characteristics:" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:101 +msgid "tiled: -t switch of raster2pgsql" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:102 +msgid "with overview: -l 2,4,8,... switch of raster2pgsql" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:103 +msgid "with a GIST spatial index on the raster column: -I switch of raster2pgsql" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:105 +msgid "with constraints registered: -C switch of raster2pgsql" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:110 +msgid "To get a summary about your raster via GDAL use gdalinfo:" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:116 +msgid "" +"For more examples, check the PostGIS Raster FAQ section: `Can I export my" +" PostGIS Raster data to other raster formats? " +"<https://postgis.net/docs/RT_FAQ.html#idm28288>`__" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:123 +msgid "The driver developers" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:125 +msgid "Jorge Arévalo (jorgearevalo at libregis.org)" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:126 +msgid "David Zwarg (dzwarg at azavea.com)" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:127 +msgid "Even Rouault (even.rouault at spatialys.com)" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:132 +msgid "" +"`GDAL PostGISRaster driver Wiki " +"<https://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html>`__" +msgstr "" + +#: ../../source/drivers/raster/postgisraster.rst:134 +msgid "" +"`PostGIS Raster documentation " +"<https://postgis.net/docs/RT_reference.html>`__" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:7 +msgid "PRF" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:11 +msgid "" +"PRF or MegaTIFF is an internal format of PHOTOMOD software for storing " +"large images." +msgstr "" + +#: ../../source/drivers/raster/prf.rst:14 +msgid "" +"This format was developed to store images larger than 4 GB. As a basis " +"for storing data used TIFF or JPEG2000 format. Raster is split into " +"fragments (tiles) such that each fragment does not exceeded a predefined " +"size (e.g., less than 1 GB). An overview file also added to process " +"raster data on a small scales." +msgstr "" + +#: ../../source/drivers/raster/prf.rst:20 +msgid "" +"PRF files has two variations: 'prf' for imagery data and 'x-dem' for " +"elevation data. Files can be georeferenced, but projection information " +"can be stored only in external files (\\*.prj)." +msgstr "" + +#: ../../source/drivers/raster/prf.rst:24 +msgid "Image format has the following structure:" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:26 +msgid "the header XML file 'image_name.prf'/'image_name.x-dem'" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:27 +msgid "folder 'image_name' with raster subtiles" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:28 +msgid "" +"files \\*.tif/*.jp2/*.demtif inside folder 'image_name', containing " +"raster fragments and the overview image" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:31 +msgid "" +"The driver support the data type among Byte, UInt16, UInt32, Float32 or " +"Float64." +msgstr "" + +#: ../../source/drivers/raster/prf.rst:42 +msgid "`Racurs company home page <http://www.racurs.ru>`__" +msgstr "" + +#: ../../source/drivers/raster/prf.rst:43 +msgid "`PHOTOMOD Lite home page <http://www.racurs.ru/index.php?page=453>`__" +msgstr "" + +#: ../../source/drivers/raster/r.rst:5 +msgid "R -- R Object Data Store" +msgstr "" + +#: ../../source/drivers/raster/r.rst:7 +msgid "R" +msgstr "" + +#: ../../source/drivers/raster/r.rst:11 +msgid "" +"The R Object File Format is supported for write access, and limited read " +"access by GDAL. This format is the native format R uses for objects saved" +" with the *save* command and loaded with the *load* command. GDAL " +"supports writing a dataset as an array object in this format, and " +"supports reading files with simple rasters in essentially the same " +"organization. It will not read most R object files." +msgstr "" + +#: ../../source/drivers/raster/r.rst:18 +msgid "" +"Currently there is no support for reading or writing georeferencing " +"information." +msgstr "" + +#: ../../source/drivers/raster/r.rst:50 +msgid "`R Project <http://www.r-project.org/>`__" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:5 +msgid "Rasterlite - Rasters in SQLite DB" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:7 +msgid "Rasterlite" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:11 +msgid "The Rasterlite driver allows reading and creating Rasterlite databases." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:16 +msgid "" +"Those databases can be produced by the utilities of the `rasterlite " +"<http://www.gaia-gis.it/spatialite>`__ distribution, such as " +"rasterlite_load, rasterlite_pyramids, ...." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:19 +msgid "" +"The driver supports reading grayscale, paletted and RGB images stored as " +"GIF, PNG, TIFF or JPEG tiles. The driver also supports reading " +"overviews/pyramids, spatial reference system and spatial extent." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:21 +msgid "" +"GDAL/OGR must be compiled with OGR SQLite driver support. For read " +"support, linking against spatialite library is not required, but recent " +"enough sqlite3 library is needed to read rasterlite databases. rasterlite" +" library is not required either." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:26 +msgid "" +"For write support a new table, linking against spatialite library " +"\\*is\\* required." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:29 +msgid "" +"Although the Rasterlite documentation only mentions GIF, PNG, TIFF, JPEG " +"as compression formats for tiles, the driver supports reading and writing" +" internal tiles in any format handled by GDAL. Furthermore, the " +"Rasterlite driver also allow reading and writing as many bands and as " +"many band types as supported by the driver for the internal tiles." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:46 +msgid "Connection string syntax in read mode" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:48 +msgid "" +"Syntax: 'rasterlitedb_name' or " +"'RASTERLITE:rasterlitedb_name[,table=raster_table_prefix][,minx=minx_val,miny=miny_val,maxx=maxx_val,maxy=maxy_val][,level=level_number]" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:51 +#: ../../source/drivers/vector/sqlite.rst:167 +msgid "where :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:53 +msgid "*rasterlitedb_name* is the filename of the RasterLite DB." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:54 +msgid "" +"*raster_table_prefix* is the prefix of the raster table to open. For each" +" raster, there are 2 corresponding SQLite tables, suffixed with " +"\\_rasters and \\_metadata" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:57 +msgid "" +"*minx_val,miny_val,maxx_val,maxy_val* set a user-defined extent " +"(expressed in coordinate system units) for the raster that can be " +"different from the default extent." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:60 +msgid "" +"*level_number* is the level of the pyramid/overview to open, 0 being the " +"base pyramid." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:66 +msgid "" +"The driver can create a new database if necessary, create a new raster " +"table if necessary and copy a source dataset into the specified raster " +"table." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:70 +msgid "" +"If data already exists in the raster table, the new data will be added. " +"You can use the WIPE=YES creation options to erase existing data." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:73 +msgid "" +"The driver does not support updating a block in an existing raster table." +" It can only append new data." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:76 +msgid "" +"Syntax for the name of the output dataset: " +"'RASTERLITE:rasterlitedb_name,table=raster_table_prefix' or " +"'rasterlitedb_name'" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:80 +msgid "" +"It is possible to specify only the DB name as in the later form, but only" +" if the database does not already exists. In that case, the raster table " +"name will be base on the DB name itself." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:139 +msgid "|about-config-options| The following configuration option is supported:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:150 +msgid "" +"The driver supports building (if the dataset is opened in update mode) " +"and reading internal overviews." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:153 +msgid "" +"If no internal overview is detected, the driver will try using external " +"overviews (.ovr files)." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:156 +msgid "" +"Options can be used for internal overviews building. They can be " +"specified with the :config:`RASTERLITE_OVR_OPTIONS` configuration option," +" as a comma separated list of the above creation options. See below " +"examples." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:161 +msgid "All resampling methods supported by GDAL overviews are available." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:167 +msgid "" +"Some of the performance hints of the OGR SQLite driver apply. In " +"particular setting the OGR_SQLITE_SYNCHRONOUS configuration option to OFF" +" when creating a dataset or adding overviews might increase performance " +"on some filesystems." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:172 +msgid "" +"After having added all the raster tables and building all the needed " +"overview levels, it is advised to run :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:179 +msgid "" +"in order to optimize the database, and increase read performances " +"afterwards. This is particularly true with big rasterlite datasets. Note " +"that the operation might take a long time." +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:186 +msgid "Accessing a rasterlite DB with a single raster table :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:225 +msgid "Listing a multi-raster table DB :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:251 +msgid "Accessing a raster table within a multi-raster table DB:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:257 +msgid "Creating a new rasterlite DB with data encoded in JPEG tiles :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:263 +msgid "Creating internal overviews :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:269 +msgid "Cleaning internal overviews :" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:275 +msgid "Creating external overviews in a .ovr file:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:281 +msgid "Creating internal overviews with options (GDAL 1.10 or later):" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:287 +msgid ":" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:292 +msgid "" +"`Spatialite and Rasterlite home page <https://www.gaia-" +"gis.it/fossil/libspatialite/index>`__" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:294 +msgid "" +"`Rasterlite manual <http://www.gaia-gis.it/gaia-sins/rasterlite-docs" +"/rasterlite-man.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:296 +msgid "" +"`Rasterlite howto <http://www.gaia-gis.it/gaia-sins/rasterlite-docs" +"/rasterlite-how-to.pdf>`__" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:298 +msgid "" +"`Sample databases <http://www.gaia-" +"gis.it/spatialite-2.3.1/resources.html>`__" +msgstr "" + +#: ../../source/drivers/raster/rasterlite.rst:300 +#: ../../source/drivers/raster/rasterlite2.rst:196 +msgid ":ref:`OGR SQLite driver <vector.sqlite>`" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:5 +msgid "RasterLite2 - Rasters in SQLite DB" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:9 +#: ../../source/drivers/vector/sqlite.rst:6 +msgid "SQLite" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:11 +msgid "" +"The above short name is not a typo. The RasterLite2 functionality is part" +" of the :ref:`vector.sqlite` driver." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:16 +msgid "" +"The SQLite driver allows reading and writing SQLite databases containing " +"RasterLite2 coverages." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:21 +msgid "" +"Those databases can be produced by the utilities of the `RasterLite2 " +"<https://www.gaia-gis.it/fossil/librasterlite2>`__ distribution, such as " +"rl2tools." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:25 +msgid "" +"The driver supports reading grayscale, paletted, RGB, multispectral " +"images stored as tiles in the many compressed formats supported by " +"libRasterLite2. The driver also supports reading overviews/pyramids, " +"spatial reference system and spatial extent." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:27 +msgid "" +"GDAL/OGR must be compiled with sqlite support and against librasterlite2 " +"and libspatialite." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:30 +msgid "" +"The driver is implemented a unified SQLite / SpatiaLite / RasterLite2 " +"vector and raster capable driver." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:43 +#: ../../source/drivers/vector/gmlas.rst:34 +msgid "Opening syntax" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:45 +msgid "" +"A RasterLite2 filename can be specified as the connection string. If the " +"file contains a single RasterLite2 coverage, this one will be exposed as " +"the GDAL dataset. If the file contains multiple coverages, each one will " +"be exposed as a subdataset with the syntax " +"RASTERLITE2:filename:coverage_name. See `the basic concepts of " +"RasterLite2 <https://www.gaia-" +"gis.it/fossil/librasterlite2/wiki?name=basic_concepts>`__." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:52 +msgid "" +"If a coverage is made of several sections, they will be listed as " +"subdatasets of the coverage dataset, so as to be accessed individually. " +"By default, they will be exposed as a unified dataset. The syntax of " +"section-based dataset is " +"RASTERLITE2:filename:coverage_name:section_id:section_name." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:59 +#: ../../source/drivers/vector/driver_summary.rst:13 +msgid "Creation" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:61 +msgid "" +"The driver supports creating new databases from scratch, adding new " +"coverages to an existing database and adding sections to an existing " +"coverage." +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:146 +msgid "Reading a RasterLite2 database with a single coverage:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:152 +msgid "" +"Listing the subdatasets corresponding to the coverages of a RasterLite2 " +"database with several coverages:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:159 +msgid "Reading a subdataset corresponding to a coverage:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:165 +msgid "Creating a RasterLite2 dataset from a grayscale image:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:171 +msgid "" +"Creating a RasterLite2 dataset from a RGB image, and using JPEG " +"compression:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:178 +msgid "" +"Adding a RasterLite2 coverage to an existing SpatiaLite/RasterLite2 " +"database:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:185 +msgid "Adding pyramids to a coverage:" +msgstr "" + +#: ../../source/drivers/raster/rasterlite2.rst:194 +msgid "" +"`Rasterlite2 home page <https://www.gaia-" +"gis.it/fossil/librasterlite2/index>`__" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:5 +msgid "RDB - *RIEGL* Database" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:7 +msgid "RDB" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:13 +msgid "" +"GDAL can read \\*.mpx files in the RDB format, the in-house format used " +"by `RIEGL Laser Measurement Systems GmbH <http://www.riegl.com>`__ " +"through the RDB library." +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:15 +msgid "" +"The driver relies on the RDB library, which can be downloaded `here " +"<https://repository.riegl.com/software/libraries/rdblib>`__ . The minimum" +" version required of the rdblib is 2.2.0." +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:23 +msgid "Provided Bands" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:25 +msgid "" +"All attributes stored in the RDB, but the coordinates, are provided in " +"bands. Vector attributes are split up into multiple bands. The attributes" +" are currently mapped as follows:" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:29 +msgid "RDB attribute" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:29 +msgid "GDAL Band" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:31 +msgid "riegl.surface_normal[0]," +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:33 +msgid "riegl.surface_normal[1]," +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:35 +msgid "riegl.surface_normal[2]" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:31 +msgid "Band 1" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:33 +msgid "Band 2" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:35 +msgid "Band 3" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:37 +msgid "riegl.timestamp_min" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:37 +msgid "Band 4" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:39 +msgid "riegl.timestamp_max" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:39 +msgid "Band 5" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:41 +msgid "riegl.reflectance" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:41 +msgid "Band 6" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:43 +msgid "riegl.amplitude" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:43 +msgid "Band 7" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:45 +msgid "riegl.deviation" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:45 +msgid "Band 8" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:47 +msgid "riegl.height_center" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:47 +msgid "Band 9" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:49 +msgid "riegl.height_mean" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:49 +msgid "Band 10" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:51 +msgid "riegl.height_min" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:51 +msgid "Band 11" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:53 +msgid "riegl.height_max" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:53 +msgid "Band 12" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:55 +msgid "riegl.point_count" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:55 +msgid "Band 13" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:57 +msgid "riegl.point_count_grid_cell" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:57 +msgid "Band 14" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:59 +msgid "riegl.pca_thickness" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:59 +msgid "Band 15" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:61 +msgid "riegl.std_dev" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:61 +msgid "Band 16" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:63 +msgid "riegl.voxel_count" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:63 +msgid "Band 17" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:65 +msgid "riegl.id" +msgstr "" + +#: ../../source/drivers/raster/rdb.rst:65 +msgid "Band 18" +msgstr "" + +#: ../../source/drivers/raster/rik.rst:5 +msgid "RIK -- Swedish Grid Maps" +msgstr "" + +#: ../../source/drivers/raster/rik.rst:7 +msgid "RIK" +msgstr "" + +#: ../../source/drivers/raster/rik.rst:11 +msgid "" +"Supported by GDAL for read access. This format is used in maps issued by " +"the swedish organization Lantmäteriet. Supports versions 1, 2 and 3 of " +"the RIK format, but only 8 bits per pixel." +msgstr "" + +#: ../../source/drivers/raster/rik.rst:15 +msgid "" +"This driver is based on the work done in the `TRikPanel " +"<http://sourceforge.net/projects/trikpanel/>`__ project." +msgstr "" + +#: ../../source/drivers/raster/rik.rst:18 +msgid "NOTE: Implemented as :source_file:`frmts/rik/rikdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:5 +msgid "RMF -- Raster Matrix Format" +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:7 +msgid "RMF" +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:11 +msgid "" +"RMF is a simple tiled raster format used in the GIS \"Integration\" and " +"\"Panorama\" GIS. The format itself has very poor capabilities." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:14 +msgid "" +"There are two flavors of RMF called MTW and RSW. MTW supports 16-bit " +"integer and 32/64-bit floating point data in a single channel and aimed " +"to store DEM data. RSW is a general purpose raster. It supports single " +"channel colormapped or three channel RGB images. Only 8-bit data can be " +"stored in RSW. Simple georeferencing can be provided for both image " +"types." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:35 +msgid "**ELEVATION_MINIMUM**: Minimum elevation value (MTW only)." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:36 +msgid "**ELEVATION_MAXIMUM**: Maximum elevation value (MTW only)." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:37 +msgid "" +"**ELEVATION_UNITS**: Name of the units for raster values (MTW only). Can " +"be \"m\" (meters), \"cm\" (centimeters), \"dm\" (decimeters), \"mm\" " +"(millimeters)." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:40 +msgid "" +"**ELEVATION_TYPE**: Could be either 0 (absolute elevation) or 1 (total " +"elevation). MTW only." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:114 +msgid "Implemented as :source_file:`frmts/rmf/rmfdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/rmf.rst:115 +msgid "`\"Panorama\" GIS homepage <http://www.gisinfo.ru/index_en.htm>`__" +msgstr "" + +#: ../../source/drivers/raster/roi_pac.rst:5 +msgid "ROI_PAC -- ROI_PAC" +msgstr "" + +#: ../../source/drivers/raster/roi_pac.rst:11 +msgid "" +"Driver for the image formats used in the JPL's ROI_PAC project " +"(https://aws.roipac.org/). All image type are supported excepted .raw " +"images." +msgstr "" + +#: ../../source/drivers/raster/roi_pac.rst:15 +msgid "Metadata are stored in the ROI_PAC domain." +msgstr "" + +#: ../../source/drivers/raster/roi_pac.rst:17 +msgid "" +"Georeferencing is supported, but expect problems when using the UTM " +"projection, as ROI_PAC format do not store any hemisphere field." +msgstr "" + +#: ../../source/drivers/raster/roi_pac.rst:20 +msgid "" +"When creating files, you have to be able to specify the right data type " +"corresponding to the file type (slc, int, etc), else the driver will " +"output an error." +msgstr "" + +#: ../../source/drivers/raster/roi_pac.rst:24 +msgid "NOTE: Implemented as :source_file:`frmts/raw/roipacdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:5 +msgid "RPFTOC -- Raster Product Format/RPF (a.toc)" +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:7 +msgid "RPFTOC" +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:11 +msgid "" +"This is a read-only reader for RPF products, like CADRG or CIB, that uses" +" the table of content file - A.TOC - from a RPF exchange, and exposes it " +"as a virtual dataset whose coverage is the set of frames contained in the" +" table of content." +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:16 +msgid "" +"The driver will report a different subdataset for each subdataset found " +"in the A.TOC file." +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:19 +msgid "Result of a gdalinfo on a A.TOC file." +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:35 +msgid "" +"In some situations, :ref:`raster.nitf` tiles inside a subdataset don't " +"share the same palettes. The RPFTOC driver will do its best to remap " +"palettes to the reported palette by gdalinfo (which is the palette of the" +" first tile of the subdataset). In situations where it would not give a " +"good result, you can try to set the RPFTOC_FORCE_RGBA environment " +"variable to TRUE before opening the subdataset. This will cause the " +"driver to expose the subdataset as a RGBA dataset, instead of a paletted " +"one." +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:44 +msgid "" +"It is possible to build external overviews for a subdataset. The overview" +" for the first subdataset will be named A.TOC.1.ovr for example, for the " +"second dataset it will be A.TOC.2.ovr, etc. Note that you must re-open " +"the subdataset with the same setting of RPFTOC_FORCE_RGBA as the one you " +"have used when you have created it. Do not use any method other than " +"NEAREST resampling when building overviews on a paletted subdataset " +"(RPFTOC_FORCE_RGBA unset)" +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:52 +msgid "" +"A gdalinfo on one of this subdataset will return the various NITF " +"metadata, as well as the list of the NITF tiles of the subdataset." +msgstr "" + +#: ../../source/drivers/raster/rpftoc.rst:60 +msgid "NOTE: Implemented as :source_file:`frmts/nitf/rpftocdataset.cpp`" +msgstr "" + +#: ../../source/drivers/raster/rraster.rst:5 +msgid "RRASTER -- R Raster" +msgstr "" + +#: ../../source/drivers/raster/rraster.rst:7 +msgid "RRASTER" +msgstr "" + +#: ../../source/drivers/raster/rraster.rst:13 +msgid "" +"This is a read-only reader for the datasets handled by the `R Raster " +"package <https://cran.r-project.org/web/packages/raster/index.html>`__. " +"Those datasets are made of a .grd file, which is a text header file, and " +"a .gri binary file containing the raster data itself. The .grd is the " +"file opened by GDAL. Starting with GDAL 2.3, the driver will read " +"ratvalues as RAT or color tables. Layer names will be assigned to GDAL " +"band description. The 'creator' and 'created' attributes of the " +"'[general]' section will be assigned to the GDAL 'CREATOR' and 'CREATED' " +"dataset metadata items." +msgstr "" + +#: ../../source/drivers/raster/rraster.rst:23 +msgid "" +"Starting with GDAL 2.3, the driver has write capabilities. Color tables " +"or RAT will be written. The 'CREATOR' and 'CREATED' dataset metadata " +"items will be written as the 'creator' and 'created' attributes of the " +"'[general]' section. Band description will be written as the 'layername' " +"attribute of the '[description]' section." +msgstr "" + +#: ../../source/drivers/raster/rraster.rst:64 +msgid "" +"Description of the `\"rasterfile\" format " +"<https://rspatial.org/raster/pkg/appendix2.html>`__" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:5 +msgid "RS2 -- RadarSat 2 XML Product" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:7 +msgid "RS2" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:11 +msgid "" +"This driver will read some RadarSat 2 XML polarimetric products. In " +"particular complex products, and 16bit magnitude detected products." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:14 +msgid "" +"The RadarSat 2 XML products are distributed with a primary XML file " +"called product.xml, and a set of supporting XML data files with the " +"actual imagery stored in TIFF files. The RS2 driver will be used if the " +"product.xml or the containing directory is selected, and it can treat all" +" the imagery as one consistent dataset." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:20 +msgid "" +"The complex products use \"32bit void typed\" TIFF files which are not " +"meaningfully readable normally. The RS2 driver takes care of converting " +"this into useful CInt16 format internally." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:24 +msgid "" +"The RS2 driver also reads geolocation tiepoints from the product.xml file" +" and represents them as GCPs on the dataset." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:27 +msgid "" +"It is very likely that RadarSat International will be distributing other " +"sorts of datasets in this format; however, at this time this driver only " +"supports specific RadarSat 2 polarimetric products. All other will be " +"ignored, or result in various runtime errors. It is hoped that this " +"driver can be generalized when other product samples become available." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:41 +#: ../../source/drivers/raster/safe.rst:141 +msgid "Data Calibration" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:43 +msgid "" +"If you wish to have GDAL apply a particular calibration LUT to the data " +"when you open it, you have to open the appropriate subdatasets. The " +"following subdatasets exist within the SUBDATASET domain for RS2 " +"products:" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:48 +msgid "uncalibrated - open with RADARSAT_2_CALIB:UNCALIB: prepended to filename" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:50 +msgid "beta\\ :sub:`0` - open with RADARSAT_2_CALIB:BETA0: prepended to filename" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:52 +msgid "" +"sigma\\ :sub:`0` - open with RADARSAT_2_CALIB:SIGMA0: prepended to " +"filename" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:54 +msgid "gamma - open with RADARSAT_2_CALIB:GAMMA: prepended to filename" +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:56 +msgid "" +"Note that geocoded (SPG/SSG) products do not have this functionality " +"available. Also be aware that the LUTs must be in the product directory " +"where specified in the product.xml, otherwise loading the product with " +"the calibration LUT applied will fail." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:61 +msgid "" +"One caveat worth noting is that the RADARSAT-2 driver will supply the " +"calibrated data as GDT_Float32 or GDT_CFloat32 depending on the type of " +"calibration selected. The uncalibrated data is provided as " +"GDT_Int16/GDT_Byte/GDT_CInt16, also depending on the type of product " +"selected." +msgstr "" + +#: ../../source/drivers/raster/rs2.rst:70 +msgid "RadarSat document RN-RP-51-27." +msgstr "" + +#: ../../source/drivers/raster/s102.rst:5 +msgid "S102 -- S-102 Bathymetric Surface Product" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:7 +msgid "S102" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:13 +msgid "" +"This driver provides read-only support for bathymetry data in the S-102 " +"format, which is a specific product profile in an HDF5 file" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:16 +msgid "" +"S-102 files have two image bands representing depth (band 1), uncertainty" +" (band 2) values for each cell in a raster grid area." +msgstr "" + +#: ../../source/drivers/raster/s102.rst:19 +msgid "" +"Note that positive values of depth mean values *below* the reference " +"surface of the vertical datum. The :oo:`DEPTH_OR_ELEVATION` open option " +"can be set to ``ELEVATION`` to expose depth values as elevation values, " +"by negating their sign (i.e. positive values of elevation mean values " +"above the reference surface)" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:24 +#: ../../source/drivers/raster/s104.rst:25 +#: ../../source/drivers/raster/s111.rst:29 +msgid "Georeferencing is reported." +msgstr "" + +#: ../../source/drivers/raster/s102.rst:57 +msgid "" +"This is the default behavior of most GDAL formats, but the native " +"organization of the data in S-102 products is to have the first line of " +"the grid being the southern-most one. This native organization can be " +"exposed by the driver by setting this option to NO (in which case the 6th" +" term of the geotransform matrix will be positive)" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:66 +msgid "Starting with GDAL 3.9, GDAL can handle QualityOfSurvey spatial metadata." +msgstr "" + +#: ../../source/drivers/raster/s102.rst:68 +msgid "" +"When such spatial metadata is present, the subdataset list will include a" +" name of the form ``S102:\"{filename}\":QualityOfSurvey``" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:71 +msgid "" +"The ``/QualityOfSurvey/featureAttributeTable`` dataset is exposed as a " +"GDAL Raster Attribute Table associated to the GDAL raster band. The pixel" +" values of the raster match the ``id`` column of the Raster Attribute " +"Table." +msgstr "" + +#: ../../source/drivers/raster/s102.rst:78 +msgid "Implemented as :source_file:`frmts/hdf5/s102dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/s102.rst:79 +msgid "" +"`S-102 Bathymetric Surface Product Specification " +"<https://registry.iho.int/productspec/view.do?idx=199&product_ID=S-102&statusS=5&domainS=20&category=product_ID&searchValue=>`__" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:80 +#: ../../source/drivers/raster/s104.rst:59 +#: ../../source/drivers/raster/s111.rst:63 +msgid ":ref:`BAG driver <raster.bag>`" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:81 +#: ../../source/drivers/raster/s111.rst:65 +msgid ":ref:`S-104 driver <raster.s104>`" +msgstr "" + +#: ../../source/drivers/raster/s102.rst:82 +#: ../../source/drivers/raster/s104.rst:61 +msgid ":ref:`S-111 driver <raster.s111>`" +msgstr "" + +#: ../../source/drivers/raster/s104.rst:5 +msgid "S104 -- S-104 Water Level Information for Surface Navigation Product" +msgstr "" + +#: ../../source/drivers/raster/s104.rst:7 +msgid "S104" +msgstr "" + +#: ../../source/drivers/raster/s104.rst:13 +msgid "" +"This driver provides read-only support for water level data in the S-104 " +"format, which is a specific product profile in an HDF5 file." +msgstr "" + +#: ../../source/drivers/raster/s104.rst:16 +msgid "" +"S-104 files have two image bands representing water level height (band 1)" +" and water level trend (band 2) values for each cell in a raster grid " +"area." +msgstr "" + +#: ../../source/drivers/raster/s104.rst:19 +msgid "" +"When opening a S-104 file, no raster band is directly available. But a " +"list of subdatasets will be reported, one for each timestamp available in" +" the file." +msgstr "" + +#: ../../source/drivers/raster/s104.rst:22 +msgid "" +"An actual dataset can be opened through such a subdataset, with a syntax " +"like ``S104:\"filename.h5\":Group_001``." +msgstr "" + +#: ../../source/drivers/raster/s104.rst:27 +msgid "" +"Note that the driver currently only supports regularly gridded S104 " +"datasets." +msgstr "" + +#: ../../source/drivers/raster/s104.rst:48 +msgid "" +"This is the default behavior of most GDAL formats, but the native " +"organization of the data in S-104 products is to have the first line of " +"the grid being the southern-most one. This native organization can be " +"exposed by the driver by setting this option to NO (in which case the 6th" +" term of the geotransform matrix will be positive)" +msgstr "" + +#: ../../source/drivers/raster/s104.rst:57 +msgid "Implemented as :source_file:`frmts/hdf5/s104dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/s104.rst:58 +msgid "" +"`S-104 Bathymetric Surface Product Specification " +"<https://registry.iho.int/productspec/view.do?idx=198&product_ID=S-104&statusS=5&domainS=20&category=product_ID&searchValue=S-104>`__" +msgstr "" + +#: ../../source/drivers/raster/s111.rst:5 +msgid "S111 -- S-111 Surface Currents Product" +msgstr "" + +#: ../../source/drivers/raster/s111.rst:7 +msgid "S111" +msgstr "" + +#: ../../source/drivers/raster/s111.rst:13 +msgid "" +"This driver provides read-only support for surface currents in the S-111 " +"format, which is a specific product profile in an HDF5 file." +msgstr "" + +#: ../../source/drivers/raster/s111.rst:16 +msgid "" +"S-111 files have two image bands representing the following values for " +"each cell in a raster grid area:" +msgstr "" + +#: ../../source/drivers/raster/s111.rst:19 +msgid "surface current speed (band 1), in knots" +msgstr "" + +#: ../../source/drivers/raster/s111.rst:20 +msgid "" +"surface current direction (band 2), in degree measured from true north " +"clock-wise." +msgstr "" + +#: ../../source/drivers/raster/s111.rst:23 +msgid "" +"When opening a S-111 file, no raster band is directly available. But a " +"list of subdatasets will be reported, one for each timestamp available in" +" the file." +msgstr "" + +#: ../../source/drivers/raster/s111.rst:26 +msgid "" +"An actual dataset can be opened through such a subdataset, with a syntax " +"like ``S111:\"filename.h5\":Group_001``." +msgstr "" + +#: ../../source/drivers/raster/s111.rst:31 +msgid "" +"Note that the driver currently only supports regularly gridded S111 " +"datasets." +msgstr "" + +#: ../../source/drivers/raster/s111.rst:52 +msgid "" +"This is the default behavior of most GDAL formats, but the native " +"organization of the data in S-111 products is to have the first line of " +"the grid being the southern-most one. This native organization can be " +"exposed by the driver by setting this option to NO (in which case the 6th" +" term of the geotransform matrix will be positive)" +msgstr "" + +#: ../../source/drivers/raster/s111.rst:61 +msgid "Implemented as :source_file:`frmts/hdf5/s111dataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/s111.rst:62 +msgid "" +"`S-111 Bathymetric Surface Product Specification " +"<https://registry.iho.int/productspec/view.do?idx=178&product_ID=S-111&statusS=5&domainS=20&category=product_ID&searchValue=S-111>`__" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:5 +msgid "SAFE -- Sentinel-1 SAFE XML Product" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:7 +msgid "SAFE" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:11 +msgid "" +"Driver for Sentinel products. Currently supports only Sentinel-1 SAR " +"products. See also the :ref:`GDAL Sentinel-2 driver <raster.sentinel2>`" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:14 +msgid "" +"SENTINEL data products are distributed using a SENTINEL-specific " +"variation of the Standard Archive Format for Europe (SAFE) format " +"specification. The SAFE format has been designed to act as a common " +"format for archiving and conveying data within ESA Earth Observation " +"archiving facilities." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:20 +msgid "" +"The SAFE driver will be used if the manifest.safe or the containing " +"directory is selected, and it can treat all the imagery as one consistent" +" dataset." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:24 +msgid "" +"The SAFE driver also reads geolocation grid points from the metadata and " +"represents them as GCPs on the dataset." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:27 +msgid "" +"ESA will be distributing other satellite datasets in this format; " +"however, at this time this driver only supports specific Sentinel-1 SAR " +"products. All other will be ignored, or result in various runtime errors." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:40 +msgid "Multiple measurements" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:42 +msgid "" +"If the product contains multiple measurements (for example multiple " +"polarizations), each one is available as a raster band - if the swath is " +"the same. When the swath is the same, the geographic area is the same." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:46 +msgid "" +"If the product contains multiple swaths and multiple polatizations, the " +"driver shows the first swath by default. To access other swaths, the user" +" must select a specific subdataset." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:50 +msgid "" +"The syntax of subdataset naming and their content has been significantly " +"change in GDAL 3.4." +msgstr "" + +#: ../../source/drivers/raster/safe.rst:56 +msgid "Opening the Sentinel-1 product:" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:121 +msgid "It's not mandatory to open manifest.safe, just pass the folder name:" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:127 +msgid "Opening a single measurement (for example IW/VH):" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:134 +msgid "or starting with GDAL 3.4" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:143 +msgid "" +"Starting with GDAL 3.4, calibration is applied for SIGMA0, BETA0 and " +"GAMMA calibration subdataset" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:148 +msgid "" +"`SAR Formats (ESA Sentinel Online) <https://sentinel.esa.int/web/sentinel" +"/user-guides/sentinel-1-sar/data-formats/sar-formats>`__" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:150 +msgid "" +"`SAFE Specification (ESA Sentinel Online) " +"<https://sentinel.esa.int/web/sentinel/user-guides/sentinel-1-sar/data-" +"formats/safe-specification>`__" +msgstr "" + +#: ../../source/drivers/raster/safe.rst:152 +msgid ":ref:`GDAL Sentinel-2 driver <raster.sentinel2>`" +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:5 +msgid "SAR_CEOS -- CEOS SAR Image" +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:7 +msgid "SAR_CEOS" +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:11 +msgid "" +"This is a read-only reader for CEOS SAR image files. To use, select the " +"main imagery file." +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:14 +msgid "" +"This driver works with most Radarsat, JERS-1 and ERS data products, " +"including single look complex products; however, it is unlikely to work " +"for non-Radar CEOS products. The simpler :ref:`raster.ceos` driver is " +"often appropriate for these." +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:19 +msgid "" +"This driver will attempt to read 15 lat/long GCPS by sampling the per-" +"scanline CEOS superstructure information. In the case of products from " +"the Alaska Satellite Facility, it will obtain corner coordinates from " +"either the map projection record in the case of ScanSAR products, or the " +"facility data record for non-ScanSAR products. It also captures various " +"pieces of metadata from various header files, including:" +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:40 +msgid "" +"The SAR_CEOS driver also includes some support for SIR-C and PALSAR " +"polarimetric data. The SIR-C format contains an image in compressed " +"scattering matrix form, described `here " +"<http://southport.jpl.nasa.gov/software/dcomp/dcomp.html>`__. GDAL " +"decompresses the data as it is read in. The PALSAR format contains bands " +"that correspond almost exactly to elements of the 3x3 Hermitian " +"covariance matrix- see the `ERSDAC-VX-CEOS-004A.pdf " +"<http://www.ersdac.or.jp/palsar/palsar_E.html>`__ document for a complete" +" description (pixel storage is described on page 193). GDAL converts " +"these to complex floating point covariance matrix bands as they are read " +"in. The convention used to represent the covariance matrix in terms of " +"the scattering matrix elements HH, HV (=VH), and VV is indicated below. " +"Note that the non-diagonal elements of the matrix are complex values, " +"while the diagonal values are real (though represented as complex bands)." +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:63 +msgid "The identities of the bands are also reflected in the metadata." +msgstr "" + +#: ../../source/drivers/raster/sar_ceos.rst:65 +msgid "NOTE: Implemented as :source_file:`frmts/ceos2/sar_ceosdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:5 +msgid "SAGA -- SAGA GIS Binary Grid File Format" +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:7 +msgid "SAGA" +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:11 +msgid "" +"The driver supports both reading and writing (including create, delete, " +"and copy) SAGA GIS binary grids. SAGA binary grid datasets are made of an" +" ASCII header (.SGRD) and a binary data (.SDAT) file with a common " +"basename. The .SDAT file should be selected to access the dataset. " +"Starting with GDAL 2.3, the driver can read compressed .sg-grd-z files " +"that are ZIP archives with .sgrd, .sdat and .prj files." +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:18 +msgid "" +"The driver supports reading the following SAGA datatypes (in brackets the" +" corresponding GDAL types): BIT (GDT_Byte), BYTE_UNSIGNED (GDT_Byte), " +"BYTE (GDT_Byte), SHORTINT_UNSIGNED (GDT_UInt16), SHORTINT (GDT_Int16), " +"INTEGER_UNSIGNED (GDT_UInt32), INTEGER (GDT_Int32), FLOAT (GDT_Float32) " +"and DOUBLE (GDT_Float64)." +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:24 +msgid "" +"The driver supports writing the following SAGA datatypes: BYTE_UNSIGNED " +"(GDT_Byte), SHORTINT_UNSIGNED (GDT_UInt16), SHORTINT (GDT_Int16), " +"INTEGER_UNSIGNED (GDT_UInt32), INTEGER (GDT_Int32), FLOAT (GDT_Float32) " +"and DOUBLE (GDT_Float64)." +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:29 +msgid "" +"Currently the driver does not support zFactors other than 1 and reading " +"SAGA grids which are written TOPTOBOTTOM." +msgstr "" + +#: ../../source/drivers/raster/sdat.rst:32 +msgid "NOTE: Implemented as :source_file:`frmts/saga/sagadataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/sdts.rst:5 +msgid "SDTS -- USGS SDTS DEM" +msgstr "" + +#: ../../source/drivers/raster/sdts.rst:7 +#: ../../source/drivers/vector/driver_summary.rst:357 +#: ../../source/drivers/vector/sdts.rst:4 +#: ../../source/drivers/vector/sdts.rst:6 +msgid "SDTS" +msgstr "" + +#: ../../source/drivers/raster/sdts.rst:11 +msgid "" +"GDAL includes support for reading USGS SDTS formatted DEMs. USGS DEMs are" +" always returned with a data type of signed sixteen bit integer, or 32bit" +" float. Projection and georeferencing information is also returned." +msgstr "" + +#: ../../source/drivers/raster/sdts.rst:15 +msgid "" +"SDTS datasets consist of a number of files. Each DEM should have one file" +" with a name like XXXCATD.DDF. This should be selected to open the " +"dataset." +msgstr "" + +#: ../../source/drivers/raster/sdts.rst:19 +msgid "" +"The elevation units of DEMs may be feet or meters. The GetType() method " +"on a band will attempt to return if the units are Feet (\"ft\") or Meters" +" (\"m\")." +msgstr "" + +#: ../../source/drivers/raster/sdts.rst:23 +msgid "NOTE: Implemented as :source_file:`frmts/sdts/sdtsdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:5 +msgid "SENTINEL2 -- Sentinel-2 Products" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:7 +msgid "SENTINEL2" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:9 +msgid "" +"This driver is built-in by default, but requires a JPEG2000 capable " +"driver to read the imagery" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:11 +msgid "" +"Driver for Sentinel-2 Level-1B, Level-1C and Level-2A products. Starting " +"with GDAL 2.1.3, Level-1C with \"Safe Compact\" encoding are also " +"supported." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:15 +msgid "" +"The SENTINEL2 driver will be used if the main metadata .xml file at the " +"root of a SENTINEL2 data product is opened (whose name is typically " +"S2A_OPER_MTD_SAFL1C\\_....xml). It can also accept directly .zip files " +"downloaded from the `Sentinels Scientific Data Hub " +"<https://scihub.copernicus.eu/>`__" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:21 +msgid "" +"To be able to read the imagery, GDAL must be configured with at least one" +" of the JPEG2000 capable drivers." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:24 +msgid "" +"SENTINEL-2 data are acquired on 13 spectral bands in the visible and " +"near-infrared (VNIR) and Short-wavelength infrared (SWIR) spectrum, as " +"show in the below table:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:29 +msgid "Band name" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:29 +msgid "Resolution (m)" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:29 +msgid "Central wavelength (nm)" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:29 +msgid "Band width (nm)" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:29 +msgid "Purpose" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:31 +msgid "B01" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:31 +#: ../../source/drivers/raster/sentinel2.rst:40 +#: ../../source/drivers/raster/sentinel2.rst:41 +msgid "60" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:31 +msgid "443" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:31 +msgid "Aerosol detection" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:32 +msgid "B02" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:32 +#: ../../source/drivers/raster/sentinel2.rst:33 +#: ../../source/drivers/raster/sentinel2.rst:34 +#: ../../source/drivers/raster/sentinel2.rst:38 +msgid "10" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:32 +msgid "490" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:32 +msgid "65" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:32 +msgid "Blue" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:33 +msgid "B03" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:33 +msgid "560" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:33 +msgid "35" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:33 +msgid "Green" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:34 +msgid "B04" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:34 +msgid "665" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:34 +#: ../../source/drivers/raster/sentinel2.rst:41 +msgid "30" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:34 +msgid "Red" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:35 +msgid "B05" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:35 +msgid "705" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:35 +#: ../../source/drivers/raster/sentinel2.rst:36 +msgid "15" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:35 +#: ../../source/drivers/raster/sentinel2.rst:36 +#: ../../source/drivers/raster/sentinel2.rst:37 +#: ../../source/drivers/raster/sentinel2.rst:39 +msgid "Vegetation classification" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:36 +msgid "B06" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:36 +msgid "740" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:37 +msgid "B07" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:37 +msgid "783" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:38 +msgid "B08" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:38 +msgid "842" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:38 +msgid "115" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:38 +msgid "Near infrared" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:39 +msgid "B08A" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:39 +msgid "865" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:40 +msgid "B09" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:40 +msgid "945" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:40 +msgid "Water vapour" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:41 +msgid "B10" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:41 +msgid "1375" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:41 +msgid "Cirrus" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:42 +msgid "B11" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:42 +msgid "1610" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:42 +msgid "90" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:42 +#: ../../source/drivers/raster/sentinel2.rst:43 +msgid "Snow / ice / cloud discrimination" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:43 +msgid "B12" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:43 +msgid "2190" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:43 +msgid "180" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:54 +msgid "Level-1B" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:56 +msgid "" +"Level-1B products are composed of several \"granules\" of ~ 25 km across-" +"track x ~ 23km along-track, in sensor geometry (i.e. non ortho-" +"rectified). Each granule correspond to the imagery captured by one of the" +" 12 detectors across-track (for a total 290 km swath width). The imagery " +"of each band is put in a separate JPEG2000 file." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:62 +msgid "Level-1B products are aimed at advanced users." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:64 +msgid "" +"When opening the main metadata .xml file, the driver will typically " +"expose N \\* 3 sub-datasets, where N is the number of granules composing " +"the user product, and 3 corresponds to the number of spatial resolutions." +" There's one for the 4 10m bands, one for the 6 20m bands and one for the" +" 3 60m bands. Caution: the number of such subdatasets can be typically of" +" several hundreds or more." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:71 +msgid "" +"It is also possible to open the metadata .xml of a given granule, in " +"which case 3 subdatasets will be reported for each of the 3 spatial " +"resolutions." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:75 +msgid "" +"When opening a subdataset, the georeferencing is made of 5 ground control" +" points for the 4 corner of the images and the center of image." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:79 +msgid "Level-1C" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:81 +msgid "" +"Level-1C products are organized in ortho-rectified tiles of 100 km x 100 " +"km in UTM WGS84 projections. The imagery of each band is put in a " +"separate JPEG2000 file." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:85 +#: ../../source/drivers/raster/sentinel2.rst:120 +msgid "" +"When opening the main metadata .xml file, the driver will typically " +"expose 4 sub-datasets:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:88 +msgid "one for the 4 10m bands," +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:89 +msgid "one for the 6 20m bands," +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:90 +msgid "one for the 3 60m bands and," +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:91 +msgid "one for a preview of the R,G,B bands at a 320m resolution" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:93 +#: ../../source/drivers/raster/sentinel2.rst:134 +msgid "" +"All tiles of same resolution and projection are mosaiced together. If a " +"product spans over several UTM zones, they will be exposed as separate " +"subdatasets." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:97 +msgid "" +"It is also possible to open the metadata .xml file of each tile (only for" +" original L1C encoding, not supported on \"Safe Compact\" encoding), in " +"which case the driver will typically expose the 4 above mentioned types " +"of sub-datasets." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:103 +msgid "Level-2A" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:105 +msgid "" +"Similarly to Level-1C, Level-2A products are organized in ortho-rectified" +" tiles of 100 km x 100 km in UTM WGS84 projections. The imagery of each " +"band is put in a separate JPEG2000 file. The values are Bottom-Of-" +"Atmosphere (BOA) reflectances. L2A specific bands are also computed:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:111 +msgid "AOT: Aerosol Optical Thickness map (at 550nm)" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:112 +msgid "" +"CLD: Raster mask values range from 0 for high confidence clear sky to 100" +" for high confidence cloudy" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:114 +msgid "" +"SCL: Scene Classification. The meaning of the values is indicated in the " +"Category Names of the band." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:116 +msgid "" +"SNW: Raster mask values range from 0 for high confidence NO snow/ice to " +"100 for high confidence snow/ice" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:118 +msgid "WVP: Scene-average Water Vapour map" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:123 +msgid "one for the 4 native 10m bands, and L2A specific bands (AOT and WVP)" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:124 +msgid "" +"one for the 6 native 20m bands, and L2A specific bands (AOT, WVP, SCL, " +"CLD and SNW)," +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:126 +msgid "" +"one for the B01 and B09 native 60m bands, and L2A specific bands (AOT, " +"WVP, SCL, CLD and SNW)," +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:128 +msgid "" +"one for a true-color image (TCI) of the R,G,B bands at a 10m resolution, " +"for the \"compact\" L2A product formulation (or a preview of the R,G,B " +"bands at a 320m resolution for the older L2A product formulation). The " +"TCI products at resolution 20m and 60m are not exposed, as they are just " +"subsampled versions of the 10m product." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:141 +msgid "" +"Metadata of the main metadata .xml file is available in the general " +"metadata domain. The whole XML file is also accessible through the " +"xml:SENTINEL2 metadata domain." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:145 +msgid "" +"Subdatasets are based on the VRT format, so the definition of this VRT " +"can be obtained by querying the xml:VRT metadata domain." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:149 +msgid "Performance issues for L1C and L2A" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:151 +msgid "" +"Due to the way Sentinel-2 products are structured, in particular because " +"of the number of JPEG2000 files involved, zoom-out operations can be very" +" slow for products made of many tiles. For interactive display, it can be" +" useful to generate overviews (can be a slow operation by itself). This " +"can be done with the gdaladdo utility on the subdataset name. The " +"overview file is created next to the main metadata .xml file, with the " +"same name, but prefixed with \\_XX_EPSG_YYYYY.tif.ovr where " +"XX=10m,20m,60m or PREVIEW and YYYYY is the EPSG code." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:160 +msgid "" +"Trick: if the content of the zoom-out preview is not important for the " +"use case, blank overviews can be created instantaneously by using the " +"NONE resampling method ('-r none' as gdaladdo switch)." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:164 +msgid "" +"When converting a subdataset to another format like tiled GeoTIFF, if " +"using the JP2OpenJPEG driver, the recommended minimum value for the " +":config:`GDAL_CACHEMAX` configuration option is (subdataset_width \\* " +"2048 \\* 2 ) / 10000000 if generating a INTERLEAVE=BAND GeoTIFF, or that " +"value multiplied by the number of bands for the default INTERLEAVE=PIXEL " +"configuration. The current versions of the OpenJPEG libraries can also " +"consume a lot of memory to decode a JPEG2000 tile (up to 600MB), so you " +"might want to specify the :config:`GDAL_NUM_THREADS` configuration option" +" to a reasonable number of threads if you are short of memory (the " +"default value is the total number of virtual CPUs)." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:178 +msgid "|about-open-options| The driver can be passed the following open options:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:189 +msgid "" +"0 on areas with no tiles, or when the tile data is set to the NODATA or " +"SATURATED special values," +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:191 +msgid "4095 on areas with valid data." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:193 +msgid "" +"Note: above open options can also be specified as configuration options, " +"by prefixing the open option name with SENTINEL2\\_ (e.g. " +"SENTINEL2_ALPHA)." +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:200 +msgid "Opening the main metadata file of a Sentinel2 product:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:257 +msgid "Opening the .zip file directly:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:263 +msgid "Opening the 10 meters resolution bands of a L1C subdataset:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:337 +msgid "Conversion of a L1C subdataset to tiled GeoTIFF" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:345 +msgid "Generating blank overviews for a L1C subdataset:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:351 +msgid "" +"Creating a VRT file from the subdataset (can be convenient to have the " +"subdatasets as files):" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:359 +msgid "Opening the 10 meters resolution bands of a L1B subdataset:" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:457 +msgid "`Sentinels Scientific Data Hub <https://scihub.esa.int/>`__" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:458 +msgid "" +"`Sentinel 2 User guide <https://sentinels.copernicus.eu/web/sentinel" +"/user-guides/sentinel-2-msi>`__" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:460 +msgid "" +"`Sentinel 2 User Handbook <https://sentinels.copernicus.eu/web/sentinel" +"/user-guides/document-" +"library/-/asset_publisher/xlslt4309D5h/content/sentinel-2-user-" +"handbook>`__" +msgstr "" + +#: ../../source/drivers/raster/sentinel2.rst:466 +msgid "" +"This driver has been developed by `Spatialys <http://spatialys.com>`__ " +"with funding from `Centre National d'Etudes Spatiales (CNES) " +"<https://cnes.fr>`__" +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:5 +msgid "SGI -- SGI Image Format" +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:7 +msgid "SGI" +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:11 +msgid "" +"The SGI driver currently supports the reading and writing of SGI Image " +"files." +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:14 +msgid "" +"The driver currently supports 1, 2, 3, and 4 band images. The driver " +"currently supports \"8 bit per channel value\" images. The driver " +"supports both uncompressed and run-length encoded (RLE) images for " +"reading, but created files are always RLE compressed.." +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:19 +msgid "The GDAL SGI Driver was based on Paul Bourke's SGI image read code." +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:23 +msgid "" +"`Paul Bourke's SGI Image Read Code " +"<http://astronomy.swin.edu.au/~pbourke/dataformats/sgirgb/>`__" +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:25 +msgid "" +"`SGI Image File Format Document " +"<ftp://ftp.sgi.com/graphics/SGIIMAGESPEC>`__" +msgstr "" + +#: ../../source/drivers/raster/sgi.rst:28 +msgid "NOTE: Implemented as :source_file:`frmts/sgi/sgidataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/sigdem.rst:5 +msgid "SIGDEM -- Scaled Integer Gridded DEM" +msgstr "" + +#: ../../source/drivers/raster/sigdem.rst:7 +msgid "SIGDEM" +msgstr "" + +#: ../../source/drivers/raster/sigdem.rst:13 +msgid "" +"The SIGDEM driver supports reading and writing `Scaled Integer Gridded " +"DEM <https://github.com/revolsys/sigdem>`__ files." +msgstr "" + +#: ../../source/drivers/raster/sigdem.rst:16 +msgid "" +"SIGDEM files contain exactly 1 band. The in-memory band data is stored " +"using GDT_Float64." +msgstr "" + +#: ../../source/drivers/raster/sigdem.rst:19 +msgid "" +"SIGDEM prefers use of an EPSG ID inside the file for coordinate systems. " +"Only if the spatial reference doesn't have an EPSG ID will a .prj file be" +" written or read." +msgstr "" + +#: ../../source/drivers/raster/sigdem.rst:23 +msgid "NOTE: Implemented as :source_file:`frmts/sigdem/sigdemdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/snodas.rst:5 +msgid "SNODAS -- Snow Data Assimilation System" +msgstr "" + +#: ../../source/drivers/raster/snodas.rst:7 +msgid "SNODAS" +msgstr "" + +#: ../../source/drivers/raster/snodas.rst:11 +msgid "" +"This is a convenience driver to read Snow Data Assimilation System data. " +"Those files contain Int16 raw binary data. The file to provide to GDAL is" +" the .Hdr file." +msgstr "" + +#: ../../source/drivers/raster/snodas.rst:15 +msgid "" +"`Snow Data Assimilation System (SNODAS) Data Products at NSIDC " +"<http://nsidc.org/data/docs/noaa/g02158_snodas_snow_cover_model/index.html>`__" +msgstr "" + +#: ../../source/drivers/raster/snodas.rst:18 +msgid "NOTE: Implemented as :source_file:`frmts/raw/snodasdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/srp.rst:5 +msgid "SRP -- Standard Product Format (ASRP/USRP) (.gen)" +msgstr "" + +#: ../../source/drivers/raster/srp.rst:7 +msgid "SRP" +msgstr "" + +#: ../../source/drivers/raster/srp.rst:11 +msgid "" +"The ASRP and USRP raster products (as defined by DGIWG) are variations on" +" a common standard product format and are supported for reading by GDAL. " +"ASRP and USRP datasets are made of several files - typically a .GEN, " +".IMG, .SOU and .QAL file with a common basename. The .IMG file should be " +"selected to access the dataset." +msgstr "" + +#: ../../source/drivers/raster/srp.rst:17 +msgid "" +"ASRP (in a geographic coordinate system) and USRP (in a UTM/UPS " +"coordinate system) products are single band images with a palette and " +"georeferencing." +msgstr "" + +#: ../../source/drivers/raster/srp.rst:21 +msgid "" +"the Transmission Header File (.THF) can also be used as an input to GDAL." +" If the THF references more than one image, GDAL will report the images " +"it is composed of as subdatasets. If the THF references just one image, " +"GDAL will open it directly." +msgstr "" + +#: ../../source/drivers/raster/srp.rst:26 +msgid "NOTE: Implemented as :source_file:`frmts/adrg/srpdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:5 +msgid "SRTMHGT -- SRTM HGT Format" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:7 +msgid "SRTMHGT" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:11 +msgid "" +"The SRTM HGT driver currently supports the reading of SRTM-3 and SRTM-1 " +"V2 (HGT) files. The files must be named like NXXEYYY.hgt, or starting " +"with GDAL 2.1.2, NXXEYYY[.something].hgt" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:15 +msgid "" +"Starting with GDAL 2.2, the driver can directly read .hgt.zip files " +"provided that they are named like NXXEYYY[.something].hgt.zip and contain" +" a NXXEYYY.hgt file. For previous versions, use " +"/vsizip//path/to/NXXEYYY[.something].hgt.zip/NXXEYYY.hgt syntax" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:20 +msgid "" +"The driver does support creating new files, but the input data must be " +"exactly formatted as a SRTM-3 or SRTM-1 cell. That is the size, and " +"bounds must be appropriate for a cell." +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:26 +msgid "" +"`SRTM documentation " +"<http://dds.cr.usgs.gov/srtm/version2_1/Documentation>`__" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:28 +msgid "`SRTM FAQ <http://www2.jpl.nasa.gov/srtm/faq.html>`__" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:29 +msgid "`SRTM data <http://dds.cr.usgs.gov/srtm/version2_1/>`__" +msgstr "" + +#: ../../source/drivers/raster/srtmhgt.rst:31 +msgid "NOTE: Implemented as :source_file:`frmts/srtmhgt/srtmhgtdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:5 +msgid "STACIT - Spatio-Temporal Asset Catalog Items" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:9 +msgid "STACIT" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:13 +msgid "" +"This driver supports opening STAC API ItemCollections, with the input " +"usually being a `STAC API search query <https://github.com/radiantearth" +"/stac-api-spec/tree/main/item-search>`_ or the results saved as a JSON " +"file. Items in the response must include projection information following" +" the `Projection Extension Specification <https://github.com/stac-" +"extensions/projection/>`_. It builds a virtual mosaic from the items." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:16 +msgid "" +"A STACIT dataset which has no subdatasets is actually a :ref:`raster.vrt`" +" dataset. Thus, translating it into VRT will result in a VRT file that " +"directly references the items." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:19 +msgid "" +"Note that `STAC API ItemCollections <https://github.com/radiantearth" +"/stac-api-spec/blob/main/fragments/itemcollection/README.md>`_ are not " +"the same as `STAC Collections <https://github.com/radiantearth/stac-" +"spec/tree/master/collection-spec>`_. STAC API ItemCollections are GeoJSON" +" FeatureCollections enhanced with STAC entities." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:22 +#: ../../source/drivers/raster/stacta.rst:36 +#: ../../source/drivers/raster/wms.rst:453 +#: ../../source/drivers/raster/wmts.rst:25 +#: ../../source/drivers/vector/gtfs.rst:24 +msgid "Open syntax" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:24 +msgid "" +"STACIT datasets/subdatasets can be accessed with one of the following " +"syntaxes:" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:26 +#: ../../source/drivers/raster/stacta.rst:40 +msgid "``filename.json``: local file" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:28 +msgid "``STACIT:\"https://example.com/filename.json\"``: remote file or query" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:30 +msgid "" +"``STACIT:\"filename.json\":asset=my_asset``: specify the name of the " +"asset GDAL should read (i.e. \"visual\")" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:32 +msgid "" +"``STACIT:\"filename.json\":collection=my_collect,asset=my_asset``: limit " +"to items in a given collection and specify asset to read" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:34 +msgid "" +"``STACIT:\"filename.json\":collection=my_collect,asset=my_asset,crs=my_crs``:" +" specify a collection, asset, and limit to items in a given CRS" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:36 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if STACIT`` option to command " +"line utilities accepting it, or ``STACIT`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename or URL." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:79 +msgid "" +"Starting with GDAL 3.9.1, the ``REMOVE_IF_NO_NODATA`` strategy is applied" +" by default. The STACIT virtual mosaic will omit fully covered items, " +"only if no band declares a nodata value. (Note that the determination " +"whether a band has a nodata value of not is done by opening one of the " +"items, and assuming it is representative of the characteristics of the " +"others in the collection)." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:86 +msgid "" +"This strategy can be forced in all cases by selecting the " +"``USE_MOST_RECENT`` strategy (this was the strategy applied prior to " +"3.9.1)" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:89 +msgid "" +"The ``USE_ALL`` strategy always causes all items to be listed in the " +"virtual mosaic, with the most recent ones being rendered on top of the " +"less recent ones." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:96 +msgid "" +"If a STACIT JSON file contains several collections, assets or CRS, the " +"driver will return a list of subdataset names to open each of the " +"possible subdatasets." +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:108 +msgid "" +"List the subdatasets associated to a `STAC search " +"<https://github.com/radiantearth/stac-api-spec/tree/master/item-search>`_" +" on a given collection, bbox and starting from a datetime:" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:116 +msgid "Open a subdataset returned by the above request:" +msgstr "" + +#: ../../source/drivers/raster/stacit.rst:126 +msgid ":ref:`raster.stacta` documentation page." +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:5 +msgid "STACTA - Spatio-Temporal Asset Catalog Tiled Assets" +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:9 +msgid "STACTA" +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:13 +msgid "" +"This driver supports opening JSON files following the `Spatio-Temporal " +"Asset Catalog Tiled Assets <https://github.com/stac-extensions/tiled-" +"assets>`_ specification. Such JSON file references tiles (also called " +"metatiles), split from a potentially big dataset according to a tiling " +"scheme, with several zoom levels. The driver provides a single raster " +"view, with overviews, of the dataset described by the JSON file. The " +"driver supports metatiles of arbitrary size." +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:20 +msgid "" +"The driver may use the `Electro-Optical Extension <https://github.com" +"/stac-extensions/eo>`__ and, starting with GDAL 3.8.2, the `Raster " +"Extension <https://github.com/stac-extensions/raster>`__ attached to an " +"asset template." +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:38 +msgid "" +"STACTA datasets/subdatasets can be accessed with one of the following " +"syntaxes:" +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:42 +msgid "``STACTA:\"https://example.com/filename.json\"``: remote file" +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:44 +msgid "" +"``STACTA:\"filename.json\":my_asset``: specify an asset of a local/remote" +" file" +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:46 +msgid "" +"``STACTA:\"filename.json\":my_asset:my_tms``: specify an asset and tiling" +" scheme of a local/remote file" +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:48 +msgid "The root of the JSON file must be of type ``Feature``." +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:50 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if STACTA`` option to command " +"line utilities accepting it, or ``STACTA`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename or URL." +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:80 +msgid "" +"If a STACTA JSON file contains several asset templates and/or tiling " +"scheme, the driver will return a list of subdataset names to open each of" +" the possible subdatasets." +msgstr "" + +#: ../../source/drivers/raster/stacta.rst:92 +msgid ":ref:`raster.stacit` documentation page." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:5 +msgid "Terragen -- Terragen™ Terrain File" +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:7 +msgid "Terragen" +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:11 +msgid "" +"Terragen terrain files store 16-bit elevation values with optional " +"gridspacing (but not positioning). The file extension for Terragen " +"heightfields is \"TER\" or \"TERRAIN\" (which in the former case is the " +"same as Leveller, but the driver only recognizes Terragen files). The " +"driver ID is \"Terragen\". The dataset is file-based and has only one " +"elevation band. Void elevations are not supported. Pixels are considered " +"points." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:33 +msgid "" +"``dataset::GetProjectionRef()`` returns a local coordinate system using " +"meters." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:36 +msgid "``band::GetUnitType()`` returns meters." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:38 +msgid "" +"Elevations are ``Int16``. You must use the ``band::GetScale()`` and " +"``band::GetOffset()`` to convert them to meters." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:46 +msgid "" +"Use the ``Create`` call. Set the ``MINUSERPIXELVALUE`` option (a float) " +"to the lowest elevation of your elevation data, and ``MAXUSERPIXELVALUE``" +" to the highest. The units must match the elevation units you will give " +"to ``band::SetUnitType()``." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:51 +msgid "" +"Call ``dataset::SetProjection()`` and ``dataset::SetGeoTransform()`` with" +" your coordinate system details. Otherwise, the driver will not encode " +"physical elevations properly. Geographic (degree-based) coordinate " +"systems will be converted to a local meter-based system." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:56 +msgid "" +"To maintain precision, a best-fit baseheight and scaling will be used to " +"use as much of the 16-bit range as possible." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:59 +msgid "Elevations are ``Float32``." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:64 +msgid "Roundtripping" +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:66 +msgid "" +"Errors per trip tend to be a few centimeters for elevations and up to one" +" or two meters for ground extents if degree-based coordinate systems are " +"written. Large degree-based DEMs incur unavoidable distortions since the " +"driver currently only uses meters." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:74 +msgid "Implemented as :source_file:`frmts/terragen/terragendataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:75 +msgid "" +"See `readme.txt <./readme.txt>`__ for installation and support " +"information." +msgstr "" + +#: ../../source/drivers/raster/terragen.rst:77 +msgid "" +"`Terragen Terrain File Specification " +"<http://www.planetside.co.uk/terragen/dev/tgterrain.html>`__." +msgstr "" + +#: ../../source/drivers/raster/tga.rst:5 +msgid "TGA -- TARGA Image File Format" +msgstr "" + +#: ../../source/drivers/raster/tga.rst:9 +msgid "TGA" +msgstr "" + +#: ../../source/drivers/raster/tga.rst:13 +msgid "The TGA driver currently supports reading TGA 2.0 files." +msgstr "" + +#: ../../source/drivers/raster/tga.rst:15 +msgid "" +"The driver supports reading 1 (grey-level or paletted), 3 (RGB), and 4 " +"(RGBA, or RGB-undefined) band images. The driver supports both " +"uncompressed or RLE-compressed images. Top-left or bottom-left origins " +"are supported (if the later, the lines are re-order to expose a top-left " +"order). 16-bit RGB encoded images are also supported." +msgstr "" + +#: ../../source/drivers/raster/tga.rst:21 +msgid "" +"The following metadata items may be reported: IMAGE_ID, AUTHOR_NAME and " +"COMMENTS. The extended area is used to determine if the fourth band is an" +" alpha channel or not." +msgstr "" + +#: ../../source/drivers/raster/tga.rst:33 +msgid "" +"`Format specification " +"<http://www.dca.fee.unicamp.br/~martino/disciplinas/ea978/tgaffs.pdf>`_" +msgstr "" + +#: ../../source/drivers/raster/til.rst:5 +msgid "TIL -- EarthWatch/DigitalGlobe .TIL" +msgstr "" + +#: ../../source/drivers/raster/til.rst:7 +msgid "TIL" +msgstr "" + +#: ../../source/drivers/raster/til.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/til/tildataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:5 +msgid "TileDB - TileDB raster" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:7 +#: ../../source/drivers/vector/tiledb.rst:7 +msgid "TileDB" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:13 +msgid "GDAL can read and write TileDB arrays through the TileDB library." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:15 +#: ../../source/drivers/vector/tiledb.rst:15 +msgid "" +"The driver relies on the Open Source TileDB `library <https://github.com" +"/TileDB-Inc/TileDB>`__ (MIT licensed)." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:32 +msgid "The following open options exist:" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:60 +msgid "The following creation options exist:" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:108 +msgid "" +"``BAND``: a 3D array is created with the slowest varying dimension being " +"the band." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:109 +msgid "" +"``PIXEL``: a 3D array is created with the fastest varying dimension being" +" the band." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:110 +msgid "" +"``ATTRIBUTES``: a 2D array is created with each band being stored in a " +"separate TileDB attribute." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:124 +msgid "" +"When the dataset is created within a TileDB group, overviews that may be " +"created are stored as TileDB arrays inside that group, next to the full " +"resolution array. This makes administration of the dataset easier." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:128 +msgid "" +"Otherwise, the past default behavior (CREATE_GROUP=NO) is to create the " +"dataset as a TileDB array. Overviews cannot be created in that mode." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:137 +msgid "" +"The TileDB driver supports the :ref:`multidim_raster_data_model` for " +"reading and writing operations. It requires GDAL to be built and run " +"against TileDB >= 2.15." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:140 +msgid "" +"The driver supports: - creating and reading groups and subgroups - " +"creating and reading multidimensional dense arrays with a numeric data " +"type - creating and reading numeric or string attributes in groups and " +"arrays - storing an indexing array of a dimension as a TileDB dimension " +"label" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:146 +msgid "" +"The multidimensional API supports reading dense arrays created by the " +"classic raster API of GDAL." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:149 +msgid "The following multidimensional dataset open options are available:" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:151 +#: ../../source/drivers/raster/tiledb.rst:159 +msgid "" +"**TILEDB_CONFIG=config**: A local file with TileDB configuration `options" +" <https://docs.tiledb.io/en/stable/tutorials/config.html>`__" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:154 +#: ../../source/drivers/raster/tiledb.rst:167 +msgid "" +"**TILEDB_TIMESTAMP=val**: inclusive ending timestamp when opening this " +"array" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:157 +msgid "The following multidimensional dataset creation options are available:" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:162 +#: ../../source/drivers/raster/tiledb.rst:182 +msgid "" +"**TILEDB_TIMESTAMP=val**: Create array at this timestamp. Should be " +"strictly greater than zero when set." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:165 +msgid "The following array open options are available:" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:170 +msgid "The following array creation options are available:" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:172 +msgid "**BLOCKSIZE=val1,val2,...,valN**: Block size in pixels" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:174 +msgid "" +"**COMPRESSION=NONE/GZIP/ZSTD/LZ4/RLE/BZIP2/DOUBLE-DELTA/POSITIVE-DELTA**:" +" Compression to use. Default is NONE" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:177 +msgid "**COMPRESSION_LEVEL=int_value**: compression level" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:179 +msgid "" +"**IN_MEMORY=YES/NO**: hether the array should be only in-memory. Useful " +"to create an indexing variable that is serialized as a dimension label" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:185 +msgid "" +"Cf :source_file:`autotest/gdrivers/tiledb_multidim.py` for examples of " +"how to use the Python multidimensional API with the TileDB driver." +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:191 +#: ../../source/drivers/vector/tiledb.rst:240 +msgid "`TileDB home page <https://tiledb.io/>`__" +msgstr "" + +#: ../../source/drivers/raster/tiledb.rst:193 +msgid ":ref:`TileDB vector <vector.tiledb>` documentation page" +msgstr "" + +#: ../../source/drivers/raster/tsx.rst:5 +msgid "TSX -- TerraSAR-X Product" +msgstr "" + +#: ../../source/drivers/raster/tsx.rst:7 +msgid "TSX" +msgstr "" + +#: ../../source/drivers/raster/tsx.rst:11 +msgid "NOTE: Implemented as :source_file:`frmts/tsx/tsxdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:5 +msgid "USGSDEM -- USGS ASCII DEM (and CDED)" +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:7 +msgid "USGSDEM" +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:11 +msgid "" +"GDAL includes support for reading USGS ASCII DEM files. This is the " +"traditional format used by USGS before being replaced by SDTS, and is the" +" format used for CDED DEM data products from Canada. Most popular " +"variations on USGS DEM files should be supported, including correct " +"recognition of coordinate system, and georeferenced positioning." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:17 +msgid "" +"The 7.5 minute (UTM grid) USGS DEM files will generally have regions of " +"missing data around the edges, and these are properly marked with a " +"nodata value. Elevation values in USGS DEM files may be in meters or " +"feet, and this will be indicated by the return value of " +"GDALRasterBand::GetUnitType() (either \"m\" or \"ft\")." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:23 +msgid "" +"Note that USGS DEM files are represented as one big tile. This may cause " +"cache thrashing problems if the GDAL tile cache size is small. It will " +"also result in a substantial delay when the first pixel is read as the " +"whole file will be ingested." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:28 +msgid "" +"Some of the code for implementing usgsdemdataset.cpp was derived from VTP" +" code by Ben Discoe. See the `Virtual Terrain " +"<http://www.vterrain.org/>`__ project for more information on VTP." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:45 +msgid "" +"GDAL supports export of geographic (and UTM) USGS DEM and CDED data " +"files, including the ability to generate CDED 2.0 50K products to " +"Canadian federal government specifications." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:49 +msgid "" +"Input data must already be sampled in a geographic or UTM coordinate " +"system. By default the entire area of the input file will be output, but " +"for CDED50K products the output file will be sampled at the production " +"specified resolution and on product tile boundaries." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:54 +msgid "" +"If the input file has appropriate coordinate system information set, " +"export to specific product formats can take input in different coordinate" +" systems (i.e. from Albers projection to NAD83 geographic for CDED50K " +"production)." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:146 +msgid "" +"Example: The following would generate a single CDED50K tile, extracting " +"from the larger DEM coverage yk_3arcsec for a tile with the top left " +"corner -117w,60n. The file yk_template.dem is used to set some product " +"fields including the Producer of Data, Process Code and Origin Code " +"fields." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:159 +msgid "NOTE: Implemented as :source_file:`frmts/usgsdem/usgsdemdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/usgsdem.rst:161 +msgid "" +"The USGS DEM reading code in GDAL was derived from the importer in the " +"`VTP <http://www.vterrain.org/>`__ software. The export capability was " +"developed with the financial support of the Yukon Department of " +"Environment." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:5 +msgid "VICAR -- VICAR" +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:12 +msgid "" +"PDS3 datasets can incorporate a VICAR header. By default, GDAL will use " +"the :ref:`PDS <raster.pds>` driver in that situation. Starting with GDAL " +"3.1, if the :config:`GDAL_TRY_PDS3_WITH_VICAR` configuration option is " +"set to YES, the dataset will be opened by the VICAR driver. " +"Alternatively, starting with GDAL 3.10, specifying the ``-if VICAR`` " +"option to command line utilities accepting it, or ``VICAR`` as the only " +"value of the ``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also " +"forces the driver to recognize the passed filename." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:37 +msgid "" +"Starting with GDAL 3.1, the VICAR label can be retrieved as JSON-" +"serialized content in the json:VICAR metadata domain." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:137 +msgid "Binary prefixes" +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:139 +msgid "" +"Starting with GDAL 3.1, if the VICAR label declares a non-zero binary " +"prefix length (`NBB` label item), then GDAL will look in the `vicar.json`" +" configuration file if there is an entry corresponding to the `BLTYPE` " +"label item (currently only M94_HRSC is defined), and if there is a match," +" a OGR vector layer will be available on the dataset, with a feature for " +"each image record." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:183 +msgid "" +"Starting with GDAL 3.1, the VICAR driver supports updating imagery of " +"existing datasets, creating new datasets through the CreateCopy() and " +"Create() interfaces." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:187 +msgid "" +"When using CreateCopy(), gdal_translate or gdalwarp, an effort is made to" +" preserve as much as possible of the original label when doing VICAR to " +"VICAR conversions. This can be disabled with the :co:`USE_SRC_LABEL=NO` " +"creation option." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:224 +msgid "" +"Value of MAP.TARGET_NAME. This is normally deduced from the SRS datum " +"name. If specified, and USE_SRC_MAP is in effect, this will be taken into" +" account to override the source TARGET_NAME." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:251 +msgid "Implemented as :source_file:`frmts/pds/vicardataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:252 +msgid "`VICAR documentation <https://www-mipl.jpl.nasa.gov/vicar.html>`_" +msgstr "" + +#: ../../source/drivers/raster/vicar.rst:253 +msgid "" +"`VICAR file format <https://www-" +"mipl.jpl.nasa.gov/external/VICAR_file_fmt.pdf>`_" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:5 +msgid "VRT -- GDAL Virtual Format" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:7 ../../source/drivers/vector/vrt.rst:6 +msgid "VRT" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:14 +msgid "" +"The VRT driver is a format driver for GDAL that allows a virtual GDAL " +"dataset to be composed from other GDAL datasets with repositioning, and " +"algorithms potentially applied as well as various kinds of metadata " +"altered or added. VRT descriptions of datasets can be saved in an XML " +"format normally given the extension .vrt." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:20 +msgid "Note .vrt files starting with" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:22 +msgid "<OGRVRTDataSource> open with :ref:`ogrinfo`, etc." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:23 +msgid "<VRTDataset> open with :ref:`gdalinfo`, etc." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:25 +msgid "" +"The VRT format can also describe :ref:`gdal_vrttut_warped` and " +":ref:`gdal_vrttut_pansharpen`" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:28 +msgid "" +"For mosaic with a very large number of tiles (tens of thousands or " +"mores), the :ref:`GTI <raster.gti>` driver may be used starting with GDAL" +" 3.9." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:31 +msgid "" +"An example of a simple .vrt file referring to a 512x512 dataset with one " +"band loaded from :file:`utm.tif` might look like this:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:49 +msgid "" +"Many aspects of the VRT file are a direct XML encoding of the " +":ref:`raster_data_model` which should be reviewed for understanding of " +"the semantics of various elements." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:53 +msgid "" +"VRT files can be produced by translating to VRT format. The resulting " +"file can then be edited to modify mappings, add metadata or other " +"purposes. VRT files can also be produced programmatically by various " +"means." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:57 +msgid "" +"This tutorial will cover the .vrt file format (suitable for users editing" +" .vrt files), and how .vrt files may be created and manipulated " +"programmatically for developers." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:77 +msgid "" +"Setting explicitly the block size is an advanced setting that should only" +" be used when the user has determined that it is needed. By default the " +"block size is set to:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:81 +msgid "" +"128x128 for a source-based VRT raster band. Unless the VRT is made of a " +"single source and this single source is not subsetted, in which case the " +"block size of the unique source will be set as the VRT raster band block " +"size)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:85 +msgid "512x128 for a warped VRT." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:88 +#: ../../source/drivers/raster/vrt_multidimensional.rst:37 +msgid ".vrt Format" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:90 +msgid "" +"A `XML schema of the GDAL VRT format " +"<https://raw.githubusercontent.com/OSGeo/gdal/master/frmts/vrt/data/gdalvrt.xsd>`_" +" is available." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:93 +msgid "" +"Note, .vrt files starting with - <OGRVRTDataSource> open with ogrinfo, " +"etc. - <VRTDataset> open with gdalinfo, etc." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:97 +#: ../../source/drivers/raster/vrt_multidimensional.rst:42 +msgid "" +"Virtual files stored on disk are kept in an XML format with the following" +" elements." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:100 +msgid "" +"**VRTDataset**: This is the root element for the whole GDAL dataset. It " +"must have the attributes rasterXSize and rasterYSize describing the width" +" and height of the dataset in pixels. It may have a subClass attributes " +"with values VRTWarpedDataset (:ref:`gdal_vrttut_warped`) or " +"VRTPansharpenedDataset (:ref:`gdal_vrttut_pansharpen`). It may have SRS, " +"GeoTransform, GCPList, Metadata, MaskBand and VRTRasterBand subelements." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:107 +msgid "VRTDataset" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:109 +msgid "The allowed subelements for VRTDataset are :" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:111 +msgid "" +"**SRS**: This element contains the spatial reference system (coordinate " +"system) in OGC WKT format. Note that this must be appropriately escaped " +"for XML, so items like quotes will have the ampersand escape sequences " +"substituted. As well as WKT, valid input to the " +":cpp:func:`OGRSpatialReference::SetFromUserInput` method (such as well " +"known GEOGCS names, and PROJ.4 format) is also allowed in the SRS " +"element." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:117 +msgid "" +"The **dataAxisToSRSAxisMapping** attribute is allowed since GDAL 3.0 to " +"describe the relationship between the axis indicated in the CRS " +"definition and the axis of the GeoTransform or GCP metadata. The value of" +" the attribute is a comma separated list of integers. The number of " +"elements of this list must be the number of axis of the CRS. Values start" +" at 1. If m denotes the array values of this attribute, then m[0] is the " +"data axis number for the first axis of the CRS. If the attribute is " +"missing, then the OAMS_TRADITIONAL_GIS_ORDER data axis to CRS axis " +"mapping strategy is implied." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:119 +msgid "" +"**GeoTransform**: This element contains a six value affine " +"geotransformation for the dataset, mapping between pixel/line coordinates" +" and georeferenced coordinates. Typically (geotransform[0], " +"geotransform[3]) will be the (easting, northing) of the upper-left corner" +" of the raster, geotransform[1] the horizontal resolution in geospatial " +"coordinates/pixel, and geotransform[5] the vertical resolution in " +"geospatial coordinates/pixel, as a negative value if the image is north-" +"up oriented. See :ref:`raster_data_model_geotransform` for more details " +"about that mapping." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:125 +msgid "" +"**GCPList**: This element contains a list of Ground Control Points for " +"the dataset, mapping between pixel/line coordinates and georeferenced " +"coordinates. The Projection attribute should contain the SRS of the " +"georeferenced coordinates in the same format as the SRS element. The " +"dataAxisToSRSAxisMapping attribute is the same as in the SRS element." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:134 +msgid "" +"**Metadata**: This element contains a list of metadata name/value pairs " +"associated with the VRTDataset as a whole, or a VRTRasterBand. It has " +"<MDI> (metadata item) subelements which have a \"key\" attribute and the " +"value as the data of the element. The Metadata element can be repeated " +"multiple times, in which case it must be accompanied with a \"domain\" " +"attribute to indicate the name of the metadata domain." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:142 +msgid "" +"**MaskBand**: This element represents a mask band that is shared between " +"all bands on the dataset (see GMF_PER_DATASET in RFC 15). It must contain" +" a single VRTRasterBand child element, that is the description of the " +"mask band itself." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:157 +msgid "" +"**OverviewList**: (GDAL >= 3.2.0, not valid for VRTPansharpenedDataset) " +"This elements contains a list of overview factors, separated by space, to" +" create \"virtual overviews\". For example ``2 4``. It can be used so " +"that bands of the VRT datasets declare overviews. This only makes sense " +"to use if the sources added in those bands have themselves overviews " +"compatible with the declared factor. It is generally not necessary to use" +" this mechanism, since downsampling pixel requests on a VRT dataset/band " +"are able to use overviews of the sources, even when the VRT bands do not " +"declare them. One situation where explicit overviews are needed at the " +"VRT level is the warping of a VRT to a lower resolution. This element can" +" also be used with an existing VRT dataset by running " +":cpp:func:`GDALDataset::BuildOverviews` or :program:`gdaladdo` with the " +":config:`VRT_VIRTUAL_OVERVIEWS` configuration option set to ``YES``:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:175 +msgid "" +"Virtual overviews have the least priority compared to the **Overview** " +"element at the **VRTRasterBand** level, or to materialized .vrt.ovr " +"files." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:179 +msgid "**VRTRasterBand**: This represents one band of a dataset." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:182 +msgid "VRTRasterBand" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:184 +msgid "The attributes for VRTRasterBand are:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:186 +msgid "" +"**dataType** (optional): type of the pixel data associated with this band" +" (use names Byte, UInt16, Int16, UInt32, Int32, Float32, Float64, CInt16," +" CInt32, CFloat32 or CFloat64). If not specified, defaults to 1" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:190 +msgid "**band** (optional): band number this element represents (1 based)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:192 +msgid "" +"**blockXSize** (optional, GDAL >= 3.3): block width. If not specified, " +"defaults to the minimum of the raster width and 128." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:195 +msgid "" +"**blockYSize** (optional, GDAL >= 3.3): block height. If not specified, " +"defaults to the minimum of the raster height and 128." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:198 +msgid "" +"This element may have Metadata, ColorInterp, NoDataValue, " +"HideNoDataValue, ColorTable, GDALRasterAttributeTable, Description and " +"MaskBand subelements as well as the various kinds of source elements such" +" as SimpleSource, ComplexSource, AveragedSource, NoDataFromMaskSource, " +"KernelFilteredSource and ArraySource. A raster band may have many " +"\"sources\" indicating where the actual raster data should be fetched " +"from, and how it should be mapped into the raster bands pixel space." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:200 +msgid "The allowed subelements for VRTRasterBand are :" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:202 +msgid "" +"**ColorInterp**: The data of this element should be the name of a color " +"interpretation type. One of Gray, Palette, Red, Green, Blue, Alpha, Hue," +" Saturation, Lightness, Cyan, Magenta, Yellow, Black, or Unknown." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:208 +msgid "" +"**NoDataValue**: If the input datasets to be composed have a nodata value" +" for this raster band, set this element's value to that nodata value for " +"it to be reflected in the VRT. This must not be confused with the NODATA " +"element of a VRTComplexSource element." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:214 +msgid "" +"**HideNoDataValue**: If this value is 1, the nodata value will not be " +"reported. Essentially, the caller will not be aware of a nodata pixel " +"when it reads one. Any datasets copied/translated from this will not " +"have a nodata value. This is useful when you want to specify a fixed " +"background value for the dataset. The background will be the value " +"specified by the NoDataValue element. Default value is 0 when this " +"element is absent." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:220 +msgid "" +"**ColorTable**: This element is parent to a set of Entry elements " +"defining the entries in a color table. Currently only RGBA color tables " +"are supported with c1 being red, c2 being green, c3 being blue and c4 " +"being alpha. The entries are ordered and will be assumed to start from " +"color table entry 0." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:229 +msgid "" +"**GDALRasterAttributeTable**: (GDAL >=2.3) This element is parent to a " +"set of FieldDefn elements defining the columns of a raster attribute " +"table, followed by a set of Row elements defining the values of the " +"columns of each row." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:268 +msgid "" +"**Description**: This element contains the optional description of a " +"raster band as its text value." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:274 +msgid "" +"**UnitType**: This optional element contains the vertical units for " +"elevation band data. One of \"m\" for meters or \"ft\" for feet. Default" +" assumption is meters." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:280 +msgid "" +"**Offset**: This optional element contains the offset that should be " +"applied when computing \"real\" pixel values from scaled pixel values on " +"a raster band. The default is 0.0." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:286 +msgid "" +"**Scale**: This optional element contains the scale that should be " +"applied when computing \"real\" pixel values from scaled pixel values on " +"a raster band. The default is 1.0." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:292 +msgid "" +"**Overview**: This optional element describes one overview level for the " +"band. It should have a child SourceFilename and SourceBand element. The" +" SourceFilename may have a relativeToVRT boolean attribute. Multiple " +"elements may be used to describe multiple overviews." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:301 +msgid "" +"**CategoryNames**: This optional element contains a list of Category " +"subelements with the names of the categories for classified raster band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:313 +msgid "" +"**SimpleSource**: The SimpleSource_ indicates that raster data should be " +"read from a separate dataset, indicating the dataset, and band to be read" +" from, and how the data should map into this band's raster space." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:315 +msgid "" +"**AveragedSource**: The AveragedSource is derived from the SimpleSource " +"and shares the same properties except that it uses an averaging " +"resampling instead of a nearest neighbour algorithm as in SimpleSource, " +"when the size of the destination rectangle is not the same as the size of" +" the source rectangle. Note: a more general mechanism to specify " +"resampling algorithms can be used. See above paragraph about the " +"'resampling' attribute." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:317 +msgid "" +"**NoDataFromMaskSource**: (GDAL >= 3.9) The NoDataFromMaskSource is " +"derived from the SimpleSource and shares the same properties except that " +"it replaces the value of the source with the value of the NODATA child " +"element when the value of the mask band of the source is less or equal to" +" the MaskValueThreshold child element. This is typically used to " +"transform a R,G,B,A image into a R,G,B one with a NoData value." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:319 +msgid "" +"**ComplexSource**: The ComplexSource_ is derived from the SimpleSource " +"(so it shares the SourceFilename, SourceBand, SrcRect and DstRect " +"elements), but it provides support to rescale and offset the range of the" +" source values. Certain regions of the source can be masked by specifying" +" the NODATA value, or starting with GDAL 3.3, with the " +"<UseMaskBand>true</UseMaskBand> element." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:321 +msgid "" +"**KernelFilteredSource**: The KernelFilteredSource_ is a pixel source " +"derived from the Simple Source (so it shares the SourceFilename, " +"SourceBand, SrcRect and DstRect elements, but it also passes the data " +"through a simple filtering kernel specified with the Kernel element." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:323 +msgid "" +"**ArraySource**: The ArraySource_ indicates that raster data should be " +"read from a 2D array using the multidimensional API." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:325 +msgid "" +"**MaskBand**: This element represents a mask band that is specific to the" +" VRTRasterBand it contains. It must contain a single VRTRasterBand child " +"element, that is the description of the mask band itself." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:328 +msgid "Sources" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:331 +msgid "SimpleSource" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:333 +msgid "" +"The SimpleSource may have the SourceFilename, SourceBand, SrcRect, and " +"DstRect subelements. The SrcRect element will indicate what rectangle on" +" the indicated source file should be read, and the DstRect element " +"indicates how that rectangle of source data should be mapped into the " +"VRTRasterBands space." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:338 +msgid "" +"SrcRect and DstRect are expressed in pixel/line coordinate space. Their " +"relationship with the geospatial coordinate space is given by the " +"geotransform matrix of the source for SrcRect, and of the VRT itself " +"(**GeoTransform** element) for DstRect. See " +":ref:`raster_data_model_geotransform` for more details about that " +"mapping." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:344 +msgid "" +"The relativeToVRT attribute on the SourceFilename indicates whether the " +"filename should be interpreted as relative to the .vrt file (value is 1) " +"or not relative to the .vrt file (value is 0). The default is 0." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:348 +msgid "" +"Some characteristics of the source band can be specified in the optional " +"``SourceProperties`` element to enable the VRT driver to defer the " +"opening of the source dataset until it really needs to read data from it." +" This is particularly useful when building VRTs with a big number of " +"source datasets. The needed parameters are the raster dimensions, the " +"size of the blocks and the data type. If the SourceProperties tag is not " +"present, the source dataset will be opened at the same time as the VRT " +"itself." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:357 +msgid "" +"Starting with GDAL 3.4, the ``SourceProperties`` element is no longer " +"necessary for deferred opening of the source datasets." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:360 +msgid "" +"The content of the SourceBand subelement can refer to a mask band. For " +"example mask,1 means the mask band of the first band of the source." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:373 +msgid "" +"A OpenOptions subelement can be added to specify the open options to " +"apply when opening the source dataset. It has <OOI> (open option item) " +"subelements which have a \"key\" attribute and the value as the data of " +"the element." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:390 +msgid "" +"A resampling attribute can be specified on a SimpleSource or " +"ComplexSource element to specified the resampling algorithm used when the" +" size of the destination rectangle is not the same as the size of the " +"source rectangle. The values allowed for that attribute are : " +"nearest,bilinear,cubic, cubicspline,lanczos,average,mode." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:407 +msgid "ComplexSource" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:409 +msgid "" +"Alternatively to linear scaling, non-linear scaling using a power " +"function can be used by specifying the Exponent, SrcMin, SrcMax, DstMin " +"and DstMax elements. If SrcMin and SrcMax are not specified, they are " +"computed from the source minimum and maximum value (which might require " +"analyzing the whole source dataset). Exponent must be positive. (Those 5 " +"values can be set with the -exponent and -scale options of " +"gdal_translate.)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:417 +msgid "" +"The ComplexSource supports adding a custom lookup table to transform the " +"source values to the destination. The LUT can be specified using the " +"following form:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:425 +msgid "" +"The intermediary values are calculated using a linear interpolation " +"between the bounding destination values of the corresponding range. " +"Source values should be listed in a monotonically non-decreasing order. " +"If there is a Not-A-Number (NaN) source value, it should be the first " +"one. Clamping is performed for input pixel values outside of the range " +"specified by the LUT. That is, if an input pixel value is lower than the " +"minimum source value, then the destination value corresponding to that " +"minimum source value is used as the output pixel value. And similarly for" +" an input pixel value that is greater than the maximum source value." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:434 +msgid "" +"The ComplexSource supports fetching a color component from a source " +"raster band that has a color table. The ColorTableComponent value is the " +"index of the color component to extract : 1 for the red band, 2 for the " +"green band, 3 for the blue band or 4 for the alpha band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:439 +msgid "" +"When transforming the source values the operations are executed in the " +"following order:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:442 +msgid "" +"Masking, if the NODATA element is set or, starting with GDAL 3.3, if the " +"UseMaskBand is set to true and the source band has a mask band. Note that" +" this is binary masking only, so no alpha blending is done if the mask " +"band is actually an alpha band with non-0 or non-255 values." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:446 +msgid "Color table expansion" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:447 +msgid "For linear scaling, applying the scale ratio, then scale offset" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:448 +msgid "" +"For non-linear scaling, apply (DstMax-DstMin) * pow( (SrcValue-SrcMin) / " +"(SrcMax-SrcMin), Exponent) + DstMin" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:449 +msgid "Table lookup" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:465 +msgid "Non-linear scaling:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:483 +msgid "KernelFilteredSource" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:485 +msgid "" +"The Kernel element should have two child elements, Size and Coefs and " +"optionally the boolean attribute normalized (defaults to false=0). The " +"size must always be an odd number, and the Coefs must have Size * Size " +"entries separated by spaces. For now kernel is not applied to sub-" +"sampled or over-sampled data." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:502 +msgid "" +"Starting with GDAL 2.3, a separable kernel may also be used. In this " +"case the number of Coefs entries should correspond to the Size. The " +"Coefs specify a one-dimensional kernel which is applied along each axis " +"in succession, resulting in far quicker execution. Many common image-" +"processing filters are separable. For example, a Gaussian blur:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:520 +msgid "NoDataFromMaskSource" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:524 +msgid "" +"The NoDataFromMaskSource is derived from the SimpleSource and shares the " +"same properties except that it replaces the value of the source with the " +"value of the NODATA child element when the value of the mask band of the " +"source is less or equal to the MaskValueThreshold child element. This is " +"typically used to transform a R,G,B,A image into a R,G,B one with a " +"NoData value. An optional RemappedValue element can be set to specify the" +" value onto which valid pixels whose value is the one of NODATA should be" +" remapped to. When RemappedValue is not explicitly specified, for Byte " +"bands, if NODATA=255, it is implicitly set to 254, otherwise it is set to" +" NODATA+1." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:540 +msgid "ArraySource" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:544 +msgid "" +"The ArraySource_ indicates that raster data should be read from a 2D " +"array using the multidimensional API. If the original array is not a 3D " +"array, a DerivedArray with a View step must be typically used to create a" +" 2D slice." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:548 +msgid "ArraySource can have the following child elements:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:550 +msgid "" +"``SingleSourceArray``, ``DerivedArray`` or ``Array``: required as first " +"child element" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:551 +msgid "``SrcRect`` (same syntax and semantics as in SimpleSource): optional" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:552 +msgid "``DstRect`` (same syntax and semantics as in SimpleSource): optional" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:555 +msgid "SingleSourceArray" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:557 +msgid "" +"SingleSourceArray references a multidimensional raster through a " +"SourceFilename element and an array through its full path within it with " +"SourceArray. When SingleSourceArray is used as a direct child of " +"ArraySource, it must be a 2-dimensional array." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:573 +msgid "" +"Be careful that quite often arrays in the multidimensional API use a " +"\"bottom-up\" approach, and it might thus be needed to reverse the Y " +"axis, with a View expression with a DerivedArray (cf below example)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:578 +msgid "DerivedArray" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:580 +msgid "" +"A DerivedArray starts with an array coming from a SingleSourceArray (but " +"it could also be a DerivedArray or a Array), which must be the first " +"child element, and applies different processing steps wrapped in zero or " +"more Step elements." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:585 +msgid "View step: applies the :cpp:func:`GDALMDArray::GetView` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:587 +msgid "" +"The ``View`` element must have an ``expr`` attribute, which is the " +"argument of :cpp:func:`GDALMDArray::GetView` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:590 +msgid "" +"The following example slices the 3D dimension at index 0 and flips the " +"vertical axis (assuming 1st dimension is a non-spatial one, 2nd dimension" +" is the Y dimension and 3rd dimension is the X dimension)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:608 +msgid "``Transpose`` step: applies the :cpp:func:`GDALMDArray::Transpose` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:610 +msgid "" +"The ``Transpose`` element must have a ``newOrder`` attribute, which is " +"the argument of :cpp:func:`GDALMDArray::Transpose` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:613 +msgid "The following example transposes the 2 axis of a 2D array" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:629 +msgid "Resample step: applies the :cpp:func:`GDALMDArray::GetResampled` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:631 +msgid "" +"The ``Resample`` element may have the following child elements, which " +"correspond to the arguments of the :cpp:func:`GDALMDArray::GetResampled` " +"method:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:634 +msgid "" +"``Dimension``: with a ``name`` and ``size`` attribute. This element may " +"be repeated." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:635 +msgid "" +"``ResampleAlg``: whose value is ``NearestNeighbour`` (default), " +"``Cubic``, ``CubicSpline``, ``Bilinear``, ``Lanczos``, ``Average``, " +"``RMS`` or ``Mode``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:636 +msgid "" +"``SRS``: target SRS (string recognized by " +":cpp:func:`OGRSpatialReference::SetFromUserInput`)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:637 +#: ../../source/drivers/raster/vrt.rst:667 +#: ../../source/drivers/raster/vrt.rst:721 +msgid "" +"``Option`` with a ``name`` attribute and the value as the content of the " +"element. This element may be repeated." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:659 +msgid "Grid step: applies the :cpp:func:`GDALMDArray::GetGridded` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:661 +msgid "" +"The ``Grid`` element may have the following child elements, which " +"correspond to the arguments of the :cpp:func:`GDALMDArray::GetGridded` " +"method:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:664 +msgid "``GridOptions`` (required): name and options of the gridding algorithm" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:665 +msgid "" +"``XArray`` (optional): its child value should be a SingleSourceArray, " +"DerivedArray or Array pointing to the array to use for the X dimension. " +"This is needed if the source array does not have a ``coordinates`` " +"attribute." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:666 +msgid "" +"``YArray`` (optional): its child value should be a SingleSourceArray, " +"DerivedArray or Array pointing to the array to use for the Y dimension. " +"This is needed if the source array does not have a ``coordinates`` " +"attribute." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:698 +msgid "" +"``GetUnscaled`` step: applies the :cpp:func:`GDALMDArray::GetUnscaled` " +"method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:700 +msgid "It does not have any child elements." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:716 +msgid "``GetMask`` step: applies the :cpp:func:`GDALMDArray::GetMask` method" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:718 +msgid "" +"The ``GetMask`` element may have the following child elements, which " +"correspond to the arguments of the :cpp:func:`GDALMDArray::GetMask` " +"method:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:740 +msgid "Array" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:742 +msgid "" +":ref:`Array <vrt_multidimensional>` can be used to mosaic several " +"multidimensional arrays." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:748 +msgid "" +"GDAL can make efficient use of overviews available in the sources that " +"compose the bands when dealing with RasterIO() requests that involve " +"downsampling. But in the general case, the VRT bands themselves will not " +"expose overviews." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:752 +msgid "Except if (from top priority to lesser priority) :" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:754 +msgid "" +"The **Overview** element is present in the VRTRasterBand element. See " +"above." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:755 +msgid "or external .vrt.ovr overviews are built" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:756 +msgid "" +"(starting with GDAL 3.2) explicit virtual overviews, if a " +"**OverviewList** element is declared in the VRTDataset element (see " +"above). Those virtual overviews will be hidden by external .vrt.ovr " +"overviews that might be built later." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:759 +msgid "" +"(starting with GDAL 2.1) implicit virtual overviews, if the VRTRasterBand" +" are made of a single SimpleSource or ComplexSource that has overviews. " +"Those virtual overviews will be hidden by external .vrt.ovr overviews " +"that might be built later." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:764 +msgid ".vrt Descriptions for Raw Files" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:766 +msgid "" +"So far we have described how to derive new virtual datasets from existing" +" files supported by GDAL. However, it is also common to need to utilize " +"raw binary raster files for which the regular layout of the data is known" +" but for which no format specific driver exists. This can be " +"accomplished by writing a .vrt file describing the raw file." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:772 +msgid "" +"For example, the following .vrt describes a raw raster file containing " +"floating point complex pixels in a file called *l2p3hhsso.img*. The " +"image data starts from the first byte (ImageOffset=0). The byte offset " +"between pixels is 8 (PixelOffset=8), the size of a CFloat32. The byte " +"offset from the start of one line to the start of the next is 9376 bytes " +"(LineOffset=9376) which is the width (1172) times the size of a pixel " +"(8)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:791 +msgid "" +"Some things to note are that the VRTRasterBand has a subClass specifier " +"of \"VRTRawRasterBand\". Also, the VRTRawRasterBand contains a number of" +" previously unseen elements but no \"source\" information. " +"VRTRawRasterBands may never have sources (i.e. SimpleSource), but should " +"contain the following elements in addition to all the normal \"metadata\"" +" elements previously described which are still supported." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:798 +msgid "" +"**SourceFilename**: The name of the raw file containing the data for this" +" band. The relativeToVRT attribute can be used to indicate if the " +"SourceFilename is relative to the .vrt file (1) or not (0)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:800 +msgid "" +"**ImageOffset**: The offset in bytes to the beginning of the first pixel " +"of data of this image band. Defaults to zero." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:802 +msgid "" +"**PixelOffset**: The offset in bytes from the beginning of one pixel and " +"the next on the same line. In packed single band data this will be the " +"size of the **dataType** in bytes." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:804 +msgid "" +"**LineOffset**: The offset in bytes from the beginning of one scanline of" +" data and the next scanline of data. In packed single band data this " +"will be PixelOffset * rasterXSize." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:806 +msgid "" +"**ByteOrder**: Defines the byte order of the data on disk. Either LSB " +"(Least Significant Byte first) such as the natural byte order on Intel " +"x86 systems or MSB (Most Significant Byte first) such as the natural byte" +" order on Motorola or Sparc systems. Defaults to being the local machine" +" order." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:808 +msgid "A few other notes:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:810 +msgid "" +"The image data on disk is assumed to be of the same data type as the band" +" **dataType** of the VRTRawRasterBand." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:812 +msgid "" +"All the non-source attributes of the VRTRasterBand are supported, " +"including color tables, metadata, nodata values, and color " +"interpretation." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:814 +msgid "" +"The VRTRawRasterBand supports in place update of the raster, whereas the " +"source based VRTRasterBand is always read-only." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:816 +msgid "" +"The OpenEV tool includes a File menu option to input parameters " +"describing a raw raster file in a GUI and create the corresponding .vrt " +"file." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:818 +msgid "" +"Multiple bands in the one .vrt file can come from the same raw file. Just" +" ensure that the ImageOffset, PixelOffset, and LineOffset definition for " +"each band is appropriate for the pixels of that particular band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:820 +msgid "Another example, in this case a 400x300 RGB pixel interleaved image." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:849 +msgid "Creation of VRT Datasets" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:851 +msgid "" +"The VRT driver supports several methods of creating VRT datasets. The " +":file:`vrtdataset.h` include file should be installed with the core GDAL " +"include files, allowing direct access to the VRT classes. However, even " +"without that most capabilities remain available through standard GDAL " +"interfaces." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:857 +msgid "" +"To create a VRT dataset that is a clone of an existing dataset use the " +":cpp:func:`GDALDriver::CreateCopy` method. For example to clone " +":file:`utm.tif` into a :file:`wrk.vrt` file in C++ the following could be" +" used:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:873 +msgid "" +"Note the use of :cpp:func:`GDALOpenShared` when opening the source " +"dataset. It is advised to use :cpp:func:`GDALOpenShared` in this " +"situation so that you are able to release the explicit reference to it " +"before closing the VRT dataset itself. In other words, in the previous " +"example, you could also invert the 2 last lines, whereas if you open the " +"source dataset with :cpp:func:`GDALOpen`, you'd need to close the VRT " +"dataset before closing the source dataset." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:880 +msgid "" +"To obtain the resulting VRT XML of :file:`wrk.vrt` without having to read" +" the text from an actual file, you can modify the above code to open the " +"new dataset with an empty filename and use the \"xml:VRT\" metadata " +"domain." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:892 +msgid "" +"To create a virtual copy of a dataset with some attributes added or " +"changed such as metadata or coordinate system that are often hard to " +"change on other formats, you might do the following. In this case, the " +"virtual dataset is created \"in memory\" only by virtual of creating it " +"with an empty filename, and then used as a modified source to pass to a " +":cpp:func:`GDALDriver::CreateCopy` written out in TIFF format." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:915 +msgid "" +"In the above example the nodata value is set as -999. You can set the " +"HideNoDataValue element in the VRT dataset's band using " +":cpp:func:`GDALRasterBand::SetMetadataItem` on that band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:923 +msgid "" +"In this example a virtual dataset is created with the " +":cpp:func:`GDALDriver::Create` method, and adding bands and sources " +"programmatically, but still via the \"generic\" API. A special attribute " +"of VRT datasets is that sources can be added to the VRTRasterBand (but " +"not to VRTRawRasterBand) by passing the XML describing the source into " +":cpp:func:`GDALRasterBand::SetMetadataItem` on the special domain target " +"\"new_vrt_sources\". The domain target \"vrt_sources\" may also be used," +" in which case any existing sources will be discarded before adding the " +"new ones. In this example we construct a simple averaging filter source " +"instead of using the simple source." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:949 +msgid "" +"A more general form of this that will produce a 3x3 average filtered " +"clone of any input datasource might look like the following. In this " +"case we deliberately set the filtered datasource as in the " +"\"vrt_sources\" domain to override the SimpleSource created by the " +"`cpp:func:`GDALDriver::CreateCopy` method. The fact that we used " +"`cpp:func:GDALDriver::CreateCopy` ensures that all the other metadata, " +"georeferencing and so forth is preserved from the source dataset ... the " +"only thing we are changing is the data source for each band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:986 +msgid "" +"The :cpp:class:`VRTDataset` class is one of the few dataset " +"implementations that supports the :cpp:func:`GDALDataset::AddBand` " +"method. The options passed to the :cpp:func:`GDALDataset::AddBand` method" +" can be used to control the type of the band created (VRTRasterBand, " +"VRTRawRasterBand, VRTDerivedRasterBand), and in the case of the " +"VRTRawRasterBand to set its various parameters. For standard " +"VRTRasterBand, sources should be specified with the above " +":cpp:func:`GDALRasterBand::SetMetadataItem` examples." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1014 +msgid "Using Derived Bands (with pixel functions in C/C++)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1016 +msgid "" +"A specialized type of band is a 'derived' band which derives its pixel " +"information from its source bands. With this type of band you must also " +"specify a pixel function, which has the responsibility of generating the " +"output raster. Pixel functions are created by an application and then " +"registered with GDAL using a unique key." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1022 +msgid "" +"Using derived bands you can create VRT datasets that manipulate bands on " +"the fly without having to create new band files on disk. For example, " +"you might want to generate a band using four source bands from a nine " +"band input dataset (x0, x3, x4, and x8) and some constant y:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1031 +msgid "" +"You could write the pixel function to compute this value and then " +"register it with GDAL with the name \"MyFirstFunction\". Then, the " +"following VRT XML could be used to display this derived band:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1072 +msgid "" +"PixelFunctionArguments can only be used with C++ pixel functions in GDAL " +"versions 3.4 and greater." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1075 +msgid "" +"In addition to the subclass specification (VRTDerivedRasterBand) and the " +"PixelFunctionType value, there is another new parameter that can come in " +"handy: SourceTransferType. Typically the source rasters are obtained " +"using the data type of the derived band. There might be times, however, " +"when you want the pixel function to have access to higher resolution " +"source data than the data type being generated. For example, you might " +"have a derived band of type \"Float\", which takes a single source of " +"type \"CFloat32\" or \"CFloat64\", and returns the imaginary portion. To" +" accomplish this, set the SourceTransferType to \"CFloat64\". Otherwise " +"the source would be converted to \"Float\" prior to calling the pixel " +"function, and the imaginary portion would be lost." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1097 +msgid "Default Pixel Functions" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1099 +msgid "" +"GDAL provides a set of default pixel functions that can be used without " +"writing new code:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1106 +msgid "PixelFunctionType" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1107 +msgid "Number of input sources" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1108 +msgid "PixelFunctionArguments" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1110 +msgid "**cmul**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1113 +msgid "multiply the first band for the complex conjugate of the second" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1114 +msgid "**complex**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1117 +msgid "make a complex band merging two bands used as real and imag values" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1118 +msgid "**conj**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1121 +msgid "" +"computes the complex conjugate of a single raster band (just a copy if " +"the input is non-complex)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1122 +msgid "**dB**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1124 +msgid "``fact`` (optional)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1125 +msgid "" +"perform conversion to dB of the abs of a single raster band (real or " +"complex): ``20. * log10( abs( x ) )``. The optional ``fact`` parameter " +"can be set to ``10`` to get the alternative formula: ``10. * log10( abs( " +"x ) )``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1126 +msgid "**dB2amp**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1129 +msgid "" +"perform scale conversion from logarithmic to linear (amplitude) (i.e. " +"``10 ^ ( x / 20 )`` ) of a single raster band (real only). Deprecated in " +"GDAL v3.5. Please use the ``exp`` pixel function with ``base = 10.`` and " +"``fact = 0.05`` i.e. ``1./20``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1130 +msgid "**dB2pow**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1133 +msgid "" +"perform scale conversion from logarithmic to linear (power) (i.e. ``10 ^ " +"( x / 10 )`` ) of a single raster band (real only). Deprecated in GDAL " +"v3.5. Please use the ``exp`` pixel function with ``base = 10.`` and " +"``fact = 0.1`` i.e. ``1./10``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1134 +msgid "**diff**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1137 +msgid "computes the difference between 2 raster bands (``b1 - b2``)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1138 +msgid "**div**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1141 +msgid "divide one raster band by another (``b1 / b2``)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1142 +msgid "**norm_diff**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1145 +msgid "" +"computes the normalized difference between two raster bands: ``(b1 - " +"b2)/(b1 + b2)``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1146 +msgid "**exp**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1148 +msgid "``base`` (optional), ``fact`` (optional)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1149 +msgid "" +"computes the exponential of each element in the input band ``x`` (of real" +" values): ``e ^ x``. The function also accepts two optional parameters: " +"``base`` and ``fact`` that allow to compute the generalized formula: " +"``base ^ ( fact * x )``. Note: this function is the recommended one to " +"perform conversion form logarithmic scale (dB): `` 10. ^ (x / 20.)``, in " +"this case ``base = 10.`` and ``fact = 0.05`` i.e. ``1. / 20``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1150 +msgid "**imag**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1153 +msgid "extract imaginary part from a single raster band (0 for non-complex)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1154 +msgid "**intensity**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1157 +msgid "" +"computes the intensity ``Re( x * conj(x) )`` of a single raster band " +"(real or complex)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1158 +msgid "**interpolate_exp**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1159 +#: ../../source/drivers/raster/vrt.rst:1163 +#: ../../source/drivers/raster/vrt.rst:1175 +#: ../../source/drivers/raster/vrt.rst:1179 +#: ../../source/drivers/raster/vrt.rst:1187 +#: ../../source/drivers/raster/vrt.rst:1211 +msgid ">= 2" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1160 +#: ../../source/drivers/raster/vrt.rst:1164 +msgid "``t0``, ``dt``, ``t``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1161 +msgid "" +"interpolate a value at time (or position) ``t`` given input sources " +"beginning at position ``t0`` with spacing ``dt`` using exponential " +"interpolation" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1162 +msgid "**interpolate_linear**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1165 +msgid "" +"interpolate a value at time (or position) ``t`` given input sources " +"beginning at ``t0`` with spacing ``dt`` using linear interpolation" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1166 +msgid "**inv**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1168 +#: ../../source/drivers/raster/vrt.rst:1188 +#: ../../source/drivers/raster/vrt.rst:1212 +msgid "``k`` (optional)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1169 +msgid "" +"inverse (``1./x``). If the optional ``k`` parameter is set then the " +"result is multiplied by ``k`` (``k / x``)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1170 +msgid "**log10**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1173 +msgid "" +"compute the logarithm (base 10) of the abs of a single raster band (real " +"or complex): ``log10( abs( x ) )``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1174 +msgid "**max**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1176 +#: ../../source/drivers/raster/vrt.rst:1180 +msgid "``propagateNoData`` (optional)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1177 +msgid "" +"(GDAL >= 3.8) maximum of 2 or more raster bands, ignoring by default " +"pixels at nodata. If the optional ``propagateNoData`` parameter is set to" +" ``true``, then if a nodata pixel is found in one of the bands, if will " +"be propagated to the output value." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1178 +msgid "**min**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1181 +msgid "" +"(GDAL >= 3.8) minimum of 2 or more raster bands, ignoring by default " +"pixels at nodata. If the optional ``propagateNoData`` parameter is set to" +" ``true``, then if a nodata pixel is found in one of the bands, if will " +"be propagated to the output value." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1182 +msgid "**mod**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1185 +msgid "extract module from a single raster band (real or complex)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1186 +msgid "**mul**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1189 +msgid "" +"multiply 2 or more raster bands. If the optional ``k`` parameter is " +"provided then the result is multiplied by the scalar ``k``." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1190 +msgid "**phase**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1193 +msgid "extract phase from a single raster band [-PI,PI] (0 or PI for non-complex)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1194 +msgid "**polar**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1196 +msgid "``amplitude_type`` (optional)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1197 +msgid "" +"make a complex band using input bands for amplitude and phase values ``b1" +" * exp( j * b2 )``. The optional (string) parameter ``amplitude_type`` " +"can be ``AMPLITUDE`` (default) ``INTENSITY`` or ``dB``. Note: if " +"``amplitude_type`` is set to ``INTENSITY`` then negative values are " +"clipped to zero." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1198 +msgid "**pow**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1200 +msgid "``power``" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1201 +msgid "" +"raise a single raster band to a constant power, specified with argument " +"``power`` (real only)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1202 +msgid "**real**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1205 +msgid "" +"extract real part from a single raster band (just a copy if the input is " +"non-complex)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1206 +msgid "**sqrt**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1209 +msgid "perform the square root of a single raster band (real only)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1210 +msgid "**sum**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1213 +msgid "" +"sum 2 or more raster bands. If the optional ``k`` parameter is provided " +"then it is added to each element of the result" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1214 +msgid "**replace_nodata**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1215 +#: ../../source/drivers/raster/vrt.rst:1219 +msgid "= 1" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1216 +msgid "``to`` (optional)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1217 +msgid "" +"convert incoming ``NoData`` values to a new value, IEEE 754 `nan` by " +"default" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1218 +msgid "**scale**" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1221 +msgid "" +"perform scaling according to the ``offset`` and ``scale`` values of the " +"raster band" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1224 +msgid "Writing Pixel Functions" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1226 +msgid "" +"To register this function with GDAL (prior to accessing any VRT datasets " +"with derived bands that use this function), an application calls " +":cpp:func:`GDALAddDerivedBandPixelFuncWithArgs` with a key and a " +":cpp:type:`GDALDerivedPixelFuncWithArgs`:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1242 +msgid "" +"A good time to do this is at the beginning of an application when the " +"GDAL drivers are registered. ``pszMetadata`` is optional and can be " +"``nullptr``. It can be used to declare the function signature to the user" +" and to request additional parameters aside from the ones from the " +"Dataset." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1247 +msgid "" +"A :cpp:type:`GDALDerivedPixelFuncWithArgs` is defined with a signature " +"similar to :cpp:func:`GDALRasterBand::IRasterIO`:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst +msgid "Parameters" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1252 +msgid "" +"A pointer to packed rasters; one per source. The datatype of all will be" +" the same, specified in the ``eSrcType`` parameter." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1255 +msgid "The number of source rasters." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1257 +msgid "" +"The buffer into which the data should be read, or from which it should be" +" written. This buffer must contain at least ``nBufXSize * nBufYSize`` " +"words of type eBufType. It is organized in left to right, top to bottom " +"pixel order. Spacing is controlled by the ``nPixelSpace`` and " +"``nLineSpace`` parameters." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1263 +msgid "" +"The width of the buffer image into which the desired region is to be " +"read, or from which it is to be written." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1266 +msgid "" +"The height of the buffer image into which the desired region is to be " +"read, or from which it is to be written." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1269 +msgid "The type of the pixel values in the ``papoSources`` raster array." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1272 +msgid "" +"The type of the pixel values that the pixel function must generate in the" +" ``pData`` data buffer." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1275 +msgid "" +"The byte offset from the start of one pixel value in ``pData`` to the " +"start of the next pixel value within a scanline. If defaulted (0) the " +"size of the datatype eBufType is used." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1279 +msgid "" +"The byte offset from the start of one scanline in pData to the start of " +"the next." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1282 +msgid "An optional string list of named function arguments (e.g. ``y=4``)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1285 +msgid "" +"It is also possible to register a :cpp:type:`GDALDerivedPixelFunc` (which" +" omits the final :cpp:type:`CSLConstList` argument) using " +":cpp:func:`GDALAddDerivedBandPixelFunc`." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1287 +msgid "The following is an implementation of the pixel function:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1349 +msgid "Using Derived Bands (with pixel functions in Python)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1351 +msgid "" +"Starting with GDAL 2.2, in addition to pixel functions written in C/C++ " +"as documented in the :ref:`vrt_derived_bands` section, it is possible to " +"use pixel functions written in Python. Both `CPython " +"<https://www.python.org/>`_ and `NumPy <http://www.numpy.org/>`_ are " +"requirements at run-time." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1356 +msgid "" +"The subelements for VRTRasterBand (whose subclass specification must be " +"set to VRTDerivedRasterBand) are :" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1359 +msgid "" +"**PixelFunctionType** (required): Must be set to a function name that " +"will be defined as a inline Python module in PixelFunctionCode element or" +" as the form \"module_name.function_name\" to refer to a function in an " +"external Python module" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1361 +msgid "**PixelFunctionLanguage** (required): Must be set to Python." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1363 +msgid "" +"**PixelFunctionCode** (required if PixelFunctionType is of the form " +"\"function_name\", ignored otherwise). The in-lined code of a Python " +"module, that must be at least have a function whose name is given by " +"PixelFunctionType." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1365 +msgid "" +"**BufferRadius** (optional, defaults to 0): Amount of extra pixels, with " +"respect to the original RasterIO() request to satisfy, that are fetched " +"at the left, right, bottom and top of the input and output buffers passed" +" to the pixel function. Note that the values of the output buffer in this" +" buffer zone willbe ignored." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1367 +msgid "" +"**SkipNonContributingSources** (optional, added in GDAL 3.7, defaults to " +"false) = true/false: Whether sources that do not intersect the " +"VRTRasterBand RasterIO() requested region should be omitted. By default, " +"data for all sources, including ones that do not intersect it, are passed" +" to the pixel function. By setting this parameter to false, only sources " +"that intersect the requested region will be passed." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1369 +msgid "" +"The signature of the Python pixel function must have the following " +"arguments:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1371 +msgid "" +"**in_ar**: list of input NumPy arrays. One NumPy array for each source. " +"If SkipNonContributingSources=true, only contributing sources will be " +"passed." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1372 +msgid "" +"**out_ar**: output NumPy array to fill. The array is initialized at the " +"right dimensions and with the VRTRasterBand.dataType." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1373 +msgid "" +"**xoff**: pixel offset to the top left corner of the accessed region of " +"the band. Generally not needed except if the processing depends on the " +"pixel position in the raster." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1374 +msgid "" +"**yoff** line offset to the top left corner of the accessed region of the" +" band. Generally not needed." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1375 +msgid "" +"**xsize**: width of the region of the accessed region of the band. Can be" +" used together with out_ar.shape[1] to determine the horizontal " +"resampling ratio of the request." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1376 +msgid "" +"**ysize**: height of the region of the accessed region of the band. Can " +"be used together with out_ar.shape[0] to determine the vertical " +"resampling ratio of the request." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1377 +msgid "**raster_xsize**: total width of the raster band. Generally not needed." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1378 +msgid "**raster_ysize**: total height of the raster band. Generally not needed." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1379 +msgid "" +"**buf_radius**: radius of the buffer (in pixels) added to the left, " +"right, top and bottom of in_ar / out_ar. This is the value of the " +"optional BufferRadius element that can be set so that the original pixel " +"request is extended by a given amount of pixels." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1380 +msgid "**gt**: geotransform. Array of 6 double values." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1381 +msgid "" +"**kwargs**: dictionary with user arguments defined in " +"PixelFunctionArguments" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1383 +msgid "" +"The provided ``out_ar`` array must be modified in-place. Any value " +"currently returned by the pixel function is ignored." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1388 +msgid "" +"If wanting to fill ``out_ar`` from another array, use the ``out_ar[:] = " +"...`` syntax." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1395 +msgid "VRT that multiplies the values of the source file by a factor of 1.5" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1421 +msgid "VRT that adds 2 (or more) rasters" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1449 +msgid "VRT that computes hillshading using an external library" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1470 +msgid "with hillshading.py:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1529 +msgid "Python module path" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1531 +msgid "" +"When importing modules from inline Python code or when relying on out-of-" +"line code (PixelFunctionType of the form \"module_name.function_name\"), " +"you need to make sure the modules are accessible through the python path." +" Note that contrary to the Python interactive interpreter, the current " +"path is not automatically added when used from GDAL. So you may need to " +"define the **PYTHONPATH** environment variable if you get " +"ModuleNotFoundError exceptions." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1539 +msgid "Security implications" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1541 +msgid "" +"The ability to run Python code potentially opens the door to many " +"potential vulnerabilities if the user of GDAL may process untrusted " +"datasets. To avoid such issues, by default, execution of Python pixel " +"function will be disabled. The execution policy can be controlled with " +"the following configuration options:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1553 +msgid "" +"YES: all VRT scripts are considered as trusted and their Python pixel " +"functions will be run when pixel operations are involved." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1554 +msgid "" +"NO: all VRT scripts are considered untrusted, and none Python " +"pixelfunction will be run." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1555 +msgid "" +"TRUSTED_MODULES (default setting): all VRT scripts with inline Python " +"code in their PixelFunctionCode elements will be considered untrusted and" +" will not be run. VRT scripts that use a PixelFunctionType of the form " +"\"module_name.function_name\" will be considered as trusted, only if " +"\"module_name\" is allowed in the " +":config:`GDAL_VRT_PYTHON_TRUSTED_MODULES` configuration option." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1564 +msgid "Linking mechanism to a Python interpreter" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1566 +msgid "" +"Currently only CPython 2 and 3 is supported. The GDAL shared object is " +"not explicitly linked at build time to any of the CPython library. When " +"GDAL will need to run Python code, it will first determine if the Python " +"interpreter is loaded in the current process (which is the case if the " +"program is a Python interpreter itself, or if another program, e.g. QGIS," +" has already loaded the CPython library). Otherwise it will look if the " +":config:`PYTHONSO` configuration option is defined. This option can be " +"set to point to the name of the Python library to use, either as a " +"shortname like \"libpython3.10.so\" if it is accessible through the Linux" +" dynamic loader (so typically in one of the paths in /etc/ld.so.conf or " +"LD_LIBRARY_PATH) or as a full path name like \"/usr/lib/x86_64-linux-" +"gnu/libpython3.10.so\". The same holds on Windows will shortnames like " +"\"python310.dll\" if accessible through the PATH or full path names like " +"\"c:\\\\python310\\\\python310.dll\". If the :config:`PYTHONSO` " +"configuration option is not defined, it will look for a \"python\" binary" +" in the directories of the PATH and will try to determine the related " +"shared object (it will retry with \"python3\" if no \"python\" has been " +"found). If the above was not successful, then a predefined list of shared" +" objects names will be tried. At the time of writing, the order of " +"versions searched is 3.8, 3.9, 3.10, 3.11, 3.12, 3.7, 3.6, 3.5, 3.4, 3.3," +" 3.2. Enabling debug information (:config:`CPL_DEBUG=ON`) will show which" +" Python version is used." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1587 +msgid "Just-in-time compilation" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1589 +msgid "" +"The use of a just-in-time compiler may significantly speed up execution " +"times. `Numba <http://numba.pydata.org/>`_ has been successfully tested. " +"For better performance, it is recommended to use a offline pixel function" +" so that the just-in-time compiler may cache its compilation." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1594 +msgid "Given the following :file:`mandelbrot.py` file :" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1646 +msgid "The following VRT file can be used (to be opened with QGIS for example)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1683 +msgid "Warped VRT" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1685 +msgid "" +"A warped VRT is a VRTDataset with subClass=\"VRTWarpedDataset\". It has a" +" GDALWarpOptions element which describe the warping options." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1729 +msgid "Pansharpened VRT" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1733 +msgid "" +"A VRT can describe a dataset resulting from a `pansharpening operation " +"<https://en.wikipedia.org/wiki/Pansharpened_image>`_ The pansharpening " +"VRT combines a panchromatic band with several spectral bands of lower " +"resolution to generate output spectral bands of the same resolution as " +"the panchromatic band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1739 +msgid "" +"VRT pansharpening assumes that the panchromatic and spectral bands have " +"the same projection (or no projection). If that is not the case, " +"reprojection must be done in a prior step. Bands might have different " +"geotransform matrices, in which case, by default, the resulting dataset " +"will have as extent the union of all extents." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1744 +msgid "" +"Currently the only supported pansharpening algorithm is a \"weighted\" " +"Brovey algorithm. The general principle of this algorithm is that, after " +"resampling the spectral bands to the resolution of the panchromatic band," +" a pseudo panchromatic intensity is computed from a weighted average of " +"the spectral bands. Then the output value of the spectral band is its " +"input value multiplied by the ratio of the real panchromatic intensity " +"over the pseudo panchromatic intensity." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1751 +msgid "Corresponding pseudo code:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1760 +msgid "" +"A valid pansharpened VRT must declare subClass=\"VRTPansharpenedDataset\"" +" as an attribute of the VRTDataset top element. The VRTDataset element " +"must have a child **PansharpeningOptions** element. This " +"PansharpeningOptions element must have a **PanchroBand** child element " +"and one of several **SpectralBand** elements. PanchroBand and " +"SpectralBand elements must have at least a **SourceFilename** child " +"element to specify the name of the dataset. They may also have a " +"**SourceBand** child element to specify the number of the band in the " +"dataset (starting with 1). If not specify, the first band will be " +"assumed. **OpenOptions** can also be specified" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1770 +msgid "" +"The SpectralBand element must generally have a **dstBand** attribute to " +"specify the number of the output band (starting with 1) to which the " +"input spectral band must be mapped. If the attribute is not specified, " +"the spectral band will be taken into account in the computation of the " +"pansharpening, but not exposed as an output band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1775 +msgid "" +"Panchromatic and spectral bands should generally come from different " +"datasets, since bands of a GDAL dataset are assumed to have all the same " +"dimensions. Spectral bands themselves can come from one or several " +"datasets. The only constraint is that they have all the same dimensions " +"and geotransform." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1780 +msgid "" +"An example of a minimalist working VRT is the following. It will " +"generates a dataset with 3 output bands corresponding to the 3 input " +"spectral bands of multispectral.tif, pansharpened with panchromatic.tif." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1819 +msgid "" +"In the above example, 3 output pansharpend bands will be created from the" +" 3 declared input spectral bands. The weights will be 1/3. Cubic " +"resampling will be used. The projection and geotransform from the " +"panchromatic band will be reused for the VRT dataset." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1824 +msgid "" +"It is possible to create more explicit and declarative pansharpened VRT, " +"allowing for example to only output part of the input spectral bands " +"(e.g. only RGB when the input multispectral dataset is RGBNir). It is " +"also possible to add \"classic\" VRTRasterBands, in addition to the " +"pansharpened bands." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1829 +msgid "" +"In addition to the above mentioned required PanchroBand and SpectralBand " +"elements, the PansharpeningOptions element may have the following " +"children elements :" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1832 +msgid "" +"**Algorithm**: to specify the pansharpening algorithm. Currently, only " +"WeightedBrovey is supported." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1833 +msgid "" +"**AlgorithmOptions**: to specify the options of the pansharpening " +"algorithm. With WeightedBrovey algorithm, the only supported option is a " +"**Weights** child element whose content must be a comma separated list of" +" real values assigning the weight of each of the declared input spectral " +"bands. There must be as many values as declared input spectral bands." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1834 +msgid "" +"**Resampling**: the resampling kernel used to resample the spectral bands" +" to the resolution of the panchromatic band. Can be one of Cubic " +"(default), Average, Near, CubicSpline, Bilinear, Lanczos." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1835 +msgid "" +"**NumThreads**: Number of worker threads. Integer number or ALL_CPUS. If " +"this option is not set, the :config:`GDAL_NUM_THREADS` configuration " +"option will be queried (its value can also be set to an integer or " +"ALL_CPUS)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1836 +msgid "" +"**BitDepth**: Can be used to specify the bit depth of the panchromatic " +"and spectral bands (e.g. 12). If not specified, the NBITS metadata item " +"from the panchromatic band will be used if it exists." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1837 +msgid "" +"**NoData**: Nodata value to take into account for panchromatic and " +"spectral bands. It will be also used as the output nodata value. If not " +"specified and all input bands have the same nodata value, it will be " +"implicitly used (unless the special None value is put in NoData to " +"prevent that)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1838 +msgid "" +"**SpatialExtentAdjustment**: Can be one of **Union** (default), " +"**Intersection**, **None** or **NoneWithoutWarning**. Controls the " +"behavior when panchromatic and spectral bands have not the same " +"geospatial extent. By default, Union will take the union of all spatial " +"extents. Intersection the intersection of all spatial extents. None will " +"not proceed to any adjustment at all, but will emit a warning. " +"NoneWithoutWarning is the same as None, but in a silent way." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1840 +msgid "" +"The below examples creates a VRT dataset with 4 bands. The first band is " +"the panchromatic band. The 3 following bands are than red, green, blue " +"pansharpened bands computed from a multispectral raster with red, green, " +"blue and near-infrared bands. The near-infrared bands is taken into " +"account for the computation of the pseudo panchromatic intensity, but not" +" bound to an output band." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1906 +#: ../../source/drivers/raster/vrt_multidimensional.rst:5 +msgid "Multidimensional VRT" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1910 +msgid "See the dedicated :ref:`vrt_multidimensional` page." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1919 +msgid "Processed dataset VRT" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1923 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:9 +msgid "" +"A VRT processed dataset is a specific variant of the :ref:`raster.vrt` " +"format, to apply chained processing steps that may apply to several bands" +" at the same time." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1926 +msgid "See the dedicated :ref:`vrt_processed_dataset` page." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1935 +msgid "vrt:// connection string" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1939 +msgid "" +"In some contexts, it might be useful to benefit from features of VRT " +"without having to create a file or to provide the rather verbose VRT XML " +"content as the connection string. For that purpose, the following URI " +"syntax is supported for the dataset name since GDAL 3.1" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1980 +msgid "" +"The supported options currently are ``bands``, ``a_nodata``, ``a_srs``, " +"``a_ullr``, ``ovr``, ``expand``, ``a_scale``, ``a_offset``, ``ot``, " +"``gcp``, ``if``, ``scale``, ``exponent``, ``outsize``, ``projwin``, " +"``projwin_srs``, ``tr``, ``r``, ``srcwin``, ``a_gt``, ``oo``, " +"``unscale``, ``a_coord_epoch``, ``nogcp``, ``epo``, ``eco``, ``sd_name``," +" and ``sd``." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1984 +msgid "Other options may be added in the future." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1986 +msgid "" +"The effect of the ``bands`` option is to change the band composition. The" +" values specified are the source band numbers (between 1 and N), possibly" +" out-of-order or with repetitions. The ``mask`` value can be used to " +"specify the global mask band. This can also be seen as an equivalent of " +"running `gdal_translate -of VRT -b num1 ... -b numN`." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1991 +msgid "" +"The effect of the ``a_nodata`` option (added in GDAL 3.9) is to assign " +"(override) the nodata value of the source in the same way as " +"(:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1994 +msgid "" +"The effect of the ``a_srs`` option (added in GDAL 3.7) is to assign " +"(override) the coordinate reference system of the source in the same way " +"as (:ref:`gdal_translate`), it may be missing, or incorrect. The value " +"provided for ``a_srs`` may be a string or a file containing a srs " +"definition." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:1999 +msgid "" +"The effect of the ``a_ullr`` option (added in GDAL 3.7) is to assign " +"(override) the georeferenced bounds of the source in the same way as " +"(:ref:`gdal_translate`). The value consists of four numeric values " +"separated by commas, in the order 'xmin,ymax,xmax,ymin' (upper left x,y, " +"lower right x,y)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2003 +msgid "" +"The effect of the ``ovr`` option (added in GDAL 3.7) is to specify which " +"overview level of source file must be used, with the first overview level" +" being 0 (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2006 +msgid "" +"The effect of the ``expand`` option (added in GDAL 3.7) is to expose a " +"dataset with 1 band with a color table as a dataset with 3 (RGB) or 4 " +"(RGBA) bands, as with (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2009 +msgid "" +"The effect of the ``a_scale`` option (added in GDAL 3.7) is to set band " +"scaling value (no modification of pixel values is done), as with " +"(:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2012 +msgid "" +"The effect of the ``a_offset`` option (added in GDAL 3.7) is to set band " +"offset value (no modification of pixel values is done), as with " +"(:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2015 +msgid "" +"The effect of the ``ot`` option (added in GDAL 3.7) is to force the " +"output image bands to have a specific data type supported by the driver " +"as with (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2018 +msgid "" +"The effect of the ``gcp`` option (added in GDAL 3.7) is to add the " +"indicated ground control point to the output dataset. Values are a set of" +" numbers as per (:ref:`gdal_translate`) " +"``pixel,line,easting,northing[,elevation]``. Multiple entries may be " +"included. This can also be seen as an equivalent of running " +"`gdal_translate -of VRT -gcp pixel1 line1 easting1 northing1 [elevation1]" +" -gcp pixel2 line2 easting2 northing2 [elevation2] ... -gcp pixelN lineN " +"eastingN northingN [elevationN]`." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2023 +msgid "" +"The effect of the ``if`` option (added in GDAL 3.7) is to specify the " +"format/driver name/s to be attempted to open the input file " +"(:ref:`gdal_translate`). Values may be repeated separated by comma This " +"can also be seen as an equivalent of running `gdal_translate -of VRT -if " +"DRV1 -if DRV2 ... -if DRVN`." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2027 +msgid "" +"The effect of the ``scale`` option (added in GDAL 3.7) is to rescale the " +"input pixel values from the range **src_min** to **src_max** to the range" +" **dst_min** to **dst_max** ``src_min,src_max[,dst_min,dst_max]`` either" +" 2 or 4 comma separated values. The same rules apply for the source and " +"destination ranges, and ``scale_bn`` syntax may be used as it is with " +"(:ref:`gdal_translate`). The option ``scale=true`` (default if " +"unspecified is ``scale=false``) may also be used without value arguments " +"(added in GDAL 3.8), where it results in the output range 0,255 from " +"whatever the source range is. Do consider the need for also using ``ot`` " +"option in order to accommodate the intended output range." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2031 +msgid "" +"The effect of the ``exponent`` option (added in GDAL 3.7) is to apply " +"non-linear scaling with a power function, a single value to be used with " +"the ``scale`` option. The same ``exponent_bn`` syntax may be used in " +"combination with ``scale_bn`` to target specific band/s as per " +"(:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2035 +msgid "" +"The effect of the ``outsize`` option (added in GDAL 3.7) is to set the " +"size of the output, in numbers `pixel,line` or in fraction `pixel%,line%`" +" as per (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2037 +msgid "" +"The effect of the ``projwin`` option (added in GDAL 3.8) is to select a " +"subwindow from the source image in georeferenced coordinates in the same " +"way as (:ref:`gdal_translate`). The value consists of four numeric values" +" separated by commas, in the order 'xmin,ymax,xmax,ymin', these are in " +"the native georeferenced coordinates of the source unless ``projwin_srs``" +" is also provided." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2042 +msgid "" +"The effect of the ``projwin_srs`` option (added in GDAL 3.8) is to " +"specify the SRS in which to interpret the coordinates given with " +"``projwin`` in the same way as (:ref:`gdal_translate`). This option only " +"applies if ``projwin`` is also supplied." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2044 +msgid "" +"The effect of the ``tr`` option (added in GDAL 3.8) is to set the target " +"resolution, two positive values in georeferenced coordinates, applied in " +"the same way as (:ref:`gdal_translate`). The value consists of two " +"numeric values separated by commas in the order 'xres,yres'." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2046 +msgid "" +"The effect of the ``r`` option (added in GDAL 3.8) is to set the " +"resampling algorithm used, with 'nearest' as the default. This is applied" +" in the same way as (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2048 +msgid "" +"The effect of the ``srcwin`` option (added in GDAL 3.8) is to select a " +"subwindow from the source image based on pixel/line location as with " +"(:ref:`gdal_translate`). The value consists of four integer values " +"separated by commas, in the order 'xoff,yoff,xsize,ysize'." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2051 +msgid "" +"The effect of the ``a_gt`` option (added in GDAL 3.8) is to " +"override/assign the geotransform of the output as with " +"(:ref:`gdal_translate`). The value consists of six numeric values " +"separated by commas, in the order 'gt(0),gt(1),gt(2),gt(3),gt(4),gt(5)'." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2054 +msgid "" +"The effect of the ``oo`` option (added in GDAL 3.8) is to set driver-" +"specific dataset open options, multiple values are allowed. The value " +"consists of string key value pairs with multiple pairs separated by " +"commas e.g. ``oo=<key>=<val>`` or . " +"``oo=<key1>=<val1>,<key2>=<val2>,...``. This is applied in the same way " +"as (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2057 +msgid "" +"The effect of the ``unscale`` option (added in GDAL 3.8) is to apply the " +"scale/offset metadata for the bands to convert scaled values to unscaled " +"values. To apply this use syntax ``unscale=true``, or ``unscale=false`` " +"(which is the default if not specified). Do consider the need for also " +"using ``ot`` option in order to accommodate the intended output range, " +"see more details for the same argument as with (:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2059 +msgid "" +"The effect of the ``a_coord_epoch`` option (added in GDAL 3.8) is to " +"assign a coordinate epoch, linked with the output SRS as with " +"(:ref:`gdal_translate`)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2062 +msgid "" +"The effect of the ``nogcp`` option (added in GDAL 3.8) is to not copy the" +" GCPs in the source dataset to the output dataset " +"(:ref:`gdal_translate`). To apply this use syntax ``nogcp=true``, or " +"``nogcp=false`` (which is the default if not specified)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2065 +msgid "" +"The effect of the ``epo`` option (added in GDAL 3.8) is that ``srcwin`` " +"or ``projwin`` values that fall partially outside the source raster " +"extent will be considered as an error as per (:ref:`gdal_translate`). To " +"apply this use syntax ``epo=true``, or ``epo=false`` (which is the " +"default if not specified)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2067 +msgid "" +"The effect of the ``eco`` option (added in GDAL 3.8) is that ``srcwin`` " +"or ``projwin`` values that fall completely outside the source raster " +"extent will be considered as an error as per (:ref:`gdal_translate`). To " +"apply this use syntax ``eco=true``, or ``eco=false`` (which is the " +"default if not specified)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2069 +msgid "" +"The effect of the ``sd_name`` option (added in GDAL 3.9) is to choose an " +"individual subdataset by name for sources that have multiple subdatasets." +" This means that rather than a fully-qualified description such as " +"\"NETCDF:myfile.nc:somearray\" we may use " +"\"vrt://myfile.nc?sd_name=somearray\". This option is mutually exclusive " +"with ``sd``." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2074 +msgid "" +"The effect of the ``sd`` option (added in GDAL 3.9) is to choose an " +"individual subdataset by number for sources that have multiple " +"subdatasets. This means that rather than a fully-qualified description " +"such as \"NETCDF:myfile.nc:somearray\" we may use " +"\"vrt://myfile.nc?sd=<n>\" where \"<n>\" is between 1 and the number of " +"subdatasets. Note that there is no guarantee of the order of the " +"subdatasets within a source between GDAL versions (or in some cases " +"between file series in datasets). This mode is for convenience only, " +"please use ``sd_name`` to choose a subdataset by name explicitly. This " +"option is mutually exclusive with ``sd_name``." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2083 +msgid "" +"The options may be chained together separated by '&'. (Beware the need " +"for quoting to protect the ampersand)." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2093 +msgid "Multi-threading optimizations" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2095 +msgid "" +"Starting with GDAL 3.6, the ComputeStatistics() implementation can " +"benefit from multi-threading if the sources are not overlapping and " +"belong to different datasets. This can be enabled by setting the " +":config:`GDAL_NUM_THREADS` configuration option to an integer or " +"``ALL_CPUS``." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2101 +msgid "Multi-threading issues" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2105 +msgid "" +"The below section applies to GDAL <= 2.2. Starting with GDAL 2.3, the use" +" of VRT datasets is subject to the standard GDAL dataset multi-threaded " +"rules (that is a VRT dataset handle may only be used by a same thread at " +"a time, but you may open several dataset handles on the same VRT file and" +" use them in different threads)" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2111 +msgid "" +"When using VRT datasets in a multi-threading environment, you should be " +"careful to open the VRT dataset by the thread that will use it " +"afterwards. The reason for that is that the VRT dataset uses " +":cpp:func:`GDALOpenShared` when opening the underlying datasets. So, if " +"you open twice the same VRT dataset by the same thread, both VRT datasets" +" will share the same handles to the underlying datasets." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2118 +msgid "" +"The shared attribute, on the SourceFilename indicates whether the dataset" +" should be shared (value is 1) or not (value is 0). The default is 1. If " +"several VRT datasets referring to the same underlying sources are used in" +" a multithreaded context, shared should be set to 0. Alternatively, the " +":config:`VRT_SHARED_SOURCE` configuration option can be set to ``NO`` to " +"force non-shared mode:" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2134 +msgid "Performance considerations" +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2136 +msgid "" +"A VRT can reference many (hundreds, thousands, or more) datasets. Due to " +"operating system limitations, and for performance at opening time, it is " +"not reasonable/possible to open them all at the same time. GDAL has a " +"\"pool\" of datasets opened by VRT files whose maximum limit is 100 by " +"default. When it needs to access a dataset referenced by a VRT, it checks" +" if it is already in the pool of open datasets. If not, when the pool has" +" reached its limit, it closes the least recently used dataset to be able " +"to open the new one. This maximum limit of the pool can be increased by " +"setting the :config:`GDAL_MAX_DATASET_POOL_SIZE` configuration option to " +"a bigger value. Note that a typical user process on Linux is limited to " +"1024 simultaneously opened files, and you should let some margin for " +"shared libraries, etc... gdal_translate and gdalwarp, by default, " +"increase the pool size to 450." +msgstr "" + +#: ../../source/drivers/raster/vrt.rst:2149 +msgid "" +"Starting with GDAL 3.7, the :config:`GDAL_MAX_DATASET_POOL_RAM_USAGE` " +"configuration option to a number of bytes, to limit the RAM usage of " +"opened datasets in the pool." +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:9 +msgid "" +"Multidimensional VRT is a specific variant of the :ref:`raster.vrt` " +"format, dedicated to represent Multidimensional arrays, according to the " +":ref:`multidim_raster_data_model`." +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:13 +msgid "Here's an example of such a file:" +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:39 +msgid "" +"A `XML schema of the GDAL VRT format " +"<https://raw.githubusercontent.com/OSGeo/gdal/master/data/gdalvrt.xsd>`_ " +"is available." +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:45 +msgid "" +"**VRTDataset**: This is the root element for the whole GDAL dataset. It " +"has no attributes, and must have a single Group child element with an " +"attribute name set to \"/\"" +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:55 +msgid "" +"**Group**: This represents a :cpp:class:`GDALGroup`. There is at least " +"one root group of name \"/\" immediately under the VRTDataset element. A " +"Group must have a *name* attribute, and may have the following child " +"elements, with 0:n multiplicity: Dimension, Attribute, Array, Group" +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:60 +msgid "" +"**Dimension**: This represents a :cpp:class:`GDALDimension`. It has the " +"following attributes: *name* (required), *size* (required), *type* and " +"*direction*" +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:68 +msgid "" +"**Attribute**: This represents a :cpp:class:`GDALAttribute`. It must have" +" a *name* attribute and a child *DataType* element. Attribute values are " +"stored in one or several child *Value* element(s)" +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:72 +msgid "" +"The value of *DataType* may be: String, Byte, UInt16, Int16, UInt32, " +"Int32, Float32, Float64, CInt16, CInt32, CFloat32 or CFloat64." +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:83 +msgid "" +"**Array**: This represents a :cpp:class:`GDALMDArray`. It must have a " +"*name* attribute and a child *DataType* element. It may have 0 or more " +"*DimensionRef* or *Dimension* child elements to define its dimensions. " +"And the following elements may be optionally specified to define its " +"properties. *SRS, *Unit*, *NoDataValue*, *Offset* and *Scale*. To define " +"its values, it may have one *RegularlySpacedValues* element, or zero, one" +" or several elements among *ConstantValue*, *InlineValues*, " +"*InlineValuesWithValueElement* or *Source*." +msgstr "" + +#: ../../source/drivers/raster/vrt_multidimensional.rst:129 +msgid "" +"**Source**: This indicates that raster data should be read from a " +"separate dataset. A Source must have a *SourceFilename*, and either a " +"*SourceArray* (when the source is a Multidimensional dataset), or a " +"*SourceBand* (when the source is a classic 2D dataset) child element. It " +"may have a *SourceTranspose* child element to apply a " +":cpp:func:`GDALMDArray::Transpose` operation and a *SourceView* to apply " +"slicing/trimming operations or extraction of a component of a compound " +"data type (see :cpp:func:`GDALMDArray::GetView`). It may have a " +"*SourceSlab* element with attributes *offset*, *count* and *step* " +"defining respectively the starting offset of the source, the number of " +"values along each dimension and the step between source elements. It may " +"have a *DestSlab* element with an *offset* attribute to define where the " +"source data is placed into the target array. SourceSlab operates on the " +"output of SourceView if specified, which operates itself on the output of" +" SourceTranspose if specified." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:5 +msgid "VRT processed dataset" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:12 +msgid "" +"The following built-in algorithms are introduced, and may typically be " +"applied in the following order:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:15 +msgid "" +"LocalScaleOffset: apply per-pixel gain and offset coming (typically " +"subsampled) from auxiliary datasets. Can be used for dehazing processing." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:18 +msgid "" +"BandAffineCombination: perform an affine transformation combination of " +"bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:20 +msgid "Trimming: apply local thresholding of saturation" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:22 +msgid "LUT: apply a look-up table (band per band)" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:24 +msgid "" +"More algorithms can be registered at run-time with the " +":cpp:func:`GDALVRTRegisterProcessedDatasetFunc` function`" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:27 +msgid "" +"Here's an example of such a file to apply various correction to a " +"R,G,B,NIR dataset:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:116 +msgid ".vrt format" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:118 +msgid "" +"The ``VRTDataset`` root element must have a " +"``subClass=\"VRTProcessedDataset\"`` attribute." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:120 +msgid "" +"The following child elements of ``VRTDataset`` may be defined: ``SRS``, " +"``GeoTransform``, ``Metadata``. If they are not explicitly set, they are " +"inferred from the input dataset." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:122 +msgid "" +"``VRTRasterBand`` elements may be explicitly defined, in particular if " +"the data type of the virtual dataset after all processing steps is " +"different from the input one, or if the number of output bands is " +"different from the number of input bands. If there is no explicit " +"``VRTRasterBand`` element, the number and data types of input bands are " +"used implicitly. When explicitly defined, ``VRTRasterBand`` elements must" +" have a ``subClass=\"VRTProcessedRasterBand\"`` attribute. ` It must also" +" have the 2 following child elements:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:126 +msgid "" +"``Input``, which must have one and only one of the following " +"``SourceFilename`` or ``VRTDataset`` as child elements, to define the " +"input dataset to which to apply the processing steps." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:128 +msgid "``ProcessingSteps``, with at least one child ``Step`` element." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:130 +msgid "" +"Each ``Step`` must have a ``Algorithm`` child element, and an optional " +"``name`` attribute. The value of ``Algorithm`` must be a registered " +"VRTProcessedDataset function. At time of writing, the following 4 " +"algorithms are defined: ``LocalScaleOffset``, ``BandAffineCombination``, " +"``Trimming`` and ``LUT``." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:133 +msgid "" +"A ``Step`` will generally have one or several ``Argument`` child " +"elements, some of them being required, others optional. Consult the " +"documentation of each algorithm." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:136 +msgid "LocalScaleOffset algorithm" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:138 +msgid "" +"Apply per-pixel gain and offset coming (typically subsampled) from " +"auxiliary datasets. Can be used for dehazing processing." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:141 +msgid "" +"The gain and offset auxiliary datasets must have a georeferencing " +"consistent of the input dataset, but may have a different resolution." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:144 +msgid "" +"The formula applied by that algorithm is: ``output_value = " +"clamp(input_value * gain - offset, min, max)``" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:146 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:222 +msgid "The following required arguments must be specified:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:148 +msgid "" +"``gain_dataset_filename_{band}``: Filename to the gain dataset, where " +"{band} must be replaced by 1 to the number of input bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:150 +msgid "" +"``gain_dataset_band_{band}``: Band number corresponding to " +"``gain_dataset_filename_{band}``, where {band} must be replaced by 1 to " +"the number of input bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:152 +msgid "" +"``offset_dataset_filename_{band}``: Filename to the offset dataset, where" +" {band} must be replaced by 1 to the number of input bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:154 +msgid "" +"``offset_dataset_band_{band}``: Band number corresponding to " +"``offset_dataset_filename_{band}``, where {band} must be replaced by 1 to" +" the number of input bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:157 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:182 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:233 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:265 +msgid "The following optional arguments may be specified:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:159 +msgid "" +"``relativeToVRT``: Whether gain and offset filenames are relative to the " +"VRT. Allowed values are ``true`` and ``false``. Defaults to ``false``" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:161 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:192 +msgid "``min``: Clamp minimum value, applied before writing the output value." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:163 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:194 +msgid "``max``: Clamp maximum value, applied before writing the output value." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:165 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:243 +msgid "" +"``nodata``: Override the input nodata value coming from the previous step" +" (or the input dataset for the first step)." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:167 +msgid "" +"``gain_nodata``: Override the nodata value coming from the gain " +"dataset(s)." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:169 +msgid "" +"``offset_nodata``: Override the nodata value coming from the offset " +"dataset(s)." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:173 +msgid "BandAffineCombination algorithm" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:175 +msgid "Perform an affine transformation combination of bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:177 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:253 +msgid "The following required argument must be specified:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:179 +msgid "" +"``coefficients_{band}``: Comma-separated coefficients for combining bands" +" where {band} must be replaced by 1 to the number of output bands. The " +"number of coefficients in each argument must be 1 + " +"number_of_input_bands, where the first coefficient is a constant, the " +"second coefficient is the weight of the first input band, the third " +"coefficient is the weight of the second input band, etc." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:184 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:267 +msgid "" +"``src_nodata``: Override the input nodata value coming from the previous " +"step (or the input dataset for the first step)." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:186 +#: ../../source/drivers/raster/vrt_processed_dataset.rst:269 +msgid "``dst_nodata``: Set the output nodata value." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:188 +msgid "" +"``replacement_nodata``: Value to substitute to a valid computed value " +"that would be equal to dst_nodata." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:190 +msgid "" +"``dst_intended_datatype``: Intended datatype of output (which might be " +"different than the working data type). Used to infer an appropriate value" +" for replacement_nodata when it is not specified." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:198 +msgid "Trimming algorithm" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:200 +msgid "" +"Apply local thresholding of saturation, with a special processing of the " +"R,G,B bands compared to other bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:202 +msgid "The pseudo algorithm used for each pixel is:" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:224 +msgid "" +"``trimming_dataset_filename``: Filename of the trimming dataset. It must " +"have one single band. It must have a georeferencing consistent of the " +"input dataset, but may have a different resolution." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:226 +msgid "``top_rgb``: Maximum saturating RGB output value." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:228 +msgid "``tone_ceil``: Maximum threshold beyond which we give up saturation." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:230 +msgid "" +"``top_margin``: Margin to allow for dynamics in brighest areas (between 0" +" and 1, should be close to 0)" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:235 +msgid "" +"``relativeToVRT``: Whether the trimming dataset filename is relative to " +"the VRT. Allowed values are ``true`` and ``false``. Defaults to ``false``" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:237 +msgid "``red_band``: Index (one-based) of the red band. Defaults to 1." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:239 +msgid "``green_band``: Index (one-based) of the green band. Defaults to 1." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:241 +msgid "``blue_band``: Index (one-based) of the blue band. Defaults to 1." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:245 +msgid "" +"``trimming_nodata``: Override the nodata value coming from the trimming " +"dataset." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:249 +msgid "LUT" +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:251 +msgid "" +"Apply a look-up table (band per band), typically to get from UInt16 to " +"Byte data types." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:255 +msgid "" +"``lut_{band}``: List of the form ``[src value 1]:[dest value 1],[src " +"value 2]:[dest value 2],....``. {band} must be replaced by 1 to the " +"number of bands." +msgstr "" + +#: ../../source/drivers/raster/vrt_processed_dataset.rst:257 +msgid "" +"The intermediary values are calculated using a linear interpolation " +"between the bounding destination values of the corresponding range. " +"Source values should be monotonically non-decreasing. Clamping is " +"performed for input pixel values outside of the range specified by the " +"LUT. That is, if an input pixel value is lower than the minimum source " +"value, then the destination value corresponding to that minimum source " +"value is used as the output pixel value. And similarly for an input pixel" +" value that is greater than the maximum source value." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:5 +msgid "WCS -- OGC Web Coverage Service" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:7 +msgid "WCS" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:11 +msgid "" +"The optional GDAL WCS driver allows use of a coverage in a WCS server as " +"a raster dataset. GDAL acts as a client to the WCS server." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:14 +msgid "" +"Accessing a WCS server is accomplished by creating a local service " +"description file that contains one `<WCS_GDAL>` XML element. It is " +"important that there is no spaces or other content outside that element. " +"Starting at version 2.3 the service description file is meant to be " +"managed by the driver in a cache directory. User should control the " +"contents of the service file using options. The dataset name is " +":samp:`WCS:<URL>`, where the <URL> is the URL of the server appended " +"potentially appended with WCS version, coverage, and possibly other " +"parameters. If the WCS version is 2.0.1 further parameters can be given " +"to control how the data model of the coverage is mapped to the GDAL data " +"model." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:26 +msgid "" +"If the URL does not contain a coverage name, the driver attempts to fetch" +" the capabilities document from the server, parse it, and show the " +"resulting metadata to the user. Coverages are shown as subdatasets. If " +"the URL contains a coverage name as parameter (the key 'coverage' can be " +"used irrespective of the WCS version), the driver attempts to fetch the " +"coverage description document from the server, parse it, and create " +"service description file. A small test GetCoverage request may be done to" +" obtain details of the served data. If the respective server capabilities" +" file is not cached, it will also be fetched." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:36 +msgid "" +"With service version 2.0.1 (for which support is available starting at " +"GDAL version 2.3), it may be that the coverage has more than two " +"dimensions. In that case, the driver will append the coverage metadata " +"and show zero bands. At that point, the user must use options to further " +"instruct the driver how to deal with extra dimensions and data fields." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:42 +msgid "" +"The WCS driver supports WCS versions 1.0.0, 1.1.0, 1.1.1, 1.1.2, and " +"2.0.1 at basic level (version 0.7 is not supported and support for " +"version 2.0.1 is available starting at GDAL 2.3). Any return format that " +"is a single file, and is in a format supported by GDAL should work. The " +"driver will prefer a format with \"tiff\" in the name, otherwise it will " +"fallback to the first offered format. However, the user may set the " +"preferred format. Coordinate systems are read from the DescribeCoverage " +"result." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:59 +msgid "Service description file" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:61 +msgid "" +"The service description file has the following elements as immediate " +"children of the document element. Note that when the \"WCS:<URL>\" syntax" +" for dataset name is used, the contents of the service description file " +"is meant to be modified by using options." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:66 +msgid "**ServiceURL**: URL of the service without parameters" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:67 +msgid "" +"**Version**: The WCS version that is used in the communication. If the " +"dataset name syntax WCS:URL is used the default is 2.0.1 and the server's" +" response may change the user request, otherwise defaults to 1.0.0. " +"Versions 1.0.0, 1.1.0, 1.1.1, 1.1.2, and 2.0.1 are supported." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:71 +msgid "**CoverageName**: The coverage that is used for the dataset." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:72 +msgid "" +"**Format**: The format to use for GetCoverage calls. If not set, selected" +" by the driver. (WCS version 2.0)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:74 +msgid "" +"**PreferredFormat**: The format to use for GetCoverage calls. If not set," +" selected by the driver. (WCS versions 1.0 and 1.1)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:76 +msgid "" +"**Interpolation**: The interpolation method used when scaling. Should be " +"one of the server supported values. (GDAL 2.3)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:78 +msgid "**BlockXSize**: The block width to use for block cached remote access." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:80 +msgid "**BlockYSize**: The block height to use for block cached remote access." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:82 +msgid "" +"**OverviewCount**: The number of overviews to represent bands as having. " +"Defaults to a number such that the top overview is fairly smaller (less " +"than 1K x 1K or so)." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:85 +msgid "" +"**NoDataValue**: The nodata value to use for all the bands (blank for " +"none). Normally determined by the driver. With version 2.0.1 this may be " +"a comma separated list of values, one for each band." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:88 +msgid "**Elements for controlling the range and domain:**" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:89 +msgid "" +"**Domain**: The axes that are used for the spatial dimensions. The " +"default is to use the first two axes given by the server. The axis order " +"swap may apply. Syntax: *axis_name,axis_name* A *field_name:field_name* " +"in the list denotes a range of fields. (Used only with version 2.0.1)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:94 +msgid "" +"**DefaultTime**: A timePosition to use by default when accessing " +"coverages with a time dimension. Populated with the last offered time " +"position by default. (Used only with version 1.0.0)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:97 +msgid "" +"**FieldName**: Name of the field being accessed. Used only with version " +"1.1. Defaults to the first field in the DescribeCoverage. In version 1.1 " +"the range consists of one or more fields, which may be scalar or vector. " +"A vector field contains one or more bands." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:101 +msgid "" +"**BandCount**: Number of bands in the dataset, normally determined by the" +" driver." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:103 +msgid "" +"**BandType**: The pixel data type to use. Normally determined by the " +"driver." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:105 +msgid "**Elements for controlling the communication:**" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:106 +#: ../../source/drivers/vector/wfs.rst:67 +msgid "" +"**Timeout**: The timeout to use for remote service requests. If not " +"provided, the libcurl default is used." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:108 +#: ../../source/drivers/vector/wfs.rst:69 +msgid "" +"**UserPwd**: May be supplied with *userid:password* to pass a userid and " +"password to the remote server." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:110 +#: ../../source/drivers/vector/wfs.rst:71 +msgid "" +"**HttpAuth**: May be BASIC, NTLM or ANY to control the authentication " +"scheme to be used." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:112 +msgid "" +"**GetCoverageExtra**: An additional set of keywords to add to GetCoverage" +" requests in URL encoded form. eg. \"&RESAMPLE=BILINEAR&Band=1\". Note " +"that the extra parameters should not be known parameters (see below)." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:116 +msgid "" +"**DescribeCoverageExtra**: An additional set of keywords to add to " +"DescribeCoverage requests in URL encoded form. eg. \"&CustNo=775\"" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:118 +msgid "" +"**Elements that may be needed to deal with server quirks (GDAL 2.3):** " +"**Note:** The options are not propagated to the subdataset with the " +"switch -sd." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:122 +msgid "" +"**OriginAtBoundary**: Set this flag if the server reports grid origin to " +"be at the pixel boundary instead of the pixel center. (Use for MapServer " +"versions <= 7.0.7 with WCS versions 1.0.0 and 2.0.1)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:125 +msgid "" +"**OuterExtents**: Set to consider WCS 1.1 extents as boundaries of outer " +"pixels instead of centers of outer pixels. (Use for GeoServer)." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:127 +msgid "" +"**BufSizeAdjust**: Set to 0.5 in WCS 1.1 if data access fails due to the " +"response not having expected size. (Use for GeoServer)." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:129 +msgid "" +"**OffsetsPositive**: Use with MapServer in WCS version 2.0.1 together " +"wwith NrOffsets." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:131 +msgid "" +"**NrOffsets**: Set to 2 if the server requires that there are only two " +"values in the GridOffsets. Use when the server is MapServer or ArcGIS. " +"With MapServer use also OffsetsPositive." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:134 +msgid "" +"**GridCRSOptional**: Let the driver skip Grid\\* parameters from a WCS " +"1.1 GetCoverage request if the request is not scaled. Do not use for " +"GeoServer." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:137 +msgid "" +"**NoGridAxisSwap**: Set to tell the driver not to swap axis order. When " +"reading the grid geometry (in WCS 1.1 the origin and offsets, in WCS " +"2.0.1 the grid envelope, axis labels, and offsets) no axis order swap is " +"done although it would otherwise be done if this flag is set. In 1.1 it " +"would be done if the CRS has inverted axes. In 2.0.1 it would be done if " +"the axisOrder of the sequenceRule in GridFunction defines so. This is " +"needed usually both in 1.1 and 2.0.1 when parsing coverage descriptions " +"from MapServer and GeoServer." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:145 +msgid "" +"**SubsetAxisSwap** Set to tell the driver to swap the axis names in " +"boundedBy.Envelope.axisLabels when making WCS 2.0.1 GetCoverage request. " +"Needed for GeoServer when EPSG dictates axis order swap." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:148 +msgid "" +"**UseScaleFactor**: Set to tell the driver to use scale by factor " +"approach instead of scale to size when making a WCS 2.0.1 GetCoverage " +"request. Required when the server is ArcGIS." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:153 +msgid "Range and dimension subsetting" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:155 +msgid "" +"When WCS version 2.0.1 is used, the range (fields/bands) and the " +"dimension can and/or may need to be subsetted. If the data model of the " +"coverage contains dimensions beyond the two geographic or map " +"coordinates, those dimensions must be sliced for GDAL. The coverage may " +"also contain a large number of fields, from which only a subset is wanted" +" in the GDAL dataset." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:162 +msgid "" +"Range and dimension subsetting must be done via URL parameters since from" +" one coverage it is possible to create more than one different GDAL " +"datasets. In the WCS cache this means that there may be the sets of files" +" related to a GDAL dataset:" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:167 +msgid "" +"server Capabilities file and a GDAL dataset metadata file made from it " +"(key = URL with WCS version number)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:169 +msgid "" +"server DescribeCoverage file, a template GDAL service file made from it, " +"and a GDAL dataset metadata file made for it (key = URL with WCS version " +"number and coverage name)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:172 +msgid "" +"the GDAL service file specifically for this dataset, and a GDAL dataset " +"metadata file (key = URL with WCS version number, coverage name, and " +"range and dimension subsetting parameters)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:176 +msgid "" +"The following URL parameters are used to control the range and dimension " +"subsetting. Note that these can also be set through options into the " +"service file. The ones in URL take precedence." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:180 +msgid "" +"**RangeSubset**: Used to select a subset of coverage fields to the " +"dataset. Syntax: *field_name,field_name:field_name,..* (Note: requires " +"that the server implements the range subsetting extension.)" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:183 +msgid "" +"**Subset**: Trim or slice a dimension when fetching data from the server." +" Syntax: " +"*axis_name(trim_begin_value,trim_end_value);axis_name(slice_value)* Note " +"that trimming the geographic/map coordinates is done by the driver." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:190 +msgid "Other WCS parameters" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:192 +msgid "" +"The following WCS (version 2.0.1) parameters are recognized besides what " +"has been described above. These all can be set either through options or " +"directly into the URL. The ones in URL take precedence. Note that it is " +"up to the server to support/recognize these." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:197 +msgid "MediaType" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:198 +msgid "UpdateSequence" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:199 +msgid "GEOTIFF:COMPRESSION" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:200 +msgid "GEOTIFF:JPEG_QUALITY" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:201 +msgid "GEOTIFF:PREDICTOR" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:202 +msgid "GEOTIFF:INTERLEAVE" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:203 +msgid "GEOTIFF:TILING" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:204 +msgid "GEOTIFF:TILEWIDTH" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:209 +msgid "" +"When the \"WCS:<URL>\" dataset name syntax is used, open options are used" +" to control the driver and the contents of the service description file. " +"In the case the URL does not contain coverage name, the service " +"description file is not used and thus in that case the options are not " +"written into it. Open options are given separate to the dataset name, " +"with GDAL utility programs they are given using the -oo switch (`-oo " +"\"NAME=VALUE\"`). The -oo switch expects only one option but more options" +" can be given repeating the switch." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:218 +msgid "" +"In addition to DescribeCoverageExtra and GetCoverageExtra, which are " +"stored in the service description file, there is also " +"GetCapabilitiesExtra, which can be used as an open option when requesting" +" the overall capabilities from the server. The open option " +"SKIP_GETCOVERAGE can be used to prevent the driver making a GetCoverage " +"request to the server, which it usually does if it can't determine the " +"band count and band data type from the capabilities or coverage " +"descriptions. This option may be needed if GetCoverage request fails." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:227 +msgid "" +"All above listed element names can be given as options to the WCS driver." +" In the case of flags the option should formally be \"Name=TRUE\", but " +"only \"Name\" suffices." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:232 +msgid "The cache" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:234 +msgid "" +"When the \"WCS:<URL>\" dataset name syntax is used, the server responses," +" the service description file, and the metadata files are stored in a " +"cache. Generally, if the needed resource is in the cache, it will be used" +" and no extra calls to the server are done." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:239 +msgid "The default location of the cache directory is $HOME/.gdal/wcs_cache" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:241 +msgid "The cache contents can be seen as subdatasets using an empty URL:" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:247 +msgid "The cache control options/flags are" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:249 +msgid "**CACHE=path** Overrides the default cache location." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:250 +msgid "" +"**CLEAR_CACHE** The cache is completely initialized and all files are " +"deleted." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:252 +msgid "" +"**REFRESH_CACHE** The cache entry, either capabilities or coverage, " +"depending on the call at hand, is deleted." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:254 +msgid "**DELETE_FROM_CACHE=k** The cache entry (subdataset k), is deleted." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:257 +msgid "The WCS: dataset name syntax" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:259 +msgid "" +"The URL in the dataset name is not a complete WCS request URL. The " +"request URL, specifically, its query part, for GetCapabilities, " +"DescribeCoverage, and GetCoverage requests is composed by the driver. " +"Typically the user should only need to add to the server address the " +"version and coverage parameters. The string 'coverage' can be used as the" +" coverage parameter key although different WCS versions use different " +"keys. 'coverage' is also always used in the cache key." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:267 +msgid "" +"The user may add arbitrary standard and non-standard extra parameters to " +"the URL. However, when that is done, it should be noted that the URL is a" +" cache database key and capability documents are linked to coverage " +"documents through the key. Please consider using the Extra open options." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:273 +msgid "Time" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:275 +msgid "" +"This driver includes experimental support for time based WCS 1.0.0 " +"servers. On initial access the last offered time position will be " +"identified as the DefaultTime. Each time position available for the " +"coverage will be treated as a subdataset." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:280 +msgid "" +"Note that time based subdatasets are not supported when the service " +"description is the filename. Currently time support is not available for " +"versions other than WCS 1.0.0." +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:287 +msgid "A gdalinfo call to a coverage served by MapServer:" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:299 +msgid "A gdal_translate call to a scaled clip of a coverage served by GeoServer:" +msgstr "" + +#: ../../source/drivers/raster/wcs.rst:317 +msgid "`OGC WCS Standards <http://www.opengeospatial.org/standards/wcs>`__" +msgstr "" + +#: ../../source/drivers/raster/webp.rst:5 +msgid "WEBP - WEBP" +msgstr "" + +#: ../../source/drivers/raster/webp.rst:11 +msgid "GDAL can read and write WebP images through the WebP library." +msgstr "" + +#: ../../source/drivers/raster/webp.rst:14 +msgid "" +"WebP is a new image format that provides lossy compression for " +"photographic images. A WebP file consists of VP8 image data, and a " +"container based on RIFF." +msgstr "" + +#: ../../source/drivers/raster/webp.rst:18 +msgid "" +"The driver rely on the Open Source WebP library (BSD licensed). The WebP " +"library (at least in its version 0.1) only offers compression and " +"decompression of whole images, so RAM might be a limitation when dealing " +"with big images (which are limited to 16383x16383 pixels)." +msgstr "" + +#: ../../source/drivers/raster/webp.rst:23 +msgid "" +"The WEBP driver supports 3 bands (RGB) images. It also supports 4 bands " +"(RGBA)" +msgstr "" + +#: ../../source/drivers/raster/webp.rst:25 +msgid "" +"The WEBP driver can be used as the internal format used by the " +":ref:`raster.rasterlite` driver." +msgstr "" + +#: ../../source/drivers/raster/webp.rst:41 +msgid "Various creation options exists, among them :" +msgstr "" + +#: ../../source/drivers/raster/webp.rst:74 +msgid "`WebP home page <https://developers.google.com/speed/webp/>`__" +msgstr "" + +#: ../../source/drivers/raster/wld.rst:5 +msgid "WLD -- ESRI World File" +msgstr "" + +#: ../../source/drivers/raster/wld.rst:7 +msgid "" +"A world file file is a plain ASCII text file consisting of six values " +"separated by newlines. The format is:" +msgstr "" + +#: ../../source/drivers/raster/wld.rst:30 +msgid "You can construct that file simply by using your favorite text editor." +msgstr "" + +#: ../../source/drivers/raster/wld.rst:32 +msgid "" +"World file usually has suffix ``.wld``, but sometimes it may has " +"``.tfw``, ``.tifw``, ``.jgw`` or other suffixes depending on the image " +"file it comes with." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:5 +msgid "WMS -- Web Map Services" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:7 +#: ../../source/drivers/raster/wms.rst:105 +msgid "WMS" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:11 +msgid "" +"Accessing several different types of web image services is possible using" +" the WMS format in GDAL." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:24 +msgid "XML description file" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:26 +msgid "" +"Services are accessed by creating a local service description XML file --" +" there are examples below for each of the supported image services. It is" +" important that there be no spaces or other content before the " +"``<GDAL_WMS>`` element." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:32 +msgid "<GDAL_WMS>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:33 +msgid "<Service name=\"WMS\">" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:33 +msgid "" +"Define what mini-driver to use, currently supported are: WMS, WorldWind, " +"TileService, TMS, TiledWMS, VirtualEarth or AGS. (required)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:34 +msgid "<Version>1.1.1</Version>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:34 +msgid "WMS version. (optional, defaults to 1.1.1)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:35 +msgid "<ServerUrl>http://host.domain.com/wms.cgi?</ServerUrl>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:35 +msgid "WMS server URL. (required)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:36 +msgid "<SRS>EPSG:4326</SRS>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:36 +msgid "" +"Image projection (optional, defaults to EPSG:4326 in WMS and 102100 in " +"AGS, WMS version 1.1.1 or below only and ArcGIS Server). For ArcGIS " +"Server the spatial reference can be specified as either a well-known ID " +"or as a `spatial reference json object " +"<http://resources.arcgis.com/en/help/rest/apiref/geometry.html#sr>`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:37 +msgid "<CRS>CRS:83</CRS>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:37 +msgid "" +"Image projection (optional, defaults to EPSG:4326, WMS version 1.3.0 or " +"above only)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:38 +msgid "<ImageFormat>image/jpeg</ImageFormat>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:38 +msgid "" +"Format in which to request data. Paletted formats like image/gif will be " +"converted to RGB. (optional, defaults to image/jpeg)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:39 +msgid "<Transparent>FALSE</Transparent>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:39 +msgid "" +"Set to TRUE to include \"transparent=TRUE\" in the WMS GetMap request " +"(optional defaults to FALSE).  The request format and BandsCount need to " +"support alpha." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:40 +msgid "<Layers>modis%2Cglobal_mosaic</Layers>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:40 +msgid "" +"A URL encoded, comma separated string of layers (required, except for " +"TiledWMS)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:41 +msgid "<TiledGroupName>Clementine</TiledGroupName>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:41 +msgid "Comma separated list of layers. (required for TiledWMS)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:42 +msgid "<Styles></Styles>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:42 +msgid "Comma separated list of styles. (optional)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:43 +msgid "<BBoxOrder>xyXY</BBoxOrder>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:43 +msgid "" +"Reorder bbox coordinates arbitrarily. May be required for version 1.3 " +"servers. (optional) x - low X coordinate, y - low Y coordinate, X - high " +"X coordinate, Y - high Y coordinate" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:45 +msgid "</Service>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:46 +#: ../../source/drivers/raster/wmts.rst:239 +msgid "<DataWindow>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:46 +msgid "" +"Define size and extents of the data. (required, except for TiledWMS and " +"VirtualEarth)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:47 +#: ../../source/drivers/raster/wmts.rst:248 +msgid "<UpperLeftX>-180.0</UpperLeftX>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:47 +msgid "" +"X (longitude) coordinate of upper-left corner. (optional, defaults to " +"-180.0, except for VirtualEarth)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:48 +#: ../../source/drivers/raster/wmts.rst:253 +msgid "<UpperLeftY>90.0</UpperLeftY>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:48 +msgid "" +"Y (latitude) coordinate of upper-left corner. (optional, defaults to " +"90.0, except for VirtualEarth)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:49 +#: ../../source/drivers/raster/wmts.rst:258 +msgid "<LowerRightX>180.0</LowerRightX>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:49 +msgid "" +"X (longitude) coordinate of lower-right corner. (optional, defaults to " +"180.0, except for VirtualEarth)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:50 +#: ../../source/drivers/raster/wmts.rst:263 +msgid "<LowerRightY>-90.0</LowerRightY>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:50 +msgid "" +"Y (latitude) coordinate of lower-right corner. (optional, defaults to " +"-90.0, except for VirtualEarth)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:51 +msgid "<SizeX>2666666</SizeX>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:51 +#: ../../source/drivers/raster/wms.rst:52 +msgid "Image size in pixels." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:52 +msgid "<SizeY>1333333</SizeY>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:53 +msgid "<TileX>0</TileX>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:53 +msgid "" +"Added to tile X value at highest resolution. (ignored for WMS, tiled " +"image sources only, optional, defaults to 0)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:54 +msgid "<TileY>0</TileY>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:54 +msgid "" +"Added to tile Y value at highest resolution. (ignored for WMS, tiled " +"image sources only, optional, defaults to 0)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:55 +msgid "<TileLevel>0</TileLevel>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:55 +msgid "" +"Tile level at highest resolution. (tiled image sources only, optional, " +"defaults to 0)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:56 +msgid "<TileCountX>0</TileCountX>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:56 +msgid "" +"Can be used to define image size, SizeX = TileCountX \\* BlockSizeX \\* " +"2\\ :sup:`TileLevel`. (tiled image sources only, optional, defaults to 0)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:57 +msgid "<TileCountY>0</TileCountY>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:57 +msgid "" +"Can be used to define image size, SizeY = TileCountY \\* BlockSizeY \\* " +"2\\ :sup:`TileLevel`. (tiled image sources only, optional, defaults to 0)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:58 +msgid "<YOrigin>top</YOrigin>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:58 +msgid "" +"Can be used to define the position of the Y origin with respect to the " +"tile grid. Possible values are 'top', 'bottom', and 'default', where the " +"default behavior is mini-driver-specific. (TMS mini-driver only, " +"optional, defaults to 'bottom' for TMS)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:59 +#: ../../source/drivers/raster/wmts.rst:268 +msgid "</DataWindow>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:60 +msgid "<Projection>EPSG:4326</Projection>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:60 +msgid "" +"Image projection (optional, defaults to value reported by mini-driver or " +"EPSG:4326)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:61 +msgid "<IdentificationTolerance>2</IdentificationTolerance>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:61 +msgid "Identification tolerance (optional, defaults to 2)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:62 +msgid "<BandsCount>3</BandsCount>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:62 +msgid "" +"Number of bands/channels, 1 for grayscale data, 3 for RGB, 4 for RGBA. " +"(optional, defaults to 3)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:63 +#: ../../source/drivers/raster/wmts.rst:279 +msgid "<DataType>Byte</DataType>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:63 +#: ../../source/drivers/raster/wmts.rst:279 +msgid "" +"Band data type, one of: Byte, Int16, UInt16, Int32, UInt32, Float32, " +"Float64, etc.. (optional, defaults to Byte)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:64 +msgid "<DataValues NoData=\"0 0 0\" min=\"1 1 1\" max=\"255 255 255\" />" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:64 +msgid "" +"Define NoData and/or minimum and/or maximum value for bands. " +"nodata_values, min_values, max_values can be one single value, or a value" +" per band, with a space separator between value" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:65 +msgid "<BlockSizeX>1024</BlockSizeX>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:65 +#: ../../source/drivers/raster/wms.rst:66 +msgid "" +"Block size in pixels. (optional, defaults to 1024, except for " +"VirtualEarth)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:66 +msgid "<BlockSizeY>1024</BlockSizeY>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:67 +msgid "<OverviewCount>10</OverviewCount>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:67 +msgid "" +"Count of reduced resolution layers each having 2 times lower resolution. " +"(optional, default is calculated at runtime)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:68 +#: ../../source/drivers/raster/wmts.rst:318 +msgid "<Cache>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:68 +msgid "" +"Enable local disk cache. Allows for offline operation. (optional but " +"present in the autogenerated service file, cache is disabled when not " +"present or if it is overridden with GDAL_ENABLE_WMS_CACHE=NO)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:69 +#: ../../source/drivers/raster/wmts.rst:326 +msgid "<Path>./gdalwmscache</Path>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:69 +msgid "" +"Location where to store cache files. It is safe to use same cache path " +"for different data sources. /vsimem/ paths are supported allowing for " +"temporary in-memory cache. (optional, cf below Caching section for " +"default value)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:70 +#: ../../source/drivers/raster/wmts.rst:344 +msgid "<Depth>2</Depth>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:70 +#: ../../source/drivers/raster/wmts.rst:344 +msgid "" +"Number of directory layers. 2 will result in files being written as " +"cache_path/A/B/ABCDEF... (optional, defaults to 2)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:71 +#: ../../source/drivers/raster/wmts.rst:350 +msgid "<Extension>.jpg</Extension>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:71 +#: ../../source/drivers/raster/wmts.rst:350 +msgid "Append to cache files. (optional, defaults to none)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:72 +#: ../../source/drivers/raster/wmts.rst:338 +msgid "<Type>file</Type>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:72 +#: ../../source/drivers/raster/wmts.rst:338 +msgid "" +"Cache type. Now supported only 'file' type. In 'file' cache type files " +"are stored in file system folders. (optional, defaults to 'file')" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:73 +msgid "<Expires>604800</Expires>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:73 +msgid "" +"Time in seconds cached files will stay valid. If cached file expires it " +"is deleted when maximum size of cache is reached. Also expired file can " +"be overwritten by the new one from web. Default value is 7 days " +"(604800s)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:74 +msgid "<MaxSize>67108864</MaxSize>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:74 +msgid "" +"The cache maximum size in bytes. If cache reached maximum size, expired " +"cached files will be deleted. Default value is 64 Mb (67108864 bytes)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:75 +msgid "<CleanTimeout>120</CleanTimeout>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:75 +msgid "" +"Clean Thread Run Timeout in seconds. How often to run the clean thread, " +"which finds and deletes expired cached files. Default value is 120s. Use " +"value of 0 to disable the Clean Thread (effectively unlimited cache " +"size). If you intend to use very large cache size you might want to " +"disable the cache clean or to use a much longer timeout as the time that " +"takes to scan the cache files for expired cache files might be long. " +"(\"disabled\" was the only option for GDAL <= 2.2; \"120s\" was the only " +"option for 2.3 <= GDAL <= 3.1)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:76 +msgid "<Unique>True</Unique>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:76 +msgid "" +"If set to true the path will appended with md5 hash of ServerURL. Default" +" value is true." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:77 +#: ../../source/drivers/raster/wmts.rst:353 +msgid "</Cache>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:78 +msgid "<MaxConnections>2</MaxConnections>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:78 +msgid "" +"Maximum number of simultaneous connections. (optional, defaults to 2). " +"Can also be set with the :config:`GDAL_MAX_CONNECTIONS` configuration " +"option (GDAL >= 3.2)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:79 +#: ../../source/drivers/raster/wmts.rst:359 +msgid "<Timeout>300</Timeout>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:79 +msgid "" +"Connection timeout in seconds. (optional, defaults to 300 or " +":config:`GDAL_HTTP_TIMEOUT`, if specified)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:80 +#: ../../source/drivers/raster/wmts.rst:362 +msgid "<OfflineMode>true</OfflineMode>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:80 +#: ../../source/drivers/raster/wmts.rst:362 +msgid "" +"Do not download any new images, use only what is in cache. Useful only " +"with cache enabled. (optional, defaults to false)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:81 +msgid "<AdviseRead>true</AdviseRead>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:81 +msgid "" +"Enable AdviseRead API call - download images into cache. (optional, " +"defaults to false)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:82 +msgid "<VerifyAdviseRead>true</VerifyAdviseRead>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:82 +msgid "" +"Open each downloaded image and do some basic checks before writing into " +"cache. Disabling can save some CPU cycles if server is trusted to always " +"return correct images. (optional, defaults to true)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:83 +msgid "<ClampRequests>false</ClampRequests>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:83 +msgid "" +"Should requests, that otherwise would be partially outside of defined " +"data window, be clipped resulting in smaller than block size request. " +"(optional, defaults to true)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:84 +msgid "<UserAgent>GDAL WMS driver (http://www.gdal.org/frmt_wms.html)</UserAgent>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:84 +msgid "" +"HTTP User-agent string. Some servers might require a well-known user-" +"agent such as \"Mozilla/5.0\" (optional, defaults to \"GDAL WMS driver " +"(http://www.gdal.org/frmt_wms.html)\"). When used with some servers, like" +" OpenStreetMap ones, it is highly recommended to put a custom user agent " +"to avoid being blocked if the default user agent had to be blocked." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:85 +#: ../../source/drivers/raster/wmts.rst:375 +msgid "<Accept>mimetype>/Accept>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:85 +msgid "" +"HTTP Accept header to specify the MIME type of the expected output of the" +" server. Empty by default" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:86 +#: ../../source/drivers/raster/wmts.rst:380 +msgid "<UserPwd>user:password</UserPwd>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:86 +#: ../../source/drivers/raster/wmts.rst:380 +msgid "User and Password for HTTP authentication (optional)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:87 +#: ../../source/drivers/raster/wmts.rst:383 +msgid "<UnsafeSSL>true</UnsafeSSL>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:87 +msgid "" +"Skip SSL certificate verification. May be needed if server is using a " +"self signed certificate (optional, defaults to false)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:88 +msgid "<Referer>http://example.foo/</Referer>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:88 +#: ../../source/drivers/raster/wmts.rst:390 +msgid "HTTP Referer string. Some servers might require it (optional)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:89 +msgid "<ZeroBlockHttpCodes>204,404</ZeroBlockHttpCodes>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:89 +msgid "" +"Comma separated list of HTTP response codes that will be interpreted as a" +" 0 filled image (i.e. black for 3 bands, and transparent for 4 bands) " +"instead of aborting the request. (optional, defaults to 204)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:90 +msgid "<ZeroBlockOnServerException>true</ZeroBlockOnServerException>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:90 +msgid "" +"Whether to treat a Service Exception returned by the server as a 0 filled" +" image instead of aborting the request. (optional, defaults to false)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:91 +msgid "</GDAL_WMS>" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:92 +msgid "\\" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:95 +msgid "" +"Starting with GDAL 2.3, additional HTTP headers can be sent by setting " +"the GDAL_HTTP_HEADER_FILE configuration option to point to a filename of " +"a text file with “key: value” HTTP headers." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:98 +msgid "Minidrivers" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:100 +msgid "" +"The GDAL WMS driver has support for several internal 'minidrivers', which" +" allow access to different web mapping services. Each of these services " +"may support a different set of options in the Service block." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:107 +msgid "" +"Communications with an OGC WMS server. Has support for both tiled and " +"untiled requests." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:110 +msgid "" +"WMS layers can be queried (through a GetFeatureInfo request) with the " +"gdallocationinfo utility, or with a GetMetadataItem(\"Pixel_iCol_iLine\"," +" \"LocationInfo\") call on a band object." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:166 +msgid "TileService" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:168 +msgid "" +"Service to support talking to a WorldWind `TileService " +"<http://www.worldwindcentral.com/wiki/TileService>`__. Access is always " +"tile based." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:173 +msgid "WorldWind" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:175 +msgid "Access to web-based WorldWind tile services. Access is always tile based." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:179 +msgid "TMS" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:181 +msgid "" +"The TMS Minidriver is designed primarily to support the users of the `TMS" +" Specification " +"<http://wiki.osgeo.org/wiki/Tile_Map_Service_Specification>`__. This " +"service supports only access by tiles." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:186 +msgid "" +"Because TMS is similar to many other 'x/y/z' flavored services on the " +"web, this service can also be used to access these services. To use it in" +" this fashion, you can use replacement variables, of the format ${x}, " +"${y}, etc." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:191 +msgid "Supported variables (name is case sensitive) are :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:193 +msgid "${x} -- x position of the tile" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:194 +msgid "" +"${y} -- y position of the tile. This can be either from the top or the " +"bottom of the tileset, based on whether the YOrigin parameter is set to " +"true or false." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:197 +msgid "${z} -- z position of the tile -- zoom level" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:198 +msgid "" +"${version} -- version parameter, set in the config file. Defaults to " +"1.0.0." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:200 +msgid "${format} -- format parameter, set in the config file. Defaults to 'jpg'." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:202 +msgid "${layer} -- layer parameter, set in the config file. Defaults to nothing." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:205 +msgid "A typical ServerURL might look like:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:206 +msgid "``http://tilecache.osgeo.org/wms-c/Basic.py/${version}/${layer}/${z}/${x}/${y}.${format}``" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:209 +msgid "" +"In order to better suit TMS users, any URL that does not contain \"${\" " +"will automatically have the string above (after \"Basic.py/\") appended " +"to their URL." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:211 +msgid "" +"The TMS Service has 3 XML configuration elements that are different from " +"other services: ``Format`` which defaults to ``jpg``, ``Layer`` which has" +" no default, and ``Version`` which defaults to ``1.0.0``." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:215 +msgid "" +"Additionally, the TMS service respects one additional parameter, at the " +"DataWindow level, which is the YOrigin element. This element should be " +"one of ``bottom`` (the default in TMS) or ``top``, which matches " +"OpenStreetMap and many other popular tile services." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:220 +msgid "" +"Two examples of usage of the TMS service are included in the examples " +"below." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:224 +msgid "OnEarth Tiled WMS" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:226 +msgid "" +"The OnEarth Tiled WMS minidriver supports the Tiled WMS specification " +"implemented for the JPL OnEarth driver per the specification at " +"http://web.archive.org/web/20130511182803/http://onearth.jpl.nasa.gov/tiled.html." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:230 +msgid "" +"Only the ServerUrl and the TiledGroupName are required, most of the " +"required information is automatically fetched from the remote server " +"using the GetTileService method at open time." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:233 +msgid "A typical OnEarth Tiled WMS configuration file might look like:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:245 +msgid "The TiledWMS minidriver can use the following open options :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:247 +msgid "" +"TiledGroupName -- The value is a string that identifies one of the tiled " +"services available on the server" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:249 +msgid "" +"Change -- A <Key>:<Value> pair, which will be passed to the server. The " +"key has to match a change key that the server declares for the respective" +" tiled group. This option can be used multiple times, for different keys." +" Example: - Change=time:2020-02-02" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:255 +msgid "" +"These open options are only accepted if the corresponding XML element is " +"not present in the configuration file." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:259 +msgid "VirtualEarth" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:261 +msgid "" +"Access to web-based Virtual Earth tile services. Access is always tile " +"based." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:264 +msgid "The ${quadkey} variable must be found in the ServerUrl element." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:266 +msgid "The DataWindow element might be omitted. The default values are :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:268 +msgid "UpperLeftX = -20037508.34" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:269 +msgid "UpperLeftY = 20037508.34" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:270 +msgid "LowerRightX = 20037508.34" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:271 +msgid "LowerRightY = -20037508.34" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:272 +msgid "TileLevel = 21" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:273 +msgid "OverviewCount = 20" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:274 +msgid "SRS = EPSG:3857" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:275 +msgid "BlockSizeX = 256" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:276 +msgid "BlockSizeY = 256" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:279 +msgid "ArcGIS REST API" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:281 +msgid "" +"Access to ArcGIS REST `map service resource " +"<http://resources.arcgis.com/en/help/rest/apiref/mapserver.html>`__ " +"(untiled requests)." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:285 +msgid "" +"AGS layers can be `queried " +"<http://resources.arcgis.com/en/help/rest/apiref/identify.html>`__ " +"(through a GetFeatureInfo request) with the gdallocationinfo utility, or " +"with a GetMetadataItem(\"Pixel_iCol_iLine\", \"LocationInfo\") call on a " +"band object." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:297 +msgid "Internet Imaging Protocol (IIP) (GDAL 2.1 and later)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:299 +msgid "" +"Access to images served through `IIP protocol " +"<https://en.wikipedia.org/wiki/Internet_Imaging_Protocol>`__. The server " +"must support the JTL (Retrieve a tile as a complete JFIF image) extension" +" of the IIP protocol." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:304 +msgid "If using the XML syntax, the ServerURL must contain the FIF parameter." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:306 +msgid "" +"Otherwise it is also possible to use " +"\"IIP:http://foo.com/FIF=image_name\" syntax as connection string, to " +"retrieve from the server information on the full resolution dimension and" +" the number of resolutions." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:310 +msgid "" +"The XML definition can then be generated with \"gdal_translate " +"IIP:http://foo.com/FIF=image_name out.xml -of WMS\"" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:314 +msgid "Caching" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:316 +msgid "" +"Caching of remote pixel data is possible by setting a <Cache> element in " +"the WMS configuration file." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:319 +msgid "" +"Before GDAL 3.9, if the <Path> sub-element of <Cache> was not specified, " +"the directory of the cache was ``./gdalwmscache`` (that is to say a " +"``gdalwmscache`` subdiretory of the current directory), unless the " +":config:`GDAL_DEFAULT_WMS_CACHE_PATH` configuration option is specified." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:324 +msgid "" +"Starting with GDAL 3.9, the directory of the cache is set according to " +"the following logic (first listed criterion is prioritary over following " +"ones):" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:327 +msgid "Value of the <Path> sub-element of <Cache>, if specified." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:329 +msgid "" +"``${GDAL_DEFAULT_WMS_CACHE_PATH}`` if " +":config:`GDAL_DEFAULT_WMS_CACHE_PATH` is set." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:331 +msgid "" +"``${XDG_CACHE_HOME}/gdalwmscache`` if the ``XDG_CACHE_HOME`` " +"configuration option is set." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:333 +msgid "" +"On Unix, ``${HOME}/.cache/gdalwmscache`` if the ``HOME`` configuration " +"option is set." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:335 +msgid "" +"On Windows, ``${USERPROFILE}/.cache/gdalwmscache`` if the ``USERPROFILE``" +" configuration option is set." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:337 +msgid "" +"``${CPL_TMPDIR}/gdalwmscache_${USER}`` if :config:`CPL_TMPDIR` and " +"``USER`` configuration options are set." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:339 +msgid "If ``CPL_TMPDIR`` is not set, then ``TMPDIR`` is used, or ``TEMP``" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:341 +msgid "" +"If ``USER`` is not set, ``USERNAME`` is used if set. If neither " +"``USERNAME`` or ``USER`` are set, the md5sum of the filename of the " +"configuration file is used)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:344 +msgid "" +"``./gdalwmscache_{md5sum(filename)}`` if none of the above mentioned " +"configuration options are set." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:346 +msgid "" +"Note that if the <Unique> element is set to true (which is its default " +"value), a subdirectory whose name is the md5sum of the filename of the " +"configuration file is appended to the caching directory." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:350 +msgid "" +"The actual caching directory can be got by querying the ``CACHE_PATH`` " +"metadata item on the dataset." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:356 +msgid "The following :ref:`configuration options <configoptions>` are available:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:386 +msgid "" +"The below examples rely on external servers that might go down over time." +" They are just here to demonstrate how to use the various services." +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"`onearth_global_mosaic.xml " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_wms_onearth_global_mosaic.xml>`__" +" - Landsat mosaic from a `OnEarth <http://onearth.jpl.nasa.gov/>`__ WMS " +"server" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:402 +msgid "*Note : this particular server does no longer accept regular WMS queries.*" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:405 +msgid "" +"`metacarta_wmsc.xml " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_wms_metacarta_wmsc.xml>`__" +" - It is possible to configure a WMS Service conforming to a WMS-C cache " +"by specifying a number of overviews and specifying the 'block size' as " +"the tile size of the cache. The following example is a sample set up for " +"a 19-level \"Global Profile\" WMS-C cache." +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"`tileservice_bmng.xml " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_wms_tileservice_bmng.xml>`__" +" - - TileService, Blue Marble NG (January)" +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"`tileservice_nysdop2004.xml " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_wms_tileservice_nysdop2004.xml>`__" +" - TileService, NYSDOP 2004" +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"`OpenStreetMap TMS Service Example " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_wms_openstreetmap_tms.xml>`__:" +" Connect to OpenStreetMap tile service. Note that this file takes " +"advantage of the tile cache; more information about configuring the tile " +"cache settings is available above. Please also change the <UserAgent>, to" +" avoid the default one being used, and potentially blocked by OSM servers" +" in case a too big usage of it would be seen." +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"``gdal_translate -of PNG -outsize 512 512 frmt_wms_openstreetmap_tms.xml " +"openstreetmap.png``" +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"`MetaCarta TMS Layer Example " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_wms_metacarta_tms.xml>`__," +" accessing the default MetaCarta TMS layer." +msgstr "" + +#: ../../source/drivers/raster/wms.rst +msgid "" +"``gdal_translate -of PNG -outsize 512 256 frmt_wms_metacarta_tms.xml " +"metacarta.png``" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:430 +msgid "" +"`BlueMarble Amazon S3 Example " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_wms_bluemarble_s3_tms.xml>`__" +" accessed with the TMS minidriver." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:433 +msgid "" +"`Google Maps " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_wms_googlemaps_tms.xml>`__" +" accessed with the TMS minidriver." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:436 +msgid "" +"`ArcGIS MapServer Tiles " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_wms_arcgis_mapserver_tms.xml>`__" +" accessed with the TMS minidriver." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:439 +msgid "" +"OnEarth Tiled WMS `Clementine " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_twms_Clementine.xml>`__," +" `daily " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_twms_daily.xml>`__," +" and `srtm " +"<https://github.com/OSGeo/gdal/blob/master/gdal/frmts/wms/frmt_twms_srtm.xml>`__" +" examples." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:443 +msgid "" +"`VirtualEarth Aerial Layer " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_wms_virtualearth.xml>`__" +" accessed with the VirtualEarth minidriver." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:446 +msgid "" +"`ArcGIS online sample server layer " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_ags_arcgisonline.xml>`__" +" accessed with the ArcGIS Server REST API minidriver." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:449 +msgid "" +"`IIP online sample server layer " +"<https://github.com/OSGeo/gdal/blob/master/frmts/wms/frmt_wms_iip.xml>`__" +" accessed with the IIP minidriver." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:455 +msgid "The WMS driver can open :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:457 +msgid "a local service description XML file :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:463 +#: ../../source/drivers/raster/wmts.rst:36 +msgid "the content of a description XML file provided as filename :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:469 +msgid "the base URL of a WMS service, prefixed with *WMS:* :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:475 +msgid "" +"A list of subdatasets will be returned, resulting from the parsing of the" +" GetCapabilities request on that server." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:478 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if WMS`` option to command " +"line utilities accepting it, or ``WMS`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed URL, without the ``WMS:`` prefix." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:483 +msgid "" +"a pseudo GetMap request, such as the subdataset name returned by the " +"previous syntax :" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:490 +msgid "" +"the base URL of a Tiled WMS service, prefixed with *WMS:* and with " +"request=GetTileService as GET argument:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:497 +msgid "" +"A list of subdatasets will be returned, resulting from the parsing of the" +" GetTileService request on that server." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:500 +msgid "the URL of a REST definition for a ArcGIS MapServer:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:506 +msgid "(GDAL >= 2.1.0) the URL of a IIP image:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:513 +msgid "Generation of WMS service description XML file" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:515 +msgid "" +"The WMS service description XML file can be generated manually, or " +"created as the output of the CreateCopy() operation of the WMS driver, " +"only if the source dataset is itself a WMS dataset. Said otherwise, you " +"can use gdal_translate with as source dataset any of the above syntax " +"mentioned in \"Open syntax\" and as output an XML file. For example:" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:525 +#: ../../source/drivers/raster/wmts.rst:465 +msgid "" +"The generated file will come with default values that you may need to " +"edit." +msgstr "" + +#: ../../source/drivers/raster/wms.rst:531 +msgid "`OGC WMS Standards <http://www.opengeospatial.org/standards/wms>`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:532 +msgid "" +"`WMS Tiling Client Recommendation (WMS-C) " +"<http://wiki.osgeo.org/index.php/WMS_Tiling_Client_Recommendation>`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:534 +msgid "" +"`WorldWind TileService " +"<http://www.worldwindcentral.com/wiki/TileService>`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:536 +msgid "" +"`TMS Specification " +"<http://wiki.osgeo.org/wiki/Tile_Map_Service_Specification>`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:538 +msgid "" +"`OnEarth Tiled WMS specification " +"<http://web.archive.org/web/20130511182803/http://onearth.jpl.nasa.gov/tiled.html>`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:540 +msgid "" +"`ArcGIS Server REST API " +"<http://resources.arcgis.com/en/help/rest/apiref/>`__" +msgstr "" + +#: ../../source/drivers/raster/wms.rst:542 +msgid ":ref:`raster.wmts` driver page." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:5 +msgid "WMTS -- OGC Web Map Tile Service" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:7 +msgid "WMTS" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:13 +msgid "" +"Access to WMTS layers is possible with the GDAL WMTS client driver (needs" +" Curl support). It support both RESTful and KVP protocols." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:27 +msgid "The WMTS driver can open :" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:29 +msgid "" +"a local service description XML file, whose syntax is described in the " +"below section :" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:42 +msgid "a local GetCapabilities response of a WMTS service :" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:48 +msgid "the URL to the GetCapabilities response of a WMTS service:" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:54 +msgid "" +"the URL to the GetCapabilities response of a WMTS service, prefixed with " +"*WMTS:*, and possibly with optional layer, tilematrixset, " +"tilematrix/zoom_level, style and extendbeyonddateline parameters, with " +"the following syntax " +"*WMTS:url[,layer=layer_id][,tilematrixset=tms_id][,tilematrix=tm_id|,zoom_level=level][,style=style_id][,extendbeyonddateline=yes/no]*." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:68 +msgid "the *WMTS:* prefix with open options" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:74 +msgid "" +"In any of the above syntaxes, if several layers are present and no layer " +"disambiguation was done with the layer parameter/open option, or if a " +"layer has more than one style or a tile matrix set, a list of subdatasets" +" will be returned. If there is only one layer, it will be opened on the " +"default style and the first tile matrix set listed." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:80 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if WMTS`` option to command " +"line utilities accepting it, or ``WMTS`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename/URL, when it is not using subdataset " +"syntax (it can typically be used to force open a HDF5 file that would be " +"nominally recognized by the HDF5 driver)." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:89 +msgid "The following open options are available:" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:170 +msgid "Local service description XML file" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:172 +msgid "" +"It is important that there be no spaces or other content before the " +"``<GDAL_WMTS>`` element." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:176 +msgid "<GDAL_WMTS>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:178 +msgid "<GetCapabilitiesUrl>http://foo/WM TSCapabilities.xml</GetCapabiliti esUrl>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:178 +msgid "" +"URL (or filename for local files) to GetCapabilities response document " +"(required). For a KVP only server, will be like " +"http://end_point?SERVICE=WMTS& ;REQUEST=GetCapabilities ." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:186 +msgid "<ExtraQueryParameters>foo=bar&" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:186 +msgid "" +"URL query parameters to add to all requests (GetCapabilities, GetTile, " +"GetFeatureInfo) (added in GDAL 3.5.1)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:191 +msgid "<Layer>layer_id</Layer>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:191 +msgid "" +"Layer identifier (optional, but may be needed to disambiguate between " +"several layers)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:195 +msgid "<Style>style_id</Style>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:195 +msgid "" +"Style identifier. Must be one of the listed styles for the layer. " +"(optional, but may be needed to disambiguate between several styles)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:201 +msgid "<TileMatrixSet>tile_matrix_set_id </TileMatrixSet>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:201 +msgid "" +"Tile Matrix Set identifier. Must be one of the listed tile matrix set for" +" the layer. (optional, but may be needed to disambiguate between several " +"tile matrix sets)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:207 +msgid "<TileMatrix>tile_matrix_id</TileM atrix>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:207 +msgid "" +"Tile Matrix identifier. Must be one of the listed tile matrix of the " +"select tile matrix set for the layer. (optional, GDAL >= 2.2. Exclusive " +"with ZoomLevel. If not specified the last tile matrix, ie the one with " +"the best resolution, is selected)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:216 +msgid "<ZoomLevel>int_value</ZoomLevel>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:216 +msgid "" +"Index of the maximum zoom level / tile matrix to use. The first one (ie " +"the one of lower resolution) is indexed 0. (optional, GDAL >= 2.2. " +"Exclusive with TileMatrix. If not specified the last tile matrix, ie the " +"one with the best resolution, is selected)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:225 +msgid "<Format>image/png</Format>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:225 +msgid "" +"Tile format, used by GetTile requests. Must be one of the listed Format " +"for the layer. (optional, but may be needed to disambiguate between " +"several Format)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:232 +msgid "<InfoFormat>application/xml</Info Format>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:232 +msgid "" +"Info format, used by GetFeatureInfo requests. Must be one of the listed " +"InfoFormat for the layer. (optional, but may be needed to disambiguate " +"between several InfoFormat)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:239 +msgid "" +"Define extents of the data. (optional, when not specified the driver will" +" query the declared extent of the layer, and if not present fallback to " +"the extent of the select tile matrix set, taking into account potential " +"tile matrix set limits)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:248 +msgid "" +"X (longitude/easting) coordinate of upper-left corner, in the SRS of the " +"tile matrix set. (required if DataWindow is present)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:253 +msgid "" +"Y (latitude/northing) coordinate of upper-left corner, in the SRS of the " +"tile matrix set. (required if DataWindow is present)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:258 +msgid "" +"X (longitude/easting) coordinate of lower-right corner, in the SRS of the" +" tile matrix set. (required if DataWindow is present)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:263 +msgid "" +"Y (latitude/northing) coordinate of lower-right corner, in the SRS of the" +" tile matrix set. (required if DataWindow is present)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:270 +msgid "<Projection>EPSG:4326</Projection >" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:270 +msgid "" +"Declared projection, in case the one of the TileMatrixSet is not " +"desirable (optional, defaults to value of the TileMatrixSet)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:275 +msgid "<BandsCount>4</BandsCount>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:275 +msgid "" +"Number of bands/channels, 1 for grayscale data, 3 for RGB, 4 for RGBA. " +"(optional, defaults to 4)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:284 +msgid "<ExtendBeyondDateLine>false</Exte ndBeyondDateLine>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:284 +msgid "" +"Whether to make the extent go over dateline and warp tile requests. Only " +"appropriate when the 2 following conditions are met (optional, defaults " +"to false):" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:291 +msgid "" +"for a geodetic SRS or EPSG:3857, with tile matrix sets such as the whole " +"[-180,180] range of longitude is entirely covered by an integral number " +"of tiles (e.g. GoogleMapsCompatible)." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:298 +#: ../../source/drivers/vector/tiledb.rst:57 +msgid "AND" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:300 +msgid "" +"when the layer BoundingBox in the SRS of the tile matrix set covers the " +"whole [-180,180] range of longitude, and that there is another " +"BoundingBox in another SRS that is centered around longitude 180. If such" +" alternate BoundingBox is not present in the GetCapabilities document, " +"DataWindow must be explicitly specified" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:313 +msgid "" +"OR when the layer BoundingBox in the SRS of the tile matrix set extends " +"beyond the dateline." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:318 +msgid "" +"Enable local disk cache. Allows for offline operation. (optional, cache " +"is disabled when absent, but it is present in the autogenerated XML, can " +"be overridden with GDAL_ENABLE_WMS_CACHE=NO" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:326 +msgid "" +"Location where to store cache files. It is safe to use same cache path " +"for different data sources. (optional, defaults to ./gdalwmscache if " +"GDAL_DEFAULT_WMS_CACHE_PATH configuration option is not specified) " +"/vsimem/ paths are supported allowing for temporary in-memory cache" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:355 +msgid "<MaxConnections>2</MaxConnections >" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:355 +msgid "Maximum number of simultaneous connections. (optional, defaults to 2)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:359 +msgid "Connection timeout in seconds. (optional, defaults to 300)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:367 +msgid "" +"<UserAgent>GDAL WMS driver (http://www.gdal.org/frmt_wms.htm " +"l)</UserAgent>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:367 +msgid "" +"HTTP User-agent string. Some servers might require a well-known user-" +"agent such as \"Mozilla/5.0\" (optional, defaults to \"GDAL WMS driver " +"(http://www.gdal.org/frmt_wms.htm l)\")." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:375 +msgid "" +"HTTP Accept header to specify the MIME type of the expected output of the" +" server. Empty by default. (added in GDAL 3.5.1)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:383 +msgid "" +"Skip SSL certificate verification. May be needed if server is using a " +"self signed certificate (optional, defaults to false, but set to true in " +"autogenerated XML)." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:390 +msgid "<Referer>http://example.foo/</Ref erer>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:393 +msgid "<ZeroBlockHttpCodes>204,404</Zero BlockHttpCodes>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:393 +msgid "" +"Comma separated list of HTTP response codes that will be interpreted as a" +" 0 filled image (i.e. black for 3 bands, and transparent for 4 bands) " +"instead of aborting the request. (optional, defaults to non set, but set " +"to 204,404 in autogenerated XML)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:403 +msgid "<ZeroBlockOnServerException>true< /ZeroBlockOnServerException>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:403 +msgid "" +"Whether to treat a Service Exception returned by the server as a 0 filled" +" image instead of aborting the request. (optional, defaults to false, but" +" set to true in autogenerated XML)" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:410 +msgid "</GDAL_WMTS>" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:415 +msgid "" +"Starting with GDAL 2.3, additional HTTP headers can be sent by setting " +"the :config:`GDAL_HTTP_HEADER_FILE` configuration option to point to a " +"filename of a text file with “key: value” HTTP headers." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:420 +msgid "GetFeatureInfo request" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:422 +msgid "" +"WMTS layers can be queried (through a GetFeatureInfo request) with the " +"gdallocationinfo utility, or with a GetMetadataItem(\"Pixel_iCol_iLine\"," +" \"LocationInfo\") call on a band object." +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:431 +msgid "Generation of WMTS service description XML file" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:433 +msgid "" +"The WMTS service description XML file can be generated manually, or " +"created as the output of the CreateCopy() operation of the WMTS driver, " +"only if the source dataset is itself a WMTS dataset. Said otherwise, you " +"can use gdal_translate with as source dataset any of the above syntax " +"mentioned in \"Open syntax\" and as output an XML file. For example:" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:443 +msgid "generates the following file:" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:471 +msgid "`OGC WMTS Standard <http://www.opengeospatial.org/standards/wmts>`__" +msgstr "" + +#: ../../source/drivers/raster/wmts.rst:472 +msgid ":ref:`raster.wms` driver page." +msgstr "" + +#: ../../source/drivers/raster/xpm.rst:5 +msgid "XPM -- X11 Pixmap" +msgstr "" + +#: ../../source/drivers/raster/xpm.rst:7 +msgid "XPM" +msgstr "" + +#: ../../source/drivers/raster/xpm.rst:11 +msgid "" +"GDAL includes support for reading and writing XPM (X11 Pixmap Format) " +"image files. These are colormapped one band images primarily used for " +"simple graphics purposes in X11 applications. It has been incorporated in" +" GDAL primarily to ease translation of GDAL images into a form usable " +"with the GTK toolkit." +msgstr "" + +#: ../../source/drivers/raster/xpm.rst:17 +msgid "" +"The XPM support does not support georeferencing (not available from XPM " +"files) nor does it support XPM files with more than one character per " +"pixel. New XPM files must be colormapped or greyscale, and colortables " +"will be reduced to about 70 colors automatically." +msgstr "" + +#: ../../source/drivers/raster/xpm.rst:22 +msgid "NOTE: Implemented as :source_file:`frmts/xpm/xpmdataset.cpp`." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:5 +msgid "XYZ -- ASCII Gridded XYZ" +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:7 +msgid "XYZ" +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:11 +msgid "" +"GDAL supports reading and writing ASCII **gridded** XYZ raster datasets " +"(i.e. ungridded XYZ, LIDAR XYZ etc. must be opened by other means. See " +"the documentation of the :ref:`gdal_grid` utility)." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:15 +msgid "" +"Those datasets are ASCII files with (at least) 3 columns, each line " +"containing the X and Y coordinates of the center of the cell and the " +"value of the cell. (Note the XYZ driver only uses the first band of the " +"dataset. I.e., columns beyond the third are ignored.)" +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:20 +msgid "The spacing between each cell must be constant." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:22 +msgid "The following data organization are supported :" +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:24 +msgid "" +"Cells with same Y coordinates must be placed on consecutive lines. For a " +"same Y coordinate value, the lines in the dataset must be organized by " +"increasing X values. The value of the Y coordinate can increase or " +"decrease however." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:29 +msgid "" +"or, starting with GDAL 3.2.1, cells with same X coordinates must be " +"placed on consecutive lines. For a same X coordinate value, the columns " +"must be organized by increasing or decreasing Y values. For that " +"organization, no missing value is supported, and the whole dataset will " +"be ingested into memory (thus the driver will limit to 100 million " +"points)." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:35 +msgid "" +"The supported column separators are space, comma, semicolon and " +"tabulations." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:37 +msgid "" +"The driver tries to autodetect an header line and will look for 'x', " +"'lon' or 'east' names to detect the index of the X column, 'y', 'lat' or " +"'north' for the Y column and 'z', 'alt' or 'height' for the Z column. If " +"no header is present or one of the column could not be identified in the " +"header, the X, Y and Z columns (in that order) are assumed to be the " +"first 3 columns of each line. The open option :oo:`COLUMN_ORDER` " +"overrides these assumptions (except on 'AUTO')." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:45 +msgid "" +"The opening of a big dataset can be slow as the driver must scan the " +"whole file to determine the dataset size and spatial resolution. The " +"driver will autodetect the data type among Byte, Int16, Int32 or Float32." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:-1 +msgid "" +"COLUMN_ORDER=[AUTO/XYZ/YXZ]: (GDAL >= 3.10) Defaults to AUTO. Specifies" +" the order of the columns. It overrides the header." +msgstr "" + +#: ../../source/drivers/raster/xyz.rst:105 +msgid "Documentation of :ref:`gdal_grid`" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:11 +msgid "" +"Built-in by default, but liblz4, libxz (lzma), libzstd and libblosc " +"strongly recommended to get all compressors" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:14 +msgid "" +"Zarr is a format for the storage of chunked, compressed, N-dimensional " +"arrays. This format is supported for read and write access, and using the" +" traditional 2D raster API or the newer multidimensional API" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:18 +msgid "" +"The driver supports the Zarr V2 specification, and has experimental " +"support for the in-progress Zarr V3 specification." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:23 +msgid "" +"The current implementation of Zarr V3 before GDAL 3.8 is incompatible " +"with the latest evolutions of the Zarr V3 specification. GDAL 3.8 is " +"compatible with the Zarr V3 specification at date 2023-May-7, and is not " +"interoperable with Zarr V3 datasets produced by earlier GDAL versions." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:29 +msgid "" +"Local and cloud storage (see :ref:`virtual_file_systems`) are supported " +"in read and write." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:43 +msgid "Concepts" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:45 +msgid "" +"A Zarr dataset is made of a hierarchy of nodes, with intermediate nodes " +"being groups (:cpp:class:`GDALGroup`), and leafs being arrays " +"(:cpp:class:`GDALMDArray`)." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:49 +msgid "Dataset name" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:51 +msgid "" +"For Zarr V2, the dataset name recognized by the Open() method of the " +"driver is a directory that contains a :file:`.zgroup` file, a " +":file:`.zarray` file or a :file:`.zmetadata` file (consolidated " +"metadata). For faster exploration, the driver will use consolidated " +"metadata by default when found." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:56 +msgid "" +"For Zarr V3, the dataset name recognized by the Open() method of the " +"driver is a directory that contains a :file:`zarr.json` file (root of the" +" dataset)." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:59 +msgid "" +"For datasets on file systems where file listing is not reliable, as often" +" with /vsicurl/, it is also possible to prefix the directory name with " +"``ZARR:``, and it is necessary to surround the /vsicurl/-prefixed URL " +"with double quotes. e.g `ZARR:\"/vsicurl/https://example.org/foo.zarr\"`." +" Note that when passing such string in a command line shell, extra " +"quoting might be necessary to preserve the double-quoting." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:66 +msgid "" +"For example with a Bash shell, the whole connection string needs to be " +"surrounded with single-quote characters:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:75 +msgid "Compression methods" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:77 +msgid "" +"Compression methods available depend on how GDAL is built, and `libblosc " +"<https://github.com/Blosc/c-blosc>`__ too." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:80 +msgid "A full-feature build will show:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:92 +msgid "" +"For specific uses, it is also possible to register at run-time extra " +"compressors and decompressors with :cpp:func:`CPLRegisterCompressor` and " +":cpp:func:`CPLRegisterDecompressor`." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:96 +msgid "XArray _ARRAY_DIMENSIONS" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:98 +msgid "" +"The driver support the ``_ARRAY_DIMENSIONS`` special attribute used by " +"`XArray " +"<http://xarray.pydata.org/en/stable/generated/xarray.open_zarr.html>`__ " +"to store the dimension names of an array." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:103 +msgid "NCZarr extensions" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:105 +msgid "" +"The driver support the `NCZarr v2 " +"<https://www.unidata.ucar.edu/software/netcdf/documentation/NUG/nczarr_head.html>`__" +" extensions of storing the dimension names of an array (read-only)" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:110 +msgid "SRS encoding" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:112 +msgid "" +"The Zarr specification has no provision for spatial reference system " +"encoding. GDAL uses a ``_CRS`` attribute that is a dictionary that may " +"contain one or several of the following keys: ``url`` (using a OGC CRS " +"URL), ``wkt`` (WKT:2019 used by default on writing, WKT1 also supported " +"on reading.), ``projjson``. On reading, it will use ``url`` by default, " +"if not found will fallback to ``wkt`` and then ``projjson``." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:247 +msgid "Particularities of the classic raster API" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:249 +msgid "" +"If the Zarr dataset contains one single array with 2 dimensions, it will " +"be exposed as a regular GDALDataset when using the classic raster API. If" +" the dataset contains more than one such single array, or arrays with 3 " +"or more dimensions, the driver will list subdatasets to access each array" +" and/or 2D slices within arrays with 3 or more dimensions." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:258 +msgid "The following dataset open options are available:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:320 +msgid "Multi-threaded caching" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:322 +msgid "" +"The driver implements the :cpp:func:`GDALMDArray::AdviseRead` method. " +"This proceed to multi-threaded decoding of the tiles that intersect the " +"area of interest specified. A sufficient cache size must be specified. " +"The call is blocking." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:327 +msgid "The options that can be passed to the methods are:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:329 +msgid "" +"**CACHE_SIZE=value_in_byte**: Maximum RAM to use, expressed in number of " +"bytes. If not specified, half of the remaining GDAL block cache size will" +" be used. Note: the caching mechanism of Zarr array will not update this " +"remaining block cache size." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:334 +msgid "" +"**NUM_THREADS=integer or ALL_CPUS**: Number of threads to use in " +"parallel. If not specified, the :config:`GDAL_NUM_THREADS` configuration " +"option will be taken into account." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:341 +msgid "" +"The following options are creation options of the classic raster API, or " +"array-level creation options for the multidimensional API (must be " +"prefixed with ``ARRAY:`` using :program:`gdalmdimtranslate`):" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:465 +msgid "" +"The following options are creation options of the classic raster API, or " +"dataset-level creation options for the multidimensional API :" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:479 +msgid "The following options are creation options of the classic raster API only:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:513 +msgid "Get information on the dataset using the multidimensional tools:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:520 +msgid "Convert a netCDF file to ZARR using the multidimensional tools:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:527 +msgid "" +"Convert a 2D slice (the one at index 0 of the non-2D dimension) of a 3D " +"array to GeoTIFF:" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:535 +msgid "" +"The single quoting around the connection string is specific to the Bash " +"shell to make sure that the double quoting is preserved." +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:542 +msgid "" +"`Zarr format and its Python implementation " +"<https://zarr.readthedocs.io/en/stable/>`__" +msgstr "" + +#: ../../source/drivers/raster/zarr.rst:543 +msgid "" +"`(In progress) Zarr V3 specification <https://zarr-" +"specs.readthedocs.io/en/core-protocol-v3.0-dev/>`__" +msgstr "" + +#: ../../source/drivers/raster/zmap.rst:5 +msgid "ZMap -- ZMap Plus Grid" +msgstr "" + +#: ../../source/drivers/raster/zmap.rst:7 +msgid "ZMAP" +msgstr "" + +#: ../../source/drivers/raster/zmap.rst:11 +msgid "" +"Supported for read access and creation. This format is an ASCII " +"interchange format for gridded data in an ASCII line format for transport" +" and storage. It is commonly used in applications in the Oil and Gas " +"Exploration field." +msgstr "" + +#: ../../source/drivers/raster/zmap.rst:16 +msgid "" +"By default, files are interpreted and written according to the " +"PIXEL_IS_AREA convention. If you define the ZMAP_PIXEL_IS_POINT " +"configuration option to TRUE, the PIXEL_IS_POINT convention will be " +"followed to interpret/write the file (the georeferenced values in the " +"header of the file will then be considered as the coordinate of the " +"center of the pixels). Note that in that case, GDAL will report the " +"extent with its usual PIXEL_IS_AREA convention (the coordinates of the " +"topleft corner as reported by GDAL will be a half-pixel at the top and " +"left of the values that appear in the file)." +msgstr "" + +#: ../../source/drivers/raster/zmap.rst:26 +msgid "" +"Informal specification given in this `GDAL-dev mailing list thread " +"<http://lists.osgeo.org/pipermail/gdal-dev/2011-June/029173.html>`__" +msgstr "" + +#: ../../source/drivers/raster/zmap.rst:29 +msgid "NOTE: Implemented as :source_file:`frmts/zmap/zmapdataset.cpp`." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:5 +#: ../../source/drivers/vector/amigocloud.rst:9 +#: ../../source/drivers/vector/driver_summary.rst:17 +msgid "AmigoCloud" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:13 +msgid "" +"This driver can connect to the AmigoCloud API services. GDAL/OGR must be " +"built with Curl support in order for the AmigoCloud driver to be " +"compiled." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:16 +#: ../../source/drivers/vector/carto.rst:14 +msgid "The driver supports read and write operations." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:30 +msgid "The minimal syntax to open a AmigoCloud datasource is:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:39 +msgid "" +"**datasets=dataset_id1[,dataset_id2, ..]**: A list of AmigoCloud dataset " +"IDs. This is necessary when you need to access a particular AmigoCloud " +"dataset." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:43 +#: ../../source/drivers/vector/carto.rst:40 +msgid "If several parameters are specified, they must be separated by a space." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:45 +msgid "" +"If no datset_id is provided, the driver will print list of available " +"datasets for given project." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:48 +msgid "For example: **\"AmigoCloud:1234 datasets\"**" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:61 +msgid "All the access permissions are defined by AmigoCloud backend." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:63 +msgid "" +"Authenticated access is obtained by specifying the API key given in the " +"AmigoCloud dashboard web interface. It is specified with the " +":config:`AMIGOCLOUD_API_KEY` configuration option." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:68 +#: ../../source/drivers/vector/carto.rst:53 +#: ../../source/drivers/vector/eeda.rst:154 +#: ../../source/drivers/vector/geojson.rst:135 +#: ../../source/drivers/vector/libkml.rst:910 +#: ../../source/drivers/vector/netcdf.rst:187 +#: ../../source/drivers/vector/ngw.rst:122 +#: ../../source/drivers/vector/plscenes_data_v1.rst:144 +msgid "Geometry" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:70 +msgid "" +"The OGR driver will report as many geometry fields as available in the " +"layer, following RFC 41." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:74 +#: ../../source/drivers/vector/carto.rst:59 +#: ../../source/drivers/vector/csw.rst:30 +#: ../../source/drivers/vector/eeda.rst:160 +#: ../../source/drivers/vector/elasticsearch.rst:186 +#: ../../source/drivers/vector/mongodbv3.rst:152 +#: ../../source/drivers/vector/oapif.rst:51 +#: ../../source/drivers/vector/plscenes_data_v1.rst:150 +#: ../../source/drivers/vector/tiledb.rst:50 +#: ../../source/drivers/vector/wfs.rst:156 +msgid "Filtering" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:76 +msgid "" +"The driver will forward any spatial filter set with " +":cpp:func:`OGRLayer::SetSpatialFilter` to the server. It also makes the " +"same for attribute filters set with " +":cpp:func:`OGRLayer::SetAttributeFilter`." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:81 +#: ../../source/drivers/vector/carto.rst:73 +#: ../../source/drivers/vector/elasticsearch.rst:426 +#: ../../source/drivers/vector/gpsbabel.rst:74 +#: ../../source/drivers/vector/mapml.rst:44 +#: ../../source/drivers/vector/mongodbv3.rst:222 +#: ../../source/drivers/vector/ngw.rst:158 +msgid "Write support" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:83 +msgid "Dataset creation and deletion is possible." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:85 +#: ../../source/drivers/vector/carto.rst:77 +#: ../../source/drivers/vector/elasticsearch.rst:430 +#: ../../source/drivers/vector/mongodbv3.rst:226 +#: ../../source/drivers/vector/wfs.rst:219 +msgid "" +"Write support is only enabled when the datasource is opened in update " +"mode." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:88 +msgid "" +"The mapping between the operations of the AmigoCloud service and the OGR " +"concepts is the following :" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:91 +#: ../../source/drivers/vector/carto.rst:83 +msgid ":cpp:func:`OGRFeature::CreateFeature` <==> ``INSERT`` operation" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:92 +#: ../../source/drivers/vector/carto.rst:84 +msgid ":cpp:func:`OGRFeature::SetFeature` <==> ``UPDATE`` operation" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:93 +#: ../../source/drivers/vector/carto.rst:85 +msgid ":cpp:func:`OGRFeature::DeleteFeature` <==> ``DELETE`` operation" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:94 +#: ../../source/drivers/vector/carto.rst:86 +msgid ":cpp:func:`OGRDataSource::CreateLayer` <==> ``CREATE TABLE`` operation" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:95 +msgid ":cpp:func:`OGRDataSource::DeleteLayer` <==> `DROP TABLE` operation" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:97 +msgid "" +"When inserting a new feature with CreateFeature(), and if the command is " +"successful, OGR will fetch the returned amigo_id (GUID) and use hash " +"value of it as the OGR FID." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:101 +#: ../../source/drivers/vector/carto.rst:93 +#: ../../source/drivers/vector/wfs.rst:250 +msgid "" +"The above operations are by default issued to the server synchronously " +"with the OGR API call. This however can cause performance penalties when " +"issuing a lot of commands due to many client/server exchanges." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:142 +msgid "Different ways to provide AmigoCloud API token:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:155 +msgid "Show list of datasets." +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:166 +msgid "Accessing data from a list of datasets:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:172 +#: ../../source/drivers/vector/carto.rst:217 +msgid "Creating and populating a table from a shapefile:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:178 +msgid "Append the data to an existing table (dataset id: 12345) from a shapefile:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:190 +msgid "" +"Overwriting the data of an existing table (dataset id: 12345) with data " +"from a shapefile:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:197 +msgid "" +"Delete existing dataset (dataset id: 12345) and create a new one with " +"data from a shapefile:" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:204 +msgid "" +"Overwriting the data of an existing table (dataset id: 12345) with data " +"from a shapefile. Filter the only the records with values of the field " +"\"visited_on\" after 2017-08-20" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:215 +msgid "" +"`AmigoCloud API Token management " +"<https://www.amigocloud.com/accounts/tokens>`__" +msgstr "" + +#: ../../source/drivers/vector/amigocloud.rst:216 +msgid "`AmigoCloud API Browser <https://www.amigocloud.com/api/v1/>`__" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:4 +#: ../../source/drivers/vector/driver_summary.rst:22 +msgid "(Geo)Arrow IPC File Format / Stream" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:8 +msgid "Arrow" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:10 +#: ../../source/drivers/vector/driver_summary.rst:25 +msgid "Apache Arrow C++ library" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:12 +msgid "" +"The Arrow IPC File Format (Feather) is a portable file format for storing" +" Arrow tables or data frames (from languages like Python or R) that " +"utilizes the Arrow IPC format internally." +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:16 +msgid "The driver supports the 2 variants of the format:" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:18 +msgid "" +"File or Random Access format, also known as Feather: for serializing a " +"fixed number of record batches. Random access is required to read such " +"files, but they can be generated using a streaming-only capable file. The" +" recommended extension for such file is ``.arrow``" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:23 +msgid "" +"Streaming IPC format: for sending an arbitrary length sequence of record " +"batches. The format must generally be processed from start to end, and " +"does not require random access. That format is not generally materialized" +" as a file. If it is, the recommended extension is ``.arrows`` (with a " +"trailing s). But the driver can support regular files as well as the " +"/vsistdin/ and /vsistdout/ streaming files. On opening, it might " +"difficult for the driver to detect that the content is specifically a " +"Arrow IPC stream, especially if the extension is not ``.arrows``, and the" +" metadata section is large. Prefixing the filename with " +"``ARROW_IPC_STREAM:`` (e.g \"ARROW_IPC_STREAM:/vsistdin/\") will cause " +"the driver to unconditionally open the file as a streaming IPC format. " +"Alternatively, starting with GDAL 3.10, specifying the ``-if ARROW`` " +"option to command line utilities accepting it, or ``ARROW`` as the only " +"value of the ``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also " +"forces the driver to recognize the passed filename." +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:39 +msgid "" +"This driver also supports geometry columns using the GeoArrow " +"specification." +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:41 +msgid "" +"The driver should be considered experimental as the GeoArrow " +"specification is not finalized yet." +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:55 +#: ../../source/drivers/vector/parquet.rst:59 +msgid "The driver supports creating only a single layer in a dataset." +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:60 +#: ../../source/drivers/vector/carto.rst:140 +#: ../../source/drivers/vector/csv.rst:429 +#: ../../source/drivers/vector/dgnv8.rst:206 +#: ../../source/drivers/vector/filegdb.rst:126 +#: ../../source/drivers/vector/flatgeobuf.rst:62 +#: ../../source/drivers/vector/geoconcept.rst:155 +#: ../../source/drivers/vector/geojsonseq.rst:66 +#: ../../source/drivers/vector/gpx.rst:231 +#: ../../source/drivers/vector/hana.rst:181 +#: ../../source/drivers/vector/jsonfg.rst:132 +#: ../../source/drivers/vector/mitab.rst:145 +#: ../../source/drivers/vector/mongodbv3.rst:236 +#: ../../source/drivers/vector/mssqlspatial.rst:108 +#: ../../source/drivers/vector/mvt.rst:402 +#: ../../source/drivers/vector/mysql.rst:106 +#: ../../source/drivers/vector/oci.rst:138 +#: ../../source/drivers/vector/openfilegdb.rst:123 +#: ../../source/drivers/vector/parquet.rst:64 +#: ../../source/drivers/vector/pg.rst:245 +#: ../../source/drivers/vector/pgdump.rst:53 +#: ../../source/drivers/vector/pmtiles.rst:222 +#: ../../source/drivers/vector/selafin.rst:351 +#: ../../source/drivers/vector/shapefile.rst:348 +#: ../../source/drivers/vector/sqlite.rst:325 +msgid "" +"|about-layer-creation-options| The following layer creation options are " +"supported:" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:111 +#: ../../source/drivers/vector/parquet.rst:227 +msgid "Conda-forge package" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:113 +#: ../../source/drivers/vector/parquet.rst:229 +msgid "" +"The driver can be installed as a plugin for the ``libgdal`` conda-forge " +"package with:" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:123 +msgid "" +"`Feather File Format " +"<https://arrow.apache.org/docs/python/feather.html>`__" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:125 +msgid "`GeoArrow specification <https://github.com/geopandas/geo-arrow-spec>`__" +msgstr "" + +#: ../../source/drivers/vector/arrow.rst:127 +msgid "Related driver: :ref:`Parquet driver <vector.parquet>`" +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:5 +#: ../../source/drivers/vector/driver_summary.rst:27 +msgid "Arc/Info Binary Coverage" +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:7 +msgid "AVCBIN" +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:11 +msgid "" +"Arc/Info Binary Coverages (eg. Arc/Info V7 and earlier) are supported by " +"OGR for read access." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:14 +#: ../../source/drivers/vector/avce00.rst:14 +msgid "" +"The label, arc, polygon, centroid, region and text sections of a coverage" +" are all supported as layers. Attributes from INFO are appended to " +"labels, arcs, polygons or region where appropriate. When available the " +"projection information is read and translated. Polygon geometries are " +"collected for polygon and region layers from the composing arcs." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:20 +#: ../../source/drivers/vector/avce00.rst:20 +msgid "" +"Text sections are represented as point layers. Display height is " +"preserved in the HEIGHT attribute field; however, other information about" +" text orientation is discarded." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:24 +#: ../../source/drivers/vector/avce00.rst:24 +msgid "" +"Info tables associated with a coverage, but not specifically named to be " +"attached to one of the existing geometric layers is currently not " +"accessible through OGR. Note that info tables are stored in an 'info' " +"directory at the same level as the coverage directory. If this is " +"inaccessible or corrupt no info attributes will be appended to coverage " +"layers, but the geometry should still be accessible." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:31 +msgid "" +"If the directory contains files with names like w001001.adf then the " +"coverage is a :ref:`grid coverage <raster.aig>` suitable to read with " +"GDAL, not a vector coverage supported by OGR." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:35 +#: ../../source/drivers/vector/avce00.rst:31 +msgid "The layers are named as follows:" +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:37 +#: ../../source/drivers/vector/avce00.rst:33 +msgid "" +"A label layer (polygon labels, or free standing points) is named LAB if " +"present." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:39 +#: ../../source/drivers/vector/avce00.rst:35 +msgid "A centroid layer (polygon centroids) is named CNT if present." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:40 +#: ../../source/drivers/vector/avce00.rst:36 +msgid "An arc (line) layer is named ARC if present." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:41 +#: ../../source/drivers/vector/avce00.rst:37 +msgid "A polygon layer is named \"PAL\" if present." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:42 +#: ../../source/drivers/vector/avce00.rst:38 +msgid "A text section is named according to the section subclass." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:43 +#: ../../source/drivers/vector/avce00.rst:39 +msgid "A region subclass is named according to the subclass name." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:45 +msgid "" +"The Arc/Info binary coverage driver attempts to optimize spatial queries " +"but due to the lack of a spatial index this is just accomplished by " +"minimizing processing for features not within the spatial window." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:49 +msgid "" +"Random (by FID) reads of arcs, and polygons is supported it may not be " +"supported for other feature types." +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:62 +#: ../../source/drivers/vector/avce00.rst:55 +msgid "`AVCE00 Library Page <http://avce00.maptools.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/avcbin.rst:63 +msgid ":ref:`AVCE00 OGR Driver (.E00) <vector.avce00>`" +msgstr "" + +#: ../../source/drivers/vector/avce00.rst:5 +#: ../../source/drivers/vector/driver_summary.rst:32 +msgid "Arc/Info E00 (ASCII) Coverage" +msgstr "" + +#: ../../source/drivers/vector/avce00.rst:7 +msgid "AVCE00" +msgstr "" + +#: ../../source/drivers/vector/avce00.rst:11 +msgid "" +"Arc/Info E00 Coverages (eg. Arc/Info V7 and earlier) are supported by OGR" +" for read access." +msgstr "" + +#: ../../source/drivers/vector/avce00.rst:41 +msgid "" +"Random (by FID) reads of arcs, and polygons is supported it may not be " +"supported for other feature types. Random access to E00 files is " +"generally slow." +msgstr "" + +#: ../../source/drivers/vector/avce00.rst:56 +msgid ":ref:`AVCBin OGR Driver (Binary Coverage) <vector.avcbin>`" +msgstr "" + +#: ../../source/drivers/vector/cad.rst:5 +msgid "CAD -- AutoCAD DWG" +msgstr "" + +#: ../../source/drivers/vector/cad.rst:11 +msgid "" +"OGR DWG support is based on libopencad, so the list of supported DWG " +"(DXF) versions can be seen in libopencad documentation. All drawing " +"entities are separated into layers as they are in DWG file, not in 1 " +"layer as DXF Driver does." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:16 +#: ../../source/drivers/vector/dwg.rst:17 +msgid "" +"DWG files are considered to have no georeferencing information through " +"OGR. Features will all have the following generic attributes:" +msgstr "" + +#: ../../source/drivers/vector/cad.rst:19 +msgid "CADGeometry: CAD Type of the presented geometry." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:20 +msgid "" +"Thickness: Thickness of the object drawing units (if it is not supported " +"by this type, it is set to 0.0)." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:22 +msgid "Color (RGB): IntegerList contains R,G,B components of the color." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:23 +#: ../../source/drivers/vector/dwg.rst:23 +msgid "" +"ExtendedEntity: Where available, extended entity attributes all appended " +"to form a single text attribute." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:34 +#: ../../source/drivers/vector/dgn.rst:42 +#: ../../source/drivers/vector/dgnv8.rst:40 +msgid "Supported Elements" +msgstr "" + +#: ../../source/drivers/vector/cad.rst:36 +#: ../../source/drivers/vector/dgn.rst:44 +msgid "The following element types are supported:" +msgstr "" + +#: ../../source/drivers/vector/cad.rst:38 +msgid "POINT: Produces a simple point geometry feature." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:39 +msgid "" +"LINE: Translated as a LINESTRING. Rounded polylines (those with their " +"vertices' budge attributes set) will be tessellated. Single-vertex " +"polylines are translated to POINT." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:42 +msgid "CIRCLE, ARC: Translated as a CIRCULARSTRING." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:43 +msgid "3DFACE: Translated as POLYGON." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:45 +msgid "The driver is read-only." +msgstr "" + +#: ../../source/drivers/vector/cad.rst:50 +msgid "" +"`ODA DWG Reference " +"<https://www.opendesign.com/files/guestdownloads/OpenDesign_Specification_for_.dwg_files.pdf>`__" +msgstr "" + +#: ../../source/drivers/vector/cad.rst:51 +msgid "`Libopencad repository <https://github.com/nextgis-borsch/lib_opencad>`__" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:5 +#: ../../source/drivers/vector/driver_summary.rst:42 +msgid "Carto" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:7 +msgid "CARTO" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:11 +msgid "" +"This driver can connect to the services implementing the Carto API. " +"GDAL/OGR must be built with Curl support in order for the Carto driver to" +" be compiled." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:26 +msgid "The minimal syntax to open a Carto datasource is :" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:32 +msgid "" +"For single-user accounts, connection name is the account name. For multi-" +"user accounts, connection_name must be the user name, not the account " +"name. Additional optional parameters can be specified after the ':' sign." +" Currently the following one is supported:" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:37 +msgid "" +"**tables=table_name1[,table_name2]\\***: A list of table names. This is " +"necessary when you need to access to public tables for example." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:45 +msgid "" +"Most operations, in particular write operations, require an authenticated" +" access. The only exception is read-only access to public tables." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:48 +msgid "" +"Authenticated access is obtained by specifying the API key given in the " +"management interface of the Carto service. It is specified with the " +"CARTO_API_KEY configuration option." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:55 +msgid "" +"The OGR driver will report as many geometry fields as available in the " +"layer (except the 'the_geom_webmercator' field), following RFC 41." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:61 +msgid "" +"The driver will forward any spatial filter set with " +":cpp:func:`OGRLayer::SetSpatialFilter` to the server. It also makes the " +"same for attribute filters set with :cpp:func:`SetAttributeFilter`." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:67 +#: ../../source/drivers/vector/eeda.rst:168 +#: ../../source/drivers/vector/elasticsearch.rst:209 +#: ../../source/drivers/vector/mongodbv3.rst:165 +#: ../../source/drivers/vector/ngw.rst:150 +#: ../../source/drivers/vector/plscenes_data_v1.rst:159 +msgid "Paging" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:69 +msgid "" +"Features are retrieved from the server by chunks of 500 by default. This " +"number can be altered with the :config:`CARTO_PAGE_SIZE` configuration " +"option." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:75 +msgid "Table creation and deletion is possible." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:80 +msgid "" +"The mapping between the operations of the Carto service and the OGR " +"concepts is the following :" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:87 +msgid ":cpp:func:`OGRDataSource::DeleteLayer` <==> ``DROP TABLE`` operation" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:89 +msgid "" +"When inserting a new feature with :cpp:func:`OGRFeature::CreateFeature`, " +"and if the command is successful, OGR will fetch the returned rowid and " +"use it as the OGR FID." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:97 +msgid "" +"So, on a newly created layer, the ``INSERT`` of " +":cpp:func:`OGRFeature::CreateFeature` operations are grouped together in " +"chunks until they reach 15 MB (can be changed with the " +":config:`CARTO_MAX_CHUNK_SIZE` configuration option, with a value in MB)," +" at which point they are transferred to the server. By setting " +":config:`CARTO_MAX_CHUNK_SIZE` to 0, immediate transfer occurs." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:105 +msgid "" +"Don't use :cpp:func:`OGRDataSource::DeleteLayer` and " +":cpp:func:`OGRDataSource::CreateLayer` to overwrite a table. Instead only" +" call :cpp:func:`OGRDataSource::CreateLayer` with OVERWRITE=YES. This " +"will avoid CARTO deleting maps that depend on this table" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:111 +#: ../../source/drivers/vector/geopackage_aspatial.rst:35 +#: ../../source/drivers/vector/gpkg.rst:60 +msgid "SQL" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:113 +msgid "" +"SQL commands provided to the :cpp:func:`OGRDataSource::ExecuteSQL` call " +"are executed on the server side, unless the OGRSQL dialect is specified. " +"You can use the full power of PostgreSQL + PostGIS SQL capabilities." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:120 +msgid "The following open options are available: |about-open-options|" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:164 +msgid "" +"**SRS**: Output SRS must be EPSG:4326. You can use ``-a_srs`` or " +"``-t_srs`` to assign or transform to 4326 before importing." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:166 +msgid "" +"**Geometry type**: Must be different than NONE. You can set to something " +"generic with ``-nlt GEOMETRY``." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:211 +msgid "Accessing data from a public table:" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:223 +msgid "" +"Creating and populating a table from a CSV containing geometries on " +"EPSG:4326:" +msgstr "" + +#: ../../source/drivers/vector/carto.rst:231 +msgid "" +"The ``-a_srs`` and ``-nlt`` must be provided to CARTODBFY since the " +"information isn't extracted from the CSV." +msgstr "" + +#: ../../source/drivers/vector/carto.rst:237 +msgid "`Carto API overview <https://carto.com/docs/>`__" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:4 +#: ../../source/drivers/vector/driver_summary.rst:47 +msgid "Comma Separated Value (.csv)" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:6 +msgid "CSV" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:10 +msgid "" +"OGR supports reading and writing primarily non-spatial tabular data " +"stored in text CSV files. CSV files are a common interchange format " +"between software packages supporting tabular data and are also easily " +"produced manually with a text editor or with end-user written scripts or " +"programs." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:16 +msgid "" +"The datasource name may be either a single CSV file or point to a " +"directory. For a directory to be recognised as a .csv datasource at least" +" half the files in the directory need to have the extension .csv. One " +"layer (table) is produced from each .csv file accessed. Starting with " +"GDAL 3.7, pipe separated values files with a \".psv\" extension are also " +"recognized." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:24 +msgid "" +"For files structured as CSV, but not ending with the \".csv\" extension, " +"the 'CSV:' prefix can be added before the filename to force loading by " +"the CSV driver." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:28 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if CSV`` option to command " +"line utilities accepting it, or ``CSV`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed filename, without the ``CSV:`` prefix." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:33 +msgid "" +"The OGR CSV driver supports reading and writing. Because the CSV format " +"has variable length text lines, reading is done sequentially. Reading " +"features in random order will generally be very slow. OGR CSV layer might" +" have a coordinate system stored in a .prj file (see GeoCSV " +"specification). When reading a field named \"WKT\" is assumed to contain " +"WKT geometry, but also is treated as a regular field. The OGR CSV driver " +"returns all attribute columns as string data types if no field type " +"information file (with .csvt extension) is available." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:42 +msgid "" +"Limited type recognition can be done for Integer, Real, String, Date " +"(YYYY-MM-DD), Time (HH:MM:SS+nn), DateTime (YYYY-MM-DD HH:MM:SS+nn) " +"columns through a descriptive file with the same name as the CSV file, " +"but a .csvt extension. In a single line the types for each column have to" +" be listed with double quotes and be comma separated (e.g., " +"\"Integer\",\"String\"). It is also possible to specify explicitly the " +"width and precision of each column, e.g. " +"\"Integer(5)\",\"Real(10.7)\",\"String(15)\". The driver will then use " +"these types as specified for the csv columns. Subtypes can be passed " +"between parenthesis, such as \"Integer(Boolean)\", \"Integer(Int16)\" and" +" \"Real(Float32)\". Starting with GDAL 2.1, accordingly with the `GeoCSV " +"specification <http://giswiki.hsr.ch/GeoCSV>`__, the \"CoordX\" or " +"\"Point(X)\" type can be used to specify a column with longitude/easting " +"values, \"CoordY\" or \"Point(Y)\" for latitude/northing values and " +"\"WKT\" for geometries encoded in WKT" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:59 +msgid "" +"Starting with GDAL 2.2, the \"JSonStringList\", \"JSonIntegerList\", " +"\"JSonInteger64List\" and \"JSonRealList\" types can be used in .csvt to " +"map to the corresponding OGR StringList, IntegerList, Integer64List and " +"RealList types. The field values are then encoded as JSON arrays, with " +"proper CSV escaping." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:65 +msgid "" +"Automatic field type guessing can also be done if specifying the open " +"options described in the below \"Open options\" section." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:81 +msgid "" +"CSV files have one line for each feature (record) in the layer (table). " +"The attribute field values are separated by commas. At least two fields " +"per line must be present. Lines may be terminated by a DOS (CR/LF) or " +"Unix (LF) style line terminators. Each record should have the same number" +" of fields. The driver will also accept a semicolon, a tabulation, a " +"pipe, or a space character as field separator. Starting with GDAL 3.8, " +"the autodection will select the separator with the most occurrences if " +"there are several candidates on the first line of the CSV file (and warn" +" about that). The :oo:`SEPARATOR` open option may also be set to define " +"the desired separator. Previous versions select comma by default when " +"there are several potential separators." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:94 +msgid "" +"Complex attribute values (such as those containing commas, quotes or " +"newlines) may be placed in double quotes. Any occurrences of double " +"quotes within the quoted string should be doubled up to \"escape\" them." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:98 +msgid "" +"By default, the driver attempts to treat the first line of the file as a " +"list of field names for all the fields. However, if one or more of the " +"names is all numeric it is assumed that the first line is actually data " +"values and dummy field names are generated internally (field_1 through " +"field_n) and the first record is treated as a feature. Numeric values are" +" treated as field names if they are enclosed in double quotes. Starting " +"with GDAL 2.1, this behavior can be modified via the HEADERS open option." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:107 +msgid "" +"All CSV files are treated as UTF-8 encoded. A Byte Order Mark (BOM) at " +"the beginning of the file will be parsed correctly. The layer creation " +"option :lco:`WRITE_BOM` can be used to create a file with a Byte Order " +"Mark, which can improve compatibility with some software (particularly " +"Excel)." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:113 +msgid "Example (employee.csv):" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:121 +msgid "" +"Note that the Comments value for the first data record is placed in " +"double quotes because the value contains quotes, and those quotes have to" +" be doubled up so we know we haven't reached the end of the quoted string" +" yet." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:126 +msgid "" +"Many variations of textual input are sometimes called Comma Separated " +"Value files, including files without commas, but fixed column widths, " +"those using tabs as separators or those with other auxiliary data " +"defining field types or structure. This driver does not attempt to " +"support all such files, but instead to support simple .csv files that can" +" be auto-recognised. Scripts or other mechanisms can generally be used to" +" convert other variations into a form that is compatible with the OGR CSV" +" driver." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:136 +msgid "Reading CSV containing spatial information" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:139 +msgid "Building point geometries" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:141 +#: ../../source/drivers/vector/csv.rst:227 +msgid "Consider the following CSV file (test.csv):" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:150 +msgid "" +"Starting with GDAL 2.1, it is possible to directly specify the potential " +"names of the columns that can contain X/longitude and Y/latitude with the" +" :oo:`X_POSSIBLE_NAMES` and :oo:`Y_POSSIBLE_NAMES` open option." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:154 +msgid "" +"*ogrinfo -ro -al test.csv -oo X_POSSIBLE_NAMES=Lon\\* -oo " +"Y_POSSIBLE_NAMES=Lat\\* -oo KEEP_GEOM_COLUMNS=NO* will return :" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:171 +msgid "" +"If the CSV file does not have a header line, the dummy \"field_n\" names " +"can be used as possible names for coordinate fields. For example plain " +"XYZ point data can be opened as" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:175 +msgid "" +"*ogrinfo -ro -al elevation.xyz -oo X_POSSIBLE_NAMES=field_1 -oo " +"Y_POSSIBLE_NAMES=field_2 -oo Z_POSSIBLE_NAMES=field_3*" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:178 +msgid "" +"Otherwise, if one or several columns contain a geometry definition " +"encoded as WKT, WKB (encoded in hexadecimal) or GeoJSON (in which case " +"the GeoJSON content must be formatted to follow CSV rules, that is to say" +" it must be surrounded by double-quotes, and double-quotes inside the " +"string must be repeated for proper escaping), the name of such column(s) " +"can be derived from the :oo:`GEOM_POSSIBLE_NAMES` open option." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:185 +msgid "" +"For older versions, it is possible to extract spatial information " +"(points) from a CSV file which has columns for the X and Y coordinates, " +"through the use of the :ref:`VRT <vector.vrt>` driver." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:189 +msgid "You can write the associated VRT file (test.vrt):" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:202 +msgid "and *ogrinfo -ro -al test.vrt* will return :" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:225 +msgid "Building line geometries" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:237 +msgid "" +"With a GDAL build with Spatialite enabled, *ogrinfo test.csv -dialect " +"SQLite -sql \"SELECT way_id, MakeLine(MakePoint(CAST(x AS float),CAST(y " +"AS float))) FROM test GROUP BY way_id\"* will return :" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:254 +#: ../../source/drivers/vector/selafin.rst:407 +msgid "" +"The driver supports reading and writing to files managed by VSI Virtual " +"File System API, which include \"regular\" files, as well as files in the" +" /vsizip/ (read-write) , /vsigzip/ (read-only) , /vsicurl/ (read-only) " +"domains." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:259 +#: ../../source/drivers/vector/geojson.rst:422 +#: ../../source/drivers/vector/georss.rst:245 +#: ../../source/drivers/vector/gpx.rst:392 +#: ../../source/drivers/vector/jsonfg.rst:193 +#: ../../source/drivers/vector/kml.rst:135 +#: ../../source/drivers/vector/libkml.rst:956 +#: ../../source/drivers/vector/pgdump.rst:262 +msgid "Writing to /dev/stdout or /vsistdout/ is also supported." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:261 +msgid "" +"Reading from /vsistdin/ is supported using the ``CSV:/vsistdin/`` " +"connection string and provided that none of the open options whose name " +"starts with ``AUTODETECT_`` is used." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:419 +msgid "" +"The driver supports creating new databases (as a directory of .csv " +"files), adding new .csv files to an existing directory or .csv files or " +"appending features to an existing .csv table. Starting with GDAL 2.1, " +"deleting or replacing existing features, or adding/modifying/deleting " +"fields is supported, provided the modifications done are small enough to " +"be stored in RAM temporarily before flushing to disk." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:427 +msgid "Layer Creation options" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:519 +msgid "" +"This example shows using ogr2ogr to transform a shapefile with point " +"geometry into a .csv file with the X,Y,Z coordinates of the points as " +"first columns in the .csv file" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:527 +msgid "" +"This example shows using ogr2ogr to transform a shapefile into a .csv " +"file with geometry field formatted using GeoJSON format." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:535 +msgid "" +"Convert a CSV into a GeoPackage. Specify the names of the coordinate " +"columns and assign a coordinate reference system." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:546 +msgid "" +"Use `ogr2ogr -segmentize` to densify a input geometry being specified in " +"the ``WKT`` special field. Note that one needs to specify the " +"GEOMETRY=AS_WKT layer creation option, otherwise the input geometry would" +" be returned unmodified:" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:563 +msgid "Particular datasources" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:565 +msgid "The CSV driver can also read files whose structure is close to CSV files :" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:568 +msgid "" +"Airport data files NfdcFacilities.xls, NfdcRunways.xls, NfdcRemarks.xls " +"and NfdcSchedules.xls found on that `FAA website " +"<http://www.faa.gov/airports/airport_safety/airportdata_5010/menu/index.cfm>`__" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:572 +msgid "" +"Files from the `USGS GNIS " +"<http://geonames.usgs.gov/domestic/download_data.htm>`__ (Geographic " +"Names Information System)" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:576 +msgid "The allCountries file from `GeoNames <http://www.geonames.org>`__" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:578 +msgid "" +"`Eurostat .TSV files " +"<http://epp.eurostat.ec.europa.eu/NavTree_prod/everybody/BulkDownloadListing?file=read_me.pdf>`__" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:582 +#: ../../source/drivers/vector/ili.rst:111 +#: ../../source/drivers/vector/vrt.rst:563 +msgid "Other Notes" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:584 +msgid "" +"`GeoCSV specification <http://giswiki.hsr.ch/GeoCSV>`__ (supported by " +"GDAL >= 2.1)" +msgstr "" + +#: ../../source/drivers/vector/csv.rst:586 +msgid "" +"Initial development of the OGR CSV driver was supported by `DM Solutions " +"Group <http://www.dmsolutions.ca/>`__ and `GoMOOS " +"<http://www.gomoos.org/>`__." +msgstr "" + +#: ../../source/drivers/vector/csv.rst:589 +msgid "" +"`Carto <https://carto.com/>`__ funded field type auto-detection and open " +"options related to geometry columns." +msgstr "" + +#: ../../source/drivers/vector/csw.rst:4 +msgid "CSW - OGC CSW (Catalog Service for the Web)" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:6 +msgid "CSW" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:10 +msgid "" +"This driver can connect to a OGC CSW service. It supports CSW 2.0.2 " +"protocol. GDAL/OGR must be built with Curl support in order to the CSW " +"driver to be compiled. And the GML driver should be set-up for read " +"support (thus requiring GDAL/OGR to be built with Xerces or Expat " +"support)." +msgstr "" + +#: ../../source/drivers/vector/csw.rst:16 +msgid "It retrieves records with Dublin Core metadata." +msgstr "" + +#: ../../source/drivers/vector/csw.rst:26 +msgid "" +"The minimal syntax to open a CSW datasource is : *CSW:* and the URL open " +"option, or *CSW:http://path/to/CSW/endpoint*" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:32 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server. It also makes its best effort to do the same for attribute " +"filters set with SetAttributeFilter() when possible (turning OGR SQL " +"language into OGC filter description)." +msgstr "" + +#: ../../source/drivers/vector/csw.rst:37 +msgid "" +"The *anytext* field can be queried to do a search in any text field. Note" +" that we always return it as null content however in OGR side, to avoid " +"duplicating information." +msgstr "" + +#: ../../source/drivers/vector/csw.rst:42 +msgid "Issues" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:44 +msgid "" +"Some servers do not respect EPSG axis order, in particular latitude, " +"longitude order for WGS 84 geodetic coordinates, so it might be needed to" +" specify the :config:`GML_INVERT_AXIS_ORDER_IF_LAT_LONG=NO` configuration" +" option in those cases." +msgstr "" + +#: ../../source/drivers/vector/csw.rst:94 +msgid ":copy-config:`GML_INVERT_AXIS_ORDER_IF_LAT_LONG`" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:99 +msgid "Listing all the records of a CSW server:" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:105 +msgid "" +"Listing all the records of a CSW server with spatial and an attribute " +"filter on a give field:" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:112 +msgid "" +"Listing all the records of a CSW server that matches a text on any text " +"field:" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:119 +msgid "Listing all the records of a CSW server as ISO 19115/19119:" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:128 +msgid "`OGC CSW Standard <http://www.opengeospatial.org/standards/cat>`__" +msgstr "" + +#: ../../source/drivers/vector/csw.rst:129 +#: ../../source/drivers/vector/wfs.rst:428 +msgid ":ref:`GML driver documentation <vector.gml>`" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:4 +#: ../../source/drivers/vector/driver_summary.rst:57 +msgid "Microstation DGN" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:6 +msgid "DGN" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:10 +msgid "" +"Microstation DGN files from Microstation versions predating version 8.0 " +"are supported for reading (a :ref:`DGNv8 driver <vector.dgnv8>`, using " +"Teigha libraries, is available to read and write DGN v8 files). The " +"entire file is represented as one layer (named \"elements\")." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:15 +#: ../../source/drivers/vector/dgnv8.rst:19 +msgid "" +"DGN files are considered to have no georeferencing information through " +"OGR. Features will all have the following generic attributes:" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:18 +#: ../../source/drivers/vector/dgnv8.rst:22 +msgid "Type: The integer type code as listed below in supported elements." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:19 +msgid "Level: The DGN level number (0-63)." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:20 +#: ../../source/drivers/vector/dgnv8.rst:24 +msgid "GraphicGroup: The graphic group number." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:21 +#: ../../source/drivers/vector/dgnv8.rst:25 +msgid "ColorIndex: The color index from the dgn palette." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:22 +#: ../../source/drivers/vector/dgnv8.rst:26 +msgid "Weight: The drawing weight (thickness) for the element." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:23 +#: ../../source/drivers/vector/dgnv8.rst:27 +msgid "Style: The style value for the element." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:24 +msgid "EntityNum and MSLink: The Entity ID and MSLINK values in database linkage." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:25 +#: ../../source/drivers/vector/dgnv8.rst:28 +msgid "" +"ULink: User data linkage (multiple user data linkages may exist for each " +"element)." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:27 +msgid "" +"DGN files do not contain spatial indexes; however, the DGN driver does " +"take advantage of the extents information at the beginning of each " +"element to minimize processing of elements outside the current spatial " +"filter window when in effect." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:46 +msgid "Line (3): Line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:47 +#: ../../source/drivers/vector/dgnv8.rst:46 +msgid "Line String (4): Multi segment line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:48 +#: ../../source/drivers/vector/dgnv8.rst:47 +msgid "Shape (6): Polygon geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:49 +#: ../../source/drivers/vector/dgnv8.rst:49 +msgid "Curve (11): Approximated as a line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:50 +msgid "B-Spline (21): Treated (inaccurately) as a line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:51 +msgid "Arc (16): Approximated as a line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:52 +msgid "Ellipse (15): Approximated as a line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:53 +#: ../../source/drivers/vector/dgnv8.rst:54 +msgid "Text (17): Treated as a point geometry." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:55 +#: ../../source/drivers/vector/dgnv8.rst:59 +msgid "" +"Generally speaking any concept of complex objects, and cells as " +"associated components is lost. Each component of a complex object or cell" +" is treated as a independent feature." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:60 +msgid "MSLINK" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:62 +msgid "" +"A DGN element can have a correspondence to a row in a database table, " +"known as database linkage or database attribute. The EntityNum refers to " +"the database table. The MSLink is the key to find the row in that table." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:68 +#: ../../source/drivers/vector/dgnv8.rst:64 +msgid "User data linkage" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:70 +msgid "" +"A DGN element may have multiple user data linkages. Each linkage has a " +"user id, application id and a number of words of data. The user data " +"linkage output reports the data for each different application id found " +"as raw hexadecimal words (16bits). The application id is the second word " +"of the raw data." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:76 +msgid "" +"Is up to the user how to decode the user raw data, depending on the " +"application id." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:80 +#: ../../source/drivers/vector/dgnv8.rst:75 +msgid "Styling Information" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:82 +#: ../../source/drivers/vector/dgnv8.rst:77 +msgid "" +"Some drawing information about features can be extracted from the " +"ColorIndex, Weight and Style generic attributes; however, for all " +"features an OGR style string has been prepared with the values encoded in" +" ready-to-use form for applications supporting OGR style strings." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:87 +#: ../../source/drivers/vector/dgnv8.rst:82 +msgid "" +"The various kinds of linear geometries will carry style information " +"indicating the color, thickness and line style (i.e. dotted, solid, etc)." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:91 +#: ../../source/drivers/vector/dgnv8.rst:86 +msgid "" +"Polygons (Shape elements) will carry styling information for the edge as " +"well as a fill color if provided. Fill patterns are not supported." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:94 +#: ../../source/drivers/vector/dgnv8.rst:89 +msgid "" +"Text elements will contain the text, angle, color and size information " +"(expressed in ground units) in the style string." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:100 +msgid "2D DGN files may be written with OGR with significant limitations:" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:102 +#: ../../source/drivers/vector/dgnv8.rst:104 +msgid "" +"Output features have the usual fixed DGN attributes. Attempts to create " +"any other fields will fail." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:104 +msgid "" +"Virtual no effort is currently made to translate OGR feature style " +"strings back into DGN representation information." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:106 +#: ../../source/drivers/vector/dgnv8.rst:110 +msgid "" +"POINT geometries that are not text (Text is NULL, and the feature style " +"string is not a LABEL) will be translated as a degenerate (0 length) line" +" element." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:109 +msgid "" +"Polygon, and multipolygon objects will be translated to simple polygons " +"with all rings other than the first discarded." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:111 +msgid "" +"Polygons and line strings with too many vertices will be split into a " +"group of elements prefixed with a Complex Shape Header or Complex Chain " +"Header element as appropriate." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:114 +msgid "" +"A seed file must be provided (or if not provided, " +"$PREFIX/share/gdal/seed_2d.dgn will be used). Many aspects of the " +"resulting DGN file are determined by the seed file, and cannot be " +"affected via OGR, such as initial view window." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:118 +msgid "" +"The various collection geometries other than MultiPolygon are completely " +"discarded at this time." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:120 +#: ../../source/drivers/vector/dgnv8.rst:113 +msgid "" +"Geometries which fall outside the \"design plane\" of the seed file will " +"be discarded, or corrupted in unpredictable ways." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:122 +msgid "" +"DGN files can only have one layer. Attempts to create more than one layer" +" in a DGN file will fail." +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:126 +#: ../../source/drivers/vector/dgnv8.rst:117 +#: ../../source/drivers/vector/georss.rst:147 +#: ../../source/drivers/vector/gml.rst:646 +#: ../../source/drivers/vector/gmlas.rst:349 +#: ../../source/drivers/vector/gpkg.rst:272 +#: ../../source/drivers/vector/gpx.rst:253 +#: ../../source/drivers/vector/jsonfg.rst:116 +#: ../../source/drivers/vector/libkml.rst:73 +#: ../../source/drivers/vector/mapml.rst:59 +#: ../../source/drivers/vector/miramon.rst:289 +#: ../../source/drivers/vector/mvt.rst:226 +#: ../../source/drivers/vector/netcdf.rst:267 +#: ../../source/drivers/vector/ngw.rst:207 +#: ../../source/drivers/vector/pmtiles.rst:104 +#: ../../source/drivers/vector/shapefile.rst:341 +#: ../../source/drivers/vector/tiledb.rst:138 +msgid "Dataset creation options" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:128 +msgid "" +"|about-dataset-creation-options| The following dataset-creation options " +"are supported:" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:185 +msgid "`Dgnlib Page <http://dgnlib.maptools.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:186 +#: ../../source/drivers/vector/dgnv8.rst:233 +#: ../../source/drivers/vector/jml.rst:91 +#: ../../source/drivers/vector/pdf.rst:107 +msgid ":ref:`ogr_feature_style`" +msgstr "" + +#: ../../source/drivers/vector/dgn.rst:187 +msgid ":ref:`DGNv8 driver <vector.dgnv8>` (using Teigha libraries)" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:4 +#: ../../source/drivers/vector/driver_summary.rst:62 +msgid "Microstation DGN v8" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:8 +msgid "DGNv8" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:10 +#: ../../source/drivers/vector/driver_summary.rst:65 +#: ../../source/drivers/vector/driver_summary.rst:70 +#: ../../source/drivers/vector/dwg.rst:8 +msgid "Open Design Alliance Teigha library" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:12 +msgid "" +"Microstation DGN files from Microstation version 8.0 are supported for " +"reading and writing. Each model of the file is represented by a OGR " +"layer." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:16 +msgid "" +"This driver requires to be built against the (non open source) Open " +"Design Alliance Teigha library." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:23 +msgid "Level: The DGN level number." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:42 +msgid "The following element types are supported in reading:" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:44 +msgid "Cell Header (2): used for polygons with holes" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:45 +msgid "Line (3): Line (2 points) geometry." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:48 +msgid "TextNode (7): Container of Text elements." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:50 +msgid "ComplexString (12): Treated as line string or compound curve." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:51 +msgid "ComplexShape (14): Treated as polygon or curve polygon." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:52 +msgid "Ellipse (15): Approximated as a line geometry or a circular string." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:53 +msgid "Arc (16): Approximated as a line geometry or a circular string." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:55 +msgid "B-Spline (21): Treated as a line geometry." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:56 +msgid "PointString (22): Treated as multi point." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:57 +msgid "Shared cell reference (35): Treated as point." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:66 +msgid "" +"A DGN element may have multiple user data linkages. Each linkage has a " +"user id, application id and a number of words of data. The user data " +"linkage output reports the data for each different application id." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:70 +msgid "" +"For unknown application ids, the raw data is reported as hexadecimal " +"words (16bit). Is up to the user how to decode the user data, depending " +"on the application id." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:95 +msgid "" +"The various metadata items that can be set in the DGN header with the " +"dataset creation options (see below) can be retrieved in the \"DGN\" " +"metadata domain." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:102 +msgid "DGN files may be written with OGR with limitations:" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:106 +msgid "" +"Translation from OGR feature style strings back into DGN representation " +"information is limited to a few properties of LABEL (text, font name, " +"size, angle, color), PEN (color) and BRUSH (fill color) tools." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:119 +#: ../../source/drivers/vector/geoconcept.rst:84 +#: ../../source/drivers/vector/georss.rst:149 +#: ../../source/drivers/vector/gml.rst:648 +#: ../../source/drivers/vector/gpx.rst:255 +#: ../../source/drivers/vector/jsonfg.rst:118 +#: ../../source/drivers/vector/kml.rst:94 +#: ../../source/drivers/vector/mapml.rst:61 +#: ../../source/drivers/vector/mitab.rst:108 +#: ../../source/drivers/vector/mvt.rst:228 +#: ../../source/drivers/vector/netcdf.rst:269 +#: ../../source/drivers/vector/pgdump.rst:37 +#: ../../source/drivers/vector/pmtiles.rst:106 +#: ../../source/drivers/vector/selafin.rst:328 +#: ../../source/drivers/vector/sqlite.rst:276 +msgid "" +"|about-dataset-creation-options| The following dataset creation options " +"are supported:" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:221 +#: ../../source/drivers/vector/dwg.rst:89 +msgid "Building" +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:223 +#: ../../source/drivers/vector/dwg.rst:91 +msgid "" +"See :ref:`ODA platform support <vector.oda>` for building GDAL with ODA " +"support." +msgstr "" + +#: ../../source/drivers/vector/dgnv8.rst:232 +msgid ":ref:`DGN (v7) driver <vector.dgn>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:16 +msgid ":ref:`AmigoCloud <vector.amigocloud>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:21 +msgid ":ref:`Arrow <vector.arrow>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:26 +msgid ":ref:`AVCBIN <vector.avcbin>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:31 +msgid ":ref:`AVCE00 <vector.avce00>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:36 +msgid ":ref:`CAD <vector.cad>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:37 +#: ../../source/drivers/vector/driver_summary.rst:67 +#: ../../source/drivers/vector/dwg.rst:4 +msgid "AutoCAD DWG" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:41 +msgid ":ref:`CARTO <vector.carto>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:46 +msgid ":ref:`CSV <vector.csv>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:51 +msgid ":ref:`CSW <vector.csw>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:52 +msgid "OGC CSW (Catalog Service for the Web)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:56 +msgid ":ref:`DGN <vector.dgn>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:61 +msgid ":ref:`DGNv8 <vector.dgnv8>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:66 +msgid ":ref:`DWG <vector.dwg>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:71 +msgid ":ref:`DXF <vector.dxf>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:72 +#: ../../source/drivers/vector/dxf.rst:4 +msgid "AutoCAD DXF" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:76 +msgid ":ref:`EDIGEO <vector.edigeo>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:77 +#: ../../source/drivers/vector/edigeo.rst:4 +#: ../../source/drivers/vector/edigeo.rst:6 +msgid "EDIGEO" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:81 +msgid ":ref:`EEDA <vector.eeda>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:82 +#: ../../source/drivers/vector/eeda.rst:4 +msgid "Google Earth Engine Data API" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:86 +msgid ":ref:`Elasticsearch <vector.elasticsearch>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:87 +#: ../../source/drivers/vector/elasticsearch.rst:4 +msgid "Elasticsearch: Geographically Encoded Objects for Elasticsearch" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:91 +msgid ":ref:`ESRIJSON <vector.esrijson>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:92 +#: ../../source/drivers/vector/esrijson.rst:4 +msgid "ESRIJSON / FeatureService driver" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:96 +msgid ":ref:`FileGDB <vector.filegdb>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:97 +#: ../../source/drivers/vector/filegdb.rst:4 +msgid "ESRI File Geodatabase (FileGDB)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:100 +#: ../../source/drivers/vector/filegdb.rst:8 +msgid "FileGDB API library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:101 +msgid ":ref:`FlatGeobuf <vector.flatgeobuf>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:102 +#: ../../source/drivers/vector/flatgeobuf.rst:4 +#: ../../source/drivers/vector/flatgeobuf.rst:8 +msgid "FlatGeobuf" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:106 +msgid ":ref:`Geoconcept <vector.geoconcept>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:107 +#: ../../source/drivers/vector/geoconcept.rst:4 +msgid "GeoConcept text export" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:111 +msgid ":ref:`GeoJSON <vector.geojson>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:112 +#: ../../source/drivers/vector/geojson.rst:4 +#: ../../source/drivers/vector/geojson.rst:6 +msgid "GeoJSON" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:116 +msgid ":ref:`GeoJSONSeq <vector.geojsonseq>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:117 +#: ../../source/drivers/vector/geojsonseq.rst:4 +msgid "GeoJSONSeq: sequence of GeoJSON features" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:121 +msgid ":ref:`GeoRSS <vector.georss>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:122 +#: ../../source/drivers/vector/georss.rst:4 +msgid "GeoRSS : Geographically Encoded Objects for RSS feeds" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:125 +#: ../../source/drivers/vector/driver_summary.rst:155 +#: ../../source/drivers/vector/driver_summary.rst:195 +#: ../../source/drivers/vector/driver_summary.rst:205 +#: ../../source/drivers/vector/georss.rst:8 +#: ../../source/drivers/vector/gpx.rst:8 ../../source/drivers/vector/jml.rst:8 +#: ../../source/drivers/vector/kml.rst:8 +msgid "(read support needs libexpat)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:126 +msgid ":ref:`GML <vector.gml>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:127 +msgid "Geography Markup Language" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:130 +#: ../../source/drivers/vector/gml.rst:8 +msgid "(read support needs Xerces or libexpat)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:131 +msgid ":ref:`GMLAS <vector.gmlas>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:132 +msgid "Geography Markup Language (GML) driven by application schemas" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:135 +#: ../../source/drivers/vector/driver_summary.rst:185 +#: ../../source/drivers/vector/driver_summary.rst:190 +#: ../../source/drivers/vector/driver_summary.rst:260 +#: ../../source/drivers/vector/gmlas.rst:10 +#: ../../source/drivers/vector/ili.rst:10 ../../source/drivers/vector/nas.rst:8 +msgid "Xerces" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:136 +msgid ":ref:`GMT <vector.gmt>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:137 +#: ../../source/drivers/vector/gmt.rst:4 +msgid "GMT ASCII Vectors (.gmt)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:141 +msgid ":ref:`GPKG <vector.gpkg>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:142 +msgid "GeoPackage vector" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:146 +msgid ":ref:`GPSBabel <vector.gpsbabel>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:147 +#: ../../source/drivers/vector/gpsbabel.rst:4 +#: ../../source/drivers/vector/gpsbabel.rst:6 +msgid "GPSBabel" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:150 +#: ../../source/drivers/vector/gpsbabel.rst:8 +msgid "(read support needs GPX driver and libexpat)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:151 +msgid ":ref:`GPX <vector.gpx>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:152 +msgid "GPS Exchange Format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:156 +msgid ":ref:`GRASS <vector.grass>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:157 +#: ../../source/drivers/vector/grass.rst:4 +msgid "GRASS Vector Format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:161 +msgid ":ref:`GTFS <vector.gtfs>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:162 +msgid "General Transit Feed Specification" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:166 +msgid ":ref:`HANA <vector.hana>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:167 +#: ../../source/drivers/vector/hana.rst:4 +msgid "SAP HANA" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:170 +#: ../../source/drivers/vector/hana.rst:8 +msgid "odbc-cpp-wrapper" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:171 +msgid ":ref:`IDB <vector.idb>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:172 +#: ../../source/drivers/vector/idb.rst:4 ../../source/drivers/vector/idb.rst:6 +msgid "IDB" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:175 +#: ../../source/drivers/vector/idb.rst:8 +msgid "Informix DataBlade" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:176 +msgid ":ref:`IDRISI <vector.idrisi>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:177 +#: ../../source/drivers/vector/idrisi.rst:4 +msgid "Idrisi Vector (.VCT)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:181 +msgid ":ref:`INTERLIS 1 <vector.ili>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:182 +#: ../../source/drivers/vector/driver_summary.rst:187 +#: ../../source/drivers/vector/ili.rst:4 +msgid "\"INTERLIS 1\" and \"INTERLIS 2\" drivers" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:186 +msgid ":ref:`INTERLIS 2 <vector.ili>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:191 +msgid ":ref:`JML <vector.jml>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:192 +#: ../../source/drivers/vector/jml.rst:4 +msgid "JML: OpenJUMP JML format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:196 +msgid ":ref:`JSONFG <vector.jsonfg>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:197 +msgid "OGC Features and Geometries JSON" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:201 +msgid ":ref:`KML <vector.kml>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:202 +msgid "Keyhole Markup Language" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:206 +msgid ":ref:`LIBKML <vector.libkml>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:207 +#: ../../source/drivers/vector/libkml.rst:4 +msgid "LIBKML Driver (.kml .kmz)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:210 +#: ../../source/drivers/vector/libkml.rst:8 +msgid "libkml" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:211 +msgid ":ref:`LVBAG <vector.lvbag>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:212 +#: ../../source/drivers/vector/lvbag.rst:5 +msgid "Dutch Kadaster LV BAG 2.0 Extract" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:215 +#: ../../source/drivers/vector/driver_summary.rst:295 +#: ../../source/drivers/vector/driver_summary.rst:385 +#: ../../source/drivers/vector/driver_summary.rst:440 +#: ../../source/drivers/vector/lvbag.rst:11 +#: ../../source/drivers/vector/ods.rst:8 ../../source/drivers/vector/svg.rst:8 +#: ../../source/drivers/vector/xlsx.rst:9 +msgid "libexpat" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:216 +msgid ":ref:`MapML <vector.mapml>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:217 +#: ../../source/drivers/vector/mapml.rst:4 +#: ../../source/drivers/vector/mapml.rst:8 +msgid "MapML" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:221 +msgid ":ref:`Memory <vector.memory>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:222 +#: ../../source/drivers/vector/memory.rst:4 +#: ../../source/drivers/vector/memory.rst:6 +msgid "Memory" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:226 +msgid ":ref:`MiraMonVector <vector.miramon>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:227 +#: ../../source/drivers/vector/miramon.rst:4 +msgid "MiraMon Vector" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:231 +msgid ":ref:`MapInfo File <vector.mitab>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:232 +#: ../../source/drivers/vector/mitab.rst:4 +msgid "MapInfo TAB and MIF/MID" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:236 +msgid ":ref:`MongoDBv3 <vector.mongodbv3>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:237 +#: ../../source/drivers/vector/mongodbv3.rst:4 +#: ../../source/drivers/vector/mongodbv3.rst:8 +msgid "MongoDBv3" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:240 +#: ../../source/drivers/vector/mongodbv3.rst:10 +msgid "Mongo CXX >= 3.4.0 client library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:241 +msgid ":ref:`MSSQLSpatial <vector.mssqlspatial>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:242 +msgid "Microsoft SQL Server Spatial Database" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:245 +#: ../../source/drivers/vector/driver_summary.rst:290 +#: ../../source/drivers/vector/driver_summary.rst:340 +#: ../../source/drivers/vector/mssqlspatial.rst:8 +#: ../../source/drivers/vector/odbc.rst:8 +#: ../../source/drivers/vector/pgeo.rst:8 +msgid "ODBC library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:246 +msgid ":ref:`MVT <vector.mvt>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:247 +#: ../../source/drivers/vector/mvt.rst:4 +msgid "MVT: Mapbox Vector Tiles" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:250 +#: ../../source/drivers/vector/mvt.rst:10 +msgid "(requires SQLite and GEOS for write support)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:251 +msgid ":ref:`MySQL <vector.mysql>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:252 +#: ../../source/drivers/vector/mysql.rst:4 +#: ../../source/drivers/vector/mysql.rst:6 +msgid "MySQL" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:255 +#: ../../source/drivers/vector/mysql.rst:8 +msgid "MySQL library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:256 +msgid ":ref:`NAS <vector.nas>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:257 +msgid "ALKIS" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:261 +msgid ":ref:`netCDF <vector.netcdf>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:262 +msgid "Vector" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:266 +msgid ":ref:`NGW <vector.ngw>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:271 +msgid ":ref:`UK .NTF <vector.ntf>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:272 +#: ../../source/drivers/vector/ntf.rst:4 ../../source/drivers/vector/ntf.rst:6 +msgid "UK .NTF" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:276 +msgid ":ref:`OAPIF <vector.oapif>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:277 +#: ../../source/drivers/vector/oapif.rst:4 +msgid "OGC API - Features" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:281 +msgid ":ref:`OCI <vector.oci>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:282 +#: ../../source/drivers/vector/oci.rst:4 +msgid "Oracle Spatial" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:285 +#: ../../source/drivers/vector/oci.rst:8 +msgid "OCI library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:286 +msgid ":ref:`ODBC <vector.odbc>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:287 +#: ../../source/drivers/vector/odbc.rst:4 +msgid "ODBC RDBMS" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:291 +msgid ":ref:`ODS <vector.ods>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:292 +msgid "Open Document Spreadsheet" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:296 +msgid ":ref:`OGDI <vector.ogdi>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:297 +#: ../../source/drivers/vector/ogdi.rst:4 +msgid "OGDI Vectors" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:300 +#: ../../source/drivers/vector/ogdi.rst:8 +msgid "OGDI library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:301 +msgid ":ref:`OpenFileGDB <vector.openfilegdb>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:302 +#: ../../source/drivers/vector/openfilegdb.rst:4 +msgid "ESRI File Geodatabase vector (OpenFileGDB)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:306 +msgid ":ref:`OSM <vector.osm>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:307 +msgid "OpenStreetMap XML and PBF" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:310 +#: ../../source/drivers/vector/osm.rst:8 +msgid "libsqlite3 (and libexpat for OSM XML)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:311 +msgid ":ref:`Parquet <vector.parquet>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:312 +#: ../../source/drivers/vector/parquet.rst:4 +msgid "(Geo)Parquet" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:315 +#: ../../source/drivers/vector/parquet.rst:10 +msgid "Parquet component of the Apache Arrow C++ library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:316 +msgid ":ref:`PDF <vector.pdf>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:321 +msgid ":ref:`PDS <vector.pds>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:322 +msgid "Planetary Data Systems TABLE" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:326 +msgid ":ref:`PostgreSQL <vector.pg>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:327 +#: ../../source/drivers/vector/pg.rst:4 +msgid "PostgreSQL / PostGIS" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:330 +#: ../../source/drivers/vector/pg.rst:8 +msgid "PostgreSQL client library (libpq)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:331 +msgid ":ref:`PGDump <vector.pgdump>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:332 +#: ../../source/drivers/vector/pgdump.rst:4 +msgid "PostgreSQL SQL Dump" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:336 +msgid ":ref:`PGeo <vector.pgeo>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:337 +#: ../../source/drivers/vector/pgeo.rst:4 +msgid "ESRI Personal GeoDatabase" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:341 +msgid ":ref:`PLScenes <vector.plscenes>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:342 +#: ../../source/drivers/vector/plscenes.rst:4 +msgid "PLScenes (Planet Labs Scenes/Catalog API)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:346 +msgid ":ref:`PMTiles <vector.pmtiles>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:347 +msgid "ProtoMaps Tiles" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:351 +msgid ":ref:`S57 <vector.s57>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:352 +#: ../../source/drivers/vector/s57.rst:4 +msgid "IHO S-57 (ENC)" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:356 +msgid ":ref:`SDTS <vector.sdts>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:361 +msgid ":ref:`Selafin <vector.selafin>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:362 +#: ../../source/drivers/vector/selafin.rst:4 +msgid "Selafin files" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:366 +msgid ":ref:`ESRI Shapefile <vector.shapefile>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:367 +#: ../../source/drivers/vector/shapefile.rst:4 +msgid "ESRI Shapefile / DBF" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:371 +msgid ":ref:`SOSI <vector.sosi>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:372 +#: ../../source/drivers/vector/sosi.rst:5 +msgid "Norwegian SOSI Standard" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:375 +#: ../../source/drivers/vector/sosi.rst:9 +msgid "FYBA library" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:376 +msgid ":ref:`SQLite <vector.sqlite>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:377 +#: ../../source/drivers/vector/sqlite.rst:4 +msgid "SQLite / Spatialite RDBMS" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:380 +#: ../../source/drivers/vector/sqlite.rst:8 +msgid "libsqlite3 or libspatialite" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:381 +msgid ":ref:`SVG <vector.svg>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:382 +msgid "Scalable Vector Graphics" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:386 +msgid ":ref:`SXF <vector.sxf>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:387 +#: ../../source/drivers/vector/sxf.rst:6 +msgid "SXF" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:391 +msgid ":ref:`TIGER <vector.tiger>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:392 +#: ../../source/drivers/vector/tiger.rst:4 +msgid "U.S. Census TIGER/Line" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:396 +msgid ":ref:`TileDB <vector.tiledb>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:397 +msgid "TileDB vector" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:400 +#: ../../source/drivers/vector/tiledb.rst:11 +msgid "TileDB >= 2.7" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:401 +msgid ":ref:`TopoJSON <vector.topojson>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:402 +#: ../../source/drivers/vector/topojson.rst:4 +msgid "TopoJSON driver" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:406 +msgid ":ref:`VDV <vector.vdv>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:407 +msgid "VDV-451/VDV-452/INTREST Data Format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:411 +msgid ":ref:`VFK <vector.vfk>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:412 +msgid "Czech Cadastral Exchange Data Format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:416 +msgid ":ref:`VRT <vector.vrt>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:417 +msgid "Virtual Format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:421 +msgid ":ref:`WAsP <vector.wasp>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:422 +msgid "WAsP .map format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:426 +msgid ":ref:`WFS <vector.wfs>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:427 +msgid "OGC WFS service" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:431 +msgid ":ref:`XLS <vector.xls>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:432 +msgid "MS Excel format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:435 +#: ../../source/drivers/vector/xls.rst:8 +msgid "libfreexl" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:436 +msgid ":ref:`XLSX <vector.xlsx>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:437 +msgid "MS Office Open XML spreadsheet" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:441 +msgid ":ref:`XODR <vector.xodr>`" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:442 +msgid "OpenDRIVE Road Description Format" +msgstr "" + +#: ../../source/drivers/vector/driver_summary.rst:445 +#: ../../source/drivers/vector/xodr.rst:10 +msgid "libOpenDRIVE >= 0.5.0, GEOS" +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:6 +msgid "DWG" +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:10 +msgid "" +"OGR supports reading most versions of AutoCAD DWG when built with the " +"Open Design Alliance Teigha library. DWG is a binary working format used " +"for AutoCAD drawings. A reasonable effort has been made to make the OGR " +"DWG driver work similarly to the OGR DXF driver which shares a common " +"data model. The entire contents of the .dwg file is represented as a " +"single layer named \"entities\"." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:20 +#: ../../source/drivers/vector/dxf.rst:32 +msgid "Layer: The name of the DXF layer. The default layer is \"0\"." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:21 +msgid "" +"SubClasses: Where available, a list of classes to which an element " +"belongs." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:25 +#: ../../source/drivers/vector/dxf.rst:48 +msgid "Linetype: Where available, the line type used for this entity." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:26 +#: ../../source/drivers/vector/dxf.rst:49 +msgid "EntityHandle: The hexadecimal entity handle. A sort of feature id." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:27 +#: ../../source/drivers/vector/dxf.rst:50 +msgid "Text: The text of labels." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:29 +msgid "" +"A reasonable attempt is made to preserve line color, line width, text " +"size and orientation via OGR feature styling information when translating" +" elements. Currently no effort is made to preserve fill styles or complex" +" line style attributes." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:34 +#: ../../source/drivers/vector/dxf.rst:176 +msgid "" +"The :config:`OGR_ARC_STEPSIZE` and :config:`OGR_ARC_MAX_GAP` " +"configurations options control the approximation of arcs, ellipses, " +"circles and rounded polylines as linestrings." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:53 +msgid "" +"A new layer will be available called blocks. It will contain one or more " +"features for each block defined in the file. In addition to the usual " +"attributes, they will also have a BlockName attribute indicate what block" +" they are part of." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:57 +msgid "" +"The entities layer will have new attributes BlockName, BlockScale, " +"BlockAngle and BlockAttributes." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:59 +msgid "" +"BlockAttributes will be a list of (tag x value) pairs of all visible " +"attributes (JSON encoded)." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:61 +msgid "" +"block referenced will populate these new fields with the corresponding " +"information (they are null for all other entities)." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:63 +msgid "" +"block references will not have block geometry inlined - instead they will" +" have a point geometry for the insertion point." +msgstr "" + +#: ../../source/drivers/vector/dwg.rst:66 +msgid "" +"The intention is that with :config:`DWG_INLINE_BLOCKS` disabled, the " +"block references will remain as references and the original block " +"definitions will be available via the blocks layer." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:6 +msgid "DXF" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:10 +msgid "" +"DXF is an ASCII format used for interchanging AutoCAD drawings between " +"different software packages. OGR supports reading DXF files generated by " +"all recent versions of AutoCAD, and writing DXF files that are compatible" +" with AutoCAD 2004 and later." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:15 +msgid "" +"DXF files are considered to have no georeferencing information through " +"OGR." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:26 +msgid "DXF Reader" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:28 +msgid "" +"By default, the entire contents of the file are represented as a single " +"OGR layer named \"entities\". Features will all have the following " +"generic fields:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:33 +msgid "" +"PaperSpace: 1 if the entity is located on a layout (paper space), NULL " +"otherwise." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:35 +msgid "SubClasses: Where available, a list of classes to which an entity belongs." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:37 +msgid "" +"ExtendedEntity (GDAL <= 2.2.x): The values of extended entity attributes " +"all appended to form a single text field, where available." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:39 +msgid "" +"RawCodeValues (GDAL >= 2.3.0): A string list containing all group codes " +"and values that are not handled by the DXF reader. Only available when " +"the configuration option :config:`DXF_INCLUDE_RAW_CODE_VALUES=TRUE`." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:53 +msgid "Supported Entities" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:55 +msgid "The following entity types are supported:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:57 +msgid "POINT: Produces a simple POINT geometry feature." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:58 +#, python-format +msgid "" +"MTEXT, TEXT: Produces a POINT feature with LABEL style information. The " +"style string may include the following parameters: f s t a c w p dx dy bo" +" it. Text positioning might not precisely match CAD software (especially " +"the vertical alignment of MTEXT), as calculation of the exact position " +"would require GDAL to be aware of the font metrics. By default, character" +" escapes such as %%p are honored where applicable, and MTEXT control " +"sequences like \\\\Wx.xx; are stripped. To disable this behavior and " +"retrieve the raw text values, set the configuration option " +":config:`DXF_TRANSLATE_ESCAPE_SEQUENCES=FALSE`." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:72 +msgid "" +"LINE, POLYLINE, LWPOLYLINE: Translated as a LINESTRING. Rounded polylines" +" (those with their vertices' bulge attributes set) will be tessellated. " +"Single-vertex polylines are translated to POINT. Polyface meshes are " +"translated as POLYHEDRALSURFACE geometries." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:76 +msgid "MLINE:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:78 +msgid "" +"(GDAL >= 2.3.0) Translated as a MULTILINESTRING. Only the geometry is " +"reconstructed; styling applied to individual line elements within the " +"MLINE is ignored. Fill colors and start/end caps are also omitted." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:82 +#: ../../source/drivers/vector/dxf.rst:166 +msgid "(GDAL <= 2.2.x) No support." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:84 +msgid "" +"CIRCLE, ELLIPSE, ARC, SPLINE, (GDAL >= 2.3.0) HELIX: Translated as a " +"LINESTRING, tessellating the curve into line segments. (GDAL >= 2.3.0) " +"CIRCLEs with nonzero \"thickness\" (cylinders) are approximated as a " +"POLYHEDRALSURFACE." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:88 +msgid "" +"INSERT: By default, the block definition referenced by the INSERT will be" +" inserted as a compound geometry (for example, a MULTILINESTRING for a " +"block containing many lines, or a GEOMETRYCOLLECTION for a block that " +"contains points and lines). If the block contains TEXT or MTEXT entities," +" they are not merged into the compound geometry and are instead returned " +"as separate features." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:95 +msgid "" +"Three configuration options are available to control the behavior of " +"INSERT entities:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:118 +msgid "ATTDEF, ATTRIB:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:120 +msgid "" +"(GDAL >= 2.3.0) Attributes (ATTRIB) are treated as TEXT entities, and " +"attribute definitions (ATTDEF) inside blocks are ignored. The behavior is" +" different when :config:`DXF_INLINE_BLOCKS` is false (see below)." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:123 +msgid "" +"(GDAL <= 2.2.x) ATTDEF entities are treated as TEXT. ATTRIB entities are " +"not supported." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:126 +msgid "" +"HATCH: Line and arc boundaries are collected as a polygon geometry, but " +"no effort is currently made to represent the fill style of HATCH " +"entities. Behavior is affected by the following configuration option:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:137 +msgid "" +"(GDAL <= 2.2.x) Only line and polyline boundary paths are translated " +"correctly." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:140 +msgid "" +"3DFACE, SOLID, (GDAL >= 2.3.0) TRACE: Translated as POLYGON, except for " +"SOLID and TRACE entities with only one distinct vertex (translated as " +"POINT) or two distinct vertices (translated as LINESTRING)." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:144 +msgid "DIMENSION:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:146 +msgid "" +"(GDAL >= 2.3.0) The DXF format allows each DIMENSION entity to reference " +"an \"anonymous\" block (a block whose name starts with \\*D) that " +"contains the geometry of the DIMENSION. If present, this anonymous block " +"will be inlined at the required position. Otherwise, fallback will occur " +"to a simple DIMENSION renderer that explodes a linear dimension as a " +"MULTILINESTRING feature. Arrowheads, if present, are translated as one or" +" more additional features. The fallback renderer will render nonlinear " +"dimensions as if they were linear." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:155 +msgid "" +"(GDAL <= 2.2.x) Dimensions are translated as a MULTILINESTRING and a " +"POINT for the text." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:158 +msgid "LEADER, MULTILEADER:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:160 +msgid "" +"(GDAL >= 2.3.0) The leader line is translated as a LINESTRING (LEADER) or" +" MULTILINESTRING (MULTILEADER). Arrowheads, if present, are translated as" +" one or more additional features. Text for MULTILEADER entities is " +"translated into a POINT feature with a label. Block content for " +"MULTILEADERS is treated as for INSERT. Spline leaders are tessellated " +"into line segments." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:168 +msgid "3DSOLID, REGION, BODY, SURFACE: See below." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:170 +msgid "" +"A reasonable attempt is made to preserve color, line width (lineweight), " +"line type, text size and orientation via OGR feature styling information " +"when translating entities. Currently no effort is made to preserve " +"complex line types (those that include text or shapes) or HATCH fill " +"styles." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:180 +msgid "" +"For splines, the interpolated polyline contains eight vertices for each " +"control point." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:183 +msgid "" +"Object coordinate systems (OCS), also known as \"extrusions\", are " +"supported for all entities to which they apply as per the DXF " +"specification, except DIMENSION, LEADER and MULTILEADER. These three " +"entity types also currently lack support for elevations; the geometries " +"will always be 2D." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:190 +msgid "DXF_INLINE_BLOCKS" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:192 +msgid "" +"The default behavior is for INSERT entities to be exploded with the " +"geometry of the BLOCK they reference. However, if the " +":config:`DXF_INLINE_BLOCKS` configuration option is set to the value " +"FALSE, then the behavior is different as described here." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:197 +msgid "" +"A new layer will be available called \"blocks\". It will contain one or " +"more features for each BLOCK defined in the file. In addition to the " +"usual fields, they will also have a Block field indicating what block " +"they are part of. (Note, in GDAL 2.2.x and earlier this field was called " +"BlockName.)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:202 +msgid "" +"(GDAL >= 2.3.0) ATTDEF entities in the blocks layer will have an " +"AttributeTag field, giving the tag of the ATTDEF entity." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:204 +msgid "The entities layer will have several new fields:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:206 +msgid "BlockName: The name of the referenced block." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:207 +msgid "BlockScale: The X, Y, and Z scale factors." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:208 +msgid "BlockAngle: The angle of the block in degrees." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:209 +msgid "" +"BlockOCSNormal (GDAL >= 2.3.0): The unit normal vector of the object " +"coordinate system (OCS) of the INSERT entity." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:211 +msgid "" +"BlockOCSCoords (GDAL >= 2.3.0): The OCS coordinates of the insertion " +"point." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:213 +msgid "" +"BlockAttributes (GDAL >= 2.3.0): The text content of attributes " +"associated with this block. Each entry in this string list contains an " +"attribute tag, followed by a space, followed by the text for that " +"attribute (which may be empty)." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:218 +msgid "" +"INSERT entities will populate these new fields with the corresponding " +"information (they are null for all other entities)." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:220 +msgid "" +"INSERT entities will not have block geometry inlined - instead they will " +"have a POINT geometry for the insertion point." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:223 +msgid "" +"The intention is that with :config:`DXF_INLINE_BLOCKS` disabled, the " +"block references will remain as references and the original block " +"definitions will be available via the blocks layer. On export this " +"configuration will result in the creation of similar blocks." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:229 +msgid "3D Extensibility" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:231 +msgid "" +"DXF files may contain 3DSOLID, REGION, BODY and SURFACE entities, which " +"contain 3D modelling data in the proprietary Autodesk ShapeManager (ASM) " +"format, a broadly compatible fork of the ACIS format. GDAL cannot " +"transform these entities into OGR geometries, so they are skipped by " +"default." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:236 +msgid "This behavior can be controlled with the following configuration option:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:246 +msgid "ASMData: A binary field that contains the ASM data." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:247 +msgid "" +"ASMTransform: A column-major list of 12 real values indicating the affine" +" transformation to be applied to the entity." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:250 +msgid "" +"This feature only works for DXF files in AutoCAD 2013 (AC1027) format and" +" later." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:254 +msgid "Character Encodings" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:256 +msgid "" +"Normally DXF files are in the ANSI_1252 / Win1252 encoding. GDAL/OGR " +"attempts to translate this to UTF-8 when reading and back into ANSI_1252 " +"when writing. DXF files can also have a header field ($DWGCODEPAGE) " +"indicating the encoding of the file. An attempt is made to use this to " +"recode other code pages to UTF-8. Whether this works will depend on the " +"code page naming and whether GDAL/OGR is built against the iconv library " +"for character recoding." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:264 +msgid "" +"In some cases the $DWGCODEPAGE setting in a DXF file will be wrong, or " +"unrecognised by OGR. In this case, :config:`DXF_ENCODING` may be used to " +"override what id will be used by OGR in transcoding:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:278 +msgid "DXF Writer" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:280 +msgid "" +"DXF files are written in AutoCAD 2004 format. A standard header " +"(everything up to the ENTITIES keyword) is written from the " +"$GDAL_DATA/header.dxf file, and the $GDAL_DATA/trailer.dxf file is added " +"after the entities. Only one OGR layer can be used to create the output " +"file (but many DXF layers can be created - see below)." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:286 +msgid "" +"Point features with LABEL styling are written as MTEXT entities based on " +"the styling information." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:288 +msgid "Point features without LABEL styling are written as POINT entities." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:289 +msgid "" +"LineString and MultiLineString features are written as one or more " +"LWPOLYLINE entities, closed in the case of polygon rings. If the geometry" +" does not have a constant elevation, a POLYLINE entity is written. An " +"effort is made to preserve line width and color." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:293 +msgid "" +"Polygon, Triangle and MultiPolygon features are written as HATCH entities" +" by default. To write these features as LWPOLYLINE/POLYLINE entities " +"instead, set the configuration option :config:`DXF_WRITE_HATCH=FALSE`:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:304 +msgid "" +"You may need to do this if your geometries do not have a constant " +"elevation, as the DXF HATCH entity cannot represent such geometries." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:308 +msgid "" +"Only the first tool (PEN, BRUSH, etc) in the style string is read. The " +"following style string parameters are understood:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:314 +#: ../../source/drivers/vector/pdf.rst:57 +msgid "Tool" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:315 +msgid "Available on geometry types" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:316 +msgid "Supported parameters" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:317 +#: ../../source/drivers/vector/pdf.rst:60 +msgid "PEN" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:318 +msgid "Point, (Multi)LineString" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:319 +#: ../../source/drivers/vector/pdf.rst:61 +msgid "color (c); width (w); dash pattern (p)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:320 +#: ../../source/drivers/vector/pdf.rst:63 +msgid "BRUSH" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:321 +msgid "(Multi)Polygon, Triangle" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:322 +#: ../../source/drivers/vector/pdf.rst:64 +msgid "foreground color (fc)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:323 +#: ../../source/drivers/vector/pdf.rst:74 +msgid "SYMBOL" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:324 +#: ../../source/drivers/vector/dxf.rst:327 +#: ../../source/drivers/vector/ogdi.rst:14 +msgid "Point" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:325 +msgid "color (c)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:326 +#: ../../source/drivers/vector/pdf.rst:66 +msgid "LABEL" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst +msgid "GDAL >= 2.3.0: text (t); font name (f); font size (s), treated as cap" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst +msgid "height; bold (bo); italic (it); text color (c); x and y offsets (dx," +msgstr "" + +#: ../../source/drivers/vector/dxf.rst +msgid "dy); angle (a); anchor point (p); stretch (w)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst +msgid "GDAL <= 2.2.x: text (t); font size (s), treated as cap height; text" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst +msgid "color (c); angle (a); anchor point (p)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:334 +msgid "" +"|about-dataset-creation-options| The driver supports the following " +"dataset creation options:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:349 +msgid "" +"The header and trailer templates can be complete DXF files. The driver " +"will scan them and only extract the needed portions (portion before or " +"after the ENTITIES section)." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:354 +msgid "Block References" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:356 +msgid "" +"It is possible to export a \"blocks\" layer to DXF in addition to the " +"\"entities\" layer in order to produce actual DXF BLOCKs definitions in " +"the output file. It is also possible to write INSERT entities if a block " +"name is provided for an entity. To make this work the following " +"conditions apply:" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:362 +msgid "" +"A \"blocks\" layer may be created, and it must be created before the " +"entities layer." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:364 +msgid "" +"The entities in the blocks layer should have the Block field populated. " +"(Note, in GDAL 2.2.x and earlier this attribute was called BlockName.)" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:367 +msgid "" +"Objects to be written as INSERTs in the entities layer should have a " +"POINT geometry, and the BlockName field set. You may also set BlockAngle," +" BlockScale, BlockOCSNormal and BlockOCSCoords (see above under " +":config:`DXF_INLINE_BLOCKS` for details). If BlockOCSCoords is set to a " +"list of 3 real numbers, it is used as the location of the block; in this " +"situation the position of the POINT geometry is ignored." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:373 +msgid "" +"If a block (name) is already defined in the template header, that will be" +" used regardless of whether a new definition was provided in the blocks " +"layer." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:377 +msgid "" +"The intention is that a simple translation from DXF to DXF with " +":config:`DXF_INLINE_BLOCKS` set to FALSE will approximately reproduce the" +" original blocks and keep INSERT entities as INSERT entities rather than " +"exploding them." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:383 +msgid "Layer Definitions" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:385 +msgid "" +"When writing entities, if populated the Layer field is used to set the " +"written entities layer. If the layer is not already defined in the " +"template header then a new layer definition will be introduced, copied " +"from the definition of the default layer (\"0\")." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:391 +msgid "Linetype Definitions" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:393 +msgid "" +"When writing linestring geometries, the following rules apply with regard" +" to linetype (dash pattern) definitions." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:396 +msgid "" +"If the Linetype field is set on a written feature, and that linetype is " +"already defined in the template header, then it will be referenced from " +"the entity. If a style string is present with a \"p\" pattern " +"proportional to the linetype defined in the header, a linetype scale " +"value is written." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:401 +msgid "" +"If the Linetype field is set, but the linetype is not defined in the " +"header template, then a definition will be added if the feature has an " +"OGR style string with a PEN tool and a \"p\" pattern setting." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:404 +msgid "" +"If the feature has no Linetype field set, but it does have an OGR style " +"string with a PEN tool with a \"p\" pattern set, then an automatically " +"named linetype will be created in the output file. Or, if an appropriate " +"linetype was previously created, that linetype will be referenced, with a" +" linetype scale if required." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:410 +msgid "" +"The intention is that \"dot dash\" style patterns will be preserved when " +"written to DXF and that specific linetypes can be predefined in the " +"header template, and referenced using the Linetype field if desired." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:414 +msgid "" +"It is assumed that patterns are using \"g\" (georeferenced) units for " +"defining the line pattern. If not, the scaling of the DXF patterns is " +"likely to be wrong - potentially very wrong." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:419 +msgid "Units" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:421 +msgid "" +"GDAL writes DXF files with measurement units set to \"Imperial - " +"Inches\". If you need to change the units, edit the `$MEASUREMENT " +"<https://knowledge.autodesk.com/support/autocad/learn-" +"explore/caas/CloudHelp/cloudhelp/2018/ENU/AutoCAD-Core/files/GUID-" +"1D074C55-0B63-482E-8A37-A52AC0C7C8FE-htm.html>`__ and `$INSUNITS " +"<https://knowledge.autodesk.com/support/autocad/learn-" +"explore/caas/CloudHelp/cloudhelp/2018/ENU/AutoCAD-Core/files/GUID-" +"A58A87BB-482B-4042-A00A-EEF55A2B4FD8-htm.html>`__ variables in the header" +" template." +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:434 +msgid "" +"`List of known issues " +"<https://github.com/OSGeo/gdal/blob/master/ogr/ogrsf_frmts/dxf/KNOWN_ISSUES.md>`__" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:437 +msgid "" +"`AutoCAD 2000 DXF Reference " +"<http://www.autodesk.com/techpubs/autocad/acad2000/dxf/>`__" +msgstr "" + +#: ../../source/drivers/vector/dxf.rst:440 +msgid "" +"`AutoCAD 2014 DXF Reference " +"<http://images.autodesk.com/adsk/files/autocad_2014_pdf_dxf_reference_enu.pdf>`__" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:10 +msgid "" +"This driver reads files encoded in the French EDIGEO exchange format, a " +"text based file format aimed at exchanging geographical information " +"between GIS, with powerful description capabilities, topology modeling, " +"etc." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:15 +msgid "" +"The driver has been developed to read files of the French PCI (Plan " +"Cadastral Informatisé - Digital Cadastral Plan) as produced by the DGI " +"(Direction Générale des Impots - General Tax Office). The driver should " +"also be able to open other EDIGEO based products." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:20 +msgid "" +"The driver must be provided with the .THF file describing the EDIGEO " +"exchange and it will read the associated .DIC, .GEO, .SCD, .QAL and .VEC " +"files." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:24 +msgid "" +"In order the SRS of the layers to be correctly built, the IGNF file that " +"contains the definition of IGN SRS must be placed in the directory of " +"PROJ resource files." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:28 +msgid "" +"The whole set of files will be parsed into memory. This may be a " +"limitation if dealing with big EDIGEO exchanges." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:56 +msgid "Labels" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:58 +msgid "" +"For EDIGEO PCI files, the labels are contained in the ID_S_OBJ_Z_1_2_2 " +"layer. OGR will export styling following the :ref:`ogr_feature_style`." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:61 +msgid "It will also add the following fields :" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:63 +msgid "OGR_OBJ_LNK: the id of the object that is linked to this label" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:64 +msgid "OBJ_OBJ_LNK_LAYER: the name of the layer of the linked object" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:65 +msgid "" +"OGR_ATR_VAL: the value of the attribute to display (found in the ATR " +"attribute of the OGR_OBJ_LNK object)" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:67 +msgid "" +"OGR_ANGLE: the rotation angle in degrees (0 = horizontal, counter-clock-" +"wise oriented)" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:69 +msgid "" +"OGR_FONT_SIZE: the value of the HEI attribute multiplied by the value of " +"the configuration option :config:`OGR_EDIGEO_FONT_SIZE_FACTOR`." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:72 +msgid "" +"Combined with the FON (font family) attributes, they can be used to " +"define the styling in QGIS for example." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:75 +msgid "" +"By default, OGR will create specific layers (xxx_LABEL) to dispatch into " +"the various labels of the ID_S_OBJ_Z_1_2_2 layer according to the value " +"of xxx=OBJ_OBJ_LNK_LAYER. This can be disabled by setting " +":config:`OGR_EDIGEO_CREATE_LABEL_LAYERS` to NO." +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:83 +msgid "" +"`Introduction to the EDIGEO standard " +"<http://georezo.net/wiki/main/donnees/edigeo>`__ (in French)" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:85 +msgid "" +"`EDIGEO standard - AFNOR NF Z 52000 " +"<http://georezo.net/wiki/_media/main/geomatique/norme_edigeo.zip>`__ (in " +"French)" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:88 +msgid "" +"`Standard d'échange des objets du PCI selon la norme EDIGEO " +"<https://www.craig.fr/sites/www.craig.fr/files/contenu/60-2010-le-pci-en-" +"auvergne/docs/edigeopci.pdf>`__ (in French)" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:91 +msgid "" +"`Homepage of the French Digital Cadastral Plan " +"<http://www.cadastre.gouv.fr>`__ (in French)" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:93 +msgid "" +"`Geotools EDIGEO module description " +"<http://old.geotools.org/77692976.html>`__ (in English), `unmaintained " +"and removed <https://github.com/geotools/geotools/pull/2446/files>`__" +msgstr "" + +#: ../../source/drivers/vector/edigeo.rst:96 +msgid "" +"`Sample of EDIGEO data " +"<https://github.com/geotools/geotools/tree/affa340d16681f1bb78673d23fb38a6c1eb2b38a/modules/unsupported/edigeo/src/test/resources/org/geotools/data/edigeo" +"/test-data>`__" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:8 +msgid "EEDA" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:12 +msgid "" +"The driver supports read-only operations to list images and their " +"metadata as a vector layer, using Google Earth Engine REST API." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:23 +msgid "The minimal syntax to open a datasource is:" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:29 +msgid "" +"where collection is something like projects/earthengine-" +"public/assets/COPERNICUS/S2." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:48 +msgid "" +"Authentication Bearer header passed through the EEDA_BEARER or " +":config:`EEDA_BEARER_FILE` configuration options." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:56 +msgid "" +"Finally if none of the above method succeeds, the code will check if the " +"current machine is a Google Compute Engine instance, and if so will use " +"the permissions associated to it (using the default service account " +"associated with the VM). To force a machine to be detected as a GCE " +"instance you can set :config:`CPL_MACHINE_IS_GCE` to YES." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:68 +msgid ":copy-config:`EEDA_BEARER`" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:70 +msgid ":copy-config:`EEDA_BEARER_FILE`" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:72 +msgid ":copy-config:`GOOGLE_APPLICATION_CREDENTIALS`" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:74 +msgid ":copy-config:`EEDA_PRIVATE_KEY`" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:76 +msgid ":copy-config:`EEDA_PRIVATE_KEY_FILE`" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:78 +msgid ":copy-config:`EEDA_CLIENT_EMAIL`" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:89 +#: ../../source/drivers/vector/plscenes_data_v1.rst:134 +msgid "Attributes" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:91 +msgid "" +"The layer field definition is built by requesting a single image from the" +" collection and guessing the schema from its \"properties\" element. The " +"\"eedaconf.json\" file from the GDAL configuration will also be read to " +"check if the collection schema is described in it, in which case the " +"above mentioned schema guessing will not done." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:97 +msgid "The following attributes will always be present:" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:103 +msgid "Field name" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:103 +msgid "Meaning" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:103 +msgid "Server-side filter compatible" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:105 +msgid "name" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:105 +#: ../../source/drivers/vector/eeda.rst:109 +#: ../../source/drivers/vector/eeda.rst:112 +#: ../../source/drivers/vector/eeda.rst:114 +#: ../../source/drivers/vector/eeda.rst:143 +#: ../../source/drivers/vector/eeda.rst:145 +#: ../../source/drivers/vector/netcdf.rst:84 +#: ../../source/drivers/vector/netcdf.rst:125 +#: ../../source/drivers/vector/netcdf.rst:126 +#: ../../source/drivers/vector/selafin.rst:103 +msgid "String" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:105 +msgid "" +"Image name (e.g. projects/earthengine-public/ " +"assets/COPERNICUS/S2/20170430T190351\\_ 20170430T190351_T10SEG)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:109 +msgid "id" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:109 +msgid "" +"Image ID; equivalent to name without the \"projects/\\*/assets/\" prefix " +"(e.g. users/USER/ASSET)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:112 +msgid "path" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:112 +msgid "(Deprecated) Image path; equivalent to id" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:114 +msgid "gdal_dataset" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:114 +msgid "" +"GDAL dataset name (e.g. EEDAI:projects/earthengine-public/ " +"assets/COPERNICUS/S2/ 20170430T190351_20170430T190351\\_ T10SEG) that can" +" be opened with the :ref:`raster.eedai` driver" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:121 +msgid "startTime" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:121 +#: ../../source/drivers/vector/eeda.rst:124 +#: ../../source/drivers/vector/eeda.rst:127 +#: ../../source/drivers/vector/netcdf.rst:92 +#: ../../source/drivers/vector/netcdf.rst:136 +msgid "DateTime" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:121 +msgid "Acquisition start date" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:121 +msgid "**Yes** (restricted to >= comparison on top level)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:124 +msgid "endTime" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:124 +msgid "Acquisition end date" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:124 +msgid "**Yes** (restricted to <= comparison on top level)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:127 +msgid "updateTime" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:127 +msgid "Update date" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:129 +msgid "sizeBytes" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:129 +#: ../../source/drivers/vector/netcdf.rst:88 +#: ../../source/drivers/vector/netcdf.rst:131 +#: ../../source/drivers/vector/netcdf.rst:132 +msgid "Integer64" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:129 +msgid "File size in bytes" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:131 +msgid "band_count" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:131 +#: ../../source/drivers/vector/eeda.rst:133 +#: ../../source/drivers/vector/eeda.rst:135 +#: ../../source/drivers/vector/netcdf.rst:85 +#: ../../source/drivers/vector/netcdf.rst:122 +#: ../../source/drivers/vector/netcdf.rst:123 +#: ../../source/drivers/vector/netcdf.rst:128 +#: ../../source/drivers/vector/netcdf.rst:129 +#: ../../source/drivers/vector/selafin.rst:80 +msgid "Integer" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:131 +msgid "Number of bands" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:133 +msgid "band_max_width" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:133 +msgid "Maximum width among bands" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:135 +msgid "band_max_height" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:135 +msgid "Maximum height among bands" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:137 +msgid "band_min_pixel_size" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:137 +#: ../../source/drivers/vector/eeda.rst:139 +#: ../../source/drivers/vector/eeda.rst:141 +#: ../../source/drivers/vector/netcdf.rst:89 +#: ../../source/drivers/vector/netcdf.rst:133 +#: ../../source/drivers/vector/netcdf.rst:135 +msgid "Real" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:137 +msgid "Minimum pixel size among bands" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:139 +msgid "band_upper_left_x" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:139 +msgid "X origin (only set if equal among all bands)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:141 +msgid "band_upper_left_y" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:141 +msgid "Y origin (only set if equal among all bands)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:143 +msgid "band_crs" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:143 +msgid "CRS as EPSG:XXXX or WKT (only set if equal among all bands)" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:145 +msgid "other_properties" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:145 +msgid "" +"Serialized JSON dictionary with key/value pairs where key is not a " +"standalone field" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:149 +msgid "" +"\"Server-side filter compatible\" means that when this field is included " +"in an attribute filter, it is forwarded to the server (otherwise only " +"client-side filtering is done)." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:156 +msgid "" +"The footprint of each image is reported as a MultiPolygon with a " +"longitude/latitude WGS84 coordinate system (EPSG:4326)." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:162 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server. It also makes the same for simple attribute filters set with" +" SetAttributeFilter(). The 3 boolean operators (AND, OR, NOT) and the " +"comparison operators (=, <>, <, <=, > and >=) are supported." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:170 +msgid "" +"Features are retrieved from the server by chunks of 1000 by default (and " +"this is the maximum value accepted by the server). This number can be " +"altered with the :config:`EEDA_PAGE_SIZE` configuration option." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:175 +msgid "Extent and feature count" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:177 +msgid "" +"The reported extent and feature count will always be respectively " +"(-180,-90,180,90) and -1, given there is no way to get efficient answer " +"to those queries from the server." +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:184 +msgid "Listing all images available:" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:196 +msgid "Listing all images under a point of (lat,lon)=(40,-100) :" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:202 +msgid "Listing all images available matching criteria :" +msgstr "" + +#: ../../source/drivers/vector/eeda.rst:211 +msgid ":ref:`Google Earth Engine Data API Image driver <raster.eedai>`" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:6 +msgid "Elasticsearch" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:10 +msgid "Driver is read-write starting with GDAL 2.1" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:13 +msgid "" +"As of GDAL 2.1, Elasticsearch 1.X and, partially, 2.X versions are " +"supported (5.0 known not to work). GDAL 2.2 adds supports for " +"Elasticsearch 2.X and 5.X" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:15 +msgid "" +"`Elasticsearch <http://elasticsearch.org/>`__ is an Enterprise-level " +"search engine for a variety of data sources. It supports full-text " +"indexing and geospatial querying of those data in a fast and efficient " +"manor using a predefined REST API." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:28 +msgid "Opening dataset name syntax" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:30 +msgid "" +"Starting with GDAL 2.1, the driver supports reading existing indices from" +" a Elasticsearch host. There are two main possible syntaxes to open a " +"dataset:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:34 +msgid "Using *ES:http://hostname:port* (where port is typically 9200)" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:35 +msgid "Using *ES:* with the open options to specify HOST and PORT" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:38 +msgid "Layer open options" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:147 +msgid "Elasticsearch vs OGR concepts" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:149 +msgid "" +"Each mapping type inside a Elasticsearch index will be considered as a " +"OGR layer. A Elasticsearch document is considered as a OGR feature." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:153 +#: ../../source/drivers/vector/georss.rst:72 +msgid "Field definitions" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:155 +msgid "" +"Fields are dynamically mapped from the input OGR data source. However, " +"the driver will take advantage of advanced options within Elasticsearch " +"as defined in a `field mapping file " +"<http://code.google.com/p/ogr2elasticsearch/wiki/ModifyingtheIndex>`__." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:160 +msgid "" +"The mapping file allows you to modify the mapping according to the " +"`Elasticsearch field-specific types " +"<http://www.elasticsearch.org/guide/reference/mapping/core-" +"types.html>`__. There are many options to choose from, however, most of " +"the functionality is based on all the different things you are able to do" +" with text fields within Elasticsearch." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:172 +msgid "Geometry types" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:174 +msgid "" +"In GDAL 2.0 and earlier, the driver was limited in the geometry it " +"handles: even if polygons were provided as input, they were stored as " +"`geo point " +"<http://www.elasticsearch.org/guide/en/elasticsearch/reference/current" +"/mapping-geo-point-type.html>`__ and the \"center\" of the polygon is " +"used as value of the point. Starting with GDAL 2.1, `geo_shape " +"<https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-" +"geo-shape-type.html>`__ is used to store all geometry types (except curve" +" geometries that are not handled by Elasticsearch and will be " +"approximated to their linear equivalents)." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:188 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:191 +msgid "" +"Starting with GDAL 2.2, SQL attribute filters set with " +"SetAttributeFilter() are converted to `Elasticsearch filter syntax " +"<https://www.elastic.co/guide/en/elasticsearch/reference/current/query-" +"dsl-filters.html>`__. They will be combined with the potentially defined " +"spatial filter." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:196 +msgid "" +"It is also possible to directly use a Elasticsearch filter by setting the" +" string passed to SetAttributeFilter() as a JSON serialized object, e.g." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:204 +msgid "" +"Note: if defining directly an Elastic Search JSON filter, the spatial " +"filter specified through SetSpatialFilter() will be ignored, and must " +"thus be included in the JSON filter if needed." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:211 +msgid "" +"Features are retrieved from the server by chunks of 100. This can be " +"altered with the BATCH_SIZE open option." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:215 +#: ../../source/drivers/vector/gml.rst:175 +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:13 +#: ../../source/drivers/vector/libkml.rst:276 +#: ../../source/drivers/vector/mongodbv3.rst:172 +msgid "Schema" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:217 +msgid "" +"When reading a Elastic Search index/type, OGR must establish the schema " +"of attribute and geometry fields, since OGR has a fixed schema concept." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:220 +msgid "" +"In the general case, OGR will read the mapping definition and the first " +"100 documents (can be altered with the " +":oo:`FEATURE_COUNT_TO_ESTABLISH_FEATURE_DEFN` open option) of the " +"index/type and build the schema that best fit to the found fields and " +"values." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:225 +msgid "" +"It is also possible to set the :oo:`JSON_FIELD=YES` open option so that a" +" \\_json special field is added to the OGR schema. When reading Elastic " +"Search documents as OGR features, the full JSON version of the document " +"will be stored in the \\_json field. This might be useful in case of " +"complex documents or with data types that do not translate well in OGR " +"data types. On creation/update of documents, if the \\_json field is " +"present and set, its content will be used directly (other fields will be " +"ignored)." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:235 +#: ../../source/drivers/vector/mongodbv3.rst:199 +msgid "Feature ID" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:237 +msgid "" +"Elastic Search have a special \\_id field that contains the unique ID of " +"the document. This field is returned as an OGR field, but cannot be used " +"as the OGR special FeatureID field, which must be of integer type. By " +"default, OGR will try to read a potential 'ogc_fid' field to set the OGR " +"FeatureID. The name of this field to look up can be set with the FID open" +" option. If the field is not found, the FID returned by OGR will be a " +"sequential number starting at 1, but it is not guaranteed to be stable at" +" all." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:247 +#: ../../source/drivers/vector/mongodbv3.rst:211 +msgid "ExecuteSQL() interface" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:249 +msgid "" +"Starting with GDAL 2.2, SQL requests, involving a single layer, with " +"WHERE and ORDER BY statements will be translated as Elasticsearch " +"queries." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:253 +msgid "" +"Otherwise, if specifying \"ES\" as the dialect of ExecuteSQL(), a JSON " +"string with a serialized `Elastic Search filter " +"<https://www.elastic.co/guide/en/elasticsearch/reference/current/query-" +"dsl-filters.html>`__ can be passed. The search will be done on all " +"indices and types, unless the filter itself restricts the search. The " +"returned layer will be a union of the types returned by the " +":oo:`FEATURE_COUNT_TO_ESTABLISH_FEATURE_DEFN` first documents. It will " +"also contain the \\_index and \\_type special fields to indicate the " +"provenance of the features." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:263 +msgid "" +"The following filter can be used to restrict the search to the \"poly\" " +"index and its \"FeatureCollection\" type mapping (Elasticsearch 1.X and " +"2.X)" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:283 +msgid "For Elasticsearch 5.X (works also with 2.X) :" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:303 +msgid "" +"Aggregations are not supported through the ExecuteSQL() interface, but " +"through the below described mechanism." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:309 +msgid "Aggregations" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:313 +msgid "" +"The driver can support issuing aggregation requests to an index. " +"ElasticSearch aggregations can potentially be rather complex, so the " +"driver currently limits to geohash grid based spatial aggegrations, with " +"additional fields with statistical indicators (min, max, average, .), " +"which can be used for example to generate heatmaps. The specification of " +"the aggegation is done through the :oo:`AGGREGATION` open option, whose " +"value is a JSON serialized object whose members are:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:321 +msgid "``index`` (required): the name of the index to query." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:323 +msgid "" +"``geometry_field`` (optional): the path to the geometry field on which to" +" do `geohash grid aggregation " +"<https://www.elastic.co/guide/en/elasticsearch/reference/current/search-" +"aggregations-bucket-geohashgrid-aggregation.html>`__. For documents with " +"points encoded as GeoJSON, this will be for example " +"`geometry.coordinates`. When this property is not specified, the driver " +"will analyze the mapping and use the geometry field definition found into" +" it (provided there is a single one). Note that aggegration on geo_shape " +"geometries is only supported since Elasticsearch 7 and may require a non-" +"free license." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:331 +msgid "" +"``geohash_grid`` (optional): a JSON object, describing a few " +"characteristics of the geohash_grid, that can have the following members:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:334 +msgid "" +"``size`` (optional): maximum number of geohash buckets to return per " +"query. The default is 10,000. If ``precision`` is specified and the " +"number of results would exceed ``size``, then the server will trim the " +"results, by sorting by decreasing number of documents matched." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:339 +msgid "" +"``precision`` (optional): string length of the geohashes used to define " +"cells/buckets in the results, in the [1,12] range. A geohash of size 1 " +"can generate up to 32 buckets, of size 2 up to 32*32 buckets, etc. When " +"it is not specified, the driver will automatically compute a value, " +"taking into account the ``size`` parameter and the spatial filter, so " +"that the theoretical number of buckets returned does not exceed ``size``." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:346 +msgid "" +"``fields`` (optional): a JSON object, describing which additional " +"statistical fields should be added, that can have the following members:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:349 +msgid "" +"``min`` (optional): array with the paths to index properties on which to " +"compute the minimum during aggegation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:352 +msgid "" +"``max`` (optional): array with the paths to index properties on which to " +"compute the maximum during aggegation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:355 +msgid "" +"``avg`` (optional): array with the paths to index properties on which to " +"compute the average during aggegation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:358 +msgid "" +"``sum`` (optional): array with the paths to index properties on which to " +"compute the sum during aggegation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:361 +msgid "" +"``count`` (optional): array with the paths to index properties on which " +"to compute the value_count during aggegation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:364 +msgid "" +"``stats`` (optional): array with the paths to index properties on which " +"to compute all the above indicators during aggegation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:367 +msgid "" +"When using a GeoJSON mapping, the path to an index property is typically " +"``property.some_name``." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:370 +msgid "" +"When specifying the :oo:`AGGREGATION` open option, a single read-only " +"layer called ``aggregation`` will be returned. A spatial filter can be " +"set on it using the standard OGR SetSpatialFilter() API: it is applied " +"prior to aggregation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:374 +msgid "" +"An example of a potential value for the :oo:`AGGREGATION` open option can" +" be:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:392 +msgid "" +"It will return a layer with a Point geometry field and the following " +"fields:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:394 +msgid "" +"``key`` of type String: the value of the geohash of the corresponding " +"bucket" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:395 +msgid "" +"``doc_count`` of type Integer64: the number of matching documents in the " +"bucket" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:396 +msgid "``field_a_min`` of type Real" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:397 +msgid "``field_b_min`` of type Real" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:398 +msgid "``field_c_min`` of type Real" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:399 +msgid "``field_c_max`` of type Real" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:400 +msgid "``field_c_avg`` of type Real" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:401 +msgid "``field_c_sum`` of type Real" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:402 +msgid "``field_c_count`` of type Integer64" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:405 +msgid "Multi-target layers" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:409 +msgid "" +"The GetLayerByName() method accepts a layer name that can be a comma-" +"separated list of indices, potentially combined with the '*' wildcard " +"character. See " +"https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-" +"index.html. Note that in the current implementation, the field definition" +" will be established from the one of the matching layers, but not all, so" +" using this functionality will be appropriate when the multiple matching " +"layers share the same schema." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:417 +msgid "Getting metadata" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:419 +msgid "Getting feature count is efficient." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:421 +msgid "" +"Getting extent is efficient, only on geometry columns mapped to " +"Elasticsearch type geo_point. On geo_shape fields, feature retrieval of " +"the whole layer is done, which might be slow." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:428 +msgid "Index/type creation and deletion is possible." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:433 +msgid "" +"When inserting a new feature with CreateFeature() in non-bulk mode, and " +"if the command is successful, OGR will fetch the returned \\_id and use " +"it for the SetFeature() operation." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:438 +msgid "Spatial reference system" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:440 +msgid "" +"Geometries stored in Elastic Search are supposed to be referenced as " +"longitude/latitude over WGS84 datum (EPSG:4326). On creation, the driver " +"will automatically reproject from the layer (or geometry field) SRS to " +"EPSG:4326, provided that the input SRS is set and that is not already " +"EPSG:4326." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:449 +msgid "" +"|about-layer-creation-options| Starting with GDAL 2.1, the driver " +"supports the following layer creation options:" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:624 +msgid "" +"|about-config-options| The following (deprecated) configuration options " +"are available. Starting with GDAL 2.1, layer creation options are also " +"available and should be preferred (see above):" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:666 +msgid "**Open the local store:**" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:672 +msgid "**Open a remote store:**" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:678 +msgid "**Filtering on a Elastic Search field:**" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:684 +msgid "" +"**Using \"match\" query on Windows:** On Windows the query must be " +"between double quotes and double quotes inside the query must be escaped." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:692 +msgid "**Basic aggregation:**" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:698 +msgid "**Load an Elasticsearch index with a shapefile:**" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:704 +msgid "" +"**Create a Mapping File:** The mapping file allows you to modify the " +"mapping according to the `Elasticsearch field-specific types " +"<http://www.elasticsearch.org/guide/reference/mapping/core-" +"types.html>`__. There are many options to choose from, however, most of " +"the functionality is based on all the different things you are able to do" +" with text fields." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:715 +#: ../../source/drivers/vector/elasticsearch.rst:728 +#: ../../source/drivers/vector/elasticsearch.rst:743 +#: ../../source/drivers/vector/elasticsearch.rst:756 +msgid "or (GDAL >= 2.1):" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:721 +msgid "" +"**Read the Mapping File:** Reads the mapping file during the " +"transformation" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:734 +msgid "" +"**Bulk Uploading (for larger datasets):** Bulk loading helps when " +"uploading a lot of data. The integer value is the number of bytes that " +"are collected before being inserted. `Bulk size considerations " +"<https://www.elastic.co/guide/en/elasticsearch/guide/current/bulk.html#_how_big_is_too_big>`__" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:749 +msgid "" +"**Overwrite the current Index:** If specified, this will overwrite the " +"current index. Otherwise, the data will be appended." +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:765 +msgid "`Home page for Elasticsearch <http://elasticsearch.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:766 +msgid "`Examples Wiki <http://code.google.com/p/ogr2elasticsearch/w/list>`__" +msgstr "" + +#: ../../source/drivers/vector/elasticsearch.rst:767 +msgid "`Google Group <http://groups.google.com/group/ogr2elasticsearch>`__" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:6 +msgid "ESRIJSON" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:10 +#: ../../source/drivers/vector/topojson.rst:10 +msgid "" +"(Note: prior to GDAL 2.3, the functionality of this driver was available " +"in the GeoJSON driver. They are now distinct drivers)" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:13 +msgid "" +"This driver can read the JSON output of Feature Service requests " +"following the `GeoServices REST Specification " +"<http://www.esri.com/industries/landing-" +"pages/geoservices/geoservices.html>`__, like implemented by `ArcGIS " +"Server REST API " +"<http://help.arcgis.com/en/arcgisserver/10.0/apis/rest/index.html>`__. " +"The driver can scroll through such result sets that are spread over " +"multiple pages (for ArcGIS servers >= 10.3). This is automatically " +"enabled if URL does not contain an explicit *resultOffset* parameter. If " +"it contains this parameter and scrolling is still desired, the " +":oo:`FEATURE_SERVER_PAGING` open option must be set to YES. The page size" +" can be explicitly set with the *resultRecordCount* parameter (but is " +"subject to a server limit). If it is not set, OGR will set it to the " +"maximum value allowed by the server." +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:27 +msgid "" +"Note: for paged requests to work properly, it is generally necessary to " +"add a sort clause on a field, typically the OBJECTID with a " +"\"&orderByFields=OBJECTID+ASC\" parameter in the URL, so that the server " +"returns the results in a reliable way." +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:40 +#: ../../source/drivers/vector/geojson.rst:39 +#: ../../source/drivers/vector/geojsonseq.rst:37 +#: ../../source/drivers/vector/libkml.rst:41 +#: ../../source/drivers/vector/topojson.rst:24 +msgid "Datasource" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:42 +#: ../../source/drivers/vector/geojsonseq.rst:39 +#: ../../source/drivers/vector/topojson.rst:26 +msgid "The driver accepts three types of sources of data:" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:44 +#: ../../source/drivers/vector/topojson.rst:28 +msgid "" +"Uniform Resource Locator (`URL <http://en.wikipedia.org/wiki/URL>`__) - a" +" Web address to perform `HTTP <http://en.wikipedia.org/wiki/HTTP>`__ " +"request." +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:47 +msgid "" +"Plain text file with ESRIJSON data - identified from the file extension " +".json" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:49 +msgid "Text passed directly and encoded in ESRI JSON" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:51 +msgid "" +"Starting with GDAL 2.3, the URL/filename/text might be prefixed with " +"ESRIJSON: to avoid any ambiguity with other drivers. Alternatively, " +"starting with GDAL 3.10, specifying the ``-if ESRIJSON`` option to " +"command line utilities accepting it, or ``ESRIJSON`` as the only value of" +" the ``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the " +"driver to recognize the passed URL/filename/text." +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:75 +msgid "" +"Read the result of a FeatureService request against a GeoServices REST " +"server (note that this server does not support paging):" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:85 +#: ../../source/drivers/vector/geojsonseq.rst:145 +#: ../../source/drivers/vector/jsonfg.rst:237 +#: ../../source/drivers/vector/topojson.rst:45 +msgid ":ref:`GeoJSON driver <vector.geojson>`" +msgstr "" + +#: ../../source/drivers/vector/esrijson.rst:86 +msgid "" +"`GeoServices REST Specification <http://www.esri.com/industries/landing-" +"pages/geoservices/geoservices.html>`__" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:6 +msgid "FileGDB" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:10 +msgid "" +"The FileGDB driver provides read and write access to vector layers of " +"File Geodatabases (.gdb directories) created by ArcGIS 10 and above. The " +"dataset name must be the directory/folder name, and it must end with the " +".gdb extension." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:15 +msgid "" +"Note : the :ref:`OpenFileGDB driver <vector.openfilegdb>` driver exists " +"as an alternative built-in (i.e. not depending on a third-party library) " +"driver." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:26 +#: ../../source/drivers/vector/geopackage_aspatial.rst:67 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:66 +msgid "Requirements" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:28 +msgid "" +"`FileGDB API SDK " +"<http://www.esri.com/apps/products/download/#File_Geodatabase_API_1.3>`__" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:30 +msgid "Curve in geometries are supported on reading with GDAL >= 2.2." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:33 +msgid "Bulk feature loading" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:35 +msgid "" +"The :config:`FGDB_BULK_LOAD` configuration option can be set to YES to " +"speed-up feature insertion (or sometimes solve problems when inserting a " +"lot of features (see http://trac.osgeo.org/gdal/ticket/4420). The effect " +"of this configuration option is to cause a write lock to be taken and a " +"temporary disabling of the indexes. Those are restored when the " +"datasource is closed or when a read operation is done." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:42 +msgid "" +"Bulk load is enabled by default for newly created layers (unless " +"otherwise specified)." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:46 +#: ../../source/drivers/vector/openfilegdb.rst:54 +#: ../../source/drivers/vector/parquet.rst:169 +msgid "SQL support" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:48 +msgid "" +"SQL statements are run through the SQL engine of the FileGDB SDK API. " +"This holds for non-SELECT statements. However, due to partial/inaccurate " +"support for SELECT statements in current FileGDB SDK API versions (v1.2)," +" SELECT statements will be run by default by the OGR SQL engine. This can" +" be changed by specifying the *-dialect FileGDB* option to ogrinfo or " +"ogr2ogr." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:56 +#: ../../source/drivers/vector/openfilegdb.rst:61 +#: ../../source/drivers/vector/pgeo.rst:52 +msgid "Special SQL requests" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:58 +msgid "" +"\"GetLayerDefinition a_layer_name\" and \"GetLayerMetadata a_layer_name\"" +" can be used as special SQL requests to get respectively the definition " +"and metadata of a FileGDB table as XML content." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:62 +msgid "" +"Starting with GDAL 3.5, the \"REPACK\" special SQL request can be issued " +"to ask for database compaction." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:66 +#: ../../source/drivers/vector/openfilegdb.rst:251 +#: ../../source/drivers/vector/pgeo.rst:89 +msgid "Field domains" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:70 +msgid "" +"Retrieving coded and range field domains are supported. Writing support " +"has been added in GDAL 3.5." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:74 +#: ../../source/drivers/vector/gpkg.rst:173 +#: ../../source/drivers/vector/openfilegdb.rst:258 +#: ../../source/drivers/vector/pgeo.rst:96 +#: ../../source/drivers/vector/sqlite.rst:231 +msgid "Relationships" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:78 +#: ../../source/drivers/vector/pgeo.rst:100 +msgid "Relationship retrieval is supported." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:81 +#: ../../source/drivers/vector/openfilegdb.rst:265 +msgid "Hiearchical organization" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:85 +msgid "" +"The hiearchical organization of tables and feature classes as top-level " +"element or within a feature dataset can be explored using the methods " +":cpp:func:`GDALDataset::GetRootGroup`, " +":cpp:func:`GDALGroup::GetGroupNames`, :cpp:func:`GDALGroup::OpenGroup`, " +":cpp:func:`GDALGroup::GetVectorLayerNames` and " +":cpp:func:`GDALGroup::OpenVectorLayer`" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:92 +#: ../../source/drivers/vector/gpkg.rst:168 +#: ../../source/drivers/vector/mssqlspatial.rst:284 +#: ../../source/drivers/vector/openfilegdb.rst:276 +#: ../../source/drivers/vector/sqlite.rst:226 +msgid "Transaction support" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:94 +msgid "" +"The FileGDB driver implements transactions at the database level, through" +" an emulation (as per :ref:`rfc-54`), since the FileGDB SDK itself does " +"not offer it. This works by backing up the current state of a geodatabase" +" when StartTransaction(force=TRUE) is called. If the transaction is " +"committed, the backup copy is destroyed. If the transaction is rolled " +"back, the backup copy is restored. So this might be costly when operating" +" on huge geodatabases." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:102 +msgid "" +"Starting with GDAL 2.1, on Linux/Unix, instead of a full backup copy only" +" layers that are modified are backed up." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:105 +#: ../../source/drivers/vector/openfilegdb.rst:285 +msgid "" +"Note that this emulation has an unspecified behavior in case of " +"concurrent updates (with different connections in the same or another " +"process)." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:110 +msgid "CreateFeature() support" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:112 +msgid "" +"The FileGDB SDK API does not allow to create a feature with a FID " +"specified by the user. Starting with GDAL 2.1, the FileGDB driver " +"implements a special FID remapping technique to enable the user to create" +" features at the FID of their choice." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:119 +#: ../../source/drivers/vector/flatgeobuf.rst:55 +#: ../../source/drivers/vector/geoconcept.rst:82 +#: ../../source/drivers/vector/hana.rst:174 +#: ../../source/drivers/vector/mitab.rst:106 +#: ../../source/drivers/vector/openfilegdb.rst:116 +#: ../../source/drivers/vector/pg.rst:238 +#: ../../source/drivers/vector/pgdump.rst:35 +msgid "Dataset Creation Options" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:121 +#: ../../source/drivers/vector/openfilegdb.rst:118 +msgid "None." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:124 +#: ../../source/drivers/vector/flatgeobuf.rst:60 +#: ../../source/drivers/vector/geoconcept.rst:153 +#: ../../source/drivers/vector/hana.rst:179 +#: ../../source/drivers/vector/mitab.rst:143 +#: ../../source/drivers/vector/mssqlspatial.rst:106 +#: ../../source/drivers/vector/mysql.rst:104 +#: ../../source/drivers/vector/oci.rst:136 +#: ../../source/drivers/vector/openfilegdb.rst:121 +#: ../../source/drivers/vector/pg.rst:243 +#: ../../source/drivers/vector/pgdump.rst:51 +msgid "Layer Creation Options" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:167 +#: ../../source/drivers/vector/openfilegdb.rst:176 +msgid "" +"ArcMap 10.0 and OGR defaults for XYTOLERANCE are 0.001m (or equivalent) " +"for projected coordinate systems, and 0.000000008983153° for geographic " +"coordinate systems. ArcMap 10.0 and OGR defaults for ZTOLERANCE and " +"MTOLERANCE are 0.0001." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:179 +msgid "" +"**XORIGIN, YORIGIN, ZORIGIN, MORIGIN, XYSCALE, ZSCALE, MSCALE**: These " +"parameters control the `coordinate precision grid " +"<http://help.arcgis.com/en/sdk/10.0/java_ao_adf/conceptualhelp/engine/index.html#//00010000037m000000>`__" +" inside the file geodatabase. The dimensions of the grid are determined " +"by the origin, and the scale. The origin defines the location of a " +"reference grid point in space. The scale is the reciprocal of the " +"resolution. So, to get a grid with an origin at 0 and a resolution of " +"0.001 on all axes, you would set all the origins to 0 and all the scales " +"to 1000." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:189 +#: ../../source/drivers/vector/openfilegdb.rst:191 +msgid "" +"*Important*: The domain specified by ``(xmin=XORIGIN, ymin=YORIGIN, " +"xmax=(XORIGIN + 9E+15 / XYSCALE), ymax=(YORIGIN + 9E+15 / XYSCALE))`` " +"needs to encompass every possible coordinate value for the feature class." +" If features are added with coordinates that fall outside the domain, " +"errors will occur in ArcGIS with spatial indexing, feature selection, and" +" exporting data." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:196 +#: ../../source/drivers/vector/openfilegdb.rst:198 +msgid "ArcMap 10.0 and OGR defaults:" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:198 +#: ../../source/drivers/vector/openfilegdb.rst:200 +msgid "" +"For geographic coordinate systems: XORIGIN=-400, YORIGIN=-400, " +"XYSCALE=1000000000" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:200 +#: ../../source/drivers/vector/openfilegdb.rst:202 +msgid "" +"For projected coordinate systems: XYSCALE=10000 for the default " +"XYTOLERANCE of 0.001m. XORIGIN and YORIGIN change based on the coordinate" +" system, but the OGR default of -2147483647 is suitable with the default " +"XYSCALE for all coordinate systems." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:204 +#: ../../source/drivers/vector/openfilegdb.rst:206 +msgid "ZORIGIN and MORIGIN: -100000" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:205 +#: ../../source/drivers/vector/openfilegdb.rst:207 +msgid "ZSCALE and MSCALE: 10000" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:207 +msgid "MORIGIN and MSCALE added in GDAL 3.5.1" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:261 +#: ../../source/drivers/vector/geojson.rst:491 +#: ../../source/drivers/vector/geojsonseq.rst:124 +#: ../../source/drivers/vector/gml.rst:1319 +#: ../../source/drivers/vector/gpkg.rst:701 +#: ../../source/drivers/vector/jsonfg.rst:196 +#: ../../source/drivers/vector/openfilegdb.rst:290 +msgid "Geometry coordinate precision" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:263 +#: ../../source/drivers/vector/geojson.rst:493 +#: ../../source/drivers/vector/geojsonseq.rst:126 +#: ../../source/drivers/vector/gml.rst:1321 +#: ../../source/drivers/vector/gpkg.rst:703 +#: ../../source/drivers/vector/jsonfg.rst:198 +#: ../../source/drivers/vector/openfilegdb.rst:292 +msgid "3.9" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:265 +#: ../../source/drivers/vector/openfilegdb.rst:294 +msgid "" +"The driver supports reading and writing the geometry coordinate " +"precision, using the XYResolution, ZResolution and MResolution members of" +" the :cpp:class:`OGRGeomCoordinatePrecision` settings of the " +":cpp:class:`OGRGeomFieldDefn`. ``XYScale`` is computed as 1.0 / " +"``XYResolution`` (and similarly for the Z and M components). The " +"tolerance setting is computed as being one tenth of the resolution" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:272 +#: ../../source/drivers/vector/openfilegdb.rst:301 +msgid "" +"On reading, the coordinate precision grid parameters are returned as " +"format specific options of :cpp:class:`OGRGeomCoordinatePrecision` with " +"the ``FileGeodatabase`` format key, with the following option key names: " +"``XYScale``, ``XYTolerance``, ``XYOrigin``, ``ZScale``, ``ZTolerance``, " +"``ZOrigin``, ``MScale``, ``MTolerance``, ``MOrigin``. On writing, they " +"are also honored (they will have precedence over XYResolution, " +"ZResolution and MResolution)." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:280 +#: ../../source/drivers/vector/openfilegdb.rst:309 +msgid "" +"On layer creation, the XORIGIN, YORIGIN, ZORIGIN, MORIGIN, XYSCALE, " +"ZSCALE, ZORIGIN, XYTOLERANCE, ZTOLERANCE, MTOLERANCE layer creation " +"options will be used in priority over the settings of " +":cpp:class:`OGRGeomCoordinatePrecision`." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:287 +msgid "" +"The SDK is known to be unable to open layers with particular spatial " +"reference systems. This might be the case if messages \"FGDB: Error " +"opening XXXXXXX. Skipping it (Invalid function arguments.)\" when running" +" ``ogrinfo --debug on the.gdb`` (reported as warning in GDAL 2.0). Using " +"the OpenFileGDB driver will generally solve that issue." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:293 +msgid "" +"FGDB coordinate snapping will cause geometries to be altered during " +"writing. Use the origin and scale layer creation options to control the " +"snapping behavior." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:297 +msgid "" +"Reading data compressed in SDC format (Smart Data Compression) is not " +"support by the driver, because it is not supported by the ESRI SDK." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:300 +msgid "" +"Reading data compressed in CDF format (Compressed Data Format) requires " +"ESRI SDK 1.4 or later." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:303 +msgid "" +"Some applications create FileGeodatabases with non-spatial tables which " +"are not present in the GDB_Items metadata table. These tables cannot be " +"opened by the ESRI SDK, so GDAL will automatically fallback to the " +"OpenFileGDB driver to read these tables. Accordingly they will be opened " +"with the limitations of the OpenFileGDB driver (for instance, they will " +"be read only)." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:310 +msgid "The driver does not support 64-bit integers." +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:315 +msgid "" +"`ESRI File Geodatabase API Page <https://github.com/Esri/file-" +"geodatabase-api/>`__" +msgstr "" + +#: ../../source/drivers/vector/filegdb.rst:317 +msgid "" +":ref:`OpenFileGDB driver <vector.openfilegdb>`, not depending on a third-" +"party library/SDK" +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:12 +msgid "" +"This driver implements read/write support for access to features encoded " +"in `FlatGeobuf <https://github.com/bjornharrtell/flatgeobuf>`__ format, a" +" performant binary encoding for geographic data based on flatbuffers that" +" can hold a collection of Simple Features." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:27 +msgid "Multi layer support" +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:29 +msgid "" +"A single .fgb file only contains one single layer. For multiple layer " +"support, it is possible to put several .fgb files in a directory, and use" +" that directory name as the connection string." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:33 +msgid "" +"On creation, passing a filename without a .fgb suffix will instruct the " +"driver to create a directory of that name, and create layers as .fgb " +"files in that directory." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:37 +msgid "" +"Starting with GDAL 3.9, metadata set at the layer level will be written " +"in the FlatGeobuf header, and retrieved on reading as layer metadata." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:57 +#: ../../source/drivers/vector/geopackage_aspatial.rst:144 +#: ../../source/drivers/vector/geopackage_aspatial.rst:149 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:88 +#: ../../source/drivers/vector/hana.rst:176 +#: ../../source/drivers/vector/miramon.rst:291 +#: ../../source/drivers/vector/pg.rst:240 +#: ../../source/drivers/vector/shapefile.rst:343 +msgid "None" +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:96 +msgid "" +"Currently, NULL geometries are not supported with " +":lco:`SPATIAL_INDEX=YES`." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:98 +msgid "" +"`More background and dicussion on this issue at " +"<https://github.com/flatgeobuf/flatgeobuf/discussions/260>`__" +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:100 +msgid "" +"The creation of the packet Hilbert R-Tree requires an amount of RAM which" +" is at least the number of features times 83 bytes." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:106 +msgid "" +"Simple translation of a single shapefile into a FlatGeobuf file. The file" +" 'filename.fgb' will be created with the features from abc.shp and " +"attributes from abc.dbf. The file ``filename.fgb`` must **not** already " +"exist, as it will be created." +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:115 +msgid "Conversion of a Geopackage file with multiple layers:" +msgstr "" + +#: ../../source/drivers/vector/flatgeobuf.rst:124 +msgid "`FlatGeobuf at GitHub <https://github.com/bjornharrtell/flatgeobuf>`__" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:6 +msgid "Geoconcept" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:10 +#: ../../source/drivers/vector/geoconcept.rst:41 +msgid "GeoConcept text export files should be available for writing and reading." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:13 +#: ../../source/drivers/vector/geoconcept.rst:44 +msgid "" +"The OGR GeoConcept driver treats a single GeoConcept file within a " +"directory as a dataset comprising layers. GeoConcept files extensions are" +" ``.txt`` or ``.gxt``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:17 +#: ../../source/drivers/vector/geoconcept.rst:48 +msgid "" +"Currently the GeoConcept driver only supports multi-polygons, lines and " +"points." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:30 +msgid "GeoConcept Text File Format (gxt)" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:32 +msgid "GeoConcept is a GIS developed by the Company GeoConcept SA." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:34 +msgid "" +"It's an object oriented GIS, where the features are named « objects », " +"and feature types are named « type/subtype » (class allowing " +"inheritance)." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:38 +msgid "" +"Among its import/export formats, it proposes a simple text format named " +"gxt. A gxt file may contain objects from several type/subtype." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:54 +msgid "" +"The GeoConcept driver treats a GeoConcept file (``.txt`` or ``.gxt``) as " +"a dataset." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:57 +msgid "" +"GeoConcept files can store multiple kinds of geometry (one by layer), " +"even if a GeoConcept layer can only have one kind of geometry." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:60 +msgid "" +"Note this makes it very difficult to translate a mixed geometry layer " +"from another format into GeoConcept format using ogr2ogr, since ogr2ogr " +"has no support for separating out geometries from a source layer." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:64 +msgid "" +"GeoConcept sub-type is treated as OGR feature. The name of a layer is " +"therefore the concatenation of the GeoConcept type name, ``'.'`` and " +"GeoConcept sub-type name." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:68 +msgid "GeoConcept type definition (``.gct`` files) are used for creation only." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:70 +msgid "" +"GeoConcept feature fields definition are stored in an associated ``.gct``" +" file, and so fields suffer a number of limitations (FIXME) :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:73 +msgid "Attribute names are not limited in length." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:74 +msgid "" +"Only Integer, Real and String field types are supported. The various " +"list, and other field types cannot be created for the moment (they exist " +"in the GeoConcept model, but are not yet supported by the GeoConcept " +"driver)." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:79 +msgid "The OGR GeoConcept driver does not support deleting features." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:101 +msgid "" +"It is important to note that a GeoConcept export file can hold different " +"types and associated sub-types." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:104 +msgid "" +"configuration section : the GCT file starts with ``//#SECTION CONFIG`` " +"and ends with ``//#ENDSECTION CONFIG``. All the configuration is enclosed" +" within these marks." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:107 +msgid "" +"map section : purely for documentation at the time of writing this " +"document. This section starts with ``//#SECTION MAP`` and ends with " +"``//#ENDSECTION MAP``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:110 +msgid "" +"type section : this section defines a class of features. A type has a " +"name (keyword ``Name``) and an ID (keyword ``ID``). A type holds sub-" +"types and fields. This section starts with ``//#SECTION TYPE`` and ends " +"with ``//#ENDSECTION TYPE``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:115 +msgid "" +"sub-type section : this sub-section defines a kind og features within a " +"class. A sub-type has a name (keyword ``Name``), an ID (keyword ``ID``), " +"a type of geometry (keyword ``Kind``) and a dimension. The following " +"types of geometry are supported : POINT, LINE, POLYGON. The current " +"release of this driver does not support the TEXT geometry. The dimension " +"can be 2D, 3DM or 3D. A sub-type holds fields. This section starts with " +"``//#SECTION SUBTYPE`` and ends with ``//#ENDSECTION SUBTYPE``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:124 +msgid "" +"fields section : defines user fields. A field has a name (keyword " +"``Name``), an ID (keyword ``ID``), a type (keyword ``Kind``). The " +"following types of fields are supported : INT, REAL, MEMO, CHOICE, DATE, " +"TIME, LENGTH, AREA. This section starts with ``//#SECTION FIELD`` and " +"ends with ``//#ENDSECTION FIELD``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:131 +msgid "field section : defines type fields. See above." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:133 +msgid "" +"field section : defines general fields. Out of these, the following rules" +" apply :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:136 +msgid "" +"private field names start with a '@' : the private fields are " +"``Identifier``, ``Class``, ``Subclass``, ``Name``, ``NbFields``, ``X``, " +"``Y``, ``XP``, ``YP``, ``Graphics``, ``Angle``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:139 +msgid "" +"some private field are mandatory (they must appear in the configuration) " +": ``Identifier``, ``Class``, ``Subclass``, ``Name``, ``X``, ``Y``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:142 +msgid "" +"If the sub-type is linear (LINE), then the following fields must be " +"declared ``XP``, ``YP``." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:144 +msgid "" +"If the sub-type is linear or polygonal (LINE, POLY), then ``Graphics`` " +"must be declared." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:146 +msgid "" +"If the sub-type is ponctual or textual (POINT, TEXT), the ``Angle`` may " +"be declared." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:149 +msgid "" +"When this option is not used, the driver manage types and sub-types name " +"based on either the layer name or on the use of ``-nln`` option." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:166 +msgid "" +"At the present moment, coordinates are written with 2 decimals for " +"Cartesian spatial reference systems (including height) or with 9 decimals" +" for geographical spatial reference systems." +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:174 +msgid "Example of a .gct file :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:247 +msgid "Example of a GeoConcept text export :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:265 +msgid "Example of use :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:267 +msgid "Creating a GeoConcept export file :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:273 +msgid "Appending new features to an existing GeoConcept export file :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:279 +msgid "Translating a GeoConcept export file layer into MapInfo file :" +msgstr "" + +#: ../../source/drivers/vector/geoconcept.rst:288 +msgid "`GeoConcept web site <http://www.geoconcept.com/>`__" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:10 +msgid "" +"This driver implements read/write support for access to features encoded " +"in `GeoJSON <http://geojson.org/>`__ format. GeoJSON is a dialect based " +"on the `JavaScript Object Notation (JSON) <http://json.org/>`__. JSON is " +"a lightweight plain text format for data interchange and GeoJSON is " +"nothing other than its specialization for geographic content." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:16 +msgid "" +"GeoJSON is supported as an output format of a number of services: " +"`GeoServer " +"<http://docs.geoserver.org/2.6.x/en/user/services/wfs/outputformats.html>`__," +" `CartoWeb <http://exportgge.sourceforge.net/kml/>`__, etc." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:20 +msgid "" +"The OGR GeoJSON driver translates GeoJSON encoded data to objects of the " +"`OGR Simple Features model <ogr_arch.html>`__: Datasource, Layer, " +"Feature, Geometry. The implementation is based on `GeoJSON Specification," +" v1.0 <http://geojson.org/geojson-spec.html>`__." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:25 +msgid "" +"Starting with GDAL 2.1.0, the GeoJSON driver supports updating existing " +"GeoJSON files. In that case, the default value for the NATIVE_DATA open " +"option will be YES." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:41 +msgid "The OGR GeoJSON driver accepts three types of sources of data:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:43 +#: ../../source/drivers/vector/geojsonseq.rst:41 +#: ../../source/drivers/vector/jsonfg.rst:46 +msgid "" +"Uniform Resource Locator (`URL <http://en.wikipedia.org/wiki/URL>`__) - a" +" Web address to perform `HTTP <http://en.wikipedia.org/wiki/HTTP>`__ " +"request" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:46 +msgid "" +"Plain text file with GeoJSON data - identified from the file extension " +".geojson or .json" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:48 +msgid "Text passed directly and encoded in GeoJSON" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:50 +msgid "" +"Starting with GDAL 2.3, the URL/filename/text might be prefixed with " +"GeoJSON: to avoid any ambiguity with other drivers. Alternatively, " +"starting with GDAL 3.10, specifying the ``-if GeoJSON`` option to command" +" line utilities accepting it, or ``GeoJSON`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed URL/filename/text." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:58 +#: ../../source/drivers/vector/libkml.rst:256 +msgid "Layer" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:60 +msgid "" +"A GeoJSON datasource is translated to single OGRLayer object with pre-" +"defined name *OGRGeoJSON*:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:67 +msgid "" +"It is also valid to assume that OGRDataSource::GetLayerCount() for " +"GeoJSON datasource always returns 1." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:70 +msgid "Starting with GDAL 2.2, the layer name is built with the following logic:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:73 +msgid "If a \"name\" member is found at the FeatureCollection level, it is used." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:75 +msgid "" +"Otherwise if the filename is regular (ie not a URL with query " +"parameters), then the filename without extension and path is used as the " +"layer name." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:78 +msgid "Otherwise OGRGeoJSON is used." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:80 +msgid "" +"Accessing Web Service as a datasource (i.e. FeatureServer), each request " +"will produce new layer. This behavior conforms to stateless nature of " +"HTTP transaction and is similar to how Web browsers operate: single " +"request == single page." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:85 +msgid "" +"If a top-level member of GeoJSON data is of any other type than " +"*FeatureCollection*, the driver will produce a layer with only one " +"feature. Otherwise, a layer will consists of a set of features." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:89 +msgid "" +"If the :oo:`NATIVE_DATA` open option is set to YES, members at the level " +"of the FeatureCollection will be stored as a serialized JSON object in " +"the NATIVE_DATA item of the NATIVE_DATA metadata domain of the layer " +"object (and \"application/vnd.geo+json\" in the NATIVE_MEDIA_TYPE of the " +"NATIVE_DATA metadata domain)." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:96 +#: ../../source/drivers/vector/libkml.rst:468 +#: ../../source/drivers/vector/ngw.rst:108 +msgid "Feature" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:98 +msgid "" +"The OGR GeoJSON driver maps each object of following types to new " +"*OGRFeature* object: Point, LineString, Polygon, GeometryCollection, " +"Feature." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:102 +msgid "" +"According to the *GeoJSON Specification*, only the *Feature* object must " +"have a member with name *properties*. Each and every member of " +"*properties* is translated to OGR object of type of OGRField and added to" +" corresponding OGRFeature object." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:107 +msgid "" +"The *GeoJSON Specification* does not require all *Feature* objects in a " +"collection to have the same schema of properties. If *Feature* objects in" +" a set defined by *FeatureCollection* object have different schema of " +"properties, then resulting schema of fields in OGRFeatureDefn is " +"generated as `union <http://en.wikipedia.org/wiki/Union_(set_theory)>`__ " +"of all *Feature* properties." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:114 +msgid "" +"Schema detection will recognized fields of type String, Integer, Real, " +"StringList, IntegerList and RealList, Integer(Boolean), Date, Time and " +"DateTime." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:117 +msgid "" +"It is possible to tell the driver to not to process attributes by setting" +" configuration option :config:`ATTRIBUTES_SKIP=YES`. Default behavior is " +"to preserve all attributes (as an union, see previous paragraph), what is" +" equal to setting :config:`ATTRIBUTES_SKIP=NO`." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:123 +msgid "" +"If the :oo:`NATIVE_DATA` open option is set to YES, the Feature JSON " +"object will be stored as a serialized JSON object in the NativeData " +"property of the OGRFeature object (and \"application/vnd.geo+json\" in " +"the NativeMediaType property). On write, if a OGRFeature to be written " +"has its NativeMediaType property set to \"application/vnd.geo+json\" and " +"its NativeData property set to a string that is a serialized JSON object," +" then extra members of this object (i.e. not the \"property\" dictionary," +" nor the first 3 dimensions of geometry coordinates) will be used to " +"enhance the created JSON object from the OGRFeature. See :ref:`rfc-60` " +"for more details." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:137 +msgid "" +"Similarly to the issue with mixed-properties features, the *GeoJSON " +"Specification* draft does not require all *Feature* objects in a " +"collection must have geometry of the same type. Fortunately, OGR objects " +"model does allow to have geometries of different types in single layer - " +"a heterogeneous layer. By default, the GeoJSON driver preserves type of " +"geometries." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:144 +msgid "" +"However, sometimes there is a need to generate a homogeneous layer from a" +" set of heterogeneous features. For this purpose, it is possible to tell " +"the driver to wrap all geometries with OGRGeometryCollection type as a " +"common denominator. This behavior may be controlled by setting the " +":config:`GEOMETRY_AS_COLLECTION` configuration option to YES." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:242 +msgid "" +"To explain :oo:`FLATTEN_NESTED_ATTRIBUTES`, consider the following " +"GeoJSON fragment:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:268 +msgid "\"ogrinfo test.json -al -oo FLATTEN_NESTED_ATTRIBUTES=yes\" reports:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:281 +msgid "" +"|about-layer-creation-options| This driver supports the following layer " +"creation options:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:417 +#: ../../source/drivers/vector/jsonfg.rst:188 +msgid "" +"The driver supports reading and writing to files managed by VSI Virtual " +"File System API, which includes \"regular\" files, as well as files in " +"the /vsizip/ (read-write), /vsigzip/ (read-write), /vsicurl/ (read-only) " +"domains." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:425 +msgid "Round-tripping of extra JSON members" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:427 +msgid "See :ref:`rfc-60` for more details." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:429 +msgid "" +"Starting with GDAL 2.1, extra JSON members at the FeatureCollection, " +"Feature or geometry levels that are not normally reflected in the OGR " +"abstraction, such as the ones called \"extra_XXXXX_member\" in the below " +"snippet, are by default preserved when executing ogr2ogr with GeoJSON " +"both at the source and destination. This also applies to extra values in " +"position tuples of geometries, beyond the 3rd dimension (100, 101 in the " +"below example), if the transformation preserves the geometry structure " +"(for example, reprojection is allowed, but not change in the number of " +"coordinates)." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:461 +msgid "" +"This behavior can be turned off by specifying the **-noNativeData** " +"switch of the ogr2ogr utility." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:465 +msgid "RFC 7946 write support" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:467 +msgid "" +"By default, the driver will write GeoJSON files following GeoJSON 2008 " +"specification. When specifying the :lco:`RFC7946=YES` creation option, " +"the RFC 7946 standard will be used instead." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:471 +msgid "" +"The differences between the 2 versions are mentioned in `Appendix B of " +"RFC 7946 <https://tools.ietf.org/html/rfc7946#appendix-B>`__ and recalled" +" here for what matters to the driver:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:475 +msgid "" +"Coordinates must be geographic over the WGS 84 ellipsoid, hence if the " +"spatial reference system specified at layer creation time is not " +"EPSG:4326, on-the-fly reprojection will be done by the driver." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:479 +msgid "" +"Polygons will be written such as to follow the right-hand rule for " +"orientation (counterclockwise external rings, clockwise internal rings)." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:482 +msgid "" +"The values of a \"bbox\" array are \"[west, south, east, north]\", not " +"\"[minx, miny, maxx, maxy]\"" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:484 +msgid "" +"Some extension member names (see previous section about round/tripping) " +"are forbidden in the FeatureCollection, Feature and Geometry objects." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:487 +msgid "" +"The default coordinate precision is 7 decimal digits after decimal " +"separator." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:495 +#: ../../source/drivers/vector/jsonfg.rst:200 +msgid "" +"The GeoJSON driver supports reading and writing the geometry coordinate " +"precision, using the :cpp:class:`OGRGeomCoordinatePrecision` settings of " +"the :cpp:class:`OGRGeomFieldDefn` Those settings are used to round the " +"coordinates of the geometry of the features to an appropriate decimal " +"precision." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:502 +#: ../../source/drivers/vector/geojsonseq.rst:135 +msgid "" +"The :lco:`COORDINATE_PRECISION` layer creation option has precedence over" +" the values set on the :cpp:class:`OGRGeomFieldDefn`." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:505 +msgid "" +"Implementation details: the coordinate precision is stored as " +"``xy_coordinate_resolution`` and ``z_coordinate_resolution`` members at " +"the FeatureCollection level. Their numeric value is expressed in the " +"units of the SRS." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:524 +msgid "How to dump content of .geojson file:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:530 +msgid "How to query features from remote service with filtering by attribute:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:536 +msgid "" +"How to translate number of features queried from FeatureServer to ESRI " +"Shapefile:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:543 +msgid "How to translate a ESRI Shapefile into a RFC 7946 GeoJSON file:" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:552 +msgid "`GeoJSON <http://geojson.org/>`__ - encoding geographic content in JSON" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:554 +msgid "`RFC 7946 <https://tools.ietf.org/html/rfc7946>`__ standard." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:555 +msgid "" +"`GeoJSON 2008 <http://geojson.org/geojson-spec.html>`__ specification " +"(obsoleted by RFC 7946)." +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:557 +msgid "`JSON <http://json.org/>`__ - JavaScript Object Notation" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:558 +msgid ":ref:`GeoJSON sequence driver <vector.geojsonseq>`" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:559 +msgid ":ref:`OGC Features and Geometries JSON (JSON-FG) driver <vector.jsonfg>`" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:560 +msgid ":ref:`ESRI JSON / FeatureService driver <vector.esrijson>`" +msgstr "" + +#: ../../source/drivers/vector/geojson.rst:561 +msgid ":ref:`TopoJSON driver <vector.topojson>`" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:8 +msgid "GeoJSONSeq" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:12 +msgid "" +"This driver implements read/creation support for features encoded " +"individually as `GeoJSON <http://geojson.org/>`__ Feature objects, " +"separated by newline (LF) (`Newline Delimited JSON " +"<https://github.com/ndjson/ndjson-spec>`__) or record-separator (RS) " +"characters (`RFC 8142 <https://tools.ietf.org/html/rfc8142>`__ standard: " +"GeoJSON Text Sequences)" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:19 +msgid "" +"Such files are equivalent to a GeoJSON FeatureCollection, but are more " +"friendly for incremental parsing." +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:22 +msgid "" +"The driver automatically reprojects geometries to WGS84 longitude, " +"latitude, if the layer is created with another SRS." +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:25 +msgid "Appending to an existing file is supported since GDAL 3.6" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:44 +msgid "" +"Plain text file with GeoJSON data - identified from the file extension " +".geojsonl or .geojsons" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:46 +msgid "Text passed directly as filename, and encoded as GeoJSON sequences" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:48 +msgid "" +"The URL/filename/text might be prefixed with GeoJSONSeq: to avoid any " +"ambiguity with other drivers. Alternatively, starting with GDAL 3.10, " +"specifying the ``-if GeoJSONSeq`` option to command line utilities " +"accepting it, or ``GeoJSONSeq`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed URL/filename/text." +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:61 +msgid ":copy-config:`OGR_GEOJSON_MAX_OBJ_SIZE`" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:128 +msgid "" +"On creation, the GeoJSONSeq driver supports using the geometry coordinate" +" precision, from th :cpp:class:`OGRGeomCoordinatePrecision` settings of " +"the :cpp:class:`OGRGeomFieldDefn`. Those settings are used to round the " +"coordinates of the geometry of the features to an appropriate decimal " +"precision." +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:138 +msgid "" +"The value of those geometry coordinate precision is *not* serialized in " +"the generated file, hence on reading, the driver will not advertise a " +"geometry coordinate precision." +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:146 +msgid "" +"`RFC 7946 <https://tools.ietf.org/html/rfc7946>`__ standard: the GeoJSON " +"Format." +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:148 +msgid "" +"`RFC 8142 <https://tools.ietf.org/html/rfc8142>`__ standard: GeoJSON Text" +" Sequences (RS separator)" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:150 +msgid "" +"`GeoJSONL <https://www.interline.io/blog/geojsonl-extracts/>`__: An " +"optimized format for large geographic datasets" +msgstr "" + +#: ../../source/drivers/vector/geojsonseq.rst:152 +msgid "" +"`JSON streaming on Wikipedia " +"<https://en.wikipedia.org/wiki/JSON_streaming>`__: An overview over " +"formats for concatenated JSON in a single file" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:4 +msgid "GeoPackage aspatial extension" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:6 +msgid "" +"This extension has been superseded by GeoPackage 1.2 ``attributes`` data " +"type." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:8 +msgid "GeoPackage 1.0 Extension" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:10 +msgid "" +"Extension follows template from Annex I of the OGC `GeoPackage 1.0 " +"Specification`_." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:13 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:11 +msgid "Extension Title" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:15 +msgid "Aspatial Support" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:20 +msgid "" +"Support for aspatial data (i.e. SQLite tables/views without a geometry " +"column), potentially with associated metadata." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:23 +msgid "" +"This was used in GDAL 2.0 and GDAL 2.1, before the introduction of the " +"'attributes' data_type of GeoPackage v1.2. Starting with GDAL 2.2, " +"'attributes' will be used by default, so this extension is now legacy." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:28 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:22 +msgid "Extension Author" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:30 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:24 +msgid "`GDAL - Geospatial Data Abstraction Library`_, author_name `gdal`." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:33 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:27 +msgid "Extension Name or Template" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:51 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:48 +msgid "Extension Type" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:53 +msgid "Extension of Existing Requirement in Clause 2." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:56 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:53 +msgid "Applicability" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:58 +msgid "" +"This extension applies to any aspatial user data table or view specified " +"in the ``gpkg_contents`` table with a lowercase `data_type` column value " +"of \"aspatial\"." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:62 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:61 +msgid "Scope" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:64 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:63 +msgid "Read-write" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:70 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:69 +msgid "GeoPackage" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:72 +msgid "Contents Table - Aspatial" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:74 +msgid "" +"The `gpkg_contents` table SHALL contain a row with a lowercase " +"`data_type` column value of \"aspatial\" for each aspatial user data " +"table or view." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:77 +msgid "User Data Tables" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:79 +msgid "" +"The second component of the SQL schema for aspatial tables in an Extended" +" GeoPackage described in clause 'Contents Table - Aspatial' above are " +"user tables or views that contain aspatial user data." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:83 +msgid "" +"An Extended GeoPackage with aspatial support is not required to contain " +"any user data tables. User data tables MAY be empty." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:86 +msgid "" +"An Extended GeoPackage with aspatial support MAY contain tables or views." +" Every such aspatial table or view MAY have a column with column type " +"INTEGER and PRIMARY KEY AUTOINCREMENT column constraints per EXAMPLE." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:94 +msgid "Column Name" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:97 +msgid "Null" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:98 +msgid "Default" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:99 +msgid "Key" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:100 +msgid "`id`" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:101 +msgid "INTEGER" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:102 +msgid "Autoincrement primary key" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:103 +msgid "no" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:105 +msgid "PK" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:106 +msgid "`text_attribute`" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:107 +msgid "TEXT" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:108 +msgid "Text attribute of row" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:109 +#: ../../source/drivers/vector/geopackage_aspatial.rst:115 +#: ../../source/drivers/vector/geopackage_aspatial.rst:121 +#: ../../source/drivers/vector/geopackage_aspatial.rst:127 +msgid "yes" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:112 +msgid "`real_attribute`" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:113 +msgid "REAL" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:114 +msgid "Real attribute of row" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:118 +msgid "`boolean_attribute`" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:119 +msgid "BOOLEAN" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:120 +msgid "Boolean attribute of row" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:124 +msgid "`raster_or_photo`" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:125 +msgid "BLOB" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:126 +msgid "Photograph" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:131 +msgid "" +"An integer primary key of an aspatial table or view allows features to be" +" linked to row level metadata records in the `gpkg_metadata` table by " +"`SQLite ROWID`_ values in the `gpkg_metadata_reference` table as " +"described in clause 2.4.3 Metadata Reference Table." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:136 +msgid "An aspatial table or view SHALL NOT have a geometry column." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:138 +msgid "" +"Columns in aspatial tables or views SHALL be defined using only the data " +"types specified in Table 1 in Clause 1.1.1.1.3." +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:142 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:86 +msgid "GeoPackage SQLite Configuration" +msgstr "" + +#: ../../source/drivers/vector/geopackage_aspatial.rst:147 +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:91 +msgid "GeoPackage SQLite Extension" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:6 +msgid "GeoRSS" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:10 +msgid "GeoRSS is a way of encoding location in RSS or Atom feeds." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:12 +msgid "" +"OGR has support for GeoRSS reading and writing. Read support is only " +"available if GDAL is built with *expat* library support" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:15 +msgid "The driver supports RSS documents in RSS 2.0 or Atom 1.0 format." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:17 +msgid "" +"It also supports the `3 ways of encoding location " +"<http://georss.org/model>`__ : GeoRSS simple, GeoRSS GML and W3C Geo (the" +" later being deprecated)." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:21 +msgid "" +"The driver can read and write documents without location information as " +"well." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:24 +msgid "" +"The default datum for GeoRSS document is the WGS84 datum (EPSG:4326). " +"Although that GeoRSS locations are encoded in latitude-longitude order in" +" the XML file, all coordinates reported or expected by the driver are in " +"longitude-latitude order. The longitude/latitude order used by OGR is " +"meant for compatibility with most of the rest of OGR drivers and " +"utilities. For locations encoded in GML, the driver will support the " +"srsName attribute for describing other SRS." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:32 +msgid "" +"Simple and GML encoding support the notion of a *box* as a geometry. This" +" will be decoded as a rectangle (Polygon geometry) in OGR Simple Feature " +"model." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:36 +msgid "" +"A single layer is returned while reading a RSS document. Features are " +"retrieved from the content of <item> (RSS document) or <entry> (Atom " +"document) elements." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:50 +#: ../../source/drivers/vector/gml.rst:399 +#: ../../source/drivers/vector/gpx.rst:124 +#: ../../source/drivers/vector/jml.rst:35 +#: ../../source/drivers/vector/kml.rst:70 +msgid "Encoding issues" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:52 +#: ../../source/drivers/vector/gml.rst:401 +#: ../../source/drivers/vector/gpx.rst:126 +#: ../../source/drivers/vector/jml.rst:37 +#: ../../source/drivers/vector/kml.rst:72 +msgid "Expat library supports reading the following built-in encodings :" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:54 +#: ../../source/drivers/vector/gml.rst:403 +#: ../../source/drivers/vector/gpx.rst:128 +#: ../../source/drivers/vector/jml.rst:39 +#: ../../source/drivers/vector/kml.rst:74 +msgid "US-ASCII" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:55 +#: ../../source/drivers/vector/gml.rst:404 +#: ../../source/drivers/vector/gpx.rst:129 +#: ../../source/drivers/vector/jml.rst:40 +#: ../../source/drivers/vector/kml.rst:75 +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "UTF-8" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:56 +#: ../../source/drivers/vector/gml.rst:405 +#: ../../source/drivers/vector/gpx.rst:130 +#: ../../source/drivers/vector/jml.rst:41 +#: ../../source/drivers/vector/kml.rst:76 +msgid "UTF-16" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:57 +#: ../../source/drivers/vector/gml.rst:406 +#: ../../source/drivers/vector/gpx.rst:131 +#: ../../source/drivers/vector/jml.rst:42 +#: ../../source/drivers/vector/kml.rst:77 +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-1" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:58 +#: ../../source/drivers/vector/gml.rst:407 +#: ../../source/drivers/vector/gpx.rst:132 +#: ../../source/drivers/vector/jml.rst:43 +#: ../../source/drivers/vector/kml.rst:78 +msgid "Windows-1252" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:60 +#: ../../source/drivers/vector/gml.rst:409 +#: ../../source/drivers/vector/gpx.rst:134 +#: ../../source/drivers/vector/kml.rst:80 +msgid "" +"The content returned by OGR will be encoded in UTF-8, after the " +"conversion from the encoding mentioned in the file header is." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:66 +msgid "" +"If your GeoRSS file is not encoded in one of the previous encodings, it " +"will not be parsed by the GeoRSS driver. You may convert it into one of " +"the supported encoding with the *iconv* utility for example and change " +"accordingly the *encoding* parameter value in the XML header." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:68 +msgid "" +"When writing a GeoRSS file, the driver expects UTF-8 content to be passed" +" in." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:74 +msgid "" +"While reading a GeoRSS document, the driver will first make a full scan " +"of the document to get the field definitions." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:77 +msgid "" +"The driver will return elements found in the base schema of RSS channel " +"or Atom feeds. It will also return extension elements, that are allowed " +"in namespaces." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:81 +msgid "Attributes of first level elements will be exposed as fields." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:83 +msgid "" +"Complex content (elements inside first level elements) will be returned " +"as an XML blob." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:86 +msgid "" +"When a same element is repeated, a number will be appended at the end of " +"the attribute name for the repetitions. This is useful for the <category>" +" element in RSS and Atom documents for example." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:90 +msgid "The following content :" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:109 +#: ../../source/drivers/vector/gpx.rst:171 +msgid "will be interpreted in the OGR SF model as :" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:128 +msgid "" +"On export, all layers are written to a single file. Update of existing " +"files is not supported." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:131 +#: ../../source/drivers/vector/gpx.rst:197 +msgid "" +"If the output file already exits, the writing will not occur. You have to" +" delete the existing file first." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:134 +msgid "" +"A layer that is created cannot be immediately read without closing and " +"reopening the file. That is to say that a dataset is read-only or write-" +"only in the same session." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:138 +#: ../../source/drivers/vector/gpx.rst:200 +msgid "Supported geometries :" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:140 +msgid "Features of type wkbPoint/wkbPoint25D." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:141 +msgid "Features of type wkbLineString/wkbLineString25D." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:142 +msgid "Features of type wkbPolygon/wkbPolygon25D." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:144 +msgid "Other type of geometries are not supported and will be silently ignored." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:231 +msgid "" +"When translating from a source dataset, it may be necessary to rename the" +" field names from the source dataset to the expected RSS or ATOM " +"attribute names, such as <title>, <description>, etc... This can be done " +"with a :ref:`OGR VRT <vector.vrt>` dataset, or by using the \"-sql\" " +"option of the ogr2ogr utility (see :ref:`rfc-21`)" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:240 +#: ../../source/drivers/vector/gml.rst:794 +#: ../../source/drivers/vector/gpx.rst:387 +#: ../../source/drivers/vector/kml.rst:130 +#: ../../source/drivers/vector/libkml.rst:951 +msgid "" +"The driver supports reading and writing to files managed by VSI Virtual " +"File System API, which include \"regular\" files, as well as files in the" +" /vsizip/ (read-write) , /vsigzip/ (read-write) , /vsicurl/ (read-only) " +"domains." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:250 +msgid "The ogrinfo utility can be used to dump the content of a GeoRSS datafile :" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:259 +msgid "" +"The ogr2ogr utility can be used to do GeoRSS to GeoRSS translation. For " +"example, to translate a Atom document into a RSS document" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:268 +msgid "" +"Note : in this example we map equivalent fields, from the source name to " +"the expected name of the destination format." +msgstr "" + +#: ../../source/drivers/vector/georss.rst:272 +msgid "" +"The following Python script shows how to read the content of a online " +"GeoRSS feed" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:311 +msgid "`Home page for GeoRSS format <http://georss.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:312 +msgid "`Wikipedia page for GeoRSS format <http://en.wikipedia.org/wiki/GeoRSS>`__" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:314 +msgid "`Wikipedia page for RSS format <http://en.wikipedia.org/wiki/RSS>`__" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:315 +msgid "`RSS 2.0 specification <http://www.rssboard.org/rss-specification>`__" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:316 +msgid "" +"`Wikipedia page for Atom format " +"<http://en.wikipedia.org/wiki/Atom_(standard)>`__" +msgstr "" + +#: ../../source/drivers/vector/georss.rst:318 +msgid "`Atom 1.0 specification <http://www.ietf.org/rfc/rfc4287.txt>`__" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:4 +msgid "GML - Geography Markup Language" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:6 +msgid "GML" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:10 +msgid "" +"OGR has limited support for GML reading and writing. Update of existing " +"files is not supported." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:13 +msgid "Supported GML flavors :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:16 +msgid "Read" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:16 +msgid "Write" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:18 +msgid "GML2 and GML3 that can" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:18 +msgid "GML 2.1.2 or GML 3 SF-0" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:19 +msgid "be translated into simple feature model" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:19 +msgid "(GML 3.1.1 Compliance level SF-0)" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:22 +msgid "" +"Starting with GDAL 2.2, another driver, :ref:`GMLAS <vector.gmlas>`, for " +"GML driven by application schemas, is also available. Both GML and GMLAS " +"drivers have their use cases." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:120 +msgid "Parsers" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:122 +msgid "" +"The reading part of the driver only works if OGR is built with Xerces " +"linked in. When Xerces is unavailable, read support also works if OGR is " +"built with Expat linked in. XML validation is disabled by default. GML " +"writing is always supported, even without Xerces or Expat." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:128 +msgid "" +"Note: if both Xerces and Expat are available at build time, the GML " +"driver will preferentially select at runtime the Expat parser for cases " +"where it is possible (GML file in a compatible encoding), and default " +"back to Xerces parser in other cases. However, the choice of the parser " +"can be overridden by specifying the :config:`GML_PARSER` configuration " +"option to **EXPAT** or **XERCES**." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:136 +#: ../../source/drivers/vector/oapif.rst:62 +msgid "CRS support" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:138 +msgid "" +"The GML driver has coordinate system support. This is only reported when " +"all the geometries of a layer have a srsName attribute, whose value is " +"the same for all geometries. For srsName such as " +"\"urn:ogc:def:crs:EPSG:\" (or \"http://www.opengis.net/def/crs/EPSG/0/\" " +"starting with GDAL 2.1.2), for geographic coordinate systems (as returned" +" by WFS 1.1.0 for example), the axis order should be (latitude, " +"longitude) as required by the standards, but this is unusual and can " +"cause issues with applications unaware of axis order. So by default, the " +"driver will swap the coordinates so that they are in the (longitude, " +"latitude) order and report a SRS without axis order specified. It is " +"possible to get the original (latitude, longitude) order and SRS with " +"axis order by setting the configuration option " +":config:`GML_INVERT_AXIS_ORDER_IF_LAT_LONG` to **NO**." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:152 +msgid "" +"There also situations where the srsName is of the form \"EPSG:XXXX\" " +"(whereas \"urn:ogc:def:crs:EPSG::XXXX\" would have been more explicit on " +"the intent) and the coordinates in the file are in (latitude, longitude) " +"order. By default, OGR will not consider the EPSG axis order and will " +"report the coordinates in (latitude,longitude) order. However, if you set" +" the configuration option :config:`GML_CONSIDER_EPSG_AS_URN` to **YES**, " +"the rules explained in the previous paragraph will be applied." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:160 +msgid "" +"The above also applied for projected coordinate systems whose EPSG " +"preferred axis order is (northing, easting)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:163 +msgid "" +"Starting with GDAL 2.1.2, the :oo:`SWAP_COORDINATES` open option (or " +":config:`GML_SWAP_COORDINATES` configuration option) can be set to " +"AUTO/YES/NO. It controls whether the order of the x/y or long/lat " +"coordinates should be swapped. In AUTO mode, the driver will determine if" +" swapping must be done from the srsName and value of other options like " +":oo:`CONSIDER_EPSG_AS_URN` and :oo:`INVERT_AXIS_ORDER_IF_LAT_LONG`. When " +":oo:`SWAP_COORDINATES` is set to YES, coordinates will be always swapped " +"regarding the order they appear in the GML, and when it set to NO, they " +"will be kept in the same order. The default is AUTO." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:177 +msgid "" +"In contrast to most GML readers, the OGR GML reader does not require the " +"presence of an XML Schema definition of the feature classes (file with " +".xsd extension) to be able to read the GML file. If the .xsd file is " +"absent or OGR is not able to parse it, the driver attempts to " +"automatically discover the feature classes and their associated " +"properties by scanning the file and looking for \"known\" gml objects in " +"the gml namespace to determine the organization. While this approach is " +"error prone, it has the advantage of working for GML files even if the " +"associated schema (.xsd) file has been lost." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:187 +msgid "" +"It is possible to specify an explicit filename for the XSD schema to use," +" by using \"a_filename.gml,xsd=another_filename.xsd\" as a connection " +"string. The XSD can also be specified as the value of the XSD open " +"option." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:193 +msgid "" +"The first time a GML file is opened, if the associated .xsd is absent or " +"could not been parsed correctly, it is completely scanned in order to " +"determine the set of featuretypes, the attributes associated with each " +"and other dataset level information. This information is stored in a .gfs" +" file with the same basename as the target gml file. Subsequent accesses " +"to the same GML file will use the .gfs file to predefine dataset level " +"information accelerating access. To a limited extent the .gfs file can be" +" manually edited to alter how the GML file will be parsed. Be warned that" +" the .gfs file will be ignored if the associated .gml file has a newer " +"timestamp." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:204 +msgid "" +"When prescanning the GML file to determine the list of feature types, and" +" fields, the contents of fields are scanned to try and determine the type" +" of the field. In some applications it is easier if all fields are just " +"treated as string fields. This can be accomplished by setting the " +"configuration option :config:`GML_FIELDTYPES` to the value " +"**ALWAYS_STRING**." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:210 +msgid "" +"The :config:`GML_ATTRIBUTES_TO_OGR_FIELDS` configuration option can be " +"set to **YES** so that attributes of GML elements are also taken into " +"account to create OGR fields." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:214 +msgid "" +"You can use :config:`GML_GFS_TEMPLATE` configuration option (or " +":oo:`GFS_TEMPLATE` open option) set to a **path_to_template.gfs** in " +"order to unconditionally use a predefined GFS file. This option is really" +" useful when you are planning to import many distinct GML files in " +"subsequent steps [**-append**] and you absolutely want to preserve a " +"fully consistent data layout for the whole GML set. Please, pay attention" +" not to use the **-lco LAUNDER=yes** setting when using " +":config:`GML_GFS_TEMPLATE`; this should break the correct recognition of " +"attribute names between subsequent GML import runs." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:225 +msgid "Particular GML application schemas" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:227 +msgid "" +"Feature attributes in nested GML elements (non-flat attribute hierarchy) " +"that can be found in some GML profiles, such as UK Ordnance Survey " +"MasterMap, are detected. IntegerList, RealList and StringList field types" +" when a GML element has several occurrences are also supported." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:232 +msgid "" +"A specialized GML driver - the :ref:`NAS <vector.nas>` driver - is " +"available to read German AAA GML Exchange Format (NAS/ALKIS)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:236 +msgid "The GML driver has partial support for reading AIXM or CityGML files." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:239 +msgid "The GML driver supports reading :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:241 +msgid "" +"`Finnish National Land Survey GML files (a.k.a MTK GML) for topographic " +"data. " +"<http://xml.nls.fi/XML/Schema/Maastotietojarjestelma/MTK/201202/Maastotiedot.xsd>`__" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:244 +msgid "" +"`Finnish National Land Survey GML files for cadastral data " +"<http://xml.nls.fi/XML/Schema/sovellus/ktjkii/modules/kiinteistotietojen_kyselypalvelu_WFS/Asiakasdokumentaatio/ktjkiiwfs/2010/02/>`__." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:246 +msgid "" +"`Cadastral data in Inspire GML schemas " +"<http://inspire.ec.europa.eu/schemas/cp/3.0/CadastralParcels.xsd>`__." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:248 +msgid "" +"`Czech RUIAN Exchange Format (VFR) " +"<http://www.cuzk.cz/Uvod/Produkty-a-sluzby/RUIAN/2-Poskytovani-udaju-" +"RUIAN-ISUI-VDP/Vymenny-format-RUIAN/Vymenny-format-" +"RUIAN-%28VFR%29.aspx>`__." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:251 +msgid "The GML driver supports reading responses to CSW GetRecords queries." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:253 +msgid "Since OGR 2.2, the GML driver supports reading Japanese FGD GML v4 files." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:257 +msgid "Geometry reading" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:259 +msgid "" +"When reading a feature, the driver will by default only take into account" +" the last recognized GML geometry found (in case they are multiples) in " +"the XML subtree describing the feature." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:263 +msgid "" +"But, if the .xsd schema is understood by the XSD parser and declares " +"several geometry fields, or the .gfs file declares several geometry " +"fields, multiple geometry fields will be reported by the GML driver " +"according to :ref:`rfc-41`." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:268 +msgid "" +"In case of multiple geometry occurrences, if a geometry is in a " +"<geometry> element, this will be the one selected. This will make default" +" behavior consistent with Inspire objects." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:272 +msgid "" +"The user can change the .gfs file to select the appropriate geometry by " +"specifying its path with the <GeometryElementPath> element. See the " +"description of the .gfs syntax below." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:277 +msgid "" +"GML geometries including TopoCurve, TopoSurface, MultiCurve are also " +"supported. The TopoCurve type GML geometry can be interpreted as either " +"of two types of geometries. The Edge elements in it contain curves and " +"their corresponding nodes. By default only the curves, the main " +"geometries, are reported as OGRMultiLineString. To retrieve the nodes, as" +" OGRMultiPoint, the configuration option :config:`GML_GET_SECONDARY_GEOM`" +" should be set to the value **YES**. When this is set only the secondary " +"geometries are reported." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:286 +msgid "" +"Arc, ArcString, ArcByBulge, ArcByCenterPoint, Circle and " +"CircleByCenterPoints will be returned as circular string OGR geometries. " +"If they are included in other GML elements such as CurveComposite, " +"MultiCurve, Surface, corresponding non-linear OGR geometries will be " +"returned as well. When reading GML3 application schemas, declarations of " +"geometry fields such as CurvePropertyType, SurfacePropertyType, " +"MultiCurvePropertyType or MultiSurfacePropertyType will be also " +"interpreted as being potential non-linear geometries, and corresponding " +"OGR geometry type will be used for the layer geometry type." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:298 +msgid "gml:xlink resolving" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:300 +msgid "" +"gml:xlink resolving is supported. When the resolver finds an element " +"containing the tag xlink:href, it tries to find the corresponding element" +" with the gml:id in the same gml file, other gml file in the file system " +"or on the web using cURL. Set the configuration option " +":config:`GML_SKIP_RESOLVE_ELEMS` to **NONE** to enable resolution." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:306 +msgid "" +"By default the resolved file will be saved in the same directory as the " +"original file with the extension \".resolved.gml\", if it doesn't exist " +"already. This behavior can be changed using the configuration option " +":config:`GML_SAVE_RESOLVED_TO`. Set it to **SAME** to overwrite the " +"original file. Set it to a **filename ending with .gml** to save it to " +"that location. Any other values are ignored. If the resolver cannot write" +" to the file for any reason, it will try to save it to a temporary file " +"generated using CPLGenerateTempFilename(\"ResolvedGML\"); if it cannot, " +"resolution fails." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:316 +msgid "" +"Note that the resolution algorithm is not optimized for large files. For " +"files with more than a couple of thousand xlink:href tags, the process " +"can go beyond a few minutes. A rough progress is displayed through " +"CPLDebug() for every 256 links. It can be seen by setting the environment" +" variable :config:`CPL_DEBUG`. The resolution time can be reduced if you " +"know any elements that will not be needed. Mention a comma separated list" +" of names of such elements with the configuration option " +":config:`GML_SKIP_RESOLVE_ELEMS`. Set it to **ALL** to skip resolving " +"altogether (default action). Set it to **NONE** to resolve all the " +"xlinks." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:327 +msgid "" +"An alternative resolution method is available. This alternative method " +"will be activated using the configuration option " +":config:`GML_SKIP_RESOLVE_ELEMS=HUGE`. In this case any gml:xlink will be" +" resolved using a temporary SQLite DB so to identify any corresponding " +"gml:id relation. At the end of this SQL-based process, a resolved file " +"will be generated exactly as in the **NONE** case but without their " +"limits. The main advantages in using an external (temporary) DBMS so to " +"resolve gml:xlink and gml:id relations are the following:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:336 +msgid "" +"no memory size constraints. The **NONE** method stores the whole GML " +"node-tree in-memory; and this practically means that no GML file bigger " +"than 1 GB can be processed at all using a 32-bit platform, due to memory " +"allocation limits. Using a file-system based DBMS avoids at all this " +"issue." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:341 +msgid "" +"by far better efficiency, most notably when huge GML files containing " +"many thousands (or even millions) of xlink:href / gml:id relational " +"pairs." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:344 +msgid "" +"using the :config:`GML_SKIP_RESOLVE_ELEMS=HUGE` method realistically " +"allows to successfully resolve some really huge GML file (3GB+) " +"containing many millions xlink:href / gml:id in a reasonable time (about " +"an hour or so on)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:348 +msgid "" +"The :config:`GML_SKIP_RESOLVE_ELEMS=HUGE` method supports the following " +"further configuration option:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:355 +msgid "TopoSurface interpretation rules [polygons and internal holes]" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:357 +msgid "" +"The GML driver is able to recognize two different interpretation rules " +"for TopoSurface when a polygon contains any internal hole:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:361 +msgid "the previously supported interpretation rule assumed that:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:363 +#: ../../source/drivers/vector/gml.rst:374 +msgid "each TopoSurface may be represented as a collection of many Faces" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:364 +msgid "" +"*positive* Faces [i.e. declaring **orientation=\"+\"**] are assumed to " +"represent the Exterior Ring of some Polygon." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:366 +msgid "" +"*negative* Faces [i.e. declaring **orientation=\"-\"**] are assumed to " +"represent an Interior Ring (aka *hole*) belonging to the latest declared " +"Exterior Ring." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:369 +msgid "" +"ordering any Edge used to represent each Ring is important: each Edge is " +"expected to be exactly adjacent to the next one." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:372 +msgid "the new interpretation rule now assumes that:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:375 +msgid "" +"the declared **orientation** for any Face has nothing to deal with " +"Exterior/Interior Rings" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:377 +msgid "" +"each Face is now intended to represent a complete Polygon, eventually " +"including any possible Interior Ring (*holes*)" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:379 +msgid "" +"the relative ordering of any Edge composing the same Face is completely " +"not relevant" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:382 +msgid "" +"The newest interpretation seems to fully match GML 3 standard " +"recommendations; so this latest is now assumed to be the default " +"interpretation supported by OGR." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:386 +msgid "" +"**NOTE** : Using the newest interpretation requires GDAL/OGR to be built " +"against the GEOS library." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:389 +msgid "" +"Using the :config:`GML_FACE_HOLE_NEGATIVE` configuration option you can " +"select the actual interpretation to be applied when parsing GML 3 " +"topologies:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:393 +msgid "" +"setting :config:`GML_FACE_HOLE_NEGATIVE=NO` (*default* option) will " +"activate the newest interpretation rule" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:395 +msgid "" +"but explicitly setting :config:`GML_FACE_HOLE_NEGATIVE=YES` still enables" +" to activate the old interpretation rule" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:412 +msgid "" +"If the GML file is not encoded in one of the previous encodings and the " +"only parser available is Expat, it will not be parsed by the GML driver. " +"You may convert it into one of the supported encodings with the *iconv* " +"utility for example and change accordingly the *encoding* parameter value" +" in the XML header." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:418 +msgid "When writing a GML file, the driver expects UTF-8 content to be passed in." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:421 +msgid "" +"Note: The .xsd schema files are parsed with an integrated XML parser " +"which does not currently understand XML encodings specified in the XML " +"header. It expects encoding to be always UTF-8. If attribute names in the" +" schema file contains non-ascii characters, it is better to use *iconv* " +"utility and convert the .xsd file into UTF-8 encoding first." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:428 +msgid "Feature id (fid / gml:id)" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:430 +msgid "" +"The driver exposes the content of the gml:id attribute as a string field " +"called *gml_id*, when reading GML WFS documents. When creating a GML3 " +"document, if a field is called *gml_id*, its content will also be used to" +" write the content of the gml:id attribute of the created feature." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:436 +msgid "" +"The driver autodetects the presence of a fid (GML2) (resp. gml:id (GML3))" +" attribute at the beginning of the file, and, if found, exposes it by " +"default as a *fid* (resp. *gml_id*) field. The autodetection can be " +"overridden by specifying the :config:`GML_EXPOSE_FID` or " +":config:`GML_EXPOSE_GML_ID` configuration option to **YES** or **NO**." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:444 +msgid "" +"When creating a GML2 document, if a field is called *fid*, its content " +"will also be used to write the content of the fid attribute of the " +"created feature." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:451 +#: ../../source/drivers/vector/gmlas.rst:172 +msgid "Performance issues with large multi-layer GML files." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:453 +msgid "" +"There is only one GML parser per GML datasource shared among the various " +"layers. By default, the GML driver will restart reading from the " +"beginning of the file, each time a layer is accessed for the first time, " +"which can lead to poor performance with large GML files." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:458 +msgid "" +"The :config:`GML_READ_MODE` configuration option can be set to " +"**SEQUENTIAL_LAYERS** if all features belonging to the same layer are " +"written sequentially in the file. The reader will then avoid unnecessary " +"resets when layers are read completely one after the other. To get the " +"best performance, the layers must be read in the order they appear in the" +" file." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:465 +msgid "" +"If no .xsd and .gfs files are found, the parser will detect the layout of" +" layers when building the .gfs file. If the layers are found to be " +"sequential, a *<SequentialLayers>true</SequentialLayers>* element will be" +" written in the .gfs file, so that the :config:`GML_READ_MODE` will be " +"automatically initialized to SEQUENTIAL_LAYERS if not explicitly set by " +"the user." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:472 +msgid "" +"The :config:`GML_READ_MODE` configuration option can be set to " +"INTERLEAVED_LAYERS to be able to read a GML file whose features from " +"different layers are interleaved. In the case, the semantics of the " +"GetNextFeature() will be slightly altered, in a way where a NULL return " +"does not necessarily mean that all features from the current layer have " +"been read, but it could also mean that there is still a feature to read, " +"but that belongs to another layer. In that case, the file should be read " +"with code similar to the following one :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:574 +msgid "Whether to consider srsName like EPSG:XXXX as respecting EPSG axis order." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:632 +msgid "" +"When changing the value of most of the above options, it is recommended " +"to delete the ``.gfs`` file if it pre-exists, otherwise mis-behavior " +"might be observed." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:640 +msgid "" +"On export all layers are written to a single GML file all in a single " +"feature collection. Each layer's name is used as the element name for " +"objects from that layer. Geometries are always written as the " +"ogr:geometryProperty element on the feature." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:691 +msgid "" +"*GML2* in order to write GML files that follow GML 2.1.2 (Default before " +"GDAL 3.4)" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:692 +msgid "*GML3* in order to write GML files that follow GML 3.1.1 SF-0 profile." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:694 +msgid "" +"*GML3Deegree* in order to produce a GML 3.1.1 .XSD schema, with a few " +"variations with respect to what is recommended by GML3 SF-0 profile, but " +"that will be better accepted by some software (such as Deegree 3)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:698 +msgid "" +"*GML3.2*\\ in order to write GML files that follow GML 3.2.1 SF-0 " +"profile. (Default since GDAL 3.4)" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:701 +msgid "" +"Non-linear geometries can be written. This is only compatible with " +"selecting on of that above GML3 format variant. Otherwise, such " +"geometries will be approximating into their closest matching linear " +"geometry. Note: fields of type StringList, RealList or IntegerList can be" +" written. This will cause to advertise the SF-1 profile in the .XSD " +"schema (such types are not supported by SF-0)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:713 +msgid "" +"Whether to use the gml:FeatureCollection, instead of creating a dedicated" +" container element in the target namespace. Only valid for " +"FORMAT=GML3/GML3.2. Note that gml:FeatureCollection has been deprecated " +"in GML 3.2, and is not allowed by the OGC 06-049r1 \"Geography Markup " +"Language (GML) simple features profile\" (for GML 3.1.1) and OGC 10-100r3" +" \"Geography Markup Language (GML) simple features profile (with " +"Corrigendum)\" (for GML 3.2) specifications." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:799 +msgid "" +"Writing to /dev/stdout or /vsistdout/ is also supported. Note that in " +"that case, only the content of the GML file will be written to the " +"standard output (and not the .xsd). The <boundedBy> element will not be " +"written. This is also the case if writing in /vsigzip/" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:805 +msgid "Syntax of .gfs files" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:807 +msgid "" +"A XML Schema for .gfs files can be found at " +"https://raw.githubusercontent.com/OSGeo/gdal/master/ogr/ogrsf_frmts/gml/data/gfs.xsd" +" ." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:810 +#: ../../source/drivers/vector/gml.rst:918 +#: ../../source/drivers/vector/gml.rst:988 +msgid "Let's consider the following test.gml file :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:834 +#: ../../source/drivers/vector/gml.rst:1001 +#: ../../source/drivers/vector/gml.rst:1069 +msgid "and the following associated .gfs file." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:858 +msgid "" +"Note the presence of the '|' character in the <ElementPath> and " +"<GeometryElementPath> elements to specify the wished field/geometry " +"element that is a nested XML element. Nested field elements are " +"supported, as well as specifying <GeometryElementPath> If " +"GeometryElementPath is not specified, the GML driver will use the last " +"recognized geometry element." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:865 +msgid "" +"The <GeometryType> element can be specified to force the geometry type. " +"Accepted values are : 0 (any geometry type), 1 (point), 2 (linestring), 3" +" (polygon), 4 (multipoint), 5 (multilinestring), 6 (multipolygon), 7 " +"(geometrycollection)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:870 +msgid "" +"The <GeometryElementPath> and <GeometryType> can be specified as many " +"times as there are geometry fields in the GML file. Another possibility " +"is to define a <GeomPropertyDefn>element as many times as necessary:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:894 +#: ../../source/drivers/vector/gml.rst:1023 +msgid "The output of *ogrinfo test.gml -ro -al* is:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:913 +msgid "Advanced .gfs syntax" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:916 +msgid "Specifying ElementPath to find objects embedded into top level objects" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:960 +msgid "" +"By default, only the TopLevelObject object would be reported and it would" +" only use the second geometry. This is not the desired behavior in that " +"instance. You can edit the generated .gfs and modify it like the " +"following in order to specify a full path to the element (top level XML " +"element being omitted) :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:982 +msgid "Getting XML attributes as OGR fields" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:984 +msgid "" +"The element@attribute syntax can be used in the <ElementPath> to specify " +"that the value of attribute 'attribute' of element 'element' must be " +"fetched." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1041 +msgid "Using conditions on XML attributes" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1043 +msgid "" +"A <Condition> element can be specified as a child element of a " +"<PropertyDefn>. The content of the Condition follows a minimalistic XPath" +" syntax. It must be of the form @attrname[=|!=]'attrvalue' [and|or " +"other_cond]*. Note that 'and' and 'or' operators cannot be mixed (their " +"precedence is not taken into account)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1049 +msgid "" +"Several <PropertyDefn> can be defined with the same <ElementPath>, but " +"with <Condition> that must be mutually exclusive." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1052 +msgid "Let's consider the following testcondition.gml file :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1105 +msgid "The output of *ogrinfo testcondition.gml -ro -al* is:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1127 +msgid "Registry for GML application schemas" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1129 +msgid "" +"The \"data\" directory of the GDAL installation contains a " +"\"gml_registry.xml\" file that links feature types of GML application " +"schemas to .xsd or .gfs files that contain their definition. This is used" +" in case no valid .gfs or .xsd file is found next to the GML file." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1134 +msgid "" +"An alternate location for the registry file can be defined by setting its" +" full pathname to the GML_REGISTRY configuration option." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1137 +msgid "An example of such a file is :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1179 +msgid "" +"XML schema definition (.xsd) files are pointed by the schemaLocation " +"attribute, whereas OGR .gfs files are pointed by the gfsSchemaLocation " +"attribute. In both cases, the filename can be a URL (http://, https://), " +"an absolute filename, or a relative filename (relative to the location of" +" gml_registry.xml)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1185 +msgid "" +"The schema is used if and only if the namespace prefix and URI are found " +"in the first bytes of the GML file (e.g. " +"*xmlns:ktjkiiwfs=\"http://xml.nls.fi/ktjkiiwfs/2010/02\"*), and that the " +"feature type is also detected in the first bytes of the GML file (e.g. " +"*ktjkiiwfs:KiinteistorajanSijaintitiedot*). If the element value is " +"defined than the schema is used only if the feature type together with " +"the value is found in the first bytes of the GML file (e.g. " +"*vf:TypSouboru>OB_UKSH*)." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1195 +msgid "Building junction tables" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1197 +msgid "" +"The :source_file:`swig/python/gdal-" +"utils/osgeo_utils/samples/ogr_build_junction_table.py` script can be used" +" to build a `junction table " +"<http://en.wikipedia.org/wiki/Junction_table>`__ from OGR layers that " +"contain \"XXXX_href\" fields. Let's considering the following output of a" +" GML file with links to other features :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1216 +msgid "After running" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1222 +msgid "to import it into PostGIS and" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1228 +msgid "" +", a *myfeature_otherfeature* table will be created and will contain the " +"following content :" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1232 +msgid "myfeature_gml_id" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1232 +msgid "otherfeature_gml_id" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1234 +#: ../../source/drivers/vector/gml.rst:1235 +msgid "myFeature.1" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1234 +#: ../../source/drivers/vector/gml.rst:1237 +msgid "otherFeature.10" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1235 +msgid "otherFeature.20" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1236 +#: ../../source/drivers/vector/gml.rst:1237 +msgid "myFeature.2" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1236 +msgid "otherFeature.30" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1241 +msgid "Reading datasets resulting from a WFS 2.0 join queries" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1243 +msgid "The GML driver can read datasets resulting from a WFS 2.0 join queries." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1245 +msgid "Such datasets typically look like:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1293 +msgid "" +"OGR will group together the attributes from the layers participating to " +"the join and will prefix them with the layer name. So the above example " +"will be read as the following:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1323 +msgid "" +"The GML driver supports reading and writing the geometry coordinate " +"precision, using the :cpp:class:`OGRGeomCoordinatePrecision` settings of " +"the :cpp:class:`OGRGeomFieldDefn`. Those settings are used to round the " +"coordinates of the geometry of the features to an appropriate decimal " +"precision." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1328 +msgid "" +"Implementation details: the coordinate precision is stored in the XML " +"schema as " +"``xs:annotation/xs:appinfo[source=\"http://ogr.maptools.org/\"]/ogr:xy_coordinate_resolution``" +" and " +"``xs:annotation/xs:appinfo[source=\"http://ogr.maptools.org/\"]/ogr:z_coordinate_resolution``" +" optional elements in the declaration of the geometry column. Their " +"numeric value is expressed in the units of the SRS." +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1350 +msgid "" +"The ogr2ogr utility can be used to dump the results of a Oracle query to " +"GML:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1357 +msgid "" +"The ogr2ogr utility can be used to dump the results of a PostGIS query to" +" GML:" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1367 +msgid "`GML Specifications <http://www.opengeospatial.org/standards/gml>`__" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1368 +msgid "" +"`GML 3.1.1 simple features profile - OGC(R) 06-049r1 " +"<http://portal.opengeospatial.org/files/?artifact_id=15201>`__" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1370 +msgid "" +"`Geography Markup Language (GML) simple features profile (with " +"Corrigendum) (GML 3.2.1) - OGC(R) 10-100r3 " +"<https://portal.opengeospatial.org/files/?artifact_id=42729>`__" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1373 +msgid "`Xerces <http://xml.apache.org/xerces2-j/index.html>`__" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1374 +msgid "" +":ref:`GMLAS - Geography Markup Language (GML) driven by application " +"schemas <vector.gmlas>`" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1376 +msgid "" +":ref:`NAS/ALKIS : specialized GML driver for cadastral data in Germany " +"<vector.nas>`" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1382 +msgid "" +"Implementation for :config:`GML_SKIP_RESOLVE_ELEMS=HUGE` was contributed " +"by A.Furieri, with funding from Regione Toscana" +msgstr "" + +#: ../../source/drivers/vector/gml.rst:1384 +msgid "" +"Support for cadastral data in Finnish National Land Survey GML and " +"Inspire GML was funded by The Information Centre of the Ministry of " +"Agriculture and Forestry (Tike)" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:4 +msgid "GMLAS - Geography Markup Language (GML) driven by application schemas" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:8 +msgid "GMLAS" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:12 +msgid "" +"This driver can read and write XML files of arbitrary structure, included" +" those containing so called Complex Features, provided that they are " +"accompanied by one or several XML schemas that describe the structure of " +"their content. While this driver is generic to any XML schema, the main " +"target is to be able to read and write documents referencing directly or " +"indirectly to the GML namespace." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:19 +msgid "The driver requires Xerces-C >= 3.1." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:21 +msgid "" +"The driver can deal with files of arbitrary size with a very modest RAM " +"usage, due to its working in streaming mode." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:36 +msgid "" +"The connection string is GMLAS:/path/to/the.gml. Note the ``GMLAS:`` " +"prefix. If this prefix it is omitted, then the GML driver is likely to be" +" used." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:39 +msgid "" +"Alternatively, starting with GDAL 3.10, specifying the ``-if GMLAS`` " +"option to command line utilities accepting it, or ``GMLAS`` as the only " +"value of the ``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also " +"forces the driver to recognize the passed filename." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:43 +msgid "" +"It is also possible to only used ``GMLAS:`` as the connection string, but" +" in that case the schemas must be explicitly provided with the ``XSD`` " +"open option." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:48 +msgid "Mapping of XML structure to OGR layers and fields" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:50 +msgid "" +"The driver scans the XML schemas referenced by the XML/GML to build the " +"OGR layers and fields. It is strictly required that the schemas, directly" +" or indirectly used, are fully valid. The content of the XML/GML file " +"itself is marginally used, mostly to determine the SRS of geometry " +"columns." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:56 +msgid "" +"XML elements declared at the top level of a schema will generally be " +"exposed as OGR layers. Their attributes and sub-elements of simple XML " +"types (string, integer, real, ...) will be exposed as OGR fields. For " +"sub-elements of complex type, different cases can happen. If the " +"cardinality of the sub-element is at most one and it is not referenced by" +" other elements, then it is \"flattened\" into its enclosing element. " +"Otherwise it will be exposed as a OGR layer, with either a link to its " +"\"parent\" layer if the sub-element is specific to its parent element, or" +" through a junction table if the sub-element is shared by several " +"parents." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:67 +msgid "" +"By default the driver is robust to documents non strictly conforming to " +"the schemas. Unexpected content in the document will be silently ignored," +" as well as content required by the schema and absent from the document." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:72 +msgid "" +"Consult the :ref:`GMLAS mapping examples <gmlas_mapping_examples>` page " +"for more details." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:75 +msgid "" +"By default in the configuration, swe:DataRecord and swe:DataArray " +"elements from the Sensor Web Enablement (SWE) Common Data Model namespace" +" will receive a special processing, so they are mapped more naturally to " +"OGR concepts. The swe:field elements will be mapped as OGR fields, and " +"the swe:values element of a swe:DataArray will be parsed into OGR " +"features in a dedicated layer for each swe:DataArray. Note that those " +"conveniency exposure is for read-only purpose. When using the write side " +"of the driver, only the content of the general mapping mechanisms will be" +" used." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:86 +msgid "Metadata layers" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:88 +msgid "" +"Three special layers \"_ogr_fields_metadata\", \"_ogr_layers_metadata\", " +"\"_ogr_layer_relationships\" and \"_ogr_other_metadata\" add extra " +"information to the basic ones you can get from the OGR data model on OGR " +"layers and fields." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:93 +msgid "" +"Those layers are exposed if the :oo:`EXPOSE_METADATA_LAYERS` open option " +"is set to YES (or if enabled in the configuration). They can also be " +"individually retrieved by specifying their name in calls to " +"GetLayerByName(), or on as layer names with the ogrinfo and ogr2ogr " +"utility." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:99 +msgid "" +"Consult the :ref:`GMLAS metadata layers <gmlas_metadata_layers>` page for" +" more details." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:103 +msgid "Configuration file" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:105 +msgid "" +"A default configuration file " +":source_file:`ogr/ogrsf_frmts/gmlas/data/gmlasconf.xml` file is provided " +"in the data directory of the GDAL installation. Its structure and content" +" is documented in :source_file:`ogr/ogrsf_frmts/gmlas/data/gmlasconf.xsd`" +" schema." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:112 +msgid "This configuration file enables the user to modify the following settings:" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:115 +msgid "whether remote schemas should be downloaded. Enabled by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:116 +msgid "whether the local cache of schemas is enabled. Enabled by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:117 +msgid "the path of the local cache. By default, $HOME/.gdal/gmlas_xsd_cache" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:118 +msgid "" +"whether validation of the document against the schemas should be enabled." +" Disabled by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:120 +msgid "" +"whether validation error should cause dataset opening to fail. Disabled " +"by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:122 +msgid "" +"whether the metadata layers should be exposed by default. Disabled by " +"default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:124 +msgid "" +"whether a 'ogr_pkid' field should always be generated. Disabled by " +"default. Turning that on can be useful on layers that have a ID attribute" +" whose uniqueness is not guaranteed among various documents. Which could " +"cause issues when appending several documents into a target database " +"table." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:129 +msgid "" +"whether layers and fields that are not used in the XML document should be" +" removed. Disable by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:131 +msgid "whether OGR array data types can be used. Enabled by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:132 +msgid "" +"whether the XML definition of the GML geometry should be reported as a " +"OGR string field. Disabled by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:134 +msgid "" +"whether only XML elements that derive from gml:_Feature or " +"gml:AbstractFeature should be considered in the initial pass of the " +"schema building, when at least one element in the schemas derive from " +"them. Enabled by default." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:138 +msgid "several rules to configure if and how xlink:href should be resolved." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:139 +msgid "" +"a definition of XPaths of elements and attributes that must be ignored, " +"so as to lighten the number of OGR layers and fields." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:142 +msgid "" +"This file can be adapted and modified versions can be provided to the " +"driver with the :oo:`CONFIG_FILE` open option. None of the elements of " +"the configuration file are required. When they are absent, the default " +"value indicated in the schema documentation is used." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:147 +msgid "" +"Configuration can also be provided through other open options. Note that " +"some open options have identical names to settings present in the " +"configuration file. When such open option is provided, then its value " +"will override the one of the configuration file (either the default one, " +"or the one provided through the :oo:`CONFIG_FILE` open option)." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:154 +msgid "Geometry support" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:156 +msgid "" +"XML schemas only indicate the geometry type but do not constraint the " +"spatial reference systems (SRS), so it is theoretically possible to have " +"object instances of the same class having different SRS for the same " +"geometry field. This is not practical to deal with, so when geometry " +"fields are detected, an initial scan of the document is done to find the " +"first geometry of each geometry field that has an explicit srsName set. " +"This one will be used for the whole geometry field. In case other " +"geometries of the same field would have different SRS, they will be " +"reprojected." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:166 +msgid "" +"By default, only the OGR geometry built from the GML geometry is exposed " +"in the OGR feature. It is possible to change the IncludeGeometryXML " +"setting of the configuration file to true so as to expose a OGR string " +"field with the XML definition of the GML geometry." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:174 +msgid "" +"Traditionnaly to read a OGR datasource, one iterate over layers with " +"GDALDataset::GetLayer(), and for each layer one iterate over features " +"with OGRLayer::GetNextFeature(). While this approach still works for the " +"GMLAS driver, it may result in very poor performance on big documents or " +"documents using complex schemas that are translated in many OGR layers." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:180 +msgid "" +"It is thus recommended to use GDALDataset::GetNextFeature() to iterate " +"over features as soon as they appear in the .gml/.xml file. This may " +"return features from non-sequential layers, when the features include " +"nested elements." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:260 +msgid "Whether unused layers should be removed from the reported layers." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:288 +msgid "" +"The GMLAS driver can write XML documents in a schema-driven way by " +"converting a source dataset (contrary to most other drivers that have " +"read support that implement the CreateLayer() and CreateFeature() " +"interfaces). The typical workflow is to use the read side of the GMLAS " +"driver to produce a SQLite/Spatialite/ PostGIS database, potentially " +"modify the features imported and re-export this database as a new XML " +"document." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:296 +msgid "" +"The driver will identify in the source dataset \"top-level\" layers, and " +"in those layers will find which features are not referenced by other top-" +"level layers. As the creation of the output XML is schema-driver, the " +"schemas need to be available. There are two possible ways:" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:301 +msgid "" +"either the result of the processing of the schemas was stored as the 4 " +"\\_ogr_\\* metadata tables in the source dataset by using the " +":oo:`EXPOSE_METADATA_LAYERS=YES` open option when converting the source " +".xml)," +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:305 +msgid "" +"or the schemas can be specified at creation time with the " +":dsco:`INPUT_XSD` creation option." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:308 +msgid "" +"By default, the driver will \"wrap\" the features inside a WFS 2.0 " +"wfs:FeatureCollection / wfs:member element. It is also possible to ask " +"the driver to create instead a custom wrapping .xsd file that declares " +"the ogr_gmlas:FeatureCollection / ogr_gmlas:featureMember XML elements." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:313 +msgid "" +"Note that while the file resulting from the export should be XML valid, " +"there is no strong guarantee that it will validate against the additional" +" constraints expressed in XML schema(s). This will depend on the content " +"of the features (for example if converting from a GML file that is not " +"conformant to the schemas, the output of the driver will generally be not" +" validating)" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:320 +msgid "" +"If the input layers have geometries stored as GML content in a \\_xml " +"suffixed field, then the driver will compare the OGR geometry built from " +"that XML content with the OGR geometry stored in the dedicated geometry " +"field of the feature. If both match, then the GML content stored in the " +"\\_xml suffixed field will be used, such as to preserve particularities " +"of the initial GML content. Otherwise GML will be exported from the OGR " +"geometry." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:328 +msgid "" +"To increase export performance on very large databases, creating " +"attribute indexes on the fields pointed by the 'layer_pkid_name' " +"attribute in '_ogr_layers_metadata' might help." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:333 +msgid "ogr2ogr behavior" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:335 +msgid "" +"When using ogr2ogr / GDALVectorTranslate() to convert to XML/GML from a " +"source database, there are restrictions to the options that can be used. " +"Only the following options of ogr2ogr are supported:" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:339 +msgid "dataset creation options (see below)" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:340 +msgid "layer names" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:341 +msgid "spatial filter through -spat option." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:342 +msgid "attribute filter through -where option" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:344 +msgid "" +"The effect of spatial and attribute filtering will only apply on top-" +"levels layers. Sub-features selected through joins will not be affected " +"by those filters." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:351 +msgid "" +"|about-dataset-creation-options| The supported dataset creation options " +"are:" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:451 +msgid "Listing content of a data file:" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:457 +msgid "Converting to PostGIS:" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:463 +msgid "Converting to Spatialite and back to GML" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:473 +msgid "" +":ref:`GML <vector.gml>`: general purpose driver not requiring the " +"presence of schemas, but with limited support for complex features" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:475 +msgid "" +":ref:`NAS/ALKIS <vector.nas>`: specialized GML driver for cadastral data " +"in Germany" +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:481 +msgid "" +"Initial implementation has been funded by the European Union's Earth " +"observation programme Copernicus, as part of the tasks delegated to the " +"European Environment Agency." +msgstr "" + +#: ../../source/drivers/vector/gmlas.rst:485 +msgid "" +"Development of special processing of some Sensor Web Enablement (SWE) " +"Common Data Model swe:DataRecord and swe:DataArray constructs has been " +"funded by Bureau des Recherches Géologiques et Minières (BRGM)." +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:4 +msgid "GMLAS - Mapping examples" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:6 +msgid "" +"This page gives a few examples of how XML constructs are mapped to OGR " +"layers and fields by the :ref:`vector.gmlas` driver." +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:10 +msgid "Mapping examples" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:14 +msgid "Document" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:15 +msgid "OGR layers" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:16 +#: ../../source/drivers/vector/selafin.rst:77 +msgid "Comments" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:47 +msgid "" +"Element with attributes and sub-elements of simple type and maximum " +"cardinality of 1." +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:98 +msgid "Example with array and child layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:152 +msgid "" +"Example of nested element, that can be folded into main layer. Use of an " +"attribute on a sub-element." +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:268 +msgid "" +"Example of of a common element \"name\" referenced by 2 layers " +"\"MyFeature\" and \"MyFeature1\". The links are established through the " +"junction layers \"MyFeature_names_name_name\" and " +"\"MyFeature2_names_name_name\"." +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:273 +msgid "swe:DataArray" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:275 +msgid "The following snippet" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:317 +msgid "will receive a special processing to be mapped into a dedicated layer:" +msgstr "" + +#: ../../source/drivers/vector/gmlas_mapping_examples.rst:353 +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:161 +msgid ":ref:`main documentation page for GMLAS driver <vector.gmlas>`" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:4 +msgid "GMLAS - Metadata layers" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:6 +msgid "" +"This page details the structure of the extra metadata layers reported by " +"the :ref:`vector.gmlas` driver." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:10 +msgid "\\_ogr_fields_metadata layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:12 +msgid "" +"This layer gives metadata about OGR fields, and also \"abstract\" fields " +"that describe the relation ship between a parent and child layer." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:15 +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:93 +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:121 +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:142 +msgid "Its fields are:" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:17 +msgid "``layer_name``: Name of the layer to which the field belongs to" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:19 +msgid "" +"``field_name``: Name of the field. May be null when field_category is " +"PATH_TO_CHILD_ELEMENT_NO_LINK or GROUP" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:22 +msgid "" +"``field_xpath``: XPath of the element/attribute whose content is used for" +" the field. The XPath is relative to the element that is the direct " +"parent of this element/attribute, or a parent element in case of " +"flattening. May be null for a field generated by OGR." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:27 +msgid "" +"``field_type``: the XML schema base data type (string, int, long, ID, " +"...). Extended with \"geometry\". May be null for a field generated by " +"OGR" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:30 +msgid "``field_is_list``: Whether the XML type is a list." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:32 +msgid "" +"``field_min_occurs``: Integer value with the minimum number of " +"occurrences of values. 0 or 1 typically. Or more for array types. May be " +"null for a field generated by OGR" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:36 +msgid "" +"``field_max_occurs``: Integer value with the maximum number of " +"occurrences of values. 1 typically. Or more for array types. 2147483647 " +"means unlimited. May be null for a field generated by OGR" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:40 +msgid "" +"``field_repetition_on_sequence``: Boolean value to indicate if the field " +"is related to a <sequence maxOccurs=\">1 or unbounded\"> construct. Only " +"set when field_max_occurs is not 0 or 1." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:44 +msgid "``field_default_value``: Default value of the field, or null" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:46 +msgid "``field_fixed_value``: Fixed value of the field, or null" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:48 +msgid "" +"``field_category``: Category of the field. May be REGULAR, " +"PATH_TO_CHILD_ELEMENT_NO_LINK, PATH_TO_CHILD_ELEMENT_WITH_LINK, " +"PATH_TO_CHILD_ELEMENT_WITH_JUNCTION_TABLE, GROUP or SWE_FIELD. May be " +"null for a field generated by OGR." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:53 +msgid "" +"``field_related_layer``: Name of the child layer for field_category != " +"REGULAR" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:55 +msgid "" +"``field_junction_layer``: Name of the junction layer. Only set if " +"field_category is equal to PATH_TO_CHILD_ELEMENT_WITH_JUNCTION_TABLE" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:58 +msgid "``field_documentation``: Documentation from the schema." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:60 +msgid "Explanation of field_category values:" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:62 +msgid "" +"REGULAR: the field is made from the value of an element or attribute that" +" is a direct child of the element that is the root of the layer " +"considered." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:65 +msgid "" +"PATH_TO_CHILD_ELEMENT_NO_LINK: A field declared with this category is not" +" instantiated as a OGR field of the layer 'layer_name'. It is merely " +"there to declare the relationship between the parent and child layers. " +"This is when a sub-element is of a complex type or a repeated sub-element" +" of simple type that does not match one of the OGR array types." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:71 +msgid "" +"PATH_TO_CHILD_ELEMENT_WITH_LINK: the content of this field is the primary" +" key of a OGR feature of another layer. The field_related_layer field " +"contains the name of that linked layer." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:74 +msgid "" +"PATH_TO_CHILD_ELEMENT_WITH_JUNCTION_TABLE: A field declared with this " +"category is not instantiated as a OGR field of the layer 'layer_name'. It" +" is merely there to declare the relationship between the parent and child" +" layers. This is when the link between the parent and child layer is done" +" through a junction table (case where the child layer is referenced by " +"other parent layers)." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:80 +msgid "" +"GROUP: A field declared with this category is not instantiated as a OGR " +"field of the layer 'layer_name'. It is merely there to declare the " +"relationship between the parent and child layers. This is when a layer " +"uses XML schema group constructs with repeated cardinality." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:84 +msgid "" +"SWE_FIELD: A field derived from special processing of swe:DataRecord or " +"swe:DataArray elements." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:89 +msgid "\\_ogr_layers_metadata layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:91 +msgid "This layer gives metadata about OGR layers." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:95 +msgid "``layer_name``: Name of the layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:97 +msgid "" +"``layer_xpath``: XPath of the element that is used as the root element " +"for the layer. May be suffixed with \";extra=XXXX\" for group constructs " +"or repeated sequences of repeated elements, so as to distinguish for the " +"XPath of their parent element. Will be null for junction tables or " +"SWE_DATA_ARRAY layers." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:102 +msgid "" +"``layer_category``: Category of the layer. One of TOP_LEVEL_ELEMENT, " +"NESTED_ELEMENT, JUNCTION_TABLE or SWE_DATA_ARRAY" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:105 +msgid "" +"``layer_pkid_name``: Name of the primary key field. This is the text " +"attribute that uniquely identified a feature (in its layer). This is the " +"XML attribute/name of type xs:ID when it exists, otherwise a \"ogr_pkid\"" +" field is automatically created. Will be null for SWE_DATA_ARRAY layers." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:110 +msgid "" +"``layer_parent_pkid_name``: Name of the field that is a foreign key to " +"the parent layer of this layer. Only set for a NESTED_ELEMENT layer." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:113 +msgid "``layer_documentation``: Documentation from the schema." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:117 +msgid "\\_ogr_layer_relationships layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:119 +msgid "This layer gives metadata about relationship between OGR layers." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:123 +msgid "``parent_layer``: Name of the parent layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:125 +msgid "``parent_pkid``: Name of the primary key of the parent layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:127 +msgid "" +"``parent_element_name``: Name of the XML element that links from the " +"parent to the child. Will be null when the child layer is due to group " +"constructs or repeated sequences of repeated elements of the parent." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:131 +msgid "``child_layer``: Name of the child layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:133 +msgid "" +"``child_pkid``: Name of the primary key of the child layer. Will be null " +"for SWE_DATA_ARRAY layers" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:138 +msgid "\\_ogr_other_metadata layer" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:140 +msgid "This layer contains key / value pairs with different information." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:144 +msgid "``key``: Name of the metadata item" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:145 +msgid "``value``: Value of the metadata imtem" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:147 +msgid "Possible keys are :" +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:149 +msgid "document_filename: Filename of the XML/GML file read." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:150 +msgid "configuration_filename: Filename of the XML configuration file used." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:151 +msgid "configuration_inlined: XML content of the configuration file." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:152 +msgid "namespace_uri_XX: URI of a namespace referenced by the schema(s)." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:153 +msgid "namespace_location_XX: Location of a schema." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:154 +msgid "namespace_prefix_XX: Prefix of a namespace referenced by the schema(s)." +msgstr "" + +#: ../../source/drivers/vector/gmlas_metadata_layers.rst:156 +msgid "gml_version: GML version, such as 2.1.2, 3.1.1 or 3.2.1" +msgstr "" + +#: ../../source/drivers/vector/gmt.rst:6 +msgid "GMT" +msgstr "" + +#: ../../source/drivers/vector/gmt.rst:10 +msgid "" +"OGR supports reading and writing GMT ASCII vector format. This is the " +"format used by the Generic Mapping Tools (GMT) package, and includes " +"recent additions to the format to handle more geometry types, and " +"attributes. Currently GMT files are only supported if they have the " +"extension \".gmt\". Old (simple) GMT files are treated as either point, " +"or linestring files depending on whether a \">\" line is encountered " +"before the first vertex. New style files have a variety of auxiliary " +"information including geometry type, layer extents, coordinate system and" +" attribute field declarations in comments in the header, and for each " +"feature can have attributes." +msgstr "" + +#: ../../source/drivers/vector/gmt.rst:33 +msgid "" +"The driver supports creating new GMT files, and appending additional " +"features to existing files, but update of existing features is not " +"supported. Each layer is created as a separate .gmt file. If a name that " +"ends with .gmt is not given, then the GMT driver will take the layer name" +" and add the \".gmt\" extension." +msgstr "" + +#: ../../source/drivers/vector/gmt.rst:39 +msgid "" +"Writing to /dev/stdout or /vsistdout/ is supported since GDAL 3.5.0 (note" +" that the file will then lack the optional region/bounding box header " +"item)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:4 +msgid "GPKG -- GeoPackage vector" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:10 +msgid "" +"This driver implements support for access to spatial tables in the `OGC " +"GeoPackage format standard " +"<http://www.opengeospatial.org/standards/geopackage>`__ The GeoPackage " +"standard uses a SQLite database file as a generic container, and the " +"standard defines:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:16 +msgid "" +"Expected metadata tables (``gpkg_contents``, ``gpkg_spatial_ref_sys``, " +"``gpkg_geometry_columns``)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:18 +msgid "" +"Binary format encoding for geometries in spatial tables (basically a GPKG" +" standard header object followed by ISO standard well-known binary (WKB))" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:21 +msgid "" +"Naming and conventions for extensions (extended feature types) and " +"indexes (how to use SQLite r-tree in an interoperable manner)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:28 +msgid "" +"The driver also supports reading and writing the following non-linear " +"geometry types: CIRCULARSTRING, COMPOUNDCURVE, CURVEPOLYGON, MULTICURVE " +"and MULTISURFACE" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:32 +msgid "" +"GeoPackage raster/tiles are supported. See the :ref:`GeoPackage raster " +"<raster.gpkg>` documentation page." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:45 +#: ../../source/drivers/vector/xodr.rst:22 +msgid "Specification version" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:47 +msgid "" +"Starting with GDAL 2.2, the driver is able to create GeoPackage databases" +" following the 1.0/1.0.1, 1.1 or 1.2 versions. For GDAL 2.2, it will " +"automatically adjust to the minimum version required for the features of " +"GeoPackage used. For GDAL 2.3 or later, it will default to 1.2. Explicit " +"version choice can be done by specifying the VERSION dataset creation " +"option." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:57 +msgid "GeoPackage only supports one geometry column per table." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:62 +msgid "" +"The driver supports OGR attribute filters, and users are expected to " +"provide filters in the SQLite dialect, as they will be executed directly " +"against the database." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:66 +msgid "" +"SQL SELECT statements passed to ExecuteSQL() are also executed directly " +"against the database. If Spatialite is used, a recent version (4.2.0) is " +"needed and use of explicit cast operators AsGPB() is required to " +"transform GeoPackage geometries to Spatialite geometries (the reverse " +"conversion from Spatialite geometries is automatically done by the GPKG " +"driver). It is also possible to use with any Spatialite version, but in a" +" slower way, by specifying the \"INDIRECT_SQLITE\" dialect. In which " +"case, GeoPackage geometries automatically appear as Spatialite geometries" +" after translation by OGR." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:76 +msgid "" +"Starting with GDAL 2.2, the \"DROP TABLE layer_name\" and \"ALTER TABLE " +"layer_name RENAME TO new_layer\" statements can be used. They will update" +" GeoPackage system tables." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:80 +msgid "" +"Starting with GDAL 2.2, the " +"\"HasSpatialIndex('table_name','geom_col_name')\" statement can be used " +"for checking if the table has spatial index on the named geometry column." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:85 +msgid "" +"When dropping a table, or removing records from tables, the space they " +"occupied is not immediately released and kept in the pool of file pages " +"that SQLite may reuse later. If you need to shrink the file to its " +"minimum size, you need to issue an explicit \"VACUUM\" SQL request. Note " +"that this will result in a full rewrite of the file." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:92 +msgid "SQL functions" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:94 +msgid "" +"The following SQL functions, from the GeoPackage specification, are " +"available:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:96 +msgid "ST_MinX(geom *Geometry*): returns the minimum X coordinate of the geometry" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:98 +msgid "ST_MinY(geom *Geometry*): returns the minimum Y coordinate of the geometry" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:100 +msgid "ST_MaxX(geom *Geometry*): returns the maximum X coordinate of the geometry" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:102 +msgid "ST_MaxY(geom *Geometry*): returns the maximum Y coordinate of the geometry" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:104 +msgid "" +"ST_IsEmpty(geom *Geometry*): returns 1 if the geometry is empty (but not " +"null), e.g. a POINT EMPTY geometry" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:106 +msgid "" +"ST_GeometryType(geom *Geometry*): returns the geometry type: 'POINT', " +"'LINESTRING', 'POLYGON', 'MULTIPOLYGON', 'MULTILINESTRING', 'MULTIPOINT'," +" 'GEOMETRYCOLLECTION'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:109 +msgid "ST_SRID(geom *Geometry*): returns the SRID of the geometry" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:110 +msgid "" +"GPKG_IsAssignable(expected_geom_type *String*, actual_geom_type *String*)" +" : mainly, needed for the 'Geometry Type Triggers Extension'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:113 +msgid "" +"The following functions, with identical syntax and semantics as in " +"Spatialite, are also available :" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:116 +msgid "" +"CreateSpatialIndex(table_name *String*, geom_column_name *String*): " +"creates a spatial index (RTree) on the specified table/geometry column" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:119 +msgid "" +"DisableSpatialIndex(table_name *String*, geom_column_name *String*): " +"drops an existing spatial index (RTree) on the specified table/geometry " +"column" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:122 +msgid "" +"ST_Area(geom *Geometry*): compute the area in square units of the " +"geometry SRS." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:123 +msgid "" +"ST_Area(geom *Geometry*, use_ellipsoid *boolean*): (GDAL >= 3.9): compute" +" the area in square meters, considering the geometry on the ellipsoid " +"(use_ellipsoid must be set to true/1)." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:126 +msgid "" +"SetSRID(geom *Geometry*, srs_id *Integer*): overrides the geometry' SRS " +"ID, without reprojection." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:128 +msgid "" +"ST_Transform(geom *Geometry*, target_srs_id *Integer*): reproject the " +"geometry to the SRS of specified srs_id. If no SRS with that given srs_id" +" is not found in gpkg_spatial_ref_sys, starting with GDAL 3.2, it will be" +" interpreted as a EPSG code." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:132 +msgid "" +"ST_EnvIntersects(geom *Geometry*, minx *Double*, miny *Double*, maxx " +"*Double*, maxy *Double*): (GDAL >= 3.7) Returns 1 if the minimum bounding" +" box of geom intersects the bounding box defined by " +"(minx,miny)-(maxx,maxy), or 0 otherwise." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:135 +msgid "" +"ST_EnvIntersects(geom1 *Geometry*, geom2 *Geometry*): (GDAL >= 3.7) " +"Returns 1 if the minimum bounding box of geom1 intersects the one of " +"geom2, or 0 otherwise. (Note: this function, as all others, does not " +"automatically uses spatial indices)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:140 +msgid "" +"The raster SQL functions mentioned at :ref:`raster.gpkg.raster` are also " +"available." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:144 +msgid "Link with Spatialite" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:146 +msgid "" +"If it has been compiled against Spatialite 4.2 or later, it is also " +"possible to use Spatialite SQL functions. Explicit transformation from " +"GPKG geometry binary encoding to Spatialite geometry binary encoding must" +" be done." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:155 +msgid "Starting with Spatialite 4.3, CastAutomagic is no longer needed." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:157 +msgid "" +"Note that due to the loose typing mechanism of SQLite, if a geometry " +"expression returns a NULL value for the first row, this will generally " +"cause OGR not to recognize the column as a geometry column. It might be " +"then useful to sort the results by making sure that non-null geometries " +"are returned first:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:170 +#: ../../source/drivers/vector/sqlite.rst:228 +msgid "" +"The driver implements transactions at the database level, per " +":ref:`rfc-54`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:177 +msgid "" +"Many-to-many relationship retrieval is supported, respecting the OGC " +"GeoPackage Related Tables Extension. One-to-many relationships will also " +"be reported for tables which utilize FOREIGN KEY constraints." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:180 +msgid "" +"Relationship creation, deletion and updating is supported since GDAL 3.7." +" Relationships can only be updated to change their base or related table " +"fields, or the relationship related table type. It is not permissible to " +"change the base or related table itself, or the mapping table details. If" +" this is desired then a new relationship should be created instead." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:185 +msgid "" +"Note that when a many-to-many relationship is created in a GeoPackage, " +"GDAL will always insert the mapping table into the gpkg_contents table. " +"Formally this is not required by the Related Tables Extension (instead, " +"the table should only be listed in gpkgext_relations), however failing to" +" list the mapping table in gpkg_contents prevents it from being usable in" +" some other applications (e.g. ESRI software)." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:192 +#: ../../source/drivers/vector/odbc.rst:62 +#: ../../source/drivers/vector/openfilegdb.rst:103 +#: ../../source/drivers/vector/pg.rst:154 +#: ../../source/drivers/vector/pgeo.rst:70 +#: ../../source/drivers/vector/sqlite.rst:241 +msgid "Dataset open options" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:222 +msgid "" +"The attached database must be a GeoPackage one too, so that its geometry " +"blobs are properly recognized (so typically not a Spatialite one)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:248 +msgid "" +"Note: open options are typically specified with \"-oo name=value\" syntax" +" in most OGR utilities, or with the ``GDALOpenEx()`` API call." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:251 +msgid "" +"Note: configuration option :config:`OGR_SQLITE_JOURNAL` can be used to " +"set the journal mode of the GeoPackage (and thus SQLite) file, see also " +"https://www.sqlite.org/pragma.html#pragma_journal_mode." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:258 +msgid "" +"When creating a new GeoPackage file, the driver will attempt to force the" +" database into a UTF-8 mode for text handling, satisfying the OGR strict " +"UTF-8 capability. For pre-existing files, the driver will work with " +"whatever it is given." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:274 +msgid "" +"|about-dataset-creation-options| The following creation options (specific" +" to vector, or common with raster) are available:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:339 +msgid "" +"Other options are available for raster. See the :ref:`GeoPackage raster " +"<raster.gpkg>` documentation page." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:490 +msgid ":copy-config:`OGR_SQLITE_JOURNAL`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:492 +msgid ":copy-config:`OGR_SQLITE_CACHE`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:494 +msgid ":copy-config:`OGR_SQLITE_SYNCHRONOUS`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:496 +msgid ":copy-config:`OGR_SQLITE_LOAD_EXTENSIONS`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:498 +msgid ":copy-config:`OGR_SQLITE_PRAGMA`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:510 +msgid ":copy-config:`SQLITE_USE_OGR_VFS`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:527 +msgid "" +"GDAL uses the standardized `gpkg_metadata " +"<http://www.geopackage.org/spec/#_metadata_table>`__ and " +"`gpkg_metadata_reference " +"<http://www.geopackage.org/spec/#_metadata_reference_table>`__ tables to " +"read and write metadata, on the dataset and layer objects." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:533 +msgid "" +"GDAL metadata, from the default metadata domain and possibly other " +"metadata domains, is serialized in a single XML document, conformant with" +" the format used in GDAL PAM (Persistent Auxiliary Metadata) .aux.xml " +"files, and registered with md_scope=dataset and " +"md_standard_uri=http://gdal.org in gpkg_metadata. For the dataset, this " +"entry is referenced in gpkg_metadata_reference with a " +"reference_scope=geopackage. For a layer, this entry is referenced in " +"gpkg_metadata_reference with a reference_scope=table and table_name={name" +" of the table}" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:554 +msgid "Non-spatial tables" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:556 +msgid "" +"The core GeoPackage specification of GeoPackage 1.0 and 1.1 did not " +"support non-spatial tables. This was added in GeoPackage 1.2 as the " +"\"attributes\" data type." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:560 +msgid "" +"The driver allows creating and reading non-spatial tables with the " +":ref:`vector.geopackage_aspatial`." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:562 +msgid "" +"Starting with GDAL 2.2, the driver will also, by default, list non " +"spatial tables that are not registered through the gdal_aspatial " +"extension, and support the GeoPackage 1.2 \"attributes\" data type as " +"well. Starting with GDAL 2.2, non spatial tables are by default created " +"following the GeoPackage 1.2 \"attributes\" data type (can be controlled " +"with the :lco:`ASPATIAL_VARIANT` layer creation option)." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:570 +msgid "Spatial views" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:572 +msgid "" +"Views can be created and recognized as valid spatial layers if a " +"corresponding record is inserted into the gpkg_contents and " +"gpkg_geometry_columns table." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:576 +msgid "" +"Starting with GDAL 2.2, in the case of the columns in the SELECT clause " +"of the view acts a integer primary key, then it can be recognized by OGR " +"as the FID column of the view, provided it is renamed as OGC_FID. " +"Selecting a feature id from a source table without renaming will not be " +"sufficient, since due to joins this feature id could appear several " +"times. Thus the user must explicitly acknowledge that the column is " +"really a primary key." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:592 +msgid "" +"This requires GDAL to be compiled with the SQLITE_HAS_COLUMN_METADATA " +"option and SQLite3 with the SQLITE_ENABLE_COLUMN_METADATA option. " +"Starting with GDAL 2.3, this can be easily verified if the " +"SQLITE_HAS_COLUMN_METADATA=YES driver metadata item is declared (for " +"example with \"ogrinfo --format GPKG\")." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:598 +msgid "" +"Starting with GDAL 3.7.1, it is possible to define a geometry column as " +"the result of a Spatialite spatial function. Note however that this is an" +" extension likely to be non-interoperable with other software that does " +"not activate Spatialite for the SQLite3 database connection. Such " +"geometry column should be registered into the ``gpkg_extensions`` using " +"the ``gdal_spatialite_computed_geom_column`` extension name (cf " +":ref:`vector.gpkg_spatialite_computed_geom_column`), like below:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:618 +msgid "Coordinate Reference Systems" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:620 +msgid "" +"Valid geographic, projected and compound CRS supported in general by GDAL" +" are also supported by GeoPackage and stored in the " +"``gpkg_spatial_ref_sys`` table." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:623 +msgid "Two special hard-coded CRS are reserved per the GeoPackage specification:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:625 +msgid "" +"srs_id=0, for a Undefined Geographic CRS. For GDAL 3.8 or earlier, this " +"one is selected by default if creating a spatial layer without any " +"explicit CRS" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:628 +msgid "" +"srs_id=-1, for a Undefined Projected CRS. It might be selected by " +"creating a layer with a CRS instantiated from the following WKT string: " +"``LOCAL_CS[\"Undefined Cartesian SRS\"]``. (GDAL >= 3.3)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:632 +msgid "" +"Starting with GDAL 3.9, a layer without any explicit CRS is mapped " +"from/to a custom entry of srs_id=99999 with the following properties:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:635 +msgid "``srs_name``: ``Undefined SRS``" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:636 +msgid "``organization``: ``GDAL``" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:637 +msgid "``organization_coordsys_id``: 99999" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:638 +msgid "" +"``definition``: ``LOCAL_CS[\"Undefined " +"SRS\",LOCAL_DATUM[\"unknown\",32767],UNIT[\"unknown\",0],AXIS[\"Easting\",EAST],AXIS[\"Northing\",NORTH]]``" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:639 +msgid "" +"``definition_12_063`` (when the CRS WKT extension is used): " +"``ENGCRS[\"Undefined " +"SRS\",EDATUM[\"unknown\"],CS[Cartesian,2],AXIS[\"easting\",east,ORDER[1],LENGTHUNIT[\"unknown\",0]],AXIS[\"northing\",north,ORDER[2],LENGTHUNIT[\"unknown\",0]]]``" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:640 +msgid "``description``: ``Custom undefined coordinate reference system``" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:642 +msgid "" +"Note that the use of a LOCAL_CS / EngineeringCRS is mostly to provide a " +"valid CRS definition to comply with the requirements of the GeoPackage " +"specification and to be compatible of other applications (or GDAL 3.8 or " +"earlier), but the semantics of that entry is intended to be \"undefined " +"SRS of any kind\"." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:650 +msgid "(Restricted to those that have a vector scope)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:658 +msgid "" +"`Non-Linear Geometry Types " +"<http://www.geopackage.org/guidance/extensions/nonlinear_geometry_types.html>`__" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:660 +msgid "Yes, since GDAL 2.1" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:661 +msgid "" +"`RTree Spatial Indexes " +"<http://www.geopackage.org/guidance/extensions/rtree_spatial_indexes.html>`__" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:667 +msgid "`Schema <http://www.geopackage.org/guidance/extensions/schema.html>`__" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:669 +msgid "Yes, since GDAL 3.3 (Geopackage constraints exposed as field domains)" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:672 +msgid "" +"Partially, since GDAL 2.2. GDAL can read databases using this extension, " +"but cannot interpret a SRS entry that has only a WKT v2 entry." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:673 +msgid ":ref:`vector.geopackage_aspatial`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:675 +msgid "Yes. Deprecated in GDAL 2.2 for the *attributes* official data_type" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:676 +msgid ":ref:`vector.gpkg_spatialite_computed_geom_column`" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:678 +msgid "Yes, starting with GDAL 3.7.1" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:679 +msgid "" +"`OGC GeoPackage Related Tables Extension <http://www.geopackage.org/spec" +"/related-tables/>`__" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:681 +msgid "Yes, starting with GDAL 3.6" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:684 +#: ../../source/drivers/vector/shapefile.rst:269 +msgid "Compressed files" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:686 +msgid "" +"Starting with GDAL 3.7, the driver can also support reading and creating " +".gpkg.zip files containing one .gpkg file." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:689 +msgid "" +"On large files, good read performance can only be achieved if the file " +"inside the .zip is not compressed or compressed using the `SOZip " +"<https://sozip.org>`__ optimization." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:693 +msgid "Update of an existing file is not supported." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:695 +msgid "" +"Creation involves the creation of a temporary file. Sufficiently large " +"files will be automatically compressed using the SOZip optimization." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:705 +msgid "" +"The GeoPackage driver supports reading and writing the geometry " +"coordinate precision, using the :cpp:class:`OGRGeomCoordinatePrecision` " +"settings of the :cpp:class:`OGRGeomFieldDefn`. By default, the geometry " +"coordinate precision is only noted in metadata, and does not cause " +"geometries that are written to be modified to comply with this precision." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:711 +msgid "Several settings may be combined to apply further processing:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:713 +msgid "" +"if the :config:`OGR_APPLY_GEOM_SET_PRECISION` configuration option is set" +" to ``YES``, the :cpp:func:`OGRGeometry::SetPrecision` method will be " +"applied when calling the CreateFeature() and SetFeature() method of the " +"driver, to round X and Y coordinates to the specified precision, and fix " +"potential geometry invalidities resulting from the rounding." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:719 +msgid "" +"if the ``DISCARD_COORD_LSB`` layer creation option is set to YES, the " +"less-significant bits of the WKB geometry encoding which are not relevant" +" for the requested precision are set to zero. This can improve further " +"lossless compression stages, for example when putting a GeoPackage in an " +"archive. Note however that when reading back such geometries and " +"displaying them to the maximum precision, they will not \"exactly\" match" +" the original :cpp:class:`OGRGeomCoordinatePrecision` settings. However, " +"they will round back to it. The value of the ``DISCARD_COORD_LSB`` layer " +"creation option is written in the dataset metadata, and will be re-used " +"for later edition sessions." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:730 +msgid "" +"if the ``UNDO_DISCARD_COORD_LSB_ON_READING`` layer creation option is set" +" to YES (only makes sense if the ``DISCARD_COORD_LSB`` layer creation " +"option is also set to YES), when *reading* back geometries from a " +"dataset, the :cpp:func:`OGRGeometry::roundCoordinates` method will be " +"applied so that the geometry coordinates exactly match the original " +"specified coordinate precision. That option will only be honored by GDAL " +"3.9 or later." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:738 +msgid "" +"Implementation details: the coordinate precision is stored in a record in" +" each of the ``gpkg_metadata`` and ``gpkg_metadata_reference`` table, " +"with the following additional constraints on top of the ones imposed by " +"the GeoPackage specification:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:743 +msgid "gpkg_metadata.md_standard_uri = 'http://gdal.org'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:744 +msgid "gpkg_metadata.mime_type = 'text/xml'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:745 +msgid "" +"gpkg_metadata.metadata = '<CoordinatePrecision " +"xy_resolution=\"{xy_resolution}\" z_resolution=\"{z_resolution}\" " +"m_resolution=\"{m_resolution}\" discard_coord_lsb={true or false} " +"undo_discard_coord_lsb_on_reading={true or false} />'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:746 +msgid "gpkg_metadata_reference.reference_scope = 'column'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:747 +msgid "gpkg_metadata_reference.table_name = '{table_name}'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:748 +msgid "gpkg_metadata_reference.column_name = '{geometry_column_name}'" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:750 +msgid "" +"Note that the xy_resolution, z_resolution or m_resolution attributes of " +"the XML CoordinatePrecision element are optional. Their numeric value is " +"expressed in the units of the SRS for xy_resolution and z_resolution." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:759 +msgid "" +"The same performance hints apply as those mentioned for the :ref:`SQLite " +"driver <target_drivers_vector_sqlite_performance_hints>`." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:765 +msgid "" +"Simple translation of a single shapefile into GeoPackage. The table 'abc'" +" will be created with the features from abc.shp and attributes from " +"abc.dbf. The file ``filename.gpkg`` must **not** already exist, as it " +"will be created. For adding new layers into existing geopackage run " +"ogr2ogr with **-update**." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:775 +msgid "" +"Update of an existing GeoPackage file – e.g. a GeoPackage template – by " +"adding features to it from another GeoPackage file containing features " +"according to the same or a backwards compatible database schema." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:784 +msgid "" +"Translation of a directory of shapefiles into a GeoPackage. Each file " +"will end up as a new table within the GPKG file. The file " +"``filename.gpkg`` must **not** already exist, as it will be created." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:792 +msgid "" +"Translation of a PostGIS database into a GeoPackage. Each table in the " +"database will end up as a table in the GPKG file. The file " +"``filename.gpkg`` must **not** already exist, as it will be created." +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:800 +msgid "Perform a join between 2 GeoPackage databases:" +msgstr "" + +#: ../../source/drivers/vector/gpkg.rst:811 +msgid ":ref:`GeoPackage raster <raster.gpkg>` documentation page" +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:4 +msgid "GeoPackage Spatialite computed geometry column extension" +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:6 +msgid "GeoPackage 1.3.1 Extension" +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:8 +msgid "" +"Extension follows template from Annex E of the OGC `GeoPackage 1.3.1 " +"Specification`_." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:13 +msgid "Spatialite computed geometry column" +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:18 +msgid "" +"Support for geometry column computed from the result of a SQL function of" +" the Spatialite library." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:29 +msgid "The extension name is ``gdal_spatialite_computed_geom_column``." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:31 +msgid "" +"Each view using the extension should register its geometry column with " +"the following template:" +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:50 +msgid "Extension of Existing Requirement in Clause 2.1 \"Features\"." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:55 +msgid "" +"This extension applies to any view specified in the ``gpkg_contents`` " +"table with a lowercase `data_type` column value of \"features\" which " +"defines its geometry column as the result of a SQL function of the " +"Spatialite library." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:71 +msgid "" +"A view using this extension should have its geometry column defined as " +"the result of a Spatialite SQL function returning a geometry, and wrapped" +" with the ``AsGPB`` function to return a GeoPackage geometry blob." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:75 +msgid "An example of such a view is:" +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:82 +msgid "" +"The view name and geometry column name should be registered in the " +"``gpkg_extensions`` table, as shown in the above Extension Template." +msgstr "" + +#: ../../source/drivers/vector/gpkg_spatialite_computed_geom_column.rst:93 +msgid "" +"This extension assumes that the `Spatialite SQL functions`_ are available" +" at runtime." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:10 +msgid "" +"The GPSBabel driver for now that relies on the `GPSBabel " +"<http://www.gpsbabel.org>`__ utility to access various GPS file formats." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:14 +msgid "The GPSBabel executable must be accessible through the PATH." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:24 +#: ../../source/drivers/vector/mapml.rst:34 +msgid "Read support" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:26 +msgid "" +"The driver needs the :ref:`GPX <vector.gpx>` driver to be fully " +"configured with read support (through Expat library) to be able to parse " +"the output of GPSBabel, as GPX is used as the intermediate pivot format." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:30 +msgid "" +"The returned layers can be waypoints, routes, route_points, tracks, " +"track_points depending on the input data." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:33 +msgid "" +"The syntax to specify an input datasource is : " +"*GPSBabel:gpsbabel_file_format[,gpsbabel_format_option]*:[features=[waypoints,][tracks,][routes]:]filename*" +" where :" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:37 +#: ../../source/drivers/vector/gpsbabel.rst:89 +msgid "" +"*gpsbabel_file_format* is one of the `file formats " +"<http://www.gpsbabel.org/capabilities.shtml>`__ handled by GPSBabel." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:40 +#: ../../source/drivers/vector/gpsbabel.rst:92 +msgid "" +"*gpsbabel_format_option* is any option handled by the specified GPSBabel " +"format (refer to the documentation of each GPSBabel format)" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:42 +msgid "" +"*features=* can be used to modify the type of features that GPSBabel will" +" import. waypoints matches the -w option of gpsbabel commandline, tracks " +"matches -t and routes matches -r. This option can be used to require full" +" data import from GPS receivers that are slow and for which GPSBabel " +"would only fetch waypoints by default. See the documentation on `Route " +"and Track modes " +"<http://www.gpsbabel.org/htmldoc-1.3.6/Route_And_Track_Modes.html>`__ for" +" more details." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:50 +msgid "" +"*filename* can be an actual on-disk file, a file handled through the GDAL" +" virtual file API, or a special device handled by GPSBabel such as " +"\"usb:\", \"/dev/ttyS0\", \"COM1:\", etc.. What is actually supported " +"depends on the used GPSBabel format." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:55 +msgid "" +"Alternatively, for a few selected GPSBabel formats, just specifying the " +"filename might be sufficient. The list includes for now :" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:58 +msgid "garmin_txt" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:59 +msgid "gtrnctr" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:60 +msgid "gdb" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:61 +msgid "magellan" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:62 +msgid "mapsend" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:63 +msgid "mapsource" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:64 +msgid "nmea" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:65 +msgid "osm" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:66 +msgid "ozi" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:67 +msgid "igc" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:69 +msgid "" +"The :config:`USE_TEMPFILE=YES` configuration option can be used to create" +" an on-disk temporary GPX file instead of a in-memory one, when reading " +"big amount of data." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:76 +msgid "" +"The driver relies on the GPX driver to create an intermediate file that " +"will be finally translated by GPSBabel to the desired GPSBabel format. " +"(The GPX driver does not need to be configured for read support for " +"GPSBabel write support.)." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:81 +msgid "" +"The support geometries, options and other creation issues are the ones of" +" the GPX driver. Please refer to its :ref:`documentation <vector.gpx>` " +"for more details." +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:85 +msgid "" +"The syntax to specify an output datasource is : " +"*GPSBabel:gpsbabel_file_format[,gpsbabel_format_option]*:filename* where " +":" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:95 +msgid "" +"Alternatively, you can just pass a filename as output datasource name and" +" specify the dataset creation option " +"GPSBABEL_DRIVER=gpsbabel_file_format[,gpsbabel_format_option]\\*" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:99 +msgid "" +"When writing large datasets, the :config:`USE_TEMPFILE` configuration " +"option may be used:" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:113 +msgid "Reading the waypoints from a Garmin USB receiver :" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:119 +msgid "Converting a shapefile to Magellan Mapsend format :" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:128 +msgid "`GPSBabel Home Page <http://www.gpsbabel.org>`__" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:129 +msgid "`GPSBabel file formats <http://www.gpsbabel.org/capabilities.shtml>`__" +msgstr "" + +#: ../../source/drivers/vector/gpsbabel.rst:131 +msgid ":ref:`GPX driver page <vector.gpx>`" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:4 +msgid "GPX - GPS Exchange Format" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:6 +msgid "GPX" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:10 +msgid "" +"GPX (the GPS Exchange Format) is a light-weight XML data format for the " +"interchange of GPS data (waypoints, routes, and tracks) between " +"applications and Web services on the Internet." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:14 +msgid "" +"OGR has support for GPX reading (if GDAL is build with *expat* library " +"support) and writing." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:17 +msgid "Version supported are GPX 1.0 and 1.1 for reading, GPX 1.1 for writing." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:19 +msgid "The OGR driver supports reading and writing of all the GPX feature types:" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:21 +msgid "*waypoints* : layer of features of OGR type wkbPoint" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:22 +msgid "*routes* : layer of features of OGR type wkbLineString" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:23 +msgid "*tracks* : layer of features of OGR type wkbMultiLineString" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:25 +msgid "" +"It also supports reading of route points and track points in standalone " +"layers (*route_points* and *track_points*), so that their own attributes " +"can be used by OGR." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:31 +msgid "" +"In addition to its GPX attributes, each route point of a route has a " +"*route_fid* (foreign key to the FID of its belonging route) and a " +"*route_point_id* which is its sequence number in the route." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:34 +msgid "" +"The same applies for track points with *track_fid*, *track_seg_id* and " +"*track_seg_point_id*. All coordinates are relative to the WGS84 datum " +"(EPSG:4326)." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:36 +msgid "" +"The OGR GPX driver reads and writes the GPX attributes for the waypoints," +" routes and tracks." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:39 +msgid "" +"Starting with GDAL 3.7, metadata from the top <metadata> element is " +"reported at dataset level." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:67 +#: ../../source/drivers/vector/gpx.rst:102 +msgid "\"track_seg_id\" to \"trksegid\"" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:68 +#: ../../source/drivers/vector/gpx.rst:103 +msgid "\"track_seg_point_id\" to \"trksegptid\"" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:69 +#: ../../source/drivers/vector/gpx.rst:104 +msgid "\"route_point_id\" to \"rteptid\"" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:71 +#: ../../source/drivers/vector/gpx.rst:106 +msgid "" +"But note that no particular processing will be done for any extension " +"field names." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:140 +msgid "" +"If your GPX file is not encoded in one of the previous encodings, it will" +" not be parsed by the GPX driver. You may convert it into one of the " +"supported encoding with the *iconv* utility for example and change " +"accordingly the *encoding* parameter value in the XML header." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:142 +msgid "When writing a GPX file, the driver expects UTF-8 content to be passed in." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:146 +msgid "Extensions element reading" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:148 +msgid "" +"If the *<extensions>* element is detected in a GPX file, OGR will expose " +"the content of its sub elements as fields. Complex content of sub " +"elements will be exposed as an XML blob." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:152 +msgid "The following sequence GPX content :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:188 +msgid "" +"Note : the GPX driver will output content of the extensions element only " +"if it is found in the first records of the GPX file. If extensions appear" +" later, you can force an explicit parsing of the whole file with the " +":config:`GPX_USE_EXTENSIONS` configuration option." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:194 +msgid "" +"On export all layers are written to a single GPX file. Update of existing" +" files is not currently supported." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:202 +msgid "Features of type wkbPoint/wkbPoint25D are written in the *wpt* element." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:204 +msgid "" +"Features of type wkbLineString/wkbLineString25D are written in the *rte* " +"element." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:206 +msgid "" +"Features of type wkbMultiLineString/wkbMultiLineString25D are written in " +"the *trk* element." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:208 +msgid "Other type of geometries are not supported." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:210 +msgid "" +"For route points and tracks points, if there is a Z coordinate, it is " +"used to fill the elevation element of the corresponding points." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:213 +msgid "" +"If a layer is named \"track_points\" with wkbPoint/wkbPoint25D " +"geometries, the tracks in the GPX file will be built from the sequence of" +" features in that layer. This is the way of setting GPX attributes for " +"each track point, in addition to the raw coordinates. Points belonging to" +" the same track are identified thanks to the same value of the " +"'track_fid' field (and it will be broken into track segments according to" +" the value of the 'track_seg_id' field). They must be written in sequence" +" so that track objects are properly reconstructed. The 'track_name' field" +" can be set on the first track point to fill the <name> element of the " +"track. Similarly, if a layer is named \"route_points\" with " +"wkbPoint/wkbPoint25D geometries, the routes in the GPX file will be built" +" from the sequence of points with the same value of the 'route_fid' " +"field. The 'route_name' field can be set on the first track point to fill" +" the <name> element of the route." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:296 +msgid "" +"Dataset creation options to fill the top <metadata> element have been " +"added in GDAL 3.7:" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:339 +msgid "" +"Waypoints, routes and tracks must be written into that order to be valid " +"against the XML Schema." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:342 +msgid "" +"When translating from a source dataset, it may be necessary to rename the" +" field names from the source dataset to the expected GPX attribute names," +" such as <name>, <desc>, etc... This can be done with a :ref:`OGR VRT " +"<vector.vrt>` dataset, or by using the \"-sql\" option of the ogr2ogr " +"utility." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:349 +msgid "Issues when translating to Shapefile" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:351 +msgid "" +"When translating the *track_points* layer to a Shapefile, the field names" +" \"track_seg_id\" and \"track_seg_point_id\" are truncated to 10 " +"characters in the .DBF file, thus leading to duplicate names." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:355 +msgid "" +"To avoid this, you can define the :config:`GPX_SHORT_NAMES` configuration" +" option to TRUE." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:358 +msgid "To translate the track_points layer of a GPX file to a set of shapefiles :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:365 +msgid "" +"Shapefile does not support fields of type DateTime. It only supports " +"fields of type Date. So by default, you will lose the hour:minute:second " +"part of the *Time* elements of a GPX file." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:369 +msgid "" +"You can use the OGR SQL CAST operator to convert the *time* field to a " +"string :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:376 +msgid "" +"There is a more convenient way to select all fields and ask for the " +"conversion of the ones of a given type to strings:" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:397 +msgid "The ogrinfo utility can be used to dump the content of a GPX datafile :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:403 +msgid "The ogr2ogr utility can be used to do GPX to GPX translation :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:412 +msgid "" +"Note : in the case of GPX to GPX translation, you need to specify the " +"layer names, in order to discard the route_points and track_points " +"layers." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:416 +msgid "Use of the *<extensions>* tag for output :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:422 +msgid "which will give an output like the following one :" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:446 +msgid "" +"Use of -sql option to remap field names to the ones allowed by the GPX " +"schema:" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:454 +msgid "FAQ" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:456 +msgid "" +"How to solve \"ERROR 6: Cannot create GPX layer XXXXXX with unknown " +"geometry type\" ?" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:459 +msgid "" +"This error happens when the layer to create does not expose a precise " +"geometry type, but just a generic wkbUnknown type. This is for example " +"the case when using ogr2ogr with a SQL request to a PostgreSQL " +"datasource. You must then explicitly specify -nlt POINT (or LINESTRING or" +" MULTILINESTRING)." +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:468 +msgid "`Home page for GPX format <http://www.topografix.com/gpx.asp>`__" +msgstr "" + +#: ../../source/drivers/vector/gpx.rst:469 +msgid "`GPX 1.1 format documentation <http://www.topografix.com/GPX/1/1/>`__" +msgstr "" + +#: ../../source/drivers/vector/grass.rst:10 +msgid "" +"The GDAL-GRASS driver can read GRASS GIS vector maps. The driver is " +"maintained at the `GDAL-GRASS GIS driver repository " +"<https://github.com/OSGeo/gdal-grass/>`__." +msgstr "" + +#: ../../source/drivers/vector/grass.rst:13 +msgid "" +"For the driver documentation, please visit the `GDAL-GRASS GIS vector " +"driver page <https://github.com/OSGeo/gdal-" +"grass/blob/main/docs/grass_vector.md>`__." +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:4 +msgid "GTFS - General Transit Feed Specification" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:8 +msgid "GTFS" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:12 +msgid "" +"This driver can read a .zip archive containing text files following the " +"GTFS specification." +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:15 +msgid "The driver presents layers with their original structure, and:" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:17 +msgid "enhances the ``stops`` layer with Point geometries" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:18 +msgid "" +"enhances the ``trips`` layer with LineString geometries reconstructed by " +"joining the ``trips`` layer with ``stops`` and ``stop_times`` layers" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:20 +msgid "" +"expose a ``shapes_geom`` layer, if the optional ``shapes`` is present by " +"constructing LineString geometries." +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:26 +msgid "The connection name can be:" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:28 +msgid "a .zip filename containing GTFS .txt files" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:29 +msgid "" +"a directory name prefixed with ``GTFS:`` (potentially a " +"``/vsizip/path/to/the.zip`` filename prefixed with ``GTFS:``)" +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:32 +msgid "" +"Alternatively, starting with GDAL 3.10, specifying the ``-if GTFS`` " +"option to command line utilities accepting it, or ``GTFS`` as the only " +"value of the ``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also " +"forces the driver to recognize the passed filename." +msgstr "" + +#: ../../source/drivers/vector/gtfs.rst:46 +msgid "`GTFS Wikipedia page <https://en.wikipedia.org/wiki/GTFS>`__" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:6 +msgid "HANA" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:10 +msgid "" +"This driver implements read and write access for spatial data stored in " +"an `SAP HANA <https://www.sap.com/products/hana.html>`__ database." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:25 +msgid "" +"To connect to an SAP HANA database, use a connection string specifying " +"the database name, with additional parameters as necessary. The HANA: " +"prefix is used to mark the name as a HANA connection string." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:31 +#: ../../source/drivers/vector/pg.rst:49 +msgid "" +"In this syntax each parameter setting is in the form keyword = value. " +"Spaces around the equal sign are optional. To write an empty value, or a " +"value containing spaces, surround it with single quotes, e.g., keyword = " +"'a value'. Single quotes and backslashes within the value must be escaped" +" with a backslash, i.e., \\' and \\\\." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:39 +#: ../../source/drivers/vector/mssqlspatial.rst:83 +#: ../../source/drivers/vector/pg.rst:93 +msgid "SQL statements" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:41 +msgid "" +"The HANA driver passes SQL statements directly to HANA by default, rather" +" than evaluating them internally when using the ExecuteSQL() call on the " +"OGRDataSource, or the -sql command option to ogr2ogr. Attribute query " +"expressions are also passed directly through to HANA. It's also possible " +"to request the OGR HANA driver to handle SQL commands with the :ref:`OGR " +"SQL <ogr_sql_dialect>` engine, by passing **\"OGRSQL\"** string to the " +"ExecuteSQL() method, as the name of the SQL dialect." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:50 +msgid "" +"The HANA driver in OGR supports the OGRDataSource::StartTransaction(), " +"OGRDataSource::CommitTransaction() and " +"OGRDataSource::RollbackTransaction() calls in the normal SQL sense." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:57 +msgid "" +"The HANA driver does not support creation of new schemas, but it does " +"allow creation of new layers (tables) within an existing schema." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:61 +msgid "Dataset Open options" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:257 +msgid "Multitenant Database Containers" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:259 +msgid "" +"In order to connect to a tenant database, you need to specify a port " +"number assigned exactly to a desired instance. This port number can be " +"determined by executing the following query from the tenant database." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:267 +msgid "" +"For more details, see **Section 2.9 Connections for Multitenant Database " +"Containers** in `SAP HANA Multitenant Database Containers " +"<https://help.sap.com/doc/0987e3b51fb74e5a8631385fe4599c97/2.0.00/en-" +"us/sap_hana_multitenant_database_containers_en.pdf>`__." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:274 +msgid "" +"This example shows how to list HANA layers on a specified host using " +":ref:`ogrinfo` command." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:293 +msgid "" +"This example shows how to print summary information about a given layer, " +"i.e. 'planet_osm_line', using :ref:`ogrinfo`." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:332 +msgid "" +"This example shows how to export data from the 'points' table to a " +"shapefile called 'points_output.shp'." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:338 +msgid "" +"This example shows how to create and populate a table with data taken " +"from a shapefile." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:346 +msgid "For developers" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:348 +msgid "" +"To compile the SAP HANA driver, `odbc-cpp-wrapper <https://github.com/SAP" +"/odbc-cpp-wrapper/>`__ library needs to be linked or installed. For more " +"details, see comments in nmake.opt or configure.ac files to build the " +"driver for Windows or Linux/MacOS correspondingly." +msgstr "" + +#: ../../source/drivers/vector/hana.rst:354 +msgid "`SAP HANA Home Page <https://www.sap.com/products/hana.html>`__" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:355 +msgid "" +"`SAP HANA Spatial Reference " +"<https://help.sap.com/viewer/cbbbfc20871e4559abfd45a78ad58c02/2.0.03/en-" +"US/e1c934157bd14021a3b43b5822b2cbe9.html>`__" +msgstr "" + +#: ../../source/drivers/vector/hana.rst:356 +msgid "" +"`SAP HANA ODBC Connection Properties " +"<https://help.sap.com/viewer/0eec0d68141541d1b07893a39944924e/2.0.02/en-" +"US/7cab593774474f2f8db335710b2f5c50.html>`__" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:10 +msgid "" +"This driver implements support for access to spatial tables in IBM " +"Informix extended with the DataBlade spatial module." +msgstr "" + +#: ../../source/drivers/vector/idb.rst:13 +msgid "When opening a database, its name should be specified in the form" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:19 +msgid "The IDB: prefix is used to mark the name as a IDB connection string." +msgstr "" + +#: ../../source/drivers/vector/idb.rst:21 +msgid "" +"If the *geometry_columns* table exists, then all listed tables and named " +"views will be treated as OGR layers. Otherwise all regular user tables " +"will be treated as layers." +msgstr "" + +#: ../../source/drivers/vector/idb.rst:25 +msgid "" +"Regular (non-spatial) tables can be accessed, and will return features " +"with attributes, but not geometry. If the table has a \"st_*\" field, it " +"will be treated as a spatial table. The type of the field is inspected to" +" determine how to read it." +msgstr "" + +#: ../../source/drivers/vector/idb.rst:30 +msgid "Driver supports automatic FID detection." +msgstr "" + +#: ../../source/drivers/vector/idb.rst:42 +#: ../../source/drivers/vector/pgdump.rst:248 +msgid "Environment variables" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:44 +msgid "``INFORMIXDIR`` It should be set to Informix client SDK install dir" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:46 +msgid "``INFORMIXSERVER``: Default Informix server name" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:48 +msgid "``DB_LOCALE``: Locale of Informix database" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:50 +msgid "``CLIENT_LOCALE``: Client locale" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:52 +msgid "" +"For more information about Informix variables read documentation of " +"Informix Client SDK" +msgstr "" + +#: ../../source/drivers/vector/idb.rst:69 +msgid "" +"This example shows using ogrinfo to list Informix DataBlade layers on a " +"different host." +msgstr "" + +#: ../../source/drivers/vector/idrisi.rst:6 +msgid "IDRISI" +msgstr "" + +#: ../../source/drivers/vector/idrisi.rst:10 +msgid "" +"This driver reads Idrisi vector files with .vct extension. The driver " +"recognized point, lines and polygons geometries." +msgstr "" + +#: ../../source/drivers/vector/idrisi.rst:13 +msgid "" +"For geographical referencing identification, the .vdc file contains " +"information that points to a file that holds the geographic reference " +"details. Those files uses extension REF and resides in the same folder as" +" the RST image or more likely in the Idrisi installation folders." +msgstr "" + +#: ../../source/drivers/vector/idrisi.rst:24 +msgid "" +"Note that the driver recognizes the name convention used in Idrisi for " +"UTM and State Plane geographic reference so it doesn't need to access the" +" REF files. That is the case for RDC file that specify \"utm-30n\" or " +"\"spc87ma1\" in the \"ref. system\" field. Note that exporting to RST in " +"any other geographical reference system will generate a suggested REF " +"content in the comment section of the RDC file." +msgstr "" + +#: ../../source/drivers/vector/idrisi.rst:31 +msgid "The driver can retrieve attributes from .ADC / .AVL ASCII files." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:6 +msgid "INTERLIS 1" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:8 +msgid "INTERLIS 2" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:12 +msgid "OGR has support for INTERLIS reading and writing." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:17 +msgid "" +"`INTERLIS <http://www.interlis.ch/>`__ is a standard which has been " +"especially composed in order to fulfill the requirements of modeling and " +"the integration of geodata into contemporary and future geographic " +"information systems. With the usage of unified, documented geodata and " +"the flexible exchange possibilities the following advantage may occur:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:19 +msgid "the standardized documentation" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:20 +msgid "the compatible data exchange" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:21 +msgid "the comprehensive integration of geodata e.g. from different data owners." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:23 +msgid "the quality proofing" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:24 +msgid "the long term data storage" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:25 +msgid "the contract-proof security and the availability of the software" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:27 +msgid "" +"OGR supports INTERLIS 1 and INTERLIS 2 (2.2 and 2.3) with the following " +"limitations:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:30 +msgid "Curves in Interlis 1 area polygons are converted to line segments" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:31 +msgid "" +"Interlis 1 Surface geometries with non-numeric IDENT field are not " +"included in the attribute layer" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:33 +msgid "Embedded INTERLIS 2 structures and line attributes are not supported" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:34 +msgid "Incremental transfer is not supported" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:35 +msgid "Transfer id (TID) is used as feature id" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:47 +msgid "Model support" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:49 +msgid "" +"Data is read and written into transfer files which have different formats" +" in INTERLIS 1 (.itf) and INTERLIS 2 (.xtf). Models are passed in " +"IlisMeta format by using \"a_filename.xtf,models.imd\" as a connection " +"string." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:54 +msgid "" +"IlisMeta files can be be generated with the ili2c compiler. Command line " +"example:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:61 +msgid "Some possible transformations using :ref:`ogr2ogr`." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:63 +msgid "Interlis 1 -> Shape:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:69 +msgid "Interlis 2 -> Shape:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:75 +msgid "or without model:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:81 +msgid "Example with curves and multiple geometries:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:87 +msgid "Shape -> Interlis 2:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:93 +msgid "Importing multiple Interlis 1 files into PostGIS:" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:101 +msgid "Arc interpolation" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:104 +msgid "" +"Converting INTERLIS arc geometries to line segments can be forced by " +"setting the configuration variable :config:`OGR_STROKE_CURVE` to TRUE." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:108 +msgid "" +"The approximation of arcs as linestrings is done by splitting the arcs " +"into subarcs of no more than a threshold angle. This angle is the " +":config:`OGR_ARC_STEPSIZE`. This defaults to one degree, but may be " +"overridden by setting the configuration variable " +":config:`OGR_ARC_STEPSIZE`." +msgstr "" + +#: ../../source/drivers/vector/ili.rst:113 +msgid "" +"`ogrtools <https://github.com/sourcepole/ogrtools>`__ library includes " +"extensions for the OGR Interlis driver" +msgstr "" + +#: ../../source/drivers/vector/ili.rst:115 +msgid "" +"Development of the OGR INTERLIS driver was supported by `Swiss Federal " +"Administration <http://www.kogis.ch/>`__, `Canton Solothurn " +"<http://www.sogis.ch/>`__ and `Canton Thurgovia " +"<http://www.geoinformation.tg.ch/>`__." +msgstr "" + +#: ../../source/drivers/vector/index.rst:5 +msgid "Vector drivers" +msgstr "" + +#: ../../source/drivers/vector/index.rst:18 +msgid "" +"The following drivers have been retired and moved to the " +"https://github.com/OSGeo/gdal-extra-drivers repository: AeronavFAA, BNA, " +"HTF, OpenAir, SEGUKOOA, SEGY, SUA, XPlane" +msgstr "" + +#: ../../source/drivers/vector/jml.rst:6 +msgid "JML" +msgstr "" + +#: ../../source/drivers/vector/jml.rst:10 +msgid "" +"OGR has support for reading and writing .JML files used by the OpenJUMP " +"software. Read support is only available if GDAL is built with *expat* " +"library support" +msgstr "" + +#: ../../source/drivers/vector/jml.rst:14 +msgid "" +".jml is a variant of GML format. There is no formal definition of the " +"format. It supports a single layer per file, mixed geometry types, and " +"for each feature, a geometry and several attributes of type integer, " +"double, string, date or object. That object data type, used for example " +"to store 64 bit integers, but potentially arbitrary serialized Java " +"objects, is converted as string when reading. Contrary to GML, the " +"definition of fields is embedded in the .jml file, at its beginning." +msgstr "" + +#: ../../source/drivers/vector/jml.rst:22 +msgid "" +"Support for reading and writing spatial reference systems requires GDAL " +"2.3 or later." +msgstr "" + +#: ../../source/drivers/vector/jml.rst:45 +msgid "" +"The content returned by OGR will be encoded in UTF-8, after the " +"conversion from the encoding mentioned in the file header is. But files " +"produced by OpenJUMP are always UTF-8 encoded." +msgstr "" + +#: ../../source/drivers/vector/jml.rst:49 +msgid "When writing a JML file, the driver expects UTF-8 content to be passed in." +msgstr "" + +#: ../../source/drivers/vector/jml.rst:53 +msgid "Styling" +msgstr "" + +#: ../../source/drivers/vector/jml.rst:55 +msgid "" +"OpenJUMP uses an optional string attribute called \"R_G_B\" to determine " +"the color of objects. The field value is \"RRGGBB\" where RR, GG, BB are " +"respectively the value of the red, green and blue components expressed as" +" hexadecimal values from 00 to FF. When reading a .jml file, OGR will " +"translate the R_G_B attribute to the Feature Style encoding, unless a " +"OGR_STYLE attribute is present. When writing a .jml file, OGR will " +"extract from the Feature Style string the color of the PEN tool or the " +"forecolor of the BRUSH tool to write the R_G_B attribute, unless the " +"R_G_B attribute is defined in the provided feature. The addition of the " +"R_G_B attribute can be disabled by setting the CREATE_R_G_B_FIELD layer " +"creation option to NO." +msgstr "" + +#: ../../source/drivers/vector/jml.rst:70 +msgid "" +"|about-layer-creation-options| The JML writer supports the following " +"*layer* creation options:" +msgstr "" + +#: ../../source/drivers/vector/jml.rst:96 +msgid "" +"The author wishes to thank Jukka Rahkonen for funding the development of " +"this driver." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:4 +msgid "JSONFG -- OGC Features and Geometries JSON" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:8 +msgid "JSONFG" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:12 +msgid "" +"This driver implements read/write support for access to features encoded " +"in `OGC Features and Geometries JSON - Part 1: Core " +"<https://docs.ogc.org/DRAFTS/21-045.html>`__ format." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:15 +msgid "" +"JSON-FG is a set of extensions over the :ref:`GeoJSON<vector.geojson>` " +"format." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:17 +msgid "The following extensions are supported:" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:19 +msgid "" +"capturing the feature type in a ``featureType`` element to affect " +"features to separate" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:21 +msgid "" +"capturing a coordinate reference system (not necessarily WGS 84) in a " +"``coordRefSys`` element, that is the one used by geometries written in " +"the ``place`` element" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:24 +msgid "``time`` element at Feature level" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:25 +msgid "" +"minimum support for Polyhedron geometries (with a single outer shell) and" +" Prism with Point, LineString or Polygon base." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:30 +msgid "This driver implements a draft version of the standard." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:44 +msgid "The JSON-FG driver accepts three types of sources of data:" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:49 +msgid "Plain text file with JSON-FG data, typically with a .json extension" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:50 +msgid "Text passed directly and encoded in JSON-FG" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:52 +msgid "" +"The URL/filename/text might be prefixed with ``JSONFG:`` to avoid any " +"ambiguity with other drivers. Alternatively, starting with GDAL 3.10, " +"specifying the ``-if JSONFG`` option to command line utilities accepting " +"it, or ``JSONFG`` as the only value of the ``papszAllowedDrivers`` of " +":cpp:func:`GDALOpenEx`, also forces the driver to recognize the passed " +"URL/filename/text." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:60 +msgid "Time support" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:62 +msgid "On reading:" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:64 +msgid "" +"Feature.time.date elements are mapped to a OGR ``time`` field of type " +"Date. If there is a property also called ``time``, the OGR field for " +"Feature.time is called ``jsonfg_time``" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:68 +msgid "" +"Feature.time.timestamp elements are mapped to a OGR ``time`` field of " +"type DateTime" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:71 +msgid "" +"Feature.time.interval elements are mapped to a OGR ``time_start`` and " +"``time_end`` fields of type Date or DateTime. If there are properties " +"with those names, the OGR fields for Feature.time are prefixed with " +"``jsonfg_`` Unbounded intervals (``..``) are mapped to a unset OGR " +"feature field." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:76 +msgid "" +"On writing, if fields called ``time``, ``time_start``, ``time_end`` of " +"type Date or DateTime are created, their content is used to set the " +"Feature.time element with the reverse logic as the above explained " +"reading side. The field names may also be prefixed with ``jsonfg_`` to " +"distinguish them from fields ``time``, ``time_start``, ``time_end`` that " +"must be written in Feature.properties" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:207 +msgid "" +"The :lco:`COORDINATE_PRECISION_GEOMETRY` or " +":lco:`COORDINATE_PRECISION_PLACE` layer creation option has precedence " +"over the values set on the :cpp:class:`OGRGeomFieldDefn`." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:210 +msgid "" +"Implementation details: the coordinate precision is stored as " +"``xy_coordinate_resolution_place`` and ``z_coordinate_resolution_place`` " +"members at the FeatureCollection level, for the geometries written in the" +" ``place`` element. Their numeric value is expressed in the units of the " +"SRS." +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:215 +msgid "" +"For the ``geometry`` standard GeoJSON element, the coordinate precision " +"is stored as ``xy_coordinate_resolution`` and ``z_coordinate_resolution``" +" members, and their numeric value is expressed in the units of the " +"OGC:CRS84 SRS (hence decimal degrees for ``xy_coordinate_resolution``)" +msgstr "" + +#: ../../source/drivers/vector/jsonfg.rst:236 +msgid "" +"`OGC Features and Geometries JSON - Part 1: Core " +"<https://docs.ogc.org/DRAFTS/21-045.html>`__" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:4 +msgid "KML - Keyhole Markup Language" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:6 +msgid "KML" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:10 +msgid "" +"Keyhole Markup Language (KML) is an XML-based language for managing the " +"display of 3D geospatial data. KML has been accepted as an OGC standard, " +"and is supported in one way or another on the major GeoBrowsers. Note " +"that KML by specification uses only a single projection, EPSG:4326. All " +"OGR KML output will be presented in EPSG:4326. As such OGR will create " +"layers in the correct coordinate system and transform any geometries." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:17 +msgid "" +"At this time, only vector layers are handled by the KML driver. *(there " +"are additional scripts supplied with the GDAL project that can build " +"other kinds of output)*" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:31 +msgid "KML Reading" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:33 +msgid "" +"KML reading is only available if GDAL/OGR is built with the Expat XML " +"Parser, otherwise only KML writing will be supported." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:36 +msgid "" +"Supported geometry types are ``Point``, ``Linestring``, ``Polygon``, " +"``MultiPoint``, ``MultiLineString``, ``MultiPolygon`` and " +"``MultiGeometry``. There are limitations, for example: the nested nature " +"of folders in a source KML file is lost; folder ``<description>`` tags " +"will not carry through to output. Folders containing multiple geometry " +"types, like POINT and POLYGON, are supported." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:44 +msgid "KML Writing" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:46 +msgid "" +"Since not all features of KML are able to be represented in the Simple " +"Features geometry model, you will not be able to generate many KML-" +"specific attributes from within GDAL/OGR. Please try a few test files to " +"get a sense of what is possible." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:51 +msgid "" +"When outputting KML, the OGR KML driver will translate each OGR Layer " +"into a KML Folder (you may encounter unexpected behavior if you try to " +"mix the geometry types of elements in a layer, e.g. ``LINESTRING`` and " +"``POINT`` data)." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:56 +msgid "" +"The KML Driver will rename some layers, or source KML folder names, into " +"new names it considers valid, for example '``Layer #0``', the default " +"name of the first unnamed Layer, becomes ``'Layer__0'``." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:60 +msgid "" +"KML is mix of formatting and feature data. The <description> tag of a " +"Placemark will be displayed in most geobrowsers as an HTML-filled " +"balloon. When writing KML, Layer element attributes are added as simple " +"schema fields. This best preserves feature type information." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:65 +msgid "" +"Limited support is available for fills, line color and other styling " +"attributes. Please try a few sample files to get a better sense of actual" +" behavior." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:86 +msgid "" +"If your KML file is not encoded in one of the previous encodings, it will" +" not be parsed by the KML driver. You may convert it into one of the " +"supported encoding with the *iconv* utility for example and change " +"accordingly the *encoding* parameter value in the XML header." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:88 +msgid "When writing a KML file, the driver expects UTF-8 content to be passed in." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:140 +msgid "" +"The ogr2ogr utility can be used to dump the results of a PostGIS query to" +" KML:" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:147 +msgid "How to dump contents of .kml file as OGR sees it:" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:154 +#: ../../source/drivers/vector/mysql.rst:44 +#: ../../source/drivers/vector/oci.rst:73 +msgid "Caveats" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:156 +msgid "" +"Google Earth seems to have some limits regarding the number of " +"coordinates in complex geometries like polygons. If the problem appears, " +"then problematic geometries are displayed completely or partially covered" +" by vertical stripes. Unfortunately, there are no exact number given in " +"the KML specification about this limitation, so the KML driver will not " +"warn about potential problems. One of possible and tested solutions is to" +" simplify a line or a polygon to remove some coordinates. Here is the " +"whole discussion about this issue on the `Google KML Developer Forum " +"<http://groups.google.com/group/kml-support>`__, in the `polygon displays" +" with vertical stripes <http://groups.google.com/group/kml-support-" +"getting-started/browse_thread/thread/e6995b8073e69c41>`__ thread." +msgstr "" + +#: ../../source/drivers/vector/kml.rst:172 +msgid "`KML Specification <https://developers.google.com/kml/?csw=1>`__" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:173 +msgid "`KML Tutorial <https://developers.google.com/kml/documentation/kml_tut>`__" +msgstr "" + +#: ../../source/drivers/vector/kml.rst:175 +msgid ":ref:`LIBKML driver <vector.libkml>` An alternative GDAL KML driver" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:6 +msgid "LIBKML" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:10 +msgid "" +"The LIBKML driver is a client of `Libkml " +"<https://github.com/libkml/libkml>`__ , a reference implementation of " +"`KML <http://www.opengeospatial.org/standards/kml/>`__ reading and " +"writing, in the form of a cross platform C++ library. You must build and " +"install Libkml in order to use this OGR driver. Note: you need to build " +"libkml 1.3 or master." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:17 +msgid "" +"Note that if you build and include this LIBKML driver, it will become the" +" default reader of KML for ogr, overriding the previous :ref:`KML driver " +"<vector.kml>`. You can still specify either KML or LIBKML as the output " +"driver via the command line" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:22 +msgid "" +"Libkml from Google provides reading services for any valid KML file. " +"However, please be advised that some KML facilities do not map into the " +"Simple Features specification OGR uses as its internal structure. " +"Therefore, a best effort will be made by the driver to understand the " +"content of a KML file read by libkml into ogr, but your mileage may vary." +" Please try a few KML files as samples to get a sense of what is " +"understood. In particular, nesting of feature sets more than one deep " +"will be flattened to support ogr's internal format." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:43 +msgid "" +"You may specify a datasource as a kml file ``somefile.kml`` , a directory" +" ``somedir/`` , or a kmz file ``somefile.kmz`` ." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:47 +msgid "" +"By default on directory and kmz datasources, an index file of all the " +"layers will be read from or written to doc.kml. It contains a " +"`<NetworkLink> " +"<https://developers.google.com/kml/documentation/kmlreference#networklink>`__" +" to each layer file in the datasource. This feature can be turned off by " +"setting the configuration option :config:`LIBKML_USE_DOC.KML` to \"NO\":" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:62 +msgid "StyleTable" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:64 +msgid "" +"Datasource style tables are written to the `<Document> " +"<https://developers.google.com/kml/documentation/kmlreference#document>`__" +" in a .kml, style/style.kml in a kmz file, or style.kml in a directory, " +"as one or more `<Style> " +"<https://developers.google.com/kml/documentation/kmlreference#style>`__ " +"elements. Not all of :ref:`ogr_feature_style` can translate into KML." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:75 +msgid "" +"|about-dataset-creation-options| The following dataset creation options " +"can be used to generate a `<atom:Author> " +"<https://developers.google.com/kml/documentation/kmlreference#atomauthor>`__" +" element at the top Document level." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:95 +msgid "Additional dataset creation options affecting the top Document level:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:117 +msgid "Container properties" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:119 +msgid "" +"The following dataset creation options can be used to set container " +"options :" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:148 +msgid "List style" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:150 +msgid "" +"The following dataset creation options can be used to control how the " +"main folder (folder of layers) appear in the Places panel of the Earth " +"browser, trough a `<ListStyle> " +"<https://developers.google.com/kml/documentation/kmlreference#liststyle>`__" +" element:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:171 +msgid "Balloon style" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:173 +msgid "" +"If a style *foo* is defined, it is possible to add a `<BalloonStyle> " +"<https://developers.google.com/kml/documentation/kmlreference#balloonstyle>`__" +" element to it, by specifying the **foo_BALLOONSTYLE_BGCOLOR** and/or " +"**foo_BALLOONSTYLE_TEXT** elements." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:179 +msgid "NetworkLinkControl" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:181 +msgid "" +"A `<NetworkLinkControl> " +"<https://developers.google.com/kml/documentation/kmlreference#networklinkcontrol>`__" +" element can be defined if at least one of the following dataset creation" +" option is specified:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:235 +msgid "Update documents" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:237 +msgid "" +"When defining the dataset creation option **UPDATE_TARGETHREF**, a " +"NetworkLinkControl KML file with an `<Update> " +"<https://developers.google.com/kml/documentation/kmlreference#update>`__ " +"element will be generated. See the `tutorial about update " +"<https://developers.google.com/kml/documentation/updates>`__." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:243 +msgid "" +"The CreateFeature() operation on a layer will be translated as a " +"`<Create> " +"<https://developers.google.com/kml/documentation/kmlreference#create>`__ " +"element." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:247 +msgid "" +"The SetFeature() operation on a layer will be translated as a `<Change> " +"<https://developers.google.com/kml/documentation/kmlreference#change>`__ " +"element." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:251 +msgid "" +"The DeleteFeature() operation on a layer will be translated as a " +"`<Delete> " +"<https://developers.google.com/kml/documentation/kmlreference#delete>`__ " +"element." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:258 +msgid "" +":cpp:class:`OGRLayer` are mapped to kml files as a `<Document> " +"<https://developers.google.com/kml/documentation/kmlreference#document>`__" +" or `<Folder> " +"<https://developers.google.com/kml/documentation/kmlreference#folder>`__," +" and in kmz files or directories as a separate kml file." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:266 +#: ../../source/drivers/vector/libkml.rst:519 +msgid "Style" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:268 +msgid "" +"Layer style tables can not be read from or written to a kml layer that is" +" a `<Folder> " +"<https://developers.google.com/kml/documentation/kmlreference#folder>`__," +" otherwise they are in the `<Document> " +"<https://developers.google.com/kml/documentation/kmlreference#document>`__" +" that is the layer." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:278 +msgid "" +"Read and write of `<Schema> " +"<https://developers.google.com/kml/documentation/kmlreference#schema>`__ " +"is supported for .kml files, .kmz files, and directories." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:285 +msgid "" +"|about-layer-creation-options| The following layer creation options can " +"be used to generate a `<LookAt> " +"<https://developers.google.com/kml/documentation/kmlreference#lookat>`__ " +"element at the layer level." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:305 +msgid "" +"Alternatively, a `<Camera> " +"<https://developers.google.com/kml/documentation/kmlreference#camera>`__ " +"element can be generated." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:325 +msgid "" +"A `<Region> " +"<https://developers.google.com/kml/documentation/kmlreference#region>`__ " +"element can be generated to control when objects of the layer are visible" +" or not. If :lco:`REGION_XMIN`, :lco:`REGION_YMIN`, :lco:`REGION_XMAX` " +"and :lco:`REGION_YMAX`, the region coordinates are determined from the " +"spatial extent of the features being written in the layer." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:376 +msgid "" +"A `<ScreenOverlay> " +"<https://developers.google.com/kml/documentation/kmlreference#screenoverlay>`__" +" element can be added to display a logo, a legend, etc..." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:405 +msgid "" +"The following option controls whether layers are written as a Document or" +" a Folder:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:417 +msgid "" +"The following layer creation options can be used to set container options" +" :" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:445 +msgid "Do not confuse them with the same named dataset creation options." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:447 +msgid "" +"The following layer creation options can be used to control how the " +"folder of a layer appear in the Places panel of the Earth browser, trough" +" a `<ListStyle> " +"<https://developers.google.com/kml/documentation/kmlreference#liststyle>`__" +" element:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:470 +msgid "" +"An :cpp:class:`OGRFeature` generally translates to kml as a `<Placemark> " +"<https://developers.google.com/kml/documentation/kmlreference#placemark>`__," +" and vice-versa." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:475 +msgid "" +"If the model field is defined, a `<Model> " +"<https://developers.google.com/kml/documentation/kmlreference#model>`__ " +"object within the Placemark will be generated." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:479 +msgid "" +"If the networklink field is defined, a `<NetworkLink> " +"<https://developers.google.com/kml/documentation/kmlreference#networklink>`__" +" will be generated. Other networklink fields are optional." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:483 +msgid "" +"If the photooverlay field is defined, a `<PhotoOverlay> " +"<https://developers.google.com/kml/documentation/kmlreference#photooverlay>`__" +" will be generated (provided that the camera_longitude, camera_latitude, " +"camera_altitude, camera_altitudemode, head and/or tilt and/or roll, " +"leftfov, rightfov, bottomfov, topfov, near fields are also set. The shape" +" field is optional." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:490 +msgid "" +"In case the PhotoOverlay is a big image, it is highly recommended to tile" +" it and generate overview levels, as explained in the `PhotoOverlay " +"tutorial <https://developers.google.com/kml/documentation/photos>`__. In " +"which case, the URL should contain the \"$[level]\", \"$[x]\" and " +"\"$[y]\" sub-strings in the photooverlay field, and the " +"imagepyramid_tilesize, imagepyramid_maxwidth, imagepyramid_maxheight and " +"imagepyramid_gridorigin fields should be set." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:498 +msgid "" +"Placemark, Model, NetworkLink and PhotoOverlay objects can have an " +"associated camera if the camera_longitude, camera_latitude, " +"camera_altitude, camera_altitudemode, head and/or tilt and/or roll fields" +" are defined." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:503 +msgid "" +"KML `<GroundOverlay> " +"<https://developers.google.com/kml/documentation/kmlreference#groundoverlay>`__" +" elements are supported for reading (unless the " +":config:`LIBKML_READ_GROUND_OVERLAY` configuration option is set to " +"FALSE). For such elements, there are icon and drawOrder fields." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:508 +msgid "The following configuration options affect reading of features:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:521 +msgid "" +"Style Strings at the feature level are Mapped to KML as either a `<Style>" +" <https://developers.google.com/kml/documentation/kmlreference#style>`__ " +"or `<StyleUrl> " +"<https://developers.google.com/kml/documentation/kmlreference#styleurl>`__" +" in each `<Placemark> " +"<https://developers.google.com/kml/documentation/kmlreference#placemark>`__." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:528 +msgid "The following configuration options affect handling of styles:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:556 +msgid "" +"When writing a kml, if there exist 2 styles of the form " +"\"astylename_normal\" and \"astylename_highlight\" (where astylename is " +"any string), then a StyleMap object will be creating from both styles and" +" called \"astylename\"." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:562 +msgid "Fields" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:564 +msgid "" +"OGR fields (feature attributes) are mapped to kml with `<Schema> " +"<https://developers.google.com/kml/documentation/kmlreference#schema>`__;" +" and `<SimpleData> " +"<https://developers.google.com/kml/documentation/kmlreference#simpledata>`__," +" except for some special fields as noted below." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:572 +msgid "" +"It is also possible to export fields as `<Data> " +"<https://developers.google.com/kml/documentation/kmlreference#data>`__ " +"elements using the following configuration option:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:581 +msgid "" +"A rich set of :ref:`configuration options <configoptions>` are available " +"to define how fields in input and output, map to a KML `<Placemark> " +"<https://developers.google.com/kml/documentation/kmlreference#placemark>`__." +" For example, if you want a field called 'Cities' to map to the `<name> " +"<https://developers.google.com/kml/documentation/kmlreference#name>`__; " +"tag in KML, you can set a configuration option. Note these are " +"independent of layer creation and dataset creation options' `<name>`." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:912 +msgid "" +"Translation of :cpp:class:`OGRGeometry` to KML Geometry is pretty " +"straightforward with only a couple of exceptions. Point to `<Point> " +"<https://developers.google.com/kml/documentation/kmlreference#point>`__ " +"(unless heading and/or tilt and/or roll field names are found, in which " +"case a `Camera " +"<https://developers.google.com/kml/documentation/kmlreference#camera>`__ " +"object will be generated), LineString to `<LineString> " +"<https://developers.google.com/kml/documentation/kmlreference#linestring>`__," +" LinearRing to `<LinearRing> " +"<https://developers.google.com/kml/documentation/kmlreference#linearring>`__," +" and Polygon to `<Polygon> " +"<https://developers.google.com/kml/documentation/kmlreference#polygon>`__." +" In OGR a polygon contains an array of LinearRings, the first one being " +"the outer ring. KML has the tags `<outerBoundaryIs> " +"<https://developers.google.com/kml/documentation/kmlreference#outerboundaryis>`__" +" and `<innerBoundaryIs> " +"<https://developers.google.com/kml/documentation/kmlreference#innerboundaryis>`__" +" to differentiate between the two. OGR has several Multi types of " +"geometry : GeometryCollection, MultiPolygon, MultiPoint, and " +"MultiLineString. When possible, OGR will try to map `<MultiGeometry> " +"<https://developers.google.com/kml/documentation/kmlreference#multigeometry>`__" +" to the more precise OGR geometry type (MultiPoint, MultiLineString or " +"MultiPolygon), and default to GeometryCollection in case of mixed " +"content." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:937 +msgid "The following configuration options control geometry translation:" +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:961 +msgid "" +"The following bash script will build a :ref:`csv <vector.csv>` file and a" +" :ref:`vrt <vector.vrt>` file, and then translate them to KML using " +":ref:`ogr2ogr` into a .kml file with timestamps and styling." +msgstr "" + +#: ../../source/drivers/vector/libkml.rst:1069 +msgid "" +"The following example shows how the three levels of `<name>` in LIBKML " +"relate to their controlling options:" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:9 +msgid "LVBAG" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:13 +msgid "" +"This driver can read XML files in the LV BAG 2.0 extract format as " +"provided by the Dutch Kadaster BAG products. All LV BAG 2.0 extract " +"products are supported. The driver supports all BAG layers including " +"those introduced in BAG 2.0." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:17 +#: ../../source/drivers/vector/ods.rst:14 +#: ../../source/drivers/vector/xlsx.rst:16 +msgid "" +"The driver is only available if GDAL/OGR is compiled against the Expat " +"library." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:20 +msgid "" +"Each extract XML file is presented as a single OGR layer. The layers are " +"georeferenced in their native (EPSG:28992) SRS." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:23 +msgid "" +"More information about the LV BAG 2.0 can be found at " +"https://www.kadaster.nl/zakelijk/producten/adressen-en-" +"gebouwen/bag-2.0-extract" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:25 +msgid "" +"LV BAG model definitions are available at " +"https://developer.kadaster.nl/schemas/-/categories/4119958" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:27 +msgid "" +"Note 1 : The earlier BAG 1.0 extract is **not supported**\\ by this " +"driver." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:29 +msgid "" +"Note 2 : The driver will only read ST (Standaard Levering) extract files." +" Mutation ML (Mutatie Levering) files are not supported." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:35 +msgid "" +"The following open options can be specified (typically with the **-oo**\\" +" name=value parameters of ogrinfo or ogr2ogr):" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:55 +msgid "" +"The driver supports reading from files managed by VSI Virtual File System" +" API, which include \"regular\" files, as well as files in the /vsizip/ " +"domain. See examples below." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:67 +msgid "" +"The ogr2ogr utility can be used to dump the results of a LV BAG extract " +"to WGS84 in GeoJSON:" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:74 +msgid "How to dump contents of extract file as OGR sees it:" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:80 +msgid "" +"Insert repaired features from LV BAG extract archive into PostgreSQL as " +"WGS84 geometries. The table 'pand' will be created with the features from" +" 9999PND18122019.zip. The database instance (lvbag) must already exist, " +"and the table 'pand' must not already exist." +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:88 +msgid "Load a LV BAG extract directory into Postgres:" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:97 +msgid "Create GeoPackage from 'Nummeraanduiding' dataset:" +msgstr "" + +#: ../../source/drivers/vector/lvbag.rst:108 +msgid "" +"`Kadaster LV BAG 2.0 page (Dutch) " +"<https://www.kadaster.nl/zakelijk/producten/adressen-en-" +"gebouwen/bag-2.0-extract>`__" +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:12 +msgid "" +"This driver implements read and write support for the `MapML " +"specification <https://maps4html.org/MapML/spec>`_. It only implements " +"reading and writing vector features." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:18 +msgid "" +"This driver implements an experimental specification, and inherits its " +"experimental status. This specification may change at a later point, or " +"not be adopted. Files written by this driver may no longer be readable in" +" later versions of GDAL." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:36 +msgid "Layers are identified with the ``class`` attribute of features." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:38 +msgid "" +"Fields are retrieved from the HTML table in the ``properties`` element of" +" features. This assumes that they are written following the exact same " +"structure as the write side of the driver. Otherwise no fields will be " +"retrieved. Field type is guessed from the values, and may consequently be" +" sometimes inaccurate." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:46 +msgid "Several layers can be written in the same MapML file." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:48 +msgid "" +"Only the following CRS are natively supports, EPSG:4326 (WGS 84), " +"EPSG:3857 (WebMercator), EPSG:3978 (NAD83 / Canada Atlas Lambert) and " +"EPSG:5936 (WGS 84 / EPSG Alaska Polar Stereographic). Layers in other CRS" +" will be automatically reprojected to EPSG:4326." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:53 +msgid "" +"Geometry types Point, LineString, Polygon, MultiPoint, MultiLineString, " +"MultiPolygon and GeometryCollection are supported." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:56 +msgid "Attributes are written as a HTML table." +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:152 +msgid "`MapML specification <https://maps4html.org/MapML/spec>`_" +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:153 +msgid "`MapML schemas <https://github.com/Maps4HTML/MapML/tree/gh-pages/schema>`_" +msgstr "" + +#: ../../source/drivers/vector/mapml.rst:154 +msgid ":ref:`gdal2tiles` mapml output" +msgstr "" + +#: ../../source/drivers/vector/memory.rst:10 +msgid "" +"This driver implements read and write access layers of features contained" +" entirely in memory. This is primarily useful as a high performance, and " +"highly malleable working data store. All update options, geometry types, " +"and field types are supported." +msgstr "" + +#: ../../source/drivers/vector/memory.rst:15 +msgid "" +"There is no way to open an existing Memory datastore. It must be created " +"with CreateDataSource() and populated and used from that handle. When the" +" datastore is closed all contents are freed and destroyed." +msgstr "" + +#: ../../source/drivers/vector/memory.rst:19 +msgid "" +"The driver does not implement spatial or attribute indexing, so spatial " +"and attribute queries are still evaluated against all features. Fetching " +"features by feature id should be very fast (just an array lookup and " +"feature copy)." +msgstr "" + +#: ../../source/drivers/vector/memory.rst:34 +msgid "" +"Any name may be used for a created datasource. There are no datasource or" +" layer creation options supported. Layer names need to be unique, but are" +" not otherwise constrained." +msgstr "" + +#: ../../source/drivers/vector/memory.rst:38 +msgid "" +"Before GDAL 2.1, feature ids passed to CreateFeature() are preserved " +"*unless* they exceed 10000000 in which case they will be reset to avoid a" +" requirement for an excessively large and sparse feature array. Starting " +"with GDAL 2.1, sparse IDs can be handled." +msgstr "" + +#: ../../source/drivers/vector/memory.rst:43 +msgid "New fields can be added or removed to a layer that already has features." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:8 +msgid "MiraMonVector" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:12 +msgid "" +"This driver is capable of translating (reading and writing) structured " +"vectors of point, arc (*linestrings*), and polygon types from MiraMon " +"vector format." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:15 +msgid "" +"In MiraMon the concepts of OGRMultiPoints and OGRMultiLineStrings are not" +" supported, but the driver translates a multipoint into N points and a " +"multistring into N arcs. When reading a MiraMon file of type *.pol*, the " +"corresponding layer will be reported as of type wkbPolygon, but depending" +" on the number of parts of each geometry, the actual type of the geometry" +" for each feature can be either OGRPolygon or OGRMultiPolygon." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:22 +msgid "" +"The reading driver verifies if multipart polygons adhere to the " +"specification (that is to say, the vertices of outer rings should be " +"oriented clockwise on the X/Y plane, and those of inner rings " +"counterclockwise). Otherwise, the driver corrects the orientation (in the" +" original format this specification is not the case as polygon files are " +"based on topological arc files, where the order of the vertices may be " +"relevant)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:30 +msgid "" +"Measures (M coordinate) are not supported. Symbolization is neither read " +"nor generated by this driver." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:33 +msgid "" +"A `look-up-table of MiraMon " +"<https://www.miramon.cat/help/eng/mm32/AP6.htm>`__ and `EPSG " +"<https://epsg.org/home.html>`__ Spatial Reference Systems allows matching" +" identifiers in both systems." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:37 +msgid "" +"If a layer contains an old *.rel* format file (used some decades ago), a " +"warning message will appear explaining how to convert it into a modern " +"*.rel 4* file." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:50 +msgid "Overview of MiraMon format" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:52 +msgid "" +"The MiraMon format is a binary format for vector layer data, linked to " +"one or more database tables, with or without topology and with rich " +"metadata. More information about the structured MiraMon vector format is " +"available `on the public specification " +"<https://www.miramon.cat/new_note/eng/notes/MiraMon_structured_vectors_file_format.pdf>`__." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:57 +msgid "" +"It is important to keep in mind that a MiraMon vector layer is composed " +"by several files as follows:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:59 +msgid "" +"To operate with a point layer, you must provide the name with the " +"extension .pnt (the T.dbf and T.rel files must accompany the .pnt)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:62 +msgid "" +"To operate with a linestring layer, you must provide the name with the " +"extension .arc (the A.dbf and A.rel, .nod, N.dbf, and N.rel files must " +"accompany the .arc)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:65 +msgid "" +"To operate with a polygon layer, you must provide the name with the " +"extension .pol (the P.dbf, P.rel, A.dbf and A.rel, .nod, N.dbf, and N.rel" +" files must accompany the .pol)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:68 +msgid "" +"By providing only the main file name, the driver will automatically use " +"the other sidecar files to obtain the necessary information. In the " +"creation of MiraMon layers, you only need to provide the name of the main" +" file (with or without extension), and the driver will create the rest of" +" the files." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:72 +msgid "The following outlines the information contained within each sidecar file:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:74 +msgid "" +"Preliminary note: *FileName* is, in the following explanations, the first" +" part of the name of the layer file." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:77 +msgid "" +"**Point layers**: These layers contain *point* type features which are " +"described by a single coordinate (x,y) or (x, y, z). Each layer is " +"composed by 3 files:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:80 +msgid "" +"*FileName.pnt* file: Contains the geographic database with the " +"coordinates that define the point vector features." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:83 +msgid "" +"*FileNameT.dbf* file (note the 'T' before the '.'): Contains the main " +"table of the database in dBASE (DBF) format, or in `extended DBF format " +"<https://www.miramon.cat/new_note/eng/notes/DBF_estesa.pdf>`__, if " +"necessary. It contains the information (usually alphanumeric, but also " +"file or web links, etc) of every feature. The Feature Identifier (FID) " +"field is a field called *ID_GRAFIC* and relates every geographical " +"feature to one or more records in the main table." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:89 +msgid "" +"*FileNameT.rel* file (note the 'T' before the '.'): Contains the layer " +"metadata, the relational structure of the database (links between the " +"main table and other tables [thesauruses, etc] if needed, and the " +"cardinality of the link) and the default symbolization description. In " +"the GDAL environment only some aspects are documented: the spatial " +"reference system, the language of the metadata (English), the extension " +"and a description of the fields." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:96 +msgid "" +"**Arc layers**: These layers contain *linestring* type features which are" +" lines described by a series of segments, each one defined by coordinates" +" (x, y) or (x, y, z). Both extreme vertices of each *linestring* are " +"called nodes. Each layer is composed by 6 files:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:100 +msgid "" +"*FileName.arc* file: Contains the geographic database with the " +"coordinates that define the linestring (arc) vector features." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:103 +msgid "" +"*FileNameA.dbf* file (note the 'A' before the '.'): Contains the main " +"table of the database in dBASE (DBF) format, or in `extended DBF format " +"<https://www.miramon.cat/new_note/eng/notes/DBF_estesa.pdf>`__, if " +"necessary. It contains the information (usually alphanumeric, but also " +"file or web links, etc) of every feature. The Feature Identifier (FID) " +"field is a field called *ID_GRAFIC* and relates every geographical " +"feature to one or more records in the main table." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:109 +msgid "" +"*FileNameA.rel* file (note the 'A' before the '.'): Contains the layer " +"metadata, the relational structure of the database (links between the " +"main table and other tables [thesauruses, etc] if needed, and the " +"cardinality of the link) and the default symbolization description. In " +"the GDAL environment only some aspects are documented: the spatial " +"reference system, the language of the metadata (English), the extension " +"and a description of the fields." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:116 +#: ../../source/drivers/vector/miramon.rst:169 +msgid "" +"*FileName.nod* file: Contains the geographic database with information " +"about the linestring needed to define each node. It is necessary in the " +"MiraMon vector format but not read by the GDAL MiraMon vector driver " +"because nodes contain topological information that is not transferred to " +"other formats." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:121 +#: ../../source/drivers/vector/miramon.rst:174 +msgid "" +"*FileNameN.dbf* file (note the 'N' before the '.'): Contains the main " +"table of the database in dBASE (DBF) format, or in extended DBF if " +"necessary. This table contains information about the relationships " +"between arcs and nodes, and other attributes of the nodes, if needed. It " +"is necessary in the MiraMon vector format but not read by the GDAL " +"MiraMon vector driver because nodes contain topological information that " +"is not transferred to other formats." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:127 +msgid "" +"*FileNameN.rel* file (note the 'N' before the '.'): Contains the layer " +"metadata, the relational structure of the database (links between the " +"main table and other tables [thesauruses, etc] if needed, and the " +"cardinality of the link) and the default symbolization description. It is" +" necessary in the MiraMon vector format but not read by the GDAL MiraMon " +"vector driver because nodes contain topological information that is not " +"transferred to other formats." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:134 +msgid "" +"**Polygon layers**: These layers contain *polygon* or *multipolygon* type" +" features. In MiraMon vector format a polygon is a closed shape described" +" by one or more arcs. A polygon can have holes inside it. A polygon can " +"also be linked to other polygons; in this case, it is termed a group " +"(*multipolygon*). Each layer is composed by 9 files:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:140 +msgid "" +"*FileName.pol* file: Contains the geographic database with information " +"about the linestring vector features needed to define the polygon (or " +"multipolygon) vector features." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:143 +msgid "" +"*FileNameP.dbf* file (note the 'P' before the '.'): Contains the main " +"table of the database in dBASE (DBF) format, or in `extended DBF format " +"<https://www.miramon.cat/new_note/eng/notes/DBF_estesa.pdf>`__, if " +"necessary. It contains the information (usually alphanumeric, but also " +"file or web links, etc) of every feature. The Feature Identifier (FID) " +"field is a field called *ID_GRAFIC* and relates every geographical " +"feature to one or more records in the main table." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:149 +msgid "" +"*FileNameP.rel* file (note the 'P' before the '.'): Contains the layer " +"metadata, the relational structure of the database (links between the " +"main table and other tables [thesauruses, etc] if needed, and the " +"cardinality of the link) and the default symbolization description. In " +"the GDAL environment only some aspects are documented: the spatial " +"reference system, the language of the metadata (English), the extension " +"and a description of the fields." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:156 +msgid "" +"*FileName.arc* file: Contains the geographic database with the " +"coordinates that define the arc vector features. The polygons within the " +"polygon file reference the arcs in this file by their index." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:159 +msgid "" +"*FileNameA.dbf* file (note the 'A' before the '.'): Contains the main " +"table of the database in dBASE (DBF) format, or in extended DBF if " +"necessary. This table contains information about the relationship between" +" arcs and polygons, not the main features information. It is necessary in" +" MiraMon but not read directly by the GDAL MiraMon vector driver because " +"it is redundant to the information on the linestring part." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:165 +msgid "" +"*FileNameA.rel* file (note the 'A' before the '.'): Contains additional " +"data about the data, the relations of the database and the symbolization " +"description. It is necessary in MiraMon but not read directly by the GDAL" +" MiraMon vector driver." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:180 +msgid "" +"*FileNameN.rel* file (note the 'N' before the '.'): Contains additional " +"data about the data, the relations of the database and the symbolization " +"description. It is necessary in MiraMon but not read directly by the GDAL" +" MiraMon vector driver." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:185 +#: ../../source/drivers/vector/shapefile.rst:66 +msgid "Encoding" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:187 +msgid "" +"When reading MiraMon files the code page setting in the header of the " +".dbf file is read and used to translate string fields to UTF-8 " +"(regardless of whether they are in ANSI, OEM or UTF-8)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:191 +msgid "" +"When writing MiraMon files the codepage of *.dbf* files can be ANSI or " +"UTF8 depending on the layer creation option DBFEncoding." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:197 +msgid "" +"MiraMon can only store one kind of geometry per layer (points, arcs or " +"polygons). Mixing different kinds of layers (including raster and " +"geoservices as WMS or WMTS) is possible through MiraMon maps (.mmm). " +"During creation the driver generates the necessary files to accommodate " +"each of the three possible types of geometries. For instance, if a layer " +"or a dataset contains points and arcs, a set of point files and a set of " +"arc files will be created." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:205 +msgid "" +"Consequently, during creation the MiraMon vector driver output can be a " +"folder or a set of files with the appropriate extension (*.pnt*, etc):" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:208 +msgid "" +"If the output is a **folder**, it will contain all the translated layers " +"with the original name in the origin dataset." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:210 +msgid "" +"In this case a *.mmm* file will be created referencing all layers in the " +"origin dataset to make an easy open of the dataset using the MiraMon " +"software." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:212 +msgid "" +"In this case, please specify the MiraMon file output format name using " +"the -f option (**-f MiraMonVector**)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:214 +msgid "" +"If the output is a **file** with extension all the translated layers in " +"the origin dataset will be created with the specified name. Use this " +"option only when you know that there is only one layer with one feature " +"type in the origin dataset." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:217 +msgid "" +"The attributes of the MiraMon feature are stored in an associated *.dbf*." +" If a classical DBF IV table could not be used (too many fields or " +"records, large text fields, etc) a file type called extended DBF is used." +" This is an improvement of dBASE IV DBF files. The specification of this " +"format can be found in `this file " +"<https://www.miramon.cat/new_note/eng/notes/DBF_estesa.pdf>`__." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:223 +msgid "" +"Note that extended *.dbf* files cannot be opened with Excel or other " +"typical programs. If the complete MiraMon Professional software is not " +"installed on the computer, the free and standalone MiraD application can " +"be downloaded from `this page <https://www.miramon.cat/USA/Prod-" +"MiraD.htm>`__ to open them." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:232 +msgid "The MiraMon driver accepts three types of sources of data:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:234 +msgid "" +"When translating from a MiraMon vector format, the MiraMon vector driver " +"input needs a file with one of the described extensions:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:237 +msgid "*.pnt* for *points*." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:238 +msgid "*.arc* for *linestrings*." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:239 +msgid "*.pol* for *polygons* (or *multipolygons*)." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:241 +msgid "" +"The extension *.nod* is not valid for translation. Take in consideration " +"all auxiliary files described above." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:244 +#: ../../source/drivers/vector/shapefile.rst:227 +msgid "Field sizes" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:246 +msgid "" +"The driver will automatically extend string and integer fields to " +"dynamically accommodate the length of the data to be inserted." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:250 +#: ../../source/drivers/vector/shapefile.rst:251 +msgid "Size Issues" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:252 +msgid "" +"Geometry: The MiraMon vector format explicitly uses 32-bit offsets in the" +" 1.1 version and 64-bit offsets in the 2.0 version. It is better to " +"produce 1.1 version files if 2.0 version is not really necessary than " +"always use 2.0 version. Version 1.x files are smaller." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:256 +#: ../../source/drivers/vector/shapefile.rst:257 +msgid "" +"Attributes: The dbf format does not have any offsets in it, so it can be " +"arbitrarily large." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:262 +msgid "The following open options are available." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:315 +msgid "" +"As at the moment of this release, UTF-8 tables are not editable in the " +"`MiraD application <https://www.miramon.cat/USA/Prod-MiraD.htm>`__, so it" +" is recommended to use ANSI instead, if there are no coding problems." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:329 +msgid "" +"A translation from an *Example_1.dxf* file with one layer but some " +"different geometric types in the layer, will result 'file1.dxf' into a " +"new MiraMon set of layers in the 'output_folder'." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:337 +msgid "" +"A translation from a *Example_2.dxf* file with one polygon type layer " +"'file1.dxf' into a new MiraMon layer 'territories.pol' (with UTF-8 " +"encoding at the *.dbf* files) is performed like this:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:345 +msgid "" +"A translation from a MiraMon layer of arcs, 'rivers.arc', into a new " +"*.gml* file (taking only the first element of the multirecords in the " +"attributes table) is performed like this:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:352 +msgid "" +"A translation from a MiraMon layer 'tracks.arc' into a new *.gml* file " +"taking the first height of every point is performed like this:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:359 +msgid "" +"A translation from a MiraMon layer 'tracks.arc' into a new *.gml* file " +"taking the last height of every point and documenting the attribute " +"descriptors in Catalan (if the layer is multilingual and it has this " +"language available) is performed like this:" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:371 +msgid "" +"`MiraMon's vector format specifications " +"<https://www.miramon.cat/new_note/eng/notes/MiraMon_structured_vectors_file_format.pdf>`__" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:372 +msgid "" +"`MiraMon Extended DBF format " +"<https://www.miramon.cat/new_note/eng/notes/DBF_estesa.pdf>`__" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:373 +msgid "" +"`MiraMon vector layer concepts " +"<https://www.miramon.cat/help/eng/mm32/ap2.htm#structured_vector>`__." +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:374 +msgid "`MiraMon page <https://www.miramon.cat/Index_usa.htm>`__" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:375 +msgid "`MiraMon help guide <https://www.miramon.cat/help/eng>`__" +msgstr "" + +#: ../../source/drivers/vector/miramon.rst:376 +msgid "" +"`Grumets research group, the people behind MiraMon " +"<https://www.grumets.cat/index_eng.htm>`__" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:6 +msgid "MapInfo File" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:10 +msgid "" +"MapInfo datasets in native (TAB) format and in interchange (MIF/MID) " +"format are supported for reading and writing. Update of existing TAB " +"files is supported (append of new features, modifications and deletions " +"of existing features, adding/renaming/deleting fields, ...). Update of " +"existing MIF/MID files is not supported." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:17 +msgid "" +"Note: In the rest of this document \"MIF/MID File\" is used to refer to a" +" pair of .MIF + .MID files, and \"TAB file\" refers to the set of files " +"for a MapInfo table in binary form (usually with extensions .TAB, .DAT, " +".MAP, .ID, .IND)." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:22 +msgid "" +"The MapInfo driver treats a whole directory of files as a dataset, and a " +"single file within that directory as a layer. In this case the directory " +"name should be used as the dataset name." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:26 +msgid "" +"However, it is also possible to use one of the files (.tab or .mif) in a " +"MapInfo set as the dataset name, and then it will be treated as a dataset" +" with one single layer." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:30 +msgid "" +"MapInfo coordinate system information is supported for reading and " +"writing." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:45 +msgid "" +"The TAB File format requires that the bounds (geographical extents) of a " +"new file be set before writing the first feature." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:48 +msgid "" +"There is currently no automated setting of valid default bounds for each " +"spatial reference system, so for the time being, the MapInfo driver sets " +"the following default bounds when a new layer is created:" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:52 +msgid "" +"For a file in LAT/LON (geographic) coordinates: BOUNDS (-180, -90) (180, " +"90)" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:54 +msgid "" +"For any other projection: BOUNDS (-30000000 + false_easting, -15000000 + " +"false_northing) (30000000 + false_easting, 15000000 + false_northing)" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:58 +msgid "It is possible to override those bounds through two mechanisms." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:60 +msgid "" +"specify a user-defined file that contain projection definitions with " +"bounds. The name of this file must be specified with the " +":config:`MITAB_BOUNDS_FILE` configuration option. This allows users to " +"override the default bounds for existing projections, and to define " +"bounds for new projections not listed in the hard-coded table in the " +"driver. The format of the file is a simple text file with one CoordSys " +"string per line. The CoordSys lines should follow the MIF specs, and MUST" +" include the optional Bounds definition at the end of the line, e.g." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:74 +msgid "" +"It is also possible to establish a mapping between a source CoordSys and " +"a target CoordSys with bounds. Such a mapping is specified by adding a " +"line starting with \"Source = \" followed by a CoordSys (spaces before or" +" after the equal sign do not matter). The following line should start " +"with \"Destination = \" followed by a CoordSys with bounds, e.g." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:87 +msgid "use the :lco:`BOUNDS` layer creation option (see below)" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:89 +msgid "" +"If no coordinate system is provided when creating a layer, the projection" +" case is used, not geographic, which can result in very low precision if " +"the coordinates really are geographic. You can add \"-a_srs WGS84\" to " +"the **ogr2ogr** commandline during a translation to force geographic " +"mode." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:95 +msgid "MapInfo feature attributes suffer a number of limitations:" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:97 +msgid "" +"Only Integer, Real and String field types can be created. The various " +"list, and binary field types cannot be created." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:99 +msgid "" +"For String fields, the field width is used to establish storage size in " +"the .dat file. This means that strings longer than the field width will " +"be truncated" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:102 +msgid "String fields without an assigned width are treated as 254 characters." +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:164 +msgid "Currently supported values for the encoding name are:" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:166 +msgid "MapInfo encodings" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ENCODING value" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "MapInfo charset" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "description" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "\"\" (empty string)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "Neutral" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "No character conversions performed." +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "UTF-8 (Works with recent MapInfo versions, since v15.2)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_1" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-1 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-2" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_2" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-2 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-3" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_3" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-3 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-4" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_4" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-4 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-5" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_5" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-5 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-6" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_6" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-6 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-7" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_7" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-7 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-8" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_8" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-8 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO-8859-9" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO8859_9" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "ISO 8859-9 (UNIX)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "EUC-JP" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "PackedEUCJapaese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "UNIX, standard Japanese implementation." +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1252" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsLatin1" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1250" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsLatin2" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1256" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsArabic" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1251" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsCyrillic" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1257" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsBalticRim" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1253" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsGreek" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1255" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsHebrew" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP1254" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsTurkish" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "Windows Eastern Europe" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP950" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsTradChinese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "Windows Traditional Chinese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP936" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsSimpChinese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "Windows Simplified Chinese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP932" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsJapanese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP949" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "WindowsKorean" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP437" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage437" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 437 = IBM Extended ASCII" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP850" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage850" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 850 = Multilingual" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP852" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage852" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 852 = Eastern Europe" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP855" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage855" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 855 = Cyrillic" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP857" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage857" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP860" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage860" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 860 = Portuguese" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP861" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage861" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 861 = Icelandic" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP863" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage863" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 863 = French Canadian" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP864" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage864" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 864 = Arabic" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP865" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage865" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 865 = Nordic" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CP869" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "CodePage869" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "DOS Code Page 869 = Modern Greek" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "(no iconv match)" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "LICS" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "Lotus worksheet release 1,2 character set" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "LMBCS" +msgstr "" + +#: ../../source/drivers/vector/mapinfo_encodings.csv:1 +msgid "Lotus worksheet release 3,4 character set" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:206 +msgid "`MITAB Page <http://mitab.maptools.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/mitab.rst:207 +msgid "" +"`About friendly layer names " +"<https://support.pitneybowes.com/SearchArticles/VFP05_KnowledgeWithSidebarHowTo?id=kA180000000CtuHCAS&popup=false&lang=en_US>`__" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:12 +msgid "This driver can connect to the a MongoDB service." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:14 +msgid "" +"The driver supports read, creation, update and delete operations of " +"documents/features and collections/layers. The MongoDB database must " +"exist before operating on it with OGR." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:18 +msgid "This driver requires the MongoDB C++ v3.4.0 client library." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:28 +msgid "MongoDB vs OGR concepts" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:30 +msgid "" +"A MongoDB collection within a database is considered as a OGR layer. A " +"MongoDB document is considered as a OGR feature." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:36 +msgid "There are two main possible syntaxes:" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:38 +msgid "" +"One using `MongoDB URI <https://docs.mongodb.com/manual/reference" +"/connection-string/index.html>`__ prefixed with *MONGODBV3:*, such as " +"MONGODBV3:mongodb://[usr:pwd@]host1[:port1]...[,hostN[:portN]]][/[db][?options]]" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:42 +msgid "" +"One using just MongoDBv3: as the name and open options to specify host, " +"port, user, password, database, etc..." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:45 +msgid "" +"Note: the MONGODBV3: prefix before a URI starting with *mongodb://* is " +"required to make it recognize by this driver, instead of the legacy " +"driver. If the URI is starting with *mongodb+srv://*, then it is not " +"needed." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:50 +msgid "|about-open-options| The open options available are:" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:149 +msgid "Whether to use bulk insert for feature creation." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:154 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server when a \"2d\" or \"2dsphere\" spatial index is available on " +"the geometry field." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:158 +msgid "" +"However, in the current state, SQL attribute filters set with " +"SetAttributeFilter() are evaluated only on client-side. To enable server-" +"side filtering, the string passed to SetAttributeFilter() must be a JSON " +"object in the `MongoDB filter syntax " +"<https://docs.mongodb.com/manual/reference/method/db.collection.find/index.html>`__." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:167 +msgid "" +"Features are retrieved from the server by chunks of 101 documents or just" +" enough documents to exceed 1 megabyte. Subsequent batch size is 4 " +"megabytes. This can be altered with the BATCH_SIZE open option." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:174 +msgid "" +"When reading a MongoDB collection, OGR must establish the schema of " +"attribute and geometry fields, since, contrary to MongoDB collections " +"which are schema-less, OGR has a fixed schema concept." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:178 +msgid "" +"In the general case, OGR will read the first 100 documents (can be " +"altered with the FEATURE_COUNT_TO_ESTABLISH_FEATURE_DEFN open option) of " +"the collection and build the schema that best fit to the found fields and" +" values." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:183 +msgid "" +"If the collection/layer has been previously created with OGR, a " +"\\_ogr_metadata special collection contains the OGR schema, in which case" +" it will be directly used. It might be possible to ignore the schema " +"written in \\_ogr_metadata by setting the USE_OGR_METADATA=NO open " +"option." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:189 +msgid "" +"It is also possible to set the JSON_FIELD=YES open option so that a " +"\\_json special field is added to the OGR schema. When reading MongoDB " +"documents as OGR features, the full JSON version of the document will be " +"stored in the \\_json field. This might be useful in case of complex " +"documents or with data types that do not translate well in OGR data " +"types. On creation/update of documents, if the \\_json field is present " +"and set, its content will be used directly (other fields will be " +"ignored)." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:201 +msgid "" +"MongoDB have a special \\_id field that contains the unique ID of the " +"document. This field is returned as an OGR field, but cannot be used as " +"the OGR special FeatureID field, which must be of integer type. By " +"default, OGR will try to read a potential 'ogc_fid' field to set the OGR " +"FeatureID. The name of this field to look up can be set with the FID open" +" option. If the field is not found, the FID returned by OGR will be a " +"sequential number starting at 1, but it is not guaranteed to be stable at" +" all." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:213 +msgid "" +"If specifying \"MongoDB\" as the dialect of ExecuteSQL(), a JSON string " +"with a serialized `MongoDB command " +"<https://docs.mongodb.com/manual/reference/command/index.html>`__ can be " +"passed. The result will be returned as a JSON string in a single OGR " +"feature." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:219 +msgid "Standard SQL requests will be executed on client-side." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:224 +msgid "Layer/collection creation and deletion is possible." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:229 +msgid "" +"When inserting a new feature with CreateFeature(), and if the command is " +"successful, OGR will fetch the returned \\_id and use it for the " +"SetFeature() operation." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:286 +msgid "Listing the tables of a MongoDB database:" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:292 +msgid "Filtering on a MongoDB field:" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:298 +msgid "Creating and populating a collection from a shapefile:" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:307 +msgid "" +"GDAL/OGR must be built against the `MongoDB C++ driver client library " +"<https://github.com/mongodb/mongo-cxx-driver>`__, v3.4.0, in order to the" +" MongoDBv3 driver to be compiled." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:311 +msgid "" +"You must first follow `MongoDB C++ driver client build instructions " +"<http://mongocxx.org/mongocxx-v3/installation/>`__." +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:314 +msgid "Then:" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:316 +msgid "" +"On Linux/Unix, run ./configure --with-mongocxxv3 (potentially by " +"overriding PKG_CONFIG_PATH to point to the " +"{INSTALLATION_PREFIX_OF_MONGOCXX}/lib/pkgconfig" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:319 +msgid "" +"On Windows, uncomment and adapt the following in nmake.opt (or add in " +"nmake.local):" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:334 +msgid "`MongoDB C++ Driver <https://github.com/mongodb/mongo-cxx-driver>`__" +msgstr "" + +#: ../../source/drivers/vector/mongodbv3.rst:335 +msgid "`MongoDB Manual <https://docs.mongodb.com/manual/>`__" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:4 +msgid "MSSQLSpatial - Microsoft SQL Server Spatial Database" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:6 +msgid "MSSQLSpatial" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:10 +msgid "" +"This driver implements support for access to spatial tables in Microsoft " +"SQL Server 2008+ which contains the geometry and geography data types to " +"represent the geometry columns." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:26 +msgid "" +"To connect to a MSSQL datasource, use a connection string specifying the " +"database name, with additional parameters as necessary. The connection " +"strings must be prefixed with '*MSSQL:*'." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:32 +msgid "" +"In addition to the standard parameters of the `ODBC driver connection " +"string <http://msdn.microsoft.com/en-us/library/ms130822.aspx>`__ format " +"the following custom parameters can also be used in the following syntax:" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:37 +msgid "" +"**Tables=schema1.table1(geometry column1),schema2.table2(geometry " +"column2)**: By using this parameter you can specify the subset of the " +"layers to be used by the driver. If this parameter is not set, the layers" +" are retrieved from the geometry_columns metadata table. You can omit " +"specifying the schema and the geometry column portions of the syntax." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:43 +msgid "" +"**GeometryFormat=native|wkb|wkt|wkbzm**: The desired format in which the " +"geometries should be retrieved from the server. The default value is " +"'native' in this case the native SqlGeometry and SqlGeography " +"serialization format is used. When using the 'wkb' or 'wkt' setting the " +"geometry representation is converted to 'Well Known Binary' and 'Well " +"Known Text' at the server. This conversion requires a significant " +"overhead at the server and makes the feature access slower than using the" +" native format. The wkbzm format can only be used with SQL Server 2012." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:53 +msgid "The parameter names are not case sensitive in the connection strings." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:55 +msgid "" +"Specifying the **Database** parameter is required by the driver in order " +"to select the proper database." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:58 +msgid "" +"The connection may contain the optional **Driver** parameter if a custom " +"SQL server driver should be loaded (like FreeTDS). The default is **{SQL " +"Server}**." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:62 +msgid "" +"Authentication is supported either through a **trusted_conection** or " +"through username (**UID**) and password (**PWD**). As providing username " +"and password on the commandline can be a security issue, login " +"credentials can also be more securely stored in user defined environment " +"variables *MSSQLSPATIAL_UID* and *MSSQLSPATIAL_PWD*." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:69 +#: ../../source/drivers/vector/netcdf.rst:140 +#: ../../source/drivers/vector/pg_advanced.rst:60 +msgid "Layers" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:71 +msgid "" +"If the user defines the environment variable " +":config:`MSSQLSPATIAL_LIST_ALL_TABLES=YES` (and does not specify Tables= " +"in the connection string), all regular user tables will be treated as " +"layers. This option is useful if you want tables with with no spatial " +"data" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:76 +msgid "" +"By default the MSSQL driver will only look for layers that are registered" +" in the *geometry_columns* metadata table. If the user defines the " +"environment variable :config:`MSSQLSPATIAL_USE_GEOMETRY_COLUMNS=NO` then " +"the driver will look for all user spatial tables found in the system " +"catalog" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:85 +msgid "" +"The MS SQL Spatial driver passes SQL statements directly to MS SQL by " +"default, rather than evaluating them internally when using the " +"ExecuteSQL() call on the OGRDataSource, or the -sql command option to " +"ogr2ogr. Attribute query expressions are also passed directly through to " +"MSSQL. It's also possible to request the OGR MSSQL driver to handle SQL " +"commands with the :ref:`OGR SQL <ogr_sql_dialect>` engine, by passing " +"**\"OGRSQL\"** string to the ExecuteSQL() method, as the name of the SQL " +"dialect." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:94 +msgid "" +"The MSSQL driver in OGR supports the OGRLayer::StartTransaction(), " +"OGRLayer::CommitTransaction() and OGRLayer::RollbackTransaction() calls " +"in the normal SQL sense." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:101 +msgid "" +"This driver doesn't support creating new databases, you might want to use" +" the *Microsoft SQL Server Client Tools* for this purpose, but it does " +"allow creation of new layers within an existing database." +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:286 +msgid "The driver implements transactions at the dataset level, per :ref:`rfc-54`" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:291 +msgid "Creating a layer from an OGR data source" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:299 +msgid "Connecting to a layer and dump the contents" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:307 +msgid "Connecting with username/password" +msgstr "" + +#: ../../source/drivers/vector/mssqlspatial.rst:313 +msgid "Connecting with username/password stored in environment variables" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:8 +msgid "MVT" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:12 +msgid "" +"The MVT driver can read and write Mapbox Vector Tile files, as standalone" +" files, uncompressed or gzip-compressed (typical extensions are .pbf, " +".mvt, .mvt.gz), or a tileset at a given zoom level of such files. Write " +"support requires GDAL to be built with libsqlite3 and GEOS support." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:18 +msgid "" +"Mapbox Vector Tiles stored within a SQLite container conforming to the " +"MBTiles format are handled by the :ref:`MBTiles <raster.mbtiles>` driver." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:22 +msgid "" +"Tilesets of MVT files can for example be generated by `tippecanoe " +"<https://github.com/mapbox/tippecanoe>`__ or `tileserver-gl " +"<https://github.com/klokantech/tileserver-gl>`__. The output file " +"hierarchy will contain a :ref:`metadata.json <mvt_metadata_json>` file at" +" its root and {z}/{x}/{y}.pbf files with the tiles, where z is the zoom " +"level and (x, y) the coordinate of the tile in a given zoom level. The " +"origin of the tiling system is the top-left tile (XYZ convention). For " +"example, for zoom levels 0 and 1 :" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:45 +msgid "" +"The driver will assume by default EPSG:3857 (WebMercator) spatial " +"reference system and Z/X/Y tiling structure, if opening a filename with " +"{Z}/{X}/{Y}.pbf or {Z}-{X}-{Y}.pbf name, or a zoom level of a tileset. " +"Otherwise integer coordinates will be reported." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:50 +msgid "" +"Note: When opening a zoom level of a tileset, the driver will make no " +"effort of stitching together geometries for features that overlap several" +" tiles." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:66 +msgid "The following connection strings are supported:" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:68 +msgid "*/path/to/some.pbf*" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:69 +msgid "*MVT:http[s]://path/to/some.pbf*" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:70 +msgid "" +"*/path/to/{Z}*: where {Z} is a zoom level between 0 and 30, tiles are in " +"/path/to/{Z}/{X}/{Y}.pbf files, and /path/to/metadata.json or " +"/path/to.json should typically exist." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:73 +msgid "*MVT:http[s]://path/to/{Z]*" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:75 +msgid "" +"The MVT: prefix may be added before the filename or directory name to " +"help forcing identification of datasets in some rare cases where non-" +"guided identification would fail." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:82 +msgid "metadata.json" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:84 +msgid "" +"This file is typically generated by tippecanoe and has the following " +"content:" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:138 +msgid "" +"The MVT driver only uses the \"json\" key to retrieve the layer names, " +"their fields and the geometry type, and the \"bounds\" key for the layer " +"extent." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:142 +msgid "" +"If this file cannot be found, the layer schema is established by scanning" +" the features of the tile(s)." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:145 +msgid "" +"As an extension, OGR handles in reading and writing custom tiling schemes" +" by using the *crs*, *tile_origin_upper_left_x*, " +"*tile_origin_upper_left_y* and *tile_dimension_zoom_0* metadata items. " +"For example, for the Finnish ETRS-TM35FIN (EPSG:3067) tiling scheme:" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:216 +msgid "" +"Tiles are generated with WebMercator (EPSG:3857) projection by default " +"(custom tiling schemes can be defined with the TILING_SCHEME option). " +"Several layers can be written. It is possible to decide at which zoom " +"level ranges a given layer is written." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:269 +#: ../../source/drivers/vector/pmtiles.rst:133 +msgid "" +"Maximum zoom level at which tiles are generated. Maximum supported value " +"is 22." +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:370 +#: ../../source/drivers/vector/pmtiles.rst:190 +msgid "Layer configuration" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:442 +msgid "" +"`Mapbox Vector Tile Specification <https://github.com/mapbox/vector-tile-" +"spec>`__" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:444 +msgid ":ref:`MBTiles <raster.mbtiles>` driver" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:445 +msgid "" +"`tippecanoe <https://github.com/mapbox/tippecanoe>`__: Builds vector " +"tilesets from large (or small) collections of GeoJSON, Geobuf, or CSV " +"features" +msgstr "" + +#: ../../source/drivers/vector/mvt.rst:448 +msgid "" +"`Links to tools dealing with Mapbox Vector Tiles " +"<https://github.com/mapbox/awesome-vector-tiles>`__" +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:10 +msgid "" +"This driver implements read and write access for spatial data in `MySQL " +"<http://www.mysql.org/>`__ tables." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:13 +msgid "" +"When opening a database, its name should be specified in the form " +"\"MYSQL:dbname[,options]\" where the options can include comma separated " +"items like \"user=*userid*\", \"password=*password*\", \"host=*host*\" " +"and \"port=*port*\"." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:18 +msgid "" +"As well, a \"tables=*table*;*table*...\" option can be added to restrict " +"access to a specific list of tables in the database. This option is " +"primarily useful when a database has a lot of tables, and scanning all " +"their schemas would take a significant amount of time." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:23 +msgid "" +"Currently all regular user tables are assumed to be layers from an OGR " +"point of view, with the table names as the layer names. Named views are " +"not currently supported." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:27 +msgid "" +"If a single integer field is a primary key, it will be used as the FID " +"otherwise the FID will be assigned sequentially, and fetches by FID will " +"be extremely slow." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:31 +msgid "" +"By default, SQL statements are passed directly to the MySQL database " +"engine. It's also possible to request the driver to handle SQL commands " +"with :ref:`OGR SQL <ogr_sql_dialect>` engine, by passing **\"OGRSQL\"** " +"string to the ExecuteSQL() method, as name of the SQL dialect." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:46 +msgid "" +"In the case of a layer defined by a SQL statement, fields either named " +"\"OGC_FID\" or those that are defined as NOT NULL, are a PRIMARY KEY, and" +" are an integer-like field will be assumed to be the FID." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:49 +msgid "" +"Geometry fields are read from MySQL using WKB format. Versions older than" +" 5.0.16 of MySQL are known to have issues with some WKB generation and " +"may not work properly." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:52 +msgid "" +"The OGR_FID column, which can be overridden with the MYSQL_FID layer " +"creation option, is implemented as a **INT UNIQUE NOT NULL " +"AUTO_INCREMENT** field. This appears to implicitly create an index on the" +" field." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:56 +msgid "" +"The geometry column, which defaults to *SHAPE* and can be overridden with" +" the :lco:`GEOMETRY_NAME` layer creation option, is created as a **NOT " +"NULL** column in unless :lco:`SPATIAL_INDEX` is disabled. By default a " +"spatial index is created at the point the table is created." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:60 +msgid "" +"SRS information is stored using the OGC Simple Features for SQL layout, " +"with *geometry_columns* and *spatial_ref_sys* metadata tables being " +"created in the specified database if they do not already exist. The " +"*spatial_ref_sys* table is **not** pre-populated with SRS and EPSG values" +" like PostGIS. If no EPSG code is found for a given table, the MAX(SRID) " +"value will be used. With MySQL 8.0 or later, the " +"*ST_SPATIAL_REFERENCE_SYSTEMS* table provided by the database is used " +"instead of *spatial_ref_sys*." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:68 +msgid "" +"Connection timeouts to the server can be specified with the " +"**MYSQL_TIMEOUT** environment variable. For example, SET " +"MYSQL_TIMEOUT=3600. It is possible this variable only has an impact when " +"the OS of the MySQL server is Windows." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:72 +msgid "" +"The MySQL driver opens a connection to the database using " +"CLIENT_INTERACTIVE mode. You can adjust this setting " +"(interactive_timeout) in your mysql.ini or mysql.cnf file of your server " +"to your liking." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:76 +msgid "" +"We are using WKT to insert geometries into the database. If you are " +"inserting big geometries, you will need to be aware of the " +"*max_allowed_packet* parameter in the MySQL configuration. By default it " +"is set to 1M, but this will not be large enough for really big " +"geometries. If you get an error message like: *Got a packet bigger than " +"'max_allowed_packet' bytes*, you will need to increase this parameter." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:87 +msgid "" +"The MySQL driver does not support creation of new datasets (a database " +"within MySQL), but it does allow creation of new layers within an " +"existing database." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:91 +msgid "" +"By default, the MySQL driver will attempt to preserve the precision of " +"OGR features when creating and reading MySQL layers. For integer fields " +"with a specified width, it will use **DECIMAL** as the MySQL field type " +"with a specified precision of 0. For real fields, it will use **DOUBLE** " +"with the specified width and precision. For string fields with a " +"specified width, **VARCHAR** will be used." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:98 +msgid "The MySQL driver makes no allowances for character encodings at this time." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:101 +msgid "The MySQL driver is not transactional at this time." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:164 +msgid "" +"The following example datasource name opens the database schema " +"*westholland* with password *psv9570* for userid *root* on the port " +"*3306*. No hostname is provided, so localhost is assumed. The tables= " +"directive means that only the bedrijven table is scanned and presented as" +" a layer for use." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:174 +msgid "" +"The following example uses ogr2ogr to create copy the world_borders layer" +" from a shapefile into a MySQL table. It overwrites a table with the " +"existing name *borders2*, sets a layer creation option to specify the " +"geometry column name to *SHAPE2*." +msgstr "" + +#: ../../source/drivers/vector/mysql.rst:183 +msgid "" +"The following example uses ogrinfo to return some summary information " +"about the borders2 layer in the test database." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:4 +msgid "NAS - ALKIS" +msgstr "" + +#: ../../source/drivers/vector/nas.rst:6 +msgid "NAS" +msgstr "" + +#: ../../source/drivers/vector/nas.rst:10 +msgid "" +"The NAS driver reads the NAS/ALKIS format used for cadastral data in " +"Germany. The format is a GML profile with fairly complex GML3 objects not" +" easily read with the general OGR GML driver." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:14 +msgid "" +"This driver depends on GDAL/OGR being built with the Xerces XML parsing " +"library." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:17 +msgid "" +"The driver looks for \"opengis.net/gml\" and one of the strings semicolon" +" separated strings listed in the configuration option **NAS_INDICATOR** " +"(which defaults to \"NAS-Operationen;AAA-Fachschema;aaa.xsd;aaa-suite\") " +"to determine if a input is a NAS file and ignores all files without any " +"matches." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:22 +msgid "" +"The configuration option **NAS_GFS_TEMPLATE** makes it possible to " +"cleanly map element paths to feature attributes using a GFS file like in " +"the GML driver. Multiple geometries per layer are also possible (eg. " +"ax_flurstueck.objektkoordinaten next to the regular wkb_geometry). " +"Starting with GDAL 3.7, defining the NAS_GFS_TEMPLATE configuration " +"option is required for the NAS driver to open a file. It may be set to " +"the empty string to mean that the driver should try to establish the " +"schema of the file from its content, but using one of templates mentioned" +" below is recommended. Alternatively, starting with GDAL 3.10, specifying" +" the ``-if NAS`` option to command line utilities accepting it, or " +"``NAS`` as the only value of the ``papszAllowedDrivers`` of " +":cpp:func:`GDALOpenEx`, also forces the driver to recognize the passed " +"filename." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:34 +msgid "" +"The GFS templates and PostgreSQL schemas are part of `norGIS ALKIS-Import" +" <http://www.norbit.de/68/>`__ (also featuring a shell script and PyQt " +"frontend which ease the import). There are currently two versions:" +msgstr "" + +#: ../../source/drivers/vector/nas.rst:38 +msgid "" +"GeoInfoDok 6: `GFS template " +"<https://github.com/norBIT/alkisimport/blob/master/alkis-schema.gfs>`__ " +"(for GDAL >=3.8 and `<3.8 " +"<https://github.com/norBIT/alkisimport/blob/master/alkis-" +"schema.37.gfs>`__) and `PostgreSQL schema " +"<https://github.com/norBIT/alkisimport/blob/master/alkis-schema.sql>`__" +msgstr "" + +#: ../../source/drivers/vector/nas.rst:39 +msgid "" +"GeoInfoDok 7.1.2: `GFS template " +"<https://github.com/norBIT/alkisimport/blob/gid7/alkis-schema.gfs>`__ and" +" `PostgreSQL schema <https://github.com/norBIT/alkisimport/blob/gid7" +"/alkis-schema.sql>`__" +msgstr "" + +#: ../../source/drivers/vector/nas.rst:41 +msgid "" +"The files were generated using `xmi2db " +"<https://github.com/norBIT/xmi2db/>`__ (fork of `xmi2db " +"<https://github.com/pkorduan/xmi2db>`__) from the official application " +"schema." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:45 +msgid "" +"In GDAL 3.8 the creation of the relation layer *alkis_beziehungen* was " +"removed. Prior the configuration option **NAS_NO_RELATION_LAYER** allowed" +" to disable its population - which was default in ALKIS-Import. The " +"information found there was redundant to the relation fields also " +"contained in original elements/tables. Enabling the option also made " +"progress reporting available." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:51 +msgid "" +"Duplicate data in datasets will usually causes errors. When importing " +"separate datasets into PostgreSQL it is useful to enable " +"\"OGR_PG_SKIP_CONFLICTS\" to skip conflicting features." +msgstr "" + +#: ../../source/drivers/vector/nas.rst:55 +msgid "" +"This driver was implemented within the context of the `PostNAS project " +"<http://trac.wheregroup.com/PostNAS>`__, which has more information on " +"its use and other related projects." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:4 +msgid "NetCDF: Network Common Data Form - Vector" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:12 +msgid "" +"The netCDF driver supports read and write (creation from scratch and in " +"some cases append operations) to vector datasets (you can find " +"documentation for the :ref:`raster side <raster.netcdf>`)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:16 +msgid "" +"NetCDF is an interface for array-oriented data access and is used for " +"representing scientific data." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:19 +msgid "" +"The driver handles the \"point\", \"profile\" and \"trajectory\" (single " +"trajectory) `feature types <http://cfconventions.org/cf-" +"conventions/v1.6.0/cf-conventions.html#_features_and_feature_types>`__ of" +" the CF 1.6 convention. For CF-1.7 and below (as well as non-CF files), " +"it also supports a more custom approach for non-point geometries." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:24 +msgid "" +"The driver also supports writing and reading from CF-1.8 convention " +"compliant files that have simple geometry information encoded within " +"them." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:37 +msgid "Conventions and Data Formats" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:38 +msgid "" +"The netCDF vector driver supports reading and writing netCDF files " +"following the Climate and Forecast (CF) Metadata Conventions. Vector " +"datasets can be written using the simple geometry specification of the " +"CF-1.8 convention, or by using the CF-1.6 convention and by writing non-" +"point geometry items as WKT." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:43 +msgid "Distinguishing the Two Formats" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:44 +msgid "" +"Upon reading a netCDF file, the driver will attempt to read the global " +"*Conventions* attribute. If i's value is *CF-1.8* or higher (in this " +"exact format, as specified in the CF convention), then the driver will " +"check if the netCDF file has *CF-1.8* geometries contained within it. If " +"the *Conventions* attribute has a value lower than CF-1.8 or no CF-1.8 " +"geometries, the driver will try to detect \"point\", \"profile\" and " +"\"trajectory\" (single trajectory) feature types." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:49 +msgid "CF-1.8 Writing Limitations" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:50 +msgid "" +"Writing to a CF-1.8 netCDF dataset poses some limitations. Only writing " +"the feature types specified by the CF-1.8 standard (see section `Geometry" +" <#geometry>`__ for more details) are supported, and measured features " +"are only partially supported. Other geometries, such as non-simple curve " +"geometries, are not supported in any way." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:54 +msgid "CF-1.8 datasets also do not support the *append* access mode." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:56 +msgid "" +"There are what are considered *reserved variable names* for CF-1.8 " +"datasets. These variable names are used by the driver to store its " +"metadata. Refrain from using these names as layer names to avoid naming " +"conflicts when writing datasets with multiple layers." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:59 +msgid "" +"Suppose a layer in a CF-1.8 dataset has the name LAYER with a field with " +"name FIELD. Then the following names would be considered *reserved*:" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:61 +msgid "*LAYER_node_coordinates*: used to store point information" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:62 +msgid "" +"*LAYER_node_count*: used to store per shape point count information (not " +"created if LAYER has a geometry type of Point)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:63 +msgid "" +"*LAYER_part_node_count*: used to store per part point count information " +"(only created if LAYER consists of MultiLineStrings, MultiPolygons, or " +"has at least one Polygon with interior rings)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:64 +msgid "" +"*LAYER_interior_ring*: used to store interior ring information (only " +"created if LAYER consists of at least one Polygon with interior rings)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:65 +msgid "*LAYER_field_FIELD*: used to store field information for FIELD." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:67 +msgid "These names are the only reserved names applying to CF-1.8 datasets." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:69 +msgid "CF-1.6/WKT datasets are not limited to the aforementioned restrictions." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:72 +msgid "Mapping of concepts" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:75 +msgid "Field types" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:77 +msgid "" +"On creation of netCDF files, the mapping between OGR field types and " +"netCDF type is the following :" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:81 +#: ../../source/drivers/vector/netcdf.rst:120 +msgid "netCDF type" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:83 +#: ../../source/drivers/vector/netcdf.rst:124 +msgid "String(1)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:83 +msgid "char" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:84 +msgid "char (bi-dimensional), or string for NC4" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:85 +#: ../../source/drivers/vector/netcdf.rst:129 +msgid "int" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:86 +msgid "Integer(Boolean)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:87 +#: ../../source/drivers/vector/netcdf.rst:127 +msgid "Integer(Int16)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:88 +msgid "int64 for NC4, or double for NC3 as a fallback" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:90 +#: ../../source/drivers/vector/netcdf.rst:134 +msgid "Real(Float32)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:90 +#: ../../source/drivers/vector/netcdf.rst:134 +msgid "float" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:91 +#: ../../source/drivers/vector/netcdf.rst:130 +msgid "Date" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:91 +msgid "int (with units=\"days since 1970-1-1\")" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:92 +#: ../../source/drivers/vector/netcdf.rst:136 +msgid "double (with units=\"seconds since 1970-1-1 0:0:0\")" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:95 +msgid "" +"The driver also writes the following attributes for each OGR fields / " +"netCDF variables." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:98 +msgid "" +"*ogr_field_name*: OGR field name (useful if the netCDF variable name is " +"different, due to collision)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:100 +msgid "" +"*ogr_field_type*: OGR field type (such as " +"String,Integer,Date,DateTime,etc...)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:102 +msgid "" +"*ogr_field_width*: OGR field width. Only set if it is non-zero, except " +"for strings" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:104 +msgid "*ogr_field_precision*: OGR field precision. Only set if it is non-zero" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:106 +msgid "" +"*standard_name*\": (GDAL >= 3.7) OGR field alternative name, if it is " +"compatible of the convention for the value of standard_name." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:108 +msgid "" +"*long_name*: (GDAL >= 3.7) OGR field comment, or if not set, OGR field " +"alternative name if it is not compatible of standard_name, or \"Field " +"{ogr_field_name}\" otherwise." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:112 +msgid "" +"They are written by default (unless the `WRITE_GDAL_TAGS " +"<#WRITE_GDAL_TAGS>`__ dataset creation option is set to NO). They are not" +" required for reading, but may help to better identify field " +"characteristics" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:117 +msgid "On reading, the mapping is the following :" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:123 +msgid "ubyte (NC4 only)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:124 +msgid "char (mono dimensional)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:125 +msgid "char (bi dimensional)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:126 +msgid "string (NC4 only)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:128 +msgid "ushort (NC4 only)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:130 +msgid "int or double (with units=\"days since 1970-1-1\")" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:131 +msgid "uint (NC4 only)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:132 +msgid "int64 (NC4 only)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:133 +msgid "uint64 (NC4 only)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:141 +msgid "" +"In the CF-1.8 compliant driver, a single layer corresponds to a single " +"**geometry container** within a CF-1.8 compliant netCDF file. A geometry " +"container, per the CF-1.8 specification, is referred to by another " +"variable (presumably a data variable) through the **geometry** attribute." +" When reading a CF-1.8 compliant netCDF file, all geometry containers " +"within the netCDF file will be present in the opened dataset as separate " +"layers. Similarly, when writing to a CF-1.8 dataset, each layer will be " +"written to a geometry container whose variable name is that of the source" +" layer. When writing to a CF-1.8 dataset specifically, multiple layers " +"are always enabled and are always in a single netCDF file, regardless of " +"the :dsco:`MULTIPLE_LAYERS` option." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:151 +msgid "" +"When working with files made with older versions of the driver (pre " +"CF-1.8), a single netCDF file generally corresponds to a single OGR " +"layer, provided that it contains only mono-dimensional variables, indexed" +" by the same dimension (or bi-dimensional variables of type char). For " +"netCDF v4 files with multiple groups, each group may be seen as a " +"separate OGR layer. On writing, the :dsco:`MULTIPLE_LAYERS` dataset " +"creation option can be used to control whether multiple layers is " +"disabled, or if multiple layers should go in separate files, or separate " +"groups." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:161 +msgid "Strings" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:163 +msgid "" +"Variable length strings are not natively supported in netCDF v3 format. " +"To work around that, OGR uses bi-dimensional char variables, whose first " +"dimension is the record dimension, and second dimension the maximum width" +" of the string." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:168 +msgid "" +"By default, OGR implements a \"auto-grow\" mode in writing, where the " +"maximum width of the variable used to store a OGR string field is " +"extended when needed." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:172 +msgid "" +"For WKT datasets, this leads to a full rewrite of already written " +"records; although this process is transparent for the user, it can slow " +"down the creation process in non-linear ways. A similar mechanism is used" +" to handle layers with geometry types other than point to store the ISO " +"WKT representation of the geometries." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:178 +msgid "" +"For CF-1.8 datasets, growing the string width dimension is a relatively " +"inexpensive process which does not involve recopying of records, but " +"involves only a simple integer reassignment. Because of how inexpensive " +"dimension growth is with CF-1.8 datasets, auto growth of the string width" +" dimension is always on." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:183 +msgid "" +"When using a netCDF v4 output format (NC4), strings will be by default " +"written as netCDF v4 variable length strings." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:189 +msgid "" +"Supported feature types when reading from a CF-1.8 convention compliant " +"netCDF file include OGRPoint, OGRLineString, OGRPolygon, OGRMultiPoint, " +"OGRMultiLineString, and OGRMultiPolygon. Due to slight ambiguities " +"present in the CF-1.8 convention concerning Polygons versus " +"MultiPolygons, the driver will in most cases default to assuming a " +"MultiPolygon for the geometry of a layer with **geometry_type** polygon. " +"The one exception where a Polygon type will be used is when the attribute" +" **part_node_count** is not present within that layer's geometry " +"container. Per convention requirements, the driver supports reading and " +"writing from geometries with X, Y, and Z axes. Writing from source layers" +" with features containing an M axis is also partially supported. The X, " +"Y, and Z information of a measured feature will be able to be captured in" +" a CF-1.8 netCDF file, but the measure information will be lost " +"completely." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:200 +msgid "" +"When working with a CF-1.6/WKT dataset, layers with a geometry type of " +"Point or Point25D will cause the implicit creation of x,y(,z) variables " +"for a projected coordinate system, or lon,lat(,z) variables for " +"geographic coordinate systems. For other geometry types, a variable " +"\"ogc_wkt\" ( bi-dimensional char for NC3 output, or string for NC4 " +"output) is created and used to store the geometry as a ISO WKT string." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:209 +msgid "\"Profile\" feature type" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:211 +msgid "" +"The driver can handle \"profile\" feature type, i.e. phenomenons that " +"happen at a few positions along a vertical line at a fixed horizontal " +"position. In that representation, some variables are indexed by the " +"profile, and others by the observation." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:216 +msgid "" +"More precisely, the driver supports reading and writing profiles " +"organized accordingly with the \"`Indexed ragged array representation " +"<http://cfconventions.org/cf-conventions/v1.6.0/cf-" +"conventions.html#_indexed_ragged_array_representation_of_profiles>`__\" " +"of profiles." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:221 +msgid "" +"On reading, the driver will collect values of variables indexed by the " +"profile dimension and expose them as long as variables indexed by the " +"observation dimension, based on a variable such as \"parentIndex\" with " +"an attribute \"instance_dimension\" pointing to the profile dimension." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:226 +msgid "" +"On writing, the `FEATURE_TYPE <#FEATURE_TYPE>`__\\ =PROFILE layer " +"creation option must be set and the driver will need to be instructed " +"which OGR fields are indexed either by the profile or by the observation " +"dimension. The list of fields indexed by the profile can be specified " +"with the `PROFILE_VARIABLES <#PROFILE_VARIABLES>`__ layer creation " +"options (other fields are assumed to be indexed by the observation " +"dimension). Fields indexed by the profile are the horizontal geolocation " +"(created implicitly), and other user attributes such as the location " +"name, etc. Care should be taken into selecting which variables are " +"indexed by the profile dimension: given 2 OGR features (taking into " +"account only the variables indexed by the profile dimension), if they " +"have different values for such variables, they will be considered to " +"belong to different profiles." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:240 +msgid "" +"In the below example, the station_name and time variables may be indexed " +"by the profile dimension (the geometry is assumed to be also indexed by " +"the profile dimension), since all records that have the same value for " +"one of those variables have same values for the other ones, whereas " +"temperature and Z should be indexed by the default dimension." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:247 +msgid "station_name" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:247 +msgid "time" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:247 +msgid "geometry" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:247 +msgid "temperature" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:247 +msgid "Z" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:249 +#: ../../source/drivers/vector/netcdf.rst:251 +msgid "Paris" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:249 +#: ../../source/drivers/vector/netcdf.rst:251 +msgid "2016-03-01T00:00:00Z" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:249 +#: ../../source/drivers/vector/netcdf.rst:251 +msgid "POINT (2 49)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:249 +msgid "25" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:249 +#: ../../source/drivers/vector/netcdf.rst:250 +msgid "100" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:250 +#: ../../source/drivers/vector/netcdf.rst:252 +msgid "Vancouver" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:250 +#: ../../source/drivers/vector/netcdf.rst:252 +msgid "2016-04-01T12:00:00Z" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:250 +#: ../../source/drivers/vector/netcdf.rst:252 +msgid "POINT (-123 49.25)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:250 +msgid "5" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:251 +#: ../../source/drivers/vector/netcdf.rst:252 +msgid "500" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:252 +msgid "-15" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:255 +msgid "" +"An integer field, with the name of the profile dimension (whose default " +"name is \"profile\", which can be altered with the `PROFILE_DIM_NAME " +"<#PROFILE_DIM_NAME>`__ layer creation option), will be used to store the " +"automatically computed id of profile sites (unless a integer OGR field " +"with the same name exits)." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:261 +msgid "" +"The size of the profile dimension defaults to 100 for non-NC4 output " +"format, and is extended automatically in case of additional profiles " +"(with similar performance issues as growing strings). For NC4 output " +"format, the profile dimension is of unlimited size by default." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:295 +msgid "Whether to write GDAL specific information as netCDF attributes." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:304 +msgid "" +"The following option will only have effect when simultaneously specifying" +" :dsco:`GEOMETRY_ENCODING=WKT`:" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:321 +msgid "|about-layer-creation-options|" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:323 +msgid "The following option applies to both dataset types:" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:332 +msgid "" +"The following options require a dataset with " +":dsco:`GEOMETRY_ENCODING=WKT`:" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:394 +msgid "The following option requires a dataset with GEOMETRY_ENCODING=CF_1.8:" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:425 +msgid "XML configuration file" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:427 +msgid "" +"A XML configuration file conforming to the schema specified in " +":source_file:`frmts/netcdf/data/netcdf_config.xsd` can be used for very " +"precise control on the output format, in particular to set all needed " +"attributes (such as units) to conform to the `NetCDF CF-1.6 convention " +"<http://cfconventions.org/cf-conventions/v1.6.0/cf-conventions.html>`__." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:434 +msgid "" +"It has been designed in particular, but not exclusively, to be usable in " +"use cases involving the `MapServer OGR output " +"<http://mapserver.org/output/ogr_output.html>`__." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:438 +msgid "Such a file can be used to :" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:440 +msgid "set dataset and layer creation options." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:441 +msgid "set global netCDF attributes." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:442 +msgid "map OGR field names to netCDF variable names." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:443 +msgid "set netCDF attributes attached to netCDF variables." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:445 +msgid "" +"The scope of effect is either globally, when elements are defined as " +"direct children of the root <Configuration> node, or specifically to a " +"given layer, when defined as children of a <Layer> node." +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:449 +msgid "" +"The filename is specified with the CONFIG_FILE dataset creation option. " +"Alternatively, the content of the file can be specified inline as the " +"value of the option (it must then begin strictly with the " +"\"<Configuration\" characters)" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:454 +msgid "The following example shows all possibilities and precedence rules:" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:489 +msgid "The effect on the output can be checked by running the **ncdump** utility" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:493 +msgid "Further Reading" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:495 +msgid ":ref:`Raster side of the netCDF driver. <raster.netcdf>`" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:496 +msgid "" +"`NetCDF CF-1.6 convention <http://cfconventions.org/cf-conventions/v1.6.0" +"/cf-conventions.html>`__" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:498 +msgid "" +"`NetCDF CF-1.8 convention draft <https://github.com/cf-convention/cf-" +"conventions/blob/master/ch07.adoc>`__" +msgstr "" + +#: ../../source/drivers/vector/netcdf.rst:508 +msgid "" +"Development of the read/write vector capabilities for netCDF was funded " +"by `Meteorological Service of Canada <https://www.ec.gc.ca/meteo-" +"weather/>`__ , `World Ozone and Ultraviolet Radiation Data Centre " +"<http://woudc.org>`__, and the `US Geological Survey " +"<https://www.usgs.gov>`__." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:43 +msgid "" +"The driver can connect to the services implementing the NextGIS Web REST " +"API. NGW driver requires cURL support in GDAL. The driver supports read " +"and write operations." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:53 +msgid "" +"**NextGIS Web URL** may be an URL to nextgis.com cloud service (for " +"example, https://demo.nextgis.com), or some other URL including port and " +"additional path (for example, http://192.168.1.1:8000/test)." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:61 +msgid "" +"All vector layers, PostGIS, raster layers, styles will list as child " +"resources if identifier is resource group. In other case this will be a " +"separate layer." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:70 +msgid ":copy-config:`NGW_USERPWD`" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:89 +msgid ":copy-config:`NGW_JSON_DEPTH`" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:91 +msgid "" +"The depth of json response that can be parsed. If depth is greater than " +"this value, parse error occurs." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:110 +msgid "" +"If the :oo:`NATIVE_DATA` open option is set to YES, the *extensions* json" +" object will store as a serialized json object in the NativeData property" +" of the OGRFeature object (and \"application/json\" in the " +"NativeMediaType property). If writing OGRFeature has NativeMediaType " +"property set to \"application/json\" and its NativeData property set to " +"serialized json object the new NGW feature *extensions* json object will " +"fill from this json object." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:118 +msgid "" +"Extensions json object structure see in `NextGIS Web API documentation " +"<https://docs.nextgis.com/docs_ngweb_dev/doc/developer/resource.html#feature>`__" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:124 +msgid "" +"NextGIS Web supports only one geometry column. Default spatial reference " +"is Web Mercator (EPSG:3857). The following geometry types are available:" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:127 +msgid "POINT" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:128 +msgid "LINESTRING" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:129 +msgid "POLYGON" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:130 +msgid "MULTIPOINT" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:131 +msgid "MULTILINESTRING" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:132 +msgid "MULTIPOLYGON" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:134 +msgid "Geometry with Z value also supported." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:137 +msgid "Field data types" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:139 +msgid "NextWeb supports only following field types:" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:145 +msgid "OFTDate" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:146 +msgid "OFTTime" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:147 +msgid "OFTDateTime" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:152 +msgid "" +"Features can retrieved from NextGIS Web by chunks if supported by server " +"(available since NextGIS Web 3.1). The chunk size can be altered with the" +" :config:`NGW_PAGE_SIZE` configuration option or :oo:`PAGE_SIZE` open " +"option." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:160 +msgid "" +"Datasource and layers creation and deletion is possible. Write support is" +" only enabled when the datasource is opened in update mode and user has " +"appropriate permissions. Vector and PostGIS layers insert and update " +"operations are cached if :oo:`BATCH_SIZE` is greater 0. Delete operation " +"executes immediately." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:209 +#: ../../source/drivers/vector/tiledb.rst:140 +#: ../../source/drivers/vector/vdv.rst:49 +msgid "" +"|about-dataset-creation-options| The following dataset creation options " +"are available:" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:241 +msgid "Whether to store the json *extensions* key in feature native data." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:281 +msgid "" +"NextGIS Web metadata are supported in datasource, vector, PostGIS, raster" +" layers and styles. Metadata are stored at specific domain \"NGW\". " +"NextGIS Web supported metadata are strings and numbers. Metadata keys " +"with decimal numbers will have suffix **.d** and for real numbers - " +"**.f**. To create new metadata item, add new key=value pair in NGW domain" +" using the *SetMetadataItem* function and appropriate suffix. During " +"transferring to NextGIS Web, suffix will be omitted. You must ensure that" +" numbers correctly transform from string to number." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:298 +msgid "" +"Vector layer field properties (alias, identifier, label field, grid " +"visibility) map to layer metadata the following way:" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:301 +msgid "field alias -> FIELD_{field number}_ALIAS (for example FIELD_0_ALIAS)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:302 +msgid "identifier -> FIELD_{field number}_ID (for example FIELD_0_ID)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:303 +msgid "" +"label field -> FIELD_{field number}_LABEL_FIELD (for example " +"FIELD_0_LABEL_FIELD)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:305 +msgid "" +"grid visibility -> FIELD_{field number}_GRID_VISIBILITY (for example " +"FIELD_0_GRID_VISIBILITY)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:308 +msgid "" +"Starting from GDAL 3.3 field alias can be set/get via " +"`SetAlternativeName` and `GetAlternativeNameRef`." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:312 +#: ../../source/drivers/vector/vfk.rst:152 +msgid "Filters" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:314 +msgid "" +"Vector and PostGIS layers support SetIgnoredFields method. When this " +"method executes any cached features will be freed." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:317 +msgid "" +"Vector and PostGIS layers support SetAttributeFilter and SetSpatialFilter" +" methods. The attribute filter will evaluate at server side if condition " +"is one of following comparison operators:" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:321 +msgid "greater (>)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:322 +msgid "lower (<)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:323 +msgid "greater or equal (>=)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:324 +msgid "lower or equal (<=)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:325 +msgid "equal (=)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:326 +msgid "not equal (!=)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:327 +msgid "LIKE SQL statement (for strings compare)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:328 +msgid "ILIKE SQL statement (for strings compare)" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:330 +msgid "" +"Also only AND operator without brackets supported between comparison. For" +" example," +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:340 +msgid "In other cases attribute filter will evaluate on client side." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:342 +msgid "You can set attribute filter using NextGIS Web native format. For example," +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:349 +msgid "" +"Don't forget to add 'NGW:' perefix to where clause and 'fld\\_' prefix to" +" field name." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:352 +msgid "" +"Dataset supports ExecuteSQL method. Only the following queries are " +"supported:" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:355 +msgid "DELLAYER: layer_name; - delete layer with layer_name." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:356 +msgid "DELETE FROM layer_name; - delete any features from layer with layer_name." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:358 +msgid "DROP TABLE layer_name; - delete layer with layer_name." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:359 +msgid "ALTER TABLE src_layer RENAME TO dst_layer; - rename layer." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:360 +msgid "" +"SELECT field_1,field_2 FROM src_layer WHERE field_1 = 'Value 1' AND " +"field_2 = 'Value 2';" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:363 +msgid "" +"In SELECT statement field list or asterisk can be provided. The WHERE " +"clause has same limitations as SetAttributeFilter method input." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:369 +msgid "Read datasource contents (1730 is resource group identifier):" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:375 +msgid "" +"Read layer details (`1730` is resource group identifier, `Parks` is " +"vecror layer name):" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:382 +msgid "" +"Creating and populating a vector layer from a shapefile in existing " +"resource group with identifier 1730. New vector layer name will be \"some" +" new name\":" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:390 +msgid "" +"The `-update` key is mandatory, otherwise the destination datasource will" +" silently delete. The `-t_srs EPSG:3857` key is mandatory because vector " +"layers spatial reference in NextGIS Web can be only in EPSG:3857." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:395 +msgid "" +"The `-doo \"BATCH_SIZE=100\"` key is recommended for speed up feature " +"transferring." +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:397 +msgid "" +"Creating and populating a vector layer from a shapefile in new resource " +"group with name \"new group\" and parent identifier 1730. New vector " +"layer name will be \"some new name\":" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:408 +msgid ":ref:`Raster side of the driver <raster.ngw>`" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:409 +msgid "" +"`NextGIS Web documentation " +"<https://docs.nextgis.com/docs_ngweb/source/toc.html>`__" +msgstr "" + +#: ../../source/drivers/vector/ngw.rst:411 +msgid "" +"`NextGIS Web for developers " +"<https://docs.nextgis.com/docs_ngweb_dev/doc/toc.html>`__" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:10 +msgid "" +"The National Transfer Format, mostly used by the UK Ordnance Survey, is " +"supported for read access." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:13 +msgid "" +"This driver treats a directory as a dataset and attempts to merge all the" +" .NTF files in the directory, producing a layer for each type of feature " +"(but generally not for each source file). Thus a directory containing " +"several Landline files will have three layers (LANDLINE_POINT, " +"LANDLINE_LINE and LANDLINE_NAME) regardless of the number of landline " +"files." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:20 +msgid "" +"NTF features are always returned with the British National Grid " +"coordinate system. This may be inappropriate for NTF files written by " +"organizations other than the UK Ordnance Survey." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:34 +msgid "" +"`General UK NTF Information " +"<https://web.archive.org/web/20130730111701/http://home.gdal.org/projects/ntf/index.html>`__" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:38 +msgid "Implementation Notes" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:41 +msgid "Products (and Layers) Supported" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:104 +msgid "" +"The dataset as a whole will also have a FEATURE_CLASSES layer containing " +"a pure table relating FEAT_CODE numbers with feature class names " +"(FC_NAME). This applies to all products in the dataset. A few layer types" +" (such as the Code Point, and Address Point products) don't include " +"feature classes. Some products use features classes that are not defined " +"in the file, and so they will not appear in the FEATURE_CLASSES layer." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:112 +msgid "Product Schemas" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:114 +msgid "" +"The approach taken in this reader is to treat one file, or a directory of" +" files as a single dataset. All files in the dataset are scanned on open." +" For each particular product (listed above) a set of layers are created; " +"however, these layers may be extracted from several files of the same " +"product." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:120 +msgid "" +"The layers are based on a low level feature type in the NTF file, but " +"will generally contain features of many different feature codes " +"(FEAT_CODE attribute). Different features within a given layer may have a" +" variety of attributes in the file; however, the schema is established " +"based on the union of all attributes possible within features of a " +"particular type (i.e. POINT) of that product family (i.e. OSCAR Network)." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:128 +msgid "" +"If an NTF product is read that doesn't match one of the known schema's it" +" will go through a different generic handler which has only layers of " +"type GENERIC_POINT and GENERIC_LINE. The features only have a FEAT_CODE " +"attribute." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:133 +msgid "" +"Details of what layers of what products have what attributes can be found" +" in the NTFFileReader::EstablishLayers() method at the end of " +"ntf_estlayers.cpp. This file also contains all the product specific " +"translation code." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:139 +msgid "Special Attributes" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:180 +msgid "Generic Products" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:182 +msgid "" +"In situations where a file is not identified as being part of an existing" +" known product it will be treated generically. In this case the entire " +"dataset is scanned to establish what features have what attributes. " +"Because of this, opening a generic dataset can be much slower than " +"opening a recognised dataset. Based on this scan a list of generic " +"features (layers) are defined from the following set:" +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:199 +msgid "" +"Generic products are primarily handled by the ntf_generic.cpp module " +"whereas specific products are handled in ntf_estlayers.cpp." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:202 +msgid "" +"Because some data products (OSNI datasets) not from the Ordnance Survey " +"were found to have record groups in unusual orders compared to what the " +"UK Ordnance Survey does, it was found necessary to cache all the records " +"of level 3 and higher generic products, and construct record groups by id" +" reference from within this cache rather than depending on convenient " +"record orderings. This is accomplished by the NTFFileReader \"indexing\" " +"capability near the bottom of ntffilereader.cpp. Because of this in " +"memory indexing accessing generic datasets can be much more memory " +"intensive than accessing known data products, though it isn't necessary " +"for generic level 1 and 2 products." +msgstr "" + +#: ../../source/drivers/vector/ntf.rst:213 +msgid "" +"It is possible to force a known product to be treated as generic by " +"setting the FORCE_GENERIC option to \"ON\" using " +"OGRNTFDataSource::SetOptionsList() as is demonstrated in ntfdump.cpp. " +"This may also be accomplished from outside OGR applications by setting " +"the OGR_NTF_OPTIONS environment variable to \"FORCE_GENERIC=ON\"." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:8 +msgid "OAPIF" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:12 +msgid "" +"This driver can connect to a OGC API - Features service. It assumes that " +"the service supports OpenAPI 3.0/JSON/GeoJSON encoding for respectively " +"API description, feature collection metadata and feature collection data." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:18 +msgid "" +"In versions prior to GDAL 3.1, this driver was called the WFS3 driver, " +"and only supported draft versions of the specification." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:29 +msgid "" +"The syntax to open a OGC API - Features datasource is : " +"*OAPIF:http://path/to/OAPIF/endpoint*" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:32 +msgid "where endpoint is the landing page or a the path to collections/{id}." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:34 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if OAPIF`` option to command " +"line utilities accepting it, or ``OAPIF`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed URL without the ``OAPIF:`` prefix." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:40 +msgid "Layer schema" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:42 +msgid "" +"OGR needs a fixed schema per layer, but OGC API - Features Core doesn't " +"impose fixed schema. The driver will use the XML schema or JSON schema " +"pointed by the \"describedby\" relationship of a collection, if it " +"exists. The driver will also retrieve the first page of features (using " +"the selected page) and establish a schema from this." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:53 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server. In OGC API - Features Core, only a subset of attributes " +"allowed by the server can be queried for equalities, potentially combined" +" with a AND logical operator. More complex requests will be partly or " +"completely evaluated on client-side." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:59 +msgid "Rectangular spatial filtering is forward to the server as well." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:64 +msgid "" +"Starting with GDAL 3.7, the driver supports the `OGC API - Features - " +"Part 2: Coordinate Reference Systems by Reference " +"<https://docs.ogc.org/is/18-058/18-058.html>`__ extension. If a server " +"reports a storageCRS property, that property will be used to set the CRS " +"of the OGR layer. Otherwise the default will be OGC:CRS84 (WGS84 " +"longitude, latitude). As most all OGR drivers, the OAPIF driver will " +"report the SRS and geometries, and expect spatial filters, in the \"GIS-" +"friendly\" order, with longitude/easting first (X component), " +"latitude/northing second (Y component), potentially overriding the axis " +"order of the authority." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:74 +msgid "" +"The CRS of layers can also be controlled with the :oo:`CRS` or " +":oo:`PREFERRED_CRS` open options documented below." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:115 +msgid "" +"Set to YES to ignore the XML Schema or JSON schema that may be offered by" +" the server." +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:147 +msgid "Listing the types of a OGC API - Features server :" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:157 +msgid "Listing the summary information of a OGC API - Features layer :" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:211 +msgid "" +"Filtering on a property (depending on if the server exposes filtering " +"capabilities of the properties, part or totally of the filter might be " +"evaluated on client side)" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:244 +#: ../../source/drivers/vector/openfilegdb.rst:40 +#: ../../source/drivers/vector/osm.rst:179 +msgid "Spatial filtering" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:279 +msgid "" +"`\"OGC API - Features - Part 1: Core\" Standard " +"<http://docs.opengeospatial.org/is/17-069r3/17-069r3.html>`__" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:281 +msgid "" +"`\"OGC API - Features - Part 2: Coordinate Reference Systems by " +"Reference\" Standard <https://docs.ogc.org/is/18-058/18-058.html>`__" +msgstr "" + +#: ../../source/drivers/vector/oapif.rst:283 +msgid ":ref:`WFS (1.0,1.1,2.0) driver documentation <vector.wfs>`" +msgstr "" + +#: ../../source/drivers/vector/oci.rst:6 +msgid "OCI" +msgstr "" + +#: ../../source/drivers/vector/oci.rst:10 +msgid "" +"This driver supports reading and writing data in Oracle Spatial (8.1.7 or" +" later) Object-Relational format. The Oracle Spatial driver is not " +"normally built into OGR, but may be built in on platforms where the " +"Oracle client libraries are available." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:15 +#, python-format +msgid "" +"When opening a database, its name should be specified in the form " +"\"OCI:userid/password@database_instance:table,table\". The list of tables" +" is optional. The database_instance portion may be omitted when accessing" +" the default local database instance. See the `Oracle Help Center " +"<https://docs.oracle.com/search/?q=oci%20driver>`_ for more information " +"about the OCI driver." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:22 +msgid "" +"If the list of tables is not provided, then all tables appearing in " +"ALL_SDO_GEOM_METADATA will be treated by OGR as layers with the table " +"names as the layer names. Non-spatial tables or spatial tables not listed" +" in the ALL_SDO_GEOM_METADATA view [#]_ are not accessible unless " +"explicitly listed in the datasource name. Even in databases where all " +"desired layers are in the ALL_SDO_GEOM_METADATA view, it may be desirable" +" to list only the tables to be used as this can substantially reduce " +"initialization time in databases with many tables." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:31 +msgid "" +"If the table has an integer column called OGR_FID it will be used as the " +"feature id by OGR (and it will not appear as a regular attribute). When " +"loading data into Oracle Spatial OGR will always create the OGR_FID " +"field." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:36 +msgid "" +"When reading data from one or more views, the view names should be " +"specified in the form " +"\"OCI:userid/password@database_instance:view,view\". What is written " +"above regarding tables, applies to views as well." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:41 +msgid "" +"It is the database user that is responsible for updating the " +"ALL_SDO_GEOM_METADATA view, by inserting an appropriate row into the " +"USER_SDO_GEOM_METADATA view. This is why it is possible that the table " +"you want to read from is not listed in the ALL_SDO_GEOM_METADATA." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:55 +msgid "SQL Issues" +msgstr "" + +#: ../../source/drivers/vector/oci.rst:57 +msgid "" +"By default, the Oracle driver passes SQL statements directly to Oracle " +"rather than evaluating them internally when using the ExecuteSQL() call " +"on the OGRDataSource, or the -sql command option to ogr2ogr. Attribute " +"query expressions are also passed through to Oracle." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:62 +msgid "" +"As well two special commands are supported via the ExecuteSQL() " +"interface. These are \"**DELLAYER:<table_name>**\" to delete a layer, and" +" \"**VALLAYER:<table_name>**\" to apply the SDO_GEOM.VALIDATE_GEOMETRY() " +"check to a layer. Internally these pseudo-commands are translated into " +"more complex SQL commands for Oracle." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:68 +msgid "" +"It is also possible to request the driver to handle SQL commands with " +":ref:`OGR SQL <ogr_sql_dialect>` engine, by passing **\"OGRSQL\"** string" +" to the ExecuteSQL() method, as name of the SQL dialect." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:75 +msgid "" +"The type recognition logic is currently somewhat impoverished. No effort " +"is made to preserve real width information for integer and real fields." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:78 +msgid "" +"Various types such as objects, and BLOBs in Oracle will be completely " +"ignored by OGR." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:80 +msgid "" +"Currently the OGR transaction semantics are not properly mapped onto " +"transaction semantics in Oracle." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:82 +msgid "" +"If an attribute called OGR_FID exists in the schema for tables being " +"read, it will be used as the FID. Random (FID based) reads on tables " +"without an identified (and indexed) FID field can be very slow. To force " +"use of a particular field name the :config:`OCI_FID` configuration option" +" (e.g. environment variable) can be set to the target field name." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:88 +msgid "" +"Curved geometry types are converted to linestrings or linear rings in six" +" degree segments when reading. The driver has no support for writing " +"curved geometries." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:91 +msgid "" +"There is no support for point cloud (SDO_PC), TIN (SDO_TIN) and " +"annotation text data types in Oracle Spatial." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:93 +msgid "" +"It might be necessary to define the environment variable NLS_LANG to " +"\"American_America.UTF8\" to avoid issues with floating point numbers " +"being truncated to integer on non-English environments." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:96 +msgid "" +"For developers: when running the driver under the memory error detection " +"tool Valgrind, specifying the database_instance, typically to localhost, " +"or with the TWO_TASK environment variable seems to be compulsory, " +"otherwise \"TNS:permission denied\" errors will be reported)" +msgstr "" + +#: ../../source/drivers/vector/oci.rst:101 +msgid "" +"The logic for finding the specified table or view first checks whether a " +"table with the given name exists, then a view, and then tries again with " +"quoted names. This may result in one or more errors of the following type" +" written to the output: \"ORA-04043: object <object_name> does not " +"exist\", even if the object actually is found later on." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:111 +msgid "" +"The Oracle Spatial driver does not support creation of new datasets " +"(database instances), but it does allow creation of new layers within an " +"existing database." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:115 +msgid "" +"Upon closing the OGRDataSource newly created layers will have a spatial " +"index automatically built. At this point the USER_SDO_GEOM_METADATA table" +" will also be updated with bounds for the table based on the features " +"that have actually been written. One consequence of this is that once a " +"layer has been loaded it is generally not possible to load additional " +"features outside the original extents without manually modifying the " +"DIMINFO information in USER_SDO_GEOM_METADATA and rebuilding the spatial " +"index." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:292 +msgid "Layer Open Options" +msgstr "" + +#: ../../source/drivers/vector/oci.rst:316 +msgid "" +"Simple translation of a shapefile into Oracle. The table 'ABC' will be " +"created with the features from abc.shp and attributes from abc.dbf." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:323 +#: ../../source/drivers/vector/pg.rst:490 +msgid "" +"This second example loads a political boundaries layer from VPF (via the " +":ref:`OGDI driver <vector.ogdi>`), and renames the layer from the cryptic" +" OGDI layer name to something more sensible. If an existing table of the " +"desired name exists it is overwritten." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:334 +msgid "" +"This example shows using ogrinfo to evaluate an SQL query statement " +"within Oracle. More sophisticated Oracle Spatial specific queries may " +"also be used via the -sql commandline switch to ogrinfo." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:342 +msgid "This example shows hows to list information about an Oracle view." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:348 +msgid "" +"This example shows hows to convert certain columns from an Oracle view to" +" a GeoPackage file, explicitly assigning the layer name and the " +"coordinate reference system, and converting timestamps to UTC." +msgstr "" + +#: ../../source/drivers/vector/oci.rst:359 +msgid "" +"I would like to thank `SRC, LLC <http://www.extendthereach.com/>`__ for " +"its financial support of the development of this driver." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:4 +msgid "Open Design Alliance - ODA Platform" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:6 +msgid "" +"ODA Platform (previously named Teigha) is required to enable GDAL support" +" for reading AutoCAD DWG and Microstation DGN v8 files. GDAL/OGR must be " +"built with ODA support in order to enable these drivers." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:10 +msgid "ODA required products" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:12 +msgid "" +"ODA Platform includes several SDK. Drawings SDK provides access to all " +"data in .dwg and .dgn through an object-oriented API. It is required to " +"compile GDAL. Since Kernel SDK is required by all products, these two " +"products must be downloaded:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:15 +msgid "Kernel" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:16 +msgid "Drawings" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:18 +msgid "" +"These libraries are not publicly available. You have to became a member " +"to get access to the libraries. Upon authentication the libraries are " +"available from: `ODA Member Downloads " +"<https://www.opendesign.com/members/memberfiles>`__" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:23 +msgid "Get the libraries" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:25 +msgid "" +"To selected the appropriate files to download, consider the following ODA" +" name conventions (for Linux):" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:27 +msgid "lnx - Linux" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:28 +msgid "X86, X64 - indicates X86 or X64 platform" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:29 +msgid "4.4, 4.7, 4.8, 4.9, 5.2, 5.3, 6.3, 7.2, 8.3 - GCC versions" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:30 +msgid "dll - indicates a shared library version" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:31 +msgid "pic - compiled with Position Independent Code option" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:33 +msgid "" +"ODA archives also contains a release suffix in order to distinguish " +"between releases, like 21.2 or 21.6." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:35 +msgid "" +"To download the required files for Linux, the following files could be " +"downloaded:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:37 +msgid "`Kernel_lnxX64_7.2dll_21.6.tar.gz`" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:38 +msgid "`Drawings_lnxX64_7.2dll_21.6.tar.gz`" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:40 +msgid "In this example, the files names are:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:42 +msgid "`lnx` for Linux" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:43 +msgid "`X64` for X64 architecture" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:44 +msgid "`7.2` for gcc 7.2" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:45 +msgid "`dll` for shared library version" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:46 +msgid "`21.6` ODA 2021 release, build 6" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:49 +msgid "Compiling the libraries" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:51 +msgid "The libraries must be merged before compiling." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:60 +msgid "" +"To compile, an activation key is required. It can be requested from ODA " +"Products Activation. The activation key must be copied to " +"`ThirdParty/activation/`." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:67 +msgid "Compile the ODA libraries with:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:75 +msgid "" +"Make sure your gcc major version matches ODA libs gcc version. On Ubuntu," +" for example, you can install different gcc/g++ versions, like 7, 8 and " +"9. Switch between them with:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:83 +msgid "ODA libraries path" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:85 +msgid "" +"After compiling ODA, the resulting libs are in a non standard search " +"path. There is no `make install` included to copy the libraries to a " +"standard location. This might be an issue." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:89 +msgid "" +"You have different alternative options to compile and run GDAL/OGR with " +"ODA:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:91 +msgid "copy the ODA libraries to a standard location" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:92 +msgid "" +"set LD_LIBRARY_PATH (like " +"`LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/jgr/dev/cpp/ODA21.6/base_7.2/bin/lnxX64_7.2dll`)." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:93 +msgid "" +"Adding ODA folder to the system library path (`echo " +"\"/home/jgr/dev/cpp/ODA21.6/base_7.2/bin/lnxX64_7.2dll\" | sudo tee -a " +"/etc/ld.so.conf.d/z_gdal-ODA.conf`)" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:94 +msgid "" +"Setting a run time path (`rpath`) when compiling GDAL (like " +"`LDFLAGS=\"-Wl,-rpath=/home/jgr/dev/cpp/ODA21.6/base_7.2/bin/lnxX64_7.2dll\"`)." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:97 +msgid "ODA library names" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:99 +msgid "" +"Some ODA library names do not conform the usual Linux standard `lib*.so`." +" If you don't use `rpath`, for the other alternatives listed above, you " +"might have to create symbolic links from the actual names. Example:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:111 +msgid "Check with `ldconfig -v` if all ODA libraries are now visible." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:115 +msgid "Compiling GDAL" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:117 +msgid "" +"After compiling ODA libraries, GDAL can be build using two additional " +"options:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:119 +msgid "`--with-teigha=/home/jgr/dev/cpp/ODA21.6/base_7.2`" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:120 +msgid "`--with-teigha-plt=lnxX64_7.2dll`" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:122 +msgid "" +"The value of `--with-teigha` is the full path of the folder where the " +"libraries were merged and compiled." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:124 +msgid "" +"The value of `--with-teigha-plt` must match the platform name used by " +"ODA. The platform name is the folder name under `Platforms`:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:132 +msgid "GDAL compilation" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:134 +msgid "" +"Use your own GDAL build configuration and add the previous mentioned " +"options. After running `configure`, make sure that `Teigha (DWG and " +"DGNv8)` support is configured." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:136 +msgid "As an example, compiling GDAL can be:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:151 +msgid "" +"We added `LDFLAGS=\"-L/usr/lib/x86_64-linux-gnu\"` to use system libs " +"over ODA's `libpcre`, `libcurl`, etc." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:154 +msgid "Testing" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:156 +msgid "" +"After compiling GDAL, you can check if the new drivers `DGNV8` and `DWG` " +"are supported with:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:167 +msgid "" +"If a file is DGNv8, you will see that driver in action when opening the " +"file:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:177 +msgid "Troubleshooting" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:179 +msgid "" +"If you find linking errors, you can set `LD_LIBRARY_PATH` or `LDFLAGS` " +"environment variables to make sure you are able to get the ODA libraries " +"from their location." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:181 +msgid "Use `ldconfig -v` to check if ODA's library folder is listed." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:183 +msgid "For example, you can try:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:190 +msgid "You can force a run time location (with `rpath`) with:" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:197 +msgid "Adjust these settings, according to your build environment." +msgstr "" + +#: ../../source/drivers/vector/oda.rst:202 +msgid "`Introducing the ODA Platform <https://www.opendesign.com/products>`__" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:203 +msgid ":ref:`AutoCAD DWG <vector.dwg>`" +msgstr "" + +#: ../../source/drivers/vector/oda.rst:204 +msgid ":ref:`Microstation DGN v8 <vector.dgnv8>`" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:6 +msgid "ODBC" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:10 +msgid "" +"OGR optionally supports spatial and non-spatial tables accessed via ODBC." +" ODBC is a generic access layer for access to many database systems, and " +"data that can be represented as a database (collection of tables). ODBC " +"support is potentially available on Unix and Windows platforms, but is " +"only included in unix builds by special configuration options." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:17 +msgid "" +"ODBC datasources are accessed using a datasource name of the form " +"**ODBC:\\ userid/password\\ @\\ dsn,\\ " +"schema.tablename(geometrycolname),...:srs_tablename(sridcolumn,srtextcolumn)**." +" With optional items dropped the following are also acceptable:" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:21 +msgid "**ODBC:\\ userid/password\\ @\\ dsn**" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:22 +msgid "**ODBC:\\ userid\\ @\\ dsn,\\ table_list**" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:23 +msgid "**ODBC:\\ dsn,\\ table_list**" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:24 +msgid "**ODBC:\\ dsn**" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:25 +msgid "**ODBC:\\ dsn,\\ table_list:srs_tablename**" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:27 +msgid "" +"The **dsn** is the ODBC Data Source Name. Normally ODBC datasources are " +"setup using an ODBC Administration tool, and assigned a DSN. That DSN is " +"what is used to access the datasource." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:31 +msgid "" +"By default the ODBC searches for GEOMETRY_COLUMNS table. If found it is " +"used to identify the set of spatial tables that should be treated as " +"layers by OGR. If not found, then all tables in the datasource are " +"returned as non-spatial layers. However, if a table list (a list of comma" +" separated table names) is provided, then only those tables will be " +"represented as layers (non-spatial). Fetching the full definition of all " +"tables in a complicated database can be quite time consuming, so the " +"ability to restrict the set of tables accessed is primarily a performance" +" issue." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:41 +msgid "" +"If the GEOMETRY_COLUMNS table is found, it is used to select a column to " +"be the geometry source. If the tables are passed in the datasource name, " +"then the geometry column associated with a table can be included in round" +" brackets after the tablename. It is currently a hardcoded assumption " +"that the geometry is in Well Known Binary (WKB) format if the field is " +"binary, or Well Known Text (WKT) otherwise. The GEOMETRY_COLUMNS table " +"should have at least the columns F_TABLE_NAME, F_GEOMETRY_COLUMN and " +"GEOMETRY_TYPE." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:50 +msgid "" +"If the table has a geometry column, and has fields called XMIN, YMIN, " +"XMAX and YMAX then direct table queries with a spatial filter accelerate " +"the spatial query. The XMIN, YMIN, XMAX and YMAX fields should represent " +"the extent of the geometry in the row in the tables coordinate system." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:55 +msgid "" +"By default, SQL statements are passed directly to the underlying database" +" engine. It's also possible to request the driver to handle SQL commands " +"with the :ref:`OGR SQL <ogr_sql_dialect>` engine, by passing " +"**\"OGRSQL\"** string to the ExecuteSQL() method, as name of the SQL " +"dialect." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:83 +msgid "Access Databases (.MDB) support" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:85 +msgid "" +"On Windows provided that the \"Microsoft Access Driver (\\*.mdb)\" ODBC " +"driver is installed, non-spatial MS Access Databases (not Personal " +"Geodabases or Geomedia databases) can be opened directly by their " +"filenames." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:90 +msgid "" +"On Linux opening non-spatial MS Access Databases using the ODBC driver is" +" possible via installation of unixODBC and mdbtools. See :ref:`MDB " +"<vector.pgeo>` for instructions on how to enable this." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:94 +msgid "" +"The driver supports either .mdb or .accdb extensions for Microsoft Access" +" databases. Additionally, it also supports opening files with the ESRI " +".style database extension (which is just an alias for the .mdb file " +"extension)." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:102 +msgid "" +"Currently the ODBC OGR driver is read-only, so new features, tables and " +"datasources cannot normally be created by OGR applications. This " +"limitation may be removed in the future." +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:109 +msgid "" +"`MSDN ODBC API Reference <http://msdn.microsoft.com/en-" +"us/library/ms714562(VS.85).aspx>`__" +msgstr "" + +#: ../../source/drivers/vector/odbc.rst:111 +msgid ":ref:`PGeo driver <vector.pgeo>`" +msgstr "" + +#: ../../source/drivers/vector/ods.rst:4 +msgid "ODS - Open Document Spreadsheet" +msgstr "" + +#: ../../source/drivers/vector/ods.rst:6 +msgid "ODS" +msgstr "" + +#: ../../source/drivers/vector/ods.rst:10 +msgid "" +"This driver can read, write and update spreadsheets in Open Document " +"Spreadsheet format, used by applications like OpenOffice / LibreOffice / " +"KSpread / etc..." +msgstr "" + +#: ../../source/drivers/vector/ods.rst:17 +#: ../../source/drivers/vector/xls.rst:16 +#: ../../source/drivers/vector/xlsx.rst:19 +msgid "" +"Each sheet is presented as a OGR layer. No geometry support is available " +"directly (but you may use the OGR VRT capabilities for that)." +msgstr "" + +#: ../../source/drivers/vector/ods.rst:20 +msgid "Note 1 : spreadsheets with passwords are not supported." +msgstr "" + +#: ../../source/drivers/vector/ods.rst:22 +msgid "" +"Note 2 : when updating an existing document, all existing styles, " +"formatting, formulas and other concepts (charts, drawings, macros, ...) " +"not understood by OGR will be lost : the document is re-written from " +"scratch from the OGR data model." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:6 +msgid "OGDI" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:10 +msgid "" +"OGDI vector support is optional in OGR, and is normally only configured " +"if OGDI is installed on the build system. If available OGDI vectors are " +"supported for read access for the following family types:" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:15 +msgid "Line" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:16 +msgid "Area" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:17 +msgid "" +"Text (Currently returned as points with the text in the \"text\" " +"attribute)" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:20 +msgid "OGDI can (among other formats) read VPF products, such as DCW and VMAP." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:22 +msgid "" +"If an OGDI gltp url is opened directly the OGDI 3.1 capabilities for the " +"driver/server are queried to get a list of layers. One OGR layer is " +"created for each OGDI family available for each layer in the datastore. " +"For drivers such as VRF this can result in a lot of layers. Each of the " +"layers has an OGR name based on the OGDI name plus an underscore and the " +"family name. For instance a layer might be called " +"**watrcrsl@hydro(*)_line** if coming out of the VRF driver. (layer names " +"can be simplified with :config:`OGR_OGDI_LAUNDER_LAYER_NAMES=YES`)" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:31 +msgid "" +"Alternatively to accessing all the layers in a datastore, it is possible " +"to open a particular layer using a customized filename consisting of the " +"regular GLTP URL to which you append the layer name and family type " +"(separated by colons). This mechanism must be used to access layers of " +"pre OGDI 3.1 drivers as before OGDI 3.1 there was no regular way to " +"discover available layers in OGDI." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:42 +msgid "" +"Where <layer_name> is the OGDI Layer name, and <family> is one of: " +"\"line\", \"area\", \"point\", or \"text\"." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:45 +msgid "" +"OGDI coordinate system information is supported for most coordinate " +"systems. A warning will be produced when a layer is opened if the " +"coordinate system cannot be translated." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:49 +msgid "There is no update or creation support in the OGDI driver." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:57 +msgid "Error handling" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:59 +msgid "" +"Starting with GDAL 2.2 and OGDI > 3.2.0beta2, if the OGDI_STOP_ON_ERROR " +"environment variable is set to NO, some errors can be gracefully " +"recovered by OGDI (in VPF driver). They will still be caught by GDAL and " +"emitted as regular GDAL errors." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:64 +msgid "" +"Note: be aware that this is a work in progress. Not all recoverable " +"errors can be recovered, and some errors might be recovered silently." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:84 +msgid "Usage example 'ogrinfo':" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:90 +msgid "" +"In the dataset name 'gltp:/vrf/usr4/mpp1/v0eur/vmaplv0/eurnasia' the " +"gltp:/vrf part is not really in the filesystem, but has to be added. The " +"VPF data was at /usr4/mpp1/v0eur/. The 'eurnasia' directory should be at " +"the same level as the dht. and lat. files. The 'hydro' reference is a " +"subdirectory of 'eurnasia/' where watrcrsl.\\* is found." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:96 +msgid "Usage examples VMAP0 to SHAPE conversion with 'ogr2ogr':" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:103 +msgid "" +"An OGR SQL query against a VMAP dataset. Again, note the careful quoting " +"of the layer name." +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:114 +msgid "`OGDI.SourceForge.Net <http://ogdi.sourceforge.net/>`__" +msgstr "" + +#: ../../source/drivers/vector/ogdi.rst:115 +msgid "`VMap0 Coverages <http://www.terragear.org/docs/vmap0/coverage.html>`__" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:10 +msgid "" +"The OpenFileGDB driver provides read, write and update access to vector " +"layers of File Geodatabases (.gdb directories) created by ArcGIS 10 and " +"above (it has also read-only support for ArcGIS 9.x geodatabases). The " +"dataset name must be the directory/folder name, and it must end with the " +".gdb extension." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:19 +msgid "" +"A specific .gdbtable file (including \"system\" tables) can also be " +"opened directly." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:22 +msgid "Curve in geometries are supported with GDAL >= 2.2." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:24 +msgid "Write and update capabilities are supported since GDAL >= 3.6" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:26 +msgid "" +"The driver also supports :ref:`raster layers<raster.openfilegdb>` since " +"GDAL 3.7" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:33 +msgid "3.6" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:42 +msgid "" +"Since GDAL 3.2, the driver can use the native .spx spatial indices for " +"spatial filtering." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:45 +msgid "" +"In earlier versions, it uses the minimum bounding rectangle included at " +"the beginning of the geometry blobs to speed up spatial filtering. By " +"default, it also builds on the fly a in-memory spatial index during the " +"first sequential read of a layer. Following spatial filtering operations " +"on that layer will then benefit from that spatial index. The building of " +"this in-memory spatial index can be disabled by setting the " +":config:`OPENFILEGDB_IN_MEMORY_SPI` configuration option to NO." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:56 +msgid "" +"SQL statements are run through the OGR SQL engine. When attribute indexes" +" (.atx files) exist, the driver will use them to speed up WHERE clauses " +"or SetAttributeFilter() calls." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:63 +msgid "" +"\"GetLayerDefinition a_layer_name\" and \"GetLayerMetadata a_layer_name\"" +" can be used as special SQL requests to get respectively the definition " +"and metadata of a FileGDB table as XML content (only available in " +"Geodatabases created with ArcGIS 10 or above)" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:68 +msgid "" +"The \"CREATE INDEX idx_name ON layer_name(field_name)\" SQL request can " +"be used to create an attribute index. idx_name must have 16 characters or" +" less, start with a letter and contain only alphanumeric characters or " +"underscore." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:72 +msgid "" +"The \"RECOMPUTE EXTENT ON layer_name\" SQL request can be used to trigger" +" an update of the layer extent in layer metadata. This is useful when " +"updating or deleting features that modify the general layer extent." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:76 +msgid "" +"The \"REPACK\" or \"REPACK layer_name\" SQL requests can be used " +"respectively to compact the whole database or a given layer. This is " +"useful when doing editions (updates or feature deletions) that may leave " +"holes in .gdbtable files. The REPACK command causes the .gdbtable to be " +"rewritten without holes. Note that compaction does not involve extent " +"recomputation." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:149 +msgid "" +"On reading, this information is exposed in the ALIAS_NAME layer metadata " +"item (GDAL >= 3.8)." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:170 +msgid "" +"**XYTOLERANCE, ZTOLERANCE, MTOLERANCE**\\=value: These parameters control" +" the snapping tolerance used for advanced ArcGIS features like network " +"and topology rules. They won't effect any OGR operations, but they will " +"by used by ArcGIS. The units of the parameters are the units of the " +"coordinate reference system." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:181 +msgid "" +"**XORIGIN, YORIGIN, ZORIGIN, MORIGIN, XYSCALE, ZSCALE, ZORIGIN**\\=value:" +" These parameters control the `coordinate precision grid " +"<http://help.arcgis.com/en/sdk/10.0/java_ao_adf/conceptualhelp/engine/index.html#//00010000037m000000>`__" +" inside the file geodatabase. The dimensions of the grid are determined " +"by the origin, and the scale. The origin defines the location of a " +"reference grid point in space. The scale is the reciprocal of the " +"resolution. So, to get a grid with an origin at 0 and a resolution of " +"0.001 on all axes, you would set all the origins to 0 and all the scales " +"to 1000." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:239 +msgid "64-bit integer field support" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:243 +msgid "" +"On creation, 64-bit integer field support requires setting the " +":lco:`TARGET_ARCGIS_VERSION` layer creation option to " +"``ARCGIS_PRO_3_2_OR_LATER``. Note that Esri `recommends " +"<https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview" +"/arcgis-field-data-" +"types.htm#ESRI_SECTION2_8BF2454C879941258DC44AF6BB31F386>`__ to restrict " +"the range of 64-bit integer values to [-9007199254740991, " +"9007199254740991] for the larger compatibility. GDAL will allow writing " +"values outside of that range without warning, and can also read them " +"fine." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:255 +#: ../../source/drivers/vector/pgeo.rst:93 +msgid "Coded and range field domains are supported." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:262 +msgid "Relationship retrieval, creation, deletion and updating is supported." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:269 +msgid "" +"The hierarchical organization of tables and feature classes as top-level " +"element or within a feature dataset can be explored using the methods " +":cpp:func:`GDALDataset::GetRootGroup`, " +":cpp:func:`GDALGroup::GetGroupNames`, :cpp:func:`GDALGroup::OpenGroup`, " +":cpp:func:`GDALGroup::GetVectorLayerNames` and " +":cpp:func:`GDALGroup::OpenVectorLayer`" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:278 +msgid "" +"The driver implements transactions at the database level, through an " +"emulation (as per :ref:`rfc-54`). This works by backing up the current " +"state of the modified parts of a geodatabase after " +"StartTransaction(force=TRUE) is called. If the transaction is committed, " +"the backup copy is destroyed. If the transaction is rolled back, the " +"backup copy is restored." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:314 +msgid "Advantages of the OpenFileGDB driver, compared to the FileGDB driver" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:316 +msgid "Can read ArcGIS 9.X Geodatabases, and not only 10 or above." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:318 +msgid "Can open layers with any spatial reference system." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:320 +msgid "Thread-safe (i.e. datasources can be processed in parallel)." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:322 +msgid "" +"Uses the VSI Virtual File API, enabling the user to read a Geodatabase in" +" a ZIP file or stored on a HTTP server." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:325 +msgid "Faster on databases with a big number of fields." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:327 +msgid "Does not depend on a third-party library." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:329 +msgid "Robust against corrupted Geodatabase files." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:334 +msgid "" +"Reading data compressed in SDC format (Smart Data Compression) or in CDF " +"format (Compressed Data Format) is not supported. For CDF, the " +":ref:`FileGDB driver <vector.filegdb>` can be used." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:338 +msgid "" +"Support for tables with 64-bit OBJECTIDs (which require GDAL >= 3.10), " +"where OBJECTIDs are sparse, is read-only and incomplete. The driver will " +"emit a warning if such situation occurs, and will attribute non-faithful " +"OBJECTIDs." +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:346 +msgid "Read layer from FileGDB and load into PostGIS:" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:352 +msgid "Get detailed info for FileGDB:" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:358 +msgid "Get detailed info for a zipped FileGDB:" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:367 +msgid ":ref:`OpenFileGDB raster <raster.openfilegdb>` documentation page" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:368 +msgid ":ref:`FileGDB driver <vector.filegdb>`, relying on the FileGDB API SDK" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:369 +msgid "" +"Reverse-engineered specification of the `FileGDB format " +"<https://github.com/rouault/dump_gdbtable/wiki/FGDB-Spec>`__" +msgstr "" + +#: ../../source/drivers/vector/openfilegdb.rst:376 +msgid "" +"Edition/write capabilities of the driver have been funded by the " +"following organizations: Provincie Zuid-Holland, Provincie Gelderland and" +" Gemeente Amsterdam." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:4 +msgid "OSM - OpenStreetMap XML and PBF" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:6 +msgid "OSM" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:10 +msgid "" +"This driver reads OpenStreetMap files, in .osm (XML based) and .pbf " +"(optimized binary) formats." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:13 +msgid "" +"The driver is available if GDAL is built with SQLite support and, for " +".osm XML files, with Expat support." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:16 +msgid "The filenames must end with .osm or .pbf extension." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:18 +msgid "The driver will categorize features into 5 layers :" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:20 +msgid "**points** : \"node\" features that have significant tags attached." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:21 +msgid "**lines** : \"way\" features that are recognized as non-area." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:22 +msgid "" +"**multilinestrings** : \"relation\" features that form a " +"multilinestring(type = 'multilinestring' or type = 'route')." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:24 +msgid "" +"**multipolygons** : \"relation\" features that form a multipolygon (type " +"= 'multipolygon' or type = 'boundary'), and \"way\" features that are " +"recognized as area." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:27 +msgid "" +"**other_relations** : \"relation\" features that do not belong to the " +"above 2 layers." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:38 +#: ../../source/drivers/vector/pgeo.rst:128 +msgid "Configuration" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:40 +msgid "" +"In the *data* folder of the GDAL distribution, you can find an " +":source_file:`ogr/ogrsf_frmts/osm/data/osmconf.ini` file that can be " +"customized to fit your needs. You can also define an alternate path with " +"the :config:`OSM_CONFIG_FILE` configuration option." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:45 +msgid "" +"The customization is essentially which OSM attributes and keys should be " +"translated into OGR layer fields." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:48 +msgid "" +"Fields can be computed with SQL expressions (evaluated by SQLite engine) " +"from other fields/tags. For example to compute the z_order attribute." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:53 +msgid "\"other_tags\" field" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:55 +msgid "" +"When keys are not strictly identified in the *osmconf.ini* file, the " +"key/value pair is appended in a \"other_tags\" field, with a syntax " +"compatible with the PostgreSQL HSTORE type. See the *COLUMN_TYPES* layer " +"creation option of the :ref:`PG driver <vector.pg>`. The " +"``hstore_get_value()`` function can be used with the :ref:`OGRSQL " +"<ogr_sql_dialect>` or :ref:`SQLite <sql_sqlite_dialect>` SQL dialects to " +"extract the value of a given key." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:70 +msgid "" +"Starting with GDAL 3.7, it is possible to ask the format of this field to" +" be JSON encoded, by using the TAGS_FORMAT=JSON open option, or the " +"``tags_format=json`` setting in the *osmconf.ini* file." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:75 +msgid "\"all_tags\" field" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:77 +msgid "" +"Similar to \"other_tags\", except that it contains both keys specifically" +" identified to be reported as dedicated fields, as well as other keys." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:80 +msgid "" +"\"all_tags\" is disabled by default, and when enabled, it is exclusive " +"with \"other_tags\"." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:138 +msgid "Interleaved reading" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:140 +msgid "" +"Due to the nature of OSM files and how the driver works internally, the " +"default reading mode that works per-layer might not work correctly, " +"because too many features will accumulate in the layers before being " +"consumed by the user application." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:145 +msgid "" +"Starting with GDAL 2.2, applications should use the " +"``GDALDataset::GetNextFeature()`` API to iterate over features in the " +"order they are produced." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:149 +msgid "" +"For earlier versions, for large files, applications should set the " +":config:`OGR_INTERLEAVED_READING=YES` configuration option to turn on a " +"special reading mode where the following reading pattern must be used:" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:174 +msgid "" +"Note : the ogr2ogr application has been modified to use that " +":config:`OGR_INTERLEAVED_READING` mode without any particular user " +"action." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:181 +msgid "" +"Due to way .osm or .pbf files are structured and the parsing of the file " +"is done, for efficiency reasons, a spatial filter applied on the points " +"layer will also affect other layers. This may result in lines or polygons" +" that have missing vertices." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:186 +msgid "" +"To improve this, a possibility is using a larger spatial filter with some" +" buffer for the points layer, and then post-process the output to apply " +"the desired filter. This would not work however if a polygon has vertices" +" very far away from the interest area. In which case full conversion of " +"the file to another format, and filtering of the resulting lines or " +"polygons layers would be needed." +msgstr "" + +#: ../../source/drivers/vector/osm.rst:194 +msgid "Reading .osm.bz2 files and/or online files" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:196 +msgid "" +".osm.bz2 are not natively recognized, however you can process them (on " +"Unix), with the following command :" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:203 +msgid "You can convert a .osm or .pbf file without downloading it :" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:215 +msgid "And to combine the above steps :" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:270 +msgid "`OpenStreetMap home page <http://www.openstreetmap.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:271 +msgid "" +"`OSM XML Format description " +"<http://wiki.openstreetmap.org/wiki/OSM_XML>`__" +msgstr "" + +#: ../../source/drivers/vector/osm.rst:273 +msgid "" +"`OSM PBF Format description " +"<http://wiki.openstreetmap.org/wiki/PBF_Format>`__" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:8 +msgid "Parquet" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:12 +msgid "" +"From https://parquet.apache.org/: \"Apache Parquet is an open source, " +"column-oriented data file format designed for efficient data storage and " +"retrieval. It provides efficient data compression and encoding schemes " +"with enhanced performance to handle complex data in bulk. Parquet is " +"available in multiple languages including Java, C++, Python, etc...\"" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:17 +msgid "" +"This driver also supports geometry columns using the GeoParquet " +"specification." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:19 +msgid "" +"The GeoParquet 1.0.0 specification is supported since GDAL 3.8.0. The " +"GeoParquet 1.1.0 specification is supported since GDAL 3.9.0." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:70 +msgid "" +"Compression method. Available values depend on how the Parquet library " +"was compiled. Defaults to SNAPPY when available, otherwise NONE." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:152 +msgid "" +"Note however that enabling this option involves creating a temporary " +"GeoPackage file (in the same directory as the final Parquet file), and " +"thus requires temporary storage (possibly up to several times the size of" +" the final Parquet file, depending on Parquet compression) and additional" +" processing time." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:158 +msgid "" +"The efficiency of spatial filtering depends on the ROW_GROUP_SIZE. If it " +"is too large, too many features that are not spatially close will be " +"grouped together. If it is too small, the file size will increase, and " +"extra processing time will be necessary to browse through the row groups." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:163 +msgid "" +"Note also that when this option is enabled, the Arrow writing API (which " +"is for example triggered when using ogr2ogr to convert from Parquet to " +"Parquet), fallbacks to the generic implementation, which does not support" +" advanced Arrow types (lists, maps, etc.)." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:171 +msgid "" +"SQL statements are run through the OGR SQL engine. Statistics can be used" +" to speed-up evaluations of SQL requests like: \"SELECT MIN(colname), " +"MAX(colname), COUNT(colname) FROM layername\"" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:176 +msgid "Dataset/partitioning read support" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:178 +msgid "" +"Starting with GDAL 3.6.0, the driver can read directories that contain " +"several Parquet files, and expose them as a single layer. This support is" +" only enabled if the driver is built against the ``arrowdataset`` C++ " +"library." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:182 +msgid "" +"It is also possible to force opening single Parquet file in that mode by " +"prefixing their filename with ``PARQUET:``." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:185 +msgid "" +"Optimized spatial and attribute filtering for Arrow datasets is available" +" since GDAL 3.10." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:193 +msgid "" +"Layer metadata can be read and written. It is serialized as JSON content " +"in a ``gdal:metadata`` domain." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:197 +msgid "Multithreading" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:199 +msgid "" +"Starting with GDAL 3.6.0, the driver will use up to 4 threads for reading" +" (or the maximum number of available CPUs returned by " +":cpp:func:`CPLGetNumCPUs()` if it is lower by 4). This number can be " +"configured with the configuration option :config:`GDAL_NUM_THREADS`, " +"which can be set to an integer value or ``ALL_CPUS``." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:206 +msgid "Validation script" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:208 +msgid "" +"The :source_file:`swig/python/gdal-" +"utils/osgeo_utils/samples/validate_geoparquet.py` Python script can be " +"used to check compliance of a Parquet file against the GeoParquet " +"specification." +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:212 +msgid "To validate only metadata:" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:219 +msgid "To validate metadata and check content of geometry column(s):" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:239 +msgid "`Apache Parquet home page <https://parquet.apache.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:241 +msgid "`Parquet file format <https://github.com/apache/parquet-format>`__" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:243 +msgid "" +"`GeoParquet specification " +"<https://github.com/opengeospatial/geoparquet>`__" +msgstr "" + +#: ../../source/drivers/vector/parquet.rst:245 +msgid "Related driver: :ref:`Arrow driver <vector.arrow>`" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:11 +msgid "" +"Refer to the :ref:`PDF raster <raster.pdf>` documentation page for common" +" documentation of the raster and vector sides of the driver." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:26 +msgid "" +"This driver can read and write geospatial PDF with vector features. " +"Vector read support requires linking to one of the above mentioned " +"dependent libraries, but write support does not. The driver can read " +"vector features encoded according to PDF's logical structure facilities " +"(as described by \"§10.6 - Logical Structure\" of PDF spec), or retrieve " +"only vector geometries for other vector PDF files." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:33 +msgid "" +"If there is no such logical structure, the driver will not try to " +"interpret the vector content of the PDF, unless you defined the " +":config:`OGR_PDF_READ_NON_STRUCTURED` configuration option to YES." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:38 +msgid "Feature style support" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:40 +msgid "" +"For write support, the driver has partial support for the style " +"information attached to features, encoded according to the " +":ref:`ogr_feature_style`." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:44 +msgid "The following tools are recognized:" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:46 +msgid "For points, LABEL and SYMBOL." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:47 +msgid "For lines, PEN." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:48 +msgid "For polygons, PEN and BRUSH." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:50 +msgid "" +"The supported attributes for each tool are summed up in the following " +"table:" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:58 +msgid "Supported attributes" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:62 +msgid "PEN(c:#FF0000,w:5px)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:65 +msgid "BRUSH(fc:#0000FF)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "GDAL >= 2.3.0: text (t), limited to ASCII strings; font name (f), see" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "note below; font size (s); bold (bo); italic (it); text color (c); x and" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "y offsets (dx, dy); angle (a); anchor point (p), values 1 through 9;" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "stretch (w)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "GDAL <= 2.2.x: text (t), limited to ASCII strings; font size (s); text" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "color (c); x and y offsets (dx, dy); angle (a)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:73 +msgid "LABEL(c:#000000,t:\"Hello World!\",s:5g)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:75 +msgid "" +"id (ogr-sym-0 to ogr-sym-9, and filenames for raster symbols); color (c);" +" size (s)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "SYMBOL(c:#00FF00,id:\"ogr- sym-3\",s:10)" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst +msgid "SYMBOL(c:#00000080,id:\"a_symbol.png\")" +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:79 +#, python-format +msgid "" +"Alpha values are supported for colors to control the opacity. If not " +"specified, for BRUSH, it is set at 50% opaque." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:82 +msgid "" +"For SYMBOL with a bitmap name, only the alpha value of the color " +"specified with 'c' is taken into account." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:85 +msgid "" +"A font name starting with \"Times\" or containing the string \"Serif\" " +"(case sensitive) will be treated as Times. A font name starting with " +"\"Courier\" or containing the string \"Mono\" (case sensitive) will be " +"treated as Courier. All other font names will be treated as Helvetica." +msgstr "" + +#: ../../source/drivers/vector/pdf.rst:106 +msgid ":ref:`PDF raster <raster.pdf>` documentation page" +msgstr "" + +#: ../../source/drivers/vector/pds.rst:4 +msgid "PDS - Planetary Data Systems TABLE" +msgstr "" + +#: ../../source/drivers/vector/pds.rst:10 +msgid "" +"This driver reads TABLE objects from PDS datasets. Note there is a GDAL " +"PDS driver to read the raster IMAGE objects from PDS datasets." +msgstr "" + +#: ../../source/drivers/vector/pds.rst:13 +msgid "" +"The driver must be provided with the product label file (even when the " +"actual data is placed in a separate file)." +msgstr "" + +#: ../../source/drivers/vector/pds.rst:16 +msgid "" +"If the label file contains a *TABLE* object, it will be read as the only " +"layer of the dataset. If no *TABLE* object is found, the driver will look" +" for all objects containing the TABLE string and read each one in a " +"layer." +msgstr "" + +#: ../../source/drivers/vector/pds.rst:21 +msgid "" +"ASCII and BINARY tables are supported. The driver can retrieve the field " +"descriptions from inline COLUMN objects or from a separate file pointed " +"by ^STRUCTURE." +msgstr "" + +#: ../../source/drivers/vector/pds.rst:25 +msgid "" +"If the table has a LONGITUDE and LATITUDE columns of type REAL and with " +"UNIT=DEGREE, they will be used to return POINT geometries." +msgstr "" + +#: ../../source/drivers/vector/pds.rst:36 +msgid "" +"`Description of PDS format <https://pds.jpl.nasa.gov/tools/standards-" +"reference.shtml>`__ (see Annex A.29 from StdRef_20090227_v3.8.pdf)" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:6 +msgid "PostgreSQL" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:10 +msgid "" +"This driver implements support for access to spatial tables in PostgreSQL" +" extended with the `PostGIS <http://postgis.net/>`__ spatial data " +"support. Some support exists in the driver for use with PostgreSQL " +"without PostGIS but with less functionalities." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:15 +msgid "" +"This driver requires a connection to a Postgres database. If you want to " +"prepare a SQL dump to inject it later into a Postgres database, you can " +"instead use the :ref:`PostgreSQL SQL Dump driver <vector.pgdump>`." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:19 +msgid "" +"You can find additional information on the driver in the :ref:`Advanced " +"OGR PostgreSQL driver Information <vector.pg_advanced>` page." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:22 +msgid "" +"Starting with GDAL 3.9, only PostgreSQL >= 9 and PostGIS >= 2 are " +"supported." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:37 +msgid "" +"To connect to a Postgres datasource, use a connection string specifying " +"the database name, with additional parameters as necessary. The PG: " +"prefix is used to mark the name as a postgres connection string." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:43 +msgid "*or*" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:56 +msgid "Starting with GDAL 3.1 also this syntax is supported:" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:63 +msgid "Starting with GDAL 3.4, the URI syntax is also supported" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:70 +msgid "" +"It's also possible to omit the database name and connect to a *default* " +"database, with the same name as the user name." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:72 +msgid "" +"**Note**: We use PQconnectdb() to make the connection. See details from " +"`PostgreSQL libpq documentation <https://www.postgresql.org/docs/12" +"/libpq-connect.html>`__)." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:76 +msgid "Geometry columns" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:78 +msgid "" +"If the *geometry_columns* table exists (i.e. PostGIS is enabled for the " +"accessed database), then all tables and named views listed in the " +"*geometry_columns* table will be treated as OGR layers. Otherwise " +"(PostGIS disabled for the accessed database), all regular user tables and" +" named views will be treated as layers." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:84 +msgid "" +"The driver also supports the `geography " +"<http://postgis.net/docs/manual-1.5/ch04.html#PostGIS_Geography>`__ " +"column type." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:88 +msgid "" +"The driver also supports reading and writing the following non-linear " +"geometry types :CIRCULARSTRING, COMPOUNDCURVE, CURVEPOLYGON, MULTICURVE " +"and MULTISURFACE" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:95 +msgid "" +"The PostgreSQL driver passes SQL statements directly to PostgreSQL by " +"default, rather than evaluating them internally when using the " +"ExecuteSQL() call on the OGRDataSource, or the -sql command option to " +"ogr2ogr. Attribute query expressions are also passed directly through to " +"PostgreSQL. It's also possible to request the ogr Pg driver to handle SQL" +" commands with the :ref:`OGR SQL <ogr_sql_dialect>` engine, by passing " +"**\"OGRSQL\"** string to the ExecuteSQL() method, as the name of the SQL " +"dialect." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:104 +msgid "" +"Note that the PG driver uses PostgreSQL cursors to browse through the " +"result set of a ExecuteSQL() request, and that, at time of writing, " +"PostgreSQL default settings aren't optimized when the result set is small" +" enough to fit in one result page. If you experiment bad performance, " +"specifying the ``PRELUDE_STATEMENTS=SET cursor_tuple_fraction = 1.0;`` " +"open option might help." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:110 +msgid "" +"The PostgreSQL driver in OGR supports the " +"OGRDataSource::StartTransaction(), OGRDataSource::CommitTransaction() and" +" OGRDataSource::RollbackTransaction() calls in the normal SQL sense." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:117 +msgid "" +"The PostgreSQL driver does not support creation of new datasets (a " +"database within PostgreSQL), but it does allow creation of new layers " +"within an existing database." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:121 +msgid "" +"As mentioned above the type system is impoverished, and many OGR types " +"are not appropriately mapped into PostgreSQL." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:124 +msgid "" +"If the database has PostGIS types loaded (i.e. the geometry type), newly " +"created layers will be created with the PostGIS Geometry type. Otherwise " +"they will use OID." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:128 +msgid "" +"By default it is assumed that text being sent to Postgres is in the UTF-8" +" encoding. This is fine for plain ASCII, but can result in errors for " +"extended characters (ASCII 155+, LATIN1, etc). While OGR provides no " +"direct control over this, you can set the PGCLIENTENCODING environment " +"variable to indicate the format being provided. For instance, if your " +"text is LATIN1 you could set the environment variable to LATIN1 before " +"using OGR and input would be assumed to be LATIN1 instead of UTF-8. An " +"alternate way of setting the client encoding is to issue the following " +"SQL command with ExecuteSQL() : \"SET client_encoding TO encoding_name\" " +"where encoding_name is LATIN1, etc. Errors can be caught by enclosing " +"this command with a CPLPushErrorHandler()/CPLPopErrorHandler() pair." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:141 +msgid "Updating existing tables" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:142 +msgid "" +"When data is appended to an existing table (for example, using the " +"``-append`` option in ``ogr2ogr``) the driver will, by default, emit an " +"INSERT statement for each row of data to be added. This may be " +"significantly slower than the COPY-based approach taken when creating a " +"new table, but ensures consistency of unique identifiers if multiple " +"connections are accessing the table simultaneously." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:149 +msgid "" +"If only one connection is accessing the table when data is appended, the " +"COPY-based approach can be chosen by setting the config option " +"``PG_USE_COPY`` to ``YES``, which may significantly speed up the " +"operation." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:407 +msgid "" +"At time of writing, PgPoolII is not compatible with COPY mode as used by " +"the OGR PostgreSQL driver. Thus you should force PG_USE_COPY=NO when " +"using PgPoolII." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:481 +msgid "" +"Simple translation of a shapefile into PostgreSQL. The table 'abc' will " +"be created with the features from abc.shp and attributes from abc.dbf. " +"The database instance (warmerda) must already exist, and the table abc " +"must not already exist." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:501 +msgid "Export a single Postgres table to GeoPackage:" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:509 +msgid "Export many Postgres tables to GeoPackage:" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:517 +msgid "Export a whole Postgres database to GeoPackage:" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:526 +msgid "Load a single layer GeoPackage into Postgres:" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:536 +msgid "" +"In this example we merge tiger line data from two different directories " +"of tiger files into one table. Note that the second invocation uses " +"-append and no :lco:`OVERWRITE=yes`." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:547 +msgid "" +"This example shows using ogrinfo to evaluate an SQL query statement " +"within PostgreSQL. More sophisticated PostGIS specific queries may also " +"be used via the -sql commandline switch to ogrinfo." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:555 +msgid "" +"This example shows using ogrinfo to list PostgreSQL/PostGIS layers on a " +"different host." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:562 +msgid "" +"This example shows use of :oo:`PRELUDE_STATEMENTS` and " +":oo:`CLOSING_STATEMENTS` as destination open options of ogr2ogr." +msgstr "" + +#: ../../source/drivers/vector/pg.rst:570 +msgid "FAQs" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:572 +msgid "" +"**Why can't I see my tables? PostGIS is installed and I have data** You " +"must have permissions on all tables you want to read *and* " +"geometry_columns and spatial_ref_sys. Misleading behavior may follow " +"without an error message if you do not have permissions to these tables. " +"Permission issues on geometry_columns and/or spatial_ref_sys tables can " +"be generally confirmed if you can see the tables by setting the " +"configuration option :config:`PG_LIST_ALL_TABLES` to YES. (e.g. ``ogrinfo" +" --config PG_LIST_ALL_TABLES YES PG:xxxxx``)" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:585 +msgid ":ref:`Advanced OGR PostgreSQL driver Information <vector.pg_advanced>`" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:586 +msgid ":ref:`OGR PostgreSQL SQL Dump driver Page <vector.pgdump>`" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:587 +#: ../../source/drivers/vector/pgdump.rst:286 +msgid "`PostgreSQL Home Page <http://www.postgresql.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:588 +#: ../../source/drivers/vector/pgdump.rst:287 +msgid "`PostGIS <http://postgis.net/>`__" +msgstr "" + +#: ../../source/drivers/vector/pg.rst:589 +#: ../../source/drivers/vector/pgdump.rst:288 +msgid "" +"`PostGIS / OGR Wiki Examples Page " +"<http://trac.osgeo.org/postgis/wiki/UsersWikiOGR>`__" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:4 +msgid "PostgreSQL / PostGIS - Advanced Driver Information" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:6 +msgid "" +"The information collected in that page deal with advanced topics, not " +"found in the :ref:`OGR PostgreSQL driver Information <vector.pg>` page." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:10 +msgid "Connection options related to schemas and tables" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:12 +msgid "" +"The database opening should be significantly faster than in previous " +"versions, so using tables= or schemas= options will not bring further " +"noticeable speed-ups." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:16 +msgid "" +"The set of tables to be scanned can be overridden by specifying " +"*tables=[schema.]table[(geom_column_name)][,[schema2.]table2[(geom_column_name2)],...]*" +" within the connection string. If the parameter is found, the driver " +"skips enumeration of the tables as described in the next paragraph." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:22 +msgid "" +"It is possible to restrict the schemas that will be scanned while " +"establishing the list of tables. This can be done by specifying " +"*schemas=schema_name[,schema_name2]* within the connection string. This " +"can also be a way of speeding up the connection to a PostgreSQL database " +"if there are a lot of schemas. Note that if only one schema is listed, it" +" will also be made automatically the active schema (and the schema name " +"will not prefix the layer name). Otherwise, the active schema is still " +"'public', unless otherwise specified by the *active_schema=* option." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:32 +msgid "" +"The active schema ('public' being the default) can be overridden by " +"specifying *active_schema=schema_name* within the connection string. The " +"active schema is the schema where tables are created or looked for when " +"their name is not explicitly prefixed by a schema name. Note that this " +"does not restrict the tables that will be listed (see *schemas=* option " +"above). When getting the list of tables, the name of the tables within " +"that active schema will not be prefixed by the schema name. For example, " +"if you have a table 'foo' within the public schema, and a table 'foo' " +"within the 'bar_schema' schema, and that you specify " +"active_schema=bar_schema, 2 layers will be listed : 'foo' (implicitly " +"within 'bar_schema') and 'public.foo'." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:45 +msgid "Multiple geometry columns" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:47 +msgid "" +"The PostgreSQL driver supports accessing tables with multiple PostGIS " +"geometry columns." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:50 +msgid "" +"OGR supports reading, updating, creating tables with multiple PostGIS " +"geometry columns (following :ref:`rfc-41`) For such a table, a single OGR" +" layer will be reported with as many geometry fields as there are " +"geometry columns in the table." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:55 +msgid "" +"For backward compatibility, it is also possible to query a layer with " +"GetLayerByName() with a name formatted like 'foo(bar)' where 'foo' is a " +"table and 'bar' a geometry column." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:62 +msgid "" +"Even when PostGIS is enabled, if the user defines the environment " +"variable :config:`PG_LIST_ALL_TABLES=YES` (and does not specify tables=)," +" all regular user tables and named views will be treated as layers. " +"However, tables with multiple geometry column will only be reported once " +"in that mode. So this variable is mainly useful when PostGIS is enabled " +"to find out tables with no spatial data, or views without an entry in " +"*geometry_columns* table." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:70 +msgid "" +"In any case, all user tables can be queried explicitly with " +"GetLayerByName()" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:73 +msgid "" +"Regular (non-spatial) tables can be accessed, and will return features " +"with attributes, but not geometry. If the table has a \"wkb_geometry\" " +"field, it will be treated as a spatial table. The type of the field is " +"inspected to determine how to read it. It can be a PostGIS **geometry** " +"field, which is assumed to come back in OGC WKT, or type BYTEA or OID in " +"which case it is used as a source of OGC WKB geometry." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:80 +msgid "Tables inherited from spatial tables are supported." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:83 +msgid "" +"If there is an \"ogc_fid\" field, it will be used to set the feature id " +"of the features, and not treated as a regular field." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:86 +msgid "" +"The layer name may be of the form \"schema.table\". The schema must " +"exist, and the user needs to have write permissions for the target and " +"the public schema." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:90 +msgid "If the user defines the environment variable" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:96 +msgid "" +"(and does not specify tables=), only the regular user tables will be " +"treated as layers. The default action is to include the views. This " +"variable is particularly useful when you want to copy the data into " +"another format while avoiding the redundant data from the views." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:102 +msgid "Named views" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:104 +msgid "" +"When PostGIS is enabled for the accessed database, named views are " +"supported, provided that there is an entry in the *geometry_columns* " +"tables. But, note that the AddGeometryColumn() SQL function doesn't " +"accept adding an entry for a view (only for regular tables). So, that " +"must usually be done by hand with a SQL statement like :" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:114 +msgid "" +"It is also possible to use named views without inserting a row in the " +"geometry_columns table. For that, you need to explicitly specify the name" +" of the view in the \"tables=\" option of the connection string. See " +"above. The drawback is that OGR will not be able to report a valid SRS " +"and figure out the right geometry type." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:121 +msgid "Retrieving FID of newly inserted feature" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:123 +msgid "" +"The FID of a feature (i.e. usually the value of the OGC_FID column for " +"the feature) inserted into a table with CreateFeature(), in non-copy " +"mode, will be retrieved from the database and can be obtained with " +"GetFID(). One side-effect of this new behavior is that you must be " +"careful if you re-use the same feature object in a loop that makes " +"insertions. After the first iteration, the FID will be set to a non-null " +"value, so at the second iteration, CreateFeature() will try to insert the" +" new feature with the FID of the previous feature, which will fail as you" +" cannot insert 2 features with same FID. So in that case you must " +"explicitly reset the FID before calling CreateFeature(), or use a fresh " +"feature object." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:136 +msgid "Snippet example in Python :" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:146 +msgid "or :" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:155 +msgid "" +"Old GDAL behavior can be obtained by setting the configuration option " +":config:`OGR_PG_RETRIEVE_FID` to FALSE." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:159 +msgid "Issues with transactions" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:161 +msgid "" +"Efficient sequential reading in PostgreSQL requires to be done within a " +"transaction (technically this is a CURSOR WITHOUT HOLD). So the PG driver" +" will implicitly open such a transaction if none is currently opened as " +"soon as a feature is retrieved. This transaction will be released if " +"ResetReading() is called (provided that no other layer is still being " +"read)." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:168 +msgid "" +"If within such an implicit transaction, an explicit dataset level " +"StartTransaction() is issued, the PG driver will use a SAVEPOINT to " +"emulate properly the transaction behavior while making the active cursor " +"on the read layer still opened." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:173 +msgid "" +"If an explicit transaction is opened with dataset level " +"StartTransaction() before reading a layer, this transaction will be used " +"for the cursor that iterates over the layer. When explicitly committing " +"or rolling back the transaction, the cursor will become invalid, and " +"ResetReading() should be issued again to restart reading from the " +"beginning." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:180 +msgid "" +"As calling SetAttributeFilter() or SetSpatialFilter() implies an implicit" +" ResetReading(), they have the same effect as ResetReading(). That is to " +"say, while an implicit transaction is in progress, the transaction will " +"be committed (if no other layer is being read), and a new one will be " +"started again at the next GetNextFeature() call. On the contrary, if they" +" are called within an explicit transaction, the transaction is " +"maintained." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:188 +msgid "" +"With the above rules, the below examples show the SQL instructions that " +"are run when using the OGR API in different scenarios." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:281 +msgid "" +"Note: in reality, the PG drivers fetches 500 features at once. The FETCH " +"1 is for clarity of the explanation." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:285 +msgid "Advanced Examples" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:287 +msgid "" +"This example shows using ogrinfo to list only the layers specified by the" +" *tables=* options." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:294 +msgid "" +"This example shows using ogrinfo to query a table 'foo' with multiple " +"geometry columns ('geom1' and 'geom2')." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:301 +msgid "" +"This example show how to list only the layers inside the schema apt200810" +" and apt200812. The layer names will be prefixed by the name of the " +"schema they belong to." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:309 +msgid "" +"This example shows using ogrinfo to list only the layers inside the " +"schema named apt200810. Note that the layer names will not be prefixed by" +" apt200810 as only one schema is listed." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:317 +msgid "" +"This example shows how to convert a set of shapefiles inside the " +"apt200810 directory into an existing Postgres schema apt200810. In that " +"example, we could have use the schemas= option instead." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:325 +msgid "" +"This example shows how to convert all the tables inside the schema " +"apt200810 as a set of shapefiles inside the apt200810 directory. Note " +"that the layer names will not be prefixed by apt200810 as only one schema" +" is listed" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:334 +msgid "" +"This example shows how to overwrite an existing table in an existing " +"schema. Note the use of -nln to specify the qualified layer name." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:341 +msgid "" +"Note that using -lco SCHEMA=mytable instead of -nln would not have worked" +" in that case (see `#2821 <http://trac.osgeo.org/gdal/ticket/2821>`__ for" +" more details)." +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:345 +msgid "" +"If you need to overwrite many tables located in a schema at once, the " +"-nln option is not the more appropriate, so it might be more convenient " +"to use the active_schema connection string. The following example will " +"overwrite, if necessary, all the PostgreSQL tables corresponding to a set" +" of shapefiles inside the apt200810 directory :" +msgstr "" + +#: ../../source/drivers/vector/pg_advanced.rst:359 +msgid ":ref:`OGR PostgreSQL driver Information <vector.pg>`" +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:6 +msgid "PGDump" +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:10 +msgid "" +"This write-only driver implements support for generating a SQL dump file " +"that can later be injected into a live PostgreSQL instance. It supports " +"PostgreSQL extended with the `PostGIS <http://postgis.net/>`__ " +"geometries." +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:15 +msgid "This driver is very similar to the PostGIS shp2pgsql utility." +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:17 +msgid "Most creation options are shared with the regular PostgreSQL driver." +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:19 +msgid "" +"The PGDump driver supports creating tables with multiple PostGIS geometry" +" columns (following :ref:`rfc-41`)" +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:253 +msgid ":copy-config:`PG_USE_COPY`" +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:258 +msgid "" +"The driver supports writing to files managed by VSI Virtual File System " +"API, which include \"regular\" files, as well as files in the /vsizip/, " +"/vsigzip/ domains." +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:267 +msgid "" +"Simple translation of a shapefile into PostgreSQL into a file abc.sql. " +"The table 'abc' will be created with the features from abc.shp and " +"attributes from abc.dbf. The SRID is specified. :config:`PG_USE_COPY` is " +"set to YES to improve the performance." +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:276 +msgid "Pipe the output of the PGDump driver into the psql utility." +msgstr "" + +#: ../../source/drivers/vector/pgdump.rst:285 +msgid ":ref:`OGR PostgreSQL driver Page <vector.pg>`" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:6 +msgid "PGeo" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:10 +msgid "" +"OGR optionally supports reading ESRI Personal GeoDatabase .mdb files via " +"ODBC. Personal GeoDatabase is a Microsoft Access database with a set of " +"tables defined by ESRI for holding geodatabase metadata, and with " +"geometry for features held in a BLOB column in a custom format " +"(essentially Shapefile geometry fragments). This driver accesses the " +"personal geodatabase via ODBC but does not depend on any ESRI middle-" +"ware." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:18 +msgid "" +"Personal Geodatabases are accessed by passing the file name of the .mdb " +"file to be accessed as the data source name." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:21 +msgid "" +"In order to facilitate compatibility with different configurations, the " +":config:`PGEO_DRIVER_TEMPLATE` config option was added to provide a way " +"to programmatically set the DSN with the filename as an argument. In " +"cases where the driver name is known, this allows for the construction of" +" the DSN based on that information in a manner similar to the default " +"(used for Windows access to the Microsoft Access Driver)." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:29 +msgid "" +"OGR treats all feature tables as layers. Most geometry types should be " +"supported, including 3D data. Measure information (m value) is also " +"supported. Coordinate system information should be properly associated " +"with layers." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:33 +msgid "" +"Currently the OGR Personal Geodatabase driver does not take advantage of " +"spatial indexes for fast spatial queries, though that may be added in the" +" future." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:37 +msgid "" +"The Personal GeoDatabase format does not strictly differentiate between " +"multi and single geometry types for polygon or line layers, and it is " +"possible for a polygon or line layer to contain a mix of both single and " +"multi type geometries. Accordingly, in order to provide predictable " +"geometry types, the GDAL driver will always report the type of a line " +"layer as wkbMultiLineString, and a polygon layer as wkbMultiPolygon. " +"Single-part line or polygon features in the database will be promoted to " +"multilinestrings or multipolygons during reading." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:46 +msgid "" +"By default, SQL statements are passed directly to the MDB database " +"engine. It's also possible to request the driver to handle SQL commands " +"with :ref:`OGR SQL <ogr_sql_dialect>` engine, by passing **\"OGRSQL\"** " +"string to the ExecuteSQL() method, as name of the SQL dialect." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:54 +msgid "" +"\"GetLayerDefinition a_layer_name\" and \"GetLayerMetadata a_layer_name\"" +" can be used as special SQL requests to get respectively the definition " +"and metadata of a Personal GeoDatabase table as XML content." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:103 +msgid "How to use PGeo driver with unixODBC and MDB Tools (on Unix and Linux)" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:105 +msgid "" +"This article gives step-by-step explanation of how to use OGR with " +"unixODBC package and how to access Personal Geodatabase with PGeo driver." +" See also `GDAL wiki for other details " +"<http://trac.osgeo.org/gdal/wiki/mdbtools>`__" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:111 +msgid "Prerequisites" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:115 +msgid "Install `unixODBC <http://www.unixodbc.org>`__ >= 2.2.11" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:116 +msgid "" +"Install MDB Tools. The official upstream of MDB Tools is maintained at " +"`https://github.com/mdbtools/mdbtools " +"<https://github.com/mdbtools/mdbtools>`__ Version 0.9.4 or later is " +"recommended for best compatibility with the PGeo driver. With the latest " +"version no additional configuration (the followings) is required on " +"Debian Linux and :bash:`ogrinfo sample.mdb` works fine." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:123 +msgid "(On Ubuntu : sudo apt-get install unixodbc libmdbodbc)" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:125 +msgid "(On Debian : sudo apt-get install unixodbc odbc-mdbtools)" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:130 +msgid "There are two configuration files for unixODBC:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:132 +msgid "" +"odbcinst.ini - this file contains definition of ODBC drivers available to" +" all users; this file can be found in /etc directory or location given as" +" --sysconfdir if you did build unixODBC yourself." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:135 +msgid "" +"odbc.ini - this file contains definition of ODBC data sources (DSN " +"entries) available to all users." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:137 +msgid "" +"~/.odbc.ini - this is the private file where users can put their own ODBC" +" data sources." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:140 +msgid "" +"Editing the odbc.ini files is only required if you want to setup an ODBC " +"Data Source Name (DSN) so that Personal Geodatabase files can be directly" +" accessed via DSN. This is entirely optional, as the PGeo driver will " +"automatically handle the required connection parameters for you if a " +"direct .mdb file name is used instead." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:146 +msgid "Format of configuration files is very simple:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:154 +msgid "" +"For more details, refer to `unixODBC manual " +"<http://www.unixodbc.org/doc/>`__." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:158 +msgid "1. ODBC driver configuration" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:160 +msgid "" +"First, you need to configure ODBC driver to access Microsoft Access " +"databases with MDB Tools. Add following definition to your odbcinst.ini " +"file." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:174 +msgid "" +"[Microsoft Access Driver (\\*.mdb)] - remember to use \"Microsoft Access " +"Driver (\\*.mdb)\" as the name of section because PGeo driver composes " +"ODBC connection string for Personal Geodatabase using \"DRIVER=Microsoft " +"Access Driver (\\*.mdb);\" string." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:178 +msgid "Description - put short description of this driver definition." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:179 +msgid "Driver - full path of ODBC driver for MDB Tools." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:182 +msgid "2. ODBC data source configuration (optional)" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:184 +msgid "" +"In this section, I use 'sample.mdb' as a name of Personal Geodatabase, so" +" replace this name with your own database." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:187 +msgid "Create .odbc.ini file in your HOME directory:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:193 +msgid "Put following ODBC data source definition to your .odbc.ini file:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:208 +msgid "Step by step explanation of DSN entry:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:210 +msgid "" +"[sample_pgeo] - this is name of ODBC data source (DSN). You will refer to" +" your Personal Geodatabase using this name. You can use your own name " +"here." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:213 +msgid "Description - short description of the DSN entry." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:214 +msgid "Driver - full name of driver defined in step 1. above." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:215 +msgid "Database - full path to .mdb file with your Personal Geodatabase." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:216 +msgid "Host, Port, User and Password entries are not used by MDB Tools driver." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:220 +msgid "Testing PGeo driver with ogrinfo" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:222 +msgid "Now, you can try to access PGeo data source with ogrinfo." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:224 +msgid "First, check if you have PGeo driver built in OGR:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:235 +msgid "" +"Now, you can access your Personal Geodatabase. If you've setup a DSN for " +"the Personal Geodatabase (as detailed in section 2 above), the data " +"source should be PGeo:<DSN> where <DSN> is the name of DSN entry you put " +"to your .odbc.ini." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:239 +msgid "" +"Alternatively, you can pass a .mdb filename directly to OGR to avoid " +"manual creation of the DSN." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:249 +msgid "" +"After you run the command above, you should get list of layers stored in " +"your geodatabase." +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:252 +msgid "Now, you can try to query details of particular layer:" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:263 +msgid "Resources" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:265 +msgid "" +"`About ESRI Geodatabase " +"<http://www.esri.com/software/arcgis/geodatabase/index.html>`__" +msgstr "" + +#: ../../source/drivers/vector/pgeo.rst:267 +msgid "`MDB Tools project home <https://github.com/mdbtools/mdbtools>`__" +msgstr "" + +#: ../../source/drivers/vector/plscenes.rst:6 +msgid "PLScenes" +msgstr "" + +#: ../../source/drivers/vector/plscenes.rst:10 +msgid "" +"This driver can connect to Planet Labs Data V1 API. GDAL/OGR must be " +"built with Curl support in order for the PLScenes driver to be compiled." +msgstr "" + +#: ../../source/drivers/vector/plscenes.rst:13 +msgid "Please consult the dedicated pages for each version of the API:" +msgstr "" + +#: ../../source/drivers/vector/plscenes.rst:23 +msgid "" +"`Documentation of Planet Scenes Data API V1 " +"<https://developers.planet.com/docs/apis/data/>`__" +msgstr "" + +#: ../../source/drivers/vector/plscenes.rst:25 +#: ../../source/drivers/vector/plscenes_data_v1.rst:256 +msgid ":ref:`Raster PLMosaic / Planet Mosaics API driver <raster.plmosaic>`" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:4 +msgid "PLScenes (Planet Labs Scenes), Data V1 API" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:8 +msgid "" +"The driver supports read-only operations to list scenes and their " +"metadata as a vector layer per item-types: \"PSOrthoTile\", " +"\"REOrthoTile\", \"PSScene3Band\", \"PSScene4Band\", \"REScene\", " +"\"Landsat8L1G\", \"Sentinel2L1C\". It can also access raster scenes." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:30 +msgid "**version**\\ =data_v1: To specify the API version to request." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:31 +msgid "" +"**api_key**\\ =value: To specify the Planet API KEY. It is mandatory, " +"unless it is supplied through the open option API_KEY, or the " +"configuration option :config:`PL_API_KEY`." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:34 +msgid "" +"**follow_links**\\ =YES/NO: Whether assets links should be followed for " +"each scene (vector). Getting assets links require a HTTP request per " +"scene, which might be costly when enumerating through a lot of products. " +"Defaults to NO." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:38 +msgid "" +"**scene**\\ =scene_id: To specify the scene ID, when accessing raster " +"data. Optional for vector layer access." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:40 +msgid "" +"**itemtypes**\\ =name: To specify the item types name. Optional for " +"vector layer access. Mandatory for raster access." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:42 +msgid "" +"**asset**\\ =value: To specify the asset type (for raster fetching). " +"Default is \"visual\". Optional for vector layer access. If the option is" +" not specified and the 'visual' asset category does not exist for the " +"scene (or if the value is set to 'list'), the returned dataset will have " +"subdatasets for the available asset categories." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:47 +msgid "" +"**medata**\\ =YES/NO: (Raster only) Whether scene metadata should be " +"fetch from the API and attached to the raster dataset. Defaults to YES." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:126 +msgid ":copy-config:`PL_API_KEY`" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:136 +msgid "" +"The layer field definition is built from the \"plscensconf.json\" file in" +" the GDAL configuration. The links to downloadable products are in " +"*asset_XXXXX_location* attributes where XXXXX is the asset category id, " +"when they are active. Otherwise they should be activated by sending a " +"POST request to the URL in the *asset_XXXXX_activate_link* attribute " +"(what the raster driver does automatically)" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:146 +msgid "" +"The footprint of each scene is reported as a MultiPolygon with a " +"longitude/latitude WGS84 coordinate system (EPSG:4326)." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:152 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server. It also makes the same for simple attribute filters set with" +" SetAttributeFilter(). Note that not all attributes support all " +"comparison operators. Refer to comparator column in `Metadata properties " +"<https://www.planet.com/docs/v0/scenes/#metadata>`__" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:161 +msgid "" +"Features are retrieved from the server by chunks of 250 by default (and " +"this is the maximum value accepted by the server). This number can be " +"altered with the :config:`PLSCENES_PAGE_SIZE` configuration option." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:167 +msgid "Vector layer (scene metadata) examples" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:169 +msgid "Listing all scenes available (with the rights of the account) :" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:187 +msgid "" +"Listing all scenes available on PSOrthoTile item types, under a point of " +"(lat,lon)=(40,-100) :" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:194 +msgid "" +"Listing all scenes available within a bounding box (lat,lon)=(40,-100) to" +" (lat,lon)=(39,-99)" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:201 +msgid "Listing all scenes available matching criteria :" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:207 +msgid "List all downloadable scenes:" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:214 +msgid "Raster access" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:216 +msgid "" +"Scenes can be accessed as raster datasets, provided that the scene ID is " +"specified with the 'scene' parameter / :oo:`SCENE` open option. The " +"'itemtypes' parameter / :oo:`ITEMTYPES` open option must also be " +"specified. The asset type (visual, analytic, ...) can be specified with " +"the 'asset' parameter / :oo:`ASSET` open option. The scene id is the " +"content of the value of the 'id' field of the features." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:223 +msgid "" +"If the product is not already generated on the server, it will be " +"activated, and the driver will wait for it to be available. The length of" +" this retry can be configured with the :oo:`ACTIVATION_TIMEOUT` open " +"option." +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:228 +msgid "Raster access examples" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:230 +msgid "Displaying raster metadata :" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:242 +msgid "Converting/downloading a whole file:" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:252 +msgid ":ref:`General documentation page for PLScenes driver <vector.plscenes>`" +msgstr "" + +#: ../../source/drivers/vector/plscenes_data_v1.rst:254 +msgid "" +"`Documentation of Planet Scenes Data API v1 " +"<https://developers.planet.com/docs/apis/data/>`__" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:5 +msgid "PMTiles -- ProtoMaps Tiles" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:9 +msgid "PMTiles" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:13 +msgid "" +"This driver supports reading and writing `PMTiles " +"<https://github.com/protomaps/PMTiles>`__ datasets containing vector " +"tiles, encoded in the MapVector Tiles (MVT) format." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:16 +msgid "" +"PMTiles is a single-file archive format for tiled data. A PMTiles archive" +" can be hosted on a commodity storage platform such as S3, and enables " +"low-cost, zero-maintenance map applications that are \"serverless\" - " +"free of a custom tile backend or third party provider." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:21 +msgid "" +"This driver is compatible with all GDAL :ref:`network-based virtual file " +"systems <network_based_file_systems>`" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:27 +msgid "" +"The supported datasets must contain a JSON metadata document following " +"the `MBTiles specification <https://github.com/mapbox/mbtiles-" +"spec/blob/master/1.3/spec.md#vector-tileset-metadata>`__, containing at " +"least the ``vector_layers`` array." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:32 +msgid "" +"Note that the driver will make no effort of stitching together geometries" +" for linear or polygonal features that overlap several tiles. An " +"application that wishes to eliminate those interrupts could potentially " +"use the CLIP=NO open option to get larger boundaries, and use appropriate" +" clipping graphic primitives to hide those discontinuities." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:59 +msgid "" +"Vector tiles are generally produced with a buffer that provides overlaps " +"between adjacent tiles, and can be used to display them properly. When " +"using vector tiles as a vector layer source, like in OGR vector model, " +"this padding is undesirable, hence the default behavior of clipping." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:89 +msgid "" +"Tiles are generated with WebMercator (EPSG:3857) projection. Several " +"layers can be written. It is possible to decide at which zoom level " +"ranges a given layer is written." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:97 +msgid "" +"The driver implements also a direct translation mode when using " +":program:`ogr2ogr` with a MBTiles vector dataset as input and a PMTiles " +"output dataset, without any argument: ``ogr2ogr out.pmtiles in.mbtiles``." +" In that mode, existing MVT tiles from the MBTiles files are used as " +"such, contrary to the general writing mode that will involve computing " +"them by discretizing geometry coordinates." +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:250 +msgid "/vsipmtiles/ virtual file system" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:252 +msgid "" +"The /vsipmtiles/ virtual file system offers a view of the content of a " +"PMTiles dataset has a file hierarchy, with the following structure:" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:263 +msgid "" +"The :source_file:`swig/python/gdal-utils/osgeo_utils/samples/gdal_ls.py` " +"and :source_file:`swig/python/gdal-utils/osgeo_utils/samples/gdal_cp.py` " +"sample utilities can be used to explore and extract data from a PMTiles " +"dataset" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:268 +msgid "Listing the content of a dataset:" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:274 +#: ../../source/drivers/vector/pmtiles.rst:296 +msgid "outputs:" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:290 +msgid "Displaying the metadata JSON file:" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:334 +msgid "Extracting all content in a local directory:" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:342 +msgid "" +"Simple translation of a single shapefile into PMTiles. Dataset creation " +"options (dsco) MINZOOM and MAXZOOM specifies tile zoom levels. ::" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:347 +msgid "" +"Merge all PostgreSQL/PostGIS tables in a schema into a single PMTiles " +"file. PostgreSQL table names are used as layer names. Dataset creation " +"options (dsco) MINZOOM and MAXZOOM specifies tile zoom levels. ::" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:356 +msgid "`PMTiles specification <https://github.com/protomaps/PMTiles>`__" +msgstr "" + +#: ../../source/drivers/vector/pmtiles.rst:358 +msgid ":ref:`MBTiles driver <raster.mbtiles>`" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:6 +msgid "S57" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:10 +msgid "" +"International Hydrographic Organisation (IHO) S-57 Electronic Navigation " +"Charts (ENC) datasets are supported for read access." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:13 +msgid "" +"The S-57 driver module produces features for all S-57 features in the " +"S-57 file, and associated updates. S-57 (ENC) files normally have the " +"extension \".000\"." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:17 +msgid "" +"S-57 feature objects are translated into features. S-57 geometry objects " +"are automatically collected and formed into geometries on the features." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:20 +msgid "" +"The S-57 reader depends on having two supporting files, " +"s57objectclasses.csv, and s57attributes.csv available at runtime in order" +" to translate features in an object class specific manner. These should " +"be in the directory pointed to by the environment variable S57_CSV, or in" +" the current working directory." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:26 +msgid "" +"S-57 update files contain information on how to update a distributed S-57" +" base data file. The base files normally have the extension .000 while " +"the update files have extensions like .001, .002 and so on. The S-57 " +"reader will normally read and apply all updates files to the in memory " +"version of the base file on the fly. The feature data provided to the " +"application therefore includes all the updates." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:43 +msgid "Feature Translation" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:45 +msgid "" +"Normally all features read from S-57 are assigned to a layer based on the" +" name of the object class (OBJL) to which they belong. For instance, with" +" an OBJL value of 2, the feature is an \"Airport / airfield\" and has a " +"short name of \"AIRARE\" which is used as the layer name. A typical S-57 " +"transfer will have in excess of 100 layers." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:51 +msgid "" +"Each feature type has a predefined set of attributes as defined by the " +"S-57 standard. For instance, the airport (AIRARE) object class can have " +"the AIRARE, CATAIR, CONDTN, CONVIS, NOBJNM, OBJNAM, STATUS, INFORM, " +"NINFOM, NTXTDS, PICREP, SCAMAX, SCAMIN, TXTDSC, RECDAT, RECIND, SORDAT, " +"and SORIND attributes. These short names can be related to longer, more " +"meaningful names using an S-57 object/attribute catalog such as the S-57 " +"standard document itself, or the catalog files (s57attributes.csv, and " +"s57objectclasses.csv). Such a catalog can also be used to establish all " +"the available object classes, and their attributes." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:61 +msgid "" +"The following are some common attributes, including generic attributes " +"which appear on all feature, regardless of object class. is turned on." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:100 +msgid "The following are present if LNAM_REFS is enabled:" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:116 +msgid "DSID layer" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:118 +msgid "" +"Dataset wide fields, such as DSID (Data Set Identification), DSSI (Data " +"Set Structure Information) and DSPM (Data Set Parameter) are exposed in a" +" layer ``DSID`` which has a single feature. See paragraph 7.3.1 \"Data " +"set general information record structure\" of `IHO S-57 Edition 3.1 " +"standard (main)`_" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:125 +msgid "Soundings" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:127 +msgid "" +"Depth soundings are handled somewhat specially in S-57 format, in order " +"to efficiently represent the many available data points. In S-57 one " +"sounding feature can have many sounding points. The S-57 reader splits " +"each of these out into its own feature type \\`SOUNDG' feature with an " +"s57_type of \\`s57_point3d'. All the soundings from a single feature " +"record will have the same AGEN, FIDN, FIDS and LNAM value." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:135 +msgid "S57 Control Options" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:137 +msgid "" +"There are several control options which can be used to alter the behavior" +" of the S-57 reader. Users can set these by appending them in the " +"OGR_S57_OPTIONS environment variable." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:141 +msgid "" +"They can also be specified independently as open options to the driver. " +"|about-open-options| The following open options are supported:" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:234 +msgid "S-57 Export" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:236 +msgid "" +"Preliminary S-57 export capability is intended only for specialized use, " +"and is not properly documented at this time. Setting the following " +"options is a minimum required to support S-57 to S-57 conversion via OGR." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:244 +msgid "" +"|about-dataset-creation-options| The following dataset creation options " +"are supported to supply basic information for the S-57 data set " +"descriptive records (DSID and DSPM, see the S-57 standard for a more " +"detailed description):" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:373 +msgid "`S-57 Online Object/Attribute Catalog <http://www.s-57.com/>`__" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:374 +msgid "" +"`Frank's S-57 Page (at archive.org) " +"<https://web.archive.org/web/20130730111701/http://home.gdal.org/projects/s57/index.html>`__:" +" Links to other resources, and sample datasets." +msgstr "" + +#: ../../source/drivers/vector/s57.rst:377 +msgid "`IHO S-57 Edition 3.1 standard (main)`_" +msgstr "" + +#: ../../source/drivers/vector/s57.rst:378 +msgid "" +"`S-57 Appendix B " +"<https://iho.int/uploads/user/pubs/standards/s-57/20ApB1.pdf>`__" +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:10 +msgid "" +"SDTS TVP (Topological Vector Profile) and Point Profile datasets are " +"supported for read access. Each primary attribute, node (point), line and" +" polygon module is treated as a distinct layer." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:14 +msgid "" +"To select an SDTS transfer, the name of the catalog file should be used. " +"For instance ``TR01CATD.DDF`` where the first four characters are all " +"that typically varies." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:18 +msgid "" +"SDTS coordinate system information is properly supported for most " +"coordinate systems defined in SDTS." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:21 +msgid "There is no update or creation support in the SDTS driver." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:23 +msgid "" +"Note that in TVP datasets the polygon geometry is formed from the " +"geometry in the line modules. Primary attribute module attributes should " +"be properly attached to their related node, line or polygon features, but" +" can be accessed separately as their own layers." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:28 +msgid "This driver has no support for raster (DEM) SDTS datasets." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:40 +msgid "" +"`SDTS Abstraction Library " +"<https://web.archive.org/web/20130730111701/http://home.gdal.org/projects/sdts/index.html>`__:" +" The base library used to implement this driver." +msgstr "" + +#: ../../source/drivers/vector/sdts.rst:43 +msgid "" +"`http://mcmcweb.er.usgs.gov/sdts <http://mcmcweb.er.usgs.gov/sdts/>`__: " +"Main USGS SDTS web page." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:6 +msgid "Selafin" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:10 +msgid "" +"OGR supports reading from 2D Selafin/Seraphin files. Selafin/Seraphin is " +"the generic output and input format of geographical files in the open-" +"source `Telemac hydraulic model <http://www.opentelemac.org>`__. The file" +" format is suited to the description of numerical attributes for a set of" +" point features at different time steps. Those features usually " +"correspond to the nodes in a finite-element model. The file also holds a " +"connectivity table which describes the elements formed by those nodes and" +" which can also be read by the driver." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:19 +msgid "The driver supports the use of VSI virtual files as Selafin datasources." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:21 +msgid "" +"The driver offers full read-write support on Selafin files. However, due " +"to the particular nature of Selafin files where element (polygon) " +"features and node (point) features are closely related, writing on " +"Selafin layers can lead to counter-intuitive results. In a general way, " +"writing on any layer of a Selafin data-source will cause side effects on " +"all the other layers. Also, it is very important **not to open the same " +"datasource more than once in update mode**. Having two processes write at" +" the same time on a single datasource can lead to irreversible data " +"corruption. The driver issues a warning each time a datasource is opened " +"in update mode." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:42 +msgid "Magic bytes" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:44 +msgid "" +"There is no generic extension to Selafin files. The adequate format is " +"tested by looking at a dozen of magic bytes at the beginning of the file:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:48 +msgid "" +"The first four bytes of the file should contain the values (in " +"hexadecimal): 00 00 00 50. This actually indicates the start of a string " +"of length 80 in the file." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:51 +msgid "" +"At position 84 in the file, the eight next bytes should read (in " +"hexadecimal): 00 00 00 50 00 00 00 04." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:54 +msgid "" +"Files which match those two criteria are considered to be Selafin files " +"and the driver will report it has opened them successfully." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:60 +msgid "" +"Selafin format is designed to hold data structures in a portable and " +"compact way, and to allow efficient random access to the data. To this " +"purpose, Selafin files are binary files with a generic structure." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:65 +msgid "Elements" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:67 +msgid "" +"Selafin files are made of the juxtaposition of elements. Elements have " +"one of the following types:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:70 +msgid "integer," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:71 +msgid "string," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:72 +msgid "floating point values," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:73 +msgid "arrays of integers," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:74 +msgid "arrays of floating point values." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:77 +msgid "Element" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:77 +msgid "Internal representation" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:80 +#: ../../source/drivers/vector/selafin.rst:91 +msgid "a b c d" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:80 +msgid "" +"Integers are stored on 4 bytes in big-endian format (most significant " +"byte first). The value of the integer is 2\\ :sup:`24`.a+2\\ :su " +"p:`16`.b+2\\ :sup:`8`. c+d." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:91 +msgid "Floating point" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:91 +msgid "" +"Floating point values are stored on 4 bytes in IEEE 754 format and under " +"big-endian convention (most significant byte first). Endianness is " +"detected at run time only once when the first floating point value is " +"read." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:103 +#: ../../source/drivers/vector/selafin.rst:121 +#: ../../source/drivers/vector/selafin.rst:142 +msgid "Length 1 2 ... Length" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:103 +msgid "Strings are stored in three parts:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:106 +msgid "an integer holding the length (in characters) of the string, over 4 bytes;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:111 +msgid "the sequence of characters of the string, each character on one byte;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:116 +msgid "the same integer with the length of the string repeated" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:121 +msgid "Array of integers" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:121 +msgid "Arrays of integers are stored in three parts:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:125 +#: ../../source/drivers/vector/selafin.rst:147 +msgid "" +"an integer holding the length (in bytes, thus 4 times the number of " +"elements) of the array, over 4 bytes;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:132 +msgid "" +"the sequence of integers in the array, each integer on 4 bytes as " +"described earlier;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:138 +#: ../../source/drivers/vector/selafin.rst:160 +msgid "the same integer with the length of the array repeated" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:142 +msgid "Array of floating point values" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:142 +msgid "Arrays of floating point values are stored in three parts:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:154 +msgid "" +"the sequence of floating point values in the array, each one on 4 bytes " +"as described earlier;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:166 +msgid "Full structure" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:168 +msgid "" +"The header of a Selafin file holds the following elements in that exact " +"order:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:171 +msgid "" +"a *string* of 80 characters with the title of the study; the last 8 " +"characters shall be \"SERAPHIN\" or \"SERAFIN\" or \"SERAFIND\";" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:173 +msgid "" +"an *array of integers* of exactly 2 elements, the first one being the " +"number of variables (attributes) *nVar*, and the second is ignored;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:175 +msgid "*nVar strings* with the names of the variables, each one with length 32;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:177 +msgid "an *array of integers* of exactly 10 elements:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:179 +msgid "the third element is the x-coordinate of the origin of the model;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:180 +msgid "the fourth element is the y-coordinate of the origin of the model;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:181 +msgid "" +"the tenth element *isDate* indicates if the date of the model has to be " +"read (see later);" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:183 +msgid "" +"in addition, the second element being unused by hydraulic software at the" +" moment, it is used by the driver to store the spatial reference system " +"of the datasource, in the form of a single integer with the EPSG number " +"of the projection;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:188 +msgid "" +"if *isDate*\\ =1, an *array of integers* of exactly 6 elements, with the " +"starting date of the model (year, month, day, hour, minute, second);" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:191 +msgid "an *array of integers* of exactly 4 elements:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:193 +msgid "the first element is the number of elements *nElements*," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:194 +msgid "the second element is the number of points *nPoints*," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:195 +msgid "" +"the third element is the number of points per element\\ " +"*nPointsPerElement*," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:197 +msgid "the fourth element must be 1;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:199 +msgid "" +"an *array of integers* of exactly *nElements*nPointsPerElement* elements," +" with each successive set of *nPointsPerElement* being the list of the " +"number of the points (number starting with 1) constituting an element;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:203 +msgid "" +"an *array of integers* of exactly *nPoints* elements ignored by the " +"driver (the elements shall be 0 for inner points and another value for " +"the border points where a limit condition is applied);" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:206 +msgid "" +"an *array of floating point values* of exactly *nPoints* elements with " +"the x-coordinates of the points;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:208 +msgid "" +"an *array of floating point values* of exactly *nPoints* elements with " +"the y-coordinates of the points;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:211 +msgid "" +"The rest of the file actually holds the data for each successive time " +"step. A time step contains the following elements:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:214 +msgid "" +"a *array of floating point values* of exactly 1 element, being the date " +"of the time step relative to the starting date of the simulation (usually" +" in seconds);" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:217 +msgid "" +"*nVar array of floating point values*, each with exactly *nPoints* " +"elements, with the values of each attribute for each point at the current" +" time step." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:222 +msgid "Mapping between file and layers" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:225 +msgid "Layers in a Selafin datasource" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:227 +msgid "The Selafin driver accepts only Selafin files as data sources." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:229 +msgid "" +"Each Selafin file can hold one or several time steps. All the time steps " +"are read by the driver and two layers are generated for each time step:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:232 +msgid "" +"one layer with the nodes (points) and their attributes: its name is the " +"base name of the data source, followed by \"_p\" (for Points);" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:234 +msgid "" +"one layer with the elements (polygons) and their attributes calculated as" +" the averages of the values of the attributes of their vertices: its name" +" is the base name of the data source, followed by \"_e\" (for Elements)." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:239 +msgid "" +"Finally, either the number of the time step, or the calculated date of " +"the time step (based on the starting date and the number of seconds " +"elapsed), is added to the name. A data source in a file called Results " +"may therefore be read as several layers:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:244 +msgid "" +"``Results_p2014_05_01_20_00_00``, meaning that the layers holds the " +"attributes for the nodes and that the results hold for the time step at " +"8:00 PM, on May 1st, 2014;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:247 +msgid "" +"``Results_e2014_05_01_20_00_00``, meaning that the layers holds the " +"attributes for the elements and that the results hold for the time step " +"at 8:00 PM, on May 1st, 2014;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:250 +msgid "" +"``Results_p2014_05_01_20_15_00``, meaning that the layers holds the " +"attributes for the elements and that the results hold for the time step " +"at 8:15 PM, on May 1st, 2014;" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:256 +msgid "Constraints on layers" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:258 +msgid "" +"Because of the `format of the Selafin file <#format>`__, the layers in a " +"single Selafin datasource are not independent from each other. Changing " +"one layer will most certainly have side effects on all other layers. The " +"driver updates all the layers to match the constraints:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:263 +msgid "" +"All the point layers have the same number of features. When a feature is " +"added or removed in one layer, it is also added or removed in all other " +"layers." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:266 +msgid "" +"Features in different point layers share the same geometry. When the " +"position of one point is changed, it is also changed in all other layers." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:269 +msgid "" +"All the element layers have the same number of features. When a feature " +"is added or removed in one layer, it is also added or removed in all " +"other layers." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:272 +msgid "" +"All the polygons in element layers have the same number of vertices. The " +"number of vertices is fixed when the first feature is added to an element" +" layer, and can not be changed afterwards without recreating the " +"datasource from scratch." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:276 +msgid "" +"Features in different element layers share the same geometry. When an " +"element is added or removed in one layer, it is also added or removed in " +"all other layers." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:279 +msgid "" +"Every vertex of every feature in an element layer has a corresponding " +"point feature in the point layers. When an element feature is added, if " +"its vertices do not exist yet, they are created in the point layers." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:283 +msgid "" +"Points and elements layers only support attributes of type \"REAL\". The " +"format of real numbers (width and precision) can not be changed." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:287 +msgid "Layer filtering specification" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:289 +msgid "" +"As a single Selafin files may hold millions of layers, and the user is " +"generally interested in only a few of them, the driver supports syntactic" +" sugar to filter the layers before they are read." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:293 +msgid "" +"When the datasource is specified, it may be followed immediately by a " +"*layer filtering specification.*, as in ``Results[0:10]``. The effects of" +" the layer filtering specification is to indicate which time steps shall " +"be loaded from all Selafin files." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:298 +msgid "" +"The layer filtering specification is a comma-separated sequence of range " +"specifications, delimited by square brackets and maybe preceded by the " +"character 'e' or 'p'. The effect of characters 'e' and 'p' is to select " +"respectively either only elements or only nodes. If no character is " +"added, both nodes and elements are selected. Each range specification is:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:305 +msgid "" +"either a single number, representing one single time step (whose numbers " +"start with 0)," +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:307 +msgid "" +"or a set of two numbers separated by a colon: in that case, all the time " +"steps between and including those two numbers are selected; if the first " +"number is missing, the range starts from the beginning of the file (first" +" time step); if the second number is missing, the range goes to the end " +"of the file (last time step);" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:313 +msgid "" +"Numbers can also be negative. In this case, they are counted from the end" +" of the file, -1 being the last time step." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:316 +msgid "Some examples of layer filtering specifications:" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:319 +msgid "[0]" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:319 +msgid "First time step only, but return both points and elements" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:320 +msgid "[e:9]" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:320 +msgid "First 10 time steps only, and only layers with elements" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:321 +msgid "[p-4:]" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:321 +msgid "Last 4 time steps only, and only layers with nodes" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:322 +msgid "[3,10,-2:-1]" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:322 +msgid "" +"4\\ :sup:`th`, 11\\ :sup:`th`, and last two time steps, for both nodes " +"and elements" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:326 +msgid "Datasource creation options" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:345 +msgid "" +"An example of datasource creation option is: ``-dsco TITLE=\"My " +"simulation\" -dsco DATE=2014-05-01_10:00:00``." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:361 +msgid "An example of a layer creation option is: ``-lco DATE=24000``." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:364 +msgid "Notes about the creation and the update of a Selafin datasource" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:366 +msgid "" +"The driver supports creating and writing to Selafin datasources, but " +"there are some caveats when doing so." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:369 +msgid "" +"When a new datasource is created, it does not contain any layer, feature " +"or attribute." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:372 +msgid "" +"When a new layer is created, it automatically inherits the same number of" +" features and attributes as the other layers of the same type (points or " +"elements) already in the datasource. The features inherit the same " +"geometry as their corresponding ones in other layers. The attributes are " +"set to 0. If there was no layer in the datasource yet, the new layer is " +"created with no feature and attribute.In any case, when a new layer is " +"created, two layers are actually added: one for points and one for " +"elements." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:381 +msgid "" +"New features and attributes can be added to the layers or removed. The " +"behavior depends on the type of layer (points or elements). The following" +" table explains the behavior of the driver in the different cases." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:387 +msgid "Operation" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:387 +msgid "Points layers" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:387 +msgid "Element layers" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:389 +msgid "Change the geometry of a feature" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:389 +msgid "" +"The coordinates of the point are changed in the current layer and all " +"other layers in the datasource." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:389 +msgid "" +"The coordinates of all the vertices of the element are changed in the " +"current layer and all other layers in the datasource. It is not possible " +"to change the number of vertices. The order of the vertices matters." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:390 +msgid "Change the attributes of a feature" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:390 +msgid "The attributes of the point are changed in the current layer only." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:390 +msgid "No effect." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:391 +msgid "Add a new feature" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:391 +msgid "" +"A new point is added at the end of the list of features, for this layer " +"and all other layers. Its attributes are set to the values of the new " +"feature." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:391 +msgid "" +"The operation is only allowed if the new feature has the same number of " +"vertices as the other features in the layer. The vertices are checked to " +"see if they currently exist in the set of points. A vertex is considered " +"equal to a point if its distance is less than some maximum distance, " +"approximately equal to 1/1000\\ :sup:`th` of the average distance between" +" two points in the points layers. When a corresponding point is found, it" +" is used as a vertex for the element. If no point is found, a new is " +"created in all associated layers." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:392 +msgid "Delete a feature" +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:392 +msgid "" +"The point is removed from the current layer and all point layers in the " +"datasource. All elements using this point as a vertex are also removed " +"from all element layers in the datasource." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:392 +msgid "" +"The element is removed from the current layer and all element layers in " +"the datasource." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:395 +msgid "" +"Typically, this implementation of operations is exactly what you'll " +"expect. For example, ogr2ogr can be used to reproject the file without " +"changing the inner link between points and elements." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:399 +msgid "" +"It should be noted that update operations on Selafin datasources are very" +" slow. This is because the format does no allow for quick insertions or " +"deletion of features and the file must be recreated for each operation." +msgstr "" + +#: ../../source/drivers/vector/selafin.rst:415 +msgid "" +"There is no SRS specification in the Selafin standard. The implementation" +" of SRS is an addition of the driver and stores the SRS in an unused data" +" field in the file. Future software using the Selafin standard may use " +"this field and break the SRS specification. In this case, Selafin files " +"will still be readable by the driver, but their writing will overwrite a " +"value which may have another purpose." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:6 +msgid "ESRI Shapefile" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:10 +msgid "" +"All varieties of ESRI Shapefiles should be available for reading, " +"creation and editing. The driver can also handle standalone DBF files " +"without associated .shp files." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:14 +msgid "" +"Normally the OGR Shapefile driver treats a whole directory of shapefiles " +"as a dataset, and a single shapefile within that directory as a layer. In" +" this case the directory name should be used as the dataset name. " +"However, it is also possible to use one of the files (.shp, .shx or .dbf)" +" in a shapefile set as the dataset name, and then it will be treated as a" +" dataset with one layer." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:21 +msgid "" +"Note that when reading a Shapefile of type SHPT_ARC, the corresponding " +"layer will be reported as of type wkbLineString, but depending on the " +"number of parts of each geometry, the actual type of the geometry for " +"each feature can be either OGRLineString or OGRMultiLineString. The same " +"applies for SHPT_POLYGON shapefiles, reported as layers of type " +"wkbPolygon, but depending on the number of parts of each geometry, the " +"actual type can be either OGRPolygon or OGRMultiPolygon." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:29 +msgid "" +"Measures (M coordinate) are supported. A Shapefile with measures is " +"created if the specified geometry type is measured or an appropriate " +"layer creation option is used. When a shapefile which may have measured " +"geometries is opened, the first shape is examined and if it uses " +"measures, the geometry type of the layer is set accordingly. This " +"behavior can be changed with the ADJUST_GEOM_TYPE open option." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:37 +msgid "" +"MultiPatch files are read and each patch geometry is turned into a TIN or" +" a GEOMETRYCOLLECTION of TIN representation for fans and meshes." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:40 +msgid "" +"If a .prj files in old Arc/Info style or new ESRI OGC WKT style is " +"present, it will be read and used to associate a projection with " +"features. Starting with GDAL 2.3, a match will be attempted with the EPSG" +" databases to identify the SRS of the .prj with an entry in the catalog." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:46 +msgid "" +"The read driver assumes that multipart polygons follow the specification," +" that is to say the vertices of outer rings should be oriented clockwise " +"on the X/Y plane, and those of inner rings counterclockwise. If a " +"Shapefile is broken w.r.t. that rule, it is possible to define the " +"configuration option :config:`OGR_ORGANIZE_POLYGONS` to DEFAULT to " +"proceed to a full analysis based on topological relationships of the " +"parts of the polygons so that the resulting polygons are correctly " +"defined in the OGC Simple Feature convention." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:68 +msgid "" +"An attempt is made to read the code page setting in the .cpg file, or as " +"a fallback in the LDID/codepage setting from the .dbf file, and use it to" +" translate string fields to UTF-8 on read, and back when writing. LDID " +"\"87 / 0x57\" is treated as ISO-8859-1 which may not be appropriate. The " +":config:`SHAPE_ENCODING` configuration option may be used to override the" +" encoding interpretation of the shapefile with any encoding supported by " +"CPLRecode or to \"\" to avoid any recoding." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:76 +msgid "" +"Starting with GDAL 3.1, the following metadata items are available in the" +" \"SHAPEFILE\" domain:" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:79 +msgid "" +"**LDID_VALUE**\\ =integer: Raw LDID value from the DBF header. Only " +"present if this value is not zero." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:81 +msgid "" +"**ENCODING_FROM_LDID**\\ =string: Encoding name deduced from LDID_VALUE. " +"Only present if LDID_VALUE is present" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:83 +msgid "" +"**CPG_VALUE**\\ =string: Content of the .cpg file. Only present if the " +"file exists." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:85 +msgid "" +"**ENCODING_FROM_CPG**\\ =string: Encoding name deduced from CPG_VALUE. " +"Only present if CPG_VALUE is present" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:87 +msgid "" +"**SOURCE_ENCODING**\\ =string: Encoding used by GDAL to encode/recode " +"strings. If the user has provided the :config:`SHAPE_ENCODING` " +"configuration option or ``ENCODING`` open option have been provided " +"(included to empty value), then their value is used to fill this metadata" +" item. Otherwise it is equal to ENCODING_FROM_CPG if it is present. " +"Otherwise it is equal to ENCODING_FROM_LDID." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:95 +msgid "Spatial and attribute indexing" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:97 +msgid "" +"The OGR Shapefile driver supports spatial indexing and a limited form of " +"attribute indexing." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:100 +msgid "" +"The spatial indexing uses the same .qix quadtree spatial index files that" +" are used by UMN MapServer. Spatial indexing can accelerate spatially " +"filtered passes through large datasets to pick out a small area quite " +"dramatically." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:105 +msgid "" +"It can also use the ESRI spatial index files (.sbn / .sbx), but writing " +"them is not supported currently." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:108 +msgid "" +"To create a spatial index (in .qix format), issue a SQL command of the " +"form" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:115 +msgid "" +"where optional DEPTH specifier can be used to control number of index " +"tree levels generated. If DEPTH is omitted, tree depth is estimated on " +"basis of number of features in a shapefile and its value ranges from 1 to" +" 12." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:120 +msgid "To delete a spatial index issue a command of the form" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:126 +msgid "" +"Otherwise, the `MapServer <http://mapserver.org>`__ shptree utility can " +"be used:" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:133 +msgid "" +"More information is available about this utility at the `MapServer " +"shptree page <http://mapserver.org/utilities/shptree.html>`__" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:136 +msgid "" +"Currently the OGR Shapefile driver only supports attribute indexes for " +"looking up specific values in a unique key column. To create an attribute" +" index for a column issue an SQL command of the form \"CREATE INDEX ON " +"tablename USING fieldname\". To drop the attribute indexes issue a " +"command of the form \"DROP INDEX ON tablename\". The attribute index will" +" accelerate WHERE clause searches of the form \"fieldname = value\". The " +"attribute index is actually stored as a mapinfo format index and is not " +"compatible with any other shapefile applications." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:148 +msgid "" +"The Shapefile driver treats a directory as a dataset, and each Shapefile " +"set (.shp, .shx, and .dbf) as a layer. The dataset name will be treated " +"as a directory name. If the directory already exists it is used and " +"existing files in the directory are ignored. If the directory does not " +"exist it will be created." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:154 +msgid "" +"As a special case attempts to create a new dataset with the extension " +".shp will result in a single file set being created instead of a " +"directory." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:158 +msgid "" +"ESRI shapefiles can only store one kind of geometry per layer " +"(shapefile). On creation this is may be set based on the source file (if " +"a uniform geometry type is known from the source driver), or it may be " +"set directly by the user with the layer creation option SHPT (shown " +"below). If not set the layer creation will fail. If geometries of " +"incompatible types are written to the layer, the output will be " +"terminated with an error." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:166 +msgid "" +"Note that this can make it very difficult to translate a mixed geometry " +"layer from another format into Shapefile format using ogr2ogr, since " +"ogr2ogr has no support for separating out geometries from a source layer." +" See the `FAQ " +"<http://trac.osgeo.org/gdal/wiki/FAQVector#HowdoItranslateamixedgeometryfiletoshapefileformat>`__" +" for a solution." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:173 +msgid "" +"Shapefile feature attributes are stored in an associated .dbf file, and " +"so attributes suffer a number of limitations:" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:176 +msgid "" +"Attribute names can only be up to 10 characters long. The OGR Shapefile " +"driver tries to generate unique field names. Successive duplicate field " +"names, including those created by truncation to 10 characters, will be " +"truncated to 8 characters and appended with a serial number from 1 to 99." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:184 +msgid "a → a, a → a_1, A → A_2;" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:185 +msgid "abcdefghijk → abcdefghij, abcdefghijkl → abcdefgh_1" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:187 +msgid "" +"Only Integer, Integer64, Real, String and Date (not DateTime, just " +"year/month/day) field types are supported. The various list, and binary " +"field types cannot be created." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:191 +msgid "" +"The field width and precision are directly used to establish storage size" +" in the .dbf file. This means that strings longer than the field width, " +"or numbers that don't fit into the indicated field format will suffer " +"truncation." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:196 +msgid "" +"Integer fields without an explicit width are treated as width 9, and " +"extended to 10 or 11 if needed." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:199 +msgid "" +"Integer64 fields without an explicit width are treated as width 18, and " +"extended to 19 or 20 if needed." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:202 +msgid "" +"Real (floating point) fields without an explicit width are treated as " +"width 24 with 15 decimal places of precision." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:205 +msgid "String fields without an assigned width are treated as 80 characters." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:207 +msgid "" +"Also, .dbf files are required to have at least one field. If none are " +"created by the application an \"FID\" field will be automatically created" +" and populated with the record number." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:211 +msgid "" +"The OGR shapefile driver supports rewriting existing shapes in a " +"shapefile as well as deleting shapes. Deleted shapes are marked for " +"deletion in the .dbf file, and then ignored by OGR. To actually remove " +"them permanently (resulting in renumbering of FIDs) invoke the SQL " +"'REPACK <tablename>' via the datasource ExecuteSQL() method." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:217 +msgid "" +"REPACK will also result in .shp being rewritten if a feature geometry has" +" been modified with SetFeature() and resulted in a change of the size the" +" binary encoding of the geometry in the .shp file." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:222 +msgid "" +"Starting with GDAL 2.2, REPACK is also done automatically at file " +"closing, or at FlushCache()/SyncToDisk() time, since shapefiles with " +"holes can cause interoperability issues with other software." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:229 +msgid "" +"The driver knows to auto-extend string and integer fields (up to the 255 " +"bytes limit imposed by the DBF format) to dynamically accommodate for the" +" length of the data to be inserted." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:233 +msgid "" +"It is also possible to force a resize of the fields to the optimal width " +"by issuing a SQL 'RESIZE <tablename>' via the datasource ExecuteSQL() " +"method. This is convenient in situations where the default column width " +"(80 characters for a string field) is bigger than necessary." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:239 +msgid "Spatial extent" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:241 +msgid "" +"Shapefiles store the layer spatial extent in the .SHP file. The layer " +"spatial extent is automatically updated when inserting a new feature in a" +" shapefile. However when updating an existing feature, if its previous " +"shape was touching the bounding box of the layer extent but the updated " +"shape does not touch the new extent, the computed extent will not be " +"correct. It is then necessary to force a recomputation by invoking the " +"SQL 'RECOMPUTE EXTENT ON <tablename>' via the datasource ExecuteSQL() " +"method. The same applies for the deletion of a shape." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:253 +msgid "" +"Geometry: The Shapefile format explicitly uses 32bit offsets and so " +"cannot go over 8GB (it actually uses 32bit offsets to 16bit words), but " +"the OGR shapefile implementation has a limitation to 4GB." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:260 +msgid "" +"However, for compatibility with other software implementation, it is not " +"recommended to use a file size over 2GB for both .SHP and .DBF files." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:263 +msgid "" +"The 2GB_LIMIT=YES layer creation option can be used to strictly enforce " +"that limit. For update mode, the :config:`SHAPE_2GB_LIMIT` configuration " +"option can be set to YES for similar effect. If nothing is set, a warning" +" will be emitted when the 2GB limit is reached." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:271 +msgid "" +"Starting with GDAL 3.1, the driver can also support reading, creating and" +" editing .shz files (ZIP files containing the .shp, .shx, .dbf and other " +"side-car files of a single layer) and .shp.zip files (ZIP files contains " +"one or several layers). Creation and editing involves the creation of " +"temporary files." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:427 +msgid "" +"Starting with GDAL 3.7, for Polygon/MultiPolygon, the default value is " +"NO, with the effect that the winding order of rings will be determined " +"from the outer/inner rings of the input Polygon/MultiPolygon, and not as " +"a post process topological analysis like done in previous GDAL versions, " +"which could cause troubles for non-planar 3D geometries." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:457 +msgid "" +"A merge of two shapefiles 'file1.shp' and 'file2.shp' into a new file " +"'file_merged.shp' is performed like this:" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:465 +msgid "" +"The second command is opening file_merged.shp in update mode, and trying " +"to find existing layers and append the features being copied." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:468 +msgid "The -nln option sets the name of the layer to be copied to." +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:470 +msgid "Building a spatial index :" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:476 +msgid "Resizing columns of a DBF file to their optimal size :" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:486 +msgid "`Shapelib Page <http://shapelib.maptools.org/>`__" +msgstr "" + +#: ../../source/drivers/vector/shapefile.rst:487 +msgid "" +"`User Notes on OGR Shapefile Driver " +"<http://trac.osgeo.org/gdal/wiki/UserDocs/Shapefiles>`__" +msgstr "" + +#: ../../source/drivers/vector/sosi.rst:7 +msgid "SOSI" +msgstr "" + +#: ../../source/drivers/vector/sosi.rst:11 +msgid "This driver requires the FYBA library." +msgstr "" + +#: ../../source/drivers/vector/sosi.rst:16 +msgid "" +"|about-open-options| Starting with GDAL 3.1, the following open options " +"can be specified:" +msgstr "" + +#: ../../source/drivers/vector/sosi.rst:31 +msgid "" +"This example will convert a sosi file to a shape a file where all " +"duplicate fields in a feature will be appended with a comma between." +msgstr "" + +#: ../../source/drivers/vector/sosi.rst:37 +msgid "" +"This example will convert a sosi file to a shape a file where only " +"duplicates for BEITEBRUKERID and OPPHAV will appended with a comma " +"between." +msgstr "" + +#: ../../source/drivers/vector/sosi.rst:43 +msgid "" +"This example will convert a sosi file to a shape a file where for " +"BEITEBRUKERID and OPPHAV will be appended with a semicolon and comma " +"between" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:10 +msgid "" +"OGR optionally supports spatial and non-spatial tables stored in SQLite " +"3.x database files. SQLite is a \"light weight\" single file based RDBMS " +"engine with fairly complete SQL semantics and respectable performance." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:14 +msgid "" +"The driver can handle \"regular\" SQLite databases, as well as Spatialite" +" databases (spatial enabled SQLite databases). The type of an existing " +"database can be checked from the SQLITE debug info value \"OGR style " +"SQLite DB found/ SpatiaLite DB found/SpatiaLite v4 DB found\" obtained by" +" running ``ogrinfo db.sqlite --debug on``" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:20 +msgid "" +"Starting with GDAL 2.2, the SQLite driver can also read databases with " +":ref:`RasterLite2 raster coverages <raster.rasterlite2>`." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:23 +msgid "" +"The SQLite database is essentially typeless, but the SQLite driver will " +"attempt to classify attributes field as text, integer or floating point " +"based on the contents of the first record in a table. Datetime field " +"types are also handled." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:28 +msgid "" +"Starting with GDAL 2.2, the \"JSonStringList\", \"JSonIntegerList\", " +"\"JSonInteger64List\" and \"JSonRealList\" SQLite declaration types are " +"used to map the corresponding OGR StringList, IntegerList, Integer64List " +"and RealList types. The field values are then encoded as JSON arrays, " +"with proper CSV escaping." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:34 +msgid "" +"SQLite databases often do not work well over NFS, or some other networked" +" file system protocols due to the poor support for locking. It is safest " +"to operate only on SQLite files on a physical disk of the local system." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:39 +msgid "" +"SQLite is an optionally compiled in driver. It is not compiled in by " +"default." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:42 +msgid "" +"By default, SQL statements are passed directly to the SQLite database " +"engine. It's also possible to request the driver to handle SQL commands " +"with :ref:`OGR SQL <ogr_sql_dialect>` engine, by passing **\"OGRSQL\"** " +"string to the ExecuteSQL() method, as name of the SQL dialect." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:47 +msgid "" +"The :config:`OGR_SQLITE_SYNCHRONOUS` configuration option has been added." +" When set to OFF, this issues a 'PRAGMA synchronous = OFF' command to the" +" SQLite database. This has the advantage of speeding-up some write " +"operations (e.g. on EXT4 filesystems), but at the expense of data safety " +"w.r.t system/OS crashes. So use it carefully in production environments " +"and read the SQLite `related documentation " +"<http://www.sqlite.org/pragma.html#pragma_synchronous>`__." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:55 +msgid "" +"Any SQLite `pragma <http://www.sqlite.org/pragma.html>`__ can be " +"specified with the :config:`OGR_SQLITE_PRAGMA` configuration option. The " +"syntax is ``OGR_SQLITE_PRAGMA = " +"\"pragma_name=pragma_value[,pragma_name2=pragma_value2]*\"``." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:70 +msgid "\"Regular\" SQLite databases" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:72 +msgid "" +"The driver looks for a geometry_columns table laid out as defined loosely" +" according to OGC Simple Features standards, particularly as defined in " +"`FDO RFC 16 <http://trac.osgeo.org/fdo/wiki/FDORfc16>`__. If found it is " +"used to map tables to layers." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:77 +msgid "" +"If geometry_columns is not found, each table is treated as a layer. " +"Layers with a WKT_GEOMETRY field will be treated as spatial tables, and " +"the WKT_GEOMETRY column will be read as Well Known Text geometry." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:81 +msgid "" +"If geometry_columns is found, it will be used to lookup spatial reference" +" systems in the spatial_ref_sys table." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:84 +msgid "" +"While the SQLite driver supports reading spatial data from records, there" +" is no support for spatial indexing, so spatial queries will tend to be " +"slow (use Spatialite for that). Attributes queries may be fast, " +"especially if indexes are built for appropriate attribute columns using " +"the \"CREATE INDEX ON ( )\" SQL command." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:90 +msgid "" +"The driver also supports reading and writing the following non-linear " +"geometry types :CIRCULARSTRING, COMPOUNDCURVE, CURVEPOLYGON, MULTICURVE " +"and MULTISURFACE. Note: this is not true for Spatialite databases, since " +"those geometry types are not supported by current Spatialite versions." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:97 +msgid "Tables with multiple geometry columns" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:99 +msgid "" +"Layers with multiple geometry columns can be created, modified or read, " +"following new API described in :ref:`rfc-41`" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:103 +msgid "REGEXP operator" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:105 +msgid "" +"By default, the REGEXP operator has no implementation in SQLite. With " +"OGRbuilt against the PCRE library, the REGEXP operator is available in " +"SQL statements run by OGR." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:110 +msgid "Using the SpatiaLite library (Spatial extension for SQLite)" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:112 +msgid "" +"The SQLite driver can read and write SpatiaLite databases. Creating or " +"updating a spatialite database requires explicit linking against " +"SpatiaLite library (version >= 2.3.1). Explicit linking against " +"SpatiaLite library also provides access to functions provided by this " +"library, such as spatial indexes, spatial functions, etc..." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:118 +msgid "A few examples :" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:130 +msgid "Opening with 'VirtualShape:'" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:132 +msgid "(Require Spatialite support)" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:134 +msgid "" +"It is possible to open on-the-fly a shapefile as a VirtualShape with " +"Spatialite. The syntax to use for the datasource is " +"\"VirtualShape:/path/to/shapefile.shp\" (the shapefile must be a \"real\"" +" file)." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:139 +msgid "" +"This gives the capability to use the spatial operations of Spatialite " +"(note that spatial indexes on virtual tables are not available)." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:143 +msgid "The SQLite SQL dialect" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:145 +msgid "" +"The SQLite SQL engine can be used to run SQL queries on any OGR " +"datasource if using the :ref:`sql_sqlite_dialect`." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:149 +msgid "The VirtualOGR SQLite extension" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:151 +msgid "" +"The GDAL/OGR library can be loaded as a `SQLite extension " +"<http://www.sqlite.org/lang_corefunc.html#load_extension>`__. The " +"extension is loaded with the load_extension(gdal_library_name) SQL " +"function, where gdal_library_name is typically libgdal.so on Unix/Linux, " +"gdal110.dll on Windows, etc.." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:157 +msgid "" +"After the extension is loaded, a virtual table, corresponding to a OGR " +"layer, can be created with one of the following SQL statement :" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:169 +msgid "*datasource_name* is the connection string to any OGR datasource." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:170 +msgid "*update_mode* = 0 for read-only mode (default value) or 1 for update mode." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:172 +msgid "*layer_name* = the name of a layer of the opened datasource." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:173 +msgid "" +"*expose_ogr_style* = 0 to prevent the OGR_STYLE special from being " +"displayed (default value) or 1 to expose it." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:176 +msgid "" +"Note: *layer_name* does not need to be specified if the datasource has " +"only one single layer." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:179 +msgid "From the sqlite3 console, a typical use case is :" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:201 +msgid "" +"Alternatively, you can use the " +"*ogr_datasource_load_layers(datasource_name[, update_mode[, prefix]])* " +"function to automatically load all the layers of a datasource." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:216 +msgid "" +"Refer to the :ref:`sql_sqlite_dialect` for an overview of the " +"capabilities of VirtualOGR tables." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:222 +msgid "" +"The SQLite driver supports creating new SQLite database files, or adding " +"tables to existing ones." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:235 +msgid "" +"Relationship retrieval is supported. Relationships will be reported for " +"tables which utilize FOREIGN KEY constraints." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:238 +msgid "" +"Relationship creation is supported since GDAL 3.7, for one-to-many " +"relationships only." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:270 +msgid "" +"The other database must be of a type recognized by this driver, so its " +"geometry blobs are properly recognized (so typically not a GeoPackage " +"one)" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:274 +msgid "Database creation options" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:295 +msgid "" +"Please note: OGR must be linked against *libspatialite* in order to " +"support insert/write on SpatiaLite; if not, *read-only* mode is enforced." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:299 +msgid "" +"Attempting to perform any insert/write on SpatiaLite skipping the " +"appropriate library support simply produces broken (corrupted) DB-files." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:303 +msgid "" +"Important notice: when the underlying *libspatialite* is v.2.3.1 (or any " +"previous version) any Geometry will be casted to 2D [XY], because earlier" +" versions of this library are simply able to support 2D [XY] dimensions. " +"Version 2.4.0 (or any subsequent) is required in order to support 2.5D " +"[XYZ]." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:509 +msgid "" +"SQLite is a Transactional DBMS; while many INSERT statements are executed" +" in close sequence, BEGIN TRANSACTION and COMMIT TRANSACTION statements " +"have to be invoked appropriately (with the OGR_L_StartTransaction() / " +"OGR_L_CommitTransaction()) in order to get optimal performance. By " +"default, if no transaction is explicitly started, SQLite will autocommit " +"on every statement, which will be slow. If using ogr2ogr, its default " +"behavior is to COMMIT a transaction every 100000 inserted rows. The " +"**-gt** argument allows explicitly setting the number of rows for each " +"transaction." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:519 +msgid "" +"SQLite usually has a very minimal memory foot-print; just about 20MB of " +"RAM are reserved to store the internal Page Cache [merely 2000 pages]. " +"This value too may well be inappropriate under many circumstances, most " +"notably when accessing some really huge DB-file containing many tables " +"related to a corresponding Spatial Index. Explicitly setting a much more " +"generously dimensioned internal Page Cache may often help to get a " +"noticeably better performance. You can explicitly set the internal Page " +"Cache size using the configuration option :config:`OGR_SQLITE_CACHE` " +"*value* [*value* being measured in MB]; if your HW has enough available " +"RAM, defining a Cache size as big as 512MB (or even 1024MB) may sometimes" +" help a lot in order to get better performance." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:532 +msgid "" +"Setting the :config:`OGR_SQLITE_SYNCHRONOUS` configuration option to " +"*OFF* might also increase performance when creating SQLite databases " +"(although at the expense of integrity in case of interruption/crash )." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:537 +msgid "" +"If many source files will be collected into the same Spatialite table, it" +" can be much faster to initialize the table without a spatial index by " +"using -lco :lco:`SPATIAL_INDEX=NO` and to create spatial index with a " +"separate command after all the data are appended. Spatial index can be " +"created with ogrinfo command" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:551 +msgid "" +"If a database has gone through editing operations, it might be useful to " +"run a `VACUUM <https://sqlite.org/lang_vacuum.html>`__ query to compact " +"and optimize it." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:563 +msgid "Convert a non-spatial SQLite table into a GeoPackage:" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:579 +msgid "Perform a join between 2 SQLite/Spatialite databases:" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:590 +msgid "" +"Development of the OGR SQLite driver was supported by `DM Solutions Group" +" <http://www.dmsolutions.ca/>`__ and `GoMOOS <http://www.gomoos.org/>`__." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:593 +msgid "" +"Full support for SpatiaLite was contributed by A.Furieri, with funding " +"from `Regione Toscana <http://www.regione.toscana.it/>`__" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:599 +msgid "`http://www.sqlite.org <http://www.sqlite.org/>`__: Main SQLite page." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:600 +msgid "" +"https://www.gaia-gis.it/fossil/libspatialite/index: SpatiaLite extension " +"to SQLite." +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:601 +msgid "" +"`FDO RFC 16 <http://trac.osgeo.org/fdo/wiki/FDORfc16>`__: FDO Provider " +"for SQLite" +msgstr "" + +#: ../../source/drivers/vector/sqlite.rst:603 +msgid ":ref:`RasterLite2 driver <raster.rasterlite2>`" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:4 +msgid "SVG - Scalable Vector Graphics" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:6 +msgid "SVG" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:10 +msgid "" +"OGR has support for SVG reading (if GDAL is built with *expat* library " +"support)." +msgstr "" + +#: ../../source/drivers/vector/svg.rst:13 +msgid "" +"Currently, it will only read SVG files that are the output from Cloudmade" +" Vector Stream Server" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:16 +msgid "All coordinates are relative to the Pseudo-mercator SRS (EPSG:3857)." +msgstr "" + +#: ../../source/drivers/vector/svg.rst:18 +msgid "The driver will return 3 layers :" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:20 +msgid "points" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:21 +msgid "lines" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:22 +msgid "polygons" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:34 +msgid "`W3C SVG page <http://www.w3.org/TR/SVG/>`__" +msgstr "" + +#: ../../source/drivers/vector/svg.rst:35 +msgid "" +"`Cloudmade vector documentation <http://developers.cloudmade.com/wiki" +"/vector-stream-server/Documentation>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:4 +msgid "Storage and eXchange Format - SXF" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:10 +msgid "" +"This driver reads SXF files, open format often associated with Russian " +"GIS Software Panorama." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:13 +msgid "" +"The driver is read only, but supports deletion of data source. The driver" +" supports SXF binary files version 3.0 and higher." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:16 +msgid "The SXF layer support the following capabilities:" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:18 +msgid "Strings as UTF8" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:19 +msgid "Random Read" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:20 +msgid "Fast Feature Count" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:21 +msgid "Fast Get Extent" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:22 +msgid "Fast Set Next By Index" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:24 +msgid "" +"The driver uses classifiers (RSC files) to map feature from SXF to " +"layers. Features that do not belong to any layer are put to the layer " +"named \"Not_Classified\". The layers with zero features are not present " +"in data source." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:29 +msgid "" +"To be used automatically, the RSC file should have the same name as SXF " +"file. User can provide RSC file path using config option " +"**SXF_RSC_FILENAME**. This config option overrides the use of same name " +"RSC." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:34 +msgid "" +"The RSC file usually stores long and short layer name. The long name is " +"usually in Russian, and short in English. The **SXF_LAYER_FULLNAME** " +"config option allows choosing which layer names to use. If " +"SXF_LAYER_FULLNAME is TRUE - the driver uses long names, if FALSE - " +"short." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:40 +msgid "" +"The attributes are read from SXF file. Maximum number of fields is " +"created for the same layer features with different number of attributes. " +"If attribute has a code mapped to RSC file, driver adds only the code " +"(don't get real value from RSC, as the value type may differ from field " +"type)." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:46 +msgid "" +"If config option **SXF_SET_VERTCS** set to ON, the layers spatial " +"reference will include vertical coordinate system description if exist." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:49 +msgid "Since GDAL 3.1 config options can be passed as driver open options." +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:61 +msgid "`Panorama web page <http://gisinfo.ru>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:62 +msgid "" +"`SXF binary format description v.4 (rus) - pdf " +"<http://gistoolkit.ru/download/doc/sxf4bin.pdf>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:64 +msgid "" +"`SXF binary format description v.4 (rus) - doc " +"<http://gistoolkit.ru/download/classifiers/formatsxf.zip>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:66 +msgid "" +"`SXF format description v.3 (rus) <http://loi.sscc.ru/gis/formats/Format-" +"geo/sxf/sxf3-231.txt>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:68 +msgid "" +"`RSC format description (rus) " +"<http://gistoolkit.ru/download/classifiers/formatrsc.zip>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:70 +msgid "" +"`Test spatial data in SXF format (rus) " +"<http://www.gisinfo.ru/price/price_map.htm>`__" +msgstr "" + +#: ../../source/drivers/vector/sxf.rst:72 +msgid "" +"`Some RSC files (rus) " +"<http://www.gisinfo.ru/classifiers/classifiers.htm>`__" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:6 +msgid "TIGER" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:10 +msgid "TIGER/Line file sets are support for read access." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:12 +msgid "" +"TIGER/Line files are a digital database of geographic features, such as " +"roads, railroads, rivers, lakes, political boundaries, census statistical" +" boundaries, etc. covering the entire United States. The data base " +"contains information about these features such as their location in " +"latitude and longitude, the name, the type of feature, address ranges for" +" most streets, the geographic relationship to other features, and other " +"related information. They are the public product created from the Census " +"Bureau's TIGER (Topologically Integrated Geographic Encoding and " +"Referencing) data base of geographic information. TIGER was developed at " +"the Census Bureau to support the mapping and related geographic " +"activities required by the decennial census and sample survey programs." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:24 +msgid "" +"Note that the TIGER/Line product does not include census demographic " +"statistics. Those are sold by the Census Bureau in a separate format (not" +" directly supported by FME), but those statistics do relate back to " +"census blocks in TIGER/Line files." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:29 +msgid "" +"To open a TIGER/Line dataset, select the directory containing one or more" +" sets of data files. The regions are counties, or county equivalents. " +"Each county consists of a series of files with a common basename, and " +"different extensions. For instance, county 1 in state 26 (Michigan) " +"consists of the following file set in Tiger98." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:55 +msgid "" +"The TIGER/Line coordinate system is hardcoded to NAD83 lat/long degrees. " +"This should be appropriate for all recent years of TIGER/Line production." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:59 +msgid "There is no update or creation support in the TIGER/Line driver." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:61 +msgid "" +"The reader was implemented for TIGER/Line 1998 files, but some effort has" +" gone into ensuring compatibility with 1992, 1995, 1997, 1999, 2000, " +"2002, 2003 and 2004 TIGER/Line products as well. The 2005 products have " +"also been reported to work fine. It is believe that any TIGER/Line " +"product from the 1990's should work with the reader, with the possible " +"loss of some version specific information." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:76 +msgid "Feature Representation" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:78 +msgid "" +"With a few exceptions, a feature is created for each record of a " +"TIGER/Line data file. Each file (i.e. .RT1, .RTA) is translated to an " +"appropriate OGR feature type, with attribute names matching those in the " +"TIGER/Line product manual." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:83 +msgid "" +"The TIGER/Line RT (record type), and VERSION attributes are generally " +"discarded, but the MODULE attribute is added to each feature. The MODULE " +"attribute contains the basename (eg. TGR26001) of the county module from " +"which the feature originated. For some keys (such as LAND, POLYID, and " +"CENID) this MODULE attribute is needed to make the key unique when the " +"dataset (directory) consists of more than one county of data." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:90 +msgid "" +"Following is a list of feature types, and their relationship to the " +"TIGER/Line product." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:94 +msgid "CompleteChain" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:96 +msgid "" +"A CompleteChain is a polyline with an associated TLID (TIGER/Line ID). " +"The CompleteChain features are established from a type 1 record (Complete" +" Chain Basic Data Record), and if available it is associated type 3 " +"record (Complete Chain Geographic Entity Codes). As well, any type 2 " +"records (Complete Chain Shape Coordinates) available are used to fill in " +"intermediate shape points on the arc. The TLID is the primary key, and is" +" unique within the entire national TIGER/Line coverage." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:104 +msgid "These features always have a line geometry." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:107 +msgid "AltName" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:109 +msgid "" +"These features are derived from the type 4 record (Index to Alternate " +"Feature Identifiers), and relate a TLID to 1 to 4 alternate feature name " +"numbers (the FEAT attribute) which are kept separately as FeatureIds " +"features. The standard reader pipeline attaches the names from the " +"FeatureIds features as array attributes ALT_FEDIRS{}, ALT_FEDIRP{}, " +"ALT_FENAME{} and ALT_FETYPE{}. The ALT_FENAME{} is a list of feature " +"names associated with the TLID on the AltName feature." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:117 +msgid "" +"Note that zero, one or more AltName records may exist for a given TLID, " +"and each AltName record can contain between one and four alternate names." +" Because it is still very difficult to utilize AltName features to relate" +" altername names to CompleteChains, it is anticipated that the standard " +"reader pipeline for TIGER/Line files will be upgraded in the future, " +"resulting in a simplification of alternate names." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:124 +#: ../../source/drivers/vector/tiger.rst:136 +#: ../../source/drivers/vector/tiger.rst:147 +#: ../../source/drivers/vector/tiger.rst:170 +#: ../../source/drivers/vector/tiger.rst:179 +#: ../../source/drivers/vector/tiger.rst:201 +#: ../../source/drivers/vector/tiger.rst:210 +#: ../../source/drivers/vector/tiger.rst:222 +#: ../../source/drivers/vector/tiger.rst:239 +msgid "These features have no associated geometry." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:127 +msgid "FeatureIds" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:129 +msgid "" +"These features are derived from type 5 (Complete Chain Feature " +"Identifiers) records. Each feature contains a feature name (FENAME), and " +"it is associated feature id code (FEAT). The FEAT attribute is the " +"primary key, and is unique within the county module. FeatureIds have a " +"one to many relationship with AltName features, and KeyFeatures features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:139 +msgid "ZipCodes" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:141 +msgid "" +"These features are derived from type 6 (Additional Address Range and ZIP " +"Code Data) records. These features are intended to augment the ZIP Code " +"information kept directly on CompleteChain features, and there is a many " +"to one relationship between ZipCodes features and CompleteChain features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:150 +msgid "Landmarks" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:152 +msgid "" +"These features are derived from type 7 (Landmark Features) records. They " +"relate to point, or area landmarks. For area landmarks there is a one to " +"one relationship with an AreaLandmark record. The LAND attribute is the " +"primary key, and is unique within the county module." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:157 +msgid "" +"These features may have an associated point geometry. Landmarks " +"associated with polygons will not have the polygon geometry attached. It " +"would need to be collected (via the AreaLandmark feature) from a Polygon " +"feature." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:163 +msgid "AreaLandmarks" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:165 +msgid "" +"These features are derived from type 8 (Polygons Linked to Area " +"Landmarks) records. Each associates a Landmark feature (attribute LAND) " +"with a Polygon feature (attribute POLYID). This feature has a many to " +"many relationship with Polygon features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:173 +msgid "KeyFeatures" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:175 +msgid "" +"These features are derived from type 9 (Polygon Geographic Entity Codes) " +"records. They may be associated with a FeatureIds feature (via the FEAT " +"attribute), and a Polygon feature (via the POLYID attribute)." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:182 +msgid "Polygon" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:184 +msgid "" +"These features are derived from type A (Polygon Geographic Entity Codes) " +"records and if available the related type S (Polygon Additional " +"Geographic Entity Codes) records. The POLYID attribute is the primary " +"key, uniquely identifying a polygon within a county module." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:189 +msgid "" +"These features do not have any geometry associated with them as read by " +"the OGR TIGER driver. It needs to be externally related using the " +"PolyChainLink. The gdal/pymod/samples/tigerpoly.py script may be used to " +"read a TIGER dataset and extract the polygon layer **with geometry** as a" +" shapefile." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:196 +msgid "EntityNames" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:198 +msgid "These features are derived from type C (Geographic Entity Names) records." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:204 +msgid "IDHistory" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:206 +msgid "" +"These features are derived from type H (TIGER/Line ID History) records. " +"They can be used to trace the splitting, merging, creation and deletion " +"of CompleteChain features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:213 +msgid "PolyChainLink" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:215 +msgid "" +"These features are derived from type I (Link Between Complete Chains and " +"Polygons) records. They are normally all consumed by the standard reader " +"pipeline while attaching CompleteChain geometries to Polygon features to " +"establish their polygon geometries. PolyChainLink features have a many to" +" one relationship with Polygon features, and a one to one relationship " +"with CompleteChain features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:225 +msgid "PIP" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:227 +msgid "" +"These features are derived from type P (Polygon Internal Point) records. " +"They relate to a Polygon feature via the POLYID attribute, and can be " +"used to establish an internal point for Polygon features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:231 +msgid "These features have a point geometry." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:234 +msgid "ZipPlus4" +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:236 +msgid "" +"These features are derived from type Z (ZIP+4 Codes) records. ZipPlus4 " +"features have a many to one relationship with CompleteChain features." +msgstr "" + +#: ../../source/drivers/vector/tiger.rst:244 +msgid "" +"http://www.census.gov/geo/www/tiger/: More information on the TIGER/Line " +"file format, and data product can be found on this U.S. Census web page." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:5 +msgid "TileDB -- TileDB vector" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:13 +msgid "GDAL can read and write TileDB sparse arrays containing vector data." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:26 +msgid "Supported datasets" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:28 +msgid "" +"The driver can read TileDB sparse arrays that contain at least 2 " +"dimensions of type Float64. By default dimensions names ``_X`` and ``_Y``" +" are looked up, but this can be customized with the :oo:`DIM_X` and " +":oo:`DIM_Y` open options." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:32 +msgid "" +"Attributes (or extra dimensions) of the following TileDB data types are " +"recognized as OGR fields: Bool, Int16, Int32, Int64, Float32, Float64, " +"String_ASCII, String_UTF8, Blob, varying size UInt8 (as Binary), " +"DateTime_Day, DateTime_MS, Time_MS. Attributes of other data types will " +"be ignored." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:37 +msgid "" +"If a ``wkb_geometry`` named attribute of type Binary is found, it is used" +" as the geometry column, and is assumed to contain WKB encoded " +"geometries. If there is no such column, Point geometries are assumed and " +"the X, Y (and optional Z) dimensions are used to create the corresponding" +" OGR point geometries." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:44 +msgid "Dataset connection string" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:46 +msgid "" +"Valid dataset connection strings are paths to a local or remote TileDB " +"sparse array, or to a local or remote TileDB group that contains TileDB " +"sparse arrays." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:52 +msgid "" +"The bounding box of OGR spatial filters is forwarded to the TileDB query " +"engine." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:54 +msgid "" +"OGR attribute filters are translated to TileDB query conditions for the " +"following elements:" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:58 +msgid "OR" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:59 +msgid "NOT" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:60 +msgid "" +"comparisons of the form \"attribute_name operator constant\" where " +"operator is ``=``, ``<>``, ``<``, ``<=``, ``>``, ``>=``" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:62 +msgid "attribute_name IS NULL" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:63 +msgid "attribute_name IS NOT NULL" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:64 +msgid "attribute_name IN (value1, ... valueN)" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:65 +msgid "attribute_name BETWEEN min_val AND max_val" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:67 +#, python-format +msgid "" +"Other OGR attribute filter elements may be used, but this may cause the " +"filter to be fully or partially evaluated on OGR side. For example, given" +" the filter \"int_attribute = 5 AND string_attribute LIKE '%foo%'\", the " +"condition on int_attribute will be translated as a TileDB query " +"condition, and the right side of the AND operation will be evaluated as a" +" post-filter on OGR side." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:74 +msgid "Arrow C Stream data interface" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:76 +msgid "" +"The driver has an efficient implementation of the :ref:`Arrow C Stream " +"data interface <vector_api_tut_arrow_stream>`" +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:79 +msgid "" +"The ``INCLUDE_FID=YES/NO`` and ``MAX_FEATURES_IN_BATCH=number`` options " +"of :cpp:func:`OGRLayer::GetArrowStream()` are supported. If " +"MAX_FEATURES_IN_BATCH is not specified, it defaults to the value of the " +"BATCH_SIZE open option." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:86 +msgid "" +"By default, when creating a layer, the driver will create a TileDB sparse" +" array at the location of the dataset connection string. Consequently " +"only one OGR layer can be created in that mode. If several layers need to" +" be created and accessible through a OGR dataset connection, a TileDB " +"group needs to be created to point to the different arrays (layers), by " +"specifying the :dsco:`CREATE_GROUP=YES` dataset creation option." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:93 +msgid "The driver supports appending features to exiting layers." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:95 +msgid "" +"The driver does not support adding new fields to a layer where features " +"have already been written." +msgstr "" + +#: ../../source/drivers/vector/tiledb.rst:242 +msgid ":ref:`TileDB raster <raster.tiledb>` documentation page" +msgstr "" + +#: ../../source/drivers/vector/topojson.rst:6 +msgid "TopoJSON" +msgstr "" + +#: ../../source/drivers/vector/topojson.rst:13 +msgid "" +"The driver can read the `TopoJSON format <https://github.com/topojson" +"/topojson-specification/blob/master/README.md>`__" +msgstr "" + +#: ../../source/drivers/vector/topojson.rst:31 +msgid "" +"Plain text file with TopoJSON data - identified from the file extension " +".json or .topojson" +msgstr "" + +#: ../../source/drivers/vector/topojson.rst:33 +msgid "Text passed directly and encoded in Topo JSON" +msgstr "" + +#: ../../source/drivers/vector/topojson.rst:35 +msgid "" +"Starting with GDAL 2.3, the URL/filename/text might be prefixed with " +"TopoJSON: to avoid any ambiguity with other drivers. Alternatively, " +"starting with GDAL 3.10, specifying the ``-if TopoJSON`` option to " +"command line utilities accepting it, or ``TopoJSON`` as the only value of" +" the ``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the " +"driver to recognize the passed URL/filename/text." +msgstr "" + +#: ../../source/drivers/vector/topojson.rst:46 +msgid "" +"`TopoJSON Format Specification <https://github.com/topojson/topojson-" +"specification/blob/master/README.md>`__" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:4 +msgid "VDV - VDV-451/VDV-452/INTREST Data Format" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:8 +msgid "VDV" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:12 +msgid "" +"This driver can read and create text files following the VDV-451 file " +"format, which is a text format similar to CSV files, potentially " +"containing several layers within the same file." +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:16 +msgid "It supports in particular reading 2 \"profiles\" :" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:18 +msgid "(read/write) VDV-452 standard for route network / timetable" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:19 +msgid "" +"(read/only) \"INTREST Data format\" used by the `Austrian official open " +"government street graph <https://www.data.gv.at/katalog/dataset/3fefc838" +"-791d-4dde-975b-a4131a54e7c5>`__" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:23 +msgid "" +"The generic reader/writer for VDV-451/VDV-452 can support arbitrarily " +"large files. For the INTREST data case, for combined layers in a single " +"file, the driver ingests the whole file in memory to reconstruct the Link" +" layer." +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:28 +msgid "" +"Interleave reading among layers is supported in files with multiple " +"layers." +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:43 +msgid "" +"The driver can create new layers (either in the same file, or in separate" +" files in the same directory). It can append a new layer into an existing" +" file, but it cannot append/edit/delete features to an existing layer, or" +" modify the attribute structure of an existing layer after features have " +"been written." +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:154 +msgid "" +"`VDV-451 file format <https://www.vdv.de/vdv-" +"schrift-451.pdfx?forced=false>`__ (German)" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:157 +msgid "" +"`VDV-452 data model " +"<https://www.vdv.de/service/downloads_onp.aspx?id=4328&forced=false>`__ " +"(German)" +msgstr "" + +#: ../../source/drivers/vector/vdv.rst:159 +msgid "" +"`Austrian INTREST data format " +"<https://gip.gv.at/assets/downloads/1908_dokumentation_gipat_ogd.pdf>`__ " +"(German)" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:4 +msgid "VFK - Czech Cadastral Exchange Data Format" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:6 +msgid "VFK" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:10 +msgid "" +"This driver reads VFK files, i.e. data in the *Czech cadastral exchange " +"data format*. The VFK file is recognized as an datasource with multiple " +"layers." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:14 +msgid "The driver is compiled only if GDAL is *built with SQLite support*." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:16 +msgid "" +"Points are represented as wkbPoints, lines and boundaries as " +"wkbLineStrings and areas as wkbPolygons. wkbMulti\\* features are not " +"used. Feature types cannot be mixed in one layer." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:30 +msgid "" +"|about-open-options| Starting with GDAL 2.3, the following open options " +"can be specified:" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:98 +msgid "Internal working and performance tweaking" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:100 +msgid "" +"If backend SQLite database already exists then the driver reads features " +"directly from the database and not from input VFK file given as an input " +"datasource. This causes significant performance gain when reading " +"features by the driver." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:105 +msgid "" +"The driver reads by default all data blocks from VFK file when building " +"backend SQLite database. When configuration option " +":config:`OGR_VFK_DB_READ_ALL_BLOCKS` =NO is given, the driver reads only " +"data blocks which are requested by the user. This can be useful when the " +"user want to process only part of VFK data." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:114 +msgid "" +"Data related to a single cadastral area is typically distributed in " +"multiple VFK files. Example below is based on `sample VFK files " +"<https://services.cuzk.cz/vfk/anonym/>`__ provided by the Czech State " +"Administration of Land Surveying and Cadastre. In order to process all " +"VFK files related to a single cadastral area (in example below with ID " +"602515), the configuration option :config:`OGR_VFK_DB_NAME` has to be " +"defined." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:133 +msgid "Datasource name" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:135 +msgid "Datasource name is a full path to the VFK file." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:137 +msgid "" +"The driver supports reading files managed by VSI Virtual File System API," +" which include \"regular\" files, as well as files in the /vsizip/, " +"/vsigzip/, and /vsicurl/ read-only domains." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:141 +msgid "" +"Since GDAL 2.2 also a full path to the backend SQLite database can be " +"used as an datasource. By default, such datasource is read by SQLite " +"driver. If configuration option :config:`OGR_VFK_DB_READ` =YES is given, " +"such datasource is opened by VFK driver instead." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:147 +msgid "Layer names" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:149 +msgid "VFK data blocks are used as layer names." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:155 +msgid "Attribute filter" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:157 +msgid "" +"An internal SQL engine is used to evaluate the expression. Evaluation is " +"done once when the attribute filter is set." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:161 +msgid "Spatial filter" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:163 +msgid "" +"Bounding boxes of features stored in topology structure are used to " +"evaluate if a features matches current spatial filter. Evaluation is done" +" once when the spatial filter is set." +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:168 +msgid "References" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:170 +msgid "" +"`OGR VFK Driver Implementation Issues " +"<https://www.researchgate.net/publication/238067945_OGR_VFK_Driver_Implementation_Issues>`__" +msgstr "" + +#: ../../source/drivers/vector/vfk.rst:172 +msgid "" +"`Czech cadastral exchange data format documentation " +"<http://www.cuzk.cz/Dokument.aspx?PRARESKOD=998&MENUID=0&AKCE=DOC:10-VF_ISKNTEXT>`__" +" (in Czech)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:4 +msgid "VRT -- Virtual Format" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:10 +msgid "" +"OGR Virtual Format is a driver that transforms features read from other " +"drivers based on criteria specified in an XML control file. It is " +"primarily used to derive spatial layers from flat tables with spatial " +"information in attribute columns. It can also be used to associate " +"coordinate system information with a datasource, merge layers from " +"different datasources into a single data source, or even just to provide " +"an anchor file for access to non-file oriented datasources." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:18 +msgid "The virtual files are currently normally prepared by hand." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:30 +msgid "" +"The CreateFeature(), SetFeature() and DeleteFeature() operations are " +"supported on a layer of a VRT dataset, if the following conditions are " +"met :" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:34 +msgid "the VRT dataset is opened in update mode" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:35 +msgid "the underlying source layer supports those operations" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:36 +msgid "the *SrcLayer* element is used (as opposed to the *SrcSQL* element)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:37 +msgid "" +"the FID of the VRT features is the same as the FID of the source " +"features, that is to say, the *FID* element is not specified" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:41 +msgid "Virtual File Format" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:43 +msgid "" +"The root element of the XML control file is **OGRVRTDataSource**. It has " +"an **OGRVRTLayer** (or **OGRVRTWarpedLayer** or **OGRVRTUnionLayer**) " +"child for each layer in the virtual datasource, and a **Metadata** " +"element." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:48 +msgid "" +"An XML schema of the OGR VRT format is provided in " +":source_file:`ogr/ogrsf_frmts/vrt/data/ogrvrt.xsd`. When GDAL is " +"configured with libXML2 support, that schema will be used to validate the" +" VRT documents. Non-conformities will be reported only as warnings. That " +"validation can be disabled by setting the :config:`GDAL_XML_VALIDATION` " +"configuration option to \"NO\"." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:56 +msgid "Metadata element" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:58 +msgid "" +"**Metadata** (optional): This element contains a list of metadata " +"name/value pairs associated with the dataset as a whole. It has <MDI> " +"(metadata item) subelements which have a \"key\" attribute and the value " +"as the data of the element. The Metadata element can be repeated multiple" +" times, in which case it must be accompanied with a \"domain\" attribute " +"to indicate the name of the metadata domain." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:66 +msgid "OGRVRTLayer element" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:68 +msgid "" +"A **OGRVRTLayer** element should have a **name** attribute with the layer" +" name, and may have the following subelements:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:71 +msgid "" +"**SrcDataSource** (mandatory): The value is the name of the datasource " +"that this layer will be derived from. The element may optionally have a " +"**relativeToVRT** attribute which defaults to \"0\", but if \"1\" " +"indicates that the source datasource should be interpreted as relative to" +" the virtual file. This can be any OGR supported dataset, including ODBC," +" CSV, etc. The element may also have a **shared** attribute to control " +"whether the datasource should be opened in shared mode. Defaults to OFF " +"for SrcLayer use and ON for SrcSQL use." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:80 +msgid "" +"**OpenOptions** (optional): This element may list a number of open " +"options as child elements of the form <OOI " +"key=\"key_name\">value_name</OOI>" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:84 +msgid "" +"**Metadata** (optional): This element contains a list of metadata " +"name/value pairs associated with the layer as a whole. It has <MDI> " +"(metadata item) subelements which have a \"key\" attribute and the value " +"as the data of the element. The Metadata element can be repeated multiple" +" times, in which case it must be accompanied with a \"domain\" attribute " +"to indicate the name of the metadata domain." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:91 +msgid "" +"**SrcLayer** (optional): The value is the name of the layer on the source" +" data source from which this virtual layer should be derived. If this " +"element isn't provided, then the SrcSQL element must be provided." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:95 +msgid "" +"**SrcSQL** (optional): An SQL statement to execute to generate the " +"desired layer result. This should be provided instead of the SrcLayer for" +" statement derived results. Some limitations may apply for SQL derived " +"layers. An optional **dialect** attribute can be specified on the SrcSQL " +"element to specify which SQL \"dialect\" should be used : possible values" +" are currently :ref:`OGRSQL <ogr_sql_dialect>` or :ref:`SQLITE " +"<sql_sqlite_dialect>`. If *dialect* is not specified, the default dialect" +" of the datasource will be used." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:105 +msgid "" +"**FID** (optional): Name of the source attribute column from which the " +"FID of features should be derived. If not provided, the FID of the source" +" features will be used directly." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:109 +msgid "Logic for GDAL >= 2.4: Different situations are possible:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:115 +msgid "" +"A FID column will be reported as source_field_name with the content of " +"source field source_field_name." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:122 +msgid "" +"A FID column will be reported as dest_field_name with the content of " +"source field source_field_name. dest_field_name can potentially be set to" +" the empty string." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:130 +msgid "" +"No FID column is reported. The FID value of VRT features is the FID value" +" of the source features." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:137 +msgid "" +"A FID column will be reported as dest_field_name with the content of the " +"implicit source FID column. The FID value of VRT features is the FID " +"value of the source features." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:141 +msgid "" +"Logic for GDAL < 2.4: The layer will report the FID column name only if " +"it is also reported as a regular field. A \"name\" attribute can be " +"specified on the FID element so that the FID column name is always " +"reported." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:146 +msgid "" +"**Style** (optional): Name of the attribute column from which the style " +"of features should be derived. If not provided, the style of the source " +"features will be used directly." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:150 +msgid "" +"**GeometryType** (optional): The geometry type to be assigned to the " +"layer. If not provided it will be taken from the source layer. The value " +"should be one of \"wkbNone\", \"wkbUnknown\", \"wkbPoint\", " +"\"wkbLineString\", \"wkbPolygon\", \"wkbMultiPoint\", " +"\"wkbMultiLineString\", \"wkbMultiPolygon\", or " +"\"wkbGeometryCollection\". Optionally \"25D\" may be appended to mark it " +"as including Z coordinates. Defaults to \"wkbUnknown\" indicating that " +"any geometry type is allowed." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:158 +msgid "" +"**LayerSRS** (optional): The value of this element is the spatial " +"reference to use for the layer. If not provided, it is inherited from the" +" source layer. The value may be WKT or any other input that is accepted " +"by the OGRSpatialReference::SetUserInput() method. If the value is NULL, " +"then no SRS will be used for the layer." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:164 +msgid "" +"**GeometryField** (optional): This element is used to define how the " +"geometry for features should be derived." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:167 +msgid "" +"The GeometryField element can be repeated as many times as necessary to " +"create multiple geometry fields. If no **GeometryField** element is " +"specified, all the geometry fields of the source layer will be exposed by" +" the VRT layer. In order not to expose any geometry field of the source " +"layer, you need to specify OGRVRTLayer-level **GeometryType** element to " +"wkbNone." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:174 +msgid "The following attributes can be defined:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:176 +msgid "" +"**name** = string (recommended, and mandatory if the VRT will expose " +"multiple geometry fields)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:178 +msgid "" +"Name that will be used to define the VRT geometry field name. If not set," +" empty string is used." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:181 +msgid "**encoding** = Direct/WKT/WKB/PointFromColumns (optional)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:183 +msgid "Type of geometry encoding." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:185 +msgid "" +"If the encoding is \"Direct\" or not specified, then the **field** " +"attribute must be set to the name of the source geometry field, if there " +"are multiple source geometry fields. If neither **encoding** nor " +"**field** are specified, it is assumed that the name of source geometry " +"field is the value of the **name** attribute." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:191 +msgid "" +"If the encoding is \"WKT\" or \"WKB\" then the **field** attribute must " +"be set to the name of the source field containing the WKT or WKB " +"geometry." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:194 +msgid "" +"If the encoding is \"PointFromColumns\" then the **x**, **y**, **z** and " +"**m** attributes must be set to the names of the columns to be used for " +"the X, Y, Z and M coordinates. The **z** and **m** attributes are " +"optional." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:198 +msgid "**field** = string (conditional)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:200 +msgid "" +"Name of the source field (or source geometry field for **encoding** = " +"Direct) from which this GeometryField should fetch geometries. This must " +"be set if **encoding** is WKT or WKB." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:204 +msgid "**x**, **y**, **z**, **m** = string (conditional)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:206 +msgid "" +"Name of the source fields for the X, Y, Z and M coordinates when " +"**encoding** = PointFromColumns" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:209 +msgid "**reportSrcColumn** = true/false (optional)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:211 +msgid "" +"Specify whether the source geometry fields (the fields set in the " +"**field**, **x**, **y**, **z**, **m** attributes) should also be included" +" as fields of the VRT layer. It defaults to true. If set to false, the " +"source geometry fields will only be used to build the geometry of the " +"features of the VRT layer." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:217 +msgid "" +"Note that reportSrcColumn=true is taken into account only if no explicit " +"**Field** element is defined and when **encoding** is not \"Direct\". If " +"at least one field is explicitly defined, and reporting of the source " +"geometry field is desired, an explicit **Field** element for it must be " +"defined." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:222 +msgid "**nullable** = true/false (optional)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:224 +msgid "" +"The optional **nullable** attribute can be used to specify whether the " +"geometry field is nullable. It defaults to \"true\"." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:228 +msgid "The following child elements of **GeometryField** can be defined:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:230 +msgid "" +"**GeometryType** (optional) : same syntax as OGRVRTLayer-level " +"**GeometryType**. Useful when there are multiple geometry fields." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:232 +msgid "" +"**SRS** (optional) : same syntax as OGRVRTLayer-level **LayerSRS** (note " +"SRS vs LayerSRS). Useful when there are multiple geometry fields." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:234 +msgid "" +"**SrcRegion** (optional) : same syntax as OGRVRTLayer-level " +"**SrcRegion**. Useful when there are multiple geometry fields." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:236 +msgid "" +"**ExtentXMin**, **ExtentYMin**, **ExtentXMax** and **ExtentXMax** " +"(optional) : same syntax as OGRVRTLayer-level elements of same name. " +"Useful when there are multiple geometry fields." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:239 +msgid "" +"**XYResolution** (optional, GDAL >= 3.9): Resolution for the coordinate " +"precision of the X and Y coordinates. Expressed in the units of the X and" +" Y axis of the SRS" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:242 +msgid "" +"**ZResolution** (optional, GDAL >= 3.9): Resolution for the coordinate " +"precision of the Z coordinates. Expressed in the units of the Z axis of " +"the SRS" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:245 +msgid "" +"**MResolution** (optional, GDAL >= 3.9): Resolution for the coordinate " +"precision of the M coordinates." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:249 +msgid "" +"**SrcRegion** (optional) : This element is used to define an initial " +"spatial filter for the source features. This spatial filter will be " +"combined with any spatial filter explicitly set on the VRT layer with the" +" SetSpatialFilter() method. The value of the element must be a valid WKT " +"string defining a polygon. An optional **clip** attribute can be set to " +"\"TRUE\" to clip the geometries to the source region, otherwise the " +"source geometries are not modified." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:257 +msgid "" +"**Field** (optional): One or more attribute fields may be defined with " +"Field elements. If no Field elements are defined, the fields of the " +"source layer/sql will be defined on the VRT layer. The Field may have the" +" following attributes:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:262 +msgid "**name** (required): the name of the field." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:263 +msgid "" +"**type**: the field type, one of \"Integer\", \"IntegerList\", \"Real\", " +"\"RealList\", \"String\", \"StringList\", \"Binary\", \"Date\", \"Time\"," +" or \"DateTime\". Defaults to \"String\"." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:266 +msgid "" +"**subtype**: the field subtype, one of \"None\", \"Boolean\", \"Int16\", " +"\"Float32\". Defaults to \"None\"." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:268 +msgid "**width**: the field width. Defaults to unknown." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:269 +msgid "**precision**: the field width. Defaults to zero." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:270 +msgid "" +"**src**: the name of the source field to be copied to this one. Defaults " +"to the value of \"name\"." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:272 +msgid "" +"**nullable** can be used to specify whether the field is nullable. It " +"defaults to \"true\"." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:274 +msgid "" +"**unique** can be used to specify whether the field has a unique " +"constraint. It defaults to \"false\". (GDAL >= 3.2)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:276 +msgid "**alternativeName**: the field alternative name. (GDAL >= 3.7)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:277 +msgid "**comment**: the field comment. (GDAL >= 3.7)" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:279 +msgid "" +"**FeatureCount** (optional) : This element is used to define the feature " +"count of the layer (when no spatial or attribute filter is set). This can" +" be useful on static data, when getting the feature count from the source" +" layer is slow." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:284 +#: ../../source/drivers/vector/vrt.rst:303 +msgid "" +"**ExtentXMin**, **ExtentYMin**, **ExtentXMax** and **ExtentXMax** " +"(optional) : Those elements are used to define the extent of the layer. " +"This can be useful on static data, when getting the extent from the " +"source layer is slow." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:290 +msgid "OGRVRTWarpedLayer element" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:292 +msgid "" +"A **OGRVRTWarpedLayer** element is used to do on-the-fly reprojection of " +"a source layer. It may have the following subelements:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:296 +msgid "" +"**OGRVRTLayer**, **OGRVRTWarpedLayer** or **OGRVRTUnionLayer** " +"(mandatory): the source layer to reproject." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:298 +msgid "" +"**SrcSRS** (optional): The value of this element is the spatial reference" +" to use for the layer before reprojection. If not specified, it is " +"deduced from the source layer." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:301 +msgid "" +"**TargetSRS** (mandatory): The value of this element is the spatial " +"reference to use for the layer after reprojection." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:307 +msgid "" +"**WarpedGeomFieldName** (optional) : The value of this element is the " +"geometry field name of the source layer to wrap. If not specified, the " +"first geometry field will be used. If there are several geometry fields, " +"only the one matching WarpedGeomFieldName will be warped; the other ones " +"will be untouched." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:314 +msgid "OGRVRTUnionLayer element" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:316 +msgid "" +"A **OGRVRTUnionLayer** element is used to concatenate the content of " +"source layers. It should have a **name** and may have the following " +"subelements:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:320 +msgid "" +"**OGRVRTLayer**, **OGRVRTWarpedLayer** or **OGRVRTUnionLayer** (mandatory" +" and may be repeated): a source layer to add in the union." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:322 +msgid "" +"**PreserveSrcFID** (optional) : may be ON or OFF. If set to ON, the FID " +"from the source layer will be used, otherwise a counter will be used. " +"Defaults to OFF." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:325 +msgid "" +"**SourceLayerFieldName** (optional) : if specified, an additional field " +"(named with the value of SourceLayerFieldName) will be added in the layer" +" field definition. For each feature, the value of this field will be set " +"with the name of the layer from which the feature comes from." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:330 +msgid "" +"**GeometryType** (optional) : see above for the syntax. If not specified," +" the geometry type will be deduced from the geometry type of all source " +"layers." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:333 +msgid "" +"**LayerSRS** (optional) : see above for the syntax. If not specified, the" +" SRS will be the SRS of the first source layer." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:335 +msgid "" +"**FieldStrategy** (optional, exclusive with **Field** or " +"**GeometryField**) : may be **FirstLayer** to use the fields from the " +"first layer found, **Union** to use a super-set of all the fields from " +"all source layers, or **Intersection** to use a sub-set of all the common" +" fields from all source layers. Defaults to **Union**." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:340 +msgid "" +"**Field** (optional, exclusive with **FieldStrategy**) : see above for " +"the syntax. Note: the src attribute is not supported in the context of a " +"OGRVRTUnionLayer element (field names are assumed to be identical)." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:344 +msgid "" +"**GeometryField** (optional, exclusive with **FieldStrategy**): the " +"**name** attribute and the following sub-elements **GeometryType**, " +"**SRS** and **Extent[X|Y][Min|Max]** are available." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:347 +msgid "**FeatureCount** (optional) : see above for the syntax" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:348 +msgid "" +"**ExtentXMin**, **ExtentYMin**, **ExtentXMax** and **ExtentXMax** " +"(optional) : see above for the syntax" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:352 +msgid "Example: ODBC Point Layer" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:354 +msgid "" +"In the following example (disease.ovf) the worms table from the ODBC " +"database DISEASE is used to form a spatial layer. The virtual file uses " +"the \"x\" and \"y\" columns to get the spatial location. It also marks " +"the layer as a point layer, and as being in the WGS84 coordinate system." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:372 +msgid "Example: Renaming attributes" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:374 +msgid "" +"It can be useful in some circumstances to be able to rename the field " +"names from a source layer to other names. This is particularly true when " +"you want to transcode to a format whose schema is fixed, such as GPX " +"(<name>, <desc>, etc.). This can be accomplished using SQL this way:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:388 +msgid "This can also be accomplished using explicit field definitions:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:403 +msgid "Example: Transparent spatial filtering" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:405 +msgid "" +"The following example will only return features from the source layer " +"that intersect the (0,40)-(10,50) region. Furthermore, returned " +"geometries will be clipped to fit into that region." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:419 +msgid "Example: Reprojected layer" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:421 +msgid "" +"The following example will return the source.shp layer reprojected to " +"EPSG:4326." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:436 +msgid "Example: Union layer" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:438 +msgid "" +"The following example will return a layer that is the concatenation of " +"source1.shp and source2.shp." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:455 +msgid "Example: SQLite/Spatialite SQL dialect" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:457 +msgid "" +"The following example will return four different layers which are " +"generated in a fly from the same polygon shapefile. The first one is the " +"shapefile layer as it stands. The second layer gives simplified polygons " +"by applying SpatiaLite function \"Simplify\" with parameter tolerance=10." +" In the third layer the original geometries are replaced by their convex " +"hulls. In the fourth layer SpatiaLite function PointOnSurface is used for" +" replacing the original geometries by points which are inside the " +"corresponding source polygons. Note that for using the last three layers " +"of this VRT file GDAL must be compiled with SQLite and SpatiaLite." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:488 +msgid "Example: Multiple geometry fields" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:490 +msgid "" +"The following example will expose all the attribute and geometry fields " +"of the source layer:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:501 +msgid "To expose only part (or all!) of the fields:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:522 +msgid "To reproject the 'pg_geom_field_2' geometry field to EPSG:4326:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:536 +msgid "" +"To make the union of several multi-geometry layers and keep only a few of" +" them:" +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:565 +msgid "" +"When the *GeometryField* is \"WKT\" spatial filtering is applied after " +"extracting all rows from the source datasource. Essentially that means " +"there is no fast spatial filtering on WKT derived geometries." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:568 +msgid "" +"When the *GeometryField* is \"PointFromColumns\", and a *SrcLayer* (as " +"opposed to *SrcSQL*) is used, and a spatial filter is in effect on the " +"virtual layer then the spatial filter will be internally translated into " +"an attribute filter on the X and Y columns in the *SrcLayer*. In cases " +"where fast spatial filtering is important it can be helpful to index the " +"X and Y columns in the source datastore, if that is possible. For " +"instance if the source is an RDBMS. You can turn off that feature by " +"setting the *useSpatialSubquery* attribute of the GeometryField element " +"to FALSE." +msgstr "" + +#: ../../source/drivers/vector/vrt.rst:577 +msgid "" +".vrt files starting with - <OGRVRTDataSource> open with ogrinfo, etc. - " +"<VRTDataset> open with gdalinfo, etc." +msgstr "" + +#: ../../source/drivers/vector/wasp.rst:4 +msgid "WAsP - WAsP .map format" +msgstr "" + +#: ../../source/drivers/vector/wasp.rst:6 +msgid "WAsP" +msgstr "" + +#: ../../source/drivers/vector/wasp.rst:10 +msgid "" +"This driver writes .map files to be used with WAsP. The only allowed " +"geometries are linestrings." +msgstr "" + +#: ../../source/drivers/vector/wasp.rst:61 +msgid "" +"Note that if not option is specified, the layer is assumed to be an " +"elevation layer where the elevation is the z-components of the " +"linestrings' points." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:4 +msgid "WFS - OGC WFS service" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:6 +msgid "WFS" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:10 +msgid "" +"This driver can connect to a OGC WFS service. It supports WFS 1.0, 1.1 " +"and 2.0 protocols. GDAL/OGR must be built with Curl support in order for " +"the WFS driver to be compiled. Usually WFS requests return results in GML" +" format, so the GML driver should generally be set-up for read support " +"(thus requiring GDAL/OGR to be built with Xerces or Expat support). It is" +" sometimes possible to use alternate underlying formats when the server " +"supports them (such as OUTPUTFORMAT=json)." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:18 +msgid "" +"The driver supports read-only services, as well as transactional ones " +"(WFS-T)." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:29 +msgid "" +"The minimal syntax to open a WFS datasource is : " +"*WFS:http://path/to/WFS/service* or " +"*http://path/to/WFS/service?SERVICE=WFS*" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:33 +msgid "" +"Starting with GDAL 3.10, specifying the ``-if WFS`` option to command " +"line utilities accepting it, or ``WFS`` as the only value of the " +"``papszAllowedDrivers`` of :cpp:func:`GDALOpenEx`, also forces the driver" +" to recognize the passed URL without the ``WFS:`` prefix." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:38 +msgid "" +"Additional optional parameters can be specified such as *TYPENAME*, " +"*VERSION*, *MAXFEATURES* (WFS < 2) or *COUNT* (WFS > 2) as specified in " +"WFS specification." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:41 +msgid "" +"The name provided to the TYPENAME parameter must be exactly the layer " +"name reported by OGR, in particular with its namespace prefix when its " +"exists. Note: several type names can be provided and separated by comma." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:45 +msgid "" +"It is also possible to specify the name of an XML file whose content " +"matches the following syntax (the <OGRWFSDataSource> element must be the " +"first bytes of the file):" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:55 +msgid "" +"Note: the URL must be XML-escaped, for example the *&* character must be " +"written as *&*" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:58 +msgid "" +"At the first opening, the content of the result of the *GetCapabilities* " +"request will be appended to the file, so that it can be cached for later " +"openings of the dataset. The same applies for the *DescribeFeatureType* " +"request issued to discover the field definition of each layer." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:63 +msgid "" +"The service description file has the following additional elements as " +"immediate children of the ``OGRWFSDataSource`` element that may be " +"optionally set." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:73 +msgid "**Version**: Set a specific WFS version to use (either 1.0.0 or 1.1.0)." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:75 +msgid "" +"**PagingAllowed**: Set to ON if paging must be enabled. See \"Request " +"paging\" section." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:77 +msgid "" +"**PageSize**: Page size when paging is enabled. See \"Request paging\" " +"section." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:79 +msgid "" +"**BaseStartIndex**: Base of the start index when paging is enabled (0 or " +"1). See \"Request paging\" section." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:81 +msgid "" +"**COOKIE**: HTTP cookies that are passed in HTTP requests, formatted as " +"COOKIE1=VALUE1; COOKIE2=VALUE2... Starting with GDAL 2.3, additional HTTP" +" headers can be sent by setting the :config:`GDAL_HTTP_HEADER_FILE` " +"configuration option to point to a filename of a text file with “key: " +"value” HTTP headers." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:88 +msgid "Request paging" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:90 +msgid "" +"The WFS driver will read the GML content as a stream instead as a whole " +"file, which will improve interactivity and help when the content cannot " +"fit into memory. This can be turned off by setting the " +":config:`OGR_WFS_USE_STREAMING` configuration option to NO if this is not" +" desirable (for example, when iterating several times on a layer that can" +" fit into memory). When streaming is enabled, GZip compression is also " +"requested. It has been observed that some WFS servers, that cannot do on-" +"the-fly compression, will cache on their side the whole content to be " +"sent before sending the first bytes on the wire. To avoid this, you can " +"set the :config:`CPL_CURL_GZIP` configuration option to NO." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:103 +msgid "Paging with WFS 2.0" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:105 +msgid "" +"The WFS driver will automatically detect if server supports paging, when " +"requesting a WFS 2.0 server. The page size (number of features fetched in" +" a single request) is limited to 100 by default when not declared by the " +"server. It can be changed by setting the :config:`OGR_WFS_PAGE_SIZE` " +"configuration option, or by specifying COUNT as a query parameter in the " +"URL of the connection string." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:112 +msgid "" +"If only the N first features must be downloaded and paging through the " +"whole layer is not desirable, the :config:`OGR_WFS_PAGING_ALLOWED` " +"configuration option should be set to OFF." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:116 +msgid "" +"Starting with GDAL 3.8, if the feature count is already known before " +"fetching the first feature, and the feature count is less than the page " +"size, then the WFS driver will not use paging (no ``STARTINDEX`` " +"parameter will be used in the requests). (This behavior improves " +"compatibility with Geoserver when datasources with no primary key.)" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:123 +msgid "Paging with WFS 1.0 or 1.1" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:125 +msgid "" +"Some servers (such as MapServer >= 6.0) support the use of STARTINDEX " +"that allows doing the requests per \"page\", and thus to avoid " +"downloading the whole content of the layer in a single request. Paging " +"was introduced in WFS 2.0.0 but servers may support it as an vendor " +"specific option also with WFS 1.0.0 and 1.1.0. The OGR WFS client will " +"use paging when the :config:`OGR_WFS_PAGING_ALLOWED` configuration option" +" is explicitly set to ON. The page size (number of features fetched in a " +"single request) is limited to 100 by default when not declared by the " +"server. It can be changed by setting the :config:`OGR_WFS_PAGE_SIZE` " +"configuration option." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:137 +msgid "" +"WFS 2.0.2 specification has clarified that the first feature in paging is" +" at index 0. But some server implementations of WFS paging have " +"considered that it was at index 1 (including MapServer <= 6.2). The " +"default base start index is 0, as mandated by the specification. The " +":config:`OGR_WFS_BASE_START_INDEX` configuration option can however be " +"set to 1 to be compatible with the server implementations that considered" +" the first feature to be at index 1." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:147 +msgid "Paging options" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:149 +msgid "" +"Those 3 options (:config:`OGR_WFS_PAGING_ALLOWED`, " +":config:`OGR_WFS_PAGE_SIZE`, :config:`OGR_WFS_BASE_START_INDEX`) can also" +" be set in a WFS XML description file with the elements of similar names " +"(PagingAllowed, PageSize, BaseStartIndex)." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:158 +msgid "" +"The driver will forward any spatial filter set with SetSpatialFilter() to" +" the server. It also makes its best effort to do the same for attribute " +"filters set with SetAttributeFilter() when possible (turning OGR SQL " +"language into OGC filter description). When this is not possible, it will" +" default to client-side only filtering, which can be a slow operation " +"because involving fetching all the features from the servers." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:166 +msgid "The following spatial functions can be used :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:168 +msgid "" +"the 8 spatial binary predicate: **ST_Equals, ST_Disjoint, ST_Touches, " +"ST_Contains, ST_Intersects, ST_Within, ST_Crosses and ST_Overlaps** that " +"take 2 geometry arguments. Typically the geometry column name, and a " +"constant geometry such as built with ST_MakeEnvelope or ST_GeomFromText." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:173 +msgid "**ST_DWithin(geom1,geom2,distance_in_meters)**" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:174 +msgid "**ST_Beyond(geom1,geom2,distance_in_meters)**" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:175 +msgid "" +"**ST_MakeEnvelope(xmin,ymin,xmax,ymax[,srs])**: to build an envelope. srs" +" can be an integer (an EPSG code), or a string directly set as the " +"srsName attribute of the gml:Envelope. GDAL will take care of needed axis" +" swapping, so coordinates should be expressed in the \"natural GIS " +"order\" (for example long,lat for geodetic systems)" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:180 +msgid "" +"**ST_GeomFromText(wkt,[srs])**: to build a geometry from its WKT " +"representation." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:183 +msgid "" +"Note that those spatial functions are only supported as server-side " +"filters." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:187 +msgid "Layer joins" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:189 +msgid "" +"For WFS 2.0 servers that support joins, SELECT statements that involve " +"joins will be run on server side. Spatial joins can also be done by using" +" the above mentioned spatial functions, if the server supports spatial " +"joins." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:194 +msgid "" +"There might be restrictions set by server on the complexity of the joins." +" The OGR WFS driver also restricts column selection to be column names, " +"potentially with aliases and type casts, but not expressions. The ON and " +"WHERE clauses must also be evaluated on server side, so no OGR special " +"fields are allowed for example. ORDER BY clauses are supported, but the " +"fields must belong to the primary table." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:201 +msgid "Example of valid statement :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:214 +msgid "Write support / WFS-T" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:216 +msgid "" +"The WFS-T protocol only enables the user to operate at feature level. No " +"datasource, layer or field creations are possible." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:222 +msgid "" +"The mapping between the operations of the WFS Transaction service and the" +" OGR concepts is the following:" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:225 +msgid "OGRFeature::CreateFeature() <==> WFS insert operation" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:226 +msgid "OGRFeature::SetFeature() <==> WFS update operation" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:227 +msgid "OGRFeature::DeleteFeature() <==> WFS delete operation" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:229 +msgid "Lock operations (LockFeature service) are not available at that time." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:231 +msgid "" +"There are a few caveats to keep in mind. OGR feature ID (FID) is an " +"integer based value, whereas WFS/GML gml:id attribute is a string. Thus " +"it is not always possible to match both values. The WFS driver exposes " +"then the gml:id attribute of a feature as a 'gml_id' field." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:236 +msgid "" +"When inserting a new feature with CreateFeature(), and if the command is " +"successful, OGR will fetch the returned gml:id and set the 'gml_id' field" +" of the feature accordingly. It will also try to set the OGR FID if the " +"gml:id is of the form layer_name.numeric_value. Otherwise the FID will be" +" left to its unset default value." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:242 +msgid "" +"When updating an existing feature with SetFeature(), the OGR FID field " +"will be ignored. The request issued to the driver will only take into " +"account the value of the gml:id field of the feature. The same applies " +"for DeleteFeature()." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:248 +msgid "Write support and OGR transactions" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:254 +msgid "" +"It is possible to surround those operations between " +"OGRLayer::StartTransaction() and OGRLayer::CommitTransaction(). The " +"operations will be stored into memory and only executed at the time " +"CommitTransaction() is called." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:259 +msgid "" +"The drawback for CreateFeature() is that the user cannot know which " +"gml:id have been assigned to the inserted features. A special SQL " +"statement has been introduced into the WFS driver to workaround this : by" +" issuing the \"SELECT \\_LAST_INSERTED_FIDS\\_ FROM layer_name\" (where " +"layer_name is to be replaced with the actual layer_name) command through " +"the OGRDataSource::ExecuteSQL(), a layer will be returned with as many " +"rows with a single attribute gml_id as the count of inserted features " +"during the last committed transaction." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:268 +msgid "" +"Note : currently, only CreateFeature() makes use of OGR transaction " +"mechanism. SetFeature() and DeleteFeature() will still be issued " +"immediately." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:273 +msgid "Special SQL commands" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:275 +msgid "" +"The following SQL / pseudo-SQL commands passed to " +"OGRDataSource::ExecuteSQL() are specific of the WFS driver :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:278 +msgid "" +"\"DELETE FROM layer_name WHERE expression\" : this will result into a WFS" +" delete operation. This can be a fast way of deleting one or several " +"features. In particularly, this can be a faster replacement for " +"OGRLayer::DeleteFeature() when the gml:id is known, but the feature has " +"not been fetched from the server." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:284 +msgid "\"SELECT \\_LAST_INSERTED_FIDS\\_ FROM layer_name\" : see above paragraph." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:287 +msgid "" +"Currently, any other SQL command will be processed by the generic layer, " +"meaning client-side only processing. Server side spatial and attribute " +"filtering must be done through the SetSpatialFilter() and " +"SetAttributeFilter() interfaces." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:293 +msgid "Special layer : WFSLayerMetadata" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:295 +msgid "" +"A \"hidden\" layer called \"WFSLayerMetadata\" is filled with records " +"with metadata for each WFS layer." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:298 +msgid "" +"Each record contains a \"layer_name\", \"title\" and \"abstract\" field, " +"from the document returned by GetCapabilities." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:301 +msgid "That layer is returned through GetLayerByName(\"WFSLayerMetadata\")." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:304 +msgid "Special layer : WFSGetCapabilities" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:306 +msgid "" +"A \"hidden\" layer called \"WFSGetCapabilities\" is filled with the raw " +"XML result of the GetCapabilities request." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:309 +msgid "That layer is returned through GetLayerByName(\"WFSGetCapabilities\")." +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:392 +msgid "Listing the types of a WFS server :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:398 +msgid "" +"Listing the types of a WFS server whose layer structures are cached in a " +"XML file :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:405 +msgid "Listing the features of the dvg:nw_dvg2_rbz layer, with a spatial filter :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:411 +msgid "" +"Retrieving the features of GN \"Köln\" and \"Viersen\" from the " +"dvg:nw_dvg2_krs layer :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:418 +msgid "Display layer metadata :" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:427 +msgid "`OGC WFS Standard <http://www.opengeospatial.org/standards/wfs>`__" +msgstr "" + +#: ../../source/drivers/vector/wfs.rst:429 +msgid ":ref:`OGC API - Features driver documentation <vector.oapif>`" +msgstr "" + +#: ../../source/drivers/vector/xls.rst:4 +msgid "XLS - MS Excel format" +msgstr "" + +#: ../../source/drivers/vector/xls.rst:6 +msgid "XLS" +msgstr "" + +#: ../../source/drivers/vector/xls.rst:10 +msgid "" +"This driver reads spreadsheets in MS Excel format. GDAL/OGR must be built" +" against the FreeXL library (GPL/LPL/MPL licensed), and the driver has " +"the same restrictions as the FreeXL library itself as far as which and " +"how Excel files are supported. (At the time of writing - with FreeXL " +"1.0.0a -, it means in particular that formulas are not supported.)" +msgstr "" + +#: ../../source/drivers/vector/xls.rst:47 +msgid "" +"`Homepage of the FreeXL library <https://www.gaia-" +"gis.it/fossil/freexl/index>`__" +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:5 +msgid "XLSX - MS Office Open XML spreadsheet" +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:7 +msgid "XLSX" +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:11 +msgid "" +"This driver can read, write and update spreadsheets in Microsoft Office " +"Open XML (a.k.a. OOXML) spreadsheet format, generated by applications " +"like Microsoft Office 2007 and later versions. LibreOffice/OpenOffice can" +" also export documents in that format since their v3 version." +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:22 +msgid "" +"Note 1 : depending on the application that produced the file, the driver " +"might succeed or not in retrieving the result of formulas. Some " +"applications write the evaluated result of formulas in the document, in " +"which case the driver will be able to retrieve it. Otherwise the raw " +"formula string will be returned." +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:28 +msgid "Note 2 : spreadsheets with passwords are not supported." +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:30 +msgid "" +"Note 3 : when updating an existing document, all existing styles, " +"formatting, formulas and other concepts (charts, drawings, macros, ...) " +"not understood by OGR will be lost : the document is re-written from " +"scratch from the OGR data model." +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:98 +msgid "" +"Transform CSV file input.csv to an Office Open XML file output.xlsx. The " +"spreadsheet will contain one sheet with name \"input\"." +msgstr "" + +#: ../../source/drivers/vector/xlsx.rst:105 +msgid "" +"Add the contents of CSV file input2.csv to the OOXML file output.xlsx " +"created in the first example. The spreadsheet will now contain two " +"sheets, \"input\" and \"input2\"." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:4 +msgid "XODR -- OpenDRIVE Road Description Format" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:8 +msgid "XODR" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:12 +msgid "" +"This driver provides read access to road network elements of OpenDRIVE " +"datasets." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:14 +msgid "" +"`OpenDRIVE <https://www.asam.net/standards/detail/opendrive/>`_ is an " +"open industry format for lane-detailed description of road networks, " +"commonly used in applications of the automotive and transportation " +"systems domains. It bundles polynomial, continuous road geometry " +"modelling with all necessary topological links and semantic information " +"from traffic-regulating infrastructure (signs and traffic lights)." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:24 +msgid "" +"The currently supported OpenDRIVE version is 1.4 and depends on what is " +"provided by libOpenDRIVE_." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:29 +msgid "Supported OpenDRIVE elements" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:31 +msgid "" +"The XODR driver exposes OpenDRIVE's different road elements as separate " +"layers by converting geometric elements into 3-dimensional OGR geometry " +"types. The following _`layer types` are currently implemented:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:33 +msgid "" +"*ReferenceLine*: Road reference line (``<planView>``) as " +":cpp:class:`OGRLineString`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:34 +msgid "*LaneBorder*: Outer road lane border as :cpp:class:`OGRLineString`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:35 +msgid "" +"*Lane*: Polygonal surface (TIN) of the lane mesh as " +":cpp:class:`OGRTriangulatedSurface`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:36 +msgid "" +"*RoadMark*: Polygonal surface (TIN) of the road mark mesh as " +":cpp:class:`OGRTriangulatedSurface`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:37 +msgid "" +"*RoadObject*: Polygonal surface (TIN) of the road object mesh as " +":cpp:class:`OGRTriangulatedSurface`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:38 +msgid "" +"*RoadSignal*: Polygonal surface (TIN) of the road signal mesh as " +":cpp:class:`OGRTriangulatedSurface`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:41 +msgid "Spatial reference" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:43 +msgid "" +"By definition, OpenDRIVE geometries are always referenced in a Cartesian " +"coordinate system which defaults to having its origin at ``(0, 0, 0)``. " +"If real-world coordinates are used, the OpenDRIVE header provides a " +"PROJ.4 string with the definition of a projected spatial reference " +"system:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:51 +msgid "" +"The XODR driver uses this PROJ definition as spatial reference for " +"creation of all OGR geometry layers." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:56 +msgid "" +"The supported content encoding of OpenDRIVE XML files is limited to what " +"pugixml is able to automatically guess (see `4.6. Encodings " +"<https://pugixml.org/docs/manual.html#loading.encoding>`_). The default " +"fallback encoding is UTF-8." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:61 +msgid "" +"The following open options can be specified (typically with the ``-oo " +"name=value`` parameters of :program:`ogrinfo` or :program:`ogr2ogr`):" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:80 +msgid "" +"Translate OpenDRIVE road *ReferenceLine* elements (``<planView>``) to " +":ref:`Shapefile <vector.shapefile>` using :program:`ogr2ogr`. The desired" +" :ref:`layer type <layer types>` which is to be extracted from the " +"dataset is specified as the last parameter of the function call." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:86 +msgid "" +"Convert the whole OpenDRIVE dataset with all its different layers into a " +":ref:`GeoPackage <vector.gpkg>` using:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:92 +msgid "" +"Convert the whole OpenDRIVE dataset with custom parameters :oo:`EPSILON` " +"and :oo:`DISSOLVE_TIN` into a :ref:`GeoPackage <vector.gpkg>`:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:99 +msgid "Convenient usage through docker image" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:101 +msgid "" +"To use the XODR driver through a docker image, first build the image from" +" the corresponding docker directory" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:108 +msgid "" +"For general usage information refer to `GDAL Docker images " +"<https://github.com/OSGeo/gdal/tree/master/docker#usage>`__. Usage " +"examples:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:110 +msgid "" +"Use :program:`ogrinfo` to extract detailed information about a local " +"`xodr` file by mounting your current working directory (`$PWD`) " +"containing the file into the Docker container:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:116 +msgid "" +"Use :program:`ogr2ogr` to convert a local `xodr` file into any other " +"supported OGR output format. The result will be automatically available " +"in your host machine's working directory which is mounted into the " +"container:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:123 +msgid "" +"Alternatively, you can run a docker container that enables using the XODR" +" driver in an isolated workspace from within the container" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:131 +msgid "General building notes" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:133 +msgid "Building of the driver as plugin is tested to work on" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:135 +msgid "Ubuntu 24.04 using GCC" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:136 +msgid "" +"Windows 10 using GCC 13.1.0 (with MCF threads) + MinGW-w64 11.0.0 (MSVCRT" +" runtime), which is obtainable from `WinLibs <https://winlibs.com/>`_." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:138 +msgid "Ensure to meet the following driver dependencies:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:140 +msgid "PROJ" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:141 +msgid "GEOS" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:142 +msgid "" +"libOpenDRIVE_ as shared library (built with CMake option " +"``-DBUILD_SHARED_LIBS=ON``)" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:144 +msgid "" +"Then, after checking out GDAL sources with this driver extension, create " +"the build directory:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:152 +msgid "" +"From the build directory configure CMake to activate our XODR driver as " +"plugin:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:158 +msgid "" +"The :file:`cmake/` path is usually automatically created when installing " +"libOpenDRIVE and contains the necessary configuration files for inclusion" +" into other project builds." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:160 +msgid "Now, build GDAL and install it:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:167 +msgid "" +"Afterwards you will find a new shared library file " +":file:`{path/to/GDAL/installdir}/lib/gdalplugins/ogr_XODR`." +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:170 +msgid "Verifying a successful build" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:172 +msgid "Check if XODR driver is found:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:179 +msgid "This should print basic capabilities of the driver:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:192 +msgid "" +"If you are on Linux, depending on your environment, you might experience " +"linker errors like:" +msgstr "" + +#: ../../source/drivers/vector/xodr.rst:198 +msgid "" +"In such cases ensure that your environment variable ``LD_LIBRARY_PATH`` " +"points to the corresponding install directories of libOpenDRIVE and GDAL " +"and run ``ldconfig`` afterwards." +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/faq.mo b/doc/source/locale/ja/LC_MESSAGES/faq.mo new file mode 100644 index 0000000000000000000000000000000000000000..e2267788ba9b0b286d5bc42a09828116e4c130f8 GIT binary patch literal 415 zcmYk2&rZTX5XLd_)T3t)bMS_PTO^9hpHOJQCM_kUn&@qTrIwW4y4@Oi5MR${ajQn0 zWRm%2f0=J~KF>}+8YWImo}0X=#lN^T^{aWry0=hr$JZMD4L)*JW>Qd?xlRC9%nPYB zhGm*<a9pJ&CX#}+h!UJA&a^?%WtvlHlXeHmEfO2ZHSOFq$sHjE#F)Qj^~hiD$#Y^1 zBXk|Ok7(#OpQE{F1+3JVC??9BX{jhoAA$hpPUu133mrcgIj$Rf%jM9ZBCS|zEO+cr zV8YqH?m#~XMtRnfDjiyjyizR3sZ{%tf+)UaIk0>1Qw~Va3jNSK{@QL4Ya)f_!mM*B zjEUy&`l`rTCVH@bVXEYMQ0Xmpk6gX>mMiqcT5d9tQs}NSZOypg%G|~r?m%J8Ry>Dx J%kCJ9#urd-cUS-b literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/faq.po b/doc/source/locale/ja/LC_MESSAGES/faq.po new file mode 100644 index 000000000000..3138263f7b6d --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/faq.po @@ -0,0 +1,198 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/faq.rst:5 +msgid "FAQ" +msgstr "" + +#: ../../source/faq.rst:12 +msgid "Contents" +msgstr "" + +#: ../../source/faq.rst:16 +msgid "What does GDAL stand for?" +msgstr "" + +#: ../../source/faq.rst:18 +msgid "GDAL - Geospatial Data Abstraction Library" +msgstr "" + +#: ../../source/faq.rst:20 +msgid "" +"It is sometimes pronounced \"goo-doll\" (a bit like goo-gle), while " +"others pronounce it \"gee-doll,\" and others pronounce it \"gee-dall.\"" +msgstr "" + +#: ../../source/faq.rst:22 +msgid "" +"`Listen <https://soundcloud.com/danabauer/how-do-you-pronounce-" +"gdal#t=00:02:58>`__ how Frank Warmerdam prounounces it and the history " +"behind the acronym." +msgstr "" + +#: ../../source/faq.rst:25 +msgid "What is this OGR stuff?" +msgstr "" + +#: ../../source/faq.rst:27 +msgid "" +"OGR used to be a separate vector IO library inspired by OpenGIS Simple " +"Features which was separated from GDAL. With the GDAL 2.0 release, the " +"GDAL and OGR components were integrated together." +msgstr "" + +#: ../../source/faq.rst:30 +msgid "What does OGR stand for?" +msgstr "" + +#: ../../source/faq.rst:32 +msgid "" +"OGR used to stand for OpenGIS Simple Features Reference Implementation. " +"However, since OGR is not fully compliant with the OpenGIS Simple Feature" +" specification and is not approved as a reference implementation of the " +"spec the name was changed to OGR Simple Features Library. The only " +"meaning of OGR in this name is historical. OGR is also the prefix used " +"everywhere in the source of the library for class names, filenames, etc." +msgstr "" + +#: ../../source/faq.rst:35 +msgid "What does CPL stand for?" +msgstr "" + +#: ../../source/faq.rst:37 +msgid "" +"Common Portability Library. Think of it as GDAL internal cross-platform " +"standard library. Back in the early days of GDAL development, when cross-" +"platform development as well as compatibility and standard conformance of" +" compilers was a challenge (or PITA), CPL proved necessary for smooth " +"portability of GDAL/OGR." +msgstr "" + +#: ../../source/faq.rst:39 +msgid "" +"CPL, or parts of it, is used by some projects external to GDAL (eg. " +"MITAB, libgeotiff)." +msgstr "" + +#: ../../source/faq.rst:42 +msgid "When was the GDAL project started?" +msgstr "" + +#: ../../source/faq.rst:44 +msgid "" +"In late 1998, Frank Warmerdam started to work as independent professional" +" on the GDAL/OGR library." +msgstr "" + +#: ../../source/faq.rst:47 +msgid "Is GDAL/OGR proprietary software?" +msgstr "" + +#: ../../source/faq.rst:49 +msgid "No, GDAL/OGR is a Free and Open Source Software." +msgstr "" + +#: ../../source/faq.rst:52 +msgid "What license does GDAL/OGR use?" +msgstr "" + +#: ../../source/faq.rst:54 +msgid "See :ref:`license`" +msgstr "" + +#: ../../source/faq.rst:57 +msgid "What operating systems does GDAL-OGR run on?" +msgstr "" + +#: ../../source/faq.rst:59 +msgid "" +"You can use GDAL/OGR on all modern flavors of Unix: Linux, FreeBSD, Mac " +"OS X; all supported versions of Microsoft Windows; mobile environments " +"(Android and iOS). Both 32-bit and 64-bit architectures are supported." +msgstr "" + +#: ../../source/faq.rst:62 +msgid "Is there a graphical user interface to GDAL/OGR?" +msgstr "" + +#: ../../source/faq.rst:64 +msgid "See :ref:`software_using_gdal`:" +msgstr "" + +#: ../../source/faq.rst:72 +msgid "What compiler can I use to build GDAL/OGR?" +msgstr "" + +#: ../../source/faq.rst:74 +msgid "" +"GDAL/OGR must be compiled with a C++17 capable compiler since GDAL 3.9 " +"(C++11 in previous versions)" +msgstr "" + +#: ../../source/faq.rst:76 +msgid "Build requirements are described in :ref:`build_requirements`." +msgstr "" + +#: ../../source/faq.rst:79 +msgid "" +"I have a question that's not answered here. Where can I get more " +"information?" +msgstr "" + +#: ../../source/faq.rst:81 +msgid "See :ref:`community`" +msgstr "" + +#: ../../source/faq.rst:83 +msgid "" +"Keep in mind, the quality of the answer you get does bear some relation " +"to the quality of the question. If you need more detailed explanation of " +"this, you can find it in essay `How To Ask Questions The Smart Way " +"<http://www.catb.org/~esr/faqs/smart-questions.html>`_ by Eric S. " +"Raymond." +msgstr "" + +#: ../../source/faq.rst:86 +msgid "How do I add support for a new format?" +msgstr "" + +#: ../../source/faq.rst:88 +msgid "" +"To some extent this is now covered by the :ref:`raster_driver_tut` and " +":ref:`vector_driver_tut`" +msgstr "" + +#: ../../source/faq.rst:91 +msgid "Is GDAL thread-safe ?" +msgstr "" + +#: ../../source/faq.rst:93 +msgid "See :ref:`multithreading`" +msgstr "" + +#: ../../source/faq.rst:96 +msgid "How do I cite GDAL ?" +msgstr "" + +#: ../../source/faq.rst:98 +msgid "See `CITATION`_" +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/index.mo b/doc/source/locale/ja/LC_MESSAGES/index.mo new file mode 100644 index 0000000000000000000000000000000000000000..556b490cdd0d16724dff10d4036d0dbd2e8dd286 GIT binary patch literal 2043 zcma)6-)|E~5WZGal`Qq8FMX-1=`%g!0HSaZguzbg%El;hTY*|7YkTb+I^P|)d!bg5 z%H2UppeU%6K<N)C4Wxl42%(BV6ZlX1vbiMmxqm=s_iQJkRI26E?2p-*Z@zDK|9o@H z6%Bu{;rBLvIXT(%vvB<PE1K3q`v!j1S2gV&v@Y6XXs6Jg!2Q3_uH*OV7EOB#*YmGy z+Pi2!L;D5VFVSj)xoi<k1_ZcAY-SPecwm`Tk9cip;MgOKQxAw;hjChyyG`mamvEC< zP$!&7uNL79_!!|blt(Q}7_EbE*VRcV6)M1Z+oDi*sSU%9@6{+69&H$-mRX}VqoYu5 zV+0DLn_UJsQVlp54zoJ;=tvr}5^)FSdth>KJ<6z!C<rjqZepq~@G8T~YCOT(a_ZDl z#dN$nHIbKiaYq5F5zE4eKwKBGDg=rcTn6U5uH$j6wL?N03LJ>V9H==h%HX8Q#}Lvu z@l49w;55KzwBcKFyCpfr&=h=bS|&HqUox&p?W%$GD!8ua)F_jn(@>E#9nOC;JURj{ zX;P?DR`bj%o|g=M=wrz3ne974io2~mI0QS=d(wSfVbWT87>Py7oa3mdHcY!(FsH#! z5|57fGSNu0POMSwsN+M6wBdyBaH>LrX@l!myKFEiojRe?Hyq1yPD;jdX4B-@CFQEj z1BE&YWHwCd8E`6BE}YViBnb3EUH_PR3~M!#1gRk^dDTm-Y1Z|Fev|1H$AHw4az#Jn zQ6++&Bb*wlP(Aa$p6P?k4rAx8t(iTU3_9vVblj97JAOy=*&)4D)^l0-plp;1TaT3w z=Tk-OZoSg$d;<nPDi+~zwv>l``BJt}Jdn-hhVsM1`_a{I`pC8c$4PIZS14)871&oS z9<a=`<2CoEj#$1&EPVhk1~b5R)s*%3?S*96pV^x#6-xPys{7KJ)FH>_$dF!XyO@O2 z&-pgjBBs3;YGcG>l=u6*q3_=Cldv1q)AM%CsUzVA?5>(THArphAvZ`|+kk_liXFc_ z-M14{B-dR8_eC@(!p9<fCZZ(~{3@dFM0meDU09oY@_hQTh|bB~@L9ZkD_)us;Wzk? zXC_ytz83-dUr<42L^Lf2(OnVD%JtKs2ri58Ys{i9ekV_ej`v=?^CDOP5#E()qN^f$ zD8glx^0CAeTou8c|Meb#2rh_lGCup;^XUsBxT3P(5y2S|JVi)p_!rVnbj&aBh$IA& z2bdO5Er{@U5&ft@O(d0WV&IlSdRK%G6w*f`nw7v402i;VES{DTy7aD|UtWLkbB{?8 z;c;a39{R@{&Ku-+{d;a5pz*}q+P65Cw6D(HSdW%bi`A)1D^F1i$y2Xb#XnYkBPk3e zL9x3+CgO!>HdfBxj33>W(k6-qH$)g<0rAZBczF&LU3vNpbBh2Aekh`!WU0|)mrfkt zQ8axe!e3+uL~8Kg$e{ObiRilGZ&3tD#{J~I+O_%v629=_yQLzlCc&1K?lY=dDb;Fp zHoo~l1lVn%2+t>aBL&G5r=*$};i3p<Wq(H#T09l5ot^FU;Y;7Ul|OE;EMga-i09N% zyd(EilTL4rv_5|=p12*)Uy_%iqmC3JKKEp8a$;>#lBXoV?WHR{@#Ni*y^VlTnu`fw I=st-50Axm@6951J literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/index.po b/doc/source/locale/ja/LC_MESSAGES/index.po new file mode 100644 index 000000000000..109cc3e89779 --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/index.po @@ -0,0 +1,82 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/index.rst:12 +msgid "User" +msgstr "" + +#: ../../source/index.rst:3 +msgid "GDAL" +msgstr "" + +#: ../../source/about_no_title.rst:1 +msgid "" +"GDAL is a translator library for raster and vector geospatial data " +"formats that is released under an MIT style Open Source :ref:`license` by" +" the `Open Source Geospatial Foundation`_. As a library, it presents a " +"single raster abstract data model and single vector abstract data model " +"to the calling application for all supported formats. It also comes with " +"a variety of useful command line utilities for data translation and " +"processing. The `NEWS`_ page describes the June 2024 GDAL/OGR 3.9.1 " +"release." +msgstr "" +"GDAL はラスターとベクターの空間データ形式をを変換するライブラリです。これは MIT スタイル :ref:`license` の " +"オープンソースとして `Open Source Geospatial Foundation`_ から公開されています. " +"ライブラリとしてのGDALはすべてのサポートする形式をアプリケーションから単一のラスタ抽象データモデルか単一のベクター抽象モデルとして利用する機能を提供しています。またGDALではデータ変換やデータ加工をするための多彩で便利なコマンドラインユーティリティを提供しています。" +" `NEWS`_ ページには 2024 6月の GDAL/OGR 3.9.1 リリースについての情報があります。" + +#: ../../source/about_no_title.rst:-1 +msgid "OSGeo project" +msgstr "OSGeoプロジェクト" + +#: ../../source/about_no_title.rst:10 +msgid "See :ref:`software_using_gdal`" +msgstr "参照 :ref:`software_using_gdal`" + +#: ../../source/about_no_title.rst:16 +msgid "" +"You may quote GDAL in publications by using the following Digital Object " +"Identifier: |DOI|" +msgstr "" +"以下のデジタルオブジェクト識別子を利用して出版物でGDALを引用することができます " +": |DOI|" + +#: ../../source/about_no_title.rst +msgid "DOI 10.5281/zenodo.5884351" +msgstr "" + +#: ../../source/index.rst:7 +msgid "" +"This documentation is also available as a `PDF file <gdal.pdf>`_, and `a " +".ZIP of individual HTML pages <https://github.com/OSGeo/gdal-" +"docs/archive/refs/heads/master.zip>`_ for offline browsing. (The .ZIP " +"also includes that .PDF.) The documentation reflects the latest state of " +"the development branch of the software." +msgstr "" + +#: ../../source/index.rst:30 +msgid "Index" +msgstr "目次" + +#: ../../source/index.rst:32 +msgid ":ref:`genindex`" +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/index_pdf.mo b/doc/source/locale/ja/LC_MESSAGES/index_pdf.mo new file mode 100644 index 0000000000000000000000000000000000000000..e2267788ba9b0b286d5bc42a09828116e4c130f8 GIT binary patch literal 415 zcmYk2&rZTX5XLd_)T3t)bMS_PTO^9hpHOJQCM_kUn&@qTrIwW4y4@Oi5MR${ajQn0 zWRm%2f0=J~KF>}+8YWImo}0X=#lN^T^{aWry0=hr$JZMD4L)*JW>Qd?xlRC9%nPYB zhGm*<a9pJ&CX#}+h!UJA&a^?%WtvlHlXeHmEfO2ZHSOFq$sHjE#F)Qj^~hiD$#Y^1 zBXk|Ok7(#OpQE{F1+3JVC??9BX{jhoAA$hpPUu133mrcgIj$Rf%jM9ZBCS|zEO+cr zV8YqH?m#~XMtRnfDjiyjyizR3sZ{%tf+)UaIk0>1Qw~Va3jNSK{@QL4Ya)f_!mM*B zjEUy&`l`rTCVH@bVXEYMQ0Xmpk6gX>mMiqcT5d9tQs}NSZOypg%G|~r?m%J8Ry>Dx J%kCJ9#urd-cUS-b literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/index_pdf.po b/doc/source/locale/ja/LC_MESSAGES/index_pdf.po new file mode 100644 index 000000000000..232a8ccffd88 --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/index_pdf.po @@ -0,0 +1,29 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/index_pdf.rst:7 +msgid "User" +msgstr "" + +#: ../../source/index_pdf.rst:5 +msgid "GDAL" +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/license.mo b/doc/source/locale/ja/LC_MESSAGES/license.mo new file mode 100644 index 0000000000000000000000000000000000000000..e2267788ba9b0b286d5bc42a09828116e4c130f8 GIT binary patch literal 415 zcmYk2&rZTX5XLd_)T3t)bMS_PTO^9hpHOJQCM_kUn&@qTrIwW4y4@Oi5MR${ajQn0 zWRm%2f0=J~KF>}+8YWImo}0X=#lN^T^{aWry0=hr$JZMD4L)*JW>Qd?xlRC9%nPYB zhGm*<a9pJ&CX#}+h!UJA&a^?%WtvlHlXeHmEfO2ZHSOFq$sHjE#F)Qj^~hiD$#Y^1 zBXk|Ok7(#OpQE{F1+3JVC??9BX{jhoAA$hpPUu133mrcgIj$Rf%jM9ZBCS|zEO+cr zV8YqH?m#~XMtRnfDjiyjyizR3sZ{%tf+)UaIk0>1Qw~Va3jNSK{@QL4Ya)f_!mM*B zjEUy&`l`rTCVH@bVXEYMQ0Xmpk6gX>mMiqcT5d9tQs}NSZOypg%G|~r?m%J8Ry>Dx J%kCJ9#urd-cUS-b literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/license.po b/doc/source/locale/ja/LC_MESSAGES/license.po new file mode 100644 index 000000000000..53beac4f90c6 --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/license.po @@ -0,0 +1,63 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/license.rst:5 ../../source/license.rst:8 +msgid "License" +msgstr "" + +#: ../../source/license.rst:10 +msgid "" +"In general GDAL/OGR is licensed under an MIT style license with the " +"following terms:" +msgstr "" + +#: ../../source/license.rst:13 +msgid "" +"Permission is hereby granted, free of charge, to any person obtaining a " +"copy of this software and associated documentation files (the " +"\"Software\"), to deal in the Software without restriction, including " +"without limitation the rights to use, copy, modify, merge, publish, " +"distribute, sublicense, and/or sell copies of the Software, and to permit" +" persons to whom the Software is furnished to do so, subject to the " +"following conditions:" +msgstr "" + +#: ../../source/license.rst:20 +msgid "" +"The above copyright notice and this permission notice shall be included " +"in all copies or substantial portions of the Software." +msgstr "" + +#: ../../source/license.rst:23 +msgid "" +"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS" +" OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF " +"MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN" +" NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM," +" DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR " +"OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE" +" USE OR OTHER DEALINGS IN THE SOFTWARE." +msgstr "" + +#: ../../source/license.rst:31 +msgid "The full licensing terms are available in the `LICENSE.TXT`_ file." +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/programs.mo b/doc/source/locale/ja/LC_MESSAGES/programs.mo new file mode 100644 index 0000000000000000000000000000000000000000..e2267788ba9b0b286d5bc42a09828116e4c130f8 GIT binary patch literal 415 zcmYk2&rZTX5XLd_)T3t)bMS_PTO^9hpHOJQCM_kUn&@qTrIwW4y4@Oi5MR${ajQn0 zWRm%2f0=J~KF>}+8YWImo}0X=#lN^T^{aWry0=hr$JZMD4L)*JW>Qd?xlRC9%nPYB zhGm*<a9pJ&CX#}+h!UJA&a^?%WtvlHlXeHmEfO2ZHSOFq$sHjE#F)Qj^~hiD$#Y^1 zBXk|Ok7(#OpQE{F1+3JVC??9BX{jhoAA$hpPUu133mrcgIj$Rf%jM9ZBCS|zEO+cr zV8YqH?m#~XMtRnfDjiyjyizR3sZ{%tf+)UaIk0>1Qw~Va3jNSK{@QL4Ya)f_!mM*B zjEUy&`l`rTCVH@bVXEYMQ0Xmpk6gX>mMiqcT5d9tQs}NSZOypg%G|~r?m%J8Ry>Dx J%kCJ9#urd-cUS-b literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/programs.po b/doc/source/locale/ja/LC_MESSAGES/programs.po new file mode 100644 index 000000000000..6236332b9a65 --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/programs.po @@ -0,0 +1,10322 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/programs/argument_syntax.rst:5 +msgid "Syntax of arguments of command-line utilities" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:7 +msgid "" +"The following table describes the notation used to document the syntax of" +" arguments of command-line utilities." +msgstr "" + +#: ../../source/programs/argument_syntax.rst:13 +msgid "Notation" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:14 +#: ../../source/programs/gdal-config.rst:28 +#: ../../source/programs/gdal2tiles.rst:31 +#: ../../source/programs/gdal2xyz.rst:28 +#: ../../source/programs/gdal_contour.rst:27 +#: ../../source/programs/gdal_create.rst:35 +#: ../../source/programs/gdal_edit.rst:31 +#: ../../source/programs/gdal_fillnodata.rst:26 +#: ../../source/programs/gdal_footprint.rst:36 +#: ../../source/programs/gdal_grid.rst:34 +#: ../../source/programs/gdal_merge.rst:26 +#: ../../source/programs/gdal_pansharpen.rst:31 +#: ../../source/programs/gdal_polygonize.rst:25 +#: ../../source/programs/gdal_proximity.rst:27 +#: ../../source/programs/gdal_rasterize.rst:31 +#: ../../source/programs/gdal_retile.rst:32 +#: ../../source/programs/gdal_sieve.rst:23 +#: ../../source/programs/gdal_translate.rst:43 +#: ../../source/programs/gdal_viewshed.rst:31 +#: ../../source/programs/gdaladdo.rst:27 +#: ../../source/programs/gdalattachpct.rst:22 +#: ../../source/programs/gdalbuildvrt.rst:36 +#: ../../source/programs/gdalcompare.rst:26 +#: ../../source/programs/gdaldem.rst:84 ../../source/programs/gdalinfo.rst:27 +#: ../../source/programs/gdallocationinfo.rst:27 +#: ../../source/programs/gdalmanage.rst:23 +#: ../../source/programs/gdalmdiminfo.rst:26 +#: ../../source/programs/gdalmdimtranslate.rst:34 +#: ../../source/programs/gdalmove.rst:23 +#: ../../source/programs/gdalsrsinfo.rst:22 +#: ../../source/programs/gdaltindex.rst:34 +#: ../../source/programs/gdaltransform.rst:28 +#: ../../source/programs/gdalwarp.rst:51 +#: ../../source/programs/gnmanalyse.rst:27 +#: ../../source/programs/gnmmanage.rst:31 +#: ../../source/programs/nearblack.rst:25 ../../source/programs/ogr2ogr.rst:68 +#: ../../source/programs/ogr_layer_algebra.rst:31 +#: ../../source/programs/ogrinfo.rst:32 ../../source/programs/ogrlineref.rst:30 +#: ../../source/programs/ogrmerge.rst:36 ../../source/programs/ogrtindex.rst:28 +#: ../../source/programs/pct2rgb.rst:22 ../../source/programs/rgb2pct.rst:22 +#: ../../source/programs/sozip.rst:36 +msgid "Description" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:16 +msgid "Text without brackets or braces" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:17 +msgid "Text that must be typed as shown" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:19 +msgid "``<value>``" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:20 +msgid "Placeholder for which a value must be substituted." +msgstr "" + +#: ../../source/programs/argument_syntax.rst:22 +msgid "``[`` Text inside square brackets ``]``" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:23 +msgid "Optional item." +msgstr "" + +#: ../../source/programs/argument_syntax.rst:25 +msgid "``{`` Text inside braces ``}``" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:26 +msgid "Set of required items, separated by a vertical bar." +msgstr "" + +#: ../../source/programs/argument_syntax.rst:28 +msgid "Vertical bar (``|``)" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:29 +msgid "" +"Separator between mutually exclusive items. At least one must be " +"specified." +msgstr "" + +#: ../../source/programs/argument_syntax.rst:31 +msgid "Ellipsis (``...``)" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:32 +msgid "Placed after an item that can be repeated." +msgstr "" + +#: ../../source/programs/argument_syntax.rst:36 +#: ../../source/programs/gdal_contour.rst:138 +#: ../../source/programs/gdal_edit.rst:211 +#: ../../source/programs/gdal_pansharpen.rst:114 +#: ../../source/programs/gdal_viewshed.rst:158 +#: ../../source/programs/gdalinfo.rst:170 +#: ../../source/programs/gdalsrsinfo.rst:72 +#: ../../source/programs/ogrlineref.rst:164 +#: ../../source/programs/ogrtindex.rst:104 ../../source/programs/rgb2pct.rst:66 +msgid "Example" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:38 +msgid "Given the following synopsis:" +msgstr "" + +#: ../../source/programs/argument_syntax.rst:45 +msgid "The following command lines are valid:" +msgstr "" + +#: ../../source/programs/gdal-config.rst:5 +msgid "gdal-config (Unix)" +msgstr "" + +#: ../../source/programs/gdal-config.rst:9 +msgid "Determines various information about a GDAL installation." +msgstr "" + +#: ../../source/programs/gdal-config.rst:14 +#: ../../source/programs/gdal2tiles.rst:14 +#: ../../source/programs/gdal2xyz.rst:14 ../../source/programs/gdal_calc.rst:14 +#: ../../source/programs/gdal_contour.rst:14 +#: ../../source/programs/gdal_create.rst:16 +#: ../../source/programs/gdal_edit.rst:14 +#: ../../source/programs/gdal_fillnodata.rst:14 +#: ../../source/programs/gdal_footprint.rst:16 +#: ../../source/programs/gdal_grid.rst:14 +#: ../../source/programs/gdal_merge.rst:14 +#: ../../source/programs/gdal_pansharpen.rst:16 +#: ../../source/programs/gdal_polygonize.rst:14 +#: ../../source/programs/gdal_proximity.rst:14 +#: ../../source/programs/gdal_rasterize.rst:14 +#: ../../source/programs/gdal_retile.rst:14 +#: ../../source/programs/gdal_sieve.rst:14 +#: ../../source/programs/gdal_translate.rst:14 +#: ../../source/programs/gdal_viewshed.rst:16 +#: ../../source/programs/gdaladdo.rst:14 +#: ../../source/programs/gdalattachpct.rst:14 +#: ../../source/programs/gdalbuildvrt.rst:14 +#: ../../source/programs/gdalcompare.rst:14 +#: ../../source/programs/gdaldem.rst:14 ../../source/programs/gdalinfo.rst:14 +#: ../../source/programs/gdallocationinfo.rst:14 +#: ../../source/programs/gdalmanage.rst:14 +#: ../../source/programs/gdalmdiminfo.rst:16 +#: ../../source/programs/gdalmdimtranslate.rst:16 +#: ../../source/programs/gdalmove.rst:14 +#: ../../source/programs/gdalsrsinfo.rst:14 +#: ../../source/programs/gdaltindex.rst:14 +#: ../../source/programs/gdaltransform.rst:14 +#: ../../source/programs/gdalwarp.rst:14 +#: ../../source/programs/gnmanalyse.rst:14 +#: ../../source/programs/gnmmanage.rst:14 +#: ../../source/programs/nearblack.rst:14 ../../source/programs/ogr2ogr.rst:14 +#: ../../source/programs/ogr_layer_algebra.rst:16 +#: ../../source/programs/ogrinfo.rst:15 ../../source/programs/ogrlineref.rst:14 +#: ../../source/programs/ogrmerge.rst:14 ../../source/programs/ogrtindex.rst:14 +#: ../../source/programs/pct2rgb.rst:14 ../../source/programs/rgb2pct.rst:14 +#: ../../source/programs/sozip.rst:16 +msgid "Synopsis" +msgstr "" + +#: ../../source/programs/gdal-config.rst:30 +msgid "" +"This utility script (available on Unix systems) can be used to determine " +"various information about a GDAL installation. It is normally just used " +"by configure scripts for applications using GDAL but can be queried by an" +" end user." +msgstr "" + +#: ../../source/programs/gdal-config.rst:37 +msgid "the top level directory for the GDAL installation." +msgstr "" + +#: ../../source/programs/gdal-config.rst:41 +msgid "The libraries and link directives required to use GDAL." +msgstr "" + +#: ../../source/programs/gdal-config.rst:45 +msgid "The include and macro definition required to compiled modules using GDAL." +msgstr "" + +#: ../../source/programs/gdal-config.rst:50 +msgid "Reports the GDAL version." +msgstr "" + +#: ../../source/programs/gdal-config.rst:54 +msgid "" +"Reports \"yes\" or \"no\" to standard output depending on whether OGR is " +"built into GDAL." +msgstr "" + +#: ../../source/programs/gdal-config.rst:59 +msgid "Reports which formats are configured into GDAL to stdout." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:5 +msgid "gdal2tiles" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:9 +msgid "Generates directory with TMS tiles, KMLs and simple web viewers." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:33 +msgid "" +"This utility generates a directory with small tiles and metadata, " +"following the OSGeo Tile Map Service Specification. Simple web pages with" +" viewers based on Google Maps, OpenLayers and Leaflet are generated as " +"well - so anybody can comfortably explore your maps on-line and you do " +"not need to install or configure any special software (like MapServer) " +"and the map displays very fast in the web browser. You only need to " +"upload the generated directory onto a web server." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:40 +msgid "" +"GDAL2Tiles also creates the necessary metadata for Google Earth (KML " +"SuperOverlay), in case the supplied map uses EPSG:4326 projection." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:43 +msgid "" +"World files and embedded georeferencing is used during tile generation, " +"but you can publish a picture without proper georeferencing too." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:48 +msgid "" +"Inputs with non-Byte data type (i.e. ``Int16``, ``UInt16``,...) will be " +"clamped to the ``Byte`` data type, causing wrong results. To avoid this " +"it is necessary to rescale input to the ``Byte`` data type using " +"`gdal_translate` utility." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:54 +msgid "" +"Config options of the input drivers may have an effect on the output of " +"gdal2tiles. An example driver config option is GDAL_PDF_DPI, which can be" +" found at :ref:`configoptions`" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:58 +msgid "" +"gdal2tiles is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/options/help.rst:3 +msgid "Show this help message and exit" +msgstr "" + +#: ../../source/programs/options/help_general.rst:3 +msgid "" +"Gives a brief usage message for the generic GDAL commandline options and " +"exit." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:67 +msgid "" +"Tile cutting profile (mercator, geodetic, raster) - default 'mercator' " +"(Google Maps compatible)." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:69 +msgid "" +"Starting with GDAL 3.2, additional profiles are available from " +"tms_XXXX.json files placed in GDAL data directory (provided all zoom " +"levels use same origin, tile dimensions, and resolution between " +"consecutive zoom levels vary by a factor of two)." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:75 +msgid "" +"Resampling method (average, near, bilinear, cubic, cubicspline, lanczos, " +"antialias, mode, max, min, med, q1, q3) - default 'average'." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:79 +msgid "The spatial reference system used for the source input data." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:83 +msgid "" +"Generate XYZ tiles (OSM Slippy Map standard) instead of TMS. In the " +"default mode (TMS), tiles at y=0 are the southern-most tiles, whereas in " +"XYZ mode (used by OGC WMTS too), tiles at y=0 are the northern-most " +"tiles." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:91 +msgid "" +"When using the geodetic profile, specifies the base resolution as " +"0.703125 or 2 tiles at zoom level 0." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:96 +msgid "Zoom levels to render (format:'2-5', '10-' or '10')." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:100 +#: ../../source/programs/gdal_retile.rst:133 +msgid "Resume mode. Generate only missing files." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:104 +msgid "" +"Value in the input dataset considered as transparent. If the input " +"dataset had already an associate nodata value, it is overridden by the " +"specified value." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:109 +msgid "Generate verbose output of tile generation." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:111 +msgid "" +"Starting with GDAL 3.7, that verbose output is emitted through the " +"``logging.getLogger(\"gdal2tiles\")`` object." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:116 +msgid "Exclude transparent tiles from result tileset." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:120 +msgid "Disable messages and status to stdout" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:126 +msgid "" +"Number of parallel processes to use for tiling, to speed-up the " +"computation." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:132 +msgid "" +"Assume launched by mpiexec, enable MPI parallelism and ignore " +"--processes. Requires working MPI environment and the MPI for Python " +"(mpi4py) package. User should set GDAL_CACHEMAX to an appropriate cache " +"size per process based on memory per node and the number of processes " +"launched per node." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:141 +msgid "Width and height in pixel of a tile. Default is 256." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:147 +msgid "" +"Which output driver to use for the tiles, determines the file format of " +"the tiles. Currently PNG, WEBP and JPEG (JPEG added in GDAL 3.9) are " +"supported. Default is PNG. Additional configuration for the WEBP and JPEG" +" drivers are documented below." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:155 +msgid "" +"Comma-separated tuple of values (thus typically \"R,G,B\"), that are " +"ignored as contributing source * pixels during resampling. The number of " +"values in the tuple must be the same as the number of bands, excluding " +"the alpha band. Several tuples of excluded values may be specified using " +"the \"(R1,G1,B2),(R2,G2,B2)\" syntax. Only taken into account by Average " +"currently. This concept is a bit similar to nodata/alpha, but the main " +"difference is that pixels matching one of the excluded value tuples are " +"still considered as valid, when determining the target pixel " +"validity/density." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:168 +msgid "" +"Minimum percentage of source pixels that must be set at one of the " +"--excluded-values to cause the excluded value, that is in majority among " +"source pixels, to be used as the target pixel value. Default value is " +"50(%)" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:175 +msgid "" +"Minimum percentage of source pixels that must be at nodata (or alpha=0 or" +" any other way to express transparent pixel) to cause the target pixel " +"value to be transparent. Default value is 100 (%), which means that a " +"target pixel is transparent only if all contributing source pixels are " +"transparent. Only taken into account for average resampling." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:185 +#: ../../source/programs/gdal2xyz.rst:87 +msgid "Show help message and exit." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:189 +msgid "Show program's version number and exit." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:193 +msgid "KML (Google Earth) options" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:195 +msgid "Options for generated Google Earth SuperOverlay metadata" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:199 +msgid "" +"Generate KML for Google Earth - default for 'geodetic' profile and " +"'raster' in EPSG:4326. For a dataset with different projection use with " +"caution!" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:203 +msgid "Avoid automatic generation of KML files for EPSG:4326." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:207 +msgid "URL address where the generated tiles are going to be published." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:211 +msgid "Web viewer options" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:213 +msgid "Options for generated HTML viewers a la Google Maps" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:217 +msgid "" +"Web viewer to generate (all, google, openlayers, leaflet, mapml, none) - " +"default 'all'." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:221 +msgid "Title of the map." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:225 +msgid "Copyright for the map." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:229 +msgid "Google Maps API key from http://code.google.com/apis/maps/signup.html." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:233 +msgid "Bing Maps API key from https://www.bingmapsportal.com/" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:237 +msgid "MapML options" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:239 +msgid "" +"MapML support is new to GDAL 3.2. When --webviewer=mapml is specified, " +"--xyz is implied, as well as --tmscompatible if --profile=geodetic." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:242 +msgid "The following profiles are supported:" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:244 +msgid "mercator: mapped to OSMTILE MapML tiling scheme" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:245 +msgid "geodetic: mapped to WGS84 MapML tiling scheme" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:246 +msgid "APSTILE: from the tms_MapML_APSTILE.json data file" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:248 +msgid "The generated MapML file in the output directory is ``mapml.mapl``" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:250 +msgid "Available options are:" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:254 +msgid "" +"Filename of a template mapml file where variables will be substituted. If" +" not specified, the generic template_tiles.mapml file from GDAL data " +"resources will be used" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:259 +msgid "" +"The --url option is also used to substitute ``${URL}`` in the template " +"MapML file." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:262 +msgid "WEBP options" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:264 +msgid "" +"WEBP tiledriver support is new to GDAL 3.6. It is enabled by using " +"--tiledriver=WEBP." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:267 +msgid "" +"The following configuration options are available to further customize " +"the WebP output:" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:271 +#: ../../source/programs/gdal2tiles.rst:295 +msgid "QUALITY is a integer between 1-100. Default is 75." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:275 +msgid "Use WEBP lossless compression, default is lossy" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:280 +msgid "GDAL :ref:`WEBP driver <raster.webp>` documentation can be consulted" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:284 +msgid "JPEG options" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:286 +msgid "" +"JPEG tiledriver support is new to GDAL 3.9. It is enabled by using " +"--tiledriver=JPEG." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:288 +msgid "" +"Note that JPEG does not support transparency, hence edge tiles will " +"display black pixels in areas not covered by the source raster." +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:291 +msgid "" +"The following configuration options are available to further customize " +"the JPEG output:" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:299 +#: ../../source/programs/gdal2xyz.rst:100 +#: ../../source/programs/gdal_calc.rst:185 +#: ../../source/programs/gdal_create.rst:103 +#: ../../source/programs/gdal_footprint.rst:220 +#: ../../source/programs/gdal_grid.rst:506 +#: ../../source/programs/gdal_merge.rst:113 +#: ../../source/programs/gdal_rasterize.rst:223 +#: ../../source/programs/gdal_translate.rst:435 +#: ../../source/programs/gdaladdo.rst:281 +#: ../../source/programs/gdalbuildvrt.rst:236 +#: ../../source/programs/gdalcompare.rst:118 +#: ../../source/programs/gdallocationinfo.rst:148 +#: ../../source/programs/gdalmanage.rst:70 +#: ../../source/programs/gdalmdiminfo.rst:83 +#: ../../source/programs/gdalmdimtranslate.rst:173 +#: ../../source/programs/gdaltindex.rst:304 +#: ../../source/programs/gdaltransform.rst:167 +#: ../../source/programs/gdalwarp.rst:700 ../../source/programs/ogr2ogr.rst:688 +#: ../../source/programs/ogrinfo.rst:250 ../../source/programs/ogrmerge.rst:184 +#: ../../source/programs/sozip.rst:150 +msgid "Examples" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:301 +msgid "Basic example:" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:308 +msgid "MapML generation:" +msgstr "" + +#: ../../source/programs/gdal2tiles.rst:315 +msgid "MPI example:" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:5 +msgid "gdal2xyz" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:9 +msgid "Translates a raster file into `xyz` format." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:30 +msgid "" +"The :program:`gdal2xyz` utility can be used to translate a raster file " +"into xyz format. `gdal2xyz` can be used as an alternative to " +"`gdal_translate of=xyz`. Features include:" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:33 +msgid "Select more then one band" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:34 +msgid "Skip or replace nodata value" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:35 +msgid "Return the output as numpy arrays." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:39 +msgid "" +"gdal2xyz is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:47 +msgid "How many rows/cols to skip in each iteration." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:51 +#: ../../source/programs/gdal_translate.rst:189 +msgid "" +"Selects a subwindow from the source image for copying based on pixel/line" +" location." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:55 +msgid "" +"Select band *band* from the input spectral bands for output. Bands are " +"numbered from 1 in the order spectral bands are specified. Multiple " +"**-b** switches may be used. When no -b switch is used, the first band " +"will be used. In order to use all input bands set `-allbands` or `-b 0`." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:63 +msgid "Select all input bands." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:67 +msgid "Use comma instead of space as a delimiter." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:71 +msgid "Exclude the output lines with nodata value (as determined by srcnodata)" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:75 +msgid "" +"The nodata value of the dataset (for skipping or replacing) Default " +"(`None`) - Use the dataset nodata value; `Sequence`/`Number` - Use the " +"given nodata value (per band or per dataset)." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:81 +msgid "" +"Replace source nodata with a given nodata. Has an effect only if not " +"setting `-skipnodata`. Default(`None`) - Use `srcnodata`, no replacement;" +" `Sequence`/`Number` - Replace the `srcnodata` with the given nodata " +"value (per band or per dataset)." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:91 +#: ../../source/programs/gdal_translate.rst:410 +msgid "" +"The source dataset name. It can be either file name, URL of data source " +"or subdataset name for multi-dataset files." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:96 +#: ../../source/programs/gdal_create.rst:100 +#: ../../source/programs/gdal_translate.rst:415 +#: ../../source/programs/gdalmdimtranslate.rst:165 +#: ../../source/programs/gdalwarp.rst:490 +msgid "The destination file name." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:107 +msgid "" +"To create a text file in `xyz` format from the input file `input.tif`. " +"The first columns, x and y, are the coordinates of the centers of each " +"cell. The remaining columns represent the first and second bands. We also" +" replace the dataset nodata values with zeros." +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:114 +msgid "Caveats" +msgstr "" + +#: ../../source/programs/gdal2xyz.rst:116 +msgid "" +"gdal2xyz output values with a limited precision. Use ``gdal_translate -of" +" XYZ`` if more precision is desired." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:5 +msgid "gdal_calc" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:9 +msgid "Command line raster calculator with numpy syntax." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:-1 +msgid "DESCRIPTION" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:25 +msgid "" +"Command line raster calculator with numpy syntax. Use any basic " +"arithmetic supported by numpy arrays such as ``+``, ``-``, ``*``, and " +"``/`` along with logical operators such as ``>``. Note that all files " +"must have the same dimensions (unless extent option is used), but no " +"projection checking is performed (unless projectionCheck option is used)." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:33 +msgid "" +"gdal_calc is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:39 +msgid "" +"Calculation in numpy syntax using ``+``, ``-``, ``/``, ``*``, or any " +"numpy array functions (i.e. ``log10()``). Multiple ``--calc`` options can" +" be listed to produce a multiband file (GDAL >= 3.2)." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:44 +msgid "" +"Input gdal raster file, you can use any letter (a-z, A-Z). (lower case " +"supported since GDAL 3.3)" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:46 +msgid "" +"A letter may be repeated, or several values (separated by space) can be " +"provided (GDAL >= 3.3). Since GDAL 3.5, wildcard exceptions (using ?, " +"\\*) are supported for all shells/platforms. The effect will be to create" +" a 3-dim numpy array. In such a case, the calculation formula must use " +"this input as a 3-dim array and must return a 2D array (see examples " +"below). In case the calculation does not return a 2D array an error would" +" be generated." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:54 +msgid "Number of raster band for file A (default 1)." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:58 +msgid "Output file to generate or fill." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:62 +msgid "" +"Output NoDataValue (default datatype specific value). To indicate not " +"setting a NoDataValue use --NoDataValue=none (GDAL >= 3.3)" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:66 +msgid "" +"Using the Python API: ``None`` value will indicate default datatype " +"specific value. ``'none'`` value will indicate not setting a NoDataValue." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:74 +msgid "" +"Ignores the input bands NoDataValue. By default, the input bands " +"NoDataValue are not participating in the calculation. By setting this " +"setting - no special treatment will be performed on the input " +"NoDataValue. and they will be participating in the calculation as any " +"other value. The output will not have a set NoDataValue, unless you " +"explicitly specified a specific value by setting --NoDataValue=<value>." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:81 +msgid "" +"Output datatype, must be one of [``Byte``, ``Int8``, ``UInt16``, " +"``Int16``, ``UInt32``, ``Int32``, ``UInt64``, ``Int64``, ``Float64``, " +"``Float32``, ``CInt16``, ``CInt32``, ``CFloat64``, ``CFloat32``]." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:85 +msgid "" +"Despite the datatype set using ``--type``, when doing intermediate " +"aritmethic operations using operands of the same type, the operation " +"result will honor the original datatype. This may lead into unexpected " +"results in the final result." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:90 +msgid "" +"UInt64, Int64, CInt16, CInt32, CFloat32, CFloat64 have been added in GDAL" +" 3.5.3 Int8 has been added in GDAL 3.7" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:95 +msgid "GDAL format for output file." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:99 +msgid "" +"Allows specifying a filename of a color table (or a ColorTable object) " +"(with Palette Index interpretation) to be used for the output raster. " +"Supported formats: txt (i.e. like gdaldem, but color names are not " +"supported), qlr, qml (i.e. exported from QGIS)" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:106 +msgid "" +"This option determines how to handle rasters with different extents. This" +" option is mutually exclusive with the `projwin` option, which is used " +"for providing a custom extent." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:109 +msgid "" +"For all the options below the pixel size (resolution) and SRS (Spatial " +"Reference System) of all the input rasters must be the same." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:111 +msgid "" +"``ignore`` (default) - only the dimensions of the rasters are compared. " +"if the dimensions do not agree the operation will fail." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:113 +msgid "" +"``fail`` - the dimensions and the extent (bounds) of the rasters must " +"agree, otherwise the operation will fail." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:115 +msgid "" +"``union`` - the extent (bounds) of the output will be the minimal " +"rectangle that contains all the input extents." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:117 +msgid "" +"``intersect`` - the extent (bounds) of the output will be the maximal " +"rectangle that is contained in all the input extents." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:123 +msgid "" +"This option provides a custom extent for the output, it is mutually " +"exclusive with the `extent` option." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:129 +msgid "" +"By default, no projection checking will be performed. By setting this " +"option, if the projection is not the same for all bands then the " +"operation will fail." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:136 +msgid "" +"Passes a creation option to the output format driver. Multiple options " +"may be listed. See format specific documentation for legal creation " +"options for each format." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:142 +msgid "The same as creation-option_." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:146 +msgid "" +"Process all bands of given raster (a-z, A-Z). Requires a single calc for " +"all bands." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:150 +msgid "" +"Overwrite output file if it already exists. Overwriting must be " +"understood here as deleting and recreating the file from scratch. Note " +"that if this option is *not* specified and the output file already " +"exists, it will be updated in place." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:157 +msgid "Print debugging information." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:161 +#: ../../source/programs/gdal_merge.rst:76 +msgid "Suppress progress messages." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:165 +msgid "Python options" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:169 +msgid "" +"The following options are available by using function the python " +"interface of gdal_calc. They are not available using the command prompt." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:174 +msgid "" +"A dictionary of custom functions or other names to be available for use " +"in the Calc expression." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:178 +msgid "" +"If enabled, the output dataset would be returned from the function and " +"not closed." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:182 +msgid "" +"Allows specifying a ColorTable object (with Palette Index interpretation)" +" to be used for the output raster." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:187 +msgid "Add two files together:" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:193 +msgid "Average of two layers:" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:201 +msgid "" +"In the previous example, beware that if A and B inputs are of the same " +"datatype, for example integers, you may need to force the conversion of " +"one of the operands before the division operation." +msgstr "" + +#: ../../source/programs/gdal_calc.rst:208 +msgid "Add three files together (two options with the same result):" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:218 +msgid "Average of three layers (two options with the same result):" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:228 +msgid "Maximum of three layers (two options with the same result):" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:238 +msgid "Set values of zero and below to null:" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:244 +msgid "Using logical operator to keep a range of values from input:" +msgstr "" + +#: ../../source/programs/gdal_calc.rst:250 +msgid "Work with multiple bands:" +msgstr "" + +#: ../../source/programs/gdal_contour.rst:5 +msgid "gdal_contour" +msgstr "" + +#: ../../source/programs/gdal_contour.rst:9 +msgid "Builds vector contour lines from a raster elevation model." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:29 +msgid "" +"The :program:`gdal_contour` generates a vector contour file from the " +"input raster elevation model (DEM)." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:32 +msgid "" +"The contour line-strings are oriented consistently and the high side will" +" be on the right, i.e. a line string goes clockwise around a top." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:41 +msgid "Picks a particular band to get the DEM from. Defaults to band 1." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:45 +msgid "" +"Provides a name for the attribute in which to put the elevation. If not " +"provided no elevation attribute is attached. Ignored in polygonal " +"contouring (:option:`-p`) mode." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:51 +msgid "" +"Provides a name for the attribute in which to put the minimum elevation " +"of contour polygon. If not provided no minimum elevation attribute is " +"attached. Ignored in default line contouring mode." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:59 +msgid "" +"Provides a name for the attribute in which to put the maximum elevation " +"of contour polygon. If not provided no maximum elevation attribute is " +"attached. Ignored in default line contouring mode." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:67 +msgid "" +"Force production of 3D vectors instead of 2D. Includes elevation at every" +" vertex." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:72 +msgid "" +"Ignore any nodata value implied in the dataset - treat all values as " +"valid." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:76 +msgid "Input pixel value to treat as \"nodata\"." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:80 +msgid "Create output in a particular format." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:84 +msgid "" +"If not specified, the format is guessed from the extension (previously " +"was ESRI Shapefile)." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:88 +#: ../../source/programs/gdal_footprint.rst:183 +#: ../../source/programs/gnmanalyse.rst:65 +#: ../../source/programs/ogr2ogr.rst:194 +#: ../../source/programs/ogrlineref.rst:68 +#: ../../source/programs/ogrmerge.rst:133 +msgid "Dataset creation option (format specific)" +msgstr "" + +#: ../../source/programs/gdal_contour.rst:92 +#: ../../source/programs/gdal_footprint.rst:179 +#: ../../source/programs/gdal_polygonize.rst:87 +#: ../../source/programs/gdaltindex.rst:137 +#: ../../source/programs/gnmanalyse.rst:69 +#: ../../source/programs/ogr2ogr.rst:198 ../../source/programs/ogrmerge.rst:137 +msgid "Layer creation option (format specific)" +msgstr "" + +#: ../../source/programs/gdal_contour.rst:96 +msgid "" +"Elevation interval between contours. Ignored if -fl is used. Must specify" +" either -i or -fl or -e." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:101 +msgid "" +"Offset from zero relative to which to interpret intervals. Ignored if -fl" +" is used." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:103 +msgid "" +"For example, `-i 100` requests contours at ...-100, 0, 100... Further " +"adding `-off 25` makes that request instead ...-75, 25, 125..." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:108 +msgid "" +"Name one or more \"fixed levels\" to extract. Must specify either -i or " +"-fl or -e." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:113 +msgid "" +"Generate levels on an exponential scale: `base ^ k`, for `k` an integer. " +"Must specify either -i or -fl or -e." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:120 +msgid "Provide a name for the output vector layer. Defaults to \"contour\"." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:124 +msgid "Generate contour polygons rather than contour lines." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:130 +msgid "Be quiet: do not print progress indicators." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:133 +#: ../../source/programs/gdal_footprint.rst:214 +#: ../../source/programs/gdal_grid.rst:501 +#: ../../source/programs/gdal_rasterize.rst:216 +#: ../../source/programs/gdal_translate.rst:428 +#: ../../source/programs/gdal_viewshed.rst:153 +#: ../../source/programs/gdaladdo.rst:276 +#: ../../source/programs/gdalbuildvrt.rst:264 +#: ../../source/programs/gdaldem.rst:395 ../../source/programs/gdalinfo.rst:163 +#: ../../source/programs/gdalmdiminfo.rst:78 +#: ../../source/programs/gdalmdimtranslate.rst:168 +#: ../../source/programs/gdaltindex.rst:336 +#: ../../source/programs/gdalwarp.rst:752 +#: ../../source/programs/nearblack.rst:125 +#: ../../source/programs/ogr2ogr.rst:681 ../../source/programs/ogrinfo.rst:243 +#: ../../source/programs/sozip.rst:144 +msgid "C API" +msgstr "" + +#: ../../source/programs/gdal_contour.rst:135 +msgid "" +"Functionality of this utility can be done from C with " +":cpp:func:`GDALContourGenerate`." +msgstr "" + +#: ../../source/programs/gdal_contour.rst:140 +msgid "" +"This would create 10-meter contours from the DEM data in :file:`dem.tif` " +"and produce a shapefile in :file:`contour.shp|shx|dbf` with the contour " +"elevations in the ``elev`` attribute." +msgstr "" + +#: ../../source/programs/gdal_create.rst:5 +msgid "gdal_create" +msgstr "" + +#: ../../source/programs/gdal_create.rst:11 +msgid "Create a raster file (without source dataset)." +msgstr "" + +#: ../../source/programs/gdal_create.rst:37 +msgid "" +"The :program:`gdal_create` utility can be used to initialize a new raster" +" file, from its dimensions, band count and set various parameters, such " +"as CRS, geotransform, nodata value, metadata. It can be used also in " +"special cases, like creating a PDF file from a XML composition file." +msgstr "" + +#: ../../source/programs/options/ot.rst:3 +msgid "" +"Force the output image bands to have a specific data type supported by " +"the driver, which may be one of the following: ``Byte``, ``Int8``, " +"``UInt16``, ``Int16``, ``UInt32``, ``Int32``, ``UInt64``, ``Int64``, " +"``Float32``, ``Float64``, ``CInt16``, ``CInt32``, ``CFloat32`` or " +"``CFloat64``." +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:36 +#: ../../source/programs/options/of.rst:3 ../../source/programs/pct2rgb.rst:37 +msgid "" +"Select the output format. Starting with GDAL 2.3, if not specified, the " +"format is guessed from the extension (previously was GTiff). Use the " +"short format name." +msgstr "" + +#: ../../source/programs/gdal_create.rst:52 +msgid "" +"Set the size of the output file in pixels. First figure is width. Second " +"one is height." +msgstr "" + +#: ../../source/programs/gdal_create.rst:57 +msgid "Number of bands. Defaults to 1 if -outsize is specified, or 0 otherwise." +msgstr "" + +#: ../../source/programs/gdal_create.rst:61 +msgid "" +"A fixed value to burn into a band. A list of :option:`-burn` options can " +"be supplied, one per band (the first value will apply to the first band, " +"the second one to the second band, etc.). If a single value is specified," +" it will apply to all bands." +msgstr "" + +#: ../../source/programs/gdal_create.rst:68 +msgid "" +"Override the projection for the output file. The<srs_def> may be any of " +"the usual GDAL/OGR forms, complete WKT, PROJ.4, EPSG:n or a file " +"containing the WKT. No reprojection is done." +msgstr "" + +#: ../../source/programs/gdal_create.rst:74 +msgid "Assign the georeferenced bounds of the output file." +msgstr "" + +#: ../../source/programs/gdal_create.rst:78 +#: ../../source/programs/gdal_edit.rst:134 +#: ../../source/programs/gdal_merge.rst:98 +#: ../../source/programs/gdal_rasterize.rst:123 +msgid "Assign a specified nodata value to output bands." +msgstr "" + +#: ../../source/programs/gdal_create.rst:82 +#: ../../source/programs/gdal_translate.rst:308 +msgid "Passes a metadata key and value to set on the output dataset if possible." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:320 +#: ../../source/programs/options/co.rst:5 +msgid "" +"Many formats have one or more optional creation options that can be used " +"to control particulars about the file created. For instance, the GeoTIFF " +"driver supports creation options to control compression, and whether the " +"file should be tiled." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:325 +#: ../../source/programs/gdalmdimtranslate.rst:61 +#: ../../source/programs/options/co.rst:10 +msgid "" +"The creation options available vary by format driver, and some simple " +"formats have no creation options at all. A list of options supported for " +"a format can be listed with the :ref:`--formats " +"<raster_common_options_formats>` command line option but the " +"documentation for the format is the definitive source of information on " +"driver creation options. See :ref:`raster_drivers` format specific " +"documentation for legal creation options for each format." +msgstr "" + +#: ../../source/programs/gdal_create.rst:88 +#: ../../source/programs/gdal_footprint.rst:142 +#: ../../source/programs/gdal_grid.rst:165 +#: ../../source/programs/gdal_pansharpen.rst:94 +#: ../../source/programs/gdal_rasterize.rst:196 +#: ../../source/programs/gdal_translate.rst:383 +#: ../../source/programs/gdaldem.rst:161 +#: ../../source/programs/nearblack.rst:111 +msgid "Suppress progress monitor and other non-error output." +msgstr "" + +#: ../../source/programs/gdal_create.rst:94 +msgid "" +"Name of GDAL input dataset that serves as a template for default values " +"of options -outsize, -bands, -ot, -a_srs, -a_ullr and -a_nodata. Note " +"that the pixel values will *not* be copied." +msgstr "" + +#: ../../source/programs/gdal_create.rst:105 +msgid "Initialize a new GeoTIFF file with a uniform value of 10" +msgstr "" + +#: ../../source/programs/gdal_create.rst:112 +msgid "Create a PDF file from a XML composition file:" +msgstr "" + +#: ../../source/programs/gdal_create.rst:120 +msgid "Initialize a blank GeoTIFF file from an input one:" +msgstr "" + +#: ../../source/programs/gdal_edit.rst:5 +msgid "gdal_edit" +msgstr "" + +#: ../../source/programs/gdal_edit.rst:9 +msgid "Edit in place various information of an existing GDAL dataset." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:33 +msgid "" +":program:`gdal_edit` can be used to edit in place various information of " +"an existing GDAL dataset (projection, geotransform, nodata, metadata)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:37 +msgid "" +"It works only with raster formats that support update access to existing " +"datasets." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:41 +msgid "" +"Depending on the format, older values of the updated information might " +"still be found in the file in a \"ghost\" state, even if no longer " +"accessible through the GDAL API. This is for example the case of the " +":ref:`raster.gtiff` format (this is not a exhaustive list)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:48 +msgid "" +"gdal_edit is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:54 +msgid "" +"Open the dataset in read-only. Might be useful for drivers refusing to " +"use the dataset in update-mode. In which case, updated information will " +"go into PAM :file:`.aux.xml` files." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:60 +msgid "" +"Defines the target coordinate system. This coordinate system will be " +"written to the dataset. If the empty string or None is specified, then " +"the existing coordinate system will be removed (for TIFF/GeoTIFF, might " +"not be well supported besides that)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:68 +msgid "" +"Assign/override the coordinate epoch of the dataset, as a decimal year " +"(e.g., 2021.3)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:74 +msgid "Remove the coordinate epoch of the dataset." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:80 +msgid "Assign/override the georeferenced bounds of the dataset." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:84 +msgid "" +"Assign/override the georeferenced bounds of the dataset from three " +"points: upper-left, upper-right and lower-left. Unlike :option:`-a_ullr`," +" this also supports rotated datasets (edges not parallel to coordinate " +"system axes)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:92 +#: ../../source/programs/gdal_rasterize.rst:159 +msgid "" +"Set target resolution. The values must be expressed in georeferenced " +"units. Both must be positive values." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:97 +msgid "Remove the georeference information." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:101 +msgid "Remove RPC information." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:107 +msgid "Remove band statistics information." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:113 +msgid "Calculate and store band statistics." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:119 +msgid "" +"Store user-defined values for band statistics (minimum, maximum, mean and" +" standard deviation). If any of the values is set to None, the real " +"statistics are calclulated from the file and the ones set to None are " +"used from the real statistics." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:128 +msgid "Calculate and store approximate band statistics." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:138 +msgid "Remove existing nodata values." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:144 +msgid "" +"Assign a specified scale value to output bands. If a single scale value " +"is provided it will be set for all bands. Alternatively one scale value " +"per band can be provided, in which case the number of scale values must " +"match the number of bands. If no scale is needed, it it recommended to " +"set the value to 1. Scale and Offset are generally used together. For " +"example, scale and offset might be used to store elevations in a unsigned" +" 16bit integer file with a precision of 0.1, and starting from -100. True" +" values would be calculated as: true_value = (pixel_value * scale) + " +"offset" +msgstr "" + +#: ../../source/programs/gdal_edit.rst:154 +msgid "" +"These values can be applied using -unscale during a " +":program:`gdal_translate` run." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:160 +msgid "" +"Assign a specified offset value to output bands. If a single offset value" +" is provided it will be set for all bands. Alternatively one offset value" +" per band can be provided, in which case the number of offset values must" +" match the number of bands. If no offset is needed, it recommended to set" +" the value to 0. For more see scale." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:171 +msgid "Assign a unit to output band(s)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:177 +msgid "" +"Change the color interpretation of band X (where X is a valid band " +"number, starting at 1)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:184 +msgid "" +"Add the indicated ground control point to the dataset. This option may be" +" provided multiple times to provide a set of GCPs." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:189 +msgid "" +"Remove existing metadata (in the default metadata domain). Can be " +"combined with :option:`-mo`." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:196 +msgid "" +"Passes a metadata key and value to set on the output dataset if possible." +" This metadata is added to the existing metadata items, unless " +":option:`-unsetmd` is also specified." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:202 +msgid "Open option (format specific)." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:206 +msgid "" +"The :option:`-a_ullr`, :option:`-a_ulurll`, :option:`-tr` and " +":option:`-unsetgt` options are exclusive." +msgstr "" + +#: ../../source/programs/gdal_edit.rst:208 +msgid "" +"The :option:`-unsetstats` and either :option:`-stats` or " +":option:`-approx_stats` options are exclusive." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:5 +msgid "gdal_fillnodata" +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:9 +msgid "Fill raster regions by interpolation from edges." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:28 +msgid "" +":program:`gdal_fillnodata` fills selection regions (usually nodata areas)" +" by interpolating from valid pixels around the edges of the area." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:31 +msgid "" +"Additional details on the algorithm are available in the " +":cpp:func:`GDALFillNodata` docs." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:36 +msgid "" +"gdal_fillnodata is a Python utility, and is only available if GDAL Python" +" bindings are available." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:42 +msgid "" +"The script runs in quiet mode. The progress monitor is suppressed and " +"routine messages are not displayed." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:47 +msgid "" +"The maximum distance (in pixels) that the algorithm will search out for " +"values to interpolate. The default is 100 pixels." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:52 +msgid "" +"The number of 3x3 average filter smoothing iterations to run after the " +"interpolation to dampen artifacts. The default is zero smoothing " +"iterations." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:57 +msgid "Specify a special argument to the algorithm. Currently none are supported." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:61 +msgid "The band to operate on, by default the first band is operated on." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:65 +msgid "" +"Use the first band of the specified file as a validity mask (zero is " +"invalid, non-zero is valid)." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:70 +msgid "" +"Select the output format. The default is :ref:`raster.gtiff`. Use the " +"short format name." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:77 +msgid "" +"By default, pixels are interpolated using an inverse distance weighting " +"(``inv_dist``). It is also possible to choose a nearest neighbour " +"(``nearest``) strategy." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:83 +msgid "" +"The source raster file used to identify target pixels. Only one band is " +"used." +msgstr "" + +#: ../../source/programs/gdal_fillnodata.rst:88 +msgid "The new file to create with the interpolated result." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:5 +msgid "gdal_footprint" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:11 +msgid "Compute footprint of a raster." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:38 +msgid "" +"The :program:`gdal_footprint` utility can be used to compute the " +"footprint of a raster file, taking into account nodata values (or more " +"generally the mask band attached to the raster bands), and generating " +"polygons/multipolygons corresponding to areas where pixels are valid, and" +" write to an output vector file." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:43 +msgid "" +"The :program:`nearblack` utility may be run as a pre-processing step to " +"generate proper mask bands." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:53 +msgid "" +"Band(s) of interest. Between 1 and the number of bands of the raster. May" +" be specified multiple times. If not specified, all bands are taken into " +"account. The way multiple bands are combined is controlled by " +":option:`-combine_bands`" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:60 +msgid "" +"Defines how the mask bands of the selected bands are combined to generate" +" a single mask band, before being vectorized. The default value is " +"``union``: that is a pixel is valid if it is valid at least for one of " +"the selected bands. ``intersection`` means that a pixel is valid only " +"ifit is valid for all selected bands." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:69 +msgid "" +"To specify which overview level of source file must be used, when " +"overviews are available on the source raster. By default the full " +"resolution level is used. The index is 0-based, that is 0 means the first" +" overview level. This option is mutually exclusive with " +":option:`-srcnodata`." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:76 +msgid "" +"Set nodata values for input bands (different values can be supplied for " +"each band). If a single value is specified, it applies to all selected " +"bands. If more than one value is supplied, there should be as many values" +" as the number of selected bands, and all values should be quoted to keep" +" them together as a single operating system argument. If the option is " +"not specified, the intrinsic mask band of each selected bands will be " +"used." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:86 +msgid "" +"Target coordinate system. By default if the input dataset is " +"georeferenced, ``georef`` is implied, that is the footprint geometry will" +" be expressed as coordinates in the CRS of the raster (or the one " +"specified with :option:`-t_srs`). If specifying ``pixel``, the " +"coordinates of the footprint geometry are column and line indices." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:94 +msgid "" +"Target CRS of the output file. The <srs_def> may be any of the usual " +"GDAL/OGR forms, complete WKT, PROJ.4, EPSG:n or a file containing the " +"WKT. Specifying this option implies -t_cs georef The footprint is " +"reprojected from the CRS of the source raster to the specified CRS." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:103 +msgid "" +"When specified, multipolygons are split as several features each with one" +" single polygon." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:108 +msgid "When specified, the convex hull of (multi)polygons is computed." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:112 +msgid "" +"The specified value of this option is the maximum distance between 2 " +"consecutive points of the output geometry. The unit of the distance is in" +" pixels if :option:`-t_cs` equals ``pixel``, or otherwise in " +"georeferenced units of the source raster. This option is applied before " +"the reprojection implied by :option:`-t_srs`." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:120 +msgid "" +"The specified value of this option is the tolerance used to merge " +"consecutive points of the output geometry using the " +":cpp:func:`OGRGeometry::Simplify` method. The unit of the distance is in " +"pixels if :option:`-t_cs` equals ``pixel``, or otherwise in georeferenced" +" units of the target vector dataset. This option is applied after the " +"reprojection implied by :option:`-t_srs`." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:129 +msgid "" +"Minimum value for the area of a ring The unit of the area is in square " +"pixels if :option:`-t_cs` equals ``pixel``, or otherwise in georeferenced" +" units of the target vector dataset. This option is applied after the " +"reprojection implied by :option:`-t_srs`" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:136 +msgid "" +"Maximum number of points of each output geometry (not counting the " +"closing point of each ring, which is always identical to the first " +"point). The default value is 100. ``unlimited`` can be used to remove " +"that limitation." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:146 +#: ../../source/programs/gdal_translate.rst:406 +#: ../../source/programs/gdaladdo.rst:87 +#: ../../source/programs/gdalbuildvrt.rst:207 +#: ../../source/programs/gdallocationinfo.rst:77 +#: ../../source/programs/gdalwarp.rst:476 +msgid "Dataset open option (format specific)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:150 +msgid "" +"Select the output format. Use the short format name. Guessed from the " +"file extension if not specified" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:157 +msgid "" +"Specifies the name of the field in the resulting vector dataset where the" +" path of the input dataset will be stored. The default field name is " +"\"location\". To prevent writing the path of the input dataset, use " +":option:`-no_location`" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:166 +msgid "" +"Turns off the writing of the path of the input dataset as a field in the " +"output vector dataset." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:173 +msgid "" +"Enables writing the absolute path of the input dataset. By default, the " +"filename is written in the location field exactly as specified on the " +"command line." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:187 +msgid "Name of the target layer. ``footprint`` if not specified." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:191 +msgid "Overwrite the target layer if it exists." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:195 +msgid "The source raster file name." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:199 +msgid "" +"The destination vector file name. If the file and the output layer exist," +" the new footprint is appended to them, unless :option:`-overwrite` is " +"used." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:203 +msgid "" +"Post-vectorization geometric operations are applied in the following " +"order:" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:205 +msgid "optional splitting (:option:`-split_polys`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:206 +msgid "optional densification (:option:`-densify`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:207 +msgid "optional reprojection (:option:`-t_srs`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:208 +msgid "optional filtering by minimum ring area (:option:`-min_ring_area`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:209 +msgid "optional application of convex hull (:option:`-convex_hull`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:210 +msgid "optional simplification (:option:`-simplify`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:211 +msgid "limitation of number of points (:option:`-max_points`)" +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:216 +msgid "This utility is also callable from C with :cpp:func:`GDALFootprint`." +msgstr "" + +#: ../../source/programs/gdal_footprint.rst:222 +msgid "" +"Compute the footprint of a GeoTIFF file as a GeoJSON file using WGS 84 " +"longitude, latitude coordinates" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:5 +msgid "gdal_grid" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:9 +msgid "Creates regular grid from the scattered data." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:36 +msgid "" +"This program creates a regular grid (raster) from the scattered data read" +" from the OGR datasource. Input data will be interpolated to fill grid " +"nodes with values, you can choose from various interpolation methods." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:40 +msgid "" +"It is possible to set the :config:`GDAL_NUM_THREADS` configuration option" +" to parallelize the processing. The value to specify is the number of " +"worker threads, or ``ALL_CPUS`` to use all the cores/CPUs of the " +"computer." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:51 +msgid "" +"If not set then a default type is used, which might not be supported by " +"the relevant driver, causing a error." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:58 +msgid "Set georeferenced X extents of output file to be created." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:62 +msgid "Set georeferenced Y extents of output file to be created." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:66 +msgid "" +"Set output file resolution (in target georeferenced units). Note that " +":option:`-tr` just works in combination with a valid input from " +":option:`-txe` and :option:`-tye`" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:73 +msgid "" +"Set the size of the output file in pixels and lines. Note that " +":option:`-outsize` cannot be used with :option:`-tr`" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:78 +msgid "" +"Override the projection for the output file. The *srs_def* may be any of" +" the usual GDAL/OGR forms, complete WKT, PROJ.4, EPSG:n or a file " +"containing the WKT. No reprojection is done." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:85 +msgid "" +"Identifies an attribute field on the features to be used to get a Z value" +" from. This value overrides the Z value read from the feature geometry " +"record (naturally, if you have a Z value in the geometry, otherwise you " +"have no choice and should specify a field name containing a Z value)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:93 +msgid "" +"Addition to the attribute field on the features to be used to get a Z " +"value from. The addition should be the same unit as the Z value. The " +"result value will be Z value + Z increase value. The default value is 0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:99 +msgid "" +"This is multiplication ratio for the Z field. This can be used for a " +"shift from e.g. feet to meters or from elevation to depth. The result " +"value will be (Z value + Z increase value) * Z multiply value. The " +"default value is 1." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:106 +msgid "" +"Set the interpolation algorithm or data metric name and (optionally) its " +"parameters. See the `Interpolation algorithms`_ and `Data metrics`_ " +"sections for further discussion of available options." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:112 +msgid "" +"Adds a spatial filter to select only features contained within the " +"bounding box described by (xmin, ymin) - (xmax, ymax)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:118 +msgid "" +"Adds a spatial filter to select only features contained within the " +"specified bounding box (expressed in source SRS), WKT geometry (POLYGON " +"or MULTIPOLYGON), from a datasource or to the spatial extent of the " +":option:`-spat` option if you use the ``spat_extent`` keyword. When " +"specifying a datasource, you will generally want to use it in combination" +" with the :option:`-clipsrclayer`, :option:`-clipsrcwhere` or " +":option:`-clipsrcsql` options." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:128 +msgid "Select desired geometries using an SQL query instead." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:132 +#: ../../source/programs/ogr2ogr.rst:413 +msgid "Select the named layer from the source clip datasource." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:136 +msgid "Restrict desired geometries based on an attribute query." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:140 +#: ../../source/programs/gdal_rasterize.rst:95 +msgid "" +"Indicates the layer(s) from the datasource that will be used for input " +"features. May be specified multiple times, but at least one layer name " +"or a :option:`-sql` option must be specified." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:147 +msgid "" +"An optional SQL WHERE style query expression to be applied to select " +"features to process from the input layer(s)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:152 +msgid "" +"An SQL statement to be evaluated against the datasource to produce a " +"virtual layer of features to be processed." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:159 +#: ../../source/programs/gdal_rasterize.rst:192 +#: ../../source/programs/gdalmdimtranslate.rst:157 +msgid "Source dataset open option (format specific)" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:169 +#: ../../source/programs/gdal_rasterize.rst:200 +msgid "Any OGR supported readable datasource." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:173 +msgid "The GDAL supported output file." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:177 +msgid "Interpolation algorithms" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:179 +msgid "There are a number of interpolation algorithms to choose from." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:181 +msgid "More details about them can also be found in :ref:`gdal_grid_tut`" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:186 +msgid "invdist" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:188 +msgid "" +"Inverse distance to a power. This is the default algorithm. It has the " +"following parameters:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:191 +#: ../../source/programs/gdal_grid.rst:228 +msgid "``power``: Weighting power (default 2.0)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:192 +#: ../../source/programs/gdal_grid.rst:229 +msgid "``smoothing``: Smoothing parameter (default 0.0)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:193 +msgid "" +"``radius1``: The first radius (X axis if rotation angle is 0) of the " +"search ellipse. Set this parameter to zero to use the whole point array. " +"Default is 0.0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:196 +msgid "" +"``radius2``: The second radius (Y axis if rotation angle is 0) of the " +"search ellipse. Set this parameter to zero to use the whole point array. " +"Default is 0.0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:199 +#: ../../source/programs/gdal_grid.rst:273 +#: ../../source/programs/gdal_grid.rst:323 +#: ../../source/programs/gdal_grid.rst:386 +msgid "" +"``radius``: Set first and second radius (mutually exclusive with radius1 " +"and radius2). Default is 0.0. Added in GDAL 3.6" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:201 +#: ../../source/programs/gdal_grid.rst:275 +#: ../../source/programs/gdal_grid.rst:325 +#: ../../source/programs/gdal_grid.rst:388 +msgid "" +"``angle``: Angle of search ellipse rotation in degrees (counter " +"clockwise, default 0.0)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:203 +msgid "" +"``max_points``: Maximum number of data points to use. Do not search for " +"more points than this number. This is only used if the search ellipse is " +"set (both radii are non-zero). Zero means that all found points should be" +" used. Default is 0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:207 +#: ../../source/programs/gdal_grid.rst:390 +msgid "" +"``min_points``: Minimum number of data points to use. If less amount of " +"points found the grid node considered empty and will be filled with " +"NODATA marker. This is only used if search ellipse is set (both radii are" +" non-zero). Default is 0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:211 +msgid "" +"``max_points_per_quadrant``: Maximum number of data points to use per " +"quadrant. Default is 0. Added in GDAL 3.6. When specified, this actually " +"uses invdistnn implementation." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:214 +msgid "" +"``min_points_per_quadrant``: Minimum number of data points to use per " +"quadrant. Default is 0. Added in GDAL 3.6. When specified, this actually " +"uses invdistnn implementation." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:217 +#: ../../source/programs/gdal_grid.rst:250 +#: ../../source/programs/gdal_grid.rst:297 +#: ../../source/programs/gdal_grid.rst:327 +#: ../../source/programs/gdal_grid.rst:350 +#: ../../source/programs/gdal_grid.rst:406 +msgid "``nodata``: NODATA marker to fill empty points (default 0.0)." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:221 +msgid "invdistnn" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:225 +msgid "" +"Inverse distance to a power with nearest neighbor searching, ideal when " +"max_points is used. It has following parameters:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:230 +msgid "" +"``radius``: The radius of the search circle, which should be non-zero. " +"Default is 1.0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:232 +msgid "" +"``max_points``: Maximum number of data points to use. Do not search for " +"more points than this number. Found points will be ranked from nearest to" +" furthest distance when weighting. Default is 12." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:235 +msgid "" +"``min_points``: Minimum number of data points to use. If less amount of " +"points found the grid node is considered empty and will be filled with " +"NODATA marker. Default is 0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:238 +#: ../../source/programs/gdal_grid.rst:285 +#: ../../source/programs/gdal_grid.rst:394 +msgid "" +"``max_points_per_quadrant``: Maximum number of data points to use per " +"quadrant. Default is 0. Added in GDAL 3.6. When specified, the algorithm " +"will only take into account up to max_points_per_quadrant points for each" +" of the right-top, left-top, right-bottom and right-top quadrant relative" +" to the point being interpolated." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:243 +#: ../../source/programs/gdal_grid.rst:290 +#: ../../source/programs/gdal_grid.rst:399 +msgid "" +"``min_points_per_quadrant``: Minimum number of data points to use per " +"quadrant. Default is 0. Added in GDAL 3.6. If that number is not reached," +" the point being interpolated will be set with the NODATA marker. When " +"specified, the algorithm will collect at least min_points_per_quadrant " +"points for each of the right-top, left-top, right-bottom and right-top " +"quadrant relative to the point being interpolated." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:253 +#: ../../source/programs/gdal_grid.rst:303 +#: ../../source/programs/gdal_grid.rst:409 +msgid "" +"When ``min_points_per_quadrant`` or ``max_points_per_quadrant`` is " +"specified, the search will start with the closest point to the point " +"being interpolated from the first quadrant, then the closest point to the" +" point being interpolated from the second quadrant, etc. up to the 4th " +"quadrant, and will continue with the next closest point in the first " +"quadrant, etc. until ``max_points`` and/or ``max_points_per_quadrant`` " +"thresholds are reached." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:263 +msgid "average" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:265 +msgid "Moving average algorithm. It has following parameters:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:267 +#: ../../source/programs/gdal_grid.rst:317 +#: ../../source/programs/gdal_grid.rst:380 +msgid "" +"``radius1``: The first radius (X axis if rotation angle is 0) of search " +"ellipse. Set this parameter to zero to use whole point array. Default is " +"0.0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:270 +#: ../../source/programs/gdal_grid.rst:320 +#: ../../source/programs/gdal_grid.rst:383 +msgid "" +"``radius2``: The second radius (Y axis if rotation angle is 0) of search " +"ellipse. Set this parameter to zero to use whole point array. Default is " +"0.0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:277 +msgid "" +"``max_points``: Maximum number of data points to use. Do not search for " +"more points than this number. Found points will be ranked from nearest to" +" furthest distance when weighting. Default is 0. Added in GDAL 3.6 Only " +"taken into account if one or both of ``min_points_per_quadrant`` or " +"``max_points_per_quadrant`` is specified" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:282 +msgid "" +"``min_points``: Minimum number of data points to use. If less amount of " +"points found the grid node considered empty and will be filled with " +"NODATA marker. Default is 0." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:300 +msgid "" +"Note, that it is essential to set search ellipse for moving average " +"method. It is a window that will be averaged when computing grid nodes " +"values." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:313 +msgid "nearest" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:315 +msgid "Nearest neighbor algorithm. It has following parameters:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:331 +msgid "linear" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:335 +msgid "Linear interpolation algorithm." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:337 +msgid "" +"The Linear method performs linear interpolation by computing a Delaunay " +"triangulation of the point cloud, finding in which triangle of the " +"triangulation the point is, and by doing linear interpolation from its " +"barycentric coordinates within the triangle. If the point is not in any " +"triangle, depending on the radius, the algorithm will use the value of " +"the nearest point or the nodata value." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:344 +msgid "It has following parameters:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:346 +msgid "" +"``radius``: In case the point to be interpolated does not fit into a " +"triangle of the Delaunay triangulation, use that maximum distance to " +"search a nearest neighbour, or use nodata otherwise. If set to -1, the " +"search distance is infinite. If set to 0, nodata value will be always " +"used. Default is -1." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:354 +msgid "Data metrics" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:356 +msgid "" +"Besides the interpolation functionality :program:`gdal_grid` can be used " +"to compute some data metrics using the specified window and output grid " +"geometry. These metrics are:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:360 +msgid "``minimum``: Minimum value found in grid node search ellipse." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:362 +msgid "``maximum``: Maximum value found in grid node search ellipse." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:364 +msgid "" +"``range``: A difference between the minimum and maximum values found in " +"grid node search ellipse." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:367 +msgid "``count``: A number of data points found in grid node search ellipse." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:369 +msgid "" +"``average_distance``: An average distance between the grid node (center " +"of the search ellipse) and all of the data points found in grid node " +"search ellipse." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:373 +msgid "" +"``average_distance_pts``: An average distance between the data points " +"found in grid node search ellipse. The distance between each pair of " +"points within ellipse is calculated and average of all distances is set " +"as a grid node value." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:378 +msgid "All the metrics have the same set of options:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:417 +msgid "Reading comma separated values" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:419 +msgid "" +"Often you have a text file with a list of comma separated XYZ values to " +"work with (so called CSV file). You can easily use that kind of data " +"source in :program:`gdal_grid`. All you need is to create a virtual " +"dataset header (VRT) for your CSV file and use it as an input datasource " +"for :program:`gdal_grid`. You can find details on the VRT format on the " +":ref:`vector.vrt` description page." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:425 +msgid "" +"Here is a small example. Let's say we have a CSV file called *dem.csv* " +"containing" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:437 +msgid "" +"For the above data we will create a *dem.vrt* header with the following " +"content:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:450 +msgid "" +"This description specifies so called 2.5D geometry with three " +"coordinates X, Y and Z. The Z value will be used for interpolation. Now " +"you can use *dem.vrt* with all OGR programs (start with :ref:`ogrinfo`" +" to test that everything works fine). The datasource will contain a " +"single layer called *\"dem\"* filled with point features constructed " +"from values in the CSV file. Using this technique you can handle CSV " +"files with more than three columns, switch columns, etc. OK, now the " +"final step:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:462 +msgid "Or, if we do not wish to use a VRT file:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:469 +msgid "" +"If your CSV file does not contain column headers then it can be handled " +"in the VRT file in the following way:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:476 +msgid "" +"The :ref:`vector.csv` description page contains details on CSV format " +"supported by GDAL/OGR." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:480 +msgid "Creating multiband files" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:482 +msgid "" +"Creating multiband files is not directly possible with gdal_grid. One " +"might use gdal_grid multiple times to create one band per file, and then " +"use :ref:`gdalbuildvrt` -separate and then :ref:`gdal_translate`:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:492 +msgid "" +"Or just use :ref:`gdal_merge`, to combine the one-band files into a " +"single one:" +msgstr "" + +#: ../../source/programs/gdal_grid.rst:503 +msgid "This utility is also callable from C with :cpp:func:`GDALGrid`." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:508 +msgid "" +"The following would create raster TIFF file from VRT datasource described" +" in `Reading comma separated values`_ section using the inverse distance " +"to a power method. Values to interpolate will be read from Z value of " +"geometry record." +msgstr "" + +#: ../../source/programs/gdal_grid.rst:517 +msgid "" +"The next command does the same thing as the previous one, but reads " +"values to interpolate from the attribute field specified with **-zfield**" +" option instead of geometry record. So in this case X and Y coordinates " +"are being taken from geometry and Z is being taken from the " +"*\"Elevation\"* field. The :config:`GDAL_NUM_THREADS` is also set to " +"parallelize the computation." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:5 +msgid "gdal_merge" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:9 +msgid "Mosaics a set of images." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:28 +msgid "" +"This utility will automatically mosaic a set of images. All the images " +"must be in the same coordinate system and have a matching number of " +"bands, but they may be overlapping, and at different resolutions. In " +"areas of overlap, the last image will be copied over earlier ones. " +"Nodata/transparency values are considered on a band by band level, i.e. a" +" nodata/transparent pixel on one source band will not set a " +"nodata/transparent value on all bands for the target pixel in the " +"resulting raster nor will it overwrite a valid pixel value." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:38 +msgid "" +"gdal_merge is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:46 +msgid "" +"The name of the output file, which will be created if it does not already" +" exist (defaults to \"out.tif\")." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:57 +msgid "" +"Pixel size to be used for the output file. If not specified the " +"resolution of the first input file will be used." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:63 +msgid "" +"(target aligned pixels) align the coordinates of the extent of the output" +" file to the values of the -tr, such that the aligned extent includes the" +" minimum extent. Alignment means that xmin / resx, ymin / resy, xmax / " +"resx and ymax / resy are integer values." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:70 +msgid "" +"The extents of the output file. If not specified the aggregate extents of" +" all input files will be used." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:80 +msgid "Generate verbose output of mosaicing operations as they are done." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:84 +msgid "Place each input file into a separate band." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:88 +msgid "" +"Grab a pseudo-color table from the first input image, and use it for the " +"output. Merging pseudo-colored images this way assumes that all input " +"files use the same color table." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:94 +msgid "Ignore pixels from files being merged in with this pixel value." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:102 +#: ../../source/programs/gdal_rasterize.rst:127 +msgid "" +"Pre-initialize the output image bands with these values. However, it is " +"not marked as the nodata value in the output file. If only one value is " +"given, the same value is used in all the bands." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:108 +msgid "" +"The output file is created (and potentially pre-initialized) but no input" +" image data is copied into it." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:116 +msgid "Creating an image with the pixels in all bands initialized to 255" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:124 +msgid "Creating an RGB image that shows blue in pixels with no data" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:126 +msgid "" +"The first two bands will be initialized to 0 and the third band will be " +"initialized to 255." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:135 +msgid "Passing a large list of files to :program:`gdal_merge`" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:137 +msgid "" +"A large list of files can be passed to :program:`gdal_merge` by listing " +"them in a text file using:" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:144 +msgid "on Linux, or" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:150 +msgid "" +"on Windows. The text file can then be passed to :program:`gdal_merge` " +"using `--optfile`:" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:158 +msgid "Creating an RGB image by merging 3 different greyscale bands" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:160 +msgid "" +"Conduct \"merging by stacking\" with the :option:`-separate` flag. Given " +"three greyscale files that cover the same area, you can run:" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:167 +msgid "" +"This maps :file:`1.tif` to red, :file:`2.tif` to green and :file:`3.tif` " +"to blue." +msgstr "" + +#: ../../source/programs/gdal_merge.rst:170 +msgid "Specifying overlap precedence" +msgstr "" + +#: ../../source/programs/gdal_merge.rst:172 +msgid "" +"The last image in the input line comes out on top of the finished image " +"stack. You might also need to use :option:`-n` to note which value should" +" not be copied into the destination image if it is not already defined as" +" nodata." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:5 +msgid "gdal_pansharpen" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:9 +msgid "Perform a pansharpen operation." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:11 +msgid "(Since GDAL 2.1)" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:33 +msgid "" +":program:`gdal_pansharpen` performs a pan-sharpening operation. It can " +"create a \"classic\" output dataset (such as GeoTIFF), or a VRT dataset " +"describing the pan-sharpening operation." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:37 +msgid "More details can be found in the :ref:`gdal_vrttut_pansharpen` section." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:41 +msgid "" +"gdal_pansharpen is a Python utility, and is only available if GDAL Python" +" bindings are available." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:47 +msgid "" +"Select the output format. Starting with GDAL 2.3, if not specified, the " +"format is guessed from the extension (previously was ``GTiff``). Use the " +"short format name. ``VRT`` can also be used." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:53 +msgid "" +"Select band *band* from the input spectral bands for output. Bands are " +"numbered from 1 in the order spectral bands are specified. Multiple " +"**-b** switches may be used. When no -b switch is used, all input " +"spectral bands are set for output." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:60 +msgid "" +"Specify a weight for the computation of the pseudo panchromatic value. " +"There must be as many -w switches as input spectral bands." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:65 +msgid "Select a resampling algorithm. ``cubic`` is the default." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:69 +msgid "" +"Specify number of threads to use to do the resampling and pan-sharpening " +"itself. Can be an integer number or ``ALL_CPUS``." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:74 +msgid "" +"Specify the bit depth of the panchromatic and spectral bands (e.g. 12). " +"If not specified, the NBITS metadata item from the panchromatic band will" +" be used if it exists." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:80 +msgid "" +"Specify nodata value for bands. Used for the resampling and pan-" +"sharpening computation itself. If not set, deduced from the input bands, " +"provided they have a consistent setting." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:86 +msgid "" +"Select behavior when bands have not the same extent. See " +"*SpatialExtentAdjustment* documentation in :ref:`gdal_vrttut_pansharpen` " +"``union`` is the default." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:98 +msgid "Dataset with panchromatic band (first band will be used)." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:102 +msgid "" +"Dataset with one or several spectral bands. If the band option is not " +"specified, all bands of the datasets are taken into account. Otherwise, " +"only the specified (num)th band. The same dataset can be repeated several" +" times." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:109 +msgid "Output dataset" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:111 +msgid "Bands should be in the same projection." +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:116 +msgid "With spectral bands in a single dataset :" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:122 +msgid "With a few spectral bands from a single dataset, reordered :" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:128 +msgid "With spectral bands in several datasets :" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:134 +msgid "Specify weights:" +msgstr "" + +#: ../../source/programs/gdal_pansharpen.rst:140 +msgid "" +"Specify RGB bands from a RGBNir multispectral dataset while computing the" +" pseudo panchromatic intensity on the 4 RGBNir bands:" +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:5 +msgid "gdal_polygonize" +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:9 +msgid "Produces a polygon feature layer from a raster." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:26 +msgid "" +"This utility creates vector polygons for all connected regions of pixels " +"in the raster sharing a common pixel value. Each polygon is created with" +" an attribute indicating the pixel value of that polygon. A raster mask " +"may also be provided to determine which pixels are eligible for " +"processing." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:31 +msgid "" +"The utility will create the output vector datasource if it does not " +"already exist, otherwise it will try to append to an existing one." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:34 +msgid "" +"The utility is based on the ::cpp:func:`GDALPolygonize` function which " +"has additional details on the algorithm." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:39 +msgid "" +"gdal_polygonize is a Python utility, and is only available if GDAL Python" +" bindings are available." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:47 +msgid "Use 8 connectedness. Default is 4 connectedness." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:51 +msgid "" +"Do not use the default validity mask for the input band (such as nodata, " +"or alpha masks)." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:56 +msgid "" +"Use the first band of the specified file as a validity mask (zero is " +"invalid, non-zero is valid). If not specified, the default validity mask " +"for the input band (such as nodata, or alpha masks) will be used (unless " +"-nomask is specified)" +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:62 +msgid "The source raster file from which polygons are derived." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:66 +msgid "" +"The band on <raster_file> to build the polygons from. Starting with GDAL " +"2.2, the value can also be set to \"mask\", to indicate that the mask " +"band of the first band must be used (or \"mask,band_number\" for the mask" +" of a specified band)" +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:73 +msgid "" +"Select the output format. Starting with GDAL 2.3, if not specified, the " +"format is guessed from the extension (previously was GML). Use the short " +"format name" +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:81 +msgid "Polygonize option. See ::cpp:func:`GDALPolygonize` documentation." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:93 +msgid "Overwrite the output layer if it already exists." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:97 +msgid "The destination vector file to which the polygons will be written." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:101 +msgid "The name of the layer created to hold the polygon features." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:105 +msgid "The name of the field to create (defaults to \"DN\")." +msgstr "" + +#: ../../source/programs/gdal_polygonize.rst:109 +msgid "" +"The script runs in quiet mode. The progress monitor is suppressed and " +"routine messages are not displayed." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:5 +msgid "gdal_proximity" +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:9 +msgid "Produces a raster proximity map." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:29 +msgid "" +":program:`gdal_proximity` generates a raster proximity map indicating the" +" distance from the center of each pixel to the center of the nearest " +"pixel identified as a target pixel. Target pixels are those in the " +"source raster for which the raster pixel value is in the set of target " +"pixel values." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:36 +msgid "" +"gdal_proximity is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:44 +msgid "The source raster file used to identify target pixels." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:48 +msgid "" +"The destination raster file to which the proximity map will be written. " +"It may be a pre-existing file of the same size as srcfile. If it does not" +" exist it will be created." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:54 +msgid "Identifies the band in the source file to use (default is 1)." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:58 +msgid "Identifies the band in the destination file to use (default is 1)." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:66 +msgid "" +"Specify a data type supported by the driver, which may be one of the " +"following: ``Byte``, ``UInt16``, ``Int16``, ``UInt32``, ``Int32``, " +"``Float32`` (default), or ``Float64``." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:72 +msgid "" +"A list of target pixel values in the source image to be considered target" +" pixels. If not specified, all non-zero pixels will be considered target " +"pixels." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:77 +msgid "" +"Indicate whether distances generated should be in pixel or georeferenced " +"coordinates (default PIXEL)." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:82 +msgid "" +"The maximum distance to be generated. The nodata value will be used for " +"pixels beyond this distance. If a nodata value is not provided, the " +"output band will be queried for its nodata value. If the output band does" +" not have a nodata value, then the value 65535 will be used. Distance is " +"interpreted in pixels unless -distunits GEO is specified." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:90 +msgid "Specify a nodata value to use for the destination proximity raster." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:94 +msgid "" +"Indicate whether nodata pixels in the input raster should be nodata in " +"the output raster (default NO)." +msgstr "" + +#: ../../source/programs/gdal_proximity.rst:98 +msgid "" +"Specify a value to be applied to all pixels that are within the -maxdist " +"of target pixels (including the target pixels) instead of a distance " +"value." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:5 +msgid "gdal_rasterize" +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:9 +msgid "Burns vector geometries into a raster" +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:33 +msgid "" +"This program burns vector geometries (points, lines, and polygons) into " +"the raster band(s) of a raster image. Vectors are read from OGR " +"supported vector formats. If the output raster already exists, the " +"affected pixels are updated in-place." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:38 +msgid "" +"Note that on the fly reprojection of vector data to the coordinate system" +" of the raster data is only supported since GDAL 2.1.0." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:47 +msgid "" +"The band(s) to burn values into. Multiple -b arguments may be used to " +"burn into a list of bands. The default is to burn into band 1. Not used" +" when creating a new raster." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:53 +msgid "" +"Invert rasterization. Burn the fixed burn value, or the burn value " +"associated with the first feature into all parts of the image *not* " +"inside the provided polygon." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:59 +msgid "" +"When the vector features contain a polygon nested within another polygon " +"(like an island in a lake), GDAL must be built against GEOS to get " +"correct results." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:65 +msgid "" +"Enables the ALL_TOUCHED rasterization option so that all pixels touched " +"by lines or polygons will be updated, not just those on the line render " +"path, or whose center point is within the polygon (behavior is " +"unspecified when the polygon is just touching the pixel center). Defaults" +" to disabled for normal rendering rules." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:73 +msgid "" +"A fixed value to burn into a band for all objects. A list of " +":option:`-burn` options can be supplied, one per band being written to." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:78 +msgid "" +"Identifies an attribute field on the features to be used for a burn-in " +"value. The value will be burned into all output bands." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:83 +msgid "" +"Indicates that a burn value should be extracted from the \"Z\" values of " +"the feature. Works with points and lines (linear interpolation along each" +" segment). For polygons, works properly only if the are flat (same Z " +"value for all vertices)." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:90 +msgid "" +"Instead of burning a new value, this adds the new value to the existing " +"raster. Suitable for heatmaps for instance." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:101 +msgid "" +"An optional SQL WHERE style query expression to be applied to select " +"features to burn in from the input layer(s)." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:106 +msgid "" +"An SQL statement to be evaluated against the datasource to produce a " +"virtual layer of features to be burned in. Starting with GDAL 3.7, the " +"``@filename`` syntax can be used to indicate that the content is in the " +"pointed filename." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:113 +msgid "" +"SQL dialect. In some cases can be used to use (unoptimized) OGR SQL " +"instead of the native SQL of an RDBMS by passing OGRSQL. The \"SQLITE\" " +"dialect can also be used with any datasource." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:133 +msgid "" +"Override the projection for the output file. If not specified, the " +"projection of the input vector file will be used if available. When using" +" this option, no reprojection of features from the SRS of the input " +"vector to the specified SRS of the output raster, so use only this option" +" to correct an invalid source SRS. The <srs_def> may be any of the usual " +"GDAL/OGR forms, complete WKT, PROJ.4, EPSG:n or a file containing the " +"WKT." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:142 +msgid "" +"set a transformer option suitable to pass to " +":cpp:func:`GDALCreateGenImgProjTransformer2`. This is used when " +"converting geometries coordinates to target raster pixel space. For " +"example this can be used to specify RPC related transformer options." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:153 +msgid "" +"Set georeferenced extents. The values must be expressed in georeferenced " +"units. If not specified, the extent of the output file will be the extent" +" of the vector layers." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:164 +msgid "" +"(target aligned pixels) Align the coordinates of the extent of the output" +" file to the values of the :option:`-tr`, such that the aligned extent " +"includes the minimum extent. Alignment means that xmin / resx, ymin / " +"resy, xmax / resx and ymax / resy are integer values." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:171 +msgid "" +"Set output file size in pixels and lines. Note that :option:`-ts` cannot " +"be used with :option:`-tr`" +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:176 +msgid "" +"Force the output bands to be of the indicated data type. Defaults to " +"``Float64``" +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:180 +msgid "" +"Force the algorithm used (results are identical). The raster mode is used" +" in most cases and optimise read/write operations. The vector mode is " +"useful with a decent amount of input features and optimise the CPU use. " +"That mode have to be used with tiled images to be efficient. The auto " +"mode (the default) will chose the algorithm based on input and output " +"properties." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:204 +msgid "" +"The GDAL supported output file. Must support update mode access. This " +"file will be created if it does not already exist If the output raster " +"already exists, the affected pixels are updated in-place." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:208 +msgid "" +"The program creates a new target raster image when any of the " +":option:`-of`, :option:`-a_nodata`, :option:`-init`, :option:`-a_srs`, " +":option:`-co`, :option:`-te`, :option:`-tr`, :option:`-tap`, " +":option:`-ts`, or :option:`-ot` options are used. The resolution or size " +"must be specified using the :option:`-tr` or :option:`-ts` option for all" +" new rasters. The target raster will be overwritten if it already exists" +" and any of these creation-related options are used." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:218 +msgid "This utility is also callable from C with :cpp:func:`GDALRasterize`." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:225 +msgid "" +"The following would burn all polygons from mask.shp into the RGB TIFF " +"file work.tif with the color red (RGB = 255,0,0)." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:233 +msgid "" +"The following would burn all \"class A\" buildings into the output " +"elevation file, pulling the top elevation from the ROOF_H attribute." +msgstr "" + +#: ../../source/programs/gdal_rasterize.rst:240 +msgid "" +"The following would burn all polygons from footprint.shp into a new " +"1000x1000 rgb TIFF as the color red. Note that :option:`-b` is not used;" +" the order of the :option:`-burn` options determines the bands of the " +"output raster." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:5 +msgid "gdal_retile" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:9 +msgid "Retiles a set of tiles and/or build tiled pyramid levels." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:34 +msgid "" +"This utility will retile a set of input tile(s). All the input tile(s) " +"must be georeferenced in the same coordinate system and have a matching " +"number of bands." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:37 +msgid "" +"Optionally pyramid levels are generated. All pyramid levels are generated" +" from the input tiles (not from previous levels)." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:40 +msgid "It is possible to generate shape file(s) for the tiled output." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:42 +msgid "" +"If your number of input tiles exhausts the command line buffer, use the " +"general :ref:`--optfile <raster_common_options_optfile>` option" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:47 +#: ../../source/programs/gdal_sieve.rst:39 +msgid "" +"gdal_retile is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:55 +msgid "" +"The directory where the tile result is created. Pyramids are stored in " +"sub-directories numbered from 1. Created tile names have a numbering " +"schema and contain the name of the source tiles(s)" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:67 +msgid "" +"Pixel size to be used for the output file. If not specified, 256 x 256 " +"is the default" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:72 +msgid "" +"Overlap in pixels between consecutive tiles. If not specified, 0 is the " +"default" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:78 +msgid "Number of pyramids levels to build." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:82 +msgid "Generate verbose output of tile operations as they are done." +msgstr "" + +#: ../../source/programs/gdal_retile.rst:86 +msgid "No retiling, build only the pyramids" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:90 +msgid "Resampling algorithm, default is near" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:94 +msgid "" +"Source spatial reference to use. The coordinate systems that can be " +"passed are anything supported by the " +"OGRSpatialReference.SetFromUserInput() call, which includes EPSG, PCS," +" and GCSes (i.e. EPSG:4296), PROJ.4 declarations (as above), or the name " +"of a .prj file containing well known text. If no srs_def is given, " +"the srs_def of the source tiles is used (if there is any). The srs_def " +"will be propagated to created tiles (if possible) and to the optional " +"shape file(s)" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:104 +msgid "The name of shape file containing the result tile(s) index" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:108 +msgid "The name of the attribute containing the tile name" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:112 +msgid "" +"The name of the csv file containing the tile(s) georeferencing " +"information. The file contains 5 columns: tilename,minx,maxx,miny,maxy" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:117 +msgid "" +"The column delimiter used in the CSV file, default value is a semicolon " +"\";\"" +msgstr "" + +#: ../../source/programs/gdal_retile.rst:121 +msgid "" +"Normally the tiles of the base image are stored as described in " +":option:`-targetDir`. For large images, some file systems have " +"performance problems if the number of files in a directory is too big, " +"causing gdal_retile not to finish in reasonable time. Using this " +"parameter creates a different output structure. The tiles of the base " +"image are stored in a sub-directory called 0, the pyramids in sub-" +"directories numbered 1,2,.... Within each of these directories another " +"level of sub-directories is created, numbered from 0...n, depending of " +"how many tile rows are needed for each level. Finally, a directory " +"contains only the tiles for one row for a specific level. For large " +"images a performance improvement of a factor N could be achieved." +msgstr "" + +#: ../../source/programs/gdal_sieve.rst:5 +msgid "gdal_sieve" +msgstr "" + +#: ../../source/programs/gdal_sieve.rst:9 +msgid "Removes small raster polygons." +msgstr "" + +#: ../../source/programs/gdal_sieve.rst:25 +msgid "" +":program:`gdal_sieve` removes raster polygons smaller than a provided " +"threshold size (in pixels) and replaces them with the pixel value of the " +"largest neighbour polygon. The result can be written back to the existing" +" raster band, or copied into a new file." +msgstr "" + +#: ../../source/programs/gdal_sieve.rst:30 +msgid "" +"The input dataset is read as integer data which means that floating point" +" values are rounded to integers. Re-scaling source data may be necessary " +"in some cases (e.g. 32-bit floating point data with min=0 and max=1)." +msgstr "" + +#: ../../source/programs/gdal_sieve.rst:34 +msgid "" +"Additional details on the algorithm are available in the " +":cpp:func:`GDALSieveFilter` docs." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:5 +msgid "gdal_translate" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:9 +msgid "Converts raster data between different formats." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:45 +msgid "" +"The :program:`gdal_translate` utility can be used to convert raster data " +"between different formats, potentially performing some operations like " +"subsettings, resampling, and rescaling pixels in the process." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:57 +msgid "" +"Don't be forgiving of mismatches and lost data when translating to the " +"output format." +msgstr "" + +#: ../../source/programs/options/if.rst:3 +msgid "" +"Format/driver name to be attempted to open the input file(s). It is " +"generally not necessary to specify it, but it can be used to skip " +"automatic driver detection, when it fails to select the appropriate " +"driver. This option can be repeated several times to specify several " +"candidate drivers. Note that it does not force those drivers to open the " +"dataset. In particular, some drivers have requirements on file " +"extensions." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:66 +msgid "" +"Select an input band **band** for output. Bands are numbered from 1. " +"Multiple :option:`-b` switches may be used to select a set of input bands" +" to write to the output file, or to reorder bands. **band** can also be " +"set to \"mask,1\" (or just \"mask\") to mean the mask band of the first " +"band of the input dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:74 +msgid "" +"Select an input band **band** to create output dataset mask band. Bands " +"are numbered from 1. **band** can be set to \"none\" to avoid copying the" +" global mask of the input dataset if it exists. Otherwise it is copied by" +" default (\"auto\"), unless the mask is an alpha channel, or if it is " +"explicitly used to be a regular band of the output dataset (\"-b mask\")." +" **band** can also be set to \"mask,1\" (or just \"mask\") to mean the " +"mask band of the 1st band of the input dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:84 +msgid "" +"To expose a dataset with 1 band with a color table as a dataset with 3 " +"(RGB) or 4 (RGBA) bands. Useful for output drivers such as JPEG, " +"JPEG2000, MrSID, ECW that don't support color indexed datasets. The " +"'gray' value enables to expand a dataset with a color table that only " +"contains gray levels to a gray indexed dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:92 +msgid "" +"Set the size of the output file. Outsize is in pixels and lines unless " +"'%' is attached in which case it is as a fraction of the input image " +"size. If one of the 2 values is set to 0, its value will be determined " +"from the other one, while maintaining the aspect ratio of the source " +"dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:99 +msgid "" +"set target resolution. The values must be expressed in georeferenced " +"units. Both must be positive values. This is mutually exclusive with " +":option:`-outsize`, :option:`-a_ullr`, and :option:`-a_gt`." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:107 +msgid "" +"To specify which overview level of source file must be used. The default " +"choice, AUTO, will select the overview level whose resolution is the " +"closest to the target resolution. Specify an integer value (0-based, i.e." +" 0=1st overview level) to select a particular level. Specify AUTO-n where" +" n is an integer greater or equal to 1, to select an overview level below" +" the AUTO one. Or specify NONE to force the base resolution to be used " +"(can be useful if overviews have been generated with a low quality " +"resampling method, and a higher quality resampling method is specified " +"with :option:`-r`." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:116 +msgid "" +"When :option:`-ovr` is specified to an integer value, and none of " +":option:`-outsize` and :option:`-tr` is specified, the size of the " +"overview will be used as the output size." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:120 +msgid "" +"When :option:`-ovr` is specified, values of :option:`-srcwin`, when " +"specified, should be expressed as pixel offset and size of the full " +"resolution source dataset. Similarly when using :option:`-outsize` with " +"percentage values, they refer to the size of the full resolution source " +"dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:127 +msgid "Select a resampling algorithm." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:129 +msgid "" +"``nearest`` (default) applies a nearest neighbour (simple sampling) " +"resampler" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:131 +#: ../../source/programs/gdaladdo.rst:49 +msgid "" +"``average`` computes the average of all non-NODATA contributing pixels. " +"Starting with GDAL 3.1, this is a weighted average taking into account " +"properly the weight of source pixels not contributing fully to the target" +" pixel." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:133 +#: ../../source/programs/gdaladdo.rst:51 +msgid "" +"``rms`` computes the root mean squared / quadratic mean of all non-NODATA" +" contributing pixels (GDAL >= 3.3)" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:135 +#: ../../source/programs/gdaladdo.rst:53 +msgid "``bilinear`` applies a bilinear convolution kernel." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:137 +#: ../../source/programs/gdaladdo.rst:60 +msgid "``cubic`` applies a cubic convolution kernel." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:139 +#: ../../source/programs/gdaladdo.rst:62 +msgid "``cubicspline`` applies a B-Spline convolution kernel." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:141 +#: ../../source/programs/gdaladdo.rst:64 +msgid "``lanczos`` applies a Lanczos windowed sinc convolution kernel." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:143 +#: ../../source/programs/gdaladdo.rst:68 +msgid "" +"``mode`` selects the value which appears most often of all the sampled " +"points." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:147 +msgid "" +"Rescale the input pixels values from the range **src_min** to **src_max**" +" to the range **dst_min** to **dst_max**. If omitted the output range is " +"0 to 255. If omitted the input range is automatically computed from the " +"source dataset, in its whole (not just the window of interest potentially" +" specified with :option:`-srcwin` or :option:`-projwin`). This may be a " +"slow operation on a large source dataset, and if using it multiple times " +"for several gdal_translate invocation, it might be beneficial to call " +"``gdalinfo -stats {source_dataset}`` priorly to precompute statistics, " +"for formats that support serializing statistics computations (GeoTIFF, " +"VRT...) Note that the values specified after :option:`-scale` are only " +"used to compute a scale and offset to apply to the input raster values. " +"In particular, ``src_min`` and ``src_max`` are not used to clip input " +"values. :option:`-scale` can be repeated several times (if specified only" +" once, it also applies to all bands of the output dataset), so as to " +"specify per band parameters. It is also possible to use the \"-scale_bn\"" +" syntax where bn is a band number (e.g. \"-scale_2\" for the 2nd band of " +"the output dataset) to specify the parameters of one or several specific " +"bands." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:168 +msgid "" +"To apply non-linear scaling with a power function. exp_val is the " +"exponent of the power function (must be positive). This option must be " +"used with the -scale option. If specified only once, -exponent applies to" +" all bands of the output image. It can be repeated several times so as to" +" specify per band parameters. It is also possible to use the " +"\"-exponent_bn\" syntax where bn is a band number (e.g. \"-exponent_2\" " +"for the 2nd band of the output dataset) to specify the parameters of one " +"or several specific bands." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:178 +msgid "" +"Apply the scale/offset metadata for the bands to convert scaled values to" +" unscaled values. It is also often necessary to reset the output " +"datatype with the :option:`-ot` switch. The unscaled value is computed " +"from the scaled raw value with the following formula:" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:184 +msgid "" +"{unscaled\\_value} = {scaled\\_value} * {scale} + {offset}\n" +"\n" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:193 +msgid "" +"Selects a subwindow from the source image for copying (like " +":option:`-srcwin`) but with the corners given in georeferenced " +"coordinates (by default expressed in the SRS of the dataset. Can be " +"changed with :option:`-projwin_srs`)." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:200 +msgid "" +"In GDAL 2.1.0 and 2.1.1, using -projwin with coordinates not aligned with" +" pixels will result in a sub-pixel shift. This has been corrected in " +"later versions. When selecting non-nearest neighbour resampling, starting" +" with GDAL 2.1.0, sub-pixel accuracy is however used to get better " +"results." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:208 +msgid "" +"Specifies the SRS in which to interpret the coordinates given with " +":option:`-projwin`. The <srs_def> may be any of the usual GDAL/OGR forms," +" complete WKT, PROJ.4, EPSG:n or a file containing the WKT." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:213 +msgid "This does not cause reprojection of the dataset to the specified SRS." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:217 +msgid "" +"(Error when Partially Outside) If this option is set, :option:`-srcwin` " +"or :option:`-projwin` values that falls partially outside the source " +"raster extent will be considered as an error. The default behavior is to " +"accept such requests, when they were considered as an error before." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:224 +msgid "" +"(Error when Completely Outside) Same as :option:`-epo`, except that the " +"criterion for erroring out is when the request falls completely outside " +"the source raster extent." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:230 +msgid "" +"Override the projection for the output file. Can be used with " +":option:`-a_ullr` or :option:`-a_gt` to specify the extent in this " +"projection." +msgstr "" + +#: ../../source/programs/options/srs_def.rst:1 +msgid "" +"The coordinate reference systems that can be passed are anything " +"supported by the :cpp:func:`OGRSpatialReference::SetFromUserInput` call, " +"which includes EPSG Projected, Geographic or Compound CRS (i.e. " +"EPSG:4296), a well known text (WKT) CRS definition, PROJ.4 declarations, " +"or the name of a .prj file containing a WKT CRS definition." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:235 +msgid "No reprojection is done." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:241 +msgid "" +"Assign a coordinate epoch, linked with the output SRS. Useful when the " +"output SRS is a dynamic CRS." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:246 +msgid "" +"Set band scaling value. No modification of pixel values is done. Note " +"that the :option:`-unscale` does not take into account " +":option:`-a_scale`. You may for example specify ``-scale 0 1 <offset> " +"<offset+scale>`` to apply a (offset, scale) tuple, for the equivalent of " +"the 2 steps: ``gdal_translate input.tif tmp.vrt -a_scale scale -a_offset " +"offset`` followed by ``gdal_translate tmp.vrt output.tif -unscale``" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:257 +msgid "" +"Set band offset value. No modification of pixel values is done. Note that" +" the :option:`-unscale` does not take into account :option:`-a_offset`. " +"You may for example specify ``-scale 0 1 <offset> <offset+scale>`` to " +"apply a (offset, scale) tuple, for the equivalent of the 2 steps: " +"``gdal_translate input.tif tmp.vrt -a_scale scale -a_offset offset`` " +"followed by ``gdal_translate tmp.vrt output.tif -unscale``" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:268 +msgid "" +"Assign/override the georeferenced bounds of the output file. This " +"assigns georeferenced bounds to the output file, ignoring what would have" +" been derived from the source file. So this does not cause reprojection " +"to the specified SRS. This is mutually exclusive with :option:`-a_gt`" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:276 +msgid "" +"Assign/override the geotransform of the output file. This assigns the " +"geotransform to the output file, ignoring what would have been derived " +"from the source file. So this does not cause reprojection to the " +"specified SRS. See :ref:`geotransforms_tut`. This is mutually exclusive " +"with :option:`-a_ullr`" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:286 +msgid "" +"Assign a specified nodata value to output bands. It can be set to " +"``none`` to avoid setting a nodata value to the output file if one exists" +" for the source file. Note that, if the input dataset has a nodata value," +" this does not cause pixel values that are equal to that nodata value to " +"be changed to the value specified with this option." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:294 +msgid "" +"Override the color interpretation of band X (where X is a valid band " +"number, starting at 1)" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:301 +msgid "" +"Override the color interpretation of all specified bands. For example " +"-colorinterp red,green,blue,alpha for a 4 band output dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:312 +msgid "" +"Passes a metadata key and value in specified domain to set on the output " +"dataset if possible." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:334 +msgid "" +"In addition to the driver-specific creation options, gdal_translate (and " +":cpp:func:`GDALTranslate` and :cpp:func:`GDALCreateCopy`) recognize the " +"following options:" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:342 +msgid "" +"Can be specified to YES to avoid prior destruction of existing dataset, " +"for drivers that support adding several subdatasets (e.g. GTIFF, NITF)" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:350 +msgid "" +"Defines if metadata domains of the source dataset should be copied to the" +" destination dataset. In the default AUTO mode, only \"safe\" domains " +"will be copied, which include the default metadata domain (some drivers " +"may include other domains such as IMD, RPC, GEOLOCATION). When setting " +"YES, all domains will be copied (but a few reserved ones like " +"IMAGE_STRUCTURE or DERIVED_SUBDATASETS). Currently only recognized by the" +" GTiff, COG, VRT, PNG and JPEG drivers." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:359 +msgid "When setting NO, no source metadata will be copied." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:365 +msgid "" +"Defines which source metadata domain should be copied. This option " +"restricts the list of source metadata domains to be copied (it implies " +"COPY_SRC_MDD=YES if it is not set). This option may be specified as many " +"times as they are source domains. The default metadata domain is the " +"empty string \"\" (\"_DEFAULT_\") may also be used when empty string is " +"not practical). Currently only recognized by the GTiff, COG, VRT, PNG and" +" JPEG drivers." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:374 +msgid "Do not copy the GCPs in the source dataset to the output dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:378 +msgid "" +"Add the indicated ground control point to the output dataset. This " +"option may be provided multiple times to provide a set of GCPs." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:387 +msgid "" +"Copy all subdatasets of this file to individual output files. Use with " +"formats like HDF that have subdatasets." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:392 +msgid "Force (re)computation of statistics." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:396 +msgid "Do not copy source RAT into destination dataset." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:400 +msgid "" +"Do not copy the XMP metadata in the source dataset to the output dataset " +"when driver is able to copy it." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:419 +#: ../../source/programs/gdaladdo.rst:258 +msgid "Nodata / source validity mask handling during resampling" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:421 +msgid "" +"Masked values, either identified through a nodata value metadata set on " +"the source band, a mask band, an alpha band will not be used during " +"resampling (when using :option:`-outsize` or :option:`-tr`)." +msgstr "" + +#: ../../source/programs/nodata_handling_gdaladdo_gdal_translate.rst:1 +msgid "" +"The details of how it is taken into account depends on the resampling " +"kernel:" +msgstr "" + +#: ../../source/programs/nodata_handling_gdaladdo_gdal_translate.rst:3 +msgid "" +"for nearest resampling, for each target pixel, one of the potential " +"contributing source pixels is selected (in an implementation specific " +"way). Its value is used as it, be it valid or invalid." +msgstr "" + +#: ../../source/programs/nodata_handling_gdaladdo_gdal_translate.rst:7 +msgid "" +"for bilinear, cubic, cubicspline and lanczos, for each target pixel, the " +"weights of contributing source pixels is set to zero to ignore them when " +"they are masked. There is an extra specificity for cubic: given that some" +" of the weights in the kernel are negative, such strategy could lead to " +"strong overshoot/undershoot when there is an alternance of valid and " +"invalid pixels. Consequently, if any of the horizontal or vertical " +"direction, if the maximum number of valid source pixels in each dimension" +" is less than the radius of the resampling kernel, the target pixel is " +"considered as nodata." +msgstr "" + +#: ../../source/programs/nodata_handling_gdaladdo_gdal_translate.rst:16 +msgid "" +"for the other resampling methods, source pixels contributing to the " +"target pixel are ignored if masked. Only the valid ones are taken into " +"account. If there are none, the target pixel is considered as nodata." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:430 +msgid "This utility is also callable from C with :cpp:func:`GDALTranslate`." +msgstr "" + +#: ../../source/programs/gdal_translate.rst:442 +msgid "To create a JPEG-compressed TIFF with internal mask from a RGBA dataset" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:450 +msgid "To create a RGBA dataset from a RGB dataset with a mask" +msgstr "" + +#: ../../source/programs/gdal_translate.rst:457 +msgid "Subsetting using :option:`-projwin` and :option:`-outsize`:" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:5 +msgid "gdal_viewshed" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:11 +msgid "" +"Calculates a viewshed raster from an input raster DEM using method " +"defined in [Wang2000]_ for a user defined point." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:33 +msgid "" +"By default the :program:`gdal_viewshed` generates a binary visibility " +"raster from one band of the input raster elevation model (DEM). The " +"output raster will be of type Byte. With the -mode flag can also return a" +" minimum visible height raster of type Float64." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:38 +msgid "" +"The algorithm as implemented currently will only output meaningful " +"results if the georeferencing is in a projected coordinate reference " +"system." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:49 +msgid "" +"Select an input band **band** containing the DEM data. Bands are numbered" +" from 1. Only a single band can be used. Only the part of the raster " +"within the specified maximum distance around the observer point is " +"processed." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:55 +msgid "The value to be set for the cells in the output raster that have no data." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:58 +msgid "" +"Currently, no special processing of input cells at a nodata value is done" +" (which may result in erroneous results)." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:63 +msgid "The X position of the observer (in SRS units)." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:67 +msgid "The Y position of the observer (in SRS units)." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:71 +msgid "" +"The height of the observer above the DEM surface in the height unit of " +"the DEM. Default: 2" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:75 +msgid "" +"The height of the target above the DEM surface in the height unit of the " +"DEM. Default: 0" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:79 +msgid "" +"Maximum distance from observer to compute visibiliy. It is also used to " +"clamp the extent of the output raster." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:84 +msgid "" +"Coefficient to consider the effect of the curvature and refraction. When " +"calculating visibility between two points (i.e. Line Of Sight or " +"Viewshed), The magnitude of this effect varies with atmospheric " +"conditions and depends on the wavelength." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:88 +msgid "" +"Different applications for calculating visibility use different " +"interchangeable notation to describe this phenomena: Refraction " +"Coefficient, Curvature Coefficient, and Sphere Diameter Factor. " +"gdal_viewshed uses the Curvature Coefficient notation." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:92 +msgid "{CurvCoeff}=1-{RefractionCoeff}" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:96 +msgid "" +"Changes in air density curve the light downward causing an observer to " +"see further and the earth to appear less curved, as if the sphere (earth)" +" diameter is larger then it actually is. The ratio between that imaginary" +" sphere diameter and the actual sphere diameter is given by the formula:" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:100 +msgid "" +"{SphereDiameterFactor}=1/{CurvCoeff}=1/(1-{RefractionCoeff})\n" +"\n" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:103 +msgid "" +"For visible light, the standard atmospheric refraction coefficient that " +"is generally used is 1/7. Thus the default value (since GDAL 3.4) for " +"CurvCoeff that gdal_viewshed uses is 0.85714 (=~ 1-1/7) for Earth CRS. " +"Starting with GDAL 3.6, for non-Earth CRS (those whole semi-major axis " +"differs by more than 5% with the one of WGS 84), CurvCoeff default value " +"is 1.0, to account for the no refraction use case." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:109 +msgid "The height of the DEM is corrected according to the following formula:" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:111 +msgid "Height_{Corrected}=Height_{DEM}-{CurvCoeff}\\frac{{TargetDistance}^2}{SphereDiameter}" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:115 +msgid "" +"Typical coefficient values are given in the table below (use Curvature " +"Coeff value for the cc option)" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:118 +msgid "Use Case" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:118 +msgid "Refraction Coeff" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:118 +msgid "**Curvature Coeff**" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:118 +msgid "Sphere Diameter Factor" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:119 +msgid "No Refraction" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:119 +#: ../../source/programs/gdal_viewshed.rst:122 +msgid "0" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:119 +#: ../../source/programs/gdal_viewshed.rst:122 +msgid "1" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:120 +msgid "Visible Light" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:120 +msgid "1/7" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:120 +msgid "6/7 (=~0.85714)" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:120 +msgid "7/6 (=~1.1666)" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:121 +msgid "Radio Waves" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:121 +msgid "0.25 ~ 0.325" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:121 +msgid "0.75 ~ 0.675" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:121 +msgid "1.33 ~ 1.48" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:122 +msgid "Flat Earth" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:122 +msgid "inf" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:127 +msgid "Pixel value to set for invisible areas. Default: 0" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:131 +msgid "" +"Pixel value to set for the cells that fall outside of the range specified" +" by the observer location and the maximum distance. Default: 0" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:136 +msgid "Pixel value to set for visible areas. Default: 255" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:140 +msgid "Sets what information the output contains." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:142 +msgid "Possible values: NORMAL, DEM, GROUND" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:144 +msgid "NORMAL returns a raster of type Byte containing visible locations." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:146 +msgid "" +"DEM and GROUND will return a raster of type Float64 containing the " +"minimum target height for target to be visible from the DEM surface or " +"ground level respectively. Flags -tz, -iv and -vv will be ignored." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:150 +msgid "Default NORMAL" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:155 +msgid "" +"Functionality of this utility can be done from C with " +":cpp:func:`GDALViewshedGenerate`." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:160 +msgid "" +"Screenshot of 2 combined viewshed analysis, with the yellow pixels " +"showing the area that is visible from the both observation locations (the" +" green dots), while the small green area is only visible from one " +"location." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:168 +msgid "" +"Create a viewshed raster with a radius of 500 for a person standing at " +"location (-10147017, 5108065)." +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:175 +msgid "Reference" +msgstr "" + +#: ../../source/programs/gdal_viewshed.rst:177 +msgid "" +"Generating Viewsheds without Using Sightlines. Wang, Jianjun, Robinson, " +"Gary J., and White, Kevin. Photogrammetric Engineering and Remote " +"Sensing. p81. https://www.asprs.org/wp-" +"content/uploads/pers/2000journal/january/2000_jan_87-90.pdf" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:5 +msgid "gdaladdo" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:9 +msgid "Builds or rebuilds overview images." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:29 +msgid "" +"The :program:`gdaladdo` utility can be used to build or rebuild overview " +"images for most supported file formats with one of several downsampling " +"algorithms." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:38 +msgid "" +"Select a resampling algorithm. The default is ``nearest``, which is " +"generally not appropriate if sub-pixel accuracy is desired." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:41 +msgid "" +"Starting with GDAL 3.9, when refreshing existing TIFF overviews, the " +"previously used method, as noted in the RESAMPLING metadata item of the " +"overview, will be used if :option:`-r` is not specified." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:45 +msgid "The available methods are:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:47 +msgid "``nearest`` applies a nearest neighbour (simple sampling) resampler." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:55 +msgid "" +"``gauss`` applies a Gaussian kernel before computing the overview, which " +"can lead to better results than simple averaging in e.g case of sharp " +"edges with high contrast or noisy patterns. The advised level values " +"should be 2, 4, 8, ... so that a 3x3 resampling Gaussian kernel is " +"selected." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:66 +msgid "``average_magphase`` averages complex data in mag/phase space." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:72 +msgid "" +"Select an input band **band** for overview generation. Band numbering " +"starts from 1. Multiple :option:`-b` switches may be used to select a set" +" of input bands to generate overviews." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:78 +msgid "" +"open the dataset in read-only mode, in order to generate external " +"overview (for GeoTIFF especially)." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:83 +msgid "remove all overviews." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:91 +msgid "" +"Maximum width or height of the smallest overview level. Only taken into " +"account if explicit levels are not specified. Defaults to 256." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:100 +msgid "" +"This option performs a partial refresh of existing overviews, when " +"<filename> is a VRT file with an external overview. It checks the " +"modification timestamp of all the sources of the VRT and regenerate the " +"overview for areas corresponding to sources whose timestamp is more " +"recent than the external overview of the VRT. By default all existing " +"overview levels will be refreshed, unless explicit levels are specified." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:112 +msgid "" +"This option performs a partial refresh of existing overviews, in the " +"region of interest specified by georeference coordinates where <ulx> is " +"the X value of the upper left corner, <uly> is the Y value of the upper " +"left corner, <lrx> is the X value of the lower right corner and <lry> is " +"the Y value of the lower right corner. By default all existing overview " +"levels will be refreshed, unless explicit levels are specified." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:124 +msgid "" +"This option performs a partial refresh of existing overviews, in the " +"region of interest specified by one or several filenames (names separated" +" by comma). Note that the filenames are only used to determine the " +"regions of interest to refresh. The reference source pixels are the one " +"of the main dataset. By default all existing overview levels will be " +"refreshed, unless explicit levels are specified." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:133 +msgid "The file to build overviews for (or whose overviews must be removed)." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:137 +msgid "" +"A list of integral overview levels to build. Ignored with " +":option:`-clean` option." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:141 +msgid "" +"Levels are no longer required to build overviews. In which case, " +"appropriate overview power-of-two factors will be selected until the " +"smallest overview is smaller than the value of the -minsize switch." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:145 +msgid "" +"Starting with GDAL 3.9, if there are already existing overviews, the " +"corresponding levels will be used to refresh them if no explicit levels " +"are specified." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:150 +msgid "" +"gdaladdo will honour properly NODATA_VALUES tuples (special dataset " +"metadata) so that only a given RGB triplet (in case of a RGB image) will " +"be considered as the nodata value and not each value of the triplet " +"independently per band." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:154 +msgid "" +"Selecting a level value like ``2`` causes an overview level that is 1/2 " +"the resolution (in each dimension) of the base layer to be computed. If " +"the file has existing overview levels at a level selected, those levels " +"will be recomputed and rewritten in place." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:159 +msgid "" +"For internal GeoTIFF overviews (or external overviews in GeoTIFF format)," +" note that -clean does not shrink the file. A later run of gdaladdo with " +"overview levels will cause the file to be expanded, rather than reusing " +"the space of the previously deleted overviews. If you just want to change" +" the resampling method on a file that already has overviews computed, you" +" don't need to clean the existing overviews." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:165 +msgid "" +"Some format drivers do not support overviews at all. Many format drivers" +" store overviews in a secondary file with the extension .ovr that is " +"actually in TIFF format. By default, the GeoTIFF driver stores overviews" +" internally to the file operated on (if it is writable), unless the -ro " +"flag is specified." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:170 +msgid "" +"Most drivers also support an alternate overview format using Erdas " +"Imagine format. To trigger this use the :config:`USE_RRD=YES` " +"configuration option. This will place the overviews in an associated " +".aux file suitable for direct use with Imagine or ArcGIS as well as GDAL " +"applications. (e.g. --config USE_RRD YES)" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:176 +msgid "External overviews in GeoTIFF format" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:178 +msgid "" +"External overviews created in TIFF format may be compressed using the " +":config:`COMPRESS_OVERVIEW` configuration option. All compression " +"methods, supported by the GeoTIFF driver, are available here. (e.g. " +"``--config COMPRESS_OVERVIEW DEFLATE``). The photometric interpretation " +"can be set with the :config:`PHOTOMETRIC_OVERVIEW` =RGB/YCBCR/... " +"configuration option, and the interleaving with the " +":config:`INTERLEAVE_OVERVIEW` =PIXEL/BAND configuration option." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:185 +msgid "" +"Since GDAL 3.6, :config:`COMPRESS_OVERVIEW` and " +":config:`INTERLEAVE_OVERVIEW` are honoured when creating internal " +"overviews of TIFF files." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:188 +msgid "" +"For JPEG compressed external and internal overviews, the JPEG quality can" +" be set with ``--config JPEG_QUALITY_OVERVIEW value``." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:191 +msgid "" +"For WEBP compressed external and internal overviews, the WEBP quality " +"level can be set with ``--config WEBP_LEVEL_OVERVIEW value``. If not set," +" will default to 75." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:194 +msgid "" +"For WEBP compressed external and internal overviews, the WEBP " +"lossless/lossy switch can be set with ``--config WEBP_LOSSLESS_OVERVIEW " +"value``. If not set, will default to NO (lossy). Added in GDAL 3.6.0" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:197 +msgid "" +"For LERC compressed external and internal overviews, the max error " +"threshold can be set with ``--config MAX_Z_ERROR_OVERVIEW value``. If not" +" set, will default to 0 (lossless). Added in GDAL 3.4.1" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:200 +msgid "" +"For DEFLATE or LERC_DEFLATE compressed external and internal overviews, " +"the compression level can be set with ``--config ZLEVEL_OVERVIEW value``." +" If not set, will default to 6. Added in GDAL 3.4.1" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:203 +msgid "" +"For ZSTD or LERC_ZSTD compressed external and internal overviews, the " +"compression level can be set with ``--config ZSTD_LEVEL_OVERVIEW value``." +" If not set, will default to 9. Added in GDAL 3.4.1" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:206 +msgid "" +"For JPEG-XL compressed external and internal overviews, the following " +"settings can be set since GDAL 3.9.0:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:208 +msgid "" +"Whether compression should be lossless with ``--config " +"JXL_LOSSLESS_OVERVIEW YES|NO``. Default is YES" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:210 +msgid "" +"Level of effort with ``--config JXL_EFFORT_OVERVIEW value``, with value " +"between 1(fast) and 9(flow). Default is 5" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:212 +msgid "" +"Distance level for lossy compression with ``--config " +"JXL_DISTANCE_OVERVIEW value``, with value: 0=mathematically lossless, " +"1.0=visually lossless, usual range [0.5,3]. Default is 1.0. Ignored if " +"JXL_LOSSLESS_OVERVIEW is YES" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:214 +msgid "" +"Distance level for lossy compression of alpha channel with ``--config " +"JXL_ALPHA_DISTANCE_OVERVIEW value``, with value: 0=mathematically " +"lossless, 1.0=visually lossless, usual range [0.5,3]. Default is the same" +" value as JXL_DISTANCE_OVERVIEW. Ignored if JXL_LOSSLESS_OVERVIEW is YES" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:217 +msgid "" +"For LZW, ZSTD or DEFLATE compressed external overviews, the predictor " +"value can be set with ``--config PREDICTOR_OVERVIEW 1|2|3``." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:220 +msgid "To produce the smallest possible JPEG-In-TIFF overviews, you should use:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:226 +msgid "" +"External overviews can be created in the BigTIFF format by using the " +":config:`BIGTIFF_OVERVIEW` configuration option: ``--config " +"BIGTIFF_OVERVIEW {IF_NEEDED|IF_SAFER|YES|NO}``." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:230 +msgid "" +"The default value is IF_SAFER starting with GDAL 2.3.0 (previously was " +"IF_NEEDED). The behavior of this option is exactly the same as the " +"BIGTIFF creation option documented in the GeoTIFF driver documentation." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:234 +msgid "YES forces BigTIFF." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:235 +msgid "NO forces classic TIFF." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:236 +msgid "" +"IF_NEEDED will only create a BigTIFF if it is clearly needed " +"(uncompressed, and overviews larger than 4GB)." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:238 +msgid "IF_SAFER will create BigTIFF if the resulting file *might* exceed 4GB." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:240 +msgid "" +"Sparse GeoTIFF overview files (that is tiles which are omitted if all " +"their pixels are at the nodata value, when there's one, or at 0 " +"otherwise) can be obtained with ``--config SPARSE_OK_OVERVIEW ON``. Added" +" in GDAL 3.4.1" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:244 +msgid "" +"See the documentation of the :ref:`raster.gtiff` driver for further " +"explanations on all those options." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:247 +msgid "Setting blocksize in Geotiff overviews" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:249 +msgid "``--config GDAL_TIFF_OVR_BLOCKSIZE <size>``" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:251 +msgid "Example: ``--config GDAL_TIFF_OVR_BLOCKSIZE 256``" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:253 +msgid "" +"Default value is 128, or starting with GDAL 3.1, if creating overviews on" +" a tiled GeoTIFF file, the tile size of the full resolution image. Note: " +"without this setting, the file can have the full resolution image with a " +"blocksize different from overviews blocksize.(e.g. full resolution image " +"at blocksize 256, overviews at blocksize 128)" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:260 +msgid "" +"Invalid values in source pixels, either identified through a nodata value" +" metadata set on the source band, a mask band, an alpha band will not be " +"used during resampling." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:267 ../../source/programs/sozip.rst:137 +msgid "Multithreading" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:271 +msgid "" +"The :config:`GDAL_NUM_THREADS` configuration option can be set to " +"``ALL_CPUS`` or a integer value to specify the number of threads to use " +"for overview computation." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:278 +msgid "" +"Functionality of this utility can be done from C with " +":cpp:func:`GDALBuildOverviews`." +msgstr "" + +#: ../../source/programs/gdaladdo.rst:283 +msgid "" +"Create overviews, embedded in the supplied TIFF file, with automatic " +"computation of levels (GDAL 2.3 or later)" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:290 +msgid "Create overviews, embedded in the supplied TIFF file:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:296 +msgid "" +"Create an external compressed GeoTIFF overview file from the ERDAS .IMG " +"file:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:302 +msgid "" +"Create an external JPEG-compressed GeoTIFF overview file from a 3-band " +"RGB dataset (if the dataset is a writable GeoTIFF, you also need to add " +"the -ro option to force the generation of external overview):" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:311 +msgid "Create an Erdas Imagine format overviews for the indicated JPEG file:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:317 +msgid "" +"Create overviews for a specific subdataset, like for example one of " +"potentially many raster layers in a GeoPackage (the \"filename\" " +"parameter must be driver prefix, filename and subdataset name, like e.g. " +"shown by gdalinfo):" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:324 +msgid "" +"Refresh overviews of a VRT file, for sources that have been modified " +"after the .vrt.ovr generation:" +msgstr "" + +#: ../../source/programs/gdaladdo.rst:335 +msgid "Refresh overviews of a TIFF file:" +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:5 +msgid "gdalattachpct" +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:9 +msgid "Attach a color table from one file to another file." +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:24 +msgid "" +"This utility will attach a color table file from an input raster file or " +"a color table file to another raster." +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:28 +msgid "" +"gdalattachpct is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:42 +msgid "" +"Extract the color table from <palette_file>. The<palette_file> must be " +"either a raster file in a GDAL supported format with a palette or a color" +" file in a supported format (txt, qml, qlr)." +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:48 +#: ../../source/programs/pct2rgb.rst:58 +msgid "The input file." +msgstr "" + +#: ../../source/programs/gdalattachpct.rst:52 +#: ../../source/programs/pct2rgb.rst:62 +msgid "The output RGB file that will be created." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:5 +msgid "gdalbuildvrt" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:9 +msgid "Builds a VRT from a list of datasets." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:38 +msgid "" +"This program builds a VRT (Virtual Dataset) that is a mosaic of the list " +"of input GDAL datasets. The list of input GDAL datasets can be specified " +"at the end of the command line, or put in a text file (one filename per " +"line) for very long lists, or it can be a MapServer tileindex (see " +":ref:`gdaltindex` utility). In the later case, all entries in the tile " +"index will be added to the VRT." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:46 +msgid "" +"Starting with GDAL 3.9, for virtual mosaic with a very large number of " +"source rasters (typically hundreds of thousands of source rasters, or " +"more), it is advised to use the :ref:`gdaltindex` utility to generate a " +"tile index compatible of the :ref:`GTI <raster.gti>` driver." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:51 +msgid "" +"With -separate, each files goes into a separate band in the VRT dataset. " +"Otherwise, the files are considered as source rasters of a larger mosaic " +"and the VRT file has as many bands as one of the input files." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:55 +msgid "" +"If one GDAL dataset is made of several subdatasets and has 0 raster " +"bands, all the subdatasets will be added to the VRT rather than the " +"dataset itself." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:58 +msgid "" +"gdalbuildvrt does some amount of checks to assure that all files that " +"will be put in the resulting VRT have similar characteristics : number of" +" bands, projection, color interpretation... If not, files that do not " +"match the common characteristics will be skipped. (This is only true in " +"the default mode, and not when using the -separate option)" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:63 +msgid "" +"If there is some amount of spatial overlapping between files, the order " +"of files appearing in the list of source matter: files that are listed at" +" the end are the ones from which the content will be fetched. Note that " +"nodata will be taken into account to potentially fetch data from less " +"priority datasets, but currently, alpha channel is not taken into account" +" to do alpha compositing (so a source with alpha=0 appearing on top of " +"another source will override is content). This might be changed in later " +"versions." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:77 +msgid "" +"Use the specified value as the tile index field, instead of the default " +"value which is 'location'." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:82 +msgid "" +"In case the resolution of all input files is not the same, the " +"-resolution flag enables the user to control the way the output " +"resolution is computed." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:85 +msgid "" +"`highest` will pick the smallest values of pixel dimensions within the " +"set of source rasters." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:87 +msgid "" +"`lowest` will pick the largest values of pixel dimensions within the set " +"of source rasters." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:89 +msgid "" +"`average` is the default and will compute an average of pixel dimensions " +"within the set of source rasters." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:91 +msgid "" +"`user` must be used in combination with the :option:`-tr` option to " +"specify the target resolution." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:95 +msgid "" +"Set target resolution. The values must be expressed in georeferenced " +"units. Both must be positive values. Specifying those values is of course" +" incompatible with highest|lowest|average values for " +":option:`-resolution` option." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:102 +msgid "" +"(target aligned pixels) align the coordinates of the extent of the output" +" file to the values of the :option:`-tr`, such that the aligned extent " +"includes the minimum extent. Alignment means that xmin / resx, ymin / " +"resy, xmax / resx and ymax / resy are integer values." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:109 +msgid "" +"Set georeferenced extents of VRT file. The values must be expressed in " +"georeferenced units. If not specified, the extent of the VRT is the " +"minimum bounding box of the set of source rasters." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:114 +msgid "" +"Adds an alpha mask band to the VRT when the source raster have none. " +"Mainly useful for RGB sources (or grey-level sources). The alpha band is " +"filled on-the-fly with the value 0 in areas without any source raster, " +"and with value 255 in areas with source raster. The effect is that a RGBA" +" viewer will render the areas without source rasters as transparent and " +"areas with source rasters as opaque. This option is not compatible with " +":option:`-separate`." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:122 +msgid "" +"Even if any band contains nodata value, giving this option makes the VRT " +"band not report the NoData. Useful when you want to control the " +"background color of the dataset. By using along with the -addalpha " +"option, you can prepare a dataset which doesn't report nodata value but " +"is transparent in areas with no data." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:130 +msgid "" +"Set nodata values for input bands (different values can be supplied for " +"each band). If more than one value is supplied all values should be " +"quoted to keep them together as a single operating system argument. If " +"the option is not specified, the intrinsic nodata settings on the source " +"datasets will be used (if they exist). The value set by this option is " +"written in the NODATA element of each ComplexSource element. Use a value " +"of `None` to ignore intrinsic nodata settings on the source datasets." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:141 +msgid "" +"Starting with GDAL 3.3, if a source has a mask band (internal/external " +"mask band, or alpha band), a <ComplexSource> element is created by " +"default with a <UseMaskBand>true</UseMaskBand> child element, to instruct" +" the VRT driver to use the mask band of the source to mask pixels being " +"composited. This is a generalization of the NODATA element. When " +"specifying the -ignore_srcmaskband option, the mask band of sources will " +"not be taken into account, and in case of overlapping between sources, " +"the last one will override previous ones in areas of overlap." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:154 +msgid "" +"Insert a <NoDataFromMaskSource> source, which replaces the value of the " +"source with the value of :option:`-vrtnodata` (or 0 if not specified) " +"when the value of the mask band of the source is less or equal to the " +"threshold. This is typically used to transform a R,G,B,A image into a " +"R,G,B one with a NoData value." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:161 +msgid "" +"Select an input <band> to be processed. Bands are numbered from 1. If " +"input bands not set all bands will be added to vrt. Multiple :option:`-b`" +" switches may be used to select a set of input bands." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:167 +msgid "" +"If the input dataset contains several subdatasets, use a subdataset with " +"the specified number (starting from 1). This is an alternative of giving " +"the full subdataset name as an input to the utility." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:173 +msgid "" +"Set nodata values at the VRT band level (different values can be supplied" +" for each band). If more than one value is supplied all values should be" +" quoted to keep them together as a single operating system argument. If " +"the option is not specified, intrinsic nodata settings on the first " +"dataset will be used (if they exist). The value set by this option is " +"written in the NoDataValue element of each VRTRasterBand element. Use a " +"value of `None` to ignore intrinsic nodata settings on the source " +"datasets." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:182 +msgid "" +"Place each input file into a separate band. Contrary to the default mode," +" it is not required that all bands have the same datatype." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:185 +msgid "" +"Starting with GDAL 3.8, all bands of each input file are added as " +"separate VRT bands, unless :option:`-b` is specified to select a subset " +"of them. Before GDAL 3.8, only the first band of each input file was " +"placed into a new VRT band, and :option:`-b` was ignored." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:192 +msgid "" +"When this option is specified, the utility will accept to make a VRT even" +" if the input datasets have not the same projection. Note: this does not " +"mean that they will be reprojected. Their projection will just be " +"ignored." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:198 +msgid "" +"Override the projection for the output file. The <srs_def> may be any of" +" the usual GDAL/OGR forms, complete WKT, PROJ.4, EPSG:n or a file " +"containing the WKT. No reprojection is done." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:203 +msgid "Select a resampling algorithm. Nearest is the default" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:213 +msgid "To specify a text file with an input filename on each line" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:217 +msgid "To disable the progress bar on the console" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:221 +msgid "Overwrite the VRT if it already exists." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:225 +msgid "" +"Turn warnings as failures. This is mutually exclusive with -non_strict, " +"the latter which is the default." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:231 +msgid "" +"Skip source datasets that have issues with warnings, and continue " +"processing. This is the default." +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:238 +msgid "Make a virtual mosaic from all TIFF files contained in a directory :" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:244 +msgid "Make a virtual mosaic from files whose name is specified in a text file :" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:251 +msgid "Make a RGB virtual mosaic from 3 single-band input files :" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:257 +msgid "Make a virtual mosaic with blue background colour (RGB: 0 0 255) :" +msgstr "" + +#: ../../source/programs/gdalbuildvrt.rst:266 +msgid "This utility is also callable from C with :cpp:func:`GDALBuildVRT`." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:5 +msgid "gdalcompare" +msgstr "" + +#: ../../source/programs/gdalcompare.rst:9 +msgid "Compare two images." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:28 +msgid "" +":program:`gdalcompare` compares two GDAL supported datasets and reports " +"the differences. In addition to reporting differences to the standard " +"output the script will also return the difference count in its exit " +"value." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:33 +msgid "" +"Image pixels, and various metadata are checked. There is also a byte by " +"byte comparison done which will count as one difference. So if it is only" +" important that the GDAL visible data is identical a difference count of " +"1 (the binary difference) should be considered acceptable." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:40 +msgid "" +"gdalcompare is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:50 +msgid "" +"Whether to output the difference in pixel content in a TIFF file in the " +"current directory." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:57 +msgid "Whether to skip exact comparison of binary content." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:63 +msgid "Whether to skip comparison of overviews." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:69 +msgid "Whether to skip comparison of GEOLOCATION metadata domain." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:75 +msgid "Whether to skip comparison of geotransform matrix." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:81 +msgid "Whether to skip comparison of metadata" +msgstr "" + +#: ../../source/programs/gdalcompare.rst:87 +msgid "" +"Whether to skip comparison of Rational Polynomial Coefficients (RPC) " +"metadata domain." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:93 +msgid "Whether to skip comparison of spatial reference systems (SRS)." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:97 +msgid "" +"If this flag is passed the script will compare all subdatasets that are " +"part of the dataset, otherwise subdatasets are ignored." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:102 +msgid "The file that is considered correct, referred to as the golden file." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:106 +msgid "The file being compared to the golden file, referred to as the new file." +msgstr "" + +#: ../../source/programs/gdalcompare.rst:109 +msgid "" +"Note that the :program:`gdalcompare` script (like all the other scripts) " +"can also be called as a library from python code: `from osgeo_utils " +"import gdalcompare`. The primary entry point is " +"`gdalcompare.compare_db()` which takes a golden `gdal.Dataset` and a new " +"`gdal.Dataset` as arguments and returns a difference count (excluding the" +" binary comparison). The `gdalcompare.compare_sds()` entry point can be " +"used to compare subdatasets." +msgstr "" + +#: ../../source/programs/gdaldem.rst:5 +msgid "gdaldem" +msgstr "" + +#: ../../source/programs/gdaldem.rst:9 +msgid "Tools to analyze and visualize DEMs." +msgstr "" + +#: ../../source/programs/gdaldem.rst:20 +msgid "From any GDAL-supported elevation raster:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:22 +msgid "Generate a shaded relief map:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:32 +msgid "Generate a slope map:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:41 +msgid "" +"Generate an aspect map, outputs a 32-bit float raster with pixel values " +"from 0-360 indicating azimuth:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:51 +msgid "Generate a color relief map:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:61 +msgid "Generate a Terrain Ruggedness Index (TRI) map:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:69 +msgid "Generate a Topographic Position Index (TPI) map:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:76 +msgid "Generate a roughness map:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:86 +msgid "" +"The :program:`gdaldem` generally assumes that x, y and z units are " +"identical. If x (east-west) and y (north-south) units are identical, but " +"z (elevation) units are different, the scale (-s) option can be used to " +"set the ratio of vertical units to horizontal. For LatLong projections " +"near the equator, where units of latitude and units of longitude are " +"similar, elevation (z) units can be converted to be compatible by using " +"scale=370400 (if elevation is in feet) or scale=111120 (if elevation is " +"in meters). For locations not near the equator, it would be best to " +"reproject your grid using gdalwarp before using gdaldem." +msgstr "" + +#: ../../source/programs/gdaldem.rst:98 +#: ../../source/programs/ogr_layer_algebra.rst:46 +msgid "Where <mode> is one of the seven available modes:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:100 +msgid "``hillshade``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:102 +msgid "Generate a shaded relief map from any GDAL-supported elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:104 +msgid "``slope``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:106 +msgid "Generate a slope map from any GDAL-supported elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:108 +msgid "``aspect``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:110 +msgid "Generate an aspect map from any GDAL-supported elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:112 +msgid "``color-relief``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:114 +msgid "Generate a color relief map from any GDAL-supported elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:116 +msgid "``TRI``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:118 +msgid "" +"Generate a map of Terrain Ruggedness Index from any GDAL-supported " +"elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:120 +msgid "``TPI``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:122 +msgid "" +"Generate a map of Topographic Position Index from any GDAL-supported " +"elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:124 +msgid "``roughness``" +msgstr "" + +#: ../../source/programs/gdaldem.rst:126 +msgid "Generate a map of roughness from any GDAL-supported elevation raster." +msgstr "" + +#: ../../source/programs/gdaldem.rst:128 +msgid "The following general options are available:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:134 +msgid "The input DEM raster to be processed" +msgstr "" + +#: ../../source/programs/gdaldem.rst:138 +msgid "The output raster produced" +msgstr "" + +#: ../../source/programs/gdaldem.rst:142 +msgid "Select the output format." +msgstr "" + +#: ../../source/programs/gdaldem.rst:146 +msgid "" +"If not specified, the format is guessed from the extension (previously " +"was :ref:`raster.gtiff`). Use the short format name." +msgstr "" + +#: ../../source/programs/gdaldem.rst:151 +msgid "Do the computation at raster edges and near nodata values" +msgstr "" + +#: ../../source/programs/gdaldem.rst:155 +msgid "Select an input band to be processed. Bands are numbered from 1." +msgstr "" + +#: ../../source/programs/gdaldem.rst:163 +msgid "" +"For all algorithms, except color-relief, a nodata value in the target " +"dataset will be emitted if at least one pixel set to the nodata value is " +"found in the 3x3 window centered around each source pixel. The " +"consequence is that there will be a 1-pixel border around each image set " +"with nodata value." +msgstr "" + +#: ../../source/programs/gdaldem.rst:168 +msgid "" +"If :option:`-compute_edges` is specified, gdaldem will compute values at " +"image edges or if a nodata value is found in the 3x3 window, by " +"interpolating missing values." +msgstr "" + +#: ../../source/programs/gdaldem.rst:173 +msgid "Modes" +msgstr "" + +#: ../../source/programs/gdaldem.rst:176 +msgid "hillshade" +msgstr "" + +#: ../../source/programs/gdaldem.rst:178 +msgid "" +"This command outputs an 8-bit raster with a nice shaded relief effect. " +"It’s very useful for visualizing the terrain. You can optionally specify " +"the azimuth and altitude of the light source, a vertical exaggeration " +"factor and a scaling factor to account for differences between vertical " +"and horizontal units." +msgstr "" + +#: ../../source/programs/gdaldem.rst:180 +msgid "The value 0 is used as the output nodata value." +msgstr "" + +#: ../../source/programs/gdaldem.rst:182 ../../source/programs/gdaldem.rst:231 +msgid "The following specific options are available :" +msgstr "" + +#: ../../source/programs/gdaldem.rst:186 ../../source/programs/gdaldem.rst:235 +#: ../../source/programs/gdaldem.rst:254 +msgid "" +"The literature suggests Zevenbergen & Thorne to be more suited to smooth " +"landscapes, whereas Horn's formula to perform better on rougher terrain." +msgstr "" + +#: ../../source/programs/gdaldem.rst:190 +msgid "Vertical exaggeration used to pre-multiply the elevations" +msgstr "" + +#: ../../source/programs/gdaldem.rst:194 +msgid "" +"Ratio of vertical units to horizontal. If the horizontal unit of the " +"source DEM is degrees (e.g Lat/Long WGS84 projection), you can use " +"scale=111120 if the vertical units are meters (or scale=370400 if they " +"are in feet)" +msgstr "" + +#: ../../source/programs/gdaldem.rst:198 +msgid "" +"Azimuth of the light, in degrees. 0 if it comes from the top of the " +"raster, 90 from the east, ... The default value, 315, should rarely be " +"changed as it is the value generally used to generate shaded maps." +msgstr "" + +#: ../../source/programs/gdaldem.rst:202 +msgid "" +"Altitude of the light, in degrees. 90 if the light comes from above the " +"DEM, 0 if it is raking light." +msgstr "" + +#: ../../source/programs/gdaldem.rst:206 +msgid "combined shading, a combination of slope and oblique shading." +msgstr "" + +#: ../../source/programs/gdaldem.rst:210 +msgid "" +"multidirectional shading, a combination of hillshading illuminated from " +"225 deg, 270 deg, 315 deg, and 360 deg azimuth." +msgstr "" + +#: ../../source/programs/gdaldem.rst:216 +msgid "" +"shading which tries to minimize effects on other map features beneath. " +"Can't be used with -alt option." +msgstr "" + +#: ../../source/programs/gdaldem.rst:220 +msgid "" +"Multidirectional hillshading applies the formula of " +"http://pubs.usgs.gov/of/1992/of92-422/of92-422.pdf." +msgstr "" + +#: ../../source/programs/gdaldem.rst:222 +msgid "" +"Igor's hillshading uses formula from Maperitive " +"http://maperitive.net/docs/Commands/GenerateReliefImageIgor.html." +msgstr "" + +#: ../../source/programs/gdaldem.rst:225 +msgid "slope" +msgstr "" + +#: ../../source/programs/gdaldem.rst:227 +msgid "" +"This command will take a DEM raster and output a 32-bit float raster with" +" slope values. You have the option of specifying the type of slope value " +"you want: degrees or percent slope. In cases where the horizontal units " +"differ from the vertical units, you can also supply a scaling factor." +msgstr "" + +#: ../../source/programs/gdaldem.rst:229 +msgid "The value `-9999` is used as the output nodata value." +msgstr "" + +#: ../../source/programs/gdaldem.rst:239 +msgid "" +"If specified, the slope will be expressed as percent slope. Otherwise, it" +" is expressed as degrees" +msgstr "" + +#: ../../source/programs/gdaldem.rst:241 +msgid ":option:`-s`" +msgstr "" + +#: ../../source/programs/gdaldem.rst:243 +msgid "" +"Ratio of vertical units to horizontal. If the horizontal unit of the " +"source DEM is degrees (e.g Lat/Long WGS84 projection), you can use " +"scale=111120 if the vertical units are meters (or scale=370400 if they " +"are in feet)." +msgstr "" + +#: ../../source/programs/gdaldem.rst:246 +msgid "aspect" +msgstr "" + +#: ../../source/programs/gdaldem.rst:248 +msgid "" +"This command outputs a 32-bit float raster with values between 0° and " +"360° representing the azimuth that slopes are facing. The definition of " +"the azimuth is such that : 0° means that the slope is facing the North, " +"90° it's facing the East, 180° it's facing the South and 270° it's facing" +" the West (provided that the top of your input raster is north oriented)." +" The aspect value -9999 is used as the nodata value to indicate undefined" +" aspect in flat areas with slope=0." +msgstr "" + +#: ../../source/programs/gdaldem.rst:250 ../../source/programs/gdaldem.rst:273 +msgid "The following specifics options are available :" +msgstr "" + +#: ../../source/programs/gdaldem.rst:258 +msgid "" +"Return trigonometric angle instead of azimuth. Thus 0° means East, 90° " +"North, 180° West, 270° South." +msgstr "" + +#: ../../source/programs/gdaldem.rst:262 +msgid "Return 0 for flat areas with slope=0, instead of -9999." +msgstr "" + +#: ../../source/programs/gdaldem.rst:264 +msgid "" +"By using those 2 options, the aspect returned by gdaldem aspect should be" +" identical to the one of GRASS r.slope.aspect. Otherwise, it's identical " +"to the one of Matthew Perry's :file:`aspect.cpp` utility." +msgstr "" + +#: ../../source/programs/gdaldem.rst:269 +msgid "color-relief" +msgstr "" + +#: ../../source/programs/gdaldem.rst:271 +msgid "" +"This command outputs a 3-band (RGB) or 4-band (RGBA) raster with values " +"are computed from the elevation and a text-based color configuration " +"file, containing the association between various elevation values and the" +" corresponding wished color. By default, the colors between the given " +"elevation values are blended smoothly and the result is a nice colorized " +"DEM. The -exact_color_entry or -nearest_color_entry options can be used " +"to avoid that linear interpolation for values that don't match an index " +"of the color configuration file." +msgstr "" + +#: ../../source/programs/gdaldem.rst:277 +msgid "Text-based color configuration file" +msgstr "" + +#: ../../source/programs/gdaldem.rst:281 +msgid "Add an alpha channel to the output raster" +msgstr "" + +#: ../../source/programs/gdaldem.rst:285 +msgid "" +"Use strict matching when searching in the color configuration file. If " +"none matching color entry is found, the \"0,0,0,0\" RGBA quadruplet will " +"be used" +msgstr "" + +#: ../../source/programs/gdaldem.rst:290 +msgid "" +"Use the RGBA quadruplet corresponding to the closest entry in the color " +"configuration file." +msgstr "" + +#: ../../source/programs/gdaldem.rst:292 +msgid "" +"The color-relief mode is the only mode that supports VRT as output " +"format. In that case, it will translate the color configuration file into" +" appropriate LUT elements. Note that elevations specified as percentage " +"will be translated as absolute values, which must be taken into account " +"when the statistics of the source raster differ from the one that was " +"used when building the VRT." +msgstr "" + +#: ../../source/programs/gdaldem.rst:298 +msgid "" +"The text-based color configuration file generally contains 4 columns per " +"line: the elevation value and the corresponding Red, Green, Blue " +"component (between 0 and 255). The elevation value can be any floating " +"point value, or the nv keyword for the nodata value. The elevation can " +"also be expressed as a percentage: 0% being the minimum value found in " +"the raster, 100% the maximum value." +msgstr "" + +#: ../../source/programs/gdaldem.rst:305 +msgid "" +"An extra column can be optionally added for the alpha component. If it is" +" not specified, full opacity (255) is assumed." +msgstr "" + +#: ../../source/programs/gdaldem.rst:308 +msgid "Various field separators are accepted: comma, tabulation, spaces, ':'." +msgstr "" + +#: ../../source/programs/gdaldem.rst:310 +msgid "" +"Common colors used by GRASS can also be specified by using their name, " +"instead of the RGB triplet. The supported list is: white, black, red, " +"green, blue, yellow, magenta, cyan, aqua, grey/gray, orange, brown, " +"purple/violet and indigo." +msgstr "" + +#: ../../source/programs/gdaldem.rst:315 +msgid "" +"GMT :file:`.cpt` palette files are also supported (COLOR_MODEL = RGB " +"only)." +msgstr "" + +#: ../../source/programs/gdaldem.rst:317 +msgid "" +"Note: the syntax of the color configuration file is derived from the one " +"supported by GRASS r.colors utility. ESRI HDR color table files (.clr) " +"also match that syntax. The alpha component and the support of tab and " +"comma as separators are GDAL specific extensions." +msgstr "" + +#: ../../source/programs/gdaldem.rst:322 +msgid "For example:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:334 +msgid "" +"To implement a \"round to the floor value\" mode, the elevation value can" +" be duplicate with a new value being slightly above the threshold. For " +"example to have red in [0,10], green in ]10,20] and blue in ]20,30]:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:348 +msgid "TRI" +msgstr "" + +#: ../../source/programs/gdaldem.rst:350 +msgid "" +"This command outputs a single-band raster with values computed from the " +"elevation. `TRI` stands for Terrain Ruggedness Index, which measures the " +"difference between a central pixel and its surrounding cells." +msgstr "" + +#: ../../source/programs/gdaldem.rst:354 ../../source/programs/gdaldem.rst:379 +#: ../../source/programs/gdaldem.rst:390 +msgid "The value -9999 is used as the output nodata value." +msgstr "" + +#: ../../source/programs/gdaldem.rst:356 +msgid "The following option is available:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:360 +msgid "" +"Starting with GDAL 3.3, the Riley algorithm (see Riley, S.J., De Gloria, " +"S.D., Elliot, R. (1999): A Terrain Ruggedness that Quantifies Topographic" +" Heterogeneity. Intermountain Journal of Science, Vol.5, No.1-4, " +"pp.23-27) is available and the new default value. This algorithm uses the" +" square root of the sum of the square of the difference between a central" +" pixel and its surrounding cells. This is recommended for terrestrial use" +" cases." +msgstr "" + +#: ../../source/programs/gdaldem.rst:367 +msgid "" +"The Wilson (see Wilson et al 2007, Marine Geodesy 30:3-35) algorithm uses" +" the mean difference between a central pixel and its surrounding cells. " +"This is recommended for bathymetric use cases." +msgstr "" + +#: ../../source/programs/gdaldem.rst:372 +msgid "TPI" +msgstr "" + +#: ../../source/programs/gdaldem.rst:374 +msgid "" +"This command outputs a single-band raster with values computed from the " +"elevation. `TPI` stands for Topographic Position Index, which is defined " +"as the difference between a central pixel and the mean of its surrounding" +" cells (see Wilson et al 2007, Marine Geodesy 30:3-35)." +msgstr "" + +#: ../../source/programs/gdaldem.rst:381 ../../source/programs/gdaldem.rst:392 +msgid "There are no specific options." +msgstr "" + +#: ../../source/programs/gdaldem.rst:384 +msgid "roughness" +msgstr "" + +#: ../../source/programs/gdaldem.rst:386 +msgid "" +"This command outputs a single-band raster with values computed from the " +"elevation. Roughness is the largest inter-cell difference of a central " +"pixel and its surrounding cell, as defined in Wilson et al (2007, Marine " +"Geodesy 30:3-35)." +msgstr "" + +#: ../../source/programs/gdaldem.rst:397 +msgid "This utility is also callable from C with :cpp:func:`GDALDEMProcessing`." +msgstr "" + +#: ../../source/programs/gdaldem.rst:402 +msgid "Authors" +msgstr "" + +#: ../../source/programs/gdaldem.rst:404 +msgid "" +"Matthew Perry perrygeo@gmail.com, Even Rouault " +"even.rouault@spatialys.com, Howard Butler hobu.inc@gmail.com, Chris " +"Yesson chris.yesson@ioz.ac.uk" +msgstr "" + +#: ../../source/programs/gdaldem.rst:407 +msgid "" +"Derived from code by Michael Shapiro, Olga Waupotitsch, Marjorie Larson, " +"Jim Westervelt: U.S. Army CERL, 1993. GRASS 4.1 Reference Manual. U.S. " +"Army Corps of Engineers, Construction Engineering Research Laboratories, " +"Champaign, Illinois, 1-425." +msgstr "" + +#: ../../source/programs/gdaldem.rst:412 +#: ../../source/programs/gdaltindex.rst:341 +#: ../../source/programs/gdalwarp.rst:758 +msgid "See also" +msgstr "" + +#: ../../source/programs/gdaldem.rst:414 +msgid "Documentation of related GRASS utilities:" +msgstr "" + +#: ../../source/programs/gdaldem.rst:416 +msgid "https://grass.osgeo.org/grass79/manuals/r.slope.aspect.html" +msgstr "" + +#: ../../source/programs/gdaldem.rst:418 +msgid "https://grass.osgeo.org/grass79/manuals/r.relief.html" +msgstr "" + +#: ../../source/programs/gdaldem.rst:420 +msgid "https://grass.osgeo.org/grass79/manuals/r.colors.html" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:5 +msgid "gdalinfo" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:9 +msgid "Lists information about a raster dataset." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:29 +msgid "" +":program:`gdalinfo` program lists various information about a GDAL " +"supported raster dataset." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:32 +#: ../../source/programs/gdalmdiminfo.rst:32 +msgid "The following command line parameters can appear in any order" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:40 +msgid "" +"Display the output in json format. Since GDAL 3.6, this includes key-" +"value pairs useful for building a `STAC item " +"<https://github.com/radiantearth/stac-spec/blob/v1.0.0/item-spec/item-" +"spec.md>`_ , including statistics and histograms if ``-stats`` or " +"``-hist`` flags are passed, respectively." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:48 +msgid "" +"Force computation of the actual min/max values for each band in the " +"dataset." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:53 +#: ../../source/programs/gdalmdiminfo.rst:69 +msgid "" +"Read and display image statistics. Force computation if no statistics are" +" stored in an image." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:58 +msgid "" +"Read and display image statistics. Force computation if no statistics are" +" stored in an image. However, they may be computed based on overviews or " +"a subset of all tiles. Useful if you are in a hurry and don't want " +"precise stats." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:65 +msgid "Report histogram information for all bands." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:69 +msgid "" +"Suppress ground control points list printing. It may be useful for " +"datasets with huge amount of GCPs, such as L1B AVHRR or HDF4 MODIS which " +"contain thousands of them." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:75 ../../source/programs/ogrinfo.rst:175 +msgid "" +"Suppress metadata printing. Some datasets may contain a lot of metadata " +"strings." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:80 +msgid "Suppress printing of raster attribute table." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:84 +msgid "Suppress printing of color table." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:88 +msgid "Force computation of the checksum for each band in the dataset." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:92 ../../source/programs/ogrinfo.rst:180 +msgid "List all metadata domains available for the dataset." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:96 +msgid "adds metadata using:" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:98 +msgid "``domain`` Report metadata for the specified domain." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:100 +msgid "``all`` Report metadata for all domains." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:104 +msgid "Only display the first file of the file list." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:108 +msgid "WKT format used to display the SRS. Currently the supported values are:" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:111 ../../source/programs/ogrinfo.rst:216 +msgid "``WKT1``" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:113 +msgid "``WKT2`` (latest WKT version, currently *WKT2_2019*)" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:115 ../../source/programs/ogrinfo.rst:220 +msgid "``WKT2_2015``" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:117 +msgid "``WKT2_2018`` (deprecated)" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:119 +msgid "``WKT2_2019``" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:125 +msgid "" +"If the input dataset contains several subdatasets read and display a " +"subdataset with specified ``n`` number (starting from 1). This is an " +"alternative of giving the full subdataset name." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:131 +msgid "Report a PROJ.4 string corresponding to the file's coordinate system." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:135 +msgid "Dataset open option (format specific)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:140 +msgid "The gdalinfo will report all of the following (if known):" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:142 +msgid "The format driver used to access the file." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:143 +msgid "Raster size (in pixels and lines)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:144 +msgid "The coordinate system for the file (in OGC WKT)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:145 +msgid "" +"The geotransform associated with the file (rotational coefficients are " +"currently not reported)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:147 +msgid "" +"Corner coordinates in georeferenced, and if possible lat/long based on " +"the full geotransform (but not GCPs)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:149 +msgid "Ground control points." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:150 +msgid "File wide (including subdatasets) metadata." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:151 +msgid "Band data types." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:152 +msgid "Band color interpretations." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:153 +msgid "Band block size." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:154 +msgid "Band descriptions." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:155 +msgid "Band min/max values (internally known and possibly computed)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:156 +msgid "Band checksum (if computation asked)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:157 +msgid "Band NODATA value." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:158 +msgid "Band overview resolutions available." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:159 +msgid "Band unit type (i.e.. \"meters\" or \"feet\" for elevation bands)." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:160 +msgid "Band pseudo-color tables." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:165 +msgid "This utility is also callable from C with :cpp:func:`GDALInfo`." +msgstr "" + +#: ../../source/programs/gdalinfo.rst:201 +msgid "" +"For corner coordinates formatted as decimal degree instead of the above " +"degree, minute, second, inspect the ``wgs84Extent`` member of gdalinfo " +"-json:" +msgstr "" + +#: ../../source/programs/gdalinfo.rst:203 +msgid "Example of JSON output with ``gdalinfo -json byte.tif``" +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:5 +msgid "gdallocationinfo" +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:9 +msgid "Raster query tool" +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:29 +msgid "" +"The :program:`gdallocationinfo` utility provide a mechanism to query " +"information about a pixel given its location in one of a variety of " +"coordinate systems. Several reporting options are provided." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:39 +msgid "The output report will be XML formatted for convenient post processing." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:43 +msgid "" +"The only output is filenames production from the LocationInfo request " +"against the database (i.e. for identifying impacted file from VRT)." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:48 +msgid "" +"The only output is the pixel values of the selected pixel on each of the " +"selected bands. By default, the value of each band is output on a " +"separate line, unless :option:`-field_sep` is specified." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:54 +msgid "" +"Selects a band to query. Multiple bands can be listed. By default all " +"bands are queried." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:59 +msgid "" +"Query the (overview_level)th overview (overview_level=1 is the 1st " +"overview), instead of the base band. Note that the x,y location (if the " +"coordinate system is pixel/line) must still be given with respect to the " +"base band." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:65 +msgid "The coordinate system of the input x, y location." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:69 +msgid "Indicates input x,y points are in the georeferencing system of the image." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:73 +msgid "Indicates input x,y points are WGS84 long, lat." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:83 +msgid "" +"Set this flag to avoid extra non-numeric content at end of input lines to" +" be appended to the output lines in -valonly mode (requires " +":option:`-field_sep` to be also defined), or as a dedicated field in " +"default or :option:`-xml` modes." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:91 +msgid "" +"Enable Echo mode, where input coordinates are prepended to the output " +"lines in :option:`-valonly` mode." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:98 +msgid "" +"Defines the field separator, used in :option:`-valonly` mode, to separate" +" different values. It defaults to the new-line character, which means " +"that when querying a raster with several bands, the output will contain " +"one value per line, which may make it hard to recognize which value " +"belongs to which set of input x,y points when several ones are provided. " +"Defining the field separator is also needed" +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:107 +msgid "The source GDAL raster datasource name." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:111 +msgid "" +"X location of target pixel. By default the coordinate system is " +"pixel/line unless -l_srs, -wgs84 or -geoloc supplied." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:116 +msgid "" +"Y location of target pixel. By default the coordinate system is " +"pixel/line unless -l_srs, -wgs84 or -geoloc supplied." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:120 +msgid "" +"This utility is intended to provide a variety of information about a " +"pixel. Currently it reports:" +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:123 +msgid "The location of the pixel in pixel/line space." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:124 +msgid "" +"The result of a LocationInfo metadata query against the datasource. This " +"is implemented for VRT files which will report the file(s) used to " +"satisfy requests for that pixel, and by the :ref:`raster.mbtiles` driver." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:128 +msgid "The raster pixel value of that pixel for all or a subset of the bands." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:129 +msgid "The unscaled pixel value if a Scale and/or Offset apply to the band." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:131 +msgid "" +"The pixel selected is requested by x/y coordinate on the command line, or" +" read from stdin. More than one coordinate pair can be supplied when " +"reading coordinates from stdin. By default integer pixel/line coordinates" +" are expected. However with use of the :option:`-geoloc`, " +":option:`-wgs84`, or :option:`-l_srs` switches it is possible to specify " +"the location in other coordinate systems." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:137 +msgid "" +"The default report is in a human readable text format. It is possible to" +" instead request xml output with the -xml switch." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:140 +msgid "" +"For scripting purposes, the -valonly and -lifonly switches are provided " +"to restrict output to the actual pixel values, or the LocationInfo files " +"identified for the pixel." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:144 +msgid "" +"It is anticipated that additional reporting capabilities will be added to" +" gdallocationinfo in the future." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:150 +msgid "Simple example reporting on pixel (256,256) on the file utm.tif." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:160 +msgid "" +"Query a VRT file providing the location in WGS84, and getting the result " +"in xml." +msgstr "" + +#: ../../source/programs/gdallocationinfo.rst:174 +msgid "Reading location from stdin." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:5 +msgid "gdalmanage" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:9 +msgid "Identify, delete, rename and copy raster data files." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:25 +msgid "" +"The :program:`gdalmanage` program can perform various operations on " +"raster data files, depending on the chosen *mode*. This includes " +"identifying raster data types and deleting, renaming or copying the " +"files." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:31 +msgid "Mode of operation" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:33 +msgid "**identify** *<datasetname>*:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:34 +msgid "List data format of file(s)." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:35 +msgid "**copy** *<datasetname>* *<newdatasetname>*:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:36 +msgid "Create a copy of the raster file with a new name." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:37 +msgid "**rename** *<datasetname>* *<newdatasetname>*:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:38 +msgid "Change the name of the raster file." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:39 +msgid "**delete** *<datasetname>*:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:40 +msgid "Delete raster file(s)." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:44 +msgid "Recursively scan files/folders for raster files." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:48 +msgid "" +"Recursively scan folders for raster files, forcing recursion in folders " +"recognized as valid formats." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:52 +msgid "Report failures if file type is unidentified." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:56 +msgid "" +"Specify format of raster file if unknown by the application. Uses short " +"data format name (e.g. *GTiff*)." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:61 +msgid "" +"Raster file to operate on. With **identify** may be repeated for multiple" +" files." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:65 +msgid "" +"For copy and rename modes, you provide a *source* filename and a *target*" +" filename, just like copy and move commands in an operating system." +msgstr "" + +#: ../../source/programs/gdalmanage.rst:73 +msgid "Using identify mode" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:75 +msgid "" +"Report the data format of the raster file by using the *identify* mode " +"and specifying a data file name:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:84 +msgid "Recursive mode will scan subfolders and report the data format:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:101 +msgid "Using copy mode" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:103 +msgid "Copy the raster data:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:110 +msgid "Using rename mode" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:112 +msgid "Rename raster data:" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:119 +msgid "Using delete mode" +msgstr "" + +#: ../../source/programs/gdalmanage.rst:121 +msgid "Delete the raster data:" +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:5 +msgid "gdalmdiminfo" +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:11 +msgid "Reports structure and content of a multidimensional dataset." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:28 +msgid "" +":program:`gdalmdiminfo` program lists various information about a GDAL " +"supported multidimensional raster dataset as JSON output. It follows the " +"following `JSON schema " +"<https://github.com/OSGeo/gdal/blob/master/data/gdalmdiminfo_output.schema.json>`_" +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:40 +msgid "Most verbose output. Report attribute data types and array values." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:44 +msgid "Outputs on a single line without any indentation." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:48 +msgid "Name of the array used to restrict the output to the specified array." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:52 +msgid "" +"Number of values in each dimension that is used to limit the display of " +"array values. By default, unlimited. Only taken into account if used with" +" -detailed." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:58 +msgid "" +"Dataset open option (format specific). This option may be used several " +"times." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:63 +#: ../../source/programs/gdalmdimtranslate.rst:100 +msgid "" +"Option passed to :cpp:func:`GDALGroup::GetMDArrayNames` to filter " +"reported arrays. Such option is format specific. Consult driver " +"documentation. This option may be used several times." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:80 +msgid "This utility is also callable from C with :cpp:func:`GDALMultiDimInfo`." +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:85 +msgid "Display general structure1" +msgstr "" + +#: ../../source/programs/gdalmdiminfo.rst:194 +msgid "Display detailed information about a given array" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:5 +msgid "gdalmdimtranslate" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:11 +msgid "" +"Converts multidimensional data between different formats, and perform " +"subsetting." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:36 +msgid "" +":program:`gdalmdimtranslate` program converts multidimensional raster " +"between different formats, and/or can perform selective conversion of " +"specific arrays and groups, and/or subsetting operations." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:40 +msgid "The following command line parameters can appear in any order." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:50 +msgid "" +"Select the output format. This can be a format that supports " +"multidimensional output (such as :ref:`raster.netcdf`, " +":ref:`vrt_multidimensional`), or a \"classic\" 2D formats, if only one " +"single 2D array results of the other specified conversion operations. " +"When this option is not specified, the format is guessed when possible " +"from the extension of the destination filename." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:58 +msgid "" +"Many formats have one or more optional creation options that can be used " +"to control particulars about the file created." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:70 +msgid "" +"Array-level creation options may be passed by prefixing them with " +"``ARRAY:``. See :cpp:func:`GDALGroup::CopyFrom` for further details " +"regarding such options." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:75 +msgid "" +"Instead of converting the whole dataset, select one array, and possibly " +"perform operations on it. This option can be specified several times to " +"operate on different arrays." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:79 +msgid "" +"<array_spec> may be just an array name, potentially using a fully " +"qualified syntax (/group/subgroup/array_name). Or it can be a combination" +" of options with the syntax: " +"name={src_array_name}[,dstname={dst_array_name}][,resample=yes][,transpose=[{axis1},{axis2},...][,view={view_expr}]" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:84 +msgid "The following options are processed in that order:" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:86 +msgid "" +"``resample=yes`` asks for the array to run through " +":cpp:func:`GDALMDArray::GetResampled`." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:89 +msgid "" +"[{axis1},{axis2},...] is the argument of " +":cpp:func:`GDALMDArray::Transpose`." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:89 +msgid "For example, transpose=[1,0] switches the axis order of a 2D array." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:91 +msgid "" +"{view_expr} is the value of the *viewExpr* argument of " +":cpp:func:`GDALMDArray::GetView`" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:93 +msgid "" +"When specifying a view_expr that performs a slicing or subsetting on a " +"dimension, the equivalent operation will be applied to the corresponding " +"indexing variable." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:106 +msgid "" +"Instead of converting the whole dataset, select one group, and possibly " +"perform operations on it. This option can be specified several times to " +"operate on different groups. If only one group is specified, its content " +"will be copied directly to the target root group. If several ones are " +"specified, they are copied under the target root group" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:112 +msgid "" +"<group_spec> may be just a group name, potentially using a fully " +"qualified syntax (/group/subgroup/subsubgroup_name). Or it can be a " +"combination of options with the syntax: " +"name={src_group_name}[,dstname={dst_group_name}][,recursive=no]" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:119 +msgid "" +"Performs a subsetting (trimming or slicing) operation along a dimension, " +"provided that it is indexed by a 1D variable of numeric or string data " +"type, and whose values are monotically sorted. <subset_spec> follows " +"exactly the `OGC WCS 2.0 KVP encoding " +"<https://portal.opengeospatial.org/files/09-147r3>`__ for subsetting." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:125 +msgid "" +"That is dim_name(min_val,max_val) or dim_name(sliced_val) The first " +"syntax will subset the dimension dim_name to values in the " +"[min_val,max_val] range. The second syntax will slice the dimension " +"dim_name to value sliced_val (and this dimension will be removed from the" +" arrays that reference to it)" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:131 +msgid "Using -subset is incompatible of specifying a *view* option in -array." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:135 +msgid "" +"Applies a integral scale factor to one or several dimensions, that is " +"extract 1 value every N values (without resampling)." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:138 +msgid "" +"<scaleaxes_spec> follows exactly the syntax of the KVP encoding of the " +"SCALEAXES parameter of `OGC WCS 2.0 Scaling Extension " +"<https://portal.opengeospatial.org/files/12-039>`__, but limited to " +"integer scale factors." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:143 +msgid "That is <dim1_name>(<scale_factor>)[,<dim2_name>(<scale_factor>)]..." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:145 +msgid "Using -scaleaxes is incompatible of specifying a *view* option in -array." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:149 +msgid "" +"By default, some failures during the translation are tolerated, such as " +"not being able to write group attributes. When setting this option, such " +"failures will cause the process to fail." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:161 +msgid "The source dataset name." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:170 +msgid "" +"This utility is also callable from C with " +":cpp:func:`GDALMultiDimTranslate`." +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:175 +msgid "Convert a netCDF file to a multidimensional VRT file" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:181 +msgid "Extract a 2D slice of a time,Y,X array" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:187 +msgid "Subsample along X and Y axis" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:193 +msgid "" +"Reorder the values of a time,Y,X array along the Y axis from top-to-" +"bottom to bottom-to-top (or the reverse)" +msgstr "" + +#: ../../source/programs/gdalmdimtranslate.rst:200 +msgid "Transpose an array that has X,Y,time dimension order to time,Y,X" +msgstr "" + +#: ../../source/programs/gdalmove.rst:5 +msgid "gdalmove" +msgstr "" + +#: ../../source/programs/gdalmove.rst:9 +msgid "Transform georeferencing of raster file in place." +msgstr "" + +#: ../../source/programs/gdalmove.rst:25 +msgid "" +"The :program:`gdalmove` script transforms the bounds of a raster file " +"from one coordinate system to another, and then updates the coordinate " +"system and geotransform of the file. This is done without altering pixel " +"values at all. It is loosely similar to using gdalwarp to transform an " +"image but avoiding the resampling step in order to avoid image damage. It" +" is generally only suitable for transformations that are effectively " +"linear in the area of the file." +msgstr "" + +#: ../../source/programs/gdalmove.rst:32 +msgid "" +"If no error threshold value (:option:`-et`) is provided then the file is " +"not actually updated, but the errors that would be incurred are reported." +" If :option:`-et` is provided then the file is only modify if the " +"apparent error being introduced is less than the indicate threshold (in " +"pixels)." +msgstr "" + +#: ../../source/programs/gdalmove.rst:37 +msgid "" +"Currently the transformed geotransform is computed based on the " +"transformation of the top left, top right, and bottom left corners. A " +"reduced overall error could be produced using a least squares fit of at " +"least all four corner points." +msgstr "" + +#: ../../source/programs/gdalmove.rst:43 +msgid "" +"gdalmove is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/gdalmove.rst:49 +msgid "" +"Override the coordinate system of the file with the indicated coordinate " +"system definition. Optional. If not provided the source coordinate system" +" is read from the source file." +msgstr "" + +#: ../../source/programs/gdalmove.rst:55 +msgid "" +"Defines the target coordinate system. This coordinate system will be " +"written to the file after an update." +msgstr "" + +#: ../../source/programs/gdalmove.rst:60 +msgid "" +"The error threshold (in pixels) beyond which the file will not be " +"updated. If not provided no update will be applied to the file, but " +"errors will be reported." +msgstr "" + +#: ../../source/programs/gdalmove.rst:64 +msgid "<target_file>" +msgstr "" + +#: ../../source/programs/gdalmove.rst:66 +msgid "" +"The file to be operated on. To update this must be a file format that " +"supports in place updates of the geotransform and SRS." +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:5 +msgid "gdalsrsinfo" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:9 +msgid "Lists info about a given SRS in number of formats (WKT, PROJ.4, etc.)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:24 +msgid "" +"The :program:`gdalsrsinfo` utility reports information about a given SRS " +"from one of the following:" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:26 +msgid "" +"The filename of a dataset supported by GDAL/OGR which contains SRS " +"information" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:27 +msgid "" +"Any of the usual GDAL/OGR forms (complete WKT, PROJ.4, EPSG:n or a file " +"containing the SRS)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:36 +msgid "Print WKT on single line" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:40 +msgid "Validate SRS" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:44 +msgid "Search for EPSG number(s) corresponding to SRS" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:48 +msgid "Output types:" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:50 +msgid "``default``: proj4 and wkt (default option)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:51 +msgid "``all``: all options available" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:52 +msgid "``wkt_all``: all wkt options available" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:53 +msgid "``PROJJSON``: PROJJSON string (GDAL >= 3.1 and PROJ >= 6.2)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:54 +msgid "``proj4``: PROJ.4 string" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:55 +msgid "``wkt1``: OGC WKT format (full)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:56 +msgid "``wkt_simple``: OGC WKT 1 (simplified)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:57 +msgid "``wkt_noct``: OGC WKT 1 (without OGC CT params)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:58 +msgid "``wkt_esri``: ESRI WKT format" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:59 +msgid "``wkt``: Latest WKT version supported, currently wkt2_2019" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:60 +msgid "``wkt2``: Latest WKT2 version supported, currently wkt2_2019" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:61 +msgid "``wkt2_2015``: OGC WKT2:2015" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:62 +msgid "``wkt2_2019``: OGC WKT2:2019 (for GDAL < 3.6, use ``wkt2_2018``)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:63 +msgid "``mapinfo``: Mapinfo style CoordSys format" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:64 +msgid "``xml``: XML format (GML based)" +msgstr "" + +#: ../../source/programs/gdalsrsinfo.rst:68 +msgid "" +"may be the filename of a dataset supported by GDAL/OGR from which to " +"extract SRS information OR any of the usual GDAL/OGR forms (complete WKT," +" PROJ.4, EPSG:n or a file containing the SRS)" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:5 +msgid "gdaltindex" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:9 +msgid "Creates an OGR-supported dataset as a raster tileindex." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:36 +msgid "" +"This program creates an OGR-supported dataset with a record for each " +"input raster file, an attribute containing the filename, and a polygon " +"geometry outlining the raster. This output is suitable for use with " +"`MapServer <http://mapserver.org/>`__ as a raster tileindex, or as input " +"for the :ref:`GTI <raster.gti>` driver." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:49 +msgid "Overwrite the tile index if it already exists." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:55 +msgid "" +"Whether directories specified in <file_or_dir> should be explored " +"recursively." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:61 +msgid "" +"Pattern that the filenames contained in directories pointed by " +"<file_or_dir> should follow. '*' is a wildcard character that matches any" +" number of any characters including none. '?' is a wildcard character " +"that matches a single character. Comparisons are done in a case " +"insensitive way. Several filters may be specified." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:68 +msgid "For example :``-filename_filter \"*.tif\" -filename_filter \"*.tiff\"``" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:74 +msgid "" +"Minimum pixel size in term of geospatial extent per pixel (resolution) " +"that a raster should have to be selected. The pixel size is evaluated " +"after reprojection of its extent to the target SRS defined by " +":option:`-t_srs`." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:83 +msgid "" +"Maximum pixel size in term of geospatial extent per pixel (resolution) " +"that a raster should have to be selected. The pixel size is evaluated " +"after reprojection of its extent to the target SRS defined by " +":option:`-t_srs`." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:90 +msgid "" +"The OGR format of the output tile index file. Starting with GDAL 2.3, if " +"not specified, the format is guessed from the extension (previously was " +"ESRI Shapefile)." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:96 +msgid "" +"The output field name to hold the file path/location to the indexed " +"rasters. The default tile index field name is ``location``." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:101 +msgid "" +"The absolute path to the raster files is stored in the tile index file. " +"By default the raster filenames will be put in the file exactly as they " +"are specified on the command line." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:107 +msgid "" +"Only files with same projection as files already inserted in the " +"tileindex will be inserted (unless :option:`-t_srs` is specified). " +"Default does not check projection and accepts all inputs." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:113 +msgid "" +"Geometries of input files will be transformed to the desired target " +"coordinate reference system. Default creates simple rectangular polygons " +"in the same coordinate reference system as the input rasters." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:120 +msgid "" +"The name of the field to store the SRS of each tile. This field name can " +"be used as the value of the TILESRS keyword in MapServer" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:125 +msgid "" +"The format in which the SRS of each tile must be written. Types can be " +"``AUTO``, ``WKT``, ``EPSG``, ``PROJ``. This option should be used " +"together with :option:`-src_srs_format`." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:131 +msgid "Layer name to create/append to in the output tile index file." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:141 +msgid "" +"The name of the output file to create/append to. The default dataset will" +" be created if it doesn't already exist, otherwise it will append to the " +"existing dataset." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:147 +msgid "" +"The input GDAL raster files, can be multiple files separated by spaces. " +"Wildcards may also be used. Stores the file locations in the same style " +"as specified here, unless :option:`-write_absolute_path` option is also " +"used." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:151 +msgid "" +"Starting with GDAL 3.9, this can also be a directory name. " +":option:`-recursive` can also be used to recurse down to sub-directories." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:154 +msgid "" +"It is also possible to use the generic option ``--optfile filelist.txt`` " +"to specify a list of source files." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:159 +msgid "Options specific to use by the GDAL GTI driver" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:161 +msgid "" +"gdaltindex can be used to generate a tile index suitable for use by the " +":ref:`GTI <raster.gti>` driver. There are two possibilities:" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:164 +msgid "" +"either use directly a vector tile index generated by gdaltindex as the " +"input of the GTI driver" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:167 +msgid "" +"or generate a small XML .gti wrapper file, for easier use with non-file-" +"based formats such as databases, or for vector formats that do not " +"support setting layer metadata items." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:171 +msgid "" +"Formats that support layer metadata are for example GeoPackage (``-f " +"GPKG``), FlatGeoBuf (``-f FlatGeoBuf``) or PostGIS (``-f PG``)" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:174 +msgid "" +"Setting :option:`-tr` and :option:`-ot` is recommended to avoid the GTI " +"driver to have to deduce them by opening the first tile in the index. If " +"the tiles have nodata or mask band, :option:`-nodata` and " +":option:`-mask` should also be set." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:179 +msgid "" +"In a GTI context, the extent of all tiles referenced in the tile index " +"must be expressed in a single SRS. Consequently, if input tiles may have " +"different SRS, either :option:`-t_srs` or " +":option:`-skip_different_projection` should be specified." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:189 +msgid "" +"Filename of the XML Virtual Tile Index file to generate, that can be used" +" as an input for the GDAL GTI / Virtual Raster Tile Index driver. This " +"can be useful when writing the tile index in a vector format that does " +"not support writing layer metadata items." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:198 +msgid "Target resolution in SRS unit per pixel." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:200 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``RESX`` and ``RESY`` layer metadata items for formats " +"that support layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:208 +msgid "Target extent in SRS unit." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:210 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``MINX``, ``MINY``, ``MAXX`` and ``MAXY`` layer metadata" +" items for formats that support layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:218 +msgid "" +"Data type of the tiles of the tile index: ``Byte``, ``Int8``, ``UInt16``," +" ``Int16``, ``UInt32``, ``Int32``, ``UInt64``, ``Int64``, ``Float32``, " +"``Float64``, ``CInt16``, ``CInt32``, ``CFloat32`` or ``CFloat64``" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:222 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``DATA_TYPE`` layer metadata item for formats that " +"support layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:230 +msgid "Number of bands of the tiles of the tile index." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:232 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``BAND_COUNT`` layer metadata item for formats that " +"support layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:236 +msgid "" +"A mix of tiles with N and N+1 bands is allowed, provided that the color " +"interpretation of the (N+1)th band is alpha. The N+1 value must be " +"written as the band count in that situation." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:240 +msgid "" +"If :option:`-nodata` or :option:`-colorinterp` are specified and have " +"multiple values, the band count is also inferred from that number." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:247 +msgid "Nodata value of the tiles of the tile index." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:249 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``NODATA`` layer metadata item for formats that support " +"layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:257 +msgid "" +"Color interpretation of of the tiles of the tile index: ``red``, " +"``green``, ``blue``, ``alpha``, ``gray``, ``undefined``." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:260 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``COLOR_INTERPRETATION`` layer metadata item for formats" +" that support layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:268 +msgid "Whether tiles in the tile index have a mask band." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:270 +msgid "" +"Written in the XML Virtual Tile Index if :option:`-gti_filename` is " +"specified, or as ``MASK_BAND`` layer metadata item for formats that " +"support layer metadata." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:278 +msgid "" +"Write an arbitrary layer metadata item, for formats that support layer " +"metadata. This option may be repeated." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:282 +msgid "This option cannot be used together :option:`-gti_filename`" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:288 +msgid "" +"Fetch a metadata item from the raster tile and write it as a field in the" +" tile index." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:291 +msgid "" +"<gdal_md_name> should be the name of the raster metadata item. " +"``{PIXEL_SIZE}`` may be used as a special name to indicate the pixel " +"size." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:294 +msgid "<fld_name> should be the name of the field to create in the tile index." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:296 +msgid "" +"<fld_type> should be the name of the type to create. One of ``String``, " +"``Integer``, ``Integer64``, ``Real``, ``Date``, ``DateTime``" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:299 +msgid "This option may be repeated." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:301 +msgid "For example: ``-fetch_md TIFFTAG_DATETIME creation_date DateTime``" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:306 +msgid "" +"Produce a shapefile (``doq_index.shp``) with a record for every image " +"that the utility found in the ``doq`` folder. Each record holds " +"information that points to the location of the image and also a bounding " +"rectangle shape showing the bounds of the image:" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:315 +msgid "" +"Perform the same command as before, but now we create a GeoPackage " +"instead of a Shapefile." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:321 +msgid "" +"The :option:`-t_srs` option can also be used to transform all input " +"rasters into the same output projection:" +msgstr "" + +#: ../../source/programs/gdaltindex.rst:328 +msgid "" +"Make a tile index from files listed in a text file, with metadata " +"suitable for use by the GDAL GTI / Virtual Raster Tile Index driver." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:338 +msgid "This utility is also callable from C with :cpp:func:`GDALTileIndex`." +msgstr "" + +#: ../../source/programs/gdaltindex.rst:343 +msgid "" +":ref:`raster_common_options` for other command-line options, and in " +"particular the :ref:`--optfile <raster_common_options_optfile>` switch " +"that can be used to specify a list of input datasets." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:5 +msgid "gdaltransform" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:9 +msgid "Transforms coordinates" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:30 +msgid "" +"The gdaltransform utility reprojects a list of coordinates into any " +"supported projection,including GCP-based transformations." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:39 +msgid "" +"Set source spatial reference. The coordinate systems that can be passed " +"are anything supported by the OGRSpatialReference.SetFromUserInput() " +"call, which includes EPSG PCS and GCSes (i.e. EPSG:4296), PROJ.4 " +"declarations (as above), or the name of a .prj file containing well known" +" text." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:49 +#: ../../source/programs/gdalwarp.rst:129 ../../source/programs/ogr2ogr.rst:331 +msgid "" +"Assign a coordinate epoch, linked with the source SRS. Useful when the " +"source SRS is a dynamic CRS. Only taken into account if :option:`-s_srs` " +"is used." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:53 +#: ../../source/programs/gdaltransform.rst:72 +#: ../../source/programs/gdalwarp.rst:133 +#: ../../source/programs/gdalwarp.rst:154 ../../source/programs/ogr2ogr.rst:273 +#: ../../source/programs/ogr2ogr.rst:335 +msgid "" +"Before PROJ 9.4, :option:`-s_coord_epoch` and :option:`-t_coord_epoch` " +"were mutually exclusive, due to lack of support for transformations " +"between two dynamic CRS." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:58 +msgid "" +"set target spatial reference. The coordinate systems that can be passed " +"are anything supported by the OGRSpatialReference.SetFromUserInput() " +"call, which includes EPSG PCS and GCSes (i.e. EPSG:4296), PROJ.4 " +"declarations (as above), or the name of a .prj file containing well known" +" text." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:68 +msgid "" +"Assign a coordinate epoch, linked with the output SRS. Useful when the " +"output SRS is a dynamic CRS. Only taken into account if :option:`-t_srs` " +"is used." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:77 +msgid "" +"A PROJ string (single step operation or multiple step string starting " +"with +proj=pipeline), a WKT2 string describing a CoordinateOperation, or " +"a urn:ogc:def:coordinateOperation:EPSG::XXXX URN overriding the default " +"transformation from the source to the target CRS. It must take into " +"account the axis order of the source and target CRS." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:87 +msgid "" +"set a transformer option suitable to pass to " +":cpp:func:`GDALCreateGenImgProjTransformer2`." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:91 +#: ../../source/programs/gdalwarp.rst:200 +msgid "" +"order of polynomial used for warping (1 to 3). The default is to select a" +" polynomial order based on the number of GCPs." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:96 +#: ../../source/programs/gdalwarp.rst:205 ../../source/programs/ogr2ogr.rst:558 +msgid "Force use of thin plate spline transformer based on available GCPs." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:100 +#: ../../source/programs/gdalwarp.rst:209 +msgid "Force use of RPCs." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:104 +#: ../../source/programs/gdalwarp.rst:213 +msgid "Force use of Geolocation Arrays." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:108 +msgid "Inverse transformation: from destination to source." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:112 +msgid "" +"Provide a GCP to be used for transformation (generally three or more are " +"required). Pixel and line need not be integers." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:116 +msgid "Restrict output to \"x y\" instead of \"x y z\"" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:122 +msgid "" +"Set this flag to avoid extra non-numeric content at end of input lines to" +" be appended to the output lines." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:129 +msgid "" +"Enable Echo mode, where input coordinates are prepended to the output " +"lines." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:135 +msgid "" +"Defines the field separator, to separate different values. It defaults to" +" the space character." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:140 +msgid "" +"Raster dataset with source projection definition or GCPs. If not given, " +"source projection/GCPs are read from the command-line :option:`-s_srs` or" +" :option:`-gcp` parameters." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:144 +msgid "" +"Note that only the SRS and/or GCPs of this input file is taken into " +"account, and not its pixel content." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:148 +msgid "Raster dataset with destination projection definition." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:150 +msgid "" +"Coordinates are read as pairs, triples (for 3D,) or (since GDAL 3.0.0,) " +"quadruplets (for X,Y,Z,time) of numbers per line from standard input, " +"transformed, and written out to standard output in the same way. All " +"transformations offered by gdalwarp are handled, including gcp-based " +"ones." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:155 +msgid "" +"Starting with GDAL 3.9, additional non-numeric content (typically point " +"name) at the end of an input line will also be appended to the output " +"line, unless the :option:`-ignore_extra_input` is added." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:159 +msgid "" +"Note that input and output must always be in decimal form. There is " +"currently no support for DMS input or output." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:162 +msgid "" +"If an input image file is provided, input is in pixel/line coordinates on" +" that image. If an output file is provided, output is in pixel/line " +"coordinates on that image." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:170 +msgid "Reprojection Example" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:172 +msgid "Simple reprojection from one projected coordinate system to another:" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:179 +msgid "" +"Produces the following output in meters in the \"Belge 1972 / Belgian " +"Lambert 72\" projection:" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:187 +msgid "Image RPC Example" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:189 +msgid "" +"The following command requests an RPC based transformation using the RPC " +"model associated with the named file. Because the -i (inverse) flag is " +"used, the transformation is from output georeferenced (WGS84) coordinates" +" back to image coordinates." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:200 +msgid "Produces this output measured in pixels and lines on the image:" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:207 +msgid "X,Y,Z,time transform" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:209 +msgid "" +"15-term time-dependent Helmert coordinate transformation from ITRF2000 to" +" ITRF93 for a coordinate at epoch 2000.0" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:222 +msgid "" +"Produces this output measured in longitude degrees, latitude degrees and " +"ellipsoid height in meters:" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:229 +msgid "Ground control points" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:231 +msgid "" +"Task: find one address and assign another. We pick Salt Lake City, where " +"road names *are* their grid values. We first establish some ground " +"control points at road intersections. We'll use :ref:`--optfile " +"<raster_common_options_optfile>` for easy reuse of our GCPs." +msgstr "" + +#: ../../source/programs/gdaltransform.rst:243 +msgid "Where is the address \"370 S. 300 E.\"?" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:250 +msgid "" +"Nearby, a newly constructed building needs an address assigned. We use " +":option:`-i`:" +msgstr "" + +#: ../../source/programs/gdaltransform.rst:257 +msgid "(i.e., 143 E. 200 S. Or 144 if across the street.)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:5 +msgid "gdalwarp" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:9 +msgid "Image reprojection and warping utility" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:53 +msgid "" +"The :program:`gdalwarp` utility is an image mosaicing, reprojection and " +"warping utility. The program can reproject to any supported projection, " +"and can also apply GCPs stored with the image if the image is \"raw\" " +"with control information." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:68 +msgid "" +"Specify an input band number to warp (between 1 and the number of bands " +"of the source dataset)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:71 +msgid "" +"This option is used to warp a subset of the input bands. All input bands " +"are used when it is not specified." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:74 +msgid "" +"This option may be repeated multiple times to select several input bands." +" The order in which bands are specified will be the order in which they " +"appear in the output dataset (unless :option:`-dstband` is specified)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:78 +msgid "" +"The alpha band should not be specified in the list, as it will be " +"automatically retrieved (unless :option:`-nosrcalpha` is specified)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:81 +msgid "" +"The following invocation will warp an input datasets with bands ordered " +"as Blue, Green, Red, NearInfraRed in an output dataset with bands ordered" +" as Red, Green, Blue." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:94 +msgid "" +"Specify the output band number in which to warp. In practice, this option" +" is only useful when updating an existing dataset, e.g to warp one band " +"at at time." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:106 +msgid "" +"If :option:`-srcband` is specified, there must be as many occurrences of " +":option:`-dstband` as there are of :option:`-srcband`." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:109 +msgid "" +"The output alpha band should not be specified, as it will be " +"automatically created if the input dataset has an alpha band, or if " +":option:`-dstalpha` is specified." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:113 +msgid "" +"If :option:`-dstband` is not specified, then ``-dstband 1 -dstband 2 ... " +"-dstband N`` is assumed where N is the number of input bands (specified " +"explicitly either with :option:`-srcband` or implicitly)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:120 +msgid "" +"Set source spatial reference. If not specified the SRS found in the input" +" dataset will be used." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:150 +#: ../../source/programs/options/srs_def_gdalwarp.rst:1 +msgid "" +"The coordinate reference systems that can be passed are anything " +"supported by the OGRSpatialReference.SetFromUserInput() call, which " +"includes EPSG Projected, Geographic or Compound CRS (i.e. EPSG:4296), a " +"well known text (WKT) CRS definition, PROJ.4 declarations, or the name of" +" a .prj file containing a WKT CRS definition." +msgstr "" + +#: ../../source/programs/options/srs_def_gdalwarp.rst:6 +msgid "" +"Starting with GDAL 2.2, if the SRS has an explicit vertical datum that " +"points to a PROJ.4 geoidgrids, and the input dataset is a single band " +"dataset, a vertical correction will be applied to the values of the " +"dataset." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:138 +msgid "Set target spatial reference." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:140 +msgid "" +"A source SRS must be available for reprojection to occur. The source SRS " +"will be by default the one found in the input dataset when it is " +"available, or as overridden by the user with :option:`-s_srs`" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:150 +msgid "" +"Assign a coordinate epoch, linked with the target SRS. Useful when the " +"target SRS is a dynamic CRS. Only taken into account if :option:`-t_srs` " +"is used." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:159 ../../source/programs/ogr2ogr.rst:340 +msgid "" +"A PROJ string (single step operation or multiple step string starting " +"with +proj=pipeline), a WKT2 string describing a CoordinateOperation, or " +"a urn:ogc:def:coordinateOperation:EPSG::XXXX URN overriding the default " +"transformation from the source to the target CRS." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:164 ../../source/programs/ogr2ogr.rst:345 +msgid "" +"It must take into account the axis order of the source and target CRS, " +"that is typically include a ``step proj=axisswap order=2,1`` at the " +"beginning of the pipeline if the source CRS has northing/easting axis " +"order, and/or at the end of the pipeline if the target CRS has " +"northing/easting axis order." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:169 +msgid "" +"When creating a new output file, using :option:`-t_srs` is still " +"necessary to have the target CRS written in the metadata of the output " +"file, but the parameters of the CoordinateOperation will override those " +"of the standard transformation." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:178 +msgid "" +"Set a transformer option suitable to pass to " +":cpp:func:`GDALCreateGenImgProjTransformer2`. See " +":cpp:func:`GDALCreateRPCTransformerV2()` for RPC specific options." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:183 +msgid "" +"Force the use of vertical shift. This option is generally not necessary, " +"except when using an explicit coordinate transformation (:option:`-ct`), " +"and not specifying an explicit source and target SRS." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:191 +msgid "" +"Disable the use of vertical shift when one of the source or target SRS " +"has an explicit vertical datum, and the input dataset is a single band " +"dataset." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:194 +msgid "this option was named ``-novshiftgrid`` in GDAL 2.2 to 3.3." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:217 +msgid "" +"Error threshold for transformation approximation (in pixel units - " +"defaults to 0.125, unless, starting with GDAL 2.1, the RPC_DEM " +"transformer option is specified, in which case, an exact transformer, " +"i.e. err_threshold=0, will be used)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:224 +msgid "" +"Refines the GCPs by automatically eliminating outliers. Outliers will be " +"eliminated until minimum_gcps are left or when no outliers can be " +"detected. The tolerance is passed to adjust when a GCP will be " +"eliminated. Not that GCP refinement only works with polynomial " +"interpolation. The tolerance is in pixel units if no projection is " +"available, otherwise it is in SRS units. If minimum_gcps is not provided," +" the minimum GCPs according to the polynomial model is used." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:233 +msgid "" +"Set georeferenced extents of output file to be created (in target SRS by " +"default, or in the SRS specified with :option:`-te_srs`)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:238 +msgid "" +"Specifies the SRS in which to interpret the coordinates given with -te. " +"The <srs_def> may be any of the usual GDAL/OGR forms, complete WKT, " +"PROJ.4, EPSG:n or a file containing the WKT. This must not be confused " +"with -t_srs which is the target SRS of the output dataset. " +":option:`-te_srs` is a convenience e.g. when knowing the output " +"coordinates in a geodetic long/lat SRS, but still wanting a result in a " +"projected coordinate system." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:248 +msgid "Set output file resolution (in target georeferenced units)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:250 +msgid "" +"If not specified (or not deduced from -te and -ts), gdalwarp will, in the" +" general case, generate an output raster with xres=yres." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:253 +msgid "" +"Starting with GDAL 3.7, if neither :option:`-tr` nor :option:`-ts` are " +"specified, that no reprojection is involved (including taking into " +"account geolocation arrays or RPC), the resolution of the source file(s) " +"will be preserved (in previous version, an output raster with xres=yres " +"was always generated). It is possible to ask square pixels to still be " +"generated, by specifying ``square`` as the value for :option:`-tr`." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:262 +msgid "" +"(target aligned pixels) align the coordinates of the extent of the output" +" file to the values of the :option:`-tr`, such that the aligned extent " +"includes the minimum extent (edges lines/columns that are detected as " +"blank, before actual warping, will be removed starting with GDAL 3.8). " +"Alignment means that xmin / resx, ymin / resy, xmax / resx and ymax / " +"resy are integer values." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:271 +msgid "" +"Set output file size in pixels and lines. If width or height is set to 0," +" the other dimension will be guessed from the computed resolution. Note " +"that :option:`-ts` cannot be used with :option:`-tr`" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:277 +msgid "" +"To specify which overview level of source files must be used. The default" +" choice, AUTO, will select the overview level whose resolution is the " +"closest to the target resolution. Specify an integer value (0-based, i.e." +" 0=1st overview level) to select a particular level. Specify AUTO-n where" +" n is an integer greater or equal to 1, to select an overview level below" +" the AUTO one. Or specify NONE to force the base resolution to be used " +"(can be useful if overviews have been generated with a low quality " +"resampling method, and the warping is done using a higher quality " +"resampling method)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:288 +msgid "" +"Set a warp option. The :cpp:member:`GDALWarpOptions::papszWarpOptions` " +"docs show all options. Multiple :option:`-wo` options may be listed." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:295 +msgid "" +"Working pixel data type. The data type of pixels in the source image and " +"destination image buffers." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:300 +msgid "Resampling method to use. Available methods are:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:302 +msgid "" +"``near``: nearest neighbour resampling (default, fastest algorithm, worst" +" interpolation quality)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:304 +msgid "``bilinear``: bilinear resampling." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:306 +msgid "``cubic``: cubic resampling." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:308 +msgid "``cubicspline``: cubic spline resampling." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:310 +msgid "``lanczos``: Lanczos windowed sinc resampling." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:312 +msgid "" +"``average``: average resampling, computes the weighted average of all " +"non-NODATA contributing pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:314 +msgid "" +"``rms`` root mean square / quadratic mean of all non-NODATA contributing " +"pixels (GDAL >= 3.3)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:316 +msgid "" +"``mode``: mode resampling, selects the value which appears most often of " +"all the sampled points. In the case of ties, the first value identified " +"as the mode will be selected." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:318 +msgid "" +"``max``: maximum resampling, selects the maximum value from all non-" +"NODATA contributing pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:320 +msgid "" +"``min``: minimum resampling, selects the minimum value from all non-" +"NODATA contributing pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:322 +msgid "" +"``med``: median resampling, selects the median value of all non-NODATA " +"contributing pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:324 +msgid "" +"``q1``: first quartile resampling, selects the first quartile value of " +"all non-NODATA contributing pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:326 +msgid "" +"``q3``: third quartile resampling, selects the third quartile value of " +"all non-NODATA contributing pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:328 +msgid "" +"``sum``: compute the weighted sum of all non-NODATA contributing pixels " +"(since GDAL 3.1)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:332 +msgid "" +"When downsampling is performed (use of :option:`-tr` or :option:`-ts`), " +"existing overviews (either internal/implicit or external ones) on the " +"source image will be used by default by selecting the closest overview to" +" the desired output resolution. The resampling method used to create " +"those overviews is generally not the one you specify through the " +":option:`-r` option. Some formats, like JPEG2000, can contain significant" +" outliers due to wavelet compression works. It might thus be useful in " +"those situations to use the :option:`-ovr` ``NONE`` option to prevent " +"existing overviews to be used." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:344 +msgid "" +"Set nodata masking values for input bands (different values can be " +"supplied for each band). If more than one value is supplied all values " +"should be quoted to keep them together as a single operating system " +"argument. Masked values will not be used in interpolation (details given " +"in :ref:`gdalwarp_nodata`)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:349 +msgid "" +"Use a value of ``None`` to ignore intrinsic nodata settings on the source" +" dataset." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:351 +msgid "" +"When this option is set to a non-``None`` value, it causes the " +"``UNIFIED_SRC_NODATA`` warping option (see " +":cpp:member:`GDALWarpOptions::papszWarpOptions`) to be set to ``YES``, if" +" it is not explicitly set." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:355 +msgid "" +"If ``-srcnodata`` is not explicitly set, but the source dataset has " +"nodata values, they will be taken into account, with " +"``UNIFIED_SRC_NODATA`` at ``PARTIAL`` by default." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:361 +msgid "" +"Set nodata values for output bands (different values can be supplied for " +"each band). If more than one value is supplied all values should be " +"quoted to keep them together as a single operating system argument. New " +"files will be initialized to this value and if possible the nodata value " +"will be recorded in the output file. Use a value of ``None`` to ensure " +"that nodata is not defined. If this argument is not used then nodata " +"values will be copied from the source dataset." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:371 +msgid "" +"Force the last band of a source image to be considered as a source alpha " +"band." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:376 +msgid "" +"Prevent the alpha band of a source image to be considered as such (it " +"will be warped as a regular band)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:383 +msgid "Create an output alpha band to identify nodata (unset/transparent) pixels." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:387 +msgid "" +"Set the amount of memory that the warp API is allowed to use for caching." +" The value is interpreted as being in megabytes if the value is less than" +" 10000. For values >=10000, this is interpreted as bytes." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:392 +msgid "" +"The warper will total up the memory required to hold the input and output" +" image arrays and any auxiliary masking arrays and if they are larger " +"than the \"warp memory\" allowed it will subdivide the chunk into smaller" +" chunks and try again." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:397 +msgid "" +"If the -wm value is very small there is some extra overhead in doing many" +" small chunks so setting it larger is better but it is a matter of " +"diminishing returns." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:403 +msgid "" +"Use multithreaded warping implementation. Two threads will be used to " +"process chunks of image and perform input/output operation " +"simultaneously. Note that computation is not multithreaded itself. To do " +"that, you can use the :option:`-wo` NUM_THREADS=val/ALL_CPUS option, " +"which can be combined with :option:`-multi`" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:411 +msgid "Be quiet." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:421 +msgid "" +"Enable use of a blend cutline from the name of a vector dataset. Starting" +" with GDAL 3.9, a WKT geometry string starting with POLYGON or " +"MULTIPOLYGON can also be specified." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:429 +msgid "Sets or overrides the SRS of the cutline." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:433 +msgid "Select the named layer from the cutline datasource." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:437 +msgid "Restrict desired cutline features based on attribute query." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:441 +msgid "" +"Select cutline features using an SQL query instead of from a layer with " +":option:`-cl`." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:445 +msgid "Set a blend distance to use to blend over cutlines (in pixels)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:449 +msgid "Crop the extent of the target dataset to the extent of the cutline." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:453 +msgid "" +"Overwrite the target dataset if it already exists. Overwriting must be " +"understood here as deleting and recreating the file from scratch. Note " +"that if this option is *not* specified and the output file already " +"exists, it will be updated in place." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:460 +msgid "" +"Do not copy metadata. Without this option, dataset and band metadata (as " +"well as some band information) will be copied from the first source " +"dataset. Items that differ between source datasets will be set to * (see " +":option:`-cvmd` option)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:466 +msgid "" +"Value to set metadata items that conflict between source datasets " +"(default is \"*\"). Use \"\" to remove conflicting items." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:471 +msgid "" +"Set the color interpretation of the bands of the target dataset from the " +"source dataset." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:480 +msgid "Output dataset open option (format specific)" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:486 +msgid "The source file name(s)." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:493 +msgid "" +"Mosaicing into an existing output file is supported if the output file " +"already exists. The spatial extent of the existing file will not be " +"modified to accommodate new data, so you may have to remove it in that " +"case, or use the -overwrite option." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:498 +msgid "" +"Polygon cutlines may be used as a mask to restrict the area of the " +"destination file that may be updated, including blending. If the OGR " +"layer containing the cutline features has no explicit SRS, the cutline " +"features must be in the SRS of the destination file. When writing to a " +"not yet existing target dataset, its extent will be the one of the " +"original raster unless -te or -crop_to_cutline are specified." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:505 +msgid "" +"Starting with GDAL 3.1, it is possible to use as output format a driver " +"that only supports the CreateCopy operation. This may internally imply " +"creation of a temporary file." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:512 +msgid "Nodata / source validity mask handling" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:514 +msgid "" +"Invalid values in source pixels, either identified through a nodata value" +" metadata set on the source band, a mask band, an alpha band or the use " +"of :option:`-srcnodata` will not be used in interpolation. The details of" +" how it is taken into account depends on the resampling kernel:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:519 +msgid "" +"for nearest resampling, for each target pixel, the coordinate of its " +"center is projected back to source coordinates and the source pixel " +"containing that coordinate is identified. If this source pixel is " +"invalid, the target pixel is considered as nodata." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:524 +msgid "" +"for bilinear, cubic, cubicspline and lanczos, for each target pixel, the " +"coordinate of its center is projected back to source coordinates and a " +"corresponding source pixel is identified. If this source pixel is " +"invalid, the target pixel is considered as nodata. Given that those " +"resampling kernels have a non-null kernel radius, this source pixel is " +"just one among other several source pixels, and it might be possible that" +" there are invalid values in those other contributing source pixels. The " +"weights used to take into account those invalid values will be set to " +"zero to ignore them." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:534 +msgid "" +"for the other resampling methods, source pixels contributing to the " +"target pixel are ignored if invalid. Only the valid ones are taken into " +"account. If there are none, the target pixel is considered as nodata." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:538 +msgid "" +"If using :option:`-srcnodata` for multiple images with different invalid " +"values, you need to either (a) pre-process them to have the same to-be-" +"ignored value, or (b) set the nodata flag for each file. Use (b) if you " +"need to preserve the original values for some reason, for example:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:559 +msgid "Approximate transformation" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:561 +msgid "" +"By default :program:`gdalwarp` uses a linear approximator for the " +"transformations with a permitted error of 0.125 pixels. The approximator " +"basically transforms three points on a scanline: the start, end and " +"middle. Then it compares the linear approximation of the center based on " +"the end points to the real thing and checks the error. If the error is " +"less than the error threshold then the remaining points are approximated " +"(in two chunks utilizing the center point). If the error exceeds the " +"threshold, the scanline is split into two sections, and the approximator " +"is recursively applied to each section until the error is less than the " +"threshold or all points have been exactly computed." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:572 +msgid "" +"The error threshold (in pixels) can be controlled with the gdalwarp " +":option:`-et` switch. If you want to compare a true pixel-by-pixel " +"reprojection use :option:`-et 0` which disables this approximator " +"entirely." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:577 +msgid "Vertical transformation" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:579 +msgid "" +"While gdalwarp can essentially perform coordinate transformations in the " +"2D space, it can perform as well vertical transformations. This is " +"automatically enabled when the 2 following conditions are met:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:583 +msgid "" +"at least one of the source or target CRS has an explicit vertical CRS (as" +" part of a compound CRS) or is a 3D (generally geographic) CRS," +msgstr "" + +#: ../../source/programs/gdalwarp.rst:585 +msgid "and the raster has a single band." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:587 +msgid "" +"This mode can also be forced by using the :option:`-vshift` (this is " +"essentially useful when the CRS involved are not explicitly 3D, but a " +"transformation pipeline is specified with :option:`-ct`), or disabled " +"with :option:`-novshift`." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:592 +msgid "" +"When a vertical transformation is involved, typically a shift value read " +"in a geoid grid will be applied. This may require such grid(s) to be " +"installed, or PROJ networking capabilities to be enabled. Consult `PROJ " +"<https://proj.org>`__ documentation for more details. In addition to a " +"shift, the raster values may be multiplied by a factor to take into " +"account vertical unit changes. In priority, the value returned by " +":cpp:func:`GDALRasterBand::GetUnitType` is used. The following values are" +" currently recognized: ``m``, ``metre``, ``metre``, ``ft``, ``foot``, " +"``US survey foot``. If there is no defined unit type at the band level, " +"the vertical unit of the source CRS is used. The vertical unit of the " +"target CRS is also used to determine that conversion factor. The " +"conversion factor may be overridden by setting the " +"``MULT_FACTOR_VERTICAL_SHIFT`` warping option with :option:`-wo`. For " +"example ``-wo MULT_FACTOR_VERTICAL_SHIFT=1`` to disable any vertical unit" +" change." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:607 +msgid "Memory usage" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:609 +msgid "" +"Adding RAM will almost certainly increase the speed of " +":program:`gdalwarp`. That's not at all the same as saying that it is " +"worth it, or that the speed increase will be significant. Disks are the " +"slowest part of the process. By default :program:`gdalwarp` won't take " +"much advantage of RAM. Using the flag :option:`-wm 500` will operate on " +"500MB chunks at a time which is better than the default. The warp memory " +"specified by :option:`-wm` is shared among all threads, so it is " +"especially beneficial to increase this value when running " +":program:`gdalwarp` with :option:`-wo NUM_THREADS` (or its equivalent " +":config:`GDAL_NUM_THREADS`) greater than 1." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:619 +msgid "" +"Increasing the I/O block cache size may also help. This can be done by " +"setting the :config:`GDAL_CACHEMAX` configuration like:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:626 +msgid "" +"This uses 500MB of RAM for read/write caching, and 500MB of RAM for " +"working buffers during the warp. Beyond that it is doubtful more memory " +"will make a substantial difference." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:630 +msgid "" +"Check CPU usage while :program:`gdalwarp` is running. If it is " +"substantially less than 100% then you know things are IO bound. Otherwise" +" they are CPU bound. The ``--debug`` option may also provide useful " +"information. For instance, after running the following:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:639 +msgid "a message like the following will be output:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:645 +msgid "" +"In this case it is saying that band 1 of :file:`utm.tif` has 32 blocks, " +"but that 224 block reads were done, implying that lots of data was having" +" to be re-read, presumably because of a limited IO cache. You will also " +"see messages like:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:655 +msgid "" +"The Src/Dst windows show you the \"chunk size\" being used. In this case " +"my whole image which is very small. If you find things are being broken " +"into a lot of chunks increasing :option:`-wm` may help somewhat." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:659 +msgid "" +"But far more important than memory are ensuring you are going through an " +"optimized path in the warper. If you ever see it reporting " +"``GDALWarpKernel()::GWKGeneralCase()`` you know things will be relatively" +" slow. Basically, the fastest situations are nearest neighbour resampling" +" on 8bit data without nodata or alpha masking in effect." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:667 +msgid "Compressed output" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:669 +msgid "" +"In some cases, the output of :program:`gdalwarp` may be much larger than " +"the original, even if the same compression algorithm is used. By default," +" :program:`gdalwarp` operates on chunks that are not necessarily aligned " +"with the boundaries of the blocks/tiles/strips of the output format, so " +"this might cause repeated compression/decompression of partial blocks, " +"leading to lost space in the output format." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:676 +msgid "" +"The situation can be improved by using the ``OPTIMIZE_SIZE`` warping " +"option (:option:`-wo OPTIMIZE_SIZE=YES`), but note that depending on the " +"source and target projections, it might also significantly slow down the " +"warping process." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:680 +msgid "" +"Another possibility is to use :program:`gdalwarp` without compression and" +" then follow up with :program:`gdal_translate` with compression:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:688 +msgid "" +"Alternatively, you can use a VRT file as the output format of " +":program:`gdalwarp`. The VRT file is just an XML file that will be " +"created immediately. The :program:`gdal_translate` operations will be of " +"course a bit slower as it will do the real warping operation." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:702 +msgid "Basic transformation:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:709 +msgid "" +"For instance, an eight bit spot scene stored in GeoTIFF with control " +"points mapping the corners to lat/long could be warped to a UTM " +"projection with a command like this:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:717 +msgid "" +"For instance, the second channel of an ASTER image stored in HDF with " +"control points mapping the corners to lat/long could be warped to a UTM " +"projection with a command like this:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:728 +msgid "" +"To apply a cutline on a un-georeferenced image and clip from pixel " +"(220,60) to pixel (1160,690):" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:735 +msgid "where cutline.csv content is like:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:742 +msgid "" +"To transform a DEM from geoid elevations (using EGM96) to WGS84 " +"ellipsoidal heights:" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:754 +msgid "This utility is also callable from C with :cpp:func:`GDALWarp`." +msgstr "" + +#: ../../source/programs/gdalwarp.rst:762 +msgid "" +"`Wiki page discussing options and behaviours of gdalwarp " +"<https://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp>`_" +msgstr "" + +#: ../../source/programs/gdalwarp.rst:766 +msgid "" +"Wiki page discussing options and behaviours of gdalwarp: " +"https://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp" +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:5 +msgid "gnmanalyse" +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:9 +msgid "Analyses networks" +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:29 +msgid "" +"The :program:`gnmanalyse` program provides analysing capabilities of " +"geographical networks in GDAL. The results of calculations are return in " +"an OGRLayer format or as a console text output if such layer is " +"undefined. All calculations are made considering the blocking state of " +"features." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:37 +msgid "" +"Calculates the best path between two points using Dijkstra algorithm from" +" start_gfid point to end_gfid point." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:41 +msgid "" +"Calculates K shortest paths between two points using Yen's algorithm " +"(which internally uses Dijkstra algorithm for single path calculating) " +"from start_gfid point to end_gfid point." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:45 +msgid "" +"Calculates the \"resource distribution\". The connected components search" +" is performed using breadth-first search and starting from that features " +"which are marked by rules as 'EMITTERS'." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:49 +msgid "" +"The name and path of the dataset to save the layer with resulting paths. " +"Not need to be existed dataset." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:53 +msgid "Define this to set the format of newly created dataset." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:57 +msgid "" +"The name of the resulting layer. If the layer exist already - it will be " +"rewritten." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:61 +#: ../../source/programs/gnmmanage.rst:119 +msgid "The network to work with (path and name)." +msgstr "" + +#: ../../source/programs/gnmanalyse.rst:73 +msgid "Algorithm option (format specific)" +msgstr "" + +#: ../../source/programs/gnmmanage.rst:5 +msgid "gnmmanage" +msgstr "" + +#: ../../source/programs/gnmmanage.rst:9 +msgid "Manages networks" +msgstr "" + +#: ../../source/programs/gnmmanage.rst:33 +msgid "" +"The :program:`gnmmanage` program can perform various managing operations " +"on geographical networks in GDAL. In addition to creating and deleting " +"networks this includes capabilities of managing network's features, " +"topology and rules." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:41 +msgid "" +"Different information about network: system and class layers, network " +"metadata, network spatial reference." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:45 +msgid "Create network." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:49 +msgid "Output file format name." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:53 +msgid "Spatial reference input." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:57 +msgid "Network creation option set as pair name=value." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:61 +msgid "Import layer with dataset name to copy." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:65 +msgid "Layer name in dataset. If unset, 0 layer is copied." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:69 +msgid "" +"Make a topological connection, where the gfid_src and gfid_tgt are " +"vertices and gfid_con is edge (gfid_con can be -1, so the system edge " +"will be inserted)." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:71 +msgid "Manually assign the following values:" +msgstr "" + +#: ../../source/programs/gnmmanage.rst:75 +msgid "Cost / weight" +msgstr "" + +#: ../../source/programs/gnmmanage.rst:79 +msgid "Inverse cost" +msgstr "" + +#: ../../source/programs/gnmmanage.rst:83 +msgid "Direction of the edge." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:87 +msgid "Removes the connection from the graph." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:91 +msgid "Creates a rule in the network by the given rule_str string." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:95 +msgid "" +"Create topology automatically with the given double tolerance and layer " +"names. In no layer name provided all layers of network will be used." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:99 +msgid "Delete network." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:103 +msgid "Change blocking state of network edges or vertices." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:107 +msgid "" +"Block feature before the main operation. Blocking features are saved in " +"the special layer." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:111 +msgid "Unblock feature before the main operation." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:115 +msgid "Unblock all blocked features before the main operation." +msgstr "" + +#: ../../source/programs/gnmmanage.rst:123 +msgid "The network layer name." +msgstr "" + +#: ../../source/programs/index.rst:23 ../../source/programs/index.rst:122 +msgid "Common options" +msgstr "" + +#: ../../source/programs/index.rst:5 +msgid "Programs" +msgstr "" + +#: ../../source/programs/index.rst:8 +msgid "General" +msgstr "" + +#: ../../source/programs/index.rst:18 +msgid ":ref:`argument_syntax`" +msgstr "" + +#: ../../source/programs/index.rst:21 +msgid "Raster programs" +msgstr "" + +#: ../../source/programs/index.rst:67 +msgid ":ref:`Common options <raster_common_options>`" +msgstr "" + +#: ../../source/programs/index.rst:68 +msgid "" +":ref:`gdal-config`: Determines various information about a GDAL " +"installation." +msgstr "" + +#: ../../source/programs/index.rst:69 +msgid "" +":ref:`gdal2tiles`: Generates directory with TMS tiles, KMLs and simple " +"web viewers." +msgstr "" + +#: ../../source/programs/index.rst:70 +msgid ":ref:`gdal2xyz`: Translates a raster file into xyz format." +msgstr "" + +#: ../../source/programs/index.rst:71 +msgid ":ref:`gdal_calc`: Command line raster calculator with numpy syntax." +msgstr "" + +#: ../../source/programs/index.rst:72 +msgid "" +":ref:`gdal_contour`: Builds vector contour lines from a raster elevation " +"model." +msgstr "" + +#: ../../source/programs/index.rst:73 +msgid ":ref:`gdal_create`: Create a raster file (without source dataset)." +msgstr "" + +#: ../../source/programs/index.rst:74 +msgid "" +":ref:`gdal_edit`: Edit in place various information of an existing GDAL " +"dataset." +msgstr "" + +#: ../../source/programs/index.rst:75 +msgid ":ref:`gdal_fillnodata`: Fill raster regions by interpolation from edges." +msgstr "" + +#: ../../source/programs/index.rst:76 +msgid ":ref:`gdal_footprint`: Compute footprint of a raster." +msgstr "" + +#: ../../source/programs/index.rst:77 +msgid ":ref:`gdal_grid`: Creates regular grid from the scattered data." +msgstr "" + +#: ../../source/programs/index.rst:78 +msgid ":ref:`gdal_merge`: Mosaics a set of images." +msgstr "" + +#: ../../source/programs/index.rst:79 +msgid ":ref:`gdal_pansharpen`: Perform a pansharpen operation." +msgstr "" + +#: ../../source/programs/index.rst:80 +msgid ":ref:`gdal_polygonize`: Produces a polygon feature layer from a raster." +msgstr "" + +#: ../../source/programs/index.rst:81 +msgid ":ref:`gdal_proximity`: Produces a raster proximity map." +msgstr "" + +#: ../../source/programs/index.rst:82 +msgid ":ref:`gdal_rasterize`: Burns vector geometries into a raster." +msgstr "" + +#: ../../source/programs/index.rst:83 +msgid "" +":ref:`gdal_retile`: Retiles a set of tiles and/or build tiled pyramid " +"levels." +msgstr "" + +#: ../../source/programs/index.rst:84 +msgid ":ref:`gdal_sieve`: Removes small raster polygons." +msgstr "" + +#: ../../source/programs/index.rst:85 +msgid ":ref:`gdal_translate`: Converts raster data between different formats." +msgstr "" + +#: ../../source/programs/index.rst:86 +msgid ":ref:`gdal_viewshed`: Compute a visibility mask for a raster." +msgstr "" + +#: ../../source/programs/index.rst:87 +msgid ":ref:`gdaladdo`: Builds or rebuilds overview images." +msgstr "" + +#: ../../source/programs/index.rst:88 +msgid "" +":ref:`gdalattachpct`: Attach a color table to a raster file from an input" +" file." +msgstr "" + +#: ../../source/programs/index.rst:89 +msgid ":ref:`gdalbuildvrt`: Builds a VRT from a list of datasets." +msgstr "" + +#: ../../source/programs/index.rst:90 +msgid ":ref:`gdalcompare`: Compare two images." +msgstr "" + +#: ../../source/programs/index.rst:91 +msgid ":ref:`gdaldem`: Tools to analyze and visualize DEMs." +msgstr "" + +#: ../../source/programs/index.rst:92 +msgid ":ref:`gdalinfo`: Lists information about a raster dataset." +msgstr "" + +#: ../../source/programs/index.rst:93 +msgid ":ref:`gdallocationinfo`: Raster query tool" +msgstr "" + +#: ../../source/programs/index.rst:94 +msgid ":ref:`gdalmanage`: Identify, delete, rename and copy raster data files." +msgstr "" + +#: ../../source/programs/index.rst:95 +msgid ":ref:`gdalmove`: Transform georeferencing of raster file in place." +msgstr "" + +#: ../../source/programs/index.rst:96 +msgid "" +":ref:`gdalsrsinfo`: Lists info about a given SRS in number of formats " +"(WKT, PROJ.4, etc.)" +msgstr "" + +#: ../../source/programs/index.rst:97 +msgid ":ref:`gdaltindex`: Builds an OGR-supported dataset as a raster tileindex." +msgstr "" + +#: ../../source/programs/index.rst:98 +msgid ":ref:`gdaltransform`: Transforms coordinates." +msgstr "" + +#: ../../source/programs/index.rst:99 +msgid ":ref:`gdalwarp`: Image reprojection and warping utility." +msgstr "" + +#: ../../source/programs/index.rst:100 +msgid ":ref:`nearblack`: Convert nearly black/white borders to black." +msgstr "" + +#: ../../source/programs/index.rst:101 +msgid ":ref:`pct2rgb`: Convert an 8bit paletted image to 24bit RGB." +msgstr "" + +#: ../../source/programs/index.rst:102 +msgid ":ref:`rgb2pct`: Convert a 24bit RGB image to 8bit paletted." +msgstr "" + +#: ../../source/programs/index.rst:105 +msgid "Multidimensional Raster programs" +msgstr "" + +#: ../../source/programs/index.rst:116 +msgid "" +":ref:`gdalmdiminfo`: Reports structure and content of a multidimensional " +"dataset." +msgstr "" + +#: ../../source/programs/index.rst:117 +msgid "" +":ref:`gdalmdimtranslate`: Converts multidimensional data between " +"different formats, and perform subsetting." +msgstr "" + +#: ../../source/programs/index.rst:120 +msgid "Vector programs" +msgstr "" + +#: ../../source/programs/index.rst:136 +msgid ":ref:`Common options <vector_common_options>`" +msgstr "" + +#: ../../source/programs/index.rst:137 +msgid ":ref:`ogrinfo`: Lists information about an OGR-supported data source." +msgstr "" + +#: ../../source/programs/index.rst:138 +msgid ":ref:`ogr2ogr`: Converts simple features data between file formats." +msgstr "" + +#: ../../source/programs/index.rst:139 +msgid ":ref:`ogrtindex`: Creates a tileindex." +msgstr "" + +#: ../../source/programs/index.rst:140 +msgid "" +":ref:`ogrlineref`: Create linear reference and provide some calculations " +"using it." +msgstr "" + +#: ../../source/programs/index.rst:141 +msgid ":ref:`ogrmerge`: Merge several vector datasets into a single one." +msgstr "" + +#: ../../source/programs/index.rst:142 +msgid "" +":ref:`ogr_layer_algebra`: Performs various Vector layer algebraic " +"operations." +msgstr "" + +#: ../../source/programs/index.rst:145 +msgid "Geographic network programs" +msgstr "" + +#: ../../source/programs/index.rst:156 +msgid ":ref:`gnmmanage`: Manages networks" +msgstr "" + +#: ../../source/programs/index.rst:157 +msgid ":ref:`gnmanalyse`: Analyses networks" +msgstr "" + +#: ../../source/programs/index.rst:160 +msgid "Other utilities" +msgstr "" + +#: ../../source/programs/index.rst:170 +msgid ":ref:`sozip`: Generate a seek-optimized ZIP (SOZip) file" +msgstr "" + +#: ../../source/programs/nearblack.rst:5 +msgid "nearblack" +msgstr "" + +#: ../../source/programs/nearblack.rst:9 +msgid "Convert nearly black/white borders to black." +msgstr "" + +#: ../../source/programs/nearblack.rst:27 +msgid "" +"This utility will scan an image and try to set all pixels that are nearly" +" or exactly black, white or one or more custom colors around the collar " +"to black or white. This is often used to \"fix up\" lossy compressed air " +"photos so that color pixels can be treated as transparent when mosaicing." +" The output format must use lossless compression if either alpha band or " +"mask band is not set." +msgstr "" + +#: ../../source/programs/nearblack.rst:39 +msgid "The name of the output file to be created." +msgstr "" + +#: ../../source/programs/nearblack.rst:43 +msgid "" +"Select the output format. Starting with GDAL 2.3, if not specified, the " +"format is guessed from the extension (previously was ERDAS Imagine .img)." +" Use the short format name (GTiff for GeoTIFF for example)." +msgstr "" + +#: ../../source/programs/nearblack.rst:50 +msgid "" +"Passes a creation option to the output format driver. Multiple " +":option:`-co` options may be listed. See :ref:`raster_drivers` format " +"specific documentation for legal creation options for each format." +msgstr "" + +#: ../../source/programs/nearblack.rst:54 +msgid "Only valid when creating a new file" +msgstr "" + +#: ../../source/programs/nearblack.rst:58 +msgid "Search for nearly white (255) pixels instead of nearly black pixels." +msgstr "" + +#: ../../source/programs/nearblack.rst:62 +msgid "" +"Search for pixels near the specified color. May be specified multiple " +"times. When -color is specified, the pixels that are considered as the " +"collar are set to 0." +msgstr "" + +#: ../../source/programs/nearblack.rst:67 +msgid "" +"Select how far from black, white or custom colors the pixel values can be" +" and still considered near black, white or custom color. Defaults to 15." +msgstr "" + +#: ../../source/programs/nearblack.rst:72 +msgid "" +"number of consecutive non-black pixels that can be encountered before the" +" giving up search inwards. Defaults to 2." +msgstr "" + +#: ../../source/programs/nearblack.rst:77 +msgid "" +"Adds an alpha band if the output file is specified and the input file has" +" 3 bands, or sets the alpha band of the output file if it is specified " +"and the input file has 4 bands, or sets the alpha band of the input file " +"if it has 4 bands and no output file is specified. The alpha band is set " +"to 0 in the image collar and to 255 elsewhere." +msgstr "" + +#: ../../source/programs/nearblack.rst:84 +msgid "" +"Adds a mask band to the output file, or adds a mask band to the input " +"file if it does not already have one and no output file is specified. The" +" mask band is set to 0 in the image collar and to 255 elsewhere." +msgstr "" + +#: ../../source/programs/nearblack.rst:92 +msgid "Selects the algorithm to apply." +msgstr "" + +#: ../../source/programs/nearblack.rst:94 +msgid "" +"``twopasses`` uses a top-to-bottom pass followed by a bottom-to-top pass." +" This is the only algorithm implemented before GDAL 3.8. It may miss with" +" concave areas. The algorithm processes the image one scanline at a time." +" A scan \"in\" is done from either end setting pixels to black or white " +"until at least \"non_black_pixels\" pixels that are more than \"dist\" " +"gray levels away from black, white or custom colors have been encountered" +" at which point the scan stops. The nearly black, white or custom color " +"pixels are set to black or white. The algorithm also scans from top to " +"bottom and from bottom to top to identify indentations in the top or " +"bottom." +msgstr "" + +#: ../../source/programs/nearblack.rst:104 +msgid "" +"``floodfill`` (added in GDAL 3.8) uses the `Flood Fill " +"<https://en.wikipedia.org/wiki/Flood_fill#Span_filling>`_ algorithm and " +"will work with concave areas. It requires creating a temporary dataset " +"and is slower than ``twopasses``. When a non-zero value for :option:`-nb`" +" is used, ``twopasses`` is actually called as an initial step of " +"``floodfill``." +msgstr "" + +#: ../../source/programs/nearblack.rst:115 +msgid "" +"The input file. Any GDAL supported format, any number of bands, normally" +" 8bit Byte bands." +msgstr "" + +#: ../../source/programs/nearblack.rst:119 +msgid "The processing is all done in 8bit (Bytes)." +msgstr "" + +#: ../../source/programs/nearblack.rst:121 +msgid "" +"If the output file is omitted, the processed results will be written back" +" to the input file - which must support update." +msgstr "" + +#: ../../source/programs/nearblack.rst:127 +msgid "This utility is also callable from C with :cpp:func:`GDALNearblack`." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:5 +msgid "ogr2ogr" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:9 +msgid "Converts simple features data between file formats." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:70 +msgid "" +":program:`ogr2ogr` can be used to convert simple features data between " +"file formats. It can also perform various operations during the process, " +"such as spatial or attribute selection, reducing the set of attributes, " +"setting the output coordinate system or even reprojecting the features " +"during translation." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:83 +msgid "" +"Output file format name, e.g. ``ESRI Shapefile``, ``MapInfo File``, " +"``PostgreSQL``. Starting with GDAL 2.3, if not specified, the format is " +"guessed from the extension (previously was ESRI Shapefile)." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:89 +msgid "" +"Append to existing layer instead of creating new. This option also " +"enables :option:`-update`." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:96 +msgid "" +"Variant of :option:`-append` where the " +":cpp:func:`OGRLayer::UpsertFeature` operation is used to insert or update" +" features instead of appending with :cpp:func:`OGRLayer::CreateFeature`." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:100 +msgid "" +"This is currently implemented only in a few drivers: :ref:`vector.gpkg` " +"and :ref:`vector.mongodbv3`." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:103 +msgid "" +"The upsert operation uses the FID of the input feature, when it is set " +"and is a \"significant\" (that is the FID column name is not the empty " +"string), as the key to update existing features. It is crucial to make " +"sure that the FID in the source and target layers are consistent." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:108 +msgid "" +"For the GPKG driver, it is also possible to upsert features whose FID is " +"unset or non-significant (:option:`-unsetFid` can be used to ignore the " +"FID from the source feature), when there is a UNIQUE column that is not " +"the integer primary key." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:115 +msgid "Delete the output layer and recreate it empty" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:119 +msgid "" +"Open existing output datasource in update mode rather than trying to " +"create a new one" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:124 +msgid "Comma-delimited list of fields from input layer to copy to the new layer." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:126 +msgid "" +"Starting with GDAL 3.9, field names with spaces, commas or double-quote " +"should be surrounded with a starting and ending double-quote character, " +"and double-quote characters in a field name should be escaped with " +"backslash." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:130 +msgid "" +"Depending on the shell used, this might require further quoting. For " +"example, to select ``regular_field``, ``a_field_with space, and comma`` " +"and ``a field with \" double quote`` with a Unix shell:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:138 +msgid "" +"A field is only selected once, even if mentioned several times in the " +"list and if the input layer has duplicate field names." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:141 +msgid "Geometry fields can also be specified in the list." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:143 +msgid "" +"All fields are selected when -select is not specified. Specifying the " +"empty string can be used to disable selecting any attribute field, and " +"only keep geometries." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:147 +msgid "" +"Note this setting cannot be used together with ``-append``. To control " +"the selection of fields when appending to a layer, use ``-fieldmap`` or " +"``-sql``." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:152 ../../source/programs/ogrmerge.rst:153 +msgid "" +"Display progress on terminal. Only works if input layers have the \"fast " +"feature count\" capability." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:157 +msgid "" +"SQL statement to execute. The resulting table/layer will be saved to the " +"output. Starting with GDAL 2.1, the ``@filename`` syntax can be used to " +"indicate that the content is in the pointed filename." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:163 +msgid "" +"SQL dialect. In some cases can be used to use the (unoptimized) " +":ref:`ogr_sql_dialect` instead of the native SQL of an RDBMS by passing " +"the ``OGRSQL`` dialect value. The :ref:`sql_sqlite_dialect` dialect can " +"be chosen with the ``SQLITE`` and ``INDIRECT_SQLITE`` dialect values, and" +" this can be used with any datasource." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:170 +msgid "" +"Attribute query (like SQL WHERE). Starting with GDAL 2.1, the " +"``@filename`` syntax can be used to indicate that the content is in the " +"pointed filename." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:175 ../../source/programs/ogrmerge.rst:158 +msgid "Continue after a failure, skipping the failed feature." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:179 +msgid "" +"spatial query extents, in the SRS of the source layer(s) (or the one " +"specified with ``-spat_srs``). Only features whose geometry intersects " +"the extents will be selected. The geometries will not be clipped unless " +"``-clipsrc`` is specified." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:186 +msgid "Override spatial filter SRS." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:190 +msgid "Name of the geometry field on which the spatial filter operates on." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:202 +msgid "Assign an alternate name to the new layer" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:206 +msgid "" +"Define the geometry type for the created layer. One of ``NONE``, " +"``GEOMETRY``, ``POINT``, ``LINESTRING``, ``POLYGON``, " +"``GEOMETRYCOLLECTION``, ``MULTIPOINT``, ``MULTIPOLYGON``, " +"``MULTILINESTRING``, ``CIRCULARSTRING``, ``COMPOUNDCURVE``, " +"``CURVEPOLYGON``, ``MULTICURVE``, and ``MULTISURFACE`` non-linear " +"geometry types. Add ``Z``, ``M``, or ``ZM`` to the type name to specify " +"coordinates with elevation, measure, or elevation and measure. " +"``PROMOTE_TO_MULTI`` can be used to automatically promote layers that mix" +" polygon or multipolygons to multipolygons, and layers that mix " +"linestrings or multilinestrings to multilinestrings. Can be useful when " +"converting shapefiles to PostGIS and other target drivers that implement " +"strict checks for geometry types. ``CONVERT_TO_LINEAR`` can be used to to" +" convert non-linear geometry types into linear geometry types by " +"approximating them, and ``CONVERT_TO_CURVE`` to promote a non-linear type" +" to its generalized curve type (``POLYGON`` to ``CURVEPOLYGON``, " +"``MULTIPOLYGON`` to ``MULTISURFACE``, ``LINESTRING`` to " +"``COMPOUNDCURVE``, ``MULTILINESTRING`` to ``MULTICURVE``). Starting with " +"version 2.1 the type can be defined as measured (\"25D\" remains as an " +"alias for single \"Z\"). Some forced geometry conversions may result in " +"invalid geometries, for example when forcing conversion of multi-part " +"multipolygons with ``-nlt POLYGON``, the resulting polygon will break the" +" Simple Features rules." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:228 +msgid "" +"Starting with GDAL 3.0.5, ``-nlt CONVERT_TO_LINEAR`` and ``-nlt " +"PROMOTE_TO_MULTI`` can be used simultaneously." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:233 +msgid "" +"Force the coordinate dimension to val (valid values are ``XY``, ``XYZ``, " +"``XYM``, and ``XYZM`` - for backwards compatibility ``2`` is an alias for" +" ``XY`` and ``3`` is an alias for ``XYZ``). This affects both the layer " +"geometry type, and feature geometries. The value can be set to " +"``layer_dim`` to instruct feature geometries to be promoted to the " +"coordinate dimension declared by the layer. Support for M was added in " +"GDAL 2.1." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:242 +msgid "" +"Assign an output SRS, but without reprojecting (use :option:`-t_srs` to " +"reproject)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:251 +msgid "" +"Assign a coordinate epoch, linked with the output SRS. Useful when the " +"output SRS is a dynamic CRS. Only taken into account if :option:`-a_srs` " +"is used." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:257 +msgid "Reproject/transform to this SRS on output, and assign it as output SRS." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:259 +msgid "" +"A source SRS must be available for reprojection to occur. The source SRS " +"will be by default the one found in the source layer when it is " +"available, or as overridden by the user with :option:`-s_srs`" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:269 +msgid "" +"Assign a coordinate epoch, linked with the output SRS. Useful when the " +"output SRS is a dynamic CRS. Only taken into account if :option:`-t_srs` " +"is used. It is also mutually exclusive with :option:`-a_coord_epoch`." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:278 +msgid "" +"Override source SRS. If not specified the SRS found in the input layer " +"will be used. This option has only an effect if used together with " +":option:`-t_srs` to reproject." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:288 +msgid "" +"Set/override the geometry X/Y coordinate resolution. If only a numeric " +"value is specified, it is assumed to be expressed in the units of the " +"target SRS. The m, mm or deg suffixes can be specified to indicate that " +"the value must be interpreted as being in meter, millimeter or degree." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:293 +msgid "" +"When specifying this option, the :cpp:func:`OGRGeometry::SetPrecision` " +"method is run on geometries (that are not curves) before passing them to " +"the output driver, to avoid generating invalid geometries due to the " +"potentially reduced precision (unless the " +":config:`OGR_APPLY_GEOM_SET_PRECISION` configuration option is set to " +"``NO``)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:299 +msgid "" +"If neither this option nor :option:`-unsetCoordPrecision` are specified, " +"the coordinate resolution of the source layer, if available, is used." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:306 +msgid "" +"Set/override the geometry Z coordinate resolution. If only a numeric " +"value is specified, it is assumed to be expressed in the units of the " +"target SRS. The m or mm suffixes can be specified to indicate that the " +"value must be interpreted as being in meter or millimeter. If neither " +"this option nor :option:`-unsetCoordPrecision` are specified, the " +"coordinate resolution of the source layer, if available, is used." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:317 +msgid "" +"Set/override the geometry M coordinate resolution. If neither this option" +" nor :option:`-unsetCoordPrecision` are specified, the coordinate " +"resolution of the source layer, if available, is used." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:325 +msgid "" +"Prevent the geometry coordinate resolution from being set on target " +"layer(s)." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:354 +msgid "" +"Use the FID of the source features instead of letting the output driver " +"automatically assign a new one (for formats that require a FID). If not " +"in append mode, this behavior is the default if the output driver has a " +"FID layer creation option, in which case the name of the source FID " +"column will be used and source feature IDs will be attempted to be " +"preserved. This behavior can be disabled by setting ``-unsetFid``. This " +"option is not compatible with ``-explodecollections``." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:364 +msgid "" +"If provided, only the feature with the specified feature id will be " +"processed. Operates exclusive of the spatial or attribute queries. Note:" +" if you want to select several features based on their feature id, you " +"can also use the fact the 'fid' is a special field recognized by OGR SQL." +" So, `-where \"fid in (1,3,5)\"` would select features 1, 3 and 5." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:372 ../../source/programs/ogrinfo.rst:95 +msgid "Limit the number of features per layer." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:376 +msgid "Input dataset open option (format specific)." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:380 +msgid "" +"Destination dataset open option (format specific), only valid in -update " +"mode." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:384 +msgid "" +"Group n features per transaction (default 100 000). Increase the value " +"for better performance when writing into DBMS drivers that have " +"transaction support. ``n`` can be set to unlimited to load the data into " +"a single transaction." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:391 +msgid "" +"Force the use of a dataset level transaction (for drivers that support " +"such mechanism), especially for drivers such as FileGDB that only support" +" dataset level transaction in emulation mode." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:397 +msgid "Clip geometries (before potential reprojection) to one of the following:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:399 +msgid "the specified bounding box (expressed in source SRS)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:400 +msgid "a WKT geometry (POLYGON or MULTIPOLYGON expressed in source SRS)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:401 ../../source/programs/ogr2ogr.rst:425 +msgid "one or more geometries selected from a datasource" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:402 +msgid "the spatial extent of the -spat option if you use the spat_extent keyword." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:404 +msgid "" +"When specifying a datasource, you will generally want to use -clipsrc in " +"combination of the -clipsrclayer, -clipsrcwhere or -clipsrcsql options." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:409 +msgid "" +"Select desired geometries from the source clip datasource using an SQL " +"query." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:417 +msgid "" +"Restrict desired geometries from the source clip layer based on an " +"attribute query." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:421 +msgid "Clip geometries (after potential reprojection) to one of the following:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:423 +msgid "the specified bounding box (expressed in destination SRS)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:424 +msgid "a WKT geometry (POLYGON or MULTIPOLYGON expressed in destination SRS)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:427 +msgid "" +"When specifying a datasource, you will generally want to use -clipdst in " +"combination with the -clipdstlayer, -clipdstwhere or -clipdstsql options." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:432 +msgid "" +"Select desired geometries from the destination clip datasource using an " +"SQL query." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:436 +msgid "Select the named layer from the destination clip datasource." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:440 +msgid "" +"Restrict desired geometries from the destination clip layer based on an " +"attribute query." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:444 +msgid "Split geometries crossing the dateline meridian (long. = +/- 180deg)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:448 +msgid "" +"Offset from dateline in degrees (default long. = +/- 10deg, geometries " +"within 170deg to -170deg will be split)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:453 +msgid "" +"Distance tolerance for simplification. Note: the algorithm used preserves" +" topology per feature, in particular for polygon geometries, but not for " +"a whole layer." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:457 +msgid "" +"The specified value of this option is the tolerance used to merge " +"consecutive points of the output geometry using the " +":cpp:func:`OGRGeometry::Simplify` method The unit of the distance is in " +"georeferenced units of the source vector dataset. This option is applied " +"before the reprojection implied by :option:`-t_srs`" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:466 +msgid "" +"The specified value of this option is the maximum distance between two " +"consecutive points of the output geometry before intermediate points are " +"added. The unit of the distance is georeferenced units of the source " +"raster. This option is applied before the reprojection implied by " +":option:`-t_srs`" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:473 +msgid "" +"Run the :cpp:func:`OGRGeometry::MakeValid` operation, followed by " +":cpp:func:`OGRGeometryFactory::removeLowerDimensionSubGeoms`, on " +"geometries to ensure they are valid regarding the rules of the Simple " +"Features specification." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:481 +msgid "" +"Converts any field of the specified type to a field of type string in the" +" destination layer. Valid types are : ``Integer``, ``Integer64``, " +"``Real``, ``String``, ``Date``, ``Time``, ``DateTime``, ``Binary``, " +"``IntegerList``, ``Integer64List``, ``RealList``, ``StringList``. Special" +" value ``All`` can be used to convert all fields to strings. This is an " +"alternate way to using the CAST operator of OGR SQL, that may avoid " +"typing a long SQL query. Note that this does not influence the field " +"types used by the source driver, and is only an afterwards conversion. " +"Also note that this option is without effects on fields whose presence " +"and type is hard-coded in the output driver (e.g KML, GPX)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:493 +msgid "" +"Converts any field of the specified type to another type. Valid types are" +" : ``Integer``, ``Integer64``, ``Real``, ``String``, ``Date``, ``Time``, " +"``DateTime``, ``Binary``, ``IntegerList``, ``Integer64List``, " +"``RealList``, ``StringList``. Types can also include subtype between " +"parenthesis, such as ``Integer(Boolean)``, ``Real(Float32)``, ... Special" +" value ``All`` can be used to convert all fields to another type. This is" +" an alternate way to using the CAST operator of OGR SQL, that may avoid " +"typing a long SQL query. This is a generalization of -fieldTypeToString. " +"Note that this does not influence the field types used by the source " +"driver, and is only an afterwards conversion. Also note that this option " +"is without effects on fields whose presence and type is hard-coded in the" +" output driver (e.g KML, GPX)" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:510 +msgid "" +"Converts date time values from the timezone specified in the source value" +" to the target timezone expressed with :option:`-dateTimeTo`. Datetime " +"whose timezone is unknown or localtime are not modified." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:514 +msgid "HH must be in the [0,14] range and MM=00, 15, 30 or 45." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:518 +msgid "Set field width and precision to 0." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:522 +msgid "" +"Split fields of type StringList, RealList or IntegerList into as many " +"fields of type String, Real or Integer as necessary." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:527 +msgid "" +"To be combined with ``-splitlistfields`` to limit the number of subfields" +" created for each split field." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:532 +msgid "" +"Produce one feature for each geometry in any kind of geometry collection " +"in the source file, applied after any ``-sql`` option. This options is " +"not compatible with ``-preserve_fid`` but ``-sql \"SELECT fid AS " +"original_fid, * FROM ...\"`` can be used to store the original FID if " +"needed." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:539 +msgid "Uses the specified field to fill the Z coordinate of geometries." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:543 +msgid "" +"Use the indicated ground control point to compute a coordinate " +"transformation. The transformation method can be selected by specifying " +"the :option:`-order` or :option:`-tps` options. Note that unlike raster " +"tools such as gdal_edit or gdal_translate, GCPs are not added to the " +"output dataset. This option may be provided multiple times to provide a " +"set of GCPs (at least 2 GCPs are needed)." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:553 +msgid "" +"Order of polynomial used for warping (1 to 3). The default is to select a" +" polynomial order based on the number of GCPs." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:562 +msgid "" +"Specifies the list of field indexes to be copied from the source to the " +"destination. The (n)th value specified in the list is the index of the " +"field in the target layer definition in which the n(th) field of the " +"source layer must be copied. Index count starts at zero. To omit a field," +" specify a value of -1. There must be exactly as many values in the list " +"as the count of the fields in the source layer. We can use the 'identity'" +" setting to specify that the fields should be transferred by using the " +"same order. This setting should be used along with the ``-append`` " +"setting." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:573 +msgid "" +"This is a specialized version of ``-append``. Contrary to ``-append``, " +"``-addfields`` has the effect of adding, to existing target layers, the " +"new fields found in source layers. This option is useful when merging " +"files that have non-strictly identical structures. This might not work " +"for output formats that don't support adding fields to existing non-empty" +" layers. Note that if you plan to use -addfields, you may need to combine" +" it with -forceNullable, including for the initial import." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:583 +msgid "" +"Do field name matching between source and existing target layer in a more" +" relaxed way if the target driver has an implementation for it." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:588 +msgid "" +"Do not propagate not-nullable constraints to target layer if they exist " +"in source layer." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:593 +msgid "" +"Do not propagate default field values to target layer if they exist in " +"source layer." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:598 +msgid "" +"Can be specified to prevent the name of the source FID column and source " +"feature IDs from being re-used for the target layer. This option can for " +"example be useful if selecting source features with a ORDER BY clause." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:606 +msgid "Treat empty string values as null." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:612 +msgid "" +"When this is specified, any selected field that is linked to a coded " +"field domain will be accompanied by an additional field " +"(``{dstfield}_resolved``), that will contain the description of the coded" +" value." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:618 +msgid "" +"To disable copying of metadata from source dataset and layers into target" +" dataset and layers, when supported by output driver." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:623 +msgid "" +"Passes a metadata key and value to set on the output dataset, when " +"supported by output driver." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:628 +msgid "" +"To disable copying of native data, i.e. details of source format not " +"captured by OGR abstraction, that are otherwise preserved by some drivers" +" (like GeoJSON) when converting to same format." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:636 +msgid "Output dataset name." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:640 +msgid "Source dataset name." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:644 +msgid "" +"One or more source layer names to copy to the output dataset. If no layer" +" names are passed, then all source layers are copied." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:649 +msgid "Performance Hints" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:651 +msgid "" +"When writing into transactional DBMS (SQLite/PostgreSQL,MySQL, etc...), " +"it might be beneficial to increase the number of INSERT statements " +"executed between BEGIN TRANSACTION and COMMIT TRANSACTION statements. " +"This number is specified with the -gt option. For example, for SQLite, " +"explicitly defining -gt 65536 ensures optimal performance while " +"populating some table containing many hundreds of thousands or millions " +"of rows. However, note that -skipfailures overrides -gt and sets the size" +" of transactions to 1." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:659 +msgid "" +"For PostgreSQL, the :config:`PG_USE_COPY` config option can be set to YES" +" for a significant insertion performance boost. See the PG driver " +"documentation page." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:662 +msgid "" +"More generally, consult the documentation page of the input and output " +"drivers for performance hints." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:666 +msgid "Known issues" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:668 +msgid "" +"Starting with GDAL 3.8, ogr2ogr uses internally an Arrow array based API " +"(cf :ref:`rfc-86`) for some source formats (in particular GeoPackage or " +"FlatGeoBuf), and for the most basic types of operations, to improve " +"performance. This substantial change in the ogr2ogr internal logic has " +"required a number of fixes throughout the GDAL 3.8.x bugfix releases to " +"fully stabilize it, and we believe most issues are resolved with GDAL " +"3.9. If you hit errors not met with earlier GDAL versions, you may " +"specify ``--config OGR2OGR_USE_ARROW_API NO`` on the ogr2ogr command line" +" to opt for the classic algorithm using an iterative feature based " +"approach. If that flag is needed with GDAL >= 3.9, please file an issue " +"on the `GDAL issue tracker <https://github.com/OSGeo/gdal/issues>`__." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:683 +msgid "This utility is also callable from C with :cpp:func:`GDALVectorTranslate`." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:690 +msgid "Basic conversion from Shapefile to GeoPackage:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:696 +msgid "" +"Change the coordinate reference system from ``EPSG:4326`` to " +"``EPSG:3857``:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:702 +msgid "Example appending to an existing layer:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:708 +msgid "Clip input layer with a bounding box (<xmin> <ymin> <xmax> <ymax>):" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:714 +msgid "Filter Features by a ``-where`` clause:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:722 +msgid "More examples are given in the individual format pages." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:725 +msgid "Advanced examples" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:727 +msgid "" +"Reprojecting from ETRS_1989_LAEA_52N_10E to EPSG:4326 and clipping to a " +"bounding box:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:733 +msgid "" +"Using the ``-fieldmap`` setting. The first field of the source layer is " +"used to fill the third field (index 2 = third field) of the target layer," +" the second field of the source layer is ignored, the third field of the " +"source layer used to fill the fifth field of the target layer." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:742 +msgid "Outputting geometries with the CSV driver." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:744 +msgid "" +"By default, this driver does not preserve geometries on layer creation by" +" default. An explicit layer creation option is needed:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:751 +msgid "Extracting only geometries." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:753 +msgid "" +"There are different situations, depending if the input layer has a named " +"geometry column, or not. First check, with ogrinfo if there is a reported" +" geometry column." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:761 +msgid "" +"In that situation where the input format is a FileGeodatabase, it is " +"called SHAPE and can thus be referenced directly in a SELECT statement." +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:769 +msgid "" +"For a shapefile with a unnamed geometry column, ``_ogr_geometry_`` can be" +" used as a special name to designate the implicit geometry column, when " +"using the default :ref:`OGR SQL <ogr_sql_dialect>` dialect. The name " +"begins with an underscore and SQL syntax requires that it must appear " +"between double quotes. In addition the command line interpreter may " +"require that double quotes are escaped and the final SELECT statement " +"could look like:" +msgstr "" + +#: ../../source/programs/ogr2ogr.rst:781 +msgid "" +"If using the :ref:`SQL SQLite <sql_sqlite_dialect>` dialect, the special " +"geometry name is ``geometry`` when the source geometry column has no " +"name." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:5 +msgid "ogr_layer_algebra" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:11 +msgid "Performs various Vector layer algebraic operations." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:33 +msgid "" +"The :program:`ogr_layer_algebra` provides a command line utility to " +"perform various vector layer algebraic operations. The utility takes a " +"vector input source and a method source and generates the output of the " +"operation in the specified output file." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:38 +msgid "" +"ogr_layer_algebra is a Python utility, and is only available if GDAL " +"Python bindings are available." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:48 +msgid "``Union``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:50 +msgid "" +"A union is a set of features, which represent areas that are in either of" +" the operand layers." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:52 +msgid "``Intersection``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:54 +msgid "" +"An intersection is a set of features, which represent the common areas of" +" two layers." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:56 +msgid "``SymDifference``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:58 +msgid "" +"A symmetric difference is a set of features, which represent areas that " +"are in operand layers but which do not intersect." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:60 +msgid "``Identity``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:62 +msgid "" +"The identity method identifies features in the input layer with features " +"in the method layer possibly splitting features into several features. By" +" default the result layer has attributes from both operand layers." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:65 +msgid "``Update``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:67 +msgid "" +"The update method creates a layer, which add features into the input " +"layer from the method layer possibly cutting features in the input layer." +" By default the result layer has attributes only from the input layer." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:70 +msgid "``Clip``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:72 +msgid "" +"The clip method creates a layer, which has features from the input layer " +"clipped to the areas of the features in the method layer. By default the " +"result layer has attributes of the input layer." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:75 +msgid "``Erase``" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:77 +msgid "" +"The erase method creates a layer, which has features from the input layer" +" whose areas are erased by the features in the method layer. By default " +"the result layer has attributes of the input layer." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:82 +msgid "" +"Input dataset path for the operation to be performed. For operations " +"involving two datasets, this is one of the datasets." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:87 +msgid "" +"Layer name of the ``input_ds`` for which the operations have to be " +"performed ( Optional )" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:91 +msgid "" +"Method data set path for the operation to be performed. This is usually " +"the conditional data set supplied to the operation ( ex: clip , erase , " +"update ) This is the Second data set in the operation ( ex : Union, " +"Intersection , SymDifference )" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:97 +msgid "" +"Layer name of the ``method_ds`` for which the operations have to be " +"performed ( Optional )" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:101 +msgid "" +"Output data set path for writing the result of the operations performed " +"by ``ogr_layer_algebra``." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:105 +msgid "" +"Layer name of the ``output_lyr_name`` where the output vector has to be " +"written. ( Optional )" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:109 +msgid "" +"Indicates whether the ``output_ds`` have to be overwritten with the " +"generated result of ``ogr_layer_algebra``." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:113 +msgid "" +"Attributes for which the operation has to run on ``input_ds`` and " +"``method_ds``." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:117 +msgid "" +"Select the output format.If not specified, the format is guessed from the" +" extension (previously was ESRI Shapefile). Use the short format name" +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:123 +msgid "Dataset creation option (format specific)." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:127 +#: ../../source/programs/ogrlineref.rst:72 +msgid "Layer creation option (format specific)." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:131 +msgid "" +"Comma-delimited list of fields from input layer to copy to the output " +"layer , if eligible according to the operation." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:136 +msgid "" +"Comma-delimited list of fields from method layer to copy to the output " +"layer , if eligible according to the operation." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:141 +msgid "" +"Define the geometry type for the created layer. One of NONE, GEOMETRY, " +"POINT, LINESTRING, POLYGON, GEOMETRYCOLLECTION, MULTIPOINT, MULTIPOLYGON," +" GEOMETRY25D, POINT25D, LINESTRING25D, POLYGON25D, GEOMETRYCOLLECTION25D," +" MULTIPOINT25D, MULTIPOLYGON25D." +msgstr "" + +#: ../../source/programs/ogr_layer_algebra.rst:148 +msgid "Assign an output SRS, but without reprojecting" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:5 +msgid "ogrinfo" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:9 +msgid "" +"Lists information about an OGR-supported data source. With SQL statements" +" it is also possible to edit data." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:34 +msgid "" +"The :program:`ogrinfo` program lists various information about an OGR-" +"supported data source to stdout (the terminal). By executing SQL " +"statements it is also possible to edit data." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:46 +msgid "" +"Display the output in json format, conforming to the " +"`ogrinfo_output.schema.json " +"<https://github.com/OSGeo/gdal/blob/master/apps/data/ogrinfo_output.schema.json>`__" +" schema." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:54 +msgid "Open the data source in read-only mode." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:58 +msgid "" +"List all layers (used instead of having to give layer names as " +"arguments). In the default text output, this also enables listing all " +"features, which can be disabled with :option:`-so`. In JSON output, -al " +"is implicit, but listing of features must be explicitly enabled with " +":option:`-features`." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:67 +msgid "" +"Enable random layer reading mode, i.e. iterate over features in the order" +" they are found in the dataset, and not layer per layer. This can be " +"significantly faster for some formats (for example OSM, GMLAS). -rl " +"cannot be used with -sql." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:77 +msgid "" +"Summary Only: suppress listing of individual features and show only " +"summary information like projection, schema, feature count and extents." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:82 +msgid "Enable listing of features. This has the opposite effect of :option:`-so`." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:84 +msgid "" +"This option should be used with caution if using the library function " +":cpp:func:`GDALVectorInfo` and/or :option:`-json`, as the whole output of" +" ogrinfo will be built in memory. Consequently, when used on a large " +"collection of features, RAM may be exhausted." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:99 +msgid "" +"Quiet verbose reporting of various information, including coordinate " +"system, layer schema, extents, and feature count." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:104 +msgid "" +"An attribute query in a restricted form of the queries used in the SQL " +"`WHERE` statement. Only features matching the attribute query will be " +"reported. Starting with GDAL 2.1, the ``@<filename>`` syntax can be used " +"to indicate that the content is in the pointed filename." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:109 +msgid "Example of ``-where`` and quoting:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:118 +msgid "" +"Execute the indicated SQL statement and return the result. Starting with " +"GDAL 2.1, the ``@<filename>`` syntax can be used to indicate that the " +"content is in the pointed filename (e.g ``@my_select.txt`` where " +"my_select.txt is a file in the current directory). Data can also be " +"edited with SQL INSERT, UPDATE, DELETE, DROP TABLE, ALTER TABLE etc. " +"Editing capabilities depend on the selected dialect with " +":option:`-dialect`." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:128 +msgid "" +"SQL dialect. In some cases can be used to use (unoptimized) " +":ref:`ogr_sql_dialect` instead of the native SQL of an RDBMS by passing " +"the ``OGRSQL`` dialect value. The :ref:`sql_sqlite_dialect` can be " +"selected with the ``SQLITE`` and ``INDIRECT_SQLITE`` dialect values, and " +"this can be used with any datasource." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:135 +msgid "The area of interest. Only features within the rectangle will be reported." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:139 +msgid "Name of the geometry field on which the spatial filter operates." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:143 +msgid "" +"If provided, only the feature with this feature id will be reported. " +"Operates exclusive of the spatial or attribute queries. Note: if you want" +" to select several features based on their feature id, you can also use " +"the fact the 'fid' is a special field recognized by OGR SQL. So, `-where " +"\"fid in (1,3,5)\"` would select features 1, 3 and 5." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:151 +msgid "" +"If set to ``NO``, the feature dump will not display field values. Default" +" value is ``YES``." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:158 +msgid "Display details about a field domain." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:162 +msgid "" +"If set to ``NO``, the feature dump will not display the geometry. If set " +"to ``SUMMARY``, only a summary of the geometry will be displayed. If set " +"to ``YES`` or ``ISO_WKT``, the geometry will be reported in full OGC WKT " +"format. If set to ``WKT`` the geometry will be reported in legacy " +"``WKT``. Default value is ``YES``. (WKT and ``ISO_WKT`` are available " +"starting with GDAL 2.1, which also changes the default to ISO_WKT)" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:171 +msgid "Dataset open option (format-specific)" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:184 +msgid "" +"Report metadata for the specified domain. ``all`` can be used to report " +"metadata in all domains." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:189 +msgid "Suppress feature count printing." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:193 +msgid "Suppress spatial extent printing." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:199 +msgid "" +"Request a 3D extent to be reported (the default is 2D only). Note that " +"this operation might be slower than requesting the 2D extent, depending " +"on format and driver capabilities." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:205 +msgid "Suppress layer geometry type printing." +msgstr "" + +#: ../../source/programs/options/formats_vector.rst:3 +msgid "" +"List all vector formats supported by this GDAL build (read-only and read-" +"write) and exit. The format support is indicated as follows:" +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:7 +#: ../../source/programs/options/formats_vector.rst:6 +msgid "``ro`` is read-only driver" +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:8 +#: ../../source/programs/options/formats_vector.rst:7 +msgid "``rw`` is read or write (i.e. supports :cpp:func:`GDALDriver::CreateCopy`)" +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:9 +#: ../../source/programs/options/formats_vector.rst:8 +msgid "" +"``rw+`` is read, write and update (i.e. supports " +":cpp:func:`GDALDriver::Create`)" +msgstr "" + +#: ../../source/programs/options/formats_vector.rst:9 +msgid "" +"A ``v`` is appended for formats supporting virtual IO (``/vsimem``, " +"``/vsigzip``, ``/vsizip``, etc)." +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:11 +#: ../../source/programs/options/formats_vector.rst:10 +msgid "A ``s`` is appended for formats supporting subdatasets." +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:13 +#: ../../source/programs/options/formats_vector.rst:12 +msgid "" +"The order in which drivers are listed is the one in which they are " +"registered, which determines the order in which they are successively " +"probed when opening a dataset. Most of the time, this order does not " +"matter, but in some situations, several drivers may recognize the same " +"file. The ``-if`` option of some utilities can be specified to restrict " +"opening the dataset with a subset of drivers (generally one). Note that " +"it does not force those drivers to open the dataset. In particular, some " +"drivers have requirements on file extensions. Alternatively, the " +":config:`GDAL_SKIP` configuration option can also be used to exclude one " +"or several drivers." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:213 +msgid "" +"The WKT format used to display the SRS. Currently supported values for " +"the ``format`` are:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:218 +msgid "``WKT2`` (latest WKT version, currently *WKT2_2018*)" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:222 +msgid "``WKT2_2018``" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:228 +msgid "" +"The data source to open. May be a filename, directory or other virtual " +"name. See the OGR Vector Formats list for supported datasources." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:233 +msgid "" +"One or more layer names may be reported. If no layer names are passed " +"then ogrinfo will report a list of available layers (and their layer wide" +" geometry type). If layer name(s) are given then their extents, " +"coordinate system, feature count, geometry type, schema and all features " +"matching query parameters will be reported to the terminal. If no query " +"parameters are provided, all features are reported." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:240 +msgid "Geometries are reported in OGC WKT format." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:245 +msgid "This utility is also callable from C with :cpp:func:`GDALVectorInfo`." +msgstr "" + +#: ../../source/programs/ogrinfo.rst:252 +msgid "Example of reporting the names of the layers in a NTF file:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:265 +msgid "" +"Example of retrieving a summary (``-so``) of a layer without showing " +"details about every single feature:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:298 +msgid "" +"Example of retrieving information on a file in JSON format without " +"showing details about every single feature:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:502 +msgid "" +"Example of using -q and an attribute query, to restrict the output to " +"certain features in a layer:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:520 +msgid "" +"Example of updating a value of an attribute in a shapefile with SQL by " +"using the SQLite dialect:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:526 +msgid "Adding a column to an input file:" +msgstr "" + +#: ../../source/programs/ogrinfo.rst:532 +msgid "" +"Sometimes there is no input file involved in a calculation. In such cases" +" one may use the ``:memory:`` input file which is a in-memory empty " +"SQLite file (and the SQLite SQL dialect will be implicitly used)." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:5 +msgid "ogrlineref" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:9 +msgid "Create linear reference and provide some calculations using it" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:32 +msgid "The :program:`ogrlineref` program can be used to:" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:34 +msgid "create a linear reference file from input data" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:36 +msgid "" +"return the \"linear referenced\" distance for the projection of the input" +" coordinates (point) on the path" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:39 +msgid "" +"return the coordinates (point) on the path according to the \"linear " +"referenced\" distance" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:42 +msgid "" +"return the portion of the path according to the \"linear referenced\" " +"begin and end distances" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:45 +msgid "" +"The :program:`ogrlineref` utility creates a linear reference - a file " +"containing segments of a certain length (e.g. 1 km in reference units.) " +"The user can get coordinates, linear referenced distances or sublines " +"(subpaths) from this file. The utility does not require the ``M`` or " +"``Z`` components in the geometry. The results can be stored in any OGR " +"supported format. Also some information is written to the stdout." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:56 +msgid "Show progress." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:60 +msgid "Suppress all messages except errors and results." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:64 +#: ../../source/programs/ogrtindex.rst:50 +msgid "Select an output format name. The default is to create a shapefile." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:76 +msgid "Create the linear reference file (linestring of parts)." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:80 +msgid "The path to input linestring datasource (e.g. the road)" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:84 +#: ../../source/programs/ogrlineref.rst:97 +#: ../../source/programs/ogrlineref.rst:113 +#: ../../source/programs/ogrlineref.rst:121 +msgid "The layer name in datasource" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:88 +msgid "" +"The field name of unique values to separate the input lines (e.g. the set" +" of roads)." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:93 +msgid "The path to linear references points (e.g. the road mile-stones)" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:101 +msgid "The field name of distances along path (e.g. mile-stones values)" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:105 +msgid "The field name of unique values to map input reference points to lines." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:109 +msgid "The path to linear reference file." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:117 +msgid "The path to output linear reference file (linestring datasource)" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:125 +msgid "The field name for storing the unique values of input lines" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:129 +msgid "The part size in linear units" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:133 +msgid "Return linear referenced position for input X, Y" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:137 +msgid "Input X coordinate" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:141 +msgid "Input Y coordinate" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:145 +msgid "Return point on path for input linear distance" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:149 +msgid "The input linear distance" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:153 +msgid "Return the portion of the input path from and to input linear positions." +msgstr "" + +#: ../../source/programs/ogrlineref.rst:157 +msgid "The input begin linear distance" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:161 +msgid "The input end linear distance" +msgstr "" + +#: ../../source/programs/ogrlineref.rst:166 +msgid "" +"This example would create a shapefile (:file:`parts.shp`) containing a " +"data needed for linear referencing (1 km parts):" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:5 +msgid "ogrmerge" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:9 +msgid "Merge several vector datasets into a single one." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:27 +msgid "Options specific to the :ref:`-single <ogrmerge_single_option>` option:" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:40 +msgid "" +":program:`ogrmerge` takes as input several vector datasets, each of them " +"having one or several vector layers, and copies them into a target " +"dataset." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:44 +msgid "There are essentially two modes:" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:46 +msgid "" +"the default one, where each input vector layer, is copied as a separate " +"layer into the target dataset" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:49 +msgid "" +"another one, activated with the -single switch, where the content of all " +"input vector layers is appended into a single target layer. This assumes " +"that the schema of those vector layers is more or less the same." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:54 +msgid "" +"Internally this generates a :ref:`vector.vrt` file, and if the output " +"format is not VRT, final translation is done with :program:`ogr2ogr` or " +":py:func:`gdal.VectorTranslate`. So, for advanced uses, output to VRT, " +"potential manual editing of it and :program:`ogr2ogr` can be done." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:61 +msgid "" +"ogrmerge is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:69 +msgid "Output dataset name. Required." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:73 +msgid "One or several input vector datasets. Required" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:77 +msgid "" +"Select the output format. Starting with GDAL 2.3, if not specified, the " +"format is guessed from the extension (previously was ESRI Shapefile). Use" +" the short format name" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:84 +msgid "If specified, all input vector layers will be merged into a single one." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:88 +msgid "" +"Name of the output vector layer (in single mode, and the default is " +"\"merged\"), or template to name the output vector layers in default mode" +" (the default value is ``{AUTO_NAME}``). The template can be a string " +"with the following variables that will be susbstitued with a value " +"computed from the input layer being processed:" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:94 +msgid "" +"``{AUTO_NAME}``: equivalent to ``{DS_BASENAME}_{LAYER_NAME}`` if both " +"values are different, or ``{LAYER_NAME}`` when they are identical (case " +"of shapefile)." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:97 +msgid "``{DS_NAME}``: name of the source dataset" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:98 +msgid "``{DS_BASENAME}``: base name of the source dataset" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:99 +msgid "``{DS_INDEX}``: index of the source dataset" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:100 +msgid "``{LAYER_NAME}``: name of the source layer" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:101 +msgid "``{LAYER_INDEX}``: index of the source layer" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:105 +msgid "Open an existing dataset in update mode." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:109 +msgid "" +"Overwrite the existing dataset if it already exists (for file based " +"datasets)" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:114 +msgid "" +"Open an existing dataset in update mode, and if output layers already " +"exist, append the content of input layers to them." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:119 +msgid "" +"Open an existing dataset in update mode, and if output layers already " +"exist, replace their content with the one of the input layer." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:125 +msgid "" +"Only take into account input layers whose geometry type match the type(s)" +" specified. Valid values for geom_type_name are GEOMETRY, POINT, " +"LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, " +"GEOMETRYCOLLECTION, CIRCULARSTRING, CURVEPOLYGON, MULTICURVE, " +"MULTISURFACE, CURVE, SURFACE, TRIANGLE, POLYHEDRALSURFACE and TIN." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:141 +msgid "Assign an output SRS" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:145 +msgid "Reproject/transform to this SRS on output" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:149 +msgid "Override source SRS" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:162 +msgid "" +"Only used with :option:`-single`. Determines how the schema of the target" +" layer is built from the schemas of the input layers. May be FirstLayer " +"to use the fields from the first layer found, Union to use a super-set of" +" all the fields from all source layers, or Intersection to use a sub-set " +"of all the common fields from all source layers. Defaults to Union." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:171 +msgid "" +"Only used with :option:`-single`. If specified, the schema of the target " +"layer will be extended with a new field 'name', whose content is " +"determined by -src_layer_field_content." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:177 +msgid "" +"Only used with :option:`-single`. If specified, the schema of the target " +"layer will be extended with a new field (whose name is given by " +":option:`-src_layer_field_name`, or 'source_ds_lyr' otherwise), whose " +"content is determined by ``layer_name_template``. The syntax of " +"``layer_name_template`` is the same as for :option:`-nln`." +msgstr "" + +#: ../../source/programs/ogrmerge.rst:186 +msgid "Create a VRT with a layer for each input shapefiles" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:192 +msgid "Same, but creates a GeoPackage file" +msgstr "" + +#: ../../source/programs/ogrmerge.rst:198 +msgid "" +"Concatenate the content of france.shp and germany.shp in merged.shp, and " +"adds a 'country' field to each feature whose value is 'france' or " +"'germany' depending where it comes from." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:5 +msgid "ogrtindex" +msgstr "" + +#: ../../source/programs/ogrtindex.rst:9 +msgid "Creates a tileindex." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:30 +msgid "" +":program:`ogrtindex` program can be used to create a tileindex - a file " +"containing a list of the identities of a bunch of other files along with " +"their spatial extents. This is primarily intended to be used with " +"`MapServer <http://mapserver.org/>`__ for tiled access to layers using " +"the OGR connection type." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:42 +msgid "Add layer number ``n`` from each source file in the tile index." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:46 +msgid "Add the layer named ``name`` from each source file in the tile index." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:54 +msgid "The name to use for the dataset name. Defaults to LOCATION." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:58 +msgid "Filenames are written with absolute paths" +msgstr "" + +#: ../../source/programs/ogrtindex.rst:62 +msgid "" +"Only layers with same projection ref as layers already inserted in the " +"tileindex will be inserted." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:67 +msgid "" +"Extent of input files will be transformed to the desired target " +"coordinate reference system. Using this option generates files that are " +"not compatible with MapServer < 7.2. Default creates simple rectangular " +"polygons in the same coordinate reference system as the input vector " +"layers." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:77 +msgid "" +"The name of the field to store the SRS of each tile. This field name can " +"be used as the value of the TILESRS keyword in MapServer >= 7.2." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:84 +msgid "" +"The format in which the SRS of each tile must be written. Available " +"formats are: ``AUTO``, ``WKT``, ``EPSG``, ``PROJ``." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:91 +msgid "" +"By default ogrtindex checks that all layers inserted into the index have " +"the same attribute schemas. If you specify this option, this test will be" +" disabled. Be aware that resulting index may be incompatible with " +"MapServer!" +msgstr "" + +#: ../../source/programs/ogrtindex.rst:96 +msgid "" +"If no :option:`-lnum` or :option:`-lname` arguments are given it is " +"assumed that all layers in source datasets should be added to the tile " +"index as independent records." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:100 +msgid "" +"If the tile index already exists it will be appended to, otherwise it " +"will be created." +msgstr "" + +#: ../../source/programs/ogrtindex.rst:106 +msgid "" +"This example would create a shapefile (:file:`tindex.shp`) containing a " +"tile index of the ``BL2000_LINK`` layers in all the NTF files in the " +":file:`wrk` directory:" +msgstr "" + +#: ../../source/programs/pct2rgb.rst:5 +msgid "pct2rgb" +msgstr "" + +#: ../../source/programs/pct2rgb.rst:9 +msgid "Convert an 8bit paletted image to 24bit RGB." +msgstr "" + +#: ../../source/programs/pct2rgb.rst:24 +msgid "" +"This utility will convert a pseudo-color band on the input file into an " +"output RGB file of the desired format." +msgstr "" + +#: ../../source/programs/pct2rgb.rst:29 +msgid "" +"pct2rgb is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/pct2rgb.rst:43 +msgid "Band to convert to RGB, defaults to 1." +msgstr "" + +#: ../../source/programs/pct2rgb.rst:47 +msgid "Generate a RGBA file (instead of a RGB file by default)." +msgstr "" + +#: ../../source/programs/pct2rgb.rst:51 +msgid "" +"Extract the color table from <palette_file> instead of getting it from " +"<source_file>. Can be used to have a consistent color table for multiple " +"files. The <palette_file> must be either a raster file in a GDAL " +"supported format with a palette or a color file in a supported format " +"(txt, qml, qlr)." +msgstr "" + +#: ../../source/programs/pct2rgb.rst:64 +msgid "" +"The '-expand rgb|rgba' option of :ref:`gdal_translate` obsoletes that " +"utility." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:5 +msgid "Common options for raster programs" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:7 +msgid "All GDAL command line programs support the following common options." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:11 +#: ../../source/programs/vector_common_options.rst:11 +msgid "Report the version of GDAL and exit." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:15 +#: ../../source/programs/vector_common_options.rst:15 +msgid "Report detailed information about GDAL in use." +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:3 +msgid "" +"List all raster formats supported by this GDAL build (read-only and read-" +"write) and exit." +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:5 +msgid "The format support is indicated as follows:" +msgstr "" + +#: ../../source/programs/options/formats_raster.rst:10 +msgid "" +"A ``v`` is appended for formats supporting virtual IO (/vsimem, /vsigzip," +" /vsizip, etc)." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:22 +msgid "" +"List detailed information about a single format driver. The format should" +" be the short name reported in the --formats list, such as GTiff." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:27 +msgid "" +"Read the named file and substitute the contents into the command line " +"options list. Lines beginning with # will be ignored. Multi-word " +"arguments may be kept together with double quotes. Multiple --optfiles " +"may be used: --optfile file1 --optfile file2..." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:32 +msgid "" +"Sets the named configuration keyword to the given value, as opposed to " +"setting them as environment variables. Some common configuration keywords" +" are :config:`GDAL_CACHEMAX` (memory used internally for caching in " +"megabytes) and :config:`GDAL_DATA` (path of the GDAL \"data\" directory)." +" Individual drivers may be influenced by other :ref:`configuration " +"options <list_config_options>`." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:36 +msgid "" +"Control what debugging messages are emitted. A value of ON will enable " +"all debug messages. A value of OFF will disable all debug messages. " +"Another value will select only debug messages containing that string in " +"the debug prefix code." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:40 +msgid "" +"Gives a brief usage message for the generic GDAL command line options and" +" exit." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:43 +msgid "Creating new files" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:45 +msgid "" +"Access an existing file to read it is generally quite simple. Just " +"indicate the name of the file or dataset on the command line. However, " +"creating a file is more complicated. It may be necessary to indicate the " +"format to create, various creation options affecting how it will be " +"created and perhaps a coordinate system to be assigned. Many of these " +"options are handled similarly by different GDAL utilities, and are " +"introduced here." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:55 +msgid "" +"Select the format to create the new file as. The formats are assigned " +"short names such as GTiff (for GeoTIFF) or HFA (for Erdas Imagine). The " +"list of all format codes can be listed with the :option:`--formats` " +"switch. Only formats list as ``(rw)`` (read-write) can be written." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:62 +msgid "" +"If not specified, the format is guessed from the extension. Previously, " +"it was generally GTiff for raster, or ESRI Shapefile for vector." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:71 +msgid "" +"Several utilities (e.g. :command:`gdal_translate` and " +":command:`gdalwarp`) include the ability to specify coordinate systems " +"with command line options like :option:`-a_srs` (assign SRS to output), " +":option:`-s_srs` (source SRS) and :option:`-t_srs` (target SRS). These " +"utilities allow the coordinate system (SRS = spatial reference system) to" +" be assigned in a variety of formats." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:77 +msgid "``NAD27|NAD83|WGS84|WGS72``" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:79 +msgid "" +"These common geographic (lat/long) coordinate systems can be used " +"directly by these names." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:82 +msgid "``EPSG:n``" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:84 +msgid "" +"Coordinate systems (projected or geographic) can be selected based on " +"their EPSG codes. For instance, :samp:`EPSG:27700` is the British " +"National Grid. A list of EPSG coordinate systems can be found in the GDAL" +" data files :file:`gcs.csv` and :file:`pcs.csv`." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:89 +msgid "``PROJ.4 definition``" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:91 +msgid "" +"A PROJ.4 definition string can be used as a coordinate system. Take care " +"to keep the proj.4 string together as a single argument to the command " +"(usually by double quoting)." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:95 +msgid "For instance :samp:`+proj=utm +zone=11 +datum=WGS84`." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:97 +msgid "``OpenGIS Well Known Text``" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:99 +msgid "" +"The Open GIS Consortium has defined a textual format for describing " +"coordinate systems as part of the Simple Features specifications. This " +"format is the internal working format for coordinate systems used in " +"GDAL. The name of a file containing a WKT coordinate system definition " +"may be used a coordinate system argument, or the entire coordinate system" +" itself may be used as a command line option (though escaping all the " +"quotes in WKT is quite challenging)." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:107 +msgid "``ESRI Well Known Text``" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:109 +msgid "" +"ESRI uses a slight variation on OGC WKT format in their ArcGIS product " +"(ArcGIS :file:`.prj` files), and these may be used in a similar manner o " +"WKT files, but the filename should be prefixed with ``ESRI::``." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:113 +msgid "For example, `\"ESRI::NAD 1927 StatePlane Wyoming West FIPS 4904.prj\"`." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:115 +msgid "``Spatial References from URLs``" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:117 +msgid "" +"For example http://spatialreference.org/ref/user/north-pacific-albers-" +"conic-equal-area/." +msgstr "" + +#: ../../source/programs/raster_common_options.rst:119 +msgid ":file:`filename`" +msgstr "" + +#: ../../source/programs/raster_common_options.rst:121 +msgid "" +"File containing WKT, PROJ.4 strings, or XML/GML coordinate system " +"definitions can be provided." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:5 +msgid "rgb2pct" +msgstr "" + +#: ../../source/programs/rgb2pct.rst:9 +msgid "Convert a 24bit RGB image to 8bit paletted." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:24 +msgid "" +"This utility will compute an optimal pseudo-color table for a given RGB " +"image using a median cut algorithm on a downsampled RGB histogram. Then" +" it converts the image into a pseudo-colored image using the color table." +" This conversion utilizes Floyd-Steinberg dithering (error diffusion) to " +"maximize output image visual quality." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:32 +msgid "" +"rgb2pct is a Python utility, and is only available if GDAL Python " +"bindings are available." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:40 +msgid "" +"Select the number of colors in the generated color table. Defaults to " +"256. Must be between 2 and 256." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:45 +msgid "" +"Extract the color table from <palette_file> instead of computing it. Can " +"be used to have a consistent color table for multiple files. The " +"<palette_file> must be either a raster file in a GDAL supported format " +"with a palette or a color file in a supported format (txt, qml, qlr)." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:52 +msgid "" +"Select the output format. Starting with GDAL 2.3, if not specified, the " +"format is guessed from the extension (previously was GTiff). Use the " +"short format name. Only output formats supporting pseudo-color tables " +"should be used." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:59 +msgid "The input RGB file." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:63 +msgid "The output pseudo-colored file that will be created." +msgstr "" + +#: ../../source/programs/rgb2pct.rst:68 +msgid "" +"If it is desired to hand create the palette, likely the simplest text " +"format is the GDAL VRT format. In the following example a VRT was " +"created in a text editor with a small 4 color palette with the RGBA " +"colors 238/238/238/255, 237/237/237/255, 236/236/236/255 and " +"229/229/229/255." +msgstr "" + +#: ../../source/programs/sozip.rst:5 +msgid "sozip" +msgstr "" + +#: ../../source/programs/sozip.rst:11 +msgid "Generate a seek-optimized ZIP (SOZip) file." +msgstr "" + +#: ../../source/programs/sozip.rst:38 +msgid "The :program:`sozip` utility can be used to:" +msgstr "" + +#: ../../source/programs/sozip.rst:40 +msgid "create a :ref:`sozip_intro` file" +msgstr "" + +#: ../../source/programs/sozip.rst:41 +msgid "append files to an existing ZIP/SOZip file" +msgstr "" + +#: ../../source/programs/sozip.rst:42 +msgid "list the contents of a ZIP/SOZip file" +msgstr "" + +#: ../../source/programs/sozip.rst:43 +msgid "validate a SOZip file" +msgstr "" + +#: ../../source/programs/sozip.rst:44 +msgid "convert an existing Zip file in a SOZip optimized one" +msgstr "" + +#: ../../source/programs/sozip.rst:53 +msgid "Quiet mode. No progress message is emitted on the standard output." +msgstr "" + +#: ../../source/programs/sozip.rst:57 +msgid "Verbose mode." +msgstr "" + +#: ../../source/programs/sozip.rst:62 +msgid "" +"Grow an existing zip file with the content of the specified filename(s). " +"This is the default mode of the utility. This switch is here for " +"compatibility with Info-ZIP :program:`zip` utility" +msgstr "" + +#: ../../source/programs/sozip.rst:68 +msgid "Overwrite the target zip file if it already exists." +msgstr "" + +#: ../../source/programs/sozip.rst:73 +msgid "" +"List the files contained in the zip file in an output similar to Info-ZIP" +" :program:`unzip` utility, but with the addition of a column indicating " +"whether each file is seek-optimized." +msgstr "" + +#: ../../source/programs/sozip.rst:79 +msgid "" +"Validates a SOZip file. Baseline ZIP validation is done in a light way, " +"limited to being able to browse through ZIP records with the InfoZIP-" +"based ZIP reader used by GDAL. But validation of the SOZip-specific " +"aspects is done in a more thoroughful way." +msgstr "" + +#: ../../source/programs/sozip.rst:87 +msgid "" +"Travels the directory structure of the specified directory/directories " +"recursively." +msgstr "" + +#: ../../source/programs/sozip.rst:92 +msgid "" +"Store just the name of a saved file (junk the path), and do not store " +"directory names. By default, sozip will store the full path (relative to " +"the current directory)." +msgstr "" + +#: ../../source/programs/sozip.rst:98 +msgid "" +"Re-process {input.zip} to generate a SOZip-optimized .zip. Options " +":option:`--enable-sozip`, :option:`--sozip-chunk-size` and :option" +":`--sozip-min-file-size` may be used in that mode." +msgstr "" + +#: ../../source/programs/sozip.rst:104 +msgid "" +"In ``auto`` mode, a file is seek-optimized only if its size is above the " +"value of :option:`--sozip-chunk-size`. In ``yes`` mode, all input files " +"will be seek-optimized. In ``no`` mode, no input files will be seek-" +"optimized." +msgstr "" + +#: ../../source/programs/sozip.rst:111 +msgid "" +"Chunk size for a seek-optimized file. Defaults to 32768 bytes. The value " +"is specified in bytes, or K and M suffix can be respectively used to " +"specify a value in kilo-bytes or mega-bytes." +msgstr "" + +#: ../../source/programs/sozip.rst:117 +msgid "" +"Minimum file size to decide if a file should be seek-optimized, in " +"--enable-sozip=auto mode. Defaults to 1 MB byte. The value is specified " +"in bytes, or K, M or G suffix can be respectively used to specify a value" +" in kilo-bytes, mega-bytes or giga-bytes." +msgstr "" + +#: ../../source/programs/sozip.rst:124 +msgid "" +"Store the Content-Type for the file being added as a key-value pair in " +"the extra field extension 'KV' (0x564b) dedicated to storing key-value " +"pair metadata" +msgstr "" + +#: ../../source/programs/sozip.rst:129 +msgid "Filename of the zip file to create/append to/list." +msgstr "" + +#: ../../source/programs/sozip.rst:133 +msgid "Filename of the file to add." +msgstr "" + +#: ../../source/programs/sozip.rst:139 +msgid "" +"The :config:`GDAL_NUM_THREADS` configuration option can be set to " +"``ALL_CPUS`` or a integer value to specify the number of threads to use " +"for SOZip-compressed files. Defaults to ``ALL_CPUS``." +msgstr "" + +#: ../../source/programs/sozip.rst:146 +msgid "" +"Functionality of this utility can be done from C with " +":cpp:func:`CPLAddFileInZip` or :cpp:func:`VSICopyFile`." +msgstr "" + +#: ../../source/programs/sozip.rst:152 +msgid "" +"Create a, potentially seek-optimized, ZIP file with the content of " +"my.gpkg:" +msgstr "" + +#: ../../source/programs/sozip.rst:159 +msgid "" +"Create a, potentially seek-optimized, ZIP file from the content of a " +"source directory:" +msgstr "" + +#: ../../source/programs/sozip.rst:167 +msgid "Create a, potentially seek-optimized, ZIP file from an existing ZIP file." +msgstr "" + +#: ../../source/programs/sozip.rst:174 +msgid "" +"List the contents of a ZIP file and display which files are seek-" +"optimized:" +msgstr "" + +#: ../../source/programs/sozip.rst:181 +msgid "Validates a SOZip file:" +msgstr "" + +#: ../../source/programs/vector_common_options.rst:5 +msgid "Common options for vector programs" +msgstr "" + +#: ../../source/programs/vector_common_options.rst:7 +msgid "All GDAL OGR command line programs support the following common options." +msgstr "" + +#: ../../source/programs/vector_common_options.rst:21 +msgid "" +"List detailed information about a single format driver. The format should" +" be the short name reported in the :option:`--formats` list, such as GML." +msgstr "" + +#: ../../source/programs/vector_common_options.rst:27 +msgid "" +"Read the named file and substitute the contents into the command line " +"options list. Lines beginning with ``#`` will be ignored. Multi-word " +"arguments may be kept together with double quotes." +msgstr "" + +#: ../../source/programs/vector_common_options.rst:33 +msgid "" +"Sets the named configuration keyword to the given value, as opposed to " +"setting them as environment variables. Some common configuration keywords" +" are :config:`SHAPE_ENCODING` (force shapefile driver to read DBF files " +"with the given character encoding) and :config:`CPL_TMPDIR` (define the " +"location of temporary files). Individual drivers may be influenced by " +"other :ref:`configuration options <list_config_options>`." +msgstr "" + +#: ../../source/programs/vector_common_options.rst:41 +msgid "" +"Control what debugging messages are emitted. A value of ON will enable " +"all debug messages. A value of OFF will disable all debug messages. " +"Otherwise, a debug message will be emitted if its category appears " +"somewhere in the value string." +msgstr "" + +#: ../../source/programs/vector_common_options.rst:49 +msgid "" +"Gives a brief usage message for the generic GDAL OGR command line options" +" and exit." +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/software_using_gdal.mo b/doc/source/locale/ja/LC_MESSAGES/software_using_gdal.mo new file mode 100644 index 0000000000000000000000000000000000000000..e2267788ba9b0b286d5bc42a09828116e4c130f8 GIT binary patch literal 415 zcmYk2&rZTX5XLd_)T3t)bMS_PTO^9hpHOJQCM_kUn&@qTrIwW4y4@Oi5MR${ajQn0 zWRm%2f0=J~KF>}+8YWImo}0X=#lN^T^{aWry0=hr$JZMD4L)*JW>Qd?xlRC9%nPYB zhGm*<a9pJ&CX#}+h!UJA&a^?%WtvlHlXeHmEfO2ZHSOFq$sHjE#F)Qj^~hiD$#Y^1 zBXk|Ok7(#OpQE{F1+3JVC??9BX{jhoAA$hpPUu133mrcgIj$Rf%jM9ZBCS|zEO+cr zV8YqH?m#~XMtRnfDjiyjyizR3sZ{%tf+)UaIk0>1Qw~Va3jNSK{@QL4Ya)f_!mM*B zjEUy&`l`rTCVH@bVXEYMQ0Xmpk6gX>mMiqcT5d9tQs}NSZOypg%G|~r?m%J8Ry>Dx J%kCJ9#urd-cUS-b literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/software_using_gdal.po b/doc/source/locale/ja/LC_MESSAGES/software_using_gdal.po new file mode 100644 index 000000000000..d019463fe6e4 --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/software_using_gdal.po @@ -0,0 +1,731 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/software_using_gdal.rst:5 +msgid "Software using GDAL" +msgstr "" + +#: ../../source/software_using_gdal.rst:8 +msgid "Free and open source" +msgstr "" + +#: ../../source/software_using_gdal.rst:10 +msgid "" +"`actinia <https://actinia.mundialis.de/>`_ A cloud based geoprocessing " +"platform from mundialis (GPL v3)" +msgstr "" + +#: ../../source/software_using_gdal.rst:11 +msgid "" +"`Biodiverse <http://shawnlaffan.github.io/biodiverse>`_ A tool for the " +"spatial analysis of diversity. Uses GDAL for import/export of data (GPL " +"v3)" +msgstr "" + +#: ../../source/software_using_gdal.rst:12 +msgid "" +"`Bluemapia <https://sourceforge.net/projects/bluemapia/>`_ Multi-" +"Map(Google,Microsoft,Open Street Map, NOAA/BSB Charts,self-calibrated " +"raster) location-based GPS app for Windows Mobile. (GPL v2)" +msgstr "" + +#: ../../source/software_using_gdal.rst:13 +msgid "" +"`BRL-CAD <https://brlcad.org>`_ An open source solid modeling computer-" +"aided design system." +msgstr "" + +#: ../../source/software_using_gdal.rst:14 +msgid "" +"`Demeter <http://demeter.sourceforge.net/>`_ Another OpenGL based terrain" +" engine somewhat similar to VTP." +msgstr "" + +#: ../../source/software_using_gdal.rst:15 +msgid "" +"`EOxServer <http://eoxserver.org>`_ OGC-compliant server for Earth " +"Observation (EO) data supporting WMS and WCS with EO application profiles" +" (EOxServer Open License)" +msgstr "" + +#: ../../source/software_using_gdal.rst:16 +msgid "" +"`exactextract <https://github.com/isciences/exactextract>`_ Fast and " +"accurate raster/vector zonal statistics (Apache 2.0)" +msgstr "" + +#: ../../source/software_using_gdal.rst:17 +msgid "" +"`Feature Data Objects (FDO) <http://fdo.osgeo.org>`_ Open source " +"spatial data access libraries (LGPL)" +msgstr "" + +#: ../../source/software_using_gdal.rst:18 +msgid "" +"`Fiona <http://pypi.python.org/pypi/Fiona>`_ Fiona is OGR's neater " +"Python API – sleek and elegant on the outside, indomitable power on the " +"inside." +msgstr "" + +#: ../../source/software_using_gdal.rst:19 +msgid "" +"`gdal3.js.org <https://gdal3.js.org>`_ Convert raster and vector " +"geospatial data to various formats and coordinate systems entirely in the" +" browser." +msgstr "" + +#: ../../source/software_using_gdal.rst:20 +msgid "" +"`GdalToTiles <http://www.codeplex.com/gdal2tilescsharp>`_ C# Program " +"(open source) for making image tiles for Google Earth with KML " +"Superoverlay." +msgstr "" + +#: ../../source/software_using_gdal.rst:21 +msgid "" +"`GeoDa <http://geodacenter.github.io/index.html>`_ Introduction to " +"Spatial Data Analysis (spatial autocorrelation and spatial regression) " +"(GPL)" +msgstr "" + +#: ../../source/software_using_gdal.rst:22 +msgid "" +"`GeoDjango <https://docs.djangoproject.com/en/dev/ref/contrib/gis/>`_ A" +" framework for building geographic web applications." +msgstr "" + +#: ../../source/software_using_gdal.rst:23 +msgid "" +"`GeoKettle " +"<https://live.osgeo.org/archive/10.0/en/overview/geokettle_overview.html>`_" +" An open source spatial ETL (Extract, Transform and Load) tool (LGPL)" +msgstr "" + +#: ../../source/software_using_gdal.rst:24 +msgid "" +"`GeoNotebook <https://github.com/OpenGeoscience/geonotebook>`_ a " +"Jupyter notebook extension for geospatial visualization and analysis. " +"(Apache 2.0)" +msgstr "" + +#: ../../source/software_using_gdal.rst:25 +msgid "" +"`GeoServer <http://geoserver.org>`_ a open source software server " +"written in Java that allows users to share and edit geospatial data." +msgstr "" + +#: ../../source/software_using_gdal.rst:26 +msgid "" +"`GMT (Generic Mapping Tools) <http://gmt.soest.hawaii.edu>`_ an open " +"source collection of tools for processing and displaying xy and xyz " +"datasets." +msgstr "" + +#: ../../source/software_using_gdal.rst:27 +msgid "" +"`GRASS GIS <http://grass.osgeo.org>`_ A raster/vector open source GIS " +"that uses GDAL for raster/vector import and export (via " +"r.in.gdal/r.out.gdal)" +msgstr "" + +#: ../../source/software_using_gdal.rst:28 +msgid "`gstat <http://www.gstat.org>`_ a geostatistical modelling package." +msgstr "" + +#: ../../source/software_using_gdal.rst:29 +msgid "" +"`GuidosToolbox " +"<https://forest.jrc.ec.europa.eu/en/activities/lpa/gtb/>`_ A multi-" +"platform desktop application for generic image object analysis." +msgstr "" + +#: ../../source/software_using_gdal.rst:30 +msgid "`gvSIG <http://www.gvsig.com>`_ Desktop GIS Client." +msgstr "" + +#: ../../source/software_using_gdal.rst:31 +msgid "" +"`ILWIS <http://www.itc.nl/ilwis>`_ Remote Sensing and GIS Desktop " +"Package." +msgstr "" + +#: ../../source/software_using_gdal.rst:32 +msgid "" +"`Image I/O-Ext <https://github.com/geosolutions-it/imageio-ext>`_ " +"includes gdalframework, a framework leveraging on GDAL via SWIG's " +"generated JAVA bindings to provide support for a broad set of data " +"formats." +msgstr "" + +#: ../../source/software_using_gdal.rst:33 +msgid "" +"`libLAS <https://liblas.org>`_ Open Source LAS 1.0/1.1 ASPRS LiDAR data" +" translation toolset" +msgstr "" + +#: ../../source/software_using_gdal.rst:34 +msgid "" +"`Loader <https://github.com/AstunTechnology/Loader>`_ A simple loader " +"for geographic data in GML and KML that needs some preparation before " +"loading via ogr2ogr." +msgstr "" + +#: ../../source/software_using_gdal.rst:35 +msgid "`MapGuide <http://mapguide.osgeo.org>`_ Open source web mapping server." +msgstr "" + +#: ../../source/software_using_gdal.rst:36 +msgid "`Mapnik <http://mapnik.org>`_ C++/ Python mapping toolkit" +msgstr "" + +#: ../../source/software_using_gdal.rst:37 +msgid "" +"`MapServer <http://mapserver.org/index.html>`_ A popular web mapping " +"application with GDAL support." +msgstr "" + +#: ../../source/software_using_gdal.rst:38 +msgid "" +"`MapWindow <http://www.mapwindow.org>`_ open source ActiveX control " +"with GIS functionality." +msgstr "" + +#: ../../source/software_using_gdal.rst:39 +msgid "" +"`MultiSpec <https://github.com/larrybiehl/MultiSpec>`_ Application for " +"interactively analyzing multispectral/hyperspectral image data." +msgstr "" + +#: ../../source/software_using_gdal.rst:40 +msgid "" +"`NASA Ames Stereo Pipeline " +"<https://github.com/NeoGeographyToolkit/StereoPipeline>`_ Software for " +"creating terrain models and ortho images from planetary stereo images. " +"(Apache 2.0)" +msgstr "" + +#: ../../source/software_using_gdal.rst:41 +msgid "" +"`NASA WorldWind <https://worldwind.arc.nasa.gov/>`_ Multiplatform " +"virtual globe library to quickly and easily create interactive " +"visualizations of 3D globes, map and geographical information." +msgstr "" + +#: ../../source/software_using_gdal.rst:42 +msgid "" +"`NextGIS Formbuilder <http://nextgis.com/nextgis-formbuilder>`_ Desktop " +"application for creating and editing forms." +msgstr "" + +#: ../../source/software_using_gdal.rst:43 +msgid "" +"`NextGIS Web <http://nextgis.com/nextgis-web>`_ Server-side Web GIS and " +"a framework for storage, visualization and permissions management of all " +"kinds" +msgstr "" + +#: ../../source/software_using_gdal.rst:44 +msgid "" +"`Ogr2 GUI <https://sourceforge.net/projects/ogr2gui/>`_ Graphical user " +"interface for ogr2ogr" +msgstr "" + +#: ../../source/software_using_gdal.rst:45 +msgid "" +"`OpenCPN <http://opencpn.org>`_ A concise ChartPlotter/Navigator. A " +"cross-platform ship-borne GUI application." +msgstr "" + +#: ../../source/software_using_gdal.rst:46 +msgid "" +"`OpenEV <http://openev.sourceforge.net>`_ An OpenGL/GTK/Python based " +"graphical viewer which exclusively uses GDAL for raster access." +msgstr "" + +#: ../../source/software_using_gdal.rst:47 +msgid "" +"`OFGT <https://github.com/openforis/geospatial-toolkit>`_ a collection " +"of utilities for multipurpose forest monitoring under the `Open Foris " +"Initiative <http://km.fao.org/OFwiki/index.php/Main_Page>`_ Open Foris " +"Initiative." +msgstr "" + +#: ../../source/software_using_gdal.rst:48 +msgid "" +"`OpenFLUID <https://www.openfluid-project.org>`_ a software platform " +"for spatial modelling of landscapes dynamics" +msgstr "" + +#: ../../source/software_using_gdal.rst:49 +msgid "" +"`OpenSceneGraph <http://www.openscenegraph.org>`_ 3D rendering engine " +"with `osgdem " +"<http://www.openscenegraph.org/projects/osg/wiki/Support/UserGuides/osgdem>`_" +" and `osgEarth <http://wush.net/trac/osgearth/wiki/Downloads>`_ plugins." +msgstr "" + +#: ../../source/software_using_gdal.rst:50 +msgid "" +"`Opticks <http://opticks.org>`_ an open source remote sensing " +"application and development framework, with a GDAL plugin." +msgstr "" + +#: ../../source/software_using_gdal.rst:51 +msgid "" +"`Orfeo Toolbox (OTB) <http://www.orfeo-toolbox.org>`_ a general remote " +"sensing image processing library." +msgstr "" + +#: ../../source/software_using_gdal.rst:52 +msgid "" +"`OSSIM <http://www.ossim.org>`_ Another geospatial viewing and analysis" +" environment which uses GDAL as one of several plugins." +msgstr "" + +#: ../../source/software_using_gdal.rst:53 +msgid "`PDAL <https://pdal.io>`_ Point Cloud Data Abstraction Library" +msgstr "" + +#: ../../source/software_using_gdal.rst:54 +msgid "" +"`pktools <http://pktools.nongnu.org/html/index.html>`_ open source " +"(GPLv3) tools written in C++ for remote sensing image processing" +msgstr "" + +#: ../../source/software_using_gdal.rst:55 +msgid "" +"`PNMapcalc <http://pawel.netzel.pl/index.php?id=software#a_mapcalc>`_ A" +" raster map calculator with C-like scripting language." +msgstr "" + +#: ../../source/software_using_gdal.rst:56 +msgid "" +"`PostGIS <http://www.postgis.net>`_ spatial database extender for " +"PostgreSQL: The raster loader and many of the raster SQL functions rely " +"on GDAL." +msgstr "" + +#: ../../source/software_using_gdal.rst:57 +msgid "" +"`PostgreSQL OGR Foreign Data Wrapper <https://github.com/pramsey/pgsql-" +"ogr-fdw>`_ Expose OGR layer as PostgreSQL foreign tables." +msgstr "" + +#: ../../source/software_using_gdal.rst:58 +msgid "`QGIS <http://www.qgis.org>`_ A cross platform desktop GIS." +msgstr "" + +#: ../../source/software_using_gdal.rst:59 +msgid "" +"`R <http://www.r-project.org>`_ A free software environment for " +"statistical computing and graphics, with bindings to GDAL via the rgdal " +"package." +msgstr "" + +#: ../../source/software_using_gdal.rst:60 +msgid "" +"`Rasterio <https://rasterio.readthedocs.io>`_ Python library and " +"command line utilities to read and write GDAL rasters." +msgstr "" + +#: ../../source/software_using_gdal.rst:61 +msgid "" +"`Rasterix <https://github.com/mogasw/rasterix/>`_ A cross platform open" +" source utility to process raster data based on Qt and GDAL." +msgstr "" + +#: ../../source/software_using_gdal.rst:62 +msgid "" +"`SAGA GIS <http://www.saga-gis.org/en/index.html>`_ A free geographic " +"information system (GIS), with a special 'Application Programming " +"Interface' (API) for geographic data processing." +msgstr "" + +#: ../../source/software_using_gdal.rst:63 +msgid "" +"`SNAP <http://step.esa.int/main/toolboxes/snap>`_ Sentinel Application " +"Platform for Earth Observation processing and analysis." +msgstr "" + +#: ../../source/software_using_gdal.rst:64 +msgid "" +"`StarSpan <https://github.com/Ecotrust/starspan>`_ raster/vector " +"analysis." +msgstr "" + +#: ../../source/software_using_gdal.rst:65 +msgid "" +"`t-rex <http://t-rex.tileserver.ch>`_ Vector tile server written in " +"Rust." +msgstr "" + +#: ../../source/software_using_gdal.rst:66 +msgid "" +"`Thuban <http://thuban.intevation.org>`_ A multi-platform interactive " +"geographic data viewer." +msgstr "" + +#: ../../source/software_using_gdal.rst:67 +msgid "" +"`Vertual Terrain Project <http://www.vterrain.org>`_ fostering tools " +"for easy construction of the real world in interactive, 3D digital form." +msgstr "" + +#: ../../source/software_using_gdal.rst:68 +msgid "" +"`ViRGiS <https://www.virgis.org/>`__ Creating a GIS Platform in Virtual " +"Reality / Mixed Reality" +msgstr "" + +#: ../../source/software_using_gdal.rst:71 +msgid "Proprietary license / Other" +msgstr "" + +#: ../../source/software_using_gdal.rst:73 +msgid "" +"`3D DEM Viewer <http://www.msmacrosystem.nl/Ilwis/index.html>`_ from MS " +"MacroSystem." +msgstr "" + +#: ../../source/software_using_gdal.rst:74 +msgid "" +"`Cadcorp SIS: <http://www.cadcorp.com>`_ A Windows GIS with a GDAL and " +"OGR plugins." +msgstr "" + +#: ../../source/software_using_gdal.rst:75 +msgid "" +"`Carmenta Engine <http://www.carmenta.com>`_ (previously known as " +"SpatialAce): A GIS Rapid Application Development environment" +msgstr "" + +#: ../../source/software_using_gdal.rst:76 +msgid "" +"`CARTO <http://www.carto.com>`_ A cloud mapping platform to analyze and " +"visualize geospatial data." +msgstr "" + +#: ../../source/software_using_gdal.rst:77 +msgid "`Cartographica <http://www.macgis.com>`_ Macintosh GIS package." +msgstr "" + +#: ../../source/software_using_gdal.rst:78 +msgid "" +"`CatchmentSIM <https://csse.com.au/index.php/products/catchmentsim>`_ A " +"Windows terrain analysis model for hydrologic applications." +msgstr "" + +#: ../../source/software_using_gdal.rst:79 +msgid "" +"`Daylon Leveller <https://www.daylongraphics.com/products/leveller.php>`_" +" A terrain/heightfield/bumpmap modeler" +msgstr "" + +#: ../../source/software_using_gdal.rst:80 +msgid "" +"`Eonfusion <http://www.eonfusion.com>`_ Analysis and visualization of " +"time-varying spatial datasets integrated via true data fusion." +msgstr "" + +#: ../../source/software_using_gdal.rst:81 +msgid "" +"`ERDAS ER Viewer <https://www.hexagongeospatial.com/products/power-" +"portfolio/other-producer-products/erdas-er-viewer>`_ Image viewer for " +"very large JPEG 2000 and ECW files." +msgstr "" + +#: ../../source/software_using_gdal.rst:82 +msgid "`ESRI ArcGIS 9.2+ <http://www.esri.com>`_ A popular GIS platform." +msgstr "" + +#: ../../source/software_using_gdal.rst:83 +msgid "" +"`Eternix Blaze <http://www.eternix.co.il>`_ Advanced geo-spatial " +"visualization application and SDK." +msgstr "" + +#: ../../source/software_using_gdal.rst:84 +msgid "" +"`FalconView <http://www.falconview.org>`_ Windows-based GIS platform " +"with roots in military mission planning, now available as a free GIS " +"visualization and analysis package." +msgstr "" + +#: ../../source/software_using_gdal.rst:85 +msgid "" +"`flighttrack <http://flighttrack.sourceforge.net>`_ GPS track viewing " +"and downloading software for Mac." +msgstr "" + +#: ../../source/software_using_gdal.rst:86 +msgid "" +"`FME <http://www.safe.com>`_ A GIS translator package includes a GDAL " +"plugin." +msgstr "" + +#: ../../source/software_using_gdal.rst:87 +msgid "" +"`GenGIS <http://kiwi.cs.dal.ca/GenGIS>`_ Software for geospatial " +"analysis of genetic data." +msgstr "" + +#: ../../source/software_using_gdal.rst:88 +msgid "" +"`Geographic Imager <https://www.avenza.com/geographic-imager>`_ DEM / " +"aerial / satellite image processing GIS plug-in for Adobe Photoshop, by " +"Avenza Systems." +msgstr "" + +#: ../../source/software_using_gdal.rst:89 +msgid "" +"`GeoDMS <http://www.objectvision.hosting.it-rex.nl/geodms>`_ A " +"framework for building spatial calculation models." +msgstr "" + +#: ../../source/software_using_gdal.rst:90 +msgid "`GeoFusion <http://www.geofusion.com>`_ 3D visualization." +msgstr "" + +#: ../../source/software_using_gdal.rst:91 +msgid "" +"`GeoView Pro <https://apps.apple.com/lu/app/geoview-" +"pro/id590559352?l=fr>`_ IOS mobile mapping application." +msgstr "" + +#: ../../source/software_using_gdal.rst:92 +msgid "" +"`Geoweb3d <http://www.geoweb3d.com>`_ A 3D virtual globe that provides " +"on-the-fly, game-quality visualization of GIS data." +msgstr "" + +#: ../../source/software_using_gdal.rst:93 +msgid "`Google Earth <http://earth.google.com>`_ A 3D world viewer." +msgstr "" + +#: ../../source/software_using_gdal.rst:94 +msgid "" +"`GPSeismic <http://www.gpseismic.com>`_ A suite of applications for " +"seismic survey." +msgstr "" + +#: ../../source/software_using_gdal.rst:95 +msgid "" +"`HydroDaVE Explorer <http://www.hydrodave.com>`_ A web-enabled client " +"that provides users an easy to use, secure, and reliable data management " +"platform to efficiently manage, access, and analyze environmental data." +msgstr "" + +#: ../../source/software_using_gdal.rst:96 +msgid "" +"`IDRISI <http://www.idrisi.com>`_ A GIS and Image Processing Windows " +"Desktop application. Uses GDAL to import/export/warp raster data." +msgstr "" + +#: ../../source/software_using_gdal.rst:97 +msgid "" +"`Infraworks <https://www.autodesk.com/products/infraworks/overview>`_ a" +" BIM software for infrastructure project design, part of the Autodesk " +"suite." +msgstr "" + +#: ../../source/software_using_gdal.rst:98 +msgid "" +"`iShare <https://www.astuntechnology.com/cloud-products/ishare/>`_ Web " +"data integration and publishing platform by Astun Technology." +msgstr "" + +#: ../../source/software_using_gdal.rst:99 +msgid "" +"`Makai Voyager <http://voyager.makai.com>`_ An advanced 3D/4D " +"geospatial visualization platform." +msgstr "" + +#: ../../source/software_using_gdal.rst:100 +msgid "" +"`MapInfo Professional <http://www.mapinfo.com/product/mapinfo-" +"professional>`_ Desktop GIS and mapping application" +msgstr "" + +#: ../../source/software_using_gdal.rst:101 +msgid "" +"`MapTiler <http://www.maptiler.com>`_ Generator of tiles for " +"interactive maps and overlays made from raster images and geodata." +msgstr "" + +#: ../../source/software_using_gdal.rst:102 +msgid "" +"`Maptitude Mapping Software " +"<http://www.caliper.com/maptitude/mappingsoftware.htm>`_ Desktop GIS and" +" business mapping application" +msgstr "" + +#: ../../source/software_using_gdal.rst:103 +msgid "" +"`MicroImages TNT <http://www.microimages.com>`_ advanced software for " +"geospatial analysis (Windows, Linux, Mac OS X and UNIX)" +msgstr "" + +#: ../../source/software_using_gdal.rst:104 +msgid "" +"`Micromine <http://www.micromine.com>`_ A mining software solution that" +" uses GDAL for reading/writing various geospatial file formats." +msgstr "" + +#: ../../source/software_using_gdal.rst:105 +msgid "" +"`Mirone <http://joa-quim.pt/mirone/main.html>`_ Matlab based package " +"for geospatial, oceanographic and geophysical analysis of grids" +msgstr "" + +#: ../../source/software_using_gdal.rst:106 +msgid "" +"`Mygeodata Converter " +"<http://mygeodata.eu/apps/converter/index_EN.html>`_ Online converter of" +" GDAL raster and OGR vector formats" +msgstr "" + +#: ../../source/software_using_gdal.rst:107 +msgid "" +"`OPALS <https://opals.geo.tuwien.ac.at/html/stable/index.html>`_ " +"Orientation and Processing of Airborne Laser Scanning Data" +msgstr "" + +#: ../../source/software_using_gdal.rst:108 +msgid "" +"`Procura <http://www.michellcomputing.co.uk/procura.html>`_ Landholding " +"inspection system developed for the UK Homes and Communities Agency. GDAL" +" is used for checking out background mapping." +msgstr "" + +#: ../../source/software_using_gdal.rst:109 +msgid "" +"`ScanMagic " +"<https://www.scanex.ru/en/software/vizualizatsiya-i-katalogizatsiya/scan-" +"magic/>`_ Win32 application for visualization, analysis and processing of" +" remote sensing data." +msgstr "" + +#: ../../source/software_using_gdal.rst:110 +msgid "" +"`Scalable Algorithmics (SCALGO) <http://scalgo.com>`_ Software for " +"efficiently constructing and performing computations on very large raster" +" and TIN terrain models." +msgstr "" + +#: ../../source/software_using_gdal.rst:111 +msgid "" +"`Scenomics <http://www.scenomics.com>`_ Software for building terrain " +"databases uses GDAL for projection and data import/export." +msgstr "" + +#: ../../source/software_using_gdal.rst:112 +msgid "" +"`scenProc <http://www.scenerydesign.org/scenproc>`_ scenProc: A tool to " +"create scenery for Microsoft Flight Simulator and Lockheed Martin " +"Prepar3D by processing G" +msgstr "" + +#: ../../source/software_using_gdal.rst:113 +msgid "" +"`SeaView <https://www.seaviewgis.com>`_ A 3D GIS package for " +"geophysical and hydrographical data (side scan sonar, subbottom profiler," +" magnetometer, multibeam, etc." +msgstr "" + +#: ../../source/software_using_gdal.rst:114 +msgid "" +"`SkylineGlobe <http://www.skylineglobe.com>`_ The Skyline suite of " +"interactive applications allows you to build, view, query and analyze " +"customized, virtual 3D landscapes." +msgstr "" + +#: ../../source/software_using_gdal.rst:115 +msgid "" +"`SpacEyes3D <http://www.spaceyes.com>`_ 3D visualization software for " +"cartographic data." +msgstr "" + +#: ../../source/software_using_gdal.rst:116 +msgid "" +"`Spatial Manager <http://www.spatialmanager.com>`_ A product suite " +"designed designed to manage spatial data in a simple, fast and " +"inexpensive way. Uses GDAL to import/export data." +msgstr "" + +#: ../../source/software_using_gdal.rst:117 +msgid "" +"`TacitView <https://www.insitu.com/information-delivery/information-" +"processing/tacitview>`_ An imagery visualization and exploitation " +"package for military intelligence." +msgstr "" + +#: ../../source/software_using_gdal.rst:118 +msgid "" +"`TatukGIS <http://www.tatukgis.com>`_ Desktop GIS mapping and data " +"editing application." +msgstr "" + +#: ../../source/software_using_gdal.rst:119 +msgid "" +"`Team Awareness Kit <https://tak.gov>`_ Suite of georeferenced imagery " +"and situational awareness tools developed for military planning and " +"execution, now available for civilian use." +msgstr "" + +#: ../../source/software_using_gdal.rst:120 +msgid "" +"`TerraGo Technologies <http://www.terragotech.com>`_ The GeoPDF file " +"format is used to distribute and collaborate geospatial data and uses " +"GDAL for data import/export." +msgstr "" + +#: ../../source/software_using_gdal.rst:121 +msgid "" +"`TerrainView <http://www.viewtec.net>`_ Interactive real-time 3D GIS " +"Software." +msgstr "" + +#: ../../source/software_using_gdal.rst:122 +msgid "" +"`TransCAD GIS <http://www.caliper.com>`_ Desktop Transportation " +"Analysis Software" +msgstr "" + +#: ../../source/software_using_gdal.rst:123 +msgid "" +"`TravTime <https://travtime.software.informer.com/download/>`_ .NET " +"Application for visualizing, processing and analyzing GPS data for travel" +" time, speed, and de" +msgstr "" + +#: ../../source/software_using_gdal.rst:124 +msgid "" +"`VectorWorks <http://www.vectorworks.net>`_ The Vectorworks line of " +"software products provides professional design solutions in the AEC, " +"entertainment and landscape design industries." +msgstr "" + +#: ../../source/software_using_gdal.rst:125 +msgid "" +"`WindNinja <https://www.firelab.org/project/windninja>`_ wind model for" +" fire behavior modeling." +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/sponsors.mo b/doc/source/locale/ja/LC_MESSAGES/sponsors.mo new file mode 100644 index 0000000000000000000000000000000000000000..e2267788ba9b0b286d5bc42a09828116e4c130f8 GIT binary patch literal 415 zcmYk2&rZTX5XLd_)T3t)bMS_PTO^9hpHOJQCM_kUn&@qTrIwW4y4@Oi5MR${ajQn0 zWRm%2f0=J~KF>}+8YWImo}0X=#lN^T^{aWry0=hr$JZMD4L)*JW>Qd?xlRC9%nPYB zhGm*<a9pJ&CX#}+h!UJA&a^?%WtvlHlXeHmEfO2ZHSOFq$sHjE#F)Qj^~hiD$#Y^1 zBXk|Ok7(#OpQE{F1+3JVC??9BX{jhoAA$hpPUu133mrcgIj$Rf%jM9ZBCS|zEO+cr zV8YqH?m#~XMtRnfDjiyjyizR3sZ{%tf+)UaIk0>1Qw~Va3jNSK{@QL4Ya)f_!mM*B zjEUy&`l`rTCVH@bVXEYMQ0Xmpk6gX>mMiqcT5d9tQs}NSZOypg%G|~r?m%J8Ry>Dx J%kCJ9#urd-cUS-b literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/sponsors.po b/doc/source/locale/ja/LC_MESSAGES/sponsors.po new file mode 100644 index 000000000000..b33333b2d2eb --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/sponsors.po @@ -0,0 +1,312 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/sponsors/faq.rst:5 +msgid "Sponsoring FAQ" +msgstr "" + +#: ../../source/sponsors/faq.rst:8 +msgid "Why does GDAL need sponsorship?" +msgstr "" + +#: ../../source/sponsors/faq.rst:10 +msgid "" +"GDAL is the most central piece of `Critical Digital Infrastructure`_ in " +"the geospatial world, serving as the primary building block for data " +"management and processing in open source, commercial, and government " +"geospatial software. But most of its resources have gone to the " +"development of new features, while the maintenance burden has only " +"increased with more functionality." +msgstr "" + +#: ../../source/sponsors/faq.rst:18 +msgid "" +"The purpose of sponsor funding is to provide substantial long-acting " +"resources that give the project the ability to address software, testing," +" and project challenges that do not attract individual sponsorship " +"attention. With a pool of resources that are not earmarked for features, " +"it can attack usability, performance, and modernization challenges that " +"benefit everyone. Sustained funding enables multi-year efforts that do " +"not disrupt the existing GDAL user base, and it will provide the baseline" +" resources to allow day-to-day maintenance operations to continue " +"uninterrupted." +msgstr "" + +#: ../../source/sponsors/faq.rst:27 +msgid "" +"The larger funding levels enabled by sponsorship aim to help GDAL grow to" +" a team of maintainers, as is typical in other leading open source " +"projects. The past few years have seen only one maintainer, who has been " +"stretched thin. The resources provided by this effort allow maintenance " +"activities to continue *and* allow the project to support on-boarding " +"additional developers to tackle various needs of the project that have " +"been ignored due to lack of direct funding interest." +msgstr "" + +#: ../../source/sponsors/faq.rst:34 +msgid "My organization wants to sponsor. How can we do that?" +msgstr "" + +#: ../../source/sponsors/faq.rst:36 +msgid "" +"To learn about the benefits of becoming a sponsor at various levels start" +" with the `Sustainable GDAL Sponsorship Prospectus`_. If you are " +"interested, need help convincing your key decision-makers, or have any " +"questions, don't hesitate to contact gdal-sponsors@osgeo.org." +msgstr "" + +#: ../../source/sponsors/faq.rst:44 +msgid "" +"What is NumFOCUS and why is the project using that foundation rather than" +" using OSGeo for this effort?" +msgstr "" + +#: ../../source/sponsors/faq.rst:46 +msgid "" +"`NumFOCUS <https://numfocus.org>`__ is a US-based 501(c)(3) tax-exempt " +"non-profit that is already managing funding for many individual software " +"projects using this model such as Numpy, Jupyter, pandas, Julia, and " +"SciPy. They have staff, policies, procedures, and infrastructure for " +"managing the financial support of open source software projects with this" +" funding model. Many organizations in the initial list of sponsors are " +"already funding projects through NumFOCUS, and adding GDAL to the roster " +"improves efficiency on their side." +msgstr "" + +#: ../../source/sponsors/faq.rst:54 +msgid "" +"`OSGeo <https://www.osgeo.org>`__ does not have staff and procedures to " +"manage tracking workloads and payments. OSGeo also does not provide tax-" +"exempt status for contributions. NumFOCUS has established relationships " +"with a large number of the initial sponsors. These properties are why the" +" GDAL PSC has chosen the NumFOCUS path for management of this effort." +msgstr "" + +#: ../../source/sponsors/faq.rst:61 +msgid "So GDAL is a NumFOCUS project now?" +msgstr "" + +#: ../../source/sponsors/faq.rst:63 +msgid "" +"Not exactly. GDAL will be a project within NumFOCUS under the \"Grantor-" +"Grantee Model\". OSGeo is still the primary foundational \"home\" of GDAL" +" such as it is, but NumFOCUS is providing this financial vehicle and " +"service to the project under the purview of its charter." +msgstr "" + +#: ../../source/sponsors/faq.rst:69 +msgid "What is the project going to do with the money?" +msgstr "" + +#: ../../source/sponsors/faq.rst:71 +msgid "" +"The GDAL PSC will control the purse strings. Contributors seeking " +"resources will submit a proposal to the PSC (RFC-style, but not public) " +"describing the tasks and efforts they will seek to achieve. Any " +"substantial efforts with external impacts will continue to be required to" +" use the GDAL RFC process as described in :ref:`rfc-1`." +msgstr "" + +#: ../../source/sponsors/faq.rst:77 +msgid "" +"Developers will be able submit requests to the GDAL PSC for 'maintenance " +"work units', which could encompass ticket i/o and related code " +"improvements, CI grooming, mailing list gardening, and fuzzing response " +"activities." +msgstr "" + +#: ../../source/sponsors/faq.rst:81 +msgid "" +"A significant portion (25% per year if possible) of the resources will be" +" targeted toward *growing* new active developers into the project. " +"Examples of this include soliciting ticket and code contributors with " +"funding if they show interest and aptitude, and providing resources to " +"mentor and support junior developers who are working into roles in the " +"project. These activities are extremely hard to do without financial " +"support." +msgstr "" + +#: ../../source/sponsors/faq.rst:88 +msgid "" +"Spot resources will be available to attack needs that have difficulty " +"finding funded attention, such as API improvements in support of specific" +" application niches and subsystem refreshes like build, tests, and CI. " +"The GDAL PSC could fund significant RFCs that demonstrate need and " +"agreement on an ad hoc basis." +msgstr "" + +#: ../../source/sponsors/faq.rst:93 +msgid "" +"The GDAL PSC will delegate some resources to GDAL-related projects and " +"dependencies – libtiff, libgeotiff, PROJ, shapelib, and the various " +"language bindings and libraries. If more resources than the GDAL project " +"itself can use are available for a particular year, the project will open" +" them up to the wider community of related libraries and users to " +"repurpose them." +msgstr "" + +#: ../../source/sponsors/faq.rst:100 +msgid "How can the resources be used?" +msgstr "" + +#: ../../source/sponsors/faq.rst:102 +msgid "" +"The funds cannot be used to benefit an individual contributor or be " +"directed by a contributor through the non-profit organization. For " +"example, a fictional Imagery Corp cannot fund NumFOCUS with explicit " +"intent to have those resources used to fix bugs or add features that " +"benefit Imagery Corp. Imagery Corp can still continue to solicit GDAL " +"active contributors, or actively contribute the fixes themselves, to " +"achieve their goals with the software." +msgstr "" + +#: ../../source/sponsors/faq.rst:110 +msgid "How is this going to impact GDAL software releases?" +msgstr "" + +#: ../../source/sponsors/faq.rst:112 +msgid "" +"A primary goal of this effort is to provide resources needed to allow the" +" current GDAL maintainer to keep up the existing release schedule and " +"cadence. Without these resources, the schedule was likely to have " +"significantly stretched out to one or two maintenance releases per year." +msgstr "" + +#: ../../source/sponsors/faq.rst:119 +msgid "Can I use some of the funding to support fixing something?" +msgstr "" + +#: ../../source/sponsors/faq.rst:121 +msgid "" +"Quite possibly. The GDAL PSC will provide a proposal template where you " +"will need to describe the issue(s), propose the approach and impacts of " +"it, and state your cost to complete the effort." +msgstr "" + +#: ../../source/sponsors/index.rst:5 +msgid "Sponsors" +msgstr "" + +#: ../../source/sponsors/index.rst:7 +msgid "" +"GDAL is a truly collaborative effort, with many diverse organizations " +"contributing resources to its success. The following organizations take " +"an extra step, providing unrestricted funding every year to maintain and " +"improve the health of the project:" +msgstr "" + +#: ../../source/sponsors/index.rst:12 +msgid "Gold level:" +msgstr "" + +#: ../../source/sponsors/index.rst:47 +msgid "Silver level:" +msgstr "" + +#: ../../source/sponsors/index.rst:70 +msgid "Bronze level:" +msgstr "" + +#: ../../source/sponsors/index.rst:113 +msgid "Supporter level:" +msgstr "" + +#: ../../source/sponsors/index.rst:120 +msgid "Myles Sutherland" +msgstr "" + +#: ../../source/sponsors/index.rst:124 +msgid "`Dynamic Graphics, Inc. <https://www.dgi.com/>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:128 +msgid "`Kaplan Open Source Consulting <https://kaplanopensource.co.il/>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:132 +msgid "`PIX4D <https://www.pix4d.com/>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:136 +msgid "`Regrid <https://regrid.com>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:140 +msgid "`Satelligence <https://satelligence.com/>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:144 +msgid "`Space Intelligence <https://www.space-intelligence.com>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:148 +msgid "`Umbra <https://umbra.space/>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:152 +msgid "`Vortex f.d.c. <https://vortexfdc.com/>`__" +msgstr "" + +#: ../../source/sponsors/index.rst:194 +msgid "" +"The GDAL Project is hosted by `OSGeo <https://www.osgeo.org>`__, and a " +"fiscally sponsored project of `NumFOCUS <https://numfocus.org>`__, a " +"nonprofit dedicated to supporting the open-source scientific computing " +"community. If you like GDAL and want to support our mission, please " +"consider making a `donation <https://numfocus.org/donate-to-gdal>`__ to " +"support our efforts." +msgstr "" + +#: ../../source/sponsors/index.rst:200 +msgid "" +"NumFOCUS is 501(c)(3) non-profit charity in the United States; as such, " +"donations to NumFOCUS are tax-deductible as allowed by law. As with any " +"donation, you should consult with your personal tax adviser or the IRS " +"about your particular tax situation." +msgstr "" + +#: ../../source/sponsors/index.rst:221 +msgid "Sponsoring" +msgstr "" + +#: ../../source/sponsors/index.rst:223 +msgid "" +"If your organization benefits from GDAL we recommend joining the group of" +" sponsors above to \"pay it forward\" and ensure the project has the " +"resources to stay healthy and grow. To learn about the benefits of " +"becoming a sponsor at various levels start with the `Sustainable GDAL " +"Sponsorship Prospectus`_. If you are interested, need help convincing " +"your key decision-makers, or have any questions, don't hesitate to " +"contact gdal-sponsors@osgeo.org." +msgstr "" + +#: ../../source/sponsors/index.rst:231 +msgid "Related resources" +msgstr "" + +#: ../../source/sponsors/index.rst:233 +msgid "`Sustainable GDAL Sponsorship Prospectus`_." +msgstr "" + +#: ../../source/sponsors/index.rst:234 +msgid ":ref:`Sponsoring frequently asked questions (FAQ) <sponsoring-faq>`." +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/tutorials.mo b/doc/source/locale/ja/LC_MESSAGES/tutorials.mo new file mode 100644 index 0000000000000000000000000000000000000000..e2267788ba9b0b286d5bc42a09828116e4c130f8 GIT binary patch literal 415 zcmYk2&rZTX5XLd_)T3t)bMS_PTO^9hpHOJQCM_kUn&@qTrIwW4y4@Oi5MR${ajQn0 zWRm%2f0=J~KF>}+8YWImo}0X=#lN^T^{aWry0=hr$JZMD4L)*JW>Qd?xlRC9%nPYB zhGm*<a9pJ&CX#}+h!UJA&a^?%WtvlHlXeHmEfO2ZHSOFq$sHjE#F)Qj^~hiD$#Y^1 zBXk|Ok7(#OpQE{F1+3JVC??9BX{jhoAA$hpPUu133mrcgIj$Rf%jM9ZBCS|zEO+cr zV8YqH?m#~XMtRnfDjiyjyizR3sZ{%tf+)UaIk0>1Qw~Va3jNSK{@QL4Ya)f_!mM*B zjEUy&`l`rTCVH@bVXEYMQ0Xmpk6gX>mMiqcT5d9tQs}NSZOypg%G|~r?m%J8Ry>Dx J%kCJ9#urd-cUS-b literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/tutorials.po b/doc/source/locale/ja/LC_MESSAGES/tutorials.po new file mode 100644 index 000000000000..98a17a301c74 --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/tutorials.po @@ -0,0 +1,4534 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/tutorials/gdal_grid_tut.rst:5 +msgid "GDAL Grid Tutorial" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:8 +msgid "Introduction to Gridding" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:10 +msgid "" +"Gridding is a process of creating a regular grid (or call it a raster " +"image) from the scattered data. Typically you have a set of arbitrary " +"data scattered over the region of survey measurements and you would like " +"to convert them into the regular grid for further processing and " +"combining with other grids." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:-1 +msgid "Scattered data gridding" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:25 +msgid "" +"This problem can be solved using data interpolation or approximation " +"algorithms. But you are not limited by interpolation here. Sometimes you " +"don't need to interpolate your data but rather compute some statistics or" +" data metrics over the region. Statistics are valuable themselves or " +"could be used for better choosing the interpolation algorithm and " +"parameters." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:31 +msgid "" +"That is what GDAL Grid API is about. It helps you to interpolate your " +"data (see `Interpolation of the Scattered Data`_) or compute data metrics" +" (see `Data Metrics Computation`_)." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:35 +msgid "" +"There are two ways of using this interface. Programmatically it is " +"available through the :cpp:func:`GDALGridCreate` C function; for end " +"users there is a :ref:`gdal_grid` utility (which see for an up-to-date " +"list of all current features). The rest of this document discusses " +"details on algorithms and their parameters implemented in GDAL Grid API." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:42 +msgid "Interpolation of the Scattered Data" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:45 +msgid "Inverse Distance to a Power" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:47 +msgid "" +"The Inverse Distance to a Power gridding method is a weighted average " +"interpolator. You should supply the input arrays with the scattered data " +"values including coordinates of every data point and output grid " +"geometry. The function will compute an interpolated value for the given " +"position in the output grid." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:53 +msgid "" +"For every grid node the resulting value :math:`Z` will be calculated " +"using the formula:" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:56 +msgid "Z=\\frac{\\sum_{i=1}^n{\\frac{Z_i}{r_i^p}}}{\\sum_{i=1}^n{\\frac{1}{r_i^p}}}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:60 +#: ../../source/tutorials/gdal_grid_tut.rst:103 +#: ../../source/tutorials/gdal_grid_tut.rst:139 +#: ../../source/tutorials/gdal_grid_tut.rst:155 +#: ../../source/tutorials/gdal_grid_tut.rst:172 +msgid "where:" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:62 +#: ../../source/tutorials/gdal_grid_tut.rst:106 +#: ../../source/tutorials/gdal_grid_tut.rst:142 +#: ../../source/tutorials/gdal_grid_tut.rst:158 +#: ../../source/tutorials/gdal_grid_tut.rst:175 +msgid ":math:`Z_i` is a known value at point :math:`i`," +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:63 +msgid ":math:`r_i` is a distance from the grid node to point :math:`i`," +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:64 +msgid ":math:`p` is a weighting power," +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:65 +#: ../../source/tutorials/gdal_grid_tut.rst:143 +#: ../../source/tutorials/gdal_grid_tut.rst:159 +#: ../../source/tutorials/gdal_grid_tut.rst:176 +msgid ":math:`n` is a number of points in `Search Ellipse`_." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:67 +msgid "" +"The smoothing parameter :math:`s` is used as an additive term in the " +"Euclidean distance calculation:" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:69 +msgid "{r_i}=\\sqrt{{r_{ix}}^2 + {r_{iy}}^2 + s^2}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:73 +msgid "" +"where :math:`r_{ix}` and :math:`r_{iy}` are the horizontal and vertical " +"distances between the grid node to point :math:`i` respectively." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:76 +msgid "In this method the weighting factor :math:`w` is" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:78 +msgid "w=\\frac{1}{r^p}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:82 +msgid "" +"See :cpp:class:`GDALGridInverseDistanceToAPowerOptions` for the list of " +":cpp:func:`GDALGridCreate` parameters and :ref:`gdal_grid_invdist` for " +"the list of :ref:`gdal_grid` options." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:87 +msgid "Moving Average" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:89 +msgid "" +"The Moving Average is a simple data averaging algorithm. It uses a moving" +" window of elliptic form to search values and averages all data points " +"within the window. `Search Ellipse`_ can be rotated by specified angle, " +"the center of ellipse located at the grid node. Also the minimum number " +"of data points to average can be set. If there are not enough points in " +"window, the grid node is considered empty and will be filled with " +"specified NODATA value." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:97 +msgid "Mathematically it can be expressed with the formula:" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:99 +msgid "Z=\\frac{\\sum_{i=1}^n{Z_i}}{n}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:105 +#: ../../source/tutorials/gdal_grid_tut.rst:141 +#: ../../source/tutorials/gdal_grid_tut.rst:157 +#: ../../source/tutorials/gdal_grid_tut.rst:174 +msgid ":math:`Z` is a resulting value at the grid node," +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:107 +msgid ":math:`n` is a number of points in search `Search Ellipse`_." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:109 +msgid "" +"See :cpp:class:`GDALGridMovingAverageOptions` for the list of " +":cpp:func:`GDALGridCreate` parameters and :ref:`gdal_grid_average` for " +"the list of :ref:`gdal_grid` options." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:113 +msgid "Nearest Neighbor" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:115 +msgid "" +"The Nearest Neighbor method doesn't perform any interpolation or " +"smoothing, it just takes the value of nearest point found in the grid " +"node search ellipse and returns it as a result. If there are no points " +"found, the specified NODATA value will be returned." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:120 +msgid "" +"See :cpp:class:`GDALGridNearestNeighborOptions` for the list of " +":cpp:func:`GDALGridCreate` parameters and :ref:`gdal_grid_nearest` for " +"the list of :ref:`gdal_grid` options." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:124 +msgid "Data Metrics Computation" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:126 +msgid "" +"All the metrics have the same set controlling options. See the " +":cpp:class:`GDALGridDataMetricsOptions`." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:130 +msgid "Minimum Data Value" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:132 +msgid "" +"Minimum value found in grid node `Search Ellipse`_. If there are no " +"points found, the specified NODATA value will be returned." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:135 +msgid "Z=\\min{(Z_1,Z_2,\\ldots,Z_n)}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:146 +msgid "Maximum Data Value" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:148 +msgid "" +"Maximum value found in grid node `Search Ellipse`_. If there are no " +"points found, the specified NODATA value will be returned." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:151 +msgid "Z=\\max{(Z_1,Z_2,\\ldots,Z_n)}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:162 +msgid "Data Range" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:164 +msgid "" +"A difference between the minimum and maximum values found in grid `Search" +" Ellipse`_. If there are no points found, the specified NODATA value will" +" be returned." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:168 +msgid "Z=\\max{(Z_1,Z_2,\\ldots,Z_n)}-\\min{(Z_1,Z_2,\\ldots,Z_n)}" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:179 +msgid "Search Ellipse" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:181 +msgid "" +"Search window in gridding algorithms specified in the form of rotated " +"ellipse. It is described by the three parameters:" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:184 +msgid "" +":math:`radius_1` is the first radius (:math:`x` axis if rotation angle is" +" 0)," +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:185 +msgid "" +":math:`radius_2` is the second radius (:math:`y` axis if rotation angle " +"is 0)," +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:186 +msgid "" +":math:`angle` is a search ellipse rotation angle (rotated counter " +"clockwise)." +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:-1 +msgid "Search ellipse" +msgstr "" + +#: ../../source/tutorials/gdal_grid_tut.rst:198 +msgid "" +"Only points located inside the search ellipse (including its border line)" +" will be used for computation." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:5 +msgid "Geotransform Tutorial" +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:8 +msgid "Introduction to Geotransforms:" +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:9 +msgid "" +"A geotransform is an affine transformation from the image coordinate " +"space (row, column), also known as (pixel, line) to the georeferenced " +"coordinate space (projected or geographic coordinates)." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:13 +msgid "A geotransform consists in a set of 6 coefficients:" +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:15 +msgid "``GT(0)`` x-coordinate of the upper-left corner of the upper-left pixel." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:16 +msgid "``GT(1)`` w-e pixel resolution / pixel width." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:17 +msgid "``GT(2)`` row rotation (typically zero)." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:18 +msgid "``GT(3)`` y-coordinate of the upper-left corner of the upper-left pixel." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:19 +msgid "``GT(4)`` column rotation (typically zero)." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:20 +msgid "" +"``GT(5)`` n-s pixel resolution / pixel height (negative value for a " +"north-up image)." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:23 +msgid "" +"Transformation from image coordinate space to georeferenced coordinate " +"space:" +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:30 +msgid "" +"Note that the pixel/line coordinates in the above are from (0.0,0.0) at " +"the top left corner of the top left pixel to " +"(width_in_pixels,height_in_pixels) at the bottom right corner of the " +"bottom right pixel. The pixel/line location of the center of the top left" +" pixel would therefore be (0.5,0.5)." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:35 +msgid "In case of north up images:" +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:36 +msgid "``GT(2)``, ``GT(4)`` coefficients are zero." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:37 +msgid "``GT(1)``, ``GT(5)`` is the pixel size." +msgstr "" + +#: ../../source/tutorials/geotransforms_tut.rst:38 +msgid "" +"``GT(0)``, ``GT(3)`` position is the top left corner of the top left " +"pixel of the raster." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:5 +msgid "GNM API tutorial" +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:9 +msgid "" +"This document is intended to describe using the GNM C++ classes to work " +"with networks. It is advised to read the :ref:`gnm_data_model` before to " +"understand the purpose and structure of GNM classes." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:12 +msgid "Managing networks" +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:14 +msgid "" +"In the first example we will create a small water network on the base of " +"the set of spatial data (two shapefiles: pipes and wells which are " +"situated at the GDAL source tree: autotest\\\\gnm\\\\data). The use of " +"the common network format - :cpp:class:`GNMGdalNetwork` class - will " +"allow us to select one of the GDAL-supported vector formats for our " +"network - ESRI Shapefile. After the creation we will build a topology and" +" add some additional data: pumps layer, in order to manually edit network" +" topology." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:16 +msgid "" +"Initially we register GDAL drivers and create some options (string " +"pairs), which will be passed as parameters during network creation. Here " +"we create a network's name." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:33 +msgid "" +"Some options are obligatory. The following parameters must be specified " +"during the network creation: the path/name; format of network storage; " +"spatial reference system (EPSG, WKT, etc.). The according dataset with " +"the \"network part\" will be created and the resulting network will be " +"returned." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:43 +msgid "" +"For now we have a void network consisted of only \"system layers\". We " +"need to populate it with \"class layers\" full of features, so we open a " +"certain foreign dataset and copy layers from it to our network. Note, " +"that we use GDALDataset:: methods for working with \"class layers\", " +"because :cpp:class:`GNMNetwork` inherited from GDALDataset." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:58 +msgid "" +"After the successful copying we have the network full of features, but " +"with no topology. The features were added and registered in the network " +"but they are still not connected with each other. Now it is time to build" +" the network topology. There are two ways of doing this in GNM: manually " +"or automatically. In the most cases automatic building is more " +"convenient, while manual is useful for small editings. Automatic building" +" requires some parameters: we must specify which \"class layers\" will " +"participate in topology building (we select our two layers), a snap " +"tolerance, direct and inverse cost, direction, which is equal 0.00005 in " +"our case. If the building will be successful the network's graph will be " +"filled with the according connections." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:81 +msgid "" +"At this point we have a ready network with topological and spatial data, " +"which can be used now for different purposes (analysis, converting into " +"different formats, etc). But sometimes it is necessary to modify some " +"network's data. For example we need to add additional features and attach" +" them to our built topology (modify topology). We create a new \"class " +"layer\" in the network and add one feature to it." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:114 +msgid "" +"After the successful creation the feature will be registered in the " +"network and we can connect it with others. There can be two possible ways" +" to do this. In the first case we need a real feature which will be an " +"edge in the connection, while in the second case we do not need such " +"feature, and passing -1 into the " +":cpp:func:`GNMGenericNetwork::ConnectFeatures` method means that the " +"special system edge will be created for this connection and added to the " +"graph automatically. In our case we had added only one point feature and " +"we have not got the line one to be an edge, so we will use the " +"\"virtual\" connection. We pass the GFID of our point as the source, the " +"GFID of one of the existed features as the target and -1 as the " +"connector. Note that we also set the costs (direct and inverse) and the " +"direction of our edge manually and these values will be written to the " +"graph. When we used the automatic connection (which also uses " +"ConnectFeatures() internally) such vales were set automatically according" +" to the rule which we also set before." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:124 +msgid "" +"After all we correctly close the network which frees the allocated " +"resources." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:131 +#: ../../source/tutorials/gnm_api_tut.rst:299 +msgid "All in one block:" +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:237 +msgid "Analysing networks" +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:239 +msgid "" +"In the second example we will analyse the network which we have built in " +"the first example. We will calculate the shortest path between two points" +" via Dijkstra algorithm performing the feature blockings and saving the " +"resulting path into the file." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:241 +msgid "Initially we open our network, passing the path to its Shapefile dataset." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:259 +msgid "" +"Before any calculations we open the dataset which will hold the layer " +"with the resulting path." +msgstr "" + +#: ../../source/tutorials/gnm_api_tut.rst:275 +msgid "" +"Finally we use the Dijkstra shortest path method to calculations. This " +"path will be found passing over the blocked feature and saved into " +"internal memory OGRLayer, which we copy to the real dataset. Now it can " +"be visualized by GIS." +msgstr "" + +#: ../../source/tutorials/index.rst:5 +msgid "Tutorials" +msgstr "" + +#: ../../source/tutorials/index.rst:8 +msgid "Raster" +msgstr "" + +#: ../../source/tutorials/index.rst:20 +msgid "Multidimensional raster" +msgstr "" + +#: ../../source/tutorials/index.rst:28 +msgid "Vector" +msgstr "" + +#: ../../source/tutorials/index.rst:38 +msgid "Geographic Network Model" +msgstr "" + +#: ../../source/tutorials/index.rst:46 +msgid "" +"Projections and Spatial Reference Systems tutorial (OSR - " +"OGRSpatialReference)" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:5 +msgid "Multidimensional raster API tutorial" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:8 +msgid "Read the content of an array" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:11 +msgid "In C++" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:53 +msgid "In C" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:131 +msgid "In Python" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:141 +msgid "If NumPy is available:" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:153 +#: ../../source/tutorials/vector_python_driver.rst:631 +msgid "Other examples" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:155 +msgid "Test scripts from the GDAL autotest suite" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:157 +msgid "" +":ref:`MEM <raster.mem>` driver: " +":source_file:`autotest/gdrivers/memmultidim.py`" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:158 +msgid "" +":ref:`netCDF <raster.netcdf>` driver: " +":source_file:`autotest/gdrivers/netcdf_multidim.py`" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:159 +msgid "" +":ref:`HDF5 <raster.hdf5>` driver: " +":source_file:`autotest/gdrivers/hdf5multidim.py`" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:160 +msgid "" +":ref:`VRT <raster.vrt>` driver: " +":source_file:`autotest/gdrivers/vrtmultidim.py`" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:161 +msgid "" +":ref:`gdalmdiminfo` tests: " +":source_file:`autotest/utilities/test_gdalmdiminfo_lib.py`" +msgstr "" + +#: ../../source/tutorials/multidimensional_api_tut.rst:162 +msgid "" +":ref:`gdalmdimtranslate` tests: " +":source_file:`autotest/utilities/test_gdalmdimtranslate_lib.py`" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:5 +msgid "OGR Coordinate Reference Systems and Coordinate Transformation tutorial" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:16 +#: ../../source/tutorials/vector_python_driver.rst:12 +msgid "Introduction" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:18 +msgid "" +"The :cpp:class:`OGRSpatialReference` and " +":cpp:class:`OGRCoordinateTransformation` classes provide respectively " +"services to represent coordinate reference systems (known as CRS or SRS, " +"such as typically a projected CRS associating a map projection with a " +"geodetic datums) and to transform between them. These services are " +"loosely modeled on the OpenGIS Coordinate Transformations specification, " +"and rely on the Well Known Text (WKT) format (in its various versions: " +"OGC WKT 1, ESRI WKT, WKT2:2015 and WKT2:2018) for describing coordinate " +"systems." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:27 +msgid "References and applicable standards" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:29 +msgid "" +"`PROJ documentation <https://proj4.org>`_: projection methods and " +"coordinate operations" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:30 +msgid "" +"`ISO:19111 and WKT standards " +"<https://proj4.org/development/reference/cpp/cpp_general.html#standards>`_" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:31 +msgid "" +"`GeoTIFF Projections Transform List " +"<http://geotiff.maptools.org/proj_list>`_: understanding formulations of " +"projections in WKT for GeoTIFF" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:32 +msgid "`EPSG Geodesy web page <http://www.epsg.org>`_ is also a useful resource" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:35 +msgid "Defining a Geographic Coordinate Reference System" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:37 +msgid "" +"CRS are encapsulated in the :cpp:class:`OGRSpatialReference` class. There" +" are a number of ways of initializing an OGRSpatialReference object to a " +"valid coordinate reference system. There are two primary kinds of CRS. " +"The first is geographic (positions are measured in long/lat) and the " +"second is projected (such as UTM - positions are measured in meters or " +"feet)." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:43 +msgid "" +"A Geographic CRS contains information on the datum (which implies a " +"spheroid described by a semi-major axis, and inverse flattening), prime " +"meridian (normally Greenwich), and an angular units type which is " +"normally degrees. The following code initializes a geographic CRS on " +"supplying all this information along with a user visible name for the " +"geographic CRS." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:63 +msgid "" +"The abbreviation CS in :cpp:func:`OGRSpatialReference::SetGeogCS` is not " +"appropriate according to current geodesic terminology, and should be " +"understood as CRS" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:66 +msgid "" +"Of these values, the names \"My geographic CRS\", \"My WGS84 Spheroid\", " +"\"Greenwich\" and \"degree\" are not keys, but are used for display to " +"the user. However, the datum name \"World Geodetic System 1984\" is used" +" as a key to identify the datum, and should be set to a known value from " +"the EPSG registry, so that appropriate datum transformations can be done " +"during coordinate operations. The list of valid geodetic datum can be " +"seen in the 3rd column of the `geodetic_datum.sql " +"<https://github.com/OSGeo/PROJ/blob/master/data/sql/geodetic_datum.sql>`_" +" file." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:77 +msgid "" +"In WKT 1, space characters in datum names are normally replaced by " +"underscore. And WGS_1984 is used as an alias of \"World Geodetic System " +"1984\"" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:80 +msgid "" +"The OGRSpatialReference has built in support for a few well known CRS, " +"which include \"NAD27\", \"NAD83\", \"WGS72\" and \"WGS84\" which can be " +"defined in a single call to " +":cpp:func:`OGRSpatialReference::SetWellKnownGeogCS`." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:91 +msgid "" +"The abbreviation CS in SetWellKnownGeogCS() is not appropriate according " +"to current geodesic terminology, and should be understood as CRS" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:94 +msgid "" +"Furthermore, any geographic CRS in the EPSG database can be set by its " +"GCS code number if the EPSG database is available." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:101 +msgid "" +"For serialization, and transmission of projection definitions to other " +"packages, the OpenGIS Well Known Text format for coordinate systems is " +"used. An OGRSpatialReference can be initialized from WKT, or converted " +"back into WKT. As of GDAL 3.0, the default format for WKT export is still" +" OGC WKT 1." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:115 +msgid "outputs:" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:125 +msgid "or in more readable form:" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:142 +msgid "" +"Starting with GDAL 3.0, the :cpp:func:`OGRSpatialReference::exportToWkt` " +"method accepts options," +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:170 +msgid "" +"This method with options is available in C as the " +":cpp:func:`OSRExportToWktEx` function." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:172 +msgid "" +"The :cpp:func:`OGRSpatialReference::importFromWkt` method can be used to " +"set an OGRSpatialReference from a WKT CRS definition." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:176 +msgid "CRS and axis order" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:178 +msgid "" +"One \"detail\" that has been omitted in previous sections is the topic of" +" the order of coordinate axis in a CRS. A Geographic CRS is, according to" +" ISO:19111 modeling, made of two main components: a geodetic datum and a " +"`coordinate system " +"<http://docs.opengeospatial.org/as/18-005r4/18-005r4.html#42>`_. For 2D " +"geographic CRS, the coordinate system axes are the longitude and the " +"latitude, and the values along those axes are expressed generally in " +"degree (ancient French-based CRS may use grad)." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:185 +msgid "" +"The order in which they are specified, that is latitude first, longitude " +"second, or the reverse, is a constant matter of confusion and vary " +"depending on conventions used by geodetic authorities, GIS user, file " +"format and protocol specifications, etc. This is the source of various " +"interoperability issues." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:190 +msgid "" +"Before GDAL 3.0, the :cpp:class:`OGRSpatialReference` class did not " +"honour the axis order mandated by the authority defining a CRS and " +"consequently stripped axis order information from the WKT string when the" +" order was latitude first, longitude second. Coordinate transformations " +"using the OGRCoordinateTransformation class also assumed that geographic " +"coordinates passed or returned by the Transform() method of this class " +"used the longitude, latitude order." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:197 +msgid "" +"Starting with GDAL 3.0, the axis order mandated by the authority defining" +" a CRS is by default honoured by the OGRCoordinateTransformation class, " +"and always exported in WKT1. Consequently CRS created with the " +"\"EPSG:4326\" or \"WGS84\" strings use the latitude first, longitude " +"second axis order." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:202 +msgid "" +"In order to help migration from code bases still using coordinates with " +"the longitude, latitude order, it is possible to attach a metadata " +"information to a OGRSpatialReference instance, to specify that for the " +"purpose of coordinate transformations, the order of values effectively " +"passed or returned, will be longitude, latitude. For that, the following " +"must be called" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:212 +msgid "" +"The argument passed to " +":cpp:func:`OGRSpatialReference::SetAxisMappingStrategy` is the data axis " +"to CRS axis mapping strategy." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:215 +msgid "" +":c:macro:`OAMS_TRADITIONAL_GIS_ORDER` means that for geographic CRS with " +"lat/long order, the data will still be long/lat ordered. Similarly for a " +"projected CRS with northing/easting order, the data will still be " +"easting/northing ordered." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:216 +msgid "" +":c:macro:`OAMS_AUTHORITY_COMPLIANT` means that the data axis will be " +"identical to the CRS axis. This is the default value when instantiating " +"OGRSpatialReference." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:217 +msgid "" +":c:macro:`OAMS_CUSTOM` means that the data axes are customly defined with" +" SetDataAxisToSRSAxisMapping()." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:219 +msgid "" +"What has been discussed in this section for the particular case of " +"Geographic CRS also applies to Projected CRS. While most of them use " +"Easting first, Northing second convention, some defined in the EPSG " +"registry use the reverse convention." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:223 +msgid "" +"Another way to keep using the Traditional GIS order for some specific " +"well known CRS is to calling to " +":cpp:func:`OGRSpatialReference::SetWellKnownGeogCS` with \"CRS27\", " +"\"CRS83\" or \"CRS84\" instead of \"NAD27\", \"NAD83\" and \"WGS84\" " +"respectively." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:232 +msgid "Defining a Projected CRS" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:234 +msgid "" +"A projected CRS (such as UTM, Lambert Conformal Conic, etc.) requires and" +" underlying geographic CRS as well as a definition for the projection " +"transform used to translate between linear positions (in meters or feet) " +"and angular long/lat positions. The following code defines a UTM zone 17" +" projected CRS with an underlying geographic CRS (datum) of WGS84." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:249 +msgid "" +"Calling :cpp:func:`OGRSpatialReference::SetProjCS` sets a user name for " +"the projected CRS and establishes that the system is projected. The " +":cpp:func:`OGRSpatialReference::SetWellKnownGeogCS` associates a " +"geographic coordinate system, and the " +":cpp:func:`OGRSpatialReference::SetUTM` call sets detailed projection " +"transformation parameters. At this time the above order is important in " +"order to create a valid definition, but in the future the object will " +"automatically reorder the internal representation as needed to remain " +"valid." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:259 +msgid "For now, be careful of the order of steps defining an OGRSpatialReference!" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:261 +msgid "" +"The above definition would give a WKT version that looks something like " +"the following. Note that the UTM 17 was expanded into the details " +"transverse mercator definition of the UTM zone." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:286 +msgid "" +"There are methods for many projection methods including " +":cpp:func:`OGRSpatialReference::SetTM` (Transverse Mercator), " +":cpp:func:`OGRSpatialReference::SetLCC` (Lambert Conformal Conic), and " +":cpp:func:`OGRSpatialReference::SetMercator`." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:290 +msgid "Querying Coordinate Reference System" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:292 +msgid "" +"Once an OGRSpatialReference has been established, various information " +"about it can be queried. It can be established if it is a projected or " +"geographic CRS using the :cpp:func:`OGRSpatialReference::IsProjected` and" +" :cpp:func:`OGRSpatialReference::IsGeographic` methods. The " +":cpp:func:`OGRSpatialReference::GetSemiMajor`, " +":cpp:func:`OGRSpatialReference::GetSemiMinor` and " +":cpp:func:`OGRSpatialReference::GetInvFlattening` methods can be used to " +"get information about the spheroid. The " +":cpp:func:`OGRSpatialReference::GetAttrValue` method can be used to get " +"the PROJCS, GEOGCS, DATUM, SPHEROID, and PROJECTION names strings. The " +":cpp:func:`OGRSpatialReference::GetProjParm` method can be used to get " +"the projection parameters. The " +":cpp:func:`OGRSpatialReference::GetLinearUnits` method can be used to " +"fetch the linear units type, and translation to meters." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:303 +msgid "" +"Note that the names of the projection method and parameters is the one of" +" WKT 1." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:306 +msgid "" +"The following code demonstrates use of " +":cpp:func:`OGRSpatialReference::GetAttrValue` to get the projection, and " +":cpp:func:`OGRSpatialReference::GetProjParm` to get projection " +"parameters. The GetAttrValue() method searches for the first \"value\" " +"node associated with the named entry in the WKT text representation. The " +"#define'ed constants for projection parameters (such as " +"SRS_PP_CENTRAL_MERIDIAN) should be used when fetching projection " +"parameter with GetProjParm(). The code for the Set methods of the various" +" projections in ogrspatialreference.cpp can be consulted to find which " +"parameters apply to which projections." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:340 +msgid "Coordinate Transformation" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:342 +msgid "" +"The :cpp:class:`OGRCoordinateTransformation` class is used for " +"translating positions between different CRS. New transformation objects " +"are created using :cpp:func:`OGRCreateCoordinateTransformation`, and then" +" the :cpp:func:`OGRCoordinateTransformation::Transform` method can be " +"used to convert points between CRS." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:373 +msgid "" +"There are a couple of points at which transformations can fail. First, " +"OGRCreateCoordinateTransformation() may fail, generally because the " +"internals recognize that no transformation between the indicated systems " +"can be established, and will return a NULL pointer." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:379 +msgid "" +"The OGRCoordinateTransformation::Transform() method itself can also fail." +" This may be as a delayed result of one of the above problems, or as a " +"result of an operation being numerically undefined for one or more of the" +" passed in points. The Transform() function will return TRUE on success," +" or FALSE if any of the points fail to transform. The point array is " +"left in an indeterminate state on error." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:387 +msgid "" +"Though not shown above, the coordinate transformation service can take 3D" +" points, and will adjust elevations for elevation differences in " +"spheroids, and datums. Elevations given on a geographic or projected CRS " +"are assumed to be ellipsoidal heights. When using a compound CRS made of " +"a horizontal CRS (geographic or projected) and a vertical CRS, elevations" +" will be related to a vertical datum (mean sea level, gravity based, " +"etc.)." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:394 +msgid "" +"Starting with GDAL 3.0, a time value (generally as a value in decimal " +"years) can also be specified for time-dependent coordinate operations." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:397 +msgid "" +"The following example shows how to conveniently create a long/lat " +"coordinate system using the same geographic CRS as a projected coordinate" +" system, and using that to transform between projected coordinates and " +"long/lat. The returned coordinates will be in longitude, latitude order " +"due to the call to SetAxisMappingStrategy(OAMS_TRADITIONAL_GIS_ORDER)" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:427 +msgid "Advanced Coordinate Transformation" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:429 +msgid "" +"OGRCreateCoordinateTransformation() under-the-hood may determine several " +"candidate coordinate operations transforming from the source CRS to the " +"target CRS. Those candidate coordinate operations each have their own " +"area of use. When Transform() is invoked, it will determine the most " +"appropriate coordinate operation based on the coordinates of the point to" +" transform and area of use. For example, there are several dozens of " +"possible coordinate operations for the NAD27 to WGS84 transformation." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:437 +msgid "" +"If a bounding box of the area of interest into which coordinates to " +"transform are located is known, it is possible to specify it to restrict " +"the candidate coordinate operations to consider:" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:447 +msgid "" +"For cases where a particular coordinate operation must be used, it is " +"possible to specify it as as a PROJ string (single step operation or " +"multiple step string starting with +proj=pipeline), a WKT2 string " +"describing a CoordinateOperation, or a " +"urn:ogc:def:coordinateOperation:EPSG::XXXX URN" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:473 +msgid "Alternate Interfaces" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:475 +msgid "" +"A C interface to the coordinate system services is defined in " +"ogr_srs_api.h, and Python bindings are available via the osr.py module. " +"Methods are close analogs of the C++ methods but C and Python bindings " +"are missing for some C++ methods." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:481 +msgid "C bindings" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:577 +msgid "Python bindings" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:604 +msgid "History and implementation considerations" +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:606 +msgid "" +"Before GDAL 3.0, the OGRSpatialReference class was strongly tied to OGC " +"WKT (WKT 1) format specified by `Coordinate Transformation Services (CT) " +"specification (01-009) " +"<http://portal.opengeospatial.org/files/?artifact_id=999>`_, and the way " +"it was interpreted by GDAL, which various caveats detailed in the " +":ref:`wktproblems` page. The class mostly contained an in-memory tree-" +"like representation of WKT 1 strings. The class used to directly " +"implement import and export to OGC WKT 1, WKT-ESRI and PROJ.4 formats. " +"Reprojection services were only available if GDAL had been build against " +"the PROJ library." +msgstr "" + +#: ../../source/tutorials/osr_api_tut.rst:616 +msgid "" +"Starting with GDAL 3.0, the `PROJ <https://proj4.org>`_ >= 6.0 library " +"has become a required dependency of GDAL. PROJ 6 has built-in support for" +" OGC WKT 1, ESRI WKT, OGC WKT 2:2015 and OGC WKT 2:2018 representations. " +"PROJ 6 also implements a C++ object class hierarchy of the ISO-19111 / " +"OGC Abstract Topic 2 \"Referencing by coordinate\" standard. Consequently" +" the OGRSpatialReference class has been modified to act mostly as a " +"wrapper on top of PROJ PJ* CRS objects, and tries to abstract away from " +"the OGC WKT 1 representation as much as possible. However, for backward " +"compatibility, some methods still expect arguments or return values that " +"are specific of OGC WKT 1. The design of th OGRSpatialReference class is " +"also still monolithic. Users wanting direct and fine grained access to " +"CRS representations might want to directly use the PROJ 6 C or C++ API." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:5 +msgid "Raster API tutorial" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:8 +msgid "Opening the File" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:10 +msgid "" +"Before opening a GDAL supported raster datastore it is necessary to " +"register drivers. There is a driver for each supported format. Normally " +"this is accomplished with the :cpp:func:`GDALAllRegister` function which " +"attempts to register all known drivers, including those auto-loaded from " +".so files using :cpp:func:`GDALDriverManager::AutoLoadDrivers`. If for " +"some applications it is necessary to limit the set of drivers it may be " +"helpful to review the code from gdalallregister.cpp. Python automatically" +" calls GDALAllRegister() when the gdal module is imported." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:12 +msgid "" +"Once the drivers are registered, the application should call the free " +"standing :cpp:func:`GDALOpen` function to open a dataset, passing the " +"name of the dataset and the access desired (GA_ReadOnly or GA_Update)." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:14 +#: ../../source/tutorials/raster_api_tut.rst:98 +#: ../../source/tutorials/raster_api_tut.rst:163 +#: ../../source/tutorials/raster_api_tut.rst:241 +#: ../../source/tutorials/raster_api_tut.rst:314 +#: ../../source/tutorials/raster_api_tut.rst:369 +#: ../../source/tutorials/raster_api_tut.rst:410 +#: ../../source/tutorials/raster_api_tut.rst:458 +#: ../../source/tutorials/raster_api_tut.rst:485 +#: ../../source/tutorials/vector_api_tut.rst:1160 +msgid "In C++:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:40 +#: ../../source/tutorials/raster_api_tut.rst:119 +#: ../../source/tutorials/raster_api_tut.rst:190 +#: ../../source/tutorials/raster_api_tut.rst:254 +#: ../../source/tutorials/raster_api_tut.rst:332 +#: ../../source/tutorials/raster_api_tut.rst:383 +#: ../../source/tutorials/raster_api_tut.rst:426 +#: ../../source/tutorials/raster_api_tut.rst:467 +#: ../../source/tutorials/raster_api_tut.rst:506 +#: ../../source/tutorials/vector_api_tut.rst:1175 +msgid "In C:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:67 +#: ../../source/tutorials/raster_api_tut.rst:143 +#: ../../source/tutorials/raster_api_tut.rst:217 +#: ../../source/tutorials/raster_api_tut.rst:267 +#: ../../source/tutorials/raster_api_tut.rst:349 +#: ../../source/tutorials/raster_api_tut.rst:396 +#: ../../source/tutorials/raster_api_tut.rst:442 +#: ../../source/tutorials/raster_api_tut.rst:476 +#: ../../source/tutorials/raster_api_tut.rst:529 +#: ../../source/tutorials/vector_api_tut.rst:390 +#: ../../source/tutorials/vector_api_tut.rst:700 +msgid "In Python:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:76 +msgid "" +"Note that if :cpp:func:`GDALOpen` returns NULL it means the open failed, " +"and that an error messages will already have been emitted via " +":cpp:func:`CPLError`. If you want to control how errors are reported to " +"the user review the :cpp:func:`CPLError` documentation. Generally " +"speaking all of GDAL uses :cpp:func:`CPLError` for error reporting. Also," +" note that pszFilename need not actually be the name of a physical file " +"(though it usually is). It's interpretation is driver dependent, and it " +"might be an URL, a filename with additional parameters added at the end " +"controlling the open or almost anything. Please try not to limit GDAL " +"file selection dialogs to only selecting physical files." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:79 +msgid "Getting Dataset Information" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:81 +msgid "" +"As described in the :ref:`raster_data_model`, a :cpp:class:`GDALDataset` " +"contains a list of raster bands, all pertaining to the same area, and " +"having the same resolution. It also has metadata, a coordinate system, a " +"georeferencing transform, size of raster and various other information." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:83 +msgid "" +"In the particular, but common, case of a \"north up\" image without any " +"rotation or shearing, the georeferencing transform " +":ref:`geotransforms_tut` takes the following form :" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:94 +msgid "In the general case, this is an affine transform." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:96 +msgid "" +"If we wanted to print some general information about the dataset we might" +" do the following:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:159 +msgid "Fetching a Raster Band" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:161 +msgid "" +"At this time access to raster data via GDAL is done one band at a time. " +"Also, there is metadata, block sizes, color tables, and various other " +"information available on a band by band basis. The following codes " +"fetches a :cpp:class:`GDALRasterBand` object from the dataset (numbered 1" +" through :cpp:func:`GDALRasterBand::GetRasterCount`) and displays a " +"little information about it." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:237 +msgid "Reading Raster Data" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:239 +msgid "" +"There are a few ways to read raster data, but the most common is via the " +":cpp:func:`GDALRasterBand::RasterIO` method. This method will " +"automatically take care of data type conversion, up/down sampling and " +"windowing. The following code will read the first scanline of data into a" +" similarly sized buffer, converting it to floating point as part of the " +"operation." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:252 +#: ../../source/tutorials/raster_api_tut.rst:265 +msgid "" +"The pafScanline buffer should be freed with CPLFree() when it is no " +"longer used." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:276 +msgid "" +"Note that the returned scanline is of type string, and contains xsize*4 " +"bytes of raw binary floating point data. This can be converted to Python " +"values using the struct module from the standard library:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:283 +msgid "The RasterIO call takes the following arguments." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:294 +msgid "" +"Note that the same RasterIO() call is used to read, or write based on the" +" setting of eRWFlag (either GF_Read or GF_Write). The nXOff, nYOff, " +"nXSize, nYSize argument describe the window of raster data on disk to " +"read (or write). It doesn't have to fall on tile boundaries though access" +" may be more efficient if it does." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:296 +msgid "" +"The pData is the memory buffer the data is read into, or written from. " +"It's real type must be whatever is passed as eBufType, such as " +"GDT_Float32, or GDT_Byte. The RasterIO() call will take care of " +"converting between the buffer's data type and the data type of the band. " +"Note that when converting floating point data to integer RasterIO() " +"rounds down, and when converting source values outside the legal range of" +" the output the nearest legal value is used. This implies, for instance, " +"that 16bit data read into a GDT_Byte buffer will map all values greater " +"than 255 to 255, the data is not scaled!" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:298 +msgid "" +"The nBufXSize and nBufYSize values describe the size of the buffer. When " +"loading data at full resolution this would be the same as the window " +"size. However, to load a reduced resolution overview this could be set to" +" smaller than the window on disk. In this case the RasterIO() will " +"utilize overviews to do the IO more efficiently if the overviews are " +"suitable." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:300 +msgid "" +"The nPixelSpace, and nLineSpace are normally zero indicating that default" +" values should be used. However, they can be used to control access to " +"the memory data buffer, allowing reading into a buffer containing other " +"pixel interleaved data for instance." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:303 +msgid "Closing the Dataset" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:305 +msgid "" +"Please keep in mind that :cpp:class:`GDALRasterBand` objects are owned by" +" their dataset, and they should never be destroyed with the C++ delete " +"operator. :cpp:class:`GDALDataset`'s can be closed by calling " +":cpp:func:`GDALClose` (it is NOT recommended to use the delete operator " +"on a GDALDataset for Windows users because of known issues when " +"allocating and freeing memory across module boundaries. See the relevant " +"topic on the FAQ). Calling GDALClose will result in proper cleanup, and " +"flushing of any pending writes. Forgetting to call GDALClose on a dataset" +" opened in update mode in a popular format like GTiff will likely result " +"in being unable to open it afterwards." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:308 +msgid "Techniques for Creating Files" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:310 +msgid "" +"New files in GDAL supported formats may be created if the format driver " +"supports creation. There are two general techniques for creating files, " +"using CreateCopy() and Create(). The CreateCopy method involves calling " +"the CreateCopy() method on the format driver, and passing in a source " +"dataset that should be copied. The Create method involves calling the " +"Create() method on the driver, and then explicitly writing all the " +"metadata, and raster data with separate calls. All drivers that support " +"creating new files support the CreateCopy() method, but only a few " +"support the Create() method." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:312 +msgid "" +"To determine if a particular format supports Create or CreateCopy it is " +"possible to check the DCAP_CREATE and DCAP_CREATECOPY metadata on the " +"format driver object. Ensure that :cpp:func:`GDALAllRegister` has been " +"called before calling :cpp:func:`GDALDriverManager::GetDriverByName`. In " +"this example we fetch a driver, and determine whether it supports " +"Create() and/or CreateCopy()." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:362 +msgid "" +"Note that a number of drivers are read-only and won't support Create() or" +" CreateCopy()." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:365 +msgid "Using CreateCopy()" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:367 +msgid "" +"The :cpp:func:`GDALDriver::CreateCopy` method can be used fairly simply " +"as most information is collected from the source dataset. However, it " +"includes options for passing format specific creation options, and for " +"reporting progress to the user as a long dataset copy takes place. A " +"simple copy from the a file named pszSrcFilename, to a new file named " +"pszDstFilename using default options on a format whose driver was " +"previously fetched might look like this:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:406 +msgid "" +"Note that the CreateCopy() method returns a writable dataset, and that it" +" must be closed properly to complete writing and flushing the dataset to " +"disk. In the Python case this occurs automatically when \"dst_ds\" goes " +"out of scope. The FALSE (or 0) value used for the bStrict option just " +"after the destination filename in the CreateCopy() call indicates that " +"the CreateCopy() call should proceed without a fatal error even if the " +"destination dataset cannot be created to exactly match the input dataset." +" This might be because the output format does not support the pixel " +"datatype of the input dataset, or because the destination cannot support " +"writing georeferencing for instance." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:408 +msgid "" +"A more complex case might involve passing creation options, and using a " +"predefined progress monitor like this:" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:454 +msgid "Using Create()" +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:456 +msgid "" +"For situations in which you are not just exporting an existing file to a " +"new file, it is generally necessary to use the " +":cpp:func:`GDALDriver::Create` method (though some interesting options " +"are possible through use of virtual files or in-memory files). The " +"Create() method takes an options list much like CreateCopy(), but the " +"image size, number of bands and band type must be provided explicitly." +msgstr "" + +#: ../../source/tutorials/raster_api_tut.rst:483 +msgid "" +"Once the dataset is successfully created, all appropriate metadata and " +"raster data must be written to the file. What this is will vary according" +" to usage, but a simple case with a projection, geotransform and raster " +"data is covered here." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:5 +msgid "Raster driver implementation tutorial" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:10 +#: ../../source/tutorials/vector_driver_tut.rst:10 +msgid "Overall Approach" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:12 +msgid "" +"In general new formats are added to GDAL by implementing format specific " +"drivers as subclasses of :cpp:class:`GDALDataset`, and band accessors as " +"subclasses of :cpp:class:`GDALRasterBand`. As well, a " +":cpp:class:`GDALDriver` instance is created for the format, and " +"registered with the :cpp:class:`GDALDriverManager`, to ensure that the " +"system knows about the format." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:14 +msgid "" +"This tutorial will start with implementing a simple read-only driver " +"(based on the JDEM driver), and then proceed to utilizing the " +"RawRasterBand helper class, implementing creatable and updatable formats," +" and some esoteric issues." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:16 +msgid "" +"It is strongly advised that the :ref:`raster_data_model` be reviewed and " +"understood before attempting to implement a GDAL driver." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:19 +msgid "Implementing the Dataset" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:21 +msgid "" +"We will start showing minimal implementation of a read-only driver for " +"the Japanese DEM format (:source_file:`frmts/jdem/jdemdataset.cpp`). " +"First we declare a format specific dataset class, JDEMDataset in this " +"case." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:44 +msgid "" +"In general we provide capabilities for a driver, by overriding the " +"various virtual methods on the GDALDataset base class. However, the " +"Open() method is special. This is not a virtual method on the base class," +" and we will need a freestanding function for this operation, so we " +"declare it static. Implementing it as a method in the JDEMDataset class " +"is convenient because we have privileged access to modify the contents of" +" the database object." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:46 +msgid "The open method itself may look something like this:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:102 +msgid "" +"The first step in any database Open function is to verify that the file " +"being passed is in fact of the type this driver is for. It is important " +"to realize that each driver's Open function is called in turn till one " +"succeeds. Drivers must quietly return nullptr if the passed file is not " +"of their format. They should only produce an error if the file does " +"appear to be of their supported format, but is for some reason " +"unsupported or corrupt. The information on the file to be opened is " +"passed in contained in a GDALOpenInfo object. The GDALOpenInfo includes " +"the following public data members:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:124 +msgid "" +"The driver can inspect these to establish if the file is supported. If " +"the `pszFilename` refers to an object in the file system, the `bStatOK` " +"flag will be set to TRUE. As well, if the file was successfully opened, " +"the first kilobyte or so is read in, and put in pabyHeader, with the " +"exact size in `nHeaderBytes`." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:126 +msgid "" +"In this typical testing example it is verified that the file was " +"successfully opened, that we have at least enough header information to " +"perform our test, and that various parts of the header are as expected " +"for this format. In this case, there are no magic numbers for JDEM format" +" so we check various date fields to ensure they have reasonable century " +"values. If the test fails, we quietly return NULL indicating this file " +"isn't of our supported format." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:128 +msgid "The identification is in fact delegated to a Identify() static function :" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:173 +msgid "" +"It is important to make the \"is this my format\" test as stringent as " +"possible. In this particular case, we check that dates are in the 19th " +"or 20th centry, but as this might also be too weak, we check that the " +"geospatial extent is consistent, and valid for Japan. Once we are " +"satisfied that the file is of our format, we can do any other tests that " +"are necessary to validate the file is usable, and in particular that we " +"can provide the level of access desired. Since the JDEM driver does not " +"provide update support, error out in that case." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:192 +msgid "" +"Next we need to create an instance of the database class in which we will" +" set various information of interest. We create it as a " +"std::unique_ptr<JDEMDataset> with the cpl::make_unique<> utility " +"(equivalent to std::make_unique<> available in C++14 and later), to make " +"memory management easier in error code paths." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:209 +msgid "" +"At this point we \"borrow\" the file handle that was held by " +"GDALOpenInfo* (we did make sure that poDS->m_fp is initialized to nullptr" +" in the inline member definition). This file pointer uses the VSI*L GDAL " +"API to access files on disk. This virtualized POSIX-style API allows some" +" special capabilities like supporting large files, in-memory files and " +"zipped files." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:213 +msgid "" +"Next the X and Y size are extracted from the header. The `nRasterXSize` " +"and `nRasterYSize` are data fields inherited from the GDALDataset base " +"class, and must be set by the Open() method." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:230 +msgid "" +"All the bands related to this dataset must be created and attached using " +"the SetBand() method. We will explore the JDEMRasterBand() class shortly." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:237 +msgid "" +"Finally we assign a name to the dataset object, and call the " +"GDALPamDataset TryLoadXML() method which can initialize auxiliary " +"information from an .aux.xml file if available. We also initialize for " +"external overviews (in a .ovr side car file). For more details on these " +"services review the GDALPamDataset and related classes." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:253 +msgid "Implementing the RasterBand" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:255 +msgid "" +"Similar to the customized JDEMDataset class subclassed from GDALDataset, " +"we also need to declare and implement a customized JDEMRasterBand derived" +" from :cpp:class:`GDALRasterBand` for access to the band(s) of the JDEM " +"file. For JDEMRasterBand the declaration looks like this:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:275 +msgid "" +"The constructor may have any signature, and is only called from the " +"Open() method. Other virtual methods, such as " +":cpp:func:`GDALRasterBand::IReadBlock` must be exactly matched to the " +"method signature in gdal_priv.h." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:277 +msgid "The constructor implementation looks like this:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:294 +msgid "" +"The following data members are inherited from GDALRasterBand, and should " +"generally be set in the band constructor." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:304 +msgid "" +"The full set of possible GDALDataType values are declared in gdal.h, and " +"include GDT_Byte, GDT_UInt16, GDT_Int16, and GDT_Float32. The block size " +"is used to establish a natural or efficient block size to access the data" +" with. For tiled datasets this will be the size of a tile, while for most" +" other datasets it will be one scanline, as in this case." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:306 +msgid "" +"Next we see the implementation of the code that actually reads the image " +"data, IReadBlock()." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:363 +msgid "Key items to note are:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:365 +msgid "" +"It is typical to cast the GDALRasterBand::poDS member to the derived type" +" of the owning dataset. If your RasterBand class will need privileged " +"access to the owning dataset object, ensure it is declared as a friend " +"(omitted above for brevity)." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:366 +msgid "" +"If an error occurs, report it with CPLError(), and return CE_Failure. " +"Otherwise return CE_None." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:367 +msgid "" +"The pImage buffer should be filled with one block of data. The block is " +"the size declared in nBlockXSize and nBlockYSize for the raster band. The" +" type of the data within pImage should match the type declared in " +"eDataType in the raster band object." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:368 +msgid "" +"The nBlockXOff and nBlockYOff are block offsets, so with 128x128 tiled " +"datasets values of 1 and 1 would indicate the block going from (128,128) " +"to (255,255) should be loaded." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:371 +msgid "The Driver" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:373 +msgid "" +"While the JDEMDataset and JDEMRasterBand are now ready to use to read " +"image data, it still isn't clear how the GDAL system knows about the new " +"driver. This is accomplished via the :cpp:class:`GDALDriverManager`. To " +"register our format we implement a registration function. The declaration" +" goes in gcore/gdal_frmts.h: void CPL_DLL GDALRegister_JDEM(void);" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:376 +msgid "The definition in the driver file is:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:405 +msgid "" +"Note the use of GDAL_CHECK_VERSION macro. This is a macro that should be " +"used by drivers that can be built as a plugin. As the GDAL C++ ABI may, " +"and will, change between GDAL feature releases (for example from GDAL " +"3.x.0 to 3.y.0), it is necessary to recompile your driver against the " +"header files of the GDAL feature version with which you want to make it " +"work. The GDAL_CHECK_VERSION macro will check that the GDAL version with " +"which the driver was compiled and the version against which it is running" +" are compatible (checking that the major and minor version numbers are " +"equal). The C++ ABI will however remain stable for releases of the same " +"release branch (that is for bug fixes releases x.y.z of a given feature " +"release x.y.0)." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:407 +msgid "" +"The registration function will create an instance of a GDALDriver object " +"when first called, and register it with the GDALDriverManager. The " +"following fields can be set in the driver before registering it with the " +"GDALDriverManager." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:409 +msgid "" +"The description is the short name for the format. This is a unique name " +"for this format, often used to identity the driver in scripts and command" +" line programs. Normally 3-5 characters in length, and matching the " +"prefix of the format classes. (mandatory)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:410 +msgid "" +"GDAL_DCAP_RASTER: set to YES to indicate that this driver handles raster " +"data. (mandatory)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:411 +msgid "" +"GDAL_DMD_LONGNAME: A longer descriptive name for the file format, but " +"still no longer than 50-60 characters. (mandatory)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:412 +msgid "" +"GDAL_DMD_HELPTOPIC: The name of a help topic to display for this driver, " +"if any. In this case JDEM format is contained within the various format " +"web page held in gdal/html. (optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:413 +msgid "" +"GDAL_DMD_EXTENSIONS: The extensions used for files of this type, without " +"the leading '.'. If more than one, they should be separated with space. " +"(optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:414 +msgid "" +"GDAL_DMD_MIMETYPE: The standard mime type for this file format, such as " +"\"image/png\". (optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:415 +msgid "" +"GDAL_DMD_CREATIONOPTIONLIST: There is evolving work on mechanisms to " +"describe creation options. See the geotiff driver for an example of this." +" (optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:416 +msgid "" +"GDAL_DMD_CREATIONDATATYPES: A list of space separated data types " +"supported by this create when creating new datasets. If a Create() method" +" exists, these will be will supported. If a CreateCopy() method exists, " +"this will be a list of types that can be losslessly exported but it may " +"include weaker data types than the type eventually written. For instance," +" a format with a CreateCopy() method, and that always writes Float32 " +"might also list Byte, Int16, and UInt16 since they can losslessly " +"translated to Float32. An example value might be \"Byte Int16 UInt16\". " +"(required - if creation supported)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:417 +msgid "" +"GDAL_DCAP_VIRTUALIO: set to YES to indicate that this driver can deal " +"with files opened with the VSI*L GDAL API. Otherwise this metadata item " +"should not be defined. (optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:418 +msgid "" +"pfnOpen: The function to call to try opening files of this format. " +"(optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:419 +msgid "" +"pfnIdentify: The function to call to try identifying files of this " +"format. A driver should return 1 if it recognizes the file as being of " +"its format, 0 if it recognizes the file as being NOT of its format, or -1" +" if it cannot reach to a firm conclusion by just examining the header " +"bytes. (optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:420 +msgid "" +"pfnCreate: The function to call to create new updatable datasets of this " +"format. (optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:421 +msgid "" +"pfnCreateCopy: The function to call to create a new dataset of this " +"format copied from another source, but not necessary updatable. " +"(optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:422 +msgid "" +"pfnDelete: The function to call to delete a dataset of this format. " +"(optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:423 +msgid "" +"pfnUnloadDriver: A function called only when the driver is destroyed. " +"Could be used to cleanup data at the driver level. Rarely used. " +"(optional)" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:425 +#: ../../source/tutorials/vector_driver_tut.rst:66 +msgid "" +"For a driver that can be built as a plugin (that is to say a standalone " +"shared object, loaded at runtime by GDAL), since GDAL 3.9 and " +":ref:`rfc-96`, there is a way to implement the driver in a way where the " +"plugin will be loaded only when necessary, and not immediately at " +":cpp:func:`GDALAllRegister` time. Consult :ref:`rfc96_example_driver` for" +" the changes needed to make the driver compatible of deferred plugin " +"loading." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:428 +msgid "Adding Driver to GDAL Tree" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:430 +msgid "" +"Note that the GDALRegister_JDEM() method must be called by the higher " +"level program in order to have access to the JDEM driver. Normal practice" +" when writing new drivers is to:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:432 +msgid "" +"Add a driver directory under frmts, with the directory name the same as " +"the short name." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:433 +msgid "" +"Add a CMakeLists.txt in that directory modeled on those from other " +"similar directories (i.e. the jdem directory)." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:434 +msgid "" +"Reference the new driver in frmts/CMakeLists.txt, using the " +"gdal_optional_format() or gdal_dependent_format() functions depending if " +"it requires no external dependency or it has at least one." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:435 +msgid "" +"Add the module with the dataset, and rasterband implementation. Generally" +" this is called <short_name>dataset.cpp, with all the GDAL specific code " +"in one file, though that is not required." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:436 +msgid "" +"Add the registration entry point declaration (i.e. GDALRegister_JDEM()) " +"to gcore/gdal_frmts.h." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:437 +msgid "" +"Add a call to the registration function to frmts/gdalallregister.cpp, " +"protected by an appropriate #ifdef." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:439 +msgid "" +"Once this is all done, it should be possible to rebuild GDAL, and have " +"the new format available in all the utilities. The :ref:`gdalinfo` " +"utility can be used to test that opening and reporting on the format is " +"working, and the :ref:`gdal_translate` utility can be used to test image " +"reading." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:442 +msgid "Adding Georeferencing" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:444 +msgid "" +"Now we will take the example a step forward, adding georeferencing " +"support. We add the following two virtual method overrides to " +"JDEMDataset, taking care to exactly match the signature of the method on " +"the GDALDataset base class." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:451 +msgid "" +"The implementation of :cpp:func:`GDALDataset::GetGeoTransform` just " +"copies the usual geotransform matrix into the supplied buffer. Note that " +":cpp:func:`GDALDataset::GetGeoTransform` may be called a lot, so it isn't" +" generally wise to do a lot of computation in it. In many cases the " +"Open() will collect the geotransform, and this method will just copy it " +"over. Also note that the geotransform return is based on an anchor point " +"at the top left corner of the top left pixel, not the center of pixel " +"approach used in some packages." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:475 +msgid "" +"The :cpp:func:`GDALDataset::GetSpatialRef` method returns a pointer to an" +" internal OGRSpatialReference object." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:484 +msgid "" +"In this case the coordinate system is fixed for all files of this format," +" and has been initialized in the JDEMDataset constructor. But in more " +"complex cases, a definition may need to be composed on the fly, in which " +"case it may be helpful to use the :cpp:class:`OGRSpatialReference` class " +"to help build the definition." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:498 +msgid "" +"This completes explanation of the features of the JDEM driver. The full " +"source for jdemdataset.cpp can be reviewed as needed." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:501 +msgid "Overviews" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:503 +msgid "" +"GDAL allows file formats to make pre-built overviews available to " +"applications via the :cpp:func:`GDALRasterBand::GetOverview` and related " +"methods. However, implementing this is pretty involved, and goes beyond " +"the scope of this document for now. The GeoTIFF driver " +"(gdal/frmts/gtiff/geotiff.cpp) and related source can be reviewed for an " +"example of a file format implementing overview reporting and creation " +"support." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:505 +msgid "" +"Formats can also report that they have arbitrary overviews, by overriding" +" the :cpp:func:`GDALRasterBand::HasArbitraryOverviews` method on the " +"GDALRasterBand, returning TRUE. In this case the raster band object is " +"expected to override the :cpp:func:`GDALRasterBand::RasterIO` method " +"itself, to implement efficient access to imagery with resampling. This is" +" also involved, and there are a lot of requirements for correct " +"implementation of the RasterIO() method. An example of this can be found " +"in the OGDI and ECW formats." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:507 +msgid "" +"However, by far the most common approach to implementing overviews is to " +"use the default support in GDAL for external overviews stored in TIFF " +"files with the same name as the dataset, but the extension .ovr appended." +" In order to enable reading and creation of this style of overviews it is" +" necessary for the GDALDataset to initialize the `oOvManager` object " +"within itself. This is typically accomplished with a call like the " +"following near the end of the Open() method (after the PAM " +":cpp:func:`GDALDataset::TryLoadXML`)." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:513 +msgid "" +"This will enable default implementations for reading and creating " +"overviews for the format. It is advised that this be enabled for all " +"simple file system based formats unless there is a custom overview " +"mechanism to be tied into." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:516 +msgid "File Creation" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:518 +msgid "" +"There are two approaches to file creation. The first method is called the" +" :cpp:func:`GDALDriver::CreateCopy` method, and involves implementing a " +"function that can write a file in the output format, pulling all imagery " +"and other information needed from a source GDALDataset. The second " +"method, the dynamic creation method, involves implementing a Create " +"method to create the shell of the file, and then the application writes " +"various information by calls to set methods." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:520 +msgid "" +"The benefits of the first method are that that all the information is " +"available at the point the output file is being created. This can be " +"especially important when implementing file formats using external " +"libraries which require information like color maps, and georeferencing " +"information at the point the file is created. The other advantage of this" +" method is that the CreateCopy() method can read some kinds of " +"information, such as min/max, scaling, description and GCPs for which " +"there are no equivalent set methods." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:522 +msgid "" +"The benefits of the second method are that applications can create an " +"empty new file, and write results to it as they become available. A " +"complete image of the desired data does not have to be available in " +"advance." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:524 +msgid "" +"For very important formats both methods may be implemented, otherwise do " +"whichever is simpler, or provides the required capabilities." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:527 +msgid "CreateCopy" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:529 +msgid "" +"The GDALDriver::CreateCopy() method call is passed through directly, so " +"that method should be consulted for details of arguments. However, some " +"things to keep in mind are:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:531 +msgid "" +"If the `bStrict` flag is FALSE the driver should try to do something " +"reasonable when it cannot exactly represent the source dataset, " +"transforming data types on the fly, dropping georeferencing and so forth." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:532 +msgid "" +"Implementing progress reporting correctly is somewhat involved. The " +"return result of the progress function needs always to be checked for " +"cancellation, and progress should be reported at reasonable intervals. " +"The JPEGCreateCopy() method demonstrates good handling of the progress " +"function." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:533 +msgid "" +"Special creation options should be documented in the on-line help. If the" +" options take the format \"NAME=VALUE\" the papszOptions list can be " +"manipulated with :cpp:func:`CPLFetchNameValue` as demonstrated in the " +"handling of the QUALITY and PROGRESSIVE flags for JPEGCreateCopy()." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:534 +msgid "" +"The returned GDALDataset handle can be in ReadOnly or Update mode. Return" +" it in Update mode if practical, otherwise in ReadOnly mode is fine." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:536 +msgid "" +"The full implementation of the CreateCopy function for JPEG (which is " +"assigned to pfnCreateCopy in the GDALDriver object) is here. static " +"GDALDataset *" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:644 +msgid "Dynamic Creation" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:646 +msgid "" +"In the case of dynamic creation, there is no source dataset. Instead the " +"size, number of bands, and pixel data type of the desired file is " +"provided but other information (such as georeferencing, and imagery data)" +" would be supplied later via other method calls on the resulting " +"GDALDataset." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:648 +msgid "" +"The following sample implement PCI .aux labeled raw raster creation. It " +"follows a common approach of creating a blank, but valid file using non-" +"GDAL calls, and then calling GDALOpen(,GA_Update) at the end to return a " +"writable file handle. This avoids having to duplicate the various setup " +"actions in the Open() function." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:753 +msgid "" +"File formats supporting dynamic creation, or even just update-in-place " +"access also need to implement an IWriteBlock() method on the raster band " +"class. It has semantics similar to IReadBlock(). As well, for various " +"esoteric reasons, it is critical that a FlushCache() method be " +"implemented in the raster band destructor. This is to ensure that any " +"write cache blocks for the band be flushed out before the destructor is " +"called." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:756 +msgid "RawDataset/RawRasterBand Helper Classes" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:758 +msgid "" +"Many file formats have the actual imagery data stored in a regular, " +"binary, scanline oriented format. Rather than re-implement the access " +"semantics for this for each formats, there are provided " +":cpp:class:`RawDataset` and :cpp:class:`RawRasterBand` classes declared " +"in gcore/ that can be utilized to implement efficient and convenient " +"access." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:760 +msgid "" +"In these cases the format specific band class may not be required, or if " +"required it can be derived from RawRasterBand. The dataset class should " +"be derived from RawDataset." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:762 +msgid "" +"The Open() method for the dataset then instantiates raster bands passing " +"all the layout information to the constructor. For instance, the PNM " +"driver uses the following calls to create it's raster bands." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:785 +msgid "The RawRasterBand takes the following arguments." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:787 +msgid "" +"poDS: The GDALDataset this band will be a child of. This dataset must be " +"of a class derived from RawRasterDataset." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:788 +msgid "nBand: The band it is on that dataset, 1 based." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:789 +msgid "fpRaw: The FILE * handle to the file containing the raster data." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:790 +msgid "" +"nImgOffset: The byte offset to the first pixel of raster data for the " +"first scanline." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:791 +msgid "" +"nPixelOffset: The byte offset from the start of one pixel to the start of" +" the next within the scanline." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:792 +msgid "" +"nLineOffset: The byte offset from the start of one scanline to the start " +"of the next." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:793 +msgid "eDataType: The GDALDataType code for the type of the data on disk." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:794 +msgid "" +"bNativeOrder: FALSE if the data is not in the same endianness as the " +"machine GDAL is running on. The data will be automatically byte swapped." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:796 +msgid "" +"Simple file formats utilizing the Raw services are normally placed all " +"within one file in the gdal/frmts/raw directory. There are numerous " +"examples there of format implementation." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:799 +msgid "Metadata, and Other Exotic Extensions" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:801 +msgid "" +"There are various other items in the GDAL data model, for which virtual " +"methods exist on the GDALDataset and GDALRasterBand. They include:" +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:803 +msgid "" +"Metadata: Name/value text values about a dataset or band. The " +"GDALMajorObject (base class for GDALRasterBand and GDALDataset) has " +"built-in support for holding metadata, so for read access it only needs " +"to be set with calls to SetMetadataItem() during the Open(). The SAR_CEOS" +" (frmts/ceos2/sar_ceosdataset.cpp) and GeoTIFF drivers are examples of " +"drivers implementing readable metadata." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:805 +msgid "" +"ColorTables: GDT_Byte raster bands can have color tables associated with " +"them. The frmts/png/pngdataset.cpp driver contains an example of a format" +" that supports colortables." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:807 +msgid "" +"ColorInterpretation: The PNG driver contains an example of a driver that " +"returns an indication of whether a band should be treated as a Red, " +"Green, Blue, Alpha or Greyscale band." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:809 +msgid "" +"GCPs: GDALDatasets can have a set of ground control points associated " +"with them (as opposed to an explicit affine transform returned by " +"GetGeotransform()) relating the raster to georeferenced coordinates. The " +"MFF2 (gdal/frmts/raw/hkvdataset.cpp) format is a simple example of a " +"format supporting GCPs." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:811 +msgid "" +"NoDataValue: Bands with known \"nodata\" values can implement the " +"GetNoDataValue() method. See the PAux (frmts/raw/pauxdataset.cpp) for an " +"example of this." +msgstr "" + +#: ../../source/tutorials/raster_driver_tut.rst:813 +msgid "" +"Category Names: Classified images with names for each class can return " +"them using the GetCategoryNames() method though no formats currently " +"implement this." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:5 +msgid "Vector API tutorial" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:7 +msgid "" +"This document is intended to document using the OGR C++ classes to read " +"and write data from a file. It is strongly advised that the reader first" +" review the :ref:`vector_data_model` document describing the key classes " +"and their roles in OGR." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:12 +msgid "" +"It also includes code snippets for the corresponding functions in C and " +"Python." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:15 +msgid "Reading From OGR" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:17 +msgid "" +"For purposes of demonstrating reading with OGR, we will construct a small" +" utility for dumping point layers from an OGR data source to stdout in " +"comma-delimited format." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:21 +msgid "" +"Initially it is necessary to register all the format drivers that are " +"desired. This is normally accomplished by calling " +":cpp:func:`GDALAllRegister` which registers all format drivers built into" +" GDAL/OGR." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:25 +#: ../../source/tutorials/vector_api_tut.rst:57 +#: ../../source/tutorials/vector_api_tut.rst:88 +#: ../../source/tutorials/vector_api_tut.rst:287 +#: ../../source/tutorials/vector_api_tut.rst:335 +#: ../../source/tutorials/vector_api_tut.rst:431 +#: ../../source/tutorials/vector_api_tut.rst:537 +#: ../../source/tutorials/vector_api_tut.rst:1040 +#: ../../source/tutorials/vector_api_tut.rst:1121 +#: ../../source/tutorials/vector_api_tut.rst:1213 +#: ../../source/tutorials/vector_api_tut.rst:1237 +#: ../../source/tutorials/vector_api_tut.rst:1263 +#: ../../source/tutorials/vector_api_tut.rst:1303 +#: ../../source/tutorials/vector_api_tut.rst:1528 +#: ../../source/tutorials/vector_api_tut.rst:1598 +msgid "In C++ :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:37 +#: ../../source/tutorials/vector_api_tut.rst:70 +#: ../../source/tutorials/vector_api_tut.rst:96 +#: ../../source/tutorials/vector_api_tut.rst:234 +#: ../../source/tutorials/vector_api_tut.rst:310 +#: ../../source/tutorials/vector_api_tut.rst:365 +#: ../../source/tutorials/vector_api_tut.rst:438 +#: ../../source/tutorials/vector_api_tut.rst:615 +#: ../../source/tutorials/vector_api_tut.rst:1060 +#: ../../source/tutorials/vector_api_tut.rst:1103 +#: ../../source/tutorials/vector_api_tut.rst:1135 +#: ../../source/tutorials/vector_api_tut.rst:1222 +#: ../../source/tutorials/vector_api_tut.rst:1248 +#: ../../source/tutorials/vector_api_tut.rst:1276 +#: ../../source/tutorials/vector_api_tut.rst:1382 +#: ../../source/tutorials/vector_api_tut.rst:1557 +#: ../../source/tutorials/vector_api_tut.rst:1624 +msgid "In C :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:48 +msgid "" +"Next we need to open the input OGR datasource. Datasources can be files," +" RDBMSes, directories full of files, or even remote web services " +"depending on the driver being used. However, the datasource name is " +"always a single string. In this case we are hardcoded to open a " +"particular shapefile. The second argument (GDAL_OF_VECTOR) tells the " +":cpp:func:`OGROpen` method that we want a vector driver to be use and " +"that don't require update access. On failure NULL is returned, and we " +"report an error." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:83 +msgid "" +"A GDALDataset can potentially have many layers associated with it. The " +"number of layers available can be queried with " +":cpp:func:`GDALDataset::GetLayerCount` and individual layers fetched by " +"index using :cpp:func:`GDALDataset::GetLayer`. However, we will just " +"fetch the layer by name." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:105 +msgid "" +"Now we want to start reading features from the layer. Before we start we" +" could assign an attribute or spatial filter to the layer to restrict the" +" set of feature we get back, but for now we are interested in getting all" +" features." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:109 +#: ../../source/tutorials/vector_api_tut.rst:155 +msgid "With GDAL 2.3 and C++11:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:116 +msgid "With GDAL 2.3 and C:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:123 +msgid "" +"If using older GDAL versions, while it isn't strictly necessary in this " +"circumstance since we are starting fresh with the layer, it is often wise" +" to call :cpp:func:`OGRLayer::ResetReading` to ensure we are starting at " +"the beginning of the layer. We iterate through all the features in the " +"layer using OGRLayer::GetNextFeature(). It will return NULL when we run " +"out of features." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:129 +#: ../../source/tutorials/vector_api_tut.rst:195 +msgid "With GDAL < 2.3 and C++ :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:140 +msgid "With GDAL < 2.3 and C :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:150 +msgid "" +"In order to dump all the attribute fields of the feature, it is helpful " +"to get the :cpp:class:`OGRFeatureDefn`. This is an object, associated " +"with the layer, containing the definitions of all the fields. We loop " +"over all the fields, and fetch and report the attributes based on their " +"type." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:276 +msgid "" +"There are a few more field types than those explicitly handled above, but" +" a reasonable representation of them can be fetched with the " +":cpp:func:`OGRFeature::GetFieldAsString` method. In fact we could " +"shorten the above by using GetFieldAsString() for all the types." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:281 +msgid "" +"Next we want to extract the geometry from the feature, and write out the " +"point geometry x and y. Geometries are returned as a generic " +":cpp:class:`OGRGeometry` pointer. We then determine the specific geometry" +" type, and if it is a point, we cast it to point and operate on it. If " +"it is something else we write placeholders." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:327 +msgid "" +"The :cpp:func:`wkbFlatten` macro is used above to convert the type for a " +"wkbPoint25D (a point with a z coordinate) into the base 2D geometry type " +"code (wkbPoint). For each 2D geometry type there is a corresponding 2.5D " +"type code. The 2D and 2.5D geometry cases are handled by the same C++ " +"class, so our code will handle 2D or 3D cases properly." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:333 +msgid "Several geometry fields can be associated to a feature." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:402 +msgid "" +"Note that :cpp:func:`OGRFeature::GetGeometryRef` and " +":cpp:func:`OGRFeature::GetGeomFieldRef` return a pointer to the internal " +"geometry owned by the OGRFeature. There we don't actually delete the " +"return geometry." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:408 +msgid "" +"With GDAL 2.3 and C++11, the looping over features is simply terminated " +"by a closing curly bracket." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:415 +msgid "" +"With GDAL 2.3 and C, the looping over features is simply terminated by " +"the following." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:424 +msgid "" +"For GDAL < 2.3, as the :cpp:func:`OGRLayer::GetNextFeature` method " +"returns a copy of the feature that is now owned by us. So at the end of " +"use we must free the feature. We could just \"delete\" it, but this can " +"cause problems in windows builds where the GDAL DLL has a different " +"\"heap\" from the main program. To be on the safe side we use a GDAL " +"function to delete the feature." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:446 +msgid "" +"The OGRLayer returned by :cpp:func:`GDALDataset::GetLayerByName` is also " +"a reference to an internal layer owned by the GDALDataset so we don't " +"need to delete it. But we do need to delete the datasource in order to " +"close the input file. Once again we do this with a custom delete method " +"to avoid special win32 heap issues." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:452 +#: ../../source/tutorials/vector_api_tut.rst:1293 +msgid "In C/C++ :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:460 +msgid "All together our program looks like this." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:462 +msgid "With GDAL 2.3 and C++11 :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:744 +msgid "Reading From OGR using the Arrow C Stream data interface" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:748 +msgid "" +"Instead of retrieving features one at a time, it is also possible to " +"retrieve them by batches, with a column-oriented memory layout, using the" +" :cpp:func:`OGRLayer::GetArrowStream` method. Note that this method is " +"more difficult to use than the traditional " +":cpp:func:`OGRLayer::GetNextFeature` approach, and is only advised when " +"compatibility with the `Apache Arrow C Stream interface " +"<https://arrow.apache.org/docs/format/CStreamInterface.html>`_ is needed," +" or when column-oriented consumption of layers is required." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:756 +msgid "" +"Pending using an helper library, consumption of the Arrow C Stream " +"interface requires reading of the following documents:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:759 +msgid "" +"`Arrow C Stream interface " +"<https://arrow.apache.org/docs/format/CStreamInterface.html>`_" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:760 +#: ../../source/tutorials/vector_api_tut.rst:1686 +msgid "" +"`Arrow C data interface " +"<https://arrow.apache.org/docs/format/CDataInterface.html>`_" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:761 +#: ../../source/tutorials/vector_api_tut.rst:1687 +msgid "" +"`Arrow Columnar Format " +"<https://arrow.apache.org/docs/format/Columnar.html>`_." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:763 +msgid "" +"The Arrow C Stream interface interface consists of a set of C structures," +" ArrowArrayStream, that provides two main callbacks to get:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:766 +msgid "" +"a ArrowSchema with the get_schema() callback. A ArrowSchema describes a " +"set of field descriptions (name, type, metadata). All OGR data types have" +" a corresponding Arrow data type." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:770 +msgid "" +"a sequence of ArrowArray with the get_next() callback. A ArrowArray " +"captures a set of values for a specific column/field in a subset of " +"features. This is the equivalent of a `Series " +"<https://arrow.apache.org/docs/python/pandas.html#series>`_ in a Pandas " +"DataFrame. This is a potentially hiearchical structure that can aggregate" +" sub arrays, and in OGR usage, the main array will be a StructArray which" +" is the collection of OGR attribute and geometry fields. The layout of " +"buffers and children arrays per data type is detailed in the `Arrow " +"Columnar Format <https://arrow.apache.org/docs/format/Columnar.html>`_." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:780 +msgid "" +"If a layer consists of 4 features with 2 fields (one of integer type, one" +" of floating-point type), the representation as a ArrowArray is " +"*conceptually* the following one:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:789 +msgid "" +"The content of a whole layer can be seen as a sequence of record batches," +" each record batches being an ArrowArray of a subset of features. Instead" +" of iterating over individual features, one iterates over a batch of " +"several features at once." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:794 +msgid "" +"The ArrowArrayStream, ArrowSchema, ArrowArray structures are defined in a" +" ogr_recordbatch.h public header file, directly derived from " +"https://github.com/apache/arrow/blob/main/cpp/src/arrow/c/abi.h to get " +"API/ABI compatibility with Apache Arrow C++. This header file must be " +"explicitly included when the related array batch API is used." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:800 +msgid "The GetArrowStream() method has the following signature:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:807 +msgid "It is also available in the C API as :cpp:func:`OGR_L_GetArrowStream`." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:809 +msgid "" +"out_stream is a pointer to a ArrowArrayStream structure, that can be in a" +" uninitialized state (the method will ignore any initial content)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:812 +msgid "" +"On successful return, and when the stream interfaces is no longer needed," +" it must must be freed with out_stream->release(out_stream)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:815 +msgid "" +"There are extra precautions to take into account in a OGR context. Unless" +" otherwise specified by a particular driver implementation, the " +"ArrowArrayStream structure, and the ArrowSchema or ArrowArray objects its" +" callbacks have returned, should no longer be used (except for " +"potentially being released) after the OGRLayer from which it was " +"initialized has been destroyed (typically at dataset closing). " +"Furthermore, unless otherwise specified by a particular driver " +"implementation, only one ArrowArrayStream can be active at a time on a " +"given layer (that is the last active one must be explicitly released " +"before a next one is asked). Changing filter state, ignored columns, " +"modifying the schema or using ResetReading()/GetNextFeature() while using" +" a ArrowArrayStream is strongly discouraged and may lead to unexpected " +"results. As a rule of thumb, no OGRLayer methods that affect the state of" +" a layer should be called on a layer, while an ArrowArrayStream on it is " +"active." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:829 +msgid "" +"The papszOptions that may be provided is a NULL terminated list of " +"key=value strings, that may be driver specific." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:832 +msgid "OGRLayer has a base implementation of GetArrowStream() that is such:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:834 +msgid "" +"The get_schema() callback returns a schema whose top-level object " +"returned is of type Struct, and whose children consist of the FID column," +" all OGR attribute fields and geometry fields to Arrow fields. The FID " +"column may be omitted by providing the INCLUDE_FID=NO option." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:839 +msgid "" +"When get_schema() returns 0, and the schema is no longer needed, it must " +"be released with the following procedure, to take into account that it " +"might have been released by other code, as documented in the Arrow C data" +" interface:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:850 +msgid "The get_next() callback retrieve the next record batch over the layer." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:852 +msgid "" +"out_array is a pointer to a ArrowArray structure, that can be in a " +"uninitialized state (the method will ignore any initial content)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:855 +msgid "" +"The default implementation uses GetNextFeature() internally to retrieve " +"batches of up to 65,536 features (configurable with the " +"MAX_FEATURES_IN_BATCH=num option). The starting address of buffers " +"allocated by the default implementation is aligned on 64-byte boundaries." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:860 +msgid "" +"The default implementation outputs geometries as WKB in a binary field, " +"whose corresponding entry in the schema is marked with the metadata item " +"``ARROW:extension:name`` set to ``ogc.wkb``. Specialized implementations " +"may output by default other formats (particularly the Arrow driver that " +"can return geometries encoded according to the GeoArrow specification " +"(using a list of coordinates). The GEOMETRY_ENCODING=WKB option can be " +"passed to force the use of WKB (through the default implementation)" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:868 +msgid "" +"The method may take into account ignored fields set with " +"SetIgnoredFields() (the default implementation does), and should take " +"into account filters set with SetSpatialFilter() and " +"SetAttributeFilter(). Note however that specialized implementations may " +"fallback to the default (slower) implementation when filters are set." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:873 +msgid "" +"Mixing calls to GetNextFeature() and get_next() is not recommended, as " +"the behavior will be unspecified (but it should not crash)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:876 +msgid "" +"When get_next() returns 0, and the array is no longer needed, it must be " +"released with the following procedure, to take into account that it might" +" have been released by other code, as documented in the Arrow C data " +"interface:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:886 +msgid "" +"Drivers that have a specialized implementation advertise the new " +"OLCFastGetArrowStream layer capability." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:889 +msgid "" +"Using directly (as a producer or a consumer) a ArrowArray is admittedly " +"not trivial, and requires good intimacy with the Arrow C data interface " +"and columnar array specifications, to know, in which buffer of an array, " +"data is to be read, which data type void* buffers should be cast to, how " +"to use buffers that contain null/not_null information, how to use offset " +"buffers for data types of type List, etc. The study of the " +"gdal_array._RecordBatchAsNumpy() method of the SWIG Python bindings " +"(:source_file:`swig/include/gdal_array.i`) can give a good hint of how to" +" use an ArrowArray object, in conjunction with the associated " +"ArrowSchema." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:899 +msgid "" +"The below example illustrates how to read the content of a layer that " +"consists of a integer field and a geometry field:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1028 +msgid "" +"To write features by batches using an ArrowArray, consult " +":ref:`vector_api_tut_arrow_write`." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1031 +msgid "Writing To OGR" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1033 +msgid "" +"As an example of writing through OGR, we will do roughly the opposite of " +"the above. A short program that reads comma separated values from input " +"text will be written to a point shapefile via OGR." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1037 +msgid "" +"As usual, we start by registering all the drivers, and then fetch the " +"Shapefile driver as we will need it to create our output file." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1080 +msgid "" +"Next we create the datasource. The ESRI Shapefile driver allows us to " +"create a directory full of shapefiles, or a single shapefile as a " +"datasource. In this case we will explicitly create a single file by " +"including the extension in the name. Other drivers behave differently. " +"The second, third, fourth and fifth argument are related to raster " +"dimensions (in case the driver has raster capabilities). The last " +"argument to the call is a list of option values, but we will just be " +"using defaults in this case. Details of the options supported are also " +"format specific." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1089 +msgid "In C ++ :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1116 +msgid "" +"Now we create the output layer. In this case since the datasource is a " +"single file, we can only have one layer. We pass wkbPoint to specify the" +" type of geometry supported by this layer. In this case we aren't " +"passing any coordinate system information or other special layer creation" +" options." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1149 +msgid "" +"Now that the layer exists, we need to create any attribute fields that " +"should appear on the layer. Fields must be added to the layer before any" +" features are written. To create a field we initialize an " +":cpp:union:`OGRField` object with the information about the field. In " +"the case of Shapefiles, the field width and precision is significant in " +"the creation of the output .dbf file, so we set it specifically, though " +"generally the defaults are OK. For this example we will just have one " +"attribute, a name string associated with the x,y point." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1157 +msgid "" +"Note that the template OGRField we pass to " +":cpp:func:`OGRLayer::CreateField` is copied internally. We retain " +"ownership of the object." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1194 +msgid "" +"The following snipping loops reading lines of the form \"x,y,name\" from " +"stdin, and parsing them." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1197 +msgid "In C++ and in C :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1208 +msgid "" +"To write a feature to disk, we must create a local OGRFeature, set " +"attributes and attach geometry before trying to write it to the layer. " +"It is imperative that this feature be instantiated from the " +"OGRFeatureDefn associated with the layer it will be written to." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1231 +msgid "" +"We create a local geometry object, and assign its copy (indirectly) to " +"the feature. The :cpp:func:`OGRFeature::SetGeometryDirectly` differs from" +" :cpp:func:`OGRFeature::SetGeometry` in that the direct method gives " +"ownership of the geometry to the feature. This is generally more " +"efficient as it avoids an extra deep object copy of the geometry." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1260 +msgid "" +"Now we create a feature in the file. The " +":cpp:func:`OGRLayer::CreateFeature` does not take ownership of our " +"feature so we clean it up when done with it." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1290 +msgid "" +"Finally we need to close down the datasource in order to ensure headers " +"are written out in an orderly way and all resources are recovered." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1301 +msgid "The same program all in one block looks like this:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1461 +#: ../../source/tutorials/vector_api_tut.rst:1653 +msgid "In Python :" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1522 +msgid "" +"Several geometry fields can be associated to a feature. This capability " +"is just available for a few file formats, such as PostGIS." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1525 +msgid "" +"To create such datasources, geometry fields must be first created. " +"Spatial reference system objects can be associated to each geometry " +"field." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1593 +msgid "" +"To write a feature to disk, we must create a local OGRFeature, set " +"attributes and attach geometries before trying to write it to the layer." +" It is imperative that this feature be instantiated from the " +"OGRFeatureDefn associated with the layer it will be written to." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1671 +msgid "Writing to OGR using the Arrow C Data interface" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1675 +msgid "" +"Instead of writing features one at a time, it is also possible to write " +"them by batches, with a column-oriented memory layout, using the " +":cpp:func:`OGRLayer::WriteArrowBatch` method. Note that this method is " +"more difficult to use than the traditional " +":cpp:func:`OGRLayer::CreateFeature` approach, and is only advised when " +"compatibility with the `Apache Arrow C Data interface " +"<https://arrow.apache.org/docs/format/CDataInterface.html>`_ is needed, " +"or when column-oriented writing of layers is required." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1683 +msgid "" +"Pending using an helper library, generation of the Arrow C Data interface" +" requires reading of the following documents:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1689 +msgid "" +"Consult :ref:`vector_api_tut_arrow_stream` for introduction to the " +"ArrowSchema and ArrowArray basic types involved for batch writing." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1692 +msgid "The WriteArrowBatch() method has the following signature:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1708 +msgid "It is also available in the C API as :cpp:func:`OGR_L_WriteArrowBatch`." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1710 +msgid "" +"This is semantically close to calling " +":cpp:func:`OGRLayer::CreateFeature()` with multiple features at once." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1713 +msgid "" +"The ArrowArray must be of type struct (format=+s), and its children " +"generally map to a OGR attribute or geometry field (unless they are " +"struct themselves)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1716 +msgid "" +"Method :cpp:func:`OGRLayer::IsArrowSchemaSupported` can be called to " +"determine if the schema will be supported by WriteArrowBatch()." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1719 +msgid "" +"OGR fields for the corresponding children arrays must exist and be of a " +"compatible type. For attribute fields, they should be created with " +":cpp:func:`OGRLayer::CreateFieldFromArrowSchema`." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1723 +msgid "" +"Arrays for geometry columns should be of binary or large binary type and " +"contain WKB geometry." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1726 +msgid "" +"Note that the passed array may be set to a released state " +"(array->release==NULL) after this call (not by the base implementation, " +"but in specialized ones such as Parquet or Arrow for example)" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1730 +msgid "Supported options of the base implementation are:" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1732 +msgid "" +"FID=name. Name of the FID column in the array. If not provided, " +"GetFIDColumn() is used to determine it. The special name " +"OGRLayer::DEFAULT_ARROW_FID_NAME is also recognized if neither FID nor " +"GetFIDColumn() are set. The corresponding ArrowArray must be of type " +"int32 (i) or int64 (l). On input, values of the FID column are used to " +"create the feature. On output, the values of the FID column may be set " +"with the FID of the created feature (if the array is not released)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1741 +msgid "" +"GEOMETRY_NAME=name. Name of the geometry column. If not provided, " +"GetGeometryColumn() is used. The special name " +"OGRLayer::DEFAULT_ARROW_GEOMETRY_NAME is also recognized if neither " +"GEOMETRY_NAME nor GetGeometryColumn() are set. Geometry columns are also " +"identified if they have ARROW:extension:name=ogc.wkb as a field metadata." +" The corresponding ArrowArray must be of type binary (w) or large binary " +"(W)." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1750 +msgid "" +"Drivers that have a specialized implementation (such as " +":ref:`vector.parquet` and :ref:`vector.arrow`) advertise the " +"OLCFastWriteArrowBatch layer capability." +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1753 +msgid "" +"The following example in Python demonstrates how to copy a layer from one" +" format to another one (assuming it has at most a single geometry " +"column):" +msgstr "" + +#: ../../source/tutorials/vector_api_tut.rst:1821 +msgid "" +"For the Python bindings, in addition to the above " +"ogr.Layer.IsArrowSchemaSupported(), " +"ogr.Layer.CreateFieldFromArrowSchema() and ogr.Layer.WriteArrowBatch() " +"methods, 3 similar methods exist using the `PyArrow " +"<https://arrow.apache.org/docs/python/index.html>`__ data types:" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:5 +msgid "Vector driver implementation tutorial" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:12 +msgid "" +"In general new formats are added to OGR by implementing format specific " +"drivers with instantiating a :cpp:class:`GDALDriver` and subclasses of " +":cpp:class:`GDALDataset` and :cpp:class:`OGRLayer`. The GDALDriver " +"instance is registered with the :cpp:class:`GDALDriverManager` at " +"runtime." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:17 +msgid "" +"Before following this tutorial to implement an OGR driver, please review " +"the :ref:`vector_data_model` document carefully." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:20 +msgid "The tutorial will be based on implementing a simple ascii point format." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:23 +msgid "Implementing GDALDriver" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:25 +msgid "" +"The format specific driver class is implemented as a instance of " +"GDALDriver. One instance of the driver will normally be created, and " +"registered with the GDALDriverManager. The instantiation of the driver " +"is normally handled by a global C callable registration function, similar" +" to the following placed in the same file as the driver class." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:55 +msgid "" +"The :cpp:func:`GDALDriver::SetDescription` sets the name of the driver. " +"This name is specified on the commandline when creating datasources so it" +" is generally good to keep it short and without any special characters or" +" spaces." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:59 +msgid "" +"SetMetadataItem( GDAL_DCAP_VECTOR, \"YES\" ) is specified to indicate " +"that the driver will handle vector data." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:62 +msgid "" +"SetMetadataItem( GDAL_DCAP_VIRTUALIO, \"YES\" ) is specified to indicate " +"that the driver can deal with files opened with the VSI*L GDAL API. " +"Otherwise this metadata item should not be defined." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:68 +msgid "" +"The driver declaration generally looks something like this for a format " +"with read or read and update access (the Open() method) and creation " +"support (the Create() method)." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:81 +msgid "" +"The Open() method is called by :cpp:func:`GDALOpenEx`. It should quietly " +"return NULL if the passed filename is not of the format supported by the " +"driver. If it is the target format, then a new GDALDataset object for " +"the dataset should be returned." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:85 +msgid "" +"It is common for the Open() method to be delegated to an Open() method on" +" the actual format's GDALDataset class." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:106 +msgid "The Identify() method is implemented as such :" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:118 +msgid "" +"Examples of the Create() method is left for the section on creation and " +"update." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:121 +msgid "Basic Read Only Data Source" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:123 +msgid "" +"We will start implementing a minimal read-only datasource. No attempt is" +" made to optimize operations, and default implementations of many methods" +" inherited from GDALDataset are used." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:127 +msgid "" +"The primary responsibility of the datasource is to manage the list of " +"layers. In the case of the SPF format a datasource is a single file " +"representing one layer so there is at most one layer. The \"name\" of a " +"datasource should generally be the name passed to the Open() method." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:132 +msgid "" +"The Open() method below is not overriding a base class method, but we " +"have it to implement the open operation delegated by the driver class." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:135 +msgid "" +"For this simple case we provide a stub " +":cpp:func:`GDALDataset::TestCapability` that returns FALSE for all " +"extended capabilities. The TestCapability() method is pure virtual, so " +"it does need to be implemented." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:159 +msgid "" +"The constructor is a simple initializer to a default state. The Open() " +"will take care of actually attaching it to a file. The destructor is " +"responsible for orderly cleanup of layers." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:180 +msgid "" +"The Open() method is the most important one on the datasource, though in " +"this particular instance it passes most of its work off to the " +"OGRSPFLayer constructor if it believes the file is of the desired format." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:184 +msgid "" +"Note that Open() methods should try and determine that a file isn't of " +"the identified format as efficiently as possible, since many drivers may " +"be invoked with files of the wrong format before the correct driver is " +"reached. In this particular Open() we just test the file extension but " +"this is generally a poor way of identifying a file format. If available," +" checking \"magic header values\" or something similar is preferable." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:191 +msgid "" +"In the case of the SPF format, update in place is not supported, so we " +"always fail if bUpdate is FALSE." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:218 +msgid "" +"A GetLayer() method also needs to be implemented. Since the layer list " +"is created in the Open() this is just a lookup with some safety testing." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:234 +msgid "Read Only Layer" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:236 +msgid "" +"The OGRSPFLayer is implements layer semantics for an .spf file. It " +"provides access to a set of feature objects in a consistent coordinate " +"system with a particular set of attribute columns. Our class definition " +"looks like this:" +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:263 +msgid "" +"The layer constructor is responsible for initialization. The most " +"important initialization is setting up the :cpp:class:`OGRFeatureDefn` " +"for the layer. This defines the list of fields and their types, the " +"geometry type and the coordinate system for the layer. In the SPF format" +" the set of fields is fixed - a single string field and we have no " +"coordinate system info to set." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:269 +msgid "" +"Pay particular attention to the reference counting of the OGRFeatureDefn." +" As OGRFeature's for this layer will also take a reference to this " +"definition, it is important that we also establish a reference on behalf " +"of the layer itself." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:295 +msgid "" +"Note that the destructor uses :cpp:func:`OGRFeatureDefn::Release` on the " +"OGRFeatureDefn. This will destroy the feature definition if the " +"reference count drops to zero, but if the application is still holding " +"onto a feature from this layer, then that feature will hold a reference " +"to the feature definition and it will not be destroyed here (which is " +"good!)." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:311 +msgid "" +"The :cpp:func:`OGRLayer::GetNextFeature` method is usually the work horse" +" of OGRLayer implementations. It is responsible for reading the next " +"feature according to the current spatial and attribute filters installed." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:315 +msgid "" +"The while() loop is present to loop until we find a satisfactory feature." +" The first section of code is for parsing a single line of the SPF text " +"file and establishing the x, y and name for the line." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:351 +msgid "" +"The next section turns the x, y and name into a feature. Also note that " +"we assign a linearly incremented feature id. In our case we started at " +"zero for the first feature, though some drivers start at 1." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:364 +msgid "" +"Next we check if the feature matches our current attribute or spatial " +"filter if we have them. Methods on the OGRLayer base class support " +"maintain filters in the OGRLayer member fields " +":cpp:member:`OGRLayer::m_poFilterGeom` (spatial filter) and " +":cpp:member:`OGRLayer::m_poAttrQuery` (attribute filter) so we can just " +"use these values here if they are non-NULL. The following test is " +"essentially \"stock\" and done the same in all formats. Some formats " +"also do some spatial filtering ahead of time using a spatial index." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:372 +msgid "" +"If the feature meets our criteria we return it. Otherwise we destroy it," +" and return to the top of the loop to fetch another to try." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:387 +msgid "" +"While in the middle of reading a feature set from a layer, or at any " +"other time the application can call :cpp:func:`OGRLayer::ResetReading` " +"which is intended to restart reading at the beginning of the feature set." +" We implement this by seeking back to the beginning of the file, and " +"resetting our feature id counter." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:400 +msgid "" +"In this implementation we do not provide a custom implementation for the " +"GetFeature() method. This means an attempt to read a particular feature " +"by its feature id will result in many calls to GetNextFeature() until the" +" desired feature is found. However, in a sequential text format like spf" +" there is little else we could do anyway." +msgstr "" + +#: ../../source/tutorials/vector_driver_tut.rst:406 +msgid "There! We have completed a simple read-only feature file format driver." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:5 +msgid "Vector driver in Python implementation tutorial" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:14 +msgid "" +"Since GDAL 3.1, the capability of writing read-only vector drivers in " +"Python has been added. It is strongly advised to read the " +":ref:`vector_driver_tut` first, which will give the general principles of" +" how a vector driver works." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:18 +msgid "" +"This capability does not require the use of the GDAL/OGR SWIG Python " +"bindings (but a vector Python driver may use them.)" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:21 +msgid "" +"Note: per project policies, this is considered as an \"experimental\" " +"feature and the GDAL project will not accept such Python drivers to be " +"included in the GDAL repository. Drivers aiming at inclusion in GDAL " +"master should priorly be ported to C++. The rationale for this is that:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:26 +msgid "" +"the correctness of the Python code can mostly be checked at runtime, " +"whereas C++ benefits from static analysis (at compile time, and other " +"checkers)." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:28 +msgid "" +"Python code is executed under the Python Global Interpreter Lock, which " +"makes them not scale." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:30 +msgid "Not all builds of GDAL have Python available." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:34 +msgid "Linking mechanism to a Python interpreter" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:36 +msgid "See :ref:`linking_mechanism_to_python_interpreter`" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:39 +msgid "Driver location" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:41 +msgid "" +"Driver filenames must start with `gdal_` or `ogr_` and have the `.py` " +"extension. They will be searched in the following directies:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:44 +msgid "" +"the directory pointed by the ``GDAL_PYTHON_DRIVER_PATH`` configuration " +"option (there may be several paths separated by `:` on Unix or `;` on " +"Windows)" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:46 +msgid "" +"if not defined, the directory pointed by the ``GDAL_DRIVER_PATH`` " +"configuration option." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:48 +msgid "" +"if not defined, in the directory (hardcoded at compilation time on Unix " +"builds) where native plugins are located." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:51 +msgid "" +"GDAL does not try to manage Python dependencies that are imported by the " +"driver .py script. It is up to the user to make sure its current Python " +"environment has all required dependencies installed." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:56 +msgid "Import section" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:58 +msgid "Drivers must have the following import section to load the base classes." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:64 +msgid "" +"The ``gdal_python_driver`` module is created dynamically by GDAL and is " +"not present on the file system." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:68 +msgid "Metadata section" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:70 +msgid "" +"In the first 1000 lines of the .py file, a number of required and " +"optional KEY=VALUE driver directives must be defined. They are parsed by " +"C++ code, without using the Python interpreter, so it is vital to respect" +" the following constraints:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:75 +msgid "" +"each declaration must be on a single line, and start with ``# gdal: " +"DRIVER_`` (space character between sharp character and gdal, and between " +"colon character and DRIVER\\_)" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:77 +msgid "" +"the value must be a literal value of type string (except for # gdal: " +"DRIVER_SUPPORTED_API_VERSION which can accept an array of integers), " +"without expressions, function calls, escape sequences, etc." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:80 +msgid "strings may be single or double-quoted" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:82 +msgid "The following directives must be declared:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:84 +msgid "``# gdal: DRIVER_NAME = \"NAME\"``: the short name of the driver" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:85 +msgid "" +"``# gdal: DRIVER_SUPPORTED_API_VERSION = [1]``: the API version(s) " +"supported by the driver. Must include 1, which is the only currently " +"supported version in GDAL 3.1" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:87 +msgid "``# gdal: DRIVER_DCAP_VECTOR = \"YES\"``: declares a vector driver" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:88 +msgid "``# gdal: DRIVER_DMD_LONGNAME = \"a longer name of the driver\"``" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:90 +msgid "Additional directives:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:92 +msgid "" +"``# gdal: DRIVER_DMD_EXTENSIONS = \"ext1 ext2\"``: list of extension(s) " +"recognized by the driver, without the dot, and separated by space" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:94 +msgid "" +"``# gdal: DRIVER_DMD_HELPTOPIC = \"https://example.com/my_help.html\"``: " +"URL to a help page for the driver" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:96 +msgid "" +"``# gdal: DRIVER_DMD_OPENOPTIONLIST = \"<OpenOptionList><Option " +"name='OPT1' type='boolean' description='bla' " +"default='NO'/></OpenOptionList>\"`` where the XML is an " +"``OptionOptionList``." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:98 +msgid "" +"and all other metadata items found in gdal.h starting with ``GDAL_DMD_`` " +"or ``GDAL_DCAP`` by creating an item name which starts with ``# gdal: " +"DRIVER_`` and the value of the ``GDAL_DMD_`` or ``GDAL_DCAP`` metadata " +"item. For example ``#define GDAL_DMD_CONNECTION_PREFIX " +"\"DMD_CONNECTION_PREFIX\"`` becomes ``# gdal: " +"DRIVER_DMD_CONNECTION_PREFIX``" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:104 +#: ../../source/tutorials/vector_python_driver.rst:144 +#: ../../source/tutorials/vector_python_driver.rst:175 +#: ../../source/tutorials/vector_python_driver.rst:201 +msgid "Example:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:116 +msgid "Driver class" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:118 +msgid "" +"The entry point .py script must contains a single class that inherits " +"from ``gdal_python_driver.BaseDriver``." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:121 +msgid "That class must define the following methods:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst +msgid "Parameters" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:126 +#: ../../source/tutorials/vector_python_driver.rst:137 +msgid "File name, or more generally, connection string." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:127 +#: ../../source/tutorials/vector_python_driver.rst:138 +msgid "" +"First bytes of the file (if it is a file). At least 1024 (if the file has" +" at least 1024 bytes), or more if a native driver in the driver probe " +"sequence has requested more previously." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:129 +#: ../../source/tutorials/vector_python_driver.rst:140 +msgid "Open flags. To be ignored for now." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:130 +#: ../../source/tutorials/vector_python_driver.rst:141 +msgid "Open options." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst +msgid "Returns" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:131 +msgid "" +"True if the file is recognized by the driver, False if not, or -1 if that" +" cannot be known from the first bytes." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:142 +msgid "an object deriving from gdal_python_driver.BaseDataset or None" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:162 +msgid "Dataset class" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:164 +msgid "" +"The Driver.open() method on success should return an object from a class " +"that inherits from ``gdal_python_driver.BaseDataset``." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:168 +msgid "Layers" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:170 +msgid "" +"The role of this object is to store vector layers. There are two " +"implementation options. If the number of layers is small or they are fast" +" to construct, then the ``__init__`` method can defined a ``layers`` " +"attribute that is a sequence of objects from a class that inherits from " +"``gdal_python_driver.BaseLayer``." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:184 +msgid "Otherwise, the following two methods should be defined:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:189 +msgid "the number of layers" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:194 +msgid "" +"Index of the layer to return. Normally between 0 and self.layer_count() -" +" 1, but calling code might pass any value. In case of invalid index, None" +" should be returned." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:197 +msgid "" +"an object deriving from gdal_python_driver.BaseLayer or None. The C++ " +"code will take care of caching that object, and this method will only be " +"called once for a given idx value." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:214 +msgid "Metadata" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:216 +msgid "" +"The dataset may define a ``metadata`` dictionary, in ``__init__`` of key:" +" value of type string, for the default metadata domain. Alternatively, " +"the following method may be implemented." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:223 +msgid "metadata domain. Empty string for the default one" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:224 +msgid "None, or a dictionary of key:value pairs of type string;" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:227 +msgid "Other methods" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:229 +msgid "The following method may be optionally implemented:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:234 +msgid "" +"Called at the destruction of the C++ peer GDALDataset object. Useful to " +"close database connections for example." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:239 +msgid "Layer class" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:241 +msgid "" +"The Dataset object will instantiate one or several objects from a class " +"that inherits from ``gdal_python_driver.BaseLayer``." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:245 +msgid "Metadata, and other definitions" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:247 +msgid "The following attributes are required and must defined at __init__ time:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:252 +msgid "Layer name, of type string. If not set, a ``name`` method must be defined." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:257 +msgid "" +"Sequence of field definitions (may be empty). Each field is a dictionary " +"with the following properties:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:263 +msgid "Required" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:268 +msgid "" +"A integer value of type ogr.OFT\\_ (from the SWIG Python bindings), or " +"one of the following string values: ``String``, ``Integer``, " +"``Integer16``, ``Integer64``, ``Boolean``, ``Real``, ``Float``, " +"``Binary``, ``Date``, ``Time``, ``DateTime``" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:272 +msgid "" +"If that attribute is not set, a ``fields`` method must be defined and " +"return such a sequence." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:278 +msgid "" +"Sequence of geometry field definitions (may be empty). Each field is a " +"dictionary with the following properties:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:284 +msgid "Required. May be empty" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:289 +msgid "" +"Required. A integer value of type ogr.wkb\\_ (from the SWIG Python " +"bindings), or one of the following string values: ``Unknown``, ``Point``," +" ``LineString``, ``Polygon``, ``MultiPoint``, ``MultiLineString``, " +"``MultiPolygon``, ``GeometryCollections`` or all other values returned by" +" :cpp:func:`OGRGeometryTypeToName`" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:297 +msgid "" +"The SRS attached to the geometry field as a string that can be ingested " +"by :cpp:func:`OGRSpatialReference::SetFromUserInput`, such as a PROJ " +"string, WKT string, or ``AUTHORITY:CODE``." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:301 +msgid "" +"If that attribute is not set, a ``geometry_fields`` method must be " +"defined and return such a sequence." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:304 +msgid "The following attributes are optional:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:309 +msgid "" +"Feature ID column name, of type string. May be empty string. If not set, " +"a ``fid_name`` method may be defined." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:315 +msgid "" +"A dictionary of key: value strings, corresponding to metadata of the " +"default metadata domain. Alternatively, a ``metadata`` method that " +"accepts a domain argument may be defined." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:322 +msgid "" +"Can be set to True if the feature iterator takes into account the " +"``attribute_filter`` attribute that can be set on the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:328 +msgid "" +"Can be set to True if the feature iterator takes into account the " +"``spatial_filter`` attribute that can be set on the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:334 +msgid "" +"Can be set to True if the feature_count method takes into account the " +"``attribute_filter`` attribute that can be set on the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:340 +msgid "" +"Can be set to True if the feature_count method takes into account the " +"``spatial_filter`` attribute that can be set on the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:344 +msgid "Feature iterator" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:346 +msgid "" +"The Layer class must implement the iterator interface, so typically with " +"a ``__iter__`` method." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:349 +msgid "" +"The resulting iterator must produce dictionaries for each feature's " +"content. The keys allowed in the returned dictionary are:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:355 +msgid "" +"Strongly recommended. The value must be an integer to be recognized as a " +"FID." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:360 +msgid "Required. The value must be the string ``\"OGRFeature\"``" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:365 +msgid "" +"Required. The value must be either a dictionary whose keys are field " +"names; or None" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:370 +msgid "" +"Required. the value must be a dictionary whose keys are geometry field " +"names (possibly the empty string for unnamed geometry columns); or None." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:373 +msgid "" +"The value of each key must be either a geometry encoded as a WKT string; " +"a geometry encoded as ISO WKB as a `bytes-like object " +"<https://docs.python.org/3/glossary.html#term-bytes-like-object>`__; or " +"None." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:380 +msgid "" +"Optional. The value must be a string conforming to the " +":ref:`ogr_feature_style`." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:383 +msgid "Filtering" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:385 +msgid "" +"By default, any attribute or spatial filter set by the user of the OGR " +"API will be evaluated by the generic C++ side of the driver, by iterating" +" over all features of the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:389 +msgid "" +"If the ``iterator_honour_attribute_filter`` (resp. " +"``iterator_honour_spatial_filter``) attribute of the layer object is set " +"to ``True``, the attribute filter (resp. spatial filter) must be honoured" +" by the feature iterator method." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:393 +msgid "" +"The attribute filter is set in the ``attribute_filter`` attribute of the " +"layer object. It is a string conforming to :ref:`OGR SQL " +"<ogr_sql_dialect>`. When the attribute filter is changed by the OGR API, " +"the ``attribute_filter_changed`` optional method is called (see below " +"paragraph about optional methods). An implementation of " +"``attribute_filter_changed`` may decide to fallback on evaluation by the " +"generic C++ side of the driver by calling the ``SetAttributeFilter`` " +"method (see below passthrough example)" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:401 +msgid "" +"The geometry filter is set in the ``spatial_filter`` attribute of the " +"layer object. It is a string encoding as ISO WKT. It is the " +"responsibility of the user of the OGR API to express it in the CRS of the" +" layer. When the attribute filter is changed by the OGR API, the " +"``spatial_filter_changed`` optional method is called (see below paragraph" +" about optional methods). An implementation of ``spatial_filter_changed``" +" may decide to fallback on evaluation by the generic C++ side of the " +"driver by calling the ``SetSpatialFilter`` method (see below passthrough " +"example)" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:411 +msgid "Optional methods" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:413 +msgid "The following methods may be optionally implemented:" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:418 +msgid "the list [xmin,ymin,xmax,ymax] with the spatial extent of the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:423 +msgid "the number of features of the layer." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:425 +msgid "" +"If self.feature_count_honour_attribute_filter or " +"self.feature_count_honour_spatial_filter are set to True, the attribute " +"filter and/or spatial filter must be honoured by this method." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:432 +msgid "feature ID" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:433 +msgid "" +"a feature object in one of the formats of the ``__next__`` method " +"described above, or None if no object matches fid" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:439 +msgid "" +"This method is called whenever self.attribute_filter has been changed. It" +" is the opportunity for the driver to potentially change the value of " +"self.iterator_honour_attribute_filter or " +"feature_count_honour_attribute_filter attributes." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:447 +msgid "" +"This method is called whenever self.spatial_filter has been changed (its " +"value is a geometry encoded in WKT) It is the opportunity for the driver " +"to potentially change the value of self.iterator_honour_spatial_filter or" +" feature_count_honour_spatial_filter attributes." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:456 +msgid "" +"potential values are BaseLayer.FastGetExtent, " +"BaseLayer.FastSpatialFilter, BaseLayer.FastFeatureCount, " +"BaseLayer.RandomRead, BaseLayer.StringsAsUTF8 or other strings supported " +"by :cpp:func:`OGRLayer::TestCapability`" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:460 +msgid "True if the capability is supported, False otherwise." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:463 +msgid "Full example" +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:465 +msgid "" +"The following example is a passthrough driver that forwards the calls to " +"the SWIG Python GDAL API. It has no practical use, and is just intended " +"to show case most possible uses of the API. A real-world driver will only" +" use part of the API demonstrated. For example, the passthrough driver " +"implements attribute and spatial filters in a completely dummy way, by " +"calling back the C++ part of the driver. The " +"``iterator_honour_attribute_filter`` and " +"``iterator_honour_spatial_filter`` attributes, and the " +"``attribute_filter_changed`` and ``spatial_filter_changed`` method " +"implementations, could have omitted with the same result." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:474 +msgid "" +"The connection strings recognized by the drivers are " +"``PASSHTROUGH:connection_string_supported_by_non_python_drivers``. Note " +"that the prefixing by the driver name is absolutely not a requirement, " +"but something specific to this particular driver which is a bit " +"artificial (without the prefix, the connection string would go directly " +"to the native driver). The CityJSON driver mentioned in the :ref:`Other " +"examples <other_examples>` paragraph does not need it." +msgstr "" + +#: ../../source/tutorials/vector_python_driver.rst:633 +msgid "" +"Other examples, including a CityJSON driver, may be found at " +"https://github.com/OSGeo/gdal/tree/master/examples/pydrivers" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:5 +msgid "GDAL Warp API tutorial (Reprojection, ...)" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:10 +msgid "Overview" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:12 +msgid "" +"The GDAL Warp API (declared in :ref:`gdalwarper.h <gdalwarp_cpp>`) " +"provides services for high performance image warping using application " +"provided geometric transformation functions (GDALTransformerFunc), a " +"variety of resampling kernels, and various masking options. Files much " +"larger than can be held in memory can be warped." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:14 +msgid "" +"This tutorial demonstrates how to implement an application using the Warp" +" API. It assumes implementation in C++ as C and Python bindings are " +"incomplete for the Warp API. It also assumes familiarity with the " +":ref:`raster_data_model`, and the general GDAL API." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:16 +msgid "" +"Applications normally perform a warp by initializing a " +":cpp:class:`GDALWarpOptions` structure with the options to be utilized, " +"instantiating a GDALWarpOperation based on these options, and then " +"invoking the :cpp:func:`GDALWarpOperation::ChunkAndWarpImage` method to " +"perform the warp options internally using the :cpp:class:`GDALWarpKernel`" +" class." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:19 +msgid "A Simple Reprojection Case" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:20 +msgid "" +"First we will construct a relatively simple example for reprojecting an " +"image, assuming an appropriate output file already exists, and with " +"minimal error checking." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:70 +msgid "" +"This example opens the existing input and output files (in.tif and " +"out.tif). A :cpp:class:`GDALWarpOptions` structure is allocated " +"(:cpp:func:`GDALCreateWarpOptions` sets lots of sensible defaults for " +"stuff, always use it for defaulting things), and the input and output " +"file handles, and band lists are set. The panSrcBands and panDstBands " +"lists are dynamically allocated here and will be free automatically by " +":cpp:func:`GDALDestroyWarpOptions`. The simple terminal output progress " +"monitor (GDALTermProgress) is installed for reporting completion progress" +" to the user." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:72 +msgid "" +":cpp:func:`GDALCreateGenImgProjTransformer` is used to initialize the " +"reprojection transformation between the source and destination images. We" +" assume that they already have reasonable bounds and coordinate systems " +"set. Use of GCPs is disabled." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:74 +msgid "" +"Once the options structure is ready, a GDALWarpOperation is instantiated " +"using them, and the warp actually performed with " +":cpp:func:`GDALWarpOperation::ChunkAndWarpImage`. Then the transformer, " +"warp options and datasets are cleaned up." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:76 +msgid "" +"Normally error check would be needed after opening files, setting up the " +"reprojection transformer (returns NULL on failure), and initializing the " +"warp." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:79 +msgid "Other Warping Options" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:81 +msgid "" +"The GDALWarpOptions structures contains a number of items that can be set" +" to control warping behavior. A few of particular interest are:" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:83 +msgid "" +":cpp:member:`GDALWarpOptions::dfWarpMemoryLimit` - Set the maximum amount" +" of memory to be used by the GDALWarpOperation when selecting a size of " +"image chunk to operate on. The value is in bytes, and the default is " +"likely to be conservative (small). Increasing the chunk size can help " +"substantially in some situations but care should be taken to ensure that " +"this size, plus the GDAL cache size plus the working set of GDAL, your " +"application and the operating system are less than the size of RAM or " +"else excessive swapping is likely to interfere with performance. On a " +"system with 256MB of RAM, a value of at least 64MB (roughly 64000000 " +"bytes) is reasonable. Note that this value does not include the memory " +"used by GDAL for low level block caching." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:85 +msgid "" +":cpp:member:`GDALWarpOptions::eResampleAlg` - One of GRA_NearestNeighbour" +" (the default, and fastest), GRA_Bilinear (2x2 bilinear resampling) or " +"GRA_Cubic. The GRA_NearestNeighbour type should generally be used for " +"thematic or color mapped images. The other resampling types may give " +"better results for thematic images, especially when substantially " +"changing resolution." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:87 +msgid "" +":cpp:member:`GDALWarpOptions::padfSrcNoDataReal` - This array (one entry " +"per band being processed) may be setup with a \"nodata\" value for each " +"band if you wish to avoid having pixels of some background value copied " +"to the destination image." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:89 +msgid "" +":cpp:member:`GDALWarpOptions::papszWarpOptions` - This is a string list " +"of NAME=VALUE options passed to the warper. See the " +":cpp:member:`GDALWarpOptions::papszWarpOptions` docs for all options. " +"Supported values include:" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:91 +msgid "" +"INIT_DEST=[value] or INIT_DEST=NO_DATA: This option forces the " +"destination image to be initialized to the indicated value (for all " +"bands) or indicates that it should be initialized to the NO_DATA value in" +" padfDstNoDataReal/padfDstNoDataImag. If this value isn't set the " +"destination image will be read and the source warp overlaid on it." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:93 +msgid "" +"WRITE_FLUSH=YES/NO: This option forces a flush to disk of data after each" +" chunk is processed. In some cases this helps ensure a serial writing of " +"the output data otherwise a block of data may be written to disk each " +"time a block of data is read for the input buffer resulting in a lot of " +"extra seeking around the disk, and reduced IO throughput. The default at " +"this time is NO." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:96 +msgid "Creating the Output File" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:98 +msgid "" +"In the previous case an appropriate output file was already assumed to " +"exist. Now we will go through a case where a new file with appropriate " +"bounds in a new coordinate system is created. This operation doesn't " +"relate specifically to the warp API. It is just using the transformation " +"API." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:168 +msgid "Some notes on this logic:" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:170 +msgid "" +"We need to create the transformer to output coordinates such that the " +"output of the transformer is georeferenced, not pixel line coordinates " +"since we use the transformer to map pixels around the source image into " +"destination georeferenced coordinates." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:172 +msgid "" +"The :cpp:func:`GDALSuggestedWarpOutput` function will return an " +"adfDstGeoTransform, nPixels and nLines that describes an output image " +"size and georeferenced extents that should hold all pixels from the " +"source image. The resolution is intended to be comparable to the source, " +"but the output pixels are always square regardless of the shape of input " +"pixels." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:174 +msgid "" +"The warper requires an output file in a format that can be \"randomly\" " +"written to. This generally limits things to uncompressed formats that " +"have an implementation of the Create() method (as opposed to " +"CreateCopy()). To warp to compressed formats, or CreateCopy() style " +"formats it is necessary to produce a full temporary copy of the image in " +"a better behaved format, and then CreateCopy() it to the desired final " +"format." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:176 +msgid "" +"The Warp API copies only pixels. All color maps, georeferencing and other" +" metadata must be copied to the destination by the application." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:179 +msgid "Performance Optimization" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:181 +msgid "" +"There are a number of things that can be done to optimize the performance" +" of the warp API:" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:183 +msgid "" +"Increase the amount of memory available for the Warp API chunking so that" +" larger chunks can be operated on at a time. This is the " +":cpp:member:`GDALWarpOptions::dfWarpMemoryLimit` parameter. In theory the" +" larger the chunk size operated on the more efficient the I/O strategy, " +"and the more efficient the approximated transformation will be. However, " +"the sum of the warp memory and the GDAL cache should be less than RAM " +"size, likely around 2/3 of RAM size." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:185 +msgid "" +"Increase the amount of memory for GDAL caching. This is especially " +"important when working with very large input and output images that are " +"scanline oriented. If all the input or output scanlines have to be re-" +"read for each chunk they intersect performance may degrade greatly. Use " +":cpp:func:`GDALSetCacheMax` to control the amount of memory available for" +" caching within GDAL." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:187 +msgid "" +"Use an approximated transformation instead of exact reprojection for each" +" pixel to be transformed. This code illustrates how an approximated " +"transformation could be created based on a reprojection transformation, " +"but with a given error threshold (dfErrorThreshold in output pixels)." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:196 +msgid "" +"When writing to a blank output file, use the INIT_DEST option in the " +":cpp:member:`GDALWarpOptions::papszWarpOptions` to cause the output " +"chunks to be initialized to a fixed value, instead of being read from the" +" output. This can substantially reduce unnecessary IO work." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:198 +msgid "" +"Use tiled input and output formats. Tiled formats allow a given chunk of " +"source and destination imagery to be accessed without having to touch a " +"great deal of extra image data. Large scanline oriented files can result " +"in a great deal of wasted extra IO." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:200 +msgid "" +"Process all bands in one call. This ensures the transformation " +"calculations don't have to be performed for each band." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:202 +msgid "" +"Use the :cpp:func:`GDALWarpOperation::ChunkAndWarpMulti` method instead " +"of :cpp:func:`GDALWarpOperation::ChunkAndWarpImage`. It uses a separate " +"thread for the IO and the actual image warp operation allowing more " +"effective use of CPU and IO bandwidth. For this to work GDAL needs to " +"have been built with multi-threading support (default on Win32, default " +"on Unix, for previous versions -with-threads was required in configure)." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:204 +msgid "" +"The resampling kernels vary in work required from nearest neighbour being" +" least complex, to more complex with bilinear and then cubic. Don't use a" +" more complex resampling kernel than needed." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:206 +msgid "" +"Avoid use of esoteric masking options so that special simplified logic " +"case be used for common special cases. For instance, nearest neighbour " +"resampling with no masking on 8bit data is highly optimized compared to " +"the general case." +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:209 +msgid "Other Masking Options" +msgstr "" + +#: ../../source/tutorials/warp_tut.rst:211 +msgid "" +"The GDALWarpOptions include a bunch of esoteric masking capabilities, for" +" validity masks, and density masks on input and output. Some of these are" +" not yet implemented and others are implemented but poorly tested. Other " +"than per-band validity masks it is advised that these features be used " +"with caution at this time." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:5 +msgid "OGC WKT Coordinate System Issues" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:7 +msgid "" +"This document is intended to discuss some issues that arise in attempting" +" to use OpenGIS Well Known Text descriptions of coordinate systems. It " +"discusses various vendor implementations and issues between the original " +"`\"Simple Features\" specification (ie. SF-SQL 99-049) " +"<http://portal.opengeospatial.org/files/?artifact_id=829>`__ and the " +"newer `Coordinate Transformation Services (CT) specification (01-009) " +"<http://portal.opengeospatial.org/files/?artifact_id=999>`__ which " +"defines an extended form of WKT." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:17 +msgid "WKT Implementations" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:19 +msgid "" +"At this time I am aware of at least the following software packages that " +"use some form of WKT internally, or for interchange of coordinate system " +"descriptions:" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:23 +msgid "Oracle Spatial (WKT is used internally in MDSYS.WKT, loosely SFSQL based)" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:25 +msgid "" +"ESRI - The Arc8 system's projection engine uses a roughly simple features" +" compatible description for projections. I believe ESRI provided the WKT " +"definition for the simple features spec." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:28 +msgid "" +"Cadcorp - Has the ability to read and write CT 1.0 style WKT. Cadcorp " +"wrote the CT spec." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:30 +msgid "" +"OGR/GDAL - reads/writes WKT as its internal coordinate system description" +" format. Attempts to support old and new forms as well as forms from " +"ESRI." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:33 +msgid "FME - Includes WKT read/write capabilities built on OGR." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:34 +msgid "MapGuide - Uses WKT in the SDP data access API. Roughly SF compliant." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:35 +msgid "" +"PostGIS - Keeps WKT in the spatial_ref_sys table, but it is up to clients" +" to translate to PROJ.4 format for actual use. I believe the " +"spatial_ref_sys table is populated using OGR generated translations." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:40 +msgid "Projection Parameters" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:42 +msgid "" +"The various specs do not list a set of projections, and the parameters " +"associated with them. This leads to various selection of parameter names " +"(and sometimes projection names) from different vendors. I have attempted" +" to maintain a list of WKT bindings for different projections as part of " +"my `GeoTIFF Projections List <https://gdal.org/proj_list>`__ registry. " +"Please try to adhere to the projection names and parameters listed there." +" That list also tries to relate the projections to the GeoTIFF, EPSG and " +"PROJ.4 formulations where possible." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:52 +msgid "" +"The one case where it isn't followed by a vendor that I am aware of ESRIs" +" definition of Lambert Conformal Conic. In EPSG there is a 1SP and a 2SP " +"form of this. ESRI merges them, and just have different parameters " +"depending on the type." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:57 +msgid "" +"One other issue is that the CT specification does explicitly list " +"parameters for the Transverse Mercator, LCC 1SP and LCC 2SP projections; " +"however, it lists standard_parallel1 and standard_parallel2 as parameters" +" for LCC 2SP which conflicts with the existing usage of " +"standard_parallel_1 and standard_parallel_2 and conflicts with examples " +"in the same CT spec. My position is that the table in section 10.x of the" +" CT spec is in error and that the widely used form is correct. Note that " +"the table in the CT spec conflicts with other examples in the same spec." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:67 +msgid "" +"A third issue is the formulation for Albers. While I have used " +"longitude_of_center and latitude_of_center ESRI uses Central_meridian and" +" latitude_of_origin." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:71 +msgid "ESRI:" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:83 +msgid "OGR:" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:96 +msgid "Datum Names" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:98 +msgid "" +"In Simple Features style WKT, the name associated with a datum is the " +"only way to identify the datum. In CT WKT the datum can also have a " +"TOWGS84 parameter indicating its relationship to WGS84, and an AUTHORITY " +"parameter relating it to EPSG or some other authority space. However, in " +"SF WKT the name itself is the only key." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:104 +msgid "" +"By convention OGR and Cadcorp have translated the datum names in a " +"particular way from the EPSG database in order to produce comparible " +"names. The rule is to convert all non alphanumeric characters to " +"underscores, then to strip any leading, trailing or repeating " +"underscores. This produces well behaved datum names like " +"\"Nouvelle_Triangulation_Francaise\"." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:111 +msgid "" +"However, other vendors have done different things. ESRI seems to follow a" +" similar convention but prefixes all datum names with \"D\\_\" as well, " +"giving names like \"D_WGS_1972\". Also they have lots of other " +"differences for reasons that are not clear. For instance for what Cadcorp" +" and OGR call \"Nouvelle_Triangulation_Francaise\", they call it " +"\"D_NTF\". Oracle appears to use the raw names without cleanup. So for " +"NTF they use \"NTF (Paris meridian)\"." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:119 +msgid "" +"The short result of this is that it is almost impossible to recognise and" +" compare datums between different Simple Features implementations, though" +" I have had some success in translating ESRI datum names to match " +"Cadcorp/OGR conventions, with some special casing." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:125 +msgid "Parameter Ordering" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:127 +msgid "" +"It is worthwhile keeping in mind that the BNF grammars for WKT in the SF " +"specs, and the CT spec imply specific orders for most items. For instance" +" the BNF for the PROJCS item in the CT spec is" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:136 +msgid "" +"This clearly states that the PROJECTION keyword follows the GEOGCS, " +"followed by the UNIT, AXIS and AUTHORITY items. Providing them out of " +"order is technically a violation of the spec. On the other hand, WKT " +"consumers are encouraged to be flexible on ordering." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:142 +msgid "Units of PARAMETERs" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:144 +msgid "" +"The linear PARAMETER values in a PROJCS must be in terms of the linear " +"units for that PROJCS. I think the only linear units are the false " +"easting and northing type values. Thus, in common cases like a state " +"plane zone in feet, the false easting and northing will also be in feet." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:149 +msgid "" +"The angular PARAMETER values in a PROJCS must be in terms of the angular " +"units of the GEOGCS. If the GEOGCS is in gradians, for instance, then all" +" the projection angles must also be in gradians!" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:154 +msgid "Units of PRIMEM" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:156 +msgid "What units should the prime meridian appear in?" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:158 +msgid "" +"The CT 1.0 specification (7.3.14 PRIMEM) says *\"The units of the must be" +" inferred from the context. If the PRIMEM clause occurs inside a GEOGCS, " +"then the longitude units will match those of the geographic coordinate " +"system.\"* Note: for a geocentric coordinate system, it says *\"If the " +"PRIMEM clause occurs inside a GEOCCS, then the units will be in " +"degrees\"*." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:164 +msgid "" +"The SF-SQL spec (99-049) does not attempt to address the issue of units " +"of the prime meridian." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:166 +msgid "" +"Existing ESRI EPSG translation to WKT uses degrees for prime meridian, " +"even when the GEOGCS is in gradians as shown in their translation of EPSG" +" 4807:" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:178 +msgid "" +"OGR implements the same interpretation as ESRI for its " +"OGRSpatialReference class: the PRIMEM longitude is always in degrees. See" +" `GDAL Ticket #4524 <https://trac.osgeo.org/gdal/ticket/4524>`__" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:196 +msgid "" +"Cadcorp implements according to the CT 1.0 specification as shown in " +"their translation of EPSG 4807:" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:215 +msgid "" +"Oracle Spatial 8.1.7 uses the following definition for what I assume is " +"supposed to be EPSG 4807. Interestingly it does not bother with using " +"gradians, and it appears that the prime meridian is expressed in radians " +"with very low precision!" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:229 +msgid "Sign of TOWGS84 Rotations" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:232 +msgid "Discussion" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:234 +msgid "" +"In EPSG there are two methods of defining the 7 parameter Bursa-Wolf " +"parameters, 9606 (position vector 7-parameter) and 9607 (coordinate frame" +" rotation). The only difference is that the sign of the rotation " +"coefficients is reversed between them." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:239 +msgid "" +"I (Frank Warmerdam) had somehow convinced myself that the TOWGS84 values " +"in WKT were supposed to be done using the sense in 9606 (position vector " +"7-parameter) and that if I read a 9607 I would need to switch the " +"rotation signs before putting it into a TOWGS84 chunk in WKT." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:244 +msgid "" +"However, I see in the WKT dump you (Martin from Cadcorp) sent me you are " +"using the 9607 sense. For instance, this item appears to use 9607 values " +"directly without switching the sign." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:259 +msgid "" +"I read over the TOWGS84[] clause in the 1.0 CT spec, and it just talks " +"about them being the Bursa Wolf transformation parameters (on page 22, " +"7.3.18). I also scanned through to 12.3.15.2 and 12.3.27 and they are " +"nonspecific as to the handedness of the TOWGS84 rotations." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:264 +msgid "" +"I am seeking a clarification of whether TOWGS84 matches EPSG 9606 or EPSG" +" 9607. Furthermore, I would like to see any future rev of the spec " +"clarify this, referencing the EPSG method definitions." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:268 +msgid "" +"Martin wrote back that he was uncertain on the correct signage and that " +"the Adam had programmed the Cadcorp implementation empirically, according" +" to what seemed to work for the test data available." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:272 +msgid "" +"I am prepared to adhere to the Cadorp sign usage (as per EPSG 9607) if " +"this can be clarified in the specification." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:276 +msgid "Current state of OGR implementation" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:278 +msgid "" +"OGR imports from/exports to WKT assumes EPSG 9606 convention (position " +"vector 7-parameter), as `proj does <https://proj.org/>`__." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:282 +msgid "" +"When importing from EPSG parameters expressed with EPSG 9607, it does the" +" appropriate conversion (negating the sign of the rotation terms)." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:286 +msgid "Longitudes Relative to PRIMEM?" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:288 +msgid "" +"Another related question is whether longtiudinal projection parameters " +"(ie. central meridian) are relative to the GEOGCS prime meridian or " +"relative to greenwich. While the simplest approach is to treat all " +"longitudes as relative to Greenwich, I somehow convinced myself at one " +"point that the longitudes were intended to be relative to the prime " +"meridian. However, a review of 7.3.11 (describing PARAMETER) in the CT " +"1.0 spec provides no support for this opinion, and an inspection of EPSG " +"25700 in Cadcorp also suggests that the central meridian is relative to " +"greenwich, not the prime meridian." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:327 +msgid "" +"Based on this, I am proceeding on the assumption that while parameters " +"are in the units of the GEOGCS they are not relative the GEOGCS prime " +"meridian." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:332 +msgid "Numerical Precision in WKT" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:334 +msgid "" +"The specification does not address the precision to which values in WKT " +"should be stored. Some implementations, such as Oracles apparently, use " +"rather limited precision for parameters such as Scale Factor making it " +"difficult to compare coordinate system descriptions or even to get " +"comparable numerical results." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:340 +#, python-format +msgid "" +"The best practice is to preserve the original precision as specified in " +"the source database, such as EPSG where possible. Given that many systems" +" do not track precision, at least it is advisable to produce values with " +"the equivalent of the C \"%.16g\" format, maintaining 16 digits of " +"precision, capturing most of the precision of a double precision IEEE " +"floating point value." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:348 +msgid "Other Notes" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:350 +msgid "" +"ESRI seems to use Equidistant_Cylindrical for what I know as " +"Equirectangular." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:355 +msgid "History" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:357 +msgid "" +"2018: Even Rouault: make it clear that OGR implements EPSG 9606 " +"convention for TOWGS84." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:359 +msgid "" +"2018: Even Rouault: remove mention about CT 1.0 specification (7.3.14 " +"PRIMEM) having an error, and explicitly mentions that OGR uses degrees " +"for PRIMEM longitude." +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:362 +msgid "2018: Even Rouault: add hyperlinks" +msgstr "" + +#: ../../source/tutorials/wktproblems.rst:363 +msgid "" +"2007 or before: Originally written by `Frank Warmerdam " +"<https://web.archive.org/web/20130728081442/http://pobox.com/~warmerdam>`__." +msgstr "" + diff --git a/doc/source/locale/ja/LC_MESSAGES/user.mo b/doc/source/locale/ja/LC_MESSAGES/user.mo new file mode 100644 index 0000000000000000000000000000000000000000..e2267788ba9b0b286d5bc42a09828116e4c130f8 GIT binary patch literal 415 zcmYk2&rZTX5XLd_)T3t)bMS_PTO^9hpHOJQCM_kUn&@qTrIwW4y4@Oi5MR${ajQn0 zWRm%2f0=J~KF>}+8YWImo}0X=#lN^T^{aWry0=hr$JZMD4L)*JW>Qd?xlRC9%nPYB zhGm*<a9pJ&CX#}+h!UJA&a^?%WtvlHlXeHmEfO2ZHSOFq$sHjE#F)Qj^~hiD$#Y^1 zBXk|Ok7(#OpQE{F1+3JVC??9BX{jhoAA$hpPUu133mrcgIj$Rf%jM9ZBCS|zEO+cr zV8YqH?m#~XMtRnfDjiyjyizR3sZ{%tf+)UaIk0>1Qw~Va3jNSK{@QL4Ya)f_!mM*B zjEUy&`l`rTCVH@bVXEYMQ0Xmpk6gX>mMiqcT5d9tQs}NSZOypg%G|~r?m%J8Ry>Dx J%kCJ9#urd-cUS-b literal 0 HcmV?d00001 diff --git a/doc/source/locale/ja/LC_MESSAGES/user.po b/doc/source/locale/ja/LC_MESSAGES/user.po new file mode 100644 index 000000000000..f095abb9da16 --- /dev/null +++ b/doc/source/locale/ja/LC_MESSAGES/user.po @@ -0,0 +1,7545 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 1998-2024 +# This file is distributed under the same license as the GDAL package. +# FIRST AUTHOR <EMAIL@ADDRESS>, 2024. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: GDAL \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-07-01 03:46+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language: ja\n" +"Language-Team: ja <LL@li.org>\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.14.0\n" + +#: ../../source/user/configoptions.rst:5 +msgid "Configuration options" +msgstr "" + +#: ../../source/user/configoptions.rst:7 +msgid "" +"This page discusses runtime configuration options for GDAL. These are " +"distinct from options to the build-time configure script. Runtime " +"configuration options apply on all platforms, and are evaluated at " +"runtime. They can be set programmatically, by commandline switches or in " +"the environment by the user." +msgstr "" + +#: ../../source/user/configoptions.rst:12 +msgid "" +"Configuration options are normally used to alter the default behavior of " +"GDAL/OGR drivers and in some cases the GDAL/OGR core. They are " +"essentially global variables the user can set." +msgstr "" + +#: ../../source/user/configoptions.rst:17 +msgid "How to set configuration options?" +msgstr "" + +#: ../../source/user/configoptions.rst:19 +msgid "" +"One example of a configuration option is the :config:`GDAL_CACHEMAX` " +"option. It controls the size of the GDAL block cache, in megabytes. It " +"can be set in the environment on Unix (bash/bourne) shell like this:" +msgstr "" + +#: ../../source/user/configoptions.rst:29 +msgid "In a DOS/Windows command shell it is done like this:" +msgstr "" + +#: ../../source/user/configoptions.rst:35 +msgid "" +"It can also be set on the commandline for most GDAL and OGR utilities " +"with the ``--config`` switch, though in a few cases these switches are " +"not evaluated in time to affect behavior." +msgstr "" + +#: ../../source/user/configoptions.rst:43 +msgid "" +"Since GDAL 3.9, it is also possible to set a config option in a more " +"conventional way by using a single ``<NAME>``=``<VALUE>`` command line " +"string instead of having ``<NAME>`` and ``<VALUE>`` as two space-" +"separated strings." +msgstr "" + +#: ../../source/user/configoptions.rst:51 +msgid "" +"In C/C++ configuration switches can be set programmatically with " +":cpp:func:`CPLSetConfigOption`:" +msgstr "" + +#: ../../source/user/configoptions.rst:60 +msgid "" +"Normally a configuration option applies to all threads active in a " +"program, but they can be limited to only the current thread with " +":cpp:func:`CPLSetThreadLocalConfigOption`" +msgstr "" + +#: ../../source/user/configoptions.rst:68 +msgid "" +"For boolean options, the values YES, TRUE or ON can be used to turn the " +"option on; NO, FALSE or OFF to turn it off." +msgstr "" + +#: ../../source/user/configoptions.rst:75 +msgid "GDAL configuration file" +msgstr "" + +#: ../../source/user/configoptions.rst:79 +msgid "" +"On driver registration, loading of configuration is attempted from a set " +"of predefined files." +msgstr "" + +#: ../../source/user/configoptions.rst:82 +msgid "" +"The following locations are tried by " +":cpp:func:`CPLLoadConfigOptionsFromPredefinedFiles`:" +msgstr "" + +#: ../../source/user/configoptions.rst:84 +msgid "" +"the location pointed by the environment variable (or configuration " +"option) :config:`GDAL_CONFIG_FILE` is attempted first. If it is set, the " +"next steps are not attempted" +msgstr "" + +#: ../../source/user/configoptions.rst:88 +msgid "" +"for Unix builds, the location pointed by ${sysconfdir}/gdal/gdalrc is " +"first attempted (where ${sysconfdir} evaluates to ${prefix}/etc, unless " +"the ``--sysconfdir`` switch of ./configure has been invoked). Then " +"$(HOME)/.gdal/gdalrc is tried, potentially overriding what was loaded " +"with the sysconfdir" +msgstr "" + +#: ../../source/user/configoptions.rst:93 +msgid "" +"for Windows builds, the location pointed by $(USERPROFILE)/.gdal/gdalrc " +"is attempted." +msgstr "" + +#: ../../source/user/configoptions.rst:96 +msgid "" +"A configuration file is a text file in a .ini style format. Lines " +"starting with `#` are comment lines." +msgstr "" + +#: ../../source/user/configoptions.rst:99 +msgid "" +"The file may contain a ``[configoptions]`` section, that lists " +"configuration options and their values." +msgstr "" + +#: ../../source/user/configoptions.rst:102 +#: ../../source/user/configoptions.rst:136 +#: ../../source/user/virtual_file_systems.rst:14 +msgid "Example:" +msgstr "" + +#: ../../source/user/configoptions.rst:111 +msgid "" +"Configuration options set in the configuration file can later be " +"overridden by calls to :cpp:func:`CPLSetConfigOption` or " +":cpp:func:`CPLSetThreadLocalConfigOption`, or through the ``--config`` " +"command line switch." +msgstr "" + +#: ../../source/user/configoptions.rst:115 +msgid "" +"The value of environment variables set before GDAL starts will be used " +"instead of the value set in the configuration files, unless, starting " +"with GDAL 3.6, the configuration file starts with a ``[directives]`` " +"section that contains a ``ignore-env-variables=yes`` entry." +msgstr "" + +#: ../../source/user/configoptions.rst:129 +msgid "" +"Starting with GDAL 3.5, a configuration file can also contain credentials" +" (or more generally options related to a virtual file system) for a given" +" path prefix, that can also be set with " +":cpp:func:`VSISetPathSpecificOption`. Credentials should be put under a " +"``[credentials]`` section, and for each path prefix, under a relative " +"subsection whose name starts with \"[.\" (e.g. " +"\"[.some_arbitrary_name]\"), and whose first key is \"path\"." +msgstr "" + +#: ../../source/user/configoptions.rst:154 +msgid "Global configuration options" +msgstr "" + +#: ../../source/user/configoptions.rst:157 +msgid "Logging" +msgstr "" + +#: ../../source/user/configoptions.rst:175 +msgid "" +"At the commandline this can also be set with --debug <value> as well as " +"with --config CPL_DEBUG <value>." +msgstr "" + +#: ../../source/user/configoptions.rst:202 +msgid "Performance and caching" +msgstr "" + +#: ../../source/user/configoptions.rst:257 +msgid "" +"Number of datasets that can be opened simultaneously by the GDALProxyPool" +" mechanism (used by VRT for example). Can be increased to get better " +"random I/O performance with VRT mosaics made of numerous underlying " +"raster files. Be careful: on Linux systems, the number of file handles " +"that can be opened by a process is generally limited to 1024. This is " +"currently clamped between 2 and 1000." +msgstr "" + +#: ../../source/user/configoptions.rst:269 +#, python-format +msgid "" +"The value can also be suffixed with ``MB`` or ``GB`` to respectively " +"express it in megabytes or gigabytes. The default value is 25% of the " +"usable physical RAM minus the :config:`GDAL_CACHEMAX` value." +msgstr "" + +#: ../../source/user/configoptions.rst:278 +msgid "" +"Size of the swath when copying raster data from one dataset to another " +"one (in bytes). Should not be smaller than :config:`GDAL_CACHEMAX`." +msgstr "" + +#: ../../source/user/configoptions.rst:292 +msgid "" +"If set to EMPTY_DIR, only the file that is being opened will be seen when" +" a GDAL driver will request sibling files, so this is a way to disable " +"loading side-car/auxiliary files." +msgstr "" + +#: ../../source/user/configoptions.rst:312 +msgid "" +"When enabled, this cache is used for most I/O in GDAL, including local " +"files." +msgstr "" + +#: ../../source/user/configoptions.rst:323 +msgid "Driver management" +msgstr "" + +#: ../../source/user/configoptions.rst:330 +msgid "" +"This option can be used to unregister one or several GDAL drivers. This " +"can be useful when a driver tries to open a dataset that it should not " +"recognize, or when several drivers are built-in that can open the same " +"datasets (for example JP2MrSID, JP2ECW, JPEG2000 and JP2KAK for JPEG2000 " +"datasets). The value of this option must be a space delimited list of the" +" short name of the GDAL drivers to unregister." +msgstr "" + +#: ../../source/user/configoptions.rst:337 +msgid "" +"This option must be set before calling :cpp:func:`GDALAllRegister`, or an" +" explicit call to :cpp:func:`GDALDriverManager::AutoSkipDrivers` will be " +"required." +msgstr "" + +#: ../../source/user/configoptions.rst:354 +msgid "" +"This function will automatically load drivers from shared libraries. It " +"searches the \"driver path\" for .so (or .dll) files that start with the " +"prefix \"gdal_X.so\". It then tries to load them and then tries to call a" +" function within them called GDALRegister_X() where the 'X' is the same " +"as the remainder of the shared library basename ('X' is case sensitive), " +"or failing that to call GDALRegisterMe()." +msgstr "" + +#: ../../source/user/configoptions.rst:361 +msgid "" +"There are a few rules for the driver path. If the ``GDAL_DRIVER_PATH`` " +"environment variable it set, it is taken to be a list of directories to " +"search separated by colons on UNIX, or semi-colons on Windows. Otherwise " +"the /usr/local/lib/gdalplugins directory, and (if known) the " +"lib/gdalplugins subdirectory of the gdal home directory are searched on " +"UNIX and $(BINDIR)\\gdalplugins on Windows." +msgstr "" + +#: ../../source/user/configoptions.rst:368 +msgid "" +"Auto loading can be completely disabled by setting the " +"``GDAL_DRIVER_PATH`` config option to \"disable\"." +msgstr "" + +#: ../../source/user/configoptions.rst:371 +msgid "" +"This option must be set before calling :cpp:func:`GDALAllRegister`, or an" +" explicit call to :cpp:func:`GDALDriverManager::AutoLoadDrivers` will be " +"required." +msgstr "" + +#: ../../source/user/configoptions.rst:381 +msgid "General options" +msgstr "" + +#: ../../source/user/configoptions.rst:389 +msgid "" +"This option is read by the GDAL and OGR driver registration functions. It" +" is used to expand EPSG codes into their description in the OSR model " +"(WKT based)." +msgstr "" + +#: ../../source/user/configoptions.rst:393 +msgid "" +"On some builds (Unix), the value can be hard-coded at compilation time to" +" point to the path after installation (/usr/share/gdal/data for example)." +" On Windows platform, this option must be generally declared." +msgstr "" + +#: ../../source/user/configoptions.rst:487 +msgid "" +"Can be set to YES to use Erdas Imagine format (.aux) as overview format. " +"See :program:`gdaladdo` documentation." +msgstr "" + +#: ../../source/user/configoptions.rst:498 +msgid "Vector related options" +msgstr "" + +#: ../../source/user/configoptions.rst:508 +msgid "" +"The approximation of arcs as linestrings is done by splitting the arcs " +"into subarcs of no more than the angle specified by this option." +msgstr "" + +#: ../../source/user/configoptions.rst:533 +msgid "" +"``DEFAULT``: perform a full analysis of the topological relationships " +"between all rings, classifying them as shells or holes and associating " +"them according to the OGC Simple Features convention. If the topological " +"analysis determines that a valid geometry cannot be constructed, the " +"result will be the same as with :config:`OGR_ORGANIZE_POLYGONS=SKIP`." +msgstr "" + +#: ../../source/user/configoptions.rst:539 +msgid "" +"``ONLY_CCW``: assume that rings with clockwise orientation represent " +"shells and rings with counterclockwise orientation represent holes. " +"Perform a limited topological analysis to determine which shell contains " +"each hole. The Shapefile driver defaults to this method." +msgstr "" + +#: ../../source/user/configoptions.rst:544 +msgid "" +"``CCW_INNER_JUST_AFTER_CW_OUTER``: assume that rings with clockwise " +"orientation represent shells and rings with counterclockwise orientation " +"represent holes and immediately follow the outer ring with which they are" +" associated." +msgstr "" + +#: ../../source/user/configoptions.rst:549 +msgid "" +"``SKIP``: avoid attempting to classify rings as shells or holes. A single" +" geometry (Polygon/MultiPolygon/CurvePolygon/MultiSurface) will be " +"returned with all polygons as top-level polygons. If non-polygonal " +"elements are present, a GeometryCollection will be returned." +msgstr "" + +#: ../../source/user/configoptions.rst:569 +msgid "" +"Those XML based drivers should write UTF8 content. If they are provided " +"with non UTF8 content, they will replace each non-ASCII character by '?' " +"when OGR_FORCE_ASCII=YES." +msgstr "" + +#: ../../source/user/configoptions.rst:573 +msgid "" +"Set to NO to preserve the content, but beware that the resulting XML file" +" will not be valid and will require manual edition of the encoding in the" +" XML header." +msgstr "" + +#: ../../source/user/configoptions.rst:592 +msgid "Networking options" +msgstr "" + +#: ../../source/user/configoptions.rst:601 +msgid "For example:" +msgstr "" + +#: ../../source/user/configoptions.rst:870 +msgid "" +"When using NTLM, you can set the domain by prepending it to the user name" +" and separating the domain and name with a forward (/) or backward slash " +"(\\). Like this: \"domain/user:password\" or \"domain\\user:password\". " +"Some HTTP servers (on Windows) support this style even for Basic " +"authentication." +msgstr "" + +#: ../../source/user/configoptions.rst:897 +msgid "" +"GDAL respects the environment variables http_proxy, ftp_proxy, all_proxy " +"etc, if any of those are set. GDAL_HTTP_PROXY option does however " +"override any possibly set environment variables." +msgstr "" + +#: ../../source/user/configoptions.rst:943 +msgid "Persistent Auxiliary Metadata (PAM) options" +msgstr "" + +#: ../../source/user/configoptions.rst:963 +msgid "PROJ options" +msgstr "" + +#: ../../source/user/configoptions.rst:972 +msgid "" +"This option can be used to control the behavior of gdalwarp when warping " +"global datasets or when transforming from/to polar projections, which " +"causes coordinate discontinuities. See " +"http://trac.osgeo.org/gdal/ticket/2305." +msgstr "" + +#: ../../source/user/configoptions.rst:976 +msgid "" +"The background is that PROJ does not guarantee that converting from " +"src_srs to dst_srs and then from dst_srs to src_srs will yield to the " +"initial coordinates. This can lead to errors in the computation of the " +"target bounding box of gdalwarp, or to visual artifacts." +msgstr "" + +#: ../../source/user/configoptions.rst:981 +msgid "" +"If CHECK_WITH_INVERT_PROJ option is not set, gdalwarp will check that the" +" the computed coordinates of the edges of the target image are in the " +"validity area of the target projection. If they are not, it will retry " +"computing them by setting :config:`CHECK_WITH_INVERT_PROJ=TRUE` that " +"forces ogrct.cpp to check the consistency of each requested projection " +"result with the invert projection." +msgstr "" + +#: ../../source/user/configoptions.rst:987 +msgid "If set to NO, gdalwarp will not attempt to use the invert projection." +msgstr "" + +#: ../../source/user/configoptions.rst:994 +msgid "" +"Used in combination with :config:`CHECK_WITH_INVERT_PROJ=TRUE`. Define " +"the acceptable threshold used to check if the roundtrip from src_srs to " +"dst_srs and from dst_srs to srs_srs yield to the initial coordinates. The" +" value must be expressed in the units of the source SRS (typically " +"degrees for a geographic SRS, meters for a projected SRS)" +msgstr "" + +#: ../../source/user/configoptions.rst:1007 +msgid "" +"Can be set to YES to remove points that cannot be reprojected. This can " +"for example help reproject lines that have an extremity at a pole, when " +"the reprojection does not support coordinates at poles." +msgstr "" + +#: ../../source/user/configoptions.rst:1071 +msgid "List of configuration options and where they are documented" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:5 +msgid "Coordinate epoch support" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:10 +msgid "Dynamic CRS and coordinate epoch" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:12 +msgid "" +"This document is intended to document the support for coordinate epoch, " +"linked to dynamic CRS." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:15 +msgid "" +"In a dynamic CRS, coordinates of a point on the surface of the Earth may " +"change with time. To be unambiguous the coordinates must always be " +"qualified with the epoch at which they are valid. The coordinate epoch is" +" not necessarily the epoch at which the observation was collected." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:20 +msgid "" +"Examples of dynamic CRS are ``WGS 84 (G1762)``, ``ITRF2014``, " +"``ATRF2014``." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:22 +msgid "" +"The generic EPSG:4326 WGS 84 CRS is also considered dynamic, although it " +"is not recommended to use it due to being based on a datum ensemble whose" +" positional accuracy is 2 meters, but prefer one of its realizations, " +"such as WGS 84 (G1762)" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:26 +msgid "" +"The :cpp:func:`OGRSpatialReference::IsDynamic` method can be used to test" +" if a CRS is a dynamic one." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:29 +msgid "" +"The :cpp:func:`OGRSpatialReference::SetCoordinateEpoch` and " +":cpp:func:`OGRSpatialReference::GetCoordinateEpoch` methods can be used " +"to set/retrieve a coordinate epoch associated with a CRS. The coordinate " +"epoch is expressed as a decimal year (e.g. 2021.3 for April 21, 2021)." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:34 +msgid "" +"Formally, the coordinate epoch of an observation belongs to the " +"observation. However, almost all formats do not allow for storing per-" +"observation epoch, and typical usage is a set of observations with the " +"same epoch. Therefore we store the epoch as property of the CRS, and " +"assume that it is valid for every observation. This choice eases " +"processing, storage and format complexity for most usage. For now, this " +"means that a dataset containing observations or points with different " +"epochs cannot be handled." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:42 +msgid "" +"For vector formats, per-geometry coordinate epoch could also make sense, " +"but as most formats only support a per-layer CRS, we also for now limit " +"support of coordinate epoch at the layer level. The underlying coordinate" +" transformation mechanics can support per-vertex coordinate epoch." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:48 +msgid "Support in raster and vector formats" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:50 +msgid "" +"At time of writing, no formats handled by GDAL/OGR have a standardized " +"way of encoding a coordinate epoch. We consequently have made choices how" +" to encode it, with the aim of being as much as possible backward " +"compatible with existing readers. Those encodings might change if " +"corresponding official specifications evolve to take this concept into " +"account. The coordinate epoch is only written when attached to the SRS of" +" the layer/dataset that is created." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:59 +msgid "FlatGeoBuf" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:61 +msgid "" +"The coordinate epoch is encoded as a WKT:2019 string using the ``EPOCH`` " +"subnode of the `COORDINATEMETADATA " +"<http://docs.opengeospatial.org/is/18-010r7/18-010r7.html#130>`__ " +"construct, set in the ``Crs.wkt`` header field of the FlatGeoBuf file." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:82 +msgid "" +"Such construct will not be understood by GDAL < 3.4, but if the CRS has " +"an associated EPSG code, this will not cause issues in those older GDAL " +"versions." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:87 +msgid "GeoPackage vector/raster" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:89 +msgid "" +"Each vector/raster table which has an associated coordinate epoch encodes" +" it in the ``epoch`` column of the ``gpkg_spatial_ref_sys`` table, using " +"an extended version of the CRS WKT extension " +"(https://github.com/opengeospatial/geopackage/pull/600)." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:94 +msgid "GeoTIFF" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:96 +msgid "" +"The coordinate epoch is encoded as a new GeoTIFF GeoKey, " +"``CoordinateEpochGeoKey`` of code 5120 and type DOUBLE." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:125 +#: ../../source/user/virtual_file_systems.rst:334 +msgid "JPEG2000" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:127 +msgid "GeoJP2 boxes use the above mentioned GeoTIFF encoding." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:131 +msgid "Persistent Auxiliary Metadata (.aux.xml)" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:133 +#: ../../source/user/coordinate_epoch.rst:146 +msgid "" +"The coordinate epoch is encoded as ``coordinateEpoch`` attribute of the " +"``SRS`` element." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:144 +msgid "GDAL VRT" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:159 +msgid "Support in utilities" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:161 +msgid "" +":program:`gdalinfo` and :program:`ogrinfo` report the coordinate epoch, " +"when attached to a dataset/layer SRS." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:164 +msgid "" +":program:`gdal_edit.py` has a ``-a_coord_epoch`` option to define the " +"epoch of a dataset in place." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:166 +msgid "" +":program:`gdal_translate` and :program:`ogr2ogr` have a " +"``-a_coord_epoch`` option to be used together with ``-a_srs``, and " +"otherwise preserve the coordinate epoch in the output SRS from the source" +" SRS when no SRS related options are specified." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:170 +msgid "" +":program:`gdalwarp` and :program:`ogr2ogr` have a ``-s_coord_epoch`` " +"option to be used together with ``-s_srs`` (resp. ``-t_coord_epoch`` " +"option to be used together with ``-t_srs``) to override/set the " +"coordinate epoch of the source (resp. target) CRS." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:174 +msgid "" +"Before PROJ 9.4, ``-s_coord_epoch`` and ``-t_coord_epoch`` were mutually " +"exclusive, due to lack of support for transformations between two dynamic" +" CRS." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:177 +msgid "" +":program:`gdalwarp` preserves the coordinate epoch in the output SRS when" +" appropriate." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:181 +msgid "Support in coordinate transformation" +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:183 +msgid "" +"The :cpp:class:`OGRCoordinateTransformation` class can perform time-" +"dependent transformations between a static and dynamic CRS based on the " +"coordinate epoch passed per vertex." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:187 +msgid "" +"It can also take into account the coordinate epoch associated with a " +"dynamic CRS, when doing time-dependent transformations between a static " +"and dynamic CRS. The :config:`OGR_CT_USE_SRS_COORDINATE_EPOCH` " +"configuration option can be set to ``NO`` to disable using the coordinate" +" epoch associated with the source or target CRS." +msgstr "" + +#: ../../source/user/coordinate_epoch.rst:193 +msgid "" +"If a per-vertex time is specified, it overrides the one associated with " +"the CRS." +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:5 +msgid "GDAL Python Utilities" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:7 +msgid "" +"The GDAL python utilities are included with GDAL. If you've installed " +"GDAL you already have them. However you may want to use a newer or older " +"version of the utilities without changing GDAL. This is where **gdal-" +"utils** comes in." +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:12 +msgid "" +"**gdal-utils**: is the GDAL Python Utilities *distribution*. This is what" +" you install. Its home page is https://pypi.org/project/gdal-utils/ . " +"Install with ``pip install gdal-utils``." +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:16 +msgid "" +"**osgeo_utils**: is the python *package*. This is what you use in your " +"code after installing, e.g. ``from osgeo_utils import ...``. If you're " +"not writing code, ignore it." +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:20 +msgid "Commonly used utilities include:" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:22 +msgid "gdal_merge" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:23 +msgid "gdal_edit" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:24 +msgid "gdal_calc" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:25 +msgid "ogrmerge" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:28 +msgid "Developers" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:30 +msgid "Read the :ref:`gdal-utils project charter <rfc-78>`." +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:32 +msgid "Clone or download the gdal project: https://github.com/OSGeo/gdal/" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:34 +msgid "" +"In your IDE set gdal-utils as the root folder, `.../swig/python/gdal-" +"utils <https://github.com/OSGeo/gdal/tree/master/swig/python/gdal-" +"utils/>`__." +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:37 +msgid "" +"**./osgeo_utils** - contains the Programs (those scripts that have launch" +" wrappers created by pip and added to PYTHONHOME/Scripts)" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:40 +msgid "" +"**./osgeo_utils/samples** - working python scripts but not typically " +"available in path (run them with ``python3 " +"path/to/samples/something.py``)" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:44 +msgid "" +"Improve the docs by editing the RST pages in `.../doc/source " +"<https://github.com/OSGeo/gdal/tree/master/doc/source>`__ which generate " +"the web pages:" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:48 +msgid "https://gdal.org/api/index.html#python-api" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:49 +msgid "https://gdal.org/programs/index.html#programs" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:50 +msgid "https://gdal.org/api/python_samples.html" +msgstr "" + +#: ../../source/user/gdal_python_utilities.rst:52 +msgid "" +"Contribute changes with `Pull Requests " +"<https://github.com/OSGeo/gdal/pulls>`__ from your fork to main GDAL " +"project and use *gdal-utils* label." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:5 +msgid "Geographic Networks Data Model" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:7 +msgid "" +"This document is intended to describe the purpose and the structure of " +"Geographic Network Model classes. GNM is the part of GDAL and provides " +"the methods of creating, managing and analysing geographical networks." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:9 +msgid "" +"The key purpose of GNM classes: - To provide an abstraction for different" +" existed network formats, like GDAL (previously OGR) provides one for " +"spatial vector formats; - To provide a network functionality to those " +"spatial formats which does not have it at all." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:14 +msgid "General concept" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:16 +msgid "" +"Any real-world network can be represented as a set of vector data, which " +"can be itself represented in GDAL as a GDALDataset. In GNM this data " +"consists of two parts. Network's topology (graph), network's metadata " +"(name/description), set of special feature identifiers, etc. belong to " +"the \"network part\", while the common for GDAL layers, features, " +"geometries belong to the \"spatial/attribute part\". In order to work " +"with the datasets of different formats the following classes were " +"designed in GNM." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:19 +msgid "Network" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:21 +msgid "" +":cpp:class:`GNMNetwork` represents an abstract network. The network data " +"and spatial/attribute data in a dataset of some format in fact can be not" +" separable (just additional layers/fields/tags), while the concrete " +"implementation of GNMNetwork \"knows\" which data from the whole dataset " +"refers to \"network part\" and is able to operate it. GNMNetwork allows " +"user the following:" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:23 +msgid "" +"-Setting/unsetting connections. These generic methods of building the " +"network topology (automatically and manually) receive the identifiers of " +"features being connected in a common way, while the concrete " +"implementation knows where and how to store and build the topology; " +"-Reading connections. The generic methods return the connections in the " +"common way; -Adding/removing layers/features. When the feature or layer " +"is being added to the network some actions can be initiated (weights " +"change in a graph, cascade changes in connected features). Concrete " +"GNMNetwork describes how it is done. -Defining network's business logic " +"or behavior. It can be expressed in network rules or " +"constraints/restrictions. Expected that each rule can be set from a " +"string and each concrete GNMNetwork will transform it to the internal " +"look." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:29 +msgid "Format" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:31 +msgid "" +"GNMNetwork inherits GDALDataset and looks like OGRDatasource with " +"additional functionality. There are a set of GDAL drivers for networks. " +"The generic network implementation in GDAL provides additional " +"functionality like rules, virtual edges and vertices. Also, while editing" +" the feature the network control the network rules and other specific, " +"and can deny saving edits. The other network drivers (pgRouting, OSRM, " +"GraphHopper, etc.) should provide the basic functionality via the " +"GNMNetwork class." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:34 +msgid "Network formats" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:36 +msgid "" +"To add a ``native`` support of the existed network format (like PostGIS " +"pgRouting, Oracle Spatial Networks, topology in GML, etc.) to GNM the " +"developer should implement the corresponding GNMDriver-GNMNetwork " +"interface. But there is also a capability to use the ``generic`` network " +"format, which is already implemented in GNM as a special class. It can be" +" extremely useful when there is a need to create and use a network in the" +" format that initially does not have its \"network part\" (like ESRI " +"Shapefile) directly." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:39 +msgid "GNMGenericNetwork" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:41 +msgid "" +":cpp:class:`GNMGenericNetwork` is a concrete implementation of the " +"GNMNetwork. GNMGenericNetwork intends to support the most GDALDataset " +"drivers (depends on the corresponding driver capabilities). Technically " +"the network format abstraction is achieved with the help of GDAL " +"abstraction: datasets and layers approach. GNMGdalNetwork aggregates a " +"GDALDataset instance where the \"network part\" is represented as a set " +"of \"system layers\" (wkbNone geometry, specific attribute fields) and " +"the spatial/attribute data is regarded as the set of \"class layers\" or " +"\"classes\" (layers with geometries and attributes, as usual). The " +"\"network part\" is created and maintained by GNMGenericNetwork " +"automatically and provides methods to work with it." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:43 +msgid "" +"The way of describing real-world networks by GNMGenericNetwork intends to" +" be a generic, because: -The most general type of graph is used, which " +"holds every useful information: directions of edges " +"(directed/undirected), edge costs (weighted/unweighted). This graph is " +"stored as an incidence list: source vertex feature id, target vertex " +"feature id, edge feature id, direct cost, inverse cost, direction of " +"edge; -Any feature with any geometry can be the vertex or the edge in a " +"graph. Also, it may be no feature “under” the connection's edge at all " +"(actually the virtual edge is created for this case). All this means that" +" user operates with the feature identifiers, while the GNMGenericNetwork " +"guaranties the connections integrity among features; -Any feature in the " +"network will gain the unique identifier – Global Feature Identifier " +"(GFID) which allows unify any amount of \"class layers\" under one " +"network; -GNMGenericNetwork uses its own way to determine the network's " +"business logic. See :cpp:func:`GNMGenericNetwork::CreateRule` for more " +"details." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:49 +msgid "" +"See the :cpp:class:`GNMGenericNetwork` class documentation for more " +"details." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:51 +msgid "" +"The network of common format has also the following important features: " +"-The single spatial reference system is used in the network, that means " +"that each feature which appears in the network will be transformed to " +"this SRS; -The network always created void and there is a need to import " +"or create features; -It is not possible to remove the \"network part\" " +"from the dataset – only delete the whole network with all data. The " +"deletion is made layer by layer and deletes only system and class layers " +"which registered in the network." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:57 +msgid "Network analysis" +msgstr "" + +#: ../../source/user/gnm_data_model.rst:59 +msgid "" +"The network analysis in GNM is implemented in :cpp:class:`GNMNetwork` " +"object." +msgstr "" + +#: ../../source/user/gnm_data_model.rst:61 +msgid "" +":cpp:class:`GNMGenericNetwork` holds the graph in memory in STL " +"containers and provides basic algorithms which return the results in the " +"array-form (e.g. std::vector full of path's edges and vertices GFIDs). " +"But the caller get a result as OGRLayer there features get from layers " +"consist the network. Also some additional fields created (VERTEX/EDGE " +"indicator field, GFID, layer name, etc.). The caller have to free the " +"result OGRLayer via :cpp:func:`GDALDataset::ReleaseResultSet`" +msgstr "" + +#: ../../source/user/index.rst:7 +msgid "GDAL Virtual File Systems" +msgstr "" + +#: ../../source/user/index.rst:5 +msgid "User oriented documentation" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:5 +msgid "Multidimensional Raster Data Model" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:7 +msgid "" +"This document attempts to describe the GDAL multidimensional data model, " +"that has been added in GDAL 3.1. That is the types of information that a " +"GDAL multidimensional dataset can contain, and their semantics." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:11 +msgid "" +"The multidimensional raster API is a generalization of the traditional " +":ref:`raster_data_model`, to address 3D, 4D or higher dimension datasets." +" Currently, it is limited to basic read/write API, and is not that much " +"plugged into other higher level utilities." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:17 +msgid "" +"It is strongly inspired from the netCDF and HDF5 API and data models. See" +" `HDF5 format and data model " +"<https://portal.opengeospatial.org/files/81716>`_." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:20 +msgid "" +"A :cpp:class:`GDALDataset` with multidimensional content contains a root " +":cpp:class:`GDALGroup`." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:24 +msgid "Group" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:26 +msgid "" +"A :cpp:class:`GDALGroup` (modelling a `HDF5 Group " +"<https://portal.opengeospatial.org/files/81716#_hdf5_group>`_) is a named" +" container of GDALAttribute, GDALMDArray or other GDALGroup. Hence " +"GDALGroup can describe a hierarchy of objects." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:31 +msgid "Attribute" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:33 +msgid "" +"A :cpp:class:`GDALAttribute` (modelling a `HDF5 Attribute " +"<https://portal.opengeospatial.org/files/81716#_hdf5_attribute>`_) has a " +"name and a value, and is typically used to describe a metadata item. The " +"value can be (for the HDF5 format) in the general case a multidimensional" +" array of \"any\" type (in most cases, this will be a single value of " +"string or numeric type)" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:39 +msgid "Multidimensional array" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:41 +msgid "" +"A :cpp:class:`GDALMDArray` (modelling a `HDF5 Dataset " +"<https://portal.opengeospatial.org/files/81716#_hdf5_dataset>`_) has a " +"name, a multidimensional array, references a number of GDALDimension, and" +" has a list of GDALAttribute." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:45 +msgid "" +"Most drivers use the row-major convention for dimensions: that is, when " +"considering that the array elements are stored consecutively in memory, " +"the first dimension is the slowest varying one (in a 2D image, the row), " +"and the last dimension the fastest varying one (in a 2D image, the " +"column). That convention is the default convention used for NumPy arrays," +" the MEM driver and the HDF5 and netCDF APIs. The GDAL API is mostly " +"agnostic about that convention, except when passing a NULL array as the " +"*stride* parameter for the :cpp:func:`GDALAbstractMDArray::Read` and " +":cpp:func:`GDALAbstractMDArray::Write` methods. You can refer to `NumPy " +"documentation about multidimensional array indexing order issues " +"<https://docs.scipy.org/doc/numpy/reference/internals.html" +"#multidimensional-array-indexing-order-issues>`_" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:55 +msgid "a GDALMDArray has also optional properties:" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:57 +msgid "Coordinate reference system: :cpp:class:`OGRSpatialReference`" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:58 +msgid "No data value:" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:59 +msgid "Unit" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:60 +msgid "Offset, such that unscaled_value = offset + scale * raw_value" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:61 +msgid "Scale, such that unscaled_value = offset + scale * raw_value" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:63 +msgid "" +"Number of operations can be applied on an array to get modified views of " +"it: :cpp:func:`GDALMDArray::Transpose()`, " +":cpp:func:`GDALMDArray::GetView()`, etc." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:66 +msgid "" +"The :cpp:func:`GDALMDArray::Cache()` method can be used to cache the " +"value of a view array into a sidecar file." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:70 +msgid "Dimension" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:72 +msgid "" +"A :cpp:class:`GDALDimension` describes a dimension / axis used to index " +"multidimensional arrays. It has the following properties:" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:75 +msgid "a name" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:76 +msgid "" +"a size, that is the number of values that can be indexed along the " +"dimension" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:78 +msgid "" +"a type, which is a string giving the nature of the dimension. Predefined " +"values are: HORIZONTAL_X, HORIZONTAL_Y, VERTICAL, TEMPORAL, PARAMETRIC " +"Other values might be used. Empty value means unknown." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:81 +msgid "" +"a direction. Predefined values are: EAST, WEST, SOUTH, NORTH, UP, DOWN, " +"FUTURE, PAST Other values might be used. Empty value means unknown." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:84 +msgid "" +"a reference to a GDALMDArray variable, typically one-dimensional, " +"describing the values taken by the dimension. For a georeferenced " +"GDALMDArray and its X dimension, this will be typically the values of the" +" easting/longitude for each grid point." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:90 +msgid "Data Type" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:92 +msgid "" +"A :cpp:class:`GDALExtendedDataType` (modelling a `HDF5 datatype " +"<https://portal.opengeospatial.org/files/81716#_hdf5_datatype>`_) " +"describes the type taken by an individual value of a GDALAttribute or " +"GDALMDArray. Its class can be NUMERIC, STRING or COMPOUND. For NUMERIC, " +"the existing :cpp:enum:`GDALDataType` enumerated values are supported. " +"For COMPOUND, the data type is a list of members, each member being " +"described by a name, a offset in byte in the compound structure and a " +"GDALExtendedDataType." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:103 +msgid "The HDF5 modelisation allows for more complex datatypes." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:107 +msgid "" +"HDF5 does not have native data types for complex values whereas " +"GDALDataType does. So a driver may decide to expose a GDT\\_Cxxxx " +"datatype from a HDF5 Compound data type representing a complex value." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:112 +msgid "Differences with the GDAL 2D raster data model" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:114 +msgid "" +"The concept of GDALRasterBand is no longer used for multidimensional. " +"This can be modelled as either different GDALMDArray, or using a compound" +" data type." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:119 +msgid "" +"Bridges between GDAL 2D classic raster data model and multidimensional " +"data model" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:121 +msgid "" +"The :cpp:func:`GDALRasterBand::AsMDArray` and " +":cpp:func:`GDALMDArray::AsClassicDataset` can be used to respectively " +"convert a raster band to a MD array or a 2D dataset to a MD array." +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:126 +msgid "Applications" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:128 +msgid "" +"The following applications can be used to inspect and manipulate " +"multidimensional datasets:" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:131 +msgid ":ref:`gdalmdiminfo`" +msgstr "" + +#: ../../source/user/multidim_raster_data_model.rst:132 +msgid ":ref:`gdalmdimtranslate`" +msgstr "" + +#: ../../source/user/multithreading.rst:5 +msgid "Multi-threading" +msgstr "" + +#: ../../source/user/multithreading.rst:8 +msgid "GDAL API: re-entrant, but not thread-safe" +msgstr "" + +#: ../../source/user/multithreading.rst:10 +msgid "" +"The exact meaning of the terms ``thread-safe`` or ``re-entrant`` is not " +"fully standardized. We will use here the `QT definitions " +"<https://doc.qt.io/qt-5/threads-reentrancy.html>`__. In particular, a C " +"function or C++ method is said to be re-entrant if it can be called " +"simultaneously from multiple threads, *but* only if each invocation uses " +"its own data." +msgstr "" + +#: ../../source/user/multithreading.rst:16 +msgid "All GDAL public C functions and C++ methods are re-entrant, except:" +msgstr "" + +#: ../../source/user/multithreading.rst:18 +msgid "the general initialization functions, like :cpp:func:`GDALAllRegister`." +msgstr "" + +#: ../../source/user/multithreading.rst:19 +msgid "" +"the general cleanup functions like :cpp:func:`GDALDestroy` or " +":cpp:func:`OSRCleanup`." +msgstr "" + +#: ../../source/user/multithreading.rst:21 +msgid "" +"Those functions should not be called concurrently from several threads, " +"and it is general best practice to call them from the main thread of the " +"program at program initialization and termination." +msgstr "" + +#: ../../source/user/multithreading.rst:25 +msgid "" +"Unless otherwise stated, no GDAL public C functions and C++ methods " +"should be assumed to be thread-safe. That is you should not call " +"simultaneously GDAL functions from multiple threads on the same data " +"instance, or even instances that are closely related through ownership " +"relationships. For example, for a multi-band raster dataset, it is not " +"safe to call concurrently GDAL functions on different " +":cpp:class:`GDALRasterBand` instances owned by the same " +":cpp:class:`GDALDataset` instance (each thread should instead manipulate " +"a distinct GDALDataset). Similarly for a GDALDataset owning several " +":cpp:class:`OGRLayer`." +msgstr "" + +#: ../../source/user/multithreading.rst:34 +msgid "" +"The reason is that most implementations of GDALDataset or GDALRasterBand " +"are stateful. A GDALDataset typically owns a file handle, and performs " +"seek/read operations on it, thus not allowing concurrent access. Block " +"cache related structures for a given GDALDataset are not thread-safe. " +"Drivers also often implement lazy initialization strategies to access " +"various metadata which are resolved only the first time the method to " +"access them is invoked. Drivers may also rely on third-party libraries " +"that expose objects that are not thread-safe." +msgstr "" + +#: ../../source/user/multithreading.rst:43 +msgid "" +"Those restrictions apply to the C and C++ ABI, and all languages bindings" +" (unless they would take special precautions to serialize calls)" +msgstr "" + +#: ../../source/user/multithreading.rst:47 +msgid "GDAL block cache and multi-threading" +msgstr "" + +#: ../../source/user/multithreading.rst:49 +msgid "" +"The current design of the GDAL raster block cache allows concurrent reads" +" of several datasets. However performance issues may arise when writing " +"several datasets from several threads, due to lock contention in the " +"global structures of the block cache mechanism." +msgstr "" + +#: ../../source/user/multithreading.rst:54 +msgid "RAM fragmentation and multi-threading" +msgstr "" + +#: ../../source/user/multithreading.rst:56 +msgid "" +"It has been observed that scenarios that involve multi-threading reading " +"or writing of raster datasets are prone to cause a high RAM usage, in " +"particular when using the default dynamic memory allocator of Linux. " +"Using the alternate `tcmalloc <https://github.com/google/tcmalloc>`__ " +"memory allocator helps reducing the amount of virtual and resident memory" +" used." +msgstr "" + +#: ../../source/user/multithreading.rst:62 +msgid "" +"For example, with Debian/Ubuntu distributions, this can be done by " +"installing the ``libtcmalloc-minimal4`` package and running the binary " +"that executes GDAL with:" +msgstr "" + +#: ../../source/user/multithreading.rst:71 +msgid "GDAL and multi-processing" +msgstr "" + +#: ../../source/user/multithreading.rst:73 +msgid "" +"POSIX fork() API should not be called during the middle of a GDAL " +"operation, otherwise some structures like mutexes might appear to be " +"locked forever in the forked process. If multi-processing is done, we " +"recommend that processes are forked before any GDAL operation is done. " +"Operating on the same GDALDataset instance in several sub-processes will " +"generally lead to wrong results due to the underlying file descriptors " +"being shared." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:5 +msgid "Feature Style Specification" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:7 +msgid "Version 0.016 - 2018-12-03" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:10 +msgid "1. Overview" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:12 +msgid "" +"This document defines the way feature style information (i.e. colors, " +"line width, symbols, etc.) should be handled at the various levels in " +"GDAL's vector drivers (OGR)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:16 +msgid "" +"The following GDAL vector drivers have varying levels of support for " +"feature styles: :ref:`DWG (libopencad) <vector.cad>`, :ref:`DWG (Teigha) " +"<vector.dwg>`, :ref:`DXF <vector.dxf>`, :ref:`KML (libkml) " +"<vector.libkml>`, :ref:`MapInfo <vector.mitab>`, :ref:`MicroStation DGN " +"v7 <vector.dgn>` and :ref:`DGN v8 <vector.dgnv8>`, :ref:`OpenJUMP JML " +"<vector.jml>` and :ref:`PDF <raster.pdf>`." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:24 +msgid "1.1 Style is a property of Feature object" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:26 +msgid "" +"Conceptually, the feature style should be seen as a property of a " +"feature. Even though some systems store style information in a special " +"attribute, in GDAL it is more consistent to see the style as a property, " +"just the same way the geometry of a feature is also a property." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:31 +msgid "" +"This does not prevent us from storing the style information in an " +"attribute when writing to some formats that have no provision for styles " +"(e.g. E00). But then at the time such a dataset is opened through GDAL, " +"the name of the attribute that contains style information should either " +"be specified in some metadata, or be specified by the user." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:37 +msgid "" +"Also, in the SFCOM interface, the style information will be stored in an " +"attribute just like the geometry is." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:41 +msgid "1.2 Feature Styles can be stored at 2 levels" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:43 +msgid "" +"The style defines the way a feature should be drawn, but it is very " +"common to have several features that share the same style. In those " +"cases, instead of duplicating the style information on each feature, we " +"will provide a more efficient way to share style information." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:48 +msgid "There are two levels at which style information can be found:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:50 +msgid "" +"A **dataset** can have a table of pre-defined styles that can then be " +"referred to by the layers or by the individual features. The mechanism " +"for that is defined further down in this document." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:53 +msgid "" +"A **feature (OGRFeature object)** can have its own complete style " +"definition. Alternatively, a feature can be linked to a style in the " +"dataset's table of styles. This can save storage space when the same " +"styles are reused often." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:58 +msgid "" +"It should be possible to have style information stored at one or more of " +"the various levels while working on a given dataset. The level(s) where " +"the style is actually stored will depend on the most efficient approach " +"for the format we are dealing with." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:64 +msgid "1.3 Drawing Tools" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:66 +msgid "" +"We define a small set of drawing tools that are used to build style " +"definitions:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:69 +msgid "**PEN**: For linear styles" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:70 +msgid "**BRUSH**: For filling areas" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:71 +msgid "**SYMBOL**: Point symbols" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:72 +msgid "**LABEL**: For annotations" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:74 +msgid "" +"Each drawing tool can take a number of parameters, all optional. The " +"style syntax is built in a way that a system that cannot support all " +"possible parameters can safely skip and ignore the parameters it does not" +" support. This will also make it easy to extend the specification in the " +"future without breaking existing code or applications." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:80 +msgid "" +"A style can use a single tool, or use a combination of one or more tools." +" By combining the use of several tools in a style, one can build " +"virtually any type of graphical representation. For instance, the SYMBOL " +"tool can be used to place spaced symbols along a line. Also, the LABEL " +"tool can be used to place text on a point, stretch it along a line, or " +"even, by combining the PEN tool with the LABEL tool, use the line as a " +"leader to the text label, and draw the text string on the last vertex of " +"the line." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:89 +msgid "" +"Of course, few systems can support all that. But the intention here is to" +" have a style specification that is powerful and flexible enough to allow" +" all types of formats to exchange style information with the least " +"possible loss." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:95 +msgid "1.4 Feature attributes can be used by style definitions" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:97 +msgid "" +"In some cases, it might be useful for a style definition to refer to an " +"attribute field on the feature for a given tool parameter's value instead" +" of having a hardcoded value inside the style itself." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:101 +msgid "" +"Example of this are text angle, text string, etc... these values change " +"for every single text label, but we can share the rest of the label style" +" at the layer level if we lookup the angle and text string in an " +"attribute on each feature." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:106 +msgid "" +"The syntax of the style string provides a way that any parameter value " +"can be either a constant value, or a lookup to an attribute field." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:110 +msgid "1.5 Tool parameter units" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:112 +msgid "" +"Several parameter values can be expressed in different measurement units " +"depending on the file format you are dealing with. For instance, some " +"systems express line width, or text height in points, other in pixels, " +"and others use ground units. In order to accommodate all that, all " +"parameters can be specified in one of the following units systems:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:118 +msgid "**g**: Map Ground Units (whatever the map coordinate units are)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:119 +msgid "**px**: Pixels" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:120 +msgid "**pt**: Points (1/72 inch)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:121 +msgid "**mm**: Millimeters" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:122 +msgid "**cm**: Centimeters" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:123 +msgid "**in**: Inches" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:125 +msgid "" +"Some tools will have to be provided at the GDAL client level to simplify " +"the conversion of any value from one units system to another. This would " +"imply that the GDAL client has to specify a map scale so that conversions" +" from ground units to paper/pixel units can be performed." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:133 +msgid "2. Feature Style String" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:135 +msgid "" +"As was mentioned earlier, styles definitions will usually be stored as " +"strings, either in a per-layer (or per-dataset) table, or directly in the" +" features." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:140 +msgid "2.1 Examples" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:142 +msgid "Here are some example style definition strings:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:144 +msgid "A 5 pixels wide red line: ``PEN(c:#FF0000,w:5px)``" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:146 +msgid "" +"A polygon filled in blue, with a black outline: " +"``BRUSH(fc:#0000FF);PEN(c:#000000)``" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:148 +msgid "A point symbol: ``SYMBOL(c:#00FF00,id:\"points.sym-45,ogr-sym-7\")``" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:150 +msgid "" +"A text label, taking the text string from the \"text_attribute\" " +"attribute field: ``LABEL(f:\"Times New " +"Roman\",s:12pt,t:{text_attribute})\"``" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:154 +msgid "" +"Here is what a style table that contains all the above styles could look " +"like:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:164 +msgid "" +"Then individual features can refer to styles from the table above using " +"the \"@\" character followed by the style name in their style property." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:167 +msgid "" +"For instance, a feature with its style set to \"@road\" would be drawn as" +" a red line." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:171 +msgid "2.2 Style String Syntax" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:173 +msgid "Each feature object has a style property (a string):" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:179 +msgid "``<style_def>`` is defined later in this section." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:180 +msgid "" +"An empty style string means that the feature's style is unspecified. It " +"does not indicate that the feature is invisible – an invisible feature " +"may be indicated using a fully transparent color, like PEN(c:#00000000)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:184 +msgid "" +"``@<style_name>`` is a reference to a predefined style in the layer or " +"the dataset's style table. The layer's table is looked up first, and if " +"style_name is not found there then the dataset's table will be looked up." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:188 +msgid "" +"Finally, ``{<field_name>}`` means that the style property should be read " +"from the specified attribute field." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:191 +msgid "" +"The <style_def> is the real style definition. It is a combination of 1 or" +" more style parts separated by semicolons. Each style_part uses a drawing" +" tool to define a portion of the complete graphical representation:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:214 +msgid "" +"By default, style parts are drawn in the order that they appear in the " +"style_def string unless each part is assigned a different level parameter" +" value (see the level parameter definition)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:218 +msgid "" +"All drawing tool parameters are optional. So it is legal to have a " +"style_part with an empty drawing tool parameter list (e.g. \"PEN()\"). " +"For each parameter that does not have any specified value, it is up to " +"the client application to use its own default value. This document " +"provides advisory default values for most parameters, but it is not " +"mandatory for an application to use those default values." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:225 +msgid "" +"When {<field_name>} is used for a tool_param value, several options are " +"available with respect to the units. The units can be specified after the" +" field name as in PEN(c:#FF0000,w:{line_width}pt) or can be left " +"unspecified as in PEN(c:#FF0000,w:{line_width}). In the first case, the " +"default units will be points (pt), but if the attribute field line_width " +"contains a value followed by a units abbreviation (e.g. \"5px\") then the" +" units specified in the attribute fields have precedence (in this case " +"pixels). Note that the attribute field does not have to contain a units " +"value and probably won't in most cases; it is just an optional feature to" +" be able to override the default units from inside an attribute field's " +"value." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:238 +msgid "2.3 Pen Tool Parameters" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:240 +#: ../../source/user/ogr_feature_style.rst:364 +#: ../../source/user/ogr_feature_style.rst:459 +#: ../../source/user/ogr_feature_style.rst:586 +msgid "**Applicable geometry types:**" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:242 +msgid "" +"Point: When applied to a point, a PEN tool can only define the color and " +"the size of the point to draw." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:244 +msgid "Polyline: This is the most obvious case." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:245 +msgid "Polygon: Defines the way the outline of a polygon should be drawn." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:247 +msgid "" +"Here is the current list of PEN tool parameters. While this is sufficient" +" to cover all the cases that we have encountered so far, new parameters " +"might be added in the future to handle new types of graphical " +"representation. Note again that all parameters are optional:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:252 +msgid "``c``: **Pen Color**, expressed hexadecimal (#RRGGBB[AA])" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:254 +#: ../../source/user/ogr_feature_style.rst:377 +#: ../../source/user/ogr_feature_style.rst:386 +#: ../../source/user/ogr_feature_style.rst:519 +msgid "" +"[AA]: the last 2 digits define the alpha channel value, with 0 being " +"transparent and FF being opaque. The default is FF (opaque)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:256 +msgid "Suggested default: black (c:#000000)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:257 +msgid "Example: PEN(c:#FF0000), or PEN(C:#FF0000FF)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:260 +msgid "" +"``w``: **Pen Width**, expressed as a numeric value with units (g, px, pt," +" mm, cm, in)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:263 +msgid "Suggested default: 1 pixel" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:264 +msgid "Examples: PEN(c:#FF0000,w:5px), PEN(w:3pt), PEN(w:50g)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:266 +msgid "" +"``p``: **Pattern**. To create dash lines. A list of pen-down/pen-up " +"distances" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:268 +#: ../../source/user/ogr_feature_style.rst:319 +#: ../../source/user/virtual_file_systems.rst:79 +#: ../../source/user/virtual_file_systems.rst:168 +#: ../../source/user/virtual_file_systems.rst:195 +#: ../../source/user/virtual_file_systems.rst:1092 +#: ../../source/user/virtual_file_systems.rst:1110 +#: ../../source/user/virtual_file_systems.rst:1221 +#: ../../source/user/virtual_file_systems.rst:1303 +msgid "Examples:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:270 +msgid "|style_pen1| = PEN(c:#FF0000,w:2px,p:\"4px 5px\"). short-dash line" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:276 +msgid "style_pen1" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:272 +msgid "|style_pen2| = PEN(c:#FF0000,w:2px,p:\"10px 5px\"). long-dash line" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:279 +msgid "style_pen2" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:274 +msgid "" +"|style_pen3| = PEN(c:#FF0000,w:2px,p:\"10px 5px 4px 5px\"). long/short " +"dash" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:282 +msgid "style_pen3" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:287 +msgid "" +"``id``: **Comma-delimited list of Pen Names or Ids** For systems that " +"identify pens with a name or an id. The names in the comma-delimited list" +" of ids are scanned until one is recognized by the target system. Pen Ids" +" can be either system-specific ids (see further below) or be one of the " +"pre-defined OGR pen ids for known line patterns. The id parameter should " +"always include one of the OGR ids at the end of the comma-delimited list " +"of ids so that an application never has to rely on understanding system-" +"specific ids." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:296 +msgid "Here is the current list of OGR pen ids (this could grow time):" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:298 +msgid "ogr-pen-0: solid (the default when no id is provided)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:299 +msgid "ogr-pen-1: null pen (invisible)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:300 +msgid "ogr-pen-2: dash" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:301 +msgid "ogr-pen-3: short-dash" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:302 +msgid "ogr-pen-4: long-dash" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:303 +msgid "ogr-pen-5: dot line" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:304 +msgid "ogr-pen-6: dash-dot line" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:305 +msgid "ogr-pen-7: dash-dot-dot line" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:306 +msgid "ogr-pen-8: alternate-line (sets every other pixel)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:308 +msgid "" +"System-specific ids are very likely to be meaningful only to that " +"specific system that created them. The ids should start with the system's" +" name, followed by a dash (-), followed by whatever information is " +"meaningful to that system (a number, a name, a filename, etc.). e.g. " +"\"mapinfo-5\", or \"mysoft-lines.sym-123\", or \"othersystems-funnyline\"" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:314 +msgid "" +"System-specific ids are allowed in order to prevent loss of information " +"when dealing with data from systems that store line patterns in external " +"files or that have their own pre-defined set of line styles (for " +"instance, to do a MapInfo MIF to TAB translation without any loss." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:321 +msgid "PEN(c:#00FF00,id:\"ogr-pen-0\") - simple solid line" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:322 +msgid "" +"PEN(c:#00FF00,id:\"mapinfo-5,ogr-pen-7\") - corresponds to MapInfo's Pen " +"#5, and a system that can't understand MapInfo pens falls back on the " +"default \"ogr-pen-7\" pen (dot-dot line)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:327 +msgid "``cap``: **Pen Cap** - Set the shape of end points of lines." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:329 +msgid "" +"\"cap:b\" - Butt: The ends of the line don't extend beyond the end " +"points. This is the default." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:331 +msgid "" +"\"cap:r\" - Round: Terminate lines with a circle whose diameter is equal " +"to the line width." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:333 +msgid "" +"\"cap:p\" - Projecting: Similar to Butt, but the ends of the line extend " +"by half of line width beyond the end points." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:337 +msgid "``j``: **Pen Join** - Set the shape of the join point (vertex) of lines." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:339 +msgid "" +"\"j:m\" - Miter: Extend the outer edge of the lines until they touch. " +"This is the default." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:341 +msgid "" +"\"j:r\" - Rounded: Join lines with an arc whose center is at the join " +"point and whose diameter is equal to the line width." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:343 +msgid "" +"\"j:b\" - Bevel: Join the lines with butt end caps and fill the resulting" +" triangular notch at the join position." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:347 +msgid "" +"``dp``: **Perpendicular Offset**, expressed as a numeric value units (g, " +"px, pt, mm, cm, in)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:350 +msgid "" +"Offset from the line center. If the offset is negative then the pen will " +"be drawn left of the main segment and right otherwise." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:354 +#: ../../source/user/ogr_feature_style.rst:449 +#: ../../source/user/ogr_feature_style.rst:566 +#: ../../source/user/ogr_feature_style.rst:713 +msgid "" +"``l``: **Priority Level** - Numeric value defining the order in which " +"style parts should be drawn." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:357 +#: ../../source/user/ogr_feature_style.rst:452 +#: ../../source/user/ogr_feature_style.rst:569 +#: ../../source/user/ogr_feature_style.rst:716 +msgid "" +"Lower priority style parts are drawn first, and higher priority ones are " +"drawn on top. If priority level is unspecified, the default is 1." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:362 +msgid "2.4 Brush Tool Parameters" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:366 +msgid "Point: Not applicable." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:367 +msgid "Polyline: Not applicable." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:368 +msgid "Polygon: Defines the way the surface of a polygon is filled." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:370 +msgid "" +"Here is the current list of BRUSH tool parameters. Note again that that " +"this list may be extended in the future, and all parameters are optional:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:374 +msgid "" +"``fc``: **Brush ForeColor**, expressed in hexadecimal (#RRGGBB[AA]). Used" +" for painting the brush pattern itself." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:379 +#, python-format +msgid "Suggested default: 50% grey (c:#808080)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:380 +msgid "Example: BRUSH(fc:#FF0000)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:383 +msgid "" +"``bc``: **Brush BackColor**, expressed in hexadecimal (#RRGGBB[AA]). Used" +" for painting the area behind the brush pattern." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:388 +msgid "Suggested default: transparent (c:#FFFFFF00)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:389 +msgid "Example: BRUSH(fc:#FF0000,bc:#FFEEDD)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:392 +msgid "" +"``id``: **Brush Name or Brush Id** - Comma-delimited list of brush names " +"or ids. The names in the comma-delimited list of ids are scanned until " +"one is recognized by the target system." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:396 +msgid "" +"Brush Ids can be either system-specific ids (see furtherbelow) or be one " +"of the pre-defined OGR brush ids for well known brush patterns. The id " +"parameter should always include one of the OGR ids at the end of the " +"comma-delimited list of ids so that an application never has to rely on " +"understanding system-specific ids." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:402 +msgid "Here is the current list of OGR brush ids (this could grow over time):" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:406 +msgid "ogr-brush-0: solid foreground color (the default when no id is provided)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:407 +msgid "" +"ogr-brush-1: null brush (transparent - no fill, irrespective of fc or bc " +"values" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:409 +msgid "ogr-brush-2: horizontal hatch" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:410 +msgid "ogr-brush-3: vertical hatch" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:411 +msgid "ogr-brush-4: top-left to bottom-right diagonal hatch" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:412 +msgid "ogr-brush-5: bottom-left to top-right diagonal hatch" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:413 +msgid "ogr-brush-6: cross hatch" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:414 +msgid "ogr-brush-7: diagonal cross hatch" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:416 +msgid "" +"Like with Pen Ids, system-specific brush ids are very likely to be " +"meaningful only to that specific system that created them. The ids should" +" start with the system's name, followed by a dash (-), followed by " +"whatever information is meaningful to that system (a number, a name, a " +"filename, etc.)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:421 +msgid "" +"The following conventions will be used for common system-specific brush " +"ids:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:423 +msgid "\"bmp-filename.bmp\" for Windows BMP patterns" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:425 +msgid "" +"Other conventions may be added in the future (such as vector symbols, " +"WMF, etc)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:429 +msgid "" +"``a``: **Angle** - Rotation angle (in degrees, counterclockwise) to apply" +" to the brush pattern." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:433 +msgid "``s``: **Size or Scaling Factor** - Numeric value with or without units." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:435 +msgid "" +"If units are specified, then this value is the absolute size to draw the " +"brush or symbol. If no units are specified then it is taken as a scaling " +"factor relative to the symbol's default size." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:440 +msgid "" +"``dx``, ``dy``: **Spacing**, expressed as a numeric value with units (g, " +"px, pt, mm, cm, in)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:443 +msgid "" +"If filling an area using point symbols, these values will define the " +"spacing to use between them. \"dx\" is the horizontal distance between " +"the center of two adjacent symbols and \"dy\" is the vertical distance. " +"The default is to use the symbol's bounding box width and height for dx " +"and dy respectively." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:457 +msgid "2.5 Symbol Tool Parameters" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:461 +msgid "Point: Place a symbol at the point's location" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:462 +msgid "" +"Polyline: Place symbols along the polyline, either at each vertex, or " +"equally spaced." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:464 +msgid "Polygon: Place the symbols on the outline of the polygon." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:466 +msgid "" +"Here is the current list of SYMBOL tool parameters. Note again that that " +"this list may be extended in the future, and all parameters are optional:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:470 +msgid "" +"``id``: **Symbol Name or Id** - Comma-delimited list of symbol names or " +"ids." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:472 +msgid "" +"The names in the comma-delimited list of ids are scanned until one is " +"recognized by the target system." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:475 +msgid "" +"Symbol Ids can be either system-specific ids (see further below) or be " +"one of the pre-defined OGR symbol ids for well known symbols. The id " +"parameter should always include one of the OGR ids at the end of the " +"comma-delimited list of ids so that an application never has to rely on " +"understanding system-specific ids." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:481 +msgid "Here is the current list of OGR symbol ids (this could grow over time):" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:485 +msgid "ogr-sym-0: cross (+)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:486 +msgid "ogr-sym-1: diagcross (X)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:487 +msgid "ogr-sym-2: circle (not filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:488 +msgid "ogr-sym-3: circle (filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:489 +msgid "ogr-sym-4: square (not filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:490 +msgid "ogr-sym-5: square (filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:491 +msgid "ogr-sym-6: triangle (not filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:492 +msgid "ogr-sym-7: triangle (filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:493 +msgid "ogr-sym-8: star (not filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:494 +msgid "ogr-sym-9: star (filled)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:495 +msgid "" +"ogr-sym-10: vertical bar (can be rotated using angle attribute to produce" +" diagonal bar)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:498 +msgid "" +"Like with Pen Ids, system-specific symbol ids are very likely to be " +"meaningful only to that specific system that created them. The ids should" +" start with the system's name, followed by a dash (-), followed by " +"whatever information is meaningful to that system (a number, a name, a " +"filename, etc.)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:503 +msgid "" +"The following conventions will be used for common system-specific symbol " +"ids:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:505 +msgid "\"bmp-filename.bmp\" for Windows BMP symbols" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:506 +#, python-format +msgid "" +"\"font-sym-%d\" for a font symbols, where %d is a glyph number inside a " +"font, font family is defined by **f** style field." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:509 +msgid "" +"Other conventions may be added in the future (such as vector symbols, " +"WMF, etc.)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:513 +msgid "" +"``a``: **Angle** - Rotation angle (in degrees, counterclockwise) to apply" +" to the symbol." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:517 +msgid "``c``: **Symbol Color**, expressed in hexadecimal (#RRGGBB[AA])" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:521 +msgid "Suggested default symbol color: black (c:#000000)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:522 +#: ../../source/user/ogr_feature_style.rst:561 +#: ../../source/user/ogr_feature_style.rst:578 +#: ../../source/user/ogr_feature_style.rst:603 +msgid "Example ::" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:526 +msgid "``o``: **Symbol Outline Color**, expressed in hexadecimal (#RRGGBB[AA])." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:528 +msgid "" +"If this parameter is set, an additional halo or border of this color is " +"drawn around the symbol." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:532 +msgid "``s``: **Size or Scaling Factor** - Numeric value with or without units." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:534 +msgid "" +"If units are specified, then this value is the absolute size to draw the " +"symbol. If no units are specified then it is taken as a scaling factor " +"relative to the symbol's default size." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:539 +msgid "" +"``dx``, ``dy``: **X and Y offset**, of the symbol's insertion point, " +"expressed as a numeric value with units (g, px, pt, mm, cm, in)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:542 +msgid "" +"Applies to point geometries, and to symbols placed at each vertex of a " +"polyline." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:546 +msgid "" +"``ds``, ``dp``, ``di``: **Spacing parameters** for symbols spaced along a" +" line, expressed as a numeric value with units (g, px, pt, mm, cm, in)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:549 +msgid "" +"``ds`` is the step to use when placing symbols along the line. By " +"default, symbols applied to a feature with a line geometry are placed at " +"each vertex, butsetting \"ds\" triggers the placement of symbols at an " +"equal distance along the line. \"ds\" has no effect for a feature with a " +"point geometry." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:555 +msgid "" +"``dp`` can be used together with \"ds\" to specify the perpendicular " +"distance between the symbols' center and the line along which they're " +"placed." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:558 +msgid "" +"``di`` can be used to specify an initial offset from the beginning of the" +" line." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:573 +#: ../../source/user/ogr_feature_style.rst:598 +msgid "``f``: **Font Name** - Comma-delimited list of fonts names." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:575 +#: ../../source/user/ogr_feature_style.rst:600 +msgid "" +"Works like the CSS font-family property: the list of font names is " +"scanned until a known font name is encountered." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:584 +msgid "2.6 Label Tool Parameters" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:588 +msgid "Point: Place a text label at the point's location" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:589 +msgid "Polyline: Place text along the polyline." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:590 +msgid "" +"Polygon: Place a label at the centroid of the polygon. All parameters " +"behave exactly as if the geometry was a point located at the polygon's " +"centroid." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:594 +msgid "" +"Here is the current list of LABEL tool parameters. Note again that that " +"this list may be extended in the future, and all parameters are optional:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:608 +msgid "" +"``s``: **Font Size**, expressed as a numeric value with units (g, px, pt," +" mm, cm, in)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:611 +msgid "" +"In the CAD world, font size, or \"text height\", determines the height of" +" a capital letter - what typographers call \"cap height\". But in the " +"worlds of typesetting, graphics and cartography, font size refers to the " +"\"em height\" of the font, which is taller than the cap height. This " +"means that text assigned a height of 1 inch in a DXF file will look " +"larger (often about 45% larger) than 72-point text in a PDF file or " +"MapInfo map. At present, GDAL vector drivers treat the \"s:\" style " +"string value as whichever font size measurement (cap height or em height)" +" is used natively by that format, which may result in incorrect text " +"sizing when using the ogr2ogr tool. This parameter could be subject to " +"clearer specification in the future." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:623 +msgid "" +"``t``: **Text String** - Can be a constant string, or a reference to an " +"attribute field's value." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:626 +msgid "" +"If a double-quote character or backslash (\\) character is present in the" +" string, it is escaped with a backslash character before it." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:629 +msgid "Examples ::" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:636 +msgid "``a``: **Angle** - Rotation angle (in degrees, counterclockwise)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:638 +msgid "" +"``c``: **Text Foreground Color**, expressed in hexadecimal (#RRGGBB[AA]) " +"Suggested default: black (c:#000000)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:641 +msgid "" +"``b``: **Text Background Color** - Color of the filled box to draw behind" +" the label, expressed in hexadecimal (#RRGGBB[AA]). No box drawn if not " +"set." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:644 +msgid "" +"``o``: **Text Outline Color** - Color of the text outline (halo in " +"MapInfo terminology), expressed in hexadecimal (#RRGGBB[AA]). No outline " +"if not set." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:647 +msgid "" +"``h``: **Shadow Color** - Color of the text shadow, expressed in " +"hexadecimal (#RRGGBB[AA]). No shadow if not set." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:650 +#, python-format +msgid "" +"``w``: **Stretch** - The stretch factor changes the width of all " +"characters in the font by the given percentage. For example, a setting of" +" 150 results in all characters in the font being stretched to 150% of " +"their usual width. The default stretch factor is 100." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:655 +msgid "" +"``m``: **Label Placement Mode** - How the text is drawn relative to the " +"feature's geometry." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:658 +msgid "" +"\"m:p\" - The default. A simple label is attached to a point or to the " +"first vertex of a polyline." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:660 +msgid "" +"\"m:l\" - Text is attached to the last vertex of a polyline. A PEN tool " +"can be combined with this LABEL tool to draw the polyline as a leader to " +"the label." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:663 +msgid "" +"\"m:s\" - Stretch the text string along a polyline, with an equal spacing" +" between each character." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:665 +msgid "" +"\"m:m\" - Place text as a single label at the middle of a polyline (based" +" on total line length)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:667 +msgid "\"m:w\" - One word per line segment in a polyline." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:668 +msgid "" +"\"m:h\" - Every word of text attached to polyline is placed horizontally " +"in its segment, anchor point is a center of segment." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:670 +msgid "" +"\"m:a\" - Every word of text attached to polyline is stretched to fit the" +" segment of polyline and placed along that segment. The anchor point is a" +" start of a segment." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:675 +msgid "" +"``p``: **Anchor Position** - A value from 1 to 12 defining the label's " +"position relative to the point to which it is attached" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:678 +msgid "" +"There are four vertical alignment modes: *baseline*, *center*, *top* and " +"*bottom*; and three horizontal modes: *left*, *center* and *right*." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:683 +msgid "" +"Currently, the precise interpretation of these values (for example, " +"whether accents on uppercase letters sit above or below the alignment " +"point with p:7) differs from file format to file format. This parameter " +"could be subject to clearer specification in the future." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:689 +msgid "" +"``dx``, ``dy``: **X and Y offset** of the label's insertion point, " +"expressed as a numeric value with units (g, px, pt, mm, cm, in)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:692 +msgid "Applies to text placed on a point, or at each vertex of a polyline." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:695 +msgid "" +"``dp``: **Perpendicular Offset** for labels placed along a line, " +"expressed as a numeric value with units (g, px, pt, mm, cm, in)." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:698 +msgid "" +"\"dp\" specifies the perpendicular distance between the label and the " +"line along which it is placed. If the offset is negative then the label " +"will be shifted left of the main segment, and right otherwise." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:703 +msgid "``bo``: **Bold** - Set to 1 for bold text. Set to 0 or omitted otherwise." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:705 +msgid "" +"``it``: **Italic** - Set to 1 for italic text. Set to 0 or omitted " +"otherwise." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:707 +msgid "" +"``un``: **Underline** - Set to 1 for underlined text. Set to 0 or omitted" +" otherwise." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:710 +msgid "" +"``st``: **Strikethrough** - Set to 1 for struck-through text. Set to 0 " +"or omitted otherwise." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:721 +msgid "2.7 Styles Table Format" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:723 +msgid "" +"For file formats that support tables of styles, then the predefined " +"styles would be stored in that format." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:726 +msgid "" +"For file formats that do not support tables of styles, then the style " +"table could be stored in a text file with a .ofs (OGR Feature Styles) " +"extension and the same basename as the dataset. This would apply to " +"formats like Esri Shapefile." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:731 +msgid "Here is an example of a .ofs file:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:744 +msgid "" +"The first line is a signature with a version number, which must be " +"present." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:747 +msgid "" +"The second line (StyleField: \"style\") is the name of the attribute " +"field in which the Feature Style String is stored for each object in the " +"corresponding layer. This is optional, if not set, then the objects in " +"the layer will all share the same style defined in DefaultStyle." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:752 +msgid "" +"The third line (DefaultStyle:...) defines the style that applies by " +"default to all objects that have no explicit style." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:755 +msgid "Then the list of style definitions follow." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:758 +msgid "2.8 Using OGR SQL to transfer the style between the data sources" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:760 +msgid "" +"You can use the **OGR_STYLE** special field to extract the feature level " +"style, and ogr2ogr can be used to transfer the style string between data " +"sources according to the following example:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:768 +msgid "" +"Without specifying the length of the style field, the output driver may " +"truncate the length to a default value. Therefore it may be necessary to " +"specify the target length manually, like:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:776 +msgid "" +"OGR is aware of using the OGR_STYLE field if it exists, and " +"OGRFeature::GetStyleString will return the value of this field if no " +"style string has been specified programmatically." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:785 +msgid "3. OGR Support Classes" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:787 +msgid "" +"The :cpp:class:`OGRFeature` class has member functions " +":cpp:func:`OGRFeature::GetStyleString`, " +":cpp:func:`OGRFeature::SetStyleString` and " +":cpp:func:`OGRFeature::SetStyleStringDirectly` which may be used to " +"interact with a feature's style string as a C-style string. Additionally," +" there are :cpp:func:`OGRFeature::GetStyleTable`, " +":cpp:func:`OGRFeature::SetStyleTable` and " +":cpp:func:`OGRFeature::SetStyleTableDirectly` for managing style tables " +"as instances of the :cpp:class:`OGRStyleTable` class." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:794 +msgid "" +"The :cpp:class:`OGRLayer` and :cpp:class:`GDALDataset` classes also have " +":cpp:func:`OGRLayer::GetStyleTable`, :cpp:func:`OGRLayer::SetStyleTable` " +"and :cpp:func:`OGRLayer::SetStyleTableDirectly` member functions." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:797 +msgid "" +"To parse style strings, the :cpp:class:`OGRStyleMgr` class is used. Each " +"style tool in the string is accessed as an instance of the " +":cpp:class:`OGRStyleTool` class. Lastly, four helper classes exist, one " +"for each tool (:cpp:class:`OGRStylePen`, :cpp:class:`OGRStyleBrush`, " +":cpp:class:`OGRStyleSymbol`, :cpp:class:`OGRStyleLabel`), with each " +"available parameter represented by a getter and setter member function. " +"To understand these classes better, it may be useful to read the " +":source_file:`ogr/ogr_featurestyle.h` and " +":source_file:`ogr/ogrfeaturestyle.cpp` code files." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:810 +msgid "Here is some example C++ code:" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:888 +msgid "Revision history" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:890 +msgid "" +"**Version 0.016 - 2018-12-03 - Andrew Sudorgin** Restored and documented " +"font property for point symbols" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:892 +msgid "" +"**Version 0.015 - 2018-01-08 - Alan Thomas** Update outdated material; " +"minor changes to BRUSH 'id' and LABEL 't', 'bo', 'it', 'un', 'st'; " +"clarify BRUSH 'fc', 'bc', SYMBOL 'o' and LABEL 's', 'w', 'p'" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:896 +msgid "" +"**Version 0.014 - 2011-07-24 - Even Rouault** Mention the escaping of " +"double-quote characters in the text string of a LABEL (ticket #3675)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:899 +msgid "" +"**Version 0.013 - 2008-07-29 - Daniel Morissette** Added 'o:' for font " +"point symbol outline color (ticket #2509)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:901 +msgid "" +"**Version 0.012 - 2008-07-21 - Daniel Morissette** Added 'o:' for text " +"outline color and updated 'b:' to be specifically a filled label " +"background box (ticket #2480)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:904 +msgid "" +"**Version 0.011 - 2008-02-28 - Tamas Szekeres** Note about OGR SQL to " +"transfer the style between the data sources" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:906 +msgid "" +"**Version 0.010 - 2006-09-23- Andrey Kiselev** Added label styles 'w', " +"'st', 'h', 'm:h', 'm:a', 'p:{10,11,12}'" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:908 +msgid "" +"**Version 0.009 - 2005-03-11- Frank Warmerdam** Remove reference to " +"OGRWin, move into ogr distribution" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:910 +msgid "" +"**Version 0.008 - 2001-03-21- Frank Warmerdam** Fix minor typos (h:12pt " +"instead of s:12pt in examples)" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:912 +msgid "" +"**Version 0.008 - 2000-07-15 - Stephane Villeneuve** Remove style table " +"in Layer. Add forecolor and backcolor to brush." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:914 +msgid "" +"**Version 0.007 - 2000-06-22 - Daniel Morissette** Fixed typo and added " +"offset param for PEN." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:916 +msgid "" +"**Version 0.006 - 2000-06-20 - Daniel Morissette** Added the OGR-Win idea" +" and made small changes here and there." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:918 +msgid "" +"**Version 0.005 - 2000-06-12 - Daniel Morissette** Allow passing of " +"comma-delimited list of names in PEN's \"id\" parameter. Defined system-" +"independent pen style names." +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:922 +msgid "" +"**Version 0.004 - 2000-06-09 - Stephane Villeneuve** Added PEN cap and " +"join parameters More clearly defined the API" +msgstr "" + +#: ../../source/user/ogr_feature_style.rst:925 +msgid "" +"**Version 0.003 - 2000-02-15 - Daniel Morissette** First kind-of-complete" +" version." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:5 +msgid "OGR SQL dialect" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:9 +msgid "" +"The GDALDataset supports executing commands against a datasource via the " +":cpp:func:`GDALDataset::ExecuteSQL` method. While in theory any sort of " +"command could be handled this way, in practice the mechanism is used to " +"provide a subset of SQL SELECT capability to applications. This page " +"discusses the generic SQL implementation implemented within OGR, and " +"issues with driver specific SQL support." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:16 +msgid "" +"The ``OGRSQL`` dialect can be requested with the ``OGRSQL`` string passed" +" as the dialect parameter of :cpp:func:`GDALDataset::ExecuteSQL`, or with" +" the `-dialect` option switch of the :ref:`ogrinfo` or :ref:`ogr2ogr` " +"utilities." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:20 +msgid "" +"An alternate dialect, the ``SQLite`` dialect, can be used instead of the " +"``OGRSQL`` dialect. Refer to the :ref:`sql_sqlite_dialect` page for more " +"details." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:23 +msgid "" +"The OGRLayer class also supports applying an attribute query filter to " +"features returned using the :cpp:func:`OGRLayer::SetAttributeFilter()` " +"method. The syntax for the attribute filter is the same as the WHERE " +"clause in the OGR SQL SELECT statement. So everything here with regard " +"to the WHERE clause applies in the context of the " +"``SetAttributeFilter()`` method." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:30 +msgid "SELECT" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:32 +msgid "" +"The SELECT statement is used to fetch layer features (analogous to table " +"rows in an RDBMS) with the result of the query represented as a temporary" +" layer of features. The layers of the datasource are analogous to tables " +"in an RDBMS and feature attributes are analogous to column values. The " +"simplest form of OGR SQL SELECT statement looks like this:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:42 +msgid "" +"In this case all features are fetched from the layer named \"polylayer\"," +" and all attributes of those features are returned. This is essentially " +"equivalent to accessing the layer directly. In this example the \"*\" is " +"the list of fields to fetch from the layer, with \"*\" meaning that all " +"fields should be fetched." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:48 +msgid "" +"This slightly more sophisticated form still pulls all features from the " +"layer but the schema will only contain the geometry column and the EAS_ID" +" and PROP_VALUE attributes. With OGR SQL dialect the geometry column is " +"always included in the result so it does not need to appear in the SQL " +"statement." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:57 +msgid "" +"A much more ambitious SELECT, restricting the features fetched with a " +"WHERE clause, and sorting the results might look like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:64 +msgid "" +"This select statement will produce a table with just one feature, with " +"geometry and one attribute (named something like \"count_eas_id\") " +"containing the number of distinct values of the eas_id attribute." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:73 +msgid "General syntax" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:75 +msgid "The general syntax of a SELECT statement is:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:84 +msgid "List Operators" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:86 +msgid "" +"The field list is a comma-separated list of the fields to be carried into" +" the output features from the source layer. They will appear on output " +"features in the order they appear on in the field list, so the field list" +" may be used to re-order the fields. The special character ``*`` is taken" +" to mean \"all fields\". The syntax ``* EXCLUDE ([fields])`` can be used " +"to select all fields except those listed in parentheses." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:93 +msgid "" +"A special form of the field list uses the DISTINCT keyword. This returns" +" a list of all the distinct values of the named attribute. When the " +"DISTINCT keyword is used, only one attribute may appear in the field " +"list. The DISTINCT keyword may be used against any type of field. " +"Currently the distinctness test against a string value is case " +"insensitive in OGR SQL. The result of a SELECT with a DISTINCT keyword " +"is a layer with one column (named the same as the field operated on), and" +" one feature per distinct value. Geometries are discarded. The distinct" +" values are assembled in memory, so a lot of memory may be used for " +"datasets with a large number of distinct values." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:108 +msgid "" +"There are also several summarization operators that may be applied to " +"columns. When a summarization operator is applied to any field, then all " +"fields must have summarization operators applied. The summarization " +"operators are COUNT (a count of instances), AVG (numerical average), SUM " +"(numerical sum), MIN (lexical or numerical minimum), and MAX (lexical or " +"numerical maximum). This example produces a variety of summarization " +"information on parcel property values:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:121 +msgid "" +"It is also possible to apply the COUNT() operator to a DISTINCT SELECT to" +" get a count of distinct values, for instance:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:128 +msgid "" +"As a special case, the COUNT() operator can be given a \"*\" argument " +"instead of a field name which is a short form for count all the records." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:136 +msgid "" +"Field names can also be prefixed by a table name though this is only " +"really meaningful when performing joins. It is further demonstrated in " +"the JOIN section." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:140 +msgid "" +"Field definitions can also be complex expressions using arithmetic, and " +"functional operators. However, the DISTINCT keyword, and summarization " +"operators like MIN, MAX, AVG and SUM may not be applied to expression " +"fields. Boolean resulting expressions (comparisons, logical operators) " +"can also be used." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:149 +msgid "or" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:157 +msgid "Functions" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:159 +msgid "" +"The SUBSTR function can be used to extract a substring from a string. Its" +" syntax is the following one : SUBSTR(string_expr, start_offset [, " +"length]). It extracts a substring of string_expr, starting at offset " +"start_offset (1 being the first character of string_expr, 2 the second " +"one, etc...). If start_offset is a negative value, the substring is " +"extracted from the end of the string (-1 is the last character of the " +"string, -2 the character before the last character, ...). If length is " +"specified, up to length characters are extracted from the string. " +"Otherwise the remainder of the string is extracted." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:167 +msgid "" +"Note: for the time being, the character as considered to be equivalent to" +" bytes, which may not be appropriate for multi-byte encodings like UTF-8." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:176 +msgid "" +"The ``hstore_get_value()`` function can be used to extract a value " +"associate to a key from a HSTORE string, formatted like " +"'key=>value,other_key=>other_value,...'" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:184 +msgid "Using the field name alias" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:186 +msgid "" +"OGR SQL supports renaming the fields following the SQL92 specification by" +" using the AS keyword according to the following example:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:193 +msgid "" +"The field name alias can be used as the last operation in the column " +"specification. Therefore we cannot rename the fields inside an operator, " +"but we can rename whole column expression, like these two:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:203 +msgid "Changing the type of the fields" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:205 +msgid "" +"OGR SQL supports changing the type of the columns by using the SQL92 " +"compliant CAST operator according to the following example:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:212 +msgid "Currently casting to the following target types are supported:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:214 +msgid "boolean" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:215 +msgid "character(field_length). By default, field_length=1." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:216 +msgid "float(field_length)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:217 +msgid "numeric(field_length, field_precision)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:218 +msgid "smallint(field_length) : 16 bit signed integer" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:219 +msgid "integer(field_length)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:220 +msgid "bigint(field_length), 64 bit integer, extension to SQL92" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:221 +msgid "date(field_length)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:222 +msgid "time(field_length)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:223 +msgid "timestamp(field_length)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:224 +msgid "geometry, geometry(geometry_type), geometry(geometry_type,epsg_code)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:226 +msgid "" +"Specifying the field_length and/or the field_precision is optional. An " +"explicit value of zero can be used as the width for character() to " +"indicate variable width. Conversion to the 'integer list', 'double list'" +" and 'string list' OGR data types are not supported, which doesn't " +"conform to the SQL92 specification." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:232 +msgid "" +"While the CAST operator can be applied anywhere in an expression, " +"including in a WHERE clause, the detailed control of output field format " +"is only supported if the CAST operator is the \"outer most\" operators on" +" a field in the field definition list. In other contexts it is still " +"useful to convert between numeric, string and date data types." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:238 +msgid "" +"Casting a WKT string to a geometry is allowed. geometry_type can be " +"POINT[Z], LINESTRING[Z], POLYGON[Z], MULTIPOINT[Z], MULTILINESTRING[Z], " +"MULTIPOLYGON[Z], GEOMETRYCOLLECTION[Z] or GEOMETRY[Z]." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:243 +msgid "String literals and identifiers quoting" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:245 +msgid "" +"Strict SQL92 rules are applied regarding string literals and identifiers " +"quoting." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:247 +msgid "" +"String literals (constants) must be surrounded with single-quote " +"characters. e.g. WHERE a_field = 'a_value'" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:250 +msgid "" +"Identifiers (column names and tables names) can be used unquoted if they " +"don't contain special characters or are not a SQL reserved keyword. " +"Otherwise they must be surrounded with double-quote characters. e.g. " +"WHERE \"from\" = 5." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:255 +msgid "WHERE" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:257 +msgid "" +"The argument to the WHERE clause is a logical expression used select " +"records from the source layer. In addition to its use within the WHERE " +"statement, the WHERE clause handling is also used for OGR attribute " +"queries on regular layers via :cpp:func:`OGRLayer::SetAttributeFilter`." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:262 +msgid "" +"In addition to the arithmetic and other functional operators available in" +" expressions in the field selection clause of the SELECT statement, in " +"the WHERE context logical operators are also available and the evaluated " +"value of the expression should be logical (true or false)." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:267 +msgid "" +"The available logical operators are ``=``, ``!=``, ``<>``, ``<``, ``>``, " +"``<=``, ``>=``, ``LIKE`` and ``ILIKE``, ``BETWEEN`` and ``IN``. Most of " +"the operators are self explanatory, but it is worth noting that ``!=`` is" +" the same as ``<>``, the string equality is case insensitive, but the " +"``<``, ``>``, ``<=`` and ``>=`` operators *are* case sensitive." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:283 +msgid "" +"Starting with GDAL 3.1, LIKE is case sensitive, and ILIKE is case " +"insensitive. In previous versions, LIKE was also case insensitive. If the" +" old behavior is wished in GDAL 3.1, the :config:`OGR_SQL_LIKE_AS_ILIKE` " +"can be set to ``YES``." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:287 +msgid "" +"Starting with GDAL 3.9, for layers declaring the OLCStringsAsUTF8 " +"capability (that is the content of their fields of String type is UTF-8 " +"encoded), UTF-8 characters are taken into account by ``LIKE`` and " +"``ILIKE`` operators. For ILIKE case insensitive comparisons, this is " +"restricted to the `ASCII " +"<https://en.wikipedia.org/wiki/Basic_Latin_(Unicode_block)>`__, `Latin-1 " +"Supplement <https://en.wikipedia.org/wiki/Latin-" +"1_Supplement_(Unicode_block)>`__, `Latin Extended-A " +"<https://en.wikipedia.org/wiki/Latin_Extended-A>`__, `Latin Extended-B " +"<https://en.wikipedia.org/wiki/Latin_Extended-B>`__, `Greek and Coptic " +"<https://en.wikipedia.org/wiki/Greek_and_Coptic>`__ and `Cyrillic " +"<https://en.wikipedia.org/wiki/Greek_and_Coptic>`__ Unicode categories." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:298 +msgid "" +"The value argument to the ``LIKE`` and ``ILIKE`` operators is a pattern " +"against which the value string is matched. In this pattern percent (%) " +"matches any number of characters, and underscore ( _ ) matches any one " +"character. An optional ESCAPE escape_char clause can be added so that the" +" percent or underscore characters can be searched as regular characters, " +"by being preceded with the escape_char." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:318 +msgid "" +"The ``IN`` takes a list of values as its argument and tests the attribute" +" value for membership in the provided set." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:330 +msgid "" +"The syntax of the ``BETWEEN`` operator is \"field_name BETWEEN value1 AND" +" value2\" and it is equivalent to \"field_name >= value1 AND field_name " +"<= value2\"." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:333 +msgid "" +"In addition to the above binary operators, there are additional operators" +" for testing if a field is null or not. These are the ``IS NULL`` and " +"``IS NOT NULL`` operators." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:337 +msgid "" +"Basic field tests can be combined in more complicated predicates using " +"logical operators include ``AND``, ``OR``, and the unary logical ``NOT``." +" Subexpressions should be bracketed to make precedence clear. Some more " +"complicated predicates are:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:349 +msgid "WHERE Limitations" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:351 +msgid "" +"Fields must all come from the primary table (the one listed in the FROM " +"clause)." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:353 +msgid "" +"All string comparisons are case insensitive except for ``<``, ``>``, " +"``<=`` and ``>=``" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:356 +msgid "ORDER BY" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:358 +msgid "" +"The ``ORDER BY`` clause is used force the returned features to be " +"reordered into sorted order (ascending or descending) on one or multiple " +"fields. Ascending (increasing) order is the default if neither the ASC or" +" DESC keyword is provided. For example:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:371 +msgid "" +"Note that ORDER BY clauses cause two passes through the feature set. One" +" to build an in-memory table of field values corresponded with feature " +"ids, and a second pass to fetch the features by feature id in the sorted " +"order. For formats which cannot efficiently randomly read features by " +"feature id this can be a very expensive operation." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:377 +msgid "" +"Sorting of string field values is case sensitive, not case insensitive " +"like in most other parts of OGR SQL." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:381 +msgid "LIMIT and OFFSET" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:383 +msgid "" +"Starting with GDAL 2.2, the ``LIMIT`` clause can be used to limit the " +"number of features returned. For example" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:390 +msgid "" +"The ``OFFSET`` clause can be used to skip the first features of the " +"result set. The value after OFFSET is the number of features skipped. For" +" example, to skip the first 3 features from the result set:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:398 +msgid "Both clauses can be combined:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:405 +msgid "JOINs" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:407 +msgid "" +"OGR SQL supports a limited form of one to one JOIN. This allows records " +"from a secondary table to be looked up based on a shared key between it " +"and the primary table being queried. For instance, a table of city " +"locations might include a **nation_id** column that can be used as a " +"reference into a secondary **nation** table to fetch a nation name. A " +"joined query might look like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:419 +msgid "" +"This query would result in a table with all the fields from the city " +"table, and an additional \"nation.name\" field with the nation name " +"pulled from the nation table by looking for the record in the nation " +"table that has the \"id\" field with the same value as the city.nation_id" +" field." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:424 +msgid "" +"Joins introduce a number of additional issues. One is the concept of " +"table qualifiers on field names. For instance, referring to " +"city.nation_id instead of just nation_id to indicate the nation_id field " +"from the city layer. The table name qualifiers may only be used in the " +"field list, and within the ``ON`` clause of the join." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:430 +msgid "" +"Wildcards are also somewhat more involved. All fields from the primary " +"table (**city** in this case) and the secondary table (**nation** in this" +" case) may be selected using the usual ``*`` wildcard. But the fields of" +" just one of the primary or secondary table may be selected by prefixing " +"the asterix with the table name." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:436 +msgid "" +"The field names in the resulting query layer will be qualified by the " +"table name, if the table name is given as a qualifier in the field list." +" In addition field names will be qualified with a table name if they " +"would conflict with earlier fields. For instance, the following select " +"would result might result in a results set with a **name, nation_id, " +"nation.nation_id** and ** nation.name** field if the city and nation " +"tables both have the **nation_id** and **name** fieldnames." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:448 +msgid "" +"On the other hand if the nation table had a **continent_id** field, but " +"the city table did not, then that field would not need to be qualified in" +" the result set. However, if the selected instead looked like the " +"following statement, all result fields would be qualified by the table " +"name." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:458 +msgid "" +"In the above examples, the **nation** table was found in the same " +"datasource as the **city** table. However, the OGR join support " +"includes the ability to join against a table in a different data source, " +"potentially of a different format. This is indicated by qualifying the " +"secondary table name with a datasource name. In this case the secondary " +"datasource is opened using normal OGR semantics and utilized to access " +"the secondary table until the query result is no longer needed." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:471 +msgid "" +"While not necessarily very useful, it is also possible to introduce table" +" aliases to simplify some SELECT statements. This can also be useful to " +"disambiguate situations where tables of the same name are being used from" +" different data sources. For instance, if the actual tables names were " +"messy we might want to do something like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:483 +msgid "It is possible to do multiple joins in a single query." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:491 +msgid "" +"The expression after ON is typically of the form " +"\"{primary_table}.{field_name} = {secondary_table}.{field_name}\", and in" +" that order. It is also possible to use a more complex boolean " +"expression, involving multiple comparison operators, but with the " +"restrictions mentioned in the below \"JOIN limitations\" section. In " +"particular, in case of multiple joins (3 tables or more) the fields " +"compared in a JOIN must belong to the primary table (the one after FROM) " +"and the table of the active JOIN." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:501 +msgid "JOIN Limitations" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:503 +msgid "" +"Joins can be very expensive operations if the secondary table is not " +"indexed on the key field being used." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:504 +msgid "" +"Joined fields may not be used in WHERE clauses, or ORDER BY clauses at " +"this time. The join is essentially evaluated after all primary table " +"subsetting is complete, and after the ORDER BY pass." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:505 +msgid "" +"Joined fields may not be used as keys in later joins. So you could not " +"use the province id in a city to lookup the province record, and then use" +" a nation id from the province id to lookup the nation record. This is a" +" sensible thing to want and could be implemented, but is not currently " +"supported." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:506 +msgid "" +"Datasource names for joined tables are evaluated relative to the current " +"processes working directory, not the path to the primary datasource." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:507 +msgid "" +"These are not true LEFT or RIGHT joins in the RDBMS sense. Whether or " +"not a secondary record exists for the join key or not, one and only one " +"copy of the primary record is returned in the result set. If a secondary" +" record cannot be found, the secondary derived fields will be NULL. If " +"more than one matching secondary field is found only the first will be " +"used." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:510 +msgid "UNION ALL" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:512 +msgid "" +"The SQL engine can deal with several SELECT combined with UNION ALL. The " +"effect of UNION ALL is to concatenate the rows returned by the right " +"SELECT statement to the rows returned by the left SELECT statement." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:523 +msgid "UNION ALL restrictions" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:525 +msgid "" +"The processing of UNION ALL in OGR differs from the SQL standard, in " +"which it accepts that the columns from the various SELECT are not " +"identical. In that case, it will return a super-set of all the fields " +"from each SELECT statement." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:529 +msgid "" +"There is also a restriction : ORDER BY can only be specified for each " +"SELECT, and not at the level of the result of the union." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:533 +msgid "SPECIAL FIELDS" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:535 +msgid "" +"The OGR SQL query processor treats some attributes of the features as " +"built-in special fields which can be used in SQL statements alongside the" +" other fields. These fields can be placed in the SELECT list, the WHERE " +"clause and the ORDER BY clause respectively. Special fields will not be " +"included in the result by default but they may be explicitly included by " +"adding them to the SELECT list. When accessing field values, the special " +"fields will take precedence over other fields in the data source with the" +" same names." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:545 +#: ../../source/user/sql_sqlite_dialect.rst:161 +msgid "Feature id (FID)" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:547 +msgid "" +"Normally the feature id is a special property of a feature and not " +"treated as an attribute of the feature. In some cases it is convenient " +"to be able to utilize the feature id in queries and result sets as a " +"regular field. To do so use the name ``FID``. If the layer has a named " +"FID column (:cpp:func:`OGRLayer::GetFIDColumn` != \"\"), this name may " +"also be used." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:554 +#: ../../source/user/sql_sqlite_dialect.rst:171 +#: ../../source/user/sql_sqlite_dialect.rst:179 +msgid "" +"The field wildcard expansions will not include the feature id, but it may" +" be explicitly included using a syntax like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:562 +#: ../../source/user/sql_sqlite_dialect.rst:120 +msgid "Geometry field" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:564 +msgid "" +"The OGR SQL dialect adds the geometry field of the datasource to the " +"result set by default. Users do not need to select the geometry " +"explicitly but it is still possible to do so. Common use case is when " +"geometry is the only field that is needed. In this case the name of the " +"geometry field to be used in the SQL statement is the name returned by " +":cpp:func:`OGRLayer::GetGeometryColumn`, and also \"Geometry Column = " +"...\" in :program:`ogrinfo` output. If the method returns an empty string" +" then a special name \"_ogr_geometry_\" must be used. The name begins " +"with an underscore and SQL syntax requires that it must appear between " +"double quotes. In addition the command line interpreter may require that " +"double quotes are escaped and the final SELECT statement could look like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:580 +msgid "OGR_GEOMETRY" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:582 +msgid "" +"Some of the data sources (like MapInfo tab) can handle geometries of " +"different types within the same layer. The ``OGR_GEOMETRY`` special field" +" represents the geometry type returned by " +":cpp:func:`OGRGeometry::getGeometryName` and can be used to distinguish " +"the various types. By using this field one can select particular types of" +" the geometries like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:593 +msgid "OGR_GEOM_WKT" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:595 +msgid "" +"The Well Known Text representation of the geometry can also be used as a " +"special field. To select the WKT of the geometry ``OGR_GEOM_WKT`` might " +"be included in the select list, like:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:603 +msgid "" +"Using the ``OGR_GEOM_WKT`` and the ``LIKE`` operator in the WHERE clause " +"we can get similar effect as using OGR_GEOMETRY:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:612 +msgid "OGR_GEOM_AREA" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:614 +msgid "" +"The ``OGR_GEOM_AREA`` special field returns the area of the feature's " +"geometry computed by the OGRSurface::get_Area() method. For " +"OGRGeometryCollection and OGRMultiPolygon the value is the sum of the " +"areas of its members. For non-surface geometries the returned area is " +"0.0." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:619 +msgid "For example, to select only polygon features larger than a given area:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:626 +msgid "OGR_STYLE" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:628 +#: ../../source/user/sql_sqlite_dialect.rst:195 +msgid "" +"The ``OGR_STYLE`` special field represents the style string of the " +"feature returned by OGRFeature::GetStyleString(). By using this field and" +" the ``LIKE`` operator the result of the query can be filtered by the " +"style. For example we can select the annotation features as:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:638 +msgid "" +"It is possible to use the ``OGR_STYLE`` field name as a special field " +"name in the field selection as an alternate way of setting the " +":cpp:func:`OGRFeature::SetStyleString` value, typically by aliasing " +"another field or a string literal." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:647 +msgid "" +"By default, the OGR_STYLE field will still be visible as a regular field." +" If this is undesirable, starting with GDAL 3.10, it can be hidden by " +"adding the HIDDEN keyword at the end of the field specification." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:657 +msgid "CREATE INDEX" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:659 +msgid "" +"Some OGR SQL drivers support creating of attribute indexes. Currently " +"this includes the Shapefile driver. An index accelerates very simple " +"attribute queries of the form **fieldname = value**, which is what is " +"used by the ``JOIN`` capability. To create an attribute index on the " +"nation_id field of the nation table a command like this would be used:" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:670 +msgid "Index Limitations" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:672 +msgid "" +"Indexes are not maintained dynamically when new features are added to or " +"removed from a layer." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:673 +msgid "" +"Very long strings (longer than 256 characters?) cannot currently be " +"indexed." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:674 +msgid "" +"To recreate an index it is necessary to drop all indexes on a layer and " +"then recreate all the indexes." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:675 +msgid "" +"Indexes are not used in any complex queries. Currently the only query " +"the will accelerate is a simple \"field = value\" query." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:678 +msgid "DROP INDEX" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:680 +msgid "" +"The OGR SQL DROP INDEX command can be used to drop all indexes on a " +"particular table, or just the index for a particular column." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:689 +msgid "ALTER TABLE" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:691 +msgid "The following OGR SQL ALTER TABLE commands can be used." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:693 +msgid "" +"-\"ALTER TABLE tablename ADD [COLUMN] columnname columntype\" to add a " +"new field. Supported if the layer declares the OLCCreateField capability." +" -\"ALTER TABLE tablename RENAME [COLUMN] oldcolumnname TO " +"newcolumnname\" to rename an existing field. Supported if the layer " +"declares the OLCAlterFieldDefn capability. -\"ALTER TABLE tablename ALTER" +" [COLUMN] columnname TYPE columntype\" to change the type of an existing " +"field. Supported if the layer declares the OLCAlterFieldDefn capability. " +"-\"ALTER TABLE tablename DROP [COLUMN] columnname\" to delete an existing" +" field. Supported if the layer declares the OLCDeleteField capability." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:698 +msgid "" +"The columntype value follows the syntax of the types supported by the " +"CAST operator described above." +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:708 +msgid "DROP TABLE" +msgstr "" + +#: ../../source/user/ogr_sql_dialect.rst:710 +msgid "" +"The OGR SQL DROP TABLE command can be used to delete a table. This is " +"only supported on datasources that declare the ODsCDeleteLayer " +"capability." +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:5 +msgid "OGR SQL dialect and SQLITE SQL dialect" +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:7 +msgid "" +"The GDALDataset supports executing commands against a datasource via the " +":cpp:func:`GDALDataset::ExecuteSQL` method. How such commands are " +"evaluated is dependent on the datasets." +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:11 +msgid "" +"For most file formats (e.g. Shapefiles, GeoJSON, MapInfo files), the " +"built-in :ref:`ogr_sql_dialect` dialect will be used by defaults. It is " +"also possible to request the :ref:`sql_sqlite_dialect` alternate dialect " +"to be used, which will use the SQLite engine to evaluate commands on GDAL" +" datasets." +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:16 +msgid "" +"All OGR drivers for database systems: :ref:`vector.mysql`, " +":ref:`vector.pg`, :ref:`vector.oci`, :ref:`vector.sqlite`, " +":ref:`vector.gpkg`, :ref:`vector.odbc`, :ref:`vector.pgeo`, " +":ref:`vector.hana` and :ref:`vector.mssqlspatial`, override the " +":cpp:func:`GDALDataset::ExecuteSQL` function with dedicated " +"implementation and, by default, pass the SQL statements directly to the " +"underlying RDBMS. In these cases the SQL syntax varies in some " +"particulars from OGR SQL. Also, anything possible in SQL can then be " +"accomplished for these particular databases. Generally, only the result " +"of SELECT statements will be returned as layers. For those drivers, it is" +" also possible to explicitly request the ``OGRSQL`` and ``SQLITE`` " +"dialects, although performance will generally be much less as the native " +"SQL engine of those database systems." +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:29 +msgid "Dialects" +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:39 +msgid "ExecuteSQL()" +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:41 +msgid "" +"SQL is executed against an GDALDataset, not against a specific layer. " +"The call looks like this:" +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:50 +msgid "" +"The ``pszDialect`` argument is in theory intended to allow for support of" +" different command languages against a provider, but for now applications" +" should always pass an empty (not NULL) string to get the default " +"dialect." +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:54 +msgid "" +"The ``poSpatialFilter`` argument is a geometry used to select a bounding " +"rectangle for features to be returned in a manner similar to the " +":cpp:func:`OGRLayer::SetSpatialFilter` method. It may be NULL for no " +"special spatial restriction." +msgstr "" + +#: ../../source/user/ogr_sql_sqlite_dialect.rst:59 +msgid "" +"The result of an ExecuteSQL() call is usually a temporary OGRLayer " +"representing the results set from the statement. This is the case for a " +"SELECT statement for instance. The returned temporary layer should be " +"released with :cpp:func:`GDALDataset::ReleaseResultsSet` method when no " +"longer needed. Failure to release it before the datasource is destroyed " +"may result in a crash." +msgstr "" + +#: ../../source/user/raster_data_model.rst:5 +msgid "Raster Data Model" +msgstr "" + +#: ../../source/user/raster_data_model.rst:7 +msgid "" +"This document attempts to describe the GDAL data model. That is the types" +" of information that a GDAL data store can contain, and their semantics." +msgstr "" + +#: ../../source/user/raster_data_model.rst:10 +#: ../../source/user/vector_data_model.rst:123 +msgid "Dataset" +msgstr "" + +#: ../../source/user/raster_data_model.rst:12 +msgid "" +"A dataset (represented by the :cpp:class:`GDALDataset` class) is an " +"assembly of related raster bands and some information common to them all." +" In particular the dataset has a concept of the raster size (in pixels " +"and lines) that applies to all the bands. The dataset is also responsible" +" for the georeferencing transform and coordinate system definition of all" +" bands. The dataset itself can also have associated metadata, a list of " +"name/value pairs in string form." +msgstr "" + +#: ../../source/user/raster_data_model.rst:14 +msgid "" +"Note that the GDAL dataset, and raster band data model is loosely based " +"on the OpenGIS Grid Coverages specification." +msgstr "" + +#: ../../source/user/raster_data_model.rst:17 +msgid "Coordinate System" +msgstr "" + +#: ../../source/user/raster_data_model.rst:18 +msgid "" +"Dataset coordinate systems are represented as OpenGIS Well Known Text " +"strings. This can contain:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:20 +msgid "An overall coordinate system name." +msgstr "" + +#: ../../source/user/raster_data_model.rst:21 +msgid "A geographic coordinate system name." +msgstr "" + +#: ../../source/user/raster_data_model.rst:22 +msgid "A datum identifier." +msgstr "" + +#: ../../source/user/raster_data_model.rst:23 +msgid "An ellipsoid name, semi-major axis, and inverse flattening." +msgstr "" + +#: ../../source/user/raster_data_model.rst:24 +msgid "A prime meridian name and offset from Greenwich." +msgstr "" + +#: ../../source/user/raster_data_model.rst:25 +msgid "A projection method type (e.g., Transverse Mercator)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:26 +msgid "A list of projection parameters (e.g., central_meridian)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:27 +msgid "A units name, and conversion factor to meters or radians." +msgstr "" + +#: ../../source/user/raster_data_model.rst:28 +msgid "Names and ordering for the axes." +msgstr "" + +#: ../../source/user/raster_data_model.rst:29 +msgid "" +"Codes for most of the above in terms of predefined coordinate systems " +"from authorities such as EPSG." +msgstr "" + +#: ../../source/user/raster_data_model.rst:31 +msgid "" +"For more information on OpenGIS WKT coordinate system definitions, and " +"mechanisms to manipulate them, refer to the osr_tutorial document and/or " +"the OGRSpatialReference class documentation." +msgstr "" + +#: ../../source/user/raster_data_model.rst:33 +msgid "" +"The coordinate system returned by " +":cpp:func:`GDALDataset::GetProjectionRef` describes the georeferenced " +"coordinates implied by the affine georeferencing transform returned by " +":cpp:func:`GDALDataset::GetGeoTransform`. The coordinate system returned " +"by :cpp:func:`GDALDataset::GetGCPProjection` describes the georeferenced " +"coordinates of the GCPs returned by :cpp:func:`GDALDataset::GetGCPs`." +msgstr "" + +#: ../../source/user/raster_data_model.rst:35 +msgid "" +"Note that a returned coordinate system strings of \"\" indicates nothing " +"is known about the georeferencing coordinate system." +msgstr "" + +#: ../../source/user/raster_data_model.rst:40 +msgid "Affine GeoTransform" +msgstr "" + +#: ../../source/user/raster_data_model.rst:42 +msgid "" +"GDAL datasets have two ways of describing the relationship between raster" +" positions (in pixel/line coordinates) and georeferenced coordinates. The" +" first, and most commonly used is the affine transform (the other is " +"GCPs)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:44 +msgid "" +"The affine transform consists of six coefficients returned by " +":cpp:func:`GDALDataset::GetGeoTransform` which map pixel/line coordinates" +" into georeferenced space using the following relationship:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:51 +msgid "" +"In case of north up images, the GT(2) and GT(4) coefficients are zero, " +"and the GT(1) is pixel width, and GT(5) is pixel height. The " +"(GT(0),GT(3)) position is the top left corner of the top left pixel of " +"the raster." +msgstr "" + +#: ../../source/user/raster_data_model.rst:53 +msgid "" +"Note that the pixel/line coordinates in the above are from (0.0,0.0) at " +"the top left corner of the top left pixel to " +"(width_in_pixels,height_in_pixels) at the bottom right corner of the " +"bottom right pixel. The pixel/line location of the center of the top left" +" pixel would therefore be (0.5,0.5)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:56 +msgid "GCPs" +msgstr "" + +#: ../../source/user/raster_data_model.rst:58 +msgid "" +"A dataset can have a set of control points relating one or more positions" +" on the raster to georeferenced coordinates. All GCPs share a " +"georeferencing coordinate system (returned by " +":cpp:func:`GDALDataset::GetGCPProjection`). Each GCP (represented as the " +"GDAL_GCP class) contains the following:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:73 +msgid "" +"The pszId string is intended to be a unique (and often, but not always " +"numerical) identifier for the GCP within the set of GCPs on this dataset." +" The pszInfo is usually an empty string, but can contain any user defined" +" text associated with the GCP. Potentially this can also contain machine " +"parsable information on GCP status though that isn't done at this time." +msgstr "" + +#: ../../source/user/raster_data_model.rst:75 +msgid "" +"The (Pixel,Line) position is the GCP location on the raster. The (X,Y,Z) " +"position is the associated georeferenced location with the Z often being " +"zero." +msgstr "" + +#: ../../source/user/raster_data_model.rst:77 +msgid "" +"The GDAL data model does not imply a transformation mechanism that must " +"be generated from the GCPs ... this is left to the application. However " +"1st to 5th order polynomials are common." +msgstr "" + +#: ../../source/user/raster_data_model.rst:79 +msgid "" +"Normally a dataset will contain either an affine geotransform, GCPs or " +"neither. It is uncommon to have both, and it is undefined which is " +"authoritative." +msgstr "" + +#: ../../source/user/raster_data_model.rst:82 +msgid "Metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:84 +msgid "" +"GDAL metadata is auxiliary format and application specific textual data " +"kept as a list of name/value pairs. The names are required to be well " +"behaved tokens (no spaces, or odd characters). The values can be of any " +"length, and contain anything except an embedded null (ASCII zero)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:86 +msgid "" +"The metadata handling system is not well tuned to handling very large " +"bodies of metadata. Handling of more than 100K of metadata for a dataset " +"is likely to lead to performance degradation." +msgstr "" + +#: ../../source/user/raster_data_model.rst:88 +msgid "" +"Some formats will support generic (user defined) metadata, while other " +"format drivers will map specific format fields to metadata names. For " +"instance the TIFF driver returns a few information tags as metadata " +"including the date/time field which is returned as:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:94 +msgid "" +"Metadata is split into named groups called domains, with the default " +"domain having no name (NULL or \"\"). Some specific domains exist for " +"special purposes. Note that currently there is no way to enumerate all " +"the domains available for a given object, but applications can \"test\" " +"for any domains they know how to interpret." +msgstr "" + +#: ../../source/user/raster_data_model.rst:96 +msgid "" +"The following metadata items have well defined semantics in the default " +"domain:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:98 +msgid "" +"AREA_OR_POINT: May be either \"Area\" (the default) or \"Point\". " +"Indicates whether a pixel value should be assumed to represent a sampling" +" over the region of the pixel or a point sample at the center of the " +"pixel. This is not intended to influence interpretation of georeferencing" +" which remains area oriented." +msgstr "" + +#: ../../source/user/raster_data_model.rst:99 +msgid "" +"NODATA_VALUES: The value is a list of space separated pixel values " +"matching the number of bands in the dataset that can be collectively used" +" to identify pixels that are nodata in the dataset. With this style of " +"nodata a pixel is considered nodata in all bands if and only if all bands" +" match the corresponding value in the NODATA_VALUES tuple. This metadata " +"is not widely honoured by GDAL drivers, algorithms or utilities at this " +"time." +msgstr "" + +#: ../../source/user/raster_data_model.rst:100 +msgid "" +"MATRIX_REPRESENTATION: This value, used for Polarimetric SAR datasets, " +"contains the matrix representation that this data is provided in. The " +"following are acceptable values:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:102 +msgid "SCATTERING" +msgstr "" + +#: ../../source/user/raster_data_model.rst:103 +msgid "SYMMETRIZED_SCATTERING" +msgstr "" + +#: ../../source/user/raster_data_model.rst:104 +msgid "COVARIANCE" +msgstr "" + +#: ../../source/user/raster_data_model.rst:105 +msgid "SYMMETRIZED_COVARIANCE" +msgstr "" + +#: ../../source/user/raster_data_model.rst:106 +msgid "COHERENCY" +msgstr "" + +#: ../../source/user/raster_data_model.rst:107 +msgid "SYMMETRIZED_COHERENCY" +msgstr "" + +#: ../../source/user/raster_data_model.rst:108 +msgid "KENNAUGH" +msgstr "" + +#: ../../source/user/raster_data_model.rst:109 +msgid "SYMMETRIZED_KENNAUGH" +msgstr "" + +#: ../../source/user/raster_data_model.rst:110 +msgid "" +"POLARIMETRIC_INTERP: This metadata item is defined for Raster Bands for " +"polarimetric SAR data. This indicates which entry in the specified matrix" +" representation of the data this band represents. For a dataset provided " +"as a scattering matrix, for example, acceptable values for this metadata " +"item are HH, HV, VH, VV. When the dataset is a covariance matrix, for " +"example, this metadata item will be one of Covariance_11, Covariance_22, " +"Covariance_33, Covariance_12, Covariance_13, Covariance_23 (since the " +"matrix itself is a hermitian matrix, that is all the data that is " +"required to describe the matrix)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:111 +msgid "" +"METADATATYPE: If IMAGERY Domain present, the item consist the reader " +"which processed the metadata. Now present such readers:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:113 +msgid "DG: DigitalGlobe imagery metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:114 +msgid "GE: GeoEye (or formally SpaceImaging) imagery metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:115 +msgid "OV: OrbView imagery metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:116 +msgid "DIMAP: Pleiades imagery metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:117 +msgid "MSP: Resurs DK-1 imagery metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:118 +msgid "ODL: Landsat imagery metadata" +msgstr "" + +#: ../../source/user/raster_data_model.rst:119 +msgid "" +"CACHE_PATH: A cache directory path. Now this metadata item sets only by " +"WMS driver. This is useful when dataset deletes with cached data or when " +"external program need to put tiles in cache for some area of interest." +msgstr "" + +#: ../../source/user/raster_data_model.rst:122 +msgid "SUBDATASETS Domain" +msgstr "" + +#: ../../source/user/raster_data_model.rst:124 +msgid "" +"The SUBDATASETS domain holds a list of child datasets. Normally this is " +"used to provide pointers to a list of images stored within a single multi" +" image file." +msgstr "" + +#: ../../source/user/raster_data_model.rst:126 +msgid "" +"For example, an NITF with two images might have the following subdataset " +"list." +msgstr "" + +#: ../../source/user/raster_data_model.rst:135 +msgid "" +"The value of the _NAME is the string that can be passed to " +":cpp:func:`GDALOpen` to access the file. The _DESC value is intended to " +"be a more user friendly string that can be displayed to the user in a " +"selector." +msgstr "" + +#: ../../source/user/raster_data_model.rst:137 +msgid "" +"Drivers which support subdatasets advertise the ``DMD_SUBDATASETS`` " +"capability. This information is reported when the --format and --formats " +"options are passed to the command line utilities." +msgstr "" + +#: ../../source/user/raster_data_model.rst:139 +msgid "" +"Currently, drivers which support subdatasets are: ADRG, ECRGTOC, " +"GEORASTER, GTiff, HDF4, HDF5, netCDF, NITF, NTv2, OGDI, PDF, " +"PostGISRaster, Rasterlite, RPFTOC, RS2, TileDB, WCS, and WMS." +msgstr "" + +#: ../../source/user/raster_data_model.rst:142 +msgid "IMAGE_STRUCTURE Domain" +msgstr "" + +#: ../../source/user/raster_data_model.rst:144 +msgid "" +"Metadata in the default domain is intended to be related to the image, " +"and not particularly related to the way the image is stored on disk. That" +" is, it is suitable for copying with the dataset when it is copied to a " +"new format. Some information of interest is closely tied to a particular " +"file format and storage mechanism. In order to prevent this getting " +"copied along with datasets it is placed in a special domain called " +"IMAGE_STRUCTURE that should not normally be copied to new formats." +msgstr "" + +#: ../../source/user/raster_data_model.rst:146 +msgid "" +"Currently the following items are defined by :ref:`rfc-14` as having " +"specific semantics in the IMAGE_STRUCTURE domain." +msgstr "" + +#: ../../source/user/raster_data_model.rst:148 +msgid "" +"COMPRESSION: The compression type used for this dataset or band. There is" +" no fixed catalog of compression type names, but where a given format " +"includes a COMPRESSION creation option, the same list of values should be" +" used here as there." +msgstr "" + +#: ../../source/user/raster_data_model.rst:149 +msgid "" +"NBITS: The actual number of bits used for this band, or the bands of this" +" dataset. Normally only present when the number of bits is non-standard " +"for the datatype, such as when a 1 bit TIFF is represented through GDAL " +"as GDT_Byte." +msgstr "" + +#: ../../source/user/raster_data_model.rst:150 +msgid "" +"INTERLEAVE: This only applies on datasets, and the value should be one of" +" PIXEL, LINE or BAND. It can be used as a data access hint." +msgstr "" + +#: ../../source/user/raster_data_model.rst:151 +msgid "" +"PIXELTYPE: This may appear on a GDT_Byte band (or the corresponding " +"dataset) and have the value SIGNEDBYTE to indicate the unsigned byte " +"values between 128 and 255 should be interpreted as being values between " +"-128 and -1 for applications that recognise the SIGNEDBYTE type. Starting" +" with GDAL 3.7, this metadata item is no longer used, as the Int8 data " +"type is used for signed bytes." +msgstr "" + +#: ../../source/user/raster_data_model.rst:158 +msgid "RPC Domain" +msgstr "" + +#: ../../source/user/raster_data_model.rst:160 +msgid "" +"The RPC metadata domain holds metadata describing the Rational Polynomial" +" Coefficient geometry model for the image if present. This geometry model" +" can be used to transform between pixel/line and georeferenced locations." +" The items defining the model are:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:162 +msgid "" +"ERR_BIAS: Error - Bias. The RMS bias error in meters per horizontal axis " +"of all points in the image (-1.0 if unknown)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:163 +msgid "" +"ERR_RAND: Error - Random. RMS random error in meters per horizontal axis " +"of each point in the image (-1.0 if unknown)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:164 +msgid "LINE_OFF: Line Offset" +msgstr "" + +#: ../../source/user/raster_data_model.rst:165 +msgid "SAMP_OFF: Sample Offset" +msgstr "" + +#: ../../source/user/raster_data_model.rst:166 +msgid "LAT_OFF: Geodetic Latitude Offset" +msgstr "" + +#: ../../source/user/raster_data_model.rst:167 +msgid "LONG_OFF: Geodetic Longitude Offset" +msgstr "" + +#: ../../source/user/raster_data_model.rst:168 +msgid "HEIGHT_OFF: Geodetic Height Offset" +msgstr "" + +#: ../../source/user/raster_data_model.rst:169 +msgid "LINE_SCALE: Line Scale" +msgstr "" + +#: ../../source/user/raster_data_model.rst:170 +msgid "SAMP_SCALE: Sample Scale" +msgstr "" + +#: ../../source/user/raster_data_model.rst:171 +msgid "LAT_SCALE: Geodetic Latitude Scale" +msgstr "" + +#: ../../source/user/raster_data_model.rst:172 +msgid "LONG_SCALE: Geodetic Longitude Scale" +msgstr "" + +#: ../../source/user/raster_data_model.rst:173 +msgid "HEIGHT_SCALE: Geodetic Height Scale" +msgstr "" + +#: ../../source/user/raster_data_model.rst:174 +msgid "" +"LINE_NUM_COEFF (1-20): Line Numerator Coefficients. Twenty coefficients " +"for the polynomial in the Numerator of the rn equation. (space separated)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:175 +msgid "" +"LINE_DEN_COEFF (1-20): Line Denominator Coefficients. Twenty coefficients" +" for the polynomial in the Denominator of the rn equation. (space " +"separated)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:176 +msgid "" +"SAMP_NUM_COEFF (1-20): Sample Numerator Coefficients. Twenty coefficients" +" for the polynomial in the Numerator of the cn equation. (space " +"separated)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:177 +msgid "" +"SAMP_DEN_COEFF (1-20): Sample Denominator Coefficients. Twenty " +"coefficients for the polynomial in the Denominator of the cn equation. " +"(space separated)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:179 +msgid "" +"These fields are directly derived from the document prospective GeoTIFF " +"RPC document (http://geotiff.maptools.org/rpc_prop.html) which in turn is" +" closely modeled on the NITF RPC00B definition." +msgstr "" + +#: ../../source/user/raster_data_model.rst:181 +msgid "" +"The line and pixel offset expressed with LINE_OFF and SAMP_OFF are with " +"respect to the center of the pixel." +msgstr "" + +#: ../../source/user/raster_data_model.rst:184 +msgid "IMAGERY Domain (remote sensing)" +msgstr "" + +#: ../../source/user/raster_data_model.rst:186 +msgid "" +"For satellite or aerial imagery the IMAGERY Domain may be present. It " +"depends on the existence of special metadata files near the image file. " +"The files at the same directory with image file tested by the set of " +"metadata readers, if files can be processed by the metadata reader, it " +"fill the IMAGERY Domain with the following items:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:188 +msgid "SATELLITEID: A satellite or scanner name" +msgstr "" + +#: ../../source/user/raster_data_model.rst:189 +msgid "" +"CLOUDCOVER: Cloud coverage. The value between 0 - 100 or 999 if not " +"available" +msgstr "" + +#: ../../source/user/raster_data_model.rst:190 +msgid "ACQUISITIONDATETIME: The image acquisition date time in UTC" +msgstr "" + +#: ../../source/user/raster_data_model.rst:193 +msgid "xml: Domains" +msgstr "" + +#: ../../source/user/raster_data_model.rst:195 +msgid "" +"Any domain name prefixed with \"xml:\" is not normal name/value metadata." +" It is a single XML document stored in one big string." +msgstr "" + +#: ../../source/user/raster_data_model.rst:198 +msgid "Raster Band" +msgstr "" + +#: ../../source/user/raster_data_model.rst:200 +msgid "" +"A raster band is represented in GDAL with the :cpp:class:`GDALRasterBand`" +" class. It represents a single raster band/channel/layer. It does not " +"necessarily represent a whole image. For instance, a 24bit RGB image " +"would normally be represented as a dataset with three bands, one for red," +" one for green and one for blue." +msgstr "" + +#: ../../source/user/raster_data_model.rst:202 +msgid "A raster band has the following properties:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:204 +msgid "" +"A width and height in pixels and lines. This is the same as that defined " +"for the dataset, if this is a full resolution band." +msgstr "" + +#: ../../source/user/raster_data_model.rst:205 +msgid "" +"A datatype (GDALDataType). One of Byte, Int8, UInt16, Int16, UInt32, " +"Int32, UInt64, Int64, Float32, Float64, and the complex types CInt16, " +"CInt32, CFloat32, and CFloat64." +msgstr "" + +#: ../../source/user/raster_data_model.rst:207 +msgid "" +"UInt64 and Int64 data types have been added in GDAL 3.5. Beyond reading " +"and write pixel values, their support is limited. Some algorithms might " +"use 64-bit floating-point internally (warping), as well as some methods " +"returning only double values (GetMinimum(), GetMaximum(), etc.), or even " +"32-bit floating point (overview, RasterIO resampling). Hence the range " +"where exact values are preserved can be [0, 2^53] (or less if 32-bit " +"floating-point is used)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:209 +msgid "Int8 data type has been added in GDAL 3.7." +msgstr "" + +#: ../../source/user/raster_data_model.rst:211 +msgid "" +"A block size. This is a preferred (efficient) access chunk size. For " +"tiled images this will be one tile. For scanline oriented images this " +"will normally be one scanline." +msgstr "" + +#: ../../source/user/raster_data_model.rst:212 +msgid "" +"A list of name/value pair metadata in the same format as the dataset, but" +" of information that is potentially specific to this band." +msgstr "" + +#: ../../source/user/raster_data_model.rst:213 +msgid "An optional description string." +msgstr "" + +#: ../../source/user/raster_data_model.rst:214 +msgid "" +"An optional single nodata pixel value (see also NODATA_VALUES metadata on" +" the dataset for multi-band style nodata values)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:215 +msgid "" +"An optional nodata mask band marking pixels as nodata or in some cases " +"transparency as discussed in RFC 15: Band Masks and documented in " +"GDALRasterBand::GetMaskBand()." +msgstr "" + +#: ../../source/user/raster_data_model.rst:216 +msgid "" +"An optional list of category names (effectively class names in a thematic" +" image)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:217 +msgid "An optional minimum and maximum value." +msgstr "" + +#: ../../source/user/raster_data_model.rst:218 +msgid "Optional statistics stored in metadata:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:220 +msgid "STATISTICS_MEAN: mean" +msgstr "" + +#: ../../source/user/raster_data_model.rst:221 +msgid "STATISTICS_MINIMUM: minimum" +msgstr "" + +#: ../../source/user/raster_data_model.rst:222 +msgid "STATISTICS_MAXIMUM: maximum" +msgstr "" + +#: ../../source/user/raster_data_model.rst:223 +msgid "STATISTICS_STDDEV: standard deviation" +msgstr "" + +#: ../../source/user/raster_data_model.rst:224 +msgid "" +"STATISTICS_APPROXIMATE: only present if GDAL has computed approximate " +"statistics" +msgstr "" + +#: ../../source/user/raster_data_model.rst:225 +msgid "STATISTICS_VALID_PERCENT: percentage of valid (not nodata) pixel" +msgstr "" + +#: ../../source/user/raster_data_model.rst:227 +msgid "" +"An optional offset and scale for transforming raster values into meaning " +"full values (e.g., translate height to meters)." +msgstr "" + +#: ../../source/user/raster_data_model.rst:228 +msgid "" +"An optional raster unit name. For instance, this might indicate linear " +"units for elevation data." +msgstr "" + +#: ../../source/user/raster_data_model.rst:229 +msgid "A color interpretation for the band. This is one of:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:231 +msgid "GCI_Undefined: the default, nothing is known." +msgstr "" + +#: ../../source/user/raster_data_model.rst:232 +msgid "GCI_GrayIndex: this is an independent gray-scale image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:233 +msgid "GCI_PaletteIndex: this raster acts as an index into a color table" +msgstr "" + +#: ../../source/user/raster_data_model.rst:234 +msgid "GCI_RedBand: this raster is the red portion of an RGB or RGBA image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:235 +msgid "GCI_GreenBand: this raster is the green portion of an RGB or RGBA image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:236 +msgid "GCI_BlueBand: this raster is the blue portion of an RGB or RGBA image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:237 +msgid "GCI_AlphaBand: this raster is the alpha portion of an RGBA image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:238 +msgid "GCI_HueBand: this raster is the hue of an HLS image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:239 +msgid "GCI_SaturationBand: this raster is the saturation of an HLS image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:240 +msgid "GCI_LightnessBand: this raster is the hue of an HLS image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:241 +msgid "GCI_CyanBand: this band is the cyan portion of a CMY or CMYK image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:242 +msgid "GCI_MagentaBand: this band is the magenta portion of a CMY or CMYK image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:243 +msgid "GCI_YellowBand: this band is the yellow portion of a CMY or CMYK image" +msgstr "" + +#: ../../source/user/raster_data_model.rst:244 +msgid "GCI_BlackBand: this band is the black portion of a CMYK image." +msgstr "" + +#: ../../source/user/raster_data_model.rst:246 +msgid "A color table, described in more detail later." +msgstr "" + +#: ../../source/user/raster_data_model.rst:247 +msgid "Knowledge of reduced resolution overviews (pyramids) if available." +msgstr "" + +#: ../../source/user/raster_data_model.rst:250 +msgid "Color Table" +msgstr "" + +#: ../../source/user/raster_data_model.rst:252 +msgid "" +"A color table consists of zero or more color entries described in C by " +"the following structure:" +msgstr "" + +#: ../../source/user/raster_data_model.rst:271 +msgid "" +"The color table also has a palette interpretation value " +"(GDALPaletteInterp) which is one of the following values, and indicates " +"how the c1/c2/c3/c4 values of a color entry should be interpreted." +msgstr "" + +#: ../../source/user/raster_data_model.rst:273 +msgid "GPI_Gray: Use c1 as gray scale value." +msgstr "" + +#: ../../source/user/raster_data_model.rst:274 +msgid "GPI_RGB: Use c1 as red, c2 as green, c3 as blue and c4 as alpha." +msgstr "" + +#: ../../source/user/raster_data_model.rst:275 +msgid "GPI_CMYK: Use c1 as cyan, c2 as magenta, c3 as yellow and c4 as black." +msgstr "" + +#: ../../source/user/raster_data_model.rst:276 +msgid "GPI_HLS: Use c1 as hue, c2 as lightness, and c3 as saturation." +msgstr "" + +#: ../../source/user/raster_data_model.rst:278 +msgid "" +"To associate a color with a raster pixel, the pixel value is used as a " +"subscript into the color table. That means that the colors are always " +"applied starting at zero and ascending. There is no provision for " +"indicating a pre-scaling mechanism before looking up in the color table." +msgstr "" + +#: ../../source/user/raster_data_model.rst:281 +msgid "Overviews" +msgstr "" + +#: ../../source/user/raster_data_model.rst:283 +msgid "" +"A band may have zero or more overviews. Each overview is represented as a" +" \"free standing\" :cpp:class:`GDALRasterBand`. The size (in pixels and " +"lines) of the overview will be different than the underlying raster, but " +"the geographic region covered by overviews is the same as the full " +"resolution band." +msgstr "" + +#: ../../source/user/raster_data_model.rst:285 +msgid "" +"The overviews are used to display reduced resolution overviews more " +"quickly than could be done by reading all the full resolution data and " +"downsampling." +msgstr "" + +#: ../../source/user/raster_data_model.rst:287 +msgid "" +"Bands also have a HasArbitraryOverviews property which is TRUE if the " +"raster can be read at any resolution efficiently but with no distinct " +"overview levels. This applies to some FFT encoded images, or images " +"pulled through gateways where downsampling can be done efficiently at the" +" remote point." +msgstr "" + +#: ../../source/user/raster_data_model.rst:289 +msgid "" +"How overviews are selected depends on the software logic. The " +":cpp:func:`GDALRasterBand::RasterIO` or :cpp:func:`GDALDataset::RasterIO`" +" methods document their logic." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:5 +msgid "SQL SQLite dialect" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:9 +msgid "" +"The ``SQLite`` dialect can be used as an alternate SQL dialect to the " +":ref:`ogr_sql_dialect`. This assumes that GDAL/OGR is built with support " +"for SQLite, and preferably with `Spatialite <https://www.gaia-" +"gis.it/fossil/libspatialite/index>`_ support too to benefit from spatial " +"functions." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:14 +msgid "" +"The SQLite dialect may be used with any OGR datasource, like the OGR SQL " +"dialect. The ``SQLite`` dialect can be requested with the ``SQLite`` " +"string passed as the dialect parameter of " +":cpp:func:`GDALDataset::ExecuteSQL`, or with the `-dialect` option of the" +" :ref:`ogrinfo` or :ref:`ogr2ogr` utilities." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:19 +msgid "" +"This is mainly aimed to execute SELECT statements, but, for datasources " +"that support update, INSERT/UPDATE/DELETE statements can also be run. " +"GDAL is internally using `the Virtual Table Mechanism of SQLite " +"<https://sqlite.org/vtab.html>`_ and therefore operations like ALTER " +"TABLE are not supported. For executing ALTER TABLE or DROP TABLE use " +":ref:`ogr_sql_dialect`" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:25 +msgid "" +"If the datasource is SQLite database (GeoPackage, SpatiaLite) then SQLite" +" dialect acts as native SQL dialect and Virtual Table Mechanism is not " +"used. It is possible to force GDAL to use Virtual Tables even in this " +"case by specifying \"-dialect INDIRECT_SQLITE\". This should be used only" +" when necessary, since going through the virtual table mechanism might " +"affect performance." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:31 +msgid "" +"The syntax of the SQL statements is fully the one of the SQLite SQL " +"engine. You can refer to the following pages:" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:34 +msgid "`SELECT <http://www.sqlite.org/lang_select.html>`_" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:35 +msgid "`INSERT <http://www.sqlite.org/lang_insert.html>`_" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:36 +msgid "`UPDATE <http://www.sqlite.org/lang_update.html>`_" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:37 +msgid "`DELETE <http://www.sqlite.org/lang_delete.html>`_" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:40 +msgid "SELECT statement" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:42 +msgid "" +"The SELECT statement is used to fetch layer features (analogous to table " +"rows in an RDBMS) with the result of the query represented as a temporary" +" layer of features. The layers of the datasource are analogous to tables " +"in an RDBMS and feature attributes are analogous to column values. The " +"simplest form of OGR SQLITE SELECT statement looks like this:" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:52 +msgid "" +"More complex statements can of course be used, including WHERE, JOIN, " +"USING, GROUP BY, ORDER BY, sub SELECT, ..." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:55 +msgid "" +"The table names that can be used are the layer names available in the " +"datasource on which the ExecuteSQL() method is called." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:58 +msgid "" +"Similarly to OGRSQL, it is also possible to refer to layers of other " +"datasources with the following syntax : " +"\"other_datasource_name\".\"layer_name\"." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:65 +msgid "" +"If the master datasource is SQLite database (GeoPackage, SpatiaLite) it " +"is necessary to use indirect SQLite dialect. Otherwise additional " +"datasources are never opened but tables to be used in joins are searched " +"from the master database." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:74 +msgid "" +"The column names that can be used in the result column list, in WHERE, " +"JOIN, ... clauses are the field names of the layers. Expressions, SQLite " +"functions, spatial functions, etc... can also be used." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:79 +msgid "" +"The conditions on fields expressed in WHERE clauses, or in JOINs are " +"translated, as far as possible, as attribute filters that are applied on " +"the underlying OGR layers. Joins can be very expensive operations if the " +"secondary table is not indexed on the key field being used." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:85 +msgid "LIKE operator" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:87 +msgid "" +"In SQLite, the LIKE operator is case insensitive, unless ``PRAGMA " +"case_sensitive_like = 1`` has been issued." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:90 +msgid "" +"Starting with GDAL 3.9, GDAL installs a custom LIKE comparison, such that" +" UTF-8 characters are taken into account by ``LIKE`` and ``ILIKE`` " +"operators. For ILIKE case insensitive comparisons, this is restricted to " +"the `ASCII " +"<https://en.wikipedia.org/wiki/Basic_Latin_(Unicode_block)>`__, `Latin-1 " +"Supplement <https://en.wikipedia.org/wiki/Latin-" +"1_Supplement_(Unicode_block)>`__, `Latin Extended-A " +"<https://en.wikipedia.org/wiki/Latin_Extended-A>`__, `Latin Extended-B " +"<https://en.wikipedia.org/wiki/Latin_Extended-B>`__, `Greek and Coptic " +"<https://en.wikipedia.org/wiki/Greek_and_Coptic>`__ and `Cyrillic " +"<https://en.wikipedia.org/wiki/Greek_and_Coptic>`__ Unicode categories." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:101 +msgid "Delimited identifiers" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:103 +msgid "" +"If names of layers or attributes are reserved keywords in SQL like 'FROM'" +" or they begin with a number or underscore they must be handled as " +"\"delimited identifiers\" and enclosed between double quotation marks in " +"queries. Double quotes can be used even when they are not strictly " +"needed." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:112 +msgid "" +"When SQL statements are used in the command shell and the statement " +"itself is put between double quotes, the internal double quotes must be " +"escaped with \\\\" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:122 +msgid "" +"The ``GEOMETRY`` special field represents the geometry of the feature " +"returned by OGRFeature::GetGeometryRef(). It can be explicitly specified " +"in the result column list of a SELECT, and is automatically selected if " +"the * wildcard is used." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:127 +msgid "" +"For OGR layers that have a non-empty geometry column name (generally for " +"RDBMS datasources), as returned by OGRLayer::GetGeometryColumn(), the " +"name of the geometry special field in the SQL statement will be the name " +"of the geometry column of the underlying OGR layer. If the name of the " +"geometry column in the source layer is empty, like with shapefiles etc., " +"the name to use in the SQL statement is always \"geometry\". Here we'll " +"use it case-insensitively (as all field names are in a SELECT statement):" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:138 +#: ../../source/user/sql_sqlite_dialect.rst:150 +#: ../../source/user/sql_sqlite_dialect.rst:216 +#: ../../source/user/sql_sqlite_dialect.rst:343 +#: ../../source/user/sql_sqlite_dialect.rst:354 +msgid "returns:" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:163 +msgid "" +"The feature id is a special property of a feature and not treated as an " +"attribute of the feature. In some cases it is convenient to be able to " +"utilize the feature id in queries and result sets as a regular field. To" +" do so use the name ``rowid``." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:168 +msgid "" +"Starting with GDAL 3.8, if the layer has a named FID column " +"(:cpp:func:`OGRLayer::GetFIDColumn` != \"\"), this name may also be used." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:186 +msgid "It is of course possible to rename it:" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:193 +msgid "OGR_STYLE special field" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:205 +msgid "Spatialite SQL functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:207 +msgid "" +"When GDAL/OGR is build with support for the `Spatialite <https://www" +".gaia-gis.it/fossil/libspatialite/index>`_ library, a lot of `extra SQL " +"functions <http://www.gaia-gis.it/gaia-sins/spatialite-sql-" +"latest.html>`_, in particular spatial functions, can be used in results " +"column fields, WHERE clauses, etc...." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:232 +msgid "" +"Note that due to the loose typing mechanism of SQLite, if a geometry " +"expression returns a NULL value for the first row, this will generally " +"cause OGR not to recognize the column as a geometry column. It might be " +"then useful to sort the results by making sure that non-null geometries " +"are returned first:" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:242 +msgid "OGR datasource SQL functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:244 +msgid "" +"The ``ogr_datasource_load_layers(datasource_name[, update_mode[, " +"prefix]])`` function can be used to automatically load all the layers of " +"a datasource as :ref:`VirtualOGR tables <vector.sqlite>`." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:260 +msgid "OGR layer SQL functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:262 +msgid "" +"The following SQL functions are available and operate on a layer name : " +"``ogr_layer_Extent()``, ``ogr_layer_SRID()``, " +"``ogr_layer_GeometryType()`` and ``ogr_layer_FeatureCount()``" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:280 +msgid "OGR compression functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:282 +msgid "" +"``ogr_deflate(text_or_blob[, compression_level])`` returns a binary blob " +"compressed with the ZLib deflate algorithm. See " +":cpp:func:`CPLZLibDeflate`" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:285 +msgid "" +"``ogr_inflate(compressed_blob)`` returns the decompressed binary blob, " +"from a blob compressed with the ZLib deflate algorithm. If the " +"decompressed binary is a string, use CAST(ogr_inflate(compressed_blob) AS" +" VARCHAR). See CPLZLibInflate()." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:291 +msgid "Other functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:293 +msgid "" +"The ``hstore_get_value()`` function can be used to extract a value " +"associate to a key from a HSTORE string, formatted like " +"\"key=>value,other_key=>other_value,...\"" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:303 +msgid "Raster related functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:305 +msgid "" +"The ``gdal_get_pixel_value()`` function (added in GDAL 3.7) can be used " +"to extract the value of a pixel in a GDAL dataset. It requires the " +"configuration option OGR_SQLITE_ALLOW_EXTERNAL_ACCESS to be set to YES " +"(for security reasons)." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:309 +msgid "It takes 5 arguments:" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:311 +msgid "a string with the dataset name" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:312 +msgid "a band number (numbering starting at 1)" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:313 +msgid "" +"a string being \"georef\" to indicate that subsequent values will be " +"georeferenced coordinates, or \"pixel\" to indicate that subsequent " +"values will be in column, line pixel space" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:316 +msgid "georeferenced X value or column number" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:317 +msgid "georeferenced Y value or line number" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:326 +msgid "OGR geocoding functions" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:328 +msgid "" +"The following SQL functions are available : ``ogr_geocode(...)`` and " +"``ogr_geocode_reverse(...)``." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:330 +msgid "" +"``ogr_geocode(name_to_geocode [, field_to_return [, option1 [, option2, " +"...]]])`` where name_to_geocode is a literal or a column name that must " +"be geocoded. field_to_return if specified can be \"geometry\" for the " +"geometry (default), or a field name of the layer returned by " +":cpp:func:`OGRGeocode`. The special field \"raw\" can also be used to " +"return the raw response (XML string) of the geocoding service. option1, " +"option2, etc.. must be of the key=value format, and are options " +"understood by :cpp:func:`OGRGeocodeCreateSession` or OGRGeocode()." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:337 +msgid "" +"This function internally uses the OGRGeocode() API. Refer to it for more " +"details." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:389 +msgid "" +"``ogr_geocode_reverse(longitude, latitude, field_to_return [, option1 [, " +"option2, ...]])`` where longitude, latitude is the coordinate to query. " +"field_to_return must be a field name of the layer returned by " +"OGRGeocodeReverse() (for example 'display_name'). The special field " +"\"raw\" can also be used to return the raw response (XML string) of the " +"geocoding service. option1, option2, etc.. must be of the key=value " +"format, and are options understood by OGRGeocodeCreateSession() or " +"OGRGeocodeReverse()." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:396 +msgid "" +"``ogr_geocode_reverse(geometry, field_to_return [, option1 [, option2, " +"...]])`` is also accepted as an alternate syntax where geometry is a " +"(Spatialite) point geometry." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:399 +msgid "" +"This function internally uses the :cpp:func:`OGRGeocodeReverse` API. " +"Refer to it for more details." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:402 +msgid "Spatialite spatial index" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:404 +msgid "" +"Spatialite spatial index mechanism can be triggered by making sure a " +"spatial index virtual table is mentioned in the SQL (of the form " +"idx_layername_geometrycolumn), or by using the more recent SpatialIndex " +"from the VirtualSpatialIndex extension. In which case, a in-memory RTree " +"will be built to be used to speed up the spatial queries." +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:409 +msgid "" +"For example, a spatial intersection between 2 layers, by using a spatial " +"index on one of the layers to limit the number of actual geometry " +"intersection computations :" +msgstr "" + +#: ../../source/user/sql_sqlite_dialect.rst:421 +msgid "or more elegantly :" +msgstr "" + +#: ../../source/user/vector_data_model.rst:5 +msgid "Vector Data Model" +msgstr "" + +#: ../../source/user/vector_data_model.rst:7 +msgid "" +"This page documents the classes used to handle vector data. Many data " +"types and method names are based on the OGC Simple Features data model, " +"so it may be helpful to review the `specifications published by OGC " +"<https://www.ogc.org/standard/sfa/>`__. For historical reasons, GDAL uses" +" the \"OGR\" prefix to denote types and functions that apply only to " +"vector data." +msgstr "" + +#: ../../source/user/vector_data_model.rst:11 +msgid "Class Overview" +msgstr "" + +#: ../../source/user/vector_data_model.rst:13 +msgid "The following classes form the core of the vector data model:" +msgstr "" + +#: ../../source/user/vector_data_model.rst:15 +msgid "" +"Geometry (:ref:`ogr_geometry.h <ogrgeometry_cpp>`): The geometry classes " +"(:cpp:class:`OGRGeometry`, etc) encapsulate the OGC vector data types. " +"They provide some geometry operations and translation to/from well known " +"binary and text format. A geometry includes a spatial reference system " +"(projection)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:16 +msgid "" +"Spatial Reference (:ref:`ogr_spatialref.h <ogrspatialref>`): An " +":cpp:class:`OGRSpatialReference` encapsulates the definition of a " +"projection and datum." +msgstr "" + +#: ../../source/user/vector_data_model.rst:17 +msgid "" +"Feature (:ref:`ogr_feature.h <ogrfeature_cpp>`): The " +":cpp:class:`OGRFeature` encapsulates the definition of a whole feature, " +"that is a set of geometries and attributes relating to a single entity." +msgstr "" + +#: ../../source/user/vector_data_model.rst:18 +msgid "" +"Feature Class Definition (:ref:`ogr_feature.h <ogrfeature_cpp>`): The " +":cpp:class:`OGRFeatureDefn` class captures the schema (set of field " +"definitions) for a group of related features (normally a whole layer)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:19 +msgid "" +"Layer (:ref:`ogrsf_frmts.h <ogrlayer_cpp>`): :cpp:class:`OGRLayer` is an " +"abstract class representing a layer of features in a " +":cpp:class:`GDALDataset`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:20 +msgid "" +"Dataset (:ref:`gdal_priv.h <gdaldataset_cpp>`): A " +":cpp:class:`GDALDataset` is an abstract base class representing a file or" +" database containing one or more :cpp:class:`OGRLayer` objects." +msgstr "" + +#: ../../source/user/vector_data_model.rst:21 +msgid "" +"Drivers (:ref:`gdal_priv.h <gdaldriver_cpp>`): A :cpp:class:`GDALDriver` " +"represents a translator for a specific format, capable of opening and " +"possibly writing :cpp:class:`GDALDataset` objects. All available drivers " +"are managed by the :cpp:class:`GDALDriverManager`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:24 +msgid "Geometry" +msgstr "" + +#: ../../source/user/vector_data_model.rst:26 +msgid "" +"Individual geometry classes are used to represent the different types of " +"vector geometry. All the geometry classes derive from " +":cpp:class:`OGRGeometry` which defines the common functionality of all " +"geometries. Geometry types include :cpp:class:`OGRPoint`, " +":cpp:class:`OGRLineString`, :cpp:class:`OGRPolygon`, " +":cpp:class:`OGRGeometryCollection`, :cpp:class:`OGRMultiPoint`, " +":cpp:class:`OGRMultiLineString`, :cpp:class:`OGRMultiPolygon`, and " +":cpp:class:`OGRPolyhedralSurface`. The special case of a triangular " +"polygon can be represented as a :cpp:class:`OGRTriangle`, a non-" +"overlapping collection of which can be represented by an " +":cpp:class:`OGRTriangulatedSurface`. An additional set of types is used " +"to store non-linear geometries: :cpp:class:`OGRCircularString`, " +":cpp:class:`OGRCompoundCurve`, :cpp:class:`OGRCurvePolygon`, " +":cpp:class:`OGRMultiCurve` and :cpp:class:`OGRMultiSurface`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:30 +msgid "" +"Any of the above geometry classes can store coordinates in two (XY), " +"three (XYZ or XYM), or four (XYZM) dimensions." +msgstr "" + +#: ../../source/user/vector_data_model.rst:32 +msgid "" +"Additional intermediate classes contain functionality that is used by " +"multiple geometry types. These include :cpp:class:`OGRCurve` (base class " +"for :cpp:class:`OGRLineString`) and :cpp:class:`OGRSurface` (base class " +"for :cpp:class:`OGRPolygon`). Some intermediate interfaces modeled in the" +" simple features abstract model and SFCOM are not modeled in OGR at this " +"time. In most cases the methods are aggregated into other classes." +msgstr "" + +#: ../../source/user/vector_data_model.rst:-1 +msgid "Diagram of OGRGeometry and subclasses" +msgstr "" + +#: ../../source/user/vector_data_model.rst:37 +msgid "" +"The :cpp:class:`OGRGeometryFactory` is used to convert well known text " +"(WKT) and well known binary (WKB) format data into the appropriate " +":cpp:class:`OGRGeometry` subclass. These are predefined ASCII and binary " +"formats for representing all the types of simple features geometries." +msgstr "" + +#: ../../source/user/vector_data_model.rst:39 +msgid "" +"The :cpp:class:`OGRGeometry` includes a reference to an " +":cpp:class:`OGRSpatialReference` object, defining the spatial reference " +"system of that geometry. This is normally a reference to a shared spatial" +" reference object with reference counting for each of the " +":cpp:class:`OGRGeometry` objects using it." +msgstr "" + +#: ../../source/user/vector_data_model.rst:41 +msgid "" +"While it is theoretically possible to derive other or more specific " +"geometry classes from the existing :cpp:class:`OGRGeometry` classes, this" +" isn't an aspect that has been well thought out. In particular, it would " +"be possible to create specialized classes using the " +":cpp:class:`OGRGeometryFactory` without modifying it." +msgstr "" + +#: ../../source/user/vector_data_model.rst:44 +msgid "Compatibility issues with non-linear geometries" +msgstr "" + +#: ../../source/user/vector_data_model.rst:46 +msgid "" +"Generic mechanisms have been introduced so that creating or modifying a " +"feature with a non-linear geometry in a layer of a driver that does not " +"support it will transform that geometry in the closest matching linear " +"geometry. This linearization can be controlled using " +":ref:`configoptions_vector`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:48 +msgid "" +"On the other side, when retrieving data from the OGR C API, the " +":cpp:func:`OGRSetNonLinearGeometriesEnabledFlag` function can be used, so" +" that geometries and layer geometry type returned are also converted to " +"their linear approximation if necessary." +msgstr "" + +#: ../../source/user/vector_data_model.rst:51 +msgid "Spatial Reference" +msgstr "" + +#: ../../source/user/vector_data_model.rst:53 +msgid "" +"The :cpp:class:`OGRSpatialReference` class is intended to store an " +"OpenGIS Spatial Reference System definition. Currently local, geographic " +"and projected coordinate systems are supported. Vertical coordinate " +"systems, geocentric coordinate systems, and compound (horizontal + " +"vertical) coordinate systems are as well supported in recent GDAL " +"versions." +msgstr "" + +#: ../../source/user/vector_data_model.rst:55 +msgid "" +"The spatial coordinate system data model is inherited from the OpenGIS " +"Well Known Text format. A simple form of this is defined in the Simple " +"Features specifications. A more sophisticated form is found in the " +"Coordinate Transformation specification. The " +":cpp:class:`OGRSpatialReference` is built on the features of the " +"Coordinate Transformation specification but is intended to be compatible " +"with the earlier simple features form." +msgstr "" + +#: ../../source/user/vector_data_model.rst:57 +msgid "" +"There is also an associated :cpp:class:`OGRCoordinateTransformation` " +"class that encapsulates use of |PROJ| for converting between different " +"coordinate systems." +msgstr "" + +#: ../../source/user/vector_data_model.rst:60 +msgid "Feature / Feature Definition" +msgstr "" + +#: ../../source/user/vector_data_model.rst:62 +msgid "" +"The :cpp:class:`OGRGeometry` captures the geometry of a vector feature. " +"The :cpp:class:`OGRFeature` contains geometry, and adds feature " +"attributes, feature id, and a feature class identifier. It may also " +"contain styling information. Several geometries can be associated with an" +" :cpp:class:`OGRFeature`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:64 +msgid "" +"The set of attributes (:cpp:class:`OGRFieldDefn`), their types, names and" +" so forth is represented via the :cpp:class:`OGRFeatureDefn` class. One " +":cpp:class:`OGRFeatureDefn` normally exists for a layer of features. The " +"same definition is shared in a reference counted manner by the feature of" +" that type (or feature class)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:66 +msgid "" +"The feature id (FID) of a feature is intended to be a unique identifier " +"for the feature within the layer it is a member of. Freestanding " +"features, or features not yet written to a layer may have a null " +"(OGRNullFID) feature id. The feature ids are modeled in OGR as a 64-bit " +"integer; however, this is not sufficiently expressive to model the " +"natural feature ids in some formats. For instance, the GML feature id is " +"a string." +msgstr "" + +#: ../../source/user/vector_data_model.rst:68 +msgid "" +"The :cpp:class:`OGRFeatureDefn` also contains an indicator of the types " +"of geometry allowed for that feature class (returned as an " +":cpp:enum:`OGRwkbGeometryType` from " +":cpp:func:`OGRFeatureDefn::GetGeomType`). If this is " +":cpp:enumerator:`OGRwkbGeometryType::wkbUnknown` then any type of " +"geometry is allowed. This implies that features in a given layer can " +"potentially be of different geometry types though they will always share " +"a common attribute schema." +msgstr "" + +#: ../../source/user/vector_data_model.rst:70 +msgid "" +"Several geometry fields (:cpp:class:`OGRGeomFieldDefn`) can be associated" +" with an :cpp:class:`OGRFeatureDefn`. Each geometry field has its own " +"indicator of geometry type allowed, returned by " +":cpp:func:`OGRGeomFieldDefn::GetType`, and its spatial reference system, " +"returned by :cpp:func:`OGRGeomFieldDefn::GetSpatialRef`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:72 +msgid "" +"The :cpp:class:`OGRFeatureDefn` also contains a feature class name " +"(normally used as a layer name)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:75 +msgid "Field Definitions" +msgstr "" + +#: ../../source/user/vector_data_model.rst:77 +msgid "" +"The behavior of each field in a feature class is defined by a shared " +":cpp:class:`OGRFieldDefn`. The :cpp:class:`OGRFieldDefn` specifies the " +"field type from the values of :cpp:enum:`OGRFieldType`. Values stored in " +"this field may be further restricted according to a " +":cpp:enum:`OGRFieldSubType`. For example, a field may have a type of " +":cpp:enumerator:`OGRFieldType::OFTInteger` with a subtype of " +":cpp:enumerator:`OGRFieldSubType::OFSTBoolean`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:82 +msgid "" +"The :cpp:class:`OGRFieldDefn` can also track whether a field is allowed " +"to be null (:cpp:func:`OGRFieldDefn::IsNullable`), whether its value must" +" be unique (:cpp:func:`OGRFieldDefn::IsUnique`), and formatting " +"information such as the number of decimal digits, width, and " +"justification. It may also define a default value in case one is not " +"manually specified." +msgstr "" + +#: ../../source/user/vector_data_model.rst:85 +msgid "Field Domains" +msgstr "" + +#: ../../source/user/vector_data_model.rst:87 +msgid "" +"Some formats support the use of field domains that describe the values " +"that can be stored in a given attribute field. An " +":cpp:class:`OGRFieldDefn` may reference a single " +":cpp:class:`OGRFieldDomain` that is associated with a " +":cpp:class:`GDALDataset`. Programs using GDAL may use the " +":cpp:class:`OGRFieldDomain` to appropriately constrain user input. GDAL " +"does not perform validation itself and will allow the storage of values " +"that violate a field's associated :cpp:class:`OGRFieldDomain`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:90 +msgid "Available types of :cpp:class:`OGRFieldDomain` include:" +msgstr "" + +#: ../../source/user/vector_data_model.rst:92 +msgid "" +":cpp:class:`OGRCodedFieldDomain`, which constrains values those present " +"in a specified enumeration" +msgstr "" + +#: ../../source/user/vector_data_model.rst:93 +msgid "" +":cpp:class:`OGRRangeFieldDomain`, which constrains values to a specified " +"range" +msgstr "" + +#: ../../source/user/vector_data_model.rst:94 +msgid "" +":cpp:class:`OGRGlobFieldDomain`, which constrains values to those " +"matching a specified pattern" +msgstr "" + +#: ../../source/user/vector_data_model.rst:96 +msgid "" +"Additionally, an :cpp:class:`OGRFieldDomain` may define policies " +"describing the values that should be assigned to domain-controlled fields" +" when features are split or merged." +msgstr "" + +#: ../../source/user/vector_data_model.rst:99 +msgid "Layer" +msgstr "" + +#: ../../source/user/vector_data_model.rst:101 +msgid "" +"An :cpp:class:`OGRLayer` represents a layer of features within a data " +"source. All features in an :cpp:class:`OGRLayer` share a common schema " +"and are of the same :cpp:class:`OGRFeatureDefn`. An :cpp:class:`OGRLayer`" +" class also contains methods for reading features from the data source. " +"The :cpp:class:`OGRLayer` can be thought of as a gateway for reading and " +"writing features from an underlying data source such as a file on disk, " +"or the result of a database query." +msgstr "" + +#: ../../source/user/vector_data_model.rst:103 +msgid "" +"The :cpp:class:`OGRLayer` includes methods for sequential and random " +"reading and writing. Read access (via the " +":cpp:func:`OGRLayer::GetNextFeature` method) normally reads all features," +" one at a time sequentially; however, it can be limited to return " +"features intersecting a particular geographic region by installing a " +"spatial filter on the :cpp:class:`OGRLayer` (via the " +":cpp:func:`OGRLayer::SetSpatialFilter` method). A filter on attributes " +"can only be set with the :cpp:func:`OGRLayer::SetAttributeFilter` method." +" By default, all available attributes and geometries are read but this " +"can be controlled by flagging fields as ignored " +"(:cpp:func:`OGRLayer::SetIgnoredFields`)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:105 +msgid "" +"Starting with GDAL 3.6, as an alternative to getting features through " +"``GetNextFeature``, it is possible to retrieve them by batches, with a " +"column-oriented memory layout, using the " +":cpp:func:`OGRLayer::GetArrowStream` method (cf " +":ref:`vector_api_tut_arrow_stream`)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:107 +msgid "" +"An :cpp:class:`OGRLayer` may also store an :cpp:class:`OGRStyleTable` " +"that provides a set of styles that may be used by features in the layer. " +"More information on GDAL's handling of feature styles can be found in the" +" :ref:`ogr_feature_style`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:109 +msgid "" +"One flaw in the current OGR architecture is that the spatial and " +"attribute filters are set directly on the :cpp:class:`OGRLayer` which is " +"intended to be the only representative of a given layer in a data source." +" This means it isn't possible to have multiple read operations active at " +"one time with different spatial filters on each." +msgstr "" + +#: ../../source/user/vector_data_model.rst:114 +msgid "" +"Another question that might arise is why the :cpp:class:`OGRLayer` and " +":cpp:class:`OGRFeatureDefn` classes are distinct. An " +":cpp:class:`OGRLayer` always has a one-to-one relationship to an " +":cpp:class:`OGRFeatureDefn`, so why not amalgamate the classes? There are" +" two reasons:" +msgstr "" + +#: ../../source/user/vector_data_model.rst:116 +msgid "" +"As defined now :cpp:class:`OGRFeature` and :cpp:class:`OGRFeatureDefn` " +"don't depend on :cpp:class:`OGRLayer`, so they can exist independently in" +" memory without regard to a particular layer in a data store." +msgstr "" + +#: ../../source/user/vector_data_model.rst:117 +msgid "" +"The SF CORBA model does not have a concept of a layer with a single fixed" +" schema the way that the SFCOM and SFSQL models do. The fact that " +"features belong to a feature collection that is potentially not directly " +"related to their current feature grouping may be important to " +"implementing SFCORBA support using OGR." +msgstr "" + +#: ../../source/user/vector_data_model.rst:119 +msgid "" +"The :cpp:class:`OGRLayer` class is an abstract base class. An " +"implementation is expected to be subclassed for each file format driver " +"implemented. OGRLayers are normally owned directly by their " +":cpp:class:`GDALDataset`, and aren't instantiated or destroyed directly." +msgstr "" + +#: ../../source/user/vector_data_model.rst:125 +msgid "" +"A :cpp:class:`GDALDataset` represents a set of :cpp:class:`OGRLayer` " +"objects. This usually represents a single file, set of files, database or" +" gateway. A :cpp:class:`GDALDataset` has a list of :cpp:class:`OGRLayer` " +"which it owns but can return references to." +msgstr "" + +#: ../../source/user/vector_data_model.rst:127 +msgid "" +":cpp:class:`GDALDataset` is an abstract base class. An implementation is " +"expected to be subclassed for each file format driver implemented. " +":cpp:class:`GDALDataset` objects are not normally instantiated directly " +"but rather with the assistance of an :cpp:class:`GDALDriver`. Deleting an" +" :cpp:class:`GDALDataset` closes access to the underlying persistent data" +" source, but does not normally result in deletion of that file." +msgstr "" + +#: ../../source/user/vector_data_model.rst:129 +msgid "" +"A :cpp:class:`GDALDataset` has a name (usually a filename or database " +"connection string) that can be used to reopen the data source with a " +":cpp:class:`GDALDriver`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:131 +msgid "" +"The :cpp:class:`GDALDataset` also has support for executing a datasource " +"specific command, normally a form of SQL. This is accomplished via the " +":cpp:func:`GDALDataset::ExecuteSQL` method. While some datasources (such " +"as PostGIS and Oracle) pass the SQL through to an underlying database, " +"OGR also includes support for evaluating a subset of the SQL SELECT " +"statement against any datasource (see :ref:`ogr_sql_sqlite_dialect`.)" +msgstr "" + +#: ../../source/user/vector_data_model.rst:133 +msgid "" +"When using some drivers, the :cpp:class:`GDALDataset` also offers a " +"mechanism for to start, commit, and rollback transactions when " +"interacting with the underlying data store." +msgstr "" + +#: ../../source/user/vector_data_model.rst:136 +msgid "" +"A :cpp:class:`GDALDataset` may also be aware of relationships between " +"layers (e.g., a foreign key relationship between database tables). " +"Information about these relationships is stored in a " +":cpp:class:`GDALRelationshp`." +msgstr "" + +#: ../../source/user/vector_data_model.rst:140 +msgid "" +"Earlier versions of GDAL represented vector datasets using the " +":cpp:class:`OGRDataSource` class. This class has been maintained for " +"backwards compatibility but is functionally equivalent to a " +":cpp:class:`GDALDataset` for vector data." +msgstr "" + +#: ../../source/user/vector_data_model.rst:143 +msgid "Drivers" +msgstr "" + +#: ../../source/user/vector_data_model.rst:145 +msgid "" +"A :cpp:class:`GDALDriver` object is instantiated for each file format " +"supported. The :cpp:class:`GDALDriver` objects are registered with the " +":cpp:class:`GDALDriverManager`, a singleton class that is normally used " +"to open new datasets." +msgstr "" + +#: ../../source/user/vector_data_model.rst:147 +msgid "" +"It is intended that a new :cpp:class:`GDALDriver` object is instantiated " +"and define function pointers for operations like Identify(), Open() for " +"each file format to be supported (along with a file format specific " +":cpp:class:`GDALDataset`, and :cpp:class:`OGRLayer` classes)." +msgstr "" + +#: ../../source/user/vector_data_model.rst:149 +msgid "" +"On application startup registration functions are normally called for " +"each desired file format. These functions instantiate the appropriate " +":cpp:class:`GDALDriver` objects, and register them with the " +":cpp:class:`GDALDriverManager`. When a dataset is to be opened, the " +"driver manager will normally try each :cpp:class:`GDALDataset` in turn, " +"until one succeeds, returning a :cpp:class:`GDALDataset` object." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:5 +msgid "" +"GDAL Virtual File Systems (compressed, network hosted, etc...): /vsimem, " +"/vsizip, /vsitar, /vsicurl, ..." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:8 +msgid "Introduction" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:10 +msgid "" +"GDAL can access files located on \"standard\" file systems, i.e. in the /" +" hierarchy on Unix-like systems or in C:\\, D:\\, etc... drives on " +"Windows. But most GDAL raster and vector drivers use a GDAL-specific " +"abstraction to access files. This makes it possible to access less " +"standard types of files, such as in-memory files, compressed files (.zip," +" .gz, .tar, .tar.gz archives), encrypted files, standard input and output" +" (STDIN, STDOUT), files stored on network (either publicly accessible, or" +" in private buckets of commercial cloud storage services), etc." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:12 +msgid "" +"Each special file system has a prefix, and the general syntax to name a " +"file is /vsiPREFIX/..." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:21 +msgid "Chaining" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:23 +msgid "It is possible to chain multiple file system handlers." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:35 +msgid "" +"(Note is also OK to say /vsizip/vsicurl/... with a single slash. (But " +"when writing documentation please still use two.))" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:38 +msgid "Drivers supporting virtual file systems" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:40 +msgid "" +"Virtual file systems can only be used with GDAL or OGR drivers supporting" +" the \"large file API\", which is now the vast majority of file based " +"drivers. The full list of these formats can be obtained by looking at the" +" driver marked with 'v' when running either ``gdalinfo --formats`` or " +"``ogrinfo --formats``." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:42 +msgid "A notable exception is the HDF4 driver." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:47 +msgid "/vsizip/ (.zip archives)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:50 +msgid "Read capabilities" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:52 +msgid "" +"/vsizip/ is a file handler that allows reading ZIP archives on-the-fly " +"without decompressing them beforehand." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:54 +msgid "" +"To point to a file inside a zip file, the filename must be of the form " +":file:`/vsizip/path/to/the/file.zip/path/inside/the/zip/file`, where " +":file:`path/to/the/file.zip` is relative or absolute and " +":file:`path/inside/the/zip/file` is the relative path to the file inside " +"the archive." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:56 +msgid "" +"To use the .zip as a directory, you can use " +":file:`/vsizip/path/to/the/file.zip` or " +":file:`/vsizip/path/to/the/file.zip/subdir`. Directory listing is " +"available with :cpp:func:`VSIReadDir`. A :cpp:func:`VSIStatL` " +"(\"/vsizip/...\") call will return the uncompressed size of the file. " +"Directories inside the ZIP file can be distinguished from regular files " +"with the VSI_ISDIR(stat.st_mode) macro as for regular file systems. " +"Getting directory listing and file statistics are fast operations." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:58 +msgid "" +"Note: in the particular case where the .zip file contains a single file " +"located at its root, just mentioning :file:`/vsizip/path/to/the/file.zip`" +" will work." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:60 +msgid "The following configuration options are specific to the /zip/ handler:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:87 +msgid "" +".kmz, .ods and .xlsx extensions are also detected as valid extensions for" +" zip-compatible archives." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:89 +msgid "" +"Starting with GDAL 2.2, an alternate syntax is available so as to enable " +"chaining and not being dependent on .zip extension, e.g.: " +"``/vsizip/{/path/to/the/archive}/path/inside/the/zip/file``. Note that " +":file:`/path/to/the/archive` may also itself use this alternate syntax." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:92 +msgid "Write capabilities" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:94 +msgid "" +"Write capabilities are also available. They allow creating a new zip file" +" and adding new files to an already existing (or just created) zip file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:96 +msgid "Creation of a new zip file:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:106 +msgid "Addition of a new file to an existing zip:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:114 +msgid "" +"Starting with GDAL 2.4, the :config:`GDAL_NUM_THREADS` configuration " +"option can be set to an integer or ``ALL_CPUS`` to enable multi-threaded " +"compression of a single file. This is similar to the pigz utility in " +"independent mode. By default the input stream is split into 1 MB chunks " +"(the chunk size can be tuned with the " +":config:`CPL_VSIL_DEFLATE_CHUNK_SIZE` configuration option, with values " +"like \"x K\" or \"x M\"), and each chunk is independently compressed (and" +" terminated by a nine byte marker 0x00 0x00 0xFF 0xFF 0x00 0x00 0x00 0xFF" +" 0xFF, signaling a full flush of the stream and dictionary, enabling " +"potential independent decoding of each chunk). This slightly reduces the " +"compression rate, so very small chunk sizes should be avoided. Starting " +"with GDAL 3.7, this technique is reused to generate .zip files following " +":ref:`sozip_intro`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:117 +msgid "" +"Read and write operations cannot be interleaved. The new zip must be " +"closed before being re-opened in read mode." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:122 +msgid "SOZip (Seek-Optimized ZIP)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:124 +msgid "" +"GDAL (>= 3.7) has full read and write support for .zip files following " +"the `SOZip (Seek-Optimized ZIP) <https://sozip.org>`__ profile." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:127 +msgid "" +"The ``/vsizip/`` virtual file system uses the SOZip index to perform fast" +" random access within a compressed SOZip-enabled file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:130 +msgid "" +"The :ref:`vector.shapefile` and :ref:`vector.gpkg` drivers can directly " +"generate SOZip-enabled .shz/.shp.zip or .gpkg.zip files." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:133 +msgid "" +"The :cpp:func:`CPLAddFileInZip` C function, which can compress a file and" +" add it to an new or existing ZIP file, enables the SOZip optimization " +"when relevant (ie when a file to be compressed is larger than 1 MB). " +"SOZip optimization can be forced by setting the " +":config:`CPL_SOZIP_ENABLED` configuration option to YES. Or totally " +"disabled by setting it to NO." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:139 +msgid "" +"The :cpp:func:`VSIGetFileMetadata` method can be called on a filename of " +"the form :file:`/vsizip/path/to/the/file.zip/path/inside/the/zip/file` " +"and with domain = \"ZIP\" to get information if a SOZip index is " +"available for that file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:143 +msgid "" +"The :ref:`sozip` new command line utility can be used to create a seek-" +"optimized ZIP file, to append files to an existing ZIP file, list the " +"contents of a ZIP file and display the SOZip optimization status or " +"validate a SOZip file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:151 +msgid "/vsigzip/ (gzipped file)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:153 +msgid "" +"/vsigzip/ is a file handler that allows on-the-fly reading of GZip (.gz) " +"files without decompressing them in advance." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:155 +msgid "" +"To view a gzipped file as uncompressed by GDAL, you must use the " +":file:`/vsigzip/path/to/the/file.gz` syntax, where " +":file:`path/to/the/file.gz` is relative or absolute." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:157 +msgid "The following configuration options are specific to the /vsigzip/ handler:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:176 +msgid "" +":cpp:func:`VSIStatL` will return the uncompressed file size, but this is " +"potentially a slow operation on large files, since it requires " +"uncompressing the whole file. Seeking to the end of the file, or at " +"random locations, is similarly slow. To speed up that process, " +"\"snapshots\" are internally created in memory so as to be able being " +"able to seek to part of the files already decompressed in a faster way. " +"This mechanism of snapshots also apply to /vsizip/ files." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:178 +msgid "" +"Write capabilities are also available, but read and write operations " +"cannot be interleaved." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:180 +msgid "" +"Starting with GDAL 2.4, the :config:`GDAL_NUM_THREADS` configuration " +"option can be set to an integer or ``ALL_CPUS`` to enable multi-threaded " +"compression of a single file. This is similar to the pigz utility in " +"independent mode. By default the input stream is split into 1 MB chunks " +"(the chunk size can be tuned with the " +":config:`CPL_VSIL_DEFLATE_CHUNK_SIZE` configuration option, with values " +"like \"x K\" or \"x M\"), and each chunk is independently compressed (and" +" terminated by a nine byte marker 0x00 0x00 0xFF 0xFF 0x00 0x00 0x00 0xFF" +" 0xFF, signaling a full flush of the stream and dictionary, enabling " +"potential independent decoding of each chunk). This slightly reduces the " +"compression rate, so very small chunk sizes should be avoided." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:185 +msgid "/vsitar/ (.tar, .tgz archives)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:187 +msgid "" +"/vsitar/ is a file handler that allows on-the-fly reading in regular " +"uncompressed .tar or compressed .tgz or .tar.gz archives, without " +"decompressing them in advance." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:189 +msgid "" +"To point to a file inside a .tar, .tgz .tar.gz file, the filename must be" +" of the form " +":file:`/vsitar/path/to/the/file.tar/path/inside/the/tar/file`, where " +":file:`path/to/the/file.tar` is relative or absolute and " +":file:`path/inside/the/tar/file` is the relative path to the file inside " +"the archive." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:191 +msgid "" +"To use the .tar as a directory, you can use " +":file:`/vsizip/path/to/the/file.tar` or " +":file:`/vsitar/path/to/the/file.tar/subdir`. Directory listing is " +"available with :cpp:func:`VSIReadDir`. A :cpp:func:`VSIStatL` " +"(\"/vsitar/...\") call will return the uncompressed size of the file. " +"Directories inside the TAR file can be distinguished from regular files " +"with the VSI_ISDIR(stat.st_mode) macro as for regular file systems. " +"Getting directory listing and file statistics are fast operations." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:193 +msgid "" +"Note: in the particular case where the .tar file contains a single file " +"located at its root, just mentioning :file:`/vsitar/path/to/the/file.tar`" +" will work." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:203 +msgid "" +"Starting with GDAL 2.2, an alternate syntax is available so as to enable " +"chaining and not being dependent on .tar extension, e.g.: " +":file:`/vsitar/{/path/to/the/archive}/path/inside/the/tar/file`. Note " +"that :file:`/path/to/the/archive` may also itself use this alternate " +"syntax." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:208 +msgid "/vsi7z/ (.7z archives)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:212 +msgid "" +"/vsi7z/ is a file handler that allows reading `7z " +"<https://en.wikipedia.org/wiki/7z>`__ archives on-the-fly without " +"decompressing them beforehand. This file system is read-only. Directory " +"listing and :cpp:func:`VSIStatL` are available, similarly to above " +"mentioned file systems." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:217 +#: ../../source/user/virtual_file_systems.rst:249 +msgid "" +"It requires GDAL to be built against `libarchive " +"<https://libarchive.org/>`__ (and libarchive having LZMA support to be of" +" practical use)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:220 +msgid "" +"To point to a file inside a 7z file, the filename must be of the form " +":file:`/vsi7z/path/to/the/file.7z/path/inside/the/7z/file`, where " +":file:`path/to/the/file.7z` is relative or absolute and " +":file:`path/inside/the/7z/file` is the relative path to the file inside " +"the archive.`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:225 +msgid "" +"Default extensions recognized by this virtual file system are: ``7z``, " +"``lpk`` (Esri ArcGIS Layer Package), ``lpkx``, ``mpk`` (Esri ArcGIS Map " +"Package), ``mpkx`` and ``ppkx`` (Esri ArcGIS Pro Project Package)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:229 +msgid "" +"An alternate syntax is available so as to enable chaining and not being " +"dependent on those extensions, e.g.: " +":file:`/vsi7z/{/path/to/the/archive}/path/inside/the/archive`. Note that " +":file:`/path/to/the/archive` may also itself use this alternate syntax." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:233 +#: ../../source/user/virtual_file_systems.rst:263 +msgid "" +"Note that random seeking within a large compressed file will be " +"inefficient when backward seeking is needed (decompression will be " +"restarted from the start of the file). Performance will be the best in " +"sequential reading." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:240 +msgid "/vsirar/ (.rar archives)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:244 +msgid "" +"/vsirar/ is a file handler that allows reading `RAR " +"<https://en.wikipedia.org/wiki/RAR_(file_format)>`__ archives on-the-fly " +"without decompressing them beforehand. This file system is read-only. " +"Directory listing and :cpp:func:`VSIStatL` are available, similarly to " +"above mentioned file systems." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:252 +msgid "" +"To point to a file inside a RAR file, the filename must be of the form " +":file:`/vsirar/path/to/the/file.rar/path/inside/the/rar/file`, where " +":file:`path/to/the/file.rar` is relative or absolute and " +":file:`path/inside/the/rar/file` is the relative path to the file inside " +"the archive.`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:257 +msgid "The default extension recognized by this virtual file system is: ``rar``" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:259 +msgid "" +"An alternate syntax is available so as to enable chaining and not being " +"dependent on those extensions, e.g.: " +":file:`/vsirar/{/path/to/the/archive}/path/inside/the/archive`. Note that" +" :file:`/path/to/the/archive` may also itself use this alternate syntax." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:270 +msgid "Network based file systems" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:272 +msgid "" +"A generic :ref:`/vsicurl/ <vsicurl>` file system handler exists for " +"online resources that do not require particular signed authentication " +"schemes. It is specialized into sub-filesystems for commercial cloud " +"storage services, such as :ref:`/vsis3/ <vsis3>`, :ref:`/vsigs/ " +"<vsigs>`, :ref:`/vsiaz/ <vsiaz>`, :ref:`/vsioss/ <vsioss>` or " +":ref:`/vsiswift/ <vsiswift>`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:274 +msgid "" +"When reading of entire files in a streaming way is possible, prefer using" +" the :ref:`/vsicurl_streaming/ <vsicurl_streaming>`, and its variants for" +" the above cloud storage services, for more efficiency." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:277 +msgid "How to set credentials ?" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:279 +msgid "" +"Cloud storage services require setting credentials. For some of them, " +"they can be provided through configuration files (~/.aws/config, ~/.boto," +" ..) or through environment variables / configuration options." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:283 +msgid "" +"Starting with GDAL 3.6, :cpp:func:`VSISetPathSpecificOption` can be used " +"to set configuration options with a granularity at the level of a file " +"path, which makes it easier if using the same virtual file system but " +"with different credentials (e.g. different credentials for bucket " +"\"/vsis3/foo\" and \"/vsis3/bar\")" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:288 +msgid "" +"Starting with GDAL 3.5, credentials (or path specific options) can be " +"specified in a :ref:`GDAL configuration file <gdal_configuration_file>`, " +"either in a specific one explicitly loaded with " +":cpp:func:`CPLLoadConfigOptionsFromFile`, or one of the default " +"automatically loaded by " +":cpp:func:`CPLLoadConfigOptionsFromPredefinedFiles`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:293 +msgid "" +"They should be put under a ``[credentials]`` section, and for each path " +"prefix, under a relative subsection whose name starts with ``[.`` (e.g. " +"``[.some_arbitrary_name]``), and whose first key is ``path``. ` .. code-" +"block::" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:311 +msgid "Network/cloud-friendliness and file formats" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:313 +msgid "" +"While most GDAL raster and vector file systems can be accessed in a " +"remote way with /vsicurl/ and other derived virtual file systems, " +"performance is highly dependent on the format, and even for a given " +"format on the special data arrangement. Performance also depends on the " +"particular access pattern made to the file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:319 +msgid "" +"For interactive visualisation of raster files, the file should ideally " +"have the following characteristics:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:322 +msgid "it should be tiled in generally square-shaped tiles." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:323 +msgid "it should have an index of the tile location within the file" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:324 +msgid "it should have overviews/pyramids" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:327 +msgid "TIFF/GeoTIFF" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:329 +msgid "" +"Cloud-optimized GeoTIFF files as generated by the :ref:`raster.cog` " +"driver are suitable for network access. More generally tiled GeoTIFF " +"files with overviews are." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:336 +msgid "" +"JPEG2000 is generally not suitable for network access, unless using a " +"layout carefully designed for that purpose, and when using a JPEG200 " +"library that is heavily optimized." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:340 +msgid "" +"JPEG2000 files can come in many flavors : single-tiled vs tiled, with " +"different progression order (this is of particular importance for single-" +"tiled access), and with optional markers" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:344 +msgid "" +"The OpenJPEG library (usable through the :ref:`raster.jp2openjpeg` " +"driver), at the time of writing, needs to ingest each tile-part that " +"participates to the area of interest of the pixel query in a whole (and " +"thus for a single-tiled file, to ingest the whole file). It also does not" +" make use of the potentially present TLM (Tile-Part length) marker, which" +" is the equivalent of a tile index, nor PLT (Packed Length, tile-part " +"header), which is an index of packets within a tile. The Kakadu library " +"(usable through the :ref:`raster.jp2kak` driver), can use those markers " +"to limit the number of bytes to ingest (but for single-tiled raster, " +"performance might still suffer.)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:354 +msgid "" +"The `dump_jp2.py " +"<https://raw.githubusercontent.com/OSGeo/gdal/master/swig/python/gdal-" +"utils/osgeo_utils/samples/dump_jp2.py>`__ Python script can be used to " +"check the characteristics of a given JPEG200 file. Fields of interest to " +"examine in the output are:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:358 +msgid "" +"the tile size (given by the ``XTsiz`` and ``YTsiz`` fields in the ``SIZ``" +" marker)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:359 +msgid "the presence of ``TLM`` markers" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:360 +msgid "the presence of ``PLT`` markers" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:365 +msgid "/vsicurl/ (http/https/ftp files: random access)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:367 +msgid "" +"/vsicurl/ is a file system handler that allows on-the-fly random reading " +"of files available through HTTP/FTP web protocols, without prior download" +" of the entire file. It requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:369 +msgid "" +"Recognized filenames are of the form " +":file:`/vsicurl/http[s]://path/to/remote/resource` or " +":file:`/vsicurl/ftp://path/to/remote/resource`, where " +":file:`path/to/remote/resource` is the URL of a remote resource." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:371 +msgid "Example using :program:`ogrinfo` to read a shapefile on the internet:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:377 +msgid "" +"Starting with GDAL 2.3, options can be passed in the filename with the " +"following syntax: ``/vsicurl?[option_i=val_i&]*url=http://...`` where " +"each option name and value (including the value of \"url\") is URL-" +"encoded. Currently supported options are:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:379 +msgid "" +"use_head=yes/no: whether the HTTP HEAD request can be emitted. Default to" +" YES. Setting this option overrides the behavior of the " +":config:`CPL_VSIL_CURL_USE_HEAD` configuration option." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:380 +msgid "" +"max_retry=number: default to 0. Setting this option overrides the " +"behavior of the :config:`GDAL_HTTP_MAX_RETRY` configuration option." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:381 +msgid "" +"retry_delay=number_in_seconds: default to 30. Setting this option " +"overrides the behavior of the :config:`GDAL_HTTP_RETRY_DELAY` " +"configuration option." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:382 +msgid "" +"retry_codes=``ALL`` or comma-separated list of HTTP error codes. Setting " +"this option overrides the behavior of the :config:`GDAL_HTTP_RETRY_CODES`" +" configuration option. (GDAL >= 3.10)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:383 +msgid "" +"list_dir=yes/no: whether an attempt to read the file list of the " +"directory where the file is located should be done. Default to YES." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:384 +msgid "useragent=value: HTTP UserAgent header" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:385 +msgid "referer=value: HTTP Referer header" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:386 +msgid "cookie=value: HTTP Cookie header" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:387 +msgid "" +"header_file=value: Filename that contains one or several \"Header: " +"Value\" lines" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:388 +msgid "unsafessl=yes/no" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:389 +msgid "low_speed_time=value" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:390 +msgid "low_speed_limit=value" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:391 +msgid "proxy=value" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:392 +msgid "proxyauth=value" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:393 +msgid "proxyuserpwd=value" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:394 +msgid "" +"pc_url_signing=yes/no: whether to use the URL signing mechanism of " +"Microsoft Planetary Computer " +"(https://planetarycomputer.microsoft.com/docs/concepts/sas/). (GDAL >= " +"3.5.2). Note that starting with GDAL 3.9, this may also be set with the " +"path-specific option ( cf :cpp:func:`VSISetPathSpecificOption`) " +"``VSICURL_PC_URL_SIGNING`` set to ``YES``." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:395 +msgid "" +"pc_collection=name: name of the collection of the dataset for Planetary " +"Computer URL signing. Only used when pc_url_signing=yes. (GDAL >= 3.5.2)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:397 +msgid "" +"Partial downloads (requires the HTTP server to support random reading) " +"are done with a 16 KB granularity by default. Starting with GDAL 2.3, the" +" chunk size can be configured with the :config:`CPL_VSIL_CURL_CHUNK_SIZE`" +" configuration option, with a value in bytes. If the driver detects " +"sequential reading, it will progressively increase the chunk size up to " +"128 times :config:`CPL_VSIL_CURL_CHUNK_SIZE` (so 2 MB by default) to " +"improve download performance." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:399 +msgid "" +"In addition, a global least-recently-used cache of 16 MB shared among all" +" downloaded content is used, and content in it may be reused after a file" +" handle has been closed and reopen, during the life-time of the process " +"or until :cpp:func:`VSICurlClearCache` is called. Starting with GDAL 2.3," +" the size of this global LRU cache can be modified by setting the " +"configuration option :config:`CPL_VSIL_CURL_CACHE_SIZE` (in bytes)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:401 +msgid "" +"When increasing the value of :config:`CPL_VSIL_CURL_CHUNK_SIZE` to " +"optimize sequential reading, it is recommended to increase " +":config:`CPL_VSIL_CURL_CACHE_SIZE` as well to 128 times the value of " +":config:`CPL_VSIL_CURL_CHUNK_SIZE`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:403 +msgid "" +"Starting with GDAL 2.3, the :config:`GDAL_INGESTED_BYTES_AT_OPEN` " +"configuration option can be set to impose the number of bytes read in one" +" GET call at file opening (can help performance to read Cloud optimized " +"geotiff with a large header)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:405 +#: ../../source/user/virtual_file_systems.rst:455 +msgid "" +"The :config:`GDAL_HTTP_PROXY` (for both HTTP and HTTPS protocols), " +":config:`GDAL_HTTPS_PROXY` (for HTTPS protocol only), " +":config:`GDAL_HTTP_PROXYUSERPWD` and :config:`GDAL_PROXY_AUTH` " +"configuration options can be used to define a proxy server. The syntax to" +" use is the one of Curl ``CURLOPT_PROXY``, ``CURLOPT_PROXYUSERPWD`` and " +"``CURLOPT_PROXYAUTH`` options." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:407 +#: ../../source/user/virtual_file_systems.rst:457 +msgid "" +"Starting with GDAL 2.1.3, the :config:`CURL_CA_BUNDLE` or " +":config:`SSL_CERT_FILE` configuration options can be used to set the path" +" to the Certification Authority (CA) bundle file (if not specified, curl " +"will use a file in a system location)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:409 +msgid "" +"Starting with GDAL 2.3, additional HTTP headers can be sent by setting " +"the :config:`GDAL_HTTP_HEADER_FILE` configuration option to point to a " +"filename of a text file with \"key: value\" HTTP headers." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:411 +msgid "" +"As an alternative, starting with GDAL 3.6, the " +":config:`GDAL_HTTP_HEADERS` configuration option can also be used to " +"specify headers. :config:`CPL_CURL_VERBOSE=YES` allows one to see them " +"and more, when combined with ``--debug``." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:415 +msgid "" +"Starting with GDAL 2.3, the :config:`GDAL_HTTP_MAX_RETRY` (number of " +"attempts) and :config:`GDAL_HTTP_RETRY_DELAY` (in seconds) configuration " +"option can be set, so that request retries are done in case of HTTP " +"errors 429, 502, 503 or 504." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:417 +msgid "" +"Starting with GDAL 3.6, the following configuration options control the " +"TCP keep-alive functionality (cf https://daniel.haxx.se/blog/2020/02/10" +"/curl-ootw-keepalive-time/ for a detailed explanation):" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:419 +msgid "" +":config:`GDAL_HTTP_TCP_KEEPALIVE` = YES/NO. whether to enable TCP keep-" +"alive. Defaults to NO" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:420 +msgid "" +":config:`GDAL_HTTP_TCP_KEEPIDLE` = integer, in seconds. Keep-alive idle " +"time. Defaults to 60. Only taken into account if " +"GDAL_HTTP_TCP_KEEPALIVE=YES." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:421 +msgid "" +":config:`GDAL_HTTP_TCP_KEEPINTVL` = integer, in seconds. Interval time " +"between keep-alive probes. Defaults to 60. Only taken into account if " +"GDAL_HTTP_TCP_KEEPALIVE=YES." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:423 +msgid "" +"Starting with GDAL 3.7, the following configuration options control " +"support for SSL client certificates:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:425 +msgid "" +":config:`GDAL_HTTP_SSLCERT` = filename. Filename of the the SSL client " +"certificate. Cf https://curl.se/libcurl/c/CURLOPT_SSLCERT.html" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:426 +msgid "" +":config:`GDAL_HTTP_SSLCERTTYPE` = string. Format of the SSL certificate: " +"\"PEM\" or \"DER\". Cf https://curl.se/libcurl/c/CURLOPT_SSLCERTTYPE.html" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:427 +msgid "" +":config:`GDAL_HTTP_SSLKEY` = filename. Private key file for TLS and SSL " +"client certificate. Cf https://curl.se/libcurl/c/CURLOPT_SSLKEY.html" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:428 +msgid "" +":config:`GDAL_HTTP_KEYPASSWD` = string. Passphrase to private key. Cf " +"https://curl.se/libcurl/c/CURLOPT_KEYPASSWD.html" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:430 +msgid "" +"More generally options of :cpp:func:`CPLHTTPFetch` available through " +"configuration options are available. Starting with GDAL 3.7, the above " +"configuration options can also be specified as path-specific options with" +" :cpp:func:`VSISetPathSpecificOption`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:434 +msgid "" +"The file can be cached in RAM by setting the configuration option " +":config:`VSI_CACHE` to ``TRUE``. The cache size defaults to 25 MB, but " +"can be modified by setting the configuration option " +":config:`VSI_CACHE_SIZE` (in bytes). Content in that cache is discarded " +"when the file handle is closed." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:436 +msgid "" +"Starting with GDAL 2.3, the :config:`CPL_VSIL_CURL_NON_CACHED` " +"configuration option can be set to values like " +":file:`/vsicurl/http://example.com/foo.tif:/vsicurl/http://example.com/some_directory`," +" so that at file handle closing, all cached content related to the " +"mentioned file(s) is no longer cached. This can help when dealing with " +"resources that can be modified during execution of GDAL related code. " +"Alternatively, :cpp:func:`VSICurlClearCache` can be used." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:438 +msgid "" +"Starting with GDAL 2.1, ``/vsicurl/`` will try to query directly " +"redirected URLs to Amazon S3 signed URLs during their validity period, so" +" as to minimize round-trips. This behavior can be disabled by setting the" +" configuration option :config:`CPL_VSIL_CURL_USE_S3_REDIRECT` to ``NO``." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:440 +#: ../../source/user/virtual_file_systems.rst:461 +msgid "" +":cpp:func:`VSIStatL` will return the size in st_size member and file " +"nature- file or directory - in st_mode member (the later only reliable " +"with FTP resources for now)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:442 +msgid "" +":cpp:func:`VSIReadDir` should be able to parse the HTML directory listing" +" returned by the most popular web servers, such as Apache and Microsoft " +"IIS." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:447 +msgid "/vsicurl_streaming/ (http/https/ftp files: streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:449 +msgid "" +"/vsicurl_streaming/ is a file system handler that allows on-the-fly " +"sequential reading of files streamed through HTTP/FTP web protocols, " +"without prior download of the entire file. It requires GDAL to be built " +"against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:451 +msgid "" +"Although this file handler is able seek to random offsets in the file, " +"this will not be efficient. If you need efficient random access and that " +"the server supports range downloading, you should use the :ref:`/vsicurl/" +" <vsicurl>` file system handler instead." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:453 +msgid "" +"Recognized filenames are of the form " +":file:`/vsicurl_streaming/http[s]://path/to/remote/resource` or " +":file:`/vsicurl_streaming/ftp://path/to/remote/resource`, where " +":file:`path/to/remote/resource` is the URL of a remote resource." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:459 +msgid "" +"The file can be cached in RAM by setting the configuration option " +":config:`VSI_CACHE` to ``TRUE``. The cache size defaults to 25 MB, but " +"can be modified by setting the configuration option " +":config:`VSI_CACHE_SIZE` (in bytes)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:466 +msgid "/vsis3/ (AWS S3 files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:468 +msgid "" +"/vsis3/ is a file system handler that allows on-the-fly random reading of" +" (primarily non-public) files available in AWS S3 buckets, without prior " +"download of the entire file. It requires GDAL to be built against " +"libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:470 +msgid "" +"It also allows sequential writing of files. No seeks or read operations " +"are then allowed, so in particular direct writing of GeoTIFF files with " +"the GTiff driver is not supported, unless, if, starting with GDAL 3.2, " +"the :config:`CPL_VSIL_USE_TEMP_FILE_FOR_RANDOM_WRITE` configuration " +"option is set to ``YES``, in which case random-write access is possible " +"(involves the creation of a temporary local file, whose location is " +"controlled by the :config:`CPL_TMPDIR` configuration option). Deletion of" +" files with :cpp:func:`VSIUnlink` is also supported. Starting with GDAL " +"2.3, creation of directories with :cpp:func:`VSIMkdir` and deletion of " +"(empty) directories with :cpp:func:`VSIRmdir` are also possible." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:474 +msgid "" +"Recognized filenames are of the form :file:`/vsis3/bucket/key`, where " +"``bucket`` is the name of the S3 bucket and ``key`` is the S3 object " +"\"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:476 +#: ../../source/user/virtual_file_systems.rst:690 +#: ../../source/user/virtual_file_systems.rst:804 +#: ../../source/user/virtual_file_systems.rst:935 +#: ../../source/user/virtual_file_systems.rst:991 +#: ../../source/user/virtual_file_systems.rst:1119 +msgid "The generalities of :ref:`/vsicurl/ <vsicurl>` apply." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:478 +msgid "The following configuration options are specific to the /vsis3/ handler:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:533 +msgid "" +"Path to file with identity token for use for authentication via the " +"`AssumeRoleWithWebIdentity API " +"<https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithWebIdentity.html>`_." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:609 +#: ../../source/user/virtual_file_systems.rst:758 +#: ../../source/user/virtual_file_systems.rst:861 +msgid "" +"Several authentication methods are possible, and are attempted in the " +"following order:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:611 +msgid "" +"If :config:`AWS_NO_SIGN_REQUEST=YES` configuration option is set, request" +" signing is disabled. This option might be used for buckets with public " +"access rights. Available since GDAL 2.3" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:612 +msgid "" +"The :config:`AWS_SECRET_ACCESS_KEY` and :config:`AWS_ACCESS_KEY_ID` " +"configuration options can be set. The :config:`AWS_SESSION_TOKEN` " +"configuration option must be set when temporary credentials are used." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:613 +msgid "" +"Starting with GDAL 2.3, alternate ways of providing credentials similar " +"to what the \"aws\" command line utility or Boto3 support can be used. If" +" the above mentioned environment variables are not provided, the " +"``~/.aws/credentials`` or ``%UserProfile%/.aws/credentials`` file will be" +" read (or the file pointed by :config:`CPL_AWS_CREDENTIALS_FILE`). The " +"profile may be specified with the :config:`AWS_DEFAULT_PROFILE` " +"environment variable, or starting with GDAL 3.2 with the " +":config:`AWS_PROFILE` environment variable (the default profile is " +"\"default\")." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:614 +msgid "" +"The ``~/.aws/config`` or ``%UserProfile%/.aws/config`` file may also be " +"used (or the file pointer by :config:`AWS_CONFIG_FILE`) to retrieve " +"credentials and the AWS region." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:615 +msgid "" +"Starting with GDAL 3.6, if :config:`AWS_ROLE_ARN` and " +":config:`AWS_WEB_IDENTITY_TOKEN_FILE` are defined we will rely on " +"credentials mechanism for web identity token based AWS STS action " +"AssumeRoleWithWebIdentity (See.: " +"https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-" +"accounts.html)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:616 +msgid "" +"If none of the above method succeeds, instance profile credentials will " +"be retrieved when GDAL is used on EC2 instances (cf :ref:`vsis3_imds`)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:618 +msgid "" +"On writing, the file is uploaded using the S3 multipart upload API. The " +"size of chunks is set to 50 MB by default, allowing creating files up to " +"500 GB (10000 parts of 50 MB each). If larger files are needed, then " +"increase the value of the :config:`VSIS3_CHUNK_SIZE` config option to a " +"larger value (expressed in MB). In case the process is killed and the " +"file not properly closed, the multipart upload will remain open, causing " +"Amazon to charge you for the parts storage. You'll have to abort yourself" +" with other means such \"ghost\" uploads (e.g. with the s3cmd utility) " +"For files smaller than the chunk size, a simple PUT request is used " +"instead of the multipart upload API." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:620 +#: ../../source/user/virtual_file_systems.rst:877 +msgid "" +"Since GDAL 3.1, the :cpp:func:`VSIRename` operation is supported (first " +"doing a copy of the original file and then deleting it)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:622 +msgid "" +"Since GDAL 3.1, the :cpp:func:`VSIRmdirRecursive` operation is supported " +"(using batch deletion method). The " +":config:`CPL_VSIS3_USE_BASE_RMDIR_RECURSIVE` configuration option can be " +"set to YES if using a S3-like API that doesn't support batch deletion " +"(GDAL >= 3.2). Starting with GDAL 3.6, this can be set as a path-specific" +" option in the :ref:`GDAL configuration file <gdal_configuration_file>`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:624 +msgid "" +"The :config:`CPL_VSIS3_CREATE_DIR_OBJECT` configuration option can be set" +" to NO to prevent the :cpp:func:`VSIMkdir` operation from creating an " +"empty object with the name of the directory terminated with a slash " +"directory. By default GDAL creates such object, so that empty directories" +" can be modeled, but this may cause compatibility problems with " +"applications that do not expect such empty objects." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:627 +msgid "" +"Starting with GDAL 3.5, profiles that use IAM role assumption (see " +"https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-role.html)" +" are handled. The ``role_arn`` and ``source_profile`` keywords are " +"required in such profiles. The optional ``external_id``, ``mfa_serial`` " +"and ``role_session_name`` can be specified. ``credential_source`` is not " +"supported currently." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:632 +msgid "/vsis3/ and AWS Instance Metadata Service (IMDS)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:634 +msgid "" +"On EC2 instances, GDAL will try to use the `IMDSv2 " +"<https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-" +"instance-metadata-service.html>`__ protocol in priority to get the " +"authentication tokens for AWS S3, and fallback to IMDSv1 in case of " +"failure. Note however that on recent Amazon Linux instances, IMDSv1 is no" +" longer accessible, and thus IMDSv2 must be correctly configured (and " +"even if IMDSv1 is available, mis-configured IMDSv2 will cause delays in " +"the authentication step)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:636 +msgid "" +"There are known issues when running inside a Docker instance in a EC2 " +"instance that require extra configuration of the instance. For example, " +"you need to `increase the hop limit to 2 " +"<https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-" +"retrieval.html#imds-considerations>`__" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:638 +msgid "There are several ways to do this. One way is to run this command: ::" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:646 +msgid "" +"Another is to set the HttpPutResponseHopLimit metadata on an " +"AutoScalingGroup LaunchTemplate: - " +"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_InstanceMetadataOptionsRequest.html" +" - https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-" +"properties-ec2-launchtemplate-metadataoptions.html" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:650 +msgid "" +"Another possibility is to start the Docker container with host networking" +" (``--network=host``), although this breaks isolation of containers by " +"exposing all ports of the host to the container and has thus `security " +"implications <https://stackoverflow.com/a/57051970/40785>`__." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:653 +msgid "Configuring /vsis3/ with Minio" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:655 +msgid "" +"The following configuration options can be set to access a `Minio Docker " +"image <https://min.io/docs/minio/container/index.html>`__" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:658 +msgid "AWS_VIRTUAL_HOSTING=FALSE" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:659 +msgid "AWS_HTTPS=NO" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:660 +msgid "AWS_S3_ENDPOINT=\"localhost:9000\"" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:661 +msgid "AWS_REGION=\"us-east-1\"" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:662 +msgid "AWS_SECRET_ACCESS_KEY=\"your_secret_access_key\"" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:663 +msgid "AWS_ACCESS_KEY_ID=\"your_access_key\"" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:668 +msgid "/vsis3_streaming/ (AWS S3 files: streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:670 +msgid "" +"/vsis3_streaming/ is a file system handler that allows on-the-fly " +"sequential reading of (primarily non-public) files available in AWS S3 " +"buckets, without prior download of the entire file. It requires GDAL to " +"be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:672 +msgid "" +"Recognized filenames are of the form :file:`/vsis3_streaming/bucket/key` " +"where ``bucket`` is the name of the S3 bucket and ``key`` is the S3 " +"object \"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:674 +msgid "" +"Authentication options, and read-only features, are identical to " +":ref:`/vsis3/ <vsis3>`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:681 +msgid "/vsigs/ (Google Cloud Storage files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:683 +msgid "" +"/vsigs/ is a file system handler that allows on-the-fly random reading of" +" (primarily non-public) files available in Google Cloud Storage buckets, " +"without prior download of the entire file. It requires GDAL to be built " +"against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:685 +msgid "" +"Starting with GDAL 2.3, it also allows sequential writing of files. No " +"seeks or read operations are then allowed, so in particular direct " +"writing of GeoTIFF files with the GTiff driver is not supported, unless, " +"if, starting with GDAL 3.2, the " +":config:`CPL_VSIL_USE_TEMP_FILE_FOR_RANDOM_WRITE` configuration option is" +" set to ``YES``, in which case random-write access is possible (involves " +"the creation of a temporary local file, whose location is controlled by " +"the :config:`CPL_TMPDIR` configuration option). Deletion of files with " +":cpp:func:`VSIUnlink`, creation of directories with :cpp:func:`VSIMkdir` " +"and deletion of (empty) directories with :cpp:func:`VSIRmdir` are also " +"possible." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:688 +msgid "" +"Recognized filenames are of the form :file:`/vsigs/bucket/key` where " +"``bucket`` is the name of the bucket and ``key`` is the object \"key\", " +"i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:692 +msgid "The following configuration options are specific to the /vsigs/ handler:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:760 +msgid "" +"If :config:`GS_NO_SIGN_REQUEST=YES` configuration option is set, request " +"signing is disabled. This option might be used for buckets with public " +"access rights. Available since GDAL 3.4" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:761 +msgid "" +"The :config:`GS_SECRET_ACCESS_KEY` and :config:`GS_ACCESS_KEY_ID` " +"configuration options can be set for AWS-style authentication" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:762 +msgid "" +"The :config:`GDAL_HTTP_HEADER_FILE` configuration option to point to a " +"filename of a text file with \"key: value\" headers. Typically, it must " +"contain a \"Authorization: Bearer XXXXXXXXX\" line." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:763 +msgid "" +"(GDAL >= 3.7) The :config:`GDAL_HTTP_HEADERS` configuration option can " +"also be set. It must contain at least a line starting with " +"\"Authorization:\" to be used as an authentication method." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:764 +msgid "" +"(GDAL >= 2.3) The :config:`GS_OAUTH2_REFRESH_TOKEN` configuration option " +"can be set to use OAuth2 client authentication. See " +"http://code.google.com/apis/accounts/docs/OAuth2.html This refresh token " +"can be obtained with the ``gdal_auth.py -s storage`` or ``gdal_auth.py -s" +" storage-rw`` script Note: instead of using the default GDAL application " +"credentials, you may define the :config:`GS_OAUTH2_CLIENT_ID` and " +":config:`GS_OAUTH2_CLIENT_SECRET` configuration options (need to be " +"defined both for gdal_auth.py and later execution of /vsigs)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:765 +msgid "" +"(GDAL >= 2.3) The :config:`GOOGLE_APPLICATION_CREDENTIALS` configuration " +"option can be set to point to a JSON file containing OAuth2 service " +"account credentials (``type: service_account``), in particular a private " +"key and a client email. See " +"https://developers.google.com/identity/protocols/OAuth2ServiceAccount for" +" more details on this authentication method. The bucket must grant the " +"\"Storage Legacy Bucket Owner\" or \"Storage Legacy Bucket Reader\" " +"permissions to the service account. The :config:`GS_OAUTH2_SCOPE` " +"configuration option can be set to change the default permission scope " +"from \"https://www.googleapis.com/auth/devstorage.read_write\" to " +"\"https://www.googleapis.com/auth/devstorage.read_only\" if needed." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:766 +msgid "" +"(GDAL >= 3.4.2) The :config:`GOOGLE_APPLICATION_CREDENTIALS` " +"configuration option can be set to point to a JSON file containing OAuth2" +" user credentials (``type: authorized_user``)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:767 +msgid "" +"(GDAL >= 2.3) Variant of the previous method. The " +":config:`GS_OAUTH2_PRIVATE_KEY` (or :config:`GS_OAUTH2_PRIVATE_KEY_FILE` " +"and :config:`GS_OAUTH2_CLIENT_EMAIL` can be set to use OAuth2 service " +"account authentication. See " +"https://developers.google.com/identity/protocols/OAuth2ServiceAccount for" +" more details on this authentication method. The " +":config:`GS_OAUTH2_PRIVATE_KEY` configuration option must contain the " +"private key as a inline string, starting with ``-----BEGIN PRIVATE " +"KEY-----``. Alternatively the :config:`GS_OAUTH2_PRIVATE_KEY_FILE` " +"configuration option can be set to indicate a filename that contains such" +" a private key. The bucket must grant the \"Storage Legacy Bucket Owner\"" +" or \"Storage Legacy Bucket Reader\" permissions to the service account. " +"The :config:`GS_OAUTH2_SCOPE` configuration option can be set to change " +"the default permission scope from " +"\"https://www.googleapis.com/auth/devstorage.read_write\" to " +"\"https://www.googleapis.com/auth/devstorage.read_only\" if needed." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:768 +msgid "" +"(GDAL >= 2.3) An alternate way of providing credentials similar to what " +"the \"gsutil\" command line utility or Boto3 support can be used. If the " +"above mentioned environment variables are not provided, the " +":file:`~/.boto` or :file:`UserProfile%/.boto` file will be read (or the " +"file pointed by :config:`CPL_GS_CREDENTIALS_FILE`) for the " +"gs_secret_access_key and gs_access_key_id entries for AWS style " +"authentication. If not found, it will look for the " +"gs_oauth2_refresh_token (and optionally client_id and client_secret) " +"entry for OAuth2 client authentication." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:769 +msgid "" +"(GDAL >= 2.3) Finally if none of the above method succeeds, the code will" +" check if the current machine is a Google Compute Engine instance, and if" +" so will use the permissions associated to it (using the default service " +"account associated with the VM). To force a machine to be detected as a " +"GCE instance (for example for code running in a container with no access " +"to the boot logs), you can set :config:`CPL_MACHINE_IS_GCE` to ``YES``." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:771 +msgid "" +"Since GDAL 3.1, the Rename() operation is supported (first doing a copy " +"of the original file and then deleting it)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:778 +msgid "/vsigs_streaming/ (Google Cloud Storage files: streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:780 +msgid "" +"/vsigs_streaming/ is a file system handler that allows on-the-fly " +"sequential reading of files (primarily non-public) files available in " +"Google Cloud Storage buckets, without prior download of the entire file. " +"It requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:782 +msgid "" +"Recognized filenames are of the form :file:`/vsigs_streaming/bucket/key` " +"where ``bucket`` is the name of the bucket and ``key`` is the object " +"\"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:784 +msgid "" +"Authentication options, and read-only features, are identical to " +":ref:`/vsigs/ <vsigs>`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:791 +msgid "/vsiaz/ (Microsoft Azure Blob files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:793 +msgid "" +"/vsiaz/ is a file system handler that allows on-the-fly random reading of" +" (primarily non-public) files available in Microsoft Azure Blob " +"containers, without prior download of the entire file. It requires GDAL " +"to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:795 +msgid "" +"See :ref:`/vsiadls/ <vsiadls>` for a related filesystem for Azure Data " +"Lake Storage Gen2." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:797 +msgid "" +"It also allows sequential writing of files. No seeks or read operations " +"are then allowed, so in particular direct writing of GeoTIFF files with " +"the GTiff driver is not supported, unless, if, starting with GDAL 3.2, " +"the :config:`CPL_VSIL_USE_TEMP_FILE_FOR_RANDOM_WRITE` configuration " +"option is set to ``YES``, in which case random-write access is possible " +"(involves the creation of a temporary local file, whose location is " +"controlled by the :config:`CPL_TMPDIR` configuration option). A block " +"blob will be created if the file size is below 4 MB. Beyond, an append " +"blob will be created (with a maximum file size of 195 GB)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:800 +msgid "" +"Deletion of files with :cpp:func:`VSIUnlink`, creation of directories " +"with :cpp:func:`VSIMkdir` and deletion of (empty) directories with " +":cpp:func:`VSIRmdir` are also possible. Note: when using " +":cpp:func:`VSIMkdir`, a special hidden :file:`.gdal_marker_for_dir` empty" +" file is created, since Azure Blob does not natively support empty " +"directories. If that file is the last one remaining in a directory, " +":cpp:func:`VSIRmdir` will automatically remove it. This file will not be " +"seen with :cpp:func:`VSIReadDir`. If removing files from directories not " +"created with :cpp:func:`VSIMkdir`, when the last file is deleted, its " +"directory is automatically removed by Azure, so the sequence " +"``VSIUnlink(\"/vsiaz/container/subdir/lastfile\")`` followed by " +"``VSIRmdir(\"/vsiaz/container/subdir\")`` will fail on the " +":cpp:func:`VSIRmdir` invocation." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:802 +msgid "" +"Recognized filenames are of the form :file:`/vsiaz/container/key`, where " +"``container`` is the name of the container and ``key`` is the object " +"\"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:806 +msgid "The following configuration options are specific to the /vsiaz/ handler:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:863 +msgid "The :config:`AZURE_STORAGE_CONNECTION_STRING` configuration option" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:865 +msgid "" +"The :config:`AZURE_STORAGE_ACCOUNT` configuration option is set to " +"specify the account name AND" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:867 +msgid "" +"(GDAL >= 3.5) The :config:`AZURE_STORAGE_ACCESS_TOKEN` configuration " +"option is set to specify the access token, that will be included in a " +"\"Authorization: Bearer ${AZURE_STORAGE_ACCESS_TOKEN}\" header. This " +"access token is typically obtained using Microsoft Authentication Library" +" (MSAL)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:868 +msgid "" +"The :config:`AZURE_STORAGE_ACCESS_KEY` configuration option is set to " +"specify the secret key." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:869 +msgid "" +"The :config:`AZURE_NO_SIGN_REQUEST=YES` configuration option is set, so " +"as to disable any request signing. This option might be used for accounts" +" with public access rights. Available since GDAL 3.2" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:870 +msgid "" +"The :config:`AZURE_STORAGE_SAS_TOKEN` configuration option (``AZURE_SAS``" +" if GDAL < 3.5) is set to specify a Shared Access Signature. This SAS is " +"appended to URLs built by the /vsiaz/ file system handler. Its value " +"should already be URL-encoded and should not contain any leading '?' or " +"'&' character (e.g. a valid one may look like " +"\"st=2019-07-18T03%3A53%3A22Z&se=2035-07-19T03%3A53%3A00Z&sp=rl&sv=2018-03-28&sr=c&sig=2RIXmLbLbiagYnUd49rgx2kOXKyILrJOgafmkODhRAQ%3D\")." +" Available since GDAL 3.2" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:871 +msgid "" +"The current machine is a Azure Virtual Machine with Azure Active " +"Directory permissions assigned to it (see https://docs.microsoft.com/en-" +"us/azure/active-directory/managed-identities-azure-resources/qs-" +"configure-portal-windows-vm). Available since GDAL 3.3." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:873 +msgid "" +"Authentication using Azure Active Directory Workload Identity (using " +"AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_FEDERATED_TOKEN_FILE and " +"AZURE_AUTHORITY_HOST environment variables), typically for Azure " +"Kubernetes, is available since GDAL 3.7.2" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:875 +msgid "" +"Starting with GDAL 3.5, the `configuration file " +"<https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-" +"conceptual/azure-cli-configuration.md>` of the \"az\" command line " +"utility can be used. The following keys of the ``[storage]`` section will" +" be used in the following priority: ``connection_string``, ``account`` + " +"``key`` or ``account`` + ``sas_token``" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:879 +msgid "" +"Since GDAL 3.3, the :cpp:func:`VSIGetFileMetadata` and " +":cpp:func:`VSISetFileMetadata` operations are supported." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:886 +msgid "/vsiaz_streaming/ (Microsoft Azure Blob files: streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:888 +msgid "" +"/vsiaz_streaming/ is a file system handler that allows on-the-fly " +"sequential reading of files (primarily non-public) files available in " +"Microsoft Azure Blob containers, buckets, without prior download of the " +"entire file. It requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:890 +msgid "" +"Recognized filenames are of the form " +":file:`/vsiaz_streaming/container/key` where ``container`` is the name of" +" the container and ``key`` is the object \"key\", i.e. a filename " +"potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:892 +msgid "" +"Authentication options, and read-only features, are identical to " +":ref:`/vsiaz/ <vsiaz>`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:899 +msgid "/vsiadls/ (Microsoft Azure Data Lake Storage Gen2)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:901 +msgid "" +"/vsiadls/ is a file system handler that allows on-the-fly random reading " +"of (primarily non-public) files available in Microsoft Azure Data Lake " +"Storage file systems, without prior download of the entire file. It " +"requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:906 +msgid "" +"It has similar capabilities as :ref:`/vsiaz/ <vsiaz>`, and in particular " +"uses the same configuration options for authentication. Its advantages " +"over /vsiaz/ are a real management of directory and Unix-style ACL " +"support. Some features require the Azure storage to have hierarchical " +"support turned on. Consult its `documentation <https://docs.microsoft.com" +"/en-us/azure/storage/blobs/data-lake-storage-introduction>`__" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:912 +msgid "The main enhancements over /vsiaz/ are:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:914 +msgid "" +"True directory support (no need for the artificial " +":file:`.gdal_marker_for_dir` empty file that is used for /vsiaz/ to have " +"empty directories)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:916 +msgid "One-call recursive directory deletion with :cpp:func:`VSIRmdirRecursive`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:917 +msgid "Atomic renaming with :cpp:func:`VSIRename`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:918 +msgid "" +":cpp:func:`VSIGetFileMetadata` support for the \"STATUS\" and \"ACL\" " +"metadata domains" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:919 +msgid "" +":cpp:func:`VSISetFileMetadata` support for the \"PROPERTIES\" and \"ACL\"" +" metadata domains" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:926 +msgid "/vsioss/ (Alibaba Cloud OSS files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:928 +msgid "" +"/vsioss/ is a file system handler that allows on-the-fly random reading " +"of (primarily non-public) files available in Alibaba Cloud Object Storage" +" Service (OSS) buckets, without prior download of the entire file. It " +"requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:930 +#: ../../source/user/virtual_file_systems.rst:986 +#: ../../source/user/virtual_file_systems.rst:1116 +msgid "" +"It also allows sequential writing of files. No seeks or read operations " +"are then allowed, so in particular direct writing of GeoTIFF files with " +"the GTiff driver is not supported, unless, if, starting with GDAL 3.2, " +"the :config:`CPL_VSIL_USE_TEMP_FILE_FOR_RANDOM_WRITE` configuration " +"option is set to ``YES``, in which case random-write access is possible " +"(involves the creation of a temporary local file, whose location is " +"controlled by the :config:`CPL_TMPDIR` configuration option). Deletion of" +" files with :cpp:func:`VSIUnlink` is also supported. Creation of " +"directories with :cpp:func:`VSIMkdir` and deletion of (empty) directories" +" with :cpp:func:`VSIRmdir` are also possible." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:933 +msgid "" +"Recognized filenames are of the form :file:`/vsioss/bucket/key` where " +"``bucket`` is the name of the OSS bucket and ``key`` is the OSS object " +"\"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:937 +#: ../../source/user/virtual_file_systems.rst:993 +msgid "The following configuration options are specific to the /vsioss/ handler:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:960 +msgid "" +"The :config:`OSS_SECRET_ACCESS_KEY` and :config:`OSS_ACCESS_KEY_ID` " +"configuration options must be set. The :config:`OSS_ENDPOINT` " +"configuration option should normally be set to the appropriate value, " +"which reflects the region attached to the bucket. If the bucket is stored" +" in another region than oss-us-east-1, the code logic will redirect to " +"the appropriate endpoint." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:962 +msgid "" +"On writing, the file is uploaded using the OSS multipart upload API. The " +"size of chunks is set to 50 MB by default, allowing creating files up to " +"500 GB (10000 parts of 50 MB each). If larger files are needed, then " +"increase the value of the :config:`VSIOSS_CHUNK_SIZE` config option to a " +"larger value (expressed in MB). In case the process is killed and the " +"file not properly closed, the multipart upload will remain open, causing " +"Alibaba to charge you for the parts storage. You'll have to abort " +"yourself with other means. For files smaller than the chunk size, a " +"simple PUT request is used instead of the multipart upload API." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:969 +msgid "/vsioss_streaming/ (Alibaba Cloud OSS files: streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:971 +msgid "" +"/vsioss_streaming/ is a file system handler that allows on-the-fly " +"sequential reading of files (primarily non-public) files available in " +"Alibaba Cloud Object Storage Service (OSS) buckets, without prior " +"download of the entire file. It requires GDAL to be built against " +"libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:973 +msgid "" +"Recognized filenames are of the form :file:`/vsioss_streaming/bucket/key`" +" where ``bucket`` is the name of the bucket and ``key`` is the object " +"\"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:975 +msgid "" +"Authentication options, and read-only features, are identical to " +":ref:`/vsioss/ <vsioss>`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:982 +msgid "/vsiswift/ (OpenStack Swift Object Storage)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:984 +msgid "" +"/vsiswift/ is a file system handler that allows on-the-fly random reading" +" of (primarily non-public) files available in OpenStack Swift Object " +"Storage (swift) buckets, without prior download of the entire file. It " +"requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:989 +msgid "" +"Recognized filenames are of the form :file:`/vsiswift/bucket/key` where " +"``bucket`` is the name of the swift bucket and ``key`` is the swift " +"object \"key\", i.e. a filename potentially containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1015 +msgid "" +"Three authentication methods are possible, and are attempted in the " +"following order:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1017 +msgid "" +"The :config:`SWIFT_STORAGE_URL` and :config:`SWIFT_AUTH_TOKEN` " +"configuration options are set respectively to the storage URL (e.g " +"http://127.0.0.1:12345/v1/AUTH_something) and the value of the x-auth-" +"token authorization token." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1018 +msgid "" +"The :config:`SWIFT_AUTH_V1_URL`, :config:`SWIFT_USER` and " +":config:`SWIFT_KEY` configuration options are set respectively to the " +"endpoint of the Auth V1 authentication (e.g " +"http://127.0.0.1:12345/auth/v1.0), the user name and the key/password. " +"This authentication endpoint will be used to retrieve the storage URL and" +" authorization token mentioned in the first authentication method." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1019 +msgid "" +"Authentication with Keystone v3 is using the same options as python-" +"swiftclient, see https://docs.openstack.org/python-" +"swiftclient/latest/cli/index.html#authentication for more details. GDAL " +"(>= 3.1) supports the following options:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1021 +#: ../../source/user/virtual_file_systems.rst:1032 +msgid "`OS_IDENTITY_API_VERSION=3`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1022 +#: ../../source/user/virtual_file_systems.rst:1034 +msgid "`OS_AUTH_URL`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1023 +msgid "`OS_USERNAME`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1024 +msgid "`OS_PASSWORD`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1025 +msgid "`OS_USER_DOMAIN_NAME`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1026 +msgid "`OS_PROJECT_NAME`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1027 +msgid "`OS_PROJECT_DOMAIN_NAME`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1028 +#: ../../source/user/virtual_file_systems.rst:1037 +msgid "`OS_REGION_NAME`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1030 +msgid "" +"Application Credential Authentication via Keystone v3, GDAL (>= 3.3.1) " +"supports application-credential authentication with the following " +"options:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1033 +msgid "`OS_AUTH_TYPE=v3applicationcredential`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1035 +msgid "`OS_APPLICATION_CREDENTIAL_ID`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1036 +msgid "`OS_APPLICATION_CREDENTIAL_SECRET`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1039 +msgid "" +"This file system handler also allows sequential writing of files (no " +"seeks or read operations are then allowed)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1041 +msgid "" +"In some versions of OpenStack Swift, the access to large (segmented) " +"files fails unless they are explicitly marked as static large objects, " +"instead of being dynamic large objects which is the default. Using the " +"python-swiftclient this can be achieved when uploading the file by " +"passing the ``--use-slo`` flag (see https://docs.openstack.org/python-" +"swiftclient/latest/cli/index.html#swift-upload for all options). For more" +" information about large objects see " +"https://docs.openstack.org/swift/latest/api/large_objects.html." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1048 +msgid "/vsiswift_streaming/ (OpenStack Swift Object Storage: streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1050 +msgid "" +"/vsiswift_streaming/ is a file system handler that allows on-the-fly " +"sequential reading of files (primarily non-public) files available in " +"OpenStack Swift Object Storage (swift) buckets, without prior download of" +" the entire file. It requires GDAL to be built against libcurl." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1052 +msgid "" +"Recognized filenames are of the form " +":file:`/vsiswift_streaming/bucket/key` where ``bucket`` is the name of " +"the bucket and ``key`` is the object \"key\", i.e. a filename potentially" +" containing subdirectories." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1054 +msgid "" +"Authentication options, and read-only features, are identical to " +":ref:`/vsiswift/ <vsiswift>`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1061 +msgid "/vsihdfs/ (Hadoop File System)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1063 +msgid "" +"/vsihdfs/ is a file system handler that provides read access to HDFS. " +"This handler requires GDAL to have been built with Java support (CMake " +"`FindJNI <https://cmake.org/cmake/help/latest/module/FindJNI.html>`__) " +"and :ref:`HDFS <building_from_source_hdfs>` support. Support for this " +"handler is currently only available on Unix-like systems." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1069 +msgid "" +"Note: support for the HTTP REST API (webHdfs) is also available with " +":ref:`vsiwebhdfs`" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1071 +msgid "" +"The LD_LIBRARY_PATH and CLASSPATH environment variables must be typically" +" set up as following." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1081 +msgid "" +"Failure to properly define the CLASSPATH will result in hard crashes in " +"the native libhdfs." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1084 +msgid "Relevant Hadoop documentation links:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1086 +msgid "" +"`C API libhdfs <https://hadoop.apache.org/docs/stable/hadoop-project-dist" +"/hadoop-hdfs/LibHdfs.html>`__" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1087 +msgid "" +"`HDFS Users Guide <https://hadoop.apache.org/docs/stable/hadoop-project-" +"dist/hadoop-hdfs/HdfsUserGuide.html>`__" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1088 +msgid "" +"`Hadoop: Setting up a Single Node Cluster " +"<https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-" +"common/SingleCluster.html>`__" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1090 +msgid "" +"Recognized filenames are of the form :file:`/vsihdfs/hdfsUri` where " +"``hdfsUri`` is a valid HDFS URI." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1104 +msgid "/vsiwebhdfs/ (Web Hadoop File System REST API)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1106 +msgid "" +"/vsiwebhdfs/ is a file system handler that provides read and write access" +" to HDFS through its HTTP REST API." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1108 +msgid "" +"Recognized filenames are of the form " +":file:`/vsiwebhdfs/http://hostname:port/webhdfs/v1/path/to/filename`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1121 +msgid "The following configuration options are available:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1145 +msgid "" +"This file system handler also allows sequential writing of files (no " +"seeks or read operations are then allowed)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1152 +msgid "/vsistdin/ (standard input streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1154 +msgid "" +"/vsistdin/ is a file handler that allows reading from the standard input " +"stream." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1156 +msgid "" +"The filename syntax must be only :file:`/vsistdin/`, (not e.g., " +"/vsistdin/path/to/f.csv , but \"/vsistdin?buffer_limit=value\" is OK.)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1159 +msgid "" +"The file operations available are of course limited to Read() and forward" +" Seek(). Full seek in the first MB of a file is possible, and it is " +"cached so that closing, re-opening :file:`/vsistdin/` and reading within " +"this first megabyte is possible multiple times in the same process." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1164 +msgid "" +"The size of the in-memory cache can be controlled with the " +":config:`CPL_VSISTDIN_BUFFER_LIMIT` configuration option:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1174 +msgid "The \"/vsistdin?buffer_limit=value\" syntax can also be used." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1176 +msgid "" +"/vsistdin filenames can be combined with other file system. For example, " +"to read a file within a potentially big ZIP file streamed to " +"gdal_translate:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1187 +msgid "/vsistdout/ (standard output streaming)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1189 +msgid "" +"/vsistdout/ is a file handler that allows writing into the standard " +"output stream." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1191 +msgid "The filename syntax must be only :file:`/vsistdout/`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1193 +msgid "The file operations available are of course limited to Write()." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1195 +msgid "" +"A variation of this file system exists as the " +":file:`/vsistdout_redirect/` file system handler, where the output " +"function can be defined with :cpp:func:`VSIStdoutSetRedirection`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1200 +msgid "/vsimem/ (in-memory files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1202 +msgid "" +"/vsimem/ is a file handler that allows block of memory to be treated as " +"files. All portions of the file system underneath the base path " +":file:`/vsimem/` will be handled by this driver." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1204 +msgid "" +"Normal VSI*L functions can be used freely to create and destroy memory " +"arrays, treating them as if they were real file system objects. Some " +"additional methods exist to efficiently create memory file system objects" +" without duplicating original copies of the data or to \"steal\" the " +"block of memory associated with a memory file. See " +":cpp:func:`VSIFileFromMemBuffer` and :cpp:func:`VSIGetMemFileBuffer`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1206 +msgid "Directory related functions are supported." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1208 +msgid "" +"/vsimem/ files are visible within the same process. Multiple threads can " +"access the same underlying file in read mode, provided they used " +"different handles, but concurrent write and read operations on the same " +"underlying file are not supported (locking is left to the responsibility " +"of calling code)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1213 +msgid "/vsisubfile/ (portions of files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1215 +msgid "" +"The /vsisubfile/ virtual file system handler allows access to subregions " +"of files, treating them as a file on their own to the virtual file system" +" functions (VSIFOpenL(), etc)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1217 +msgid "" +"A special form of the filename is used to indicate a subportion of " +"another file: :file:`/vsisubfile/<offset>[_<size>],<filename>`." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1219 +msgid "" +"The size parameter is optional. Without it the remainder of the file from" +" the start offset as treated as part of the subfile. Otherwise only " +"<size> bytes from <offset> are treated as part of the subfile. The " +"<filename> portion may be a relative or absolute path using normal rules." +" The <offset> and <size> values are in bytes." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1228 +msgid "" +"Unlike the /vsimem/ or conventional file system handlers, there is no " +"meaningful support for filesystem operations for creating new files, " +"traversing directories, and deleting files within the /vsisubfile/ area. " +"Only the :cpp:func:`VSIStatL`, :cpp:func:`VSIFOpenL` and operations based" +" on the file handle returned by :cpp:func:`VSIFOpenL` operate properly." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1233 +msgid "/vsisparse/ (sparse files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1235 +msgid "" +"The /vsisparse/ virtual file handler allows a virtual file to be composed" +" from chunks of data in other files, potentially with large spaces in the" +" virtual file set to a constant value. This can make it possible to test " +"some sorts of operations on what seems to be a large file with image data" +" set to a constant value. It is also helpful when wanting to add test " +"files to the test suite that are too large, but for which most of the " +"data can be ignored. It could, in theory, also be used to treat several " +"files on different file systems as one large virtual file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1237 +msgid "" +"The file referenced by /vsisparse/ should be an XML control file " +"formatted something like:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1271 +msgid "Hopefully the values and semantics are fairly obvious." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1277 +msgid "/vsicached/ (File caching)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1279 +msgid "" +"The :cpp:func:`VSICreateCachedFile` function takes a virtual file handle " +"and returns a new handle that caches read-operations on the input file " +"handle. The cache is RAM based and the content of the cache is discarded " +"when the file handle is closed. The cache is a least-recently used lists " +"of blocks of 32KB each (default size)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1281 +msgid "" +"This is mostly useful for files accessible through slow local/operating-" +"system-mounted filesystems." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1283 +msgid "" +"That is implicitly used by a number of the above mentioned file systems " +"(namely the default one for standard file system operations, and the " +"/vsicurl/ and other related network file systems) if the ``VSI_CACHE`` " +"configuration option is set to ``YES``." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1285 +msgid "" +"The default size of caching for each file is 25 MB (25 MB for each file " +"that is cached), and can be controlled with the ``VSI_CACHE_SIZE`` " +"configuration option (value in bytes)." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1287 +msgid "" +"The :cpp:class:`VSICachedFile` class only handles read operations at that" +" time, and will error out on write operations." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1289 +msgid "" +"Starting with GDAL 3.8, a ``/vsicached?`` virtual file system also exists" +" to cache a particular file." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1291 +msgid "" +"The syntax is the following one: " +"``/vsicached?[option_i=val_i&]*file=<filename>`` where each option name " +"and value (including the value of ``file``) is URL-encoded (actually, " +"only required for the ampersand character. It might be desirable to have " +"forward slash character uncoded). It is important that the ``file`` " +"option appears at the end, so that code that tries to look for side-car " +"files, list directory content, can work properly." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1298 +msgid "Currently supported options are:" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1300 +msgid "" +"``chunk_size=<value>`` where value is the` size of the chunk size in " +"bytes. ``KB`` or ``MB`` suffixes can be also appended (without space " +"after the numeric value). The maximum supported value is 1 GB." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1301 +msgid "" +"``cache_size=<value>`` where value is the size of the cache size in " +"bytes, for each file. ``KB`` or ``MB`` suffixes can be also appended." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1305 +msgid "``/vsicached?chunk_size=1MB&file=/home/even/byte.tif``" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1306 +msgid "``/vsicached?file=./byte.tif``" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1312 +msgid "/vsicrypt/ (encrypted files)" +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1314 +msgid "" +"/vsicrypt/ is a special file handler is installed that allows " +"reading/creating/update encrypted files on the fly, with random access " +"capabilities." +msgstr "" + +#: ../../source/user/virtual_file_systems.rst:1316 +msgid "Refer to :cpp:func:`VSIInstallCryptFileHandler` for more details." +msgstr "" +